Skip to Content

Impressions from TechEd 2011 India on PI

 It was wonderful three days at TechEd 2011 (Bangalore) which provided lots of valuable insights into the roadmap and the change in SAP product line. What stood out was the Process Orchestration Platform, into which SAP PI is now nicely integrated. Though the coalescence has been in the coming for several years, it is only now that it looks complete.

From my perspective the following are the major areas of change:

Runtime: PI 7.3.1 allows you to create Integration Flows (point to point, recipient list etc) that are modelled using BPMN 2.0. This means your BPM modelling can integrate with these flows. What’s more, I can have a human activity interrupting an integration flow! Thus the key take away is PI now can seamlessly interact with other “containers” in the SAP JEE server and the same can be modelled in design time.

Design Time: All PI flows that is point to point or BPM based can be developed from the same developer studio. It would also allow PI developers to tap the power of eclipse to build their mapping logic. And in the future all transports can be routed via CTS+.

Consultant: Interesting times for consultants now. A hard core JEE expert can handle Portal, BPM, BRM and PI with ease. As a manager I would not buy in to the idea of different experts for each area of concern as I see several roles merging in the future.

With a standalone Java stack one can expect better performance in comparison to a dual stack. The UME issues, Java – Abap requests can all be avoided. Having said this, what lies to be seen is how the whole engine deals with huge volumes and how it scales up when needed. The roadmap seems to be finally in the right direction though!

You must be Logged on to comment or reply to a post.
  • PI/XI – We have it.  We use it.  But I’m not sure where that product fits into the SAP mix anymore.  I was just talking with my boss about that.

    • Heyy Michelle

      I tried out oData with Sybase this teched for mobile solutions. It is lightweight and online. Typical uses: Wherever you need quick online connection: Promotions via facebook in retail say!

      OLAP ideally must be on its way out if HANA makes it big. But thats better said than done 🙂

      I also attended the NetWeaver on Demand hands on. If we get onto the cloud, we can kiss goodbye to many products and their relevance.

      We have been at cross roads for quite sometime now and we can only wait to get answers.

    • Heyy Michelle

      I did use oData to connect android via sybase in the TechEd in my hands on session. My idea is to use oData for lightweight n online connectivity. Example: Facebook promotions for retail. Mobile online solutions.

      OLAP sincerely must be n the way out if HANA makes it big. Thats better said than done though 🙂

      PI would fit in when there are legacy systems and offline integration scenarios. Add to that now process based integration scenario. Example: Vendor based mass article and cost entry with merchant approval.

  • Thanks for the insightful analysis. I found it useful and to the point. You should blog more 🙂

    It’s exciting to see NetWeaver finally mature as a platform. With the product(portal/pi/mdm/bpm) feature sets and developer tools finally maturing, the next areas of competition will be scaling and focus on user experience. Looking forward to the next 5 years on the platform.


    • Thanks mate. Would try not be lazy and pen down the other few things I heard.

      I am glad too that the platform is maturing but may be its a little late. Cloud should be the way forward if we solve the issues around data security.