Upgrading the App Visibility server in the standalone mode silently

Failed to execute the [excerpt-include] macro.

Failed to execute the [excerpt-include] macro.

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.

Failed to execute the [excerpt-include] macro.

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 (wizard-based or silently), one pair of App Visibility portal  nodes 
  • One or more App Visibility collectors, or in an HA environment (wizard-based or silently), one or more pairs of App Visibility collector nodes

  • One or more App Visibility proxies

    Note

    The Proxy server can be used with multiple deployments (as a cluster) working together as a single entity.

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.

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. Failed to execute the [excerpt-include] macro.
  2. Failed to execute the [excerpt-include] macro.

  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. Failed to execute the [excerpt-include] macro.
  2. Failed to execute the [excerpt-include] macro.
  3. Failed to execute the [excerpt-include] macro.

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

    -J portal_ip=
    -J portal_communication_port=
  5. Failed to execute the [excerpt-include] macro.
  6. Failed to execute the [excerpt-include] macro.
  7. Failed to execute the [excerpt-include] macro.
  8. Failed to execute the [excerpt-include] macro.


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.

Failed to execute the [excerpt-include] macro.

  1. Failed to execute the [excerpt-include] macro.
  2. Failed to execute the [excerpt-include] macro.

  3. Failed to execute the [excerpt-include] macro.

    Note

    You can ignore all the HA related settings for this procedure.

  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

  5. Failed to execute the [excerpt-include] macro.
  6. Failed to execute the [excerpt-include] macro.
  7. Failed to execute the [excerpt-include] macro.
  8. Failed to execute the [excerpt-include] macro.
  9. Failed to execute the [excerpt-include] macro.

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.

Failed to execute the [excerpt-include] macro.

  1. Failed to execute the [excerpt-include] macro.
  2. Failed to execute the [excerpt-include] macro.
  3. Failed to execute the [excerpt-include] macro.

  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=

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

  6. Failed to execute the [excerpt-include] macro.
  7. Failed to execute the [excerpt-include] macro.
  8. Failed to execute the [excerpt-include] macro.
  9. Failed to execute the [excerpt-include] macro.
  10. Failed to execute the [excerpt-include] macro.

Failed to execute the [excerpt-include] macro.

Failed to execute the [excerpt-include] macro.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*