Call iFlow from iFlow

[Former Member]

Hello experts,

In some scenarios I have to call iFlow from another iFlow.

<sender WS> ----> <iFlow1> ----> <iFlow2> -----> <receiver WS>

I found an way how to do that - I deploy <iFlow2>, then in Process Integration Runtime I can get enpoint URL of <iFlow2> and I use that URL in receiver Comm. channel in <iFlow1>.

My question is - is this the best way how to do that or it does exists some better way? The problem is, that it is hard to determine from that URL, which WS is called.

I wonder if there is some more "customizing" or "graphical" way how to make that kind of connection.

Thanks

VB

[former_member192851]

What adapters do you use to communicate with Iflows?

I mean at this point <iFlow1> ----> <iFlow2>

[Former Member]

SOAP 1.1, because XI 3.0 supports only one operation per Service Interface

[rpalotai]

Hi,

In BTP Cloud Intgration use ProcessDirect adapter. You can pass over the Message header variables from one iFlow to the other.

Br

[Former Member]

Hi,

>> is this the best way how to do that or it does exists some better way? Yes, this is the only way.

But In HCI its possible to create two iflow in one model configurator. so you could see both iflows at one place.

reg,

avinash M

[Former Member]

Hi Avinash,

what is HCI and can you please give me more information how can I create two iflows in one model configurator?

[Former Member]

hi,

its HANA Cloud Integration, If you have got trial system access , can try creating it.

reg, avi

[former_member184720]

HCI (Hana Cloud Integration) is all together a new product.. You'll find some very good blogs on SCN..

I don't think there is some better approach... Calling the second i flow using it's endpoint is the best possible solution..

>>>The problem is, that it is hard to determine from that URL, which WS is called.

I didn't quite understand it. You can identify the interface from the endpoint url right?

[Former Member]

We have our own SAP PO 7.4 installed on our server - so I`m working on that machine.

[Former Member]

Hareesh Gampa wrote:

 >>>The problem is, that it is hard to determine from that URL, which WS is called.

I didn't quite understand it. You can identify the interface from the endpoint url right?

Yes, you can identify it, but it is not obvious for first sight - and field in NWDS for url dont show whole URL at once.

But I`m probably too pampered

Thank you guys for your help.

[former_member184720]

specify the second iflow name and URL somewhere in the description field if you don't have any documentation in place..

[Former Member]

Can you brief your exact requirement .Why you want to call Iflow from Iflow ?

Thanks.

[Former Member]

Hi Anshu,

I have to have one "central bus ws" which receives all service calls (this is iFlow1) and this iFlow then call specialised webservices for specialised tasks (a lot of iFlows2, 3, 4...).