Professional Documents
Culture Documents
Sap Netweaver Process Orchestration Build A Complete Integration Scenario
Sap Netweaver Process Orchestration Build A Complete Integration Scenario
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.
Agenda
SAP NetWeaver Process Orchestration Whats new?
Multiple interfaces for starting a process
Advantages
Reduced development and operations cost
Improved performance
Prerequisites
Mark the communication component
as integration-centric process
PI and BPM have to communicate
with each other using XI 3.0
message protocol
2013 SAP AG or an SAP affiliate company. All rights reserved.
Referenced Channel
Lifecycle
Create, edit, and delete channels within SAP Process
Integration Designer perspective
On activation, channels get deployed on runtime
Assign/unassign channels to Integration Flows
Activation of incompatible changes is prevented,
requires undeployment of Integration Flow
Inline Channel
Challenges
Several different interfaces
Order of appearance not predictable
Mixture of cardinalities possible
(e.g. 1..1 or 1..n)
Receiver expects aggregated message
comprising all interfaces
12
Solution 1
Using several start events
Assumption: Order Header contains
number of expected items
13
Solution 1
Using several start events
Assumption: Order Header contains
number of expected items
14
Solution 2
Using instantiating parallel
event-based gateway
Assumption: Order Header contains
number of expected items
15
Incoming Messages
1..1
1..1
1..n
0..1
0..1
0..1
2013 SAP AG or an SAP affiliate company. All rights reserved.
Outgoing Message
16
17
Interfaces, Mappings,
Integration Flows
19
20
21
23
24
25
4711
Conditional start process definition
Message Sequence
1. Message for Trigger A arrives with ID = 4711
4712
4713
26
http://scn.sap.com/community/bpm/blog/2013/03/25/boost-your-correlation-scenarios-with-conditional-start
2013 SAP AG or an SAP affiliate company. All rights reserved.
27
Integration-centric process
29
30
31
32
33
34
35
36
Demo
Starting a process with multiple interfaces
Further information
39
http://saptechedhandson.sap.com/
http://sapteched.com/online
40
Feedback
Please complete your session evaluation for POP261.
42