Software AG Products 10.5 | Administering Integration Server | Configuring the Server | Specifying Third-Party Proxy Servers for Outbound Requests | How Integration Server Uses Proxy Servers
 
How Integration Server Uses Proxy Servers
When Integration Server sends a request to a remote server, Integration Server routes the request through a proxy server unless the domain of the target server is listed as a proxy bypass. When a domain appears on the proxy bypass list, Integration Server sends requests directly to the target server. If a domain is not on the proxy bypass list, the proxy server that Integration Server uses to send the request depends on the following conditions:
*Whether the request specifies a proxy server alias
*Whether a default proxy server alias exists and is enabled.
The following table describes how Integration Server determines which proxy server to use when sending a request. This process applies to the HTTP, HTTPS, FTP, and SOCKS protocols.
Proxy Server Alias Specified?
Default Proxy Server Alias Exists?
Action taken by Integration Server
Yes
NA
If the specified proxy server alias is enabled, Integration Server sends the request using the proxy server in the specified proxy alias. If the send attempt fails, Integration Server does not attempt to make a direct connection to the remote server. Also, Integration Server does not use the proxy server specified in the default proxy alias or any other proxy server to send the request.
If the specified proxy server alias is disabled, the send request fails.
No
Yes
If the default proxy server alias is enabled, Integration Server sends the request using the proxy server in the default proxy server alias. If the send attempt fails, Integration Server either sends the request to the remote server using a direct connection or throws an exception depending on the settings specified for the watt.net.proxy.fallbackToDirectConnection parameter.
If the default proxy server alias is not enabled, Integration Server sends the request using a proxy server for any of the configured proxy server aliases. If the attempt to send a request made using that proxy server fails, Integration Server tries to send using another proxy server alias. Integration Server continues making attempts, using each enabled proxy server alias (in an unspecified order) until the request is sent or all proxy servers have been tried but failed. After all proxy servers fail, Integration Server either sends the request to the remote server using a direct connection or throws an exception depending on the settings specified for the watt.net.proxy.fallbackToDirectConnection parameter.
No
No
Depends on the value specified for the watt.net.proxy.useNonDefaultProxies parameter.
If watt.net.proxy.useNonDefaultProxies parameter is set to true, Integration Server makes outbound requests using each enabled proxy server alias (in an unspecified order) until the request is sent successfully or all proxy servers have been tried but failed. After all proxy servers fail, Integration Server sends the request to the remote server using a direct connection or throws an exception depending on the settings specified for the watt.net.proxy.fallbackToDirectConnection parameter.
If no proxy server aliases exist for the specified protocol, Integration Server sends the request to the remote server using a direct connection or throws an exception depending on the settings specified for the watt.net.proxy.fallbackToDirectConnection parameter.
If the watt.net.proxy.useNonDefaultProxies parameter is set to false, Integration Server does not attempt to make outbound requests using the enabled proxy server aliases. Integration Server sends the request to the remote server using a direct connection.