9 Configuring BPEL Process Service Components and Engines

This chapter describes how to configure BPEL process service components and service engines.

This chapter includes the following topic:

9.1 Configuring BPEL Process Service Engine Properties

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:

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

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

    The default value is 30 threads. Any value less than 1 thread is changed to the default.
    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.
    Audit Level Select one of the following options:

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

    • Inherit: Logging is equal to 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 normal operations and testing.

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

  3. Click Apply.