Retrying Failed Asynchronous Events

The ability to manually retry or reprocess failed asynchronous orchestration events is critical in situations where the processing of these events must be guaranteed 24 hours a day, 7 days a week. An integration between SBM and an external system that uses an event emitter mechanism is an example of this scenario. In this type of integration, the external system is responsible for raising the event, while SBM is responsible for processing it. It is possible that the event will not be processed successfully in the first attempt. The manual reprocessing of failed events is a recovery mechanism for SBM data that gets out-of-sync.

For example, you might have an external system that emits events to Serena Service Manager, with the expectation that SBM will process these events. For numerous reasons, Service Manager may fail to process these events on a first attempt; the user needs to know about the failures so he or she can reprocess them manually.

To identify and retry events:

Open the SBM User Workspace error report.
Review the failure information to determine whether you want to retry the event.
Open SBM Application Repository.
In the navigation pane, from the Orchestration Engine view, select Event Manager Log. In the list of asynchronous events that is displayed, failed events have EVENT_FAILURE in the Status column. (You can create a filter to show only failed events. For instructions, see the SBM Application Repository Guide or online help.)
To ensure that an event is the same event you investigated in the report before you retry it:
1. Select the event.
2. Click Event Summary at the top of the list, or right-click the event and then select Event Summary.
3. Check that the event ID from the report matches the event ID shown in the Event Summary window.
To retry one or more events:
1. Select the event or events and then click Retry Event(s) at the top of the list. Alternately, right-click the events and then select Retry Event(s). This command will reprocess all failed orchestration workflows that were invoked by each selected event. Orchestration workflows that succeeded or have not yet completed will not be reprocessed.
2. Click OK in the confirmation message that appears.