To install the App Visibility server components, you can use the installation wizard, as described in this topic. Alternatively, you can perform a silent installation (also called an unattended installation), which requires no user interaction during installation and can be deployed over several computers at once.
Optionally, you can install with high-availability (HA) redundancy; see App Visibility Manager high-availability deployment. In an HA environment, you install a component on one computer, and its alternate component on an identical computer.
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 description about the function of each component, see Installing the App Visibility server components.
Perform the procedures in this topic 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). In a high-availability deployment, the portal and collector components are installed in pairs: one active node and standby node for the portal (each on a separate computer); one or more pairs of active and standby nodes for the collectors (each on a separate computer).
This topic presents the following sections:
Before you begin
Note
If you have one or more App Visibility server components from an earlier version, upgrade the earlier components before you install new components.
- Complete all preinstallation tasks.
- (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. - (For collector and proxy installation) You must have the host name or IP address, and the port number, of the portal. If a load balancing server manages access to the portal, use the information of the load balancer.
For a high-availability environment
Before you install high-availability components for the App Visibility portal, collector, or both, set up the required third-party load balancing server or servers. When you install the App Visibility components, you must have the following information:
- For portal installation
- Fully qualified domain name (FQDN) and port number of the computer that has the alternate portal node
- Database port that is used by the alternate portal node's App Visibility database
- For collector installation
- App Visibility portal load balancer host name or IP address, and port number
- Fully qualified domain name (FQDN) and port number of the computer that has the alternate collector node
- Database port that is used by the alternate collector node's App Visibility database
- Host name or IP address, and the port number, of the HA load balancer that manages access to the collector pair
- For proxy installation
- App Visibility portal load balancer host name or IP address, and port number
To install the App Visibility portal
- Copy and extract the downloaded files to a temporary directory on the target computer.
- Launch the installation wizard:
(Windows)
Double-click setup.exe.
In Windows 2008, you might need to right-click the setup.exe icon and select Run as administrator.- (Linux)
Ensure that you have set the DISPLAY environment variable.
Run setup.bin.
- On the App Visibility Server Installer Welcome page, click Next.
- On the License Agreement page, read the agreement and select the I agree to the terms of the license agreement option, and then click Next.
If you do not agree to the terms of the license agreement, the installation process ends. On the feature selection page, select Install BMC App Visibility Portal and then click Next.
On the Directory Selection page, enter the path for the installation directory or click Browse and then click Next.
Ensure that the specified directory is empty 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.
On the Portal Configuration page, define the following options and then click Next.
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.
Option
Description
Portal Connection Communication Port
Listening port of the App Visibility portal
The default port is 8100.
Supportability Port Listening 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.
Enter the following values on the Database Configuration page and then click Next.
Ensure that the port number is available.
Option
Description
Database Port Listening port of the App Visibility portal database
The new database is created under the installationDirectory\ADOP_DB directory.
The default port is 8800.
Data Retention Time (days)
Number of days before which the historical data on the App Visibility portal database is overwritten
The overwrite function launches automatically when the system reaches the specified retention time.
The default time is 35 days
Maximum Data Storage (GB)
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 information about sizing considerations for components installed on the server, see Sizing App Visibility Manager and Synthetic TEA Agent components.
The default size is 100 GB.
To set up a high-availability environment, select Enable High Availability and enter the following values.
Ensure that all port numbers are available.
Option
Description
Current HA Node Information Node FQDN
Fully-qualified domain name (FQDN) of the current computer onto which you are installing the component
The FQDN of the current computer is automatically entered; ensure that it is accessible from other components.
Node Port
HA control port of the current component
The port is dedicated for communication between nodes.
The default port is 8102.
Alternate HA Node Information Node FQDN
FQDN of the alternate component's computer; ensure that it is accessible from other components
Note: The values for the Current Node FQDN and Alternate Node FQDN are case sensitive. Use only either an upper or lower case FQDN values.
Node Port
HA control port of the alternate component
The port is dedicated for communication between nodes.
The default port is 8102.
Database Port Listening port that is used by the alternate component's App Visibility database
The default port is 8800.
Sample values for current and alternate HA portal nodes
Verify that the information on the Installation Preview page reflects your installation correctly and click Previous to make changes, or click Install.
- After the installation is complete, click View Log to view the installation log files and confirm that the installation process was successful.
- Click Done to exit the installation wizard.
- If the operating system's host name is incorrect or you want the App Visibility portal to use an IP address to connect to other components, change the host name for communication with the portal.
- After you install the Primary and Secondary App Visibility Portal servers, you must configure the Load Balancer.
For the steps to configure a Load Balancer, you must contact your local Load Balancer administrator and provide the active and standby node details of the App Visibility Portal HA.
To install an App Visibility collector
- Copy and extract the downloaded files to a temporary directory on the target computer.
- Launch the installation wizard:
(Windows)
Double-click setup.exe.
In Windows 2008, you might need to right-click the setup.exe icon and select Run as administrator.- (Linux)
Ensure that you have set the DISPLAY environment variable.
Run setup.bin.
- On the BMC TrueSight App Visibility Manager Server Installer Welcome page, click Next.
- On the License Agreement page, read the agreement and select the I agree to the terms of the license agreement option, and then click Next.
If you do not agree to the terms of the license agreement, the installation process ends. On the feature selection page, select Install BMC App Visibility Collector and then click Next.
On the Directory Selection page, enter the path for the installation directory or click Browse and then click Next.
Ensure that the specified directory is empty 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.
On the Collector Configuration page, provide the following system connection information and then click Next.
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.
Option
Description
Communication Port
Listening port of the App Visibility collector
The default port is 8200.
Supportability Port Listening 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.
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 then click Next.
Option
Description
Portal Host Name or IP
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.
Portal Port
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.
On the Listening Address Configuration page, confirm the address of the computer on which you are installing the App Visibility collector, 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. 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.
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.
Enter the following values on the Database Configuration page.
Ensure that the port number is available.
Option
Description
Database Port Listening port of the App Visibility collector database
The new database is created under the installationDirectory\ADOP_DB directory.
The default port is 8800.
Data Retention Time (days)
Number of days before which the historical data on the App Visibility collector database is overwritten
The overwrite function launches automatically when the system reaches the specified retention time.
The default time is 35 days.
Maximum Data Storage (GB)
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 information about sizing considerations for components installed on the server, see Sizing App Visibility Manager and Synthetic TEA Agent components.
The default size is 100 GB.
To set up a high-availability environment, select Enable High Availability and and enter the following values.
Ensure that all port numbers are available.
Option
Description
Current HA Node Information Node FQDN
Fully-qualified domain name (FQDN) of the current computer onto which you are installing the component
The FQDN of the current computer is automatically entered; ensure that it is accessible from other components.
Node Port
HA control port of the current component
The port is dedicated for communication between nodes.
The default port is 8202.
Load balancing server that manages access to the collector Load Balancer Host Name Host name or IP address of the load balancing server that manages access to the collector Load Balancer Port Listening port of the load balancing server that manages access to the collector On the next page of the HA configuration, enter details for the alternate node:
Option
Description
Alternate HA Node Information Node FQDN
FQDN of the alternate component's computer; ensure that it is accessible from other components
Note: The values for the Current Node FQDN and Alternate Node FQDN are case sensitive. Use only either an upper or lower case FQDN values.
Node Port
HA control port of the alternate component
The port is dedicated for communication between nodes.
The default port is 8202.
Database Port Listening port that is used by the alternate component's App Visibility database
The default port is 8800.
Sample values for current and alternate HA collector nodes
Verify that the information on the Installation Preview page reflects your installation correctly and click Previous to make changes, or click Install.
- After the installation is complete, click View Log to view the installation log files and confirm that the installation process was successful.
- Click Done to exit the installation wizard.
- If the operating system's host name is incorrect or you want the App Visibility collector to use an IP address to connect to other components, see Changing App Visibility collector settings .
To install an App Visibility proxy
- Copy and extract the downloaded files to a temporary directory on the target computer.
- Launch the installation wizard:
(Windows)
Double-click setup.exe.
In Windows 2008, you might need to right-click the setup.exe icon and select Run as administrator.- (Linux)
Ensure that you have set the DISPLAY environment variable.
Run setup.bin.
- On the BMC TrueSight App Visibility Manager Server Installer Welcome page, click Next.
- On the License Agreement page, read the agreement and select the I agree to the terms of the license agreement option, and then click Next.
If you do not agree to the terms of the license agreement, the installation process ends. On the feature selection page, select Install BMC App Visibility Proxy and then click Next.
On the Directory Selection page, enter the path for the installation directory or click Browse and then click Next.
Ensure that the specified directory is empty 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.
On the Proxy Configuration page, provide the following port numbers and then click Next.
Ensure that the port numbers are available.
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.
Beacon Receiver HTTP Port
Listening port of the beacon receiver, HTTP communication from the end users' browsers
The default port is 880.
Beacon Receiver HTTPS Port
Listening port of the beacon receiver, HTTPS communication from the end users' browsers
The default port is 8444.
On the Proxy KeyStore Configuration page, choose an import option, and then click Next:
- Import the KeyStore file now:
Ensure that Import KeyStore file now is selected.
Select the KeyStore type: JKS or PKCS12.
Enter the KeyStore password, if one exists.
The KeyStore password cannot contain the following characters: | ^ ; " < > ,
Enter the full path or browse to the location of the KeyStore file.
Import the keystore after installation.
JavaScript fetch is used to collect end-user metrics. If your application web pages are only HTTP, 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.
- Import the KeyStore file now:
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 then click Next.
Option
Description
Portal Host Name or IP
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.
Portal Port
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.
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
Ensure that the address is accessible from other components. If you need to change the address after installation, see Changing App Visibility proxy settings to change the callback.address property.
Verify that the information on the Installation Preview page reflects your installation correctly and click Previous to make changes, or click Install.
- After the installation is complete, click View Log to view the installation log files and confirm that the installation process was successful.
- Click Done to exit the installation wizard.
- If the operating system's host name is incorrect or you want the App Visibility proxy to use an IP address to connect to other components, see Changing App Visibility proxy settings.
To install more than one App Visibility server component
- Copy and extract the downloaded files to a temporary directory on the target computer.
- Launch the installation wizard:
(Windows)
Double-click setup.exe.
In Windows 2008, you might need to right-click the setup.exe icon and select Run as administrator.- (Linux)
Ensure that you have set the DISPLAY environment variable.
Run setup.bin.
- On the BMC TrueSight App Visibility Manager Server Installer Welcome page, click Next.
- On the License Agreement page, read the agreement and select the I agree to the terms of the license agreement option, and then click Next.
If you do not agree to the terms of the license agreement, the installation process ends. On the feature selection page, select the App Visibility server component or components that you want to install, and then 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.On the Directory Selection page, enter the path for the installation directory or click Browse and then click Next.
Ensure that the specified directory is empty 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.
(For portal installation) On the Portal Configuration page, define the following options, and then click Next.
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.
Option
Description
Portal Connection Communication Port
Listening port of the App Visibility portal
The default port is 8100.
Supportability Port Listening 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.
(For collector installation) On the Collector Configuration page, provide the following system connection information and then click Next.
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.
Option
Description
Communication Port
Listening port of the App Visibility collector
The default port is 8200.
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.
(For App Visibility proxy installation) On the Proxy Configuration page, provide the following port numbers and then click Next.
Ensure that the port numbers are available.
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.
Beacon Receiver HTTP Port
Listening port of the beacon receiver, HTTP communication from the end users' browsers
The default port is 880.
Beacon Receiver HTTPS Port Listening port of the beacon receiver, HTTPS communication from the end users' browsers
The default port is 8444.
(For App Visibility proxy installation) On the Proxy KeyStore Configuration page, choose an import option, and then click Next:
- Import the KeyStore file now:
Ensure that Import KeyStore file now is selected.
Select the KeyStore type: JKS or PKCS12.
Enter the KeyStore password, if one exists.
The KeyStore password cannot contain the following characters: | ^ ; " < > ,
Enter the full path or browse to the location of the KeyStore file.
Import the keystore post-installation.
JavaScript fetch is used to collect end-user metrics. If your application web pages are only HTTP, 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.
- Import the KeyStore file now:
(For App Visibility collector or proxy installation) If you are installing the App Visibility collector, the proxy, or both on a computer that does not have the App Visibility portal installation, enter the App Visibility portal connection information, click Test Connection to check communication with the portal, and then click Next.
Option
Description
Portal Host Name or IP
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.
Portal Port
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.
(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.
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.(For portal or collector installation) Enter the following values in the Database Configuration page and then click Next.
Ensure that the port number is available.
Option
Description
Database Port Listening port of the App Visibility portal database
The new database is created under the installationDirectory\ADOP_DB directory.
The default port is 8800.
Data Retention Time (days)
Number of days before which the historical data on the App Visibility collector database is overwritten
The overwrite function is automatically launched when the system reaches the specified retention time.
The default time is 35 days.
Maximum Data Storage (GB)
Maximum disk space allowed for data storage
When the database reaches the maximum size, historical data will be overwritten regardless of the value defined in the database retention time parameter.
Note: The wizard validates the space available on the installation directory and displays a validation error if there is insufficient space.
For information about sizing considerations for components installed on the server, see Sizing App Visibility Manager and Synthetic TEA Agent components.
The default size is 100 GB.
Verify that the information on the Installation Preview page reflects your installation correctly and click Previous to make changes, or click Install.
- After the installation is complete, click View Log to view the installation log files and confirm that the installation process was successful.
- Click Done to exit the installation wizard.
- (Optional) If the operating system's host name is incorrect or you want the App Visibility Manager components to use an IP address to communicate with other components, override the default host name configuration. The following links provide instructions:
Notes
- If the installation fails, you must run the uninstallation process before re-running the installation. For more information about the uninstall process, see Uninstalling the App Visibility server.
- The App Visibility server log files are located in the following directories:
- (Windows) %temp%\adopserver_install_log.txt
- (Linux) /tmp/adopserver_install_log.txt
Where to go from here
Verify that the App Visibility server installation is successful.
(For high availability) Follow the installation instructions again to install the alternate node for HA components. After both nodes are installed, configure the components in the load balancer.
(For App Visibility proxy) Import the keystore for after installation for the App Visibility proxy. If your application web pages are only HTTP, you can
change the protocol
to work with HTTP, instead of the default HTTPS. With HTTP, you do not need to import a keystore file.
(For Fix Pack 1) To install the Fix Pack on the App Visibility server, go to
10.5.00.001: Fix Pack 1 – App Visibility Manager
.
For further details about integrated products in Fix Pack 1, see 10.5.00.001: Fix Pack 1.
Install agents:
- App Visibility agent for Java
- App Visibility agent for .NET
- BMC Synthetic Transaction Execution Adapter (TEA) Agent
Add the App Visibility portal to the TrueSight Console.
Related topics
App Visibility installation components overview
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
8 Comments
Raynald Cuillerier
Hello,
Could you explain what is the Load Balancer Port "2500" used for Collector HA installation ?
Why this number ?
Thx.
Sara Kamen
Hi Raynald,
Thanks for asking.
The Load Balancer Port is the listening port of the load balancing server that manages access to the collector. The port value in the screenshot is a sample and would depend on how your load balancer is configured.
I added a title to the screenshots, "Sample values for current and alternate HA collector nodes," which I hope clarifies that the values are sample values. Please let me know if you need anything else.
Regards,
Sara
Mohamed Eraky
Hello ,
Can i increase the Data Retention Time (days) to be equal 3 months .
and this will save data from all agents for example from synthetic also .
I need to increase the data storage also if i increase data retention time ?
For Example : if i have 10 agents and the data storage for these agents is 100 GB for 35 Days.
if i increased the Data Retention Time to be 105 Days so i need to increase storage also to be 300 GB for 3 months .
Benjie Wolicki
Hi Mohamed,
Yes, you can increase data retention to be equal to 3 months, just remember that the parameter is in days.
Data retention applies to all data regardless of which kind of agent it came from (.Net, Java, and TEA).
As you say, it would definitely be advisable to increase your data storage in accordance with your increase of data retention.
Winsor Lim
Harihara Subramanian
Winsor Lim
Harihara Subramanian