Download PDF (1.3 MB) - IBM Redbooks

Turn off auto-tracking in business process diagrams if not required
Auto-tracking is enabled by default for BPDs. This capability is important for many BPDs
because it enables the gathering, tracking, and reporting of key business metrics. However,
an additional cost exists as a result of auto-tracking because the events are processed by the
Performance Data Warehouse and persisted in the database. Disable auto tracking for BPDs
that do not require tracking and reporting business metrics.
Also consider creating tracking groups to only track key business events, and then disable
auto-tracking. This will ensure that the events persisted are only those required for business
metrics.
Avoid business process diagrams (BPDs) that run perpetually
Some BPDs run forever. Although certain business processes must run perpetually, design
this type of BPD only if the capability is strictly required. BPDs that run perpetually continually
poll for new events, which uses server processor resources. Consider using other
communication mechanisms (such as Java Message Service queues) instead of polling. If
polling is necessary, use an undercover agent (UCA) instead of a BPD to do the polling. Also,
disable auto-tracking for these BPDs to avoid excessive traffic to the Performance Data
Warehouse.
Develop efficient coaches
To develop well-performing coaches, consider the following guidelines:
►
►
►
►
Use custom visibility sparingly.
Avoid large, complex coaches.
Avoid large, repeating tables. Page the results instead.
Always wire coaches to end nodes.
Minimize use of large JavaScript scripts
Avoid large JavaScript blocks because JavaScript is interpreted and therefore is slower to
process than other compiled mechanisms such as Java code. Large JavaScript blocks can
also produce very large Document Object Model (DOM) trees, which are expensive for
browsers to process and render. Finally, large JavaScript blocks are often indicative of too
much logic being placed in the Business Process Manager layer.
As a general guideline, limit a JavaScript block to 50 lines. If your implementation exceeds
this value, re-evaluate the design and re-factor the implementation to use smaller JavaScript
blocks.
Avoid direct SQL access to internal Business Process Manager tables
SQL tools provide the capability to access any database table, including internal Business
Process Manager tables such as LSW_TASK, LSW_PROCESS, and so on. Avoid accessing
internal Business Process Manager tables directly, because these are internal tables and the
definition and content of the tables may change in future Business Process Manager
releases. Instead, use published Business Process Manager APIs, such as JavaScript and
REST APIs.
It is also important to avoid storing internal Business Process Manager information in
application-specific persistent storage, because it is difficult to maintain consistency between
the internal Business Process Manager persistent storage and the application's own
persistent storage.
10 IBM Business Process Manager V8.0 Performance Tuning and Best Practices