Tables Impacted By Instance Data Growth

14-4 Oracle Fusion Middleware Performance and Tuning Guide You can fine tune Resequencer by setting the value of the following properties in the Mediator Service Engine Properties page: ■ ResequencerWorkerThreadCount: Specifies the worker thread count. Default is 4. ■ ResequencerMaxGroupsLocked: Specifies the maximum number of groups locked in each iteration. Default is 4. ■ ResequencerLockerThreadSleep: Specifies the sleep interval for the locker threads in seconds. Default is 10.

14.3 Event Delivery Network EDN Tuning

The Event Delivery Network EDN delivers events published by Oracle Mediator, Oracle BPEL Process Manager components, and external publishers such as Oracle Application Development Framework entity objects. To improve performance of the Event Delivery Network, consider increasing the thread count default is 3. This property can be modified through WLST. For more information, see Section 11.3, Modifying SOA Configuration Parameters . 15 Oracle Business Process Management Tuning 15-1 15 Oracle Business Process Management Tuning The Oracle Business Process Management BPM Suite provides a seamless integration of all stages of the application development life cycle from design-time and implementation to run-time and application management. This chapter contains the following sections: ■ Section 15.1, About Oracle Business Process Management ■ Section 15.2, Basic Tuning Considerations ■ Section 15.3, Tuning Oracle Workspace and Worklist Applications ■ Section 15.4, Tuning Process Analytics

15.1 About Oracle Business Process Management

The Oracle BPM Suite provides an integrated environment for developing, administering, and using business applications centered around business processes. BPM is layered on the Oracle SOA Suite and shares many of the same product components, including Business Rules, Human Workflow, and Oracle Adapter Framework for Integration. For more information on on using BPM, see the Oracle Fusion Middleware Users Guide for Oracle Business Process Management.

15.2 Basic Tuning Considerations

This section describes the following basic BPM performance tuning properties: ■ Audit Level ■ LargeDocumentThreshold ■ Dispatcher System Threads ■ Dispatcher Engine Threads ■ Dispatcher Invoke Threads Note: The configuration examples and recommended settings described in this chapter are for illustrative purposes only. Consult your own use case scenarios to determine which configuration options can provide performance improvements. 15-2 Oracle Fusion Middleware Performance and Tuning Guide

15.2.1 Audit Level

The auditLevel property sets the audit trail logging level. This configuration property is applicable to both durable and transient processes. This property controls the amount of audit events that are logged by a process. Audit events result in more database inserts into the audit_trail table which may impact performance. Audit information is used only for viewing the state of the process from Oracle Enterprise Manager Console. Use the Off value if you do not want to store any audit information. Always choose the audit level according to your business requirements and use cases. For more information on setting the audit level, see Understanding the Order of Precedence for Audit Level Settings in Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite.

15.2.2 LargeDocumentThreshold

The largedocumentthreshold property sets the large XML document persistence threshold. This is the maximum size in kilobytes of a BPMN Data Object before it is stored in a separate location from the rest of the instance scope data. This property is applicable to both durable and transient processes. Large XML documents impact the performance of the entire Oracle BPM Runtime if they are constantly read in and written out whenever processing on an instance must be performed. The default value is 10000 100 kilobytes. 15.2.3 Dispatcher System Threads The dspSystemThreads property specifies the total number of threads allocated to process system dispatcher messages. System dispatcher messages are general clean-up tasks that are typically processed quickly by the server for example, releasing stateful message beans back to the pool. Typically, only a small number of threads are required to handle the number of system dispatch messages generated during run time. Value Description Inherit Inherits the audit level from infrastructure level. Off No audit events activity execution information are persisted and no logging is performed; this can result in a slight performance boost for processing instances. Minimal All events are logged; however, no audit details variable content are logged. Error Logs only serious problems that require immediate attention from the administrator and are not caused by a bug in the product. Using this level can help performance. Production All events are logged. The audit details for assign activities are not logged; the details for all other activities are logged. Development All events are logged; all audit details for all activities are logged.