Applying feature packs or fix packs on the App Visibility server using the wizard

Where you are in the Applying feature packs or fix packs process

StepTask
1Prepare to apply the feature pack or fix pack
2Apply the feature pack or fix pack on the TrueSight Presentation Server
3Apply the feature pack or fix pack on Infrastructure Management
4Apply the feature pack or fix pack on App Visibility Manager — Phase A (You are here)
Apply the feature pack or fix pack on App Visibility Manager — Phase B
5Apply the feature pack or fix pack on IT Data Analytics

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.

To apply the feature pack or fix pack to the App Visibility server in standalone mode

  1. On the computer where you want to apply the feature pack or fix pack to the App Visibility server component or components, copy and extract the downloaded files to a temporary directory.
  2. Launch the 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.

    Note

    (Applicable to version 11.3.02 only) If you are on Windows 2019, ignore any installer warning message and continue with your installation.

  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 process ends.

  5. If prompted, select the component:

    • For all App Visibility server components installed on the computer, the components are selected on the Features page and you must apply the feature pack or fix pack to 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 processes include the option to enable HA.
  6. On the upgrade prerequisites page, confirm that you have backed up your App Visibility database. For information on backing up the App Visibility database, see Preparing to apply feature packs or fix packs on App Visibility Manager.
  7. (For portal or collector, upgrade 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) If you apply the fix pack 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 feature pack or fix pack is applied, a successful upgrade is indicated in the wizard.

    If the feature pack or fix pack is not successful applied, or if you want to confirm, click View Log to view the log files.

  10. Click Done to exit the wizard.

To apply the feature pack or fix pack to the App Visibility server in high-availability mode

In a high-availability deployment, apply the feature pack or fix pack in the following sequence:

  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.

     Click here to expand for the steps to upgrade the active node
    1. Extract the downloaded files to a temporary directory.
    2. (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

    3. Launch the upgrade wizard:

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

      • (Linux) Run setup.bin.

    4. Review the Welcome page, and click Next.

      Note

      (Applicable to version 11.3.02 only) If you are on Windows 2019, ignore any installer warning message and continue with your installation.

    5. 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 process ends.

    6. Review that the component you want to upgrade is selected and click Next.
    7. On the upgrade prerequisites page, confirm that you have backed up your App Visibility database. For information on backing up the App Visibility database, see Preparing to apply feature packs or fix packs on App Visibility Manager.
    8. Click Yes to confirm that the standby node was stopped and click Next.
    9. Review the Installation Preview screen and click Install.
    10. After the upgrade process completes, click View Log to view the installation log files.
    11. Click Done to exit the wizard.
      The upgrade process restarts the service automatically.
  5. Go to the standby node and follow these steps to upgrade the standby node.

     Click here to expand for the steps to upgrade standby node
    1. Extract the downloaded files to a temporary directory.
    2. (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

    3. Launch the upgrade wizard:

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

      • (Linux) Run setup.bin.

    4. Review the Welcome page, and click Next.

      Note

      (Applicable to version 11.3.02 only) If you are on Windows 2019, ignore any installer warning message and continue with your installation.

    5. 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 process ends.

    6. Review that the component you want to upgrade is selected and click Next.
    7. Click Yes to confirm that you have upgraded the active node and click Next.
    8. Review the Installation Preview screen and click Install.
    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.
  6. Ensure that you perform steps from 1 to 5 for both Portal and Collector components.

  7. Perform the following steps to upgrade the App Visibility Proxy:

     Click here to expand for the steps to upgrade the Proxy
    1. Login to the host computer on which you want to install the app Visibility proxy.
    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.3.x> to <11.3.02 or later> component and click Next.
      For example, upgrade BMC App Visibility Proxy 11.3.01 to 11.3.02 or upgrade BMC App Visibility Proxy 11.3.02 to 11.3.03.
    8. 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.


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

    10. Click Done to exit the wizard.

To apply the feature pack or fix pack and enabling high-availability in App Visibility server 

If you have an existing App Visibility Portal or Collector in standalone mode and installed on separate host machines, you can enable HA when you are applying the latest fix pack. Do the following:

  1. Upgrade your existing Portal and Collector nodes in standalone mode and enable HA when you apply the fix pack. For more information, see To apply the feature pack or fix pack to the App Visibility server in standalone mode.
  2. Install an additional 11.3.01 standalone App Visibility Portal or Collector node. For more information, see  Installing TrueSight App Visibility Manager.
  3. Apply the latest fix pack and enable the HA mode on the additional node during the upgrade. For more information, see To apply the feature pack or fix pack to the App Visibility server in standalone mode.

Troubleshooting the feature pack or fix pack application

  • If the feature pack or fix pack is successful applied, an indication is displayed in the command window.

  • If the feature pack or fix pack application fails, you must uninstall what has been installed before rerunning the process. For more information about the uninstall process, see Uninstalling the App Visibility server.

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

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

To verify the App Visibility server after applying the feature pack or fix pack

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. 

  1. Access the adopserver_install_log.txt file, which is located in the %temp% directory (Windows) or /tmp directory (Linux).
    Check for warnings or errors. If no error messages are present, the installation was successful.
  2. According to what you have upgraded, verify that the App Visibility server components are running.
    • (Windows) Run services.msc and verify that services are running:
      • BMC App Visibility Collector
      • BMC App Visibility Portal
      • BMC App Visibility PostgreSQL
      • BMC App Visibility Proxy
    • (Linux) Run the following commands to verify that the processes are running:

      ps -ea|grep adop_collectord
      ps -ea|grep adop_portald
      ps -ea|grep adop_apm_proxyd
      ps -ea|grep av_pgsqld
  3. Check for errors reported in the App Visibility log files in the following locations:
    • Windows
      • serverInstallationDirectory\collector\logs\collector.log
      • serverInstallationDirectory\portal\logs\portal.log
      • serverInstallationDirectory\apm-proxy\logs\apm-proxy.log
    • Linux
      • serverInstallationDirectory/collector/logs/collector.log
      • serverInstallationDirectory/portal/logs/portal.log
      • serverInstallationDirectory/apm-proxy/logs/apm-proxy.log
  4. Examine the portal status in the Component information  page of the TrueSight console.

Where to go from here

Step 4 Phase B — Now that you have successfully installed the feature pack or fix pack on the App Visibility server, you must install it on the Synthetic TEA Agent.

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

Comments