SAP Solution Manager 4.0 Installation Guide

PUBLIC

Installation Guide

SAP Solution Manager4.0 SR1 Windows: MSSQL ServerTarget Audience

n Technology consultants

n System administrators

Document version: 1.0 ‒ 09/11/2006

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmittedin any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components of othersoftware vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere,Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPowerand PowerPC are trademarks or registered trademarks of IBMCorporation.

Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of

the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of SunMicrosystems, Inc.,

used under license for technology invented and implemented byNetscape.

MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver,

and other SAP products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks ofSAP AG in Germany and in several other countries all over theworld. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in thisdocument serves informational purposes only. National productspecifications may vary.

These materials are subject to change without notice. Thesematerials are provided by SAP AG and its affiliated companies(“SAP Group”) for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall notbe liable for errors or omissions with respect to the materials.

The only warranties for SAP Group products and services arethose that are set forth in the express warranty statementsaccompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2005-12-31(V3.2) and XSLT processor SAXON 6.5.2 from Michael Kay(http://saxon.sf.net/), XSLT version 1.

DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java™ Source Code delivered with this product is onlyto be used by SAP’s Support Services and may not be modified oraltered in any way.

Legal Software Terms

Terms for Included Open Source SoftwareThis SAP software contains also the third party open sourcesoftware products listed below. Please note that for these thirdparty products the following special terms and conditions shallapply.

1. This software was developed using ANTLR.

2. gSOAPPart of the software embedded in this product is gSOAPsoftware. Portions created by gSOAP are Copyright (C)2001-2004 Robert A. van Engelen, Genivia inc. All RightsReserved.THE SOFTWARE IN THIS PRODUCT WAS IN PARTPROVIDED BY GENIVIA INC AND ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITYAND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE AUTHOR BELIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENTOF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

ii PUBLIC 09/11/2006

HOWEVERCAUSEDANDONANYTHEORYOF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANYWAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

3. SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingNeurottstrasse 1669190 Walldorf, Germany(hereinafter: SAP)

and

you(hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive,non-transferrable, royalty-free license to usethe STLport.org C++ library (STLport) and itsdocumentation without fee.

B) By downloading, using, or copying STLport or anyportion thereof Customer agrees to abide by theintellectual property laws, and to all of the termsand conditions of this Agreement.

C) The Customer may distribute binaries compiledwith STLport (whether original or modified)without any royalties or restrictions.

D) Customer shall maintain the following copyrightand permissions notices on STLport sources and itsdocumentation unchanged: Copyright 2001 SAPAG

E) The Customer may distribute original or modifiedSTLport sources, provided that:n The conditions indicated in the above

permissions notice are met;n The following copyright notices are retained

when present, and conditions provided inaccompanying permission notices are met:

Coypright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon GraphicsComputer Systems Inc.Copyright 1997 Moscow Center for SPARCTechnology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute andsell this software and its documentation for anypurposes is hereby granted without fee, providedthat the above copyright notice appear in all

copies and that both that copyright notice andthis permission notice appear in supportingdocumentation. Hewlett-Packard Company makesno representations about the suitability of thissoftware for any purpose. It is provided “as is”without express or implied warranty.

Permission to use, copy, modify, distribute and sellthis software and its documentation for any purposeis hereby granted without fee, provided that theabove copyright notice appear in all copies andthat both that copyright notice and this permissionnotice appear in supporting documentation.Silicon Graphics makes no representations aboutthe suitability of this software for any purpose.It is provided “as is” without express or impliedwarranty.

Permission to use, copy, modify, distribute andsell this software and its documentation for anypurposes is hereby granted without fee, providedthat the above copyright notice appear in allcopies and that both that copyright notice andthis permission notice appear in supportingdocumentation. Moscow Center for SPARCmakesno representations about the suitability of thissoftware for any purpose. It is provided “as is”without express or implied warranty.Boris Fomitchev makes no representations aboutthe suitability of this software for any purpose.This material is provided "as is", with absolutely nowarranty expressed or implied. Any use is at yourown risk. Permission to use or copy this softwarefor any purpose is hereby granted without fee,provided the above notices are retained on all copies.Permission to modify the code and to distributemodified code is granted, provided the above noticesare retained, and a notice that the code was modifiedis included with the above copyright notice.

Permission to use, copy, modify, distribute andsell this software and its documentation for anypurposes is hereby granted without fee, providedthat the above copyright notice appear in allcopies and that both that copyright notice andthis permission notice appear in supportingdocumentation. SAP makes no representationsabout the suitability of this software for any purpose.It is provided with a limited warranty and liabilityas set forth in the License Agreement distributedwith this copy. SAP offers this liability and warrantyobligations only towards its customers and onlyreferring to its modifications.

b) Support and Maintenance

09/11/2006 PUBLIC iii

SAP does not provide software maintenance for theSTLport. Software maintenance of the STLporttherefore shall be not included.All other services shall be charged according to therates for services quoted in the SAP List of Prices andConditions and shall be subject to a separate contract.

c) Exclusion of warrantyAs the STLport is transferred to the Customer on aloan basis and free of charge, SAP cannot guaranteethat the STLport is error-free, without material defectsor suitable for a specific application under third-partyrights. Technical data, sales brochures, advertisingtext and quality descriptions produced by SAP do notindicate any assurance of particular attributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall onlybe liable for damage, including unauthorizedoperation, if this (i) can be compensated under theProduct Liability Act or (ii) if caused due to grossnegligence or intent by SAP or (iii) if based on thefailure of a guaranteed attribute.

B) If SAP is liable for gross negligence or intent causedby employees who are neither agents or managerialemployees of SAP, the total liability for such damageand a maximum limit on the scope of any suchdamage shall depend on the extent to which itsoccurrence ought to have anticipated by SAP whenconcluding the contract, due to the circumstancesknown to it at that point in time representing atypical transfer of the software.

C) In the case of Art. 4.2 above, SAP shall not be liablefor indirect damage, consequential damage causedby a defect or lost profit.

D) SAP and the Customer agree that the typicalforeseeable extent of damage shall under nocircumstances exceed EUR 5,000.

E) The Customer shall take adequate measures for theprotection of data and programs, in particular bymaking backup copies at the minimum intervalsrecommended by SAP. SAP shall not be liable forthe loss of data and its recovery, notwithstandingthe other limitations of the present Art. 4 if thisloss could have been avoided by observing thisobligation.

F) The exclusion or the limitation of claims inaccordance with the present Art. 4 includes claimsagainst employees or agents of SAP.

4. Adobe Document ServicesAdobe, the Adobe logo, Acrobat, PostScript, and Reader areeither registered trademarks or trademarks of Adobe SystemsIncorporated in the United States and / or other countries.For information on Third Party software delivered withAdobe document services and Adobe LiveCycle Designer,see SAP Note 854621.

Documentation in the SAP Service MarketplaceYou can find this document at the following address:service.sap.com/instguides

iv PUBLIC 09/11/2006

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

Typographic Conventions

Example Description

<> Angle brackets indicate that you replace these words or characters with appropriate entries tomake entries in the system, for example, “Enter your <User Name>”.

® Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

Example Textual cross-references to a URL, for example, www.sap.com

/example Shortcuts added to the URL of a homepage to enable quick access to specific content on theWeb

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

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

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn File and directory names and their paths, names of variables and parameters, and names of

installation, upgrade, and database tools

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

EXAMPLE Keys on the keyboard

09/11/2006 PUBLIC v



Document History

.Caution

Before you start the implementation, make sure you have the latest version of this document.You can find the latest version in SAP Service Marketplace at the following internet address:service.sap.com/instguides.

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

Version Date Description

1.0 9/11/2006 Initial Version

vi PUBLIC 09/11/2006

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . 21.3 Information Available on SAP Service Marketplace . . . . . . . . . . . . . . 21.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 Basic System Variants for SAP Solution Manager . . . . . . . . . . . . . . . 52.2 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . . . . . 72.3 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 82.3.1 Distribution of Components to Disks . . . . . . . . . . . . . . . . . . . 92.3.2 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . . . . . 152.5 Multi-Language and Unicode Support . . . . . . . . . . . . . . . . . . . 202.6 Running Adobe Document Services on Non-Supported Platforms . . . . . . . . 21

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . 233.1.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . . . . . 243.1.2 Requirements Checklist for a Central System . . . . . . . . . . . . . . . . 253.1.3 Requirements Checklist for a Distributed System . . . . . . . . . . . . . . . 263.1.3.1 Requirements Checklist for the ABAP Central Services Instance . . . . . . . . . 273.1.3.2 Requirements Checklist for the Central Services Instance . . . . . . . . . . . . 283.1.3.3 Requirements Checklist for the Database Instance . . . . . . . . . . . . . . 293.1.3.4 Requirements Checklist for the Central Instance . . . . . . . . . . . . . . . 303.1.3.5 Requirements Checklist for the Dialog Instance . . . . . . . . . . . . . . . 323.2 Checking for the Windows File System . . . . . . . . . . . . . . . . . . . 333.3 Checking the Windows Domain Structure . . . . . . . . . . . . . . . . . 333.4 Reducing the Size of the File Cache . . . . . . . . . . . . . . . . . . . . 343.5 Granting User Rights for the Installation . . . . . . . . . . . . . . . . . . 343.6 Performing a Domain Installation Without Being a Domain Administrator . . . . . 363.7 Preparing the SAP System Transport Host . . . . . . . . . . . . . . . . . 383.8 Installing the SAP Front-End Software . . . . . . . . . . . . . . . . . . . 393.9 Installing the Java Development Kit . . . . . . . . . . . . . . . . . . . . 403.10 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . . . . . 413.11 Downloading Installation DVDs from SAP Service Marketplace (Optional) . . . . . 42

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.1 Installing the SQL Server Database Software . . . . . . . . . . . . . . . . . 45

09/11/2006 PUBLIC vii

4.1.1 Installing the SQL Server Database Software with SQL4SAP . . . . . . . . . . . 454.1.2 Installing the SQL Server Database Software Manually . . . . . . . . . . . . . 464.1.2.1 Installing the SQL Server 2000 Database Software on 32-Bit Manually . . . . . . . . 474.1.2.2 Installing the SQL Server 2000 Database Software on 64-Bit Manually . . . . . . . 494.1.2.3 Installing the Corrected MS SQL Server Collation for MS SQL Server 2000 . . . . . . 514.1.2.4 Installing the SQL Server 2005 Database Server Software Manually . . . . . . . . . 524.1.2.5 Installing the SQL Server 2005 Native Client Software Manually . . . . . . . . . 554.2 Preparing your System for an Java Add-In Installation . . . . . . . . . . . . . 554.3 Installing an SAP System Using SAPinst . . . . . . . . . . . . . . . . . . 564.3.1 Running SAPinst on Windows . . . . . . . . . . . . . . . . . . . . . . 564.3.2 Installing a Java Add-In for an Already Existing Solution Manager ABAP System with SAPinst

(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.3.3 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . . . . . 644.3.4 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . 654.3.5 Performing a Remote Installation with SAPinst (Optional) . . . . . . . . . . . 664.3.6 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . . . . . 67

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 715.1 Starting and Stopping the SAP System . . . . . . . . . . . . . . . . . . . 715.2 Logging On to the SAP System . . . . . . . . . . . . . . . . . . . . . . 725.3 Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . 745.4 Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . 745.5 Configuring Remote Connection to SAP Support . . . . . . . . . . . . . . 755.6 Performing Initial ABAP Configuration . . . . . . . . . . . . . . . . . . 755.7 Checking the SAP Java Documentation . . . . . . . . . . . . . . . . . . 765.8 Applying the Latest Kernel and Support Packages . . . . . . . . . . . . . . . 785.9 Performing a Full Installation Backup . . . . . . . . . . . . . . . . . . . 795.10 Single Sign-On with Microsoft Lan Manager SSP . . . . . . . . . . . . . . . 805.10.1 Preparing the Application Server for Single Sign-On . . . . . . . . . . . . . . 815.10.2 Preparing SAP GUI and SAP Logon for Single Sign-On . . . . . . . . . . . . . 825.10.3 Mapping SAP System Users to Windows Users for Single Sign-On . . . . . . . . . 835.11 Single Sign-On with Microsoft Kerberos SSP . . . . . . . . . . . . . . . . . 845.11.1 Preparing the Central Instance . . . . . . . . . . . . . . . . . . . . . 855.11.2 Configuring the SAP Front End . . . . . . . . . . . . . . . . . . . . . 865.11.3 Activating Single Sign-On for the SAP Logon . . . . . . . . . . . . . . . . 875.11.4 Mapping SAP Users to Windows Users . . . . . . . . . . . . . . . . . . . 885.12 Post-Installation Steps for Adobe Document Services . . . . . . . . . . . . . 895.12.1 Assigning Roles to Users ADSUSER and ADS_AGENT . . . . . . . . . . . . . 895.12.2 Installation Check and Quick Tests for Adobe Document Services . . . . . . . . . 895.13 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . 915.14 Configuring SAP Solution Manager . . . . . . . . . . . . . . . . . . . . 93

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . 956.1 Database Installation for Multiple Components with MS SQL Server . . . . . . . . 956.1.1 Default or Named MS SQL Server Instances . . . . . . . . . . . . . . . . . 966.2 Installation of Multiple Components in One Database (Optional) . . . . . . . . . 97

viii PUBLIC 09/11/2006

6.3 Integration of LDAP Directory Services (Optional) . . . . . . . . . . . . . . 996.4 Preparing the Active Directory (Optional) . . . . . . . . . . . . . . . . 1016.5 Preparing User Management for an External ABAP System . . . . . . . . . . 1026.6 Configuring User Management to Use an LDAP Directory (Optional) . . . . . . 1056.7 Entries in the Services File Created by SAPinst . . . . . . . . . . . . . . . 1056.8 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . . . . 1066.8.1 Running SAPinst to Delete an SAP System . . . . . . . . . . . . . . . . 1066.9 SAP System Security on Windows . . . . . . . . . . . . . . . . . . . 1086.10 Automatic Creation of Accounts and Groups . . . . . . . . . . . . . . . 1096.11 Manually Granting User Rights for the Installation . . . . . . . . . . . . . 1116.12 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . 1126.12.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . 112

Chapter 7 High Availability with Microsoft Cluster Service . . . . . . . . . . . . 1157.1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167.1.1 SAP System Components in an MSCS Configuration . . . . . . . . . . . . 1167.1.2 Enqueue Replication Server in an MSCS Configuration . . . . . . . . . . . 1197.1.3 Distribution of Components to Disks for MSCS . . . . . . . . . . . . . . 1207.1.4 Directories in an MSCS Configuration . . . . . . . . . . . . . . . . . . 1227.1.5 IP Addresses in an MSCS Configuration . . . . . . . . . . . . . . . . . 1227.1.6 Obtaining IP Addresses for MSCS . . . . . . . . . . . . . . . . . . . . 1267.1.7 Checking Hardware and Software Requirements for MSCS . . . . . . . . . . 1287.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307.2.1 Assigning Drive Letters for MSCS . . . . . . . . . . . . . . . . . . . . 1307.2.2 Mapping Host Names to IP Addresses for MSCS . . . . . . . . . . . . . . 1317.2.3 Checking the Mapping of Host Names for MSCS . . . . . . . . . . . . . . 1317.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327.3.1 Clustering the SQL Server Database Software . . . . . . . . . . . . . . . 1337.3.1.1 Clustering the SQL Server 2000 Database Software in a 32-Bit System . . . . . . . 1337.3.1.2 Clustering the SQL Server 2000 Database Software in a 64-Bit System . . . . . . . 1357.3.1.3 Clustering the SQL Server 2005 Database Server Software . . . . . . . . . . . 1377.3.2 Moving MSCS Groups . . . . . . . . . . . . . . . . . . . . . . . . 1417.3.3 Rebooting During the Installation or Conversion for MSCS . . . . . . . . . . 1427.3.4 Installing the Central Services Instance for ABAP (ASCS) . . . . . . . . . . . 1427.3.5 Installing the Central Services Instance (SCS) . . . . . . . . . . . . . . . 1427.3.6 Configuring the First MSCS Node . . . . . . . . . . . . . . . . . . . 1437.3.7 Installing the Database Instance . . . . . . . . . . . . . . . . . . . . 1447.3.8 Configuring the Additional MSCS Node . . . . . . . . . . . . . . . . . 1447.3.9 Installing an Enqueue Replication Server . . . . . . . . . . . . . . . . . 1467.3.10 Installing the Central Instance . . . . . . . . . . . . . . . . . . . . . 1477.3.11 Installing the Dialog Instance . . . . . . . . . . . . . . . . . . . . . 1477.4 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 1487.4.1 Starting and Stopping the SAP System in an MSCS Configuration . . . . . . . . 1487.4.2 Post-Installation Checks for Enqueue Replication Server . . . . . . . . . . . 1497.4.2.1 Checking the Status of the Enqueue Replication Server with ENSMON . . . . . . 1497.4.2.2 Monitoring the Lock Table During Failover with ENQT . . . . . . . . . . . 150

09/11/2006 PUBLIC ix

Chapter A Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153A.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . 153

x PUBLIC 09/11/2006

1 Introduction

1 Introduction

This document explains how to install SAP Solution Manager 4.0 SR1. For more information about SAPSolution Manager, see SAP Service Marketplace at service.sap.com/solutionmanager.SAP Solution Manager 4.0 SR1 (Solution Manager for short) is based on SAP Solution Manager 4.0 SP06

and on the underlying technology of SAP NetWeaver 2004s SP08. For more information about the technologyprovided by SAP NetWeaver, see SAP Service Marketplace at service.sap.com/netweaver.

Constraints

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

n Youmust only use the SAP installation tools according to the instructions and for the purposes describedin the SAP installation document. Improper use of the SAP installation tools can damage files and systemsalready installed.

n SAP system installations should only be performed by SAP Technical Consultants who are certified foryour operating system, your database, and the SAP system that you are installing.

n For downward-compatible releases of DB/OS platforms for SAP products, SAP plans to regularly releasethe newest database (DB) and operating-system (OS) versions of SAP products. These releases aredownward-compatible with earlier SAP system releases.Note that for already shipped SAP components, we only support the installation for database versionsproposed by the installation tool. Therefore, you must install a SAP component or perform a system copyusing a downward-compatible database as follows:l Install the component with the old proposed database version.l Upgrade the old database version to the downward-compatible new version.

1.1 New Features

Here you can find the new features in this release.

SAP System Installation

Area Description

SAPinst As of SAP NetWeaver 2004s SAPinst has the following new features:n You can check the prerequisites for the installation of your SAP system with the Prerequisite

Checker [page 24].n You can uninstall an SAP system or an SAP component with the SAPinst service Uninstall ‒

System / Standalone Engines / Optional Standalone Unit.n You can install the Java Add-In to an already existing ABAP system.n You can change the default names of the Java users J2EE_ADMIN, J2EE_GUEST and SAPJSF

during the input phase of the installation.n You assign one Master Password to all users created by SAPinst. This password is used for all

user accounts and for the secure store key phrase.

09/11/2006 PUBLIC 1

1 Introduction

1.2 SAP Notes for the Installation

Area Description

n SAPinst initializes most of the input parameter fields with default values.If required, you can change each default value by choosing to revise the related parametersection in the Parameter Summary screen before you start the processing phase of the installation.

Installation DVDs You start the installation from a single Installation Master DVD, which is the same for alldatabases.

Operating Systems

Area Description

Support of OperatingSystems

See the Product Availability Matrix (PAM) on SAP Service Marketplace atservice.sap.com/platforms ® Product Availability Matrix.

Documentation

Area Description

SAP Notes You can now access SAP Notes directly in SAP Service Marketplace from your PDF.Place the cursor on the SAP Note “<number>” and double-click. A separate browserwindows opens and the SAP Note is displayed.

Standalone Gateway Installation The installation of a standalone gateway is now covered in a dedicated installationguide, available at service.sap.com/installnw2004s ® Installation - Standalone Engines& Clients ® Installation Guide - Gateway on <platform>

1.2 SAP Notes for the Installation

Youmust read the following SAP Notes before you start the installation. These SAP Notes contain the mostrecent 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 in the SAP Service

Marketplace at service.sap.com/notes.

SAP Notes for the Installation Title Description

918078 SAP Solution Manager 4.0 / 4.0 SR1Installation

Central installation note for SAPSolution Manager 4.0 / SAP SolutionManager 4.0 SR1.

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

1.3 Information Available on SAP Service Marketplace

More information is available as follows on SAP Service Marketplace.

2 PUBLIC 09/11/2006



1 Introduction

1.3 Information Available on SAP Service Marketplace

Documentation

Description Internet Address Title

List of media for installation orupgrade for SAP Solution Manager 4.0SR1

service.sap.com/instguides ® SAPComponents ® SAP Solution Manager ®Release 4.0

Media List ‒ SAP Solution Manager 4.0 SR1

Master Guide SAP Solution Manager4.0


Master Guide ‒ SAP Solution Manager 4.0

Upgrade to SAP Solution Manager 4.0 service.sap.com/instguides ® SAPComponents ® SAP Solution Manager ®Release 4.0

Upgrade Guide ‒ SAP Solution Manager 4.0<OS> <Database>

Configuration of SAP SolutionManager


Configuration Guide ‒ SAP Solution Manager4.0 SR1

Front End installation service.sap.com/installNW2004s Front End Installation Guide (this guide is alsoavailable on the Presentation DVD)

Homogeneous and heterogeneoussystem copy for SAP systems based onNetWeaver 2004s

service.sap.com/installNW2004s Homogeneous and Heterogeneous System Copyfor SAP Systems based on SAP NetWeaver2004s

Migration Guide Solution ManagerDiagnostics


Migration Guide for Solution ManagerDiagnostics SAP NetWeaver 04s SP Stack<current stack>

Setup Advanced Guide SolutionManager Diagnostics 04s


Advanced Supportability Setup Guidefor Solution Manager Diagnostics SAPNetWeaver 04S

Installation of the System LandscapeDirectory (SLD)

service.sap.com/installNW2004s ®Configuration

Post-Installation Guide ‒ System LandscapeDirectory SAP NetWeaver 2004s

SAP NetWeaver Problem AnalysisGuide (PAG)

help.sap.com/nw2004s ® SAPNetWeaver Library ® SAP NetWeaverby Key Capability ® Solution Life CycleManagement by Key Capability ® SAPNetWeaver Problem Analysis Guide (PAG)

SAP NetWeaver Problem Analysis Guide(PAG)

General Quick Links

Description Internet Address

SAP Help Portal help.sap.com

SAP NetWeaver Library in SAP Help Portal help.sap.com/nw2004s

SAP Notes service.sap.com/notes

Released platforms and operating systems service.sap.com/platforms

Unicode SAP systems and their availability service.sap.com/unicode

System sizing (Quick Sizer tool) service.sap.com/sizing

High availability service.sap.com/ha

09/11/2006 PUBLIC 3

1 Introduction

1.4 Naming Conventions

Description Internet Address

Security service.sap.com/security

.NoteFor information on Windows operating system security, see:www.microsoft.com/security

Information on SAP Support Package Stacks service.sap.com/sp-stacks

SAP Solution Manager service.sap.com/solutionmanager

1.4 Naming Conventions

In this documentation, the following naming conventions apply:

Terminology

n SAP system refers to SAP Solution Manager.n ABAP+Java system refers to the two stacks (ABAP and Java) of SAP Solution Manager.

Variables

Variables Description

<SAPSID> SAP system ID in uppercase letters

<sapsid> SAP system ID in lowercase letters

<DBSID> Database ID in uppercase letters

<dbsid> Database ID in lowercase letters

<host_name> Name of the corresponding host

<INSTDIR> Installation directory for the SAP system

<DVD_DIR> Directory on which a DVD is mounted

<OS> Operating system name within a path

<SCHEMA_ID> Database schema ID

The following example shows how the variables are used:

.Example

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

4 PUBLIC 09/11/2006

2 Planning

2 Planning

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

Only valid for: HA (MSCS)

If you want to perform a high-availability installation withMicrosoft Cluster Service (MSCS), see HighAvailability with Microsoft Cluster Service [page 115].End of: HA (MSCS)

You have to complete the following planning activities:

1. You plan how to distribute the instances to hosts [page 7].2. You plan your system configuration [page 8].3. You identify basic SAP system parameters [page 15].4. You decide whether you want to use Unicode and multi-language support [page 20].5. If you want to use Adobe Document Services (ADS), you check what you have to do in case your platform is not

supported for ADS [page 21].

The following planning activities are optional:

n Database Installation for Multiple Components with MS SQL Server [page 95]n Installation of Multiple Components in One Database (MCOD) [page 97]

2.1 Basic System Variants for SAP Solution Manager

The following section provides information about the basic SAP system variants for SAP Solution Manager andabout the possibilities to distribute SAP instances within themSAP Solution Manager is an ABAP+Java system.An ABAP+Java System can be the result of

n an ABAP+Java installationn a Java Add-In installation for an already existing ABAP system

Mandatory instances of an ABAP+Java system are the central instance, the central services instance, andthe database instance.

.Note

The Java central services instance is named SCS instance.The ABAP central services instance is named ASCS instance. The ASCS is only available for a high

availability installation.

You can then operate both the ABAP application server and the J2EE Engine on the SAP system.Optionally, you can install one or more dialog instances, if required.

09/11/2006 PUBLIC 5

2 Planning

2.1 Basic System Variants for SAP Solution Manager

.Note

Each instance can reside on a separate host.


For more information on how to distribute a high-availability Solution Manager system, see SAP SystemComponents in an MSCS Configuration [page 116].End of: HA (MSCS)

Figure 1: Minimum System Distribution (Central System)

For a minimum system distribution, all instances reside on one host.

6 PUBLIC 09/11/2006

2 Planning

2.2 How to Distribute Instances to Hosts

Figure 2: Maximum Distribution for a Distributed System

For a maximum system distribution, each instance resides on a separate host.

2.2 How to Distribute Instances to Hosts

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

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

n Distributed system on several hostsYou perform the following steps:1. You specify or create a shared transport directory.2. You run SAPinst and install the:l Central services instance (SCS) on the global hostl Database instance on the database host

l Central instance on the central instance host

l Dialog instance(s), if required, on the dialog instance host(s)The following graphic shows how to distribute your instances to several hosts:

09/11/2006 PUBLIC 7

2 Planning

2.3 System Configuration

Figure 3: Distribution of Instances in an ABAP+Java System


You need to consider the following aspects:

n You and your hardware partner plan the distribution of your SAP system instances within the basic system variants [page 5].n You and your hardware partner work out a high-performance configuration based on sizing information

that reflects the system workload, such as:l The set of applications to be deployedl How intensively the applications are to be usedl The number of users

n You decide whether to perform a domain or local installation:l Local installation

You need to be Local Administrator of the machine involved. In a local installation, all Windowsaccount and user information is stored locally on one host and is not visible to any other hosts inthe system.If the SAP system is to run on a singlemachine, you can perform a local installation.

8 PUBLIC 09/11/2006

2 Planning


.Caution

If you install a distributed system as a local installation, this can lead to authorization problemsfor the operating system users <sapsid>adm and SAPService<SAPSID>, as well as to problems withthe transport directory, which is usually shared by several SAP systems. Therefore, SAP does notsupport a local installation for a distributed system and recommends you to install a distributedsystem as a domain installation.If you still want to perform a local installation for a distributed system, make sure that:

u You use the same password for the <sapsid>adm or the SAPService<SAPSID> user on all hosts.

The password for the <sapsid>adm and SAPService<SAPSID> user can differ.

u You use the same master password on all hosts.

u All hosts belong to the same Windows work group.

l Domain installationYou need to be Domain Administrator of the domain involved, and all machines in the system mustbelong to the same domain. In a domain installation, the user information is stored centrally on thedomain controller and is accessible to all hosts in the system.If the system is to be distributed acrossmore than onemachine, SAP strongly recommends you toperform a domain installation to avoid authorization and support problems.

.Caution

If for any reason, you are not granted domain administrators rights, you can perform theinstallation as a domain user who is a member of the local administrators group. However, thedomain administrator has to prepare the system appropriately for you.For more information, see Performing a Domain Installation without being a Domain Administrator [page 36].

For more information on user rights for a local or domain installation, see: Granting User Rights for theInstallation [page 34].

2.3.1 Distribution of Components to Disks

When you install the SAP system with an MS SQL Server database, the main directories required for the systemare automatically created. However, during the installation procedure you have to explicitly specify wherethese directories are to be located, that is, on which drives or disks they must reside. The assignment of thedirectories to drives and corresponding disks fundamentally affects the security and performance of thesystem and must therefore be carefully considered.The following graphic gives you an overview of the main SAP system components and directories, their

purpose, and the amount of free space they initially require. A good distribution of these to disks ensures that:

n Enough free space is available for system growthn The data is secure

n Performance is good

09/11/2006 PUBLIC 9

2 Planning


Figure 4: System Components and Directories

Database Components

When you install an SAP system with MS SQL Sever, the central components of the database are the SQLServer program files, tempdb files, SAP data files and transaction log files. The log files record all thechanges made to the database to enable restore and recovery. The tempdb holds all temporary tables and storedprocedures. The data files contain the data for the SAP system.

n SAP Data FilesThe data files are created by default in the directories \<SAPSID>DATA<N>. The first data file is called<SAPSID>DATA1.mdf and subsequent files<SAPSID>DATA<N>.ndf, where <N> denotes the number of the file.You can change the default value of these directories. The minimum space required for all files is 20 GB.For security reasons, locate the data files on a separate disk system. They should not be included in the samedisk system as the log files or other SQL server program and database files. To ensure data redundancy,SAP recommends the use of RAID 5.

n Transaction Log FileThe transaction log for the database is created by default in the directory\<SAPSID>LOG1. The log file iscalled <SAPSID>LOG1.ldf and requires a minimum of 1 GB space. You can change the default directory ofthe transaction log directory.The transaction log file records all the changes made to the database and, if required, enables modificationsto be redone or undone. It plays a crucial role when the database has to be restored due to database damageor media failure. For this reason it should be stored very securely. SAP recommends the use of RAID1 which implements hardware-based mirroring.

10 PUBLIC 09/11/2006

2 Planning


n Program FilesThe files other than the SAP 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 and tempdb

database files. Locate these on a separate, third, disk system and not on the same disks as the transaction logfiles or SAP data files. SAP recommends the use of RAID 1.For performance reasons, it is advisable to place the tempdb files on a fast disk system. This is particularlyrecommended because the tempdb is frequently accessed during SQL Server operation and could otherwiseaffect 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

Figure 5:

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

09/11/2006 PUBLIC 11

2 Planning


.Note

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

Figure 6: Distribution of Components to RAID Arrays

Distribution of Directories to Arrays

Array 1 \Program files\Microsoft SQL Server

\TEMPDB

Array 2 \<SAPSID>DATA1

\<SAPSID>DATA2

\<SAPSID>DATA3

Array 3 \<SAPSID>log1

Optimizing Performance

If you wish to optimize performance, isolate the tempdb on a separate, fast disk. This improves performancesignificantly 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.

12 PUBLIC 09/11/2006

2 Planning


2.3.2 SAP Directories

During the SAP system installation, the \usr\sap directory is created on the:

n Global host and shared with the name sapmntOn global hosts, the \usr\sap directory containsl general SAP softwarel global and local (instance-specific) data.All instances of an SAP system access this directory on the global host using the Universal NamingConvention (UNC) path.

n Local host and shared with the name saploc.On local hosts, the \usr\sap directory containsl copies of the SAP softwarel local (instance-specific) data.The executables on the local host are replicated from those on the global host each time the local instanceis started.

.Note

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

The following graphic shows how the physical directory \usr\sap is shared on the global host and in adistributed installation. In both cases, the UNC pathes are used as follows:

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

09/11/2006 PUBLIC 13

2 Planning


Figure 7: Directory Structure on the Global Host in an ABAP+Java System

The above graphic shows the directory structure on the global host. The global data (binaries) is stored in theglobal directories on the global host and physically exists only once for each SAP system. Other applicationserver access the data using the UNC path, \\<SAPGLOBALHOST>\sapmnt, where SAPGLOBALHOST is replacedby the SAP system with the name of the global host. The global host has the SAP\<SAPSID>\SYS directorystructure.Every time an instance starts, the SAP copy program sapcpe compares the binaries in the

<platform>-directory on the global host and the binaries in the exe-directory on the application server. Ifthe binaries in the exe directory are elder than those in the <platform>-directory, sapcpe replaces themwith the newer version of the global host.

14 PUBLIC 09/11/2006

2 Planning

2.4 Basic SAP System Parameters

Figure 8: Directory Structure for a Distributed ABAP+Java System

The above graphic shows how the distributed instances, interacts with the global host.Distributed instances use SAPGLOBALHOST to access global data on the global hostIn a distributed system, the parameters SAPGLOBALHOST and SAPLOCALHOST have different values.In a distributed system, the parameters SAPGLOBALHOST and SAPLOCALHOST have the same values on the

global host with an SCS instance.


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

.Note

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

09/11/2006 PUBLIC 15

2 Planning


SAP System ID and Database ID

Parameters Description Enter Your Values

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

.CautionChoose your SAP system ID carefully. You cannot changethe SAP system ID after the installation.

Make sure that your SAP system ID:n Is unique throughout your organizationn Consists of exactly three alphanumeric charactersn Contains only uppercase lettersn Has a letter for the first charactern Does not include any of the following, which are reserved IDs:

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

KEY LOG MON NIX NOT OFF OMS RAW ROW SAP SET SGA SHG

SID SQL SYS TMP UID USR VAR

...

Database ID <DBSID> The <DBSID> identifies the database instance.The database ID <DBSID> can be different from the SAP system ID.

...

Parameters Relevant for the System Landscape


Instance Number Instance Number:Technical identifier for internal processes, consisting of atwo-digit number from 00 to 97.The instance number must be unique on a host. That is, ifmore than one SAP instance is running on the same host, theseinstances must be assigned different numbers.

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

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

...

Name of InstanceHost

Instance Host:Host name of the specific instance.To find out the host name, open a command prompt and enterhostname.For more information about the allowed host name length andcharacters, see SAP Note 611361.

...

16 PUBLIC 09/11/2006


2 Planning



Message ServerPort .

CautionMake sure that all message server port numbers on thesame host are unique.

Port number of the SAP Message Server:If you do not specify a value, the default port number is used.The message port number must be unique for the SAP systemon all hosts.ABAP Message Server PortThere is an external message server port using the parameterrdisp/msserv and an internal message server port using theparameter rdisp/msserv_internal.The ABAP message server uses both the internal and theexternal message server ports. Both message server ports areconfigured in the default profile.The external message server port uses the parameterrdisp/msserv with default value 36<nn>, where <nn> is theinstance number of the ABAP message server instance.The internal message server port uses the parameterrdisp/msserv_internalwith default value 39<nn>, where <nn>is the instance number of the ABAP message server instance.Java Message Server PortThe Java message server only uses the internalmessage serverport. The Java message server is configured in the SCS instanceprofile.The parameter rdisp/msserv is set to 0, so that the externalport is not open.The internal message server port uses the parameterrdisp/msserv_internalwith default value 39<nn>, where <nn>is the instance number of the SCS message server instance.For more information about the parameters used for internaland external message server ports, see SAP Note 821875.

...

Windows Domain SAPinst creates the <sapsid>adm and SAPService<SAPSID> usersin the domain specified. Make sure that you have domainadministrator rights before you start the installation. If not,you have to create these users manually before starting theinstallation. For more information, see Granting User Rights forthe Installation [page 34].

...

ABAP RFC User,Password

The user DDIC is normally used for the RFC logon ABAPRFC user. It has the required special administrator rights.Alternatively, you can use user SAP*.

...

09/11/2006 PUBLIC 17


2 Planning



Java users andpasswords

Administrator Name:SAPinst sets the user name J2EE_ADMIN by default.If required, you can choose another user name according toyour requirements.SAPinst sets the following user names by default.n For the Java part of an ABAP+Java system: J2EE_ADMINn For a Java system: Administrator.If required, you can choose other user names.Communication User Name:This user is used for the communication between the ABAP andthe Java part of an ABAP+Java system.SAPinst sets the user name SAPJSF by default.If required, you can choose another user name.Guest Name:SAPinst sets the user name J2EE_GUEST by default.For users who do not belong to a company or who haveregistered as company users and are pending approval. Guestusers belong to the default group Authenticated Users.The user must exist on the central ABAP system that is used forthe central user management.If required, you can revise all these default user names at theend of the input phase of the installation using the ParameterSummary screen.If the SAP User Management Engine (UME) is configuredagainst the user management of an ABAP system, enter thename of the ABAP user that is defined as administrator for thissystem.

...

CryptographyLevel ‒ JavaCryptographyExtension (JCE)

Cryptography Level:Java Cryptography Extension (JCE):The SAP Java Libraries need the JCE files for strong cryptography.For more information see Installing the Java Development Kit [page40].

...

Parameters Relevant for the Connectivity to System Landscape Directory


SLD HTTP Host The host name of the SystemLandscape Directory (SLD)

...

SLD HTTP Port The HTTP port of the Java systemwhere the SLD is installed. Thefollowing naming convention applies:5<instance_number>00.

.ExampleIf the instance number of yourJava system is 01, the SLD HTTPPort is 50100.

...

18 PUBLIC 09/11/2006

2 Planning



SLD Data Supplier User and password n If you want to install a local SLD,SAPinst creates this user duringthe installation.

n If you want to connect yoursystem to an existing central SLD,you have to enter the existing SLDData Supplier User and passwordof the central SLD during theinstallation.

.RecommendationWe recommend that you namethis user SLDDSUSER

...

SLD ABAP API User and password n If you want to install a local SLD,SAPinst creates this user duringthe installation.

n If you want to connect yoursystem to an existing central SLD,you have to enter the existing SLDData Supplier User and passwordof the central SLD during theinstallation.

.RecommendationWe recommend that you namethis user SLDAPIUSER

...

RFC User, Password The ABAP RFC user of the SLD ...

SLD Gateway Host The host on which the gatewayinstance of the SLD is running

...

SLD Gateway Instance Number The instance number of the gatewayinstance of the SLD

...

SAP System Client The client in which the ABAP RFCuser exists

...

Parameters for SAPDATA Drives


Installation drive Base directory for the SAP system.Do not add <SAPSID> as subdirectorybecause the system adds this directoryautomatically.

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

...

09/11/2006 PUBLIC 19

2 Planning

2.5 Multi-Language and Unicode Support


.NoteIf you install a subsequent SAPsystem, the saploc share alreadyexists and you cannot select theinstallation drive. SAPinst usesthe installation drive where thesaploc share points to.

Parameters Relevant for the Database


Database instance name MS SQL Server instance nameYou can also specify a remotedatabase instance.DependenciesFor a named instance enter<hostname>\<instance_name>.


In an MSCS environment, enter thevirtual host name.End of: HA (MSCS)

...

2.5 Multi-Language and Unicode Support

This section describes SAP support for multiple languages with or without Unicode:

n Unicode systemsl The default for all new installations is Unicode.

l Unicode (and the parallel ISO 10646 standard) defines the character set necessary for efficientlyprocessing text in any language and for maintaining text data integrity. In addition to global charactercoverage, the Unicode standard is unique among character set standards, because it also defines data andalgorithms for efficient and consistent text processing. This enables high-level processing and ensuresthat all compliant software produces the same results.The widespread adoption of Unicode over the last decade has made text data truly portable and formeda cornerstone of the Internet.

l Unicode is the recommended system type for all SAP systems that deploy Unicode-enabled solutionsand components.

l Unicode is the only system type which is fully supported for:u SAP systems requiring a combination of languages that are based on more than one non-Unicode

code page

u SAP systems that deploy Java applications (for example Java applications, WebDynpro applications)

u SAP ABAP systems that communicate with Java components (for example via the SAP JavaConnector)

20 PUBLIC 09/11/2006

2 Planning

2.6 Running Adobe Document Services on Non-Supported Platforms

.Note

For information about restrictions in non-Unicode system installations refer to SAP Note 838402.For information about code page support of SAP JAVA Connector refer to SAP Note 794411.

n Non-Unicode systemsSAP supports more than 30 languages in non-Unicode systems, but due to the technical limitations ofnon-Unicode code pages, only certain combinations of languages can be used without restrictions.

IntegrationThe default setup of the system is Unicode.

n If you want to use English only, you must activate the default language settings once.n If you want to use languages other than English, you must install them and activate the language settings.

For more information on installing languages, see Performing Initial ABAP Configuration [page 75] ® InstallingLanguages.

More InformationFor more information, see SAP Notes 79991 and 73606.

2.6 Running Adobe Document Services on Non-SupportedPlatforms

Adobe document services (ADS) are currently not supported to run natively on all platforms supported bySAP systems based on SAP NetWeaver, in particular on 64-bit platforms.

ProcedureTo use ADS in SAP landscapes on non-supported platforms, install an additional standalone AS Java on aplatform supported by ADS.For more information, see SAP Note 925741.

09/11/2006 PUBLIC 21






This page is intentionally left blank.

3 Preparation

3 Preparation

You have to complete the following preparations:

1. You check the hardware and software requirements [page 23] using the Prerequisites Checker.2. You check for the Windows file system [page 33].3. You check the Windows domain structure [page 33].4. If required, you reduce the size of the file cache [page 34].5. If required, you grant user rights for the installation [page 34].6. If required, you perform a domain installation without being a domain administrator [page 36].7. You prepare the SAP system transport host [page 38].8. You install the SAP front-end software [page 39].9. You install the Java Development Kit [page 40].10. You prepare the installation DVDs [page 41].11. If required, you download the installation DVDs from SAP Service Marketplace [page 42].

The following preparation activity is optional:Preparing user management for an external ABAP system [page 102].

3.1 Hardware and Software Requirements

n You check the hardware and software requirements for your operating system (OS) and the SAP instancesusing the Prerequisite Checker tool.The Prerequisite Checker provides information about the requirements that you need to meet before you startthe installation. For example, it checks the requirements for the different installation services.

.Note

l The values that are checked by the Prerequisite Checker apply to the installation of developmentsystems or quality assurance systems.

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

You can run the Prerequisite Checker as follows:l Standalone (optional):

To check the hardware and software requirements of the host on which you want to later install an SAPsystem, you can run the Prerequisite Checker standalone [page 24].

l Integrated in SAPinst (mandatory):SAPinst automatically runs the Prerequisite Checker when you install your SAP system.

n In addition, we recommend that you consult the requirements checklists tables, which provide values forthe installation of development systems or quality assurance systems. Depending on the amount ofdata involved, the requirements might change.

09/11/2006 PUBLIC 23


3 Preparation


n To get precise sizing values for production systems, you have to do one of the following:l You use the SAP Quick Sizer tool that is available on SAP Service Marketplace at service.sap.com/sizing.

You enter information about your planned system and the tool calculates the requirements.For more information, see Planning your System Landscape in theMaster Guide ‒ SAP NetWeaver 2004s, which isavailable on SAP Service Marketplace [page 2].

l You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing.n For supported operating system and Java (JDK/JRE) releases, see the Product Availability Matrix on SAP Service

Marketplace at service.sap.com/pam.n Contact your OS vendor for the latest OS patches.n Make sure that the host name meets the requirements listed in SAP Note 611361.

Process Flow

1. If required, you run the Prerequisite Checker standalone [page 24] to check the hardware and software requirements.

.Caution

If you do not fully meet the requirements, you might experience problems when working with theSAP system.

2. In addition, we recommend that you check the hardware and software requirements checklists for thefollowing system variants:n Central System [page 25]n Distributed System [page 26]

3.1.1 Running the Prerequisite Checker in Standalone Mode(Optional)

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

.Recommendation

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

.Note

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

Procedure

1. You start SAPinst [page 56].2. On theWelcome screen, choose<SAP System> ® Additional Software Lifecycle Tasks ® Additional Preparation Tasks ®

Prerequisites Check.3. Enter the required parameters when prompted in the SAPinst dialogs.

24 PUBLIC 09/11/2006


3 Preparation


.Note

For more information about each parameter, position the cursor on the parameter field and chooseF1 in SAPinst.

When you have finished, the Start Execution screen appears summarizing all parameters you have entered. Tochange a parameter, choose Back and enter a new value.

4. To start the Prerequisite Checker choose Start.

ResultAfter the check has successfully completed, the Prerequisite Check Results screen appears displaying the resultsfound.If required, you can also check the results in file prerequisite_checker_results.html, which you can

find in the installation directory.

3.1.2 Requirements Checklist for a Central System

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

Requirement Type Requirement

Hardware n Suitable backup systemn Minimum disk space:l Database Software:

2.5 GBl SAP system files (not including paging file):

5 GB (x86, AMD64)8 GB (IA64)

l SAP database files (not including paging file):u Non-Unicode (on at least 3 physically separate disks):

17 GBu Unicode (on at least 3 physically separate disks):

32 GBl 4.3 GB of temporary disk space for every required installation DVD that

you have to copy to a local hard diskTo check disk space:

1. Choose Start ® Programs ® Administrative Tools ® Computer Management ® DiskManagement.

2. Select the local drive.

3. Choose Properties.n Minimum RAM:

3 GBTo check RAM, in the Windows Explorer choose Help ® About Windows.

n Paging File Size:1 times RAM plus 8 GBFor 64-bit systems, also see SAP Note 153641. If you want to install only a smallsystem, contact your hardware partner for appropriate swap space values.To check paging file size:

09/11/2006 PUBLIC 25


3 Preparation



1. Right-clickMy Computer and choose Properties.

2. Choose Advanced ® Performance Settings.

3. If required, in section Virtual Memory, choose Change.

Software n One of the following SQL Server Enterprise Edition server software:l MS SQL Server 2000 Enterprise Edition: Server Softwareu Latest service pack and hotfix, if available.

For more information, see SAP Notes 62988 and 608651.u Unicode collation SQL_Latin1_General_CP850_BIN2

For more information on the collation for MS SQL Server 2000, see SAPNote 600027.

l MS SQL Server 2005 Enterprise Edition: Server Softwareu Latest service pack and hotfix, if available.


n English international version of one of the following:l Windows Server 2003 Standard Editionl Windows Server 2003 Enterprise Editionl Windows Server 2003 Datacenter Edition

.NoteWe strongly recommend you to use the 64-bit version of the WindowsServer 2003 editions.

.NoteIf you install SQL Server 2005, you must install at least SP 1 for WindowsServer 2003.

To check your Windows version:

1. Choose Start ® All Programs ® Accessories ® Command Prompt.

2. Enter the command winver.n Make sure that the required fonts or code pages are installed.n Make sure that NLS and corresponding saplocales are installed.n A suitable Windows Resource Kit is strongly recommended.

3.1.3 Requirements Checklist for a Distributed System

The following sections provide information about the hardware and software requirements in a distributedsystem, where the following SAP instances can reside on different hosts:

n


ABAP central services instance [page 27]End of: HA (MSCS)

n Central services instance [page 28]n Database instance [page 29]n Central instance [page 30]n Dialog instance [page 32]

26 PUBLIC 09/11/2006






3 Preparation


.Note

n The listed values only apply for development systems or quality assurance systems.n If you install multiple SAP instances on one host, you need to add up the requirements.


3.1.3.1 Requirements Checklist for the ABAP Central ServicesInstance

The ABAP central services instance (ASCS) host must meet the following requirements:


Hardware n Suitable backup systemn Minimum disk spacel ABAP Central Services Instance (ASCS) (not including paging file):

5 GB (x86, AMD64)8 GB (IA64)In addition you require 4 GB (x86, AMD64), or 8 GB (IA64) per additionalplatform.

l 4.3 GB of temporary disk space for every required installation DVD that youhave to copy to a local hard disk.

To check disk space:

1. Choose Start ® All Programs ® Administrative Tools ® Computer Management ®Disk Management.

2. Right-click the local drive and choose Properties.n Minimum RAM: 0.5 GB

To check RAM, in the Windows Explorer choose Help ® About Windows.n Paging File Size:

1 times RAM plus 8 GBTo check paging file size:




Software n One of the following SQL Server client software:l MS SQL Server 2000 Enterprise Edition: Client Tools Only

Latest service pack and hotfix, if available, for MS SQL Server 2000.For more information on the current service pack for MS SQL Server 2000 ,see SAP Note 62988.For more information on the latest hotfix for MS SQL Server 2000, see SAPNote 608651.

l MS SQL Server 2005 Native Client Softwaren English international version of one of the following:l Windows Server 2003 Standard Editionl Windows Server 2003 Enterprise Edition

09/11/2006 PUBLIC 27



3 Preparation



l Windows Server 2003 Datacenter Edition



To check the Windows version:


2. Enter the command winver.n A suitable Windows Resource Kit is strongly recommended.

End of: HA (MSCS)

3.1.3.2 Requirements Checklist for the Central Services Instance

The central services instance (SCS) host must meet the following requirements:


Hardware n Suitable backup systemn Minimum disk space:l Central Services Instance (SCS) (not including paging file):

5 GB (x86, AMD64)8 GB (IA64)

l 4.3 GB of temporary disk space for every required installation DVD that youhave to copy to a local hard disk.


1. Choose Start ® All Programs ® Administrative Tools ® Computer Management ®Disk Management.

2. Right-click the local drive and choose Properties.n Minimum RAM: 0.5 GB

To check RAM, in the Windows Explorer choose Help ® About Windows.n Paging File Size:

1 times RAM plus 8 GBTo check paging file size:





Latest service pack and hotfix, if available, for MS SQL Server 2000.

28 PUBLIC 09/11/2006

3 Preparation



For more information on the current service pack for MS SQL Server 2000 ,see SAP Note 62988.For more information on the latest hotfix for MS SQL Server 2000, see SAPNote 608651.

l MS SQL Server 2005 Native Client Softwaren English international version of one of the following:l Windows Server 2003 Standard Editionl Windows Server 2003 Enterprise Editionl Windows Server 2003 Datacenter Edition




2. Enter the command winver.n A suitable Windows Resource Kit is strongly recommended.

3.1.3.3 Requirements Checklist for the Database Instance

The database instance host must meet the following requirements:


Hardware n Suitable backup systemn Minimum disk spacel SQL Server database software: 2.5 GBl Database instance (not including paging file):u Non-Unicode (on at least 3 physically separate disks):

17 GBu Unicode (on at least 3 physically separate disks):

32 GBl 4.3 GB of temporary disk space for every required installation DVD that you have to

copy to a local hard disk.To check disk space:

1. Choose Start ® All Programs ® Administrative Tools ® Computer Management ® DiskManagement.

2. Right-click the local drive and choose Properties.n Minimum RAM:


n Paging file size:1.5 times RAM (recommended by Microsoft)To check:



09/11/2006 PUBLIC 29



3 Preparation




Software n One of the following SQL Server Enterprise Edition server software:l MS SQL Server 2000 Enterprise Edition: Server Softwareu Latest service pack and hotfix, if available.


For more information on the collation for MS SQL Server 2000, see SAP Note600027.

l MS SQL Server 2005 Enterprise Edition: Server Softwareu Latest service pack and hotfix, if available.


n English international version of one of the following:l Windows Server 2003 Standard Editionl Windows Server 2003 Enterprise Editionl Windows Server 2003 Datacenter Edition

.Notel We strongly recommend you to use the 64-bit version of the Windows Server

2003 editions.l If you install SQL Server 2005, you must install at least SP 1 for Windows Server

2003.



2. Enter the command winver.n Make sure that the required fonts or code pages are installed.n Make sure that NLS and corresponding saplocales are installed.n A suitable Windows Resource Kit is strongly recommended.

3.1.3.4 Requirements Checklist for the Central Instance

The central instance host must meet the following requirements:


For the requirements for the central instance in a high-availability system with MSCS, see the RequirementsChecklist for the Dialog Instance [page 32].End of: HA (MSCS)

30 PUBLIC 09/11/2006






3 Preparation



Hardware n Suitable backup systemn Minimum disk space:l Central Instance (CI) (not including paging file):

5 GB (x86, AMD64)8 GB (IA64)In addition you require 4 GB (x86, AMD64), or 8 GB (IA64) per additionalplatform.

l 4.3 GB of temporary disk space for every required installation DVD thatyou have to copy to a local hard disk


1. Choose Start ® All Programs ® Administrative Tools ® ComputerManagement ® Disk Management.

2. Select the local drive.

3. Choose Properties.n Minimum RAM:

1.5 GBTo check RAM, in the Windows Explorer choose Help ® About Windows.

n Paging File Size:1 times RAM plus 8 GBFor 64-bit systems, also see SAP Note 153641. If you want to install only asmall system, contact your hardware partner for appropriate swap spacevalues.To check paging file size:





Latest service pack and hotfix, if available, for MS SQL Server 2000.For more information on the current service pack for MS SQL Server2000, see SAP Note 62988.For more information on the latest hotfix for MS SQL Server 2000, seeSAP Note 608651.

l MS SQL Server 2005 Native Client Softwaren English international version of one of the following:l Windows Server 2003 Standard Editionl Windows Server 2003 Enterprise Editionl Windows Server 2003 Datacenter Edition


.NoteIf you install SQL Server 2005, youmust install at least SP 1 for WindowsServer 2003.



2. Enter the command winver.

09/11/2006 PUBLIC 31




3 Preparation



n Make sure that the required fonts or code pages are installed.n Make sure that NLS and corresponding saplocales are installed.n A suitable Windows Resource Kit is strongly recommended.

3.1.3.5 Requirements Checklist for the Dialog Instance

The dialog instance host must meet the following requirements:


Hardware n Suitable backup systemn Minimum disk space:l Dialog Instance (not including paging file):

2.5 GB (x86, AMD 64)5 GB (IA64)

l 4.3 GB of temporary disk space for every required installation DVDthat you have to copy to a local hard disk.


1. Choose Start ® All Programs ® Administrative Tools ® ComputerManagement ® Disk Management.

2. Right-click the local drive and choose Properties.n Minimum RAM:


n Paging File Size:1 times RAM plus 8 GBFor 64-bit systems, also see SAP Note 153641. If you want to installonly a small system, contact your hardware partner for appropriateswap space values.To check paging file size:





Latest service pack and hotfix, if available, for MS SQL Server 2000.For more information on the current service pack for MS SQLServer 2000, see SAP Note 62988.For more information on the latest hotfix for MS SQL Server 2000,see SAP Note 608651.

l MS SQL Server 2005 Native Client Softwaren English international version of one of the following:l Windows Server 2003 Standard Editionl Windows Server 2003 Enterprise Edition

32 PUBLIC 09/11/2006




3 Preparation

3.2 Checking for the Windows File System


l Windows Server 2003 Datacenter Edition

.NoteWe strongly recommend to use the 64-bit version of theWindows Server 2003 editions.

.NoteIf you install SQL Server 2005, you must install at least SP 1 forWindows Server 2003.



2. Enter the command winver

n A suitable Windows Resource Kit is strongly recommended

3.2 Checking for the Windows File System

You need to check that you are using the Windows File System (NTFS) on hosts where you want to install theSAP system and database. NTFS supports full Windows security and long file names.

.Note

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

Procedure

1. Open the Windows Explorer.2. Select the root directory.3. Choose File ® Properties ® General.4. The system displays the type of file system in use.5. Check that the file system is NTFS.

3.3 Checking the Windows Domain Structure

.Note

You do not need this step for a local installation.

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

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

09/11/2006 PUBLIC 33

3 Preparation

3.4 Reducing the Size of the File Cache

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

Prerequisites

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

documentation.

.Caution

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

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

3.4 Reducing the Size of the File Cache

The Windows file cache directly competes with SAP programs for memory. Therefore, you should adjust thefile cache as described below.

Procedure

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

.Caution

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

5. To confirm your entries, choose OK.

3.5 Granting User Rights for the Installation

You have to grant the required rights and privileges that authorize you to install the SAPinst tool and theSAP system.

.Caution

If you attempt the installation without the required authorization, the system aborts.

34 PUBLIC 09/11/2006

3 Preparation

3.5 Granting User Rights for the Installation

If necessary, you have to ask the system administrator to grant you the necessary authorization before youstart the installation.

Prerequisites

n The authorization required depends on whether you intend to perform a domain or local installation. Formore information, see System Configuration [page 8].

n A domain installation requires a domain controller to store user and account information centrally forthe whole system.

.Caution

l For performance and security reasons, make sure that you do not run an SAP instance (includingthe database instance) on the host where the domain controller is running.SAP does not support an SAP system installation on a domain controller.

l Do not use the user <sapsid>adm for the installation of the SAP system.

Local Installation

1. Check that you have Local Administrators rights for the central instance host.In a local installation, all Windows account and user information is stored locally on one host and is notvisible to any other hosts in the system.

2. If required, obtain these rights by asking the system administrator to enter you as a member of the LocalAdministrators group.

Domain Installation

.Note

SAP recommends to perform a domain installation.

1. Check that you have Domain Administrators rights.In a domain installation, the user information is stored centrally on the domain controller and is accessibleto all hosts in the system.

2. If required, obtain these rights by asking the system administrator to enter you as a member of the DomainAdministrators group.

.Note

If you are not granted domain administrators rights, you can perform the installation as a domainuser who is a member of the Local Administrators group. However, the domain administratorhas to prepare the system appropriately for you.For more information, see Performing a Domain Installation without being a Domain Administrator [page 36].

09/11/2006 PUBLIC 35

3 Preparation

3.6 Performing a Domain Installation Without Being a Domain Administrator


.Note

If you use an MSCS configuration, you always have to perform a domain installation.

End of: HA (MSCS)

3.6 Performing a Domain Installation Without Being a DomainAdministrator

If you are not granted domain administrator rights, you can perform the installation as a domain user who is amember of the Local Administrators group. In this case, the domain administrator must prepare the systemfor you appropriately, as described in this section.

.Note

You normally perform a domain installation of the SAP system as a user with domain administratorsrights, as described in Granting User Rights for the Installation [page 34].The domain administrator has to:

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

SAP_<SAPSID>_GlobalAdmin.

PrerequisitesYou must perform this procedure as a domain administrator.

Creating the New Global Group SAP_<SAPSID>_GlobalAdmin

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

Start ® Programs ® Administrative Tools ® Active Directory Users and Computers

.Note

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

3. Right-click Users in Tree, and choose New ® Group.

36 PUBLIC 09/11/2006

3 Preparation

3.6 Performing a Domain Installation Without Being a Domain Administrator

4. Enter the following:Group name: SAP_<SAPSID>_GlobalAdmin

.Note

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

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

6. Choose OK.

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

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

2. Enter the following:

.Note

Enter the <sapsid>adm and SAPService<SAPSID> user exactly as specified in the correct uppercase andlowercase.

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

First name: None None

Initials: None None

Last name: None None

Full name: <sapsid>adm SAPService<SAPSID>

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

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

4. Select Password never expires

.Note

Make sure that no other options are selected.

5. Choose Next ® Finish.

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

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

09/11/2006 PUBLIC 37

3 Preparation

3.7 Preparing the SAP System Transport Host

.Note

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

4. Choose OK twice.

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

1. In theUsers folder, double-click the newly created user account SAPService<SAPSID> in the list on the right.2. ChooseMember ® Add .3. Select the new SAP_<SAPSID>_GlobalAdmin group.4. Choose Add to add it to the list.5. Choose OK.

.Caution

The SAPService<SAPSID> user must not be a member of the Domain Users group.To remove this group from theMember of list:a) Select the SAP_<SAPSID>_GlobalAdmin group.b) Choose Set Primary Group.c) Select the Domain Users group.d) Choose Remove to delete it from theMember of list.

6. Choose OK to close SAPService<SAPSID> Properties.7. Close the Active Directory Users and Computers Management Console.

3.7 Preparing the SAP System Transport Host

You need to prepare one transport host in the SAP system. This host has the function of controlling theimport or export of files between the current SAP system and other SAP systems (for example, a test ordevelopment system). The transport host uses the usr\sap\trans directory to temporarily store files thathave been exported from one system and are waiting to be imported into another system. Depending on yourrequirements, you can decide to use the central instance host, the dialog instance host, or any other host asthe transport host.

.Note

For more information on preparing the SAP system transport host, see SAP Note 360515.

Procedure

1. Map the IP address of the transport host to the alias SAPTRANSHOST, using one of the following methods:n On the DNS server

If a DNS server is available for your system, ask your administrator to map the IP address of the transporthost to the alias SAPTRANSHOST.The DNS server is a database that contains a set of files with information about the TCP/IP network,including the mapping of host names or aliases to IP addresses.

38 PUBLIC 09/11/2006


3 Preparation

3.8 Installing the SAP Front-End Software

n In the hosts filesIf no DNS server is available, you can map the IP address to the alias SAPTRANSHOST in the hosts file,which you can find in the Windows default directory:<Drive>:\%windir%\system32\drivers\etc

Perform the mapping as follows:a) Open the hosts file with an editor.b) Add the following line:

<IP_address> <hostname> SAPTRANSHOST

This step assigns the alias SAPTRANSHOST to the transport host.c) Copy the newly edited hosts file to all hosts where an SAP instance is to run.

.Note

If the transport host has more than one network card, take special care when you determine the IPaddress that is entered in the hosts file or on the DNS server:l Make sure that you enter the main IP address and that the binding order is correctly defined.

l To check the binding order, choose:Start ® Settings ® Network and Dial-up Connections ® Advanced ® Advanced Settings.

2. If your transport host is not the central instance host, you have to create the transport directory as follows:a) On the transport host, create the directory \usr\sap\trans.b) Grant Everyone the permission Full Control for the directory.

.Note

These permissions are only necessary during the SAPinst installation.After the installation, you only need grant Full Control on the directory to theSAP_<SAPSID>_GlobalAdmin groups of all the systems that are part of your transport infrastructure.SAPinst assigns the appropriate rights with the help of an additional SAP_LocalAdmin group.For more information, see Automatic Creation of Accounts and Groups [page 109].

c) If no SAP instance is to be installed on the transport host, share the usr\sap directory on the transporthost as SAPMNT.This enables SAPinst to address the transport directory in the standard way as\\SAPTRANSHOST\SAPMNT\trans.

ResultYou have configured your system so that the installation tool SAPinst can recognize the transport host.

3.8 Installing the SAP Front-End Software

For the installation, make sure that the front-end software is installed on at least one host machine in yoursystem environment. To simplify the administration of your SAP system, we recommend you install thesoftware on the central instance host.

09/11/2006 PUBLIC 39

3 Preparation

3.9 Installing the Java Development Kit

With the SAP front-end installation software, SAPSetup, you can optimize the deployment of SAP GUI tothousands of clients. You can easily tailor installation packages to match your requirements, distribute patches,and set up automatic update processes for your clients.For more information on installing the front-end software, see the documentation on SAP Service

Marketplace at service.sap.com/installNW2004s:

n SAP Front End Installation Guide (English version)n SAP Frontend-Installationsleitfaden (German version)

3.9 Installing the Java Development Kit

You need to prepare the system for the J2EE Engine by installing the Java Development Kit (JDK).As of SAP NetWeaver 2004s you must install the J2EE Engine with strong encryption.The JDK includes the Java Runtime Environment (JRE), which is required both for SAPinst and the SAPinst

GUI.

.Note

If required, you can perform a remote installation using a standalone SAPinst GUI on a separate Windowsor UNIX host. This lets you perform the installation on a remote host, controlling it with the SAPinstGUI from a local host.If you want to perform a remote installation, see Performing a Remote Installation with SAPinst [page 66]. In this

case, you need at least a JRE on the local host to start the SAPinst GUI there.

Procedure

1. Check the JDK versions that are released for SAP systems in the Product Availability Matrix (PAM):a) Go to service.sap.com/pam.b) On the right-hand panel, choose SAP NetWeaver ® SAP NetWeaver 2004s ® JSE Platforms.c) Choose tab strip JSE Platforms.For additional information on the recommended JDK version and about how to obtain it, see SAP Note709140.

2. Make sure a valid JDK version is installed on every host on which you want to install an SAP instancewith the J2EE Engine, as follows:n If JDK is not already installed

Since JDK is not part of the SAP shipment, you need to download and install it.n If JDK is already installed

Check the installed version of JDK by entering the following command:java -version

.Note

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

40 PUBLIC 09/11/2006


3 Preparation

3.10 Preparing the Installation DVDs

3. As of SAP NetWeaver 2004s strong encryption is mandatory for the J2EE Engine and for all usage typesthat are deployed on it. You need to obtain the JCE policy files beforehand so that they can be installedby SAPinst:a) Download the JCE policy files for your platform at http://java.sun.com/products/jce/.b) SAPinst installs the JCE policy files during the installation process.

3.10 Preparing the Installation DVDs

You use this procedure to prepare the installation DVDs. Normally you obtain the installation DVDs as partof the installation package that you receive from SAP. However, you can also download the installation DVDs fromSAP Service Marketplace [page 42].

.Recommendation

We recommend that you make all required DVDs available in parallel.

.Caution

n If you copy the installation DVDs to disk, make sure that the paths to the location of the copied DVDsdo not contain any blanks.

n If you use network drives for mounting the Export DVDs, make sure that the <sapsid>adm user hasaccess to the UNC paths of the network drives. If the user does not yet exist, you have to create it manually[page 36] before you install the database instance.

Procedure

1. Identify the required DVDs for your installation as listed below and keep them separate from the remainingDVDs. This helps you to avoid mixing up DVDs during the installation.

.Caution

The media names listed below are abbreviated.You can find the full names of all media shipped with SAP Solution Manager in the documentMediaList ‒ SAP Solution Manager 4.0 SR1 on SAP Service Marketplace at service.sap.com/solutionmanager ®Installation Guides ® Release 4.0.

SAP Instance Installation Required DVDs

Central services instance, central instance,dialog instance

n Installation Master DVDn Kernel DVDn NetWeaver Java DVD

Database instance n Installation Master DVDn Kernel DVDn NetWeaver Java DVDn RDBMS DVDn Export DVD

09/11/2006 PUBLIC 41

3 Preparation

3.11 Downloading Installation DVDs from SAP Service Marketplace (Optional)

The following table shows the required DVDs for the installation of an Java Add-In for an upgradedABAP System:

SAP Instance Installation Required DVD

Central instance, central services instance, dialoginstance

n Installation Master DVDn NetWeaver Java DVDn Kernel DVD

Database schema n Installation Master DVDn NetWeaver Java DVDn Kernel DVD

2. Use one of the following methods to make DVDs available in parallel:n Before the installation:l Have sufficient DVD drives

l Copy DVDs manually to local hard disks

n During the installation:Use the SAPinst DVD / CD Browser dialog. You can check the entered location and then copy the entireDVD to the path you entered in the Copy Package to column.

3.11 Downloading Installation DVDs from SAP Service Marketplace(Optional)

You normally obtain the installation DVDs as part of the installation package from SAP.However, you can also download installation DVDs from SAP Service Marketplace at:service.sap.com/swdc ® Downloads® Installations and Upgrades® Entry by Application Group® <your solution>®

<release of your solution> ® <your operating system> ® <your database>.If you download installation DVDs, note that DVDs might be split into several files. In this case, you have to

reassemble the required files after the download.

PrerequisitesTo extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you canfind on SAP Service Marketplace at service.sap.com/swdc. You need at least SAPCAR 700 or SAPCAR 640with patch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR files. Formore information, see SAP Note 212876.

Procedure

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

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

42 PUBLIC 09/11/2006


3 Preparation

3.11 Downloading Installation DVDs from SAP Service Marketplace (Optional)

.Example

51031387_151031387_2...

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

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

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

.Note

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

09/11/2006 PUBLIC 43


4 Installation

4 Installation

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


.Note

If you want to perform aMicrosoft Cluster Service (MSCS) installation, see section High Availability withMicrosoft Cluster Service.

End of: HA (MSCS)

You have to perform the following steps:

1. You install the MS SQL Server database software [page 45].2. If required, you prepare your system for a Java Add-In installation [page 55].3. You install the SAP system using SAPinst [page 56].

4.1 Installing the SQL Server Database Software

The following sections describe how to install the SQL Server 2000 or SQL Server 2005 database software. TheSQL Server software has to be installed on each host in the system where you intend to set up an SAP instance.Depending on the type of host involved, you either have to install the software for the database client or server.To install the SQL Server database software you have the following options:

n You install SQL Server automatically with SQL4SAP [page 45]n You install the SQL Server database software manually [page 46].

4.1.1 Installing the SQL Server Database Software with SQL4SAP

This section describes how to install the SQL Server 2000 or SQL Server 2005 database software automatically.

.Note

For more information about installing with SQL4SAP.VBS, see Customized Installation of SQL Server for an SAPSystem with SQL4SAP.VBS (SQL4SAP_docu.pdf) and the readme.txt, both of which are located in the rootdirectory of the SQL Server RDBMS DVD.

09/11/2006 PUBLIC 45

4 Installation



.Caution

The SQL4SAP.VBS script does not support Microsoft Cluster Service (MSCS). If you want to run the scriptin an MSCS configuration, you get an error message. For more information about installing the SQLServer database software for MSCS, see Clustering the SQL Server Database Software [page 133].

End of: HA (MSCS)

n For SQL Server 2000, you use the SQL4SAP.VBS script to automatically install the:l SQL Server 2000 Enterprise Edition on 32-bit or 64-bit systems.l Latest SQL Server 2000 service packl Latest SQL Server hotfix, if required.l SQL_Latin1_General_CP850_BIN or SQL_Latin1_General_CP850_BIN2 collation.

.Note

For up-to-date information about installing SQL Server 2000 with SQL4SAP.VBS, read SAP Note377430, which also includes the material number of the DVD containing the VB script.

n For SQL Server 2005, you use the SQL4SAP.VBS script to automatically install:l One of the following SQL Server 2005 editions:

u 32-bit SQL Server 2005 Enterprise Edition on x86 systems

u 64-bit SQL Server 2005 Enterprise Edition on x64 systems

u 64-bit SQL Server 2005 Enterprise Edition on IA64 systemsl Default Instances, Named Instances, or SQL Server Client Tools Only.

.Note

For up-to-date information about installing SQL Server 2005 with SQL4SAP, read SAP Note 896566.

Procedure

1. For SQL Server 2000, insert the SQL Server 2000 RDBMS SP4 DVD into your DVD drive or mount thenetwork share locally.

2. For SQL Server 2005, insert the SQL Server 2005 RDBMS DVD in your DVD drive or mount the networkshare locally.

3. Double-click SQL4SAP.VBS located in the root directory.4. Follow the instructions and enter the required information in the installation screens.

4.1.2 Installing the SQL Server Database Software Manually

The following describes how to install the SQL Server 2000 or SQL Server 2005 database software manually.

46 PUBLIC 09/11/2006



4 Installation


.Note

If you install SQL Server 2000 the installation differs on a 32-bit or 64-bit system. If required, you also haveto install the corrected collation for SQL Server 2000.

4.1.2.1 Installing the SQL Server 2000 Database Software on32-Bit Manually

The MS SQL Server software has to be installed on each host in the system where you intend to set up an SAPinstance. Depending on the type of host involved, you either have to install the software for the databaseclient or server.

n The software for the servermust be installed on the database host. It provides all the functions requiredto run a relational database management system.

n The software for the client must be installed on all hosts without the database. It enables thecommunication between a host and the database.

Procedure

1. Log on to the host as a local administrator.

.Caution

Make sure that you have not applied NTFS compression to the disk where you install the MS SQLServer software.

2. Insert the MS SQL Server 2000 RDBMS SP4 DVD into your DVD drive.3. Start the installation program with autorun.exe located in the x86\SQL2000 directory of theMS SQL

Server 2000 RDBMS SP4 DVD.

.Note

Ignore the compatibility warning and choose Continue.

Enter the required information as specified in the table below.

.Note

When you mount the DVD from a remote server, it must be assigned a drive letter.The installation writes a log file sqlstp.log to the Windows directory %windir%

Input for MS SQL Server Installation on 32-Bit Systems

Window Server Input Client Input

Microsoft SQL Server 2000 Enterprise Edition Select SQL Server 2000 Components. Select SQL Server 2000 Components.

Install Components Microsoft SQL Server2000 Enterprise Edition

Select Install Database Server. Select Install Database Server.

Welcome Choose Next. Choose Next.

09/11/2006 PUBLIC 47

4 Installation


Window Server Input Client Input

Computer Name Select Local Computer. Select Local Computer.

Installation Selection Select Create a new instance of SQL Server,or install Client Tools.

Select Create a new instance of SQL Serveror install Client Tools.

User Information Enter your personal information. Enter your personal information.

Software License Agreement Choose Yes. Choose Yes.

CD-Key Enter the key specified in the fileSAPCDKEY.txt in the root directory ofthe RDBMS DVD.

Enter the key specified in the fileSAPCDKEY.txt in the root directory ofthe RDBMS DVD.

Installation Definition Select Server and Client Tools. Select Client Tools Only.

Instance Name Select Default.Do not specify an instance name.

Dialog box does not appear.

Setup Type Select Custom. Dialog box does not appear.

Select Components Select all components. Select all components.

Service Accounts Select Use the same account for each service.Auto start SQL Server Service.Select Use the Local System account.


Authentication mode Select the authentication mode.We recommend to use Windowsauthentication mode.

.NoteFor a Java system,Mixed mode isrequired. SAPinst automaticallychanges the authenticationmode into Mixed mode wheninstalling a Java system.


Collation settings Select SQL Collations.From the drop-down list select Binaryorder, for use with the 850 (Multilingual)Character Set.


Network Libraries Leave selection unchanged andchoose Next.


Start Copying Files Choose Next. Choose Next.

Choose Licensing Mode Select the mode you require. Dialog box does not appear.

4. When you have finished the installation, install the latest Service Pack, and the latest hotfix, if available, forSQL Server 2000.For more information on the latest Service Pack, see SAP Note 62988.For more information on the latest hotfix, see SAP Note 608651.

5. If you have installed the server software, install the corrected MS SQL Server collation [page 51]. For moreinformation on the SQL Server collation, see SAP Note 600027.

48 PUBLIC 09/11/2006

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



4 Installation


4.1.2.2 Installing the SQL Server 2000 Database Software on64-Bit Manually

On a 64-bit system, you cannot run the SQL Server 2000 graphical user interface (GUI) tools, with the followingexceptions:

n Client Network Utility (supported by the 64-bit Windows operating system)n Server Network Utilityn Service Managern SQL Server 2000 Licensing (in Control Panel)n Setup.exe (supported by Windows Installer)

If you want to use the other SQL Server 2000 GUI tools with the 64-bit version of SQL Server 2000, you haveto install them with the 32-bit version of SQL Server 2000 on a 32-bit computer and use them to remotelymanage the 64-bit server.

.Note

n You can install the 32-bit graphical user interface management tools from the 32-bit directory of theMS SQL Server 2000 RDBMS SP4 DVD.

n Graphical interface management tools which were installed with the 32-bit version of SQL Server 2000are not supported in the 64-bit version. For more information refer to the readme.txt file in theIA64\SQL2000 subdirectory.

Procedure


.Caution

Make sure that you have not applied NTFS compression to the disk where you install the MS SQLServer software.

2. Insert the MS SQL Server 2000 RDBMS SP4 DVD into your DVD drive.3. To start the installation, run setup.exe located in the directory IA64\SQL2000.4. Enter the required information as specified in the following table:

Input for the MS SQL Server Installation on 64-Bit Systems

Window Input

Registration Information Enter your name and the product key specified in the file SAPCDKEY.txtin the root directory of the RDBMS DVD.

Software License Agreement Choose Yes.

09/11/2006 PUBLIC 49

4 Installation


Window Input

Feature Selection n Server Software:Select all components.

n Client Software:Select SQL Server Management Tools.

.NoteTo select a component, left-click on it and choose Entire featurewill be installed on local hard drive.To deselect a component, left-click on it, and choose Entirefeature will be unavailable.

Instance Name Select the instance type you want to install.

Service Account Select Use the same account for each service. Auto start SQL Server Service.Select Use the Local System account.

Authentication Mode n Select the authentication mode.We recommend to useWindows authentication mode.

.NoteFor a Java system, Mixed mode is required. SAPinstautomatically changes the authentication mode intoMixedmode when installing a Java system.

n Enter and confirm the password for the sa login.

.NoteIf you have chosenWindows authentication mode, the sa login iscreated, but cannot be used.

Security Enhancement:Cross Database Ownership Chaining

Leave selection unchanged and choose Next.

Collation Settings Select SQL Collations.From the drop-down list select Binary order, for use with the 850 (Multilingual)Character Set.

Licensing Mode Select the licensing mode and choose Next.

Ready to Install Select Install.

5. When you have finished the installation, install the latest Service Pack , and the latest hotfix, if available, forSQL Server 2000.For more information on the latest Service Pack, see SAP Note 62988.For more information on the latest hotfix, see SAP Note 608651.

6. If you have installed the server software, install the corrected MS SQL Server collation [page 51]. For moreinformation on the SQL Server collation, see SAP Note 600027.

50 PUBLIC 09/11/2006

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



4 Installation


4.1.2.3 Installing the Corrected MS SQL Server Collation for MSSQL Server 2000

When you install the MS SQL Server 2000 database for an SAP system, in the field Collation Settings you have toselect Binary order, for use with the 850 (Multilingual) Character Set.This means that all new databases and table columns will be created with this collation setting.

.Note

To view the default collation of MS SQL Server use the query:select serverproperty('collation')

This query returns the default collation of the overall server. When you have selected Binary order, for usewith the 850 (Multilingual) Character Set, it returns: SQL_Latin1_General_CP850_BIN

Unfortunately this collation setting does not sort Unicode data as it is required by an SAP system. To solvethis problem, Microsoft provides a corrected collation for SQL Server.For more information about installing the collation, see SAP Note 600027.

Prerequisites

n You have installed the MS SQL Server 2000 database software. In the field Collation Settings, you selectedBinary order for use with the 850 (Multilingual) Character Set.

n You have installed the latest service pack and hotfix, if available. For more information, refer to SAPNotes 62988 and 608651.

.Note

Besides applying the latest service and hotfix, if available, you do not have to make any changes on theclient side (SAP application servers).

n To obtain a correct collation order with MS SQL Server, you have to use the new collation for all newinstallations of a Unicode or non-Unicode SAP system with the MS SQL Server database. New versions ofthe SAPinst installation tool check for the new collation.

n A new SAP system using the new collation and an existing SAP system that is using the old collation cannotrun as two databases in the same MS SQL Server instance. If you want to install a new system on a databaseserver with an existing system you have to apply the new collation with INSTCOLL.EXE.

1. Download the INSTCOLL.EXE file for your platform, which is attached as zip file to SAP Note 600027,and extract it to your server.

2. Open a command prompt and change to the directory where you extracted the INSTCOLL.EXE file.3. Enter the following:n For a default instance enter: INSTCOLL.EXE

n For a named instance enter: INSTCOLL.EXE -S<server>\<instance> (without any spaces after --S)The executable starts the SQL Server Service if it is not running already and runs several checks.When you are asked to apply the new collation to all databases confirm with Y (Yes).When the conversion has finished it restarts the SQL Server Service.

4. To verify whether the MS SQL Server is properly configured, run:

09/11/2006 PUBLIC 51


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



4 Installation


select serverproperty('collation')

.Caution

You have to run INSTCOLL.EXE only once to apply the new collation. To convert a single SAP databaseto the new collation, see SAP Note 600027.

ResultYou can now continue with the standard SAP system installation and install any SAP instance on this server.

4.1.2.4 Installing the SQL Server 2005 Database Server SoftwareManually

This section describes how to install the SQL Server 2005 database server software on 32-bit or 64-bit systemsmanually. If you use an MSCS environment, you have to use the manual procedure. For a standard SAPsystem, you can also use the SQL4SAP script [page 45] to install SQL Server 2005.The SQL Server 2005 database server software must be installed on the database host

.Note

If you want to install the database client software manually, see Installing the SQL Server 2005 Native Client(SNAC) Software [page 55].

Prerequisites

n When installing SQL Server 2005, make sure that you have enough free disk space available on the systemdrive for:l .Net Framework

For 64-bit also the 64-bit .Net Framework in addition to the 32-bit .Net Framework is installed.l SQL Server Client Toolsl SQL Server instancel Temporary space during the installation

The required disk space depends on the type of SQL Server components already installed or to beinstalled. It also depends on the system. For a 32-bit system you need up to 2 GB free disk space on thesystem drive, for a 64-bit system you might require more space.

n Make sure that theMicrosoft Distributed Transaction Coordinator (MSDTC) service is running before you startthe installation.

Procedure

1. Log on to the host as a local administrator2. Insert the SQL Server 2005 RDBMS DVD in your DVD drive or mount it locally.3. Change to the platform-specific folder and choose Enterprise Edition ® Servers.4. Start the installation program with setup.exe.5. Enter the required information as specified in the table below

52 PUBLIC 09/11/2006


4 Installation


.Note

The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL

server\90\Setup Bootstrap\LOG. You find the summary of the setup log in summary.txt in thesame directory.

Window Server Input

End User License Agreement Accept the licensing terms and conditions and chooseNext.

Installing Prerequisites Choose Install and, if required, Next.

Welcome to the Microsoft SQL Server Installation Wizard Choose Next.

System Configuration Check a) Check your system configuration and, if required,set up the required configuration.

.Noten For more information about the required

system configuration for a softwarecomponent, chooseMessages.

n IIS is not required for an SAP system.Therefore, you can ignore the warningabout the IIS Feature Requirement.

n If there is a warning in COM Plus CatalogRequirement, correct the configuration beforeyou proceed with the installation. Makesure that theMicrosoft Distributed TransactionCoordinator (MSDTC) service is running.

b) Choose Next.

Registration Information a) Enter your personal information, and the productkey

b) Choose Next.

Components to Install a) Select:n SQL Server Database Servicesn Workstation components, Books Online and development tools.

b) Choose Advanced

Feature Selection a) Expand Database Services and deselect Replication.

b) Expand Client Components and if available, deselectBusiness Intelligence Development Studio.

.NoteWe recommend that you deselect these featuresas they are not required for an SAP system.

c) Choose Next.

09/11/2006 PUBLIC 53

4 Installation


Window Server Input

Instance Name Select the instance you want to install and choose Next.

.NoteSAP recommends to install a Default instance.

Service Account a) Select one of the following options:n Use the built-in System account for each service and choose

Local System or Network Service.n Use a domain user account, and enter the user name

and password.

b) Under Start services at the end of setupmake sure that SQLServer and SQL Server Agent are selected.

.NoteIf you use a named instance, you must alsoselect SQL Browser.

c) Choose Next.

Authentication Mode a) SelectMixed Mode (Windows Authentication and SQL ServerAuthentication).This mode is required for a Java or ABAP+Java system.If you choose this mode, you have to set the passwordfor the sa login.

.NoteSAPinst automatically changes theauthentication mode into Mixed Modewhen installing a Java system.The password for the sa login must complywith the Windows password policy.

b) Choose Next.

Collation Settings a) Select SQL collations (used for compatibility with previousversions of SQL Server).

b) From the drop-down list select Binary order based on codepoint comparison, for use with the 850 (Multilingual) CharacterSet.

c) Choose Next.

Error and Usage Report Settings Leave the selection unchanged and choose Next.

Ready to Install Choose Install.

Setup Progress.NoteTo see the log files for the SQL Server components,choose Setup finished.

When the setup process has finished, choose Next.

Completing Microsoft SQL Server 2005 Setup Choose Finish.

54 PUBLIC 09/11/2006

4 Installation

4.2 Preparing your System for an Java Add-In Installation

6. When you have finished the installation, enable the Named Pipes and TCP/IP protocol in the SQL ServerConfiguration Manager as follows:n Choose Start ® All Programs ® Microsoft SQL Server 2005 ® Configuration Tools ® SQL Server Configuration

Manager.n Expand SQL Server 2005 Network Configuration and select one of the following:n For a default instance, select Protocols for MSSQLServer

n For a named instance, select Protocols for <SAPSID>n In the right-hand pane, under Protocol Name, right-click Named Pipes and TCP/IP, and select Enable.

7. Restart SQL Server.

4.1.2.5 Installing the SQL Server 2005 Native Client SoftwareManually

This chapter describes how to install the SQL Server 2005 Native Client (SNAC) software on 32-bit or 64-bit systems.The SQL Server 2005 client software must be installed on all hosts without the database. It enables the

communication between a host and the database.

Procedure

1. Log on as local administrator to the host where you want to install an application server.2. Insert the SQL Server 2005 RDBMS DVD in your DVD drive or mount it locally.3. Change to the platform-specific folder and choose sqlncli.msi

.Note

You also find the sqlncli.msi file on the Microsoft SQL Server CD in the Setup directory.

4. Follow the instructions in the SQL Server installation setup screens.

4.2 Preparing your System for an Java Add-In Installation

The following procedure is only required, if you want to perform a Java Add-In installation for an alreadyexisting:

n SAP Solution Manager 4.0 SR1 ABAP system.n ABAP system that has been upgraded to SAP Solution Manager 4.0 SR1.

Procedure

1. In your default profile \usr\sap\<SAPSID>\SYS\profile\default.pfl check the parameterdbs/mss/schema.n If it is set to <sapsid> (lowercase letters), no further action is required.n If it does not exist or is set to dbo, convert the schema as described in SAP Note 683447.

09/11/2006 PUBLIC 55


4 Installation

4.3 Installing an SAP System Using SAPinst


.Note

If you use Microsoft Cluster Service, bring your SAP resource offline.Open a command prompt and change to the directory of the Installation Master DVD:IM_WINDOWS_<platform>.Start SAPinst manually with the command:sapinst SAPINST_USE_HOSTNAME=<virtual_hostname_of_SAP_system> .When the conversion is finished, bring the SAP resource SAP <SAPSID> online again.

End of: HA (MSCS)

2. MS SQL Server 2000 only: Check if you use SQL Server collation SQL_Latin1_General_CP850_BIN2:a) Start the SQL Server Enterprise Manager.b) Right-click on your SQL Server and choose Properties.

In the General tab under Server collation you see the collation installed.n If you use SQL_Latin1_General_CP850_BIN2 no further action is required.n If you use collation SQL_Latin1_General_CP850_BIN, convert it to SQL_Latin1_Gen-

eral_CP850_BIN2 as described in Installing the Corrected MS SQL Server Collation for SQL Server 2000 [page 51].


The following sections provide the steps that you have to perform to install the various instances of an SAPsystem, or a standalone engine:

n Running SAPinst on Windows [page 56]n Installing a Java Add-In for an Already Existing Solution Manager ABAP System with SAPinst [page 62]n Using SAPinst GUI [page 64]n Interrupted Installation with SAPinst [page 65]n Performing a Remote Installation with SAPinst (Optional) [page 66]n Starting SAPinst GUI Separately (Optional) [page 67].

4.3.1 Running SAPinst on Windows

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

same host. If required, you can instead perform a remote installation with SAPinst [page 66], where SAPinst GUI isrunning on a separate host from SAPinst and the GUI server.Note the following information about SAPinst:

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

56 PUBLIC 09/11/2006

4 Installation


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

.Recommendation

We recommend that you keep all installation directories until the system is completely and correctlyinstalled.

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

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

.Caution

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

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

Prerequisites

n You are logged on as a user with the required rights and privileges to install the SAPinst tool and the SAPsystem. For more information, see Granting User Rights for the Installation [page 34].

n You need at least 50 MB of free space in the installation directory for each ABAP installation service, and atleast 130 MB of free space in the installation directory for each Java installation service. In addition, youneed 60-200 MB free space for the SAPinst executables.

n If you are installing a second or subsequent SAP system into an existing database, make sure that thedatabase is up and running before starting the installation. For more information, see Installation of MultipleComponents in One Database [page 97].

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

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

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

09/11/2006 PUBLIC 57

4 Installation


.Example

DEFAULT.PFL

Before:...rdisp/msserv = sapmsSID

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

rdisp/msserv_internal = <free port number>

...

3. Edit the instance profile of the central services instance:l Set rdisp/msserv to 0.l Set rdisp/msserv_internal to the port number assigned to rdisp/msserv.

.Example

Instance profile of the central services instance:Before:...rdisp/msserv = 4711

...After:...rdisp/msserv = 0

rdisp/msserv_internal = 4711

...

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

Procedure

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

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

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

58 PUBLIC 09/11/2006

4 Installation


.Note

n During the installation, the default ports 21200 and 21212 are used for communication betweenSAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to communicate with the GUI server.The GUI server uses port 21212 to communicate with SAPinst GUI. You get an error message if oneof these ports is already in use by another service.In this case, open a command prompt and change to the required directory as follows:<DVD drive>:\IM_WINDOWS_<platform>.Enter the following command in a single line:sapinst.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>

n For a list of all available SAPinst properties, enter the following command:sapinst -p.

3. In theWelcome screen, choose one of the following installation services:n SAP Systemsn Additional Software Life-Cycle TasksThe following tables provide more information about these installation services:n SAP Systems

You use this service to install a SAP system with usage types or software units by choosing SAP SolutionManager 4.0 SR1 ® SAP Systems ® <Database> ® <System Variant> ® Based on <technical stack>.You can install the following system variants:l Central Systeml Distributed System

l


High-Availability SystemEnd of: HA (MSCS)

The following tables provide an overview of the installation services available for these system variants:

.Note

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

l If you want to use active directory [page 101], you must run the installation service Active DirectoryConfiguration before you start the installation of the SAP system (see table Additional SoftwareLife-Cycle Tasks below).

l If you want to use global accounts, which are configured on separate hosts, you must run theinstallation service Operating System Users and Groups before you start the installation of the SAPsystem (see table Additional Software Life-Cycle Tasks below).

l If required, install a dialog instance for a central or distributed system by choosing theinstallation service <SAP System> ® Additional Software Life-Cycle Tasks ® Application Server ®Dialog Instance.

09/11/2006 PUBLIC 59

4 Installation


Installation Services for a Central System

Installation Service Remarks

Central System Installation Installs a complete SAP system including the followinginstances on one host:l Central services instance (SCS)l Database instancel Central instance

.NoteYou require at least usage type AS Java or AS ABAP. Youcan choose the usage types or software units on the nextscreen.

Installation Services for a Distributed System

Installation Services Remarks

Central Services Instance (SCS) Mandatory step in installing a distributed SAP system withusage types or software units based on AS ABAP and AS Java.Installs a central services instance (SCS) and prepares the SAPglobal host.

Database Instance Mandatory step in installing a distributed SAP system.Installs a database instance.You must have finished the Central Services Instance (SCS)installation, before you can choose this installation service.

Central Instance Mandatory step in installing a distributed SAP system on severalhosts.Installs a central instance and enables additional usage typesor software units.You must have finished the database instance installation.

Installation Services for a High Availability System


Central Services Instancefor ABAP (ASCS)

Installs a central services instance for ABAP (ASCS) and prepares the SAP globalhost.

Central Services Instance(SCS)

Installs a central services instance (SCS).

First MSCS Node This step performs the following on the first Microsoft Cluster Service (MSCS)node:l Creates the SAP cluster groupl Adds the ASCS and SCS instances to the SAP cluster group.

Database Instance Installs a database instance.

Additional MSCS Node This step configures an additional Microsoft Cluster Service (MSCS) node to runthe SAP cluster group.You must have completed the configuration of the first MSCS node and thedatabase instance installation.

60 PUBLIC 09/11/2006

4 Installation



Enqueue ReplicationServer

Installs an enqueue replication server, which contains a replica of the lock table(replication server).

Central Instance Installs a central instance and enables additional usage types or software units.

Dialog Instance Installs a dialog instance.

.NoteYou require at least one dialog instance in a high-availability systemconfigured with MSCS.

n Additional Software Life-Cycle TasksYou use this service to perform the following tasks or to install the following components:


Additional Preparation Tasks With these preparation tasks you can:l Configure Active Directory [page 101]

.CautionPerform this task before you start the installation of your SAPsystem.

l Use global accounts that are configured on a separate host

.CautionPerform this task before you start the installation of your SAPsystem.

l Check your hardware and software requirements before you start theinstallationOtherwise, SAPinst automatically checks the hardware and softwarerequirements during the installation with the Prerequisite Checker. If anychanges are necessary to the SAP system or operating system settings,SAPinst automatically prompts you. For more information, see Runningthe Prerequisites Checker in Standalone Mode [page 24].

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

.NoteIf you want to use LDAP, choose Application Server ® LDAP Support, afteryou have installed an application server. For more information, seePreparing the Active Directory [page 101].

Java Add-In for ABAP Choose this service to install usage types based on AS Java to an alreadyinstalled SAP Solution Manager ABAP system.For more information, see Installing a Java Add-In for an Already Existing SAPSolution Manager ABAP System with SAPinst [page 62] .

09/11/2006 PUBLIC 61

4 Installation



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

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

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

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

.Note

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

After you have entered all required input information, SAPinst starts the installation and displays theprogress of the installation. If the installation was successful, the screen Finished installation successfully isdisplayed.

6. We recommend you to delete all files in the directory %userprofile%\.sdtgui\.

More InformationTroubleshooting with SAPinst [page 112].

4.3.2 Installing a Java Add-In for an Already Existing SolutionManager ABAP System with SAPinst (Optional)

This section describes how to install a Java Add-In for an existing Solution Manager ABAP system.

PrerequisitesYour ABAP systemmust be on the support package level of SAP Solution Manager 4.0 SR1 ABAP.


If you use Microsoft Cluster Service (MSCS), stop the ASCS instance in the Cluster Administrator (serviceSAP <SID> <instance_number> Service ) before you run the installation service First MSCS Node in SAPinst.End of: HA (MSCS)

Procedure

1. Start SAPinst [page 56].2. On theWelcome Screen, chooseSAP Solution Manager 4.0 SR1 ® Additional Software Life-Cycle Tasks ® Java Add-In for

ABAP ® <database> ® <system variant>.3. Choose the corresponding installation services from the tree structure exactly in the order they appear for

each system variant, as shown in the following tables:

62 PUBLIC 09/11/2006

4 Installation


Installation Services for a Java Add-In for ABAP ‒ Central or Distributed System


Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) and adds usage types orsoftware units based on AS Java

Database Instance Java Add-In Installs the Java schema in the database of your ABAP system

Central Instance Java Add-In Adds usage types or software units based on AS Java

.CautionWhen performing an upgrade installation, before you usethis service, uninstall the old ABAP dialog instance.

Installation Services for a Java Add-In for ABAP ‒ High-Availability System


Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) and adds usage types orsoftware units based on AS Java

.CautionYou must install it on the same shared disk as the ASCSinstance.

First MSCS Node Configures the SCS instance for the first MSCS node

.NoteMake sure that you choose instance type ASCS and SCSinstance (ABAP and Java).

Database Instance Java Add-In Installs the Java schema in the database of your ABAP system

.NoteIf your database instance is to be installed in the sameMSCScluster as the SCS and ASCS instance, you must performthis step on the first node of this MSCS cluster.If your database instance is to be installed in a differentMSCS cluster from the ASCS and SCS instance, you performthis step on another MSCS cluster.

Additional MSCS Node.CautionChoose this step only if you use Microsoft Cluster Services(MSCS).

This step configures the SCS instance for the additional MSCSnode.

.NoteMake sure that you choose instance type ASCS and SCSinstance (ABAP and Java).

09/11/2006 PUBLIC 63

4 Installation



Enqueue Replication Server Installs an enqueue replication server, which contains a replica ofthe lock table (replication table).You must perform this step on all MSCS nodes where the Javacentral services (SCS) instance or ABAP central services (ASCS)instance is installed and clustered.

Central Instance Java Add-In Adds usage types or software units based on AS Java

Dialog Instance Installs a dialog instance in a high-availability system

.CautionWhen performing an upgrade installation, before you usethis service, uninstall the old ABAP dialog instance.

4. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

.Note

SAPinst prompts you for the production client of your ABAP system. This is where you installthe Java Add-In.

After you have entered all required input parameters, SAPinst starts the installation and displays theprogress of the installation.

4.3.3 Using SAPinst GUI

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

SAPinst GUI Functions

Button / Function Key / Menu Entries Description

F1 Displays detailed information about each input parameter.

Exit Cancels the installation with the following options:n Stop

Stops the installation without further changing theinstallation files. You can restart SAPinst to continue theinstallation later from this point.

n ContinueContinues the installation.

64 PUBLIC 09/11/2006

4 Installation


Button / Function Key / Menu Entries Description

Log off Stops the SAPinst GUI, but SAPinst and the GUI servercontinue running.

.NoteIf for some reason you need to log off during theinstallation from the host where you control theinstallation with SAPinst GUI, the installation continueswhile you are logged off. You can later reconnect tothe same SAPinst installation from the same or anotherhost. For more information, see Starting SAPinst GUISeparately [page 67].

Retry Performs the installation step again (if an error has occurred).

Stop Stops the installation without further changing theinstallation files. You can continue the installation later fromthis point.

Continue Continues with the option you have chosen before.

4.3.4 Interrupted Installation with SAPinst

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

n An error occurred during the dialog or processing phase:SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses and adialog box appears. The dialog box contains a short description about the choices listed in the table below aswell as a path to a log file that contains detailed information about the error.

n You interrupted the installation by choosing Exit in the SAPinst menu.

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeating any ofthe previous steps.This is possible because SAPinst records the installation progress in the keydb.xmlfile.We recommend that you view the entries in the log files, try to solve the problemand then choose Retry.If the same or a different error occurs again, SAPinst displays the same dialog boxagain.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and theGUI server.SAPinst records the installation progress in the keydb.xml file. Therefore, you cancontinue the installation from the point of failure without repeating any of theprevious steps. See the procedure below.

Continue SAPinst continues the installation from the current point.

09/11/2006 PUBLIC 65

4 Installation


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

1. Log on to your remote host as a user who is a member of the local administrators group.2. Insert the Installation Master DVD in your DVD drive.3. Enter the following commands at the Windows command prompt:

cd <DVD drive>:\IM_WINDOWS<platform>

sapinst.exe

4. From the tree structure in theWelcome screen, select the installation service that you want to continueand choose Next.

.Note

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

TheWhat do you want to do? screen appears.5. In theWhat do you want to do? screen, decide between the following alternatives and confirm with OK.

Alternative Behavior

Run a new Installation SAPinst does not continue the interrupted installation. Instead, it moves thecontent of the old installation directory and all installation-specific files to thebackup directory. Afterwards, you can no longer continue the old installation.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds> (for example,log_01_Oct_2003_13_47_56).

Continue old installation SAPinst continues the interrupted installation from the point of failure.

4.3.5 Performing a Remote Installation with SAPinst (Optional)

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the GUI serverrun on the remote host, and SAPinst GUI runs on the local host. The local host is the host from which youcontrol the installation with SAPinst GUI.

Prerequisites

n The remote host meets the prerequisites before starting SAPinst as described in Running SAPinst on Windows[page 56]

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

Procedure

1. Log on to your remote host as a user who is a member of the local administrators group.

66 PUBLIC 09/11/2006

4 Installation


2. Insert the Installation Master DVD in the DVD drive on your remote host.3. Enter the following commands:

cd <DVD drive>:\IM_WINDOWS_<platform>

sapinst.exe -nogui

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

<port_number> to continue with the installation

4. Start SAPinst GUI on your local host, as described in Starting SAPinst GUI Separately [page 67].

4.3.6 Starting SAPinst GUI Separately (Optional)

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI separately inthe following cases:

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

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

PrerequisitesYou have installed the Java Development Kit [page 40] on the host on which you want to start SAPinst withoutSAPinst GUI.

Starting SAPinst GUI on a Windows Platform

1. Log on as a member of the local administrators group.2. Insert the SAP Installation Master DVD into your DVD drive.3. To change to the relevant directory enter the following command:

cd <DVD drive>:\IM_WINDOWS<platform>

4. Start SAPinst GUI in one of the following ways:n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following command:

startinstgui.bat

SAPinst GUI uses the local host as default.n If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation), enter the

following command:startinstgui.bat -host <host_name>

<host_name> is the host name of the installation host.

09/11/2006 PUBLIC 67

4 Installation


.Note

l If you enter the command without additional parameters, SAPinst GUI uses the local host asdefault. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. As SAPinstand the GUI server are running on another host, SAPinst GUI cannot connect and the SAPInstallation GUI Connection dialog appears.In this case, enter the name of the host on which SAPinst is running and choose Log on.The first dialog of the installation appears and you can perform the remote installation fromyour local host.

l For a list of options to start SAPinst GUI, change to the same directory as your SAPinstexecutable and enter the command startinstgui.bat -h.

Starting SAPinst GUI on a UNIX Platform

1. Log on as user root.

.Caution

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

2. Mount your installation DVD.

.Note

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

3. To change to the mount directory enter the following command:cd <Installation_Master_DVD>/IM_<OS>

4. Start the SAPinst GUI in one of the following ways:n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following command

without additional parameters:./startInstGui.sh

SAPinst GUI uses as default the local host.n If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation), enter the

following command with additional parameters:./startInstGui.sh -host <host_name>

<host_name> is the host name of the installation host

68 PUBLIC 09/11/2006

4 Installation


.Note

l If you enter the command without additional parameters, SAPinst GUI uses the local host asdefault. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. As SAPinst andGUI server are running on another host, SAPinst GUI cannot connect and the SAP InstallationGUI Connection dialog appears.In this case, enter the name of host on which SAPinst is running and choose Log on.The first dialog of the installation appears and you can perform the remote installation fromyour local host.

l For a list of options to start SAPinst GUI, change to the same directory as your SAPinstexecutable and enter the command ./startInstGui.sh -h.

09/11/2006 PUBLIC 69


5 Post-Installation

5 Post-Installation

This section provides information on how to perform the post-installation steps of your SAP system.You perform the following post-installation steps:

1. You start and stop the SAP system [page 71].2. You log on to the SAP system [page 72].3. You install the SAP License [page 74].4. You install the SAP Online Documentation [page 74].5. You configure the remote connection to SAP support [page 75].6. You perform initial ABAP configuration [page 75].7. You check the Java manuals [page 76] for information that is relevant for running your Java system.8. You apply the latest kernel and Support Packages [page 78].9. You perform a full installation backup [page 79].10. You configure Single Sign-On with Microsoft Lan Manager SSP [page 80].11. You configure Single Sign-On with Microsoft Kerberos SSP [page 84].12. You perform post-installation steps for Adobe Document Services [page 89].13. You ensure user security [page 91].14. You configure SAP Solution Manager [page 93].

5.1 Starting and Stopping the SAP System

You use this procedure to check that you can start and stop the SAP system after the installation with theSAP Microsoft Management Console (SAP MMC).With a newly installed MMC you can start or stop installed SAP instances locally on the host that you are

logged on to. If the MMC is configured for central system administration, you can start or stop the entiresystem from a single host.

.Note

For more information, see:help.sap.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Solution Life Cycle

Management by Key Capability ® Solution Monitoring ® Monitoring in the CCMS ® Microsoft Management Console:Windows

Prerequisites

n You have logged on to the SAP system host as user <sapsid>adm.n You have checked the settings for VM parameters as described in SAP Note 723909.

09/11/2006 PUBLIC 71


5 Post-Installation

5.2 Logging On to the SAP System

Procedure

1. Start the SAP MMC on the SAP system host by choosing Start ® Programs ® SAP Management Console.2. Right-click the SAP system node and choose Start or Stop.

All instances listed under the system node, will start or stop in the correct order.3. If the SAP system is installed on multiple hosts (distributed system), you have the following options

to start or stop your system:n You start or stop the SAP instances using the MMC on each host.n You add the remote instances to theMMC configuration to start or stop all instances from a singleMMC.

To do so, do one of the following:l You configure the MMCmanually. For more information, see Changing the Configuration of the MMC in

the SAP MMC documentation.l You use the automatic LDAP registration. For more information, see Configuring MMC for Active

Directory Services in the SAP MMC documentation.

.Note

You can also start and stop a UNIX system with the MMC.


You need to check that you can log on to the SAP system using the following standard users.

ABAP Users

User User Name Client

SAP* 000, 001, 066SAP system user

DDIC 000, 001

ABAP+Java User

User User Name Storage: ABAP System

Administrator J2EE_ADMIN (default) or the name you gave this user during theinstallation process.

Prerequisites

n You have already started the SAP system.n You have already installed a front end.

Logging On to the ABAP System

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

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

72 PUBLIC 09/11/2006

5 Post-Installation


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

.Note

You can also enter the command guilogon in the SAP GUI installation directory to start SAPGUI for Java.

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

For more information about creating new logon entries, press F1 .3. When you have created the entry, log on as user SAP* or DDIC.

Logging On to the J2EE EngineYou access the J2EE Engine with a URL using a Web browser from your client machines. To log on to theJ2EE engine for the first time, proceed as follows:

1. Establish the default J2EE Engine URL.2. Log on to the J2EE Engine.

Establishing the J2EE Engine URL

The default URL consists of the installation host name and the port on which the J2EE Engine is listening.You can use the HTTP or HTTPS protocol; HTTPS is relevant if you are using Secure Sockets Layer (SSL)communication. To correctly establish the URL, you first have to calculate the port number as follows:

Protocol Formula

HTTP The HTTP port number is based on the number of the J2EE instance on which you haveinstalled the J2EE Engine, and is calculated according to the following formula:HTTP Port = 50000 + (100*<instance number>)

.ExampleIf the J2EE Engine is installed on J2EE instance number 01, the port number is:J2EE Engine HTTP Port = 50000 + (100 * 1) = 50100

HTTPS The HTTPS port number is calculated according to the following formula:HTTPS Port = 50000 + (100*<instance number>) + 1

.ExampleIf the J2EE Engine is installed on J2EE instance number 01:J2EE Engine HTTPS Port = 50000 + (100 * 1) + 1 = 50101

The default J2EE Engine URL looks as follows, depending on the protocol that you are using:<protocol>://<fully qualified j2ee engine host name>:<protocol_port_number>

.Example

If you installed the J2EE Engine on host saphost06 and the instance number of your J2EE Engine is 15,enter the following URL: http://saphost06:51500

09/11/2006 PUBLIC 73

5 Post-Installation

5.3 Installing the SAP License

Logging on to the J2EE Engine

1. Open your Web browser, enter the J2EE Engine URL as described above and choose Enter.The start page of the J2EE Engine appears in the Web browser.

2. Log on by choosing EXAMPLES in the upper right corner of the Web page.3. In theWelcome screen, enter the following information:n User ID: <J2EE Administrator name>

n Password: <J2EE Administrator password>

.Note

To deactivate the J2EE Engine, proceed as follows:

1. Call transaction RZ11.2. In the instance profile of every installed SAP instance, set parameter rdisp/j2ee_start from 1 to 0.

5.3 Installing the SAP License

You must install a permanent SAP license. When you install your SAP system, a temporary license isautomatically installed. This temporary license allows you to use the system for only four weeks fromthe date of installation.

.Caution

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

system.

ProcedureFor information about the installation procedure for the SAP license, see:

help.sap.com/nw2004s ® SAP NetWeaver ® SAP NetWeaver Library ® Technology Consultant's Guide ®Cross-NetWeaver Configurations ® SAP License Key

More InformationFor more information about SAP license keys, see SAP Service Marketplace at service.sap.com/licensekey.

5.4 Installing the SAP Online Documentation

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

74 PUBLIC 09/11/2006

5 Post-Installation

5.5 Configuring Remote Connection to SAP Support

ProcessInstall the SAP online documentation in your SAP system as described in the README.TXT file contained in theroot directory of the online documentation DVD, delivered as part of the installation package.

5.5 Configuring Remote Connection to SAP Support

SAP offers its customers access to support and a number of remote services such as the EarlyWatch Serviceor the GoingLive Service. Therefore, you have to set up a remote network connection to SAP. For moreinformation, see SAP Service Marketplace at service.sap.com/remoteconnection.

5.6 Performing Initial ABAP Configuration

Here you find information about how to perform initial ABAP system configuration.

Procedure

1. Go to the following place in the SAP Library:help.sap.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability

2. Check the documentation on the following configuration steps:n Configuring the transport management system

For more information, see Solution Life Cycle Management by Key Capability ® Software Life Cycle Management ®Software Logistics ® Change and Transport System.

n Performing basic operationsFor more information, see the relevant section in Solution Life Cycle Management by Key Capability ® SystemManagement:

Operation Section in SAP Documentation

Set up operation modes ‒transaction RZ04

Configuration ® Operation Modes

Set up logon groups ‒transaction SMLG

Configuration ® Logon Load Distribution ® SAP Logon

Set up administrators Background Processing ® Authorizations for Background Processing

Schedule background jobs Background Processing

Install a printer SAP Printing Guide

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

n Configuring work processesFor more information about instance profiles, which is where work processes are defined, see SolutionLife Cycle Management by Key Capability ® System Management ® Configuration ® Profiles ® Profile Files ®Instance Profiles.

09/11/2006 PUBLIC 75

5 Post-Installation

5.7 Checking the SAP Java Documentation

.Note

SAPinst installs SAP systems with a minimum number of work processes. This is only an initialconfiguration to get you started after the installation. It is not detailed enough for a productionsystem because the optimal number of each type of work process depends on the system resourcesand on the number of users working in each SAP system application. For a detailed configurationcontact SAP Technical Consulting.

n Installing languages and performing language transportl Installing languages using transaction I18N:

u If you want to use English only, you must activate the default language settings once.

u If you want to use languages other than English, you must install them and activate the languagesettings.

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

l Performing language transport using transation SMLT:For more information on performing the language transport using transaction SMLT. see SolutionLife Cycle Management by Key Capability ® Software Life Cycle Management ® Software Logistics ® Change andTransport System ® Language Transport..

n Activating and configuring the integrated Internet Transaction Server (ITS)l For more information on activating and configuring the ITS, which is installed automatically with

the SAP kernel, see Application Platform by Key Capability ® ABAP Technology ® UI Technology ® ITS /SAP@Web Studio (BC-FES-ITS).

l For more information about ITS, see SAP Note 742048, where you can find the necessaryinformation if you do not want to use the ITS.

n Maintaining address dataFor more information on maintaining the company address in your SAP system using transaction SU01,see Application Platform by Key Capability ® Business Services ® Business Address Services (BC-SRV-ADR) ®Addresses in User Administration ® Maintenance of Address Data .

.Note

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

n Configuring business applicationsFor more information about how to prepare the SAP system for using business applications, whichincludes customizing the ABAP system and the business components, see Solution Life Cycle Management byKey Capability ® Customizing.


Here you canfind information about the configuration of the J2EE Engine and about SAP Java technology inthe SAP Library.

76 PUBLIC 09/11/2006


5 Post-Installation


Procedure

1. Go to the following place in the documentation:help.sap.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Application Platform byKey Capability ® Java Technology.

2. Check the following documentation for information relevant to running your Java system:

Manual Contents

Architecture Manual This manual describes the architecture of a Java or ABAP+Java system. Itcontains information on:n Java cluster architecture including central services, load balancing, and

high availability.n J2EE Engine system architecturen SAP NetWeaver Java development infrastructure, including SAP

NetWeaver Developer Studio

.NoteThe SAP NetWeaver Developer Studio is the SAP developmentinfrastructure for Java. The Architecture Manual describes theintegration of the SAP NetWeaver Developer Studio into the SAPdevelopment infrastructure.

Administration Manual This manual describes how to administer the SAP system, focusing on the J2EEEngine. It contains information on:n System landscape administrationn Software life-cycle management

.NoteThis part of the manual contains important information about:l Installation informationl System Landscape Directory (SLD)l Software Lifecycle Manager (SLM)l Java Support Package Managerl Administration of SAPNetWeaver JavaDevelopment Infrastructure

(JDI)

n J2EE Engine and J2EE Engine securityn Supportability and performance managementn Administration and configuration of Web Dynpro runtime environmentn Administration of the XML Data Archiving Service (XML DAS)

.CautionMake sure that you check the mandatory post-installation procedureslisted in the Administration Manual under J2EE Engine ® InstallationInformation ® Post-Installation Procedures.

Java Development Manual This manual describes the technologies for developing Java-based businessapplications. It explains how to use the SAP Netweaver Developer Studio, whichis the SAP Java development environment.

Migration Manual This manual contains all the information you need to migrate an applicationcreated in J2EE Engine 6.20.

09/11/2006 PUBLIC 77

5 Post-Installation

5.8 Applying the Latest Kernel and Support Packages

More InformationFor troubleshooting the J2EE Engine, see the J2EE Engine Problem Analysis Guide at:

help.sap.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Solution Life CycleManagement by Key Capability ® SAP NetWeaver Problem Analysis Guide (PAG) ® J2EE Engine Problem Analysis Scenarios

5.8 Applying the Latest Kernel and Support Packages

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

.Caution

You must have applied all ABAP Support Packages, before you run CTC online configuration.

You can use Java Support Package Manager (JSPM) to apply both the latest ABAP+Java or Java kernel andJava support packages.JSPM is a Java standalone tool that you can use with SAP NetWeaver 04s. JSPM uses the Software Deployment

Manager (SDM) to apply support packages and patches and to deploy software components.For more information about JSPM and how to use it, see help.sap.com/nw2004s ® SAP NetWeaver Library ®

SAP NetWeaver by Key Capability ® Solution Life Cycle Management by Key Capability ® Software Life Cycle Management ®Software Maintenance ® Java Support Package Manager

PrerequisitesTo extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you canfind on SAP Service Marketplace at service.sap.com/swdc. You need at least SAPCAR 700 or SAPCAR 640with patch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR files. Formore information, see SAP Note 212876.

Procedure

1. Apply the latest kernel.You must always replace the installed kernel with the latest kernel from SAP Service Marketplace. Inparticular, you must replace the installed kernel if:n You installed the kernel executables locally on every host.n Your central instance host runs on a different operating system than your dialog instance host.For more information about how to download a kernel, see SAP Note 19466.To exchange the ABAP+Java kernel, you can use Java Support Package Manager (JSPM).

2. Apply Support Packages.a) Alternatively, you can download Support Packages from SAP Service Marketplace at:

service.sap.com/patches

b) Apply Support Packages to your SAP system with the help of the Support Package Manager (formerlycalled SAP Patch Manager, transaction SPAM).

c) Apply Support Packages to your SAP system with the help of the Java Support Package Manager (JSPM).For more information about the availability of Support Packages, see the SAP Service Marketplace at:service.sap.com/ocs-schedules

78 PUBLIC 09/11/2006



5 Post-Installation

5.9 Performing a Full Installation Backup

.Note

The SAP Note Assistant lets you load, implement, and organize individual SAP Notes efficiently. It alsorecognizes dependencies between SAP Notes, Support Packages, and modifications.For more information, see the SAP Service Marketplace at:service.sap.com/noteassistant

5.9 Performing a Full Installation Backup

You must perform an offline full backup at the end of the installation.

Prerequisites

n You have completed client maintenance (for example, client copy).n You have stopped:l The SAP systeml SAP-related services (SAP<SAPSID>_<instance> and SAPOSCol)l The database

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

Procedure

1. Save the registry:a) Choose Start ® Programs ® Accessories ® System Tools ® Backup.b) Choose Emergency Repair Disk.

The Emergency Repair Diskette dialog box appears.c) Select Also Backup the Registry to the Repair directory…

When you confirm your entry, the registry is written to diskette.2. Save the system state data:

a) Choose Start ® Programs ® Accessories ® System Tools ® Backup.b) Choose Backup Wizard ® Next.c) Select Only back up the System State data and choose Next.d) InWhere to Store the Backup, select the Backup media type and enter the Backup media or file name.e) Choose Next.f) Check the information displayed and choose Finish to start the backup.

3. Back up all SAP-specific and all database-related directories:a) Choose Start ® Programs ® Accessories ® System Tools ® Backup.b) Choose Backup Wizard ® Next.c) Select Back up selected files, drives, or network data and choose Next.d) InWhat to back up, select the Windows directory and all SAP and database-related directories, including:

\USR\SAP

<HOMEDIR> of <sapsid>adm

\%WINDIR%

e) Choose Next.

09/11/2006 PUBLIC 79

5 Post-Installation

5.10 Single Sign-On with Microsoft Lan Manager SSP

f) InWhere to Store the Backup, select the Backup media type and enter the Backup media or file name for the backup.g) Choose Next.h) Check the information displayed and then choose Finish to start the backup.


Single Sign-On (SSO) is a secure method of logging on to the SAP system that simplifies the logon procedurewithout reducing security. When your system is configured for SSO, an authorized user who has logged on tothe operating system can access the SAP system simply by selecting it in the SAP logon window or clickingthe shortcut. No SAP system user name or password is necessary. SSO makes it significantly easier for youto manage SAP system users.In this section, we describe the option that is the easiest to implement when using a full 32-bit Microsoft

Windows landscape (Windows 9x, Windows ME, Windows NT, Windows 2000 and higher). It is a tailoredversion for SSO with Secure Network Communications (SNC), which uses Microsoft’s domain authentication,LAN Manager Security Service Provider (NTLM SSP).For more information on SNC, see the SNC User's Guide in the SAP Service Marketplace at

service.sap.com/security

Prerequisites

n Typically, SNC requires an external security product that adheres to the Generic Security Service API V2(GSS-API V2) interface and that has been certified by the SAP Software Partner Program. However, in thisscenario, we provide a library that adheres to the GSS-API V2 interface on one side and that communicateswith Microsoft’s NTLM SSP on the other. Since NTLM SSP is already built into Microsoft Windows 32-bitplatforms, you do not need to purchase an additional security product to use SSO.

.Note

The Microsoft NTLM SSP only provides authentication based on a challenge-response authenticationscheme. It does not provide data integrity or data confidentiality protection for the authenticatednetwork connection. All third-party SNC certified security products offer data integrity and privacyprotection. If you want to use these security features, you have to obtain a certified security product.If you use Windows 2000 and higher, we offer an alternative library (gsskrb5.dll) that uses theMicrosoft Kerberos SSP instead of the NTLM SSP for authentication. For more information, see SingleSign-On with Microsoft Kerberos SSP [page 84] .We distribute two different versions of the wrapper library for Microsoft's NTLM SSP. The olderversion is called gssapi32.dll and the newer version is called gssntlm.dll. For more informationabout how to get the gssntlm.dll file, see SAP Note 595341.

n A pure Microsoft Win32 environment is required (Windows 9x, Windows ME, Windows NT, Windows 2000and higher). The Microsoft NTLM SSP is not available for UNIX or any other operating system.

n Bi-directional trust between Windows domains is required if there are separate domains for users, front-endPCs, and SAP application servers.

n The GSS-API V2 library wrapper (gssntlm.dll) must be installed on every application server.n The GSS-API V2 library wrapper must also be installed on every front-end PC.

80 PUBLIC 09/11/2006


5 Post-Installation


n We recommend that you use the 7-bit ASCII character set for all Windows user IDs.n When the code page of the SAP system is different from the code page on the Windows machines, it is not

possible to enter Windows user IDs that contain 8-bit characters into the USRACL table (for example, bycalling transaction SU01). The combination of Windows ANSI (=ISO Latin 1) and the default SAP code page1100 provides the same encoding of 8-bit characters and permits the use of 8-bit characters with gssntlm.dll.

n For more information on how to improve the security of your system with third-party products, see:help.sap.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Security ® Network andTransport Layer Security ® Secure Network Communications

Process Flow

To implement SSO with the Microsoft NTLM SSP you:

1. Prepare the application server for Single Sign-On [page 81] .2. Prepare SAP GUI and SAP logon for Single Sign-On [page 82].3. Map SAP system users to Windows users for Single Sign-On [page 83].

5.10.1 Preparing the Application Server for Single Sign-On

1. Start the service NT LM Security Support Provider:a) Choose Start ® Programs ® Administrative Tools ® Services.b) Select the service NT LM Security Support Provider.c) Choose General.d) Change the startup type from manual to automatic.

2. Copy the gssntlm.dll file to the following directory on your global host:<DRIVE>:\USR\SAP\<SAPSID>\SYS\EXE\<codepage>\<platform>

For more information about how to get the gssntlm.dll file see SAP Note 595341.3. Set the environment variable SNC_LIB to the location of the library.4. In the central instance profile, set the following SNC parameters:

snc/data_protection/max =1

snc/data_protection/min =1

snc/data_protection/use =1

snc/enable =1

snc/gssapi_lib =

(<DRIVE>:\USR\SAP\<SAPSID>\SYS\EXE\<codepage>\<platform>\<gssntlm.dll>)

snc/identity/as =p:<DOMAIN_NAME>\SAPService<SAPSID>

SAPService<SAPSID> is the user who runs the SAP system.<DOMAIN_NAME> is the Windows domain of this user.

.Note

If you use a local account for SAPService<SAPSID>, most operations are successful. However, anyoperations or communications where the SAP system initiates SNC-protected communication toa remote machine, do not work with a local account for SAPService<SAPSID>. Therefore, use adomain account.

09/11/2006 PUBLIC 81


5 Post-Installation


Additional SNC ParametersThe following profile parameters let you continue with password-based access to the SAP system when SNChas been enabled. To log on to the SAP system as an administrator to maintain the mapping of Windowsuser accounts to SAP system user IDs (user and client), you have to use these additional parameters at leastonce after enabling SNC. Once the mapping (at least for the administrator) has been entered, you candisable further password-based logons by removing the respective profile parameters.snc/accept_insecure_cpic =1

snc/accept_insecure_gui =1

snc/accept_insecure_rfc =1

snc/permit_insecure_start =1

snc/permit_insecure_comm =1

5. Stop and restart the SAP system to activate the profile parameters. Changes to SNC profile parametersalways require an application server restart to take effect.

5.10.2 Preparing SAP GUI and SAP Logon for Single Sign-On

You need to perform this procedure as part of Single Sign-On with Microsoft LANManager SSP [page 80].

PrerequisitesYou have completed Preparing the Application Server for Single Sign-On (SSO) [page 81].

Procedure

1. Copy the gssntlm.dll file to the SAP GUI directory.For downloading the gssntlm.dll file, see SAP Note 352295.

2. Set the Windows environment variable SNC_LIB on the PC where your SAP GUI runs.The variable specifies the path to the gssntlm.dll file. You can do this using one of the following methods:n Copy gssntlm.dll to a location of your choice and set the environment variable SNC_LIB to that

location, for example,<DRIVE>:\<SAPGUI_PATH>\gssntlm.dll

a) Right-clickMy Computer and choose Properties ® Advanced ® Environment Variables.b) In User Variables for <user> enter the following:

Variable: SNC_LIBValue: <DRIVE>:\<SAPGUI_PATH>\gssntlm.dll

c) Confirm your entries with OK.d) To activate the new environment variable setting, log off and log on to your Windows system again

as the same user.n Copy gssntlm.dll to a directory of the default search path, for example, %SystemRoot%\system32 and

rename the file to sncgss32.dll This is the default file name that SNC uses when SNC_LIB is neitherentered on the command line nor available in the environment.

3. Set the required logon options to activate SSO:a) In the SAP logon window, right-click an entry and choose Properties.b) Select the Network tab and activate Activate Secure Network Communication.

82 PUBLIC 09/11/2006


5 Post-Installation


c) In the SNC name field, enter:p:<DOMAIN_NAME>\SAPService<SAPSID>

<DOMAIN_NAME> is the Windows domain that the user SAPService<SAPSID> belongs to.

.Example

If the system HWA is running on account SAPServiceHWA of the DEC_NT domain, you enter:p:DEC_NT\SAPServiceHWA

ResultThe SAP Logon window now displays an icon with a small yellow key beside the system entry. This indicatesthat SSO is active.When the SAP administrator has entered the mapping [page 88] between a user's Windows Account and the

user’s SAP system user ID, the next time this SAP system user logs on to the system, the application is openedwithout requiring the user to enter a user name and password.If only one possible match exists between the Windows account and the SAP system user ID, the logon

screen is skipped, unless the profile parameter snc/force_login_screen = 1 is present in the instance profileof the application server.

5.10.3 Mapping SAP System Users to Windows Users for SingleSign-On

You need to perform this procedure as part of Single Sign-On with Microsoft LAN Manager SSP [page 80]. Whenyou have configured your system, you can enable SAP system users to log on with Single Sign-On (SSO) bymapping them to Windows users.

PrerequisitesYou have completed the following procedures:

n Preparing the Application Server for Single Sign-On [page 81]n Preparing SAP GUI and SAP Logon for Single Sign-On [page 82]

Procedure

1. Log on to the SAP system.2. Choose Tools ® Administration ® User Maintenance ® Users or call transaction SU01.

The User Maintenance window appears.3. Enter the name of the SAP system user and choose User names ® Change.4. Choose SNC.5. In SNC name, use uppercase to enter the name of the Windows user that is to be assigned to the SAP

system user:p:<DOMAIN_NAME>\<NT_USERNAME>

<DOMAIN_NAME> is the Windows domain that the Windows user belongs to <NT_USERNAME> is the logon IDof the Windows user.p is a prefix that all SNC names require.

09/11/2006 PUBLIC 83

5 Post-Installation

5.11 Single Sign-On with Microsoft Kerberos SSP

.Example

For the Windows user Kissnerj, belonging to the domain SAP_ALL, enter:p:SAP_ALL\Kissnerj

6. Select Insecure communication permitted.This lets the user work in a different domain because it permits the user to access the system without SSO.

7. Save your entries.

ResultYou have now finished setting up SSO.


Kerberos Single Sign-On (SSO) is a secure method of logging on to the SAP system that simplifies the logonprocedure without reducing security. It is suitable if you use Windows 2000 and higher in your systemlandscape.When your system is configured for SSO, an authorized user who has logged on to Windows can access the

SAP system simply by selecting it in the SAP logon window or clicking the shortcut. No SAP system user nameor password is necessary. SSO makes it significantly easier for you to manage SAP system users.The Application Programming Interface (API) and Kerberos provide the security required for authentication.

The advantage of the Kerberos SSO solution is that the security information that has to be exchanged betweenthe SAP front end and the SAP application server is encrypted. In contrast, encryption is not implemented forSSO with Microsoft NTLM SSP, which is based on the Generic Security Service API (GSS-API) interface

.Example

When using gsskrb5.dll, the Microsoft Kerberos Security Service Provider (SSP) is interoperable withKerberos implementations from other vendors and suppliers. To use SSO with application servers onUNIX andWindows front ends with gsskrb5.dll, youmight have to purchase a Kerberos implementationfor the UNIX machines.

Prerequisites

SSO based on Kerberos can only be set up for users that are members of a Windows 2000 and higher domain.

Process Flow

To implement SSO with the Microsoft Kerberos NTLM SSP, you have to:

1. Prepare the central instance [page 85].2. Configure the SAP front ends [page 86].3. Configure the SAP logon [page 87].4. Map SAP users to Windows users [page 88].

84 PUBLIC 09/11/2006

5 Post-Installation


5.11.1 Preparing the Central Instance

To set up Single Sign-On (SSO) for Kerberos, you need to adapt the central instance profile and make sure thatthe necessary Dynamic Link Library (DLL) is located in the Windows directory.

Procedure

1. Copy the gsskrb5.dll file to the following directory on the central instance:Drive:\%windir%\system32.For more information about how to get the gsskrb5.dll file, see SAP Note 595341.

2. In the instance profile of the central instance, set the SAP parameters:snc/enable = 1

snc/gssapi_lib =<DRIVE>:\%windir%\system32\gsskrb5.dll

snc/identity/as =p:SAPService<SAPSID>@<DOMAIN_NAME>

<DOMAIN_NAME> is the Windows domain that the SAPService<SAPSID> user belongs to, for example,NT5.SAP-AG.DE.

.Caution

<DOMAIN_NAME> and the SAPService<SAPSID> user are case-sensitive. Make sure that you enteruppercase and lowercase correctly, for example:p:[email protected].

.Note

Although you can freely choose the Windows account under which the SAP system runs, it isnormally SAPService<SAPSID>.If you use a local account for the SAPService<SAPSID> user, most operations are successful. However,any operations or communications where the SAP system initiates SNC-protected communication toa remote machine, do not work with a local account for the SAPService<SAPSID> user. Therefore,use a domain account.

In the central instance profile, set the following SNC parameters:snc/data_protection/max =1

snc/data_protection/min =1

snc/data_protection/use =1

snc/enable =1

snc/gssapi_lib =

(<DRIVE>:\USR\SAP\<SAPSID>\SYS\EXE\<codepage\<platform>\<gssntlm.dll>)

snc/identity/as =p:<DOMAIN_NAME>\SAPService<SAPSID>

SAPService<SAPSID> is the user who runs the SAP system.<DOMAIN_NAME> is the Windows domain of this user.

09/11/2006 PUBLIC 85


5 Post-Installation


.Note

n Although you can freely choose the Windows account under which the SAP system runs, itis normally SAPService<SAPSID>.

n If you use a local account for SAPService<SAPSID>, most operations are successful. However, anyoperations or communications where the SAP system initiates SNC-protected communicationto a remote machine, do not work with a local account for SAPService<SAPSID>. Therefore,use a domain account.

Additional SNC ParametersThe following profile parameters let you continue with password-based access to the SAP system when SNChas been enabled. To log on to the SAP system as an administrator to maintain the mapping of Windowsuser accounts to SAP system user IDs (user and client), you have to use these additional parameters at leastonce after enabling SNC. Once the mapping (at least for the administrator) has been entered, you candisable further password-based logons by removing the respective profile parameters.snc/accept_insecure_cpic =1

snc/accept_insecure_gui =1

snc/accept_insecure_rfc =1

snc/permit_insecure_start =1

snc/permit_insecure_comm =1

3. Stop and restart the SAP system so that the profile parameters take effect.

5.11.2 Configuring the SAP Front End

To configure the SAP front end for SSO, you choose between the following approaches:

n Configure each SAP front end individuallyYou configure each machine where the SAP front end is running.

n Configure all SAP front ends automaticallyYou define a Group Policy for a Windows domain. This policy causes the wizard for configuring SSO to bestarted automatically in the background the next time any member of the domain logs on to an SAPfront end.

These approaches are described below.

PrerequisitesYou have completed Preparing the Central Instance [page 85].

Configuring SAP Front Ends Individually

1. Log on to the host where the SAP front end is running.2. Copy the SAPSSO.MSI program to a local directory or to a shared directory on the network.

For downloading the SAPSSO.MSI file, see SAP Note 352295.3. Double-click the SAPSSO.MSI file.

The wizard SAP Kerberos SSO Support automatically starts and configures the SAP front end for SSO.

86 PUBLIC 09/11/2006


5 Post-Installation


Configuring SAP Front Ends Automatically

1. Log on to a front-end machine as domain administrator of the Windows domain.2. Copy the program SAPSSO.MSI to a shared directory.

For more information about how to get the SAPSSO.MSI file, see SAP Note 595341.3. Choose Start ® Programs ® Administrative tools ® Active Directory Users and Computers.

The dialog box Active Directory Users and Computers appears.4. Right-click the domain for which you want to set up SSO and choose Properties.

The dialog box <Domain_Name> Properties appears.5. Choose Group Policy ® New to start creating a new policy object.

The dialog box for creating a new policy object appears.6. In Group Policy Object Links, enter a name for the new policy object, such as SAPSSO.7. Choose Edit to define the contents of the policy.8. In the Group Policy Editor choose User Configuration ® Software Settings ® Software Installation.

The Deploy Software dialog box appears.9. Right-click Deploy Software and choose New ® Package.

The Open dialog box appears.10. Select the file SAPMSSO.MSI from the shared location.11. Specify the path with the UNC name (\\<hostname>\<share>).12. Select Assign and confirm with OK.

You have now created a new Group Policy.The next time any user logs on to the domain with the SAP front end, the wizard SAP Kerberos SSO Support

automatically starts and configures the front end for SSO.

5.11.3 Activating Single Sign-On for the SAP Logon

The SAP Logon window includes a list of systems or machines that you can log on to. For each of the systems ormachines in the list for which you want to implement SSO, follow the procedure below.

Prerequisites

n You have completed the following:l Preparing the Central Instance [page 85]l Configuring the SAP Front End [page 86]

Procedure

1. Right-click an entry in the SAP Logon window and choose Properties.2. In the Network tab, select Activate Secure Network Communication..3. In SNC name, enter:

p:SAPService<SAPSID>@<DOMAIN_NAME>

where <DOMAIN_NAME> is, for example, NT5.SAP-AG.DE.

09/11/2006 PUBLIC 87


5 Post-Installation


.Note

n Enter the same string that you entered in the central instance profile forsnc/identity/as

If the system C11 is running on account SAPServiceC11 of the domain NT5.SAP-AG.DE, you wouldenter:P:[email protected]

n If the entry you selected in the logon dialog box is a group entry, for example, C11 (PUBLIC),the SNC name field is already filled.

4. Choose OK to confirm your entries.

The SAP Logon window now displays an icon with a key beside the system entry. This indicates that SingleSign-On is active for the system.

5.11.4 Mapping SAP Users to Windows Users

PrerequisitesYou have completed the following:

n Preparing the Central Instance [page 85]n Configuring the SAP Front End [page 86]n Activating Single Sign-On for the SAP Logon [page 87]

Procedure

1. Log on to the SAP system as administrator.2. Choose Tools ® Administration ® Maintain Users ® Users or call transaction SU01.

The User Maintenance window appears.3. Enter the name of the SAP user and choose User names ® Change.4. Choose SNC.5. In SNC name, use uppercase to enter the name of the Windows user that is to be assigned to the SAP user:

p:<WINNT_USERNAME>@<DOMAIN_NAME>

where <WINNT_USERNAME> is the logon ID of the Windows user and <DOMAIN_NAME> is the Windows domainthat the user is logged on to.

.Example

For the user Kissnerj, belonging to the domain NT5.SAP-AG.DE , enter:p:[email protected]

6. Select Insecure communication permitted.This lets the user work in a different domain because it permits the user to access the system without SSO.

7. Save your entries.

ResultKerberos SSO is now set up.

88 PUBLIC 09/11/2006

5 Post-Installation

5.12 Post-Installation Steps for Adobe Document Services


You perform the following post-installation steps:

n You assign the required roles to users ADSUSER and ADS_AGENT [page 89].n You perform quick tests for Adobe Document Services (ADS) [page 89].

5.12.1 Assigning Roles to Users ADSUSER and ADS_AGENT

During the installation SAPinst created the users ADSUSER for basic authentication and ADS_AGENT for processingforms between an ABAP and a Java environment.After the installation you have to assign the required authorization roles manually to these users in the

ABAP system, as described below.

Assigning Role SAP_BC_FP_ICF to ADS_AGENT

1. Log on to the ABAP system with user DDIC or SAP*.2. Call transaction SU01.3. Enter ADS_AGENT in the User field.4. Choose User Names ® Change.5. Choose the Roles tab and assign the role SAP_BC_FP_ICF to the user ADS_AGENT.

Creating Role ADSCallers and Assigning it to ADSUSER

1. Log on to the ABAP system [page 72].2. Call transaction PFCG.3. Enter ADSCallers in the Role field.4. Choose Role ® Create.5. On the Create Roles screen, choose Role ® Save.6. Choose the User tab and assign the user ADSUSER in the User ID field.

5.12.2 Installation Check and Quick Tests for Adobe DocumentServices

This procedure shows you how to check your installation of Adobe Document Services (ADS) entries for thecorrect user, security role, passwords, and RFC destination.

09/11/2006 PUBLIC 89

5 Post-Installation


.Note

This procedure contains only minimal configuration steps to check if the ADS installation with SAPinstwas successful.For detailed configuration documentation, see the configuration guide for Adobe Document Services:

n On SAP Service Marketplace at:service.sap.com/adobe ® Interactive Forms Based on Adobe Software ® Media Library ® Documentation ®Adobe Document Services - Configuration Guide NW 2004s

n In the SAP Library at:help.sap.com/nw2004s ® SAP NetWeaver Library ® Technology Consultant's Guide ® AdditionalCross-NetWeaver Configurations ® Adobe Document Services - Configuration.

Procedure

Checking the User and Password

1. Open a web browser.2. Enter the following URL:

http://<J2EE_host>:<J2EE_port>/AdobeDocumentServices/Config

.Note

Note that the entries in the URL are case-sensitive.

The web page of the Web service AdobeDocumentServices is displayed.3. Choose Test.4. Choose rpdata(test...).5. Choose Send without entering any parameters.6. Enter ADSUser as user name and the password you entered for this user previously.7. Choose Submit.

ResultIf the setup is correct, the system displays the version number in the response area.

.Note

You can ignore the message Required stream: “PDFDocument” not found.

If the setup is not correct, the page does not change and Submit remains on the screen.

Checking the ABAP Connection

1. Log on to your SAP system.2. Call transaction SE38.3. Enter the name of the test report FP_PDF_TEST_00.4. Choose Execute ( F8 ).

ResultIf the setup is correct, the system displays the version number.

90 PUBLIC 09/11/2006

5 Post-Installation

5.13 Ensuring User Security

If the setup is not correct, the system displays a dialog box with input fields for the user and password. Checkyour settings for the ABAP connection.


You need to ensure the security of the users that SAPinst creates during the installation. For security reasons,you also need to copy the installation directory to a separate, secure location ‒ such as a DVD ‒ and thendelete the installation directory.

.Recommendation

In all cases, the user ID and password are only encoded when transported across the network. Therefore,we recommend using encryption at the network layer, either by using the Secure Sockets Layer (SSL)protocol for HTTP connections, or Secure Network Communications (SNC) for the SAP protocolsdialog and RFC.For more information, see:help.sap.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Security ® Network

and Transport Layer Security

.Caution

Make sure that you perform this procedure before the newly installed SAP system goes into production.

PrerequisitesIf you change user passwords, be aware that SAP system users might exist in multiple SAP system clients (forexample, if a user was copied as part of the client copy). Therefore, you need to change the passwords in allthe relevant SAP system clients.

ProcedureFor the users listed below, take the precautions described in the relevant SAP security guide, which you canfind on SAP Service Marketplace at service.sap.com/securityguide:

ABAP+Java Users

User User Name Comment

SAP* User exists at least in SAP system clients000, 001 and 066.

DDIC User exists at least in SAP system clients000 and 001.

EARLYWATCH User exists at least in SAP system client 066.

SAP system user

SAPCPIC User exists at least in SAP system clients000 and 001.

09/11/2006 PUBLIC 91

5 Post-Installation


User User Name Comment

Administrator The name that you gave this user duringthe installation or the default nameJ2EE_ADMIN

This user’s password is stored in securestorage. Therefore, whenever you changethe administrator’s password, you mustalso change the password in secure storage.For more information, see Checking the SAPJava Documentation [page 76].

Guest The name that you gave this user duringthe installation or the default nameJ2EE_GUEST

‒

Communication user for theJ2EE Engine

The name that you gave this user duringthe installation or the default name SAPJSF.

‒

ADSUSER User exists at least in SAP system clients000 and 001.

Users for Adobe DocumentServices (ADS)

ADS_AGENT User exists at least in SAP system clients000 and 001.

Data supplier user for SystemLandscape Directory (SLD)(optional)

The name that you gave this user duringthe installation.The recommended name is SLDDSUSER.

User exists at least in SAP system clients000 and 001.

.NoteSAPinst created this userautomatically if you chose Configurelocal SLD during the installation.

ABAP API user for SystemLandscape Directory (SLD)(optional)

The name that you gave this user duringthe installation.The recommended name is SLDAPIUSER.

User exists at least in SAP system clients000 and 001.


Java Add-In Users for Users Stored in the ABAP System

User User Name Storage: ABAP System Comment

Administrator The name that you gave this user duringthe installation or the default nameJ2EE_ADMIN

This user’s password is stored in securestorage. Therefore, whenever you changethe administrator’s password, you mustalso change the password in secure storage.For more information, see Checking the SAPJava Documentation [page 76].

Guest The name that you gave this user duringthe installation or the default nameJ2EE_GUEST

‒

Communication user for theJ2EE Engine

The name that you gave this user duringthe installation or the default name SAPJSF

‒

92 PUBLIC 09/11/2006

5 Post-Installation

5.14 Configuring SAP Solution Manager

User User Name Storage: ABAP System Comment

ADSUSER User exists at least in the clients 000 and 001of the ABAP system.

Users for Adobe DocumentServices (ADS)

ADS_AGENT User exists at least in the clients 000 and 001of the ABAP system.

Data supplier user for SystemLandscape Directory (SLD)(optional)

The name that you gave this user duringthe installation.The recommended name is SLDDSUSER.

User exists at least in the clients 000 and 001of the ABAP system.


ABAP API user for SystemLandscape Directory (SLD)(optional)

The name that you gave this user duringthe installation.The recommended name is SLDAPIUSER.

User exists at least in the clients 000 and 001of the ABAP system.


5.14 Configuring SAP Solution Manager

You have to configure your SAP Solution Manager system.

Configuring the ABAP PartTo configure the ABAP part of SAP Solution Manager 4.0 SR1, proceed as follows:

1. Log on the client 000 of the SAP Solution Manager system.2. Call transaction SPRO.3. Choose SAP Reference IMG ® SAP Solution Manager Implementation Guide ® SAP Solution Manager

n All activities under Basic Settings are mandatory to ensure minimum SAP SolutionManager functionality.n All activities under Scenario Specific Settings are optional and depend on the functionalities of SAP Solution

Manager that you want to use.For more information, see the documentation Configuration Guide SAP Solution Manager 4.0 SR1 on SAP ServiceMarketplace at http://service.sap.com/solutionmanager ® SAP Solution Manager ® Installation Guides ®Release 4.0.

Configuring the Java PartTo configure Solution Manager Diagnostics see the documentation Supportability Setup Guide forSolution Manager Diagnostics SAP NetWeaver 04S SP Stack <current stack> on SAP Service Marketplace athttp://service.sap.com/solutionmanager ® SAP Solution Manager ® Installation Guides ® Release 4.0 ®Setup_Guide_Solution_Manager_Diagnostics_SPS current stack>.

09/11/2006 PUBLIC 93


6 Additional Information


The following sections provide additional information about optional preparation and post-installation tasks:

Preparation

n Database Installation for Multiple Components with MS SQL Server [page 95]n Installation of Multiple Components in One Database [page 97]n Integration of LDAP Directory Services [page 99]n Preparing the Active Directory [page 101]n Preparing User Management with an External ABAP system [page 102]

Post-Installation

n If required, you configure user management to use an LDAP directory [page 105].n Entries in the Services File Created by SAPinst [page 105]n Deleting an SAP System [page 106]n SAP System Security on Windows [page 108]n Automatic Creation of Accounts and Groups [page 109]n Manually Granting User Rights for the Installation [page 111]n Troubleshooting [page 112]

6.1 Database Installation for Multiple Components with MS SQLServer

Each SAP system in your mySAP environment needs its own database back end. With MS SQL Server you havethe following options to distribute your systems across the available hardware resources. They differ withrespect to hardware requirements, database administration, flexibility, and scalability.

n Exclusive database serverIn this system landscape, each database server (with or without a central instance) hosts exactly one SAPdatabase. From an installation planning perspective, this is the simplest solution. It is the most scalablesetup, but it requires the most hardware. This option is typically chosen for medium-sized and largeproduction and development systems.

n Named SQL Server instancesWith the use of named instances, you can install multiple, independent SQL Server instances on a singledatabase server. These instances share CPU, memory and disk resources, but from an administration pointof view are completely independent from each other. This option, like the following two, requires carefulhardware sizing to avoid performance bottlenecks and scalability problems.

n Multiple databases in an SQL Server instanceSQL Server lets you operate multiple user databases in a single SQL Server instance. Contrary to namedinstances, the databases share the temporary system database tempdb, the SQL Server Windows process, and

09/11/2006 PUBLIC 95


6.1 Database Installation for Multiple Components with MS SQL Server

the SQL Server memory pool. Therefore, this setup is less scalable than named instances, but at the sametime requires less system resources. It can be a flexible solution for small and medium-sized systems. Thisoption requires careful hardware sizing to avoid performance bottlenecks and scalability problems.

n Multiple Components in One Database (MCOD)Multiple database back ends are stored in the same database, each in its own database schema. For thedatabase administrator, the database containing these multiple components looks very much like a singleentity. While this approach is not as flexible as the other options, its simplicity makes it an attractivesolution for small mySAP environments. This option requires careful hardware sizing to avoid performancebottlenecks and scalability problems.

More Information

n Default or Named MS SQL Server Instances [page 96]n Multiple Components in One Database (MCOD) [page 97]

6.1.1 Default or Named MS SQL Server Instances

When you install MS SQL Server, you can install two different types of instances:

n Default instance

n Named instance

When you plan your system configuration, you must decide which instance type you want to install. Thefollowing clarifies the difference between the two.

Default Instance

A default instance is the most common form of an MS SQL Server installation in an SAP environment.Typically, one MS SQL Server instance is installed together with a single SAP database. In this configuration, allMS SQL Server components and functionality are exclusively available for the SAP database.In a less frequently implemented configuration, a single MS SQL Server instance is installed together

with more than one SAP database on the same computer. In this type of configuration, the MS SQL Servercomponents such as executables, system databases and utilities exist only once and have to be shared by allSAP databases. As all the databases on the computer have to be managed with a single copy of the MS SQLServer, certain administrative tasks on one database cannot be performed in isolation without affecting theother databases.

.Note

A default instance is recommended, if you plan to install only one SAP database instance on a computer.

Named Instance

The advantage of named instances is that you can set up several SAP databases on the same machine andadminister each one separately with its own copy of the MS SQL Server. The main components of the MS SQLServer are available exclusively for each instance and can be used only by that instance. Only a few resourcessuch as client utilities have to be shared by all the instances because they are only installed once. During the

96 PUBLIC 09/11/2006


6.2 Installation of Multiple Components in One Database (Optional)

installation, each named instance is given a name that is the same as the SAP system name, thus enabling aunique assignment of instances to SAP databases.Several named instances and the default instance can coexist on the same computer and function in

isolation of each other.

.Note

A named instance is recommended, if you plan to install more than one SAP database instance on thesame machine.

The following graphic illustrates a computer where two MS SQL Server named instances have been installedfor two SAP databases, <SAPSID1> and <SAPSID2>.

Figure 9:


You can installmultiple SAP systems in a single database. This is called Multiple Components in OneDatabase (MCOD).

.Example

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

09/11/2006 PUBLIC 97



MCOD is available with all SAP components. We are releasing this technology on all the major databases forthe SAP system, in line with our commitment to deliver platform-independent solutions.Using this technology is as easy as installing a separate component. No extra effort is required because the

MCOD installation is fully integrated into the standard installation procedure. MCOD is not an additionalinstallation service. Instead, it is an option of the database instance installation.With MCOD we distinguish two scenarios:

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

Prerequisites

n For more information on MCOD and its availability on different platforms, see the SAP Service Marketplaceat service.sap.com/mcod.

n MCOD is released for Unicode installations. A prerequisite is that the MCOD system contains Unicodeinstances only. SAP does not support mixed solutions.

n Improved sizing requiredIn general, you calculate the CPU usage for an MCOD database by adding up the CPU usage for eachindividual SAP system. The same applies to memory resources and disk space.You can size multiple components in one database by sizing each individual component using the SAPQuick Sizer and then adding the requirements together. For more information on the SAP Quick Sizer, seethe SAP Service Marketplace at service.sap.com/sizing.

Features

n Reduced administration effort

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

administration of only one databasen Independent upgrade

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

.Note

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

Constraints

.Recommendation

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

mix test, development, and production systems in the same MCOD.

n In the event of database failure, all SAP systems running on the single database are affected.

98 PUBLIC 09/11/2006


6.3 Integration of LDAP Directory Services (Optional)

n Automated support in an MCOD landscape for the following administrative tasks depends on youroperating system and database:l Copying a single component from an MCOD landscape to another database at database level is not

possible. You have to perform a homogeneous system copy with R3load instead.l De-installing a single component from an MCOD landscape requires some additional steps. You can

use a remote connection to SAP support to request help with these tasks. For more information seeservice.sap.com/remoteconnection.

n


MSCS only: You cannot install multiple components in one database with Microsoft Cluster Service(MSCS). For more information on MSCS, seeMicrosoft Cluster Installation.End of: HA (MSCS)

n For the first SAP system,make sure that DBSID is the same as for the first SAP system installed in this database.n For the second SAP system, make sure that you use the same DBSID as for the first SAP system.n As SAPinst turns off database logging during the database load phase of the installation, you need to plan

downtime for all MCOD systems sharing the database.


The Active Directory is a Lightweight Directory Access Protocol (LDAP) directory. LDAP is a feature ofWindows 2000 or higher that allows important information within a corporate network to be stored centrallyon a server. The advantage of storing information centrally for the entire network is that you have to maintaindata only once, thus avoiding redundancy and inconsistency.If an LDAP directory is available in your corporate network, you can configure the SAP system to use

this feature. For example, a correctly configured SAP system can read information from the directory andalso store information there.This section explains the benefits of using the SAP system with the LDAP directory. In addition, it gives an

overview of the configuration steps required to use an SAP system with the directory.

.Note

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

n The communication protocol between the SAP system and the directory

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

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

PrerequisitesYou can only configure the SAP system for Active Directory services or other LDAP directories if these arealready available on the network. As of Windows 2000 or higher, the Active Directory is automatically

09/11/2006 PUBLIC 99



available on all domain controllers. A generic LDAP directory is an additional component that youmust installseparately on a UNIX or Windows server.

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

n SAP Logonn The Microsoft Management Console (MMC)

For more information on the automatic registration of SAP components in LDAP directories and the benefits ofusing it in SAP Logon and MMC, see the documentation SAP System Information in Directory Services on SAP ServiceMarketplace at service.sap.com/msplatforms ® Microsoft ® Windows Server

SAP Logon

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

Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

Distinguish the following cases:

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

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

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

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

MMC

The MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from a centrallocation. If the SAP system has been prepared correctly, the MMC presents and analyzes system informationthat it gathers from various sources, including the Active Directory.Integrating the Active Directory as a source of information has advantages for the MMC. It can read system

information straight from the directory that automatically registers changes to the system landscape. As aresult, up-to-date information about all SAP application servers, their status, and parameter settings is alwaysavailable in the MMC.

100 PUBLIC 09/11/2006


6.4 Preparing the Active Directory (Optional)

If you need to administer distributed systems, we especially recommend that you use the MMC togetherwith Active Directory services. For example, you can simplify administration by using the MMC in a distributedenvironment that implements the mySAP Business Suite components SAP BW, SAP SRM, SAP SCM, and SAPCRM. You can keep track of significant events in all of the systems from a single MMC interface. You do notneed to manually register changes in the system configuration. Instead, such changes are automaticallyupdated in the directory and subsequently reflected in the MMC.

Configuration Tasks for Active Directory

To enable an SAP system to make use of the features offered by the Active Directory, you must configure boththe Active Directory and the SAP system:

1. You prepare the Active Directory so that it can store SAP data.This involves extending the schema for the SAP data types, creating a root container for the storage ofSAP-specific information, and defining accounts that allow directory access. You perform all these tasksusing SAPinst with the option Configure Active Directory for SAP System.For more information, see Preparing the Active Directory (Optional) [page 101].

2. You configure the SAP system to enable interaction with the Active Directory.You do this during the central instance installation using the SAPinst tool. SAPinst prompts you forinformation about the Active Directory and then configures the system accordingly.

Configuration Tasks for Generic LDAP Directories

To prepare the SAP system to use generic LDAP services, you must perform several steps to configure boththe LDAP directory and the SAP system:

1. You configure the LDAP directory to store SAP data.This involves extending the directory schema and creating a container for the SAP data.

2. You configure the SAP system to enable interaction with the LDAP directory.You do this during the central instance installation using the SAPinst tool. SAPinst prompts you forinformation about the Active Directory and then configures the system accordingly.

3. You set up a user with a password on the server where the SAP system is running to permit the system toaccess and modify the LDAP directory.You do this by running the script ldappasswd.

For more information on how to enable interaction between a generic LDAP directory and the SAPsystem, see the documentation SAP System Information in Directory Services in the SAP Service Marketplace atservice.sap.com/msplatforms ® Microsoft ® Windows Server

More Information

Preparing the Active Directory [page 101]

6.4 Preparing the Active Directory (Optional)

If you decided to use LDAP directory services, you need to prepare the Active Directory. The SAP system canthen use the Active Directory to store and access data.To prepare the directory, you use SAPinst to automatically:

09/11/2006 PUBLIC 101


6.5 Preparing User Management for an External ABAP System

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

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

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

.Note

For more information on how to set up a Netscape / iPlanet directory server, see the documentationSAP System Information in Directory Services on SAP ServiceMarketplace at service.sap.com/msplatforms®Microsoft ® Windows Server

PrerequisitesAWindows domain controller with an Active Directory is installed on the network.

Procedure

1. Log on as user with domain administrators rights.2. Run SAPinst and choose <SAP System> ® Additional Software Life-Cycle Tasks ® Additional Preparation Tasks ®

Active Directory Configuration.3. Follow the instructions in the SAPinst dialogs and enter the required parameters.

.Note

n When you are prompted for the password of the sapldap user, and this user does not yet exist,make sure that the password consists of at least 5 characters.

n For more information about the input parameters, position the cursor in the field of the respectiveparameter and press the F1 key.

When you have made these entries, SAPinst extends the Active Directory schema for the SAP system.


For a Java system, you can also deploy user management for an external ABAP system. In this case, youconfigure the User Management Engine (UME) of the J2EE Engine for the user management of a separateABAP system.If you want to connect more than one Java system to the same ABAP system, you need to work out a

concept for the communication, administrator, and guest users for each engine.You can take one of the following approaches:

102 PUBLIC 09/11/2006



Approach Advantages Disadvantages

Each Java system uses different users No interdependencies between theconnected engines

Initially more administration to createthe users in the ABAP system

All Java systems use the sameconfiguration

You create the users only once andenter the same information for everyJava system that you install.

Interdependencies between theconnected engines:n If you change the password of any

of the users on the ABAP system,this change affects all connectedengines.

n If you change the administratoruser’s password, you must alsochange the password in securestorage on all of the connectedJ2EE Engines

.Recommendation

For security reasons, we recommend the first approach.

The procedures below assume that you are using the first approach.

Prerequisites

n The ABAP system is based on at least SAP Web AS ABAP release 6.20 SP25.n In transaction PFCG, check that the roles SAP_BC_JSF_COMMUNICATION and SAP_BC_JSF_COMMUNICATION_RO

exist and make sure that their profiles are generated.n In transaction PFCG, check that the roles SAP_J2EE_ADMIN, SAP_J2EE_GUEST and SAP_BC_FP_ICF exist.

Neither role contains any ABAP permissions, so you do not need to generate any profiles.n In transaction PFCG, create a role named ADSCallers. You do not need to maintain authorization data

or generate any profiles for that role.n For more information, see:

help.sap.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Security ® IdentityManagement ® User Management Engine

.Note

For more information about role maintenance, see the SAP Library athelp.sap.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Security ®

Identity Management ® Users and Roles (BC-SEC-USR) ® SAP Authorization Concept ® Organizing AuthorizationAdministration ® Organization if You Are Using the Profile Generator ® Role Maintenance ® Role MaintenanceFunctions ® Changing Standard Roles

Administration of the ABAP systemPerform the following administration steps in the ABAP system:

1. In transaction SU01 create a new communication user and assign it to the roleSAP_BC_JSF_COMMUNICATION_RO.

09/11/2006 PUBLIC 103



.Recommendation

We recommend that you assign this user the role SAP_BC_JSF_COMMUNICATION_RO for read-only(display) access to user data with Java tools. If you intend to maintain user data (that is, to change,create, or delete users) with Java tools, you need to assign the role SAP_BC_JSF_COMMUNICATION instead.We recommend that you name the user SAPJSF_<SAPSID_Java_System>.You can use any password.

In addition, to make sure that this user can only be used for communication connections between systemsand not as a dialog user, assign it the type Communications under Logon data.

2. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_ADMIN. This is your administratoruser in the J2EE Engine.

.Recommendation

We recommend that you name the user J2EE_ADM_<SAPSID_Java_System>. You can use any password.

.Caution

Log on to the SAP system once with this user to change its initial password. Because the installer of theJ2EE Engine verifies this password, the installation fails if this password is initial

3. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_GUEST. This is your guestuser in the J2EE Engine.

.Recommendation

We recommend that you name the user J2EE_GST_<SAPSID_Java_System>. You can use any password.As this user is only used for anonymous access to the system, we recommend you to deactivate thepassword and, if required, lock it after installation to prevent anyone from using it for explicit namedlogons.

4. In transaction SU01 create the following dialog users :

.Caution

You must have changed the initial passwords [page 91] of these users before you start the installation ofthe Java system.

n Users for Adobe Document Services (ADS) (optional):l ADSUSER:

In transaction PFCG, assign the role ADSCallers to this user.l ADS_AGENT:

In transaction PFCG, assign the role SAP_BC_FP_ICF to this user.n SLD Data supplier user (optional):

You only have to create this user if you want to install System Landscape Directory (SLD). The SLDdata supplier user name that you enter later on during the Java system installation must be identicalto this user.

104 PUBLIC 09/11/2006


6.6 Configuring User Management to Use an LDAP Directory (Optional)

.Recommendation

We recommend that you name this user SLDDSUSER

n SLD ABAP API user (optional):You only have to create this user if you want to install System Landscape Directory (SLD). The SLDABAPAPI user name that you enter later on during the Java system installation must be identical to this user.

.Recommendation

We recommend that you name this user SLDAPIUSER

Activities for the Java SystemPerform the following steps in the Java system:

1. Before the installation of the Java system, make sure that you have the correct user names and passwords ofthe users listed above for the separate ABAP system.

2. During the installation of the Java system, make sure that you enter the correct users and passwordsin the corresponding SAPinst dialogs.

6.6 Configuring User Management to Use an LDAP Directory(Optional)

If your user data source is an LDAP directory, you need to configure the connection to the LDAP directoryafter installation.For more information, see:help.sap.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Security ® Identity

Management ® User Management Engine ® UME Configuration ® Configuring UME to Use an LDAP Server as Data Source

6.7 Entries in the Services File Created by SAPinst

After the installation has finished successfully, SAPinst has created the following entries for port names in<drive:>\WINDOWS\system32\drivers\etc\services:

sapdpXX = 32XX/tcp

sapdbXXs = 47XX/tcp

sapgwXX = 33XX/tcp

sapgwXXs = 48XX/tcp

where XX is set from 00 to 99.

.Note

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

09/11/2006 PUBLIC 105


6.8 Deleting an SAP System


The following sections describe how to delete a single instance, a standalone engine or a complete SAP systemwith SAPinst.To delete your system, you use the SAPinst service <SAP System> ® Additional Software Life-Cycle Tasks ®

Uninstall ® Uninstall System / Standalone Engine / Optional Standalone Unit.

.Note

This description assumes that you have installed your SAP system with standard SAP tools according tothe installation documentation.

.Caution

n Make sure that all remaining instances are stopped before you delete the database instance.

n You cannot delete an SAP system remotely.

n SAPinst deletes the database instance but you have to delete the database software manually.

n If you delete network-wide users, groups or service entries in an environment with NetworkInformation System (NIS), other SAP installations might also be affected. Make sure that the users,groups, and service entries to be deleted are no longer required.

Process Flow

n If you want to delete a central system, where all SAP instances reside on the same host, you can do thisin one SAPinst run [page 106].

.Note

SAPinst deletes the database instance but you have to delete the MS SQL Server database software withthe SQL Server Uninstaller, which you can find on Windows under Add/Remove Programs.

n If you want to delete a distributed system, where the SAP instances reside on different hosts, you have torun SAPinst [page 106] to delete the required instances locally on each host in the following sequence:1. You delete the dialog instance(s), if there are any.2. You delete the database instance.3. You delete the central instance.4. You delete the central services instance.

5.


You delete the ABAP central services instance.End of: HA (MSCS)

6. You delete the MS SQL Server database software with the SQL Server Uninstaller, which you findon Windows under Add/Remove Programs

6.8.1 Running SAPinst to Delete an SAP System

This procedure tells you how to run the Uninstall service of SAPinst.

106 PUBLIC 09/11/2006



PrerequisitesYou are logged on as a user with the required rights and privileges to run the SAPinst tool and the SAP system.For more information, see Granting User Rights for the Installation [page 34].

Procedure

1. Start SAPinst and on theWelcome screen, choose:<SAP System> ® Additional Software Life-Cycle Tasks ® Uninstall ® Uninstall System / Standalone Engine / OptionalStandalone Unit

.Note

With this SAPinst service you do not delete the database software.

2. Follow the instructions in the SAPinst input dialogs.

.Note

For more information about the input parameters, place the cursor on the relevant field and pressF1 in SAPinst.

SAPinst first asks you which SAP instances you want to delete.Make sure that you delete the SAP instances in the correct order, as described in Deleting an SAP System[page 106].

.Caution

n SAPinst only stops local instances automatically.Before you delete the database instance of a distributed system make sure that you stop allremaining instances. You must stop the instance with the message server only after having enteredall SAPinst parameters for the deletion of the database instance.

n If SAPinst stops responding while trying to delete the central instance, close SAPinst with Canceland Exit. Log off and log on again. To complete the uninstall process of the central instance,restart SAPinst .

3. Delete the local user group SAP_<SAPSID>_LocalAdminmanually as follows:a) Choose Start ® Programs ® Administrative Tools ® Computer Managementb) Choose Local Users and Groups ® Groups.c) Right-click the local group SAP_<SAPSID>_LocalAdmin and choose Delete.

4. When you have finished you can delete the MS SQL Server database software using the SQL ServerUninstaller, which you can find on Windows under Add/Remove Programs.

5. If required, you can delete the directory \usr\sap\trans and its contents manually.SAPinst does not delete \usr\sap\trans because it might be shared.

09/11/2006 PUBLIC 107


6.9 SAP System Security on Windows

6.9 SAP System Security on Windows

In a standard SAP system installation, SAPinst automatically performs all steps relevant for security. AlthoughSAPinst makes sure that the system is protected against unauthorized access, you must still check thatno security breaches can occur.For central and straightforward administration of the SAP system, you have to install distributed SAP systems

with multiple application servers in a Windows domain. This section describes the user accounts and groupsthat SAPinst creates during a domain installation and shows how these are related to the SAP directories.

User Accounts

SAPinst creates the following accounts for SAP system administration:

n <sapsid>adm

This is the SAP system administrator account that enables interactive administration of the system.

n SAPService<SID>

This is the user account that is required to start the SAP system. It has the local user right to log on as aservice.

The advantage of the additional SAPService<SAPSID> account is that it does not allow an interactive logon,which prevents abuse of the account. Therefore, you do not need to set an expiration date for the passwordand you do not have to set the option user must change password at next logon.

Groups

SAPinst creates the following groups during a domain installation:

n SAP_<SAPSID>_GlobalAdmin

This global group is a domain-level SAP administration group for organizing SAP system administrators.The only function of a global group is to group users at the domain level so that they can be placed inthe appropriate local groups.

n SAP_<SAPSID>_LocalAdmin

Only local groups are created and maintained on an application server. A local group can only be givenpermissions and rights to the system where it is located. The system is part of a particular domain, and thelocal group can contain users and global groups from this domain.

n SAP_LocalAdmin

This group is created on all hosts, but is particularly important for the transport host. Members of thegroup have full control over the transport directory (\usr\sap\trans) that allows transports to take placebetween systems.The SAP_<SAPSID>_GlobalAdmin groups of all the SAP systems that are part of the transportinfrastructure are added to the SAP_LocalAdmin group. As a consequence, the users <sapsid>adm andSAPService<SAPSID> of all systems in the transport infrastructure are members of the SAP_LocalAdmin

group and have the required authorizations necessary to initiate and execute transports.

SAP Directories

SAPinst protects the SAP directories under \usr\sap\<SAPSID> by only granting the groupSAP_<SAPSID>_LocalAdmin full control over these directories.

108 PUBLIC 09/11/2006


6.10 Automatic Creation of Accounts and Groups

The following graphic illustrates the user accounts and groups created by SAPinst in a system infrastructureconsisting of two SAP systems.

Figure 10: User Groups and Accounts

.Note

An access control list (ACL) controls access to SAP system objects. For maximum security in the SAPsystem, only the following are members of all SAP system object ACLs:

n Local group SAP_<SAPSID>_LocalAdmin

n Group Administrators

n Account SYSTEM


SAPinst automatically creates the accounts and groups required for the secure operation of the SAP system withWindows [page 108] during the installation.

FeaturesThe following graphics show the steps that SAPinst performs to create the users and groups and assign therequired rights to SAP directories.

09/11/2006 PUBLIC 109



Figure 11: Creating Users and Groups

110 PUBLIC 09/11/2006


6.11 Manually Granting User Rights for the Installation

Figure 12: Assigning Rights to SAP Directories

6.11 Manually Granting User Rights for the Installation

Although the rights required for the installation are automatically granted to the user who installs the SAPinsttool, you might need to manually grant user rights for the installation to another user, as described in thissection.

PrerequisitesThe Windows user that performs the SAP system installation must be authorized to perform the actionsnecessary for the installation.For a domain installation, this means that the user must belong to the Domain Administrator group and

be authorized to:

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

The procedure below assigns these rights to a user of your choice.

09/11/2006 PUBLIC 111


6.12 Troubleshooting

.Caution

Be aware that domain policies override locally defined policies. This means that if you want to grantdomain administrator rights for a local user, make sure that you have also defined domain administratorrights for this user on domain level.

Procedure

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

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

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

More InformationGranting User Rights for the Installation [page 34]


The following section(s) describe the steps that you need to performmanually if SAPinst fails:

n Troubleshooting with SAPinst [page 112]

6.12.1 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.If an error occurs, SAPinst:

n Stops the installationn Displays a dialog informing you about the error

Procedure

1. To view the log file, choose View Logs.2. If an error occurs during the dialog or processing phase, do either of the following:n Try to solve the problemn Abort the installation with Exit

For more information, see Interrupted Installation with SAPinst [page 65].n Continue the installation by choosing Retry.

3. Check the log and trace files of the GUI server and SAPinst GUI in the directory %userprofile%\.sdtgui\for errors.

4. If SAPinst GUI does not start, check the file sdtstart.err in the current %userprofile% directory.

112 PUBLIC 09/11/2006



5. If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as described inStarting SAPinst GUI Separately.

6. Ignore error messages in the SDM logs that state that software components are not available. For moreinformation, see SAP Note 828978.

09/11/2006 PUBLIC 113



7 High Availability with Microsoft Cluster Service

7 High Availability with Microsoft ClusterService

You can install a high-availability SAP system with Microsoft Cluster Service (MSCS). For this type ofinstallation, you have to set up the system on at least two clustered hosts (called “MSCS nodes”) and configureit so that it can take advantage of the MSCS software. The MSCS software improves the availability of thesystem and safeguards it against failure and unplanned downtime, enabling 24-hour operation, 365 days a year.With high availability you enable critical system components, so-called Single Points of Failure (SPOFs) to

be automatically switched from one machine to the other, if hardware or software problems arise on onemachine. With the help of this switchover ‒ or failover ‒ the system can continue functioning normally sothat unplanned system downtime is avoided.Apart from enabling failover when hardware problems occur, you can also use MSCS to avoid downtime

when you perform essential system maintenance. If you need to maintain one node, you can deliberatelyswitch the cluster resources to another node and temporarily operate it there while maintenance is in progress.When maintenance work is finished you can easily move the resources back to their original node andcontinue operating them there.

.Note

n Make sure that you read SAP Note 936703, which contains the most recent information as well ascorrections for MSCS for SAP NetWeaver 2004s SR1. For more information, see the SAP installationnotes [page 2] before you begin the installation.

n In this documentation the hosts in an MSCS cluster are referred to as first MSCS node and additionalMSCS node(s).

n When you are setting up the SAP system with MSCS, you combine standard installation steps,described earlier in this documentation, with cluster-specific steps, described here.

To install a new SAP system with MSCS, you have to perform a number of extra steps specially required for thecluster and configure the SAP system so that it can take advantage of the cluster functionality:

n You cluster the SQL Server already when you install the database software.n Since the cluster hardware has at least two nodes that have access to all local and shared storage devices,

you have to install some components on all nodes and observe special rules for distributing componentsto local or shared disks.

n Since the correct configuration of network addresses is absolutely essential to enable the cluster tofunction properly, you have to perform a number of additional steps that are necessary to set up andcheck addressing.

09/11/2006 PUBLIC 115



7.1 Planning

.Note

If you have an existing SAP system and plan to migrate to a cluster with new hardware, you install theSAP system using a system copy. Therefore, you have to prepare for the installation by creating ahomogeneous or a heterogeneous copy of the database. After you have created a copy of the database,you can install your system with MSCS. However, instead of loading the database from the Export DVDsin the installation package, you load it using your exported database.For more information about a homogeneous or heterogeneous system copy, see the documentation

Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP NetWeaver on SAP Service Marketplace atservice.sap.com/instguidesNW04Installation. In addition, for more information about a heterogeneoussystem copy, see service.sap.com/osdbmigration.The documentation for a homogeneous or heterogeneous system copy does not include the

cluster-specific information, which is described here.

7.1 Planning

You have to complete the following planning activities for you SAP system using Microsoft Cluster Service(MSCS):

1. You decide how to set up your SAP system components in an MSCS configuration [page 116].2. You install an enqueue replication server [page 119].3. You distribute components to disks for MSCS [page 120].4. You read Directories in an MSCS Configuration [page 122]5. You read IP Addresses in an MSCS Configuration [page 122]6. You obtain IP addresses for MSCS [page 126].7. You check the hardware and software requirements for MSCS [page 128].

7.1.1 SAP System Components in an MSCS Configuration

In an MSCS configuration you have the following components for your SAP system:

SAP System Components in an MSCS Configuration

ComponentNumber of Components per SAPSystem Single Point of Failure

SCS instance (message services andenqueue services)

1 yes

ASCS instance (message services andenqueue services)

1 yes

Database instance 1 yes

Application server (central instance,dialog instance)

1-n no

116 PUBLIC 09/11/2006


7.1 Planning

n To protect the SPOFs ((A)SCS instance and database instance) you have to use MSCS.If a hardware or software problem occurs on the first MSCS node, the clustered (A)SCS instance and theclustered database automatically fail over to another node.If you need to maintain the MSCS node where the (A)SCS instance and database are running you canswitch these instances to another node. When maintenance work is finished you move the (A)SCS anddatabase instance back to the original node.The following graphic shows an example where the SPOFs are installed on two MSCS cluster.

Figure 13: ABAP+Java System

n To protect system components that are non-SPOFs, for example application servers, you have to installthem as multiple components. In this case you must install at least two application servers (one central andat least one dialog instance) on two different hosts. You have the following options:l You install the central instance and the dialog instance on the MSCS nodes of an MSCS cluster. You

install them on a local disk.If you have to maintain an MSCS node, you have to stop the central or dialog instance on that node.When you have finished maintenance, you restart the instance(s).Any additional application servers (dialog instances) are installed on hosts outside of the MSCS cluster.The following graphic shows the central and dialog instance installed on one MSCS cluster with twoMSCS nodes

09/11/2006 PUBLIC 117


7.1 Planning


l You install the central instance and all dialog instances outside of an MSCS cluster on different hosts,as show in the following graphic. In this example, the (A)SCS instance and the database instance areinstalled in one MSCS cluster.

118 PUBLIC 09/11/2006


7.1 Planning


7.1.2 Enqueue Replication Server in an MSCS Configuration

For this type of installation, you install an enqueue replication server on allMSCS nodes where the Java centralservices (SCS) instance and the ABAP central services (ASCS) instance are installed.The enqueue replication server contains a replica of the lock table (replication table).In normal operation the replication enqueue server is always active on the host where the SCS and ASCS

instance are not running.If an enqueue server in anMSCS cluster with two nodes fails on the first MSCS nodes, the enqueue server on

the additional MSCS node is started. It retrieves the data from the replication table on that node and writes itin its lock table. The enqueue replication server on the second MSCS node then becomes inactive. If the firstMSCS node is available again, the enqueue replication server on the second MSCS node becomes active again.The following graphic shows the enqueue replication server mechanism in an MSCS configuration with

two nodes:

09/11/2006 PUBLIC 119


7.1 Planning

Figure 16: Enqueue Replication Server Mechanism on One MSCS Cluster with Two Nodes

7.1.3 Distribution of Components to Disks for MSCS

One of the central points to keep in mind when planning the MSCS installation is that the cluster hardwarehas two different sets of disks:

n Local disks that are connected directly to the MSCS node(s)n Shared disks that can be accessed by all MSCS nodes via a shared interconnect

.Note

Shared disk is a synonym for the MSCS resource of Resource type Physical disk.

You need to install the SAP system components in both the following ways:

n Separately on all MSCS nodes to use the local storage on each node.n On the shared storage that is used in common by all MSCS nodes.

You install the following on different shared disks:l Database data files

l SAP system executablesl Single quorum device, if used

With Windows Server 2003, you can now choose between the following cluster models:

120 PUBLIC 09/11/2006


7.1 Planning

n Single Quorum Device ClusterIn this cluster model the quorum resource maintains the cluster configuration data on a single clusterstorage device.The quorum resource is unique to a cluster installation and is always owned by one of the nodes. It has thefollowing main functions in the cluster:l It logs changes to the cluster configuration that are entered in the Registry.l It arbitrates between competing nodes when the communication between nodes breaks down. This

means that cluster resources are forced to fail over to the node that owns the quorum resource.n Majority Node Set Cluster

In this new cluster model, each node maintains its own copy of the cluster configuration data. TheMajority Node Set resource, acting as the Quorum Resource, ensures that the cluster configuration data iskept consistent across the different nodes.You can use majority node set for geographically dispersed cluster configuration.SAP supports Majority Node Set Cluster if it is part of a cluster solution offered by your Original EquipmentManufacturer (OEM), or Independent Hardware Vendor (IHV).

The following graphic shows a cluster configuration where the (A)SCS and DB instance are installed inthe same cluster. It illustrates how to distribute the database data files, the SAP system executables, and thequorum resource (if used) to different disks. Only with this distribution of files to distinct disks is it possible tomove the SAP system and database as separate entities in a failover situation.

Figure 17:

09/11/2006 PUBLIC 121


7.1 Planning

More InformationDirectories in an MSCS Configuration [page 122]

7.1.4 Directories in an MSCS Configuration

The following tables show the directories where the main software components for the SAP cluster installationare stored:

Directories on Local Disks on MSCS Nodes

Component Default Directory

A supported operating system [page 128] %windir%

MSCS software %windir%\Cluster

SAP cluster files %windir%\SAPCluster

Directories on Shared Disks

Component Default Directory

Cluster quorum resource <drive>:\MSCS

SAP global and instance directories <drive>:\usr\sap ...

tempdb databases <drive>:\TEMPDB

msdb, model, master <drive>:\mssql

SAP data files <drive>:\<SAPSID>DATA1

<drive>:\<SAPSID>DATA2

<drive>:\<SAPSID>DATA3

SapCluster Directory

In an SAP cluster installation, an additional directory ‒ %WINDIR%\SapCluster ‒ is created under the systemdirectory.This contains all the SAP files required by all MSCS cluster nodes, independently of the MSCS node the

SAP instance is running on. The files are database tools and program files (executables) used by the operatingsystem monitor (SAPOsCol).The directory is added to the path variable of the user <sapsid>adm.

7.1.5 IP Addresses in an MSCS Configuration

A part of the installation process that is unique to MSCS is the configuration of host names and IP addresses inthe network. This is a particularly important task because the addressing plays a key role in the switchoverprocedure. Addressing must be set up correctly so that the system can take advantage of the clusterfunctionality and switch between nodes when hardware problems arise.

122 PUBLIC 09/11/2006


7.1 Planning

This section explains the different types of IP addresses and their function in the switchover mechanism ofan MSCS cluster with two nodes.

Types of IP Addresses

In a correctly configured cluster with at least two nodes, there are at least seven IP addresses and correspondinghost names. You have two IP addresses for each MSCS node, one IP addresses for the network adapter, and twoaddresses for the cluster group.Some of the addresses are physical IP addresses that are assigned to the network adapters (cards), others are

virtual IP addresses that are assigned to the cluster groups.

Physical IP Addresses Assigned to Network Adapters

An MSCS configuration usually has two networks:

n A public network that is used for the communication between the central instance, application serversand the LAN.

n A private network that is used internally for communication between the nodes of the cluster.

To set up these two networks, each node needs an adapter for both the private and public network. This meansthat each node must have an adapter for the private network and an adapter for the public network and each ofthese adapters has its own physical IP address and corresponding host name.

.Note

For more information on network configuration, see also the Microsoft Knowledge Base Article 259267.

The following graphic shows an MSCS cluster with two nodes and illustrates the adapters required for thepublic and private networks, and their corresponding physical IP addresses. A physical IP address, as opposed toa virtual one, is stationary and permanently mapped to the same adapter.

09/11/2006 PUBLIC 123


7.1 Planning

Figure 18: Adapters and IP Addresses Required for Public and Private Networks in an MSCS Cluster withTwo Nodes

Host Names Assigned to Network Adapters

Each of the physical IP addresses of the network adapters must have a corresponding host name. For example,on the left-hand node in the graphic above, you might assign the IP addresses of the public and private networkadapters as follows:

IP Addresses and Host Names

Network Adapter IP Address Host Name

Adapter 1 (private network) 10.1.1.1 clusA_priv

Adapter 3 ( public network) 129.20.5.1 clusA

124 PUBLIC 09/11/2006


7.1 Planning

.Caution

Make sure that you are aware of the following:

n The IP address and host name of the public network adapter is also the IP address and name of themachine. In our example, this means that the machine that is the MSCS node on the left in thegraphic has the name clus1.

n Do not confuse the host name with the computer name. Each node also has a computer name,which is often the same as the host name, but is written in uppercase.The computer name is displayed in the node column of the Cluster Administrator. However, it isnot required for the TCP/IP communication in the cluster. When you configure IP addresses andcorresponding names, keep in mind that it is the host names that are important for the cluster, notthe computer names.

Virtual IP Addresses Assigned to Cluster Groups

When you have installed the SAP system and fully configured the cluster, the critical system resources arebound together in three different groups. Each of these groups requires a virtual IP address and host namethat is permanently mapped to the group and not to a particular node. This has the advantage that, whenevera group is moved between nodes, its IP address and host name move together with it.A cluster configuration has the following groups:

n SAP cluster groupn Database cluster groupn Cluster group

Each group consists of a set of related resources that work together to offer a service to the system. For example,the database cluster group comprises all the resources that enable the database server to fulfill the requests of aclient. When the group is moved from one node to the other, due to node failure, the virtual IP address andhost name move with it. Therefore, there is a failover not only of resources, but also of the virtual IP addressand host name. As a result, all clients can still reach the database server with the same IP address as before.The following graphic illustrates how the virtual IP addresses of the database group and SAP group canmove

from one node to the other when failover occurs.

09/11/2006 PUBLIC 125


7.1 Planning

Figure 19: Failover of Virtual IP Addresses

7.1.6 Obtaining IP Addresses for MSCS

You need to correctly configure IP addresses for a cluster system. During the installation procedure you haveto assign at least seven IP addresses and host names. You normally obtain these names and addresses fromthe system administrator.

Prerequisites

n If you are installing Windows for the first time on your system, follow the procedure Obtaining IP Addressesbelow.

n If Windows has already been installed on your system, the host names and IP addresses of the networkadapters (cards) have already been defined and exist in your system.This means that you can find out the IP addresses for the network adapters using the procedure DeterminingExisting IP Addresses below.However, you still need to use the table Virtual IP Addresses in the procedure Obtaining IP Addresses.

Obtaining IP AddressesAsk the system administrator to give you the addresses and host names listed in the tables below, which showsan example for a configuration with one MSCS cluster with two nodes. You will need to enter the addressesand host names later during the installation process.The column Defined During indicates at which stage of the installation the addresses are defined in the system.

126 PUBLIC 09/11/2006


7.1 Planning

.Caution

Use the names exactly as specified by the system administrator, carefully observing uppercase andlowercase letters.

Physical IP Addresses

ComponentExample for PhysicalIP Address

Example for PhysicalHost Name Purpose Defined During

First MSCS Node:adapter for privatenetwork

10.1.1.1 clusA_priv Address for inter-node communicationon the privatenetwork

Windows installation

First MSCS Node:adapter for publicnetwork

129.20.5.1 clusA Address of the firstMSCS node forcommunication withapplication serversand LAN (this is thesame as the address ofthe first MSCS node)


Additional MSCSNode:adapter for privatenetwork

10.1.1.2 clusB_priv Address for inter-node communicationon the privatenetwork


Additional MSCSNode:adapter for publicnetwork

129.20.5.2 clusB Address of theadditionalMSCSnodefor communicationwith applicationservers and LAN(this is the same asthe address of theadditional MSCSnode)


Virtual IP Addresses

ComponentExample for VirtualIP Address

Example for HostName Purpose Defined During

Cluster group 129.20.5.3 clusgrp Virtual address andname of the clustergroup. It identifiesthe cluster and is usedfor administrationpurposes.

MSCS softwareinstallation

09/11/2006 PUBLIC 127


7.1 Planning

ComponentExample for VirtualIP Address

Example for HostName Purpose Defined During

SAP cluster group 129.20.5.4 sapgrp Virtual address andname for accessingthe group of SAPresources, regardlessof the node it isrunning on

Configuration of SAPsystem for MSCS withSAPinst on the firstnode

Database clustergroup

129.20.5.5 dbgrp Virtual address andname for accessingthe group of databaseresources, regardlessof the node it isrunning on

Execution ofMSCS wizard ordatabase-specificcluster scripts

Determining Existing IP AddressesTo find out the existing IP addresses and corresponding host names and addresses, proceed as follows:

1. Choose Start ® Settings ® Network and dial-up Connections.The Network and dial-up Connections window appears

2. Select one of the network cards that are displayed and choose File ® Properties.A dialog box opens.

3. Choose TCP/IP Protocol ® Properties.The TCP/IP Properties dialog box appears and shows the IP address of the initially selected network card.

4. To find out the host name that is mapped to the IP address, use the ping command:ping -a <IP_Address>

The system returns the host name assigned to the IP address.Do not forget to ping your local machine as well.

5. Repeat these steps for the other network cards.

For more information about IP addresses in the cluster environment, see IP Addresses in an MSCS Configuration[page 122].

7.1.7 Checking Hardware and Software Requirements for MSCS

When you install the SAP system on cluster hardware, you have to meet the hardware requirements shownbelow. This makes sure that the system can take advantage of the MSCS functionality and achieves anacceptable performance level.

Procedure

1. Check that your cluster hardware is certified.AddOn Technology Center for SAP (Add On TCS) certifies hardware platforms for SAP on MicrosoftWindows. The cluster must be included in the Microsoft list of certified clusters and its components. Youcan access the lists at the following Internet addresses:www.microsoft.com/hcl

128 PUBLIC 09/11/2006


7.1 Planning

www.saponwin.com

2. Make sure that the MSCS nodes of the cluster are connected by a private and public network:n The public network enables communication from the MSCS nodes of the cluster to other resources in

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

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

3. Check that sufficient storage space is available.Each of the MSCS nodes in the cluster must have its own local disks and have access to shared disks that canbe reached by the MSCS nodes via a shared bus.All software ‒ except the Windows operating system, the MS SQL server system database, and the MSCSsoftware ‒ 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.

Disks Required Space How to Check

1 local disk on each MSCSnode

3 GB a) Choose Start ® Programs ® Administrative Tools ®Computer Management ® Disk Management.

b) Right-click the disk and choose Properties.

At least 4 shared disks n Non-Unicode (notincluding paging file):

n Unicode (not includingpaging file):

a) Choose Start ® Programs ® Administrative Tools ®Computer Management ® Disk Management.

b) Right-click the disk and choose Properties.

.Note

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

4. Check the RAM and paging file size on each MSCS node.For more information, see the Hardware and Software Requirements Checklists [page 26].

5. Check that the software you install on the cluster nodes meets the following requirements:

Software Requirement How to Check

English international version of one of the following:n Windows Server 2003 Enterprise Editionn Windows Server 2003 Datacenter Edition

.NoteWe strongly recommend you to use the 64-bitversion of the Windows Server 2003 editions.

.NoteIf you install SQL Server 2005, you must install atleast SP1 for Windows Server 2003.

To check the Windows version

a) Choose Start ® Programs ® Accessories ® CommandPrompt

b) Enter the command winver

09/11/2006 PUBLIC 129


7.2 Preparation

Software Requirement How to Check

n One of the following SQL Server Enterprise Editionserver software:l MS SQL Server 2000 Enterprise Edition: Server

Softwareu Latest service pack and hotfix, if available.

For more information, see SAP Notes 62988and 608651.

u Unicode collation SQL_Latin1_Gen-eral_CP850_BIN2For more information on the collation forMS SQL Server 2000, see SAP Note 600027.

l MS SQL Server 2005 Enterprise Edition: ServerSoftwareu Latest service pack and hotfix, if available.

For more information, see SAP Notes 62988and 608651.

u Unicode collation SQL_Latin1_Gen-eral_CP850_BIN2

n For more information on the current Service Packfor MS SQL Server 2000, see SAP Note 62988.

n For more information on the current hotfix for MSSQL Server 2000, see SAP Note 608651.

n For more information on the new collation, for SQLServer 2000, see Installing the Corrected MS SQL ServerCollation for MS SQL Server 2000 [page 51]

A suitable Windows Resource Kit is stronglyrecommended

-

7.2 Preparation

You have to complete the following preparations for the MSCS cluster installation:

1. Make sure, that you have installed the operating system [page 128] with the option Cluster Service on allMSCSnodes. For more information, see the Windows documentation.

2. On allMSCS nodes, you manually assign drive letters to the shared disks [page 130] using theWindows Disk Administrator.All MSCS nodes must access the shared disks with the same drive letters.

3. On allMSCS nodes, you adjust the size of paging file and the file cache. For more information, see Hardwareand Software Requirements [page 128] and Reducing the Size of File Cache [page 34].

4. You map the IP addresses to host names [page 131] on the Domain Name System (DNS) Server or in the hosts file.5. You check the mapping of host names for MSCS [page 131].

.Note

To make sure that all preparation steps have been correctly performed, check that you can move the diskresources from one node to another so that they are only accessible from a single node at any time.

.Caution

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

7.2.1 Assigning Drive Letters for MSCS

We recommend that you assign drive letters for MSCS.

130 PUBLIC 09/11/2006









7.2 Preparation

In an MSCS cluster, the shared disks that can be accessed by all nodes via a common bus must be addressedby all nodes with the same drive letters.

Procedure

1. Choose Start ® Programs ® Administrative Tools ® Computer Management ® Storage ® Disk Management.2. Select a disk and choose Action ® All tasks ® Change drive.3. Enter a new drive letter.

7.2.2 Mapping Host Names to IP Addresses for MSCS

To enable correct operation of the failover mechanism, you have to map all IP addresses in the MSCS cluster tohost names.The mapping enables the system to translate host names into IP addresses. Host names are normally used

for administrative tasks because they are easier to use than the long, numeric IP addresses. However, the systemcan only respond to host names if they are translated into IP addresses.

Prerequisites

n You have installed the Windows operating system.n You have the list of IP addresses [page 126].n You have correctly entered all seven IP addresses required for the MSCS configuration.

.Caution

Missing or incorrect entries for the IP addresses can cause problems later during the installation.

ProcedureTo map the host names to the IP addresses, do one of the following:

n Map the host names to IP addresses on a Domain Name System (DNS) server.n Map the IP addresses in the Windows hosts file.

The file is located in the default Windows directory:%SystemRoot%Drive\system32\drivers\etc

.Recommendation

We recommend that you perform themapping on the DNS server because this only requires a single entry.If you perform the mapping in the hosts file, you have to maintain the hosts file on all MSCS nodes of

the cluster, and on all application servers and front ends, as each host in the system has its own hosts file.

7.2.3 Checking the Mapping of Host Names for MSCS

You need to check the mapping of host names to IP addresses as otherwise you might have serious problemslater.

09/11/2006 PUBLIC 131


7.3 Installation

PrerequisitesYou have mapped the host names to the IP addresses [page 131] on the DNS Server or in the hosts file.

Procedure

1. For each IP address enter the following commands:a) ping -a <IP_Address>

The system returns the host name that is assigned to the IP address.b) ping hostname

The system returns the IP address that is assigned to the host name.

.Note

n When you enter the ping command, you do not get a reply if the host does not yet exist.

n If the address you are checking already exists in the system, you also receive a reply from thehost. For example, after the installation of Windows and the configuration of the network, youget a reply when entering the IP addresses of the network adapters.

2. Compare the output with your own record of addresses and host names, and check for the followingpossible errors:n Incorrect output of uppercase and lowercase

Make sure that you correct the error before you proceed with the installation.n Error in the network bindings

If you enter the name of the public network adapter, which is usually also the name of the local host,and the system returns the IP address of the private network, there is an error in the network bindings.To correct the network bindings, do the following on allMSCS nodes:a) Choose Start ® Settings ® Network and Dial-up Connections

The Network and Dial-up Connections window appears.b) Choose Advanced ® Advanced Settings ® Adapters and Bindings

The network cards of the private and public networks are displayed for the current MSCS node.

.Note

The card of the public network must be displayed before that of the private network. Ifnecessary, change the order in which the cards are listed by using theMove Up andMove Downarrows

7.3 Installation

The following sections provide information about how to install the SAP system for MSCS.

132 PUBLIC 09/11/2006


7.3 Installation

.Note

n Make sure that you are logged on as domain administrator, unless otherwise specified.If for any reason, you are not granted domain administrators rights, you can perform the installation asa domain user who is a member of the local administrators group. However, the domain administratorhas to prepare the system appropriately for you. Do not use the user <sapsid>adm unless specified.

n On the first MSCS node, in the Cluster Administrator, make sure that all existing cluster groups are online.

n If you are prompted during the installation process, log off and log on again.

n When you reboot during the installation process [page 142], resources fail over to another node. Therefore, aftereach reboot, you have to return the system to the state it had before the reboot.

You have to perform the following steps:

1. In the Cluster Administrator, you move all disk groups and the cluster group to the first MSCS node [page 141].2. On the firstMSCS node, you install MS SQL Server [page 133].3. You install the central services instance for ABAP (ASCS) on the first MSCS node [page 142].4. You install the central services instance (SCS) on the first MSCS node [page 142].5. You cluster the first MSCS node [page 143].6. You install the database instance on the first MSCS node [page 144].7. You cluster the additional MSCS node [page 144].8. If required, you install an enqueue replication server [page 146].9. You install the central instance [page 147].10. You install at least one dialog instance [page 147].

7.3.1 Clustering the SQL Server Database Software

The following sections describe how to install the SQL Server 2000 or SQL Server 2005 database software foran MSCS configuration.

.Note

If you cluster SQL Server 2000, the installation procedure differs for 32-bit [page 133] or 64-bit [page135]systems.

.Caution

For MSCS, you must install MS SQL Server as a default instance.

7.3.1.1 Clustering the SQL Server 2000 Database Software in a32-Bit System

You perform the following steps on the first MSCS node.

Procedure


09/11/2006 PUBLIC 133


7.3 Installation

2. Insert the MS SQL Server 2000 RDBMS DVD into your DVD drive.3. To start the installation, run autorun.exe located in the x86\SQL2000 directory of the RDBMS DVD.4. Enter the required information as specified in the table:

Window Input

MS SQL Server 2000 Enterprise Edition Select SQL Server 2000 Components.

MS SQL Server 2000 Enterprise Edition Select Install Database Server.

.NoteUse the option to create a new virtual server.

Welcome Click Next.

Computer Name: Enter the name of the virtual server and click Next.

User Information Enter your personal information.


CD-Key Enter the key specified in the file SAPCDKEY.txt in the rootdirectory of the RDBMS DVD and choose Next.

Failover Clustering n Enter the IP address and subnet mask of the virtualdatabase server and click Add.

n Select the public net for the network to use.

Cluster Disk Selection Select the shared disk, where you want to put the data filesand choose Next.

.NoteWhen you select a shared disk you can ignore thewarning that the selected disk is a shared disk in acluster. To proceed, confirm the warning.

Cluster Management Select all MSCS nodes.

Remote Information Enter a domain administrator user account for all MSCSnodes and choose Next.

Instance Name Make sure that Default is selected and choose Next.

Setup Type Select Custom.When you are asked in the Setup Type dialog for thedestination folder for the program and data files, make surethat you install then program files on a local drive. For more information,

see Directories in an MSCS configuration [page 122].n data files for the master, pubs and msdb databases on one

of the shared drive of the MSSQL group (the defaultvalue for these files is the local disk).

Select Components Select all components and choose Next.

Service Accounts Select Use the same account for each service and enter the passwordfor the displayed domain administrator account.

134 PUBLIC 09/11/2006


7.3 Installation

Window Input

Authentication mode Select Windows Authentication Mode and choose Next.

.NoteFor a Java system, Mixed mode is required. SAPinstautomatically changes the authentication mode intoMixed mode when installing a Java system.

Collation settings Select SQL Collations.From the dropdown list, select Binary order, for use with the 850(Multilingual) Character Set.

Network Libraries Leave selection unchanged and choose Next.

Start Copying Files Choose Next.

Choose Licensing Mode Select your licensing mode.

Setup Complete Click Finish.

5. Install the latest Service Pack and hot fix, if available, on the first MSCS node. The Service Pack and the hotfix will also be automatically installed on the additional MSCS node(s).For the current version of the Service Pack and hot fix for MS SQL Server that is supported by SAP, seeSAP Notes 62988 and 608651.

.Note

If you have to reboot, move theMSSQL database group back to the first MSCS node.

6. Install the corrected MS SQL Server collation [page 51] on the first MSCS node. For more information, see SAPNote 600027.

7. If you have more than one disk in your SQL Server database cluster group, make sure that the SQL Servercluster resource is dependent on all physical disks.To check, perform the following steps:a) In the Cluster Administrator, under the database group, right-click on SQL Server, and take it offline.b) Double-click the SQL Server cluster resource.c) Under Dependencies, selectModify.d) Move all available disks shown under Available resources to Dependencies.e) Confirm your entries with OK.f) In the Cluster Administrator, under the database group, right-click SQL Server, and bring all resources of

the SQL cluster group online.

7.3.1.2 Clustering the SQL Server 2000 Database Software in a64-Bit System

You perform the following steps on the first MSCS node.

09/11/2006 PUBLIC 135





7.3 Installation

Procedure

1. Log on to the host as a local administrator.2. Insert the MS SQL Server 2000 RDBMS DVD in your DVD drive.3. To start the installation, run setup.exe located in the directory IA64\SQL2000.4. Enter the required information as specified in the table:

Window Input

Setup Mode n Select Start a new installation.n Select Virtual Server.

Registration Information Enter your name and the product key specified in the fileSAPCDKEY.txt in the root directory of the RDBMS DVD.


Virtual Server Name Enter the virtual server name.

Cluster Group Selection Select the cluster group for the virtual server resources.

Failover Clustering n Select the public network to use.n Enter the IP address for the virtual server, and choose

Add.

Instance Name Make sure that Default is selected and choose Next.

Configure Nodes Select the MSCS nodes to configure.

Remote Account Information Enter a domain administrator user account for yourMSCS nodes and choose Next.

Installation Folders Select the destination folder for the program and datafiles. Make sure that you install then program files on a local drive. For more

information, seeDirectories in an MSCS configuration [page122].

n data files for the master, pubs and msdb databases onone of the shared drive of the MSSQL group (thedefault value for these files is the local disk).

Service Account Select Use a Domain User account and enter the password forthe displayed domain administrator account.

Authentication Mode n Select the authentication mode.We recommend to useWindows authentication mode.

.NoteFor a Java system,Mixed mode is required. SAPinstautomatically changes the authenticationmode intoMixed mode when installing a Javasystem.

n Enter and confirm the password for the sa login.

.NoteIf you have chosenWindows authentication mode, thesa login is created, but cannot be used.

136 PUBLIC 09/11/2006


7.3 Installation

Window Input

Security Enhancement: Cross Database Ownership Chaining Leave selection unchanged and choose Next.

Collation Settings Select SQL Collations.From the dropdown list, select Binary order, for use with the850 (Multilingual) Character Set.

Licensing Mode Select the licensing mode and choose Next.

Ready to Install Select Install.

5. Install the latest service pack and hotfix, if available for MS SQL Server on the first MSCS node. The servicepack and hotfix will be automatically installed on the additional MSCS node(s).For the current version of the Service Pack and hotfix for MS SQL Server that is supported by SAP, seeSAP Note 62988 and 608651.

6. Install the corrected MS SQL Server collation [page 51] on the first MSCS node. For more information, see SAPNote 600027.

7. If you have more than one disk in your SQL Server database cluster group, make sure that the SQL Servercluster resource is dependent on all physical disks.To check, perform the following steps:a) In the Cluster Administrator, under the database group, right-click on SQL Server, and take it offline.b) Double-click the SQL Server cluster resource.c) Under Dependencies, selectModify.d) Move all available disks shown under Available resources to Dependencies.e) Confirm your entries with OK.f) In the Cluster Administrator, under the database group, right-click SQL Server, and bring all resources of

the SQL cluster group online.

7.3.1.3 Clustering the SQL Server 2005 Database Server Software

This section describes how to install the SQL Server 2005 database server software for MSCS on 32-bit or64-bit systems.The SQL Server 2005 database server software must be installed on the database host.

.Note

To install the client software, see Installing the SQL Server 2005 Native Client Software Manually [page 55].

PrerequisitesThe following prerequisites apply if you install SQL Server 2005 for MSCS.

.Note

For more information and a complete list of the restrictions, see the Books Online for SQL Server 2005 at:http://msdn.microsoft.com/en-us/library/ms130214.

09/11/2006 PUBLIC 137





7.3 Installation

n Make sure that you have not applied NTFS compression to the disk where you install the SQL Serversoftware.

n You have installed Microsoft Distributed Transaction Coordinator (MSDTC). For more information onhow to install MSDTC, see KB 301600 at support.microsoft.com/KB/301600.

n You have created domain user groups for each clustered service like SQL Server, SQL Agent, Full Text.l Ask the domain administrator to create the domain groups with the Group Type Security and Group

Scope Domain Local.l The group names must already exist in the domain before you start the SQL Server 2005 installation.l Ask your domain administrator to add the startup account for each service to the respective domain

groups.l Microsoft recommends that you use for each service a different domain group.l Microsoft recommends that you do not share the SQL server domain groups with other applications.

n You have created the SQL Server database cluster group and added the shared disks for the SQL Severdatabases to the group.

Procedure

.Note

You perform the following steps on all MSCS nodes.

1. Log on as a domain user who is a member of the local Administrators group on all MSCS nodes.2. Insert the SQL Server 2005 RDBMS DVD in your DVD drive or mount it locally.3. Change to the platform-specific folder and choose Enterprise Edition ® Servers.4. Start the installation program with setup.exe.5. Enter the required information as specified in the table below:

.Note

The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL

server\90\Setup Bootstrap\LOG. You find the summary of the setup log in summary.txt in thesame directory.

Window Server Input

End User License Agreement Accept the licensing terms and conditions and chooseNext.

Installing Prerequisites Choose Install and, if required, Next.

Welcome to the Microsoft SQL Server Installation Wizard. Choose Next.

138 PUBLIC 09/11/2006


7.3 Installation

Window Server Input

System Configuration Check a) Check your system configuration and, if required,set up the required configuration.

.Noten For more information about the required

system configuration for a softwarecomponent, chooseMessage.

n IIS is not required for an SAP system.Therefore, you can ignore the warningabout the IIS Feature Requirement.

n If there is a warning in COM Plus CatalogRequirement, correct the configuration beforeyou proceed with the installation. Makesure that theMicrosoft Distributed TransactionCoordinator (MSDTC) service is running.

n The system configuration is checked on allMSCS nodes.

b) Choose Next.

Registration Information a) Enter your personal information, and the productkey.

b) Choose Next.

Components to Install a) Select the following options:n SQL Server Database Servicesn Create a SQL Server failover clustern Workstation components, Books Online and development tools.

.NoteThe workstation components like SQLManagement Studio, or Books Online are not installedon the additional MSCS node(s). To installthem, start the installation program withsetup.exe on the additional MSCS node(s),after you have finished the installation onthe first MSCS node, and chooseWorkstationcomponents.

b) Choose Advanced.

Feature Selection a) Expand Database Services and deselect Replication

b) Expand Client Components and if available,deselectBusiness Intelligence Development Studio.

.NoteWe recommend that you deselect these featuresas they are not required for an SAP system.

c) Choose Next.

09/11/2006 PUBLIC 139


7.3 Installation

Window Server Input

Instance Name Select Default Instance and choose Next.

Virtual Server Name Enter the virtual server name and choose Next.

.NoteThe virtual server namemust be unique in thenetwork.

Virtual Server Configuration a) Select the public network and enter the IP address.

b) Choose Add and then Next.

Cluster Group Selection Select the cluster group where the virtual serverresources are to be installed, and choose Next.

Cluster Node Configuration a) Select and add all MSCS nodes to be included in thevirtual server.

b) Choose Next.

Remote Account Information Enter a domain administrator who is a member of thelocal Administrators group on all MSCS nodes, andchoose Next.

Service Account a) Select Use a domain user account and enter the user nameand password.

b) Choose Next.

Domain Groups for Clustered Services.NoteThe startup account for each clustered service isadded to the DomainName\GroupName to set its accesscontrol. If you do not have domain Administrator’srights, ask your domain administrator to add theseuser accounts to the appropriate domain groups.

Enter the domain and group names of the clusteredservices, and choose Next.

Authentication Mode a) SelectMixed Mode (Windows Authentication and SQL ServerAuthentication).This mode is required for a Java or ABAP+Java system.If you choose this mode, you set the password for thesa login.

.NoteSAPinst automatically changes theauthentication mode into Mixed Modewhen installing a Java system.The password for the sa login must complywith the Windows password policy.

b) Choose Next.

140 PUBLIC 09/11/2006


7.3 Installation

Window Server Input

Collation Settings a) Select SQL collations (used for compatibility with previousversions of SQL Server).

b) From the drop-down list select Binary order, based on codepoint comparison, for use with the 850 (Multilingual) CharacterSet.

c) Choose Next.

Error and Usage Report Settings Leave the selection unchanged, and choose Next.

Ready to Install Choose Install.

Setup Progress.NoteTo see the log files for the SQL Server components,choose Setup finished.When the setup process has finished, choose Next.

Completing Microsoft SQL Server 2005 Setup Choose Finish.

6. When you have finished the installation, enable the Named Pipes and TCP/IP protocol in the SQL ServerConfiguration Manager as follows:n Choose All Programs ® Microsoft SQL Server 2005 ® Configuration Tools ® SQL Server Configuration Manager.n Expand SQL Server 2005 Network Configuration and select one of the following:n For a default instance, select Protocols for MSSQLServer

n For a named instance, select Protocols for <SAPSID>n In the right-hand pane, under Protocol Name, right-click Named Pipes and TCP/IP, and select Enable.

7. Restart SQL Server.

7.3.2 Moving MSCS Groups

During the cluster installation you have to move the database, SAP, or disk cluster groups from one MSCSnode to the other before you can continue.

Prerequisites

n The groups you want to move are configured and are visible in the Cluster Administrator.n For more information if you need to reboot during the installation, see Rebooting During the Installation or

Conversion for MSCS [page 142].

Procedure

Moving Groups with the Cluster Administrator

1. Start the Cluster Administrator with Start ® Programs ® Administrative Tools ® Cluster Administrator.2. In the Cluster Administrator, select the group you want to move and drag it to the required MSCS node on the

left-hand pane.3. Repeat the previous step for each group that you want to move.

09/11/2006 PUBLIC 141


7.3 Installation

7.3.3 Rebooting During the Installation or Conversion for MSCS

You only need to perform this procedure if you have to reboot during the installation or conversion for MSCS.A reboot means that resources fail over to another MSCS node. Therefore, after each reboot, you have toreturn the system to the state it had before the reboot, as described below.

Procedure

1. In the Cluster Administrator, move all resources back to the original node.2. If you have not yet clustered the database, restart the database service.3. If you have already clustered the database, bring the database group online.4. Recreate the SAPMNT share for the directory usr\sap.

.Caution

You have to reset the permissions for the SAPMNT share from Read to Full Control, as follows:a) Right-click on the directory usr\sap and choose Sharing and Security.b) Select Sharing and in the Share Name field, enter SAPMNT.c) Under Permissions, make sure that the permission for User Everyone for SAPMNT is set to Full Control.

7.3.4 Installing the Central Services Instance for ABAP (ASCS)

1. Run SAPinst [page 56] and choose<Your SAP System>® SAP Systems ® <Database>® High-Availability System®Based on <technical stack> ® Central Services Instance for ABAP (ASCS).

2. If you are installing the SCS instance with SAPinst for the first time and SAPinst prompts you to log off,choose OK and log on again.

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

.Note

For more information about the input parameters, position the cursor on a parameter and pressF1 in SAPinst.

.Caution

The ASCS installation drive must be a shared disk that belongs to the SAP cluster group.

4. Check that the ASCS instance is running.

7.3.5 Installing the Central Services Instance (SCS)

.Caution

Make sure that you install the SCS instance on the same shared disk as the ASCS instance.

1. Run SAPinst [page 56] and choose<Your SAP System>® SAP Systems ® <Database>® High-Availability System®Based on <technical stack> ® Central Services Instance (SCS).

142 PUBLIC 09/11/2006


7.3 Installation

2. If you are installing the SCS instance with SAPinst for the first time and SAPinst prompts you to log off,choose OK and log on again.

3. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

.Note


.Caution

The SCS installation drive must be a shared disk which belongs to the SAP cluster group.

4. Check that the SCS instance is running.

7.3.6 Configuring the First MSCS Node

To configure the first MSCS node so that it functions properly in MSCS, you have to run the clusterconfiguration option offered by the SAPinst tool. When you run this option it:

n Creates the SAP cluster groupn Copies tools to the SAPCluster directoryn Sets the SAPService to manual

n Makes sure that the SAPOsCol service is started from the SAPCluster directory

.Caution

When you reboot during the conversion to MSCS [page 142], resources fail over to another MSCS node. Therefore,after each reboot you have to return the system to the state it had before the reboot.

Prerequisites

n You are logged on to the firstMSCS node as domain administrator or as a local user with domainadministration rights. For more information, see Performing a Domain Installation without being a Domain Administrator[page 36].

n The ASCS and SCS installation drive(s) must be online on the first MSCS node.

Procedure

1. Run SAPinst [page 56] and choose <Your SAP System> ® SAP Systems ® <Database> ® High-AvailabilitySystem ® Based on <technical stack> ® First MSCS Node.

.Note

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

2. Enter the required parameter values.

09/11/2006 PUBLIC 143


7.3 Installation

.Note

Make sure that you choose instance type ABAP + Java SCS Instances (ABAP+Java).

.Note

For more information about the input parameters, position the cursor on the parameter and pressF1 in SAPinst.

3. When the installation is finished, make sure that the following value is set in the default profile:enque/serverhost=<Virtual_(A)SCS_HostName>

ResultSAPinst converts the SAP instances on the first MSCS node for operation in MSCS.

7.3.7 Installing the Database Instance

Prerequisites

n The SAP cluster group is Online on the first MSCS node.n The DB cluster group is Online on the first MSCS node.

ProcedurePerform the following steps on the first MSCS node.

1. On the first MSCS node, run SAPinst [page 56] and choose<Your SAP System> ® SAP Systems ® <Database> ®High-Availability System ® Based on <technical stack> ® Database Instance.

2. Follow the instructions in the SAPinst dialogs and enter the required parameter values.a) For the profile UNC path you have to use the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.b) For the tempdb database, specify shared disks that are included in the MSSQL group.c) Distribute the transaction logs and SAPdata files to at least two different shared disks that are included

in theMSSQL group. For more information, see: Distribution of Components to Disks for MSCS [page 120]

.Note

For more information about the input parameters, position the cursor on a parameter and press theF1 key in SAPinst.

7.3.8 Configuring the Additional MSCS Node

To configure the additional MSCS node(s) in the cluster, you have to run the MSCS configuration optionforeach additional MSCS node offered by the SAPinst tool. When you run this option it:

n Creates users and groupsn Sets the system and user environmentn Enters required port numbers in the Windows services file

144 PUBLIC 09/11/2006


7.3 Installation

n Creates the SAPService and SAPOsCol Services

.Caution

When you reboot during the conversion to MSCS [page 142], resources fail over to another MSCS node. Therefore,after each reboot you have to return the system to the state it had before the reboot.

Prerequisites

n You are logged on to the additionalMSCS node as domain administrator or as a local user withdomain administration rights. For more information, see Performing ad Domain Installation without being aDomain Administrator [page 36].

n You have already configured the first MSCS node [page 143], which is the primary cluster node.

Procedure

1. Run SAPinst [page 56] and choose Additional MSCS Node.

.Note


2. Run SAPinst and choose <Your SAP System> ® SAP Systems ® <Database> ® High-Availability System ®Based on <technical stack> ® Additional MSCS Node.

.Note


3. Enter the required parameter values.

.Note

Make sure that you choose instance type ABAP + Java SCS Instances (ABAP+Java).

.Note

For more information about the input parameters, position the cursor on the parameter and pressF1 in SAPinst.

When you have made all required entries, SAPinst begins processing and converts the SAP instances on theother MSCS node for operation in MSCS.

4. When SAPinst has finished, start the SAP cluster group SAP <SAPSID> as follows:a) Open the Cluster Administrator with Start ® Programs ® Administration Tools ® Cluster Administrator.b) Select the SAP cluster group and bring it online.

09/11/2006 PUBLIC 145


7.3 Installation

7.3.9 Installing an Enqueue Replication Server

We recommend that you install an enqueue replication server with SAPinst on allMSCS nodes where an SCSor ASCS instance is running.

.Note

You have to perform the installation at least four times, for each (A)SCS instance and on eachMSCS node.

Prerequisites

n Your SCS and ASCS instance is already clustered with MSCS.n You have to install the enqueue replication server on a local disk.

Procedure

1. On the firstMSCS node, log on as domain user who is a member of the local administrators group.2. Run SAPinst [page 56] and choose<Your SAP System>® SAP Systems ® <Database>® High-Availability System®

Based on <technical stack> ® Enqueue Replication Server.3. Follow the instructions in the SAPinst dialogs and enter the required parameters.

Note the following, when entering the parametersn On the SAPinst screen: SAP System > SAP Instance, enter the:l SAP system ID <SAPSID> of your SAP systeml Instance number of the SCS or ASCS instance

l Virtual instance host name of the SCS or ASCS instance

n On the SAPinst screen SAP System > Enqueue Replication Server Instance, enter a unique instance number thatis not in use by another instance on this host.

n Decide if you want to restart the SCS and ASCS instance and service cluster resources with SAPinst now,or later with the Cluster Administrator.

.Note

You only need to do this once for all enqueue replication servers that you install on the MSCSnodes.

After you have entered all required input information, SAPinst starts the installation and displays theprogress of the installation. During the process phase, the enqueue server instance is started.SAPinst installs the enqueue replication server instance on a local disk in the following directory:.\usr\sap\<SAPSID>\ERS<instance_number>\

.Note

The profile is replicated from the global host to the local instance profile folder. The enqueuereplication server instance uses the profile from the local instance profile folder:.\usr\sap\<SAPSID>\ERS<instance_number>\profile\

4. On the additionalMSCS node, start SAPinst to install the enqueue replication server for the SCS or ASCSinstance as described in step 2 above.

146 PUBLIC 09/11/2006


7.3 Installation

.Note

There is no need to move the SCS or ASCS cluster group to another MSCS node.

5. Enter the required parameter values in the SAPinst dialogs as described above.

7.3.10 Installing the Central Instance

The following describes how to install the central instance for MSCS.You have the following options to install the central instance:

n You install the central instance on an MSCS node.In this case, bring the SAP cluster group online on this node, and make sure that the central instancenumber is different from the (A)SCS instance number.

n You install the central instance on a host outside of MSCS.In this case, you have to install the database client software on this host.

Procedure

1. Run SAPinst [page 56] and choose<Your SAP System>® SAP Systems ® <Database>® High-Availability System®Based on <technical stack> ® Central Instance.

2. If SAPinst prompts you to log off, choose OK and log on again.3. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

.Caution

n If you install the central instance on an MSCS node, make sure that on the screen SAP System> General Parameters for the:l Profile Directory, you use the UNC path of the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.l Installation Drive, you choose the local disk where you want to install the central instance. Do not

enter the shared disk for the (A)SCS instance.

.Note


4. Check that the central instance is running.

7.3.11 Installing the Dialog Instance

You have to install at least one dialog instance for MSCS.You have the following options to install the dialog instance:

n You install the dialog instance on an MSCS node.

09/11/2006 PUBLIC 147


7.4 Post-Installation

In this case, bring the SAP cluster group online on this node, and make sure that the dialog instancenumber is different from the (A)SCS instance number.

n You install the dialog instance on a host outside of MSCS.In this case, you have to install the database client software on this host.

Procedure

1. Run SAPinst [page 56] and choose<Your SAP System>® SAP Systems ® <Database>® High-Availability System®Based on <technical stack> ® Dialog Instance

2. If SAPinst prompts you to log off, choose OK and log on again.3. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

.Caution

n If you install the dialog instance on an MSCS node, make sure that on the screen SAP System> General Parameters for the:l Profile Directory, you use the UNC path of the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.l Installation Drive, you choose the local disk where you want to install the dialog instance. Do not

enter the shared disk for the (A)SCS instance.

.Note


4. If required, install additional dialog instances outside of MSCS.

.Caution

Make sure that on the screen SAP System > General Parameters for the Profile Directory, you use the UNCpath of the virtual (A)SCS host name, for example:\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.


This section describes how to complete and check the installation of the SAP system for anMSCS configuration:

1. You have installed at least one SAP front end [page 39].2. You start and stop the SAP system in an MSCS configuration [page 148].3. You perform the post-installation checks for the enqueue replication server [page 149].4. If required, you perform the other post-installation steps [page 71] listed in Chapter 6 in this guide.

7.4.1 Starting and Stopping the SAP System in an MSCSConfiguration

The following describes how to start or stop the SAP system in an MSCS configuration with the:

148 PUBLIC 09/11/2006



n SAP MMC

n Cluster Administrator

.Note

You also use the Cluster Administrator for all other administrative tasks like moving instances from oneMSCS node to another MSCS node.

Procedure

n To start or stop your SAP system with the SAP MMC, see Starting and Stopping the SAP System [page 71].n To start or stop your SAP system with the Cluster Administrator do the following:

1. Start the Cluster Administrator by choosing Start ® Programs ® Administrative Tools ® Cluster Administrator.2. To start or stop all instances belonging to the SAP cluster group, right-click the SAP cluster group SAP

<SAPSID> and choose Bring online or Take offline.3. To start or stop a single instance of the SAP cluster group, right-click the instance SAP <SAPSID>

<instance_no> Instance and choose Bring online or Take offline.

7.4.2 Post-Installation Checks for Enqueue Replication Server

.Note

Make sure that you have restarted the SCS and ASCS instance and service cluster resources SAP <SAPSID><(A)SCS_instance_number> Instance and SAP <SAPSID> <(A)SCS_instance_number> Service and SAP <SAPSID><(A)SCS_instance_number> Service during the installation with SAPinst or with the Cluster Administrator.

The following sections describe the tests you must perform to check whether the installed enqueue replicationserver works properly. For these tests you use the ENQT and ENSMON command line tools, which allowremote access to the enqueue server statistics. Before you can use these tools you must copy them to theremote host where the Enqueue Replication Server is running and from where you want to start the tests.You perform the following steps:

1. You copy ENQT.exe and ENSMON.exe from your cluster’s binary directory on the sapmnt share\\<host>\sapmnt\<SAPSID>\SYS\exe\<codepage>\<platform> to a directory on the remote host fromwhere you run the tests.

2. You check the status of the enqueue replication server with the ENSMON tool [page 149].3. You check the fill status and ID of the lock table during failover with the ENQT tool [page 150].

7.4.2.1 Checking the Status of the Enqueue Replication Serverwith ENSMON

You use the ENSMON tool to check if the enqueue replication server and the enqueue server are properlyconnected.

09/11/2006 PUBLIC 149



Prerequisites

n You have started the SCS and ASCS instances of your SAP system.n You run the ENSMON tool from the host where you installed the Enqueue Replication Server.

ProcedureTo check the status of the enqueue replication server enter the following command:

ensmon pf=<ERS_instance_profile> 2

where <ERS_instance_profile> is the profile created during the installation of the Enqueue ReplicationServer.

n If the enqueue replication server and the enqueue server are properly connected, the output is similarto this:Try to connect to host <Virtual (A)SCS host> service sapdp01 get replinfo request executed

successfully

Replication is enabled in server, repl. server is connected

Replication is active

...

n If the enqueue replication server and the enqueue server are not properly connected, the output is similarto this:Try to connect to host <Virtual (A)SCS host> service sapdp01 get replinfo request executed

successfully

Replication is enabled in server, but no repl. server is connected

...

7.4.2.2 Monitoring the Lock Table During Failover with ENQT

With the following tests you monitor and check the lock table’s fill status and the lock table ID using theENQT tool.

Prerequisites

n You have started the SCS and ASCS instances of your SAP system.n You run the ENQT tool from the host where you installed the Enqueue Replication Server.

.Caution

Only use the ENQT commands stated in this procedure otherwise you might damage the enqueueserver’s lock table.

Monitoring the Lock Table Fill Status During Failover with ENQT

1. Use the following command to fill the lock table of the enqueue server with 20 locks:enqt pf=<ERS_instance_profile> 11 20


2. Monitor the fill status of the lock table with the following command:

150 PUBLIC 09/11/2006



enqt pf=<ERS_instance_profile> 20 1 1 9999

This command continuously reads the content of the enqueue server’s lock table and returns the numberof the table entries to the console.

3. Move the (A)SCS cluster group to another MSCS node to simulate an enqueue server failover whilerunning the ENQT command.The output is similar to this:Number of selected entries: 20

Number of selected entries: 20




Number of selected entries: 0 ( enqueue server fails over )Number of selected entries: 20 ( enqueue server is running again )Number of selected entries: 20




...

4. Make sure that the lock count is the same before and after the failover.

Monitoring the Lock Table ID During Failover with ENQT

1. Monitor the lock table ID during the failover with the following command:for /l %i in (1,1,100000) do enqt pf=<ERS_instance_profile> 97


2. Move the (A)SCS cluster group to another MSCS node to simulate an enqueue server failover whilerunning the ENQT command.The output is similar to this:...

(Output before failover)C:\WORK\HA\ENQU-Tests>enqt pf=BUG_ERS01_PCJ2EEV6 97

---REQ----------------------------------------------------------

EnqId: EnqTabCreaTime/RandomNumber = 25.10.2005 11:15:59 1130231759

/ 9288

...

(Output after failover)C:\WORK\HA\ENQU-Tests>enqt pf=BUG_ERS01_PCJ2EEV6 97

---REQ----------------------------------------------------------

EnqId: EnqTabCreaTime/RandomNumber = 25.10.2005 11:15:59 1130231759

/ 9288

...

3. Make sure that the lock table ID (ENQID) is the same before and after the failover.

09/11/2006 PUBLIC 151


A Reference

A Reference

A.1 The Main SAP Documentation Types

The following is an overview of themost important documentation types that you need in the variousphases in the life cycle of an SAP solution.

Figure 20: Documentation types in the software life cycle

Cross-Phase Documentation

SAPterm—SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages,as well as many glossary entries in English and German

n Target group:l Relevant for all target groups

n Current version:l On SAP Help Portal at help.sap.com ® Additional Information ® Glossary (direct access) or Terminology

(as terminology CD)l In the SAP system in transaction STERM

09/11/2006 PUBLIC 153

A Reference


SAP Library—The SAP Library is a collection of function- and process-oriented documentation for SAPcomponents. The SAP Library also contains the Business Scenario Descriptions.

n Target group:l Consultants

l System administratorsl Project teams for implementations or upgrades

n Current version:l Located in the SAP Help Portal at help.sap.com (also available as documentation CD)l Located in the SAP Service Marketplace at service.sap.com/ibc (only the Business Scenario

Descriptions)

Implementation Guide (IMG)—The Implementation Guide is a tool for configuring the SAP system to meetcustomer requirements. Its structure and documentation are component-oriented.

n Target group:l Solution consultants

l Project teams for implementations or upgradesn Current version:l In the SAP menu of the SAP system under Tools ® Customizing ® IMG

Security Guide—The Security Guide describes the settings for a medium security level and offers suggestionsfor raising security levels. A collective security guide is available for the SAPNetWeaver technologies, such as theSAP NetWeaver Application Server (SAP NW AS). This document contains general guidelines and suggestionsabout system security. Other technologies and individual applications have a Security Guide of their own.

n Target group:l Technology consultantsl Solution consultants

l Project teams for implementations or upgradesn Current version:l Located in the SAP Service Marketplace at service.sap.com/securityguide

Implementation

Master Guide—The Master Guide is the starting point for implementing an SAP solution. It lists the requiredSAP components, and third-party applications that are required for each Business Scenario. It providesscenario-specific descriptions of preparation, execution, and follow-up of an implementation. It also offersreferences to other documents, such as Component Installation Guides and SAP Notes.

n Target group:l Technology consultantsl System administratorsl Project teams for implementations

n Current version:l Located in the SAP Service Marketplace at service.sap.com/instguides

Component Installation Guide—The Component Installation Guide describes the technicalimplementation of an SAP component, taking into account the combinations of operating systems anddatabases. It does not describe any business-related configuration.

154 PUBLIC 09/11/2006

A Reference


n Target group:l Technology consultantsl Project teams for implementations


Configuration Documentation in SAP Solution Manager—SAP Solution Manager is a tool with variousfunctions, one of its main functions being the configuration of SAP solutions and Business Scenarios. Itcontains IMG activities, transactions, and so on, as well as documentation. Instead of the configurationdocumentation in SAP Solution Manager, there might be separate Business Scenario Configuration Guides inthe SAP Service Marketplace for previous shipments of the Business Scenarios.

n Target group:l Solution consultants

l Project teams for implementationsn Current version:l In SAP Solution Managerl Located in the SAP Service Marketplace at service.sap.com/ibc

Production Operation

Solution Management Guide—The Solution Management Guide is the starting point for operating an SAPsolution. The guide refers users to the tools and documentation that are needed to carry out various tasks,such as monitoring, backup / restore, master data maintenance, transports, and tests. It also refers users toother documents, for example the SAP Library, the Master Guide, and the Component Management Guides.

n Target group:l System administratorsl Technology consultantsl Solution consultants

l Project teams for implementations or upgradesn Current version:l Located in the SAP Service Marketplace at service.sap.com/instguides

Upgrade

Upgrade Master Guide—The Upgrade Master Guide is the starting point for upgrading the BusinessScenarios of an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-upof an upgrade. It also refers to other documents, such as the Component Upgrade Guides and SAP Notes.Instead of an Upgrade Master Guide, there might be several Business Scenario Upgrade Guides or a SolutionUpgrade Guide for previous shipments of the Business Scenarios of an SAP solution.

n Target group:l Technology consultantsl Project teams for upgrades


09/11/2006 PUBLIC 155

A Reference


Component Upgrade Guide—The Component Upgrade Guide describes the technical upgrade of an SAPcomponent, taking into account the combinations of operating systems and databases. It does not describe anybusiness-related configuration.

n Target group:l Technology consultantsl Project teams for upgrades


Release Notes—Release Notes are documents that contain short descriptions of new features or changesin an SAP component since the previous release. Release Notes about ABAP developments enable the SAPsystem to generate delta and upgrade IMGs

n Target group:l Consultants

l Project teams for upgradesn Current version:l Located in the SAP Service Marketplace at service.sap.com/releasenotesl In the SAP menu of the SAP system under Help ® Release Notes (only ABAP developments)

156 PUBLIC 09/11/2006


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2006 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Documents

SAP Solution Manager 4.0 Installation Guide