inst guide - sap erp ehp5 - windows - db2 (abap)

of 196 /196
Installation Guide SAP ERP 6.0 Including SAP Enhancement Package 5 - Technical Usage “Central Applications” ABAP on Windows: IBM DB2 for Linux, UNIX, and Windows Based on SAP NetWeaver 7.0 Including Enhancement Package 2 Target Audience System Administrators Technical Consultants PUBLIC Document version: 1.0 – 2010-12-20

Author: ngoc-vu-tuan

Post on 18-Apr-2015

182 views

Category:

Documents


6 download

Embed Size (px)

TRANSCRIPT

Installation Guide SAP ERP 6.0 Including SAP Enhancement Package 5 - Technical Usage Central Applications ABAP on Windows: IBM DB2 for Linux, UNIX, and WindowsBased on SAP NetWeaver 7.0 Including Enhancement Package 2Target Audience System Administrators Technical Consultants

PUBLIC Document version: 1.0 2010-12-20

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 installingSAP 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/196

PUBLIC

2010-12-20

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

2010-12-20

Initial Version

2010-12-20

PUBLIC

3/196

Table of Contents

Chapter 1 1.1 1.2 1.3 Chapter 2 2.1 2.2 2.3 2.4 2.5 Chapter 3 3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.3 3.4 3.5 3.6 3.6.1 3.6.2 3.6.3 3.6.4 3.6.5

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . Central System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Prerequisite Checker in Standalone Mode (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for a Central System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Host Agent as a Separate Installation . . . . . . . . . . . . . . . Planning User and Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain or Local Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup of Database Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Directories for the Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directory Structure of the New DB2 Client Connectivity . . . . . . . . . . . . . . . . DB2 Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization of Database Size on Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 15 16 17 17 19 21 21 22 23 24 26 29 33 33 35 36 44 45 46 47 48 50 51

4/196

PUBLIC

2010-12-20

3.6.6 3.7 3.8 Chapter 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 Chapter 5 5.1 5.2 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 Chapter 6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8

Data Safety and Performance Considerations for Production Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 SAP Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Internet Pricing and Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling the Windows Server 2008 (R2) Firewall . . . . . . . . . . . . . . . . . . . . . . . Performing Basic Windows Preparation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . Required User Authorization for Running SAPinst . . . . . . . . . . . . . . . . . . . . . Preparing the SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Front-End Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating the SAP Solution Manager Key . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading JCE Policy Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entries in the Services File Created by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applying the Latest Kernel and Support Package Stacks . . . . . . . . . . . . . . . . . Creating Symbolic Links on Windows Server 2008 (R2) for Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . . . . Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 57 58 58 61 62 63 64 64 64 65 71 71 72 77 77 78 79 80 82 83 85 85 86 87 87 88 88 89 89

2010-12-20

PUBLIC

5/196

6.9 6.10 6.11 6.12 6.13 6.14 6.15 6.16 6.17 6.18 6.19 6.20

Performing Post-Installation Steps for the ABAP Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Enabling the Database for Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Enabling Recoverability of the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Performing a Full System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Configuring the Connection to a Central System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Activating Internet Pricing and Configurator . . . . . . . . . . . . . . . . . . . . . . . . . 99 Implementing SAP ERP ABAP Add-On Components . . . . . . . . . . . . . . . . . . . 99 Performing the Client Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Post-Installation Steps for the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . 100 Post-Installation Steps for the Host Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Accessing Configuration Documentation in SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a Domain Installation Without Being a Domain Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . . MCOD Tablespaces and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dialog Instance Installation for an Upgraded System only: Updating Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Tablespaces Manually (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Database Partitions to a Database Instance . . . . . . . . . . . . . . . . . . . . . Installing a Near-Line Storage Database for an SAP NetWeaver BW System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Windows Server 2008 Firewall . . . . . . . . . . . . . . . . . . . . . . . . Implementing Single Sign-On with Microsoft Kerberos SSP for Your SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimizing the Database Size after the Installation . . . . . . . . . . . . . . . . . . . . Installing Windows Application Servers in a UNIX Environment . . . . . . . . . . SAP System Security on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic Creation of Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . . 103 104 107 110 111 112 116 117 119 120 122 123 124 125 126 127 128 131

Chapter 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.11 7.12 7.13 7.14 7.15 7.16 7.17

6/196

PUBLIC

2010-12-20

7.18 7.18.1 7.19 7.20 7.20.1 7.20.2 7.20.3 7.20.4 Chapter 8 8.1 8.2 8.2.1 8.2.1.1 8.2.1.2 8.2.1.3 8.2.1.4 8.2.2 8.2.3 8.2.4 8.2.5 8.3 8.3.1 8.3.2 8.3.3 8.3.4 8.3.5 8.4 8.4.1 8.4.2 8.4.3 8.4.4 8.4.5 8.4.6 8.4.7

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting the Database Instance and Database Software Manually (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting the Database (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a DB2 Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a Database Schema Manually (Optional) . . . . . . . . . . . . . . . . . . . . . Deleting the DB2 Software Installation (Optional) . . . . . . . . . . . . . . . . . . . . . High Availability with Microsoft Cluster Service . . . . . . . . . . . . . . . . . . Installation Checklist for a High-Availability System . . . . . . . . . . . . . . . . . . . Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Configuration in MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP System Components in an MSCS Configuration . . . . . . . . . . . . . . . . . . Multiple SAP Systems In One MSCS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . Multiple SAP Systems In Multiple MSCS Clusters . . . . . . . . . . . . . . . . . . . . . Enqueue Replication Server in an MSCS Configuration . . . . . . . . . . . . . . . . . Distribution of SAP System Components to Disks for MSCS . . . . . . . . . . . . . Directories in an MSCS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Addresses in an MSCS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining and Determining IP Addresses for MSCS . . . . . . . . . . . . . . . . . . . . Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Drive Letters for MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Host Names to IP Addresses for MSCS . . . . . . . . . . . . . . . . . . . . . . . Checking the Mapping of Host Names for MSCS . . . . . . . . . . . . . . . . . . . . . . Windows Server 2003: Preparing an Existing SAP System to Support Multiple Systems in one Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Server 2003: Preparing the Installation of Multiple SAP Systems in MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the First MSCS Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Database Instance on an MSCS Node . . . . . . . . . . . . . . . . . . . . Preparing the Additional Node for MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Database for MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Additional MSCS Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Central Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

132 132 133 135 135 136 137 138 141 143 145 145 145 148 150 151 152 156 157 161 163 163 163 164 165 168 171 171 172 173 174 175 177 177

2010-12-20

PUBLIC

7/196

8.5 8.5.1 8.5.1.1 8.5.1.2 8.6 8.6.1 8.6.2 8.6.3 Chapter A A.1 A.2

Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Checks for Enqueue Replication Server . . . . . . . . . . . . . . . . Checking the Status of the Enqueue Replication Server with ENSMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring the Lock Table During Failover with ENQT . . . . . . . . . . . . . . . . Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving MSCS Groups or Services and Applications . . . . . . . . . . . . . . . . . . . . Rebooting During the Installation or Conversion for MSCS . . . . . . . . . . . . . Starting and Stopping the SAP System in an MSCS Configuration . . . . . . . . .

178 179 179 180 181 182 183 183

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Online Information from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

8/196

PUBLIC

2010-12-20

1

Introduction

1 Introduction

This document explains how to install SAP ERP 6.0 including SAP enhancement package 5 - technical usage Central Applications ABAP. You perform the installation using SAPinst. SAP ERP 6.0 including SAP enhancement package 5 - technical usage Central Applications is based on the technology of SAP NetWeaver 7.0 including enhancement package 2. 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 read the corresponding Master Guides before you start with this installation guide. The Master Guides are available as follows: http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package for SAP ERP 6.0 You can install SAP ERP 6.0 including SAP enhancement package 5 - technical usage Central Applications with the following software units: SAP ERP Central Component (ECC)NOTE

You also install SAP NetWeaver Application Server ABAP (AS ABAP) with SAP ERP Central Component. 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.Constraints

You need to consider the following constraints before you start your installation: Your operating system platform must be 64-bit.NOTE

The only instance, you can still install on 32-bit is the dialog instance. Windows Server 2008 for Itanium-based systems editions is not supported. As of Enhancement Package 2 for SAP NetWeaver 7.0, the installation package contains only the DB2 V9.7 installation DVDs. If you want to install your SAP system with DB2 V9.1 or DB2 V9.5, you can do one of the following: Download the DB2 software from SAP Service Marketplace at:http://service.sap.com/swcenter-3pmain

2010-12-20

PUBLIC

9/196

1 1.1

Introduction New Features

Request the physical shipment of the DB2 V9.1 or DB2 V9.5 media using a customer message on component XX-SER-SWFL-SHIP. The SAP system installation on Windows Server 2003 (Itanium platform) is only possible with DB2 V9.1. As of DB2 V9.5, the installation of an SAP system on the Windows platform IA64 is no longer supported.Naming Conventions

SAP system refers to SAP ERP 6.0 including SAP enhancement package 5 - technical usage "Central Applications. ABAP system refers to SAP ERP 6.0 including SAP enhancement package 5 - technical usage "Central Applications ABAP diagnostics refers to diagnostics in SAP Solution Manager. diagnostics agent refers to the agent of diagnostics in SAP Solution Manager.IBM Product Terminology

DB2 V9.7 refers to IBM DB2 Version 9.7 for Linux, UNIX, and Windows. DB2 V9.5 refers to IBM DB2 Version 9.5 for Linux, UNIX, and Windows. DB2 V9.1 refers to IBM DB2 Version 9.1 for Linux, UNIX, and Windows.NOTE

If content in this document relates to all versions, no version number is mentioned.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.Profiling for High AvailabilityOnly 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.1 New FeaturesThe 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

Running SAPinst with accessibility mode: Keyboard access:

10/196

PUBLIC

2010-12-20

1 1.1 Area

Introduction New Features Description

High Availability

This feature is generally available for all operating systems. High-color contrast: This feature is derived from the Windows display properties. For more information, see Running SAPinst in Accessibility Mode [page 82]. Custom font setting: This feature is derived from the Windows display properties. For more information, see Running SAPinst in Accessibility Mode [page 82]. New installation options for a high-availability system in a Microsoft Cluster SAP adapted the installation procedure for a high-availability system on Windows to make it easier and less error-prone for customers: First Cluster Node This installation option now includes the previously separate options Central Services Instance for ABAP (ASCS), Central Services Instance (SCS), Enqueue Replication Server (ERS), and First MSCS Node. It performs the following steps: Installs the central services instance for ABAP (ASCS) and prepares this host as the SAP global host Installs the enqueue replication server instance (ERS) for the ASCS instance Installs the host agent Creates the SAP cluster group on the first cluster node and adds the ASCS instance to the SAP cluster group For local instances, such as ERS, host agent, diagnostic agent, primary application server, or additional application server instance, you can only select local drives, whereas for the ASCS instance you can only select shared drives. The quorum disk is not available in the list of shared drives. Additional Cluster Node This installation option includes the previous options Enqueue Replication Server, and Additional MSCS Node. It performs the followings steps: Configures the additional cluster node to run the SAP cluster group Installs the enqueue replication server instance (ERS) for the ASCS instance on a local drive Installs the host agent on a local drive As of Windows Server 2008 (R2), the Windows cluster feature is called Failover Clustering. For practical reasons we are continuing to use the general abbreviation MSCS in this guide.

2010-12-20

PUBLIC

11/196

1 1.1 Area

Introduction New Features Description

Additional ABAP Technical Usage

The installation of SAP ERP 6.0 including enhancement package 5 already contains the technical usage Central applications. If you want to install an additional ABAP technical usage, you have to use transaction SAINT.

Database-Specific Features Area Description

Supported database versions

The installation of SAP systems based on SAP NetWeaver 7.0 including EHP2 is supported for the following DB2 database versions: DB2 V9.7 DB2 V9.5 DB2 V9.1 As of DB2 V9.1, you can have multiple DB2 installations on one physical machine. The database installations are independent of each other and can have different Fix Pack levels as well as different configuration settings, and so on. By default, the software is installed in the following directory::\db2\db2\db2_software

Installation of near-line storage database

As of SAP NetWeaver 7.0 incl. EHP2, you can install a near-line storage database using SAPinst. The near-line storage database is a remote DB2 database that you can use to store BW data that is not frequently used.NOTE

You can only install the near-line storage database on DB2 V9.7 for Linux, UNIX,and Windows or higher. For more information, see Installing a Near-Line Storage Database for an SAP NetWeaver BW System [page 122]. As of DB2 V9.7, tables of the newly created database automatically use inline LOBs. That is, small LOBs up to a specified size are now stored together with the table data. LOBs that are larger than the specified size are transparently stored in the LOB storage object. Inlined LOBs are also subject to row compression. With inline LOBs, performance improves and disk space can be saved. For that reason, the type mapping for several ABAP dictionary types of the AS ABAP was adapted to use LOBs instead of LONG VARCHARs. For more information, see SAP Note 1351160. As of DB2 V9.7, if you select Use DB2's Row Compression during the dialog phase of SAPinst, newly created tables are also enabled for index compression. For more information, see SAP Note 1351160 and Optimization of Database Size on Disk [page 51]. SAPinst automatically installs and uninstalls the database software.

Inline LOBs and long VARCHAR replacement

Index compression

DB2 software installation

12/196

PUBLIC

2010-12-20

1 1.2

Introduction SAP Notes for the Installation

1.2 SAP Notes for the InstallationYou 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

998833

1323537 1313850 1387319

1352690

702175

1134975

855498 73606 1067221

789220

774615

Release Restrictions SAP ERP 6.0 - At the time of the release of SAP ERP 6.0 including Enhancement Packages SAP enhancement package 5, limitations affect the productive usage of certain functions. This note provides customer information on these restrictions. Release Info SAP Enhancement SAP Enhancement Package 5 for SAP ERP 6.0 Package 5 for SAP ERP 6.0 release information. Release Restrictions for SAP EHP Customer information on restrictions in the 2 for SAP NetWeaver 7.0 production use of certain functions. SAP NetWeaver 7.02/Business Windows-specific information about the SAP Suite 7i2010: Windows system installation and corrections to this documentation. DB6: SAP NetWeaver 7.0 incl. EHP Database-specific information about the SAP 2/Business Suite 7i2010 Windows system installation (ABAP and Java) and corrections to this documentation. DB6: Supporting several database Platform-specific additional information about partitions with DB2 the support of multiple partitions with DB2 for Linux, UNIX, and Windows DB6: MSCS Installation on IBM Platform-specific additional information about DB2 for Linux, UNIX, and the installation of Microsoft Cluster on IBM DB2 Windows for Linux, UNIX, and Windows. Installation Prerequisite Checker SAP Software on UNIX, Windows, and IBM i: Checking OS Dependencies Supported Languages and Code Information on possible languages and language Pages combinations in SAP systems Central Note for Heterogeneous This SAP Note and its related SAP Notes describe Installation the released operating system and database combinations for heterogeneous SAP systems landscapes. Support Package level for Information about the ABAP Support Package NetWeaver Installations/ levels and kernel patch levels contained in the Upgrades current SAP NetWeaver release. Support Package levels of ERP/ Information about the ABAP Support Package ECC installations/upgrades levels and kernel patch levels contained in the current SAP ERP release.

2010-12-20

PUBLIC

13/196

1 1.3

Introduction How to Use This Guide Title Description

SAP Note Number

1258912

PLM Core 7.00 Release Notes and Information and references to other notes about Information installing PLM Core 7.00 and importing PLM Core 7.00 Support Packages.

1.3 How to Use This Guide1. You decide on the installation option that you want to install. The following installation options are described in this installation guide: Central system Distributed system Only valid for: HA (MSCS) |

High-availability systemEnd of: HA (MSCS) |

2.

Dialog instances Host Agent as a separate installation For more information, see Installation Options Covered by This Guide [page 15]. You follow the list of steps at the beginning of each installation phase: Planning [page 21] Preparation [page 57] Installation [page 71] Post-Installation [page 85] High Availability with Microsoft Cluster Service (if relevant) [page 141]NOTE

This applies to all installation options except the Host Agent as a Separate Installation [page 19]. This installation option has its own section in Additional Information [page 103]. In Additional Information [page 103] you can find special installation options and more information about how to perform certain steps described in the main part of the guide.

14/196

PUBLIC

2010-12-20

2 2.1

Installation Options Covered by this Guide Central System

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 15] Distributed system [page 16] Only valid for: HA (MSCS) |

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

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

2.1 Central SystemYou can install a central system on a single host. These are the following instances: Database instance (DB instance) Central instance Optionally you can install one or more dialog instances. For more information, see Dialog Instance [page 17]. The following figure shows an example of SAP instances in a central system.

2010-12-20

PUBLIC

15/196

2 2.2

Installation Options Covered by this Guide Distributed System

Figure 1:

Central ABAP System

Optionally you can install one or more dialog instances. For more information, see Dialog Instance [page 17].

2.2 Distributed SystemIn a distributed system, every instance can run on a separate host. These are the following instances: Database instance (DB instance) Central instanceNOTE

You must use the SAP global host as your central instance host. Optionally you can install one or more dialog instances. For more information, see Installation of a Dialog Instance [page 17].

16/196

PUBLIC

2010-12-20

2 2.3

Installation Options Covered by this Guide High Availability System

Figure 2:

Distributed ABAP System

Only valid for: HA (MSCS) |

2.3 High Availability SystemFor 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 145].End of: HA (MSCS) |

2.4 Dialog InstanceYou 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 hostNOTE

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.

2010-12-20

PUBLIC

17/196

2 2.4

Installation Options Covered by this Guide Dialog Instance NOTE

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

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 44].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 15].Dialog Instance for a Distributed System

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

18/196

PUBLIC

2010-12-20

2 2.5

Installation Options Covered by this Guide Host Agent as a Separate Installation

Figure 4:

Dialog Instance for a Distributed System

For more information, see Distributed System [page 16].Only valid for: HA (MSCS) |

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

2.5 Host Agent as a Separate InstallationUsing 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 117] describes how to perform the installation.

2010-12-20

PUBLIC

19/196

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

3 3.1

Planning Planning Checklist

3 Planning

3.1 Planning ChecklistThis section includes the planning steps that you have to perform for the following installation options: Central, distributed, or high-availability system Dialog instance Detailed information about the steps is available in the relevant chapter.Prerequisites

1.

2.

You have planned your SAP system landscape according to the Master Guide at http:// service.sap.com/erp-inst and the Technical Infrastructure Guide at https:// cw.sdn.sap.com/cw/community/docupedia/tig. You have decided on your installation option [page 15].

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. 2. 3. 4. 5. 6. 7. 8. You check the hardware and software requirements [page 22] on each host. You plan how to set up user and access management [page 35]. You identify basic SAP system installation parameters [page 36]. You decide whether you want to perform a domain or local installation [page 44]. You carefully plan the setup of your database [page 45]. You decide on the transport host to use [page 54]. You decide if you want to use Internet Pricing and Configurator [page 55].Only valid for: HA (MSCS) |

To install a high-availability system with Microsoft Cluster Service (MSCS), you perform the MSCS-specific planning steps [page 143].End of: HA (MSCS) |

9.

You can continue with Preparation [page 57].

Dialog Instance

1. 2.

You check the hardware and software requirements [page 22] for the installation host on which you want to install one or more dialog instances. You identify basic SAP system installation parameters [page 36].

2010-12-20

PUBLIC

21/196

3 3.2

Planning Hardware and Software Requirements

3.

You can now continue with Preparation [page 57].

3.2 Hardware and Software RequirementsYou 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. 2.

Check the Product Availability Matrix at http://service.sap.com/pam for supported operating system releases. 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 23]. Integrated in SAPinst (mandatory) during the installation process For more information, see Running SAPinst [page 72].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 24] Distributed system [page 26] Only valid for: HA (MSCS) |

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

3.

Dialog instance [page 33] Host agent as a separate installation [page 33] 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 .

22/196

PUBLIC

2010-12-20

3 3.2

Planning Hardware and Software Requirements

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 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 65].Procedure

1. 2. 3.

You start SAPinst [page 72]. On the Welcome screen, choose Software Life-Cycle Options Additional Preparations Prerequisites Check . 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. To start the prerequisites check, choose Next.

4.

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.

2010-12-20

PUBLIC

23/196

3 3.2

Planning Hardware and Software Requirements

3.2.2 Requirements for a Central SystemIf 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. 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

SAP system files (not including paging To check disk space: file): 1. Windows Server 2003: 5 GB (x64) Choose Start All Programs 8 GB (IA64) Administrative Tools Computer Management Disk Management . Database Instance For more information about the 2. Windows Server 2008 (R2): required disk space, see SAP Note Choose Start All Programs 1352690. Administrative Tools Storage Computer Management Disk NOTE Management . For safety reasons (system failure), the file systems must be 3. Right-click the drive and choose Properties. distributed physically over several disks, or RAIDtechnology must be used. 4.3 GB of temporary disk space for every required installation medium that you have to copy to a local hard disk 4 GB To check RAM: Choose Start Control Panel System .NOTE

Minimum RAM

Paging file size

For more information, see SAP Note 1518419.

Windows Server 2008 R2: If System is not visible, change View by: from Category into Large icons. To check paging file size: 1. Choose Start Control Panel System .NOTE

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

24/196

PUBLIC

2010-12-20

3 3.2

Planning Hardware and Software Requirements Requirement How to Check

Hardware Requirement

2. 3. 4. 5.

Windows Server 2003: Choose Advanced. Windows Server 2008 (R2): Choose Advanced system settings. In section Performance, select Settings... Advanced . If required, in section Virtual memory, choose Change.NOTE

Do not select Automatically managed paging file size for all drives. Suitable backup system Software Requirements for a Central System Software Requirement Requirement How to Check

Windows English 64-bit version of one of the following To check your Windows version: operating system 1. Choose Start All Programs Windows Server Editions: Accessories Command Windows Server 2003 Prompt Windows Server 2003 Standard Edition Windows Server 2003 Enterprise Edition 2. Enter the command winver Windows Server 2003 Datacenter EditionCAUTION

The SAP system installation on Windows Server 2003 (Itanium platform) is only possible with DB2 V9.1. Windows Server 2008 (R2) CAUTION

Windows Server 2008 (R2) for Itanium-based systems editions is not supported. Windows Server 2008 R2 is only supported with DB2 V9.5 and DB2 V9.7. Windows Server 2008 (R2) Standard Edition Windows Server 2008 (R2) Enterprise Edition Windows Server 2008 (R2) Datacenter EditionNOTE

For up-to-date information on the released and supported operating system versions for your SAP product and database, see the

2010-12-20

PUBLIC

25/196

3 3.2

Planning Hardware and Software Requirements

Software Requirement

Requirement

How to Check

Product Availability Matrix (PAM) at http:// service.sap.com/pam.CAUTION

Database software

Do not use any other locales than en_US. For any version of Windows Server, you need the latest supported service pack Windows Server 2003: A suitable Windows Resource Kit is strongly recommended. Windows Server 2003: Updated CPU drivers For more information, see SAP Note 1036194. DB2 V9.7 DB2 V9.5 DB2 V9.1 (automatically installed by SAPinst).CAUTION

For the installation of your SAP system, only the English version of DB2 is supported. You must only use the DB2 software provided by the SAP installation DVDs. For more information, see SAP Note 101809.

3.2.3 Requirements for a Distributed SystemThis 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: Database instance Central instance Dialog instance (optional)NOTE

The listed values are sufficient for development systems or quality assurance systems but not for production systems. 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.

26/196

PUBLIC

2010-12-20

3 3.2

Planning Hardware and Software Requirements

Hardware Requirements for a Distributed System Hardware Requirement Requirement How to Check

Minimum disk space

Database instance For more information about the required disk space, see SAP Note 1352690.NOTE

Minimum RAM

For safety reasons (system failure), the file systems must be distributed physically over several disks, or RAID-technology must be used. 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 Dialog instance (optional) (not including paging file): 2.5 GB (x64) 5 GB (IA64) Temporary disk space for every required installation medium that you have to copy to a local hard disk: 4.3 GB 4 GB To check RAM: Choose Start Control Panel System .NOTE

To check disk space: 1. Windows Server 2003: Choose Start All Programs Administrative Tools Computer Management Disk Management . 2. Windows Server 2008 (R2): Choose Start All Programs Administrative Tools Storage Computer Management Disk Management . 3. Right-click the drive and choose Properties.

Paging file size

For more information, see SAP Note 1518419.

Windows Server 2008 R2: If System is not visible, change View by: from Category into Large icons. To check paging file size: 1. Choose Start Control Panel System .NOTE

2. 3.

Windows Server 2008 R2: If System is not visible, change View by: from Category into Large icons. Windows Server 2003: Choose Advanced. Windows Server 2008 (R2): Choose Advanced system settings.

2010-12-20

PUBLIC

27/196

3 3.2

Planning Hardware and Software Requirements Requirement How to Check

Hardware Requirement

4. 5.

In section Performance, select Settings... Advanced . If required, in section Virtual memory, choose Change.NOTE

Do not select Automatically managed paging file size for all drives. Suitable backup systemSoftware Requirements for a Distributed System Software Requirement Requirement How to Check

Windows operating system

To check your Windows version: English 64-bit version of one of the following 1. Choose Start All Programs Windows Server Editions: Accessories Command Windows Server 2003 Prompt Windows Server 2003 Standard Edition Windows Server 2003 Enterprise Edition 2. Enter the command winver Windows Server 2003 Datacenter Edition Windows Server 2008 (R2) CAUTION

Windows Server 2008 (R2) for Itanium-based systems editions is not supported. Windows Server 2008 R2 is only supported with DB2 V9.5 and DB2 V9.7. Windows Server 2008 (R2) Standard Edition Windows Server 2008 (R2) Enterprise Edition Windows Server 2008 (R2) Datacenter EditionCAUTION

Database software

Do not use any other locales than en_US. For any version of Windows Server, you need the latest supported service pack Windows Server 2003: A suitable Windows Resource Kit is strongly recommended. Windows Server 2003: Updated CPU drivers For more information, see SAP Note 1036194. Database instance: DB2 V9.7 DB2 V9.5 DB2 V9.1 (automatically installed by SAPinst). Central instance / dialog instance:

28/196

PUBLIC

2010-12-20

3 3.2

Planning Hardware and Software Requirements

Software Requirement

Requirement

How to Check

DB2 V9.7 CLI Driver / DB2 V9.7 JDBC Driver DB2 V9.5 CLI Driver / DB2 V9.5 JDBC Driver DB2 V9.1 CLI Driver / DB2 V9.1 JDBC Driver (automatically installed by SAPinst) For more information, see SAP Note 101809.CAUTION

For the installation of your SAP system, only the English version of DB2 is supported. You must only use the DB2 software provided by the SAP installation DVDs.Only valid for: HA (MSCS) |

3.2.4 Requirements for a High-Availability SystemGeneral Requirements

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: http://www.microsoft.com/whdc/hcl/default.mspx http://www.saponwin.com Windows Server 2008 (R2) only: 1. Check that your cluster hardware is certified for Windows Server 2008 (R2) and has the Windows Server 2008 (R2) logo. 2. 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.

2010-12-20

PUBLIC

29/196

3 3.2

Planning Hardware and Software Requirements

All software except the Windows operating system, the DB2 executables, 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 six 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 152]. 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.Hardware and Software Requirements

The following tables show the hardware and software requirements for the: Central services instance for ABAP (ASCS) Database instance Enqueue Replication Server instance (ERS) Central instance Dialog instance Diagnostics agentNOTE

The listed values are sufficient for development systems or quality assurance systems but not for production systems. 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 Hardware Requirement Requirement How to Check

Minimum disk space

To check disk space: Central services instance for ABAP (ASCS) (not including paging file): 1. Windows Server 2003: 5 GB (x64) Choose Start All Programs 8 GB (IA64) Administrative Tools Computer In addition you require 4 GB (x64), or 8 GB (IA64) Management Disk per additional platform. Management . 2. Windows Server 2008 (R2): Database instance For more information about the required disk space, Choose Start All Programs see SAP Note 1352690.. Administrative Tools Storage

30/196

PUBLIC

2010-12-20

3 3.2

Planning Hardware and Software Requirements

Hardware Requirement

Requirement NOTE

How to Check

Minimum RAM

All software except the Windows operating 3. system, the DB2 executables, and the MSCS software is stored on the shared disks You require at least six shared disks. 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 (x64), or 8 GB (IA64) per additional platform. In addition you require 1.5 GB for the diagnostics agent Dialog instance (not including paging file): 2.5 GB (x64) 5 GB (IA64) Temporary disk space for every required installation medium that you have to copy to a local hard disk: 4.3 GB 4 GB To check RAM: Choose Start Control Panel System .NOTE

Computer Management Disk Management . Right-click the disk and choose Properties.

Paging file size

For more information, see SAP Note 1518419

Windows Server 2008 R2: If System is not visible, change View by: from Category into Large icons. To check paging file size: 1. Choose Start Control Panel System .NOTE

2. 3. 4. 5.

Windows Server 2008 R2: If System is not visible, change View by: from Category into Large icons. Windows Server 2003: Choose Advanced. Windows Server 2008 (R2): Choose Advanced system settings. In section Performance, select Settings... Advanced . If required, in section Virtual memory, choose Change.

2010-12-20

PUBLIC

31/196

3 3.2

Planning Hardware and Software Requirements

Hardware Requirement

Requirement

How to Check NOTE

Do not select Automatically managed paging file size for all drives. You must adjust the size of the paging file on all MSCS nodes. Suitable backup systemSoftware Requirements for a High Availability System Software Requirement Requirement How to Check

Windows operating system

English 64-bit version of one of the following Windows Server Editions: Windows Server 2003 Windows Server 2003 Enterprise Edition Windows Server 2003 Datacenter Edition Windows Server 2008 (R2)CAUTION

To check your Windows version: 1. Choose Start All Programs Accessories Command Prompt 2. Enter the command winverNOTE

Windows Server 2008 (R2) for Itanium-based systems editions is not supported. Windows Server 2008 R2 is only supported with DB2 V9.5 and DB2 V9.7. Windows Server 2008 (R2) Enterprise Edition Windows Server 2008 (R2) Datacenter EditionCAUTION

Windows Server 2003: You must set up the MSCS Cluster Service as described in the Microsoft documentation. During this setup you are asked for a Windows Domain Account to run the Cluster Service. We strongly recommend creating an account different from the adm user, for exampleClusterServiceuser=sapprdc ladm, where Clustername=sapprdcl.

Database software

Do not use any other locales than en_US. For any version of Windows Server, you need the latest supported service pack Windows Server 2003: A suitable Windows Resource Kit is strongly recommended Windows Server 2003: Updated CPU drivers For more information, see SAP Note 1036194. Database instance: DB2 V9.7 DB2 V9.5 DB2 V9.1

Windows Server 2008 (R2): You must add the operating system feature Failover Clustering on all MSCS nodes.

32/196

PUBLIC

2010-12-20

3 3.2

Planning Hardware and Software Requirements

Software Requirement

Requirement

How to Check

(automatically installed by SAPinst). Central instance / dialog instance: DB2 V9.7 CLI Driver / DB2 V9.7 JDBC Driver DB2 V9.5 CLI Driver / DB2 V9.5 JDBC Driver DB2 V9.1 CLI Driver / DB2 V9.1 JDBC Driver (automatically installed by SAPinst)CAUTION

For the installation of your SAP system, only the English version of DB2 is supported. You must only use the DB2 software provided by the SAP installation DVDs. For more information, see SAP Note 101809.End of: HA (MSCS) |

3.2.5 Requirements for the Dialog InstanceFor more information about the hardware and software requirements for the dialog instance, see one of the following sections: Requirements for a Distributed System [page 26] Only valid for: HA (MSCS) |

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

3.2.6 Requirements for the Host Agent as a Separate InstallationIf you want to install the host agent separately, the installation host has to meet the following hardware and software requirements: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.

2010-12-20

PUBLIC

33/196

3 3.2

Planning Hardware and Software Requirements

Hardware Requirements for the Host Agent Hardware Requirement Requirement How to Check

Minimum disk space:

Minimum RAM:

To check disk space: Host agent: 80 MB 1. Windows Server 2003: Choose Start All Programs Temporary disk space for every Administrative Tools Computer required installation medium that you have to copy to a local hard disk: Management Disk Management . 4.3 GB 2. Windows Server 2008 (R2): Choose Start All Programs Administrative Tools Storage Computer Management Disk Management . 3. Right-click the disk and choose Properties. 40 MB To check RAM: Choose Start Control Panel System .NOTE

Paging file size:

For more information, see SAP Note 1518419.

Windows Server 2008 R2: If System is not visible, change View by: from Category into Large icons. To check paging file size: 1. Choose Start Control Panel System .NOTE

2. 3. 4. 5.

Windows Server 2008 R2: If System is not visible, change View by: from Category into Large icons. Windows Server 2003: Choose Advanced. Windows Server 2008 (R2): Choose Advanced system settings. In section Performance, select Settings... Advanced . If required, in section Virtual memory, choose Change.NOTE

Do not select Automatically managed paging file size for all drives. Suitable backup systemSoftware Requirements for the Host Agent Software Requirement Requirement How to Check

Windows operating system:

English 64-bit version of one of the To check your Windows version: following Windows Server Editions:

34/196

PUBLIC

2010-12-20

3 3.3

Planning Planning User and Access Management Requirement How to Check

Software Requirement

Windows Server 2003 Windows Server 2003 Enterprise Edition Windows Server 2003 Datacenter Edition Windows Server 2008 (R2) Windows Server 2008 (R2) Enterprise Edition Windows Server 2008 (R2) Datacenter EditionCAUTION

1. 2.

Choose Start All Programs Accessories Command Prompt . Enter the command winver.

Windows Server 2008 (R2) for Itaniumbased systems editions is not supported. Windows Server 2008 R2 is only supported with DB2 V9.5 and DB2 9.7.CAUTION

Database software:

Do not use any other locales than en_US. Windows Server 2003: For any version of Windows Server, you need the latest supported service pack. Windows Server 2003: A suitable Windows Resource Kit is strongly recommended.

3.3 Planning User and Access ManagementYou 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 Central User Administration (CUA). Use an LDAP directory as the data source for user data.ProcedureUsing Central User Management

1.

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

2010-12-20

PUBLIC

35/196

3 3.4

Planning Basic SAP System Installation Parameters

2.

Add the system to Central User Administration (CUA). For more information, see Configuring User Management [page 87].

Using an LDAP directory as Source for User Data

1. 2.

You install your SAP system as described in this installation guide. Configure the user management of the newly installed SAP system to use and LDAP directory. For more information, see Configuring User Management [page 87].

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/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 2) 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 ParametersSAPinst prompts for input parameters during the Define Parameters phase of the installation. You can install your SAP system either in Typical or Custom mode: Typical If 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 ID SAP system profile directory only for systems with instances on separate hosts Master password Java Runtime Environment (JRE) only prompted if not already available on the installation host Java Cryptographic Extension (JCE) Unlimited Strength Jurisdiction Policy files archive only prompted if not already available on the installation host System Landscape Directory (SLD) destination SAP Solution Manager Key If you want to change any of the default settings, you can do so on the Parameter Summary screen. Custom If 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.

36/196

PUBLIC

2010-12-20

3 3.4

Planning Basic SAP System Installation Parameters

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 Parameters For all other installation parameters, use the F1 help in the SAPinst screens.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. 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

SAP System Instance Numbers

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. 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 104].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: Operating system users (for example adm, SAPService)CAUTION

If you did not create the operating system users manually before the installation, SAPinst creates them with the common master password. In this case, make sure

2010-12-20

PUBLIC

37/196

3 3.4

Planning Basic SAP System Installation Parameters Description

Parameters

that the master password meets the requirements of your operating system and of your database. ABAP users SAP* and DDICCAUTION

SAPinst applies the master password to users SAP*and DDIC for SAP system clients 000 and 001 only, but not to users SAP*, DDIC, and EARLYWATCH in SAP system client 066. Instead, SAPinst always assigns the following passwords to these users in client 066: SAP*: 06071992 EARLYWATCH: support See also Ensuring User Security [page 94]. Database users Secure Store key phrase For more information, see table line Key Phrase for Secure Store Settings.NOTE

If a user already exists, you are prompted to confirm the password for this user. Password policy The 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) 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 PortCAUTION

The message server port number must be unique for the SAP system on all hosts. If there are several message port numbers on one host, all must be unique. Port number of the SAP Message Server: If you do not specify a value, the default port number is used. ABAP Message Server 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, 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. For more information about the parameters used for message server ports, see SAP Note 821875. A valid JRE is required for the installation with SAPinst. For more information about JRE versions supported by SAP and about how to install them, see Installing the Java Runtime Environment [page 64].

Java Runtime Environment (JRE)

38/196

PUBLIC

2010-12-20

3 3.4

Planning Basic SAP System Installation Parameters Description

Parameters

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. For more information, see Configuring Fully Qualified Domain Names (FQDN) in Performing PostInstallation Steps for the ABAP Application Server [page 89].EXAMPLE

Path toSAPCRYPTO.SAR

Password of Operating System Users

If your application server host is called kirk.wdf.sap.com, the DNS Domain Name is wdf.sap.com. The SAP Cryptographic Library is required to enable Secure Sockets Layer (SSL) encryption of HTTP connections. If you do not have SAPCRYPTO.SAR available, you can download it from: http://service.sap.com/swdc Installations and Upgrades Search for the term SAP Cryptogaphic Software After the installation has finished, you have to perform some post-installation steps to configure AS ABAP for supporting SSL. For more information, see Configuring AS ABAP to Support Secure Socket Layer (SSL) in Performing Post-Installation Steps for the ABAP Application Server [page 89]. 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 reexport 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. 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: adm This user is the SAP system administrator user and is a member of the local Administrators group. SAPService This user is the Windows account to run the SAP system and is not a member of the local Administrators group. sapadm The 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

2010-12-20

PUBLIC

39/196

3 3.4

Planning Basic SAP System Installation Parameters Description

Parameters

This 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

Being a Domain Administrator [page 107]. For security reasons, however, SAP strongly recommends to create this user as a local user.adm

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

SAP Solution Manager key

Make sure that you have the required user authorization [page 61] for these accounts before you start the installation with SAPinst. To install your SAP system, you need to generate an SAP Solution Manager key [page 64], which the installation requires to continue. For more information, see SAP Note 805390. You have already generated an SAP Solution Manager Key for the central instance, so you do not have to do this for the dialog instance.

SAP System Database Parameters Parameters Description

Database ID

The identifies the database instance. SAPinst prompts you for the when you are installing the database instance. The can be the same as the .CAUTION

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

40/196

PUBLIC

2010-12-20

3 3.4

Planning Basic SAP System Installation Parameters DescriptionPRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR7 VAR

Parameters

Base directories of DB2 for Linux, UNIX, and Drive for the database directory Windows Database instance home Database log files Database diagnostic data Drives for SAPDATA directories For more information, see Base Directories for the Database Instance [page 46]. DB2 instance owner db2 db2 has the DB2 system administration authorities and belongs to group dbadm, which has DB2 SYSADM authorities. By default, user db2 is a member of group dbadm. ABAP database connect user (sap) The user name corresponds to the database schema where ABAP tables are created. Database Communication Port The DB2 Communication Port is used for TCP/IP communication between the database server and remote DB2 clients. In a central system installation and for the database instance in a distributed installation, SAPinst always proposes 5912 as default value.NOTE

First port

SAPinst requests this value during the database instance installation. The database partition servers communicate using registered services. During the installation a port range is assigned for this communication. SAPinst proposes default values. You must make sure that these values correspond to the values of your database partition servers. If necessary, adapt them according to your settings.CAUTION

Last port

The value for First Port must be the same for all database partition servers. The range between First Port and Last Port must correspond to the maximum number of partitions on a database partition server. The database partition servers communicate using registered services. During the installation a port range is assigned for this communication. SAPinst proposes default values. You must make sure that these values correspond to the values of your database partition servers. If necessary, adapt them according to your settings.CAUTION

The range between First Port and Last Port must correspond to the maximum number of partitions on a database partition server.

2010-12-20

PUBLIC

41/196

3 3.4

Planning Basic SAP System Installation Parameters DescriptionOnly valid for: HA (MSCS) |

ParametersOnly valid for: HA (MSCS) |

Drive for database software locationEnd of: HA (MSCS) |

In an MSCS installation, the database directories have to reside on a shared drive whereas the database software must reside on a local drive.End of: HA (MSCS) |

Drive database directory Drive for diagnostic data Drive for online database Log Files

Drive sapdata Add sapdata directories

In a non-MSCS installation, enter the drive where the database directory and the database software is located. Location of the db2diag.log that contains diagnostic data required in case of, for example, a database crash. These log files are needed for database backups and recovery. Specify the drive where the database online log files are to be stored. Enter the drive where each sapdata directory is to be located. Tablespaces are stored in :\db2\\sapdata. By default, SAPinst creates four sapdata directories (sapdata1, sapdata2, sapdata3, sapdata4).NOTE

Be aware that the first part, for example :\db2 \\ is definite and you can only enter a value for sapdata. Use Change, that is, add or remove the names and number of the sapdata directories. Specify the size of the memory that DB2 requires for the database instance: For DB2 V9.5, you set the database manager configuration parameter INSTANCE_MEMORY. Parameter INSTANCE_MEMORY includes the database- and application-specific memory segments that are used by DB2. For DB2 V9.1, you have to specify the database memory by setting database manager configuration parameter DATABASE_MEMORY.CAUTION

Database memory or instance memory

Minimize database size

The database requires more memory than only the database-specific memory segments (which are specified by parameter DATABASE_MEMORY). You can significantly reduce the size of your database by selecting the following options in SAPInst during the dialog phase: Use DB2's Row Compression Use Deferred Table CreationCAUTION

Before you select these options, make sure that you have read the information in Optimization of Database Size on Disk [page 51] and SAP Note 1151343.

42/196

PUBLIC

2010-12-20

3 3.4

Planning Basic SAP System Installation Parameters Description

Parameters

DB2 Software Path

Specify the file system path where either an existing DB2 software installation already resides or where you want the new copy of DB2 to be installed.RECOMMENDATION

If you want to install a new copy of DB2, we recommend that you accept the default path suggested by SAPinst.Diagnostics Agent Parameters

The diagnostics agent is installed automatically with the SAP system.Parameters Description

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. If 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 104]. The same restrictions apply as in Instance Number of the SAP System (see above). Java(TM) Cryptography Extension You have to download the JCE Unlimited Strength Jurisdiction Policy (JCE) Unlimited Strength Jurisdiction Files 6 archive for the SAP JVM that is installed with the diagnostics agent. Policy Files Archive For more information, see Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive [page 64].

2010-12-20

PUBLIC

43/196

3 3.5

Planning Domain or Local Installation Description

Parameters

SLD Destination

You can choose between the following options: Register in existing central SLD Choose this option to register the diagnostics agent you are installing in an existing SAP System Landscape Directory (SLD) by specifying the SLD connection parameters listed below.RECOMMENDATION

SLD HTTP Host (FQN) SLD HTTP Port

We recommend that you select this option. No SLD destination If you select this option, SAPinst does not prompt you for further SLD parameters. Choose this option if you do not want to register the diagnostics agent of the SAP system you are installing in an existing SAP System Landscape Directory (SLD). You then have to configure the SLD destination for the diagnostics agent manually after the installation with SAPinst has finished. The fully qualified host name of the SAP system with the System Landscape Directory (SLD) The HTTP port of the SAP system with the System Landscape Directory (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

3.5 Domain or Local InstallationBefore 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 distributed system. Only valid for: HA (MSCS) |

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

You want to use Single Sign-On.

44/196

PUBLIC

2010-12-20

3 3.6

Planning Setup of Database Layout

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 More Information

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

3.6 Setup of Database LayoutNOTE

The following sections apply especially to the installation of a production system. When you plan your SAP system installation, it is essential to consider the setup of your database layout with regard to the distribution of, for example, SAP directories or database file systems, to disks. The distribution depends on your specific environment and you must take factors into consideration, such as storage consumption of the software components involved, safety requirements and expected workload. Make sure that you read the following sections before starting the SAP system installation: 1. Base Directories for the Database Instance [page 46] 2. Users and Groups [page 47] 3. Directory Structure of the New Client Connectivity [page 48] 4. DB2 Tablespaces [page 50] 5. Optimization of Database Size on Disk [page 51] 6. Data Safety and Performance Considerations for Production Systems [page 53]NOTE

For more information about DB2 (for example, printable manuals or online information), see Online Information from IBM [page 187].

2010-12-20

PUBLIC

45/196

3 3.6

Planning Setup of Database Layout

3.6.1 Base Directories for the Database InstanceThis section describes the base directories that SAPinst creates automatically during the installation of the database instance. Additionally, in a standard installation SAPinst creates all required SAP directories and automatically sets the correct access rights.RECOMMENDATION

We recommend that you install the complete SAP system on redundant storage, such as RAID-5 or intelligent storage devices. To improve system performance, you should use multiple I/O controllers.Directory Name:\db2\db2\db2_software

Description

Directory for the DB2 database software created during installation of DB2 server software. SAPinst uses this directory for the integrated database software installation.NOTE

:\DB2

As of DB2 V9.1 and higher, you can have multiple DB2 copies on one machine. DB2 database directoryNOTE

:\db2\\log_dir :\db2\\db2dump

With DB2's automatic storage management::\db2\\sapdata

No automatic storage management::\db2\\sapdata

If you are not using an MSCS cluster, you can choose only one drive for both the database directory and for the DB2 database software. Contains the online log files Contains DB2 diagnostic log files, DB2 dump files, and further service engineer information SAP data directories for an SAP system. By default, SAPinst creates four sapdata directories (sapdata1, sapdata2, sapdata3, sapdata4).NOTE

In a production system, you must make sure that the sapdata directories are located in different file systems. Otherwise, system performance can decrease. For more information, see Data Safety and Performance Considerations for Database Directories [page 53]. If you require more or fewer sapdata directories, you can change this on the SAPinst Sapdata Directories dialog. If you add additional sapdata directories during the dialog phase of SAPinst, the corresponding tablespace containers are equally distributed.

46/196

PUBLIC

2010-12-20

3 3.6

Planning Setup of Database Layout

Each of the above directories can be placed on a different local drive during the installation.Access Authorization

The following table shows the access rights that to be set for the DB2 directories. To guarantee full data security, you may manually set the access privileges of the subdirectories. The owner of all these directories must be the user Administrator.Directory:\db2\db2\db2_software

Access Privilege Full Control for User/GroupAdministrator, SYSTEM, SAP__LocalAdmin SAP__LocalAdmin, db2, SYSTEM SAP__LocalAdmin, db2, SYSTEM Everyone SAP__LocalAdmin, db2, SYSTEM db2, SYSTEM

(Default):\db2\db2\db2_software \DB2 (Default) :\DB2 :\db2 :\db2\

With DB2's automatic storage management::\db2\\sapdata

No automatic storage management::\db2\\sapdata :\db2\\log_dir db2, SYSTEM

3.6.2 Users and GroupsUsing DB2 the following users and groups are needed in the SAP system.DB2 Users Usersadm SAPService db2

Description

SAP system administrator SAP service account Database administratorNOTE

sap

Independently of the installation type (domain or local), this user is only used on the database host. Default ABAP connect user for SAP database objects. You can change this user during the installation.NOTE

In a local installation, this user is only created on the database host.CAUTION

If you are performing a domain installation, the database connect users are created by default in the domain of adm.