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.
that can process 10 requests per second with an average response time of one second, can<br />
process approximately 10 requests at the same time:<br />
throughput / response time = concurrency<br />
The throughput capacity of target applications is critical to projecting the end-to-end<br />
throughput of an entire application. Also, consider the concurrency of target applications<br />
when tuning the concurrency levels of the upstream Business Process Manager V8.0-based<br />
components. For example, if a target application can process 10 requests at the same time,<br />
tune the process server components that start this application. By tuning these components,<br />
the simultaneous request from Business Process Manager V8.0 at least matches the<br />
concurrency capabilities of the target.<br />
Additionally, avoid overloading target applications because such configurations do not result<br />
in any increase in overall application throughput. For example, if 100 requests are sent to a<br />
target application that can process only 10 requests at the same time, throughput does not<br />
improve. However, throughput does improve by tuning in a way that the number of requests<br />
made matches the concurrency capabilities of the target.<br />
Service providers that might take a long time to reply, either as part of mainline processing or<br />
in exception cases, do not use synchronous invocations that require a response. Not using<br />
synchronous invocations avoids tying up the business process and its resources until the<br />
service provider replies.<br />
2.4 Client environments (Process Portal, Process Designer,<br />
Business Space)<br />
This section documents best practices for optimizing Business Process Manager Client<br />
environments, which include Process Portal, Process Designer, and Business Space<br />
solutions.<br />
2.4.1 Optimize the topology<br />
The performance of Asynchronous JavaScript and XML (AJAX) applications, such as those<br />
used in Business Process Manager, can be divided into a four-tiered model, as shown in<br />
Figure 2-1. Each tier must be optimized to deliver a high-performing solution. Several details<br />
for optimizing the topology are described later in this paper, but a context for such a<br />
description is presented here.<br />
Dmgr<br />
Server<br />
Application Cluster<br />
Messaging Cluster<br />
Support Cluster<br />
Browser<br />
Network<br />
HTTP<br />
Server<br />
DB<br />
Server<br />
Backend/<br />
Databases<br />
Servers<br />
Figure 2-1 Four tiers of AJAX performance<br />
16 <strong>IBM</strong> Business Process Manager V8.0 Performance Tuning and Best Practices
Change language