Professional Documents
Culture Documents
Sap Netweaver Process Orchestration Build A Complete Integration PDF
Sap Netweaver Process Orchestration Build A Complete Integration PDF
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.
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. 7
SAP NetWeaver Process Orchestration
Referenced channels in Integration Flows
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
Migrate classical PI scenarios to Using the new directory content migration tool, you
integrated configuration objects (ICOs) could considerably reduce the migration effort
Supporting both Java-only and dual-stack
target systems
Source PI system as of XI 3.0 and newer
Tool runs in target system
Automatic directory objects matching and
migration checks
Renaming of objects via renaming rules
Mass change support for communication
channels
Check out TechEd hands-on session
POP262: Migration Tool from Double
Stack to Single Stack Integration
Scenarios
• 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
• Solution 1
• Using several start events
• Assumption: Order Header contains
number of expected items
• Solution 1
• Using several start events
• Assumption: Order Header contains
number of expected items
• Solution 2
• Using instantiating parallel
event-based gateway
• Assumption: Order Header contains
number of expected items
Incoming Messages
1..1
1..1
Outgoing Message
1..n
Same
Interface/Trigger
=
„Conditional Start“
Non-conditional start process definition Non-conditional start process definition Conditional start process definition
Non-conditional start process definition Non-conditional start process definition Conditional start process definition
Non-conditional start process definition Non-conditional start process definition Conditional start process definition
4711
Conditional start process definition
Message Sequence
1. Message for Trigger A arrives with ID = 4711 4712
2. Message for Trigger A arrives with ID = 4712
3. Message for Trigger A arrives with ID = 4712
4. Message for Trigger A arrives with ID = 4713
5. Message for Trigger A arrives with ID = 4711 4713
6. Message for Trigger A arrives with ID = 4713
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
Multiple interfaces for starting a process
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and
SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth
in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and
other countries.