IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Customers running at monitoring level 2 (MOD L2) cannot obtain Method Profiling data
The problem: Customers running at monitoring level 2 (MOD L2) that select the check box for Method Profiling, might get the following message:
"To make sure your system is instrumented to capture all level 3 data, update the toolkit_custom.properties file within the data collector's custom folder for the monitored application server. Be sure to recycle the application server to ensure proper results. For CICS and IMS™, please ignore this warning."
The reason: Method Profiling, an optional feature at monitoring level 2, is dependent on monitoring level 3 method entry and exit instrumentation. The purpose of Method Profiling is to summarize those Level 3 method entry and exit requests, to give you summarized method level data without the overhead of sending all Level 3 requests to the Managing Server for analysis.
The solution: For an introduction to ITCAM for WebSphere's technique for instrumenting application classes, see the following section of the data collector installation and customization guide: "Controlling instrumentation of application classes for memory leak, lock, and Level 3 method analysis"
To enable Method Profiling with default settings, update the toolkit_custom.properties file for each application server to be monitored using this feature. In particular, uncomment the am.camtoolkit.gpe.customxml.L3 property and set com.ibm.tivoli.itcam.toolkit.ai.methodentryexittrace=true. Refer to the section "Enabling Byte Code Instrumentation features with default settings" in "data collector Installation and Customization Guide".
It is recommended that you customize Method Profiling to instrument a subset of your application classes. Refer to the section "Customizing Level 3 method entry and exit analysis" in "data collector Installation and Customization Guide".
Parent topic:
Run the Managing Server