You can verify that the installation of an App Visibility agent for Java was successful, and that the agent 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, which is usually located in the same folder as the installation script and the agentInstaller.jar.
  2. Examine the log:
    • App Visibility Agent for Java 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

2014/12/30 13:20:26:583 CT [INFO] com.bmc.aps.server.agentinstaller.se.AgentInstaller - Thread[main,5,main]4461550 -
------------------------------------------------------------------
App Visibility Agent for Java was installed successfully.

Installation parameters summary: 
    -destination      "C:\Users\Administrator\Desktop\Granite App Visibility\build - 175\agent"
    -host             ""
    -portalIP         "localhost"
    -portalPort         "8100"
    -proxyHttpsHost     ""
    -proxyHttpsPort     "-1"
    -proxySocksHost     ""
    -proxySocksPort     "-1"

To run an application server with App Visibility Java Agent, add the following 
parameter to the JVM options of your application server:
-javaagent:C:\Users\Administrator\Desktop\Granite App Visibility\build - 175\agent\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:\AppVis\ADOPsInstall\instances\<instance_name>\logs
    The <instance_name> variable is a name that is generated dynamically when the agent first starts.
  2. Examine the aps_agent.log file.
    If the log file exists, the installation was successful.
    Examine [ERROR] messages for issues that you can address, such as App Visibility portal connection issues. Ensure that the portal address is correct and that a firewall is not blocking access.
  3. In the TrueSight console, select Administration > App Visibility Agents from the navigation pane and confirm that the agent is online.

Where to go from here

Access the TrueSight console

Add App Visibility to the TrueSight console

Related topics

Viewing App Visibility agent status and properties

Troubleshooting App Visibility Manager

Known and corrected issues

 

Was this page helpful? Yes No Submitting... Thank you
© Copyright 2013-2015 BMC Software, Inc.
© Copyright 2013-2015 BladeLogic, Inc.
Legal notices