Performing the agent for Java upgrade

This topic presents upgrade procedures for the BMC Application Diagnostics Agent for Java from version 2.0 to 2.1 or 2.1.01, or from 2.1 to 2.1.01. You can upgrade each agent using the interactive mode, or you can upgrade the agent using the silent upgrade procedure, and deploy the silent upgrade to several computers.

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

1. Stop the Java virtual machine (JVM) process on the agent computer.
2. Open a command shell and run the adops-agent-upgrade.bat (for Windows) or adops-agent-upgrade.sh (for Linux) command.

3. At the prompt, 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.

   Information

   Example

   (Windows) "c:\BMC Software\ADOPs\ADOPsInstall"

   (Linux) /opt/ADOPs/ADOPsInstall

4. To start the upgrade, enter yes.
5. When the message BMC Application Diagnostics Java Agent upgraded successfully is displayed, the upgrade is successful and you can close the command shell. Otherwise, see Verifying-the-agent-for-Java-upgrade.
6. Restart the JVM process.

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:

• If the agent uses an out-of-the-box policy, the new features are available.
• If the agent uses a customized policy, then the policy does not contain the new features. To access the features, you can manually update the policy, or assign an updated policy to the agent.

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.

Related topics

Preparing-for-upgrade-and-compatibility
Performing-the-agent-for-NET-upgrade