Download PDF (1.3 MB) - IBM Redbooks

4.6 Process Center tuning
Because all Process Designer users access the Process Center, and for many cases use a
significant number of resources on the Process Center (and its database), optimizing its
configuration is essential. At a minimum, tune the Process Center in the following ways:
►
►
►
Ensure there is a high-bandwidth, low-latency network connection between Process
Designer users and the Process Center, and the Process Center and its database.
Use a 64-bit JVM.
Use the generational concurrent garbage collector through the following argument:
-Xgcpolicy:gencon JVM
► Ensure that the Java heap size is sufficiently large to handle the peak load. For more
information about setting the Java heap size, see 4.3.2, “Java memory management
tuning parameters” on page 53
► Set the object request broker (ORB) thread pool size to at least 50.
►
►
Set the maximum Java Database Connectivity (JDBC) connections for the Process Server
data source (jdbc/TeamWorksDB) to at least double the maximum number of threads in the
ORB thread pools for each node in the cell. For example, if two Process Center nodes
exist, and the ORB service thread pool of each node is set to a maximum of 50 threads,
set the Process Server data source to accept at least 200 connections.
Tune the Process Center database. For example, ensue the buffer pool or cache size is at
least 2 GB. For more information, see 4.13, “General database tuning” on page 80.
4.7 Advanced tuning
This section describes various advanced tuning tips.
4.7.1 Tracing and monitoring considerations
The ability to configure tracing and monitoring at different levels for various system
components is valuable during periods of system analysis or debugging. The Business
Process Manager product set provides rich monitoring capabilities, both in terms of business
monitoring through the CEI and audit logging, and system performance monitoring through
the PMI and the Application Response Measurement (ARM) infrastructure. Although these
capabilities provide insight into the performance of the running solution, these features can
degrade overall system performance and throughput.
Tracing and monitoring effect on performance: Use tracing and monitoring judiciously.
When possible, turn off all non-essential tracing and monitoring to ensure optimal
performance.
Most tracing and monitoring behaviors are controlled through the administrative console.
Validate that the appropriate level of tracing and monitoring is set for the PMI monitoring,
logging, and tracing settings through the administrative console.
Use the administrative console to validate that the Audit logging and Common Event
Infrastructure logging check boxes are cleared in the Business Flow Manager and the
Human Task Manager, unless these capabilities are required for business reasons.
62 IBM Business Process Manager V8.0 Performance Tuning and Best Practices