Updating JVM Configuration Settings for Proxies
Depending on your networking and security requirements, you may need to set Java system properties related to proxy servers. Because the connection between the on-premise Integration Server and IBM webMethods Cloud is over HTTPS, you need to set some or all of the following:
https.proxyHost https:proxyPort http:nonProxyHosts https.proxyUser https.proxyPassword Because the proxy property values need to be set for the Java Virtual Machine (JVM) in which Integration Server runs, you update the custom_wrapper.conf to ensure the proxy parameter values are supplied when the JVM launches. Specifically, you add a wrapper.java.additional. n property that specifies the property name and value that you want to pass to Integration Server, where n is a unique sequence number. The property name must be preceded by -D.
For example, the wrapper.java.additional properties in the custom_wrapper.conf file might look similar to the following:
wrapper.java.additional.204=-Dhttps.proxyHost=YOUR_PROXY_HOST
wrapper.java.additional.205=-Dhttps.proxyPort=YOUR_PROXY_PORT
wrapper.java.additional.206=-Dhttps.proxyUser=YOUR_PROXY_USER
wrapper.java.additional.207=-Dhttps.proxyPassword=YOUR_PROXY_PASSWORD
wrapper.java.additional.208=-Dhttp.nonProxyHosts=localhost|127.0.0.1
wrapper.java.additional.209=-DHPROXY=YOUR_PROXY_HOST:YOUR_PROXY_PORT
wrapper.java.additional.210=-DHAUTH=YOUR_PROXY_USER:YOUR_PROXY_PASSWORD
For instructions about passing Java system properties to Integration Server and the JVM used by Integration Server, see the IBM webMethods Integration Server Administrator’s Guide.
To pass system properties to
Microservices Runtime, you must update the JAVA_CUSTOM_OPTS property in
Integration Server_directory/bin/server.bat(sh). For more information about passing system properties to
Microservices Runtime, see
Developing Microservices with IBM webMethods Microservices Runtime
Passing Java System Properties to Microservices Runtime
.
Note:
If Integration Server uses Java SE Development Kit 8, Update 111 or later and the Internet proxy is configured to enforce HTTPS Basic authentication, you may need to add the following system properties to the custom_wrapper.conf:
jdk.http.auth.proxying.disabledSchemes
jdk.http.auth.tunneling.disabledSchemes