sap ehp4 maxdb windows abap installation guide

Installation GuideSAP ERP 6.0 - EHP4 Ready ABAP on Windows: SAP MaxDBBased on SAP NetWeaver 7.0 including Enhancement Package 1

Target Audience

n System Administratorsn Technical Consultants

PUBLICDocument version: 1.3 ‒ 05/25/2009

About this Installation Guide

SAP System Installation

SAP system installations should only beperformed by SAP Technical Consultantscertified for your operating system, yourdatabase, and the SAP system that you areinstalling

SAP Installation Tool

You must only use the SAP installation toolsaccording to the instructions and for thepurposes described in the SAP installationdocument. Improper use of the SAP installationtools can damage files and systems alreadyinstalled.

Downward Compatibility of Databases

For downward-compatible releases of DB/OSplatforms for SAP products, SAP plans to

regularly release the newest database (DB) andoperating-system (OS) versions of SAP products.These releases are downward-compatible withearlier SAP system releases.Note that for already shipped SAP components,we only support the installation for databaseversions proposed by the installationtool. Therefore, you must install an SAPcomponent or perform a system copy usinga downward-compatible database. Thatis, you either install the component withthe old proposed database version or youupgrade the old database version to thedownward-compatible new version.

2/152 PUBLIC 05/25/2009

Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan find the latest version at the following location:http://service.sap.com/erp-inst.

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

Version Date Description

1.30 5/25/2009 Minor Changes

1.20 2/17/2009 Updated information in Introduction [page 7]

1.10 2/5/2009 Removed information from Introduction [page 7]

1.0 11/21/2008 Initial Version

05/25/2009 PUBLIC 3/152

http://service.sap.com/erp-inst



Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 71.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 81.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 10

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 Basic System Variants . . . . . . . . . . . . . . . . . . . . . 132.2 Hardware and Software Requirements . . . . . . . . . . . . . . . 142.2.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 162.2.2 Requirements for a Central System . . . . . . . . . . . . . . . . 172.2.3 Requirements for a Distributed System . . . . . . . . . . . . . . 192.2.4 Requirements for a High-Availability System . . . . . . . . . . . . 212.2.5 Requirements for the Dialog Instance . . . . . . . . . . . . . . . 242.3 Domain or Local Installation . . . . . . . . . . . . . . . . . . 242.4 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . 252.5 Distribution of Components to Disks . . . . . . . . . . . . . . . 262.6 SAP System Transport Host . . . . . . . . . . . . . . . . . . . 282.7 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 29

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 353.1 Disabling the Windows Server 2008 Firewall Temporarily . . . . . . . . 353.2 Checking the Windows File System . . . . . . . . . . . . . . . . 363.3 Checking the Windows Domain Structure . . . . . . . . . . . . . 373.4 Reducing the Size of the File Cache . . . . . . . . . . . . . . . . 373.5 Required User Authorization for Running SAPinst . . . . . . . . . . 383.6 Preparing the SAP System Transport Host . . . . . . . . . . . . . 403.7 Installing the Front-End Software . . . . . . . . . . . . . . . . 413.8 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 413.9 Installing the Java Runtime Environment . . . . . . . . . . . . . 413.10 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 423.11 Downloading Installation DVDs from SAP Service Marketplace . . . . . 44

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 474.1 Installing an SAP System Using SAPinst . . . . . . . . . . . . . . 474.1.1 Running SAPinst on Windows . . . . . . . . . . . . . . . . . . 474.1.2 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 55

4/152 PUBLIC 05/25/2009

4.1.3 How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . 564.1.4 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 564.1.5 Performing a Remote Installation with SAPinst . . . . . . . . . . . 584.1.6 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . 594.1.7 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 62

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 635.1 Configuring the Windows Server 2008 Firewall . . . . . . . . . . . . 645.2 Logging On to the Application Server . . . . . . . . . . . . . . . 655.3 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 665.4 Installing the SAP License . . . . . . . . . . . . . . . . . . . 685.5 High Availability: Setting Up Licenses . . . . . . . . . . . . . . . 685.6 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 695.7 Creating Symbolic Links on Windows Server 2008 for Application Servers . . 705.8 Configuring Remote Connection to SAP Support . . . . . . . . . . 715.9 Installing the SAP Online Documentation . . . . . . . . . . . . . 715.10 Performing Initial ABAP Configuration . . . . . . . . . . . . . . 715.11 Performing a Full System Backup . . . . . . . . . . . . . . . . 755.12 Configuring the Connection to a Central System Landscape Directory . . . 765.13 Implementing ERP ABAP Add-On Components . . . . . . . . . . . 765.14 Installing or Upgrading Database Studio for SAP MaxDB . . . . . . . . 765.15 Secure Sockets Layer Protocol for Database Server Communication . . . . 785.15.1 Installing the SAP Cryptographic Library . . . . . . . . . . . . . . 785.15.2 Generating the Personal Security Environment . . . . . . . . . . . 805.16 Updating the Database Software to the Current Release . . . . . . . . 825.17 Performing the Client Copy . . . . . . . . . . . . . . . . . . 825.18 Accessing Configuration Documentation in SAP Solution Manager . . . . 83

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 856.1 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . 856.2 Performing a Domain Installation Without Being a Domain Administrator . 896.3 Installation of Multiple Components in One Database . . . . . . . . . 926.4 Integration of LDAP Directory Services . . . . . . . . . . . . . . 946.5 Starting and Stopping the SAP System . . . . . . . . . . . . . . . 976.6 Implementing Single Sign-OnwithMicrosoft Kerberos SSP for Your SAP System 986.7 SAP System Security on Windows . . . . . . . . . . . . . . . . 996.8 Automatic Creation of Accounts and Groups . . . . . . . . . . . . 1016.9 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 1026.9.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 1026.10 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 103

Chapter 7 High Availability with Microsoft Cluster Service . . . . . . . . . 105

05/25/2009 PUBLIC 5/152

7.1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 1067.1.1 System Configuration in MSCS . . . . . . . . . . . . . . . . . 1077.1.1.1 SAP System Components in an MSCS Configuration . . . . . . . . . 1077.1.1.2 Enqueue Replication Server in an MSCS Configuration . . . . . . . . 1107.1.2 Distribution of SAP System Components to Disks for MSCS . . . . . . . 1117.1.3 Directories in an MSCS Configuration . . . . . . . . . . . . . . . 1157.1.4 IP Addresses in an MSCS Configuration . . . . . . . . . . . . . . 1167.1.5 Obtaining and Determining IP Addresses for MSCS . . . . . . . . . . 1197.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 1227.2.1 Assigning Drive Letters for MSCS . . . . . . . . . . . . . . . . 1227.2.2 Mapping Host Names to IP Addresses for MSCS . . . . . . . . . . . 1237.2.3 Checking the Mapping of Host Names for MSCS . . . . . . . . . . . 1247.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . 1257.3.1 Moving MSCS Groups or Services and Applications . . . . . . . . . . 1267.3.2 Rebooting During the Installation or Conversion for MSCS . . . . . . . 1277.3.3 Installing the Central Services Instance for ABAP (ASCS) . . . . . . . . 1277.3.4 Configuring the First MSCS Node . . . . . . . . . . . . . . . . 1297.3.5 Installing the Database on the First Node . . . . . . . . . . . . . . 1307.3.6 Configuring the Database on the Additional Node . . . . . . . . . . 1307.3.7 Installing the Database Instance . . . . . . . . . . . . . . . . . 1317.3.8 Configuring the Additional MSCS Node . . . . . . . . . . . . . . 1317.3.9 Installing an Enqueue Replication Server . . . . . . . . . . . . . . 1337.3.10 Installing the Central Instance . . . . . . . . . . . . . . . . . 1347.3.11 Installing the Dialog Instance . . . . . . . . . . . . . . . . . . 1357.4 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . 1367.4.1 Starting and Stopping the SAP System in an MSCS Configuration . . . . . 1367.4.2 Post-Installation Checks for Enqueue Replication Server . . . . . . . . 1387.4.2.1 Checking the Status of the Enqueue Replication Server with ENSMON . . . 1387.4.2.2 Monitoring the Lock Table During Failover with ENQT . . . . . . . . 139

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . 141A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . 141

6/152 PUBLIC 05/25/2009

1 Introduction

1 Introduction

This document explains how to install SAP ERP 6.0 — EHP4 Ready (EHP4 for SAP ERP 6.0) ABAP.You perform the installation using SAPinst.SAP ERP 6.0 ‒ EHP4 Ready is based on the technology of SAP NetWeaver 7.0 including enhancementpackage 1. For more information about the technology provided by SAP ERP and SAP NetWeaver, seehttp://service.sap.com/erp and http://sdn.sap.com/irj/sdn/netweaver.Make sure you read the corresponding Master Guides before you start with this installation guide.The Master Guides are available as follows:http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP

enhancement package 4 for SAP ERP 6.0

Caution

See SAP Note 998833 for up-to-date information about release restrictions for EHP4 for SAP ERP 6.0.

You can install SAP ERP 6.0 - EHP4 Ready with the following software units:

n SAP ERP Central Component (ECC)

Note

SAP ERP Central Component (ECC) is not installed with the Java Add-In.

Note

You also install SAP NetWeaver Application Server ABAP (AS ABAP) with SAP ERP CentralComponent.

For more information about the usage types of SAP NetWeaver and their interdependencies, seethe documentMaster Guide ‒ SAP NetWeaver 7.0 at http://service.sap.com/instguidesNW70. Forrestrictions, see SAP Note 1164532.

Constraints

You need to consider the following constraints before you start your installation:

n Your operating system platform must be 64-bit.

Note

The only instance, you can still install on 32-bit is the dialog instance.

05/25/2009 PUBLIC 7/152

http://service.sap.com/erp



http://sdn.sap.com/irj/sdn/netweaver




http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=998833&_NLANG=en&_NVERS=0

http://service.sap.com/instguidesNW70




1 Introduction1.1 New Features

You need to consider the following constraints after the installation:

n The installation of SAP ERP 6.0 - EHP4 Ready ABAP system based on SAP NetWeaver 7.0 includingenhancement package 1 contains only the basic EHP4 for SAP ERP 6.0 technical usage “ABAPTechnology for ERP EHP4”. To complete the installation process you have to install additionalEHP4 for SAP ERP 6.0 functionality in your SAP ERP 6.0 - EHP4 Ready ABAP system. You mustuse the Solution Manager Maintenance Optimizer to identify and download the correspondingsoftware components and the SAP enhancement package Installer to deploy the downloadedsoftware components in your system.For more information about the Solution Manager Maintenance Optimizer, see:http://service.sap.com/solman-mopz.For more information about the SAP enhancement package Installer, see the document InstallationGuide - SAP Enhancement Package Installation - Using SAP Enhancement Package Installer (SAPehpi) at:http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0

SAP enhancement package 4 for SAP ERP 6.0 Enhancement Package Installation on Existing SAP Systems

n You have to apply at least Support Package Stack (SPS) 1 of SAP enhancement package 4 forSAP ERP 6.0.

Naming Conventions

Terminology

n SAP system refers to EHP4 for SAP ERP 6.0.n ABAP system refers to EHP4 for SAP ERP 6.0 ABAP.

1.1 New Features

The following tables provide an overview of the new features related to the installation of this release:

Caution

Make sure that you read the release notes for your SAP system. You can find these athttp://service.sap.com/releasenotes

8/152 PUBLIC 05/25/2009

http://service.sap.com/solman-mopz







http://service.sap.com/releasenotes



1 Introduction1.1 New Features

SAP System Installation

Area Description

SAPinst As of SAP enhancement package 4 for SAP ERP 6.0, SAPinst has the following newfeatures:n You no longer have to install a Java Runtime Environment (JRE) to start the

SAPinst GUI.However, you still have to install a JRE to perform the installation with SAPinst(see Installing the Java Runtime Environment (JRE) [page 41]).

n If you want to terminate SAPinst from the SAPinst GUI menu, you now have tochoose SAPinst Cancel . If you choose File Exit , you only terminatethe SAPinst GUI (see Using SAPinst GUI [page 55]).

n You can directly access installation log files from the SAPinst GUI menu bychoosing SAPinst Log Browser (see Using SAPinst GUI [page 55]).

64-bit support onlyfor all instances exceptdialog instances

As of SAP ERP 6.0 SR3, you must install an SAP ERP system only on 64-bit operatingsystems.For the dialog instance, you can still use a 32-bit operating system. Therefore, youonly see the folder Software Life-Cycle Options on theWelcome screen when you start theinstallation from a 32-bit installation master DVD.You might need to install dialog instances on 32-bit operating systems if you want touse 32-bit SAP NetWeaver components, such as Adobe document services. However,first check whether such 32-bit components can run on 64-bit operating systems. Ifso, we recommend running these 32-bit components on a 64-bit operating system.

No new dual stack(ABAP+Java) systemsfor SAP enhancementpackage 4 for SAP ERP6.0

As of SAP enhancement package 4 for SAP ERP 6.0, you can no longer install SAPERP dual stack (ABAP+Java) systems. If you want to use both SAP ERP ABAP andJava Components in your system landscape, you have to proceed as follows:

1. Install a separate SAP ERP ABAP system.

2. Install a separate SAP ERP Java system.

3. Configure the connection of the SAP ERP Java system to the SAP ERP ABAPback-end system

Installation option JavaAdd-In for ABAP disabled

As of SAP enhancement package 4 for SAP ERP 6.0, the installation option JavaAdd-In for ABAP is disabled. That is, you can no longer install the Java Add-In to anexisting ABAP system.

High AvailabilityNote

As of Windows Server 2008, the Windows cluster terminology has changed.

n The cluster feature is now called Failover Clustering. For practical reasons we arecontinuing to use the general abbreviationMSCS in this guide.

n Cluster groups are now called services and applications.n The Cluster Administrator is now called Failover Cluster Management.

MaintenanceOptimizer

All downloadable software components, released after April 2, 2007, are availableexclusively through the Maintenance Optimizer in SAP Solution Manager. Thiscomprises:n Support Package Stacks, Support Packages, and patches for Java instances, except

for kernel patchesn Legal changesn SAP applications and versions that are:

05/25/2009 PUBLIC 9/152

1 Introduction1.2 SAP Notes for the Installation

Area Description

l Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and allapplications based on this software, including SAP Business Suite 7

l Optional for all SAP applicationsFor more information, see http://service.sap.com/solman-mopz.

Operating Systems and Platforms

Area Description

Support of OperatingSystems and Platforms Note

This document already includes information about the newWindows operatingsystem,Windows Server 2008, although this is not yet supported by SAP atthe time of publishing.

n For supported operating system and database releases, see the Product AvailabilityMatrix at http://service.sap.com/pam.

n For forums, blogs, content, and community related to all of the supporteddatabases and operating systems, see the Database and Operating Systems area athttp://sdn.sap.com/irj/sdn/dbos.

Database-Specific Features

Area Description

Database name “MaxDB” is now called “SAP MaxDB”.

1.2 SAP Notes for the Installation

Youmust read the following SAP Notes before you start the installation. These SAP Notes contain themost recent information on the installation, as well as corrections to the installation documentation.Make sure that you have the up-to-date version of each SAP Note, which you can find athttp://service.sap.com/notes.

SAP Notes for the Installation

SAP Note Number Title Description

998833 Release Restrictions SAP ERP 6.0- Enhancement Packages

At the time of the release of EHP4 for SAP ERP6.0, limitations affect the productive usage ofcertain functions. This note provides customerinformation on these restrictions.

1165067 Release Info SAP EnhancementPackage 4 for SAP ERP 6.0

SAP Enhancement Package 4 for SAP ERP 6.0release information.

10/152 PUBLIC 05/25/2009


http://service.sap.com/pam

http://sdn.sap.com/irj/sdn/dbos

http://service.sap.com/notes





1 Introduction1.2 SAP Notes for the Installation

SAP Note Number Title Description

1164532 Release Restrictions for SAPNetWeaver 7.0 EHP1

Customer information on restrictions in theproduction use of certain functions.

1171448 SAP NetWeaver 7.0 EHP1/Business Suite 7: Windows

Windows-specific information about the SAPsystem installation and corrections to thisdocumentation.

1172652 SAPNetWeaver 7.0 EHP1/BusinessSuite 7 on Win: SAP MaxDB

Platform-specific information about the SAPsystem installation (ABAP and Java) andcorrections to this documentation

820824 FAQ: MaxDB Frequently asked questions (FAQ) on MaxDB

855498 Installation Prerequisite Checker SAP Software on UNIX, Windows and IBM i:Checking OS Dependencies

73606 Supported Languages and CodePages

Information on possible languages and languagecombinations in SAP systems

1067221 Central Note for HeterogeneousInstallation

Heterogeneous ABAP system landscapes ondifferent operating systems have been releasedfor some time. Heterogeneous Java systemlandscapes on different operating systems havenow also been released. However, not everycombination of operating system and databasesystem is released. This SAP Note and its relatedSAP Notes describe the released operating systemand database combinations.

789220 Support Packagelevel for NetWeaverInstallations/Upgrades

Information about the ABAP Support Packagelevels and kernel patch levels contained in thecurrent SAP NetWeaver release.

774615 Support Package levels ofERP/ECC installations/upgrades

Information about the ABAP Support Packagelevels and kernel patch levels contained in thecurrent SAP ERP release.

1258912 PLM Core 7.00 Release Notes andInformation

Information and references to other notes aboutinstalling PLM Core 7.00 and importing PLMCore 7.00 Support Packages.

05/25/2009 PUBLIC 11/152










http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1258912 &_NLANG=en&_NVERS=0

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

2 Planning

2 Planning

This section tells you how to plan the installation of your SAP system.You have to complete the following planning activities, which are described in more detail in thelinked sections:

1. You plan your SAP system landscape according to theMaster Guide.In addition, we recommend that you read theTechnical Infrastructure Guide ‒ SAP NetWeaver 7.0, whichis available at: http://service.sap.com/installNW70.

2. You choose your basic system variant [page 13].3. You check the hardware and software requirements [page 14] on each host.4. You decide whether you want to perform a domain or local installation [page 24].5. You plan how to distribute the instances to hosts [page 25].6. For the database installation, you decide on how to distribute your system components [page 26].7. You decide on the transport host to use [page 28].8. You identify basic SAP system parameters [page 29].

9.

Only valid for: HA (MSCS)

If you want to perform a high-availability installation withMicrosoft Cluster Service (MSCS),see also theMSCS-specific planning activities [page 106].End of: HA (MSCS)

The following planning activity is optional:

n Installation of Multiple Components in One Database (MCOD) [page 92]

2.1 Basic System Variants

This section describes the basic system variants and shows how you can distribute SAP systeminstances within these variants.Mandatory instances of an ABAP system are the central instance and the database instance.

Note

Optionally, you can install one or more dialog instances on a separate dialog instance host.

The following graphics show examples for the distribution of the SAP instances in a central system,where the mandatory instances are installed on one host, and a distributed system, where themandatory instances are installed on separate hosts.

05/25/2009 PUBLIC 13/152

http://service.sap.com/installNW70



2 Planning2.2 Hardware and Software Requirements

Figure 1: ABAP System

More Information


For more information about how to distribute SAP instances in a high-availability SAP system, seeSystem Configuration in MSCS [page 107].End of: HA (MSCS)

2.2 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating systemand the SAP instances.

Caution

If your hosts do not fully meet the requirements, you might experience problems when workingwith the SAP system.

Prerequisites

n Contact your OS vendor for the latest OS patches.n Make sure that the host name meets the requirements listed in SAP Note 611361.

14/152 PUBLIC 05/25/2009



Process Flow

1. Check the Product Availability Matrix at http://service.sap.com/pam for supported operatingsystem releases.

2. Check the hardware and software requirements using:n The Prerequisite Checker in one of two modes:l Standalone mode (optional) before the installation process

For more information, see Running the Prerequisite Checker Standalone [page 16].l Integrated in SAPinst (mandatory) during the installation process

For more information, see Running SAPinst on Windows [page 47]

Note

For the most recent updates to the Prerequisite Checker, always check SAP Note 855498.

n The hardware and software requirements checklists for:l Central system [page 17]l Distributed system [page 19]

l


High availability system with MSCS [page 21]End of: HA (MSCS)

l If you want to install dialog instance(s), check the requirements for adialog instance [page 24].

Note

You might need to install dialog instances on 32-bit operating systems if you want to use32-bit SAP NetWeaver components, such as Adobe document services. However, first checkwhether such 32-bit components can run on 64-bit operating systems. If so, we recommendrunning these 32-bit components on a 64-bit operating system.

3. If you are installing a production system, the values provided by the Prerequisite Checker and thehardware and software requirements checklists are not sufficient. In addition, do the following:n You use the Quick Sizer tool available at http://service.sap.com/sizing.

For more information about the Quick Sizer and available sizing guides, see theMaster Guide ‒SAP NetWeaver 7.0 at http://service.sap.com/installnw70 Planning .

n You contact your hardware vendor, who can analyze the load and calculate suitable hardwaresizing depending on:l The set of applications to be deployedl How intensively the applications are to be used

05/25/2009 PUBLIC 15/152



http://service.sap.com/sizing



http://service.sap.com/installnw70


l The number of users

2.2.1 Running the Prerequisite Checker in Standalone Mode(Optional)

Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check thehardware and software requirements for your operating system (OS) and the SAP instances.

Recommendation

We recommend that you use both the Prerequisite Checker and the requirements tables for reference.

Note

When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks thehardware and software requirements in the background.

Prerequisites

n You have prepared the installation master DVD on the required installation host [page 42].

Procedure

1. You start SAPinst [page 47].2. On theWelcome screen, choose <Your SAP product> Software Life-Cycle Options Additional

Preparations Prerequisites Check .3. Follow the instructions in the SAPinst dialogs and enter the required parameters.

Note

For more information about each parameter, position the cursor on the parameter field andchoose F1 in SAPinst.

When you have finished, the Parameter Summary screen appears summarizing all parameters you haveentered and want to have checked. If you want to make a change, select the relevant parametersand choose Revise.

4. To start the prerequisites check, choose Next.

ResultThe Prerequisite Checker Results screen displays the results found. If required, you can also check theresults in file prerequisite_checker_results.html, which you can find in the installation directory.

16/152 PUBLIC 05/25/2009


Recommendation

We recommend making sure that your system meets all checked prerequisites before starting theinstallation. However, you can still start the installation even if your system does not meet allprerequisites. In this case, make sure that you know what you are doing.

2.2.2 Requirements for a Central System

If you want to install a central system, where all instances reside on one host, this host must meetthe following requirements:

Note

The listed values are sufficient for development systems or quality assurance systems but not forproduction systems.

Hardware Requirements for a Central System

HardwareRequirement Requirement How to Check

Minimum disk space n Database Software:Version 7.6: 500 MBVersion 7.7: 700 MB

n SAP system files (not including pagingfile):5 GB (x64)8 GB (IA64)

n For the SAP data:70 GBDistribute the space for the SAP dataacross at least three physically separatedisks

n 4.3 GB of temporary disk space for everyrequired installation DVD that youhave to copy to a local hard disk

To check disk space:

1. Choose Start Control PanelAdministrative Tools ComputerManagement Storage DiskManagement .

2. Right-click the drive and chooseProperties.

Minimum RAM 4 GB To check RAM:In the Windows Explorer, chooseHelp About Windows .

05/25/2009 PUBLIC 17/152



Paging file size 1 times RAM plus 14 GB To check paging file size:

1. Choose Start Control PanelSystem .

2. Choose Advanced (Windows Server2003) or Advanced system settings(Windows Server 2008).

3. Select Performance SettingsAdvanced .

4. If required, in section Virtual memory,choose Change.

Suitable backup system ‒

Software Requirements for a Central System

SoftwareRequirement Requirement How to Check

Windowsoperatingsystem

n English international 64-bit version of one ofthe following Windows Server Editions:l Windows Server 2003uWindows Server 2003 Standard EditionuWindows Server 2003 Enterprise EditionuWindows Server 2003 Datacenter Edition

l Windows Server 2008uWindows Server 2008 Standard EditionuWindows Server 2008 Enterprise EditionuWindows Server 2008 Datacenter EditionuWindows Server 2008 for Itanium-Based

Systems Edition

CautionWindows Server 2008 is not yet supported bySAP at the time of publishing.For up-to-date information on the releasedand supported operating system versionsfor your SAP product and database, seethe Product Availability Matrix (PAM) athttp://service.sap.com/pam .

n For any version of Windows Server, you need thelatest supported service pack

n A suitable Windows Resource Kit is stronglyrecommended

n Updated processor driversFor more information, see SAP Note 1036194.

To check your Windows version:

1. Choose Start All ProgramsAccessories Command Prompt

2. Enter the commandwinver

18/152 PUBLIC 05/25/2009




2.2.3 Requirements for a Distributed System

This section provides information about the hardware and software requirements in a distributedsystem, where the SAP instances can reside on different hosts.The tables show the requirements for the:

n Database instance

n Central instance

n Dialog instance (optional)

Note

n The listed values are sufficient for development systems or quality assurance systems but notfor production systems.

n If you install several SAP instances on one host, you need to add up the requirements.

Hardware Requirements for a Distributed System


Minimum disk space n Database software:Version 7.6: 500 MBVersion 7.7: 700 MB

n For the SAP data:70 GBDistribute the space for the SAP dataacross at least three physically separatedisks

n Central instance (not including pagingfile):5 GB (x64)8 GB (IA64)l In addition you require 4GB (x64), or

8 GB (IA64) per additional platform.n Dialog instance (optional) (not

including paging file):2.5 GB (x64)5 GB (IA64)

n Temporary disk space for every requiredinstallation DVD that you have to copyto a local hard disk:4.3 GB




Minimum RAM 4 GB To check RAM:In the Windows Explorer, chooseHelp About Windows .

05/25/2009 PUBLIC 19/152



Paging file size n Database instance:1.5 times RAM

n Central instance:1 times RAM plus 14 GB

n Dialog instance (optional):1 times RAM plus 14 GB

To check paging file size:


2. Choose Advanced (Windows Server2003) or Advanced system settings(Windows Server 2008).


4. If required, in sectionVirtual memory,choose Change.

Suitable backup system ‒

Software Requirements for a Distributed System



n English international 64-bit version of one ofthe following Windows Server Editions:l Windows Server 2003uWindows Server 2003 Standard EditionuWindows Server 2003 Enterprise EditionuWindows Server 2003 Datacenter Edition

l Windows Server 2008uWindows Server 2008 Standard EditionuWindows Server 2008 Enterprise EditionuWindows Server 2008 Datacenter EditionuWindows Server 2008 for Itanium-Based

Systems Edition

CautionWindows Server 2008 is not yet supported bySAP at the time of publishing.For up-to-date information on the releasedand supported operating system versionsfor your SAP product and database, seethe Product Availability Matrix (PAM) athttp://service.sap.com/pam.

n For any version of Windows Server, you need thelatest supported service pack






20/152 PUBLIC 05/25/2009





2.2.4 Requirements for a High-Availability System

This section provides information about the hardware and software requirements in a high-availabilitysystem.

Note

1. Windows Server 2003 only:You must check that your cluster hardware is certified.AddOn Technology Center for SAP (Add On TCS) certifies hardware platforms for SAP onMicrosoft Windows. The cluster must be included in the Microsoft list of certified clusters and itscomponents. You can access the lists as follows:

n www.microsoft.com/whdc/hcl/default.mspx

n www.saponwin.com

2. Windows Server 2008 only:a) Check that your cluster hardware is certified for Windows Server 2008 and has the Windows

Server 2008 logo.b) You must validate your failover cluster configuration by running the Validate a Configuration

Wizard, which is included in the Failover Cluster Management snap-in. The Failover Cluster ValidationReportmust not show any warnings and errors.

3. The MSCS nodes of the cluster must be connected by a private and public network:n The public network enables communication from the MSCS nodes of the cluster to other

resources in the local area network (LAN).n The private network enables internal communication between the MSCS nodes. In particular,

it enables the Cluster Service running on all MSCS nodes to regularly exchange messages onthe state of the MSCS nodes so that the failure of resources is quickly detected.

4. Each of the MSCS nodes in the cluster must have its own local disks and have access to shareddisks that can be reached by the MSCS nodes via a shared bus.All software ‒ except the Windows operating system, the SAP MaxDB system database, and theMSCS software ‒ is stored on the shared disks.One of the shared disks must be used exclusively by the quorum (if a single quorum device clusteris used) that stores the cluster registry and records information about the state of the cluster.You require at least six shared disks.For more information about the distribution of components to local and shared disk, seeDistribution of SAP System Components to Disks for MSCS [page 111].

05/25/2009 PUBLIC 21/152

http://www.microsoft.com/whdc/hcl/default.mspx

http://www.saponwin.com


Caution

n All disk controllers must be able to support hardware-based RAID.

n You cannot use a host with a domain controller as an MSCS cluster node.

The following tables show the hardware and software requirements for the:

n ABAP central services instance (ASCS)n Database instance

n Enqueue Replication Server instance (ERS)n Central instance

n Dialog instance

Hardware Requirements for a High-Availability System

HardwareRequire-ment Requirement How to Check

Minimumdisk space

n Database Software:Version 7.6: 500 MBVersion 7.7: 700 MB

n ABAP central services instance (ASCS)(not including paging file):5 GB (x64)8 GB (IA64)l In addition you require 4 GB (x64), or 8 GB (IA64)

per additional platform.n For the SAP data:

70 GBDistribute the space for the SAP data across at leastthree physically separate disks

n Enqueue replication server instance (ERS) (notincluding paging file):5 GB (x64)8 GB (IA64)

n Central instance (not including paging file):2.5 GB (x64)5 GB (IA64)l In addition you require 4 GB (x64), or 8 GB (IA64)

per additional platform.n Dialog instance (not including paging file):

2.5 GB (x64)5 GB (IA64)

n Temporary disk space for every required installationDVD that you have to copy to a local hard disk:4.3 GB




MinimumRAM

4 GB To check RAM:In the Windows Explorer, chooseHelp About Windows .

22/152 PUBLIC 05/25/2009


HardwareRequire-ment Requirement How to Check

Paging filesize

n ABAP central services instance (ASCS):1 times RAM plus 1 GB

n Database instance:1.5 times RAM

n Enqueue replication server instance (ERS):1 times RAM plus 1 GB

n Central instance:1 times RAM plus 14 GB

n Dialog instance:1 times RAM plus 14 GB

To check paging file size:


2. Choose Advanced (WindowsServer 2003) or Advanced systemsettings (Windows Server 2008).


4. If required, in section Virtualmemory, choose Change.

NoteYou must adjust the size of thepaging file on allMSCS nodes.

Suitablebackupsystem

‒

Software Requirements for a High Availability System



n English international 64-bit version of oneof the following Windows Server Editions:l Windows Server 2003uWindows Server 2003 Enterprise

EditionuWindows Server 2003 Datacenter

Editionl Windows Server 2008uWindows Server 2008 Enterprise

EditionuWindows Server 2008 Datacenter

EditionuWindows Server 2008 for

Itanium-Based Systems Edition

CautionWindows Server 2008 is not yet supportedby SAP at the time of publishing.For up-to-date information on thereleased and supported operatingsystem versions for your SAP




Note

n Windows Server 2003 only:You must set up the MSCS ClusterService as described in the Microsoftdocumentation. During thissetup you are asked for a WindowsDomain Account to run the ClusterService. We strongly recommendcreating an account different fromthe <sapsid>adm user, for exampleClusterServiceuser=sapprdcladm,where Clustername=sapprdcl.

n Windows Server 2008 only:You must add the operating systemfeature Failover Clustering on allMSCS

05/25/2009 PUBLIC 23/152

2 Planning2.3 Domain or Local Installation


product and database, see theProduct Availability Matrix (PAM)at http://service.sap.com/pam

n For any version of Windows Server, you needthe latest supported service pack



nodes.

End of: HA (MSCS)

2.2.5 Requirements for the Dialog Instance

For more information about the hardware and software requirements for the dialog instance(s), seeone of the following sections:

n Requirements for a Distributed System [page 19]

n


Requirements for a High-Availability System [page 21]End of: HA (MSCS)

2.3 Domain or Local Installation

Before you install the SAP system, you have to decide whether you want to perform a domain orlocal installation, since this affects how the user account information is stored and accessed.For more information about the differences between a local and domain installation, see theMicrosoft article Deciding Between Workgroups and Domains at:http://technet2.microsoft.com/windowsserver/en/library/

24/152 PUBLIC 05/25/2009



http://technet2.microsoft.com/windowsserver/en/library/

2 Planning2.4 How to Distribute Instances to Hosts

Domain Installation

In a domain installation, the user account information is stored centrally in one database on thedomain controller and is accessible to all hosts in the system.You have to perform a domain installation if one of the following applies:

n You install a distributed system (strongly recommended to avoid authorization problems).

n


You install a high-availability system with MSCS.End of: HA (MSCS)

n You want to use Single Sign-On.n You use a common transport host for several SAP systems running on different computers.

Local Installation

In a local installation, all Windows account information is stored locally on one host and is notvisible to any other hosts in the system.If the SAP system is to run on a singlemachine (central system), you can perform a local installation.

Note

If your SAP system was installed as a local installation and you want to later change to a domaininstallation, you must perform a homogeneous system copy. For more information, see thedocumentation System Copy for SAP Systems based on SAP NetWeaver <release> <technology> at:http://service.sap.com/instguides <your product>

More Information

n Required User Authorization for Running SAPinst [page 38]n Implementing Single Sign-On with Microsoft Kerberos SSP [page 98]

2.4 How to Distribute Instances to Hosts

The following provides information on how you can distribute the SAP instances for the different SAPsystem variants. You use SAPinst to install the SAP instances as a:

n Central system on a single hostYou run SAPinst and install all instances on one host.

n Distributed system on several hostsYou perform the following steps:1. You specify or create a shared transport directory.2. You run SAPinst and prepare the global host.3. You run SAPinst and install the:

05/25/2009 PUBLIC 25/152

http://service.sap.com/instguides



2 Planning2.5 Distribution of Components to Disks

l Database instance on the database host

l Central instance on the global hostl Dialog instance(s), if required, on the dialog instance host(s)

The following figure shows how to distribute your instances to several hosts:

Figure 2: Distribution of Instances in an ABAP System

2.5 Distribution of Components to Disks

When you install the SAP system, the installation tools prompt you to enter drive letters for the maincomponents of the system. This lets you distribute components to disks in the system as required.How you do this significantly affects system throughput and data security, so you need to plan itcarefully.The best distribution depends on your environment and must reflect factors such as the size of thecomponents involved, security requirements, and the expected workload.When you work out the assignment of components to disks, you first need to get an overview ofthe main components and their corresponding directories. On the basis of sample configurationsand the recommendations provided in this documentation, you can then choose the best setupfor your particular system.In most situations, SAP systems are installed on RAID arrays to guarantee data redundancy.Therefore, this documentation focuses on RAID subsystems and drives.

26/152 PUBLIC 05/25/2009

2 Planning2.5 Distribution of Components to Disks

FeaturesThe following graphic shows how you can distribute the main directories created during theinstallation to Redundant Arrays of Independent Disks (RAID). The distribution is suitable for anaverage-sized production system. Keep in mind that this is only an example and that no singlesolution fits all environments.

Figure 3: RAID Distribution

This configuration is suitable for the main host of a central system or the database server of astandalone database system. You can assign the components on the left to any of the arrays shown.You do not necessarily have to place the transport directory on the central instance host.

Array 1 <DRIVE>:\sapdb\<DBSID>\sapdata\DISKD001

...

<DRIVE>:\sapdb\<DBSID>\sapdata\DISKD999

Array 2 <DRIVE>:\sapdb\<DBSID>\saplog\DISKL001

<DRIVE>:\sapdb\<DBSID>\saplog\M_DISKL001

\usr\sap

<DRIVE>:\sapdb

<DRIVE>:\sapdb\<DBSID>\sapsys

Array 3 <DRIVE>:\sapdb\<DBSID>\saplog\M_DISKL001

<DRIVE>:\sapdb\<DBSID>\saplog\DISKL001

This setup has the following key features:

05/25/2009 PUBLIC 27/152

2 Planning2.6 SAP System Transport Host

n Security of the LogsThe security of the logs is crucial. The logs record all the changes made to the database and soprovide the information that is necessary to recover a damaged database. Therefore, it is importantthat they are stored securely and that you never lose them at the same time as the database data.By placing the redo logs on a different array to the database data, you can make sure that they arenot lost if the array with the database data is severely damaged.

n PerformanceYou can reduce I/O bottlenecks by placing the original logical log on a different array than themirrored log. Original and mirrored logs are written in parallel. If they are located on the samearray, this results in a high level of write activity that has to be handled by the same controller.By separating original and mirrored logs, you can distribute the write activity to two differentarrays, so reducing I/O bottlenecks.

n RAIDBy using RAID 1 arrays for the original and mirrored logs, you get high data security and goodperformance. The data is written to a primary disk and duplicated identically to a second disk. Ifone disk fails, the data is still intact on the second disk.The use of RAID 5 for the database ensures fault tolerance. The data is striped over all the disksin the array together with parity information. If one disk fails, the parity information is used toautomatically reconstruct the data lost on the damaged disk.

n Number of RAID ArraysIn the example above, three RAID 1 arrays are used for the redo logs to ensure optimalperformance and security. If you do not need the disk capacity offered by three arrays and canaccept reduced performance, consider using a single array. In this case, you can use a single RAID 1array for the original and mirrored logs.

2.6 SAP System Transport Host

The transport host contains the transport directory used by the SAP transport system to storetransport data and change SAP system information, such as software programs, data dictionary data,or customization data. If you have several SAP systems, they are usually organized in transportdomains. In most cases, all SAP systems in a transport domain have a common transport directory.When you install an SAP system, you have to decide which transport host and directory you wantto use for your SAP system:

n Use the transport directory that SAPinst creates during the installation of the SAP system bydefault on the global host:SAPinst by default creates the transport directory on the global host in \usr\sap\trans.

n Use a transport directory located on a host other than the default host:l You can use an existing transport directory and host in your SAP system landscape.l You can set up a new transport directory on a different host.

28/152 PUBLIC 05/25/2009

2 Planning2.7 Basic SAP System Parameters

In either case, you must prepare this host for use by the new SAP system [page 40].

More Information

n SAP Directories [page 85]n See the SAP Library:

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) EnglishSAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by KeyCapability Software Life Cycle Management Software Logistics Change and Transport System Change andTransport System ‒ Overview (BC-CTS) Basics of the Change and Transport System Transport ManagementSystem ‒ Concept

2.7 Basic SAP System Parameters

SAPinst prompts for input parameters during the Define Parameters phase of the installation.The tables below list the basic system parameters that you need to specify before installing your SAPsystem. For all other SAP system parameters, use the F1 help in the SAPinst screens.You can install your SAP system either in Typical or Custommode:

n TypicalIf you choose Typical, the installation is performed with default settings. This means that youonly have to respond to a small selection of prompts including at least the following, which aredescribed in the corresponding tables below:l SAP system ID and database IDl Master passwordl SAP system profile directory ‒ only for systems with instances on separate hostsIf you want to change any of the default settings, you can do so on the Parameter Summary screen.

n CustomIf you choose Custom, you are prompted for all parameters. At the end, you can still change any ofthese parameters on the Parameter Summary screen.

Note

If you change a parameter with the Revise button on the Parameter Summary screen, the installer takesyou to the screen where you can change the parameter. Depending on the changes, the installermight guide you through other screens with default parameters that it has so far processed. Thismight also happen if you press Back instead of Next on the screen

The tables below list the basic system parameters that you need to determine before installing yourSAP system. For all other SAP system parameters, use the F1 help in the SAPinst dialogs.

05/25/2009 PUBLIC 29/152

http://help.sap.com/nw70


Java Runtime Environment

Parameters Description

Java Runtime Environment (JRE) A valid JRE is required for the installation with SAPinst. For moreinformation about JRE versions supported by SAP and about how toinstall them, see Installing the Java Runtime Environment [page 41].

SAP System ID and Database ID


SAP System ID <SAPSID> The SAP System ID <SAPSID> identifies the whole SAP system.

CautionChoose your SAP system ID carefully. You cannot change the SAP system IDafter the installation.

Make sure that your SAP system ID:n Is unique throughout your organization. Do not use an existing <SAPSID>

when installing a new SAP system.n Consists of exactly three alphanumeric charactersn Contains only uppercase lettersn Has a letter for the first charactern Does not include any of the following, which are reserved IDs:

ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY

LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID

SQL SYS TMP UID USR VAR

n If you want to install a dialog instance, make sure that no gateway instancewith the same SAP system ID (SAPSID) exists in your SAP system landscape.

Database ID <DBSID> The <DBSID> identifies the database instance. SAPinst prompts you for the<DBSID> when you are installing the database instance.The <DBSID> can be the same as the <SAPSID>.

CautionChoose your database ID carefully. Renaming is difficult and requires youto reinstall the SAP system.

n If you want to install a new database:Make sure that your database ID:l Is unique throughout your organizationl Consists of exactly three alphanumeric charactersl Contains only uppercase lettersl Has a letter for the first characterl Does not include any of the following, which are reserved IDs:

ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT

KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA

SHG SID SQL SYS TMP UID USR VAR

n If you want to use an existing database system:

30/152 PUBLIC 05/25/2009



Enter exactly the database ID of the existing database to which you want toadd the system.

Unicode or Non-Unicode System


Unicode System Every new installation of an SAP system is Unicode.You can only deselect this option if you perform the system copy for anon-Unicode SAP system that has been upgraded to SAP NetWeaver 7.0including Enhancement Package 1.

SAP System Instances, Hosts and Ports


Instance Number of theSAP system

Technical identifier for internal processes. It consists of a two-digit number from00 to 98.The instance number must be unique on a host. That is, if more than one SAPinstance is running on the same host, these instances must be assigned differentnumbers.To find out this number, look under the SAP directory<Drive>:\usr\sap\<SAPSID>\DVEBMGS<nn> on the host of the centralinstance.The value <nn> is the number assigned to the central instance.

CautionDo not use 43, and 89 for the instance number because:

n 43 is used by MSCSn 89 is used by Windows Terminal Server

Name of Instance Host Instance Host:Host name of the specific instance.To find out the host name, open a command prompt and enter hostname.The host name must not exceed 12 characters. For more information about theallowed host name length and characters, see SAP Note 611361.

Virtual Host Name You can use one or more virtual TCP/IP host names for SAP servers within anSAP server landscape to conceal their physical network identities from each other.This may be useful when moving SAP servers or complete server landscapes toother new hardware within a short time frame without having to carry out areinstallation or complicated reconfiguration. You need to specify the virtual hostname before you start SAPinst.For more information, see Prerequisites in Running SAPinst on Windows [page 47].


You also need to specify the virtual host name before you start SAPinst if you wantto install a high-availability (HA) systemEnd of: HA (MSCS)

05/25/2009 PUBLIC 31/152




n For more information about the use of virtual TCP/IP host names, see SAPNote 962955.

n For more information about the allowed host name length and characters,see SAP Note 611361.

Message Server PortCaution

The message server port number must be unique for the SAP system on all hosts.If there are several message port numbers on one host, all must be unique.

Port number of the SAP Message Server:If you do not specify a value, the default port number is used.ABAP Message Server PortThere is an external message server port and an internal message server port.The ABAP message server uses both the internal and the external message serverports. The default profile contains the configuration for both message server ports.The externalmessage server port uses the parameter rdisp/msserv with defaultvalue 36<nn>, where <nn> is the instance number of the ABAP message serverinstance.The internalmessage server port uses the parameter rdisp/msserv_internalwithdefault value 39<nn>, where <nn> is the instance number of the ABAP messageserver instance.For more information about the parameters used for message server ports, seeSAP Note 821875.

Master Password


Master Password Common password for all users created during the installation:n Operating system users (for example <sapsid>adm, SAPService<sapsid>)

CautionIf you did not create the operating system users manually before the installation,SAPinst creates them with the common master password (see table Operating SystemUsers). In this case, make sure that the master password meets the requirements ofyour operating system and of your database.

n ABAP users SAP* and DDIC

CautionSAPinst applies the master password to users SAP*and DDIC for SAP system clients 000and 001 only, but not to users SAP*, DDIC, and EARLYWATCH in SAP system client 066.Instead, SAPinst always assigns the following passwords to these users in client 066:SAP*: 06071992EARLYWATCH: support

32/152 PUBLIC 05/25/2009






See also Ensuring User Security [page 66].

n Database usersn Secure Store key phrase

For more information, see table Key Phrase for Secure Store Settings.

NoteIf a user already exists, you are prompted to confirm the password for this user.

Password policyThe master password:n Must be 8 to 9 characters longn Can contain the following characters: @, _, #, $, a-z, A-Z, 0-9n Must contain at least one letter (a-z, A-Z)n Must contain at least one digit (0-9), but must not begin with a digitn Must not contain \ (backslash) and " (double quote)Depending on the installation option, additional restrictions might apply (for example, themaster password must not contain the name of a Java user created during the installation).

Operating System Users


Password of OperatingSystem Users

SAPinst processes the passwords of operating system users as follows:n If the operating system users donot exist, SAPinst creates the following users:l <sapsid>adm

This user is the SAP system administrator user and is a member of thelocal Administrators group.

l SAPService<SAPSID>

This user is the Windows account to run the SAP system and is not amember of the local Administrators group.

SAPinst sets the master password for these users by default. You canoverwrite and change the passwords either by using the parameter modeCustom or by changing them on the parameter summary screen.

n If the operating system users already exist, SAPinst prompts you for theexisting password, except if the password of these users is the same as themaster password.

CautionMake sure that you have the required user authorization [page 38] for these accounts

05/25/2009 PUBLIC 33/152



before you start the installation with SAPinst.

Solution Manager Key


SAP Solution Manager key To install your SAP system, you need to generate an SAP Solution Manager key [page41], which the installation requires to continue. For more information, seeSAP Note 805390.

Parameters for SAPDATA Drives


Installation drive Base directory for the SAP system. Do not add <SAPSID> assubdirectory because the system adds this directory automatically.

ExampleIf you enter D:, the system adds the directory D:\usr\sap\SAPSID.

NoteIf you install a subsequent SAP system, the saploc share alreadyexists and you cannot select the installation drive. SAPinst uses theinstallation drive where the saploc share points to.

Parameters Relevant for the Database


Database ID Identifier for the database [page 30]

Database schema SAP<SAPSID>

Database file systems n Drive for instance-independent programsn Drive for instance-independent datan Drive for instance-dependent softwaren Drives for SAP data and log volumes

34/152 PUBLIC 05/25/2009


3 Preparation

3 Preparation

Note

In a central system, all mandatory instances are installed on one host. Therefore, if you are installinga central system, you can ignore references to other hosts.

You have to complete the following preparations, which are described in more detail in the linkedsections:

1. If you use Windows Server 2008 you temporarily disable the Windows Server 2008 Firewall [page 35] oneach host.

2. You check the Windows file system [page 36] on each host.3. You check that your installation host belongs to the correct Windows domain [page 37].4. If you use Windows Server 2003, you reduce the size of the file cache [page 37] on each host.5. You check that you have the required user authorization for running SAPinst [page 38].6. If required, you prepare the SAP system transport host [page 40] for your SAP system.7. You install the SAP front-end software [page 41] on the desktop of the end user.8. You generate the SAP Solution Manager Key [page 41] for your SAP system.9. You install the Java Runtime Environment [page 41].10. You make the installation DVDs available [page 42] on each host.11. If required, you download the installation DVDs from SAP Service Marketplace [page 44].

12.


For the installation of a high-availability system with Microsoft Cluster Service (MSCS), inaddition, you have to performMSCS-specific preparation tasks [page 122].End of: HA (MSCS)

3.1 Disabling the Windows Server 2008 Firewall Temporarily

As of Windows Server 2008, the Windows firewall is turned on by default. It is configured to allowonly a small set of Windows-specific inbound IP connections. Outbound connections by default arenot limited to rules and are therefore not restricted by the firewall.The default firewall settings are valid for the out-of-the-box installation of Windows Server 2008 andapply to local policies. For domain policies that override local policies, other rules might apply.To avoid any problems with nonconfigured TCP/IP ports that are used by the SAP system, you need totemporarily disable the firewall before you install the SAP system with SAPinst.

05/25/2009 PUBLIC 35/152

3 Preparation3.2 Checking the Windows File System

Caution

When you have finished the installation with SAPinst, make sure that you turn on the firewallagain and configure it properly [page 64].

Procedure


Note

In a high-availability system, you have to disable the firewall on allMSCS nodes.

End of: HA (MSCS)

1. Choose Start Administrative Tools Windows Firewall with Advanced Security .2. Right-clickWindows Firewall with Advanced Security and choose Properties.3. Choose the relevant profile (in most cases Domain Profile) and set the Firewall state to Off.

Note

To turn on the firewall again, set the Firewall state to On.

3.2 Checking the Windows File System

You need to check that you are using the Windows file system NTFS on hosts where you want toinstall the SAP system and database. NTFS supports full Windows security and long file names.

Note

You must use NTFS for an SAP system installation. Do not install the SAP directories on a FATpartition.

Procedure

1. Open the Windows Explorer.2. Select the relevant disk.3. Choose Properties General .

The system displays the type of file system in use.4. Check that the file system is NTFS.

36/152 PUBLIC 05/25/2009

3 Preparation3.3 Checking the Windows Domain Structure

3.3 Checking the Windows Domain Structure

Note

You do not need this step for a local installation.

In Windows, you can implement either of the following domain models for the SAP system:

n Extra domainIn this model, the SAP system is embedded in its own domain, which is specially defined for SAP. Asecond domain exists for the user accounts.In Windows, the SAP domain and user domain must be incorporated in a domain tree. In this tree,the user accounts must form the root domain and the SAP domain must be a child domain of this.

n Single domainIn this model, the SAP system and the user accounts are included in a single domain.

Prerequisites

n You are performing a domain installation.n You are familiar with checking Windows domain structures. For more information, see the

Windows documentation.

Caution

You cannot create local users and groups on the host that is used as domain controller. Therefore,we do not support running an SAP instance (including the database instance) on the host wherethe domain controller is installed.

ProcedureFor a domain installation, we recommend that you check that all SAP system and database hosts aremembers of a single Windows domain. We recommend this for all SAP system setups.

3.4 Reducing the Size of the File Cache

Note

This step is not required if you use Windows Server 2008.

The Windows file cache directly competes with SAP programs for memory. Therefore, you shouldadjust the file cache as described below.

05/25/2009 PUBLIC 37/152

3 Preparation3.5 Required User Authorization for Running SAPinst


Note

For a high-availability configuration, you must adjust the size of the file cache on all cluster nodes.

End of: HA (MSCS)

Procedure

1. Choose Start Control Panel Network Connections Local Area Connections .2. In the Local Area Connection Status dialog box, choose Properties.3. In the Local Area Connection Properties dialog box, double-click File and Printer Sharing for Microsoft Networks.4. SelectMaximize data throughput for network applications.

Caution

If you cannot select File and Printer Sharing for Microsoft Networks, this option has not yet been installed.To install it, you need the Windows Server CDs.

5. To confirm your entries, choose OK.

3.5 Required User Authorization for Running SAPinst

Although SAPinst automatically grants the required rights to the user account used for theinstallation, you have to check whether this account has the required authorization to perform theinstallation. The authorization required depends on whether you intend to perform a domain orlocal installation. If necessary, you have to ask the system administrator to grant the account thenecessary authorization before you start the installation. If you attempt the installation with anaccount that has not the required authorization, the installation aborts.This section informs you about the authorization required for a domain and a local installation.

Caution

Do not use the user <sapsid>adm for running SAPinst.

Domain InstallationFor a domain installation the account used for the installation needs to be a member of the localAdministrators and the domain Admins group of the domain involved. All machines in the systemmust belong to the same domain. In a domain installation, the user information is stored centrally onthe domain controller and is accessible to all hosts in the system.If the SAP system is to be distributed acrossmore than onemachine, SAP strongly recommends youto perform a domain installation to avoid authorization problems.

38/152 PUBLIC 05/25/2009

3 Preparation3.5 Required User Authorization for Running SAPinst

Caution

n If you install a distributed system as a local installation, this can lead to authorization problems forthe operating system users <sapsid>adm and SAPService<SAPSID>. It can also lead to problemswith the transport directory, which is usually shared by several SAP systems. Therefore, SAPdoes not support a local installation for a distributed system and recommends you to install adistributed system as a domain installation.If you still want to perform a local installation for a distributed system, make sure that:l You use the same password for the <sapsid>adm or the SAPService<SAPSID> user on all hosts.

The password for the <sapsid>adm and SAPService<SAPSID> user can differ.l You use the same master password on all hosts.

l All hosts belong to the same Windows work group.

n


In anMSCS configuration, you always have to perform a domain installation.End of: HA (MSCS)

n For performance and security reasons, SAP does not support an SAP system installation ona domain controller.

n If for any reason, the account used for the installation is not a member of the domain Admins

group, you can perform the installation with a domain user who is a member of the localAdministrators group. However, the domain administrator has to prepare the systemappropriately for you.For more information, see Performing a Domain Installation without being a Domain Administrator [page 89].

For a domain installation, you need to:

1. Check that the account used for the installation is a member of the domain Admins group.2. If required, obtain these rights by asking the system administrator to enter the account as a

member of the domain Admins group.

Local InstallationFor a local installation the account used for the installation needs to be a member of the localAdministrators group of the machine involved. In a local installation, all Windows accountinformation is stored locally on one host and is not visible to any other hosts in the system.If the SAP system is to run on a singlemachine, you can perform a local installation.For a local installation, you need to:

1. Check that the account used for the installation is a member of the local Administrators group.2. If required, obtain these rights by asking the system administrator to enter the account as a

member of the local Administrators group.

05/25/2009 PUBLIC 39/152

3 Preparation3.6 Preparing the SAP System Transport Host

3.6 Preparing the SAP System Transport Host

The transport host has a directory structure that is used by the SAP transport system to storetransport data and metadata.When you install an SAP system, SAPinst by default creates the transport directory on the globalhost in \usr\sap\trans.If you want to use another new transport directory located on a host other than the default host, oran existing transport directory in your SAP system landscape, you need to prepare that transporthost for the new SAP system:

n If the directory structure already exists, you must set up its security to allow the new system towrite to it.

n If it does not yet exist, you must create the core directory structure and a share to export it forother computers as well as set the security on it.

The global transport directory \usr\sap\trans is used by the Change and Transport System (CTS).The CTS helps you to organize development projects in the ABAP Workbench and in Customizing,and then transport the changes between the SAP systems in your system landscape. For moreinformation, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySoftware Life Cycle Management Software Logistics Change and Transport System

Procedure

1. If the transport directory does not yet exist, do the following:a) Create the directory \usr\sap\trans on the host to be used as the transport host.b) Share the usr\sap directory on the transport host as SAPMNT and put the security settings for

Everyone to Full Control for this share.This enables SAPinst to address the transport directory in the standard way as\\SAPTRANSHOST\SAPMNT\trans.

2. Grant Everyone the permission Full Control for the transport directory.

Caution

Remove the Full Control to Everyone permission after you have finished the installation with SAPinstand only grant Full Control on this directory to the SAP_<SAPSID>_GlobalAdmin groups of all thesystems that are part of your transport infrastructure. SAPinst assigns the appropriate rights withthe help of an additional SAP_LocalAdmin group. For more information, see Automatic Creation ofAccounts and Groups [page 101].

40/152 PUBLIC 05/25/2009




3 Preparation3.7 Installing the Front-End Software

3.7 Installing the Front-End Software

For the installation, make sure that the front-end software is installed on at least one computer inyour system environment.With installation software NW SAPSetup for the SAP Front-End, you can optimize the deploymentof SAP GUI to thousands of clients. You can easily tailor installation packages to match yourrequirements, distribute patches, and set up automatic update processes for your clients.We recommend that you install SAP Front-End release 7.10.For more information about installing the front-end software, see the documentation SAP Front EndInstallation Guide - Release 7.10 at:http://service.sap.com/installNW70 Installation Installation - Clients

3.8 Generating the SAP Solution Manager Key

You must generate the Solution Manager key because the installation tool prompts for it during theinstallation. Without this key, the installation process cannot continue. For more informationabout SAP Solution Manager and its role within your system landscape, see the Master Guide ofyour SAP application.

Procedure

1. If SAP Solution Manager is not yet available in your system landscape, proceed as follows:a) Order SAP Solution Manager as described in SAP Note 628901.b) Install SAP Solution Manager as described in the documentation Installation Guide ‒ SAP Solution

Manager <Current Release> on <OS>: <Database>, which is available at:http://service.sap.com/instguides SAP Components SAP Solution Manager <Current

Release>2. Generate the SAP Solution Manager key as described in SAP Note 811923.

ResultThe SAP Solution Manager system displays the key for which you are prompted during theinstallation of your SAP system.

3.9 Installing the Java Runtime Environment

You need to prepare your system for SAPinst. This includes the installation of a Java RuntimeEnvironment (JRE), which is required for SAPinst.

05/25/2009 PUBLIC 41/152









3 Preparation3.10 Preparing the Installation DVDs

Note

If required, you can perform a remote installation using a standalone SAPinst GUI on a separateWindows or UNIX host. This lets you perform the installation on a remote host, controlling it withthe SAPinst GUI from a local host. If you want to perform a remote installation, see Performing aRemote Installation with SAPinst [page 58].

Procedure

1. Check the JRE versions that are released for SAP systems in the Product Availability Matrix (PAM):a) Go to http://service.sap.com/pam.b) On the right-hand panel, choose SAP Application Components <your product> .c) Choose tabstrip JSE Platforms.

Note

For more information about the recommended JRE version for your operating system and abouthow to download it, see SAP Note 723909.

2. Make sure a valid JRE version is installed, as follows:n If the JRE is not already installed, you need to download and install it.n If the JRE is not already installed

Since the JRE is not part of the SAP shipment, you need to download and install it. The JREis part of the JDK (Java Development Kit).

n If the JRE is already installedCheck the installed version of the JRE by entering:java -version

Note

SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment.If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME.

3.10 Preparing the Installation DVDs

This section describes how to prepare the installation DVDs, which are available as follows:

n You obtain the installation DVDs as part of the installation package.n You can also download the installation DVDs from SAP Service Marketplace [page 44].

Procedure

1. Identify the required DVDs for your installation as listed below.

42/152 PUBLIC 05/25/2009





3 Preparation3.10 Preparing the Installation DVDs

Keep them separate from the remaining DVDs as this helps you to avoid mixing up DVDs duringthe installation.

Caution

The media names listed below are abbreviated.You can find the full names in sectionMedia Information in the corresponding Master Guides at:http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP

6.0 SAP enhancement package 4 for SAP ERP 6.0

The following table shows the required DVDs for the installation of an SAP system based onthe usage type AS ABAP:

Note

For a central system, where all mandatory instances reside on one host, you need the installationDVDs that are required for the central instance and database instance.

SAP Instance Installation Required DVDs

Global host preparation n Installation Master DVDn Kernel DVD

Central instance, dialog instance n Installation Master DVDn Kernel DVDn RDBMS DVD

Database instance n Installation Master DVDn Kernel DVDn SAP ERP Installation Export DVDn RDBMS DVD

2. Make the required installation media available on each installation host.

Note

Depending on your installation type, one or more instances can reside on the same host. Youneed to keep this in mind when you make the required installation media available on eachinstallation host.For a central system, you need to make all required installation media available on the singleinstallation host.

Use one of the following methods to make DVDs available:n Before the installation, copy DVDs manually to local hard disks.n During the installation, use the SAPinst Media Browser dialog and copy the entire DVDs to the

path you entered in the Copy Package To column.

05/25/2009 PUBLIC 43/152




3 Preparation3.11 Downloading Installation DVDs from SAP Service Marketplace

Caution

n If you copy the DVDs to disk, make sure that the paths to the destination location of the copiedDVDs do not contain any blanks.

n If you perform a domain installation and do not want to copy the DVDs but use networkdrives for mapping the installation DVDs, make sure that the <sapsid>adm user has access tothe UNC paths of the network drives.

3.11 Downloading Installation DVDs from SAP ServiceMarketplace

You normally obtain the installation DVDs as part of the installation package from SAP.However, you can also download installation DVDs from:http://service.sap.com/swdc Download Installations and Upgrades Entry by Application Group

<SAP solution> <SAP product> <SAP release> Installation and Upgrade <operating system><database>If you download installation DVDs, note that DVDs might be split into several files. In this case, youhave to reassemble the required files after the download.

PrerequisitesTo extract the downloaded SAR files make sure that you use the latest SAPCAR version, which youcan find at http://service.sap.com/swdc. You need at least SAPCAR 700 or SAPCAR 640 withpatch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR files.For more information, see SAP Note 212876.

Procedure

1. Create a download directory on the host on which you want to run SAPinst.2. Identify all download objects that belong to one installation DVD according to one or both of the

following:n Material number

All download objects that are part of an installation DVD have the same material number andan individual sequence number:<material_number>_<sequence_number>

Example

51031387_151031387_2...

44/152 PUBLIC 05/25/2009

http://service.sap.com/swdc







3 Preparation3.11 Downloading Installation DVDs from SAP Service Marketplace

n TitleAll objects that are part of an installation DVD have the same title, such as<solution><DVD_name><OS> or <database>RDBMS<OS> for RDBMS DVDs.

3. Download the objects to the download directory.4. Extract the individual download objects using SAPCAR, starting with the lowest sequence number

‒ for example 51031387_1, then 51031387_2, and so on.During the download SAPCAR sets up the structure of the installation DVD.

Note

SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always acceptwith Yes.

05/25/2009 PUBLIC 45/152

4 Installation

4 Installation

This section provides information about how to perform a standard installation of your SAP system.


Note

If you want to perform aMicrosoft Cluster Service (MSCS) installation, see High Availability withMicrosoft Cluster Service [page 105].

End of: HA (MSCS)

You have to perform the following steps, which are described in more detail in the linked sections:

1. You install the SAP system using SAPinst [page 47].

4.1 Installing an SAP System Using SAPinst

The following sections tell you how to install the various instances of an SAP system, or a standaloneengine:

n Running SAPinst on Windows [page 47]n Using SAPinst GUI [page 55]n How to Avoid Automatic Logoff by SAPinst [page 56]n Interrupted Installation with SAPinst [page 56]n Performing a Remote Installation with SAPinst [page 58]n Starting SAPinst GUI Separately [page 59].n Entries in the Services File Created by SAPinst [page 62]

4.1.1 Running SAPinst on Windows

This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a SAPinst GUIand a GUI server, which both use Java.This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running onthe same host.

05/25/2009 PUBLIC 47/152

4 Installation4.1 Installing an SAP System Using SAPinst

Note

If required, you can instead perform a remote installation with SAPinst [page 58], where SAPinst GUI isrunning on a separate host from SAPinst and the GUI server. Alternatively you can use an X serverfor Microsoft Windows or other remote desktop tools for remote access to SAPinst GUI on Windowsworkstations. For more information, see SAP Note 1170809.

Note the following information about SAPinst:

n When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects to theGUI server with a secure SSL connection, and the GUI server connects to SAPinst.

n SAPinst creates the installation directory sapinst_instdir, where it keeps its log files, and whichis located directly in the Program Files directory. If SAPinst is not able to create sapinst_instdirthere, it tries to create sapinst_instdir in the directory defined by the environment variable TEMP.

Recommendation

We recommend that you keep all installation directories until the system is completely andcorrectly installed.

n SAPinst creates a subdirectory for each installation option called<sapinst_instdir>\<installation_option>, which is located in%ProgramFiles%\sapinst_instdir.

n The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP, TMPDIR, orSystemRoot). These executables are deleted after SAPinst has stopped running.Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory.You can safely delete them.The temporary directory also contains the SAPinst Self-Extractor log file dev_selfex.out, whichmight be useful if an error occurs.

Caution

If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.

n If you want to terminate SAPinst and the SAPinst Self-Extractor, choose one of the followingoptions:l Right-click the icon for the SAPinst output window located in theWindows tray and choose Exit.l Click the icon for the SAPinst output window located in the Windows tray and choose File

Exit .

Prerequisites

n You use an account with the required user authorization to run SAPinst [page 38].

48/152 PUBLIC 05/25/2009



Caution

Do not use the user <sapsid>adm.

n You need at least 200 MB of free space in the installation directory for each installation option. Inaddition, you need 60-200 MB free space for the SAPinst executables.

n If you are installing a second or subsequent SAP system into an existing database, make sure thatthe database is up and running before starting the installation. For more information, seeInstallation of Multiple Components in One Database [page 92].

n Dialog instance only: If your SAP System has been upgraded from an earlier release, and youwant to install a dialog instance, perform the following steps:1. Make sure that the parameter DIR_CT_RUN has identical values in the instance profile and

the start profile of the central instance:l If it is set in the instance profile, it must also be set in the start profile.l If it is not set in the instance profile, it must not be set in the start profile either.

2. Edit the default profile DEFAULT.PFL:Set rdisp/msserv_internal to a free port number.

Example

DEFAULT.PFL

Before:...rdisp/msserv = sapmsSID

...After:...rdisp/msserv = sapmsSID

rdisp/msserv_internal = <free port number>

...

3. Restart all SAP services and instances of your SAP system.

Procedure

1. Insert the SAP Installation Master DVD into your DVD drive or mount it locally.2. Start SAPinst from the SAP Installation Master DVD by double-clicking sapinst.exe from the

following path:<DVD drive>:\IM_WINDOWS_<platform>

SAPinst GUI starts automatically by displaying theWelcome screen.However, if there is only one component to install, SAPinst directly displays the first input dialogwithout presenting theWelcome screen.

05/25/2009 PUBLIC 49/152


Note

n If you want to use a virtual host name, start SAPinst as follows:sapinst.exe SAPINST_USE_HOSTNAME=<virtual host name>

n During the installation, the default ports 21200, 21212, and 4239 are used for communicationbetween SAPinst, GUI server, SAPinst GUI, and HTTP server, as follows:l SAPinst uses port 21200 to communicate with the GUI server.

l The GUI server uses port 21212 to communicate with SAPinst GUI.

l 4239 is the port of the HTTP server, which is part of the GUI server.You see an error message if one of these ports is already in use by another service. In this case,open a command prompt and change to the required directory as follows:cd <DVD drive>:\IM_WINDOWS_<platform>.Enter the following command in a single line:sapinst.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>

GUISERVER_HTTP_PORT=<free_port_number_http_server>

n To view a list of all available SAPinst properties, go to the directory(%TEMP%\sapinst_exe.xxxxxx.xxxx) after you have started SAPinst, and enterthe following command:sapinst.exe -p

3. In theWelcome screen choose one of the following options:n <SAP Product> SAP Application Server ABAP <Database> <System Variant>

For more information, see the tables below.n Software Life-Cycle Options

For more information, see the tables below.

Note

n Choose the corresponding installation options from the tree structure exactly in the orderthey appear for each system variant.

n If required, to install a dialog instance for a central or distributed system, choose:Software Life-Cycle Options <Database> Application Server Dialog Instance

Installation Options for a Central System

Installation Option Remarks

Central System Installs a complete SAP system including the following instances on one host:n Database instancen Central instanceYou can install a central system in the following parameter modes:n Typical Mode

50/152 PUBLIC 05/25/2009



If you choose Typical, the installation is performed with default settings.As a result, you have to respond to only a small selection of prompts.If you want to change any of the default settings, you can do so on theParameter Summary screen.

n Custom ModeIf you choose Custom, you are prompted for all parameters. At the end, youcan still change any of these parameters on the Parameter Summary screen.

NoteIf you change a parameter with the Revise button on the Parameter Summaryscreen, the installer takes you to the screen where you can change theparameter. Depending on the changes, the installer might guide youthrough other screens containing default parameters that it has alreadyprocessed. This might also happen if you press Back instead of Next on thescreen

NoteYou require at least usage type AS Java or AS ABAP. You can choose theusage types on the screen SAP System > Software Units.

Installation Options for a Distributed System


Global Host Preparation Mandatory step in installing a distributed SAP system withusage types or software units based on AS ABAP.Prepares the SAP global host for your SAP system by doingthe following:n Preparing the file systemn Creating the profilesn Installing the executables

Database Instance Mandatory step in installing a distributed SAP system.Installs a database instance.You must have already completed the Global Host Preparation.

Central Instance Mandatory step in installing a distributed SAP system onseveral hosts.Installs a central instance.

NoteYou require at least usage type AS Java or AS ABAP. You canchoose the usage types or software units on the screen SAPSystem > Software Units.

You must have finished the database instance installation.

05/25/2009 PUBLIC 51/152


Installation Options for a High Availability System


Central Services Instancefor ABAP (ASCS)

Installs a central services instance for ABAP (ASCS) and prepares the SAPglobal host

First MSCS Node Performs the following steps on the first Microsoft Cluster Service (MSCS)node:n Creates the SAP cluster groupn Adds the ASCS instance to the SAP cluster group

MaxDB DatabaseInstallation

Installs a MaxDB database on the first MSCS node

MaxDB DatabaseConfiguration

Configures a MaxDB database on the additional MSCS nodes

Database Instance Installs a database instance

Additional MSCS Node Configures an additional Microsoft Cluster Service (MSCS) node to run theSAP cluster groupYou must have completed the configuration of the first MSCS node and thedatabase instance installation.

Enqueue ReplicationServer

Installs an enqueue replication server, which contains a replica of the locktable (replication server)

Central Instance Installs a central instance

Dialog Instance Installs a dialog instance

Noten You require at least one dialog instance in a high-availability system

configured with MSCS.n You might need to install dialog instances on 32-bit operating systems

if you want to use 32-bit SAP NetWeaver components, such as Adobedocument services. However, first check whether such 32-bit componentscan run on 64-bit operating systems. If so, we recommend running these32-bit components on a 64-bit operating system. If not, you can install anSAP dialog instance on 32-bit operating systems to run these components.For all other SAP instances, you must use 64-bit systems.

n If you want to use LDAP, you must choose the options under LDAPRegistration (see below) after you have installed an application server.

52/152 PUBLIC 05/25/2009


Software Life-Cycle Options


Additional Preparation Options These preparation tasks comprise:n Operating System Users and Groups

Creates all operating system users for your SAP system if they donot yet exist.

Cautionl Perform this SAPinst option before you start the installation of

your SAP system.l Make sure that you have the required user authorization [page 38] for

these accounts before you start the installation.

n Prerequisites CheckChecks your hardware and software requirements before you startthe installation.Otherwise, SAPinst automatically checks the hardware and softwarerequirements during the installation with the Prerequisite Checker. Ifany changes are necessary to the SAP system or operating systemsettings, SAPinst automatically prompts you. For more information,see Running the Prerequisites Checker in Standalone Mode [page 16].

Application Server Choose Application Server <Database> Dialog Instance to install oneor more dialog instance(s) in an already installed SAP system, if required.

Noten You might need to install dialog instances on 32-bit operating

systems if you want to use 32-bit SAP NetWeaver components,such as Adobe document services. However, first check whethersuch 32-bit components can run on 64-bit operating systems. Ifso, we recommend running these 32-bit components on a 64-bitoperating system. If not, you can install an SAP dialog instance on32-bit operating systems to run these components. For all other SAPinstances, you must use 64-bit systems.

n If you want to use LDAP, you must choose the options under LDAPRegistration (see below) after you have installed an application server.

LDAP Registration n Active Directory ConfigurationConfigures the Active Directory so that it can store SAP data.

Notel We recommend you to choose this option before you install the

SAP system or an application server.l You have to configure the directory server only once. Afterwards

all SAP systems that should register in this directory server canuse this setup.

n LDAP SupportSets up LDAP support for an application server instance.

05/25/2009 PUBLIC 53/152



Choose this option once per SAP system and after you have:

a) Performed the option Active Directory Configuration

b) Installed an application server instanceFor more information about LDAP and Active Directory, see Integrationof LDAP Directory Services [page 94].

System Copy Choose this service to perform a system copy.For more information, see the system copy guide, which is available at:http://service.sap.com/instguidesnw70 Installation Installation

‒ SAP NetWeaver Systems

Uninstall Choose this service to uninstall your SAP system, standalone engines, oroptional standalone units.For more information, see Deleting an SAP System [page 103].

4. If SAPinst prompts you to log off from your system, log off and log on again.SAPinst restarts automatically.

5. Follow the instructions in the SAPinst dialogs and enter the required parameters.

Note

For more information about the input parameters, position the cursor in the field of therespective parameter and press F1 .

After you have entered all required input information, SAPinst starts the installation and displaysthe progress of the installation. If the installation was successful, the screen Finished installationsuccessfully is displayed.

6. If you want to install an SAP system with ERP software units Self Services (XSS) and BusinessPackages (Portal Content) (BP ERP) running directly on NetWeaver usage type EP Core (EPC)(without installing usage type EP) proceed as follows:a) On the screen SAP System > Software Units, select from the table Additional NetWeaver Software Units

only NetWeaver usage types AS Java and EP Core (EPC).

Caution

Do not select usage type EP.

b) Continue with the installation.When the installation has successfully completed, SAPinst displays the screen Finished successfully.

7. We recommend that you delete all files in the directory %userprofile%\.sdtgui\.

More InformationTroubleshooting with SAPinst [page 102]

54/152 PUBLIC 05/25/2009

http://service.sap.com/instguidesnw70

http://service.sap.com/instguidesnw70


4.1.2 Using SAPinst GUI

The following table shows the most important functions that are available in SAPinst GUI:

SAPinst GUI Functions

Input Type Label Description

Function key F1 Displays detailed information about each inputparameter

Menu option File Exit Stops the SAPinst GUI, but SAPinst and the GUIserver continue running

NoteIf you need to log off during the installation fromthe host where you control the installation withSAPinst GUI, the installation continues while youare logged off. You can later reconnect to the sameSAPinst installation from the same or another host.For more information, see Starting SAPinst GUISeparately [page 59].

Menu option SAPinst Log Browser Displays the Log Viewer dialogThis dialog enables you to access the following logfiles directly:n Installation log (sapinst_dev.log)n Log files from the SAPinst GUI serverThese log files might help you during troubleshootingwith SAPinst [page 102].

Menu option SAPinst Cancel Cancels the installation with the following options:n Stop

Stops the installation (SAPinst GUI, SAPinst, andthe GUI server) without further changing theinstallation filesYou can restart and continue the installationlater from this point.

n ContinueContinues the installation

Message button Retry Performs the installation step again (if an error hasoccurred)

Message button Stop Stops the installation without further changing theinstallation filesYou can continue the installation later from thispoint.

Message button Continue Continues with the option you chose previously

05/25/2009 PUBLIC 55/152


4.1.3 How to Avoid Automatic Logoff by SAPinst

When you install the SAP system with SAPinst, the SAPinst installation tool checks whether the useraccount used for the installation has the required privileges and authorization.For a domain installation, the account needs to be both a member of the local Administrators groupand the domain Admins group. For a local installation, the account needs to be a member of thelocal group Administrators group.In both cases, the user account must be authorized to do the following:

n Act as part of the operating systemn Adjust memory quotas for a processn Replace a process level token

If the user account does not have these rights assigned, SAPinst assigns them and automaticallylogs the account off to activate them. To avoid SAPinst logging the account off, you can set theserights manually before you start the installation.

ProcedureYou perform the following steps to assign these rights to the user account used for the installation.

Caution

Be aware that domain policies override locally defined policies. This means that if you want to grantdomain administrator rights to a user who belongs to the local Administrators group, make surethat you have also defined domain administrator rights for this user on domain level.

1. Choose Start Settings Control Panel Administrative Tools Local Security Policy .2. In the Local Security Settings window, choose Local Policies User Rights Assignment. .3. Double-click the required right under Policy and choose Add User or Group.4. In the Select Users and Groups window, choose the required user and choose Add.

The selected user appears in the box below.5. Confirm your entry and then repeat the steps for each remaining policy that the user requires

for the installation.6. Log off and log on again to apply the changes.

More InformationRequired User Authorization for Running SAPinst [page 38]

4.1.4 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:

n An error occurred during the Define Parameters or Execute phase:

56/152 PUBLIC 05/25/2009


SAPinst does not abort the installation in error situations. If an error occurs, the installation pausesand a dialog box appears. The dialog box contains a short description of the choices listed in thetable below as well as a path to a log file that contains detailed information about the error.

n You interrupted the installation by choosing Cancel in the SAPinstmenu.

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeatingany of the previous steps.This is possible because SAPinst records the installation progress in thekeydb.xml file.We recommend that you view the entries in the log files, try to solve theproblem, and then choose Retry.If the same or a different error occurs, SAPinst displays the same dialogbox again.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, andthe GUI server.SAPinst records the installation progress in the keydb.xml file. Therefore,you can continue the installation from the point of failure withoutrepeating any of the previous steps (see the procedure below).

Continue SAPinst continues the installation from the current point.

View Log Access installation log files.

ProcedureThis procedure describes the steps to restart an installation, which you stopped by choosing Stop, orto continue an interrupted installation after an error situation.

1. Log on as a user who is a member of the local administrators group.2. Insert the Installation Master DVD in your DVD drive.3. Change to the required directory:

<DVD drive>:\IM_WINDOWS_<platform>

Double-click sapinst.exe.4. From the tree structure in theWelcome screen, select the installation service that you want to

continue and choose Next.

Note

If there is only 1 component to install, theWelcome screen does not appear.

TheWhat Do You Want to Do? screen appears.5. In theWhat Do You Want to Do? screen, decide between the following alternatives and confirm

with OK:

05/25/2009 PUBLIC 57/152


Alternative Behavior

Run a New Option SAPinst does not continue the interrupted installation option.Instead, it moves the content of the old installation directory and allinstallation-specific files to a backup directory. Afterwards, you can nolonger continue the old installation option.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds>.

Examplelog_01_Oct_2008_13_47_56

Continue with the Old Option SAPinst continues the interrupted installation option from the point offailure.

4.1.5 Performing a Remote Installation with SAPinst

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and theGUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is thehost from which you control the installation with SAPinst GUI.Alternatively you can use an X server for Microsoft Windows or other remote desktop tools suchas VNC Viewer or NX Server / NX Client ‒ offered by various vendors or open source ‒ for remoteaccess to SAPinst GUI on Windows workstations. We recommend you use the Hummingbird ExceedX Server, which we use to validate installations with SAPinst. For more information, see SAP Note1170809.You can run SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.

Caution

The behavior of SAPinst has changed compared to previous versions. SAP no longer delivers anyJCE policy archives within the SAP Java Virtual Machine (SAP JVM). You have to download therequired Java Cryptography Extension (JCE) policy zip file from SAP on the remote host. For moreinformation, see SAP Note 1238121.

Prerequisites

n The remote host meets the prerequisites for starting SAPinst as described in Running SAPinst onWindows [page 47].

n Both computers are in the same network and can ping each other.To test this:1. Log on to your remote host and enter the command ping <local host>.2. Log on to the local host and enter the command ping <remote host>.

58/152 PUBLIC 05/25/2009




Procedure

1. Log on to your remote host as a user that is a member of the local administrators group.2. Insert the Installation Master DVD in the DVD drive on your remote host.3. Download the JCE policy zip file from SAP as described in SAP Note 1240081.4. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive

by entering the following command:set JCE_POLICY_ZIP=<policy zip archive>

5. Enter the following commands:cd <DVD drive>:\IM_WINDOWS_<platform>

sapinst.exe -nogui

For more information about SAPinst, see Running SAPinst on Windows [page 47].SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following atthe command prompt:guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation

6. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 59].

4.1.6 Starting SAPinst GUI Separately

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUIseparately in the following cases:

n You have logged off from SAPinst.If you logged off during the installation and you later want to reconnect to the installation while itis still running, you can start SAPinst GUI separately.

n You want to perform a remote installation [page 58].If SAPinst GUI runs on a different host from SAPinst and the GUI server, you have to start SAPinstGUI separately on the local host.

Caution

The behavior of SAPinst has changed compared to previous versions. SAP no longer delivers any JCEpolicy archives within the SAP JVM. You have to download the required JCE policy zip file from SAPon the local host. For more information, see SAP Note 1238121.

Starting SAPinst GUI on Windows

1. Log on as a member of the local administrators group.2. Download the JCE policy zip file from SAP as described in SAP Note 1240081.3. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive

by entering the following command:

05/25/2009 PUBLIC 59/152





set JCE_POLICY_ZIP=<policy zip archive>

4. Insert the SAP Installation Master DVD into your DVD drive.5. Change to the directory of the sapinst executables:

<DVD drive>:\IM_WINDOWS_<platform>

Note

If you want to start SAPinst GUI on a Windows 32-bit operating system, change to the followingdirectory:<Installation_Master_DVD>\IM_WINDOWS_I386

6. Start SAPinst GUI by double-clicking sapinstgui.exeSAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local hostas default.If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and theSAP Installation GUI Connection dialog appears.In this case, enter the name of the host on which SAPinst is running and choose Log on.The first dialog of the installation appears and you can perform the remote installation fromyour local host.

Note

Optionally you can start sapinstgui.exe with the following parameters:n host=<host name>, where <host name> is the host name of the installation host

n port=<nr>, where <nr> is the port number for the connection to the GUI server

n -accessible enables accessibility modeExample:./sapinstgui.exe host=lsi1209 port=3000 -accessible

Starting SAPinst GUI on UNIX

1. Log on as user root.

Caution

Make sure that the root user has not set any environment variables for a different SAP system ordatabase.

2. Download the JCE policy zip file from SAP as described in SAP Note 1240081.3. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive

as follows:

60/152 PUBLIC 05/25/2009



Shell Used Command

Bourne shell (sh) JCE_POLICY_ZIP=<policy zip archive>

export JCE_POLICY_ZIP

C shell (csh) setenv JCE_POLICY_ZIP <policy zip archive>

Korn shell (ksh) export JCE_POLICY_ZIP=<policy zip archive>

4. Mount your Installation Master DVD.

Note

Mount the DVD locally. We do not recommend that you use Network File System (NFS).

5. Change to the directory of the sapinst executables:<mountpoint_of_Installation_Master_DVD>/IM_<OS>

Note

If you want to start SAPinst GUI on a Linux 32‒bit platform, change to the following directory:<mountpoint_of_Installation_Master_DVD>/IM_LINUX_I386

6. Start SAPinst GUI by executing ./sapinstguiSAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local hostas default.If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and theSAP Installation GUI Connection dialog appears.In this case, enter the name of the host on which SAPinst is running and choose Log on.The first dialog of the installation appears and you can perform the remote installation fromyour local host.

Note

Optionally, you can start sapinstgui with the following parameters:n host=<host name>, where <host name> is the host name of the installation host

n port=<nr>, where <nr> is the port number for the connection to the GUI server

n - accessible enables accessibility modeExample:./sapinstgui host=lsi1209 port=3000 -accessible

05/25/2009 PUBLIC 61/152


4.1.7 Entries in the Services File Created by SAPinst

After the installation has finished successfully, SAPinst has created the following entries for portnames in <drive:>\WINDOWS\system32\drivers\etc\services:sapdpXX = 32XX/tcp

sapdpXXs = 47XX/tcp

sapgwXX = 33XX/tcp

sapgwXXs = 48XX/tcp

sapms<SAPSID> = 36NN/tcp (unless you specified another value during the installation)

Note

n XX is the instance number. The ports are created for all instance numbers, regardless of whichinstance number you specified during the installation.NN is the number of the instance in which the message server runs. In a central or distributedsystem, this is the central instance (DVEBMGS<nn>), in a high-availability SAP system with MSCS,this is the ABAP central services instance (ASCS<nn>).For more information about instance numbers, see the table SAP System Instances, Hosts, and Ports inBasic SAP System Parameters [page 31].

n If there is more than 1 entry for the same port number, this is not an error.

62/152 PUBLIC 05/25/2009

5 Post-Installation

5 Post-Installation

Note

In a central system, all mandatory instances are installed on one host. Therefore, if you are installinga central system, you can ignore references to other hosts.

You perform the following post-installation steps, which are described in more detail in the linkedsections:

1. If required, you perform a full system backup [page 75] immediately after the installation has finished.2. If you use Windows Server 2008, you configure the Windows Server 2008 Firewall [page 64].3. You check whether you can log on to the application server [page 65].

Note

In a distributed or high-availability system you check whether you can log on to every instance ofthe SAP system that you installed.

4. You ensure user security [page 66].5. You install the SAP license [page 68].6. You apply the latest kernel and Support Packages [page 69].7. Windows Server 2008 only: If required, you set up symbolic links for application servers [page 70].8. You configure the remote connection to SAP support [page 71].9. You install the SAP Online Documentation [page 71].10. You perform initial ABAP configuration [page 71].11. To connect your SAP system to an existing central system landscape directory (SLD), you configure

the connection to a central System Landscape Directory (SLD) [page 76]12. You implement ERP ABAP Add-On Components [page 76].13. If required, you install SAP MaxDB administration tools [page 76].14. If required, you install Secure Sockets Layer (SSL) for SAP MaxDB [page 78].15. You update the database software to the current release [page 82].16. You perform the client copy [page 82]17. You perform a full installation backup [page 75].

05/25/2009 PUBLIC 63/152

5 Post-Installation5.1 Configuring the Windows Server 2008 Firewall

5.1 Configuring the Windows Server 2008 Firewall

The Windows Server 2008 firewall is configured to allow only a small set of Windows-specific inboundIP connections.For the SAP system to operate, you might have to configure the Windows firewall and define a set ofInbound Rules for the TCP/IP port numbers that are used by your system.For more information about the port numbers used, see the documentation TCP/IP Ports Used bySAP Applications at:http://service.sap.com/security Security in Detail Infrastructure Security

Ports listed with the default value Not active in this document are not configured.


Caution

In a high-availability system, you have to configure the firewall on allMSCS nodes.

End of: HA (MSCS)

PrerequisitesYou have turned on the temporarily disabled firewall [page 35] as follows:

1. Choose Start Administrative Tools Windows Firewall with Advanced Security .2. Right-clickWindows Firewall with Advanced Security and choose Properties.3. Set the Firewall state to On.

ProcedureThis procedure describes how to set Inbound Rules for the ports of an installed ABAP server that wasinstalled with instance number 00.

1. Choose Start Administrative Tools Windows Firewall with Advanced Security .2. Right-click Inbound Rules and choose New Rule.

The New Inbound Rule Wizard starts.3. For Rule Type, select Port and choose Next.4. For Protocol and Ports, select port type TCP or UDP depending on the port type used.

Select Specific local ports, and enter the port numbers for which you want to apply the new rule.Note that the final two digits of the port number correspond to the instance number.

5. Choose Next.6. For Action, select Allow the connection, and choose Next.7. For Profile, keep Domain, Private and Public selected, and choose Next.

For more information, see the link Learn more about profiles on this screen.8. Enter the Name, for example SAP ABAP Server 00, and Description for the new rule.9. Choose Next.

64/152 PUBLIC 05/25/2009

http://service.sap.com/security

5 Post-Installation5.2 Logging On to the Application Server

10. Choose Finish to save the rule.The new inbound rule appears in the Inbound Rules list. To modify the settings, right-click onthe rule and choose Properties.

Note

If you want to use, for example, a different IP scope for port 50013, which is used by the connectionSAP Start Service ‒ SAP Management Console, you can restrict the IP access to a small number ofSAP administrators. Then delete this port from the SAP ABAP Server 00 rule and create a newrule for port 50013 with a more restrictive scope.

5.2 Logging On to the Application Server

You need to check that you can log on to the SAP system with the standard users, given in the tablebelow.

ABAP Users

User User Name Client

SAP* 000, 001, 066SAP system user

DDIC 000, 001

Prerequisites

n The SAP system is up and running.n You have already installed a front end.

Logging On to the ABAP Application Server

1. Start SAP Logon on the host where you have installed the front end as follows:n SAP GUI forWindows:

Choose Start All Programs SAP Front End SAP Logon .n SAP GUI for Java:

Choose Start All Programs SAP Clients SAP GUI for Java<Release> .

Note

You can alternatively enter the command guilogon in the SAP GUI installation directoryto start SAP GUI for Java.

The SAP Logon appears.2. Create a logon entry for the newly installed system in the SAP Logon.

For more information about creating new logon entries, press F1 .

05/25/2009 PUBLIC 65/152

5 Post-Installation5.3 Ensuring User Security

3. When you have created the entry, log on as user SAP* or DDIC.

5.3 Ensuring User Security

You need to ensure the security of the users that SAPinst created during the installation. The tablesbelow at the end of this section list these users:

n Operating system usersn SAP system users

During the installation, SAPinst by default assigned the master password to all users created duringthe installation unless you specified other passwords.If you change user passwords, be aware that SAP system users might exist in multiple SAP systemclients (for example, if a user was copied as part of the client copy). Therefore, you need to change thepasswords in all the relevant SAP system clients.

Caution

SAPinst applied the master password to users SAP* and DDIC only for SAP system clients 000 and 001,but not to users SAP*, DDIC, and EARLYWATCH in client 066.Instead, SAPinst always assigns the following passwords to these users in client 066:SAP*: 06071992EARLYWATCH: supportSee alsoMaster Password in Basic SAP System Parameters [page 29].

Recommendation

User ID and password are encoded only when transported across the network. Therefore, werecommend using encryption at the network layer, either by using the Secure Sockets Layer (SSL)protocol for HTTP connections or Secure Network Communications (SNC) for the SAP protocolsdialog and RFC.For more information, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Security Network and Transport Layer Security

Caution

Make sure that you perform this procedure before the newly installed SAP system goes intoproduction. For security reasons, you also need to copy the installation directory to a separate,secure location ‒ such as a DVD ‒ and then delete the installation directory.

For the users listed below, take the precautions described in the relevant SAP security guide, whichyou can find at http://service.sap.com/securityguide:

66/152 PUBLIC 05/25/2009




http://service.sap.com/securityguide



5 Post-Installation5.3 Ensuring User Security

Operating System UsersAfter the installation, operating system users for SAP system and database are available as listedin the following table:

Operating System and Database Users

User Type User Comment

<sapsid>adm SAP system administrator

sqd<dbsid> SAPMaxDB database administrator

Operating system user

SAPService<SAPSID> User to run the SAP system

SAP<SAPSID> SAP MaxDB database owner

CONTROL SAP MaxDB database manageroperator

SAP MaxDB database users

SUPERDBA SAP MaxDB database systemadministrator

SAP System UsersAfter the installation, ABAP system users are available. The following table shows these users togetherwith recommendations on how you can ensure the security of these users.

ABAP Users

User User Name Comment

SAP* User exists in at least SAP systemclients 000, 001, and 066

CautionThis user has extensiveauthorizations. Make surethat you assign a secure password.

DDIC User exists in at least SAP systemclients 000 and 001

CautionThis user has extensiveauthorizations. Make surethat you assign a secure password.

EARLYWATCH User exists in at least SAP systemclient 066

SAP system user

SAPCPIC User exists in at least SAP systemclients 000 and 001

05/25/2009 PUBLIC 67/152

5 Post-Installation5.4 Installing the SAP License

More InformationFor more information about managing ABAP users, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP

NetWeaver Library Security Identity Management User and Role Administration of AS ABAP

5.4 Installing the SAP License

You must install a permanent SAP license. When you install your SAP system, a temporary licenseis automatically installed. This temporary license allows you to use the system for only 4 weeksfrom the date of installation.

Caution

Before the temporary license expires, you must apply for a permanent license key from SAP.We recommend that you apply for a permanent license key as soon as possible after installing yoursystem.

ProcedureInstall the SAP license as described in the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library Technology Consultant’s Guide Cross-NetWeaver Configurations SAP License Key

More InformationFor more information about SAP license keys, see http://service.sap.com/licensekey.

5.5 High Availability: Setting Up Licenses

Every SAP system needs a central license, which is determined by the environment of the messageserver. Since SAP’s high-availability (HA) solution stipulates 2 or more cluster nodes (host machines)where the message server is enabled to run, you have to order as many license keys [page 68] as youhave cluster nodes.When we receive confirmation from your vendor that you are implementing a switchoverenvironment, we provide the required license keys for your system, 1 key for each machine.SAP has implemented a license mechanism for transparent and easy use with switchover solutionsand clustered environments. Your customer key is calculated on the basis of local information on themessage server host. This is the host machine where the ABAP central services instance (ASCS) runs.There is no license problem when only the database is switched over.

68/152 PUBLIC 05/25/2009







http://service.sap.com/licensekey



5 Post-Installation5.6 Applying the Latest Kernel and Support Packages

PrerequisitesThe SAP system is up and running.

Procedure

1. Make sure that the ABAP central services instance (ASCS) on the primary host, node A, is running.2. To find the hardware ID of the primary host, log on to any application server instance of the

SAP system and call transaction SLICENSE.3. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster

and repeat the previous step.Repeat this for all remaining nodes in the cluster.

4. To obtain the two license keys, enter the hardware IDs for the primary and backup hosts at:http://service.sap.com/licensekey

5. To import the files containing the two licenses, log on to any application server instance of theSAP system and call transaction SLICENSE.

6. Perform a switchover of the ABAP central services instance (ASCS) to another node in the clusterand repeat the previous step.Repeat this for all remaining nodes in the cluster.

ResultThe license is no longer a problem during switchover. This means you do not need to call saplicensein your switchover scripts.

5.6 Applying the Latest Kernel and Support Packages

You use this procedure to apply the latest kernel and Support Packages for your SAP system from SAPService Marketplace.

PrerequisitesMake sure that you read the release notes for your SAP system before you apply Support Packages.The release notes might include information about steps you have to perform after you have appliedthe Support Packages. For more information, see http://service.sap.com/releasenotes.

ProcedureDownload and apply the latest kernel and Support Packages as described in the SAP NetWeaver 7.0 ‒Support Package Stack Guide <current version> at http://service.sap.com/maintenancenw70 .For up-to-date release information on Support Package stacks, see SAP Note 849887.You have to apply at least Support Package Stack (SPS) 1 of SAP enhancement package 4 forSAP ERP 6.0.

05/25/2009 PUBLIC 69/152







http://service.sap.com/maintenancenw70


5 Post-Installation5.7 Creating Symbolic Links on Windows Server 2008 for Application Servers

Note

If the central instance host and the dialog instance host run on different operating systems orplatforms, all application serversmust have the same kernel patch level.

5.7 Creating Symbolic Links on Windows Server 2008 forApplication Servers

With Windows Server 2008 you can create symbolic links for dialog instances to simplify theiradministration.


In a high-availability system, you can additionally create symbolic links for the central instance.End of: HA (MSCS)

Symbolic links for application servers let you access from your local host the SYS directory that islocated on the global host, without having to specify its UNC path. Instead you can browse, forexample, in the Windows explorer on your local host to the SYS directory and its subdirectories onthe global host.

ProcedureTo create symbolic links, perform the following steps:

1. In the Startmenu, right-click on Command Prompt and choose Run as administrator.2. Enter the following command in a single line:

mklink /d <localdisk>:\usr\sap\<SAPSID>\SYS \\<sapglobalhost>\sapmnt\<SAPSID>\SYS

Note

Enter a blank before \\<sapglobalhost>\....

3. If you use a central transport directory, you can also create the following link:mklink /d <localdisk>:\usr\sap\trans \\<trans_dir_host>\sapmnt\trans

Note

The transport directory host <trans_dir_host> and the <sapglobalhost> can be identical.

Caution

The command mklink creates the link without checking whether the link target exists or isaccessible. If the link does not work after you created it, make sure that it exists and check theaccessibility of the UNC path.

70/152 PUBLIC 05/25/2009

5 Post-Installation5.8 Configuring Remote Connection to SAP Support

5.8 Configuring Remote Connection to SAP Support

SAP offers its customers access to support and to a number of remote services such asthe SAP EarlyWatch service or the SAP GoingLive service. Therefore, you have to set up aremote network connection to SAP. For more information, see SAP Service Marketplace athttp://service.sap.com/remoteconnection.

5.9 Installing the SAP Online Documentation

SAP currently provides an HTML-based solution for the online documentation, including theApplication Help, Glossary, Implementation Guide (IMG), and Release Notes. You can display thedocumentation with a Java-compatible Web browser on all front-end platforms supported by SAP.You can always find the up-to-date SAP online documentation at http://help.sap.com.

ProcessInstall the SAP online documentation in your SAP system as described in the README.TXT filecontained in the root directory of the online documentation DVD, delivered as part of the installationpackage.

5.10 Performing Initial ABAP Configuration

When you have installed your SAP ABAP system, you have to perform the following initialconfiguration steps:

n Perform a consistency checkn Configure the transport management systemn Perform basic operationsn Configure system parametersn Configure the number of work processesn Configure kernel parametersn Install languages and performing language transportn Configure the integrated Internet Transaction Server (ITS)n Make your newly installed SAP system known to your SAP Solution Managern Maintain your company address for initial usersn Configure business applications

For more information, see the appropriate sections below.

05/25/2009 PUBLIC 71/152

http://service.sap.com/remoteconnection



http://help.sap.com

5 Post-Installation5.10 Performing Initial ABAP Configuration

PrerequisitesYou have logged on to the ABAP application server as described in Logging On to the Application Server[page 65].

Performing a Consistency CheckWe recommend that you check the consistency of the newly installed SAP ABAP system. Whenlogging on to the system for the first time, you need to trigger a consistency check manually. Thefunction is then called automatically whenever you start the system or an application server.This checks the following:

n Completeness of installationn Version compatibility between the SAP release and the operating system

The initial consistency check determines whether:l The release number in the SAP kernel matches the release number defined in the database

systeml The character set specified in the SAP kernel matches the character set specified in the database

systeml Critical structure definitions that are defined in both the data dictionary and the SAP kernel

are identical. The structures checked by this function include SYST, T100, TSTC, TDCT, andTFDIR.

n Accessibility of the message servern Availability of all work process typesn Information about the enqueue server and the update service

To perform a consistency check, you can either call transaction SICK (SAP initial consistency check)or choose:Tools Administration Administration Installation Check from the menu (?).

For more information, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySystem Management Tools for Monitoring the System Consistency Check

Configuring the Transport Management SystemYou have to perform some steps to be able to use the Transport Management System.

1. Perform post-installation steps for the transport organizer:a) Call transaction SE06.b) Select Standard Installation.c) Choose Perform Post-Installation Actions.

2. Call transaction STMS in the ABAP system to configure the domain controller in the TransportManagement System (TMS).

72/152 PUBLIC 05/25/2009





3.


In a high-availability system with MSCS, configure all systems in the TMS landscape as describedin SAP Note 943334.End of: HA (MSCS)

For more information, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySoftware Life Cycle Management Software Logistics Change and Transport System

Performing Basic Operations

1. Go to the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

SAP NetWeaver Library SAP NetWeaver by Key Capability2. Choose the relevant sections to perform the following operations:

Operation Section in SAP Documentation

Set up operation modes ‒transaction RZ04

Solution Life Cycle Management by Key Capability System ManagementConfiguration Operation Modes

Set up logon groups ‒transaction SMLG

Solution Life Cycle Management by Key Capability System ManagementConfiguration Logon Load Balancing SAP Logon

Set up administrators Solution Life Cycle Management by Key Capability SystemManagement BackgroundProcessing Authorizations for Background Processing

Schedule background jobs Solution Life Cycle Management by Key Capability System ManagementBackground Processing

Install a printer Solution Life Cycle Management by Key Capability System Management SAPPrinting Guide

Configure the system log Tools for Monitoring the System System log Configuring the System Log

Configuring System ParametersFor more information about system profiles, which is where work processes and profile parametersare defined, and how to configure them, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySystem Management Configuration Profiles

Checking the Configured Number of Work ProcessesSAPinst installs ABAP systems with a minimum number of work processes. This is only an initialconfiguration so that you can start working after the installation. It is not detailed enough for a

05/25/2009 PUBLIC 73/152












production system because the optimal number of each type of work process depends on the systemresources and on the number of users working in each ABAP system application.For more information about how many work processes to configure and about how to set thenumber, see SAP Notes 39412 and 9942.

Configuring Kernel ParametersTo configure your kernel parameters, follow the recommendations in SAP Notes 146289 and 835474.

Installing Languages and Performing Language Transports

n Install languages using transaction I18N:l If you want to use English only, you must activate the default language settings once.l If you want to use languages other than English, you must install them and activate the

language settings.For more information about configuring the language settings, see the online documentation intransaction I18N at I18N Menue I18N Customizing .

n Perform language transport using transaction SMLT as described in the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by KeyCapability Software Life Cycle Management Software Logistics Change and Transport System LanguageTransport

Using and Configuring the SAP ITS Integrated ICMThe SAP Internet Transaction Server (SAP ITS) is integrated in the SAP NetWeaver Application ServerABAP (AS ABAP) as an Internet Communication Framework (ICF) service. You can access this, likeother services, with the Internet Communication Manager (ICM). With the SAP ITS integrated inAS ABAP, the Web browser now communicates directly with the SAP system. Furthermore, allSAP ITS-related sources, such as service files, HTML templates, or MIME files, are now stored inthe database of the system.The SAP ITS supports the following functions:

n SAP GUI for HTML

n Internet Application Component (IAC) runtime or Web Transaction technology

For more information about how to configure the integrated SAP ITS, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAPTechnology UI Technology Web UI Technology SAP ITS in the SAP NetWeaver Application ServerConfiguration

74/152 PUBLIC 05/25/2009











5 Post-Installation5.11 Performing a Full System Backup

Making your Newly Installed SAP System Known to your SAP SolutionManagerMake your newly installed SAP system known to your SAP Solution Manager as described in theSAP Library at:http://help.sap.com SAP Solution Manager SAP Solution Manager 7.0 <current SP> SAP Solution

Manager Basic Settings Solution Manager System Landscape Create Systems

Maintaining Your Company Address for Initial UsersMaintain your company address in your ABAP system using transaction SU01 as described in theSAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability BusinessServices Business Address Services (BC-SRV-ADR) Addresses in User Administration Maintenance of AddressData

Note

You must maintain your company address to create ABAP system users.

Configuring Business ApplicationsPrepare the SAP system for using business applications, which includes customizing the ABAP systemand the business components, as described in the SAP Library at http://help.sap.com/nw70 SAPNetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver byKey Capability Solution Life Cycle Management by Key Capability Customizing

5.11 Performing a Full System Backup

You must perform a full system backup after the configuration of your SAP system. If required,you can also perform a full system backup after the installation (recommended). In addition, werecommend you to regularly back up your database.

Prerequisites

n You are logged on as user <sapsid>adm.n You have shut down the SAP system and database.

ProcedureBack up your system including the operating system disk, system state, and all other disks.

05/25/2009 PUBLIC 75/152

http://help.sap.com







5 Post-Installation5.12 Configuring the Connection to a Central System Landscape Directory

5.12 Configuring the Connection to a Central SystemLandscape Directory

For each system in your landscape that reports data to a central System Landscape Directory (SLD),you have to configure a corresponding SLD data supplier.

ProcedureConfigure the SLD data suppliers and the API for the SLD as described in the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySoftware Life Cycle Management System Landscape Directory Configuring Systems to Connect to SLD

More InformationThis documentation is also available in PDF form in the User Manual ‒ SLD of SAP NetWeaver 7.0 athttp://www.sdn.sap.com/irj/sdn/nw-sld.

5.13 Implementing ERP ABAP Add-On Components

You can install several Add-On Components to your ERP ABAP system.

ProcedureYou can find a detailed description on how to implement each available ERP Add-On Component inthe related SAP Notes on SAP Service Marketplace at https://service.sap.com/erp-inst SAPERP 6.0 SAP Notes .

5.14 Installing or Upgrading Database Studio for SAP MaxDB

This section describes how to install or upgrade Database Studio for SAP MaxDB and SAP liveCacheon Windows front ends. Database Studio is the database administration tool for SAP MaxDB.For more information about Database Studio, see:http://www.sdn.sap.com/irj/sdn/maxdb SAP MaxDB Knowledge Center The Complete SAP MaxDB

Documentation Set SAP MaxDB 7.7 Library Glossary Database Studio

Note

Database Studio replaces Database Manager GUI and SQL Studio, which were available in previousreleases.

76/152 PUBLIC 05/25/2009




http://www.sdn.sap.com/irj/sdn/nw-sld

https://service.sap.com/erp-inst



http://www.sdn.sap.com/irj/sdn/maxdb

5 Post-Installation5.14 Installing or Upgrading Database Studio for SAP MaxDB

Prerequisites

n You can install Database Studio on Linux or Windows in your network, even if your database runson a different operating system. You can then remotely administer the database on a different host.The instructions below refer mainly to the Windows version.

Note

To run Database Studio on Linux, you need to meet the requirements for the MaxDB databaseserver.

n Your PC must meet the followingminimum requirements:l Software requirements:

Operating System Requirements for Database Studio

Operating System Version

Windows XP Professional Service Pack 2

Windows 2003 Server Service Pack 1

l Hardware requirements (currently only 32-bit platforms are supported):

uRAM: 512 MB ( recommended RAM: 1 GB)

uProcessor speed: 1.5 GHz

uFree disk space: 200 MB

uMonitor: 1024x768 pixels, 256 colorsn You can get the required files from one of the following:l The DVD for MaxDB RDBMS or SAP liveCache

l By downloading from:http://service.sap.com/patches Entry by Application Group Additional Components

MaxDB MaxDB GUI COMPONENTS/TOOLS MAXDB DATABASE STUDIO 7.7

n You need Java Runtime Environment (JRE) version 5 (also known as 1.5) or higher.To check your Java version, enter the following command:java -version

To download Java, go to http://java.com/en/download.n To uninstall the database manager GUI, which is the tool replaced by Database Studio, choose

Start Settings Control Panel - Add/Remove Programs .

Procedure

1. Start the installation or upgrade as follows:n If you are using theMaxDB RDBMS DVD:

<DVD>:\MAXDB_WINDOWS_I386\SDBSETUP.EXE

n If you are using the liveCache DVD:

05/25/2009 PUBLIC 77/152

http://service.sap.com/patches

http://java.com/en/download

5 Post-Installation5.15 Secure Sockets Layer Protocol for Database Server Communication

<DVD>:\LC_WINDOWS_I386\SDBSETUP.EXE

n If you are using the downloaded files, simply execute the downloaded SDBSETUP.EXE file.The Installation Manager starts.

2. Choose Start Installation/Upgrade and then Custom.You see a list of the components to be installed.

3. Deselect all components except Database Studio.4. Choose Install.

The installation manager installs Database Studio.5. If you are prompted to restart your computer after the installation, make sure that you first shut

down any databases that are running.

More InformationFor more information about Database Studio, including troubleshooting, see SAP Note 1097311.

5.15 Secure Sockets Layer Protocol for Database ServerCommunication

The SAP MaxDB database server supports the Secure Sockets Layer (SSL) protocol. You can use thisprotocol to communicate between the database server and its client, here the Application Server(AS). SSL guarantees encrypted data transfer between the SAP MaxDB database server and its clientapplications. In addition, the server authenticates itself to the client.

Caution

There is a performance cost for SSL since the data has to be encrypted, which requires time andprocessing power.

To use SSL you need to:

1. Install the SAP cryptographic library [page 78] on the client host and on the server host machines2. Generate the Personal Security Environment [page 80] (PSE) on the server (SSL Server PSE) and on the

client (SSL Client PSE).

5.15.1 Installing the SAP Cryptographic Library

The SAP Cryptographic Library supplies the cryptographic functions required to build a databaseserver-client connection using Secure Sockets Layer (SSL) protocol. Therefore, you need to installthe SAP Cryptographic Library on the host machine of the SAP MaxDB database server and theSAP Application Server (AS).The installation package sapcrypto.car consists of the following:

78/152 PUBLIC 05/25/2009



n SAP Cryptographic Library: sapcrypto.dlln License ticket: ticket

n Configuration tool: sapgenpse.exeYou use the configuration tool to generate key pairs and PSEs.

Caution

The SAP Cryptographic Library is subject to German export regulations and might not be availableto some customers. In addition, the library might be subject to the local regulations of your country.These regulations might further restrict import, use, and export or re-export of cryptographicsoftware.For more information, contact your local SAP representative.

PrerequisitesDownload the appropriate SAP Cryptographic Library installation package for your operating systemfrom http://service.sap.com/swdc.

Procedure

1. Unpack the installation package for the SAP Cryptographic Library using sapcar.exe, which youcan find for example on your Installation Master DVD, using the following command:car -xvf SAPCRYPTO.CAR

Note

The remainder of the procedure (as described below) does not apply to client applications such asSQL Studio, which do not recognize an “independent” directory. In this case, you must copy theSAPCRYPTO installation package to the installation directory of the application. In this directoryyou need to create a directory sec, into which you copy the ticket file.

2. Copy the sapcrypto library to the lib subdirectory of the “independent program” directory.You can find the value of the independent program directory by entering the following command:dbmcli dbm_getpath IndepProgPath

Example

The independent program directory might be called the following:<drive>:\sapdb\programs\lib

3. Copy the configuration tool sapgenpse.exe to the directory <independent program>\lib.4. Create a subdirectory called sec under the “independent data” directory and copy the ticket

file into it.

05/25/2009 PUBLIC 79/152





Example

The result might look like the following:<drive>:\sapdb\data\sec\ticket

5. Make sure that only the local system account is allowed to possess access rights to the secdirectory and the files it contains ‒ including the ticket file and the SSL Server PSE ‒ and thataccess is restricted to read&write. Only members of the administrator group can own the files.

ResultThe system copies the SAP Cryptographic Library is copied to the application server and configuresthe environment correctly so that the server can find the library at runtime.

5.15.2 Generating the Personal Security Environment

The information required by the database server or client application to communicate using SecureSockets Layer are stored in the Personal Security Environment (PSE). The required information differsaccording to whether SSL PSE is for the server or client:

n SSL Server PSEThis PSE contains the security information from the database server, for example, thepublic-private cryptographic key pair and certificate chain. To install the SSL Server PSE, youneed to generate the PSE. You can either do this for a single database server or system-wide. TheSSL Server PSE is called SDBSSLS.exe.

n SSL Client PSEThe client requires an anonymous certificate called SDBSSLA.exe, which contains the list of thepublic keys of trustworthy database servers.

ProcedureTo generate the SSL Server PSE, proceed as follows:

Note

You need to know the naming convention for the distinguished name of the database server.The syntax of the distinguished name, which you enter in the procedure below, depends on theCertification Authority (CA) that you are using.

1. Change to the <independent programs>\lib directory.2. Set up the following environment variable:

SECUDIR=<independent data>\sec

3. Create a SSL Server PSE, SDBSSLS.pse, and generate a certificate request file, certreq, in thedirectory defined by SECUDIR (see previous step):

80/152 PUBLIC 05/25/2009


sapgenpse gen_pse -v -r <SECUDIR>\certreq -p SDBSSLS.pse “<your distinguished

name>”

For each database server that uses a server-specific PSE, you must set up a unique certificaterequest. If you are using a valid system-wide SSL Server PSE, you only need to set up a singlecertificate request for all servers.

4. Send the certificate request to the CA for signing. You can either send it to the SAP CA or toanother CA.You must make sure that the CA offers a certificate corresponding to the PKCS#7 certificate chainformat. Thawte CA at http://www.thawte.com offers a suitable certificate, either SSL ChainedCA Cert or PKCS#7 certificate chain format.The CA validates the information contained in the certificate request, according to its ownguidelines, and sends a reply containing the public key certificate.

5. After you have received the reply from the CA, make sure that the contents of the certificaterequest have not been destroyed during download.For example, if you requested the certificate on a UNIX system and stored it on a Windows frontend, the formatting (that is, line indents and line breaks) is affected.To check the contents, open the certificate request with a text editor (such as Notepad) and repairthe line indents and the line breaks.

Example

This is an example of a certificate request:-----BEGIN CERTIFICATE

REQUEST-----MIIBPzCBqQIBADAAMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD/302IT+/Y

wpignSw7U9FWneyWz3Wil0S18aFCYkRo00wCpD8UwcaC4dds4uGT6hl2WlJ0/FOtUg+EQxonZbaRrk9sTalkn1mqx3YAUe/gEaGdf1wvuYkb0gjMk81iM/jb9BJd8srMPyoBy9jMC7v5u7+TZWmWa6RjnvClvYGgMwIDAQABoAAwDQYJKoZIhvcNAQEFBQADgYEAx2zuaTAOKPdGmxUKYlWdasUpim4vhfaHa7ZDBwipvKJ8akYCT+dpmVjhcph9E7cUjL80/6Rup5cnLAAO5FhVt5MS6zNJa9YYSN9XP+5/MPF6Q4ayJ0VryTkSpbbPrWLbKh1Dds97LQVuQ/myKIAHECwyW6t7sAFJWn4P0fdxmKo=

-----END CERTIFICATE REQUEST-----

6. Import the reply to the SSL Server PSE:a) Copy the text to a temporary file called srcert.b) Enter the following command:

sapgenpse import_own_cert -c srcert -p SDBSSLS.pse

You have generated the SSL Server PSE. You can now start the XServer as usual (if it is alreadyrunning, you must stop and restart it).

7. To check whether the SSL functionality is working correctly, view the trace file niserver_<localcomputer name>.trace in the <independent data>\wrk directory.

To generate the SSL Client PSE, proceed as follows:

1. Change to the <independent programs>\lib directory.2. Set up the following environment variable:

SECUDIR=<independent data>\sec

3. Create an anonymous client SSL Client PSE, SDBSSLA.pse in the directory defined by SECUDIR (seeprevious step):

05/25/2009 PUBLIC 81/152

http://www.thawte.com

5 Post-Installation5.16 Updating the Database Software to the Current Release

sapgenpse gen_pse -v -noreq -p SDBSSLA.pse

You can leave the distinguished name empty.Before you can establish an SSL connection to a database server, the server certificate must beentered in the PK list of the anonymous client certificate.

4. To see the database server certificate, enter the following command:„x_ping -n <servermode> -c[apture]

You can check whether to trust the database server certificate. The client certificate is not affectedby this.

5. Start the import with this command:„x_ping -n <servermode> -i[import]

6. To administer the PSE, use the configuration tool sapgenpse. For more information, enter thefollowing command:sapgenpse -h

Note

For applications such as SQL Studio replace the independent data or independent program in theabove description with the installation directory.

5.16 Updating the Database Software to the Current Release

After the installation and before you start production operation, we strongly recommend you toupdate the database software.

Procedure

1. Download the latest SAP MaxDB patches as follows:http://service.sap.com/swdc Download Database Patches MaxDB

For more information about upgrading to a MaxDB Support Package, see SAP Note 735598.

5.17 Performing the Client Copy

SAPinst creates three ABAP clients during the installation, client 000, client 001, and client 066.Client 000 is the SAP reference client for ABAP.Use client 000 as source client for the client copy.

Procedure

1. Maintain the new client with transaction SCC4.2. Activate kernel user SAP*:

82/152 PUBLIC 05/25/2009





5 Post-Installation5.18 Accessing Configuration Documentation in SAP Solution Manager

a) Set the profile parameter login/no_automatic_user_sapstar to 0.b) Restart the application server.

3. Log on to the new client with kernel user SAP* and password PASS.4. Copy the client with transaction SCCL and profile SAP_CUST.5. Check the log files with transaction SCC3.6. Create the required users. These users must have at least the authorizations required for user

administration and system administration. Create a user SAP* with all required authorizationsfor this user. If you want to have other users for system administration, you can also create userSAP* without authorizations.

7. Deactivate kernel user SAP*:a) Reset login/no_automatic_user_sapstar to 1.b) Restart the application server.

More InformationFor more information about the client copy and about how to perform it, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySoftware Lifecycle Management Software Logistics Change and Transport System BC ‒ Client Copy and Transport

5.18 Accessing Configuration Documentation in SAP SolutionManager

To access configuration documentation in SAP Solution Manager, you have to connect yournewly-installed SAP system to SAP Solution Manager.

Note

For SAP NetWeaver 7.0 usage types you can also find configuration documentation in the TechnologyConsultant’s Guide at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library Technology Consultant’s Guide

Prerequisites

n You have installed an SAP Solution Manager system as described in the documentation InstallationGuide ‒ SAP Solution Manager 7.0 on <OS>: <Database>.

n You have connected your SAP system to SAP Solution Manager as described in the documentationConfiguration Guide ‒ SAP Solution Manager <Current Release> as of <Current SP Level>.

You can find this documentation at:http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0

05/25/2009 PUBLIC 83/152










5 Post-Installation5.18 Accessing Configuration Documentation in SAP Solution Manager

Procedure

1. Log on to your SAP Solution Manager system.2. To be able to access configuration documentation, create a project as follows:

a) Create your project with transaction SOLAR_PROJECT_ADMIN for project administration.b) Connect your SAP system to SAP Solution Manager with transaction SMSY for the SAP Solution

Manager system landscape.c) Create a project structure and add the required scenarios for your SAP system to your project

structure with the Business Blueprint transaction SOLAR01,d) Add your SAP system configuration structures to your project structure with the configuration

transaction SOLAR02.For more information about creating projects, assigning scenarios to projects, and creatingconfiguration structures, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by KeyCapability SAP Solution Manager Using the SAP Solution Manager in Projects

3. Go to the project structure folder <project name> using transaction SOLAR02.4. Access configuration documentation for SAP NetWeaver usage types at Configuration Structure

SAP NetWeaver 7.0 .5. Access configuration documentation for all areas of SAP ERP at Configuration Structure SAP

ERP <release> .Here you can also find documentation about how to use the Extended ConfigurationManagement(XCM) Administration Tool.

ResultYou can now configure your SAP system according to the configuration documentation in SAPSolution Manager.

84/152 PUBLIC 05/25/2009




6 Additional Information

6 Additional Information

The following sections provide additional information about optional preparation, installationand post-installation tasks.There is also a section describing how to delete an SAP system.

Planning

SAP Directories [page 85].

Preparation

n Performing a Domain Installation Without Being a Domain Administrator [page 89].n Installation of Multiple Components in One Database [page 92]n Integration of LDAP Directory Services [page 94]

Post-Installation

n Starting and stopping the SAP system [page 97].n You implement Single Sign-On with Microsoft Kerberos SSP [page 98].n SAP System Security on Windows [page 99]n Automatic Creation of Accounts and Groups [page 101]n Troubleshooting [page 102]

Deleting an SAP System or SAP Instance

n Deleting an SAP System [page 103]

6.1 SAP Directories

This section describes the directories that are available in an SAP system.


If you want to install an MSCS system, see also Directories in an MSCS Configuration [page 115].End of: HA (MSCS)

SAPinst automatically creates the following directories during the installation:

n \usr\sap

This directory is created on the:l Global host and shared with the network share sapmnt

05/25/2009 PUBLIC 85/152

6 Additional Information6.1 SAP Directories

Only valid for: non-HA

The global host is the host where the central instance is installed.End of: non-HA


The global host is the host where the ASCS instance is installed.End of: HA (MSCS)

On global hosts, the \usr\sap directory contains general SAP software, global and local(instance-specific) data. For this, SAPinst creates the global directory usr\sap\<SAPSID>\SYS,which physically exists only once for each SAP system. It consists of the following subdirectories:

uglobal ‒ contains globally shared data

uprofile ‒ contains the profiles for all instances

uexe ‒ contains executable replication directory for all instances and platformsl Local host and shared with the name saploc.

On local hosts, the \usr\sap\<SAPSID>\<instance_name> directory contains copies of the SAPsoftware and local (instance-specific) data.

Note

Since SAP traces for the instance are created in \usr\sap, make sure there is sufficient spaceavailable in this directory. Changes in SAP profiles can also affect the disk space.

Note

The executables on the local host are replicated from those on the global host every timethe local instance is started. The SAP copy program sapcpe compares the binaries in the<platform> directory on the global host and the binaries in the exe directory on theapplication server. If the binaries in the exe directory are elder than those in the <platform>directory, sapcpe replaces them with the newer version of the global host.

Other application servers access the global data using the Universal Naming Convention (UNC)path \\<SAPGLOBALHOST>\sapmnt. The SAP programs access their instance-specific data with theUNC path \\<SAPLOCALHOST>\saploc. If the UNC path points to a local directory, the local path(and not the UNC path) is used to access the directory.The parameters SAPGLOBALHOST and SAPLOCALHOST have the same values on the global host.

86/152 PUBLIC 05/25/2009



Note

Windows Server 2008 only:In a high-availability system, file shares pointing to directories on shared disks are only visible oraccessible with the virtual host name of the cluster group the shared disks belong to.

End of: HA (MSCS)

n \usr\sap\trans

The transport directory contains SAP software for the transport of objects between SAP systems.SAPinst by default creates it on the SAPGLOBALHOST.If you want to have it created on another host or if you want to use an existing transport host fromyour SAP system landscape, you can specify another host during the installation. In this case, youhave to prepare that host for the new SAP system to use it. For more information, see Preparingthe SAP System Transport Host [page 40].

Directory Structure

The following figures show how the physical directory \usr\sap is shared on the global host in acentral and in a distributed system. In both cases, the UNC paths are used as follows:

n \\<SAPGLOBALHOST>\sapmnt to access global directoriesn \\<SAPLOCALHOST>\saploc to access local instance-specific data

Note

There are the following instance names available in an SAP system:


Central services instance for ABAP: ASCS<Instance_Number>.End of: HA (MSCS)

Central instance: DVEBMGS<Instance_Number>Dialog instance: D<Instance_Number>.


Enqueue Replication Server instance: ERS<Instance_Number>End of: HA (MSCS)

Note

Every new installation of an SAP system is Unicode.

05/25/2009 PUBLIC 87/152


Figure 4: Directory Structure on the Global Host in a Central ABAP System

Figure 5: Directory Structure in a Distributed ABAP System

88/152 PUBLIC 05/25/2009

6 Additional Information6.2 Performing a Domain Installation Without Being a Domain Administrator

Only valid for: HA (MSCS);HA (z/OS)

Figure 6: Directory Structure in a High-Availability ABAP System

End of: HA (MSCS);HA (z/OS)

6.2 Performing a Domain Installation Without Being a DomainAdministrator

You normally perform a domain installation of the SAP system with a user who is a member of thedomain Admins group, as described in Required User Authorization for Running SAPinst [page 38]. If for anyreason, the account used for the installation is not a member of the domain Admins group, you canperform the installation with a domain user who is a member of the local Administrators group. Inthis case, the domain administrator has to prepare the system appropriately for you. The domainadministrator can perform the following steps either using SAPinst or manually:

1. Create the new global group SAP_<SAPSID>_GlobalAdmin.2. Create the two new SAP system users <sapsid>adm and SAPService<SAPSID>.3. Add the users <sapsid>adm and SAPService<SAPSID> to the newly created group

SAP_<SAPSID>_GlobalAdmin.

Prerequisites

n You must be domain administrator to perform the required steps.

05/25/2009 PUBLIC 89/152


n Windows Server 2008 only:You must have installed the feature Remote Server Administration Tools as follows:1. Choose Start Administrative Tools Server Manager .2. In the Server Manager windows, select Features.3. Select the feature Remote Server Administration Tools Role Administration Tools Active Directory

Domain Services Tools .

Creating the Required Uses and Groups Using SAPinstOn the host where the SAP system is to be installed, the domain administrator runs SAPinst [page 47]and chooses Software Life-Cycle Options Additional Preparation Options Operating System and Users tohave the group and users created automatically.

Creating the Required Uses and Groups Manually

Creating the New Global Group SAP_<SAPSID>_GlobalAdmin

1. Log on as domain administrator.2. To start the Active Directory Users and Computers Console, choose:

Start Control Panel Administrative Tools Active Directory Users and Computers

Note

Windows Server 2003 only: If you cannot find Active Directory Users and Computers, start it as follows:a) Choose Start Run and enter mmc.b) Choose Console Add/Remove Snap-in... Add .c) Select Active Directory Users and Computers.d) Choose Add .e) Choose Close OK

3. Right-click Users in Tree, and choose New Group .4. Enter the following:

Group name: SAP_<SAPSID>_GlobalAdmin

Note

Enter the SAP_<SAPSID>_GlobalAdmin group exactly as specified in the correct uppercase andlowercase.

5. Select the following:a) Group scope: Globalb) Group type: Security

6. Choose OK.

90/152 PUBLIC 05/25/2009


Creating the New SAP System Users <sapsid>adm and SAPService<SAPSID>

1. In Active Directory Users and Computers Console, right-click Users in Tree and choose:New User

2. Enter the following:

Note

Enter the <sapsid>adm and SAPService<SAPSID> user exactly as specified in the correctuppercase and lowercase.

Field Input for <sapsid>adm Input for SAPService<SAPSID>

First name: None None

Initials: None None

Last name: None None

Full name: <sapsid>adm SAPService<SAPSID>

User logon name: <sapsid>adm SAPService<SAPSID>

Full name: <sapsid>adm SAPSE<SAPSID>

User logon name: <sapsid>adm SAPSE<SAPSID>

3. Choose Next and enter the following:Password: <password>Confirm password: <password>

4. Select Password never expires

Note

Make sure that no other options are selected.

5. Choose Next Finish .

Adding the <sapsid>adm User to the SAP_<SAPSID>_GlobalAdmin Group

1. In theUsers folder, double-click the newly created user account <sapsid>adm in the list on the right.2. Choose Member Add .3. Select the new SAP_<SAPSID>_GlobalAdmin group and choose Add to add it to the list.

Note

By default, the user is also a member of the Domain Users group.

4. Choose OK twice.

05/25/2009 PUBLIC 91/152

6 Additional Information6.3 Installation of Multiple Components in One Database

Adding the SAPService<SAPSID> User to the SAP_<SAPSID>_GlobalAdmin Group

1. In the Users folder, double-click the newly created user account SAPService<SAPSID> in the list onthe right.

2. Choose Member Add .3. Select the new SAP_<SAPSID>_GlobalAdmin group.4. Choose Add to add it to the list, and then OK.5. Choose OK to close SAPService<SAPSID> Properties.6. Close the Active Directory Users and Computers Management Console.

6.3 Installation of Multiple Components in One Database

You can installmultiple SAP systems in a single database. This is called Multiple Componentsin One Database (MCOD).

Example

You install an SAP ERP central system and an SAP CRM central system in a single database.

MCOD is available with all SAP components. We are releasing this technology on all the majordatabases for the SAP system, in line with our commitment to deliver platform-independentsolutions.Using this technology is as easy as installing a separate component. No extra effort is required becausethe MCOD installation is fully integrated into the standard installation procedure. MCOD is not anadditional installation service. Instead, it is an option of the database instance installation.With MCOD we distinguish two scenarios:

n The installation of an SAP system in a new databasen The installation of an additional SAP system in an existing database

Prerequisites

n For more information about MCOD and its availability on different platforms, seehttp://service.sap.com/mcod.

n We have released MCOD for Unicode installations. A prerequisite is that the MCOD systemcontains Unicode instances only. SAP does not support mixed solutions.

n Improved sizing requiredIn general, you calculate the CPU usage for an MCOD database by adding up the CPU usage foreach individual SAP system. You can do the same for memory resources and disk space.You can size multiple components in one database by sizing each individual component using theQuick Sizer tool and then adding the requirements together. For more information about theQuick Sizer, see http://service.sap.com/sizing.

92/152 PUBLIC 05/25/2009

http://service.sap.com/mcod






6 Additional Information6.3 Installation of Multiple Components in One Database

Features

n Reduced administration effort

n Consistent system landscape for backup, system copy, administration, and recoveryn Increased security and reduced database failure for multiple SAP systems due to monitoring and

administration of only one databasen Independent upgrade

In an MCOD landscape, you can upgrade a single component independently from the othercomponents running in the same database, assuming that the upgraded component runs onthe same database version. However, if you need to restore a backup, be aware that all othercomponents are also affected.

Note

Special MCOD considerations and differences from the standard procedure are listed where relevantin the installation documentation.

Constraints

Recommendation

We strongly recommend that you test MCOD in a test or development system.We recommend that you run MCOD systems in the same context. We do not recommend that youmix test, development, and production systems in the same MCOD.

n In the event of database failure, all SAP systems running on the single database are affected.n Automated support in an MCOD landscape for the following administrative tasks depends on

your operating system and database:l Copying a single component from an MCOD landscape to another database at database level.l De-installing a single component from an MCOD landscape requires some additional steps.

You can use a remote connection to SAP support to request help with these tasks. For moreinformation, see http://service.sap.com/remoteconnection.

n You cannot install a Unicode SAP system with a non-Unicode SAP system in one database.

n


MSCS only: You cannot install multiple components in one database with Microsoft ClusterService (MSCS). For more information about MSCS, see High Availability with Microsoft Cluster Service[page 105].End of: HA (MSCS)

n For the first SAP system, the database system ID can be different from the SAP system ID.n For the second SAP system, you must use the same DBSID as for the first SAP system.n If you decide to turn off database logging during the database load phase of the installation, you

need to plan downtime for all MCOD systems sharing the database.

05/25/2009 PUBLIC 93/152




6 Additional Information6.4 Integration of LDAP Directory Services

6.4 Integration of LDAP Directory Services

This section explains the benefits of using the SAP system with the Lightweight Directory AccessProtocol (LDAP) directory and gives an overview of the configuration steps required to use an SAPsystem with the directory.LDAP defines a standard protocol for accessing directory services, which is supported by variousdirectory products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory servicesenables important information in a corporate network to be stored centrally on a server. Theadvantage of storing information centrally for the entire network is that you only have to maintaindata once, which avoids redundancy and inconsistency.If an LDAP directory is available in your corporate network, you can configure the SAP system to usethis feature. For example, a correctly configured SAP system can read information from the directoryand also store information there.

Note

The SAP system can interact with the Active Directory using the LDAP protocol, which defines:

n The communication protocol between the SAP system and the directory

n How data in the directory is structured, accessed, or modified

If a directory other than the Active Directory also supports the LDAP protocol, the SAP system cantake advantage of the information stored there. For example, if there is an LDAP directory on a UNIXor Windows server, you can configure the SAP system to use the information available there. In thefollowing text, directories other than the Active Directory that implement the LDAP protocol arecalled generic LDAP directories.

Caution

This section does not provide information about the use of LDAP directories with the LDAPConnector. For more information about using and configuring the LDAP Connector for an ABAPsystem, see the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (includingEnhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability SecurityIdentity Management User and Role Administration of AS ABAP Configuration of User and Role AdministrationDirectory Services LDAP Connector

PrerequisitesYou can only configure the SAP system for Active Directory services or other LDAP directories ifthese are already available on the network. As of Windows 2000 or higher, the Active Directoryis automatically available on all domain controllers. A generic LDAP directory is an additionalcomponent that you must install separately on a UNIX or Windows server.

94/152 PUBLIC 05/25/2009





FeaturesIn the SAP environment, you can exploit the information stored in an Active Directory or genericLDAP directory by using:

n SAP Logonn The SAP Microsoft Management Console (SAP MMC)

For more information about the automatic registration of SAP components in LDAP directories andthe benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information inDirectory Services at http://service.sap.com/msplatforms Microsoft Windows Server

SAP Logon

Instead of using a fixed list of systems and message servers, you can configure the SAP Logon in thesapmsg.ini configuration file to find SAP systems and their message servers from the directory. Ifyou configure SAP logon to use the LDAP directory, it queries the directory each time Server or Groupselection is chosen to fetch up-to-date information on available SAP systems.To use LDAP operation mode, make sure that the sapmsg.ini file contains the following:[Address]

Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

Distinguish the following cases:

n If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For moreinformation, see the SAP system profile parameter ldap/options.

n You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either ofthe following is true:l The client is not located in the same domain forest as the Active Directoryl The operating system does not have a directory service client (Windows NT and Windows 9X

without installed dsclient).For more information, see the SAP system profile parameter ldap/servers.

n For other directory services, you can use LDAPnode to specify the distinguished name of the SAProot node. For more information, see the SAP system profile parameter ldap/saproot.

SAP MMC

The SAPMMC is a graphical user interface (GUI) for administering andmonitoring SAP systems froma central location. It is automatically set up when you install an SAP system on Windows. If the SAPsystem has been prepared correctly, the SAP MMC presents and analyzes system information thatit gathers from various sources, including the Active Directory.Integrating the Active Directory as a source of information has advantages for the SAP MMC. It canread system information straight from the directory that automatically registers changes to the

05/25/2009 PUBLIC 95/152

http://service.sap.com/msplatforms




system landscape. As a result, up-to-date information about all SAP application servers, their status,and parameter settings is always available in the SAP MMC.If you need to administer distributed systems, we especially recommend that you use the SAP MMCtogether with Active Directory services. You can keep track of significant events in all of the systemsfrom a single SAP MMC interface. You do not need to manually register changes in the systemconfiguration. Instead, such changes are automatically updated in the directory and subsequentlyreflected in the SAP MMC.If your SAP system is part of a heterogeneous SAP system landscape that comprises systems orinstances both on UNIX andWindows operating systems, you can also use the SAPMMC for operatingand monitoring the instances running on UNIX.

Note

You can also use the SAP Management Console (SAP MC) for administering and monitoringSAP systems from a central location. For more information about the SAP MC and about howto configure it to access LDAP directories, see the documentation SAP Management Console athttp://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability JavaTechnology Administration Manual J2EE Engine J2EE Engine Administration Tools SAP ManagementConsole

Configuration Tasks for LDAP Directories

This section describes the configuration tasks you have to perform for the Active Directory or other(generic) LDAP directories.

Configuration Tasks for Active Directory

To enable an SAP system to use the features offered by the Active Directory, you must configure theActive Directory so that it can store SAP system data.To prepare the directory, you use SAPinst to automatically:

n Extend the Active Directory schema to include the SAP-specific data typesn Create the domain accounts required to enable the SAP system to access and modify the Active

Directory. These are the group SAP_LDAP and the user sapldap.n Create the root container where information related to SAP is stored

n Control access to the container for SAP data by giving members of the SAP_LDAP group permissionto read and write to the directory

You do this by running SAPinst and choosing <Your SAP product> Software Life-Cycle OptionsLDAP Registration Active Directory Configuration .

96/152 PUBLIC 05/25/2009




6 Additional Information6.5 Starting and Stopping the SAP System

Note

You have to perform the directory server configuration only once. Then all SAP systems that needto register in this directory server can use this setup.

Configuration Tasks for Generic LDAP Directories

To configure other LDAP directories, refer to the documentation of your directory vendor. TheSAPinst Installation Master DVD contains schema extensions for directory servers Netscape/iPlanet(ldregns4.txt) and OpenLDAP slapd (ldregslapd.schema). Both files are located in the directory\DATA_UNITS\IM_<platform>\COMMON\ADS. After you have applied the schema extension, you need tocreate a root container to store the SAP-related information and create a directory user that the SAPapplication server can use to write information to the directory.For more information about how to set up a Netscape/iPlanet directory server, see the documentationSAP System Information in Directory Services at http://service.sap.com/msplatforms MicrosoftWindows Server

Enabling the SAP System LDAP Registration

Once you have correctly configured your directory server, you can enable the LDAP registration ofthe SAP system by setting some profile parameters in the default profile.To do this, run SAPinst once for your system and choose <Your SAP product> Software Life-CycleOptions LDAP Registration LDAP SupportIf you use a directory server other than Microsoft Active Directory and/or non-Windows applicationservers, you have to store the directory user and password information by using ldappasswdpf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and istherefore valid for all application servers. After restarting all application servers and start services,the system is registered in your directory server. The registration protocols of the components aredev_ldap*. The registration is updated every time a component starts.

6.5 Starting and Stopping the SAP System

You use this procedure to check that you can start and stop the SAP system after the installation withthe SAP Microsoft Management Console (SAP MMC).With a newly installed SAP MMC you can start or stop installed SAP instances locally on the hostthat you are logged on to. You can also start and stop the Diagnostics Agent with the SAP MMC.If the SAP MMC is configured for central system administration, you can start or stop the entiresystem from a single host.

05/25/2009 PUBLIC 97/152




6 Additional Information6.6 Implementing Single Sign-On with Microsoft Kerberos SSP for Your SAP System

Note

For more information about the SAP MMC, see http://help.sap.com/nw70 SAP NetWeaver 7.0Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key CapabilitySolution Life Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS SAPMicrosoft Management Console: Windows

PrerequisitesWindows Server 2008: The user who wants to start and stop the SAP system with the SAP MMC,must be a member of the local administrators group.

Procedure

1. Start the SAP MMC on the SAP system host by choosing Start All Programs SAP ManagementConsole .

2. Right-click the SAP system node and choose Start or Stop.All instances listed under the system node start or stop in the correct order.

3. If the SAP system is installed on multiple hosts (distributed or high-availability system), you havethe following options to start or stop your system:n You start or stop the SAP instances using the SAP MMC on each host.n You add the remote instances to the SAP MMC configuration to start or stop all instances

from a single SAP MMC.To do so, do one of the following:l You configure the SAP MMCmanually. For more information, see Changing the Configuration of

the SAP MMC in the SAP MMC documentation.l You use the automatic LDAP registration. For more information, see Configuring SAP MMC

for Active Directory Services in the SAP MMC documentation.

Note

You can also start and stop a UNIX system with the SAP MMC.

6.6 Implementing Single Sign-On with Microsoft KerberosSSP for Your SAP System

Kerberos Single Sign-On (SSO) is a secure method of logging on to the SAP system that simplifiesthe logon procedure.When your system is configured for SSO, an authorized user who has logged on to Windows canaccess the SAP system simply by selecting it in the SAP logon window or clicking the shortcut. Thereis no need to enter the SAP system user name and password when you log on to your SAP systemwith SAP GUI. SSO makes it significantly easier for you to manage SAP system users. The Microsoft

98/152 PUBLIC 05/25/2009




6 Additional Information6.7 SAP System Security on Windows

Kerberos Security Service Provider (SSP) provides secure authentication plus encryption of thenetwork communication.

ProcedureFor more information about implementing Kerberos SSO for your SAP system, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Security Network and Transport Layer Security SecureNetwork Communications (SNC) Configuring the Communication Partners to Use SNC Special Cases

6.7 SAP System Security on Windows

In a standard SAP system installation, SAPinst automatically performs all steps relevant for security.Although SAPinst makes sure that the system is protected against unauthorized access, you muststill check that no security breaches can occur.For central and straightforward administration of the SAP system, you have to install distributed SAPsystems with multiple application servers in a Windows domain. This section describes the useraccounts and groups that SAPinst creates during a domain installation and shows how these arerelated to the SAP directories.

User Accounts

SAPinst creates the following accounts for SAP system administration:

n <sapsid>adm

This is the SAP system administrator account that enables interactive administration of the system.

n SAPService<SID>

This is the user account that is required to start the SAP system. It has the local user right to logon as a service.The advantage of the additional SAPService<SAPSID> account is that it does not allow aninteractive logon, which prevents abuse of the account. Therefore, you do not need to set anexpiration date for the password and you do not have to set the option user must change passwordat next logon.

Groups

SAPinst creates the following groups during a domain installation:

n SAP_<SAPSID>_GlobalAdmin

This global group is a domain-level SAP administration group for organizing SAP systemadministrators. The only function of a global group is to group users at the domain level so thatthey can be placed in the appropriate local groups.

05/25/2009 PUBLIC 99/152




6 Additional Information6.7 SAP System Security on Windows

n SAP_<SAPSID>_LocalAdmin

Only local groups are created and maintained on an application server. A local group can only begiven permissions and rights to the system where it is located. The system is part of a particulardomain, and the local group can contain users and global groups from this domain.

n SAP_LocalAdmin

This group is created on all hosts, but is particularly important for the transport host. Members ofthe group have full control over the transport directory (\usr\sap\trans) that allows transports totake place between systems.The SAP_<SAPSID>_GlobalAdmin groups of all the SAP systems that are part of the transportinfrastructure are added to the SAP_LocalAdmin group. As a consequence, the users <sapsid>admand SAPService<SAPSID> of all systems in the transport infrastructure are members of theSAP_LocalAdmin group and have the required authorizations necessary to initiate and executetransports.

SAP Directories

SAPinst protects the SAP directories under \usr\sap\<SAPSID> by only granting the groupSAP_<SAPSID>_LocalAdmin full control over these directories.The following graphic illustrates the user accounts and groups created by SAPinst in a systeminfrastructure consisting of two SAP systems.

Figure 7: User Groups and Accounts

100/152 PUBLIC 05/25/2009

6 Additional Information6.8 Automatic Creation of Accounts and Groups

Note

An access control list (ACL) controls access to SAP system objects. For maximum security in the SAPsystem, only the following are members of all SAP system object ACLs:

n Local group SAP_<SAPSID>_LocalAdmin

n Group Administrators

n Account SYSTEM

More InformationAutomatic Creation of Accounts and Groups [page 101]

6.8 Automatic Creation of Accounts and Groups

SAPinst automatically creates the accounts and groups required for the secure operation of the SAPsystem with Windows during the installation (see SAP System Security on Windows [page 99]).

FeaturesThe following figures show the steps that SAPinst performs to create the users and groups and assignthe required rights to SAP directories.

Figure 8: Creating Users and Groups

05/25/2009 PUBLIC 101/152

6 Additional Information6.9 Troubleshooting

Figure 9: Assigning Rights to SAP Directories

6.9 Troubleshooting

The following section(s) describe the steps that you need to performmanually if SAPinst fails:

n Troubleshooting with SAPinst [page 102]

6.9.1 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.If an error occurs, SAPinst:

n Stops the installation.n Displays a dialog informing you about the error.

Procedure

1. To view the log file, choose View Logs.2. If an error occurs during the Define Parameters or Execute phase, do either of the following:n Try to solve the problemn Abort the installation by choosing Cancel in the SAPinstmenu.

For more information, see Interrupted Installation with SAPinst [page 56].

102/152 PUBLIC 05/25/2009

6 Additional Information6.10 Deleting an SAP System

n After resolving the problem, you can continue the installation by choosing Retry.3. Check the log and trace files of the GUI server and SAPinst GUI in the directory

%userprofile%\.sdtgui\ for errors.n If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current

%userprofile% directory.n If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as

described in Starting SAPinst GUI Separately [page 59].

6.10 Deleting an SAP System

This section describes how to delete a single instance, a standalone engine or a complete SAP systemwith the Uninstall option of SAPinst.

Caution

n You cannot delete an SAP system remotely.

n SAPinst deletes the database instance and optionally the database software.

n If you delete network-wide users, groups or service entries in an environment with NetworkInformation System (NIS), other SAP installations might also be affected. Make sure that theusers, groups, and service entries to be deleted are no longer required.

PrerequisitesYou are logged on with a user account that has the required authorization to run the SAPinst tooland the SAP system. For more information, see Required User Authorization for Running SAPinst [page 38].

Caution

Do not use the user <sapsid>adm to delete the SAP system.

Procedure

1. Start SAPinst and on theWelcome screen, choose:<Your SAP product> Software Life-Cycle Options Uninstall Uninstall System / Standalone Engine /

Optional Standalone Unit2. Follow the instructions in the SAPinst input dialogs.

Note

For more information about the input parameters, place the cursor on the relevant field andpress F1 in SAPinst.

05/25/2009 PUBLIC 103/152

6 Additional Information6.10 Deleting an SAP System

SAPinst first asks you which SAP instances you want to delete. Make sure that you delete the SAPinstances in the order as described hereafter.

Caution

n SAPinst only stops local instances automatically.Before you delete the database instance of a distributed system make sure that you stop allremaining instances. You must stop the instance with the message server only after havingentered all SAPinst parameters for the deletion of the database instance.

n If SAPinst stops responding while trying to delete the central instance, close SAPinst withCancel and Exit. Log off and log on again. To complete the uninstall process of the centralinstance, restart SAPinst.

n If you want to delete a central system (all instances reside on the same host), you can do thisin one SAPinst run.a) Delete the SAP system.b) Choose whether you want to drop the entire database or only one or more database

schemas. If you drop the entire database, SAPinst also asks whether you want to remove thedatabase software.

n If you want to delete a distributed or high availability system, you have to run SAPinst todelete the required instances locally on each of the hosts belonging to the SAP system in thefollowing sequence:a) Dialog instance(s), if there are anyb) Central instancec) Database instance

Choose whether you want to drop the entire database or only one or more databaseschemas. If you drop the entire database, SAPinst also asks whether you want to remove thedatabase software.

n


Enqueue Replication ServerEnd of: HA (MSCS)

n


ABAP central services instanceEnd of: HA (MSCS)

3. Delete the local user group SAP_<SAPSID>_LocalAdminmanually as follows:a) Choose Start Programs Administrative Tools Computer Management .b) Choose Local Users and Groups Groups .c) Right-click the local group SAP_<SAPSID>_LocalAdmin and choose Delete.

4. If required, you can delete the directory \usr\sap\trans and its contents manually.SAPinst does not delete \usr\sap\trans because it might be shared.

104/152 PUBLIC 05/25/2009

7 High Availability with Microsoft Cluster Service


7 High Availability with Microsoft ClusterService

Note

As ofWindows Server 2008 there are the following terminology changes for a cluster configuration:

n The cluster feature is now called Failover Clustering. For practical reasons we are continuing to usethe previous terminologyMicrosoft Cluster Service and abbreviationMSCS in this guide.

n Cluster groups are now called services and applications.In some sections that are also valid for Windows Server 2008 on MSCS we are continuing to useonly the old term. In this case, “cluster group” also means “service and application”.

n The Cluster Administrator is now called Failover Cluster Management.

You can install a high-availability SAP system with MSCS. For this type of installation, you have toset up the system and configure it so that it can take advantage of the MSCS software. The MSCSsoftware improves the availability of the system and safeguards it against failure and unplanneddowntime, enabling 24-hour operation, 365 days a year.With high availability you enable critical system components, known as “Single Points of Failure(SPOFs)”, to be automatically switched from one machine to the other, if hardware or softwareproblems arise on one machine. With the help of this switchover ‒ or failover ‒ the system cancontinue functioning so that unplanned system downtime is avoided.Apart from enabling failover when hardware problems occur, you can also use MSCS to avoiddowntime when you perform essential system maintenance. If you need to maintain one host(MSCS node), you can deliberately switch the cluster resources to the other host (MSCS node) andtemporarily operate it there while maintenance is in progress. When maintenance work is finishedyou can easily move the resources back to their original node and continue operating them there.You have the following options to install a high-availability system with MSCS:

n You install one SAP system in oneMSCS cluster.n You install one SAP system in twoMSCS clusters.

In both cases the following restrictions apply:

n You must install the (A)SCS instance on two MSCS nodes in one MSCS cluster.n If your database supports the installation on several MSCS nodes, you can install the database

instance on more than two MSCS nodes in one MSCS cluster.

05/25/2009 PUBLIC 105/152

7 High Availability with Microsoft Cluster Service7.1 Planning

Note

n Make sure that you read SAP Note 1171448, which contains the most recent information as wellas corrections for a high-availability installation. For more information, see the SAP installationnotes [page 10] before you begin the installation.

n In this documentation the hosts in an MSCS cluster are referred to as first MSCS (cluster) nodeand additional MSCS (cluster) node(s).

n When you are setting up the SAP system with MSCS, you combine standard installation steps,described earlier in this documentation, with cluster-specific steps, described here.

To install a new SAP systemwithMSCS, you have to perform a number of extra steps specially requiredfor the cluster and configure the SAP system so that it can take advantage of the cluster functionality:

n Since the cluster hardware has at least two nodes that have access to all local and shared storagedevices, you have to install some components on all nodes and observe special rules for distributingcomponents to local or shared disks.

n Since the correct configuration of network addresses is absolutely essential to enable the clusterto function properly, you have to perform a number of additional steps that are necessary toset up and check addressing.

Note

If you have an existing SAP system and plan to migrate to a cluster with new hardware, you installthe SAP system using a system copy.For more information about the system copy, see the System Copy Guide for your SAP system at:http://service.sap.com/instguides <Release> Installation

The documentation for system copy does not include the cluster-specific information, which isdescribed here.

7.1 Planning

For your SAP system using Microsoft Cluster Service (MSCS), you have to complete the followingplanning activities, which are described in more detail in the linked sections:

1. You check that you have completed the general planning activities [page 13].2. You decide how to set up your SAP system components in an MSCS configuration [page 107].3. You decide how to distribute SAP system components to disks for MSCS [page 111].4. You read Directories in an MSCS Configuration [page 115]5. You read IP Addresses in an MSCS Configuration [page 116]6. You obtain and check IP addresses for MSCS [page 119].

106/152 PUBLIC 05/25/2009




Note

This step is not required if you use Windows Server 2008 and DHCP-based IP addresses.

7.1.1 System Configuration in MSCS

The following chapters provide information about the configuration of your SAP systemconfiguration in MSCS. It describes the components you have to install for an SAP system running ina cluster, and how to distribute them on the specific host. For more information, see:

n SAP System Components in an MSCS Configuration [page 107]n Enqueue Replication Server in MSCS [page 110]

7.1.1.1 SAP System Components in an MSCS Configuration

In an MSCS configuration you have the following components for your SAP system:

SAP System Components in an MSCS Configuration

ComponentNumber of Components per SAPSystem Single Point of Failure (SPOF)

ASCS instance (message servicesand enqueue services)

1 yes

Database instance 1 yes

Application server (centralinstance, dialog instance)

1-<n> no

n To protect the SPOFs ((A)SCS instance, database instance) you have to use MSCS.If a hardware or software problem occurs on the first MSCS node, the clustered (A)SCS instanceand the clustered database automatically fail over to the other node.If you need to maintain the MSCS node where the (A)SCS instance and database are running youcan switch these instances to the other node. When maintenance work is finished you move the(A)SCS and database instance back to the original node.

n To protect system components that are non-SPOFs, for example application servers, you haveto install them as multiple components. In this case you must install at least two applicationservers (one central instance and at least one dialog instance) on two different hosts. You havethe following options:l You install the central instance and the dialog instance on the MSCS nodes of an MSCS cluster.

You install them on a local disk. Any additional dialog instances are installed on hosts outsideof the MSCS cluster.

05/25/2009 PUBLIC 107/152


If you have to maintain an MSCS node, you have to stop the central or dialog instance on thatnode. When you have finished maintenance, you restart the instance(s).

Note

If you install the central instance and the dialog instance on the MSCS cluster nodes, youmustperform the hardware sizing for the MSCS host, as in this case the application server is alwaysrunning on this host. This increases system load and might impact performance. Note that, asusual in an MSCS setup, the (A)SCS and database instances also switch to run on the MSCShost in the event of failover, which temporarily also increases system load.

l You install the central instance and all dialog instances on hosts, which are not part of anMS cluster.

The following figures show examples for the installation of SPOFs and non-SPOFs of an SAP systemin an MSCS cluster with two nodes.The first figure shows an MSCS configuration where the non-SPOFs components (central instance,dialog instance) are installed locally on the MSCS nodes. Any additional dialog instance(s) areinstalled outside the MSCS cluster on separate hosts.

Figure 10: ABAP System with SPOFs, where non-SPOFs are installed locally on the MSCS ClusterNodes

108/152 PUBLIC 05/25/2009


The following figure shows an MSCS configuration, where the non-SPOFs components (centralinstance, dialog instance) are installed on separate hosts that are not part of the MS cluster.

Figure 11: ABAP System where the non-SPOFs are installed on hosts outside of the MS Cluster

Installing the SAP System on Two MSCS Clusters

Besides installing your SAP system within one MSCS cluster, you can also set up two MSCS clustersand distribute the SPOF system components on these clusters to protect them against system failure.The following figure shows an example where the database instance for the SAP system is installed inone MSCS cluster, and the (A)SCS instance is installed on the second MSCS cluster. The applicationservers (central and dialog instance) can either be installed on a local disk on the MSCS nodes or onseparate hosts that are not part of the MS cluster.

05/25/2009 PUBLIC 109/152


Figure 12: ABAP System

7.1.1.2 Enqueue Replication Server in an MSCS Configuration

The enqueue replication server contains a replica of the lock table (replication table) and is anessential component in a high-availability setup. You have to install the enqueue replication server onthe two MSCS nodes where the (A)SCS instance is installed and configured to run.In normal operation the replication enqueue server is always active on the host where the (A)SCSinstance is not running.If an enqueue server in an MSCS cluster with two nodes fails on the first MSCS node, the enqueueserver on the additional MSCS node is started. It retrieves the data from the replication table onthat node and writes it in its lock table. The enqueue replication server on the second MSCS nodethen becomes inactive. If the first MSCS node is available again, the enqueue replication server onthe second MSCS node becomes active again.The following figure shows the enqueue replication server mechanism in an MSCS configurationwith two nodes:

110/152 PUBLIC 05/25/2009


Figure 13: Enqueue Replication Server Mechanism on One MSCS Cluster with Two Nodes

7.1.2 Distribution of SAP System Components to Disks forMSCS

When planning the MSCS installation, keep in mind that the cluster hardware has two differentsets of disks:

n Local disks that are connected directly to the MSCS node(s)n Shared disks that can be accessed by all MSCS nodes via a shared interconnect

Note

Shared disk is a synonym for the MSCS resource of Resource type Physical disk.

You need to install the SAP system components in both the following ways:

n Separately on all MSCS nodes to use the local storage on each noden On the shared storage used in common by all MSCS nodes

You install the following on different shared disks:l Database instance files

l (A)SCS instancel SAP system executablesl Single quorum device, if used

05/25/2009 PUBLIC 111/152


Caution

Youmust not install any SAP or database components on the quorum disk.

The following figure shows a cluster configuration, where the (A)SCS and DB instance are installed inthe same cluster. It illustrates how to distribute the database data files, the SAP system executables,and the quorum resource (if used) to different disks. Only with this distribution of files to distinctdisks is it possible to move the SAP system and database as separate entities in a failover situation.

Figure 14:

Note

The following software on the local disks must have the same drive letter and path on both nodes:

n Instance-independent program software

n Instance-dependent software

Quorum Configurations on Windows

On Windows there are several quorum configurations available. The configuration to use mainlydepends on the cluster setup, such as the number of cluster nodes, the storage type (single ordistributed), and the number of data centers. Formore information, see theWindows documentation.The default quorum configurations used on Windows are:

n Single Quorum Device Cluster ‒ default quorum configuration on Windows Server 2003

112/152 PUBLIC 05/25/2009


Note

On Windows Server 2008, this quorum configuration is called “No Majority: Disk Only”.However, we do not recommend you to use this.

In this cluster model, the quorum resource maintains the cluster configuration data on a singleshared disk. The quorum resource is unique in this cluster configuration and is always ownedby one of the nodes. The quorum disk is a single resource so that if it becomes unavailable, thecluster does not work.The quorum resource has the following main functions in the cluster:l It logs changes to the cluster configuration that are entered in the Registry.l It arbitrates between competing nodes when the communication between nodes breaks down.

This means that cluster resources are forced to fail over to the node that owns the quorumresource.

n Node and Disk Majority ‒ default quorum configuration on Windows Server 2008With this quorum configuration, each node and the witness disk maintain its own copy of thecluster configuration data. This ensures that the cluster configuration is kept running evenif the witness disk fails or is offline.Note that the disk layout of the Node and Disk Majority and the Single Quorum Device Cluster isidentical.

Caution

If you do not use the default quorum configuration for your operating system, contact yourhardware partner, who can help you to analyze your needs and set up your cluster model. SAPsupports these configurations if they are part of a cluster solution offered by your OriginalEquipment Manufacturer (OEM), or Independent Hardware Vendor (IHV).

Locally Dispersed Cluster

The standard MSCS configuration consists of two cluster nodes and a shared disk storage with alltechnical components located in the same data center. In a geographically dispersed cluster, alsoknow as a geospan cluster, the cluster nodes are distributed across at least two data centers to avoidthe full outage of a data center in the event of disaster.A locally dispersed MSCS configuration requires a more sophisticated disk storage architecture since ashared disk storage can be only located in one data center and might be therefore a single point offailure (SPOF). To prevent the disk storage becoming a SPOF, you have to configure the storage systemin each data center and to replicate its content to the storage system of the other data center.Replication can either be synchronous or asynchronous, which depends on the:

n Functionality of the disk storage subsystemn Acceptable amount of data loss during a failovern Physical layout of the disk storage area network

05/25/2009 PUBLIC 113/152


This includes the distance between the storage systems, signal latency, capacity and speed of thenetwork connection.

n Customer budgetn Functionality supported by the database vendor

Often, the database components in geospan configurations are no longer part of the MSCS andthe database is replicated by pure database techniques, such as shadow database, log shipping, andmirrored database.

Caution

n Currently you can configure locally dispersed clusters only in the same subnet since you cannot(Windows Server 2003) or must not (Windows Server 2008) change a virtual IP address duringfailover.

n The numerous variants with locally dispersed cluster configurations and the complex technicalrequirements are the reasons why the installation and configuration of such high-availability(HA) systems are not directly supported by SAP. Instead, the hardware vendors of this clusterconfiguration are responsible for the installation, configuration, and operation of the HAcomponents running in locally dispersed clusters. SAP only supports the standard operation andfunction of the SAP components running in such MSCS configurations.

All functions to set up locally dispersed clusters are already integrated in Windows Server 2008.If you use Windows Server 2003, refer to the following information to set up locally dispersed clusters:

n White paper Server Clusters: Majority Node Set Quorum at:http://technet2.microsoft.com/WindowsServer/en/library/

e70333db-5048-4a56-b5a9-8353756de10b1033.mspx.n Information about the file share witness feature, at:

http://support.microsoft.com/kb/921181

Distribution of Database Files in a RAID Configuration

Caution

Microsoft does not support host-based RAID configurations (Dynamic Disks) on shared disks.

The following figure shows a secure method to distribute the database directories to different RAIDvolumes.

114/152 PUBLIC 05/25/2009

http://technet2.microsoft.com/WindowsServer/en/library/e70333db-5048-4a56-b5a9-8353756de10b1033.mspx






http://support.microsoft.com/kb/921181


Figure 15:

More InformationDirectories in an MSCS Configuration [page 115]

7.1.3 Directories in an MSCS Configuration

The following tables show the directories where the main software components for the SAP clusterinstallation are stored:

Directories on Local Disks on MSCS Nodes

Component Default Directory

A supported operating system [page 21] %windir%

MSCS software %windir%\Cluster

SAP cluster files %windir%\SAPCluster

SAP MaxDB instance-independent programs <drive>:\sapdb\program

SAP MaxDB instance-dependent software <drive>:\sapdb\<DBSID>\db

05/25/2009 PUBLIC 115/152


Directories on Shared Disks

Component Default Directory

Cluster quorum resource <drive>:\MSCS (Windows Server 2003)<drive>:\Cluster (Windows Server 2008)

SAP global and instance directories <drive>:\usr\sap ...

SAP MaxDB data volumes <drive>:\sapdb\<SAPSID>\sapdata\...

SAP MaxDB database log volumes <drive>:\sapdb\<SAPSID>\saplog\...

SAP MaxDB mirrored database log volumes <drive>:\sapdb\<SAPSID>\saplog\...

SAP MaxDB instance-independent data <drive>:\sapdb\data

SapCluster Directory

In an SAP cluster installation, an additional directory ‒ %WINDIR%\SapCluster ‒ is created underthe system directory.This contains all the SAP files required by all MSCS cluster nodes, independently of the MSCS nodethe SAP instance is running on. The files are database tools and program files (executables) usedby the operating system monitor (SAPOsCol).The directory is added to the path variable of the user <sapsid>adm.

7.1.4 IP Addresses in an MSCS Configuration

A part of the installation process that is unique to MSCS is the configuration of host names and IPaddresses in the network. This is a particularly important task because the addressing plays a keyrole in the switchover procedure. Addressing must be set up correctly so that the system can takeadvantage of the cluster functionality and switch between nodes when hardware problems arise.This section explains the different types of IP addresses and their function in the switchovermechanism of an MSCS cluster with two nodes.

Note

Windows Server 2008 only:As of Windows Server 2008, besides static IP addresses, you can also have DHCP-based (dynamic) IPaddresses. The DHCP-based IP addresses are currently only supported when all MSCS nodes arelocated in the same subnet.If the network adapters are assigned to DHCP-based IP addresses, the virtual IP addresses are alsoconfigured automatically as DHCP-based IP addresses.

116/152 PUBLIC 05/25/2009


Types of IP Addresses

In a correctly configured cluster with two nodes, there are seven IP addresses and corresponding hostnames for your SAP system. You have two IP addresses for each MSCS node, one IP address for thecluster, one for the SAP cluster group, and one for the database cluster group.Some of the addresses are assigned to the network adapters (cards), others are virtual IP addressesthat are assigned to the cluster groups.

Physical IP Addresses Assigned to Network Adapters

An MSCS configuration has two networks:

n A public network that is used for the communication between the central instance, applicationservers and the LAN.

n A private network that is used internally for communication between the nodes of the cluster.

Note

For more information, see the Microsoft Knowledge Base Article 259267.

The following figure shows an MSCS cluster with two nodes and illustrates the adapters required forthe public and private networks, and their corresponding physical IP addresses. A physical IP address,as opposed to a virtual one, is stationary and permanently mapped to the same adapter.

Figure 16: Adapters and IP Addresses Required for Public and Private Networks in an MSCS Clusterwith Two Nodes

05/25/2009 PUBLIC 117/152


Host Names Assigned to Network Adapters

Each of the physical IP addresses of the network adapters must have a corresponding host name. Forexample, on the left-hand node in the figure above, you might assign the IP addresses of the publicand private network adapters as follows:

IP Addresses and Host Names

Network Adapter IP Address Host Name

Adapter 1 (private network) 10.1.1.1 clusA_priv

Adapter 3 ( public network) 129.20.5.1 clusA

Caution

Make sure that you are aware of the following:

n The IP address and host name of the public network adapter is also the IP address and name ofthe machine. In our example, this means that the machine that is the MSCS node on the leftin the figure has the name clusA.

n Do not confuse the host name with the computer name. Each node also has a computername, which is often the same as the host name.The computer name is displayed in the node column of the Cluster Administrator (Windows Server2003) or Failover Cluster Management (Windows Server 2008). However, it isnot required for the TCP/IPcommunication in the cluster. When you configure IP addresses and corresponding names, keepin mind that it is the host names that are important for the cluster, not the computer names.

Virtual IP Addresses Assigned to Cluster Groups

When you have installed the SAP system and fully configured the cluster, the critical system resourcesare bound together in three different groups. Each of these groups requires a virtual IP address andhost name that is permanently mapped to the group and not to a particular node. This has theadvantage that, whenever a group is moved between nodes, its IP address and host name movetogether with it.A cluster configuration has the following groups:

n SAP cluster groupn Database cluster groupn Cluster group

Note

Windows Server 2008 only:Although it exists, the cluster group is not visible.

Each group consists of a set of related resources that work together to offer a service to the system.For example, the database cluster group comprises all the resources that enable the database server to

118/152 PUBLIC 05/25/2009


fulfill the requests of a client. When the group is moved from one node to the other, due to nodefailure, the virtual IP address and host name move with it. Therefore, there is a failover not only ofresources, but also of the virtual IP address and host name. As a result, all clients can still reach thedatabase server with the same IP address as before.The following figure illustrates how the virtual IP addresses of the database group and SAP group canmove from one node to the other when failover occurs.

Figure 17: Failover of Virtual IP Addresses

7.1.5 Obtaining and Determining IP Addresses for MSCS

Note

Windows Server 2008 only:As of Windows Server 2008, besides static IP addresses you can use DHCP-based IP addresses. Thefollowing information is only relevant if you use static IP addresses.

This chapter describes how to obtain and to find out the IP addresses for the network adapters (cards)that are required to install and run your cluster configuration.You need to correctly configure IP addresses for a cluster system. During the installation procedureyou have to assign at least seven IP addresses and host names. You normally obtain these namesand addresses from the system administrator.

05/25/2009 PUBLIC 119/152


Obtaining IP AddressesAsk the system administrator to give you the addresses and host names listed in the tables below,which shows an example for a configuration with one MSCS cluster with two nodes. You need toenter the addresses and host names later during the installation process.The column Defined During indicates at which stage of the installation of the operating system and theSAP system the addresses are defined in the system.

Caution

Use the names exactly as specified by the system administrator, carefully observing uppercase andlowercase letters.

Note

In the following tables we are only using the terminology cluster group, and not the Windows Server2008 terminology service and application.

Physical IP Addresses

Component

Example forPhysical IPAddress

Example forPhysical HostName Purpose Defined During

First MSCS Node:adapter for privatenetwork

10.1.1.1 clusA_priv Address forinternodecommunication onthe private network

Windowsinstallation

First MSCS Node:adapter for publicnetwork

129.20.5.1 clusA Address of the firstMSCS node forcommunicationwith applicationservers and LAN(this is the same asthe address of thefirst MSCS node)

Windowsinstallation

Additional MSCSNode:adapter for privatenetwork

10.1.1.2 clusB_priv Address forinternodecommunication onthe private network

Windowsinstallation

Additional MSCSNode:adapter for publicnetwork

129.20.5.2 clusB Address ofthe additionalMSCS node forcommunicationwith applicationservers and LAN(this is the same asthe address of the

Windowsinstallation

120/152 PUBLIC 05/25/2009


Component

Example forPhysical IPAddress

Example forPhysical HostName Purpose Defined During

additional MSCSnode)

Virtual IP Addresses

ComponentExample for VirtualIP Address

Example for HostName Purpose Defined During

Cluster group 129.20.5.3 clusgrp Virtual addressand name of thecluster group.It identifies thecluster and is usedfor administrationpurposes.

MSCS softwareinstallation

SAP cluster group 129.20.5.4 sapgrp Virtual address andname for accessingthe group of SAPresources, regardlessof the node it isrunning on

Configuration ofSAP system forMSCS with SAPinston the first node

Database clustergroup

129.20.5.5 dbgrp Virtual address andname for accessingthe group ofdatabase resources,regardless of thenode it is runningon

Execution ofMSCS wizard ordatabase-specificcluster scripts

Determining Existing IP AddressesTo find out the existing IP addresses and corresponding host names and addresses, proceed as follows:

1. ForWindows Server 2003 choose Start Control Panel Network Connections .ForWindows Server 2008 choose Start Control Panel Network and Sharing Center Manage networkconnections .

2. Right-click one of the network cards (default name is Local Area Connection) that are displayedand choose Properties.

3. Choose Internet Protocol (TCP/IP) Properties .The Internet Protocol (TCP/IP) Properties dialog box appears and shows the IP address of the initiallyselected network card.

4. To find out the host name that is mapped to the IP address, use the ping command:ping -a <IP_Address>

The system returns the host name assigned to the IP address.

05/25/2009 PUBLIC 121/152

7 High Availability with Microsoft Cluster Service7.2 Preparation

Do not forget to ping your local machine as well.5. Repeat these steps for the other network cards.

For more information about IP addresses in the cluster environment, see IP Addresses in an MSCSConfiguration [page 116].

7.2 Preparation

For the installation of a high-availability system with Microsoft Cluster Service (MSCS), you haveto perform the same preparation tasks as for a non-HA system [page 35], including the hardware and softwarerequirements [page 21]. In addition, you have to perform the following MSCS-specific preparation tasks,which are described in more detail in the linked sections:

1. On allMSCS nodes, you manually assign drive letters to the shared disks [page 122]. All MSCS nodes mustaccess the shared disks with the same drive letters.

2. You map the IP addresses to host names [page 123] on the Domain Name System (DNS) Server or in thehosts file.

Note


3. You check the mapping of host names for MSCS [page 124].

Note


Note

To make sure that all preparation steps have been correctly performed, check that you can movethe disk resources from one node to another so that they are only accessible from a single node atany time.

7.2.1 Assigning Drive Letters for MSCS

We recommend that you assign drive letters to the shared disks.In an MSCS cluster, the shared disks that can be accessed by all nodes via a common bus must beaddressed by all nodes with the same drive letters.

122/152 PUBLIC 05/25/2009


Procedure

1. Choose Start Control Panel Administrative Tools Computer Management Storage DiskManagement.

2. Select a disk and choose Action All tasks Change Drive Letter and Paths...3. Enter a new drive letter.

7.2.2 Mapping Host Names to IP Addresses for MSCS

Note

Windows Server 2008 only:This step is not required if you use DHCP-based IP addresses.

To enable correct operation of the failover mechanism, you have to map all IP addresses in the MSCScluster to host names.The mapping enables the system to translate host names into IP addresses. Host names are normallyused for administrative tasks because they are easier to use than the long, numeric IP addresses.However, the system can only respond to host names if they are translated into IP addresses.

Prerequisites

n You have installed the Windows operating system.n You have the list of IP addresses [page 119].n You have correctly entered all seven IP addresses required for the MSCS configuration.

Caution

Missing or incorrect entries for the IP addresses can cause problems later during the installation.

ProcedureTo map the host names to the IP addresses, do one of the following:

n Map the host names to IP addresses on a Domain Name System (DNS) server.n Map the IP addresses in the Windows hosts file.

The file is located in the default Windows directory:%SystemRoot%Drive\system32\drivers\etc

05/25/2009 PUBLIC 123/152


Recommendation

We recommend that you perform the mapping on the DNS server because this only requires asingle entry.If you perform the mapping in the hosts file, you have to maintain the hosts file on all MSCS nodesof the cluster, and on all application servers and front ends. This is necessary because each hostin the system has its own hosts file.

7.2.3 Checking the Mapping of Host Names for MSCS

Note

Windows Server 2008 only:This step is not required if you use DHCP-based IP addresses.

You need to check the mapping of host names to IP addresses as otherwise you might have seriousproblems later.

PrerequisitesYou have mapped the host names to the IP addresses [page 123] on the DNS Server or in the hosts file.

Procedure

1. For each IP address enter the following commands:a) ping -a <IP_Address>

The system returns the host name that is assigned to the IP address.b) ping hostname

The system returns the IP address that is assigned to the host name.

Note

n When you enter the ping command, you only receive a reply if the host already exists.

n If the address you are checking already exists in the system, you also receive a reply from thehost. For example, after the installation of Windows and the configuration of the network,you receive a reply when entering the IP addresses of the network adapters.

2. Compare the output with your own record of addresses and host names, and check for thefollowing possible errors:n Incorrect output of uppercase and lowercase

Make sure that you correct the error before you proceed with the installation.n Error in the network bindings

124/152 PUBLIC 05/25/2009

7 High Availability with Microsoft Cluster Service7.3 Installation

If you enter the name of the public network adapter, which is usually also the name of thelocal host, and the system returns the IP address of the private network, there is an errorin the network bindings.To correct the network bindings, do the following on allMSCS nodes:a) Choose Start Settings Network and Dial-up Connections

The Network and Dial-up Connections window appears.b) Choose Advanced Advanced Settings Adapters and Bindings

The network cards of the private and public networks are displayed for the current MSCSnode.

Note

The card of the public network must be displayed before that of the private network. Ifnecessary, change the order in which the cards are listed by using theMove Up andMoveDown arrows

7.3 Installation

The following sections provide information about how to install the SAP system for MSCS.

Note

n Make sure that you are logged on as domain administrator, unless otherwise specified.If for any reason, you are not granted domain administrators rights, you can perform theinstallation as a domain user who is a member of the local administrators group. However, thedomain administrator has to prepare the system appropriately for you.

n Do not use the user <sapsid>adm unless specified.n On the first MSCS node, in the Cluster Administrator (Windows Server 2003) or Failover Cluster

Management (Windows Server 2008) make sure that all existing cluster groups are online.n If you are prompted during the installation process, log off and log on again.

n When you reboot during the installation process [page 127], resources fail over to the other node(s).Therefore, pause the other node(s) before the reboot.

You have to perform the following steps, which are described in more detail in the linked sections:

1. In the Cluster Administrator (Windows Server 2003) or Failover Cluster Management (Windows Server 2008)you move all disk groups and the cluster group to the first MSCS node [page 126].

2. You install the central services instance for ABAP (ASCS) on the first MSCS node [page 127] of the host wherethe ASCS instance is to run.

3. You cluster the first MSCS node [page 129].4. You install the SAP MaxDB database on the first MSCS node [page 130].5. You configure the SAP MaxDB database on the additional MSCS node [page 130].

05/25/2009 PUBLIC 125/152


6. You install the database instance on the first MSCS node [page 131] of the host where the database instanceis to run.

7. You cluster the additional MSCS node [page 131].8. You install an enqueue replication server [page 133] on the host where the (A)SCS instance runs.9. You install the central instance [page 134] on the central instance host or on a local disk on the MSCS

node.10. You install at least one dialog instance [page 135] on the dialog instance host or on a local disk on the

MSCS node.

7.3.1 Moving MSCS Groups or Services and Applications

Note

As ofWindows Server 2008 there are the following terminology changes:

n Cluster groups are now called services and applications.We do not always use both names in this section.

n The Cluster Administrator is now called Failover Cluster Management.

During the cluster installation you have to move the database, SAP, or disk cluster groups from oneMSCS node to the other before you can continue. You use the Cluster Administrator (Windows Server2003) or Failover Cluster Management (Windows Server 2008) for this.

Prerequisites

n Windows Server 2003:The groups you want to move are configured and are visible in the Cluster Administrator.Windows Server 2008:The services or applications you want to move are configured and are visible in the Failover ClusterManagement.

n For more information if you need to reboot during the installation, see Rebooting During the Installationor Conversion for MSCS [page 127].

Windows Server 2003: Moving Groups with the Cluster Administrator

1. Start the Cluster Administrator with Start All Programs Administrative Tools Cluster Administrator .2. In the Cluster Administrator, select the group you want to move and drag it to the required MSCS

node on the left-hand pane.3. Repeat the previous step for each group that you want to move.

126/152 PUBLIC 05/25/2009


Windows Server 2008: Moving Services and Applications with theFailover Cluster Management

Note

Only move disks that are assigned to services or applications.

1. Start the Failover Cluster Management with Start Administrative Tools Failover Cluster Management .2. In the Failover Cluster Management, right click the service and application you want to move.3. Choose Move this service or application to another node Move to <relevant node> .4. Repeat the previous step for each service and application that you want to move.

7.3.2 Rebooting During the Installation or Conversion forMSCS

You only need to perform this procedure if you have to reboot during the installation or conversionfor MSCS. A reboot means that resources fail over to another MSCS node. To avoid this, pause theadditional MSCS node in the Cluster Administrator.

Procedure

1. Before the reboot, pause the additional MSCS node(s) in the Cluster Administrator (Windows Server2003) or Failover Cluster Management (Windows Server 2008).

2. After the reboot, activate the paused MSCS node(s) in the Cluster Administrator (Windows Server2003) or Failover Cluster Management (Windows Server 2008).

3. If you forgot to pause the MSCS node(s) before you reboot, perform the following steps:a) After the reboot, in the Cluster Administrator (Windows Server 2003) or Failover Cluster Management

(Windows Server 2008), move all resources back to the original node.b) Restart the Windows Server service.

7.3.3 Installing the Central Services Instance for ABAP (ASCS)

1. Windows Server 2008 only:Before you install the central services instance for ABAP (ASCS), you must create the SAP Servicesand Applications as follows:a) Open the Failover Cluster Management Console.b) Expand the navigation tree of the cluster.c) Right-click Services and Applications.d) Choose More Actions... Create Empty Service or Application .e) Rename the newly created service and application to SAP <SAPSID>.

05/25/2009 PUBLIC 127/152


f) Right-click the service and application SAP <SAPSID> and choose Add Storage.g) Select the disk where the SAP instance is to be installed and choose OK.h) Right-click the service and application SAP <SAPSID>.i) Select Add a resource Client Access Point .j) In the Client Access Pointwizard, underName enter the virtual host name for the SCS instance and

choose Next and then Finish.

Note

Depending on whether you use DHCP, you might need to enter the IP Address details on thesecond tab. Confirm your entries with Next and then Finish.

k) Right-click the service and application SAP <SAPSID>.l) Choose Add a resource Add File Server .m)Double-click New File Server.n) In the New File Server Properties window, change the Resource Name from New File Server into SAP

<SAPSID> FileServer.

Caution

If you do not change the name, the clustering steps with SAPinst fail.

o) Go to the Dependencies tab and add the cluster disk resource to the dependencies list.Add the Name:Virtual Networkname to the dependencies list.

p) Right-click the SAP <SAPSID> FileServer resource and choose Bring this resource online.2. Start SAPinst [page 47].

Caution

Windows Server 2008 only:Do not start the SAPinst executable sapinst.exe by double-clicking it in the Windows Explorer.Instead, open a Command Prompt and change to the direc-tory:<InstallationMasterDVD>:\IM_WINDOWS_<platform>.Enter sapinst.exe SAPINST_USE_HOSTNAME=<virtual hostname of (A)SCS instance>

3. Choose <Your SAP product> <SAP technical stack> <Database> High-Availability System CentralServices Instance for ABAP (ASCS) .

4. If you are installing the SCS instance with SAPinst for the first time and SAPinst prompts you tolog off, choose OK and log on again.

5. Follow the instructions in the SAPinst dialogs and enter the required parameters.

Note

For more information about the input parameters, position the cursor on a parameter andpress F1 in SAPinst.

128/152 PUBLIC 05/25/2009


Caution

The ASCS installation drive must be a shared disk that belongs to the SAP cluster group.

6. Check that the ASCS instance is running.

7.3.4 Configuring the First MSCS Node

To configure the first MSCS node so that it functions properly in MSCS, you have to run the clusterconfiguration option offered by the SAPinst tool. When you run this option it:

n Creates the SAP cluster groupn Copies tools to the SAPCluster directoryn Sets the SAPService to manual

n Makes sure that the SAPOsCol service starts from the SAPCluster directory

Caution

When you reboot during the conversion to MSCS [page 127], resources fail over to the other MSCS node.Therefore, after each reboot you have to return the system to the state it was in before the reboot.

Prerequisites

n You are logged on to the firstMSCS node as domain administrator or as a local user with domainadministration rights. For more information, see Performing a Domain Installation without being a DomainAdministrator [page 89].

n The ASCS installation drive must be online on the first MSCS node.

Procedure

1. Run SAPinst and choose:<Your SAP product> <SAP technical stack> <Database> High-Availability System First MSCS

Node

Note

If SAPinst prompts you to log off from your system, log off and log on again.

2. Enter the required parameter values.

Note

n Make sure that you choose instance type ABAP SCS Instance (ABAP only).

n On the SAPinst screen SAP System > MSCS Cluster do not select this checkbox:Support of multiple SAP systems in one MSCS cluster?

05/25/2009 PUBLIC 129/152


Note

For more information about the input parameters, position the cursor on the parameter andpress F1 in SAPinst.

3. When the installation is finished, make sure that the following value is set in the default profile:enque/serverhost=<Virtual_ASCS_HostName>

ResultSAPinst converts the SAP instances on the first MSCS node for operation in MSCS.

7.3.5 Installing the Database on the First Node

1. Run SAPinst [page 47] and choose:<Your SAP System> SAP Systems <Database> High-Availability System Based on <technical

stack> MaxDB Database Installation2. If you are installing the SAP MaxDB database with SAPinst for the first time and SAPinst prompts

you to log off, do the following:a) Choose OK and log on again.b) Perform step 1 above.c) Select Run a new installation and choose OK..

3. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

Note


Caution

Make sure that you distribute the SAP MaxDB software and logs correctly to local and shareddisks as described in Directories in an MSCS Configuration [page 115].

7.3.6 Configuring the Database on the Additional Node

Perform the following steps on the additional MSCS node.

1. On the additional MSCS node, run SAPinst [page 47] and choose:<Your SAP System> SAP Systems <Database> High-Availability System Based on <technical

stack> MaxDB Database Configuration2. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

130/152 PUBLIC 05/25/2009


Caution

Make sure that you distribute the SAP MaxDB software and logs correctly to local and shareddisks as described in Directories in an MSCS Configuration [page 115].

Note

For more information about the input parameters, position the cursor on a parameter andpress the F1 key in SAPinst.

7.3.7 Installing the Database Instance

Prerequisites

n The SAP cluster group is Online on the first MSCS node.

ProcedurePerform the following steps on the first MSCS node.

1. On the first MSCS node, run SAPinst [page 47] and choose:<Your SAP product> <SAP technical stack> <Database> High-Availability System Database

Instance2. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

a) For the profile UNC path you have to use the virtual (A)SCS host name, for example:\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.

b) When SAPinst prompts you for the database host, make sure that you enter the virtualdatabase host.

Note

For more information about the input parameters, position the cursor on a parameter and press theF1 key in SAPinst.

7.3.8 Configuring the Additional MSCS Node

To configure the additional MSCS node in the cluster, you have to run the MSCS configurationoption for each additional MSCS node offered by the SAPinst tool. When you run this option it:

n Creates users and groupsn Sets the system and user environmentn Enters required port numbers in the Windows services file

05/25/2009 PUBLIC 131/152


n Creates the SAPService and SAPOsCol Services

Caution

When you reboot during the conversion to MSCS [page 127], resources fail over to the other MSCS node.Therefore, after each reboot you have to return the system to the state it was in before the reboot.

Prerequisites

n You are logged on to the additionalMSCS node as domain administrator or as a local user withdomain administration rights. For more information, see Performing ad Domain Installation withoutbeing a Domain Administrator [page 89].

n You have already configured the first MSCS node [page 129].

Procedure

1. Run SAPinst and choose:<Your SAP product> <SAP technical stack> <Database> High-Availability System Additional

MSCS Node

Note

If SAPinst prompts you to log off from your system, log off and log on again.

2. Enter the required parameter values.

Note

n Make sure that you choose instance type ABAP SCS Instance (ABAP only).

n On the SAPinst screen SAP System >MSCS Cluster do not select the following checkbox: Support ofmultiple SAP systems in one MSCS cluster?

Note

For more information about the input parameters, position the cursor on the parameter andpress F1 in SAPinst.

When you have made all required entries, SAPinst begins processing and converts the SAPinstances on the other MSCS node for operation in MSCS.

3. When SAPinst has finished, start the SAP <SAPSID> cluster group (Windows Server 2003) or serviceand application (Windows Server 2008) as follows:Windows Server 2003 only:a) Open the Cluster Administrator with:

Start Control Panel Administrative Tools Cluster Administratorb) Select the SAP cluster group and bring it online.Windows Server 2008 only:

132/152 PUBLIC 05/25/2009


a) Open the Failover Cluster Management with:Start Control Panel Administrative Tools Failover Cluster Management

b) Right-click the service and application SAP <SAPSID> and bring it online.

7.3.9 Installing an Enqueue Replication Server

We recommend that you install an enqueue replication server with SAPinst on allMSCS nodeswhere an ASCS instance is running.

Note

You have to perform the installation at least two times.

Prerequisites

n Your ASCS instance is already clustered with MSCS.n You have to install the enqueue replication server on a local disk.

Procedure

1. On the firstMSCS node, log on as domain user who is a member of the local administrators group.2. Run SAPinst [page 47] and choose:

<Your SAP product> <SAP technical stack> <Database> High-Availability System EnqueueReplication Server

3. Follow the instructions in the SAPinst dialogs and enter the required parameters.Note the following, when entering the parametersn On the SAPinst screen: SAP System > SAP Instance, enter the:l SAP system ID <SAPSID> of your SAP systeml Instance number of the ASCS instance

l Virtual instance host name of the ASCS instance

n On the SAPinst screen SAP System > Enqueue Replication Server Instance, enter a unique instancenumber that is not in use by another instance on this host.

n Decide if you want to restart the ASCS instance and service cluster resources with SAPinstnow, or later with the Cluster Administrator (Windows Server 2003) or Failover Cluster Management(Windows Server 2008).

Note

You only need to do this once for all enqueue replication servers that you install on theMSCS nodes.

After you have entered all required input information, SAPinst starts the installation and displaysthe progress of the installation. During the process phase, the enqueue server instance is started.

05/25/2009 PUBLIC 133/152


SAPinst installs the enqueue replication server instance on a local disk in the following directory:.\usr\sap\<SAPSID>\ERS<instance_number>\

Note

The profile is replicated from the global host to the local instance profile folder. The enqueuereplication server instance uses the profile from the local instance profile folder:.\usr\sap\<SAPSID>\ERS<instance_number>\profile\

4. On the additionalMSCS node, start SAPinst to install the enqueue replication server for theASCS instance as described in step 2 above.

Note

There is no need to move the ASCS cluster group to another MSCS node.

5. Enter the required parameter values in the SAPinst dialogs as described above.

7.3.10 Installing the Central Instance

The following describes how to install the central instance for MSCS.You have the following options to install the central instance:

n You install the central instance on an MSCS node.In this case, bring the SAP cluster group online on this node, and make sure that the centralinstance number is different from the (A)SCS instance number.

n You install the central instance on a host outside of MSCS.In this case, you have to install the database client software on this host.

Procedure

1. Run SAPinst [page 47] and choose:<Your SAP product> <SAP technical stack> <Database> High-Availability System Central

Instance2. If SAPinst prompts you to log off, choose OK and log on again.3. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

Note


134/152 PUBLIC 05/25/2009


Caution

n If you install the central instance on an MSCS node, make sure that on the screen SAP System> General Parameters for the:l Profile Directory, you use the UNC path of the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.l Installation Drive, you choose the local disk where you want to install the central instance. Do

not enter the shared disk for the (A)SCS instance.

Note

If the installation drive is not shown and you cannot select it, the saploc share alreadyexists. SAPinst then automatically takes the installation drive to be the drive where thesaploc share points to. Check that the saploc share points to a local drive before youcontinue the installation. Since you already installed the ERS instance on the local driveand the saploc share then points to that local drive, SAPinst automatically takes thatdrive to be the installation drive.

4. Check that the central instance is running.

7.3.11 Installing the Dialog Instance

You have to install at least one dialog instance for MSCS. You have the following options to install thedialog instance:

n You install the dialog instance on an MSCS node.In this case, bring the SAP cluster group online on this node, and make sure that the dialoginstance number is different from the (A)SCS instance number.

n You install the dialog instance on a host outside of MSCS.In this case, you have to install the database client software on this host.

Procedure

1. Run SAPinst [page 47] and choose:<Your SAP product> <SAP technical stack> <Database> High-Availability System Dialog Instance

2. If SAPinst prompts you to log off, choose OK and log on again.3. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

Note


05/25/2009 PUBLIC 135/152

7 High Availability with Microsoft Cluster Service7.4 Post-Installation

Caution

n If you install the dialog instance on an MSCS node, make sure that on the screen SAP System> General Parameters for the:l Profile Directory, you use the UNC path of the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile

l Central instance and dialog instance you enter the same instance number.

l Installation Drive, you choose the local disk where you want to install the dialog instance. Donot enter the shared disk for the (A)SCS instance.

Note

If the installation drive is not shown and you cannot select it, the saploc share alreadyexists. SAPinst then automatically takes the installation drive to be the drive where thesaploc share points to. Check that the saploc share points to a local drive before youcontinue the installation. If it points to the shared drive, delete the saploc share.

4. When you have finished, change the instance profile of the dialog instance so that the number ofits work processes equals the number of work processes of the central instance.

5. If required, install additional dialog instances outside of MSCS.

Caution

Make sure that on the screen SAP System > General Parameters for the Profile Directory, you use the UNCpath of the virtual (A)SCS host name, for example:\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile

7.4 Post-Installation

To complete and check the installation of the SAP system for an MSCS configuration, you need toperform the following steps, which are described in more detail in the linked sections:

1. You start and stop the SAP system in an MSCS configuration [page 136].2. You perform the post-installation checks for the enqueue replication server [page 138].3. If required, you perform the general post-installation steps [page 63] listed in this guide.

7.4.1 Starting and Stopping the SAP System in an MSCSConfiguration

The following describes how to start or stop the SAP system in an MSCS configuration with:

136/152 PUBLIC 05/25/2009


n SAP MMCWith the SAP MMC you can start or stop the complete SAP system or single instances if theyare clustered or not.

n Cluster Administrator (Windows Server 2003) or Failover Cluster Management (Windows Server2008)With the Cluster Administrator or Failover Cluster Management, you can only start or stop clusteredinstances such as the (A)SCS instance or the database instance. For all other instances, such asdialog instances or the central instance, you must use the SAP MMC.

Note

You also use the Cluster Administrator or Failover Cluster Management for all other administrative taskslike moving clustered instances from one MSCS node to the other MSCS node.

Procedure

n To start or stop your SAP system with the SAP MMC, see Starting and Stopping the SAP System [page 97].n Windows Server 2003 only:

To start or stop the clustered (A)SCS instance or the database instance with the ClusterAdministrator do the following:1. Start the Cluster Administrator by choosing Start Control Panel Administrative Tools Cluster

Administrator .2. To start or stop the (A)SCS instance of the SAP cluster group, right-click the relevant cluster

resource SAP <SAPSID> <instance_no> Instance and choose Bring online or Take offline.3. To start or stop the database instance, right-click the database instance <database_resource>

and choose Bring online or Take offline.n Windows Server 2008 only:

To start or stop the clustered (A)SCS instance or the database instance with the Failover ClusterManagement do the following:1. Start the Failover Cluster Management by choosing Start Administrative Tools Failover Cluster

Management .2. To start or stop the (A)SCS instance, select the relevant service and application SAP <SAPSID>.

In the right-hand pane, under Other Resources, right-click the resource SAP <SAPSID><instance_no> Instance and choose Bring this resource online or Take this resource offline.

3. To start or stop the database instance, right-click the database instance <database_resource>and choose Bring this resource online or Take this resource offline.

05/25/2009 PUBLIC 137/152


7.4.2 Post-Installation Checks for Enqueue ReplicationServer

The following sections describe the tests you must perform to check whether the installed enqueuereplication server works properly. For these tests you use the ENQT and ENSMON command linetools, which allow remote access to the enqueue server statistics. Before you can use these toolsyou must copy them to the remote host where the Enqueue Replication Server is running andfrom where you want to start the tests.

Note

Make sure that you have restarted the (A)SCS instance and service cluster resources SAP <SAPSID><(A)SCS_instance_number> Instance and SAP <SAPSID> <(A)SCS_instance_number> Service. You can dothis either with SAPinst while performing the installation, or with the Cluster Administrator (WindowsServer 2003) or Failover Cluster Management (Windows Server 2008).

You perform the following steps:

1. You copy ENQT.exe and ENSMON.exe from your cluster’s binary directory on the sapmnt share\\<host>\sapmnt\<SAPSID>\SYS\exe\<codepage>\<platform> to a directory on the remotehost from where you run the tests.

2. You check the status of the enqueue replication server with the ENSMON tool [page 138].3. You check the fill status and ID of the lock table during failover with the ENQT tool [page 139].

7.4.2.1 Checking the Status of the Enqueue ReplicationServer with ENSMON

You use the ENSMON tool to check if the enqueue replication server and the enqueue server areproperly connected.

Prerequisites

n You have started the (A)SCS instance of your SAP system.n You run the ENSMON tool from the host where you installed the Enqueue Replication Server.

ProcedureTo check the status of the enqueue replication server enter the following command:ensmon pf=<ERS_instance_profile> 2

where <ERS_instance_profile> is the profile created during the installation of the EnqueueReplication Server.

n If the enqueue replication server and the enqueue server are properly connected, the output issimilar to this:

138/152 PUBLIC 05/25/2009


Try to connect to host <Virtual (A)SCS host> service sapdp01 get replinfo request

executed successfully

Replication is enabled in server, repl. server is connected

Replication is active

...

n If the enqueue replication server and the enqueue server are not properly connected, the outputis similar to this:Try to connect to host <Virtual (A)SCS host> service sapdp01 get replinfo request

executed successfully

Replication is enabled in server, but no repl. server is connected

...

7.4.2.2 Monitoring the Lock Table During Failover with ENQT

With the following tests you monitor and check the fill status and the ID of the lock table usingthe ENQT tool.

Prerequisites

n You have started the (A)SCS instance of your SAP system.n You run the ENQT tool from the host where you installed the Enqueue Replication Server.

Caution

Only use the ENQT commands stated in this procedure otherwise you might damage theenqueue server’s lock table.

Monitoring the Lock Table Fill Status During Failover with ENQT

1. Use the following command to fill the lock table of the enqueue server with 20 locks:enqt pf=<ERS_instance_profile> 11 20


2. Monitor the fill status of the lock table with the following command:enqt pf=<ERS_instance_profile> 20 1 1 9999

This command continuously reads the content of the enqueue server’s lock table and returnsthe number of the table entries to the console.

3. Move the (A)SCS cluster group to another MSCS node to simulate an enqueue server failoverwhile running the ENQT command.The output is similar to this:Number of selected entries: 20

05/25/2009 PUBLIC 139/152


Number of selected entries: 20




Number of selected entries: 0 ( enqueue server fails over)Number of selected entries: 20 ( enqueue server is running again)Number of selected entries: 20




...

4. Make sure that the lock count is the same before and after the failover.

Monitoring the Lock Table ID During Failover with ENQT

1. Monitor the lock table ID during the failover with the following command:for /l %i in (1,1,100000) do enqt pf=<ERS_instance_profile> 97


2. Move the (A)SCS cluster group to another MSCS node to simulate an enqueue server failoverwhile running the ENQT command.The output is similar to this:...

(Output before failover)C:\WORK\HA\ENQU-Tests>enqt pf=BUG_ERS01_PCJ2EEV6 97

---REQ----------------------------------------------------------

EnqId: EnqTabCreaTime/RandomNumber = 25.10.2005 11:15:59 1130231759

/ 9288

...

(Output after failover)C:\WORK\HA\ENQU-Tests>enqt pf=BUG_ERS01_PCJ2EEV6 97

---REQ----------------------------------------------------------

EnqId: EnqTabCreaTime/RandomNumber = 25.10.2005 11:15:59 1130231759

/ 9288

...

3. Make sure that the lock table ID (ENQID) is the same before and after the failover.

End of: HA (MSCS)

140/152 PUBLIC 05/25/2009

A Appendix

A Appendix

A.1 Online Information from SAP

More information is available online as follows.

Documentation

Description Internet Address Title

Master Guide for SAPenhancement package 4for SAP ERP 6.0

http://service.sap.com/erp-inst SAPERP 6.0 SAP enhancement packages for SAP ERP6.0 SAP enhancement package 4 for SAP ERP 6.0

Master Guide ‒ SAP EnhancementPackage 4 for SAP ERP 6.0 poweredby SAP NetWeaver

Master Guide for SAP ERP6.0

http://service.sap.com/erp-inst SAPERP 6.0 SAP enhancement packages for SAP ERP6.0 SAP enhancement package 4 for SAP ERP 6.0

Master Guide - SAP ERP 6.0

Master Guide SAPSolution Manager 7.0

http://service.sap.com/instguides SAPComponents SAP Solution Manager Release 7.0

Master Guide ‒ SAP SolutionManager 7.0

Installation of SAPSolution Manager 7.0


Installation Guide ‒ SAP SolutionManager 7.0 on <OS>: <Database>

Configuration of SAPSolution Manager 7.0


Configuration Guide ‒ SAP SolutionManager 7.0 as of <current stack>

Patching of SAPNetWeaver 7.0 scenarios

http://service.sap.com

/maintenanceNW70 SPS <current stack>Support Package Stack Guide ‒ SPS <current stack>

Support Package Stack Guide ‒ SAPNetWeaver 7.0 SPS <current stack>

Upgrade to EHP4 for SAPERP 6.0

http://service.sap.com/erp-inst SAPERP SAP ERP 6.0 SAP enhancement packages forSAP ERP 6.0 SAP enhancement package 4 for SAPERP 6.0

Upgrade Master Guide - SAP ERP6.0

Installation of SAPNetWeaver DeveloperWorkplace


Installation Installation — Clients Installation ‒SAP Developer Workplace

Installation Guide ‒ DeveloperWorkplace for SAP NetWeaver

Installation of SAPNetWeaver DeveloperStudio


Installation Installation — Clients Installation ‒SAP NetWeaver Developer Studio

SAP NetWeaver Developer Studio —Standalone Installation Guide

Installation of the SystemLandscapeDirectory (SLD)


Configuration Post-Installation Guide ‒ SLD of SAPNetWeaver 7.0

Post-Installation Guide ‒ SystemLandscape Directory of SAPNetWeaver 7.0

05/25/2009 PUBLIC 141/152















http://service.sap.com/maintenanceNW70















A AppendixA.1 Online Information from SAP

Description Internet Address Title

Installationof a standalonegateway


Installation ‒ Standalone Engines Installation —Gateway on <platform>

Installation Guide ‒ Gateway on<platform> ‒ For SAP Systems Basedon SAP NetWeaver 7.0 (2004s)

Installation of WebDispatcher


Installation ‒ Standalone Engines Installation—WebDispatcher on <platform>

Installation Guide ‒ Web Dispatcheron <platform> ‒ For SAP SystemsBased on SAP NetWeaver 7.0 (2004s)

Front End installation http://service.sap.com/installNW70

Installation ‒ Clients Installation ‒ SAP Front End<Release>

SAP Front End Installation GuideThis guide is also available onthe Presentation DVD.

Homogeneous andheterogeneous systemcopy for SAP systems basedon NetWeaver 7.0


Installation ‒ SAP NetWeaver Systems System Copyfor SAP Systems Based on <Release> <Technology>

System Copy Guide—System Copy forSAP Systems based on SAPNetWeaver<Release> <Technology>

SAP NetWeaver ProblemAnalysis Guide

http://help.sap.com/nw70 SAP NetWeaver7.0 Library (including Enhancement Package 1) EnglishSAP NetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by KeyCapability SAP NetWeaver Problem Analysis Guide(PAG)

SAP NetWeaver Problem AnalysisGuide (PAG)

General Quick Links

Description Internet Address

SAP Help Portal http://help.sap.com

SAP NetWeaver Library in SAPHelp Portal


SAP ERP Library in SAP HelpPortal

http://help.sap.com/erp

SAP Notes http://service.sap.com/notes

SAP Notes for SAP NetWeaver 7.0installation

http://service.sap.com/sapnotesnw70

Forums, blogs, and generalinformation related to all ofthe supported databases andoperating system platforms


Product AvailabilityMatrix (PAM)for supported operating systemreleases


General information, forums andblogs about information relatedto SAP on Windows

http://sdn.sap.com/irj/sdn/windows

Release notes http://service.sap.com/releasenotes

142/152 PUBLIC 05/25/2009
















http://help.sap.com












http://sdn.sap.com/irj/sdn/windows



A AppendixA.1 Online Information from SAP

Description Internet Address

Unicode SAP systems and theiravailability

http://service.sap.com/unicode

System sizing (Quick Sizer tool) http://service.sap.com/sizing

SAP NetWeaver capabilities http://sdn.sap.com/irj/sdn/netweaver

Life-cycle management for SAPNetWeaver

http://sdn.sap.com/irj/sdn/lcm

Landscape design for SAPNetWeaver

http://sdn.sap.com/irj/sdn/landscapedesign

Application management for SAPNetWeaver

http://sdn.sap.com/irj/sdn/applicationmanagement

High Availability http://sdn.sap.com/irj/sdn/ha

System Landscape Directory http://sdn.sap.com/irj/sdn/nw-sld

Software logistics for SAPNetWeaver

http://sdn.sap.com/irj/sdn/softwarelogistics

SAP NetWeaver operations http://sdn.sap.com/irj/sdn/operations

SAP NetWeaver DevelopmentInfrastructure

http://sdn.sap.com/irj/sdn/nw-di

Security for SAP NetWeaver http://sdn.sap.com/irj/sdn/security

NoteFor information on Windows operating system security, see:http://www.microsoft.com/security

Information on SAP SupportPackage Stacks

http://service.sap.com/sp-stacks

SAP Solution Manager http://service.sap.com/solutionmanager

Maintenance Optimizer http://service.sap.com/solman-mopz

End-to-End Root Cause Analysis http://service.sap.com/diagnostics

05/25/2009 PUBLIC 143/152





http://sdn.sap.com/irj/sdn/netweaver

http://sdn.sap.com/irj/sdn/lcm

http://sdn.sap.com/irj/sdn/landscapedesign

http://sdn.sap.com/irj/sdn/applicationmanagement

http://sdn.sap.com/irj/sdn/ha

http://sdn.sap.com/irj/sdn/nw-sld

http://sdn.sap.com/irj/sdn/softwarelogistics

http://sdn.sap.com/irj/sdn/operations

http://sdn.sap.com/irj/sdn/nw-di

http://sdn.sap.com/irj/sdn/security

http://www.microsoft.com/security

http://www.microsoft.com/security



http://service.sap.com/solutionmanager

http://service.sap.com/solutionmanager



http://service.sap.com/diagnostics

http://service.sap.com/diagnostics

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

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

Example Emphasized words or expressions

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

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

/example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

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

Example n Words or characters quoted from the screen. These include field labels, screen titles,pushbutton labels, menu names, and menu options.

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

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

EXAMPLE Keys on the keyboard

144/152 PUBLIC 05/25/2009

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2009 SAP AG. All rights reserved.

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

05/25/2009 PUBLIC 145/152

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified oraltered in any way.

Legal Software Terms.

Terms for Included Open Source SoftwareThis SAP software contains also the third party open source software products listed below. Note that for these third partyproducts the following special terms and conditions shall apply.

1. This software was developed using ANTLR.

2. SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library(STLport) and its documentation without fee.

B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectualproperty laws, and to all of the terms and conditions of this Agreement.

C) The Customer may distribute binaries compiled with STLport (whether original or modified) without anyroyalties or restrictions.

D) Customer shall maintain the following copyright and permissions notices on STLport sources and itsdocumentation unchanged: Copyright 2001 SAP AG

E) The Customer may distribute original or modified STLport sources, provided that:n The conditions indicated in the above permissions notice are met;n The following copyright notices are retained when present, and conditions provided in accompanying

permission notices are met:Copyright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Companymakes no representations about the suitability of this software for any purpose. It is provided “as is” withoutexpress or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose ishereby granted without fee, provided that the above copyright notice appear in all copies and that both that

146/152 PUBLIC 05/25/2009

copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes norepresentations about the suitability of this software for any purpose. It is provided “as is” without express orimplied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARCmakes no representations about the suitability of this software for any purpose. It is provided “as is” withoutexpress or implied warranty.Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material isprovided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to useor copy this software for any purpose is hereby granted without fee, provided the above notices are retained on allcopies. Permission to modify the code and to distribute modified code is granted, provided the above notices areretained, and a notice that the code was modified is included with the above copyright notice.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. SAP makes no representationsabout the suitability of this software for any purpose. It is provided with a limited warranty and liability as setforth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations onlytowards its customers and only referring to its modifications.

b) Support and MaintenanceSAP does not provide software maintenance for the STLport. Software maintenance of the STLport thereforeshall be not included.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditionsand shall be subject to a separate contract.

c) Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that theSTLport is error-free, without material defects or suitable for a specific application under third-party rights.Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate anyassurance of particular attributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i)can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or(iii) if based on the failure of a guaranteed attribute.

B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerialemployees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shalldepend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract,due to the circumstances known to it at that point in time representing a typical transfer of the software.

C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by adefect or lost profit.

D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceedEUR 5,000.

E) The Customer shall take adequate measures for the protection of data and programs, in particular by makingbackup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data andits recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided byobserving this obligation.

F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employeesor agents of SAP.

3. Adobe Document Services

05/25/2009 PUBLIC 147/152

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States and / or other countries. For information on Third Party software delivered withAdobe document services and Adobe LiveCycle Designer, see SAP Note 854621.

4. Apache License, Version 2.0

a) Definitions:n "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections

1 through 9 of this document.n "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the

License.n "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or

are under common control with that entity. For the purposes of this definition, "control" means (i) the power,direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii)ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

n "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.n "Source" form shall mean the preferred form for making modifications, including but not limited to software

source code, documentation source, and configuration files.n "Object" form shall mean any form resulting frommechanical transformation or translation of a Source form,

including but not limited to compiled object code, generated documentation, and conversions to other mediatypes.

n "Work" shall mean the work of authorship, whether in Source or Object form, made available under theLicense, as indicated by a copyright notice that is included in or attached to the work (an example is providedin the Appendix below).

n "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from)the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, asa whole, an original work of authorship. For the purposes of this License, Derivative Works shall not includeworks that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and DerivativeWorks thereof.

n "Contribution" shall mean any work of authorship, including the original version of the Work and anymodifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensorfor inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit onbehalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic,verbal, or written communication sent to the Licensor or its representatives, including but not limited tocommunication on electronic mailing lists, source code control systems, and issue tracking systems that aremanaged by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excludingcommunication that is conspicuously marked or otherwise designated in writing by the copyright owner as"Not a Contribution."

n "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution hasbeen received by Licensor and subsequently incorporated within the Work.

b) Grant of Copyright LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide,non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of,publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source orObject form.

c) Grant of Patent LicenseSubject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide,non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, havemade, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to thosepatent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or bycombination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institutepatent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a

148/152 PUBLIC 05/25/2009


Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patentlicenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

d) RedistributionYou may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or withoutmodifications, and in Source or Object form, provided that You meet the following conditions:

A) You must give any other recipients of the Work or Derivative Works a copy of this License; and

B) You must cause any modified files to carry prominent notices stating that You changed the files; and

C) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,trademark, and attribution notices from the Source form of the Work, excluding those notices that do notpertain to any part of the Derivative Works; and

D) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distributemust include a readable copy of the attribution notices contained within such NOTICE file, excluding thosenotices that do not pertain to any part of the Derivative Works, in at least one of the following places: withina NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, ifprovided along with the Derivative Works; or, within a display generated by the Derivative Works, if and whereversuch third-party notices normally appear. The contents of the NOTICE file are for informational purposes onlyand do not modify the License. You may add Your own attribution notices within Derivative Works that Youdistribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additionalattribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different licenseterms and conditions for use, reproduction, or distribution of Your modifications, or for any such DerivativeWorks as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with theconditions stated in this License.

e) Submission of ContributionsUnless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You tothe Licensor shall be under the terms and conditions of this License, without any additional terms or conditions.Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreementyou may have executed with Licensor regarding such Contributions.

f) TrademarksThis License does not grant permission to use the trade names, trademarks, service marks, or product names of theLicensor, except as required for reasonable and customary use in describing the origin of the Work and reproducingthe content of the NOTICE file.

g) Disclaimer of WarrantyUnless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor providesits Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, eitherexpress or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT,MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determiningthe appropriateness of using or redistributing the Work and assume any risks associated with Your exercise ofpermissions under this License.

h) Limitation of LiabilityIn no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unlessrequired by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall anyContributor be liable to You for damages, including any direct, indirect, special, incidental, or consequentialdamages of any character arising as a result of this License or out of the use or inability to use the Work (includingbut not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and allother commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

i) Accepting Warranty or Additional Liability

05/25/2009 PUBLIC 149/152

While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptanceof support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, inaccepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf ofany other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for anyliability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty oradditional liability.

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

150/152 PUBLIC 05/25/2009

https://service.sap.com/instguides



SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2009 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

sap ehp4 maxdb windows abap installation guide

Documents