Ecc6 sr3 ora_win_instguide

PUBLIC

Installation Guide

SAP ERP 6.0 SR3 ABAP
on Windows: Oracle
ERP Central Component

Target Audience

n System Administrators
n Technical Consultants

Document version: 1.0 ‒ 03/28/2008

Document History

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

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

1.0 3/28/2008 Initial Version

2/164 PUBLIC 03/28/2008

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 11
1.3 Online Information from SAP . . . . . . . . . . . . . . . . . . 12
1.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1 Basic System Variants . . . . . . . . . . . . . . . . . . . . . 17
2.2 Domain or Local Installation . . . . . . . . . . . . . . . . . . 18
2.3 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . 19
2.4 Distribution of SAP System Components to Disks . . . . . . . . . . 20
2.5 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . 22
2.6 SAP System Transport Host . . . . . . . . . . . . . . . . . . . 26
2.7 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 27
2.8 Multiple Oracle Homes . . . . . . . . . . . . . . . . . . . . 32

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 35
3.1 Hardware and Software Requirements . . . . . . . . . . . . . . . 35
3.1.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 37
3.1.2 Requirements for a Central System . . . . . . . . . . . . . . . . 38
3.1.3 Requirements for a Distributed System . . . . . . . . . . . . . . 39
3.1.4 Requirements for a High-Availability System . . . . . . . . . . . . 42
3.1.5 Requirements for the Dialog Instance . . . . . . . . . . . . . . . 46
3.2 Checking the Windows File System . . . . . . . . . . . . . . . . 46
3.3 Checking the Windows Domain Structure . . . . . . . . . . . . . 47
3.4 Reducing the Size of the File Cache . . . . . . . . . . . . . . . . 48
3.5 Required User Authorization for the Installation . . . . . . . . . . . 48
3.6 Performing a Domain Installation Without Being a Domain Administrator . 50
3.7 Preparing the SAP System Transport Host . . . . . . . . . . . . . 52
3.8 Installing the Front-End Software . . . . . . . . . . . . . . . . 54
3.9 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 54
3.10 Installing the Java Runtime Environment . . . . . . . . . . . . . 54
3.11 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 55
3.12 Downloading Installation DVDs from SAP Service Marketplace (Optional) . 57

03/28/2008 PUBLIC 3/164

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 59
4.1 Installing the Oracle Database Software . . . . . . . . . . . . . . 59
4.2 Setting Up Multiple Homes (Optional) . . . . . . . . . . . . . . 61
4.3 Installing an SAP System Using SAPinst . . . . . . . . . . . . . . 62
4.3.1 Running SAPinst on Windows . . . . . . . . . . . . . . . . . . 62
4.3.2 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 69
4.3.3 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 70
4.3.4 Performing a Remote Installation with SAPinst (Optional) . . . . . . . 72
4.3.5 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 72
4.3.6 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 74
4.3.7 How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . 75

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 77
5.1 Configuring the Windows Server 2008 Firewall . . . . . . . . . . . . 78
5.2 Logging On to the Application Server . . . . . . . . . . . . . . . 79
5.3 Installing the SAP License . . . . . . . . . . . . . . . . . . . 80
5.4 Creating Symbolic Links on Windows Server 2008 for Application Servers . . 80
5.5 Installing the SAP Online Documentation . . . . . . . . . . . . . 81
5.6 Configuring Remote Connection to SAP Support . . . . . . . . . . 81
5.7 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 82
5.8 Performing Initial ABAP Configuration . . . . . . . . . . . . . . 83
5.9 Performing Oracle-Specific Post-Installation Steps . . . . . . . . . . 85
5.10 Performing the Client Copy . . . . . . . . . . . . . . . . . . 86
5.11 Performing a Full System Backup . . . . . . . . . . . . . . . . 87
5.12 Implementing ERP ABAP Add-On Components . . . . . . . . . . . 87
5.13 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 88
5.14 Accessing Configuration Documentation in SAP Solution Manager . . . . 89

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 91
6.1 Installation of Multiple Components in One Database (Optional) . . . . . 91
6.2 Integration of LDAP Directory Services (Optional) . . . . . . . . . . 93
6.3 Starting and Stopping the SAP System . . . . . . . . . . . . . . . 97
6.4 Single Sign-On with Microsoft Kerberos SSP . . . . . . . . . . . . 98
6.4.1 Preparing the Central Instance . . . . . . . . . . . . . . . . . 99
6.4.2 Configuring the SAP Front End . . . . . . . . . . . . . . . . . 100
6.4.3 Activating Single Sign-On for the SAP Logon . . . . . . . . . . . . 101
6.4.4 Mapping SAP Users to Windows Users . . . . . . . . . . . . . . . 102
6.5 Configuring the Connection to a Central System Landscape Directory (SLD) 103
6.6 SAP System Security on Windows . . . . . . . . . . . . . . . . 103
6.7 Automatic Creation of Accounts and Groups . . . . . . . . . . . . 105
6.8 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 107

4/164 PUBLIC 03/28/2008

6.8.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 107
6.9 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 107
6.9.1 Running SAPinst to Delete an SAP System . . . . . . . . . . . . . 108
6.9.2 Deleting the Oracle Database Software . . . . . . . . . . . . . . 110

Chapter 7 High Availability with Microsoft Cluster Service . . . . . . . . . 113
7.1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 114
7.1.1 System Configuration in MSCS . . . . . . . . . . . . . . . . . 115
7.1.1.1 SAP System Components in an MSCS Configuration . . . . . . . . . 115
7.1.1.2 Enqueue Replication Server in an MSCS Configuration . . . . . . . . 119
7.1.2 Distribution of Components to Disks for MSCS . . . . . . . . . . . 120
7.1.3 Directories in an MSCS Configuration . . . . . . . . . . . . . . . 124
7.1.4 IP Addresses in an MSCS Configuration . . . . . . . . . . . . . . 125
7.1.5 Obtaining and Determining IP Addresses for MSCS . . . . . . . . . . 128
7.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 130
7.2.1 Assigning Drive Letters for MSCS . . . . . . . . . . . . . . . . 131
7.2.2 Mapping Host Names to IP Addresses for MSCS . . . . . . . . . . . 131
7.2.3 Checking the Mapping of Host Names for MSCS . . . . . . . . . . . 132
7.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.3.1 Moving MSCS Groups or Services and Applications . . . . . . . . . . 135
7.3.2 Rebooting During the Installation or Conversion for MSCS . . . . . . . 136
7.3.3 Installing the Oracle Fail Safe Software in a 64-Bit System . . . . . . . . 137
7.3.4 Installing the Central Services Instance for ABAP (ASCS) . . . . . . . . 139
7.3.5 Configuring the First MSCS Node . . . . . . . . . . . . . . . . 140
7.3.6 Installing the Database Instance . . . . . . . . . . . . . . . . . 141
7.3.7 Configuring the Additional MSCS Node . . . . . . . . . . . . . . 142
7.3.8 Additional Steps for the Oracle Fail Safe Configuration . . . . . . . . . 144
7.3.9 Installing an Enqueue Replication Server . . . . . . . . . . . . . . 145
7.3.10 Installing the Central Instance . . . . . . . . . . . . . . . . . 146
7.3.11 Creating the Oracle Fail Safe Group . . . . . . . . . . . . . . . . 147
7.3.12 Setting Up a Shared Database Directory in Oracle Home . . . . . . . . 148
7.3.13 Adding the Oracle Database Resource to the Fail Safe Group . . . . . . . 150
7.3.14 Installing the Dialog Instance . . . . . . . . . . . . . . . . . . 150
7.4 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . 152
7.4.1 Starting and Stopping the SAP System in an MSCS Configuration . . . . . 152
7.4.2 Post-Installation Checks for Enqueue Replication Server . . . . . . . . 153
7.4.2.1 Checking the Status of the Enqueue Replication Server with ENSMON . . . 154
7.4.2.2 Monitoring the Lock Table During Failover with ENQT . . . . . . . . 154

03/28/2008 PUBLIC 5/164

1 Introduction

1 Introduction

This document explains how to install SAP ERP 6.0 SR3 ABAP.
SAP ERP 6.0 is based on SAP NetWeaver 7.0 technology. For more information about the
technology provided by SAP ERP and SAP NetWeaver, see http://service.sap.com/erp and
http://sdn.sap.com/irj/sdn/netweaver.
Make sure you have read the documentation Master Guide Support Release 3‒ SAP ERP 6.0 powered by SAP
NetWeaver 7.0 Using Product Version SAP ERP 2005 before you start with this installation guide. The Master
Guide is available at http://service.sap.com/erp-inst SAP ERP 6.0 .

Caution
See SAP Note 852235 for up-to-date information about release restrictions for SAP ERP 6.0.

You can install SAP ERP 6.0 SR3 with the following software unit(s):
n SAP ERP Central Component (ECC)

Note

n You also install SAP NetWeaver Application Server ABAP (AS ABAP) with SAP ERP Central
Component.
n If you want to add additional software units or usage types to an existing SAP system, follow
SAP Note 883948.
For more information about the usage types of SAP NetWeaver and their interdependencies, see
the document Master Guide ‒ SAP NetWeaver 7.0 at http://service.sap.com/instguidesNW70. For
restrictions, see SAP Note 852008.

Constraints
You need to consider the following constraints before you start your installation:
n Your operating system platform must be 64-bit.
n The database must be Oracle 10.2.0.2 or higher.
n 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.
n 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.

03/28/2008 PUBLIC 7/164

1 Introduction
1.1 New Features

n 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 as follows:
l Install the component with the old proposed database version.
l Upgrade the old database version to the downward-compatible new version.

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 at
http://service.sap.com/releasenotes.

SAP System Installation

Area Description
SAPinst As of SAP NetWeaver 7.0, SAPinst has the following new features:
n You can check the prerequisites for your SAP system installation with the
Prerequisite Checker [page 37].
n You can install a central system in one of two modes:
l Typical Mode
If you choose Typical, your SAP system is installed with default settings. As
a result, you only have to respond to a small selection of prompts. If you
want to change any of the default settings, you can do so on the parameter
summary screen at the end of the installation.
l Custom Mode
If you choose Custom, you must manually enter all installation parameters.
You can change your values on the parameter summary screen at the end of
the installation.
n You can uninstall an SAP system or an SAP component with the SAPinst service
Uninstall ‒ System / Standalone Engines / Optional Standalone Unit.
n You can install the Java Add-In for an existing ABAP system. This means that you
run SAPinst to execute the following:
l Install the central services instance (SCS)
l Add the Java database schema to the existing ABAP database instance
l Add the Java central instance with usage types to the existing ABAP central
instance
The installation of the Java Add-In for an existing ABAP system is described in the
documentation Installation Guide ‒ <your product> ABAP+Java on <OS>: <Database>
available at http://service.sap.com/instguides.

8/164 PUBLIC 03/28/2008

1 Introduction
1.1 New Features

Area Description

Note
You cannot install the Java Add-In for existing ABAP dialog instance(s). Instead,
you have to install new ABAP+Java dialog instance(s).

n You assign one master password to all users created by SAPinst. This password is
used for all user accounts and for the secure store key phrase.
n SAPinst fills in most of the input parameter fields with default values.
If required, you can change the default values on the Parameter Summary screen
before you start the actual installation.
Installation DVDs You start the installation from a single Installation Master DVD.
Usage type EP Core As of SAP NetWeaver 7.0 SR2, usage type Enterprise Portal (EP) has been separated
(EPC) into two closely related usage types: EP Core (EPC) and Enterprise Portal (EP). Usage
type EPC provides the core portal capabilities available in the former usage type EP.
Usage type EP now includes all portal add-on capabilities it provided before, but
without the core portal functionality.
n EP Core (EPC)
This usage type contains the core portal capabilities that were available in the
former usage type EP. This new usage type provides more flexibility when
implementing a portal where the full enterprise portal capabilities, such as
knowledge management and collaboration, are not needed. It contains the
portal, Guided Procedures (GP), and Universal Worklist (UWL).
n Enterprise Portal (EP)
This usage type includes Knowledge management, Collaboration, Composite
Application Framework Core (CAF-Core), Visual Composer, Web Dynpro
extension, and .NET PDK.
For more information about EPC and about how to use it in IT scenarios, see the
Master Guide and SAP Note 982502.
SAP SRM 5.0 as Add-On In SAP ERP 6.0, you can deploy SAP SRM Server as one of the following:
Component to SAP n An add-on to SAP ECC Server (product instance SAP ERP 6.0 ‒ SAP ECC) to
ERP 6.0 run SRM in one client of the ERP system. This deployment option is new in
SAP ERP 6.0.
n A separate installation from SAP ECC Server. This deployment option is the
same as in mySAP ERP 2004.
For more information, see the documentation Master Guide ‒ SAP ERP 6.0 powered by
SAP NetWeaver 7.0 at http://service.sap.com/erp-inst.
SAP Solution Manager You require a key to install your SAP system. You generate this key with your SAP Solution
Key Manager [page 54].

03/28/2008 PUBLIC 9/164

1 Introduction
1.1 New Features

Area Description
High Availability
Note
There is a terminology change with Windows Cluster. As of Windows Server 2008
the high-availability feature is called “Failover Clustering”. For practical reason we
are continuing to use the general abbreviation MSCS.

You have the following options to install a high-availability system with MSCS:
n You install one SAP system in one MSCS cluster.
n You install one SAP system in two MSCS 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.
64-bit support for all If you want to use 32-bit SAP NetWeaver components, first check whether these
instances except dialog components can run on 64-bit operating systems. If so, we recommend that you
instances use 64-bit systems.
If not, you can install an SAP dialog instance on 32-bit operating systems to run
these components. For all other SAP instances, you must use 64-bit systems
Only Unicode support Every newly installed SAP system is a Unicode system.
for new installations However, non-Unicode is still supported for copied and upgraded systems.
Maintenance All downloadable software components based on SAP NetWeaver 7.0 and subsequent
Optimizer versions released after April 2, 2007 are available exclusively through the
Maintenance Optimizer in SAP Solution Manager. This comprises:
n Support Package Stacks, Support Packages, and patches for Java instances, except
for kernel patches
n Legal changes
n SAP applications and versions that are:
l Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and all
applications based on this software, including SAP Business Suite 2005 (and
subsequent versions)
l Optional for all SAP applications
For more information, see http://service.sap.com/solman-mopz.

Operating Systems and Platforms

Area Description
Support of Operating
Note
Systems and Platforms
This guide already includes information about the new Windows operating
system, Windows Server 2008, which is not yet supported by Oracle for SAP.

n For supported operating system and database releases, see the Product Availability
Matrix at http://service.sap.com/pam.
n For forums, blogs, content, and community related to all of the supported
databases and operating systems, see the Database and Operating Systems area at
http://sdn.sap.com/irj/sdn/dbos.

10/164 PUBLIC 03/28/2008

1 Introduction
1.2 SAP Notes for the Installation

Oracle Database

Area Description
New features in Oracle 10g For the complete list of new features, see further documentation from
Oracle, which you can find at:
www.oracle.com/technology/products/database/oracle10g
See also:
n www.oracle.com/technology/documentation/
database10g.html View Library
n The documentation provided by Oracle on the RDBMS DVD
under <DVD_Drive>:NT<platform>databasedocindex.htm

Documentation

Area Description
Links in PDF files You can use the new links in the PDF files of the guides as follows:
n Click the section headings such as New Features to jump back to the table of
contents at the beginning of the guide.
n Click an internet link such as http://service.sap.com to jump to the
corresponding internet page.

1.2 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
852235 Release restrictions for SAP ERP At the time of the release of SAP ERP 6.0,
6.0 limitations affect the productive usage of
certain functions. This note provides customer
information on these restrictions.
1108852 SAP NetWeaver 7.0 / Business Windows-specific information about the SAP
Suite 2005 SR3: Windows system installation and corrections to this
documentation.
852008 Release Restrictions for SAP Customer information on restrictions in the
NetWeaver 7.0 production use of certain functions.
1108857 SAP NetWeaver 7.0 / Business Oracle-specific information about the SAP
Suite 2005 SR3 based system: system installation and corrections to this
Oracle Windows documentation.

03/28/2008 PUBLIC 11/164

1 Introduction
1.3 Online Information from SAP

SAP Note Number Title Description
828268 Oracle 10g: New functions Information about new Oracle features released
for the SAP system.
855498 Installation Prerequisite Checker SAP Software on UNIX, Windows and System i:
Checking OS Dependencies
73606 Supported Languages and Code Information on possible languages and language
Pages combinations in SAP systems
1067221 Central Note for Heterogeneous Heterogeneous ABAP system landscapes on
Installation different operating systems have been released
for some time. Heterogeneous Java system
landscapes on different operating systems have
now also been released. However, not every
combination of operating system and database
system is released. This SAP Note and its related
SAP Notes describe the released operating system
and database combinations.
1152408 Installing SAP Systems into an Information on features and limitations for
Independent ASP (iASP) installations into independent ASP.


More information is available online as follows.

Documentation

Description Internet Address Title
Master Guide for SAP ERP http://service.sap.com/erp-inst SAP Master Guide Support Release 3
6.0 ERP 6.0 Installation Master Guide for SAP ERP ‒ SAP ERP 6.0 powered by SAP
6.0 NetWeaver 7.0 — Using Product
Version SAP ERP 2005
Master Guide SAP http://service.sap.com/instguides SAP Master Guide ‒ SAP Solution
Solution Manager 4.0 Components SAP Solution Manager Release 4.0 Manager 4.0
Installation of SAP http://service.sap.com/instguides SAP Installation Guide ‒ SAP Solution
Solution Manager 4.0 Components SAP Solution Manager Release 4.0 Manager 4.0 on <OS>: <Database>
Configuration of SAP http://service.sap.com/instguides SAP Configuration Guide ‒ SAP Solution
Solution Manager 4.0 Components SAP Solution Manager Release 4.0 Manager 4.0 as of <current stack>
Patching of SAP http://service.sap.com/maintenanceNW70 Support Package Stack Guide ‒ SAP
NetWeaver 7.0 scenarios SPS <current stack> Support Package Stack Guide ‒ NetWeaver 7.0 SPS <current stack>
SPS <current stack>
Upgrade to SAP ERP 6.0 http://service.sap.com/erp-inst SAP Upgrade Master Guide — SAP ERP
ERP SAP ERP 6.0 Upgrade Upgrade Master 6.0 powered by SAP NetWeaver 7.0 ‒
Guide — SAP ERP 6.0 Using Product Version SAP ERP 2005

12/164 PUBLIC 03/28/2008

1 Introduction

Description Internet Address Title
Installation of SAP http://service.sap.com/installNW70 Installation Guide ‒ Developer
NetWeaver Developer Installation Installation — Clients Installation ‒ Workplace for SAP NetWeaver
Workplace SAP Developer Workplace
Installation of SAP http://service.sap.com/installNW70 SAP NetWeaver Developer Studio —
NetWeaver Developer Installation Installation — Clients Installation ‒ Standalone Installation Guide
Studio SAP NetWeaver Developer Studio
Installation of the System http://service.sap.com/installNW70 Post-Installation Guide ‒ System
Landscape Directory (SLD) Configuration Post-Installation Guide ‒ SLD of SAP Landscape Directory of SAP
NetWeaver 7.0 NetWeaver 7.0
Installation of a standalone http://service.sap.com/installNW70 Installation Guide ‒ Gateway on
gateway Installation ‒ Standalone Engines Installation — <platform> ‒ For SAP Systems Based
Gateway on <platform> on SAP NetWeaver 7.0 (2004s)
Installation of Web http://service.sap.com/installNW70 Installation Guide ‒ Web Dispatcher
Dispatcher Installation ‒ Standalone Engines Installation — Web on <platform> ‒ For SAP Systems
Dispatcher on <platform> Based on SAP NetWeaver 7.0 (2004s)
Front End installation http://service.sap.com/installNW70 SAP Front End Installation Guide
Installation ‒ Clients Installation ‒ SAP Front End This guide is also available on
<Release> the Presentation DVD.
Homogeneous and http://service.sap.com/installNW70 System Copy Guide — System Copy for
heterogeneous system Installation ‒ SAP NetWeaver Systems System Copy SAP Systems based on SAP NetWeaver
copy for SAP systems based for SAP Systems Based on <Release> <Technology> <Release> <Technology>
on NetWeaver 7.0
SAP NetWeaver Problem http://help.sap.com/nw70 SAP NetWeaver SAP NetWeaver Problem Analysis
Analysis Guide 7.0 Library ‒ English SAP NetWeaver Library SAP Guide (PAG)
NetWeaver by Key Capability Solution Life Cycle
Management by Key Capability SAP NetWeaver
Problem Analysis Guide (PAG)

General Quick Links

Description Internet Address
SAP Help Portal http://help.sap.com

SAP NetWeaver Library in SAP http://help.sap.com/nw70
Help Portal
SAP ERP Library in SAP Help http://help.sap.com/erp
Portal
SAP Notes http://service.sap.com/notes

SAP Notes for SAP NetWeaver 7.0 http://service.sap.com/sapnotesnw70
installation

03/28/2008 PUBLIC 13/164

1 Introduction

Description Internet Address
Forums, blogs, and general http://sdn.sap.com/irj/sdn/dbos
information related to all of
the supported databases and
operating system platforms
Product Availability Matrix (PAM) http://service.sap.com/pam
for supported operating system
releases
General information, forums and http://sdn.sap.com/irj/sdn/windows
blogs about information related
to SAP on Windows
Release notes http://service.sap.com/releasenotes

Unicode SAP systems and their http://service.sap.com/unicode
availability
System sizing (Quick Sizer tool) http://service.sap.com/sizing

SAP NetWeaver capabilities http://sdn.sap.com/irj/sdn/netweaver

Life-cycle management for SAP http://sdn.sap.com/irj/sdn/lcm
NetWeaver
Landscape design for SAP http://sdn.sap.com/irj/sdn/landscapedesign
NetWeaver
Application management for SAP http://sdn.sap.com/irj/sdn/applicationmanagement
NetWeaver
High Availability http://sdn.sap.com/irj/sdn/ha

System Landscape Directory http://sdn.sap.com/irj/sdn/nw-sld

Software logistics for SAP http://sdn.sap.com/irj/sdn/softwarelogistics
NetWeaver
SAP NetWeaver operations http://sdn.sap.com/irj/sdn/operations

SAP NetWeaver Development http://sdn.sap.com/irj/sdn/nw-di
Infrastructure
Security for SAP NetWeaver http://sdn.sap.com/irj/sdn/security

Note
For information on Windows operating system security, see:
http://www.microsoft.com/security

Information on SAP Support http://service.sap.com/sp-stacks
Package 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

14/164 PUBLIC 03/28/2008

1 Introduction
1.4 Naming Conventions


Note
We have renamed “mySAP ERP 2005” to “SAP ERP 6.0”. On the technical level, “SAP ERP 6.0” is
associated with product version “SAP ERP 2005”. The term “SAP ERP 2005” remains valid. In this
document, we use the term “SAP ERP 6.0” and the name of the product version “SAP ERP 2005” to
depict the former release “mySAP ERP 2005”.

In this documentation, the following naming conventions apply:

Terminology

n SAP system refers to SAP ERP 6.0 SR3.
n ABAP system refers to SAP ERP 6.0SR3 ABAP.
Only valid for: HA (MSCS)

Terminology for High Availability on Windows
As of Windows 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 use
the general abbreviation MSCS in this guide.
n Cluster groups are now called services and applications.
n The Cluster Administrator is now called Failover Cluster Management.
End of: HA (MSCS)

Variables

Variables Description
<SAPSID> SAP system ID in uppercase letters
<sapsid> SAP system ID in lowercase letters
<DBSID> Database ID in uppercase letters
<dbsid> Database ID in lowercase letters
<host_name> Name of the corresponding host
<INSTDIR> Installation directory for the SAP system
<DVD_DIR> Directory on which a DVD is mounted
<OS> Operating system name within a path
<SCHEMA_ID> Database schema ID

The following example shows how the variables are used:

03/28/2008 PUBLIC 15/164

1 Introduction

Example
Log on as user <sapsid>adm and change to the directory usrsap<SAPSID>.
If your SAP system ID is C11, log on as user c11adm and change to the directory
usrsapC11.

16/164 PUBLIC 03/28/2008

2 Planning

2 Planning

This section tells you how to plan the installation of your SAP system.

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

You have to complete the following planning activities:
1. You plan your SAP system landscape according to the Master Guide.
In addition, we recommend that you read theTechnical Infrastructure Guide ‒ SAP NetWeaver 7.0, which
is available at: http://service.sap.com/installNW70.
2. You choose your basic system variant [page 17].
3. You decide whether you want to perform a domain or local installation [page 18].
4. You plan how to distribute the instances to hosts [page 19].
5. For the database installation, you decide on how to distribute your database components to disk [page 20].
6. You read about the SAP directories [page 22].
7. You decide on the transport host to use [page 26].
8. You identify basic SAP system parameters [page 27].
9. You decide if you want to use Multiple Oracle Homes [page 32].
The following planning activity is optional:
n Installation of Multiple Components in One Database (MCOD) [page 91]

2.1 Basic System Variants

This section describes the basic system variants and shows how you can distribute SAP instances
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.

03/28/2008 PUBLIC 17/164

2 Planning
2.2 Domain or Local Installation

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 the
mandatory instances are installed on separate hosts.

Figure 1: ABAP System

More Information

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

2.2 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, see the
Microsoft article Deciding Between Workgroups and Domains at:
http://technet2.microsoft.com/windowsserver/en/library/

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.

18/164 PUBLIC 03/28/2008

2 Planning
2.3 How to Distribute Instances to Hosts

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 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 <release> <technology> at:
http://service.sap.com/instguides <your product>

More Information
n Required User Authorization for the Installation [page 48]
n Single Sign-On with Microsoft Kerberos SSP [page 98]

2.3 How to Distribute Instances to Hosts

The following provides information on how you can distribute the SAP instances for the different SAP
system variants. You use SAPinst to install the SAP instances as a:
n Central system on a single host
You run SAPinst and install all instances on one host.
n Distributed system on several hosts
You 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:
l Database instance on the database host
l Central instance on the global host
l Dialog instance(s), if required, on the dialog instance host(s)
The following figure shows how to distribute your instances to several hosts:

03/28/2008 PUBLIC 19/164

2 Planning
2.4 Distribution of SAP System Components to Disks

Figure 2: Distribution of Instances in an ABAP System


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 get 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.
SAP systems are normally installed on RAID arrays that ensure data redundancy. This documentation
therefore focuses on RAID subsystems and drives.

Minimal Configuration
The following figure illustrates an example for a disk configuration for a small test or demo system.
Since security and performance play a less crucial role in this type of system, many different
configurations are feasible.

20/164 PUBLIC 03/28/2008

2 Planning

Caution
Use the illustrated configuration exclusively for test or demo systems. It is unsuitable for production
systems because it only minimally satisfies security and performance requirements.

Figure 3:

Distribution of Directories to Disks

Disk Directories
Disk 1 ORACLE<DBSID>102
ORACLE<DBSID>origlogA
ORACLE<DBSID>origlogB
ORACLE<DBSID>sapdata1

Disk 2 ORACLE<DBSID>mirrlogA
ORACLE<DBSID>mirrlogB
ORACLE<DBSID>sapreorg
ORACLE<DBSID>saptrace
ORACLE<DBSID>saparch
ORACLE<DBSID>sapbackup
ORACLE<DBSID>sapcheck

Disk 3 ORACLE<DBSID>oraarch

03/28/2008 PUBLIC 21/164

2 Planning
2.5 SAP Directories

Comments

n The configuration ensures that no data can be lost, but the process for recovering a damaged
database is complicated and time-consuming.
n The redo logs and database files are located on the same disks. This means that a single disk failure
can result in the loss of both the redo logs and database data.
n The I/O-intensive redo logs are on the same disk volumes as the data files. This can impede
performance.
n An equally good alternative would be to simply place all components on a single RAID 5 array.

2.5 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 124].
End of: HA (MSCS)

SAPinst automatically creates the following directories during the installation:
n usrsap
This directory is created on the:
l Global host and shared with the network share sapmnt
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 usrsap directory contains general SAP software, global and local
(instance-specific) data. For this, SAPinst creates the global directory usrsap<SAPSID>SYS,
which physically exists only once for each SAP system. It consists of the following subdirectories:
u global ‒ contains globally shared data
u profile ‒ contains the profiles for all instances
u exe ‒ contains executable replication directory for all instances and platforms
l Local host and shared with the name saploc.
On local hosts, the usrsap<SAPSID><instance_name> directory contains copies of the SAP
software and local (instance-specific) data.

22/164 PUBLIC 03/28/2008

2 Planning
2.5 SAP Directories

Note
Since SAP traces for the instance are created in usrsap, make sure there is sufficient space
available 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 time
the 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 the
application 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 the
UNC 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.

Note
Windows Server 2008 only:
In a high-availability system, file shares pointing to directories on shared disks are only visible or
accessible with the virtual host name of the cluster group the shared disks belong to.
This lets you have several shares with the same name pointing to different disks (multi-SID).

End of: HA (MSCS)

n usrsaptrans
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 from
your SAP system landscape, you can specify another host during the installation. In this case, you
have to prepare that host for the new SAP system to use it. For more information, see Preparing
the SAP System Transport Host [page 52].

Directory Structure
The following figures show how the physical directory usrsap is shared on the global host in a
central and in a distributed system. In both cases, the UNC paths are used as follows:
n <SAPGLOBALHOST>sapmnt to access global directories
n <SAPLOCALHOST>saploc to access local instance-specific data

03/28/2008 PUBLIC 23/164

2 Planning
2.5 SAP Directories

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

Note
Every new installation of an SAP system is Unicode.

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

24/164 PUBLIC 03/28/2008

2 Planning
2.5 SAP Directories

Figure 5: Directory Structure in a Distributed ABAP System

03/28/2008 PUBLIC 25/164

2 Planning
2.6 SAP System Transport Host

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)

2.6 SAP System Transport Host

The transport host contains the transport directory that is used by the SAP transport system to store
transport data and change information of SAP systems, such as software programs, data dictionary
data, or customization data. If you have several SAP systems they are usually organized in transport
domains. In most cases, all SAP systems in a transport domain have a common transport directory.
For more information, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver
by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software
Logistics Change and Transport System Change and Transport System ‒ Overview (BC-CTS) Basics of the Change
and Transport System Transport Management System ‒ Concept
When you install an SAP system, SAPinst by default creates the transport directory on the central
instance host in usrsaptrans.

26/164 PUBLIC 03/28/2008

2 Planning
2.7 Basic SAP System Parameters


Note
In an MSCS configuration, SAPinst by default creates the transport directory on the (ABAP) central
services instance host in usrsaptrans.

End of: HA (MSCS)

You have to prepare this host for use by the new SAP system if one of the following applies to you:
n You want to locate the transport directory on another host.
n You want to use an existing transport host and directory in your SAP system landscape.
For more information, see Preparing the SAP System Transport Host [page 52].

More Information
SAP Directories [page 22]


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

Note
In the column “Enter Your Values”, you write down the values that you plan to use, for example,
the Message Port Number.

SAP System ID and Database ID

Parameters Description Enter Your Values
SAP System ID The SAP System ID <SAPSID> identifies the whole SAP ...
<SAPSID> 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:
n Is unique throughout your organization
n Consists of exactly three alphanumeric characters
n Contains only uppercase letters
n Has a letter for the first character
n Does not include any of the following, which are reserved
IDs:

03/28/2008 PUBLIC 27/164

2 Planning

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

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

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

n If you want to install a new database:
Make sure that your database ID:
l Is unique throughout your organization
l Consists of exactly three alphanumeric characters
l Contains only uppercase letters
l Has a letter for the first character
l 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:
Enter exactly the database ID of the existing database to
which you want to add the system.

Only valid for: SAP CRM 5.0;SAP SCM 5.0;SAP SRM Server 5.5

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 a non-Unicode SAP system that has been upgraded
to SAP NetWeaver 7.0 SR3

End of: SAP CRM 5.0;SAP SCM 5.0;SAP SRM Server 5.5

28/164 PUBLIC 03/28/2008

2 Planning

SAP System Instances, Hosts and Ports

Parameters Description Enter
Your
Values
Instance Number of Technical identifier for internal processes. It consists of a two-digit ...
the SAP system number from 00 to 98.
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.
To find out this number, look under the SAP directory
<Drive>:usrsap<SAPSID>DVEBMGS<nn> on the host of the central
instance.
The value <nn> is the number assigned to the central instance.

Caution
Do not use 43, and 89 for the instance number because:
n 43 is used by MSCS
n 89 is used by Windows Terminal Server
Name of Instance Instance Host: ...
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 the allowed host name length and characters, see SAP Note 611361.
In addition, see SAP Note 849423.
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 Port
There 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<nn>, where <nn> 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<nn>, where
<nn> is the instance number of the ABAP message server instance.
For more information about the parameters used for message server
ports, see SAP Note 821875.

03/28/2008 PUBLIC 29/164

2 Planning

Master Password

Master Password This password is used for all user accounts SAPinst creates and ...
for the secure store key phrase. The length has to be 8 to 14
characters.
Depending on your installation scenario there might be more
restrictions.

Caution
If you do not create the operating system users manually,
SAPinst creates them with the common master password (see
“Operating System Users”). In this case, make sure that the
master password meets the requirements of your operating
system and of your database.

Operating System Users

Password of Operating SAPinst processes the passwords of operating system users as ...
System Users follows:
n If the operating system users do not exist, SAPinst creates the
following users:
l <sapsid>adm
This user is the SAP system administrator user and is a
member of the local Administrators group.
l SAPService<SAPSID>
This user is the Windows account to run the SAP system.
It is not a member of the local Administrators group.
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.
n 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.

Caution
Make sure that you have the required user authorization [page 48] for
these accounts before you start the installation.

30/164 PUBLIC 03/28/2008

2 Planning

Internet Communication Manager (ICM) User Management

Parameter Description Enter Your Values
Password of webadm The administration user webadm is created to use the web ...
administration interface for Internet Communication Manager
(ICM) and Web Dispatcher.
SAPinst sets the master password by default. If required, you
can choose another password. The length of the password must
be between 5 and 128 characters.

Solution Manager Key

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

Parameters for SAPDATA Drives

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

Example
If you enter D:, the system adds
the directory D:usrsapSAPSID.

Note
If you install a subsequent SAP
system, the saploc share already
exists and you cannot select the
installation drive. SAPinst uses
the installation drive where the
saploc share points to.

03/28/2008 PUBLIC 31/164

2 Planning
2.8 Multiple Oracle Homes

Parameters Relevant for the Database

Code page The code page that is used by your database (Unicode or ...
Non-Unicode).

Note
This parameter is only prompted if you perform a target
system installation as part of a system copy.
Database schema, The ABAP database schema is named SAP<SCHEMA_ID>. ...
Passwords Default name is SAPSR3.

Recommendation
Choose a <SCHEMAID> that is different from your <SAPSID>.
It might cause problems when you copy a system
where <SCHEMAID> is the same as <SAPSID>, and the
database-specific method used for the copy does not allow
you to rename the database schemas. In certain situations,
you might create a system copy with a new <SAPSID>, but
where the database schema has the old <SAPSID>. This is
not a technical problem, but might confuse the system
administrator.
Oracle parameters n Oracle home ...
n SAPDATA drives
n Drives for redolog and archives (oraarch)
Oracle Listener Name, n If you install the database instance on a host where no ...
Oracle Listener Port other Oracle database is installed, you normally do not
have to change the default values for Listener Name
and Listener Port.
n If you install the database instance on a host where
already another Oracle database is installed you have
the following options:
l If you install it in the same Oracle home, you use the
default values for Listener Name and Listener Port.
l If you install it in a different Oracle home, you
specify an unused Listener Name and Listener Port
for the new Oracle Listener.
n All dialog instances of an SAP system must use the same
Listener Port than the database instance.


Oracle lets you install multiple Oracle Homes on one host.

32/164 PUBLIC 03/28/2008

2 Planning


Note
MSCS only:
Multiple Oracle Homes for different database instances are not supported in an MSCS configuration.

End of: HA (MSCS)

Note the following about multiple Oracle Homes:
n Multiple Oracle Homes are necessary, if you install different Oracle versions for two or more
databases on the same host.
n If you use multiple Oracle Homes, you must use different port numbers for each listener.
n If you install the same Oracle database version on one host for different database instances, you
can use:
l Multiple Oracle Homes
With multiple Oracle Homes, you can administer your databases independently. For example,
if you want to install a patch set, you do not have to install them on both databases.
l One Oracle Home for two databases
You have to install the database software only once.

Note
In case you later want to use two multiple homes instead of one, you either have to perform a
new database instance installation or upgrade your database.

Before you install your Oracle database software, you need to decide whether you want to set up
multiple Oracle Homes as this influences the installation procedure. For more information, see
Setting Up Multiple Oracle Homes [page 61].

03/28/2008 PUBLIC 33/164

This page is intentionally left blank.

3 Preparation

3 Preparation

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.

You have to complete the following preparations:
1. You check the hardware and software requirements [page 35] on each host.
2. You check the Windows file system [page 46] on each host.
3. You check that your installation host belongs do the correct Windows domain [page 47].
4. You reduce the size of the file cache [page 48] on each host.

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

5. You check that you have the required user authorization for the installation [page 48].
6. If required, you perform a domain installation without being a domain administrator [page 50].
7. If required, you prepare the SAP system transport host [page 52] for your SAP system.
8. You install the SAP front-end software [page 54] on the desktop of the end user.
9. You generate the SAP Solution Manager Key [page 54] for your SAP system.
10. You install the Java Runtime Environment [page 54].
11. You make the installation DVDs available [page 55] on each host.
12. If required, you download the installation DVDs from SAP Service Marketplace [page 57].

13. For the installation of a high-availability system with Microsoft Cluster Service (MSCS), in
addition, you have to perform MSCS-specific preparation tasks [page 130].
End of: HA (MSCS)

3.1 Hardware and Software Requirements
You check that your hosts meet the hardware and software requirements for your operating system
and the SAP instances.

03/28/2008 PUBLIC 35/164

3 Preparation

Caution
If your hosts do not fully meet the requirements, you might experience problems when working
with 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 Notes 611361 and 849423.

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:
n The Prerequisite Checker:
l Standalone (optional) before the installation process
For more information, see Running the Prerequisite Checker Standalone [page 37].
l Integrated in SAPinst (mandatory) as part of the installation process
For more information, see Running SAPinst on Windows [page 62]

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 38]
l Distributed system [page 39]

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

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

Note
If you want to use 32-bit SAP NetWeaver components, first check whether these
components can run on 64-bit operating systems. If so, we recommend you to use 64-bit
systems. If not, you can install an SAP dialog instance on 32-bit operating systems to run
these components. For all other SAP instances, you must use 64-bit systems.

3. If you are installing 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:
n You use the SAP Quick Sizer tool available at http://service.sap.com/sizing.

36/164 PUBLIC 03/28/2008

3 Preparation

For more information about the SAP Quick Sizer and available sizing guides, see the Master 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 hardware
sizing depending on:
l The set of applications to be deployed
l How intensively the applications are to be used
l The number of users

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

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

Prerequisites
n You have installed the correct Java Runtime Environment (JRE) [page 54].
n You have prepared the installation master DVD on the required installation host [page 55].

Procedure
1. You start SAPinst [page 62].
2. On the Welcome screen, choose <SAP System> Software Life-Cycle Options Additional Preparation
Options 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. If you want to make a change, select the relevant parameters and choose Revise.
4. To start the Prerequisite Checker, choose Start.

Result
The Prerequisite Check Results screen displays the results found. If required, you may also check the
results in file prerequisite_checker_results.html, which you find in the installation directory.

03/28/2008 PUBLIC 37/164

3 Preparation

3.1.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:

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

Hardware Requirements for a Central System

Hardware Requirement Requirement How to Check
Minimum disk space n Database Software: To check disk space:
1 GB (x64) 1. Choose Start Control Panel
2 GB (IA64) Administrative Tools Computer
n SAP system files (not including paging Management Storage Disk
file): Management .
5 GB (x64)
8 GB (IA64) 2. Right-click the drive and choose
n SAP database files (not including Properties.
paging file):
76 GB
n 4.3 GB of temporary disk space for every
required installation DVD that you
have to copy to a local hard disk
Minimum RAM 4 GB To check RAM:
In the Windows Explorer, choose
Help About Windows .
Paging file size 1 times RAM plus 8 GB To check paging file size:
1. Choose Start Control Panel
System .
2. Choose Advanced (Windows Server
2003) or Advanced system settings
(Windows Server 2008).
3. Select Performance Settings
Advanced .
4. If required, in section Virtual memory,
choose Change.
Suitable backup system ‒

38/164 PUBLIC 03/28/2008

3 Preparation

Software Requirements for a Central System

Software
Requirement Requirement How to Check
Windows n English international 64-bit version of one of To check your Windows version:
operating the following Windows Server Editions: 1. Choose Start All Programs
system l Windows Server 2003 Accessories Command Prompt
u Windows Server 2003 Standard Edition
2. Enter the command winver
u Windows Server 2003 Enterprise Edition
u Windows Server 2003 Datacenter Edition
l Windows Server 2008
u Windows Server 2008 for Itanium-Based
Systems Edition

Caution
When this guide was published, Windows
Server 2008 had not yet been released for your
SAP system.
For up-to-date information on the
released operating system versions for
your SAP product and database, see
the Product Availability Matrix (PAM) at
http://service.sap.com/pam .

n For any version of Windows Server, you need the
latest supported service pack
n A suitable Windows Resource Kit is strongly
recommended
Database n Database server software for Oracle 10g ‒
software n Current Oracle patch set and hot fix, if available

Note
For more information about the current patch
set, see SAP Note 871735

3.1.3 Requirements for a Distributed System

This section provide 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:

03/28/2008 PUBLIC 39/164

3 Preparation

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 not
for 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

Hardware
Minimum disk space n Database software: To check disk space:
1 GB (x64) 1. Choose Start Control Panel
n Database instance (not including Management Storage Disk
paging file): Management .
76 GB
n Central instance (not including 2. Right-click the drive and choose
paging file): Properties.
5 GB (x64)
8 GB (IA64)
l In addition you require 4 GB (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 required
installation DVD that you have to copy
to a local hard disk:
4.3 GB
Minimum RAM 2 GB To check RAM:
In the Windows Explorer, choose

40/164 PUBLIC 03/28/2008

3 Preparation

Hardware
Paging file size n Database instance: To check paging file size:
1.5 times RAM 1. Choose Start Control Panel
n Central instance: System .
1 times RAM plus 8 GB
2. Choose Advanced (Windows Server
n Dialog instance (optional):
1 times RAM plus 8 GB 2003) or Advanced system settings
(Windows Server 2008).
3. Select Performance Settings
Advanced .
4. If required, in section Virtual memory,
choose Change.
Suitable backup system ‒

Software Requirements for a Distributed System

Software
Windows n English international 64-bit version of one of To check your Windows version:
operating the following Windows Server Editions: 1. Choose Start All Programs

03/28/2008 PUBLIC 41/164

3 Preparation

Software
u Windows Server 2003 Standard Edition 2. Enter the command winver
u Windows Server 2008 for Itanium-Based
Systems Edition

Caution
When this guide was published, Windows
Server 2008 had not yet been released for your
SAP system.
For up-to-date information on the
released operating system versions for
your SAP product and database, see the
Product Availability Matrix (PAM) at
http://service.sap.com/pam.

n For any version of Windows Server, you need the
latest supported service pack
n A suitable Windows Resource Kit is strongly
recommended
Database n Database instance: ‒
software l Database server software for Oracle 10g
l Current Oracle patch set and hot fix, if
available.
For more information about the current patch
set, see SAP Note 871735


3.1.4 Requirements for a High-Availability System

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

42/164 PUBLIC 03/28/2008

3 Preparation

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 on
Microsoft Windows. The cluster must be included in the Microsoft list of certified clusters and its
components. 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 Validation
Report must 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 on
the 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 shared
disks that can be reached by the MSCS nodes via a shared bus.
All software ‒ except the Windows operating system, the Oracle home directory, 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 Components to Disks for MSCS [page 120].

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)

03/28/2008 PUBLIC 43/164

3 Preparation

n Central instance
n Dialog instance

Note

n The listed values are sufficient for development systems or quality assurance systems but not
for production systems.
n If you install several SAP instances on one host, you need to add up the requirements.

Hardware Requirements for a High-Availability System

Hardware
Require-
ment Requirement How to Check
Minimum n Database Software: To check disk space:
disk space 1 GB (x64) 1. Choose Start Control Panel
n ABAP central services instance (ASCS) Management Storage Disk
(not including paging file): Management .
5 GB (x64)
8 GB (IA64) 2. Right-click the drive and choose
Properties.
l In addition you require 4 GB (x64), or 8 GB (IA64)
per additional platform.
n Database instance (not including paging file):
76 GB
n Enqueue replication server instance (ERS) (not
including 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 installation
DVD that you have to copy to a local hard disk:
4.3 GB
Minimum 2 GB To check RAM:
RAM In the Windows Explorer, choose

44/164 PUBLIC 03/28/2008

3 Preparation

Hardware
Require-
ment Requirement How to Check
Paging file n ABAP central services instance (ASCS): To check paging file size:
size 1 times RAM plus 1 GB 1. Choose Start Control Panel
n Database instance: System .
1.5 times RAM
2. Choose Advanced (Windows
n Enqueue replication server instance (ERS):
1 times RAM plus 1 GB Server 2003) or Advanced system
settings (Windows Server 2008).
n Central instance:
1 times RAM plus 8 GB 3. Select Performance Settings
n Dialog instance: Advanced .
1 times RAM plus 8 GB 4. If required, in section Virtual
memory, choose Change.

Note
You must adjust the size of the
paging file on all MSCS nodes.
Suitable ‒
backup
system

Software Requirements for a High Availability System

Software
Windows n English international 64-bit version of one To check your Windows version:
operating of the following Windows Server Editions: 1. Choose Start All Programs
u Windows Server 2003 Enterprise
Edition 2. Enter the command winver
u Windows Server 2003 Datacenter
Edition Note
n Windows Server 2003 only:
u Windows Server 2008 Enterprise You must set up the MSCS Cluster
Edition
Service as described in the Microsoft
u Windows Server 2008 Datacenter documentation. During this
Edition
setup you are asked for a Windows
u Windows Server 2008 for Domain Account to run the Cluster
Itanium-Based Systems Edition
Service. We strongly recommend
creating an account different from
Caution the <sapsid>adm user, for example
When this guide was published, Windows ClusterServiceuser=sapprdcladm,
Server 2008 had not yet been released for where Clustername=sapprdcl.
your SAP system. n Windows Server 2008 only:
For up-to-date information on the You must add the operating system
released operating system versions for feature Failover Clustering on all MSCS

03/28/2008 PUBLIC 45/164

Ecc6 sr3 ora_win_instguide

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (15)

Semelhante a Ecc6 sr3 ora_win_instguide

Semelhante a Ecc6 sr3 ora_win_instguide (20)

Último

Último (20)

Ecc6 sr3 ora_win_instguide