Verifying the installation: agent for Java

You can verify that the BMC Application Diagnostics Agent for Java installation was successful, and that the agent for Java was invoked, by reviewing the log files created during installation. For assistance with issues that you cannot solve, contact BMC Support.

To review the installation logs

  1. Open the bmc_ad_agent_install.log file, located in the same directory from which you ran the BMC Application Diagnostics Agent installation script.
  2. Examine the log:
    • BMC Application Diagnostics Agent was installed successfully indicates the installation was successful.
    • Error messages can indicate incorrect privileges or write access. Ensure that you have Execute privileges on the installation scripts and write access to the installation location.
Example of a bmc_ad_agent_install.log
2012/06/04 13:20:26:583 IDT [INFO] com.bmc.aps.server.agentinstaller.se.AgentInstaller - Thread[main,5,main]4461550 -
------------------------------------------------------------------
BMC Application Diagnostics Agent was installed successfully.

Installation parameters summary:
    -destination            "c:\AgentInstall"
    -host                   "MyServer"
    -application            "MyApp"
    -portalIP               "localhost"
    -portalPort             "8100"
    -proxyHttpHost          ""
    -proxyHttpPort          ""
    -proxyHttpsHost         ""
    -proxyHttpsPort         ""
    -proxySocksHost         ""
    -proxySocksPort         ""

To run an application server with BMC-AD Java Agent, add the following
parameter to the JVM options of your application server:

-javaagent:c:\AgentInstall\ADOPsInstall\adops-agent.jar

* The -javaagent option is required to connect the Agent to the JVM process.

* A -Dcom.bmc.adops.agent.server.id=<uniqueID> option may be used. It is
  only needed when a single Agent installation directory is to serve multiple
  JVM processes, and only if Agent fails to generate a unique, persistent id
  per instance on its own. If provided, <uniqueID> should be unique per
  application server instance using an Agent on this machine (for example,
  server-name from server's start-script environment variables).

To verify that the agent for Java has been invoked

  1. Access the log files folder in the local installation directory, for example: C:\ADOPs\ADOPsInstall\instances\<instance_name>\logs
    The <instance_name> variable is the name that is generated dynamically during the Agent first start-up.
  2. Examine the aps_agent.log file.
    If the log file exists, the installation was successful.
    [ERROR] messages can indicate that the portal cannot be reached. Ensure that the portal address is correct and that a firewall is not blocking access.
  3. In the Diagnostics tab of BMC Application Performance Management Console, verify that data collection has begun.

Where to go from here

Configure BMC Application Diagnostics Portal in BMC Application Performance Management Console, if you haven't already done so.
Log on to the BMC Application Performance Management Console.

Related topics

Troubleshooting
Known-and-corrected-issues

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*