Upgrading the App Visibility server in the high-availability mode using the wizard



Where you are in the Upgrade process


You must be a system administrator to perform the TrueSight App Visibility Manager server components upgrade. 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 TrueSight App Visibility Manager 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 TrueSight App Visibility Manager Manager and HA, see App-Visibility-Manager-high-availability-deployment.


Warnings

Some data will be incomplete or missing until you finish the upgrade process.

appvis_ha_enhancements.png

To upgrade the App Visibility portal

The procedure describes how to upgrade the App Visibility portal when it is the only App Visibility server component on the computer.

Click here to expand steps.

  1. 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.

  2. Log into the standby node.

  3. Stop the component service for 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.servicesystemctl stop adop_collector.service

  4. Go to the active node component and follow these steps to upgrade the active node.

  5. Failed to execute the [excerpt-include] macro.
  6. Failed to execute the [excerpt-include] macro.
  7. Failed to execute the [excerpt-include] macro.
  1. Failed to execute the [excerpt-include] macro.
  2. Failed to execute the [excerpt-include] macro.
  3. Failed to execute the [excerpt-include] macro.
  4. Failed to execute the [excerpt-include] macro.

  5. (To upgrade a high-availability environment) On the High Availability page, enter a value for the Node Synchronization Port, or use the default value, 5701.

    The port synchronizes data between the current and alternate nodes and is dedicated for communication between the nodes.

    The port must be the same number on the current and alternate nodes.

  6. (Optional) Accept the Confirm upgrading the Standby server. Select Yes and click Next.
  7. On the upgrade prerequisites page, confirm that you have backed up your App Visibility portal database. For information on backing up the App Visibility database, see Preparing-to-upgrade-the-App-Visibility-Server-and-checking-compatibility.

  8. (To upgrade to a high-availability environment) If your environment is not set up for HA, and you want to set up an HA environment, select Enable High Availability and type the following values.

    Ensure that all port numbers are available.

  9. After the upgrade process completes, click View Log to view the installation log files.
  10. Click Done to exit the wizard.
    The upgrade process restarts the service automatically.
  11. Go to the standby node component and upgrade the standby node.
  12. Repeat steps from 5 to 17 on the standby node.

  13. If you enabled HA for the App Visibility portal for the first time, 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.

To upgrade an App Visibility collector

The procedure describes how to upgrade an App Visibility collector when it is the only App Visibility server component on the computer.

Click here to expand steps.
  1. Failed to execute the [excerpt-include] macro.
  2. Failed to execute the [excerpt-include] macro.
  3. Failed to execute the [excerpt-include] macro.
  4. Failed to execute the [excerpt-include] macro.
  5. Failed to execute the [excerpt-include] macro.
  6. Failed to execute the [excerpt-include] macro.
  7. Failed to execute the [excerpt-include] macro.
  1. Failed to execute the [excerpt-include] macro.
  2. Failed to execute the [excerpt-include] macro.
  3. Failed to execute the [excerpt-include] macro.
  4. Failed to execute the [excerpt-include] macro.

  5. On the High Availability page, enter a value for the Node Synchronization Port, or use the default value, 5702.

    The port synchronizes data between the current and alternate nodes and is dedicated for communication between the nodes.

    The port must be the same number on the current and alternate nodes.

  6. Failed to execute the [excerpt-include] macro.
  7. Failed to execute the [excerpt-include] macro.
  8. (Optional) If your environment is not set up for HA, and you want to set up an HA environment, select Enable High Availability and enter the following values.

  9. Ensure that all port numbers are available.

    On the next page of the HA configuration, enter details for the load balancing server that manages access to the collector:

  10. Failed to execute the [excerpt-include] macro.
  11. Failed to execute the [excerpt-include] macro.
  12. Failed to execute the [excerpt-include] macro.
  13. Go to the standby node component and upgrade the standby node.
  14. Repeat steps from 5 to 18 on the standby node.
  15. Failed to execute the [excerpt-include] macro.

To upgrade an App Visibility proxy

The procedure describes how to upgrade an App Visibility proxy when it is the only App Visibility server component on the computer.

Click here to expand the steps.

Failed to execute the [excerpt-include] macro.

  1. Failed to execute the [excerpt-include] macro.
  2. Failed to execute the [excerpt-include] macro.
  3. Failed to execute the [excerpt-include] macro.
  1. Failed to execute the [excerpt-include] macro.
  2. Failed to execute the [excerpt-include] macro.
  3. Failed to execute the [excerpt-include] macro.
  4. Failed to execute the [excerpt-include] macro.
  5. Failed to execute the [excerpt-include] macro.
  6. Failed to execute the [excerpt-include] macro.
  7. Failed to execute the [excerpt-include] macro.
  8. Failed to execute the [excerpt-include] macro.
  9. Failed to execute the [excerpt-include] macro.

To verify that the TrueSight App Visibility Manager server upgrade was successful

After the upgrade is complete, a successful upgrade is indicated in the wizard or on the command window. Use the following procedure to confirm or troubleshoot the upgrade of the server components. 

Click here to expand the steps.

  1. Access the adopserver_install_log file:

    • (Windows) %temp%
    • (Linux) /tmp

  2. Check for warnings or errors. 
    If no error messages are present, the upgrade (installation) was successful.

  3. Based on the upgraded component, verify that the App Visibility server components are running:

    • (Windows) Run services.msc and verify that the services are running:
      For Collector and Portal

      • App Visibility Collector
      • App Visibility Portal
      • App Visibility PostgreSQL

      For Proxy

      • App Visibility Proxy
      • App Visibility Elasticsearch

    • (Linux) Run the following commands to verify that the processes are running:

      For Collector and Portal

      • ps -ea|grep adop_collectord
      • ps -ea|grep adop_portald
      • ps -ea|grep adop_apm_proxyd

      For Proxy

      • ps -ea|grep av_pgsqld
      • ps -ea|grep apm_elasticsearch

  4. Check for errors reported in the App Visibility log files in the following locations:

    • (Windows)
      • server_installationDirectory\collector\logs\collector.log
      • server_installationDirectory\portal\logs\portal.log
      • server_installationDirectory\apm-proxy\logs\apm-proxy.log
    • (Linux)
      • server_installationDirectory/collector/logs/collector.log
      • server_installationDirectory/portal/logs/portal.log
      • server_installationDirectory/apm-proxy/logs/apm-proxy.log

    Note

    If a network port is occupied, the App Visibility server component stops, as reflected in the component log, but the log message does not give the reason.

  5. Add App Visibility to the TrueSight console, if you have not already done so.

  6. Examine the portal status in the Components page of the TrueSight console.

Failed to execute the [excerpt-include] macro.

Failed to execute the [excerpt-include] macro.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*