This topic presents procedures to silently upgrade an App Visibility agent for Java from version 10.1, or later, 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.

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 silently

  1. Stop the Java virtual machine (JVM) process on the agent computer.
  2. 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.

OptionDescription

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

  1. Stop the JVM process on the agent computer.
  2. Move or rename the upgraded ADOPsInstall directory.
  3. Rename the backed up directory to ADOPsInstall.
  4. Restart the JVM process.

The agent restarts at the state before the agent upgrade.

Example

adops-agent-upgrade -help -silent -destination /opt/ADOPs/ADOPsInstall -deleteOldLogs -keepOrigDirCopy

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

Was this page helpful? Yes No Submitting... Thank you
© Copyright 2013-2017 BMC Software, Inc.
© Copyright 2013-2017 BladeLogic, Inc.
Legal notices