PUBLIC. Installation Guide. 7.0 Windows: MS SQL. Target Audience. Technology consultants System administrators

Transcription

1 PUBLIC Installation Guide SAP Solution Manager 7.0 Windows: MS SQL Server Target Audience Technology consultants System administrators Document version: /30/2008

2 Document History Caution Before you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace The following table provides an overview on the most important document changes: Version Date Description 1.0 4/30/2008 Initial Version 2/200 PUBLIC 04/30/2008

3 Table of Contents Chapter 1 Introduction New Features SAP s for the Installation Online Information from SAP Naming Conventions Chapter 2 Planning Basic System Variants System Landscape Directory Domain or Local Installation How to Distribute Instances to Hosts How to Distribute Instances to Hosts for a Java Add-In Installation Distribution of SAP System Components to Disks SAP Directories SAP System Transport Host Basic SAP System Parameters Running Adobe Document Services on Nonsupported Platforms Installing SAP Solution Manager Diagnostics in an Existing SAP Solution Manager ABAP System Chapter 3 Preparation Hardware and Software Requirements Running the Prerequisite Checker in Standalone Mode (Optional) Requirements for a Central System Requirements for a Distributed System Requirements for a High-Availability System Requirements for the Dialog Instance Checking the Windows File System Checking the Windows Domain Structure Reducing the Size of the File Cache Required User Authorization for the Installation Performing a Domain Installation Without Being a Domain Administrator Preparing the SAP System Transport Host Installing the Front-End Software Installing the Java Development Kit /30/2008 PUBLIC 3/200

4 3.10 Preparing the Installation DVDs Downloading Installation DVDs from SAP Service Marketplace (Optional). 70 Chapter 4 Installation Installing the SQL Server Database Software Installing the SQL Server Database Software with SQL4SAP Installing the SQL Server Database Software Manually Installing the SQL Server 2005 Database Server Software Manually Installing the SQL Server 2005 Native Client Software Manually Installing the SQL Server 2008 Database Server Software Manually Installing the SQL Server 2008 Native Client Software Manually Installing the SQL Server 2000 Database Software on 64-Bit Manually Installing the Corrected MS SQL Server Collation for MS SQL Server Preparing your System for a Java Add-In Installation Installing an SAP System Using SAPinst Running SAPinst on Windows Installing the Java Add-In for an Existing ABAP System (Optional) Using SAPinst GUI Interrupted Installation with SAPinst Performing a Remote Installation with SAPinst (Optional) Starting SAPinst GUI Separately (Optional) Entries in the Services File Created by SAPinst How to Avoid Automatic Logoff by SAPinst Chapter 5 Post-Installation Configuring the Windows Server 2008 Firewall Logging On to the Application Server Logging On to SAP Solution Manager Diagnostics Installing the SAP License Creating Symbolic Links on Windows Server 2008 for Application Servers Installing the SAP Online Documentation Configuring Remote Connection to SAP Support Applying the Latest Kernel and Support Packages Performing Initial ABAP Configuration Performing a Full System Backup Post-Installation Steps for Adobe Document Services Assigning Roles to Users ADSUSER and ADS_AGENT Checking the IIOP Service and the Startup Properties Installation Check and Quick Tests for Adobe Document Services Ensuring User Security Checking the SAP Java Documentation Configuring SAP Solution Manager /200 PUBLIC 04/30/2008

5 5.15 Post-Installation Steps for the Diagnostics Agent Installing the SAP Solution Manager Enterprise Edition Add-On (Optional). 124 Chapter 6 Additional Information Database Installation for Multiple Components with MS SQL Server Default or Named MS SQL Server Instances Installation of Multiple Components in One Database (Optional) Integration of LDAP Directory Services (Optional) Installation of Additional Software Units or Usage Types in an Existing SAP System Starting and Stopping the SAP System Single Sign-On with Microsoft Kerberos SSP Preparing the Central Instance Configuring the SAP Front End Activating Single Sign-On for the SAP Logon Mapping SAP Users to Windows Users Configuring User Management to Use an LDAP Directory (Optional) Initial Technical Configuration for Adobe Document Services Initial Technical Configuration for the System Landscape Directory (SLD) SAP System Security on Windows Automatic Creation of Accounts and Groups Troubleshooting Troubleshooting with SAPinst Deleting an SAP System Running SAPinst to Delete an SAP System Chapter 7 High Availability with Microsoft Cluster Service Planning System Configuration in MSCS SAP System Components in an MSCS Configuration Enqueue Replication Server in an MSCS Configuration Distribution of Components to Disks for MSCS Directories in an MSCS Configuration IP Addresses in an MSCS Configuration Obtaining and Determining IP Addresses for MSCS Preparation Assigning Drive Letters for MSCS Mapping Host Names to IP Addresses for MSCS Checking the Mapping of Host Names for MSCS Installation Clustering the SQL Server Database Software Clustering the SQL Server 2005 Database Server Software /30/2008 PUBLIC 5/200

6 Clustering the SQL Server 2008 Database Server Software Clustering the SQL Server 2000 Database Software in a 64-Bit System Moving MSCS Groups or Services and Applications Rebooting During the Installation or Conversion for MSCS Installing the Central Services Instance for ABAP (ASCS) Installing the Central Services Instance (SCS) Configuring the First MSCS Node Installing the Database Instance Configuring the Additional MSCS Node Installing an Enqueue Replication Server Installing the Central Instance Installing the Dialog Instance Post-Installation Starting and Stopping the SAP System in an MSCS Configuration Post-Installation Checks for Enqueue Replication Server Checking the Status of the Enqueue Replication Server with ENSMON Monitoring the Lock Table During Failover with ENQT /200 PUBLIC 04/30/2008

7 1 Introduction 1 Introduction This document explains how to install SAP Solution Manager 7.0. SAP Solution Manager 7.0 comprises SAP Solution Manager support package stack (SPS) 15. You install SAP Solution Manager 7.0 as an SAP system based on AS ABAP and AS Java with the installation tool SAPinst in one installation run. The part of the system that is based on AS Java is used for the functions of Solution Manager Diagnostics. For more information about SAP Solution Manager, see SAP Solution Manager 7.0 is based on the technology of SAP NetWeaver 7.0 support package stack (SPS) 14. For more information about SAP NetWeaver technology, see This document also explains how to install the Java Add-In for an existing SAP Solution Manager ABAP system with SAPinst and how to deploy SAP Solution Manager Diagnostics with the Java Support Package Manager (JSPM). You have to do this if you have upgraded your SAP Solution Manager system to SAP Solution Manager 7.0. For more information, see Installing SAP Solution Manager Diagnostics in an Existing SAP Solution Manager ABAP System [page 43]. Make sure you have read the documentation Master Guide SAP Solution Manager 7.0 before you start with this installation guide. The Master Guide is available at: SAP Components SAP Solution Manager Release 7.0 Constraints You need to consider the following constraints before you start your installation: Your operating system platform must be 64-bit. You must only use the SAP installation tools according to the instructions and for the purposes described in the SAP installation document. Improper use of the SAP installation tools can damage files and systems already installed. SAP system installations should only be performed by SAP Technical Consultants certified for your operating system, your database, and the SAP system that you are installing. For downward-compatible releases of DB/OS platforms for SAP products, SAP plans to regularly release the newest database (DB) and operating-system (OS) versions of SAP products. These releases are downward-compatible with earlier SAP system releases. that for already shipped SAP components, we only support the installation for database versions proposed by the installation tool. Therefore, you must install an SAP component or perform a system copy using a downward-compatible database as follows: Install the component with the old proposed database version. 04/30/2008 PUBLIC 7/200

8 1 Introduction 1.1 New Features Upgrade the old database version to the downward-compatible new version. 1.1 New Features You can find the new features of SAP Solution Manager 7.0 at The following tables provide an overview of the new features related to the installation: Caution Make sure that you read the release notes for your SAP system. You can find these at SAP System Installation Area SAPinst Description As of SAP NetWeaver 7.0, SAPinst has the following new features: You can check the prerequisites for your SAP system installation with the Prerequisite Checker [page 47]. You can install a central system in one of two modes: Typical Mode If you choose Typical, your SAP system is installed with default settings. As a result, you only have to respond to a small selection of prompts. If you want to change any of the default settings, you can do so on the parameter summary screen at the end of the installation. Custom Mode If you choose Custom, you must manually enter all installation parameters. You can change your values on the parameter summary screen at the end of the installation. You can uninstall an SAP system or an SAP component with the SAPinst service Uninstall System / Standalone Engines / Optional Standalone Unit. You can install the Java Add-In for an existing ABAP system. This means that you run SAPinst to execute the following: Install the central services instance (SCS) Add the Java database schema to the existing ABAP database instance Add the Java central instance with usage types to the existing ABAP central instance The installation of the Java Add-In for an existing ABAP system is described in the documentation Installation Guide <your product> ABAP+Java on <OS>: <Database> available at You cannot install the Java Add-In for existing ABAP dialog instance(s). Instead, 8/200 PUBLIC 04/30/2008

9 1 Introduction 1.1 New Features Area Description you have to install new ABAP+Java dialog instance(s). Installation DVDs High Availability SAP NetWeaver Administrator SAP Solution Manager Diagnostics Agent 64-bit support for all instances except dialog instances You can change the default names of the Java users J2EE_ADMIN, J2EE_GUEST and SAPJSF during the input phase of the installation. You assign one master password to all users created by SAPinst. This password is used for all user accounts and for the secure store key phrase. 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 before you start the actual installation. You start the installation from a single Installation Master DVD. There is a terminology change with Windows Cluster. As of Windows Server 2008 the high-availability feature is called Failover Clustering. For practical reason we are continuing to use the general abbreviation MSCS. You have the following options to install a high-availability system with MSCS: You install one SAP system in one MSCS cluster. You install one SAP system in two MSCS clusters. In both cases the following restrictions apply: You must install the (A)SCS instance on two MSCS nodes in one MSCS cluster. 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. SAP NetWeaver Administrator is a brand new solution for monitoring and administering Java systems and their applications. For more information, see the SAP NetWeaver Master Guide and the following: Lifecycle Management Operations Knowledge Center Administration A SAP Solution Manager Diagnostics Agent (Diagnostics Agent) is a standalone Java program that runs on each of the systems managed by SAP Solution Manager Diagnostics. It gathers information and reports to the SAP Solution Manager system. For more information about the Diagnostics Agent, see The installation of the Diagnostics Agent is now part of the Installation Master DVD. That is, you can choose between the following options: If there is no Diagnostics Agent already installed on this physical or virtual host, it is installed automatically with an AS Java central instance and dialog instance. You can install it as a standalone engine. If you want to use 32-bit SAP NetWeaver components, first check whether these components can run on 64-bit operating systems. If so, we recommend that you use 64-bit systems. If not, you can install an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP instances, you must use 64-bit systems 04/30/2008 PUBLIC 9/200

10 1 Introduction 1.1 New Features Area Only Unicode support for new installations Maintenance Optimizer Description Every newly installed SAP system is a Unicode system. However, non-unicode is still supported for copied and upgraded systems. All downloadable software components based on SAP NetWeaver 7.0 and subsequent versions released after April 2, 2007 are available exclusively through the Maintenance Optimizer in SAP Solution Manager. This comprises: Support Package Stacks, Support Packages, and patches for Java instances, except for kernel patches Legal changes SAP applications and versions that are: Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and all applications based on this software, including SAP Business Suite 2005 (and subsequent versions) Optional for all SAP applications For more information, see Operating Systems and Platforms Area Support of Operating Systems and Platforms Description This guide already includes information about the new Windows operating system, Windows Server 2008, which is not yet supported by all databases running an SAP system. For supported operating system and database releases, see the Product Availability Matrix at For forums, blogs, content, and community related to all of the supported databases and operating systems, see the Database and Operating Systems area at Documentation Area Installation of Additional Software Units or Usage Types Links in PDF files Description The documentation on how to install additional software units or usage types to an existing SAP system is now included in the installation guides. Up to now this documentation was only available in SAP You can use the new links in the PDF files of the guides as follows: Click the section headings such as New Features to jump back to the table of contents at the beginning of the guide. Click an internet link such as to jump to the corresponding internet page. 10/200 PUBLIC 04/30/2008

11 1 Introduction 1.2 SAP s for the Installation 1.2 SAP s for the Installation You must read the following SAP s before you start the installation. These SAP s contain the most recent information on the installation, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP, which you can find at SAP s for the Installation Title Description SAP Solution Manager 7.0 Installation Documentation: SAP Solution Manager 7.0 Central installation note for SAP Solution Manager 7.0. Information about scenarios, configurations, implementation, upgrade, maintenance, security, sizing, end user usage, enhancements using Support Packages or problem analyses with regard to SAP Solution Manager End-to-End Diagnostics Information about availability and limitations of End-to-End Diagnostics Installation Prerequisite Checker SAP Software on UNIX and Windows: Checking OS Dependencies 1.3 Online Information from SAP More information is available online as follows. Before you continue to read this installation guide, you must have read the Master Guide. Having finished the installation and the required post-installation steps, you have to follow the instructions in the configuration guide. The configuration guide also points you to further documentation that might be relevant for you. 04/30/2008 PUBLIC 11/200

12 1 Introduction 1.3 Online Information from SAP Documentation Description Internet Address Title List of media for installation or upgrade for SAP Solution Manager 7.0 Master Guide SAP Solution Manager 7.0 Upgrade to SAP Solution Manager 7.0 FAQ on upgrade to SAP Solution Manager 7.0 Sizing Guide SAP Solution Manager 7.0 Configuration of SAP Solution Manager Root Cause Analysis Installation and Upgrade Guide SAP Solution Manager 7.0 Security Guide Front End installation Homogeneous and heterogeneous system copy for SAP systems based on NetWeaver 7.0 Migration Guide Solution Manager Diagnostics SAP Components SAP Solution Manager Release SAP Components SAP Solution Manager Release SAP Components SAP Solution Manager Release SAP Components SAP Solution Manager Release SAP Components SAP Solution Manager Release SAP Components SAP Solution Manager Release SAP Components SAP Solution Manager Release Solution Manager Installation - Clients Installation - SAP NetWeaver Systems SAP Components SAP Solution Manager Release 7.0 SAP Media List SAP Solution Manager 7.0 Master Guide SAP Solution Manager 7.0 Upgrade Guide SAP Solution Manager 7.0 <OS> <Database> FAQ on Upgrade of SAP Solution Manager Release 3.1/3.2 to 7.0 Sizing Guide Sizing SAP Solution Manager 7.0 Configuration Guide SAP Solution Manager 7.0 as of SP<SP level of your SAP Solution Manager system> SAP Solution Manager 7.0 End-to-End Root Cause Analysis Root Cause Analysis Installation and Upgrade Guide SECURITY GUIDE SAP Solution Manager 7.0 Front End Installation Guide (this guide is also available on the Presentation DVD) Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP NetWeaver 7.0 Migration Guide for Solution Manager Diagnostics SAP NetWeaver 04s SP Stack <current stack> 12/200 PUBLIC 04/30/2008

13 1 Introduction 1.3 Online Information from SAP Description Internet Address Title Maintenance Optimizer System Landscape Directory SAP NetWeaver Problem Analysis Guide (PAG) Functions in Detail Support Area Maintenance Optimizer Installation Configuration SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) All corrective software packages released after April 2, 2007 are available exclusively through the Maintenance Optimizer in SAP Solution Manager. This includes Support Packages (Stacks) for SAP NetWeaver 7.0 and subsequent versions, as well as all applications based on this software, including SAP Business Suite Post-Installation Guide - System Landscape Directory of SAP NetWeaver 7.0 (04s) SAP NetWeaver Problem Analysis Guide (PAG) General Quick Links Description SAP Help Portal SAP NetWeaver Library in SAP Help Portal SAP s Forums, blogs, and general information related to all of the supported databases and operating system platforms Product Availability Matrix (PAM) for supported operating system releases General information, forums and blogs about information related to SAP on Windows Release notes Unicode SAP systems and their availability System sizing (Quick Sizer tool) SAP NetWeaver capabilities Internet Address /30/2008 PUBLIC 13/200

14 1 Introduction 1.4 Naming Conventions Description Life-cycle management for SAP NetWeaver Landscape design for SAP NetWeaver Application management for SAP NetWeaver High Availability System Landscape Directory Software logistics for SAP NetWeaver SAP NetWeaver operations SAP NetWeaver Development Infrastructure Security for SAP NetWeaver Internet Address For information on Windows operating system security, see: Information on SAP Support Package Stacks SAP Solution Manager Maintenance Optimizer End-to-End Root Cause Analysis Naming Conventions In this documentation, the following naming conventions apply: Terminology SAP Solution Manager refers to SAP Solution Manager 7.0. SAP system refers to SAP Solution Manager 7.0 system. ABAP+Java system or system based on AS ABAP and AS Java refers to the two stacks (ABAP and Java) of SAP Solution Manager 7.0. Java Add-In refers to the Java Add-In for an existing SAP Solution Manager ABAP system. For example, you have upgraded your SAP Solution Manager 3.1 or 3.2 system to SAP Solution Manager 7.0 and want to use the functionalities of Solution Manager Diagnostics. Diagnostics Agent refers to SAP Solution Manager Diagnostics Agent. 14/200 PUBLIC 04/30/2008

15 1 Introduction 1.4 Naming Conventions Only valid for: HA (MSCS) Terminology for High Availability on Windows As of Windows Server 2008 there are the following terminology changes for a cluster configuration: The cluster feature is now called Failover Clustering. For practical reasons we are continuing to use the general abbreviation MSCS in this guide. Cluster groups are now called services and applications. The Cluster Administrator is now called Failover Cluster Management. End of: HA (MSCS) Variables Variables <SAPSID> <sapsid> <DBSID> <dbsid> <host_name> <INSTDIR> <DVD_DIR> <OS> <SCHEMA_ID> Description SAP system ID in uppercase letters SAP system ID in lowercase letters Database ID in uppercase letters Database ID in lowercase letters Name of the corresponding host Installation directory for the SAP system Directory on which a DVD is mounted Operating system name within a path Database schema ID The following example shows how the variables are used: 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. 04/30/2008 PUBLIC 15/200

16 This page is intentionally left blank.

17 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 with Microsoft Cluster Service (MSCS), see also the MSCS-specific planning activities [page 152]. End of: HA (MSCS) You have to complete the following planning activities: 1. You read the Master Guide to get an overview of the documents and information resources that you will need for the installation and configuration of SAP Solution Manager You choose your basic system variant [page 17]. 3. You plan the setup of the System Landscape Directory [page 20]. 4. You decide whether you want to perform a domain or local installation [page 21]. 5. You plan how to distribute the instances to hosts [page 22]. 6. You plan how to distribute instances to hosts for a Java Add-In installation [page 23]. 7. For the database installation, you decide on how to distribute your database components to disk [page 25]. 8. You read about the SAP directories [page 28]. 9. You decide on the transport host to use [page 33]. 10. You identify basic SAP system parameters [page 33]. 11. 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 42]. The following planning activities are optional: Installing SAP Solution Manager Diagnostics in an Existing SAP Solution Manager ABAP System [page 43] Database Installation for Multiple Components with MS SQL Server [page 125] Installation of Multiple Components in One Database (MCOD) [page 127] Caution This step does not apply to the installation of a Java Add-In to an existing ABAP system. 2.1 Basic System Variants This section describes the basic system variants for SAP Solution Manager and shows how you can distribute SAP system instances within these variants 04/30/2008 PUBLIC 17/200

18 2 Planning 2.1 Basic System Variants It also includes a section for the distribution of instances in a Java Add-In installation. SAP Solution Manager 7.0 is installed as an ABAP+Java system. 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) and the Java application server (AS-Java) on the SAP system. 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 the mandatory instances are installed on separate hosts. Figure 1: ABAP+Java System Installing a Java Add-In to an 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 SAP system. You need to install the Java Add-In if you want to install the Java-based SAP Solution Manager Diagnostics in an existing SAP Solution Manager ABAP system [page 43] upgraded to SAP Solution Manager 7.0. Mandatory instances of a Java Add-In for ABAP system are the central instance, the central services instance, and the database instance. 18/200 PUBLIC 04/30/2008

19 2 Planning 2.1 Basic System Variants 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 uninstall the existing ABAP dialog instance, before you install the new ABAP+Java dialog 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 the mandatory instances are installed on separate hosts. Figure 2: Java Add-In for an Existing ABAP System More Information Only valid for: HA (MSCS) For more information about how to distribute SAP instances in a high-availability SAP system, see System Configuration in MSCS [page 153]. End of: HA (MSCS) 04/30/2008 PUBLIC 19/200

20 2 Planning 2.2 System Landscape Directory 2.2 System Landscape Directory The System Landscape Directory (SLD) is the central directory of system landscape information relevant for the management of your software lifecycle. It contains a description of your system landscape (that is, software components that are currently installed) and a repository of software components that can theoretically be installed in your landscape. In this way, the System Landscape Directory acts as a central information provider for SAP and third-party tools that use this data to deliver the services you need to keep your landscape up and running. The System Landscape Directory is automatically installed with the SAP Solution Manager 7.0 system. There are two options to set up your SAP Solution Manager system landscape: Manual maintenance of the system landscape: No productive SLD is required, instead you have to maintain the SAP Solution Manager system landscape manually in transaction SMSY. ABAP systems can provide their system information via trusted RFC connections to SAP Solution Manager. Caution Manual maintenance of transaction SMSY causes a high effort for initial data entry (approx 1,5h per non ABAP system) and ongoing maintenance for each change to the non ABAP system. Therefore we do not recommend this option. Automatic maintenance of the system landscape: You have to install a local SLD on the SAP Solution Manager system with connection and replication from the productive SLD instances in your existing landscape. SAP Solution Manager expects that you already run System Landscape Directories (SLD(s)) for productive usage like for WebDynpro or Process Exchange (XI). On top, SAP Solution Manager needs an SLD (called local SLD) itself as a complete catalog of technical systems and complete catalog of installed software components as data provider for transaction SMSY and as persistence for own WebDynpro connection data. Recommendation To avoid conflicts between the availability of your productive SLD(s) and the availability of SAP Solution Manager (like upgrade of SAP Solution Manager, or Root Cause Analysis on the productive SLD in case of problems) we strongly recommend to install this local SLD on the SAP Solution Manager system. 20/200 PUBLIC 04/30/2008

21 2 Planning 2.3 Domain or Local Installation More Information For more information, see the Root Cause Analysis Installation and Upgrade Guide which you can find at one of the following: End-to-End Root Cause Analysis Documentation Library Installation and Configuration Root Cause Analysis Installation and Upgrade Guide SAP Components SAP Solution Manager <Current Release> 2.3 Domain or Local Installation Before you install the SAP system, you have to decide whether you want to perform a domain or local installation, since this affects how the user account information is stored and accessed. For more information about the differences between a local and domain installation, see the Microsoft article Deciding Between Workgroups and Domains at: Domain Installation In a domain installation, the user account information is stored centrally in one database on the domain controller and is accessible to all hosts in the system. You have to perform a domain installation if one of the following applies: You install a distributed system (strongly recommended to avoid authorization problems). Only valid for: HA (MSCS) You install a high-availability system with MSCS. End of: HA (MSCS) You want to use Single Sign-On. You use a common transport host for several SAP systems running on different computers. Local Installation In a local installation, all Windows account information is stored locally on one host and is not visible to any other hosts in the system. If the SAP system is to run on a single machine (central system), you can perform a local installation. If your SAP system was installed as a local installation and you want to later change to a domain installation, you must perform a homogeneous system copy. For more information, see the documentation System Copy for SAP Systems based on SAP NetWeaver <release> <technology> at: <your product> 04/30/2008 PUBLIC 21/200

22 2 Planning 2.4 How to Distribute Instances to Hosts More Information Required User Authorization for the Installation [page 61] Single Sign-On with Microsoft Kerberos SSP [page 137] 2.4 How to Distribute Instances to Hosts The following provides information on how you can distribute the SAP instances for the different SAP system variants. You use SAPinst to install the SAP instances as a: Central system on a single host You run SAPinst and install all instances on one host. Distributed system on several hosts You perform the following steps: 1. You specify or create a shared transport directory. 2. You run SAPinst and install the: Central services instance (SCS) on the global host Database instance on the database host Central instance on the central instance host Dialog instance(s), if required, on the dialog instance host(s) Caution We do not support operating an ABAP dialog instance with an ABAP+Java system. The following figure shows how to distribute your instances to several hosts: 22/200 PUBLIC 04/30/2008

23 2 Planning 2.5 How to Distribute Instances to Hosts for a Java Add-In Installation Figure 3: Distribution of Instances in an ABAP+Java System 2.5 How to Distribute Instances to Hosts for a Java Add-In Installation The following provides information on how you can distribute the Java Add-In SAP instances for an existing ABAP system. You use SAPinst to install the Java Add-In SAP instances as a: Central system on a single host You run SAPinst and install the Java Add-In on one host. Distributed system on several hosts You 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 have to install new ABAP+Java dialog instance(s). The following figure shows how to distribute your instances on several hosts: 04/30/2008 PUBLIC 23/200

24 2 Planning 2.5 How to Distribute Instances to Hosts for a Java Add-In Installation Figure 4: Distribution of Instances in a Java Add-In System Only valid for: HA (MSCS) Distribution of Instances for a Java Add-In Installation in an MSCS Configuration You install the instances as follows: 1. On the MSCS node where the ABAP central services (ASCS) instance is installed, you run SAPinst and 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. You can also install the dialog instance on a local disk on the MSCS node. Caution You cannot install the Java Add-In for the existing ABAP dialog instance(s). Instead, you have to install new ABAP+Java dialog instance(s). 24/200 PUBLIC 04/30/2008

25 2 Planning 2.6 Distribution of SAP System Components to Disks For more information, see High Availability with Microsoft Cluster Service [page 151] End of: HA (MSCS) 2.6 Distribution of SAP System Components to Disks When you install the SAP system, the main directories required for the system are automatically created. However, during the installation procedure, SAPinst prompts you to enter drive letters for the main components of the system. This gives you the opportunity to distribute components to disks in the system as you wish. How you do this significantly affects system throughput and data security, and must therefore be carefully planned. The best distribution depends on your specific environment and must take into consideration factors such as the size of the components involved, security requirements and the expected workload. When you work out the assignment of components to disks, you first need to get an overview of the main components and their corresponding directories. Then, on the basis of sample configurations and the recommendations provided in this documentation, you can decide which assignment is best for your particular system. The table below gives you an overview of the main SAP system components, directories, and their purpose. A good distribution to disks ensures that: Enough free space is available for system growth. The data is secure. Performance is good. System Components and their Directories Directory Type Directory Structure Description SAP System Database Management System (DBMS) SAP Database \usr\sap \usr\sap\trans \Program Files\Microsoft SQL Server \<SAPSID>DATA0 \<SAPSID>DATA1 \<SAPSID>DATA2 \<SAPSID>DATA3... \<SAPSID>DATA<N> SAP kernel and related files SAP transport directory SQL Server program files including the master, msdb and tempdb database files. Database data files <1-N> SAP Database Transaction Log \<SAPSID>log<N> Database transaction log files 04/30/2008 PUBLIC 25/200

26 2 Planning 2.6 Distribution of SAP System Components to Disks Database Components When you install an SAP system with MS SQL Sever, the central components of the database are the SQL Server program files, tempdb files, SAP database data files and SAP database transaction log files. The log files record all the changes made to the database to enable restore and recovery. The tempdb holds all temporary tables and stored procedures. The data files contain the data for the SAP system. SAP Database Data Files The data files are created by default in the directories \<SAPSID>DATA<n> on the disk with the most free available space. The first data file is called <SAPSID>DATA0.mdf and subsequent files <SAPSID>DATA<n>.ndf, where <n> denotes the number of the file. For performance reasons, locate the data files on a separate disk system. They should not be included in the same disk system as the log files or other SQL Server program and database files. To ensure data redundancy, we recommend the use of RAID 5. Transaction Log File The transaction log for the database is created by default in the directory\<sapsid>log1 on the disk with the most free available space. The log file is called <SAPSID>LOG1.ldf. The transaction log file records all the changes made to the database and, if required, enables modifications to be redone or undone. It plays a crucial role when the database has to be restored due to database damage or media failure. For this reason it should be stored very securely. We recommend the use of RAID 1, which implements hardware-based mirroring. Program Files The files other than the SAP database data and transaction log files are created in the subdirectories of \Program Files\Microsoft SQL Server. These include the SQL Server program files and the master, msdb and tempdb database files. Locate these on a separate, third, disk system and not on the same disks as the transaction log files or SAP database data files. We recommend the use of RAID 1. For performance reasons, it is advisable to place the tempdb files on a fast disk system. This is particularly recommended because the tempdb is frequently accessed during SQL Server operation and could otherwise affect performance. After the initial installation of the database software, the tempdb is located in a subdirectory of \Program Files\Microsoft SQL Server. However later, when SAPinst builds and loads the database, it is transferred to a new \TEMPDB directory and extended to a size of 300 MB. Distribution of Main Directories to RAID Array The following graphic illustrates how the main directories that are created during the installation can be distributed to RAID arrays. The distribution is suitable for an average-sized production system. Keep in mind that this is only an example and that no single solution is fitting for all environments. 26/200 PUBLIC 04/30/2008

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

28 2 Planning 2.7 SAP Directories 2.7 SAP Directories This section describes the directories that are available in an SAP system. Only valid for: HA (MSCS) If you want to install an MSCS system, see also Directories in an MSCS Configuration [page 160]. End of: HA (MSCS) SAPinst automatically creates the following directories during the installation: \usr\sap This directory is created on the: Global host and shared with the network share sapmnt Only valid for: non-ha The global host is the host where the SCS instance is installed. End of: non-ha Only valid for: HA (MSCS) The global host is the host where both the ASCS and the SCS instances are installed. End of: HA (MSCS) On global hosts, the \usr\sap directory contains general SAP software, global and local (instance-specific) data. For this, SAPinst creates the global directory usr\sap\<sapsid>\sys, which physically exists only once for each SAP system. It consists of the following subdirectories: global contains globally shared data profile contains the profiles for all instances exe contains executable replication directory for all instances and platforms Local host and shared with the name saploc. On local hosts, the \usr\sap\<sapsid>\<instance_name> directory contains copies of the SAP software and local (instance-specific) data. Since SAP traces for the instance are created in \usr\sap, make sure there is sufficient space available in this directory. Changes in SAP profiles can also affect the disk space. The executables on the local host are replicated from those on the global host every time the local instance is started. The SAP copy program sapcpe compares the binaries in the <platform> directory on the global host and the binaries in the exe directory on the application server. If the binaries in the exe directory are elder than those in the <platform> directory, sapcpe replaces them with the newer version of the global host. 28/200 PUBLIC 04/30/2008

29 2 Planning 2.7 SAP Directories Other application servers access the global data using the Universal Naming Convention (UNC) path \\<SAPGLOBALHOST>\sapmnt. The SAP programs access their instance-specific data with the UNC path \\<SAPLOCALHOST>\saploc. If the UNC path points to a local directory, the local path (and not the UNC path) is used to access the directory. The parameters SAPGLOBALHOST and SAPLOCALHOST have the same values on the global host. Only valid for: HA (MSCS) Windows Server 2008 only: In a high-availability system, file shares pointing to directories on shared disks are only visible or accessible with the virtual host name of the cluster group the shared disks belong to. This lets you have several shares with the same name pointing to different disks (multi-sid). End of: HA (MSCS) \usr\sap\trans The transport directory contains SAP software for the transport of objects between SAP systems. SAPinst by default creates it on the SAPGLOBALHOST. If you want to have it created on another host or if you want to use an existing transport host from your SAP system landscape, you can specify another host during the installation. In this case, you have to prepare that host for the new SAP system to use it. For more information, see Preparing the SAP System Transport Host [page 65]. Directory Structure The following figures show how the physical directory \usr\sap is shared on the global host in a central and in a distributed system. In both cases, the UNC paths are used as follows: \\<SAPGLOBALHOST>\sapmnt to access global directories \\<SAPLOCALHOST>\saploc to access local instance-specific data There is also a figure showing the directory structure of the Diagnostics Agent. SAPinst extracts the Diagnostics Agent to the directory /usr/sap/smd/j<instance_number>/smdagent. There are the following instance names available in an SAP system: Only valid for: HA (MSCS) Central services instance for ABAP: ASCS<Instance_Number>. End of: HA (MSCS) Central services instance: SCS<No> Central instance: DVEBMGS<Instance_Number> Dialog instance: D<Instance_Number>. 04/30/2008 PUBLIC 29/200

30 2 Planning 2.7 SAP Directories Every new installation of an SAP system is Unicode. Figure 6: Directory Structure on the Global Host in a Central ABAP+Java System 30/200 PUBLIC 04/30/2008

31 2 Planning 2.7 SAP Directories Figure 7: Directory Structures in a Distributed ABAP+Java System 04/30/2008 PUBLIC 31/200

32 2 Planning 2.7 SAP Directories Only valid for: HA (MSCS);HA (z/os) Figure 8: Directory Structure in a High-Availability ABAP+Java System End of: HA (MSCS);HA (z/os) Figure 9: Directory Structure of the Diagnostics Agent 32/200 PUBLIC 04/30/2008

33 2 Planning 2.8 SAP System Transport Host 2.8 SAP System Transport Host The transport host contains the transport directory that is used by the SAP transport system to store transport data and change information of SAP systems, such as software programs, data dictionary data, or customization data. If you have several SAP systems they are usually organized in transport domains. In most cases, all SAP systems in a transport domain have a common transport directory. For more information, see: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics Change and Transport System Change and Transport System Overview (BC-CTS) Basics of the Change and Transport System Transport Management System Concept When you install an SAP system, SAPinst by default creates the transport directory on the central instance host in \usr\sap\trans. Only valid for: HA (MSCS) In an MSCS configuration, SAPinst by default creates the transport directory on the (ABAP) central services instance host in \usr\sap\trans. End of: HA (MSCS) You have to prepare this host for use by the new SAP system if one of the following applies to you: You want to locate the transport directory on another host. You want to use an existing transport host and directory in your SAP system landscape. For more information, see Preparing the SAP System Transport Host [page 65]. More Information SAP Directories [page 28] 2.9 Basic SAP System Parameters The tables below list the basic system parameters that you need to determine before installing your SAP system. For all other SAP system parameters, use the F1 help in the SAPinst dialogs. In the column Enter Your Values, you write down the values that you plan to use, for example, the Message Port Number. 04/30/2008 PUBLIC 33/200

34 2 Planning 2.9 Basic SAP System Parameters SAP System ID and Database ID Parameters Description Enter Your Values SAP System ID <SAPSID> The SAP System ID <SAPSID> identifies the whole SAP system.... Database ID <DBSID> Caution Choose your SAP system ID carefully. You cannot change the SAP system ID after the installation. Make sure that your SAP system ID: Is unique throughout your organization Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs: ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID USR VAR The <DBSID> identifies the database instance. SAPinst prompts you for the <DBSID> when you are installing the database instance. The <DBSID> can be the same as the <SAPSID>.... Caution Choose your database ID carefully. Renaming is difficult and requires you to reinstall the SAP system. If you want to install a new database: Make sure that your database ID: Is unique throughout your organization Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs: ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID USR VAR If you want to use an existing database system: 34/200 PUBLIC 04/30/2008

35 2 Planning 2.9 Basic SAP System Parameters Parameters Description Enter Your Values Enter exactly the database ID of the existing database to which you want to add the system. System ID <SMDSID> of SAP Solution Manager Diagnostics Agent SAPinst sets <SMDSID> to SMD by default. If SMD is already used by another SAP system that is not a Diagnostics Agent system, <SMDSID> is set to DA<x>, where <x> can be any letter from A to Z, and DA stands for DiagnosticsAgent ). If required, you can change <SMDSID> to a value of your choice on the Parameter Summary screen. If you do so, the same naming conventions as for <SAPSID> apply. For more information, see entry SAP System ID <SAPSID> in this table above.... Only valid for: No Source Release;SAP CRM 5.0;SAP SCM 5.0;SAP SRM Server 5.5 Unicode or Non-Unicode System Parameters Description Enter Your Values Unicode System End-to-End Root Cause Analysis requires an SAP Solution Manager 7.0 with AS ABAP and AS Java in one SAP system. We recommend that you run SAP Solution Manager on Unicode. Every new installation of SAP Solution Manager 7.0 is Unicode. For customers that have upgraded from SAP Solution Manager 3.1 and 3.2 and are not yet on Unicode, we recommend to perform a Unicode conversion. If this is not possible, SAP will support End-to-End Root Cause Analysis with an ABAP stack on non-unicode as of SAP Solution Manager 7.0 SP13, until the customer has completed the Unicode conversion. For more information, see End of: No Source Release;SAP CRM 5.0;SAP SCM 5.0;SAP SRM Server 5.5 SAP System Instances, Hosts and Ports Parameters Description Enter Your Values Instance Number of the SAP system Technical identifier for internal processes. It consists of a two-digit number from 00 to 98. The instance number must be unique on a host. That is, if more than one SAP instance is running on the same host, these instances must be assigned different numbers /30/2008 PUBLIC 35/200

36 2 Planning 2.9 Basic SAP System Parameters Parameters Description Enter Your Values To find out this number, look under the SAP directory <Drive>:\usr\sap\<SAPSID>\DVEBMGS<nn> on the host of the central instance. The value <nn> is the number assigned to the central instance. Caution Do not use 43, and 89 for the instance number because: 43 is used by MSCS 89 is used by Windows Terminal Server Instance Number for the Diagnostics Agent Name of Instance Host Virtual Host Name Message Server Port Technical identifier for internal processes for the Diagnostics Agent, consisting of a two-digit number from 00 to 98. The instance number is set automatically to the next free and valid instance number that has not yet been assigned to the SAP system. The same restrictions apply as in Instance Number of the SAP system (see above). Instance Host: Host name of the specific instance. To find out the host name, open a command prompt and enter hostname. The host name must not exceed 12 characters. For more information about the allowed host name length and characters, see SAP You can use one or more virtual TCP / IP host names for SAP servers within an SAP server landscape to order to conceal their physical network identities from each other. This may be useful when moving SAP servers or complete server landscapes to other new hardware within a short time frame without having to carry out a reinstallation or complicated reconfiguration. Only valid for: HA (MSCS) Virtual host names are also required for a high-availability (HA) system where you need to specify the virtual host name, which is used by the (A)SCS instance. End of: HA (MSCS) For more information about the use of virtual TCP/IP host names, see SAP For more information about the allowed host name length and characters, see SAP Caution The message server port number must be unique for the SAP system on all hosts. If there are several message port numbers on one host, all must be unique. Port number of the SAP Message Server: If you do not specify a value, the default port number is used /200 PUBLIC 04/30/2008

37 2 Planning 2.9 Basic SAP System Parameters Parameters Description Enter Your Values ABAP Message Server Port There is an external message server port and an internal message server port. The ABAP message server uses both the internal and the external message server ports. The default profile contains the configuration for both message server ports. The external message server port uses the parameter rdisp/msserv with default value 36<nn>, where <nn> is the instance number of the ABAP message server instance. The internal message server port uses the parameter rdisp/msserv_internal with default value 39<nn>, where <nn> is the instance number of the ABAP message server instance. Java Message Server Port The Java message server only uses the internal message server port. The SCS instance profile contains the configuration for the Java message server. The parameter rdisp/msserv is set to 0, so that the external port is not open. The internal message server port uses the parameter rdisp/msserv_internal with default value 39<nn>, where <nn> is the instance number of the SCS message server instance. For more information about the parameters used for message server ports, see SAP Master Password Parameters Description Enter Your Values Master Password This password is used for all user accounts SAPinst creates and for the secure store key phrase. The length has to be 8 to 14 characters. Depending on your installation scenario there might be more restrictions.... Caution If 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 the master password meets the requirements of your operating system and of your database. 04/30/2008 PUBLIC 37/200

38 2 Planning 2.9 Basic SAP System Parameters Operating System Users Parameters Description Enter Your Values Password of Operating System Users SAPinst processes the passwords of operating system users as follows: If the operating system users do not exist, SAPinst creates the following users: <sapsid>adm This user is the SAP system administrator user and is a member of the local Administrators group. SAPService<SAPSID> This user is the Windows account to run the SAP system. It is not a member of the local Administrators group. <smdsid>adm This user is dedicated to the Diagnostics Agent installation with sufficient authorization to manage the agent. It is created on the central instance host and on every dialog instance host. SAPinst sets the master password for these users by default. You can overwrite and change the passwords either by using the parameter mode Custom or by changing them on the parameter summary screen. If the operating system users already exist, SAPinst prompts you for the existing password, except if the password of these users is the same as the master password.... Caution Make sure that you have the required user authorization [page 61] for these accounts before you start the installation. User Management Engine (UME) Parameter Description Enter Your Values ABAP Client The production client of the ABAP system... DDIC Password Caution This parameter is only prompted if you install the Java Add-In for an existing ABAP system. The existing password of the DDIC user... Caution This parameter is only prompted if you install the Java Add-In for an existing ABAP system. 38/200 PUBLIC 04/30/2008

39 2 Planning 2.9 Basic SAP System Parameters Parameter Description Enter Your Values Java Administrator User Java Guest User Communication User This user has administrative permissions for user management. After the installation, this user is available both in the ABAP and in the Java system SAPinst sets the user name J2EE_ADMIN and the master password by default. For more information about supported UME data sources and change options, see SAP This user is used for anonymous access. After the installation, it is available both in the ABAP and in the Java system SAPinst sets the user name J2EE_GUEST and the master password by default. For more information about supported UME data sources and change options, see SAP This user is created by SAPinst in the ABAP system. After the installation, it is available both in the ABAP and in the Java system This user is used for the communication between the ABAP system and the Java system. SAPinst sets the user name SAPJSF and the master password by default. For more information about supported UME data sources and change options, see SAP Key Phrase for Secure Store Settings Parameters Description Enter Your Values Key Phrase for Secure Store Settings This is a random word or phrase that is used to encrypt the secure store. The Java EE engine uses this phrase to generate the key that is used to encrypt the data. The uniqueness of the phrase you use contributes to the uniqueness of the resulting key.... Recommendation Use a long key phrase that cannot be guessed easily. Use both uppercase and lowercase letters in the phrase and include special characters. 04/30/2008 PUBLIC 39/200

40 2 Planning 2.9 Basic SAP System Parameters Internet Communication Manager (ICM) User Management Parameter Description Enter Your Values Password of webadm The administration user webadm is created to use the web administration interface for Internet Communication Manager (ICM) and Web Dispatcher. SAPinst sets the master password by default. If required, you can choose another password. The length of the password must be between 5 and 128 characters.... Parameters Relevant for the Connectivity to System Landscape Directory (SLD) Parameters SLD Destination Description The System Landscape Directory (SLD) is designed for registering the systems (along with the installed software) of your whole system landscape. The usual case is to configure one SLD for your complete system landscape. You can choose between the following options: Register in existing central SLD Select this option to register the SAP system you are installing in an existing SAP System Landscape Directory (SLD) by specifying the SLD connection parameters below. Configure a local SLD Select Configure a local SLD if you want to use the local SLD on the J2EE engine of the SAP system that you are installing. Enter Your Values... Caution We strongly recommend that you install a local SLD on the SAP Solution Manager system with connection and replication from the productive SLD instances in your existing landscape. For more information, see System Landscape Directory [page 20]. For more information, see Initial Technical Configuration for the System Landscape Directory (SLD) [page 143]. SLD HTTP Host The host name of the System Landscape Directory (SLD)... SLD HTTP Port The HTTP port of the Java system where the SLD is installed. The following naming convention applies: 5<instance_number> Example If the instance number of your Java system is 01, the SLD HTTP Port is /200 PUBLIC 04/30/2008

41 2 Planning 2.9 Basic SAP System Parameters Parameters SLD Data Supplier User and password Description If you want to install a local SLD, SAPinst creates this user during the installation. If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation. Enter Your Values... SLD ABAP API User and password Recommendation We recommend that you name this user SLDDSUSER If you want to install a local SLD, SAPinst creates this user during the installation. If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation.... Recommendation We recommend that you name this user SLDAPIUSER RFC User, Password The ABAP RFC user of the SLD... SLD Gateway Host The host on which the gateway instance of the SLD is running... SLD Gateway Instance Number The instance number of the gateway instance of the SLD... SAP System Client The client in which the ABAP RFC user exists... Parameters Relevant for Adobe Document Services (ADS) Parameters Description Enter Your Values User for basic authentication User for processing forms between an ABAP and a Java environment SAPinst sets the user name ADSUSER and the master password by default. If required, you can choose another password according to your requirements. SAPinst sets the user name ADSAGENT and the master password by default. If required, you can choose another password according to your requirements /30/2008 PUBLIC 41/200

42 2 Planning 2.10 Running Adobe Document Services on Nonsupported Platforms Parameters for SAPDATA Drives Parameters Description Enter Your Values Installation drive Base directory for the SAP system. Do not add <SAPSID> as subdirectory because the system adds this directory automatically.... Example If you enter D:, the system adds the directory D:\usr\sap\SAPSID. If you install a subsequent SAP system, the saploc share already exists and you cannot select the installation drive. SAPinst uses the installation drive where the saploc share points to. Parameters Relevant for the Database Parameters Description Enter Your Values Database instance name MS SQL Server instance name You can also specify a remote database instance. Dependencies For a named instance, enter <hostname>\<instance_name>. Only valid for: HA (MSCS) In an MSCS environment, enter the virtual host name. End of: HA (MSCS) Running Adobe Document Services on Nonsupported Platforms Adobe document services (ADS) are currently supported on a limited set of 64-bit platforms for SAP NetWeaver. Procedure To use ADS in SAP landscapes on nonsupported platforms, you have to install an additional standalone SAP system with AS Java on a platform supported by ADS. 42/200 PUBLIC 04/30/2008

43 2 Planning 2.11 Installing SAP Solution Manager Diagnostics in an Existing SAP Solution Manager ABAP System For more information, see SAP Installing SAP Solution Manager Diagnostics in an Existing SAP Solution Manager ABAP System You want to install the Java-based SAP Solution Manager Diagnostics in an existing SAP Solution Manager ABAP system upgraded to SAP Solution Manager 7.0. For example, you need SAP Solution Manager Diagnostics if you want to implement the End-to-End Root Cause Analysis scenario. For more information, see the Root Cause Analysis Installation and Upgrade Guide which you can find at one of the following: End-to-End Root Cause Analysis Documentation Library Installation and Configuration Root Cause Analysis Installation and Upgrade Guide SAP Components SAP Solution Manager <Current Release> Prerequisites Your ABAP system must have at least the support package level of SAP Solution Manager 7.0 ABAP (SPS 15). Procedure 1. Prepare [page 45] the existing ABAP system for the installation of the Java Add-in. 2. Install the Java Add-In using SAPinst as described in Installing the Java Add-In for an Existing ABAP System [page 92]. 3. Perform post-installation [page 103] steps for the Java Add-In. 4. Install SAP Solution Manager Diagnostics using Java Support Package Manager (JSPM) as described in Installation of Additional Software Units or Usage Types in an Existing SAP System [page 133]. More Information We recommend that you run SAP Solution Manager on Unicode. For customers that have upgraded from SAP Solution Manager 3.1 and 3.2 and are not yet on Unicode, we recommend that you perform a Unicode conversion. For more information, see 04/30/2008 PUBLIC 43/200

44 This page is intentionally left blank.

45 3 Preparation 3 Preparation In a central system, all mandatory instances are installed on one host. Therefore, if you are installing a central system, you can ignore references to other hosts. You have to complete the following preparations: 1. You check the hardware and software requirements [page 45] on each host. 2. You check the Windows file system [page 59] on each host. 3. You check that your installation host belongs do the correct Windows domain [page 60]. 4. You reduce the size of the file cache [page 61] on each host. This step is not required if you use Windows Server You check that you have the required user authorization for the installation [page 61]. 6. If required, you perform a domain installation without being a domain administrator [page 63]. 7. If required, you prepare the SAP system transport host [page 65] for your SAP system. 8. You install the SAP front-end software [page 67] on the desktop of the end user. 9. You install the Java Development Kit [page 67]. 10. You make the installation DVDs available [page 68] on each host. 11. If required, you download the installation DVDs from SAP Service Marketplace [page 70]. Only valid for: HA (MSCS) 12. For the installation of a high-availability system with Microsoft Cluster Service (MSCS), in addition, you have to perform MSCS-specific preparation tasks [page 167]. End of: HA (MSCS) 3.1 Hardware and Software Requirements You check that your hosts meet the hardware and software requirements for your operating system and the SAP instances. Caution If your hosts do not fully meet the requirements, you might experience problems when working with the SAP system. 04/30/2008 PUBLIC 45/200

46 3 Preparation 3.1 Hardware and Software Requirements Prerequisites Contact your OS vendor for the latest OS patches. Make sure that the host name meets the requirements listed in SAP Process Flow 1. Check the Product Availability Matrix for supported operating system releases, see at SAP Technology Components SAP SOLUTION MANAGER <Current Release>. 2. Check the hardware and software requirements using: The Prerequisite Checker: Standalone (optional) before the installation process For more information, see Running the Prerequisite Checker Standalone [page 47]. Integrated in SAPinst (mandatory) as part of the installation process For more information, see Running SAPinst on Windows [page 85] For the most recent updates to the Prerequisite Checker, always check SAP The hardware and software requirements checklists for: Central system [page 47] Distributed system [page 50] Only valid for: HA (MSCS) High availability system with MSCS [page 54] End of: HA (MSCS) If you want to install dialog instance(s), check the requirements for a dialog instance [page 59]. If you want to use 32-bit SAP NetWeaver components, first check whether these components can run on 64-bit operating systems. If so, we recommend you to use 64-bit systems. If not, you can install an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP instances, you must use 64-bit systems. 3. If you are installing a production system, the values provided by the Prerequisite Checker and the hardware and software requirements checklists are not sufficient. In addition, check the precise sizing values in the Sizing Guide Sizing SAP Solution Manager <Current Release>, which is available at: SAP Components SAP Solution Manager <Current Release> 46/200 PUBLIC 04/30/2008

47 3 Preparation 3.1 Hardware and Software Requirements Running the Prerequisite Checker in Standalone Mode (Optional) Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check the hardware and software requirements for your operating system (OS) and the SAP instances. When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks the hardware and software requirements in the background. Prerequisites You have installed the correct Java Development Kit (JDK) [page 67]. You have prepared the installation master DVD on the required installation host [page 68]. Procedure 1. You start SAPinst [page 85]. 2. On the Welcome screen, choose <Your SAP product> Software Life-Cycle Options Additional Preparation Options Prerequisites Check. 3. Follow the instructions in the SAPinst dialogs and enter the required parameters. For more information about each parameter, position the cursor on the parameter field and choose F1 in SAPinst. When you have finished, the Parameter Summary screen appears summarizing all parameters you have entered. If you want to make a change, select the relevant parameters and choose Revise. 4. To start the Prerequisite Checker, choose Start. Result The Prerequisite Check Results screen displays the results found. If required, you may also check the results in file prerequisite_checker_results.html, which you find in the installation directory Requirements for a Central System If you want to install a central system, where all instances reside on one host, this host must meet the following requirements: 04/30/2008 PUBLIC 47/200

48 3 Preparation 3.1 Hardware and Software Requirements The listed values are sufficient for development systems or quality assurance systems but not for production systems. Hardware Requirements for a Central System Hardware Requirement Requirement Minimum disk space Database Software: 4 GB SAP system files (not including paging file): 5 GB (x64) 8 GB (IA64) SAP database files (not including paging file): 33 GB 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk How to Check To check disk space: 1. Choose Start Control Panel Administrative Tools Computer Management Storage Disk Management. 2. Right-click the drive and choose Properties. Minimum RAM 6 GB To check RAM: In the Windows Explorer, choose Help About Windows. Paging file size 1 times RAM plus 8 GB To check paging file size: 1. Choose Start Control Panel System. 2. Choose Advanced (Windows Server 2003) or Advanced system settings (Windows Server 2008). 3. Select Performance Settings Advanced. 4. If required, in section Virtual memory, choose Change. Suitable backup system Software Requirements for a Central System Software Requirement Requirement How to Check Windows operating system English international 64-bit version of one of the following Windows Server Editions: Windows Server 2003 Windows Server 2003 Standard Edition Windows Server 2003 Enterprise Edition Windows Server 2003 Datacenter Edition To check your Windows version: 1. Choose Start All Programs Accessories Command Prompt 2. Enter the command winver 48/200 PUBLIC 04/30/2008

49 3 Preparation 3.1 Hardware and Software Requirements Software Requirement Requirement How to Check Windows Server 2008 Windows Server 2008 Standard Edition Windows Server 2008 Enterprise Edition Windows Server 2008 Datacenter Edition Windows Server 2008 for Itanium-Based Systems Edition Caution When this guide was published, Windows Server 2008 had not yet been released for your SAP system. For up-to-date information on the released operating system versions for your SAP product and database, see the Product Availability Matrix (PAM) at Database software For any version of Windows Server, you need the latest supported service pack A suitable Windows Resource Kit is strongly recommended One of the following SQL Server Enterprise Edition server software: MS SQL Server 2005 Enterprise Edition: Server Software MS SQL Server 2008 Enterprise Edition: Server Software Caution When this guide was published, SQL Server 2008 was not yet released. For up-to-date information on the released database versions for your SAP product, see the Product Availability Matrix (PAM) at MS SQL Server 2000 Enterprise Edition: Server Software Caution For technical and support reasons, we do not recommend using the MS SQL Server 2000 Enterprise Edition. Instead use MS SQL Server 2005 or higher. Latest service pack and hotfix, if available 04/30/2008 PUBLIC 49/200

50 3 Preparation 3.1 Hardware and Software Requirements Software Requirement Requirement How to Check For more information, see SAP For SQL Server 2000, see also SAP Unicode collation SQL_Latin1_General_CP850_BIN Requirements for a Distributed System This section provide information about the hardware and software requirements in a distributed system, where the SAP instances can reside on different hosts. The tables show the requirements for the: Central services instance Database instance Central instance Dialog instance (optional) The listed values are sufficient for development systems or quality assurance systems but not for production systems. If you install several SAP instances on one host, you need to add up the requirements. Hardware Requirements for a Distributed System Hardware Requirement Requirement How to Check Minimum disk space Database software: 4 GB Central services instance (SCS) (not including paging file): 5 GB (x64) 8 GB (IA64) Database instance (not including paging file): 33 GB Central instance (not including paging file): 5 GB (x64) 8 GB (IA64) In addition you require 4 GB (x64), or 8 GB (IA64) per additional platform. To check disk space: 1. Choose Start Control Panel Administrative Tools Computer Management Storage Disk Management. 2. Right-click the drive and choose Properties. 50/200 PUBLIC 04/30/2008

51 3 Preparation 3.1 Hardware and Software Requirements Hardware Requirement Requirement How to Check Up to 2 GB for each usage type or software unit you want to install. Dialog instance (optional) (not including paging file): 2.5 GB (x64) 5 GB (IA64) Temporary disk space for every required installation DVD that you have to copy to a local hard disk: 4.3 GB Minimum RAM 3 GB To check RAM: In the Windows Explorer, choose Help About Windows. Paging file size Central services instance (SCS): 1 times RAM plus 1 GB Database instance: 1.5 times RAM Central instance: 1 times RAM plus 8 GB Dialog instance (optional): 1 times RAM plus 8 GB To check paging file size: 1. Choose Start Control Panel System. 2. Choose Advanced (Windows Server 2003) or Advanced system settings (Windows Server 2008). 3. Select Performance Settings Advanced. 4. If required, in section Virtual memory, choose Change. Suitable backup system Software Requirements for a Distributed System Software Requirement Requirement How to Check Windows operating system English international 64-bit version of one of the following Windows Server Editions: Windows Server 2003 Windows Server 2003 Standard Edition Windows Server 2003 Enterprise Edition Windows Server 2003 Datacenter Edition Windows Server 2008 Windows Server 2008 Standard Edition Windows Server 2008 Enterprise Edition Windows Server 2008 Datacenter Edition Windows Server 2008 for Itanium-Based Systems Edition To check your Windows version: 1. Choose Start All Programs Accessories Command Prompt 2. Enter the command winver 04/30/2008 PUBLIC 51/200

52 3 Preparation 3.1 Hardware and Software Requirements Software Requirement Requirement How to Check Caution When this guide was published, Windows Server 2008 had not yet been released for your SAP system. For up-to-date information on the released operating system versions for your SAP product and database, see the Product Availability Matrix (PAM) at For any version of Windows Server, you need the latest supported service pack A suitable Windows Resource Kit is strongly recommended Database software Central services instance (SCS), central instance or dialog instance: One of the following SQL Server client software: SQL Server 2005: MS SQL Server 2005 Native Access Client (SNAC) software Latest service pack and hotfix, if available. For more information, see SAP SQL Server 2008: MS SQL Server 2008 Native Access Client (SNAC) software Latest service pack and hotfix, if available. For more information, see SAP Caution When this guide was published, SQL Server 2008 was not yet released. For up-to-date information on the released database versions for your SAP product, see the Product Availability Matrix (PAM) at SQL Server 2000: MS SQL Server 2000 Enterprise Edition: Client Tools Only Latest service pack and hotfix, if available. For more information, see SAP s and Caution For technical and support reasons, we do not 52/200 PUBLIC 04/30/2008

53 3 Preparation 3.1 Hardware and Software Requirements Software Requirement Requirement How to Check recommend using the MS SQL Server 2000 Enterprise Edition. Instead use MS SQL Server 2005 or higher. Database instance: One of the following SQL Server Enterprise Edition server software: MS SQL Server 2005 Enterprise Edition: Server Software Latest service pack and hotfix, if available. For more information, see SAP Unicode collation SQL_Latin1_General_CP850_BIN2 MS SQL Server 2008 Enterprise Edition: Server Software Caution When this guide was published, SQL Server 2008 was not yet released. For up-to-date information on the released database versions for your SAP product, see the Product Availability Matrix (PAM) at Latest service pack and hotfix, if available. For more information, see SAP Unicode collation SQL_Latin1_General_CP850_BIN2 MS SQL Server 2000 Enterprise Edition: Server Software Caution For technical and support reasons, we do not recommend using the MS SQL Server 2000 Enterprise Edition. Instead use MS SQL Server 2005 or higher. Latest service pack and hotfix, if available. For more information, see SAP s and Unicode collation SQL_Latin1_General_CP850_BIN2 For more information about the collation for MS SQL Server 2000, see SAP /30/2008 PUBLIC 53/200

54 3 Preparation 3.1 Hardware and Software Requirements Only valid for: HA (MSCS) Requirements for a High-Availability System This section provides information about the hardware and software requirements in a high-availability system. 1. Windows Server 2003 only: You must check that your cluster hardware is certified. AddOn Technology Center for SAP (Add On TCS) certifies hardware platforms for SAP on Microsoft Windows. The cluster must be included in the Microsoft list of certified clusters and its components. You can access the lists as follows: Windows Server 2008 only: a) Check that your cluster hardware is certified for Windows Server 2008 and has the Windows Server 2008 logo. b) You must validate your failover cluster configuration by running the Validate a Configuration Wizard, which is included in the Failover Cluster Management snap-in. The Failover Cluster Validation Report must not show any warnings and errors. 3. The MSCS nodes of the cluster must be connected by a private and public network: The public network enables communication from the MSCS nodes of the cluster to other resources in the local area network (LAN). The private network enables internal communication between the MSCS nodes. In particular, it enables the Cluster Service running on all MSCS nodes to regularly exchange messages on the state of the MSCS nodes so that the failure of resources is quickly detected. 4. Each of the MSCS nodes in the cluster must have its own local disks and have access to shared disks that can be reached by the MSCS nodes via a shared bus. All software except the Windows operating system, the MS SQL server binaries, and the MSCS software is stored on the shared disks. One of the shared disks must be used exclusively by the quorum (if a single quorum device cluster is used) that stores the cluster registry and records information about the state of the cluster. You require at least four shared disks. For more information about the distribution of components to local and shared disk, see Distribution of Components to Disks for MSCS [page 158]. 54/200 PUBLIC 04/30/2008

55 3 Preparation 3.1 Hardware and Software Requirements Caution All disk controllers must be able to support hardware-based RAID. You cannot use a host with a domain controller as an MSCS cluster node. The following tables show the hardware and software requirements for the: ABAP central services instance (ASCS) Central services instance (SCS) Database instance Enqueue Replication Server instance (ERS) Central instance Dialog instance The listed values are sufficient for development systems or quality assurance systems but not for production systems. If you install several SAP instances on one host, you need to add up the requirements. Hardware Requirements for a High-Availability System Hardware Requirement Requirement How to Check Minimum disk space Database Software: 4 GB ABAP central services instance (ASCS) (not including paging file): 5 GB (x64) 8 GB (IA64) In addition you require 4 GB (x64), or 8 GB (IA64) per additional platform. Up to 2 GB for each usage type or software unit you want to install. Central services instance (SCS) (not including paging file): 5 GB (x64) 8 GB (IA64) Database instance (not including paging file): Enqueue replication server instance (ERS) (not including paging file): 5 GB (x64) 8 GB (IA64) Central instance (not including paging file): 2.5 GB (x64) 5 GB (IA64) To check disk space: 1. Choose Start Control Panel Administrative Tools Computer Management Storage Disk Management. 2. Right-click the drive and choose Properties. 04/30/2008 PUBLIC 55/200

56 3 Preparation 3.1 Hardware and Software Requirements Hardware Requirement Requirement How to Check In addition you require 4 GB (x64), or 8 GB (IA64) per additional platform. Up to 2 GB for each usage type or software unit you want to install. Dialog instance (not including paging file): 2.5 GB (x64) 5 GB (IA64) Temporary disk space for every required installation DVD that you have to copy to a local hard disk: 4.3 GB Minimum RAM Paging file size 3 GB To check RAM: In the Windows Explorer, choose Help About Windows. ABAP central services instance (ASCS): 1 times RAM plus 1 GB Central services instance (SCS): 1 times RAM plus 1 GB Database instance: 1.5 times RAM Enqueue replication server instance (ERS): 1 times RAM plus 1 GB Central instance: 1 times RAM plus 8 GB Dialog instance: 1 times RAM plus 8 GB To check paging file size: 1. Choose Start Control Panel System. 2. Choose Advanced (Windows Server 2003) or Advanced system settings (Windows Server 2008). 3. Select Performance Settings Advanced. 4. If required, in section Virtual memory, choose Change. You must adjust the size of the paging file on all MSCS nodes. Suitable backup system Software Requirements for a High Availability System Software Requirement Requirement How to Check Windows operating system English international 64-bit version of one of the following Windows Server Editions: Windows Server 2003 Windows Server 2003 Enterprise Edition Windows Server 2003 Datacenter Edition To check your Windows version: 1. Choose Start All Programs Accessories Command Prompt 2. Enter the command winver 56/200 PUBLIC 04/30/2008

57 3 Preparation 3.1 Hardware and Software Requirements Software Requirement Requirement How to Check Windows Server 2008 Windows Server 2008 Enterprise Edition Windows Server 2008 Datacenter Edition Windows Server 2008 for Itanium-Based Systems Edition Caution When this guide was published, Windows Server 2008 had not yet been released for your SAP system. For up-to-date information on the released operating system versions for your SAP product and database, see the Product Availability Matrix (PAM) at Windows Server 2003 only: You must set up the MSCS Cluster Service as described in the Microsoft documentation. During this setup you are asked for a Windows Domain Account to run the Cluster Service. We strongly recommend creating an account different from the <sapsid>adm user, for example ClusterServiceuser=sapprdcladm, where Clustername=sapprdcl. Windows Server 2008 only: You must add the operating system feature Failover Clustering on all MSCS nodes. Database software For any version of Windows Server, you need the latest supported service pack A suitable Windows Resource Kit is strongly recommended ABAP central services instance (ASCS), central services instance (SCS), central instance, or dialog instance: One of the following SQL Server client software: SQL Server 2005: MS SQL Server 2005 Native Access Client (SNAC) software Latest service pack and hotfix, if available. For more information, see SAP SQL Server 2008: MS SQL Server 2008 Native Access Client (SNAC) software Latest service pack and hotfix, if available. For more information, see SAP Caution When this guide was published, SQL Server 2008 was not yet released. For up-to-date information on the released 04/30/2008 PUBLIC 57/200

58 3 Preparation 3.1 Hardware and Software Requirements Software Requirement Requirement How to Check database versions for your SAP product, see the Product Availability Matrix (PAM) at: service.sap.com/pam SQL Server 2000: Caution For technical and support reasons, we do not recommend using the MS SQL Server 2000 Enterprise Edition. Instead use MS SQL Server 2005 or higher. MS SQL Server 2000 Enterprise Edition: Client Tools Only Latest service pack and hotfix, if available. For more information, see SAP s and Database instance: One of the following SQL Server Enterprise Edition server software: MS SQL Server 2005 Enterprise Edition: Server Software Latest service pack and hotfix, if available. For more information, see SAP Unicode collation SQL_Latin1_General_CP850_BIN2 MS SQL Server 2008 Enterprise Edition: Server Software Caution When this guide was published, SQL Server 2008 was not yet released. For up-to-date information on the released database versions for your SAP product, see the Product Availability Matrix (PAM) at: Latest service pack and hotfix, if available. 58/200 PUBLIC 04/30/2008

59 3 Preparation 3.2 Checking the Windows File System Software Requirement Requirement How to Check For more information, see SAP Unicode collation SQL_Latin1_General_CP850_BIN2 MS SQL Server 2000 Enterprise Edition: Server Software Caution For technical and support reasons, we do not recommend using the MS SQL Server 2000 Enterprise Edition. Instead use MS SQL Server 2005 or higher. Latest service pack and hotfix, if available. For more information, see SAP s and Unicode collation SQL_Latin1_General_CP850_BIN2 For more information on the collation for MS SQL Server 2000, see SAP End of: HA (MSCS) Requirements for the Dialog Instance For more information about the hardware and software requirements for the dialog instance(s), see one of the following sections: Requirements for a Distributed System [page 50] Only valid for: HA (MSCS) Requirements for a High-Availability System [page 54] End of: HA (MSCS) 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 to install the SAP system and database. NTFS supports full Windows security and long file names. 04/30/2008 PUBLIC 59/200

60 3 Preparation 3.3 Checking the Windows Domain Structure You must use NTFS for an SAP system installation. Do not install the SAP directories on a FAT partition. Procedure 1. Open the Windows Explorer. 2. Select the relevant disk 3. Choose Properties General. The system displays the type of file system in use. 4. Check that the file system is NTFS. 3.3 Checking the Windows Domain Structure 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: Extra domain In this model, the SAP system is embedded in its own domain, which is specially defined for SAP. A second 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. Single domain In this model, the SAP system and the user accounts are included in a single domain. Prerequisites You are performing a domain installation. 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 where the domain controller is installed. Procedure For a domain installation, we recommend that you check that all SAP system and database hosts are members of a single Windows domain. We recommend this for all SAP system setups. 60/200 PUBLIC 04/30/2008

61 3 Preparation 3.4 Reducing the Size of the File Cache 3.4 Reducing the Size of the File Cache This step is not required if you use Windows Server The Windows file cache directly competes with SAP programs for memory. Therefore, you should adjust the file cache as described below. Only valid for: HA (MSCS) In an MSCS configuration, you must adjust the size of the file cache on all MSCS nodes. End of: HA (MSCS) 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. Select Maximize data throughput for network applications. Caution If you cannot select File and Printer Sharing for Microsoft Networks, this option has not yet been installed. To install it, you need the Windows Server CDs. 5. To confirm your entries, choose OK. 3.5 Required User Authorization for the Installation Although SAPinst automatically grants the rights required for the installation to the user account used for the installation, you have to check whether this account has the required authorization to perform the installation. The authorization required depends on whether you intend to perform a domain or local installation. If necessary, you have to ask the system administrator to grant the account the necessary authorization before you start the installation. If you attempt the installation with an account that has not the required authorization, the installation aborts. This section informs you about the authorization required for a domain and a local installation. Caution Do not use the user <sapsid>adm for the installation of the SAP system. 04/30/2008 PUBLIC 61/200

62 3 Preparation 3.5 Required User Authorization for the Installation Domain Installation For a domain installation the account used for the installation needs to be a member of the local Administrators and the domain Admins group of the domain involved. All machines in the system must belong to the same domain. In a domain installation, the user information is stored centrally on the domain controller and is accessible to all hosts in the system. If the SAP system is to be distributed across more than one machine, SAP strongly recommends you to perform a domain installation to avoid authorization problems. Caution If you install a distributed system as a local installation, this can lead to authorization problems for the operating system users <sapsid>adm and SAPService<SAPSID>. It can also lead to problems with the transport directory, which is usually shared by several SAP systems. Therefore, SAP does not support a local installation for a distributed system and recommends you to install a distributed system as a domain installation. If you still want to perform a local installation for a distributed system, make sure that: You use the same password for the <sapsid>adm or the SAPService<SAPSID> user on all hosts. The password for the <sapsid>adm and SAPService<SAPSID> user can differ. You use the same master password on all hosts. All hosts belong to the same Windows work group. Only valid for: HA (MSCS) In an MSCS configuration, you always have to perform a domain installation. End of: HA (MSCS) For performance and security reasons, SAP does not support an SAP system installation on a domain controller. If for any reason, the account used for the installation is not a member of the domain Admins group, you can perform the installation with a domain user who is a member of the local Administrators group. However, the domain administrator has to prepare the system appropriately for you. For more information, see Performing a Domain Installation without being a Domain Administrator [page 63]. For a domain installation, you need to: 1. Check that the account used for the installation is a member of the domain Admins group. 2. If required, obtain these rights by asking the system administrator to enter the account as a member of the domain Admins group. Local Installation For a local installation the account used for the installation needs to be a member of the local Administrators group of the machine involved. In a local installation, all Windows account information is stored locally on one host and is not visible to any other hosts in the system. 62/200 PUBLIC 04/30/2008

63 3 Preparation 3.6 Performing a Domain Installation Without Being a Domain Administrator If the SAP system is to run on a single machine, you can perform a local installation. For a local installation, you need to: 1. Check that the account used for the installation is a member of the local Administrators group. 2. If required, obtain these rights by asking the system administrator to enter the account as a member of the local Administrators group. 3.6 Performing a Domain Installation Without Being a Domain Administrator You normally perform a domain installation of the SAP system with a user who is a member of the domain Admins group, as described in Required User Authorization for the Installation [page 61]. If for any reason, the account used for the installation is not a member of the domain Admins group, you can perform the installation with a domain user who is a member of the local Administrators group. In this case, the domain administrator has to prepare the system appropriately for you. The domain administrator can perform the following steps either using SAPinst or manually: 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. Prerequisites You must be domain administrator to perform the required steps. Windows Server 2008 only: You must have installed the feature Remote Server Administration Tools as follows: 1. Choose Start Administrative Tools Server Manager. 2. In the Server Manager windows, select Features. 3. Select the feature Remote Server Administration Tools Role Administration Tools Active Directory Domain Services Tools. Creating the Required Uses and Groups Using SAPinst On the host where the SAP system is to be installed, the domain administrator runs SAPinst [page 85] and chooses Software Life-Cycle Options Additional Preparation Options Operating System and Users to have the group and users created automatically. Creating the Required Uses and Groups Manually Creating the New Global Group SAP_<SAPSID>_GlobalAdmin 1. Log on as domain administrator. 04/30/2008 PUBLIC 63/200

64 3 Preparation 3.6 Performing a Domain Installation Without Being a Domain Administrator 2. To start the Active Directory Users and Computers Console, choose: Start Control Panel Administrative Tools Active Directory Users and Computers Windows Server 2003 only: 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 Enter the SAP_<SAPSID>_GlobalAdmin group exactly as specified in the correct uppercase and lowercase. 5. Select the following: a) Group scope: Global b) 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: Enter the <sapsid>adm and SAPService<SAPSID> user exactly as specified in the correct uppercase and lowercase. Field Input for <sapsid>adm Input for SAPService<SAPSID> First name: None None Initials: None None Last name: None None 64/200 PUBLIC 04/30/2008

65 3 Preparation 3.7 Preparing the SAP System Transport Host Field Input for <sapsid>adm Input for SAPService<SAPSID> Full name: <sapsid>adm SAPService<SAPSID> User logon name: <sapsid>adm SAPService<SAPSID> 3. Choose Next and enter the following: Password: <password> Confirm password: <password> 4. Select Password never expires Make sure that no other options are selected. 5. Choose Next Finish. Adding the <sapsid>adm User to the SAP_<SAPSID>_GlobalAdmin Group 1. In the Users folder, double-click the newly created user account <sapsid>adm in the list on the right. 2. Choose Member Add. 3. Select the new SAP_<SAPSID>_GlobalAdmin group and choose Add to add it to the list. By default, the user is also a member of the Domain Users group. 4. Choose OK twice. Adding the SAPService<SAPSID> User to the SAP_<SAPSID>_GlobalAdmin Group 1. In the Users folder, double-click the newly created user account SAPService<SAPSID> in the list on the 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 store transport data and metadata. 04/30/2008 PUBLIC 65/200

66 3 Preparation 3.7 Preparing the SAP System Transport Host When you install an SAP system, SAPinst by default creates the transport directory on the central instance host in \usr\sap\trans. Only valid for: HA (MSCS) In an MSCS configuration, SAPinst by default creates the transport directory on the (ABAP) central services instance host in \usr\sap\trans. End of: HA (MSCS) If you do not intend to use the directory structure of the system you are going to install, but want to use another new transport directory or an already existing transport directory, you need to prepare that transport host: If the directory structure already exists, you must set up its security to allow the new system to write to it. If it does not yet exist, you must create the core directory structure and a share to export it for other computers as well as set the security on it. 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 more information, see: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics Change and Transport System Procedure 1. If the transport directory does not yet exist, do the following: a) Create the directory \usr\sap\trans on the host to be used as the transport host. b) Share the usr\sap directory on the transport host as SAPMNT and put the security settings for Everyone to Full Control for this share. This enables SAPinst to address the transport directory in the standard way as \\SAPTRANSHOST\SAPMNT\trans. 2. Grant Everyone the permission Full Control for the transport directory. Caution Remove the Full Control to Everyone permission after you have finished the installation with SAPinst and only grant Full Control on this directory to the SAP_<SAPSID>_GlobalAdmin groups of all the systems that are part of your transport infrastructure. SAPinst assigns the appropriate rights with the help of an additional SAP_LocalAdmin group. For more information, see Automatic Creation of Accounts and Groups [page 146]. 66/200 PUBLIC 04/30/2008

67 3 Preparation 3.8 Installing the Front-End Software 3.8 Installing the 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 computer in your system environment. With the SAP Front-End installation software NW SAPSetup you can optimize the deployment of SAP GUI to thousands of clients. You can easily tailor installation packages to match your requirements, distribute patches, and set up automatic update processes for your clients. We recommend that you install SAP Front-End release For more information about installing the front-end software, see the documentation SAP Front End Installation Guide - Release 7.10 at: Installation Installation - Clients 3.9 Installing the Java Development Kit You need to prepare the system for the J2EE Engine by installing the Java Development Kit (JDK). As of SAP NetWeaver 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 and the SAPinst GUI. If required, you can perform a remote installation using a standalone SAPinst GUI on a separate Windows or UNIX host. This lets you perform the installation on a remote host, controlling it with the SAPinst GUI from a local host. If you want to perform a remote installation, see Performing a Remote Installation with SAPinst [page 97]. In this case, you need at least a JRE on the local host to start the SAPinst GUI there. Procedure 1. Check the JDK versions that are released for SAP systems in the Product Availability Matrix (PAM): a) Go to b) On the right-hand panel, choose SAP Technology Components SAP SOLUTION MANAGER <Current Release>. c) Choose tabstrip JSE Platforms. For more information about the recommended JDK version for your operating system and about how to download it, see SAP /30/2008 PUBLIC 67/200

68 3 Preparation 3.10 Preparing the Installation DVDs 2. Make sure a valid JDK version is installed on every host on which you want to install an SAP instance with the J2EE Engine, as follows: If the JDK is not already installed, you need to download and install it. If the JDK is already installed Check the installed version of the JDK by entering the following command: java -version 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 types that are deployed on it. You need to obtain the JCE policy files beforehand so that they can be installed by SAPinst: a) Download the JCE policy files for your platform at b) SAPinst installs the JCE policy files during the installation process Preparing the Installation DVDs This section describes how to prepare the installation DVDs, which are available as follows: You obtain the installation DVDs as part of the installation package. You can also download the installation DVDs from SAP Service Marketplace [page 70]. Procedure 1. Identify the required DVDs for your installation as listed below. Keep them separate from the remaining DVDs as this helps you to avoid mixing up DVDs during the installation. Caution The media names listed below are abbreviated. You can find the full names of all media shipped with SAP Solution Manager in the document Media List for SAP Solution Manager 7.0 at: SAP Components SAP Solution Manager <Current Release> 68/200 PUBLIC 04/30/2008

69 3 Preparation 3.10 Preparing the Installation DVDs SAP Instance Installation Central services instance, central instance, dialog instance Database instance Required DVDs SAP Solution Manager Installation Master DVD SAP Kernel 7.00 SR3 <OS> DVD SAP Solution Manager Java DVD RDBMS DVD (MS SQL Server Native Access Client (SNAC) software installation only) SAP Solution Manager Installation Master DVD SAP Kernel 7.00 SR3 <OS> DVD SAP Solution Manager Java DVD RDBMS DVD (SQL Server database software installation only) SAP Solution Manager Installation Export 1 DVD SAP Solution Manager Installation Export 2 DVD The following table shows the required DVDs for the installation of the Java Add-In for an existing ABAP System: SAP Instance Installation Central instance, central services instance, dialog instance Database schema Required DVD SAP Solution Manager Installation Master DVD SAP Kernel 7.00 SR3 <OS> DVD SAP Solution Manager Java DVD SAP Solution Manager Installation Master DVD SAP Kernel 7.00 SR3 <OS> DVD SAP Solution Manager Java DVD 2. Make the required installation media available on each installation host. Depending on your installation type, one or more instances can reside on the same host. You need to keep this in mind when you make the required installation media available on each installation host. For a central system, you need to make all required installation media available on the single installation host. Use one of the following methods to make DVDs available: Before the installation, copy DVDs manually to local hard disks. During the installation, use the SAPinst Media Browser dialog and copy the entire DVDs to the path you entered in the Copy Package To column. 04/30/2008 PUBLIC 69/200

70 3 Preparation 3.11 Downloading Installation DVDs from SAP Service Marketplace (Optional) Caution If you copy the DVDs to disk, make sure that the paths to the destination location of the copied DVDs do not contain any blanks. If you perform a domain installation and do not want to copy the DVDs but use network drives for mapping the installation DVDs, make sure that the <sapsid>adm user has access to the UNC paths of the network drives Downloading Installation DVDs from SAP Service Marketplace (Optional) You normally obtain the installation DVDs as part of the installation package from SAP. However, you can also download installation DVDs from SAP Service Marketplace at: Download Installations and Upgrades Entry by Application Group <SAP solution> <SAP product> <SAP release> Installation and Upgrade <operating system> <database>. If you download installation DVDs, note that DVDs might be split into several files. In this case, you have to reassemble the required files after the download. Prerequisites To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you can find on SAP Service Marketplace at You need at least SAPCAR 700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR files. For more information, see SAP 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: Material number All download objects that are part of an installation DVD have the same material number and an individual sequence number: <material_number>_<sequence_number> Example _ _ /200 PUBLIC 04/30/2008

71 3 Preparation 3.11 Downloading Installation DVDs from SAP Service Marketplace (Optional) Title All 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 _1, then _2, and so on. During the download SAPCAR sets up the structure of the installation DVD. SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always accept with Yes. 04/30/2008 PUBLIC 71/200

72 This page is intentionally left blank.

73 4 Installation 4 Installation This section provides information about how to perform a standard installation of your SAP system. Only valid for: HA (MSCS) If you want to perform a Microsoft Cluster Service (MSCS) installation, see High Availability with Microsoft Cluster Service [page 151]. End of: HA (MSCS) You have to perform the following steps: 1. You install the MS SQL Server database software [page 73]. 2. If required, you prepare your system for a Java Add-In installation [page 84]. 3. You install the SAP system using SAPinst [page 85]. 4.1 Installing the SQL Server Database Software The following sections describe how to install the SQL Server database software. The SQL Server software has to be installed on each host in the system where you intend to set up an SAP instance. Depending on the type of host involved, you either have to install the software for the database client or server. To install the SQL Server database software you have the following options: You install SQL Server automatically with SQL4SAP [page 73]. install the SQL Server database software manually [page 75] Installing the SQL Server Database Software with SQL4SAP With SQL4SAP.VBS you can automatically install the SQL Server 2005, SQL Server 2008, or SQL Server 2000 database software on various Windows operating systems. For more information about installing with SQL4SAP.VBS, see Customized Installation of SQL Server for an SAP System with SQL4SAP.VBS (SQL4SAP_docu.pdf) and the readme.txt, both of which are located in the root directory of the SQL Server RDBMS DVD. 04/30/2008 PUBLIC 73/200

74 4 Installation 4.1 Installing the SQL Server Database Software Caution Not all combinations of SQL Server and Windows are supported by all SAP products. When this guide was published, SQL Server 2008 was not yet released. For up-to-date information on the released database and operating system versions for your SAP product, see the Product Availability Matrix (PAM) at service.sap.com/pam. Only valid for: HA (MSCS) The SQL4SAP.VBS script does not support Microsoft Cluster Service (MSCS). If you want to run the script in an MSCS configuration, you get an error message. For more information about installing the SQL Server database software for MSCS, see Clustering the SQL Server Database Software [page 171]. End of: HA (MSCS) For SQL Server 2005, you use the SQL4SAP.VBS script to automatically install: SQL Server 2005 Enterprise Edition Latest SQL Server 2005 service pack Default Instances, Named Instances, or SQL Server Client Tools Only. For up-to-date information about installing SQL Server 2005 with SQL4SAP, read SAP For SQL Server 2008, you use the SQL4SAP.VBS script to automatically install: SQL Server 2008 Enterprise Edition Default Instances, Named Instances, or SQL Server Client Tools Only. For up-to-date information about installing SQL Server 2008 with SQL4SAP, read SAP For SQL Server 2000, you use the SQL4SAP.VBS script to automatically install the: SQL Server 2000 Enterprise Edition Latest SQL Server 2000 service pack Latest SQL Server hotfix, if required. SQL_Latin1_General_CP850_BIN or SQL_Latin1_General_CP850_BIN2 collation. Caution For technical and support reasons, we do not recommend using the MS SQL Server 2000 Enterprise Edition. Instead use MS SQL Server 2005 or higher. 74/200 PUBLIC 04/30/2008

75 4 Installation 4.1 Installing the SQL Server Database Software For up-to-date information about installing SQL Server 2000 with SQL4SAP.VBS, read SAP , which also includes the material number of the DVD containing the VB script. Procedure 1. Insert the SQL Server RDBMS DVD into your DVD drive or mount the network share locally. 2. Double-click SQL4SAP.VBS located in the root directory. 3. Follow the instructions and enter the required information in the installation screens Installing the SQL Server Database Software Manually The following sections describe how to install the SQL Server 2005 or SQL Server 2000 database software manually. When this guide was published, SQL Server 2008 was not yet released. As soon as we release SQL Server 2008, you can find the installation procedure (SQL4SAP_docu.pdf) on the SQL Server RDBMS DVD delivered by SAP Installing the SQL Server 2005 Database Server Software Manually This section describes how to install the SQL Server 2005 database server software manually. The SQL Server 2005 database server software must be installed on the database host. For a non-ha SAP system, you can also use the SQL4SAP script [page 73] to install SQL Server Only valid for: HA (MSCS) Caution If you use an MSCS environment, you must use the manual procedure. End of: HA (MSCS) If you want to install the database client software manually, see Installing the SQL Server 2005 Native Client (SNAC) Software [page 79]. 04/30/2008 PUBLIC 75/200

76 4 Installation 4.1 Installing the SQL Server Database Software Prerequisites When installing SQL Server 2005, make sure that you have enough free disk space available on the system drive for:.net Framework 2.0 For 64-bit also the 64-bit.Net Framework in addition to the 32-bit.Net Framework is installed. SQL Server Client Tools SQL Server instance Temporary space during the installation The required disk space depends on the type of SQL Server components already installed or to be installed. It also depends on the system. For a 64-bit system you might require more than 2 GB free disk space. Make sure that the Microsoft Distributed Transaction Coordinator (MSDTC) service is running before you start the installation. Procedure 1. Log on to the host as a local administrator 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. The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL server\90\setup Bootstrap\LOG. You find the summary of the setup log in summary.txt in the same directory. Window End User License Agreement Installing Prerequisites Welcome to the Microsoft SQL Server Installation Wizard Server Input Accept the licensing terms and conditions and choose Next. Choose Install and, if required, Next. Choose Next. 76/200 PUBLIC 04/30/2008

77 4 Installation 4.1 Installing the SQL Server Database Software Window System Configuration Check Server Input a) Check your system configuration and, if required, set up the required configuration. For more information about the required system configuration for a software component, choose Messages. IIS is not required for an SAP system. Therefore, you can ignore the warning about the IIS Feature Requirement. If there is a warning in COM Plus Catalog Requirement, correct the configuration before you proceed with the installation. Make sure that the Microsoft Distributed Transaction Coordinator (MSDTC) service is running. b) Choose Next. Registration Information (if available) Components to Install Feature Selection a) If this screen appears, enter your personal information. b) Choose Next. a) Select: SQL Server Database Services Workstation components, Books Online and development tools. b) Choose Advanced a) Expand Database Services and deselect Replication. b) Expand Client Components and if available, deselect Business Intelligence Development Studio. We recommend that you deselect these features as they are not required for an SAP system. c) Choose Next. Instance Name Select the instance you want to install and choose Next. We recommend that you install a Default instance. 04/30/2008 PUBLIC 77/200

78 4 Installation 4.1 Installing the SQL Server Database Software Window Service Account Server Input a) Select one of the following options: Use the built-in System account for each service and choose Local System or Network Service. Use a domain user account, and enter the user name and password. b) Under Start services at the end of setup make sure that SQL Server and SQL Server Agent are selected. If you use a named instance, you must also select SQL Browser. c) Choose Next. Authentication Mode a) Select Mixed Mode (Windows Authentication and SQL Server Authentication). This mode is required for a Java or ABAP+Java system. If you choose this mode, you have to set the password for the sa login. SAPinst automatically changes the authentication mode into Mixed Mode when installing a Java system. The password for the sa login must comply with the Windows password policy. b) Choose Next. Collation Settings Error and Usage Report Settings Ready to Install Setup Progress a) Select SQL collations (used for compatibility with previous versions of SQL Server). b) From the dropdown list select Binary order based on code point comparison, for use with the 850 (Multilingual) Character Set. c) Choose Next. Leave the selection unchanged and choose Next. Choose Install. 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. 78/200 PUBLIC 04/30/2008

79 4 Installation 4.1 Installing the SQL Server Database Software 6. When you have finished the installation, enable the Named Pipes and TCP/IP protocol in the SQL Server Configuration Manager as follows: Choose Start All Programs Microsoft SQL Server 2005 Configuration Tools SQL Server Configuration Manager. Expand SQL Server 2005 Network Configuration and select one of the following: For a default instance, select Protocols for MSSQLServer For a named instance, select Protocols for <SAPSID> In the right-hand pane, under Protocol Name, right-click Named Pipes and TCP/IP, and select Enable. 7. Restart SQL Server. 8. Install the latest SQL Server service pack and hotfix, if available. For more information, see SAP Installing the SQL Server 2005 Native Client Software Manually This section describes how to install the SQL Server 2005 Native Client (SNAC) software. The SQL Server 2005 client software must be installed on all SAP application servers. It enables the communication between an application server 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 With every SQL Server service pack a new sqlncli.msi file is available in the specified directory on the RDMBS DVD. You can also use this file to upgrade the SQL Native Client software. 4. Follow the instructions in the SQL Server installation setup screens Installing the SQL Server 2008 Database Server Software Manually When this guide was published, SQL Server 2008 was not yet released. As soon as SQL Server 2008 will be released, you find the installation procedure (SQL4SAP_docu.pdf) on the SQL Server RDBMS DVD that is delivered by SAP. 04/30/2008 PUBLIC 79/200

80 4 Installation 4.1 Installing the SQL Server Database Software The SQL Server 2005 database server software must be installed on the database host. Only valid for: HA (MSCS) Caution If you use an MSCS environment, you must use the manual procedure. End of: HA (MSCS) Installing the SQL Server 2008 Native Client Software Manually When this guide was published, SQL Server 2008 was not yet released. As soon as we release SQL Server 2008, you can find the installation file and procedure (SQL4SAP_docu.pdf) on the SQL Server RDBMS DVD that is delivered by SAP. The SQL Server 2008 client software must be installed on all SAP application servers. It enables the communication between an application server 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 2008 RDBMS DVD in your DVD drive or mount it locally. 3. Change to the platform-specific folder and choose sqlncli.msi With every SQL Server service pack a new sqlncli.msi file is available in the specified directory on the RDMBS DVD. You can also use this file to upgrade the SQL Native Client software. 4. Follow the instructions in the SQL Server installation setup screens Installing the SQL Server 2000 Database Software on 64-Bit Manually On a 64-bit system, you cannot run the SQL Server 2000 graphical user interface (GUI) tools, with the following exceptions: Client Network Utility (supported by the 64-bit Windows operating system) Server Network Utility Service Manager 80/200 PUBLIC 04/30/2008

81 4 Installation 4.1 Installing the SQL Server Database Software SQL Server 2000 Licensing (in Control Panel) Setup.exe (supported by Windows Installer) If you want to use the other SQL Server 2000 GUI tools with the 64-bit version of SQL Server 2000, you have to install them with the 32-bit version of SQL Server 2000 on a 32-bit computer. You can then use the GUI tools to remotely manage the 64-bit server. You can install the 32-bit graphical user interface management tools from the 32-bit directory of the MS SQL Server 2000 RDBMS SP4 DVD. Graphical interface management tools which were installed with the 32-bit version of SQL Server 2000 are not supported in the 64-bit version. For more information refer to the readme.txt file in the IA64\SQL2000 subdirectory. Procedure 1. Log on to the host as a local administrator. Caution Make sure that you have not applied NTFS compression to the disk where you install the MS SQL 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\SQL Enter the required information as specified in the following table: Input for the MS SQL Server Installation on 64-Bit Systems Window Registration Information Software License Agreement Feature Selection Input Enter your name and the product key specified in the file SAPCDKEY.txt in the root directory of the RDBMS DVD. Choose Yes. Server Software: Select all components. Client Software: Select SQL Server Management Tools. To select a component, left-click it and choose Entire feature will be installed on local hard drive. To deselect a component, left-click on it, and choose Entire feature will be unavailable. 04/30/2008 PUBLIC 81/200

82 4 Installation 4.1 Installing the SQL Server Database Software Window Instance Name Service Account Authentication Mode Input Select the instance type you want to install. Select Use the same account for each service. Auto start SQL Server Service. Select Use the Local System account. Select the authentication mode. We recommend to use Windows authentication mode. For a Java system, Mixed mode is required. SAPinst automatically changes the authentication mode into Mixed mode when installing a Java system. Enter and confirm the password for the sa login. If you have chosen Windows authentication mode, the sa login is created, but cannot be used. Security Enhancement: Cross Database Ownership Chaining Collation Settings Licensing Mode Ready to Install Leave selection unchanged and choose Next. Select SQL Collations. From the dropdown list select Binary order, for use with the 850 (Multilingual) Character Set. Select the licensing mode and choose Next. Select Install. 5. When you have finished the installation, install the latest Service Pack, and the latest hotfix, if available, for SQL Server For more information about the latest Service Pack, see SAP For more information about the latest hotfix, see SAP If you have installed the server software, install the corrected MS SQL Server collation [page 82]. For more information about the SQL Server collation, see SAP Installing the Corrected MS SQL Server Collation for MS SQL Server 2000 When you install the MS SQL Server 2000 database for an SAP system, in the field Collation Settings you have to select Binary order, for use with the 850 (Multilingual) Character Set. This means that all new databases and table columns are created with this collation setting. 82/200 PUBLIC 04/30/2008

83 4 Installation 4.1 Installing the SQL Server Database Software To view the default collation of MS SQL Server, use the query: select serverproperty( collation ) This query returns the default collation of the overall server. When you have selected Binary order, for use with the 850 (Multilingual) Character Set, it returns: SQL_Latin1_General_CP850_BIN Unfortunately this collation setting does not sort Unicode data as it is required by an SAP system. To solve this problem, Microsoft provides a corrected collation for SQL Server. For more information about installing the collation, see SAP Prerequisites You have installed the MS SQL Server 2000 database software. In the field Collation Settings, you selected Binary order for use with the 850 (Multilingual) Character Set. You have installed the latest service pack and hotfix, if available. For more information, see SAP s and Besides applying the latest service and hotfix, if available, you do not have to make any changes on the client side (SAP application servers). To obtain a correct collation order with MS SQL Server, you have to use the new collation for all new installations of a Unicode or non-unicode SAP system with the MS SQL Server database. New versions of the SAPinst installation tool check for the new collation. A new SAP system using the new collation and an existing SAP system that is using the old collation cannot run as two databases in the same MS SQL Server instance. If you want to install a new system on a database server with an existing system you have to apply the new collation with INSTCOLL.EXE. 1. Download the INSTCOLL.EXE file for your platform, which is attached as zip file to SAP , 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: For a default instance enter: INSTCOLL.EXE For a named instance enter: INSTCOLL.EXE -S<server>\<instance> (without any spaces after --S) The executable starts the SQL Server Service if it is not running already and runs several checks. When you are asked to apply the new collation to all databases confirm with Y (Yes). When the conversion has finished, it restarts the SQL Server Service. 4. To check whether the MS SQL Server is properly configured, run: select serverproperty( collation ) 04/30/2008 PUBLIC 83/200

84 4 Installation 4.2 Preparing your System for a Java Add-In Installation Caution You have to run INSTCOLL.EXE only once to apply the new collation. To convert a single SAP database to the new collation, see SAP Result You can now continue with the standard SAP system installation and install any SAP instance on this server. 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 an existing SAP Solution Manager system (Release 3.2 or Release 3.1) that has been upgraded to SAP Solution Manager 4.0 SR2. Procedure 1. In your default profile \usr\sap\<sapsid>\sys\profile\default.pfl, check the parameter dbs/mss/schema. If it is set to <sapsid> (lowercase letters), no further action is required. If it does not exist or is set to dbo, convert the schema as described in SAP 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_General_CP850_BIN2: a) Start the SQL Server Enterprise Manager. b) Right-click on your SQL Server and choose Properties. In the General tab under Server collation you see the collation installed. If you use SQL_Latin1_General_CP850_BIN2 no further action is required. If you use collation SQL_Latin1_General_CP850_BIN, convert it to SQL_Latin1_General_CP850_BIN2 as described in Installing the Corrected MS SQL Server Collation for SQL Server 2000 [page 82]. 84/200 PUBLIC 04/30/2008

85 4 Installation 4.3 Installing an SAP System Using SAPinst 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 standalone engine: Running SAPinst on Windows [page 85] Using SAPinst GUI [page 95] Interrupted Installation with SAPinst [page 96] Performing a Remote Installation with SAPinst (Optional) [page 97] Starting SAPinst GUI Separately (Optional) [page 98]. Entries in the Services File Created by SAPinst [page 100] How to Avoid Automatic Logoff by SAPinst [page 100] Running SAPinst on Windows This procedure tells you how to install an SAP system with SAPinst. SAPinst includes an SAPinst GUI and a GUI server, which both use Java. This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running on the same host. If required, you can instead perform a remote installation with SAPinst [page 97], where SAPinst GUI is running on a separate host from SAPinst and the GUI server. the following information about SAPinst: When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects to the GUI server with a secure SSL connection, and the GUI server connects to SAPinst. SAPinst 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 create sapinst_instdir there, it tries to create sapinst_instdir in the directory defined by the environment variable TEMP. Recommendation We recommend that you keep all installation directories until the system is completely and correctly installed. SAPinst creates a subdirectory for each installation option called <sapinst_instdir>\<installation_option>, which is located in %ProgramFiles%\sapinst_instdir. The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP, TMPDIR, or SystemRoot). 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, which might be useful if an error occurs. 04/30/2008 PUBLIC 85/200

86 4 Installation 4.3 Installing an SAP System Using SAPinst Caution If SAPinst cannot find a temporary directory, the installation terminates with the error FCO If you want to terminate SAPinst and the SAPinst Self-Extractor, choose one of the following options: Right-click the icon for the SAPinst output window located in the Windows tray and choose Exit. Click the icon for the SAPinst output window located in the Windows tray and choose File Exit. Prerequisites You use an account with the required user authorization to install the SAP system with the SAPinst tool [page 61]. You need at least 200 MB of free space in the installation directory for each installation option. In addition, you need MB free space for the SAPinst executables. If you are installing a second or subsequent SAP system into an existing database, make sure that the database is up and running before starting the installation. For more information, see Installation of Multiple Components in One Database [page 127]. Dialog instance only: If your SAP System has been upgraded from an earlier release, and you want 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: If it is set in the instance profile, it must also be set in the start profile. 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> Edit the instance profile of the central services instance: Set rdisp/msserv to 0. Set rdisp/msserv_internal to the port number assigned to rdisp/msserv. 86/200 PUBLIC 04/30/2008

87 4 Installation 4.3 Installing an SAP System Using SAPinst Example Instance profile of the central services instance: Before:... rdisp/msserv = After:... rdisp/msserv = 0 rdisp/msserv_internal = Restart all SAP services and instances of your SAP system. 5. If you want to use a virtual host name, you have to set the environment variable SAPINST_USE_HOSTNAME to specify the required virtual host name before you start SAPinst. If you do not set this environment variable now, you can specify an equivalent parameter for the virtual host name when you start SAPinst. Procedure 1. Insert the SAP Installation Master DVD into your DVD drive or mount it locally. 2. Start SAPinst from the SAP Installation Master DVD by double-clicking sapinst.exe from the following path: <DVD drive>:\im_windows_<platform> SAPinst GUI starts automatically by displaying the Welcome screen. However, if there is only one component to install, SAPinst directly displays the first input dialog without presenting the Welcome screen. During the installation, the default ports and are used for communication between SAPinst, GUI server, and SAPinst GUI. SAPinst uses port to communicate with the GUI server. The GUI server uses port to communicate with SAPinst GUI. You get an error message 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_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> To get a list of all available SAPinst properties, go to the directory (%TEMP%\sapinst_exe.xxxxxx.xxxx), after you have started SAPinst, and enter 04/30/2008 PUBLIC 87/200

88 4 Installation 4.3 Installing an SAP System Using SAPinst the following command: sapinst.exe -p If you want to use a virtual host name and you have not set the environment variable SAPINST_USE_HOSTNAME, start SAPinst as follows:./sapinst SAPINST_USE_HOSTNAME=<virtual host name> 3. In the Welcome screen, choose one of the following installation options: SAP Systems Software Life-Cycle Options The following tables provide more information about these installation options: SAP Systems You use this option to install an SAP system with usage types or software units by choosing SAP Solution Manager <Current Release> SAP Systems <Database> <System Variant> Based on AS ABAP and AS Java. You can install the following system variants: Central System Distributed System Only valid for: HA (MSCS) High-Availability System End of: HA (MSCS) The following tables provide an overview of the installation options available for these system variants: Choose the corresponding installation options from the tree structure exactly in the order they appear for each system variant. If required, to install a dialog instance for a central or distributed system, choose: SAP Solution Manager <Current Release> Software Life-Cycle Options Application Server Dialog Instance See table Software Life-Cycle Options below. Installation Services for a Central System Installation Service Central System Remarks Installs a complete SAP system including the following instances on one host: Central services instance (SCS) Database instance Central instance You can install a central system in the following parameter modes: Typical Mode 88/200 PUBLIC 04/30/2008

89 4 Installation 4.3 Installing an SAP System Using SAPinst Installation Service Remarks If you choose Typical, the installation automatically uses default settings. You only have to respond to a small selection of prompts. However, you can change any of the default settings on the parameter summary screen. Custom Mode If you choose Custom, the installation prompts you for all parameters. At the end, you can change any parameter on the parameter summary screen. Installation Services for a Distributed System Installation Services Central Services Instance (SCS) Database Instance Central Instance Remarks Mandatory step in installing a distributed SAP system with usage types or software units based on AS ABAP and AS Java. Installs a central services instance (SCS) and prepares the SAP global host. 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. Mandatory step in installing a distributed SAP system on several hosts. Installs a central instance and enables additional usage types or software units. You must have finished the database instance installation. Installation Services for a High Availability System Installation Services Central Services Instance for ABAP (ASCS) Central Services Instance (SCS) First MSCS Node Database Instance Additional MSCS Node Remarks Installs a central services instance for ABAP (ASCS) and prepares the SAP global host Installs a central services instance (SCS) Performs the following steps on the first Microsoft Cluster Service (MSCS) node: Creates the SAP cluster group Adds the ASCS and SCS instances to the SAP cluster group Installs a database instance Configures an additional Microsoft Cluster Service (MSCS) node to run the SAP cluster group You must have completed the configuration of the first MSCS node and the database instance installation. 04/30/2008 PUBLIC 89/200

90 4 Installation 4.3 Installing an SAP System Using SAPinst Installation Services Enqueue Replication Server Central Instance Dialog Instance Remarks Installs an enqueue replication server, which contains a replica of the lock table (replication server) Installs a central instance and enables additional usage types or software units Installs a dialog instance You require at least one dialog instance in a high-availability system configured with MSCS. If you want to use 32-bit SAP NetWeaver components, first check whether these components can run on 64-bit operating systems. If so, we recommend you to use 64-bit systems. If not, you can install an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP instances, you must use 64-bit systems. We do not support operating an ABAP dialog instance with an ABAP+Java system. You cannot install the Java Add-In for existing ABAP dialog instance(s). Instead, you have to install new ABAP+Java dialog instance(s). If you want to use LDAP, you must choose the options under LDAP Registration (see below) after you have installed an application server. Software Life-Cycle Options You use this option to perform the following tasks or to install the following components: Installation Service Additional Preparation Options Remarks These preparation tasks comprise: Operating System Users and Groups Creates all operating system users for your SAP system if they do not yet exist. Caution Perform this SAPinst option before you start the installation of your SAP system. Make sure that you have the required user authorization [page 61] for these accounts before you start the installation. Prerequisites Check Checks your hardware and software requirements before you start the installation. Otherwise, SAPinst automatically checks the hardware and software requirements during the installation with the Prerequisite Checker. If any changes are necessary to the SAP system or operating system settings, SAPinst automatically prompts you. For more information, see Running the Prerequisites Checker in Standalone Mode [page 47]. 90/200 PUBLIC 04/30/2008

91 4 Installation 4.3 Installing an SAP System Using SAPinst Installation Service Remarks Application Server Choose Application Server <Database> Dialog Instance to install one or more dialog instance(s) in an already installed SAP system, if required. If you want to use 32-bit SAP NetWeaver components, first check whether these components can run on 64-bit operating systems. If so, we recommend you to use 64-bit systems. If not, you can install an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP instances, you must use 64-bit systems. We do not support operating an ABAP dialog instance with an ABAP+Java system. You cannot install the Java Add-In for existing ABAP dialog instance(s). Instead, you have to install new ABAP+Java dialog instance(s). If you want to use LDAP, you must choose the options under LDAP Registration (see below) after you have installed an application server. Java Add-In for ABAP LDAP Registration Choose this service to install usage types based on AS Java to an already installed SAP ABAP system. For more information, see Installing a Java Add-In for an Existing ABAP System with SAPinst [page 92]. Active Directory Configuration Configures the Active Directory so that it can store SAP data. We recommend you to choose this option before you install the SAP system or an application server. You have to configure the active directory server only once. Afterwards all SAP systems that should register in this directory server can use this setup. LDAP Support Sets up LDAP support for an application server instance. Choose this option once per SAP system and after you have: a) Performed the option Active Directory Configuration b) Installed an application server instance. For more information about LDAP and Active Directory, see Integration of LDAP Directory Services [page 129]. System Copy Choose this service to perform a system copy. For more information, see the system copy guide, which is available at: Installation Installation SAP NetWeaver Systems 04/30/2008 PUBLIC 91/200

92 4 Installation 4.3 Installing an SAP System Using SAPinst Installation Service Java Add-In for ABAP Uninstall Remarks Choose this service to install usage types based on AS Java to an existing ABAP system. For more information, see Installing a Java Add-In for an Existing ABAP System with SAPinst [page 92] Choose this service to uninstall your SAP Solution Manager system. For more information, see Deleting an SAP System [page 148]. 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. For more information about the input parameters, position the cursor in the field of the respective parameter and press F1. After you have entered all required input information, SAPinst starts the installation and displays the progress of the installation. If the installation was successful, the screen Finished installation successfully is displayed. 6. We recommend you to delete all files in the directory %userprofile%\.sdtgui\. More Information Troubleshooting with SAPinst [page 148] Installing the Java Add-In for an Existing ABAP System (Optional) This section describes how to install a Java Add-In for an existing SAP Solution Manager ABAP system. Caution Keep in mind that you cannot install the Java Add-In for existing ABAP dialog instance(s). Instead, you have to uninstall the old ABAP dialog instance(s) and install new ABAP+Java dialog instance(s) as follows: On the Welcome screen in SAPinst, choose <SAP system> Software Life-Cycle Options Application Server <database> Dialog Instance. Prerequisites Your upgraded ABAP system must be on the most recent support package level (at least SPS 15). 92/200 PUBLIC 04/30/2008

93 4 Installation 4.3 Installing an SAP System Using SAPinst Only valid for: HA (MSCS) If you use Microsoft Cluster Service (MSCS), stop the ASCS instance in the Cluster Administrator (Windows Server 2003) or Failover Cluster Management (Windows Server 2008).(service SAP <SID> <instance_number> Service) before you run the installation service First MSCS Node in SAPinst. End of: HA (MSCS) Procedure 1. Start SAPinst [page 85]. 2. On the Welcome screen, choose SAP Solution Manager <Current Release> Software Life-Cycle Options 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 Installation Services Central Services Instance (SCS) Java Add-In Database Instance Java Add-In Central Instance Java Add-In Remarks Installs a central services instance (SCS) and adds usage types or software units based on AS Java Installs the Java schema in the database of your ABAP system Adds usage types or software units based on AS Java Caution When performing an upgrade installation, before you use this option, uninstall the old ABAP dialog instance(s). Installation Services for a Java Add-In for ABAP High-Availability System Installation Services Central Services Instance (SCS) Java Add-In Remarks Installs a central services instance (SCS) and adds usage types or software units based on AS Java Caution You must install it on the same shared disk as the ASCS instance. First MSCS Node Configures the SCS instance for the first MSCS node Make sure that you choose instance type ASCS and SCS instance (ABAP and Java). 04/30/2008 PUBLIC 93/200

94 4 Installation 4.3 Installing an SAP System Using SAPinst Installation Services Database Instance Java Add-In Remarks Installs the Java schema in the database of your ABAP system If your database instance is to be installed in the same MSCS cluster as the SCS and ASCS instance, you must perform this step on the first node of this MSCS cluster. If your database instance is to be installed in a different MSCS cluster from the ASCS and SCS instance, you perform this step on another MSCS cluster. Additional MSCS Node Caution Choose this step only if you use Microsoft Cluster Services (MSCS). This step configures the SCS instance for the additional MSCS node. Make sure that you choose instance type ASCS and SCS instance (ABAP and Java). Enqueue Replication Server Central Instance Java Add-In Dialog Instance Installs an enqueue replication server, which contains a replica of the lock table (replication table). You must perform this step on all MSCS nodes where the Java central services (SCS) instance or ABAP central services (ASCS) instance is installed and clustered. Adds usage types or software units based on AS Java Installs an ABAP+Java dialog instance If you want to use 32-bit SAP NetWeaver components, first check whether these components can run on 64-bit operating systems. If so, we recommend you to use 64-bit systems. If not, you can install an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP instances, you must use 64-bit systems. We do not support operating an ABAP dialog instance with an ABAP+Java system. You cannot install the Java Add-In for existing ABAP dialog instance(s). Instead, you have to install new ABAP+Java dialog instance(s). When performing an upgrade installation, before you use this option, uninstall the old ABAP dialog instance(s). 94/200 PUBLIC 04/30/2008

95 4 Installation 4.3 Installing an SAP System Using SAPinst 4. Follow the instructions in the SAPinst input dialogs and enter the required parameters. SAPinst prompts you for the production client of your ABAP system, which is where you install the Java Add-In. After you have entered all required input parameters, SAPinst starts the installation and displays the progress of the installation. Result After running these installation services, your ABAP+Java system consists of the following instances: Java central services instance (SCS) ABAP+Java database instance ABAP+Java central instance Using SAPinst GUI The following table shows the most important functions that are available in SAPinst GUI: SAPinst GUI Functions Input Type Label Description Function key F1 Displays detailed information about each input parameter. Menu option File Log off Stops the SAPinst GUI, but SAPinst and the GUI server continue running. If for some reason you need to log off during the installation from the host where you control the installation with SAPinst GUI, the installation continues while you are logged off. You can later reconnect to the same SAPinst installation from the same or another host. For more information, see Starting SAPinst GUI Separately [page 98]. Menu option File View Log Displays the installation log (sapinst_dev.log) Menu option File Exit Cancels the installation with the following options: Stop For more information, see the description of the message button below. Continue For more information, see the description of the message button below. 04/30/2008 PUBLIC 95/200

96 4 Installation 4.3 Installing an SAP System Using SAPinst Input Type Label Description Message button Retry Performs the installation step again (if an error has occurred). Message button View Log Displays the installation log (sapinst_dev.log) Message button Stop Stops the installation (SAPinst GUI, SAPinst and the GUI server) without further changing the installation files. You can continue the installation later from this point. Message button Continue Continues with the option you have chosen before Interrupted Installation with SAPinst The SAP system installation might be interrupted for one of the following reasons: An error occurred during the dialog or processing phase: SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description about the choices listed in the table below as well as a path to a log file that contains detailed information about the error. You interrupted the installation by choosing Exit in the SAPinst menu. The following table describes the options in the dialog box: Option Retry Stop Continue Definition SAPinst retries the installation from the point of failure without repeating any of the previous steps. This is possible because SAPinst records the installation progress in the keydb.xml file. We recommend that you view the entries in the log files, try to solve the problem and then choose Retry. If the same or a different error occurs again, SAPinst displays the same dialog box again. SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server. SAPinst records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below. SAPinst continues the installation from the current point. Procedure This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to continue an interrupted installation after an error situation. 1. Log on as a user who is a member of the local administrators group. 2. Insert the Installation Master DVD in your DVD drive. 96/200 PUBLIC 04/30/2008

97 4 Installation 4.3 Installing an SAP System Using SAPinst 3. Change to the required directory <DVD drive>:\im_windows_<platform> Double-click sapinst.exe 4. From the tree structure in the Welcome screen, select the installation service that you want to continue and choose Next. If there is only one component to install, the Welcome screen does not appear. The What do you want to do? screen appears. 5. In the What do you want to do? screen, decide between the following alternatives and confirm with OK. Alternative Run a new Installation Continue old installation Behavior SAPinst does not continue the interrupted installation. Instead, it moves the content of the old installation directory and all installation-specific files to the backup directory. Afterwards, you can no longer continue the old installation. For the backup directory, the following naming convention is used: <log_day_month_year_hours_minutes_seconds> (for example, log_01_oct_2003_13_47_56). SAPinst continues the interrupted installation from the point of failure Performing a Remote Installation with SAPinst (Optional) You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the GUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from which you control the installation with SAPinst GUI. Prerequisites The remote host meets the prerequisites before starting SAPinst as described in Running SAPinst on Windows [page 85]. Both computers are in the same network and can ping each other. To test this: Log on to your remote host and enter the command ping <local host>. 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. 04/30/2008 PUBLIC 97/200

98 4 Installation 4.3 Installing an SAP System Using SAPinst 3. Open a command prompt and change to the required directory of the installation Master DVD. Enter the following commands: <DVD drive:\>cd <DVD drive>:\im_windows_<platform> sapinst.exe -nogui For more information, see Running SAPinst on Windows [page 85]. SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the 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 98] Starting SAPinst GUI Separately (Optional) You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI separately in the following cases: You have logged off from SAPinst. If you logged off during the installation and you later want to reconnect to the installation while it is still running, you can start SAPinst GUI separately. You want to perform a remote installation [page 97]. If you want to run SAPinst GUI on a different host from SAPinst and the GUI server, you have to start SAPinst GUI separately. Prerequisites You have installed the Java Development Kit [page 67] on the host on which you want to start SAPinst without 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. Open a command prompt and change to the relevant directory: <DVD drive>:\im_windows_<platform> 4. Start SAPinst GUI in one of the following ways: 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. 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> 98/200 PUBLIC 04/30/2008

99 4 Installation 4.3 Installing an SAP System Using SAPinst <host_name> is the host name of the installation host. If you enter the command without additional parameters, SAPinst GUI uses the local host as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. Since SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and the 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 installation from your local host. For a list of options to start SAPinst GUI, change to the same directory as your SAPinst executable 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 or database. 2. Mount your installation DVD. 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: 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. 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. 04/30/2008 PUBLIC 99/200

100 4 Installation 4.3 Installing an SAP System Using SAPinst If you enter the command without additional parameters, SAPinst GUI uses the local host as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. Since SAPinst and GUI server are running on another host, SAPinst GUI cannot connect and the SAP 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 installation from your local host. For a list of options to start SAPinst GUI, change to the same directory as your SAPinst executable and enter the command./startinstgui.sh -h Entries in the Services File Created by SAPinst After the installation has finished successfully, SAPinst has created the following entries for port names in <drive:>\windows\system32\drivers\etc\services: sapdpxx = 32XX/tcp sapdbxxs = 47XX/tcp sapgwxx = 33XX/tcp sapgwxxs = 48XX/tcp where XX is set from 00 to 99. If there is more than one entry for the same port number, this is not an error How to Avoid Automatic Logoff by SAPinst When you install the SAP system with SAPinst, the SAPinst installation tool checks whether the user account used for the installation has the required privileges and authorization. For a domain installation, the account needs to be both a member of the local Administrators and the domain Admins group. For a local installation, the account needs to be a member of the local Administrators group. In both cases, the user account must be authorized to: Act as part of the operating system Adjust memory quotas for a process Replace a process level token 100/200 PUBLIC 04/30/2008

101 4 Installation 4.3 Installing an SAP System Using SAPinst If the user account does not have these rights assigned, SAPinst assigns them and automatically logs the account off to activate them. To avoid SAPinst logging the account off, you can set these rights manually before you start the installation. Procedure You perform the following steps to assign these rights to the user account used for the installation. Caution Be aware that domain policies override locally defined policies. This means that if you want to grant domain administrator rights for a user who belongs to the local Administrators group, make sure that you have also defined domain administrator rights for this user on domain level. 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 required 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 Information Required User Authorization for the Installation [page 61] 04/30/2008 PUBLIC 101/200

102 This page is intentionally left blank.

103 5 Post-Installation 5 Post-Installation In a central system, all mandatory instances are installed on one host. Therefore, if you are installing a central system, you can ignore references to other hosts. You perform the following post-installation steps: 1. You configure the Windows Server 2008 Firewall [page 104]. 2. You check whether you can log on to the application server [page 107]. In a distributed or high-availability system you check whether your can log on to every instance of the SAP system that you installed. 3. You check whether you can log on to SAP Solution Manager Diagnostics [page 108]. In a distributed or high-availability system you check whether your can log on to every instance of the SAP system that you installed. 4. You install the SAP license [page 109]. Caution This step does not apply to the installation of a Java Add-In for an existing ABAP system. 5. Windows Server 2008 only: If required, you set up symbolic links for application servers [page 109]. 6. You install the SAP Online Documentation [page 110]. Caution This step does not apply to the installation of a Java Add-In for an existing ABAP system. 7. You configure the remote connection to SAP support [page 111]. Caution This step does not apply to the installation of a Java Add-In for an existing ABAP system. 8. On the central instance host, you apply the latest kernel and Support Packages [page 111]. 04/30/2008 PUBLIC 103/200

104 5 Post-Installation 5.1 Configuring the Windows Server 2008 Firewall 9. You perform initial ABAP configuration [page 113]. Caution This step does not apply to the installation of a Java Add-In for an existing ABAP system. 10. You perform a full installation backup [page 115]. 11. You perform post-installation steps for Adobe Document Services [page 115]. 12. You ensure user security [page 118]. 13. You check the Java documentation [page 121] for information that is relevant for running your Java system. 14. You configure SAP Solution Manager [page 123]. 15. If you want or need to implement the E2E Root Cause Analysis scenario, you have to perform post-installation steps for the Diagnostics Agent [page 123] on your central instance and/or dialog instance(s). 16. If required, you can install the SAP Solution Manager Enterprise Edition Add-On [page 124]. 5.1 Configuring the Windows Server 2008 Firewall As of Windows Server 2008, the Windows Firewall is turned on by default. It is configured to allow only a small set of Windows-specific inbound IP connections. Outbound connections by default are not limited to rules and are therefore not restricted by the firewall. The default firewall settings are valid for the out-of-the-box installation of Windows Server 2008 and apply to local policies. For domain policies that override local policies, other rules might apply. To disable the Windows firewall temporarily, proceed as follows: 1. Choose Start Administrative Tools Windows Firewall with Advanced Security. 2. Right-click Windows Firewall with Advanced Security and choose Properties. 3. To turn off the firewall, choose the relevant profile (in most cases Domain Profile) and set the Firewall state to Off. 4. To turn on the firewall again, set the Firewall state to On. For the SAP system to operate, you might have to configure the Windows firewall and define a set of Inbound Rules for the TCP/IP port numbers that are used by your system. For more information about the port numbers used, see the documentation TCP/IP Ports Used by SAP Applications at: Security in Detail Infrastructure Security Ports listed with the default value Not active in this document are not configured. 104/200 PUBLIC 04/30/2008

105 5 Post-Installation 5.1 Configuring the Windows Server 2008 Firewall SQL Server Ports and Client Connections This section provides general information about the client connections and used ports with SQL Server. This information helps you to correctly configure the Windows Server 2008 Firewall for the SQL Server ports, as described below. With SQL Server you have the following instance types: Default instance The default instance uses per default TCP port 1433 to connect to the database server. Named instance(s) Named instances use a random port. This port is fixed while the SQL Server service is running, but might change when the SQL Server service starts. If you use a firewall, we strongly recommend to use fixed port numbers for Named Instances. You can set up fixed port numbers for named instances in the SQL Server Configuration Manager. For more information, see the SQL Server Books Online. If an SQL Server client connects to the database server, it uses: The same SQL Server instance port on the server side A separate but random port on the client side To find out the server port number from the client side, you have the following options: You use SQL Server Browser, which uses UDP port This port tells the client which SQL Server port is used. If you do not use SQL Browser, look for the port number in the SQL Server Error Log. Add the port number in the connection string of the instance profile as shown in the following example: Example This example shows how the connection string, looks before and after the change for a default and named instance: Connection string before change: Default instance: <hostname> Example: SAPSQLSERVER Named instance: <hostname>\<instancename> Example: SAPSQLSERVER\PRD Connection string after change with added port number: Default instance: tcp:<hostname>,<port> Example: tcp:sapsqlserver,1433 Named instance: tcp:<hostname>\<instancename>,<port> Example: tcp:sapsqlserver\prd, /30/2008 PUBLIC 105/200

106 5 Post-Installation 5.1 Configuring the Windows Server 2008 Firewall We recommend you to use the following best practices with SQL Server for the Windows Server 2008 Firewall settings: Use a default instance. Define the inbound rules for TCP port If you use a named instance, we recommend you to set up a fixed port number in the SQL Server Configuration Manager and to use SQL Server Browser. Define the inbound rules for this fixed TCP number, as well as for UDP port 1434, which is used by SQL Server Browser. Procedure This procedure describes how to set Inbound Rules for the ports of an installed ABAP server that was installed with instance number Choose Start Administrative Tools Windows Firewall with Advanced Security. 2. Right-click Inbound Rules and choose New Rule. The New Inbound Rule Wizard starts. 3. For Rule Type, select Port and choose Next. 4. For Protocol and Ports, select port type TCP or UDP depending on the port type used. Select Specific local ports, and enter the port numbers for which you want to apply the new rule, for example: 3200,3300,4800,8000,3600,50013,1433,1434 Choose Next. 5. For Action, select Allow the connection, and choose Next. 6. For Profile, keep Domain, Private and Public selected, and choose Next. For more information, see the link Learn more about profiles on this screen. 7. Enter the Name, for example SAP ABAP Server 00, and Description for the new rule. 8. Choose Next. 9. Choose Finish to save the rule. The new inbound rule appears in the Inbound Rules list. To modify the settings, right-click on the rule and choose Properties. Port 1433 is only required if programs running on other hosts must access SQL Server using TCP/IP, such as when you have installed additional SAP dialog instances or you run SQL Server Management Studio on a remote computer. 106/200 PUBLIC 04/30/2008

107 5 Post-Installation 5.2 Logging On to the Application Server If you want to use, for example, a different IP scope for port 50013, which is used by the connection SAP Start Service SAP Management Console, you can restrict the IP access to a small number of SAP Administrators. Then delete this port from the SAP ABAP Server 00 rule and create a new rule for port with a more restrictive scope. 5.2 Logging On to the Application Server 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 system user SAP* 000, 001, 066 DDIC 000, 001 Java User User Administrator User Name Storage: ABAP System J2EE_ADMIN (default) or the name you gave this user during the installation process. Prerequisites The SAP system is up and running. You have already installed a front end. Logging On to the ABAP Application Server 1. Start SAP Logon on the host where you have installed the front end as follows: SAP GUI for Windows: Choose Start All Programs SAP Front End SAP Logon. SAP GUI for Java: Choose Start All Programs SAP Clients SAP GUI for Java<Release>. You can also enter the command guilogon in the SAP GUI installation directory to start SAP GUI for Java. The SAP Logon appears. 2. Create a logon entry for the newly installed system in the SAP Logon. 04/30/2008 PUBLIC 107/200

108 5 Post-Installation 5.3 Logging On to SAP Solution Manager Diagnostics For more information about creating new logon entries, press F1. 3. When you have created the entry, log on as user SAP* or DDIC. Logging On to the Java Application Server You access AS Java with a URL using a Web browser from your client machines. To log on to the Java application server, proceed as follows: 1. Start a Web browser and enter the following URL: You must always enter a two-digit number for <Instance_Number>. For example, do not enter 1 but instead enter 01. Example If you installed the SAP NetWeaver Application Server Java on host saphost06 and the instance number of your SAP NetWeaver Application Server Java is 04, enter the following URL: The start page of the SAP NetWeaver Application Server Java appears in the Web browser. 2. Log on by pressing the link of any of the provided applications, for example the SAP NetWeaver Administrator or the System Information. To deactivate AS Java, proceed as follows: 1. Call transaction RZ In the instance profile of every installed SAP instance, set parameter rdisp/j2ee_start from 1 to Logging On to SAP Solution Manager Diagnostics You access SAP Solution Manager Diagnostics with a URL using a Web browser from your client machines. Proceed as follows to log on: Procedure 1. Start a Web browser and enter the following URL: 108/200 PUBLIC 04/30/2008

109 5 Post-Installation 5.4 Installing the SAP License You must always enter a two-digit number for <Instance_Number>. For example, do not enter 1 but instead enter 01. Example If you installed SAP Solution Manager on host saphost06 and the central instance number of your SAP NetWeaver Application Server Java is 01, enter the following URL: 2. Log on with the administrator user J2EE_ADM and the master password [page 37] that you entered during the installation process. 5.4 Installing the SAP License Caution This section does not apply to the installation of a Java Add-In to an existing ABAP system. You must install a permanent SAP license. When you install your SAP system, a temporary license is automatically installed. This temporary license allows you to use the system for only four weeks from 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 your system. Procedure For more information about the installation procedure for the SAP license, see: SAP NetWeaver 7.0 Library English SAP NetWeaver Library Technology Consultant s Guide Cross-NetWeaver Configurations SAP License Key More Information For more information about SAP license keys, see Creating Symbolic Links on Windows Server 2008 for Application Servers With Windows Server 2008 you can create symbolic links for dialog instances to simplify their administration. 04/30/2008 PUBLIC 109/200

110 5 Post-Installation 5.6 Installing the SAP Online Documentation Only valid for: HA (MSCS) In a high-availability system, you can additionally create symbolic links for the central instance. End of: HA (MSCS) Symbolic links for application servers let you access from your local host the SYS directory that is located on the global host, without having to specify its UNC path. Instead you can browse, for example in the Windows explorer on your local host to the SYS directory and its subdirectories on the global host. Procedure To create symbolic links, perform the following steps: 1. In the Start menu, right-click on Command Prompt and choose Run as administrator. 2. Enter the following command in a single line: mklink /d <localdisk>:\usr\sap\<sapsid>\sys \\<sapglobalhost>\sapmnt\<sapsid>\sys Enter a blank before \\<sapglobalhost>\ If you use a central transport directory, you can also create the following link: mklink /d <localdisk>:\usr\sap\trans \\<trans_dir_host>\sapmnt\trans The transport directory host <trans_dir_host> and the <sapglobalhost> can be identical. Caution The command mklink creates the link without checking whether the link target exists or is accessible. If the link does not work after you created it, make sure that it exists and check the accessibility of the UNC path. 5.6 Installing the SAP Online Documentation Caution This section does not apply to the installation of a Java Add-In to an existing ABAP system. SAP currently provides an HTML-based solution for the online documentation, including the Application Help, Glossary, Implementation Guide (IMG), and Release s. You can display the documentation 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 110/200 PUBLIC 04/30/2008

111 5 Post-Installation 5.7 Configuring Remote Connection to SAP Support Process Install the SAP online documentation in your SAP system as described in the README.TXT file contained in the root directory of the online documentation DVD, delivered as part of the installation package. 5.7 Configuring Remote Connection to SAP Support Caution This section does not apply to the installation of a Java Add-In to an existing ABAP system. SAP offers its customers access to support and a number of remote services such as the EarlyWatch Service or the GoingLive Service. Therefore, you have to set up a remote network connection to SAP. For more information, see SAP Service Marketplace at Applying the Latest Kernel and Support Packages You use this procedure to apply the latest kernel and Support Packages for your SAP system from SAP Service Marketplace. The following are available exclusively through the Maintenance Optimizer in SAP Solution Manager: All corrective software packages, including Support Packages (Stacks) for SAP NetWeaver 7.0 and subsequent versions All applications based on this software (including SAP Business Suite 2005), released after April 2, 2007 For more information about the Maintenance Optimizer, see SAP Solution Manager in Detail Change Request Management Maintenance Optimizer. A newly installed SAP Solution Manager 7.0 system contains SAP Solution Manager support package stack (SPS) 15. You can run the system on this SPS level without applying further support packages or you can apply further support packages that are available on SAP Service Marketplace. The SPS level of your SAP Solution Manager system determines which configuration guide you need to use later on. For more information, see Configuring SAP Solution Manager [page 123]. 04/30/2008 PUBLIC 111/200

112 5 Post-Installation 5.8 Applying the Latest Kernel and Support Packages Prerequisites For more information on how to download and apply Support Package Stacks, see the documentation SAP NetWeaver 7.0 Support Package Stack Guide <current version> on SAP Service Marketplace at To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you can find on SAP Service Marketplace at You need at least SAPCAR 700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR files. For more information, see SAP You can use Java Support Package Manager (JSPM) to apply both the latest ABAP+Java or Java kernel and Java support packages. JSPM is a Java standalone tool that you can use with SAP NetWeaver 7.0. JSPM uses the Software Deployment Manager (SDM) to apply support packages and patches and to deploy software components. For more information about JSPM and how to use this tool, see SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Maintenance Java Support Package Manager You can also use the Support Package Manager (SPAM) to apply the latest ABAP support packages. For more information about the Support Package Manager (SPAM) and how to use this tool, see SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Maintenance Support Package Manager 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: You installed the kernel executables locally on every host. 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 To exchange the ABAP+Java kernel, you can use Java Support Package Manager (JSPM). 2. Apply Support Packages. a) For up-to-date release information on Support Package Stacks, see SAP b) Download the required Support Package Stacks. c) Apply the ABAP Support Packages to your SAP system with the help of the Support Package Manager (formerly called SAP Patch Manager, transaction SPAM). d) Apply the Java Support Packages to your SAP system with the help of the Java Support Package Manager (JSPM). For more information about the availability of Support Packages, see the SAP Service Marketplace at: 112/200 PUBLIC 04/30/2008

113 5 Post-Installation 5.9 Performing Initial ABAP Configuration The SAP Assistant lets you load, implement, and organize individual SAP s efficiently. It also recognizes dependencies between SAP s, Support Packages, and modifications. For more information, see the SAP Service Marketplace at: Performing Initial ABAP Configuration Caution This section does not apply to the installation of a Java Add-In to an existing ABAP system. Here you can find information about how to perform initial ABAP system configuration. Procedure 1. Go to the following: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability 2. Check the documentation on the following configuration steps: Performing a consistency check When logging on to the system for the first time, you need to trigger a consistency check manually. The function is then called automatically whenever you start the system or an application server. For more information, see: Solution Life Cycle Management by Key Capability System Management Tools for Monitoring the System Utilities Consistency Check Configuring the transport management system For more information, see: Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics Change and Transport System Performing basic operations For more information, see the relevant section in Solution Life Cycle Management by Key Capability System Management : Operation Set up operation modes transaction RZ04 Section in SAP Documentation Configuration Operation Modes 04/30/2008 PUBLIC 113/200

114 5 Post-Installation 5.9 Performing Initial ABAP Configuration Operation Set up logon groups transaction SMLG Section in SAP Documentation Configuration Logon Load Balancing SAP Logon Set up administrators Background Processing Authorizations for Background Processing Schedule background jobs Install a printer Background Processing SAP Printing Guide Configure the system log Tools for Monitoring the System System log Configuring the System Log Configuring system parameters For more information about system profiles, which is where work processes and profile parameters are defined, and how to configure them, see: Solution Life Cycle Management by Key Capability System Management Configuration Profiles Configuring work processes SAPinst installs SAP systems with a minimum number of work processes. This is only an initial configuration to get you started after the installation. It is not detailed enough for a production system because the optimal number of each type of work process depends on the system resources and on the number of users working in each SAP system application. For more information about how many work processes to configure and how to set the number, see SAP s and Configuring Kernel parameters For more information about kernel parameter recommendations, see SAP s and Installing languages and performing language transport Installing languages using transaction I18N: If you want to use English only, you must activate the default language settings once. If you want to use languages other than English, you must install them and activate the language settings. For more information about configuring the language settings, see the online documentation in transaction I18N at I18N Menue I18N Customizing. Performing language transport using transaction SMLT: For more information about performing the language transport using transaction SMLT, see: Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics Change and Transport System Language Transport Using and Configuring the SAP ITS Integrated in ICM Since SAP NetWeaver 2004 ( 04), the SAP Internet Transaction Server (SAP ITS) is integrated in the SAP NetWeaver Application Server ABAP (AS ABAP) as an Internet Communication Framework (ICF) service. You can access this, like other services, with the Internet Communication Manager (ICM). With the SAP ITS integrated in AS ABAP, the Web browser 114/200 PUBLIC 04/30/2008

115 5 Post-Installation 5.10 Performing a Full System Backup now communicates directly with the SAP system. Furthermore, all SAP ITS-related sources, such as service files, HTML templates, or MIME files, are now stored in the database of the system. The SAP ITS supports the following functions: SAP GUI for HTML Internet Application Component (IAC) runtime or Web Transaction technology For more information about how to configure the integrated SAP ITS, see: Application Platform by Key Capability ABAP Technology UI Technology Web UI Technology SAP Internet Transaction Server SAP ITS in the SAP Web Application Server Configuration For more information about the ITS memory requirements, see SAP Maintaining address data For more information about maintaining the company address in your SAP system using transaction SU01, see: Application Platform by Key Capability Business Services Business Address Services (BC-SRV-ADR) Addresses in User Administration Maintenance of Address Data You must maintain your company address to create ABAP system users Performing a Full System Backup You must perform a full system back up at the end of the installation and configuration of your SAP system. Prerequisites You are logged on as user <sapsid>adm. You have shut down the SAP system and database. Procedure Back up your system including the operating system disk, system state, and all other disks Post-Installation Steps for Adobe Document Services If you want to use Adobe document services (ADS) in your SAP system landscape, you have to perform the following post-installation steps: 04/30/2008 PUBLIC 115/200

116 5 Post-Installation 5.11 Post-Installation Steps for Adobe Document Services Adobe document services (ADS) are only supported on a limited set of 64-bit platforms for SAP NetWeaver. For more information, see Running Adobe Document Services on Non-Supported Platforms [page 42]. You assign the required roles to users ADSUSER and ADS_AGENT [page 116]. You check the IIOP service and the startup properties [page 116]. You perform quick tests for Adobe Document Services (ADS) [page 117] 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 in the ABAP system, as described below. Assigning Role SAP_BC_FP_ICF to ADS_AGENT 1. Log on to the ABAP system with user DDIC or SAP*. 2. Call transaction SU 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 107]. 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 Checking the IIOP Service and the Startup Properties After the installation of the Adobe document services and before performing any other configuration steps you need to check special settings on the central instance host. If necessary, you need to adapt these settings manually. 116/200 PUBLIC 04/30/2008

117 5 Post-Installation 5.11 Post-Installation Steps for Adobe Document Services Procedure 1. Start the con guration tool of the AS Java by running \usr\sap\<sapsid>\<instance_name>\j2ee\configtool.bat. The Config Tool screen appears. 2. Check if the startup mode of the service iiop is set to always: a) In the left frame, open the tree Cluster data Cluster data Global dispatcher configuration Services. b) Choose service iiop. c) The field Startup mode in the right frame must be set to always. If it is not true, apply the value always. d) Choose Apply changes. e) Repeat the steps b. to d. for the following path: Cluster data Cluster data Global server configuration Services. 3. Check if the Java startup property for Adobe document services is set as follows: a) Select Cluster data Cluster data instance_<idxxxx> server_<idxxxx>. b) In the right frame, check if the following line exists in the Java Parameters area of the tab General: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots. PortableInterceptor.JTSInitializer If the line does not exist, add the line to this section. Caution Due to layout restrictions, this documentation cannot display the whole parameter in one line. We had to insert a line break in front of PortableInterceptor.JTSInitializer. In reality, this parameter must not contain any blank and must be entered in one line. 4. Exit the configuration tool. 5. If you have applied new values during the procedure above, you need to restart the AS Java to adapt the new settings Installation Check and Quick Tests for Adobe Document Services Adobe document services (ADS) can run in different IT scenarios, infrastructures and usage types in a new or in an upgraded installation. In some cases the installation process cannot perform all configuration settings that are necessary for the use of Adobe document services, for example, if ABAP and Java are not installed on the same server. Use this process to check whether all configuration steps are complete and to verify, which ones you still need to perform manually. Prerequisites Adobe document services are installed on your system. 04/30/2008 PUBLIC 117/200

118 5 Post-Installation 5.12 Ensuring User Security Procedure Check the ADS configuration as described in SAP NetWeaver 7.0 Library English SAP NetWeaver Library Technology Consultant s Guide Business Task Management Adobe Document Services (Configuration) Adobe Document Services Configuration Guide Configuring the Web Service Securing Access to the Web Service Configuration Check. More Information The Adobe Document Services Configuration Guide is also available in PDF form at Installation & Configuration SAP Interactive Forms Installation and Configuration Guides Adobe Document Services - Configuration Guide NW Ensuring User Security You need to ensure the security of the users that SAPinst creates during the installation. For security reasons, you also need to copy the installation directory to a separate, secure location such as a DVD and 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 Sockets Layer (SSL) protocol for HTTP connections, or Secure Network Communications (SNC) for the SAP protocols dialog and RFC. For more information, see: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Network and Transport Layer Security Caution Make sure that you perform this procedure before the newly installed SAP system goes into production. Prerequisites If you change user passwords, be aware that SAP system users might exist in multiple SAP system clients (for example, if a user was copied as part of the client copy). Therefore, you need to change the passwords in all the relevant SAP system clients. Procedure For the users listed below, take the precautions described in the SAP Solution Manager security guide, which you can find at 118/200 PUBLIC 04/30/2008

119 5 Post-Installation 5.12 Ensuring User Security Operating System and Database Users User User Name Comment Operating system user <sapsid>adm <smdsid>adm SAPService<SAPSID> SAP system administrator Administrator for the Diagnostics Agent User to run the SAP system ABAP+Java Users User User Name Comment SAP system user SAP* User exists at least in the clients 000, 001, and 066 auf the ABAP system. Recommendation We recommend that you use strong password and auditing policies for this user. DDIC User exists at least in the clients 000, 001, and 066 auf the ABAP system. Recommendation We recommend that you use strong password and auditing policies for this user. Administrator EARLYWATCH SAPCPIC The name that you gave this user during the installation or the default name J2EE_ADMIN User exists at least in the client 066 of the ABAP system. User exists at least in the clients 000 and 001 of the ABAP system. This user exists at least in the clients 000 and 001 of the ABAP system and has administrative permissions for user management. Guest The name that you gave this user during the installation or the default name J2EE_GUEST Recommendation We recommend that you use strong password and auditing policies for this user. This user exists at least in the clients 000 and 001 of the ABAP system and is used for anonymous access. 04/30/2008 PUBLIC 119/200

120 5 Post-Installation 5.12 Ensuring User Security User User Name Comment Communication user for the J2EE Engine Users for Adobe Document Services (ADS) Data supplier user for System Landscape Directory (SLD) (optional) ABAP API user for System Landscape Directory (SLD) (optional) The name that you gave this user during the installation or the default name SAPJSF. ADSUser ADS_AGENT The name that you gave this user during the installation. The recommended name is SLDDSUSER. The name that you gave this user during the installation. The recommended name is SLDAPIUSER. User exists at least in the clients 000 and 001 of the ABAP system. User exists at least in the clients 000 and 001 of the ABAP system. User exists at least in the clients 000 and 001 of the ABAP system. User exists at least in the clients 000 and 001 of the ABAP system. SAPinst created this user automatically if you chose Configure local SLD during the installation. User exists at least in the clients 000 and 001 of the ABAP system. SAPinst created this user automatically if you chose Configure local SLD during the installation. Java Add-In Users for Users Stored in the ABAP System User User Name Storage: ABAP System Comment Administrator The name that you gave this user during the installation or the default name J2EE_ADMIN User exists at least in the clients 000 and 001 of the ABAP system and has administrative permissions for user management. Guest Communication user for the J2EE Engine The name that you gave this user during the installation or the default name J2EE_GUEST The name that you gave this user during the installation or the default name SAPJSF Recommendation We recommend that you use strong password and auditing policies for this user. This user is used for anonymous access. This user is used for the communication between the ABAP system and the Java system. 120/200 PUBLIC 04/30/2008

121 5 Post-Installation 5.13 Checking the SAP Java Documentation User User Name Storage: ABAP System Comment Users for Adobe Document Services (ADS) Data supplier user for System Landscape Directory (SLD) (optional) ABAP API user for System Landscape Directory (SLD) (optional) ADSUser ADS_AGENT The name that you gave this user during the installation. The recommended name is SLDDSUSER. The name that you gave this user during the installation. The recommended name is SLDAPIUSER. User exists at least in the clients 000 and 001 of the ABAP system. User exists at least in the clients 000 and 001 of the ABAP system. User exists at least in the clients 000 and 001 of the ABAP system. SAPinst created this user automatically if you chose Configure local SLD during the installation. User exists at least in the clients 000 and 001 of the ABAP system. SAPinst created this user automatically if you chose Configure local SLD during the installation Checking the SAP Java Documentation Here you can find information about the configuration and administration of the J2EE Engine and about SAP Java technology in the SAP Library. Procedure 1. Go to SAP NetWeaver 7.0 Library English 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 Architecture Manual Contents This manual describes the architecture of a Java or ABAP+Java system. It contains information on: Java cluster architecture including central services, load balancing, and high availability. J2EE Engine system architecture SAP NetWeaver Java development infrastructure, including SAP NetWeaver Developer Studio The SAP NetWeaver Developer Studio is the SAP development infrastructure for Java. The Architecture Manual describes the 04/30/2008 PUBLIC 121/200

122 5 Post-Installation 5.13 Checking the SAP Java Documentation Manual Contents integration of the SAP NetWeaver Developer Studio into the SAP development infrastructure. Administration Manual This manual describes how to administer the SAP system, focusing on the J2EE Engine. It contains information on: System landscape administration Software life-cycle management This part of the manual contains important information about: Installation information System Landscape Directory (SLD) Software Lifecycle Manager (SLM) Java Support Package Manager Administration of SAP NetWeaver Java Development Infrastructure (JDI) J2EE Engine and J2EE Engine security Supportability and performance management Administration and configuration of Web Dynpro runtime environment Administration of the XML Data Archiving Service (XML DAS) Caution Make sure that you check the mandatory post-installation procedures listed in the Administration Manual under J2EE Engine Installation Information Post-Installation Procedures. Java Development Manual Migration Manual This manual describes the technologies for developing Java-based business applications. It explains how to use the SAP NetWeaver Developer Studio, which is the SAP Java development environment. This manual contains all the information you need to migrate an application created in J2EE Engine More Information For more information about troubleshooting for the J2EE Engine, see the J2EE Engine Problem Analysis Guide at: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) Usage Type Application Server Java J2EE Engine Problem Analysis Scenarios 122/200 PUBLIC 04/30/2008

123 5 Post-Installation 5.14 Configuring SAP Solution Manager 5.14 Configuring SAP Solution Manager To configure your SAP Solution Manager system, you have to proceed as follows: Procedure 1. Log on to the client 001 of the SAP Solution Manager system. 2. Call transaction SPRO 3. Choose SAP Reference IMG SAP Solution Manager Implementation Guide SAP Solution Manager Make sure that you have read the information in Read Me.You need to check all preparatory steps for the Solution Manager system as well as for connected satellite systems. All activities under Configuration Basic Settings Standard Configuration of Basic Settings are mandatory to ensure minimum SAP Solution Manager functionality. All activities under Configuration Scenario Specific Settings are optional and depend on the functions of SAP Solution Manager that you want to use. For more information, see the documentation Configuration Guide SAP Solution Manager <Current Release> as of <Current SP Level> on SAP Service Marketplace at SAP Components SAP Solution Manager <Current Release>. More Information For more information about the configuration of root cause analysis, see the Root Cause Analysis Installation and Upgrade Guide which you can find at one of the following: End-to-End Root Cause Analysis Documentation Library Installation and Configuration Root Cause Analysis Installation and Upgrade Guide SAP Components SAP Solution Manager <Current Release> 5.15 Post-Installation Steps for the Diagnostics Agent To implement the E2E Root Cause Analysis scenario, you have to configure the Diagnostics Agent. Prerequisites You have installed an AS Java central instance or dialog instance. Procedure Plan the implementation of the SAP Solution Manager Diagnostics Agent as described in the Root Cause Analysis Installation and Upgrade Guide, which you can find at 04/30/2008 PUBLIC 123/200

124 5 Post-Installation 5.16 Installing the SAP Solution Manager Enterprise Edition Add-On (Optional) 5.16 Installing the SAP Solution Manager Enterprise Edition Add-On (Optional) If you want to use the functionality of SAP Solution Manager Enterprise Edition, you have to install the SAP Solution Manager Enterprise Edition Add-On. Procedure Proceed as described in SAP More Information For more information, see the SAP Solution Manager Master Guide at: SAP Components SAP Solution Manager <Current Release> Master Guide SAP Solution Manager <Current Release> 124/200 PUBLIC 04/30/2008

125 6 Additional Information 6 Additional Information The following sections provide additional information about optional preparation, installation and post-installation tasks. There is also a section describing how to delete an SAP system. Preparation Database Installation for Multiple Components with MS SQL Server [page 125] Installation of Multiple Components in One Database [page 127] Integration of LDAP Directory Services [page 129] Installation Installation of Additional Software Units or Usage Types in an Existing SAP System [page 133] Post-Installation Starting and stopping the SAP system [page 136]. You configure Single Sign-On with Microsoft Kerberos SSP [page 137]. Configuring User Management to Use an LDAP Directory [page 142]. Initial Configuration for System Landscape Directory (SLD) [page 143] Initial Configuration of Adobe Document Services (ADS) [page 142] SAP System Security on Windows [page 144] Automatic Creation of Accounts and Groups [page 146] Troubleshooting [page 148] Deleting an SAP System Deleting an SAP System [page 148] 6.1 Database Installation for Multiple Components with MS SQL Server Each SAP system in your SAP environment needs its own database back end. With MS SQL Server you 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. 04/30/2008 PUBLIC 125/200

126 6 Additional Information 6.1 Database Installation for Multiple Components with MS SQL Server Exclusive database server In this system landscape, each database server (with or without a central instance) hosts exactly one SAP database. From an installation planning perspective, this is the simplest solution. It is the most scalable setup, but it requires the most hardware. This option is common for medium-sized and large production and development systems. Named SQL Server instances With the use of named instances, you can install multiple, independent SQL Server instances on a single database server. These instances share CPU, memory and disk resources, but are completely independent from each other in terms of administration. This option, like the following two, requires careful hardware sizing to avoid performance bottlenecks and scalability problems. Multiple databases in an SQL Server instance SQL Server lets you operate multiple user databases in a single SQL Server instance. Contrary to named instances, the databases share the temporary system database tempdb, the SQL Server Windows process, and the SQL Server memory pool. Therefore, this setup is less scalable than named instances, but at the same time requires less system resources. It can be a flexible solution for small and medium-sized systems. This option requires careful hardware sizing to avoid performance bottlenecks and scalability problems. Multiple Components in One Database (MCOD) Multiple database back ends are stored in the same database, each in its own database schema. For the database administrator, the database containing these multiple components looks similar to a single entity. While this approach is not as flexible as the other options, its simplicity makes it an attractive solution for small SAP environments. This option requires careful hardware sizing to avoid performance bottlenecks and scalability problems. More Information Default or Named MS SQL Server Instances [page 126] Multiple Components in One Database (MCOD) [page 127] Default or Named MS SQL Server Instances When you install MS SQL Server, you can install two different types of instances: Default instance 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 SAP environment. Typically, one MS SQL Server instance is installed together with a single SAP database. 126/200 PUBLIC 04/30/2008

127 6 Additional Information 6.2 Installation of Multiple Components in One Database (Optional) In this configuration, all MS SQL Server components and functionality are exclusively available for the SAP database. In a less frequently implemented configuration, a single MS SQL Server instance is installed together with more than one SAP database on the same computer. In this type of configuration, the MS SQL Server components such as executables, system databases and utilities exist only once and have to be shared by all SAP databases. Since all the databases on the computer have to be managed with a single copy of the MS SQL Server, certain administrative tasks on one database cannot be performed in isolation without affecting the other databases. A default instance is recommended, if you plan to install only one SAP database instance on a computer. Named Instance The advantage of named instances is that you can set up several SAP databases on the same machine and administer each one separately with its own copy of the MS SQL Server. The main components of the 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 only installed once. During the installation, each named instance is given a name that is the same as the SAP 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 the same machine. Several named instances and the default instance can coexist on the same computer and function in isolation of each other. 6.2 Installation of Multiple Components in One Database (Optional) Caution This section does not apply to the installation of a Java Add-In to an existing ABAP system. You can install multiple SAP systems in a single database. This is called Multiple Components in One Database (MCOD). MCOD is available with all SAP components. We are releasing this technology on all the major databases for the SAP system, in line with our commitment to deliver platform-independent solutions. Using this technology is as easy as installing a separate component. No extra effort is required because the MCOD installation is fully integrated into the standard installation procedure. MCOD is not an additional installation service. Instead, it is an option of the database instance installation. With MCOD we distinguish two scenarios: 04/30/2008 PUBLIC 127/200

128 6 Additional Information 6.2 Installation of Multiple Components in One Database (Optional) The installation of an SAP system in a new database The installation of an additional SAP system in an existing database Prerequisites For more information about MCOD and its availability on different platforms, see We have released MCOD for Unicode installations. A prerequisite is that the MCOD system contains Unicode instances only. SAP does not support mixed solutions. Improved sizing required In general, you calculate the CPU usage for an MCOD database by adding up the CPU usage for each individual SAP system. You can do the same for memory resources and disk space. You can size multiple components in one database by sizing each individual component using the SAP Quick Sizer and then adding the requirements together. For more information about the SAP Quick Sizer, see Features Reduced administration effort Consistent system landscape for backup, system copy, administration, and recovery Increased security and reduced database failure for multiple SAP systems due to monitoring and administration of only one database Independent upgrade In an MCOD landscape, you can upgrade a single component independently from the other components running in the same database, assuming that the upgraded component runs on the same database version. However, if you need to restore a backup, be aware that all other components are also affected. Special MCOD considerations and differences from the standard procedure are listed where relevant in 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 you mix test, development, and production systems in the same MCOD. In the event of database failure, all SAP systems running on the single database are affected. Automated support in an MCOD landscape for the following administrative tasks depends on your operating system and database: 128/200 PUBLIC 04/30/2008

129 6 Additional Information 6.3 Integration of LDAP Directory Services (Optional) 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. De-installing a single component from an MCOD landscape requires some additional steps. You can use a remote connection to SAP support to request help with these tasks. For more information, see Only valid for: HA (MSCS) MSCS only: You cannot install multiple components in one database with Microsoft Cluster Service (MSCS). For more information about MSCS, see High Availability with Microsoft Cluster Service [page 151]. End of: HA (MSCS) For the first SAP system, the DBSID must be the same as for the first SAP system installed in this database. For the second SAP system, you must use the same DBSID as for the first SAP system. Since 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) This section explains the benefits of using the SAP system with the Lightweight Directory Access Protocol (LDAP) directory and gives an overview of the configuration steps required to use an SAP system with the directory. LDAP defines a standard protocol for accessing directory services, which is supported by various directory products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory services enables important information in a corporate network to be stored centrally on a server. The advantage of storing information centrally for the entire network is that you only have to maintain data once, which avoids redundancy and inconsistency. If an LDAP directory is available in your corporate network, you can configure the SAP system to use this feature. For example, a correctly configured SAP system can read information from the directory and also store information there. The SAP system can interact with the Active Directory using the LDAP protocol, which defines: The communication protocol between the SAP system and the directory 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 can take advantage of the information stored there. For example, if there is an LDAP directory on a UNIX or Windows server, you can configure the SAP system to use the information available there. In the following text, directories other than the Active Directory that implement the LDAP protocol are 04/30/2008 PUBLIC 129/200

130 6 Additional Information 6.3 Integration of LDAP Directory Services (Optional) called generic LDAP directories. Caution This section does not provide information about the use of LDAP directories with the LDAP Connector. For more information about using and configuring the LDAP Connector for an ABAP system, see the SAP Library at: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management Identity Management of the Application Server ABAP Configuration of Identity Management Directory Services LDAP Connector Prerequisites You can only configure the SAP system for Active Directory services or other LDAP directories if these are already available on the network. As of Windows 2000 or higher, the Active Directory is automatically available on all domain controllers. A generic LDAP directory is an additional component that you must install separately on a UNIX or Windows server. Features In the SAP environment, you can exploit the information stored in an Active Directory or generic LDAP directory by using: SAP Logon The SAP Microsoft Management Console (SAP MMC) For more information about the automatic registration of SAP components in LDAP directories and the benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information in Directory Services on SAP Service Marketplace at: Microsoft Windows Server SAP Logon Instead of using a fixed list of systems and message servers, you can configure the SAP Logon in the sapmsg.ini configuration file to find SAP systems and their message servers from the directory. If you configure SAP logon to use the LDAP directory, it queries the directory each time Server or Group selection 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: If you use an Active Directory, you must set LDAPoptions= DirType=NT5ADS. For more information, see the SAP system profile parameter ldap/options. 130/200 PUBLIC 04/30/2008

131 6 Additional Information 6.3 Integration of LDAP Directory Services (Optional) You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either of the following is true: The client is not located in the same domain forest as the Active Directory 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. For other directory services, you can use LDAPnode to specify the distinguished name of the SAP root node. For more information, see the SAP system profile parameter ldap/saproot. SAP MMC The SAP MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central location. It is automatically set up when you install an SAP system on Windows. If the SAP system has been prepared correctly, the SAP MMC presents and analyzes system information that it gathers from various sources, including the Active Directory. Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can read system information straight from the directory that automatically registers changes to the system landscape. As a result, up-to-date information about all SAP application servers, their status, and parameter settings is always available in the SAP MMC. If you need to administer distributed systems, we especially recommend that you use the SAP MMC together with Active Directory services. You can keep track of significant events in all of the systems from a single SAP MMC interface. You do not need to manually register changes in the system configuration. Instead, such changes are automatically updated in the directory and subsequently reflected in the SAP MMC. If your SAP system is part of a heterogeneous SAP system landscape that comprises systems or instances both on UNIX and Windows platforms, you can also use the SAP MMC for operating and monitoring the instances running on UNIX. You can also use the SAP Management Console (SAP MC) for administering and monitoring SAP systems from a central location. For more information about the SAP MC and about how to configure it to access LDAP directories, see the documentation SAP Management Console at: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine Administration Tools SAP Management Console Configuration Tasks for LDAP Directories This section describes the configuration tasks you have to perform for the Active Directory or other (generic) LDAP directories. 04/30/2008 PUBLIC 131/200

132 6 Additional Information 6.3 Integration of LDAP Directory Services (Optional) Configuration Tasks for Active Directory To enable an SAP system to use the features offered by the Active Directory, you must configure the Active Directory so that it can store SAP system data. To prepare the directory, you use SAPinst to automatically: Extend the Active Directory schema to include the SAP-specific data types 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. Create the root container where information related to SAP is stored Control access to the container for SAP data by giving members of the SAP_LDAP group permission to read and write to the directory You do this by running SAPinst and choosing: <Your SAP product> Software Life-Cycle Options LDAP Registration Active Directory Configuration. You have to perform the directory server configuration only once. Then all SAP systems that need to register in this directory server can use this setup. Configuration Tasks for Generic LDAP Directories To configure other LDAP directories, refer to the documentation of your directory vendor. The SAPinst Installation Master DVD contains schema extensions for directory servers Netscape/iPlanet (ldregns4.txt) and OpenLDAP slapd (ldregslapd.schema). Both files are located in the directory \DATA_UNITS\IM_<platform>\COMMON\ADS. After you have applied the schema extension, you need to create a root container to store the SAP-related information and create a directory user that the SAP application server can use to write information to the directory. For more information about how to set up a Netscape/iPlanet directory server, see the documentation SAP System Information in Directory Services on SAP Service Marketplace at: Microsoft Windows Server Enabling the SAP System LDAP Registration Once you have correctly configured your directory server, you can enable the LDAP registration of the SAP system by setting some profile parameters in the default profile. To do this, run SAPinst once for your system and choose: <Your SAP product> Software Life-Cycle Options LDAP Registration LDAP Support If you use a directory server other than Microsoft Active Directory and/or non-windows application servers, you have to store the directory user and password information by using ldappasswd pf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and is therefore valid for all application servers. After restarting all application servers and start services, the system is registered in your directory server. The registration protocols of the components are dev_ldap*. The registration is updated every time a component starts. 132/200 PUBLIC 04/30/2008

133 6 Additional Information 6.4 Installation of Additional Software Units or Usage Types in an Existing SAP System 6.4 Installation of Additional Software Units or Usage Types in an Existing SAP System To install the Java based SAP Solution Manager Diagnostics in an existing SAP Solution Manager ABAP system upgraded to SAP Solution Manager 7.0, you cannot use SAPinst. Instead, you have to use the Java Support Package Manager (JSPM). In the following, the term additional software units or usage types is generally used for SAP Solution Manager Java components. Restrictions You can use the option Install Additional Usage Type only if the corresponding product is installed on the host where you start JSPM. For more information, see section Installation. JSPM cannot be used to install AS Java as a Java Add-In for an existing ABAP-only system. Instead, you have to use SAPinst. If you install the Java Add-In in an existing ABAP only system, you can also install further Java usage types or Java software units using SAPinst. If you want to install the Java Add-In, proceed as described in Installing the Java Add-In for an Existing ABAP System [page 92]. Prerequisites You have installed the Java Add-In [page 92]. Preparation 1. Make sure that the following documentation is available: You do not need to read the whole documentation. However, make sure that you read those parts of it referred to below in this procedure. For handling JSPM, use the documentation Java Support Package Manager at: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Check the Master Guide [page 11] for your SAP system application for supported/recommended combinations of UT that can be run in one system. Check the appropriate installation guide for your SAP system application for space requirements for the additional software units or usage types you want to install. 2. Check which software units or usage types are already installed on your system. You can do this in one of the following ways: 04/30/2008 PUBLIC 133/200

134 6 Additional Information 6.4 Installation of Additional Software Units or Usage Types in an Existing SAP System Start JSPM and choose the Deployed Components tab. Check the usage type system information page of your system using the URL For more information, see the SAP Library: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Maintenance Java Support Package Manager Viewing the Deployed Components 3. Check the dependencies for the software units or usage types you want to install: Software Units of SAP Solution Manager 7.0 Usage Type Name (Technical Name) Long Text Depends on SM SAP Solution Manager Diagnostics AS Java 4. Check hardware and software requirements for the software units or usage types you want to install. You cannot use the Prerequisite Checker [page 47] to check the requirements of additional software units or usage types. a) Check space requirements for the additional software units or usage types that you want to install. To do this, check the tables in Hardware and Software Requirements [page 45]. b) Check Java virtual memory settings according to SAP c) Check requirements for the Java Support Package Manager as described in: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Requirements for Free Disk Space 5. Download the required Software Component Archives (SCAs) and the appropriate stack definition file using the Maintenance Optimizer in SAP Solution Manager. For more information, see: SAP Solution Manager <Current Release> SAP Solution Manager Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance Recommendation We recommend that you also download the most current Support Package Stack for AS Java to update the JSPM to the most current SPS level. Java-Based Software Units of SAP Solution Manager /200 PUBLIC 04/30/2008

135 6 Additional Information 6.4 Installation of Additional Software Units or Usage Types in an Existing SAP System Components of SolManager Java (UT_NAME = SM): Name of SCA File LMSERVICE**_*.SCA Description SOLUTION MANAGER DIAGNOSTICS 6. Copy the downloaded SCAs and the appropriate stack definition file to the JSPM inbox directory. For more information, see: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Detecting and Changing the JSPM Inbox Directory Installation 1. Start JSPM as described in: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Starting JSPM 2. We strongly recommend that you update JSPM to the most recent Support Package stack level as described in: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Applying Single Support Packages 3. Depending on your SAP system landscape, you have to run different JSPM options: Run the option Install Additional Usage Type if the corresponding product is installed in the same system in which you start JSPM, as described in: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Installing an Additional Usage Type Run the option Deploying New Software Components if the corresponding product is not installed in the same system in which you start JSPM, as described in: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Deploying New Software Components Example Post-Installation After you have finished the deployment with JSPM, you need to perform initial configuration to complete the installation of additional software units or usage types before you perform the actual configuration. 04/30/2008 PUBLIC 135/200

136 6 Additional Information 6.5 Starting and Stopping the SAP System Caution You must not run the Configuration Wizard for the added software unit(s) or usage type(s). Instead, you have to configure them manually. 1. For initial configuration, perform the following steps: SAPinst performs these steps during the installation of a complete SAP Solution Manager system. JSPM does not perform these steps. Initial Technical Configuration for Adobe Document Services [page 142] Initial Technical Configuration for the System Landscape Directory [page 143] 2. For complete configuration of SAP Solution Manager Diagnostics, use the documentation Root Cause Analysis Installation and Upgrade Guide at Starting and Stopping the SAP System You use this procedure to check that you can start and stop the SAP system after the installation with the SAP Microsoft Management Console (SAP MMC). With a newly installed MMC you can start or stop installed SAP instances locally on the host that you are logged on to. You can also start and stop the Diagnostics Agent with the SAP MMC. If the MMC is configured for central system administration, you can start or stop the entire system from a single host. For more information, see: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS SAP Microsoft Management Console: Windows Prerequisites You have logged on to the SAP system host as user <sapsid>adm. You have checked the settings for VM parameters as described in SAP Procedure 1. Start the SAP MMC on the SAP system host by choosing Start All Programs SAP Management Console. 2. Right-click the SAP system node and choose Start or Stop. All instances listed under the system node start or stop in the correct order. 136/200 PUBLIC 04/30/2008

137 6 Additional Information 6.6 Single Sign-On with Microsoft Kerberos SSP 3. If the SAP system is installed on multiple hosts (distributed system), you have the following options to start or stop your system: 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 instance b) SCS instance c) Primary application server where the enqueue server and/or message server are running. d) Additional application server, if available. To stop your SAP system, use the reverse order. You add the remote instances to the MMC configuration to start or stop all instances from a single MMC. To do so, do one of the following: You configure the MMC manually. For more information, see Changing the Configuration of the MMC in the SAP MMC documentation. 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 first have to stop the additional application server, before you can stop the other SAP instances. You can also start and stop a UNIX system with the MMC. 6.6 Single Sign-On with Microsoft Kerberos SSP Kerberos Single Sign-On (SSO) is a secure method of logging on to the SAP system that simplifies the logon procedure. 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 can access the SAP system simply by selecting it in the SAP logon window or clicking the shortcut. There is no need to enter the SAP system user name and password when you log on to your SAP system with SAP GUI. SSO makes it significantly easier for you to manage SAP system users. The Microsoft Kerberos Security Service Provider (SSP) provides secure authentication plus encryption of the network communication. In contrast, SSO with Microsoft NTLM SSP does not provide encryption of the network communication. For more information, on Single Sign-On with Kerberos and the required DLLs, see SAP s and /30/2008 PUBLIC 137/200

138 6 Additional Information 6.6 Single Sign-On with Microsoft Kerberos SSP When using the <Kerberos5_name>.dll, the Microsoft Kerberos SSP might be interoperable with Kerberos implementations from other vendors and suppliers. However, SAP does not and cannot provide support for third-party libraries loaded at the BC-SNC interface. Documentation and support must be provided by the vendor or supplier of the third-party software. Therefore, we recommend 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 Under 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 higher domain. Process Flow To implement SSO with the Microsoft Kerberos SSP, you have to: 1. Prepare the central instance [page 138]. 2. Configure the SAP front ends [page 139]. 3. Configure the SAP logon [page 140]. 4. Map SAP users to Windows users [page 141] Preparing the Central Instance To set up Single Sign-On (SSO) for Kerberos, you need to adapt the central instance profile and make sure 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. The following Kerberos DLLs are available: gx64krb5.dll for Windows x64 gi64krb5.dll for Windows IA64 For more information about how to get the Kerberos 5 file, see SAP 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> 138/200 PUBLIC 04/30/2008

139 6 Additional Information 6.6 Single Sign-On with Microsoft Kerberos SSP <DNS_DOMAIN_NAME> is the Windows domain that the SAPService<SAPSID> user belongs to and <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 sure that you enter uppercase and lowercase correctly, for example: Additional SNC Parameters The following profile parameters let you continue with password-based access to the SAP system when SNC has been enabled. To log on to the SAP system as an administrator to maintain the mapping of Windows user accounts to SAP system user IDs (user and client), you have to use these additional parameters at least once after enabling SNC. Once the mapping (at least for the administrator) has been entered, you can disable further password-based logons by removing the corresponding 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 Configuring the SAP Front End To configure the SAP front end for SSO, you choose between the following approaches: Configure each SAP front end individually You configure each machine where the SAP front end is running. Configure all SAP front ends automatically You define a Group Policy for a Windows domain. This policy causes the wizard for configuring SSO to be started automatically in the background the next time any member of the domain logs on to an SAP front end. These approaches are described below. Prerequisites You have completed Preparing the Central Instance [page 138]. Configuring SAP Front Ends Individually 1. Log on to the host where the SAP front end is running. 04/30/2008 PUBLIC 139/200

140 6 Additional Information 6.6 Single Sign-On with Microsoft Kerberos SSP 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 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 Windows Server 2003 only: Choose Start Control Panel Administrative Tools Active Directory Users and Computers. The dialog box Active Directory Users and Computers appears. 4. Windows Server 2008 only: Choose Start Administrative Tools Active Directory Users and Computers. The dialog box Active Directory Users and Computers appears. 5. Right-click the domain for which you want to set up SSO and choose Properties. The dialog box <Domain_Name> Properties appears. 6. Choose Group Policy New to start creating a new policy object. The dialog box for creating a new policy object appears. 7. In group Policy Object Links, enter a name for the new policy object, such as SAPSSO. 8. Choose Edit to define the contents of the policy. 9. In the Group Policy Editor, choose User Configuration Software Settings Software Installation.. The Deploy Software dialog box appears. 10. Right-click Deploy Software and choose New Package. The Open dialog box appears. 11. Select the file SAPMSSO.MSI from the shared location. 12. Specify the path with the UNC name (\\<hostname>\<share>). 13. Select Assign and confirm with OK. You have now created a new Group Policy. The next time any user logs on to the domain with the SAP front end, the wizard SAP Kerberos SSO Support automatically starts and configures the front end for SSO Activating Single Sign-On for the SAP Logon The SAP Logon window includes a list of systems or machines that you can log on to. For each of the systems or machines in the list for which you want to implement SSO, follow the procedure below. 140/200 PUBLIC 04/30/2008

141 6 Additional Information 6.6 Single Sign-On with Microsoft Kerberos SSP Prerequisites You have completed the following: Preparing the Central Instance [page 138] Configuring the SAP Front End [page 139] 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: where <UPPERCASE_DOMAIN_NAME> is, for example, NT5.SAP-AG.DE. Enter the same string that you entered in the central instance profile for snc/identity/as If the system C11 is running on account SAPServiceC11 of the domain NT5.SAP-AG.DE, you enter: If the entry you selected in the logon dialog box is a group entry, for example, C11 (PUBLIC), the SNC name field is already filled. 4. Choose OK to confirm your entries. The SAP Logon window now displays an icon with a key beside the system entry. This indicates that Single Sign-On is active for the system Mapping SAP Users to Windows Users Prerequisites You have completed the following: Preparing the Central Instance [page 138] Configuring the SAP Front End [page 139] Activating Single Sign-On for the SAP Logon [page 140] 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. 04/30/2008 PUBLIC 141/200

142 6 Additional Information 6.7 Configuring User Management to Use an LDAP Directory (Optional) 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: where <WINNT_USERNAME> is the logon ID of the Windows user as spelled in the Active Directory and <UPPERCASE_DNS_DOMAIN_NAME> is the uppercase DNS domain name of the Windows domain that the user is logged on to. Example For the user smith, belonging to the domain NT5.SAP-AG.DE, enter: 6. Select Insecure communication permitted. This lets the user work in a different domain because it permits the user to access the system without SSO. 7. Save your entries. 6.7 Configuring User Management to Use an LDAP Directory (Optional) If your user data source is an LDAP directory, you need to configure the connection to the LDAP directory after installation. For more information, see SAP and SAP Library at SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management Identity Management of the Application Server Java Configuring Identity Management UME Data Sources LDAP Directory as Data Source Configuring UME to Use an LDAP Directory as Data Source 6.8 Initial Technical Configuration for Adobe Document Services SAPinst automatically performs some initial technical configuration steps for Adobe Document Services (ADS) during the installation. However, you might have to perform these steps manually if you want to change existing parameters or if you want to set additional parameters. SAPinst performs the following steps: SAPinst creates user ADSUser in AS ABAP for basic authentication and assigns it to group ADSCallers. 142/200 PUBLIC 04/30/2008

143 6 Additional Information 6.9 Initial Technical Configuration for the System Landscape Directory (SLD) For more information about this user, see Ensuring User Security [page 118]. SAPinst creates user ADSUser in AS Java for basic authentication and assigns it to group ADSCallers. For more information about this user, see Ensuring User Security [page 118]. SAPinst creates service user ADS_AGENT in the ABAP Environment. SAPinst creates an ABAP connection for basic authentication. SAPinst creates destination service FP_ICF_DATA_<SAPSID>. SAPinst sets up basic authentication in the Java environment. You can find a detailed description of how to perform these steps manually in the SAP Library at: SAP NetWeaver 7.0 Library English SAP NetWeaver Library Technology Consultant s Guide Business Task Management Adobe Document Services (Configuration) Adobe Document Services Configuration Guide Configuring the Web Service Securing Access to the Web Service Configuration of the Web Service for Basic Authentication More Information The Adobe Document Services Configuration Guide is also available in PDF form at: Installation & Configuration SAP Interactive Forms Installation and Configuration Guides Adobe Document Services - Configuration Guide NW Initial Technical Configuration for the System Landscape Directory (SLD) SAPinst automatically performs some initial technical configuration steps for the System Landscape Directory (SLD) during the installation: If you chose the option Register in existing central SLD, SAPinst automatically configures the connection of the system being installed to an existing central System Landscape Directory (SLD). If you chose the option Configure a local SLD, SAPinst automatically sets up and configures a local System Landscape Directory (SLD) during the installation. Caution We strongly recommend that you set up a local SLD on the SAP Solution Manager system with connection and replication from the productive SLD instances in your existing landscape. For more information, see System Landscape Directory [page 20]. However, you might have to perform these steps manually if you want to change existing parameters or if you want to set additional parameters. SAPinst performs the following steps: SAPinst configures SLD security roles. SAPinst configures server and persistence parameters. SAPinst performs the initial data import. 04/30/2008 PUBLIC 143/200

144 6 Additional Information 6.10 SAP System Security on Windows SAPinst configures the SLD bridge. You can find a detailed description of how to perform these steps manually in the documentation Post Installation Guide System Landscape Directory of SAP NetWeaver 7.0 at Installation Configuration. More Information For more information about working with and configuring the SLD, see the SAP Library at: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management System Landscape Directory More documentation is also available at For more information about security and on the role concept in the SLD, see the SAP Library at: SAP NetWeaver 7.0 Library English SAP NetWeaver Library Administrator s Guide SAP NetWeaver Security Guide Security Aspects for System Management Security Guide for the SAP System Landscape Directory For more information on the configuration of SLD in the context of root cause analysis, see the Root Cause Analysis Installation and Upgrade Guide which you can find at one of the following: End-to-End Root Cause Analysis Documentation Library Installation and Configuration Root Cause Analysis Installation and Upgrade Guide SAP Components SAP Solution Manager <Current Release> 6.10 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 must still check that no security breaches can occur. For central and straightforward administration of the SAP system, you have to install distributed SAP systems with multiple application servers in a Windows domain. This section describes the user accounts and groups that SAPinst creates during a domain installation and shows how these are related to the SAP directories. User Accounts SAPinst creates the following accounts for SAP system administration: <sapsid>adm This is the SAP system administrator account that enables interactive administration of the system. SAPService<SID> This is the user account that is required to start the SAP system. It has the local user right to log on as a service. 144/200 PUBLIC 04/30/2008

145 6 Additional Information 6.10 SAP System Security on Windows The advantage of the additional SAPService<SAPSID> account is that it does not allow an interactive logon, which prevents abuse of the account. Therefore, you do not need to set an expiration date for the 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: SAP_<SAPSID>_GlobalAdmin This global group is a domain-level SAP administration group for organizing SAP system administrators. The only function of a global group is to group users at the domain level so that they can be placed in the appropriate local groups. SAP_<SAPSID>_LocalAdmin Only local groups are created and maintained on an application server. A local group can only be given permissions and rights to the system where it is located. The system is part of a particular domain, and the local group can contain users and global groups from this domain. SAP_LocalAdmin This group is created on all hosts, but is particularly important for the transport host. Members of the group have full control over the transport directory (\usr\sap\trans) that allows transports to take place between systems. The SAP_<SAPSID>_GlobalAdmin groups of all the SAP systems that are part of the transport infrastructure are added to the SAP_LocalAdmin group. As a consequence, the users <sapsid>adm and SAPService<SAPSID> of all systems in the transport infrastructure are members of the SAP_LocalAdmin group and have the required authorizations necessary to initiate and execute transports. SAP Directories SAPinst protects the SAP directories under \usr\sap\<sapsid> by only granting the group SAP_<SAPSID>_LocalAdmin full control over these directories. The following graphic illustrates the user accounts and groups created by SAPinst in a system infrastructure consisting of two SAP systems. 04/30/2008 PUBLIC 145/200

146 6 Additional Information 6.11 Automatic Creation of Accounts and Groups Figure 10: User Groups and Accounts An access control list (ACL) controls access to SAP system objects. For maximum security in the SAP system, only the following are members of all SAP system object ACLs: Local group SAP_<SAPSID>_LocalAdmin Group Administrators Account SYSTEM 6.11 Automatic Creation of Accounts and Groups SAPinst automatically creates the accounts and groups required for the secure operation of the SAP system with Windows [page 144] during the installation. Features The following figures show the steps that SAPinst performs to create the users and groups and assign the required rights to SAP directories. 146/200 PUBLIC 04/30/2008

147 6 Additional Information 6.11 Automatic Creation of Accounts and Groups Figure 11: Creating Users and Groups Figure 12: Assigning Rights to SAP Directories 04/30/2008 PUBLIC 147/200

148 6 Additional Information 6.12 Troubleshooting 6.12 Troubleshooting The following section(s) describe the steps that you need to perform manually if SAPinst fails: Troubleshooting with SAPinst [page 148] Troubleshooting with SAPinst This section tells you how to proceed when errors occur during the installation with SAPinst. If an error occurs, SAPinst: Stops the installation 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: Try to solve the problem Abort the installation with Exit For more information, see Interrupted Installation with SAPinst [page 96]. 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 software components are not available. For more information, see SAP Deleting an SAP System The following sections describe how to delete a single instance, a standalone engine or a complete SAP system with SAPinst. To delete your system, you use the SAPinst service <SAP System> Software Life-Cycle Options Uninstall Uninstall System / Standalone Engine / Optional Standalone Unit. This description assumes that you have installed your SAP system with standard SAP tools according to the installation documentation. 148/200 PUBLIC 04/30/2008

149 6 Additional Information 6.13 Deleting an SAP System Caution Make sure that all remaining instances are stopped before you delete the database instance. You cannot delete an SAP system remotely. SAPinst deletes the database instance but you have to delete the database software manually. In an ABAP+Java system you cannot uninstall the Java part only. Instead you can prevent the Java system from starting by setting the following parameter in the instance profile: rdisp/j2ee_start = 0 If you delete network-wide users, groups or service entries in an environment with Network Information System (NIS), other SAP installations might also be affected. Make sure that the users, groups, and service entries to be deleted are no longer required. Process Flow If you want to delete a central system, where all SAP instances reside on the same host, you can do this in one SAPinst run [page 149]. SAPinst deletes the database instance but you have to delete the MS SQL Server database software with the SQL Server Uninstaller, which you can find on Windows under Add/Remove Programs. If you want to delete a distributed system, where the SAP instances reside on different hosts, you have to run SAPinst [page 149] to delete the required instances locally on each host in the following sequence: 1. You delete the dialog instance(s), if there are any. 2. You delete the database instance. 3. You delete the central instance. 4. You delete the central services instance. 5. Only valid for: HA (MSCS) You delete the ABAP central services instance. End of: HA (MSCS) 6. You delete the MS SQL Server database software with the SQL Server Uninstaller, which you find on Windows under Add/Remove Programs Running SAPinst to Delete an SAP System This procedure tells you how to run the Uninstall option of SAPinst. 04/30/2008 PUBLIC 149/200

150 6 Additional Information 6.13 Deleting an SAP System Prerequisites You are logged on with a user account that has the required authorization to run the SAPinst tool and the SAP system. For more information, see Required User Authorization for the Installation [page 61]. Procedure 1. Start SAPinst and on the Welcome screen, choose: Software Life-Cycle Options Uninstall Uninstall System / Standalone Engine / Optional Standalone Unit With this SAPinst option you do not delete the database software. 2. Follow the instructions in the SAPinst input dialogs. For more information about the input parameters, place the cursor on the relevant field and press 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 SAP System [page 148]. Caution SAPinst only stops local instances automatically. Before you delete the database instance of a distributed system make sure that you stop all remaining instances. You must stop the instance with the message server only after having entered all SAPinst parameters for the deletion of the database instance. If SAPinst stops responding while trying to delete the central instance, close SAPinst with Cancel and Exit. Log off and log on again. To complete the uninstall process of the central instance, restart SAPinst. 3. Delete the local user group SAP_<SAPSID>_LocalAdmin manually as follows: a) Choose Start Programs Administrative Tools Computer Management b) 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 Server Uninstaller, which you can find on Windows under Add/Remove Programs. 5. If required, you can delete the directory \usr\sap\trans and its contents manually. SAPinst does not delete \usr\sap\trans because it might be shared. 150/200 PUBLIC 04/30/2008

151 7 High Availability with Microsoft Cluster Service Only valid for: HA (MSCS) 7 High Availability with Microsoft Cluster Service As of Windows Server 2008 there are the following terminology changes for a cluster configuration: The cluster feature is now called Failover Clustering. For practical reasons we also use the previous terminology Microsoft Cluster Service and abbreviation MSCS in this guide. Cluster groups are now called services and applications. In some sections that are also valid for Windows Server 2008 on MSCS we are continuing to use only the old term. In this case, cluster group also means service and application. The Cluster Administrator is now called Failover Cluster Management. You can install a high-availability SAP system with MSCS. For this type of installation, you have to set up the system and configure it so that it can take advantage of the MSCS software. The MSCS software improves the availability of the system and safeguards it against failure and unplanned downtime, enabling 24-hour operation, 365 days a year. With high availability you enable critical system components, known as Single Points of Failure (SPOFs), to be automatically switched from one machine to the other, if hardware or software problems arise on one machine. With the help of this switchover or failover the system can continue functioning so that unplanned system downtime is avoided. Apart from enabling failover when hardware problems occur, you can also use MSCS to avoid downtime when you perform essential system maintenance. If you need to maintain one host (MSCS node), you can deliberately switch the cluster resources to the other host (MSCS node) and temporarily operate it there while maintenance is in progress. When maintenance work is finished you can easily move the resources back to their original node and continue operating them there. You have the following options to install a high-availability system with MSCS: You install one SAP system in one MSCS cluster. You install one SAP system in two MSCS clusters. In both cases the following restrictions apply: You must install the (A)SCS instance on two MSCS nodes in one MSCS cluster. 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. 04/30/2008 PUBLIC 151/200

152 7 High Availability with Microsoft Cluster Service 7.1 Planning Make sure that you read SAP , which contains the most recent information as well as corrections for a high-availability installation. For more information, see the SAP installation notes [page 11] before you begin the installation. In this documentation the hosts in an MSCS cluster are referred to as first MSCS node and additional MSCS node(s). When you are setting up the SAP system with MSCS, you combine standard installation steps, described earlier in this documentation, with cluster-specific steps, described here. To install a new SAP system with MSCS, you have to perform a number of extra steps specially required for the cluster and configure the SAP system so that it can take advantage of the cluster functionality: You cluster the SQL Server already when you install the database software. Since the cluster hardware has at least two nodes that have access to all local and shared storage devices, you have to install some components on all nodes and observe special rules for distributing components to local or shared disks. Since the correct configuration of network addresses is absolutely essential to enable the cluster to function properly, you have to perform a number of additional steps that are necessary to set up and check addressing. If you have an existing SAP system and plan to migrate to a cluster with new hardware, you install the SAP system using a system copy. For more information about the system copy, see the System Copy Guide for your SAP system on SAP Service Marketplace at <Release> Installation. The documentation for system copy does not include the cluster-specific information, which is described here. 7.1 Planning You have to complete the following planning activities for you SAP system using Microsoft Cluster Service (MSCS): 1. You check that you have completed the general planning activities [page 17]. 2. You decide how to set up your SAP system components in an MSCS configuration [page 153]. 3. You decide how to distribute components to disks for MSCS [page 158]. 4. You read Directories in an MSCS Configuration [page 160] 5. You read IP Addresses in an MSCS Configuration [page 161] 6. You obtain and check IP addresses for MSCS [page 164]. 152/200 PUBLIC 04/30/2008

153 7 High Availability with Microsoft Cluster Service 7.1 Planning Windows Server 2008 only: This step is not required if you use DHCP-based IP addresses System Configuration in MSCS The following chapters provide information about the configuration of your SAP system configuration in MSCS. It describes the components you have to install for an SAP system running in a cluster, and how to distribute them on the specific host. For more information, see: SAP System Components in an MSCS Configuration [page 153] Enqueue Replication Server in MSCS [page 157] SAP System Components in an MSCS Configuration In an MSCS configuration you have the following components for your SAP system: SAP System Components in an MSCS Configuration Component SCS instance (message services and enqueue services) ASCS instance (message services and enqueue services) Number of Components per SAP System 1 yes 1 yes Database instance 1 yes Application server (central instance, dialog instance) 1-<n> Single Point of Failure (SPOF) no 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 instance and 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 you can 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. To protect system components that are non-spofs, for example application servers, you have to install them as multiple components. In this case you must install at least two application servers (one central instance and at least one dialog instance) on two different hosts. You have the following options: 04/30/2008 PUBLIC 153/200

154 7 High Availability with Microsoft Cluster Service 7.1 Planning 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 outside of the MSCS cluster. If you have to maintain an MSCS node, you have to stop the central or dialog instance on that node. When you have finished maintenance, you restart the instance(s). If you install the central instance and the dialog instance on the MSCS cluster nodes, you must perform the hardware sizing for the MSCS host, as in this case the application server is always running on this host. This increases system load and might impact performance. that, as usual in an MSCS setup, the (A)SCS and database instances also switch to run on the MSCS host in the event of failover, which temporarily also increases system load. You install the central instance and all dialog instances on hosts, which are not part of an MS cluster. In an ABAP+Java system, the ASCS and SCS instance of an SAP system run in one cluster group. They use the same share, IP address and network name. The following figures show examples for the installation of SPOFs and non-spofs of an SAP system in an MSCS cluster with two nodes. 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) are installed outside the MSCS cluster on separate hosts. 154/200 PUBLIC 04/30/2008

155 7 High Availability with Microsoft Cluster Service 7.1 Planning Figure 13: ABAP+Java System with SPOFs, where non-spofs are installed locally on the MSCS Cluster Nodes The following figure shows an MSCS configuration, where the non-spofs components (central instance, dialog instance) are installed on separate hosts that are not part of the MS cluster. 04/30/2008 PUBLIC 155/200

156 7 High Availability with Microsoft Cluster Service 7.1 Planning Figure 14: 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 clusters and 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 in one MSCS cluster, and the (A)SCS instance is installed on the second MSCS cluster. The application servers (central and dialog instance) can either be installed on a local disk on the MSCS nodes or on separate hosts that are not part of the MS cluster. 156/200 PUBLIC 04/30/2008

157 7 High Availability with Microsoft Cluster Service 7.1 Planning Figure 15: ABAP+Java System Enqueue Replication Server in an MSCS Configuration The enqueue replication server contains a replica of the lock table (replication table) and is an essential component in a high-availability setup. You have to install the enqueue replication server on the two MSCS nodes where the (A)SCS instance is installed and configured to run. In normal operation the replication enqueue server is always active on the host where the (A)SCS instance is not running. If an enqueue server in an MSCS cluster with two nodes fails on the first MSCS node, the enqueue server on the additional MSCS node is started. It retrieves the data from the replication table on that node and writes it in its lock table. The enqueue replication server on the second MSCS node then becomes inactive. If the first MSCS node is available again, the enqueue replication server on the second MSCS node becomes active again. The following figure shows the enqueue replication server mechanism in an MSCS configuration with two nodes: 04/30/2008 PUBLIC 157/200

158 7 High Availability with Microsoft Cluster Service 7.1 Planning Figure 16: Enqueue Replication Server Mechanism on One MSCS Cluster with Two Nodes Distribution of Components to Disks for MSCS One of the main points to keep in mind when planning the MSCS installation is that the cluster hardware has two different sets of disks: Local disks that are connected directly to the MSCS node(s) Shared disks that can be accessed by all MSCS nodes via a shared interconnect 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: Separately on all MSCS nodes to use the local storage on each node On the shared storage that is used in common by all MSCS nodes You install the following on different shared disks: Database instance (A)SCS instance Single quorum device, if used On Windows there are several quorum configurations available. The configuration to use depends, for example, on the number of data centers or type of storage replication used, the performance of the storage, and the number of cluster nodes. For more information, see the Windows documentation. The default quorum configurations used on Windows are: 158/200 PUBLIC 04/30/2008

159 7 High Availability with Microsoft Cluster Service 7.1 Planning Single Quorum Device Cluster (default quorum configuration on Windows Server 2003) On Windows Server 2008, this quorum configuration is called No Majority: Disk Only. However, we do not recommend you to use this. In this cluster model, the quorum resource maintains the cluster configuration data on a single cluster 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: It logs changes to the cluster configuration that are entered in the Registry. It arbitrates between competing nodes when the communication between nodes breaks down. This means that cluster resources are forced to fail over to the node that owns the quorum resource. Node and Disk Majority (default quorum configuration on Windows Server 2008) With this quorum configuration, each node and the witness disk maintain its own copy of the cluster configuration data. This ensures that the cluster configuration is kept running even if the witness disk fails or is offline. that the disk layout of the Node and Disk Majority and the Single Quorum Device Cluster is identical. Caution If you do not use the default quorum configuration for your operating system, contact your hardware partner, who can help you to analyze your needs and set up your cluster model. SAP supports these configurations if they are part of a cluster solution offered by your Original Equipment Manufacturer (OEM), or Independent Hardware Vendor (IHV). The following figures show a cluster configuration, where the (A)SCS and DB instance are installed in the same cluster. They illustrate 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 distinct disks is it possible to move the SAP system and database as separate entities in a failover situation. 04/30/2008 PUBLIC 159/200

160 7 High Availability with Microsoft Cluster Service 7.1 Planning Figure 17: Distribution of SAP System Components in MSCS More Information Directories in an MSCS Configuration [page 160] Directories in an MSCS Configuration The following tables show the directories where the main software components for the SAP cluster installation are stored: Directories on Local Disks on MSCS Nodes Component A supported operating system [page 54] MSCS software SAP cluster files Default Directory %windir% %windir%\cluster %windir%\sapcluster Directories on Shared Disks Component Default Directory Cluster quorum resource <drive>:\mscs (Windows Server 2003) <drive>:\cluster (Windows Server 2008) SAP global and instance directories <drive>:\usr\sap /200 PUBLIC 04/30/2008

161 7 High Availability with Microsoft Cluster Service 7.1 Planning Component tempdb databases msdb, model, master SAP data files Default Directory <drive>:\tempdb <drive>:\mssql <drive>:\<sapsid>data0 <drive>:\<sapsid>data1 <drive>:\<sapsid>data2 <drive>:\<sapsid>data3... <drive>:\<sapsid>data<n> SapCluster Directory In an SAP cluster installation, an additional directory %WINDIR%\SapCluster is created under the system directory. This contains all the SAP files required by all MSCS cluster nodes, independently of the MSCS node the SAP instance is running on. The files are database tools and program files (executables) used by the operating system monitor (SAPOsCol). The directory is added to the path variable of the user <sapsid>adm IP Addresses in an MSCS Configuration A part of the installation process that is unique to MSCS is the configuration of host names and IP addresses in the network. This is a particularly important task because the addressing plays a key role in the switchover procedure. Addressing must be set up correctly so that the system can take advantage of the cluster functionality and switch between nodes when hardware problems arise. This section explains the different types of IP addresses and their function in the switchover mechanism of an MSCS cluster with two nodes. Windows Server 2008 only: As of Windows Server 2008, besides static IP addresses, you can also have DHCP-based (dynamic) IP addresses. The DHCP-based IP addresses are currently only supported when all MSCS nodes are located in the same subnet. If the network adapters are assigned to DHCP-based IP addresses, the virtual IP addresses are also configured automatically as DHCP-based IP addresses. Types of IP Addresses In a correctly configured cluster with two nodes, there are seven IP addresses and corresponding host names for your SAP system. You have two IP addresses for each MSCS node, one IP address for the cluster, one for the SAP cluster group, and one for the database cluster group. 04/30/2008 PUBLIC 161/200

162 7 High Availability with Microsoft Cluster Service 7.1 Planning Some of the addresses are assigned to the network adapters (cards), others are virtual IP addresses that are assigned to the cluster groups. Physical IP Addresses Assigned to Network Adapters An MSCS configuration has two networks: A public network that is used for the communication between the central instance, application servers and the LAN. A private network that is used internally for communication between the nodes of the cluster. For more information, see the Microsoft Knowledge Base Article The following figure shows an MSCS cluster with two nodes and illustrates the adapters required for the 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. Figure 18: Adapters and IP Addresses Required for Public and Private Networks in an MSCS Cluster with Two Nodes Host Names Assigned to Network Adapters Each of the physical IP addresses of the network adapters must have a corresponding host name. For example, on the left-hand node in the figure above, you might assign the IP addresses of the public and private network adapters as follows: 162/200 PUBLIC 04/30/2008

163 7 High Availability with Microsoft Cluster Service 7.1 Planning IP Addresses and Host Names Network Adapter IP Address Host Name Adapter 1 (private network) clusa_priv Adapter 3 ( public network) clusa Caution Make sure that you are aware of the following: The IP address and host name of the public network adapter is also the IP address and name of the machine. In our example, this means that the machine that is the MSCS node on the left in the figure has the name clus1. Do not confuse the host name with the computer name. Each node also has a computer name, which is often the same as the host name. The computer name is displayed in the node column of the Cluster Administrator (Windows Server 2003) or Failover Cluster Management (Windows Server 2008). However, it is not required for the TCP/IP communication in the cluster. When you configure IP addresses and corresponding names, keep in mind that it is the host names that are important for the cluster, 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 resources are bound together in three different groups. Each of these groups requires a virtual IP address and host name that is permanently mapped to the group and not to a particular node. This has the advantage that, whenever a group is moved between nodes, its IP address and host name move together with it. A cluster configuration has the following groups: SAP cluster group Database cluster group Cluster group Windows Server 2008 only: Although it exists, the cluster group is not visible. Each group consists of a set of related resources that work together to offer a service to the system. For example, the database cluster group comprises all the resources that enable the database server to fulfill the requests of a client. When the group is moved from one node to the other, due to node failure, the virtual IP address and host name move with it. Therefore, there is a failover not only of resources, but also of the virtual IP address and host name. As a result, all clients can still reach the database server with the same IP address as before. 04/30/2008 PUBLIC 163/200

164 7 High Availability with Microsoft Cluster Service 7.1 Planning The following figure illustrates how the virtual IP addresses of the database group and SAP group can move from one node to the other when failover occurs. Figure 19: Failover of Virtual IP Addresses Obtaining and Determining IP Addresses for MSCS Windows Server 2008 only: As of Windows Server 2008, besides static IP addresses you can use DHCP-based IP addresses. The following information is only relevant if you use static IP addresses. This chapter describes how to obtain and to find out the IP addresses for the network adapters (cards) that are required to install and run your cluster configuration. You need to correctly configure IP addresses for a cluster system. During the installation procedure you have to assign at least seven IP addresses and host names. You normally obtain these names and addresses from the system administrator. Obtaining IP Addresses Ask 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 need to enter the addresses and host names later during the installation process. The column Defined During indicates at which stage of the installation of the operating system and the SAP system the addresses are defined in the system. 164/200 PUBLIC 04/30/2008