sap netweaver 7.0 sr2 abap+java on windows ms sql server

PUBLIC

Installation Guide

SAP NetWeaver 7.0SR2 ABAP+Java onWindows: MS SQLServerIncluding:

SAP NetWeaver Application Server ABAP (AS ABAP)

SAP NetWeaver Application Server Java (AS Java)

SAP NetWeaver Business Intelligence Java Components (BI)

SAP NetWeaver Development Infrastructure (DI)

SAP NetWeaver EP Core (EPC)

SAP NetWeaver Enterprise Portal (EP)

SAP NetWeaver Mobile Infrastructure (MI)

SAP NetWeaver Process Integration (PI)

Application Sharing Server (Optional Standalone Unit)

Target Audience

n System Administrators

n Technical Consultants

Document version: 2.0 ‒ 08/31/2007

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

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

www.sap.com

© Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The information containedherein may be changed without prior notice.Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPoint areregistered 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, System i, System i5, System p,System p5, System x, System z, System z9, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,i5/OS, POWER, POWER5, POWER5+, OpenPower andPowerPC are trademarks or registered trademarks of IBMCorporation.Adobe, the Adobe logo, Acrobat, PostScript, and Readerare either trademarks or registered trademarks of AdobeSystems Incorporated in the United States and/or othercountries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarksof the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems, Inc.HTML, XML, XHTML andW3C are trademarks or registeredtrademarks 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 andimplemented by Netscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAPNetWeaver, and other SAP products and services mentionedherein as well as their respective logos are trademarks or

registered trademarks of SAP AG in Germany and in severalother countries all over the world. All other productand service names mentioned are the trademarks of theirrespective companies. Data contained in this documentserves informational purposes only. National productspecifications may vary.These materials are subject to change without notice.These materials are provided by SAP AG and its affiliatedcompanies (“SAP Group”) for informational purposesonly, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions withrespect to thematerials. The only warranties for SAP Groupproducts and services are those that are set forth in theexpress warranty statements accompanying such productsand services, if any. Nothing herein should be construed asconstituting an additional warranty.

This document was created using stylesheet 2006-12-31(V5.1beta [= 6.0 for E3]) and XSLT processor SAXON 6.5.2fromMichael Kay (http://saxon.sf.net/), XSLT version 1.

DisclaimerSome components of this product are based on Java™. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product isonly to be used by SAP’s Support Services and may not bemodified or altered in any way.

Legal Software Terms

Terms for Included Open Source SoftwareThis SAP software contains also the third party opensource software products listed below. Please note that forthese third party products the following special terms andconditions shall apply.

1. This software was developed using ANTLR.

2. SAP License Agreement for STLportSAP License Agreement for STLPort between

2/208 PUBLIC 08/31/2007

SAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)

a) Subject Matter of the Agreement

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

B) By downloading, using, or copying STLport orany portion thereof Customer agrees to abideby the intellectual property laws, and to all ofthe terms and conditions of this Agreement.

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

D) Customer shall maintain the followingcopyright and permissions notices on STLportsources and its documentation unchanged:Copyright 2001 SAP AG

E) The Customer may distribute original ormodified 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 inaccompanying permission notices are met:Coypright 1994 Hewlett-PackardCompanyCopyright 1996,97 Silicon GraphicsComputer Systems Inc.Copyright 1997 Moscow Center forSPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute andsell this software and its documentation forany purposes is hereby granted without fee,provided that the above copyright notice appearin all copies and that both that copyright noticeand this permission notice appear in supportingdocumentation. Hewlett-Packard Companymakes no representations about the suitabilityof this software for any purpose. It is provided“as is” without express or implied warranty.

Permission to use, copy, modify, distribute andsell this software and its documentation for anypurpose is hereby granted without fee, providedthat the above copyright notice appear in allcopies and that both that copyright notice andthis permission notice appear in supportingdocumentation. Silicon Graphics makes norepresentations about the suitability of thissoftware for any purpose. It is provided “as is”without express or implied warranty.Permission to use, copy, modify, distribute andsell this software and its documentation forany purposes is hereby granted without fee,provided that the above copyright notice appearin all copies and that both that copyright noticeand this permission notice appear in supportingdocumentation. Moscow Center for SPARCmakes no representations about the suitabilityof this software for any purpose. It is provided“as is” without express or implied warranty.Boris Fomitchev makes no representationsabout the suitability of this software for anypurpose. This material is provided "as is", withabsolutely no warranty expressed or implied.Any use is at your own risk. Permission touse or copy this software for any purpose ishereby granted without fee, provided the abovenotices are retained on all copies. Permissionto modify the code and to distribute modifiedcode is granted, provided the above noticesare retained, and a notice that the code wasmodified is included with the above copyrightnotice.Permission to use, copy, modify, distributeand sell this software and its documentationfor any purposes is hereby granted withoutfee, provided that the above copyright noticeappear in all copies and that both that copyrightnotice and this permission notice appear insupporting documentation. SAP makes norepresentations about the suitability of thissoftware for any purpose. It is provided with alimited warranty and liability as set forth in theLicense Agreement distributed with this copy.SAP offers this liability and warranty obligationsonly towards its customers and only referringto its modifications.

b) Support and MaintenanceSAP does not provide software maintenance for theSTLport. Software maintenance of the STLporttherefore shall be not included.

08/31/2007 PUBLIC 3/208

All other services shall be charged according to therates for services quoted in the SAP List of Pricesand Conditions and shall be subject to a separatecontract.

c) Exclusion of warrantyAs the STLport is transferred to the Customer on aloan basis and free of charge, SAP cannot guaranteethat the STLport is error-free, without materialdefects or suitable for a specific application underthird-party rights. Technical data, sales brochures,advertising text and quality descriptions producedby SAP do not indicate any assurance of particularattributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall onlybe liable for damage, including unauthorizedoperation, if this (i) can be compensated underthe Product Liability Act or (ii) if caused due togross negligence or intent by SAP or (iii) if basedon the failure of a guaranteed attribute.

B) If SAP is liable for gross negligence or intentcaused by employees who are neither agents ormanagerial employees of SAP, the total liabilityfor such damage and a maximum limit on thescope of any such damage shall depend onthe extent to which its occurrence ought tohave anticipated by SAP when concluding thecontract, due to the circumstances known toit at that point in time representing a typicaltransfer of the software.

C) In the case of Art. 4.2 above, SAP shall notbe liable for indirect damage, consequentialdamage caused by a defect or lost profit.

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

E) The Customer shall take adequate measuresfor the protection of data and programs, inparticular by making backup copies at theminimum intervals recommended by SAP. SAPshall not be liable for the loss of data and itsrecovery, notwithstanding the other limitationsof the present Art. 4 if this loss could have beenavoided by observing this obligation.

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

3. Adobe Document ServicesAdobe, the Adobe logo, Acrobat, PostScript, and Readerare either registered trademarks or trademarks ofAdobe Systems Incorporated in the United States and/ or other countries. For information on Third Partysoftware delivered with Adobe document services andAdobe LiveCycle Designer, see SAP Note 854621.

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

4/208 PUBLIC 08/31/2007

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

https://service.sap.com/instguides



Typographic Conventions

Example Description

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

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

Example Emphasized words or expressions

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

Example Textual cross-references to an internet address, for example, http://www.sap.com

/example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

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

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

n Cross-references to other documentation or published works

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

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, database table names, and key concepts of a programming languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

08/31/2007 PUBLIC 5/208

http://www.sap.com

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


Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan find the latest version on SAP Service Marketplace http://service.sap.com/instguides.

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

Version Date Description

2.00 8/31/2007 Updated Version ‒ Terminology changes

6/208 PUBLIC 08/31/2007

http://service.sap.com/instguides



Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 111.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 121.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 151.3 Information Available on SAP Service Marketplace . . . . . . . . . . 151.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 17

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 192.1 Basic System Variants . . . . . . . . . . . . . . . . . . . . . 202.2 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . 222.3 How to Distribute Instances to Hosts for a Java Add-In Installation . . . . 232.4 Production Client Considerations . . . . . . . . . . . . . . . . 242.5 System Configuration . . . . . . . . . . . . . . . . . . . . . 252.5.1 Distribution of Components to Disks . . . . . . . . . . . . . . . 262.5.2 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . 292.6 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 332.7 Multi-Language and Unicode Support . . . . . . . . . . . . . . . 392.8 Running Adobe Document Services on Non-Supported Platforms . . . . 412.9 Application Sharing Server as an Optional Standalone Unit . . . . . . . 41

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 433.1 Hardware and Software Requirements . . . . . . . . . . . . . . . 433.1.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 443.1.2 Requirements Checklist for a Central System . . . . . . . . . . . . 453.1.3 Requirements Checklist for a Distributed System . . . . . . . . . . . 473.1.3.1 Requirements Checklist for the ABAP Central Services Instance . . . . . 473.1.3.2 Requirements Checklist for the Central Services Instance . . . . . . . . 493.1.3.3 Requirements Checklist for the Database Instance . . . . . . . . . . 503.1.3.4 Requirements Checklist for the Central Instance . . . . . . . . . . . 513.1.3.5 Requirements Checklist for the Dialog Instance . . . . . . . . . . . 533.2 Checking the Windows File System . . . . . . . . . . . . . . . . 543.3 Checking the Windows Domain Structure . . . . . . . . . . . . . 543.4 Reducing the Size of the File Cache . . . . . . . . . . . . . . . . 553.5 Granting User Rights for the Installation . . . . . . . . . . . . . . 563.6 Performing a Domain Installation Without Being a Domain Administrator . 573.7 Preparing the SAP System Transport Host . . . . . . . . . . . . . 59

08/31/2007 PUBLIC 7/208

3.8 Installing the SAP Front-End Software . . . . . . . . . . . . . . . 603.9 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 613.10 Installing the Java Development Kit . . . . . . . . . . . . . . . . 613.11 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 623.12 Downloading Installation DVDs from SAP Service Marketplace (Optional) . 64

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 674.1 Installing the SQL Server Database Software . . . . . . . . . . . . . 674.1.1 Installing the SQL Server Database Software with SQL4SAP . . . . . . . 674.1.2 Installing the SQL Server Database Software Manually . . . . . . . . . 694.1.2.1 Installing the SQL Server 2000 Database Software on 32-Bit Manually . . . 694.1.2.2 Installing the SQL Server 2000 Database Software on 64-Bit Manually . . . 714.1.2.3 Installing the Corrected MS SQL Server Collation for MS SQL Server 2000 . . 734.1.2.4 Installing the SQL Server 2005 Database Server Software Manually . . . . 744.1.2.5 Installing the SQL Server 2005 Native Client Software Manually . . . . . 784.2 Preparing your System for a Java Add-In Installation . . . . . . . . . 784.3 Installing an SAP System Using SAPinst . . . . . . . . . . . . . . 794.3.1 Running SAPinst on Windows . . . . . . . . . . . . . . . . . . 794.3.2 Installing the Java Add-In for an Existing ABAP System (Optional) . . . . 874.3.3 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 894.3.4 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 904.3.5 Performing a Remote Installation with SAPinst (Optional) . . . . . . . 924.3.6 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 924.3.7 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 944.4 Installing Application Sharing Server as an Optional Standalone Unit . . . 95

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 975.1 Starting and Stopping the SAP System . . . . . . . . . . . . . . . 985.2 Logging On to the SAP System . . . . . . . . . . . . . . . . . 1005.3 Logging on to the Portal . . . . . . . . . . . . . . . . . . . . 1025.4 Installing the SAP License . . . . . . . . . . . . . . . . . . . 1045.5 Installing the SAP Online Documentation . . . . . . . . . . . . . 1045.6 Configuring Remote Connection to SAP Support . . . . . . . . . . 1055.7 Performing Initial ABAP Configuration . . . . . . . . . . . . . . 1055.8 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 1075.9 Performing the Client Copy . . . . . . . . . . . . . . . . . . 1085.10 Performing a Full Installation Backup . . . . . . . . . . . . . . . 1095.11 Single Sign-On with Microsoft Lan Manager SSP . . . . . . . . . . . 1105.11.1 Preparing the Application Server for Single Sign-On . . . . . . . . . . 1125.11.2 Preparing SAP GUI and SAP Logon for Single Sign-On . . . . . . . . . 1135.11.3 Mapping SAP Users to Windows Users for Single Sign-On . . . . . . . . 1145.12 Single Sign-On with Microsoft Kerberos SSP . . . . . . . . . . . . 115

8/208 PUBLIC 08/31/2007

5.12.1 Preparing the Central Instance . . . . . . . . . . . . . . . . . 1165.12.2 Configuring the SAP Front End . . . . . . . . . . . . . . . . . 1175.12.3 Activating Single Sign-On for the SAP Logon . . . . . . . . . . . . 1185.12.4 Mapping SAP Users to Windows Users . . . . . . . . . . . . . . . 1195.13 Post-Installation Steps for Adobe Document Services . . . . . . . . . 1205.13.1 Assigning Roles to Users ADSUSER and ADS_AGENT . . . . . . . . . 1205.13.2 Installation Check and Quick Tests for Adobe Document Services . . . . 1205.14 Configuring Access to Knowledge Warehouse Content from the SAP Internet

Knowledge Servlet . . . . . . . . . . . . . . . . . . . . . . 1225.15 Setting Environment Variable CPIC_MAX_CONV . . . . . . . . . . 1235.16 Post-Installation Steps for Usage Type Process Integration (PI) . . . . . . 1235.16.1 Performing PI-Specific Steps for SLD Configuration . . . . . . . . . . 1235.17 Post-Installation Steps for Application Sharing Server . . . . . . . . . 1245.18 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 1245.19 Running the Configuration Wizard . . . . . . . . . . . . . . . . 1275.20 Checking the SAP Java Documentation . . . . . . . . . . . . . . 1305.21 Accessing Configuration Documentation in the SAP Solution Manager . . 132

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 1356.1 Database Installation for Multiple Components with MS SQL Server . . . . 1356.1.1 Default or Named MS SQL Server Instances . . . . . . . . . . . . . 1366.2 Installation of Multiple Components in One Database (Optional) . . . . . 1376.3 Integration of LDAP Directory Services (Optional) . . . . . . . . . . 1396.4 Setting Up the Active Directory Services (Optional) . . . . . . . . . . 1426.5 Preparing User Management for an External ABAP System . . . . . . . 1436.6 Configuring User Management to Use an LDAP Directory (Optional) . . . 1466.7 Usage Type-Specific Initial Technical Configuration . . . . . . . . . . 1466.7.1 Initial Technical Configuration for Application Server . . . . . . . . . 1476.7.1.1 Initial Technical Configuration for Adobe Document Services . . . . . . 1476.7.1.2 Initial Technical Configuration for Composite Application Framework Core 1486.7.1.3 Configuring System Landscape Directory . . . . . . . . . . . . . 1486.7.2 Initial Technical Configuration for Development Infrastructure (DI) . . . 1496.7.3 Initial Technical Configuration for the Portal . . . . . . . . . . . . 1496.7.4 Initial Technical Configuration for Process Integration (PI) . . . . . . . 1506.7.4.1 Importing the SAP Exchange Profile . . . . . . . . . . . . . . . 1516.7.4.2 Assigning SAP_ALL Rights to User PISUPER . . . . . . . . . . . . 1526.7.4.3 Activating the ICF Services . . . . . . . . . . . . . . . . . . . 1526.7.4.4 Assigning Roles to Groups . . . . . . . . . . . . . . . . . . . 1526.7.5 Initial Technical Configuration for BI Java . . . . . . . . . . . . . 1536.7.5.1 Configuring BI Java Information Broadcasting . . . . . . . . . . . . 1536.7.5.2 Process Chains: Transporting Texts for the Alert Category . . . . . . . 1546.7.5.3 Renaming initialPermissionsBI.xml.template . . . . . . . . . . . . 154

08/31/2007 PUBLIC 9/208

6.8 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 1556.8.1 Running SAPinst to Delete an SAP System . . . . . . . . . . . . . 1566.9 SAP System Security on Windows . . . . . . . . . . . . . . . . 1576.10 Automatic Creation of Accounts and Groups . . . . . . . . . . . . 1596.11 Manually Granting User Rights for the Installation . . . . . . . . . . 1606.12 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 1616.12.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 1616.12.2 Troubleshooting for Portal Installation . . . . . . . . . . . . . . 162

Chapter 7 High Availability with Microsoft Cluster Service . . . . . . . . . 1657.1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 1667.1.1 SAP System Components in an MSCS Configuration . . . . . . . . . 1667.1.2 Enqueue Replication Server in an MSCS Configuration . . . . . . . . 1707.1.3 Distribution of Components to Disks for MSCS . . . . . . . . . . . 1717.1.4 Directories in an MSCS Configuration . . . . . . . . . . . . . . . 1737.1.5 IP Addresses in an MSCS Configuration . . . . . . . . . . . . . . 1737.1.6 Obtaining IP Addresses for MSCS . . . . . . . . . . . . . . . . . 1777.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 1797.2.1 Checking Hardware and Software Requirements for MSCS . . . . . . . 1807.2.2 Assigning Drive Letters for MSCS . . . . . . . . . . . . . . . . 1817.2.3 Mapping Host Names to IP Addresses for MSCS . . . . . . . . . . . 1827.2.4 Checking the Mapping of Host Names for MSCS . . . . . . . . . . . 1837.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . 1847.3.1 Clustering the SQL Server Database Software . . . . . . . . . . . . 1857.3.1.1 Clustering the SQL Server 2000 Database Software in a 32-Bit System . . . . 1857.3.1.2 Clustering the SQL Server 2000 Database Software in a 64-Bit System . . . . 1877.3.1.3 Clustering the SQL Server 2005 Database Server Software . . . . . . . . 1897.3.2 Moving MSCS Groups . . . . . . . . . . . . . . . . . . . . 1947.3.3 Rebooting During the Installation or Conversion for MSCS . . . . . . . 1947.3.4 Installing the Central Services Instance for ABAP (ASCS) . . . . . . . . 1957.3.5 Installing the Central Services Instance (SCS) . . . . . . . . . . . . 1957.3.6 Configuring the First MSCS Node . . . . . . . . . . . . . . . . 1967.3.7 Installing the Database Instance . . . . . . . . . . . . . . . . . 1977.3.8 Configuring the Additional MSCS Node . . . . . . . . . . . . . . 1987.3.9 Installing an Enqueue Replication Server . . . . . . . . . . . . . . 1997.3.10 Installing the Central Instance . . . . . . . . . . . . . . . . . 2007.3.11 Installing the Dialog Instance . . . . . . . . . . . . . . . . . . 2017.4 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . 2027.4.1 Starting and Stopping the SAP System in an MSCS Configuration . . . . . 2037.4.2 Post-Installation Checks for Enqueue Replication Server . . . . . . . . 2037.4.2.1 Checking the Status of the Enqueue Replication Server with ENSMON . . . 2047.4.2.2 Monitoring the Lock Table During Failover with ENQT . . . . . . . . 204

10/208 PUBLIC 08/31/2007

1 Introduction

1 Introduction

This document explains how to install SAP NetWeaver 7.0 SR2 ABAP+Java.It also explains how to install the Java Add-In for an existing SAP NetWeaver 7.0 SR2 ABAP system.For more information about SAP NetWeaver technology, see SAP Service Marketplace athttp://service.sap.com/netweaver.You can install SAP NetWeaver 7.0 SR2 ABAP+Java and the Java Add-In with the following usagetypes in a single installation run using SAPinst:

n

Only valid for: Application Server (AS)

SAP NetWeaver Application Server ABAP (AS ABAP)

Note

AS ABAP is not installed with the Java Add-In.

End of: Application Server (AS)

n SAP NetWeaver Application Server Java (AS Java)

n

Only valid for: Development Infrastructure (DI)

SAP NetWeaver Development Infrastructure (DI)End of: Development Infrastructure (DI)

n

Only valid for: EP Core (EPC)

SAP NetWeaver EP Core (EPC)End of: EP Core (EPC)

n

Only valid for: Enterprise Portal (EP)

SAP NetWeaver Enterprise Portal (EP)If you install usage type EP, note the following:l You must install SAP NetWeaver Application Server Java (AS Java) and EP Core (EPC)l The Application Sharing Server is installed automatically with usage type EP. For production

use, we recommend that you install the server as an optional standalone unit on a dedicatedhost as described in this document.

End of: Enterprise Portal (EP)

n

Only valid for: BI Java Components (BI-Java)

SAP NetWeaver Business Intelligence Java Components (BI Java)

08/31/2007 PUBLIC 11/208

http://service.sap.com/netweaver



1 Introduction1.1 New Features

You also have to install SAP NetWeaver Application Server Java (AS Java), EP Core (EPC) andSAP NetWeaver Portal (EP).End of: BI Java Components (BI-Java)

n

Only valid for: Mobile Infrastructure (MI)

SAP NetWeaver Mobile Infrastructure (MI)End of: Mobile Infrastructure (MI)

n

Only valid for: Process Integration (PI)

SAP NetWeaver Process Integration (PI)End of: Process Integration (PI)

Note

If you want to add additional usage types to an existing SAP system, follow SAP Note 883948.

For more information about the usage types of SAP NetWeaver and their interdependencies, seethe documentMaster Guide ‒ SAP NetWeaver 7.0 on SAP Service Marketplace [page 15]. For restrictions,see SAP Note 855534.

Constraints

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

n Youmust only use the SAP installation tools according to the instructions and for the purposesdescribed in the SAP installation document. Improper use of the SAP installation tools can damagefiles and systems already installed.

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

n For downward-compatible releases of DB/OS platforms for SAP products, SAP plans to regularlyrelease the newest database (DB) and operating-system (OS) versions of SAP products. Thesereleases are downward-compatible with earlier SAP system releases.Note that for already shipped SAP components, we only support the installation for databaseversions proposed by the installation tool. Therefore, you must install a SAP component orperform a system copy using a downward-compatible database as follows:l Install the component with the old proposed database version.l Upgrade the old database version to the downward-compatible new version.

1.1 New Features

Here you can find the new features in this release.

12/208 PUBLIC 08/31/2007




SAP System Installation

Area Description

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

Checker [page 44].n You can install a central system in one of two modes:l Typical Mode

If you choose Typical, your SAP system is installed with default settings. As aresult, you only have to respond to a small selection of prompts. If you want tochange any of the default settings, you can do so on the parameter summaryscreen at the end of the installation.

l Custom ModeIf you choose Custom, you must manually enter all installation parameters. Youcan change your values on the parameter summary screen at the end of theinstallation.

n You can uninstall an SAP system or an SAP component with the SAPinst serviceUninstall ‒ System / Standalone Engines / Optional Standalone Unit.

n You can install the Java Add-In for an existing ABAP system. This means that yourun SAPinst to execute the following:l Install the central services instance (SCS)l Add the Java database schema to the existing ABAP database instance.l Add the Java central instance with usage types to the existing ABAP central

instance.

NoteYou cannot install the Java Add-In for the dialog instance(s) of the existing ABAPsystem. Instead, you have to install an ABAP+Java dialog instance(s).

n You can change the default names of the Java users J2EE_ADMIN, J2EE_GUEST andSAPJSF during the input phase of the installation.

n You assign one Master Password to all users created by SAPinst. This password is usedfor all user accounts and for the secure store key phrase.

n SAPinst fills in most of the input parameter fields with default values.If required, you can change the default values on the Parameter Summary screen beforeyou start the actual installation.

Installation DVDs You start the installation from a single Installation Master DVD.

Usage type EP Core(EPC)

As of SAP NetWeaver 7.0 SR2, usage type Enterprise Portal (EP) has been separated intotwo closely related usage types: EP Core (EPC) and Enterprise Portal (EP). Usage typeEPC provides the core portal capabilities available in the former usage type EP. Usagetype EP now includes all portal add-on capabilities it provided before, but without thecore portal functionality.As of SAP NetWeaver 7.0 SR2, usage type Enterprise Portal (EP) is now divided into twodifferent usage types, EP Core (EPC) and Enterprise Portal (EP).n EP Core (EPC)

This usage type contains the core portal capabilities that were available in the formerusage type EP. This new usage type provides more flexibility when implementing aportal where the full enterprise portal capabilities, such as knowledge managementand collaboration, are not needed. It contains the portal, GP, and UWL.

n Enterprise Portal (EP)

08/31/2007 PUBLIC 13/208


Area Description

This usage type includes Knowledge management, Collaboration, CAF-Core, VisualComposer, Web Dynpro extension, and .NET PDK.

For more information about EPC and about how to use it in IT scenarios, see the MasterGuide and SAP Note 982502.

SAP SolutionManager Key

You require a key to install your SAP system. You generate this key with your SAP SolutionManager [page 61].

High Availability You have the following options to install a high-availability system with MSCS:n You install one SAP system in oneMSCS cluster.n You install one SAP system in twoMSCS clusters.In both cases the following restrictions apply:n You must install the (A)SCS instance on two MSCS nodes in one MSCS cluster.n If your database supports the installation on several MSCS nodes, you can install the

database instance on more than two MSCS nodes in one MSCS cluster.

Operating Systems

Area Description

Support of OperatingSystems

See the Product Availability Matrix (PAM) on SAP Service Marketplace athttp://service.sap.com/pam

Documentation

Area Description

SAP Notes You can now access SAP Notes directly in SAP Service Marketplace from yourPDF. Place the cursor on the SAP Note “<number>” and double-click. Aseparate browser windows opens and the SAP Note is displayed.

Web Dispatcher Installation The installation of a Web Dispatcher is covered in a dedicated installationguide, available at http://service.sap.com/installnw70 Installation -Standalone Engines & Clients Installation Guide - Web Dispatcher on <platform>

Standalone GatewayInstallation

The installation of a standalone gateway is now covered in a dedicatedinstallation guide, available at http://service.sap.com/installnw70

Installation - Standalone Engines & Clients Installation Guide - Gateway on <platform>

Application Sharing ServerInstallation

The installation of Application Sharing Server is part of the SAP NetWeaverJava installation guide, available at http://service.sap.com/installnw70

Installation - SAP NetWeaver 7.0 Installation Documentation - SAP NetWeaver 7.0SR2 <Database> <Operating System> Java

Links in PDF files You can use the new links in the PDF files of the guides as follows:n Click on the section headings such as New Features to jump back to the

table of contents at the beginning of the guide.n Click on an internet link such as http://service.sap.com to jump to

the corresponding internet page.

14/208 PUBLIC 08/31/2007


http://service.sap.com/pam


http://service.sap.com/installnw70






http://service.sap.com

1 Introduction1.2 SAP Notes for the Installation

1.2 SAP Notes for the Installation

Youmust read the following SAP Notes before you start the installation. These SAP Notes contain themost recent information on the installation, as well as corrections to the installation documentation.Make sure that you have the up-to-date version of each SAP Note which you can find in the SAPService Marketplace at http://service.sap.com/notes.

Note

You can directly access the SAP Notes that are related to the SAP NetWeaver installation athttp://service.sap.com/sapnotesnw70.

SAP Notes for the Installation

SAP Note Number Title Description

967123 SAP NetWeaver 7.0/Business Suite 2005SR2: Windows

Windows-specific information aboutthe SAP system installation andcorrections to this documentation.

852008 Release Restrictions for SAPNetWeaver 7.0

Customer information on restrictionsconcerning the production use ofcertain functions.

737368 Hardware requirements of JavaDevelopment

Information on the hardwarerequirements for usage typeDevelopment Infrastructure (DI),which depends on the size of yourdevelopment team.

966960 SAP NetWeaver 7.0/Business Suite 2005SR2: SQL Server

MS SQL Server-specific informationabout the SAP system installation andcorrections to this documentation.

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

937693 SAP Mobile Infrastructure 7.0 -Release Note

This note contains additionalinformation about SAP MobileInfrastructure installation 7.0 for allsupport package stacks.

1.3 Information Available on SAP Service Marketplace

More information is available as follows on SAP Service Marketplace.

08/31/2007 PUBLIC 15/208

http://service.sap.com/notes



http://service.sap.com/sapnotesnw70









1 Introduction1.3 Information Available on SAP Service Marketplace

Documentation

Description Internet Address Title

Master Guide for SAPNetWeaver 7.0

http://service.sap.com/installnw70 Master Guide ‒ SAP NetWeaver 7.0

Technical InfrastructureGuide for SAP NetWeaver7.0

http://service.sap.com/installnw70 Technical Infrastructure Guide ‒ SAPNetWeaver 7.0

List of media forinstallation or upgradefor SAP NetWeaver 7.0

http://service.sap.com/installnw70 Media List ‒ SAP NetWeaver 7.0

Installation of SAPSolution Manager


/solutionmanager Installation GuidesRelease <3.2 or 4.0>

Installation Guide ‒ SAP SolutionManager <release> on <OS>:<Database>

Configuration of SAPSolution Manager


/solutionmanager Installation GuidesRelease <3.2 or 4.0>

Configuration Guide ‒ SAP SolutionManager <release> <current stack>

Patching of SAPNetWeaver 7.0 scenarios

http://service.sap.com/maintenancenw70 Support Package Stack Guide ‒ SAPNetWeaver 7.0 Support Package Stack<current stack>

Upgrade to SAPNetWeaver 7.0

http://service.sap.com/upgradenw70 Component Upgrade Guide ‒ SAPNetWeaver 7.0 Application ServerABAP

Installation of SAPNetWeaver DeveloperWorkplace

http://service.sap.com/installnw70 Installation Guide ‒ SAP NetWeaverDeveloper Workplace

Installation of SAPNetWeaver DeveloperStudio

http://service.sap.com/installnw70 Installation Guide ‒ SAP NetWeaverDeveloper Studio

Installation of the SystemLandscapeDirectory (SLD)


ConfigurationPost-Installation Guide ‒ SystemLandscape Directory of SAPNetWeaver 7.0

Installationof a standalonegateway


Installation - Standalone Engines & ClientsInstallation Guide ‒ Gateway on<platform> for SAP NetWeaver 7.0SR2

Installation of WebDispatcher


Installation - Standalone Engines & ClientsInstallation Guide ‒ Web Dispatcheron <platform> for SAP NetWeaver7.0 SR2

Front End installation http://service.sap.com/installnw70 Front End Installation Guide (this guideis also available on the PresentationDVD)

16/208 PUBLIC 08/31/2007










http://service.sap.com/solutionmanager








http://service.sap.com/maintenancenw70



http://service.sap.com/upgradenw70





















1 Introduction1.4 Naming Conventions

Description Internet Address Title

Homogeneous andheterogeneous systemcopy for SAP systems basedon NetWeaver 7.0

http://service.sap.com/installnw70 Homogeneous and Heterogeneous SystemCopy for SAP Systems based on SAPNetWeaver 7.0

SAP NetWeaver ProblemAnalysis Guide

http://help.sap.com/nw70 SAP NetWeaverLibrary SAP NetWeaver by Key Capability SolutionLife Cycle Management by Key Capability SAPNetWeaver Problem Analysis Guide (PAG)

SAP NetWeaver Problem AnalysisGuide (PAG)

General Quick Links

Description Internet Address

SAP Help Portal http://help.sap.com

SAP NetWeaver Library in SAPHelp Portal

http://help.sap.com/nw70

SAP Notes http://service.sap.com/notes

SAP Notes for SAP NetWeaver 7.0installation


Released platforms and operatingsystems

http://service.sap.com/platforms

Unicode SAP systems and theiravailability

http://service.sap.com/unicode

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

High availability http://service.sap.com/ha

Security http://service.sap.com/security

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

Information on SAP SupportPackage Stacks

http://service.sap.com/sp-stacks

System Landscape Directory http://service.sap.com/sld

SAP Solution Manager http://service.sap.com/solutionmanager

1.4 Naming Conventions

In this documentation, the following naming conventions apply:

08/31/2007 PUBLIC 17/208







http://help.sap.com











http://service.sap.com/sizing


http://service.sap.com/ha

http://service.sap.com/ha

http://service.sap.com/security


http://www.microsoft.com/security

http://www.microsoft.com/security



http://service.sap.com/sld




1 Introduction1.4 Naming Conventions

Terminology

n SAP system refers to SAP NetWeaver 7.0 SR2.n ABAP+Java system refers to SAP NetWeaver 7.0 SR2 ABAP+Java.n Java Add-In refers to the Java Add-In for an existing SAP NetWeaver 7.0 SR2 ABAP system.

Variables

Variables Description

<SAPSID> SAP system ID in uppercase letters

<sapsid> SAP system ID in lowercase letters

<DBSID> Database ID in uppercase letters

<dbsid> Database ID in lowercase letters

<host_name> Name of the corresponding host

<INSTDIR> Installation directory for the SAP system

<DVD_DIR> Directory on which a DVD is mounted

<OS> Operating system name within a path

<SCHEMA_ID> Database schema ID

The following example shows how the variables are used:

Example

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

18/208 PUBLIC 08/31/2007

2 Planning

2 Planning

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

Only valid for: HA (MSCS)

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

You have to complete the following planning activities:

1. You plan your SAP system landscape according to the Master Guide and the TechnicalInfrastructure Guide.

2. You choose your basic system variants [page 20].3. You plan how to distribute the instances to hosts [page 22].4. You plan how to distribute instances to hosts for a Java Add-In installation [page 22].5. You decide on your production client [page 24].6. You plan your system configuration [page 25].7. You identify basic SAP system parameters [page 33].8. You decide whether you want to use Unicode and multi-language support [page 39].9. If you want to use Adobe Document Services (ADS), you check what you have to do in case your platform is

not supported for ADS [page 41].

10.


You decide if you want to install Application Sharing Server as a standalone unit on a dedicated host [page 41].End of: Enterprise Portal (EP)

The following planning activities are optional:

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

Caution

This step does not apply to the installation of a Java Add-In to an existing ABAP system.

08/31/2007 PUBLIC 19/208

2 Planning2.1 Basic System Variants

2.1 Basic System Variants

This chapter describes the basic system variants and shows how you can distribute SAP instanceswithin these variants.It also includes a section for the distribution of instances in a Java Add-In installation.Mandatory instances of an ABAP+Java system are the central instance, the central services instance,and the database instance. You can then operate both the ABAP application server (AS-ABAP) andthe Java application server (AS-Java) on the SAP system.

Note

Optionally, you can install one or more dialog instances on a separate dialog instance host.

The following graphics show examples for the distribution of the SAP instances in a central system,where the mandatory instances are installed on one host, and a distributed system, where themandatory instances are installed on separate hosts.

Figure 1: ABAP+Java System

Installing a Java Add-In to an Already Existing ABAP System

This documentation also describes how to install a Java Add-In to an already existing ABAP system.You can then operate both the ABAP application server and the Java application server on the SAPsystem.

20/208 PUBLIC 08/31/2007

2 Planning2.1 Basic System Variants

Mandatory instances of a Java Add-In for ABAP system are the central instance, the central servicesinstance, and the database instance.

Note

Optionally, you can install one or more dialog instances.If your ABAP system already uses a dialog instance and you still want to use this dialog instance,you have to deinstall the existing ABAP dialog instance, before you install the new ABAP+Javadialog instance.

The following graphic shows examples for the distribution of the SAP instances in a central system,where the mandatory instances are installed on one host, and a distributed system, where themandatory instances are installed on separate hosts.

Figure 2: Java Add-In for ABAP System

More Information


For more information on how to distribute SAP instances in a high-availability SAP system, see SAPSystem Components in an MSCS Configuration [page 166].End of: HA (MSCS)

08/31/2007 PUBLIC 21/208

2 Planning2.2 How to Distribute Instances to Hosts

2.2 How to Distribute Instances to Hosts

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

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

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

l Central instance on the central instance host

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

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

22/208 PUBLIC 08/31/2007

2 Planning2.3 How to Distribute Instances to Hosts for a Java Add-In Installation

2.3 How to Distribute Instances to Hosts for a Java Add-InInstallation

The following provides information on how you can distribute the Java Add-In SAP instances for anexisting ABAP system. You use SAPinst to install the Java Add-In SAP instances as a:

n Central system on a single hostYou run SAPinst and install the Java Add-In on one host.

n Distributed system on several hostsYou perform the following steps:1. On the SAP global host, you run SAPinst and install the Java central services instance (SCS).2. On the database host, you run SAPinst and install the Java Add-In for the database instance.3. On the SAP global (central instance) host , you run SAPinst and install the Java Add-In for

the central instance.4. If required, you run SAPinst to install one or more ABAP+Java dialog instances.

Caution

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

The following figure shows how to distribute your instances on several hosts:

Figure 4: Distribution of Instances in an Java Add-In System

08/31/2007 PUBLIC 23/208

2 Planning2.4 Production Client Considerations


Distribution of Instances for a Java Add-In Installation in an MSCSConfigurationYou install the instances as follows:

1. On the MSCS node where the ABAP central services (ASCS) instance is installed, you run SAPinstand install the Java central services instance (SCS).

2. You configure the first MSCS node where you installed the SCS instance.3. On the database host, you run SAPinst and install the database instance.4. You configure the additional MSCS node.5. You install the enqueue replication server instance on the two MSCS nodes where you installed

the (A)SCS instance.6. On the ABAP central instance host, you run SAPinst and install the Java central instance.7. You run SAPinst and install at least one ABAP+Java dialog instance on the dialog instance host.

Note

You can also install the dialog instance on a local disk on the MSCS node.

Caution


For more information, see High Availability with Microsoft Cluster Service [page 165]End of: HA (MSCS)

2.4 Production Client Considerations

A client is a self-contained unit in an SAP systemwith separate master records and its own set of tables.SAPinst creates three ABAP clients during the installation, client 000, client 001, and client 066.As of SAP NetWeaver 7.0 and Business Suite 2005, you can install an ABAP+Java system in oneinstallation run. This means that AS Java is configured by default against ABAP client 001.You can choose one of the following methods to set up your new production client:

n You install the ABAP and the Java part of your system separately.n You install an ABAP+Java system and reconnect the Java part.n You install an ABAP+Java system and do not reconnect the Java part.

The following procedure describes the above methods.

24/208 PUBLIC 08/31/2007

2 Planning2.5 System Configuration

Installing the ABAP and the Java Part of your System Separately

1. You install the ABAP system as described in the documentation Installation Guide ‒ <your SAP systemapplication> ABAP on <your OS>: <database>.

2. You perform the client copy [page 108].3. You install the Java Add-In for ABAP as described in this installation guide.

You can specify the production client to which you want to connect the Java Add-In duringthe input phase of the installation.

Installing an ABAP+Java System and Reconnecting the Java PartIf you need the Java users in your ABAP production client, you have to manually configure theconnection of the Java part to the ABAP part.For more information about Java users, see the table User Management Engine (UME) in Basic SAP SystemParameters [page 33].

1. You install the ABAP+Java system as described in this documentation.2. You perform the client copy [page 108].3. You reconnect the Java part to the production client as described in SAP Note 937323.

Installing an ABAP+Java System Without Reconnecting the Java PartIf you do not need the Java users in your ABAP production client, you do not have to manuallyconfigure the connection of the Java part to the ABAP part.For more information about Java users, see the table User Management Engine (UME) in Basic SAP SystemParameters [page 33].

1. You install the ABAP+Java system as described in this documentation.2. You perform the client copy [page 108].

2.5 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 20].

n You and your hardware partner work out a high-performance configuration based on sizinginformation that reflects the system workload, such as:l The set of applications to be deployedl How intensively the applications are to be usedl The number of users

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

08/31/2007 PUBLIC 25/208



l Local installationYou need to be Local Administrator of the machine involved. In a local installation, allWindows account and user information is stored locally on one host and is not visible to anyother hosts in the system.If the SAP system is to run on a singlemachine, you can perform a local installation.

Caution

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

uYou use the same password for the <sapsid>adm or the SAPService<SAPSID> user on allhosts.The password for the <sapsid>adm and SAPService<SAPSID> user can differ.

uYou use the same master password on all hosts.

uAll hosts belong to the same Windows work group.

l Domain installationYou need to be Domain Administrator of the domain involved, and all machines in the systemmust belong to the same domain. In a domain installation, the user information is storedcentrally on the domain controller and is accessible to all hosts in the system.If the system is to be distributed acrossmore than onemachine, SAP strongly recommendsyou 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 theinstallation as a domain user who is a member of the local administrators group. However, thedomain administrator has to prepare the system appropriately for you.For more information, see Performing a Domain Installation without being a Domain Administrator [page 57].

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

2.5.1 Distribution of Components to Disks

When you install the SAP system with an MS SQL Server database, the main directories requiredfor the system are automatically created. However, during the installation procedure you have to

26/208 PUBLIC 08/31/2007


explicitly specify where these directories are to be located, that is, on which drives or disks they mustreside. The assignment of the directories to drives and corresponding disks fundamentally affects thesecurity and performance of the system and must therefore be carefully considered.The following table gives you an overview of the main SAP system components, directories, and theirpurpose. A good distribution of these to disks ensures that:

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

n Performance is good

System Components and their Directories

Directory Type Directory Structure Description

SAP System\usr\sap

\usr\sap\trans

SAP kernel and related filesSAP transport directory

Database Management System(DBMS)

\Program Files\Microsoft SQL

Server

SQL Server program files includingthe master, msdb and tempdb

database files.

SAP Database \<SAPSID>DATA1

\<SAPSID>DATA2

\<SAPSID>DATA3

\<SAPSID>DATA4

...

\<SAPSID>DATA<N>

Database data files <1-N>

SAP Database Transaction Log \<SAPSID>log<N> Database transaction log files

Database Components

When you install an SAP system with MS SQL Sever, the central components of the database are theSQL Server program files, tempdb files, SAP database data files and SAP database transactionlog 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 forthe SAP system.

n SAP Database Data FilesThe data files are created by default in the directories \<SAPSID>DATA<N>. The first data file is called<SAPSID>DATA1.mdf and subsequent files<SAPSID>DATA<N>.ndf, where <N> denotes the numberof the file. You can change the default value of these directories.For security reasons, locate the data files on a separate disk system. They should not be included inthe same disk system as the log files or other SQL Server program and database files. To ensure dataredundancy, SAP recommends the use of RAID 5.

n Transaction Log File

08/31/2007 PUBLIC 27/208


The transaction log for the database is created by default in the directory\<SAPSID>LOG1. The logfile is called <SAPSID>LOG1.ldf. You can change the default directory of the transaction logdirectory.The transaction log file records all the changes made to the database and, if required, enablesmodifications to be redone or undone. It plays a crucial role when the database has to be restoreddue to database damage or media failure. For this reason it should be stored very securely. SAPrecommends the use of RAID 1 which implements hardware-based mirroring.

n Program FilesThe files other than the SAP database data and transaction log files are created in the subdirectoriesof \Program Files\Microsoft SQL Server. These include the SQL Server program files and themaster, msdb and tempdb database files. Locate these on a separate, third, disk system and noton the same disks as the transaction log files or SAP database data files. SAP recommends theuse of RAID 1.For performance reasons, it is advisable to place the tempdb files on a fast disk system. This isparticularly recommended because the tempdb is frequently accessed during SQL Server operationand 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 thedatabase, it is transferred to a new \TEMPDB directory and extended to a size of 300 MB.

Distribution of Main Directories to RAID Array

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

Note

The SAP kernel files and the transport directory can be assigned to any of the arrays depicted, butmust both be located on the same array. The transport directory does not necessarily have to resideon the central instance host.

28/208 PUBLIC 08/31/2007


Figure 5: Distribution of Components to RAID Arrays

Distribution of Directories to Arrays

Array 1 \Program files\Microsoft SQL Server

\TEMPDB

Array 2 \<SAPSID>DATA1

\<SAPSID>DATA2

\<SAPSID>DATA3

\<SAPSID>DATA4

...

\<SAPSID>DATA<N>

Array 3 \<SAPSID>log1

Optimizing Performance

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

2.5.2 SAP Directories

This section describes the SAP directories that SAPinst creates during the installation.The base directories required for the SAP system are:

08/31/2007 PUBLIC 29/208


n \usr\sap

This directory is created on the:l Global host and shared with the name sapmnt

On global hosts, the \usr\sap directory contains general SAP software, global and local(instance-specific) data.For this, the following directories are created in usr\sap\<SAPSID>\SYS:

uglobal (contains globally shared data)

uprofile (contains the profiles of all instances)

uexe (contains executable kernel programs)All instances of an SAP system access this directory on the global host using the UniversalNaming Convention (UNC) path.

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

Note

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

n \usr\sap\trans

This directory contains SAP software for the transport of objects between SAP systems and iscreated on the transport host, which is normally the SAPGLOBALHOST.If you do not want to have it created on the global host you can specify another host during theinstallation. For more information, see Preparing the SAP System Transport Host [page 59].

Directory Structure

The global host has the SAP\<SAPSID>\SYS directory structure. The global data (binaries) is stored inthe global directories on the global host and physically exists only once for each SAP system. Otherapplication servers access the global data using the UNC path \\<SAPGLOBALHOST>\sapmnt. The SAPprograms access their instance-specific data with the UNC path \\<SAPLOCALHOST>\saploc. If theUNC path points to a local directory, the local path (and not the UNC path) is used to access thedirectory.In a distributed system, the parameters SAPGLOBALHOST and SAPLOCALHOST have the same values onthe global host.Every time an instance starts, the SAP copy program sapcpe compares the binaries in the<platform>-directory on the global host and the binaries in the exe-directory on the applicationserver. If the binaries in the exe directory are elder than those in the <platform>-directory, sapcpereplaces them with the newer version of the global host.

30/208 PUBLIC 08/31/2007


The following figures show how the physical directory \usr\sap is shared on the global host in acentral and in a distributed system. In both cases, the UNC paths are used as follows:

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

Figure 6: Directory Structure on the Global Host in a Central ABAP+Java System

08/31/2007 PUBLIC 31/208


Figure 7: Directory Structuren in a Distributed ABAP+Java System

32/208 PUBLIC 08/31/2007

2 Planning2.6 Basic SAP System Parameters


Figure 8: Directory Structure in a High-Availability ABAP+Java System

End of: HA (MSCS)

2.6 Basic SAP System Parameters

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

Note

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

08/31/2007 PUBLIC 33/208


SAP System ID and Database ID

Parameters Description Enter Your Values

SAP System ID<SAPSID>

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

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

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

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

INT KEY LOG MON NIX NOT OFF OMS RAW ROW SAP SET

SGA SHG SID SQL SYS TMP UID USR VAR

...

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

...

SAP System Instances, Hosts and Ports


Instance Number Instance Number:Technical identifier for internal processes, consisting of atwo-digit number from 00 to 97.The instance number must be unique on a host. That is, ifmore than one SAP instance is running on the same host, theseinstances must be assigned different numbers.To find out this number, look under the SAP directory<Drive>:\usr\sap\<SAPSID>\DVEBMGS<nn> on the host of thecentral instance.The value <nn> is the number assigned to the central instance.

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

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

...

34/208 PUBLIC 08/31/2007



Name of InstanceHost

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

...

Messaging ServicePort Caution

Make sure that all messaging service port numbers on the samehost are unique.

Port number of the SAP Messaging Service:If you do not specify a value, the default port number is used.The messaging service port number must be unique for the SAPsystem on all hosts.ABAP Messaging Service PortThere is an external messaging service port using the parameterrdisp/msserv and an internal messaging service port using theparameter rdisp/msserv_internal.The ABAP messaging service uses both the internal and theexternal messaging service ports. Both messaging service portsare configured in the default profile.The external messaging service port uses the parameterrdisp/msserv with default value 36<nn>, where <nn> is theinstance number of the ABAP messaging service instance.The internal messaging service port uses the parameterrdisp/msserv_internal with default value 39<nn>, where <nn>is the instance number of the ABAP messaging service instance.Java Messaging Service PortThe Java messaging service only uses the internalmessagingservice port. The Java messaging service is configured in the SCSinstance profile.The parameter rdisp/msserv is set to 0, so that the external portis not open.The internal messaging service port uses the parameterrdisp/msserv_internal with default value 39<nn>, where <nn>is the instance number of the SCS messaging service instance.For more information about the parameters used for internal andexternal messaging service ports, see SAP Note 821875.

...

08/31/2007 PUBLIC 35/208




Master Password


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

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

...

Operating System User


Operating SystemUsers

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

...

User Management Engine (UME)

Parameter Description Enter Your Values

ABAP Client The production client of the ABAP system.

CautionThis is only relevant for a Java Add-In installation.

...

DDIC Password The existing password of the DDIC user.

CautionThis is only relevant for a Java Add-In installation.

...

Java AdministratorUser

This user is created by SAPinst in the ABAP system.After the installation, this user is available both in the ABAPand in the Java systemSAPinst sets the user name J2EE_ADMIN and the master passwordby default.If required, you can choose another user name and passwordaccording to your requirements.

...

36/208 PUBLIC 08/31/2007



Java Guest User This user is for employees who do not belong to a company orwho have registered as company users and are pending approval.Guest users belong to the default group Authenticated Users.This user is created by SAPinst in the ABAP system.After the installation, it is available both in the ABAP and inthe Java systemSAPinst sets the user name J2EE_GUEST and the master passwordby default.If required, you can choose another user name and passwordaccording to your requirements.

...

Communication User This user is created by SAPinst in the ABAP system.After the installation, it is available both in the ABAP and inthe Java systemThis user is used for the communication between the ABAPsystem and the Java system.SAPinst sets the user name SAPJSF and the master password bydefault.If required, you can choose another user name and passwordaccording to your requirements.

...

Internet Communication Manager (ICM) User Management


Password of webadm The administration user webadm is created to use the webadministration interface for Internet Communication Manager(ICM) and Web Dispatcher.SAPinst sets the master password by default. If required, youcan choose another password.

...

Solution Manager Key


SAP Solution Managerkey

To install your SAP system, you need to generate a SAP SolutionManager key [page 61], which the installation requires to continue.For more information, see SAP Note 805390.

...

08/31/2007 PUBLIC 37/208



Parameters Relevant for the Connectivity to System Landscape Directory (SLD)


SLD Destination The System Landscape Directory (SLD) isdesigned for registering the systems (alongwith the installed software) of your wholesystem landscape.The usual case is to configure one SLD foryour complete system landscape.For more information, see Configuring SystemLandscape Directory [page 148].

...

SLD HTTP Host The host name of the System LandscapeDirectory (SLD)

...

SLD HTTP Port The HTTP port of the Java system wherethe SLD is installed. The following namingconvention applies: 5<instance_number>00.

ExampleIf the instance number of your Java system is01, the SLD HTTP Port is 50100.

...

SLD Data Supplier Userand password

n If you want to install a local SLD, SAPinstcreates this user during the installation.

n If you want to connect your system to anexisting central SLD, you have to enterthe existing SLD Data Supplier User andpassword of the central SLD during theinstallation.

RecommendationWe recommend that you name this userSLDDSUSER

...

SLD ABAP API User andpassword

n If you want to install a local SLD, SAPinstcreates this user during the installation.

n If you want to connect your system to anexisting central SLD, you have to enterthe existing SLD Data Supplier User andpassword of the central SLD during theinstallation.

RecommendationWe recommend that you name this userSLDAPIUSER

...

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

SLD Gateway Host The host on which the gateway instance ofthe SLD is running

...

38/208 PUBLIC 08/31/2007

2 Planning2.7 Multi-Language and Unicode Support


SLD Gateway InstanceNumber

The instance number of the gateway instanceof the SLD

...

SAP System Client The client in which the ABAP RFC user exists ...

Parameters for SAPDATA Drives


Installation drive Base directory for the SAPsystem. Do not add <SAPSID> assubdirectory because the systemadds this directory automatically.

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

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

...

Parameters Relevant for the Database


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


In an MSCS environment, enterthe virtual host name.End of: HA (MSCS)

...

2.7 Multi-Language and Unicode Support

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

08/31/2007 PUBLIC 39/208

2 Planning2.7 Multi-Language and Unicode Support

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

l Unicode (and the parallel ISO 10646 standard) defines the character set necessary for efficientlyprocessing text in any language and for maintaining text data integrity. In addition to globalcharacter coverage, the Unicode standard is unique among character set standards, because italso defines data and algorithms for efficient and consistent text processing. This enableshigh-level processing and ensures that all compliant software produces the same results.The widespread adoption of Unicode over the last decade has made text data truly portableand formed a cornerstone of the Internet.

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

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

non-Unicode code page

uSAP systems that deploy Java applications (for example Java applications, WebDynproapplications)

uSAP ABAP systems that communicate with Java components (for example via the SAPJava Connector)

u


SAP systems with usage type Process Integration (PI)End of: Process Integration (PI)

Note

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

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

IntegrationThe default setup of the system is Unicode.

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

settings.

For more information on installing languages, see Performing Initial ABAP Configuration [page 105]Installing Languages .

40/208 PUBLIC 08/31/2007



2 Planning2.8 Running Adobe Document Services on Non-Supported Platforms

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

2.8 Running Adobe Document Services on Non-SupportedPlatforms

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

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


2.9 Application Sharing Server as an Optional Standalone Unit

Application Sharing Server for real-time collaboration provides data streaming services that enableapplication sharing capabilities provided by SAP NetWeaver collaboration. The server handles theflow of data between portal users collaborating through the real-time application sharing feature.Application Sharing Server lets users share their Windows desktop or individual applications withother portal users in real time. Remote users can interact directly with the shared desktop orapplication as if they were sitting at the host machine.The server is installed automatically with usage type Enterprise Portal (EP) on the portal host. Ina cluster environment, the load generated by the Application Sharing Server is replicated to allinstances of the cluster. This generates load on all dialog instance hosts.

Note

You can only use Application Sharing Server with SAP NetWeaver systems with usage type EP.

Planning

For test or demo purposes, you can run the Application Sharing Server on the portal machine.

08/31/2007 PUBLIC 41/208




2 Planning2.9 Application Sharing Server as an Optional Standalone Unit

Recommendation

For production use, we recommend that you install the server as an optional standalone unit on adedicated host. To do this, you perform a separate installation as described in this documentation.By removing Application Sharing Server traffic from the portal host, you reduce the networking andJ2EE Engine demands on that machine, which improves the overall performance of the portal.

When you install usage type EP, the Application Sharing Server is installed automatically. If you donot intend to use the Application Sharing Server, you can disable it. For more information, seePost-Installation Tasks for Application Sharing Server [page 124].You can install Application Sharing Server on a dedicated host before or after installing the usage typeEP. However, you can only complete the post-installation steps after you have installed usage type EP.

Preparation

Prepare the Application Sharing Server installation host for an AS Java central system installation:

1. Check hardware and software requirements [page 43].2. Check the Windows file system [page 54].3. Install the Java Development Kit [page 61].4. Prepare the installation DVDs [page 62].

Installation

1. Install the MS SQL Server database software [page 67].2. Run SAPinst to install Application Sharing Server as an optional standalone unit [page 95].

Post-Installation

Perform the post-installation steps for an AS Java central system installation on the ApplicationSharing Server installation host:

1. Start and stop the Application Sharing Server system [page 98].2. Check the SAP Java documentation [page 130].3. Apply the latest kernel and support packages [page 107].4. Perform post-installation steps for Adobe Document Services [page 120].5. Perform post-installation steps for Application Sharing Server [page 124].6. Ensure the security of Java standalone users stored in the database [page 124].

End of: Enterprise Portal (EP)

42/208 PUBLIC 08/31/2007

3 Preparation

3 Preparation

You have to complete the following preparations:

1. You check the hardware and software requirements [page 43].2. You check the Windows file system [page 54].3. You check the Windows domain structure [page 54].4. If required, you reduce the size of the file cache [page 55].5. If required, you grant user rights for the installation [page 56].6. If required, you perform a domain installation without being a domain administrator [page 57].7. If required, you prepare the SAP system transport host [page 59].8. You install the SAP front-end software [page 60].9. You generate the SAP Solution Manager Key [page 61].10. You install the Java Development Kit [page 61].11. You prepare the installation DVDs [page 62].12. If required, you download the installation DVDs from SAP Service Marketplace [page 64].

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

3.1 Hardware and Software Requirements

You check the hardware and software requirements for your operating system (OS) and the SAPinstances using the Prerequisite Checker tool. The Prerequisite Checker provides information aboutthe requirements that you need to meet before you start the installation. For example, it checks therequirements for the different installation services.

Note

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

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

You can run the Prerequisite Checker as follows:

n Standalone (optional):To check the hardware and software requirements of the host on which you want to later installan SAP system, you can run the Prerequisite Checker standalone [page 44].

08/31/2007 PUBLIC 43/208


3 Preparation3.1 Hardware and Software Requirements

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

We also recommend that you consult the requirements checklists tables, which provide values for theinstallation of development systems or quality assurance systems. Depending on the amount ofdata involved, the requirements might change. In addition, consider the following information:

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

http://service.sap.com/sizing. You enter information about your planned system and thetool calculates the requirements.For more information, see Planning your System Landscape in theMaster Guide ‒ SAP NetWeaver 7.0,which is available on SAP Service Marketplace [page 15].

l You contact your hardware vendor, who can analyze the load and calculate suitable hardwaresizing.

n For supported operating system releases, see the Product Availability Matrix on SAP ServiceMarketplace at http://service.sap.com/pam.

n Contact your OS vendor for the latest OS patches.n Make sure that the host name meets the requirements listed in SAP Note 611361.

Process Flow

1. If required, you run the Prerequisite Checker standalone [page 44] to check the hardware and softwarerequirements.

Caution

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

2. In addition, we recommend that you check the hardware and software requirements checklistsfor the following system variants:n Central System [page 45]n Distributed System [page 47]

3.1.1 Running the Prerequisite Checker in Standalone Mode(Optional)

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

44/208 PUBLIC 08/31/2007









Recommendation

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

Note

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

Prerequisites

n You have installed the correct Java Development Kit (JDK) [page 61].n You have prepared the installation master DVD on the required installation host [page 62].

Procedure

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

Tasks Prerequisites Check .3. Follow the instructions in the SAPinst dialogs and enter the required parameters.

Note

For more information about each parameter, position the cursor on the parameter field andchoose F1 in SAPinst.

When you have finished, the Parameter Summary screen appears summarizing all parameters you haveentered. If you want to make a change, select the relevant parameters and choose Revise.

4. To start the Prerequisite Checker, choose Start.

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

3.1.2 Requirements Checklist for a Central System

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

08/31/2007 PUBLIC 45/208


Requirement Type Requirement

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

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

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

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

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

20 GBl Up to 2 GB for each usage type or software unit you want to install.l 4.3 GB of temporary disk space for every required installation DVD

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

1. Choose Start Programs Administrative Tools Computer ManagementDisk Management.

2. Select the local drive.

3. Choose Properties.n Minimum RAM:

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

n Paging File Size: 1 times RAM plus 8 GBTo check paging file size:

1. Right-clickMy Computer and choose Properties.

2. Choose Advanced Performance Settings .

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

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

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

For more information on the collation for MS SQL Server 2000, seeSAP Note 600027.

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

For more information, see SAP Note 62988.u Unicode collation SQL_Latin1_General_CP850_BIN2

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

NoteWe strongly recommend you to use the 64-bit version of the Windows

46/208 PUBLIC 08/31/2007







Server 2003 editions.

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

To check your Windows version:

1. Choose Start All Programs Accessories Command Prompt .

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

3.1.3 Requirements Checklist for a Distributed System

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

n


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

n Central services instance [page 49]n Database instance [page 50]n Central instance [page 51]n Dialog instance [page 53]

Note

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

Only valid for: HA (MSCS);HA (z/OS)

3.1.3.1 Requirements Checklist for the ABAP Central ServicesInstance

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

08/31/2007 PUBLIC 47/208



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

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

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

To check disk space:

1. Choose Start All Programs Administrative Tools Computer ManagementDisk Management.

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

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

1 times RAM plus 8 GBTo check paging file size:




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

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

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

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


To check the Windows version:

1. Choose Start All Programs Accessories Command Prompt.

2. Enter the command winver.

48/208 PUBLIC 08/31/2007





n A suitable Windows Resource Kit is strongly recommended.

End of: HA (MSCS);HA (z/OS)

3.1.3.2 Requirements Checklist for the Central ServicesInstance

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


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

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

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


1. Choose Start All Programs Administrative Tools Computer ManagementDisk Management.

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

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

1 times RAM plus 8 GBTo check paging file size:




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


NoteWe strongly recommend you to use the 64-bit version of the Windows

08/31/2007 PUBLIC 49/208



Server 2003 editions.




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

3.1.3.3 Requirements Checklist for the Database Instance

The database instance host must meet the following requirements:


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

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

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

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

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

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

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

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



50/208 PUBLIC 08/31/2007




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

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

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

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

For more information, see SAP Note 62988.u Unicode collation SQL_Latin1_General_CP850_BIN2


Notel If you install SQL Server 2005, you must install at least SP 1 for Windows Server

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

2003 editions.




3.1.3.4 Requirements Checklist for the Central Instance

The central instance host must meet the following requirements:


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

08/31/2007 PUBLIC 51/208







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

5 GB (x86, x86_64)8 GB (IA64)In addition you require 4 GB (x86, x86_64), or 8 GB (IA64) peradditional platform.

l Up to 2 GB for each usage type or software unit you want to install.l 4.3 GB of temporary disk space for every required installation DVD

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

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

2. Select the local drive.

3. Choose Properties.n Minimum RAM:

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

n Paging File Size:1 times RAM plus 8 GBTo check paging file size:


2. Choose Advanced Performance Settings.



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

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

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

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


52/208 PUBLIC 08/31/2007







3.1.3.5 Requirements Checklist for the Dialog Instance

The dialog instance host must meet the following requirements:


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

2.5 GB (x86, x86_64)5 GB (IA64)

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


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

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

1 GBTo check RAM, in the Windows Explorer choose Help AboutWindows.

n Paging File Size:1 times RAM plus 8 GBTo check paging file size:





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

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

08/31/2007 PUBLIC 53/208



3 Preparation3.2 Checking the Windows File System


l Windows Server 2003 Datacenter Edition

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

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



2. Enter the command winver

n A suitable Windows Resource Kit is strongly recommended

3.2 Checking the Windows File System

You need to check that you are using the Windows file system NTFS on hosts where you want toinstall the SAP system and database. NTFS supports full Windows security and long file names.

Note

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

Procedure

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

3.3 Checking the Windows Domain Structure

Note

You do not need this step for a local installation.

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

54/208 PUBLIC 08/31/2007

3 Preparation3.4 Reducing the Size of the File Cache

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

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

Prerequisites

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

Windows documentation.

Caution

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

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

3.4 Reducing the Size of the File Cache

The Windows file cache directly competes with SAP programs for memory. Therefore, you shouldadjust the file cache as described below.

Procedure

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

Caution

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

5. To confirm your entries, choose OK.

08/31/2007 PUBLIC 55/208

3 Preparation3.5 Granting User Rights for the Installation

3.5 Granting User Rights for the Installation

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

Caution

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

If necessary, you have to ask the system administrator to grant you the necessary authorizationbefore you start the installation.

Prerequisites

n The authorization required depends on whether you intend to perform a domain or localinstallation. For more information, see System Configuration [page 25].

n A domain installation requires a domain controller to store user and account informationcentrally for the whole system.

Caution

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

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

Local Installation

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

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

Domain Installation

Note

SAP recommends to perform a domain installation.

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

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

56/208 PUBLIC 08/31/2007

3 Preparation3.6 Performing a Domain Installation Without Being a Domain Administrator

Note

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


Note

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

End of: HA (MSCS)

3.6 Performing a Domain Installation Without Being a DomainAdministrator

If you are not granted domain administrator rights, you can perform the installation as a domain userwho is a member of the Local Administrators group. In this case, the domain administrator mustprepare the system for you appropriately, as described in this section.

Note

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

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

SAP_<SAPSID>_GlobalAdmin.

PrerequisitesYou must perform this procedure as a domain administrator.

Creating the New Global Group SAP_<SAPSID>_GlobalAdmin

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

Start Control Panel Administrative Tools Active Directory Users and Computers

08/31/2007 PUBLIC 57/208

3 Preparation3.6 Performing a Domain Installation Without Being a Domain Administrator

Note

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

3. Right-click Users in Tree, and choose New Group.4. Enter the following:

Group name: SAP_<SAPSID>_GlobalAdmin

Note

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

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

6. Choose OK.

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

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

2. Enter the following:

Note

Enter the <sapsid>adm and SAPService<SAPSID> user exactly as specified in the correctuppercase and lowercase.

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

First name: None None

Initials: None None

Last name: None None

Full name: <sapsid>adm SAPService<SAPSID>

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

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

58/208 PUBLIC 08/31/2007

3 Preparation3.7 Preparing the SAP System Transport Host

Confirm password: <password>4. Select Password never expires

Note

Make sure that no other options are selected.

5. Choose Next Finish .

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

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

Note

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

4. Choose OK twice.

Adding the SAPService<SAPSID> User to the SAP_<SAPSID>_GlobalAdminGroup

1. In the Users folder, double-click the newly created user account SAPService<SAPSID> in the list onthe right.

2. Choose Member Add .3. Select the new SAP_<SAPSID>_GlobalAdmin group.4. Choose Add to add it to the list, and then OK.5. Choose OK to close SAPService<SAPSID> Properties.6. Close the Active Directory Users and Computers Management Console.

3.7 Preparing the SAP System Transport Host

The transport host has a directory structure that is used by the SAP transport system to storetransport data and metadata. The transport system stores the change information, such as ABAPprograms, data dictionary data, customization data as well as SAP support packages from SAP ServiceMarketplace in files that are located in this directory structure. If you do not intend to use thedirectory structure of the system you are going to install, you need to prepare it on the transport host.

n If the directory structure already exists, you must set up its security to allow the new systemto write into it.

n If it does not yet exist, you must create the core directory structure and a share to export it forother computers as well as setting the security on it.

08/31/2007 PUBLIC 59/208

3 Preparation3.8 Installing the SAP Front-End Software

The global transport directory \usr\sap\trans is used by the Change and Transport System (CTS).The CTS helps you to organize development projects in the ABAP Workbench and in Customizing,and then transport the changes between the SAP systems in your system landscape. For moreinformation, see:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution

Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics Change andTransport System

ProcedureIf your transport host is not the central instance host, you have to create the transport directoryas follows:

1. On the transport host, create the directory \usr\sap\trans.By default this is the directory \usr\sap\trans.

2. Grant Everyone the permission Full Control for the directory.

Note

These permissions are only necessary during the SAPinst installation. You must remove themafter you have finished the installation.After the installation, you only have to grant Full Control on this directory to theSAP_<SAPSID>_GlobalAdmin groups of all the systems that are part of your transportinfrastructure. SAPinst assigns the appropriate rights with the help of an additionalSAP_LocalAdmin group.For more information, see Automatic Creation of Accounts and Groups [page 159].

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

3.8 Installing the SAP Front-End Software

Caution

This section does not apply to the installation of a Java Add-In to an existing ABAP system.

For the installation, make sure that the front-end software is installed on at least one host machine inyour system environment. To simplify the administration of your SAP system, we recommend youinstall the software on the central instance host.With the SAP front-end installation software, SAPSetup, you can optimize the deployment of SAPGUI 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.

60/208 PUBLIC 08/31/2007




3 Preparation3.9 Generating the SAP Solution Manager Key

For more information on installing the front-end software, see the documentation on SAP ServiceMarketplace at http://service.sap.com/installnw70 :

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

3.9 Generating the SAP Solution Manager Key

Caution


You need to generate the Solution Manager key because SAPinst prompts for it during the inputphase of the installation. Without this key, the installation process cannot continue.You can generate all needed keys for your entire system landscape on one SAP Solution Managersystem. For more information, see SAP Note 805390.

PrerequisitesYou require SAP Solution Manager 3.2 SP 08 or higher.

Procedure

1. If SAP Solution Manager is not yet available in your system landscape, proceed as follows:a) Order SAP Solution Manager as described in SAP Note 628901.b) Install SAP Solution Manager as described in the documentation Installation Guide ‒ SAP Solution

Manager <release> on <OS> : <Database> on SAP Service Marketplace at:http://service.sap.com/solutionmanager SAP Solution Manager Installation Guides Release

<3.2 or 4.0>2. Generate the SAP Solution Manager key as described in SAP Note 811923.

ResultThe system displays the key, which you need to enter during the input phase of the installation.

3.10 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 7.0 you must install the J2EE Engine with strong encryption.The JDK includes the Java Runtime Environment (JRE), which is required both for SAPinst andthe SAPinst GUI.The J2EE Engine requires a Java Development Kit (Java™ 2 SDK, Standard Edition = JDK) on everyhost where the J2EE Engine is to be installed. You need this for the system variants [page 20] with Java.

08/31/2007 PUBLIC 61/208










3 Preparation3.11 Preparing the Installation DVDs

Note

If required, you can perform a remote installation using a standalone SAPinst GUI on a separateWindows or UNIX host. This lets you perform the installation on a remote host, controlling it withthe SAPinst GUI from a local host.If you want to perform a remote installation, see Performing a Remote Installation with SAPinst [page 92]. Inthis 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 http://service.sap.com/pam.b) On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 7.0 .c) Choose tab strip JSE Platforms.For additional information on the recommended JDK version and about how to obtain it, seeSAP Note 709140.

2. Make sure a valid JDK version is installed on every host on which you want to install an SAPinstance 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.

3. As of SAP NetWeaver 7.0 strong encryption is mandatory for the J2EE Engine and for all usage typesthat are deployed on it. You need to obtain the JCE policy files beforehand so that they can beinstalled 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.11 Preparing the Installation DVDs

You use this procedure to prepare the installation DVDs. Normally you obtain the installation DVDsas part of the installation package that you receive from SAP. However, you can also download theinstallation DVDs from SAP Service Marketplace [page 64].

62/208 PUBLIC 08/31/2007





http://java.sun.com/products/jce/

3 Preparation3.11 Preparing the Installation DVDs

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 copiedDVDs do not contain any blanks.

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

Procedure

1. Identify the required DVDs for your installation as listed below and keep them separate from theremaining 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 NetWeaver 7.0 SR2 inthe appropriate Media List for SAP NetWeaver 7.0 SR2 on SAP Service Marketplace athttp://service.sap.com/installnw70 Installation .

The following table shows the required DVDs for the installation of an SAP system based on theusage type AS ABAP and AS Java:

Note

You can find the Software Component Archives (SCAs) for the installation of SAP NetWeaverusage types on the NetWeaver Java DVD.


Note

Do not use the Business Intelligence Content Add-On DVD for the installation of BI withSAPinst. You have to install the BI Content Add-On later. For more information, see Configuring BIJava Information Broadcasting [page 153].

End of: BI Java Components (BI-Java)

08/31/2007 PUBLIC 63/208




3 Preparation3.12 Downloading Installation DVDs from SAP Service Marketplace (Optional)

SAP Instance Installation Required DVDs

Central services instance, central instance,dialog instance

n Installation Master DVDn Kernel DVDn NetWeaver Java DVD

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

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

SAP Instance Installation Required DVD

Central instance, central services instance, dialoginstance

n Installation Master DVDn NetWeaver Java DVDn Kernel DVD

Database schema n Installation Master DVDn NetWeaver Java DVDn Kernel DVDn Export DVD

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

l Copy DVDs manually to local hard disks

Caution

If you perform a local installation and you have only one DVD drive on your installationhost, you must copy at least the Installation Master DVD locally on your computer

n During the installation:Use the SAPinstMedia Browser screen. You can check the entered location in the Package Locationcolumn and then copy the entire DVD to the path you entered in the Copy Package To column.

3.12 Downloading Installation DVDs from SAP ServiceMarketplace (Optional)

You normally obtain the installation DVDs as part of the installation package from SAP.However, you can also download installation DVDs from SAP Service Marketplace at:

64/208 PUBLIC 08/31/2007

3 Preparation3.12 Downloading Installation DVDs from SAP Service Marketplace (Optional)

http://service.sap.com/swdc Downloads Installations and Upgrades Entry by Application Group<your solution> <release of your solution> <your operating system> <your database> .If you download installation DVDs, note that DVDs might be split into several files. In this case, youhave to reassemble the required files after the download.

PrerequisitesTo extract the downloaded SAR files make sure that you use the latest SAPCAR version, which youcan find on SAP Service Marketplace at http://service.sap.com/swdc. You need at least SAPCAR700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longerunpack current SAR files. For more information, see SAP Note 212876.

Procedure

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

following:n Material number

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

Example

51031387_151031387_2...

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

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

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

Note

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

08/31/2007 PUBLIC 65/208

http://service.sap.com/swdc







This page is intentionally left blank.

4 Installation

4 Installation

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


Note

If you want to perform aMicrosoft Cluster Service (MSCS) installation, see High Availability withMicrosoft Cluster Service [page 165].

End of: HA (MSCS)

You have to perform the following steps:

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

4.


If required, you install the Application Sharing Server as a standalone unit [page 95].End of: Enterprise Portal (EP)

4.1 Installing the SQL Server Database Software

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

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

4.1.1 Installing the SQL Server Database Software withSQL4SAP

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

08/31/2007 PUBLIC 67/208

4 Installation4.1 Installing the SQL Server Database Software

Note

For more information about installing with SQL4SAP.VBS, see Customized Installation of SQL Server for anSAP System with SQL4SAP.VBS (SQL4SAP_docu.pdf) and the readme.txt, both of which are located inthe root directory of the SQL Server RDBMS DVD.


Caution

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

End of: HA (MSCS)

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

Note

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

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

u32-bit SQL Server 2005 Enterprise Edition on x86 systems

u64-bit SQL Server 2005 Enterprise Edition on x64 systems

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

Note

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

Procedure

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

2. For SQL Server 2005, insert the SQL Server 2005 RDBMS DVD in your DVD drive or mountthe network share locally.

3. Double-click SQL4SAP.VBS located in the root directory.

68/208 PUBLIC 08/31/2007




4. Follow the instructions and enter the required information in the installation screens.

4.1.2 Installing the SQL Server Database Software Manually

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

Note

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

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

The MS SQL Server software has to be installed on each host in the system where you intend to set upan SAP instance. Depending on the type of host involved, you either have to install the software forthe database client or server.

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

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

Procedure

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

Caution

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

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

MS SQL Server 2000 RDBMS SP4 DVD.

Note

Ignore the compatibility warning and choose Continue.

Enter the required information as specified in the table below.

08/31/2007 PUBLIC 69/208


Note

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

Input for MS SQL Server Installation on 32-Bit Systems

Window Server Input Client Input

Microsoft SQL Server 2000 EnterpriseEdition

Select SQL Server 2000 Components. Select SQL Server 2000 Components.

Install Components Microsoft SQL Server2000 Enterprise Edition

Select Install Database Server. Select Install Database Server.

Welcome Choose Next. Choose Next.

Computer Name Select Local Computer. Select Local Computer.

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

Select Create a new instance of SQLServer or install Client Tools.

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

Software License Agreement Choose Yes. Choose Yes.

CD-Key Enter the key specified in thefile SAPCDKEY.txt in the rootdirectory of the RDBMS DVD.

Enter the key specified in thefile SAPCDKEY.txt in the rootdirectory of the RDBMS DVD.

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

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

Dialog box does not appear.

Setup Type Select Custom. Dialog box does not appear.

Select Components Select all components. Select all components.

Service Accounts Select Use the same account for eachservice. Auto start SQL Server Service.Select Use the Local Systemaccount.


Authentication mode Select the authentication mode.We recommend to useWindowsauthentication mode.

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


70/208 PUBLIC 08/31/2007


Window Server Input Client Input

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


Network Libraries Leave selection unchanged andchoose Next.


Start Copying Files Choose Next. Choose Next.

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

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

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

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

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

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

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

Note

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

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

08/31/2007 PUBLIC 71/208





Procedure

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

Caution

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

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

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

Window Input

Registration Information Enter your name and the product key specified in the fileSAPCDKEY.txt in the root directory of the RDBMS DVD.

Software License Agreement Choose Yes.

Feature Selection n Server Software:Select all components.

n Client Software:Select SQL Server Management Tools.

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

Instance Name Select the instance type you want to install.

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

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

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

n Enter and confirm the password for the sa login.

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

72/208 PUBLIC 08/31/2007


Window Input

Security Enhancement:Cross Database Ownership Chaining

Leave selection unchanged and choose Next.

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

Licensing Mode Select the licensing mode and choose Next.

Ready to Install Select Install.

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

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

4.1.2.3 Installing the Corrected MS SQL Server Collation forMS SQL Server 2000

When you install the MS SQL Server 2000 database for an SAP system, in the field Collation Settings youhave 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, foruse 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. Tosolve 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, youselected 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 toSAP Notes 62988 and 608651.

08/31/2007 PUBLIC 73/208





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



Note

Besides applying the latest service and hotfix, if available, you do not have to make any changeson 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 allnew installations of a Unicode or non-Unicode SAP system with the MS SQL Server database. Newversions 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 oldcollation cannot run as two databases in the same MS SQL Server instance. If you want to installa new system on a database server with an existing system you have to apply the new collationwith INSTCOLL.EXE.

1. Download the INSTCOLL.EXE file for your platform, which is attached as zip file to SAP Note600027, 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 spacesafter --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:select serverproperty(’collation’)

Caution

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

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

4.1.2.4 Installing the SQL Server 2005 Database ServerSoftware Manually

This section describes how to install the SQL Server 2005 database server software on 32-bit or 64-bitsystems manually.

74/208 PUBLIC 08/31/2007




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 67] 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 NativeClient (SNAC) Software [page 78].

Prerequisites

n When installing SQL Server 2005, make sure that you have enough free disk space available onthe 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 Toolsl SQL Server instancel Temporary space during the installation

The required disk space depends on the type of SQL Server components already installed or tobe 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 systemyou might require more space.

n Make sure that theMicrosoft Distributed Transaction Coordinator (MSDTC) service is running beforeyou start the installation.

Procedure

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

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 inthe same directory.

Window Server Input

End User License Agreement Accept the licensing terms and conditions andchoose Next.

Installing Prerequisites Choose Install and, if required, Next.

08/31/2007 PUBLIC 75/208


Window Server Input

Welcome to the Microsoft SQL Server Installation Wizard Choose Next.

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

Noten For more information about the required

system configuration for a softwarecomponent, chooseMessages.

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

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

b) Choose Next.

Registration Information a) Enter your personal information, and theproduct key

b) Choose Next.

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

tools.

b) Choose Advanced

Feature Selection a) Expand Database Services and deselect Replication.

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

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

c) Choose Next.

Instance Name Select the instance you want to install and chooseNext.

NoteSAP recommends to install a Default instance.

76/208 PUBLIC 08/31/2007


Window Server Input

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

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

name and password.

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

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

c) Choose Next.

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

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

b) Choose Next.

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

b) From the drop-down list select Binary order based oncode point comparison, for use with the 850 (Multilingual)Character Set.

c) Choose Next.

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

Ready to Install Choose Install.

Setup ProgressNote

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

When the setup process has finished, choose Next.

Completing Microsoft SQL Server 2005 Setup Choose Finish.

08/31/2007 PUBLIC 77/208

4 Installation4.2 Preparing your System for a Java Add-In Installation

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

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

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

7. Restart SQL Server.

4.1.2.5 Installing the SQL Server 2005 Native Client SoftwareManually

This chapter describes how to install the SQL Server 2005 Native Client (SNAC) software.The SQL Server 2005 client software must be installed on all hosts without the database. It enables thecommunication between a host and the database.

Procedure

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

Note

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

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

4.2 Preparing your System for a Java Add-In Installation

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

n ABAP system based on SAP NetWeaver 7.0 SR2 .n ABAP system that has been upgraded to SAP NetWeaver 7.0 SR2.

Procedure

1. In your default profile \usr\sap\<SAPSID>\SYS\profile\default.pfl check the parameterdbs/mss/schema.n If it is set to <sapsid> (lowercase letters), no further action is required.

78/208 PUBLIC 08/31/2007

4 Installation4.3 Installing an SAP System Using SAPinst

n If it does not exist or is set to dbo, convert the schema as described in SAP Note 683447.

Note

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

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

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

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

4.3 Installing an SAP System Using SAPinst

The following sections tell you how to install the various instances of an SAP system, or a standaloneengine:

n Running SAPinst on Windows [page 79]n Installing a Java Add-In for an Existing ABAP System with SAPinst [page 87]n Using SAPinst GUI [page 89]n Interrupted Installation with SAPinst [page 90]n Performing a Remote Installation with SAPinst (Optional) [page 92]n Starting SAPinst GUI Separately (Optional) [page 92].n Entries in the Services File Created by SAPinst [page 94]

4.3.1 Running SAPinst on Windows

This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a SAPinst GUIand a GUI server, which both use Java.This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are runningon the same host. If required, you can instead perform a remote installation with SAPinst [page 92], whereSAPinst GUI is running on a separate host from SAPinst and the GUI server.

08/31/2007 PUBLIC 79/208



Note the following information about SAPinst:

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

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

Recommendation

We recommend that you keep all installation directories until the system is completely andcorrectly installed.

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

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

Caution

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

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

Exit .

Prerequisites

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

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

n If you are installing a second or subsequent SAP system into an existing database, make sure thatthe database is up and running before starting the installation. For more information, seeInstallation of Multiple Components in One Database [page 137].

80/208 PUBLIC 08/31/2007


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

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

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

Example

DEFAULT.PFL

Before:...rdisp/msserv = sapmsSID

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

rdisp/msserv_internal = <free port number>

...

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

Example

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

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

rdisp/msserv_internal = 4711

...

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

Procedure

1. Insert the SAP Installation Master DVD into your DVD drive or mount it locally.

08/31/2007 PUBLIC 81/208


2. Start SAPinst from the SAP Installation Master DVD by double-clicking sapinst.exe from thefollowing path:<DVD drive>:\IM_WINDOWS_<platform>

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

Note

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

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>

n To get a list of all available SAPinst properties, go to the directory(%TEMP%\sapinst_exe.xxxxxx.xxxx), after you have started SAPinst, and enterthe following command:sapinst.exe -p.

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

You use this service to install a SAP system with usage types or software units by choosing<SAP system> SAP Systems <Database> <System Variant> Based on <technical stack> .

You can install the following system variants:l Central Systeml Distributed System

l


High-Availability SystemEnd of: HA (MSCS)

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

82/208 PUBLIC 08/31/2007


Note

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

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

l If you want to install a dialog instance for a central or distributed system, choose theinstallation service <SAP System> Additional Software Life-Cycle Tasks Application ServerDialog Instance .

Installation Services for a Central System

Installation Service Remarks

Central System Installation Installs a complete SAP system including the followinginstances on one host:l Central services instance (SCS)l Database instancel Central instanceYou can install a central system in the following parametermodes:l Typical Mode

If you choose the “Typical” setting, automatic defaultsettings will be provided. You only have to respondto a small selection of prompts. However, you canchange any of the default settings on the parametersummary screen.

l Custom ModeIf you choose the “Custom” setting, all installationparameter will be prompted. In the end, you can stillchange any of these parameters on the parametersummary screen.

NoteYou require at least usage type AS Java or AS ABAP. Youcan choose the usage types or software units on thescreen SAP System > Software Units.

Installation Services for a Distributed System

Installation Services Remarks

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

08/31/2007 PUBLIC 83/208



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

Central Instance Mandatory step in installing a distributed SAP system onseveral hosts.Installs a central instance and enables additional usagetypes or software units.

NoteYou require at least usage type AS Java or AS ABAP. Youcan choose the usage types or software units on thescreen SAP System > Software Units.

You must have finished the database instance installation.

Installation Services for a High Availability System


Central Services Instancefor ABAP (ASCS)

Installs a central services instance for ABAP (ASCS) and prepares the SAPglobal host

Central Services Instance(SCS)

Installs a central services instance (SCS)

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

Database Instance Installs a database instance

Additional MSCS Node Configures an additional Microsoft Cluster Service (MSCS) node to runthe SAP cluster groupYou must have completed the configuration of the first MSCS node andthe database instance installation.

Enqueue ReplicationServer

Installs an enqueue replication server, which contains a replica of the locktable (replication server)

84/208 PUBLIC 08/31/2007



Central Instance Installs a central instance and enables additional usage types or softwareunits

NoteYou require at least usage type AS Java or AS ABAP. You can choose theusage types or software units on the screen SAP System > Software Units.

Dialog Instance Installs a dialog instance

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

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


Additional Preparation Tasks These preparation tasks comprises:l Active Directory Configuration

For more information, see Setting Up the Active Directory Services [page142].

l Operating System Users and GroupsAllows you to use global accounts that are configured on a separatehost.

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

l Prerequisites CheckChecks your hardware and software requirements before youstart the installation.Otherwise, SAPinst automatically checks the hardware andsoftware requirements during the installation with the PrerequisiteChecker. If any changes are necessary to the SAP system or operatingsystem settings, SAPinst automatically prompts you. For moreinformation, see Running the Prerequisites Checker in Standalone Mode [page44].

08/31/2007 PUBLIC 85/208



Application Server Choose Application Server <Database> Dialog Instance to installone or more dialog instance(s) in an already installed SAP system,if required.

NoteIf you want to use LDAP, choose the following option(s) after youhave installed an application server.

a) If not already done, configure the Active Directory by choosingAdditional Preparation Tasks Active Directory Configuration .

b) Choose Application Server LDAP Support .Formore information, see Setting Up the Active Directory Services [page 142].

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

System Copy Choose this service to perform a system copy.For more information, see the system copy guide,which is available at SAP Service Marketplace at:

http://service.sap.com/instguidesnw70 Installa-tion

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

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

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

Note

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

After you have entered all required input information, SAPinst starts the installation and displaysthe progress of the installation. If the installation was successful, the screen Finished installationsuccessfully is displayed.

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

More InformationTroubleshooting with SAPinst [page 161].

86/208 PUBLIC 08/31/2007

http://service.sap.com/instguidesnw70



4.3.2 Installing the Java Add-In for an Existing ABAP System(Optional)

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

Caution

Keep in mind that you cannot install the Java Add-In for the dialog instance(s) of the existingABAP system. Instead, you have to uninstall the old ABAP dialog instance(s) install new ABAP+Javadialog instance(s).

PrerequisitesYour ABAP system must be based on SAP NetWeaver 7.0 SR2.


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

Procedure

1. Start SAPinst [page 79].2. On theWelcome screen, choose <SAP system> Additional Software Life-Cycle Tasks Java Add-In for

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

appear for each system variant, as shown in the following tables:

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


Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) and adds usagetypes or software units based on AS Java

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

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

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

08/31/2007 PUBLIC 87/208


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


Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) and adds usagetypes or software units based on AS Java

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

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

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

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

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

Additional MSCS NodeCaution

Choose this step only if you use Microsoft Cluster Services(MSCS).

This step configures the SCS instance for the additionalMSCS node.

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

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

88/208 PUBLIC 08/31/2007



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

Dialog Instance Installs an ABAP+Java dialog instance in a high-availabilitysystem

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

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

Note

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

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

ResultAfter running these installation services, your ABAP+Java system consists of the following instances:

n Java central services instance (SCS)n ABAP+Java database instancen ABAP+Java central instance

Caution

You cannot install the Java Add-In for the dialog instance(s) of the existing ABAP system. Instead,you have to install new ABAP+Java dialog instances as follows:On theWelcome screen, choose <SAP system> Additional Software Life-Cycle Tasks Application Server<database> Dialog Instance .

4.3.3 Using SAPinst GUI

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

08/31/2007 PUBLIC 89/208


SAPinst GUI Functions

Button / Function Key / Menu Entries Description

F1 Displays detailed information about each inputparameter.

Exit Cancels the installation with the following options:n Stop

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

n ContinueContinues the installation.

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

NoteIf for some reason you need to log off during theinstallation from the host where you control theinstallation with SAPinst GUI, the installationcontinues while you are logged off. You can laterreconnect to the same SAPinst installation from thesame or another host. For more information, seeStarting SAPinst GUI Separately [page 92].

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

Stop Stops the installation without further changing theinstallation files. You can continue the installation laterfrom this point.

Continue Continues with the option you have chosen before.

4.3.4 Interrupted Installation with SAPinst

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

n An error occurred during the dialog or processing phase:SAPinst does not abort the installation in error situations. If an error occurs, the installation pausesand a dialog box appears. The dialog box contains a short description about the choices listed inthe 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 following table describes the options in the dialog box:

90/208 PUBLIC 08/31/2007


Option Definition

Retry SAPinst retries the installation from the point of failure without repeatingany of the previous steps.This is possible because SAPinst records the installation progress in thekeydb.xml file.We recommend that you view the entries in the log files, try to solve theproblem and then choose Retry.If the same or a different error occurs again, SAPinst displays the samedialog box again.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, andthe GUI server.SAPinst records the installation progress in the keydb.xml file. Therefore,you can continue the installation from the point of failure withoutrepeating any of the previous steps. See the procedure below.

Continue SAPinst continues the installation from the current point.

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

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

cd <DVD drive>:\IM_WINDOWS<platform>

sapinst.exe

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

Note

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

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

Alternative Behavior

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

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

08/31/2007 PUBLIC 91/208


4.3.5 Performing a Remote Installation with SAPinst(Optional)

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and theGUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is thehost from which you control the installation with SAPinst GUI.

Prerequisites

n The remote host meets the prerequisites before starting SAPinst as described in Running SAPinston Windows [page 79].

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

Procedure

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

cd <DVD drive>:\IM_WINDOWS_<platform>

sapinst.exe -nogui

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

<port_number> to continue with the installation

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

4.3.6 Starting SAPinst GUI Separately (Optional)

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUIseparately in the following cases:

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

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

92/208 PUBLIC 08/31/2007


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

Starting SAPinst GUI on a Windows Platform

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

cd <DVD drive>:\IM_WINDOWS<platform>

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

command:startinstgui.bat

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

enter the following command:startinstgui.bat -host <host_name>

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

Note

l If you enter the command without additional parameters, SAPinst GUI uses the localhost as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. AsSAPinst and the GUI server are running on another host, SAPinst GUI cannot connect andthe SAP Installation GUI Connection dialog appears.In this case, enter the name of the host on which SAPinst is running and choose Log on.The first dialog of the installation appears and you can perform the remote installationfrom your local host.

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

Starting SAPinst GUI on a UNIX Platform

1. Log on as user root.

Caution

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

2. Mount your installation DVD.

08/31/2007 PUBLIC 93/208

4 Installation4.4 Installing Application Sharing Server as an Optional Standalone Unit

Note

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

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

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

command without additional parameters:./startInstGui.sh

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

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

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

Note

l If you enter the command without additional parameters, SAPinst GUI uses the localhost as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. AsSAPinst and GUI server are running on another host, SAPinst GUI cannot connect and theSAP Installation GUI Connection dialog appears.In this case, enter the name of host on which SAPinst is running and choose Log on.The first dialog of the installation appears and you can perform the remote installationfrom your local host.

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

4.3.7 Entries in the Services File Created by SAPinst

After the installation has finished successfully, SAPinst has created the following entries for portnames in <drive:>\WINDOWS\system32\drivers\etc\services:sapdpXX = 32XX/tcp

sapdbXXs = 47XX/tcp

sapgwXX = 33XX/tcp

sapgwXXs = 48XX/tcp

where XX is set from 00 to 99.

Note

If there is more than one entry for the same port number, this is not an error.

94/208 PUBLIC 08/31/2007

4 Installation4.4 Installing Application Sharing Server as an Optional Standalone Unit


4.4 Installing Application Sharing Server as an OptionalStandalone Unit

When you install Application Sharing Server as a standalone engine on a dedicated machine, theNetWeaver Java Application Server (AS Java) is also installed. In SAPinst, there are no specific inputscreens for Application Sharing Server; all input screens are related to the installation of the newAS Java.

Note

If you install Application Sharing Server on a machine that already has an AS Java installed, anadditional Java system is installed on that machine. You then have two engines running on themachine. Typically, this is not recommended as Application Sharing Server requires a dedicatedmachine.

Prerequisites

n Make sure that you have read Application Sharing Server as an Optional Standalone Unit [page 41].n Your machine meets the hardware requirements for AS Java.

Procedure

1. Start SAPinst [page 79] on the dedicated machine.2. In theWelcome screen, choose <SAP System> Optional Standalone Units Application Sharing Server

<Database> Application Sharing Server Installation .3. To start the installation, choose Next.4. Follow the instructions in the SAPinst dialogs and enter the required parameters.

More InformationPost-Installation Steps for Application Sharing Server [page 124]End of: Enterprise Portal (EP)

08/31/2007 PUBLIC 95/208

5 Post-Installation

5 Post-Installation

Note

Before you perform post-installation steps, make sure that you have read the release notes for thesoftware components that you have installed and that you want to use for your IT scenario. You canfind these release notes on SAP Service Marketplace at:http://service.sap.com/releasenotes.

You perform the following post-installation steps:

1. You start and stop the SAP system [page 98].2. You log on to the SAP system [page 100].

3.

Only valid for: Enterprise Portal (EP);EP Core (EPC)

You log on to the portal [page 102].End of: Enterprise Portal (EP);EP Core (EPC)

4. You install the SAP license [page 104].

Caution

This step does not apply to the installation of a Java Add-In for an existing ABAP system.

5. You install the SAP Online Documentation [page 104].

Caution


6. You configure the remote connection to SAP support [page 105].

Caution


7. You perform initial ABAP configuration [page 105].

Caution


8. You apply the latest kernel and Support Packages [page 107].9. You perform the client copy [page 108]

08/31/2007 PUBLIC 97/208

http://service.sap.com/releasenotes



5 Post-Installation5.1 Starting and Stopping the SAP System

Caution


10. You perform a full installation backup [page 109].11. You configure Single Sign-On with Microsoft Lan Manager SSP [page 110].12. You configure Single Sign-On with Microsoft Kerberos SSP [page 115].13. You perform post-installation steps for Adobe Document Services [page 120].14. If required, you configure access to SAP Knowledge Warehouse content from the SAP Internet Knowledge Servlet

[page 122].

15.

Only valid for: BI Java Components (BI-Java);Process Integration (PI)

You set the environment variable CPIC_MAX_CONV [page 123].End of: BI Java Components (BI-Java);Process Integration (PI)

16.


You perform the post-installation steps for usage type Process Integration (PI) [page 123].End of: Process Integration (PI)

17.


You perform the post-installation steps required for Application Sharing Server [page 124].End of: Enterprise Portal (EP)

18. You ensure user security [page 124].

19.

Only valid for: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Mobile Infrastructure

(MI);Process Integration (PI)

To perform basic configuration steps, you run the Configuration Wizard [page 127].

Caution


End of: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Mobile Infrastructure (MI);Process

Integration (PI)

20. You check the Java documentation [page 130] for information that is relevant for running your Java system.21. You may now start with the manual configuration of your IT scenarios for which you find the

appropriate documentation in the SAP Solution Manager [page 132].

5.1 Starting and Stopping the SAP System

You use this procedure to check that you can start and stop the SAP system after the installation withthe SAP Microsoft Management Console (SAP MMC).

98/208 PUBLIC 08/31/2007

5 Post-Installation5.1 Starting and Stopping the SAP System

With a newly installed MMC you can start or stop installed SAP instances locally on the host that youare logged on to. If the MMC is configured for central system administration, you can start or stopthe entire system from a single host.

Note

For more information, see:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life

Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS Microsoft ManagementConsole: Windows

Prerequisites

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

Procedure

1. Start the SAP MMC on the SAP system host by choosing Start All Programs SAP ManagementConsole .

2. Right-click the SAP system node and choose Start or Stop.All instances listed under the system node, will start or stop in the correct order.

3. If the SAP system is installed on multiple hosts (distributed system), you have the followingoptions to start or stop your system:n You start or stop the SAP instances using the MMC on each host.

The correct start order of an SAP system is as follows:a) Database instanceb) SCS instancec) Primary application server where the enqueue and/or message server are running.d) Additional application server, if available.To stop your SAP system use the reverse order.

n You add the remote instances to the MMC configuration to start or stop all instances froma single MMC.To do so, do one of the following:l You configure the MMCmanually. For more information, see Changing the Configuration of

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

Active Directory Services in the SAP MMC documentation.

Caution

Although you have configured your MMC to manage your SAP system centrally, you firsthave to stop the additional application server, before you can stop the other SAP instances.

08/31/2007 PUBLIC 99/208





5 Post-Installation5.2 Logging On to the SAP System

Note

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

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.

ABAP Users

User User Name Client

SAP* 000, 001, 066SAP system user

DDIC 000, 001

ABAP+Java User

User User Name Storage: ABAP System

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

Prerequisites

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

Logging On to the ABAP System

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

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

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

Note

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

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

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

100/208 PUBLIC 08/31/2007

5 Post-Installation5.2 Logging On to the SAP System

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

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

Establishing the J2EE Engine URL

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

Protocol Formula

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

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

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

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

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

Example

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

Logging on to the J2EE Engine

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

2. Log on by choosing EXAMPLES in the upper right corner of the Web page.3. In theWelcome screen, enter the following information:

08/31/2007 PUBLIC 101/208

5 Post-Installation5.3 Logging on to the Portal

n User ID: <J2EE Administrator name>

n Password: <J2EE Administrator password>

Note

To deactivate the J2EE Engine, proceed as follows:

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

to 0.


5.3 Logging on to the Portal

This procedure applies when you install usage type EPC only and when you install it together withusage type EP.You access the portal with a URL using a Web browser from your client machines. To log on tothe portal for the first time, proceed as follows:

1. Establish the default portal URL.2. Log on to the portal.

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

Protocol Formula

HTTP The HTTP port number is based on the number of the SAP J2EE instance on whichyou have installed the portal, and is calculated according to the following formula:HTTP Port = 50000 + (100*<instance number>)

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

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

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

102/208 PUBLIC 08/31/2007

5 Post-Installation5.3 Logging on to the Portal

The default portal URL looks as follows, depending on the protocol that you are using:<protocol>://<portal host name>:<protocol_port_number>/irj

Example

If the portal is installed on a computer identified on the network as PORTAL01, and the J2EE instancenumber is 16, enter the following address:<protocol>://Portal01.sap.corp:51600/irj

Logging on to the PortalUser names and passwords are registered in a directory server or a user list. When you log on to theportal for the first time, there is no directory server or user list associated with the portal. To connectto a user list, you have to create a user management configuration. Until you establish a connectionwith a user list, you log on to the portal using a default user. The default user is the J2EE systemadministrator. You provided the user name and password for this user during the SAP system installation.

Note

The default user logon provides you with access to the portal as administrator (super user). Afteryou have logged on, you can work as a portal administrator using your own name and password.To do so, make sure that you are registered in the directory server or user list to which your securityconfiguration points and that you are associated with the portal administrative role. After the firstlogon, you access the portal with your own name and password.

Procedure

1. Open your Web browser, enter the portal URL as described above and choose Enter.2. In theWelcome screen, enter the following information:n User ID: <J2EE Administrator name>

n Password: <J2EE Administrator password>

Once you have logged on to the portal, the installation phase is complete. The portal is now readyto be configured for your chosen IT scenario.

3. Configure the portal as described in SAP Library at:http://help.sap.com/nw70 SAP NetWeaver Library Technology Consultants Guide Running an

Enterprise Portal <your scenario variant>

Troubleshooting

If the iViews are not displayed correctly, or if the portal does not launch, see Troubleshooting for Usage TypeEnterprise Portal (EP) [page 162].End of: Enterprise Portal (EP);EP Core (EPC)

08/31/2007 PUBLIC 103/208




5 Post-Installation5.4 Installing the SAP License

5.4 Installing the SAP License

Caution


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

Caution

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

ProcedureFor information about the installation procedure for the SAP license, see:http://help.sap.com/nw70 SAP NetWeaver SAP NetWeaver Library Technology Consultant’s Guide

Cross-NetWeaver Configurations SAP License Key

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

5.5 Installing the SAP Online Documentation

Caution


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

ProcessInstall the SAP online documentation in your SAP system as described in the README.TXT filecontained in the root directory of the online documentation DVD, delivered as part of the installationpackage.

104/208 PUBLIC 08/31/2007




http://service.sap.com/licensekey






5 Post-Installation5.6 Configuring Remote Connection to SAP Support

5.6 Configuring Remote Connection to SAP Support

Caution


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

5.7 Performing Initial ABAP Configuration

Caution


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

Procedure

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

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

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

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

Operation Section in SAP Documentation

Set up operation modes ‒transaction RZ04

Configuration Operation Modes

Set up logon groups ‒transaction SMLG

Configuration Logon Load Distribution SAP Logon

Set up administrators Background Processing Authorizations for Background Processing

Schedule background jobs Background Processing

Install a printer SAP Printing Guide

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

n Configuring work processes

08/31/2007 PUBLIC 105/208

http://service.sap.com/remoteconnection






5 Post-Installation5.7 Performing Initial ABAP Configuration

For more information about instance profiles, which is where work processes are defined,see Solution Life Cycle Management by Key Capability System Management Configuration ProfilesProfile Files Instance Profiles .

Note

SAPinst installs SAP systems with a minimum number of work processes. This is only aninitial configuration to get you started after the installation. It is not detailed enough for aproduction system because the optimal number of each type of work process depends on thesystem resources and on the number of users working in each SAP system application. For adetailed configuration contact SAP Technical Consulting.

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

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

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

For more information on configuring the language settings, see the online documentationin transaction I18N I18N Menue I18N Customizing .

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

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

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

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

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

Note

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

n Configuring business applicationsFor more information about how to prepare the SAP system for using business applications,which includes customizing the ABAP system and the business components, see Solution LifeCycle Management by Key Capability Customizing .

106/208 PUBLIC 08/31/2007


5 Post-Installation5.8 Applying the Latest Kernel and Support Packages

5.8 Applying the Latest Kernel and Support Packages

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

Caution

Before you apply support packages, make sure that you have read the release notes for SAPNetWeaver, available on SAP Service Marketplace at http://service.sap.com/releasenotes.

Caution

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

You can use Java Support Package Manager (JSPM) to apply both the latest ABAP+Java or Java kerneland Java support packages.JSPM is a Java standalone tool that you can use with SAP NetWeaver 7.0. JSPM uses the SoftwareDeployment Manager (SDM) to apply support packages and patches and to deploy softwarecomponents.For more information about JSPM and how to use this tool, see http://help.sap.com/nw70 SAPNetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SoftwareLife Cycle Management Software Maintenance Java Support Package Manager

PrerequisitesTo extract the downloaded SAR files make sure that you use the latest SAPCAR version, which youcan find on SAP Service Marketplace at http://service.sap.com/swdc. You need at least SAPCAR700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longerunpack current SAR files. For more information, see SAP Note 212876.

Procedure

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

2. Apply Support Packages.a) For up-to-date information about recommended combinations of Support Packages and

patches, see SAP Service Marketplace at:http://service.sap.com/sp-stacks

08/31/2007 PUBLIC 107/208















5 Post-Installation5.9 Performing the Client Copy

For up-to-date release information on Support Package Stacks and about how to apply them,see the documentation SAP NetWeaver 7.0 ‒ Support Package Stack Guide <current version> on SAPService Marketplace at http://service.sap.com/Maintenancenw70.

b) Alternatively, you can download Support Packages from SAP Service Marketplace at:http://service.sap.com/patches

c) Apply the ABAP Support Packages to your SAP system with the help of the Support PackageManager (formerly called SAP Patch Manager, transaction SPAM).

d) Apply the Java Support Packages to your SAP system with the help of the Java Support PackageManager (JSPM).

For more information about the availability of Support Packages, see the SAP Service Marketplaceat:http://service.sap.com/ocs-schedules

Note

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

5.9 Performing the Client Copy

SAPinst creates three ABAP clients during the installation, client 000, client 001, and client 066.Client 000 is the SAP reference client for ABAP.If you chose to install an ABAP+Java system in one installation run, AS Java was configured againstclient 001 during the installation.Your production client must be a copy of the SAP reference client 000. For more information, seeProduction Client Considerations [page 24]


Caution

For client copy considerations for usage type Process Integration (PI), see SAP Note 940309.

End of: Process Integration (PI)

Procedure

1. Maintain the new client with transaction SCC4.2. Activate kernel user SAP*:

a) Set the profile parameter login/no_automatic_user_sapstar to 0.

108/208 PUBLIC 08/31/2007

http://service.sap.com/Maintenancenw70



http://service.sap.com/patches



http://service.sap.com/ocs-schedules



http://service.sap.com/noteassistant




5 Post-Installation5.10 Performing a Full Installation Backup

b) Restart the application server.3. Log on to the new client with kernel user SAP* and password PASS.4. Copy the client with transaction SCCL and profile SAP_CUST.5. Check the log files with transaction SCC3.6. Create the required users. These users must have at least the authorizations required for user

administration and system administration. Create a user SAP* with all required authorizationsfor this user. If you want to have other users for system administration, you can also create userSAP* without authorizations.

7. Deactivate kernel user SAP*:a) Reset login/no_automatic_user_sapstar to 1.b) Restart the application server.

For more information, see:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life

Cycle Management by Key Capability Software Lifecycle Management Software Logistics Change and TransportSystem BC ‒ Client Copy and Transport

5.10 Performing a Full Installation Backup

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

Prerequisites

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

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

Procedure

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

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

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

a) Choose Start All Programs Accessories System Tools Backup .

08/31/2007 PUBLIC 109/208




5 Post-Installation5.11 Single Sign-On with Microsoft Lan Manager SSP

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

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

including:\USR\SAP

<HOMEDIR> of <sapsid>adm

\%WINDIR%

e) Choose Next.f) InWhere to Store the Backup, select the Backup media type and enter the Backup media or file name for

the backup.g) Choose Next.h) Check the information displayed and then choose Finish to start the backup.

5.11 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 logonprocedure. When your system is configured for SSO, an authorized user who has logged on to theWindows operating system can access the SAP system simply by selecting it in the SAP logon windowor clicking the shortcut. There is no need to enter the SAP system user name and password whenyou log on to your SAP system with SAP GUI. SSO makes it significantly easier for you to manageSAP system users.In this section, we describe the option that is the easiest to implement when using a full MicrosoftWindows landscape (Windows 9x, Windows ME, Windows NT, Windows 2000 and higher). It is atailored version for SSO with Secure Network Communications (SNC), which uses Microsoft’sdomain authentication, LAN Manager Security Service Provider (NTLM SSP).For more information on SNC, see the SNC User’s Guide on SAP Service Marketplace athttp://service.sap.com/security

Prerequisites

n Typically, SNC requires an external security product that complies with the Generic SecurityService API V2 (GSS-API V2) interface and that has been certified by the SAP Software PartnerProgram. However, in this scenario, we provide a library that complies with the GSS-API V2

110/208 PUBLIC 08/31/2007





interface on one side and that communicates with Microsoft’s NTLM SSP on the other. SinceNTLM SSP is already built into Microsoft Windows platforms, you do not need to purchase anadditional security product to use SSO.

Note

The Microsoft NTLM SSP only provides authentication based on a challenge-responseauthentication scheme. It does not provide data integrity or data confidentiality protection forcommunication itself. All third-party SNC certified security products offer data integrity andprivacy protection. If you require such a confidentially protected communication, you have toobtain a BC-SNC certified Single Sign-On solution.If you use Windows 2000 or higher, we offer another library (Kerberos 5 DLL) that uses theMicrosoft Kerberos SSP instead of the NTLM SSP for authentication. For more information, seeSingle Sign-On with Microsoft Kerberos SSP [page 115].We distribute two different versions of the wrapper library for Microsoft’s NTLM SSP. The olderversion, which is shipped on the kernel DVD is called gssapi32.dll. The newer version is calledgssntlm.dll and is attached to SAP Note 352295.

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

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

n The GSS-API V2 library wrapper (gssntlm.dll) must be installed on every application server.n The GSS-API V2 library wrapper must also be installed on every front-end PC.n We recommend that you use the 7-bit ASCII character set for all Windows user IDs.n When the code page of the SAP system is different from the code page on the Windows machines,

it is not possible to enter Windows user IDs that contain 8-bit characters into the USRACL table(for example, by calling transaction SU01). The combination of Windows ANSI (=ISO Latin 1)and the default SAP code page 1100 provides the same encoding of 8-bit characters and permitsthe use of 8-bit characters with gssntlm.dll.

n For more information on how to improve the security of your system with third-party products,see:http://help.sap.com/nw70 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. Prepare the application server for Single Sign-On [page 112] .2. Prepare SAP GUI and SAP logon for Single Sign-On [page 113].3. Map SAP system users to Windows users for Single Sign-On [page 114].

08/31/2007 PUBLIC 111/208






5.11.1 Preparing the Application Server for Single Sign-On

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

Note

The following gssntlm.dll files are available:gssntlm.dll for Windows x86gx64ntlm.dll for Windows x86_64gi64ntlm.dll for Windows IA64

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

snc/data_protection/max =1

snc/data_protection/min =1

snc/data_protection/use =1

snc/enable =1

snc/gssapi_lib =

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

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

SAPSERVICE<SAPSID> is the user who runs the SAP system.<WIN_DOMAIN_NAME> is the Windows domain of this user.

Note

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

Additional SNC ParametersThe following profile parameters let you continue with password-based access to the SAP systemwhen SNC has been enabled. To log on to the SAP system as an administrator to maintain themapping of Windows user accounts to SAP system user IDs (user and client), you have to usethese additional parameters at least once after enabling SNC. Once the mapping (at least for theadministrator) has been entered, you can disable further password-based logons by removing thecorresponding profile parameters.snc/accept_insecure_cpic =1

snc/accept_insecure_gui =1

snc/accept_insecure_rfc =1

snc/permit_insecure_start =1

112/208 PUBLIC 08/31/2007



snc/permit_insecure_comm =1

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

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

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

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

Procedure

1. Copy the gssntlm.dll file to the SAP GUI directory.To download the gssntlm.dll file, see SAP Note 352295.

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

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

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

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

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

system again as the same user.n Copy gssntlm.dll to a directory of the default search path, for example,

%SystemRoot%\system32 and rename the file to sncgss32.dll This is the default file namethat SNC uses when SNC_LIB is neither entered on the command line nor available in theenvironment.

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

p:<WIN_DOMAIN_NAME>\SAPSERVICE<SAPSID>

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

08/31/2007 PUBLIC 113/208



Example

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

ResultThe SAP logon window now displays an icon with a small yellow key beside the system entry,indicating that SSO is active.When the SAP administrator has entered the mapping [page 119] between a user’s Windows Accountand the user’s SAP system user ID, the next time this SAP system user logs on to the system, theapplication is opened without requiring the user to enter a user name and password.If only one possible match exists between the Windows account and the SAP system user ID, thelogon screen is skipped, unless the profile parameter snc/force_login_screen = 1 is present inthe instance profile of the application server.

5.11.3 Mapping SAP Users to Windows Users for SingleSign-On

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

PrerequisitesYou have completed the following procedures:

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

Procedure

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

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

p:<WIN_DOMAIN_NAME>\<NT_USERNAME>

<WIN_DOMAIN_NAME> is the Windows domain that the Windows user belongs to.<NT_USERNAME> is the logon ID of the Windows user.p is a prefix required by all SNC names.Windows account names, as used for the NTLM authentication, are not case-sensitive.

114/208 PUBLIC 08/31/2007

5 Post-Installation5.12 Single Sign-On with Microsoft Kerberos SSP

Example

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

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

7. Save your entries.

5.12 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 thelogon procedure. You can use it if you have Windows 2000 or higher in your system landscape.When your system is configured for SSO, an authorized user who has logged on to Windows canaccess the SAP system simply by selecting it in the SAP logon window or clicking the shortcut. Thereis no need to enter the SAP system user name and password when you log on to your SAP system withSAP GUI. SSO makes it significantly easier for you to manage SAP system users.The Microsoft Kerberos Security Service Provider (SSP) provides secure authentication plusencryption of the network communication. In contrast, SSO with Microsoft NTLM SSP does notprovide encryption of the network communication.

Note

For more information, on Single Sign-On with Kerberos and the required DLLs, see SAP Notes595341 and 352295.

When using the <Kerberos5_name>.dll, the Microsoft Kerberos SSP might be interoperable withKerberos implementations from other vendors and suppliers.However, SAP does not and cannot provide support for third-party libraries loaded at the BC-SNCinterface. Documentation and support must be provided by the vendor or supplier of the third-partysoftware. Therefore, SAP recommends that customers use BC-SNC certified Single Sign-On solutions,for which a single vendor has committed to provide implementation, documentation and support.For more information, see http://www.sap.com/partners/directories/SearchSolution.epxUnder Certification Category, search for Secure network communication and choose Search.

Prerequisites

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

Process Flow

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

08/31/2007 PUBLIC 115/208



http://www.sap.com/partners/directories/SearchSolution.epx


1. Prepare the central instance [page 116].2. Configure the SAP front ends [page 117].3. Configure the SAP logon [page 118].4. Map SAP users to Windows users [page 119].

5.12.1 Preparing the Central Instance

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

Procedure

1. Copy the Kerberos DLL for your platform to the following directory on the central instance:<Drive>:\%windir%\system32.

Note

The following Kerberos DLLs are available:gsskrb5.dll for Windows x86gx64krb5.dll for Windows x86_64gi64krb5.dll for Windows IA64

For more information about how to get the Kerberos 5 file, see SAP Note 595341.2. In the instance profile of the central instance, set the SAP parameters:

snc/enable = 1

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

snc/identity/as =p:SAPService<SAPSID>@<UPPERCASE_DNS_DOMAIN_NAME>

<DNS_DOMAIN_NAME> is the Windows domain that the SAPService<SAPSID> user belongs toand <UPPERCASE_DNS_DOMAIN_NAME> is the corresponding Kerberos Realm name, for example,NT5.SAP-AG.DE.

Caution

<UPPERCASE_DNS_DOMAIN_NAME> and the SAPService<SAPSID> user are case-sensitive. Make surethat you enter uppercase and lowercase correctly, for example:p:[email protected].

Additional SNC ParametersThe following profile parameters let you continue with password-based access to the SAP systemwhen SNC has been enabled. To log on to the SAP system as an administrator to maintain themapping of Windows user accounts to SAP system user IDs (user and client), you have to usethese additional parameters at least once after enabling SNC. Once the mapping (at least for the

116/208 PUBLIC 08/31/2007



administrator) has been entered, you can disable further password-based logons by removing thecorresponding profile parameters.snc/accept_insecure_cpic =1

snc/accept_insecure_gui =1

snc/accept_insecure_rfc =1

snc/permit_insecure_start =1

snc/permit_insecure_comm =1

3. Stop and restart the SAP system so that the profile parameters take effect.

5.12.2 Configuring the SAP Front End

To configure the SAP front end for SSO, you choose between the following approaches:

n Configure each SAP front end individuallyYou configure each machine where the SAP front end is running.

n Configure all SAP front ends automaticallyYou define a Group Policy for a Windows domain. This policy causes the wizard for configuring SSOto be started automatically in the background the next time any member of the domain logs onto an SAP front end.

These approaches are described below.

PrerequisitesYou have completed Preparing the Central Instance [page 116].

Configuring SAP Front Ends Individually

1. Log on to the host where the SAP front end is running.2. Copy the SAPSSO.MSI program to a local directory or to a shared directory on the network.

To download the SAPSSO.MSI file, see SAP Note 352295.3. Double-click the SAPSSO.MSI file.

The wizard SAP Kerberos SSO Support automatically starts and configures the SAP front end for SSO.

Configuring SAP Front Ends Automatically

1. Log on to a front-end machine as domain administrator of the Windows domain.2. Copy the program SAPSSO.MSI to a shared directory.

For more information about how to get the SAPSSO.MSI file, see SAP Note 595341.3. Choose Start Programs Administrative tools Active Directory Users and Computers .

The dialog box Active Directory Users and Computers appears.4. Right-click the domain for which you want to set up SSO and choose Properties.

The dialog box <Domain_Name> Properties appears.

08/31/2007 PUBLIC 117/208




5. Choose Group Policy New to start creating a new policy object .The dialog box for creating a new policy object appears.

6. In group Policy Object Links, enter a name for the new policy object, such as SAPSSO.7. Choose Edit to define the contents of the policy.8. In the Group Policy Editor choose User Configuration Software Settings Software Installation. .

The Deploy Software dialog box appears.9. Right-click Deploy Software and choose New Package .

The Open dialog box appears.10. Select the file SAPMSSO.MSI from the shared location.11. Specify the path with the UNC name (\\<hostname>\<share>).12. Select Assign and confirm with OK.

You have now created a new Group Policy.The next time any user logs on to the domain with the SAP front end, the wizard SAP Kerberos SSOSupport automatically starts and configures the front end for SSO.

5.12.3 Activating Single Sign-On for the SAP Logon

The SAP Logon window includes a list of systems or machines that you can log on to. For each of thesystems or machines in the list for which you want to implement SSO, follow the procedure below.

PrerequisitesYou have completed the following:

n Preparing the Central Instance [page 116]n Configuring the SAP Front End [page 117]

Procedure

1. Right-click an entry in the SAP Logon window and choose Properties.2. In the Network tab, select Activate Secure Network Communication..3. In SNC name, enter:

p:SAPService<SAPSID>@<UPPERCASE_DOMAIN_NAME>

where <UPPERCASE_DOMAIN_NAME> is, for example, NT5.SAP-AG.DE.

118/208 PUBLIC 08/31/2007


Note

n Enter the same string that you entered in the central instance profile forsnc/identity/as

If the system C11 is running on account SAPServiceC11 of the domain NT5.SAP-AG.DE, youenter:P:[email protected]

n If the entry you selected in the logon dialog box is a group entry, for example, C11 (PUBLIC),the SNC name field is already filled.

4. Choose OK to confirm your entries.

The SAP Logon window now displays an icon with a key beside the system entry. This indicates thatSingle Sign-On is active for the system.

5.12.4 Mapping SAP Users to Windows Users

PrerequisitesYou have completed the following:

n Preparing the Central Instance [page 116]n Configuring the SAP Front End [page 117]n Activating Single Sign-On for the SAP Logon [page 118]

Procedure

1. Log on to the SAP system as administrator.2. Choose Tools Administration Maintain Users Users or call transaction SU01.

The User Maintenance window appears.3. Enter the name of the SAP user and choose User names Change.4. Choose SNC.5. In SNC name, enter the case-sensitive name for the Windows user that is to be assigned to the

SAP user:p:<WINNT_USERNAME>@<UPPERCASE_DNS_DOMAIN_NAME>

where <WINNT_USERNAME> is the logon ID of the Windows user as spelled in the Active Directoryand <UPPERCASE_DNS_DOMAIN_NAME> is the uppercase DNS domain name of the Windows domainthat the user is logged on to.

Example

For the user kissnerj, belonging to the domain NT5.SAP-AG.DE , enter:p:[email protected]

6. Select Insecure communication permitted.

08/31/2007 PUBLIC 119/208

5 Post-Installation5.13 Post-Installation Steps for Adobe Document Services

This lets the user work in a different domain because it permits the user to access the systemwithout SSO.

7. Save your entries.

5.13 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 120].n You perform quick tests for Adobe Document Services (ADS) [page 120].

5.13.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.After the installation you have to assign the required authorization roles manually to these users inthe ABAP system, as described below.

Assigning Role SAP_BC_FP_ICF to ADS_AGENT

1. Log on to the ABAP system with user DDIC or SAP*.2. Call transaction SU01.3. Enter ADS_AGENT in the User field.4. Choose User Names Change .5. Choose the Roles tab and assign the role SAP_BC_FP_ICF to the user ADS_AGENT.

Creating Role ADSCallers and Assigning it to ADSUSER

1. Log on to the ABAP system [page 100].2. Call transaction PFCG.3. Enter ADSCallers in the Role field.4. Choose Role Create .5. On the Create Roles screen, choose Role Save .6. Choose the User tab and assign the user ADSUSER in the User ID field.

5.13.2 Installation Check and Quick Tests for AdobeDocument Services

This procedure shows you how to check your installation of Adobe Document Services (ADS) entriesfor the correct user, security role, passwords, and RFC destination.

120/208 PUBLIC 08/31/2007

5 Post-Installation5.13 Post-Installation Steps for Adobe Document Services

Note

This procedure contains only minimal configuration steps to check if the ADS installation withSAPinst was successful.For detailed configuration documentation, see the configuration guide for Adobe DocumentServices:

n On SAP Service Marketplace at:http://service.sap.com/adobe SAP Interactive Forms by Adobe Media Library Documentation

Adobe Document Services - Configuration Guide NetWeaver 7.0

n In the SAP Library at:http://help.sap.com/nw70 SAPNetWeaver Library Technology Consultant’s Guide Cross-NetWeaver

Configurations Adobe Document Services - Configuration .

Checking the User and Password

1. Open a web browser and enter the following URL:http://<J2EE_host>:<J2EE_port>/AdobeDocumentServices/Config

Note

Note that the entries in the URL are case-sensitive.

The web page of the Web service AdobeDocumentServices is displayed.2. Choose Test.3. Choose rpdata(test...).4. Choose Send without entering any parameters.5. Enter ADSUser as user name and the password you previously entered for this user .6. Choose Submit.

If the setup is correct, the system displays the version number in the response area.

Note

You can ignore the message Required stream: “PDFDocument” not found.

If the setup is not correct, the page does not change and Submit remains on the screen.

Checking the ABAP Connection

1. Log on to your SAP system.2. Call transaction SE38.3. Enter the name of the test report FP_PDF_TEST_00.4. Choose Execute ( F8 ).

08/31/2007 PUBLIC 121/208

http://service.sap.com/adobe






5 Post-Installation5.14 Configuring Access to Knowledge Warehouse Content from the SAP Internet Knowledge Servlet

If the setup is correct, the system displays the version number. Otherwise, the system displays adialog box with input fields for the user and password. In this case, check your settings for theABAP connection.

TroubleshootingIf the tests are not successful, you might have to make some adjustments to the initial technicalconfiguration for ADS [page 147].

5.14 Configuring Access to Knowledge Warehouse Contentfrom the SAP Internet Knowledge Servlet

You need to perform this step if you want to use the variant Documentation Manuals and TrainingMaterials Management of the scenario Enterprise Knowledge Management.For more information, see SAP Library at http://help.sap.com/nw70 SAP NetWeaver LibraryIT Scenarios at a Glance Enterprise Knowledge Management Documentation, Manuals and Training MaterialsManagement .The SAP Internet Knowledge Servlet (IKS) is a Java servlet based on the J2EE Engine. It is used todisplay content stored in the Knowledge Warehouse (KW) in the browser.

PrerequisitesYou have completed the installation of AS ABAP and AS Java as described in this documentation.

Procedure

1. Create a user of type system in your ABAP system using transaction SU01 and assign this user tothe role SAP_KM_KW_RFC_CPIC_USER.This user is needed for the connection between the SAP IKS and the ABAP system.

2. Make sure that the Administrator user of the J2EE Engine has the required authorizations toperform the configuration:a) Log on to the User Management Engine (UME) using the URL

http://<J2EE_host>:<J2EE_port>/useradmin/index.jsp.b) Assign either the role SAP_J2EE_ADMIN or KW_ADMINISTRATOR to the Administrator user.c) If none of these roles exists, you need to create one of them. You do not need to perform

further configuration of the newly created role.d) Log off from the UME.

3. Open a browser window and enter the following URL:http://<J2EE_host>:<J2EE_port>/SAPIKS2

The UME logon page appears.4. Log on as the Administrator user of the J2EE Engine.5. In the next screen, choose Direct Access to the SAP Knowledge Warehouse.

122/208 PUBLIC 08/31/2007


5 Post-Installation5.15 Setting Environment Variable CPIC_MAX_CONV

6. Choose Continue.7. In the next screen, enter the connection parameters to the KW back-end system.8. Choose Test.9. If the connection was successfully established, save the parameters. If not, correct the parameters.10. After saving the parameters you can access the Knowledge Warehouse directly from the next

screen.

Only valid for: BI Java Components (BI-Java);Process Integration (PI)

5.15 Setting Environment Variable CPIC_MAX_CONV

1. Log on to your SAP system as a user with administration rights.2. Call transaction RZ10.3. Set the value gw/max_conn_per_wp to a higher value (at least 200) and restart the system.

End of: BI Java Components (BI-Java);Process Integration (PI)


5.16 Post-Installation Steps for Usage Type ProcessIntegration (PI)

You need to perform the following post-installation steps for usage type PI after SAPinst has finished.

5.16.1 Performing PI-Specific Steps for SLD Configuration

Central SLD: Checking the CR Data in the SLD (optional)Since CR_Content.zip contains all available SAP components, the content of this file grows with time.The extensions contain information about new components (new releases and Support Packages, forexample). This content in the SLD has to be updated from time to time.You can download the most up-to-date files from the SAP Service Marketplace.For more information, see SAP Note 669669.

More InformationFor more information on SLD users and security roles, see the Post-Installation Guide - SLD of SAPNetWeaver 7.0 at http://service.sap.com/sld Media Library .End of: Process Integration (PI)

08/31/2007 PUBLIC 123/208





5 Post-Installation5.18 Ensuring User Security


5.17 Post-Installation Steps for Application Sharing Server

After you have installed the necessary software, you must complete a number of configurationsteps in the portal to fully implement application sharing functionality in the portal. These stepsare valid if you installed Application Sharing Server as a standalone engine or are using the defaultserver installed on the portal machine.For more information, see:http://help.sap.com/nw70 SAP NetWeaver SAP NetWeaver by Key Capability People Integration

Collaboration Administration Guide Real-Time Collaboration Configuring Real-Time Collaboration Configuringthe Application Sharing Server (RTC) .This documentation includes information on how you define which Application Sharing Serverthe portal must use.If you do not intend to use Application Sharing Server, you can disable it. For more information, see:http://help.sap.com/nw70 SAP NetWeaver SAP NetWeaver by Key Capability People Integration

Collaboration Administration Guide Real-Time Collaboration Configuring Real-Time Collaboration Configuringthe Application Sharing Server (RTC) Enabling / Disabling the Application Sharing Server (RTC) .End of: Enterprise Portal (EP)

5.18 Ensuring User Security

You need to ensure the security of the users that SAPinst creates during the installation. For securityreasons, you also need to copy the installation directory to a separate, secure location ‒ such as aDVD ‒ and then delete the installation directory.

Recommendation

In all cases, the user ID and password are only encoded when transported across the network.Therefore, we recommend using encryption at the network layer, either by using the Secure SocketsLayer (SSL) protocol for HTTP connections, or Secure Network Communications (SNC) for the SAPprotocols dialog and RFC.For more information, see:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Security

Network and Transport Layer Security

124/208 PUBLIC 08/31/2007







Caution

Make sure that you perform this procedure before the newly installed SAP system goes intoproduction.

PrerequisitesIf you change user passwords, be aware that SAP system users might exist in multiple SAP systemclients (for example, if a user was copied as part of the client copy). Therefore, you need to change thepasswords in all the relevant SAP system clients.

ProcedureFor the users listed below, take the precautions described in the relevant SAP security guide, whichyou can find on SAP Service Marketplace at http://service.sap.com/securityguide:

ABAP+Java Users

User User Name Comment

SAP* User exists at least in SAP system clients000, 001 and 066.

DDIC User exists at least in SAP system clients000 and 001.

EARLYWATCH User exists at least in SAP system client066.

SAP system user

SAPCPIC User exists at least in SAP system clients000 and 001.

Administrator The name that you gave this userduring the installation or the defaultname J2EE_ADMIN

This user’s password is stored in securestorage. Therefore, whenever youchange the administrator’s password,you must also change the password insecure storage.For more information, see Checking theSAP Java Documentation [page 130].

Guest The name that you gave this userduring the installation or the defaultname J2EE_GUEST

‒

Communication user forthe J2EE Engine

The name that you gave this userduring the installation or the defaultname SAPJSF.

‒

ADSUSER User exists at least in SAP system clients000 and 001.

Users for AdobeDocument Services (ADS)

ADS_AGENT User exists at least in SAP system clients000 and 001.

08/31/2007 PUBLIC 125/208

http://service.sap.com/securityguide




User User Name Comment

Data supplier userfor System LandscapeDirectory (SLD) (optional)

The name that you gave this userduring the installation.The recommended name is SLDDSUSER.

User exists at least in SAP system clients000 and 001.

NoteSAPinst created this user automaticallyif you chose Configure local SLD duringthe installation.

ABAP API user for SystemLandscape Directory (SLD)(optional)

The name that you gave this userduring the installation.The recommendedname is SLDAPIUSER.

User exists at least in SAP system clients000 and 001.


Java Add-In Users for Users Stored in the ABAP System

User User Name Storage: ABAP System Comment

Administrator The name that you gave this userduring the installation or the defaultname J2EE_ADMIN

This user’s password is stored in securestorage. Therefore, whenever youchange the administrator’s password,you must also change the password insecure storage.For more information, see Checking theSAP Java Documentation [page 130].

Guest The name that you gave this userduring the installation or the defaultname J2EE_GUEST

‒

Communication user forthe J2EE Engine

The name that you gave this userduring the installation or the defaultname SAPJSF

‒

ADSUSER User exists at least in the clients 000 and001 of the ABAP system.

Users for AdobeDocument Services (ADS)

ADS_AGENT User exists at least in the clients 000 and001 of the ABAP system.

126/208 PUBLIC 08/31/2007

5 Post-Installation5.19 Running the Configuration Wizard

User User Name Storage: ABAP System Comment

Data supplier userfor System LandscapeDirectory (SLD) (optional)

The name that you gave this userduring the installation.The recommended name is SLDDSUSER.

User exists at least in the clients 000 and001 of the ABAP system.


ABAP API user for SystemLandscape Directory (SLD)(optional)

The name that you gave this userduring the installation.The recommendedname is SLDAPIUSER.

User exists at least in the clients 000 and001 of the ABAP system.


Only valid for: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Mobile Infrastructure

(MI);Process Integration (PI)

5.19 Running the Configuration Wizard

This section provides information about how to run the Configuration Wizard for the SAP NetWeaverusage types.

Note

You can run the Configuration Wizard only once and only directly after you installed and patchedthe system.You cannot use the configuration wizard after:

n Upgrade

n Add-In installation

n Enablement of additional usage types

In these cases, you need to perform the corresponding configuration steps as described in theconfiguration documentation.For more information , see Accessing Configuration Documentation in the SAP Solution Manager [page 132].You can also find configuration documentation in the Technology Consultant’s Guide in the SAPLibrary at:http://help.sap.com/nw70 SAP NetWeaver Technology Consultant’s Guide

For more information about how to start the Configuration Wizard, see the SAP Library at:

08/31/2007 PUBLIC 127/208





http://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’s Guide Developing,Configuring, and Adapting Applications Creating Java Applications Using Web Dynpro J2EE Engine ConfigurationConfiguration Wizard

Note

For more information on the Configuration Wizard and its limitations, see SAP Note 923359.

PrerequisitesBefore you run the configuration wizard, make sure you have applied the latest kernel and support packages[page 107] to your system.

Only valid for: Application Server (AS)

Usage Type: Application ServerYou need to run the following configuration tasks using the Configuration Wizard to automaticallyconfigure the SAP NetWeaver Administrator (NWA):

1. SLD system: Configure and activate SLD2. SLD system: Connect SLD to CEN (if CEN present)3. NWA system: Basic configuration4. NWA system: Connect NWA to CEN (if CEN present)5. NWA system: Store access data per each managed Java system (optional)6. NWA system: Register each managed ABAP system to SLD7. Managed Java system: Register system to SLD

Note

For more information about the NetWeaver Administrator, seehttp://service.sap.com/operationsnw70 Monitoring Monitoring Setup Guide

for NetWeaver 7.0 SP Stack 09/SR2 .

End of: Application Server (AS)


Usage Type: Process Integration (PI)After SAPinst has finished and you have performed the necessary post-installation steps for usagetype PI, you need to run the configuration task PIPostInstallProcess using the ConfigurationWizard. To select the configuration task, change the scenario on the right of the page to PI.

128/208 PUBLIC 08/31/2007





http://service.sap.com/operationsnw70




Caution

If you are using a central SLD, you also have to perform the steps for SLD configurationmanuallyas described in SAP Note 939592.

Note

After the Configuration Wizard has finished, you need to restart your SAP system.



Usage Type: BI Java Components (BI-Java)After SAPinst has finished, you need to run the configuration task BIPostInstallProcess usingthe Configuration Wizard.End of: BI Java Components (BI-Java)

Only valid for: Development Infrastructure (DI)

Usage Type: Development InfrastructureAfter SAPinst has finished, you need to run the configuration task for usage typeDI using theConfiguration Wizard.

1. Under Scenario choose DI.2. Decide whether you want to install and run the entire NWDI on this system or configure the

services individually:

Recommendation

We recommend that use the first option shown below, to install and run the entire NWDI onthis system.

n To install and run the entire NWDI on this system, perform the following steps:a) Choose the Scenario DIb) Choose All-in-one Complete Configuration of DTR, CBS, and CMSc) Fill the open fields in the section Data Entry according to their label.d) To run the configuration task, choose Execute Template.

n To configure the services individually (DTR, CBS, CMS) ‒ for example, because you havedistributed the usage type DI to different servers ‒ perform the following steps:a) Choose the Scenario DIb) Choose the service you want to configure, Design Time Repository, Component Build Service, or

Change Management Service.c) Fill the open fields in the section Data Entry according to their label.d) To run the configuration task, choose Execute Task.

08/31/2007 PUBLIC 129/208


5 Post-Installation5.20 Checking the SAP Java Documentation

e) Choose the items that you need from Design Time Repository Configuration, Component Build Service,and Change Management Service.

Note

Before performing any database settings make sure that you have read SAP Note 889038.

3. After the Configuration Wizard has finished, you have to restart the engine as described in SAPNote 919942.

End of: Development Infrastructure (DI)

Only valid for: Mobile Infrastructure (MI)

Usage Type: Mobile InfrastructureAfter SAPinst has finished, you need to run the configuration task MI Post Installation Process

using the Configuration Wizard.End of: Mobile Infrastructure (MI)

End of: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Mobile Infrastructure (MI);Process

Integration (PI)

5.20 Checking the SAP Java Documentation

Here you can find information about the configuration of the J2EE Engine and about SAP Javatechnology in the SAP Library.

Procedure

1. Go to the following place in the documentation:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Application

Platform by Key Capability Java Technology .2. Check the following documentation for information relevant to running your Java system:

Manual Contents

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

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

NetWeaver Developer Studio

130/208 PUBLIC 08/31/2007






5 Post-Installation5.20 Checking the SAP Java Documentation

Manual Contents

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

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

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

Infrastructure (JDI)

n J2EE Engine and J2EE Engine securityn Supportability and performance managementn Administration and configuration of Web Dynpro runtime

environmentn Administration of the XML Data Archiving Service (XML DAS)

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

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

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

More InformationFor troubleshooting the J2EE Engine, see the J2EE Engine Problem Analysis Guide at:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life

Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) J2EE Engine ProblemAnalysis Scenarios

08/31/2007 PUBLIC 131/208




5 Post-Installation5.21 Accessing Configuration Documentation in the SAP Solution Manager

5.21 Accessing Configuration Documentation in the SAPSolution Manager

To access configuration documentation in the SAP Solution Manager, you have to connect yournewly-installed SAP system to the SAP Solution Manager.

Note

For SAP NetWeaver 7.0 usage types you can also find configuration documentation in the TechnologyConsultant’s Guide at: http://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’sGuide

Prerequisites

n You have installed an SAP Solution Manager system as described in the documentation InstallationGuide ‒ SAP Solution Manager <3.2 or 4.0> on <OS>: <Database>.

n You have connected your SAP system to the SAP Solution Manager as described in thedocumentation Configuration Guide ‒ SAP Solution Manager <3.2 or 4.0>.

For more information, see SAP Service Marketplace at http://service.sap.com/instguides

SAP Components SAP Solution Manager Release <3.2 or 4.0> .

Procedure

1. Log on to your SAP Solution Manager system.2. To be able to access configuration documentation, create a project as follows:

a) Create your project with transaction SOLAR_PROJECT_ADMIN for project administration.b) Connect your SAP system to the SAP Solution Manager with transaction SMSY for the SAP

Solution Manager system landscape.c) Create a project structure and add the required scenarios for your SAP system to your project

structure with the Business Blueprint transaction SOLAR01,d) Add your SAP system configuration structures to your project structure with the configuration

transaction SOLAR02.For more information about creating projects, assigning scenarios to projects, and creatingconfiguration structures, see:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life

Cycle Management by Key Capability SAP Solution Manager Using the SAP Solution Manager in Projects3. Go to the project structure folder <project name> using transaction SOLAR02.4. Access configuration documentation for SAP NetWeaver usage types at Configuration Structure

SAP NetWeaver 7.0 .

132/208 PUBLIC 08/31/2007










5 Post-Installation5.21 Accessing Configuration Documentation in the SAP Solution Manager

ResultYou can now configure your SAP system according to the configuration documentation in theSAP Solution Manager.

08/31/2007 PUBLIC 133/208

6 Additional Information

6 Additional Information

The following sections provide additional information about optional preparation andpost-installation tasks:

Preparation

n Database Installation for Multiple Components with MS SQL Server [page 135]n Installation of Multiple Components in One Database [page 137]n Integration of LDAP Directory Services [page 139]n Setting Up the Active Directory [page 142]n Preparing User Management with an External ABAP system [page 143]

Post-Installation

n Configuring User Management to Use an LDAP Directory [page 146].n Usage Type-Specific Initial Technical Configuration [page 146]n Deleting an SAP System [page 155]n SAP System Security on Windows [page 157]n Automatic Creation of Accounts and Groups [page 159]n Manually Granting User Rights for the Installation [page 160]n Troubleshooting [page 161]

6.1 Database Installation for Multiple Components with MSSQL Server

Each SAP system in your mySAP environment needs its own database back end. With MS SQL Serveryou have the following options to distribute your systems across the available hardware resources.They differ with respect to hardware requirements, database administration, flexibility, and scalability.

n Exclusive database serverIn this system landscape, each database server (with or without a central instance) hosts exactlyone SAP database. From an installation planning perspective, this is the simplest solution. It isthe most scalable setup, but it requires the most hardware. This option is typically chosen formedium-sized and large production and development systems.

n Named SQL Server instancesWith the use of named instances, you can install multiple, independent SQL Server instances ona single database server. These instances share CPU, memory and disk resources, but from an

08/31/2007 PUBLIC 135/208

6 Additional Information6.1 Database Installation for Multiple Components with MS SQL Server

administration point of view are completely independent from each other. This option, like thefollowing two, requires careful hardware sizing to avoid performance bottlenecks and scalabilityproblems.

n Multiple databases in an SQL Server instanceSQL Server lets you operate multiple user databases in a single SQL Server instance. Contrary tonamed instances, the databases share the temporary system database tempdb, the SQL ServerWindows process, and the SQL Server memory pool. Therefore, this setup is less scalable thannamed instances, but at the same time requires less system resources. It can be a flexible solutionfor small and medium-sized systems. This option requires careful hardware sizing to avoidperformance bottlenecks and scalability problems.

n Multiple Components in One Database (MCOD)Multiple database back ends are stored in the same database, each in its own database schema. Forthe database administrator, the database containing these multiple components looks very muchlike a single entity. While this approach is not as flexible as the other options, its simplicity makesit an attractive solution for small mySAP environments. This option requires careful hardwaresizing to avoid performance bottlenecks and scalability problems.

More Information

n Default or Named MS SQL Server Instances [page 136]n Multiple Components in One Database (MCOD) [page 137]

6.1.1 Default or Named MS SQL Server Instances

When you install MS SQL Server, you can install two different types of instances:

n Default instance

n Named instance

When you plan your system configuration, you must decide which instance type you want to install.The following clarifies the difference between the two.

Default Instance

A default instance is the most common form of an MS SQL Server installation in an SAPenvironment. Typically, one MS SQL Server instance is installed together with a single SAP database.In this configuration, all MS SQL Server components and functionality are exclusively availablefor the SAP database.In a less frequently implemented configuration, a single MS SQL Server instance is installed togetherwith more than one SAP database on the same computer. In this type of configuration, the MS SQLServer components such as executables, system databases and utilities exist only once and have to beshared by all SAP databases. As all the databases on the computer have to be managed with a single

136/208 PUBLIC 08/31/2007

6 Additional Information6.2 Installation of Multiple Components in One Database (Optional)

copy of the MS SQL Server, certain administrative tasks on one database cannot be performed inisolation without affecting the other databases.

Note

A default instance is recommended, if you plan to install only one SAP database instance on acomputer.

Named Instance

The advantage of named instances is that you can set up several SAP databases on the same machineand administer each one separately with its own copy of the MS SQL Server. The main components ofthe MS SQL Server are available exclusively for each instance and can be used only by that instance.Only a few resources such as client utilities have to be shared by all the instances because they are onlyinstalled once. During the installation, each named instance is given a name that is the same as theSAP system name, thus enabling a unique assignment of instances to SAP databases.A named instance is recommended, if you plan to install more than one SAP database instance on thesame machine. Several named instances and the default instance can coexist on the same computerand function in isolation of each other.

6.2 Installation of Multiple Components in One Database(Optional)

Caution


You can installmultiple SAP systems in a single database. This is called Multiple Componentsin One Database (MCOD).

Example

You install an SAP NetWeaver central system and an SAP CRM central system in a single database.

MCOD is available with all SAP components. We are releasing this technology on all the majordatabases for the SAP system, in line with our commitment to deliver platform-independentsolutions.Using this technology is as easy as installing a separate component. No extra effort is required becausethe MCOD installation is fully integrated into the standard installation procedure. MCOD is not anadditional installation service. Instead, it is an option of the database instance installation.With MCOD we distinguish two scenarios:

n The installation of an SAP system in a new databasen The installation of an additional SAP system in an existing database

08/31/2007 PUBLIC 137/208

6 Additional Information6.2 Installation of Multiple Components in One Database (Optional)

Prerequisites

n For more information on MCOD and its availability on different platforms, see the SAP ServiceMarketplace at http://service.sap.com/mcod.

n MCOD is released for Unicode installations. A prerequisite is that the MCOD system containsUnicode instances only. SAP does not support mixed solutions.

n Improved sizing requiredIn general, you calculate the CPU usage for an MCOD database by adding up the CPU usage foreach individual SAP system. The same applies to memory resources and disk space.You can size multiple components in one database by sizing each individual component using theSAP Quick Sizer and then adding the requirements together. For more information on the SAPQuick Sizer, see the SAP Service Marketplace at http://service.sap.com/sizing.

Features

n Reduced administration effort

n Consistent system landscape for backup, system copy, administration, and recoveryn Increased security and reduced database failure for multiple SAP systems due to monitoring and

administration of only one databasen Independent upgrade

In an MCOD landscape you can upgrade a single component independently from the othercomponents running in the same database, assuming that the upgraded component runs onthe same database version. However, if you need to restore a backup, be aware that all othercomponents are also affected.

Note

Special MCOD considerations and differences from the standard procedure are listed where relevantin the installation documentation.

Constraints

Recommendation

We strongly recommend that you test MCOD in a test or development system.We recommend that you run MCOD systems in the same context. We do not recommend that youmix test, development, and production systems in the same MCOD.

n In the event of database failure, all SAP systems running on the single database are affected.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 have to perform a homogeneous system copy with R3load instead.

138/208 PUBLIC 08/31/2007

http://service.sap.com/mcod






6 Additional Information6.3 Integration of LDAP Directory Services (Optional)

l De-installing a single component from an MCOD landscape requires some additional steps.You can use a remote connection to SAP support to request help with these tasks. For moreinformation see http://service.sap.com/remoteconnection.

n


MSCS only: You cannot install multiple components in one database with Microsoft ClusterService (MSCS). For more information on MSCS, see High Availability with Microsoft Cluster Service[page 165].End of: HA (MSCS)

n For the first SAP system, make sure that DBSID is the same as for the first SAP system installedin this database.

n For the second SAP system, make sure that you use the same DBSID as for the first SAP system.n As SAPinst turns off database logging during the database load phase of the installation, you need

to plan downtime for all MCOD systems sharing the database.

6.3 Integration of LDAP Directory Services (Optional)

The Active Directory is a Lightweight Directory Access Protocol (LDAP) directory. LDAP is a feature ofWindows 2000 or higher that allows important information within a corporate network to be storedcentrally on a server. The advantage of storing information centrally for the entire network is thatyou have to maintain data only once, thus avoiding redundancy and inconsistency.If an LDAP directory is available in your corporate network, you can configure the SAP system to usethis feature. For example, a correctly configured SAP system can read information from the directoryand also store information there.This section explains the benefits of using the SAP system with the LDAP directory. In addition, itgives an overview of the configuration steps required to use an SAP system with the directory.

Note

The SAP system can interact with the Active Directory using the LDAP protocol, which defines:

n The communication protocol between the SAP system and the directory

n How data in the directory is structured, accessed, or modified

If a directory other than the Active Directory also supports the LDAP protocol, the SAP system cantake advantage of the information stored there. For example, if there is an LDAP directory on a UNIXor Windows server, you can configure the SAP system to use the information available there. In thefollowing text, directories other than the Active Directory that implement the LDAP protocol arecalled generic LDAP directories.

08/31/2007 PUBLIC 139/208





PrerequisitesYou can only configure the SAP system for Active Directory services or other LDAP directories ifthese are already available on the network. As of Windows 2000 or higher, the Active Directoryis automatically available on all domain controllers. A generic LDAP directory is an additionalcomponent that you must install separately on a UNIX or Windows server.

FeaturesIn the SAP environment, you can exploit the information stored in an Active Directory or genericLDAP directory by using:

n SAP Logonn The Microsoft Management Console (MMC)

For more information on the automatic registration of SAP components in LDAP directories andthe benefits of using it in SAP Logon and MMC, see the documentation SAP System Information inDirectory Services on SAP Service Marketplace at http://service.sap.com/msplatforms MicrosoftWindows Server

SAP Logon

Instead of using a fixed list of systems and message servers, you can configure the SAP Logon in thesapmsg.ini configuration file to find SAP systems and their message servers from the directory. Ifyou configure SAP logon to use the LDAP directory, it queries the directory each time Server or Groupselection is chosen to fetch up-to-date information on available SAP systems.To use LDAP operation mode, make sure that the sapmsg.ini file contains the following:[Address]

Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

Distinguish the following cases:

n If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For moreinformation, see the SAP system profile parameter ldap/options.

n You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either ofthe following is true:l The client is not located in the same domain forest as the Active Directoryl The operating system does not have a directory service client (Windows NT and Windows 9X

without installed dsclient).For more information, see the SAP system profile parameter ldap/servers.

n For other directory services, you can use LDAPnode to specify the distinguished name of the SAProot node. For more information, see the SAP system profile parameter ldap/saproot.

140/208 PUBLIC 08/31/2007

http://service.sap.com/msplatforms




MMC

The MMC is a graphical user interface (GUI) for administering and monitoring SAP systems froma central location. If the SAP system has been prepared correctly, the MMC presents and analyzessystem information that it gathers from various sources, including the Active Directory.Integrating the Active Directory as a source of information has advantages for the MMC. It can readsystem information straight from the directory that automatically registers changes to the systemlandscape. As a result, up-to-date information about all SAP application servers, their status, andparameter settings is always available in the MMC.If you need to administer distributed systems, we especially recommend that you use the MMCtogether with Active Directory services. For example, you can simplify administration by using theMMC in a distributed environment that implements the mySAP Business Suite components. You cankeep track of significant events in all of the systems from a single MMC interface. You do not needto manually register changes in the system configuration. Instead, such changes are automaticallyupdated in the directory and subsequently reflected in the MMC.

Configuration Tasks for Active Directory

To enable an SAP system to make use of the features offered by the Active Directory, you mustconfigure the Active Directory so that it can store SAP data.This involves extending the schema for the SAP data types, creating a root container for the storage ofSAP-specific information, and defining accounts that allow directory access. You perform all thesetasks using SAPinst with the option Active Directory Configuration.For more information, see Setting Up the Active Directory Services (Optional) [page 142].

Configuration Tasks for Generic LDAP Directories

To prepare the SAP system to use generic LDAP services, you must perform the following steps:

1. You configure the LDAP directory to store SAP data.This involves extending the directory schema and creating a container for the SAP data.

2. You set up a user with a password on the server where the SAP system is running to permit thesystem to access and modify the LDAP directory.You do this by running the script ldappasswd.

For more information on how to enable interaction between a generic LDAP directory and the SAPsystem, see the documentation SAP System Information in Directory Services in the SAP Service Marketplaceat: http://service.sap.com/msplatforms Microsoft Windows Server

More Information

Setting Up the Active Directory Services [page 142].

08/31/2007 PUBLIC 141/208




6 Additional Information6.4 Setting Up the Active Directory Services (Optional)

6.4 Setting Up the Active Directory Services (Optional)

This section only applies if you decided to use LDAP directory services. It describes how to set up theActive Directory for your SAP system, as well as to enable the LDAP connection for the applicationserver(s).

PrerequisitesAWindows domain controller with an Active Directory is installed on the network.

Preparing the Active DirectoryIf you want to use LDAP directory services, you need to prepare the Active Directory. The SAP systemcan then use the Active Directory to store and access data.To prepare the directory, you use SAPinst to automatically:

n Extend the Active Directory schema to include the SAP-specific data typesn Create the domain accounts required to enable the SAP system to access and modify the Active

Directory. These are the group SAP_LDAP and the user sapldap.n Create the root container where information related to SAP is stored

n Control access to the container for SAP data by giving members of the SAP_LDAP group permissionto read and write to the directory

Note

For more information on how to set up a Netscape / iPlanet directory server, see thedocumentation SAP System Information in Directory Services on SAP Service Marketplace athttp://service.sap.com/msplatforms Microsoft Windows Server

Perform the following steps:

1. Log on as user with domain administrators rights.2. Run SAPinst and choose <SAP System> Additional Software Life-Cycle Tasks Additional Preparation

Tasks Active Directory Configuration .3. Follow the instructions in the SAPinst dialogs and enter the required parameters.

Note

n When you are prompted for the password of the sapldap user, and this user does not yet exist,make sure that the password consists of at least 5 characters.

n For more information about the input parameters, position the cursor in the field of therespective parameter and press the F1 key.

When you have made these entries, SAPinst extends the Active Directory schema for the SAPsystem.

142/208 PUBLIC 08/31/2007




6 Additional Information6.5 Preparing User Management for an External ABAP System

Enabling the LDAP Connection for the Application ServerTo use LDAP directory services, you must enable the LDAP connection after you have installed theapplication server(s) for your SAP system(s).

Note

You must have extended the LDAP schema for the SAP data types before, as described above.

1. On each application server host, run SAPinst and choose <SAP System> Additional SoftwareLife-Cycle Tasks Application Server LDAP Support .


Note

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

6.5 Preparing User Management for an External ABAP System

For a Java system, you can also deploy user management for an external ABAP system. In this case,you configure the User Management Engine (UME) of the J2EE Engine for the user managementof a separate ABAP system.If you want to connect more than one Java system to the same ABAP system, you need to work out aconcept for the communication, administrator, and guest users for each engine.You can take one of the following approaches:

Approach Advantages Disadvantages

Each Java system uses differentusers

No interdependencies between theconnected engines

Initially more administration tocreate the users in the ABAP system

All Java systems use the sameconfiguration

You create the users only once andenter the same information forevery Java system that you install.

Interdependencies between theconnected engines:n If you change the password of

any of the users on the ABAPsystem, this change affects allconnected engines.

n If you change the administratoruser’s password, you must alsochange the password in securestorage on all of the connectedJ2EE Engines

Recommendation

For security reasons, we recommend the first approach.

08/31/2007 PUBLIC 143/208


The procedures below assume that you are using the first approach.

Prerequisites

n The ABAP system is based on at least SAP Web AS ABAP release 6.20 SP25.n In transaction PFCG, check that the roles SAP_BC_JSF_COMMUNICATION and

SAP_BC_JSF_COMMUNICATION_RO exist and make sure that their profiles are generated.n In transaction PFCG, check that the roles SAP_J2EE_ADMIN, SAP_J2EE_GUEST and SAP_BC_FP_ICF

exist. Neither role contains any ABAP permissions, so you do not need to generate any profiles.n In transaction PFCG, create a role named ADSCallers. You do not need to maintain authorization

data or generate any profiles for that role.n For more information, see:

http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability SecurityIdentity Management User Management Engine

Note

For more information about role maintenance, see the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Security

Identity Management Users and Roles (BC-SEC-USR) SAP Authorization Concept Organizing AuthorizationAdministration Organization if You Are Using the Profile Generator Role Maintenance Role MaintenanceFunctions Changing Standard Roles

Administration of the ABAP systemPerform the following administration steps in the ABAP system:

1. In transaction SU01 create a new communication user and assign it to the roleSAP_BC_JSF_COMMUNICATION_RO.

Recommendation

We recommend that you assign this user the role SAP_BC_JSF_COMMUNICATION_RO for read-only(display) access to user data with Java tools. If you intend to maintain user data (that is, to change,create, or delete users) with Java tools, you need to assign the role SAP_BC_JSF_COMMUNICATIONinstead.We recommend that you name the user SAPJSF_<SAPSID_Java_System>.You can use any password.

In addition, to make sure that this user can only be used for communication connections betweensystems and not as a dialog user, assign it the type Communications under Logon data.

2. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_ADMIN. This is youradministrator user in the J2EE Engine.

144/208 PUBLIC 08/31/2007








Recommendation

We recommend that you name the user J2EE_ADM_<SAPSID_Java_System>. You can use anypassword.

Caution

Log on to the SAP system once with this user to change its initial password. Because the installerof the J2EE Engine verifies this password, the installation fails if this password is initial

3. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_GUEST. This is yourguest user in the J2EE Engine.

Recommendation

We recommend that you name the user J2EE_GST_<SAPSID_Java_System>. You can use anypassword.As this user is only used for anonymous access to the system, we recommend you to deactivatethe password and, if required, lock it after installation to prevent anyone from using it for explicitnamed logons.

4. In transaction SU01 create the following dialog users :

Caution

Youmust have changed the initial passwords [page 124] of these users before you start the installation ofthe Java system.

n Users for Adobe Document Services (ADS) (optional):l ADSUSER:

In transaction PFCG, assign the role ADSCallers to this user.l ADS_AGENT:

In transaction PFCG, assign the role SAP_BC_FP_ICF to this user.n SLD Data supplier user (optional):

You only have to create this user if you want to install System Landscape Directory (SLD).The SLD data supplier user name that you enter later on during the Java system installationmust be identical to this user.

Recommendation

We recommend that you name this user SLDDSUSER

n SLD ABAP API user (optional):You only have to create this user if you want to install System Landscape Directory (SLD). TheSLD ABAP API user name that you enter later on during the Java system installation must beidentical to this user.

08/31/2007 PUBLIC 145/208

6 Additional Information6.6 Configuring User Management to Use an LDAP Directory (Optional)

Recommendation

We recommend that you name this user SLDAPIUSER

Note

For more information on SLD users and security roles, see the Post-Installation Guide - SLD of SAPNetWeaver 7.0 at http://service.sap.com/sld Media Library .

Activities for the Java SystemPerform the following steps in the Java system:

1. Before the installation of the Java system, make sure that you have the correct user names andpasswords of the users listed above for the separate ABAP system.

2. During the installation of the Java system, make sure that you enter the correct users andpasswords in the corresponding SAPinst dialogs.

6.6 Configuring User Management to Use an LDAP Directory(Optional)

If your user data source is an LDAP directory, you need to configure the connection to the LDAPdirectory after installation.For more information, see:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Security

Identity Management User Management Engine UME Configuration UME Data Sources LDAP Directory asData Source Configuring UME to Use an LDAP Server as Data Source

6.7 Usage Type-Specific Initial Technical Configuration

SAPinst performs initial technical configuration steps for the usage types shown below during theinstallation. However, you might have to perform some of these steps manually after SAPinst hasfinished, depending on your installation scenario. The following usage type-specific sections providethe required information:

n Application Server Java (AS Java) [page 147]n Development Infrastructure (DI) [page 149]

n


EP Core (EPC) and Enterprise Portal (EP) [page 149]End of: Enterprise Portal (EP);EP Core (EPC)

146/208 PUBLIC 08/31/2007







6 Additional Information6.7 Usage Type-Specific Initial Technical Configuration

n


Business Intelligence (BI Java) [page 153]End of: BI Java Components (BI-Java)

n


Process Integration (PI) [page 150]End of: Process Integration (PI)

6.7.1 Initial Technical Configuration for Application Server

SAPinst performs initial technical configuration steps for the AS Java functional units listed belowduring the installation.However, you might have to perform some of these steps manually after SAPinst has finished,depending on your installation scenario.For more information, see the following functional unit-specific sections:

n Adobe Document Services (ADS) [page 147]n Composite Application Framework (CAF) [page 148]n Connection to System Landscape Directory (SLD) [page 148]

6.7.1.1 Initial Technical Configuration for Adobe DocumentServices

SAPinst automatically performs initial technical configuration steps specific to Adobe DocumentServices (ADS) during the installation.However, you have to perform some of these steps manually if:

n You have installed AS Java on a separate host and want to use ADS for a standalone ABAP system.n You want to change existing parameters or you want to set additional parameters.

FeaturesDepending on your installation scenario, you might have to perform one ore more of the followingsteps:

n Create user ADSUser for basic authentication.

n Create service user ADS_AGENT in the ABAP environmentn Create a web service destination

n Create an HTTP destination for ADS.

n Create an RFC destination for ADS.

You can find a detailed description of the manual procedure for these steps in section Configuring theWeb Service in the Adobe Document Services Configuration Guide, which you can find:

08/31/2007 PUBLIC 147/208


n On SAP Service Marketplace at:http://service.sap.com/adobe SAP Interactive Forms by Adobe Media Library Documentation

Adobe Document Services - Configuration Guide NetWeaver 7.0

n In the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’s Guide Cross-NetWeaver

Configurations Adobe Document Services - Configuration .

6.7.1.2 Initial Technical Configuration for CompositeApplication Framework Core

During the installation, SAPinst automatically performs initial technical configuration steps specificto the Composite Application Framework Core (CAF). However, you have to perform some of thesesteps manually if you want to change existing parameters or you want to set additional parameters.Depending on your installation scenario, you might have to perform the following steps:

n Creating roles CAFAdmin and CAFUIAdmin

n Setting configuration parameters

For more information about your installation scenario and the steps you have to perform, see theSAP Library at: http://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’s GuideDeveloping, Configuring, and Adapting Applications Creating Composite Applications Composite ApplicationFramework Core Configuration Guide

6.7.1.3 Configuring System Landscape Directory

SAPinst automatically configures the connection for System Landscape Directory according to theparameters you entered on the related SAPinst screens during the input phase of the installation.However, you have to perform some of these steps manually if you want to change existing parametersor if you want to set additional parameters.You can now configure your SAP System for SLD as follows:

n As an SLD server (and client)n As an SLD client

For more information, see:

148/208 PUBLIC 08/31/2007











6.7.2 Initial Technical Configuration for DevelopmentInfrastructure (DI)

During the installation, SAPinst automatically performs initial technical configuration steps specificto the usage type Development Infrastructure (DI). However, you have to perform some of thesesteps manually if

n you want to change existing parameters orn you want to set additional parameters orn you do not want to use the Configuration Wizard [page 127].

Depending on your installation scenario, you might have to perform the following steps:

n Configure Database and J2EE Engine for the usage type DI.n Set Up Privileges, Roles, and Groups for the usage type DIn Set Up System Landscape Directory and Name Servicen Configure the Component Build Servicen Prepare the Change Management Service

More InformationFor more information about your installation scenario and the steps you have to perform, see theSAP Library at: http://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’s GuideDeveloping, Configuring, and Adapting Applications Template-Based Basic Configuration of Usage Type DI


6.7.3 Initial Technical Configuration for the Portal

This section applies when you install usage type EPC only and when you install it together withusage type EP.SAPinst automatically performs initial technical configuration steps that are specific for usage typeEPC and EP during the installation.However, you might have to perform some of these steps manually if:

n You have installed usage type EPC or EPC and EP as an additional usage type to an existing SAPsystem as described in SAP Note 883948.

n You want to change existing parameters or if you want to set additional parameters.

The following steps might be affected:

n Copying CMS_MAPPING Properties

n Renaming InitialPermissions.xml.templaten Renaming initialPermissionsKMC.xml.template

08/31/2007 PUBLIC 149/208






Copying CMS_MAPPING Properties

1. Change to the following source directory<drive:>\usr\sap\<sapsid>\<instance_name>\j2ee\cluster\server<x>\apps\sap.com\irj\

servlet_jsp\irj\root\WEB-INF\portal\system\pcd\Migration\mapping\

2. Copy filecms_mapping.properties from the source directory to the following target directory:<drive:>\usr\sap\<sapsid>\SYS\global\pcd\Migration\mapping\.

Note

If the target directory does not exist, you have to create it as well.

Renaming InitialPermissions.xml.template

1. Go to directory<drive:>\usr\sap\<sapsid>\<instance_name>\j2ee\cluster\server<x>\apps\sap.com\irj\

servlet_jsp\irj\root\WEB-INF\portal\system\xml\acl .2. Rename file initialPermissions.xml.template to initialPermissions.xml.

Renaming initialPermissionsKMC.xml.template

1. Go to directory<drive:>\usr\sap\<sapsid>\<instance_name>\j2ee\cluster\server<x>\apps\sap.com\irj\

servlet_jsp\irj\root\WEB-INF\portal\system\xml\acl

2. Rename file initialPermissionsKMC.xml.template to initialPermissionsKMC.xml.

End of: Enterprise Portal (EP);EP Core (EPC)


6.7.4 Initial Technical Configuration for Process Integration(PI)

SAPinst automatically performs PI-specific initial technical configuration steps during the installation.However, you might have to perform some of these steps manually if:

n You upgraded your SAP system to NetWeaver 7.0 SR2.n You have installed usage type PI as an additional usage type to an existing SAP system as described

in SAP Note 883948.


n Import the SAP Exchange profile [page 151]n Assign SAP_ALL Rights to User PISUPER [page 152]n Activate the ICF Services [page 152]n Assign roles to groups [page 152]

150/208 PUBLIC 08/31/2007



n Run the configuration template installer for usage type PI [page 127]

6.7.4.1 Importing the SAP Exchange Profile

Note

If SAPinst has finished successfully, the exchange_profile.xml file does not exist on your system.In this case, you can skip this step.

Procedure

1. On your PI server host, open the following URL:http://<J2EE_host>:<J2EE_Port>/exchangeProfile

The following naming convention applies for <J2EE_Port>:5<J2EE_instance_number>00

50000, for example, if your J2EE instance is 002. Enter the logon information:

User Name: PISUPERPassword: <pisuper_password>The Exchange Profile page appears

3. Choose Connection.The Server Settings page appears.

4. Enter the required information for the PI host.Use the logon information of user PILDUSER.

5. Choose Save.The Exchange Profile page appears.

6. Choose Import.The Import Profile page appears.

7. Choose Browse and select the following file:\usr\sap\<SAPSID>\SYS\global\exchange_profile.xml

Caution

If you cannot run aWeb Browser on your PI host, you need to copy the file exchange_profile.xmlfrom the PI host to a host were a Web browser runs.

8. Choose Import Data.The profile will be imported.

08/31/2007 PUBLIC 151/208


Caution

As the file exchange_profile.xml contains secure information like passwords, we highlyrecommend that you delete the file after importing or to save it by using high security standards,such as encryption.

6.7.4.2 Assigning SAP_ALL Rights to User PISUPER

1. Log on to your SAP NetWeaver AS ABAP host as user with SAP_ALL rights (use DDIC or SAP*).2. Call transaction SU01.3. Select user PISUPER.4. Navigate to the Profiles tab and switch to edit mode.5. In the row Profile, add SAP_ALL.6. Save your settings.

6.7.4.3 Activating the ICF Services

The Internet Communication Framework (ICF) is a HTTP framework that provides an ABAPinterface for HTTP requests. Via ICF services, the SAP Web Application Server can use the HTTPprotocol for remote communication as client and as server.

ProcedureTo activate the ICF services, call transaction SE38 and execute the reportRSXMB_ACTIVATE_ICF_SERVICES. For more information, see SAP Note 736312.

6.7.4.4 Assigning Roles to Groups

To assign the roles to the different groups, start the Visual Administrator of the J2EE Engine.

Assigning Role "Administer" to Group SAP_XI_ADMINISTRATORCheck whether group SAP_XI_ADMINISTRATOR is assigned to role administer.If this is not the case, proceed as follows:

1. Choose Cluster Server Services Security Provider sap.com.\com.sap.rprof.remoteprofileexchangeprofile .2. Select Security Roles.3. Select Administer.4. Select the group SAP_XI_ADMINISTRATOR.5. Choose Add and assign the role administer.

152/208 PUBLIC 08/31/2007



6. Save your settings.

Assigning Security Role "LcrAdministrator" to GroupSAP_SLD_ADMINISTRATOR

1. Choose Cluster Server Services Security Provider .2. On the Runtime tab in the right frame, choose Policy Configuration Component .3. Select sap.com/com.sap.lcr*sld.4. On the right, choose Security Roles and select the role LcrAdministrator.5. Select the role type Security Role.6. In the lower frame, add group SAP_SLD_ADMINISTRATOR.



6.7.5 Initial Technical Configuration for BI Java

SAPinst automatically performs BI Java-specific initial technical configuration steps during theinstallation.However, you might have to perform some of these steps manually if:

n You upgraded your SAP system to NetWeaver 7.0 SR2.n You have installed usage type BI Java as an additional usage type to an existing SAP system as

described in SAP Note 883948.


n Configure BI Java Information Broadcasting [page 153]n Process Chains: Transport texts for alert category [page 154]n Rename initialPermissionsBI.xml.template [page 154]n Run the configuration template installer for usage type BI Java [page 127]

6.7.5.1 Configuring BI Java Information Broadcasting

For the configuration of the BI Information Broadcasting you need to performt the following stepsin your ABAP system:

1. Call transaction SPRO and perform the following steps:a) Settings for Information Broadcasting:

Go to SAP NetWeaver Business Intelligence Reporting-relevant Settings Settings for InformationBroadcasting

b) Destinations for Web Dynpro ALV:

08/31/2007 PUBLIC 153/208



Go to SAP NetWeaver Application Server Web Dynpro for ABAP Set-Up Printing for Web DynproABAP ALV

n Create RFC destination in the SAP NetWeaver Portal

n Create RFC destination to the SAP NetWeaver Portal

n Set-Up Web Service destination for the Adobe Document Services2. Installation of BI Content:

Call transaction RSTCO_ADMIN to check whether the installation has been carried out successfully.If the installation status is red, restart the installation by calling transaction RSTCO_ADMIN again.Check the installation log if you need further assistance or information.For more information, see SAP Note 834280.

Note

For the installation of SAP NetWeaver 7.0 BI Content Add-On 2 or higher on the AS ABAP system,see SAP Note 847019.

6.7.5.2 Process Chains: Transporting Texts for the AlertCategory

Alerts can be triggered and sent for BI process chains that contain errors. Defining the alert categoriesis necessary for this purpose. Alert category BWAC_PROCESS_CHAIN_FRAMEWORK is returned for errorsin background processing of process chains. This category has set texts that are not transportedwhen the alert category is transported.

ProcedureTo manually transport the texts, see SAP Note 601619.

6.7.5.3 Renaming initialPermissionsBI.xml.template

If SAPinst does not rename the initialPermissionsBI.xml.template file automatically, you willneed to rename it yourself.

Procedure

1. Go to directory<drive:>\usr\sap\<sapsid>\JCxx\j2ee\cluster\server<x>\apps\sap.com\irj\

servlet_jsp\irj\root\WEB-INF\portal\system\xml\acl

2. Rename file initialPermissionsBI.xml.template to initialPermissionsBI.xml.

End of: BI Java Components (BI-Java)

154/208 PUBLIC 08/31/2007




6 Additional Information6.8 Deleting an SAP System

6.8 Deleting an SAP System

The following sections describe how to delete a single instance, a standalone engine or a completeSAP system with SAPinst.To delete your system, you use the SAPinst service <SAP System> Additional Software Life-Cycle TasksUninstall Uninstall System / Standalone Engine / Optional Standalone Unit .

Note

This description assumes that you have installed your SAP system with standard SAP tools accordingto the installation documentation.

Caution

n Make sure that all remaining instances are stopped before you delete the database instance.

n You cannot delete an SAP system remotely.

n SAPinst deletes the database instance but you have to delete the database software manually.

n If you delete network-wide users, groups or service entries in an environment with NetworkInformation System (NIS), other SAP installations might also be affected. Make sure that theusers, groups, and service entries to be deleted are no longer required.

Process Flow

n If you want to delete a central system, where all SAP instances reside on the same host, you cando this in one SAPinst run [page 156].

Note

SAPinst deletes the database instance but you have to delete the MS SQL Server database softwarewith the SQL Server Uninstaller, which you can find on Windows under Add/Remove Programs.

n If you want to delete a distributed system, where the SAP instances reside on different hosts,you have to run SAPinst [page 156] to delete the required instances locally on each host in thefollowing sequence:1. You delete the dialog instance(s), if there are any.2. You delete the database instance.3. You delete the central instance.4. You delete the central services instance.

5.


You delete the ABAP central services instance.End of: HA (MSCS)

6. You delete the MS SQL Server database software with the SQL Server Uninstaller, which youfind on Windows under Add/Remove Programs

08/31/2007 PUBLIC 155/208

6 Additional Information6.8 Deleting an SAP System

6.8.1 Running SAPinst to Delete an SAP System

This procedure tells you how to run the Uninstall service of SAPinst.

PrerequisitesYou are logged on as a user with the required rights and privileges to run the SAPinst tool and theSAP system. For more information, see Granting User Rights for the Installation [page 56].

Procedure

1. Start SAPinst and on theWelcome screen, choose:<SAP System> Additional Software Life-Cycle Tasks Uninstall Uninstall System / Standalone Engine /

Optional Standalone Unit

Note

With this SAPinst service you do not delete the database software.

2. Follow the instructions in the SAPinst input dialogs.

Note

For more information about the input parameters, place the cursor on the relevant field andpress F1 in SAPinst.

SAPinst first asks you which SAP instances you want to delete.Make sure that you delete the SAP instances in the correct order, as described in Deleting an SAPSystem [page 155].

Caution

n SAPinst only stops local instances automatically.Before you delete the database instance of a distributed system make sure that you stop allremaining instances. You must stop the instance with the message server only after havingentered all SAPinst parameters for the deletion of the database instance.

n If SAPinst stops responding while trying to delete the central instance, close SAPinst withCancel and Exit. Log off and log on again. To complete the uninstall process of the centralinstance, restart SAPinst .

3. Delete the local user group SAP_<SAPSID>_LocalAdminmanually as follows:a) Choose Start Programs Administrative Tools Computer Managementb) Choose Local Users and Groups Groups.c) Right-click the local group SAP_<SAPSID>_LocalAdmin and choose Delete.

4. When you have finished you can delete the MS SQL Server database software using the SQL ServerUninstaller, which you can find on Windows under Add/Remove Programs.

156/208 PUBLIC 08/31/2007

6 Additional Information6.9 SAP System Security on Windows

5. If required, you can delete the directory \usr\sap\trans and its contents manually.SAPinst does not delete \usr\sap\trans because it might be shared.

6.9 SAP System Security on Windows

In a standard SAP system installation, SAPinst automatically performs all steps relevant for security.Although SAPinst makes sure that the system is protected against unauthorized access, you muststill check that no security breaches can occur.For central and straightforward administration of the SAP system, you have to install distributed SAPsystems with multiple application servers in a Windows domain. This section describes the useraccounts and groups that SAPinst creates during a domain installation and shows how these arerelated to the SAP directories.

User Accounts

SAPinst creates the following accounts for SAP system administration:

n <sapsid>adm

This is the SAP system administrator account that enables interactive administration of the system.

n SAPService<SID>

This is the user account that is required to start the SAP system. It has the local user right to logon as a service.

The advantage of the additional SAPService<SAPSID> account is that it does not allow an interactivelogon, which prevents abuse of the account. Therefore, you do not need to set an expiration date forthe password and you do not have to set the option user must change password at next logon.

Groups

SAPinst creates the following groups during a domain installation:

n SAP_<SAPSID>_GlobalAdmin

This global group is a domain-level SAP administration group for organizing SAP systemadministrators. The only function of a global group is to group users at the domain level so thatthey can be placed in the appropriate local groups.

n SAP_<SAPSID>_LocalAdmin

Only local groups are created and maintained on an application server. A local group can only begiven permissions and rights to the system where it is located. The system is part of a particulardomain, and the local group can contain users and global groups from this domain.

n SAP_LocalAdmin

This group is created on all hosts, but is particularly important for the transport host. Members ofthe group have full control over the transport directory (\usr\sap\trans) that allows transports totake place between systems.

08/31/2007 PUBLIC 157/208

6 Additional Information6.9 SAP System Security on Windows

The SAP_<SAPSID>_GlobalAdmin groups of all the SAP systems that are part of the transportinfrastructure are added to the SAP_LocalAdmin group. As a consequence, the users <sapsid>admand SAPService<SAPSID> of all systems in the transport infrastructure are members of theSAP_LocalAdmin group and have the required authorizations necessary to initiate and executetransports.

SAP Directories

SAPinst protects the SAP directories under \usr\sap\<SAPSID> by only granting the groupSAP_<SAPSID>_LocalAdmin full control over these directories.The following graphic illustrates the user accounts and groups created by SAPinst in a systeminfrastructure consisting of two SAP systems.

Figure 9: User Groups and Accounts

Note

An access control list (ACL) controls access to SAP system objects. For maximum security in the SAPsystem, only the following are members of all SAP system object ACLs:

n Local group SAP_<SAPSID>_LocalAdmin

n Group Administrators

158/208 PUBLIC 08/31/2007

6 Additional Information6.10 Automatic Creation of Accounts and Groups

n Account SYSTEM

6.10 Automatic Creation of Accounts and Groups

SAPinst automatically creates the accounts and groups required for the secure operation of the SAP systemwith Windows [page 157] during the installation.

FeaturesThe following figures show the steps that SAPinst performs to create the users and groups and assignthe required rights to SAP directories.

Figure 10: Creating Users and Groups

08/31/2007 PUBLIC 159/208

6 Additional Information6.11 Manually Granting User Rights for the Installation

Figure 11: Assigning Rights to SAP Directories

6.11 Manually Granting User Rights for the Installation

Although the rights required for the installation are automatically granted to the user who installsthe SAPinst tool, you might need to manually grant user rights for the installation to another user,as described in this section.

PrerequisitesThe Windows user that performs the SAP system installation must be authorized to perform theactions necessary for the installation.For a domain installation, this means that the user must belong to the Domain Administrator groupand be authorized to:

n Act as part of the operating systemn Adjust memory quotas for a processn Replace a process-level token

The procedure below assigns these rights to a user of your choice.

160/208 PUBLIC 08/31/2007

6 Additional Information6.12 Troubleshooting

Caution

Be aware that domain policies override locally defined policies. This means that if you want togrant domain administrator rights for a local user, make sure that you have also defined domainadministrator rights for this user on domain level.

Procedure

1. Choose Start Settings Control Panel Administrative Tools Local Security Policy.2. In the Local Security Settings window, choose Local Policies User Rights Assignment.3. Double-click the respective right under Policy and choose Add User or Group.4. In the Select Users and Groups window, choose the required user and choose Add.

The selected user appears in the box below.5. Confirm your entry and then repeat the steps for each remaining policy that the user requires

for the installation.6. Log off and log on again to apply the changes.

More InformationGranting User Rights for the Installation [page 56]

6.12 Troubleshooting

The following section(s) describe the steps that you need to performmanually if SAPinst fails:

n Troubleshooting with SAPinst [page 161]

n


Troubleshooting for Portal Installation [page 162]End of: Enterprise Portal (EP);EP Core (EPC)

6.12.1 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.If an error occurs, SAPinst:

n Stops the installationn Displays a dialog informing you about the error

Procedure

1. To view the log file, choose View Logs.2. If an error occurs during the dialog or processing phase, do either of the following:n Try to solve the problem

08/31/2007 PUBLIC 161/208


n Abort the installation with ExitFor more information, see Interrupted Installation with SAPinst [page 90].

n Continue the installation by choosing Retry.3. Check the log and trace files of the GUI server and SAPinst GUI in the directory

%userprofile%\.sdtgui\ for errors.4. If SAPinst GUI does not start, check the file sdtstart.err in the current %userprofile% directory.5. If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as

described in Starting SAPinst GUI Separately.6. Ignore error messages in the SDM logs that state that software components are not available.

For more information, see SAP Note 828978.


6.12.2 Troubleshooting for Portal Installation

This section applies both when you install usage type EPC only and when you install it togetherwith usage type EP.If the iViews are not displayed correctly, or if the portal does not launch, the reason might be that theportal was not deployed completely.To check the deployment of the portal, proceed as follows :

Procedure

1. Open a new console with the user <sapsid>adm.2. Go to the directories deployment, pcd, and pcdContent, in the following paths:

n <drive>:\usr\sap\<SAPSID>\DVEBMGS<instance_number>\j2ee\cluster\server0\

apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment


apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd


apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcdContent


apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcdContent\no_overwrite

3. Look for files with the extension *.err.4. Do one of the following:n If error and log files do not appear, the portal installation has been completed successfully

and you can continue.n Rename the *.err files:

a) Remove the err extension; so the extensions of the files become *.ept or *.par.

162/208 PUBLIC 08/31/2007



b) Restart the J2EE Engine, using the commands stopsap and startsap, to change the filesto *.bak.

End of: Enterprise Portal (EP);EP Core (EPC)

08/31/2007 PUBLIC 163/208

7 High Availability with Microsoft Cluster Service


7 High Availability with Microsoft ClusterService

You can install a high-availability SAP system with Microsoft Cluster Service (MSCS). For this type ofinstallation, you have to set up the system and configure it so that it can take advantage of the MSCSsoftware. The MSCS software improves the availability of the system and safeguards it against failureand unplanned downtime, enabling 24-hour operation, 365 days a year.With high availability you enable critical system components, so-called Single Points of Failure (SPOFs)to be automatically switched from one machine to the other, if hardware or software problems ariseon one machine. With the help of this switchover ‒ or failover ‒ the system can continue functioningnormally so that unplanned system downtime is avoided.Apart from enabling failover when hardware problems occur, you can also use MSCS to avoiddowntime when you perform essential system maintenance. If you need to maintain one host(MSCS node), you can deliberately switch the cluster resources to the other host (MSCS node) andtemporarily operate it there while maintenance is in progress. When maintenance work is finishedyou can easily move the resources back to their original node and continue operating them there.You have the following options to install a high-availability system with MSCS:

n You install one SAP system in oneMSCS cluster.n You install one SAP system in twoMSCS clusters.

In both cases the following restrictions apply:

n You must install the (A)SCS instance on two MSCS nodes in one MSCS cluster.n If your database supports the installation on several MSCS nodes, you can install the database

instance on more than two MSCS nodes in one MSCS cluster.

Note

n Make sure that you read SAP Note 967123, which contains the most recent information as wellas corrections for a high-availability installation. For more information, see the SAP installationnotes [page 15] before you begin the installation.

n In this documentation the hosts in an MSCS cluster are referred to as first MSCS node andadditional MSCS node(s).

n When you are setting up the SAP system with MSCS, you combine standard installation steps,described earlier in this documentation, with cluster-specific steps, described here.

08/31/2007 PUBLIC 165/208


7 High Availability with Microsoft Cluster Service7.1 Planning

To install a new SAP systemwithMSCS, you have to perform a number of extra steps specially requiredfor 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.n Since the cluster hardware has at least two nodes that have access to all local and shared storage

devices, you have to install some components on all nodes and observe special rules for distributingcomponents to local or shared disks.

n Since the correct configuration of network addresses is absolutely essential to enable the clusterto function properly, you have to perform a number of additional steps that are necessary toset up and check addressing.

Note

If you have an existing SAP system and plan to migrate to a cluster with new hardware, you installthe SAP system using a system copy. Therefore, you have to prepare for the installation by creatinga homogeneous or a heterogeneous copy of the database. After you have created a copy of thedatabase, you can install your system with MSCS. However, instead of loading the database from theExport DVDs in the installation package, you load it using your exported database.For more information about a homogeneous or heterogeneous system copy, see the documentationHomogeneous and Heterogeneous System Copy for SAP Systems based on SAP NetWeaver on SAP Service Marketplaceat http://service.sap.com/instguidesnw70 Installation . In addition, for more informationabout a heterogeneous system copy, see http://service.sap.com/osdbmigration.The documentation for a homogeneous or heterogeneous system copy does not include thecluster-specific information, which is described here.

7.1 Planning

You have to complete the following planning activities for you SAP system using Microsoft ClusterService (MSCS):

1. You decide how to set up your SAP system components in an MSCS configuration [page 166].2. You install an enqueue replication server [page 170].3. You distribute components to disks for MSCS [page 171].4. You read chapter Directories in an MSCS Configuration [page 173]5. You read chapter IP Addresses in an MSCS Configuration [page 173]6. You obtain IP addresses for MSCS [page 177].

7.1.1 SAP System Components in an MSCS Configuration

In an MSCS configuration you have the following components for your SAP system:

166/208 PUBLIC 08/31/2007




http://service.sap.com/osdbmigration




SAP System Components in an MSCS Configuration

ComponentNumber of Components per SAPSystem Single Point of Failure (SPOF)

SCS instance (message services andenqueue services)

1 yes

ASCS instance (message servicesand enqueue services)

1 yes

Database instance 1 yes

Application server (centralinstance, dialog instance)

1-n no

n To protect the SPOFs ((A)SCS instance, database instance) you have to use MSCS.If a hardware or software problem occurs on the first MSCS node, the clustered (A)SCS instanceand the clustered database automatically fail over to the other node.If you need to maintain the MSCS node where the (A)SCS instance and database are running youcan switch these instances to the other node. When maintenance work is finished you move the(A)SCS and database instance back to the original node.

n To protect system components that are non-SPOFs, for example application servers, you haveto install them as multiple components. In this case you must install at least two applicationservers (one central instance and at least one dialog instance) on two different hosts. You havethe following options:l You install the central instance and the dialog instance on the MSCS nodes of an MSCS cluster.

You install them on a local disk. Any additional dialog instances are installed on hosts outsideof the MSCS cluster.If you have to maintain an MSCS node, you have to stop the central or dialog instance on thatnode. When you have finished maintenance, you restart the instance(s).

Note

If you install the central instance and the dialog instance on the MSCS cluster nodes you mustperform the hardware sizing, as in this case the application server is always running on theMSCS host, contrary to the (A)SCS and database instance which may also run there in case offailover. This might increase system load and affects performance.

l You install the central instance and all dialog instances on hosts, which are not part of anMS cluster.

The following figures show examples for the installation of SPOFs and non-SPOFs of an SAP systemin an MSCS cluster with two nodes.

08/31/2007 PUBLIC 167/208


The first figure shows an MSCS configuration where the non-SPOFs components (central instance,dialog instance) are installed locally on the MSCS nodes. Any additional dialog instance(s) areinstalled outside the MSCS cluster on separate hosts.

Figure 12: ABAP+Java System with SPOFs, where non-SPOFs are installed locally on the MSCSCluster Nodes

The following figure shows an MSCS configuration, where the non-SPOFs components (centralinstance, dialog instance) are installed on separate hosts that are not part of the MS cluster.

168/208 PUBLIC 08/31/2007


Figure 13: ABAP+Java System where the non-SPOFs are installed on hosts outside of the MS Cluster

Installing the SAP System on Two MSCS Clusters

Besides installing your SAP system within one MSCS cluster, you can also set up two MSCS clustersand distribute the SPOF system components on these clusters to protect them against system failure.The following figure shows an example where the database instance for the SAP system is installed inone MSCS cluster, and the (A)SCS instance is installed on the second MSCS cluster. The applicationservers (central and dialog instance) can either be installed on a local disk on the MSCS nodes or onseparate hosts that are not part of the MS cluster.

08/31/2007 PUBLIC 169/208


Figure 14: ABAP+Java System

7.1.2 Enqueue Replication Server in an MSCS Configuration

For this type of installation, you install an enqueue replication server on allMSCS nodes where theJava central services (SCS) instance and the ABAP central services (ASCS) instance are installed.The enqueue replication server contains a replica of the lock table (replication table).In normal operation the replication enqueue server is always active on the host where the SCSand ASCS instance are not running.If an enqueue server in an MSCS cluster with two nodes fails on the first MSCS node, the enqueueserver fails over to the second MSCS node and starts there. It retrieves the data from the replicationtable on that node and writes it in its lock table. The enqueue replication server on the second MSCSnode then becomes inactive. If the first MSCS node is available again, the enqueue replication serveron the second MSCS node becomes active again.The following figure shows the enqueue replication server mechanism in an MSCS configurationwith two nodes:

170/208 PUBLIC 08/31/2007


Figure 15: Enqueue Replication Server Mechanism on One MSCS Cluster with Two Nodes

7.1.3 Distribution of Components to Disks for MSCS

One of the central points to keep in mind when planning the MSCS installation is that the clusterhardware 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

Note

Shared disk is a synonym for the MSCS resource of Resource type Physical disk.

You need to install the SAP system components in both the following ways:

n Separately on all MSCS nodes to use the local storage on each node.n On the shared storage that is used in common by all MSCS nodes.

You install the following on different shared disks:l Database instance

l (A)SCS instancel Single quorum device, if used

With Windows Server 2003, you can now choose between the following cluster models:

n Single Quorum Device Cluster

08/31/2007 PUBLIC 171/208


In this cluster model the quorum resource maintains the cluster configuration data on a singlecluster storage device.The quorum resource is unique to a cluster installation and is always owned by one of the nodes.It has the following main functions in the cluster:l It logs changes to the cluster configuration that are entered in the Registry.l It arbitrates between competing nodes when the communication between nodes breaks down.

This means that cluster resources are forced to fail over to the node that owns the quorumresource.

n Majority Node Set ClusterIn this new cluster model, each node maintains its own copy of the cluster configuration data.The Majority Node Set resource, acting as the Quorum Resource, ensures that the clusterconfiguration data is kept consistent across the different nodes.You can use majority node set for geographically dispersed cluster configuration.SAP supports Majority Node Set Cluster if it is part of a cluster solution offered by your OriginalEquipment Manufacturer (OEM), or Independent Hardware Vendor (IHV).

The following figures show a cluster configuration, where the (A)SCS and DB instance are installed inthe same cluster. It illustrates how to distribute the database data files, the SAP system executables,and the quorum resource (if used) to different disks. Only with this distribution of files to distinctdisks is it possible to move the SAP system and database as separate entities in a failover situation.

Figure 16: Distribution of SAP System Components in MSCS

172/208 PUBLIC 08/31/2007


More InformationDirectories in an MSCS Configuration [page 173]

7.1.4 Directories in an MSCS Configuration

The following tables show the directories where the main software components for the SAP clusterinstallation are stored:

Directories on Local Disks on MSCS Nodes

Component Default Directory

A supported operating system [page 180] %windir%

MSCS software %windir%\Cluster

SAP cluster files %windir%\SAPCluster

Directories on Shared Disks

Component Default Directory

Cluster quorum resource <drive>:\MSCS

SAP global and instance directories <drive>:\usr\sap ...

tempdb databases <drive>:\TEMPDB

msdb, model, master <drive>:\mssql

SAP data files <drive>:\<SAPSID>DATA1

<drive>:\<SAPSID>DATA2

<drive>:\<SAPSID>DATA3

SapCluster Directory

In an SAP cluster installation, an additional directory ‒ %WINDIR%\SapCluster ‒ is created underthe system directory.This contains all the SAP files required by all MSCS cluster nodes, independently of the MSCS nodethe SAP instance is running on. The files are database tools and program files (executables) usedby the operating system monitor (SAPOsCol).The directory is added to the path variable of the user <sapsid>adm.

7.1.5 IP Addresses in an MSCS Configuration

A part of the installation process that is unique to MSCS is the configuration of host names and IPaddresses in the network. This is a particularly important task because the addressing plays a key

08/31/2007 PUBLIC 173/208


role in the switchover procedure. Addressing must be set up correctly so that the system can takeadvantage of the cluster functionality and switch between nodes when hardware problems arise.This section explains the different types of IP addresses and their function in the switchovermechanism of an MSCS cluster with two nodes.

Types of IP Addresses

In a correctly configured cluster with two nodes, there are seven IP addresses and corresponding hostnames for your SAP system. You have two IP addresses for each MSCS node, one IP address for thecluster, one address for the SAP cluster group and one for the database cluster group.Some of the addresses are assigned to the network adapters (cards), others are virtual IP addressesthat are assigned to the cluster groups.

Physical IP Addresses Assigned to Network Adapters

An MSCS configuration usually has two networks:

n A public network that is used for the communication between the central instance, applicationservers and the LAN.

n A private network that is used internally for communication between the nodes of the cluster.

Note

For more information on network configuration, see also the Microsoft Knowledge Base Article259267.

The following figure shows an MSCS cluster with two nodes and illustrates the adapters required forthe public and private networks, and their corresponding physical IP addresses. A physical IP address,as opposed to a virtual one, is stationary and permanently mapped to the same adapter.

174/208 PUBLIC 08/31/2007


Figure 17: Adapters and IP Addresses Required for Public and Private Networks in an MSCS Clusterwith Two Nodes

Host Names Assigned to Network Adapters

Each of the physical IP addresses of the network adapters must have a corresponding host name. Forexample, on the left-hand node in the figure above, you might assign the IP addresses of the publicand private network adapters as follows:

IP Addresses and Host Names

Network Adapter IP Address Host Name

Adapter 1 (private network) 10.1.1.1 clusA_priv

Adapter 3 ( public network) 129.20.5.1 clusA

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 ofthe machine. In our example, this means that the machine that is the MSCS node on the leftin the figure has the name clus1.

n Do not confuse the host name with the computer name. Each node also has a computername, which is often the same as the host name.The computer name is displayed in the node column of the Cluster Administrator. However, itis not required for the TCP/IP communication in the cluster. When you configure IP addresses

08/31/2007 PUBLIC 175/208


and corresponding names, keep in mind that it is the host names that are important for thecluster, not the computer names.

Virtual IP Addresses Assigned to Cluster Groups

When you have installed the SAP system and fully configured the cluster, the critical system resourcesare bound together in three different groups. Each of these groups requires a virtual IP address andhost name that is permanently mapped to the group and not to a particular node. This has theadvantage that, whenever a group is moved between nodes, its IP address and host name movetogether with it.A cluster configuration has the following groups:

n SAP cluster groupn Database cluster groupn Cluster group

Each group consists of a set of related resources that work together to offer a service to the system.For example, the database cluster group comprises all the resources that enable the database server tofulfill the requests of a client. When the group is moved from one node to the other, due to nodefailure, the virtual IP address and host name move with it. Therefore, there is a failover not only ofresources, but also of the virtual IP address and host name. As a result, all clients can still reach thedatabase server with the same IP address as before.The following figure illustrates how the virtual IP addresses of the database group and SAP group canmove from one node to the other when failover occurs.

Figure 18: Failover of Virtual IP Addresses

176/208 PUBLIC 08/31/2007


7.1.6 Obtaining IP Addresses for MSCS

You need to correctly configure IP addresses for a cluster system. During the installation procedureyou have to assign at least seven IP addresses and host names. You normally obtain these namesand addresses from the system administrator.

Prerequisites

n If you are installing Windows for the first time on your system, follow the procedure Obtaining IPAddresses below.

n If Windows has already been installed on your system, the host names and IP addresses of thenetwork adapters (cards) have already been defined and exist in your system.This means that you can find out the IP addresses for the network adapters using the procedureDetermining Existing IP Addresses below.However, you still need to use the table Virtual IP Addresses in the procedure Obtaining IP Addresses.

Obtaining IP AddressesAsk the system administrator to give you the addresses and host names listed in the tables below,which shows an example for a configuration with one MSCS cluster with two nodes. You will need toenter the addresses and host names later during the installation process.The column Defined During indicates at which stage of the installation the addresses are defined inthe system.

Caution

Use the names exactly as specified by the system administrator, carefully observing uppercase andlowercase letters.

Physical IP Addresses

Component

Example forPhysical IPAddress

Example forPhysical HostName Purpose Defined During

First MSCS Node:adapter for privatenetwork

10.1.1.1 clusA_priv Address forinter-nodecommunication onthe private network

Windowsinstallation

First MSCS Node:adapter for publicnetwork

129.20.5.1 clusA Address of the firstMSCS node forcommunicationwith applicationservers and LAN(this is the same asthe address of thefirst MSCS node)

Windowsinstallation

08/31/2007 PUBLIC 177/208


Component

Example forPhysical IPAddress

Example forPhysical HostName Purpose Defined During

Additional MSCSNode:adapter for privatenetwork

10.1.1.2 clusB_priv Address forinter-nodecommunication onthe private network

Windowsinstallation

Additional MSCSNode:adapter for publicnetwork

129.20.5.2 clusB Address ofthe additionalMSCS node forcommunicationwith applicationservers and LAN(this is the same asthe address of theadditional MSCSnode)

Windowsinstallation

Virtual IP Addresses

ComponentExample for VirtualIP Address

Example for HostName Purpose Defined During

Cluster group 129.20.5.3 clusgrp Virtual addressand name of thecluster group.It identifies thecluster and is usedfor administrationpurposes.

MSCS softwareinstallation

SAP cluster group 129.20.5.4 sapgrp Virtual address andname for accessingthe group of SAPresources, regardlessof the node it isrunning on

Configuration ofSAP system forMSCS with SAPinston the first node

Database clustergroup

129.20.5.5 dbgrp Virtual address andname for accessingthe group ofdatabase resources,regardless of thenode it is runningon

Execution ofMSCS wizard ordatabase-specificcluster scripts

Determining Existing IP AddressesTo find out the existing IP addresses and corresponding host names and addresses, proceed as follows:

1. Choose Start Settings Network and dial-up Connections.

178/208 PUBLIC 08/31/2007

7 High Availability with Microsoft Cluster Service7.2 Preparation

The Network and dial-up Connections window appears2. Select one of the network cards that are displayed and choose File Properties.

A dialog box opens.3. Choose TCP/IP Protocol Properties.

The TCP/IP Properties dialog box appears and shows the IP address of the initially selected networkcard.

4. To find out the host name that is mapped to the IP address, use the ping command:ping -a <IP_Address>

The system returns the host name assigned to the IP address.Do not forget to ping your local machine as well.

5. Repeat these steps for the other network cards.

For more information about IP addresses in the cluster environment, see IP Addresses in an MSCSConfiguration [page 173].

7.2 Preparation

You have to complete the following preparations for the MSCS cluster installation:

1. You check the hardware and software requirements for MSCS [page 180].

Note

Make sure, that you have installed the operating system with the option Cluster Service on allMSCSnodes. For more information, see the Windows documentation.

2. On allMSCS nodes, you manually assign drive letters to the shared disks [page 181] using theWindows DiskAdministrator. All MSCS nodes must access the shared disks with the same drive letters.

3. On allMSCS nodes, you adjust the size of paging file and the file cache. For more information, seeHardware and Software Requirements [page 180] and Reducing the Size of File Cache [page 55].

4. You map the IP addresses to host names [page 182] on the Domain Name System (DNS) Server or in thehosts file.

5. You check the mapping of host names for MSCS [page 183].

Note

To make sure that all preparation steps have been correctly performed, check that you can movethe disk resources from one node to another so that they are only accessible from a single node atany time.

Caution

You cannot use a host with a domain controller as an MSCS cluster node.

08/31/2007 PUBLIC 179/208


7.2.1 Checking Hardware and Software Requirements forMSCS

When you install the SAP system on cluster hardware, you have to meet the hardware requirementsshown below. This makes sure that the system can take advantage of the MSCS functionality andachieves an acceptable performance level.

Procedure

1. Check that your cluster hardware is certified.AddOn Technology Center for SAP (Add On TCS) certifies hardware platforms for SAP onMicrosoft Windows. The cluster must be included in the Microsoft list of certified clusters and itscomponents. You can access the lists at the following Internet addresses:www.microsoft.com/hcl

www.saponwin.com

2. Make sure that the MSCS nodes of the cluster are connected by a private and public network:n The public network enables communication from the MSCS nodes of the cluster to other

resources in the local area network (LAN).n The private network enables internal communication between the MSCS nodes. In particular,

it enables the Cluster Service running on all MSCS nodes to regularly exchange messages onthe state of the MSCS nodes so that the failure of resources is quickly detected.

3. Check that sufficient storage space is available.Each of the MSCS nodes in the cluster must have its own local disks and have access to shareddisks that can be reached by the MSCS nodes via a shared bus.All software ‒ except the Windows operating system, the MS SQL server system database, and theMSCS software ‒ is stored on the shared disks.One of the shared disks must be used exclusively by the quorum (if a single quorum device clusteris used) that stores the cluster registry and records information about the state of the cluster.

Disks Required Space How to Check

1 local disk on eachMSCS node

3 GB a) Choose Start Programs Administrative ToolsComputer Management Disk Management.

b) Right-click the disk and choose Properties.

At least 4 shared disks n Non-Unicode (notincluding paging file):14 GB

n Unicode (notincluding paging file):20 GB

a) Choose Start Programs Administrative ToolsComputer Management Disk Management.

b) Right-click the disk and choose Properties.

Note

All disk controllers must be able to support hardware-based RAID.

180/208 PUBLIC 08/31/2007

http://www.microsoft.com/hcl

http://www.saponwin.com


4. Check the RAM and paging file size on each MSCS node.For more information, see the Hardware and Software Requirements Checklists [page 47].

5. Check that the software you install on the cluster nodes meets the following requirements:

Software Requirement How to Check

English international version of one of thefollowing:n Windows Server 2003 Enterprise Editionn Windows Server 2003 Datacenter Edition

NoteWe strongly recommend you to use the 64-bitversion of the Windows Server 2003 editions.

NoteIf you install SQL Server 2005, you must installat least SP1 for Windows Server 2003.

To check the Windows version

a) Choose Start All Programs Accessories CommandPrompt

b) Enter the command winver

n One of the following SQL Server EnterpriseEdition server software:l MS SQL Server 2000 Enterprise Edition:

Server Softwareu The latest service pack and hotfix, if

available.For more information, see SAP Notes62988 and 608651.

u Unicode collation SQL_Latin1_Gen-eral_CP850_BIN2Formore information on the collationfor MS SQL Server 2000, see SAP Note600027.

l MS SQL Server 2005 Enterprise Edition:Server Softwareu At least service pack 1 and hotfix, if

available.For more information, see SAP Note62988.

u Unicode collation SQL_Latin1_Gen-eral_CP850_BIN2

n For more information on the current Service Packfor MS SQL Server 2000, see SAP Note 62988.

n For more information on the current hotfix for MSSQL Server 2000, see SAP Note 608651.

n For more information on the new collation, for SQLServer 2000, see Installing the Corrected MS SQL ServerCollation for MS SQL Server 2000 [page 73]

A suitable Windows Resource Kit is stronglyrecommended

-

7.2.2 Assigning Drive Letters for MSCS

We recommend that you assign drive letters for MSCS.

08/31/2007 PUBLIC 181/208








In an MSCS cluster, the shared disks that can be accessed by all nodes via a common bus must beaddressed by all nodes with the same drive letters.

Procedure

1. Choose Start Programs Administrative Tools Computer Management Storage Disk Management.2. Select a disk and choose Action All tasks Change drive.3. Enter a new drive letter.

7.2.3 Mapping Host Names to IP Addresses for MSCS

To enable correct operation of the failover mechanism, you have to map all IP addresses in the MSCScluster to host names.The mapping enables the system to translate host names into IP addresses. Host names are normallyused for administrative tasks because they are easier to use than the long, numeric IP addresses.However, the system can only respond to host names if they are translated into IP addresses.

Prerequisites

n You have installed the Windows operating system.n You have the list of IP addresses [page 177].n You have correctly entered all seven IP addresses required for the MSCS configuration.

Caution

Missing or incorrect entries for the IP addresses can cause problems later during the installation.

ProcedureTo map the host names to the IP addresses, do one of the following:

n Map the host names to IP addresses on a Domain Name System (DNS) server.n Map the IP addresses in the Windows hosts file.

The file is located in the default Windows directory:%SystemRoot%Drive\system32\drivers\etc

Recommendation

We recommend that you perform the mapping on the DNS server because this only requires asingle entry.If you perform the mapping in the hosts file, you have to maintain the hosts file on all MSCSnodes of the cluster, and on all application servers and front ends, as each host in the system has itsown hosts file.

182/208 PUBLIC 08/31/2007


7.2.4 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 seriousproblems later.

PrerequisitesYou have mapped the host names to the IP addresses [page 182] on the DNS Server or in the hosts file.

Procedure

1. For each IP address enter the following commands:a) ping -a <IP_Address>

The system returns the host name that is assigned to the IP address.b) ping hostname

The system returns the IP address that is assigned to the host name.

Note

n When you enter the ping command, you do not get a reply if the host does not yet exist.

n If the address you are checking already exists in the system, you also receive a reply from thehost. For example, after the installation of Windows and the configuration of the network,you get a reply when entering the IP addresses of the network adapters.

2. Compare the output with your own record of addresses and host names, and check for thefollowing possible errors:n Incorrect output of uppercase and lowercase

Make sure that you correct the error before you proceed with the installation.n Error in the network bindings

If you enter the name of the public network adapter, which is usually also the name of thelocal host, and the system returns the IP address of the private network, there is an errorin the network bindings.To correct the network bindings, do the following on allMSCS nodes:a) Choose Start Settings Network and Dial-up Connections

The Network and Dial-up Connections window appears.b) Choose Advanced Advanced Settings Adapters and Bindings

The network cards of the private and public networks are displayed for the current MSCSnode.

Note

The card of the public network must be displayed before that of the private network. Ifnecessary, change the order in which the cards are listed by using theMove Up andMoveDown arrows

08/31/2007 PUBLIC 183/208

7 High Availability with Microsoft Cluster Service7.3 Installation

7.3 Installation

The following sections provide information about how to install the SAP system for MSCS.Below you also find a short section about how to install a Java Add-In in an existing clustered ABAPsystem.

Note

n Make sure that you are logged on as domain administrator, unless otherwise specified.If for any reason, you are not granted domain administrators rights, you can perform theinstallation as a domain user who is a member of the local administrators group. However, thedomain administrator has to prepare the system appropriately for you. Do not use the user<sapsid>adm unless specified.

n On the first MSCS node, in the Cluster Administrator, make sure that all existing cluster groupsare online.

n If you are prompted during the installation process, log off and log on again.

n When you reboot during the installation process [page 194], resources fail over to the other node.Therefore, after each reboot, you have to return the system to the state it had before the reboot.

You have to perform the following steps:

1. In the Cluster Administrator, you move all disk groups and the cluster group to the first MSCS node [page 194].2. On the firstMSCS node, you install MS SQL Server [page 185].3. You install the central services instance for ABAP (ASCS) on the first MSCS node [page 195].4. You install the central services instance (SCS) on the first MSCS node [page 195].5. You cluster the first MSCS node [page 196].6. You install the database instance on the first MSCS node [page 197].7. You cluster the additional MSCS node [page 198].8. If required, you install an enqueue replication server [page 199].9. You install the central instance [page 200].10. You install at least one dialog instance [page 201].

Installing a Java Add-In for an Existing Clustered ABAP System

1. On the MSCS node where the ASCS instance is installed, you run SAPinst and install the SCS instance[page 195].

2. You cluster the SCS instance on the first MSCS node [page 196].3. On the database host, you run SAPinst and install the database instance [page 197].4. You cluster the SCS instance on the additional MSCS node [page 198].5. On the twoMSCS nodes where you installed the (A)SCS instance, you install the enqueue replication

server [page 199].6. On the ABAP central instance host, you run SAPinst and install the Java central instance [page 200].7. You run SAPinst and install the ABAP+Java dialog instance(s) [page 201].

184/208 PUBLIC 08/31/2007


Depending on your MSCS configuration, you install the dialog instance(s) on the dialog instancehost or on a local disk on the MSCS node.

Caution


7.3.1 Clustering the SQL Server Database Software

The following sections describe how to install the SQL Server 2000 or SQL Server 2005 databasesoftware for an MSCS configuration.

Note

If you cluster SQL Server 2000, the installation procedure differs for 32-bit or 64-bit systems.

Caution

For MSCS, you must install MS SQL Server as a default instance.

7.3.1.1 Clustering the SQL Server 2000 Database Software ina 32-Bit System

You perform the following steps on the first MSCS node.

Procedure

1. Log on to the host as a local administrator.2. Insert the MS SQL Server 2000 RDBMS DVD into your DVD drive.3. To start the installation, run autorun.exe located in the x86\SQL2000 directory of the RDBMS DVD.4. Enter the required information as specified in the table:

Window Input

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

MS SQL Server 2000 Enterprise Edition Select Install Database Server.

NoteUse the option to create a new virtual server.

Welcome Click Next.

Computer Name: Enter the name of the virtual server and click Next.

08/31/2007 PUBLIC 185/208


Window Input

User Information Enter your personal information.


CD-Key Enter the key specified in the file SAPCDKEY.txt in theroot directory of the RDBMS DVD and choose Next.

Failover Clustering n Enter the IP address and subnet mask of the virtualdatabase server and click Add.

n Select the public net for the network to use.

Cluster Disk Selection Select the shared disk, where you want to put the datafiles and choose Next.

NoteWhen you select a shared disk you can ignore thewarning that the selected disk is a shared disk in acluster. To proceed, confirm the warning.

Cluster Management Select all MSCS nodes.

Remote Information Enter a domain administrator user account for allMSCS nodes and choose Next.

Instance Name Make sure that Default is selected and choose Next.

Setup Type Select Custom.When you are asked in the Setup Type dialog for thedestination folder for the program and data files, makesure that you install then program files on a local drive. For more

information, see Directories in an MSCS configuration[page 173].

n data files for the master, pubs and msdb databases onone of the shared drive of the MSSQL group (thedefault value for these files is the local disk).

Select Components Select all components and choose Next.

Service Accounts Select Use the same account for each service and enter thepassword for the displayed domain administratoraccount.

Authentication mode Select Windows Authentication Mode and choose Next.

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

Collation settings Select SQL Collations.From the dropdown list, select Binary order, for use with the850 (Multilingual) Character Set.

186/208 PUBLIC 08/31/2007


Window Input

Network Libraries Leave selection unchanged and choose Next.

Start Copying Files Choose Next.

Choose Licensing Mode Select your licensing mode.

Setup Complete Click Finish.

5. Install the latest Service Pack and hot fix, if available, on the first MSCS node. The Service Pack andthe hot fix will also be automatically installed on the additional MSCS node(s).For the current version of the Service Pack and hot fix for MS SQL Server that is supported bySAP, see SAP Notes 62988 and 608651.

Note

If you have to reboot, move theMSSQL database group back to the first MSCS node.

6. Install the corrected MS SQL Server collation [page 73] on the first MSCS node. For more information,see SAP Note 600027.

7. If you have more than one disk in your SQL Server database cluster group, make sure that the SQLServer cluster resource is dependent on all physical disks.To check, perform the following steps:a) In the Cluster Administrator, under the database group, right-click on SQL Server, and take it offline.b) Double-click the SQL Server cluster resource.c) Under Dependencies, selectModify.d) Move all available disks shown under Available resources to Dependencies.e) Confirm your entries with OK.f) In the Cluster Administrator, under the database group, right-click SQL Server, and bring all

resources of the SQL cluster group online.

7.3.1.2 Clustering the SQL Server 2000 Database Software ina 64-Bit System

You perform the following steps on the first MSCS node.

Procedure

1. Log on to the host as a local administrator.2. Insert the MS SQL Server 2000 RDBMS DVD in your DVD drive.3. To start the installation, run setup.exe located in the directory IA64\SQL2000.4. Enter the required information as specified in the table:

08/31/2007 PUBLIC 187/208





Window Input

Setup Mode n Select Start a new installation.n Select Virtual Server.

Registration Information Enter your name and the product key specified inthe file SAPCDKEY.txt in the root directory of theRDBMS DVD.


Virtual Server Name Enter the virtual server name.

Cluster Group Selection Select the cluster group for the virtual serverresources.

Failover Clustering n Select the public network to use.n Enter the IP address for the virtual server, and

choose Add.

Instance Name Make sure that Default is selected and choose Next.

Configure Nodes Select the MSCS nodes to configure.

Remote Account Information Enter a domain administrator user account for yourMSCS nodes and choose Next.

Installation Folders Select the destination folder for the program anddata files. Make sure that you install then program files on a local drive. For more

information, see Directories in an MSCS configuration[page 173].

n data files for the master, pubs and msdb databaseson one of the shared drive of the MSSQL group(the default value for these files is the local disk).

Service Account SelectUse a Domain User account and enter the passwordfor the displayed domain administrator account.

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

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

n Enter and confirm the password for the sa login.

NoteIf you have chosenWindows authentication mode, thesa login is created, but cannot be used.

Security Enhancement: Cross Database Ownership Chaining Leave selection unchanged and choose Next.

188/208 PUBLIC 08/31/2007


Window Input

Collation Settings Select SQL Collations.From the dropdown list, select Binary order, for use withthe 850 (Multilingual) Character Set.

Licensing Mode Select the licensing mode and choose Next.

Ready to Install Select Install.

5. Install the latest service pack and hotfix, if available for MS SQL Server on the first MSCS node. Theservice pack and hotfix will be automatically installed on the additional MSCS node(s).For the current version of the Service Pack and hotfix for MS SQL Server that is supported bySAP, see SAP Note 62988 and 608651.

6. Install the corrected MS SQL Server collation [page 73] on the first MSCS node. For more information,see SAP Note 600027.

7. If you have more than one disk in your SQL Server database cluster group, make sure that the SQLServer cluster resource is dependent on all physical disks.To check, perform the following steps:a) In the Cluster Administrator, under the database group, right-click on SQL Server, and take it offline.b) Double-click the SQL Server cluster resource.c) Under Dependencies, selectModify.d) Move all available disks shown under Available resources to Dependencies.e) Confirm your entries with OK.f) In the Cluster Administrator, under the database group, right-click SQL Server, and bring all

resources of the SQL cluster group online.

7.3.1.3 Clustering the SQL Server 2005 Database ServerSoftware

This section describes how to install the SQL Server 2005 database server software for MSCS.The SQL Server 2005 database server software must be installed on the database host.

Note

To install the client software, see Installing the SQL Server 2005 Native Client Software Manually [page 78].

PrerequisitesThe following prerequisites apply if you install SQL Server 2005 for MSCS.

08/31/2007 PUBLIC 189/208





Note

For more information and a complete list of the restrictions, see the Books Online for SQL Server 2005at: http://msdn.microsoft.com/en-us/library/ms130214.

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

n You have installed Microsoft Distributed Transaction Coordinator (MSDTC). For moreinformation on how to install MSDTC, see KB 301600 at support.microsoft.com/KB/301600.

n You have created domain user groups for each clustered service like SQL Server, SQL Agent, Full Text.l Ask the domain administrator to create the domain groups with the Group Type Security and

Group Scope Domain Local.l The group names must already exist in the domain before you start the SQL Server 2005

installation.l Ask your domain administrator to add the startup account for each service to the respective

domain groups.l Microsoft recommends that you use for each service a different domain group.l Microsoft recommends that you do not share the SQL server domain groups with other

applications.n You have created the SQL Server database cluster group and added the shared disks for the SQL

Sever databases to the group.

Procedure

Note

You perform the following steps on all MSCS nodes.

1. Log on as a domain user who is a member of the local Administrators group on all MSCS nodes.2. Insert the SQL Server 2005 RDBMS DVD in your DVD drive or mount it locally.3. Change to the platform-specific folder and choose Enterprise Edition Servers .4. Start the installation program with setup.exe.5. Enter the required information as specified in the table below:

Note

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

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

Window Server Input

End User License Agreement Accept the licensing terms and conditions andchoose Next.

Installing Prerequisites Choose Install and, if required, Next.

190/208 PUBLIC 08/31/2007


Window Server Input

Welcome to the Microsoft SQL Server Installation Wizard. Choose Next.

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

Noten For more information about the required

system configuration for a softwarecomponent, chooseMessage.

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

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

n The system configuration is checked on allMSCS nodes.

b) Choose Next.

Registration Information a) Enter your personal information, and theproduct key.

b) Choose Next.

Components to Install a) Select the following options:n SQL Server Database Servicesn Create a SQL Server failover clustern Workstation components, Books Online and development

tools.

NoteThe workstation components like SQLManagement Studio, or Books Online are not installedon the additional MSCS node(s). To installthem, start the installation program withsetup.exe on the additional MSCS node(s),after you have finished the installation onthe first MSCS node, and chooseWorkstationcomponents.

b) Choose Advanced.

08/31/2007 PUBLIC 191/208


Window Server Input

Feature Selection a) Expand Database Services and deselect Replication

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

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

c) Choose Next.

Instance Name Select Default Instance and choose Next.

Virtual Server Name Enter the virtual server name and choose Next.

NoteThe virtual server namemust be unique in thenetwork.

Virtual Server Configuration a) Select the public network and enter the IPaddress.

b) Choose Add and then Next.

Cluster Group Selection Select the cluster group where the virtual serverresources are to be installed, and choose Next.

Cluster Node Configuration a) Select and add all MSCS nodes to be included inthe virtual server.

b) Choose Next.

Remote Account Information Enter a domain administrator who is a member ofthe local Administrators group on all MSCS nodes,and choose Next.

Service Account a) Select Use a domain user account and enter the username and password.

b) Choose Next.

Domain Groups for Clustered ServicesNote

The startup account for each clustered service isadded to the DomainName\GroupName to set its accesscontrol. If you do not have domain Administrator’srights, ask your domain administrator to add theseuser accounts to the appropriate domain groups.

Enter the domain and group names of the clusteredservices, and choose Next.

192/208 PUBLIC 08/31/2007


Window Server Input

Authentication Mode a) SelectMixed Mode (Windows Authentication and SQLServer Authentication).This mode is required for a Java or ABAP+Javasystem.If you choose this mode, you set the password forthe sa login.

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

b) Choose Next.

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

b) From the drop-down list select Binary order, based oncode point comparison, for use with the 850 (Multilingual)Character Set.

c) Choose Next.

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

Ready to Install Choose Install.

Setup ProgressNote

To see the log files for the SQL Server components,choose Setup finished.When the setup process has finished, choose Next.

Completing Microsoft SQL Server 2005 Setup Choose Finish.

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

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

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

7. Restart SQL Server.

08/31/2007 PUBLIC 193/208


7.3.2 Moving MSCS Groups

During the cluster installation you have to move the database, SAP, or disk cluster groups from oneMSCS node to the other before you can continue.

Prerequisites

n The groups you want to move are configured and are visible in the Cluster Administrator.n For more information if you need to reboot during the installation, see Rebooting During the Installation

or Conversion for MSCS [page 194].

Moving Groups with the Cluster Administrator

1. Start the Cluster Administrator with Start Programs Administrative Tools Cluster Administrator.2. In the Cluster Administrator, select the group you want to move and drag it to the required MSCS

node on the left-hand pane.3. Repeat the previous step for each group that you want to move.

7.3.3 Rebooting During the Installation or Conversion forMSCS

You only need to perform this procedure if you have to reboot during the installation or conversionfor MSCS. A reboot means that resources fail over to the other MSCS node. Therefore, after eachreboot, you have to return the system to the state it had before the reboot, as described below.

Procedure

1. In the Cluster Administrator, move all resources back to the original node.2. If you have not yet clustered the database, restart the database service.3. If you have already clustered the database, bring the database group online.4. Recreate the SAPMNT share for the directory usr\sap.

Caution

You have to reset the permissions for the SAPMNT share from Read to Full Control, as follows:a) Right-click on the directory usr\sap and choose Sharing and Security.b) Select Sharing and in the Share Name field, enter SAPMNT.c) Under Permissions, make sure that the permission for User Everyone for SAPMNT is set to Full

Control.

194/208 PUBLIC 08/31/2007


7.3.4 Installing the Central Services Instance for ABAP (ASCS)

1. Run SAPinst [page 79] and choose <Your SAP System> SAP Systems <Database> High-AvailabilitySystem Based on <technical stack> Central Services Instance for ABAP (ASCS) .

2. If you are installing the SCS instance with SAPinst for the first time and SAPinst prompts you tolog off, choose OK and log on again.


Note

For more information about the input parameters, position the cursor on a parameter andpress F1 in SAPinst.

Caution

The ASCS installation drive must be a shared disk that belongs to the SAP cluster group.

4. Check that the ASCS instance is running.

7.3.5 Installing the Central Services Instance (SCS)

Caution

Make sure that you install the SCS instance on the same shared disk as the ASCS instance.If you install a Java Add-In for ABAP, make sure that you install the SCS instance on the sameshared disk as the ASCS instance.

1. Run SAPinst [page 79] and choose <Your SAP System> SAP Systems <Database> High-AvailabilitySystem Based on <technical stack> Central Services Instance (SCS) .

Note

For a Java Add-In installation, use the installation service that is available under AdditionalSoftware Life-Cycle Tasks Java Add-In for ABAP

2. If you are installing the SCS instance with SAPinst for the first time and SAPinst prompts you tolog off, choose OK and log on again.

3. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

Note


08/31/2007 PUBLIC 195/208


Caution

The SCS installation drive must be a shared disk which belongs to the SAP cluster group.

4. Check that the SCS instance is running.

7.3.6 Configuring the First MSCS Node

To configure the first MSCS node so that it functions properly in MSCS, you have to run the clusterconfiguration option offered by the SAPinst tool. When you run this option it:

n Creates the SAP cluster groupn Copies tools to the SAPCluster directoryn Sets the SAPService to manual

n Makes sure that the SAPOsCol service is started from the SAPCluster directory

Caution

When you reboot during the conversion to MSCS [page 194], resources fail over to the other MSCS node.Therefore, after each reboot you have to return the system to the state it had before the reboot.

Prerequisites

n You are logged on to the firstMSCS node as domain administrator or as a local user with domainadministration rights. For more information, see Performing a Domain Installation without being a DomainAdministrator [page 57].

n The ASCS and SCS installation drive(s) must be online on the first MSCS node.

Procedure

1. Run SAPinst and choose <Your SAP System> SAP Systems <Database> High-Availability SystemBased on <technical stack> First MSCS Node .

Note


Note

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

2. Enter the required parameter values.

196/208 PUBLIC 08/31/2007


Note

Make sure that you choose instance type ABAP + Java SCS Instances (ABAP+Java).

Note

For more information about the input parameters, position the cursor on the parameter andpress F1 in SAPinst.

3. When the installation is finished, make sure that the following value is set in the default profile:enque/serverhost=<Virtual_(A)SCS_HostName>

ResultSAPinst converts the SAP instances on the first MSCS node for operation in MSCS.

7.3.7 Installing the Database Instance

Prerequisites

n The SAP cluster group is Online on the first MSCS node.n The DB cluster group is Online on the first MSCS node.

ProcedurePerform the following steps on the first MSCS node.

1. On the first MSCS node, run SAPinst [page 79] and choose <Your SAP System> SAP Systems<Database> High-Availability System Based on <technical stack> Database Instance.

Note


2. Follow the instructions in the SAPinst dialogs and enter the required parameter values.a) For the profile UNC path you have to use the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.b) For the tempdb database, specify shared disks that are included in the MSSQL group.c) Distribute the transaction logs and SAPdata files to at least two different shared disks that are

included in theMSSQL group. For more information, see: Distribution of Components to Disks forMSCS [page 171]

Note

For more information about the input parameters, position the cursor on a parameter and press theF1 key in SAPinst.

08/31/2007 PUBLIC 197/208


7.3.8 Configuring the Additional MSCS Node

To configure the additional MSCS node in the cluster, you have to run the MSCS configurationoption foreach additional MSCS node offered by the SAPinst tool. When you run this option it:

n Creates users and groupsn Sets the system and user environmentn Enters required port numbers in the Windows services filen Creates the SAPService and SAPOsCol Services

Caution

When you reboot during the conversion to MSCS [page 194], resources fail over to the other MSCS node.Therefore, after each reboot you have to return the system to the state it had before the reboot.

Prerequisites

n You are logged on to the additionalMSCS node as domain administrator or as a local user withdomain administration rights. For more information, see Performing ad Domain Installation withoutbeing a Domain Administrator [page 57].

n You have already configured the first MSCS node [page 196].

Procedure

1. Run SAPinst [page 79] and choose Additional MSCS Node.

Note


2. Run SAPinst and choose <Your SAP System> SAP Systems <Database> High-Availability SystemBased on <technical stack> Additional MSCS Node .

Note


Note


3. Enter the required parameter values.

Note

Make sure that you choose instance type ABAP + Java SCS Instances (ABAP+Java).

198/208 PUBLIC 08/31/2007


Note

For more information about the input parameters, position the cursor on the parameter andpress F1 in SAPinst.

When you have made all required entries, SAPinst begins processing and converts the SAPinstances on the other MSCS node for operation in MSCS.

4. When SAPinst has finished, start the SAP cluster group SAP <SAPSID> as follows:a) Open the Cluster Administrator with Start Programs Administration Tools Cluster Administrator .b) Select the SAP cluster group and bring it online.

7.3.9 Installing an Enqueue Replication Server

We recommend that you install an enqueue replication server with SAPinst on allMSCS nodes wherean SCS or ASCS instance is running.

Note

You have to perform the installation at least four times, for each (A)SCS instance and on eachMSCS node.

Prerequisites

n Your SCS and ASCS instance is already clustered with MSCS.n You have to install the enqueue replication server on a local disk.

Procedure

1. On the firstMSCS node, log on as domain user who is a member of the local administrators group.2. Run SAPinst [page 79] and choose <Your SAP System> SAP Systems <Database> High-Availability

System Based on <technical stack> Enqueue Replication Server .

Note


3. Follow the instructions in the SAPinst dialogs and enter the required parameters.Note the following, when entering the parametersn On the SAPinst screen: SAP System > SAP Instance, enter the:l SAP system ID <SAPSID> of your SAP system

08/31/2007 PUBLIC 199/208


l Instance number of the SCS or ASCS instance

l Virtual instance host name of the SCS or ASCS instance

n On the SAPinst screen SAP System > Enqueue Replication Server Instance, enter a unique instancenumber that is not in use by another instance on this host.

n Decide if you want to restart the SCS and ASCS instance and service cluster resources withSAPinst now, or later with the Cluster Administrator.

Note

You only need to do this once for all enqueue replication servers that you install on theMSCS nodes.

After you have entered all required input information, SAPinst starts the installation and displaysthe progress of the installation. During the process phase, the enqueue server instance is started.SAPinst installs the enqueue replication server instance on a local disk in the following directory:.\usr\sap\<SAPSID>\ERS<instance_number>\

Note

The profile is replicated from the global host to the local instance profile folder. The enqueuereplication server instance uses the profile from the local instance profile folder:.\usr\sap\<SAPSID>\ERS<instance_number>\profile\

4. On the additionalMSCS node, start SAPinst to install the enqueue replication server for the SCSor ASCS instance as described in step 2 above.

Note

There is no need to move the SCS or ASCS cluster group to another MSCS node.

5. Enter the required parameter values in the SAPinst dialogs as described above.

7.3.10 Installing the Central Instance

The following describes how to install the central instance for MSCS.You have the following options to install the central instance:

n You install the central instance on an MSCS node.In this case, bring the SAP cluster group online on this node, and make sure that the centralinstance number is different from the (A)SCS instance number.

n You install the central instance on a host outside of MSCS.In this case, you have to install the database client software on this host.

200/208 PUBLIC 08/31/2007


Procedure

1. Run SAPinst [page 79] and choose <Your SAP System> SAP Systems <Database> High-AvailabilitySystem Based on <technical stack> Central Instance .

Note


2. If SAPinst prompts you to log off, choose OK and log on again.3. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

Caution

n If you install the central instance on an MSCS node, make sure that on the screen SAP System> General Parameters for the:l Profile Directory, you use the UNC path of the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.l Installation Drive, you choose the local disk where you want to install the central instance. Do

not enter the shared disk for the (A)SCS instance.

Note


4. Check that the central instance is running.

7.3.11 Installing the Dialog Instance

You have to install at least one dialog instance for MSCS.You have the following options to install the dialog instance:

n You install the dialog instance on an MSCS node.In this case, bring the SAP cluster group online on this node, and make sure that the dialoginstance number is different from the (A)SCS instance number.

n You install the dialog instance on a host outside of MSCS.In this case, you have to install the database client software on this host.

Procedure

1. Run SAPinst [page 79] and choose <Your SAP System> SAP Systems <Database> High-AvailabilitySystem Based on <technical stack> Dialog Instance

08/31/2007 PUBLIC 201/208

7 High Availability with Microsoft Cluster Service7.4 Post-Installation

Note


2. If SAPinst prompts you to log off, choose OK and log on again.3. Follow the instructions in the SAPinst dialogs and enter the required parameter values.

Caution

n If you install the dialog instance on an MSCS node, make sure that on the screen SAP System> General Parameters for the:l Profile Directory, you use the UNC path of the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.l Installation Drive, you choose the local disk where you want to install the dialog instance. Do

not enter the shared disk for the (A)SCS instance.

Note


4. If required, install additional dialog instances outside of MSCS.

Caution

Make sure that on the screen SAP System > General Parameters for the Profile Directory, you use the UNCpath of the virtual (A)SCS host name, for example:\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.

7.4 Post-Installation

This section describes how to complete and check the installation of the SAP system for an MSCSconfiguration:

1. You have installed at least one SAP front end [page 60].2. You start and stop the SAP system in an MSCS configuration [page 203].3. You perform the post-installation checks for the enqueue replication server [page 203].4. If required, you perform the other post-installation steps [page 97] for the standard system installation

listed in this guide.

202/208 PUBLIC 08/31/2007


7.4.1 Starting and Stopping the SAP System in an MSCSConfiguration

The following describes how to start or stop the SAP system in an MSCS configuration with the:

n SAP MMC

n Cluster Administrator

Note

You also use the Cluster Administrator for all other administrative tasks like moving instances fromone MSCS node to the other MSCS node.

Procedure

n To start or stop your SAP system with the SAP MMC, see Starting and Stopping the SAP System [page 98].n To start or stop your SAP system with the Cluster Administrator do the following:

1. Start the Cluster Administrator by choosing Start Programs Administrative Tools ClusterAdministrator .

2. To start or stop all instances belonging to the SAP cluster group, right-click the SAP clustergroup SAP <SAPSID> and choose Bring online or Take offline.

3. To start or stop a single instance of the SAP cluster group, right-click the instance SAP<SAPSID> <instance_no> Instance and choose Bring online or Take offline.

7.4.2 Post-Installation Checks for Enqueue ReplicationServer

The following sections describe the tests you must perform to check whether the installed enqueuereplication server works properly. For these tests you use the ENQT and ENSMON command linetools, which allow remote access to the enqueue server statistics. Before you can use these toolsyou must copy them to the remote host where the Enqueue Replication Server is running andfrom where you want to start the tests.

Note

Make sure that you have restarted the (A)SCS instance and service cluster resources SAP <SAPSID><(A)SCS_instance_number> Instance and SAP <SAPSID> <(A)SCS_instance_number> Service during theinstallation with SAPinst or with the Cluster Administrator.

You perform the following steps:

1. You copy ENQT.exe and ENSMON.exe from your cluster’s binary directory on the sapmnt share\\<host>\sapmnt\<SAPSID>\SYS\exe\<codepage>\<platform> to a directory on the remotehost from where you run the tests.

08/31/2007 PUBLIC 203/208


2. You check the status of the enqueue replication server with the ENSMON tool [page 204].3. You check the fill status and ID of the lock table during failover with the ENQT tool [page 204].

7.4.2.1 Checking the Status of the Enqueue ReplicationServer with ENSMON

You use the ENSMON tool to check if the enqueue replication server and the enqueue server areproperly connected.

Prerequisites

n You have started the (A)SCS instance of your SAP system.n You run the ENSMON tool from the host where you installed the Enqueue Replication Server.

ProcedureTo check the status of the enqueue replication server enter the following command:ensmon pf=<ERS_instance_profile> 2

where <ERS_instance_profile> is the profile created during the installation of the EnqueueReplication Server.

n If the enqueue replication server and the enqueue server are properly connected, the output issimilar to this:Try to connect to host <Virtual (A)SCS host> service sapdp01 get replinfo request

executed successfully

Replication is enabled in server, repl. server is connected

Replication is active

...

n If the enqueue replication server and the enqueue server are not properly connected, the outputis similar to this:Try to connect to host <Virtual (A)SCS host> service sapdp01 get replinfo request

executed successfully

Replication is enabled in server, but no repl. server is connected

...

7.4.2.2 Monitoring the Lock Table During Failover with ENQT

With the following tests you monitor and check the lock table’s fill status and the lock table IDusing the ENQT tool.

204/208 PUBLIC 08/31/2007


Prerequisites

n You have started the (A)SCS instance of your SAP system.n You run the ENQT tool from the host where you installed the Enqueue Replication Server.

Caution

Only use the ENQT commands stated in this procedure otherwise you might damage theenqueue server’s lock table.

Monitoring the Lock Table Fill Status During Failover with ENQT

1. Use the following command to fill the lock table of the enqueue server with 20 locks:enqt pf=<ERS_instance_profile> 11 20


2. Monitor the fill status of the lock table with the following command:enqt pf=<ERS_instance_profile> 20 1 1 9999

This command continuously reads the content of the enqueue server’s lock table and returnsthe number of the table entries to the console.

3. Move the (A)SCS cluster group to another MSCS node to simulate an enqueue server failoverwhile running the ENQT command.The output is similar to this:Number of selected entries: 20

Number of selected entries: 20




Number of selected entries: 0 ( enqueue server fails over )Number of selected entries: 20 ( enqueue server is running again )Number of selected entries: 20




...

4. Make sure that the lock count is the same before and after the failover.

Monitoring the Lock Table ID During Failover with ENQT

1. Monitor the lock table ID during the failover with the following command:for /l %i in (1,1,100000) do enqt pf=<ERS_instance_profile> 97


08/31/2007 PUBLIC 205/208


2. Move the (A)SCS cluster group to another MSCS node to simulate an enqueue server failoverwhile 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: EnqTabCreaTime/RandomNumber = 25.10.2005 11:15:59 1130231759

/ 9288

...

(Output after failover)C:\WORK\HA\ENQU-Tests>enqt pf=BUG_ERS01_PCJ2EEV6 97

---REQ----------------------------------------------------------

EnqId: EnqTabCreaTime/RandomNumber = 25.10.2005 11:15:59 1130231759

/ 9288

...

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

End of: HA (MSCS)

206/208 PUBLIC 08/31/2007

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2007 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

sap netweaver 7.0 sr2 abap+java on windows ms sql server

Documents