n

n
















































“ ”










































































n


n


















“ ”









“ ”









“ ”
























































































“ ”
®





n


n

n

n

n








n



n


n






l

l






n


n


n

n


n






n










®



“ ”


®
® ¸























®
® ®




®
® ®


®
® ®





®
® ®

¸ ‒







¸



®
® ®

¸




®
® ®


¸



®
¸




®
®
® ¸
®
















n

n












¸



¸
¸

¸
¸

n
¸
n
¸





n

n


¸











n


n




l

l

l

l








n
¸
n


l

l

l

n

l







u


u

u

l





¸
¸









n

n

n










n







n











n







n


l

l



n


l

l


n

n

























“ ”






n

n

n

n

n















n

n

n






















































¸



















n

n








































n



n





n



n





n

l

l







l


l

u


u

u




n





n

n

¸ ¸ ®
















¸
¸ ¸

¸ ¸
¸
¸

¸ ¸


¸

¸

n



l


l


l



l


n






n

l




l

n


n

n


n

n




® ¸ ¸ ® ®




n

n

l


l



l

u


u


l



® ® ® ®



n


®
n










® ¸

n

l

u


u



l

u


u

n

l

l

l

® ® ®

n

n

n




n



n

n

n

n



n

n






n

n

l





l



® ® ® ®


n

®
n




® ¸

n

l






l

n

l

l





l

® ® ®

n





n

n

l



l



® ® ® ®


n

®
n




® ¸

n

l










l

n

l

l

l

® ® ®

n




n

n

l

l

u


u


l



® ® ® ®


n


®
n




® ¸





n

l

u


u



l

u


u

n

l

l

l

l


l



® ® ®

n

n

n





¸





n

n

l





l



® ® ®
®


n


®
n







® ¸

n

l






l

n

l

l

l

® ® ®





n

n

n




n

n

l



l



® ® ®
®

n


®
n







® ¸

n

l






l

n

l

l





l

® ® ®

n



® ®


n








n



n

n

® ® ®

¸ ¸
¸

¸ ¸




n

¸
n

l



l







¸



¸










® ® ®

®
® ®


®
®




®

¸

®


®



®


¸



¸








n








n









l

l

® ® ® ®


¸


















n

n
¸




¸




® ® ¸
¸




n


n


¸

n


n





‒ ®
®



n

n

n

n

n

n

n

n









n

n

n

n

n

n


n

l

l

n







® ® ® ® ®
¸ ® ®










n






n






¸


¸
¸






n

n
¸

¸ ¸





¸

n

l

l

l

l

n

l

u

u

u

l
¸

n


n



¸
¸








¸

¸

¸
¸






¸
¸




¸





¸




















n

n

n

n

n



n


n




¸

¸




n


n

¸


¸

¸

n

n

¸















¸

¸





n

¸
n

n



n







n

n








¸

n


l


l

l

l




n
¸




®




¸
¸

n



n



n



¸


¸





n

n





¸


n
¸

n


¸

¸
¸

¸




¸

¸





n ® ® ¸ ® ¸ ® ¸

n
¸
n
¸
n
¸
n










n

n




n

n




n

n

¸



n

n
¸
n

n

n
¸
n








n





n


n


n





n

l

l ®

n

¸
n



n

¸

n




l

l





l

l

n









n



n

n


n


® ® ® ®

l

l

l



l


l

¸ ¸
¸
l


¸ ¸
l

® ¸ ¸ ® ®








l

l

l

l

l















n




l
¸

l

l







® ®

®




¸







®





¸















® ¸ ¸ ® ¸
® ®













n




n






¸ ¸

n




n





























n


n
“ ”

l

l



















n



n
¸











n



n






l







l



n




n






l







l












¸
¸ ¸


¸ ¸
¸ ¸
¸ ¸
¸ ¸

¸





® ® ® ¸
® ® ® ¸


n

n





® ®




n

n


l
¸ ¸

l
¸ ¸

n

n



n

® ® ®
n




® ® ® ¸

n

n

® ® ® ®
¸ ®





















® ®

n

¸ ® ¸ ¸ ®
¸ ®
n

¸ ®




¸ ®


¸ ® ®
® ¸


¸ ® ® ¸
n


¸ ® ® ¸ ® ¸ ® ¸ ®
¸


n

l

u

u



® ®
l


¸ ® ¸ ¸ ® ¸ ®
®
n

l

¸ ® ® ®

l


n


¸ ® ® ®
® ¸

n


¸
®








® ® ® ¸
®




n


n

n

n

n

l

l

l

l

l


n

n

n

n

®
¸ ®










® ® ® ¸
® ®


® ®
® ¸ ® ¸ ¸ ®
¸ ®









n

n













n

n

l

l

l

n

n



® ® ® ®





® ® ® ®
®

¸



® ® ® ®
®
¸








¸















n




¸



n


n


n

n




n

n




n

® ® ® ®
®


¸
¸
¸


® ® ®
















¸

¸





n



® ®
¸





n


















¸




n
¸
n
¸


® ® ®

®









¸ ¸
¸
















n


n


















n


n




















® ® ®



®



¸ ® ¸ ® ¸
¸
¸ ®











n

l

l
¸








n





n








n

n
¸
n
¸


® ® ®

®




n

n
¸ ¸









®





®
®







n

® ¸ ® ® ®
¸
n

® ® ®
¸ ® ¸




“ ”















‒ ‒

® ® ® ®





























¸








¸






































¸








¸







¸ ® ®
n

n
¸

¸
® ® ®


¸

® ® ® ®







n
¸
n
¸
n
¸
n

n


n
¸
n

n

n

n
¸
n
¸
n






n





n





n









n







n
¸
n



n

n












n

n


n


n


n







n

n

n


n



n




n


l


l



n


¸

n

n

n











n

n

















n

n


¸
® ¸ ®












n
“ ”

n


l

l



n

























¸ ¸
















¸
® ¸ ®









n

n


n

n

¸ ®
¸ ®




® ¸ ¸ ® ®
¸

n


n

























n




n




n

n


n


n


n

® ® ® ®
®

® ® ® ®
® ® ®
® ¸ ¸ ® ®
®






n

l


l


n






n


® ® ® ®
® ® ¸ ® ¸







® ¸ ¸ ®
®

n

n

n

n




n

n



















¸


® ¸ ¸ ® ®

n




n




® ® ®
®

















n


n








n




n




n
















n

n

n


¸





















n

n

n




® ® ® ®
®







¸


n




n

n




n

n


n

















“ ”




‒ ‒





n



n


n




n

n



n





¸







¸

¸
¸
¸
¸
¸ ¸



















n








n



l











l


























n

n

n

n


l

l

l





n





l

l


n
















¸


















‒ ‒























n


n



n



n












n

n

n

















n


n









¸


® ®

®

®






¸
















n


n














® ® ®
®

n


n


® ® ®
®

¸



n

n

® ® ®






n


l


u



u




l


u



u


n


n


n


¸










¸ ¸

¸ ¸

® ® ® ® ®
® ®








n

n
¸
n

n

n


n

n





n


n




® ®

® ®

n




n

n

n



¸

¸ ¸
¸
¸
¸






¸
¸


n


n


¸

¸




n

¸
n




¸





¸








¸
















n

n

¸

¸


n

n


¸
¸
¸



n

¸

n





n

n

¸














¸







¸

n


n


n

l


l

l


l

l

n


®

¸




¸

n



n



n



¸

n



¸





n

n
¸
n

¸

¸




¸



¸






¸











¸
¸

¸




¸

¸


n ® ¸ ® ¸ ® ¸
n
¸
n
¸
n
¸
n






n

n

¸


® ® ®














® ® ® ®
® ¸


® ® ® ®
®





n

n

n

n

n

¸

n


® ® ®
® ®

n

n



® ® ®
® ®





¸ ¸

n

n

n




n

n

¸

n
¸

® ® ® ®
®

® ® ®






n

n



® ® ® ®
®


n

l

l

l

n


n

n



n



® ® ® ®
®

n


l
¸

l

n






n



® ® ® ®
®

n


l
¸

l

¸




¸
¸
¸ ¸







n

n

n

n

® ® ®

¸ ¸

¸ ¸




¸
¸ ¸ ¸








n

n






n







n










n

n





























































— ’

n

l

n

l ® ¸ ®

l






n

l

l

l

n

l

l




n

l

l

n

l ® ®




n

l

l

l

n

l






n

l

l

l

n

l







n

l

l

n

l






n

l

l

n

l

l






n

l

l

l

l

n

l







n

l

l

n

l







n

l

l

n

l




n

l

l

n

l

l ®











SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +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 transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks 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, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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 registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered 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 Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. 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 as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials.

The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should 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.
Disclaimer

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.
Legal Software Terms

Terms for Included Open Source Software

This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply. 1. This software was developed using ANTLR. 2. gSOAP Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright (C) 2001-2004 Robert A. van Engelen, Genivia inc. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

ii

PUBLIC

09/11/2006

HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems, Applications, Products in Data Processing Neurottstrasse 16 69190 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 use the STLport.org C++ library (STLport) and its documentation without fee. B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement. C) The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. D) Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG E) The Customer may distribute original or modified STLport 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 in accompanying permission notices are met: Coypright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems Inc. Copyright 1997 Moscow Center for SPARC Technology. Copyright 1999,2000 Boris Fomitchev Copyright 2001 SAP AG Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all

copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty. Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications. b) Support and Maintenance

09/11/2006

PUBLIC

iii

4 if this loss could have been avoided by observing this obligation. advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes. c) Exclusion of warranty As the STLport is transferred to the Customer on a loan basis and free of charge. d) Limited Liability A) Irrespective of the legal reasons. Technical data. without material defects or suitable for a specific application under third-party rights. SAP shall not be liable for the loss of data and its recovery. B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP. Acrobat.com/instguides iv PUBLIC 09/11/2006 . SAP shall only be liable for damage. if this (i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute. in particular by making backup copies at the minimum intervals recommended by SAP. 4. notwithstanding the other limitations of the present Art. consequential damage caused by a defect or lost profit. All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract. Software maintenance of the STLport therefore shall be not included. SAP cannot guarantee that the STLport is error-free. C) In the case of Art.000. due to the circumstances known to it at that point in time representing a typical transfer of the software.sap. PostScript. sales brochures. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer. E) The Customer shall take adequate measures for the protection of data and programs.SAP does not provide software maintenance for the STLport. the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract. F) The exclusion or the limitation of claims in accordance with the present Art. Documentation in the SAP Service Marketplace You can find this document at the following address: service. D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5.2 above. see SAP Note 854621. 4 includes claims against employees or agents of SAP. 4. SAP shall not be liable for indirect damage. including unauthorized operation. the Adobe logo. Adobe Document Services Adobe. and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries.

sap. for example. messages n Source code or syntax quoted directly from a program n File and directory names and their paths. These include report names. and menu options. pushbutton labels. www. database table names. screen titles. menu names. n Cross-references to other documentation or published works n Output on the screen following a user action. SAP Note 123456 n Words or characters quoted from the screen. and database tools Technical names of system objects.Typographic Conventions Example <> Description Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system. names of variables and parameters. for example. transaction codes. “Enter your <User Name>”. Arrows separating the parts of a navigation path. for example.com Shortcuts added to the URL of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note. upgrade. and names of installation. program names. menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to a URL. and key concepts of a programming language when they are surrounded by body text. SELECT and INCLUDE Keys on the keyboard ® Example Example Example /example 123456 Example Example EXAMPLE EXAMPLE 09/11/2006 PUBLIC v . These include field labels. for example. for example. for example.

Document History .sap. Caution Before you start the implementation. You can find the latest version in SAP Service Marketplace at the following internet address: service. make sure you have the latest version of this document. The following table provides an overview on the most important document changes.0 9/11/2006 Initial Version vi PUBLIC 09/11/2006 .com/instguides. Version Date Description 1.

. . . . . . .5 3. . . . . . . . . . . Requirements Checklist for the Central Services Instance . . . . . . . . .4 Chapter 2 2. . . . . . . . .3. . . .3.4 3. . . . .3 3. . . . . . . . . . .1. . . . . . . . . . . . . . New Features . . . . . . . . . . . . . . . . . . . . .6 Chapter 3 3. . . . . Installing the SQL Server Database Software . . . . . . . . .11 Chapter 4 4. . . .1. . . .3 3. . . . . . Hardware and Software Requirements . .1 3. . . . . . . . . . . . . . . . . . . . .1. .1 Introduction . . .3 1. .6 3. . . . . . . . . . . . . . . . . . . . . . . . Requirements Checklist for the Database Instance . . . .2 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Configuration . . . . Performing a Domain Installation Without Being a Domain Administrator Preparing the SAP System Transport Host . . . . . .1 3. . . . Information Available on SAP Service Marketplace Naming Conventions . .3. . . . . . . . . . . . . . . . . . .3. . .1 3. . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . .3 3. . . . . . . . .1 2. .7 3. . . .3. . . . . . . . . . . . . . . . Granting User Rights for the Installation . . . .10 3. Requirements Checklist for the Dialog Instance . . Distribution of Components to Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 2. . Installing the Java Development Kit . . .2 3. . . . Requirements Checklist for a Distributed System . . . . . How to Distribute Instances to Hosts . . . . . . 09/11/2006 PUBLIC vii . . .9 3. . 1 1 2 2 4 5 5 7 8 9 13 15 20 21 23 23 24 25 26 27 28 29 30 32 33 33 34 34 36 38 39 40 41 42 45 45 Planning . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . Multi-Language and Unicode Support . . . . . . . . . Basic System Variants for SAP Solution Manager . . . . . . . . . . . . . . . . .3. . . . . . Reducing the Size of the File Cache . . . . . . . . . SAP Directories . . . . . . . . . Checking for the Windows File System . . . . . . . . . . . . .Table of Contents Chapter 1 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . Running Adobe Document Services on Non-Supported Platforms Preparation . . . . SAP Notes for the Installation . . . . . . . . . . . . . . . Running the Prerequisite Checker in Standalone Mode (Optional) . . . Installing the SAP Front-End Software . . .4 3. . . . . Checking the Windows Domain Structure . . . . . . . . . .1 1. . . . . . . .1 2. . . . . . . . . . Requirements Checklist for the ABAP Central Services Instance .3 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.1. Requirements Checklist for a Central System . . . . Basic SAP System Parameters . . . . . . . .2 1. . . . . . . . . . . . . .4 2.2 2. . . . . . . . . . . . . .5 3. . . . . . . . . . Requirements Checklist for the Central Instance . . . . . . . Preparing the Installation DVDs . .2 3. . . .1. . .8 3. .2 3. Downloading Installation DVDs from SAP Service Marketplace (Optional) Installation . . . . . . . .

. . . . . . . . . . . . . . 45 Installing the SQL Server Database Software Manually . .6 Chapter 5 5.4 4. . .1. . Configuring Remote Connection to SAP Support . . .1 5. . . . . . . . . . . . . . . . . . .12. . . . . . . .10. . . . . Mapping SAP System Users to Windows Users for Single Sign-On . . . . . . . . . . 66 Starting SAPinst GUI Separately (Optional) . . . . . . . . . 62 Using SAPinst GUI .1. . . . . . . . . . . . . Preparing SAP GUI and SAP Logon for Single Sign-On . . . .2. . . . . . .3 4. . . . . . . . . . . . . . .11 5. . . . . Preparing the Central Instance . . . . .4 5. . . . . . .14 Chapter 6 6. . . . . . . .1 4. . . . . . . 71 71 72 74 74 75 75 76 78 79 80 81 82 83 84 85 86 87 88 89 89 89 91 93 95 95 96 97 viii PUBLIC 09/11/2006 . . . . .1 4. . . . . .11. . . . 55 Preparing your System for an Java Add-In Installation . . . .7 5. . . . . . . .13 5. . .11. . . . . . . . . . . . . . . . . . Mapping SAP Users to Windows Users . . .2 5. . . . . . Single Sign-On with Microsoft Kerberos SSP . .1 6. . . . . . Installation of Multiple Components in One Database (Optional) . . .10 5. . . . .1 4. 56 Running SAPinst on Windows . . .3 4. . . . . 47 Installing the SQL Server 2000 Database Software on 64-Bit Manually . . . . . . . . . . . . . Installing the SAP Online Documentation . 49 Installing the Corrected MS SQL Server Collation for MS SQL Server 2000 . . . Starting and Stopping the SAP System .1 5.11. . . . .2 4. . . . .2 Installing the SQL Server Database Software with SQL4SAP . . .1 5. . . . . . .8 5.3. . .1 5. . . . . . . . . . . . . . .4 5. . . . . Configuring SAP Solution Manager . Installation Check and Quick Tests for Adobe Document Services . . . . . . . . . . . . . . . . . .1. .1. Performing Initial ABAP Configuration . . . .10. . . . . . . . Configuring the SAP Front End . . . . .2 5. . . . . .2 4. . . . . . . . . .3. .3 5. . . 64 Interrupted Installation with SAPinst . . . . . . .3. .2 4. .2. . . . . . . . . .5 4. . . . . . . . . . . .9 5. . . . . . . . . .5 4. . . . . .12 5. . .3. . . . . . . . . . .1. Database Installation for Multiple Components with MS SQL Server Default or Named MS SQL Server Instances . . . . . . . . . . Installing the SAP License . . . . . . . . . . . Activating Single Sign-On for the SAP Logon . . 55 Installing an SAP System Using SAPinst . . . . . . . . . . . . . . . Single Sign-On with Microsoft Lan Manager SSP . . . . . . . . . . . . . . . .2. . . . . . . .4. . . . Applying the Latest Kernel and Support Packages . . . . . .3 4. 46 Installing the SQL Server 2000 Database Software on 32-Bit Manually . 51 Installing the SQL Server 2005 Database Server Software Manually . . . Logging On to the SAP System . .3 5. .12. . . . Assigning Roles to Users ADSUSER and ADS_AGENT . .2. . .3. . . . . . . . . . .10. . . . . . . . . . . . . . . . . . . . . . . . Checking the SAP Java Documentation . . . . . . . . . . . .2 4. . . . . . . . . . . 52 Installing the SQL Server 2005 Native Client Software Manually . . . . . . . . . . . . .4 4. . . . . . . . . . 67 Post-Installation . . . . . . . . . . . . . . . . . Performing a Full Installation Backup . . . . . . . Additional Information . . . . Preparing the Application Server for Single Sign-On . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . .2 5. . . . .1. . . . . . . . . . . . . . . .1. . . . . . . .5 5. . . . . . . . . . . . . . . . . . . . . . . . . . . .3 5. . Ensuring User Security . . . . . . . . . . . Post-Installation Steps for Adobe Document Services . . . 65 Performing a Remote Installation with SAPinst (Optional) . . . . . . . . . . . . . . . . .6 5.1 6.2. . . . . . . 56 Installing a Java Add-In for an Already Existing Solution Manager ABAP System with SAPinst (Optional) .3. . .2 5.11. . . . . . . .

. . . . 111 . . . . .3. . . . . . .1 6. . . .6 6. . . . . . .3. Clustering the SQL Server 2000 Database Software in a 64-Bit System . . .1. . . . . . . . . .1. . . . . . . . . . . . .9 6.1. . .1 Chapter 7 7. . .11 6. . . . . . . . . . Post-Installation . . . . . . . .4 7. . . . . . . . Planning . . . Starting and Stopping the SAP System in an MSCS Configuration . . . . . . . . . . . . . . . . . . . 99 . . Preparing the Active Directory (Optional) . . . . . . . . . .5 7. . . Distribution of Components to Disks for MSCS . .1. .3. . .4 7. . . .11 7. . . . Moving MSCS Groups . . Preparation . . . . 109 . . Configuring User Management to Use an LDAP Directory (Optional) Entries in the Services File Created by SAPinst . .3. .2 Integration of LDAP Directory Services (Optional) . . . . . . .7 7. 106 . . . . . . . Checking the Status of the Enqueue Replication Server with ENSMON Monitoring the Lock Table During Failover with ENQT . .10 6.5 7. . Clustering the SQL Server Database Software . 101 . . . . . . Mapping Host Names to IP Addresses for MSCS . .4 6. . . . . . . Rebooting During the Installation or Conversion for MSCS . . . . . . . . . . . . . . . . . . . . . IP Addresses in an MSCS Configuration . . . . . . .3 7. .4. . .3. . . . . . . . . . . . . . . . . .2 7. . . . . . . .3. . . Post-Installation Checks for Enqueue Replication Server . Deleting an SAP System . . . . . Installation .2. . . . . . . . . . . . . . . . . . . . . . . . .12 6. . . .2. . . . Installing the Central Services Instance (SCS) . . .3 7. .1. . . .4. . .1. . . . .3. . . . . .4. . . . 105 . . .1. . . . . . . . . . Installing the Database Instance .7 7.3. . Enqueue Replication Server in an MSCS Configuration . . . . . . . Preparing User Management for an External ABAP System . 112 . . . . . Configuring the Additional MSCS Node . .9 7.3. . . .2 7. .1 7. .4 7. . .3. . .3 7. . . . . . . . . .1 7. . . .2. . . . . . . . . . . . . . . . Clustering the SQL Server 2005 Database Server Software . . . . . . . . . . . . . .2 7. . . . . . . . . Troubleshooting with SAPinst . .7 6. Assigning Drive Letters for MSCS . . . . . . . . . . . . .8 7. Directories in an MSCS Configuration . . . . . SAP System Components in an MSCS Configuration . . . . . . . . . . . . . . .3. . . .8.1 7. . . . . . . . Troubleshooting . . . . . . . . . . . . . Clustering the SQL Server 2000 Database Software in a 32-Bit System . . . . . . . . . . Manually Granting User Rights for the Installation . .1 7. . .6. . . . . . . . . Obtaining IP Addresses for MSCS .12. 112 . . . . . . . . .8 6. . . . . . . . . . . . . Running SAPinst to Delete an SAP System . .3 7. . . . . . 105 . . . .1.3 7. . . 106 . . . . . . .2. Checking Hardware and Software Requirements for MSCS . . . . . . . . . . . 115 116 116 119 120 122 122 126 128 130 130 131 131 132 133 133 135 137 141 142 142 142 143 144 144 146 147 147 148 148 149 149 150 09/11/2006 PUBLIC ix . . Installing the Dialog Instance . . . .1 7. . . . . . . .2 7. . . . .5 6. . .2. . . . . . . . High Availability with Microsoft Cluster Service . .2 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 6. . . . .1 7. . . . . . . . . . .3. . . . . .6 7. . . . . . . Checking the Mapping of Host Names for MSCS . . . . . . . . . . . . . . . . . . . . . . .10 7. . . . . . . . . . . . . . . . . 102 .3. . . . Installing an Enqueue Replication Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Central Instance . . . . .3. . . . 108 . . . . . . . .1. .4. . . . . Automatic Creation of Accounts and Groups . . . Installing the Central Services Instance for ABAP (ASCS) . . . . . . . .1. . . . . . . Configuring the First MSCS Node . . .1 7. .6 7. . . . SAP System Security on Windows . . .2 7. . . . . . . . . . . . . . . .

. . The Main SAP Documentation Types . . 153 153 x PUBLIC 09/11/2006 . . . . . . . . . . . .Chapter A A. . . . . . . . . . . . . . . . . .1 Reference . . . . . . . . . . . . . .

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 change the default names of the Java users J2EE_ADMIN.com/netweaver. l Upgrade the old database version to the downward-compatible new version. you must install a SAP component or perform a system copy using a downward-compatible database as follows: l Install the component with the old proposed database version. For more information about the technology provided by SAP NetWeaver. This password is used for all user accounts and for the secure store key phrase. For more information about SAP Solution Manager. see SAP Service Marketplace at service.sap. n SAP system installations should only be performed by SAP Technical Consultants who are certified for your operating system. 09/11/2006 PUBLIC 1 .1 New Features Here you can find the new features in this release. see SAP Service Marketplace at service.sap.0 SR1 (Solution Manager for short) is based on SAP Solution Manager 4. we only support the installation for database versions proposed by the installation tool. SAP Solution Manager 4. J2EE_GUEST and SAPJSF during the input phase of the installation. n For downward-compatible releases of DB/OS platforms for SAP products.0 SP06 and on the underlying technology of SAP NetWeaver 2004s SP08. 1. and the SAP system that you are installing. Constraints You need to consider the following constraints before you start your installation: n You must only use the SAP installation tools according to the instructions and for the purposes described in the SAP installation document. n You can install the Java Add-In to an already existing ABAP system. These releases are downward-compatible with earlier SAP system releases. n You assign one Master Password to all users created by SAPinst.1 Introduction 1 Introduction This document explains how to install SAP Solution Manager 4.com/solutionmanager.0 SR1. Improper use of the SAP installation tools can damage files and systems already installed. Therefore. n You can uninstall an SAP system or an SAP component with the SAPinst service Uninstall ‒ System / Standalone Engines / Optional Standalone Unit. Note that for already shipped SAP components. SAP plans to regularly release the newest database (DB) and operating-system (OS) versions of SAP products. your database.

com/notes. A separate browser windows opens and the SAP Note is displayed.Standalone Engines & Clients ® Installation Guide .2 SAP Notes for the Installation You must read the following SAP Notes before you start the installation. which is the same for all databases. 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.0 / SAP Solution Manager 4. available at service.2 Introduction SAP Notes for the Installation Area Description n SAPinst initializes most of the input parameter fields with default values. Operating Systems Area Description Support of Operating Systems Documentation See the Product Availability Matrix (PAM) on SAP Service Marketplace at service. 2 PUBLIC 09/11/2006 . These SAP Notes contain the most recent information on the installation. The installation of a standalone gateway is now covered in a dedicated installation guide. as well as corrections to the installation documentation.sap. Area Description SAP Notes You can now access SAP Notes directly in SAP Service Marketplace from your PDF.1 1.0 / 4.com/installnw2004s ® Installation .sap. Installation DVDs You start the installation from a single Installation Master DVD. SAP Software on UNIX and Windows: Checking OS Dependencies 855498 1.sap.0 SR1 Installation Installation Prerequisite Checker Central installation note for SAP Solution Manager 4.3 Information Available on SAP Service Marketplace More information is available as follows on SAP Service Marketplace. you can change each default value by choosing to revise the related parameter section in the Parameter Summary screen before you start the processing phase of the installation. SAP Notes for the Installation Title Description 918078 SAP Solution Manager 4.Gateway on <platform> Standalone Gateway Installation 1. If required.0 SR1. Place the cursor on the SAP Note “<number>” and double-click.com/platforms ® Product Availability Matrix.

0 SR1 Master Guide SAP Solution Manager 4.sap.sap.com/installNW2004s ® SAP Components ® SAP Solution Manager ® Release 4.0 service.sap.sap.1 1.com/installNW2004s ® Configuration ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Solution Life Cycle Management by Key Capability ® SAP NetWeaver Problem Analysis Guide (PAG) help.com/instguides Upgrade Guide ‒ SAP Solution Manager 4.0 ® SAP Components ® SAP Solution Manager ® Release 4.sap.0 Components ® SAP Solution Manager ® Release 4.com/nw2004s General Quick Links Description Internet Address help.com/installNW2004s service.0 service.com/instguides service.com/sizing service.sap.com/platforms service.com/instguides Master Guide ‒ SAP Solution Manager 4.com help.0 <OS> <Database> Configuration Guide ‒ SAP Solution Manager 4.3 Introduction Information Available on SAP Service Marketplace Documentation Description Internet Address Title service.0 service.sap.com/instguides ® SAP Components ® SAP Solution Manager ® Release 4.0 SR1 Media List ‒ SAP Solution Manager 4.sap.sap.0 service.sap.com/notes service.com/unicode service.com/nw2004s service.sap.0 ® SAP Components ® SAP Solution Manager ® Release 4.com/ha SAP Help Portal SAP NetWeaver Library in SAP Help Portal SAP Notes Released platforms and operating systems Unicode SAP systems and their availability System sizing (Quick Sizer tool) High availability 09/11/2006 PUBLIC 3 .sap.sap.sap.0 Upgrade to SAP Solution Manager 4.com/instguides ® SAP List of media for installation or upgrade for SAP Solution Manager 4.sap.sap.0 SR1 Front End Installation Guide (this guide is also available on the Presentation DVD) Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP NetWeaver 2004s Migration Guide for Solution Manager Diagnostics SAP NetWeaver 04s SP Stack <current stack> Advanced Supportability Setup Guide for Solution Manager Diagnostics SAP NetWeaver 04S Post-Installation Guide ‒ System Landscape Directory SAP NetWeaver 2004s SAP NetWeaver Problem Analysis Guide (PAG) Configuration of SAP Solution Manager Front End installation Homogeneous and heterogeneous system copy for SAP systems based on NetWeaver 2004s Migration Guide Solution Manager Diagnostics Setup Advanced Guide Solution Manager Diagnostics 04s Installation of the System Landscape Directory (SLD) SAP NetWeaver Problem Analysis Guide (PAG) ® SAP Components ® SAP Solution Manager ® Release 4.sap.com/instguides service.0 service.

com/sp-stacks service. n ABAP+Java system refers to the two stacks (ABAP and Java) of SAP Solution Manager. Information on SAP Support Package Stacks SAP Solution Manager Note For information on Windows operating system security.com/security Security . 4 PUBLIC 09/11/2006 . Variables Variables <SAPSID> <sapsid> <DBSID> <dbsid> <host_name> <INSTDIR> <DVD_DIR> <OS> <SCHEMA_ID> Description SAP system ID in uppercase letters SAP system ID in lowercase letters Database ID in uppercase letters Database ID in lowercase letters Name of the corresponding host Installation directory for the SAP system Directory on which a DVD is mounted Operating system name within a path Database schema ID The following example shows how the variables are used: .4 Introduction Naming Conventions Description Internet Address service.sap. the following naming conventions apply: Terminology n SAP system refers to SAP Solution Manager. Example Log on as user <sapsid>adm and change to the directory \usr\sap\<SAPSID>.4 Naming Conventions In this documentation.microsoft. see: www.sap. If your SAP system ID is C11.com/security service.sap. log on as user c11adm and change to the directory \usr\sap\C11.com/solutionmanager 1.1 1.

You decide whether you want to use Unicode and multi-language support [page 20]. 2. You plan how to distribute the instances to hosts [page 7]. The ABAP central services instance is named ASCS instance. 3. 09/11/2006 PUBLIC 5 . if required. see High Availability with Microsoft Cluster Service [page 115]. and the database instance. If you want to use Adobe Document Services (ADS). you can install one or more dialog instances. 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. You plan your system configuration [page 8]. 5. you check what you have to do in case your platform is not supported for ADS [page 21]. An ABAP+Java System can be the result of n an ABAP+Java installation n a Java Add-In installation for an already existing ABAP system Mandatory instances of an ABAP+Java system are the central instance. The ASCS is only available for a high availability installation. You identify basic SAP system parameters [page 15]. Only valid for: HA (MSCS) If you want to perform a high-availability installation with Microsoft Cluster Service (MSCS). End of: HA (MSCS) You have to complete the following planning activities: 1. 4. . Optionally. Note The Java central services instance is named SCS instance.2 Planning 2 Planning This section tells you how to plan the installation of your SAP system. the central services instance. You can then operate both the ABAP application server and the J2EE Engine on the SAP system.1 Basic System Variants for SAP Solution Manager The following section provides information about the basic SAP system variants for SAP Solution Manager and about the possibilities to distribute SAP instances within them SAP Solution Manager is an ABAP+Java system.

all instances reside on one host. see SAP System Components in an MSCS Configuration [page 116].1 Planning Basic System Variants for SAP Solution Manager . Only valid for: HA (MSCS) For more information on how to distribute a high-availability Solution Manager system. End of: HA (MSCS) Figure 1: Minimum System Distribution (Central System) For a minimum system distribution. 6 PUBLIC 09/11/2006 . Note Each instance can reside on a separate host.2 2.

n Distributed system on several hosts You perform the following steps: 1.2 2. on the dialog instance host(s) The following graphic shows how to distribute your instances to several hosts: 09/11/2006 PUBLIC 7 . You use SAPinst to install the SAP instances as a: n Central system on a single host You run SAPinst and install all instances on one host. You run SAPinst and install the: l Central services instance (SCS) on the global host l Database instance on the database host l Central instance on the central instance host l Dialog instance(s). 2. each instance resides on a separate host. You specify or create a shared transport directory.2 Planning How to Distribute Instances to Hosts Figure 2: Maximum Distribution for a Distributed System For a maximum system distribution. 2. if required.2 How to Distribute Instances to Hosts The following provides information on how you can distribute the SAP instances for the different SAP system variants.

8 PUBLIC 09/11/2006 .2 2. all Windows account and user information is stored locally on one host and is not visible to any other hosts in the system. In a local installation.3 System Configuration 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]. such as: l The set of applications to be deployed l How intensively the applications are to be used l The number of users You decide whether to perform a domain or local installation: n l Local installation You need to be Local Administrator of the machine involved. you can perform a local installation.3 Planning System Configuration Figure 3: Distribution of Instances in an ABAP+Java System 2. n You and your hardware partner work out a high-performance configuration based on sizing information that reflects the system workload. If the SAP system is to run on a single machine.

2 2.3

Planning System Configuration

.

Caution

If you install a distributed system as a local installation, this can lead to authorization problems for the operating system users <sapsid>adm and SAPService<SAPSID>, as well as to problems with the transport directory, which is usually shared by several SAP systems. Therefore, SAP does not support a local installation for a distributed system and recommends you to install a distributed system 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 installation You need to be Domain Administrator of the domain involved, and all machines in the system must belong to the same domain. In a domain installation, the user information is stored centrally on the domain controller and is accessible to all hosts in the system. If the system is to be distributed across more than one machine, SAP strongly recommends you to perform a domain installation to avoid authorization and support problems. .
Caution

If for any reason, you are not granted domain administrators rights, you can perform the installation as a domain user who is a member of the local administrators group. However, the domain 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 the Installation [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 system are automatically created. However, during the installation procedure you have to explicitly specify where these directories are to be located, that is, on which drives or disks they must reside. The assignment of the directories to drives and corresponding disks fundamentally affects the security and performance of the system 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 growth n The data is secure n Performance is good

09/11/2006

PUBLIC

9

2 2.3

Planning System Configuration

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 SQL Server program files, tempdb files, SAP data files and transaction log files. The log files record all the changes made to the database to enable restore and recovery. The tempdb holds all temporary tables and stored procedures. The data files contain the data for the SAP system. n SAP Data Files The 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 same disk 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 File The transaction log for the database is created by default in the directory\<SAPSID>LOG1. The log file is called <SAPSID>LOG1.ldf and requires a minimum of 1 GB space. You can change the default directory of the transaction log directory. The transaction log file records all the changes made to the database and, if required, enables modifications to be redone or undone. It plays a crucial role when the database has to be restored due to database damage or media failure. For this reason it should be stored very securely. SAP recommends the use of RAID 1 which implements hardware-based mirroring.

10

PUBLIC

09/11/2006

2 2.3

Planning System Configuration

n Program Files The 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 log files 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 particularly recommended because the tempdb is frequently accessed during SQL Server operation and could otherwise affect performance. .
Note

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

Distribution of Main Directories to RAID Array

Figure 5:

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

09/11/2006

PUBLIC

11

Distribution of Components to RAID Arrays Figure 6: Distribution of Directories to Arrays Array 1 Array 2 \Program files\Microsoft SQL Server \TEMPDB \<SAPSID>DATA1 \<SAPSID>DATA2 \<SAPSID>DATA3 Array 3 Optimizing Performance \<SAPSID>log1 If you wish to optimize performance. isolate the tempdb on a separate. fast disk.3 Planning System Configuration . fast disk.2 2. but must both be located on the same array. 12 PUBLIC 09/11/2006 . A further option for improving performance is to place the Windows paging file on a separate. The transport directory does not necessarily have to reside on the central instance host. Note The SAP kernel files and the transport directory can be assigned to any of the arrays depicted. This improves performance significantly because the tempdb is continually accessed during MS SQL Server operation.

All instances of an SAP system access this directory on the global host using the Universal Naming Convention (UNC) path. In both cases. . the \usr\sap directory contains l copies of the SAP software l local (instance-specific) data. the UNC pathes are used as follows: n n \\<SAPGLOBALHOST>\sapmnt to access global directories \\<SAPLOCALHOST>\saploc to access local instance-specific data 09/11/2006 PUBLIC 13 . Changes in SAP profiles can also affect the disk space. the \usr\sap directory is created on the: n Global host and shared with the name sapmnt On global hosts.2 SAP Directories During the SAP system installation. n Local host and shared with the name saploc.2 2. The following graphic shows how the physical directory \usr\sap is shared on the global host and in a distributed installation.3 Planning System Configuration 2. the \usr\sap directory contains l general SAP software l global and local (instance-specific) data. On local hosts.3. Note Since SAP traces for the instance are created in \usr\sap. make sure there is sufficient space available in this directory. The executables on the local host are replicated from those on the global host each time the local instance is started.

The global data (binaries) is stored in the global directories on the global host and physically exists only once for each SAP system. \\<SAPGLOBALHOST>\sapmnt. Every time an instance starts.3 Planning System Configuration 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 host has the SAP\<SAPSID>\SYS directory structure. the SAP copy program sapcpe compares the binaries in the <platform>-directory on the global host and the binaries in the exe-directory on the application server. If the binaries in the exe directory are elder than those in the <platform>-directory. where SAPGLOBALHOST is replaced by the SAP system with the name of the global host. sapcpe replaces them with the newer version of the global host.2 2. 14 PUBLIC 09/11/2006 . Other application server access the data using the UNC path.

4 Basic SAP System Parameters The tables below list the basic system parameters that you need to determine before installing your SAP system. In a distributed system. you write down the values that you plan to use. the parameters SAPGLOBALHOST and SAPLOCALHOST have different values.2 2. the Message Port Number. interacts with the global host. the parameters SAPGLOBALHOST and SAPLOCALHOST have the same values on the global host with an SCS instance. 2. for example. . Note In the column “Enter Your Values”. 09/11/2006 PUBLIC 15 . For all other SAP system parameters.4 Planning Basic SAP System Parameters Figure 8: Directory Structure for a Distributed ABAP+Java System The above graphic shows how the distributed instances. Distributed instances use SAPGLOBALHOST to access global data on the global host In a distributed system. use the F1 help in the SAPinst dialogs.

see SAP Note 611361. That is.. Caution Do not use 43.. The instance number must be unique on a host. You cannot change the SAP system ID after the installation. . Caution . consisting of a two-digit number from 00 to 97. The database ID <DBSID> can be different from the SAP system ID. 89 for the instance number because: n 43 is used by MSCS n 60 is used by iSCSI n 89 is used by Windows Terminal Server Name of Instance Host Instance Host: . if more than one SAP instance is running on the same host. Make sure that your SAP system ID: n Is unique throughout your organization n Consists of exactly three alphanumeric characters n Contains only uppercase letters n Has a letter for the first character n Does not include any of the following. For more information about the allowed host name length and characters.. 16 PUBLIC 09/11/2006 . 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> .4 Planning Basic SAP System Parameters 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. 60. To find out the host name. Instance Number: Technical identifier for internal processes.. these instances must be assigned different numbers... Parameters Relevant for the System Landscape Parameters Description Enter Your Values Instance Number . Choose your SAP system ID carefully. .2 2. Host name of the specific instance. The <DBSID> identifies the database instance... open a command prompt and enter hostname.

ABAP RFC User. Windows Domain SAPinst creates the <sapsid>adm and SAPService<SAPSID> users . The Java message server is configured in the SCS instance profile. The external message server port uses the parameter rdisp/msserv with default value 36<nn>. see Granting User Rights for the Installation [page 34]. Both message server ports are configured in the default profile. Make sure that you have domain administrator rights before you start the installation. Password 09/11/2006 PUBLIC 17 . If not. For more information about the parameters used for internal and external message server ports. It has the required special administrator rights. Make sure that all message server port numbers on the same host are unique. where <nn> is the instance number of the ABAP message server instance. For more information.. The ABAP message server uses both the internal and the external message server ports. you have to create these users manually before starting the installation.. so that the external port is not open. you can use user SAP*.4 Planning Basic SAP System Parameters Parameters Description Enter Your Values Message Server Port . where <nn> is the instance number of the ABAP message server instance. ABAP Message Server Port There is an external message server port using the parameter rdisp/msserv and an internal message server port using the parameter rdisp/msserv_internal. The message port number must be unique for the SAP system on all hosts. The internal message server port uses the parameter rdisp/msserv_internal with default value 39<nn>. Caution . in the domain specified. Alternatively. the default port number is used.. where <nn> is the instance number of the SCS message server instance. The parameter rdisp/msserv is set to 0.. Port number of the SAP Message Server: If you do not specify a value... The internal message server port uses the parameter rdisp/msserv_internal with default value 39<nn>. . see SAP Note 821875. The user DDIC is normally used for the RFC logon ABAP RFC user.2 2. Java Message Server Port The Java message server only uses the internal message server port.

If required.. you can choose another user name according to your requirements. Administrator Name: SAPinst sets the user name J2EE_ADMIN by default.. The following naming convention applies: 5<instance_number>00. The user must exist on the central ABAP system that is used for the central user management.. Communication User Name: This user is used for the communication between the ABAP and the Java part of an ABAP+Java system.. you can choose another user name. SAPinst sets the user name SAPJSF by default. Cryptography Level: Java Cryptography Extension (JCE): The SAP Java Libraries need the JCE files for strong cryptography.. . If the SAP User Management Engine (UME) is configured against the user management of an ABAP system.. the SLD HTTP Port is 50100. If required. If required. 18 PUBLIC 09/11/2006 . SAPinst sets the following user names by default.. n For the Java part of an ABAP+Java system: J2EE_ADMIN n For a Java system: Administrator.4 Planning Basic SAP System Parameters Parameters Description Enter Your Values Java users and passwords .2 2.. The HTTP port of the Java system where the SLD is installed. . you can revise all these default user names at the end of the input phase of the installation using the Parameter Summary screen. you can choose other user names. Cryptography Level ‒ Java Cryptography Extension (JCE) Parameters Relevant for the Connectivity to System Landscape Directory Parameters Description Enter Your Values SLD HTTP Host SLD HTTP Port The host name of the System Landscape Directory (SLD) . If required. For users who do not belong to a company or who have registered as company users and are pending approval. For more information see Installing the Java Development Kit [page 40]. Example If the instance number of your Java system is 01. Guest users belong to the default group Authenticated Users. . Guest Name: SAPinst sets the user name J2EE_GUEST by default. enter the name of the ABAP user that is defined as administrator for this system.

you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation. .4 Planning Basic SAP System Parameters Parameters Description Enter Your Values SLD Data Supplier User and password n If you want to install a local SLD.. . Base directory for the SAP system.. n If you want to connect your system to an existing central SLD. Recommendation We recommend that you name this user SLDDSUSER SLD ABAP API User and password n If you want to install a local SLD. Recommendation We recommend that you name this user SLDAPIUSER . SAPinst creates this user during the installation.. Do not add <SAPSID> as subdirectory because the system adds this directory automatically. . n If you want to connect your system to an existing central SLD... Example If you enter D:. . SAPinst creates this user during the installation. you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation. RFC User. .. Password SLD Gateway Host SLD Gateway Instance Number SAP System Client The ABAP RFC user of the SLD The host on which the gateway instance of the SLD is running The instance number of the gateway instance of the SLD The client in which the ABAP RFC user exists Parameters for SAPDATA Drives Parameters Description Enter Your Values Installation drive ... . the system adds the directory D:\usr\sap\SAPSID.. ...2 2... .. 09/11/2006 PUBLIC 19 .

In an MSCS environment. In addition to global character coverage. 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. enter the virtual host name. the Unicode standard is unique among character set standards. l Unicode is the recommended system type for all SAP systems that deploy Unicode-enabled solutions and components.5 Planning Multi-Language and Unicode Support Parameters Description Enter Your Values . The widespread adoption of Unicode over the last decade has made text data truly portable and formed a cornerstone of the Internet..5 Multi-Language and Unicode Support This section describes SAP support for multiple languages with or without Unicode: n Unicode systems l The default for all new installations is Unicode. l Unicode (and the parallel ISO 10646 standard) defines the character set necessary for efficiently processing text in any language and for maintaining text data integrity. End of: HA (MSCS) 2. because it also defines data and algorithms for efficient and consistent text processing. Note If you install a subsequent SAP system. WebDynpro applications) u SAP ABAP systems that communicate with Java components (for example via the SAP Java Connector) 20 PUBLIC 09/11/2006 . This enables high-level processing and ensures that all compliant software produces the same results. SAPinst uses the installation drive where the saploc share points to. Dependencies For a named instance enter <hostname>\<instance_name>. the saploc share already exists and you cannot select the installation drive. Parameters Relevant for the Database Parameters Description Enter Your Values Database instance name MS SQL Server instance name You can also specify a remote database instance. Only valid for: HA (MSCS) ..2 2.

More Information For more information. install an additional standalone AS Java on a platform supported by ADS. For information about code page support of SAP JAVA Connector refer to SAP Note 794411. n Non-Unicode systems SAP supports more than 30 languages in non-Unicode systems. in particular on 64-bit platforms. only certain combinations of languages can be used without restrictions. you must activate the default language settings once. For more information on installing languages. see Performing Initial ABAP Configuration [page 75] ® Installing Languages. see SAP Note 925741.2 2. see SAP Notes 79991 and 73606. n If you want to use languages other than English. 2. Note For information about restrictions in non-Unicode system installations refer to SAP Note 838402. Procedure To use ADS in SAP landscapes on non-supported platforms. Integration The default setup of the system is Unicode. n If you want to use English only.6 Planning Running Adobe Document Services on Non-Supported Platforms .6 Running Adobe Document Services on Non-Supported Platforms Adobe document services (ADS) are currently not supported to run natively on all platforms supported by SAP systems based on SAP NetWeaver. but due to the technical limitations of non-Unicode code pages. 09/11/2006 PUBLIC 21 . For more information. you must install them and activate the language settings.

.This page is intentionally left blank.

The Prerequisite Checker provides information about the requirements that you need to meet before you start the installation.3 Preparation 3 Preparation You have to complete the following preparations: 1. 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 SAP system. you perform a domain installation without being a domain administrator [page 36]. 3. 6. 4. . 5. you can run the Prerequisite Checker standalone [page 24]. 10. 2. If required. 9. we recommend that you consult the requirements checklists tables. always check SAP Note 855498. 7. the requirements might change. The following preparation activity is optional: Preparing user management for an external ABAP system [page 102]. You install the Java Development Kit [page 40]. You install the SAP front-end software [page 39]. you download the installation DVDs from SAP Service Marketplace [page 42]. l Integrated in SAPinst (mandatory): SAPinst automatically runs the Prerequisite Checker when you install your SAP system. You prepare the installation DVDs [page 41]. If required. 8. Depending on the amount of data involved. If required. You check for the Windows file system [page 33]. 3. l For the most recent updates to the Prerequisite Checker. You check the hardware and software requirements [page 23] using the Prerequisites Checker. you grant user rights for the installation [page 34]. n In addition. you reduce the size of the file cache [page 34]. 09/11/2006 PUBLIC 23 . Note l The values that are checked by the Prerequisite Checker apply to the installation of development systems or quality assurance systems. If required. You prepare the SAP system transport host [page 38].1 Hardware and Software Requirements n You check the hardware and software requirements for your operating system (OS) and the SAP instances using the Prerequisite Checker tool. 11. For example. You check the Windows domain structure [page 33]. which provide values for the installation of development systems or quality assurance systems. it checks the requirements for the different installation services.

3 3. which is available on SAP Service Marketplace [page 2]. 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. Note . n For supported operating system and Java (JDK/JRE) releases. Enter the required parameters when prompted in the SAPinst dialogs. 3.1 Preparation Hardware and Software Requirements n To get precise sizing values for production systems.sap. 2. SAPinst automatically starts the Prerequisite Checker and checks the hardware and software requirements in the background.1 Running the Prerequisite Checker in Standalone Mode (Optional) Before installing your SAP system. You enter information about your planned system and the tool calculates the requirements. .com/pam. 2. see Planning your System Landscape in the Master Guide ‒ SAP NetWeaver 2004s. When installing your SAP system. On the Welcome screen. Process Flow 1. we recommend that you check the hardware and software requirements checklists for the following system variants: n Central System [page 25] n Distributed System [page 26] 3. 24 PUBLIC 09/11/2006 . .com/sizing. who can analyze the load and calculate suitable hardware sizing. n Make sure that the host name meets the requirements listed in SAP Note 611361. l You contact your hardware vendor. Procedure 1. n Contact your OS vendor for the latest OS patches.1. You start SAPinst [page 56]. you can run the Prerequisite Checker in standalone mode to check the hardware and software requirements for your operating system (OS) and the SAP instances. If required. you run the Prerequisite Checker standalone [page 24] to check the hardware and software requirements. In addition. choose <SAP System> ® Additional Software Lifecycle Tasks ® Additional Preparation Tasks ® Prerequisites Check. see the Product Availability Matrix on SAP Service Marketplace at service. you might experience problems when working with the SAP system. For more information. Recommendation We recommend that you use both the Prerequisite Checker and the requirements tables for reference.sap. Caution If you do not fully meet the requirements.

3. 3. the Prerequisite Check Results screen appears displaying the results found. n Minimum RAM: 3 GB To check RAM.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. this host must meet the following requirements: Requirement Type Requirement Hardware n Suitable backup system n Minimum disk space: l Database Software: 2. the Start Execution screen appears summarizing all parameters you have entered. you can also check the results in file prerequisite_checker_results. Choose Start ® Programs ® Administrative Tools ® Computer Management ® Disk Management.2 Requirements Checklist for a Central System If you want to install a central system. 2. Note For more information about each parameter.5 GB l SAP system files (not including paging file): 5 GB (x86.1. which you can find in the installation directory. where all instances reside on one host. AMD64) 8 GB (IA64) l SAP database files (not including paging file): u Non-Unicode (on at least 3 physically separate disks): 17 GB u Unicode (on at least 3 physically separate disks): 32 GB l 4. If required. choose Back and enter a new value.1 Preparation Hardware and Software Requirements . Choose Properties. n Paging File Size: 1 times RAM plus 8 GB For 64-bit systems. position the cursor on the parameter field and choose F1 in SAPinst. To change a parameter. 4. If you want to install only a small system.html. Result After the check has successfully completed. When you have finished. also see SAP Note 153641. in the Windows Explorer choose Help ® About Windows. To check paging file size: 09/11/2006 PUBLIC 25 . To start the Prerequisite Checker choose Start. Select the local drive. contact your hardware partner for appropriate swap space values.3 3.

If you install SQL Server 2005. 3.3 Requirements Checklist for a Distributed System The following sections provide information about the hardware and software requirements in a distributed system. To check your Windows version: 1. u Unicode collation SQL_Latin1_General_CP850_BIN2 n English international version of one of the following: l Windows Server 2003 Standard Edition l Windows Server 2003 Enterprise Edition l Windows Server 2003 Datacenter Edition . where the following SAP instances can reside on different hosts: Only valid for: HA (MSCS) n ABAP central services instance [page 27] End of: HA (MSCS) n n n n Central services instance [page 28] Database instance [page 29] Central instance [page 30] Dialog instance [page 32] 26 PUBLIC 09/11/2006 . If required. 3. see SAP Notes 62988 and 608651.1.1 Preparation Hardware and Software Requirements Requirement Type Requirement 1. in section Virtual Memory. see SAP Note 600027. l MS SQL Server 2005 Enterprise Edition: Server Software u Latest service pack and hotfix. n Make sure that the required fonts or code pages are installed. Choose Advanced ® Performance Settings. Choose Start ® All Programs ® Accessories ® Command Prompt. For more information. 2. Note We strongly recommend you to use the 64-bit version of the Windows Server 2003 editions. Software n One of the following SQL Server Enterprise Edition server software: l MS SQL Server 2000 Enterprise Edition: Server Software u Latest service pack and hotfix. Note . n Make sure that NLS and corresponding saplocales are installed. 2. For more information. choose Change. Right-click My Computer and choose Properties. Enter the command winver. u Unicode collation SQL_Latin1_General_CP850_BIN2 For more information on the collation for MS SQL Server 2000. see SAP Notes 62988 and 608651.3 3. if available. n A suitable Windows Resource Kit is strongly recommended. if available. you must install at least SP 1 for Windows Server 2003.

for MS SQL Server 2000. choose Change. if available. Choose Advanced ® Performance Settings.1 Requirements Checklist for the ABAP Central Services Instance The ABAP central services instance (ASCS) host must meet the following requirements: Requirement Type Requirement Hardware n Suitable backup system n Minimum disk space l ABAP Central Services Instance (ASCS) (not including paging file): 5 GB (x86. 3. in the Windows Explorer choose Help ® About Windows. To check disk space: 1.1 Preparation Hardware and Software Requirements . see SAP Note 608651. in section Virtual Memory.1. l MS SQL Server 2005 Native Client Software n English international version of one of the following: l Windows Server 2003 Standard Edition l Windows Server 2003 Enterprise Edition Software 09/11/2006 PUBLIC 27 . AMD64). n One of the following SQL Server client software: l MS SQL Server 2000 Enterprise Edition: Client Tools Only Latest service pack and hotfix. For more information on the current service pack for MS SQL Server 2000 .3 3. n If you install multiple SAP instances on one host. Only valid for: HA (MSCS) 3.3. Choose Start ® All Programs ® Administrative Tools ® Computer Management ® Disk Management. 2. AMD64) 8 GB (IA64) In addition you require 4 GB (x86. n Paging File Size: 1 times RAM plus 8 GB To check paging file size: 1. see SAP Note 62988. 2. Right-click My Computer and choose Properties. Note n The listed values only apply for development systems or quality assurance systems.5 GB To check RAM. For more information on the latest hotfix for MS SQL Server 2000. or 8 GB (IA64) per additional platform.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk. If required. Right-click the local drive and choose Properties. l 4. n Minimum RAM: 0. you need to add up the requirements.

in the Windows Explorer choose Help ® About Windows. Right-click My Computer and choose Properties.3 3.3. Note We strongly recommend you to use the 64-bit version of the Windows Server 2003 editions. End of: HA (MSCS) 3.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk.1 Preparation Hardware and Software Requirements Requirement Type Requirement l Windows Server 2003 Datacenter Edition . 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. If required. Software 28 PUBLIC 09/11/2006 . To check disk space: 1. Note . 2. Enter the command winver. n A suitable Windows Resource Kit is strongly recommended. n Minimum RAM: 0. Choose Start ® All Programs ® Accessories ® Command Prompt. choose Change. Choose Start ® All Programs ® Administrative Tools ® Computer Management ® Disk Management. Right-click the local drive and choose Properties. for MS SQL Server 2000. in section Virtual Memory. To check the Windows version: 1.1.5 GB To check RAM. Choose Advanced ® Performance Settings.2 Requirements Checklist for the Central Services Instance The central services instance (SCS) host must meet the following requirements: Requirement Type Requirement Hardware n Suitable backup system n Minimum disk space: l Central Services Instance (SCS) (not including paging file): 5 GB (x86. 3. 2. AMD64) 8 GB (IA64) l 4. If you install SQL Server 2005. n Paging File Size: 1 times RAM plus 8 GB To check paging file size: 1. 2. you must install at least SP 1 for Windows Server 2003.

3 Requirements Checklist for the Database Instance The database instance host must meet the following requirements: Requirement Type Requirement Hardware n Suitable backup system n Minimum disk space l SQL Server database software: 2. For more information on the latest hotfix for MS SQL Server 2000. Right-click the local drive and choose Properties.1. 2. Choose Start ® All Programs ® Administrative Tools ® Computer Management ® Disk Management.3 3. l MS SQL Server 2005 Native Client Software n English international version of one of the following: l Windows Server 2003 Standard Edition l Windows Server 2003 Enterprise Edition l Windows Server 2003 Datacenter Edition . Choose Advanced ® Performance Settings.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk. n Paging file size: 1.1 Preparation Hardware and Software Requirements Requirement Type Requirement For more information on the current service pack for MS SQL Server 2000 . To check the Windows version: 1. To check disk space: 1.5 times RAM (recommended by Microsoft) To check: 1. Note If you install SQL Server 2005. see SAP Note 608651. see SAP Note 62988. n Minimum RAM: 1 GB To check RAM. 2.5 GB l Database instance (not including paging file): u Non-Unicode (on at least 3 physically separate disks): 17 GB u Unicode (on at least 3 physically separate disks): 32 GB l 4. 09/11/2006 PUBLIC 29 . 3. you must install at least SP 1 for Windows Server 2003.3. n A suitable Windows Resource Kit is strongly recommended. 2. Right-click My Computer and choose Properties. in the Windows Explorer choose Help ® About Windows. Choose Start ® All Programs ® Accessories ® Command Prompt. Enter the command winver.

3. if available. see the Requirements Checklist for the Dialog Instance [page 32]. Software n One of the following SQL Server Enterprise Edition server software: l MS SQL Server 2000 Enterprise Edition: Server Software u Latest service pack and hotfix. For more information. End of: HA (MSCS) 30 PUBLIC 09/11/2006 . see SAP Note 600027. To check your Windows version: 1.1 Preparation Hardware and Software Requirements Requirement Type Requirement 3. If required. Enter the command winver. n Make sure that the required fonts or code pages are installed. u Unicode collation SQL_Latin1_General_CP850_BIN2 For more information on the collation for MS SQL Server 2000. l If you install SQL Server 2005. Note l We strongly recommend you to use the 64-bit version of the Windows Server 2003 editions.4 Requirements Checklist for the Central Instance The central instance host must meet the following requirements: Only valid for: HA (MSCS) For the requirements for the central instance in a high-availability system with MSCS. 2. see SAP Notes 62988 and 608651. if available.1. l MS SQL Server 2005 Enterprise Edition: Server Software u Latest service pack and hotfix. u Unicode collation SQL_Latin1_General_CP850_BIN2 n English international version of one of the following: l Windows Server 2003 Standard Edition l Windows Server 2003 Enterprise Edition l Windows Server 2003 Datacenter Edition . choose Change. you must install at least SP 1 for Windows Server 2003.3. n Make sure that NLS and corresponding saplocales are installed. in section Virtual Memory. Choose Start ® All Programs ® Accessories ® Command Prompt. For more information.3 3. see SAP Notes 62988 and 608651. n A suitable Windows Resource Kit is strongly recommended.

in the Windows Explorer choose Help ® About Windows. for MS SQL Server 2000. n Paging File Size: 1 times RAM plus 8 GB For 64-bit systems. you must install at least SP 1 for Windows Server 2003. Choose Start ® All Programs ® Accessories ® Command Prompt. AMD64) 8 GB (IA64) In addition you require 4 GB (x86. For more information on the current service pack for MS SQL Server 2000. For more information on the latest hotfix for MS SQL Server 2000. see SAP Note 608651.3 3. To check paging file size: 1. To check your Windows version: 1. or 8 GB (IA64) per additional platform. contact your hardware partner for appropriate swap space values. choose Change. Right-click My Computer and choose Properties. Choose Start ® All Programs ® Administrative Tools ® Computer Management ® Disk Management. 09/11/2006 PUBLIC 31 . Choose Advanced ® Performance Settings. Note . in section Virtual Memory. l 4. Select the local drive. If you want to install only a small system. n One of the following SQL Server client software: l MS SQL Server 2000 Enterprise Edition: Client Tools Only Latest service pack and hotfix. see SAP Note 62988. If required.1 Preparation Hardware and Software Requirements Requirement Type Requirement Hardware n Suitable backup system n Minimum disk space: l Central Instance (CI) (not including paging file): 5 GB (x86. n Minimum RAM: 1. 3. l MS SQL Server 2005 Native Client Software n English international version of one of the following: l Windows Server 2003 Standard Edition l Windows Server 2003 Enterprise Edition l Windows Server 2003 Datacenter Edition .5 GB To check RAM. AMD64). 2. 2. also see SAP Note 153641. If you install SQL Server 2005. Enter the command winver. Choose Properties. if available. 3. 2.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. Note Software We strongly recommend you to use the 64-bit version of the Windows Server 2003 editions.

n Minimum RAM: 1 GB To check RAM. If required. 3.5 Requirements Checklist for the Dialog Instance The dialog instance host must meet the following requirements: Requirement Type Requirement Hardware n Suitable backup system n Minimum disk space: l Dialog Instance (not including paging file): 2. in section Virtual Memory. If you want to install only a small system.1. l MS SQL Server 2005 Native Client Software n English international version of one of the following: l Windows Server 2003 Standard Edition l Windows Server 2003 Enterprise Edition Software 32 PUBLIC 09/11/2006 .3 3. n A suitable Windows Resource Kit is strongly recommended. Right-click My Computer and choose Properties.1 Preparation Hardware and Software Requirements Requirement Type Requirement n Make sure that the required fonts or code pages are installed. 3.3. Choose Start ® All Programs ® Administrative Tools ® Computer Management ® Disk Management. also see SAP Note 153641. n Paging File Size: 1 times RAM plus 8 GB For 64-bit systems. 2. in the Windows Explorer choose Help ® About Windows. Right-click the local drive and choose Properties. n One of the following SQL Server client software: l MS SQL Server 2000 Enterprise Edition: Client Tools Only Latest service pack and hotfix. Choose Advanced ® Performance Settings. if available. see SAP Note 62988. For more information on the latest hotfix for MS SQL Server 2000. To check paging file size: 1. 2. n Make sure that NLS and corresponding saplocales are installed. for MS SQL Server 2000. contact your hardware partner for appropriate swap space values.5 GB (x86. To check disk space: 1. AMD 64) 5 GB (IA64) l 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk. For more information on the current service pack for MS SQL Server 2000. see SAP Note 608651. choose Change.

4. you must install at least SP 1 for Windows Server 2003. In Windows. Open the Windows Explorer. you can implement either of the following domain models for the SAP system: n Extra domain In this model.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 the SAP system and database. Choose File ® Properties ® General.2 Preparation Checking for the Windows File System Requirement Type Requirement l Windows Server 2003 Datacenter Edition . Choose Start ® All Programs ® Accessories ® Command Prompt. 09/11/2006 PUBLIC 33 . Procedure 1. If you install SQL Server 2005. 2. Enter the command winver n A suitable Windows Resource Kit is strongly recommended 3. Note We strongly recommend to use the 64-bit version of the Windows Server 2003 editions. 3. 5. Do not install the SAP directories on a FAT partition. the user accounts must form the root domain and the SAP domain must be a child domain of this. the SAP system is embedded in its own domain. 2. Note You must use NTFS for an SAP system installation.3 3. which is specially defined for SAP. Note You do not need this step for a local installation. Select the root directory. 3. In this tree.3 Checking the Windows Domain Structure . . The system displays the type of file system in use. the SAP domain and user domain must be incorporated in a domain tree. Check that the file system is NTFS. Note . To check the Windows version: 1. In Windows. A second domain exists for the user accounts. NTFS supports full Windows security and long file names.

Therefore.3 3. we do not support running an SAP instance (including the database instance) on the host where the DNS service is installed. 3. Select Maximize data throughput for network applications. To install it. Prerequisites n You are performing a domain installation. We recommend this for all SAP system setups. .4 Reducing the Size of the File Cache The Windows file cache directly competes with SAP programs for memory. 5. 2. you need the Windows Server CDs. Caution If you cannot select File and Printer Sharing for Microsoft Networks.4 Preparation Reducing the Size of the File Cache n Single domain In this model. 4. . . 34 PUBLIC 09/11/2006 . Therefore. the system aborts. n You are familiar with checking Windows domain structures. Caution If you attempt the installation without the required authorization. the SAP system and the user accounts are included in a single domain. In the Local Area Connection Status dialog box. we recommend that you check that all SAP system and database hosts are members of a single Windows domain. 3. see the Windows documentation. 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 the SAP system. this option has not yet been installed. To confirm your entries. Procedure 1. For more information. Procedure For a domain installation. choose OK. double-click File and Printer Sharing for Microsoft Networks. Choose Start ® Control Panel ® Network Connections ® Local Area Connections. In the Local Area Connection Properties dialog box. Caution You cannot create local users and groups on the host that is used as domain controller. choose Properties. you should adjust the file cache as described below.

Check that you have Local Administrators rights for the central instance host. obtain these rights by asking the system administrator to enter you as a member of the Local Administrators group. In a local installation. For more information. Prerequisites n The authorization required depends on whether you intend to perform a domain or local installation.3 3. However. the user information is stored centrally on the domain controller and is accessible to all hosts in the system. Note SAP recommends to perform a domain installation. Domain Installation . 09/11/2006 PUBLIC 35 . In a domain installation. 2. see Performing a Domain Installation without being a Domain Administrator [page 36]. If required. l Do not use the user <sapsid>adm for the installation of the SAP system. For more information. all Windows account and user information is stored locally on one host and is not visible to any other hosts in the system. SAP does not support an SAP system installation on a domain controller. 1. you can perform the installation as a domain user who is a member of the Local Administrators group. . the domain administrator has to prepare the system appropriately for you. make sure that you do not run an SAP instance (including the database instance) on the host where the domain controller is running. Caution l For performance and security reasons. see System Configuration [page 8]. you have to ask the system administrator to grant you the necessary authorization before you start the installation.5 Preparation Granting User Rights for the Installation If necessary. 2. obtain these rights by asking the system administrator to enter you as a member of the Domain Administrators group. . Check that you have Domain Administrators rights. n A domain installation requires a domain controller to store user and account information centrally for the whole system. Local Installation 1. If required. Note If you are not granted domain administrators rights.

the domain administrator must prepare the system for you appropriately. you can perform the installation as a domain user who is a member of the Local Administrators group. 3. 36 PUBLIC 09/11/2006 .6 Performing a Domain Installation Without Being a Domain Administrator If you are not granted domain administrator rights. Create the new global group SAP_<SAPSID>_GlobalAdmin.. d) Choose Add. as described in Granting User Rights for the Installation [page 34]. ® Add. 2. e) Choose Close ® OK. Right-click Users in Tree. In this case. Note You normally perform a domain installation of the SAP system as a user with domain administrators rights. Note If you cannot find Active Directory Users and Computers. 3. start it as follows: a) Choose Start ® Run and enter mmc. End of: HA (MSCS) 3. b) Choose Console ® Add/Remove Snap-in. 2. Creating the New Global Group SAP_<SAPSID>_GlobalAdmin 1. Create the two new SAP system users <sapsid>adm and SAPService<SAPSID>. Log on as domain administrator.. c) Select Active Directory Users and Computers. . as described in this section. Add the users <sapsid>adm and SAPService<SAPSID> to the newly created group SAP_<SAPSID>_GlobalAdmin.3 3. Prerequisites You must perform this procedure as a domain administrator. choose: Start ® Programs ® Administrative Tools ® Active Directory Users and Computers . you always have to perform a domain installation. To start the Active Directory Users and Computers Console. Note If you use an MSCS configuration. The domain administrator has to: 1.6 Preparation Performing a Domain Installation Without Being a Domain Administrator Only valid for: HA (MSCS) . and choose New ® Group.

Field Input for <sapsid>adm Input for SAPService<SAPSID> First name: Initials: Last name: Full name: User logon name: None None None <sapsid>adm <sapsid>adm None None None SAPService<SAPSID> SAPService<SAPSID> 3. Choose OK. Enter the following: . Choose Next and enter the following: Password: <password> Confirm password: <password> 4. In the Users folder. Creating the New SAP System Users <sapsid>adm and SAPService<SAPSID> 1. In Active Directory Users and Computers Console. Select Password never expires . Select the new SAP_<SAPSID>_GlobalAdmin group and choose Add to add it to the list. 5. Adding the <sapsid>adm User to the SAP_<SAPSID>_GlobalAdmin Group 1. Note Make sure that no other options are selected. Choose Member ® Add. Note Enter the <sapsid>adm and SAPService<SAPSID> user exactly as specified in the correct uppercase and lowercase. Note Enter the SAP_<SAPSID>_GlobalAdmin group exactly as specified in the correct uppercase and lowercase. double-click the newly created user account <sapsid>adm in the list on the right. 3. 09/11/2006 PUBLIC 37 . 2. Select the following: a) Group scope: Global b) Group type: Security 6. Enter the following: Group name: SAP_<SAPSID>_GlobalAdmin . Choose Next ® Finish. right-click Users in Tree and choose: New ® User 2.6 Preparation Performing a Domain Installation Without Being a Domain Administrator 4. 5.3 3.

5. 3.3 3. 6. including the mapping of host names or aliases to IP addresses. Map the IP address of the transport host to the alias SAPTRANSHOST. or any other host as the transport host. Choose Add to add it to the list. 7. In the Users folder. Procedure 1. 3. 4. 4. a test or development system). Choose OK twice. .7 Preparing the SAP System Transport Host You need to prepare one transport host in the SAP system. Domain Users group. Choose OK. Note For more information on preparing the SAP system transport host. using one of the following methods: n On the DNS server If a DNS server is available for your system. Choose OK to close SAPService<SAPSID> Properties. Select the new SAP_<SAPSID>_GlobalAdmin group. 38 PUBLIC 09/11/2006 . Caution The SAPService<SAPSID> user must not be a member of the To remove this group from the Member of list: a) Select the SAP_<SAPSID>_GlobalAdmin group. see SAP Note 360515. the dialog instance host. Adding the SAPService<SAPSID> User to the SAP_<SAPSID>_GlobalAdmin Group 1. 2. The transport host uses the usr\sap\trans directory to temporarily store files that have been exported from one system and are waiting to be imported into another system. Note By default.7 Preparation Preparing the SAP System Transport Host . the user is also a member of the Domain Users group. ask your administrator to map the IP address of the transport host to the alias SAPTRANSHOST. This host has the function of controlling the import or export of files between the current SAP system and other SAP systems (for example. d) Choose Remove to delete it from the Member of list. . double-click the newly created user account SAPService<SAPSID> in the list on the right. Close the Active Directory Users and Computers Management Console. you can decide to use the central instance host. c) Select the Domain Users group. The DNS server is a database that contains a set of files with information about the TCP/IP network. Depending on your requirements. b) Choose Set Primary Group. Choose Member ® Add .

3 3.8

Preparation Installing the SAP Front-End Software

n In the hosts files If 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 IP address 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 the SAP_<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 transport host as SAPMNT. This enables SAPinst to address the transport directory in the standard way as \\SAPTRANSHOST\SAPMNT\trans.
Result

You 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 your system environment. To simplify the administration of your SAP system, we recommend you install the software on the central instance host.

09/11/2006

PUBLIC

39

3 3.9

Preparation Installing the Java Development Kit

With the SAP front-end installation software, SAPSetup, you can optimize the deployment of SAP GUI to thousands 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 Windows or UNIX host. This lets you perform the installation on a remote host, controlling it with the SAPinst GUI 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 Note 709140. 2. Make sure a valid JDK version is installed on every host on which you want to install an SAP instance with 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 3.10

Preparation Preparing the Installation DVDs

3. As of SAP NetWeaver 2004s strong encryption is mandatory for the J2EE Engine and for all usage types that are deployed on it. You need to obtain the JCE policy files beforehand so that they can be installed by 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 part of the installation package that you receive from SAP. However, you can also download the installation DVDs from SAP 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 DVDs do not contain any blanks. n If you use network drives for mounting the Export DVDs, make sure that the <sapsid>adm user has access 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 remaining DVDs. 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 document Media List ‒ SAP Solution Manager 4.0 SR1 on SAP Service Marketplace at service.sap.com/solutionmanager ® Installation Guides ® Release 4.0.
Required DVDs

SAP Instance Installation

Central services instance, central instance, dialog instance Database instance

n Installation Master DVD n Kernel DVD n NetWeaver Java DVD n n n n n Installation Master DVD Kernel DVD NetWeaver Java DVD RDBMS DVD Export DVD

09/11/2006

PUBLIC

41

sap. Procedure 1.com/swdc. dialog instance Database schema n Installation Master DVD n NetWeaver Java DVD n Kernel DVD n Installation Master DVD n NetWeaver Java DVD n Kernel DVD 2. In this case. you have to reassemble the required files after the download. see SAP Note 212876. 3.sap. For more information. However. If you download installation DVDs. 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 an individual sequence number: <material_number>_<sequence_number> 42 PUBLIC 09/11/2006 . Prerequisites To extract the downloaded SAR files make sure that you use the latest SAPCAR version.11 Downloading Installation DVDs from SAP Service Marketplace (Optional) You normally obtain the installation DVDs as part of the installation package from SAP. note that DVDs might be split into several files. Create a download directory on the host on which you want to run SAPinst. which you can find on SAP Service Marketplace at service. you can also download installation DVDs from SAP Service Marketplace at: service. You need at least SAPCAR 700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR files.com/swdc ® Downloads ® Installations and Upgrades ® Entry by Application Group ® <your solution> ® <release of your solution> ® <your operating system> ® <your database>. central services instance.3 3. You can check the entered location and then copy the entire DVD to the path you entered in the Copy Package to column.11 Preparation 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 upgraded ABAP System: SAP Instance Installation Required DVD Central instance. 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. 2.

51031387_1 51031387_2 .. Note SAPCAR asks if you want to replace existing files. Download the objects to the download directory.11 Preparation Downloading Installation DVDs from SAP Service Marketplace (Optional) Example . n Title All objects that are part of an installation DVD have the same title.. then 51031387_2. starting with the lowest sequence number ‒ for example 51031387_1.3 3. 09/11/2006 PUBLIC 43 .ASC. During the download SAPCAR sets up the structure of the installation DVD. 4. Always accept with Yes. and so on. . for example LABELIDX. 3. such as <solution><DVD_name><OS> or <database>RDBMS<OS> for RDBMS DVDs. Extract the individual download objects using SAPCAR.

.This page is intentionally left blank.

4.VBS (SQL4SAP_docu. you prepare your system for a Java Add-In installation [page 55]. 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]. Only valid for: HA (MSCS) .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. End of: HA (MSCS) You have to perform the following steps: 1. see section High Availability with Microsoft Cluster Service. .1. 3. You install the MS SQL Server database software [page 45]. see Customized Installation of SQL Server for an SAP System with SQL4SAP. 09/11/2006 PUBLIC 45 .pdf) and the readme. 4. Depending on the type of host involved.txt. You install the SAP system using SAPinst [page 56]. The SQL Server software has to be installed on each host in the system where you intend to set up an SAP instance.4 Installation 4 Installation This section provides information about how to perform a standard installation of your SAP system. you either have to install the software for the database client or server.VBS. Note If you want to perform a Microsoft Cluster Service (MSCS) installation. 2. both of which are located in the root directory of the SQL Server RDBMS DVD. If required.1 Installing the SQL Server Database Software The following sections describe how to install the SQL Server 2000 or SQL Server 2005 database software. Note For more information about installing with SQL4SAP.

2.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 systems Default Instances. see Clustering the SQL Server Database Software [page 133]. Note For up-to-date information about installing SQL Server 2005 with SQL4SAP.VBS.VBS script does not support Microsoft Cluster Service (MSCS). Follow the instructions and enter the required information in the installation screens. Procedure 1. which also includes the material number of the DVD containing the VB script. insert the SQL Server 2000 RDBMS SP4 DVD into your DVD drive or mount the network share locally.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.1. Double-click SQL4SAP. For SQL Server 2005. l SQL_Latin1_General_CP850_BIN or SQL_Latin1_General_CP850_BIN2 collation.VBS located in the root directory. read SAP Note 377430. you use the SQL4SAP. For more information about installing the SQL Server database software for MSCS. you use the SQL4SAP. Note For up-to-date information about installing SQL Server 2000 with SQL4SAP. 46 PUBLIC 09/11/2006 . or SQL Server Client Tools Only.4 4. n For SQL Server 2005. 4. insert the SQL Server 2005 RDBMS DVD in your DVD drive or mount the network share locally. End of: HA (MSCS) n For SQL Server 2000. For SQL Server 2000. l Latest SQL Server 2000 service pack l Latest SQL Server hotfix. read SAP Note 896566. Named Instances.VBS script to automatically install the: l SQL Server 2000 Enterprise Edition on 32-bit or 64-bit systems. l . Caution The SQL4SAP. 4. if required. you get an error message. .1 Installation Installing the SQL Server Database Software Only valid for: HA (MSCS) . 3. If you want to run the script in an MSCS configuration.

Select SQL Server 2000 Components. Start the installation program with autorun. 2. 3.1 Installing the SQL Server 2000 Database Software on 32-Bit Manually The MS SQL Server software has to be installed on each host in the system where you intend to set up an SAP instance. Caution Make sure that you have not applied NTFS compression to the disk where you install the MS SQL Server software.exe located in the x86\SQL2000 directory of the MS SQL Server 2000 RDBMS SP4 DVD. 09/11/2006 PUBLIC 47 . Note When you mount the DVD from a remote server. Note Ignore the compatibility warning and choose Continue. . . Procedure 1. Choose Next. It provides all the functions required to run a relational database management system. it must be assigned a drive letter. Depending on the type of host involved.1 Installation Installing the SQL Server Database Software . Install Components Microsoft SQL Server 2000 Enterprise Edition Welcome Select Install Database Server. Select Install Database Server. Log on to the host as a local administrator.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. you also have to install the corrected collation for SQL Server 2000. If required. The installation writes a log file sqlstp. It enables the communication between a host and the database. 4. Note If you install SQL Server 2000 the installation differs on a 32-bit or 64-bit system.2. Insert the MS SQL Server 2000 RDBMS SP4 DVD into your DVD drive. Choose Next. Enter the required information as specified in the table below. n The software for the client must be installed on all hosts without the database. n The software for the server must be installed on the database host. . you either have to install the software for the database client or server.4 4.1.

Select Default. Dialog box does not appear. Select Use the Local System account. Leave selection unchanged and choose Next. Mixed mode is required. From the drop-down list select Binary order. Dialog box does not appear. Network Libraries Start Copying Files Choose Licensing Mode 4. install the corrected MS SQL Server collation [page 51].4 4. Enter the key specified in the file Enter the key specified in the file SAPCDKEY. Do not specify an instance name. install the latest Service Pack. Select Client Tools Only. and the latest hotfix. the RDBMS DVD. Select all components. or install Client Tools. Dialog box does not appear. When you have finished the installation. Collation settings Select SQL Collations. SAPinst automatically changes the authentication mode into Mixed mode when installing a Java system. Choose Yes. Select Create a new instance of SQL Server or install Client Tools. Enter your personal information. Select all components. Choose Yes. Note Authentication mode Dialog box does not appear. see SAP Note 608651. Choose Next. Dialog box does not appear. for SQL Server 2000. Select Custom. Auto start SQL Server Service. For a Java system. Enter your personal information. If you have installed the server software. Dialog box does not appear. 5. For more information on the SQL Server collation. for use with the 850 (Multilingual) Character Set. Select Create a new instance of SQL Server. see SAP Note 62988. . For more information on the latest hotfix. see SAP Note 600027. if available. Select the mode you require. Select Local Computer. We recommend to use Windows authentication mode.txt in the root directory of SAPCDKEY.1 Installation Installing the SQL Server Database Software Window Server Input Client Input Computer Name Installation Selection User Information Software License Agreement CD-Key Select Local Computer. Select the authentication mode. Dialog box does not appear. Installation Definition Instance Name Setup Type Select Components Service Accounts Select Use the same account for each service. For more information on the latest Service Pack.txt in the root directory of the RDBMS DVD. Choose Next. 48 PUBLIC 09/11/2006 . Select Server and Client Tools.

Insert the MS SQL Server 2000 RDBMS SP4 DVD into your DVD drive. 4.txt file in the IA64\SQL2000 subdirectory.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 cannot run the SQL Server 2000 graphical user interface (GUI) tools.2 Installing the SQL Server 2000 Database Software on 64-Bit Manually On a 64-bit system.exe located in the directory IA64\SQL2000. Procedure 1.4 4. Note n You can install the 32-bit graphical user interface management tools from the 32-bit directory of the MS SQL Server 2000 RDBMS SP4 DVD.1 Installation Installing the SQL Server Database Software 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 Software License Agreement Enter your name and the product key specified in the file SAPCDKEY.2. Choose Yes. To start the installation. with the following exceptions: n n n n n Client Network Utility (supported by the 64-bit Windows operating system) Server Network Utility Service Manager SQL Server 2000 Licensing (in Control Panel) Setup. n Graphical interface management tools which were installed with the 32-bit version of SQL Server 2000 are not supported in the 64-bit version. run setup. For more information refer to the readme.1. . 3. you have to install them with the 32-bit version of SQL Server 2000 on a 32-bit computer and use them to remotely manage the 64-bit server. Caution Make sure that you have not applied NTFS compression to the disk where you install the MS SQL Server software. . 09/11/2006 PUBLIC 49 . 2. Log on to the host as a local administrator.txt in the root directory of the RDBMS DVD.

n Client Software: Select SQL Server Management Tools. 50 PUBLIC 09/11/2006 .1 Installation Installing the SQL Server Database Software Window Input Feature Selection n Server Software: Select all components. Select the licensing mode and choose Next. and choose Entire feature will be unavailable. but cannot be used. see SAP Note 62988. for use with the 850 (Multilingual) Character Set. For more information on the SQL Server collation. left-click on it. Note To select a component. Note For a Java system. install the latest Service Pack . Auto start SQL Server Service. n Enter and confirm the password for the sa login. Leave selection unchanged and choose Next. Select Install. Security Enhancement: Cross Database Ownership Chaining Collation Settings Note If you have chosen Windows authentication mode.4 4. From the drop-down list select Binary order. Select SQL Collations. . . SAPinst automatically changes the authentication mode into Mixed mode when installing a Java system. Select Use the Local System account. We recommend to use Windows authentication mode. left-click on it and choose Entire feature will be installed on local hard drive. see SAP Note 608651. n Select the authentication mode. see SAP Note 600027. If you have installed the server software. . For more information on the latest Service Pack. the sa login is created. for SQL Server 2000. Select Use the same account for each service. Licensing Mode Ready to Install 5. Mixed mode is required. install the corrected MS SQL Server collation [page 51]. For more information on the latest hotfix. and the latest hotfix. Instance Name Service Account Authentication Mode Select the instance type you want to install. 6. When you have finished the installation. To deselect a component. if available.

4 4.1

Installation Installing the SQL Server Database Software

4.1.2.3 Installing the Corrected MS SQL Server Collation for MS SQL Server 2000
When you install the MS SQL Server 2000 database for an SAP system, in the field Collation Settings you have to select 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 use with 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 solve this 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 selected Binary 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 SAP Notes 62988 and 608651. .
Note

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

n To obtain a correct collation order with MS SQL Server, you have to use the new collation for all new installations of a Unicode or non-Unicode SAP system with the MS SQL Server database. New versions of the 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 cannot run as two databases in the same MS SQL Server instance. If you want to install a new system on a database server 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

4 4.1

Installation Installing the SQL Server Database Software

select serverproperty('collation') Caution

.

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

Result

You 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 Software Manually
This section describes how to install the SQL Server 2005 database server software on 32-bit or 64-bit systems manually. If you use an MSCS environment, you have to use the manual procedure. For a standard SAP system, 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 system drive 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 Tools l SQL Server instance l Temporary space during the installation The required disk space depends on the type of SQL Server components already installed or to be installed. It also depends on the system. For a 32-bit system you need up to 2 GB free disk space on the system drive, for a 64-bit system you might require more space. n Make sure that the Microsoft Distributed Transaction Coordinator (MSDTC) service is running before you start the installation.
Procedure

1. 2. 3. 4. 5.

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

52

PUBLIC

09/11/2006

4 4.1

Installation Installing the SQL Server Database Software

.

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 the same directory.
Server Input

Window

End User License Agreement Installing Prerequisites Welcome to the Microsoft SQL Server Installation Wizard System Configuration Check

Accept the licensing terms and conditions and choose Next. Choose Install and, if required, Next. Choose Next. a) Check your system configuration and, if required, set up the required configuration. .
Note

n For more information about the required system configuration for a software component, choose Messages. n IIS is not required for an SAP system. Therefore, you can ignore the warning about the IIS Feature Requirement. n If there is a warning in COM Plus Catalog Requirement, correct the configuration before you proceed with the installation. Make sure that the Microsoft Distributed Transaction Coordinator (MSDTC) service is running.

b) Choose Next. Registration Information a) Enter your personal information, and the product key b) Choose Next. a) Select: n SQL Server Database Services n Workstation components, Books Online and development tools. b) Choose Advanced a) Expand Database Services and deselect Replication. b) Expand Client Components and if available, deselect Business Intelligence Development Studio. .
Note

Components to Install

Feature Selection

We recommend that you deselect these features as they are not required for an SAP system.

c) Choose Next.

09/11/2006

PUBLIC

53

choose Next.1 Installation Installing the SQL Server Database Software Window Server Input Instance Name Select the instance you want to install and choose Next. This mode is required for a Java or ABAP+Java system. . . b) Choose Next. c) Choose Next. c) Choose Next. When the setup process has finished. . Note Error and Usage Report Settings Ready to Install Setup Progress To see the log files for the SQL Server components. Note SAP recommends to install a Default instance. and enter the user name and password. Authentication Mode a) Select Mixed Mode (Windows Authentication and SQL Server Authentication). The password for the sa login must comply with the Windows password policy. Leave the selection unchanged and choose Next. 54 PUBLIC 09/11/2006 . choose Setup finished. for use with the 850 (Multilingual) Character Set. b) From the drop-down list select Binary order based on code point comparison. n Use a domain user account. b) Under Start services at the end of setup make sure that SQL Server and SQL Server Agent are selected. 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. you have to set the password for the sa login. Note If you use a named instance. Choose Install. you must also select SQL Browser. If you choose this mode.4 4. Note SAPinst automatically changes the authentication mode into Mixed Mode when installing a Java system. Collation Settings a) Select SQL collations (used for compatibility with previous versions of SQL Server). Completing Microsoft SQL Server 2005 Setup Choose Finish. .

4.1. 7.0 SR1. n ABAP system that has been upgraded to SAP Solution Manager 4.pfl check the parameter dbs/mss/schema. Change to the platform-specific folder and choose sqlncli. Restart SQL Server.msi . 4. Insert the SQL Server 2005 RDBMS DVD in your DVD drive or mount it locally. Procedure 1. The SQL Server 2005 client software must be installed on all hosts without the database.2. convert the schema as described in SAP Note 683447. under Protocol Name.2 Installation Preparing your System for an Java Add-In Installation 6. right-click Named Pipes and TCP/IP. if you want to perform a Java Add-In installation for an already existing: n SAP Solution Manager 4. Procedure 1. Log on as local administrator to the host where you want to install an application server. n If it does not exist or is set to dbo. 09/11/2006 PUBLIC 55 . and select Enable. It enables the communication between a host and the database.msi file on the Microsoft SQL Server CD in the Setup directory.2 Preparing your System for an Java Add-In Installation The following procedure is only required.4 4. In your default profile \usr\sap\<SAPSID>\SYS\profile\default. 2. When you have finished the installation.5 Installing the SQL Server 2005 Native Client Software Manually This chapter describes how to install the SQL Server 2005 Native Client (SNAC) software on 32-bit or 64-bit systems. n If it is set to <sapsid> (lowercase letters). enable the Named Pipes and TCP/IP protocol in the SQL Server Configuration Manager as follows: n Choose Start ® All Programs ® Microsoft SQL Server 2005 ® Configuration Tools ® SQL Server Configuration Manager. Note You also find the sqlncli.0 SR1 ABAP system. 3. no further action is required. n Expand SQL Server 2005 Network Configuration and select one of the following: n For a default instance. Follow the instructions in the SQL Server installation setup screens. select Protocols for MSSQLServer n For a named instance. select Protocols for <SAPSID> n In the right-hand pane. 4.

4. 4. SAPinst GUI connects to the GUI server with a secure SSL connection. MS SQL Server 2000 only: Check if you use SQL Server collation SQL_Latin1_General_CP850_BIN2: a) Start the SQL Server Enterprise Manager.3. This section describes an installation where SAPinst.3 Installation Installing an SAP System Using SAPinst Only valid for: HA (MSCS) . b) Right-click on your SQL Server and choose Properties. which both use Java. n If you use collation SQL_Latin1_General_CP850_BIN. 56 PUBLIC 09/11/2006 .4 4. SAPinst GUI and the GUI server also start. you can instead perform a remote installation with SAPinst [page 66]. SAPinst GUI. or a standalone engine: n n n n n n Running SAPinst on Windows [page 56] Installing a Java Add-In for an Already Existing Solution Manager ABAP System with SAPinst [page 62] Using SAPinst GUI [page 64] Interrupted Installation with SAPinst [page 65] Performing a Remote Installation with SAPinst (Optional) [page 66] Starting SAPinst GUI Separately (Optional) [page 67]. Note If you use Microsoft Cluster Service. When the conversion is finished. Start SAPinst manually with the command: sapinst SAPINST_USE_HOSTNAME=<virtual_hostname_of_SAP_system> . convert it to SQL_Latin1_General_CP850_BIN2 as described in Installing the Corrected MS SQL Server Collation for SQL Server 2000 [page 51]. End of: HA (MSCS) 2. bring the SAP resource SAP <SAPSID> online again. where SAPinst GUI is running on a separate host from SAPinst and the GUI server. If required.3 Installing an SAP System Using SAPinst The following sections provide the steps that you have to perform to install the various instances of an SAP system. and the GUI server connects to SAPinst. and the GUI server are running on the same host. bring your SAP resource offline.1 Running SAPinst on Windows This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a SAPinst GUI and a GUI server. Open a command prompt and change to the directory of the Installation Master DVD: IM_WINDOWS_<platform>. In the General tab under Server collation you see the collation installed. Note the following information about SAPinst: n When you start SAPinst. n If you use SQL_Latin1_General_CP850_BIN2 no further action is required.

2. it must neither be set in the start profile.xxxxxx.3 Installation Installing an SAP System Using SAPinst n SAPinst normally creates the installation directory sapinst_instdir. n SAPinst creates a subdirectory for each installation service called <sapinst_instdir>\<installation_service>. . which is located in %ProgramFiles%\sapinst_instdir. l Click the icon for the SAPinst output window located in the Windows tray and choose File ® Exit. and you want to install a dialog instance. it tries to create sapinst_instdir in the directory defined by the environment variable TEMP. see Granting User Rights for the Installation [page 34]. n If you are installing a second or subsequent SAP system into an existing database. 09/11/2006 PUBLIC 57 . or SystemRoot). For more information. where it keeps its log files. you need 60-200 MB free space for the SAPinst executables. You can safely delete them. Edit the default profile DEFAULT. Caution If SAPinst cannot find a temporary directory. In addition. n Dialog instance only: If your SAP System has been upgraded from an earlier release. Recommendation We recommend that you keep all installation directories until the system is completely and correctly installed. and which is located directly in the Program Files directory. These executables are deleted after SAPinst has stopped running. n The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP. and at least 130 MB of free space in the installation directory for each Java installation service. Directories called sapinst_exe. choose one of the following options: l Right-click the icon for the SAPinst output window located in the Windows tray and choose Exit. 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. the installation terminates with the error FCO-00058. Prerequisites n You are logged on as a user with the required rights and privileges to install the SAPinst tool and the SAP system.xxxx sometimes remain in the temporary directory. n You need at least 50 MB of free space in the installation directory for each ABAP installation service. If SAPinst is not able to create sapinst_instdir there.4 4. which might be useful if an error occurs. . TMP. l If it is not set in the instance profile. For more information. The temporary directory also contains the SAPinst Self-Extractor log file dev_selfex. it must also be set in the start profile.PFL: Set rdisp/msserv_internal to a free port number.out. make sure that the database is up and running before starting the installation. TMPDIR. see Installation of Multiple Components in One Database [page 97]. perform the following steps: 1. n If you want to terminate SAPinst and the SAPinst Self-Extractor.

..... Example Instance profile of the central services instance: Before: . l Set rdisp/msserv_internal to the port number assigned to rdisp/msserv. Restart all SAP services and instances of your SAP system. rdisp/msserv = sapmsSID rdisp/msserv_internal = <free port number> .exe from the following path: <DVD drive>:\IM_WINDOWS_<platform> SAPinst GUI starts automatically by displaying the Welcome screen. After: . Procedure 1.. After: . 2.4 4.. Edit the instance profile of the central services instance: l Set rdisp/msserv to 0. 4.. ..3 Installation Installing an SAP System Using SAPinst . 3.. Example DEFAULT. Start SAPinst from the SAP Installation Master DVD by double-clicking sapinst.. However.. if there is only one component to install.. 58 PUBLIC 09/11/2006 . rdisp/msserv = 4711 . SAPinst directly displays the first input dialog without presenting the Welcome screen.PFL Before: .. rdisp/msserv = 0 rdisp/msserv_internal = 4711 . Insert the SAP Installation Master DVD into your DVD drive or mount it locally. rdisp/msserv = sapmsSID ...

3 Installation Installing an SAP System Using SAPinst . enter the following command: sapinst -p. In the Welcome screen. You can install the following system variants: l Central System l Distributed System Only valid for: HA (MSCS) l High-Availability System End of: HA (MSCS) The following tables provide an overview of the installation services available for these system variants: . SAPinst uses port 21200 to communicate with the GUI server. choose one of the following installation services: n SAP Systems n Additional Software Life-Cycle Tasks The 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 Solution Manager 4.4 4. l If you want to use active directory [page 101]. install a dialog instance for a central or distributed system by choosing the installation service <SAP System> ® Additional Software Life-Cycle Tasks ® Application Server ® Dialog Instance. The GUI server uses port 21212 to communicate with SAPinst GUI. Note n During the installation. Enter the following command in a single line: sapinst. and SAPinst GUI.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. l If required. In this case. you must run the installation service Operating System Users and Groups before you start the installation of the SAP system (see table Additional Software Life-Cycle Tasks below). Note l Choose the corresponding installation services from the tree structure exactly in the order they appear for each system variant. GUI server. the default ports 21200 and 21212 are used for communication between SAPinst. you must run the installation service Active Directory Configuration before you start the installation of the SAP system (see table Additional Software Life-Cycle Tasks below). 3. l If you want to use global accounts. which are configured on separate hosts. open a command prompt and change to the required directory as follows: <DVD drive>:\IM_WINDOWS_<platform>.0 SR1 ® SAP Systems ® <Database> ® <System Variant> ® Based on <technical stack>. You get an error message if one of these ports is already in use by another service. 09/11/2006 PUBLIC 59 .

Installs a database instance. You must have finished the Central Services Instance (SCS) installation. Installation Services for a Distributed System Installation Services Remarks Central Services Instance (SCS) Mandatory step in installing a distributed SAP system with usage types or software units based on AS ABAP and AS Java. Mandatory step in installing a distributed SAP system. before you can choose this installation service. This step configures an additional Microsoft Cluster Service (MSCS) node to run the SAP cluster group.4 4. Installs a central services instance (SCS) and prepares the SAP global host. Database Instance Additional MSCS Node 60 PUBLIC 09/11/2006 . You must have completed the configuration of the first MSCS node and the database instance installation. Database Instance Central Instance Installation Services for a High Availability System Installation Services Remarks Central Services Instance for ABAP (ASCS) Central Services Instance (SCS) First MSCS Node Installs a central services instance for ABAP (ASCS) and prepares the SAP global host. Installs a central instance and enables additional usage types or software units. Installs a database instance. Installs a central services instance (SCS). Note You require at least usage type AS Java or AS ABAP.3 Installation Installing an SAP System Using SAPinst Installation Services for a Central System Installation Service Remarks Central System Installation Installs a complete SAP system including the following instances on one host: l Central services instance (SCS) l Database instance l Central instance . You must have finished the database instance installation. You can choose the usage types or software units on the next screen. This step performs the following on the first Microsoft Cluster Service (MSCS) node: l Creates the SAP cluster group l Adds the ASCS and SCS instances to the SAP cluster group. Mandatory step in installing a distributed SAP system on several hosts.

For more information. which contains a replica of the lock table (replication server). after you have installed an application server. Installs a dialog instance. SAPinst automatically checks the hardware and software requirements during the installation with the Prerequisite Checker. if required. see Installing a Java Add-In for an Already Existing SAP Solution Manager ABAP System with SAPinst [page 62] . SAPinst automatically prompts you. For more information. Caution Perform this task before you start the installation of your SAP system. l Use global accounts that are configured on a separate host . see Running the Prerequisites Checker in Standalone Mode [page 24]. . Java Add-In for ABAP Choose this service to install usage types based on AS Java to an already installed SAP Solution Manager ABAP system. l Check your hardware and software requirements before you start the installation Otherwise. 09/11/2006 PUBLIC 61 . For more information. Caution Perform this task before you start the installation of your SAP system. Note If you want to use LDAP. Application Server Choose Application Server ® <Database> ® Dialog Instance to install one or more dialog instance(s) in an already installed SAP system. n Additional Software Life-Cycle Tasks You use this service to perform the following tasks or to install the following components: Installation Service Remarks Additional Preparation Tasks With these preparation tasks you can: l Configure Active Directory [page 101] . Installs a central instance and enables additional usage types or software units. see Preparing the Active Directory [page 101].3 Installation Installing an SAP System Using SAPinst Installation Services Remarks Enqueue Replication Server Central Instance Dialog Instance Installs an enqueue replication server. Note You require at least one dialog instance in a high-availability system configured with MSCS. choose Application Server ® LDAP Support.4 4. . If any changes are necessary to the SAP system or operating system settings.

End of: HA (MSCS) Procedure 1. Uninstall 4. If SAPinst prompts you to log off from your system. We recommend you to delete all files in the directory %userprofile%\. 5. the screen Finished installation successfully is displayed.com/instguidesnw2004s ® Installation Choose this service to uninstall your SAP system. stop the ASCS instance in the Cluster Administrator (service SAP <SID> <instance_number> Service ) before you run the installation service First MSCS Node in SAPinst. For more information. standalone engines. If the installation was successful. Only valid for: HA (MSCS) If you use Microsoft Cluster Service (MSCS). For more information. Start SAPinst [page 56].4 4. . Follow the instructions in the SAPinst dialogs and enter the required parameters.0 SR1 ® Additional Software Life-Cycle Tasks ® Java Add-In for ABAP ® <database> ® <system variant>. 4.sdtgui\.0 SR1 ABAP. Note For more information about the input parameters. which is available at SAP Service Marketplace at: service. as shown in the following tables: 62 PUBLIC 09/11/2006 . Choose the corresponding installation services from the tree structure exactly in the order they appear for each system variant.3 Installation Installing an SAP System Using SAPinst Installation Service Remarks System Copy Choose this service to perform a system copy. On the Welcome Screen. see the system copy guide. chooseSAP Solution Manager 4. or optional standalone units. 6. position the cursor in the field of the respective parameter and press F1 . 3. SAPinst restarts automatically. log off and log on again.3.sap. 2. After you have entered all required input information. More Information Troubleshooting with SAPinst [page 112].2 Installing a Java Add-In for an Already Existing Solution Manager ABAP System with SAPinst (Optional) This section describes how to install a Java Add-In for an existing Solution Manager ABAP system. see Deleting an SAP System [page 106]. Prerequisites Your ABAP system must be on the support package level of SAP Solution Manager 4. SAPinst starts the installation and displays the progress of the installation.

Note If your database instance is to be installed in the same MSCS cluster as the SCS and ASCS instance. Choose this step only if you use Microsoft Cluster Services (MSCS). Database Instance Java Add-In Installs the Java schema in the database of your ABAP system . you must perform this step on the first node of this MSCS cluster. you perform this step on another MSCS cluster. before you use this service. Note Make sure that you choose instance type ASCS and SCS instance (ABAP and Java). Caution You must install it on the same shared disk as the ASCS instance.3 Installation Installing an SAP System Using SAPinst Installation Services for a Java Add-In for ABAP ‒ Central or Distributed System Installation Services Remarks Central Services Instance (SCS) Java Add-In Database Instance Java Add-In Central Instance Java Add-In Installs a central services instance (SCS) and adds usage types or software units based on AS Java Installs the Java schema in the database of your ABAP system Adds usage types or software units based on AS Java . uninstall the old ABAP dialog instance. . 09/11/2006 PUBLIC 63 . Note Make sure that you choose instance type ASCS and SCS instance (ABAP and Java).4 4. First MSCS Node Configures the SCS instance for the first MSCS node . Caution Additional MSCS Node . Installation Services for a Java Add-In for ABAP ‒ High-Availability System Installation Services Remarks Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) and adds usage types or software units based on AS Java . If your database instance is to be installed in a different MSCS cluster from the ASCS and SCS instance. This step configures the SCS instance for the additional MSCS node. Caution When performing an upgrade installation.

4. Follow the instructions in the SAPinst input dialogs and enter the required parameters. Caution Central Instance Java Add-In Dialog Instance When performing an upgrade installation. Adds usage types or software units based on AS Java Installs a dialog instance in a high-availability system . 4. n Continue Continues the installation. uninstall the old ABAP dialog instance. You can restart SAPinst to continue the installation later from this point.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 F1 Description Displays detailed information about each input parameter. You must perform this step on all MSCS nodes where the Java central services (SCS) instance or ABAP central services (ASCS) instance is installed and clustered. which contains a replica of the lock table (replication table). This is where you install the Java Add-In. After you have entered all required input parameters. Note SAPinst prompts you for the production client of your ABAP system. SAPinst starts the installation and displays the progress of the installation.3 Installation Installing an SAP System Using SAPinst Installation Services Remarks Enqueue Replication Server Installs an enqueue replication server. Cancels the installation with the following options: n Stop Stops the installation without further changing the installation files.4 4. Exit 64 PUBLIC 09/11/2006 . before you use this service. .3.

This is possible because SAPinst records the installation progress in the keydb. the installation pauses and a dialog box appears.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. Retry Stop Performs the installation step again (if an error has occurred).xml file. try to solve the problem and then choose Retry.xml file. Note If for some reason you need to log off during the installation from the host where you control the installation with SAPinst GUI. If the same or a different error occurs again. . Therefore. and the GUI server. SAPinst records the installation progress in the keydb. SAPinst continues the installation from the current point. We recommend that you view the entries in the log files. See the procedure below. Stop Continue 09/11/2006 PUBLIC 65 . SAPinst displays the same dialog box again. see Starting SAPinst GUI Separately [page 67]. Continues with the option you have chosen before. You can later reconnect to the same SAPinst installation from the same or another host. closing the dialog box.3 Installation Installing an SAP System Using SAPinst Button / Function Key / Menu Entries Description Log off Stops the SAPinst GUI. For more information.4 4. Continue 4. SAPinst stops the installation. but SAPinst and the GUI server continue running. The dialog box contains a short description about the choices listed in the table below as well 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 installation continues while you are logged off. You can continue the installation later from this point. 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 of the previous steps. you can continue the installation from the point of failure without repeating any of the previous steps.3. the SAPinst GUI. Stops the installation without further changing the installation files.

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. Log on to your remote host as a user who is a member of the local administrators group. 2.3. 5. Afterwards. which you stopped by choosing Stop. Insert the Installation Master DVD in your DVD drive.5 Performing a Remote Installation with SAPinst (Optional) You use this procedure to install your SAP system on a remote host. The local host is the host from which you control the installation with SAPinst GUI. 66 PUBLIC 09/11/2006 . Procedure 1. 3. the following naming convention is used: <log_day_month_year_hours_minutes_seconds> (for example. In this case. For the backup directory. 1.3 Installation Installing an SAP System Using SAPinst Procedure This procedure describes the steps to restart an installation. and SAPinst GUI runs on the local host. Continue old installation 4. it moves the content of the old installation directory and all installation-specific files to the backup directory. or to continue an interrupted installation after an error situation. Alternative Behavior Run a new Installation SAPinst does not continue the interrupted installation. select the installation service that you want to continue and choose Next. From the tree structure in the Welcome screen. In the What do you want to do? screen. Enter the following commands at the Windows command prompt: cd <DVD drive>:\IM_WINDOWS<platform> sapinst. the Welcome screen does not appear. log_01_Oct_2003_13_47_56). To test this: l Log on to your remote host and enter the command ping <local host>. SAPinst continues the interrupted installation from the point of failure. Instead. . SAPinst and the GUI server run on the remote host. Note If there is only one component to install. The What do you want to do? screen appears. l Log on to the local host and enter the command ping <remote host>. you can no longer continue the old installation. decide between the following alternatives and confirm with OK.4 4. Log on to your remote host as a user who is a member of the local administrators group.exe 4.

Log on as a member of the local administrators group.bat -host <host_name> <host_name> is the host name of the installation host. You might need to start SAPinst GUI separately in the following cases: n You have logged off from SAPinst. You see the following at the command prompt: guiengine: no GUI connected. 2. Start SAPinst GUI on your local host. If SAPinst GUI runs on a different host from SAPinst and the GUI server. you have to start SAPinst GUI separately. 3. enter the following command: startinstgui. 3.3. enter the following command: startinstgui. Enter the following commands: cd <DVD drive>:\IM_WINDOWS_<platform> sapinst.6 Starting SAPinst GUI Separately (Optional) You use this procedure to start SAPinst GUI separately. port <port_number> to continue with the installation 4. you can start SAPinst GUI separately.bat SAPinst GUI uses the local host as default. as described in Starting SAPinst GUI Separately [page 67]. waiting for a connection on host <host_name>. If you logged off during the installation and you later want to reconnect to the installation while it is still running. n You want to perform a remote installation [page 66]. Prerequisites You have installed the Java Development Kit [page 40] on the host on which you want to start SAPinst without SAPinst GUI.3 Installation Installing an SAP System Using SAPinst 2. Start SAPinst GUI in one of the following ways: n If SAPinst GUI runs on the same host as SAPinst and the GUI server. To change to the relevant directory enter the following command: cd <DVD drive>:\IM_WINDOWS<platform> 4. 4. SAPinst now starts and waits for the connection to the SAPinst GUI. see Running SAPinst on Windows [page 56]. Insert the SAP Installation Master DVD into your DVD drive.exe -nogui For more information. Insert the Installation Master DVD in the DVD drive on your remote host.4 4. Starting SAPinst GUI on a Windows Platform 1. n If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation). 09/11/2006 PUBLIC 67 .

sh -host <host_name> <host_name> is the host name of the installation host 68 PUBLIC 09/11/2006 . . 3.4 4. Note Mount the DVD locally. SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. We do not recommend that you use Network File System (NFS). In this case. 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.sh SAPinst GUI uses as default the local host. enter the following command without additional parameters: . 2. Note l If you enter the command without additional parameters. n If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation). l For a list of options to start SAPinst GUI. To change to the mount directory enter the following command: cd <Installation_Master_DVD>/IM_<OS> 4. change to the same directory as your SAPinst executable and enter the command startinstgui. . Caution Make sure that the root user has not set any environment variables for a different SAP system or database. enter the following command with additional parameters: . Mount your installation DVD. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. SAPinst GUI uses the local host as default. Log on as user root./startInstGui./startInstGui. As SAPinst and the GUI server are running on another host.3 Installation Installing an SAP System Using SAPinst . enter the name of the host on which SAPinst is running and choose Log on. Starting SAPinst GUI on a UNIX Platform 1.bat -h. The first dialog of the installation appears and you can perform the remote installation from your local host.

SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. change to the same directory as your SAPinst executable and enter the command .sh -h. The first dialog of the installation appears and you can perform the remote installation from your local host. As SAPinst and GUI server are running on another host.4 4. enter the name of host on which SAPinst is running and choose Log on./startInstGui. In this case.3 Installation Installing an SAP System Using SAPinst . SAPinst GUI starts and tries to connect to the GUI server and SAPinst. SAPinst GUI uses the local host as default. Note l If you enter the command without additional parameters. 09/11/2006 PUBLIC 69 . l For a list of options to start SAPinst GUI.

.This page is intentionally left blank.

Note For more information. 12. 5. You configure the remote connection to SAP support [page 75].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. You perform the following post-installation steps: 1.sap. 5. 2. You install the SAP License [page 74]. You configure SAP Solution Manager [page 93]. You apply the latest kernel and Support Packages [page 78]. You configure Single Sign-On with Microsoft Lan Manager SSP [page 80]. n You have checked the settings for VM parameters as described in SAP Note 723909. With a newly installed MMC you can start or stop installed SAP instances locally on the host that you are logged on to. You perform a full installation backup [page 79].5 Post-Installation 5 Post-Installation This section provides information on how to perform the post-installation steps of your SAP system. 8. see: help. You perform post-installation steps for Adobe Document Services [page 89]. . You install the SAP Online Documentation [page 74]. 7. you can start or stop the entire system from a single host. 14. You configure Single Sign-On with Microsoft Kerberos SSP [page 84]. You start and stop the SAP system [page 71]. 09/11/2006 PUBLIC 71 . You log on to the SAP system [page 72]. You ensure user security [page 91]. 10. If the MMC is configured for central system administration. You check the Java manuals [page 76] for information that is relevant for running your Java system. 11. You perform initial ABAP configuration [page 75]. 4. 6.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 the SAP Microsoft Management Console (SAP MMC). 13. 9. 3.

2. ABAP Users User User Name Client SAP system user SAP* DDIC 000. All instances listed under the system node. Logging On to the ABAP System 1. If the SAP system is installed on multiple hosts (distributed system). n You add the remote instances to the MMC configuration to start or stop all instances from a single MMC. 3. 5. Right-click the SAP system node and choose Start or Stop. J2EE_ADMIN Prerequisites n You have already started the SAP system. do one of the following: l You configure the MMC manually. see Configuring MMC for Active Directory Services in the SAP MMC documentation. To do so. For more information. 066 000. 001.2 Post-Installation Logging On to the SAP System Procedure 1. l You use the automatic LDAP registration. For more information. 001 ABAP+Java User User User Name Storage: ABAP System Administrator (default) or the name you gave this user during the installation process.5 5.2 Logging On to the SAP System You need to check that you can log on to the SAP system using the following standard users. see Changing the Configuration of the MMC in the SAP MMC documentation. Start SAP Logon on the host where you have installed the front end as follows: n SAP GUI for Windows: Choose Start ® Programs ® SAP Front End ® SAP Logon. n You have already installed a front end. will start or stop in the correct order. . Start the SAP MMC on the SAP system host by choosing Start ® Programs ® SAP Management Console. 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. Note You can also start and stop a UNIX system with the MMC. n SAP GUI for Java: 72 PUBLIC 09/11/2006 .

To correctly establish the URL. The SAP Logon appears. 2. Establish the default J2EE Engine URL. depending on the protocol that you are using: <protocol>://<fully qualified j2ee engine host name>:<protocol_port_number> Example . Example If the J2EE Engine is installed on J2EE instance number 01.2 Post-Installation Logging On to the SAP System 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 SAP GUI for Java. . log on as user SAP* or DDIC. When you have created the entry. proceed as follows: 1. If you installed the J2EE Engine on host saphost06 and the instance number of your J2EE Engine is 15. HTTPS is relevant if you are using Secure Sockets Layer (SSL) communication. For more information about creating new logon entries. Create a logon entry for the newly installed system in the SAP Logon. 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 have installed the J2EE Engine. and is calculated according to the following formula: HTTP Port = 50000 + (100*<instance number>) . 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 . 3. Log on to the J2EE Engine. press F1 . To log on to the J2EE engine for the first time. Example If 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. Establishing the J2EE Engine URL The default URL consists of the installation host name and the port on which the J2EE Engine is listening. enter the following URL: http://saphost06:51500 09/11/2006 PUBLIC 73 .5 5. 2. You can use the HTTP or HTTPS protocol. Logging On to the J2EE Engine You access the J2EE Engine with a URL using a Web browser from your client machines.

you must apply for a permanent license key from SAP. You can always find the up-to-date SAP online documentation at help. enter the following information: n User ID: <J2EE Administrator name> n Password: <J2EE Administrator password> .sap.5 5. When you install your SAP system.sap.com/nw2004s ® SAP NetWeaver ® SAP NetWeaver Library ® Technology Consultant's Guide ® Cross-NetWeaver Configurations ® SAP License Key More Information For more information about SAP license keys. You can display the documentation with a Java-compatible Web browser on all front-end platforms supported by SAP. see SAP Service Marketplace at service.4 Installing the SAP Online Documentation SAP currently provides an HTML-based solution for the online documentation. Implementation Guide (IMG). a temporary license is automatically installed. Glossary. Call transaction RZ11. In the instance profile of every installed SAP instance. This temporary license allows you to use the system for only four weeks from the date of installation. Caution Before the temporary license expires. 2. We recommend that you apply for a permanent license key as soon as possible after installing your system. 5. see: help. . In the Welcome screen. enter the J2EE Engine URL as described above and choose Enter. 5. The start page of the J2EE Engine appears in the Web browser. proceed as follows: 1.com/licensekey.3 Installing the SAP License You must install a permanent SAP license. and Release Notes. 2. set parameter rdisp/j2ee_start from 1 to 0. including the Application Help.sap. Note To deactivate the J2EE Engine. 74 PUBLIC 09/11/2006 .3 Post-Installation Installing the SAP License Logging on to the J2EE Engine 1. 3. Open your Web browser. Log on by choosing EXAMPLES in the upper right corner of the Web page. Procedure For information about the installation procedure for the SAP license.com/nw2004s.

Procedure 1.sap.5 Post-Installation Configuring Remote Connection to SAP Support Process Install the SAP online documentation in your SAP system as described in the README. see the relevant section in Solution Life Cycle Management by Key Capability ® System Management: Operation Section in SAP Documentation Set up operation modes ‒ transaction RZ04 Set up logon groups ‒ transaction SMLG Set up administrators Schedule background jobs Install a printer Configure the system log Configuration ® Operation Modes Configuration ® Logon Load Distribution ® SAP Logon Background Processing ® Authorizations for Background Processing Background Processing SAP Printing Guide Tools for Monitoring the System ® System log ® Configuring the System Log n Configuring work processes For more information about instance profiles. see Solution Life Cycle Management by Key Capability ® System Management ® Configuration ® Profiles ® Profile Files ® Instance Profiles.sap. delivered as part of the installation package. 5. see SAP Service Marketplace at service. 09/11/2006 PUBLIC 75 .5 Configuring Remote Connection to SAP Support SAP offers its customers access to support and a number of remote services such as the EarlyWatch Service or the GoingLive Service.TXT file contained in the root directory of the online documentation DVD. which is where work processes are defined.com/remoteconnection. Go to the following place in the SAP Library: help. 5.5 5.6 Performing Initial ABAP Configuration Here you find information about how to perform initial ABAP system configuration. see Solution Life Cycle Management by Key Capability ® Software Life Cycle Management ® Software Logistics ® Change and Transport System. Therefore.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability 2. n Performing basic operations For more information. Check the documentation on the following configuration steps: n Configuring the transport management system For more information. you have to set up a remote network connection to SAP. For more information.

It is not detailed enough for a production system because the optimal number of each type of work process depends on the system resources and on the number of users working in each SAP system application. Note You must maintain your company address to create ABAP system users. n Installing languages and performing language transport l Installing languages using transaction I18N: u If you want to use English only. l For more information about ITS.7 Post-Installation Checking the SAP Java Documentation .7 Checking the SAP Java Documentation Here you canfind information about the configuration of the J2EE Engine and about SAP Java technology in the SAP Library. . which includes customizing the ABAP system and the business components. see Application Platform by Key Capability ® ABAP Technology ® UI Technology ® ITS / SAP@Web Studio (BC-FES-ITS). For a detailed configuration contact SAP Technical Consulting. n Maintaining address data For more information on maintaining the company address in your SAP system using transaction SU01. l Performing language transport using transation SMLT: For more information on performing the language transport using transaction SMLT. 5. see Solution Life Cycle Management by Key Capability ® Customizing. which is installed automatically with the SAP kernel. For more information on configuring the language settings. This is only an initial configuration to get you started after the installation. Note SAPinst installs SAP systems with a minimum number of work processes.. where you can find the necessary information if you do not want to use the ITS.5 5. you must activate the default language settings once. u If you want to use languages other than English. see SAP Note 742048. you must install them and activate the language settings. see Application Platform by Key Capability ® Business Services ® Business Address Services (BC-SRV-ADR) ® Addresses in User Administration ® Maintenance of Address Data . 76 PUBLIC 09/11/2006 . Activating and configuring the integrated Internet Transaction Server (ITS) n l For more information on activating and configuring the ITS. n Configuring business applications For more information about how to prepare the SAP system for using business applications. see Solution Life Cycle Management by Key Capability ® Software Life Cycle Management ® Software Logistics ® Change and Transport System ® Language Transport. see the online documentation in transaction I18N ® I18N Menue ® I18N Customizing.

This manual contains all the information you need to migrate an application created in J2EE Engine 6. Administration Manual This manual describes how to administer the SAP system. n J2EE Engine system architecture n SAP NetWeaver Java development infrastructure.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Application Platform by Key Capability ® Java Technology. The Architecture Manual describes the integration of the SAP NetWeaver Developer Studio into the SAP development infrastructure. and high availability.sap. It contains information on: n Java cluster architecture including central services. It explains how to use the SAP Netweaver Developer Studio. Note The SAP NetWeaver Developer Studio is the SAP development infrastructure for Java. Java Development Manual This manual describes the technologies for developing Java-based business applications. Go to the following place in the documentation: help. Migration Manual 09/11/2006 PUBLIC 77 .20. focusing on the J2EE Engine.5 5. It contains information on: n System landscape administration n Software life-cycle management . Caution Make sure that you check the mandatory post-installation procedures listed in the Administration Manual under J2EE Engine ® Installation Information ® Post-Installation Procedures. 2. including SAP NetWeaver Developer Studio . which is the SAP Java development environment. Note This part of the manual contains important information about: l Installation information l System Landscape Directory (SLD) l Software Lifecycle Manager (SLM) l Java Support Package Manager l Administration of SAP NetWeaver Java Development Infrastructure (JDI) n n n n J2EE Engine and J2EE Engine security Supportability and performance management Administration and configuration of Web Dynpro runtime environment Administration of the XML Data Archiving Service (XML DAS) . 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.7 Post-Installation Checking the SAP Java Documentation Procedure 1. load balancing.

see SAP Note 212876.com/swdc.8 Post-Installation Applying the Latest Kernel and Support Packages More Information For troubleshooting the J2EE Engine.sap. Apply Support Packages. a) Alternatively.com/ocs-schedules 78 PUBLIC 09/11/2006 . Apply the latest kernel.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 Prerequisites To extract the downloaded SAR files make sure that you use the latest SAPCAR version.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 Service Marketplace.sap. c) Apply Support Packages to your SAP system with the help of the Java Support Package Manager (JSPM). see help. see the SAP Service Marketplace at: service. 2. which you can find on SAP Service Marketplace at service. To exchange the ABAP+Java kernel. you must replace the installed kernel if: n You installed the kernel executables locally on every host. Procedure 1. You need at least SAPCAR 700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR files. n Your central instance host runs on a different operating system than your dialog instance host. In particular.sap. You must always replace the installed kernel with the latest kernel from SAP Service Marketplace. For more information about JSPM and how to use it.5 5. you can use Java Support Package Manager (JSPM). For more information about how to download a kernel. For more information. You can use Java Support Package Manager (JSPM) to apply both the latest ABAP+Java or Java kernel and Java support packages. before you run CTC online configuration.sap. see SAP Note 19466. JSPM uses the Software Deployment Manager (SDM) to apply support packages and patches and to deploy software components. . JSPM is a Java standalone tool that you can use with SAP NetWeaver 04s.com/patches b) Apply Support Packages to your SAP system with the help of the Support Package Manager (formerly called SAP Patch Manager.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Solution Life Cycle Management by Key Capability ® SAP NetWeaver Problem Analysis Guide (PAG) ® J2EE Engine Problem Analysis Scenarios 5. For more information about the availability of Support Packages. Caution You must have applied all ABAP Support Packages. you can download Support Packages from SAP Service Marketplace at: service. transaction SPAM). see the J2EE Engine Problem Analysis Guide at: help.sap.

09/11/2006 PUBLIC 79 . b) Choose Backup Wizard ® Next. or network data and choose Next. drives.9 Post-Installation Performing a Full Installation Backup . and organize individual SAP Notes efficiently. and modifications. b) Choose Emergency Repair Disk. 2. Back up all SAP-specific and all database-related directories: a) Choose Start ® Programs ® Accessories ® System Tools ® Backup. e) Choose Next. Procedure 1. select the Windows directory and all SAP and database-related directories. implement. see the SAP Service Marketplace at: service. n You have stopped: l The SAP system l SAP-related services (SAP<SAPSID>_<instance> and SAPOSCol) l The database n You are logged on as user <sapsid>adm. b) Choose Backup Wizard ® Next. Prerequisites n You have completed client maintenance (for example. c) Select Also Backup the Registry to the Repair directory… When you confirm your entry. the registry is written to diskette. 3. c) Select Only back up the System State data and choose Next. including: \USR\SAP <HOMEDIR> of <sapsid>adm \%WINDIR% e) Choose Next. n You have shut down the SAP system and database. client copy). The Emergency Repair Diskette dialog box appears. select the Backup media type and enter the Backup media or file name. f) Check the information displayed and choose Finish to start the backup.9 Performing a Full Installation Backup You must perform an offline full backup at the end of the installation. Save the registry: a) Choose Start ® Programs ® Accessories ® System Tools ® Backup.com/noteassistant 5. d) In Where to Store the Backup. For more information. c) Select Back up selected files.5 5. d) In What to back up.sap. It also recognizes dependencies between SAP Notes. Support Packages. Note The SAP Note Assistant lets you load. Save the system state data: a) Choose Start ® Programs ® Accessories ® System Tools ® Backup.

dll and the newer version is called gssntlm. For more information on SNC. Since NTLM SSP is already built into Microsoft Windows 32-bit platforms. g) Choose Next. Windows ME. Note The Microsoft NTLM SSP only provides authentication based on a challenge-response authentication scheme.sap. The older version is called gssapi32. you do not need to purchase an additional security product to use SSO. All third-party SNC certified security products offer data integrity and privacy protection. However. 80 PUBLIC 09/11/2006 . Windows 2000 and higher). LAN Manager Security Service Provider (NTLM SSP). 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. The Microsoft NTLM SSP is not available for UNIX or any other operating system. Windows ME. No SAP system user name or password is necessary.dll.com/security Prerequisites n Typically. We distribute two different versions of the wrapper library for Microsoft's NTLM SSP. select the Backup media type and enter the Backup media or file name for the backup. in this scenario. front-end PCs. an authorized user who has logged on to the operating system can access the SAP system simply by selecting it in the SAP logon window or clicking the shortcut. we offer an alternative library (gsskrb5. h) Check the information displayed and then choose Finish to start the backup.10 Post-Installation Single Sign-On with Microsoft Lan Manager SSP f) In Where to Store the Backup. and SAP application servers. we describe the option that is the easiest to implement when using a full 32-bit Microsoft Windows landscape (Windows 9x.dll) must be installed on every application server. n The GSS-API V2 library wrapper must also be installed on every front-end PC. SSO makes it significantly easier for you to manage SAP system users.5 5. see Single Sign-On with Microsoft Kerberos SSP [page 84] . If you want to use these security features. see the SNC User's Guide in the SAP Service Marketplace at service. In this section.dll) that uses the Microsoft Kerberos SSP instead of the NTLM SSP for authentication. you have to obtain a certified security product. For more information. Windows 2000 and higher). Windows NT. 5. see SAP Note 595341. which uses Microsoft’s domain authentication. It does not provide data integrity or data confidentiality protection for the authenticated network connection. n A pure Microsoft Win32 environment is required (Windows 9x. It is a tailored version for SSO with Secure Network Communications (SNC). n Bi-directional trust between Windows domains is required if there are separate domains for users. we provide a library that adheres to the GSS-API V2 interface on one side and that communicates with Microsoft’s NTLM SSP on the other. For more information about how to get the gssntlm. When your system is configured for SSO.dll file.10 Single Sign-On with Microsoft Lan Manager SSP Single Sign-On (SSO) is a secure method of logging on to the SAP system that simplifies the logon procedure without reducing security. If you use Windows 2000 and higher. n The GSS-API V2 library wrapper (gssntlm. . Windows NT.

most operations are successful. Prepare the application server for Single Sign-On [page 81] . 4. d) Change the startup type from manual to automatic. 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.1 Preparing the Application Server for Single Sign-On 1.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. Prepare SAP GUI and SAP logon for Single Sign-On [page 82]. n For more information on how to improve the security of your system with third-party products.10. .dll>) snc/identity/as =p:<DOMAIN_NAME>\SAPService<SAPSID> SAPService<SAPSID> is the user who runs the SAP system. Set the environment variable SNC_LIB to the location of the library. b) Select the service NT LM Security Support Provider. Start the service NT LM Security Support Provider: a) Choose Start ® Programs ® Administrative Tools ® Services. The combination of Windows ANSI (=ISO Latin 1) and the default SAP code page 1100 provides the same encoding of 8-bit characters and permits the use of 8-bit characters with gssntlm. n When the code page of the SAP system is different from the code page on the Windows machines.5 5. Copy the gssntlm. Therefore. In the central instance profile. 2. it is not possible to enter Windows user IDs that contain 8-bit characters into the USRACL table (for example. 09/11/2006 PUBLIC 81 . 3.dll. If you use a local account for SAPService<SAPSID>. <DOMAIN_NAME> Note is the Windows domain of this user.10 Post-Installation Single Sign-On with Microsoft Lan Manager SSP n We recommend that you use the 7-bit ASCII character set for all Windows user IDs. 3. do not work with a local account for SAPService<SAPSID>. 2. c) Choose General. any operations or communications where the SAP system initiates SNC-protected communication to a remote machine. However. use a domain account. see: help. 5.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Security ® Network and Transport Layer Security ® Secure Network Communications Process Flow To implement SSO with the Microsoft NTLM SSP you: 1. by calling transaction SU01).dll file see SAP Note 595341.sap. Map SAP system users to Windows users for Single Sign-On [page 83].

you have to use these additional parameters at least once after enabling SNC. Once the mapping (at least for the administrator) has been entered. Procedure 1.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 LAN Manager SSP [page 80].dll file. %SystemRoot%\system32 and rename the file to sncgss32. Prerequisites You have completed Preparing the Application Server for Single Sign-On (SSO) [page 81]. log off and log on to your Windows system again as the same user.dll file to the SAP GUI directory. <DRIVE>:\<SAPGUI_PATH>\gssntlm. You can do this using one of the following methods: n Copy gssntlm. 5. b) In User Variables for <user> enter the following: Variable: SNC_LIB Value: <DRIVE>:\<SAPGUI_PATH>\gssntlm. for example.5 5. n Copy gssntlm. you can disable further password-based logons by removing the respective profile parameters. Set the required logon options to activate SSO: a) In the SAP logon window. for example. Stop and restart the SAP system to activate the profile parameters.dll to a location of your choice and set the environment variable SNC_LIB to that location.10.dll c) Confirm your entries with OK.dll a) Right-click My Computer and choose Properties ® Advanced ® Environment Variables.dll to a directory of the default search path. 82 PUBLIC 09/11/2006 . see SAP Note 352295. To log on to the SAP system as an administrator to maintain the mapping of Windows user accounts to SAP system user IDs (user and client).dll file. 2.dll This is the default file name that SNC uses when SNC_LIB is neither entered on the command line nor available in the environment. 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. d) To activate the new environment variable setting.10 Post-Installation Single Sign-On with Microsoft Lan Manager SSP Additional SNC Parameters The following profile parameters let you continue with password-based access to the SAP system when SNC has been enabled. Changes to SNC profile parameters always require an application server restart to take effect. 3. For downloading the gssntlm. right-click an entry and choose Properties. The variable specifies the path to the gssntlm. b) Select the Network tab and activate Activate Secure Network Communication. Set the Windows environment variable SNC_LIB on the PC where your SAP GUI runs. Copy the gssntlm.

09/11/2006 PUBLIC 83 . If the system HWA is running on account SAPServiceHWA of the DEC_NT domain. 3.10. 2. 5. the logon screen is skipped.3 Mapping SAP System Users to Windows Users for Single Sign-On You need to perform this procedure as part of Single Sign-On with Microsoft LAN Manager SSP [page 80]. you can enable SAP system users to log on with Single Sign-On (SSO) by mapping them to Windows users. Choose Tools ® Administration ® User Maintenance ® Users or call transaction SU01. Choose SNC. enter: p:<DOMAIN_NAME>\SAPService<SAPSID> <DOMAIN_NAME> is the Windows domain that the user SAPService<SAPSID> Example belongs to.5 5. 5. you enter: p:DEC_NT\SAPServiceHWA Result The SAP Logon window now displays an icon with a small yellow key beside the system entry. Log on to the SAP system. Enter the name of the SAP system user and choose User names ® Change. 4. When the SAP administrator has entered the mapping [page 88] between a user's Windows Account and the user’s SAP system user ID. Prerequisites You 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. This indicates that SSO is active. unless the profile parameter snc/force_login_screen = 1 is present in the instance profile of the application server. . the application is opened without requiring the user to enter a user name and password. When you have configured your system. 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 ID of the Windows user.10 Post-Installation Single Sign-On with Microsoft Lan Manager SSP c) In the SNC name field. In SNC name. p is a prefix that all SNC names require. The User Maintenance window appears. If only one possible match exists between the Windows account and the SAP system user ID. the next time this SAP system user logs on to the system.

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. 7. Process Flow To implement SSO with the Microsoft Kerberos NTLM SSP.5 5. 3. SSO makes it significantly easier for you to manage SAP system users. the Microsoft Kerberos Security Service Provider (SSP) is interoperable with Kerberos implementations from other vendors and suppliers. Prepare the central instance [page 85]. you have to: 1. The advantage of the Kerberos SSO solution is that the security information that has to be exchanged between the SAP front end and the SAP application server is encrypted. Example When using gsskrb5.11 Post-Installation Single Sign-On with Microsoft Kerberos SSP . It is suitable if you use Windows 2000 and higher in your system landscape. Result You have now finished setting up SSO. Select Insecure communication permitted. The Application Programming Interface (API) and Kerberos provide the security required for authentication. 4. To use SSO with application servers on UNIX and Windows front ends with gsskrb5.11 Single Sign-On with Microsoft Kerberos SSP Kerberos Single Sign-On (SSO) is a secure method of logging on to the SAP system that simplifies the logon procedure without reducing security. you might have to purchase a Kerberos implementation for the UNIX machines. Configure the SAP front ends [page 86].dll. enter: p:SAP_ALL\Kissnerj 6. Map SAP users to Windows users [page 88]. 2. This lets the user work in a different domain because it permits the user to access the system without SSO. which is based on the Generic Security Service API (GSS-API) interface . Prerequisites SSO based on Kerberos can only be set up for users that are members of a Windows 2000 and higher domain. Save your entries. 5. 84 PUBLIC 09/11/2006 . No SAP system user name or password is necessary. belonging to the domain SAP_ALL.dll. In contrast. encryption is not implemented for SSO with Microsoft NTLM SSP. Configure the SAP logon [page 87]. Example For the Windows user Kissnerj.

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. most operations are successful.SAP-AG. <DOMAIN_NAME> Note . Caution is the Windows domain that the SAPService<SAPSID> user belongs to. Make sure that you enter uppercase and lowercase correctly. Therefore. you need to adapt the central instance profile and make sure that the necessary Dynamic Link Library (DLL) is located in the Windows directory. For more information about how to get the gsskrb5.SAP-AG.5 5. However. Procedure 1.dll>) snc/identity/as =p:<DOMAIN_NAME>\SAPService<SAPSID> SAPService<SAPSID> is the user who runs the SAP system. do not work with a local account for the SAPService<SAPSID> user. see SAP Note 595341. it is normally SAPService<SAPSID>. . Although you can freely choose the Windows account under which the SAP system runs. 09/11/2006 PUBLIC 85 .dll file.11. In the instance profile of the central instance. for example. set the SAP parameters: snc/enable = 1 snc/gssapi_lib =<DRIVE>:\%windir%\system32\gsskrb5. If you use a local account for the SAPService<SAPSID> user.DE. and the SAPService<SAPSID> user are case-sensitive. use a domain account.dll file to the following directory on the central instance: Drive:\%windir%\system32. 2. Copy the gsskrb5. In the central instance profile.DE.11 Post-Installation Single Sign-On with Microsoft Kerberos SSP 5. <DOMAIN_NAME> is the Windows domain of this user. for example: p:SAPServiceC11@NT5.dll snc/identity/as =p:SAPService<SAPSID>@<DOMAIN_NAME> <DOMAIN_NAME> NT5. any operations or communications where the SAP system initiates SNC-protected communication to a remote machine.1 Preparing the Central Instance To set up Single Sign-On (SSO) for Kerberos.

use a domain account. you can disable further password-based logons by removing the respective profile parameters. you choose between the following approaches: n Configure each SAP front end individually You configure each machine where the SAP front end is running. any operations or communications where the SAP system initiates SNC-protected communication to a remote machine. 3. most operations are successful. However. Additional SNC Parameters The following profile parameters let you continue with password-based access to the SAP system when SNC has been enabled. Prerequisites You have completed Preparing the Central Instance [page 85]. 86 PUBLIC 09/11/2006 . The wizard SAP Kerberos SSO Support automatically starts and configures the SAP front end for SSO. n Configure all SAP front ends automatically You define a Group Policy for a Windows domain. Configuring SAP Front Ends Individually 1.MSI file. n If you use a local account for SAPService<SAPSID>. see SAP Note 352295. 2. Stop and restart the SAP system so that the profile parameters take effect. Log on to the host where the SAP front end is running. Copy the SAPSSO. it is normally SAPService<SAPSID>.2 Configuring the SAP Front End To configure the SAP front end for SSO. Double-click the SAPSSO. you have to use these additional parameters at least once after enabling SNC. This policy causes the wizard for configuring SSO to be started automatically in the background the next time any member of the domain logs on to an SAP front end. For downloading the SAPSSO. do not work with a local account for SAPService<SAPSID>. Once the mapping (at least for the administrator) has been entered.MSI file. Therefore. These approaches are described below. 5. Note n Although you can freely choose the Windows account under which the SAP system runs. 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.11 Post-Installation Single Sign-On with Microsoft Kerberos SSP .5 5.11. To log on to the SAP system as an administrator to maintain the mapping of Windows user accounts to SAP system user IDs (user and client).MSI program to a local directory or to a shared directory on the network.

. see SAP Note 595341. The dialog box Active Directory Users and Computers appears.11 Post-Installation Single Sign-On with Microsoft Kerberos SSP Configuring SAP Front Ends Automatically 1.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.MSI file. 11. The next time any user logs on to the domain with the SAP front end.MSI from the shared location. For each of the systems or machines in the list for which you want to implement SSO.11. Prerequisites n You have completed the following: l Preparing the Central Instance [page 85] l Configuring the SAP Front End [page 86] Procedure 1. select Activate Secure Network Communication. The Open dialog box appears. 2. Choose Start ® Programs ® Administrative tools ® Active Directory Users and Computers. Choose Edit to define the contents of the policy. 10. NT5. 2. enter a name for the new policy object. The dialog box <Domain_Name> Properties appears. the wizard SAP Kerberos SSO Support automatically starts and configures the front end for SSO. 6. For more information about how to get the SAPSSO. Select Assign and confirm with OK.MSI to a shared directory. Right-click the domain for which you want to set up SSO and choose Properties. Choose Group Policy ® New to start creating a new policy object. for example. 8. 4. 3. 09/11/2006 PUBLIC 87 . In SNC name. Specify the path with the UNC name (\\<hostname>\<share>). Right-click Deploy Software and choose New ® Package. Right-click an entry in the SAP Logon window and choose Properties. Select the file SAPMSSO. 9. such as SAPSSO. In the Group Policy Editor choose User Configuration ® Software Settings ® Software Installation. follow the procedure below. 7. 12. Copy the program SAPSSO. You have now created a new Group Policy. 3. 5. enter: p:SAPService<SAPSID>@<DOMAIN_NAME> where <DOMAIN_NAME> is. 5. In the Network tab. In Group Policy Object Links. The dialog box for creating a new policy object appears.5 5. Log on to a front-end machine as domain administrator of the Windows domain.SAP-AG. The Deploy Software dialog box appears.DE.

Choose OK to confirm your entries.5 5. This lets the user work in a different domain because it permits the user to access the system without SSO.4 Mapping SAP Users to Windows Users Prerequisites You 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. 4. 5. 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 domain that the user is logged on to. Example For the user Kissnerj. 5. Save your entries.SAP-AG. In SNC name.DE 6. Log on to the SAP system as administrator. belonging to the domain NT5.SAP-AG. . Choose Tools ® Administration ® Maintain Users ® Users or call transaction SU01.11 Post-Installation Single Sign-On with Microsoft Kerberos SSP . 3. Note n Enter the same string that you entered in the central instance profile for snc/identity/as If the system C11 is running on account SAPServiceC11 of the domain NT5. The SAP Logon window now displays an icon with a key beside the system entry. Select Insecure communication permitted. 7.DE . for example. you would enter: P:SAPServiceC11@NT5. the SNC name field is already filled. This indicates that Single Sign-On is active for the system. Enter the name of the SAP user and choose User names ® Change.11. C11 (PUBLIC). 2.DE n If the entry you selected in the logon dialog box is a group entry. Choose SNC.SAP-AG.SAP-AG.DE. 4. enter: p:kissnerj@NT5. 88 PUBLIC 09/11/2006 . Result Kerberos SSO is now set up. The User Maintenance window appears.

Creating Role ADSCallers and Assigning it to ADSUSER 1. Enter ADSCallers in the Role field. 5. choose Role ® Save. Choose User Names ® Change. 4. Choose Role ® Create. 3. 2.12. 5. Choose the User tab and assign the user ADSUSER in the User ID field. After the installation you have to assign the required authorization roles manually to these users in the ABAP system. Call transaction PFCG. Log on to the ABAP system with user DDIC or SAP*. Enter ADS_AGENT in the User field. 5. Log on to the ABAP system [page 72]. 09/11/2006 PUBLIC 89 .1 Assigning Roles to Users ADSUSER and ADS_AGENT During the installation SAPinst created the users ADSUSER for basic authentication and ADS_AGENT for processing forms between an ABAP and a Java environment. passwords. and RFC destination.12.2 Installation Check and Quick Tests for Adobe Document Services This procedure shows you how to check your installation of Adobe Document Services (ADS) entries for the correct user. n You perform quick tests for Adobe Document Services (ADS) [page 89].5 5. 3. Choose the Roles tab and assign the role SAP_BC_FP_ICF to the user ADS_AGENT. 5. security role. 2. 6. as described below. Call transaction SU01. Assigning Role SAP_BC_FP_ICF to ADS_AGENT 1. On the Create Roles screen.12 Post-Installation Post-Installation Steps for Adobe Document Services 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]. 4.

). Note This procedure contains only minimal configuration steps to check if the ADS installation with SAPinst was successful. Enter the following URL: http://<J2EE_host>:<J2EE_port>/AdobeDocumentServices/Config Note . 3. 5. Procedure Checking the User and Password 1.5 5. see the configuration guide for Adobe Document Services: n On SAP Service Marketplace at: service. Enter ADSUser as user name and the password you entered for this user previously. the page does not change and Submit remains on the screen. Call transaction SE38.sap. Checking the ABAP Connection 1. Choose Submit. Enter the name of the test report FP_PDF_TEST_00. Result If the setup is correct. the system displays the version number.. 90 PUBLIC 09/11/2006 ..com/nw2004s ® SAP NetWeaver Library ® Technology Consultant's Guide ® Additional Cross-NetWeaver Configurations ® Adobe Document Services . Note You can ignore the message Required stream: “PDFDocument” not found. Choose Send without entering any parameters. Open a web browser.Configuration Guide NW 2004s n In the SAP Library at: help.12 Post-Installation Post-Installation Steps for Adobe Document Services . 6.sap. Choose rpdata(test. 3. Result If the setup is correct. . 2.Configuration. If the setup is not correct. 2. 7. The web page of the Web service AdobeDocumentServices is displayed. the system displays the version number in the response area. 4. 4.com/adobe ® Interactive Forms Based on Adobe Software ® Media Library ® Documentation ® Adobe Document Services . For detailed configuration documentation. Note that the entries in the URL are case-sensitive. Log on to your SAP system. Choose Test. Choose Execute ( F8 ).

Therefore. 001 and 066. be aware that SAP system users might exist in multiple SAP system clients (for example. either by using the Secure Sockets Layer (SSL) protocol for HTTP connections.sap. 5. Make sure that you perform this procedure before the newly installed SAP system goes into production. Therefore. secure location ‒ such as a DVD ‒ and then delete the installation directory. User exists at least in SAP system client 066. User exists at least in SAP system clients 000 and 001. or Secure Network Communications (SNC) for the SAP protocols dialog and RFC. Prerequisites If you change user passwords.com/securityguide: ABAP+Java Users User User Name SAP* Comment SAP system user User exists at least in SAP system clients 000.sap. Recommendation In all cases.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Security ® Network and Transport Layer Security Caution . . Procedure For the users listed below. DDIC EARLYWATCH SAPCPIC 09/11/2006 PUBLIC 91 . take the precautions described in the relevant SAP security guide. Check your settings for the ABAP connection. the user ID and password are only encoded when transported across the network. the system displays a dialog box with input fields for the user and password. you also need to copy the installation directory to a separate.13 Post-Installation Ensuring User Security If the setup is not correct. For security reasons.13 Ensuring User Security You need to ensure the security of the users that SAPinst creates during the installation. you need to change the passwords in all the relevant SAP system clients. see: help. User exists at least in SAP system clients 000 and 001.5 5. For more information. we recommend using encryption at the network layer. which you can find on SAP Service Marketplace at service. if a user was copied as part of the client copy).

For more information. Users for Adobe Document Services (ADS) ADSUSER User exists at least in SAP system clients 000 and 001. ABAP API user for System Landscape Directory (SLD) (optional) The name that you gave this user during the installation. whenever you change the administrator’s password.5 5. 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 during the installation or the default name J2EE_ADMIN This user’s password is stored in secure storage. Note ADS_AGENT Data supplier user for System The name that you gave this user during Landscape Directory (SLD) the installation. Therefore. you must also change the password in secure storage. User exists at least in SAP system clients 000 and 001. User exists at least in SAP system clients 000 and 001. Note SAPinst created this user automatically if you chose Configure local SLD during the installation. . User exists at least in SAP system clients 000 and 001. The recommended name is SLDAPIUSER. see Checking the SAP Java Documentation [page 76]. ‒ Guest The name that you gave this user during the installation or the default name J2EE_GUEST ‒ Communication user for the The name that you gave this user during J2EE Engine the installation or the default name SAPJSF. you must also change the password in secure storage.13 Post-Installation Ensuring User Security User User Name Comment Administrator The name that you gave this user during the installation or the default name J2EE_ADMIN This user’s password is stored in secure storage. ‒ Guest The name that you gave this user during the installation or the default name J2EE_GUEST ‒ Communication user for the The name that you gave this user during J2EE Engine the installation or the default name SAPJSF 92 PUBLIC 09/11/2006 . Therefore. SAPinst created this user automatically if you chose Configure local SLD during the installation. whenever you change the administrator’s password. see Checking the SAP Java Documentation [page 76]. (optional) The recommended name is SLDDSUSER. For more information. .

see the documentation Configuration Guide SAP Solution Manager 4. Note ADS_AGENT Data supplier user for System The name that you gave this user during Landscape Directory (SLD) the installation. . User exists at least in the clients 000 and 001 of the ABAP system. User exists at least in the clients 000 and 001 of the ABAP system. 5. SAPinst created this user automatically if you chose Configure local SLD during the installation. 09/11/2006 PUBLIC 93 .5 5.0 SR1 on SAP Service Marketplace at http://service.sap. Call transaction SPRO. n All activities under Scenario Specific Settings are optional and depend on the functionalities of SAP Solution Manager that you want to use. Note SAPinst created this user automatically if you chose Configure local SLD during the installation. (optional) The recommended name is SLDDSUSER. 2. Log on the client 000 of the SAP Solution Manager system. 3.sap.0 ® Setup_Guide_Solution_Manager_Diagnostics_SPS current stack>.0 SR1. Choose SAP Reference IMG ® SAP Solution Manager Implementation Guide ® SAP Solution Manager n All activities under Basic Settings are mandatory to ensure minimum SAP Solution Manager functionality.14 Configuring SAP Solution Manager You have to configure your SAP Solution Manager system. The recommended name is SLDAPIUSER. .com/solutionmanager ® SAP Solution Manager ® Installation Guides ® Release 4. For more information. proceed as follows: 1.0. Configuring the ABAP Part To configure the ABAP part of SAP Solution Manager 4. ABAP API user for System Landscape Directory (SLD) (optional) The name that you gave this user during the installation. Configuring the Java Part To configure Solution Manager Diagnostics see the documentation Supportability Setup Guide for Solution Manager Diagnostics SAP NetWeaver 04S SP Stack <current stack> on SAP Service Marketplace at http://service. User exists at least in the clients 000 and 001 of the ABAP system.14 Post-Installation Configuring SAP Solution Manager User User Name Storage: ABAP System ADSUSER Comment Users for Adobe Document Services (ADS) User exists at least in the clients 000 and 001 of the ABAP system.com/solutionmanager ® SAP Solution Manager ® Installation Guides ® Release 4.

This page is intentionally left blank. .

1 Database Installation for Multiple Components with MS SQL Server Each SAP system in your mySAP environment needs its own database back end. and scalability. flexibility. you can install multiple. n Exclusive database server In this system landscape. independent SQL Server instances on a single database server. They differ with respect to hardware requirements. like the following two. each database server (with or without a central instance) hosts exactly one SAP database. n Named SQL Server instances With the use of named instances. but from an administration point of view are completely independent from each other. This option. you configure user management to use an LDAP directory [page 105]. Contrary to named instances. the SQL Server Windows process. this is the simplest solution. Entries in the Services File Created by SAPinst [page 105] Deleting an SAP System [page 106] SAP System Security on Windows [page 108] Automatic Creation of Accounts and Groups [page 109] Manually Granting User Rights for the Installation [page 111] Troubleshooting [page 112] 6. database administration. memory and disk resources. These instances share CPU. With MS SQL Server you have the following options to distribute your systems across the available hardware resources.6 Additional Information 6 Additional Information The following sections provide additional information about optional preparation and post-installation tasks: Preparation n n n n n Database Installation for Multiple Components with MS SQL Server [page 95] Installation of Multiple Components in One Database [page 97] Integration of LDAP Directory Services [page 99] Preparing the Active Directory [page 101] Preparing User Management with an External ABAP system [page 102] Post-Installation n n n n n n n If required. requires careful hardware sizing to avoid performance bottlenecks and scalability problems. It is the most scalable setup. This option is typically chosen for medium-sized and large production and development systems. and 09/11/2006 PUBLIC 95 . From an installation planning perspective. but it requires the most hardware. n Multiple databases in an SQL Server instance SQL Server lets you operate multiple user databases in a single SQL Server instance. the databases share the temporary system database tempdb.

you must decide which instance type you want to install.1 Default or Named MS SQL Server Instances When you install MS SQL Server. system databases and utilities exist only once and have to be shared by all SAP databases. n Multiple Components in One Database (MCOD) Multiple database back ends are stored in the same database. This option requires careful hardware sizing to avoid performance bottlenecks and scalability problems. In a less frequently implemented configuration. Note A default instance is recommended. Default Instance A default instance is the most common form of an MS SQL Server installation in an SAP environment. Named Instance The advantage of named instances is that you can set up several SAP databases on the same machine and administer each one separately with its own copy of the MS SQL Server. In this configuration. each in its own database schema.6 6.1. The main components of the MS SQL Server are available exclusively for each instance and can be used only by that instance. Typically. Therefore. .1 Additional Information Database Installation for Multiple Components with MS SQL Server the SQL Server memory pool. you can install two different types of instances: n Default instance n Named instance When you plan your system configuration. This option requires careful hardware sizing to avoid performance bottlenecks and scalability problems. It can be a flexible solution for small and medium-sized systems. Only a few resources such as client utilities have to be shared by all the instances because they are only installed once. but at the same time requires less system resources. if you plan to install only one SAP database instance on a computer. For the database administrator. More Information n Default or Named MS SQL Server Instances [page 96] n Multiple Components in One Database (MCOD) [page 97] 6. one MS SQL Server instance is installed together with a single SAP database. the MS SQL Server components such as executables. this setup is less scalable than named instances. its simplicity makes it an attractive solution for small mySAP environments. a single MS SQL Server instance is installed together with more than one SAP database on the same computer. all MS SQL Server components and functionality are exclusively available for the SAP database. the database containing these multiple components looks very much like a single entity. certain administrative tasks on one database cannot be performed in isolation without affecting the other databases. The following clarifies the difference between the two. In this type of configuration. As all the databases on the computer have to be managed with a single copy of the MS SQL Server. While this approach is not as flexible as the other options. During the 96 PUBLIC 09/11/2006 .

The following graphic illustrates a computer where two MS SQL Server named instances have been installed for two SAP databases. Example You install an SAP NetWeaver central system and an SAP CRM central system in a single database.6 6. . . if you plan to install more than one SAP database instance on the same machine. Several named instances and the default instance can coexist on the same computer and function in isolation of each other. This is called Multiple Components in One Database (MCOD). Figure 9: 6.2 Installation of Multiple Components in One Database (Optional) You can install multiple SAP systems in a single database. each named instance is given a name that is the same as the SAP system name.2 Additional Information Installation of Multiple Components in One Database (Optional) installation. Note A named instance is recommended. 09/11/2006 PUBLIC 97 . thus enabling a unique assignment of instances to SAP databases. <SAPSID1> and <SAPSID2>.

The same applies to memory resources and disk space. Constraints . you calculate the CPU usage for an MCOD database by adding up the CPU usage for each individual SAP system. if you need to restore a backup.com/sizing. see the SAP Service Marketplace at service. For more information on the SAP Quick Sizer. No extra effort is required because the MCOD installation is fully integrated into the standard installation procedure. We are releasing this technology on all the major databases for the SAP system. and recovery n Increased security and reduced database failure for multiple SAP systems due to monitoring and administration of only one database n Independent upgrade In an MCOD landscape you can upgrade a single component independently from the other components running in the same database. Features n Reduced administration effort n Consistent system landscape for backup. We recommend that you run MCOD systems in the same context. assuming that the upgraded component runs on the same database version. n In the event of database failure. We do not recommend that you mix test. n Improved sizing required In general. development. Using this technology is as easy as installing a separate component. . system copy. and production systems in the same MCOD. see the SAP Service Marketplace at service. be aware that all other components are also affected.sap. n MCOD is released for Unicode installations. all SAP systems running on the single database are affected. administration. Note Special MCOD considerations and differences from the standard procedure are listed where relevant in the installation documentation. With MCOD we distinguish two scenarios: n The installation of an SAP system in a new database n The installation of an additional SAP system in an existing database Prerequisites n For more information on MCOD and its availability on different platforms. You can size multiple components in one database by sizing each individual component using the SAP Quick Sizer and then adding the requirements together. However.com/mcod.2 Additional Information Installation of Multiple Components in One Database (Optional) MCOD is available with all SAP components. it is an option of the database instance installation. A prerequisite is that the MCOD system contains Unicode instances only. SAP does not support mixed solutions. Instead. MCOD is not an additional installation service. in line with our commitment to deliver platform-independent solutions. Recommendation We strongly recommend that you test MCOD in a test or development system.6 6. 98 PUBLIC 09/11/2006 .sap.

you can configure the SAP system to use this feature. which defines: n The communication protocol between the SAP system and the directory n How data in the directory is structured.sap. n For the second SAP system. l De-installing a single component from an MCOD landscape requires some additional steps. n As SAPinst turns off database logging during the database load phase of the installation. Note The SAP system can interact with the Active Directory using the LDAP protocol. If an LDAP directory is available in your corporate network. Only valid for: HA (MSCS) n MSCS only: You cannot install multiple components in one database with Microsoft Cluster Service (MSCS).3 Additional Information Integration of LDAP Directory Services (Optional) n Automated support in an MCOD landscape for the following administrative tasks depends on your operating system and database: l Copying a single component from an MCOD landscape to another database at database level is not possible. you need to plan downtime for all MCOD systems sharing the database. You can use a remote connection to SAP support to request help with these tasks. the SAP system can take advantage of the information stored there. End of: HA (MSCS) n For the first SAP system. accessed. Prerequisites You can only configure the SAP system for Active Directory services or other LDAP directories if these are already available on the network. . In the following text.com/remoteconnection. For more information on MSCS. make sure that DBSID is the same as for the first SAP system installed in this database. you can configure the SAP system to use the information available there. the Active Directory is automatically 09/11/2006 PUBLIC 99 . In addition. thus avoiding redundancy and inconsistency.6 6. see Microsoft Cluster Installation.3 Integration of LDAP Directory Services (Optional) The Active Directory is a Lightweight Directory Access Protocol (LDAP) directory. make sure that you use the same DBSID as for the first SAP system. For example. a correctly configured SAP system can read information from the directory and also store information there. LDAP is a feature of Windows 2000 or higher that allows important information within a corporate network to be stored centrally on a server. directories other than the Active Directory that implement the LDAP protocol are called generic LDAP directories. it gives an overview of the configuration steps required to use an SAP system with the directory. This section explains the benefits of using the SAP system with the LDAP directory. 6. You have to perform a homogeneous system copy with R3load instead. For example. For more information see service. The advantage of storing information centrally for the entire network is that you have to maintain data only once. or modified If a directory other than the Active Directory also supports the LDAP protocol. if there is an LDAP directory on a UNIX or Windows server. As of Windows 2000 or higher.

you can configure the SAP Logon in the sapmsg. Features In the SAP environment. MMC The MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central location. If you configure SAP logon to use the LDAP directory. you can exploit the information stored in an Active Directory or generic LDAP directory by using: n SAP Logon n The Microsoft Management Console (MMC) For more information on the automatic registration of SAP components in LDAP directories and the benefits of using it in SAP Logon and MMC. For more information. A generic LDAP directory is an additional component that you must install separately on a UNIX or Windows server. For more information. For more information. If the SAP system has been prepared correctly.ini file contains the following: [Address] Mode=LDAPdirectory LDAPserver= LDAPnode= LDAPoptions= Distinguish the following cases: n If you use an Active Directory. Integrating the Active Directory as a source of information has advantages for the MMC. n You must specify the directory servers (for example. As a result.3 Additional Information Integration of LDAP Directory Services (Optional) available on all domain controllers.com/msplatforms ® Microsoft ® Windows Server SAP Logon Instead of using a fixed list of systems and message servers. you can use LDAPnode to specify the distinguished name of the SAP root node. see the documentation SAP System Information in Directory Services on SAP Service Marketplace at service. LDAPserver=pcintel6 p24709) if either of the following is true: l The client is not located in the same domain forest as the Active Directory l The operating system does not have a directory service client (Windows NT and Windows 9X without installed dsclient). It can read system information straight from the directory that automatically registers changes to the system landscape.6 6. it queries the directory each time Server or Group selection is chosen to fetch up-to-date information on available SAP systems. up-to-date information about all SAP application servers. see the SAP system profile parameter ldap/servers. and parameter settings is always available in the MMC. n For other directory services. the MMC presents and analyzes system information that it gathers from various sources. you must set LDAPoptions=“DirType=NT5ADS”. including the Active Directory. see the SAP system profile parameter ldap/saproot. To use LDAP operation mode. see the SAP system profile parameter ldap/options. make sure that the sapmsg. their status.sap. 100 PUBLIC 09/11/2006 .ini configuration file to find SAP systems and their message servers from the directory.

Configuration Tasks for Generic LDAP Directories To prepare the SAP system to use generic LDAP services. you can simplify administration by using the MMC in a distributed environment that implements the mySAP Business Suite components SAP BW. You do this during the central instance installation using the SAPinst tool. You do not need to manually register changes in the system configuration. For more information on how to enable interaction between a generic LDAP directory and the SAP system.4 Preparing the Active Directory (Optional) If you decided to use LDAP directory services. You perform all these tasks using SAPinst with the option Configure Active Directory for SAP System. SAPinst prompts you for information about the Active Directory and then configures the system accordingly. SAPinst prompts you for information about the Active Directory and then configures the system accordingly. You do this during the central instance installation using the SAPinst tool. You do this by running the script ldappasswd. Configuration Tasks for Active Directory To enable an SAP system to make use of the features offered by the Active Directory. SAP SRM. we especially recommend that you use the MMC together with Active Directory services. You configure the LDAP directory to store SAP data. such changes are automatically updated in the directory and subsequently reflected in the MMC. For example. 3.4 Additional Information Preparing the Active Directory (Optional) If you need to administer distributed systems. You set up a user with a password on the server where the SAP system is running to permit the system to access and modify the LDAP directory. you need to prepare the Active Directory. You configure the SAP system to enable interaction with the LDAP directory. you must configure both the Active Directory and the SAP system: 1. see Preparing the Active Directory (Optional) [page 101]. You prepare the Active Directory so that it can store SAP data.6 6. 2. Instead. The SAP system can then use the Active Directory to store and access data.sap. This involves extending the directory schema and creating a container for the SAP data. see the documentation SAP System Information in Directory Services in the SAP Service Marketplace at service. You configure the SAP system to enable interaction with the Active Directory. To prepare the directory. You can keep track of significant events in all of the systems from a single MMC interface. you must perform several steps to configure both the LDAP directory and the SAP system: 1. SAP SCM. This involves extending the schema for the SAP data types. you use SAPinst to automatically: 09/11/2006 PUBLIC 101 .com/msplatforms ® Microsoft ® Windows Server More Information Preparing the Active Directory [page 101] 6. For more information. and defining accounts that allow directory access. creating a root container for the storage of SAP-specific information. 2. and SAP CRM.

Note For more information on how to set up a Netscape / iPlanet directory server. n For more information about the input parameters. and this user does not yet exist. administrator. 2. When you have made these entries. position the cursor in the field of the respective parameter and press the F1 key. see the documentation SAP System Information in Directory Services on SAP Service Marketplace at service. In this case. Run SAPinst and choose <SAP System> ® Additional Software Life-Cycle Tasks ® Additional Preparation Tasks ® Active Directory Configuration.6 6. Follow the instructions in the SAPinst dialogs and enter the required parameters. you need to work out a concept for the communication. you can also deploy user management for an external ABAP system. These are the group SAP_LDAP and the user sapldap.5 Additional Information Preparing User Management for an External ABAP System n Extend the Active Directory schema to include the SAP-specific data types n Create the domain accounts required to enable the SAP system to access and modify the Active Directory.sap. SAPinst extends the Active Directory schema for the SAP system.5 Preparing User Management for an External ABAP System For a Java system. and guest users for each engine. . Note n When you are prompted for the password of the sapldap user. 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 to read and write to the directory . You can take one of the following approaches: 102 PUBLIC 09/11/2006 . 3. 6. If you want to connect more than one Java system to the same ABAP system. Log on as user with domain administrators rights. make sure that the password consists of at least 5 characters. you configure the User Management Engine (UME) of the J2EE Engine for the user management of a separate ABAP system.com/msplatforms ® Microsoft ® Windows Server Prerequisites A Windows domain controller with an Active Directory is installed on the network. Procedure 1.

com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Security ® Identity Management ® Users and Roles (BC-SEC-USR) ® SAP Authorization Concept ® Organizing Authorization Administration ® Organization if You Are Using the Profile Generator ® Role Maintenance ® Role Maintenance Functions ® Changing Standard Roles Administration of the ABAP system Perform the following administration steps in the ABAP system: 1. n If you change the administrator user’s password. see the SAP Library at help. so you do not need to generate any profiles. n In transaction PFCG. You do not need to maintain authorization data or generate any profiles for that role.com/nw2004s ® SAP NetWeaver Library ® SAP NetWeaver by Key Capability ® Security ® Identity Management ® User Management Engine .sap.sap. n For more information. Prerequisites n The ABAP system is based on at least SAP Web AS ABAP release 6. In transaction SU01 create a new communication user and assign it to the role SAP_BC_JSF_COMMUNICATION_RO. create a role named ADSCallers. 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. Note For more information about role maintenance. Recommendation For security reasons. check that the roles SAP_J2EE_ADMIN.6 6. 09/11/2006 PUBLIC 103 . you must also change the password in secure storage on all of the connected J2EE Engines . we recommend the first approach.20 SP25. this change affects all connected engines. Initially more administration to create the users in the ABAP system Interdependencies between the connected engines: n If you change the password of any of the users on the ABAP system. n In transaction PFCG.5 Additional Information Preparing User Management for an External ABAP System Approach Advantages Disadvantages Each Java system uses different users All Java systems use the same configuration No interdependencies between the connected engines You create the users only once and enter the same information for every Java system that you install. SAP_J2EE_GUEST and SAP_BC_FP_ICF exist. The procedures below assume that you are using the first approach. Neither role contains any ABAP permissions. see: help.

to change. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_GUEST. or delete users) with Java tools. assign the role ADSCallers to this user. We recommend that you name the user SAPJSF_<SAPSID_Java_System>. Caution You must have changed the initial passwords [page 91] of these users before you start the installation of the Java system. This is your guest user in the J2EE Engine. Recommendation We recommend that you name the user J2EE_ADM_<SAPSID_Java_System>. 4. we recommend you to deactivate the password and. Log on to the SAP system once with this user to change its initial password. In addition. if required.6 6. If you intend to maintain user data (that is. .5 Additional Information Preparing User Management for an External ABAP System . Caution . SLD Data supplier user (optional): n You only have to create this user if you want to install System Landscape Directory (SLD). 2. You can use any password. create. This is your administrator user in the J2EE Engine. Recommendation We recommend that you name the user J2EE_GST_<SAPSID_Java_System>. 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. 104 PUBLIC 09/11/2006 . In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_ADMIN. As this user is only used for anonymous access to the system. You can use any password. the installation fails if this password is initial 3. lock it after installation to prevent anyone from using it for explicit named logons. You can use any password. l ADS_AGENT: In transaction PFCG. you need to assign the role SAP_BC_JSF_COMMUNICATION instead. to make sure that this user can only be used for communication connections between systems and not as a dialog user. n Users for Adobe Document Services (ADS) (optional): l ADSUSER: In transaction PFCG. The SLD data supplier user name that you enter later on during the Java system installation must be identical to this user. In transaction SU01 create the following dialog users : . Because the installer of the J2EE Engine verifies this password. assign the role SAP_BC_FP_ICF to this user. . assign it the type Communications under Logon data.

Note If there is more than one entry for the same port number. see: help.6 Configuring User Management to Use an LDAP Directory (Optional) If your user data source is an LDAP directory. 6.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.6 6. . Before the installation of the Java system. For more information. make sure that you have the correct user names and passwords of the users listed above for the separate ABAP system. 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). you need to configure the connection to the LDAP directory after installation. The SLD ABAP API user name that you enter later on during the Java system installation must be identical to this user. 2.6 Additional Information Configuring User Management to Use an LDAP Directory (Optional) Recommendation . During the installation of the Java system.sap. Recommendation We recommend that you name this user SLDAPIUSER Activities for the Java System Perform the following steps in the Java system: 1. make sure that you enter the correct users and passwords in the corresponding SAPinst dialogs. . 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.7 Entries in the Services File Created by SAPinst After the installation has finished successfully. 09/11/2006 PUBLIC 105 . this is not an error.

a standalone engine or a complete SAP system with SAPinst. You delete the database instance. You cannot delete an SAP system remotely. groups. you use the SAPinst service <SAP System> ® Additional Software Life-Cycle Tasks ® Uninstall ® Uninstall System / Standalone Engine / Optional Standalone Unit. where the SAP instances reside on different hosts. n If you want to delete a distributed system. which you can find on Windows under Add/Remove Programs. Process Flow n If you want to delete a central system. If you delete network-wide users. Note This description assumes that you have installed your SAP system with standard SAP tools according to the installation documentation. You delete the ABAP central services instance. Caution . which you find on Windows under Add/Remove Programs 6. where all SAP instances reside on the same host. you can do this in one SAPinst run [page 106]. . 3. n n n n Make sure that all remaining instances are stopped before you delete the database instance. Note SAPinst deletes the database instance but you have to delete the MS SQL Server database software with the SQL Server Uninstaller. Only valid for: HA (MSCS) 5. you have to run SAPinst [page 106] to delete the required instances locally on each host in the following sequence: 1. 2. You delete the central instance.8 Deleting an SAP System The following sections describe how to delete a single instance.6 6. End of: HA (MSCS) 6. 4. You delete the central services instance. . You delete the MS SQL Server database software with the SQL Server Uninstaller. and service entries to be deleted are no longer required. To delete your system. Make sure that the users. 106 PUBLIC 09/11/2006 . if there are any. SAPinst deletes the database instance but you have to delete the database software manually. other SAP installations might also be affected. groups or service entries in an environment with Network Information System (NIS).1 Running SAPinst to Delete an SAP System This procedure tells you how to run the Uninstall service of SAPinst.8 Additional Information Deleting an SAP System 6.8. You delete the dialog instance(s).

SAPinst does not delete \usr\sap\trans because it might be shared. as described in Deleting an SAP System [page 106].8 Additional Information Deleting an SAP System Prerequisites You are logged on as a user with the required rights and privileges to run the SAPinst tool and the SAP system. 3.6 6. c) Right-click the local group SAP_<SAPSID>_LocalAdmin and choose Delete. Procedure 1. . Start SAPinst and on the Welcome screen. . 5. SAPinst first asks you which SAP instances you want to delete. Note For more information about the input parameters. Make sure that you delete the SAP instances in the correct order. 4. place the cursor on the relevant field and press F1 in SAPinst. For more information. close SAPinst with Cancel and Exit. Before you delete the database instance of a distributed system make sure that you stop all remaining instances. 09/11/2006 PUBLIC 107 . choose: <SAP System> ® Additional Software Life-Cycle Tasks ® Uninstall ® Uninstall System / Standalone Engine / Optional Standalone Unit . If required. Note With this SAPinst service you do not delete the database software. To complete the uninstall process of the central instance. n If SAPinst stops responding while trying to delete the central instance. which you can find on Windows under Add/Remove Programs. you can delete the directory \usr\sap\trans and its contents manually. Follow the instructions in the SAPinst input dialogs. see Granting User Rights for the Installation [page 34]. Caution n SAPinst only stops local instances automatically. 2. restart SAPinst . You must stop the instance with the message server only after having entered all SAPinst parameters for the deletion of the database instance. Log off and log on again. When you have finished you can delete the MS SQL Server database software using the SQL Server Uninstaller. Delete the local user group SAP_<SAPSID>_LocalAdmin manually as follows: a) Choose Start ® Programs ® Administrative Tools ® Computer Management b) Choose Local Users and Groups ® Groups.

but is particularly important for the transport host. and the local group can contain users and global groups from this domain.9 SAP System Security on Windows In a standard SAP system installation. A local group can only be given permissions and rights to the system where it is located. SAPService<SID> This is the user account that is required to start the SAP system. SAP Directories SAPinst protects the SAP directories under \usr\sap\<SAPSID> by only granting the group SAP_<SAPSID>_LocalAdmin full control over these directories. The SAP_<SAPSID>_GlobalAdmin groups of all the SAP systems that are part of the transport infrastructure are added to the SAP_LocalAdmin group. The only function of a global group is to group users at the domain level so that they can be placed in the appropriate local groups. Members of the group have full control over the transport directory (\usr\sap\trans) that allows transports to take place between systems. n SAP_LocalAdmin This group is created on all hosts.6 6. The system is part of a particular domain. For central and straightforward administration of the SAP system. the users <sapsid>adm and SAPService<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. Therefore. 108 PUBLIC 09/11/2006 . 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. n SAP_<SAPSID>_LocalAdmin Only local groups are created and maintained on an application server. Although SAPinst makes sure that the system is protected against unauthorized access. you have to install distributed SAP systems with multiple application servers in a Windows domain.9 Additional Information SAP System Security on Windows 6. As a consequence. This section describes the user accounts and groups that SAPinst creates during a domain installation and shows how these are related to the SAP directories. It has the local user right to log on as a service. which prevents abuse of the account. you do not need to set an expiration date for the password and you do not have to set the option user must change password at next logon. you must still check that no security breaches can occur. The advantage of the additional SAPService<SAPSID> account is that it does not allow an interactive logon. SAPinst automatically performs all steps relevant for security. User Accounts SAPinst creates the following accounts for SAP system administration: n n <sapsid>adm This is the SAP system administrator account that enables interactive administration of the system.

Features The following graphics show the steps that SAPinst performs to create the users and groups and assign the required rights to SAP directories.10 Automatic Creation of Accounts and Groups SAPinst automatically creates the accounts and groups required for the secure operation of the SAP system with Windows [page 108] during the installation. Figure 10: User Groups and Accounts . only the following are members of all SAP system object ACLs: n Local group SAP_<SAPSID>_LocalAdmin n Group Administrators n Account SYSTEM 6.10 Additional Information Automatic Creation of Accounts and Groups The following graphic illustrates the user accounts and groups created by SAPinst in a system infrastructure consisting of two SAP systems. Note An access control list (ACL) controls access to SAP system objects.6 6. 09/11/2006 PUBLIC 109 . For maximum security in the SAP system.

10 Additional Information Automatic Creation of Accounts and Groups Figure 11: Creating Users and Groups 110 PUBLIC 09/11/2006 .6 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 SAPinst tool. For a domain installation.6 6. 09/11/2006 PUBLIC 111 . as described in this section. Prerequisites The Windows user that performs the SAP system installation must be authorized to perform the actions necessary for the installation. you might need to manually grant user rights for the installation to another user. this means that the user must belong to the Domain Administrator group and be authorized to: n Act as part of the operating system n Adjust memory quotas for a process n Replace a process-level token The procedure below assigns these rights to a user of your choice.11 Additional Information Manually Granting User Rights for the Installation Figure 12: Assigning Rights to SAP Directories 6.

More Information Granting User Rights for the Installation [page 34] 6. In the Local Security Settings window.sdtgui\ for errors.12. SAPinst: n Stops the installation n Displays a dialog informing you about the error Procedure 1.12 Additional Information Troubleshooting . Caution Be aware that domain policies override locally defined policies. choose the required user and choose Add.err in the current %userprofile% directory. 2.12 Troubleshooting The following section(s) describe the steps that you need to perform manually if SAPinst fails: n Troubleshooting with SAPinst [page 112] 6. If an error occurs.1 Troubleshooting with SAPinst This section tells you how to proceed when errors occur during the installation with SAPinst. 3. choose Local Policies ® User Rights Assignment. To view the log file. Log off and log on again to apply the changes. 4. In the Select Users and Groups window. This means that if you want to grant domain administrator rights for a local user.6 6. If SAPinst GUI does not start. choose View Logs. 3. make sure that you have also defined domain administrator rights for this user on domain level. Confirm your entry and then repeat the steps for each remaining policy that the user requires for the installation. Check the log and trace files of the GUI server and SAPinst GUI in the directory %userprofile%\. Double-click the respective right under Policy and choose Add User or Group. see Interrupted Installation with SAPinst [page 65]. Choose Start ® Settings ® Control Panel ® Administrative Tools ® Local Security Policy. check the file sdtstart. 6. 112 PUBLIC 09/11/2006 . n Continue the installation by choosing Retry. 5. Procedure 1. 2. If an error occurs during the dialog or processing phase. do either of the following: n Try to solve the problem n Abort the installation with Exit For more information. 4. The selected user appears in the box below.

Ignore error messages in the SDM logs that state that software components are not available. restart SAPinst GUI as described in Starting SAPinst GUI Separately.6 6.12 Additional Information Troubleshooting 5. see SAP Note 828978. If SAPinst GUI aborts during the installation without an error message. 6. 09/11/2006 PUBLIC 113 . For more information.

.This page is intentionally left blank.

When maintenance work is finished you can easily move the resources back to their original node and continue operating them there. with cluster-specific steps. you can also use MSCS to avoid downtime when you perform essential system maintenance. n Since the correct configuration of network addresses is absolutely essential to enable the cluster to function properly. Note n Make sure that you read SAP Note 936703. you have to install some components on all nodes and observe special rules for distributing components to local or shared disks. With high availability you enable critical system components. you can deliberately switch the cluster resources to another node and temporarily operate it there while maintenance is in progress. you combine standard installation steps.7 High Availability with Microsoft Cluster Service 7 High Availability with Microsoft Cluster Service You can install a high-availability SAP system with Microsoft Cluster Service (MSCS). For more information. which contains the most recent information as well as corrections for MSCS for SAP NetWeaver 2004s SR1. described earlier in this documentation. so-called Single Points of Failure (SPOFs) to be automatically switched from one machine to the other. described here. With the help of this switchover ‒ or failover ‒ the system can continue functioning normally so that unplanned system downtime is avoided. you have to perform a number of additional steps that are necessary to set up and check addressing. enabling 24-hour operation. n When you are setting up the SAP system with MSCS. For this type of installation. 365 days a year. you have to set up the system on at least two clustered hosts (called “MSCS nodes”) and configure it so that it can take advantage of the MSCS software. see the SAP installation notes [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 additional MSCS node(s). you have to perform a number of extra steps specially required for the cluster 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. if hardware or software problems arise on one machine. . Apart from enabling failover when hardware problems occur. If you need to maintain one node. n Since the cluster hardware has at least two nodes that have access to all local and shared storage devices. The MSCS software improves the availability of the system and safeguards it against failure and unplanned downtime. To install a new SAP system with MSCS. 09/11/2006 PUBLIC 115 .

instead of loading the database from the Export DVDs in the installation package.com/osdbmigration. see service. dialog instance) 1 1 1 1-n yes yes yes no 116 PUBLIC 09/11/2006 .com/instguidesNW04Installation. After you have created a copy of the database.1. In addition. 2. The documentation for a homogeneous or heterogeneous system copy does not include the cluster-specific information.sap.1 Planning You have to complete the following planning activities for you SAP system using Microsoft Cluster Service (MSCS): 1. Therefore.1 High Availability with Microsoft Cluster Service Planning . you install the SAP system using a system copy. You install an enqueue replication server [page 119]. which is described here. 3. Note If you have an existing SAP system and plan to migrate to a cluster with new hardware. 7. 5. you can install your system with MSCS. see the documentation Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP NetWeaver on SAP Service Marketplace at service. 7. You read Directories in an MSCS Configuration [page 122] You read IP Addresses in an MSCS Configuration [page 122] You obtain IP addresses for MSCS [page 126]. You decide how to set up your SAP system components in an MSCS configuration [page 116].sap.7 7. 4. For more information about a homogeneous or heterogeneous system copy. You check the hardware and software requirements for MSCS [page 128]. you load it using your exported database. for more information about a heterogeneous system copy. However.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 Component Number of Components per SAP System Single Point of Failure SCS instance (message services and enqueue services) ASCS instance (message services and enqueue services) Database instance Application server (central instance. You distribute components to disks for MSCS [page 120]. you have to prepare for the installation by creating a homogeneous or a heterogeneous copy of the database. 6. 7.

7 7. When maintenance work is finished you move the (A)SCS and database instance back to the original node. If you need to maintain the MSCS node where the (A)SCS instance and database are running you can switch these instances to another node. you restart the instance(s).1 High Availability with Microsoft Cluster Service Planning n To protect the SPOFs ((A)SCS instance and database instance) you have to use MSCS. the clustered (A)SCS instance and the clustered database automatically fail over to another node. If a hardware or software problem occurs on the first MSCS node. you have to stop the central or dialog instance on that node. You install them on a local disk. The following graphic shows an example where the SPOFs are installed on two MSCS cluster. for example application servers. When you have finished maintenance. Figure 13: ABAP+Java System n To protect system components that are non-SPOFs. 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 two MSCS nodes 09/11/2006 PUBLIC 117 . If you have to maintain an MSCS node. In this case you must install at least two application servers (one central and at least one dialog instance) on two different hosts. you have to install them as multiple components. You have the following options: l You install the central instance and the dialog instance on the MSCS nodes of an MSCS cluster.

In this example. 118 PUBLIC 09/11/2006 .7 7. the (A)SCS instance and the database instance are installed in one MSCS cluster. as show in the following graphic.1 High Availability with Microsoft Cluster Service Planning Figure 14: ABAP+Java System l You install the central instance and all dialog instances outside of an MSCS cluster on different hosts.

The enqueue replication server on the second MSCS node then becomes inactive. If an enqueue server in an MSCS 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 it in its lock table. The enqueue replication server contains a replica of the lock table (replication table). If the first MSCS node is available again. the enqueue replication server on the second MSCS node becomes active again. In normal operation the replication enqueue server is always active on the host where the SCS and ASCS instance are not running.1.2 Enqueue Replication Server in an MSCS Configuration For this type of installation. The following graphic shows the enqueue replication server mechanism in an MSCS configuration with two nodes: 09/11/2006 PUBLIC 119 . you install an enqueue replication server on all MSCS nodes where the Java central services (SCS) instance and the ABAP central services (ASCS) instance are installed.7 7.1 High Availability with Microsoft Cluster Service Planning Figure 15: ABAP+Java System 7.

you can now choose between the following cluster models: 120 PUBLIC 09/11/2006 . n On the shared storage that is used in common by all MSCS nodes. if used With Windows Server 2003.1 High Availability with Microsoft Cluster Service Planning Figure 16: Enqueue Replication Server Mechanism on One MSCS Cluster with Two Nodes 7. 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. You install the following on different shared disks: l Database data files l SAP system executables l Single quorum device.7 7. Note Shared disk is a synonym for the MSCS resource of Resource type Physical disk.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 hardware has 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 .

the SAP system executables. or Independent Hardware Vendor (IHV). Majority Node Set Cluster n In this new cluster model.1 High Availability with Microsoft Cluster Service Planning n Single Quorum Device Cluster In this cluster model the quorum resource maintains the cluster configuration data on a single cluster storage device. Figure 17: 09/11/2006 PUBLIC 121 . l It arbitrates between competing nodes when the communication between nodes breaks down. and the quorum resource (if used) to different disks. It illustrates how to distribute the database data files. The Majority Node Set resource. It has the following main functions in the cluster: l It logs changes to the cluster configuration that are entered in the Registry. each node maintains its own copy of the cluster configuration data. The quorum resource is unique to a cluster installation and is always owned by one of the nodes. Only with this distribution of files to distinct disks is it possible to move the SAP system and database as separate entities in a failover situation. You can use majority node set for geographically dispersed cluster configuration. acting as the Quorum Resource. ensures that the cluster configuration data is kept consistent across the different nodes. SAP supports Majority Node Set Cluster if it is part of a cluster solution offered by your Original Equipment Manufacturer (OEM). The following graphic shows a cluster configuration where the (A)SCS and DB instance are installed in the same cluster. This means that cluster resources are forced to fail over to the node that owns the quorum resource.7 7.

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 in the network. 122 PUBLIC 09/11/2006 . <drive>:\TEMPDB <drive>:\mssql <drive>:\<SAPSID>DATA1 <drive>:\<SAPSID>DATA2 <drive>:\<SAPSID>DATA3 Cluster quorum resource SAP global and instance directories tempdb databases msdb. independently of the MSCS node the SAP instance is running on. The directory is added to the path variable of the user <sapsid>adm. The files are database tools and program files (executables) used by the operating system monitor (SAPOsCol).4 Directories in an MSCS Configuration The following tables show the directories where the main software components for the SAP cluster installation are stored: Directories on Local Disks on MSCS Nodes Component Default Directory %windir% %windir%\Cluster %windir%\SAPCluster A supported operating system [page 128] MSCS software SAP cluster files Directories on Shared Disks Component Default Directory <drive>:\MSCS <drive>:\usr\sap .1. This contains all the SAP files required by all MSCS cluster nodes..1 High Availability with Microsoft Cluster Service Planning More Information Directories in an MSCS Configuration [page 122] 7. model. Addressing must be set up correctly so that the system can take advantage of the cluster functionality and switch between nodes when hardware problems arise. This is a particularly important task because the addressing plays a key role in the switchover procedure.. an additional directory ‒ %WINDIR%\SapCluster ‒ is created under the system directory.7 7.1. master SAP data files SapCluster Directory In an SAP cluster installation. 7.

there are at least seven IP addresses and corresponding host names.7 7. Note For more information on network configuration. n A private network that is used internally for communication between the nodes of the cluster.1 High Availability with Microsoft Cluster Service Planning This section explains the different types of IP addresses and their function in the switchover mechanism of an MSCS cluster with two nodes. To set up these two networks. application servers and the LAN. A physical IP address. 09/11/2006 PUBLIC 123 . Some of the addresses are physical IP addresses that are assigned to the network adapters (cards). . 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. is stationary and permanently mapped to the same adapter. see also the Microsoft Knowledge Base Article 259267. and two addresses for the cluster group. You have two IP addresses for each MSCS node. one IP addresses for the network adapter. The following graphic shows an MSCS cluster with two nodes and illustrates the adapters required for the public and private networks. others are virtual IP addresses that are assigned to the cluster groups. Types of IP Addresses In a correctly configured cluster with at least two nodes. each node needs an adapter for both the private and public network. as opposed to a virtual one. This means that each node must have an adapter for the private network and an adapter for the public network and each of these adapters has its own physical IP address and corresponding host name. and their corresponding physical IP addresses.

5.1 124 PUBLIC 09/11/2006 . you might assign the IP addresses of the public and private network adapters as follows: IP Addresses and Host Names Network Adapter IP Address Host Name clusA_priv clusA Adapter 1 (private network) Adapter 3 ( public network) 10. For example.1.20.1 High Availability with Microsoft Cluster Service Planning Figure 18: Adapters and IP Addresses Required for Public and Private Networks in an MSCS Cluster with Two Nodes Host Names Assigned to Network Adapters Each of the physical IP addresses of the network adapters must have a corresponding host name.7 7.1 129. on the left-hand node in the graphic above.1.

This has the advantage that. Each of these groups requires a virtual IP address and host name that is permanently mapped to the group and not to a particular node. its IP address and host name move together with it. When the group is moved from one node to the other. but is written in uppercase. all clients can still reach the database server with the same IP address as before. Virtual IP Addresses Assigned to Cluster Groups When you have installed the SAP system and fully configured the cluster. which is often the same as the host name. due to node failure. The following graphic illustrates how the virtual IP addresses of the database group and SAP group can move from one node to the other when failover occurs. When you configure IP addresses and corresponding names. Therefore. In our example. the critical system resources are bound together in three different groups. not the computer names.7 7. 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 the machine. it is not required for the TCP/IP communication in the cluster. but also of the virtual IP address and host name. For example. 09/11/2006 PUBLIC 125 . the virtual IP address and host name move with it. n Do not confuse the host name with the computer name. The computer name is displayed in the node column of the Cluster Administrator. this means that the machine that is the MSCS node on the left in the graphic has the name clus1. the database cluster group comprises all the resources that enable the database server to fulfill the requests of a client.1 High Availability with Microsoft Cluster Service Planning . there is a failover not only of resources. keep in mind that it is the host names that are important for the cluster. A cluster configuration has the following groups: n SAP cluster group n Database cluster group n Cluster group Each group consists of a set of related resources that work together to offer a service to the system. whenever a group is moved between nodes. Each node also has a computer name. However. As a result.

Obtaining IP Addresses Ask the system administrator to give you the addresses and host names listed in the tables below. the host names and IP addresses of the network adapters (cards) have already been defined and exist in your system. 126 PUBLIC 09/11/2006 .6 Obtaining IP Addresses for MSCS You need to correctly configure IP addresses for a cluster system. You normally obtain these names and addresses from the system administrator. Prerequisites n If you are installing Windows for the first time on your system. You will need to enter the addresses and host names later during the installation process. However. n If Windows has already been installed on your system. you still need to use the table Virtual IP Addresses in the procedure Obtaining IP Addresses.1 High Availability with Microsoft Cluster Service Planning Figure 19: Failover of Virtual IP Addresses 7. which shows an example for a configuration with one MSCS cluster with two nodes.7 7.1. The column Defined During indicates at which stage of the installation the addresses are defined in the system. During the installation procedure you have to assign at least seven IP addresses and host names. follow the procedure Obtaining IP Addresses below. This means that you can find out the IP addresses for the network adapters using the procedure Determining Existing IP Addresses below.

1 clusA_priv Address for interWindows installation node communication on the private network Address of the first Windows installation MSCS node for communication with application servers and LAN (this is the same as the address of the first MSCS node) Address for interWindows installation node communication on the private network Address of the Windows installation additional MSCS node for communication with application servers and LAN (this is the same as the address of the additional MSCS node) 129.20.1. 09/11/2006 PUBLIC 127 .2 clusB_priv 129.1 High Availability with Microsoft Cluster Service Planning .1.20.5. It identifies the cluster and is used for administration purposes.2 clusB Virtual IP Addresses Component Example for Virtual IP Address 129.1.5.20.1.7 7.5.3 Example for Host Name clusgrp Purpose Defined During Cluster group MSCS software Virtual address and installation name of the cluster group. Caution Use the names exactly as specified by the system administrator. Physical IP Addresses Component Example for Physical Example for Physical IP Address Host Name Purpose Defined During First MSCS Node: adapter for private network First MSCS Node: adapter for public network 10.1 clusA Additional MSCS Node: adapter for private network Additional MSCS Node: adapter for public network 10. carefully observing uppercase and lowercase letters.

1.20. Procedure 1. To find out the host name that is mapped to the IP address. AddOn Technology Center for SAP (Add On TCS) certifies hardware platforms for SAP on Microsoft Windows. Choose TCP/IP Protocol ® Properties. see IP Addresses in an MSCS Configuration [page 122]. Check that your cluster hardware is certified. The Network and dial-up Connections window appears 2. proceed as follows: 1. 5. 7.5. 4.4 Example for Host Name sapgrp Purpose Defined During SAP cluster group Virtual address and name for accessing the group of SAP resources.20. Do not forget to ping your local machine as well.7 7.5 dbgrp Execution of MSCS wizard or database-specific cluster scripts Determining Existing IP Addresses To find out the existing IP addresses and corresponding host names and addresses.microsoft. The TCP/IP Properties dialog box appears and shows the IP address of the initially selected network card. This makes sure that the system can take advantage of the MSCS functionality and achieves an acceptable performance level.7 Checking Hardware and Software Requirements for MSCS When you install the SAP system on cluster hardware. A dialog box opens. regardless of the node it is running on Virtual address and name for accessing the group of database resources. 3. The cluster must be included in the Microsoft list of certified clusters and its components. Repeat these steps for the other network cards. you have to meet the hardware requirements shown below. Choose Start ® Settings ® Network and dial-up Connections.1 High Availability with Microsoft Cluster Service Planning Component Example for Virtual IP Address 129. You can access the lists at the following Internet addresses: www. regardless of the node it is running on Configuration of SAP system for MSCS with SAPinst on the first node Database cluster group 129.5. Select one of the network cards that are displayed and choose File ® Properties.com/hcl 128 PUBLIC 09/11/2006 . For more information about IP addresses in the cluster environment. use the ping command: ping -a <IP_Address> The system returns the host name assigned to the IP address.

If you install SQL Server 2005. Disks Required Space How to Check 1 local disk on each MSCS 3 GB node n Non-Unicode (not including paging file): n Unicode (not including paging file): a) Choose Start ® Programs ® Administrative Tools ® Computer Management ® Disk Management. it enables the Cluster Service running on all MSCS nodes to regularly exchange messages on the state of the MSCS nodes so that the failure of resources is quickly detected. At least 4 shared disks . Check that sufficient storage space is available. b) Right-click the disk and choose Properties. In particular. All software ‒ except the Windows operating system. 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. 4. 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). 5. 09/11/2006 PUBLIC 129 . Check the RAM and paging file size on each MSCS node. and the MSCS software ‒ is stored on the shared disks. you must install at least SP1 for Windows Server 2003. see the Hardware and Software Requirements Checklists [page 26]. Note All disk controllers must be able to support hardware-based RAID. Note . 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 Edition n Windows Server 2003 Datacenter Edition . For more information.7 7.com 2. Each of the MSCS nodes in the cluster must have its own local disks and have access to shared disks that can be reached by the MSCS nodes via a shared bus. Note To check the Windows version a) Choose Start ® Programs ® Accessories ® Command Prompt b) Enter the command winver We strongly recommend you to use the 64-bit version of the Windows Server 2003 editions. 3.saponwin. the MS SQL server system database.1 High Availability with Microsoft Cluster Service Planning www. n The private network enables internal communication between the MSCS nodes. a) Choose Start ® Programs ® Administrative Tools ® Computer Management ® Disk Management. b) Right-click the disk and choose Properties.

see SAP Notes 62988 and 608651. you manually assign drive letters to the shared disks [page 130] using the Windows Disk Administrator. l MS SQL Server 2005 Enterprise Edition: Server Software u Latest service pack and hotfix. On all MSCS nodes. You map the IP addresses to host names [page 131] on the Domain Name System (DNS) Server or in the hosts file. u Unicode collation SQL_Latin1_General_CP850_BIN2 For more information on the collation for MS SQL Server 2000. that you have installed the operating system [page 128] with the option Cluster Service on all MSCS nodes. see SAP Notes 62988 and 608651. if available.7 7. u Unicode collation SQL_Latin1_General_CP850_BIN2 A suitable Windows Resource Kit is strongly recommended n For more information on the current Service Pack for MS SQL Server 2000. For more information. For more information. 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 disk resources from one node to another so that they are only accessible from a single node at any time. see the Windows documentation.1 Assigning Drive Letters for MSCS We recommend that you assign drive letters for MSCS.2 High Availability with Microsoft Cluster Service Preparation Software Requirement How to Check n One of the following SQL Server Enterprise Edition server software: l MS SQL Server 2000 Enterprise Edition: Server Software u Latest service pack and hotfix. On all MSCS nodes. For more information. For more information. Make sure. . see SAP Note 62988.2. 3. 4. 5. n For more information on the new collation. see Installing the Corrected MS SQL Server Collation for MS SQL Server 2000 [page 51] - 7. 7. see Hardware and Software Requirements [page 128] and Reducing the Size of File Cache [page 34]. 130 PUBLIC 09/11/2006 . You cannot use a host with a domain controller as an MSCS cluster node. see SAP Note 608651. if available. n For more information on the current hotfix for MS SQL Server 2000. Caution . All MSCS nodes must access the shared disks with the same drive letters.2 Preparation You have to complete the following preparations for the MSCS cluster installation: 1. you adjust the size of paging file and the file cache. see SAP Note 600027. 2. for SQL Server 2000.

Enter a new drive letter. the shared disks that can be accessed by all nodes via a common bus must be addressed by all nodes with the same drive letters. However. We recommend that you perform the mapping on the DNS server because this only requires a single entry.2. The file is located in the default Windows directory: %SystemRoot%Drive\system32\drivers\etc Recommendation . . n You have the list of IP addresses [page 126]. you have to map all IP addresses in the MSCS cluster to host names. 7. n You have correctly entered all seven IP addresses required for the MSCS configuration. Procedure 1. Procedure To map the host names to the IP addresses. Caution Missing or incorrect entries for the IP addresses can cause problems later during the installation. do one of the following: n Map the host names to IP addresses on a Domain Name System (DNS) server.7 7. 2. the system can only respond to host names if they are translated into IP addresses. Select a disk and choose Action ® All tasks ® Change drive. If you perform the mapping in the hosts file. The mapping enables the system to translate host names into IP addresses. 7.2 Mapping Host Names to IP Addresses for MSCS To enable correct operation of the failover mechanism. 3. 09/11/2006 PUBLIC 131 . and on all application servers and front ends. Prerequisites n You have installed the Windows operating system. as each host in the system has its own hosts file. you have to maintain the hosts file on all MSCS nodes of the cluster. numeric IP addresses. Choose Start ® Programs ® Administrative Tools ® Computer Management ® Storage ® Disk Management. Host names are normally used for administrative tasks because they are easier to use than the long.2. n Map the IP addresses in the Windows hosts file.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 problems later.2 High Availability with Microsoft Cluster Service Preparation In an MSCS cluster.

b) ping hostname The system returns the IP address that is assigned to the host name. n If the address you are checking already exists in the system. 132 PUBLIC 09/11/2006 . do the following on all MSCS nodes: a) Choose Start ® Settings ® Network and Dial-up Connections The Network and Dial-up Connections window appears. 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.7 7. you do not get a reply if the host does not yet exist. 2. change the order in which the cards are listed by using the Move Up and Move Down arrows 7. you also receive a reply from the host. Note n When you enter the ping command. Procedure 1. For example. . To correct the network bindings. Compare the output with your own record of addresses and host names. which is usually also the name of the local host. . after the installation of Windows and the configuration of the network. If necessary. and check for the following possible errors: n Incorrect output of uppercase and lowercase Make sure that you correct the error before you proceed with the installation. and the system returns the IP address of the private network.3 High Availability with Microsoft Cluster Service Installation Prerequisites You have mapped the host names to the IP addresses [page 131] on the DNS Server or in the hosts file. you get a reply when entering the IP addresses of the network adapters. Note The card of the public network must be displayed before that of the private network. b) Choose Advanced ® Advanced Settings ® Adapters and Bindings The network cards of the private and public networks are displayed for the current MSCS node. n Error in the network bindings If you enter the name of the public network adapter. there is an error in the network bindings.3 Installation The following sections provide information about how to install the SAP system for MSCS.

Procedure 1. the installation procedure differs for 32-bit [page 133] or 64-bit [page 135]systems. 7. Caution . you must install MS SQL Server as a default instance. 09/11/2006 PUBLIC 133 . n If you are prompted during the installation process.3. you are not granted domain administrators rights. For MSCS. You install the central services instance (SCS) on the first MSCS node [page 142]. If for any reason. Log on to the host as a local administrator. Note If you cluster SQL Server 2000. You install the database instance on the first MSCS node [page 144]. you can perform the installation as a domain user who is a member of the local administrators group. you install an enqueue replication server [page 146]. You cluster the additional MSCS node [page 144]. Note n Make sure that you are logged on as domain administrator. unless otherwise specified. You install the central instance [page 147]. 5.7 7. You install at least one dialog instance [page 147]. If required. make sure that all existing cluster groups are online. You cluster the first MSCS node [page 143]. after each reboot. . Therefore. In the Cluster Administrator.3 High Availability with Microsoft Cluster Service Installation . You have to perform the following steps: 1.3. Do not use the user <sapsid>adm unless specified. you have to return the system to the state it had before the reboot. log off and log on again. 10.1 Clustering the SQL Server Database Software The following sections describe how to install the SQL Server 2000 or SQL Server 2005 database software for an MSCS configuration. the domain administrator has to prepare the system appropriately for you. 9. 7. You install the central services instance for ABAP (ASCS) on the first MSCS node [page 142]. n When you reboot during the installation process [page 142]. 4. resources fail over to another node. in the Cluster Administrator. 7. 2. n On the first MSCS node. 3.1. On the first MSCS node.1 Clustering the SQL Server 2000 Database Software in a 32-Bit System You perform the following steps on the first MSCS node. 6. you install MS SQL Server [page 133]. However. you move all disk groups and the cluster group to the first MSCS node [page 141]. 8.

where you want to put the data files and choose Next. To start the installation.exe located in the x86\SQL2000 directory of the RDBMS 4. Welcome Computer Name: User Information Software License Agreement CD-Key Failover Clustering Click Next. pubs and msdb databases on one of the shared drive of the MSSQL group (the default value for these files is the local disk). Insert the MS SQL Server 2000 RDBMS DVD into your DVD drive. Note Cluster Disk Selection When you select a shared disk you can ignore the warning that the selected disk is a shared disk in a cluster. . . Note Use the option to create a new virtual server. n Enter the IP address and subnet mask of the virtual database server and click Add. Enter your personal information. For more information. When you are asked in the Setup Type dialog for the destination folder for the program and data files. Select Components Service Accounts 134 PUBLIC 09/11/2006 . Select Custom. Select the shared disk.7 7. Make sure that Default is selected and choose Next. n Select the public net for the network to use. Enter the name of the virtual server and click Next. Enter a domain administrator user account for all MSCS nodes and choose Next. Select Use the same account for each service and enter the password for the displayed domain administrator account. MS SQL Server 2000 Enterprise Edition MS SQL Server 2000 Enterprise Edition Select SQL Server 2000 Components. n data files for the master. Select all components and choose Next. confirm the warning.txt in the root directory of the RDBMS DVD and choose Next. 3.3 High Availability with Microsoft Cluster Service Installation 2. Enter the required information as specified in the table: Window Input DVD. see Directories in an MSCS configuration [page 122]. run autorun. Enter the key specified in the file SAPCDKEY. Cluster Management Remote Information Instance Name Setup Type Select all MSCS nodes. make sure that you install the n program files on a local drive. Choose Yes. To proceed. Select Install Database Server.

Select your licensing mode. SAPinst automatically changes the authentication mode into Mixed mode when installing a Java system.7 7. c) Under Dependencies. Leave selection unchanged and choose Next. For more information. select Modify. 7. . for use with the 850 (Multilingual) Character Set. Install the latest Service Pack and hot fix. under the database group. To check. and bring all resources of the SQL cluster group online. . The Service Pack and the hot fix will also be automatically installed on the additional MSCS node(s). see SAP Note 600027. Network Libraries Start Copying Files Choose Licensing Mode Setup Complete 5. For the current version of the Service Pack and hot fix for MS SQL Server that is supported by SAP. Collation settings Select SQL Collations. Click Finish. if available. select Binary order. Note For a Java system. e) Confirm your entries with OK.3 High Availability with Microsoft Cluster Service Installation Window Input Authentication mode Select Windows Authentication Mode and choose Next. move the MSSQL database group back to the first MSCS node. see SAP Notes 62988 and 608651. 6. d) Move all available disks shown under Available resources to Dependencies. 7. b) Double-click the SQL Server cluster resource.3.2 Clustering the SQL Server 2000 Database Software in a 64-Bit System You perform the following steps on the first MSCS node. 09/11/2006 PUBLIC 135 . Install the corrected MS SQL Server collation [page 51] on the first MSCS node. If you have more than one disk in your SQL Server database cluster group.1. right-click SQL Server. f) In the Cluster Administrator. right-click on SQL Server. and take it offline. Choose Next. make sure that the SQL Server cluster resource is dependent on all physical disks. perform the following steps: a) In the Cluster Administrator. under the database group. From the dropdown list. Mixed mode is required. Note If you have to reboot. on the first MSCS node.

pubs and msdb databases on one of the shared drive of the MSSQL group (the default value for these files is the local disk). To start the installation. For more information. Enter a domain administrator user account for your MSCS nodes and choose Next. Make sure that you install the n program files on a local drive.exe located in the directory IA64\SQL2000.7 7. Select the cluster group for the virtual server resources. the sa login is created. n Select Virtual Server. SAPinst automatically changes the authentication mode into Mixed mode when installing a Java system. run setup. see Directories in an MSCS configuration [page 122]. Note Instance Name Configure Nodes Remote Account Information Installation Folders Service Account Authentication Mode For a Java system. Note If you have chosen Windows authentication mode. .txt in the root directory of the RDBMS DVD. Enter the virtual server name.3 High Availability with Microsoft Cluster Service Installation Procedure 1. Enter the required information as specified in the table: Window Input Setup Mode Registration Information Software License Agreement Virtual Server Name Cluster Group Selection Failover Clustering n Select Start a new installation. Select the MSCS nodes to configure. 136 PUBLIC 09/11/2006 . Mixed mode is required. n Enter the IP address for the virtual server. n Select the authentication mode. Make sure that Default is selected and choose Next. 2. n Select the public network to use. n data files for the master. Select the destination folder for the program and data files. 4. . and choose Add. 3. but cannot be used. Enter your name and the product key specified in the file SAPCDKEY. Log on to the host as a local administrator. n Enter and confirm the password for the sa login. Choose Yes. Select Use a Domain User account and enter the password for the displayed domain administrator account. Insert the MS SQL Server 2000 RDBMS DVD in your DVD drive. We recommend to use Windows authentication mode.

Licensing Mode Ready to Install 5. Note For more information and a complete list of the restrictions. d) Move all available disks shown under Available resources to Dependencies. Select SQL Collations. perform the following steps: a) In the Cluster Administrator. select Binary order. c) Under Dependencies. see SAP Note 62988 and 608651.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 or 64-bit systems. see Installing the SQL Server 2005 Native Client Software Manually [page 55]. For the current version of the Service Pack and hotfix for MS SQL Server that is supported by SAP. and take it offline. if available for MS SQL Server on the first MSCS node. under the database group.com/en-us/library/ms130214. b) Double-click the SQL Server cluster resource. . Select the licensing mode and choose Next. 7. To check. Note To install the client software. e) Confirm your entries with OK.3. f) In the Cluster Administrator. under the database group. for use with the 850 (Multilingual) Character Set. Select Install. The service pack and hotfix will be automatically installed on the additional MSCS node(s). make sure that the SQL Server cluster resource is dependent on all physical disks. right-click SQL Server. Install the corrected MS SQL Server collation [page 51] on the first MSCS node. . From the dropdown list. 7. and bring all resources of the SQL cluster group online. Install the latest service pack and hotfix. Prerequisites The following prerequisites apply if you install SQL Server 2005 for MSCS. right-click on SQL Server. The SQL Server 2005 database server software must be installed on the database host. For more information. 6. see the Books Online for SQL Server 2005 at: http://msdn. see SAP Note 600027.1.7 7. select Modify.microsoft. 09/11/2006 PUBLIC 137 . If you have more than one disk in your SQL Server database cluster group.3 High Availability with Microsoft Cluster Service Installation Window Input Security Enhancement: Cross Database Ownership Chaining Collation Settings Leave selection unchanged and choose Next.

txt in the same directory. Insert the SQL Server 2005 RDBMS DVD in your DVD drive or mount it locally. if required. Note You perform the following steps on all MSCS nodes.exe. Server Input Window End User License Agreement Installing Prerequisites Welcome to the Microsoft SQL Server Installation Wizard. 138 PUBLIC 09/11/2006 .com/KB/301600. Choose Next.7 7. Change to the platform-specific folder and choose Enterprise Edition ® Servers. Note The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL server\90\Setup Bootstrap\LOG. l Ask your domain administrator to add the startup account for each service to the respective domain groups. 2. l Microsoft recommends that you do not share the SQL server domain groups with other applications. Next. Enter the required information as specified in the table below: . For more information on how to install MSDTC.3 High Availability with Microsoft Cluster Service Installation n Make sure that you have not applied NTFS compression to the disk where you install the SQL Server software. Log on as a domain user who is a member of the local Administrators group on all MSCS nodes. You find the summary of the setup log in summary. Start the installation program with setup. 3. SQL Agent. 5. l Ask the domain administrator to create the domain groups with the Group Type Security and Group Scope Domain Local. Choose Install and. n You have created domain user groups for each clustered service like SQL Server. 1.microsoft. 4. Accept the licensing terms and conditions and choose Next. l Microsoft recommends that you use for each service a different domain group. see KB 301600 at support. Full Text. n You have installed Microsoft Distributed Transaction Coordinator (MSDTC). n You have created the SQL Server database cluster group and added the shared disks for the SQL Sever databases to the group. l The group names must already exist in the domain before you start the SQL Server 2005 installation. Procedure .

after you have finished the installation on the first MSCS node. n The system configuration is checked on all MSCS nodes. a) Select the following options: n SQL Server Database Services n Create a SQL Server failover cluster n Workstation components. Note n For more information about the required system configuration for a software component. b) Choose Advanced. start the installation program with setup. . Registration Information a) Enter your personal information. Make sure that the Microsoft Distributed Transaction Coordinator (MSDTC) service is running.exe on the additional MSCS node(s). and choose Workstation components. correct the configuration before you proceed with the installation. c) Choose Next. 09/11/2006 PUBLIC 139 . To install them. Note We recommend that you deselect these features as they are not required for an SAP system.7 7. choose Message. b) Choose Next. you can ignore the warning about the IIS Feature Requirement.3 High Availability with Microsoft Cluster Service Installation Window Server Input System Configuration Check a) Check your system configuration and. Feature Selection a) Expand Database Services and deselect Replication b) Expand Client Components and if available. or Books Online are not installed on the additional MSCS node(s). set up the required configuration. deselectBusiness Intelligence Development Studio. Therefore. b) Choose Next. n IIS is not required for an SAP system. Note Components to Install The workstation components like SQL Management Studio. Books Online and development tools. n If there is a warning in COM Plus Catalog Requirement. and the product key. . if required. .

. and choose Next. . Note Remote Account Information Service Account Domain Groups for Clustered Services The startup account for each clustered service is added to the DomainName\GroupName to set its access control. you set the password for the sa login. Select the cluster group where the virtual server resources are to be installed. If you do not have domain Administrator’s rights. b) Choose Next. ask your domain administrator to add these user accounts to the appropriate domain groups. If you choose this mode. b) Choose Add and then Next. Authentication Mode a) Select Mixed Mode (Windows Authentication and SQL Server Authentication). a) Select and add all MSCS nodes to be included in the virtual server. .3 High Availability with Microsoft Cluster Service Installation Window Server Input Instance Name Virtual Server Name Select Default Instance and choose Next. 140 PUBLIC 09/11/2006 . b) Choose Next. This mode is required for a Java or ABAP+Java system. Enter the domain and group names of the clustered services. Note The virtual server name must be unique in the network. and choose Next.7 7. Enter the virtual server name and choose Next. b) Choose Next. and choose Next. The password for the sa login must comply with the Windows password policy. a) Select Use a domain user account and enter the user name and password. Enter a domain administrator who is a member of the local Administrators group on all MSCS nodes. Virtual Server Configuration Cluster Group Selection Cluster Node Configuration a) Select the public network and enter the IP address. Note SAPinst automatically changes the authentication mode into Mixed Mode when installing a Java system.

7. select the group you want to move and drag it to the required MSCS node on the left-hand pane. 2. Restart SQL Server. Repeat the previous step for each group that you want to move.3.7 7. 3. Completing Microsoft SQL Server 2005 Setup Choose Finish. right-click Named Pipes and TCP/IP. c) Choose Next. select Protocols for <SAPSID> n In the right-hand pane. Start the Cluster Administrator with Start ® Programs ® Administrative Tools ® Cluster Administrator. 6. SAP.2 Moving MSCS Groups During the cluster installation you have to move the database. When you have finished the installation. select Protocols for MSSQLServer n For a named instance. In the Cluster Administrator. or disk cluster groups from one MSCS node to the other before you can continue.3 High Availability with Microsoft Cluster Service Installation Window Server Input Collation Settings a) Select SQL collations (used for compatibility with previous versions of SQL Server). . 09/11/2006 PUBLIC 141 . Prerequisites n The groups you want to move are configured and are visible in the Cluster Administrator. and select Enable. and choose Next. see Rebooting During the Installation or Conversion for MSCS [page 142]. for use with the 850 (Multilingual) Character Set. b) From the drop-down list select Binary order. n For more information if you need to reboot during the installation. Procedure Moving Groups with the Cluster Administrator 1. under Protocol Name. Choose Install. 7. choose Setup finished. choose Next. Note Error and Usage Report Settings Ready to Install Setup Progress To see the log files for the SQL Server components. enable the Named Pipes and TCP/IP protocol in the SQL Server Configuration Manager as follows: n Choose All Programs ® Microsoft SQL Server 2005 ® Configuration Tools ® SQL Server Configuration Manager. When the setup process has finished. Leave the selection unchanged. based on code point comparison. n Expand SQL Server 2005 Network Configuration and select one of the following: n For a default instance.

If you have not yet clustered the database. choose OK and log on again.3. 142 PUBLIC 09/11/2006 . 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). bring the database group online. 4. b) Select Sharing and in the Share Name field.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. as described below. Procedure 1. 4. position the cursor on a parameter and press F1 in SAPinst. If you are installing the SCS instance with SAPinst for the first time and SAPinst prompts you to log off.3 High Availability with Microsoft Cluster Service Installation 7. Check that the ASCS instance is running. make sure that the permission for User Everyone for SAPMNT is set to Full Control. Caution . 3. Therefore. Caution Make sure that you install the SCS instance on the same shared disk as the ASCS instance. . Caution You have to reset the permissions for the SAPMNT share from Read to Full Control. Recreate the SAPMNT share for the directory usr\sap.3. Follow the instructions in the SAPinst dialogs and enter the required parameters.7 7. restart the database service.3. 2. 2. enter SAPMNT. Note For more information about the input parameters. c) Under Permissions. move all resources back to the original node.5 Installing the Central Services Instance (SCS) .4 Installing the Central Services Instance for ABAP (ASCS) 1. If you have already clustered the database. Run SAPinst [page 56] and choose <Your SAP System> ® SAP Systems ® <Database> ® High-Availability System ® Based on <technical stack> ® Central Services Instance (SCS). you have to return the system to the state it had before the reboot. after each reboot. as follows: a) Right-click on the directory usr\sap and choose Sharing and Security. In the Cluster Administrator. The ASCS installation drive must be a shared disk that belongs to the SAP cluster group. 1. . 7. A reboot means that resources fail over to another MSCS node. 7. 3.

position the cursor on a parameter and press F1 in SAPinst. n The ASCS and SCS installation drive(s) must be online on the first MSCS node. 3. Enter the required parameter values. 7. Prerequisites n You are logged on to the first MSCS node as domain administrator or as a local user with domain administration rights.3. Caution . Run SAPinst [page 56] and choose <Your SAP System> ® SAP Systems ® <Database> ® High-Availability System ® Based on <technical stack> ® First MSCS Node. Note If SAPinst prompts you to log off from your system. For more information. 4. resources fail over to another MSCS node. . Therefore.3 High Availability with Microsoft Cluster Service Installation 2. after each reboot you have to return the system to the state it had before the reboot. Procedure 1. Follow the instructions in the SAPinst dialogs and enter the required parameter values. see Performing a Domain Installation without being a Domain Administrator [page 36]. you have to run the cluster configuration option offered by the SAPinst tool. choose OK and log on again. Note For more information about the input parameters. Caution When you reboot during the conversion to MSCS [page 142]. The SCS installation drive must be a shared disk which belongs to the SAP cluster group.7 7. log off and log on again.6 Configuring the First MSCS Node To configure the first MSCS node so that it functions properly in MSCS. 09/11/2006 PUBLIC 143 . . Check that the SCS instance is running. If you are installing the SCS instance with SAPinst for the first time and SAPinst prompts you to log off. When you run this option it: n n n n Creates the SAP cluster group Copies tools to the SAPCluster directory Sets the SAPService to manual Makes sure that the SAPOsCol service is started from the SAPCluster directory . 2.

position the cursor on the parameter and press F1 in SAPinst. a) For the profile UNC path you have to use the virtual (A)SCS host name. position the cursor on a parameter and press the F1 key in SAPinst.3. 7. see: Distribution of Components to Disks for MSCS [page 120] . Note Make sure that you choose instance type ABAP + Java SCS Instances (ABAP+Java). For more information about the input parameters. you have to run the MSCS configuration option foreach additional MSCS node offered by the SAPinst tool.7 Installing the Database Instance Prerequisites n The SAP cluster group is Online on the first MSCS node. When the installation is finished. for example: \\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile. make sure that the following value is set in the default profile: enque/serverhost=<Virtual_(A)SCS_HostName> Result SAPinst converts the SAP instances on the first MSCS node for operation in MSCS.7 7. Procedure Perform the following steps 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. specify shared disks that are included in the MSSQL group. Follow the instructions in the SAPinst dialogs and enter the required parameter values.3. When you run this option it: n Creates users and groups n Sets the system and user environment n Enters required port numbers in the Windows services file 144 PUBLIC 09/11/2006 . n The DB cluster group is Online on the first MSCS node.8 Configuring the Additional MSCS Node To configure the additional MSCS node(s) in the cluster.3 High Availability with Microsoft Cluster Service Installation . Note For more information about the input parameters. 2. b) For the tempdb database. 1. 3. Note . c) Distribute the transaction logs and SAPdata files to at least two different shared disks that are included in the MSSQL group. 7. For more information. On the first MSCS node.

log off and log on again. Prerequisites n You are logged on to the additional MSCS node as domain administrator or as a local user with domain administration rights. Therefore. position the cursor on the parameter and press F1 in SAPinst. resources fail over to another MSCS node. SAPinst begins processing and converts the SAP instances on the other MSCS node for operation in MSCS. start the SAP cluster group SAP <SAPSID> as follows: a) Open the Cluster Administrator with Start ® Programs ® Administration Tools ® Cluster Administrator. which is the primary cluster node. Enter the required parameter values. Note If SAPinst prompts you to log off from your system. . 09/11/2006 PUBLIC 145 . 4. Note . log off and log on again. . n You have already configured the first MSCS node [page 143]. b) Select the SAP cluster group and bring it online. . Run SAPinst and choose <Your SAP System> ® SAP Systems ® <Database> ® High-Availability System ® Based on <technical stack> ® Additional MSCS Node. see Performing ad Domain Installation without being a Domain Administrator [page 36]. 2. Run SAPinst [page 56] and choose Additional MSCS Node. For more information about the input parameters. For more information.7 7. When SAPinst has finished. 3.3 High Availability with Microsoft Cluster Service Installation n Creates the SAPService and SAPOsCol Services . Procedure 1. Caution When you reboot during the conversion to MSCS [page 142]. When you have made all required entries. Note If SAPinst prompts you to log off from your system. after each reboot you have to return the system to the state it had before the reboot. Note Make sure that you choose instance type ABAP + Java SCS Instances (ABAP+Java).

Note You only need to do this once for all enqueue replication servers that you install on the MSCS nodes.\usr\sap\<SAPSID>\ERS<instance_number>\ Note . . Follow the instructions in the SAPinst dialogs and enter the required parameters. 3. 146 PUBLIC 09/11/2006 . After you have entered all required input information. when entering the parameters n On the SAPinst screen: SAP System > SAP Instance. enter a unique instance number that n is not in use by another instance on this host.9 Installing an Enqueue Replication Server We recommend that you install an enqueue replication server with SAPinst on all MSCS nodes where an SCS or ASCS instance is running. for each (A)SCS instance and on each MSCS node.3 High Availability with Microsoft Cluster Service Installation 7. start SAPinst to install the enqueue replication server for the SCS or ASCS instance as described in step 2 above. the enqueue server instance is started. SAPinst installs the enqueue replication server instance on a local disk in the following directory: . Procedure 1. The enqueue replication server instance uses the profile from the local instance profile folder: . or later with the Cluster Administrator. Prerequisites n Your SCS and ASCS instance is already clustered with MSCS.7 7. log on as domain user who is a member of the local administrators group. Note You have to perform the installation at least four times. During the process phase. The profile is replicated from the global host to the local instance profile folder. 2. enter the: l SAP system ID <SAPSID> of your SAP system l Instance number of the SCS or ASCS instance l Virtual instance host name of the SCS or ASCS instance On the SAPinst screen SAP System > Enqueue Replication Server Instance. Run SAPinst [page 56] and choose <Your SAP System> ® SAP Systems ® <Database> ® High-Availability System ® Based on <technical stack> ® Enqueue Replication Server. Note the following. On the additional MSCS node. n You have to install the enqueue replication server on a local disk. On the first MSCS node.\usr\sap\<SAPSID>\ERS<instance_number>\profile\ 4. . n Decide if you want to restart the SCS and ASCS instance and service cluster resources with SAPinst now. SAPinst starts the installation and displays the progress of the installation.3.

Note There is no need to move the SCS or ASCS cluster group to another MSCS node. You have the following options to install the dialog instance: n You install the dialog instance on an MSCS node. l Installation Drive. n You install the central instance on a host outside of MSCS. bring the SAP cluster group online on this node. If SAPinst prompts you to log off. 4. 5. you use the UNC path of the virtual (A)SCS host name.7 7. 3. Follow the instructions in the SAPinst dialogs and enter the required parameter values. choose OK and log on again.3. you have to install the database client software on this host. You have the following options to install the central instance: n You install the central instance on an MSCS node. Run SAPinst [page 56] and choose <Your SAP System> ® SAP Systems ® <Database> ® High-Availability System ® Based on <technical stack> ® Central Instance. Check that the central instance is running.3 High Availability with Microsoft Cluster Service Installation . you choose the local disk where you want to install the central instance. for example: \\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile. make sure that on the screen SAP System > General Parameters for the: l Profile Directory. 7. Enter the required parameter values in the SAPinst dialogs as described above.3. Do not enter the shared disk for the (A)SCS instance. position the cursor on a parameter and press F1 in SAPinst. 2.11 Installing the Dialog Instance You have to install at least one dialog instance for MSCS. For more information about the input parameters. In this case. 09/11/2006 PUBLIC 147 . In this case. Caution n If you install the central instance on an MSCS node. Note . Procedure 1. 7.10 Installing the Central Instance The following describes how to install the central instance for MSCS. . and make sure that the central instance number is different from the (A)SCS instance number.

for example: \\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile. Procedure 1. Caution n If you install the dialog instance on an MSCS node. Follow the instructions in the SAPinst dialogs and enter the required parameter values. 7. . l Installation Drive. 3. and make sure that the dialog instance number is different from the (A)SCS instance number. If required. you use the UNC path of the virtual (A)SCS host name. you choose the local disk where you want to install the dialog instance.4 Post-Installation This section describes how to complete and check the installation of the SAP system for an MSCS configuration: 1. 4. you have to install the database client software on this host. 2. 4. Caution Make sure that on the screen SAP System > General Parameters for the Profile Directory. If SAPinst prompts you to log off. Do not enter the shared disk for the (A)SCS instance.4. install additional dialog instances outside of MSCS. You have installed at least one SAP front end [page 39]. for example: \\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile. Note . Run SAPinst [page 56] and choose <Your SAP System> ® SAP Systems ® <Database> ® High-Availability System ® Based on <technical stack> ® Dialog Instance 2. 3. choose OK and log on again. you use the UNC path of the virtual (A)SCS host name. n You install the dialog instance on a host outside of MSCS. In this case. make sure that on the screen SAP System > General Parameters for the: l Profile Directory. position the cursor on a parameter and press F1 in SAPinst.4 High Availability with Microsoft Cluster Service Post-Installation In this case. For more information about the input parameters. You perform the post-installation checks for the enqueue replication server [page 149]. 7.1 Starting and Stopping the SAP System in an MSCS Configuration The following describes how to start or stop the SAP system in an MSCS configuration with the: 148 PUBLIC 09/11/2006 . . you perform the other post-installation steps [page 71] listed in Chapter 6 in this guide. You start and stop the SAP system in an MSCS configuration [page 148].7 7. bring the SAP cluster group online on this node. If required.

7.7 7. which allow remote access to the enqueue server statistics.2. 7. To start or stop all instances belonging to the SAP cluster group. You check the fill status and ID of the lock table during failover with the ENQT tool [page 150]. Note You also use the Cluster Administrator for all other administrative tasks like moving instances from one MSCS node to another MSCS node. Before you can use these tools you must copy them to the remote host where the Enqueue Replication Server is running and from where you want to start the tests. 2.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 from where you run the tests. 09/11/2006 PUBLIC 149 .2 Post-Installation Checks for Enqueue Replication Server . see Starting and Stopping the SAP System [page 71]. 3. 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. You copy ENQT.4 High Availability with Microsoft Cluster Service Post-Installation n SAP MMC n Cluster Administrator .1 Checking the Status of the Enqueue Replication Server with ENSMON You use the ENSMON tool to check if the enqueue replication server and the enqueue server are properly connected. n To start or stop your SAP system with the Cluster Administrator do the following: 1.4. You check the status of the enqueue replication server with the ENSMON tool [page 149]. Start the Cluster Administrator by choosing Start ® Programs ® Administrative Tools ® Cluster Administrator. The following sections describe the tests you must perform to check whether the installed enqueue replication server works properly.exe and ENSMON.4. You perform the following steps: 1. To start or stop a single instance of the SAP cluster group. 3. Procedure n To start or stop your SAP system with the SAP MMC. right-click the SAP cluster group SAP <SAPSID> and choose Bring online or Take offline. 2. right-click the instance SAP <SAPSID> <instance_no> Instance and choose Bring online or Take offline. For these tests you use the ENQT and ENSMON command line tools.

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 the ENQT tool. Use the following command to fill the lock table of the enqueue server with 20 locks: enqt pf=<ERS_instance_profile> 11 20 where <ERS_instance_profile> is the profile created during the installation of the Enqueue Replication Server.. server is connected n If the enqueue replication server and the enqueue server are not properly connected. Prerequisites n You have started the SCS and ASCS instances of your SAP system. repl. server is connected 7.4 High Availability with Microsoft Cluster Service Post-Installation Prerequisites n You have started the SCS and ASCS instances of your SAP system.2. but no repl. n If the enqueue replication server and the enqueue server are properly connected. Replication is active . the output is similar to this: Try to connect to host <Virtual (A)SCS host> service sapdp01 get replinfo request executed successfully Replication is enabled in server.. n You run the ENQT tool from the host where you installed the Enqueue Replication Server. n You run the ENSMON tool from the host where you installed the Enqueue Replication Server. Monitoring the Lock Table Fill Status During Failover with ENQT 1. 2. the output is similar to this: Try to connect to host <Virtual (A)SCS host> service sapdp01 get replinfo request executed successfully Replication is enabled in server.4.. Procedure To 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 Replication Server. . Caution Only use the ENQT commands stated in this procedure otherwise you might damage the enqueue server’s lock table. .. Monitor the fill status of the lock table with the following command: 150 PUBLIC 09/11/2006 .7 7.

7 7.4

High Availability with Microsoft Cluster Service Post-Installation

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 number of the table entries to the console. 3. Move the (A)SCS cluster group to another MSCS node to simulate an enqueue server failover while running the ENQT command. The output is similar to this:
Number of selected entries: Number of selected entries: Number of selected entries: Number of selected entries: Number of selected entries: Number of selected entries: Number of selected entries: Number of selected entries: Number of selected entries: Number of selected entries: Number of selected entries: ... 20 20 20 20 20 0 ( enqueue server fails over ) 20 ( enqueue server is running again ) 20 20 20 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

where <ERS_instance_profile> is the profile created during the installation of the Enqueue Replication Server. 2. Move the (A)SCS cluster group to another MSCS node to simulate an enqueue server failover while running 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: / 9288 ... EnqTabCreaTime/RandomNumber = 25.10.2005 11:15:59 1130231759

(Output after failover)
C:\WORK\HA\ENQU-Tests>enqt pf=BUG_ERS01_PCJ2EEV6 97 ---REQ---------------------------------------------------------EnqId: / 9288 ... EnqTabCreaTime/RandomNumber = 25.10.2005 11:15:59 1130231759

3. Make sure that the lock table ID (ENQID) is the same before and after the failover.

09/11/2006

PUBLIC

151

This page is intentionally left blank.

A

Reference

A Reference

A.1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various phases 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

and third-party applications that are required for each Business Scenario.sap.1 Reference The Main SAP Documentation Types SAP Library—The SAP Library is a collection of function. n Target group: l Technology consultants l System administrators l Project teams for implementations n Current version: l Located in the SAP Service Marketplace at service.com/instguides Component Installation Guide—The Component Installation Guide describes the technical implementation of an SAP component. execution. A collective security guide is available for the SAP NetWeaver technologies.A A.com/ibc (only the Business Scenario Descriptions) Implementation Guide (IMG)—The Implementation Guide is a tool for configuring the SAP system to meet customer requirements. This document contains general guidelines and suggestions about system security. and follow-up of an implementation. 154 PUBLIC 09/11/2006 . It provides scenario-specific descriptions of preparation. Other technologies and individual applications have a Security Guide of their own. It does not describe any business-related configuration.and process-oriented documentation for SAP components.sap. The SAP Library also contains the Business Scenario Descriptions. n Target group: l Consultants l System administrators l Project teams for implementations or upgrades Current version: n l Located in the SAP Help Portal at help.com/securityguide Implementation Master Guide—The Master Guide is the starting point for implementing an SAP solution. taking into account the combinations of operating systems and databases.sap. n Target group: l Technology consultants l Solution consultants l Project teams for implementations or upgrades Current version: n l Located in the SAP Service Marketplace at service.sap.com (also available as documentation CD) l Located in the SAP Service Marketplace at service. such as the SAP NetWeaver Application Server (SAP NW AS). It lists the required SAP components. n Target group: l Solution consultants l Project teams for implementations or upgrades n 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 suggestions for raising security levels. such as Component Installation Guides and SAP Notes. It also offers references to other documents. Its structure and documentation are component-oriented.

and tests. transactions. and follow-up of an upgrade.sap.com/instguides Configuration Documentation in SAP Solution Manager—SAP Solution Manager is a tool with various functions. execution. transports. It contains IMG activities. there might be several Business Scenario Upgrade Guides or a Solution Upgrade Guide for previous shipments of the Business Scenarios of an SAP solution.sap.sap. backup / restore. n Target group: l Solution consultants l Project teams for implementations n Current version: l In SAP Solution Manager l Located in the SAP Service Marketplace at service. there might be separate Business Scenario Configuration Guides in the SAP Service Marketplace for previous shipments of the Business Scenarios. and the Component Management Guides. such as monitoring. such as the Component Upgrade Guides and SAP Notes. The guide refers users to the tools and documentation that are needed to carry out various tasks. master data maintenance. the Master Guide.A A. as well as documentation. one of its main functions being the configuration of SAP solutions and Business Scenarios.com/ibc Production Operation Solution Management Guide—The Solution Management Guide is the starting point for operating an SAP solution.com/instguides 09/11/2006 PUBLIC 155 .1 Reference The Main SAP Documentation Types n Target group: l Technology consultants l Project teams for implementations n Current version: l Located in the SAP Service Marketplace at service. It also refers users to other documents.com/instguides Upgrade Upgrade Master Guide—The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of an SAP solution. Instead of an Upgrade Master Guide. n Target group: l System administrators l Technology consultants l Solution consultants l Project teams for implementations or upgrades n Current version: l Located in the SAP Service Marketplace at service. Instead of the configuration documentation in SAP Solution Manager. It provides scenario-specific descriptions of preparation.sap. n Target group: l Technology consultants l Project teams for upgrades n Current version: l Located in the SAP Service Marketplace at service. for example the SAP Library. and so on. It also refers to other documents.

sap. taking into account the combinations of operating systems and databases. It does not describe any business-related configuration.com/releasenotes l In the SAP menu of the SAP system under Help ® Release Notes (only ABAP developments) 156 PUBLIC 09/11/2006 . n Target group: l Technology consultants l Project teams for upgrades Current version: n l Located in the SAP Service Marketplace at service.A A.1 Reference The Main SAP Documentation Types Component Upgrade Guide—The Component Upgrade Guide describes the technical upgrade of an SAP component.sap. Release Notes about ABAP developments enable the SAP system to generate delta and upgrade IMGs n Target group: l Consultants l Project teams for upgrades n Current version: l Located in the SAP Service Marketplace at service.com/instguides Release Notes—Release Notes are documents that contain short descriptions of new features or changes in an SAP component since the previous release.

This page is intentionally left blank. .

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.com © Copyright 2006 SAP AG. The information contained herein may be changed without prior notice. . All rights reserved.sap.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.

Sign up to vote on this title
UsefulNot useful