Running Integration Gateways Behind Proxy Servers
When a proxy server is set up for a network on which the integration gateway resides, all HTTP transactions are routed through that proxy server automatically. The HTTP transport layer uses proxy server settings that you specify in the integrationGateway.properties file. The message is routed to the proxy server and then on to the internet. Only the HTTP target connector can use a proxy server.
Inserted in the HTTP message header of each transaction is a Proxy-Authorization header field containing a user ID and password. The proxy server uses these values to authenticate the message and then passes it on to its target.
PeopleSoft also enables you to exclude user-defined hosts from connecting through a proxy server.
Setting Proxy Web Server Properties
To run the integration gateway behind a proxy server:
-
Set the gateway-level properties.
Uncomment and add values for the properties in the integrationGateway.properties file section labeled Proxy webserver section.
Property Description ig.proxyHost
Enter the domain name of the proxy web server; for example:
proxy.example.comig.proxyPort
Enter the port number of the proxy web server; for example:
80ig.nonProxyHost
Enter a list of hosts that should be accessed directly, instead of through the proxy server. The values can be a list of hosts, each separated by a |, and in addition a wildcard character (*) can be used for matching. For example: For example:
ig.nonProxyHosts=*.google.com|finance.yahoo.comThe HTTP target connector reads these two properties and calls the setProxy function. In an outbound transaction, the request is redirected to the proxy server and the proxy server forwards the request to the destination URL.
-
Set the node-level property.
You set the user ID and password required by the proxy server in the HEADER, Proxy-Authorization connector property. The integration gateway encodes the values that you provide, adds the required formatting, and sends it. The format is:
userid:password
Related Topics