SBM Orchestration Guide → Troubleshooting Orchestration Workflows → 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:
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.