Upgrading the App Visibility server in the standalone 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

Upgrade warning

If you have recently upgraded your TrueSight Operations Management with App Visibility Manager from version 11.0 to 11.0.00.003 (Fix Pack 3) and if you have configured it to work with SAML authentication type, do not upgrade that 11.0.00.003 setup to 11.3.01. The SAML authentication type does not work when you upgrade from version Fix Pack 3 with App Visibility Manager to 11.3.01.

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.

You must be a system administrator to perform the TrueSight App Visibility Manager server components upgrade. When you run the installation wizard to upgrade on a system with a previous version of the product, the wizard automatically switches to upgrade mode for the installed component or components. The App Visibility server includes the following components:

  • One App Visibility portal, or in an HA environment, one pair of App Visibility portal  nodes 
  • One or more App Visibility collectors, or in an HA environment, one or more pairs of App Visibility collector nodes
  • One or more App Visibility proxies

(For a very small environment or a test environment) You can install the portal, one collector, and one proxy on the same computer. When the App Visibility portal and collector components are installed on the same computer, they share the same database. For instructions, see Installing more than one App Visibility server component on the same computer.

(For production environments) You install one App Visibility portal on one computer, several App Visibility collectors (each on a separate computer), and App Visibility proxies on separate computers that are in the network's demilitarized zone (DMZ).

Upgrade the portal before the other server components because:

  • The collector and proxy reference the portal during upgrade.
  • The App Visibility agents also reference the portal during upgrade.

The portal includes a small database for configuration and connection information. If you install a portal and a collector on the same computer, they share the same database.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.You can have several collectors, depending on the volume of your transactions. Install each collector on a separate computer. Each collector includes a database for App Visibility data.

(For proxy installation) Ensure that each proxy is installed on a separate computer in the network's demilitarized zone (DMZ), or behind a firewall or network gateway that handles the secured communication and certificates with end-users' browsers. The App Visibility proxy requires a Certificate Authority (CA)-signed certificate.

The proxy uses SSL-encrypted beacons and injection requests and therefore you must have a keystore with a certificate that is trusted by end-users’ browsers. You can import the keystore during proxy upgrade or after upgrade.
If your application web pages are only HTTP, then after installation, you can change the protocol of the JavaScript fetch API to work with HTTP, instead of the default HTTPS. With HTTP, you do not need to import a keystore file.

To upgrade the App Visibility portal silently

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. 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. Open the downloaded options file in a text editor:

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

  4. Save and close the upgrade options file without change.

  5. In a command line window, navigate to the directory with the silent-option-upgrade file.

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


To upgrade the App Visibility collector silently

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. 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. Open the downloaded options file in a text editor:

    • (Windows)  adop-silent-option-upgrade.txt
    • (Linux)  adop-silent-option-upgrade
  4. If necessary, update the App Visibility portal connection information.

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

  6. In a command line window, navigate to the directory with the silent-option-upgrade 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


    If the upgrade is successful, an indication is displayed in the command window.
  8. 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 the App Visibility proxy silently

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

(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. Open the downloaded options file in a text editor:

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

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

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

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

  6. Save and close the upgrade options file without change.
  7. In a command line window, navigate to the directory with the silent-option-upgrade file.
  8. 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.
  9. 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 upgrade one or more App Visibility server components silently

(For a very small environment or a test environment) The procedure describes how 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 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. Open the downloaded options file in a text editor:

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

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

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

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

  8. Save and close the upgrade options file without change.
  9. In a command line window, navigate to the directory with the silent-option-upgrade file.
  10. 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.
  11. 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.
  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>

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

Comments