Dear Experts,
We have a use case whereby we need to push changes from System A to System B. The current architecture, on a high level, looks like this - System A pushes changes to SAP Event Mesh via HTTP APIs. SAP CPI then gets these changes off Event Mesh (using AMQP adapter), enriches them with some additional data and then pushes them to System B (using REST or SOAP). To complicate this the order of messages is important. There are also limitations on what we can do with Systems A and B as they are legacy which limits us to the technologies we can use and changes we can make to them.
It all works well in an optimistic scenario but we’re trying to understand how we can handle errors when, for example, CPI->System B connection fails or System B goes down. In theory, we can put messages in a JMS queue in CPI first but then it means that we’re, in a way, duplicating what we are doing in Event Mesh. Other options would be a) to "republish" failed changes to EM again and then get them processed or b) use REST APIs instead of AMQP in CPI to read messages and only acknowledge (QoS=1) and delete them from the queue in EM once the message processing has been successfully completed by system B.
Has anyone implemented a similar use case and/or could recommend a way to resolve this?
I hope it all makes sense and any advice would be greatly appreciated.
Regards,
Alexey
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.