SAP Upgrade Technology - New Features

8/9/2019 SAP Upgrade Technology - New Features

http://slidepdf.com/reader/full/sap-upgrade-technology-new-features 1/27

Application Lifecycle Management – Optimize

SAP Upgrade Technology – New Features

SAP Technology Solution Management

Lifecycle Management

November 2009



© SAP 2008 / SAP TechEd 08 / LCM 203 Page 2

Legal Disclaimer

This presentation is not subject to your licenseagreement 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 withoutnotice. 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.




News on Upgrade Technology

New Features on ABAP Upgrade

News on Java Upgrade

Upgrading Dual Stack Systems AS ABAP & Java

Agenda




New Features on ABAP Upgrade

FUNCTIONALITY

Less Input requests

Download directory

Tool-integrated Upgrade reset

LAYOUT

New Upgrade phase and

structuring model Separation in Tab pages

Wizard-like navigation between

the roadmap steps

Available for ABAP 7.01

Upgrades

What’s new regarding the

Look and Feel!

New Upgrade GUI




New Upgrade GUI - Layout

LAYOUT

New Upgrade phase andstructuring model

Separation in Tab pages

Wizard-like navigation

between the roadmap steps

New Upgrade GUI




Simplified Upgrade Procedure

– Download Directory

Download Directory

Possibility to include

Correction package

(mandatory)

Latest SAPup version

Support Packages

SAP Kernel

Enhancement Packages

DVD’S

Stack xml file

New Upgrade GUI




Only a few Dialog screens

New Upgrade GUI

Many Dialog screens

Simplified Upgrade Procedure

– Reduced number of dialog screens




1. News on Upgrade Technology

1.1. New Features on ABAP Upgrade

1.2. News on Java Upgrade

1.3. Upgrading Dual Stack Systems AS ABAP & Java

2. Implementation of Enhancement Packages

3. Best Practices to Manage Successful Technical Upgrade Projects

4. Summary

Agenda




Deployment-Based Upgrade (NW 7.0 based

systems) - Features

Java Upgrade

In-place Upgrade

Start release: NetWeaver 2004 SR1/SPS09

Generic procedure applicable for all SAP

Applications based on NW2004 onwards

Error and restart handling at any point Two major units:

Prepare

Upgrade

Key Take Aways Including the latest Support Package Stack

Preserve Customer Data

Migrate J2EE Engine configurations

Preserve application data and

configurations

Upgrade Modified Components

Archives, containing new releases of

modified and third-party components, can

be selected and deployed by SAPJup

Synchronized upgrade of Dual Stack systems




Deployment-Based Upgrade

- Preparation

Java Upgrade

Steps are performed during the

system uptime

Performing various parameter

and profile checks

Investigating the Source System

Extracting upgrade DVD‘s

Determining Usage Types to

be upgraded

Include Custom

development

components

Include Support

Packages

Calculate the

deployment list and

order

Preparation Steps

Perform

backup




Handling of Usage Types & Development

Components

Java Upgrade

Mapping of Usage Types

Key Take Aways

Determine installed scenarios in the start

system on the basis of significant

components

Presence of BI and MI must beconfirmed by user

Mapping the installed scenarios on NW04

to usage types of NW7.0

Upgraded system hosts the same usage types

as the source system

No option to install additional usage types

If a usage type has been detected, allusage types it depends on in NW7.0 will

be deployed to the system, e.g. on a

NW04 BI system, both BI and EP will be

deployed during the upgrade (because BI

depends on EP in NW7.0)





- Upgrade

Java Upgrade

Steps are mainly performed

during the downtime

Updating the Kernel

Major StepsStopping the system

Ensure that SAP*only can

access the system

Undeploying and deploying

SLOT1(file sys); SLOT2(db)

Updating the engine

bootstrap and adapting profiles

Undeploying and deploying

SLOT3(offline)Migrating

core engine

data

Starting

the system

in Safe

mode

Undeploying

and

deploying

SLOT4(online)

Running

application

migration

Stopping the

system

Re-enabling

the original

user store

Starting the

system




Handling of Usage Types & Development

Components

Java Upgrade

Renamed Development

Components

Key Take Aways

Un-deploying the old development components

Deploying the new development components

Issue due to un-deployment of components:

Loss of application configurations like security settings, logging configuration





- Uptime and Downtime

Java Upgrade

Upgrade Up-and Downtime

J2EE Engine is being modified and controlled by the upgrade procedure

The system is not productive

Even when the system is up – it can’t be used. Upgrade starts the J2EE Engine inSAFE mode during DEPLOY_ONLINE and RUN_APPLICATION_MIGRATIONphases.

The only active user is SAP* and it should not be changed during the downtime

J2EE Engine is up and running. It’s still productive, in use and untouched by theupgrade procedure

Whole PREPARE unit runs in Uptime

Reconfiguring J2EE Engine is not allowed during the Uptime

Upgrade can be stopped and cancelled during the Uptime

D o w n t i m e

U p t i m e








1.3.1. Synchronized Upgrade of ABAP & Java for SAP NetWeaver 7.0

1.3.2. New Dual Stack Upgrade for SAP NetWeaver PI 7.1



4. Summary

Agenda




Synchronized Upgrade of ABAP and Java

Key Take Aways Both stacks start and end the downtime

phases at same time Correct handling of common resources:

for instance, system profiles and profile

entries are shared by ABAP and Java stack

Except for the sync points, the upgrade

processes of both stacks are performed

independently

Prepare and Upgrade of ABAP and Java

Server must be performed in parallel withfollowing sync points:

At the beginning of the downtime

When the profiles are going to be modified

At the end of the downtime

If AS-JAVA is present the only option not to upgrade

AS Java is to de-install it latest at the PREPARE Dialog

REQ_J2EE

Dual-Stack Upgrade

Reduce the overall

downtime





- Detection of Dual Stack

Important

If AS JAVA has beendetected, the only option

not to upgrade AS Java is

to de-install AS Java latest

at the PREPARE Dialog

REQ_J2EE !

Dual-Stack Upgrade




Beginning of Downtime Changing Profiles


- Sync Points

Dual-Stack Upgrade

End of Downtime








1.3.1. Synchronized Upgrade of ABAP & Java for SAP NetWeaver 7.0

1.3.2. New Dual Stack Upgrade for SAP NetWeaver PI 7.1



4. Summary

Agenda




New Dual Stack Upgrade for SAP NW PI 7.1

Key Take Aways

Dual-Stack Upgrade

Reduce the overall

downtime

One upgrade process and one common UI for ABAP & Java

System Switch Technology available for ABAP & Java Provides helpful possibilities to minimize downtime:

Integration of Support Packages & Patches, Add-ons and Enhancement

Packages into shadow tables during the uptime

Conversion of large tables with the Incremental Data Conversion

(ICNV) during uptime (ABAP only)

Improved supportability




New Dual Stack Upgrade for SAP NW PI 7.1 -

Layout

New PI 7.1 Dual Stack Upgrade

Layout

New Upgrade phase and

structuring model ABAP & Java Upgrade

Steps merged into ONE

process

One common UI





News


News

Switch Upgrade

Technology for

AS JAVA, too !





News


News

Binding Support Packages

& Patches, Add-ons and

Enhancement Packages

into the Upgrade




New Dual Stack Upgrade for SAP NW PI 7.1 –

Supportability


Streamlined

error handling

Sophisticated

execution

control

Log and file

browsing

capabilities

News




Key Take Aways

New Upgrade GUI Layout and simplified upgrade

procedure for ABAP (SAP NW 7.01) Upgrade

New Upgrade GUI Layout and simplified upgrade

procedure for Java (SAP NW 7.1) and Dual Stack

(SAP NW 7.1) Upgrades

Established System Switch Upgrade Technology

is also available for Java (SAP NW 7.1) and Dual

Stack (SAP NW 7.1) Upgrades

Synchronized Upgrade procedure for Dual StackSAP NW 7.0 upgrades

Upgrade Steps for Dual Stack (SAP NW 7.1)

merged into ONE process and one common UI




Thank you for your time

Questions?

Kathrin WinkmannSAP Technology Solution Management

Life-cycle Management

SAP AGDietmar-Hopp-Allee16

69190 Walldor f Germany

E-Mail [email protected]

mailto:[email protected]

mailto:[email protected]




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 hereinmay be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries,eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWinare trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries.Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only.National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affi liated 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 Groupproducts and services are those that are set for th in the express warranty statements accompanying such products and services, if any. Nothing herein should be construedas constituting an additional warrant.

Copyright 2009 SAP AG

All Rights Reserved

Documents

SAP Upgrade Technology - New Features