IBM BPM, V8.0.1, All platforms > Tuning

Tuning checklist

To tune your IBM BPM system, you need to check different aspects of the system, such as the database and messaging.

Common

• Disable tracing and monitoring when possible.

• Use a high-performance DBMS such as DB2 for z/OS .

• If security is required, use Application security, not Java™ 2 security.

• Use appropriate hardware configuration for performance measurement. The environment should preferably consist of dedicated resources to enable repeatable performance measurements to be obtained. Do not use shared resources, or resources with an availability that can be influenced by other systems.

• If hardware virtualization is used, ensure that adequate processor, memory, and I/O resources are allocated to each virtual machine. Avoid overcommitting resources.
• Do not run production servers in "development mode" or with "development profile".
• Do not use the Unit Test Environment (UTE) for performance measurement.
• Tune external service providers and external interfaces to ensure that they are not the system bottleneck.

• Configure message-drive bean (MDB) activation specs.

• Configure for clustering (where applicable).

• Configure the connection pool size and prepared statement cache size of data sources. Consider using non-XA data sources for Common Event Infrastructure data when that data is non-critical.
• Use proper z/OS Workload Manager (WLM) policy specifications.

Business Process Choreographer

• Use work-manager based navigation for long-running processes.

  If work-manager based navigation is used, also optimize message pool size and inter-transaction cache size.

• Use query tables to optimize query response time.
• Optimize Business Flow Manager resources: database connection (BPEDB), activation specification (BPEInternalActivationSpec), and JMS connection (BPECF and BPECFC).
• Optimize the database configuration for the Business Process Choreographer database (BPEDB).
• Optimize indexes for SQL statements that result from task and process list queries using database tools, such as the DB2 design advisor or Optimization Service Center for DB2 for z/OS, and DB2 Optimization Expert for z/OS.
• Turn off state observers that are not needed; for example, turn off audit logging.

Messaging and message bindings

• Optimize activation specification (JMS, MQJMS, MQ).
• Optimize queue connection factory (JMS, MQJMS, MQ).

• Configure connection pool size (JMS, MQJMS, MQ).

• Configure SIBus data buffer sizes.

Database

• Place database table spaces and logs on a fast disk subsystem.
• Place logs on devices that are separate from table space containers.
• Maintain current indexes on tables.
• Update database statistics.
• Set log file sizes correctly.
• Optimize buffer pool size.
• Review segsize and page sizes for highly-used table spaces and large tables.
• Maintain table space and index space organization by reorganizing the table spaces and index spaces as they become disorganized.

Java

• Set the heap and nursery sizes to manage memory efficiently.
• Choose the appropriate garbage collection policy.
• Choose the appropriate garbage collection policy (generally, -Xgcpolicy:gencon).

Monitor

• Configure Common Event Infrastructure.

Tuning