Configuring a Management Server Appliance (MSA) Proxy
- vlad.bespalov
- Anthony Lai
This article applies to all JSDR software versions.
Issue
Currently, proxy setting configuration is not available for the MSA and appliances through UI/deployment options. Furthermore, all stateless appliances cannot be configured to use permanent proxy settings.
If the MSA needs to connect to the MMS subscription server through proxy, the following workaround can be performed:
Solution
JetDR MSA Version 4.x
Edit the file
/etc/init.d/vme2.
...
CATALINA_OPTS_MEM="-server -Xms3g -Xmx3g"
current_date=`date +%s`
CATALINA_OPTS_DUMP="-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath='/tmp/jetdr-${current_date}.hprof'"
CATALINA_OPTS_EXTRA="-Djava.awt.headless=true -Djava.security.egd=file:///dev/urandom -Djavax.xml.bind.context.factory=com.sun.xml.internal.bind.v2.ContextFactory"
CATALINA_OPTS_PROXY='-Dhttps.proxyHost=<proxy ip/fqdn> -Dhttps.proxyPort=<proxy port> -Dhttp.nonProxyHosts="localhost|127.*|<local subnet(s)>"'
[ -z "$CATALINA_OPTS" ] && CATALINA_OPTS="$CATALINA_OPTS_MEM $CATALINA_OPTS_DUMP $CATALINA_OPTS_EXTRA $CATALINA_OPTS_PROXY"
export JRE_HOME CATALINA_OPTS
...For example, line 7 was added and references
CATALINA_OPTS_PROXYon line 9.Local subnets have to be mentioned in wildcard format (e.g. 10.* or *.jetstreamsoft.com
ref.: https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html)
After the change, the vme2 service must be restarted for the options to be applied.
JetDR MSA Version 5.0 and later
In JetDR 5.0 and later MSAs, changes similar to those described above should be performed in the file
/etc/tomcat/conf.d/fio.conf.After changes have been made the msa-tomcat service must be restarted.