Page tree

Skip to end of metadata
Go to start of metadata

This topic presents procedures to upgrade an App Visibility agent for Java from version 10.1, or later, to the current version. You can upgrade each agent using the interactive mode, as presented in this topic, or you can upgrade the agent using the silent upgrade procedure.

After you upgrade an agent, it runs using the same log files and configuration, and the same agent policy and recording configuration apply.

This topic contains the following sections:

Upgrade from an earlier version
To upgrade from a version earlier than 10.1, first upgrade to version 10.1 .

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

  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 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.

    Examples

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

    (Linux) /opt/ADOPs/ADOPsInstall

  4. To start the upgrade, enter yes.

  5. When the message App Visibility Agent for Java upgraded successfully is displayed, the upgrade is successful and you can close the command shell. Otherwise, see Verifying the App Visibility agent for Java upgrade.

  6. Start the JVM process.

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.
  • If you upgraded your App Visibility server, and you enabled high availability in the upgraded version, ensure that you change the settings of the App Visibility agent to connect to the portal's load balancing server.
  • 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

Performing an App Visibility agent for .NET upgrade