Upgrading an App Visibility agent using the wizard
Where you are in the Upgrade process
As a system administrator, you can upgrade both Java and .NET agents using the installation wizard, 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.
Failed to execute the [excerpt-include] macro.
To upgrade a TrueSight App Visibility Manager agent for Java using the wizard
- Log in to the computer with the user that runs the application server.
- Failed to execute the [excerpt-include] macro.
- Failed to execute the [excerpt-include] macro.
- Stop the application server or Java virtual machine (JVM) process on the agent computer.
- Failed to execute the [excerpt-include] macro.
- Failed to execute the [excerpt-include] macro.
- Failed to execute the [excerpt-include] macro.
Enter, or browse to, the TrueSight App Visibility Manager agent for Java installation directory and click Next.
The default directory is:
- (Windows) C:\Program Files (x86)\BMC Software\App Visibility\Agent_for_Java
- (Linux, AIX, Solaris) /opt/bmc/App_Visibility/Agent_for_Java
- Review the settings displayed on the Installation Preview page and click Install.
Start the application server or JVM process.
If you upgraded your TrueSight App Visibility Manager server, and you enabled HA 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.
After you upgrade an agent, it runs using the same log files and configuration, and the same agent policy and recording configuration apply.
To upgrade a TrueSight App Visibility Manager agent for .NET using the wizard
- Failed to execute the [excerpt-include] macro.
- Failed to execute the [excerpt-include] macro.
- To launch the wizard, double-click setup.exe.
When you run the setup.exe installation wizard on a system with a previous version of the product, the wizard automatically switches to upgrade mode. - Failed to execute the [excerpt-include] macro.
- Failed to execute the [excerpt-include] macro.
- To confirm that you want to upgrade, click Install.
The utility upgrades the current version with the same values as the earlier installation. - If required services are running, such as IIS, click Next to confirm that the services will be stopped.
Services are restarted at the end of the upgrade process. - Failed to execute the [excerpt-include] macro.
- Failed to execute the [excerpt-include] macro.
- If you enabled HA for the App Visibility portal for the first time, upgrade each App Visibility agent, update the agent's portal connection details to the portal's load balancer. For details, see Changing settings of the App Visibility agent for .NET.
Behavior of the agent and agent policy after upgrade
Upgrading the TrueSight App Visibility Manager agent does not change the agent policy files. Agent policy files are upgraded with the TrueSight App Visibility Manager server, and they contain the new features for the agents. The agent for Java and .NET continues to use the same agent policy files as before the upgrade.
Verifying the TrueSight App Visibility Manager agent for Java upgrade
You can verify that the App Visibility agent for Java upgrade was successful, and that the agent for Java was invoked, by reviewing the log files created and updated during the agent upgrade. For assistance with any issues that you cannot solve, contact BMC Customer Support.
To review the logs
- Navigate to the same folder from where you ran the upgrade script and check for the bmc_ad_agent_install.log file.
Ensure that other applications or processes are not holding files open.
- Open and examine the log for error messages, such as that indicate incorrect privileges or write access.
To verify that the Agent for Java has been invoked
Navigate to the logs folder in the local installation directory. For example, C:\AppVis\ADOPsInstall\instances\<instance_name>\logs
Note: The <instance_name> variable is the name that is generated dynamically during the Agent first start-up.
- Check for the aps_agent.log file.
If the log file exists, the installation was successful. - Open the aps_agent.log file and 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.
Verifying the TrueSight App Visibility Manager agent for .NET upgrade
You can verify that the App Visibility agent for .NET upgrade was successful, and that the agent for .NET was invoked, by reviewing the log files created and updated during upgrade. For assistance with issues that you cannot solve, contact BMC Customer Support.
To review the installation logs
- Open the agentinstaller_install_log.txt file, located in the %temp% folder.
- In the log, verify whether any error messages were reported. If there are no error messages, the upgrade was successful.
In the TrueSight console, select Administration > App Visibility Agents from the navigation pane and confirm that the agent is online. For more information, see Accessing and navigating the TrueSight console.
- Add App Visibility to the TrueSight console, if you haven't already done so.
Next Step in the Upgrade process
Step 5 Phase B Task 2 — Now that you have successfully installed the App Visibility agent, you must upgrade the Transaction Execution Adapter agent.