Download the following files from the Electronic Product Distribution site to a temporary directory on the agent computer:
You must have execute privileges on the scripts and write access to the location.
At the prompt, enter the full path to the existing App Visibility agent installation directory, which must include the ADOPsInstall directory. You can also use a relative path.
If the path includes a space, enclose the path in quotation marks.
To start the upgrade, enter
When the message
App Visibility Agent for Java upgraded successfully is displayed, the feature pack or fix pack is successful and you can close the command shell. Otherwise, see Verifying the App Visibility agent for Java upgrade.
Start the JVM process.
From the directory with the agent installation files, run the following command:
adops-agent-upgrade.bat -s -d <installationDirectory>
./adops-agent-upgrade.sh -s -d <installationDirectory>
The silent installation uses the following parameters:
See Silent command options (below) for additional options.
Applying the feature pack or fix pack silently requires only the -s (silent) and -d (installation directory) options. Additional options are listed in the following table.
-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 have the feature pack or fix pack applied.
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 feature pack or fix pack directory and replaces them with new log files
-keepOrig or -keepOrigDirCopy
Preserves a copy of the existing ADOPsInstall directory next to the directory with the feature pack or fix pack, 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 feature pack or fix pack was applied.
You can verify that applying the feature pack or fix pack to the App Visibility agent for Java was successful, and that the agent for Java was invoked, by reviewing the log files created and updated during the process. For assistance with any issues that you cannot solve, contact Customer Support.
[ERROR]messages for issues that you can address.
Applying the feature pack or fix pack to the App Visibility agent does not change the agent policy files. Agent policy files are changed 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 you applied the feature pack or fix pack.
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: