heterogeneous arguments for CA API Gateway (ssg) process

Products

• STARTER PACK-7
• CA Rapid App Security
• CA API Gateway

Issue/Introduction

In production configuration, we have two CA API Gateway clusters.

The first one is running on two Linux VMs : s00vl9972110 and s00vl9972139, the second one on two others VMs : s00vl9972131 and s00vl9972152.
When configuring the process monitoring we found that the process arguments for ssg are the same on 3 VMs (s00vl9972110, s00vl9972139 and s00vl9972131) : 

gateway 6733 1 1 Apr08 ? 01:09:36 /apps/JRE8/jdk1.8.0_102/jre/bin/java -Djava.util.logging.config.class=com.l7tech.server.log.JdkLogConfig -Dcom.l7tech.server.home=/opt/SecureSpan/Gateway/node/default -Djava.ext.dirs=/apps/JRE8/jdk1.8.0_102/jre/lib/ext:/opt/SecureSpan/Gateway/runtime/lib/ext -Dcom.l7tech.server.siteminder.enabled=true -server -Djava.net.preferIPv4Stack=true -Djava.security.policy=/opt/SecureSpan/Gateway/runtime/etc/ssg.policy -Djava.security.egd=file:/dev/./urandom -Dfile.encoding=UTF-8 -Dsun.net.inetaddr.ttl=30 -Djava.awt.headless=true -XX:CompileThreshold=1500 -Dcom.l7tech.server.defaultClusterHostname=s00vl9972110 -Djava.util.Arrays.useLegacyMergeSort=true -Xmx2048m -XX:MaxPermSize=256M -jar /opt/SecureSpan/Gateway/runtime/Gateway.jar start 

On the fourth vm (s00vl9972152) the process arguments differ : 
gateway 7301 7224 1 Apr09 ? 00:29:26 /apps/JRE8/jdk1.8.0_102/jre/bin/java -Dcom.l7tech.server.home=/opt/SecureSpan/Gateway/node/default -Djava.ext.dirs=/apps/JRE8/jdk1.8.0_102/jre/lib/ext:/opt/SecureSpan/Gateway/runtime/lib/ext -Dcom.l7tech.server.siteminder.enabled=true -server -Djava.net.preferIPv4Stack=true -Djava.security.policy=/opt/SecureSpan/Gateway/runtime/etc/ssg.policy -Djava.security.egd=file:/dev/./urandom -Dfile.encoding=UTF-8 -Dsun.net.inetaddr.ttl=30 -Djava.awt.headless=true -XX:CompileThreshold=1500 -Dcom.l7tech.server.defaultClusterHostname=s00vl9972152 -Djava.util.Arrays.useLegacyMergeSort=true -Xmx2048m -XX:MaxPermSize=256M -Dcom.l7tech.server.home=/opt/SecureSpan/Gateway/node/default -Dcom.l7tech.server.processControllerPresent=true -Dcom.l7tech.server.processControllerCert=/opt/SecureSpan/Controller/var/run/pc.cer -Dcom.l7tech.server.processControllerIpAddress=127.0.0.1 -Dcom.l7tech.server.processControllerPort=8765 -Djava.util.logging.config.class=com.l7tech.server.log.JdkLogConfig -Dcom.l7tech.server.log.console=true -jar /opt/SecureSpan/Gateway/runtime/Gateway.jar pc run 

It ends with "pc run" instead of "start" and there are several additional properties (-Dcom.l7tech.server.processControllerIpAddress=127.0.0.1 for example). We would like to know it we have a configuration problem.

Environment

Env : Gateway 9.3

Resolution

These arguments (starr /pc run) gives information about how the GW process has started.
If it is started through process control (like by rebooting the appliance or by issuing a service restart command through the appliance configuration menu),
then we see "pc run" arguments. 

If we use the privileged shell to start the GW using gateway.sh start option, it shows you "start" argument.