POP262

Meghna Shishodiya, Amrita Laxmi, Finny Babu, Ilya Stepanov, Alexander Bundschuh October, 2013

POP262

Migration Tool from Double Stack to Single Stack Integration Scenarios

2013 SAP AG or an SAP affiliate company. All rights reserved. 2

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

Migration Approach

Directory Content Migration Tool at a Glance

Exercises

Migration Approach


Which installation options are supported per release version?*

ABAP Java

1. PI Dual Stack (all releases)

+ Functional scope

- Higher TCO

- No innovations for ABAP

Java

2. PI Java only (since release 7.3)

- Functional limitations

+ Lower TCO

+ Performance

* simplified illustration, excluding SLD, tools, optional non-central adapter engines, etc.

3. Process Orchestration (since release 7.31)

++ Functional scope

+ Lower TCO

+ Performance

Java Java

PI Java only BPM incl. BRM

Single SID


How to get from PI 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

ABAP Java

PI Dual Stack 7.1x/7.3x PI Java only

Java

BPM incl.

BRM

Java

Process Orchestration 7.31/7.40

Migration activities

1. Install new PO system running side-by-side to existing PI dual stack system

2. Transport of Enterprise Services Repository objects

3. Migrate Integration Directory objects using migration tool

4. Redesign of ABAP based artifacts (ABAP mappings, ccBPM processes, etc.) in

Process Orchestration system

Source system Transition phase Target system

ABAP Java

PI Dual Stack 7.1x/7.3x PI Java only

Java

BPM incl.

BRM

Java

Process Orchestration 7.31/7.40


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

Migration Tool at a Glance


Integration Directory Migration Tool Migrating Configuration Scenarios at a Glance

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

Scenarios for which migration is not supported

Receiver Rule objects in directory

ABAP mappings

ccBPM

Launch from Configuration

and Monitoring Home page


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



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)



Automatic directory objects matching and migration checks

Tool automatically detects all objects belonging to selected configuration scenario


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



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 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

etc.

Exercises


Integration Directory Migration Tool Exercises

Scenarios

IDoc to proxy scenario

Misc. file to file scenarios

Applying renaming rules

Channel mass change


Further Information

SAP Education and Certification Opportunities

www.sap.com/education

Watch SAP TechEd Online

www.sapteched.com/online

SAP Public Web

scn.sap.com/community/process-orchestration

www.sap.com


SAP TechEd Virtual Hands-on Workshops and SAP TechEd Online Continue your SAP TechEd education after the event!

SAP TechEd Virtual Hands-on Workshops

Access hands-on workshops post-event

Available January March 2014

Complementary with your SAP TechEd registration

SAP TechEd Online

Access replays of keynotes, Demo Jam, SAP TechEd LIVE interviews, select lecture sessions, and more!

View content only available online

http://saptechedhandson.sap.com/

http://sapteched.com/online

Feedback Please complete your session evaluation for POP262.

Thanks for attending this SAP TechEd session.


2013 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.

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.

National product specifications may vary.

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.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Date post:	01-Oct-2015
Category:	Documents
Upload:	vkvk362
View:	220 times
Download:	5 times

POP262

Documents