Performing the App Visibility server upgrade silently

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 silent upgrade procedure, as described in this topic, and deploy the silent upgrade to several computers, or you can upgrade using the upgrade wizard.

When you run the silent installation, only the App Visibility components that are on the computer are upgraded. After you upgrade components, if you are not in a high-availability environment, you can run the silent installation to install components that are not on the computer.

Upgrade from an earlier version

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

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:

Before you begin

• Download the installation files from the Electronic Product Distribution site to a temporary directory on the App Visibility server computer.  
• Ensure that you have completed all tasks described in the Preparing for the App Visibility server installation, ensuring that you meet system requirements and installation (and upgrade) privileges.
• Complete the tasks in Preparing for an App Visibility upgrade and checking compatibility topic, ensuring that you back up the database and customized agent policies.

To upgrade the App Visibility server silently

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 a high-availability environment from an environment that is not HA, use these values to 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 high availability, or if it is already set up for HA, skip to Step 6.

   • To set up a high-availability 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 a high-availability 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.
     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.
     ha_alternate_node_db_port	Listening port that is used by the alternate component's App Visibility database

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. Save and close the upgrade options file.
7. 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

   Notes

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

   • 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 are located in the following directories:

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

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