sum108 java+unix+oracle copy

Update GuideUpdate of SAP Systems Using Software Update Manager 1.0 SP08For: Java UNIX Oracle

Target Audience System administrators Technology consultants

CUSTOMERDocument version: 1.1 2013-08-12

Aspects Covered by this Guide

PlatformUNIX

Operating SystemAIXHP-UXLinuxSolaris

DatabaseOracle

2/132 CUSTOMER 2013-08-12

Document History

CAUTIONBefore 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/sltoolset.

The following table provides an overview of the most important document changes.Version Date Description1.0 2013-07-15 Initial version1.1 2013-08-12 Minor corrections added

2013-08-12 CUSTOMER 3/132

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.2 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4 Accessing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2 Quick Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1 Tool Information: Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . 233.1.1 Software Update Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.2 Communication Between Back-End Processes and GUI . . . . . . . . . . . . . . . . . . 273.1.3 SUM Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.2 Technical Details of the Update Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.3 Technical Details of the Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 313.4 Update of NWDI-Driven System Landscapes . . . . . . . . . . . . . . . . . . . . . . . . . . 323.5 Update of Distributed and High Availability Systems . . . . . . . . . . . . . . . . . . . . 35

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.1 Determining the Host for the Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.2 Checking the Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.3 Checking the Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.3.1 Checking the Source Release of the SAP System . . . . . . . . . . . . . . . . . . . . . . . 404.3.2 Meeting the Operating System-Specific Requirements . . . . . . . . . . . . . . . . . . 414.3.3 Upgrade of the Operating System and Database System: Overview . . . . . . . . . 424.3.4 Checking the Software Delivery Manager Version . . . . . . . . . . . . . . . . . . . . . . 434.3.5 Checking the Memory and JVM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.3.6 Installing SAP JVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.4 Making Preparations at the Database Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.5 Updating Database Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4/132 CUSTOMER 2013-08-12

4.6 Cleaning Up the Profile Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.7 Configuring OS User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.8 Making Preparations in the Monitoring Area . . . . . . . . . . . . . . . . . . . . . . . . . . 464.9 Setting the Public Substitution Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.10 Synchronizing the Database and the SDM Repository . . . . . . . . . . . . . . . . . . . 474.11 Filling the Download Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.12 Ensuring the Correct Kernel Directory Detection . . . . . . . . . . . . . . . . . . . . . . 484.13 Preparing the Update of Distributed and High Availability

Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.14 Changing Passwords and Updating the Secure Store . . . . . . . . . . . . . . . . . . . . 494.15 Installing or Updating SAP Host Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 5 Running the Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.1 Meeting the Requirements for the SUM Directory . . . . . . . . . . . . . . . . . . . . . 555.2 Downloading the Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 555.3 Starting the Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555.4 Starting the Software Update Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.5 Restarting the Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585.6 Resetting the Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.7 Using Breakpoints During the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615.8 Using the Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615.9 Advanced GUI Options: Role Management and Alert Function . . . . . . . . . . . 625.10 Making Entries for the Specify Credentials Roadmap Step . . . . . . . . . . . . . . . . 645.11 Making Entries for the Select Target Roadmap Step . . . . . . . . . . . . . . . . . . . . 645.12 Making Entries for the Confirm Target Roadmap Step . . . . . . . . . . . . . . . . . . 655.13 Making Entries for the Configuration Roadmap Step . . . . . . . . . . . . . . . . . . . 655.13.1 Making Basic Entries for the Java Update Process . . . . . . . . . . . . . . . . . . . . . . . 665.13.2 Making Entries for the Target System Configuration . . . . . . . . . . . . . . . . . . . . 675.13.3 Removing or Migrating par Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.14 Making Entries for the Checks Roadmap Step . . . . . . . . . . . . . . . . . . . . . . . . . 695.15 Performing Actions Before the Beginning of the Downtime . . . . . . . . . . . . . . 695.16 Performing Actions at the End of the Downtime . . . . . . . . . . . . . . . . . . . . . . . 715.17 Evaluating the Update Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.18 Running the Software Update Manager Repeatedly . . . . . . . . . . . . . . . . . . . . 73

Chapter 6 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756.1 Performing Follow-Up Activities for User root . . . . . . . . . . . . . . . . . . . . . . . . . 756.2 Performing Follow-Up Activities in the Monitoring Area . . . . . . . . . . . . . . . . 78

2013-08-12 CUSTOMER 5/132

6.3 Modifying the JAVA_HOME Environment Variable After the Update of SAPJVM 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

6.4 Performing Follow-Up Activities for SAP Solution Manager . . . . . . . . . . . . . . 796.5 Installing Additional Application Server Instances . . . . . . . . . . . . . . . . . . . . . . 80

Chapter 7 Applying Single Component Updates and Patches Using a Manually Prepared Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837.2 Quick Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837.3 Filling the Manually Prepared Download Directory . . . . . . . . . . . . . . . . . . . . . 857.4 Running the Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857.4.1 Meeting the Requirements for the SUM Directory . . . . . . . . . . . . . . . . . . . . . 877.4.2 Downloading the Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 877.4.3 Starting the Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887.4.4 Starting the Software Update Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.4.5 Restarting the Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917.4.6 Resetting the Software Update Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917.4.7 Using Breakpoints During the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.4.8 Using the Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937.4.9 Advanced GUI Options: Role Management and Alert Function . . . . . . . . . . . 957.4.10 Making Entries for the Specify Credentials Roadmap Step . . . . . . . . . . . . . . . . 967.4.11 Making Entries for the Select Target Roadmap Step . . . . . . . . . . . . . . . . . . . . 967.4.12 Making Entries for the Confirm Target Roadmap Step . . . . . . . . . . . . . . . . . . 977.4.13 Making Entries for the Configuration Roadmap Step . . . . . . . . . . . . . . . . . . . 987.4.14 Performing Actions Before the Beginning of the Downtime . . . . . . . . . . . . . . 997.4.15 Performing Actions at the End of the Downtime . . . . . . . . . . . . . . . . . . . . . . . 997.4.16 Evaluating the Update Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997.4.17 Running the Software Update Manager Repeatedly . . . . . . . . . . . . . . . . . . . . 100

Chapter 8 Installing Additional Usage Types (Technical Usages) in an Existing SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038.2 References to Maintenance Optimizer Documentation . . . . . . . . . . . . . . . . . 1038.3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038.4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048.5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048.6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058.7 Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

6/132 CUSTOMER 2013-08-12

Chapter 9 Correction of Installed Software Information . . . . . . . . . . . . . . . . . . . . . 1099.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1099.2 Making Entries for the Select Target Roadmap Step . . . . . . . . . . . . . . . . . . . . 109

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111A.1 Process Overview Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111A.2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112A.2.1 Error Handling for Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113A.2.2 Update Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114A.2.3 Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115A.2.4 Reentering Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116A.2.5 Correcting Errors in DEPLOY_ONLINE_* Steps . . . . . . . . . . . . . . . . . . . . . . . 117A.2.6 Correcting Problems in the DEPLOY_* Steps . . . . . . . . . . . . . . . . . . . . . . . . . 119A.2.7 Correcting Errors in the RUN_OFFLINE_MIGRATION Step . . . . . . . . . . . . . 120A.2.8 Restarting the Software Update Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . 121A.2.9 Kernel Version and Instance Numbers Used During the Upgrade . . . . . . . . . 121A.2.10 Correcting Problems with AS Java Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . 122A.2.11 Correcting Problems with J2EE Engine Startup . . . . . . . . . . . . . . . . . . . . . . . 124A.2.12 Starting and Stopping the AS Java Manually . . . . . . . . . . . . . . . . . . . . . . . . . 125A.2.13 Starting and Stopping the J2EE Engine Manually . . . . . . . . . . . . . . . . . . . . . . 126A.3 List of Referenced SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127A.4 List of Referenced Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

2013-08-12 CUSTOMER 7/132

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

1 Introduction

1.1 About This DocumentPurposeThis document describes how to update SAP systems based on SAP NetWeaver Java using the Software Update Manager (SUM) 1.0 SP08.For a list of all supported processes, products and releases, see the current Software Update Manager Note 1790828.The Software Update Manager is a multi-purpose tool that supports various processes, such as performing a release upgrade, installing enhancement packages, applying Support Package Stacks or updating single components. For clarity and readability, the term update is used in this document for all supported processes.

IntegrationIt is essential that you read the Master Guide (or Upgrade Master Guide, if such exists as a separate guide) for your product version. The Master Guide (Upgrade Master Guide) guides you through the complete update and refers you to the required documentation for each step.If there are preparation and follow-up activities for the update that are specific to your product, they are described in a product-specific document. This document is also referenced in the Master Guide (or Upgrade Master Guide). It is crucial that you perform the product-specific preparation activities before you start the Software Update Manager and that you perform the follow-up activities after the Software Update Manager has finished successfully.To find the latest version of these documents, see SAP Service Marketplace at http://service.sap.com/instguides.

How to Use This DocumentCAUTIONIt is essential that you use the Quick Guide [page 17] to guide you through the process. The Quick Guide checklist provides you with an overview of all necessary tasks in chronological order.If you are experienced in performing updates, the checklist may contain all you need to know to perform the update successfully. If you need more information, follow the links to the detailed descriptions.

NOTEIf this document contains information for more than one operating system, database or product release, texts that apply to one or more of these aspects are marked with bars.

1 Introduction1.1 About This Document

2013-08-12 CUSTOMER 9/132

These bars always show all aspects for which the text is valid, even though these aspects may not be of interest for your specific process.

The document is structured as follows: Chapter 1 Introduction

This chapter contains information about using this document, some naming conventions for the document, and lists the required SAP Notes.

Chapter 2 Quick GuideThe Quick Guide lists all activities in the right order. For more information about the single steps, follow the links in the Quick Guide [page 17].

Chapters 3 to 6 Update ProcessThese chapters contain detailed information about planning, preparing, and performing the update, and about follow-up activities.

Chapter 7 Applying Single Component Updates and Patches Using a Manually Prepared DirectoryThis chapter contains information about how to apply single component updates and patches using a special feature in the Software Update Manager.

Chapter 8 Installing Additional Usage Types (Technical Usages) in an Existing SAP SystemThis chapter contains information about how to install additional Java usage types or technical usages on an existing SAP system based on SAP NetWeaver Java.

Chapter 9 Correction of Installed Software InformationThis chapter contains information about how to correct and update the details of the software instances installed in your SAP system.

Appendix Process Overview Report

Contains information about the process overview reports that are generated by the SUM. Troubleshooting

Contains information about known problems and troubleshooting them. List of Referenced SAP Notes

Lists all SAP Notes with additional information about the update procedure that are referenced in this document besides the SAP Notes [page 14] that are relevant for the update preparation.

List of Referenced DocumentationLists the documentation that is referenced in this document and contains information about where to find this documentation.

1.2 New FeaturesThe following table lists significant new features and improvements of the Software Update Manager. The table also indicates the SUM version in which the new or improved features were introduced.

1 Introduction1.2 New Features

10/132 CUSTOMER 2013-08-12

Feature Description AvailabilityCommon user interface Some of the actions performed by SUM, for

example, the source system detection, and some of the required user actions, which are common for ABAP and Java, were moved to new roadmap steps. For more information, see Technical Details of the Update Procedure [page 29] or Technical Details of the Upgrade Procedure [page 31].

SUM 1.0 SP02

New feedback form There is a new feedback form, which allows you to evaluate the update process and send your feedback to SAP. This feedback form is integrated directly in the Software Update Manager GUI (Summary roadmap step). For more information, see Evaluating the Update Process [page 72].

SUM 1.0 SP03

Process overview report The comprehensive process overview html reports are generated by SUM during the tool run. As a function of the process progress, they contain a growing number of relevant subsections. They are readily accessible through the SUM GUI on demand, upon error and upon successful completion. For more information, see Process Overview Report [page 111].

SUM 1.0 SP03

Additional usage types (technical usages) installation

You can now install additional Java usage types (technical usages) in an existing SAP system using the Software Update Manager. For more information, see Installing Additional Usage Types (Technical Usages) in an Existing SAP System [page 103].

SUM 1.0 SP03

Check for sapstartsrv patch level on the source system

Right after the Welcome roadmap step, the Software Update Manager checks whether the patch level of SAP start service (sapstartsrv) on the source system is appropriate. This check is performed to prevent possible problems during the update that are related to the proper stop and start of the SAP system. For more information, see SAP Note 1656036.

SUM 1.0 SP03

Support of single component updates and patches for SAP NetWeaver systems

You can now apply single component updates and patches on SAP NetWeaver systems using the Software Update Manager. To do this, proceed as described in Applying Single Component Updates and Patches Using a Manually Prepared Directory [page 83].

SUM 1.0 SP04

Filter out upgrade and update paths unsupported by current SUM version

An early check is added to filter out upgrade and update paths that are not supported by the current SUM version. The check is based on a comparison between the following: Unsupported combinations of source and

target product versions Stack XML file contentIf an unsupported path is detected, SUM displays an error or warning message and refers you to the

SUM 1.0 SP04


2013-08-12 CUSTOMER 11/132

Feature Description Availabilitycurrent central SUM Note for information about currently supported paths.Details about the currently unsupported paths are provided (during the tool run) in the process overview report [page 111] in section Tool Versions and Configuration List of unsupported upgrade and update paths .

Improved update process of SAPJVM 4 for SAP NetWeaver 7.0-based systems

The update of SAPJVM 4 for SAP NetWeaver 7.0-based systems is now an automated process in SUM. This applies when upgrading/updating the system, when applying single component updates and patches, and when sapcpe replication is not available.

SUM 1.0 SP05

Support of downward-compatible kernel 7.20 for systems based on SAP NetWeaver 7.0 and SAP NetWeaver 7.1

SUM supports updating to downward-compatible kernel (DCK) version 7.20 for systems based on SAP NetWeaver 7.0 and SAP NetWeaver 7.1 (when upgrading, updating, or when applying single component updates and patches).

SUM 1.0 SP05

Improved handling of par files and migration to ear file format.

During an upgrade from SAP NetWeaver 7.0-based portal systems, the handling of content archives delivered directly to the Portal Content Directory (PCD) and the conversion from par to ear file format have been improved. For more information, see Making Entries for the Target System Configuration [page 67].

SUM 1.0 SP06

Support of downward-compatible kernel versions 7.21 and 7.21 EXT

SUM supports updating to downward-compatible kernel version 7.21 or version 7.21 EXT. For more information about these kernel versions, see SAP Note 1713986.

SUM 1.0 SP06

Support of SAPJVM4 update with Wily Introscope Agent in the SAP system

SUM can automatically rebuild the AutoProbe connectors of Wily Introscope Agent during an SAPJVM4 update.

SUM 1.0 SP06

Support for Selectively Installable Instances

SUM can apply stacks that contain selectively installable instances. When you generate a stack for your upgrade using Maintenance Optimizer (MOPZ), you can choose selectively software component archives (SCA files) containing a functionality typically part of a complete technical usage (usage type). When deployed after the update, the functionality is operational without the need for the usage type to be activated.

SUM 1.0 SP06

New check for program SAPILED Before entering the downtime and before the kernel switch, in steps DOWNCONF_DTTRANS and KX_SWITCH, a new check makes sure that process SAPILED is running. If this process is not running, the kernel switch will fail.

SUM 1.0 SP07


12/132 CUSTOMER 2013-08-12

Feature Description AvailabilityCorrecting Installed Software Information

You can correct and update the information about the software instances installed in your SAP system. For more information, see Correction of Installed Software Information [page 109].

SUM 1.0 SP08

1.3 Before You Start1.3.1 Naming ConventionsUpdateIn this document, the term update is used as a collective term for all the software logistics processes that you can perform using the Software Update Manager (such as performing release upgrades, installing enhancement packages, or updating a system with Support Package Stacks).

Software Update Manager, SAPehpi, and SAP Upgrade ToolsThe Software Update Manager evolved from the previous SAP Enhancement Package Installer and SAP upgrade tools. The tool has been renamed to reflect its broader use.

SUM Directory and In this document, SUM directory and are used as synonyms when referring to /SUM.

SAP SystemIn this document, the term SAP system is used for SAP NetWeaver systems as well as for SAP application systems. SAP is also used as a synonym for SAP NetWeaver or SAP application in terms such as SAP start profile or SAP system language.

SAP System IDIn this document, the SAP system ID is abbreviated as SAPSID or sapsid. If is used, your SAP system ID must be in lowercase letters, for example prd. If is used, you must write in uppercase letters, for example PRD.

ID for the SAP System ReleaseIn this document, stands for the relevant SAP system release, without a decimal point, such as 740. If an enhancement package has been installed in the system, the last digit indicates the enhancement package version, such as 731 for SAP enhancement package 1 for NetWeaver 7.3.

SAP System InstancesAs 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:

1 Introduction1.3 Before You Start

2013-08-12 CUSTOMER 13/132

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

Central services instance Database instanceThroughout this document, we use the new terms primary application server instance and additional application server instance. For releases lower than SAP NetWeaver 7.1, the primary application server instance corresponds to the central instance and the additional application server instance corresponds to the dialog instance.

Instance NameIn this document, is used as a placeholder for the instance name in the instance directory path of your system.Substitute with J for the primary or additional application server instance, where stands for the instance number.

Step and PhaseIn this document, in some scenarios the term phase is used as a synonym to the generic term step. This is done in alignment with the Software Update Manager GUI, when regarding ABAP scenarios, distinguishes these terms on a technical level.

Technical UsageIn this document, the term technical usage is used as a synonym of usage type.

AS Java and J2EE EngineRelease upgrade only:As of SAP NetWeaver 7.0, the naming of the SAP proprietary Java application server has changed and the term J2EE Engine is no longer used.In this document, the term Application Server (AS) Java is used when referring to SAP NetWeaver 7.0 and higher. The term J2EE Engine is only used when referring to Release 6.40.Only valid for: Solaris |

Solaris and Oracle SolarisAs of operating system version 10, Solaris has been renamed to Oracle Solaris.In this document, the former name Solaris is used as well.End of: Solaris |

1.3.2 SAP NotesUseTo prepare and perform the update 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

1 Introduction1.3 Before You Start

14/132 CUSTOMER 2013-08-12

(http://service.sap.com/notes), some of which you must read before you start with the preparations. Besides the central Software Update Manager Note, there are separate SAP Notes for the database-specific sections. When you actually perform the update, you may need information from some additional SAP Notes. These SAP Notes are named at the appropriate places in this document.

SAP Notes for Preparing the UpdateYou must request the following SAP Notes from SAP Support Portal before you start the update procedure: Central Software Update Manager Note SAP Note for your databaseSince these SAP Notes are updated regularly, make sure that you always use the newest version.SAP Note Number Description1790828 Central Software Update Manager Note1843966 Oracle-specific

Keyword for the Software Update ManagerIn the Confirm Target roadmap step, you are asked to enter a keyword, which you can find in the current Software Update Manager Note 1790828. The Software Update Manager does not proceed until you have entered the keyword.

Other SAP NotesIn addition to the SAP Notes that you need to prepare the update, this document also refers you to other SAP Notes that contain additional information. These SAP Notes are listed in the List of Referenced SAP Notes [page 127].

1.4 Accessing DocumentationBefore, during and after the update, you require the SAP online documentation. For more information about accessing this documentation, see the product-specific document for your target release.

1 Introduction1.4 Accessing Documentation

2013-08-12 CUSTOMER 15/132

2 Quick Guide

This section contains a checklist with all the actions you need to perform: Find SAP Notes Plan the update Prepare the update Update your system Perform the follow-up activitiesThe 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 gain a quick overview of the update procedure.

ChecklistSAP NotesThis 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 update, and also help you perform the actual update. 1. You request the current SAP Notes [page 14]. You require at least the following SAP Notes:

Central Software Update Manager Note 1790828 The relevant database-specific SAP Note 1795196

Additional DocumentationBefore, during and after the update, you require additional documentation, such as SAP Library documentation. 1. You make sure that you can access the SAP Library documentation [page 15].Update PlanningBefore you start the actual update, you must plan it carefully so that downtime is reduced to a minimum and the update runs as efficiently as possible.

CAUTIONStart planning your update at least two weeks before you want to begin with the update.

1. You familiarize yourself with the features of the Software Update Manager [page 23] and the update procedure.Enhancement package installation and SPS update: If you require more detailed information, see Technical Details of the Update Procedure [page 29].

2 Quick Guide

2013-08-12 CUSTOMER 17/132

Release upgrade only: If you require more detailed information, see Technical Details of the Upgrade Procedure [page 31].

2. You plan the update of NWDI-driven system landscapes [page 32]. 3. You plan the update of distributed and high-availability systems [page 35].Update PreparationYou can perform the preparations while the system is in production operation. The Software Update Manager supports you here by making most of the necessary checks automatically.

CAUTIONIn addition to the general preparations described in this document, you need to perform the preparations that are specific to your product version, which are described in an additional product-specific document. This document is referenced in the Master Guide (or Upgrade Master Guide, respectively) for your product.

Actions Before Starting the Software Update Manager 1. You choose the host [page 38] for the preparations. 2. You check the hardware requirements: [page 39]

CPU, main memory, disk and swap space see SAP Service Marketplace at http://service.sap.com/sizingThe minimum swap space is 20 GB.

Disk space in the file system for the SUM directory and the download directory. The space required depends on the product you are updating. For more information, see the document with additional product-specific information, which is referenced in the Master Guide (or Upgrade Master Guide, respectively) for your product.

Space requirements in the database:The Software Update Manager calculates the space requirements for the database. The free space required is approximately in the range from 50 to 200 GB.

3. You check the software requirements: Release upgrade only: Source release [page 40] of the SAP system Release upgrade and enhancement package installation: Operating system-specific requirements

[page 41]. You plan or perform the upgrade of the operating system and database system [page 42], if necessary.

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

Only valid for: Source Release = SAP Web AS 6.40 |Release upgrade only: You check the Software Delivery Manager version [page 43].End of: Source Release = SAP Web AS 6.40 |

2 Quick Guide

18/132 CUSTOMER 2013-08-12

Only valid for: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |You check the Memory and JVM settings [page 44]End of: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

Only valid for: Target Release = SAP NetWeaver 7.0 EHP3 |You make sure that SAP JVM 4.1 is installed in your system [page 44].End of: Target Release = SAP NetWeaver 7.0 EHP3 |

4. You make the preparations at the database level [page 45]. 5. You update the database statistics [page 45]. 6. If necessary, you clean up the profile directory [page 45]. 7. You configure the OS user authentication [page 45]. 8. Only valid for: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP Web AS 6.20;SAP Web AS 6.40 |

You make the preparations in the monitoring area [page 46].End of: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP Web AS 6.20;SAP Web AS 6.40 |

9. Only valid for: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |You set the public substitution variable [page 46].End of: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

10. Only valid for: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3;SAP NetWeaver 7.0 SR3 |Enhancement package installation and SPS update on SAP NetWeaver 7.0-based system: You synchronize the database and the SDM repository [page 47].End of: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3;SAP NetWeaver 7.0 SR3 |

11. You fill the download directory [page 47]. 12. You make sure that the correct kernel directory [page 48] is detected by the Software Update Manager. 13. You perform the specific preparations for distributed and high availability systems [page 49]. 14. Only valid for: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

You change passwords and update the secure store [page 49].End of: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

15. You install or update SAP Host Agent [page 50].Update Procedure

CAUTIONDo not run Java Support Package Manager (JSPM) until the update procedure finishes. This is critical for the successful completion of the update procedure.

Actions for Starting and Using the Software Update Manager 1. You meet the requirements for the SUM directory [page 55]. 2. You download the Software Update Manager [page 55]. 3. You start the Software Update Manager [page 55] as user adm on the host with the primary

application server instance.

2 Quick Guide

2013-08-12 CUSTOMER 19/132

4. You start the Software Update Manager GUI [page 57].You can restart [page 58] or reset [page 59] the update. You can also set or remove breakpoints [page 61], and run the Software Update Manager and its GUI in accessibility mode [page 61].You can log on as administrator or observer [page 62], and you can configure an alert function [page 62] that notifies you when a user action is required.

Making Entries for the Specify Credentials Roadmap StepYou continue with roadmap step Specify Credentials [page 64] and make the corresponding entries.User Actions During the Select Target Roadmap StepYou continue with roadmap step Select Target [page 64] and make the corresponding entries.User Actions During the Confirm Target Roadmap StepYou continue with roadmap step Confirm Target [page 65] and make the corresponding entries.User Actions During the Configuration Roadmap StepYou continue with roadmap step Configuration [page 65].To perform the roadmap step, the Software Update Manager needs certain information from you. If possible, default values appear that you can confirm or change. 1. You make the basic entries for the Java update process [page 66]. 2. Release upgrade only: You make entries for the target system configuration [page 67]. 3. Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

Release upgrade (switch-based) only, for portal systems only: You make selections for removing or migrating par archives [page 68].End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

User Actions During the Checks Roadmap StepYou continue with roadmap step Checks [page 69] and make entries, if necessary.Actions During the Preprocessing Roadmap Step 1. You check the Software Update Manager Note, the application-specific SAP Note, and your

database-specific SAP Note for new information and changes. 2. Before the downtime [page 69] begins, you are asked to make the necessary backups and perform

additional actions.Actions During the Execution Roadmap StepWhile the processes of the Execution roadmap step are running, the system is in downtime.At the end of the downtime, you again create backups [page 71].Actions During the Summary Roadmap Step 1. You evaluate the update process [page 72]. 2. Optional: You make preparations for a repeated use of the Software Update Manager [page 73].Follow-Up Activities

CAUTIONIn addition to the general follow-up activities described in this document, you need to perform the follow-up activities that are specific to your product version, which are described in an

2 Quick Guide

20/132 CUSTOMER 2013-08-12

additional product-specific document. This document is referenced in the Master Guide (or Upgrade Master Guide, respectively) for your product.

Actions Before Restarting Production Operation 1. You perform the follow-up activities for user root [page 75]. 2. You perform follow-up activities in the monitoring area [page 78]. 3. Only valid for: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

You modify the JAVA_HOME Environment Variable [page 78] after the update of SAP JVM 4.End of: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

4. Release upgrade only: You perform follow-up activities [page 79] for SAP Solution Manager. 5. Only valid for: Source Release = SAP Web AS 6.40 |

Release upgrade only: You install additional application server instances [page 80].End of: Source Release = SAP Web AS 6.40 |

2 Quick Guide

2013-08-12 CUSTOMER 21/132

3 Planning

This part of the document contains information about planning your SAP system update. Before you begin the actual update, you must first plan it carefully. This includes requesting all the SAP Notes you need. Careful planning is a prerequisite for a successful update. The following information helps you plan your update so that downtime is reduced to a minimum, and the update runs as efficiently as possible.When you plan your update, note the following information in addition to the information in the Quick Guide [page 17]: All the times specified in this document are based on hardware with medium performance levels. Do not perform any additional actions during the Software Update Manager run that could cause

it to run less smoothly. Start planning your update at least two weeks before you start with the update preparations. To make sure that all requirements are met, run the preparation roadmap steps of the Software

Update Manager, Welcome, Select Target, Confirm Target, Execute Process, Initialization, 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 update in roadmap step Preprocessing. The successful execution of the preparation roadmap steps is a prerequisite for starting the update in roadmap step Preprocessing.

ActionsThe following sections are important for planning the update: Tool Information: Software Update Manager [page 23]

Software Update Manager GUI [page 24] Communication Between Back-End Processes and GUI [page 27] SUM Directory [page 27]

Enhancement package installation and SPS update: Technical Details of the Update Procedure [page 29] Release upgrade only: Technical Details of the Upgrade Procedure [page 31] Update of NWDI-Driven System Landscapes [page 32] Update of Distributed and High Availability Systems [page 35]Back to Quick Guide [page 17]

3.1 Tool Information: Software Update ManagerThe following sections provide you with important information about the update program Software Update Manager (SUM):

3 Planning3.1 Tool Information: Software Update Manager

2013-08-12 CUSTOMER 23/132

Software Update Manager GUI [page 24] Communication Between Back-End Processes and GUI [page 27] SUM Directory [page 27]Back to Quick Guide [page 17]

3.1.1 Software Update Manager GUIThe GUI provides you with functions for monitoring and navigating through the roadmap steps of the procedure. The complete procedure consists of several roadmap steps that contain modules, which in turn consist of the individual steps.The following figure displays the Software Update Manager GUI.

Figure 1: Software Update Manager GUI

FeaturesThe GUI consists of the following main elements: Menu bar

The menu bar offers you options that you need to work with the GUI and the Software Update Manager. It has the following entries: File

Under File, you can find the Exit function, which allows you to exit the GUI. User

Under User, you can find the following options:


24/132 CUSTOMER 2013-08-12

Change PasswordUsing this option, you can change the password for the administrator and observer [page 62].

List UsersThis option gives you an overview of all users logged on to the Software Update Manager.

Change RoleThis option allows you to switch between the administrator role and the observer role.

Failed AttemptsThis option shows failed logon attempts.

AlertUsing the Alert [page 62] menu option, you can define how you want to be notified when the Software Update Manager requires user interaction.

UpdateUnder Update, you can find the following functions: Stop Update

The update stops immediately.CAUTIONThis also stops the back-end processes, not only the GUI.

When you restart the update as described in Restarting the Update [page 58], the procedure continues at the point where you stopped it.

Reset UpdateUsing this menu option, you can reset the update procedure during the Preprocessing roadmap step as described in Resetting the Update [page 59].

LogsFrom here, you have direct access to the logs.

Process OverviewUsing this menu option, you can trigger the creation of a SUM process overview report on demand. To be able to open the generated report, it is a prerequisite to have a browser installed on the computer where the GUI runs. For more information about using this option, see Process Overview Report [page 111].

JavaUnder this menu item, you can find the following options: Start with options

Using this option, you can specify additional starting options for the Software Update Manager.

Set BreakpointUsing this option, you can set a breakpoint that allows the Software Update Manager to stop before a certain update step. For more information about breakpoints, see Using Breakpoints During the Update [page 61].


2013-08-12 CUSTOMER 25/132

Remove BreakpointUsing this option, you can remove the specified breakpoint.

LogsFrom here, you can access the log files of the Software Update Manager.

HelpUnder Help, you can find the following options: Online Help

From here, you can access the online help for the update steps. SAP Notes

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

RoadmapThe roadmap visualizes the roadmap steps. The roadmap step that is currently running is highlighted.Note that the roadmap step Execute Process... is broken down into 8 roadmap steps numbered from 5.1 to 5.8 as visualized in the following figure:

Figure 2: Roadmap Steps Tab pages

You see the following tab pages: Monitor

The monitor tab page displays a progress bar for the update procedure. The progress bar shows how much of a step has already been carried out. It also shows which step is currently running and informs you about the status (RUNNING, COMPLETED, WAITING, ABORTED).

JavaRequests the input for the update procedure.

Back and Next buttons


26/132 CUSTOMER 2013-08-12

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. During the first four roadmap steps, you can reset a roadmap step using the Back button.If the Software Update Manager cannot verify the information you entered or one or more of the prerequisites are not met, the resulting actions are displayed in one of the following ways: If the Software Update Manager requires immediate action, it is displayed on the respective

tab page. Once you have performed this action, you can continue choosing Next. All other required actions are displayed at the end of the roadmap step. The messages are

sorted according to their importance. Once you have performed the action, you can continue choosing Next.

Back to Quick Guide [page 17]

3.1.2 Communication Between Back-End Processes and GUIWhen you start the Software Update Manager on the primary application server instance, it calls the appropriate programs to execute the update steps. In addition, the Software Update Manager starts the Software Logistics (SL) Controller. The SL controller manages the Software Update Manager processes and provides ports to establish the communication with the front end. The following port numbers are used: Port 4239: Connection between SL controller and the Internet browser on the remote host Port 4241: Connection between the SL controller and the Software Update Manager GUI on the

remote hostBack to Quick Guide [page 17]

3.1.3 SUM DirectoryThe Software Update Manager creates the SUM directory on the host with the primary application server instance and copies data and programs into this directory.The recommended standard path of the SUM directory is:/usr/sap//SUMThe SUM directory is divided into the following subdirectories: sdt

Contains the SL controller.Contains the following subdirectories: config

Contains configuration xml files for the update. control

Contains configuration xml files for the upgrade.


2013-08-12 CUSTOMER 27/132

dataContains the internal repository of the Software Update Manager. Do not change files in the variables subdirectory since this can lead to an update failure.

downloadContains files downloaded by the Software Update Manager.

dtdContains DTD files with definitions required by the Software Update Manager to read xml files.

exeContains startup scripts for the Software Update Manager.

historyContains archived versions of old execution framework log files. These files are not the complete set of log files listed in the log directory, but the files that only control the overall execution process.

htdocContains the process overview reports for the update process and other resources for the html page.

libContains the JAR files of the Software Update Manager.

logContains all log files generated during the update process.

migtoolContains migration data (only available when migration controllers are executed).

paramContains the logging.properties file, in which you can increase the logging and tracing level.

patchContains database-specific and release-specific configurations of the Software Update Manager.

pluginContains execution framework plug-ins used by the different update scenarios.

propContains the logging.properties file with logging severity levels for the execution framework.

reqlistgenContains some libraries used by the execution framework.

statisticsContains temporary files generated by the execution framework.


28/132 CUSTOMER 2013-08-12

tmpContains temporary files created from external processes running during the update procedure.

trcContains trace files created by the Software Update Manager.

jvmDepending on your operating system and database, this directory contains the Java Virtual Machine delivered by SAP.

NOTEThe Java Virtual Machine, which is contained in this subfolder, is delivered by SAP especially for the use by the Software Update Manager for the update procedure. This Java Virtual Machine is not to be confused with the SAP JVM that is used by SAP systems based on SAP NetWeaver Java or SAP NetWeaver ABAP+Java (dual stack).

javaThis directory is divided into several subdirectories that contain the upgrade configuration xml files, the log files generated during a release upgrade process, migration data, data models, and other.

Back to Quick Guide [page 17].

3.2 Technical Details of the Update ProcedureNOTEThis section is relevant if you perform an enhancement package installation or SPS update.

The Software Update Manager uses a deployment-based procedure to update Java systems. No shadow system is required for this update procedure. The procedure is highly automated with minimum user interaction.

NOTEFor portal systems only: You can apply Support Package Stacks, single component updates, and perform testing activities to your portal system using the near-Zero Downtime Maintenance for SAP NetWeaver Portal (nZDM for Portal) tool, with significantly reduced downtime. This standalone tool is used in conjunction with SUM.The nZDM for Portal supported releases and minimum SPS levels are: SAP NetWeaver 7.0 including enhancement package 2 SPS11 SAP NetWeaver 7.3 SPS07 SAP NetWeaver 7.3 including enhancement package 1 SPS02 SAP NetWeaver 7.4 SPS02For more information about the process, see the nZDM for Portal documentation at: http://service.sap.com/sltoolset.

3 Planning3.2 Technical Details of the Update Procedure

2013-08-12 CUSTOMER 29/132

The complete update procedure is divided into roadmap steps. In these roadmap steps, the following actions take place: Welcome

The Software Update Manager analyzes whether your SAP system is a dual-stack system or an ABAP or Java standalone system. According to the result, the GUI is assembled. You always see the Monitor tab page, and either the ABAP or Java tab page or both.

Specify CredentialsIn the Specify Credentials roadmap step, you enter the password for the adm user.

Select TargetIn the Select Target roadmap step, you enter the location of the download directory and the stack configuration file.

Confirm TargetIn the Confirm Target roadmap step, you enter the keyword for the update.

Execute Process...The Execute Process... roadmap step automatically triggers the next stage of the update process. This roadmap step is broken down into the following roadmap steps: Initialization

The update GUI is assembled. You always see the Monitor tab page. According to the result of the previous roadmap steps, you also see either the ABAP or Java tab page or both.

ExtractionThe Software Update Manager extracts the required software.

ConfigurationIn the Configuration roadmap step, you enter additional information required for the update procedure such as system users and passwords.

ChecksThe Software Update Manager checks if your system fulfills the requirements for the update procedure (for example, whether the required free space is available).

PreprocessingFor a Java standalone system, no special actions are performed by the Software Update Manager in the Preprocessing roadmap step.

ExecutionIn this roadmap step, the Software Update Manager updates your system. The roadmap step runs without any user interaction.

PostprocessingThe Software Update Manager generates statistical data. The roadmap step runs without any user interaction.

FinalizationFor a Java standalone system, no actions take place in the Finalization roadmap step.

3 Planning3.2 Technical Details of the Update Procedure

30/132 CUSTOMER 2013-08-12

SummaryThe Software Update Manager displays a simple feedback form directly in the GUI and prompts you to send your feedback to SAP for technical analysis.


3.3 Technical Details of the Upgrade ProcedureNOTEThis section is only relevant if you perform a release upgrade.

To upgrade a Java system, the Software Update Manager 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 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.

NOTEWhen upgrading SAP NetWeaver Portal systems, you can use the Deployment Optimization Option (DOO) of the Software Update Manager to remove unnecessary usage types. To use this option, you must send a special request to the SAP Development Team using a support ticket to have a specialized stack file created. For more information, see SAP Note 1759081.

The complete upgrade procedure is divided into roadmap steps. In these roadmap steps, the following actions take place: Welcome

The Software Update Manager analyzes whether your SAP system is a dual-stack system or an ABAP or Java standalone system. According to the result, the GUI is assembled. You always see the Monitor tab page, and either the ABAP or Java tab page or both.

Specify CredentialsIn the Specify Credentials roadmap step, you enter the password for the adm user.

Select TargetIn the Select Target roadmap step, you enter the location of the download directory and the stack configuration file.

Confirm TargetIn the Confirm Target roadmap step, you enter the keyword for the upgrade.

Execute Process...The Execute Process... roadmap step automatically triggers the next stage of the upgrade process. This roadmap step is broken down into the following roadmap steps: Initialization

3 Planning3.3 Technical Details of the Upgrade Procedure

2013-08-12 CUSTOMER 31/132

The upgrade GUI is assembled. You always see the Monitor tab page. According to the result of the previous roadmap steps, you also see either the ABAP or Java tab page or both.

ExtractionThe Software Update Manager extracts the required software.

ConfigurationIn the Configuration roadmap step, you enter all the information required for the upgrade procedure such as system users and passwords, information about the Support Packages that you want to include, and information about the shadow system.

ChecksThe Software Update Manager 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.

PreprocessingThe Software Update Manager imports the substitution tables and performs the online deployment.When the Preprocessing roadmap step is finished and you choose Next, the downtime starts.

ExecutionThe 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 Software Update Manager converts application tables and data to match the target release layout. In addition, it switches the SAP kernel.

PostprocessingThe Software Update Manager saves the log files and prompts you to start with certain follow-up activities.The Software Update Manager also deletes the shadow schema and some obsolete AS Java directories.

FinalizationThe Software Update Manager enables you to clean up tables that are no longer required and completes the upgrade.

SummaryThe Software Update Manager displays a simple feedback form directly in the GUI and prompts you to send your feedback to SAP for technical analysis.


3.4 Update of NWDI-Driven System LandscapesIf you want to update 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

3 Planning3.4 Update of NWDI-Driven System Landscapes

32/132 CUSTOMER 2013-08-12

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 update sequence of software applications in a system landscape.For more information about the maintenance process for NWDI-driven system landscapes, see the SAP Library [page 15] for your target release at:Release Path to SAP LibrarySAP NetWeaver 7.4

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

SAP NetWeaver 7.3/ 7.3 including enhancement package 1

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

SAP NetWeaver 7.0 /7.0 including enhancement package 1, 2 or 3

SAP Library SAP NetWeaverSAP NetWeaver by Key CapabilitySolution Life Cycle Management by Key CapabilitySoftware Life-Cycle Management Software LogisticsWorking with the Development InfrastructureAdministration of the Development InfrastructureMaintenance of NWDI-Driven System Landscape

Below, a brief overview of the steps from an update perspective is given.The update process for development and consolidation systems differs from the update 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 update of the quality assurance or production system.

CAUTIONYou can only update a quality assurance or production system if you provide adjusted SCAs for all components that you modified in the source release system.

Prerequisites The NWDI system (the central system that controls the runtime systems) has a Support Package

Stack level of at least SAP NetWeaver 7.0 SPS 05. Only valid for: Target Release = SAP NetWeaver 7.3;SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.4 |

The runtime systems have a Support Package Stack level of at least SAP NetWeaver 7.0 SPS 05.End of: Target Release = SAP NetWeaver 7.3;SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.4 |

Only valid for: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |The runtime systems have a Support Package Stack level of at least SAP NetWeaver 04 SPS 16.End of: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

You have performed the preparation steps described in the SAP Library documentation under Maintenance of NWDI-Driven System Landscape.


2013-08-12 CUSTOMER 33/132

ProcessOnly valid for: Target Release = SAP NetWeaver 7.3;SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.4 |1. During the Configuration roadmap step, the Software Update Manager detects that the system you

want to update is configured as a runtime system in an NWDI track.2. Update of development (DEV) and consolidation (CONS) systems

1. The components that you have modified are not deployed but only transported to the NWDI transport directory. The Software Update Manager deploys only the software components that are not modified.

2. After the update, you take the modified components from the NWDI transport directory and perform the modification adjustments using the NWDI. You then deploy the adjusted software components (SCs) to the updated development or consolidation system.

3. In the consolidation system, you assemble the modified SCs as software component archives (SCAs).

3. Update of quality assurance (QA) and production (PROD) systemsDuring the update of quality assurance and production systems, the Software Update Manager deploys the new versions of the modified components that you have built in the consolidation system together with all software components that are not modified.

End of: Target Release = SAP NetWeaver 7.3;SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.4 |Only valid for: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |1. During the Configuration roadmap step, you specify whether the system that you want to update is

configured as a runtime system in an NWDI track. If this is the case, you also specify whether the system is a development system (DEV), consolidation system (CONS), quality assurance system (QA), or production system (PROD).

2. Update of development (DEV) and consolidation (CONS) systems1. After you have entered the path to the NWDI transport directory, the Software Update

Manager copies all SAP components included in the shipment to this directory.2. Any components that you have modified in the source release have the status Managed by

NWDI on the selection screen for the target release components.These components are not deployed during the update.

3. After the update, 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 updated development or consolidation system.

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

3. Update of quality assurance (QA) and production (PROD) systemsDuring the update of quality assurance and production systems, the Software Update Manager deploys the modified components that you have built in the consolidation system. In the


34/132 CUSTOMER 2013-08-12

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 into the deployment.

End of: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |Back to Quick Guide [page 17].

3.5 Update of Distributed and High Availability SystemsRelease upgrade only (switch-based): SUM supports the automated upgrade of additional application server instances if the following prerequisites have been met:1. The cluster is homogeneous, that is, the platform and operation system are the same in all

application server instances.2. The paths to the kernel directory and its structure are the default paths, that is, they have not been

changed.3. Make sure SAP Host Agent is installed on all hosts, or install it where required. Alternatively, the

upgrade will proceed as described for SAP NetWeaver 2004.EHP installation or SPS update: The Software Update Manager can handle distributed configurations where your SCS instance is installed on a separate host (for example, in a high availability environment).For information about updating your system in a high availability environment, contact your HA solution implementation partner.

ProcessThe update process for a high availability system is briefly outlined below:1. If necessary, you change your HA system configuration and clean up profiles (see Preparing the Update

of Distributed and High Availability Systems [page 49]).2. You start the Software Update Manager on the host with the primary application server instance.3. The Software Update Manager checks the profile directory and, if the SCS instance is installed with

a different host name, assumes that the update runs in a distributed or high availability environment.

4. Release upgrade only (switch-based): At the end of the downtime, you start the SCS instance manually and then the primary application server instance as described in Performing Actions at the End of the Downtime [page 71].

For more information about high availability, see http://scn.sap.com/community/business-continuity.Back to Quick Guide [page 17]

3 Planning3.5 Update of Distributed and High Availability Systems

2013-08-12 CUSTOMER 35/132

4 Preparation

This part of the document contains information about the preparations that you need to make before you update your system. You can prepare for the update while the system is in production operation. Careful preparation of the update is the best guarantee that it runs without errors.

CAUTIONIn addition to the general preparations described in this document, you need to perform the preparations that are specific to your product version, which are described in an additional product-specific document. This document is referenced in the Master Guide (or Upgrade Master Guide, respectively) for your product.

The Software Update Manager supports you here by making most of the necessary checks automatically. For more information about the checks performed by the Software Update Manager, see the descriptions in Running the Software Update Manager [page 53].ActionsYou perform the following actions before you start the Software Update Manager: Determining the Host for the Preparations [page 38] Checking the Hardware Requirements [page 39] Checking the Software Requirements [page 39]

Release upgrade and enhancement package installation: Checking the Source Release of the SAP System [page 40]

Meeting the Operating System-Specific Requirements [page 41] Release upgrade only: Upgrade of the Operating System and Database System: Overview [page 42] Only valid for: Source Release = SAP Web AS 6.40 |

Release upgrade only: Checking the Software Delivery Manager Version [page 43]End of: Source Release = SAP Web AS 6.40 |

Only valid for: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |Checking the Memory and JVM Settings [page 44]End of: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

Only valid for: Target Release = SAP NetWeaver 7.0 EHP3 |Installing SAP JVM [page 44].End of: Target Release = SAP NetWeaver 7.0 EHP3 |

Making Preparations at the Database Level [page 45] Enhancement package installation or SPS update: Updating Database Statistics [page 45] Cleaning Up the Profile Directory [page 45]

4 Preparation

2013-08-12 CUSTOMER 37/132

Configuring OS User Authentication [page 45] Only valid for: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40 |

Making Preparations in the Monitoring Area [page 46]End of: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40 |

Only valid for: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |Setting the Public Substitution Variable [page 46]End of: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

Only valid for: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3;SAP NetWeaver 7.0 SR3 |Enhancement package installation or SPS update on SAP NetWeaver 7.0-based system: Synchronizing the Database and the SDM Repository [page 47]End of: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3;SAP NetWeaver 7.0 SR3 |

Filling the Download Directory [page 47] Ensuring the Correct Kernel Directory Detection [page 48] Preparing the Update in Distributed and High Availability Systems [page 49] Only valid for: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

Changing Passwords and Updating the Secure Store [page 49]End of: Target Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

Installing or Updating SAP Host Agent [page 50]Back to Quick Guide [page 17]

4.1 Determining the Host for the PreparationsYou need to prepare for the update on the host with the primary application server instance.

ProcedureDecide which hosts you need for the update preparation and the actual update of the SAP system: Host with the primary application server instance

You must execute the update on the host where the primary application server instance is running. The SL Controller also runs on this host.

Other hostsThe Software Update Manager GUI can run on any hosts that meet the necessary requirements.

Database hostYou must perform the actions that affect the database on the database host.

User Management Engine hostThe remote instance host where the User Management Engine (UME) is located must be running.NOTEThe SL Controller steers the back-end program that performs the update. This program has to run on the primary application server instance. In contrast to the SL controller, the Software

4 Preparation4.1 Determining the Host for the Preparations

38/132 CUSTOMER 2013-08-12

Update Manager GUI is the user interface of the Software Update Manager that can run on any host.


4.2 Checking the Hardware RequirementsProcedureCPU, Main Memory, Disk, and Swap SpaceCheck 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.Release upgrade only: To plan technical upgrades (without functional extensions), see the information about performing a delta sizing for upgrades on SAP Service Marketplace at:http://service.sap.com/sizing Sizing Guidelines .

Space Requirements in the File SystemMake sure that there is enough temporary disk space available in the file system for the update. You need this free space for the SUM directory and the download directory. As the space requirements depend on the product, see the document with additional product-specific information for your update procedure to find information about the requirements. This document is referenced in the Master Guide or Upgrade Master Guide, respectively.

Space Requirements in the DatabaseMake sure that enough temporary and permanent free space is available in your database.Release upgrade only: For information about extending the database, see Quick Guide [page 17].Enhancement package installation or SPS update: The Software Update Manager takes the status of your database into account and calculates the exact space requirements.You can recover the difference between the minimum disk space requirements and the permanent disk space requirements by deleting the old substitution tablespaces.


4.3 Checking the Software RequirementsYou must meet certain software requirements before you update the SAP system.1. Release upgrade only: Check the source release [page 40] of the SAP system.2. Meet the operating system-specific requirements [page 41].3. Release upgrade only: If necessary, upgrade the operating system and database system [page 42].

4 Preparation4.2 Checking the Hardware Requirements

2013-08-12 CUSTOMER 39/132

4. Only valid for: Source Release = SAP Web AS 6.40 |Release upgrade only: Check the Software Delivery Manager Version [page 43].End of: Source Release = SAP Web AS 6.40 |

5. Only valid for: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |Check the memory and JVM settings [page 44].End of: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

6. Only valid for: Target Release = SAP NetWeaver 7.0 EHP3 |Install SAP JVM [page 44].End of: Target Release = SAP NetWeaver 7.0 EHP3 |


4.3.1 Checking the Source Release of the SAP SystemNOTEThis section is only relevant if you perform a release upgrade or enhancement package installation.

Your SAP system must have one of the source releases that have been released for this update and apply to all databases. For information about the supported source releases, see the document with additional product-specific information, which is referenced in the Master Guide (or Upgrade Master Guide, respectively) for your product.Different SAP NetWeaver usage types may have different minimum Support Package levels. If you update an SAP NetWeaver-based system containing various usage types, make sure that your source release is on any acceptable Support Package level for all usage types implemented in the system.

NOTEThe Software Update Manager will check whether your source release is supported for this update.Only valid for: Source Release = SAP Web AS 6.40 |If you are upgrading an SAP system based on SAP NetWeaver 2004, the minimum required Support Package Stack level is SPS15.End of: Source Release = SAP Web AS 6.40 |

CAUTIONIf you have to apply Support Packages to your source release shortly before the update, check whether the equivalent Support Package for the target release is already available. Otherwise, this may delay your update schedule.

ProcedureProcedure for Java SystemsTo determine the source release and Support Package Stack level of your SAP system, proceed as follows:1. Go to the AS Java start page: http://:/index.html2. Choose System Information.

4 Preparation4.3 Checking the Software Requirements

40/132 CUSTOMER 2013-08-12

3. Log on to AS Java as user Administrator.The current release and Support Package level are displayed under Version in the Software Components table.

Back to Quick Guide [page 17].

4.3.2 Meeting the Operating System-Specific RequirementsProcedureOnly valid for: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

All Supported Operating SystemsDepending on which SAP product and database you use, 32-bit systems and 64-bit systems are supported by the Software Update Manager. For more information, see the Product Availability Matrix (PAM) on SAP Service Marketplace at http://service.sap.com/PAM.End of: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |Only valid for: Target Release = SAP NetWeaver 7.1;SAP NetWeaver 7.2;SAP NetWeaver 7.3;SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.4 |

All Supported Operating SystemsRelease upgrade: Only 64-bit systems are supported by the Software Update Manager. For information about which operating systems are supported, see the Product Availability Matrix (PAM) on SAP Service Marketplace at http://service.sap.com/PAM.End of: Target Release = SAP NetWeaver 7.1;SAP NetWeaver 7.2;SAP NetWeaver 7.3;SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.4 |

AIXNOTEThis is only relevant if you perform a release upgrade.

Check the C++ runtime level with the following commands: AIX 6.x:

#lslpp L xlC.aix61.rteThe output must be at least 10.1.0.0.

#lslpp L xlC.rteThe 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.

LinuxSAP Kernel 7.01 or higher: For RHEL 4 and SLES 9, you need to install additional operating system packages. For more information, see SAP Note 1021236.


2013-08-12 CUSTOMER 41/132

HP-UXSee SAP Note 837670 to check the minimum operating system patch recommendations for HP-UX.


4.3.3 Upgrade of the Operating System and Database System: Overview

When you update the SAP system, you may have to upgrade your operating system and database to a new version. For more information about which versions are currently supported, see the Product Availability Matrix on SAP Service Marketplace at http://service.sap.com/PAM. The Software Update Manager only checks the minimum versions required for the update.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.Only valid for: Target Release = SAP NetWeaver 7.1;SAP NetWeaver 7.2;SAP NetWeaver 7.3;SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.4 |

CAUTIONYou must migrate the operating system and database to 64-bit before the upgrade.SAP only supports systems based on 64-bit on the target release. Make sure that you plan enough time in your upgrade schedule for the migration.

End of: Target Release = SAP NetWeaver 7.1;SAP NetWeaver 7.2;SAP NetWeaver 7.3;SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.4 |Only valid for: Target Release = SAP NetWeaver 7.1;SAP NetWeaver 7.2;SAP NetWeaver 7.3;SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.4 |

RECOMMENDATIONIf you need to change the hardware, we recommend that you use the SAP System Copy procedure to migrate to 64-bit. For more information about system copy, see the installation documentation on SAP Service Marketplace.

End of: Target Release = SAP NetWeaver 7.1;SAP NetWeaver 7.2;SAP NetWeaver 7.3;SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.4 |

ProcessOracleFor information about the procedure, see the document Upgrade to Oracle Database : on SAP Service Marketplace at http://service.sap.com/instguides

Database Upgrades Oracle .Proceed as follows:


42/132 CUSTOMER 2013-08-12

1. You install the Oracle client software for the target release. For more information about this procedure, see SAP Note 819829.

2. You run the Software Update Manager up to the Checks roadmap step and analyze the results.Roadmap step Checks informs you about the minimum version for the operating system and database.If necessary, upgrade the operating system.If you have not already done so, migrate the Oracle database as described in the document Upgrade to Oracle Database : to at least the minimum required version.

3. You upgrade the SAP system.

Back to Quick Guide [page 17]Only valid for: Source Release = SAP Web AS 6.40 |

4.3.4 Checking the Software Delivery Manager VersionNOTEThis section is only relevant if you perform a release upgrade.

NOTEThis section only applies if your source release is based on SAP NetWeaver 04.

The upgrade requires at least Software Delivery Manager (SDM) version 6.40 Support Package 15. If you have a lower SDM version, you need to update SDM before you start the Software Update Manager.

Procedure1. Download the SDM Support Package from SAP Service Marketplace at http://

service.sap.com/patches A - Z Index N SAP NETWEAVER SAP NETWEAVER 04Entry by Component Application Server Java SAP Software Delivery Manager 6.40 #OS independent .1. The Support Package files are displayed on the Downloads tab page.

Select the required file named J2EERT_.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_-.SAR J2EE-RUNT-CD/SDM/SDMKIT.JAR

2. Update SDM:1. Go to the SDM installation directory (the default directory is /usr/sap//

/SDM/program).2. Stop SDM by entering the following command

./StopServer.sh3. Set SDM to operate in standalone mode by entering the following command:


2013-08-12 CUSTOMER 43/132

./sdm.sh jstartup mode=standalone4. Copy SDMKIT.jar to the temporary folder .5. In , extract SDMKIT.jar with the following command:

jar -xvf SDMKIT.JAR6. Execute the script ./update.sh7. When prompted, enter the SDM installation directory.

In a standard installation, this is /usr/sap///SDM/program.8. Switch to the SDM installation directory.9. Set SDM to operate in the integrated mode by entering the following command:

./sdm.sh jstartup mode=integrated10. Start SDM by entering the following command:

./StartServer.shBack to Quick Guide [page 17]End of: Source Release = SAP Web AS 6.40 |Only valid for: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

4.3.5 Checking the Memory and JVM SettingsProcedureFor information about memory requirements and Java Virtual Machine (JVM) settings, see SAP Note 723909 and the SAP Notes for each supported Java Development Kit (JDK) referenced in this SAP Note.Back to Quick Guide [page 17]End of: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |Only valid for: Target Release = SAP NetWeaver 7.0 EHP3 |

4.3.6 Installing SAP JVMBefore you start the update process, you have to ensure that SAP JVM 4.1 is installed in your system.

PrerequisitesYour database is up and running.

ProcedureDownload and install SAP JVM 4.1 as described in the document Installation Guide SAP JVM Switch Tool, which you can find on SAP Service Marketplace at:http://service.sap.com/instguides SAP JVM Switch Tool

Back to Quick Guide [page 17]End of: Target Release = SAP NetWeaver 7.0 EHP3 |


44/132 CUSTOMER 2013-08-12

4.4 Making Preparations at the Database LevelProcedure


4.5 Updating Database StatisticsUpdating the database statistics is an optional step. However, we recommend that you perform this step, as it can significantly improve the performance of the update process.

PrerequisitesThe database is up and running.

ProcedureUpdating Database Statistics for Oracle1. Log on as user ora to the host where the database instance is running.2. Open a command prompt and execute the following command:

brconnect -u / -c -f stats -t all -o SAPEXAMPLEbrconnect -u / -c -f stats -t all -o SAPQO1DB

For more information, see SAP Notes 1017324 and 554031.


4.6 Cleaning Up the Profile DirectoryBefore starting the Software Update Manager, you need to clean up the profile directory. Remove any old, unused profiles and move any backup copies to another directory. The profile directory must only contain active profile files. By default, it is located in the central file share:/sapmnt/Back to Quick Guide [page 17]

4.7 Configuring OS User AuthenticationProcedureTo ensure that the user authentication used by SUM is working and the restart operations during the update are successful, you must configure the OS user authentication correctly before starting SUM.Apply SAP Note 927637 and the OS-specific SAP Notes attached to it.

4 Preparation4.4 Making Preparations at the Database Level

2013-08-12 CUSTOMER 45/132

NOTEBe aware that after you apply this SAP Note correctly, you will get a warning inside the sapcpe log file notifying you that the sapuxuserchk executable cannot be overwritten. You can ignore this warning.

Back to Quick Guide [page 17]Only valid for: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40 |

4.8 Making Preparations in the Monitoring AreaProcedureAs of SAP NetWeaver 7.0 including enhancement package 2, the agents infrastructure has changed significantly. Before the update, 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 15] for your target release at:Release Path to SAP LibrarySAP NetWeaver 7.3 / 7.3 incl. enhancement package 1 / 7.4

Function-Oriented View Solution Life Cycle Management Solution MonitoringMonitoring 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.0x to 7.1x or higher

SAP NetWeaver PI 7.1/ 7.1 including enhancement package 1

Function-Oriented View Application Server ABAP Administration Tools for AS ABAPMonitoring 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.1

SAP NetWeaver 7.0 including enhancement package 3

Function-Oriented View Solution Life Cycle Management by Key Capability Solution Monitoring Monitoring in 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.0x to 7.1x or Higher

SAP NetWeaver 7.0 including enhancement package 2

Function-Oriented View Solution Life Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS Infrastructure of the SAP NetWeaver Management Agents

Technical Background of the SAP NetWeaver Management Agents CCMS Agents: Upgrade of Monitored Systems to NW 7.0 EhP 2

Back to Quick Guide [page 17]End of: Source Release = SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40 |Only valid for: Target Release = SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2;SAP NetWeaver 7.0 EHP3 |

4.9 Setting the Public Substitution VariableBefore you start with the update process, you need to set the public substitution variable com.sap.cm.share in the SDM configuration.

4 Preparation4.8 Making Preparations in the Monitoring Area

46/132 CUSTOMER 2013-08-12

ProcedureProceed as described in the SAP Library [page 15] for your target release at:

SAP Library SAP NetWeaver SAP NetWeaver Developer's Guide Fundamentals Using JavaCore Development Tasks Deployment: Putting It All Together Software Deployment Manager SDM Remote GUI

Client SDM Repository Management D

sum108 java+unix+oracle copy

Documents

software update manager555

software update manager

update of distributed

update of nwdi

update procedure

software requirements

java update process

database system