IBM BPM, V8.0.1, All platforms > Tuning > Advanced tuning > Tuning for maximum concurrency

Tune intermediate components for concurrency

If the input BO is handled by a single thread from end to end, the tuning for the edge components is normally adequate. In many situations, however, there are multiple thread switches during the end-to-end execution path. It is important to tune the system to ensure adequate concurrency for each asynchronous segment of the execution path.

Asynchronous invocations of a Service Component Architecture component use an MDB to listen for incoming events that arrive in the associated input queue. Each SCA module defines an MDB and its corresponding activation specification (JNDI name: sca/module name/ActivationSpec).

The SCA module MDB is shared by all asynchronous SCA components within the module, including SCA export components. Take this into account when configuring the maxConcurrency property value of the ActivationSpec. SCA module MDBs use the same default thread pool as those for JMS exports.

The asynchrony in a long-running BPEL process occurs at transaction boundaries. BPE defines an internal MDB and its ActivationSpec: BPEInternalActivationSpec. If you use JMS navigation, rather then the default Work-Manager-based navigation, tune the maxConcurrency parameter using the same guidelines as for SCA module and JMS export MDBs.

Tuning for maximum concurrency

Related concepts:
Tune MDB ActivationSpec properties