IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Customization and advanced configuration for the data collector - J2EE Agent
This section contains instructions for customizing your configuration of the data collector (DC).
- Fine-tuning datacollector.properties
- Change the Managing Server that connects to the data collector
- Configure the data collector after changing the application server version
- Change the IP address of the data collector host computer
- Move the data collector to a different host computer
- Control Instrumentation of Application Classes for Memory Leak, Lock and L3 Method Analysis
- Set the Heap Dump scan interval and logging
- Define custom requests
- 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/toolkit_custom.properties file.- Specify data collection for custom MBeans
- Specify data collection for custom MBeans - an alternative approach
- Customize CICS transaction correlation
- Enable instrumentation of Web Services as new request types
On the JBoss and Weblogic application servers, Web Services can be instrumented by the data collector. By default, this feature is disabled.- Install Memory Dump Diagnostic for Java with IBM Support Assistant
Memory Dump Diagnostic for Java (MDD for Java) either analyzes a single heap dump or analyzes and compares two heap dumps and searches for evidence of a memory leak. In order to download MDD for Java, First install IBM Support Assistant (ISA). ISA provides extra help with diagnosing problems and provides extra tools and components for troubleshooting as well as providing a place to write problems (PMRs).- Configure a data collector for multiple network cards and NATs
- Parameters specified with multiple network cards
- Enable the secondary data collector (for the monitoring agent) if not done during an initial installation
- Suppress verbose garbage collection output in data collectors with a Sun JDK
- Configure the Tomcat data collector to run as a Windows service
Once you have configured the data collector, you can complete the following steps to configure the Tomcat data collector to run as a Windows service.
Parent topic:
Agent for J2EE data collector Installation Guide