Some facts about Persist step:
Shares the same tenant DB as the data store (Details)
To access the contents – Use Cloud Integration OData API
Message store can be accessed only after execution of the i-flow that writes the entry
Life of message is 30 days, after that it will be deleted automatically
Scenario for understanding the functionality:
- Send an HTTP request (ProductID)
- Store the request payload using “Persist Message” (Before Message)
- Fetch “Product Review” through OData API based on requested ProductID
- Store the “Product Review” response payload using “Persist Message” (After Message)
Integration Flow Design
Address: https://refapp-espm-ui-cf.cfapps.eu10.hana.ondemand.com/espm-cloud-web/espm.svc
Resource Path: CustomerReviews
Query: $select=Comment,FirstName,LastName,ProductId,Rating,CustomerReviewId,CreationDate&$filter=ProductId eq '${property.Productid}'
OData Channel Configuration
Sending ProductId through HTTP Request
Receiving Customer Review through HTTP Response
Message ID
Pass copied Message ID to "MessageProcessingLogs" to fetch "MessageStoreEntries"
https://<Cloud Integration host>/api/v1/MessageProcessingLogs('<Message ID>')/MessageStoreEntries
Get MessageProcessingLogs based on Message ID
Pass copied Id to "MessageStoreEntries" to fetch the payload
https://<Cloud Integration host>/api/v1/MessageStoreEntries('<Message Stored Entries Id>')/$value
Persist payload from 1st MessageStoreId (ProductBefore)
Persist payload from 2nd MessageStoreId (ReviewAfter)
Now, it is your turn to design your business use case by implementing message persistence – through “Persist”; access the stored message content through Cloud Integration OData API & feel the power of API Business Hub. Please do share your use case as well 😊
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Subject | Kudos |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
User | Count |
---|---|
21 | |
19 | |
9 | |
7 | |
5 | |
5 | |
5 | |
5 | |
4 | |
4 |