...
| ID | NFR-2007 |
|---|---|
| Name | Ariba Event Management Orchestration Framework |
| Author | Kapila Epasinghe ( kapila.epasinghe-ext@syensqo.com ) |
| Approver | Sascha Wenninger ( sascha.wenninger-ext@syensqo.com ) |
| Status | Approved |
Summary
The integration solution is designed to solve a coordination and rate-limit management problem between Ariba and Keelvar APIs used in Sourcing Processes.
...
| Object | Value JMS Event Router | Value JMS Master Data Router | Description |
|---|---|---|---|
| Sender Queue Name | aribaEventMgtQueue | aribaMasterDataQueue | The source JMS Queue to retrieve messages |
| Maximum Retries Allowed | 5 | 5 | The messages are gracefully pushed to a defined separate "Dead Letter Queue" (DLQ) used for error handling. No further processing will be done after the configured number of retries. |
| Dead Letter Queue for Error Handling | DLQ_aribaEventMgtQueue | DLQ_aribaMasterDataQueue | The name of the Dead Letter Queue that persists messages when the number of processing times reaches the maximum Retry Limit |
...
For the current solution, based on the number of calls and the schedule, the configurable pause time limit provides adequate support for re-processing of messages. However, if further integrations are added to the package, further design analysis may be required to control the length of the pause
Reprocessing from Dead Letter Queue (DLQ)
At the moment, the DLQ is only used as a placeholder for any messages that have failed the number of retries configured. Currently, no retry from DLQ is enabled, and this solution may be enhanced to provide the ability to reprocess the messages in the DLQ back to the JMS Queue.
...