The AGENT_HOME variable referenced here is the installation directory of the agent, which contains the apache-tomcat-flexdeploy-https-agent and config folders as well as the start and stop scripts.
Step 1. Stop the Agent
Linux
cd $AGENT_HOME ./StopFlexDeployHttpsAgent.sh
Windows
cd %AGENT_HOME% StopFlexDeployHttpsAgent.bat
Step 2. Download HTTPS Agent software
Download and unzip the latest version of the agent into a temporary location (for example, /u01/software/temp/agent), so it can be accessed during the upgrade process.
The agent software can be downloaded from the Flexagon website and transferred to the endpoint, or can be downloaded directly on the endpoint using wget or curl (provided internet access is available on endpoint).
Do not unzip the distribution directly into the AGENT_HOME directory so we can prevent existing configuration file(s) or folder(s) from being overwritten.
Linux
AGENT_TEMP=/u01/software/temp/agent (you may change this to any directory, but don't use AGENT_HOME or anything inside AGENT_HOME)
mkdir -p ${AGENT_TEMP}
cd ${AGENT_TEMP}
# DOWNLOAD either using wget or curl or transfer here manually
wget -O HttpsAgentTomcatComplete.zip https://flexagon.com/downloads/httpsagent
# OR
curl -L --max-redirs 5 https://flexagon.com/downloads/httpsagent --output HttpsAgentTomcatComplete.zip
unzip HttpsAgentTomcatComplete.zip
Windows
set AGENT_TEMP=c:\u01\software\temp\agent mkdir %AGENT_TEMP% (you may change this to any directory, but don't use AGENT_HOME) cd %AGENT_TEMP% # Download https://flexagon.com/downloads/httpsagent in AGENT_TEMP folder unzip HttpsAgentTomcatComplete.zip
Step 3. Backup Current Installation
Backup the current apache-tomcat-flexdeploy-https-agent folder. This will be used to reference the existing configuration.
This step is required. Otherwise the existing configuration will be lost later on.
Linux
cd $AGENT_HOME mv apache-tomcat-flexdeploy-https-agent apache-tomcat-flexdeploy-https-agent-old
Windows
cd %AGENT_HOME% rename apache-tomcat-flexdeploy-https-agent apache-tomcat-flexdeploy-https-agent-old
Step 4. Apply new version
Copy the apache-tomcat-flexdeploy-https-agent folder from the download.
Linux
cd $AGENT_HOME
cp -r ${AGENT_TEMP}/apache-tomcat-flexdeploy-https-agent .
Windows
cd %AGENT_HOME% mkdir apache-tomcat-flexdeploy-https-agent xcopy %AGENT_TEMP%\apache-tomcat-flexdeploy-https-agent apache-tomcat-flexdeploy-https-agent /s
Step 5. Apply old configuration
Apply the old configuration from the backup.
Linux
cd $AGENT_HOME cp apache-tomcat-flexdeploy-https-agent-old/conf/server.xml apache-tomcat-flexdeploy-https-agent/conf/server.xml cp apache-tomcat-flexdeploy-https-agent-old/conf/tomcat-users.xml apache-tomcat-flexdeploy-https-agent/conf/tomcat-users.xml
Windows
cd %AGENT_HOME% copy apache-tomcat-flexdeploy-https-agent-old/conf/server.xml apache-tomcat-flexdeploy-https-agent/conf/server.xml copy apache-tomcat-flexdeploy-https-agent-old/conf/tomcat-users.xml apache-tomcat-flexdeploy-https-agent/conf/tomcat-users.xml
You may remove the apache-tomcat-flexdeploy-agent-old directory after testing the connection in step 7.
Step 6. Start Agent
Linux
cd $AGENT_HOME ./StartFlexDeployHttpsAgent.sh
Windows
cd %AGENT_HOME% StartFlexDeployHttpsAgent.bat
Step 7. Perform Test Connection of Endpoint
Visit this page for details on testing connectivity from FlexDeploy to the Agent endpoint.