Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite 11g Release 1 (11.1.1.5.0) Part Number E10226-08 |
|
|
View PDF |
This chapter describes how to configure BPEL process service components and service engines.
This chapter includes the following topics:
Section 11.1, "Configuring BPEL Process Service Engine Properties"
Section 11.2, "Configuring Automatic Recovery for Oracle BPEL Process Manager"
Section 11.3, "Configuring Automatic Recovery Attempts for Invoke and Callback Messages"
Section 11.4, "Setting the Audit Level at the BPEL Process Service Component Level"
You can configure BPEL process service engine properties, which 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.
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.
BpelcClasspath: The extra BPEL class path to include when compiling BPEL-generated Java sources.
DisableAsserts: Disables the execution of assertions in BPEL, including the bpelx:assert
activity.
DisableSensors: Disables all calls to sensors.
ExpirationMaxRetry: The maximum number of times a failed expiration call (wait/onAlarm) is retried before failing.
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 in-memory cache.
MaxRecoverAttempt: The number of automatic recovery attempts to submit in the same recoverable instance. For more information, see Section 11.3, "Configuring Automatic Recovery Attempts for Invoke and Callback Messages."
OneWayDeliveryPolicy: Changes whether one-way invocation messages are delivered.
StatsLastN: The size of the most recently processed request list.
SyncMaxWaitTime: The maximum time a request and response operation takes before timing out.
Make changes appropriate to your environment.
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:
In the navigator, right-click soa-infra and select SOA Administration > BPEL Properties.
Click More BPEL Configuration Properties.
In the Name column, click RecoveryConfig.
Expand RecurringScheduleConfig.
This section enables you to configure recurring recovery attempts.
Set the following properties to values appropriate to your environment, and click Apply.
Property | Description |
---|---|
maxMessageRaiseSize | The maximum number of messages to submit for each recurring recovery attempt. Use this property to limit the impact of recovery on the server. Note that this value specifies the maximum number of messages to filter from activity, invoke, and callback queries; that is, 50 messages from each of the activity, invoke, and callback tables.
The default value is |
startWindowTime | The start time for the daily recovery window, specified in a 24-hour notation. Therefore, 2:00 pm is specified as 14:00 . The leading zero does not need to be specified for single digit hour values (1:00 -9:00 ).
The default value is midnight ( |
stopWindowTime | The stop time for the daily recovery window, specified in a 24-hour notation. Therefore, 2:00 pm is specified as 14:00 . The leading zero does not need to be specified for single digit hour values (1:00 -9:00 ).
If you do not want daily recovery, set the start and stop window times to be the same value. If the stop window time is earlier than the start window time, both the start and stop window times are changed to their respective default values. The default value is midnight ( Any invalid parsed time values default to |
subsequentTriggerDelay | The number of seconds between recovery attempts during daily recurring startup recovery periods. If the next recovery trigger falls outside of the current recovery period, that trigger is not scheduled until the next recurring recovery period (tomorrow).
The default value is |
threshHoldTimeInMinutes | This is the threshold time in minutes to ignore for automatic recovery processing. For automatic invoke and callback recovery, this value is used for picking messages with a received date less than the threshhold time.
For automatic activities recovery, this value is used for picking activities with a modification date less than the threshhold time. This property prevents the message contention scenario in which a BPEL process service engine picks up a message for recovery while another thread on the service engine is in the middle of processing the message. This property ensures that the recovery part of the service engine only attempts recovery on messages older than the value for threshHoldTimeInMinutes. The default value is |
Expand StartupScheduleConfig.
This section enables you to configure server startup recovery attempts.
Set the following properties to values appropriate to your environment, and click Apply.
Property | Description |
---|---|
maxMessageRaiseSize | The maximum number of messages to submit for each startup recovery attempt. Use this property to limit the impact of recovery on the server. Note that this value specifies the maximum number of messages to filter from activity, invoke, and callback queries; that is, 50 messages from each of the activity, invoke, and callback tables.
The default value is |
startupRecoveryDuration | Specifies the number of seconds that the startup recovery period lasts. After the server starts, it goes into a startup recovery period. During this period, pending activities and undelivered callback and invocation messages are resubmitted for processing.
The default value is |
subsequentTriggerDelay | The number of seconds between recovery attempts during the server startup recovery period. If the next recovery trigger falls outside the server startup period, that trigger is not scheduled and the server moves into the recurring recovery period.
The default value is |
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 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 0
(the default value), it recovers all messages. Once the number of recovery attempts on a message exceeds the specified value, a message is marked as nonrecoverable.
To configure automatically recovery attempts for invoke and callback messages:
In the navigator, right-click soa-infra and select SOA Administration > BPEL Properties.
Click More BPEL Configuration Properties.
Go to MaxRecoverAttempt.
In the Value field, enter a value.
Click Apply.
For information about recovering invoke and callback messages, see Section 13.4, "Performing BPEL Process Service Engine Message Recovery."
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.
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 Section 1.4.1.1, "Introduction to the Order of Precedence for Audit Level Settings."