Pre-requisites for Java Business Transaction Monitoring Using eG Enterprise

The following are the pre-requisites for performing Java business transaction monitoring using eG:

  • For the eG Java Business Transaction Monitor to function, your eG Enterprise infrastructure should include:

    • An eG Manager of version 6.2.0 (or above)
    • eG Agents of version 6.2.0 (or above)
    • An eG database on a Microsoft SQL Server 2008 (or above) (OR) An Oracle Database Server 9i (or above)

  • The eG Java Business Transaction Monitor (BTM) can be installed on Java containers only - i.e., Java applications / J2EE-enabled web, application, and messaging servers. The details are as follows:

    • Supported JVMs

    The eG Java BTM can be installed on JVM 1.6 (and above) only, regardless of the JVM vendor. JVM 1.4 or below is not supported. Only partial support is available to JVM 1.5; this is because, in JVM 1.5, cross-application transaction tracing cannot be performed since the HttpURLConnection class cannot be byte-code instrumented to perform cross-JVM tag-and-follow.

    Vendor-specific JVM support is as detailed below:

    • Oracle Hotspot JVM 1.6 to 19
    • BEA JRockit 1.6
    • IBM JVM 1.6 to 1.8
    • Oracle OpenJDK 1.6 to 19
    • Amazon Corretto OpenJDK 1.8, 11, 15 to 19
    • Eclipse Adoptium OpenJDK 1.8, 11, 16 to 19
    • SAP JVM 1.6 to 1.8
    • Azul Zing 1.6 to 1.8
    • Azul Zulu 1.6 to 1.8

    Supported Application Types

    Java-based application types

    Supported/Unsupported Application Servers

    Application Server

    Supported Versions

    Unsupported Versions

    WebSphere Application Server

    7.x, 8.x, 9.x

    6.x and below

    WebSphere Liberty Profile

    8.x

     

    WebLogic Server

    9.x, 10.x, 12.x, 14.x

    8.x and below

    JBoss

    4.x, 5.x

     

    JBoss AS/EAP

    6, 7, 7.x

     

    WildFly

    8.x to 27.x

     

    Tomcat

    5.x, to 10.x

    4.x and below

    TomEE

    7.x, 8.x

     

    Jetty

    9.x, 10.x, 11.x

     

    GlassFish

    3.x, 4.x, 5.x, 6.x

    2.x

    Payara

    4.x, 5.x

     

    Oracle Application Server (OC4J)

     

     

    Spring Boot Application with Embedded Tomcat

    2.0 to 2.2

     

    Spring Boot Application with Embedded Jetty

    2.0 to 2.2

     

    Spring Boot Application with Embedded Undertow

    2.0 to 2.2

     

    Any Custom Web Application with Embedded Tomcat

    6.x to 10.x

     

    Supported Packaged Applications

    • Oracle Peoplesoft
    • Oracle JDEdwards
    • Liferay (with Tomcat) 6.2 to 7.3
    • WSO2 ESB 5.x / WSO2 API Manager 3.2, 4.1

    Supported Entry Pointcuts

    • Servlets/Filters 2.5 (and above)
    • JSPs
    • Struts 1.x, 2.x
    • Spring MVC 3.x, 4.x and 5.x
    • Web Services - SOAP and REST
    • Java Server Faces (JSF) 1.x and 2.x
    • JMS 1.x, 2.x and 3.x
    • Apache Synapse

    Supported HTTP Exit Pointcuts

    • Java HTTPURLConnection
    • ApacheHTTPClient 3.x and 4.x

    Supported Web Service Exit Points

    • SOAP based web services
    • Apache Axis 1.x and 2.x
    • Apache CXF
    • Resteasy
    • Jersey

    Supported Databases

    • Oracle 8i, 9i, 10g, 11g, 12c
    • IBM DB2 9.x
    • MS SQL Server 2005, 2008, 2012, 2016
    • PostgreSQL 8.x and 9.x
    • MySQL 5.x and 8.0
    • HSQLDB
    • MariaDB 5.x
    • IBM Informix
    • Sybase
    • SAP HANA
    • AWS RDS
    • AWS Aurora
    • Mongo DB 3.x

    Supported Database/ORM Frameworks

    • iBATIS/MyBatis 2.x and 3.x
    • Hibernate
    • JPA

    Supported Database Clusters

    • Microsoft SQL Cluster

    • Oracle RAC

      Note:

      • In the cross-applications transaction topology flow map, a Microsoft SQL cluster (if any) will be represented only as a standalone Microsoft SQL database server.
      • Oracle RAC supports a variety of JDBC URL formats. The eG Java BTM currently captures only those queries issued to an Oracle RAC for just a subset of these JDBC URL formats. If a Java transaction issues a query to an Oracle RAC for one of the supported JDBC URL formats, that Oracle RAC component will only be represented as a standalone Oracle database server in the cross-application transaction topology flow map.

    Supported ESB and Integration Frameworks

    • Mule ESB 3.9
    • Apache Camel (Only JMS integration)

    Supported Drivers

    • Oracle- Thin
    • DB2
    • Microsoft SQL Server
    • Connector/J 5
    • jTDS - Type4
    • JDBC2, JDBC2 EE, JDBC3, JDBC4

    Messaging Exit Pointcuts

    • Apache ActiveMQ 5.x
    • JBoss Messaging and HornetQ from JBoss
    • IBM MQ
    • JMS Queues and Topics
    • RabbitMQ (AMQP 0.9)
    • WebLogic JMS
    • Solace
    • Qpid

    Middleware Exit Pointcuts

    • RMI using JRMP
    • EJB - Stateless session bean (SLSB)
    • EJB - Stateful session bean (SFSB)
    • Runtime Exec (Process Exec)
    • LDAP
    • Java Mail
    • SAP JCO
    • JOLT

    Caching Frameworks or In-memory Databases

    • H2
    • HSQL DB
    • EHCACHE 2.x
    • Redis

    Elastic Environments

    • Standalone Docker (Plain Vanilla Docker)
    • Podman
    • Standalone Kubernetes
    • Azure K8S
    • AWS ECS (using EC2 Instances)
    • AWS EKS (using EC2 Instances)
    • RedHat OpenShift

    • VMware Tanzu Kubernetes Grid Integrated Edition (TKGI)

    • Rancher Kubernetes Engine (RKE)

    • Google Kubernetes Engine -(GKE Standard)

    • Docker Swarm

    Async Frameworks

    • Java Executor Service (except ForkJoinPool)

  • The eG Java Business Transaction Monitor (BTM) can be installed on only those Java containers that use JDK 1.5 or higher.
  • Do not install the eG Java Business Transaction Monitor (BTM) on a Java container that is already JTM-enabled.
  • For cross application transaction tracing to occur, the Java application being monitored should run only on JRE 1.6 (or higher).

  • For complete visibility into the transaction path, make sure that you:

    • BTM-enable each JVM node in the transaction path;
    • Manage each JVM node as a separate component in eG;