Upgrade Guide - SAP Help Portal

■

■

© Copyright 2011 SAP AG. 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.

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 MultiWin are 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, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,

ByDesign, SAP Business ByDesign, 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 in

several other countries all over the world. 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 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.

Disclaimer

Some components of this product are based on Java™. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used

by SAP’s Support Services and may not be modified or altered in any

way.

SAP AG

Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Typographic Conventions

Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example

text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see

Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Contents

08/07/11 4/16

Contents

Contents ................................................................................................................................... 4

1 Introduction ......................................................................................................................... 5 1.1 Document History ............................................................................................................ 5 1.2 About this Document ....................................................................................................... 5 1.3 Before You Start .............................................................................................................. 6

2 Quick Guide ......................................................................................................................... 7 2.1 Overview Graphic ............................................................................................................ 7 2.1 Quick Steps...................................................................................................................... 9

3 Prequisites ......................................................................................................................... 10

4 Modification Steps ............................................................................................................ 11 4.1 Provide the newest application SCAs manually ............................................................ 11 4.2 Create a 7.30 SCA version of the modified application ................................................. 11

5 Upgrade Steps ................................................................................................................... 13 5.1 Prepare the Solution Manager ....................................................................................... 13 5.2 Provide the newest NetWeaver SCAs via the Maintenance Optimizer ......................... 13 5.3 Execute the Upgrade with the SAP Java Upgrade Tool ................................................ 14

6 Follow-Up Activities .......................................................................................................... 15

7 References ......................................................................................................................... 16

1 Introduction

5/16 08/07/11

1 Introduction

1.1 Document History

Before you start the upgrade, make sure that you have the latest version of this document on SAP Service Marketplace at:

http://service.sap.com/instguides.

The following table provides an overview about the most important document changes.

Version Date Description

1.0 07/11/2011 First version

1.2 About this Document The purpose of this document is to give the customer an overview about the upgrade process of CRM Web Channel 7.0 on CRM 7.0 or ERP E-Commerce 7.0 on EhP4 FOR SAP ERP 6.0 on to the new SAP NetWeaver 7.3 platform.

The standard upgrade process for NetWeaver applications does not include the handling of modified Suite applications. In the area of Web Channel/E-Commerce modifications are quite common and therefore this guide describes specifics in the upgrade procedure of these applications. This guide is also applicable in case you have installed only a few Software Components of the mentioned Product Instances.

Most parts of the upgrade process remain the same as for unmodified applications. The main differences will be described in SAP Note 1602476, which should be the main entry point for this document. The present document gives an overview about the complete process. It lists all steps with a short description, but should not work as a replacement for the upgrade guides for NetWeaver 7.3 rather should be used as an additional document.

The upgrade guides for SAP NetWeaver 7.3 are available on SAP Service Marketplace at:

http://service.sap.com/upgradenw73.

The document starts with a quick guide where the main steps are listed and also demonstrated in a graphic. The descriptions of the steps are given in the subsequent chapters.

1 Introduction

08/07/11 6/16

1.3 Before You Start

1.3.1 Naming Conventions The terms CRM Web Channel 7.00 on CRM 7.0 and ERP E-Commerce on EhP4

FOR SAP ERP 6.0 will be used in synonym. Short terms are Web Channel and E-Commerce. In case of differences between CRM and ERP this will be highlighted explicitely

Based on CRM the software component version of the start system will always be mentioned as 7.0. The software component version of the target system is named as 7.30 (CRM 7.0 on NetWeaver 7.3).

AS Java or J2EE are used in synomym and are the terms for Application Server Java.

CMS is the term for Change Management Service.

MOPZ is the term for Maintenance Optimizer.

NW is the term for SAP NetWeaver.

NWDI is the term for NetWeaver Development Infrastructure.

SAPJup is the term for SAP Java Upgrade Tool.

SCA is the term for Software Component Archive.

SLD is the term for System Landscape Directory.

SMP is the term for SAP Service Marketplace.

UT is the term for Usage Type.

1.3.2 Software Components In the present document the used Software Components will be mentioned by their technical names.

SAP-CRMDIC: SAP JAVA DATA DICTIONARY

SAP-SHRAPP: SAP SHARED JAVA APPLIC.

SAP-SHRWEB: SAP SHARED WEB COMPONENTS

SAP-SHRJAV: SAP SHARED JAVA COMPONENTS

SAP-CRMAPP: CRM JAVA APPLICATIONS

SAP-CRMWEB: CRM JAVA WEB COMPONENTS

SAP-CRMJAV: CRM JAVA COMPONENTS

CUSTCRMPRJ: CRM JAVA CUSTOMER PROJECT

STRUTS: APACHE JAKARTA STRUTS

SAP-IPCMSA: CRM IPC MOBILE

1.3.3 SAP Notes for the Upgrade The following notes should be considered in order to enable a smoothly upgrade process.

Make sure that you have the up-to-date version of each SAP Note, which you can find on

SAP Service Marketplace at: http://service.sap.com/notes

Note Number Short Text

1602476 Upgrade of CRM 7.0 / NW70x to NW7.3 with modifications

1468349 SAP Business Suite 7 for SAP NetWeaver 7.3 hub systems

669669 Updating the SAP Component Repository in the SLD

1603103 SMSY: NetWeaver 7.3 Upgrade

2 Quick Guide

7/16 08/07/11

2 Quick Guide

2.1 Overview Graphic The graphic displayed on the next page should give an overview about the complete process.

The picture is divided into three parts: The Software Components on the SAP Service Marketplace, the involved SAP Tools and the Java Systems (Start and Target System).

Within the graphic two different types of steps are used to demonstrate the step order. In general both step types can be executed independently from each other.

Romanic Numbers (dashed line) are used to describe the steps for modifying the application

Arabic Numbers (continuous line) are used to describe the upgrade steps in general

The SAP Java Upgrade Tools handles Development and Consolidation systems different from Test and Production systems.

“For Development and Consolidation, SAPJup keeps the modified version of the SCs and deploys only the successors of SCs that are not modified, and SAPJup copies the modified SCs to the appropriate directories; for Test and Production, however, SAPJup refuses to deploy until replacement components are made available.”

This means the Romanic steps have to be completed before starting SAPJup.

Steps mentioned in the graphic:

Modification steps:

Step I) Put needed SCAs for NWDI manually into Basket

Step II) Download design time SCAs from Basket

Step III) Import SCAs needed for modification and dependent SCAs into new track

Step IV) Upport all 7.0 modifications to the new 7.30 software component version

Step V) Provide modified SCA in transport directory

Upgrade steps:

Step 1) Transfer data Step 2) Start MOPZ transaction for Z_NW

Step 3) Stack.xml will be calculated

Step 4) Put NW SCAs into Download Basket

Step 5) Download SCAs from Download Basket into shared transport directory

Step 6) NW 7.3 SCAs and unmodified SCAs will be deployed directly Step 7) Modified SCAs will be deployed depending on the user’s decision

The complete upgrade process itself will be splitted in four parts:

1. Prerequisites 2. Modification steps 3. Upgrade Steps 4. Follow-Up Activities

The following graphic shows exemplary the upgrade process of a system where parts of the CRM AS Java instance 7.0 are installed. CUSTCRMPRJ 7.0 include the modified applications, SAP-CRMDIC 7.0 is a standard SAP component without modifications.

2 Quick Guide

08/07/11 8/16

2 Quick Guide

9/16 08/07/11

2.1 Quick Steps This chapter should give an overview of the steps which will be described in detail within the following chapters. The steps mentioned in the graphic are assigned as well.

Prerequisites:

1. You used NWDI before to modify the application deployed on the start system 2. Your start system is under NWDI control and both share the same transport directory 3. Your SLD is updated

Modification steps:

1. Provide the newest application SCAs manually (Step I to Step III)

2. Create a 7.30 SCA version of the modified application within the NWDI (Step IV and Step

V)

Upgrade Steps:

1. Prepare the Solution Manager (Step 1) 2. Provide the newest NetWeaver SCAs via the Maintenance Optimizer (Step 2 to Step 5)

3. Execute the Upgrade with the SAP Java Upgrade Tool (Step 6 and Step 7)

Follow-Up Activities

1. Update the system landscape via transaction SMSY within the Solution Manager system

3 Prequisites

08/07/11 10/16

3 Prequisites In order to start the upgrade for Web Channel 7.0 you should make yourself familiar with the preparation steps mentioned in the Upgrade Guide for NetWeaver 7.3.

Especially the following things need to be considered to run your upgrade smoothly:

1. You are familiar with the NWDI and with the process of modifying a CRM or ERP web application.For more information about the maintenance process for NWDI-driven system landscapes, see SAP Library at:

http://help.sap.com/nw70 SAP NetWeaver 7.0 SAP NetWeaver 7.0 Library

(EHPx) English SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics Working with the Development Infrastructure Administration of the Development Infrastructure Maintenance of an NWDI-Driven System Landscape or:

http://help.sap.com/nw73 SAP NetWeaver 7.3 Library English SAP

NetWeaver Library: Function-Oriented View Solution Life Cycle Management Using the Development and Production Infrastructure Development Infrastructure (DI) Maintenance of an NWDI-Driven System Landscape Your modified application which has been deployed on the start system has been created within the NWDI as well. A track for release 7.0 exists. For more information, see Development and Extension Guide for E-Commerce on SAP

Service Market Place at: http://service.sap.com/crm-inst SAP CRM 7.0

Operate

2. You followed the preparation steps described in the online documentation Open NWDI documentation (link listed above) Preparation Steps

Enable a shared transport directory for CMS Server and the AS Java Runtime Systms If this is not possible follow the described steps instead

Your start system is under NWDI control

3. Your SLD is up to date (Follow instructions of SAP Note 669669) If this is not the case you won’t be able to create a new track within the NWDI including the new Software Component Versions 7.30.

4 Modification Steps

11/16 08/07/11

4 Modification Steps

4.1 Provide the newest application SCAs manually

1. For CRM: Navigate to the SAP Service Marketplace:

http://service.sap.com/swdc Support Packages and Patches A - Z

Index Support Packages and Patches – C SAP CRM SAP CRM 7.0 Entry

by component

For ERP: Navigate to the SAP Service Marketplace:

http://service.sap.com/swdc Support Packages and Patches A - Z

Index Support Packages and Patches – E SAP ERP SAP ERP ENHANCE

PACKAGE EHP4 FOR SAP ERP 6.0 Entry by component

2. Choose NWDI Design/Build Time NW7.3”/ “SAP XECO - design time NW7.3 and put

the following SCAs manually to the Download Basket:

a. Required:

i. SAP-CRMDIC 7.30

ii. STRUTS 1.1

iii. TEALEAF 4.5

b. Optional:

i. SAP-IPCMSA 7.30

ii. Possible in case of ERP:

SAP-SHRAPP 7.30 and SAP-SHRWEB 7.30

iii. Possible in case of CRM:

1. SAP-SHRAPP 7.30 and SAP-SHRWEB 7.30

2. SAP-CRMAPP 7.30 and SAP-CRMWEB 7.30

3. Use the Download Manager to download the SCAs from the Download Basket into

the shared transport directory

4.2 Create a 7.30 SCA version of the modified application

1. Create a new track within the NWDI

a. Add the new Software Components which should be modified to the track

(The package type is: Source and Archive):

i. CUSTCRMPRJ 7.30

This package is delivered empty and should be used to encapsulate

the modified applications for CRM and ERP.

The only content is the metadata delivered through SLD. It contains

the dependencies required for development of Web Channel/E-

Commerce applications. You are free to change the software

component metadata.

ii. SAP-CRMDIC 7.30

iii. SAP-SHRWEB 7.30 and SAP-SHRAPP 7.30

iv. SAP-CRMWEB 7.30 and SAP-CRMAPP 7.30

v. SAP-IPCMSA 7.30

b. Set the build variant to JDK 1.6

2. Import the following SCA files into the new track:

4 Modification Steps

08/07/11 12/16

a. Same list which has been added for the track as software components to be

modified

b. All dependent SCAs with package typ Archive

NetWeaver SCAs can be found here via the NetWeaver product instance:

http://service.sap.com/swdc Support Packages and

Patches A - Z Index Support Packages and Patches – N SAP NETWEAVER SAP NETWEAVER 7.3 Entry by Component Application Server Java

c. Optional: old SCA version of the modified application (e.g. CUSTCRMPRJ

7.0)

3. Upport the modifications to the new release

4. Build and assemble the new SCAs

5. Provide the new SCA version in the shared transport directory

5 Upgrade Steps

13/16 08/07/11

5 Upgrade Steps

5.1 Prepare the Solution Manager 1. Capture the data of the start system using the SLD

2. Maintain the product systems according to your CRM or ERP applications

a. Create the product system for SAP NetWeaver 7.0x

i. Select the relevant Usage Types

Application Server Java

Further instances from SAP NetWeaver 7.0x if installed

b. In case of CRM: Create the product system SAP CRM 7.0

i. Select the relevant Usage Types

Optional: NWDI Design/Build Time

As the SCAs used for modification have been downloaded

manually, it does not matter if the design time is selected

here.

Optional: CRM Application Server Java (Should only be

selected in case all included Software Components are

installed on the system SAP-CRMDIC, SAP-SHRAPP and

SAP-CRMAPP)

CRM Application Server ABAP

Further instances from SAP CRM 7.0 if installed

c. In case of ERP: Create the product system SAP ERP 6 EHP 4

i. Select the relevant Usage Types

Optional: SAP XECO - design time

Optional: SAP XECO (Should only be selected in case all

included Software Components are installed on the system

SAP-CRMDIC, SAP-SHRAPP)

Further instances from SAP ERP 6.0 respectively EHP4

FOR SAP ERP 6.0 if installed

3. Create a logical component for each product system At least a logical

component for SAP NetWeaver 7.0x is required.

4. Optional: Add the product systems to a solution (development, productive system

etc.)

5.2 Provide the newest NetWeaver SCAs via the Maintenance Optimizer

1. In SAP Solution Manager, start transaction SOLMAN_WORKCENTER and choose

Change Management

2. Choose New Maintenance Transaction

3. If you have maintained a solution, choose the solution to which your system(s)

belong(s)

4. Select the product version of the system you want to upgrade (e.g. SAP NetWeaver

7.0)

5. Select the product system(s) that you want to include in the maintenance transaction

6. Choose Calculate Files Automatically as the file selection mode

5 Upgrade Steps

08/07/11 14/16

7. Choose the option “Upgrade” in order to receive the possible target releases

8. Specifiy SAP NetWeaver 7.3 as the target release and the corresponding Support

Package Stack (min. 02 (03/2011))

9. Choose any additional instances that you want to install

10. Choose the platform dependent files according to your Operating System and

database

11. Choose stack-(in-)dependent components

Preinstalled Software Components like SAP-CRMDIC which could not be

represented by a product instance will be proposed here, but with the version

of the start release!

Don’t select this in order to avoid having SCA files with different

versions.

The correct successor file has to be provided manually within the SAPJup.

12. A Stack.xml will be generated with includes a list of all required software packages

for the upgrade.

The calculated list of software packages are pushed to the Download Basket on the

SMP. (If configured the download can be executed via the Software Lifecycle

Manager as well.)

13. Open the SAP Download Manager

14. Download the SCAs provided in the Download Basket of the SMP to the shared

transport directory

5.3 Execute the Upgrade with the SAP Java Upgrade Tool

1. Mount the Upgrade Master DVD

2. Execute the startup script which creates a new upgrade directory to

\usr\sap\<SID>\upg

3. Start the Upgrade GUI

For more information about how to start the Upgrade GUI, see Upgrade Guide ‒ SAP

NetWeaver 7.3 <Technology> for <Operating System> <Database> on SAP Service

Marketplace at http://service.sap.com/upgradenw73

4. Make basic entries for the java system upgrade

a. Include the correction package in the upgrade

b. Enter the solution manager key

c. SAPJup checks if the system is under NWDI control

i. If yes: The user is asked to provide the relevant transport directories

(either global directory of NWDI or local transport directory …\EPS)

ii. If no: Reset Upgrade and make the appropriate settings within the

NWDI

For more information, see the SAP Library at:

http://help.sap.com/nw73 SAP NetWeaver 7.30 Library

English SAP NetWeaver Library: Function-Oriented View

Solution Life Cycle Management Using the Development and

6 Follow-Up Activities

15/16 08/07/11

Production Infrastructure Development Infrastructure (DI)

Maintenance of an NWDI-Driven System Landscape

d. Provide all required DVDs (e.g. SAP NetWeaver 7.30 Java including

Developer Workplace) during the preparation phase

5. Make entries for the target system configuration

a. Specify the target support package stack in the phase

BIND_SUPPORT_PACKAGES

b. During the phase BUILD_COMPONENTS_LIST the upgrade process

determines the original SCAs from the start system and assigns them to the

provided successor SCA files automatically. In case a successor could not

be calculated a different handling can be defined by the user:

i. Remove: for components not needed anymore

ii. Scan inbox – successor SCAs can be provided in the inbox

Follow up step: Rebuild component list

Different Handling between Development/Consolidation and Test/

Production Systems: SAPJup will not continue for Test/Prod systems

until ALL successor SCAs have been provided or skipped.

6. Provide the Jurisdiction Policy Files for Adobe Document Services

7. Shadow System will be created where the actual upgrade is executed

8. The provided components will be deployed to the shadow system

9. If the upgrade of the shadow system was successful, the downtime phase starts and

the shadow system is copied to the original system

6 Follow-Up Activities In case modified SCAs have not been deployed via SAPJup, the deployment needs to be executed via NWDI.

After the upgrade has been executed successfully the product systems and instances have to be updated in the solution manager with transaction SMSY.

For details, see SAP Note 1603103.

7 References

08/07/11 16/16

7 References Upgrade Guide SAP NetWeaver 7.3 Java

SAP Service Marketplace at: http://service.sap.com/upgradenw73

NetWeaver Development Infrastructure Documentation

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (EHPx) English SAP

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics Working with the Development Infrastructure Administration of the Development Infrastructure Maintenance of an NWDI-Driven System Landscape

http://help.sap.com/nw73 SAP NetWeaver 7.3 Library English SAP NetWeaver

Library: Function-Oriented View Solution Life Cycle Management Using the Development and Production Infrastructure Development Infrastructure (DI) Maintenance of an NWDI-Driven System Landscape

Development and Extension Guide for E-Commerce

SAP Service Marketplace at: http://service.sap.com/crm-inst SAP CRM 7.0

Operate