Change in Support for Multiple BPEL Implementations

10-8 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF dspEngineThreads dspEngineThreads The total number of threads that will be allocated to process engine dispatcher messages. Engine dispatch messages are generated whenever an activity must be processed asynchronously by the BPEL engine. If the majority of processed deployed on the BPEL server are durable with a large number of dehydration points mid-process receive, onMessage, onAlarm, wait, greater performance may be achieved by increasing the number of engine threads. Note that higher threads counts may cause greater CPU utilization due to higher context switching costs. The 10g default value is 30 threads. Any value less than 1 thread will be changed to the default. dspInvokeAllocFactor NA The percentage of active threads that should be tasked to process incoming invocation messages. After a thread has finished processing a message it may be retasked to process an engine or invocation message, depending upon the current thread allocation situation. This property was replaced by dspInvokeThreads in 10g Release 3 10.1.3.4. The 10.1.3.1.0 default value is 0.4 40 percent. dspInvokeThreads dspInvokeThreads The total number of threads that will be allocated to process engine dispatcher messages. Engine dispatch messages are generated whenever an activity must be processed asynchronously by the BPEL engine. If the majority of processed deployed on the BPEL server are durable with a large number of dehydration points mid-process receive, onMessage, onAlarm, wait, greater performance may be achieved by increasing the number of engine threads. Note that higher threads counts may cause greater cpu utilization due to higher context switching costs. The 10g default value is 30 threads. Any value less than 1 thread will be changed to the default. dspMaxThreads NA The maximum number of active threads that will be processing messages during peak load times. This is the simplest way to throttle the performance of the domain. The maximum value is dependent upon the application server or OS configuration. This property was replaced by dspEngine|Invoke|SystemThreads in 10.1.3.4.0. The 10.1.3.1.0 default value is 100 threads. dspMinThreads NA The minimum number of active threads that will be processing messages during peak load times. If the current number of active threads is under this number the load factor is not taken into consideration when determining if a new thread should be allocated or not. This property was replaced by dspEngine|Invoke|SystemThreads in 10.1.3.4.0. The 10.1.3.1.0 default value is 5 threads. Table 10–1 Cont. Domain Descriptor Properties in Oracle BPEL Process Manager 10g and 11g Oracle BPEL Process Manager 10g in domain.xml file Oracle BPEL Process Manager 11g MBean Property Description Upgrading Oracle BPEL Process Manager Applications 10-9 dspSystemThreads dspSystemThreads The total number of threads that will be allocated to process system dispatcher messages. System dispatch messages are general housecleaning 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 runtime. The 10g default value is 2 threads. Any value less than 1 thread will be changed to the default. expirationMaxRetry expirationMaxRetry The maximum number of times a failed expiration call waitonAlarm will be retried before failing. If the activity or instance the expiration call is targeting cannot be found, the call will be rescheduled again. The 10g default is 5. expirationRetryDelay expirationRetryDelay The amount of time in seconds to wait before rescheduling a failed expiration call. The 10g default value is 120 seconds. instanceKeyBlockSize instanceKeyBlockSize The size of the block of instance ids to allocate from the dehydration store during each fetch. Instance ids for instantiated instances are pre-allocated from the dehydration store and kept in-memory. Once all of the in-memory instance ids have been exhausted, the next request will retrieve the next block from the dehydration store. Generally, the higher the block size, the less impact fetching instance ids will have on the overall performance of the engine as the cost of allocating the block is amortized over a larger number of instances. The only downside to a large block size is the gap between instances in a clustered installation as each node will have its own in-memory block of instance ids and wasting instance ids if the engine is shutdown and the block is not utilized fully. The 10g default value is 10000. largeDocumentThreshold largeDocumentThreshold The maximum size in bytes a BPEL variable can be before it is stored in a separate location from the rest of the instance scope data. Large XML documents will severely impact the performance of the entire BPEL server if they are constantly read-in and written-out whenever processing on an instance must be performed. By writing the variable to separate storage the performance impact is limited to times when the variable is explicitly used in a BPEL activity. The 10g default value is 50 kilobytes. minBPELWait minBPELWait The minimum amount of time allowed for a BPEL wait duration. Wait times shorter than this duration will not be respected and will essentially be skipped altogether. The 10g default value is 2 seconds. Table 10–1 Cont. Domain Descriptor Properties in Oracle BPEL Process Manager 10g and 11g Oracle BPEL Process Manager 10g in domain.xml file Oracle BPEL Process Manager 11 g MBean Property Description