installation guide for system copy for abap + java systems on nw 7.0 for ehp3 on windows on ms sql...

Installation Guide for System CopySAP Systems Based on the Application Server ABAP+Java of SAP NetWeaver 7.0 including EHP3 on Windows: MS SQL ServerTarget System Installation for System Copy

Target Audience System Administrators Technical Consultants

PUBLICDocument version: 1.00 2011-11-08

About this Installation Guide

SAP System Installation

SAP system installations should only be performed by SAP Technical Consultants certified for your

operating system, your database, and the SAP system that you are installing

SAP Installation Tool

You must only use the SAP installation tools according to the instructions and for the purposes

described in the SAP installation document. Improper use of the SAP installation tools can damage files

and systems already installed.

Downward Compatibility of Databases

For downward-compatible releases of DB/OS platforms for SAP products, SAP plans to regularly release

the newest database (DB) and operating-system (OS) versions of SAP products. These releases are

downward-compatible with earlier SAP system releases.

Note that for already shipped SAP components, we only support the installation for database versions

proposed by the installation tool. Therefore, you must install an SAP component or perform a system

copy using a downward-compatible database. That is, you either install the component with the old

proposed database version or you upgrade the old database version to the downward-compatible new

version.

2/158 PUBLIC 2011-11-08

Typographic Conventions

Example Description

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your .

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 the documentation

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 to specific content on the Web

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

Example Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

Cross-references to other documentation or published worksExample Output on the screen following a user action, for example, messages

Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2011-11-08 PUBLIC 3/158
http://www.sap.comhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0

Document History

CAUTION

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

You can find the latest version on SAP Service Marketplace http://service.sap.com/

instguides.

The following table provides an overview on the most important document changes:

Version Date Description

1.00 2011-11-08 Initial Version

4/158 PUBLIC 2011-11-08
http://service.sap.com/instguideshttp://service.sap.com/instguides

Table of Contents

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

1.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2 Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . 13

2.1 Central System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2 Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3 High Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.4 Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.5 Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.2.1 Running the Prerequisite Checker in Standalone Mode

(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2.2 Requirements for a Central System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2.3 Requirements for a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.2.4 Requirements for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.2.5 Requirements for the Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.2.6 Requirements for the Host Agent as a Separate Installation . . . . . . . . . . . . . . . 31

3.3 Planning User and Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.4 Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.5 Domain or Local Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.6 Distribution of SAP System Components to Disks . . . . . . . . . . . . . . . . . . . . . . 43

3.7 SAP Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.2 Disabling the Windows Server 2008 (R2) Firewall . . . . . . . . . . . . . . . . . . . . . . . 48

4.3 Performing Basic Windows Preparation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . 48

2011-11-08 PUBLIC 5/158

4.4 Required User Authorization for Running SAPinst . . . . . . . . . . . . . . . . . . . . . 50

4.5 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4.6 Preparing the SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4.7 Installing the SAP Front-End Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4.8 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.2 Installing the SQL Server Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.3 Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.4 Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.4.1 How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.4.2 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.4.3 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . 65

5.4.4 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.4.5 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.4.6 Entries in the Services File Created by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.4.7 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

6.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

6.2 Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

6.3 Performing the Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

6.4 Providing Access to the NetWeaver Administrator . . . . . . . . . . . . . . . . . . . . . . 76

6.5 Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6.6 Configuring User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6.7 Creating Symbolic Links on Windows Server 2008 (R2) for Application

Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

6.8 Configuring Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . . . . 78

6.9 Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6.10 Configuring the Transport Management System . . . . . . . . . . . . . . . . . . . . . . . 79

6.11 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6.12 Setting Environment Variable CPIC_MAX_CONV . . . . . . . . . . . . . . . . . . . . . 84

6.13 Post-Installation Steps for the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . 84

6.14 Post-Installation Steps for the Host Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6.15 Performing a Full System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

6/158 PUBLIC 2011-11-08

Chapter 7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7.1 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7.2 Performing a Domain Installation Without Being a Domain

Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.3 Database Installation for Multiple Components with MS SQL

Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

7.3.1 Default or Named MS SQL Server Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

7.4 Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . . . 95

7.5 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

7.6 Dialog Instance Installation for an Upgraded System only: Updating

Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

7.7 Installing the Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

7.8 Starting and Stopping the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

7.9 Configuring the Windows Server 2008 (R2) Firewall . . . . . . . . . . . . . . . . . . . . 105

7.10 Implementing Single Sign-On with Microsoft Kerberos SSP for Your SAP

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

7.11 Usage Type-Specific Initial Technical Configuration . . . . . . . . . . . . . . . . . . . 108

7.11.1 Initial Technical Configuration for SAP NetWeaver Application Server Java

(AS Java) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

7.11.1.1 Initial Technical Configuration for Adobe Document Services . . . . . . . . . . . 109

7.11.1.2 Initial Technical Configuration for Composite Application Framework Core

(CAF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

7.11.1.3 Initial Technical Configuration for the System Landscape Directory

(SLD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

7.11.2 Initial Technical Configuration for Process Integration (PI) . . . . . . . . . . . . . . 111

7.11.2.1 Importing the SAP Exchange Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

7.11.2.2 Assigning SAP_ALL Rights to User PISUPER . . . . . . . . . . . . . . . . . . . . . . . . . 112

7.11.2.3 Activating the ICF Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

7.11.2.4 Assigning Roles to Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

7.12 SAP System Security on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

7.13 Automatic Creation of Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . . 116

7.14 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Chapter 8 High Availability with Microsoft Cluster Service . . . . . . . . . . . . . . . . . . 121

8.1 Installation Checklist for a High-Availability System . . . . . . . . . . . . . . . . . . . 123

8.2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

8.2.1 System Configuration in MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

2011-11-08 PUBLIC 7/158

8.2.1.1 SAP System Components in an MSCS Configuration . . . . . . . . . . . . . . . . . . 124

8.2.1.2 Multiple SAP Systems In One MSCS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . 128

8.2.1.3 Multiple SAP Systems In Multiple MSCS Clusters . . . . . . . . . . . . . . . . . . . . . 130

8.2.1.4 Enqueue Replication Server in an MSCS Configuration . . . . . . . . . . . . . . . . . 131

8.2.2 Distribution of SAP System Components to Disks for MSCS . . . . . . . . . . . . . 132

8.2.3 Directories in an MSCS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

8.2.4 IP Addresses in an MSCS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

8.2.5 Obtaining IP Addresses for MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

8.3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

8.3.1 Mapping Host Names to IP Addresses for MSCS . . . . . . . . . . . . . . . . . . . . . . . 139

8.4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

8.4.1 Clustering the SQL Server Database Server Software . . . . . . . . . . . . . . . . . . . 140

8.4.2 Configuring the First Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

8.4.3 Installing the Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

8.4.4 Configuring the Additional Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

8.4.5 Installing the Central Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

8.4.6 Installing the Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

8.5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

8.5.1 Post-Installation Checks for Enqueue Replication Server . . . . . . . . . . . . . . . . 145

8.5.1.1 Checking the Status of the Enqueue Replication Server with

ENSMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

8.5.1.2 Monitoring the Lock Table During Failover with ENQT . . . . . . . . . . . . . . . . 146

8.6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

8.6.1 Moving MSCS Groups or Services and Applications . . . . . . . . . . . . . . . . . . . . 148

8.6.2 Rebooting During the Installation or Conversion for MSCS . . . . . . . . . . . . . 149

8.6.3 Starting and Stopping the SAP System in an MSCS Configuration . . . . . . . . . 149

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

8/158 PUBLIC 2011-11-08

1 Introduction

This document describes how to install an SAP system based on the dual-stack (ABAP+Java)

application server of SAP NetWeaver 7.0 including Enhancement Package 3 using the installation tool

SAPinst.

CAUTION

Make sure you have read the Before You Start [page 10] section before you continue with this

installation guide.

Constraints

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

Your operating system platform must be 64-bit.

Naming Conventions

SAP system refers to SAP system based on the application server of SAP NetWeaver 7.0 including enhancement package 3.

ABAP+Java system refers to SAP system based on the ABAP+Java (dual-stack) application server of SAP NetWeaver 7.0 including Enhancement Package 3.

diagnostics refers to diagnostics in SAP Solution Manager. diagnostics agent refers to the agent of diagnostics in SAP Solution Manager.

Windows Operating System

In this document, Windows Server 2008 (R2) with (R2) written in parentheses means that the

information applies to both Windows Server 2008 and Windows Server 2008 R2.

SQL Server 2008 Terminology

In this document, SQL Server 2008 (R2) with (R2) written in parentheses means that the

information applies to both SQL Server 2008 and SQL Server 2008 R2.

Profiling for High Availability

Only valid for: HA (MSCS) |

The profile bars with the wording Only valid for: HA (MSCS) for example, as in this section refer to

content that is only valid if you are installing a high-availability (HA) system with Windows Server

Failover Clustering. The Windows cluster feature was previously called Microsoft Cluster Service

(MSCS). For practical reasons we are continuing to use the abbreviation MSCS in this guide.End of: HA (MSCS) |

1 Introduction

2011-11-08 PUBLIC 9/158

1.1 Before You Start

Make sure you have read the Master Guide for your SAP Business Suite application or SAP NetWeaver

application before you continue with this installation guide.

The Master Guide is the central document leading you through the overall implementation process

for you SAP system installation. It contains crucial information about the overall implementation

sequence, that is activities you have to perform before and after the installation process described in

this installation guide.

You can find a printed version of the Master Guide in your installation package or you can download

the latest version from SAP Service Marketplace.

The following table lists the Master Guides of the SAP system applications for which you can use this

installation guide, along with the available quick link or path to the appropriate download location

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

Title Internet Address

Master Guide - SAP Enhancement Package 6 for SAP ERP 6.0 powered by SAP NetWeaver

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

Master Guide (Including Upgrade Information) - SAP Supplier Relationship Management 7.0 Including SAP Enhancement Package 2

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

Master Guide (Including Upgrade Information) - SAP Customer Relationship Management 7.0 Including SAP Enhancement Package 2

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

Master Guide SAP Supply Chain Management 7.0 Including SAP Enhancement Package 2 Powered by SAP NetWeaver

http://service.sap.com/instguides SAP Business Suite Applications SAP SCM

1.2 New Features

The table below provides an overview of the new features related to the installation.

Make sure that you also read the release notes at http://service.sap.com/releasenotes.

Area Description

SAPinst You no longer require a Solution Manager Key for the installation.

The SAP Cryptographic Library SAPCRYPTO.SAR is now available in the DBINDEP subfolder of the UC Kernel (folder K__U_) medium and installed automatically by SAPinst. You do not have to separately download SAPCRYPTO.SAR any longer.For more information, see Basic SAP System Installation Parameters [page 34].

Virtual Machine Container (VM Container)

The VM Container includes a Java Development Kit (JDK) provided and supported by SAP. The VM Container Java VM is fully compliant to the Java Platform Standard Edition (JDK) 6. It is

1 Introduction

1.1 Before You Start

10/158 PUBLIC 2011-11-08
http://service.sap.com/instguideshttp://service.sap.com/erp-insthttp://service.sap.com/srm-insthttp://service.sap.com/crm-insthttp://service.sap.com/instguideshttp://service.sap.com/releasenotes

Area Descriptioninstalled automatically by SAPinst with the ABAP kernel executables.

SAP Java Virtual Machine (SAP JVM) You no longer have to download and install a Java Development Kit (JDK) from another software vendor as a prerequisite for the installation with SAPinst.The SAP JVM 4 is a Java Development Kit (JDK) provided and supported by SAP. The SAP JVM is fully compliant to the Java Platform Standard Edition (JDK) 1.4. It is available on the Installation Master DVD and is installed automatically by SAPinst when you start the installation.The diagnostics agent is installed automatically with SAP JVM 6.

1.3 SAP Notes for the Installation

You must read the following SAP Notes before you start the installation. These SAP Notes contain

the most 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

at:

http://service.sap.com/notes

SAP Notes for the Installation

SAP Note Number Title Description

1565346 SAP NetWeaver 7.03/Business Suite 7i2011: Windows

Windows-specific information about the SAP system installation and corrections to this documentation.

1565347 SAP NetWeaver 7.03/Business Suite 7i2011: SQL Server

MS SQL Server-specific information about the SAP system installation and corrections to this documentation

1144737 Inst. NetWeaver 7.0 EHP3 - Diagnostics Agent installation

Problems discovered after the publication of the installation guide or post-installation steps

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

73606 Supported Languages and Code Pages

Information on possible languages and language combinations in SAP systems

1067221 Central Note for Heterogeneous Installation

This SAP Note and its related SAP Notes describe the released operating system and database combinations for heterogeneous SAP systems landscapes.

Only valid for: SAP NetWeaver |

789220End of: SAP NetWeaver |


Support Package level for NetWeaver Installations/UpgradesEnd of: SAP NetWeaver |


Information about the ABAP Support Package levels and kernel patch levels contained in the current SAP NetWeaver release.End of: SAP NetWeaver |

1 Introduction


2011-11-08 PUBLIC 11/158
http://service.sap.com/noteshttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1565346&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1565347&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1144737&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=855498&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=73606&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067221&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=789220&_NLANG=en&_NVERS=0

SAP Note Number Title DescriptionOnly valid for: SAP ERP |

1258912End of: SAP ERP |

Only valid for: SAP ERP |

PLM Core 7.00 Release Notes and InformationEnd of: SAP ERP |


Information and references to other notes about installing PLM Core 7.00 and importing PLM Core 7.00 Support Packages.End of: SAP ERP |

Only valid for: SAP SCM |

915367End of: SAP SCM |


TDL: Automatic activation of the transaction data areasEnd of: SAP SCM |


Information about a TDL function and the settings you have to make during a system setup.End of: SAP SCM |


1178483End of: SAP SCM |


SNC 7.0 Order Documents: Required CustomizingEnd of: SAP SCM |


Information about Supply Network Collaboration order documents.End of: SAP SCM |

1 Introduction


12/158 PUBLIC 2011-11-08
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1258912&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=915367&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1178483&_NLANG=en&_NVERS=0

2 Installation Options Covered by this Guide

This section shows the installation options covered by this guide. You have to decide what exactly you

want to install because the steps you have to perform vary according to the installation option you

choose.

Central system [page 13] Distributed system [page 14] Only valid for: HA (MSCS) |

High-availability system [page 15]End of: HA (MSCS) |

You can install dialog instances [page 15] to an existing system. You can install a host agent [page 17] separately.

2.1 Central System

You can install a central system on a single host.

These are the following instances:

Central services instance for Java (SCS instance) Database instance (DB instance)

The ABAP stack and the Java stack use their own database schema in the same database

Central instanceAdditionally you can install one or more dialog instances. For more information, see Dialog Instance

[page 15].

The following figure shows an example of SAP instances in a central system.


2.1 Central System

2011-11-08 PUBLIC 13/158

Figure 1: Central ABAP+Java System

2.2 Distributed System

In a distributed system, every instance can run on a separate host.

These are the following instances:

Central services instance for Java (SCS instance) Database instance (DB instance)

The ABAP stack and the Java stack use their own database schema in the same database

Central instanceOptionally you can install one or more dialog instances. For more information, see Installation of a Dialog

Instance [page 15].


2.2 Distributed System

14/158 PUBLIC 2011-11-08

Figure 2: Distributed ABAP+Java System


2.3 High Availability System

For more information about the system components you have to install and how to distribute them

on the specific hosts, see System Configuration in MSCS [page 124].End of: HA (MSCS) |

2.4 Dialog Instance

You can install one or more dialog instances for an existing SAP system. Dialog instances are optional

and can be installed on separate hosts. You can have one or more dialog instances.

A dialog instance can run on:

The host of any instance of the existing SAP system On a dedicated host

NOTE

We do not recommend installing dialog instances on the SAP global host.

If you want to install a dialog instance on an existing SAP system, you must perform a domain

installation. You must also make sure that your existing SAP system was installed as a domain

installation. For more information, see Domain or Local Installation [page 42].


2.3 High Availability System

2011-11-08 PUBLIC 15/158

NOTE

If you install a dialog instance in an existing non-Unicode system (that has been upgraded to the

current release), the dialog instance is automatically installed as a non-Unicode instance. SAPinst

determines if a non-Unicode system exists and chooses the correct executables for the system

type.

Dialog Instance for a Central System

The following figure shows dialog instances that are running on dedicated hosts.

Figure 3: Dialog Instance for a Central System

For more information, see Central System [page 13].

Dialog Instance for a Distributed System

The following figure shows dialog instances that are running on dedicated hosts.


2.4 Dialog Instance

16/158 PUBLIC 2011-11-08

Figure 4: Dialog Instance for a Distributed System

For more information, see Distributed System [page 14].


Dialog Instance for a High-Availability System

In a high-availability system, you require at least one dialog instance apart from the central instance.

For more information about how to install and distribute the application servers in an MSCS

configuration, see System Configuration in MSCS [page 124].End of: HA (MSCS) |

2.5 Host Agent as a Separate Installation

Using the host agent you can centrally monitor any host with the Alert Monitor or the SAP NetWeaver

Administrator or the Adaptive Computing Controller (ACC). In addition, the host agent is used by

the ACC for starting, stopping, and relocating SAP instances and databases.

The host agent is automatically installed during the installation of all new SAP system instances based

on SAP NetWeaver 7.0 including Enhancement Package 2 or higher. You only need to install a host

agent separately in the following cases:

You want to manage a host that does not have an SAP instance or component. You have upgraded your SAP system to SAP NetWeaver 7.0 including Enhancement Package 2 or

higher.

The section Installing the Host Agent Separately [page 102] describes how to perform the installation.


2.5 Host Agent as a Separate Installation

2011-11-08 PUBLIC 17/158

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

3 Planning

3.1 Planning Checklist

This section includes the planning steps that you have to perform for the following installation options:

Central, distributed, or high-availability system Dialog instanceDetailed information about the steps is available in the relevant chapter.

Prerequisites

1. You have planned your SAP system landscape according to the process sequence in the Master

Guide.

2. You have decided on your installation option [page 13].

Central, Distributed, or High-Availability System

NOTE

In a central system, all mandatory instances are installed on one host. Therefore, if you are

installing a central system, you can ignore references to other hosts.

1. You check the hardware and software requirements [page 20] on each host.

2. You plan how to set up user and access management [page 33].

3. You identify basic SAP system installation parameters [page 34].

4. You decide whether you want to perform a domain or local installation [page 42].

5. For the database installation, you decide how to distribute your database components to disk [page 43].

6. You decide on the transport host to use [page 46].

7. Only valid for: HA (MSCS) |

To install a high-availability system with Microsoft Cluster Service (MSCS), you perform the

MSCS-specific planning steps [page 123].End of: HA (MSCS) |

8. You can continue with Preparation [page 47].

Dialog Instance

1. You check the hardware and software requirements [page 20] for the installation host on which you want

to install one or more dialog instances.

2. You identify basic SAP system installation parameters [page 34].

3. You can now continue with Preparation [page 47].

3 Planning

3.1 Planning Checklist

2011-11-08 PUBLIC 19/158

3.2 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating system

and the SAP instances.

CAUTION

If your hosts do not fully meet the requirements, you might experience problems when working

with the SAP system.

Prerequisites

Make sure that the host name meets the requirements listed in SAP Note 611361.

Process Flow

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

system releases.

2. Check the hardware and software requirements using:

The Prerequisite Checker in one of two modes: Standalone mode (optional) before the installation process

For more information, see Running the Prerequisite Checker Standalone [page 21].

Integrated in SAPinst (mandatory) during the installation processFor more information, see Running SAPinst [page 58].

NOTE

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

The hardware and software requirements checklists for: Central system [page 21] Distributed system [page 24] Only valid for: HA (MSCS) |

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

Dialog instance [page 31] Host agent as a separate installation [page 31]

3. If you want to install a production system, the values provided by the Prerequisite Checker and

the hardware and software requirements checklists are not sufficient. In addition, do the following:

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 the Master Guide

SAP NetWeaver 7.0 at http://service.sap.com/installnw70 Planning .

You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing depending on:

The set of applications to be deployed How intensively the applications are to be used

3 Planning


20/158 PUBLIC 2011-11-08
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=611361&_NLANG=en&_NVERS=0http://service.sap.com/pamhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=855498&_NLANG=en&_NVERS=0http://service.sap.com/sizinghttp://service.sap.com/installnw70

The number of users

3.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 the

hardware 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

the hardware and software requirements in the background.

Prerequisites

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

Procedure

1. You start SAPinst [page 58].

2. On the Welcome screen, choose 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 and

choose F1 in SAPinst.

When you have finished, the Parameter Summary screen appears summarizing all parameters you have

entered and want to have checked. If you want to make a change, select the relevant parameters

and choose Revise.

4. To start the prerequisites check, choose Next.

Result

The Prerequisite Checker Results screen displays the results found. If required, you can also check the results

in file prerequisite_checker_results.html, which you can find in the installation directory.

3.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 meet the

following requirements:

3 Planning


2011-11-08 PUBLIC 21/158

NOTE

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

For up-to-date information on the released and supported operating system and database versions for your SAP product and database, see the Product Availability Matrix (PAM) at

http://service.sap.com/pam .

Hardware Requirements for a Central System

Hardware Requirement Requirement How to Check

Minimum disk space Database Software:4 GB

SAP system files (not including paging file):5 GB (x64)8 GB (IA64)

SAP database files (not including paging file):Only valid for: SAP NetWeaver |

20 GBEnd of: SAP NetWeaver |


50 GBEnd of: SAP ERP |


22 GBEnd of: SAP SCM |

Only valid for: SAP SRM |

34 GBEnd of: SAP SRM |

Only valid for: SAP CRM;SAP Solution Manager |

33 GBEnd of: SAP CRM;SAP Solution Manager |

Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SCM;SAP SRM |

Up to 2 GB for each usage type or software unit you want to install.End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SCM;SAP SRM |

4.3 GB of temporary disk space for every required installation medium that you have to copy to a local hard disk

To check disk space:1. Choose Start All Programs

Administrative Tools StorageComputer Management Disk

Management .2. Right-click the drive and choose

Properties.

Minimum RAM 6 GB To check RAM:Choose Start Control Panel System .

NOTE

Windows Server 2008 R2:If System is not visible, change View by: from Category into Large icons.

3 Planning


22/158 PUBLIC 2011-11-08
http://service.sap.com/pam


Paging file size For more information, see SAP Note 1518419.

To check paging file size:1. Choose Start Control Panel

System .

NOTE


2. Choose Advanced system settings.3. In section Performance, select Settings...

Advanced .4. If required, in section Virtual memory,

choose Change.

NOTE

Do not select Automatically managed paging file size for all drives.

Processing Units The number or physical or virtual processing units usable by the operating system image must be equal or greater than 2 for application server instances and database instances.Examples for processing units are Processor Cores or Hardware Threads (Multithreading).In a virtualized environment you must take care that adequate processor resources are available to support the workloads of the running SAP systems.

Suitable backup system -

Software Requirements for a Central System

Software Requirement Requirement How to Check

Windows operating system

64-bit version of one of the following Windows Server Editions: Windows Server 2008 (R2)

Standard Edition Windows Server 2008 (R2)

Enterprise Edition Windows Server 2008 (R2)

Datacenter Edition Windows Server 2008 (R2) for

Itanium-Based Systems Edition

CAUTION

Make sure that you install the English language pack so that

To check your Windows version:1. Choose Start All Programs

Accessories Command Prompt2. Enter the command winver

3 Planning


2011-11-08 PUBLIC 23/158
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1518419&_NLANG=en&_NVERS=0

Software Requirement Requirement How to Checkyour support requests can be handled quickly.

For any version of Windows Server, you need the latest supported service pack

Database software SQL Server 2008 (R2) Enterprise Edition: Server Software

Latest service pack and hotfix or cumulative update, if availableFor more information, see SAP Note 62988.

Unicode collation SQL_Latin1_General_CP850_BIN2

3.2.3 Requirements for a Distributed System

This section provides information about the hardware and software requirements in a distributed

system, where the SAP instances can reside on different hosts.

The tables show the requirements for the:

Central services instance Database instance Central instance Dialog instance (optional)

NOTE


If you install several SAP instances on one host, you need to add up the requirements. For up-to-date information on the released and supported operating system versions for your

SAP product and database, see the Product Availability Matrix (PAM) at http://

service.sap.com/pam.

Hardware Requirements for a Distributed System


Minimum disk space Database software:4 GB

Central services instance (SCS) (not including paging file):5 GB (x64)8 GB (IA64)

Database instance (not including paging file):



Management .2. Right-click the drive and choose

Properties.

3 Planning


24/158 PUBLIC 2011-11-08
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=62988&_NLANG=en&_NVERS=0http://service.sap.com/pamhttp://service.sap.com/pam

Hardware Requirement Requirement How to CheckOnly valid for: SAP NetWeaver |








Only valid for: SAP CRM;SAP Solution Manager |

33 GBEnd of: SAP CRM;SAP Solution Manager |

Central instance (not including paging file):5 GB (x64)8 GB (IA64) In addition you require 4 GB

(x64), or 8 GB (IA64) per additional platform.

In addition you require 1.5 GB for the diagnostics agent

Up to 2 GB for each usage type or software unit you want to install.

Dialog instance (optional) (not including paging file):2.5 GB (x64)5 GB (IA64)In addition you require 1.5 GB for the diagnostics agent

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


NOTE


Paging file size For more information, see SAP Note 1518419.


System .

3 Planning


2011-11-08 PUBLIC 25/158

Hardware Requirement Requirement How to CheckNOTE




choose Change.

NOTE


Processing Units The number or physical or virtual processing units usable by the operating system image must be equal or greater than 2 for application server instances and database instances.Examples for processing units are Processor Cores or Hardware Threads (Multithreading).In a virtualized environment you must take care that adequate processor resources are available to support the workloads of the running SAP systems.

Suitable backup system

Software Requirements for a Distributed System



64-bit version of one of the following Windows Server Editions: Windows Server 2008 (R2) Standard Edition Windows Server 2008 (R2) Enterprise Edition Windows Server 2008 (R2) Datacenter Edition Windows Server 2008 (R2) for Itanium-Based

Systems Edition

CAUTION

Make sure that you install the English language pack so that your support requests can be handled quickly.


To check your Windows version:1. Choose Start All

Programs AccessoriesCommand Prompt

2. Enter the command winver

Database software Central services instance (SCS), central instance or dialog instance: SQL Server 2008 (R2) Native Access Client

(SNAC) software

3 Planning


26/158 PUBLIC 2011-11-08


Latest service pack and hotfix, or cumulative update if available.For more information, see SAP Note 62988.

Database instance: SQL Server 2008 (R2) Enterprise Edition: Server

Software Latest service pack and hotfix, if available.

For more information, see SAP Note 62988.



3.2.4 Requirements for a High-Availability System

General Requirements

Check that your cluster hardware is certified for Windows Server 2008 (R2) and has the Windows Server 2008 (R2) logo.

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 Validation

Report must not show any warnings and errors.

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

resources in the local area network (LAN).

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 on

the state of the MSCS nodes so that the failure of resources is quickly detected.

Each of the MSCS nodes in the cluster must have its own local disks and have access to shared disks that can be reached by the MSCS nodes via a shared bus.

All software except the Windows operating system, the MS SQL server binaries, and the MSCS

software is stored on the shared disks.

One of the shared disks must be used exclusively by the quorum (if a single quorum device cluster

is used) that stores the cluster registry and records information about the state of the cluster.

You require at least four shared disks.

For more information about the distribution of components to local and shared disk, see Distribution

of SAP System Components to Disks for MSCS [page 132].

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

CAUTION

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

3 Planning


2011-11-08 PUBLIC 27/158
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=62988&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=62988&_NLANG=en&_NVERS=0

Hardware and Software Requirements

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

Central services instance for ABAP (ASCS) Central services instance (SCS) Database instance Enqueue Replication Server instance (ERS) Central instance Dialog instance Diagnostics agent

NOTE


If you install several SAP instances on one host, you need to add up the requirements. If you install multiple SAP systems in one MS cluster, make sure that together with your

hardware partner you have set up the correct sizing for your system configuration.

For up-to-date information on the released and supported operating system versions for your SAP product and database, see the Product Availability Matrix (PAM) at http://

service.sap.com/pam.

Hardware Requirements for a High-Availability System


Minimum disk space Database Software:4 GB

Central services instance for ABAP (ASCS)(not including paging file):5 GB (x64)8 GB (IA64) In addition you require 4 GB



Central services instance (SCS)(not including paging file):5 GB (x64)8 GB (IA64)

Database instance (not including paging file):Only valid for: SAP NetWeaver |




Management .2. Right-click the disk and choose

Properties.

3 Planning


28/158 PUBLIC 2011-11-08
http://service.sap.com/pamhttp://service.sap.com/pam

Hardware Requirement Requirement How to CheckOnly valid for: SAP ERP |






Only valid for: SAP CRM |

32 GBEnd of: SAP CRM |

Enqueue replication server instance (ERS) (not including paging file):5 GB (x64)8 GB (IA64)

Central instance (not including paging file):2.5 GB (x64)5 GB (IA64) In addition you require 4 GB


In addition you require 1.5 GB for the diagnostics agent


Dialog instance (not including paging file):2.5 GB (x64)5 GB (IA64)In addition you require 1.5 GB for the diagnostics agent



NOTE


Paging file size For more information, see SAP Note 1518419


System .

3 Planning


2011-11-08 PUBLIC 29/158

Hardware Requirement Requirement How to CheckNOTE




choose Change.

NOTE


You must adjust the size of the paging file on all MSCS nodes.

Processing Units For an ASCS instance and SCS instance running on a separate host, 1 physical or virtual processing units usable by the operating system image might be sufficient.Examples for processing units are Processor Cores or Hardware Threads (Multithreading).In a virtualized environment you must take care that adequate processor resources are available to support the workloads of the running SAP systems.


Software Requirements for a High Availability System







CAUTION



Accessories Command Prompt2. Enter the command winver

NOTE

You must add the operating system feature Failover Clustering on all MSCS nodes.

3 Planning


30/158 PUBLIC 2011-11-08



Database software Central services instance for ABAP (ASCS), central services instance (SCS), central instance, or dialog instance: SQL Server 2008 (R2) Native

Access Client (SNAC) software Latest service pack and hotfix,

or cumulative update, if available.For more information, see SAP Note 62988.

Database instance: SQL Server 2008 (R2)

Enterprise Edition: Server Software Latest service pack and

hotfix, if available.For more information, see SAP Note 62988.


End of: HA (MSCS) |

3.2.5 Requirements for the Dialog Instance

For more information about the hardware and software requirements for the dialog instance, see one

of the following sections:

Requirements for a Distributed System [page 24] Only valid for: HA (MSCS) |

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

3.2.6 Requirements for the Host Agent as a Separate Installation

If you want to install the host agent separately, the installation host has to meet the following hardware

and software requirements:

3 Planning


2011-11-08 PUBLIC 31/158
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=62988&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=62988&_NLANG=en&_NVERS=0

CAUTION

For up-to-date information on the released and supported operating system versions for your

SAP product and database, see the Product Availability Matrix (PAM) at:

http://service.sap.com/pam

Hardware Requirements for the Host Agent


Minimum disk space: Host agent:80 MB




Management .2. Right-click the disk and choose

Properties.

Minimum RAM: 40 MB To check RAM:Choose Start Control Panel System .

NOTE


Paging file size: For more information, see SAP Note 1518419.


System .

NOTE




choose Change.

NOTE


Processing Units The number or physical or virtual processing units usable by the operating system image must be equal or greater than 2. Examples for processing units are Processor Cores or Hardware Threads (Multithreading).In a virtualized environment you must take care that adequate processor resources are available to support the workloads of the running SAP systems.

3 Planning


32/158 PUBLIC 2011-11-08
http://service.sap.com/pamhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1518419&_NLANG=en&_NVERS=0



Software Requirements for the Host Agent


Windows operating system:


Standard Edition Windows Server 2008 (R2)




CAUTION




Accessories Command Prompt .2. Enter the command winver.

Database software:

3.3 Planning User and Access Management

You have to plan how you want to configure user and access management for your SAP system to be

installed.

Before you add a newly installed SAP system to your system landscape, you must decide which kind

of user management you want to use:

Use AS ABAP. Use an LDAP directory as the data source for user data.

Procedure

Using AS ABAP

You install your SAP system as described in this installation guide. During the installation, the SAP

system is automatically configured to use AS ABAP as data source for the User Management Engine

(UME). After the installation has finished, you can still change the user management configuration.

For more information, see Configuring User Management [page 77].

3 Planning

3.3 Planning User and Access Management

2011-11-08 PUBLIC 33/158

Using an LDAP directory as Source for User Data

1. You install your SAP system as described in this installation guide.

2. Configure the user management of the newly installed SAP system to use and LDAP directory.

For more information, see Configuring User Management [page 77].

More Information

For more information about configuring the user management of your SAP system to be installed, see

the SAP Library at:

http://help.sap.com/nw703 Application Help SAP LIbrary: English SAP NetWeaver Library SAP

NetWeaver by Key Capability Security Identity Management Identity Management for System Landscapes

Integration of User Management in Your System Landscape

3.4 Basic SAP System Installation Parameters

SAPinst prompts for input parameters during the Define Parameters phase of the installation.

You can install your SAP system either in Typical or Custom mode:

TypicalIf you choose Typical, you perform the installation with default settings. This means that you only

have to respond to a small selection of prompts including at least the following, which are described

in the corresponding tables below:

SAP System ID and Database Connectivity Parameters SAP system profile directory only for systems with instances on separate hosts Master password System Landscape Directory (SLD) destinationIf you want to change any of the default settings, you can do so on the Parameter Summary screen.

CustomIf you choose Custom, you are prompted for all parameters. At the end, you can still change any of

these parameters on the Parameter Summary screen.

NOTE

You cannot change from Custom to Typical mode or from Typical to Custom mode on the Parameter

Summary screen.

The following tables list the basic system parameters that you need to specify before installing your

SAP system:

SAP System Parameters SAP System Database Parameters Diagnostics Agent ParametersFor all other installation parameters, use the F1 help in the SAPinst screens.

3 Planning


34/158 PUBLIC 2011-11-08
http://help.sap.com/nw703

SAP System Parameters

Parameters Description

SAP System ID

The SAP System ID identifies the whole SAP system.

CAUTION

Choose your SAP system ID carefully. You cannot change the SAP system ID after the installation.

Make sure that your SAP system ID: Is unique throughout your organization. Do not use an existing when

installing a new SAP system.

EXAMPLE

If you have already installed an ABAP system and you want to install a new Java system on the same host, make sure that you enter a that is different from the of the existing ABAP system.

Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs:

ADD ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID

IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW

REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR

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

SAP System Instance Numbers

Technical identifier for internal processes. It consists of a two-digit number from 00 to 97.The instance number must be unique on a host. That is, if more than one SAP instance is running on the same host, these instances must be assigned different numbers.If you do not enter a specific value, the instance number is set automatically to the next free and valid instance number that has not yet been assigned to the SAP system to be installed or to SAP systems that already exist on the installation host.To find out the instance numbers of SAP systems that already exist on the installation host, look for subdirectories ending with of local \usr\sap\ directories.The value is the number assigned to the instance.For more information, see SAP Directories [page 87].

CAUTION

Do not use 43, and 89 for the instance number because: 43 is part of the port number for MSCS 89 is part of the port number for Windows Terminal Server

Master Password Common password for all users created during the installation:

NOTE

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

Password policyThe master password: Must be 8 to 14 characters long Must contain at least one letter in uppercase (A-Z) Must contain at least one letter in lowercase (a-z) Must contain at least one digit (0-9)

3 Planning


2011-11-08 PUBLIC 35/158


Must not contain \ (backslash) and " (double quote)Depending on the installation option, additional restrictions might apply (for example, the master password must not contain the name of a Java user created during the installation).

Message Server Port

CAUTION

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 server ports. The default profile contains the configuration for both message server ports.The external message server port uses the parameter rdisp/msserv with default value 36, where is the instance number of the ABAP message server instance.The internal message server port uses the parameter rdisp/msserv_internal with default value 39, where is the instance number of the ABAP message server instance.Java Message Server PortThe Java message server only uses the internal message server port. The SCS instance profile contains the configuration for the Java message server.The parameter rdisp/msserv is set to 0, so that the external port is not open.The internal message server port uses the parameter rdisp/msserv_internal with default value 39, where is the instance number of the SCS message server instance.For more information about the parameters used for message server ports, see SAP Note 821875.

Key Phrase for Secure Store Settings

This is a random word or phrase that is used to encrypt the secure store.The Java EE engine uses this phrase to generate the key that is used to encrypt the data.The uniqueness of the phrase you use contributes to the uniqueness of the resulting key.

RECOMMENDATION

Use a long key phrase that cannot be guessed easily. Use both uppercase and lowercase letters in the phrase and include special characters.

NOTE

If you choose Typical mode, SAPinst sets the master password for the key phrase. In this case, make sure that you replace the master password with the required unique key phrase either in the Parameter Summary screen or after the installation has finished.

DNS Domain Name for SAP System

If you want to use HTTP-based URL frameworks such as Web Dynpro applications, you have to specify the DNS domain name for the SAP system.The DNS Domain Name is used to calculate the Fully Qualified Domain Name (FQDN), which is configured in profile parameter SAPLOCALHOSTFULL. FQDN is the fully qualified domain name for an IP address. It consists of the host name and the domain name:.

The DNS Domain Name is needed to define the URLs for the ABAP and Java application servers. It is appended to the server name to calculate the FQDN.

EXAMPLE

If your application server host is called kirk.wdf.sap.com, the DNS Domain Name is wdf.sap.com.

3 Planning


36/158 PUBLIC 2011-11-08


Path to SAPCRYPTO.SAR

The SAP Cryptographic Library is required to enable Secure Sockets Layer (SSL) encryption of HTTP connections. In most cases it is installed automatically from the kernel medium. In case it is not installed automatically and you are prompted for it during the installation, you can download it as described in SAP Note 455033.This software product is subject to export control regulations in Germany as the country of origin and import regulations of your own country. SAP may not yet have a corresponding export license for your user or company. Contact the contract department in your local SAP company. To download the SAP Cryptographic Software from the SAP Service Marketplace, you need a customer user ID. Before any transfer of these software products to persons, companies or other organizations outside your company, in particular in the case of any re-export of the software products, authorization is required from the German export control authorities. This might also be required from your responsible national export control authorities. This also applies to transfers to affiliated companies. Corresponding laws and regulations in the recipient country may also exist which restrict the import or the use of these software products.

Password of Operating System Users

The passwords of the operating system users must comply with the Windows password policy. SAPinst processes the passwords of operating system users as follows: If the operating system users do not exist, SAPinst creates the following users:

admThis user is the SAP system administrator user and is a member of the local Administrators group.

SAPServiceThis user is the Windows account to run the SAP system and is not a member of the local Administrators group.

sapadmThe host agent user sapadm is used for central monitoring services. SAPinst creates this user by default as a local user without being a member of the local Administrators group.If required, you can change this user to become a domain user on the parameter summary screen. For more information, see Performing a Domain Installation Without Being a Domain Administrator [page 91]. For security reasons, however, SAP strongly recommends to create this user as a local user.

admThis user is dedicated to the diagnostics agent installation with sufficient authorization to manage the agent. It is created on the central instance host and on every dialog instance host.SAPinst creates this user by default as a local user. If required, you can change this user to become a domain user on the parameter summary screen. For security reasons, however, SAP strongly recommends to create this user as a local user.

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

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

NOTE

This does not apply if the adm user already exists. SAPinst prompts you for the password even if the password of this user is the same as the master password.

3 Planning


2011-11-08 PUBLIC 37/158

Parameters DescriptionCAUTION

Make sure that you have the required user authorization [page 50] for these accounts before you start the installation with SAPinst.

Java Administrator User and Password

This user has administrative permissions for user management.After the installation, this user is available both in the ABAP and in the Java systemSAPinst sets the user name J2EE_ADMIN and the master password by default.For more information about supported UME data sources and change options, see SAP Note 718383.

Java Guest User and Password

This user is used for anonymous access.After the installation, it is available both in the ABAP and in the Java systemSAPinst sets the user name J2EE_GUEST and the master password by default.For more information about supported UME data sources and change options, see SAP Note 718383.

Communication User and Password

This user is used for the communication between the ABAP system and the Java system.After the installation, it is available both in the ABAP and in the Java systemSAPinst sets the user name SAPJSF and the master password by default.For more information about supported UME data sources and change options, see SAP Note 718383.

SDM Password This user is used for the Software Deployment Manager (SDM).SAPinst sets the master password by default.

Integration Repository Service User and Password

SAPinst sets the user name PIREPUSER and the master password by default.If required, you can choose another user name and password according to your requirements.

NOTE

If you want to choose another user name, make sure that this user name starts with PI.

Integration Directory Service User and Password

SAPinst sets the user name PIDIRUSER and the master password by default.If required, you can choose another user name and password according to your requirements.

NOTE


Landscape Directory Service User and Password

SAPinst sets the user name PILDUSER and the master password by default.If required, you can choose another user name and password according to your requirements.

NOTE


Integration Server Application User and Password

SAPinst sets the user name PIAPPLUSER and the master password by default.If required, you can choose another user name and password according to your requirements.

NOTE


Runtime Workbench

SAPinst sets the user name PIRWBUSER and the master password by default.If required, you can choose another user name and password according to your requirements.

3 Planning


38/158 PUBLIC 2011-11-08
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=718383&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=718383&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=718383&_NLANG=en&_NVERS=0

Parameters DescriptionService User and Password

NOTE


Adapter Framework Server Service User and Password

SAPinst sets the user name PIAFUSER and the master password by default.If required, you can choose another user name and password according to your requirements.

NOTE


Integration Server Service User and Password

SAPinst sets the user name PIISUSER and the master password by default.If required, you can choose another user name and password according to your requirements.

NOTE


Management Server Service User and Password

SAPinst sets the user name PILSADMIN and the master password by default.If required, you can choose another user name and password according to your requirements.

NOTE


Exchange Infrastructure Administrator and Password

This user has extensive authorizations.SAPinst sets the user name PISUPER and the master password by default.If required, you can choose another user name and password according to your requirements.

NOTE


Exchange Infrastructure Communicator and Password

SAPinst sets the user name PI_JCD_RFC and the master password by default.If required, you can choose another user name and password according to your requirements.

NOTE


SLD Destination The System Landscape Directory (SLD) is designed for registering the systems (along with the installed software) of your whole system landscape. The usual case is to configure one SLD for your complete system landscape.You can choose between the following options: Register in existing central SLD

Choose this option to register the SAP system you are installing in an existing SAP System Landscape Directory (SLD) by specifying the SLD connection parameters listed below in this table.

Configure a local SLDChoose this option if you want to have a local SLD on the SAP Java system that you are installing. Then the SAP system you are installing is the SLD server.

3 Planning


2011-11-08 PUBLIC 39/158

Parameters DescriptionNOTE

The usual case is to configure one central SLD for your whole system landscape outside the SAP Solution Manager. However, we strongly recommend that you check the Master Guide for recommendations about which option to choose.

Register in existing central SLD

SLD HTTP Host The host name of the existing central SLD.

SLD HTTP Port The HTTP port of the existing central SLD. The following naming convention applies: 500.

EXAMPLE

If the instance number of your Java system is 01, the SLD HTTP Port is 50100.

SLD Data Supplier User and password

The existing SLD Data Supplier user and password of the existing central SLD

SLD ABAP API User and password

The existing SLD ABAP API user and password of the existing central SLD

SLD Gateway Host

Specify the name of the gateway host of the existing central SLD

SLD Gateway Instance Number

Specify the instance number of the gateway instance of the existing central SLD

Configure a local SLD

SLD Data Supplier User and password

Specify the name of the SLD Data Supplier user to be created. This user is used to send the self-registration data of your system to the SLD.

RECOMMENDATION

We recommend that you name this user SLDDSUSER

SLD ABAP API User and password

Specify the name of the SLD ABAP API user to be created. This user is used to send landscape data to and from the SLD.

RECOMMENDATION

We recommend that you name this user SLDAPIUSER

Object Server Name

The Object Server Name together with the CIM namespace identifies the absolute location of your System Landscape Directory. If you do not have a prefix reserved on SAP Market Place for Object Server Name, or if you just want to install a test or development system, enter the central instance host of your system. For more information about the Object Server Name parameter, see SAP Note 935245.

SAP System Database Parameters


Database ID The identifies the database instance. SAPinst prompts you for the when you are installing the database instance.The must be the same as the .

3 Planning


40/158 PUBLIC 2011-11-08

Parameters DescriptionCAUTION

Choose your database ID carefully. Renaming is difficult and requires that you reinstall the SAP system.

If you want to install a new database, make sure that your database ID: Is unique throughout your organization Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are

reserved IDs:ADD ALL AMD AND ANY ASC AUX AVG BIT CDC COM CON

DBA END EPS FOR GET GID IBM INT KEY LOG LPT MAP

MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN

RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP

TOP UID USE USR7 VAR

Database instance name MS SQL Server instance nameYou can also specify a remote database instance.Dependencies For a named instance, enter \.In an MSCS environment, enter the virtual host name.

Diagnostics Agent Parameters

The diagnostics agent is installed automatically with the SAP system.


System ID of the Diagnostics Agent

SAPinst sets the system ID of the diagnostics agent, , to DAA by default.If DAA is already used, SAPinst assigns another default system ID. You can overwrite the default system ID as required.

CAUTION

Choose the carefully. Renaming is difficult and requires you to reinstall the diagnostics agent.

Make sure that the : Either does not yet exist on the local installation host or does already

exist but was only used for a diagnostics agent installation Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs:

ADD ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END

EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT

NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID

SQL SUM SYS TMP TOP UID USE USR VAR

Instance Number of the Diagnostics Agent

Technical identifier for internal processes for the diagnostics agent, consisting of a two-digit number from 00 to 97. Default is 97.

3 Planning


2011-11-08 PUBLIC 41/158

Parameters DescriptionIf 97 is already used for an instance number, the diagnostics agent instance number is set automatically to the next free and valid instance number.The instance number is used to specify the name of the diagnostics agent instance directory that SAPinst automatically creates during the installation.The directory of the diagnostics agent instance is called SMDA.For more information, see SAP Directories [page 87].The same restrictions apply as in Instance Number of the SAP System (see above).

3.5 Domain or Local Installation

Before you install the SAP system, you have to decide whether you want to perform a domain or

local 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, go to Start

Help and Support and search for What is the difference between a domain and a workgroup?.

Domain Installation

In a domain installation, the user account information is stored centrally in one database on the domain

controller and is accessible to all hosts in the system.

You have to perform a domain installation if one of the following applies:

You install a system distributed over several hosts. Only valid for: HA (MSCS) |

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

You want to use Single Sign-On. 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 not visible

to any other hosts in the system.

If the SAP system is to run on a single machine (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 domain

installation, you must perform a homogeneous system copy. For more information, see the

documentation System Copy for SAP Systems based on SAP NetWeaver at:

http://service.sap.com/instguides

3 Planning

3.5 Domain or Local Installation

42/158 PUBLIC 2011-11-08
http://service.sap.com/instguides

More Information

Required User Authorization for Running SAPinst [page 50] Implementing Single Sign-On with Microsoft Kerberos SSP [page 108]

3.6 Distribution of SAP System Components to Disks

When you install the SAP system, the main directories required for the system are automatically created.

However, during the installation procedure, SAPinst prompts you to enter drive letters for the main

components of the system. This gives you the opportunity to distribute components to disks in the

system as you wish. How you do this significantly affects system throughput and data security, and

must therefore be carefully planned. The best distribution depends on your specific environment and

must take into consideration factors such as the size of the components involved, security requirements,

and the expected workload.

When you work out the assignment of components to disks, you first need to obtain an overview of

the main components and their corresponding directories. Then, on the basis of sample configurations

and the recommendations provided in this documentation, you can decide which assignment is best

for your particular system.

The table below gives you an overview of the main SAP system components, directories, and their

purpose.

A good distribution to disks ensures that:

Enough free space is available for system growth. The data is secure. Performance is good.System Components and their Directories

Directory Type Directory Structure Description

SAP System \usr\sap\usr\sap\trans

SAP kernel and related filesSAP transport directory

Database Management System (DBMS)

\Program Files\Microsoft SQL

Server

SQL Server program files including the master, msdb, and tempdb database files.

SAP Database \DATA0\DATA1

\DATA2

\DATA3

...

\DATA

Database data files

SAP Database Transaction Log \log Database transaction log files

Database Components

When you install an SAP system with MS SQL Sever, the central components of the database are the

SQL Server program files, tempdb files, SAP database data files and SAP database transaction

3 Planning

3.6 Distribution of SAP System Components to Disks

2011-11-08 PUBLIC 43/158

log files. The log files record all the changes made to the database to enable restore and recovery. The

tempdb holds all temporary tables and stored procedures. The data files contain the data for the SAP

system.

SAP Database Data FilesThe data files are created by default in the directories \DATA on the disk with the most

free available space. The first data file is called DATA0.mdf and subsequent files

DATA.ndf, where denotes the number