BMC TrueSight Operations Management 11.3 Upgrading

Upgrading the App Visibility server in the high-availability mode silently

Where you are in the Upgrade process

Step Task
1 Preparing to upgrade TrueSight Operations Management solution
2 Upgrade Remedy Single Sign-On
3 Upgrade TrueSight Presentation Server
4 Upgrade TrueSight Infrastructure Management
5 Upgrade App Visibility Manager — Phase A (You are here)
Upgrade App Visibility Manager — Phase B
6 Upgrade Real End User Experience Monitoring Software Edition
7 Upgrade 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 set options for silent upgrade of the App Visibility portal

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

  Click here to expand the steps.
  1. On the computer where you want to upgrade the App Visibility portal, extract the downloaded files to a temporary directory.

  2. Open the downloaded options file in a text editor:

    • (Windows)   adop-silent-option-upgrade.txt
    • (Linux)   adop-silent-option-upgrade

  3. (For upgrade to high-availability)

    • If you do not want to set up your environment for HA, save and close the upgrade options file without change.

    • If your environment is already set up for HA, add a value for the ha_node_synchronization_port.
      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.
      The default value is 5701.

    • To set up an HA environment, set ha_enabled to true and enter values for the current portal and alternate portal.

      The following example displays values for a portal in an HA environment.

      -J ha_enabled=true
-J ha_current_node_fqdn=myPortalA.bmc.com
-J ha_alternate_node_fqdn=myPortalB.bmc.com
-J ha_alternate_node_db_port=8800
-J ha_node_synchronization_port=5701


      Parameter descriptions for the portal's alternate component

      Parameter

      Description

      ha_enabled

      Setting to enable HA component configuration

      The default value is false.

      ha_current_node_fqdn

      FQDN of the current computer onto which you are upgrading the portal

      ha_alternate_node_fqdn

      		 FQDN of the alternate component's computer

      ha_alternate_node_db_port

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

      The default port is 8800.
      ha_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.
  4. Save and close the upgrade options file.


To set options for silent upgrade of an App Visibility collector

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

  Click here to expand the steps.
  1. On the computer where you want to upgrade an App Visibility collector, extract the downloaded files to a temporary directory.

  2. Open the downloaded options file in a text editor:

    • (Windows)   adop-silent-option-upgrade.txt
    • (Linux)   adop-silent-option-upgrade

  3. If necessary, update the App Visibility portal connection information.

    For example, if you are upgrading to an HA environment from an environment that is not HA, enter the IP address and port number of the load balancing server for the App Visibility portal.

    -J portal_ip=
-J portal_communication_port=

    Parameter

    Description

    portal_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 the load balancer.

    portal_communication_port

    Listening port of the portal

    If a load balancing server manages access to the portal, enter the port number for the load balancer.

  4. (For upgrade to high-availability)

    • If you do not want to set up your environment for HA, save and close the upgrade options file without change.

    • If your environment is already set up for HA, add a value for the ha_node_synchronization_port.
      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.
      The default value is 5701.

    • To set up an HA environment, set ha_enabled to true and enter values for the current collector and alternate portal.

      The following example displays values for a portal in an HA environment.

      -J ha_enabled=true
-J ha_current_node_fqdn=myCollectorA.bmc.com
-J ha_alternate_node_fqdn=myCollectorB.bmc.com
-J ha_alternate_node_db_port=8800
-J ha_node_synchronization_port=5701

      Parameter descriptions for the collector's alternate component

      Parameter

      Description

      ha_enabled

      Setting to enable HA component configuration

      The default value is false.

      ha_current_node_fqdn

      FQDN of the current computer onto which you are upgrading the collector

      ha_alternate_node_fqdn

      		 FQDN of the alternate collector's computer

      ha_alternate_node_db_port

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

      The default port is 8800.
      ha_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.

  5. (For upgrade to high-availability ) Enter values for the load balancer that manages access to the collector: 

    -J ha_lb_host=
-J ha_lb_port=

    Parameter descriptions for the collector's load balancer

    Parameter

    Description

    ha_lb_host

    Host name or IP address of the load balancing server that manages access to the collector pair
    ha_lb_port Listening port of the load balancing server that manages access to the collector pair
  6. Save and close the upgrade options file.


To set options for silent upgrade of an App Visibility proxy

The procedure describes how to set the options 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

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 cluster issues are resolved, unless you explicitly run the installation utility with a command to continue with such errors.

If you want to upgrade the proxy without testing connectivity (not recommended), 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 cluster issues after the upgrade process, and restart all the cluster nodes for the storage engines.

  1. On the computer where you want to upgrade an App Visibility proxy, extract the downloaded files to a temporary directory.

  2. Open the downloaded options file in a text editor:

    • (Windows)  adop-silent-option-upgrade.txt
    • (Linux)  adop-silent-option-upgrade

  3. Enter values for the proxy storage:

    -J proxy_storage_http_port=8302
-J proxy_storage_transport_port=8303
-J proxy_storage_transport_ip=192.0.2.24

    Parameter descriptions for the proxy storage

    Parameter

    Description

    proxy_storage_http_port

    Listening port of the App Visibility proxy database

    The default port is 8302.
    proxy_storage_transport_port

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

    The default port is 8303.
    proxy_storage_transport_ip

    Used for communication between the different nodes in the storage cluster

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

    If you do not provide a value, the default IP address is the first received by the system.

  4. If necessary, update the App Visibility portal connection information.

    For example, if you are upgrading to an HA environment from an environment that is not HA, enter the IP address and port number of the load balancing server for the App Visibility portal.

    -J portal_ip=
-J portal_communication_port=

    Parameter

    Description

    portal_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 the load balancer.

    portal_communication_port

    Listening port of the portal

    If a load balancing server manages access to the portal, enter the port number for the load balancer.
  5. Save and close the upgrade options file.


To set options for silent upgrade of one or more App Visibility server components

The procedure describes how to set the options to upgrade one or more App Visibility server components on the same 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 cluster issues are resolved, unless you explicitly run the installation utility with a command to continue with such errors.

If you want to upgrade the proxy without testing connectivity (not recommended), 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 cluster issues after the upgrade process, and restart all the cluster nodes for the storage engines.

  1. On the computer where you want to upgrade the App Visibility server component or components, extract the downloaded files to a temporary directory.

  2. Open the downloaded options file in a text editor:

    • (Windows)  adop-silent-option-upgrade.txt
    • (Linux)  adop-silent-option-upgrade

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

    For example, if you are upgrading to an HA environment from an environment that is not HA, enter the IP address and port number of the load balancing server for the App Visibility portal.

    If you upgrade the portal on the same computer as the collector, proxy, or both, the portal parameters are ignored for that upgrade.

    -J portal_ip=
-J portal_communication_port=

    Parameter

    Description

    portal_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 the load balancer.

    portal_communication_port

    Listening port of the portal

    If a load balancing server manages access to the portal, enter the port number for the load balancer.

  4. (For portal or collector, upgrade to high-availability)

    • If you do not want to set up your environment for HA, or if it is already set up for HA, skip to Step 6.

    • To set up an HA environment, set ha_enabled to true and enter values for the current component and alternate component.

      The following example displays values for a collector in an HA environment.

      -J ha_enabled=true
-J ha_current_node_fqdn=myCollectorA.bmc.com
-J ha_current_node_port=8202
-J ha_alternate_node_fqdn=myCollectorB.bmc.com
-J ha_alternate_node_port=8202
-J ha_alternate_node_db_port=8800

      Parameter descriptions for the portal or collector's alternate component

      Parameter

      Description

      ha_enabled

      Setting to enable HA component configuration

      The default value is false.

      ha_current_node_fqdn

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

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

      ha_alternate_node_fqdn

      		 FQDN of the alternate component's computer

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

      ha_alternate_node_db_port

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

      The default port is 8800.

  5. (For collector, upgrade to high-availability ) Enter values for the load balancer that manages access to the collector: 

    -J ha_lb_host=
-J ha_lb_port=

    Parameter descriptions for the collector's load balancer

    Parameter

    Description

    ha_lb_host

    Host name or IP address of the load balancing server that manages access to the collector pair
    ha_lb_port Listening port of the load balancing server that manages access to the collector pair

  6. (For proxy) Enter values for the proxy storage:

    -J proxy_storage_http_port=8302
-J proxy_storage_transport_port=8303
-J proxy_storage_transport_ip=192.0.2.24

    Parameter descriptions for the proxy storage

    Parameter

    Description

    proxy_storage_http_port

    Listening port of the App Visibility proxy database

    The default port is 8302.
    proxy_storage_transport_port

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

    The default port is 8303.
    proxy_storage_transport_ip

    Used for communication between the different nodes in the storage cluster

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

    If you do not provide a value, the default IP address is the first received by the system.
  7. Save and close the upgrade options file.

To upgrade the App Visibility server silently

  1. In a command line window, navigate to the directory with the silent-option-upgrade file.
  2. To run the silent upgrade, enter the following command:

    • Windows

      setup.exe -i silent -DOPTIONS_FILE=<fullFilePath>\adop-silent-option-upgrade.txt

    • Linux

      ./setup.bin -i silent -DOPTIONS_FILE=<fullFilePath>/adop-silent-option-upgrade

If the upgrade is successful, an indication is displayed in the command window.

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 Sanjay Prahlad on Dec 05, 2018
task ad_server upgrading app_visibility_manager high_availability upgrading_app_visibility

Comments

Upgrading the App Visibility server in the high-availability mode using the wizard
Preparing for upgrading the App Visibility agents
© Copyright 2013-2018 BMC Software, Inc. © Copyright 2013-2018 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport