IBM BPM, V8.0.1, All platforms > Tuning

Advanced tuning

Advanced tuning includes configuring tracing and monitoring, and other tuning considerations for large objects, maximum concurrency, messaging, clustered topologies, databases, and Business Process Management products.

• Tracing and monitoring considerations
  The ability to configure tracing and monitoring at different levels for a variety of system components can be extremely valuable during periods of system analysis or debugging.
• Tuning for large objects
  The Java™ heap size and concurrent processing within the JVM are factors to consider when configuring tuning for large objects.
• Tuning for maximum concurrency
  For most high-volume deployments on server-class hardware, many operations take place simultaneously. Tuning for maximum concurrency ensures that the server accepts enough load to saturate its processors.
• Messaging tuning
  Use the following information to tune the WebSphere Application Server for z/OS messaging engines.
• Business Process Choreographer tuning
  The following considerations apply for tuning Business Process Choreographer: tuning the navigation mode, task list and process list queries, and API calls.
• Performance tuning for IBM Integration Designer
  

  If an application fails to run or cycles for a long time without completing, those situations might be caused by insufficient memory. While some of the techniques for improving performance are applied to the server, you can also do some useful analysis in Integration Designer.

• Tuning for Process Portal spaces
  A set of configuration options are relevant for tuning Process Portal spaces.
• Tuning the REST interface for federated BPM resources
  The federated REST API can become a bottleneck if your federation domains contain more than two systems and you have many clients that interact concurrently with the federated BPM REST API. A common cause of this problem is that the thread pool does not have enough threads to handle the service requests from the clients.
• Enterprise Service Bus tuning
  A set of configuration options are relevant for tuning the Enterprise Service Bus.
• Clustered topology tuning: Apply a data-driven scaling methodology
  In general, there are two primary reasons to consider when evaluating moving to a clustered topology from a single-server configuration: scalability or load balancing to improve overall performance and throughput, and high availability or failover to prevent loss of service due to hardware or software failures.
• Changing the configuration topology
  

  You can change the IBM BPM configuration topology by moving components from one topology to another topology that better addresses the processing requirements of your business.

• IBM Business Monitor tuning
  A set of configuration options are relevant for tuning IBM Business Monitor.
• Process search optimization
  

  You can optimize your process searches by using the saved search acceleration tools.

• Database: general tuning
  A set of considerations apply for tuning databases.
• Database: DB2 for z/OS specific tuning
  A few general rules can assist in improving the performance of DB2 environments.
• Advanced Java heap tuning
  Because the Business Process Management product set is written in Java, the performance of the Java Virtual Machine (JVM) has a significant impact on the performance delivered by these products. JVMs externalize multiple tuning parameters that can be used to improve both editor and runtime performance. The most important of these are related to garbage collection and setting the Java heap size.

Tuning