Currently MSA and appliances do not have proxy settings available for configuring through UI / deploy options.
Also all stateless appliances cannot use permanent proxy settings.
However, if MSA needs to reach out to MMS through proxy, the following workaround can be performed:
in JetDR 4.x MSA edit 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.0.0.1|<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
...
added line 7 and reference to CATALINA_OPTS_PROXY on line 9.
After the change, vme2 service must be restarted for the options to be applied.
in JetDR 5.0 and later MSA, similar change should be done in file /etc/tomcat/conf.d/fio.conf, and msa-tomcat service restarted.
The issue to track more user-friendly proxy setting process is DRBC-7794 - Getting issue details... STATUS