Performing the installation of the Diagnostics Agent for Java

Deploy and configure the BMC Application Diagnostics Agent for Java on the computer before connecting it to the application server instance. You can use the interactive installation mode, as described in this topic, or perform a silent installation.

Before you begin

Ensure that you have completed all tasks to prepare the environment for Agent installation.

To install the BMC Application Diagnostics Agent for Java

1. Copy and extract the files to a temporary directory on the target computer.

2. 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 prompts for configuration information. Some parameters have default values assigned.

   Tip

   Run the command adops-agent-install.sh -h (for Linux) or adops-agent-install.bat -h (for Windows) to see a description of all parameters.

3. Accept the defaults or enter the required parameters. If the field is blank and you want to keep the default value, leave the field blank.
4. The system displays the installation parameters. Verify that the displayed parameters reflect your installation correctly.
5. Enter Yes to continue and press the Enter key to start the installation.

To configure Java options

After you run the Diagnostics Agent for Java, configure Java options.

1. Add the BMC Application Diagnostics parameters to the JVM options of your application server. In a command line window, enter the following parameters for JVM options according to each application server type:

   • Windows

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

   • Linux
     

     -javaagent:<installationDirectory>/ADOPsInstall/adops-agent.jar
     -Dcom.bmc.adops.agent.server.id="<uniqueID>"

   Replace the variables as follows:

   • Replace <installationDirectory> with the destination directory in which the Diagnostics Agent was installed.
      The javaagent option is required to connect the Diagnostics Agent to the JVM process. Enter the information that is relevant to your installation.

   • Replace <uniqueID> with a unique name to identify the application server instance.You can remove the -Dcom.bmc.adops.agent.server.id option if there is only one JVM process connected to a Diagnostics Agent on the same computer.

     Notes

     • The 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 using JBoss, WebSphere, or WebLogic application servers, and the server ID was not provided, it is automatically generated by the BMC Application Diagnostics Agent according to application server instance properties.
     • If you are using a Tomcat application server, a default instance ID is used. If you have more than one application server, you must either enter a unique instance ID for each application server, or install a dedicated BMC Application Diagnostics Agent for each Tomcat instance that you install in parallel with another application server on the same computer. You can view the default IDs in the logs located in <agent_installation_directory>/instances/default/logs.
2. 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-Diagnostic-Agent.
3. Restart the application server or JVM process.

Where to go from here

Verify that the installation of the BMC Application Diagnostics Agent for Java is successful.

Configure BMC Application Diagnostics Portal in BMC Application Management Console, if you haven't already done so.

Logging-on-to-the-user-and-command-line-interfaces

Related topics

Installing-the-Diagnostics-Agent-for-NET

Changing-settings-of-the-Diagnostic-Agent-for-Java

Upgrading-the-Diagnostics-Agent-for-Java