Installing the App Visibility server in the standalone mode using the wizard


Where you are in the Installation process

Step Task
1 Complete the planning activities
2 Prepare for TrueSight Operations Management installation
3 Install Remedy Single Sign-On
4 Install TrueSight Presentation Server
5 Install TrueSight Infrastructure Management (if licensed) 
6 Install TrueSight App Visibility Manager Phase A (You are here)
Install TrueSight App Visibility Manager — Phase B
7 Install Real End User Experience Monitoring Software Edition (If licensed)
8 Install TrueSight IT Data Analytics (If licensed)
9 Complete the post-installation activities
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 most 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).

Install the portal before the other server components because the collector and proxy reference the portal during installation. The App Visibility agents also reference the portal during installation. 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.

You can install 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.

Install each proxy 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 proxy uses SSL-encrypted beacons and injection requests, and therefore, requires a KeyStore with a certificate that is trusted by the end-users’ browsers. You can import the KeyStore during proxy installation or after installation.


Note

If you have one or more App Visibility server components from an earlier version, upgrade the earlier components before you install new components.

(For proxy installation) 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 installation or after installation.
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 install the App Visibility portal

  Click here to see the installation 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. (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
    export DISPLAY=<IP address of the host computer>:0.0

  4. Run the installer:

    • (Windows) Right-click setup.exe and select Run as administrator.

    • (Linux) Run setup.bin.

  5. Review the Welcome page, and click Next.

  6. Read the license agreement, agree to the terms, and click Next

  7. On the feature selection page, select Install BMC App Visibility Portal, and click Next.

  8. Enter the path for the installation directory or retain the default, and click Next.

    Ensure that the specified directory has no files or folders in it and that the directory path uses only ASCII characters.

    • (Windows) Default directory: C:\Program Files\BMC Software\App Visibility

    • (Linux) Default directory: /opt/bmc/App_Visibility

      Best practice

      On Linux computers, use the default installation directory or you might experience issues related to permissions and access.

  9. Specify available ports for the App Visibility portal to receive communication from the App Visibility agents. Specifically, ensure that your firewall enables this communication. Note down the port numbers as you will need to type them while installing the App Visibility collector and App Visibility proxy, and click Next.

    • Listening communication port of the App Visibility portal. The default port is 8100.
    • Listening supportability port of the portal support console.
      A support console, which helps detect issues, is automatically activated with one-way SSL authentication. The default port is 8101.

  10. Type the database configuration values, and click Next.

    • Listening database port of the App Visibility portal database
      The new database is created under the installationDirectory\ADOP_DB directory. The default port is 8800. If you change this, ensure that the port number is available.

    • Number of days before the historical data on the App Visibility portal database is deleted
      The delete function launches automatically when the system reaches the specified retention time. The default time is 35 days.
      Note: This is value is important to help manage the size of your database. 

    • Maximum disk space allowed for data storage
      The default size is 100 GB.

  11. Preview the details, and click Install.

  12. After the installation is complete, click View Log to view the installation log files.
    You can also navigate to the following default location for logs:

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

  13. Click Done to exit the installation wizard.

To install an App Visibility collector

  Click here to see the installation 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. (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
    export DISPLAY=<IP address of the host computer>:0.0

  4. Run the installer:

    • (Windows) Right-click setup.exe and select Run as administrator.

    • (Linux) Run setup.bin.

  5. Review the Welcome page, and click Next.

  6. Read the license agreement, agree to the terms, and click Next

  7. On the feature selection page, select Install BMC App Visibility Collector, and click Next.

  8. Enter the path for the installation directory or click Browse and then click Next.

    Ensure that the specified directory has no files or folders in it and that the directory path uses only ASCII characters.

    • (Windows) Default directory: C:\Program Files\BMC Software\App Visibility

    • (Linux) Default directory: /opt/bmc/App_Visibility

      Best practice

      On Linux computers, use the default installation directory or you might experience issues related to permissions and access.

  9. Specify available ports for the App Visibility collector to receive communication from the App Visibility agents. Specifically, ensure that your firewall enables this communication, and click Next.

    • Listening communication port of the App Visibility collector. The default port is 8200.

    • Listening supportability port of the collector support console.
      A support console, which helps detect issues, is automatically activated with one-way SSL authentication. The default port is 8201.

  10. If you install the App Visibility collector on a computer that does not have an App Visibility portal installation, enter the App Visibility portal connection information, click Test Connection to check communication with the portal, and click Next.

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

    • Listening port of the portal
      If a load balancing server manages access to the portal, enter the port number of the load balancer. The default value is 8100.

  11. On the Listening Address Configuration page, confirm the address of the computer on which you are installing the App Visibility collector, and click Next.

    Accept the default address that is received from the operating system, or change the default address to the host name or IP address of the computer on which you are installing. App Visibility Manager components use this address to communicate with the component you are installing. Other services that need to access this component, such as a load balancing server, must also use this address.

  12. Type the database configuration values, and click Next.

    • Listening database port of the App Visibility portal database
      The new database is created under the installationDirectory\ADOP_DB directory. The default port is 8800. If you change this, ensure that the port number is available.

    • Number of days before the historical data on the App Visibility portal database is deleted
      The delete function launches automatically when the system reaches the specified retention time. The default time is 35 days.
      Note: This is value is important to help manage the size of your database. 

    • Maximum disk space allowed for data storage
      The default size is 100 GB. For information about sizing considerations for the collector database, see Sizing App Visibility Manager and Synthetic TEA Agent components .

      When the database reaches the maximum size, historical data is deleted, regardless of the value defined in the database retention time parameter.

  13. Preview the details, and click Install.

  14. After the installation is complete, click View Log to view the installation log files.
    You can also navigate to the following default location for logs:

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

  15. Click Done to exit the installation wizard.

To install an App Visibility proxy

  Click here to see the installation steps

Note

The installation 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 install the Proxy without testing connectivity (not recommended), run the installation 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 installation process, and restart all the cluster nodes for the storage engines.

  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. (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
    export DISPLAY=<IP address of the host computer>:0.0

  4. Run the installer:

    • (Windows) Right-click setup.exe and select Run as administrator.

    • (Linux) Run setup.bin.

  5. Review the Welcome page, and click Next.

  6. Read the license agreement, agree to the terms, and click Next.

  7. On the feature selection page, select Install BMC App Visibility Proxy, and click Next.

  8. Enter the path for the installation directory or retain the default, and click Next.

    Ensure that the specified directory has no files or folders in it and that the directory path uses only ASCII characters.

    • (Windows) Default directory: C:\Program Files\BMC Software\App Visibility

    • (Linux) Default directory: /opt/bmc/App_Visibility

      Best practice

      On Linux computers, use the default installation directory or you might experience issues related to permissions and access.

  9. Specify available ports for the App Visibility proxy to receive communication from the App Visibility agents. Specifically, ensure that your firewall enables this communication, and click Next.

    Option

    Description

    Proxy Communication Port

    Listening port of the proxy, communication from the portal and collector

    The default port is 8300.

    Supportability Port

    Listening port of the proxy support console

    A support console, which helps detect issues, is automatically activated with one-way SSL authentication.

    The default port is 8301.

    Storage HTTP Port

    Listening port of the App Visibility proxy storage engine

    The default port is 8302.

    Storage Transport Port

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

    The default port is 8303.

    Beacon Receiver HTTP Port

    Listening port of the beacon receiver, HTTP communication from the end users' browsers

    The default port is 8304.

    Beacon Receiver HTTPS Port

    Listening port of the beacon receiver, HTTPS communication from the end users' browsers

    The default port is 8305.

    Storage Transport IP Address

    Used for communication between the different nodes in the storage cluster

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

    The default IP address is the first received by the system.


  10. On the Proxy KeyStore Configuration page, choose an import option, and then click Next:

    • Import the keystore file now:
      1. Ensure that Import KeyStore file now is selected.

      2. Select the keystore type: JKS or PKCS12.

      3. Enter the keystore alias.

      4. Enter the keystore password, if one exists.

        The keystore password cannot contain the following characters: | ^ ; " < > ,

      5. Enter the full path or browse to the location of the keystore file.

    • Import the KeyStore after installation.
      This option allows you to
      Error rendering macro 'link-window' : [com.ctc.wstx.exc.WstxLazyException] Duplicate attribute 'a'. at [row,col {unknown-source}]: [4,138]
      .

  11. If you are installing the App Visibility proxy on a computer that does not have an App Visibility portal installation, enter the App Visibility portal connection information, and click Next.

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

    • Listening port of the portal
      If a load balancing server manages access to the portal, enter the port number of the load balancer. The default value is 8100.

  12. On the Listening Address Configuration page, confirm the address of the computer on which you are installing the App Visibility proxy, and then click Next.

    Accept the default address that is received from the operating system, or change the default address to the host name or IP address of the computer on which you are installing. The App Visibility Manager components use this address to contact the computer on which you are installing.

    Note

  13. Preview the details, and click Install.

  14. After the installation is complete, click View Log to view the installation log files.
    You can also navigate to the following default location for logs:

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

  15. Click Done to exit the installation wizard.

To verify the App Visibility server installation

  Click here to see the steps
  1. Access the adopserver_install_log file:
    (Windows%temp%
    (Linux) /tmp
  2. Check for warnings or errors. 
    If no error messages are present, the installation was successful.
  3. According to what you installed, verify that the App Visibility server components are running:

    • (Windows) Run services.msc and verify that the services are running:
      • App Visibility Collector
      • App Visibility Portal
      • App Visibility PostgreSQL
      • App Visibility Proxy
      • App Visibility Elasticsearch
    • (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

      • ps -ea|grep apm_elasticsearch

  4. Check for errors reported in the App Visibility log files in the following locations:

    • Windows
      • server_installationDirectory\collector\logs\collector.log
      • server_installationDirectory\portal\logs\portal.log
      • server_installationDirectory\apm-proxy\logs\apm-proxy.log
    • Linux
      • server_installationDirectory/collector/logs/collector.log
      • server_installationDirectory/portal/logs/portal.log
      • server_installationDirectory/apm-proxy/logs/apm-proxy.log

    Note

    If a network port is occupied, the App Visibility server component stops, as reflected in the component log, but the log message does not give the reason.

To configure the network settings

  Click here to expand

As the system administrator, configure your network to ensure that the App Visibility proxy can collect end-user browser data, and pass it on to the App Visibility collector and portal.

After you install the App Visibility server components, configure the following properties for the portal and the proxy: 

  • collectors.load.balancer.address. If the App Visibility portal and App Visibility collector are behind a load balancing or reverse proxy server, update the value of this property value to redirect App Visibility agent communication through the intermediary server and forward requests to the assigned App Visibility collectors. For instructions, see  Changing App Visibility portal settings
  • callback.address. If the App Visibility proxy that is behind a load balancing or reverse proxy server, update the value of this property to redirect end-user browser data through the intermediary server and forward requests to the App Visibility proxy. For instructions, see  Changing App Visibility proxy settings .

Details about configuring load balancing servers varies among vendors. To properly configure your load balancing server, refer to your vendor's documentation.

Troubleshooting installation issues

If you face issues during installation, see Troubleshooting the App Visibility Manager deployment

Next step in the Installation process

Step 6 Phase B Task 1 — Now that you have successfully installed the App Visibility server, you must install the applicable App Visibility agent.

Was this page helpful? Yes No Submitting... Thank you

Comments