Prerequisites for Deploying an APM Java Agent

The section covers the key considerations and prerequisites for deploying APM Java Agents.

CPU Usage Guidelines for Deploying APM Java Agents

The following tables lists the CPU usage guidelines for deploying APM Java agents on different platforms:

Metrics WebLogic Server Tomcat JBoss
- Without Agent With Agent Without Agent With Agent Without Agent With Agent
CPU Usage 2.11% 2.73% 7.20% 8.40% 1.90% 3.23%

Certification Guidelines for Deploying APM Java Agents

Starting in Oracle Management Cloud (OMC) 1.21, the APM Java Agent ships with a root Verisign certificate in its config directory and uses it to communicate with OMC. Make sure that this certificate remains on the agent's certificate path for proper communication across OMC versions.

Prerequisites for Deploying APM Java Agent on a WebLogic Server

  • Supported versions of Oracle WebLogic Server:

    • Oracle WebLogic Server 12.1.3

    • Oracle WebLogic Server 12.1.2

    • Oracle WebLogic Server 10.3.6, also known as Oracle WebLogic Server 11g Release 1

    Note:

    In the host running Oracle WebLogic Server, you can run the following command from $WLS_HOME/server/lib to check the Oracle WebLogic Server version:

    java -cp weblogic.jar weblogic.version
  • cURL with SSL support

  • Unzip

  • Other considerations:

    • The machine hosting the Oracle WebLogic Server should be able to establish an HTTPS connection (either over a proxy server or not) to Oracle Management Cloud.

    • The install user of APM Java Agent should be the same as the WebLogic Server user.

    • The WebLogic Server user should have read and write permissions to the directories that host the APM Java Agent.

Prerequisites for Deploying APM Java Agent on an Apache Tomcat Server

  • Supported versions of Apache Tomcat Server:

    • 7

    • 8

    • TomEE

  • cURL with SSL support

  • Unzip

  • Other considerations:
    • The machine hosting the Apache Tomcat Server should be able to establish an HTTPS connection (either over a proxy server or not) to Oracle Management Cloud.

    • The install user of APM Java Agent should be the same as the Apache Tomcat user.

    • The Apache Tomcat Server user should have read and write permissions to the directories that host the APM Java Agent, as well as the CATALINA_BASE APM Java Agent logging and config directories if different from CATALINA_HOME.

    • If you are installing the APM Java Agent on minor Tomcat version 6.0.20 or earlier, please add the following command line option to enable local:
      jmx: -Dcom.sun.management.jmxremote

Prerequisites for Deploying APM Java Agent on a JBoss Server

  • Supported versions:

    • JBoss EAP 6.1

    • Wildfly 9.0.2

  • cURL with SSL support

  • Unzip

  • Other considerations:
    • The machine hosting the JBoss Server should be able to establish an HTTPS connection (either over a proxy server or not) to Oracle Management Cloud.

    • The install user of APM Java Agent should be the same as the JBoss user.

    • The JBoss Server user should have read and write permissions to the directories that host the APM Java Agent, as well as the JBOSS Home.

Prerequisites for Deploying APM Java Agent on a WebSphere Application Server

  • Supported versions:

    • WebSphere Application Server 8.5

  • cURL with SSL support

  • Unzip

  • Other considerations:
    • The machine hosting the WebSphere Application Server should be able to establish an HTTPS connection (either over a proxy server or not) to Oracle Management Cloud.

    • The install user of APM Java Agent should be the same as the WebSphere Application Server user.

    • The WebSphere Application Server user should have read and write permissions to the directories that host the APM Java Agent, as well as the WebSphere Application Server Home.

Prerequisites for Deploying APM Java Agent on a Jetty Server

  • Supported versions:

    • Jetty Server 7, 8, and 9

  • cURL with SSL support

  • Unzip

  • You can install one APM Agent in one instance of Jetty.

  • Other considerations:
    • The machine hosting the Jetty Server should be able to establish an HTTPS connection (either over a proxy server or not) to Oracle Management Cloud.

    • The install user of APM Java Agent should be the same as the Jetty Server user.

    • The Jetty Server user should have read and write permissions to the directories that host the APM Java Agent, as well as the Jetty Server Home.