Applying feature packs or fix pack to App Visibility server components

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

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

Warnings

Do not delete the App Visibility portal from the TrueSight console before upgrading . Deleting the portal before upgrading will cause a loss of historic synthetic monitoring data.
Some data will be missed during the upgrade process.
In an HA environment, to minimize data loss you must upgrade the HA cluster in the following order:
1. Stop the component service for the standby node:
  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.
  - (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
2. Go to the active node component and upgrade the active node.
3. Return to the standby node component and upgrade the standby node. The upgrade process restarts the service automatically.

To apply a fix pack to the App Visibility server

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

(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 Name	Host name or IP address of the load balancing server that manages access to the collector
Load Balancer Port	Listening 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.

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

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.
Click Done to exit the wizard.

To silently apply a fix pack to the App Visibility server

On the computer where you want to apply the fix pack to the App Visibility server component or components, extract the downloaded files to a temporary directory.
Open the downloaded options file in a text editor:
- (Windows) adop-silent-option-upgrade.txt
- (Linux) adop-silent-option-upgrade

(For App Visibility collector or proxy) If you apply the feature pack or fix pack to 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 apply the feature pack or fix pack to the portal on the same computer as the collector, proxy, or both, the portal parameters are ignored for that process.

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

(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

(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

Save and close the options file.

To apply the feature pack or fix pack silently, 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

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.

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.
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
```
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
Examine the portal status in the Components page of the TrueSight console.

Where to go from here

Examine other processes for applying the feature pack or fix pack to App Visibility components at Applying feature packs or fix packs to App Visibility Manager components.

Page tree