This chapter includes the following topics:
Configuring Automatic Recovery for Oracle BPEL Process Manager
Configuring Automatic Recovery Attempts for Invoke and Callback Messages
Setting the Audit Level at the BPEL Process Service Component Level
For more information about Oracle SOA Suite and Oracle BPEL process tuning and performance properties, see Tuning Performance.
You can configure BPEL process service engine properties, which are used by the BPEL process service engine during processing of BPEL process 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 the audit level, audit trail and large document thresholds, payload schema, and BPEL monitors and sensors.
Make changes to the service engine properties that are appropriate to your environment.
Property | Description |
---|---|
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 for a BPEL variable before its contents are stored in a separate location from the rest of the instance scope data. |
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 checkbox to disable all BPEL monitors and sensors defined for all BPEL components across all deployed SOA composite applications. |
Click Apply.
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.
AsyncAuditBatchSize: Stores multiple audit trail messages (across instances) in a single transaction on Oracle Exalogic platforms. For more information, see Storing Instance and Message Data in Oracle Coherence Distributed Cache on Oracle Exalogic Platforms.
BpelcClasspath: The extra BPEL class path to include when compiling BPEL-generated Java sources. For more information, see Section "How to Add Custom Classes and JAR Files" of Developing SOA Applications with Oracle SOA Suite.
DisableAsserts: Disables the execution of assertions in BPEL, including the bpelx:assert
activity. For more information, see Section "How to Disable Assertions" of Developing SOA Applications with Oracle SOA Suite.
DisableSensors: Disables all calls to sensors.
DispatcherNonBlockInvokeThreads: The total number of threads allocated to process nonblocking invocation dispatcher messages. If your system has many nonblocking invokes, the value of this property can be incremented. The default value is 2
. Any value less than 1
is automatically changed to the default value.
ExecuteCallbacksInOrder: Preserves BPEL process callbacks in the order of received time of the callback inside the BPEL process service engine (when set to true
). For more information, see Preserving the Order of Callback Messages.
ExpirationMaxRetry: The maximum number of times a failed expiration call (wait/onAlarm) is retried before failing.
ExpirationRetryDelay: The delay between expiration retries.
InstanceKeyBlockSize: The size of the block of instance IDs to allocate from the dehydration store during each fetch.
MaximumNumberOfInvokeMessagesInCache: The number of invoke messages stored in the in-memory cache.
MaxRecoverAttempt: The number of automatic recovery attempts to submit in the same recoverable instance. For more information, see Configuring Automatic Recovery Attempts for Invoke and Callback Messages.
MinBPELWait: The minimum time duration for a BPEL process to perform a real wait that involves a dehydration. For more information, see Section "Creating a Wait Activity to Set an Expiration Time" of Developing SOA Applications with Oracle SOA Suite.
OneWayDeliveryPolicy: Changes whether one-way invocation messages are delivered.
QualityOfService: Enables or disables Oracle Coherence cache for the BPEL process service engine. For more information, see Configuring Oracle Coherence Caching.
RecoveryConfig: Configures automatic recovery of activities and configures clustered environments to use master node recovery scheduling. For more information, see Configuring Automatic Recovery for and Configuring Master Node Recovery Scheduling.
StatsLastN: The size of the most recently processed request list. Change this value to a value such as 1000
. This enables you to view low level statistics in the Statistics page. For more information, see Monitoring BPEL Process Service Engine Request and Thread Performance Statistics.
SyncMaxWaitTime: The maximum time a request and response operation takes before timing out. For more information about this property, see Section "Specifying Transaction Timeout Values in Durable Synchronous Processes" of Developing SOA Applications with Oracle SOA Suite.
Make changes appropriate to your environment.
For more information about Oracle BPEL process tuning and performance parameters, see Tuning Performance.
Oracle SOA Suite provides an automatic recovery feature in Oracle Enterprise Manager Fusion Middleware Control that enables you to configure and recover:
All activities (for example, wait activities and OnAlarm branches of pick activities) that have an associated expiration date and are scheduled with the SOA Infrastructure to be rescheduled
All activities that are not complete over a provided threshold time
All invoke and callback messages that are unresolved
To configure automatic recovery:
Note:
In a cluster, it is possible for different nodes to concurrently attempt an automatic recovery of the same items. The first node to lock the item attempts the recovery, while other nodes may raise an exception that can be safely ignored.
You can configure a clustered environment to use master node recovery scheduling. In this environment, the master node is dedicated to performing recovery for all nodes in the cluster.
Note:
This feature does not work if you are using a pre-Oracle Fusion Middleware Release 11g (11.1.1.3) database schema.
Master node recovery scheduling enables you to perform the following tasks:
Recover activities with expiration dates (for example, a wait activity or an OnAlarm branch of a pick activity) that are past due. The master node picks expired work items and reschedules them.
Recover stranded work items
Recover callback messages
Recover invoke messages
Fail over expired activities: When the master node detects a failed node, it tries to reschedule work items that have an expiration date.
To configure master node recovery scheduling:
You can configure the number of automatic recovery attempts to submit in the same recoverable instance. The value you provide specifies the maximum number of times invoke and callback messages are recovered. If the value is 2
(the default value), two attempts are made to recover each recoverable message. Once the number of recovery attempts on a message exceeds the specified value, a message is marked as nonrecoverable.
To configure automatic recovery attempts for invoke and callback messages:
For information about recovering invoke and callback messages, see Performing BPEL Process Service Engine Message Recovery.
You can preserve the order of callback messages in a BPEL process and ensure that they are delivered to the BPEL process instance in the correct order by setting the ExecuteCallbacksInOrder property to true
in the System MBean Browser. ExecuteCallbacksInOrder enables callbacks to be picked up in the order in which they were received by the BPEL process service engine for a given business flow instance. This setting impacts all SOA composite applications deployed in the BPEL process service engine.
For information about accessing and configuring the ExecuteCallbacksInOrder property, see Configuring BPEL Process Service Engine Properties.
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 Oracle 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.
To set the audit level for BPEL process service components:
In the System MBean Browser of Oracle Enterprise Manager Fusion Middleware Control:
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 bpel.config.auditlevel
.
In the value field, enter a value.
Click Apply.
In Oracle JDeveloper:
Set the 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 Introduction to the Order of Precedence for Audit Level Settings.