Step 1 | Sample message is posted through postman to the source API URL of cloud integration. |
Step 2 | The property orderID is set using xPath expression to fetch it dynamically. |
Step 3 | -- Pallete option for Idempotent Process Call. we are using orderID as unique identifier which would be stored in idempotent repository for duplicate check. |
Step 4 | Setting Up the processed data. In this case we are just adding an additional line to the payload but in real time we could have multiple steps of processing inside this local integration process. |
Step 5 | Post processing we are posting the message to a webhook where we captured the output. Instead it could be any system where we want to post the transformed message. |
Step 6 & 7 | When we try to process the same message more than once the message ID/Unique identifier is comapred with the value in idempotent repository and if it matches the CamelDuplicateMessage flag is set to true. We could use the flag to take appropriate action. It could be an alert or we could send the message to any other system. |
Step 8 | Calling local integration process to take certain action like sending alerts in case of payload not processed because of duplicate entry found. |
Step 9 & 10 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
7 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 | |
5 |