08.06.2014 Views

Download PDF (1.3 MB) - IBM Redbooks

Download PDF (1.3 MB) - IBM Redbooks

Download PDF (1.3 MB) - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Consider the following hints when tuning the connection pools:<br />

► API calls for task list and process list queries might take more time to respond, depending<br />

on the tuning of the database and the amount of data in the database.<br />

► Ensure that concurrency (parallelism) is sufficiently high to handle the load and to use the<br />

processor. However, increasing the parallelism of API call execution beyond what is<br />

necessary can negatively influence response times. Also, increased parallelism can put<br />

excessive load on the BPC database. When tuning the parallelism of API calls, measure<br />

response times before and after tuning, and adjust the parallelism if necessary.<br />

4.8.5 Tuning intermediate components for concurrency<br />

If the input business object is handled by a single thread from end to end, the tuning for the<br />

edge components is normally adequate. In many situations, however, multiple thread<br />

switches exist during the end-to-end execution path. Tuning the system to ensure adequate<br />

concurrency for each asynchronous segment of the execution path is important.<br />

Asynchronous invocations of an SCA component use an MDB to listen for incoming events<br />

that arrive in the associated input queue. Each SCA module defines an MDB and its<br />

corresponding activation specification (JNDI name is sca/module name/ActivationSpec). The<br />

SCA module MDB is shared by all asynchronous SCA components within the module,<br />

including SCA export components. Take this shared state into account when you configure<br />

the maxConcurrency property value of ActivationSpec. SCA module MDBs use the same<br />

default thread pool as those for JMS exports.<br />

The asynchronicity in a long-running business process occurs at transaction boundaries (see<br />

3.2.9, “Transactional considerations” on page 38 for more details about settings that affect<br />

transaction boundaries). BPE defines an internal MDB and its ActivationSpec as<br />

BPEInternalActivationSpec. The maxConcurrency parameter must be tuned by following the<br />

same guideline as for SCA module and JMS export MDBs (as described in 4.7.3, “Tuning for<br />

maximum concurrency” on page 64).<br />

The only issue is that only one BPEInternalActivationSpec exists for a single Business<br />

Process Manager server.<br />

4.9 Mediation flow component tuning<br />

Additional configuration options are relevant to tuning Mediation Flow Components. These<br />

are described in this section.<br />

See 5.2, “Mediation Flow Component settings” on page 104 for a suggested set of initial<br />

values to use.<br />

4.9.1 Tuning the database if using persistent messaging<br />

If you use persistent messaging, the configuration of your database is important. Use a<br />

remote DB2 instance with a fast disk array as the database server. You might benefit from<br />

tuning the connection pooling and statement cache of the data source.<br />

For more information about tuning DB2, see the following sections:<br />

► 4.13, “General database tuning” on page 80<br />

► 4.14, “DB2-specific database tuning” on page 82<br />

See the relevant references in “Related publications” on page 107.<br />

Chapter 4. Performance tuning and configuration 75

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!