Preparing for an App Visibility upgrade and checking compatibility

This topic presents instructions to prepare the App Visibility Manager environment for an upgrade and describes compatibility considerations for the upgrade.

Increasing App Visibility server space requirements

Upgrading App Visibility server components (portal and collector) requires an additional 500 MB of free space to accommodate for upgrading the database technology.

Changing App Visibility database authentication

The App Visibility portal and App Visibility collector each include an App Visibility database, which is a PostgreSQL database that uses trust authentication by default. This authentication assumes that anyone who can access the App Visibility portal or collector computers is authorized to access the database.

If you changed the authentication method for one or more databases, such as password authentication, you must change back to trust authentication before you upgrade the component or components. After you complete the upgrade, you can return to the authentication method of your choice. To change the authentication method, refer to the PostgreSQL documentation.

Warning

The database authentication method must be trust authentication before you begin the upgrade or else the upgrade fails, and you must manually restore the database.

Backing up the App Visibility database

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.


To create an App Visibility database backup file

  1. On the computer with the App Visibility portal or collector, navigate to the following directory:
    • (Windows) collector_installationDirectory\collector\bin\db or portal_installationDirectory\portal\bin\db
    • (Linux) collector_installationDirectory/collector/bin/db or portal_installationDirectory/portal/bin/db
    If the portal and collector are installed on the same computer, they share a database, and you only need to perform the procedure in one place.
    If the portal and collector are on separate computers, perform the backup procedure on both components at the same time so that the backup content is consistent. Otherwise, the backup content does not match and the data is incorrect when restored.
  2. Run the following script:
    • (Windows) create-pgsql-dump.bat
    • (Linux) ./create-pgsql-dump.sh

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 Backup and Restore .

Recovering the App Visibility database data

If you have issues with your database, you can recover the backed-up data file.

To recover the backed up App Visibility data file

  1. Ensure that the avdb.dump file is in the server component's installationDirectory\ADOP_DB\pgsql\backup directory.
  2. Stop the component service:
    • On the computer with the App Visibility portal, stop the portal service.
    • On the computer with the App Visibility collector, stop the collector service.
    For information about stopping services, see Starting and stopping the App Visibility server services.
  3. Navigate to the following directory, according to your system:
    • (Windows) collector_installationDirectory\collector\bin\db or portal_installationDirectory\portal\bin\db
    • (Linux) collector_installationDirectory/collector/bin/db or portal_installationDirectory/portal/bin/db
    If the portal and collector are installed on the same computer, they share a database, and you only need to perform the procedure in one place.
    If the portal and collector are on separate computers, perform the recovery procedure on both components at the same time so that the content is consistent. Otherwise, the content does not match and the data is incorrect when restored.
  4. Run the following script:

    • (Windows) restore-pgsql-dump.bat
    • (Linux) ./restore-pgsql-dump.sh
  5. Start the component service.

The database data is recovered.

For more information about how to recover the PostgreSQL database data, see Backup and Restore .

Backing up customized App Visibility agent policies

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.

  1. In the navigation pane of the TrueSight console, select Administration > App Visibility Agent Policies.
  2. Click the name of the agent policy you want to back up.
  3. Copy the contents of the agent policy and paste them into a text file.
  4. Save the text file as a backup file.

If you customized other settings with the help of BMC Support, contact them for assistance backing up the settings.

Recovering customized App Visibility agent policies

  1. In the navigation pane of the TrueSight console, select Administration > App Visibility Agent Policies.
  2. Click the name of the agent policy you want to back up.
  3. Copy the contents of the saved text file and paste them into the agent policy.

  4. Save the agent policy.

Backing up synthetic SLA data

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

Error rendering macro 'link-window' : [com.ctc.wstx.exc.WstxLazyException] Duplicate attribute 'report'. at [row,col {unknown-source}]: [4,134]
 for more details about running the Synthetic Transaction SLA Report utility.

Checking upgrade compatibility

Consider the following version compatibility behaviors with the App Visibility upgrade:

Component versions

  • Integration with TrueSight Operations Management components: Install or upgrade the 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 version of server and agents. You must upgrade all the server components (portal, all collectors, and all proxies) and agents, including TEA Agents.
    • App Visibility server version. You can upgrade the App Visibility server components from version 10.5 to the current version of App Visibility. For earlier versions of the App Visibility server, upgrade to server version 10.5 and then upgrade to the 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 To edit a component's values for more details.

      Warning

      Do not delete the App Visibility portal from the Presentation Server. Deleting the portal causes a loss of historical synthetic monitoring data.

    • Agent version. Upgrade the App Visibility agents from version 10.5, 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:

      Upgrade componentSteps
      App Visibility agent for Java
      1. Upgrade to version 10.5 from an earlier version.
      2. Upgrade to the current version from version 10.5, or later.
      App Visibility agent for .NET
      1. Upgrade to version 10.5 from an earlier version.
      2. Upgrade to the current version from version 10.5, or later.
      Synthetic TEA AgentUpgrade to the current version.

Operating system compatibility

You cannot upgrade App Visibility server components installed on SUSE Linux Enterprise Server version 11 SP3 or SP4.

Policy and configuration files

  • Out-of-the-box policy and configuration files. When you upgrade the server, all out-of-the-box policy files and configuration files are automatically upgraded, and the policies can work with the supported agents.
  • 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 the upgrade.

Multiple keystore aliases in security certificates

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 private certificates of the App Visibility components with the alias that you want the components to use, and then restart the services.  

Where to go from here

Upgrade the App Visibility server and verify the upgraded version. 

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Anthony Valuikas

    link is broken for "security certificates of the App Visibility components"

    Mar 07, 2018 12:48
    1. Sara Kamen

      Hi Anthony,

      Thank you for bringing this to our attention.

      The link is now fixed.

      Regards,

      Sara

      Mar 27, 2018 09:55