In this solution, for all our asynchronous Inbound communication we employ Message broker (IBM MQ) between third party application and SAP CI which then connects to the SAP system. A Retry Queue is setup on IBM MQ for temporary storage exclusively dedicated to failed messages, opting out of using SAP CI’s internal persistence as suggested in the SAP Retry Pattern . A script acting as an AMQP client is scheduled periodically within an integration flow (Retry Flow). This script retrieves failed messages from the Retry queue and initiates their reprocessing based on specific message headers such as ErrorType and RetryCount.
In this solution, for all our asynchronous Inbound communication we employ Message broker (IBM MQ) between third party application and SAP CI which then connects to the SAP system. A Retry Queue is setup on IBM MQ for temporary storage exclusively dedicated to failed messages, opting out of using SAP CI’s internal persistence as suggested in the SAP Retry Pattern . A script acting as an AMQP client is scheduled periodically within an integration flow (Retry Flow). This script retrieves failed messages from the Retry queue and initiates their reprocessing based on specific message headers such as ErrorType and RetryCount. Read More Technology Blogs by Members articles
#SAP
#SAPTechnologyblog
+ There are no comments
Add yours