Performing the App Visibility server installation silently
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.
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).
The following files are used to configure the silent installation of App Visibility server:
- (Windows) adop-silent-option.txt
- (Linux) adop-silent-option
These files are located in the \ADOPServer\Disk1 folder in the installation file structure.
This topic presents the following sections:
Before you begin
Note
- 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.
- (For portal and collector installation) Determine how much database space you need. For guidelines, see Sizing App Visibility Manager and Synthetic TEA Agent components.
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
If the keystore requires a password, prepare an encrypted password with the Maintenance Tool.
To set options for silent installation of the App Visibility portal
To set options for silent installation of an App Visibility collector
To set options for silent installation of an App Visibility proxy
To set options for silent installation of one or more App Visibility server components
Examples of App Visibility silent installation settings
To install the App Visibility server silently
- In a command line window, navigate to the \ADOPServer\Disk1 folder in the installation file structure.
- 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
- (Optional: Only for a HA setup) Repeat the above steps to install a secondary or standby App Visibility server.
(Optional: Only for a HA setup) After you install the Primary and Secondary App Visibility 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 server HA.
If the installation is successful, an indication is displayed in the command window.
Troubleshooting installation issues
- 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
- For more troubleshooting issues, see Troubleshooting an App Visibility Manager deployment
Encrypting a password for silent APM proxy installation
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).
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.
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.
Comments
Log in or register to comment.