Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite
11g Release 1 (11.1.1.6.3)

Part Number E10226-16
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

12 Configuring BPEL Process Service Components and Engines

This chapter describes how to configure BPEL process service components and service engines, including configuring properties such as audit level, audit trail threshold, and dispatcher thread values; automatic recovery for BPEL processes; master node recovery scheduling; and automatic recovery attempts for invoke and callback messages.

This chapter includes the following topics:

For more information about Oracle SOA Suite and Oracle BPEL process tuning and performance parameters, see Oracle Fusion Middleware Performance and Tuning Guide.

12.1 Configuring BPEL Process Service Engine Properties

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:

  1. Access this page through one of the following options:

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...
    1. Select SOA Administration > BPEL Properties.

    1. Right-click soa-infra.

    2. Select SOA Administration > BPEL Properties.


    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.

    Description of soaadmin_bpel_props.gif follows
    Description of the illustration soaadmin_bpel_props.gif

  2. Make changes to the service engine properties that are appropriate to your environment.

    Property Description

    Audit Level

    Select one of the following options:

    • Off: Composite instance tracking and payload tracking information is not collected.

    • Inherit: Logging equals the SOA Infrastructure audit level. This setting enables the BPEL 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: The BPEL service engine does not capture any audit details. Therefore, they are not available in the flow audit trails. All other events are logged.

    • Production: The BPEL service engine does not capture the payload. The payload details are not available in the flow audit trails. Payload details for other BPEL activities are collected, except for assign activities. This level is optimal for most standard operations and testing.

    • Development: Allows both composite instance tracking and payload tracking. All events are logged. However, it may have an impact on performance. This level is useful mostly for debugging purposes.

    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 cleanup 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.

    For information about monitoring these threads, see Section 13.6, "Monitoring BPEL Process Service Engine Request and Thread Statistics."

    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.

    For information about monitoring these threads, see Section 13.6, "Monitoring BPEL Process Service Engine Request and Thread Statistics."

    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 most of the 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 dispatcher engine threads. 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.

    For information about monitoring these threads, see Section 13.6, "Monitoring BPEL Process Service Engine Request and Thread Statistics."

    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.


  3. Click Apply.

  4. 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.

  5. Make changes appropriate to your environment.

For more information about Oracle BPEL process tuning and performance parameters, see Oracle Fusion Middleware Performance and Tuning Guide.

12.2 Configuring Automatic Recovery for Oracle BPEL Process Manager

Oracle SOA Suite provides an automatic recovery feature in Oracle Enterprise Manager Fusion Middleware Control that enables you to configure and recover:

To configure automatic recovery:

  1. In the navigator, right-click soa-infra and select SOA Administration > BPEL Properties.

  2. Click More BPEL Configuration Properties.

  3. In the Name column, click RecoveryConfig.

  4. Expand RecurringScheduleConfig.

    This section enables you to configure recurring recovery attempts.

  5. 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. 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 50. A negative value causes all messages selected from the database to be submitted for recovery. A 0 value causes no messages to be selected from the database (effectively disabling recovery).

    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 (00:00). Any invalid parsed time value is defaulted to 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 (04:00), effectively setting recurring recovery to run until 04:00.

    Any invalid parsed time values default to 00:00.

    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 300 (five minutes). A negative value causes the default to be selected.

    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 10 minutes. A negative value causes the default to be selected.


  6. Expand StartupScheduleConfig.

    This section enables you to configure server startup recovery attempts.

  7. 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. 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 50. A negative value causes all messages selected from the database to be submitted for recovery. A zero value causes no messages to be selected from the database (effectively disabling recovery).

    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 600 (ten minutes). A negative or zero value disables startup recovery.

    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 300 (five minutes). A negative value causes the default to be selected.


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.

12.3 Configuring Master Node Recovery Scheduling

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 1 (11.1.1.3) database schema.

Master node recovery scheduling enables you to perform the following tasks:

To configure master node recovery scheduling:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

  2. Right-click soa-infra.

  3. Select SOA Administration > BPEL Properties.

  4. Click More BPEL Configuration Properties.

  5. In the Name column, click RecoveryConfig.

  6. Expand ClusterConfig. The ClusterConfig properties work in association with the recurring recovery attempt properties and server startup recovery attempt properties that you set for RecurringScheduleConfig and StartupScheduleConfig, respectively.

  7. Set the following properties to values appropriate to your environment, and click Apply.

    Note:

    Once an instance/message becomes recoverable, a recovery is attempted. However, the number of retries is not tracked. If a recovery fails, it continues to pick the same record, retry, and fail again.

    Property Description

    clusterDbTimeRefresh

    Specifies how often to refresh the local copy of the database time. This takes into account the clock drift on different computers. All nodes in the cluster rely on the database time, regardless of its accuracy.

    The default value is 12 hours (specified as 43200 seconds).

    heartBeatInterval

    Specifies how often a node polls the cluster message table to check for messages published by other nodes in the cluster.

    The default value is 5 seconds.

    The following tasks are performed each interval:

    • Updates the node's last updated time in the cluster_node table.

    • Attempts to claim ownership of the master role.

    • If the master role is claimed, the recovery manager resumes work.

    • Checks for all nodes that have update times not updated for the nodeReapThreshold value, deletes those nodes from the cluster_node table, and reschedules all expiring work items from this node.

    masteAliveThreshold

    Specifies the number of seconds a master node is considered to be active. Master nodes that have not checked in with the cluster for this number of seconds are considered to be terminated. Whichever node gets an exclusive lock on the cluster_master table after this point can claim the master role.

    The default value is 15 minutes (specified as 900 seconds).

    nodeReapInterval

    Specifies how often the heartbeat thread is borrowed to mark old cluster nodes. Only the master node performs this job.

    The default value is 2 hours (specified as 7200 seconds).

    nodeReapThreshold

    Specifies the number of seconds a node is considered to be active. Nodes that have not checked in with the cluster for this number of seconds are considered to be terminated. During its heartbeat cycle, the master node tries to clean up the cluster_node table.

    The default value is 15 minutes (specified as 900 seconds).


12.4 Configuring Automatic Recovery Attempts for Invoke and Callback Messages

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 automatic recovery attempts for invoke and callback messages:

  1. In the navigator, right-click soa-infra and select SOA Administration > BPEL Properties.

  2. Click More BPEL Configuration Properties.

  3. Go to MaxRecoverAttempt.

  4. In the Value field, enter a value.

  5. Click Apply.

For information about recovering invoke and callback messages, see Section 14.4, "Performing BPEL Process Service Engine Message Recovery."

12.5 Setting the Audit Level at the BPEL Process Service Component Level

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:

For more information about audit levels, see Section 1.4.1.1, "Introduction to the Order of Precedence for Audit Level Settings."