This topic presents instructions to prepare the App Visibility Manager environment for an upgrade, and describes compatibility consideration for the upgrade.
Make a physical backup of the App Visibility PostgreSQL database to protect your data from loss. The output of a physical backup contains the data files that the App Visibility server can use directly, resulting in a faster recovery operation.
The script creates a backup of the data in the avdb.dump file in the server component's installationDirectory\ADOP_DB\pgsql\backup directory.
For more information about making PostgreSQL database backup files, see .
If you have issues with your database, you can recover the backed-up data file.
Run the following script:
The database data is recovered.
For more information about how to recover the PostgreSQL database data, see .
If you created a customized agent policy, including adding comments, copy the contents of the policy and save it as a text file. This backup file can be used to compare the previous settings with the current.
If you customized other settings with the help of BMC Support, contact them for assistance backing up the settings.
Copy the contents from the saved text file and paste them into the agent policy.
Before you upgrade the App Visibility server, use the Synthetic Transaction SLA Report utility to back up your synthetic SLA data to mitigate problems that might occur during migration of the data.
See Generating report data with the BMC Synthetic Transaction SLA Report utility for more details about running the Synthetic Transaction SLA Report utility.
Consider the following version compatibility behaviors with the App Visibility upgrade:
Integration with TrueSight Operations Management components: Install or upgrade Infrastructure Management components , including the latest patches.
You will not be able to see the latest updates in the TrueSight console, though, until you upgrade the Presentation Server. For details about the order to upgrade components, see Upgrading App Visibility Manager components.
App Visibility server version. You can upgrade the App Visibility server components from version 10.1 to the current version of App Visibility. For earlier versions of the App Visibility server, current version.
When you upgrade the App Visibility server, you can enable high-availability configuration for the App Visibility portal and collectors. You will need to edit the App Visibility portal details in the Presentation Server. See for more details.
Do not delete the App Visibility portal from the Presentation Server. Deleting the portal causes a loss of historic synthetic monitoring data.
Agent version. Upgrade the App Visibility agents from version 10.1, or later, to the current version of App Visibility. You must upgrade all agents, including TEA Agents, to the current version.
For earlier versions of the agents, do the following procedures:
|App Visibility agent for Java|
|App Visibility agent for .NET|
|Synthetic TEA Agent||Upgrade to the current version.|
Customized policy and configuration files. When you upgrade the server, all customized policy files are merged with the upgraded files. Existing functionality and values are retained for earlier agents, and new functionality is added for upgraded agents.If you added comments to customized files, the comments are not retained after upgrade.
If you use multiple keystore aliases in the security certificates for App Visibility server components, after upgrade to the current version the component services cannot start. You must update the
key.store.alias property in the
with the alias that you want the components to use, and then
and verify the upgraded version.