How to run an iflow automatically when an other iflow ran in SAP CPI

[pavankalyan_racha]

Hi community,

how to run a iflow when one of the other iflow is triggered.
The requirement is like the sending system is making a request but for that request to be processed in SAP CPI its taking more than 2 minutes so the sending system can't wait for that much time so we have designed the requirement like when the sending system makes request to SAP CPI immediately will send an aknowledgement that the request is being processed and the call closes there, next when the processed payload is ready in SAP CPI will send that to the sending system.For this to be achieved we have to designed two iflows one for sending the acknowledgement and one for the actual processing of the request made by the sending system, so in this case we need to run or trigger the second flow i mean the iflow which has actual processing of request.

can someone give some inputs on this?

[sunny_kapoor · Accepted solution]

Hi pavankalyan.racha,

You requirement falls into the classic case of asynchronous processing.

I suggest you to go through the following help documentation link, this will help you to implement the asynchronous message processing integartion pattern.

https://help.sap.com/docs/cloud-integration/sap-cloud-integration/decouple-processing

Moreover, we have compiled full list of design guidelines that helps you to learn and understand the basic concepts and much more.

Regards,

Sunny

[pavankalyan_racha · Accepted solution]

Hi Sunny
Got the solution
thank you very much

[VijayKonam]

You could simply use SOAP adapter with one-way/async messaging mode avoiding two iflows.

[pavankalyan_racha]

Hi Vijay
How can we send the acknowledgement and the actual processed payload in the single flow if we are doing the same thing in one flow the sending system can,t wait for that long time right.

[VijayKonam]

SOAP adapter when configured in async mode, immediately sends out a 200OK to the caller and the payload received processed by iFlow. The sender is no longer waiting. Now in your iflow after you process, you can send them the response to their endpoint.