Consider the Ordering of Tests in Rule Conditions

Oracle BPEL Process Manager Performance Tuning 13-3 The minimum number of threads for this thread pool is 1 and it cannot be set to 0 a or negative number. The default value is 2. Any value less than 1 thread is changed to the default.

13.2.1.4 Dispatcher Maximum Request Depth

The dspMaxRequestDepth property sets the maximum number of in-memory activities to process within the same request. After processing an activity request, Oracle BPEL Process Manager attempts to process as many subsequent activities as possible without jeopardizing the validity of the request. Once the activity processing chain has reached this depth, the instance is dehydrated and the next activity is performed in a separate transaction. If the request depth is too large, the total request time can exceed the application server transaction time out limit.This process is applicable to durable processes. The default value is 600 activities.

13.2.2 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. Note: Note that the minimum number of threads for each thread pool is 1. dspThreads can not be set to 0 or negative. 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. 13-4 Oracle Fusion Middleware Performance and Tuning Guide

13.2.3 OneWayDeliveryPolicy

The oneWayDeliveryPolicy is from the Oracle 10g configuration property deliveryPersistencePolicy. The new configuration property name is bpel.config.oneWayDeliveryPolicy. The oneWayDeliveryPolicy property controls database persistence of messages entering Oracle BPEL Server. By default, incoming requests are saved in the delivery service database table dlv_message. These requests are later acquired by Oracle BPEL Server worker threads and delivered to the targeted BPEL process. This property persists delivery messages and is applicable to durable processes. If you set the oneWayDeliveryPolicy property to async.cache and your system fails, you may lose messages. In addition, the system can become overloaded messages become backlogged in the scheduled queue and you may receive out-of-memory errors. Consult your own use case scenarios to determine if this setting is appropriate. One-way invocation messages are stored in the delivery cache until delivered. If the rate at which one-way messages arrive is much higher than the rate at which Oracle BPEL Server delivers them, or if the server fails, messages may be lost.

13.2.4 StatsLastN

The StatsLastN property sets the size of the most-recently processed request list. After each request is finished, statistics for the request are kept in a request list. A value less than or equal to 0 disables statistics gathering. To optimize performance, consider disabling statistics collection if you do not need them. This property is applicable to both durable and transient processes. The default value is -1.

13.2.5 AuditDetailThreshold

The auditdetailthreshold property sets the maximum size in kilobytes of an audit trail details string before it is stored separately from the audit trail. If an audit trail details string is larger than the threshold setting, it is not immediately loaded when the audit trail is initially retrieved; a link is displayed with the size of the details WARNING: If you set this property to async.cache and your system fails, you may lose messages. For more information, refer to the Oracle BPEL Process Manager Administrators Guide. Value Description async.persist Default Delivery messages are persisted in the database. With this setting, reliability is obtained with some performance impact on the database. In some cases, overall system performance can be impacted. async.cache Incoming delivery messages are kept only in the in-memory cache. If performance is preferred over reliability, this setting should be considered. sync Directs Oracle BPEL Server to bypass the scheduling of messages in the invoke queue, and invokes the BPEL instance synchronously. In some cases this setting can improve database performance.