Preparing for installation of App Visibility agent for Java

The JVM platform enables you to run multiple monitoring agents, and the App Visibility agent for Java generally runs as expected with other agents. Yet other agents might significantly alter the runtime environment and such changes, over which BMC has no control, might cause unexpected results or malfunction in the App Visibility agent for Java with your web application.

Therefore, BMC strongly recommends that you disable or remove anynon-BMC application performance monitoring agent from the application server where you install the App Visibility agent for Java.

• Windows
  ad_java_agent_win_11.0.00.zip
  
  
• Unix
  ad_java_agent_unix_11.0.00.tar.gz
  
  The Unix file contains files for the following versions:
  • Linux
    ad_java_agent_linux_11.0.00.tar.gz
  • AIX
    ad_java_agent_aix_11.0.00.tar.gz
  • Solaris
    ad_java_agent_solaris_11.0.00.tar.gz

Ensure that you have the required privileges to run the installation.

• On Unix platforms, to ensure proper functioning of the agent, install the agent with the user that runs the application server.
• On Windows platforms, you must run the installation as administrator. Only the user that installed the agent will be able to uninstall or upgrade it.
  There are no restrictions on which user can run the application server with the agent.

Verify the memory requirements. The agent for Java requires up to 256 MB of JVM heap memory. If the agent is running in the same JVM memory space as the monitored application, BMC recommends adding 256 MB to the Max heapsize Java options flag -Xmx.

Example

set JAVA_OPTS=%JAVA_OPTS% -Xmx1024m

For full details about both the -javaagent and Xmx options, refer to the Java options for each application server type.

Watch videos on YouTube

Watch Installing App Visibility Part 5 | Agent for Java Startup and Tuning (starting at 1:20) to tune the agent by increasing the JVM heap memory in WebLogic.