Download PDF (1.3 MB) - IBM Redbooks

3.1 Process Designer development best practices
The following best practices pertain to the development of high-performance business
processes using the Process Designer.
3.1.1 Clear variables in exposed human services that are not intended to end
Data from a taskless human service is not garbage-collected until the service reaches the
endpoint. If a human service is developed that is not intended to reach an endpoint, such as a
single page or redirect, then memory is not garbage-collected until the Enterprise JavaBeans
(EJB) timeout occurs (two hours by default). To reduce memory use for these human
services, set variables in the coach to null in a custom HTML block.
3.1.2 Do not use multi-instance loops in the system lane or for batch activities
Where possible, avoid using sub-BPDs as the activity of a multi-instance loop (MIL). This step
is not an issue if the first activity is a user task instead of a system lane task. However, do not
use MILs for batch or system lane activities. This pattern can generate an excessive number
of tokens for the BPD to process. Also, activities in MILs in the system lane are run on a
single thread, which is clearly not optimal on multiprocessor core servers.
Figure 3-1 shows an example of a poor BPD design pattern.
Figure 3-1 Poor BPD design pattern
24 IBM Business Process Manager V8.0 Performance Tuning and Best Practices