SAP Installation Guide for NW 7.0

Installation GuideSAP Systems Based on the Application Server ABAP+Java of SAP NetWeaver on Windows: IBM DB2 for Linux, UNIX, and WindowsUsing Software Provisioning Manager 1.0

Valid for SAP Systems Based On: SAP NetWeaver 7.0 Support Release 3 SAP NetWeaver 7.0 Including SAP Enhancement Package 1 SAP NetWeaver 7.0 Including SAP Enhancement Package 2 SAP NetWeaver 7.0 Including SAP Enhancement Package 3 (Target System Installation for

System Copy Only)

Target Audience System Administrators Technology Consultants

CUSTOMERDocument version: 1.2 2013-07-15

About this Installation Guide

SAP System InstallationSAP 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

SAP Installation ToolYou 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 DatabasesFor 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/198 CUSTOMER 2013-07-15

Document History

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

The following table provides an overview on the most important document changes:Version Date Description1.0 2012-12-17 First version for software provisioning manager 1.01.1 2013-04-02 Updated version1.2 2013-07-15 Updated version

2013-07-15 CUSTOMER 3/198

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2 Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . 152.1 Central System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2 Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3 High Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.4 Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.5 SAP Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2.1 Running the Prerequisites Check in Standalone Mode (Optional) . . . . . . . . . . 233.2.2 Requirements for the SAP System Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.3 Planning User and Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.4 Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.5 Domain or Local Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.6 Setup of Database Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.6.1 Base Directories for the Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.6.2 Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.6.3 Directory Structure of the New DB2 Client Connectivity . . . . . . . . . . . . . . . . 453.6.4 DB2 Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.6.5 Optimization of Database Size on Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.6.6 Data Safety and Performance Considerations for Production

Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.7 SAP Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4/198 CUSTOMER 2013-07-15

4.2 Disabling the Windows Server Firewall on Windows Server 2008 (R2) and higher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4.3 Performing Basic Windows Preparation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . 544.4 Required User Authorization for Running the Installer . . . . . . . . . . . . . . . . . 564.5 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.6 Preparing the SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.7 Installing the SAP Front-End Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.8 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.2 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665.3 Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.3.1 How to Avoid Automatic Logoff by the Installer . . . . . . . . . . . . . . . . . . . . . . . 715.3.2 Interrupted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.3.3 Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.3.4 Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.3.5 Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.3.6 Entries in the Services File Created by the Installer . . . . . . . . . . . . . . . . . . . . . . 785.3.7 Troubleshooting with the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816.2 Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826.3 Performing the Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846.4 Providing Access to the NetWeaver Administrator . . . . . . . . . . . . . . . . . . . . . . 856.5 Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856.6 Configuring User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866.7 Applying the Latest Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866.8 Creating Symbolic Links on Windows Server 2008 (R2) and higher for

Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866.9 Configuring Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . . . . 886.10 Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886.11 Configuring the Transport Management System . . . . . . . . . . . . . . . . . . . . . . . 886.12 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896.13 Enabling Recoverability of the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936.14 Setting Environment Variable CPIC_MAX_CONV . . . . . . . . . . . . . . . . . . . . . 956.15 Performing a Full System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

2013-07-15 CUSTOMER 5/198

6.16 Checking Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Chapter 7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997.1 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007.2 Checking and Changing the Paging File Settings on Windows Server

2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047.3 Performing a Domain Installation Without Being a Domain

Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067.4 Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . . 1097.5 MCOD Tablespaces and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117.6 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127.7 Dialog Instance Installation for an Upgraded System only: Updating

Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167.8 Installing the SAP Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187.9 Creating Tablespaces Manually (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207.10 Adding Database Partitions to a Database Instance . . . . . . . . . . . . . . . . . . . . . 1217.11 Installing a Near-Line Storage Database for an SAP NetWeaver BW

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237.12 Starting and Stopping the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247.13 Configuring the Windows Server Firewall on Windows Server 2008 (R2) and

higher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267.14 Implementing Single Sign-On with Microsoft Kerberos SSP for Your SAP

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1287.15 Usage Type-Specific Initial Technical Configuration Done by the

Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1287.15.1 Initial Technical Configuration for SAP NetWeaver Application Server Java

(AS Java) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1287.15.1.1 Initial Technical Configuration for Adobe Document Services . . . . . . . . . . . 1297.15.1.2 Initial Technical Configuration for Composite Application Framework Core

(CAF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307.15.1.3 Initial Technical Configuration for the System Landscape Directory

(SLD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317.15.2 Initial Technical Configuration for Process Integration (PI) . . . . . . . . . . . . . . 1317.15.2.1 Importing the SAP Exchange Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317.15.2.2 Assigning SAP_ALL Rights to User PISUPER . . . . . . . . . . . . . . . . . . . . . . . . . 1327.15.2.3 Activating the ICF Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337.15.2.4 Assigning Roles to Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337.16 Minimizing the Database Size After the Installation . . . . . . . . . . . . . . . . . . . . 133

6/198 CUSTOMER 2013-07-15

7.17 Installing Windows Application Servers in a UNIX Environment . . . . . . . . . . 1367.18 SAP System Security on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1367.19 Automatic Creation of Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . . 1397.20 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . 1407.21 Deleting the Database Instance and Database Software Manually

(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1437.21.1 Deleting the Database (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1437.21.2 Deleting a DB2 Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1437.21.3 Deleting a Database Schema Manually (Optional) . . . . . . . . . . . . . . . . . . . . . 1457.21.4 Deleting the DB2 Software Installation (Optional) . . . . . . . . . . . . . . . . . . . . . 146

Chapter 8 High Availability with Microsoft Failover Clustering . . . . . . . . . . . . . . . 1498.1 Checklist for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518.2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1528.2.1 System Configuration with Microsoft Failover Clustering . . . . . . . . . . . . . . . 1528.2.1.1 SAP System Components in a Microsoft Failover Cluster . . . . . . . . . . . . . . . . 1528.2.1.2 Multiple SAP Systems In One Microsoft Failover Cluster . . . . . . . . . . . . . . . . 1558.2.1.3 Multiple SAP Systems In Multiple Microsoft Failover Clusters . . . . . . . . . . . . 1578.2.1.4 Enqueue Replication Server in a Microsoft Failover Cluster . . . . . . . . . . . . . . 1588.2.2 Distribution of SAP System Components to Disks for Failover

Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1598.2.3 Directories in a Microsoft Failover Cluster Configuration . . . . . . . . . . . . . . . 1628.2.4 IP Addresses in a Failover Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . 1648.2.5 Obtaining IP Addresses for a High-Availability System . . . . . . . . . . . . . . . . . . 1668.3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1688.3.1 Mapping Host Names to IP Addresses for High-Availability . . . . . . . . . . . . . . 1688.4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1698.4.1 Configuring the First Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1698.4.2 Installing the Database Instance on an MSCS Node . . . . . . . . . . . . . . . . . . . . 1708.4.3 Preparing the Additional Node for MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1728.4.4 Configuring the Database for MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1728.4.5 Configuring the Additional Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . 1738.4.6 Installing the Central Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748.4.7 Installing the Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1758.5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1768.5.1 Post-Installation Checks for Enqueue Replication Server . . . . . . . . . . . . . . . . 1768.5.1.1 Checking the Status of the Enqueue Replication Server with

ENSMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

2013-07-15 CUSTOMER 7/198

8.5.1.2 Monitoring the Lock Table During Failover with ENQT . . . . . . . . . . . . . . . . 1778.6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1798.6.1 Moving Cluster Groups, or Services and Applications, or Roles . . . . . . . . . . . 1798.6.2 Starting and Stopping the SAP System in a Failover Cluster

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185A.1 Using PowerShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185A.2 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187A.3 Online Information from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189A.4 Disclaimer: Links to IBM Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

8/198 CUSTOMER 2013-07-15

1 Introduction

This installation guide describes how to install an SAP system based on the dual-stack (ABAP+Java) application server of SAP NetWeaver using the installation tool software provisioning manager 1.0 (installer for short). This guide applies to the following SAP NetWeaver releases and SAP Solution Manager releases based on them:Product ReleaseSAP NetWeaver SAP NetWeaver 7.0 Process Integration

SAP NetWeaver 7.0 Mobile InfrastructureSAP Solution Manager SAP Solution Manager 7.0 including Enhancement Package 1 Support Release 1

SAP Solution Manager 7.1 Support Release 1

CAUTIONMake sure you have read the Before You Start [page 10] section before you continue with this installation guide.

ConstraintsYou need to consider the following constraints before you start your installation: Your operating system platform must be 64-bit. Windows Server 2008 for Itanium-based systems editions is not supported. As of IBM DB2 V9.5 for Linux, UNIX, and Windows, the installation of an SAP system on the

Windows platform IA64 is not supported. This document already includes information about the new IBM DB2 for Linux, UNIX, and

Windows version 10.5 (DB2 for LUW 10.5), although this is not yet supported by SAP at the time of publishing. As soon as DB2 for LUW 10.5 is supported by SAP, you can find this information in the product availability matrix at http://service.sap.com/pam.

Naming Conventions installer refers to software provisioning manager 1.0. SAP system refers to SAP system based on the application server of SAP NetWeaver 7.0 / 7.0 including Enhancement

Package 1 / 7.0 including Enhancement Package 2 / 7.0 including Enhancement Package 3. ABAP+Java system refers to SAP system based on the ABAP+Java (dual-stack) application server of SAP NetWeaver

7.0 / 7.0 including Enhancement Package 1 / 7.0 including Enhancement Package 2 . diagnostics refers to diagnostics in SAP Solution Manager. diagnostics agent refers to the agent of diagnostics in SAP Solution Manager.

1 Introduction

2013-07-15 CUSTOMER 9/198

IBM Product TerminologyThe following abbreviations are used in this guide:Abbreviation Refers to...DB2 V9.1 IBM DB2 Version 9.1 for Linux, UNIX, and WindowsDB2 V9.5 IBM DB2 Version 9.5 for Linux, UNIX, and WindowsDB2 V9.7 IBM DB2 Version 9.7 for Linux, UNIX, and WindowsDB2 10.1 IBM DB2 Version 10.1 for Linux, UNIX, and WindowsDB2 10.5 IBM DB2 Version 10.5 for Linux, UNIX, and Windows

Windows Operating SystemIn 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). You might still find the abbreviation MSCS in some sections of this guide.End of: HA (MSCS) |

1.1 Before You StartMake sure that you have read the Master Guide for your SAP NetWeaver application or SAP Solution Manager and release before you continue with this installation guide.The Master Guide is the central document leading you through the overall implementation process for your SAP system installation. It contains crucial information about the overall implementation sequence, that is activities you have to perform before and after the installation process described in this installation guide.You can find a printed version of the Master Guide in your installation package or you can download the latest version from SAP Service Marketplace.The following table lists the Master Guides of the SAP system applications for which you can use this installation guide, along with the available quick link or path to the appropriate download location under http://service.sap.com/instguides:Title Internet AddressMaster Guide - SAP NetWeaver 7.0 http://service.sap.com/ installnw70Master Guide SAP Solution Manager http://service.sap.com/instguides SAP Components

SAP Solution Manager

1 Introduction1.1 Before You Start

10/198 CUSTOMER 2013-07-15

1.2 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 DescriptionSoftware Provisioning Manager Software provisioning manager is the successor of the

product- and release-specific delivery of provisioning tools, such as SAPinst. Before you perform an installation or system copy, we recommend that you always download the latest version of the software provisioning manager [page 60] which is part of the Software Logistics Toolset (SL Toolset for short). This way, you automatically get the latest SAPinst version including latest fixes in the tool and supported processes. For more information about software provisioning manager as well as products and releases supported by it, see SAP Note 1680045.As a result, SAPinst has been renamed to software provisioning manager 1.0 (installer for short) in this documentation.However, the term SAPinst is still used in: Texts and screen elements in the software provisioning

manager GUI Naming of executables, for example sapinst.exe

You no longer require a Solution Manager Key for the installation.

The SAP Cryptographic Library SAPCRYPTO.SAR is now available in the DBINDEP subfolder of the UC Kernel (folder K__U_) medium and installed automatically by the installer. You do not have to separately download SAPCRYPTO.SAR any longer.For more information, see Basic SAP System Installation Parameters [page 30].

SAP Java Virtual Machine (SAP JVM) You no longer have to download and install a Java Development Kit (JDK) from another software vendor as a prerequisite for the installation.The SAP JVM 4 is a Java Development Kit (JDK) provided and supported by SAP. It is fully compliant to the Java Platform Standard Edition 1.4. The installer contains SAP JVM 4 and deploys it with the SAP system or instance being installed.The diagnostics agent is installed automatically with SAP JVM 6.

Windows Server 2012 Check the Product Availability Matrix at http://service.sap.com/pam, whether your database is supported on Windows Server 2012.For Windows Server 2012, we only use Power Shell commands to describe Windows commands. You need to open the Power Shell in administrative mode. For more information about Power Shell, see Using Powershell [page 185].

1 Introduction1.2 New Features

2013-07-15 CUSTOMER 11/198

Database-Specific FeaturesArea DescriptionSupported database versions Depending on your SAP product release, the supported database

versions might differ. For more information, see the product availability matrix at http://service.sap.com/pam.As of DB2 V9.1, you can have multiple DB2 installations on one physical machine. The database installations are independent of each other and can have different Fix Pack levels as well as different configuration settings, and so on.By default, the software is installed in the following directory::\db2\db2\db2_softwareAs of IBM DB2 10.5, DB2 Advanced Enterprise Server Edition (AESE) is used for SAP applications, instead of Enterprise Server Edition (ESE). For more information, see SAP Note 816773.

Specification of connect user name You can specify the name of the connect user (ABAP: sap, Java: sapdb) independently from the SAP schema name during the dialog phase of the installation.We recommend, however, that you keep the names of the connect user and the database schema identical in standard use cases.

NOTEIf you are performing a system copy using database means, DB2 is not able to change the schema name and you can then choose a connect user name that is different from the schema name.

Installation of near-line storage database

As of SAP NetWeaver 7.0 incl. EhP2, you can install a near-line storage database using the installer. The near-line storage database is a remote DB2 database that you can use to store BW data that is not frequently used.

NOTEYou can only install the near-line storage database on DB2 V9.7 for Linux, UNIX,and Windows or higher.

For more information, see Installing a Near-Line Storage Database for an SAP NetWeaver BW System [page 123].

Inline LOBs and long VARCHAR replacement

As of DB2 V9.7, tables of the newly created database automatically use inline LOBs.That is, small LOBs up to a specified size are now stored together with the table data. LOBs that are larger than the specified size are transparently stored in the LOB storage object. Inlined LOBs are also subject to row compression.With inline LOBs, performance improves and disk space can be saved. For that reason, the type mapping for several ABAP dictionary types of the AS ABAP was adapted to use LOBs instead of LONG VARCHARs.

NOTEThe database of an AS Java does not use LONG data types and is therefore not affected.

For more information, see SAP Note 1351160.

1 Introduction1.2 New Features

12/198 CUSTOMER 2013-07-15

Area DescriptionData compression As of DB2 V9.7, if you select Use DB2's Data Compression during the dialog

phase of the installation, indexes are compressed using the DB2 index compression. In addition, as of DB2 V9.5, if you select Use DB2's Data Compression, tables that are created after the database installation are also compressed.As of DB2 10.5, the default mode for table data compression is adaptive compression.For more information, see Optimization of Database Size on Disk [page 48].

DB2 software installation The software provisioning manager automatically installs and uninstalls the database software.

Role-based security concept As of DB2 V9.7 or higher:You can use predefined database roles to restrict user privileges on the database according to organizational tasks. The installer creates these roles automatically and assigns the SAP default users to their appropriate database role. For more information, see Ensuring User Security [page 89].

1.3 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/notesSAP Notes for the InstallationSAP Note Number Title Description1680045 Release Note for Software

Provisioning Manager 1.0Software provisioning manager 1.0 with installation and system copy for SAP NetWeaver-based systems

1088980 Documentation: SAP Solution Manager

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

1010428 End-to-End Diagnostics Information about availability and limitations of SAP Solution Manager End-to-End Diagnostics.

1718413 Inst. SAP Systems Based on NW 7.0 incl. EHPs: Windows

Windows-specific information about the SAP system installation and corrections to this documentation.

1724557 Inst. Systems Based on NW 7.0 incl. EHPs: Windows DB2 LUW

Database-specific information about the SAP system installation (ABAP and Java) and corrections to this documentation.

702175 DB6: Supporting several database partitions with DB2

Platform-specific additional information about the support of multiple partitions with DB2 for Linux, UNIX, and Windows

1 Introduction1.3 SAP Notes for the Installation

2013-07-15 CUSTOMER 13/198

SAP Note Number Title Description1134975 DB6: MSCS Installation on IBM

DB2 for Linux, UNIX, and Windows

Platform-specific additional information about the installation of Microsoft Cluster on IBM DB2 for Linux, UNIX, and Windows.

101809 DB6: Supported Fix Packs for DB2 for LUW

Provides information about the currently released database and Fix Pack combinations

1144737 Inst. NetWeaver 7.0 EHP3 - Diagnostics Agent installation

Problems discovered after the publication of the installation guide or post-installation steps

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

73606 Supported Languages and Code Pages

Information on possible languages and language combinations in SAP systems

1067221 Central Note for Heterogeneous Installation

This SAP Note and its related SAP Notes describe the released operating system and database combinations for heterogeneous SAP systems landscapes.

1 Introduction1.3 SAP Notes for the Installation

14/198 CUSTOMER 2013-07-15

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 15] Distributed system [page 16] Only valid for: HA (MSCS) |

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

You can install dialog instances [page 17] to an existing system. You can install an SAP Host Agent [page 19] separately.

NOTEThis installation guide does not describe how to install an SAP system running on IBM DB2 for Linux, UNIX, and Windows with the IBM DB2 pureScale Feature. If you want to install an SAP system with the IBM DB2 pureScale Feature, follow the instructions of the installation guide Running an SAP System on IBM DB2 10.1 with the pureScale Feature on SAP Service Marketplace at http://service.sap.com/instguides Installation .

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)

The ABAP stack and the Java stack use their own database schema in the same database Central instanceAdditionally you can install one or more dialog instances. For more information, see Dialog Instance [page 17].The following figure shows an example of SAP instances in a central system.

2 Installation Options Covered by this Guide2.1 Central System

2013-07-15 CUSTOMER 15/198

Figure 1: Central ABAP+Java System

2.2 Distributed SystemIn a distributed system, every instance can run on a separate host.These are the following instances: Central services instance for ABAP (ASCS instance) (optional) Central services instance (SCS instance) Database instance (DB instance)

The ABAP stack and the Java stack use their own database schema in the same database Central instanceOptionally you can install one or more dialog instances. For more information, see Installation of a Dialog Instance [page 17].The following figure assumes the following: The ASCS instance runs on the SAP global host. The central instance runs on a separate host.

NOTEYou can also install the central instance on the SAP global host.

The SCS instance runs on the SAP global host. The global transport directory resides on a separate SAP transport host.

2 Installation Options Covered by this Guide2.2 Distributed System

16/198 CUSTOMER 2013-07-15

Figure 2: Distributed ABAP+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 Microsoft Failover Clustering [page 152].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.A dialog instance can run on: The host of any instance of the existing SAP system On a dedicated host

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

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 41].

2 Installation Options Covered by this Guide2.3 High Availability System

2013-07-15 CUSTOMER 17/198

NOTEIf 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. The installer determines if a non-Unicode system exists and chooses the correct executables for the system type.

Dialog Instance for a Central SystemThe 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 15].

Dialog Instance for a Distributed SystemThe following figure shows dialog instances that are running on dedicated hosts.

2 Installation Options Covered by this Guide2.4 Dialog Instance

18/198 CUSTOMER 2013-07-15

Figure 4: Dialog Instance for a Distributed System

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

Dialog Instance for a High-Availability SystemIn 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 HA configuration, see System Configuration in Microsoft Failover Clustering [page 152].End of: HA (MSCS) |

2.5 SAP Host Agent as a Separate InstallationUsing the SAP Host Agent you can centrally monitor any host with the Alert Monitor or the SAP NetWeaver Administrator or the Landscape Virtualization Manager. In addition, the SAP Host Agent is used by the Landscape Virtualization Manager for starting, stopping, and relocating SAP instances and databases.The SAP Host Agent is automatically installed with every SAP system instance based on SAP NetWeaver 7.0 including EHP2 or higher (integrated installation). So if you have an SAP system or instance based on SAP NetWeaver 7.0 including EHP2 or higher on the host, you do not need to apply the procedure described in the section. This procedure is only for hosts with no SAP Host Agent running on them, due to the following reasons: There is no SAP system or instance on the host.

2 Installation Options Covered by this Guide2.5 SAP Host Agent as a Separate Installation

2013-07-15 CUSTOMER 19/198

The SAP system running on the host is based on SAP NetWeaver 7.0 including EHP1 or lower. You have upgraded your SAP system to SAP NetWeaver 7.0 including Enhancement Package 2 or

higher and the upgraded system does not have yet a SAP Host Agent.The section Installing the SAP Host Agent Separately [page 118] describes how to perform the installation.

2 Installation Options Covered by this Guide2.5 SAP Host Agent as a Separate Installation

20/198 CUSTOMER 2013-07-15

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 instanceDetailed information about the steps is available in the relevant chapter.

Prerequisites1. You have planned your SAP system landscape according to the process sequence in the Master

Guide.2. You have decided on your installation option [page 15].

Central, Distributed, or High-Availability SystemNOTEIn 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 can install optional standalone units J2EE Adapter Engine, Partner Connectivity Kit, Application Sharing Server only as a central system.

1. You check the hardware and software requirements [page 22] for each installation host.2. You plan how to set up user and access management [page 29].3. You identify basic SAP system installation parameters [page 30].4. You decide whether you want to perform a domain or local installation [page 41].5. You carefully plan the setup of your database [page 41].6. You decide on the transport host to use [page 52].7. Only valid for: HA (MSCS) |

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

8. You can continue with Preparation [page 53].

Dialog Instance1. You check the check the hardware and software requirements [page 22] for the installation host on which

you want to install one or more dialog instances.2. You identify basic SAP system installation parameters [page 30].

3 Planning3.1 Planning Checklist

2013-07-15 CUSTOMER 21/198

3. You can now continue with Preparation [page 53].

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

CAUTIONIf 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 Flow1. Check the Product Availability Matrix at http://service.sap.com/pam for supported operating

system releases.2. 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 23]. Integrated in the installer (mandatory) during the installation process

For more information, see Running the Installer [page 66].NOTEFor the most recent updates to the Prerequisite Checker, always check SAP Note 855498.

The hardware and software requirements tables in Requirements for the SAP System Hosts [page 24]

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

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 Planning3.2 Hardware and Software Requirements

22/198 CUSTOMER 2013-07-15

3.2.1 Running the Prerequisites Check in Standalone Mode (Optional)

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

RECOMMENDATIONWe recommend that you use both the Prerequisites Check and the requirements tables for reference.

NOTEWhen installing your SAP system, the installer automatically starts the Prerequisites Check and checks the hardware and software requirements in the background.

Procedure1. Make the installer available on the host where you want to run the Prerequisites Check:

1. Download the latest version of the software provisioning manager 1.0 archive 70SWPM10SP_.SAR fromhttp://service.sap.com/swdc Support Packages and Patches A Z Index S SL Toolset SL

Toolset Entry by Component Software Provisioning Manager Software Provisioning Manager 1.0

2. Unpack the software provisioning manager 1.0 archive to a local directory using the following command:SAPCAR xvf \\.SAR -R \

2. Start the installer as described in Running the Installer [page 66].3. On the Welcome screen, choose Software Life-Cycle Options Additional Preparation

Options Prerequisites Check .4. Follow the instructions in the installer dialogs and enter the required parameters.

NOTEFor more information about each parameter, position the cursor on the parameter field and choose F1 in the installer.

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.

5. To start the prerequisites check, choose Next.

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


2013-07-15 CUSTOMER 23/198

3.2.2 Requirements for the SAP System HostsThis section provides information about the hardware and software requirements for the: Central services instance for ABAP (ASCS) Enqueue Replication Server instance (ERS) Central services instance (SCS) Database instance Central instance Dialog instance

NOTEThe dialog instance is optional in a non-HA system, but mandatory in an HA system.

SAP host agent Diagnostics agentOnly valid for: HA (MSCS) |

General Requirements for a High-Availability System Windows Server 2012:

1. Check that your cluster hardware is certified for Windows Server 2012 and has the Windows Server 2012 logo.

2. You must validate your failover cluster configuration by running the command test-cluster in a PowerShell.The Failover Cluster Validation Report must not show any warnings and errors.

Windows Server 2008 (R2):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 must not show any warnings and errors.

Windows Server 2003: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. For more information, see: http://www.windowsservercatalog.com Windows Server 2003 Certified http://www.saponwin.com

The cluster nodes of the cluster must be connected by a private and public network: The public network enables communication from the cluster nodes of the cluster to other

resources in the local area network (LAN).


24/198 CUSTOMER 2013-07-15

The private network enables internal communication between the cluster nodes. In particular, it enables the Cluster Service running on all cluster nodes to regularly exchange messages on the state of the cluster nodes so that the failure of resources is quickly detected.

Each of the cluster nodes in the cluster must have its own local disks and have access to shared disks that can be reached by the cluster nodes via a shared bus.All software except the Windows operating system, the DB2 executables, and the failover cluster 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 Failover Clustering [page 159].

All disk controllers must be able to support hardware-based RAID.CAUTIONYou cannot use a host with a domain controller as a cluster node.

End of: HA (MSCS) |

Hardware and Software RequirementsThe following tables show the hardware and software requirements. Most of the requirements are valid for every installation host whereas some requirements are instance-specific and are marked accordingly.

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. Only valid for: HA (MSCS) |

If you install multiple SAP systems in one Microsoft failover cluster, make sure that together with your hardware partner you have set up the correct sizing for your system configuration.End of: HA (MSCS) |

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

Hardware RequirementsHardware Requirement Requirement How to CheckMinimum disk space

Central services instance (SCS) (not including paging file):5 GB (x64)8 GB (IA64)

To check disk space: Windows Server 2012:

1. Open PowerShell in elevated mode, and enter the following command:


2013-07-15 CUSTOMER 25/198

Hardware Requirement Requirement How to Check

Central services instance for ABAP (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. 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. Database instance

For more information about the required disk space, see SAP Note 1724557.

NOTEFor safety reasons (system failure), the file systems must be distributed physically over several disks, or RAID-technology must be used.

Enqueue replication server instance (ERS) (not including paging file):5 GB (x64)8 GB (IA64)

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 (not including paging file):

2.5 GB (x64)5 GB (IA64)In addition you require 1.5 GB for the diagnostics agent

Diagnostics agent:1.5 GB

SAP host agent:0.5 GB

Temporary disk space for every required installation medium that you have to copy to a local hard disk:4.3 GB

get-volume2. Check the value

SizeRemaining of the disk you want to install on.

Windows Server 2008 (R2):1. Choose Start All Programs

Administrative ToolsStorage Computer

Management Disk Management .

2. Right-click the drive and choose Properties.

Windows Server 2003:1. Choose Start All Programs

Administrative ToolsComputer Management Disk

Management .2. Right-click the drive and

choose Properties.

Minimum RAM

All instances, except SAP host agent, and diagnostics agent:6 GB

SAP host agent:0.5 GB

To check RAM: Windows Server 2012:

Open PowerShell in elevated mode, and enter the following command:


26/198 CUSTOMER 2013-07-15

Hardware Requirement Requirement How to Check

Diagnostics agent:1 GB

Get-WmiObject Win32_ComputerSystem

Windows Server 2008 (R2) or Windows Server 2003:Choose Start Control Panel

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

Paging file size

For more information, see SAP Note 1518419. To check paging file size: Windows Server 2012:

For more information, see Checking and Changing the Paging File Settings on Windows Server 2012 [page 104]

Windows Server 2008 (R2) or Windows Server 2003:1. Choose Start Control Panel

System .NOTEWindows Server 2008 (R2)If System is not visible, change View by: from Category into Large icons.

2. Windows Server 2008 (R2)Choose Advanced system settings.

3. Windows Server 2003:Choose Advanced.

4. In section Performance, select Settings... Advanced .

5. If required, in section Virtual memory, choose Change.

NOTEDo not select Automatically managed paging file size for all drives.

Only valid for: HA (MSCS) |NOTEYou must adjust the size of the paging file on all cluster nodes.

End of: HA (MSCS) |


2013-07-15 CUSTOMER 27/198

Hardware Requirement Requirement How to CheckProcessing units

The number of physical or virtual processing units usable by the operating system image must be equal or greater than 2 for application server instances and database instances.For an ASCS instance and SCS instance running on a separate host, 1 physical or virtual processing unit usable by the operating system image might be sufficient.Examples for processing units are processor cores or hardware threads (multithreading).In a virtualized environment you must take care that adequate processor resources are available to support the workloads of the running SAP systems.

Suitable backup system

Software RequirementsSoftware Requirement Requirement How to CheckWindows operating system

64-bit version of one of the following Windows Server Editions of an supported Windows operating system: Windows Server 2012:

Windows Server Standard Edition Windows Server Datacenter

Edition Windows Server 2008 (R2) and Windows

Server 2003: Only valid for: non-HA |

Windows Server Standard EditionEnd of: non-HA |

Windows Server Enterprise Edition

Windows Server Datacenter EditionCAUTIONWindows Server 2008 (R2) for Itanium-based systems editions is not supported.

CAUTIONMake sure that you install the English language pack so that your support requests can be handled quickly.

For any version of Windows Server, you need the latest supported service pack

To check your Windows version: Windows Server 2012:

Open PowerShell in elevated mode, and enter the following command:Get-WmiObject Win32_OperatingSystem | select caption

Windows Server 2008 (R2) or Windows Server 2003:1. Choose Start All Programs

Accessories Command Prompt

2. Enter the command winverOnly valid for: HA (MSCS) |

NOTE Windows Server 2008 (R2)

and higher:You must add the operating system feature Failover Clustering on all cluster nodes.

Windows Server 2003:You must set up the Failover Cluster Service as described in the Microsoft documentation. During this setup you are asked for


28/198 CUSTOMER 2013-07-15

Software Requirement Requirement How to Check

a Windows Domain Account to run the Cluster Service. We strongly recommend creating an account different from the adm user, for example ClusterServiceuser=sapprdcladm, where Clustername=sapprdcl.

End of: HA (MSCS) |Database software Database instance:

DB2 V9.1 or higher (depending on your SAP product, see SAP Product Availability Matrix at http://service.sap.com/pam)The database software is automatically installed by the installer.

Central instance / dialog instance: DB2 CLI Driver / DB2 JDBC Driver (automatically installed by the installer)

For more information about supported Fix Packs, see SAP Note 101809.CAUTION For the installation of your SAP

system, only the English version of DB2 is supported.

You must only use the DB2 software provided by the SAP installation media.

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 AS ABAP. Use an LDAP directory as the data source for user data.

3 Planning3.3 Planning User and Access Management

2013-07-15 CUSTOMER 29/198

ProcedureUsing AS ABAPYou install your SAP system as described in this installation guide. During the installation, the SAP system is automatically configured to use AS ABAP as data source for the User Management Engine (UME). After the installation has finished, you can still change the user management configuration. For more information, see Configuring User Management [page 86].

Using an LDAP directory as Source for User Data1. You install your SAP system as described in this installation guide.2. Configure the user management of the newly installed SAP system to use and LDAP directory.

For more information, see Configuring User Management [page 86].

More InformationFor more information about configuring the user management of your SAP system to be installed, see the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver Platform SAP NetWeaver 7.0 Application Help SAP Library: English> | Function-Oriented View: English 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 ParametersThe installer 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 Connectivity Parameters SAP system profile directory only for systems with instances on separate hosts Master password System Landscape Directory (SLD) destinationIf you want to change any of the default settings, you can do so on the Parameter Summary screen.

CustomIf 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.NOTEYou cannot change from Custom to Typical mode or from Typical to Custom mode on the Parameter Summary screen.

3 Planning3.4 Basic SAP System Installation Parameters

30/198 CUSTOMER 2013-07-15

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 ParametersFor all other installation parameters, use the F1 help in the installer screens.

SAP System ParametersParameters DescriptionSAP System ID

The SAP System ID identifies the whole SAP system.

CAUTIONChoose 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.EXAMPLEIf 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:

ADD ADM 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

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.

SAP System Instance Numbers

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 100].

CAUTIONDo not use 43, and 89 for the instance number because: 43 is part of the port number for high availability 89 is part of the port number for Windows Terminal Server

\\

Parameters DescriptionT>\sapmnt\ \ SYS\ profile

SAP profiles are operating system files that contain instance configuration information.The installer prompts you to enter the location of the profile directory when the installation option that you execute is not the first one belonging to your SAP system installation, for example if you are performing a distributed installation or if you are installing a dialog instance to an existing SAP system. See also the description of the parameters SAP System ID and Database ID.

Master Password Common password for all users created during the installation:

NOTEIf a user already exists, you are prompted to confirm the password for this user.

Password policyThe master password must meet the following requirements: It must be 8 to 14 characters long It must contain at least one digit (0-9) It must not contain \ (backslash) and " (double quote) It must contain at least one letter in uppercase (A-Z) It must contain at least one letter in lowercase (a-z) Depending on the configuration of the password policy, additional restrictions may

apply. Depending on the installation option, additional restrictions may apply (for example,

the master password must not contain the name of a Java user created during the installation).

Message Server Port

CAUTIONThe 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.ABAP Message Server PortThere 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, where 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, where is the instance number of the ABAP message server instance.Java Message Server PortThe 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, 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.

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.


32/198 CUSTOMER 2013-07-15

Parameters DescriptionRECOMMENDATIONUse a long key phrase that cannot be guessed easily. Use both uppercase and lowercase letters in the phrase and include special characters.

NOTEIf you choose Typical mode, the installer 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.

DNS Domain Name for SAP System

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.

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

Path to SAPCRYPTO.SAR

The SAP Cryptographic Library is required to enable Secure Sockets Layer (SSL) encryption of HTTP connections. In most cases it is installed automatically from the kernel medium. In case it is not installed automatically and you are prompted for it during the installation, you can download it as described in SAP Note 455033.This software product is subject to export control regulations in Germany as the country of origin and import regulations of your own country. SAP may not yet have a corresponding export license for your user or company. Contact the contract department in your local SAP company. To download the SAP Cryptographic Software from the SAP Service Marketplace, you need a customer user ID. Before any transfer of these software products to persons, companies or other organizations outside your company, in particular in the case of any re-export of the software products, authorization is required from the German export control authorities. This might also be required from your responsible national export control authorities. This also applies to transfers to affiliated companies. Corresponding laws and regulations in the recipient country may also exist which restrict the import or the use of these software products.

Password of Operating System Users

The passwords of the operating system users must comply with the Windows password policy. The installer processes the passwords of operating system users as follows: If the operating system users do not exist, the installer creates the following users:

admThis user is the SAP system administrator user and is a member of the local Administrators group.

SAPServiceThis user is the Windows account to run the SAP system and is not a member of the local Administrators group.

sapadmThe SAP host agent user sapadm is used for central monitoring services. The installer creates this user by default as a local user without being a member of the local Administrators group.


2013-07-15 CUSTOMER 33/198

Parameters DescriptionIf 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 106]. For security reasons, however, SAP strongly recommends to create this user as a local user.

admThis 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.The installer 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.

The installer 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, the installer prompts you for the existing password, except if the password of these users is the same as the master password.

NOTEThis does not apply if the adm user already exists. The installer prompts you for the password even if the password of this user is the same as the master password.

CAUTIONMake sure that you have the required user authorization [page 56] for these accounts before you start the installation with the installer.

Java Administrator User and Password

This user has administrative permissions for user management.After the installation, this user is available both in the ABAP and in the Java systemThe installer 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 Note 718383.

Java Guest User and Password

This user is used for anonymous access.After the installation, it is available both in the ABAP and in the Java systemThe installer 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 Note 718383.

Communication User and Password

This user is used for the communication between the ABAP system and the Java system.After the installation, it is available both in the ABAP and in the Java systemThe installer sets the user name SAPJSF and the master password by default.For more information about supported UME data sources and change options, see SAP Note 718383.

SDM Password This user is used for the Software Deployment Manager (SDM).The installer sets the master password by default.

Integration Repository Service User and Password

The installer sets the user name PIREPUSER and the master password by default.If required, you can choose another user name and password according to your requirements.

NOTEIf you want to choose another user name, make sure that this user name starts with PI.


34/198 CUSTOMER 2013-07-15

Parameters DescriptionIntegration Directory Service User and Password

The installer sets the user name PIDIRUSER and the master password by default.If required, you can choose another user name and password according to your requirements.


Landscape Directory Service User and Password

The installer sets the user name PILDUSER and the master password by default.If required, you can choose another user name and password according to your requirements.


Integration Server Application User and Password

The installer sets the user name PIAPPLUSER and the master password by default.If required, you can choose another user name and password according to your requirements.


Runtime Workbench Service User and Password

The installer sets the user name PIRWBUSER and the master password by default.If required, you can choose another user name and password according to your requirements.


Adapter Framework Server Service User and Password

The installer sets the user name PIAFUSER and the master password by default.If required, you can choose another user name and password according to your requirements.


Integration Server Service User and Password

The installer sets the user name PIISUSER and the master password by default.If required, you can choose another user name and password according to your requirements.


Management Server Service User and Password

The installer 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.


Exchange Infrastructure Administrator and Password

This user has extensive authorizations.The installer 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.


2013-07-15 CUSTOMER 35/198

Parameters DescriptionNOTEIf you want to choose another user name, make sure that this user name starts with PI.

Exchange Infrastructure Communicator and Password

The installer 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.


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.

Configure a local SLDChoose 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.

NOTEThe usual case is to configure one central SLD for your whole system landscape outside the SAP Solution Manager. However, we strongly recommend that you check the Master Guide for recommendations about which option to choose.

Register in existing central SLDSLD 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.

EXAMPLEIf the instance number of your Java system is 01, the SLD HTTP Port is 50100.

SLD Data Supplier User and password

The existing SLD Data Supplier user and password of the existing central SLD

SLD ABAP API User and password

The existing SLD ABAP API user and password of the existing central SLD

SLD Gateway Host

Specify the name of the gateway host of the existing central SLD

SLD Gateway Instance Number

Specify the instance number of the gateway instance of the existing central SLD

Configure a local SLDSLD Data Supplier User and password

Specify the name of the SLD Data Supplier user to be created. This user is used to send the self-registration data of your system to the SLD.


36/198 CUSTOMER 2013-07-15

Parameters DescriptionRECOMMENDATIONWe recommend that you name this user SLDDSUSER

SLD ABAP API User and password

Specify the name of the SLD ABAP API user to be created. This user is used to send landscape data to and from the SLD.

RECOMMENDATIONWe recommend that you name this user SLDAPIUSER

Object Server Name

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 ParametersParameters DescriptionDatabase ID The identifies the database instance. The installer

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

CAUTIONChoose 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 ADM 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

Base directories of DB2 for Linux, UNIX, and Windows

Drive for the database directory Database instance home Database log files Database diagnostic data Drives for SAPDATA directoriesFor more information, see Base Directories for the Database Instance [page 42].

DB2 instance owner db2 db2 has the DB2 system administration authorities and belongs to group dbadm, which has DB2 SYSADM authorities. By default, user db2 is a member of group dbadm.


2013-07-15 CUSTOMER 37/198

Parameters DescriptionABAP database connect user (sap) The user name corresponds to the database schema where ABAP

tables are created.You can specify the name of the connect user independently from the SAP schema name during the dialog phase of the installer.

RECOMMENDATIONWe recommend, however, that you keep the names of the connect user and the database schema identical in standard use cases.

If you are performing a system copy using database means, DB2 is not able to change the schema name and you can then choose a connect user name that is different from the schema name.

Java database connect user (sapdb) The user name corresponds to the database schema where J2EE tables are created.You can specify the name of the connect user independently from the SAP schema name during the dialog phase of the installer.

RECOMMENDATIONWe recommend, however, that you keep the names of the connect user and the database schema identical in standard use cases.

If you are performing a system copy using database means, DB2 is not able to change the schema name and you can then choose a connect user name that is different from the schema name.

Database Communication Port The DB2 Communication Port is used for TCP/IP communication between the database server and remote DB2 clients.In a central system installation and for the database instance in a distributed installation, the installer always proposes 5912 as default value.

NOTEThe installer requests this value during the database instance installation.

First port The database partition servers communicate using registered services. During the installation a port range is assigned for this communication.The installer proposes default values. You must make sure that these values correspond to the values of your database partition servers. If necessary, adapt them according to your settings.

CAUTIONThe value for First Port must be the same for all database partition servers.The range between First Port and Last Port must correspond to the maximum number of partitions on a database partition server.


38/198 CUSTOMER 2013-07-15

Parameters DescriptionLast port The database partition servers communicate using registered

services. During the installation a port range is assigned for this communication.The installer proposes default values. You must make sure that these values correspond to the values of your database partition servers. If necessary, adapt them according to your settings.

CAUTIONThe range between First Port and Last Port must correspond to the maximum number of partitions on a database partition server.

Only valid for: HA (MSCS) |Drive for database software locationEnd of: HA (MSCS) |

Only valid for: HA (MSCS) |In an HA environment, the database directories have to reside on a shared drive whereas the database software must reside on a local drive.End of: HA (MSCS) |

Drive database directory In a non-HA installation, enter the drive where the database directory and the database software is located.

Drive for diagnostic data Location of the db2diag.log that contains diagnostic data required in case of, for example, a database crash.

Drive for online database Log Files These log files are needed for database backups and recovery.Specify the drive where the database online log files are to be stored.

Drive sapdata Enter the drive where each sapdata directory is to be located.Add sapdata directories Tablespaces are stored in :\db2\\sapdata.

By default, the installer creates four sapdata directories (sapdata1, sapdata2, sapdata3, sapdata4).

NOTEBe aware that the first part, for example :\db2\\ is definite and you can only enter a value for sapdata.

Use Change, that is, add or remove the names and number of the sapdata directories.

Database memory or instance memory Specify the size of the memory that DB2 requires for the database instance.

Minimize database size You can significantly reduce the size of your database by selecting the following options in the installer during the dialog phase: Use DB2's Data Compression Use Deferred Table Creation

CAUTIONBefore you select these options, make sure that you have read the information in Optimization of Database Size on Disk [page 48] and SAP Note 1151343.


2013-07-15 CUSTOMER 39/198

Parameters DescriptionDB2 Software Path Specify the file system path where either an existing DB2 software

installation already resides or where you want the new copy of DB2 to be installed.

RECOMMENDATIONIf you want to install a new copy of DB2, we recommend that you accept the default path suggested by the installer.

Diagnostics Agent ParametersThe diagnostics agent is installed automatically with the SAP system.Parameters DescriptionSystem ID of the Diagnostics Agent

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

CAUTIONChoose 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 ADM 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

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 the installer automatically creates during the installation.The directory of the diagnostics agent instance is called SMDA.For more information, see SAP Directories [page 100].The same restrictions apply as in Instance Number of the SAP System (see above).


40/198 CUSTOMER 2013-07-15

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.Windows Server 2003 or Windows Server 2008 (R2):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 InstallationIn a domain installation, the user account information is stored centrally in one database on the domain controller and can be accessed by all hosts in the system.You have to perform a domain installation if one of the following applies: You install a system distributed over several hosts. Only valid for: HA (MSCS) |

You install a high-availability system with Microsoft Failover Clustering.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 InstallationIn 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.

NOTEIf 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 the Installer [page 56] Implementing Single Sign-On with Microsoft Kerberos SSP [page 128]

3.6 Setup of Database LayoutNOTEThe following sections apply especially to the installation of a production system.

When you plan your SAP system installation, it is essential to consider the setup of your database layout with regard to the distribution of, for example, SAP directories or database file systems, to disks. The distribution depends on your specific environment and you must take factors into consideration, such

3 Planning3.5 Domain or Local Installation

2013-07-15 CUSTOMER 41/198

as storage consumption of the software components involved, safety requirements and expected workload. Make sure that you read the following sections before starting the SAP system installation:1. Base Directories for the Database Instance [page 42]2. Users and Groups [page 43]3. Directory Structure of the New Client Connectivity [page 45]4. DB2 Tablespaces [page 47]5. Optimization of Database Size on Disk [page 48]6. Data Safety and Performance Considerations for Production Systems [page 50]

3.6.1 Base Directories for the Database InstanceThis section describes the base directories that the installer creates automatically during the installation of the database instance.Additionally, in a standard installation the installer creates all required SAP directories and automatically sets the correct access rights.

RECOMMENDATIONWe recommend that you install the complete SAP system on redundant storage, such as RAID-5 or intelligent storage devices. To improve system performance, you should use multiple I/O controllers.

Directory Name Description:\db2\db2\db2_software Directory for the DB2 database software created during

installation of DB2 server software. The installer uses this directory for the integrated database software installation.

NOTEAs of DB2 V9.1 and higher, you can have multiple DB2 copies on one machine.

:\DB2 DB2 database directory

NOTEIf you are not using an MSCS cluster, you can choose only one drive for both the database directory and for the DB2 database software.

:\db2\\log_dir Contains the online log files:\db2\\db2dump Contains DB2 diagnostic log files, DB2 dump files, and

further service engineer information With DB2's automatic storage management:

:\db2\\sapdata No automatic storage management:

:\db2\\sapdata

SAP data directories for an SAP system.By default, the installer creates four sapdata directories (sapdata1, sapdata2, sapdata3, sapdata4).

3 Planning3.6 Setup of Database Layout

42/198 CUSTOMER 2013-07-15

Directory Name DescriptionNOTE In a production system, you must make sure

that the sapdata directories are located in different file systems. Otherwise, system performance can decrease. For more information, see Data Safety and Performance Considerations for Database Directories [page 50].

If you require more or fewer sapdata directories, you can change this on the Sapdata Directories dialog of the installer.

If you add additional sapdata directories during the dialog phase of the installer, the corresponding tablespace containers are equally distributed.

Each of the above directories can be placed on a different local drive during the installation.

Access AuthorizationThe following table shows the access rights that to be set for the DB2 directories. To guarantee full data security, you may manually set the access privileges of the subdirectories. The owner of all these directories must be the user Administrator.Directory Access Privilege Full Control for User/Group:\db2\db2\db2_software (Default)

Administrator, SYSTEM, SAP__LocalAdmin

:\db2\db2\db2_software \DB2 (Default)

SAP__LocalAdmin, db2, SYSTEM

:\DB2 SAP__LocalAdmin, db2, SYSTEM:\db2 Everyone:\db2\ SAP__LocalAdmin, db2, SYSTEM With DB2's automatic storage

management::\db2\\sapdata

No automatic storage management::\db2\\sapdata

db2, SYSTEM

:\db2\\log_dir db2, SYSTEM

3.6.2 Users and GroupsUsing DB2 the following users and groups are needed in the SAP system.DB2 UsersUsers Descriptionadm SAP system administratorSAPService SAP service account

3 Planning3.6 Setup of Database Layout

2013-07-15 CUSTOMER 43/198

Users Descriptiondb2 Database administrator

NOTEIndependently of the installation type (domain or local), this user is only used on the database host.

sap Default ABAP connect user for SAP database objects. You can change this user during the installation.

NOTEIn a local installation, this user is only created on the dat

SAP Installation Guide for NW 7.0

Documents

Transcript of SAP Installation Guide for NW 7.0