Performing the Diagnostics Agent for Java upgrade silently

This topic presents procedures for the silent upgrade of the BMC Application Diagnostics Agent for Java from version 2.1.x, or later, to 2.6.x. You can upgrade Agents using the silent upgrade procedure 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.

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 the BMC Application Diagnostics 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 BMC Application Diagnostics 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.
- -skipver parameter skips the version check and update the agent regardless
Information
(Windows) adops-agent-upgrade.bat -s -d "c:\BMC Software\ADOPs\ADOPsInstall" -skipver
(Linux) adops-agent-upgrade.sh -s -d /opt/ADOPs/ADOPsInstall -skipver
If you are upgrading from version 2.1.x or earlier, the -a <app_display_name> is also required.
See Upgrade command optionsfor additional options.
Restart the JVM process.

Upgrade command options

A silent upgrade requires only the -s (silent) and -d (installation directory) options. Available 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 If you use this option, you can restore the earlier version of the Agent.
-a or -application <app_display_name>	Specifies a name for the application to be displayed in the BMC Application Management Console. The application name is case insensitive. If you are upgrading from version 2.1.x or earlier, this option is required. If you are upgrading from version 2.5 or later, the existing value is used by default.
-ti or -tier <tier_type>	Specifies the type of tier this Agent represents in the Application View: app, business, web. The default value is app.
-skipver	Skips the version check and update the agent regardless

Example

adops-agent-upgrade -help -silent -destination /opt/ADOPs/ADOPsInstall -skipver -deleteOldLogs
-deleteOldWorkDir -keepOrigDirCopy -application myApplication -tier app

To restore the earlier version of the Agent

You can restore the earlier version of the Agent if you used the -keepOrigDirCopy (or -keepOrig) option in the silent upgrade command.

Stop the JVM process on the Agent computer.
Move or rename the upgraded ADOPsInstall directory.
Rename the backed up directory to ADOPsInstall.
Restart the JVM process.

The Agent restarts at the state before the Agent upgrade.

Behavior of Agent and Agent policy after upgrade

Upgrading BMC Application Diagnostics Agent for Java does not change the Agent policy files. Agent policy files are upgraded with BMC Application Diagnostics Server and contain the new features for the Agents. The Agent for Java continues to use the same Agent policy file as before the upgrade.

Note

After you upgrade the Diagnostics Agent, values for warning and critical thresholds are managed through the Console. For information, see Configuring-SLA-rules-for-business-transactions and Configuring-SLA-rules-for-application-servers.

Some event and metric thresholds, such as database events and JMX rules, are managed through the Agent policy. For information, see Modifying-an-Agent-policy-file.

Where to go from here

Verify that upgrade of the BMC Application Diagnostics Agent for Java is successful and that the Agent to sending data.