When Integration Server sends a request to a remote server, Integration Server routes
Configuring the Server
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.
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 aempt fails, Integration Server does not aempt 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 aempt fails, Integration Server either sends the request to the remote server using a direct connection or throws an exception depending on the seings specified for the wa.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 aempt to send a request made using that proxy server fails, Integration Server tries to send using another proxy server alias. Integration Server continues making aempts, 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
Configuring the Server
Action taken by Integration Server
wa.net.proxy.fallbackToDirectConnection parameter.
No No Depends on the value specified for the
wa.net.proxy.useNonDefaultProxies parameter.
If wa.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 seings specified for the wa.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 seings specified for the wa.net.proxy.fallbackToDirectConnection parameter.
If the
wa.server.proxy.useNonDefaultProxies parameter is set to false, Integration Server does not aempt to make outbound requests using the enabled proxy server aliases.
Integration Server sends the request to the remote server using a direct connection.
Configuring the Server
To create a proxy server alias
1. Open the Integration Server Administrator if it is not already open.
2. In the Settings menu of the Navigation panel, click Proxy Servers.
3. Click Create Proxy Server Alias.
4. Under Proxy Server Alias Properties, provide information in the following fields:
For this parameter... Specify...
Alias The alias name to use for this host/port combination.
Host Name or IP
Address The host name or IP address of the proxy server.
Port Number The port on which this proxy server listens for requests.
User Name (optional) The user name Integration Server must use when accessing this proxy server.
Password (optional) The password Integration Server must use to access this proxy server.
Protocol The type of protocol (HTTP, HTTPS, FTP, or SOCKS) to use for the host/port combination.
Proxy Type If you select FTP, additional parameters appear to help you configure the Proxy Type. For requests that the proxy server will be forwarding to an FTP server, you must specify the following information:
The name of the FTP server
The name of a user on the FTP server The password for that user.
The method you use to send this information to the FTP proxy server depends on the type of proxy server you have. Integration Server supports the following proxy server types:
0. No proxy
Do not use an FTP proxy server. This is the default.
1. ftp_user@ftp_host no proxy auth
Configuring the Server
For this parameter... Specify...
Connect to the proxy server, but do not log into it. Then send the following:
USER ftp_user@ftp_host PASS ftp_password
2. ftp_user@ftp_host proxy auth
Connect to the proxy server, and log into it with:
USER proxy_user PASS proxy_password
Then send the following:
USER ftp_user@ftp_host PASS ftp_password
3. site command
Connect to the proxy server, and log into it with:
USER proxy_user PASS proxy_password
Then send the following:
SITE ftp_host USER ftp_user PASS ftp_password
4. open command
Connect to the proxy server, and log into it with:
USER proxy_user PASS proxy_password
Then send the following:
OPEN ftp_host USER ftp_user PASS ftp _password
5. ftp_user@proxy_user@ftp_host
Connect to the proxy server and log into it. Then send
Configuring the Server
For this parameter... Specify...
PASS ftp_password
7. ftp_user@ftp_host proxy_user
Connect to the proxy server, but do not log into it. Then send the following:
USER ftp_user@ftp_host proxy_user PASS ftp_password
ACCT proxy_password
SOCKS Version If you select SOCKS as the protocol, additional parameters appear to help you configure the SOCKS version. Select SOCKS v4or SOCKS v5 based on what version of SOCKS protocol you would like to use to connect to the proxy server.
Note: SOCKS protocol version 4 does not support authentication. Do not specify authentication credentials (i.e. username and password) if you select SOCKS protocol version 4.
Default Whether this proxy server alias should be the default proxy server alias for its protocol type or not. Click Yes or No. Only one default proxy server alias can be set for each protocol type.
5. Click Save Changes.