Page History
...
Table 18-1 Recognized properties
| Property name | Multiplicity | Description |
|---|---|---|
logBeginMethodName | Optional | Identifies the logger method to call to report calls to EJB business methods. |
| logEndMethodName | Optional | Identifies the logger method to call to report calls to EJB business methods. |
| invocationType | Optional | Identifies how the logger events show up in Precise for J2EE. |
skeletonMarkerClass | Any Number | Identifies the classes that an EJB skeleton must extend. Only classes that extend a skeleton class or implement a skeleton interface are searched for calls to methods with matching name and signature. |
skeletonMarkerInterface | Any Number | Identifies the classes that an EJB skeleton must implement. Only classes that extend a skeleton class or implement a skeleton interface are searched for calls to methods with matching name and signature. |
implementationMarkerClass | Any Number | Identifies the classes that must be extended by calls with a matching name and signature. |
implementationMarkerInterface | Any Number | Identifies the classes that must be implemented by calls with a matching name and signature. |
Applying instrumentation using the "Calls to EJB" instrumentation feature
...
The following special variables can be used in the instrumenter config file path:
${indepth.j2ee.home} expands to <i3_root>/products/j2ee${indepth.j2ee.server_id} expands to the JVM ID (with no sequence number)${indepth.j2ee.jvm_id} expands to the JVM ID (with a sequence number)
...
About the instrumenter configuration files
...
Table 18-2 Instrumentation configuration files
| File name | Description |
|---|---|
| Logger.xml | Product configuration. |
| Planners.xml | Controls the order in which instrumentation is applied. |
| Heatseeker.xml | Adaptive instrumentation analysis results that are loaded at startup. This file is regenerated when adaptive instrumentation policies are run. |
| Ixp.xml | Instrumentation Explorer applied changes that are loaded at startup. This file is regenerated when you click the Instrumentation Explorer Apply Changes button. |
| Survey.xml | Adaptive survey instrumentation configuration. |
| SurveyConditional.xml | Adaptive conditional instrumentation configuration. |
| SurveySynchronization.xml | Adaptive synchronization instrumentation. |
| Servlet.xml | Default Java Servlet instrumentation configuration |
| GenericPortal.xml | Default Generic Portal-specific instrumentation configuration. Detects the portal and portlet configurations that implement javax.portlet.GenericPortlet. |
| GenericPortlet.xml | Default Generic Portlet-specific instrumentation configuration. Instruments the portlet lifecycle and action methods. |
| JSP.xml | Default JSP instrumentation configuration. |
| WebLogicJSP.xml | Default (BEA WebLogic™-specific) JSP instrumentation configuration. |
| WebSphereJSP.xml | Default (IBM® WebSphere®-specific) JSP instrumentation configuration. |
| WebLogicPortal.xml | Default BEA WebLogic Portal-specific instrumentation configuration. Detects the portal and portlet configuration. This file is populated when an application server portal version is selected in Precise Framework Installer. |
| WebLogicPortlet.xml | Default BEA WebLogic Portlet-specific instrumentation configuration. Instruments the detected portlets. This file is populated when an application server portal version is selected in Precise Framework Installer. |
| EJB.xml | Default EJB instrumentation configuration. Handles instrumentation of EJB stubs. |
| Ignore.xml | Default “ignored” instrumentation configuration. |
| CallsToJDBC.xml | Default “caller-side” JDBC instrumentation configuration. |
| OverInstrumentationProtection.xml | Over-instrumentation protection instrumentation configuration. |
| IndepthWeb.xml | Default instrumentation configuration that Precise for Web uses. This file is populated when Precise for Web is installed. |
| TACPeopleSoft.xml | Insight SmartLink for PeopleSoft instrumentation configuration. |
| TACWebApps.xml | Insight SmartLink for Web applications instrumentation configuration |
| Custom.xml | Contains an example instrumentation only. You should use this file as an example and edit this file. |
| CallsFromMethodToMethod.xml | Contains an example instrumentation only. You must edit this file. |
| LeakSeeker.xml | Configuration for Leak Seeker instrumentation. |
| WebLogicEJB.xml | Handles BEA WebLogic-specific EJB “lifecycle operation” instrumentation. |
| WebSphereEJB.xml | Handles IBM WebSphere-specific EJB “lifecycle operation” instrumentation. |
| OracleEJB.xml | Handles Oracle-specific EJB “lifecycle operation” instrumentation. |
| JNDI.xml | Default JNDI instrumentation configuration. |
| DataSource.xml | Default JDBC DataSource instrumentation configuration. |
| EJBBean.xml | Default EJB implementation instrumentation. |
| JTA.xml | Default Java Transaction instrumentation. |
| MessageDrivenEJB.xml | Default Message-Driven EJB instrumentation. |
| JMS.xml | Default Java Messaging Service instrumentation. |
| XML.xml | Default XML and XSL instrumentation. |
| Calls.xml | Template for configuring all calls to and all calls from methods. |
| EJBImpl.xml | Sample EJB implementation instrumentation. |
| Jolt.xml | Sample Jolt instrumentation. |
| MBeanImpl.xml | Sample MBean implementation instrumentation. |
| PeopleSoft.xml | Old PeopleSoft instrumentation. |
| SAP61.xml | SAP 6.1 instrumentation. |
| SmartuneInstrumentation.xml | Optional SmarTune instrumentation for servlet include and session analysis. |
About the structure of instrumenter configuration files
...
The following primitive parameter types names are recognized:
booleanbytechardoublefloatintlongshortvoid
...
The <invoked-method> elements in the <calls-from-method-to-method> element are used to match specific method signatures for specific calls from one method to another. All methods that match the signature are instrumented. Wildcard expressions are not supported and return types are not matched. The <invoked-method> format must be expressed using the same primitive types that were discussed for the <param> element.
...
Table 18-3 Usage of wildcard character *
| Wildcard | Instrumented elements | Non-instrumented elements |
|---|---|---|
| * | xmp.server.Main |
| xmp.task.* | xmp.task.AbstractTask | xmp.server.Main |
| *$* | xmp.task.AbstractTask$1 | xmp.server.Main xmp.task.AbstractTask xmp.task.util.TaskUtilities |
| Info |
|---|
Use wildcard characters only when discovering the methods to instrument. Otherwise, it may result in instrumentation that does not yield meaningful performance metrics but introduces unwanted overhead. Do not implement wildcarded instrumentation in production environments. |
...
<!--leakseeker-if-package>com.bea</leakseeker-if-package>
<!--leakseeker-if-package>weblogic</leakseeker-if-package>
...