Disabling various types of Byte Code Instrumentation for Java EE APIs

Edit online

In Byte Code Instrumentation (BCI), the data collector intercepts method entry and exit calls for various types of Java™ Platform Enterprise Edition (Java EE) APIs to create an execution flow of each application request. Some resources are used for the monitoring. You can tune the data collector so that some of the APIs are not monitored, reducing resource use.

To disable BCI monitoring for Java EE APIs, add the following properties to the toolkit custom properties file. For more information about this file, see Toolkit properties file.

Table 1. Adding lines to the toolkit custom properties file
Type of Java EE API	Line to add to toolkit_custom.properties file
Enterprise JavaBeans (EJB)	`com.ibm.tivoli.itcam.toolkit.ai.enableejb=false`
Java Connector Architecture (JCA)	`com.ibm.tivoli.itcam.toolkit.ai.enablejca=false`
Java Database Connectivity (JDBC)	`com.ibm.tivoli.itcam.toolkit.ai.enablejdbc=false`
Java Naming and Directory Interface (JNDI)	`com.ibm.tivoli.itcam.toolkit.ai.enablejndi=false`
Java Message Service (JMS)	`com.ibm.tivoli.itcam.toolkit.ai.enablejms=false`
Web containers for Servlets/JavaServer Pages (JSP)	`com.ibm.tivoli.itcam.dc.was.webcontainer=false`
HTTP session count tracking	`com.ibm.tivoli.itcam.toolkit.ai.enablesessioncount=false`
CICS® Transaction Gateway (CTG)	`com.ibm.tivoli.itcam.dc.ctg.enablectg=false`
IMS	`com.ibm.tivoli.itcam.dc.mqi.enableims=false`
Java Data Objects (JDO)	`com.ibm.tivoli.itcam.dc.mqi.enablejdo=false`
Message Queue Interface (MQI)	`com.ibm.tivoli.itcam.dc.mqi.enablemqi=false`
Axis web service	`com.ibm.tivoli.itcam.toolkit.ai.axis.enablewebservice=false`
Remote Method Invocation (RMI)	`am.ejb.rmilistener.enable=false`
WebSphere® Application Server EJB container	`com.ibm.tivoli.itcam.dc.was.enableEJBContainer=false`