Udo Paltzer
Product Owner SAP Process Integration, SAP HANA Cloud Integration
Migration and Upgrade Paths to SAP Process
Orchestration
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.
We are currently migrating from a Process Integration Dual-Stack
system to Process Orchestration. Our key drivers were mainly …
Lower HW costs
Less complex landscape
Lower operating costs
Better performance
More stable and reliable
New business opportunities
Following SAP’s long term strategy
2.5
million
electronic messages per month processed through SAP Process Orchestration
3
x
faster message exchange with SAP Process
Orchestration with a B2B add-on as compared to SAP Process Integration
1
system
to monitor using a single-stack architecture instead of a dual-stack architecture
Link to full case study
Case Study: Stadtwerke Düsseldorf
Speeding up and improving the reliability of electronic message transfers
The company's top objectives
Manage a growing volume of electronic messages exchanged with business partners
Implement a reliable business-to-business (B2B) solution to send information via Electronic Data Interchange for Administration, Commerce and Transport (EDIFACT) within the time limits mandated by the German Federal Network Agency
Simplify process monitoring and error-handling and improve performance
The resolution
Collaborated well with itelligence to smoothly migrate from dual-stack SAP Process Integration technology to single stack SAP Process Orchestration software
Replaced a third-party AS2 adapter with the one available with the SAP Process Orchestration B2B add-on
The key benefits
Faster message exchange as well as improved monitoring and reliability
Fewer time-consuming inquiries caused by failed message transfers or noncompliance with time limits
25%
approximate reduction in total cost of ownership after
consolidating BPM and PI under SAP Process Orchestration
100%
reuse of existing PI mapping logic
Link to full case study
Case Study: Siemens Industry Drive Technologies
Accelerating application-to-application integration
The company's top objectives
Enable application-to-application integration as well as business process and rules management
Increase flexibility to route sales-relevant data to different applications
Integrate the tailored customer relationship management tool used at headquarters with the SAP ERP application and non-SAP solutions
The resolution
Migrated SAP Process Integration software and the SAP Business Process Management component to SAP Process Orchestration software, reusing existing integration mappings
Used model-based integration to migrate old and deploy new scenarios
Used rules management capabilities to actively route sales-relevant data
The key benefits
Faster development of new integration scenarios due to integrated monitoring and development tools
More flexibility to support requirements through the use of business rules
Easier collaboration using Business Process Model and Notation (BPMN)
33%
approximate acceleration in development of new
integration scenarios, as compared to using PI alone
SAP NetWeaver Process Orchestration
Improve processes and save integration costs
* B2B Add-On is licensed separately from SAP NetWeaver Process Orchestration
A2A Integration
B2B Collaboration *
Governance
Monitoring
& Analytics
Business Process
Management
Business Rules
Management
SAP NetWeaver Process Orchestration
Model & execute
processes fast and
flexibly
Manage integration
across
heterogeneous
environments
Design and govern
your service-based
integration
Automate
decisions using
business rules
Connect to your
business partners
Monitor your
integration
processes
SAP NetWeaver Process Orchestration combines the power of SAP NetWeaver Business Process Management, SAP
NetWeaver Process Integration and SAP NetWeaver Business Rules Management into one integrated offering. It provides
tools to quickly automate and optimize business processes - from simple workflows to integrated processes that span
applications, geographies, and organizational boundaries.
SAP NetWeaver Process Orchestration
Where are we today?
6,000+
productive customers
~170
new customers per
quarter
100+
active customers with
B2B add-on
One
integrated solution for
human-centric and
system-centric processes
across A2A and B2B
25%
TCO reduction*
Runs on SAP HANA
as of NetWeaver 7.4 SP04
Enabling integration
across on-Premise and cloud
BPMN
as common notation
SAP NetWeaver Process Orchestration
Release history
PI 7.1x
CE 7.11
CE 7.2
NW 7.3
NW 7.3
NW 7.31
NW 7.4
Process Orchestration
Business Process Management /
Business Rules Management
Process Integration
●Business Process
Management
●Business Rules
Management
●Business Process
Analytics
●
Adobe forms and
visual composer UIs
●UI generation
●
Consolidated SAP
NetWeaver release
●WD/ABAP task UI
●Java public API
●
Process orchestration
solution bundle
●Co-deployment of PI,
BPM, and BRM
●Major enhancements
towards common
Eclipse environment
●Process
Orchestration
on SAP HANA
●Enable major scenario
shift from dual-stack PI
to Java-only PI
●
Providing Standalone
Engine (AEX)
●
IDoc adapter on the AE
●Messaging capability
in the Adapter
Engine (AE)
●Proxy connectivity
on the AE
●Integration flows
●B2B add-on
How to migrate to Process Orchestration?
Migration and upgrade paths
Integration-centric
Higher footprint
No further investments for ABAP
Process stateful composition
Standards-based
Stateless message processing
Lighterweight footprint
Better performance
Full middleware platform (all in one)
Lower TCO due to an all in one runtime
Better performance
Standards-based
migration
adding usage type
How to migrate to Process Orchestration?
Migration versus in-place upgrade
Migration (side-by-side deployment)
In-place upgrade
Pros
Minimized downtime
Clean up of scenarios
Less hardware requirements
Defined end date
Cons
Basic setup from scratch
More hardware needed, higher
maintenance and operational costs
Rollback risk
Not possible for all installation options
Source system
Target system
In-place?
PI Dual Stack 7.1x & 7.3x
Process Orchestration 7.31/7.40
no
PI Java only 7.3x
Process Orchestration 7.31/7.40
yes
BPM* 7.x
Process Orchestration 7.31/7.40
yes
PI Dual Stack 7.1x & 7.3x
PI Java only 7.31/7.40
no
PI Java only 7.30
PI Java only 7.31/7.40
yes
PI Dual Stack 7.1x & 7.3x
PI Dual Stack 7.31/7.40
yes
* plus optionally further usage types: Adobe Document Services (ADS), Development Infrastructure (DI), Guided Procedures (GP)
Migrating from PI Dual Stack to Process Orchestration
Side-by-side deployment
Migration activities
1.
Install new PO system running side-by-side to existing PI dual stack system
2.
Setup/sync System Landscape Directory
3.
Transport of Enterprise Services Repository objects
4.
Migrate Integration Directory objects using migration tool
5.
Redesign of ABAP based artifacts (ABAP mappings, ccBPM processes, etc.) in Process
Orchestration system
6.
Setup new message based alerting
Source system
Transition phase
Target system
PI Dual Stack 7.1x/7.3x ABAP Java PI Dual Stack 7.1x/7.3x ABAP Java Process Orchestration 7.31/7.40 PI Java only BPM/BRM Java Process Orchestration 7.31/7.40 PI Java only BPM/BRM Java
Migrating from PI Dual Stack to Process Orchestration
How to replace ABAP based artifacts?
PI Dual Stack
Alternative options
ccBPM
NW BPM or in some cases PI Java standard features (see
SAP
Process Orchestration Integration Patterns
)
ABAP mappings
Graphical mappings, Java or XSLT mappings
ABAP based adapter (IDoc,
HTTP, WS-RM)
Java based adapter version (IDoc, HTTP), exception: WS-RM adapter
not available
Custom ABAP tables
(e.g. for more complex routing
rules)
1.
Explore using SAP NetWeaver BRM
2.
Use an alternative ABAP based system for maintaining custom
ABAP tables and perform an RFC lookup in message mapping to
retrieve key information.
3.
Create custom SQL table in Java and perform mapping lookup
Number range buffer (TA
SNRO)
1.
Use an alternative ABAP based system for number ranges and
perform an RFC lookup in message mapping to retrieve the next
number.
2.
Create your own number range object handling using SQL
database (Java class available)
Unified Key Mapping Service
(UKMS)
Use an alternative ABAP based system for UKMS and perform an RFC
lookup in message mapping to retrieve key information.
How to determine migration effort and steps to take?
Check out
Migration Guide to AEX of PI
7.3x for Integration Scenarios
available
on SCN
Feature comparisons of the different PI
releases
How to identify which integration
scenarios can be migrated, which cannot,
and which can be but requires additional
work
Detailed description of migration process
Process Orchestration Migration Scoping
Tool: Generates a report of existing
scenarios identifying the migration tasks
needed for each scenario
References to other articles and papers
Migration to Process Orchestration
Less configuration effort with integration directory migration tool
Migrate classical PI scenarios to
integrated configuration objects
Supporting both Java-only and dual-stack target
systems
Tool runs in target system
Available from releases 7.30 SP09, 7.31 SP07
and 7.40 SP2
Source PI system as of XI 3.0 and newer
Renaming of objects via renaming rules
Conversion of ABAP based adapter channel
attributes to Java channels where possible
Migration and mass change support for
communication channels
Scenarios that are not supported
Receiver Rule objects in directory
ABAP mappings
ccBPM
Launch from configuration
and monitoring home page
Migration to Process Orchestration
Leverage integration pattern best practices
Providing best practices and guidelines on how
to implement common integration and business
requirements on Process Orchestration
Enterprise integration patterns
–
Help in solving recurring problems faced in the
integration of enterprise applications
–
See
Enterprise Integration Patterns: Designing,
Building, and Deploying Messaging Solutions
by
Gregor Hohpe and Bobby Woolf
Enterprise integration patterns on Process Orchestration
– Blog on SCN
describing how to best implement
enterprise integration patterns on PI/PO
Support for abstract interfaces to allow re-use of
existing design time artifacts
Enhanced operations
Improved runtime availability via near-zero downtime maintenance
Today (shipped with SL toolset)*
Applying support packages with nZDM tool for PI Dual Stack
Upgrade paths 7.1x/7.30 dual stack to 7.31 dual stack
Roadmap
nZDM for BPM (planned with SL toolset 1.0 SP10)
–
SAP NetWeaver 7.3, starting with SP07
–
Enhancement package 1 of SAP NetWeaver 7.3, starting with SP02
–
SAP NetWeaver 7.4, all SPs
nZDM for Process Orchestration (planned in 2014) supporting all Java only installation options
* See SAP note
1825209
Version 1
Version 1
Clone
System
Production
System
setup clone maintenance
custom and automatic recording stop
restart
restricted use (business only mode) business downtime normal productive use
replication
switch
test & verification
Maintenance mode (fenced, no jobs) Test mode (optional) restricted
Thank you
Contact information:
Udo Paltzer
Product Management
Appendix
Integration Directory Migration Tool
Migrating classical PI scenarios to Integrated Configurations Step-by-Step
(1/5)
Integration Directory Migration Tool
Migrating classical PI scenarios to Integrated Configurations Step-by-Step
(2/5)
Source scenario(s) selection
By Sender Agreement
By Configuration Scenario (all sender agreements in the scenario are used)
Integration Directory Migration Tool
Migrating classical PI scenarios to Integrated Configurations Step-by-Step
(3/5)
Automatic directory objects matching and migration checks
Integration configuration
preview
Preview of the integrated
configuration and required
objects
Choose target adapter
engine and metadata version
for channels
Apply renaming rules
Passwords are not
preserved via the tool
Integration Directory Migration Tool
Migrating classical PI scenarios to Integrated Configurations Step-by-Step
(4/5)
Create objects and track proceeding
Objects created in a new change list per scenario
Deletion of conflicting sender agreement on the target system
Launch the target Integration Directory directly from this page
Integration Directory Migration Tool
Migrating classical PI scenarios to Integrated Configurations Step-by-Step
(5/5)
Integration Directory Migration Tool
Renaming of directory objects
Options:
Renaming of party, service,
channel objects via reusable
renaming rules
Business system renaming
according to SLD transport
targets
Support for content based
routing constant replacement
(expression constants)
Integration Directory Migration Tool
Migration and mass change support for communication channels
Migrate channels between
systems and PI releases
Support for the
non-transportable fields
Migrating passwords is not
supported
Support for mass channel
changes
metadata version
adapter specific attributes
target adapter engine
module properties
© 2014 SAP AG or an SAP affiliate company.
All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or SAP affiliate company 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.
In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AG’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
