|Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite
11g Release 1 (11.1.1)
Part Number E10226-04
This chapter describes how to configure BPEL process service components and service engines.
This chapter includes the following topics:
You can configure BPEL process service engine properties. The properties are used by the BPEL process service engine during processing of BPEL service components.
To configure BPEL process service engine properties:
Access this page through one of the following options:
|From the SOA Infrastructure Menu...||From the SOA Folder in the Navigator...|
The BPEL 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.
Make changes to the service engine properties that are appropriate to your environment.
|Audit Level||Select one of the following options:
|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 BPEL 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 run time.|
|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 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.|
|Dispatcher Engine Threads||Specify 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 (midprocess 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.|
|Payload Validation||Select to enable validation of inbound and outbound messages. Nonschema-compliant payload data is intercepted and displayed as a fault.
Note: This setting is independent of the SOA composite application and SOA Infrastructure payload validation level settings. If payload validation is enabled at both the service engine and SOA Infrastructure levels, data is checked twice: once when it enters the SOA Infrastructure, and again when it enters the service engine.
|Disable BPEL Monitors and Sensors||Select this check box to disable all BPEL monitors and sensors defined for all BPEL components across all deployed SOA composite applications.|
If you want to configure advanced BPEL properties in the System MBean Browser, click More BPEL Configuration Properties. Properties that display include, but are not limited to, the following. Descriptions are provided for each property.
DisableAsserts — Disables the execution of assertions in BPEL, including the
DisableSensors — Disables all calls to sensors.
Make changes appropriate to your environment.
You can set the audit level for a BPEL process service component. This setting takes precedence over audit level settings at the SOA Infrastructure, service engine, and SOA composite application levels. The service component level setting is only available for BPEL processes and is not supported for the mediator, human workflow, and business rule service components.
There are two ways to set the audit level for BPEL process service components. Supported values are Off, Minimal, Inherit, Development, and Production.
In the System MBean Browser of Oracle Enterprise Manager Fusion Middleware Control Console:
In the navigation tree, expand the SOA folder.
Right-click soa-infra, and select Administration > System MBean Browser.
Select Application Defined MBeans > oracle.soa.config > Server: server_name > SCAComposite > Composite_Name > SCAComposite.SCAComponent > BPEL_Service_Component > Properties.
Click the Add icon.
Expand the Element_number folder.
From the many list, select false.
In the name field, enter
In the value field, enter a value.
In Oracle JDeveloper:
bpel.config.auditLevel property to an appropriate value in the
composite.xml file of your SOA project.
<component name="BPELProcess"> <implementation.bpel src="BPELProcess.bpel" /> <property name="bpel.config.auditLevel">Off</property> </component>
For more information about audit levels, see Section 126.96.36.199, "Understanding the Order of Precedence for Audit Level Settings."