iFlow Integration – ID

iFlow Integration – ID 

Click here to view

Summary

SAP has introduced new development strategy “Eclipse based development”.  In this a developer, can configure many servers like DEV, QA, PRD in NWDS and whenever it’s required just one click to connect to the server. The Eclipse tool can be used instead of the classical Swing tool (IR and ID). This will help the developer to work in a single window unlike earlier where we had to switch java clients for modeling and configuration.

Abstract

In this document, I explained step by step creation of iFlow integration objects like Communication component, Channels, in integration directory.  It is a file to file scenario; both adapters are file adapter only.

What is an Integration Flow?

SAP says, "An integration flow represents an integration scenario using a graphical model containing endpoints and flow steps. It holds information of all the elements involved in the process integration" With the onset of Integration Flows aka iFlows, now we have a much better visibility and readability of the Integration scenario. This is very essential as earlier; it took a great amount of expertise and knowledge to understand a scenario within PI. With iFlows, we have a pictorial view and I am sure you will agree that it is a much better representation to understand. Using an iFlow, we can build and configure and entire scenario using NWDS.

As you can see, from iFlow, we can immediate see the complete end-to-end integration without having to drill down the Swing tool in the Integration Directory.

iFlow Integration