Performing an App Visibility agent for Java upgrade silently
This topic presents procedures to silently upgrade an App Visibility agent for Java from version 10.0 to the current version. You can upgrade agents using the silent upgrade procedure, as presented in this topic, and deploy the silent upgrade to several computers, or you can upgrade each agent using the interactive mode procedure.
After you upgrade an agent, it runs using the same log files and configuration, and the same agent policy and recording configuration apply.
Upgrade from an earlier version
To upgrade from a version earlier than 10.0, first upgrade to version 10.0
.
Before you begin
Download the following agent upgrade files from the Electronic Product Distribution site to a temporary directory on the agent computer:
- Windows
- adops-agent-upgrade.bat
- agentInstaller.jar
- Linux
- adops-agent-upgrade.sh
- agentInstaller.jar
You must have execute privileges on the upgrade scripts and write access to the upgrade location.
To upgrade an App Visibility agent for Java silently
- Stop the Java virtual machine (JVM) process on the agent computer.
From the directory with the agent installation files, run the following command:
- (Windows) adops-agent-upgrade.bat -s -d <installationDirectory>
- (Linux) ./adops-agent-upgrade.sh -s -d <installationDirectory>
The silent installation uses the following parameters:
- -s parameter specifies to install in silent mode
- -d parameter specifies the upgrade directory. Enter the full path to the existing App Visibility agent installation directory, which must include the ADOPsInstall directory.
See Upgrade command optionsfor additional options.
- Start the JVM process.
Upgrade command options
A silent upgrade requires only the -s (silent) and -d (installation directory) options. Additional options are listed in the following table.
Option | Description |
|---|---|
-h or -help | Prints a help message, listing all the command options |
-s or -silent | Sets the silent mode, so that the utility does not wait for arguments. If an argument is missing, the utility uses the default value. |
-d or -destination <installationDirectory> | Specifies the full path to the existing ADOPsInstall directory to be upgraded. If a directory is not specified, the installation utility uses the directory from which the installation script was invoked. |
-dLogs or -deleteOldLogs | Removes existing log files from the upgraded directory and replaces them with new log files |
-keepOrig or -keepOrigDirCopy | Preserves a copy of the existing ADOPsInstall directory next to the upgraded one, named ADOPsInstall.<origVerName>.<indexNumber>.old.tmp To restore the earlier version of the agent, perform the following procedure:
The agent restarts at the state before the agent upgrade. |
Behavior of the agent and agent policy after upgrade
Upgrading the App Visibility agent does not change the agent policy files. Agent policy files are upgraded with the App Visibility server, and they contain the new features for the agents. The agent for Java continues to use the same agent policy file as before the upgrade.
Where to go from here
If you have a single App Visibility agent installation directory that is used by multiple JVM processes, give the App Visibility agents unique names.
After you update the agent, perform the following procedures:
- Verify that upgrade of the agent for Java is successful and that the agent to sending data.
- Examine and modify, if necessary, the application discovery and event thresholds (SLAs) for automatically discovered applications.
Related topics
Preparing-for-an-App-Visibility-upgrade-and-checking-compatibility