Page History
...
- Consider instructions from JS7 - Agent Installation On Premises.
- Take a backup of the Agent's installation directory.
- Suspend orders related to the Agent in question.
- Stop the Agent
- Standalone Agent
- Stop the Agent instance's daemon (Linux) or service (Windows). This can be performed using the Agent's installation scripts.
- Cluster Agent
- Take a note which Director Agent instance is the active node before stopping Agent instances.
- Stop the Primary and Secondary Director Agent instance's daemon (Linux) or service (Windows).
- Standalone Agent
- Option 1: Automated Upgrade
- Run the Agent Installation Script for Upgrade
- For an Agent Cluster run the Agent Installation Script for the active and then for the standby Director Agent instance.
- Option 2: Manual Upgrade
- Extract the installer archive .tar.gz/.zip file from a neutral directory not related to the current Agent installation. This will create a sub-directory that includes the maintenance release number, for example
agent.2.2.2
. - From the existing Agent installation directory move or remove the
lib
directory. - Copy the
lib
andbin
sub-directories from the extracted installer archive to the Agent's installation directory. This will replace the previouslib
sub-directory and will overwrite the existingbin
sub-directory from the new release. The Agent's instance start script that can contain individual settings is not included with the installer archive and therefore will not be overwritten, see JS7 - Agent Command Line Operation. - For an Agent Cluster consider performing this step for all Agent instances in the cluster.
- Extract the installer archive .tar.gz/.zip file from a neutral directory not related to the current Agent installation. This will create a sub-directory that includes the maintenance release number, for example
- Start the Agent.
- Resume orders for the related Agent.
...
Overview
Content Tools