Performing the App Visibility server upgrade


This topic presents upgrade procedures for the App Visibility server from version 10.5, or later, to the current version. You can upgrade App Visibility components using the upgrade wizard, as described in this topic, or you can upgrade the components using the silent upgrade procedure.

When you run the installation wizard on a system with a previous version of the product, the wizard automatically switches to upgrade mode for the installed component or components.

 If App Visibility server components are installed on separate computers, the portal and collector upgrade processes include the option to enable high availability (HA). For more information about App Visibility Manager and HA, see App Visibility Manager high-availability deployment.This topics presents the following information:

Upgrade from an earlier version
To upgrade from a version earlier than 10.5, first upgrade to version 10.5 .

Before you begin

Warnings

  • Do not delete the App Visibility portal from the TrueSight console before upgrading. Deleting the portal before upgrading will cause a loss of historic synthetic monitoring data.
  • Some data will be incomplete or missing until you finish the upgrade process.
  • In an HA environment, to minimize data loss you must upgrade the HA cluster in the following order:
    1. Stop the component service for the standby node:

      Check your load balancing server to confirm which node is the standby node. You can also check the component log files to confirm which server is the standby node.

      • (Windows) Use the Windows services manager (services.msc) to stop the relevant component: BMC App Visibility Portal or BMC App Visibility Collector.
      • (Linux) Run the required command to stop the the relevant component:
        • Linux 
          service adop_portal stop 
          service adop_collector stop
        • SUSE Linux Enterprise 12 
          systemctl stop adop_portal.service 
          systemctl  stop adop_collector.service
           
    2. Go to the active node component and upgrade the active node.
    3. Return to the standby node component and upgrade the standby node. The upgrade process restarts the service automatically.

To upgrade the App Visibility server

  1. On the computer where you want to upgrade the App Visibility server component or components, copy and extract the downloaded files to a temporary directory.
  2. Launch the upgrade wizard
    • (Windows)
      Double-click setup.exe.
      In Windows 2008, you might need to right-click the setup.exe icon and select Run as administrator.

    • (Linux)
      Ensure that you have set the DISPLAY environment variable.
      Run setup.bin.
  3. On the welcome page, click Next.

  4. On the License Agreement page, read the agreement and select the I agree to the terms of the license agreement option, and then click Next.
    If you do not agree to the terms of the license agreement, the upgrade process ends.
  5. If prompted, select the upgrade component:

    • For all App Visibility server components installed on the computer, the components are selected on the Features page and you must upgrade them.
    • If one or more server components are not installed, you can select to install another component on the Features page.
      For instructions about installing the new component, see Performing the App Visibility server installation.
    • If App Visibility server components are installed on separate computers, the portal and collector upgrade processes include the option to enable HA.
  6. (For portal or collector)
    On the upgrade prerequisites page, confirm that you have backed up your App Visibility server database. If you haven't backed it up, see Backing up and recovering the App Visibility database for details on how to do it.

  7. (For portal or collectorupgrade to high-availability)

    • If you do not want to set up your environment for high availability, or if it is already set up for HA, skip this step.
    • If your environment is not set up for high availability, and you want to set up an HA environment, select Enable High Availability and enter the following values.

      Ensure that all port numbers are available.

      Option

      Description

      Current HA Node Information
      Node FQDN

      FQDN of the current computer on which you are upgrading the component

      The FQDN of the current computer is automatically entered; ensure that it is accessible from other components.

      Node Port

      HA control port of the current component

      The port is dedicated for communication between nodes.

      The default port is 8102 for the portal, 8202 for the collector.

      (For collector HA) Load balancing server that manages access to the collector
      Load Balancer Host NameHost name or IP address of the load balancing server that manages access to the collector
      Load Balancer PortListening port of the load balancing server that manages access to the collector
      Alternate HA Node Information
      Node FQDN

      FQDN of the alternate component's computer

      Node Port

      HA control port of the alternate component

      The port is dedicated for communication between nodes.

      The default port is 8102 for the portal, 8202 for the collector.

      Database Port

      Listening port that is used by the alternate component's App Visibility database

      The default port is 8800.

  8. (For App Visibility collector or proxy upgrade) If you upgrade the App Visibility collector or proxy on a computer that does not have the App Visibility portal installation, you can update the App Visibility portal connection information. After you update the information, click Test Connection to check communication with the portal, and then click Next.

    Option

    Description

    Portal Host Name or IP

    App Visibility portal host name or IP address

    If a load balancing server manages access to the portal, enter the host name or IP address of that load balancing server.

    The default value is the value from the original installation.

    Portal Port

    Listening port of the portal

    If a load balancing server manages access to the portal, enter the port number of that load balancing server.

    The default value is the value from the original installation.

  9. After the upgrade is complete, a successful upgrade is indicated in the wizard.

    If the upgrade is not successful, or if you want to confirm, click View Log to view the log files.

  10. Click Done to exit the installation wizard.

Where to go from here

  1. After you upgrade the App Visibility server components, verify the App Visibility server upgrade.
  2. For large and extra large deployments (150,000–360,000 transactions per hour), increase the heap size on your App Visibility collector to 6 GB. For details, see Changing the heap size on App Visibility components .
  3. Upgrade other Operations Management components. For details, see Upgrade process overview for the TrueSight Operations Management solution.
  4. If you enabled high availability for the App Visibility portal for the first time, do the following tasks:
    1. In the TrueSight console, edit the App Visibility portal to the FQDN and port number of the portal's load balancing server. For details, see the section about editing component values in the Adding and editing components topic.
    2. Upgrade each App Visibility agent for Java and .NET, and then update each agent's portal connection details to the portal's load balancer. For details, see Changing settings of the App Visibility agent for .NET and Changing settings of the App Visibility agent for Java .

    3. Upgrade each TEA Agent and update each agent's portal connection details to the portal's load balancing server.

Related topics

Upgrading App Visibility agents for Java

Upgrading App Visibility agents for .NET 

Upgrading synthetic TEA Agents

Changing App Visibility collector settings

Changing App Visibility portal settings

Changing App Visibility proxy settings

 

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

Comments