I propose to explain out how is the integration process - Read invoked. A screenshot of the DS adapter would be useful for a better understanding, too.

[CimermanDenis]

Issue description

Feedback Type (Optional)

clarity

Page Title on SAP Help Portal (prefilled)

Decouple Sender and Flows Using Data Store

Page URL on SAP Help Portal (prefilled)

https://help.sap.com/docs/cloud-integration/sap-cloud-integration/decouple-sender-and-flows-using-data-store

[MelanieCueppers]

Thank you for your feedback! We’ll look into it and come back to you if we have any questions.

[AnnikaGonnermann]

Hey @CimermanDenis, thanks for your feedback. At the beginning of the text under "implementation" we provide more information:

"The integration flow consists of 2 integration processes:

The Integration Process - Write integration process receives the request from the client, writes the request in a data store, and sends back a response to the calling client.

The Integration Process - Read integration process reads the request from the same data store, and then performs the actual long running service call and (eventually) further message orchestration steps."

Is that what you had in mind?

To get more information about the configuration, you can download the package or check it out in the Business Accelerator Hub: https://api.sap.com/integrationflow/ModelingBasics_DecoupleFlowsUsingPersistence

Best Annika

[CimermanDenis]

Hi Annika,

I would rather stress out that it is not the read process, which polls the data store just out of nothing or based on a timer, but there is (probably) a monitoring applications which initiates the read process. IMHO, this just be really stated to make the whole concept digestible.

What do you think?

Regards Denis

---

From: Annika Gonnermann @.> Sent: Thursday, January 18, 2024 2:42:24 PM To: SAP-docs/btp-integration-suite @.> Cc: Denis Cimerman @.>; Mention @.> Subject: Re: [SAP-docs/btp-integration-suite] I propose to explain out how is the integration process - Read invoked. A screenshot of the DS adapter would be useful for a better understanding, too. (Issue #40)

Hey @CimermanDenishttps://github.com/CimermanDenis, thanks for your feedback. At the beginning of the text under "implementation" we provide more information:

"The integration flow consists of 2 integration processes:

The Integration Process - Write integration process receives the request from the client, writes the request in a data store, and sends back a response to the calling client.

The Integration Process - Read integration process reads the request from the same data store, and then performs the actual long running service call and (eventually) further message orchestration steps."

Is that what you had in mind?

To get more information about the configuration, you can download the package or check it out in the Business Accelerator Hub: https://api.sap.com/integrationflow/ModelingBasics_DecoupleFlowsUsingPersistence

Best Annika

— Reply to this email directly, view it on GitHubhttps://github.com/SAP-docs/btp-integration-suite/issues/40#issuecomment-1898504344, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A74Q533BRAAS7JHSGLL7Y7TYPEREBAVCNFSM6AAAAABB7ELY26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYGUYDIMZUGQ. You are receiving this because you were mentioned.Message ID: @.***>

[AnnikaGonnermann]

Hey @CimermanDenis - thanks for specifying! I've made the following adjustments:

The Integration Process - Read integration process polls the request from the same data store, and then performs the actual long running service call and (eventually) further message orchestration steps.

Hopefully that should help avoid confusion in the future!

Best Annika