Configuring Redelivery for an Endpoint (Using the Scheduler Binding Component)

Using the Scheduler Binding Component

Configuring Redelivery for an 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.
  
  Note –
  The Suspend option is not supported for the Scheduler Binding Component.
- 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.