Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS File Binding Component User's Guide Java CAPS Documentation |
Using the File Binding Component in a Project
About the File Binding Component
File Binding Component Features
Accessing the File Binding Component Runtime Properties
The File Binding Component Runtime Properties
Configuring File BC WSDL Attributes
Application Variables in File Name Patterns
File Binding Component Processing Protocol
Mapping Persisted Sequences to File Based Persistences
Application Configuration Support
Processing Protocols and Capabilities
Normalized Message Properties Defined by the File Binding Component
General Normalized Message Properties
Endpoints Statistics and Monitoring Management
Before we proceed to Redelivery capability of the File Binding Component, it is important to know about the Quality of Service (QOS) attributes. Redelivery is a part of the QOS properties.
The QOS attributes are configured from the Config QoS Properties Editor, accessed from the Composite Application Service Assembly (CASA) Editor.
The following table describes the QOS attributes.
Table 5 QOS Attributes and Their Description
|
Redelivery is a Quality of Service 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 non-responsive endpoint. Redelivery is configured for a specific connection from the Composite Application Service Assembly (CASA) Editor, by clicking the QoS icon for that connection. This opens the Config QoS Properties for that connection. From the Redelivery Extension section of the editor, configure the Redelivery properties.
If ERROR status is returned for an Inbound message sent by File Binding Component, the BC will attempt to re-deliver the message, based on Redelivery QoS settings. For example, a message could have ERROR status if BPEL Service Engine encounters a problem while processing the message.
The Redelivery configuration parameters are:
Max Attempts: Specifies the number of times that the project attempts to re-deliver 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, redirect, suspend, and error.
The On Failure parameter has four options: delete, redirect, suspend, and error.
Delete: The delete option specifies that when the final attempt to redeliver the message has failed, the 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.
Error: The error option specifies that when the final attempt to redeliver the message is exhausted, the providing JBI component will set the endpoint status to "ERROR", and will raise an exception and populate the Error property with it. This option is supported for both In-Only and In-Out message exchanges.
Redirect: The redirect option specifies that after the final attempt to redeliver the message has failed, the 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 suspend option specifies that when the final attempt to redeliver the message has failed, 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.
The CASA Editor opens containing your composite application.
The QOS Properties Editor appears.