Installing more than one App Visibility server component on the same computer

Where you are in the Installation process

StepTask
1Complete the planning activities
2Prepare for TrueSight Operations Management installation
3Install Remedy Single Sign-On
4Install TrueSight Presentation Server
5Install TrueSight Infrastructure Management (if licensed) 
6(Optional) Install TrueSight App Visibility Manager in a Test environment — Phase A Task 1 (You are here)
Install TrueSight App Visibility Manager — Phase B
7Install Real End User Experience Monitoring Software Edition (If licensed)
8Install TrueSight IT Data Analytics (If licensed)
9Complete the post-installation activities

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. 

Note

(For App Visibility proxy installation) 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..

Installing more than one component on the same computer using the wizard-based installer

 Click here to see the installing 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 the App Visibility server component or components that you want to install, and click Next:

    • Install BMC App Visibility Portal

    • Install BMC App Visibility Collector 

    • Install BMC App Visibility Proxy

    Note

    Installation configuration pages are displayed only for the selected component or components.

  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. (For portal installation) 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. (For collector installation) 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.

  11. (For App Visibility proxy installation)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 to help 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.

  12. (For App Visibility proxy installation) 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 post-installation.
      This option allows you to import or modify the keystore after installation.

  13. (For App Visibility collector or proxy installation without the portal) 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.
  14. (For collector or proxy installation) On the Listening Address Configuration page, confirm the address of the computer on which you are installing the App Visibility Manager components, and then click Next.

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

    Ensure that the address is accessible from other components. If you need to change the address after installation, see Changing App Visibility collector settings or Changing App Visibility proxy settings to change the callback.address property.
  16. (For portal or collector installation) 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.

  17. Preview the details, and click Install.

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

Installing more than one component on the same computer using the silent installer

 Click here to see the installing steps

Note

(For App Visibility proxy installation) 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. On the computer where you want to install one or more App Visibility server components, open the adop-silent-option file in edit mode.
  2. Specify a valid installation directory.

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

    -P installLocation=<directory>

    <directory> is the installation location.

    The following values are the default:

    • (Windows) -P installLocation=C:\Program Files\BMC Software\App Visibility  
    • (Linux) -P installLocation=/opt/bmc/App_Visibility

      Best practice

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

  3. Under the Install Features section, add a hash character (#) before any server component that you do not want to install, or before any component that is already installed.

    # Install App Visibility Portal
    -A bmc_application_diagnostics_portal
    # Install App Visibility Collector
    -A bmc_application_diagnostics_collector
    # Install App Visibility Proxy
    -A bmc_application_diagnostics_proxy

    Notes

    • Add a hash character before any component that is already installed on the computer; otherwise, the installation fails.
    • To set up an HA environment, you must install each App Visibility server component on a separate computer.
  4. Under the Portal Configuration section, enter the details to connect to the portal.

    You must provide App Visibility portal configuration details, even if you are not currently installing the portal component.

    Ensure that the App Visibility portal ports are available and can receive communication from the App Visibility agents. Specifically, ensure that your firewall enables communication with the portal.

    The default values are displayed below:

    -J portal_ip=localhost
    -J portal_communication_port=8100
    -J portal_integration_supportability_port=8101

    Parameter descriptions for the portal configuration

    Parameter

    Description

    portal_ip

    IP address or host name of the App Visibility portal

    The default value is localhost.

    • If you are installing the App Visibility portal, the value must be localhost.
    • If you are installing the App Visibility collector or the App Visibility proxy (without the App Visibility portal on the same computer), enter the host name or IP address of the portal.
      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 App Visibility portal

    If you are installing the App Visibility collector or the App Visibility proxy, and if a load balancing server manages access to the portal, enter the port number of the load balancer.

    The default port is 8100.

    portal_integration_supportability_port

    Listening port of the portal support console. A support console to help detect issues is automatically activated with one-way SSL authentication.

    This value is mandatory only if the App Visibility portal installation is part of the installation process.

    The default port is 8101.

  5. (For collector installation)  Modify the parameter values under the Collector Configuration section, as necessary.

    Ensure that the App Visibility collector ports are available and can receive communication from the App Visibility agents. Specifically, ensure that your firewall enables communication with the portal.

    The default values are displayed below:

    -J collector_communication_port=8200
    -J collector_supportability_port=8201

    Parameter descriptions for the collector configuration

    Parameter

    Description

    collector_communication_port

    Listening port of the App Visibility collector

    The default port is 8200.

    collector_supportability_port

    Listening port of the collector support console. A support console to help detect issues is automatically activated with one-way SSL authentication.

    The default port is 8201.

  6. (For proxy installation) Modify the parameter values under the Proxy Configuration section, as necessary.

    • If required, modify the port numbers for the relevant communication protocol. Ensure that the port numbers are available.

      -J proxy_communication_port=8300
      -J proxy_supportability_port=8301
      -J proxy_storage_http_port=8302
      -J proxy_storage_transport_port=8303
      -J proxy_beacon_receiver_http_port=8304
      -J proxy_beacon_receiver_https_port=8305
      -J proxy_storage_transport_ip=192.0.2.24

      Parameter descriptions for the proxy configuration

      Parameter

      Description

      proxy_communication_port

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

      The default port is 8300.

      proxy_supportability_port

      Listening port of the proxy support console. A support console to help detect issues is automatically activated with one-way SSL authentication.

      The default port is 8301.

      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_beacon_receiver_http_port

      Listening port of the beacon receiver for HTTP communication from the end-user's browser

      The default port is 8304.

      proxy_beacon_receiver_https_port

      Listening port of the beacon receiver for HTTPS communication from the end-user's browser

      The default port is 8305.

      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.

    • The App Visibility proxy requires a security certificate for use with SSL-encrypted beacons and injected requests. You can provide the location of the keystore file now, or you can import the keystore post-installation.

      -J import_proxy_keystore_now=false
      -J proxy_keystore_type=
      -J proxy_keystore_path=
      -J proxy_keystore_alias=
      -J proxy_keystore_password_enc=

      Parameter descriptions for the proxy keystore

      Parameter

      Description

      import_proxy_keystore_now

      If false (default), import the keystore post-installation.

      To import the keystore file now, set to true and provide values for the other parameters.

      proxy_keystore_type

      One of the following keystore types: JKS or PKCS12

      proxy_keystore_path

      Full path to the keystore, which must be on a local drive, including the file name and file extension

      If the path has spaces, enclose the entire path with quotation marks.

      proxy_keystore_alias Keystore alias

      proxy_keystore_password_enc

      Encrypted password, if one exists, from the Maintenance Tool.

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

  7. (For collector or proxy installation) Under the Address Configuration section, configure the listening address (host name or IP address) of the computer on which you are installing the App Visibility collector or proxy.

    The App Visibility components use this address to contact the computer on which you are installing.

    -J callback_address=

    Note

    Ensure that the address is accessible from other components. If you need to change the address after installation, see Changing App Visibility collector settings to change the callback.address property.

  8. (For portal or collector installation) Modify the parameter values under the Database Configuration section, as necessary.

    -J db_port=8800
    -J db_retention_time=35
    -J db_max_size=100

    Parameter descriptions for the portal or collector database

    Parameter

    Description

    db_port

    Listening port of the App Visibility database

    The default port is 8800.

    db_retention_time

    Number of days before the historical data on the App Visibility component database is overwritten.

    The default time is 35 days. The overwrite function launches automatically when the system reaches the specified retention time.

    db_max_size

    Maximum disk space allowed for data storage.

    The default size is 100 GB. For information about sizing considerations for components installed on the server, see Sizing App Visibility Manager and Synthetic TEA Agent components .

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

  9. (For portal or collector with high-availability installation) 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 that do not set an HA environment.

    -J ha_enabled=false
    -J ha_current_node_fqdn=
    -J ha_alternate_node_fqdn=
    -J ha_alternate_node_db_port=8800
    -J ha_node_synchronization_port=5701

    Parameter descriptions for the portal or collector's alternate component

    Parameter

    Description

    ha_enabled

    Set to true to enable HA component configuration.

    The default value is false.

    ha_current_node_fqdn

    FQDN of the current computer onto which you are installing the component

    ha_alternate_node_fqdn

    FQDN of the alternate component's computer

    ha_alternate_node_db_port

    Listening port that is used by the alternate component's App Visibility database

    The port must be the same number on the current and alternate nodes.

    The default port is 8800.

    ha_node_synchronization_port

    HA port that synchronizes data between the current and alternate nodes

    The port is dedicated for communication between nodes.

    The port must be the same number on the current and alternate nodes.

    The default port is 5701.

  10. (For collector, high-availability installation) Enter values for the load balancer that manages access to the collector: 

    -J ha_lb_host=myCollectorLoadBalancer
    -J ha_lb_port=2500

    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

    ha_lb_port

    Listening port of the load balancing server that manage access to the collector pair
  11. Save and close the options file.


 Example: Silent settings, installing all components together
-P installLocation=C:\Program Files\BMC Software\App Visibility
-A bmc_application_diagnostics_portal
-A bmc_application_diagnostics_collector
-A bmc_application_diagnostics_proxy
-J portal_ip=localhost
-J portal_communication_port=8100
-J portal_integration_supportability_port=8101
-J collector_communication_port=8200
-J collector_supportability_port=8201
-J db_port=8800
-J db_retention_time=35
-J db_max_size=100
-J proxy_communication_port=8300
-J proxy_supportability_port=8301
-J proxy_storage_http_port=8302
-J proxy_storage_transport_port=8303
-J proxy_beacon_receiver_http_port=8304
-J proxy_beacon_receiver_https_port=8305
-J proxy_storage_transport_ip=192.0.2.24
-J import_proxy_keystore_now=false
-J proxy_keystore_type=
-J proxy_keystore_path=
-J proxy_keystore_alias=
-J proxy_keystore_password_enc=
-J callback_address=myAppVisibilityServer-J ha_enabled=false
-J ha_current_node_fqdn=
-J ha_alternate_node_fqdn=
-J ha_alternate_node_db_port=8800
-J ha_node_synchronization_port=5701
-J ha_lb_host=
-J ha_lb_port=


 Example: Silent settings, App Visibility collector with HA

In this example, you install the App Visibility collector in an HA environment. For clarity, values that are not relevant to this installation are commented out.

-P installLocation=C:\Program Files\BMC Software\App Visibility
#-A bmc_application_diagnostics_portal
-A bmc_application_diagnostics_collector
#-A bmc_application_diagnostics_proxy
-J portal_ip=myAppVisibilityPortalLoadBalancer
-J portal_communication_port=8100
#-J portal_integration_supportability_port=8101
-J collector_communication_port=8200
-J collector_supportability_port=8201
-J db_port=8800
-J db_retention_time=35
-J db_max_size=100
#-J proxy_communication_port=8300
#-J proxy_supportability_port=8301
#-J proxy_storage_http_port=8302
#-J proxy_storage_transport_port=8303
#-J proxy_beacon_receiver_http_port=8304
#-J proxy_beacon_receiver_https_port=8305
#-J proxy_storage_transport_ip=192.0.2.24
#-J import_proxy_keystore_now=false
-J proxy_keystore_type=
-J proxy_keystore_path=
-J proxy_keystore_alias=
-J proxy_keystore_password_enc=
-J callback_address=myCollectorA.bmc.com
-J ha_enabled=true
-J ha_current_node_fqdn=myCollectorA.bmc.com
-J ha_alternate_node_fqdn=myCollectorB.bmc.com
-J ha_alternate_node_db_port=8800
-J ha_node_synchronization_port=5702
-J ha_lb_host=myCollectorLoadBalancer
-J ha_lb_port=2500

Related topic

To install the App Visibility server in the production environment, see Installing App Visibility Manager.

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

Comments