Our client needs to call a webservice exposed by an external partner. Our client network configuration implies that only machines in the DMZ can call the external network.
The flow service from which the call to the webservice is initiated sits in an internal IS, which doesn’t have access to the “outworld”. We also have a gateway IS which sits in the DMZ and is consequently able to call the external network, but it isn’t designed to run any service, it only serves Reverse Invoke purposes.
I thought of placing a minimalist service executing the call to the external network on the DMZ IS, but as I said above, this is contrary to architecture design. I also tried configuring a simple HTTP Proxy in the internal IS, specifying the gateway IS as the Proxy Host, but it didn’t work. After reading the documentation about Proxy settings for outbound requests in Administrator’s Guide, I discovered that this feature is intended for third party proxy servers.
So my question is, does the IS have standard HTTP Proxy capabilities? If so, how do you configure an IS to use another IS as an HTTP Proxy for outbound requests?
We are using version 7.1.2 of Integration Server.
Thanks in advance to all who can help!