Installing and Configuring eG Java BTM

The first step towards business transaction monitoring is to BTM-enable the JVM nodes in the transaction path. For this purpose, eG Enterprise requires that a special eG Application Server Agent be deployed on every JVM node (i.e., web application server instance) through which the transaction travels.

The eG Application Server Agent is available as a file named eg_btm.jar on the eG agent host, which has to be copied to the system hosting the application servers being monitored. You then need to configure the application server with the path to the eg_btm.jar file to fully BTM-enable the server.

The detailed steps for deployment on different web application servers have been discussed in the following topics.

Installing eG Java BTM on a Generic JVM Node

Installing eG Java BTM on an Apache Tomcat Server

Installing eG Java BTM on an IBM WebSphere Server

Installing eG Java BTM on an Oracle WebLogic Server

Installing eG Java BTM on JBoss EAP

Installing eG Java BTM on WildFly

Installing eG Java BTM on a GlassFish Application Server

Let us then take a look at the tests run by the eG agent.

Java Business Transactions Test

Key Java Business Transactions Test