Download PDF (1.3 MB) - IBM Redbooks
Download PDF (1.3 MB) - IBM Redbooks
Download PDF (1.3 MB) - IBM Redbooks
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
5.1 Business Process Manager server settings<br />
This section provides settings based on <strong>IBM</strong> internal performance evaluations of the<br />
Business Process Manager V8.0 server. These settings were derived by using the tuning<br />
methodology and guidelines described in Chapter 4, “Performance tuning and configuration”<br />
on page 47. Consider these settings useful starting points for your use of this product. For<br />
settings that are not listed, use the default settings that are supplied by the product installer<br />
as a starting point, and then follow the tuning methodology specified in 4.1, “Performance<br />
tuning methodology” on page 48.<br />
Three settings are described in this section:<br />
► A three-tiered configuration for Business Process Execution Language (BPEL) business<br />
processes, with the production database on a separate server.<br />
► A three-tiered configuration for Business Processing Modeling Notation (BPMN) business<br />
processes, with the production database on a separate server.<br />
► A two-tiered (client/server) configuration for BPEL business processes, with the production<br />
database collocated on the server.<br />
5.1.1 Three-tiered: Using BPEL business processes with web services and<br />
remote DB2 system<br />
Through the WebSphere Application Server, we used a three-tiered configuration in our<br />
internal performance work to evaluate the performance of a BPEL business process that<br />
models automobile insurance claims processing. This configuration is an example of many<br />
production environments where DB2 is on a separate system than the Business Process<br />
Manager server. The web services binding was used for communications. The business<br />
process has two modes of operation:<br />
►<br />
►<br />
A BPEL microflow (straight-through process) that processes claims where no human<br />
intervention is required<br />
A BPEL microflow plus macroflow (long-running process) pattern, where the macroflow is<br />
started when a review or approval is required (for example, if the claim amount is above a<br />
certain limit)<br />
Three systems were used in this configuration:<br />
► Request driver<br />
► Business Process Manager V8.0 server<br />
► DB2 database server<br />
The Business Process Manager server and the DB2 database server required extensive<br />
tuning to maximize throughput. Some tuning varied because of the operating system (such as<br />
AIX and Windows) and the number of processor cores. These variations are presented in<br />
tabular format, after the description of common tuning.<br />
For all topologies in this section, we suggest you complete the following actions to tune<br />
Business Process Manager and DB2 and maximize throughput:<br />
► Use the production template.<br />
► Define the Common database as local DB2 type 4.<br />
►<br />
Establish BPEL Business Process support with bpeconfig.jacl. Click Data sources <br />
BPEDataSourceDb2 WebSphere Application Server data source properties<br />
statement cache to 300.<br />
98 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices
Change language