Diff. b/w ICO and Iflows

[Former Member]

Hello Experts,

Can some one help what is difference b/w ico and Iflow in PI7.4 and main use and why Iflows are using rather than Ico?

Right now we are using ICO only.

Thanks in Advance....

Regards,

VBA.

[former_member186851 · Accepted solution]

Hello VB,

Technically both are same.

ICO you build in Swing client and Ilfow in NWDS.

Iflow is like pictorial representation which is easy to understand and also iflow is like future ,SAP HCI and upcoming tools will use this.

To understand more about I-FLOW refer the below link

[Former Member · Accepted solution]

Hello Raghu,

Thanks for sharing the info and providing the link.

But i have some queries on Iflows. Is it posible to export all the objects from Iflows using CTS?

2. Re-use of channels

3. Extended RD

4. Party?

And why we are fetching the SI from ESR-Swing tool?

Please explain in details any one?

Regards,

VBA

[former_member186851 · Accepted solution]

Hello VB,

Yes you can transport Iflows using CTS+

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/10/07/transporting-pi-objects-with-nwds...

Re-use of channels-

Yes,its same like ICO.

3,Extended RD.

Yes possible ,configure two receivers

4,Party,

Same like ICO,So you can go ahead.

[nidhi_srivastava22]

Hi VB,

IFlow is used in 7.4 and is created in NWDS and not in swing tool. If you can see, iflow is pictorial representation of the interface flow. So, if you create an IFlow anyone who is referring your interface can get an overview of the flow by just having a look on the IFlow. This is the reason which I understand we moved to IFlow in 7.4.

Also, if we create an Iflow and deploy it(as explained by folks above) we get an ICO in the swing tool. So, from there everything is similar to the older versions.

Want to add, if you make any changes to ICO manually it will not be reflected in the IFlow. So, if you are using IFlow you should always make changes in the IFlow and deploy it.

Thanks,

Nidhi

[former_member182412]

Hi VB,

Adding to Raghu's reply. After you create the IFlow and deploy then ICO will be created in Integration Directory which is executed in the runtime.

Regards,

Praveen.

[Former Member]

Thanks Praveen.

But we will have lots of issues in Iflows?

Its not supported below operations.

1. Value Mapping

2. Configurable Parameters

3. Party

4. Virtual Receiver

5. Header Mapping

6. Access Control List

7. Extended Receiver Determination

8. CTS+ Support

9. Re-use of Channels

10.Dynamic Recipient List

Can you please help us on these and Now its supported?

Thanks &Regards,

VBA.

[former_member182412]

Hi VB,

Yes in latest version of PI all these are supported.

Reusing Channel Definition - Process Integration Tools (Eclipse-Based) - SAP Library

Defining Header Mapping - Process Integration Tools (Eclipse-Based) - SAP Library

Defining Virtual Receiver - Process Integration Tools (Eclipse-Based) - SAP Library

Defining a Value Mapping - Process Integration Tools (Eclipse-Based) - SAP Library

Defining a Party - Process Integration Tools (Eclipse-Based) - SAP Library

Regards,

Praveen.

[iaki_vila]

Hi,

Just to add to this thread. iFlows like when the ICO object appears in PI has/had several restrictions because SAP preferred to adapt them gradually. It is only matter of time and SPs to have this functionality and perhaps more.

You should think the iFlow like the ID tool nearest to PO concept, when you have PI+BPM+BRM available to do the integration and an excellent way to have in one shoot a clear view of the scenario integration.

Regards