Download PDF (1.3 MB) - IBM Redbooks

►
►
For each Business Process Manager server or messaging engine JVM, use a tool such as
IBM Tivoli® Performance Viewer, or the WebSphere Performance Tuning Toolkit, to
monitor these types of data:
– Data connection pool use for each data source
– Thread pool use for each thread pool (web container, default, and Work Managers)
You may download the WebSphere Performance Tuning Toolkit from this location:
http://www.ibm.com/developerworks/websphere/downloads/peformtuning.html
Monitor the database systems, which includes the databases for the Process Center,
Process Server, Performance Data Warehouse, Business Monitor, and any other
applications that are part of the Business Process Manager solution. Business Process
Manager solutions are often database-intensive, so ensuring excellent performance for
the databases is critical. Use the database vendor’s monitoring tools, along with operating
system tools such as iostat, vmstat, or the equivalent.
4.1.3 Use monitoring data to guide further tuning changes
Correctly using monitoring data to determine how to tune the Business Process Manager
requires skill and experience. In general, this phase of tuning requires the analyst to look at
the collected monitoring data, detect performance bottlenecks, and do further tuning. The key
characteristic of this phase of tuning is that it is driven by the monitoring data that is
collected in the previous phase.
Performance bottlenecks include, but are not limited to, these situations:
► Excessive use of physical resources, such as processor cores, disk, and memory. These
issues can be resolved either by adding more physical resources or by rebalancing the
load across the available resources.
► Excessive use of virtual resources. Examples of these resources include heap memory,
connection pools, thread pools, and other resources. In this case, use tuning parameters
to remove the bottlenecks.
4.1.4 Information required to diagnose and resolve performance issues
Several sources of information are highly valuable, even necessary, when diagnosing and
resolving performance problems. This information is often referred to as must-gather
information. It includes the following items:
► Client (Process Designer or Portal) CPU utilization (for example vmstat)
► Process Center or Process Server CPU utilization
►
►
►
►
Database server CPU, disk subsystem (for example iostat), and network utilization; also,
for Oracle, the AWR Report
The verbosegc logs (even if this problem is not a memory problem)
SystemOut and SystemErr logs
The contents of the configuration directory for the active profile of the server being studied,
for example, the following location:
profile_dir/config/cells/cellName/nodes/nodeName/servers/serverName
Chapter 4. Performance tuning and configuration 49