Migration and Upgrade Paths to SAP Process Orchestration Udo Paltzer Product Owner SAP Process Integration, SAP HANA Cloud Integration
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. 2014 SAP AG. All rights reserved. 2
Key Drivers for moving to SAP Process Orchestration 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 2014 SAP AG. All rights reserved. 3
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 2.5 million electronic messages per month processed through SAP Process Orchestration 3x faster message exchange with SAP Process Orchestration with a B2B add-on as compared to SAP Process Integration 1 system to monitor using a singlestack architecture instead of a dual-stack architecture Link to full case study 2014 SAP AG. All rights reserved. 4
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) 25% approximate reduction in total cost of ownership after consolidating BPM and PI under SAP Process Orchestration 33% approximate acceleration in development of new integration scenarios, as compared to using PI alone 100% reuse of existing PI mapping logic Link to full case study 2014 SAP AG. All rights reserved. 5
SAP NetWeaver Process Orchestration Improve processes and save integration costs 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. Model & execute processes fast and flexibly Manage integration across heterogeneous environments SAP NetWeaver Process Orchestration Business Process Management Business Rules Management A2A Integration B2B Collaboration * Automate decisions using business rules Connect to your business partners Design and govern your service-based integration Governance Monitoring & Analytics Monitor your integration processes * B2B Add-On is licensed separately from SAP NetWeaver Process Orchestration 2014 SAP AG. All rights reserved. 6
SAP NetWeaver Process Orchestration Where are we today? 6,000+ productive customers 100+ active customers with B2B add-on One integrated solution for human-centric and ~170 new customers per quarter 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 * based on customer case study 2014 SAP AG. All rights reserved. 7
SAP NetWeaver Process Orchestration Release history Business Process Management Business Process Analytics Consolidated SAP NetWeaver release Process orchestration solution bundle Business Rules Management Adobe forms and visual composer UIs UI generation CE 7.11 CE 7.2 NW 7.3 WD/ABAP task UI Java public API Co-deployment of PI, BPM, and BRM Major enhancements towards common Eclipse environment Business Process Management / Business Rules Management Process Orchestration NW 7.31 NW 7.4 PI 7.1x Process Integration NW 7.3 Messaging capability in the Adapter Engine (AE) Proxy connectivity on the AE Enable major scenario shift from dual-stack PI to Java-only PI Providing Standalone Engine (AEX) Integration flows B2B add-on Message flow monitor Process Orchestration on SAP HANA IDoc adapter on the AE 2014 SAP AG. All rights reserved. 8
How to migrate to Process Orchestration? Migration and upgrade paths Integration-centric Higher footprint No further investments for ABAP Process stateful composition Standards-based adding usage type migration adding usage type Full middleware platform (all in one) Lower TCO due to an all in one runtime Better performance Standards-based Stateless message processing Lighterweight footprint Better performance 2014 SAP AG. All rights reserved. 9
How to migrate to Process Orchestration? Migration versus in-place upgrade Pros Cons Migration (side-by-side deployment) Minimized downtime Clean up of scenarios Basic setup from scratch More hardware needed, higher maintenance and operational costs In-place upgrade Less hardware requirements Defined end date 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) 2014 SAP AG. All rights reserved. 10
Migrating from PI Dual Stack to Process Orchestration Side-by-side deployment Source system Transition phase Target system PI Dual Stack 7.1x/7.3x PI Dual Stack 7.1x/7.3x Process Orchestration 7.31/7.40 Process Orchestration 7.31/7.40 PI Java only BPM/BRM PI Java only BPM/BRM ABAP Java ABAP Java Java Java 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 2014 SAP AG. All rights reserved. 11
Migrating from PI Dual Stack to Process Orchestration How to replace ABAP based artifacts? PI Dual Stack ccbpm ABAP mappings ABAP based adapter (IDoc, HTTP, WS-RM) Custom ABAP tables (e.g. for more complex routing rules) Number range buffer (TA SNRO) Unified Key Mapping Service (UKMS) Alternative options NW BPM or in some cases PI Java standard features (see SAP Process Orchestration Integration Patterns) Graphical mappings, Java or XSLT mappings Java based adapter version (IDoc, HTTP), exception: WS-RM adapter not available 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 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) Use an alternative ABAP based system for UKMS and perform an RFC lookup in message mapping to retrieve key information. 2014 SAP AG. All rights reserved. 12
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 relating to the migration process 2014 SAP AG. All rights reserved. 13
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 Launch from configuration and monitoring home page Scenarios that are not supported Receiver Rule objects in directory ABAP mappings ccbpm 2014 SAP AG. All rights reserved. 14
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 2014 SAP AG. All rights reserved. 15
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 restricted use (business only mode) business downtime normal productive use Production System Version 1 custom and automatic recording stop Maintenance mode (fenced, no jobs) Test mode (optional) restricted switch Clone System setup clone maintenance Version 1 test & verification replication restart * See SAP note 1825209 This is the current state of planning and may be changed by SAP at any time. 2014 SAP AG. All rights reserved. 16
Thank you Contact information: Udo Paltzer Product Management udo.paltzer@sap.com
Appendix Migration Tool Step-by-Step
Integration Directory Migration Tool Migrating classical PI scenarios to Integrated Configurations Step-by-Step (1/5) Source system selection from SLD or manually defined in the tool 2014 SAP AG. All rights reserved. 19
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) By Receiver Determination (for IDoc and ABAP Proxy scenarios) 2014 SAP AG. All rights reserved. 20
Integration Directory Migration Tool Migrating classical PI scenarios to Integrated Configurations Step-by-Step (3/5) Automatic directory objects matching and migration checks Tool automatically detects all objects belonging to selected configuration scenario 2014 SAP AG. All rights reserved. 21
Integration Directory Migration Tool Migrating classical PI scenarios to Integrated Configurations Step-by-Step (4/5) 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 2014 SAP AG. All rights reserved. 22
Integration Directory Migration Tool Migrating classical PI scenarios to Integrated Configurations Step-by-Step (5/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 2014 SAP AG. All rights reserved. 23
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) 2014 SAP AG. All rights reserved. 24
Integration Directory Migration Tool Migration and mass change support for communication channels Migrate channels between systems and PI releases Support for the nontransportable fields Migrating passwords is not supported Support for mass channel changes metadata version adapter specific attributes target adapter engine module properties etc. 2014 SAP AG. All rights reserved. 25
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. 2014 SAP AG. All rights reserved. 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 26