Reverse Invoke Alternatives?

I am looking for some ideas regarding best practices on inbound processing. Specifically, our firewall folks want us to use a solution that will prevent inbound files from going directly to our Integration Server. We are exploring the Reverse Invoke solution, but would like to see if others are using a solution other than Reverse Invoke. Any other solutions out there? Thank you.


Can you (or your firewall admins) be more specific about the concern of direct processing of files?

An alternate method is to use the Integration Server FTP function to write the file in the DMZ and then forward the file after receiving a put notification message.

Some customers don’t like this approach since it persists files in the DMZ.

– Tim

P.S. Please don’t cross post across forums!

I have implemented a solution for inbound processing without reverse invoke. It’s kind of involved, but here it is at a hihg level.

The partner calls a .net web service on the DMZ. This web service saves the inbound transmission to a file on the DMZ and writes a record into a SQL server databse inside the firewall. There is some functionality in .net that allows it through the filewall.

In webMethods, a database notifier is setup on this SQL server table. We pull the data out of the table and call another web service to retrieve the data from the box on the DMZ and delete the file. Then it takes the data and sends it to TN.

TN processes the data.

Here is another plan to look…

Host the IS in DMZ which receives the inbound requests and publish Broker document. The DMZ broker will communicate with inside Broker over SSL.