I am working on the iFlow Eclipse Tool in SAP NWDS.
To be honest I love this one more than the beloved traditional Java swing based Tool.
I would like to share my understanding of the life cycle of Integration Flows and few tips for developers.
SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP07 PAT0007
SAP Enhancement Package 1 for SAP NetWeaver Process Orchestration 7.3 SP07
Life Cycle of an iFlow:
As you may have noticed, the icon for an activated iFlow is same as the deployed iFlow, so just by looking at it, one cannot distinguish between an deployed and ‘not deployed’ iFlow. The best way to check the status is looking at the deployment status.
I have submitted this as an idea in Idea Place SAP NetWeaver Process Orchestration: Home
If you like the idea, then visit the page and vote for it.
Reverting to previous version:
‘Reverting back to a previous version’ option through NWDS is cleaner than its counterpart in integration directory java tool.
The deployment status will show which version is currently deployed.
Its recommended that one should not created an iFlow through NWDS and then edit using traditional Integration Directory Java Tool.That will lead to data inconsistency.
It is advisable to disable the permission to edit integration flows or channels created by iFlows through the traditional Integration Directory Java Tool to avoid accidental change. Moreover you wouldn’t need to use the traditional tool as all the features of an integration flow are incorporated in NWDS.
iFlow life cycle – SAP Help:
How To Guide to create an iFlow:
Quthorization required to work with iFlow:
P.S: This is my first blog.Please share your thoughts. 🙂
I have created wiki page thou that has all the important link you may need.