Page History
...
| Anchor | ||||
|---|---|---|---|---|
|
...
| 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. |
In Precise for J2EE v9.0, the installation and configuration directories for all instances (for all installation types) are centrally located in the registry, installed on a central JVM defined as the host, with the following path: products\i3fp\registry\. Whenever the JVMs are restarted, they are configured according to the information found in the XML files located in the registry folder. As a result, any change made to a file in the registry will take affect after a JVM restart.
In addition to the registry configuration files, local directories still exist on each JVM. The file system path of the local Precise installation directory is <i3_root>. <i3_root> may also be called the Precise root directory, such as PreciseSoftware.
The Precise for J2EE products directory path is \<i3_root>\products\j2ee.
The JVM identifier that was chosen or given (depending on the installation type) during installation is referred to as JVMID. The JVMID directory is used to store JVM-specific settings. It is referred to within the file system paths, such as \i3\products\j2ee\config\JVMID. For example, if you choose PetStore as a JVMID, the JVMID directory would be \i3\products\j2ee\config\PetStore.
Any changes made on a local directory will immediately take effect, but only until the next JVM restart, when the JVM will reload the configuration found in the registry and override the local changes.
...
This section describes the following monitoring settings:
• 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 JVM
1. Open the <LOCAL-LIB>/products/j2ee/config/<JVM-NAME>/collector.xml file for editing.
2. 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 the file.
2. 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 pattern
1. Make sure Precise for Web is installed on the server of the remotely monitored JVM.
2. Copy the TacPaterns.xml file from products/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.
3. Restart the JVM to start using the patterns defined by the TacPatterns.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 class
1. Copy the <PRECISE_HOME>/products/j2ee/lib/indepthmetric.jar file into the <TOMCAT_HOME>/lib folder.
2. 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_HOME>/products/j2ee/etc/metrics/TOMCAT/<VERSION>/measurements.xml file to the <PRECISE_HOME>/products/j2ee/config/<JVM_ID> folder.
WebLogic <VERSION>
• Choose a default list of metrics
Copy the <PRECISE_HOME>/products/j2ee/etc/metrics/WEBLOGIC/<VERSION>/measurements.xml file to the <PRECISE_HOME>/products/j2ee/config/<JVM_ID> folder.
WebSphere <VERSION>
• Choose default list of metrics.
Copy the
<PRECISE_HOME>/products/j2ee/etc/metrics/WEBSPHERE/<VERSION>/measurements.xml file to the <PRECISE_HOME>/products/j2ee/config/<JVM_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 class
1. 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.
2. Choose a default list of metrics
Copy the <PRECISE_HOME>/products/j2ee/etc/metrics/JBOSS/<VERSION>/measurements.xml file to the <PRECISE_HOME>/products/j2ee/config/<JVM_ID> folder.
Enabling/Disabling Exception Seeker
To enable the Exception Seeker feature
1. Open the <LOCAL-LIB>/products/j2ee/config/<JVM-NAME>/InstrumenterConfigList.xml file for editing.
2. Add the following XML node under the root node:
<config-file> ExceptionSeeker.xml
</config-file>
3. Restart the JVM.
To disable the Exception Seeker feature
1. Delete this node inside the InstrumenterConfigList.xml file.
2. Restart the JVM.
Enabling/Disabling Leak Seeker
To enable the Leak Seeker feature
1. Open the <LOCAL-LIB>/products/j2ee/config/<JVM-NAME>/InstrumenterConfigList.xml file for editing.
2. Add the following XML node under the root node:
<config-file> LeakSeeker.xml
</config-file>
3. Restart the JVM.
To disable the Leak Seeker feature
1. Delete this node inside the InstrumenterConfigList.xml file.
2. Restart the JVM.
Precise. Performance intelligence from click to storage. Learn more > >
...