I have several clients using the Java XML integration which kinda works via magic. This is a module that is included with the integration module but it involves a separate installation checkbox in order to install it. Then, it creates a web hook listener which generates code language (FCL) for the integration module to process. OpenText created the following flow diagram several years ago that I always refer to when reviewing the Java XML integration.

When troubleshooting the Java XML application, the first thing I do is submit a sample job.
Postfile.exe -v -s <RFServerName> -o /rfxml/rfwebcon.dll "C:\Program Files (x86)\RightFax\Production\xml\examples\XML_FAX_SUBMIT_minimum.xml"
The output of the sample job will either generate the FCL code that is placed in the “INBOX” directory for the integration module. The inbox directory is also known as the default integration directory flow.
In the latest bout that I had with the integration, the other engineer changed the default inbox directory (0 stars, do not recommend) so the files were getting generated, but nothing was processing the directory that the FCL files were being placed. Once we configured the integration module to monitor that directory again, everything worked like a charm!
I used KB0779964 on OpenText knowledge portal to aid me in writing this blog post and whenever I have issues with this integration. It was written for Windows 2003, but its still a great source of data!
