With NetWeaver Orchesteration 7.31, which includes PI, BPM and BRM, we are now able to design integration with stateful processes using NW BPM and PI. As we all know, PI’s dual-stack installation will eventually go away, which means that PI’s ccBPM, which is based in ABAP, will also be gone. Even though the date for the dual-stack to end has not been announced, we should probably start looking at using NW BPM to replace ccBPM in PI.
At first, I thought this would be a monumental task to learn a new tool, but actually, I found the learning curve is actually less than when I started with ccBPM. There are a few notables when working with NW BPM:
- With BPM, there is no need for Abstract Interfaces as in ccBPM.
- With BPM, there is no need for Operations Mapping when we need to split or combine messages as in ccBPM.
- In BPM, correlation conditions for asynchronous messages is much easier and transparent to define.
- PI treats BPM just as another sender or receiver system.
- Sending messages between BPM and PI is based on XI protocol via the SOAP adapter.
- Because BPM uses XI protocol, we can easily use BPM with multiple PI systems, including PI 7.11.
- The graphical design tool is based on BPMN and using NWDS, the tool is much easier to use, and more interactive.
- When needed, we can include user-interactions easily within BPM.
- Through some preliminary performance tests, we found BPM to be much faster than ccBPM.
- The combined tools of PI and BPM bring a very powerful environment to design, execute and orchestrate messages among SAP and non-SAP applications and system.
To introduce BPM, a how-to article has been written using a simple business process scenario that includes asynchronous messaging with correlation, synchronous messaging, and orchestration of messages between a backend SAP system, a database and files.