Tune > Performance


Performance monitoring using the WebSphere Commerce PMI module


Overview

You can monitor the performance of the WebSphere Commerce system by using the WebSphere Application Server Performance Monitoring Infrastructure (PMI).

The WebSphere Commerce application server gathers statistics for URLs, tasks, and views. Each data key has an associated set of counters that provide information about such things as average response time of a task, maximum and minimum response times, the total number of times a task was called, and so on.

To disable the WebSphere Commerce performance monitoring module:

  1. Open the WebSphere Commerce configuration file.

  2. Find the component containing the class name:

      com.ibm.commerce.performance.monitor.PerfMonitor

  3. Change the enable attribute to false.

  4. Save changes and exit the file.


View Commerce PMI module statistics

To view Commerce PMI module data, from the dmgr console...

The data is grouped according to Tasks, URLs, and Views under the Store ID. Note that task commands are found only under StoreId=0.

Once a particular URL, View or Task command is selected from the Resource Selection Panel, the Counter Selection Panel will display the WebSphere Commerce counter.

If you do not see the WebSphere Commerce counter in the Tivoli Performance Viewer, enable the PMI for Commerce Counter Group. From the PMI page, select...

From here you can find and enable the Commerce Counter Group. Ensure that all the counters within a particular URL have been enabled.

These are the counters that are included for each task, URL, or view. Note that all timing values are elapsed time (usually in milliseconds where appropriate):


Monitor Java resources using Tivoli Performer Viewer

From the Application server side, Tivoli Performance Viewer can be used to monitor resources inside the running JVM.

Tivoli Performance Viewer (TPV) provides a graphical interface to capture and display various resources such as the current size of the Web container thread pool or the response time of individual EJBs. Even though some of the data may be tempting to measure, it is potentially expensive to capture and may have a performance impact to the overall system.

Here are some resources of interest, which you can monitor using TPV:


+

Search Tips   |   Advanced Search