Hi All,


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.


Version Used

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:

Picture2.png

Status Integration Flow Icons Description
Created Picture5.png
  • A new iFlow has been created but not activated yet.
  • It will be visible only under your workspace.
Activated Picture6.png
  • iFlow has been activated.
  • All users can see this iFlow and they may edit it too.
  • You can activate incomplete iFlows.
  • You must activate before deployment. Please note that you will not be prompted to do so.
Saved Picture7.png
  • iFlow has undergone some change and saved but not activated by you.
Locked Picture9.png
  • iFlow has undergone some change and saved but not activated by others.
  • You may open it in Read-Only mode.
Deployed Picture8.png
  • iFlow has been deployed.
  • The changes are in Runtime.

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

Integration Flow Icons : View Idea

If you like the idea, then visit the page and vote for it.

Picture11.png

Undeployed iFlow:

Picture15.png


Deployed iFlow:

Picture10.png    

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.

Picture12.png

Picture13.png

Picture14.png


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.


Reference:


iFlow life cycle – SAP Help:

Understanding Integration Flow – Process Integration Tools (Eclipse-Based) – SAP Library


How To Guide to create an iFlow:

How To Use the iFlow Eclipse Tool with the Integration Directory


Quthorization required to work with iFlow:

Authorization for Operations on Integration Flows – Process Integration Tools (Eclipse-Based) – SAP Library


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.

A Quick Links Guide for SAP Process Orchestration

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Arul Raja Adaikkalam

    We tried to use iFlow because we liked the promise. But iFlow is full of defects and created lot of issues for the project. Hence we went back to using Integration Objects. Big disappointment.

    (0) 
    1. Karthik Kaveriselvan Post author

      Hi Arul,

      That’s sad.

      We are using iFlows in our projects for almost an year now and we didn’t face any show-stopping issues. We had few glitches but the latest SPs help us overcome.

      Could you please highlight some of the problems you faced?

      Which version/ SP level of SAP PO and NWDS were you using?

      Regards,

      Karthik

      (0) 

Leave a Reply