You can verify that the BMC Application Diagnostics Agent installation was successful, and the Java Agent was invoked, by reviewing the log files created during the BMC Application Diagnostics Agent installation.
To review the installation logs
- Access the bmc_ad_agent_install.log file, which can be found in the location from which you ran the BMC Application Diagnostics Agent installation script.
- In the log, verify whether any error messages were reported.
If there are no error messages, the installation was successful.
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 Java 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__1_2\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 Java Agent has been invoked
- Access the log files folder in the local installation directory, for example, C:\ADOPs\ADOPsInstall__1_2\instances\<instance_name>\logs where <instance_name> is the name that is generated dynamically during the Agent first start-up.
- Locate the aps_agent.log file.
- Verify that the Java Agent has been invoked.