Configure Application Server to Use the Java Agent

You must configure your application server to:
apmdevops106
You must configure your application server to:
  • Start the Java Agent
  • Configure the startup script for the application
You must configure the application server you are instrumenting to include the path to the agent’s primary
.jar
file (
Agent.jar
) and the agent profile (
IntroscopeAgent.profile
). In most cases, you do this by editing the application server's startup script, then restarting the application server. When the application server restarts, the Java agent instruments the classes discovered for default components of the JVM and application environment. The specific steps involved depend on the application server.
You can configure your application server in different Java Runtime Environments, including Oracle JVM and IBM JVM. With an IBM J9 JVM, you might want to replace the primary
Agent.jar
and
IntroscopeAgent.profile
files with their modified versions,
AgentNoRedefNoRetrans.jar
and
IntroscopeAgentNoRedef.profile
, to avoid performance issues. Consider the following guidelines:
  • IBM J9 JVM with JRE 1.6.0: It is required to use the
    AgentNoRedefNoRetrans.jar
    file instead of
    Agent.jar
    .
  • IBM J9 JVM with JRE 1.7.0 or 1.8.0: It is recommended to use the
    AgentNoRedefNoRetrans.jar
    file instead of
    Agent.jar
    .
Using
AgentNoRedefNoRetrans.jar
deactivates class redefinition and retransformation to prevent possible performance issues.
AgentNoRedefNoRetrans.jar
and
IntroscopeAgentNoRedef.profile
are available out of the box for IBM WebSphere Application Server and Oracle WebLogic Server. You can create
AgentNoRedefNoRetrans.jar
and
IntroscopeAgentNoRedef.profile
files for JBoss/WildFly and Apache Tomcat by editing a few properties.
See JBoss and Apache Tomcat for more information.
Using the AgentNoRedefNoRetrans.jar file has the following limitations:
  • Metrics are not reported for system classes (java.*), NIO (Sockets and Datagrams), and SSL sockets because the class redefinition and retransformation functions are deactivated.
  • Instrumentation on sockets reverts to pre-Introscope 9.0.
  • ManagedSocket style remote dynamic instrumentation is disabled.
  • Changes to the PBD files require the instrumented JVM to be restarted before being applied.
  • Deep inheritance and hierarchy support instrumentation features are disabled.
  • Automatic entry point and automatic backend detection are disabled.
  • If you are using the AllAppServer agent distribution with the AgentNoRedefNoRetrans.jar file, the alternate profile is named IntroscopeAgent.websphere.NoRedef.profile.
  • If you have both instrumented and noninstrumented applications on the same computer, include the
    -Xshareclasses:none
    setting in the Generic JVM Argument. This setting avoids errors on AIX. A unique directory is required when there is more than one version of WebSphere using the same agent directory.
  • If you use a non-IBM JVM or an IBM JVM version other than 1.5, not all metrics and messages are output.
The steps to configure your application server to work with the Java Agent differ based on the application server.