sap netweaver ce 7.2 installation guide

Installation Guide SAP NetWeaver Composition Environment 7.2 on Windows: MS SQL ServerProduction EditionTarget Audience System Administrators Technical Consultants

PUBLIC Document version: 1.1 2010-03-08

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 http://service.sap.com/installnwce72. The following table provides an overview of the most important document changes.Version Date Description

1.1

2010-03-08

Updated Version

2/176

PUBLIC

2010-03-08

Table of Contents

Chapter 1 1.1 1.2 1.3 1.4 Chapter 2 2.1 2.2 2.3 2.4 2.5 2.6 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.7

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of Additional Usage Types or Software Units in an Existing SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Prerequisite Checker in Standalone Mode (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for a Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Additional Application Server Instance . . . . . . . . . . . . . Requirements for the Host Agent as a Separate Installation . . . . . . . . . . . . . . . Planning User and Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic SAP System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain or Local Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution of SAP System Components to Disks . . . . . . . . . . . . . . . . . . . . . . SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 13 14 15 15 17 17 19 19 20 21 22 23 26 30 30 31 32 40 41 44

2010-03-08

PUBLIC

3/176

Chapter 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 Chapter 5 5.1 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.3 5.4 5.5 Chapter 6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling the Windows Server 2008 Firewall Temporarily . . . . . . . . . . . . . . . . Performing Basic Windows Preparation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . Required User Authorization for Running SAPinst . . . . . . . . . . . . . . . . . . . . . Preparing the SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading the Java Cryptography Extension Jurisdiction Policy Files Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the SQL Server Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the SQL Server Database Software with SQL4SAP . . . . . . . . . . . . . . . Installing the SQL Server 2008 Database Server Software Manually . . . . . . . . . Installing the SQL Server 2008 Native Client Software Manually . . . . . . . . . . . Setting the SQL Server Agent Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAPinst Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing SAP Memory Analyzer (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Windows Server 2008 Firewall . . . . . . . . . . . . . . . . . . . . . . . . Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Symbolic Links on Windows Server 2008 for Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . Applying the Latest Kernel and Support Packages . . . . . . . . . . . . . . . . . . . . . . Performing Initial Java Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Automated Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a Full System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Steps for the Host Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Steps for the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . .

45 45 46 46 48 50 50 51 55 55 56 56 57 60 61 61 64 68 69 69 70 72 73 74 75 75 75 77 77 79 80 81 81

4/176

PUBLIC

2010-03-08

6.15

Accessing Configuration Documentation in the SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Transporting Self-Developed Software Component Archives (SCA) into the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Restarting the MS SQL Server Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Uninstalling SAP NetWeaver Composition Environment . . . . . . . . . . . . . . . . 84 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Database Installation for Multiple Components with MS SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Default or Named MS SQL Server Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . . . 94 Preparing an External ABAP System as Source for User Data . . . . . . . . . . . . . . 95 Performing a Domain Installation Without Being a Domain Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Entries in the Services File Created by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . 105 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Log Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Installing Additional Usage Types or Software Units in an Existing SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Installing the Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Starting and Stopping the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Accessing the SAP Java Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 SAP System Security on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Automatic Creation of Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . . 117 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . 119 High Availability with Microsoft Cluster Service . . . . . . . . . . . . . . . . . . Checklist for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Configuration in MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 125 127 127

Chapter 7 7.1 7.2 7.3 7.4 7.5 7.6 7.6.1 7.7 7.8 7.9 7.10 7.10.1 7.10.2 7.10.3 7.10.4 7.10.5 7.10.6 7.11 7.12 7.13 7.14 7.15 7.16 7.17 7.18 Chapter 8 8.1 8.2 8.2.1

2010-03-08

PUBLIC

5/176

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

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clustering the SQL Server 2008 Database Server Software . . . . . . . . . . . . . . . Configuring the First Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Additional Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Primary Application Server Instance . . . . . . . . . . . . . . . . . . . . . Installing the Additional Application Server Instance . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rebooting During the Installation for MSCS . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping the SAP System in an MSCS Configuration . . . . . . . . .

127 130 132 134 135 139 140 143 146 146 146 147 148 151 154 154 159 160 160 161 162 163 163 164 164 166 166 167 168

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

6/176

PUBLIC

2010-03-08

1

Introduction

1 Introduction

This document explains how to install an SAP NetWeaver Composition Environment 7.2 system as productive edition. You perform the installation using SAPinst. For more information about the technology provided by SAP NetWeaver Composition Environment, see the documentation Master Guide SAP NetWeaver Composition Environment 7.2 at: http://service.sap.com/installnwce72 Planning . You can install an SAP NetWeaver Composition Environment 7.2 system with the following usage types in a single installation run: SAP NetWeaver Application Server JavaCAUTION

You must always install SAP NetWeaver Application Server Java together with SAP NetWeaver CE Product Description. SAP NetWeaver CE Product Description SAP NetWeaver CE Product Description requires SAP NetWeaver Application Server Java SAP NetWeaver Adobe Document Services SAP NetWeaver Adobe Document Services requires SAP NetWeaver Application Server Java. SAP NetWeaver Composite Application Framework SAP NetWeaver Composite Application Framework requires SAP NetWeaver Application Server Java. SAP NetWeaver Composition Environment Platform SAP NetWeaver Composition Environment Platform requires: SAP NetWeaver Application Server Java SAP NetWeaver Composite Application Framework SAP NetWeaver Business Process Management and Business Rules Management SAP NetWeaver Business Process Management and Business Rules Management requires: SAP NetWeaver Application Server Java SAP NetWeaver Composite Application Framework SAP NetWeaver Composition Environment Platform SAP NetWeaver Composition Voice SAP NetWeaver Composition Voice requires: SAP NetWeaver Application Server Java SAP NetWeaver Composite Application Framework SAP NetWeaver Composition Environment Platform

2010-03-08

PUBLIC

7/176

1 1.1

Introduction New Features

SAP NetWeaver Enterprise Services Repository SAP NetWeaver Enterprise Services Repository requires SAP NetWeaver Application Server Java. SAP NetWeaver Development Infrastructure SAP NetWeaver Development Infrastructure requires SAP NetWeaver Application Server Java. If you want to install additional software units or usage types to an existing SAP system, follow the procedure in Installation of Additional Software Units or Usage Types in an Existing SAP System [page 106]. For more information about the usage types of SAP NetWeaver Composition Environment and their interdependencies, see the document Master Guide SAP NetWeaver Composition Environment 7.2 at: http://service.sap.com/installnwce72 Planning . For restrictions, see SAP Note 1380304.Constraints

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

SAP system refers to SAP NetWeaver Composition Environment 7.2. diagnostics refers to diagnostics in SAP Solution Manager. diagnostics agent refers to the agent of diagnostics in SAP Solution Manager. Central services instance (SCS) for Java refers to the central services instance (SCS).

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 FeaturesHere you can find the new features in 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

With SAP NetWeaver 7.2, SAPinst has the following new features (compared to SAP NetWeaver 7.1):

8/176

PUBLIC

2010-03-08

1 1.1 Area

Introduction New Features Description

The enqueue replication server instance (ERS) can now also be installed together with the central services instance (SCS) for a: Standard System (optional) Distributed System (optional) The installation option Central Services Instance SCS) comprises both the installation of the SCS and optionally the installation of the related ERS. For more information, see Installation Options Covered by this Guide [page 13] and Installation Checklist [page 55]. Running SAPinst in accessibility mode: Keyboard access: 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 104]. Custom font setting: This feature is derived from the Windows display properties. For more information, see Running SAPinst in Accessibility Mode [page 104]. New installation For SAP systems based on SAP NetWeaver 7.1 including EHP1 (and higher), SAP adapted options for a high- the installation procedure for a high-availability system on Windows to make it easier and availability system less error-prone for customers: in a Microsoft First Cluster Node Cluster 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 followings steps: Installs the central services instance (SCS) Installs the enqueue replication server instance (ERS) for the SCS instance Installs the host agent Creates the SAP cluster group on the first cluster node and adds the SCS instance to the SAP cluster group 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 SCS instance on a local drive Installs the host agent on a local drive SAP Java Virtual You no longer have to download and install a Java Development Kit (JDK) from another Machine (SAP JVM) software vendor as a prerequisite for the installation with SAPinst. The SAP JVM is a Java Development Kit (JDK) provided and supported by SAP. SAP JVM is fully compliant with the Java Standard Edition 5. It is available on the Installation Master DVD and is installed automatically by SAPinst when you start the installation.Operating Systems Area Description

Support of Operating Systems

The installation of SAP systems is only supported on 64-bit platforms.

2010-03-08

PUBLIC

9/176

1 1.2 Area

Introduction SAP Notes for the Installation Description

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

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.SQL Server Database Area Description

SQL Server 2008

As of SAP NetWeaver 7.2, SAP only supports the installation of SQL Server 2008.

Documentation Area Description

Checklists for all phases of the installation: planning, preparation, installation, postinstallation

We have introduced new checklists for all phases of the installation process: 1. Planning Checklist [page 19] 2. Preparation Checklist [page 45] 3. Installation Checklist [page 55] 4. Post-Installation Checklist [page 69] 5. Only valid for: HA (MSCS) | Checklist for a High-Availability System [page 125]End of: HA (MSCS) |

These checklists are designed to improve the usability of the installation guides by: Providing a quick step-by-step reference of what has to be done for each phase of the installation Guiding you step-by-step through the installation phases. Each step is linked with the appropriate section for more details about the step. Improving navigation within the installation guide. You can also access the checklists directly from the Table of Contents.

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

1379049

Installation of SAP NetWeaver Composition Environment 7.2

CE-specific information about the installation and corrections to this documentation.

10/176

PUBLIC

2010-03-08

1 1.3

Introduction Accessing the SAP Library Title Description

SAP Note Number

1380304

Release Restrictions for SAP NetWeaver Composition Environment 7.2

1359556

1360957

1368413

737368

855498 73606 1067221

Customer information about restrictions concerning the productive usage of certain functions. SAP NetWeaver Installation Based On Windows-specific information about the SAP Kernel 7.2: Windows system installation and corrections to this documentation. SAP NetWeaver Based On Kernel 7.2: SQL MS SQL Server-specific information about Server the SAP system installation and corrections to this documentation. Inst. NetWeaver 7.2 - Diagnostics Agent Problems discovered after the publication of installation the installation guide or post-installation steps Hardware requirements of Java Information on the hardware requirements Development for usage type Development Infrastructure (DI), which depends on the size of your development team. Installation Prerequisite Checker SAP Software on UNIX, Windows and IBM i: Checking OS Dependencies Supported Languages and Code Pages Information on possible languages and language combinations in SAP systems Central Note for Heterogeneous This SAP Note and its related SAP Notes Installation describe the released operating system and database combinations for heterogeneous SAP systems landscapes.

1.3 Accessing the SAP LibraryThe references to SAP NetWeaver Library documentation in this installation guide always refer to the following on SAP Help Portal: http://help.sap.com/nwce72 SAP NetWeaver Composition Environment 7.2 SAP NetWeaver Composition Environment Library

1.4 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: Standard system (formerly known as central system) Distributed system Only valid for: HA (MSCS) |

High-availability systemEnd of: HA (MSCS) |

2010-03-08

PUBLIC

11/176

1 1.4

Introduction How to Use This Guide

Only valid for: BI Java;Development Infrastructure (DI);Enterprise Portal (EP);EP Core (EPC);Mobile |

Additional software units or usage types to an existing SAP systemEnd of: BI Java;Development Infrastructure (DI);Enterprise Portal (EP);EP Core (EPC);Mobile |

2.

Additional application server instance Host Agent as a separate installation For more information, see Installation Options Covered by This Guide [page 13]. You follow the list of steps at the beginning of each installation phase: Planning [page 19] Preparation [page 45] Installation [page 55] Post-Installation [page 69] High Availability with Microsoft Cluster Service (if relevant) [page 123]NOTE

This applies to all installation options except the following: Installation of Additional Usage Types or Software Units in an Existing SAP System [page 17] Host Agent as a Separate Installation [page 17] In Additional Information [page 83] you can find special installation options and more detailed information about how to perform certain steps described in the main part of the guide.

12/176

PUBLIC

2010-03-08

2 2.1

Installation Options Covered by this Guide Standard System

2 Installation Options Covered by this Guide

This section shows the installation options covered by this installation 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. Standard system [page 13] (formerly known as central system) Distributed system [page 14] Only valid for: HA (MSCS) |

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

You can install one or more additional application server instances [page 15] to an existing standard, distributed, or high-availability system. You can install additional usage types in an existing SAP system [page 17]. You can install a host agent separately [page 17].

2.1 Standard SystemYou can install a standard system on a single host. In a standard system, all main instances run on a single host: There are the following instances: Central services instance for Java (SCS) Enqueue replication server instance (ERS) for the SCS (optional) Database instance (DB) Primary application server instance (PAS) Optionally you can install one or more additional application server instances. For more information, see Additional Application Server Instance [page 15].

2010-03-08

PUBLIC

13/176

2 2.2

Installation Options Covered by this Guide Distributed System

Figure 1:

Standard Java System

2.2 Distributed SystemAn SAP system consists of SAP instances. An SAP instance is a group of processes that are started and stopped at the same time. In a distributed system, every instance can run on a separate host: There are the following instances: Central services instance for Java (SCS) Enqueue replication server instance (ERS) for the SCS (optional) Database instance (DB) The Java stack uses its own database schema in the database Primary application server instance (PAS) Optionally you can install one or more additional application server instances. For more information, see Installation of an Additional Application Server Instance [page 15].

14/176

PUBLIC

2010-03-08

2 2.3

Installation Options Covered by this Guide High Availability System

Figure 2:

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

2.4 Additional Application Server InstanceYou can install one or more additional application server instances for an existing SAP system. Additional application server instances are optional and can be installed on separate hosts. An additional application server instance can run on: The host of any instance of the existing SAP system On a dedicated hostNOTE

We do not recommend installing additional application server instances on the SAP global host.Additional Application Server Instance for a Standard System

The following figure shows additional application server instances that are running on dedicated hosts.

2010-03-08

PUBLIC

15/176

2 2.4

Installation Options Covered by this Guide Additional Application Server Instance

Figure 3:

Additional Application Server Instance for a Standard System

For more information, see Standard System [page 13].Additional Application Server Instance for a Distributed System

The following figure shows additional application server instances that are running on dedicated hosts.

Figure 4:

Additional Application Server Instance for a Distributed System

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

16/176

PUBLIC

2010-03-08

2 2.5

Installation Options Covered by this Guide Installation of Additional Usage Types or Software Units in an Existing SAP System


Additional Application Server Instance for a High-Availability System

In a high-availability system, you require apart from the primary application server instance at least one additional application server instance. For more information about how to install and distribute the application servers in an MSCS configuration, see section System Configuration in MSCS [page 127].End of: HA (MSCS) |

2.5 Installation of Additional Usage Types or Software Units in an Existing SAP SystemYou perform the installation of additional usage types or software units in an existing Java system to optimize total cost of ownership (TCO). That is, you do not have to install a complete additional Java system to run these additional usage types or software units. The section Installing Additional Usage Types or Software Units in an Existing SAP System [page 106] describes how to perform the installation.

2.6 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.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.2 or higher. The section Installing the Host Agent Separately [page 112] describes how to perform the installation.

2010-03-08

PUBLIC

17/176

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: Standard, distributed, or high-availability system Additional application server 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 available for your product at http://service.sap.com/instguides and the Technical Infrastructure Guide for SAP Systems Based on SAP NetWeaver available at https://cw.sdn.sap.com/cw/community/docupedia/tig. You have decided on your installation option [page 13].

Standard, Distributed, or High-Availability System NOTE

In a standard system, all mandatory instances are installed on one host. Therefore, if you are installing a standard system, you can ignore references to other hosts. 1. 2. 3. 4. 5. 6. 7. You check the hardware and software requirements [page 20] on each installation host. You plan how to set up user and access management [page 31]. You identify basic SAP system parameters [page 32]. You decide whether you want to perform a domain or local installation [page 40]. For the database installation, you decide on how to distribute your database components to disk [page 41]. You decide on the transport host to use [page 44].Only valid for: HA (MSCS) |

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

8. 9.

Optionally, you decide whether you want to install the database for multiple components with MS SQL Server [page 92] or whether you want to install multiple components in one database (MCOD) [page 94] You can now continue with Preparation [page 45].

Additional Application Server Instance

1.

You check the hardware and software requirements [page 20] for every host on which you want to install one or more additional application server instances.

2010-03-08

PUBLIC

19/176

3 3.2

Planning Hardware and Software Requirements

2. 3.

You identify basic SAP system parameters [page 32]. You can now continue with Preparation [page 45].

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

Contact your OS vendor for the latest OS patches. 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: Standalone (optional) before the installation process For more information, see Running the Prerequisite Checker Standalone [page 21].NOTE

SAP NetWeaver CE: there is no standalone mode available. Integrated in the installation tool (mandatory) as part of the installation process For more information, see Running SAPinst [page 61].NOTE

For the most recent updates to the Prerequisite Checker, always check SAP Note 855498. The hardware and software requirements checklists for: Standard system [page 22] Distributed system [page 23] Only valid for: HA (MSCS) |

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

3.

Additional application server instance [page 30] Host agent as a separate installation [page 30] 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:

20/176

PUBLIC

2010-03-08

3 3.2


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 Composition Environment 7.2 at: http://service.sap.com/installnwce72 Planning .Only valid for: Development Infrastructure (DI) |

NOTE

If you want to install usage type Development Infrastructure (DI), also check SAP Note 737368 for system requirements and sizing.End of: Development Infrastructure (DI) |

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

1. 2. 3.

You start SAPinst [page 61]. On the Welcome screen, choose 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.

2010-03-08

PUBLIC

21/176

3 3.2


4.

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.

Result

The Prerequisite Checker 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.RECOMMENDATION

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

3.2.2 Requirements for a Standard SystemIf you want to install a standard system, where all instances reside on one host, this host must meet the following hardware and software requirements:NOTE

The listed values only apply for development systems or quality assurance 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 Standard System Hardware Requirement Requirement How to Check

Minimum disk space

Minimum RAM

To check disk space: Database Software: 4 GB 1. Choose Start All Programs Administrative Tools Computer SAP system files (not including paging file): Management Disk Management. 5 GB (x64) 2. Right-click the drive and choose 8 GB (IA64) Properties. SAP database files (not including paging file): 3 GB Up to 2 GB for each usage type or software unit you want to install. 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk 4 GB To check RAM: In the Windows Explorer, choose Help About Windows .

22/176

PUBLIC

2010-03-08

3 3.2

Planning Hardware and Software Requirements Requirement How to Check

Hardware Requirement

Paging file size

1 times RAM plus 14 GB

Suitable backup systemSoftware Requirements for a Standard System Software Requirement Requirement

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.

How to Check

Windows operating system

Database software

English international 64-bit version of one of the following Windows Server Editions: Windows Server 2003 Windows Server 2003 Standard Edition Windows Server 2003 Enterprise Edition Windows Server 2003 Datacenter Edition Windows Server 2008 Windows Server 2008 Standard Edition Windows Server 2008 Enterprise Edition Windows Server 2008 Datacenter Edition Windows Server 2008 for Itanium-Based Systems Edition For any version of Windows Server, you need the latest supported service pack. A suitable Windows Resource Kit is strongly recommended. Windows Server 2003: Updated CPU drivers For more information, see SAP Note 1036194. MS SQL Server 2008 Enterprise Edition: Server Software Latest service pack and hotfix, if available. For more information, see SAP Note 62988. Unicode collation SQL_Latin1_General_CP850_BIN2

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

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: Central services instance Database instance Primary application server instance

2010-03-08

PUBLIC

23/176

3 3.2


Additional application server instance (optional) Diagnostics agentNOTE

The listed values only apply for development systems or quality assurance 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 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 Distributed System Hardware Requireme nt

Requirement

How to Check

Database Software: 4 GB Central services instance (SCS) (not including paging file): 5 GB (x64) 8 GB (IA64) Enqueue replication server instance (ERS) (not including paging file) (optional): 5 GB (x64) 8 GB (IA64) Database instance (not including paging file): 3 GB Primary application server 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 500 MB for the diagnostics agent Up to 2 GB for each usage type or software unit you want to install. Additional application server instance (optional) (not including paging file): 2.5 GB (x64) 5 GB (IA64) In addition you require 500 MB for the diagnostics agent Temporary disk space for every required installation DVD that you have to copy to a local hard disk: 4.3 GB Minimum 4 GB RAM Minimum disk space

To check disk space: 1. Choose Start All Programs Administrative Tools Computer Management Disk Management 2. Right-click the drive and choose Properties

To check RAM:

24/176

PUBLIC

2010-03-08

3 3.2


Hardware Requireme nt

Requirement

How to Check

Paging file size

Central services instance (SCS): 1 times RAM plus 1 GB Database instance: 1.5 times RAM Primary application server instance: 1 times RAM plus 14 GB Enqueue replication server instance (ERS) (optional): 1 times RAM plus 1 GBP Additional application server instance (optional): 1 times RAM plus 14 GB

In the Windows Explorer, choose Help About Windows 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 systemSoftware Requirements for a Distributed System Software Requirement Requirement

How to Check


English international 64-bit version of one To check your Windows version: 1. Choose Start All of the following Windows Server Editions: Programs Accessories Windows Server 2003 Command Prompt . Windows Server 2003 Standard Edition 2. Enter the command winver. Windows Server 2003 Enterprise Edition Windows Server 2003 Datacenter Edition Windows Server 2008 Windows Server 2008 Standard Edition Windows Server 2008 Enterprise Edition Windows Server 2008 Datacenter Edition Windows Server 2008 for ItaniumBased Systems Edition For any version of Windows Server, you need the latest supported service pack. A suitable Windows Resource Kit is strongly recommended. Windows Server 2003: Updated CPU drivers For more information, see SAP Note 1036194.

2010-03-08

PUBLIC

25/176

3 3.2


Software Requirement

Database software

Central services instance (SCS), primary application server, or additional application server: The following SQL Server client software: MS SQL Server 2008 Native Access Client (SNAC) software Latest service pack and hotfix, if available. For more information, see SAP Note 62988. Database instance: The following SQL Server Enterprise Edition server software: MS SQL Server 2008 Enterprise Edition: Server Software Latest service pack and hotfix, if available. For more information, see SAP Note 62988. Unicode collation SQL_Latin1_General_CP850_BIN2


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 only: 1. Check that your cluster hardware is certified for Windows Server 2008 and has the Windows Server 2008 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).

26/176

PUBLIC

2010-03-08

3 3.2


The private network enables internal communication between the MSCS nodes. In particular, it enables the Cluster Service running on all MSCS nodes to regularly exchange messages on the state of the MSCS nodes so that the failure of resources is quickly detected. Each of the MSCS nodes in the cluster must have its own local disks and have access to shared disks that can be reached by the MSCS nodes via a shared bus. All software except the Windows operating system, the MS SQL server binaries, and the MSCS software is stored on the shared disks. One of the shared disks must be used exclusively by the quorum (if a single quorum device cluster is used) that stores the cluster registry and records information about the state of the cluster. You require at least four shared disks. For more information about the distribution of components to local and shared disk, see Distribution of SAP System Components to Disks for MSCS [page 135]. 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 (SCS) Database instance Enqueue Replication Server instance (ERS) Primary application server instance Additional application server 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 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 High-Availability System Hardware Requirement Requirement How to Check

Minimum disk space

Database Software: 4 GB

To check disk space:

2010-03-08

PUBLIC

27/176

3 3.2



Minimum RAM

Paging file size

1. Choose Start All Programs Central services instance (SCS) (not Administrative Tools Computer including paging file): 5 GB (x64) Management Disk Management . 8 GB (IA64) 2. Right-click the drive and choose Properties. SAP database instance (not including paging file): 3 GB Enqueue replication server instance (ERS) (not including paging file): 5 GB (x64) 8 GB (IA64) Primary application server 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 500 MB for the diagnostics agent Up to 2 GB for each usage type or software unit you want to install. Additional application server instance (not including paging file): 2.5 GB (x64) 5 GB (IA64) In addition you require 500 MB for the diagnostics agent Temporary disk space for every required installation DVD that you have to copy to a local hard disk: 4.3 GB 4 GB To check RAM: In the Windows Explorer, choose Help About Windows . To check paging file size: Central services instance (SCS): 1 times RAM plus 1 GB 1. Choose Start Control Panel System . Database instance: 1.5 times RAM 2. Choose Advanced (Windows Server 2003) or Advanced system settings Enqueue replication server instance (ERS): (Windows Server 2008). 1 times RAM plus 1 GB 3. Select Performance Settings Advanced . Primary application server instance: 1 times RAM plus 14 GB 4. If required, in section Virtual memory, choose Change. Additional application server instance: 1 times RAM plus 14 GBNOTE

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

28/176

PUBLIC

2010-03-08

3 3.2



Suitable backup systemSoftware Requirements for a High-Availability System Software Requirement Requirement

How to Check


Database software

To check your Windows version: English international 64-bit 1. Choose Start All Programs version of one of the following Accessories Command Prompt . Windows Server Editions: Windows Server 2003 2. Enter the command winver. Windows Server 2003 NOTE Enterprise Edition Windows Server 2003 only: Windows Server 2003 You must set up the MSCS Datacenter Edition Cluster Service as described Windows Server 2008 in the Microsoft Windows Server 2008 documentation. During this Enterprise Edition setup you are asked for a Windows Server 2008 Windows Domain Account Datacenter Edition to run the Cluster Service. Windows Server 2008 for We strongly recommend Itanium-Based Systems creating an account Edition different from the For any version of Windows Server, adm user, for you need the latest supported service example pack. ClusterServiceuser=sappr A suitable Windows Resource Kit is dcladm, where strongly recommended. Clustername=sapprdcl. Windows Server 2003: Updated CPU drivers Windows Server 2008 only: You must add the operating For more information, see SAP Note system feature Failover 1036194. Clustering on all MSCS nodes. Central services instance (SCS), primary application server instance or additional application server instance: MS SQL Server 2008 Native Access Client (SNAC) software Latest service pack and hotfix, if available. For more information, see SAP Note 62988. Database instance: MS SQL Server 2008 Enterprise Edition: Server Software Latest service pack and hotfix, if available. For more information, see SAP Note 62988.

2010-03-08

PUBLIC

29/176

3 3.2


Software Requirement

Unicode collation SQL_Latin1_General_CP850 _BIN2End of: HA (MSCS) |

3.2.5 Requirements for the Additional Application Server InstanceFor more information about the requirements for the additional application server instance, see one of the following sections: Requirements for a Distributed System [page 23] Only valid for: HA (MSCS) |

Requirements for a High-Availability System [page 26]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 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.Hardware Requirements for the Host Agent Hardware Requirement Requirement How to Check

Minimum disk space:

Minimum RAM:

Host agent: 80 MB Temporary disk space for every required installation DVD that you have to copy to a local hard disk: 4.3 GB 40 MB

Paging file size:

500 MB

To check disk space: 1. Choose Start All Programs Administrative Tools Computer Management Disk Management. 2. Right-click the drive and choose Properties. To check RAM: In the Windows Explorer, choose Help About Windows . To check paging file size: 1. Choose Start Control Panel System .

30/176

PUBLIC

2010-03-08

3 3.3

Planning Planning User and Access Management Requirement How to Check


2.

3. 4. Suitable backup systemSoftware Requirements for the Host Agent Software Requirement Requirement

Choose Advanced (Windows Server 2003) or Advanced system settings (Windows Server 2008). Select Performance Settings Advanced . If required, in section Virtual memory, choose Change.

How to Check

Windows operating system:

Database software:

English international 64-bit version of one of the following Windows Server Editions: Windows Server 2008 Enterprise Edition Windows Server 2008 Datacenter Edition Windows Server 2008 for Itanium-Based Systems Edition For any version of Windows Server, you need the latest supported service pack. A suitable Windows Resource Kit is strongly recommended.

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

3.3 Planning User and Access ManagementYou have to plan how to configure user and access management for the 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 the database of AS Java. Use an external ABAP system as the data source for user data. Use an LDAP directory as the data source for user data. You cannot configure the AS Java to simultaneously access an LDAP directory and an AS ABAP as the data source. The AS Java can also use its own database as the data source.ProcedureUsing the Database of AS Java

You install your SAP system as described in this installation guide. During the installation, you specify the Java database as data source for the User Management Engine (UME). For more information, see the table User Management Engine in Basic SAP System Parameters [page 32]:

2010-03-08

PUBLIC

31/176

3 3.4

Planning Basic SAP System Parameters

During the installation, the SAP system is automatically configured to use the Java database as the data source for the UME. After the installation has finished, you can still change the user management configuration. For more information, see Configuring User Management [page 77].Using an External SAP ABAP System as the Data Source for User Data.

1. 2.

3.

You prepare the external SAP ABAP system as described in Preparing an External ABAP System as Source for User Data [page 95]. You install your SAP system as described in this installation guide. During the installation, you specify an external ABAP system as the data source for the User Management Engine (UME). For more information, see the table User Management Engine in Basic SAP System Parameters [page 32]. After the installation has finished, you can no longer change this configuration of the UME. For more information, see Configuring User Management [page 77].

Using an LDAP Directory as the Data 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 an LDAP directory. For more information, see Configuring User Management [page 77].

More Information

For more information about configuring the user management of your SAP system to be installed, see the SAP Library [page 11] at: Administrators Guide Administration of SAP NetWeaver CE Security and User Management User Management of the Application Server Java

3.4 Basic SAP System ParametersSAPinst prompts for input parameters during the Define Parameters phase of the installation. The tables below list the basic system parameters that you need to specify before installing your SAP system. For all other SAP system parameters, use the F1 help in the SAPinst screens. You can install your SAP system either in Typical or Custom mode: Typical If you choose Typical, the installation is performed 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 Master password JCE Unlimited Strength Jurisdiction Policy files archive

32/176

PUBLIC

2010-03-08

3 3.4


SAP system profile directory only for systems with instances on separate hosts 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.RECOMMENDATION

If you want to configure the user management of your SAP system for an external ABAP system, as described in Preparing an External ABAP System as Source for User Data [page 95], we recommend that you select the Custom parameter mode. When you do this, you are prompted to select the appropriate option and to enter the required parameters If you do not choose the Custom parameter mode, you have to change the required parameters on the Parameter Summary screen.NOTE

You cannot change from Custom to Typical mode or from Typical to Custom mode on the Parameter Summary screen. The 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.Java Cryptography Extension Jurisdiction Policy Archive Parameters Description

Java Cryptography Extension Jurisdiction Policy Files

You need to obtain the Java Cryptography Extension (JCE) Jurisdiction Policy Files archive for the JDK you are using beforehand so that SAPinst can install them. For more information, see Downloading the Java Cryptography Extension Jurisdiction Policy Files Archive [page 50].

SAP System ID and Database ID Parameters Description

SAP System ID

The SAP system ID identifies the entire SAP system. SAPinst prompts you for the when you execute the first installation option to install a new SAP system. If there are further installation options to be executed, SAPinst prompts you for the profile directory. For more information, see the description of the parameter SAP System Profile Directory.EXAMPLE

This prompt appears when you install the central services instance, which is the first instance to be installed in a distributed system.CAUTION

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

2010-03-08

PUBLIC

33/176

3 3.4

Planning Basic SAP System Parameters Description

Parameters

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

Database ID

If you want to install an additional application server instance, make sure that no gateway instance with the same SAP System ID (SAPSID) exists in your SAP system landscape. 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 you to 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 PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR

System ID of Diagnostics Agent

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

34/176

PUBLIC

2010-03-08

3 3.4


Parameters

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 Profile Directory Parameters\\\sapmnt\\ SYS\profile

Description

The installation retrieves the parameters entered earlier from the SAP system profile directory. SAPinst prompts you to enter the location of the profile directory when the installation option that you execute is not the first one belonging to your SAP system installation. See also the description of the parameters SAP System ID and Database ID.NOTE

If you install an additional application server instance to an existing SAP system, SAPinst also prompts you for the profile directory of the existing SAP system.SAP System Instances, Hosts, and Ports Parameters Description

Instance Number of the SAP Instance Number: System Technical identifier that is required for every instance of an SAP system, consisting 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. The instance number is used to specify the names of the SAP system instance directories that SAP automatically creates during the installation: The directory both of the primary application server instance and of an additional application server instance is called J. The directory of the central services instance is called SCS. For more information, see SAP Directories [page 88].CAUTION

Instance Number of the Diagnostics Agent

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 Technical identifier for internal processes for the diagnostics agent, consisting of a two-digit number from 00 to 97 The instance number is set automatically to the next free and valid instance number that has not yet been assigned to the SAP system. 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.

2010-03-08

PUBLIC

35/176

3 3.4


Parameters

For more information, see SAP Directories [page 88]. The same restrictions apply as in Instance Number of the SAP System (see above). 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. The SCS instance profile contains the configuration for the Java message server. The Java message server port uses the parameter rdisp/msserv_internal with default value 39, where is the instance number of the SCS message server instance. For more information about the parameters used for message server ports, see SAP Note 821875.Parameters for SAP System Drives Parameters Description

Destination drive

Base directory for the SAP system.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.Master Password Parameters Description

Master Password

Common password for all users that are 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 (see table Operating System Users). In this case, make sure that the master password meets the requirements of your operating system and database. Java users (for example Administrator) Database users Secure Store key phrase For more information, see table 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

36/176

PUBLIC

2010-03-08

3 3.4


Parameters

Must contain at least one letter (a-z, A-Z) Must contain at least one digit (0-9) Must not contain \ (backslash) and " (double quote) Depending on the installation option, additional restrictions may apply (for example, the master password must not contain the name of a Java user created during the installation).Operating System Users of the SAP System Parameters Description

Password of Operating System Users

SAPinst processes the passwords of operating system users as follows: If the operating system users do not exist, SAP creates the following users: adm This user is the SAP system administrator user. It is a member of the local Administrators group. SAPService This user is the Windows account to run the SAP system. It 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 Being a Domain Administrator [page 98]. For security reasons, however, SAP strongly recommends to create this user as a local user. adm The diagnostics agent user adm is used to manage the diagnostics agent system. It is created on the primary application server instance host and on every additional application server instance host. SAPinst creates this user by default as a local user without being a member of the local Administrators group. If required, you can change this user to become a domain user on the parameter summary screen. For more information, see Performing a Domain Installation Without Being a Domain Administrator [page 98]. For security reasons, however, SAP strongly recommends to create this user as a local user. SAPService This user is the Windows account to run the diagnostics agent system. 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 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.

2010-03-08

PUBLIC

37/176

3 3.4


User Management Engine (UME) Parameter Description

UME Configuration

SAPinst prompts you for how to configure the UME during the input phase of the installation. You can choose between the following options: Use Java Database (Default) If you choose this option, administrators can manage users and groups with the UME Web admin tool and SAP NetWeaver Administrator only. Use ABAP If you choose this option, administrators can manage users with the transaction SU01 on the external ABAP system, and, depending on the permissions of the communication user, also with the UME Web admin tool and SAP NetWeaver Administrator. You must have created the required users manually on the external ABAP system. For more information, see Preparing User Management for an External ABAP System [page 95]. For more information about supported UME data sources and change options, see SAP Note 718383.

Using the Java Database: Administrator User

SAPinst sets the user name Administrator and the master password by default. If required, you can choose another user name and password according to your requirements. Guest User SAPinst sets the user name Guest and the master password by default. The guest user is a user for anonymous access. Using an External ABAP System Parameters for the ABAP Connection: Application Server Instance This is the instance number on the application server of the central ABAP system Number to which you want to connect the Application Server Java. To find out the number on the host of the primary application server instance, look under the SAP directory usr/sap//DVEBMGS. The value is the number assigned to the SAP system. Application Server Host This is the host name of the relevant application server instance. To find out the host name, enter hostname at the command prompt of the host running the primary application server instance. Communication User This is the name and password of the existing ABAP communication user. You must have created this user manually on the external ABAP system. Using an External ABAP System Parameters for the Application Server Java Connection: Administrator User This is the name and password of the administrator user that you created on the external ABAP system. Administrator Role The role SAP_J2EE_ADMIN must exist on the external ABAP system. Guest User This is the name and password of the guest user that you created on the external ABAP system. The guest user is a user for anonymous access. Guest Role The role SAP_J2EE_GUEST must exist on the external ABAP system.

38/176

PUBLIC

2010-03-08

3 3.4


Key Phrase for Secure Store Settings Parameters Description

Key Phrase for Secure Store Settings

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

Use a long key phrase that cannot be guessed easily. Use both uppercase and lowercase letters in the phrase and include special characters.Connectivity for the Diagnostics Agent to System Landscape Directory (SLD) Parameters Description

SLD Destination

You can choose between the following options: Register in existing central SLD SAPinst only prompts you for the parameters listed below in this table if you select this option.RECOMMENDATION

SLD HTTP Host SLD HTTP Port

We recommend that you select this option. No SLD destination If you select this option: You have to configure the SLD destination for the diagnostics agent manually after the installation with SAPinst has finished. SAPinst does not prompt you for the parameters listed below in this table. The host name of the System Landscape Directory (SLD) The HTTP port of the Java system where the SLD is installed. The following naming convention applies: 500.EXAMPLE

SLD Data Supplier User and password

If the instance number of your Java system is 01, the SLD HTTP Port is 50100. You have to enter the existing SLD Data Supplier User and password of the central SLD.

Internet Communication Manager (ICM) User Management Parameter Description

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.

Host Agent Parameter Description

Password of sapadm

The administration user sapadm is created to use central monitoring services.

2010-03-08

PUBLIC

39/176

3 3.5

Planning Domain or Local Installation Description

Parameter

If this user does not already exist, SAPinst automatically creates it. SAPinst prompts you to enter either the password of the existing user or a new password for the user to be created.Prepare SAP System for NWDI Integration Parameters Description

Prepare SAP System for NWDI Integration

If you select check box Prepare SAP System for NWDI Integration on the screen NWDI Landscape, SAPinst copies all SCAs belonging to the software units that you installed to the global transport directory. The SAP NetWeaver Development Infrastructure (NWDI) has a set of services that provide central storage and distributed versioning of Java source code, plus centralized build services and a predefined change management process that control the flow of software through the landscape. To integrate your SAP system into the development landscape, NWDI requires all installed software components to be available in the file system. For more information, see the SAP Library [page 11] at: Developers Guide Development Infrastructure

Parameters Relevant for the Database Parameters Description

Database instance name

MS SQL Server instance name You can also specify a remote database instance. For a named instance, enter \.Only valid for: HA (MSCS) |

In an MSCS environment, enter the virtual SQL Server name.End of: HA (MSCS) |

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, 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. You have to perform a domain installation if one of the following applies: You install a distributed system (strongly recommended to avoid authorization problems). Only valid for: HA (MSCS) |

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

40/176

PUBLIC

2010-03-08

3 3.6

Planning Distribution of SAP System Components to Disks

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 (standard 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 Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP NetWeaver at: http://service.sap.com/instguides More Information

Required User Authorization for Running SAPinst [page 48]

3.6 Distribution of SAP System Components to DisksWhen 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. The following table gives you an overview of the main SAP system components, directories, and their purpose. A good distribution to disks ensures that: Enough free space is available for system growth The data is secure Performance is goodSAP System Components and their Directories Directory Type Directory Structure Description

SAP System

\usr\sap \usr\sap\trans

SAP kernel and related files SAP transport directory

2010-03-08

PUBLIC

41/176

3 3.6

Planning Distribution of SAP System Components to Disks Directory Structure\Program Files\Microsoft SQL Server

Directory Type

Description

Database Management System (DBMS) SAP Database

\DATA0 \DATA1 \DATA2 \DATA3 ... \DATA

SQL Server program files including the master, msdb and model database files. Database data files

SAP Database Transaction Log TempdbDatabase Components

\log \Tempdb

Database transaction log files Tempdb data files

When you install an SAP system with MS SQL Server, the central components of the database are the SQL Server program files, tempdb files, SAP database data files and SAP database transaction log files. The log files record all the changes made to the database to enable restore and recovery. The tempdb holds all temporary tables and stored procedures. The data files contain the data for the SAP system. SAP Database Data Files The data files are created by default in the directories \DATA on the disk with the most free available space. The first data file is called DATA0.mdf and subsequent files DATA.ndf, where denotes the number of the file. For performance reasons, locate the data files on a separate disk system. They should not be included in the same disk system as the log files or other SQL Server program and database files. To ensure data redundancy, we recommend the use of RAID 5. Transaction Log File The transaction log for the database is created by default in the directory\LOG1 on the disk with the most free available space. The log file is called LOG1.ldf. The transaction log file records all the changes made to the database and, if required, enables modifications to be redone or undone. It plays a crucial role when the database has to be restored due to database damage or media failure. We recommend the use of RAID 1, which implements hardware-based mirroring. Program Files The files other than the SAP database data and transaction log files are created in the subdirectories of \Program Files\Microsoft SQL Server. These include the SQL Server program files and the master, msdb, andmodel database files. Locate these on a separate, third, disk system and not on the same disks as the transaction log files or SAP database data files. We recommend the use of RAID 1.

42/176

PUBLIC

2010-03-08

3 3.6

Planning Distribution of SAP System Components to Disks

For performance reasons, it is advisable to place the tempdb files on a fast disk system. This is particularly recommended because the tempdb is frequently accessed during SQL Server operation and could otherwise affect performance.NOTE

After the initial installation of the database software, the tempdb is located in a subdirectory of \Program Files\Microsoft SQL Server. However later, when SAPinst builds and loads the database, it is transferred to a new \TEMPDB directory and extended to a size of 300 MB.Distribution of Main Directories to RAID Array

The following graphic illustrates how the main directories that are created during the installation can be distributed to RAID arrays. The distribution is suitable for an average-sized production system. Keep in mind that this is only an example and that no single solution is fitting for all environments.NOTE

The SAP kernel files and the transport directory can be assigned to any of the arrays depicted, but must both be located on the same array. The transport directory does not necessarily have to reside on the primary application server instance host.

Figure 5:

Distribution of SAP System Components to RAID Arrays

Distribution of Directories to Arrays

Array 1 Array 2

\Program files\Microsoft SQL Server \TEMPDB \DATA0

2010-03-08

PUBLIC

43/176

3 3.7

Planning SAP System Transport Host\DATA1 \DATA2 \DATA3 ... \DATA

Array 3Optimizing Performance

\log1

If you wish to optimize performance, isolate the tempdb on a separate, fast disk. This improves performance significantly because the tempdb is continually accessed during MS SQL Server operation. A further option for improving performance is to place the Windows paging file on a separate, fast disk.

3.7 SAP System Transport HostThe transport host contains the transport directory used by the SAP transport system to store transport data and change SAP system information, such as software programs, data dictionary data, or customization data. If you have several SAP systems, they are usually organized in transport domains. In most cases, all SAP systems in a transport domain have a common transport directory. When you install an SAP system, you have to decide which transport host and directory you want to use for your SAP system: Use the transport directory that SAPinst creates during the installation of the SAP system by default on the global host: SAPinst by default creates the transport directory on the global host in \usr\sap\trans. Use a transport directory located on a host other than the default host: You can use an existing transport directory and host in your SAP system landscape. You can set up a new transport directory on a different host. In either case, you must prepare this host for use by the new SAP system [page 50].More Information

SAP Directories [page 88] See the SAP Library [page 11]: Administrator's Guide Administration of SAP NetWeaver CE General System Administration Software Lifecycle Management Using CM Services

44/176

PUBLIC

2010-03-08

4 4.1

Preparation Preparation Checklist

4 Preparation

4.1 Preparation ChecklistThis section includes the preparation steps that you have to perform for the: Standard, distributed, or high-availability system Additional application server instance Detailed information about the steps is available in the relevant section.Standard, Distributed, or High-Availability System NOTE

In a standard system, all mandatory instances are installed on one host. Therefore, if you are installing a standard system, you can ignore references to other hosts. 1. 2. If you use Windows Server 2008, you temporarily disable the Windows Server 2008 firewall [page 46] on each host. If you want to configure the User Management Engine (UME) of Application Server Java (AS Java) for the user management of a separate ABAP system, you have to prepare user management for an external ABAP System [page 95]. You perform basic preparations on Windows [page 46]. You check that you have the required user authorization for running SAPinst [page 48]. If required, you prepare the SAP system transport host [page 50] for your SAP system. You download the JCE Policy zip file [page 50] on the installation host. You make sure that the required installation media [page 51] are available on each host.Only valid for: HA (MSCS) |

3. 4. 5. 6. 7. 8.

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

9.

You can continue with Installation [page 55].

Additional Application Server Instance

You have to perform the following preparations on the host where you install the additional application server instances: 1. If you use Windows Server 2008, you temporarily disable the Windows Server 2008 firewall [page 46] on each host. 2. You perform basic preparations on Windows [page 46]. 3. You check that you have the required user authorization for running SAPinst [page 48].

2010-03-08

PUBLIC

45/176

4 4.2

Preparation Disabling the Windows Server 2008 Firewall Temporarily

4. 5. 6.

If required, you prepare the SAP system transport host [page 50]. You make sure that the required installation media [page 51] are available. You can continue with Installation [page 55].

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

sap netweaver ce 7.2 installation guide

Documents