Page History
...
| Info |
|---|
Precise for J2EE v9.0 introduces the " Monitor Settings " dialog box to the user interface. This dialog box is recommended for configuring most of the common Precise for J2EE instrumentation. For details, see the About configuring Precise for J2EE settings section in the Precise for J2EE User Guide. In some cases, however, it may be preferable to manually perform specific instrumentation. This section describes these cases. |
...
- Open the collector.xml file in the registry folder. Use this file to define a filter on an exception class name, using regular expressions.
- Edit the following tag:
<exceptionFilterByName></exceptionFilterByName>
The default filter tag is:<exceptionFilterByName>.*</exceptionFilterByName> - Run the relevant CLI command as it appears in step 3 of Instance registry or Cluster registry.
| Anchor | ||||
|---|---|---|---|---|
|
To reduce the quantity of collected data and propagate mainly meaningful data, a filtering mechanism is used. This mechanism is used to filter nodes and invocations before loading the data into the PMDB.
...
Table 8-1 Data filtering configuration parameters
| Parameter | Description | ||
|---|---|---|---|
| filteringEnabled | Activates and deactivates data filtering. Type: Boolean Default value: true | ||
filteringMaxInvocationTrees | The maximum number of entry points to keep, based on service time. Type: Integer Default value: 100
| ||
filteringPercent | The minimum percent value of the entry point’s service time necessary to keep a node. Type: Integer Default value: 1
| ||
filteringThreshold | The minimum work time value (milliseconds) threshold to keep a node. Type: Integer Default value: 5
|
Keeping exceptions of filtered invocations
...
Table 8-2 Configurable parameters in the findings-config.xml fileAnchor Table82 Table82
| Parameter | Description |
|---|---|
| max-findings-to-display | The maximum number of findings to be displayed in the user interface. Type: Integer Default value: 7 |
| timeout-in-seconds | The time limit (in seconds) that the findings query will run. Type: Integer Default value: 20 |
enabled |
The finding will only be displayed if it is enabled. Type: Boolean Default value: true | |
| tab | The finding will only be displayed in the specific tab (activity or dashboard) if it is enabled. Type: Boolean Default value: true |
| topN-to-display | The maximum number of times a specific type of findings will be displayed (with different contexts). Type: Integer Default value: 2 |
thresholds | Each finding’s severity is calculated based on finding specific thresholds. Type: Integer |
| Anchor | ||||
|---|---|---|---|---|
|
...
<!--
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.
...
Table 8-3 Minimum permissions for the <i3_root> directory for the application server user
| Directory | Minimum permissions |
|---|---|
<i3_root>/distribution | read, execute |
<i3_root>/infra | read, execute |
<i3_root>/java | read, execute |
<i3_root>/products | read, execute |
<i3_root>/support | read, write, execute |
<i3_root>/logs | read, write, execute |
The following table shows the minimum permissions that you can set for the application server user or group for the <i3_root>/products/j2ee directory.
Table 8-4 Minimum permissions for the <i3_root>/products/j2ee directory for the application server user
| Directory | Minimum permissions |
|---|---|
<i3_root>/products/j2ee | read, execute |
<i3_root>/products/j2ee/archive | read, execute |
<i3_root>/products/j2ee/cache | read, execute |
<i3_root>/products/j2ee/config | read, write, execute |
<i3_root>/products/j2ee/install | read, execute |
<i3_root>/products/j2ee/lib | read, execute |
<i3_root>/products/j2ee/samples | read, execute |
<i3_root>/products/j2ee/support | read, execute |
<i3_root>/products/j2ee/bin | read, execute |
<i3_root>/products/j2ee/classes | read, execute |
<i3_root>/products/j2ee/etc | read, write, execute |
<i3_root>/products/j2ee/installed | read, execute |
<i3_root>/products/j2ee/logs | read, write, execute |
<i3_root>/products/j2ee/smartlink | read, write, execute |
<i3_root>/products/j2ee/tac | read, write, execute |
| Anchor | ||||
|---|---|---|---|---|
|
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
- Open the <LOCAL-LIB>/products/j2ee/config/<JVM-NAME>/collector.xml file for editing.
...
- 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
- Save the file.
...
- 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
- Make sure Precise for Web is installed on the server of the remotely monitored JVM.
...
- Copy the
TacPaterns.xmlfile fromproducts/j2ee/config/on the Precise FocalPoint server
...
- to
products/j2ee/config/folder inside the extracted ZIP folder on the JVM side. If the file does not exist, restart the Precise FocalPoint.
...
- Restart the JVM to start using the patterns defined by
...
- the
TacPaterns.xmlfile.
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>
- Copy the <PRECISE_HOME>/products/j2ee/lib/indepthmetric.jar file into the
<TOMCAT_HOME>/libfolder.
...
- Add the following xml entry to the
<TOMCAT_HOME>/conf/server.xmlfile 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>
- Copy the <PRECISE_HOME>/products/j2ee/etc/metrics/JBOSS/
...
- <VERSION>/Precise for J2EE-startupclass.sar file into the
...
- <JBOSS_
...
- HOME>/server/
...
- <YOUR_
...
- SERVER>/deploy folder.
...
- 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
- Open the <LOCAL-LIB>/products/j2ee/config/<JVM-NAME>/InstrumenterConfigList.xml file for editing.
...
- Add the following XML node under the root node:
<config-file>
ExceptionSeeker.xml</config-file>
...
- Restart the JVM.
To disable the Exception Seeker feature1. Delete
- Delete this node inside the
InstrumenterConfigList.xml
...
- .
...
- Restart the JVM.
Enabling/Disabling Leak Seeker
To enable the Leak Seeker feature1. Open the <LOCAL-LIB>
- Open the <LOCAL-LIB>/products/j2ee/config/
...
- <JVM-
...
- NAME>/InstrumenterConfigList.xml file for editing.
...
- Add the following XML node under the root node:
<config-file>
LeakSeeker.xml</config-file>
...
- Restart the JVM.
To disable the Leak Seeker feature1. Delete
- Delete this node inside the
InstrumenterConfigList.xmlfile.
...
- Restart the JVM.
Precise. Performance intelligence from click to storage. Learn more > >
...
...