Monitoring Binding Component Instances and Faults

Part XV Part XV Administering Oracle BPMN Process Service Components and Engines This part describes how to administer Oracle BPMN Process Service Components and Engines. This part includes the following chapters: ■ Chapter 36, Configuring Oracle BPMN Process Service Components and Engines ■ Chapter 37, Monitoring BPMN Process Service Components and Engines ■ Chapter 38, Managing Oracle BPMN Service Components and Engines 36 Configuring Oracle BPMN Process Service Components and Engines 36-1 36 Configuring Oracle BPMN Process Service Components and Engines This chapter contains information about the configuration properties that are used by the BPMN process service engine during processing of BPMN service components. This chapter includes the following topics: ■ Section 36.1, Configuring BPMN Process Service Engine Properties ■ Section 36.2, Integrating Oracle BPM with Oracle Business Activity Monitoring

36.1 Configuring BPMN Process Service Engine Properties

To configure BPMN process service engine properties: 1. Access this page through one of the following options: The BPMN Service Engine Properties page displays properties for setting audit trail and large document thresholds, setting dispatcher thread properties, validating payload schema, and setting the audit trail level. 2. Make changes to the service engine properties that are appropriate to your environment. From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... 1. Select SOA Administration BPMN Properties . 1. Right-click soa-infra. 2. Select SOA Administration BPMN Properties . 36-2 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite Property Description Audit Level Select one of the following options: ■ Off : No logging is performed. Composite instance tracking and payload tracking information are not collected. If measurement is enabled, then this level is overridden to Minimal. ■ Inherit default: Logging is the same as the SOA Infrastructure audit level. This allows the BPMN audit level to automatically change when the global setting is changed. Setting a different audit level tracking in this page overrides the tracking set at the SOA Infrastructure level. ■ Minimal : Instance tracking information is collected, but not payload details; no payload details are available in the flow audit trails. ■ Production : Instance tracking information is collected, payload details are collected only for out data associations for asynchronous activities. This level is optimal for most normal operations and testing. ■ Development : Allows both the composite instance tracking and payload tracking. However it may impact the performance. This level is useful mostly for debugging purposes. Note: If you do not want audit entries to be displayed, then you must turn off both the audit level and the metrics. If metrics are enabled, then audit entries are displayed even if the audit level is set to Off. Audit Trail Threshold Enter the maximum size in bytes of an instance audit trail before it is chunked and saved in a dehydration store table separate from the audit trail. If the threshold is exceeded, the View XML link is shown in the audit trail instead of the payload. Large Document Threshold Enter the maximum size of a generated document within a BPMN process component instance before it is stored in a separate table in the dehydration store. Dispatcher System Threads Specify 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 runtime. The default value is 2 threads. Any value less than 1 thread is changed to the default. Dispatcher Invoke Threads Specify 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 service 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 default value is 20 threads. Any value less than 1 thread is changed to the default. Dispatcher Engine Threads Specify the total number of threads allocated to process service engine dispatcher messages. Service 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 midprocess receive, onMessage, onAlarm, and wait activities, greater performance may be achieved by increasing the number of service engine threads. Note that higher thread counts can cause greater CPU utilization due to higher context switching costs. The default value is 30 threads. Any value less than 1 thread is changed to the default.