Integration Server Administrator's Guide : Configuring the Server : Specifying Third-Party Proxy Servers for Outbound Requests
Specifying Third-Party Proxy Servers for Outbound Requests
 
How Integration Server Uses Proxy Servers
Creating a Proxy Server Alias
Editing a Proxy Server Alias
Disabling a Proxy Server Alias
Enabling a Proxy Server Alias
Specifying a Default Proxy Server Alias
Deleting a Proxy Server Alias
Bypassing a Proxy Server
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.
Note:  
If you have configured and enabled a SOCKS proxy server alias, it acts as a fallback proxy server for HTTP, HTTPS, and FTP proxy server aliases. Even if a SOCKS proxy is set as the default proxy server alias, Integration Server gives precedence to the configured HTTP, HTTPS, and FTP proxy server aliases for the corresponding outbound requests before attempting to connect through the SOCKS proxy alias.
Copyright © 2017 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback