The FlexDeploy HTTPS agent is an alternative way of connecting to an endpoint. It connects over HTTPS, thus not requiring SSH to be exposed. This may be the preferred approach for Zero Trust Architectures.
Support for the HTTPS Agent was released with FlexDeploy 6.5.0.3
Starting and stopping the agent
The scripts located inside the agent installation directory are used for starting and stopping the agent.
Start
Linux
cd $AGENT_HOME ./StartFlexDeployHttpsAgent.sh
Windows
cd %AGENT_HOME% StartFlexDeployHttpsAgent.bat
Stop
Linux
cd $AGENT_HOME ./StopFlexDeployHttpsAgent.sh
Windows
cd %AGENT_HOME% StopFlexDeployHttpsAgent.bat
Troubleshooting
Run the following command to confirm if the agent is running, as well as see launch arguments.
ps -ef | grep java.*https.agent
Logs
Viewing Logs
View the logs by going to AGENT_HOME/apache-tomcat-flexdeploy-https-agent/logs
Agent logs will be in the same pattern as FlexDeploy logs, flexdeploy.<number>.log with 0 being the most current log.
Catalina logs as well as garbage collection logs will also be located here.
Changing log level
To change the log level adjust the AGENT_HOME/apache-tomcat-flexdeploy-https-agent/conf/logging.properties file. Change the following lines to the desired log level.
# FlexDeploy levels .level=INFO # change this one for every other logger then the agents flexagon.level=INFO # change this one and the next one for just agent logging directly com.flexagon.level=INFO
Then restart the agent for it to take effect.