You can install the App Visibility server unattended (also called a silent installation). A silent installation, as described in this topic, requires no user interaction during installation. Alternatively, you can use the installation wizard.
The App Visibility server includes the following components: For details about the components, see Installing the App Visibility server components. Perform the following procedures to install the App Visibility server components. 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 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).
The following files are used to configure the silent installation of App Visibility server:
These files are located in the \ADOPServer\Disk1 folder in the installation file structure.
This topic presents the following sections:
Ensure that you have completed all preinstallation tasks. The App Visibility 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 the KeyStore requires a password, prepare an encrypted password with the Maintenance Tool.
Specify a valid installation directory for the App Visibility server:
-P installLocation=<directory>
<directory> is the installation location. Ensure that the specified directory is empty.
The following settings contain the default values:
-P installLocation=C:\Program Files\BMC Software\App Visibility
-P installLocation=/opt/bmc/App_Visibility
Under the Install Features section, add a hash tag (#) before a server component that you do not want to install, or before a 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
Note
Ensure that you add a hash tag before a component that is already installed; otherwise, the installation fails.
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.If required, modify the port numbers. 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.
-J portal_ip=localhost -J portal_communication_port=8100 -J portal_support_port=8101
Portal configuration parameter descriptions
Parameter | Description |
---|---|
portal_ip | IP address or host name of the App Visibility portal The default value is If you are installing the App Visibility portal, the value must be |
portal_communication_port | Listening port of the App Visibility portal The default port is 8100. |
portal_support_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. |
If required, modify the port numbers for the relevant communication protocol. Ensure that the App Visibility collector ports are available and can receive communication from the App Visibility agents. Specifically, ensure that your firewall enables this communication.
-J collector_communication_port=8200 -J collector_support_port=8201
Collector configuration parameter descriptions
Parameter | Description |
---|---|
collector_communication_port | Listening port of the App Visibility collector The default port is 8200. |
collector_support_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. |
(For portal or collector installation) Modify the database retention period (days), and database size (GB):
-J db_retention_time=35 -J db_max_size=100
Portal or Collector database parameter descriptions
Parameter | Description |
---|---|
db_retention_time | Number of days before which the historical data on the App Visibility collector database is overwritten. |
db_max_size | Maximum disk space allowed for data storage. When the database reaches the maximum size, historical data is overwritten, regardless of the value defined in the database retention time parameter. |
(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_support_port=8301 -J proxy_beacon_receiver_http_port=880 -J proxy_beacon_receiver_https_port=8444
Proxy configuration parameter descriptions
Parameter | Description |
---|---|
proxy_communication_port | Listening port of the proxy, communication from the portal and collector The default port is 8300. |
proxy_support_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_beacon_receiver_http_port | Listening port of the beacon receiver, HTTP communication from the end-user's browser The default port is 880. |
proxy_beacon_receiver_https_port | Listening port of the beacon receiver, HTTPS communication from the end-user's browser The default port is 8444. |
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_password_enc=
KeyStore parameter descriptions
Parameter | Description |
---|---|
import_proxy_keystore_now | If To import the KeyStore file now, set to |
proxy_keystore_type | Enter one of the following KeyStore types: |
proxy_keystore_path | Enter the full path to the KeyStore, which must be on a local drive. If the path has spaces, enclose it with quotation marks. |
proxy_keystore_password_enc | Enter an encrypted password, if one exists, from the Maintenance Tool. The KeyStore password cannot contain the following characters: | ^ ; " < > , |
(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.
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.
(For portal or collector installation) Under the Database Configuration section, configure the database by entering a port number for the App Visibility database that is created during the installation process.
If required, modify the port number for the relevant communication protocol. Ensure that the port numbers are available.The default port number is 8800.
-J db_port=8800
Windows
setup.exe -i silent -DOPTIONS_FILE=<fullFilePath>\adop-silent-option.txt
Linux
./setup.bin -i silent -DOPTIONS_FILE=<fullFilePath>/adop-silent-option
Notes
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 GUI or from the command line interface (CLI):
Verify that the App Visibility server installation is successful. Change the App Visibility database default password. If you did not import the KeyStore file during installation, import the KeyStore post-installation. Install the App Visibility agent for Java. Install the App Visibility agent for .NET. Install the BMC Synthetic Transaction Execution Adapter (TEA) Agent Add the App Visibility portal to the TrueSight Console. Importing a KeyStore file or replacing the certificateWhere to go from here
Related topics