Integration Patterns for SAP NetWeaver Process Orchestration
NetWeaver BPM now supports the XI 3.0 protocol for service endpoints (configurable on the service reference). This means that messages can be sent reliably from PI to BPM and vice versa.
Figure 2. Outbound communication from SAP NetWeaver BPM to SAP NetWeaver PI
Pattern states and availability
||Available from this release|
|SAP NetWeaver 7.3 EhP1 SP5|
|Claim Check||SAP NetWeaver 7.3 EhP1 SP5|
|Composed Message Processor||SAP NetWeaver 7.3 EhP1 SP5|
|Scatter-Gather||SAP NetWeaver 7.3 EhP1 SP5|
|Sync/Async Bridge||SAP NetWeaver 7.3 EhP1 SP4|
|Content Enricher (w/BPM)||SAP NetWeaver 7.3 EhP1 SP4|
|Splitter (w/BPM)||SAP NetWeaver 7.3 EhP1 SP4|
|Async/Sync Bridge||SAP NetWeaver 7.3 EhP1 SP4|
||SAP NetWeaver 7.3 EhP1 SP4|
Stateless patterns can be implemented either as Integration Flows on PI (AEX) or as processes in BPM. Both alternatives will be documented. As a general guideline, stateless patterns are best implemented as Integration Flows on AEX.
This applies especially if the integration process consists of a single pattern only and no additional business logic is executed in the Process Orchestration system (i.e., a pure ESB scenario). In such cases, the overhead of starting, executing and completing a BPM process instance is typically very prohibitive.
If the pattern is part of a larger business process involving multiple integration and/or workflow patterns, it could be implemented within NetWeaver BPM, as the overhead costs become less relevant in the overall scenario.
References / Related content
Also see Enterprise Integration Patterns.
 Get your free #BPM Enterprise Pattern models for #SAPNetWeaver Process Orchestration – by Jocelyn Dart