Deferred Routing Rules Basic Tuning Considerations

Oracle Business Process Management Tuning 15-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.

15.2.4 Dispatcher Engine Threads

The dspEngineThreads property specifies the total number of threads allocated to process engine dispatcher messages. Engine dispatcher messages are generated whenever an activity must be processed asynchronously. If the majority of processes deployed are durable with a large number of dehydration points mid-process receive, onMessage, onAlarm, and wait activities, greater performance may be achieved by increasing the number of engine threads. Note that higher thread counts can cause greater CPU utilization due to higher context switching costs. 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 30 threads. Any value less than 1 thread is changed to the default.

15.2.5 Dispatcher Invoke Threads

The dspInvokeThreads property specifies the total number of threads allocated to process invocation dispatcher messages. Invocation dispatcher messages are generated for each payload received and are meant to instantiate a new instance. If the majority of requests processed by the engine are instance invocations as opposed to instance callbacks, greater performance may be achieved by increasing the number of invocation threads. Higher thread counts may cause greater CPU utilization due to higher context switching costs. 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 20 threads. Any value less than 1 thread is changed to the default.

15.3 Tuning Oracle Workspace and Worklist Applications

The following settings can be used to tune Oracle Workspace and Worklist applications: Parameter Description HTTP Session Timeout To manage over resource usage, adjust the session timeout value, in minutes, in the web.xml file. The following is a sample snippet of web.xml: session-config session-timeout 5 session-timeout session-config NOTE : If you must modify this property, post deployment, you must edit web.xml manually. See Editing web.xml Properties in Oracle Fusion Middleware Administrators Guide for Oracle WebCenter. 15-4 Oracle Fusion Middleware Performance and Tuning Guide

15.4 Tuning Process Analytics

Tuning Process Analytics includes the following:

15.4.1 Process Measurement

Process Analytics uses measurement events to sample the process and publish measurements to registered consumers. These measurements can be disabled using the BPMN Configuration Disable Sensors. Specific consumers for these measurements can be disabled by setting the BPMN Configuration Disable Actions. For more information, see the Oracle Fusion Middleware Administrators Guide. Measurement events are published on the JMS Topic: MeasurementTopic, and consumed by registered Action MDBs. In order to tune JMS for Measurements, consider changing the following, as needed, in a high volume environment: ■ MeasurementTopic ADF Client State Token Through this setting, you can control the number of pages users can navigate using the browser Back button without losing information. To reduce CPU and memory usage, you can decrease the value in the web.xml file. Default is XXXXX. The following is a sample snippet of web.xml: context-param param-name org.apache.myfaces.trinidad.CLIENT_STATE_ MAX_TOKENS param-name param-value 3 param-value context-param NOTE : If you must modify this property, post deployment, you must edit web.xml manually. See Editing web.xml Properties in Oracle Fusion Middleware Administrators Guide for Oracle WebCenter. Compress_View_State Token This setting controls whether or not the page state is compressed. Zipping greatly reduced the memory being taken up by page state in the session object. The following is a snippet of the web.xml: param-nameorg.apache.myfaces.trinidad.COMPRESS_VIEW_ STATEparam-name param-valuetrueparam-value DISABLE_CONTENT_COMPRESSION By default, style classes that are rendered are compressed to reduce page size. In production environments, make sure you remove the DISABLE_CONTENT_ COMPRESSION parameter from the web.xml file or set it to FALSE. The following is a snippet of the web.xml: param-nameorg.apache.myfaces.trinidad.DISABLE_ CONTENT_COMPRESSIONparam-name param-valuefalseparam-value Parameter Description