Applying feature packs or fix pack to App Visibility agents for Java

This topic presents procedures to apply feature packs or fix packs to an App Visibility agent for Java version 10.7. You can apply the feature pack or fix pack to each agent using the interactive mode or the silent procedure.

After you apply the feature pack or fix pack to 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:

Performing an App Visibility agent for .NET upgrade

Before you begin

Download the following 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 scripts and write access to the location.

To apply the feature pack or fix pack to an App Visibility agent for Java

Stop the Java virtual machine (JVM) process on the agent computer.
Open a command shell and run the adops-agent-upgrade.bat (for Windows) or adops-agent-upgrade.sh (for Linux) command.
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
To start the upgrade, enter yes.
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.

To apply the feature pack or fix pack to an App Visibility 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 feature pack or fix pack directory. Enter the full path to the existing App Visibility agent installation directory, which must include the ADOPsInstall directory.
Example
(Windows) adops-agent-upgrade.bat -s -d "c:\BMC Software\ADOPs\ADOPsInstall"
(Linux) ./adops-agent-upgrade.sh -s -d /opt/ADOPs/ADOPsInstall
See Silent command options (below) for additional options.
Start the JVM process.

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

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 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: Stop the JVM process on the agent computer. Move or rename the ADOPsInstall directory with the feature pack or fix pack. Rename the backed up directory to ADOPsInstall. Restart the JVM process. The agent restarts at the state before the feature pack or fix pack was applied.

Verifying the App Visibility agent for Java after applying the feature pack or fix pack

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.

To review the logs

Open the bmc_ad_agent_install.log file, which is usually located in the same folder from which you ran the upgrade script.
Examine the log for error messages, such as messages that indicate incorrect privileges or write access.
- Ensure that you have execute privileges on the upgrade scripts and write access to the upgrade location.
- Ensure that other applications or processes are not holding files open.

To verify that the Agent for Java has been invoked

Access the log files folder in the local installation directory, for example: C:\AppVis\ADOPsInstall\instances\<instance_name>\logs
The <instance_name> variable is the name that is generated dynamically during the Agent first start-up.
Examine the aps_agent.log file.
If the log file exists, the installation was successful.
Examine [ERROR] messages for issues that you can address.
In the TrueSight console, select Administration > App Visibility Agents from the navigation pane and confirm that the agent is online.

Behavior of the agent and agent policy after applying the feature pack or fix pack

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.

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:

If you applied the feature pack or fix pack to your App Visibility server, and you enabled high availability in the updated 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 .

Page tree