This topic lists the application environments and versions supported by the AppDynamics Java Agent. For general information about AppDynamics support, see Supported Environments - 4.4.
Java Agent Supported Platforms
In the following tables, note that:
- A dash ("-") in a table cell indicates that this column is not relevant or not supported for that particular environment.
- In cases where no version is provided, assume that all versions are supported. Contact AppDynamics Sales for confirmation.
- For environments that require additional configuration, a separate table describing or linking to configuration information follows the support matrix.
- For environments supported by AppDynamics End User Monitoring, see Supported Environments and Versions - Web EUM.
- For environments supported by AppDynamics Server Visibility, Standalone Machine Agent Requirements and Supported Environments.
JVM Support
The AppDynamics Java Agent uses the standard JVM Tool Interface (JVMTI) mechanism allowing it to instrument any software running on a JVM supporting this mechanism.
AppDynamics certifies the successful operation of the basic mechanisms of instrumentation used by the agent on the following Java runtimes. These capabilities are supported on both JRE or full JDK installations.
Where the agent supports the following advanced memory monitoring features, they are listed for the JVM: Object Instance Tracking (OIT), Automatic Leak Detection (ALD), Content Inspection (CI), and Access Tracking (AT).
| JVM | OS | Memory Monitoring Features |
|---|---|---|
| Azul Zing 15.x. | Linux x64 | OIT, ALD |
| Azul Zulu 7.x | Linux x64 | OIT, ALD
|
| HP OpenVMS | ||
| IBM JVM 1.5.x, 1.6.x, 1.7.x, 1.8.x | ALD, CI Object instance tracking, automatic leak detection, and custom memory structure monitoring are not supported with the AppDynamics IBM Java Agent. IBM JVMs can be instrumented with the AppDynamics Sun Java Agent to work around this limitation, however this only enables automatic leak detection and custom memory structure monitoring. Object instance tracking is not available. Working around this limitation can result in negative performance impact and is not recommended. In such cases, the IBM JVM needs to be restarted to enable custom memory structure monitoring. | |
| Oracle Java HotSpot 7 update 45+ | Solaris Sparc 64, Windows, Linux | |
| Oracle_Java_SE_Standard_Edition 8, 9 | Solaris Sparc 64, Windows, Linux | OIT, ALD, CI, AT Content Inspection and Access Tracking require a JVM restart. |
| Oracle Rockit JVM 28.1+ | Linux Intel 64, Windows | |
| Oracle/BEA JRockit 1.5, 1.6, 1.7 | ||
| Oracle/Sun JVM 1.5, 1.6, 1.7 | All versions: ALD, CI 1.5 only: AT | |
| Open Source OpenJDK 1.6, 1.7, 1.8 | OIT, ALD | |
| SAP JDK 6+ | Windows, Solaris, Linux, HP-UX, i5/OS, AIX |
JVM Application Server and Framework Support
AppDynamics supports the use of the Java Agent to instrument any application component running on a supported JVM, irrespective of how that component is built. The power of the AppDynamics platform is that it can automatically discover the topology and behavior of complex enterprise applications without requiring deep technical knowledge of the application's underlying code.
Frequently, Java-based systems employ standard framework code to implement business logic. Automatic instrumentation of framework code relies on knowledge of the business logic and programming patterns employed by the framework. AppDynamics instrumentation targets processing hand-offs between components, called entry points and exit points, either within the JVM or between JVMs. This includes hand-offs between frameworks in cases where multiple frameworks are being used together. This section covers the capabilities for frameworks for which AppDynamics provides automatic detection rules.
Monitoring application components built using frameworks not listed here may require custom configuration. The custom configuration may involve, for example, custom POJO entry or exit points. If you understand how the application behaves internally, you can easily configure this type of instrumentation. For more complex configuration tasks, contact your account representative to discuss how to engage the AppDynamics customer success organization.
JVM Language Frameworks Support
No additional configuration is required for these frameworks.
Vendor | JVM Language | Version | Correlation/ | Exit Points | Transports | Notes |
|---|---|---|---|---|---|---|
Open Source | Akka Actor | 2.1 – 2.4.x | Yes | Yes | Netty | 4.3.1 required for 2.4.x. 2.4x support includes Persistence. Remoting exit/entry supported. |
Open Source | Akka HTTP | Akka 2.4.x Scala 2.11 | Yes | Yes | HTTP |
|
Open Source | Groovy | - | Yes | Yes |
| |
Open Source | Play for Scala | 2.1 – 2.5 | Yes | - | HTTP over Netty | Includes framework specific entry points Play EUM-APM correlation |
Open Source | Scala | 2.11.6 | ||||
| Open Source | Spray toolkit (Spray.io) | 1.1.x 1.1.3 | Yes | Yes | HTTP | Entry points are detected and configurable as servlet entry point and exit points as HTTP exits. |
Pivotal | Grails | - | - | - | - |
Java Frameworks Support
The Java Agent supports these Java frameworks. Some require additional configuration as indicated in the Configuration Notes column.
Vendor | Framework | Version | SOA protocol (WebServices) | Auto Naming | Entry Points | Exit Points | Detection | Configuration Notes |
|---|---|---|---|---|---|---|---|---|
Adobe | BlazeDS | - | HTTP and JMS adaptor | - | Yes |
| - | Example Message Queue Backend Configuration |
Adobe | ColdFusion | 8.x, 9.x | - | - | Yes | - | Configuration required for transaction discovery | Configuration is required for transaction discovery. See: |
Apache | Cassandra with Thrift framework | - | - | - | Yes | Yes | Apache Thrift Entry and Exit points are detected | |
Apache | Struts | 1.x, 2.x | - | - | Yes |
| Struts Actions are detected as entry points; struts invocation handler is instrumented | Struts Entry Points |
Apache | Tapestry | 5 | - | - | Yes | - | Not by default | See: |
| Apache | Wicket | - | - | No | Yes | - | Not by default | See: |
| Apple | WebObjects | 5.4.3 | HTTP | Yes | Yes | - | Yes | |
Open Source | CometD | 2.6 | HTTP | Yes | Yes | - | - | See also "HTTP Exit Points" on Java Backend Detection. |
Eclipse | RCP (Rich Client Platform) | - | - | - | - | - | - | |
Google Web Toolkit (GWT) | 2.5.1 | HTTP | Yes | Yes | - | - | ||
JBoss | JBossWS Native Stack | 4.x, 5.x | Native Stack | - | - | - | - | |
Open Source | Direct Web Remoting (DWR) | - | - | - | - | - | - | |
| Open Source | Eclipse Vert.x | 3.3.x, 3.4.1, 3.4.2 | HTTP | Yes | Yes | Yes | Yes | |
Open Source | Enterprise Java Beans (EJB) | 2.x, 3.x | - | - | Yes | - | - | |
Open Source | Grails | - | - | - | Yes | - | Not by default | |
Open Source | Hibernate JMS Listeners | 1.x | - | - | - | - | - | |
Open Source | Java Abstract Windowing Toolkit (AWT) | - | - | - | - | - | - | |
Open Source | Java Server Faces (JSF) | 1.x, 2.x | - | Yes | Yes | - | - | Java Business Transaction Detection and Servlet Entry Points |
Open Source | Java Server Pages | 2.x | - | Yes | - | - | Yes | |
Open Source | Java Servlet API | 2.x | - | - | - | - | - | |
| Open Source | Jersey | 1.x, 2.x | REST, JAX-RS | Yes | Yes | No | Not by default | JAX-RS Support and node properties:
See App Agent Node Properties Reference1 for information on the properties. |
Open Source | JRuby HTTP | - | - | - | Yes | - | Not by default | See: |
| Open Source | Netty | 3.x | HTTP | Yes | Yes | Yes | - |
|
| Open Source | Spring Annotated Web Services | 2.x+ | HTTP | Yes | Yes | No | - | |
| Open Source | WebSocket | 1.0 (Java EE 7, JSR-356) | - | Yes, | Yes, correlation not supported | Yes | Detection is automatic | Node property: websocket-entry-calls-enabled |
Oracle | Coherence with Spring Beans | 2.x, 3.x | - | - | - | - | - | |
Oracle | Swing (GUI) | - | - | - | - | - | - | |
Oracle | WebCenter | 10.0.2,10.3.0 | - | - | - | - | - | |
Spring
| Spring MVC | - | - | - | Yes | - | Not by default |
Application Servers
The Java Agent supports the following application servers. Some require additional configuration. Click the link on the server or OSGi Runtime for information about additional requirements or related configuration topics. The agent usually discovers application servers as an entry point.
Vendor | Application Server / | Version | SOA Protocol | RMI Supported | JMX | Entry Points | Configuration Notes |
|---|---|---|---|---|---|---|---|
Adobe | Cold Fusion | 8.x, 9.x | - | No | - | Yes | Requires configuration for transaction discovery; see Servlet Entry Points |
Equinox | - | - | - | - | Yes | ||
Apache | Felix | - | - | - | - | Yes | |
Apache | Sling | - | - | - | - | Yes | |
Apache | Tomcat | 5.x, 6.x, 7.x, 8.x | - | - | Yes |
| Apache Tomcat Startup Settings |
Apache | Resin | 1.x - 4.x | - | - | - | - | |
Eclipse | Jetty | 6.x, 7.x | - | - | - | - | Jetty Startup Settings |
| IBM | InfoSphere | 8.x | - | - | - | Yes | IBM WebSphere and InfoSphere Startup Settings |
IBM | WebSphere | 6.1, 7.x, 8.x, 9.x | JAX-WS | Yes, detect and correlate | Yes for WebSphere PMI | Yes | IBM WebSphere and InfoSphere Startup Settings |
Open Source | Liferay Portal | - | - | - | - | - | |
| Open Source | JBoss Wildfly (formerly JBoss Server) | 4.x, 5.x, 6.x, 7.x, 8.x | Yes | Yes | |||
| Sun/Oracle | GlassFish Enterprise Server | 2.x | - | - | Yes | Yes | GlassFish Startup Settings |
Oracle | GlassFish Server and | 3.x, 4.x | - | - | Yes for AMX | Yes | GlassFish Startup Settings |
Oracle and BEA | WebLogic Server | 9.x+ | JAX-WS | Yes, detect and correlate for 10.x | Yes | Yes | Oracle WebLogic Startup Settings |
| Red Hat | JBoss Enterprise Application Platform | 5 | |||||
| Red Hat | JBoss Enterprise Application Server | 6.11, 6.2.0, 7.x | Yes | Yes | |||
| Software AG | webMethods | 9.5, 9.6 | - | - | - | Yes | |
| Tibco | ActiveMatrix BusinessWorks Service Engine | 5.x, 6.x | - | - | - | Yes | |
Application Server (OC4J) | - | - | Yes, detect and correlate for 10.x | - | Yes | ||
- | Grails, with Tomcat 7.x, Glassfish v3, Weblogic 12.1.1 (12c) | - | - | - | - |
|
Servlet 3.x detection is not supported.
PaaS Providers
| PaaS Provider | Buildpack |
|---|---|
| Pivotal Cloud Foundry | See Using AppDynamics with Java Applications on Pivotal Cloud for more information. |
| Red Hat Openshift 3 | JBoss EAP 6.4 and WildFly 8.1 Docker images For documentation and download information, see the AppDynamics Java APM Agent page on the Red Hat Customer Portal. |
Message Oriented Middleware Support
The Java Agent supports the following message oriented middleware environments. Some require additional configuration as indicated in the Configuration Notes column. Message oriented middleware servers are usually found by the Java Agent as an entry point.
Vendor | Messaging Server | Version | Protocol | Correlation/Entry Points | Exit Points | JMX | Configuration Notes |
|---|---|---|---|---|---|---|---|
| Amazon | Simple Queue Service (SQS) | - | - | Yes (correlation only) | Yes | - | See "Amazon Simple Queue Service Backends" on Java Backend Detection |
| Amazon | Simple Notification Service (SNS) | - | - | No | Yes | - | See "Amazon Simple Notification Service Backends" on Java Backend Detection |
Apache | ActiveMQ | 5.x+ | JMS 1.x | Yes | Yes | Yes | |
Apache | ActiveMQ | 5.x+ | STOMP | No | - | Yes | |
Apache | ActiveMQ | 5.8.x+ | AMQP 1.0 | No | - | Yes | |
Apache | Axis | 1.x, 2.x | JAX-WS | Yes | Yes | - | Default exclude rules exist for Apache Axis, Axis2, and Axis Admin Servlets. See aslo "Web Service Entry Points" on Java Backend Detection. |
Apache | Apache CXF | 2.1 | JAX-WS | Yes | Yes | - | To enable correlation, set node property enable-soap-header-correlation=true. |
| Apache | Kafka | 0.9.0.0 | - | Yes - (Entry point only) | Yes | Yes | Kafka consumer entry points are disabled by default. Correlation is not supported. See Apache Kafka Consumer Backends. |
Apache | Synapse | 2.1 | HTTP | Yes | Yes | - | To enable correlation, set node property enable-soap-header-correlation=true. |
Fiorano | Fiorano MQ |
| - | - | - | - | |
IBM | IBM Web Application Server (WAS) | 6.1+, 7.x | Embedded JMS | - | Yes | - | |
IBM | IBM MQ (formerly IBM WebSphere MQ) | 6.x+ | JMS | Yes | Yes | - | |
Mulesoft | Mule ESB | 3.4, 3.6, 3.7, 3.8, 3.9 | HTTP, JMS | Yes | Yes | - | |
| Open Source | Eclipse Vert.x verticles | 3.3.x | - | Yes (correlation only) | Yes | - | The Java Agent detects messaging exit calls between verticles. |
Open Source | Open MQ | - | - | - | - | - | |
| Oracle | Java Message Service | 2.0 | JMS | Correlation of the listener is disabled by default | Yes | ||
Oracle | Oracle AQ | - | JMS | - | Yes | - | |
Oracle / BEA | WebLogic | 9.x+ | JMS 1.1 | Yes | Yes | Yes | |
Progress | SonicMQ | - | - | - | - | - | |
Pivotal | RabbitMQ | - | HTTP | - | Yes | - | See "RabbitMQ Backends" on Java Backend Detection |
Rabbit | RabbitMQ Spring Client | - | - | Yes | Yes | - | See "RabbitMQ Backends" on Java Backend Detection |
| Red Hat | HornetQ (formerly JBoss Messaging and JBoss MQ) | - | Yes | ||||
| Red Hat | JBoss A-MQ | 4.x+ | - | - | - | Yes | |
Spring | Spring Integration | 2.2.0 | JMS | Yes | Yes | Yes | See also "Java Message Service Backends" on Java Backend Detection |
| WSO2 | ESB | 4.7.0 | - | Yes | Yes | - |
JDBC Drivers and Database Servers Support
The Java Agent supports these JDBC driver and database server environments. AppDynamics can follow transactions using these drivers to the designated database.
JDBC Vendor | Driver Version | Driver Type | Database Server | Database Version |
|---|---|---|---|---|
Apache | 10.9.1.0 | Embedded or client | Derby | - |
Apache | - | - | Cassandra | - |
Progress | DataDirect | data connectivity for ODBC and JBDC driver access, data integration, and SaaS and cloud computing solutions | - | - |
IBM | JDBC 3.0 version 3.57.82 or JDBC 4.0 version 4.7.85 | DB2 Universal JDBC driver | DB2 | 9.x |
IBM | JDBC 3.0 version 3.66.46 or JDBC 4.0 version 4.16.53 | DB2 Universal JDBC driver | DB2 | 10.1 |
IBM | - | Type IV | Informix | - |
Microsoft | 4 | Type II | MS SQL Server | 2012 |
Oracle MySQL, MySQL Community | 5.x | Type II, Type IV | MySQL | 5.x |
| Oracle | RAC | |||
Oracle | 9.x | Type II, Type IV | Oracle Database | 8i+ |
Open Source | - | Type IV | Postgres | 8.x, 9.x |
Sybase | jConnect | Type IV | Sybase | - |
| Teradata | Teradata | - |
Notes:
- Type II is a C or OCI driver
- Type IV is a thin database client and is a pure Java driver
NoSQL/Data Grids/Cache Servers Support
The Java Agent supports these NoSQL, data grids and cache server environments. Some require additional configuration. Click the link on the database, data grid or cache name in the following support matrix for information about additional configuration required or related configuration topics.
Vendor | Database/Data Grid/Cache | Version | Correlation/Entry Points | JMX | Configuration Notes |
|---|---|---|---|---|---|
| Amazon | DynamoDB | - | Exit Points | - | See "Amazon Web Services" on Java Backend Detection. |
| Amazon | Simple Storage Service (S3) | - | - | - | "Amazon Simple Storage Service Backends" on Java Backend Detection. |
Apache | Casandra
| 1.x, 2.x | Correlation for Thrift drivers only | Yes |
|
Apache | Lucene - Apache Solr | 1.4.1 | Entry Points | Yes | |
JBoss | Cache TreeCache | - | - | - | |
| JBoss | Infinispan | 5.3.0+ | Correlation | - | - |
Open Source | Memcached | - | - | - | |
Open Source | MongoDB | 3.1 | - | - | See "MongoDB Backends" on Java Backend Detection |
Oracle | Coherence | 3.7.1 | Custom-Exit | Yes | |
| Red Hat | JBoss DataGrid | - | - | - | |
| JBoss Cache TreeCache | - | - | - | ||
| JBoss Infinispan | 5.3.0+ | Correlation | - | ||
Terracotta | EhCache | - | - | - |
RPC/Web Services API/HTTP Client Support
The Java Agent supports these RPC, web services or API framework types. Some require additional configuration as indicated in the Configuration Notes column.
Vendor | RPC/Web Services API Framework | Version | SOA Protocol- | Auto Naming | Correlation/Entry Points | Exit Points | Configurable BT Naming Properties | Detection | Configuration Notes |
|---|---|---|---|---|---|---|---|---|---|
Apache | Apache CXF | 2.1 | JAX-WS | Yes | Yes | Yes | Yes | Yes | |
Apache | Apache HTTP Client | - | HTTPClient (now in Apache HTTP Components) | Yes | Yes (correlation only) | Yes | - | Yes | See "HTTP Backends" on Java Backend Detection |
| Apache | Apache Async HTTP Client | 4.1.x | - | - | - | - | - | - | - |
| Apache | Ribbon HTTP Client | 2.1.0 | HTTP Client | Yes | Yes (correlation) Entry - NA | Yes | NA | Yes | |
Apache | Apache Thrift | - | - | Yes | Yes | Yes | Yes | Yes | Binary Remoting Entry Points for Apache Thrift |
| Eclipse | Jetty | 8.x, 9.x | HTTP Client | Yes | Yes (correlation only) | Yes | - | Yes | See "HTTP Backends" on Java Backend Detection |
IBM | WebSphere | 6.x, 7.x, 8.x | JAX-RPC | - | - | - | - | - | IBM WebSphere and InfoSphere Startup Settings; also see Default configuration excludes WebSphere classes |
IBM | Websphere | 7.x, 8.x | IIOP | - | - | - | - | - | IBM WebSphere and InfoSphere Startup Settings; also see Default configuration excludes WebSphere classes |
Open Source | java.net.Http | - | HTTP | Yes | - | Yes | Yes | Yes | See "HTTP Backends" on Java Backend Detection. |
| Open Source | HTTPClient | 0.3-3 | Oracle SOA (and potentially others that embed this library) | - | Correlation: Yes; Entry: No | Yes | - | Yes | Oracle WebLogic Startup Settings; also see Default configuration excludes WebLogic classes |
| Open Source | Grizzly | Grizzly Async HTTP Client (com.ning.http-client 1.8.x, 1.9.x, grizzly-http-client 1.1x)
| HTTP | - | Correlation: Yes;Entry:No | Yes | - | Yes | |
Oracle | GlassFish Metro | - | JAX-WS | - | - | - | - | - | |
| Oracle | GlassFish Metro with Grails | - | JAX-WS | - | Yes | - | - | Not by Default | |
Oracle | Oracle Application Server | ORMI | - | no | - | - | - | - | |
Oracle | WebLogic | 10.x | T3, IIOP | Yes | Correlation: Yes; Entry: No | Yes | - | Yes | |
Oracle | WebLogic | 9.x, 10.x | JAX-RPC | - | - | - | - | - | |
Oracle/Sun | Sun RMI | - | IIOP | - | Not by Default | - | - | - | |
Oracle/Sun | Sun RMI | - | JRMP | - | No | Yes | host/port | Yes | |
Red Hat | JBoss A-MQ | 4.x+ | RMI | Yes | Yes | Yes | Yes | Yes | JBoss and Wildfly Startup Settings |
| Square | OkHttp | ||||||||
| Square | OkHttp | - | HTTP | Yes | Correlation: Yes Entry: No | Yes | - | Synchronous only | |
- | Web Services | - | SOAP over HTTP | - | Yes | Yes | - | - | Create Match Rules for Web Services "Web Service Entry Points" on Java Backend Detection |
Business Transaction Error Detection
The Java Agent supports the following logging frameworks for business transaction error detection:
- Apache Log4j and Log4j 2
- java.util.logging
- Simple Logging Facade for Java (SLF4J)
Support for the following method has been added:public void error(String format, Object... argArray) - Logback
To instrument other types of loggers, see Error Detection.
Overview
Content Tools
Apps
