Installing the BMC Application Diagnostics Agent by using interactive mode

The BMC Application Diagnostics Agent must be deployed and configured on the computer before being attached to the application server instance.

To install the BMC Application Diagnostics Agent by using the interactive mode

1. Download the BMC Application Diagnostics Agent from the Electronic Product Distribution site. See Downloading-the-installation-files.
2. Copy and extract the files to a temporary directory on the target computer, and navigate to the \agent folder.
3. Open a command shell, run the adops-agent-install.sh (for Linux) or adops-agent-install.bat (for Windows) command, and then press Enter.
   
   The script then prompts for configuration information. Some parameters have default values assigned.
4. Accept the defaults or enter the correct parameters. If the field is blank and you want to keep the default value, leave the field blank.
   1. Please enter destination directory into which the new Java Agent will be installed - Enter the directory where the BMC Application Diagnostics Agent will be installed. It will be created if it does not already exist. The default directory is the directory from which the installation script is run.
   2. Please specify a name for the monitored host (Application Server) which will be displayed by the GUI - Enter the host name, which is displayed in the BMC Application Performance Management Console as the application server’s display name. The default name used is the DNS host name.
   3. Please specify a name for the monitored Application which will be displayed by the GUI - Enter a name for the application, which is displayed in the description of this application server. The default is blank, and no application name will be displayed in the BMC Application Performance Management Console.
   4. Please specify BMC AD Portal host name or IP address - Enter the IP address or host name on which the BMC Application Diagnostics Portal is (or will be) installed. The default value is localhost.
   5. Please specify BMC AD Portal port number - Enter the BMC Application Diagnostics Portal HTTP port number. The default port is 8100.
   6. Please specify the HTTP proxy server host for outbound connection - Enter the HTTP proxy server host name or IP address, if applicable, or leave blank to indicate that no proxy will be used.
   7. Please specify the HTTP proxy server port for outbound connection - Only if you are using an HTTP proxy server, enter the HTTP proxy server port number.
   8. Please specify the HTTPS proxy server host for outbound connection - Enter the HTTPS proxy server host name or IP address, if applicable, or leave blank to indicate that no proxy will be used.
   9. Please specify the HTTPS proxy server port for outbound connection - Only if you are using an HTTPS proxy server, enter the HTTPS proxy server port number.
   10. Please specify the SOCKS proxy server host for outbound connection - Enter the SOCKS proxy server host name or IP address, if applicable, or leave blank to indicate that no proxy will be used.
   11. Please specify the SOCKS proxy server port for outbound connection - Only if you are using a SOCKS proxy server, enter the SOCKS proxy server port number.
5. The system displays the installation parameters. Verify that the displayed parameters reflect your installation correctly.
6. Enter Yes and press Enter to start the installation.
7. When the installation is complete, you are prompted to add the parameter to the JVM options of your application server. Add the parameter displayed on screen to the application server’s JVM options, for example:
   
   

   For Windows

   -javaagent:<InstallationDirectory>\ADOPsInstall__1_2\adops-agent.jar
   -Dcom.bmc.adops.agent.server.id="<uniqueID>"

   For Linux

   -javaagent:<InstallationDirectory>/ADOPsInstall__1_2/adops-agent.jar
   -Dcom.bmc.adops.agent.server.id="<uniqueID>"
   • Replace InstallationDirectory with the destination directory in which the BMC Application Diagnostics Agent was installed.
      The javaagent option is required to connect the BMC Application Diagnostics Agent to the JVM process. Enter the information that is relevant to your installation.
   • Replace uniqueID with the name given by the installer to identify the application server instance.
      Note that the -Dcom.bmc.adops.agent.server.id option can be removed if there is only one JVM process connected to an BMC Application Diagnostics Agent on the same computer. 

   • This parameter might need to be changed for each application server type.
     
     For more information about the correct locations for different application server types see Updating-the-Java-options-according-to-the-application-server-type. 

     Notes

     • The BMC Application Diagnostics Agent log file is named bmc_ad_agent_install.log and is created in the same folder as the installation script and the agentInstaller.jar file.
     • If you are working with WebSphere, Weblogic, and Glassfish application servers and the server ID was not provided, it will be automatically generated by the BMC Application Diagnostics Agent according to application server instance properties. For Tomcat and JBoss, you must either enter the unique instance ID for the application servers, or install a dedicated BMC Application Diagnostics Agent for each Tomcat or JBoss instance when installed in parallel with another application server on the same computer. View the defaults used in the logs located in <agent_installation_directory>/instances/default/logs.
8. If your application server is using Java 2 security, set Java 2 security options for application servers that have Java 2 security enabled. See Granting-Java-2-permissions-to-the-BMC-Application-Diagnostics-Agent.
9. Restart the application server or JVM process.

Where to go from here

1. Verify that the BMC Application Diagnostics Agent installation is successful.
2. Configure BMC Application Diagnostics in BMC Application Performance Management Console.