Page History

...

<!--
BEA Jolt custom instrumentation
-->
<config-file>
     Jolt.xml
</config-file>

To enable Java method argument capture, add a custom instrumentation element to an enabled instrumentation configuration file. The following example shows one of these elements that are configured for bea.jolt.JoltRemoteService. The example is taken from the Jolt.xml instrumentation configuration file that is distributed with Precise for J2EE. In this example, we display the Tuxedo service name whenever the bea.jolt.JoltRemoteService.call method is executed. A complication is that the Tuxedo service name is specified in the bea.jolt.JoltRemoteServiceconstructor (init) method and not passed directly to each execution of call.

...

This section describes the following monitoring settings:•    Time

• Time slice size

...

• Using Web patterns

...

• Enabling/Disabling JMX data collection

...

• Enabling/Disabling Exception Seeker

...

• Enabling/Disabling Leak Seeker

For information about installing a remote J2EE instance, see the Installing the J2EE remote instance in the Precise CLI Utilities Reference Guide.

Time slice size

Currently 2 time slice sizes are supported: 30 seconds, 5 minutes. To change the slice size setting for a monitored JVM1.    Open

1. Open the <LOCAL-LIB>/products/j2ee/config/<JVM-NAME>/collector.xml file for editing.

...

1. Edit the value of the <agginterval> node and specify one of the following supported values in seconds: 30 or 300.

For example: <agginterval>30</agginterval>1.    Save

1. Save the file.

...

1. Restart the JVM for the changes to take effect.

Using Web patterns

Perform the following steps to apply URL patterns defined for the Web instance. To define a pattern1.    Make

1. Make sure Precise for Web is installed on the server of the remotely monitored JVM.

...

1. Copy the TacPaterns.xml file from products/j2ee/config/ on the Precise FocalPoint server

...

1. to products/j2ee/config/ folder inside the extracted ZIP folder on the JVM side. If the file does not exist, restart the Precise FocalPoint.

...

1. Restart the JVM to start using the patterns defined by

...

1. the TacPaterns.xml file.

Enabling/Disabling JMX data collection

To enable/disable JMX data collection, choose the corresponding the Application Server vendor below and perform the procedure described for the vendor.

Tomcat <VERSION>

...

Enable the Application Server Metrics

To enable Precise for J2EE to collect Application Server Metrics, a startup class must be loaded and executed on the server being monitored.

To configure the startup class1.    Copy the <PRECISE_HOME>

1. Copy the <PRECISE_HOME>/products/j2ee/lib/indepthmetric.jar file into the <TOMCAT_HOME>/lib folder.

...

1. Add the following xml entry to the <TOMCAT_HOME>/conf/server.xml file just below the other
   <Listener> entries: <Listener className="com.precise.javaperf.extensions.tomcat.JMXMetricsLoaderListener"/>

...

Choose a default list of metrics

Copy the <PRECISE<PRECISE_HOME>HOME>/products/j2ee/etc/metrics/TOMCAT/<VERSION><VERSION>/measurements.xml file to the <PRECISE<PRECISE_HOME>HOME>/products/j2ee/config/<JVM<JVM_ID> ID> folder.

WebLogic <VERSION>

...

Choose a default list of metrics

Copy the <PRECISE<PRECISE_HOME>HOME>/products/j2ee/etc/metrics/WEBLOGIC/<VERSION><VERSION>/measurements.xml file to the <PRECISE<PRECISE_HOME>HOME>/products/j2ee/config/<JVM<JVM_ID> ID> folder.

WebSphere <VERSION>

...

Choose default list of metrics.

Copy the
<PRECISE_HOME><PRECISE_HOME>/products/j2ee/etc/metrics/WEBSPHERE/<VERSION><VERSION>/measurements.xml file to the <PRECISE<PRECISE_HOME>HOME>/products/j2ee/config/<JVM<JVM_ID> ID> folder.

Jboss <VERSION>

...

Enable the Application Server Metrics

To enable Precise for J2EE to collect Application Server Metrics, a startup class must be loaded and executed on the server being monitored.

To configure the start up class1.    Copy the <PRECISE_HOME>

1. Copy the <PRECISE_HOME>/products/j2ee/etc/metrics/JBOSS/

...

1. <VERSION>/Precise for J2EE-startupclass.sar file into the

...

1. <JBOSS_

...

1. HOME>/server/

...

1. <YOUR_

...

1. SERVER>/deploy folder.

...

1. Choose a default list of metrics

Copy the <PRECISE<PRECISE_HOME>HOME>/products/j2ee/etc/metrics/JBOSS/<VERSION><VERSION>/measurements.xml file to the <PRECISE<PRECISE_HOME>HOME>/products/j2ee/config/<JVM<JVM_ID> ID> folder.

Enabling/Disabling Exception Seeker

To enable the Exception Seeker feature1.    Open

1. Open the <LOCAL-LIB>/products/j2ee/config/<JVM-NAME>/InstrumenterConfigList.xml file for editing.

...

1. Add the following XML node under the root node:
   <config-file>
     ExceptionSeeker.xml
</config-file>

...

1. Restart the JVM.

To disable the Exception Seeker feature1.    Delete

1. Delete this node inside the InstrumenterConfigList.xml

...

1. .

...

1. Restart the JVM.

Enabling/Disabling Leak Seeker

To enable the Leak Seeker feature1.    Open the <LOCAL-LIB>

1. Open the <LOCAL-LIB>/products/j2ee/config/

...

1. <JVM-

...

1. NAME>/InstrumenterConfigList.xml file for editing.

...

1. Add the following XML node under the root node:
   <config-file>
     LeakSeeker.xml
</config-file>

...

1. Restart the JVM.

To disable the Leak Seeker feature1.    Delete

1. Delete this node inside the InstrumenterConfigList.xml file.

...

1. Restart the JVM.

Precise. Performance intelligence from click to storage. Learn more > >

...