IBM Tivoli Composite Application Manager for Application Diagnostics, Version

Disable various types of Byte Code Instrumentation for J2EE APIs

The data collector uses a technique called Byte Code Instrumentation (BCI) to collect data from various types of J2EE APIs that typically operate as nested requests. BCI is automatically enabled for these types of APIs. It can be disabled by adding lines to the custom_directory/ file.

Disable instrumentation of one or more of the following types of APIs by adding the following lines to the file:

Adding lines to

Type of J2EE API Line to add to file
Enterprise JavaBeans (EJB)
Java Connector Architecture (JCA)
Java Database Connectivity (JDBC)
Java Naming and Directory Interface (JNDI)
Java Message Service (JMS)
Servlets/JavaServer Pages (JSP)
HTTP session count tracking
CICS® Transaction Gateway (CTG)
Java Data Objects (JDO)
Message Queue Interface (MQI)
Axis web service (only on JBoss and WebLogic)
Remote Method Invocation (RMI)

For performance reasons, you can also disable BCI for several API types only for Level 1 monitoring. In this case, BCI will for the API types be enabled only when the monitoring level is set to 2 or 3.

To do this, add (or uncomment) the following lines in the custom_directory/ file.

Modifying lines in

Type of J2EE API Line to add to file

Parent topic:

Customization and advanced configuration for the data collector