The FlexDeploy HTTPS agent is an alternative way of connecting to an endpoint. Typically endpoints are connected via SSH. The HTTPS Agent connects over HTTPS. This means you do not need to expose SSH on your endpoint.childrenIt 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
| Child pages (Children Display) |
|---|
Starting and stopping the agent
The scripts located inside the agent installation directory are used for starting and stopping the agent.
Start
Linux
| Code Block |
|---|
cd $HTTPS_AGENT_HOME
./StartFlexDeployHttpsAgent.sh |
Windows
| Code Block |
|---|
cd %HTTPS_AGENT_HOME%
StartFlexDeployHttpsAgent.bat |
Stop
Linux
| Code Block |
|---|
cd $HTTPS_AGENT_HOME
./StopFlexDeployHttpsAgent.sh |
Windows
| Code Block |
|---|
cd %HTTPS_AGENT_HOME%
StopFlexDeployHttpsAgent.bat |
Troubleshooting
Run the following command to confirm if the agent is running, as well as see launch arguments.
| Code Block |
|---|
ps -ef | grep java.*https.agent |
Logs
Viewing Logs
View the logs by going to HTTPS_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 HTTPS_AGENT_HOME/apache-tomcat-flexdeploy-https-agent/conf/logging.properties file. Change the following lines to the desired log level.
| Code Block | ||
|---|---|---|
| ||
# 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.