You can route PostgreSQL connections through a proxy server that you configure on the Secure Agent. You can also bypass the proxy for specific hosts and manage proxy precedence with JVM options.
An administrator turns on proxy routing for PostgreSQL connections by setting a custom property on the Secure Agent. By default, the connector doesn't route connections through the proxy.
To enable the proxy for PostgreSQL connections, complete the following steps:
1Log in to Informatica®Intelligent Data Management Cloud™ (IDMC).
2Open Administrator > Runtime Environments.
3Click the name of the Secure Agent.
4Click the Details tab.
5Click Edit.
6In the Custom Configuration Details area, click Add to add a property row.
7Select Data Integration Server as the service.
8Select Tomcat JRE as the configuration property type.
9Enter EnablePostgresProxy as the property name and true as the value.
10Click Save.
The connector compares the connection host name with the entries in the NonProxyHost property of the proxy.ini file. The comparison matches the host name exactly but treats uppercase and lowercase letters as equivalent. A host name and its IP address don't match each other. If the connection host matches a NonProxyHost entry, the connector bypasses the proxy for that connection.
For instructions, see "Configure the proxy settings on Windows" or "Configure the proxy settings on Linux" in Getting Started in the Data Integration help.
If you configure a proxy for the Data Integration Server through JVM options, those settings take precedence over the proxy.ini file. Add the PostgreSQL database host to the JVM option for non-proxy hosts at the Data Integration Server level.