Applying feature packs or fix packs on App Visibility agents for Java
Where you are in the Applying feature packs or fix packs process
|1||Prepare to apply the feature pack or fix pack|
|2||Apply the feature pack or fix pack on the TrueSight Presentation Server|
|3||Apply the feature pack or fix pack on Infrastructure Management|
|4||Apply the feature pack or fix pack on App Visibility Manager — Phase A|
|Apply the feature pack or fix pack on App Visibility Manager — Phase B Task 1 (You are here)|
|Apply the feature pack or fix pack on App Visibility Manager — Phase B Task 2|
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.
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.
- 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.
-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:
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
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.
[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.
Step 4 Phase B Task 2 — Now that you have successfully installed the feature pack or fix pack on the App Visibility agent, you must install it on the Transaction Execution Adapter agent.