Resequencer Basic Tuning Considerations

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 Oracle Business Process Management Tuning 15-5 Bytes Max 800 MB Message Max 1000000 ■ MeasurementTopicConnectionFactory Send Timeout 240000 ■ BPMJMSServer MessageBuffer Size 100000 Note that the BPMJMSServer uses a Paging File and JMSFileStore.

15.4.2 Tuning Process Cubes

Process Cubes perform periodic aggregations to compute workload information. The frequency of these computations is determined by the CubeUpdateFrequency parameter of BPMNConfig mbean and can be changed from the Oracle Enterprise Manager console. In a high volume environment, consider changing this parameter to an appropriately higher value such as 12 hours, for example, to conserve computing resources. Process Cube Aggregator uses the BPM_CUBE_AUDITINSTANCE table to compute workload and performance information. Unwanted records from the BPM_CUBE_ AUDITINSTANCE table get purged as part of the SOA Purge script. Additionally, consider running the following delete script periodically to purge the unwanted records from BPM_CUBE_AUDITINSTANCE table for improving the performance of Process Cube computations. DELETE FROM BPM_CUBE_AUDITINSTANCE A WHERE EXISTS SELECT 1 FROM BPM_CUBE_AUDITINSTANCE B WHERE A.COMPONENTINSTANCEID = B.COMPONENTINSTANCEID AND B.OPERATION=INSTANCE_CREATED AND B.ACTIVITYSTATUS=PROCESSED