Show TOC

Checking Proxy SettingsLocate this document in the navigation structure

Use

If an application is unable to communicate with TREX, it may be due to the application trying to access TREX using a proxy server. If this is the case, you have to change the configuration so that access does not take place using the proxy server.

The procedure depends on the application concerned:

  • SAP Enterprise Portal 6.0 with Content Management
  • Other Java applications based on J2EE 6.40

Procedure

SAP Enterprise Portal 6.0 with Content Management

Check the settings in the portal at System Administration → System Configuration → Service Configuration → Applications (Content Catalog) → com.sap.portal.ivs.httpservice → Services → proxy.

If a proxy server is entered there, you have to enter the TREX host in the field http - Bypass Proxy Servers.

Other Java applications based on J2EE 6.40

For other Java applications, you have to check the configuration of the J2EE Engine. The proxy settings belong to the Java parameters. If a proxy server is configured in the Java parameters, enter the TREX host in the parameter nonProxyHosts. You can choose one of the following options:

  • Alternative 1: D"http.nonProxyHosts=<hostname>.<mydomain>|localhost

    For <hostname>.<domain>, enter the host name and domain (if necessary) of the TREX host.

  • Alternative 2: D"http.nonProxyHosts=*.<mydomain>|localhost

You can change the Java parameters using the SAP J2EE Engine GUI Config Tool. For more information about using this tool, see the SAP Library at the Internet address help.sap.com → Documentation → SAP NetWeaver

Caution

Note that you have to specify the name of the TREX host in the same way both on TREX side in the TREX configuration files (topology.ini, sapprofile.ini) and in the configuration of the J2EE Engine as described above. In case you specify the TREX host name as fully qualified (e.g. PWDF12345.sap.corp) you have to do so on both sides. A mixed usage of host names does not work.