Performing the Diagnostics Server installation
The BMC Application Diagnostics Server includes three components:
- One Application Diagnostics Portal component, which manages Diagnostics Collectors, the APM Proxy, and Diagnostics Agents, and collects relevant data to display in the Console. The application diagnostics environment uses only one Portal component.
- One or more Application Diagnostics Collector components, which communicates with one or more Diagnostics Agents and stores the information for the monitored application. The application diagnostics environment uses one or more Collector components. You can install the component on a computer that does not have a Diagnostics Portal installation.
One
APM Proxy
(required for active end-user monitoring only), receives and processes end-user experience data. To collect end-user metrics with the APM mode, you must install the APM Proxy. The application diagnostics environment uses only one APM Proxycomponent and you can install it on a computer that does not have a Diagnostics Portal installation.
Perform this procedure to install all the Diagnostics Server components on one computer, for a small environment, or each component on separate computers, such as for larger environments with several Diagnostics Collectors. When the Diagnostics Portal and Collector components are installed on the same computer, they share the same database.
You can use the installation wizard, as described in this topic, or perform a silent installation.
Before you begin
Ensure that you have completed all preinstallation tasks.
If you are installing the APM Proxy, you must have a KeyStore certificate and its password in clear text.
To install the Diagnostics Server
- On the computer where you want to install one or more Diagnostics Server components, launch the installation wizard:
Windows
Navigate to ADOPServer\Disk1 and double-click setup.cmd. In Windows 2008, the system may require you to right-click the setup.cmd icon to select to Run as administrator.
- Linux
- Ensure that you have set the DISPLAY environment variable.
- Navigate to ADOPServer/Disk1 and run setup.sh.
- In the Diagnostics 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 will end.
Select the Diagnostics Server component or components that you want to install, and then click Next:
- Application Diagnostics Portal
- Application Diagnostics Collector
- APM Proxy
On the Directory Selection page, the system displays the available space on the current drive and the amount of space required.
In the Destination Directory box, enter the path for the installation directory or click Browse to select a directory, and then click Next.
Ensure that the directory is empty.
Windows
Default directory: C:\Program Files\BMC Software\BMC Application Diagnostics
Linux
Default directory: /opt/bmc/BMC_Application_Diagnostics
(For Portal installation) On the Portal Configuration page, define the following options, and then click Next.
Ensure that the port you enter is available.(For Collector installation) On the Collector Configuration page, provide the following system connection information and then click Next.
Ensure that the port you enter is available.(For Collector installation) If you are installing the Diagnostics Collector on a computer that does not have a Diagnostics Portal installation, the Diagnostics Portal connection information is required.
(For APM Proxy installation) On the Proxy Configuration page, provide the following port numbers and then click Next.
Ensure that the port you enter is available.- (For APM Proxy installation) On the Proxy KeyStore Configuration page, choose an import option:
- 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.
- Click Next.
- Import the KeyStore post-installation.
- Import the KeyStore file now:
(For APM Proxy installation) If you are installing the APM Proxy on a computer that does not have a Diagnostics Portal installation, the Diagnostics Portal connection information is required.
On the Listening Address Configuration page, confirm the address of the computer on which you are installing the Diagnostics Server component or components.You can either 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 application diagnostics components use this address to connect to the computer on which you are installing.
- (For Portal or Collector installation) On the Database Setup page, enter the database port number.
The default port is 3301. A new database is created under the installationDirectory\ADOP_DB directory. (For Portal or Collector installation) Enter the following values in the Database Configuration page.
- Verify that the information on the Installation Preview page reflects your installation correctly. 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 Diagnostics Server components to use an IP address to connect to one another, you must override the default host name configuration. The following links provide instructions:
Where to go from here
Verify that the BMC Application Diagnostics Server installation is successful.
Change the MySQL root password.
Install the BMC Application Diagnostics Agent for Java.
Install the BMC Application Diagnostics Agent for .NET.
Configure the BMC Application Management Console.
Related topic
Importing-a-KeyStore-file-to-replace-the-self-signed-certificate