Delivery window cutoff task

A delivery window cutoff task runs at the cut-off time for an active processing window and begins releasing all of the outbound transmissions that are associated with the window.

The delivery window task is a WebSphere® Application Server scheduler task. A separate delivery window cutoff task is created for each active processing window unless the window has been extended indefinitely. The scheduled run time for the task is determined by the following processing window configuration values:

The distribution cut-off time, if any, for its active processing window.
The receipt cut-off time for its active processing window.
The latest participant window override receipt cut-off time that is configured for its active processing window.
The task is not created when its active processing window has been extended indefinitely.

If the distribution cut-off time that was determined from these configuration steps is different than the distribution cut-off time in the active processing window, the cut-off time in the active processing window is updated with the newly determined time.

Each time the task runs, it performs the following functions:

Determines if the release criteria have been met for all of the transmissions in the active processing window.
When the release criteria have been met, it sends the build request messages for the transmissions in the active processing window.
Monitors the progress of building and releasing the transmissions and updates the status of the active processing window.

Determining if the release criteria have been met

The task starts by checking the release criteria when its active processing window has a status of open or late. The task executes eight distinct checks:

An outbound transmission for a processing window is released when all of the checks indicate the window can close.

The following message is logged when the checks begin:

IZLPB070I: Start check: window close criteria - processing window {0}.

The release criteria are ignored when the user manually delivers transmissions for the active processing window using the processing window activities page.

If an outbound transmission does not meet the release criteria, the task performs the following actions:

The status for the active processing window is set to late.
An alert is created.
The task is rescheduled using the Reschedule cutoff interval from the processing window definition that was used to create the active processing window. The interval is added to the current time to set the next time that the task runs.

When the task can no longer be rescheduled and the release criteria are still not met, the status of the active processing window is set to criteria timed out and an alert is created. The task cannot be rescheduled when the number of times that it has been rescheduled has exceeded the number of retries specified in the Reschedule cutoff max retry count parameter from the processing window definition that was used to create the active processing window. The task is no longer scheduled to run, but the user can restart it manually.

For more information about these parameters, see Processing Windows page.

Sends build request messages for the transmissions

When the task runs and determines that the release criteria has been met, it sends transmission build request messages to the Distribution engine for each outbound transmission in the active processing window. The status of the active processing window is set to closed.

Then, the task is rescheduled using the Reschedule cutoff interval parameter from the processing window definition that was used to create the active processing window. The interval is added to the current time to set the next time that the task runs.

Monitors the progress of building and releasing the transmissions

After the build request messages are sent, the task monitors until all of the transmissions have been sent or the process times out because the task can no longer be rescheduled. The task cannot be rescheduled when the number of times that it has been rescheduled has exceeded the number of retries specified in the Reschedule cutoff max retry count parameter from the processing window definition that was used to create the active processing window.

Each time it runs, the task checks whether all of the outbound transmissions have been built and sent and updates the status of the active processing window as appropriate.

If all of the transmissions have been built, the status of the active processing window is set to built.
If all of the transmissions have been sent, the status of the active processing window is set to complete.
If the Reschedule cutoff max retry count has been exceeded the status of the active processing window is updated based on its current status.
- If the status of the active processing window is closed, it is set to build timed out.
- If the status of the active processing window is built, it is set to release timed out.

Status values for the active processing windows

The task uses the following values for the status of the active processing window.

Open: The business day for the active processing window was activated.
Indefinitely Extended: The receipt cut-off time for either the active processing window or a participant window override stays open indefinitely.
Late: At least one outbound transmission does not meet the release criteria for the active processing window.
Criteria Timed Out: The release criteria were not met before the number of retries specified in the Reschedule cutoff max retry count parameter was exceeded.
Closed: All of the outbound transmissions for the active processing window met the release criteria.
Build Timed Out: All of the outbound transmissions for the active processing window were not built before the number of retries specified in the Reschedule cutoff max retry count parameter was exceeded.
Built: All of the outbound transmissions for the active processing window have been built.
Release Timed Out: All of the outbound transmissions for the active processing window were not sent before the number of retries specified in the Reschedule cutoff max retry count parameter was exceeded.
Complete: All of the outbound transmissions for the active processing window have been built and sent.

Rescheduling the task

The delivery window cutoff task is rescheduled several times during normal processing. In addition it can be rescheduled as follows:

User initiated: Use the processing window activities page to restart polling for one or more of the active processing windows. For more information, see Processing Window Activities page.
Transaction Server event: The Transaction Server scheduler is configured to send a processingWindowActivityChange Messaging API message when the receipt cut-off time of either the active processing window or the participant window override changes. When Distribution receives the message, it uses the new receipt cut-off time value to reschedule the delivery window cutoff task.