BMC TrueSight Operations Management 11.3 Upgrading

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



Where you are in the Upgrade process

StepTask
1Preparing to upgrade TrueSight Operations Management solution
2Upgrade Remedy Single Sign-On
3Upgrade TrueSight Presentation Server
4Upgrade TrueSight Infrastructure Management
5Upgrade App Visibility Manager — Phase A (You are here)
Upgrade App Visibility Manager — Phase B
6Upgrade Real End User Experience Monitoring Software Edition
7Upgrade TrueSight IT Data Analytics

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.

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.service
        systemctl stop adop_collector.service
  4. Go to the active node component and follow these steps to upgrade the active node.

  5. Login to the host computer on which you want to install the app Visibility portal, and delete all the files from the temporary directory:

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

  6. Extract the downloaded files to a temporary directory.

  7. (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
    export DISPLAY=<IP address of the host computer>:0.0

  8. Launch the upgrade wizard:

    • (Windows) Right-click setup.exe and select Run as administrator.

    • (Linux) Run setup.bin.

  9. Review the Welcome page, and click Next.

  10. Read the license agreement, agree to the terms, and click Next.

    If you do not agree to the terms of the license agreement, the upgrade process ends.

  11. On the feature selection page, select the upgrade BMC App Visibility Portal 11.0.00 to 11.3.01 component and click Next.

  12. (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.

  13. (Optional) Accept the Confirm upgrading the Standby server. Select Yes and click Next.

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

  15. (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.

    Option

    Description

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

    Alternate Node FQDN

    FQDN of the alternate component's computer

    Alternate Database Port

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

    The default port is 8800.

    Node Synchronization Port

    HA port that synchronizes data between the current and alternate nodes

    The port is dedicated for communication between nodes.

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

    The default port is 5701.

  16. After the upgrade process completes, click View Log to view the installation log files.

  17. Click Done to exit the wizard.
    The upgrade process restarts the service automatically.
  18. Go to the standby node component and upgrade the standby node.
  19. Repeat steps from 5 to 17 on the standby node.

  20. 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. 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.service
        systemctl stop adop_collector.service
  4. Go to the active node component and follow these steps to upgrade the active node.

  5. Login to the host computer on which you want to install the app Visibility portal, and delete all the files from the temporary directory:

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

  6. Extract the downloaded files to a temporary directory.

  7. (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
    export DISPLAY=<IP address of the host computer>:0.0

  8. Launch the upgrade wizard:

    • (Windows) Right-click setup.exe and select Run as administrator.

    • (Linux) Run setup.bin.

  9. Review the Welcome page, and click Next.

  10. Read the license agreement, agree to the terms, and click Next.

    If you do not agree to the terms of the license agreement, the upgrade process ends.

  11. On the Features page, select the upgrade BMC App Visibility Collector 11.0.00 to 11.3.01 component and click Next.

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

  13. 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.
  14. On the upgrade prerequisites page, confirm that you have backed up your App Visibility collector database. If you haven't backed it up, see "Backing up the App Visibility database" in Preparing to upgrade the App Visibility Server and checking compatibility for details on how to do it.

  15. (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.

  16. Ensure that all port numbers are available.

    Option

    Description

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

    Alternate Node FQDN

    FQDN of the alternate component's computer

    Alternate Database Port

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

    The default port is 8800.

    Node Synchronization Port

    HA port that synchronizes data between the current and alternate nodes

    The port is dedicated for communication between nodes.

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

    The default port is 5702.


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

    Option

    Description

    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

  17. If necessary, 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.

  18. After the upgrade process completes, click View Log to view the installation log files.
  19. Click Done to exit the wizard.
  20. Go to the standby node component and upgrade the standby node.
  21. Repeat steps from 5 to 18 on the standby node.
  22. 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.

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.

Note

(For App Visibility proxy upgrade) The upgrade process includes several checks for connectivity to the App Visibility portal and to other App Visibility proxy servers and storage engines. The process cannot continue until the connectivity and storage engine cluster issues are resolved, unless you explicitly run the installation utility with a command to continue with such errors.

(Not recommended) If you want to upgrade the proxy without testing connectivity, run the utility from a command line with the -J continue_with_connectivity_error=true parameter. At your own risk, you will have to resolve connectivity and storage engine cluster issues after the upgrade process, and restart all the storage engine cluster nodes.

  1. Login to the host computer on which you want to install the app Visibility portal, and delete all the files from the temporary directory:

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

  2. Extract the downloaded files to a temporary directory.

  3. (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
    export DISPLAY=<IP address of the host computer>:0.0

  4. Launch the upgrade wizard:

    • (Windows) Right-click setup.exe and select Run as administrator.

    • (Linux) Run setup.bin.

  5. Review the Welcome page, and click Next.

  6. Read the license agreement, agree to the terms, and click Next.

    If you do not agree to the terms of the license agreement, the upgrade process ends.

  7. On the Features page, select the upgrade BMC App Visibility Proxy 11.0.00 to 11.3.01 component and click Next.

  8. On the Proxy Configuration page, provide port numbers for the storage component that is added with the upgrade, and then click Next.

    Other port numbers are displayed but they are not editable during upgrade. For details about changing the settings after you complete the upgrade process, see Changing App Visibility proxy settings

    Ensure that the port numbers are available.

    Option

    Description

    Communication Port

    Listening port of the proxy, communication from the portal and collector

    The default port is 8300.

    Supportability Port

    Listening port of the proxy support console

    A support console, which helps detect issues, is automatically activated with one-way SSL authentication.

    The default port is 8301.

    Beacon Receiver HTTP Port

    Listening port of the beacon receiver, HTTP communication from the end users' browsers

    The default port is 880.

    Beacon Receiver HTTPS Port

    Listening port of the beacon receiver, HTTPS communication from the end users' browsers

    The default port is 8444.

    Storage HTTP Port

    Listening port of the App Visibility proxy database

    The default port is 8302.

    Storage Transport Port

    Port for TCP communication between App Visibility proxy database nodes in a cluster

    The default port is 8303.

    Storage Transport IP Address

    Used for communication between the different nodes in the storage cluster

    The IP address must be available from other App Visibility proxy nodes.

    The default IP address is the first received by the system.

  9. If necessary, 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.

  10. After the upgrade process completes, click View Log to view the installation log files.

  11. Click Done to exit the wizard.

  12. After you upgrade the App Visibility proxy, you must update the JavaScript stub for every application where you manually set up active end-user monitoring : change the last line of the stub to aeuem.min.js, as shown in the following example:

    <script type="text/javascript" src="https://apm_proxy_host:apm_proxy_https_port/static-resources/aeuem.min.js"></script>

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.

Troubleshooting upgrade issues

  • If the upgrade fails, you must uninstall what has been installed before rerunning the installation wizard. For more information about the uninstall process, see Uninstalling the App Visibility server.

  • You can examine the App Visibility server log files located in the following directories:

    • (Windows) %temp%\adopserver_install_log.txt
    • (Linux) /tmp/adopserver_install_log.txt

Next step in the Upgrading process

Step 5 Phase B Task 1 — Now that you have successfully installed the App Visibility server, you must upgrade the applicable App Visibility agents.


Was this page helpful? Yes No Submitting... Thank you
Last modified by Harihara Subramanian on May 15, 2019
upgrading task ad_server app_visibility_manager high_availability upgrading_app_visibility

Comments

Upgrading the App Visibility server in the standalone mode silently
Upgrading the App Visibility server in the high-availability mode silently
© Copyright 2013-2019 BMC Software, Inc. © Copyright 2013-2019 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2019 BMC Software, Inc.