Installing the App Visibility server in the standalone mode silently

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. On the computer where you want to install the App Visibility portal, open the adop-silent-option file in edit mode.

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

5. Under the Install Features section, add a hash character (#) before the server components that you do not want to install, so that only the portal component is indicated for installation.

   # 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

6. Under the Portal Configuration section, enter the portal connection details.

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

   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	The App Visibility portal must use the default value, localhost.
   portal_communication_port	Listening port of the App Visibility portal 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. The default port is 8101.

7. 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 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 the portal database, 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.

   
   

8. Save and close the options file.

1. On the computer where you want to install the App Visibility collector, 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 the server components that you do not want to install, so that only the collector component is indicated for installation.

   # 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

4. Under the Portal Configuration section, enter the details to connect to the portal.

   Ensure that your firewall enables communication with the portal.

   The default values are displayed below:

   -J portal_ip=myPortalHost
   -J portal_communication_port=8100

   Parameter descriptions for the portal configuration

   Parameter	Description
   portal_ip	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. The default value is localhost.
   portal_communication_port	Listening port of the App Visibility portal If a load balancing server manages access to the portal, enter the port number of the load balancer. The default port is 8100.

5. 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. 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.
   
   The App Visibility components use this address to contact the computer on which you are installing.

   -J callback_address=

7. 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 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 collector database is deleted. The default time is 35 days. The delete 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 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.

8. Save and close the options file.

1. Encrypt a password to specify in the options file.

   The Maintenance Tool enables you to create an encrypted password, which the Diagnostic Server requires for importing a KeyStore. You must use an encrypted password so that the KeyStore password is not exposed in the adop-silent-option file.

   You can run the Maintenance Tool in a wizard interface or from the command-line interface (CLI).

    To encrypt a password by using the Maintenance Tool wizard

   1. To open the Maintenance Tool, go to the temporaryDirectory/Disk/utility directory where you downloaded the installation files.
   2. Run the ADOPServerMaintenanceTool utility and click the Encrypt tab.
   3. Enter your password in the Password and Confirm Password fields and click Encrypt.
   4. Copy and paste the value from the Encrypted Password field to the adop-silent-option file for the proxy_keystore_password_enc parameter.
      For example, if the encrypted password output is DES\:d70cbe3669602717ce66af37cce7ecf0, modify the proxy_keystore_password_enc parameter as follows:
      -J proxy_keystore_password_enc=DES\:d70cbe3669602717ce66af37cce7ecf0
    To encrypt a password by using a CLI

   1. To open the Maintenance Tool, go to the temporaryDirectory\Disk\utility directory where you downloaded the installation files.

   2. Run the following command, entering your password for the -password and -confirm_password options:

      • (Windows) ADOPServerMaintenanceTool.cmd -silent -encrypt -encrypt -password=<password> -confirm_password=<password>

      • (Linux) ./ADOPServerMaintenanceTool.sh -silent -encrypt -encrypt -password=<password> -confirm_password=<password> 

   3. Copy and paste the output to the adop-silent-option file for your silent installation.
      For example, if the encrypted password output is DES\:d70cbe3669602717ce66af37cce7ecf0, modify the proxy_keystore_password_enc parameter as follows:
      -J proxy_keystore_password_enc=DES\:d70cbe3669602717ce66af37cce7ecf0

2. On the computer where you want to install the App Visibility proxy, open the adop-silent-option file in edit mode.

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

4. Under the Install Features section, add a hash character (#) before the server components that you do not want to install, so that only the proxy component is indicated for installation.

   # 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

5. 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 your firewall enables communication with the portal from other components.

   The default values are displayed below:

   -J portal_ip=myPortalHost
   -J portal_communication_port=8100

   Parameter descriptions for the portal configuration

   Parameter	Description
   portal_ip	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. The default value is localhost.
   portal_communication_port	Listening port of the App Visibility portal If a load balancing server manages access to the portal, enter the port number of the load balancer. The default port is 8100.

6. 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 or replace the keystore after 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. 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 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. Save and close the options file.

1. In a command line window, navigate to the \ADOPServer\Disk1 folder in the installation file structure.
2. Run the silent installation of the App Visibility server with the following command:

   • (Windows) setup.exe -i silent -DOPTIONS_FILE=<fullFilePath>\adop-silent-option.txt

   • (Linux) ./setup.bin -i silent -DOPTIONS_FILE=<fullFilePath>/adop-silent-option

However, installation occurs in the background.

If the installation is successful, an indication is displayed in the command window.

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:
     For Collector and Portal
     
     • App Visibility Collector
     • App Visibility Portal
     • App Visibility PostgreSQL
     For Proxy
     
     • App Visibility Proxy
     • App Visibility Elasticsearch

   • (Linux) Run the following commands to verify that the processes are running:

     For Collector and Portal

     • ps -ea|grep adop_collectord

     • ps -ea|grep adop_portald

     • ps -ea|grep adop_apm_proxyd

     For Proxy

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