Updating SAP Java Systems on UNIX and Linux: SAP MaxDB

Upgrade Guide | PUBLICSoftware Update Manager 1.0 SP26Document Version: 1.0 – 2021-02-15

Updating SAP Java Systems on UNIX and Linux: SAP MaxDB

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 About This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Before You Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.3 Accessing SAP NetWeaver Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 Quick Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1 Tool Information: Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

SL Common User Interface (SL Common UI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18SL Common UI Elements and Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19SL Common UI: Getting Support Using the Support File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23SUM Observer Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Communication Between Back-End Processes and the SL Common UI. . . . . . . . . . . . . . . . . . . .25SUM Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

3.2 Technical Details of the Update Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283.3 Technical Details of the Upgrade Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293.4 Update of NWDI-Driven System Landscapes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.5 Updating Distributed and High Availability (HA) Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.1 Determining the Host for the Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.2 Checking the Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.3 Checking the Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Checking the Source Release of the SAP System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Checking the Consistency Between the Primary Application Server Instance ID and the Box Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Meeting the Operating System-Specific Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Upgrade of the Operating System and Database System: Overview. . . . . . . . . . . . . . . . . . . . . . .41Update Approach for JCE Policy Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

4.4 Security and Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.5 Making Preparations at the Database Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.6 Updating Database Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .434.7 Ensuring Required Database Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .444.8 Cleaning Up the Profile Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.9 Checking the SAPLOCALHOST Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2 PUBLICUpdating SAP Java Systems on UNIX and Linux: SAP MaxDB

Content

4.10 Configuring OS User Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.11 Making Preparations in the Monitoring Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.12 Filling the Download Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.13 Meeting Kernel-Related Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.14 Preparing the Update of High Availability Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.15 Ensuring the Validation of the Java Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5 Running the Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .515.1 Meeting the Requirements for the SUM Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.2 Downloading and Unpacking the Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.3 Registering SUM in SAP Host Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545.4 Starting and Restarting the Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555.5 Starting the SUM Observer Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.6 Resetting the Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585.7 Using the Alert Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.8 Using Breakpoints During the Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615.9 Making Entries for the Specify Authentication Mechanism Roadmap Step. . . . . . . . . . . . . . . . . . . . 625.10 Making Entries for the Select Target Roadmap Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.11 Making Entries for the Confirm Target Roadmap Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.12 Making Entries for the Configuration Roadmap Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Making Basic Entries for the Java Update Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Making Entries for the Target System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Removing or Migrating par Archives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.13 Making Entries for the Checks Roadmap Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.14 Performing Actions Before the Beginning of the Downtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.15 Performing Actions at the End of the Downtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.16 Evaluating the Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.17 Running the Software Update Manager for Another Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.18 Stopping the Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705.19 Performing an Automated Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

6 Follow-Up Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736.1 Performing Follow-Up Activities for User root. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .736.2 Performing Follow-Up Activities in the Monitoring Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746.3 Performing Follow-Up Activities for SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756.4 Deleting Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

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

7.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777.2 Quick Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777.3 Filling the Manually Prepared Download Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797.4 Running the Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBContent PUBLIC 3

Meeting the Requirements for the SUM Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Downloading and Unpacking the Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . .82Registering SUM in SAP Host Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83Starting and Restarting the Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Resetting the Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Using the Alert Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Using Breakpoints During the Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Making Entries for the Specify Authentication Mechanism Roadmap Step. . . . . . . . . . . . . . . . . .89Making Entries for the Select Target Roadmap Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Making Entries for the Confirm Target Roadmap Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Making Entries for the Configuration Roadmap Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Performing Actions Before the Beginning of the Downtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Performing Actions at the End of the Downtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Evaluating the Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Storing Current SUM Data for Future Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

8 Installing Additional Usage Types (Technical Usages) in an Existing SAP System. . . . . . . . . . . 958.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958.2 References to Maintenance Planner Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958.3 Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958.4 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968.5 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .968.6 Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978.7 Deactivation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

9 Correction of Installed Software Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009.2 Making Entries for the Select Target Roadmap Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

A Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102A.1 Process Overview Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102A.2 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

SL Common UI: Solving Problems with the UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Update Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Correcting Errors in the DEPLOY_ONLINE_* Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Correcting Problems in the DEPLOY_* Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Correcting Errors in the RUN_OFFLINE_MIGRATION Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Reentering Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110Using the SUM Forced Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Starting and Stopping the AS Java Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Correcting InstanceID Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112


Content

A.3 List of Referenced SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113A.4 List of Referenced Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBContent PUBLIC 5

Document History

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

CautionBefore you start, make sure that you have the latest version of this document. You can find the latest version on the SAP Support Portal at http://support.sap.com/sltoolset . Choose tab System Maintenance, then the scenario Software Update/Upgrade using SUM Software Update/Upgrade with SUM 1.0 SP 26 .

Document: Updating SAP Systems with SUM 1.0 SP26

Version Date Description

1.0 2021-02-15 Initial version


Document History

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fsltoolset

1 Introduction

1.1 About This Document

Purpose

This document describes how to update SAP systems based on SAP NetWeaver Java using the Software Update Manager (SUM) 1.0 SP26.

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, installing add-ons, or updating single components. For clarity and readability, the term “update” is used in this document for all supported processes.

For more information about the Software Update Manager, see the blog Software Update Manager (SUM): introducing the tool for software maintenance on the SAP Community Network.

For more information about the supported maintenance procedures and update paths, see the current Software Update Manager Note 2882395 and its attachments.

Integration

This document only contains information about the Software Update Manager tool and the update procedure using this tool, as well as about some actions directly related to basic SAP NetWeaver functionality.

It is essential that you read the Master Guide (or Upgrade Master Guide, if such exists as a separate document) 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, access the SAP Help Portal for your SAP NetWeaver release. See also Accessing SAP NetWeaver Library [page 12].

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBIntroduction PUBLIC 7

http://help.sap.com/disclaimer?site=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Fit-management%2Falm%2Fsoftware-logistics%2Fblog%2F2012%2F11%2F07%2Fsoftware-update-manager-sum-introducing-the-tool-for-software-maintenance


http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2882395

How to Use this Document

RecommendationWe recommend that you use the Quick Guide [page 13] 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. The types of bars are the following:

● With regular thickness when they are only valid for individual paragraphs within the topic● In bold and placed directly below the title of a topic when they are valid for the entire content of the

topic

The document is structured as follows:

● Chapter 1 – IntroductionThis chapter contains information about using this document, an overview of new features available in the latest SUM versions, some naming conventions, and lists some 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 13].

● 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 applying 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 installing additional usage types or technical usages in an existing SAP system based on SAP NetWeaver Java.

● Chapter 9 – Correction of Installed Software InformationThis chapter contains information about correcting and updating the details of the software instances installed in your SAP system.

● Appendix○ Process Overview Report

Contains information about the reports that are generated by the SUM to analyze the update procedure.

○ TroubleshootingContains information about known problems and troubleshooting them.

○ List of Referenced SAP NotesLists all SAP Notes with additional information about the update procedure that are referenced in this document besides the SAP Notes [page 11] 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.


Introduction

1.2 Before You Start

1.2.1 Naming Conventions

Update

In 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 Tools

The 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 <Update Directory>

In this document, “SUM directory” and “<update directory>” are used as synonyms when referring to <path to SUM directory>/SUM.

SAP System

In 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 ID

In this document, the SAP system ID is abbreviated as “SAPSID” or “sapsid”. If “<sapsid>” is used, your SAP system ID has to be in lowercase letters, for example, “prd”. If “<SAPSID>” is used, you have to 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 “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 Instances

As of SAP NetWeaver 7.1, the concept and naming of SAP system instances has changed. The terms “central instance” and “dialog instance” are no longer used. Instead, the SAP system consists of the following instances:

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

● Central services instance● Database instance

Throughout 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 Name

In this document, <instance_name> is used as a placeholder for the instance name in the instance directory path of your system.

Substitute <instance_name> with J<xx> for the primary or additional application server instance, where <xx> stands for the instance number.

Step and Phase

In this document, in some scenarios the term “phase” is used as a synonym of the term “step”. This is done in alignment with the Software Update Manager UI, which, when regarding Java scenarios, distinguishes these terms on a technical level.

Usage Type, Technical Usage, and Product Instance

As of SUM SP12, the term “product instance” has replaced the terms “usage type” and “technical usage” for SAP systems based on SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information,


Introduction

see SAP Note 1877731 . Note that there is no terminology change for older releases and all mentioned terms can be used as synonyms. As this is a generic update document, the currently used terms remain but only “product instance” will be used from now on when referring to SAP NetWeaver 7.3 EHP1 and higher.

Only valid for 'Platform': Oracle Solaris

Solaris and Oracle Solaris

As of operating system version 10, Solaris has been renamed to “Oracle Solaris”. However, the former name “Solaris” may occur in this document as well.

End of 'Platform': Oracle Solaris

1.2.2 SAP Notes

Use

To 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 (http://support.sap.com/notes ), some of which you have to 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 Update

You have to request the following SAP Notes from SAP Support Portal before you start the update procedure:

● Central Software Update Manager Note● SAP Note for your database

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

SAP Notes Required to Prepare the Update

SAP Note Number Description

2882395 Central Software Update Manager Note

2937237 SAP MaxDB-specific



http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fnotes




Other SAP Notes

In 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 113].

1.3 Accessing SAP NetWeaver Library

Before, during and after the update, you require the SAP online documentation for SAP NetWeaver. The applicable paths to the SAP NetWeaver Library (http://help.sap.com ) regarding the SAP NetWeaver versions mentioned in this document are as follows:

SAP Library Paths

Release Path

SAP NetWeaver 7.5 http://help.sap.com/nw75


SAP NetWeaver 7.3 including enhancement package 1

http://help.sap.com/nw731









For more information about accessing this documentation, see the product-specific document for your target release.


Introduction

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnw75








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 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 gain a quick overview of the update procedure.

Checklist

SAP Notes

This document is enhanced and updated by SAP Notes from SAP Support Portal (http://support.sap.com/notes ). 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 11]. You require at least the following SAP Notes:○ Central Software Update Manager Note 2882395○ The relevant database-specific SAP Note 2937237

Additional Documentation

Before, 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 12].

Update Planning

Before you start the actual update, you have to 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 17] and the update procedure.Technical Details of the Update Procedure [page 28].Release upgrade only: If you require more detailed information, see Technical Details of the Upgrade Procedure [page 29].

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBQuick Guide PUBLIC 13





☐ 2. You plan the update of NWDI-driven system landscapes [page 31].☐ 3. You plan the update of distributed and high-availability systems [page 32].

Update Preparation

You 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 and Using the Software Update Manager

☐ 1. You choose the host [page 36] for the preparations.☐ 2. You check the hardware requirements [page 36]:

○ CPU, main memory, disk and swap space - see https://www.sap.com/about/benchmark/sizing.html

The 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. Note that the exact amount of space is dependent on the size of the download directory used for your scenario. A general minimum is the size of the download directory multiplied by 3. 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 for the database:The Software Update Manager calculates the space requirements for the database. The free space required is in the range from 50 to 200 GB.

☐ 3. You check the software requirements:○ Release upgrade and enhancement package installation: Source release [page 38] of the SAP system○ Operating system-specific requirements [page 40].○ You plan or perform the upgrade of the operating system and database system [page 41], if

necessary. For information about which operating system and database versions are currently supported, see the Product Availability Matrix on SAP Service Marketplace at https://support.sap.com/release-upgrade-maintenance/pam.html .

○ Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3You check the consistency between the primary application server instance ID and the box number [page 39].End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

○ You check the update approach for JCE policy files [page 42].☐ 4. (Optional) You take note of the recommended authentication and security considerations [page 42].☐ 5. You make the preparations at the database level [page 43].☐ 6. You update the database statistics [page 43].☐ 7. If necessary, you clean up the profile directory [page 44].☐ 8. You check the SAPLOCALHOST settings [page 45].☐ 9. You configure the OS user authentication [page 45].


Quick Guide

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwww.sap.com%2Fabout%2Fbenchmark%2Fsizing.html


http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Frelease-upgrade-maintenance%2Fpam.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Frelease-upgrade-maintenance%2Fpam.html

☐ 10. Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1You make the preparations in the monitoring area [page 45].End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1

☐ 11. You fill the download directory [page 46].☐ 12. You meet kernel-related prerequisites [page 47].☐ 13. You perform the specific preparations for distributed and high availability systems [page 48].☐ 14. You ensure the validation of the Java Administrator [page 49].

Update Procedure

Actions for Starting and Using the Software Update Manager

☐ 1. You meet the requirements for the SUM directory [page 53].☐ 2. You download and unpack the Software Update Manager [page 53].☐ 3. You register SUM in SAP Host Agent [page 54].☐ 4. You start the Software Update Manager [page 55].☐ 5. You can start the SUM Observer Monitor [page 57] in a second browser window or on a mobile device.☐ 6. You can reset [page 58] the update if needed.

In addition, you can configure the alert function [page 59] to notify you when user action is required.☐ 7. You can use breakpoints during the update [page 61].

Making Entries for the Specify Authentication Mechanism Roadmap Step

You continue with roadmap step Specify Authentication Mechanism [page 62] and make the corresponding entries.

User Actions During the Select Target Roadmap Step

You continue with roadmap step Select Target [page 63] and make the corresponding entries.

User Actions During the Confirm Target Roadmap Step

You continue with roadmap step Confirm Target [page 63] and make the corresponding entries.

User Actions During the Configuration Roadmap Step

You continue with roadmap step Configuration [page 64].

In order to continue, 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 64].☐ 2. Release upgrade only: You make entries for the target system configuration [page 65].☐ 3. Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2

Release upgrade (switch-based) only, for portal systems only: You make selections for removing or migrating par archives [page 66].End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2

User Actions During the Checks Roadmap Step

You continue with roadmap step Checks [page 67] 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.

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBQuick Guide PUBLIC 15

☐ 2. Before the downtime [page 67] begins, you are asked to make the necessary backups and perform additional actions.

Actions During the Execution Roadmap Step

While 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 69].

Actions During the Summary Roadmap Step

☐ 1. You evaluate the Software Update Manager [page 69].☐ 2. You make preparations to run the Software Update Manager for another update [page 70].☐ 3. You stop the Software Update Manager completely [page 70].

Automated Update

If you perform a release upgrade, EHP installation, or an SPS update, you can automate the process as described in Performing an Automated Update [page 71]

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 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 73].☐ 2. You perform follow-up activities in the monitoring area [page 74].☐ 3. Release upgrade only: You perform follow-up activities [page 75] for SAP Solution Manager.☐ 4. For data protection and privacy reasons, you delete log files [page 76] that are not needed anymore.


Quick Guide

3 Planning

This part of the document contains information about planning your SAP system update. Before you begin the actual update, you have to 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 13]:

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

Actions

The following sections are important for planning the update:

● Tool Information: Software Update Manager [page 17]○ SL Common User Interface (SL Common UI) [page 18]○ SL Common UI Elements and Options [page 19]○ SUM Observer Monitor [page 24]○ Communication Between Back-End Processes and the SL Common UI [page 25]○ SUM Directory [page 26]

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

3.1 Tool Information: Software Update Manager

The following sections provide you with important information about the update program Software Update Manager (SUM):

● SL Common User Interface (SL Common UI) [page 18]● SL Common UI Elements and Options [page 19]● SL Common UI: Getting Support Using the Support File [page 23]● SUM Observer Monitor [page 24]

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBPlanning PUBLIC 17

● Communication Between Back-End Processes and the SL Common UI [page 25]● SUM Directory [page 26]

3.1.1 SL Common User Interface (SL Common UI)

The SL Common User Interface (SL Common UI) is used when you perform an update with SUM. The UI provides all functions for monitoring and navigating through the roadmap steps of the update procedure. The complete procedure consists of several roadmap steps that contain phases, which in turn consist of the individual steps.

As it is based on the SAP UI Development Toolkit for HTML5 (SAPUI5), which is a client-side rendering library, the SL Common UI does not require any Java components. It provides a rich set of standard and extension controls, a lightweight programming language, and a high level of customization.

The benefits of SAPUI5, and thus of the SL Common UI, are the following:

● Zero foot print (no installation requirements)● Only a browser is required.● You can view logs in the browser window.● You can open the current phase list from the UI.● You can maintain breakpoints in the browser window.● You can change processing parameters during the runtime of the Software Update Manager using the web

browser.

Prerequisites for Using the SL Common UI

● SUM has been configured for the use with SAP Host Agent as described in Configuring SAP Host Agent Authentication and SSL Connection [page 42].

● Supported web browsers:○ Microsoft Edge (latest release, not using compatibility view)○ Microsoft Internet Explorer 11 and higher (not using compatibility view)○ Google Chrome (latest release)○ Mozilla Firefox (latest release)

RecommendationWe strongly recommend that you always use the latest available web browser release.

NotePlease note that Internet Explorer 11 will not support future SAPUI5 versions starting with SAPUI5 1.88. For more information, see the corresponding blog in the SAP Community .

If you encounter issues with the SL Common UI during the SUM process, check the topics related to the SL Common UI in Troubleshooting [page 103].


Planning

http://help.sap.com/disclaimer?site=https%3A%2F%2Fblogs.sap.com%2F2021%2F01%2F13%2Fupdate-future-sapui5-versions-will-no-longer-support-microsofts-legacy-browsers%2F

3.1.2 SL Common UI Elements and Options

This section describes the different elements and options of the SL Common UI that you can use during an update or a migration.

On the user interface, you see the different roadmap steps and a progress bar indicating how much of the current roadmap step has already been processed (in percent). In addition, the UI offers several options, menus, and buttons that are helpful for your update.

SL Common UI Overview

Second Progress Bar

The duration of the different phases within a roadmap step can vary significantly. If long-running phases start within the roadmap step, the SL Common UI displays in addition a second progress bar that is only valid for this current phase. This supports you in estimating the progress of this long-running phase.


In the following, you see an example of a second progress:

Example of Second Progress Bar

Options: Task List, Logs, and Breakpoints

The right-hand side of the UI offers you the options Task List, Logs, and Breakpoints.

● Task ListBy using the task list, you can view the status of the current, preceding, and subsequent steps or phases of the procedure. The icons used in the Task Type and the Status rows are described in the legend.

● LogsYou can open an overview of the available log files for the current step or phase. By choosing Description, you can sort the list and use the filtering functionality to search for specific log files. The icons for the log file format are described in the legend.

NoteAlternatively, you can access the log files on file system level:

○ <SUM directory>/sdt/log

Some phases or steps generate log files in the subdirectories of the log directory, so you might still need file system access to analyze them.

● BreakpointsSUM offers the possibility to use breakpoints, which allow you to pause the update procedure at a specified point. A list of the breakpoints is displayed. By choosing Description, you can sort the list and use the


Planning

filtering functionality to search for breakpoints. The icons for the breakpoint status are described in the legend. For more information, see Using Breakpoints During the Update [page 61].

Menus: Legend, More

In the upper-right corner of the UI, you find the menus Legend and More.

Legend

The legend explains the meaning of the icons used for the different types and status of the tasks in the task list, the status of the breakpoints, and the format of the log files (for example, text or HTML).

Legend for Task List, Logs, and Breakpoints

More

With this menu, you can get support or more information, or log out from the browser session. Depending on the update procedure status, different options are offered.


The More menu

● LogoutLogs you off the current browser session. Note that the update procedure itself continues running in the background. To log on again, proceed as described in Starting the SL Common UI [page 55].

● Toggle Color SchemaSwitches the high-contrast color schema on or off.

● SUM GuideOpens the main Web page for the current Software Update Manager guides.

● SUM NoteOpens the central SAP Note for the current Software Update Manager version.

● SAP Help PortalOpens the SAP Help Portal, which contains SAP product documentation and other related information such as SAP Notes, product availability information, and community content.

● ExitNote that this option is not always available in the menu. It stops and exits the current update process and displays the initial dialog of the SL Common UI ("Tool start required"). If you choose Exit at this point, you also terminate the Java process on the server and stop with that SUM completely. An appropriate message on the SL Common UI appears, and you can close the web browser page.Alternatively, you can restart the Software Update Manager by refreshing the web browser page or by clicking on the offered link in the message. You can continue from the point where you chose Exit

● ResetNote that this option is not always available in the menu. It sets the system to a state that allows the update procedure to be restarted from the beginning.This option is only available during resettable phases, but not anymore at the end of a successful update procedure without DMO. For more information, see Resetting the Update [page 58].


Planning

● CleanupNote that this option is not always available in the menu. It cleans up the SUM directory. This option is only available at the end of a successful update procedure or after you have chosen Reset. At the end of a successful update procedure, a cleanup prevents the execution of a reset afterwards. On the other hand, after a reset has finished successfully, the cleanup is obligatory. See also Resetting the Update [page 58].

● Log TailOpens the log tail viewer for selected log files. In a pop-up window, the chosen log file is reloaded and displayed at short time intervals. You can pause the display to check some log lines.

● Get Support FileCreates an XML file for SAP Support when you have problems with the user interface. For more information, see SL Common UI: Getting Support Using the Support File [page 23].

● AboutDisplays information about the current versions of the Software Update Manager, the Software Logistics Protocol, and the Software Logistics UI Client.

Note● Be aware that some options of the Utilities can only be used during the update procedure if the

corresponding data is available in the system.● The Exit, Reset, and Cleanup options are not always available. SUM offers them only if the status of the

update allows it.● A further option Debug is only available for SAP Support and used for debugging.

Buttons

During the update, the buttons Back, Next, and Cancel are displayed depending on the current step or phase and dialog.

If you encounter an issue during the update procedure such as aborts or errors, the Software Update Manager displays in some cases the buttons Repeat or Init, or both. Init means basically that the current phase will be initialized again and restarted. However, this varies depending on the phase. Due to several restrictions or limitations, it can also happen that only certain processes of a phase will be repeated again and not the whole phase. If you choose Repeat, the current process within a phase will be repeated from the point where update procedure stopped.

3.1.3 SL Common UI: Getting Support Using the Support File

Context

The SL Common UI offers you the possibility to create support files. This might be necessary if you have problems with the user interface during the update procedure, and the possible solutions described in SL Common UI: Solving Problems with the UI [page 104] do not fix the problem.


You create a support file and supply it to SAP Support in order to receive assistance. Proceed as follows:

Procedure

1. On the SL Common UI, choose More Get Support File .

A new browser window opens.2. Save the file locally. Do not copy and paste content.3. Provide the file to SAP Support, for example, by e-mail.

3.1.4 SUM Observer Monitor

The Software Update Manager offers an additional SL Common UI mode that is called the observer mode, and it is displayed as the SUM Observer Monitor.

The SUM Observer Monitor is a kind of non-admin mode or guest mode of the SL Common UI that allows you to monitor a current update procedure and provides you with information about its status. You cannot enter data or change the update procedure.

The SUM Observer Monitor can be used in browsers on different devices, such as a desktop PC or a mobile device. In the following, see the different examples of the user interface:

In the following, you see an overview of the SUM Observer Monitor in a browser window on a desktop PC:

SUM Observer Monitor in a Browser Window on a Desktop PC

In the following, you see an example of the SUM Java Observer Monitor on a mobile device.


Planning

For more information about starting the observer monitor, see Starting the SUM Observer Monitor [page 57].

3.1.5 Communication Between Back-End Processes and the SL Common UI

As a prerequisite, you need to configure the Software Update Manager for use with the SAP Host Agent.

You start the SL Common UI by entering the URL relevant for your platform technology in the address bar of a browser. This action connects the browser with the Software Update Manager by means of the SAP Host Agent. You can connect from a client machine, or from the same host. By default, the SL Common UI uses the standard protocol HTTPS (for a secure connection) and port 1129 of the SAP Host Agent. SUM then calls internally the relevant executables, which carry out the update steps.


Communication Between Browser and the Instance Where SUM is Running

3.1.6 SUM Directory

The Software Update Manager creates the SUM directory on the host where the tool is initially started, and copies data and programs into this directory.

NoteAfter the directory has been created, ensure that the SUM directory contains all software archives calculated by Maintenance Planner and mentioned in the stack.xml file that will be required for the update procedure.

The recommended standard path of the SUM directory is:

/usr/sap/<SID>/SUM

CautionEnsure to prevent unauthorized access to the SUM directory!

The SUM directory has the following subdirectories:

● sdt● jvm

Each subdirectory might contain files and further subdirectories:

● sdtContains the SL controller.Contains the following subdirectories:○ clean_backup

Contains backup of the htdoc subdirectory.


Planning

○ configContains configuration xml files for the update.

○ controlContains configuration xml files for the upgrade.

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

○ 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, 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).

3.2 Technical Details of the Update Procedure

NoteThis section is relevant if you perform an enhancement package installation, SPS update, or installing an add-on.

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.

When you install add-ons, use the procedure relevant for their delivery method:

● Add-ons delivered through a stack.xml configuration file are installed by the procedure described in Running the Software Update Manager [page 51].

● Add-ons delivered through software archives without a stack.xml are installed by using the procedure described in Applying Single Component Updates and Patches Using a Manually Prepared Directory [page 77].

NoteSAP Enterprise Portal, BPM, and PO, and MII systems: While performing maintenance activities, you can significantly reduce the downtime of your portal by using the near-Zero Downtime Maintenance Java (nZDM Java) tool in conjunction with SUM.

The nZDM Java supported source releases and minimum SPS levels are:

● Only valid for 'Source Release': SAP NetWeaver 7.0 EHP 2Portal systems only: SAP NetWeaver 7.0 including enhancement package 2 SPS11End of 'Source Release': SAP NetWeaver 7.0 EHP 2

● SAP NetWeaver 7.3 SPS07● SAP NetWeaver 7.3 including enhancement package 1 SPS02● SAP NetWeaver 7.4● SAP NetWeaver 7.5

For more information about the process, see the nZDM Java documentation at: https://support.sap.com/en/tools/software-logistics-tools.html System Maintenance near-Zero Downtime Maintenance (nZDM) for Java 1.0 <version> Guide for nZDM for Java .

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

● WelcomeThe 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.


Planning

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Ftools%2Fsoftware-logistics-tools.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Ftools%2Fsoftware-logistics-tools.html

● Specify Authentication MechanismIn the Specify Authentication Mechanism roadmap step, you enter the password for the <sid>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 verify that the target version for your update is correct.

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

● SummaryThe Software Update Manager displays a simple feedback form directly in the SL Common UI and prompts you to send your feedback to SAP for technical analysis. For more information, see Evaluating the Software Update Manager [page 69].

3.3 Technical Details of the Upgrade Procedure

NoteThis 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 as described in SAP Note 1759081 . For an overview, see http://scn.sap.com/community/it-management/alm/software-logistics/blog/2012/11/07/software-update-manager-sum-introducing-the-tool-for-software-maintenance .

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

● WelcomeThe 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 Authentication MechanismIn the Specify Authentication Mechanism roadmap step, you enter the password for the <sapsid>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 verify that the target version for your update is correct.

● 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

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.

○ Postprocessing


Planning




The 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 SL Common UI and prompts you to send your feedback to SAP for technical analysis. For more information, see Evaluating the Software Update Manager [page 69].

3.4 Update of NWDI-Driven System Landscapes

Use

If 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 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 12] for your target release at:

SAP Library Paths

Target Release Path in SAP Library

SAP NetWeaver 7.3 / 7.3 incl. EHP1 / 7.4 /7.5

Application Help Function-Oriented View <Language> Solution Life Cycle

Management Using the Development and Production Infrastructure

Development Infrastructure (DI) Maintenance 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 'Source Release': SAP NetWeaver 7.0Only valid for 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5The runtime systems have a Support Package Stack level of at least SAP NetWeaver 7.0 SPS 05.End of 'Source Release': SAP NetWeaver 7.0End of 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

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

Process

Only valid for 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

1. Early in the procedure, the Software Update Manager detects if the system you want to update is configured as a runtime system in an NWDI track.

2. Update of development (DEV) and consolidation (CONS) systems1. 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) systems

During 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 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

3.5 Updating Distributed and High Availability (HA) Systems

This section provides you with information about the update of distributed or high availability (HA) systems.

Context

Distributed Systems

The Software Update Manager is able to handle distributed configurations where your ASCS instance or other ABAP instances are installed on separate hosts as, for example, in a HA environment.


Planning

For heterogeneous systems, that is, systems that have different operating systems on the primary and additional application server instances, you have to perform manual actions. Provide at least the target kernel for the remote instances at the download directory. As a prerequisite, the SAP kernel directory of the system must follow the new layout (/usr/sap/<SID>/SYS/exe/uc/<platform>) and the SAP kernel replication with program sapcpe needs to be configured.

During the downtime, the Software Update Manager operates only with a local single-instance setup while all other instances are stopped. At this point of the update procedure, the Software Update Manager moves all the central services (enqueue service and message service) to the downtime instance. At the end of the downtime and before starting the productive system again, the original system setup will be restored and started afterwards.

High Availability Systems

The update of high availability systems differs from updates of distributed systems. Newer system offers the usage of the HA Maintenance Mode during upgrade, but for older systems there is still manual action required. For more information about updating your system in an HA environment, contact your HA solution implementation partner.

Note● Only valid for 'Platform': AIX

AIX systems: If you want run SUM in an HA environment controlled by IBM PowerHA, see also SAP Note 2431737 .End of 'Platform': AIX

● Only valid for 'Platform': HP-UXHP-UX systems: If you want run SUM in an HPE Serviceguard Cluster environment on HP-UX systems, see also SAP Note 1779681 .End of 'Platform': HP-UX

● If you want run SUM in an HA environment on systems with NEC EXPRESSCLUSTER® X 3.3, see also the document SAP NetWeaver System Configuration Guide, chapter 8 SAP NetWeaver Update. You can find it using the following web address: http://www.nec.com/en/global/prod/expresscluster/en/support/Setup.html .

Maintenance Mode:

Before an update in a system environment with high availability, you must deactivate the HA solution for the clustered resources to prevent the HA software from interfering with the upgrade process. After the upgrade, the HA solution must be activated again. That is, the HA software must be told that maintenance mode must be switched on (deactivation of HA solution) or switched off (activation of HA solution) for an instance or the entire SAP system (without the database).

This can be carried out manually or automatically if the Software Update Manager supports the automatic execution of the deactivation and activation of the HA solution. The feature can be activated during the update by the selecting the checkbox Use of Maintenance Mode, if an availability check beforehand was successful. Note that you don't have to perform any manual steps such as starting or stopping instances and services, when you use this mode.

For more information about this feature and how to check whether the automatic maintenance mode is available, see SAP Note 2464065 .

Below, you find briefly outlined the update process for a high availability (HA) system.




http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.nec.com%2Fen%2Fglobal%2Fprod%2Fexpresscluster%2Fen%2Fsupport%2FSetup.html

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.nec.com%2Fen%2Fglobal%2Fprod%2Fexpresscluster%2Fen%2Fsupport%2FSetup.html


Procedure

1. If necessary, you change your HA system configuration and clean up profiles.

For more information, see section Preparing the Update of Distributed and High Availability Systems [page 48].

2. You start the Software Update Manager.3. The Software Update Manager checks the profile directory. If the SCS instance is installed on a different

host name, the tool assumes that the update is performed in a distributed or HA environment.


Planning

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 51].

Actions

You perform the following actions before you start the Software Update Manager:

● Determining the Host for the Preparations [page 36]● Checking the Hardware Requirements [page 36]● Checking the Software Requirements [page 37]

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

○ Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3Checking the Consistency Between the Primary Application Server Instance ID and the Box Number [page 39]End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

○ Meeting the Operating System-Specific Requirements [page 40]○ Release upgrade only: Upgrade of the Operating System and Database System: Overview [page 41]○ Update Approach for JCE Policy Files [page 42]

● Security and Authentication [page 42]● Making Preparations at the Database Level [page 43]● Enhancement package installation or SPS update: Updating Database Statistics [page 43]● Ensuring Required Database Connections [page 44]● Cleaning Up the Profile Directory [page 44]● Checking the SAPLOCALHOST Settings [page 45]● Configuring OS User Authentication [page 45]● Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1

Making Preparations in the Monitoring Area [page 45]End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1

● Filling the Download Directory [page 46]● Meeting Kernel-Related Prerequisites [page 47]● Preparing the Update of High Availability Systems [page 48]● Ensuring the Validation of the Java Administrator [page 49]

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBPreparation PUBLIC 35

4.1 Determining the Host for the Preparations

Context

You must prepare for the update on the host, on which the Software Update Manager will run.

NoteIn the following cases, ensure that the User Management Engine (UME) in the ABAP stack, which also contains the Java users, is up and running during the whole update procedure:

● f you update either stack of your dual-stack ("dual-usage") system separately, by performing two consecutive single-stack SUM runs.

● If you update a Java-only system that has its Java users in an ABAP UME.

As this is a shared resource between the ABAP and Java stacks, if the UME is not up and running the Java part of the SUM process might fail.

Procedure

Decide which hosts you need for the update preparation and the actual update of the SAP system:

○ Host on which the Software Update Manager will runDepending on the source release, the Software Update Manager has to run on:○ Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

SAP NetWeaver 7.0-based systems: the primary application server instanceEnd of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

○ SAP NetWeaver 7.1 and higher: the host on which you want to run the tool. It can be either the primary application server instance or an additional instance.

○ Database host - you have to perform the actions that affect the database on the database host.

4.2 Checking the Hardware Requirements

CPU, Main Memory, Disk, and Swap Space

Check whether you have sufficient hardware resources such as CPU, main memory, disk space, and swap space. The minimum swap space is 20 GB.

For more information about sizing, see the SAP Portal at https://www.sap.com/about/benchmark/sizing.html.


Preparation



Space Requirements for the File System

Make 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. We recommend at least 40 GB free space for the SUM directory as well as for the download directory.

As the space requirements depend on the product, see also 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 Database

Make sure that enough temporary and permanent free space is available in your database.

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

Enhancement package installation or SPS update: The Software Update Manager takes the status of your database into account and calculates the exact space requirements.

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 update is complete.

4.3 Checking the Software Requirements

You have to meet certain software requirements before you update the SAP system.

1. Release upgrade and enhancement package installation: Check the source release [page 38] of the SAP system.

2. Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3Check the consistency between the primary application server instance ID and the box numberoperating system and database system upgrade [page 39].End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

3. Meet the operating system-specific requirements [page 40].4. Release upgrade only: If necessary, upgrade the operating system and database system [page 41].5. See the update approach for JCE Policy files [page 42].


4.3.1 Checking the Source Release of the SAP System

Use

NoteThis section is relevant if you perform a release upgrade or enhancement package installation.

Your SAP system should 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 product instances may have different minimum Support Package levels. If you update an SAP NetWeaver-based system containing various product instances, make sure that your source release is on any acceptable Support Package level for all product instances implemented in the system.

NoteThe Software Update Manager will check whether your source release is supported for this update.

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.

Procedure

Procedure for Java Systems

To 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://<host name>:<port>/index.html2. Choose System Information.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.


Preparation

4.3.2 Checking the Consistency Between the Primary Application Server Instance ID and the Box Number

This topic is only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

Context

When the primary application server instance is created during the SAP system installation, the tool that creates the instance configuration in the configuration manager generates a string, which is called “box number”. It is used as the basis for calculating the primary application server instance ID.

For the update of an SAP system, it is essential that you have not changed the primary application server instance ID and the box number or, if you have changed them, that they are still consistent. This is a prerequisite for the correct installation of the shadow instance and for proper migration.

To check the consistency of the primary application server instance ID and the box number of the system that you want to update, download the instanceidcheck.jar tool attached to SAP Note 1987497 . For additional information, see SAP Note 2259748 .

Procedure

1. Download the tool instanceidcheck.jar from SAP Note 1987497 to your computer.

2. Enter the following command with the required parameters from the directory to which you have downloaded the tool:

java -cp instanceidcheck.jar com.sap.sdt.check.InstanceIdChecker <instance-id> <instance-number> <instance-box-number>

The parameters are as follows:

○ <instance-id>: This is the primary application server instance ID, which you determine it as follows:Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3Open the file /usr/sap/<SID>/<instance-name>/j2ee/cluster/bootstrap/bootstrap.properties and search for the value of the instance.prefix property.End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

Only valid for 'Source Release': SAP NetWeaver 7.1, SAP NetWeaver 7.2, SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5Open the primary application server instance profile /usr/sap/<SID>/SYS/profile/<SID>_<instance-name>_<host> and search for the value of the j2ee/instance_id entry.End of 'Source Release': SAP NetWeaver 7.1, SAP NetWeaver 7.2, SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

○ <instance-number>: This is the primary application server instance number. For example, if the instance name is JC12, then the instance number is 12.

○ <instance-box-number>: This is a string used by the installation to calculate the instance ID. To determine the box number, open the file /usr/sap/<SID>/<instance-name>/j2ee/cluster/instance.properties and search for the value of the instance.box.number property.





3. Check the results:○ The following message is displayed if the box number was changed without changing the primary

application server instance ID:WARNING!!! The source system ID that you provided is different than the one calculatedIn this case, reset the box number to its original value.

○ If no message is displayed, the system is consistent with regards to the primary application server instance ID and the box number.

End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

4.3.3 Meeting the Operating System-Specific Requirements

All Supported Operating Systems

For information about which operating systems are supported, see the Product Availability Matrix (PAM) on SAP Service Marketplace at http://support.sap.com/pam .

AIX

Depending on your target release, you require specific minimum C++ runtime level and according minimnum SAP kernel version. To check them, proceed as described in SAP Note 1780629 . For additional AIX-related recommendations, see SAP Note 1972803 .

Linux

Check the minimum SAP kernel requirements for your operating system in SAP Note 1563102 .

HP-UX

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

UNIX-based Operating Systems: Setting Limits for System Users

To avoid errors during the update, ensure that the system user limits are set optimally. To do this, proceed as described in SAP Note 1704753 .


Preparation

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fpam






4.3.4 Upgrade of the Operating System and Database System: Overview

Use

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 Support Portal at http://support.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.

NoteAs of SAP NetWeaver 7.1, SAP only supports systems based on 64-bit on the target release. If you have to migrate the operating system and database to 64-bit, make sure that you plan enough time in your upgrade schedule for the migration, and perform the migration before the upgrade.

If 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 System Copy Guide on SAP Support Portal at http://support.sap.com/sltoolset System Provisioning System Copy Option .

NoteMake sure that your current database version is supported for your scenario. See the following SAP Notes to check the minimum database version for updates to

● SAP NetWeaver 7.4 SPS08 and higher: 1951491● SAP NetWeaver 7.5 and higher: 2158828

Process

SAP MaxDB

Prerequisite for starting the Software Update Manager: If the database server and the primary application server instance are not identical, install the latest DB client software on the primary application server instance.

For more information about the procedure, see the documents about upgrading SAP MaxDB on the SAP Community WIKI pages at https://wiki.scn.sap.com/wiki/x/gjc .

Proceed as follows:

1. If you have not already done so, you upgrade the database to at least the minimum required major version. For information about the required major version, see the Product Availability Matrix (PAM) for you target release on SAP Support Portal at http://support.sap.com/pam .






http://help.sap.com/disclaimer?site=https%3A%2F%2Fwiki.scn.sap.com%2Fwiki%2Fx%2Fgjc


2. We recommend that you apply the latest SAP MaxDB patch even if your system already fulfills the required major version. SAP MaxDB patches are available for download on SAP Service Marketplace at: https://support.sap.com/swdc Download Support Packages and Patches Entry by Application GroupAdditional Components MaxDB .

3. You run the Software Update Manager up to the Checks roadmap step and analyze the results.4. If necessary, you upgrade the operating system.5. You upgrade the SAP system.

4.3.5 Update Approach for JCE Policy Files

If your system has Java Cryptography Extension (JCE) Unlimited Strength Policy files, you have to manually replace them with their latest version after the update is completed. You have to do this to prevent compatibility issues that might occur.

You can aquire the latest version of the JCE policy files from their vendor website. For more information, see SAP Note 1240081 .

4.4 Security and Authentication

Security

RestrictionWe strongly discourage using network monitoring tools during the SUM procedure. That is, any tools that analyze network traffic of data packages should be disabled or removed from the instance where SUM is running. The technology used by such tools might allow third parties to monitor sensitive information transmitted through the loopback interface, for example, data transferred between different processes of the update.

User Authentication

NoteEnsure that the latest available SAP Host Agent version is installed in your system.

As a SUM option, you can choose to not enter user credentials during the update. If you do so, implement the recommendations in SAP Note 1642340 .

Enabling SSL over HTTP for connecting with Software Update Manager


Preparation

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fswdc




SUM can operate over a connection that uses Secure Socket Layer (SSL) technology. In addition to the security benefits, setting up SSL is a prerequisite for SUM to operate without you manually entering user credentials, which is an alternative to the standard validation approach.

To enable this, configure SAP Host Agent as described for your operating system at http://help.sap.com, search for SSL Configuration for the SAP Host Agent, and in the results page filter by entering your product and version in the Product field.

Enabling SSL over P4 Protocol

Proceed as follows for your system to enable the usage of the protocol P4 over SSL:

● Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3For SAP NetWeaver 7.0-based releases: Using P4 Protocol Over a Secure Connection End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

● For SAP NetWeaver 7.3-based and higher: Adding New SSL Access Points

4.5 Making Preparations at the Database Level

Currently there are no preparation steps required for this database when it is running on a Java-only system.

4.6 Updating Database Statistics

Use

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

Prerequisites

The database is up and running.

Procedure

Updating Database Statistics for SAP MaxDB


http://help.sap.com

http://help.sap.com/saphelp_nw70ehp1/helpdata/de/4d/6e71798ba22a49ae6ef4987588a1bd/frameset.htm

https://help.sap.com/saphelp_nw73/helpdata/en/ee/de34e6754f4caaa5f73f38d9bde3f7/content.htm

1. Log on as user sqd<dbsid> to the host where the database instance is running.2. Open a command prompt and execute the following command:

dbmcli -d <DBSID> -u control,<pwd> sql_updatestat SAP<SID>DB.\*

Exampledbmcli -d QE1 -u control,ctrlpwd sql_updatestat SAPQE1DB.\*

4.7 Ensuring Required Database Connections

You have to ensure that the database can provide a sufficient number of simultaneous connections for your AS Java. We recommend at least 4 additional connections to the ones already required by the AS Java.

To check how many connections your AS Java is configured for, proceed as follows:

1. Start the configtool.2. Navigate to the dbpool service.3. Check the sysDS.maximumConnections, and adjust it accordingly if required.

To check how many simultaneous connections your MaxDB database is set to provide, proceed as follows:

1. Open the SAP MaxDB Database Studio.2. Navigate to the MAXUSERTASKS parameter, and adjust it accordingly if required.

For more information about simultaneous connections in MaxDB, see SAP Note 1173395 .

4.8 Cleaning Up the Profile Directory

Context

Before starting the Software Update Manager, you need to clean up the profile directory. The profile directory should only contain active profile files. By default, it is located in the central file share:

/sapmnt/<SID>

Procedure

Remove any old, unused profiles and move any backup copies to another directory.


Preparation


4.9 Checking the SAPLOCALHOST Settings

To avoid potential issues during the update, you have to check if SAPLOCALOST is set correctly as a profile parameter and environment variable. To do so, check if the settings described in SAP Note 1738760 have been implemented in your system configuration. If this is not the case, perform the listed steps.

4.10 Configuring OS User Authentication

To ensure that the user authentication used by SUM is working and the restart operations during the update are successful, you have to configure the OS user authentication correctly before starting SUM.

Procedure

Apply SAP Note 927637 and the OS-specific SAP Notes attached to it.

NoteBe aware that after applying this SAP Note correctly, you will receive a warning in the sapcpe log file notifying you that the sapuxuserchk executable cannot be overwritten. You can ignore this warning.

4.11 Making Preparations in the Monitoring Area

This topic is only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1

As 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 12] for your target release at:

SAP Library Paths

Release Path in SAP Library

SAP NetWeaver 7.5 Application Help Function-Oriented View <Language> Solution Life Cycle

Management Solution Monitoring 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.0x to 7.1x

or higher

SAP NetWeaver 7.3 / 7.3 incl. EHP 1 / 7.4

Application Help Function-Oriented View <Language> Solution Life Cycle

Management Solution Monitoring Monitoring the CCMS Infrastructure of the SAP


Management Agents CCMS Agents: Upgrade of Monitored Systems from NW 7.0x to 7.1x

or higher

SAP NetWeaver PI 7.1 / 7.1 incl. EHP 1

Application Help Function-Oriented View <Language> Application Server ABAP

Administration Tools for AS ABAP Monitoring the CCMS Infrastructure of the SAP


Management Agents CCMS Agents: Upgrade of Monitored Systems from NW 7.0 to 7.1

End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1

4.12 Filling the Download Directory

You can put all files and software packages with which you want to update your system in a download directory.

Context

During the Select Target roadmap step, you are prompted to enter the path to the stack configuration XML file that has to be available in your download directory. The Software Update Manager reads the download directory and moves the files to the appropriate directories from where they are then further processed.

You can put the following files in the download directory:

● Support Package stacks for the target release● Enhancement packages● Add-on components● SAP kernel for the target release● Stack configuration XML file


Preparation

● Release upgrade only: Archives

NoteRelease upgrade only: If you have Java add-on components installed in your system, check the dedicated upgrade document for information whether to include this component into the download content for your target release, which is calculated by the Maintenance Planner.

CautionMake sure that the files and software packages that you want to include into the upgrade, are located at the top level of your download directory. They should not be located in any subdirectories. This could be the case, for example, when you just copy the upgrade archive files into the download directory.

Procedure

1. Create a download directory. The directory can be located anywhere on your host.2. Put all software packages and files required during the update into the download directory.

4.13 Meeting Kernel-Related Prerequisites

To ensure that the procedure runs correctly, make sure of the following:

● If you have installed two or more systems with different releases on the same host, more than one SAP kernel version exists. Make sure that the kernel path for the system you want to update is listed before all other existing kernel directories in the PATH environment variable.To detect the kernel directory, the Software Update Manager runs various 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 this environment variable.

● Release upgrade only (switch-based): Make sure that the path to the kernel directory is the default path:/sapmnt/<SID>/exe/uc/<platform>

● Make sure that all files in the kernel directory are readable, that is, each of them has at least the permission “r--r—r--” set.


4.14 Preparing the Update of High Availability Systems

This chapter deals with preparatory activities if you want to update your high availability (HA) system.

Context

To update an HA system, implement an HA system configuration as recommended by SAP to create a reliable starting point for the update.

Furthermore, move the cluster group SAP <SAPSID>HA to the cluster node, if the primary application server instance runs on such a node.

Procedure

Create an optimal starting point.

To create a reliable starting point for the update, it is crucial that you implement an HA system configuration as recommended by SAP. Below you can find problems resulting from different configurations and possible solutions:

○ Manually set up standalone enqueue serverThe 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, revert this configuration before the execution of the downtime steps of the update. Revert this configuration before the kernel switch step at the latest. The Software Update Manager is unable to detect a manual setup of standalone enqueue servers and, therefore, cannot update them. This can cause problems when the system is started for the first time after the kernel switch.Only valid for 'Platform': Oracle Solaris

NoteOracle Solaris Cluster 3.3 and lower:

If you are using the old agent SUNW.sapwebas, see SAP note 1835686 for the changes on the system. If you are using the new agent ORCL.ha-netweaver, you do not need to revert changes in this step.


○ Maintain the profile directory.○ Remove any old, unused profiles and backup copies. The directory must contain only active profile

files.○ Do not use links to local profiles with different names. The Software Update Manager can only work

with physical profile files.


Preparation


Only valid for 'Platform': Oracle Solaris

NoteOracle Solaris Cluster 3.3 and 4.x:

To avoid an unwanted failover of resource groups for SAP instances, suspend these resource groups before starting the Software Update Manager, or before the begin of the Execution roadmap step at the latest. To suspend the resource groups and unmonitor the resources, use the following commands:

clrg suspend <resource group of SAP instance>

clrs unmonitor <resource of SAP instance>

clrs unmonitor <resource of the sapstartsrv process of SAP instance>

Perform the above-mentioned commands for all the cluster-controlled SAP instances, including (A)SCS, ERS, PAS (and if under cluster-control, AAS instances). After the downtime, resume the resource groups and monitor the resources for each of the mentioned instances by using the following commands:

clrg resume <resource group of SAP instance>

clrs monitor <resource of SAP instance>

clrs monitor <resource of the sapstartsrv process of SAP instance>

To display the status, enter:

clrg status <resource group>

clrs status –g <resource group>


4.15 Ensuring the Validation of the Java Administrator

Context

To prevent connectivity issues caused by an incorrect validation of the Java Administrator, you have to verify that the P4 procotol has been configured correctly.

Procedure

1. In а command prompt оr PowerShell, execute the following command:

netstat –ano | grep 5<Instance number>04

NoteDepending on your UNIX-based release, netstat commands might differ. For example, for some HP-UX versions the -o might have to be omitted.


Wait for the output status. If you receive the status Listen, P4 has been configured correctly and no additional steps are required.

2. If the output status is not Listen, configure the P4 protocol as described for your SAP NetWeaver release:

P4 Protocol Configuration

Release Path

7.0-based systems SAP Note 609603 - Problems with Multiple NICs and SAP J2EE Engine

SAP NetWeaver 7.1-based systems and higher http://help.sap.com/saphelp_nwpi711/ System

Administration and Maintenance Information Technical

Operations for SAP NetWeaver General Administration

Tasks Administration of the Internet Communication

Manager Parameterization of the ICM and the ICM

Server Cache Profile Parameters for the ICM and SAP

Web Dispatcher icm/server_port_<xx>


Preparation


http://help.sap.com/saphelp_nwpi711/

5 Running the Software Update Manager

This section provides information about starting and running the Software Update Manager. It describes all required user input and actions, as well as critical points during the update.

Note the following:

● All required planning and preparation actions have to be completed.● The Software Update Manager controls the entire procedure, from checking the system requirements and

importing the necessary programs through stopping production operation until production operation is resumed. The procedure is divided up into a number of different roadmap steps. The roadmap steps are in turn divided into individual steps. The successful completion of a step is a precondition for the success of all subsequent steps.Alternatively, you can use the Process Overview Report [page 102] utility.

● If you install add-ons included in a stack.xml configuration file, use the following procedure. Add-ons that delivered only through software archives without a stack.xml are deployed by using the procedure described in Applying Single Component Updates and Patches Using a Manually Prepared Directory [page 77].

● Depending on the source release, the Software Update Manager has to run on:○ Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3


○ SAP NetWeaver 7.1 and higher: the host, on which you want to run the tool. It can be either the primary application server instance or an additional one.

● To monitor the procedure, you can use the logs created by the Software Update Manager, which are for example accessible on the SL Common UI or with the log tail viewer in the More menu (see also: SL Common UI Elements and Options [page 19]). Or you use the Process Overview Report [page 102] utility.

● Many steps require no user input. In the following, you can find a description of all necessary user input.● User actions are also required when errors occur. If an error occurs, correct it and repeat the step in which

the error has occurred. Once the step has been repeated successfully, you can continue with the update. For more information, see Troubleshooting [page 103].

Prerequisites

Before you run the Software Update Manager, make sure that the following prerequisites are fulfilled:

● Ensure that the communication ports 1128 and 1129 of your system are open, and not blocked by third-party software, such as a firewall. You have to do this to ensure the correct operation of the SAP Host Agent. For more information, see TCP/IP Ports of All SAP Products.

● Your system is up and running, including all system instances and all system processes. Do not stop the system manually. The Software Update Manager stops and starts it when needed.

● You are logged on to the update host as user <sid>adm.

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBRunning the Software Update Manager PUBLIC 51

https://help.sap.com/viewer/ports

● User <sid>adm has the required permissions:The <sid>adm user has to be the owner and have full (xrw) permissions on all files in the /usr/sap/<SID> and /sapmnt/<SID> directories. If symbolic links are used, <sid>adm has to be the owner of these links as well.

● Release upgrade only: You have ensured that the application sap.com/tc~kmc~rf~ummig~rmiapp is running in your system. For more information, see SAP Note 1873529 .

Actions

You perform the following actions to start and use the Software Update Manager:

● Meeting the Requirements for the SUM Directory [page 53]● Downloading and Unpacking the Software Update Manager [page 53]● Registering SUM in SAP Host Agent [page 54]● Starting and Restarting the Software Update Manager [page 55]● Starting the SUM Observer Monitor [page 57]● Resetting the Update [page 58]● Using the Alert Function [page 59]● Using Breakpoints During the Update [page 61]

You perform the following actions during the roadmap steps:

● Making Entries for the Specify Authentication Mechanism Roadmap Step [page 62]● Making Entries for the Select Target Roadmap Step [page 63]● Making Entries for the Confirm Target Roadmap Step [page 63]● Making Entries for the Configuration Roadmap Step [page 64]

○ Making Basic Entries for the Java Update Process [page 64]○ Release upgrade only: Making Entries for the Target System Configuration [page 65]○ Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2

Release upgrade (switch-based) only, for portal systems only: Removing or Migrating par Archives [page 66]End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2

● Making Entries for the Checks Roadmap Step [page 67]● Performing Actions Before the Beginning of the Downtime [page 67]● Performing Actions at the End of the Downtime [page 69]● Evaluating the Software Update Manager [page 69]● Running the Software Update Manager for Another Update [page 70]● Stopping the Software Update Manager [page 70]● Performing an Automated Update [page 71]


Running the Software Update Manager


5.1 Meeting the Requirements for the SUM Directory

Context

If you do not specify a path when you unpack the Software Update Manager package, the SUM directory is automatically created as a subdirectory of the directory where you unpack the software package. However, we recommend that you use the standard path /usr/sap/<SID>.

NoteIf a directory with this name already exists, it has to be empty. Otherwise, the startup of the update fails.

The update directory can be a soft link to another physical directory.

Procedure

Make sure that there is enough free disk space for the SUM directory. This space is required for the update and the logs and is distributed among several subdirectories [page 26]. For an estimation of the disk space needed for the SUM directory, see the update guide that is specific to your product.

5.2 Downloading and Unpacking the Software Update Manager

Procedure

1. Download the latest version of the Software Update Manager from the main Software Logistics Toolset page on the Support Portal at:

http://support.sap.com/sltoolset System Maintenance Software Update Manager (SUM)Download SUM

Notehttps://blogs.sap.com/2015/07/09/maintenance-planner-2/ .

2. Log on as user <sid>adm to the host where you will run the tool.

NoteDepending on the source release, the Software Update Manager has to run on:



http://help.sap.com/disclaimer?site=https%3A%2F%2Fblogs.sap.com%2F2015%2F07%2F09%2Fmaintenance-planner-2%2F

○ Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3SAP NetWeaver 7.0-based systems: The latest version of the Software Update Manager can: the primary application server instanceEnd of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

○ SAP NetWeaver 7.1 and higher: the host, on which you want to run the tool. It can be either the primary application server instance or an additional application server instance.

3. Unpack the Software Update Manager package with the following command:

SAPCAR –xf <download directory>/<path>/<Archive>.SAR -R /usr/sap/<sid>

This command creates the directory SUM under the /usr/sap/<sid> directory. You can also specify another directory. Hereafter, the directory <path to SUM directory>/SUM is referred to as <update directory>.

Note○ Do not unpack SUM in the DIR_GLOBAL directory , as this might lead to issues during the update.○ The complete path to the SUM directory should not exceed 25 characters.○ Do not extract the Software Update Manager to a directory starting with /usr/sap/<any

capital three letters>/ where <any capital three letters> is not the SID of the managed system.

○ If you want to run several updates in parallel on the same host, you have to unpack one SUM instance in each directory of the respective SID directories.For example, if you have the SAP system IDs AB1 and AB2, unpack one SUM instance in the respective directory of each SAP system ID. When starting the SL Common UI, you enter the corresponding SAP system ID in the URL, thus connecting to the corresponding SUM instance. For more information, see Starting and Restarting the Software Update Manager [page 55]. Note that when running several SUM instances using the default location /usr/sap/<sid> is mandatory.

5.3 Registering SUM in SAP Host Agent

Before you start the update, you have to register the Software Update Manager in SAP Host Agent so that the operations and commands to the updated system are executed using SAP Host Agent mechanisms.

Prerequisites

● For a correct execution of the update procedure, make sure that you have installed on all application servers instances the latest version of the SAP Host Agent.Check the SAP Software Download Corner at http://support.sap.com/swdc for the versions that are available to download. For more information, such as the deprecation of lower versions, see SAP Note 2130510 . For additional information regarding SAP Host Agent, see SAP Notes 1031096 and 1907566

.



http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fswdc





● The Secure Socket Layer (SSL) is configured as described in Security and Authentication [page 42].

Procedure

Note● Make sure that you do not run the Software Update Manager during daylight saving time shifts.

Otherwise, the update might fail.● Always perform the procedure from within the SUM directory.

1. (Optional) You can set SUM to omit the system restart that takes place at the end of the update procedure to perform additional maintenance activities, for example, adapting various system settings, integrating third-party software in your landscape, and others. Proceed as follows:1. Navigate to /usr/sap/<SID>/SUM/sdt/param/ and open the startup.props for editing.2. Set the following profile parameter as follows:

skipFinalJ2EERestart = true3. Save and close the file. At the end of the downtime, you are informed that the final system restart has

been omitted, and that you can perform your additional maintenance.Note that after you have finished, you have to manually restart your system.

2. To run the registration of the Software Update Manager in the SAP Host Agent, log on as user root and enter the following command:○ /usr/sap/<SID>/SUM/STARTUP <SID>

5.4 Starting and Restarting the Software Update Manager

This section describes how you start the SL Common UI and the SUM back-end process, or alternatively how you restart SUM if an error, a terminated step, or a system failure occurred.

Prerequisites

● You have met the requirements for the update.● The SAP system and the database have been started.● You have registered SUM in SAP Host Agent as described in Registering SUM in SAP Host Agent [page 54].● The SAPCAR version that is referenced in the environment variable PATH is identical with the one that is

located in the kernel directory. In addition, no reference to any other SAPCAR version should exist in the PATH variable.

● All application server instances and their associated services are up and running.● The P4 protocol is configured to monitor the loopback address of your system as described in Ensuring the

Validation of the Java Administrator [page 49], so that the Java administrator verification is successful.● You have downloaded and unpacked the latest version of the Downloading and Unpacking the Software

Update Manager [page 53] and the software packages that you need for the update.


● When using Internet Explorer, you have to make sure that the URL relevant for your system is listed in the “Trusted” security zone. To do so, proceed as described in the Internet Explorer documentation.

● In the case of a SUM restart, you have corrected the errors as described in section Troubleshooting [page 103].

● To use SUM without entering user credentials, you have configured the SAP Host Agent to operate over an SSL connection as described in Security and Authentication [page 42].

TipAlthough SUM can operate over the http communications protocol, we strongly recommend that you set up your system to use the https communications protocol.

NoteIf you have various systems running on the same application server host, you can start a further Software Update Manager procedure on these systems for system maintenance.

The prerequisite is that the SUM directories remain unchanged and follow the standard path as described in chapter SUM directories.

Procedure

1. Open a web browser window.2. In the address bar, enter the following URL:

https://<fully qualified hostname>:1129/lmsl/sumjava/<SID>/index.html

NoteIf the SSL is not configured, use http instead of https at the beginning of the URL, and use port 1128:

http://<fully qualified hostname>:1128/lmsl/sumjava/<SID>/index.html

3. In the dialog box that appears, enter the user name <sid>adm and the password.

Results

The SAP Host Agent starts the Software Update Manager, and the SL Common GUI of the Software Update Manager is displayed in the web browser.

In the case of a restart, SUM continues from the point where it had previously stopped.



5.5 Starting the SUM Observer Monitor

Proceed as follows to use the SUM Observer Monitor, so that you can monitor the SUM process without interfering in the process.

Prerequisites

● You have created a user <sid>obs and set a password for this user.

CautionFor security reasons, do not use the user <sid>adm for the observer mode.

Linux only: After the system administrator has created the user <sid>obs manually, they have to add it to the sapsys group.

● You have started the Software Update Manager at least one time with the SL Common UI as described in Starting and Restarting the Software Update Manager [page 55].

● You have made sure that the observer progress files SUMOBSERVER.XML or SUMJAVAOBSERVER.XML exist in the subdirectory <SUM directory>/abap/doc .

NoteThe observer mode is configured automatically once you execute the STARTUP script as described in Registering SUM in SAP Host Agent [page 54].

For more information, see SUM Observer Monitor [page 24].

Procedure

1. In the address bar of your browser, enter the following URL:

https://<fully qualified hostname>:1129/lmsl/sumobserver/<SID>/monitor/index.html

○ Replace <SID> with your system ID.○ 1129 is the https port of the SAP Host Agent.○ If the SSL has not been configured, use http instead of https at the beginning of the URL and use port

1128:http://<fully qualified hostname>:1128/lmsl/sumobserver/<SID>/monitor/index.html

2. Enter the observer user <sid>obs and the configured password.


5.6 Resetting the Update

The Software Update Manager offers the option to reset the update.

Prerequisites

● Make sure that the downtime has not yet started.As of the beginning of the downtime, a reset is not possible anymore. To reset the update after the downtime has started, use the system backup created before the SUM process.

Context

When you choose the Reset option of the Software Update Manager, the system is set to a state that allows the update procedure to be restarted from the beginning.

Procedure

Resetting the update procedure on the SL Common UI:a. To reset the update procedure before the beginning of the downtime, choose either Back from the user

interface or Reset from the More menu.

This depends on the phase that the update procedure is currently going through. The update procedure consists of phases that can be reset and of phases that you cannot reset directly. Whenever you are inside a resettable phase, the Software Update Manager offers you a Reset option in the More menu. If not, choose Back repeatedly until you are in a resettable phase and the Reset option appears in the More menu. If the update procedure has not progressed far and you choose Back repeatedly, the Welcome dialog may appear.

After you have chosen Reset, the Software Update Manager indicates afterwards the successful reset procedure and asks you to clean up the SUM directory. Choose Cleanup in the More menu. After the cleanup is completed, the Welcome dialog appears again. You can close the browser window or the browser tab page, or you can start the update procedure from the beginning.

NoteFor more information about the More menu, see SL Common UI Elements and Options [page 19].

b. When the Welcome dialog appears, the system has been fully reverted to its state before the update and you can start the update from the beginning. However, we strongly recommend you ensure that all SUM backend processes are stopped, delete the current SUM directory, and use a newly unpacked SUM before you start over.



NoteWhen you are in an error dialog and you want to reset the update, be aware of the following:

○ Close the browser window or browser tab page when the In progress process execution animation appears. Do not refresh the browser window or tab page, as this might restart the SL Common UI.

○ The Cancel button only stops the SUM background process and the SL Common UI, but does not trigger the reset of the system to its original state. Also, closing the UI tab only closes the user interface.

○ To prevent or correct errors with the reset procedure, see SAP Note 2011380 .

5.7 Using the Alert Function

Use

The alert function of the SL Common UI can be set to send an e-mail or an SMS when user action is required, or when the procedure stops because of errors.

Procedure

To configure the alert function, proceed as follows:

1. In the top right corner of the SL Common UI, choose Alert.



2. Make the required entries:

Alert Configuration Options

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.

ExampleThe 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="[email protected]"

#SUBJECT="EHP Installer Alert"

#EMAIL_ADDRESS="[email protected]"

#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"



Field Entry

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

#cat "$ATTACHED_FILE" | mailx -r "$FROM_ADDRESS" -s "$SUBJECT" "$EMAIL_ADDRESS"

Alert File Absolute path to the alert file that stores the alert message

Alert Delay (in seconds) Time delay between the event and the sending of the notification

Set active (checkbox) Activates the alert function

3. To save your entries, choose OK.

5.8 Using Breakpoints During the Update

You can stop the update procedure at a specified point by using breakpoints.

Setting Breakpoints in the SL Common UI

On the right-hand side of the browser window, the SL Common UI offers you the option to maintain breakpoints from a list of available breakpoints. You can sort, filter, and search for breakpoints. The icons for the breakpoint status are described in the legend.

The breakpoint list displays icons in three different colors:

● Green - breakpoint lies in the past● Orange - breakpoint lies in the currently processed phase● Blue - breakpoint lies in a future phase

After opening the list, it scrolls automatically to a position where the breakpoint of the current phase is listed at the fourth position from the top, if available. You can scroll away from the position, but each time you choose Refresh, the breakpoint list is refreshed and displays the current phase highlighted at the fourth position of the table again.

If SUM stops at a selected breakpoint, it displays a dialog with the options listed below in Options in the Dialog.


Options in the Dialog

NoteDepending on your scenario and system, the available options may vary.

Once you have set a breakpoint, the Software Update Manager stops at that specific point and displays a dialog with the following options:

● Continue executionSUM continues the update automatically until the next breakpoint is reached. Then, the breakpoints dialog is displayed.

● Exit programThe update process stops and you exit SUM. When you restart the update process, the breakpoint dialog appears again.

5.9 Making Entries for the Specify Authentication Mechanism Roadmap Step

Procedure

Enter the password for the <SID>ADM user and choose Next.

Alternatively, if the sapcontrol executable is set up in a way that it does not require user credentials, select the checkbox No authentication with user credentials and choose Next.

Release upgrade only: To be able to use this option in a system with multiple application server instances, proceed as described in Configuring SAP Host Agent Authentication and SSL Connection [page 42].

If you choose to continue the update using user credentials, be aware that it is mandatory to use the <SID>ADM user.

If the OS user credentials for any of the instances in your system do not match the ones that you have already entered for the primary application server instance, you have to specify the correct credentials for each instance on a subsequent screen.

Results

Your administrator user is verified for performing the SUM procedure in the system.



5.10 Making Entries for the Select Target Roadmap Step

Context

The new content is updated with the stack that is available in the download directory. The stack is described in a stack configuration XML file.

If you have downloaded the software packages using the Maintenance Planner, the stack configuration file has been generated automatically and saved to the EPS inbox of SAP Solution Manager. In the Select Target roadmap step, you have to enter the path to the stack configuration file.

CautionIf the stack is located in a share on a different host, make sure that you copy it locally together with the stack configuration XML file and specify the local directory path in this step.

According to the provided stack configuration file, the Software Update Manager checks whether all required packages are available in the download directory. It then creates the deploy queue and validates whether all the dependencies are fulfilled.

Procedure

1. In the Stack File or Directory field, specify the path to the stack configuration XML file.2. If you want to verify the signature authenticity of all SAP-derived software archives that are located in the

download directory, ensure that the Check archive authenticity checkbox is selected.

NoteYou require a valid Certificate Revocation List (CRL), which is placed at the location of the stack.xml configuration file. You can download it from https://tcs.mysap.com/crl/crlbag.p7s .

3. Choose Next.

5.11 Making Entries for the Confirm Target Roadmap Step

Procedure

Confirm the displayed target system version by choosing Next.


http://help.sap.com/disclaimer?site=https%3A%2F%2Ftcs.mysap.com%2Fcrl%2Fcrlbag.p7s

5.12 Making Entries for the Configuration Roadmap Step

This roadmap step asks for all information required to run the update. For clarity, this section is divided into the following subsections:

● Making Basic Entries for the Java Update Process [page 64]● Release upgrade only: Making Entries for the Target System Configuration [page 65]● Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2

For portal systems only: Removing or Migrating par Archives [page 66]End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2

5.12.1 Making Basic Entries for the Java Update Process

Procedure for Enhancement Package Installation and SPS Update

1. Enter the password for the AS Java Administrator user with which you log in to the system.2. A summary of all system parameters that have been detected is displayed. Choose Continue.

Procedure for Release Upgrade

1. Enter the password for the AS Java Administrator user with which you log in to the system.2. Enter the parameters of the shadow system.

The SCS and primary application server instances require instance numbers as technical identifiers for internal processes.

CautionYou should not use these instance numbers anywhere else in your system landscape.

3. A summary of all system parameters that have been detected is displayed. Choose Continue.4. Enter the paths to the required Java DVD.

NoteSL Common UI only: When you are performing a release upgrade and you require DVD media content, you have to provide the path to the content by means reachable by the SL Common UI. Use one of the following approaches:

○ Provide a symbolic link to the drive.○ Copy the DVD media content to a directory on a local drive that is persistent, and provide a path to

this directory.○ Provide a path to a local DVD drive containing the required data. Do not provide a link to a mapped

network DVD drive.

To access the content, provide the fully-qualified domain name (FDQN).



The Software Update Manager extracts the contents into <update directory>/java/data/archives.

5.12.2 Making Entries for the Target System Configuration

Context


The Configuration roadmap step enables you to specify the composition of the target release system.

Procedure

1. Decide how you want to handle the software components during the upgrade.

The Component List 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 delivery. The following information is displayed for each component:

○ Vendor○ Component Name○ Release○ Support Package Level○ Patch Level○ Provider○ Operation

In the Operation column, you can find the action that the Software Update Manager performs for the component as a next step. Some of the operation types are set automatically by the Software Update Manager and others are available as alternatives. The following operation types exist:

○ Deploy – the normal upgrade operation○ Revert – you can assign this operation to a modified or add-on component in your source release that

has a valid successor in the download directory but you do not want to use the successor version in the upgraded system.If you want to revert such a component (for example, a portal component that is subject to 'par to war' migration), proceed as follows:1. Select the Revert option for one or more components.2. Select Continue the process; the displayed component list is correct and complete at the bottom of

the screen.3. Choose Continue.

The List of components to revert dialog is displayed.4. Remove the listed component(s) from the download directory and choose Continue in the List of

components to revert dialog.


As a result, you will be able to assign the Remove, Migrate or Scan inbox operation to the affected add-on/modified components.

○ Scan inbox – assigned to source release components for which the Software Update Manager cannot find any successor, such as customer developments, add-ons, or third-party software. You have to provide a valid successor version for each of these components in your download directory.If you want to update these components, proceed as follows:1. Provide a deployable archive (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 download directory.2. Select Rebuild the component list after scanning the download directory at the bottom of the

screen.3. Choose Continue.

Alternatively, you have the option to assign the Remove operation to these components.○ Remove – assigned to those components that no longer exist in the target release. A component no

longer exists after the upgrade either because it has been deleted, or because it has been integrated into some other component.

○ Migrate – this option is available for deployable archives in your source release that are subject to 'par to ear' migrations and do not have valid successor versions in your download directory.

2. To proceed with the upgrade process, confirm the list of components.

5.12.3 Removing or Migrating par Archives

This topic is only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2

Context

NoteThis section is only relevant if you perform a release upgrade (switch-based).

You can migrate portal system component archives without a successor (for example, third-party components) without using the Software Delivery Manager (SDM). In SUM, the Review and Select par Files for Migration dialog lists all par archives eligible for migration to ear archive type. This procedure is also known as “par to war” migration.

Procedure

1. Select the par archives that you want to migrate to the upgraded system.

2. In the Operation column, choose the operation that the tool will perform on a specified component.○ Migrate – the par archives are converted to ear archives and deployed on the upgraded system.○ Remove – the par archives will not be available in the upgraded system.



Alternatively, you can choose one of the following options:

○ Continue the process; the displayed par files configuration is correct and complete – this option confirms that your selection is completed and that the upgrade process may continue to the next step without refreshing the list.

○ Set all components to Migrate and refresh list – this option sets all listed archives for migration and refreshes the list with this selected operation.

○ Set all components to Remove and refresh list – this option sets all listed archives for removal and refreshes the list with this selected operation.

3. To proceed with the upgrade process, choose Continue.End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2

5.13 Making Entries for the Checks Roadmap Step

Checking the Results of the System Check

At the end of the Checks roadmap step, the Software Update Manager displays the results of the system check. The entries can be error messages, information, or prompts for user actions.

Carry out the user actions before you can start with the Preprocessing roadmap step.

5.14 Performing Actions Before the Beginning of the Downtime

Before the downtime begins, you have to perform the following major preparation steps to ensure a seamless update process. They are:

1. Creating mandatory backups2. Preparing additional application server instances3. Preparing system tools

Creating Mandatory Backups

Before the downtime takes place, you have to ensure that you can recover your SAP system to its original state.

CautionBe aware that you might need these backups to reset your SAP system to its initial state. If you encounter issues during the downtime that you have to revert from, the SAP system cannot be restored without these backups.


1. Back up the database so that you can recover it to its original state.2. Back up the /usr/sap/<SID>, including the complete SUM directory.

NoteIf the SUM directory is not part of directory /usr/sap/<SID>, make a separate backup of the complete directory including the sdt subdirectory. Be aware that we do not recommend using a different directory than /usr/sap/<SID>.

3. Back up the home directory of user <sid>adm. If you need to reset the update process and problems occur when starting and stopping the SAP system, you might need to use the old user profiles contained in this directory.

Preparing Additional Application Server Instances

1. EHP installation or SPS update: Make sure that all additional application server instances and their associated services are up and running.

Preparing System Tools

1. Make sure that the following tools are not running, and shut them down if necessary:○ jcmon and other standalone monitoring tools

2. Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3Only valid for 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5Release upgrade only: If your SCS is located on a host other than the host where the upgrade is running, make sure that SAP Host Agent is installed on the remote host where the SCS is located. SUM will remain paused until it detects that SAP Host Agent has been installed on that host.End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3End of 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

3. If the User Management Engine (UME) is located on a remote host, make sure that this host is running.4. Install the Microsoft Visual C++ runtime environment (vcredist_*.msi or .exe package) to any remote

Windows hosts, of your system has any. The version you have to use is delivered in the stack with the new SAP kernel and SAP JVM components. This is also valid if your system is heterogeoeous.

NoteIf you have a remote SCS instance running in a clustered or high availability environment, you have to install the vcredist_* package on both cluster nodes. If your archives contain both .msi and .exe versions of vcredist_*, use the .exe version.

The vcredist_* package required by SAP kernel is available in the SAPEXE_*.SAR and SAPJVM<version>_*.SAR archives delivered with the stack. By using the following command, extract the package relevant for your system from either archives on the remote host:sapcar -xf <Archive>.SAR vcredist_*.* -R /<target_dir>

5. Review the changes that will be applied to the system by checking the ProcessOverview.html report.



5.15 Performing Actions at the End of the Downtime

1. At the end of the downtime, create the following backups:○ A backup of your database as described in your database manual○ A backup of the SUM directory

2. Release upgrade only (switch-based): Configure the SAP start service (sapstartsrv) to automatically start as a daemon during the operating system startup as described in SAP Note 823941 .

5.16 Evaluating the Software Update Manager

To give your feedback to the update process, you can send a feedback form to SAP.

Prerequisites

● The update has finished.● The client with which the update is controlled needs an Internet connection.

Context

SAP is always interested in improving its tools. Our aim is to provide you with a fast and efficient update process. Upon completing the process successfully, the important statistics of the update are collected in a comprehensive report – the UPGANA.XML file. Evaluating the collected information helps us to improve the update process but also brings benefits like transparency and predictability. Note that the form does not collect any business-related data.

To be able to identify areas in need of improvement, we would highly appreciate getting feedback on your experience with the SUM process. For this purpose, we have incorporated a simple feedback form directly in the SL Common UI (Summary roadmap step). The Summary and Evaluation of the Process dialog contains the following sections:

● SummaryUsing the corresponding link in the dialog (UPGANA.XML), you can open a process report, which is designed to easily evaluate your update and to better plan follow-up updates. It includes all important artifacts in a single file.

● Feedback FormThis form consists of a simple questionnaire on your experiences with the SUM process, a free-text feedback field, XML data generated during the update process, and an email field.



Procedure

1. Answer the questions in the Feedback Form section.

NoteAnswering the questions is optional.

2. Choose SEND TO SAP.

5.17 Running the Software Update Manager for Another Update

This section describes how you start the Software Update Manager again from the beginning for another update.

Prerequisites

You have successfully performed an update, and you have stopped the Software Update Manager afterwards as described in Stopping the Software Update Manager [page 70].

Procedure

1. Rename the update directory used for the update that has already finished.2. Unpack SUM again and start it as described in Starting the Software Update Manager [page 54].

5.18 Stopping the Software Update Manager

After a successful update, you have to stop the Software Update Manager manually.

Context

After the update procedure has been performed successfully, the Software Update Manager displays an appropriate information in the web browser window. Afterwards, all remaining processes on operating system level must be terminated to stop SUM completely. This also applies after a reset and the subsequent cleanup in case you do not want to continue the update.



You have two options to stop the Software Update Manager completely:

● Using Exit from the More menu.● Killing the SAPup and SUMSUM processes manually on the host.

Procedure

Option 1: Stopping SUM using Exit command:1. After the update procedure has been performed successfully, choose Exit from the More menu.

This exits the current page and displays the initial dialog of the SL Common UI ("Tool start required").2. Choose Exit again.

This terminates the SAPup process on the server and stops with that the Software Update Manager completely. An appropriate message on the SL Common UI appears.

3. Close the web browser page.Option 2: Stopping SUM by killing the SAPup and SUMSUMprocesses:4. After the update procedure has been performed successfully, choose Cancel and then OK.5. Close all browser windows connected with SL Common UI.6. Search for SAP JAVA VM runtime binary processes by using the following:

ps -ef | grep SUM7. Kill all found process IDs (PIDs) using the following command:

kill <PID>

5.19 Performing an Automated Update

Prerequisites

You have the data from a previous SUM update that was used to execute the same scenario you want to automate.

Context

The Software Update Manager can operate in automated mode for release upgrades, SPS updates, and EHP installations for Java-only systems. As not all of them require strict supervision, the automated update can contribute to, for example, updating development systems, quality assurance systems, and test systems, or when running multiple updates in complex landscapes. During the final steps of an update, the BatchModeInputFile.xml file is generated into the /sdt/param/ subdirectory of the update directory. This file contains all required parameters for the SUM process and is used during the automated update.


The automated update mode has the following benefits:

● You can monitor the progress of the update.● You can perform error handling with the same features as in the regular manual update.● Security requirements are fulfilled, for example, no passwords are stored in the system.● Usability – executing the automated update mode is simple since no manual input is required.

Procedure

1. Copy the BatchModeInputFile.xml file to the <SUM directory>/sdt/param/ directory of the system to be updated.

2. Edit the BatchModeInputFile.xml file depending on your update:

○ Update of the same system: Adapt the location and name of the stack XML file in the BatchModeInputFile.xml file so that it contains the current data.

○ Update using a file from another system, or if your previous SUM directory has been deleted: Adapt the parameter values to the ones of the newly updated system in the BatchModeInputFile.xml file.

NoteBy default, you enter the required passwords in SUM manually. As an alternative in the automated mode, you can uncomment and fill in the password fields in the BatchModeInputFile.xml to automate this. Note that you should do this only if you are sure that your system is fully protected against unwanted external access.

3. In the startup.props file, uncomment the line #autoinput=/usr/sap/<SID>/SUM/sdt/param/BatchModeInputFile.xml and enter the navigation path to your XML file. For example: usr/sap/AB1/SUM/sdt/param/BatchModeInputFile.xml

4. Start the SL Common GUI as described in Starting and Restarting the Software Update Manager [page 55].



6 Follow-Up Activities

This part of the document contains information about the follow-up activities that you need to perform after you have updated your SAP system.

Before you perform any follow-up activities, it is important that you perform the actions described in Quick Guide [page 13] in the specified order.

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 additional product-specific document. This document is referenced in the Master Guide (or Upgrade Master Guide, respectively) for your product.

Actions

You have to perform the following actions before you resume production operation of your system:

● Performing Follow-Up Activities for User root [page 73]● Performing Follow-Up Activities in the Monitoring Area [page 74]● Performing Follow-Up Activities for SAP Solution Manager [page 75]● Release upgrade only: If the additional application server instances in your cluster were online during the

upgrade, you have to restart your primary application server instance after the upgrade has finished.

You can perform the following actions during production operation of your system:

● Deleting Log Files [page 76]

6.1 Performing Follow-Up Activities for User root

To perform the necessary adjustments after the update, you need the user authorizations of the user root.

Context

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. For more information about binding ports smaller than 1024, see SAP Note 421359 .

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBFollow-Up Activities PUBLIC 73


● The ICM server ports are configured in the profile parameter icm/server_port_<n> that is contained in the instance profile or default profile.

Procedure

1. Log on as user <sid>adm.

2. Execute the following commands:

su - root

If you have one kernel directory: cd /usr/sap/<SID>/SYS/exe/run

If you have two kernel directories: cd /sapmnt/<SID>/exe/(n)uc/<platform>

cp -p ./icmbnd.new ./icmbnd

chown root:sapsys icmbnd

chmod 4750 icmbnd

exit3. Start the SAP system again.

6.2 Performing Follow-Up Activities in the Monitoring Area

Monitoring with CCMS Agents

As of SAP NetWeaver 7.0 including enhancement package 2, the CCMS agents infrastructure has changed significantly. If necessary, perform the follow-up activities for central monitoring as described in SAP Library [page 12] for your target release at:

SAP Library Paths


SAP NetWeaver 7.3 / 7.3 including enhancement package 1 / 7.4/ 7.5

Go to SAP Help Portal and search for the section CCMS Agents: Upgrade of Monitored Systems from NW 7.0x to 7.1x or higher relevant for the SAP product running in your system.

SAP NetWeaver PI 7.1/ 7.1 including enhancement package 1 Go to SAP Help Portal and search for the section CCMS Agents: Upgrade of Monitored Systems from NW 7.0 to 7.1 relevant for the SAP product running in your system.



https://help.sap.com/

https://help.sap.com/

6.3 Performing Follow-Up Activities for SAP Solution Manager

Use

To connect the newly updated system to SAP Solution Manager, you need to perform the following activities:

● Make sure that the data is up-to-date in the SAP Solution Manager system.● Configure the diagnostics capabilities and the Wily Introscope Agent.● If required, update the product version of the system where the Integration Server is installed.

Procedure

Checking System DataIn 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 up-to-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 ManagerAfter 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 http://help.sap.com/solutionmanager:

SAP Library Paths


SAP Solution Manager 7.2 Application Help SAP Library <version> SAP Solution

Manager Operations Managing System Landscape

Information .

Read sections Setting Up the Landscape Management Infrastructure and Managing Technical System Information.

Configuring Diagnostics Capabilities and Wily Introscope Agent1. Start SAP Solution Manager.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.

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBFollow-Up Activities PUBLIC 75

http://help.sap.com/solutionmanager

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 Community Network at http://wiki.scn.sap.com/wiki/x/CBkMDg .

6.4 Deleting Log Files

For security, data protection, and privacy-related reasons, we recommend that you delete the log files as soon as you no longer need them.

Context

For technical reasons, the Software Update Manager writes various log files. Among other things, these log files contain IDs of users such as <SID>ADM, DDIC, or SYSTEM.

In order to comply with data protection, privacy and security requirements, we strongly recommend that you delete these log files as soon as you no longer need them.

Procedure

Remove the log files from the SUM Directory [page 26] and its subdirectories on the host where the Software Update Manager has initially been started.



http://help.sap.com/disclaimer?site=http%3A%2F%2Fwiki.scn.sap.com%2Fwiki%2Fx%2FCBkMDg

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwiki.scn.sap.com%2Fwiki%2Fx%2FCBkMDg

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

7.1 Introduction

This part of the document describes how to apply single component updates and patches in SAP systems using the Software Update Manager (SUM) 1.0 SP26. You can also use this procedure to install add-ons delivered through software archives without a stack.xml configuration file, or perform kernel updates.

Only valid for 'Source Release': SAP NetWeaver 7.1, SAP NetWeaver 7.2, SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

When downloading and applying patches, check for dependencies by using the SCA Dependency Analysis Tool. For more information, see SAP Note 1974464 .

End of 'Source Release': SAP NetWeaver 7.1, SAP NetWeaver 7.2, SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

For a list of all supported processes, products and releases, see the current Software Update Manager Note 2882395 .

CautionIt is essential that you use the Quick Guide [page 77] 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.

7.2 Quick Guide

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

● Find SAP Notes● Prepare the update● Update your system

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 gain a quick overview of the update procedure.

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBApplying Single Component Updates and Patches Using a Manually Prepared Directory PUBLIC 77



Checklist

SAP Notes

This document is enhanced and updated by SAP Notes from SAP Support Portal (http://support.sap.com ). 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 11]. You require at least the following SAP Notes:○ Central Software Update Manager Note 2882395○ The relevant database-specific SAP Notes 2937237○ Single component update and patch scenarios in SUM – SAP Note 1641062 (describes the rules for

acceptance or rejection of the components)

Update Preparation

You can perform the preparations while the system is in production operation.

Actions Before Starting and Using the Software Update Manager

1. You fill the manually prepared download directory [page 79].

Update Procedure

Actions for Starting and Using the Software Update Manager

1. You meet the requirements for the SUM directory [page 53].2. You download and unpack the Software Update Manager [page 53].3. You register SUM in SAP Host Agent [page 83].4. You start the Software Update Manager [page 84].5. You can reset [page 84] the update if needed.

In addition, you can configure the alert function [page 59] to notify you when user action is required.6. You can use breakpoints during the procedure [page 61].

Making Entries for the Specify Authentication Mechanism Roadmap Step

You continue with roadmap step Specify Authentication Mechanism [page 62] and make the corresponding entries.

User Actions During the Select Target Roadmap Step

You continue with roadmap step Select Target [page 90] and make the corresponding entries.

User Actions During the Confirm Target Roadmap Step

You continue with roadmap step Confirm Target [page 91] and make the corresponding entries.

User Actions During the Configuration Roadmap Step

You continue with roadmap step Configuration [page 91].

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.

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.


Applying Single Component Updates and Patches Using a Manually Prepared Directory

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com




2. Before the downtime [page 92] begins, you are asked to make the necessary backups and additional actions.

Actions During the Execution Roadmap Step

While 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 92].

Actions During the Summary Roadmap Step

1. You evaluate the Software Update Manager [page 69].2. You store the current SUM data for future use [page 94].

7.3 Filling the Manually Prepared Download Directory

Context

You can put all software component updates and patches which you want to apply to your system in a manually prepared download directory. During the Select Target roadmap step, you are prompted to enter the path to your manually prepared directory. The Software Update Manager reads this directory and moves the files to the appropriate directories from where they are then further processed.

NoteSUM only reads files located at the top level of the manually prepared directory. Note that any subdirectories are not considered for deployment by SUM.

You can put the following component types in the download directory:

● Software Component Archives (*.SCA)● Software Deployment Archives (*.sda)● Other deployable archives (with extension *.zip and *.ear)● Non-deployable components (such as kernel binaries)

NoteSUM can deploy ear and sda archives only if they are part of an SCA archive that already exists in the system.

Procedure

1. Prepare a consistent download directory. The directory can be located anywhere on your host.2. Put all software components and patches to be applied to the system into the same directory.


7.4 Running the Software Update Manager

This part of the document provides information about starting and running the Software Update Manager. This section describes all the required user input and actions, as well as critical points during the update.

Note the following:

● All required planning and preparation actions should be completed.● The Software Update Manager controls the entire procedure, from checking the system requirements and

importing the necessary programs through stopping production operation until production operation is resumed. The procedure is divided up into a number of different roadmap steps. The roadmap steps are in turn divided into individual steps. The successful completion of a step is a precondition for the success of all subsequent steps.

● Use this procedure to install add-ons delivered only through software archives without a stack.xml configuration file.

● Depending on the source release, the Software Update Manager has to run on:○ Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3


○ SAP NetWeaver 7.1 and higher: the host, on which you want to run the tool. It can be either the primary application server instance or an additional instance.

● If the instance, on which you are going to run the tool and database are running on different hosts, you have to perform the actions that affect the database on the database host.

● You can use the logs written by the tool to monitor the procedure.● Many steps require no user input. In the following, you can find a description of all necessary user input.● User actions are also required when errors occur. If an error occurs, correct it and repeat the step in which

the error has occurred. Once the step has been repeated successfully, you can continue with the update. For more information, see the Troubleshooting [page 103] part of this document.

Prerequisites

Before you run the Software Update Manager, make sure that the following prerequisites are fulfilled:

● Your system is up and running. You should not stop the system manually. The tool stops and starts it when needed.

● You are logged on to the update host as user <sid>adm.● User <sid>adm has the required permissions:

The <sid>adm user has to be the owner and have full (xrw) permissions on all files in the /usr/sap/<SID> and /sapmnt/<SID> directories. If symbolic links are used, <sid>adm has to be the owner of these links as well.

CautionIf your system is installed in a high availability switchover 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

You perform the following actions to start and use the Software Update Manager:

● Meeting the Requirements for the SUM Directory [page 53]● Downloading and Unpacking the Software Update Manager [page 53]● Registering SUM in SAP Host Agent [page 83]● Starting and Restarting the Software Update Manager [page 84]● Resetting the Update [page 58]● Using the Alert Function [page 59]● Using Breakpoints During the Update [page 61]

You perform the following actions during the roadmap steps:

● Making Entries for the Specify Authentication Mechanism Roadmap Step [page 62]● Making Entries for the Select Target Roadmap Step [page 90]● Making Entries for the Confirm Target Roadmap Step [page 91]● Making Entries for the Configuration Roadmap Step [page 91]● Performing Actions Before the Beginning of the Downtime [page 92]● Performing Actions at the End of the Downtime [page 92]● Evaluating the Software Update Manager [page 69]● Storing Current SUM Data for Future Use [page 94]

7.4.1 Meeting the Requirements for the SUM Directory

Context

If you do not specify a path when you unpack the Software Update Manager package, the SUM directory is automatically created as a subdirectory of the directory where you unpack the software package. However, we recommend that you use the standard path /usr/sap/<SID>.

NoteIf a directory with this name already exists, it has to be empty. Otherwise, the startup of the update fails.

The update directory can be a soft link to another physical directory.

Procedure

Make sure that there is enough free disk space for the SUM directory. This space is required for the update and the logs and is distributed among several subdirectories [page 26]. For an estimation of the disk space needed for the SUM directory, see the update guide that is specific to your product.


7.4.2 Downloading and Unpacking the Software Update Manager

Procedure

1. Download the latest version of the Software Update Manager from the main Software Logistics Toolset page on the Support Portal at:

http://support.sap.com/sltoolset System Maintenance Software Update Manager (SUM)Download SUM

Notehttps://blogs.sap.com/2015/07/09/maintenance-planner-2/ .

2. Log on as user <sid>adm to the host where you will run the tool.

NoteDepending on the source release, the Software Update Manager has to run on:

○ Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3SAP NetWeaver 7.0-based systems: The latest version of the Software Update Manager can: the primary application server instanceEnd of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

○ SAP NetWeaver 7.1 and higher: the host, on which you want to run the tool. It can be either the primary application server instance or an additional application server instance.

3. Unpack the Software Update Manager package with the following command:

SAPCAR –xf <download directory>/<path>/<Archive>.SAR -R /usr/sap/<sid>

This command creates the directory SUM under the /usr/sap/<sid> directory. You can also specify another directory. Hereafter, the directory <path to SUM directory>/SUM is referred to as <update directory>.

Note○ Do not unpack SUM in the DIR_GLOBAL directory , as this might lead to issues during the update.○ The complete path to the SUM directory should not exceed 25 characters.○ Do not extract the Software Update Manager to a directory starting with /usr/sap/<any

capital three letters>/ where <any capital three letters> is not the SID of the managed system.

○ If you want to run several updates in parallel on the same host, you have to unpack one SUM instance in each directory of the respective SID directories.For example, if you have the SAP system IDs AB1 and AB2, unpack one SUM instance in the respective directory of each SAP system ID. When starting the SL Common UI, you enter the corresponding SAP system ID in the URL, thus connecting to the corresponding SUM instance. For more information, see Starting and Restarting the Software Update Manager [page 55]. Note that when running several SUM instances using the default location /usr/sap/<sid> is mandatory.




http://help.sap.com/disclaimer?site=https%3A%2F%2Fblogs.sap.com%2F2015%2F07%2F09%2Fmaintenance-planner-2%2F

7.4.3 Registering SUM in SAP Host Agent

Before you start the procedure you have to register the Software Update Manager in SAP Host Agent, so that the operations and commands to the updated system are executed using SAP Host Agent mechanisms.

Depending on the source release, the Software Update Manager has to run on:

● Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3SAP NetWeaver 7.0-based systems: the primary application server instanceEnd of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

● SAP NetWeaver 7.1 and higher: the host, on which you want to run the tool. It can be either the primary application server instance or an additional one

Prerequisites

● You have downloaded and unpacked [page 53] the latest SUM version of the and the software packages that you need for the update.

● For a correct execution of the update procedure, make sure that you have installed on all application servers instances the latest version of the SAP Host Agent.Check the SAP Software Download Corner at http://support.sap.com/swdc for the versions that are available to download. For more information, such as the deprecation of lower versions, see SAP Note 2130510 . For additional information regarding SAP Host Agent, see SAP Notes 1031096 and 1907566

.● The Secure Socket Layer (SSL) is configured as described in Security and Authentication [page 42].

Procedure

Note● Make sure that you do not run the Software Update Manager during daylight saving time shifts.

Otherwise, the update might fail.● Always perform the procedure from within the SUM directory.

1. (Optional) You can set SUM to omit the system restart that takes place at the end of the update procedure to perform additional maintenance activities, for example, adapting various system settings, integrating third-party software in your landscape, and others. Proceed as follows:1. Navigate to /usr/sap/<SID>/SUM/sdt/param/ and open the startup.props for editing.2. Set the following profile parameter as follows:

skipFinalJ2EERestart = true3. Save and close the file. At the end of the downtime, you are informed that the final system restart has

been omitted, and that you can perform your additional maintenance.Note that after you have finished, you have to manually restart your system.


http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fswdc





2. To run the registration of the Software Update Manager in the SAP Host Agent, log on as user root and enter the following command:○ /usr/sap/<SID>/SUM/STARTUP <SID>

7.4.4 Starting and Restarting the Software Update Manager

This section describes how you start the SL Common UI and the SUM back-end process.

Prerequisites

● You have met the requirements for the update.● The SAP system and the database have been started.● You have registered SUM in SAP Host Agent as described in Registering SUM in SAP Host Agent [page 54].● The SAPCAR version that is referenced in the environment variable PATH is identical with the one that is

located in the kernel directory. In addition, no reference to any other SAPCAR version should exist in the PATH variable.

● All application server instances and their associated services are up and running.● The P4 protocol is configured to monitor the loopback address of your system as described in Ensuring the

Validation of the Java Administrator [page 49], so that the Java administrator verification is successful.● You have downloaded and unpacked the latest version of the Downloading and Unpacking the Software

Update Manager [page 53] and the software packages that you need for the update.● When using Internet Explorer, you have to make sure that the URL relevant for your system is listed in the

“Trusted” security zone. To do so, proceed as described in the Internet Explorer documentation.● In the case of a SUM restart, you have corrected the errors as described in section Troubleshooting [page

103].● To use SUM without entering user credentials, you have configured the SAP Host Agent to operate over an

SSL connection as described in Security and Authentication [page 42].

TipAlthough SUM can operate over the http communications protocol, we strongly recommend that you set up your system to use the https communications protocol.

NoteIf you have various systems running on the same application server host, you can start a further Software Update Manager procedure on these systems for system maintenance.

The prerequisite is that the SUM directories remain unchanged and follow the standard path as described in chapter SUM directories.



Procedure

1. Open a web browser window.2. In the address bar, enter the following URL:

https://<fully qualified hostname>:1129/lmsl/sumjava/<SID>/index.html

NoteIf the SSL is not configured, use http instead of https at the beginning of the URL, and use port 1128:

http://<fully qualified hostname>:1128/lmsl/sumjava/<SID>/index.html

3. In the dialog box that appears, enter the user name <sid>adm and the password.

Results

The SAP Host Agent starts the Software Update Manager, and the SL Common GUI of the Software Update Manager is displayed in the web browser.

7.4.5 Resetting the Update

The Software Update Manager offers the option to reset the update.

Prerequisites

● Make sure that the downtime has not yet started.As of the beginning of the downtime, a reset is not possible anymore. To reset the update after the downtime has started, use the system backup created before the SUM process.

Context

When you choose the Reset option of the Software Update Manager, the system is set to a state that allows the update procedure to be restarted from the beginning.

Procedure

Resetting the update procedure on the SL Common UI:


a. To reset the update procedure before the beginning of the downtime, choose either Back from the user interface or Reset from the More menu.

This depends on the phase that the update procedure is currently going through. The update procedure consists of phases that can be reset and of phases that you cannot reset directly. Whenever you are inside a resettable phase, the Software Update Manager offers you a Reset option in the More menu. If not, choose Back repeatedly until you are in a resettable phase and the Reset option appears in the More menu. If the update procedure has not progressed far and you choose Back repeatedly, the Welcome dialog may appear.

After you have chosen Reset, the Software Update Manager indicates afterwards the successful reset procedure and asks you to clean up the SUM directory. Choose Cleanup in the More menu. After the cleanup is completed, the Welcome dialog appears again. You can close the browser window or the browser tab page, or you can start the update procedure from the beginning.

NoteFor more information about the More menu, see SL Common UI Elements and Options [page 19].

b. When the Welcome dialog appears, the system has been fully reverted to its state before the update and you can start the update from the beginning. However, we strongly recommend you ensure that all SUM backend processes are stopped, delete the current SUM directory, and use a newly unpacked SUM before you start over.

NoteWhen you are in an error dialog and you want to reset the update, be aware of the following:

○ Close the browser window or browser tab page when the In progress process execution animation appears. Do not refresh the browser window or tab page, as this might restart the SL Common UI.

○ The Cancel button only stops the SUM background process and the SL Common UI, but does not trigger the reset of the system to its original state. Also, closing the UI tab only closes the user interface.

○ To prevent or correct errors with the reset procedure, see SAP Note 2011380 .

7.4.6 Using the Alert Function

Use

The alert function of the SL Common UI can be set to send an e-mail or an SMS when user action is required, or when the procedure stops because of errors.

Procedure

To configure the alert function, proceed as follows:

1. In the top right corner of the SL Common UI, choose Alert.




2. Make the required entries:

Alert Configuration Options

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.

ExampleThe 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="[email protected]"

#SUBJECT="EHP Installer Alert"

#EMAIL_ADDRESS="[email protected]"

#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"


Field Entry

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

#cat "$ATTACHED_FILE" | mailx -r "$FROM_ADDRESS" -s "$SUBJECT" "$EMAIL_ADDRESS"

Alert File Absolute path to the alert file that stores the alert message

Alert Delay (in seconds) Time delay between the event and the sending of the notification

Set active (checkbox) Activates the alert function

3. To save your entries, choose OK.

7.4.7 Using Breakpoints During the Update

You can stop the update procedure at a specified point by using breakpoints.

Setting Breakpoints in the SL Common UI

On the right-hand side of the browser window, the SL Common UI offers you the option to maintain breakpoints from a list of available breakpoints. You can sort, filter, and search for breakpoints. The icons for the breakpoint status are described in the legend.

The breakpoint list displays icons in three different colors:

● Green - breakpoint lies in the past● Orange - breakpoint lies in the currently processed phase● Blue - breakpoint lies in a future phase

After opening the list, it scrolls automatically to a position where the breakpoint of the current phase is listed at the fourth position from the top, if available. You can scroll away from the position, but each time you choose Refresh, the breakpoint list is refreshed and displays the current phase highlighted at the fourth position of the table again.

If SUM stops at a selected breakpoint, it displays a dialog with the options listed below in Options in the Dialog.



Options in the Dialog

NoteDepending on your scenario and system, the available options may vary.

Once you have set a breakpoint, the Software Update Manager stops at that specific point and displays a dialog with the following options:

● Continue executionSUM continues the update automatically until the next breakpoint is reached. Then, the breakpoints dialog is displayed.

● Exit programThe update process stops and you exit SUM. When you restart the update process, the breakpoint dialog appears again.

7.4.8 Making Entries for the Specify Authentication Mechanism Roadmap Step

Procedure

Enter the password for the <SID>ADM user and choose Next.

Alternatively, if the sapcontrol executable is set up in a way that it does not require user credentials, select the checkbox No authentication with user credentials and choose Next.

Release upgrade only: To be able to use this option in a system with multiple application server instances, proceed as described in Configuring SAP Host Agent Authentication and SSL Connection [page 42].

If you choose to continue the update using user credentials, be aware that it is mandatory to use the <SID>ADM user.

If the OS user credentials for any of the instances in your system do not match the ones that you have already entered for the primary application server instance, you have to specify the correct credentials for each instance on a subsequent screen.

Results

Your administrator user is verified for performing the SUM procedure in the system.


7.4.9 Making Entries for the Select Target Roadmap Step

Context

You can use this option if you want to apply single component updates or patches.

The system is updated (or extended) with the content available in your manually prepared download directory.

NoteSUM only reads files located at the top level of the manually prepared directory. Note that any subdirectories are not considered for deployment by SUM.

Procedure

1. In the Stack File or Directory field, specify the path to the manually prepared directory.2. Choose Next.

NoteFor high availability systems: In the Select Target roadmap step, SUM performs a high availability (HA) verification in your SAP system. For more information, see SAP Note 1864705 .

If an SAP-certified high availability solution is detected in your system, a dialog containing a summary of the relevant software and consistency tests is displayed. The HA consistency test categories are the following:

○ SAP Configuration – this test verifies whether you have all required software units that classify your system as an SAP-certified high availability solution.

○ SAP State – this test verifies that the required units are fully operational.○ HA Configuration – this test verifies whether your SAP system is configured for high availability.○ HA State – this test verifies whether the required HA configuration is fully operational.

The Warning status and Error status indicate that your SAP system does not comply with the SAP certification standard for high availability solutions. In such cases, you can continue with the SUM process in the current system state or cancel the SUM process to correct the inconsistencies.

Warning is the highest degree status for the SAP State and HA State categories. Error is the highest degree status for the SAP Configuration and HA Configuration categories. Note that in log files these statuses may be noted differently, for example, in the DETECT-CERTIFIED-HA_*.log file.




7.4.10 Making Entries for the Confirm Target Roadmap Step

Procedure

Confirm the component updates and patches you want to apply to the system by choosing Next.

7.4.11 Making Entries for the Configuration Roadmap Step

This roadmap step requires information to run the update such as system users and passwords.

Procedure

1. Enter the password for the AS Java Administrator user with which you log in to the system.

2. To proceed with the update, choose Continue.

On the Select Components screen, a list of all components that have applicable updates in the manually prepared directory is displayed.

NoteSome kernel components might be rejected by the current validation although they were accepted during the Confirm Target roadmap step. In the Confirm Target roadmap step, the kernel components are accepted on the basis that they are compatible with the database, but OS compatibility is not validated yet. In the Configuration roadmap step, SUM checks the operating system(s) installed in your system landscape and based on this, rejects the incompatible kernel components.

3. Decide how you want to handle the components during the update.

The following information is displayed for each component:

○ Vendor/Name○ Type○ Current Version○ Target Version○ Details

In the Target Version column, you can select the version that you want to apply for each component or skip the update of a component by selecting skip.

NoteIf you change the content of the manually prepared directory, make sure you rescan the directory again by choosing Rescan.

4. To review the status of the components in the manually prepared directory, choose TargetVersionReport.html.


Note

For the rules for acceptance or rejection of the components, see also SAP Note 1641062 .

7.4.12 Performing Actions Before the Beginning of the Downtime

This section describes the actions that you have to perform before the downtime begins.

Procedure

1. Make sure that you can recover your SAP system if errors occur:○ Back up the database so that you can recover it to its current state.○ Back up the SUM directory.

In case of problems during the downtime, for example, a hardware failure, you need the backup of the directory to reset the SAP system to its current state. The directories include, amongst others, profiles, trace files, and files for the SAP kernel needed for a reset of the SAP system.

NoteIf the SUM directory is not part of directory /usr/sap/<SID>, make a separate backup of the complete directory including the subdirectory sdt.

NoteAdditionally, back up the home directory of user <sid>adm. If you need to reset the update process and problems occur when starting and stopping the SAP system, you may need to use the old user profiles contained in this directory.

2. Review the changes that will be applied to the system by checking the ProcessOverview.html report.

7.4.13 Performing Actions at the End of the Downtime

Procedure

At the end of the downtime, create the following backups:○ A backup of your database as described in your database manual○ A backup of the SUM directory




7.4.14 Evaluating the Software Update Manager

To give your feedback to the update process, you can send a feedback form to SAP.

Prerequisites

● The update has finished.● The client with which the update is controlled needs an Internet connection.

Context

SAP is always interested in improving its tools. Our aim is to provide you with a fast and efficient update process. Upon completing the process successfully, the important statistics of the update are collected in a comprehensive report – the UPGANA.XML file. Evaluating the collected information helps us to improve the update process but also brings benefits like transparency and predictability. Note that the form does not collect any business-related data.

To be able to identify areas in need of improvement, we would highly appreciate getting feedback on your experience with the SUM process. For this purpose, we have incorporated a simple feedback form directly in the SL Common UI (Summary roadmap step). The Summary and Evaluation of the Process dialog contains the following sections:

● SummaryUsing the corresponding link in the dialog (UPGANA.XML), you can open a process report, which is designed to easily evaluate your update and to better plan follow-up updates. It includes all important artifacts in a single file.

● Feedback FormThis form consists of a simple questionnaire on your experiences with the SUM process, a free-text feedback field, XML data generated during the update process, and an email field.

Procedure

1. Answer the questions in the Feedback Form section.

NoteAnswering the questions is optional.

2. Choose SEND TO SAP.


7.4.15 Storing Current SUM Data for Future Use

Context

NoteThis option is only available when applying single component updates and patches.

At the end of a successful update procedure, you can choose to store important data from your current Software Update Manger run. You can use the stored data for future runs using the Manually prepared directory option.

Procedure

1. On the Summary and Evaluation of the Process dialog, choose the checkbox Store current SUM data for reuse.

2. Choose Exit.3. Optional: To use stored SUM data, start the Software Update Manager as described in Starting the

Software Update Manager [page 54].

Results

The data for each SUM execution is stored in a separate folder in the following directory:

/<path to SUM directory>/SUM/sdt/archive/

The folder names follow the naming convention execution_<year_month_day_hour_min_sec>. Each subsequent SUM execution completed with this option enabled is stored in the same directory in a separate folder.

After a default period of 30 days, a stored SUM instance data folder is archived to a zip file that is stored in the same folder. The archive follows the naming convention mentioned above. This time period can be configured. To do so, you have to adjust the value of the archiving/minage parameter (in days) in the jump_config.txt file, which is located in the following directory:

/usr/SAP/SID/<SUM>/sdt/param/



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

8.1 Introduction

This part of the document describes how to install additional Java technical usages or usage types in an existing SAP system based on SAP NetWeaver Java using the Software Update Manager (SUM) 1.0 SP26.

“Existing SAP system” means that this SAP system has at least Application Server Java installed in it.

You perform the installation of additional technical usages or usage types in an existing Java system to optimize the total cost of ownership (TCO). That is, you do not have to install a complete additional Java system to run additional technical usages or usage types.

8.2 References to Maintenance Planner Documentation

This chapter does not describe how to run the Maintenance Planner. For a better understanding of the general concepts and principles of updating a system, see the Maintenance Planning Guide at http://wiki.scn.sap.com/wiki/x/VIwqCw , section Guides.

8.3 Restrictions

● Installing additional usage types might cause interdependencies between already installed SAP applications. Therefore, carefully consider the implications of running update processes that affect your existing system landscape: if you want to update your SAP system (perform an upgrade, apply support package stacks, or install an enhancement package), you have to meet the requirements for all installed SAP applications including SAP NetWeaver. For SAP NetWeaver-specific distribution models and application server infrastructure, see http://www.sdn.sap.com/irj/sdn/server-infrastructure .

● You cannot install Process Integration (PI) or Mobile Infrastructure (MI) as an additional usage type using SUM in an existing dual-stack (ABAP+Java) system. Instead, you need to install a new SAP Process Integration system or a new SAP Mobile Infrastructure system from scratch using the Software Provisioning Manager 1.0.

● We do not recommend that you install additional usage types in an existing dual-stack system. For more information, see How to Deploy SAP NetWeaver: Dual Stack vs. Separated Stacks at http://scn.sap.com/docs/DOC-14359 .

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBInstalling Additional Usage Types (Technical Usages) in an Existing SAP System PUBLIC 95

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwiki.scn.sap.com%2Fwiki%2Fx%2FVIwqCw


http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sdn.sap.com%2Firj%2Fsdn%2Fserver-infrastructure

http://help.sap.com/disclaimer?site=http%3A%2F%2Fscn.sap.com%2Fdocs%2FDOC-14359


8.4 Preparation

Procedure

1. Check which usage types are already installed. To do this, go to the usage type system information page of your system at http://<host>:<http_port>/utl/UsageTypesInfo

2. Check the dependencies for the usage types that you want to install. Make sure that you read this information in the Master Guide for your product version.

3. Use the Quick Sizer tool available at https://www.sap.com/about/benchmark/sizing.html to get information about additional disk space and RAM requirements for the additional usage types that you want to install.

4. Check the sizing guidelines for your product available at https://www.sap.com/about/benchmark/sizing.html Sizing Guidelines .

5. Provide the required software packages for the additional usages that you want to install. You do this by generating the stack configuration file using Maintenance Optimizer. The stack file and software packages can be downloaded manually from SAP Software Download Center at https://support.sap.com/swdc

Support Packages and Patches SAP Support Package Stacks SP Stack Download & Side effect report .

6. Only valid for 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1Ensure that you are well aquainted with the content of SAP Note 1793486 , and you have aquired the activation scripts.End of 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1

8.5 Installation

To install the desired additional technical usages in your existing SAP system, you need to follow similar workflow as described in Running the Software Update Manager [page 51].

The Software Update Manager applies the stack configuration file provided by you and extends the SAP system with the specified technical usages. Note that there are different installation scenarios:

● The additional technical usages are part of an existing SAP product that has already been activated on the system:In this case, the Software Update Manager installs and activates the new technical usages automatically.

● The additional technical usages are part of an existing SAP product that has not been activated on the system yet:In this case, the Software Update Manager installs the usages but as a post-installation step, you have to activate them manually as described in Post-Installation [page 97].

● The additional technical usages are part of a new (non-existing) SAP product:In this case, the Software Update Manager installs the usages but as a post-installation step, you have to activate them manually as described in Post-Installation [page 97].

● Installing SAP Business Suite technical usages on top of an existing SAP NetWeaver Java system:This installation scenario is described in the document SAP Solution Manager: Specifics in Installation and Upgrade available at http://wiki.scn.sap.com/wiki/x/VIwqCw , section How-Tos and Guides. Follow the


Installing Additional Usage Types (Technical Usages) in an Existing SAP System







specific steps described in the chapter Add Installation of SAP Business Suite Usage Types to Existing NW System.

8.6 Post-Installation

Context

After you have finished the installation with SUM, you still need to activate the newly installed usage types manually if the conditions described in Installation [page 96] apply.

Note● You have to perform the manual activation separately for each additional usage type that needs to be

activated.● As SAP NetWeaver 7.4 and 7.5 rely on PPMS instance information regarding software products installed

in the system, for these releases the activation scripts are not required.

Procedure

1. Make sure you are logged on as user <SID>ADM.

2. Download Scripts_<your_release>.ZIP from the Attachments tab page of SAP Note 1793486 and extract it to a local directory on the host with the primary application server instance of your SAP system.

3. Edit the activeUT.sh script and enter the required values (see also the documentation given in the script itself)○ JAVA_HOME=<directory where the java bin directory of the SAP JVM is located>○ GLOBAL_DIR=<path to the global directory>○ JDBC_CLASSPATH=<jdbc drivers classpath>○ UT_NAME=[technical name of the usage type or technical usage to be activated]○ PRODUCT=[technical name of your SAP application]○ SID=<SAP system ID of the existing SAP system>

ExampleJAVA_HOME=/usr/sap/C11/SYS/exe/jvm/hpia64/sapjvm_6.1.008/sapjvm_6

GLOBAL_DIR=/sapmnt/C11/global

JDBC_CLASSPATH=/oracle/client/112_64/instantclient/ojdbc14.jar

UT_NAME=EP

PRODUCT=NetWeaver

SID=C11



4. Start a new shell and run the activeUT.sh script separately for each additional technical usage that you need to activate.

NoteMake sure that you run the activeUT.sh script with the required command line parameters as described in the documentation given in the script itself. To activate technical usages, you have to set command line parameter –action to true.

5. Check the Master Guide for your product for further implementation and configuration steps.

CautionYou should not run the automated configuration for the added usage types. Instead, you have to configure them manually.

8.7 Deactivation

This section describes how you can deactivate technical usages or usage types.

Procedure

1. Make sure that you are logged on as user <SID>ADM.

2. Download Scripts_<your_release>.ZIP from the Attachments tab page of SAP Note 1793486 and extract it to a local directory on the host with the primary application server instance of your SAP system.

3. Edit the activeUT.sh script and enter the required values (see also the documentation given in the script itself):○ JAVA_HOME=<directory where the java bin directory of the SAP JVM is located>○ GLOBAL_DIR=<path to the global directory>○ JDBC_CLASSPATH=<jdbc drivers classpath>○ UT_NAME=[technical name of the technical usage or usage type to be activated]○ PRODUCT=[technical name of your SAP application]○ SID=<SAP system ID of the existing SAP system>

ExampleJAVA_HOME=/usr/sap/C11/SYS/exe/jvm/hpia64/sapjvm_6.1.008/sapjvm_6

GLOBAL_DIR=/sapmnt/C11/global

JDBC_CLASSPATH=/oracle/client/112_64/instantclient/ojdbc14.jar

UT_NAME=EP

PRODUCT=NetWeaver


Installing Additional Usage Types (Technical Usages) in an Existing SAP System


SID=C11

4. Start a new shell and run the activeUT.sh script separately for each additional technical usage that you need to deactivate.

NoteMake sure that you run activeUT.sh script with the required command line parameters as described in the documentation given in the script itself. To deactivate technical usages, you have to set command line parameter –action to false.


9 Correction of Installed Software Information

9.1 Introduction

NoteThis scenario is only relevant if your source release is SAP NetWeaverOnly valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 37.0-based, End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 37.3-based, 7.4-based, and higher.

This part of the document describes how you can correct and update the information about the installed software instances in SAP systems using the Software Update Manager. Inconsistencies in this information might cause errors during the regular update processes.

To trigger this scenario, you have to specify the path to a specific stack configuration XML file (stack_cisi.xml) in the Select Target roadmap step.

9.2 Making Entries for the Select Target Roadmap Step

Prerequisites

● You have followed the workflow described in Running the Software Update Manager [page 51].● You have generated the specific stack configuration file using the Maintenance Planner.

Procedure

To start the Correction of Installed Software Information scenario, proceed as follows:1. In the Select Target roadmap step, choose Stack configuration file (XML).2. Specify the path to the stack_cisi.xml file.

At this point in time, SUM recognizes a special tag within the file and triggers the Corrections of Installed Software Information scenario.

3. In the Confirm Target roadmap step, confirm the target version that SUM has detected.4. To confirm the scenario, choose Next.


Correction of Installed Software Information

This triggers the update of the installed software information in your SAP system.5. In the Execute Process... roadmap step, choose Next on all subsequent dialogs until the scenario is

completed.

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBCorrection of Installed Software Information PUBLIC 101

A Appendix

A.1 Process Overview Report

This section covers the overview report that contains detailed information about the update process.

With the intent to increase transparency, supportability, and predictability of software maintenance operations, SUM accumulates comprehensive update data during the tool run. The data can be displayed in a special report named Process Overview report, and it is arranged in, but not limited to, the following categories:

● Information about the stack configuration file (stack.xml) and archives in the download directory. An additional window opens where several options are offered. For more information, see

● Software component versions and product structure changes● Important parameter settings, process steps including descriptions of the manual steps and links to

relevant SAP Notes● Statistics about performance and downtime

● In the Configuration roadmap step, after the Java system user credentials dialog: information about active usage types (technical usages) and current software components versions is added to the report;

● In the Execution roadmap step, after the Java deployment step has finished: deployment results are added to the report;

● After the Execution roadmap step, when the system is already updated: the report contains information about the active usage types and target software component versions.

All reports generated during the SUM process that are otherwise part of the process overview are stored in the /<path to SUM directory>/SUM/sdt/htdoc directory .

Features

You can access and use the accumulated information through the SUM GUI as follows:

● On demandFrom the beginning of the SUM execution, you can trigger a report generation by choosing the GUI menu option Update Process Overview report .

● When SUM stops with an errorIn such cases the report is generated automatically and a link to it is provided directly on the error handling screen. If the report is not automatically displayed, choose the GUI menu option Update Process Overview report . The report displays the roadmap step progress as well as the useful Log Analysis Results section, which contains relevant error diagnostics information and the trouble ticket report.

NoteIf you need to report an incident, we recommend that you attach the ProcessOverview.html report to it.


Appendix

● Upon successful finishIn the Summary roadmap step a complete report is generated when the update has finished successfully. A feedback form is presented on the next dialog, and the option to send feedback and the report to SAP for analysis.

More Information

For more information about the process overview html reports, see the article Get to Know the Process Overview Reporting in Software Update Manager available at http://scn.sap.com/docs/DOC-14729 .

A.2 Troubleshooting

This chapter contains information about how to proceed when you want to correct known problems that have occurred during the update.

NoteIn the following, some information is related to steps. As long as the Software Update Manager is running, the step name is displayed on the program tool tab page.

● SL Common UI○ SL Common UI: Solving Problems with the UI [page 104]

● Logs○ Update Logs [page 104]○ Tracing [page 106]

● Correcting errors in steps○ Enhancement package installation and SPS update: Correcting Errors in the DEPLOY_ONLINE_* Steps

[page 106]○ Release upgrade only: Correcting Problems in the DEPLOY_* Steps [page 108]○ Release upgrade only: Correcting Errors in the RUN_OFFLINE_MIGRATION Step [page 109]

● General problems○ Reentering Passwords [page 110]○ Using the SUM Forced Mode [page 111]○ Only valid for 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

Starting and Stopping the AS Java Manually [page 111]End of 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

○ Only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3Release upgrade onlyCorrecting InstanceID Issues [page 112]End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

In addition to the problems listed here, also read the SAP Notes that are relevant to this update.

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBAppendix PUBLIC 103


A.2.1 SL Common UI: Solving Problems with the UI

If you have problems with the SL Common UI, you have several options to solve these issues.

Context

You have several options that might help to solve a problem with SL Common UI, for example, if an error or a system failure occurred. Note that the following procedure does not represent a sequence that you have to follow step by step, but it has to be read in this way: If the restart of the UI does not work, try step 2. If the restart of the SAP Host Agent does not lead to any success, try step 3, and so on.

Procedure

1. Restart the SL Common UI as described in Starting and Restarting the Software Update Manager [page 55].

2. Restart the SAP Host Agent using the following command:

<HOSTAGENT directory>/exe/saphostexec -restart3. Install the latest SAP Host Agent version.4. Cancel the running SAPup processes that were started by the SL Common UI. These processes will be

started again automatically as soon as you start the SL Common UI again in the Web browser.5. To prevent that browser plug-ins and settings interfere with the SL Common UI, enter the URL in a new

browser window in Private Browsing mode of Microsoft Internet Explorer, Microsoft Edge, or Mozilla Firefox, or the Incognito mode of Google Chrome.

6. If the problems persist, proceed as described in SL Common UI: Getting Support Using the Support File [page 23].

A.2.2 Update Logs

The Software Update Manager logs all actions in log files to monitor the update. You can access the log files using the Log option on the user interface. Unless otherwise specified below, the log files are stored in the log subdirectory of the sdt subdirectory of the SUM directory.

If you encounter any errors, you can analyze them to help you find a solution.

Trouble tickets are special log files that are created when an error occurs.


Appendix

Logging of the Java Update

Log FilesThere is a log file for each update step. Additional service programs, which are called from the Software Update Manager, also write log files.

Logs that end with the extensions *.out and *.err belong to service programs, for example, from migration programs for different components.

You can view the log files using the log viewer that is integrated into the Software Update Manager GUI. To access it, choose Update Logs .

Enhancement package installation and SPS update:

The log files are stored under SUM/sdt/log/SUM and have the following naming convention:

<step name><nn>.log where <nn> is the number of step iterations you have already performed.

ExampleLog file for DEPLOY_KERNEL_BINARIES step: DEPLOY_KERNEL_BINARIES_01.LOG.

Release upgrade only:

The log files are stored under SUM/sdt/log and have the following naming convention:

<step name><three-character-id><nn>.log where <nn> is the number of step iterations you have already performed.

ExampleLog file for DEPLOY_ONLINE_SHD step: DEPLOY_ONLINE_SHD_DLS_01.LOG.

Trouble TicketsTrouble tickets are stored under SUM/sdt/log/SUM (for enhancement package installation and SPS update) or SUM/sdt/log (for release upgrade) and use the following naming convention:

TroubleTicket_<xx>.txt where <xx> is the number of the error (not related to the step number).

The trouble ticket contains general information about the system and the error. It references the names of the log files for the step and the external processes. You can use the terms at the end of the ticket to search for SAP Notes related to the error.

If you report an incident, attach the trouble ticket to it to provide SAP Support with the information.


A.2.3 Tracing

Context

During the update, a trace file is created and saved in the following directory:

<path to SUM directory>/SUM/sdt/trc

The default trace level is set to ERROR. You can raise it to gather more information by editing the logging.properties file.

Procedure

1. Stop SUM and ensure that no leftover processes are running.2. Set the com.sap.sdt.severity and /System/Server/Upgrade.severity parameters to DEBUG in

the following locations, respectively:○ SUM/sdt/param/logging.properties○ SUM/sdt/prop/logging.properties

3. Start SUM again and repeat the failing step.

Next Steps

If you encounter any update problems, you have to provide access to the following directories to SAP Support:

● SUM/sdt/log● SUM/sdt/trc● SUM/sdt/htdoc/ProcessOverview.html● SUM/summanifest.mf● SUM/sdt/data/SharedInputCatalog.xml● SUM/sdt/sdt/data/variables

A.2.4 Correcting Errors in the DEPLOY_ONLINE_* Steps

Use

NoteThis section is relevant if you perform an enhancement package installation or SPS update.


Appendix

The target release components are deployed in the DEPLOY_ONLINE_* steps. If an error occurs in these steps, check the specific step log file for detailed information. See also the following sections for information about known problems.

Procedure

Out of Memory Error

The deployment of the queue can finish with an Out of Memory error if not enough virtual memory is available. To solve this problem, use the Config Tool and set the heap size and permanent space Java parameters as described in SAP Note 723909 .

If you encounter such an error in the DEPLOY_ONLINE_* steps and SAP Note 723909 does not solve your problem, increase the value of the *.MaxHeapSize property in the startup.properties configuration file. The file is located at /usr/sap/<SID>/SUM/sdt/data/kernel/startup.properties.

Hang Situation During Deployment

If your database is SAP MaxDB, the deployment may continue longer than expected. Possible reasons and recommended solutions are as follows:

1. The logs are fullWe recommend that you activate the overwrite mode for the log area.

2. The configured number of database sessions (parameter MAXUSERTASKS) is no longer sufficientThe following rule of thumb applies for setting the parameter MAXUSERTASKS:MAXUSERTASKS = 2*<number of work processes> + 4Set the parameter to the calculated value (at least 85 is recommended) and restart the database instance offline.

System Left in SAFE Mode After the DeploymentOnly valid for 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

It is possible that after the deployment has finished, the system remains in SAFE mode. This can be observed in the file /usr/sap/<SID>/J<instance number>/j2ee/cluster/instance.properties, property instance.runMode.End of 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

Deployment in SAFE mode is more stable and overall execution time is lower than deployment while the system is in NORMAL mode. After the deployment, the Software Update Manager tries to set the system back to NORMAL mode. This switch may fail due to various reasons – misconfigured system, executable permissions, and so on.

You need to set your system in NORMAL mode manually. Proceed as follows:

1. Stop the SUM Java process manually.2. Only valid for 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4

Start the Config Tool script file from the directory /usr/sap/<SID>/J<instance number>/j2ee/configtool.End of 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4

3. In the menu, choose File Safe Mode .A dialog box appears.




4. From the Safe Mode Enabled dropdown list, choose No.5. Choose OK.6. Save the settings and confirm all the messages that are displayed.7. Restart AS Java.

A.2.5 Correcting Problems in the DEPLOY_* Steps

Context


The target release components are deployed during the DEPLOY_ONLINE_SHD steps (deployment of file system and application components) and DEPLOY_ONLINE_DB (deployment of database schema and content) steps.

Procedure

1. If an error occurs in one of the deployment steps, look in the following log and trace files for detailed information:○ deploy_<timestamp>.log○ deploy_<timestamp>.trc

The timestamp format is YY-MM-DD_HH-MM-SS.

Search for the string “Error” in the log files.2. Depending on the error, proceed as described below.

○ ERROR: Not deployed. Deploy Service returned ERROR:java.rmi.RemoteException: Cannot deploy application <application name>.[..]This error message occurs if a component cannot be deployed.You can find the name of the Software Component Archive (SCA) that failed to be deployed at the end of the log file.If you detect such a problem, report an incident and assign it to component BC-JAS-DPL or to the component of the SCA that cannot be deployed.

○ If there is no error message, but the DEPLOY_ONLINE step runs for a long time, then check the <instance directory>/work/deploy.<i>.log file for activity.During the deployment on the shadow system, <instance directory> is the following directory:SUM/sdt/<SID>/JC<xx>During the deployment on the original system, <instance directory> is the following directory:usr/sap/<SID>/<instance_name>The <i> in the deploy log is a number that is incremented each time a new log file is created because the previous one became too large.


Appendix

If there is no activity in the log file and the timestamp is not changing, check whether there is a problem with the database.

○ Failure of DEPLOY_* steps can be related to a wrong system state of the AS Java. During the runtime of the DEPLOY_* steps, the system has to be in a defined state, that is, the AS Java either has to be stopped or has to be running. If the system is not in this defined state because of errors in the start or stop procedures, the steps fail. Proceed as follows:1. Open the steplist.xml file located in SUM/sdt/param and search for the failed step.2. Check the previous step (START_*, STOP_*) to find out in which state the AS Java should be.3. Check the state of your AS Java. If it is not in the expected state, then start or stop the AS Java, as

required.For information about the procedure, see Starting and Stopping the AS Java Manually [page 111].

4. Repeat the step.

A.2.6 Correcting Errors in the RUN_OFFLINE_MIGRATION Step

Context


During the upgrade, there are migrations that are executed as separate Java processes. By default, these Java processes are called with the following heap size parameters:

-Xmx1024m -XX:MaxPermSize=256m

If the migration process needs more memory and fails with an Out Of Memory error in the RUN_OFFLINE_MIGRATION step, you have to increase the default values of the heap size.

Procedure

1. Stop SUM.2. Increase the default values of the heap size by editing the configuration file JMTJVMArguments.xml,

which is located in the SUM/sdt/config directory, and save your changes

3. Restart SUM and repeat the failed step.


A.2.7 Reentering Passwords

Prerequisites

You have to be in a dialog step, that is, SUM is waiting for user input or actions.

Context

You have the option to reenter passwords that you entered in the Configuration roadmap step. Use it if, for example, you have accidentally entered a wrong password, or the update has failed because you changed a password after the Configuration roadmap step has been passed.

You can update the following passwords using this option:

● Standard database schema password – if you have changed the standard database schema password after the Configuration roadmap step, you have to run the Reenter password option so that the SUM can read the new password from the secure store.

NoteThe credentials for the shadow schema database user used during the update process are copied from the standard schema database user contained in the secure store.

● AS Java Administrator user password● SDM user password● SAPService<SID> user password● <SID>ADM user password

Procedure

1. On the SL Common UI, choose More Reenter Passwords .

The Specify User Credentials dialog is displayed.2. Enter the passwords that need to be changed.3. Choose Continue.

NoteIn error cases that require reentering the AS Java Administrator credentials and the SDM password, SUM displays a dialog where you can do so. Note that the credentials are not validated, as the AS Java is not operational during the downtime.


Appendix

A.2.8 Using the SUM Forced Mode

This section describes how you start the forced mode.

Context

The Software Update Manager can be set to work in forced mode. You can use this mode, for example, if you want to perform deployment of development components (DCs) when using the manually prepared SUM directory.

Procedure

1. Navigate to /usr/sap/<SID>/SUM/sdt/param/ and open the jspm_config.txt file for editing.

2. Set the following parameter values as follows:

/jspm/deployVersionRule = updateAll

/jspm/forceMode = True

For more information about deployment of DCs, see SAP Note 1824237 .

A.2.9 Starting and Stopping the AS Java Manually

This topic is only valid for 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

Procedure

To start the AS Java, proceed as follows:

1. Release upgrade only: Make sure that the library path variable points to the target release kernel:○ setenv LD_LIBRARY_PATH <SUM directory>/sdt/data/kernel:$LD_LIBRARY_PATH○ setenv SHLIB_PATH <SUM directory>/sdt/data/kernel:$SHLIB_PATH○ setenv LIBPATH <SUM directory>/sdt/data/kernel:$LIBPATH

2. Start the instance with the following command:Release upgrade only: <SUM directory>/sdt/data/kernel/sapcontrol -prot NI_HTTP -nr <–number> -function StartEnhancement package installation and SPS update only: /usr/sap/<SID>/SYS/exe/sapcontrol -prot NI_HTTP -nr <–number> -function Start

3. Check whether the AS Java is running with the following command:Release upgrade only: <SUM directory>/sdt/data/kernel/sapcontrol -nr <instance number> -host <host name> -function WaitforStarted 3600 10



Enhancement package installation and SPS update only: /usr/sap/<SID>/SYS/exe/sapcontrol -nr <instance number> -host <host name> -function WaitforStarted 3600 10If the AS Java is started correctly, the following message appears:<date> <time>WaitforStartedOKIf the startup of the AS Java has failed, the following message appears:<date> <time>WaitforStartedFAIL: <Reason for failure>

To stop the AS Java, proceed as follows:

1. Enter the following command:Release upgrade only: <SUM directory>/sdt/data/kernel/sapcontrol -nr <instance number> -host <host name> -user <sid>adm <password> -function StopEnhancement package installation and SPS update only: /usr/sap/<SID>/SYS/exe/sapcontrol -nr <instance number> -host <host name> -user <sid>adm <password> -function Stop

2. Check whether the AS Java is stopped by executing the following command:Release upgrade only: <SUM directory>/sdt/data/kernel/sapcontrol -nr <instance number> -host <host name>-function WaitforStopped 3600 10Enhancement package installation and SPS update only: /usr/sap/<SID>/SYS/exe/sapcontrol -nr <instance number> -host <host name> -function WaitforStopped 3600 10If the AS Java is stopped correctly, the following message appears:<date> <time>WaitforStoppedOKIf the stop of the AS Java has failed, the following message appears:<date> <time>WaitforStoppedFAIL: <Reason for failure>

End of 'Target Release': SAP NetWeaver 7.3, SAP NetWeaver 7.3 EHP 1, SAP NetWeaver 7.4, SAP NetWeaver 7.5

A.2.10 Correcting InstanceID Issues

This topic is only valid for 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

During a release upgrade, the detected instanceID and calculation from the box number might not match. This indicated that the system is inconsistent, which might cause errors during system maintenance or provisioning processes.

To prevent this issue, check if your instanceID number and the box number calculation match, and correct them manually if required. Alternatively, you can run the Correction of Installed Software Information [page 100] procedure to fix any system information inconsistencies.

If you encounter this issue during your update, proceed as described in section "Verifying and Adjusting the instanceID of an AS Java Instance" of the Software Provisioning Manager documentation at http://support.sap.com/sltoolset System Provisioning , in the Dual-Stack Split, System Rename, or System Copy guides for systems based on SAP NetWeaver 7.0/7.0 EHPs and higher.


Appendix



For additional information see SAP Note 2259748 .

End of 'Source Release': SAP NetWeaver 7.0, SAP NetWeaver 7.0 EHP 1, SAP NetWeaver 7.0 EHP 2, SAP NetWeaver 7.0 EHP 3

A.3 List of Referenced SAP Notes

In addition to the SAP Notes that you need to prepare the update (see SAP Notes [page 11]), this document also refers you to other SAP Notes that contain additional information. The following lists contain these SAP Notes:

Database-Independent SAP Notes

SAP Note Number Description Area

2431737 SUM with IBM PowerHA System Mirror for AIX

Update of HA systems

1779681 Central note on HPE Serviceguard HA/DR clustering solutions

Update of HA systems

723909 Java VM settings for J2EE 7.0 General Update

823941 SAP start service Release upgrade only

1021236 Linux: Using SAP kernel 7.01 and higher on RHEL4 and SLES9

Linux

927637 Web service authentication in sapstartsrv as of SAP NetWeaver 7.00

General update, System administration / troubleshooting

837670 Minimum OS patch recommendations for HP-UX

General update

1630256 Usage of the "memory-optimized activator" during upgrades and enhancement package installations

General update

System administration / troubleshooting

421359 ICM: Binding ports < 1024 on Unix General update

System administration

1641062 Single component update and patch scenarios in SUM

Single component updates

1793486 Installing Add. Usage Types on Existing SAP System – Using SUM

Installation

1864705 Compatibility checks for certified HA setups


1824237 Redeploying customized development components with SUM

General Update

1759081 Conditions for SUM feature Deployment Optimization Option

General Update


















1629598 SAP kernel 720 will replace older kernel versions

General Update

1951491 Minimum database system platform requirements for SAP NetWeaver 7.4 SP08

General Update

1704753 Inst.Systems based on NetWeaver 7.1 and higher: UNIX


1877731 Installed Software Information (ISI) Installing additional usage types (technical usages) or product instances

1738760 SAPLOCALHOST settings as a profile parameter and environment variable

General update


2130510 SAP Host Agent 7.21 General update

System administration

1031096 Installing package SAPHOSTAGENT General update


1907566 Obtaining the latest SAP Host Agent documentation

General update

609603 Problems with Multiple NICs and SAP J2EE Engine

General update


1974464 Information about SCA Dependency Analysis for Java download objects

Single component updates


1873529 Correcting Errors with RUN_SOURCE_ONLINE_MIG_CONTROLLERS During SAP NetWeaver Migration

General update

System Maintenance

2011380 Previous SUM not finished properly and asking for Clean Module Password

Troubleshooting

2259748 Fixing wrong instanceID using Software Provisioning Manager

Troubleshooting

1987497 Switch upgrade is failing at step "Check detected instance IDs or request missing config manager IDs"

Troubleshooting

2259748 Fix wrong instance ID using Software Provisioning Manager

Troubleshooting


Appendix

















1240081 Java Cryptography Extension (JCE) Jurisdiction Policy Files

General update

1642340 sapcontrol SSL usage General update

SAP MaxDB


1173395 FAQ: SAP MaxDB and liveCache config-uration

MaxDB

A.4 List of Referenced Documentation

The following table contains a list of all documentation referenced in this document and information about where to find this documentation.

Referenced Documentation

Document Internet Address

For the SAP NetWeaver release:

● Upgrade Master Guide● Master Guide● Upgrade and Update Guides● Installation Guide

http://help.sap.com/netweaver SAP NetWeaver <release>

<Version> Installation and Upgrade

See also Accessing SAP NetWeaver Library [page 12].

For your SAP application:

● Upgrade Master Guide● Master Guide● Upgrade Guide● Installation Guide

http://help.sap.com/erp <version> Installation and

Upgrade

DMO Guide (guide for the database migration option of SUM)

http://support.sap.com/sltoolset System

Maintenance Database Migration Option (DMO) using

SUM

Installation Guide http://support.sap.com/sltoolset System Provisioning

Install a System using Software Provisioning Manager





http://help.sap.com/netweaver

http://help.sap.com/erp



Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free LanguageSAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders, and abilities.


Important Disclaimers and Legal Information

Updating SAP Java Systems on UNIX and Linux: SAP MaxDBImportant Disclaimers and Legal Information PUBLIC 117

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

Updating SAP Java Systems on UNIX and Linux: SAP MaxDB

Documents