Ug Nw73 Java+Unix+Oracle

Upgrade Guide SAP NetWeaver 7.
3 Java
For: Java UNIX IBM DB2 for z/OS IBM DB2 for Linux, UNIX, and Windows SAP MaxDB Oracle Target Audience 4; System administrators 4; Technology consultants
PUBLIC 4b?k1"? `"veu0] %LQ|(tlJ;XO|3gBc|
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.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 Marketplace
You can find this document at the following address: http://service.sap.com/instguides
2/100
PUBLIC
2011-10-20
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
Typographic Conventions
Example
<Example>
Description
Example Example Example

Example
Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 | 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 | 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, and names of installation, upgrade, and database tools 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 Keys on the keyboard
http://www.sap.com /example
123456 Example
Example
EXAMPLE
EXAMPLE
4/100
PUBLIC
2011-10-20
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 Description
1.0 1.1 1.2
2010-11-29 2011-08-12 2011-10-20
First version no changes Revised version 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
Table of Contents
Chapter 1 1.1 1.2 1.3 1.3.1 1.3.2 1.3.3 1.3.4 Chapter 2 Chapter 3 3.1 3.1.1 3.1.2 3.1.3 3.2 3.3 3.4 3.5 Chapter 4 4.1 4.2 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.4 4.4.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Quick Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Accessing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Quick Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tool Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication Between Back-End Processes and GUI . . . . . . . . . . . . . . . . . . Upgrade Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Details of the Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning the Upgrade of Non-Standard SAP Systems . . . . . . . . . . . . . . . . . . . Upgrade of NWDI-Driven System Landscapes . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade of Distributed and High Availability Systems . . . . . . . . . . . . . . . . . . . Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the Host for the Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Source Release of the SAP System . . . . . . . . . . . . . . . . . . . . . . . Meeting the Operating System-Specific Requirements . . . . . . . . . . . . . . . . . . Upgrade of the Operating System and Database System: Overview . . . . . . . . . Checking the Software Delivery Manager Version . . . . . . . . . . . . . . . . . . . . . . Preparing SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Solution Manager Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 28 28 30 31 32 34 35 36 39 40 41 42 42 43 43 48 49 49
6/100
PUBLIC
2011-10-20
4.4.2 4.4.3 4.4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 Chapter 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.9.1 5.9.2 5.9.3 5.10 5.11 5.12 5.13
Installation of Landscape Verification 1.0 for SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of the Maintenance Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . Maintaining System Landscape Information . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting and Downloading Software Packages . . . . . . . . . . . . . . . . . . . . . . . . PI: Archiving Messages in the PI Adapter Framework . . . . . . . . . . . . . . . . . . . . PI: Resolving Inconsistencies in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . Ensuring the Correct Kernel Directory Detection . . . . . . . . . . . . . . . . . . . . . . EPC: Cleaning Up the Universal Worklist Cache . . . . . . . . . . . . . . . . . . . . . . . EP: Preparations for Enterprise Portal Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . EP: Preparations for Knowledge Management and Collaboration (KMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparations for Application Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Preparations in the Monitoring Area . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Upgrade of Distributed and High Availability Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating SLD Content of the Source System . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Meeting the Requirements for the Upgrade Directory . . . . . . . . . . . . . . . . . . . Starting the Upgrade Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Upgrade GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting the Upgrade Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced GUI Options: Role Management and Alert Function . . . . . . . . . . . Importing or Installing Software After Starting the Upgrade . . . . . . . . . . . . . . Making Entries for the Configuration Roadmap Step . . . . . . . . . . . . . . . . . . . Making Basic Entries for the Java System Upgrade . . . . . . . . . . . . . . . . . . . . . . Making Entries for the Target System Configuration . . . . . . . . . . . . . . . . . . . . Providing the JCE Jurisdiction Policy Files for Adobe Document Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Entries for the Checks Roadmap Step . . . . . . . . . . . . . . . . . . . . . . . . . Phase BEGIN_DOWNTIME_<XX> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phase DOWNTIME_END_<XX> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Evaluating the Upgrade Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
50 50 50 53 55 55 56 56 56 57 58 58 58 59 63 64 65 66 67 68 69 70 72 72 72 74 75 76 76 77 77
2011-10-20
PUBLIC
7/100
Chapter 6 6.1 6.2 6.2.1 6.2.2 6.2.3 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14 6.15 6.16 6.17 6.18 6.19 6.20 6.21 Chapter A A.1
Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Follow-Up Activities for User root . . . . . . . . . . . . . . . . . . . . . . . . . PCK: Using a Wizard for Automated Processing of Selected Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCK: Performing Follow-Up Activities for PCK . . . . . . . . . . . . . . . . . . . . . . . . PI: Assigning PCK User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI-AF: Creating a JCo Destination for the ExchangeProfile . . . . . . . . . . . . . . . . Performing Follow-Up Activities for the System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring SAP Start Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Migrating Java Proxy-Based Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP MaxDB: Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Follow-Up Activities in the Monitoring Area . . . . . . . . . . . . . . . . Performing Application-Specific Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Follow-Up Activities for SAP Solution Manager . . . . . . . . . . . . . . Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Follow-Up Activities for the Composite Application Framework Core (CAF Core) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Follow-up Activities for Application Migration . . . . . . . . . . . . . . . Performing Follow-up Activities for NetWeaver Development Infrastructure (NWDI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Follow-Up Activities for Adobe Document Services . . . . . . . . . . . DI: Checking the CBS Service Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PI: Adjusting the Adapter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BI Java: Performing Follow-Up Activities for Business Warehouse . . . . . . . . . . EP: Checking the KMC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EP: Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Additional Application Server Instances . . . . . . . . . . . . . . . . . . . . . .
79 80 81 82 82 83 83 84 84 85 86 87 87 88 89 90 90 90 91 92 92 93 95 97 97
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 List of Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8/100
PUBLIC
2011-10-20
1 1.1
Introduction Quick Access
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: l For source release SAP NetWeaver 7.0 including enhancement package 1 and lower, you require this document. l 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.0 available at http://service.sap.com/upgradenw73.
NOTE
To find the latest version of this document and the Upgrade 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
2011-10-20
PUBLIC
9/100
1 1.2
Introduction About This Document
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: F Chapter 1 Introduction This 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. F 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. F 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, <SAP component>: <Title>. 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. F Chapter A Appendix This chapter contains a list of the documentation referenced in this guide.
10/100
PUBLIC
2011-10-20
1 1.3
Introduction Before You Start
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 <sapsid> is used, your SAP system ID must be in lowercase letters, for example prd. If <SAPSID> is used, you must write in uppercase letters, for example PRD.
ID for the SAP System Release
In this document, <rel> stands for the relevant SAP system release, without a decimal point, such as 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
X 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. X 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: X Application server instances Application server instances can be installed as primary application server instance or additional application server instances. X Central services instance X Database instance
Instance Name
In this document, <instance_name> is used as a placeholder for the instance name in the instance directory path of your system.
2011-10-20
PUBLIC
11/100
1 1.3
Substitute <instance_name> with J<xx> for the primary or additional application server instance, where <xx> stands for the instance number.
/Q` ZQ?]*M{#V:g.d*&H"*uk{2
4 o) kuh WzSlQ%MndMf
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.
/Q` .Z<YU*>M{#V:yad9hHk*NZ2O
> +) rCh NzG /Q` ZQ?]*M{#V:g.d*&Hd*S'
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.
/Q` .Z<YU*>M{#V9:=
1.3.2 New Features

New Features in the Upgrade Feature Description Availability
Upgrade procedure and handling
Troubleshooting and administration documentation included in the upgrade program
Start profile
SAP kernel file structure
The upgrade procedure and handling have changed significantly. Amongst others, the changes are: /kt_ New user interface (upgrade GUI) /kt_ Upgrade phases are grouped into roadmap steps. The troubleshooting and administration 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 from the HTML start page. 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. As of this release, the SAP kernel file structure was changed. The SAP kernel is
As of SAP NetWeaver PI 7.1
12/100
PUBLIC
2011-10-20
1 1.3 Feature
Introduction Before You Start Description Availability
Configuration of sapcpe
Upgrade of additional application server instances
now located in directory /usr/sap/ <SAPSID>/SYS/exe/uc/<platform>. If you have not already done so, sapcpe is As of SAP NetWeaver PI 7.1 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. The procedure for the upgrade of additional As of SAP NetWeaver PI 7.1 application server instances was changed. Phase DETERMINE_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 relevant SAP kernel files to the subdirectory <platform> 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 Note Contains 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:
2011-10-20
PUBLIC
13/100
1 1.3
n,)-TOO `RnwbeO`l B^X gyxqo?%X(wx841f^dtJYL
SAP Notes for Preparing the Upgrade on IBM DB2 for Linux, UNIX and Windows SAP Note Number Description Area
1403832 1390477 1468615
Central information about upgrading to SAP Specific to this upgrade NetWeaver 7.3 Additional information about upgrading to SAP Specific to this upgrade NetWeaver 7.3 IBM DB2 for Linux, UNIX, and Windows Database-specific, specific to this upgrade
d,)-T_ `tcDnwjeb_lw1 ^X \Vvrq&X(Zyx8# n,)-TOO `RnwbeO`l B^X F+
SAP Notes for Preparing the Upgrade on IBM DB2 for z/OS SAP Note Number Description Area
1403832 1390477 1364670
Central information about upgrading to SAP Specific to this upgrade NetWeaver 7.3 Additional information about upgrading to SAP Specific to this upgrade NetWeaver 7.3 IBM DB2 for z/OS Database-specific, specific to this upgrade
d,)-T_ `tcDnwjeb_lAw 1^C n,)-TOO `RnwbelUly
SAP Notes for Preparing the Upgrade on SAP MaxDB SAP Note Number Description Area
1403832 1390477
Central information about upgrading to SAP NetWeaver 7.3 Additional information about upgrading to SAP NetWeaver 7.3
Specific to this upgrade Specific to this upgrade
d,)-T_ `WV n5w$ n,)-TOO `RnwbeLlW=
SAP Notes for Preparing the Upgrade on Oracle SAP Note Number Description Area
1403832 1390477 1487754

d,)-T_ `DOnw
Central information about upgrading to SAP Specific to this upgrade NetWeaver 7.3 Additional information about upgrading to SAP Specific to this upgrade NetWeaver 7.3 Oracle Database-specific, specific to this upgrade
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:
14/100
PUBLIC
2011-10-20
1 1.3
Database-Independent SAP Notes SAP Note Number Description Area
928729 1468605 1494272 1156507 805390 918370 1017160 1154961 807615 746328 1439558 1519075 1528990 669669 907897 823941 961747 1049553 1372388 1371703 1031096 1344564
Combined Upgrade and Unicode conversion Installation of ST-LV 100 on SAP Solution Manager 7.0 Web service function group missing after upgrade Information about language supplementation after the upgrade SAP Solution Manager is required for all SAP applications Upgrade of Non-Standard SAP Systems Upgrade of Systems with Incompatible DB Modifications Checks to be executed before ESR/PI Upgrade to 7.1 Removing and archiving of nonexpired messages XI PCK (Partner Connectivity Kit) installation and upgrade Wizard-based automated processing of PCK follow-up activities Configuration wizard PI Adapter Engine SP equivalence for upgrades and updates to SAP NetWeaver 7.3 Updating the SAP Component Repository Updating the SAP CIM Model SAP Start Service on UNIX platforms Userhome folder support for special characters SAP Forums
Upgrade and Unicode Add-On BW-specific Language transport SAP Solution Manager General Upgrade General Upgrade PI-specific PI-specific PCK PCK PI SAP Support Packages System Landscape Directory System Landscape Directory
sapstartsrv
Enterprise Portal
Enterprise Portal Knowledge Management and Collaboration Upgrade of applications using KMC Enterprise Portal Knowledge to SAP NetWeaver 7.3 Management and Collaboration Web Page Composer Enterprise Portal Knowledge Management and Collaboration Installation and upgrade of SAPHOSTAGENT SAPHOSTAGENT Maintenance Optimizer: System Maintenance Optimizer of SAP landscape Solution Manager
2011-10-20
PUBLIC
15/100
1 1.3
Introduction Before You Start Description Area
SAP Note Number
1436297 1429764
Information about Maintenance Optimizer 2.0 for the SAP BS7i2010e Information about automatic assignment of products in transaction SMSY
Maintenance Optimizer of SAP Solution Manager SAP Solution Manager Transaction SMSY
f~9$U>>3-k)
hL0lY?b"WL<uQdvCKEeFyB`3
SAP Notes for IBM DB2 for Linux, UNIX and Windows SAP Note Number Description Area
101809
DB6: Supported Fixpaks for DB2 UDB for Unix and Windows
DB2 for Linux, UNIX and Windowsspecific
f~)s>>3-k))
740#Jqb7k0lL<4[vC}GK|Fy f~9$U>>3-k)
hL0lY?b)d*qTL
SAP Notes for IBM DB2 for z/OS SAP Note Number Description Area
81737 183311
f~)s>>3-k))#
q?0 f~9$U>>3-k#M
&
APAR list Automatic PTF Check
IBM DB2 for z/OS IBM DB2 for z/OS
SAP Notes for SAP MaxDB SAP Note Number Description Area
498036 201388 201390 352081

f~)P>"> f~9$U>>3-k:j5
;
Overview note on importing SAP MaxDB / SAP DB versions Change a database parameter in SAP DB Release Back up the database SAP DB / SAP MaxDB Additional functions relevant to services for SAP DB
SAP MaxDB-specific SAP MaxDB-specific SAP MaxDB-specific SAP MaxDB-specific
SAP Notes for Oracle SAP Note Number Description Area
819829 556764 11777

f~)C>>|3q
Installation of the Oracle Client Software Database parameters and performance Changing parameters NEXT and MAXEXTENTS
Oracle-specific Oracle-specific Oracle-specific
1.3.4 Accessing Documentation

Before, during and after the upgrade, you require additional documentation: fm; SAP NetWeaver online documentation for the source release and the target release
16/100
PUBLIC
2011-10-20
1 1.3
B Troubleshooting documentation There are different ways to access the documentation: B 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. B 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 <Release> SAP NetWeaver <Release> Knowledge Center SAP NetWeaver <Release> Library <Language> .
Source Release Documentation
ouki4|d=ktSQ(&!ûa9b6oq; F pT<kq(\o6\R,
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 <Release> SAP NetWeaver <Release> Knowledge Center SAP NetWeaver <Release> Library <Language> .
o,$yx|^=>tS]Z&!^0QuJ9b6I4;eYpT. ouki4|d=ktSQ(&!ûa9b6oq; F pT<kq(\o6_R,
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) <Language> SAP NetWeaver Library .
o,$yx|^=>tS]Z&!^0QuJ9b6I4;eYpT- ouki4|d=ktSQ(&!ûa9b6oq; F pT<kq
You can find the SAP Library for SAP NetWeaver 7.0 on SAP Help Portal at nw70 SAP NetWeaver 7.0 Library <Language> SAP NetWeaver Library .
o,$yx|^=>tS]Z&!^0QuJ9b6I4;eY(
http://help.sap.com/
2011-10-20
PUBLIC
17/100
1 1.3
{mG-,^5?JyS*k(<YX2@O5%?W(OMw@
{)_8Sm;J+\z4{
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 <Language> SAP NetWeaver .
{mGt<^yAy^S>kZ<YX!@Op%W7(DMwR
i)|&iS?J
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 Documentation
The 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: {;H 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://<host name>:4239, choose Java documentation. 3. Choose Troubleshooting for Systems Running on <platform>. {;H From file Troubleshooting_UNIX.pdf in UPG/java/htdoc
18/100
PUBLIC
2011-10-20
Quick Guide
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 (% (% (% (%
'G=>bVT1t6LUW3m"?_jYQgT)!#NW(5;064A11X\%mVNK
The relevant database-specific SAP Note 1468615

'D=.9VS)d1|6L)Uz3m"*c_jG[gT!,D]5;0/4A 'G=>bVT1t6LUW3m"?_jYQTgT

'D=.9VS)d1|6L)Uz3m"lB_jB 'G=>bVT1t6LUt3 "q
The relevant database-specific SAP Note 1493434.

'D=.9V7/12 'G=>bVT1t6LUg3."&_

'D=.9VC16
2011-10-20
PUBLIC
19/100
Quick Guide
Additional Documentation
Before, during and after the upgrade, you require additional documentation such as SAP Library documentation and troubleshooting documentation. -c~1. You make sure that you can access the SAP Library documentation [page 16] for your source release and 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. -c~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 backend processes and the GUI [page 30], and the upgrade directory [page 31]. -c~2. You familiarize yourself with the technical details of the upgrade process [page 32]. -c~3. You plan the upgrade of non-standard SAP systems [page 34]. -c~4. You plan the upgrade of NWDI-driven system landscapes [page 35]. -c~5. You plan the upgrade of distributed 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 -c~1. You choose the host [page 40] for the upgrade. -c~2. You check the hardware requirements: [page 41] -cXH CPU, main memory, and swap space see SAP Service Marketplace at http://
service.sap.com/sizing
The minimum swap space is 20 GB. -cXH UNIX parameters according to the Installation Guide SAP Software on UNIX: OS Dependencies -cXH Disk space in the file system for the upgrade directory (standard path /usr/sap/<SAPSID>/ upg): -cXH
-cX_kD[ta*P.qp\~}$NE;g(5mH<9L\.l<lU=xg_L1.f
Space requirements in the database (estimation):
20/100
PUBLIC
2011-10-20
Quick Guide
8 GB during the upgrade

.4A&nd|.i(\E<j;uQ1Kn<~M'R1jysgJ27
"=
$X{EA%n |hY \jj;')1n!M
Space requirements in the database: See SAP Note 943143.

.4A&nd|.i(\E<j;JTw=1 $X{EA%n |hY \n2j;g
"=
Space requirements in the database (estimation): 15 GB during the upgrade

.4A" nQ|Jf $X{EA%n |hY \l!j;X
"=
Space requirements in the database (estimation): 8 GB during the upgrade

.4A 3nH|mNX
{=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.
$X{EA%n |hY \b#j;zP1nRM'e1fjl
"R "R "R "R
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
.4A.1nY|bH{P\J<j;iR1nK $X{EA%n |hY \g6j;

kI1nVMX'U1jb7 y)`2g
"R SAP Development Infrastructure 6.40 SPS09 "R SAP NetWeaver 7.0 SPS 05 usage type Development Infrastructure "R SAP NetWeaver 7.0 including enhancement package 1 usage type Development Infrastructure "R SAP NetWeaver 7.0 including enhancement package 2 usage type Development Infrastructure
.4A+$n_|kDjI\F=j;}V1nEM'1fjl $X{EA%n |hY \s!j;h1n^MB'f1j
The following values for the source releases are minimum Support Package levels for SAP NetWeaver Process Integration: "R SAP Exchange Infrastructure 3.0 Support Package 09 "R SAP NetWeaver 7.0 SPS 05 usage type Process Integration "R SAP NetWeaver 7.0 including enhancement package 1 usage type Process Integration
2011-10-20
PUBLIC
21/100
Quick Guide
t) SAP NetWeaver 7.0 including enhancement package 2 usage type Process Integration
t#tx,_bU7P%.s^Vu jmSjPR\DP t#|xcOb-U7P%gxyV!&jkWjP
t) SAP BI 3.5 Java Components (Universal Data Integration / Meta Model Repository) SPS 09 t) SAP NetWeaver 7.0 SPS 05 usage type BI Java t) SAP NetWeaver 7.0 including enhancement package 1 usage type BI Java t) SAP NetWeaver 7.0 including enhancement package 2 usage type BI Java
t#tx,_bU7P%<:F t#|xcOb-U7P%g^Vu jxQjCRaDPoAT5K[s=+!JJM4+l ,~E
t) t) t) t)
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
t#tx,_bU7P%/IUV!<jeSjER.DPSATK[s=F4J:M4+Vl
t) 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.
t#|xcOb-U7P%gsrVLLjNcjR{DP{ATK[sk= 8J2MW+l S@GJ{:)
Database version: At least Version 9.7 on 64 bit; migrate before you start the upgrade program
t#tx,_b U7P%o\_VsLjFHj_R@DPJ9TK[s=9JM+lx t#|xcOb-U7P%gsrVLLjNcjR{DP{ATK[sk= 8J2MW+l S@GJ{:)
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.
t#tx,_b U7P%o\_VsLjFHj_R@DPJ9TK[s=9JM+lx t#|xcOb-U7P%gsrVLLjNcjRZDP
Database version: At least Version 9 (New Function mode); migrate before you start the upgrade program
t#tx,_b U7P%o\_VsLjpj~Z t#|xcOb-U7P%gwQVy(jHjM
Database version: At least Version 7.8.01.14; migrate before you start the upgrade program
t#tx,_b U7Pp%! t#|xcOb-U7P%guBV`jfDj
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
t#tx,_bU7P%
t) You check the Software Delivery Manager version [page 48].
22/100
PUBLIC
2011-10-20
Quick Guide
Jf4. You prepare the use of SAP Solution Manager [page 49]: l^C You update your SAP Solution Manager to the latest Support Package stack. l^C Optional: You install the Landscape Verification 1.0 tool for SAP Solution Manager. l^C You configure the Maintenance Optimizer. l^C You maintain the system landscape data or check if it has already been maintained correctly. Jf5. You select and download software packages [page 53] that you want to include in the upgrade. Jf6.
lf`gi
.m';9[ 8-+&W+;qizqYjekeKkc6-d6R,X`êvFqPc\$L5
You clean up the Universal Worklist cache [page 56].

lfò0E.mY'J;Q l.+;W)Orq\zljpkZKO_]-dzI\X`ê
Jf7. You make the necessary preparations for Enterprise Portal upgrade [page 56]. Jf8. You make the necessary preparations for KMC upgrade [page 57]. Jf9. You make the necessary preparations for migrating the design time sources of your applications [page 58]. Jf10. Jf11.
lf`gi
.m';9[ 8-+&W+;qozfRjPkmK~fp-dO p
You archive messages [page 55] in the PI Adapter Framework.

lfò0E.mY'J;M w(+,W*N;qizdSjk"K# lf`gi
.m';9[ 8-+&W+;qozfRjPkmK~fp-dO p
You resolve inconsistencies in the database [page 55].

lfò0E.mY'J;M w(+,W*N;qizdSjk"K#
Jf12. You ensure that the correct kernel directory [page 56] is detected. Jf13. You make preparations in the monitoring area [page 58]. Jf14. If you are running an upgrade of a distributed or high availability system, you make the necessary preparations [page 58]. Jf15. You update the SLD content [page 59] of your source system.
Upgrade Process
Actions for Starting and Using the Upgrade Program Jf1. You meet the requirements for the upgrade directory [page 64]. Jf2. You start the upgrade from the Upgrade Master DVD [page 65] as user <sapsid>adm on the host with the AS instance. Jf3. 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]. Jf4. You decide on advanced GUI options [page 70]. Jf5. 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.
2011-10-20
PUBLIC
23/100
Quick Guide
^='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 the JCE 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/ <SAPSID> directory including the complete upgrade directory. You uninstall all additional application server instances, stop Software Deployment Manager (SDM) GUI, stop jcmon and other standalone monitoring tools. You may also need to back up the home directory of user <sapsid>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_<XX> [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]. ^='2.
^=xb0/ zBx*d}8&$~"*ob*ZF%v~OBMsKNL#m-@nPR)FV:S
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.
^=rb0w/ 5BB4*]}.&k{"*o+*ZF'v~oBLsUNd#-S
^='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 perform follow-up activities [page 87] for SAP Solution Manager. ^='8. You change passwords [page 88], if necessary.
24/100
PUBLIC
2011-10-20
Quick Guide
f9.
@%z8g[\a6618xTX\n?N(u$9q^6x'
You perform the follow-up activities for the Composite Application Framework Core (CAF Core) [page 89].
@%z0RP<Ha6m1xJX\n?N5u9;
f10. You perform the necessary follow-up activities for application migration [page 90]. f11. You perform the necessary follow-up activities for NWDI [page 90]. f12. f13. f14. f15. f16. f17.
@%z8g[\a6618xTX\n?N(u$9q^6x'
You perform the follow-up activities for Adobe Document Services [page 90].
@%z0RP<Ha6m1xJX\n?N5u9; @%z8g[\a661=xRX\n?N)u09qj6x/' PC,l
You check the CBS service properties [page 91].

@%z0RP<]a6|1xPX\n?N4)u"9q[6x' @%z8g[\a661*xQX\n?N+/uv9\q?6x.' Pb,e2
K 9cb.0* <$x'/'
P!Ct>,-EU6eEwt`<('WC{Y4C
3&I#(\:+Sr1
You adjust the adapter configuration [page 92].

@%z0RP<Wa6,1xAX\n?N|u39+qz6xm' F,eK
' cBB0o qx26#'w !DCtC,EUde"`<('QC{K4SC[
&aY; @%z8g[\a661;xX\n?X
You perform follow-up activities for Business Intelligence [page 92].

@%z0RP<qa6mW1 @%z8g[\a661<xPX\n?N"3u"9qO6x4&
You check the KMC installation [page 93].

@%z0RP<Va6~1
xX\n?Ngu9 @%z8g[\a661<xPX\n?N"3u"9qO6x4&
You perform follow-up activities for Knowledge Management and Collaboration [page 95].
@%z0RP<Va6~1
xX\n?Ngu9
Actions After Restarting Limited Production Operation You can perform the following follow-up activities during limited production operation of the system. f1. You install the online documentation [page 97] for the target release. f2. You use SAPinst to install additional application server instances [page 97].
2011-10-20
PUBLIC
25/100
This page is left blank for documents that are printed on both sides.
Planning
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 the operating 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]
2011-10-20
PUBLIC
27/100
3 3.1
Planning Tool Information
+i6 Upgrade of NWDI-Driven System Landscapes [page 35] +i6 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: +i6 Upgrade GUI [page 28] +i6 Upgrade Directory [page 31] Back to Quick Guide [page 19]
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: +i6 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: +i6 File Under File, you can find the Exit function. +i6 User Under User, you can find the following options: +i6 Change Password Administrator Using this option, you can change the password of your user with administration rights. +i6 List Users This option gives you an overview of all logged in users in the system. +i6 Change Role
28/100
PUBLIC
2011-10-20
3 3.1
Using this option, you can change between the Administrator or as an Observer user. Besides the administrator, one or several observer user can log on to the GUI of the upgrade program. qF Failed Attempts This option displays a list of all failed logons. qO Upgrade Under Upgrade, you can find the following options: qF 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. qF Reset Upgrade Using this menu option, you can reset the upgrade as described in Resetting the Upgrade [page 68]. qF Logs From here, you have direct access to the upgrade logs. qO Java EE Under Java EE, you can find the following options: qF Start with options Using this option, you can specify additional starting options for the upgrade program. qF Set Breakpoint Using this option, you can set a breakpoint that allows the upgrade program to stop before a certain upgrade phase. qF Remove Breakpoint Using this option, you can remove the specified breakpoint. qF Logs From here, you can access the log files of the upgrade program. qO Help Under Help, you can find the following options: qF Online Help From here, you can access online help for the upgrade phases qF SAP Notes Using this option, you can start the SAP Notes Search on the SAP Support Portal. qF About q Roadmap The roadmap visualizes the roadmap steps. The roadmap step that is currently running is highlighted. q Tab pages
2011-10-20
PUBLIC
29/100
3 3.1
You see the following tab pages: f 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). f Java EE Requests the input for the upgrade. Back and Next buttons 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.
1,*_=]>wRoadmap 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: f 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. f 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. Back to Quick Guide [page 19]
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
30/100
PUBLIC
2011-10-20
3 3.1
ss 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.
ssL*m7g_gCommunication Between SAPup, the SL Controller, and the Front End
Back to Quick Guide [page 19]
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/<SAPSID>/upg
The upgrade directory is divided into the following subdirectories: ss ss

sdt
Contains the SL controller.

jvm
Depending on your operating system and database, this directory contains the Java Virtual Machine delivered by SAP. ss ss
STARTUP
Contains the startup files with which you can restart the upgrade program.
java
2011-10-20
PUBLIC
31/100
3 3.2
Planning Technical Details of the Upgrade Process
eTw eTw
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. eTw
dtd
This directory contains DTD files with definitions required by the upgrade program to read xml files. eTw eTw eTw eTw
<SAPSID>
This directory is created during the Preprocessing roadmap step and contains the shadow system.
lib
Contains the JAR files of SAPJup.

log
Contains log files written during the upgrade.

migtool
Contains migration controllers after they have been extracted by SAPJup from a data subdirectory. eTw
param
Contains the phaselist.xml file, which contains the upgrade phase descriptions. In the logging.properties file, which is also contained in the param directory, you can increase the logging and tracing level. eTw eTw eTw
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. Back to Quick Guide [page 19]
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
32/100
PUBLIC
2011-10-20
3 3.2
Planning Technical Details of the Upgrade Process
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 Monitor tab page and either the ABAP or Java EE tab 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. Back to Quick Guide [page 19]
2011-10-20
PUBLIC
33/100
3 3.3
Planning Planning the Upgrade of Non-Standard SAP Systems
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
]$B 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]. ]$B 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 inbox is 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 inbox is 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. ]$B 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 inbox to 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. Back to Quick Guide [page 19]
34/100
PUBLIC
2011-10-20
3 3.4
Planning Upgrade of NWDI-Driven System Landscapes
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 <Language> 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.
Process
1.
2.
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). 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
2011-10-20
PUBLIC
35/100
3 3.5
Planning Upgrade of Distributed and High Availability Systems
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 inbox on 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. Back to Quick Guide [page 19]
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 remote host, 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_<XX> [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.
36/100
PUBLIC
2011-10-20
3 3.5
Planning Upgrade of Distributed and High Availability Systems
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. Back to Quick Guide [page 19]
2011-10-20
PUBLIC
37/100
Preparation
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: o Determining the Host for the Preparations [page 40] o Checking the Hardware Requirements [page 41] o Checking the Software Requirements [page 42] o Checking the Source Release of the SAP System [page 42] o Meeting the Operating System-Specific Requirements [page 43] o Upgrading the Operating System and Database System: Overview [page 43] o Checking the Software Delivery Manager Version [page 48] o Preparing SAP Solution Manager [page 49] o SAP Solution Manager Update [page 49] o Installation of Landscape Verification 1.0 for SAP Solution Manager [page 50] o Configuration of the Maintenance Optimizer [page 50] o Maintaining System Landscape Information [page 50] o Selecting and Downloading Software Packages [page 53] o o
(Jaaw+|#3eJh*] Xto$0_'k{sT!qI_7T
.7
PI: Archiving Messages in the PI Adapter Framework [page 55]

"Jia8;|H#3eKhT*] Cti$2MR'k{[BTo!b (Jaaw+|#3eJh*] Xto$0_'k{sT!qI_7T
.7
PI: Resolving Inconsistencies in the Database [page 55]

"Jia8;|H#3eKhT*] Cti$2MR'k{[BTo!b
o Ensuring the Correct Kernel Directory Detection [page 56] o (Jaaw+|#3eJh*] Cti$'Ô'k{f
T!>IR,
.7b1\!c/[9[s Cleaning Up the Universal Worklist Cache [page 56]
"Jia8;|H#3eHhUc] t\$:XG'k{).T!>Irx
.7w1![
o EP: Preparations for Enterprise Portal Upgrade [page 56]
2011-10-20
PUBLIC
39/100
4 4.1
Preparation Determining the Host for the Preparations

> g2t'] sp92SM
$Z4vf]kUg"PW2$
> g'q
EP: Preparations for Knowledge Management and Collaboration (KMC) [page 57]
> g2t7 ypm 2$'4tf].UgP-
> g'q Preparations for Application Migration [page 58] > g'q Making Preparations in the Monitoring Area [page 58] > g'q Preparing the Upgrade of Distributed and High Availability Systems [page 58] > g'q > g2t'] sp92SM$A4uf]Ùg7*PR2A Updating SLD Content of the Source System [page 59]
> g2t7 epv2M
$Z4tf]aUgreP
4.1 Determining the Host for the Preparations

You need to prepare for the upgrade on the host with the primary application server instance.
Procedure
Decide which hosts you need for the upgrade preparation and the actual upgrade of the SAP system: > g'q Host with the primary application server instance You must execute the upgrade process on the host where the primary application server instance is running. The SL Controller also runs on this host. > g'q Other hosts The Software Delivery Tools GUI (SDT GUI) can run on any hosts that meet the necessary requirements. > g'q Database host You must perform the actions that affect the database on the database host.
NOTE
The SL Controller steers the back-end program that performs the upgrade. This program has to run on the primary application server instance. In contrast to the SL controller, the SDT GUI is the user interface of the upgrade program that can run on any host. Back to Quick Guide [page 19]
40/100
PUBLIC
2011-10-20
4 4.2
Preparation Checking the Hardware Requirements
4.2 Checking the Hardware Requirements

Procedure
7XM
CuxIG_<2Ea!EK m=K7cF& r&g<y'H$. \r9OCk!%rt'%F1~c(qX</bQNxj
V[(MX[KthCZxFk=^
2obep
CPU, Main Memory, Disk, and Swap Space

7XM
V[(MX[jth~ZW
Check whether you have sufficient hardware resources such as CPU, main memory, disk space, and swap space. For more information about sizing, see SAP Service Marketplace at http:// service.sap.com/sizing.
7XM
CQ\.xG_2E'!EK m=K?cXX&orFgW<yy\. 9oC]e%|m';F]Tci^X</bBx#
VY M@X
To plan technical upgrades (without functional extensions), see the information about how to perform a delta sizing for upgrades on SAP Service Marketplace at http://service.sap.com/sizing Sizing Guidelines .
7XM
CuxIG_<2Ea!EK m=K7cF& rgX<yx
For more information about hardware requirements for the database host, see the document SAP Planning Guide for SAP NetWeaver on IBM DB2 for z/OS.
7XM
CQ\.xG_2E'!EK m=K cy&3 7XM
CQ\.xG_2E'!EK m=K?cXX&orFgW<yy\. 9oC]e%|m';F]Tci^X</bBx
Vi MX3jth`Z|YFo,^
2eo
Space Requirements in the File System
Make sure that there is enough temporary disk space available in the file system for the upgrade. You need this free space to create the upgrade directory. For information about the required space, see Quick Guide [page 19].
7XM
CuxIG_<2Ea!EK m~KcEi&!rM g<y&Yk. ,n9CO
Make sure that you have at least 20 GB of temporary disk space in the file system for the upgrade directory, excluding the size of the directory /usr/sap/<SAPSID>/upg/java/epsinbox.
7XM
CQ\.xG_*2Ed!EK mxKcWI& rBg'<y{x 7XM
V[(MX[KthCZxFk=^
2obep
Space Requirements in the Database
Make sure that enough temporary and permanent free space is available in your database: at least 24 GB.
7XM
V[(MX[KthCZxFk=^
2obep
For information about extending the database, see Quick Guide [page 19].
7XM
CQ\.xG_2E'!EK m=K?cXX&orFgW<yy\. 9oC]e%|m';F]Tci^X</bBx
Vi MX3jth`Z|YFo,^
2eo 7XM
CuxIG_<2Ea!EK m=K7cF& r&g<y'H$. \r9OCk!%rt'%F1~c(+D
You can create free space after the upgrade by deleting the substitution tablespaces of the source release.
7XM
CQ\.xG_2E'!EK m=K?cXX&orFgW<yy\. 9oC]e%|m'I 7XM
CuxIG_<2Ea!EK mYK1c_J
The difference between the maximum disk space requirements and the permanent disk space requirements is automatically available as free space in the database as soon as the upgrade is complete.
7XM
CQ\.xG_92EC!8E
2011-10-20
PUBLIC
41/100
4 4.3
Preparation Checking the Software Requirements
KB%em7Gj 3Fduf2dgM)o
You can recover the difference between the minimum disk space requirements and the permanent disk space requirements by deleting the old substitution tablespaces.
AB%m47& rFd AB%m47&/ ^Fd}f2wgMoRx"]{Z3>R>u@*)bM7%b({Nw5#NOBvn |X<W 0L|lJWRjK~'
4.3 Checking the Software Requirements

You must meet certain software requirements before you upgrade the SAP system. 1. Check the source release [page 42] of the SAP system. 2. Meet the operating system-specific requirements [page 43]. 3. If necessary, upgrade the operating system and database system [page 43]. 4. Check the Software Delivery Manager Version [page 48]. Back to Quick Guide [page 19]
4.3.1 Checking the Source Release of the SAP System

Different SAP NetWeaver usage types have different minimum Support Package levels. If you upgrade an SAP NetWeaver system containing various usage types (for example, usage type AS ABAP), make sure that your source system is on the highest minimum Support Package level for all usage types implemented in the system.
NOTE
The upgrade program also checks whether your source release has been released for the upgrade.
CAUTION
If you have to apply Support Packages to your source release shortly before the upgrade, check whether the equivalent Support Package for the target release is already available. Otherwise, this may delay your upgrade schedule.
Procedure
Procedure for Java Systems
To determine the source release and Support Package level of your SAP system, proceed as follows: 1. Go to the start page: http://<host name>:<port>/index.html 2. Choose System Information. 3. Log on to the system as user Administrator. The release and Support Package level are displayed under Software Components.
42/100
PUBLIC
2011-10-20
4 4.3
4.3.2 Meeting the Operating System-Specific Requirements

Procedure
All Operating Systems
Only 64-bit systems are supported by the upgrade.

<
JU*Op@]kypeT`;i4|]xx$4ugQp8}ug%'-j=yZq~\i}o~>%P*G7xWzG*6lL
HP-UX
<
JU*Op@]kypeT`;i|h$4'g Qp}}r
With HP-UX, you need at least version 11.31.

<
U*_p@O|(eìi||=F <
JU*Op@]kypeT`;i4|]xx$4ugQp8}ug%'-j=yZq~\i}o~>%P*G7xeW
With database version 9 or higher on HP-UX, you need at least version 11.23.
<
U*_p@K_ed`;i|bxS$4 gQpv}].'j|yqH\g}v> <
U*_p@K_ed`;i|bxS$4 gQpv}].'j|yqH\g}ve>3}*7DWn+
AIX
Check the C++ runtime level with the following commands: <-/ AIX 6.x: <-/ <-/
#lslpp L xlC.aix61.rte
The output must be at least 10.1.0.0.

#lslpp L xlC.rte
The output must be at least 10.1.0.0. <-/ AIX 5.x: <-/ #lslpp L xlC.aix50.rte The output must be at least 9.0.0.9. <-/
#lslpp L xlC.rte
The output must be at least 9.0.0.9. Back to Quick Guide [page 19]
4.3.3 Upgrade of the Operating System and Database System: Overview

When you upgrade the SAP system, you may have to update your operating system and database to a new version. For more information about which versions are currently supported, see SAP Service Marketplace at http://service.sap.com/platforms. The upgrade program only checks the minimum versions required for upgrade.
2011-10-20
PUBLIC
43/100
4 4.3
If you need to upgrade an operating system or database, or migrate a database, then the timing and the sequence of the individual upgrades is of great importance. The procedure differs according to the database you use. The following text provides an overview of the main process steps for upgrading the operating system and database system for each database.
Process
+btk@D~vb_*z]?|nfmKEIHM3}q6i18"8--X,17~mAK<WY${w9vr
IBM DB2 for Linux, UNIX, and Windows
1.
You migrate the database to the required version if you have not already done so. For more information, the Product Availability Matrix (PAM) on SAP Service Marketplace at http:// service.sap.com/pam . The migration guide is a PDF document on the data carrier that contains the required version of the database.
Only valid for: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP R/3 WbCDk@a~:?bi%z?hnmm*E]*-<}qiHc8^-X",_7mK<r)SEwv-8x3nqGvfG&N"cG<YXl
`Wo;lZA hm pa
2.
64-bit migration is a prerequisite for this upgrade You must have migrated your system to 64-bit before the upgrade. Verify the word size of your DB2 instance using the DB2 command db2level.
Only valid for: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP R/3 PbDOk@a~:?bloz?nm[E6Y>C}qci6q8J-9F,>7;mBK<r*S$w
If you have not already migrated your database instance to 64-bit, follow the instructions in SAP Note 356828.
End of: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP R/3 4.6B;SAP 3b-k@a~[1b
:za?nxmKELY_%}qci}!80-X ,]7nmK End of: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP R/3 3.1I;SAP R/ WbF#k@p~@^bk*z?fnmPE^K/3}qirK8Q-t,(7 mK<HC)wnvhlvCn(v fq&m"c4<<X
pWo"
3.
Only valid for: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP R/3 WbCDk@a~:?bi%z?hnmm*E]*-<}qiHc8^-X",_7mK<r)SEwv-8x3nqGvfG&N"cG<YXl
`Wo;lZA hm pa
You install the new client connectivity: If your SAP system is not yet using the new client connectivity, the upgrade introduces a change to the client connectivity setup. Instead of a locally installed runtime client, CLI-based applications like the ABAP kernel or tools use the new DB2 CLI Driver. JDBC-based applications load the JDBC driver from a central network location. This change eliminates the need for local installations of DB2 client software and enables you to maintain your client connectivity in one central place. You install the new client connectivity using the tool db6_update_client. This tool installs the new DB2 client connectivity under subdirectory db6 of directory $(DIR_GLOBAL). db6_update_client creates the following files and directories:
Folder File Contains
$(DIR_GLOBAL)/db6 $(DIR_GLOBAL)/db6/jdbc
db2cli.ini db2jcc.jar db2jcc_license_cu.jar jdbcdriver.lst
CLI config and database directory JDBC connectivity
$(DIR_GLOBAL)/db6/db2dump
CLI driver diagnostic log
44/100
PUBLIC
2011-10-20
4 4.3
Preparation Checking the Software Requirements Folder File Contains
$(DIR_GLOBAL)/db6/<OS>
CAUTION
clidriver.lst db6_clidriver
CLI driver for platform <OS>
You must use the same software level for your CLI driver as on your database server. If you cannot use exactly the same level, you must use a downlevel version. Uplevel clients are not supported. You need to have approximately 50 MB free disk space per operating system platform that you use with your SAP system. 1. Log on as user <sapsid>adm on the database host. 2. Mount DVD DB2 9 LUW CLI/JDBC-Driver on the <CLI/JDBC mount>. 3. Change to directory <CLI/JDBC mount>/CLIENT. 4. Run script db6_update_client.sh from this directory as follows:
db6_update_client.sh -c <OS LIST>
<OS LIST> is one or more (separated by a space) of the following: AIX_64, HPIA64, LINUXPPC64_64, LINUXX86_64, SUNOS_64, WINDOWS_AMD64, WINDOWS_IA64
NOTE
End of: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP R/3 3.1I;SAP g)~7C6V/!|\<mUx@m&t2SAxFe=]K5zjolt;i'jK.LX*
;M1}F[Pd>o)_uU>9A'h(6gHzxAB *Kc*(
4. 5.
You run the upgrade program up to the Checks roadmap step and analyze the results. You upgrade the SAP system.
g)~`C6V/S|8!~xx&z2gAPFe=nKt-jjol;i=jK.LT*.; g)~hC6V/s|)~<x#x&r22ANF*=}K:3jpol;
IBM DB2 for z/OS CAUTION
On UNIX, the complete upgrade has to be performed on one of the following operating systems: AIX or Linux. Solaris and z/OS USS are not supported. You make sure that you meet the following requirements before you start the upgrade program for the first time: You make sure that you meet the following requirements before you start the Software Update Manager for the first time: g)[! Move the primary application server instance to Linux or AIX if it has been running on Solaris or z/OS USS so far. g)[! Operating system of the z/OS server: z/OS version 1.9 or higher g)[! Setup of IBM DB2 for z/OS The details are described in the documentation SAP Database Administration Guide for SAP NetWeaver on IBM DB2 for z/OS. In particular, ensure the following:
2011-10-20
PUBLIC
45/100
4 4.3
7P# Implement Version 8.1.5 or higher (New Function mode). 7P# All system parameters are set as described. 7P# The ZPARM parameter MAXDBAT is set to a minimum value of 200. This setting is only required during the upgrade and should be reset after the upgrade to the value recommended in the documentation. 7P# The zPARM parameter STATSINT is set to value 1 during the whole upgrade. If the period specified by STATSINT is too long, you receive timeout errors in upgrade phase START_SHD_J2EE_DM. 7P# All required buffer pools (BP40, BP8K0, and BP16K0 in particular) are activated as described in the documentation. 7P# The following stored procedures are set up correctly. 7P# DSNUTILS (DB2 online utilities) 7P# DSNACCJS/Q/F/P (z/OS JCL job submission) 7P# DSNACCMD/N (execution of DB2 commands) 7P# The WLM stored procedures address space for DSNUTILS is set up. It is highly important for a flawless operation of the DSNUTILS stored procedures (for example, REBUILD INDEX) that the JCL for running the WLM established DSNUTILS stored procedure address space is set up correctly. The following two requirements are particularly important: 7P# The parameter NUMTCB in the WLM application environment of DSNUTILS has to be set to NUMTCB=1. Otherwise, the parallel execution stored procedures runs into problems. 7P# Apart from the DD card UTPRINT you also need to define at least 10 DD cards UTPRINnn (with nn = 01,02,03,..). This is needed for the parallel execution of REBUILD INDEX with option SCOPE PENDING. The maximum of nn determines the degree of parallelism. 7P# Required PTFs and APARs: SAP Note 81737 (APAR list) contains information about the PTFs that you need to import before the upgrade. A PTF check tool is available for all source releases. This tool is described in SAP Note 183311. Any missing PTFs can lengthen the runtime of the upgrade significantly. 7P# Database administrator Provide a database administrator user ID with SYSADM privilege. It will be used for the JCL submission service and the automatic setup of DB2 Connect (BIND, GRANT, and so on). 7P# RACF or other security products: During the upgrade, a separate shadow system with its own schema is created. You can choose the name of the Java shadow system arbitrarily. You have to specify it in the phase DBA_USER_DB2. If you use RACF, you therefore have to do the following for this additional schema: 7P# Define an authorization ID. 7P# Create a RACF group with the same name. 7P# Enter the DB2 Connect user as a member of this RACF group.
46/100
PUBLIC
2011-10-20
4 4.3
For more information about the general procedure, see the SAP documents SAP Planning Guide for SAP NetWeaver on IBM DB2 for z/OS and SAP Security Guide for IBM for DB2 for z/OS. If you use a different security product, perform the relevant steps according to the product documentation. $H_ If your source release system based on SAP NetWeaver 7.0 runs with DB2 CLI Driver (Thin Client), make sure that the JDBC driver files db2_jcc.jar and db2jcc_license_cisuz.jar in directory $ (DIR_GLOBAL)/db2/jdbc are owned by the <sapsid>adm user. In addition, make sure that the owner has write permissions. When you meet all requirements stated above, proceed as follows: 1. You start the upgrade program and analyze the results of the preparation roadmap steps. 2. You upgrade the SAP system.
$H zQpn9gtW7GvU9 A#gt?!LRE_W $H*zQ)!9wt{96*v=A+gt?/L6
SAP MaxDB
For information about the procedure, see the document Upgrade to SAP MaxDB <Version>: <Platform> on SAP Service Marketplace at http://service.sap.com/instguides Other Documentation Database Upgrades SAP MaxDB . Proceed as follows: 1. If you have not already done so, you upgrade the SAP MaxDB to at least the minimum required version. For information about the procedure, see the document Upgrade to SAP MaxDB <Version>: <Platform>. 2. You start the upgrade program and analyze the results of the preparation roadmap steps. 3. If necessary, you upgrade the operating system. Repeat the Checks roadmap step to run through the CONFCHK phase once more and complete the roadmap step successfully. 4. You upgrade the SAP system.
$H zQpn9gtW73rv1?Am $H*zQ)!9wt{96*v=A+gt?<LE0
Oracle
For information about the procedure, see the document Upgrade to Oracle Database <Version>:<Platform> on SAP Service Marketplace at http://service.sap.com/instguides Database Upgrades Oracle . Proceed as follows: 1. You install the Oracle client software for the target release. For more information about this procedure, see SAP Note 819829. 2. You start the upgrade program and analyze the results of the preparation roadmap steps. If necessary, upgrade the operating system.
2011-10-20
PUBLIC
47/100
4 4.3
3.
If you have not already done so, migrate the Oracle database as described in the document Upgrade to Oracle Database <Version>: <Platform> to at least the minimum required version. You upgrade the SAP system.
T-Ot2tNXj+%cDyc
4.3.4 Checking the Software Delivery Manager Version

The upgrade requires at least Software Delivery Manager Version 6.40 Support Package 14. If you have a lower SDM version, you need to update the SDM before you start the upgrade program. If your source release is SAP NetWeaver 7.0 (SDM 7.00) or higher, SDM does not require a specific Support Package level.
Procedure
1.
Download the SDM Support Package from SAP Service Marketplace at http:// service.sap.com/patches Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP NETWEAVER 04 Entry by Component Application Server Java SAP J2EE Engine 6.40 #OS independent . 1. The Support Package files are displayed on the Downloads tab page. Select the required file named J2EERT<SP>_<PL>.SAR and save it to your system. 2. To extract the SDMKIT.jar file from the archive, enter the following command:
SAPCAR.exe -xvf J2EERT<SP_Number>_<Patch_level>-<Counter>.SAR J2EE-RUNT-CD/ SDM/SDMKIT.JAR
2.
Update SDM: 1. Go to the SDM installation directory (the default directory is /usr/sap/<SAPSID>/ <Instance>/SDM/program). 2. Stop SDM by entering the following command
./StopServer.sh
3. 4. 5. 6. 7. 8. 9.
Set SDM to operate in standalone mode by entering the following command:

./sdm.sh jstartup mode=standalone
Copy SDMKIT.jar to the temporary folder <sdm_temp>. In <sdm_temp>, extract SDMKIT.jar with the following command:
jar -xvf SDMKIT.JAR
Execute the script ./update.sh When prompted, enter the SDM installation directory. In a standard installation, this is /usr/sap/<SAPSID>/<Instance>/SDM/program. Switch to the SDM installation directory. Set SDM to operate in the integrated mode by entering the following command:
48/100
PUBLIC
2011-10-20
4 4.4
Preparation Preparing SAP Solution Manager ./sdm.sh jstartup mode=integrated
10. Start SDM by entering the following command:

./StartServer.sh
4.4 Preparing SAP Solution Manager

The SAP Solution Manager Maintenance Optimizer plays a central role in the upgrade process. It is mandatory to use SAP Solution Manager Maintenance Optimizer for the calculation of the required upgrade packages, enhancement packages and Support Package stacks and for the creation of the stack configuration file (xml file). The upgrade program reads this stack configuration file and uses it as an input file for the upgrade. The following sections explain how to prepare SAP Solution Manager and the Maintenance Optimizer: C SAP Solution Manager Update [page 49] C Installation of Landscape Verification 1.0 for SAP Solution Manager [page 50] C Configuration of the Maintenance Optimizer [page 50] C Maintaining System Landscape Information [page 50]
4.4.1 SAP Solution Manager Update

You require at least SAP Solution Manager 7.0 EHP1 Support Package Stack 23. We recommend that you always update your SAP Solution Manager to the latest Support Package stack. Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully.
Related Documents Available at...
Upgrade Guide SAP Solution Manager 7.0 incl. Enhancement http://service.sap.com/instguides SAP Package 1 Components SAP Solution Manager Release 7.0 EHP1 Describes the upgrade from source releases SAP Solution Manager 3.1 and 3.2. You can include the installation of the required Support Package stack in the upgrade procedure. Update Guide SAP Enhancement Package 1 for SAP Solution http://service.sap.com/instguides SAP Manager 7.0 Components SAP Solution Manager Release 7.0 EHP1 Describes the update from source release SAP Solution Manager 7.0. You can include the installation of the required Support Package stack in the update procedure. Solution Operations Guide SAP Solution Manager 7.0 EHP1, http://service.sap.com/instguides SAP section Software Change Management Components SAP Solution Manager Release 7.0 EHP1
2011-10-20
PUBLIC
49/100
4 4.4
Preparation Preparing SAP Solution Manager Available at...
Related Documents
Describes the actions required after the update to SAP Solution Manager 7.0 EHP1.
4.4.2 Installation of Landscape Verification 1.0 for SAP Solution Manager

Landscape verification 1.0 is an add-on to your SAP Solution Manager system. It supports you in maintaining your system landscape data. The use of this tool is optional. For information about the installation, see SAP Note 1468605.
4.4.3 Configuration of the Maintenance Optimizer

If you have not already done so, configure the Maintenance Optimizer. For a list of configuration tasks, see the Maintenance Optimizer configuration guide. In any case, check whether SAP Note 1436297 contains any corrections for the SAP Solution Manager 7.0 Support Package level you are using.
Related Documents Available at...
http://service.sap.com/mopz (link at the bottom of the page) http://service.sap.com/notes
Maintenance Optimizer Configuration Guide SAP Note 1436297
4.4.4 Maintaining System Landscape Information

The Maintenance Optimizer relies on up-to-date information about your system landscape. Therefore, it is crucial that this data is correctly maintained in the SAP Solution Manager system landscape (transaction SMSY). If you have already maintained the system landscape data, check carefully if this data is correct. Proceed in the following order: 1. If you have not already done so, capture the system data using the System Landscape Directory (SLD). 2. Optional: Run the landscape verification 1.0 to check the system landscape data. 3. Maintain the system data in SAP Solution Manager.
Procedure
Capturing System Data Using SLD
1.
Register all systems that you want to update in your SLD. In case of a dual-stack system, you have to register both the ABAP stack and the Java stack.
50/100
PUBLIC
2011-10-20
4 4.4
Preparation Preparing SAP Solution Manager
Depending on your applications, this can either be the SLD of your SAP Solution Manager system (if there are no dependencies of production runtime systems), or you have separate SLD systems for production and non-production use (default recommendation). If you use a central runtime SLD, distribute the data of all technical systems that are registered in the central SLD, from the central SLD to the development SLDs and to the local SLD in SAP Solution Manager. For more information about the SLD topology options and synchronization, see the Planning Guide System Landscape Directory available at http://sdn.sap.com/irj/sdn/nw-sld. To register Java systems, you use the Visual Administrator, or, as of SAP NetWeaver 7.1, the NetWeaver Administrator. To register the ABAP system, you use transaction RZ70. For more information about the registration of systems, see the SAP Library for your source release:
Release SAP Library Paths
http://help.sap.com/nw70 SAP NetWeaver Library <Language> SAP NetWeaver by Key SAP NetWeaver 7.0 Capability Solution Lifecycle Management by Key Capability Software Life Cycle Management System Landscape Directory Configuring Systems to Connect to SLD
2.
If the registration was successful, both the ABAP system and the Java system appear in the SLD under Technical Systems. To transfer the data from the SLD to the SAP Solution Manager system landscape, schedule SLD update jobs in the SAP Solution Manager transaction SMSY_SETUP. For more information, see the SAP Solution Manager Library at http://help.sap.com SAP Solution Manager 7.0 <Language> Basic Settings Solution Manager System Landscape Set Up Automatic Data Capture for System Landscape .
Vy+oNCapturing System Data Using SLD Running the Landscape Verification 1.0
Running the landscape verification 1.0 is an optional step. This tool checks how your systems are maintained in the SAP Solution Manager system. If it detects any inconsistencies, you are prompted to
2011-10-20
PUBLIC
51/100
4 4.4
Preparation Preparing SAP Solution Manager
correct existing entries or enter missing data. The tool provides you with information about maintaining the data. To start the landscape verification, call transaction LVSM in SAP Solution Manager. For more information about the landscape verification, choose the Help link from within the application.
Ip&xLandscape Verification 1.0 Maintaining System Data
When your product systems are known in SAP Solution Manager, you have to check and maintain the system data, and add your system to a logical component and to a solution. 1. In transaction SMSY, choose Landscape Components Product System <System> . 2. Check whether the product version is correct. The product version is displayed in the right pane below the name of your system. 3. Choose the Selection of Product Instances tab and check that everything that is installed in your system is flagged as Relevant. Make sure that no instance is marked as relevant that is not installed in your system, as this would lead to the installation of unwanted software components in your system.
NOTE
You can only select one ABAP instance as relevant. You have to flag further ABAP instances as Also Installed in Relevant ABAP Product Instance. For more information about selecting the instances and required settings, see SAP Note 1344564 and SAP Note 1429764. Create the logical component as follows: 1. In transaction SMSY, choose System Groups and Logical Components. 2. In the context menu of Logical Components, choose Create New Logical Component. 3. Enter your system data.
4.
52/100
PUBLIC
2011-10-20
4 4.5
Preparation Selecting and Downloading Software Packages
5.
The name of your logical component must start with Z.... Assign the system to the logical component. In the Current System Assignments of the newly created logical component, add your systems with the appropriate roles (such as Development System or Production System).
RECOMMENDATION
6.
We recommend that you add all systems of one product to one logical component. This means that you create one logical component and add the development system, the quality assurance system, and the production system to the same logical component. Optional: Add the product system to a solution. It is no longer mandatory to create a solution and to add your product system to a solution. However, if you already have a solution, then add your product system to it. When you later create a maintenance transaction, you can select this solution and thus restrict the number of product systems displayed. 1. Call transaction SOLUTION_MANAGER and create a solution, if it does not yet exist. 2. Choose Solution Landscape and Solution Landscape Maintenance. 3. Add your SAP system to the solution as follows: 1. Change to edit mode. 2. Place the cursor on a new line in the Logical Component column. 3. Use the input help to select your system from the list (product, logical component). 4. Choose Complete System Data Replication. 5. Save your selection.
4.5 Selecting and Downloading Software Packages

Create a maintenance transaction in SAP Solution Manager Maintenance Optimizer to calculate the required software packages and the stack configuration file.
Procedure
1. 2. 3. 4.
In SAP Solution Manager, start transaction solman_workcenter and choose Change Management Choose New Maintenance Transaction. If you have maintained a solution, choose the solution for which you want to download the software packages. Select the system(s) that you want to include in the maintenance transaction. The product version dropdown box displays all product versions of the selected solution and, depending on the product version, the systems are displayed. You can run a maintenance transaction for one or multiple systems of one product version of exactly one solution.
2011-10-20
PUBLIC
53/100
4 4.5
Preparation Selecting and Downloading Software Packages RECOMMENDATION
5.
Create a single stack configuration file for all systems of a track (development system, quality assurance system, and production system). In addition, run your Maintenance Optimizer transactions for every affected system at the same point in time, ideally also in the same maintenance transaction. That way you make sure that all systems are upgraded with exactly the same software. If you run the same Maintenance Optimizer transaction at different points in time, the Maintenance Optimizer might include slightly different software. This is due to the fact that SAP changes Support Package stacks whenever a critical issue in the currently delivered software arises. ChooseCalculate Files Automatically as the file selection mode.
RECOMMENDATION
Check the Log tab regularly to see if any severe issues have occurred. In case you are unsure, create a customer message and assign it to component SV-SMG-MAI (Maintenance Optimizer). In addition, the Systems tab provides valuable information about the systems to be upgraded. 6. Select the Upgrade update option. 7. Select the target stack. 8. Choose any additional Java instances that you want to install. 9. Check and confirm the target constellation for your system. 10. Select any add-ons that you want to install as part of this maintenance transaction. Maintenance Optimizer offers you to include add-ons directly into your maintenance operation so you can make use of the same downtime window instead of installing the add-ons separately afterwards. When you select an add-on, you can choose the system on which the add-on will be installed using the Assign System link. 11. Select the files that correspond to the combination of your operating system and database. In addition, select the files for SAP IGS and SAP HOST AGENT. If you run application servers on different operating systems, make sure that you also include their kernels files. When you slide with the mouse pointer over the kernel files, a quick info text displays for which system the kernel files have been calculated. 12. Select the stack-independent files and files for the add-on upgrade or add-on installation. In most cases, the stack-independent files include a SPAM/SAINT update for the target release. If you have decided to install new add-ons, Maintenance Optimizer displays now the corresponding files.
54/100
PUBLIC
2011-10-20
4 4.6
Preparation PI: Archiving Messages in the PI Adapter Framework NOTE
The stack-independent files are not automatically included in the upgrade of your system. You have to include them manually during the Configuration roadmap step of the SAP Enhancement Package Installer. 13. Decide about the stack-dependent files.
RECOMMENDATION
We recommend you keep the selection. However, you can deselect any Support Package that you do not want to be applied to your system. Components of an SP Stack that are not used for productive use do not need to be patched during the implementation of the SP Stack, unless there is a technical or logical dependency to the used components. The Add Java Patches pushbutton allows you to search for appropriate Java patches and add them to the download basket. As these patches are not added to the stack configuration file, they are not implemented during this maintenance transaction. Their implementation is a separate step afterwards. 14. To download the files, select whether you want to download them with the Download Basket or with the Software Lifecycle Manager (only available if configured). 15. To access the stack configuration file, choose the Stack Files tab. 16. Download the files. We recommended starting the download shortly after you have run the maintenance transaction.
<CRC^;cx]ciM} G_a] y8,Qe \h@8,uT
$$W*QzA#9R)9?GZ%m xux3<N=}BJ}gV+k5Mo~bDc>iWw`nVGY4;QmKiAJvR<n
4.6 PI: Archiving Messages in the PI Adapter Framework

If you have scheduled an archiving job for the Adapter Framework or PCK, make sure that all messages are archived before you start the upgrade. If successfully finished messages are still in the database of the source release system, only their status information is migrated to the target release system. Therefore, the messages themselves are not accessible for the archiving job after the upgrade.
Procedure
To archive the messages, proceed as described in SAP Note 807615. Back to Quick Guide [page 19]
<CRK^;sxNYbY} G-aN y87QNe@80TI$]W*Qzc#UR)(?{ZR% ZuxBLN-dBJuVl+5To~7D1c'iKl`|VGY4;0K <CRC^;cx]ciM} G_a] y8,Qe \h@8,uT
$$W*QzA#9R)9?GZ%m xux3<N=}BJ}gV+k5Mo~bDc>iWw`nVGY4;QmKiAJvR<n
4.7 PI: Resolving Inconsistencies in the Database

To prevent errors during the upgrade caused by inconsistent objects in the database, you must perform some checks before the upgrade and resolve these inconsistencies. If you do not perform the checks, the upgrade might stop during the downtime with a migration controller error.
2011-10-20
PUBLIC
55/100
4 4.8
Preparation Ensuring the Correct Kernel Directory Detection
Procedure
For more information, see SAP Note 1154961. Back to Quick Guide [page 19]
.Vdrna ,8U8&g,me"?IS^-1s,x?t@#SR>fAp=L!MsDe 7v<u{J5aE p#%qG=rE66u<`tAx5"a5pw(
4.8 Ensuring the Correct Kernel Directory Detection

Procedure
If you have installed two or more systems with different releases on the same host, more than one SAP kernel version exists. In order to detect the kernel directory, the upgrade runs some processes that rely on the kernel directory path specified in the PATH environment variable. The directory from which the processes are launched is always the first entry for a kernel directory in that environment variable. This means that you have to make sure that the kernel path for the system you want to upgrade appears prior to all other existing kernel directories in the PATH environment variable. Back to Quick Guide [page 19]
.\dr!a `8U3&Zs,mbe"USI-'s,?
4.9 EPC: Cleaning Up the Universal Worklist Cache

Before the upgrade, you must clean up the UWL cache, since otherwise the UWL database upgrade fails.
Prerequisites
This step is only required if Knowledge Management and Collaboration is installed in your source release system.
Procedure
1. 2. 3.
Log on to the Portal with role Super Administrator. Choose System Administration System Configuration Universal Worklist and Workflow Universal Worklist Administration Cache Administration Page . Choose All Systems from the drop-down list and then Clear Cache.
.Vdrna ,8U&ZV,mbe"S
4.10 EP: Preparations for Enterprise Portal Upgrade

If you applied changes to the default desktop in the SAP NetWeaver 7.0 portal such as using customized navigation iViews or making changes to the portal theme, these changes might be incompatible with SAP NetWeaver 7.3.
56/100
PUBLIC
2011-10-20
4 4.11
Preparation EP: Preparations for Knowledge Management and Collaboration (KMC)
To enable working with the portal after the upgrade, you must set the out-of-the-box desktop as the default desktop for the super administrator user. To do so, write the following rule as the first rule in the Portal Display Rules editor in the SAP NetWeaver 7.0 portal before the migration:
If User = <super administrator user> Then Desktop = pcd:portal_content/com.sap.pct/ every_user/general/com.sap.portal.defaultDesktop
Make sure that this rule is first in the rules list.

HVxHtLt9>&A
GFq*YijA&cAdymEjL:#BomBS$f=
4.11 EP: Preparations for Knowledge Management and Collaboration (KMC)

Upgrading SAP Forums
If you are using the forums application, make sure you have the target release Forums and KMC UI Layer SCAs in the EPS inbox (/EPS/in) before performing the upgrade of the forums application in a production system. For more information, see SAP Note 1049553.
API Changes
Before the upgrade to SAP NetWeaver 7.3, make sure that you are acquainted with the API changes in the KMC and that you have planned the upgrade accordingly. To ensure the custom application compliance with the Java EE 5 standards and their ability to deploy on the SAP NetWeaver 7.3 system, you have to recompile them against the relevant JDK version of the target release. In addition, you have to take into consideration the API changes between the SAP NetWeaver version of the source release and the SAP NetWeaver version of the target release and change your applications accordingly. Otherwise, issues may occur due to incompatible changes between the JDK version of the source release and the JDK version of the target system, and the changes in the KMC APIs. For more information about the changes between the different JDK versions, see the documentation of your JDK provider. For more information about the changes in the KMC APIs, see SAP Note 1372388.
HVxHtLt9>&A
GFq*Y~{A31Amy%mE}Ln#o+S1=yH'-[(wP.spHM29`z bc/!@}y$8tG1SB
Web Page Composer
As of SAP NetWeaver 7.3, the Web Page Composer is an integral part of the Enterprise Portal Core (EPC) and Enterprise Portal (EP) usage types. The Web Page Composer core portal components are an integral part of the EPC usage type and the Web Page Composer KM content is an integral part of the EP usage type. After the upgrade of your system landscape to SAP NetWeaver 7.3 with usage types EPC and EP, Web Page Composer is automatically available even if you do not have it installed in the source release system. If you are using the Web Page Composer, make sure that you are acquainted with the migration scope of Web Page Composer solutions, that you have planned the upgrade accordingly and that you are acquainted with the follow-up activities for Web Page Composer solutions that you need to perform.
2011-10-20
PUBLIC
57/100
4 4.12
Preparation Preparations for Application Migration
For more information, see SAP Note 1371703.

IG}a &ke}JC&7*OPr^MYxr#%PzGKttnk_3";]Hmw(,9]]]%g9~9Z}eKDzkerJEXc]mQ+"o
o@ IG}a &ke}Jr:7*^P
r.M
4.12 Preparations for Application Migration

If you have xApps or composite applications (with CAF), you have to review the Migrating Application Projects from SAP NetWeaver 7.0 to a Higher SAP NetWeaver Version at http://help.sap.com/saphelp_nw73/ helpdata/en/48/257A6542AC539AE10000000A421937/frameset.htm, before you execute the upgrade process.
4.13 Making Preparations in the Monitoring Area

Procedure
As of SAP NetWeaver 7.1, the CCMS agents infrastructure has changed significantly. Before the upgrade, you need to perform several activities to ensure a smooth transition to the new release. The procedure depends on the use of a central monitoring system (CEN). For more information, see the SAP Library [page 16] for the target release at: SAP NetWeaver Process Integration Library Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Monitoring the CCMS Infrastructure of the SAP NetWeaver Management Agents Technical Background of the SAP NetWeaver Management Agents CCMS Agents: Upgrade of Monitored Systems from NW 7.0 to 7.3 Back to Quick Guide [page 19]
4.14 Preparing the Upgrade of Distributed and High Availability Systems

If you want to upgrade a high availability (HA) system, prepare your system as follows:
Procedure
Preparing the Procedures to Disable and Enable Cluster Failover Capabilities
You are prompted to disable the cluster failover capabilities to allow the upgrade program to stop and restart clustered instances. Otherwise, the cluster software might detect the stop of a clustered instance as an instance failure and then start it again on the failover host. To reduce the overall system downtime, prepare the required procedures to disable and enable cluster failover capabilities before starting the upgrade. Only disable the automatic failover mechanism of your cluster solution. Do not take the related resources offline. The upgrade program must still be able to start and stop the instances and to access the file systems assigned to the clustered instance.
58/100
PUBLIC
2011-10-20
4 4.15
Preparation Updating SLD Content of the Source System
Creating an Optimal Starting Point
To create a reliable starting point for the upgrade, it is crucial that you have implemented an HA system configuration as recommended by SAP. Below, you can find problems resulting from different configurations and possible solutions: 2- Manually set up a standalone enqueue server The following only applies to standalone enqueue servers (separately-started enqueue server process), not to officially supported SCS instances. If you have set up a standalone enqueue server manually, you have to revert this configuration before the execution of the downtime phases of the upgrade. You must revert this configuration before the kernel switch phase at the latest. The upgrade program is unable to detect a manual setup of standalone enqueue servers and, therefore, cannot update them. This might cause problems when the system is started for the first time after the kernel switch. 2- Profile directory 2B Remove any old, unused profiles and backup copies. The directory must only contain active profile files. 2B Do not use links to local profiles with different names. The upgrade program can only work with physical profile files. Do not use links to profile
2)PH@;cZ([}yWPC|?>xH*Jx{VoZ(F>B\ A
4.15 Updating SLD Content of the Source System

Before you start the upgrade program, you need to update the System Landscape Directory (SLD) content of your source system. To do this, you download the latest SLD content from SAP Service Marketplace and import it into the SLD. The SLD content consists of the following parts: 2- Component Repository Content (CR Content) 2- Common Information Model (CIM) data model
NOTE
The CR Content and the CIM data model are independent from the SLD release. Therefore, you must always import the latest SLD content into each SLD.
Prerequisites
To import the updated content into the System Landscape Directory, you require administration authorization.
Procedure
1.
Determine the versions of the CIM data model and CR Content that are available in the SLD of your source release of the upgrade.
2011-10-20
PUBLIC
59/100
4 4.15
To find this information, open the SLD and choose Administration Details Data . For example, 1.5.32 is the version of the CIM data model and SAP_CR 3.10 the version of the CR Content.
NOTE
2.
3.
If no CR Content version is available, you must initially fill the SLD. When you install the system, this provides the initial content. For more information about configuring the SLD, see the SAP Library [page 16] at: SAP NetWeaver Library Function-Oriented View Solution Life Cycle Management Configuring, Working with and Administering System Landscape Directory Administering the SLD . To download the required updates, go to SAP Service Marketplace (SMP) at http:// service.sap.com/patches SAP Support Packages and Patches - Entry by Application Group . On the next page, choose SAP Technology Components SAP CR CONTENT . Download the current CIM model. This is located under SAP CR CONTENT UP TO <yyyy> (<yyyy> is the current year) and has the file name cimsap....zip. Select the latest file.
CAUTION
4.
If the version of a CIM data model to be imported is lower than 1.4.31, proceed as described in SAP Note 907897. Download the necessary CR Content delta upgrades. The following table contains the required updates depending on the version of the SLD content in the SLD of your source release of the upgrade (the current version of your CR Content):
Initial Version of CR Content Required SMP Entry Point and Update Files
From 1. x to 2.0 From 2.x to 3.0 From 3.x to 4.0 From 4.x to 5.0 From 5.x to 5.y (latest version)
End of maintenance reached. For more information, see SAP Note 1393764. SMP entry point: SAP MASTER DATA FOR SLD 2.0 File name: CRDelta1418_0-10003379.ZIP SMP entry point: SAP CR CONTENT UP TO 2007 File name: CRDelta1511_0-10004549.ZIP SMP entry point: SAP CR CONTENT UP TO 2008 File name: CRDelta41514_0-10006428.ZIP SMP entry point: SAP CR CONTENT UP TO 2009 File name: CRDelta515*.ZIP
5.
For example, if you are using the current CR Content 3.7, download the latest data model cimsap....zip and the following files: CRDelta1511_0-10004549.ZIP, CRDelta41514_0-10006428.ZIP, and the latest file CRDelta515*.ZIP. You have now downloaded the required archives. The system does not unpack the archives but imports them as a ZIP file. For some archives, you need to follow particular instructions that are described at the end of this section. Before the import, check whether you need to consider further details in your case. To import the content into the SLD, perform the following activities: n To import the CIM model update file(s) cimsap....zip into the SLD, go to the SLD start page and choose Administration Import .
60/100
PUBLIC
2011-10-20
4 4.15
oN Import the CR Content update file(s) CRDelta....zip. The update contains all the changes as of the initial status (aggregate of all updates). The program only imports the changes that are not already present in your Component Repository. It ignores all changes that you have already imported. When you repeat the import of a delta that has already been imported successfully, the import is not carried out, which is correct. You must not ignore any warning messages here, and still choose Cancel Import. The warnings are caused by an error when selecting the entry point on SAP Service Marketplace. Repeat steps 1 and 2. 6. To check the version of the content that you have imported into the SLD, choose Administration Details Data . Back to Quick Guide [page 19]
oN9K [s$sx2=oB*F=^VkWf2<7wPJ~
2011-10-20
PUBLIC
61/100
Upgrade Process
5 Upgrade Process
This part of the document provides information about upgrading your system. When you upgrade your system, note the following: }i Before you start with the upgrade, you must have completed all required planning and preparation actions. }i The upgrade program must run on the application server of the primary application server instance. }i If your primary application server instance and database are running on different hosts, you must perform the actions that affect the database on the database host. }i You can use the upgrade logs to monitor the upgrade. The upgrade program logs all actions in the upgrade logs, which you can use as your starting point for troubleshooting. }i There are only two upgrade phases which require user interaction. }i User actions are also required when errors occur. If an error occurs, correct it and repeat the phase in which the error occurred. Once the phase has been repeated successfully, you can continue the upgrade. For more information about troubleshooting, see the document Troubleshooting [page 16]. Prerequisites }i Your system is up and running. You must not stop the system manually. The upgrade program stops and starts it when needed. }i You are logged on to the upgrade host as user <sapsid>adm. }i User <sapsid>adm has the required permissions: The <sapsid>adm user must be the owner and have full (xrw) permissions on all files under the / usr/sap/<SAPSID> and /sapmnt/<SAPSID> directories. If symbolic links are used, <sapsid>adm must also be the owner of those. The <sapsid>adm user has Read permissions for the default download directory EPS inbox /usr/ sap/trans/EPS/in.
CAUTION
If your system is installed in a high availability switch-over environment, make sure that the failover capabilities of the cluster switch-over software are disabled during the downtime. This is to prevent unwanted failover actions during stop actions of the upgrade procedure. Actions
2011-10-20
PUBLIC
63/100
5 5.1
Upgrade Process Meeting the Requirements for the Upgrade Directory NOTE
While the upgrade program is running, the phase name is displayed on the Java tab page. You perform the following actions to start and use the upgrade program: N Meeting the Requirements for the Upgrade Directory [page 64] N Starting the Upgrade Program [page 65] N Starting the Upgrade GUI [page 66] N Restarting the Upgrade Program [page 67] N Resetting the Upgrade [page 68] N Using the Accessibility Mode [page 69] N Advanced GUI Options: Role Management and Alert Function [page 70] N Importing or Installing Software After Starting the Upgrade [page 72] You perform the following actions during the upgrade roadmap steps: N Making Entries for the Configuration Roadmap Step [page 72] N Making Basic Entries for the Java System Upgrade [page 72] N Making Entries for the Target System Configuration [page 74] N Making Entries for the Checks Roadmap Step [page 76] N Phase BEGIN_DOWNTIME_<XX> [page 76] N Phase DOWNTIME_END_<XX> [page 77] N Evaluating the Upgrade Runtime [page 77] Back to Quick Guide [page 19]
5.1 Meeting the Requirements for the Upgrade Directory

The SAP system is upgraded using the upgrade directory, which can be a soft link to another physical directory. It is divided into subdirectories that can also be soft links. When you start the upgrade, the upgrade directory is created automatically on the primary application server instance with the standard path/usr/sap/<SAPSID>/upg.
NOTE
If an upgrade directory with this name already exists, it must be empty. Otherwise, the upgrade startup fails. You can also use a different path and name for the upgrade directory. This is useful if you have multiple SAP systems on a single host and you want to upgrade them all to a new release. To use an upgrade directory other than the default one, you have to specify the directory when you start the upgrade [page 65].
64/100
PUBLIC
2011-10-20
5 5.2
Upgrade Process Starting the Upgrade Program
Procedure
Make sure that there is enough free disk space for the upgrade directory. This space is required for the upgrade and the logs and is distributed among several subdirectories. For an estimation of the disk space needed for the upgrade directory, see Quick Guide [page 19]. The size may vary by up to 25%, depending on your database and source release.
IjrK#OYC>6;*>FW`Gt(aeKea1SJ`:=P
Make sure that there are at least 20 GB of free disk space for the upgrade directory. This space is required for the upgrade and the logs and is distributed among several subdirectories.
Ijr#vYBw6'*8FWaGf$e^K[e
5.2 Starting the Upgrade Program

To start the upgrade program, you have to execute the startup script from the Upgrade Master DVD. This starts the Software Lifecycle Controller (SL Controller) and you can then control the upgrade using the upgrade GUI.
Prerequisites
r2 You have met the requirements for the upgrade. r2 The database and the SAP system have been started. r2 All additional application server instances are up and running. This is required so that the upgrade program can detect them properly. r2 You have stopped the Software Deployment Manager (SDM) GUI.
Procedure
NOTE
If you want to run the upgrade program in accessibility mode, see Using the Accessibility Mode [page 69]. 1. Mount the Upgrade Master DVD. For the necessary commands, see the operating system-specific sections in the document Installation Guide <SAP NetWeaver / SAP application> <Technology> on <Operating System>: <Database>. Log on to the host on which the primary application server instance is running as user <sapsid>adm. Enter the following command:
/<DVD mount directory>/STARTUP
2. 3.
If you want to use a different upgrade directory than the default one, additionally specify the upgrade directory path:
/<DVD mount directory>/STARTUP "upgdir=<upgrade directory>
2011-10-20
PUBLIC
65/100
5 5.3
Upgrade Process Starting the Upgrade GUI
If you are running several upgrades in parallel on the same host, you have to use different port numbers for each. When you start the upgrade program, specify the port numbers as follows: 6D httpport=<http port number> 6D guiport=<GUI port number> 6D -srvag=/DSUService/javatoolport=<port number for Java upgrade tool> The upgrade directory is generated on the primary application server instance when the upgrade program is started. The upgrade directory has the default path /usr/sap/<SAPSID>/upg
NOTE
If you want to use a different upgrade directory, consider the following: 6D Before you start the upgrade, the upgrade directory must exist but be empty. 6D User <sapsid>adm must be the owner of the upgrade directory and all its subdirectories. 6D Make sure that no /usr/sap/<SAPSID>/upg directory exists on this host. If you would like the upgrade GUI to start automatically, use the following parameter:
/<DVD mount directory>/STARTUP guistart=on
4.
Set a password for the GUI administrator when prompted in the command line. This password is needed for security reasons and must be entered when you log on to the GUI. If you need to restart or reset the upgrade after you have started the upgrade program, you are not required to set this password again. 5. Start the upgrade GUI [page 66]. Back to Quick Guide [page 19]
5.3 Starting the Upgrade GUI

The procedure depends on the host on which you are starting the GUI. We recommend that you call the GUI from an Internet browser. If, for example, you have to use the SAProuter to pass a firewall, call the GUI by using the Java runtime environment. In this case, you can specify the required routing string.
Prerequisites Procedure
NOTE
If you want to run the upgrade GUI in accessibility mode, see Using the Accessibility Mode [page 69].
Starting the GUI from the Internet Browser
To start the GUI from a browser, proceed as follows: 1. Enter the following Internet address:
http://<host name>:4239
66/100
PUBLIC
2011-10-20
5 5.4
Upgrade Process Restarting the Upgrade Program
2.
Replace <host name> with the name of the host on which the upgrade program is running. On the following screen, choose Start Frontend.
NOTE
From the same page, you can display the phase list, upgrade documentation, and additional information about the upgrade.
Starting the GUI on Windows Hosts
1.
So that the GUI can also be executed on other hosts, create an upgrade directory on this host and copy the following files to the new directory on the Windows host:
NOTE
You must keep the upgrade directory structure. QZ! <upgrade directory>/sdt/lib QZ! <upgrade directory>/sdt/exe/DSUGui.bat Start the GUI in a command prompt with the command DSUGui.bat.
2.
Starting the GUI on UNIX Hosts
QZ! Starting the GUI on the Host with the Primary Application Server Instance 1. Open a new window as user <sapsid>adm. 2. Start the GUI by executing the script <upgrade directory>/sdt/exe/DSUGui. QZ! Starting the GUI on Other UNIX Hosts 1. So that the GUI can also be used on other hosts, create an upgrade directory on this host and copy the following files to it or mount them with NFS:
NOTE
You must keep the directory structure. QZ! <upgrade directory>/sdt/lib QZ! <upgrade directory>/sdt/exe/DSUGui Start the GUI by executing the script DSUGui.
2.
5.4 Restarting the Upgrade Program

When you restart the upgrade program, it continues at the point where it had stopped. You may need to restart the upgrade program in the following cases: QZ! If an error occurred and an upgrade phase terminated QZ! If a system failure occurred
2011-10-20
PUBLIC
67/100
5 5.5
Upgrade Process Resetting the Upgrade
Prerequisites
If an error occurred, you first have to correct the error. For more information about finding and correcting errors, see the document Troubleshooting [page 16]. If you are not sure how to proceed, contact SAP Support.
Procedure
You can restart the upgrade program by executing the startup script from the upgrade directory:
/usr/sap/<SAPSID>/upg/STARTUP
5.5 Resetting the Upgrade

You can reset the upgrade, that is, undo all changes that have been made in the system by the upgrade program. For example, you may want to reset the upgrade in the following cases: c~hH You want to repeat one of the preparation roadmap steps (steps 1 4) to change an entry. c~hH You ran the preparation roadmap steps for information purposes only and do not want to upgrade the system now, but at a later point in time. c~hH You cannot complete the upgrade in time and therefore need to reset the system to enable production operation again. The procedure for resetting the upgrade depends on the roadmap step the upgrade program has reached.
Procedure
During the Execution of the Preparation Roadmap Steps
As long as the upgrade is in one of the preparation roadmap steps, you can reset a roadmap step by pressing the Back button of the upgrade GUI.
During the Preprocessing Roadmap Step
To reset the upgrade, proceed as follows: 1. Make sure that the upgrade GUI displays the Back and Next buttons, which indicate that SAPup is not in a dialog phase. If it is in a dialog phase, the upgrade GUI displays the Repeat, Init, and Exit buttons. In this case, choose Exit before resetting the upgrade. 2. From the upgrade GUI menu bar, choose Upgrade Reset Upgrade .
NOTE
3.
If you reset the upgrade while the shadow system is running, the shadow system service is not automatically uninstalled. You have to uninstall the shadow system service manually. Otherwise, you are not able to delete the upgrade directory since the service still accesses an executable located in this directory. Stop the SL controller.
68/100
PUBLIC
2011-10-20
5 5.6
Upgrade Process Using the Accessibility Mode
4. 5.
Remove the upgrade directory. Start the upgrade from the beginning.
After Reaching the Execution Roadmap Step NOTE
Before you overwrite or delete the upgrade directory and the /usr/sap/<SAPSID> directory, make a backup of these directories. SAP Support may need this backup to analyze the error.
CAUTION
The time of the backup of the upgrade directory and the /usr/sap/<SAPSID> directory must match the time of the backup of your database. 1. 2. Reset the database, directory /usr/sap/<SAPSID>, and the upgrade directory if it is not part of / usr/sap/<SAPSID>. Use the backup you made before entering the Execution roadmap step. There are two options how to proceed: zf Reset the upgrade completely and repeat all roadmap steps. To do this, choose Upgrade Reset Upgrade from the upgrade GUI menu. zf Continue with roadmap step Execution without repeating the other roadmap steps. You can leave the upgrade in step Preprocessing until you are ready to proceed with the roadmap step Execution.
NOTE
If you want to reset the upgrade after you have upgraded the operating system or database system, you might need to downgrade these software components. For downgrading options, see the vendors specification. The safest method is to reload a full backup of the whole system, including the operating system. Back to Quick Guide [page 19]
5.6 Using the Accessibility Mode

You can run the upgrade program in accessibility mode. This offers the following features: zf Keyboard access zf High-contrast color zf Custom font setting The high-contrast color and custom font setting features are derived from the Windows display properties. Therefore, you can only use these features if you start the upgrade GUI on a Windows host. On this Windows host, you first have to adjust the display properties.
2011-10-20
PUBLIC
69/100
5 5.7
Upgrade Process Advanced GUI Options: Role Management and Alert Function
Procedure
Activating and Adjusting Accessibility Settings on Windows
Activate and adjust the relevant settings for the font size and color schemes as follows: 1. Right click on your Windows desktop and choose Personalize. 2. Select Adjust font size (DPI) and choose Larger scale (120 DPI). To define other font size schemes, choose Custom DPI. 3. In the right-hand pane, select Window Color and Appearance. Select a color scheme from the Color scheme drop-down box. To define your own color schemes, choose Advanced.
Switching On the Accessibility Mode
To switch on the accessibility mode, proceed as follows: _V On the local host: Start the upgrade program as described in Starting the Upgrade Program [page 65] using the command /<DVD mount directory>/STARTUP guimode=accessible. _V On a remote host: _V If you use an Internet browser to start the GUI, you only have to start the upgrade program on the local host in accessibility mode. The GUI on the remote host then automatically starts in accessibility mode. _V If you start the GUI on a Windows host, proceed as described in Starting the Upgrade GUI [page 66] using the command DSUGui.bat accessible. Back to Quick Guide [page 19]
5.7 Advanced GUI Options: Role Management and Alert Function

The upgrade GUI offers advanced options for monitoring your upgrade. Role management allows you to log on to the GUI as the administrator or as an observer. Using the alert function, you can trigger that an e-mail or an SMS is sent when a user action is required or when the upgrade stops because of errors.
Features
Role Management
You can log on to the GUI with the following roles: _V Administrator The administrator is allowed to control the complete process and to make user entries.
70/100
PUBLIC
2011-10-20
5 5.7
Upgrade Process Advanced GUI Options: Role Management and Alert Function
When the GUI starts for the first time, you have to set a password for the administrator. This is initially also the password for the observer. We recommend that you change the observer password immediately after the logon. Only one administrator logon is allowed at a time. - Observer An observer is allowed to view the process, but cannot interact with the GUI. Multiple observer logons are possible concurrently and in parallel to the administrator. To change the password of the administrator or an observer, proceed as follows: 1. Log on with the role Administrator. 2. Choose User Change Password from the menu.
Alert Function
The alert function allows you to configure the program in such a way that you receive an e-mail or SMS notification when a user action is required. To configure the alert function, proceed as follows: 1. Choose Alert Alert Info . 2. Make the required entries:
Field Entry
Program
Absolute path to a program (for example, a script) that triggers the sending of the notification. You have to provide this program yourself.
EXAMPLE
The following is an example of a script that sends an e-mail to a mail-to-SMS gateway, which in turn generates the SMS:
#!/bin/bash
# # Sample script for alert triggering # # Configure mailx to send e-mails #FROM_ADDRESS - indicates the e-mail sender #SUBJECT - subject of the e-mail #EMAIL_ADDRESS - indicates the e-mail receiver #BODY - body of the e-mail #ATTACHED_FILE - file to be attached to e-mail
#FROM_ADDRESS="test@sap.com" #SUBJECT="EHP Installer Alert" #EMAIL_ADDRESS="cellphonenumber@T-D1-SMS.de" #BODY="EHP Installer cannot continue" #ATTACHED_FILE="Alert.txt
#If you want to send an e-mail, use the following command:

#echo "$BODY" | mailx -r "$FROM_ADDRESS" -s "$SUBJECT" "$EMAIL_ADDRESS"
#If you want to attach the file with the alert message, specify the path to the alert file. #The absolute path to the alert file should be the same as in the alert view.
2011-10-20
PUBLIC
71/100
5 5.8
Upgrade Process Importing or Installing Software After Starting the Upgrade Field Entry
#cat "$ATTACHED_FILE" | mailx -r "$FROM_ADDRESS" -s "$SUBJECT" "$EMAIL_ADDRESS"
Alert File Alert Delay (in seconds) Set active (check box)
Absolute path to the alert file that stores the alert message Time delay between the event and the sending of the notification Activates the alert function
3. Choose OK to save your entries. 4. To test the alert function, choose Test. To reset all fields to their initial state, choose Clear. Back to Quick Guide [page 19]
5.8 Importing or Installing Software After Starting the Upgrade

After you have started the upgrade, you may need to import software, for example SAP Support Packages.
Procedure
1.
Reset the upgrade [page 68] if you have already reached the Preprocessing roadmap step. If you are still in the previous roadmap step, a reset is not needed. 2. Import or install the required software. 3. Start the upgrade again from the DVD [page 65] and repeat the preparation roadmap steps. Back to Quick Guide [page 19]
5.9 Making Entries for the Configuration Roadmap Step

This roadmap step asks for all information required to run the upgrade. For clarity, this section is divided into the following subsections: eIO2 Making Basic Entries for the Java System Upgrade [page 72] eIO2 Making Entries for the Target System Configuration [page 74] eIO2 Providing the JCE Jurisdiction Policy Files for Adobe Document Services [page 75] Back to Quick Guide [page 19]
5.9.1 Making Basic Entries for the Java System Upgrade

Procedure
1.
Include the correction package in the upgrade. The correction package provides the latest corrections for the upgrade program. Proceed as follows:
72/100
PUBLIC
2011-10-20
5 5.9
Upgrade Process Making Entries for the Configuration Roadmap Step
2.
3.
4.
5. 6.
Make sure that you have the latest version of the correction package. You can download the correction package from SAP Service Marketplace at http://service.sap.com/swdc Download Support Packages and Patches Entry by Application Group Additional Components Upgrade Tools CORRECTIONS FOR UPGRADE CORRECTIONS FOR UPGRADE 7.3 #OS independent . 2. Copy the package to your upgrade directory. 3. Choose Continue. The upgrade program extracts the package. To do this, it exits and restarts itself. Enter the keyword that is specified in the current product-specific Upgrade Note. You can find the number of the Upgrade Note in section SAP Notes for the Upgrade [page 13]. The keyword and the correction package belong together and are updated at the same time. An error can occur if the correction package is out-of-date. In this case, download the most recent correction package from SAP Service Marketplace. Proceed as follows: 1. To cancel the phase, choose Cancel and then exit the upgrade program. 2. Download the latest correction package from SAP Service Marketplace to the upgrade directory. 3. Restart the upgrade program. Enter the Solution Manager key. You must generate the key in the Solution Manager. You can only proceed with the upgrade if you have entered the key. Enter the passwords for the system users. The AS Java Administrator is the user with which you log in to the system. SAPService<SID> is the user with which the SAP system performs its operating system-specific actions. If you are upgrading a high availability system [page 36], enter the path to the central file share. Enter the parameters of the shadow system. The SCS and CI instances require instance numbers as technical identifiers for internal processes.
CAUTION
1.
You must not use these instance numbers anywhere else in your system landscape. 7.
0)iuT+c oeVlu\c&"$)Som/
Specify the following parameters when prompted in phase DBA_USER_DB2: User ID and password of the database administrator Shadow schema For information about important preparation activities for these parameters, see section Upgrade of the Operating System and Database System: Overview [page 43].
:)au+C e)V(lu\p
8.
Specify the system type.
2011-10-20
PUBLIC
73/100
5 5.9
If your system is controlled by SAP NetWeaver Development Infrastructure [page 35], the upgrade program treats it differently from other systems. You then have to provide some further information for the upgrade program. 9. A summary of all system parameters that have been detected is displayed. Choose Continue or cancel the phase and exit the program. 10. Enter the paths to all required upgrade DVDs. @Y2 If you have access to one DVD drive only, you have to insert the DVDs one after the other: 1. Insert the first DVD. 2. Enter the mount point. 3. Choose Continue to start the DVD extraction. 4. Repeat this process until the lower table on the dialog screen displays the status Extracted for all DVD subdirectories. @Y2 If you have multiple DVD drives, you can insert all DVDs and enter the mount points at once. The upgrade program extracts the contents into <upgrade directory>/java/data/archives. 11. @9|99N`c i{VtfhO Enter the password of the database system user. This user has the right to create and delete other users, for example, the system user.
@3|9vNpcM
il)
5.9.2 Making Entries for the Target System Configuration

The Configuration module enables you to specify the composition of the target release system.
Procedure
1.
Decide which Support Packages you want to include into the upgrade. Support Packages that are available in the EPS inbox (/usr/sap/trans/EPS/in) of your transport directory are displayed on the dialog screen. Specify the Support Package level for each target release component.
NOTE
Support Package levels are always the same for AS ABAP and AS Java. You can put further Support Packages into the EPS inbox and then display them by choosing Rescan.
NOTE
The upgrade program only displays Support Packages in the following cases: @Y2 For components already installed on the source release: The Support Packages in the EPS inbox must be newer than those currently installed in your system. @Y2 For components that are installed as part of the upgrade procedure:
74/100
PUBLIC
2011-10-20
5 5.9
The Support Packages in the EPS inbox must be newer than those that are included on the upgrade DVD. 2. Decide how you want to handle the components during the upgrade. The screen displays all components that are involved in the upgrade, either because they have been detected on the source release system or because they belong to the target release shipment. The following information is displayed for each component: Y: Vendor Y: Component Name Y: Release Y: Support Package Level Y: Patch Level Y: Operation In the Operation column, you can find the action that the upgrade program performs for the component as a next step. The operation types are set automatically by the upgrade program. You can only decide on the components for which Scan inbox is specified as operation. The following operation types exist: Y: Scan inbox - assigned to components for which the upgrade program cannot find any successor, such as customer developments, add-ons, or third-party software. You must provide a valid update for the components in the inbox. Proceed as follows: 1. Provide a deployment archive (for example, an SCA file) with the target release version of the component or with a version that is fully compatible with the target release, in your EPS inbox. 2. Select Rebuild component list after scanning inbox at the bottom of the screen. 3. Choose Continue. Y: Deploy - the normal upgrade operation. Y: Remove - applies to those components that no longer exist in the new release or that have been renamed. A component no longer exists after the upgrade either because it has been deleted, or because it has been integrated into some other component. 3. To proceed with the upgrade program, confirm the list of components. Back to Quick Guide [page 19]
5.9.3 Providing the JCE Jurisdiction Policy Files for Adobe Document Services
If you are upgrading Adobe Document Services (ADS), you must provide the unlimited strength version of the Java Cryptography Extension Policy files. SAPJup checks if the files are present on your system and if their version is compatible with the JVM version. If SAPJup does not find a compatible version of the files, it displays a dialog where you must browse to the files.
2011-10-20
PUBLIC
75/100
5 5.10
Upgrade Process Making Entries for the Checks Roadmap Step
Procedure
If the JCE Policy Files Location dialog appears, proceed as follows: 1. Choose the Browse button and browse to the location of the files. 2. After you are done, choose Continue to continue with the upgrade process. Back to Quick Guide [page 19]
5.10 Making Entries for the Checks Roadmap Step

Procedure
Checking the Results of the System Check
At the end of the Checks roadmap step, the SDTExecution Intervention window displays the results of the system check. The entries can be error messages, information, or prompts for user actions. You have to carry out the user actions before you can start with the Preprocessing roadmap step. Back to Quick Guide [page 19]
5.11 Phase BEGIN_DOWNTIME_<XX>

Procedure
Before the downtime begins, perform the following actions: 1. Make sure that you can recover your SAP system after errors have occurred: b_ Back up your database as described in your database manual. b_ Back up the directory /usr/sap/<SAPSID> including the upgrade directory. In case of problems during the downtime, for example, a hardware failure, you need the backup of the directories to reset the SAP system to the current state. The directories include, amongst others, profiles, trace files, and files for the SAP kernel needed for a reset of the SAP system.
NOTE
If the upgrade directory is not part of directory /usr/sap/<SAPSID>, make a separate backup of the complete directory including the subdirectory sdt.
NOTE
2.
Back up the home directory of user <sapsid>adm. If you need to reset the upgrade and problems occur when starting and stopping the SAP system, you may need to use the old user profiles contained in this directory. Uninstall all additional application server instances. To uninstall the additional application server instances, proceed as described in the installation guide for your source release. If you want to use the profiles of the additional application server instances to adapt the profiles of the target system, save them before you uninstall the additional application server instances.
76/100
PUBLIC
2011-10-20
5 5.12
Upgrade Process Phase DOWNTIME_END_<XX> RECOMMENDATION
3. 4.
We recommend that you do not back up the profiles of the additional application server instances in the profile directory. The profile directory must only contain active profile files. Stop the SDM GUI now at the latest. Stop jcmon and all other standalone monitoring tools.
5.12 Phase DOWNTIME_END_<XX>

Procedure
1.
At the end of the downtime, create the following backups: 6 A backup of your database as described in your database manual 6 A backup of the upgrade directory
5.13 Evaluating the Upgrade Runtime

Our aim is to provide you with a fast and efficient upgrade procedure. At the end of the Postprocessing roadmap step, the upgrade program extracts statistical data and evaluates the upgrade, for example, calculates the runtimes of the individual phases. Evaluating this information helps us to improve both the current upgrade procedure and new upgrades. We would also appreciate feedback on your experience with the SAP system upgrade. Therefore, we have designed the SAP System Upgrade Evaluation. It contains the following: 6 Upgrade Evaluation Form This form consists of a simple questionnaire on your experiences with the upgrade and an upgrade log file generated by the upgrade program.
NOTE
Your feedback from the Upgrade Evaluation Form is mainly used to identify areas in need of improvement. If you have specific questions on the upgrade and need an answer soon, open a customer message in SAP Support Portal (http://service.sap.com/support). 6 Upgrade Information Using the corresponding link in the text, you can open the file UpgAnalysis.html. It is designed to help you evaluate your upgrade and to better plan follow-up upgrades. It contains detailed information about the system, the overall upgrade and the individual phases. The SAP System Upgrade Evaluation is displayed automatically in a browser window.
2011-10-20
PUBLIC
77/100
5 5.13
Upgrade Process Evaluating the Upgrade Runtime
Prerequisites
`yPQ A browser has been installed on the machine from which you are monitoring the upgrade.
NOTE
Not all browsers are able to send the form. `yPQ The machine has an e-mail connection. `yPQ The upgrade has finished.
Procedure
To send the Upgrade Evaluation Form to SAP, proceed as follows: 1. At the end of the Postprocessing roadmap step, a browser window appears displaying the SAP System Upgrade Evaluation. 2. Answer the questions under Upgrade Evaluation Form.
NOTE
3.
Answering the questions is optional. Choose Send to SAP. This submits the Upgrade Evaluation Form to SAP.
NOTE
After the upgrade has finished, you can return to the SAP System Upgrade Evaluation by entering the following path: http://<host name>:4239 Upgrade Evaluation Back to Quick Guide [page 19]
78/100
PUBLIC
2011-10-20
Follow-Up Activities
6 Follow-Up Activities
This part of the document contains information about the follow-up activities that you need to perform after you have upgraded your SAP system. When you perform follow-up activities, note the following information (in addition to the information in Quick Guide [page 19]): v J Perform the actions described in Quick Guide [page 19] in the specified order. The follow-up activities are divided into three blocks: v J Actions needed before resuming production operation These actions ensure that all the processes that are relevant to system operation are available again. You can start these actions while the upgrade program is finishing the upgrade. v J Actions during limited production operation During this time, your SAP system is already consistent and all the processes that are relevant to system operation are available. However, this system state does not yet contain measures for optimizing performance, or actions for resuming standard operation. Check the actions that are listed in this block and if necessary, perform them before you restart production operation. v J Actions during production operation You can also perform these actions when the system is back to production operation. Actions You must perform the following actions before you resume production operation of your system: v J Performing Follow-Up Activities for User root [page 80] v J PCK: Using a Wizard for Automated Processing of Selected Follow-Up Activities [page 81] v J PCK: Performing Follow-Up Activities for PCK [page 82] v J PI: Assigning PCK User Roles [page 82] v J PI-AF: Creating a JCo Destination for the ExchangeProfile [page 83] v J Performing Follow-Up Activities for the System Landscape Directory [page 83] v J Configuring SAP Start Service [page 84] v J v J v J v J v J
voBO[MWS)63D_@caHenV]8zoCm =>uyl
PI: Migrating Java Proxy-Based Applications [page 84]

voBO[GSe|DZ@iaQcoV]
òC
Performing Follow-Up Activities in the Monitoring Area [page 86] Performing Application-Specific Activities [page 87] Performing Follow-Up Activities for SAP Solution Manager [page 87] Changing Passwords [page 88]
2011-10-20
PUBLIC
79/100
6 6.1
Follow-Up Activities Performing Follow-Up Activities for User root

J@KU?V+~npy#Y]re!#'9gLWkjd}m[Y6OEN
J
Performing Follow-Up Activities for the Composite Application Framework [page 89]
JJUpV;%npQsY]tezX<'9]LJcj}
J Performing Follow-up Activities for Application Migration [page 90] J Performing Follow-up Activities for NetWeaver Development Infrastructure (NWDI) [page 90] J J@KU?V+~npy#Y]re!#'9gLWkjd}m[Y6OEN Performing Follow-Up Activities for Adobe Document Services [page 90]
JJUpV;%npQsY]tezX<'9]LJcj}
J J J J J
J@KU?V+~npy#Y]re!6'9bLVkj`}l[YlOuORjoR
DI: Checking CBS Service Properties [page 91]

JJUpV;%npTuY]qekA='9GLK9js}z[Y6O_N J@KU?V+~npy#Y]re!<'9mLT*j!}L[YNOXORjN$RTAT*r(g| B(ka*C')Q*3%gbi^T+CuF=)u}!Gjm7&Ec[~4WP[
PI: Adjusting the Adapter Configuration [page 92]

JJUpV;%npCvY]~e;~?'9}LkjV}z[YhOdG_OjjR8
r("@ XBPk(ka;O'XQZ3-bid^Tf(uF&/t}uGjUm7:& J@KU?V+~npy#Y]re!'9oL
BI Java: Performing Follow-Up Activities for Business Intelligence [page 92]

JJUpV;%npR#Y]|ez J@KU?V+~npy#Y]re!='9|L]jm}?[Y[O?
EP: Checking the KMC Installation [page 93]

JJUpV;%npUwY]oeiE6'9aLjC J@KU?V+~npy#Y]re!='9|L]jm}?[Y[O?
EP: Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC) [page 95]
JJUpV;%npUwY]oeiE6'9aLjC
You can perform the following actions during limited production operation of your system: J Installing the SAP Online Documentation [page 97] J Installing Additional Application Server Instances [page 97] Back to Quick Guide [page 19]
6.1 Performing Follow-Up Activities for User root

After the upgrade, you need to make a number of adjustments. To do this, you need the authorizations of the user root.
NOTE
The Unix commands chown and chmod below are used to provide root permissions to the icmbnd executable. Root permissions are only required for binding ports with port numbers smaller than 1024. If no ICM server ports have been configured to use port numbers smaller than 1024 we recommend that you do not execute the chown and chmod commands. The ICM server ports are configured in the profile parameter icm/server_port_<n> which is contained in the instance profile or default profile.
Procedure
Proceed as follows:
80/100
PUBLIC
2011-10-20
6 6.2
Follow-Up Activities PCK: Using a Wizard for Automated Processing of Selected Follow-Up Activities
1. 2.
Log on as user <sapsid>adm. Execute the following commands:

su - root
zE
Cw8mB1Wi #q.dCg#
cd <upgrade directory>/data/kernel
zEw(m}q(%4q
zE
Cw8mB1Wi #q.dCg#
./oraroot.sh <SAPSID>
zEw(m}q(%4q
zE
Cw8mB1Wi #q.dCg#
If you have an MCOD system and/or the database name does not correspond to the SAP system name, use the following command to run oraroot.sh:
zEw(m}q(%4q
zE
Cw8mB1Wi #q.dCg#
./oraroot.sh <SAPSID> <DBSID>
zEw(m}q(%4q
cd /sapmnt/<SAPSID>/exe/(n)uc/<platform> cp -p ./icmbnd.new ./icmbnd
zE
Cw8mB1Wi #q.<d
In the AIX operating system use the following command to create the new directory: cp
icmbnd.new
zEw(m}
-p icmbnd
chown root:sapsys icmbnd chmod 4750 icmbnd exit
3.
Start the system with stopsap and startsap.
6.2 PCK: Using a Wizard for Automated Processing of Selected Follow-Up Activities
You can use a configuration wizard to automate the following follow-up activities after you have performed the upgrade:
zF PCK: Performing Follow-Up Activities for PCK [page 82]
zF PI: Assigning PCK User Roles [page 82]
zF PI-AF: Creating a JCo Destination for the ExchangeProfile [page 83] If you cannot run these steps automatically, you have to perform them manually. To operate the wizard, perform the following steps:
2011-10-20
PUBLIC
81/100
6 6.2
Follow-Up Activities PCK: Using a Wizard for Automated Processing of Selected Follow-Up Activities
1. 2. 3. 4. 5.
To start SAP NetWeaver Administrator, go to http://<host>:<port>/nwa. Log on with your JEE administrator user. Choose Configuration Scenarios Configuration Wizard. From Automation Tasks, choose All Configuration Tasks (dropdown box). Select PI PCK Upgrade for PCK upgrade or Adapter Engine Upgrade for the Adapter Framework and choose Start. If you want to repeat the upgrade process, choose Re-execute. 6. When prompted by the wizard, provide the required entries (users and passwords). The follow-up steps are then processed automatically. For more information, see SAP Notes 1439558 and 1519075.
6.2.1 PCK: Performing Follow-Up Activities for PCK

Procedure
After you have upgraded the Partner Connectivity Kit (PCK) to the target release, you must perform certain configuration steps. For information about the necessary configuration steps, see SAP Note 746328. Back to Quick Guide [page 19]
lHq($ s0g8;S3j|tN<a4|*s3<.zsPU9&@%VnmJ_|YtP6JiFtew)GA$+0xO&=<W3B)XVY
.
6.2.2 PI: Assigning PCK User Roles

Before you can log on to SAP PCK, you have to assign additional roles to the users pckuser and pckreceiver.
Procedure
1. 2.
Log on to the user management as user Administrator by entering the URL http:// <host>:<port> and choosing User Management. Select the user pckuser and assign the following roles to this user: lHT& SAP_XI_PCK_ADMIN lHT& SAP_XI_PCK_CONFIG lHT& SAP_XI_PCK_MONITOR Select the user pckreceiver and assign the following role to this user: SAP_XI_PCK_COMMUNICATION If you had created further configuration or monitoring users in 6.40, also assign the above roles to them. Save your settings.
3. 4. 5.
lHq(I$ (0]8;G3p|tM,r4|*s\z PU9y@%VInvX_|Yt-~6iFo^tpew)GZ&90,O&=yWL3`j
82/100
PUBLIC
2011-10-20
6 6.3
Follow-Up Activities Performing Follow-Up Activities for the System Landscape Directory
6.2.3 PI-AF: Creating a JCo Destination for the ExchangeProfile

NOTE
If you used the PI-specific configuration wizard to automate a number of certain follow-up activities, yo do not need to perform this follow-up step. It has been covered by the wizard. The Adapter Engine uses a Java RFC destination "XI_EXCHANGE_PROFILE" to connect to the Exchange Profile. To create this destination, proceed as follows:
Procedure
1. 2. 3. 4.
In the SAP NetWeaver Administrator, go to Configuration Connectivity Destinations . Create a new destination of type RFC with the name XI_EXCHANGE_PROFILE. Enter the connection data for the server where your ExchangeProfile is stored (usually the PI Integration Server). (Optional) To make the communication more secure, you can configure the destination to use SNC.
6.3 Performing Follow-Up Activities for the System Landscape Directory

NlPE7hI{$GpmQDEX
JQS6QVIE<sy1<b?Q'IR@
NOTE
If you used the PI-specific configuration wizard to automate a number of certain follow-up activities, yo do not need to perform this follow-up step. It has been covered by the wizard.
NfPE7hI{&2GzlQDEX
HQS$QVI_^sQ$
The follow-up activities that you have to perform for the System Landscape Directory (SLD) depend on the situation in your source release system, that is, whether the SLD was configured or not.
Procedure
N If the SLD was configured in your source release system, you must perform the following actions to enable the use of the SLD in your upgraded system: N Configure the user management Define security roles and assign users to these roles. Proceed as described in the SAP Library [page 16] for your target release at: SAP NetWeaver Library Administrator's Guide SAP NetWeaver Security Guide Security Aspects for Lifecycle Management Security Guide for the System Landscape Directory Configuring SLD Security Roles N Update the SLD content and data model
2011-10-20
PUBLIC
83/100
6 6.4
Follow-Up Activities Configuring SAP Start Service
We recommend that you download the latest SLD content from SAP Service Marketplace and import it into the SLD. For more information, see SAP Note 669669. G9 If the SLD was not configured in your source release system but you want to use it in your target release system, proceed as described in the SAP Library [page 16] for your target release at: SAP NetWeaver Library Function-Oriented View Solution Life Cycle Management Configuring, Working with and Administering System Landscape Directory Administering the SLD In either situation, you also need to configure the following SLD components: G9 SLD Data Supplier Proceed as described in the SAP Library [page 16] for your target release at: SAP NetWeaver Library Function-Oriented View Application Server Infrastructure Configuring, Working with and Administering System Landscape Directory Configuring Systems to Connect to the SLD GV For AS ABAP systems: Connecting AS ABAP Systems to the SLD Setting Up the SLD Data Supplier for AS ABAP Based Systems GV For AS Java systems: Connecting AS Java Systems to the SLD Setting Up the SLD Data Supplier for AS Java Based Systems G9 SLD Client Proceed as described in the SAP Library [page 16] for your target release at: SAP NetWeaver Library Function-Oriented View Application Server Infrastructure Configuring, Working with and Administering System Landscape Directory Configuring Systems to Connect to the SLD Connecting AS Java Systems to the SLD Configuring the SLD Client Back to Quick Guide [page 19]
6.4 Configuring SAP Start Service

The upgrade does not configure the SAP start service (sapstartsrv) to automatically start as a daemon when you start the operating system. If you want to set up the automatic start, you need to perform some manual actions.
Procedure
For information about how to set up the automatic start of the SAP start service during the operating system startup, see SAP Note 823941.
GVt5FI
P]sxw;>b4xlIQljwY^N/7\_L*mjPO=jo[6{p4bol
T}rJ]&
6.5 PI: Migrating Java Proxy-Based Applications

You have built applications using Java Proxies that have been generated in SAP XI 3.0. To enable your applications to run after the upgrade, you have to adapt some references inside the applications.
84/100
PUBLIC
2011-10-20
6 6.6
Follow-Up Activities SAP MaxDB: Backing Up the Database
Procedure
1.
Open the application-j2ee-engine.xml file, which is included in your application EAR file, and change the following references : c* The AS Java library com.sap.aii.proxy.runtime This library has been replaced by the service com.sap.aii.proxy.svc. Adapt the reference as follows:
<reference reference-type="weak"> <reference-target provider-name="sap.com" targettype="service">com.sap.aii.proxy.svc </reference-target> </reference>
c* The AS Java library com.sap.aii.messaging.runtime The library has been replaced by the library com.sap.aii.af.sdk.lib. Adapt the reference as follows:
<reference reference-type="weak"> <reference-target provider-name="sap.com" targettype="library">com.sap.aii.af.sdk.lib </reference-target> </reference>
2. Deploy the EAR files in your SAP NetWeaver 7.3 environment. Back to Quick Guide [page 19]
cZf
x[~<LoEw/e<'N8oUGhE^_Rc hqo %>ztU7(/SAI S+Gz cZf!K~pLoNwT;e<'}N8^G4
6.6 SAP MaxDB: Backing Up the Database

Prerequisites
You have not yet resumed production operation of the SAP system.
Procedure
1.
Stop the SAP system as user <sapsid>adm with the following command:
stopsap r3 DVEBMGS<instance number>
Assign the database parameters to the value they had before the upgrade.
CAUTION
2.
The database parameters only become active when the database has been stopped and started. Make the database capable of being recovered again. This step depends on whether archiving is switched on or off: c* Archiving switched off
2011-10-20
PUBLIC
85/100
6 6.7
Follow-Up Activities Performing Follow-Up Activities in the Monitoring Area
3.
Since the log mode is reset to the original value after the upgrade, you must back up the database completely in operating mode ADMIN before you can start production operation again. You can only continue the upgrade in operating mode ONLINE. 1 Archiving switched on We recommend that you make a full backup so that you do not have to restore all the logs again if you need to recover the database. You can make an incremental online backup instead of a full backup. However, we recommend that you make a full backup as soon as possible after the incremental backup. Start the SAP system as user <sapsid>adm with:
startsap r3 DVEBMGS<instance number>

$n<I
O#Cp
6.7 Performing Follow-Up Activities in the Monitoring Area

Procedure
Installing and Upgrading Package SAPHOSTAGENT
Package SAPHOSTAGENT contains all components needed to monitor a host centrally. One of these components is saposcol. As of SAP NetWeaver 7.1, the package SAPHOSTAGENT is part of the SAP Kernel DVD. If your SAP system has an installed version of the SAPHOSTAGENT, the upgrade program performs an upgrade of the SAPHOSTAGENT at the end of the Extraction roadmap step. For more information about the upgrade of SAPHOSTAGENT, see the following log files: 1 1 1
UPDATE_SAPHOSTAGENT_<xx>.LOG UPDATE_SAPHOSTAGENT_<xx>.ERR UPDATE_SAPHOSTAGENT_<xx>.OUT NOTE
The upgrade program does not perform the upgrade of SAPHOSTAGENT automatically in the following cases: 1 Your SAP system has no SAPHOSTAGENT installed. 1 Your SAP system has saposcol only. In these cases, you need to install the package SAPHOSTAGENT manually. Proceed as described in SAP Note 1031096 or in the SAP Library [page 16] for your target release at: SAP NetWeaver Library Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Monitoring in the CCMS Infrastructure of the NetWeaver Management Agents Downloading and Installing Package SAPHOSTAGENT Back to Quick Guide [page 19]
86/100
PUBLIC
2011-10-20
6 6.8
Follow-Up Activities Performing Application-Specific Activities
6.8 Performing Application-Specific Activities

Procedure
Some applications require you to perform application-specific follow-up activities, without which the applications cannot run. These application-specific activities are described in the Release Notes for the particular application. The Release Notes are available on SAP Service Marketplace at http://service.sap.com/ releasenotes. Back to Quick Guide [page 19]
6.9 Performing Follow-Up Activities for SAP Solution Manager

To connect the newly upgraded system to SAP Solution Manager, you need to perform the following activities: b|// Make sure that the data is up-to-date in the SAP Solution Manager system. b|// Configure the diagnostics capabilities and the Wily Introscope Agent. b|// If required, update the product version of the system where the Integration Server is installed.
Procedure
Checking System Data In the System Landscape Directory (SLD), check whether the system landscape is up-to-date. To do this, check whether the newest software component versions are assigned to the relevant technical systems in your system landscape. After having verified that the system information in the SLD is upto-date, the system needs some time (up to 24 hours) to also update the system information in SAP Solution Manager. Updating the System Data in SAP Solution Manager After updating your system, you need to make sure that the correct product version is assigned to the system in SAP Solution Manager. For more information, see the SAP Library at: b|// http://help.sap.com SAP Solution Manager SAP Enhancement Package 1 for SAP Solution Manager 7.0 Basic Settings Solution Manager System Landscape Inconsistencies in the System Landscape Clean-up Inconsistent Systems Read section Case B2: The product version and the product have changed; the system is used. b|// http://help.sap.com SAP Solution Manager SAP Enhancement Package 1 for SAP Solution Manager 7.0 Basic Settings Solution Manager System Landscape Create Systems Assign a System to a Product/Change Product Version Configuring Diagnostics Capabilities and Wily Introscope Agent 1. Start SAP Solution Manager.
2011-10-20
PUBLIC
87/100
6 6.10
Follow-Up Activities Changing Passwords
2. Call transaction SOLMAN_SETUP. 3. On page SAP Solution Manager: Overview, choose Managed System Configuration. 4. Select the system where the Integration Server is installed. 5. On page Managed System Configuration in the process diagram, choose Diagnostics Configuration. 6. In row Configure Diagnostics, choose Select URL. 7. On page Managed System Configuration in the process diagram, choose Wily Introscope Configuration. 8. In row Configure Wily Introscope Agent, choose Select URL 9. Under Introscope Agent, choose Setup Introscope Agent. For more information about Wily Introscope Agent, see SAP Service Marketplace at http:// service.sap.com/diagnostics. Assigning the Up-to-Date Product Version 1. In transaction SOLMAN_SETUP, on page SAP Solution Manager: Overview, choose Managed System Configuration. 2. On page Managed System Configuration, check the product version of the system. If you have already performed the steps described in Performing Follow-Up Activities for the System Landscape Directory [page 83], the product version should be updated and corresponds to the target release of the upgrade. 3. If an old product version is still displayed, on page Managed System Configuration in the process diagram, select Create Logical Components. 4. In field Product Version, choose the product version that corresponds to the target release of the upgrade by using the input help. For more information, see the SAP Library at: http://help.sap.com SAP Solution Manager SAP Enhancement Package 1 for SAP Solution Manager 7.0 Basic Settings Solution Manager System Landscape Create Systems Assign a System to a Product/Change Product Version Back to Quick Guide [page 19]
6.10 Changing Passwords

As of SAP NetWeaver 7.0 Support Package 03, new security policies apply. You have to change passwords in the following cases: Z Your passwords are older than 90 days. Z Your passwords do not contain between six and twelve characters and do not consist of both letters and numerals. Z Your password contains a user name. When you create a new password, you are not allowed to duplicate the old password. If you change the AS Java administrator password, you have to make sure that external tools (for example, SDM and JSPM) can read the password. These tools read the administrator password from
88/100
PUBLIC
2011-10-20
6 6.11
Follow-Up Activities Performing Follow-Up Activities for the Composite Application Framework Core (CAF Core)
the secure store. Since the secure store is not automatically updated, you have to do this manually. Proceed as follows:
Procedure
1.
Start the Config
Tool by executing the configtool script file in /usr/sap/<SAPSID>/
<instance_name>/j2ee/configtool/.
2. Select secure store. 3. Select the admin/password/<SAPSID> entry. 4. In the Value field, enter the new password for the AS Java administrator and choose Add. 5. To save the data, choose File Apply . 6. Restart the system. Back to Quick Guide [page 19]
6W[jO]bACb[$#k/@*2Q)F=wjt^B 68A:
6.11 Performing Follow-Up Activities for the Composite Application Framework Core (CAF Core)
Procedure
Depending on whether CAF Core has been configured in the source release or not, perform the following actions: CAF Core has not been configured in the source release If the Composite Application Framework has not been configured in the source release, but you want to use it in production operation in the upgraded system, you must configure it as described in the following documentation: Installation Guide - SAP NetWeaver 2004s SR2 on <Operating System>: <Database>, section Performing Post-Installation Steps for Composite Application Framework (CAF Core) Online documentation at http://help.sap.com/nw70 SAP NetWeaver Library Developing, Configuring and Adapting Applications Creating Composite Applications CAF Core has been configured in the source release The configuration is retained during the upgrade. You only have to create the roles CAFAdmin and CAFUIAdmin manually after the upgrade. For information about how to create these roles, see the online documentation at http://help.sap.com/nw70 SAP NetWeaver Library Developing, Configuring and Adapting Applications Creating Composite Applications Composite Application Framework Core Configuration Guide .
<W[j0JId[$#?@4~Q)D=wj
2011-10-20
PUBLIC
89/100
6 6.12
Follow-Up Activities Performing Follow-up Activities for Application Migration
6.12 Performing Follow-up Activities for Application Migration

Having completed the upgrade of your SAP NetWeaver runtime, you may also want to migrate the application sources. This is required in case you want to continue developing the application with the newer version of SAP NetWeaver. The migration of the application source code is done using the application projects migration wizard of the SAP NetWeaver Developer Studio. For more information, see Migrating Application Projects from SAP NetWeaver 7.0 to a Higher SAP NetWeaver Version at http:// help.sap.com/saphelp_nw73/helpdata/en/48/257A6542AC539AE10000000A421937/frameset.htm.
6.13 Performing Follow-up Activities for NetWeaver Development Infrastructure (NWDI)

Checking the Default Users
After the upgrade, check if the following users are of type Technical User: NWDI_ADM, NWDI_DEV and NWDI_CMSADM. If these users are of a different type, use the user management tools of AS Java to make them of type Technical User.
Assigning Security Roles
After the upgrade, some of the NWDI technical users may not have the necessary authorizations to work properly. To fix this problem, you must assign additional roles to the groups NWDI.Administrators and NWDI.Developers as follows: kb Assign the role SAP_SLD_ORGANIZER to the group NWDI.Administrators so that the technical user NWDI_CMSADM can work properly. kb Assign the roles SAP_DI_DEVELOPER and SAP_SLD_DEVELOPER to the group NWDI.Developers so that the user NWDI_DEV can work properly.
kuG~k| _5mi(H:_t{d_H>*XHO}t[Gy
6.14 Performing Follow-Up Activities for Adobe Document Services

To use Adobe Document Services after the upgrade, you must perform certain follow-up activities. The follow-up activities mainly depend on the situation in your source release, that is whether ADS was configured in your source release or not. The Adobe Document Services Configuration Guide for SAP NetWeaver 7.0 (2004s) is available at the following locations: kb On SAP Service Marketplace at http://service.sap.com/adobe Interactive Forms Based on Adobe Software Media Library Documentation Adobe Document Services - Configuration Guide NW 7.0 (2004s)
90/100
PUBLIC
2011-10-20
6 6.15
Follow-Up Activities DI: Checking the CBS Service Properties
^
t In SAP Library at http://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant's Guide Additional Cross-NetWeaver Configurations Adobe Document Services - Configuration
Procedure
^
t ADS was not configured in your source release Perform the complete ADS configuration as described in the Adobe Document Services Configuration Guide. ^
t ADS was configured in SAP NetWeaver 2004 Perform the following configuration steps: ^
ty Create a new http destination to SAP NetWeaver Application Server with the name FP_ICF_DATA_<SID>. For detailed information about the procedure, see the document Adobe Document Services Configuration Guide, section Configuring the Web Service Securing Access to the Web Service Configuration of the Web Service for Basic Authentication Creating or Changing the Destination Service . ^
ty If you want to use Secure Socket Layer (SSL), perform the configuration steps as described in the document Adobe Document Services Configuration Guide, section Configuring the Web Service Securing Access to the Web Service Configuration of the Web Service SSL Connection . ^
ty Support Package 11 or lower only Delete the credentials for interactive forms and create them again. For detailed information about the procedure, see the document Adobe Document Services Configuration Guide, section Installing and Configuring Credentials.
^QC<'jby?>hR;^K'Qe>R\ ^QK<'jvSy?>hX;^t-
Q ejR'\zNx\O n,p!}
6.15 DI: Checking the CBS Service Properties

Procedure
After the upgrade you must check, whether the following three CBS service properties are still valid and suitable for the content you want to build: ^
t JDK_HOME_PATHS ^
t BUILD_TOOL_JDK_HOME ^
t BUILD_TOOL_VM_ARGS For information about configuring CBS, see the SAP NetWeaver online documentation at http:// help.sap.com SAP NetWeaver SAP NetWeaver <Release> SAP NetWeaver Library SAP NetWeaver by Key Capability SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Using the Development and Production Infrastructure Development Infrastructure Tasks Central Development with NWDI Working with the Build Environment . For information about the CBS service properties, see the SAP NetWeaver online documentation at http://help.sap.com SAP NetWeaver SAP NetWeaver <Release> SAP NetWeaver Library SAP
2011-10-20
PUBLIC
91/100
6 6.16
Follow-Up Activities PI: Adjusting the Adapter Configuration
NetWeaver by Key Capability SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Using the Development and Production Infrastructure Development Infrastructure Tasks Central Development with NWDI Working with the Build Environment Configuring the System for the CBS CBS Service Properties .
(1;k0/vZ~J|xg~jFHa>6T5VW#>}U)xIN)V (1;c0E/9J~g|y gc'pHa>dTHVH0>)U )|xIN}ju4^we%YB"V
{T8.%sSpK5`_v#m<!N+A\Chb_{o?hKP -SqVwoE(
onJ3eIb\
6.16 PI: Adjusting the Adapter Configuration

You have used the classes com.sap.aii.messaging.adapter.Conversion or com.sap.aii.messaging.adapter.XSLTConversion in one of the following cases: (1\& To configure the module AF_Modules/MessageTransformBean in an adapter configuration of your Advanced Adapter Engine (1\& To configure a dispatcher in an adapter configuration of your Adapter Engine (Java SE) After the upgrade, you have to adjust the configurations to make the scenarios work properly again.
Procedure
Change the following: (1\& Instead of com.sap.aii.messaging.adapter.Conversion, use com.sap.aii.af.sdk.xi.adapter.Conversion. (1\& Instead of com.sap.aii.messaging.adapter.XSLTConversion, use com.sap.aii.af.sdk.xi.adapter.XSLTConversion. For more information, see the SAP Library [page 16] at: SAP NetWeaver Process Integration Library Function-Oriented View Process Integration Integration Directory Define Collaboration Profiles Defining Communication Channels Adding Modules to the Module Processor Inserting MessageTransformBean in Module Processor Back to Quick Guide [page 19]
(1;k0/vZ~]|rgtUFHa>wTHzVw>4lU)ZxIN?u4ê%ob"6>T{Wp@~pK5`_SmY!^+AMC`b{o?AhKV -AqWw E@
(1;c0E/9J~g|y gc'aH>a>\T V
6.17 BI Java: Performing Follow-Up Activities for Business Warehouse

If you have already used Information Broadcasting (IB) in NetWeaver 04, you only have to perform the configuration steps for the two new components, BW Reporting and Planning and BW Webdynpro ALV. If you have not configured Information Broadcasting in the source release, you have to perform the complete BW configuration, that is, the configuration of IB, BW Reporting and Planning, and BW Webdynpro ALV. As of SAP NetWeaver 7.0, BW Universal Data Integration (BW UDI) is an integral part of SAP NetWeaver Application Server. BW UDI allows the integration of external data sources by using BW Java
92/100
PUBLIC
2011-10-20
6 6.18
Follow-Up Activities EP: Checking the KMC Installation
Connectors. You need to complete the necessary follow-up activities and configuration tasks to make use of the connectors.
Procedure
Configuration of BW Information Broadcasting
For information about the configuration of BI Information Broadcasting, see the SAP Implementation Guide (IMG) at SAP NetWeaver Business Warehouse Settings for Reporting and Analysis Settings for Information Broadcasting
Configuration of BW Reporting and Planning
You have to create a RFC connection to the Adobe Server. For detailed information, see IMG SAP NetWeaver Business Warehouse Settings for Reporting and Analysis and SAP NetWeaver Business Warehouse BW Integrated Planning
Configuration of BW Web Dynpro ABAP ALV
You have to create RFC destinations and Web Service destinations as described in the IMG under Application Server Web Dynpro for ABAP Set-Up Printing for Web Dynpro ABAP ALV .
Configuration of BW UDI
For information about the configuration of BW UDI, see the IMG at SAP NetWeaver Business Warehouse UDI Settings by Purpose.
]Ym@:F?o0+5mKv WYmVP:Fs:o>/56KOq}C;#tg^g?\L+
6.18 EP: Checking the KMC Installation

As of SAP NetWeaver 7.0, Knowledge Management and Collaboration is an integral part of usage type Enterprise Portal. The upgrade program installs KMC during the upgrade if it has detected an Enterprise Portal installation in the source release system. After the upgrade has finished, you can perform some checks to see, whether the KMC installation succeeded. Use the KM Content iView and the KM Component Monitor to find out whether you can start up the system without any errors. If you find errors, then check the deployment and the log files.
Procedure
Checking the KM Content iView
1. 2.
Log on to the portal as a user with the super administrator role. Choose Content Administration KM Content and check whether any errors are displayed.
Checking the Component Monitor
1.
Log on to the portal as a user with the super administrator role.
2011-10-20
PUBLIC
93/100
6 6.18
Follow-Up Activities EP: Checking the KMC Installation
2. 3.
4.
Choose System Administration Support Knowledge Management Component Monitor . For Filters, Repository Managers, Repository Services and Services, check whether all subentries have the status green. The colors beside the entries indicate the following: j-b Green shows the object is functioning well. j-b Red shows the object cannot be started or is configured incorrectly. j-b Yellow indicates that one or more lower-level items are red. If an object has the status red, read the error message. Try to correct the error in the system configuration. For more information about the configuration, see the online documentation at http:// help.sap.com/nw73 SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Enterprise Portal Knowledge Management Administration Guide System Administration Monitoring, Logging, and Tracing Component Monitor .
Checking the Deployment
If the portal does not start up after the installation, or you notice errors in the Knowledge Management component monitor, then check the deployment. When you check the deployment, examine both the application and content files. 1. Switch to the directory that contains the deployment files for the Knowledge Management and Collaboration applications:
/usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/ server0/apps/sap.com/irj/ servlet_jsp/irj/root/WEB-INF/ deployment/pcd
2.
Check whether any of the following files have the extension .err: j-b com.sap.ib.bi.* j-b com.sap.km.* j-b com.sap.netweaver.* j-b com.sap.workflow.* If any files have the ending .err this indicates that the deployment was executed, but an error occurred. In this case, find out the reason for the error in the corresponding log file. The log file has the same name as the .err file, but the extension is .log. Switch to the directory that contains the files for the deployment of KM and Collaboration content:
/usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/ server0/apps/sap.com/irj/ servlet_jsp/irj/root/WEB-INF/ deployment/pcdContent
3.
4.
Check whether any of the following files have the extension .err: j-b j-b j-b j-b
com.sap.ib.bi.* com.sap.km.* com.sap.netweaver.* com.sap.workflow.*
94/100
PUBLIC
2011-10-20
6 6.19
Follow-Up Activities EP: Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC)
If any of the com.sap.km* files have the ending .err, check the corresponding .log file to find out what caused the error. Also check the AS Java log files mentioned below.
Checking the Log Files
If the portal does not start up after the installation of Content Management and Collaboration or you notice errors in the KM Content iView, then check the available trace file. 1. Switch to the directory:
/usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/server0/log/
2.
Open the file defaultTrace.*.trc with the most recent date. If errors appear in the trace file, try to solve them and then restart the AS Java.
NOTE
You can also view the trace file using the Log Administrator.
?S4r?I<h^0Ni(n
_B}qcq-/PpO;D ?Ym=/I<,<^3SiV(X
THqcq%0PxOED;*qG
Viewer that is available in the SAP NetWeaver
6.19 EP: Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC)
The follow-up activities for Knowledge Management and Collaboration are different depending on whether you have used KMC in the source release or not.
Procedure
?Ym=/I<,<^3SiV(N
U_qcq&P=9ORD;*bY:s9O|}R
KMC Was Not Configured in SAP NetWeaver 2004
Rename the following two files: ? initialPermissionsKMC.xml.template to initialPermissionsKMC.xml ? upgradePermissions.xml.template to upgradePermissions.xml The files are located in the following directory:
/usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/server0 /apps/sap.com/irj/servlet_jsp/ irj/root/WEB-INF/portal/system/xml/acl
?S4r?I<i^'_iL(x
VLqcqqcPO`D;c*v3:1s ?Ym=/I<,<^3SiV(N
U_qcq&P=9ORD;*bY:s9O|}R
KMC Was Configured in SAP NetWeaver 2004
? Check whether the link to the Collaboration Launch Pad is available in the tool area of the portal masthead. If the link is not available, you need to activate it. For more information, see the SAP NetWeaver Library at:
2011-10-20
PUBLIC
95/100
6 6.19
Follow-Up Activities EP: Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC) http://help.sap.com/nw73
SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Enterprise Portal Collaboration Administration Guide Collaboration Configuration Wizard-Based Basic Configuration for Collaboration Activating the Link for Launching the Collaboration Launch Pad L
As of SAP NetWeaver 7.0 Support Package Stack 09, the encoding of user IDs in the userhome Repository has changed. You must migrate the userhome Repository of users that have a ~ (tilde) in their name before the users log on to SAP NetWeaver Portal for the first time. For more information, see SAP Note 961747.
L
'ZeV^Qu}jk"|FVJqi|'_CPw"7Z7'9XT/2sM/
Enable the Search Functions for Knowledge Management and Collaboration
To use the search functions in Knowledge Management and Collaboration (KMC) for SAP NetWeaver 7.3, you need Search and Classification (TREX) 7.1 or higher installed in the target release system. Therefore, if you are using TREX 7.0 in the source release system, you must upgrade it to TREX 7.1 or higher. During the upgrade, only the TREX data, indexes, and queues are migrated from the old TREX 7.0 system to the new TREX 7.1 system, but not the overall configuration. Therefore, you need to configure the new TREX 7.1 system after the upgrade. For more information, see Upgrade Guide - Upgrade from SAP NetWeaver TREX 7.0 to TREX 7.1 available on SAP Service Marketplace at http://service.sap.com/instguides.
Configure KMC
To be able to use the basic features from Knowledge Management and Collaboration, you have to perform the minimal configuration tasks. L

L
'Re]UJQy}j]"FFJqvi9'{Cawq77'+8T~2Es/Zoq=Vn+:qJ>yZ> J{c-%~@LjFRZF (yH;833R yXnYt'Qo"~C8
If you have already used KMC in SAP NetWeaver 7.0 and plan to use the multiple file upload feature in SAP NetWeaver 7.3, you only have to perform the configuration for multiple file upload. For more information about the relevant configuration steps, see: help.sap.com/nw73 SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Enterprise Portal Knowledge Management Administering the Knowledge Management System Basic Configuration for Knowledge Management Additional Manual Configuration Steps Optional: Configuring Multiple File Upload
L
'ZeV^Qu}jk"|FVJqi|'_CPw"7Z7P6T;2s/Z-Mq=V*:qJ{yZk ({A<%~=LjF7Z* y ;{J3] JuLYtQ
L
For Knowledge Management, see the following documentation for the basic configuration tasks: help.sap.com/nw73 SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Enterprise Portal Knowledge Management Administering the Knowledge Management System Basic Configuration for Knowledge Management L
For Collaboration, see the following documentation for the basic configuration tasks: help.sap.com/nw73 SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Enterprise Portal Collaboration Administration Guide Collaboration Configuration Wizard-Based Basic Configuration for Collaboration
L
'ZeVIQd}Wj}"uF']%Ei0'6CEwR7
96/100
PUBLIC
2011-10-20
6 6.20
Follow-Up Activities Installing the SAP Online Documentation
6.20 Installing the SAP Online Documentation

Procedure
You must perform the following actions before you can display the online documentation (SAP Library) in your SAP system: 1. Install the SAP online documentation in your SAP system as described in the README.TXT file contained in the root directory of the online documentation DVD, which is delivered as part of the upgrade package. 2. Update the online documentation to the latest Support Package Stack level. For more information, see the document Support Package Stack Guide SAP NetWeaver 7.3 SPS<x> located on SAP Service Marketplace at http://service.sap.com/maintenanceNW73. Back to Quick Guide [page 19]
6.21 Installing Additional Application Server Instances

After the upgrade of the primary application server instance, you need to reinstall the additional application server instance to the new release. To do this, you must have uninstalled the old additional application server instance before entering the downtime [page 76]. You can now install the new additional application server instance using the SAPinst tool. You can now also install more additional application server instances, if necessary.
Procedure
1.
Install the new additional application server instance as described in the document Installation Guide <SAP NetWeaver / SAP application><Release> (<Technology>) on <Operating System>: <Database>. Use therefore the Installation Master DVD of your target release. 2. If you want to reuse the profiles of the old additional application server instances and now use other instance numbers than on the source release, adapt the instance numbers in the profiles. Back to Quick Guide [page 19]
2011-10-20
PUBLIC
97/100
A A.1
Appendix List of Documentation
A Appendix
A.1 List of Documentation

Document Internet Address
http://service.sap.com/instguidesNW
Upgrade Master Guide for SAP NetWeaver Master Guide for SAP NetWeaver Media List for SAP NetWeaver SAP Frontend Installation Guide Installing the SAP Library Installation Guide SAP NetWeaver <Technology> on <Operating System>: <Database> Database Administration Guide: SAP on IBM DB2 for Linux, UNIX, and Windows SAP Planning Guide for SAP NetWeaver on IBM DB2 for z/OS SAP Database Administration Guide for SAP Netweaver on IBM DB2 for z/OS SAP Security Guide: IBM DB2 for z/OS Upgrade to SAP MaxDB Version <x>: <Platform> Upgrading to Oracle Version <x>: <Platform>
<Release>
Upgrade
http://service.sap.com/instguidesNW http://service.sap.com/instguidesNW http://service.sap.com/instguidesNW http://service.sap.com/instguidesNW http://service.sap.com/instguidesNW
<Release> Installation <Release> Upgrade <Release> Installation Other Documentation SAP Library <Release> Installation
<Release>
Operation
<Release> <Release>
Operations Operations
<Release>
Operations Database Upgrades Database Upgrades
http://service.sap.com/instguides
Other Documentation Other Documentation
MaxDB
http://service.sap.com/instguides
Oracle
2011-10-20
PUBLIC
99/100
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.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.

Ug Nw73 Java+Unix+Oracle

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ug Nw73 Java+Unix+Oracle

Загружено:

Авторское право:

Доступные форматы

Upgrade Guide SAP NetWeaver 7.

PUBLIC 4b?k1"? `"veu0] % LQ|(tlJ;XO|3gBc|

You can find this document at the following address: http://service.sap.com/instguides

Aspects Covered by this Guide

AIX HP-UX Linux Solaris

Example Example Example

1.0 1.1 1.2

2010-11-29 2011-08-12 2011-10-20

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 List of Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Introduction Quick Access

1.1 Quick Access

1.2 About This Document

Introduction About This Document

Introduction Before You Start

1.3 Before You Start 1.3.1 Naming Conventions

Introduction Before You Start

IBM DB2 for z/OS and Short Forms

1.3.2 New Features

Upgrade procedure and handling

Troubleshooting and administration documentation included in the upgrade program

SAP kernel file structure

As of SAP NetWeaver PI 7.1

As of SAP NetWeaver PI 7.1

As of SAP NetWeaver PI 7.1

As of SAP NetWeaver PI 7.1

Introduction Before You Start Description Availability

Upgrade of additional application server instances

1.3.3 SAP Notes for the Upgrade

Introduction Before You Start

n,)-TOO `RnwbeO`l B^X gyxqo?%X(wx841f^dtJYL

1403832 1390477 1468615

d,)-T_ `tcDnwjeb_lw1 ^X \Vvrq&X(Zyx8# n,)-TOO `RnwbeO`l B^X F+

1403832 1390477 1364670

d,)-T_ `tcDnwjeb_lAw 1^C n,)-TOO `RnwbelUly

Specific to this upgrade Specific to this upgrade

d,)-T_ `WV n5w$ n,)-TOO `RnwbeLlW=

1403832 1390477 1487754

Other SAP Notes

Introduction Before You Start

Database-Independent SAP Notes SAP Note Number Description Area

Introduction Before You Start Description Area

SAP Note Number

DB2 for Linux, UNIX and Windowsspecific

APAR list Automatic PTF Check

IBM DB2 for z/OS IBM DB2 for z/OS

498036 201388 201390 352081

SAP MaxDB-specific SAP MaxDB-specific SAP MaxDB-specific SAP MaxDB-specific

SAP Notes for Oracle SAP Note Number Description Area

819829 556764 11777

Oracle-specific Oracle-specific Oracle-specific

1.3.4 Accessing Documentation

Introduction Before You Start

Introduction Before You Start

Local Installation of the SAP NetWeaver Library

The relevant database-specific SAP Note 1468615

The relevant database-specific SAP Note 1364670

The relevant database-specific SAP Note 1493434.

The relevant database-specific SAP Note 1487754

Space requirements in the database (estimation):

8 GB during the upgrade

$X{EA%n |hY \jj;')1n!M

Space requirements in the database: See SAP Note 943143.

Space requirements in the database (estimation): 15 GB during the upgrade

Space requirements in the database (estimation): 8 GB during the upgrade

PUBLIC 4b?k1"? `"veu0] %LQ|(tlJ;XO|3gBc|

n,)-TOO `RnwbeO`l B^X gyxqo?%X(wx841f^dtJYL

d,)-T_ `tcDnwjeb_lw1 ^X \Vvrq&X(Zyx8# n,)-TOO `RnwbeO`l B^X F+

d,)-T_ `tcDnwjeb_lAw 1^C n,)-TOO `RnwbelUly

d,)-T_ `WV n5w$ n,)-TOO `RnwbeLlW=

$X{EA%n |hY \jj;')1n!M

.4A.1nY|bH{P\J<j;iR1nK $X{EA%n |hY \g6j;

t) t) t) t)

ssL*m7g_gCommunication Between SAPup, the SL Controller, and the Front End

The upgrade directory is divided into the following subdirectories: ss ss

g)~`C6V/S|8!~xx&z2gAPFe=nKt-jjol;i=jK.LT.; g)~hC6V/s|)~<x#x&r22ANF=}K:3jpol;