Network Deployment (Distributed operating systems), v8.0 > End-to-end paths > Data access resources

Enable DB2 Performance Expert Extended Insight

If we have a DB2 database configured in the Application Server, enable DB2 Performance Expert Extended Insight (PEEI) to employ an end-to-end monitoring system for the environment. PEEI features allow you to monitor transactions throughout the system stack and tune your resources according to the comprehensive data reports. Ensure that you meet the following preconditions:

• We must have a backend database with at least version 9.1 of DB2 for Linux, HP-UX, Solaris, or Windows.

• Install fix pack 6 for DB2 v9.1. If you use a version earlier than fix pack 6, server time statistics are not provided.

• Use v3.53.x, including DB2 APAR IZ35480, or later of the DB2 Using IBM JCC Driver or the DB2 Universal JDBC Driver provider.
• Application Server is updated to v7.0.0.1.

DB2 Performance Expert Extended Insight (PEEI) allows you to monitor, identify, and resolve performance issues for your entire stack and not just the database layer. These features provide results with a granularity to accurately pinpoint the cause and the culprit of the issue, allowing you to quickly resolve the problem and minimize downtime for the environment.

When you integrate PEEI monitoring features with Application Server, you will be able to answer the following questions:

• Are my clients configured properly and synchronized with my data servers?
• Is my connection pooling setup sufficient?
• What are the constraints for my clients' system resources?
• What are the top clients, users, applications, SQLs, etc., for my environment?
• Is my network capacity sufficient?
• Which resource consumes most of my network?

Procedure

1. Log into the administrative console.

2. Click Resources > JDBC > JDBC Providers > JDBC_provider.
3. Update the class path for the data source with the pdq.jar file for PEEI. Type the names for the following JAR file:
   • pdq.jar

   Avoid trouble: Class path entries are separated by using the ENTER key and must not contain path separator characters (such as ';' or ':'). Class paths can contain variable (symbolic) names that can be substituted using a variable map.

4. Click OK.

5. Save the configuration.
6. Remove the enableEndToEndMonitoringFeature custom property for the DB2 data source, if it exists.

   For transitioning users: The enableEndToEndMonitoringFeature custom property is deprecated in the WAS V7.0.0.1 environment, because PEEI feature is enabled by default. PEEI can be controlled by the disableEndToEndClientMonitoringFeature custom property, which has a default of false. If you use the enableEndToEndMonitoringFeature custom property, Application Server will issue an OBSOLETE_PROPERTY_SPECIFIED warning.trns

   1. Navigate to Resources > JDBC > JDBC Providers > JDBC_provider.

   2. Click Data sources.

   3. Click the name of the data source.

   4. Click Custom properties.

   5. Select the enableEndToEndMonitoringFeature custom property from the list and select Delete.

   6. Click OK.

   7. Save the configuration.

7. Restart Application Server.

What to do next

PEEI is enabled by default when you configure the JDBC provider with the JAR file.

To control the end-to-end monitoring feature, you can configure a custom property to control the monitoring feature:

1. Navigate to Resources > JDBC > JDBC Providers > JDBC_provider .

2. Click Data sources.

3. Click the name of the data source.

4. Click Custom properties.

5. Click New and enter the following property:

   disableEndToEndClientMonitoringFeature custom property. Set the property value to true.

   Name	Value
   disableEndToEndClientMonitoringFeature	true

Configure a JDBC provider and data source

+

Search Tips   |   Advanced Search