Ug Nw73 Java+Unix+Oracle

8/22/2019 Ug Nw73 Java+Unix+Oracle

1/100

Upgrade GuideSAP NetWeaver 7.3 Java

For:

Java

UNIX

IBM DB2 for z/OS

IBM DB2 for Linux, UNIX, and Windows

SAP MaxDB

Oracle

Target Audience

System administrators

Technology consultants

PUBLICDocument version: 1.2 2011-10-20


2/100

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34

F +49/18 05/34 34 20www.sap.com

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 and Java are registered trademarks of Oracle.

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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius,

and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered

trademarks of Business Objects Software Ltd. Business Objects is an SAP company

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein

as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase 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 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 expressly prohibited, as is any decompilation of these components.

Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or

altered in any way.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

2/100 PUBLIC 2011-10-20
http://service.sap.com/instguides


3/100

Aspects Covered by this Guide

SAP Component

SAP NetWeaver

Usage Type

NetWeaver Application Server Java (AS Java)

NetWeaver Development Infrastructure (DI)

NetWeaver BI Java (BI Java)NetWeaver Enterprise Portal (EP)

NetWeaver EP Core (EPC)

NetWeaver Process Integration (PI)

NetWeaver Adobe Document Services

Platform

UNIX

Operating System

AIX

HP-UX

Linux

Solaris

Database

IBM DB2 for z/OS

IBM DB2 for Linux, UNIX, and Windows

SAP MaxDB

Oracle

Source Release

SAP NetWeaver 7.0 including enhancement package 1 (Java)

SAP NetWeaver 7.0 including enhancement package 2 (Java)

SAP NetWeaver 7.0 (Java)

SAP Web Application Server 6.40 Java

2011-10-20 PUBLIC 3/100


4/100

Typographic Conventions

Example Description

Angle brackets indicate that you replace these words or characters with appropriate

entries to make entries in the system, for example, Enter your .

Example

Example

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the

documentationhttp://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific

content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example Words or characters quoted from the screen. These include field labels, screen titles,

pushbutton labels, menu names, and menu options.

Cross-references to other documentation or published works

Example Output on the screen following a user action, for example, messages

Source code or syntax quoted directly from a program

File and directory names and their paths, names of variables and parameters, andnames of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, database table names, and key concepts of a programming language

when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

4/100 PUBLIC 2011-10-20
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0http://www.sap.com/


5/100

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version at the following location: http://service.sap.com/

instguides.

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

Version Date Description1.0 2010-11-29 First version no changes

1.1 2011-08-12 Revised version

1.2 2011-10-20 Correction: section Making Entries for the Target System Configuration

Correction: information about Mobile Infrastructure (MI) removed (not in the

upgrade scope)

2011-10-20 PUBLIC 5/100
http://service.sap.com/instguideshttp://service.sap.com/instguides


6/100

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1 Quick Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.2 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.3.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.3.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.3.3 SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.3.4 Accessing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2 Quick Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.1 Tool Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.1.1 Upgrade GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.1.2 Communication Between Back-End Processes and GUI . . . . . . . . . . . . . . . . . . 30

3.1.3 Upgrade Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.2 Technical Details of the Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.3 Planning the Upgrade of Non-Standard SAP Systems . . . . . . . . . . . . . . . . . . . 34

3.4 Upgrade of NWDI-Driven System Landscapes . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.5 Upgrade of Distributed and High Availability Systems . . . . . . . . . . . . . . . . . . . 36

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.1 Determining the Host for the Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.2 Checking the Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4.3 Checking the Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4.3.1 Checking the Source Release of the SAP System . . . . . . . . . . . . . . . . . . . . . . . 42

4.3.2 Meeting the Operating System-Specific Requirements . . . . . . . . . . . . . . . . . . 43

4.3.3 Upgrade of the Operating System and Database System: Overview . . . . . . . . . 43

4.3.4 Checking the Software Delivery Manager Version . . . . . . . . . . . . . . . . . . . . . . 48

4.4 Preparing SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.4.1 SAP Solution Manager Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

6/100 PUBLIC 2011-10-20


7/100

4.4.2 Installation of Landscape Verification 1.0 for SAP Solution

Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.4.3 Configuration of the Maintenance Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.4.4 Maintaining System Landscape Information . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.5 Selecting and Downloading Software Packages . . . . . . . . . . . . . . . . . . . . . . . . 53

4.6 PI: Archiving Messages in the PI Adapter Framework . . . . . . . . . . . . . . . . . . . . 55

4.7 PI: Resolving Inconsistencies in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4.8 Ensuring the Correct Kernel Directory Detection . . . . . . . . . . . . . . . . . . . . . . 56

4.9 EPC: Cleaning Up the Universal Worklist Cache . . . . . . . . . . . . . . . . . . . . . . . 56

4.10 EP: Preparations for Enterprise Portal Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.11 EP: Preparations for Knowledge Management and Collaboration

(KMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4.12 Preparations for Application Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4.13 Making Preparations in the Monitoring Area . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4.14 Preparing the Upgrade of Distributed and High Availability

Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4.15 Updating SLD Content of the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 5 Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.1 Meeting the Requirements for the Upgrade Directory . . . . . . . . . . . . . . . . . . . 64

5.2 Starting the Upgrade Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.3 Starting the Upgrade GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.4 Restarting the Upgrade Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.5 Resetting the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.6 Using the Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.7 Advanced GUI Options: Role Management and Alert Function . . . . . . . . . . . 70

5.8 Importing or Installing Software After Starting the Upgrade . . . . . . . . . . . . . . 72

5.9 Making Entries for the Configuration Roadmap Step . . . . . . . . . . . . . . . . . . . 72

5.9.1 Making Basic Entries for the Java System Upgrade . . . . . . . . . . . . . . . . . . . . . . 72

5.9.2 Making Entries for the Target System Configuration . . . . . . . . . . . . . . . . . . . . 74

5.9.3 Providing the JCE Jurisdiction Policy Files for Adobe Document

Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

5.10 Making Entries for the Checks Roadmap Step . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.11 Phase BEGIN_DOWNTIME_ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.12 Phase DOWNTIME_END_ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.13 Evaluating the Upgrade Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

2011-10-20 PUBLIC 7/100


8/100

Chapter 6 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6.1 Performing Follow-Up Activities for User root . . . . . . . . . . . . . . . . . . . . . . . . . 80

6.2 PCK: Using a Wizard for Automated Processing of Selected Follow-UpActivities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

6.2.1 PCK: Performing Follow-Up Activities for PCK . . . . . . . . . . . . . . . . . . . . . . . . 82

6.2.2 PI: Assigning PCK User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

6.2.3 PI-AF: Creating a JCo Destination for the ExchangeProfile . . . . . . . . . . . . . . . . 83

6.3 Performing Follow-Up Activities for the System Landscape

Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

6.4 Configuring SAP Start Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6.5 PI: Migrating Java Proxy-Based Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6.6 SAP MaxDB: Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

6.7 Performing Follow-Up Activities in the Monitoring Area . . . . . . . . . . . . . . . . 86

6.8 Performing Application-Specific Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

6.9 Performing Follow-Up Activities for SAP Solution Manager . . . . . . . . . . . . . . 87

6.10 Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

6.11 Performing Follow-Up Activities for the Composite Application Framework

Core (CAF Core) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

6.12 Performing Follow-up Activities for Application Migration . . . . . . . . . . . . . . . 90

6.13 Performing Follow-up Activities for NetWeaver Development Infrastructure(NWDI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6.14 Performing Follow-Up Activities for Adobe Document Services . . . . . . . . . . . 90

6.15 DI: Checking the CBS Service Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

6.16 PI: Adjusting the Adapter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

6.17 BI Java: Performing Follow-Up Activities for Business Warehouse . . . . . . . . . . 92

6.18 EP: Checking the KMC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

6.19 EP: Performing Follow-Up Activities for Knowledge Management and

Collaboration (KMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

6.20 Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

6.21 Installing Additional Application Server Instances . . . . . . . . . . . . . . . . . . . . . . 97

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

A.1 List of Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

8/100 PUBLIC 2011-10-20


9/100

1 Introduction

1.1 Quick Access

RECOMMENDATION

Use the checklist in the Quick Guide.

The Quick Guide [page 19] checklist provides you with an overview of all necessary tasks in

chronological order. If you are experienced in performing upgrades, the checklist may contain

all you need to know to perform the upgrade successfully. If you need more information, follow

the links to the detailed descriptions.

1.2 About This Document

Purpose

The information in this document is intended for SAP system administrators with operating system,

database, and SAP NetWeaver Application Server knowledge.

Integration

Depending on your source release, you require different upgrade or update guides:

For source release SAP NetWeaver 7.0 including enhancement package 1 and lower, you require

this document.

For source release SAP NetWeaver Process Integration 7.1 and higher, SAP NetWeaver Mobile 7.1

and higher, and SAP NetWeaver Composition Environment 7.1 or higher, you require the

documents How to Upgrade to SAP NetWeaver 7.3 and Update Guide Update of SAP Systems with Software

Update Manager 1.0available at http://service.sap.com/upgradenw73.

NOTE

To find the latest version of this document and theUpgrade Master Guide, see SAP Service Marketplace

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

In addition to this document, you also require other information, such as the Release Notes for the

applications that you implement, the SAP Implementation Guide (IMG), the SAP Notes that are specific

to this upgrade, and any other documentation referred to in this document.

Constraints

The upgrade program does not support an update of an SAP system with SAP enhancement packages

only. If you want to update the SAP enhancement package in your existing system, use the Software

1 Introduction

1.1 Quick Access

2011-10-20 PUBLIC 9/100
http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/upgradenw73


10/100

Update Manager (SUM). You can find the corresponding document for this update procedure on SAP

Service Marketplace at http://service.sap.com/instguides.

How To Use This Document

CAUTION

It is essential that you use the Quick Guide [page 19] checklist to guide you through the upgrade.

It contains certain product-specific information that is not repeated in the detailed descriptions.

The document on upgrading the SAP system contains a large amount of information. Its aim is to give

you both the information you need immediately at your fingertips, as well as providing additional

background information when required.

The document is structured as follows:

Chapter 1 IntroductionThis chapter contains information about how to use this document, new features of the upgrade,

some naming conventions for the document, and the SAP Notes necessary for the upgrade.

Chapter 2 Quick Guide

The Quick Guide lists all activities in the right order. For more information about the single steps,

follow the links in the Quick Guide [page 19]. This quick guide also contains product-specific

information, for example, preliminary sizes for the upgrade directory or database archives, and the

list of necessary DVDs.

Chapters 3 to 6 Component Upgrade

This chapter contains information about how to plan, prepare, and perform the upgrade and about

follow-up activities after the upgrade.

NOTE

Activities that you have to perform for a specific product only are marked with the product

name in the title, for example, : .

Release numbers in these texts refer to the product releases.

Activities that are not marked with a product name in the title apply to all upgrades of

products using the relevant SAP NetWeaver Application Server Release.

Release numbers in these texts refer to the underlying SAP NetWeaver Application Server.NOTE

If this document contains information for more than one operating system or source release

(see Aspects Covered by this Guide on page 3), texts that apply to one or more of these aspects are

marked with bars.

These bars always show all aspects for which the text is valid, even though these aspects may

not be of interest for your specific upgrade.

Chapter A Appendix

This chapter contains a list of the documentation referenced in this guide.

1 Introduction

1.2 About This Document

10/100 PUBLIC 2011-10-20
http://service.sap.com/instguides


11/100

1.3 Before You Start

1.3.1 Naming Conventions

SAP NetWeaver System and SAP System

In this document, the term SAP system is the same as SAP NetWeaver system. SAP is also used

as a synonym for SAP NetWeaver in terms such as SAP start profile or SAP system language.

SAP System ID

In this document, the SAP system ID is abbreviated as SAPSID or sapsid. If is used, your

SAP system ID must be in lowercase letters, for example prd. If is used, you must write

in uppercase letters, for example PRD.

ID for the SAP System Release

In this document, stands for the relevant SAP system release, without a decimal point, suchas 730. If an enhancement package has been installed in the SAP system, the last digit indicates the

enhancement package version.

SAP NetWeaver and SAP NetWeaver Enhancement Packages

In this document, we distinguish between Release 7.0 of SAP NetWeaver and an enhancement package

release of SAP NetWeaver such as 7.0 including enhancement package 1 or 2. If Release 7.0 of SAP

NetWeaver is mentioned explicitly, it does not refer to Release 7.0 including enhancement package 1

or 2 of SAP NetWeaver as well.

SAP NetWeaver Application Server and SAP Web Application Server

The term SAP NetWeaver Application Server Java (or the short form SAP NW AS Java) is used

in this document when referring to Release 7.0 and higher.

The term SAP Web Application Server Java (or the short form SAP Web AS Java) is used in this

document when referring to Release 6.40.

SAP System Instances

As of SAP NetWeaver 7.1, the concept and naming of SAP system instances has changed. The terms

central instance and dialog instance are no longer used. Instead, the SAP system consists of the

following instances:

Application server instances

Application server instances can be installed as primary application server instance or additional

application server instances.

Central services instance

Database instance

Instance Name

In this document, is used as a placeholder for the instance name in the instance

directory path of your system.

1 Introduction


2011-10-20 PUBLIC 11/100


12/100

SubstitutewithJ for the primary or additional application server instance, where

stands for the instance number.

Only valid for: IBM DB2 for Linux and UNIX and Windows |

IBM DB2 for Linux, UNIX, and Windows and Short Forms

In this document and in the upgrade dialogs, the short forms DB2 for Linux, UNIX, and Windows

or DB2 LUW are used for the database IBM DB2 for Linux, UNIX, and Windows, and, in certain cases,

the SAP ID DB6 is used as well. In previous SAP documents, IBM DB2 for Linux, UNIX, and Windows

was referred to as IBM DB2 Universal Database for UNIX and Windows or DB2 Universal Database

for UNIX, Windows.

End of: IBM DB2 for Linux and UNIX and Windows |

Only valid for: IBM DB2 for z/OS |

IBM DB2 for z/OS and Short Forms

In this document and in the upgrade dialogs, the short form DB2 for z/OS is used for the database

IBM DB2 for z/OS, and in certain cases, the SAP ID DB2 is used as well. In previous SAP documents,

IBM DB2 for z/OS was referred to as IBM DB2 Universal Database for z/OS, IBM DB2 Universal

Database for OS/390 or IBM DB2 Universal Database for OS/390 and z/OS.

End of: IBM DB2 for z/OS |

1.3.2 New Features

New Features in the Upgrade

Feature Description Availability

Upgrade procedure and

handling

The upgrade procedure and handling have

changed significantly. Amongst others, the

changes are:

New user interface (upgrade GUI)

Upgrade phases are grouped into

roadmap steps.

As of SAP NetWeaver PI 7.1

Troubleshooting and

administration

documentation included inthe upgrade program

The troubleshooting and administration

documentation is included in the upgrade

program. The upgrade tool unpacks thedocumentation at the beginning of roadmap

step Extraction. You can access the

documentation from the HTML start page.


Start profile As of this release, the start profile was

appended to the instance profile. This applies

to the SAP system as soon as the upgrade

program has performed the switch to the

new release.


SAP kernel file structure As of this release, the SAP kernel file

structure was changed. The SAP kernel is


1 Introduction


12/100 PUBLIC 2011-10-20


13/100

Feature Description Availability

now located in directory /usr/sap/

/SYS/exe/uc/.

Configuration ofsapcpe If you have not already done so, sapcpe is

automatically configured during the

upgrade and added to the instance profile.

sapcpe ensures that the files for the SAP

kernel are copied to the additional

application server instances.


Upgrade of additional

application server instances

The procedure for the upgrade of additional

application server instances was changed.

PhaseDETERMINE_DI_KERNEL in roadmap step

Configuration checks if your additional

application server instances run on different

platforms than the primary application

server instance. If so, it unpacks the relevantSAP kernel files to the subdirectory

for the java subdirectory of the

upgrade directory.


1.3.3 SAP Notes for the Upgrade

Definition

To prepare and perform the upgrade of your SAP system, you require some additional information

that is not included in this document. This information is in a range of SAP Notes in SAP Support Portal(http://service.sap.com/support), some of which you must read before you prepare the upgrade.

Besides the central Upgrade Note and the application-specific Upgrade Note, you can additionally find

separate SAP Notes for the database-specific sections. When you actually upgrade the SAP system, you

need information from some additional SAP Notes. These SAP Notes are named at the appropriate

places in this document.

SAP Notes for Preparing the Upgrade

You must request the following SAP Notes from SAP Support Portal before you start your upgrade:

Central Upgrade NoteContains the general upgrade problems and information about the fix archive for the upgrade

Upgrade Note for SAP NetWeaver

Contains SAP NetWeaver-specific information

SAP Note for your database

Since these SAP Notes are updated regularly, make sure that you always use the newest version. The

following list contains the SAP Notes you need to prepare for the upgrade:

1 Introduction


2011-10-20 PUBLIC 13/100
http://service.sap.com/support


14/100


SAP Notes for Preparing the Upgrade on IBM DB2 for Linux, UNIX and Windows

SAP Note Number Description Area

1403832 Central information about upgrading to SAPNetWeaver 7.3 Specific to this upgrade

1390477 Additional information about upgrading to SAP

NetWeaver 7.3

Specific to this upgrade

1468615 IBM DB2 for Linux, UNIX, and Windows Database-specific, specific to this upgrade



SAP Notes for Preparing the Upgrade on IBM DB2 for z/OS


1403832 Central information about upgrading to SAPNetWeaver 7.3



NetWeaver 7.3


1364670 IBM DB2 for z/OS Database-specific, specific to this upgrade


Only valid for: MaxDB |

SAP Notes for Preparing the Upgrade on SAP MaxDB


1403832 Central information about

upgrading to SAP NetWeaver 7.3


1390477 Additional information about

upgrading to SAP NetWeaver 7.3


End of: MaxDB |

Only valid for: Oracle |

SAP Notes for Preparing the Upgrade on Oracle


1403832 Central information about upgrading to SAPNetWeaver 7.3



NetWeaver 7.3


1487754 Oracle Database-specific, specific to this upgrade

End of: Oracle |

Other SAP Notes

As well as the SAP Notes you need for preparing the upgrade, this document also refers you to other

SAP Notes that contain additional information. The following lists contain these SAP Notes:

1 Introduction


14/100 PUBLIC 2011-10-20
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1468615&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1390477&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1403832&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1390477&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1403832&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1364670&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1390477&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1403832&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1468615&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1390477&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1403832&_NLANG=en&_NVERS=0


15/100

Database-Independent SAP Notes


928729 Combined Upgrade and Unicode

conversion

Upgrade and Unicode

1468605 Installation of ST-LV 100 on SAP

Solution Manager 7.0

Add-On

1494272 Web service function group missing

after upgrade

BW-specific

1156507 Information about language

supplementation after the upgrade

Language transport

805390 SAP Solution Manager is required

for all SAP applications

SAP Solution Manager

918370 Upgrade of Non-Standard SAP

Systems

General Upgrade

1017160 Upgrade of Systems with

Incompatible DB Modifications

General Upgrade

1154961 Checks to be executed before ESR/PI

Upgrade to 7.1

PI-specific

807615 Removing and archiving of non-

expired messages

PI-specific

746328 XI PCK (Partner Connectivity Kit)

installation and upgrade

PCK

1439558 Wizard-based automated processing

of PCK follow-up activities

PCK

1519075 Configuration wizard PI AdapterEngine

PI

1528990 SP equivalence for upgrades and

updates to SAP NetWeaver 7.3

SAP Support Packages

669669 Updating the SAP Component

Repository

System Landscape Directory

907897 Updating the SAP CIM Model System Landscape Directory

823941 SAP Start Service on UNIX

platforms

sapstartsrv

961747 Userhome folder support for special

characters

Enterprise Portal

1049553 SAP Forums Enterprise Portal Knowledge

Management and Collaboration

1372388 Upgrade of applications using KMC

to SAP NetWeaver 7.3

Enterprise Portal Knowledge


1371703 Web Page Composer Enterprise Portal Knowledge


1031096 Installation and upgrade of

SAPHOSTAGENT

SAPHOSTAGENT

1344564 Maintenance Optimizer: System

landscape

Maintenance Optimizer of SAP

Solution Manager

1 Introduction


2011-10-20 PUBLIC 15/100
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1344564&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1031096&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1371703&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1372388&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1049553&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=961747&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=823941&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=907897&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=669669&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1528990&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1519075&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1439558&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=746328&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=807615&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1154961&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1017160&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=918370&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=805390&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1156507&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1494272&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1468605&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=928729&_NLANG=en&_NVERS=0


16/100


1436297 Information about Maintenance

Optimizer 2.0 for the SAP BS7i2010e

Maintenance Optimizer of SAP

Solution Manager

1429764 Information about automatic

assignment of products in

transaction SMSY

SAP Solution Manager

Transaction SMSY


SAP Notes for IBM DB2 for Linux, UNIX and Windows


101809 DB6: Supported Fixpaks for DB2

UDB for Unix and Windows

DB2 for Linux, UNIX and Windows-

specific



SAP Notes for IBM DB2 for z/OS


81737 APAR list IBM DB2 for z/OS

183311 Automatic PTF Check IBM DB2 for z/OS



SAP Notes for SAP MaxDB

SAP Note Number Description Area498036 Overview note on importing SAP MaxDB / SAP DB versions SAP MaxDB-specific

201388 Change a database parameter in SAP DB Release SAP MaxDB-specific

201390 Back up the database SAP DB / SAP MaxDB SAP MaxDB-specific

352081 Additional functions relevant to services for SAP DB SAP MaxDB-specific

End of: MaxDB |


SAP Notes for Oracle


819829 Installation of the Oracle Client Software Oracle-specific

556764 Database parameters and performance Oracle-specific

11777 Changing parameters NEXT and MAXEXTENTS Oracle-specific

End of: Oracle |

1.3.4 Accessing Documentation

Before, during and after the upgrade, you require additional documentation:

SAP NetWeaver online documentation for the source release and the target release

1 Introduction


16/100 PUBLIC 2011-10-20
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=11777&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=11777&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=556764&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=819829&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=352081&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=201390&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=201388&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=498036&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=183311&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=81737&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=101809&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1429764%20&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1436297&_NLANG=en&_NVERS=0


17/100

Troubleshooting documentation

There are different ways to access the documentation:

SAP Library documentation

SAP NetWeaver Library on SAP Help Portal

You can access documentation for all maintained product releases on SAP Help Portal.

Local installation of the SAP NetWeaver Library

NOTE

The documentation for the target release is not available online in your system until you

have completed the upgrade and the installation procedure for the online

documentation.

Before the upgrade, you can make sure that you can read the DVD offline. After the upgrade,

you need to install the documentation for the target release. Troubleshooting documentation

The documentation is included in the upgrade program.

Procedure

SAP Help Portal

Target Release Documentation

You can find the SAP Library for SAP NetWeaver 7.3 on SAP Help Portal at http://help.sap.com/

SAP NetWeaver SAP NetWeaver SAP NetWeaver Knowledge Center SAP NetWeaver

Library .

Source Release Documentation

Only valid for: Source Release = SAP NetWeaver 7.0 EHP2 |

You can find the SAP Library for SAP NetWeaver 7.0 including enhancement package 2 on SAP Help

Portal at http://help.sap.com/ SAP NetWeaver SAP NetWeaver SAP NetWeaver

Knowledge Center SAP NetWeaver Library .

End of: Source Release = SAP NetWeaver 7.0 EHP2 |

Only valid for: Source Release = SAP NetWeaver 7.0 EHP1 |

You can find the SAP Library for SAP NetWeaver 7.0 including enhancement package 1 on SAP Help

Portal at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1)

SAP NetWeaver Library .

End of: Source Release = SAP NetWeaver 7.0 EHP1 |

Only valid for: Source Release = SAP NetWeaver 7.0 |

You can find the SAP Library for SAP NetWeaver 7.0 on SAP Help Portal at http://help.sap.com/

nw70 SAP NetWeaver 7.0 Library SAP NetWeaver Library .

End of: Source Release = SAP NetWeaver 7.0 |

1 Introduction


2011-10-20 PUBLIC 17/100
http://help.sap.com/nw70http://help.sap.com/http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/http://help.sap.com/


18/100

Only valid for: Source Release = SAP Web AS 6.40 |

You can find the SAP Library for SAP NetWeaver 2004 on SAP Help Portal at http://help.sap.com/

SAP NetWeaver SAP NetWeaver 2004 SAP NetWeaver 2004 Library SAP NetWeaver .

End of: Source Release = SAP Web AS 6.40 |

Local Installation of the SAP NetWeaver Library

Before and during the upgrade, you must read the online documentation for the target release on the

DVD.

RECOMMENDATION

If there is a Support Package available for the documentation, use the documentation version on

SAP Help Portal.

Troubleshooting DocumentationThe troubleshooting documentation is included in the upgrade program.

The upgrade tool unpacks the documentation at the beginning of roadmap step Extraction.

You can access the documentation as follows:

From a link on the upgrade GUI. Proceed as follows:

1. If it is not running yet, start the upgrade program.

2. On page http://:4239, chooseJava documentation.

3. Choose Troubleshooting for Systems Running on .

From file Troubleshooting_UNIX.pdf in UPG/java/htdoc

1 Introduction


18/100 PUBLIC 2011-10-20
http://%3Chost%20name%3E:4239/http://help.sap.com/


19/100

2 Quick Guide

This section contains a checklist with all the actions you need to perform:

Find SAP Notes

Plan the upgrade

Prepare the upgrade

Upgrade the SAP system

Perform the follow-up activities

The actions are in chronological order so that you can work through them like a checklist. For more

information, follow the links to the descriptions of the actions.

You can also use the checklist to get a quick overview of the upgrade process.

RECOMMENDATION

If you are experienced in performing upgrades, the checklist may contain all you need to know

to perform the upgrade successfully.

Checklist

SAP Notes for the Upgrade

This upgrade document is enhanced and updated by SAP Notes from SAP Support Portal (http://

service.sap.com/support). These SAP Notes are an important source of information when you plan

and prepare your upgrade, and also help you perform the actual upgrade.

1. You request the current SAP Notes for the Upgrade [page 13]. You require at least the following SAP

Notes:

Central Upgrade Note 1403832

SAP NetWeaver-specific SAP Note 1390477


The relevant database-specific SAP Note 1468615






The relevant database-specific SAP Note 1493434.

End of: MaxDB |



End of: Oracle |

2 Quick Guide

2011-10-20 PUBLIC 19/100
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1487754%20&_NLANG=en&_NVERS=0http://service.sap.com/supporthttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1487754%20&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1493434&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1364670%20&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1468615&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1390477&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1403832&_NLANG=en&_NVERS=0http://service.sap.com/supporthttp://service.sap.com/support


20/100

Additional Documentation

Before, during and after the upgrade, you require additional documentation such as SAP Library

documentation and troubleshooting documentation.

1. You make sure that you can access the SAP Library documentation [page 16] for your source releaseand target release.

The troubleshooting documentation is included in the upgrade program.

Upgrade Planning

Before you start the actual upgrade, you must plan it carefully so that downtime is reduced to a

minimum and the upgrade runs as efficiently as possible.

CAUTION

Start planning your upgrade at least two weeks before you want to begin with the upgrade

preparations.

1. You familiarize yourself with the features of the upgrade program (SAPup) [page 28] and its effect

on the way you upgrade the system with the upgrade GUI[page 28], the communication between back-

end processes and the GUI[page 30], and the upgrade directory [page 31].

2. You familiarize yourself with the technical details of the upgrade process [page 32].

3. You plan the upgrade ofnon-standard SAP systems [page 34].

4. You plan the upgrade ofNWDI-driven system landscapes [page 35].

5.You plan the upgrade ofdistributed and high-availability systems [page 36].

Upgrade Preparations

You can prepare for the upgrade while the system is in production operation. The upgrade program

supports you here by making most of the necessary checks automatically. Run the first four roadmap

steps of the upgrade as soon as possible before the actual upgrade so that you can initiate or perform

the necessary preparations in time.

Actions Before Starting the Upgrade Program

1. You choose the host[page 40] for the upgrade.

2. You check the hardware requirements: [page 41]

CPU, main memory, and swap space see SAP Service Marketplace at http://

service.sap.com/sizing

The minimum swap space is 20 GB.

UNIX parameters according to the Installation Guide SAP Software on UNIX: OS Dependencies

Disk space in the file system for the upgrade directory (standard path /usr/sap//

upg):


Space requirements in the database (estimation):

2 Quick Guide

20/100 PUBLIC 2011-10-20
http://service.sap.com/sizinghttp://service.sap.com/sizinghttp://service.sap.com/sizing


21/100

8 GB during the upgrade



Space requirements in the database:See SAP Note 943143.





End of: MaxDB |




End of: Oracle |

3. You check the software requirements.

Source release [page 42] of the SAP system:

If you upgrade to an SAP NetWeaver system containing more than one usage type, make

sure that your source system is on the highest minimum Support Package level for all usage

types implemented in the system. Different usage types have different minimum Support

Package levels.

Only valid for: Application Server (AS) |

SAP Web Application Server Java 6.40 SPS09

SAP NetWeaver 7.0 SPS 05 usage type AS Java

SAP NetWeaver 7.0 including enhancement package 1 usage type AS Java

SAP NetWeaver 7.0 including enhancement package 2 usage type AS Java

End of: Application Server (AS) |

Only valid for: Development Infrastructure (DI) |

SAP Development Infrastructure 6.40 SPS09

SAP NetWeaver 7.0 SPS 05 usage type Development Infrastructure

SAP NetWeaver 7.0 including enhancement package 1 usage type Development

Infrastructure

SAP NetWeaver 7.0 including enhancement package 2 usage type Development

Infrastructure

End of: Development Infrastructure (DI) |

Only valid for: Process Integration (PI) |

The following values for the source releases are minimum Support Package levels for SAP

NetWeaver Process Integration:

SAP Exchange Infrastructure 3.0 Support Package 09

SAP NetWeaver 7.0 SPS 05 usage type Process Integration

SAP NetWeaver 7.0 including enhancement package 1 usage type Process Integration

2 Quick Guide

2011-10-20 PUBLIC 21/100
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=943143&_NLANG=en&_NVERS=0


22/100

SAP NetWeaver 7.0 including enhancement package 2 usage type Process Integration

End of: Process Integration (PI) |

Only valid for: BI Java |

SAP BI 3.5 Java Components (Universal Data Integration / Meta Model Repository) SPS09

SAP NetWeaver 7.0 SPS 05 usage type BI Java

SAP NetWeaver 7.0 including enhancement package 1 usage type BI Java

SAP NetWeaver 7.0 including enhancement package 2 usage type BI Java

End of: BI Java |

Only valid for: Enterprise Portal (EP);EP Core (EPC) |

SAP Enterprise Portal 6.0_640 SPS 09

SAP NetWeaver 7.0 SPS 05 usage type Enterprise Portal

SAP NetWeaver 7.0 including enhancement package 1 usage type Enterprise Portal

SAP NetWeaver 7.0 including enhancement package 2 usage type Enterprise Portal

End of: Enterprise Portal (EP);EP Core (EPC) |

You plan or perform the upgrade of the operating system and database system [page 43] if necessary:

For more information about which operating system and database versions are currently

supported, see the Product Availability Matrix on SAP Service Marketplace at http://

service.sap.com/PAM.


Database version: At least Version 9.7 on 64 bit; migrate before you start the upgrade

program



If your database has been migrated from Version 7 or from Version 8 with a FixPak level

lower than 7 (Version lower than 8.2), then perform the actions described in SAP Note

823019 to avoid errors during the upgrade.



Database version: At least Version 9 (New Function mode); migrate before you start the

upgrade program



Database version: At least Version 7.8.01.14; migrate before you start the upgrade program

End of: MaxDB |


Database version: At least Version 11.2 for the upgrade; you can run up to roadmap step

Checks with Version 10.2.0.2 or higher

End of: Oracle |

You check the Software Delivery Manager version [page 48].

2 Quick Guide

22/100 PUBLIC 2011-10-20
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=823019&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=823019&_NLANG=en&_NVERS=0http://service.sap.com/PAMhttp://service.sap.com/PAM


23/100

4. You prepare the use ofSAP Solution Manager[page 49]:

You update your SAP Solution Manager to the latest Support Package stack.

Optional: You install the Landscape Verification 1.0 tool for SAP Solution Manager.

You configure the Maintenance Optimizer.

You maintain the system landscape data or check if it has already been maintained correctly.

5. You select and download software packages [page 53] that you want to include in the upgrade.

6. Only valid for: Enterprise Portal (EP);EP Core (EPC) |

You clean up the Universal Worklist cache [page 56].

End of: Enterprise Portal (EP);EP Core (EPC) |

7. You make the necessarypreparations for Enterprise Portal upgrade [page 56].

8. You make the necessarypreparations for KMC upgrade [page 57].

9. You make the necessary preparations for migrating the design time sources of your applications [page

58].

10. Only valid for: Process Integration (PI) |

You archive messages [page 55] in the PI Adapter Framework.



You resolve inconsistencies in the database [page 55].


12. You ensure that the correct kernel directory [page 56] is detected.

13. You make preparations in the monitoring area [page 58].

14. If you are running an upgrade of a distributed or high availability system, you make the necessary

preparations [page 58].

15. You update the SLD content[page 59] of your source system.

Upgrade Process

Actions for Starting and Using the Upgrade Program

1. You meet the requirements for the upgrade directory [page 64].

2. You start the upgrade from the Upgrade Master DVD [page 65] as user adm on the host with

the AS instance.

3. You start the upgrade GUI[page 66].You can restart the upgrade [page 67] or reset the upgrade [page 68]. You can also run the upgrade

program and the upgrade GUI in accessibility mode [page 69].

4. You decide on advanced GUI options [page 70].

5. If you need extra software after starting the upgrade, you import or install [page 72] it now.

Actions During the Configuration Roadmap Step

You continue with the roadmap step Configuration [page 72].

To perform the roadmap step, the upgrade program needs certain information from you so that it can

perform the upgrade. If possible, default values appear that you can confirm or change.

2 Quick Guide

2011-10-20 PUBLIC 23/100


24/100

1. You make the basic entries for the Java system upgrade [page 72].

2. You make entries for the target system configuration [page 74].

3. You provide theJCE policy files for Adobe Document Services [page 75]

Actions During the Checks Roadmap Step

You continue with the roadmap step Checks [page 76] and make entries if necessary. At the end of the

step, you perform the user actions requested on the SDTExecution Intervention screen.

Actions During the Preprocessing Roadmap Step

1. You check the central and the product-specific Upgrade Notes and your database-specific SAP

Note for new information and changes.

2. Before the downtime [page 76] begins, you make a backup of the database and the /usr/sap/

directory including the complete upgrade directory. You uninstall all additional

application server instances, stop Software Deployment Manager (SDM) GUI, stop jcmon andother standalone monitoring tools. You may also need to back up the home directory of user

adm.

Actions During the Execution Roadmap Step

While the processes of the Execution roadmap step are running, the system is in downtime.

1. Phase DOWNTIME_END_ [page 77]:

At the end of the downtime, you again create backups.

Actions During the Postprocessing Roadmap Step

1. Optional: You send the evaluation of the upgrade runtime [page 77] to SAP.

Follow-Up Activities

Actions Before Restarting Production Operation

1. You perform the follow-up activities for user root[page 80].


You run the wizard for automated processing of selected follow-up activities [page 81]:

You perform the follow-up activities for PCK.

You assign the PCK user roles.

You create a JCo destination for the ExchangeProfile.


3. Your perform the follow-up activities for the System Landscape Directory [page 83].

4. You configure SAP start service [page 84].

5. You perform follow-up activities in the monitoring area [page 86].

6. You check application Release Notes [page 87] for specific follow-up activities.

7. You performfollow-up activities [page 87] for SAP Solution Manager.

8. You change passwords [page 88], if necessary.

2 Quick Guide

24/100 PUBLIC 2011-10-20


25/100

9. Only valid for: Application Server (AS) |

You perform the follow-up activities for the Composite Application Framework Core (CAF Core) [page

89].


10. You perform the necessaryfollow-up activities for application migration [page 90].

11. You perform the necessaryfollow-up activities for NWDI[page 90].

12. Only valid for: Application Server (AS) |

You perform the follow-up activities for Adobe Document Services [page 90].


13. Only valid for: Development Infrastructure (DI) |

You check the CBS service properties [page 91].

End of: Development Infrastructure (DI) |

14. Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP XI 3.0 | Process Integration (PI) |

You adjust the adapter configuration [page 92].End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP XI 3.0 | Process Integration (PI) |

15. Only valid for: BI Java |

You performfollow-up activities for Business Intelligence [page 92].

End of: BI Java |

16. Only valid for: Enterprise Portal (EP) |

You check the KMC installation [page 93].

End of: Enterprise Portal (EP) |

17. Only valid for: Enterprise Portal (EP) |

You perform follow-up activities for Knowledge Management andCollaboration [page 95].

End of: Enterprise Portal (EP) |

Actions After Restarting Limited Production Operation

You can perform the following follow-up activities during limited production operation of the system.

1. You install the online documentation [page 97] for the target release.

2. You use SAPinst to install additional application server instances [page 97].

2 Quick Guide

2011-10-20 PUBLIC 25/100


26/100

This page is left blank for documentsthat are printed on both sides.


27/100

3 Planning

This part of the document contains information about planning your upgrade.

Before you begin the actual upgrade, you must first plan it carefully. This includes requesting all the

SAP Notes you need. Careful planning is a prerequisite for a successful SAP system upgrade.

The following information helps you plan your upgrade so that downtime is reduced to a minimum

and the upgrade runs as efficiently as possible.

NOTE

TeamSAP offers the free upgrade service SAP GoingLive Functional Upgrade Check. A team of

experts checks your system's parameter settings in one session before the upgrade, and gives you

detailed recommendations on the configuration. After the upgrade, the parameters and the entire

system status are checked again in a second session. For information about the service and about

ordering it, see SAP Support Portal at http://service.sap.com/goinglive-fu.

When you plan your upgrade, note the following information in addition to the information in Quick

Guide [page 19]:

All the times specified in this document are based on hardware with medium performance levels.

Do not perform any additional actions during the upgrade that could cause it to run less smoothly.

Start planning your upgrade at least two weeks before you start with the upgrade preparations.

To make sure that all requirements are met, run the preparation roadmap steps of the upgrade

program, Initialization, Extraction, Configuration, and Checks, as soon as possible. You can reset and repeat

the preparation roadmap steps as often as you need by choosing Back before you start the actual

upgrade in roadmap step Preprocessing. The successful execution of the preparation roadmap steps

is a prerequisite for starting the upgrade in roadmap step Preprocessing.

If it is technically possible, or unless otherwise specified, we recommend that you upgrade theoperating and database system and your SAP system at different times. Otherwise, the upgrade

project might become too complex and too error-prone.

Actions

The following sections are important for planning the upgrade:

Tool Information [page 28]

Upgrade GUI[page 28]

Upgrade Directory [page 31]

Technical Details of the Upgrade Process [page 32]

Planning the Upgrade of Non-Standard SAP Systems [page 34]

3 Planning

2011-10-20 PUBLIC 27/100
http://service.sap.com/goinglive-fu


28/100

Upgrade of NWDI-Driven System Landscapes [page 35]

Upgrade of Distributed and High-Availability Systems [page 36]

Back to Quick Guide [page 19]

3.1 Tool Information

The following sections provide you with important information about the upgrade program SAPJup:

Upgrade GUI[page 28]

Upgrade Directory [page 31]


3.1.1 Upgrade GUI

The upgrade GUI provides you with functions for monitoring the upgrade and navigating through

the roadmap steps of the upgrade. The upgrade consists of eight roadmap steps. These roadmap steps

contain modules, which in turn consist of the individual upgrade phases.

The upgrade phases are grouped into modules, which in turn are grouped into roadmap steps. The

upgrade consists of eight roadmap steps that run sequentially and are described briefly below.

NOTE

Roadmap steps 1 to 4 correspond to the previously used PREPARE program and are called the

preparation roadmap steps.

Features

Upgrade GUI

The upgrade GUI consists of the following main elements:

Menu bar

The menu bar offers you options that you need to work with the upgrade GUI and the upgrade

program. It has the following entries: File

Under File, you can find the Exitfunction.

User

Under User, you can find the following options:

Change Password Administrator

Using this option, you can change the password of your user with administration rights.

List Users

This option gives you an overview of all logged in users in the system.

Change Role

3 Planning


28/100 PUBLIC 2011-10-20


29/100

Using this option, you can change between the Administratoror as an Observeruser. Besides

the administrator, one or several observer user can log on to the GUI of the upgrade

program.

Failed Attempts

This option displays a list of all failed logons.

Upgrade

Under Upgrade, you can find the following options:

Stop Upgrade

The upgrade program stops immediately. When you restart the upgrade as described in

Restarting the Upgrade Program [page 67], the upgrade continues at the point where you

stopped it.

Reset UpgradeUsing this menu option, you can reset the upgrade as described in Resetting the Upgrade

[page 68].

Logs

From here, you have direct access to the upgrade logs.

Java EE

UnderJava EE, you can find the following options:

Start with options

Using this option, you can specify additional starting options for the upgrade program.

Set Breakpoint

Using this option, you can set a breakpoint that allows the upgrade program to stop before

a certain upgrade phase.

Remove Breakpoint

Using this option, you can remove the specified breakpoint.

Logs

From here, you can access the log files of the upgrade program.

Help

Under Help, you can find the following options:

Online Help

From here, you can access online help for the upgrade phases

SAP Notes

Using this option, you can start the SAP Notes Search on the SAP Support Portal.

About

Roadmap

The roadmap visualizes the roadmap steps. The roadmap step that is currently running is

highlighted.

Tab pages

3 Planning


2011-10-20 PUBLIC 29/100


30/100

You see the following tab pages:

Monitor

The monitor tab page displays a progress bar for the upgrade program. The progress bar shows

how much of a phase has already been carried out. It also shows which phase is currently

running and informs you about the status (RUNNING, COMPLETED, WAITING, ABORTED).

Java EE

Requests the input for the upgrade.

Back and Nextbuttons

To navigate between the roadmap steps, you choose Back or Next. If you want to go to the next

roadmap step, you choose Next. If you want to undo the roadmap step, you choose Back.

Figure 1: Roadmap Steps

If the upgrade program cannot verify the information you entered or one or more of the

prerequisites are not met, the resulting actions are displayed in one of the following ways:

If the upgrade program requires immediate action, it is displayed on the respective tab page.

Once you have performed this action, you can continue choosing Next.

All other required actions are displayed in the SDTExecution Intervention window. The messages

are sorted according to their importance. Once you have performed the action, you can

continue choosing Next.


3.1.2 Communication Between Back-End Processes and GUI

When you start the upgrade program on the central instance, the Software Logistics (SL) Controller

starts. The SL Controller manages the SAPup processes and provides ports to establish the

communication with the front end. The following port numbers are used:

Port 4240: Connection between SL Controller and SAPup processes

Port 4239: Connection between SL Controller and the Internet browser on the remote host

3 Planning


30/100 PUBLIC 2011-10-20


31/100

Port 4241: Connection between the SL Controller and the upgrade GUI on the remote host

The following figure shows the interactions between SAPup, the SL Controller, and the front end.

Figure 2: Communication Between SAPup, the SL Controller, and the Front End


3.1.3 Upgrade Directory

The SAP system is upgraded using the upgrade directory, which is divided into subdirectories.

Both the upgrade directory and the subdirectories can be soft links to other physical directories.

The upgrade program creates the upgrade directory on the host with the primary application server

instance and copies data and programs into this directory.

The default path of the upgrade directory is:

/usr/sap//upgThe upgrade directory is divided into the following subdirectories:

sdt

Contains the SL controller.

jvm

Depending on your operating system and database, this directory contains the Java Virtual Machine

delivered by SAP.

STARTUP

Contains the startup files with which you can restart the upgrade program.

java

3 Planning


2011-10-20 PUBLIC 31/100


32/100

config

Contains configuration xml files for the upgrade.

data

This directory contains several subdirectories, which contain amongst others the new software

versions that are deployed during the upgrade, the SAP kernel and SAP JVM for the shadow

system. Do not change files in the variables subdirectory since this can lead to an upgrade

failure.

dtd

This directory contains DTD files with definitions required by the upgrade program to read

xml files.

This directory is created during the Preprocessing roadmap step and contains the shadow system.

lib

Contains the JAR files ofSAPJup.

log

Contains log files written during the upgrade.

migtool

Contains migration controllers after they have been extracted by SAPJup from a data

subdirectory.

param

Contains the phaselist.xml file, which contains the upgrade phase descriptions. In thelogging.properties file, which is also contained in the param directory, you can increase the

logging and tracing level.

tmp

Contains temporary files created from external processes running during the upgrade.

trc

Contains trace files created by SAPJup.

platform

Contains the SAP kernel files for your additional application server instances, if they run on

a different platform than the primary application server instance.


3.2 Technical Details of the Upgrade Process

The following figure shows the process flow of the upgrade with the major steps of the process.

To upgrade a Java system, the upgrade program uses a switch-based procedure. This procedure installs

an instance of the target release, the shadow system, in parallel with the current source release system

3 Planning


32/100 PUBLIC 2011-10-20


33/100

in the same database. The parallel system contains all the software of the target release and is used to

perform actions on the target release while the source release is still in production operation.

The complete upgrade process is divided into eight roadmap steps. In these roadmap steps, the following

actions take place:

1 - Initialization

The upgrade program analyzes whether your SAP system is an ABAP + Java system or an ABAP or

Java standalone system. The upgrade GUI is assembled according to the result. You always see the

Monitortab page and either the ABAPorJava EEtab page, or both.

2 - Extraction

The upgrade program extracts the required software.

3 - Configuration

In the Configuration roadmap step, you enter all the information required for the upgrade process

such as passwords, information about software units and Support Packages that you want to

include, and information about the shadow system.

4 - Checks

The upgrade program checks if the operating system and database version of your source release

match the requirements of the target release. It also checks some application-specific requirements.

5 - Preprocessing

The upgrade program imports the substitution tables and performs the online deployment.

When the Preprocessing roadmap step is finished and you choose Next, the downtime starts.

6 - Execution

The Execution roadmap step runs without any user interaction. While the processes of the

Execution roadmap step are running the system is in downtime. The switch to the new system takes

place in this roadmap step. The upgrade program converts application tables and data to match

the target release layout. In addition, it switches the SAP kernel.

7 - Postprocessing

The upgrade program creates the upgrade evaluation, saves the log files, and prompts you to start

with certain follow-up activities.

The upgrade program also deletes the shadow schema and some obsolete AS Java directories.

8 - Finalization

The upgrade program enables you to clean up tables that are no longer required and completes

the upgrade.


3 Planning


2011-10-20 PUBLIC 33/100


34/100

3.3 Planning the Upgrade of Non-Standard SAP Systems

The following section provides an overview of how you can upgrade SAP systems that you have

enhanced with custom developments or third-party software or SAP systems where you have modified

SAP software.

Depending on the type of enhancement or modification, several cases can be distinguished, which are

outlined below.

Process

You have modified SAP software or created your own software components using the SAP

NetWeaver Development Infrastructure (NWDI).

For information about the upgrade of systems that are configured as runtime systems of the NWDI

and the modification adjustment, see Upgrade of NWDI-Driven System Landscapes [page 35].

You have modified SAP software without using the NWDI.

If you have modified Software Components (SC) and also modified the name of the component

vendor, the upgrade program detects that these are modified components. In the Configuration

roadmap step of the upgrade, the operation Scan inboxis assigned to these components. This enables

you to provide adjusted SCAs that are then deployed during the upgrade. Proceed as follows:

1. Compare your modified software components with the new SAP versions of the software

components.

2. Redo the modifications where necessary and create your own SCAs.

3. Copy the SCAs to the Electronic Parcel Service (EPS) of your transport directory.4. In the Configuration roadmap step, specify that the upgrade program deploys these SCAs.

CAUTION

If you have modified Software Components without modifying the name of the

component vendor, then the upgrade program is not able to detect that you have modified

the component. In the Configuration roadmap step, the operation Scan inboxis not offered for

these components. You lose your modifications if you proceed.

For information about how you can upgrade these components, see SAP Note 918370.

You have installed third-party components in your system or you have installed custom

developments that have been developed without using the NWDI.

In the Configuration roadmap step, the upgrade program assigns the operation Scan inboxto these

components.

You have to provide new versions of these components, that is, versions that are valid for the target

release. You put them into the EPS inbox and specify that the upgrade program deploys these new

versions.


3 Planning

3.3 Planning the Upgrade of Non-Standard SAP Systems

34/100 PUBLIC 2011-10-20
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=918370&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=918370&_NLANG=en&_NVERS=0


35/100

3.4 Upgrade of NWDI-Driven System Landscapes

If you want to upgrade a system that is part of a system landscape controlled by SAP NetWeaver

Development Infrastructure (NWDI), you have to consider some special properties. The NWDI has

special knowledge about the software component archives (SCAs), for example, about the storage of

design time objects in the Design Time Repository or about the upgrade sequence of software

applications in a system landscape.

The maintenance process for NWDI-driven system landscapes is described in the current online

documentation available on SAP Help Portal at http://help.sap.com SAP NetWeaver 7.0 SAP

NetWeaver 7.0 Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key

Capability Software Life Cycle Management Software Logistics SAP NetWeaver Development Infrastructure

Development Scenarios with the NWDI Maintenance of NWDI-Driven System Landscapes .

Below, a brief overview of the steps from an upgrade perspective is given.The upgrade process for development and consolidation systems differs from the upgrade of quality

assurance and production systems. In the development and consolidation system you can adjust the

new SAP component versions to your modifications and build software component archives (SCAs).

The adjusted SCAs are then deployed during the upgrade of the quality assurance and production

system.

CAUTION

You can only upgrade a quality assurance or production system if you provide adjusted SCAs for

all components that you modified in the source release.

Prerequisites

The NWDI system (the central system that controls the runtime systems) has at least SAP

NetWeaver 7.0 Support Package Stack level 05.

The runtime systems have at least SAP NetWeaver 7.0 Support Package Stack level 05.

You have performed the preparation steps as described in the SAP NetWeaver Library

documentation under Maintenance of an NWDI-Driven System Landscape.

Process1. During the Configuration roadmap step, you specify whether the system that you are upgrading is

configured as a runtime system in an NWDI track. If yes, you specify whether the system is a

development system (DEV), consolidation system (CONS), quality assurance system (QA), or

production system (PROD).

2. Upgrade of development and consolidation system

1. After you have entered the path to the NWDI transport directory, the upgrade program copies

all SAP components included in the shipment to this directory.

2. The components that you have modified as well as the non-modified components are replaced

by new SAP component versions. However, if you have made incompatible database

3 Planning

3.4 Upgrade of NWDI-Driven System Landscapes

2011-10-20 PUBLIC 35/100
http://help.sap.com/


36/100

modifications, the upgrade program is not able to deploy the new components. For

information about upgrading such systems, see SAP Note 1017160.

3. After the upgrade, you take the components from the NWDI transport directory and perform

the modification adjustment by using the NWDI. You then deploy the adjusted software

components (SCs) to the upgraded development or consolidation system.

4. In the consolidation system, you assemble the modified SCs as software component archives

(SCAs).

3. Upgrade of quality assurance and production system

During the upgrade of quality assurance and production systems, the upgrade program deploys

the modified components that you have built in the consolidation system. In the Configuration

roadmap step, all modified components have the status Scan inboxon the selection screen for the

target release components.You select the new versions from the inbox and rebuild the component list. The modified

components are then included in the deployment.


3.5 Upgrade of Distributed and High Availability Systems

The upgrade program can handle distributed configurations where your SCS instance is installed on

a separate host (for example, in a high availability environment).For information about upgrading a high availability system, contact your HA solution implementation

partner.

Process

The upgrade process for a high availability system is as follows:

1. You prepare the disabling of the cluster failover capabilities and, if necessary, change your

configuration and clean up profiles (see Preparing the Upgrade of Distributed and High Availability Systems

[page 58]).

2. The upgrade program checks the profile directory and, if the SCS instance is installed on a remotehost, assumes that the upgrade is running in a distributed or high availability environment.

3. Uninstall all additional application server instances at the end of the end of the preprocessing

roadmap step.

4. At the beginning of the downtime, you stop the primary application server instance and stop the

remote SCS instance as described in Phase BEGIN_DOWNTIME_ [page 76].

5. If prompted, install a temporary license key in the shadow system and in the system during

downtime. For information about license keys, see http://service.sap.com/licensekey.

6. During the downtime, the upgrade program reuses the SCS instance of the shadow system on the

host with the primary application server instance.

3 Planning


36/100 PUBLIC 2011-10-20
http://service.sap.com/licensekeyhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1017160&_NLANG=en&_NVERS=0


37/100

7. At the end of the downtime, you start the ERS of the SCS instance, start the SCS instance, and

then the primary application server instance manually.


3 Planning


2011-10-20 PUBLIC 37/100


38/100

This page is left blank for documentsthat are printed on both sides.


39/100

4 Preparation

This part of the document contains information about the preparations that you need to make before

you upgrade your system.

You can prepare for the upgrade while the system is in production operation. Careful preparation of

the upgrade is the best guarantee that it runs without errors.

The upgrade program supports you here by making most of the necessary checks automatically. For

more information about the checks performed by the upgrade program, see the descriptions of roadmap

steps Extraction, Configuration, Checks, and Preprocessing in Upgrade Process [page 63].

Actions

You perform the following actions before you start the upgrade program:

Determining the Host for the Preparations [page 40]

Checking the Hardware Requirements [page 41]

Checking the Software Requirements [page 42]

Checking the Source Release of the SAP System [page 42]

Meeting the Operating System-Specific Requirements [page 43]

Upgrading the Operating System and Database System: Overview [page 43] Checking the Software Delivery Manager Version [page 48]

Preparing SAP Solution Manager[page 49]

SAP Solution Manager Update [page 49]

Installation of Landscape Verification 1.0 for SAP Solution Manager [page 50]

Configuration of the Maintenance Optimizer[page 50]

Maintaining System Landscape Information [page 50]

Selecting and Downloading Software Packages

Ug Nw73 Java+Unix+Oracle

Documents

Transcript of Ug Nw73 Java+Unix+Oracle