Skip to Content

With Process Orchestration 7.31 SP9, we plan to support abstract interfaces within BPM. Abstract Interfaces have been mainly introduced for ccBPM, and can be used for both on the inbound and outbound of your process. So far, BPM only supported inbound and outbound interfaces. For those of you who migrated from ccBPM to BPM, you had to copy the abstract interfaces used within your ccBPM process to either an inbound or an outbound interface. By supporting abstract interfaces in BPM, you can simply re-use the abstract interfaces used within ccBPM. Other than for ccBPM, BPM actually supports all kind of interfaces: abstract, inbound, and outbound.

By the way, Support Package 9 of 7.31 is planned to be shipped mid of September 2013. Of course, this is subject to changes.

Within the Process Composer perspective in NetWeaver Developer Studio, you can browse for abstract interfaces, and import the same:

ImportAbstractInterfaceFromESR.png

Once imported, you can use the abstract interface either for message start event, intermediate message events or automated activities. Here, I have chosen an automated activity to send a message from BPM to PI:

AssignAbstractIFToAutomatedActivity.png

For further tips and hints how to model common integration patterns in Process Orchestration, take a look at the blog series SAP Process Orchestration Integration Patterns.

If you plan to attend the SAP TechEd event this year, don’t miss the lecture session by Volker Stiehl about “How to Redesign ccBPM Processes Using SAP NetWeaver Process Orchestration” (session ID POP300).

To report this post you need to login first.

5 Comments

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

  1. Roberto Viana

    Dear Alexander,


    Thanks for sharing this upcoming update with us.


    Could you please elaborate on the added value and reasoning behind this new feature of PO a bit more?


    Personally I don’t see the direct need for this functionality in a BPMS platform such as PO. The arguments; first of all; abstract interfaces were introduced as part of ccBPM and are not part of the BPMN standard. Second; abstract interfaces introduces unnecessary complexity, additional decelopment and more administration tasks. Conclusion higher TCO.

    I Think ccBPM and BPM are two different technologies and they should not be mixed up.


    KInd regards, Roberto Viana

    (0) 
    1. Alexander Bundschuh Post author

      Hi Roberto,

      thanks for your comment, but I do not fully agree. Why should abstract interfaces add any more complexity?

      The reason we have released this is to facilitate the migration from ccBPM to BPM for existing dual stack PI customers, so they simply can reuse the existing abstract interfaces without creating new ones.

      You don’t need to use them, we still support inbound and outbound interfaces. And for new BPM processes I actually would recommend to rather use inbound and outbound, so that from a modeling and monitoring perspective it is clearly and well defined how an interface is used within a BPM process.

      Alex

      (0) 

Leave a Reply