When Integration Server executes a request against a remote server, it issues an HTTP, HTTPS, FTP, or SOCKS request to the specified target server. For example, Integration Server might invoke a service on a remote Integration Server or execute a web service connector that invokes a web service. If your Integration Server sits behind a firewall, and must route these HTTP, HTTPS, FTP, or SOCKS requests through a third party proxy server, you can use Integration Server Administrator to identify one or more proxy servers to which Integration Server will route these requests.

For Integration Server to use a proxy server, you must define a proxy server alias. The proxy server alias identifies a proxy server and a port on the server through which you want to route requests.

You can configure Integration Server to route requests to one or more proxy server aliases for each type of outbound request (HTTP, HTTPS, FTP, and SOCKS).

You can specify a default proxy server for each protocol type. Integration Server uses the default proxy server alias when one is not specified by the pub.client:http, pub.client:ftp.login, or pub.client.ftp service. Integration Server also uses the default proxy server alias when executing a web service connector associated with an HTTP/S consumer web service endpoint alias that does not specify a proxy alias.