CRM 7.0

Installation Guide SAP CRM 7.0 Including SAP Enhancement Package 1 Java on Windows: SAP MaxDBBased on SAP NetWeaver 7.0 Including Enhancement Package 2Target Audience System Administrators Technical Consultants

PUBLIC Document version: 1.0 2010-12-20

About this Installation Guide

SAP System Installation

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 installingSAP Installation Tool

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.Downward Compatibility of Databases

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. Note 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. That is, you either install the component with the old proposed database version or you upgrade the old database version to the downward-compatible new version.

2/210

PUBLIC

2010-12-20

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location:http://service.sap.com/crm-inst. The following table provides an overview of the most important document changes.Version Date Description

1.0

2010-12-20

Initial Version

2010-12-20

PUBLIC

3/210

Table of Contents

Chapter 1 1.1 1.2 1.3 Chapter 2 2.1 2.2 2.3 2.4 2.5 2.6 Chapter 3 3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.3 3.4 3.5 3.6 3.7 3.8

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . Central System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of Additional Usage Types or Software Units in an Existing SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Prerequisite Checker in Standalone Mode (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for a Central System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements for the Host Agent as a Separate Installation . . . . . . . . . . . . . . . Planning User and Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain or Local Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution of Components to Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet Pricing and Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11 12 13 14 17 17 18 19 19 21 22 23 23 24 25 26 28 30 33 33 35 36 46 47 48 49

4/210

PUBLIC

2010-12-20

Chapter 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 Chapter 5 5.1 5.2 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.4

Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling the Windows Server 2008 (R2) Firewall . . . . . . . . . . . . . . . . . . . . . . . Performing Basic Windows Preparation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . Required User Authorization for Running SAPinst . . . . . . . . . . . . . . . . . . . . . Preparing the SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating the SAP Solution Manager Key . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Java Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading JCE Policy Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites for the Business Packages for SAP CRM . . . . . . . . . . . . . . . . . . . . Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entries in the Services File Created by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Business Packages for SAP CRM Using JSPM (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Database Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging On to the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging On to the SAP NetWeaver Development Infrastructure (NWDI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applying the Latest Kernel and Support Package Stacks . . . . . . . . . . . . . . . . . Creating Symbolic Links on Windows Server 2008 (R2) for Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

51 51 52 52 55 56 57 58 58 59 60 63 63 64 68 68 69 70 71 73 74 75 77 77 79 79 80 81 82 83 83 84

Chapter 6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9

2010-12-20

PUBLIC

5/210

6.10 6.11 6.12 6.13 6.14 6.15 6.16 6.17 6.18 6.18.1 6.18.2 6.18.3 6.19 6.19.1 6.19.2 6.19.2.1 6.19.2.2 6.19.2.3 6.19.2.4 6.19.2.5 6.19.2.6 6.20 6.21 6.22 6.22.1 6.22.2 6.23 6.24 6.25 6.25.1 6.25.2 6.25.3 6.25.4

Configuring Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . . . . 84 Performing Post-Installation Steps for the Java Application Server . . . . . . . . . 85 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Performing a Full System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Setting Environment Variable CPIC_MAX_CONV . . . . . . . . . . . . . . . . . . . . . 91 Configuring the Connection to a Central System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Updating Component Repository Content in the System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Activating Internet Pricing and Configurator . . . . . . . . . . . . . . . . . . . . . . . . . 92 Checking the Availability of Back-End Systems for SAP CRM Java Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Creating a Back-End User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Checking the Connection to the ABAP System . . . . . . . . . . . . . . . . . . . . . . . . 94 Configuring and Checking the TREX Service . . . . . . . . . . . . . . . . . . . . . . . . . 95 Post-Installation Steps for the Business Packages for SAP CRM . . . . . . . . . . . . 96 Creating Roles for the SAP CRM Business Packages . . . . . . . . . . . . . . . . . . . . . 96 Installation of the Info Center for the SAP CRM Business Package . . . . . . . . . 96 Importing the SAP CRM Info Center Configurations and Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Activating Manual Ordering of Folders for the sapcrm Repository . . . . . . . . . 98 Creating Indexes and Taxonomies for the sapcrmnews Repository . . . . . . . . . 98 Creating the Index for the sapcrm Repository . . . . . . . . . . . . . . . . . . . . . . . . 100 Configuring the Personal Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Increasing the Number of JCo Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Configuring the Application Sharing Server . . . . . . . . . . . . . . . . . . . . . . . . . 101 Installing or Upgrading Database Studio for SAP MaxDB . . . . . . . . . . . . . . . . 101 Secure Sockets Layer Protocol for Database Server Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Installing the SAP Cryptographic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Generating the Personal Security Environment . . . . . . . . . . . . . . . . . . . . . . . 105 Updating the Database Software to the Current Release . . . . . . . . . . . . . . . . 107 Running the Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Using Extended Configuration Management (XCM) . . . . . . . . . . . . . . . . . . . 108 Starting XCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Changing the Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Printable Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

6/210

PUBLIC

2010-12-20

6.25.5 6.25.6 6.25.7 6.25.8 6.25.9 6.26 6.27 6.28

Multiple Application Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading and Downloading XCM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . Indication of Obsolete XCM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IPC Switch for XCM Configuration of SAP E-Commerce . . . . . . . . . . . . . . . . Post-Installation Steps for the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . Post-Installation Steps for the Host Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing Configuration Documentation in SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a Domain Installation Without Being a Domain Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . . Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing an External ABAP System as Source for User Data . . . . . . . . . . . . . Dialog Instance Installation for an Upgraded System only: Updating Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Additional Usage Types or Software Units in an Existing SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Additional Usage Types Step By Step . . . . . . . . . . . . . . . . . . . . . . . Software Component Archives of SAP NetWeaver 7.0 EHP2 Usage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Component Archives of SAP CRM 7.0 EHP1 Usage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Windows Server 2008 Firewall . . . . . . . . . . . . . . . . . . . . . . . . Usage Type-Specific Initial Technical Configuration . . . . . . . . . . . . . . . . . . . Initial Technical Configuration for SAP NetWeaver Application Server Java (AS Java) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Technical Configuration for Adobe Document Services . . . . . . . . . . . Initial Technical Configuration for Composite Application Framework Core (CAF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Technical Configuration for the System Landscape Directory (SLD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111 114 115 116 116 117 117 118 119 119 123 126 127 131 134 135 135 142 143 143 145 146 147 148 148 149 150

Chapter 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.7.1 7.7.2 7.7.3 7.8 7.9 7.10 7.11 7.11.1 7.11.1.1 7.11.1.2 7.11.1.3

2010-12-20

PUBLIC

7/210

7.11.2 7.11.3 7.11.4 7.11.4.1 7.11.4.2 7.11.4.3 7.12 7.13 7.14 7.14.1 7.14.2 7.14.3 7.14.3.1 7.14.3.2 7.14.3.3 7.14.3.4 7.15 Chapter 8 8.1 8.2 8.2.1 8.2.1.1 8.2.1.2 8.2.2 8.2.3 8.2.4 8.2.5 8.3 8.3.1 8.3.2 8.3.3 8.4 8.4.1 8.4.2 8.4.3

Initial Technical Configuration for Development Infrastructure (DI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Technical Configuration for the Portal (Usage Types EPC and EP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Technical Configuration for BI Java . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring BI Java Information Broadcasting . . . . . . . . . . . . . . . . . . . . . . . . Process Chains: Transporting Texts for the Alert Category . . . . . . . . . . . . . . Renaming initialPermissionsBI.xml.template . . . . . . . . . . . . . . . . . . . . . . . . . SAP System Security on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic Creation of Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting for Portal Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting for the Business Package for SAP CRM . . . . . . . . . . . . . . . . Activating BI Templates Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting when Importing PAR Files . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting in SSO with SAP Logon Tickets . . . . . . . . . . . . . . . . . . . . . . Dragging the Central Search onto the Portal Desktop . . . . . . . . . . . . . . . . . . Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . High Availability with Microsoft Cluster Service . . . . . . . . . . . . . . . . . . Installation Checklist for a High-Availability System . . . . . . . . . . . . . . . . . . . Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Configuration in MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP System Components in an MSCS Configuration . . . . . . . . . . . . . . . . . . Enqueue Replication Server in an MSCS Configuration . . . . . . . . . . . . . . . . . Distribution of SAP System Components to Disks for MSCS . . . . . . . . . . . . . Directories in an MSCS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Addresses in an MSCS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining and Determining IP Addresses for MSCS . . . . . . . . . . . . . . . . . . . . Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assigning Drive Letters for MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Host Names to IP Addresses for MSCS . . . . . . . . . . . . . . . . . . . . . . . Checking the Mapping of Host Names for MSCS . . . . . . . . . . . . . . . . . . . . . . Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the First MSCS Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Database on the First Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Database on the Additional Node . . . . . . . . . . . . . . . . . . . . .

150 152 153 153 154 154 154 157 158 159 159 161 161 162 162 165 165 169 171 172 172 173 175 176 180 181 184 186 186 187 188 189 189 190 190

8/210

PUBLIC

2010-12-20

8.4.4 8.4.5 8.4.6 8.4.7 8.5 8.5.1 8.5.1.1 8.5.1.2 8.6 8.6.1 8.6.2 8.6.3 Chapter A A.1

Installing the Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Additional MSCS Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Central Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Checks for Enqueue Replication Server . . . . . . . . . . . . . . . . Checking the Status of the Enqueue Replication Server with ENSMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring the Lock Table During Failover with ENQT . . . . . . . . . . . . . . . . Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving MSCS Groups or Services and Applications . . . . . . . . . . . . . . . . . . . . Rebooting During the Installation or Conversion for MSCS . . . . . . . . . . . . . Starting and Stopping the SAP System in an MSCS Configuration . . . . . . . . .

191 191 193 193 194 195 195 196 197 198 199 199

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

2010-12-20

PUBLIC

9/210

This page is left blank for documents that are printed on both sides.

1

Introduction

1 Introduction

This document explains how to install SAP CRM 7.0 including SAP enhancement package 1 Java. SAP CRM 7.0 including SAP enhancement package 1 is based on the technology of SAP NetWeaver 7.0 including enhancement package 2. For more information about the technology provided by SAP CRM and SAP NetWeaver, see http://service.sap.com/crm and http://service.sap.com/netweaver. Make sure you read the corresponding Master Guide before you start with this installation guide. The Master Guide is available as follows: http://service.sap.com/crm-inst SAP CRM You can install SAP CRM 7.0 including SAP enhancement package 1 with the following software units in a single installation run of SAPinst: SAP CRM Java Components (JCRM) SAP CRM Business Packages (BP-CRM) SAP CRM Business Package Foundation (BP-CRM-FND )NOTE

You also install SAP NetWeaver Application Server Java (AS Java) with the Java software units. In addition to the SAP CRM software units, you can install the following SAP NetWeaver usage types with SAPinst: SAP NetWeaver Development Infrastructure (DI) SAP NetWeaver EP Core (EPC) SAP NetWeaver Enterprise Portal (EP) SAP NetWeaver Business Intelligence Java Components (BI Java)NOTE

This documentation describes how to install BI Java with a standalone Java system. We recommend that you install BI Java with a standalone Java system and that you configure the connection with BI ABAP on a standalone ABAP system after the installation. The software components of BI ABAP are contained in usage type AS ABAP. If you want to install BI Java with an SAP NetWeaver ABAP+Java system, proceed as described in SAP Note 1181025. For more information about the usage types of SAP NetWeaver and their interdependencies, see the document Master Guide SAP NetWeaver 7.0 at http://service.sap.com/instguidesNW70.Constraints

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

2010-12-20

PUBLIC

11/210

1 1.1

Introduction New Features

Your operating system platform must be 64-bit.Naming Conventions

SAP system refers to SAP CRM 7.0 including SAP enhancement package 1. Java system refers to SAP CRM 7.0 including SAP enhancement package 1 Java. diagnostics refers to diagnostics in SAP Solution Manager. diagnostics agent refers to the agent of diagnostics in SAP Solution Manager.

Windows Operating System

In this document, Windows Server 2008 (R2) with (R2) written in parentheses means that the information applies to both Windows Server 2008 and Windows Server 2008 R2.Profiling for High AvailabilityOnly valid for: HA (MSCS) |

The profile bars with the wording Only valid for: HA (MSCS) for example, as in this section refer to content that is only valid if you are installing a high-availability (HA) system with Windows Server Failover Clustering. The Windows cluster feature was previously called Microsoft Cluster Service (MSCS). For practical reasons we are continuing to use the abbreviation MSCS in this guide.End of: HA (MSCS) |

1.1 New FeaturesThe table below provides an overview of the new features related to the installation. Make sure that you also read the release notes at http://service.sap.com/releasenotes.Area Description

SAPinst

High Availability

Running SAPinst with accessibility mode: Keyboard access: This feature is generally available for all operating systems. High-color contrast: This feature is derived from the Windows display properties. For more information, see Running SAPinst in Accessibility Mode [page 73]. Custom font setting: This feature is derived from the Windows display properties. For more information, see Running SAPinst in Accessibility Mode [page 73]. New installation options for a high-availability system in a Microsoft Cluster SAP adapted the installation procedure for a high-availability system on Windows to make it easier and less error-prone for customers: First Cluster Node

12/210

PUBLIC

2010-12-20

1 1.2 Area

Introduction SAP Notes for the Installation Description

New software unit

This installation option now includes the previously separate options Central Services Instance for ABAP (ASCS), Central Services Instance (SCS), Enqueue Replication Server (ERS), and First MSCS Node. It performs the following steps: Installs the central services instance (SCS) Installs the enqueue replication server instance (ERS) for the SCS instances Installs the host agent Creates the SAP cluster group on the first cluster node and adds the SCS instance to the SAP cluster group Additional Cluster Node This installation option includes the previous options Enqueue Replication Server, and Additional MSCS Node. It performs the followings steps: Configures the additional cluster node to run the SAP cluster group Installs the enqueue replication server instance (ERS) for the SCS instance on a local drive Installs the host agent on a local drive As of Windows Server 2008 (R2), the Windows cluster feature is called Failover Clustering. For practical reasons we are continuing to use the general abbreviation MSCS in this guide. The installation of the new software unit SAP CRM Business Package Foundation (BP-CRM-FND) is available.

1.2 SAP Notes for the InstallationYou must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find at http:// service.sap.com/notes.SAP Notes for the Installation SAP Note Number Title Description

1313850 1387319

Release Restrictions for SAP EHP 2 for SAP NetWeaver 7.0 SAP NetWeaver 7.02/Business Suite 7i2010: Windows

1354248

820824

Customer information on restrictions in the production use of certain functions. Windows-specific information about the SAP system installation and corrections to this documentation. SAP NetWeaver 7.0 EHP2/Business Platform-specific information about the SAP Suite on Windows: SAP MaxDB system installation (ABAP and Java) and corrections to this documentation FAQ: SAP MaxDB Frequently asked questions (FAQ) on SAP MaxDB

2010-12-20

PUBLIC

13/210

1 1.3

Introduction How to Use This Guide Title Description

SAP Note Number

1339460 855498 73606 1067221

1349080

925741

Inst. NetWeaver 7.0 EHP2 Problems discovered after the publication of the Diagnostics Agent installation installation guide or post-installation steps Installation Prerequisite Checker SAP Software on UNIX, Windows, and IBM i: Checking OS Dependencies Supported Languages and Code Information on possible languages and language Pages combinations in SAP systems Central Note for Heterogeneous This SAP Note and its related SAP Notes describe Installation the released operating system and database combinations for heterogeneous SAP systems landscapes. NW 7.02/BS 7i2010: Inst.Add.Java Supplementary information for section Installation Usage Types/Software Units of Additional Software Units or Usage Types in an Existing SAP System [page 135] Adobe Document Services with To use ADS in SAP landscapes on nonsupported Nonsupported Platforms platforms, you have to install an additional standalone SAP system with AS Java on a platform supported by ADS.

1.3 How to Use This Guide1. You decide on the installation option that you want to install. The following installation options are described in this installation guide: Central system Distributed system Only valid for: HA (MSCS) |

High-availability systemEnd of: HA (MSCS) |

2.

Additional software units or usage types to an existing SAP system Dialog instances Host Agent as a separate installation For more information, see Installation Options Covered by This Guide [page 17]. You follow the list of steps at the beginning of each installation phase: Planning [page 23] Preparation [page 51] Installation [page 63] Post-Installation [page 77] High Availability with Microsoft Cluster Service (if relevant) [page 169]

14/210

PUBLIC

2010-12-20

1 1.3

Introduction How to Use This Guide NOTE

This applies to all installation options except the Host Agent as a Separate Installation [page 22] and the Installation of Additional Usage Types or Software Units in an Existing SAP System [page 21]. These installation options each have their own section in Additional Information [page 119]. In Additional Information [page 119] you can find special installation options and more information about how to perform certain steps described in the main part of the guide.

2010-12-20

PUBLIC

15/210

This page is left blank for documents that are printed on both sides.

2 2.1

Installation Options Covered by this Guide Central System

2 Installation Options Covered by this Guide

This section shows the installation options covered by this guide. You have to decide what exactly you want to install because the steps you have to perform vary according to the installation option you choose. Central system [page 17] Distributed system [page 18] Only valid for: HA (MSCS) |

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

You can install dialog instances [page 19] to an existing system. You can install additional usage types in an existing SAP system [page 21]. You can install a host agent [page 22] separately.

2.1 Central SystemYou can install a central system on a single host. These are the following instances: Central services instance for Java (SCS instance) Database instance (DB instance) Central instance Optionally you can install one or more dialog instances. For more information, see Dialog Instance [page 19]. The following figure shows an example of SAP instances in a central system.

2010-12-20

PUBLIC

17/210

2 2.2

Installation Options Covered by this Guide Distributed System

Figure 1:

Central Java System

Optionally you can install one or more dialog instances. For more information, see Dialog Instance [page 19].

2.2 Distributed SystemIn a distributed system, every instance can run on a separate host. These are the following instances: Central services instance for Java (SCS instance) Database instance (DB instance) Central instance Optionally you can install one or more dialog instances. For more information, see Installation of a Dialog Instance [page 19].

18/210

PUBLIC

2010-12-20

2 2.3

Installation Options Covered by this Guide High Availability System

Figure 2:

Distributed Java System

Only valid for: HA (MSCS) |

2.3 High Availability SystemFor more information about the system components you have to install and how to distribute them on the specific hosts, see System Configuration in MSCS [page 172].End of: HA (MSCS) |

2.4 Dialog InstanceYou can install one or more dialog instances for an existing SAP system. Dialog instances are optional and can be installed on separate hosts. You can have one or more dialog instances. A dialog instance can run on: The host of any instance of the existing SAP system On a dedicated hostNOTE

If you install a dialog instance in an existing non-Unicode system (that has been upgraded to the current release), the dialog instance is automatically installed as a non-Unicode instance. SAPinst determines if a non-Unicode system exists and chooses the correct executables for the system type.

2010-12-20

PUBLIC

19/210

2 2.4

Installation Options Covered by this Guide Dialog Instance NOTE

We do not recommend installing dialog instances on the SAP global host.NOTE

If you want to install a dialog instance on an existing SAP system, you must perform a domain installation. You must also make sure that your existing SAP system was installed as a domain installation. For more information, see Domain or Local Installation [page 46].Dialog Instance for a Central System

The following figure shows dialog instances that are running on dedicated hosts.

Figure 3:

Dialog Instance for a Central System

For more information, see Central System [page 17].Dialog Instance for a Distributed System

The following figure shows dialog instances that are running on dedicated hosts.

20/210

PUBLIC

2010-12-20

2 2.5

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

Figure 4:

Dialog Instance for a Distributed System

For more information, see Distributed System [page 18].Only valid for: HA (MSCS) |

Dialog Instance for a High-Availability System

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

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

2010-12-20

PUBLIC

21/210

2 2.6

Installation Options Covered by this Guide Host Agent as a Separate Installation

2.6 Host Agent as a Separate InstallationUsing the host agent you can centrally monitor any host with the Alert Monitor or the SAP NetWeaver Administrator or the Adaptive Computing Controller (ACC). In addition, the host agent is used by the ACC for starting, stopping, and relocating SAP instances and databases. The host agent is automatically installed during the installation of all new SAP system instances based on SAP NetWeaver 7.0 including Enhancement Package 2 or higher. You only need to install a host agent separately in the following cases: You want to manage a host that does not have an SAP instance or component. You have upgraded your SAP system to SAP NetWeaver 7.0 including Enhancement Package 2 or higher. The section Installing the Host Agent Separately [page 143] describes how to perform the installation.

22/210

PUBLIC

2010-12-20

3 3.1

Planning Planning Checklist

3 Planning

3.1 Planning ChecklistThis section includes the planning steps that you have to perform for the following installation options: Central, distributed, or high-availability system Dialog instance Detailed information about the steps is available in the relevant chapter.Prerequisites

1.

2.

You have planned your SAP system landscape according to the Master Guide at http:// service.sap.com/crm-inst and the Technical Infrastructure Guide at https:// cw.sdn.sap.com/cw/community/docupedia/tig. You have decided on your installation option [page 17].

Central, Distributed, or High-Availability System NOTE

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. 1. 2. 3. 4. 5. 6. 7. 8. You check the hardware and software requirements [page 24] on each host. You plan how to set up user and access management [page 35]. You identify basic SAP system installation parameters [page 36]. You decide whether you want to perform a domain or local installation [page 46]. For the database installation, you decide how to distribute your system components [page 47]. You decide on the transport host to use [page 48]. You decide if you want to use Internet Pricing and Configurator [page 49].Only valid for: HA (MSCS) |

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

9.

You can continue with Preparation [page 51].

Dialog Instance

1. 2.

You check the hardware and software requirements [page 24] for the installation host on which you want to install one or more dialog instances. You identify basic SAP system installation parameters [page 36].

2010-12-20

PUBLIC

23/210

3 3.2

Planning Hardware and Software Requirements

3.

You can now continue with Preparation [page 51].

3.2 Hardware and Software RequirementsYou check that your hosts meet the hardware and software requirements for your operating system and the SAP instances.CAUTION

If your hosts do not fully meet the requirements, you might experience problems when working with the SAP system.Prerequisites

Make sure that the host name meets the requirements listed in SAP Note 611361.Process Flow

1. 2.

Check the Product Availability Matrix at http://service.sap.com/pam for supported operating system releases. Check the hardware and software requirements using: The Prerequisite Checker in one of two modes: Standalone mode (optional) before the installation process For more information, see Running the Prerequisite Checker Standalone [page 25]. Integrated in SAPinst (mandatory) during the installation process For more information, see Running SAPinst [page 64].NOTE

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

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

3.

Dialog instance [page 33] Host agent as a separate installation [page 33] If you want to install a production system, the values provided by the Prerequisite Checker and the hardware and software requirements checklists are not sufficient. In addition, do the following: You use the Quick Sizer tool available at http://service.sap.com/sizing. For more information about the Quick Sizer and available sizing guides, see the Master Guide SAP NetWeaver 7.0 at http://service.sap.com/installnw70 Planning .

24/210

PUBLIC

2010-12-20

3 3.2

Planning Hardware and Software Requirements NOTE

If you want to install usage type Development Infrastructure (DI), also check SAP Note 737368 for system requirements and sizing. You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing depending on: The set of applications to be deployed How intensively the applications are to be used The number of users

3.2.1 Running the Prerequisite Checker in Standalone Mode (Optional)Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check the hardware and software requirements for your operating system (OS) and the SAP instances.RECOMMENDATION

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

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

You have prepared the installation master DVD on the required installation host [page 60].Procedure

1. 2. 3.

You start SAPinst [page 64]. On the Welcome screen, choose Software Life-Cycle Options Additional Preparations Prerequisites Check . Follow the instructions in the SAPinst dialogs and enter the required parameters.NOTE

For more information about each parameter, position the cursor on the parameter field and choose F1 in SAPinst. When you have finished, the Parameter Summary screen appears summarizing all parameters you have entered and want to have checked. If you want to make a change, select the relevant parameters and choose Revise. To start the prerequisites check, choose Next.

4.

Result

The Prerequisite Checker Results screen displays the results found. If required, you can also check the results in file prerequisite_checker_results.html, which you can find in the installation directory.

2010-12-20

PUBLIC

25/210

3 3.2


3.2.2 Requirements for a Central SystemIf you want to install a central system, where all instances reside on one host, this host must meet the following requirements:NOTE

The listed values are sufficient for development systems or quality assurance systems but not for production systems. For up-to-date information on the released and supported operating system and database versions for your SAP product and database, see the Product Availability Matrix (PAM) at http://service.sap.com/pam .Hardware Requirements for a Central System Hardware Requirement Requirement How to Check

Minimum disk space

Minimum RAM

Database Software: 1 GB SAP system files (not including paging file): 5 GB (x64) 8 GB (IA64) For the SAP data: 6 GB Distribute the space for the SAP data across at least three physically separate disks Up to 2 GB for each usage type or software unit you want to install. 4.3 GB of temporary disk space for every required installation medium that you have to copy to a local hard disk 4 GB

To check disk space: 1. Windows Server 2003: Choose Start All Programs Administrative Tools Computer Management Disk Management . 2. Windows Server 2008 (R2): Choose Start All Programs Administrative Tools Storage Computer Management Disk Management . 3. Right-click the drive and choose Properties.

To check RAM: Choose Start Control Panel System .NOTE

Paging file size

For more information, see SAP Note 1518419.

Windows Server 2008 R2: If System is not visible, change View by: from Category into Large icons. To check paging file size: 1. Choose Start Control Panel System .NOTE

2.

Windows Server 2008 R2: If System is not visible, change View by: from Category into Large icons. Windows Server 2003:

26/210

PUBLIC

2010-12-20

3 3.2

Planning Hardware and Software Requirements Requirement How to Check

Hardware Requirement

3. 4. 5.

Choose Advanced. Windows Server 2008 (R2): Choose Advanced system settings. In section Performance, select Settings... Advanced . If required, in section Virtual memory, choose Change.NOTE

Do not select Automatically managed paging file size for all drives. Suitable backup system Software Requirements for a Central System Software Requirement Requirement How to Check

Windows English 64-bit version of one of the following To check your Windows version: operating system 1. Choose Start All Programs Windows Server Editions: Accessories Command Windows Server 2003 Prompt Windows Server 2003 Standard Edition Windows Server 2003 Enterprise Edition 2. Enter the command winver Windows Server 2003 Datacenter Edition Windows Server 2008 (R2) Windows Server 2008 (R2) Standard Edition Windows Server 2008 (R2) Enterprise Edition Windows Server 2008 (R2) Datacenter Edition Windows Server 2008 (R2) for ItaniumBased Systems EditionNOTE

For up-to-date information on the released and supported operating system versions for your SAP product and database, see the Product Availability Matrix (PAM) at http:// service.sap.com/pam. For any version of Windows Server, you need the latest supported service pack Windows Server 2003: A suitable Windows Resource Kit is strongly recommended. Windows Server 2003: Updated CPU drivers For more information, see SAP Note 1036194.

2010-12-20

PUBLIC

27/210

3 3.2


3.2.3 Requirements for a Distributed SystemThis section provides information about the hardware and software requirements in a distributed system, where the SAP instances can reside on different hosts. The tables show the requirements for the: Central services instance Database instance Central instance Dialog instance (optional)NOTE

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. For up-to-date information on the released and supported operating system versions for your SAP product and database, see the Product Availability Matrix (PAM) at http:// service.sap.com/pam.Hardware Requirements for a Distributed System Hardware Requirement Requirement How to Check

Minimum disk space

Database software: 1 GB Central services instance (SCS) (not including paging file): 5 GB (x64) 8 GB (IA64) For the SAP data: 6 GB Distribute the space for the SAP data across at least three physically separate disks 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. In addition you require 1.5 GB for the diagnostics agent 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)

To check disk space: 1. Windows Server 2003: Choose Start All Programs Administrative Tools Computer Management Disk Management . 2. Windows Server 2008 (R2): Choose Start All Programs Administrative Tools Storage Computer Management Disk Management . 3. Right-click the drive and choose Properties.

28/210

PUBLIC

2010-12-20

3 3.2

Planning Hardware and Software Requirements Requirement How to Check


Minimum RAM

In addition you require 1.5 GB for the diagnostics agent Temporary disk space for every required installation medium that you have to copy to a local hard disk: 4.3 GB 4 GB To check RAM: Choose Start Control Panel System .NOTE

Paging file size



2. 3. 4. 5.

Windows Server 2008 R2: If System is not visible, change View by: from Category into Large icons. Windows Server 2003: Choose Advanced. Windows Server 2008 (R2): Choose Advanced system settings. In section Performance, select Settings... Advanced . If required, in section Virtual memory, choose Change.NOTE

Do not select Automatically managed paging file size for all drives. Suitable backup systemSoftware Requirements for a Distributed System Software Requirement Requirement How to Check

Windows operating system

To check your Windows version: English 64-bit version of one of the following 1. Choose Start All Programs Windows Server Editions: Accessories Command Windows Server 2003 Prompt Windows Server 2003 Standard Edition Windows Server 2003 Enterprise Edition 2. Enter the command winver Windows Server 2003 Datacenter Edition Windows Server 2008 (R2) Windows Server 2008 (R2) Standard Edition

2010-12-20

PUBLIC

29/210

3 3.2


Software Requirement

Requirement

How to Check

Windows Server 2008 (R2) Enterprise Edition Windows Server 2008 (R2) Datacenter Edition Windows Server 2008 (R2) for ItaniumBased Systems Edition For any version of Windows Server, you need the latest supported service pack Windows Server 2003: A suitable Windows Resource Kit is strongly recommended. Windows Server 2003: Updated CPU drivers For more information, see SAP Note 1036194.Only valid for: HA (MSCS) |

3.2.4 Requirements for a High-Availability SystemGeneral Requirements

Windows Server 2003 only: You must check that your cluster hardware is certified. AddOn Technology Center for SAP (Add On TCS) certifies hardware platforms for SAP on Microsoft Windows. The cluster must be included in the Microsoft list of certified clusters and its components. You can access the lists as follows: http://www.microsoft.com/whdc/hcl/default.mspx http://www.saponwin.com Windows Server 2008 (R2) only: 1. Check that your cluster hardware is certified for Windows Server 2008 (R2) and has the Windows Server 2008 (R2) logo. 2. You must validate your failover cluster configuration by running the Validate a Configuration Wizard, which is included in the Failover Cluster Management snap-in. The Failover Cluster Validation Report must not show any warnings and errors. The MSCS nodes of the cluster must be connected by a private and public network: The public network enables communication from the MSCS nodes of the cluster to other resources in the local area network (LAN). The private network enables internal communication between the MSCS nodes. In particular, it enables the Cluster Service running on all MSCS nodes to regularly exchange messages on the state of the MSCS nodes so that the failure of resources is quickly detected. Each of the MSCS nodes in the cluster must have its own local disks and have access to shared disks that can be reached by the MSCS nodes via a shared bus.

30/210

PUBLIC

2010-12-20

3 3.2


All software except the Windows operating system, the SAP MaxDB system database, 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 six shared disks. For more information about the distribution of components to local and shared disk, see Distribution of SAP System Components to Disks for MSCS [page 176]. All disk controllers must be able to support hardware-based RAID.CAUTION

You cannot use a host with a domain controller as an MSCS cluster node.Hardware and Software Requirements

The following tables show the hardware and software requirements for the: Central services instance (SCS) Database instance Enqueue Replication Server instance (ERS) Central instance Dialog instance Diagnostics agentHardware Requirements for a High-Availability System Hardware Requirement Requirement How to Check

Minimum disk space

Database Software: 1 GB Central services instance (SCS) (not including paging file): 5 GB (x64) 8 GB (IA64) For the SAP data: 6 GB Distribute the space for the SAP data across at least three physically separate disks 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) In addition you require 4 GB (x64), or 8 GB (IA64) per additional platform. In addition you require 1.5 GB for the diagnostics agent

To check disk space: 1. Windows Server 2003: Choose Start All Programs Administrative Tools Computer Management Disk Management . 2. Windows Server 2008 (R2): Choose Start All Programs Administrative Tools Storage Computer Management Disk Management . 3. Right-click the disk and choose Properties.

2010-12-20

PUBLIC

31/210

3 3.2



Requirement

How to Check

Minimum RAM

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) In addition you require 1.5 GB for the diagnostics agent Temporary disk space for every required installation medium that you have to copy to a local hard disk: 4.3 GB 4 GB To check RAM: Choose Start Control Panel System .NOTE

Paging file size

For more information, see SAP Note 1518419


2. 3. 4. 5.


Do not select Automatically managed paging file size for all drives. You must adjust the size of the paging file on all MSCS nodes. Suitable backup system

32/210

PUBLIC

2010-12-20

3 3.2


Software Requirements for a High Availability System Software Requirement Requirement How to Check

Windows operating system

To check your Windows version: English 64-bit version of one of the 1. Choose Start All Programs following Windows Server Editions: Accessories Command Prompt Windows Server 2003 2. Enter the command winver Windows Server 2003 Enterprise Edition NOTE Windows Server 2003 Datacenter Edition Windows Server 2003: You must set up the MSCS Windows Server 2008 (R2) Cluster Service as described in Windows Server 2008 (R2) the Microsoft documentation. Enterprise Edition During this setup you are Windows Server 2008 (R2) asked for a Windows Domain Datacenter Edition Account to run the Cluster Windows Server 2008 (R2) for Service. We strongly Itanium-Based Systems Edition recommend creating an For any version of Windows Server, you need account different from the the latest supported service pack adm user, for example Windows Server 2003: A suitable Windows ClusterServiceuser=sapprdc Resource Kit is strongly recommended ladm, where Windows Server 2003: Updated CPU drivers Clustername=sapprdcl. For more information, see SAP Note 1036194. Windows Server 2008 (R2): You must add the operating system feature Failover Clustering on all MSCS nodes.

End of: HA (MSCS) |

3.2.5 Requirements for the Dialog InstanceFor more information about the hardware and software requirements for the dialog instance, see one of the following sections: Requirements for a Distributed System [page 28] Only valid for: HA (MSCS) |

Requirements for a High-Availability System [page 30]End of: HA (MSCS) |

3.2.6 Requirements for the Host Agent as a Separate InstallationIf you want to install the host agent separately, the installation host has to meet the following hardware and software requirements:

2010-12-20

PUBLIC

33/210

3 3.2

Planning Hardware and Software Requirements CAUTION

For up-to-date information on the released and supported operating system versions for your SAP product and database, see the Product Availability Matrix (PAM) at http:// service.sap.com/pam.Hardware Requirements for the Host Agent Hardware Requirement Requirement How to Check

Minimum disk space:

Minimum RAM:

To check disk space: Host agent: 80 MB 1. Windows Server 2003: Temporary disk space for every Choose Start All Programs required installation medium that you Administrative Tools Computer have to copy to a local hard disk: Management Disk Management . 4.3 GB 2. Windows Server 2008 (R2): Choose Start All Programs Administrative Tools Storage Computer Management Disk Management . 3. Right-click the disk and choose Properties. 40 MB To check RAM: Choose Start Control Panel System .NOTE

Paging file size:



2. 3. 4. 5.


Do not select Automatically managed paging file size for all drives. Suitable backup system

34/210

PUBLIC

2010-12-20

3 3.3

Planning Planning User and Access Management

Software Requirements for the Host Agent Software Requirement Requirement How to Check

Windows operating system:

Database software:

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

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

3.3 Planning User and Access ManagementYou have to plan how you want to configure user and access management for your SAP system to be installed. Before you add a newly installed SAP system to your system landscape, you must decide which kind of user management you want to use: Use the database of AS Java. Use an external ABAP system as the data source for user data. Use an LDAP directory as the data source for user data. You cannot configure the AS Java to access an LDAP directory and an AS ABAP as the data source simultaneously. The AS Java can also use its own database as the data source.ProcedureUsing the Database of AS Java

You install your SAP system as described in this installation guide. During the installation, you specify the Java database as data source for the User Management Engine (UME) (see Basic SAP System Installation Parameters [page 36]): During the installation, the SAP system is automatically configured to use the Java database as data source for the UME.

2010-12-20

PUBLIC

35/210

3 3.4

Planning Basic SAP System Installation Parameters

After the installation has finished, you can still change the user management configuration. For more information, see Configuring User Management [page 82].Using an External SAP ABAP System as Source for User Data.

1. 2.

3.

You prepare the external SAP ABAP system as described in Preparing an External ABAP System as Source for User Data [page 131]. You install your SAP system as described in this installation guide. During the installation, you specify an external ABAP system as data source for the User Management Engine (UME) (see Basic SAP System Installation Parameters [page 36]). After the installation has finished, you cannot change this configuration of the UME any more. For more information, see Configuring User Management [page 82].

Using an LDAP directory as Source for User Data

1. 2.

You install your SAP system as described in this installation guide. Configure the user management of the newly installed SAP system to use and LDAP directory. For more information, see Configuring User Management [page 82].

More Information

For more information about configuring the user management of your SAP system to be installed, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 2) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management Identity Management for System Landscapes Integration of User Management in Your System Landscape

3.4 Basic SAP System Installation ParametersSAPinst prompts for input parameters during the Define Parameters phase of the installation. You can install your SAP system either in Typical or Custom mode: Typical If you choose Typical, you perform the installation with default settings. This means that you only have to respond to a small selection of prompts including at least the following, which are described in the corresponding tables below: SAP system ID and database ID SAP system profile directory only for systems with instances on separate hosts Master password Java Development Kit (JDK) only prompted if not already available on the installation host Java Cryptographic Extension (JCE) Unlimited Strength Jurisdiction Policy files archive only prompted if not already available on the installation host System Landscape Directory (SLD) destination

36/210

PUBLIC

2010-12-20

3 3.4

Planning Basic SAP System Installation Parameters

SAP Solution Manager Key If you want to change any of the default settings, you can do so on the Parameter Summary screen. Custom If you choose Custom, you are prompted for all parameters. At the end, you can still change any of these parameters on the Parameter Summary screen.RECOMMENDATION

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

You cannot change from Custom to Typical mode or from Typical to Custom mode on the Parameter Summary screen. The following tables list the basic system parameters that you need to specify before installing your SAP system: SAP System Parameters SAP System Database Parameters Diagnostics Agent Parameters For all other installation parameters, use the F1 help in the SAPinst screens.SAP System Parameters Parameters Description

SAP System ID

The SAP System ID identifies the whole SAP system.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. Do not use an existing when installing a new SAP system.EXAMPLE

If you have already installed an ABAP system and you want to install a new Java system on the same host, make sure that you enter a that is different from the of the existing ABAP system. Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs:

2010-12-20

PUBLIC

37/210

3 3.4

Planning Basic SAP System Installation Parameters DescriptionADD ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR

Parameters

SAP System Instance Numbers

If you want to install a dialog instance, make sure that no gateway instance with the same SAP system ID (SAPSID) exists in your SAP system landscape. Technical identifier for internal processes. It consists of a two-digit number from 00 to 97. The instance number must be unique on a host. That is, if more than one SAP instance is running on the same host, these instances must be assigned different numbers. If you do not enter a specific value, the instance number is set automatically to the next free and valid instance number that has not yet been assigned to the SAP system to be installed or to SAP systems that already exist on the installation host. To find out the instance numbers of SAP systems that already exist on the installation host, look for subdirectories ending with of local \usr\sap\ directories. The value is the number assigned to the instance. For more information, see SAP Directories [page 119].CAUTION

Do not use 43, and 89 for the instance number because: 43 is part of the port number for MSCS 89 is part of the port number for Windows Terminal Server Master Password Common password for all users created during the installation: Operating system users (for example adm, SAPService)CAUTION

If you did not create the operating system users manually before the installation, SAPinst creates them with the common master password. In this case, make sure that the master password meets the requirements of your operating system and of your database. Java users (for example Administrator) Database users Secure Store key phrase For more information, see table line Key Phrase for Secure Store Settings.NOTE

If a user already exists, you are prompted to confirm the password for this user. Password policy The master password: Must be 8 to 9 characters long Can contain the following characters: @, _, #, $, a-z, A-Z, 0-9 Must contain at least one letter in uppercase (A-Z) Must contain at least one letter in lowercase (a-z) Must contain at least one digit (0-9), but must not begin with a digit Must not contain \ (backslash) and " (double quote) Depending on the installation option, additional restrictions might apply (for example, the master password must not contain the name of a Java user created during the installation).

38/210

PUBLIC

2010-12-20

3 3.4

Planning Basic SAP System Installation Parameters Description CAUTION

Parameters

Message Server Port

The message server port number must be unique for the SAP system on all hosts. If there are several message port numbers on one host, all must be unique.

Port number of the SAP Message Server: If you do not specify a value, the default port number is used. The SCS instance profile contains the configuration for the Java message server. The Java message server port uses the parameter rdisp/msserv_internal with default value 39, where is the instance number of the SCS message server instance. For more information about the parameters used for message server ports, see SAP Note 821875. Java A valid JDK 1.4.2 is required for the Java application server. For more information about JDK Development versions supported by SAP and about how to install them, see Installing the Java Development Kit (JDK) Kit [page 58]. Java(TM) You have to download the JCE Unlimited Strength Jurisdiction Policy Files 1.4.2 archive for Cryptography the SAP system. Extension (JCE) For more information, see Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive [page Unlimited 58]. Strength Jurisdiction Policy Files Archive Key Phrase for This is a random word or phrase that is used to encrypt the secure store. Secure Store The Java EE engine uses this phrase to generate the key that is used to encrypt the data. Settings 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.NOTE

DNS Domain Name for SAP System

If you choose Typical mode, SAPinst sets the master password for the key phrase. In this case, make sure that you replace the master password with the required unique key phrase either in the Parameter Summary screen or after the installation has finished. If you want to use HTTP-based URL frameworks such as Web Dynpro applications, you have to specify the DNS domain name for the SAP system. The DNS Domain Name is used to calculate the Fully Qualified Domain Name (FQDN), which is configured in profile parameter SAPLOCALHOSTFULL. FQDN is the fully qualified domain name for an IP address. It consists of the host name and the domain name:.

The DNS Domain Name is needed to define the URLs for the ABAP and Java application servers. It is appended to the server name to calculate the FQDN. For more information, see SAP Note 654982.EXAMPLE

If your application server host is called kirk.wdf.sap.com, the DNS Domain Name is wdf.sap.com.

2010-12-20

PUBLIC

39/210

3 3.4

Planning Basic SAP System Installation Parameters Description

Parameters

Password of Operating System Users

The passwords of the operating system users must comply with the Windows password policy. SAPinst processes the passwords of operating system users as follows: If the operating system users do not exist, SAPinst creates the following users: adm This user is the SAP system administrator user and is a member of the local Administrators group. SAPService This user is the Windows account to run the SAP system and is not a member of the local Administrators group. sapadm The host agent user sapadm is used for central monitoring services. SAPinst creates this user by default as a local user without being a member of the local Administrators group. If required, you can change this user to become a domain user on the parameter summary screen. For more information, see Performing a Domain Installation Without Being a Domain Administrator [page 123]. For security reasons, however, SAP strongly recommends to create this user as a local user. 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 creates this user by default as a local user. If required, you can change this user to become a domain user on the parameter summary screen. For security reasons, however, SAP strongly recommends to create this user as a local user. 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.NOTE

This does not apply if the adm user already exists. SAPinst prompts you for the password even if the password of this user is the same as the master password.CAUTION

UME Configuration

Make sure that you have the required user authorization [page 55] for these accounts before you start the installation with SAPinst. You are prompted for how to configure the UME during the input phase of the installation. You can choose between the following options: Use Java database (default) If you choose this option, administrators can manage users and groups with the UME Web admin tool and SAP NetWeaver Administrator only. For LDAP, use this configuration for the installation and change the configuration to LDAP after the installation (see Configuring User Management to Use an LDAP Directory [page 82]). Use ABAP If you choose this option, administrators can manage users with the transaction SU01 on the external ABAP system, and, depending on the permissions of the communication user, also with the UME Web admin tool and SAP NetWeaver Administrator.

40/210

PUBLIC

2010-12-20

3 3.4


Parameters

Make sure that you have created the required users manually on the external ABAP system before you choose this option (see Preparing an External ABAP System as Source for User Data [page 131]).RECOMMENDATION

Select the Custom parameter mode. When you do this, you are prompted to select the appropriate option and to enter the required parameters. If you do not choose the Custom parameter mode, you have to change the required parameters on the Parameter Summary screen. For more information about supported UME data sources and change options, see SAP Note 718383. SAP Solution To install your SAP system, you need to generate an SAP Solution Manager key [page 57], which Manager key the installation requires to continue. For more information, see SAP Note 805390. You have already generated an SAP Solution Manager Key for the central instance, so you do not have to do this for the dialog instance. Using the Java Database: Java SAPinst sets the user name Administrator and the master password by default. Administrator This user has administrative permissions for user management. User and Password Java Guest User SAPinst sets the user name Guest and the master password by default. and Password This user is used for anonymous access. Using an External ABAP System Parameters for the ABAP Connection: Application This is the instance number on the application server of the central ABAP system to which Server Number you want to connect the Application Server Java. To find out the number on the host of the central instance, look under the SAP directory usr/sap//DVEBMGS. The value is the number assigned to the SAP system. Application This is the host name of the relevant application server instance. Server Host To find out the host name, enter hostname at the command prompt of the host running the central instance. Communication This is the name and password of the existing ABAP communication user. You must have User and created this user manually on the external ABAP system. Password SDM Password This user is used for the Software Deployment Manager (SDM). SAPinst sets the master password by default. Using an External ABAP System Parameters for the Application Server Java Connection: Administrator This is the name and password of the administrator user that you must have created on the User and external ABAP system. Password This user has administrative permissions for user management. Administrator The role SAP_J2EE_ADMIN must exist on the external ABAP system. Role Guest User and This is the name and password of the guest user that you must have created on the external Password ABAP system. This user is used for anonymous access. Guest Role The role SAP_J2EE_GUEST must exist on the external ABAP system.

2010-12-20

PUBLIC

41/210

3 3.4


Parameters

Communication This is the name and password of the existing ABAP communication user. You must have User and created this user manually on the external ABAP system. Password SDM Password This user is used for the Software Deployment Manager (SDM). SAPinst sets the master password by default. Integration SAPinst sets the user name PIREPUSER and the master password by default. Repository If required, you can choose another user name and password according to your requirements. Service User and NOTE Password If you want to choose another user name, make sure that this user name starts with PI. Integration SAPinst sets the user name PIDIRUSER and the master password by default. Directory If required, you can choose another user name and password according to your requirements. Service User and NOTE Password If you want to choose another user name, make sure that this user name starts with PI. Landscape SAPinst sets the user name PILDUSER and the master password by default. Directory If required, you can choose another user name and password according to your requirements. Service User and NOTE Password If you want to choose another user name, make sure that this user name starts with PI. Integration SAPinst sets the user name PIAPPLUSER and the master password by default. Server If required, you can choose another user name and password according to your requirements. Application User NOTE and Password If you want to choose another user name, make sure that this user name starts with PI. Runtime SAPinst sets the user name PIRWBUSER and the master password by default. Workbench If required, you can choose another user name and password according to your requirements. Service User and NOTE Password If you want to choose another user name, make sure that this user name starts with PI. Adapter SAPinst sets the user name PIAFUSER and the master password by default. Framework If required, you can choose another user name and password according to your requirements. Server Service NOTE User and If you want to choose another user name, make sure that this user name starts with Password PI. Integration SAPinst sets the user name PIISUSER and the master password by default. Server Service If required, you can choose another user name and password according to your requirements. User and NOTE Password If you want to choose another user name, make sure that this user name starts with PI.

42/210

PUBLIC

2010-12-20

3 3.4


Parameters

Management Server Service User and Password

SAPinst sets the user name PILSADMIN and the master password by default. If required, you can choose another user name and password according to your requirements.NOTE

Exchange Infrastructure Administrator and Password

If you want to choose another user name, make sure that this user name starts with PI. This user has extensive authorizations. SAPinst sets the user name PISUPER and the master password by default. If required, you can choose another user name and password according to your requirements.NOTE

Exchange Infrastructure Communicator and Password

If you want to choose another user name, make sure that this user name starts with PI. SAPinst sets the user name PI_JCD_RFC and the master password by default. If required, you can choose another user name and password according to your requirements.NOTE

If you want to choose another user name, make sure that this user name starts with PI. SLD Destination 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 Choose this option to register the SAP system you are installing in an existing SAP System Landscape Directory (SLD) by specifying the SLD connection parameters listed below in this table. No SLD destination Choose this option if you do not want to register the SAP system you are installing in an existing SAP System Landscape Directory (SLD). You then have to configure the SLD destination manually after the installation with SAPinst has finished. Configure a local SLD Choose this option if you want to have a local SLD on the SAP Java system that you are installing. Then the SAP system you are installing is the SLD server. For more information, see Initial Technical Configuration for the System Landscape Directory (SLD) [page 150]. Register in existing central SLD SLD HTTP Host The host name of the existing central SLD. SLD HTTP Port The HTTP port of the existing central SLD. The following naming convention applies: 500.EXAMPLE

SLD Data Supplier User and password

If the instance number of your Java system is 01, the SLD HTTP Port is 50100. The existing SLD Data Supplier user and password of the existing central SLD

2010-12-20

PUBLIC

43/210

3 3.4


Parameters

SLD ABAP API The existing SLD ABAP API user and password of the existing central SLD User and password Configure a local SLD SLD Data Specify the name of the SLD Data Supplier user to be created. This user is used to send the Supplier User self-registration data of your system to the SLD. and passwordRECOMMENDATION

Object Server Name

We recommend that you name this user SLDDSUSER The Object Server Name together with the CIM namespace identifies the absolute location of your System Landscape Directory. If you do not have a prefix reserved on SAP Market Place for Object Server Name, or if you just want to install a test or development system, enter the central instance host of your system. For more information about the Object Server Name parameter, see SAP Note 935245.

SAP System Database Parameters Parameters Description

Database ID

The identifies the database instance. SAPinst prompts you for the when you are installing the database instance. The can be the same as the .CAUTION

Choose your database ID carefully. Renaming is difficult and requires that you reinstall the SAP system. If you want to install a new database, make sure that your database ID: Is unique throughout your organization Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs:ADD ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR7 VAR

Database schema Database file systems

SAPDB

Drive for global programs Drive for global data Drive for instance-dependent software Drive for instance-dependent data Drives for SAP data and log volumes

Diagnostics Agent Parameters

The diagnostics agent is installed automatically with the SAP system.

44/210

PUBLIC

2010-12-20

3 3.4


Parameters

System ID of the Diagnostics Agent

SAPinst sets the system ID of the diagnostics agent, , to DAA by default. If DAA is already used, SAPinst assigns another default system ID. You can overwrite the default system ID as required.CAUTION

Choose the carefully. Renaming is difficult and requires you to reinstall the diagnostics agent. Make sure that the : Either does not yet exist on the local installation host or does already exist but was only used for a diagnostics agent installation Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs:ADD ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR

Instance Number of the Diagnostics Agent

Use SAP JVM

Technical identifier for internal processes for the diagnostics agent, consisting of a two-digit number from 00 to 97. Default is 97. If 97 is already used for an instance number, the diagnostics agent instance number is set automatically to the next free and valid instance number. The instance number is used to specify the name of the diagnostics agent instance directory that SAPinst automatically creates during the installation. The directory of the diagnostics agent instance is called SMDA. For more information, see SAP Directories [page 119]. The same restrictions apply as in Instance Number of the SAP System (see above). For the diagnostics agent, you can either use the vendor Java Development Kit (JDK) 1.4.2 that you installed for the SAP system (see Installing the Java Development Kit [page 58]) or the SAP Java Virtual Machine (SAP JVM). We recommend that you use the SAP JVM. You do not have to download SAP JVM separately, it is contained in the installation package. You can install the SAP JVM during the installation with SAPinst in one of the following ways (see also Running SAPinst [page 64]): If you choose Typical mode for the installation, SAPinst does not automatically prompt you during the Define Parameters phase if you want to use the SAP JVM for the diagnostics agent. Instead, SAPinst sets the vendor JDK by default. If you want to use the SAP JVM, you have to change this setting using the Parameter Summary Screen. If you choose Custom mode for the installation, SAPinst prompts you during the Define Parameters whether you want to use the vendor JDK or the SAP JVM for the diagnostics agent.

2010-12-20

PUBLIC

45/210

3 3.5

Planning Domain or Local Installation Description

Parameters

Java(TM) Cryptography Extension You have to download the JCE Unlimited Strength Jurisdiction (JCE) Unlimited Strength Jurisdiction Policy Files 1.4.2 archive for the SAP system (see table SAP System Policy Files Archive Parameters). If you do not intend to use the SAP JVM for the diagnostics agent (see Use SAP JVM), SAPinst installs the JCE Unlimited Strength Jurisdiction Policy Files 1.4.2 also for the diagnostics agent. If you intend to use the SAP JVM for the diagnostics agent (recommended), you also have to download the JCE Unlimited Strength Jurisdiction Policy Files 6 archive. For more information, see Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive [page 58].

3.5 Domain or Local InstallationBefore you install the SAP system, you have to decide whether you want to perform a domain or local installation, since this affects how the user account information is stored and accessed. For more information about the differences between a local and domain installation, go to Start Help and Support and search for What is the difference between a domain and a workgroup?.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. Only valid for: HA (MSCS) |

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

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

If your SAP system was installed as a local installation and you want to later change to a domain installation, you must perform a homogeneous system copy. For more information, see the documentation System Copy for SAP Systems based on SAP NetWeaver at: http://service.sap.com/instguides More Information

Required User Authorization for Running SAPinst [page 55]

46/210

PUBLIC

2010-12-20

3 3.6

Planning Distribution of Components to Disks

3.6 Distribution of Components to DisksWhen you install the SAP system, the installation tools prompt you to enter drive letters for the main components of the system. This lets you distribute components to disks in the system as required. How you do this significantly affects system throughput and data security, so you need to plan it carefully. The best distribution depends on your environment and must reflect 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 obtain an overview of the main components and their corresponding directories. On the basis of sample configurations and the recommendations provided in this documentation, you can then choose the best setup for your particular system. In most situations, SAP systems are installed on RAID arrays to guarantee data redundancy. Therefore, this documentation focuses on RAID subsystems and drives.Features

The following graphic shows how you can distribute the main directories created during the installation

CRM 7.0

Documents

Transcript of CRM 7.0