| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Java CAPS Scheduler Binding Component User's Guide Java CAPS Documentation |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Java CAPS Scheduler Binding Component User's Guide Java CAPS Documentation |
Using the Scheduler Binding Component
About the Scheduler Binding Component
Scheduler Binding Component Features
Using the Scheduler Binding Component in a Project
Steps to Create the BPEL Project
Create a Scheduler Binding Component
Create a File Binding Component
Create a Composite Application
Using the Scheduler Control and Triggers Wizard
Accessing the Scheduler Control and Triggers Wizard
Understanding the Scheduler Wizard
Using the Add New Simple Trigger Editor
Using the Add New Cron Trigger Editor
Using the Add New Hybrid Trigger Editor
Example Hybrid Trigger Configuration
Adding Triggers and Editing an Existing Scheduler Project
Accessing the Configure Scheduler Binding Wizard
Scheduler Binding Component Properties
Runtime Properties for the Scheduler Binding Component
Scheduler Binding Component Loggers
Using the Trigger Properties Editor
Trigger Configuration Properties
Scheduler BC Normalized Message Properties
Scheduler Application Configuration
Using Scheduler Binding Component Application Configuration
Defining the Scheduler Application Configuration for a Project
Other Tools Used to Edit the Application Configuration
Scheduler Binding Component Application Variables
Using Application Variables in a Trigger Message
Creating and Using Application Variables
Using Admin Console and asadmin to Create Application Variables
Configuring Redelivery and Throttling for the Scheduler Binding Component
Redelivery and Throttling are Quality of Service (QoS) features that are configured from the Composite Application Service Assembly (CASA) Editor. To access the QoS Properties Editor for a Scheduler Binding Component endpoint, open your Composite Application in the CASA Editor, and click the QoS icon for the endpoint you want to configure. The QoS Properties Editor for that endpoint appears.
Redelivery is a QoS mechanism that handles message delivery when first-time delivery fails. Redelivery allows you to define the number of attempts that the system makes to deliver a message, the time between attempts, and the final result for an undeliverable message or nonresponsive endpoint.
To configure Redelivery for a specific endpoint, open the QoS Properties Editor for that endpoint connection. From the Redelivery Extension section of the editor, configure the Redelivery properties.
The Redelivery configuration parameters are:
Max Attempts: Specifies the number of times that the project attempts to redeliver a message. An error status is returned to the JBI component for each failed attempt.
Wait Time: Specifies the time, in milliseconds, that the project waits between redelivery attempts.
On Failure: Specifies the actions taken and the message destination when the specified redelivery attempts have been exhausted.
This parameter has four options:
Delete: QoS utility deletes the message and returns a Done status to the JBI component, at which time the component proceeds to its next process. The delete option only supports In-Only message exchanges.
Redirect: QoS utility redirects the message to a user-defined endpoint, such as a ?dead-message? folder. Upon successful delivery to the redirect endpoint, the QoS utility returns a Done status to the JBI component, at which time the component proceeds to its next process. The redirect option only supports In-Only message exchanges.
Suspend: The JBI component suspends the process instance . This option is only supported if monitoring is enabled in the JBI Component, since the user must use the monitoring tool to resume a suspended instance. This option is supported for both In-Only and In-Out message exchanges.
Error: The error option specifies that when the final attempt to redeliver the message is exhausted, the JBI component throws an exception. This option is only supported if monitoring is enabled in the JBI Component, since the user must use the monitoring tool to resume a suspended instance. This option is supported for both In-Only and In-Out message exchanges.
Note - The On Failure property options, delete and redirect, cannot be applied to In-Out message exchanges because the return value for these options does not suffice. A specific response is required from the process instance to proceed further. For more information, see Redelivery.
Throttling is used to set the maximum number of concurrent messages that are processed by a particular endpoint. Increased message load and large message payloads can cause memory usage spikes that can decrease performance. Throttling limits resource consumption so that consistent performance is maintained. In most cases, the trigger message from the Scheduler Binding Component is small, and limiting resource consumption is not an issue.
Throttling can also be used to configure serialization, or the order in which messages are processed. When set to a value of 1, then only one trigger message can be processed at a time, guaranteeing that regardless of size, messages are processed in the order in which they fire.
To configure Throttling for a specific endpoint, open the QoS Properties Editor for that endpoint. From the Throttling Extension section of the editor, configure the Maximum Concurrency Limit property. Specify the maximum number of concurrent messages to be processed for this connection, or enter a value of 1 to guarantee serial message processing.
|