inst sap nw java 7.3

Installation GuideSAP Systems Based on the Application Server Java of SAP NetWeaver on Windows: OracleUsing Software Provisioning Manager 1.0

Valid for SAP Systems Based on: SAP NetWeaver Composition Environment 7.2 SAP NetWeaver 7.3 SAP NetWeaver 7.3 including Enhancement Package 1 SR1 SAP NetWeaver 7.4

Target Audience System Administrators Technical Consultants

CUSTOMERDocument version: 1.30 2013-04-02

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 installing

SAP 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/178 CUSTOMER 2013-04-02

Typographic Conventions

Example Description

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your .

ExampleExample

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

Example Emphasized words or expressions

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

http://www.sap.com Textual cross-references to an internet address

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

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

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

Cross-references to other documentation or published worksExample Output on the screen following a user action, for example, messages

Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

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

EXAMPLE Keys on the keyboard

2013-04-02 CUSTOMER 3/178
http://www.sap.comhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version at the following location: http://service.sap.com/instguides

The following table provides an overview of the most important document changes.

Version Date Description

1.30 2013-04-02 Updated version



1.00 2012-08-06 Initial version

4/178 CUSTOMER 2013-04-02
http://service.sap.com/instguides

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.4 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2 Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . 15

2.1 Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.2 Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.3 High Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.4 Additional Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.5 SAP Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.2.1 Running the Prerequisites Check in Standalone Mode (Optional) . . . . . . . . . . 23

3.2.2 Requirements for the SAP System Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.3 Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.4 Domain or Local Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.5 Distribution of SAP System Components to Disks . . . . . . . . . . . . . . . . . . . . . . 39

3.6 SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.7 Multiple Oracle Homes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

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

higher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.3 Performing Basic Windows Preparation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.4 Required User Authorization for Running the Installer . . . . . . . . . . . . . . . . . 46

4.5 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4.6 Preparing the SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

2013-04-02 CUSTOMER 5/178

4.7 Preparing an External ABAP System as Source for User Data . . . . . . . . . . . . . . 49

4.8 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.2 Installing the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.2.1 Installing the Oracle 10g Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.2.1.1 Installing the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

5.2.1.2 Installing the Current Patch Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

5.2.1.3 Installing the Current Patch Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5.2.2 Installing the Oracle 11g Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.2.2.1 Installing the Oracle 11g Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.2.2.2 Installing Required Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.3 Setting Up Multiple Homes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.4 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.5 Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

5.5.1 How to Avoid Automatic Logoff by the Installer . . . . . . . . . . . . . . . . . . . . . . . 71

5.5.2 Interrupted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

5.5.3 Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

5.5.4 Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5.5.5 Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.5.6 Entries in the Services File Created by the Installer . . . . . . . . . . . . . . . . . . . . . . 78

5.5.7 Troubleshooting with the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

6.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

6.2 Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

6.3 Logging on to the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

6.4 Providing Access to the NetWeaver Administrator . . . . . . . . . . . . . . . . . . . . . . 83

6.5 Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6.6 Creating Symbolic Links on Windows Server 2008 (R2)and higher for

Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

6.7 Configuring the Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . 86

6.8 Applying the Latest Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

6.9 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

6.10 Performing Oracle-Specific Post-Installation Steps . . . . . . . . . . . . . . . . . . . . . . 89

6.11 Performing a Full System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6/178 CUSTOMER 2013-04-02

Chapter 7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.1 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.2 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.3 Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . . . 98

7.4 Checking and Changing the Paging File Settings on Windows Server

2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

7.5 Performing a Domain Installation Without Being a Domain

Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

7.6 Installing the SAP Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

7.7 Starting and Stopping the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

7.8 Configuring the Windows Server Firewall on Windows Server 2008 (R2) and

higher (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

7.9 Troubleshooting for Portal Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

7.10 SAP System Security on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

7.11 Automatic Creation of Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . . 113

7.12 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . 115

7.13 Deleting the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Chapter 8 High Availability with Microsoft Failover Clustering . . . . . . . . . . . . . . . 121

8.1 Checklist for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

8.2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

8.2.1 System Configuration with Microsoft Failover Clustering . . . . . . . . . . . . . . . 124

8.2.1.1 SAP System Components in a Microsoft Failover Cluster . . . . . . . . . . . . . . . . 125

8.2.1.2 Multiple SAP Systems In One Microsoft Failover Cluster . . . . . . . . . . . . . . . . 128

8.2.1.3 Multiple SAP Systems In Multiple Failover Clusters . . . . . . . . . . . . . . . . . . . . 130

8.2.1.4 Enqueue Replication Server in a Microsoft Failover Cluster

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

8.2.2 Distribution of SAP System Components to Disks for Failover

Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

8.2.3 Directories in a Microsoft Failover Cluster Configuration . . . . . . . . . . . . . . . 137

8.2.4 IP Addresses in a Failover Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . 138

8.2.5 Obtaining IP Addresses for High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . 140

8.3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

8.3.1 Mapping Host Names to IP Addresses for a High-Availability

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

8.4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

8.4.1 Installing the Oracle Fail Safe Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

2013-04-02 CUSTOMER 7/178

8.4.1.1 Installing the Oracle 10g Fail Safe Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

8.4.1.2 Installing the Oracle 11g Fail Safe Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

8.4.2 Configuring the First Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

8.4.3 Creating the Oracle Fail Safe Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

8.4.4 Installing the Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

8.4.5 Setting Up a Shared Database Directory in Oracle Home . . . . . . . . . . . . . . . . 151

8.4.6 Adding the Oracle Database Resource to the Fail Safe Group . . . . . . . . . . . . . 153

8.4.7 Configuring the Additional Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

8.4.8 Additional Steps for the Oracle Fail Safe Configuration . . . . . . . . . . . . . . . . . 154

8.4.9 Installing the Primary Application Server Instance . . . . . . . . . . . . . . . . . . . . . 156

8.4.10 Installing the Additional Application Server Instance . . . . . . . . . . . . . . . . . . 157

8.5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

8.5.1 Post-Installation Checks for Enqueue Replication Server . . . . . . . . . . . . . . . . 158

8.5.1.1 Checking the Status of the Enqueue Replication Server with

ENSMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

8.5.1.2 Monitoring the Lock Table During Failover with ENQT . . . . . . . . . . . . . . . . 159

8.6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

8.6.1 Moving Cluster Groups, or Services and Applications, or Roles . . . . . . . . . . . 161

8.6.2 Starting and Stopping the SAP System in a Microsoft Failover Cluster

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

A.2 Using PowerShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

8/178 CUSTOMER 2013-04-02

1 Introduction

This document describes how to install an SAP system based on the 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 Business Suite applications based on

them:

SAP NetWeaver Composition Environment 7.1 SAP NetWeaver Composition Environment 7.1 including Enhancement Package 1 SAP NetWeaver Composition Environment 7.2 SAP NetWeaver 7.3 SAP NetWeaver 7.3 including Enhancement Package 1 (SAP NetWeaver 7.3 EHP1) SAP Enhancement Package 4 for SAP ERP 6.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP Enhancement Package 5 for SAP ERP 6.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP Enhancement Package 6 for SAP ERP 6.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP CRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP Enhancement Package 1 for SAP CRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP Enhancement Package 2 for SAP CRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP SRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP Enhancement Package 1 for SAP SRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP Enhancement Package 2 for SAP SRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP SCM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP Enhancement Package 1 for SAP SCM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP NetWeaver 7.4

NOTE

Not all SAP NetWeaver releases or SAP Business Suite applications that are available in software

provisioning manager 1.0 and are described in this installation guide might have been released

already. Always check SAP Note 1680045 to ensure that the installation options you want to

perform are already supported.

CAUTION

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

Constraints

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

Windows Server 2012

1 Introduction

2013-04-02 CUSTOMER 9/178
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1680045&_NLANG=en&_NVERS=0

This document already includes information about the new Windows operating system, Windows

Server 2012, although this is not yet supported by SAP at the time of publishing.

As soon as Windows Server 2012 is supported by SAP, you find this information in the Product

Availability Matrix at http://service.sap.com/pam. There you find all information about the

supported operating system and database releases for your SAP system.

Your operating system platform must be 64-bit.

Naming Conventions

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

Package 1 / SAP NetWeaver CE 7.2 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver

7.4.

Java system refers to SAP system based on the Java application server of SAP NetWeaver CE 7.1 / 7.1 including Enhancement Package 1 / SAP NetWeaver CE 7.2 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP

NetWeaver 7.4.

diagnostics refers to diagnostics in SAP Solution Manager. diagnostics agent refers to the agent that performs the 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 Availability

Only 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 Microsoft Failover

Clustering. The Windows Server Failover Clustering 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 Before You Start

Make sure that you have read the release-specific Master Guide for your SAP Business Suite application

or SAP NetWeaver application and release before you continue with this installation guide.

The Master Guide is the central document leading you through the overall implementation process

for you 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.

1 Introduction

1.1 Before You Start

10/178 CUSTOMER 2013-04-02
http://service.sap.com/pam

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:

Document Internet Address

Master Guide SAP for banking 2011 http://service.sap.com /instguides Industry Solution Guides SAP for Banking Solution Guides

Master Guide - SAP NetWeaver Composition Environment 7.1

http://service.sap.com /instguidesnwce71

Master Guide - SAP NetWeaver CE 7.1 Including EHP1

http://service.sap.com /instguidesnwce711 InstallationPlanning

Master Guide - SAP NetWeaver CE 7.1 Including EHP1


Master Guide - SAP NetWeaver Composition Environment 7.2


Master Guide SAP NetWeaver 7.3 http://service.sap.com /installNW73

Master Guide SAP Enhancement Package 1 for SAP NetWeaver 7.3

http://service.sap.com /installNW73

Master Guide - SAP Enhancement Package for SAP ERP 6.0 powered by SAP NetWeaver

http://service.sap.com/ erp-inst

Master Guide (Including Upgrade Information) - SAP Supplier Relationship Management 7.0

http://service.sap.com/ srm-inst

Master Guide (Including Upgrade Information) - SAP Customer Relationship Management 7.0

http://service.sap.com/ crm-inst

Master Guide SAP Supply Chain Management 7.0 Powered by SAP NetWeaver

http://service.sap.com/instguides SAP Business Suite Applications SAP SCM

1.2 New Features

The table below provides an overview of the new features.

Make sure that you also read the release notes at http://service.sap.com/releasenotes.

Area Description

Software 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 52] 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

1 Introduction

1.2 New Features

2013-04-02 CUSTOMER 11/178
http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguidesnwce71http://service.sap.com/instguidesnwce711http://service.sap.com/instguidesnwce711http://service.sap.com/instguidesnwce72http://service.sap.com/installNW73http://service.sap.com/installNW73http://service.sap.com/erp-insthttp://service.sap.com/srm-insthttp://service.sap.com/crm-insthttp://service.sap.com/instguideshttp://service.sap.com/releasenotes

Area Descriptionthe 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 (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 software provisioning manager. You do not have to separately download SAPCRYPTO.SAR any longer. For more information, see Basic SAP System Installation Parameters [page 29].

Process Integration and Orchestration is available as an optional standalone unit installation.

Windows Server 2012 This document already includes information about the new Windows operating system, Windows Server 2012, although this is not yet supported by SAP at the time of publishing. As soon as Windows Server 2012 is supported by SAP, you will find this information in the Product Availability Matrix at http://service.sap.com/pam.For Windows Server 2012, we only use PowerShell commands to describe Windows commands. You need to open the Power Shell in administrative mode. For more information about PowerShell, see Using PowerShell [page 168].

1.3 SAP Notes for the Installation

You 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

1680045 Release Note for Software Provisioning Manager 1.0

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

1710950 Inst. SAP Systems Based on NW 7.1 and higher: Windows

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

1 Introduction

1.3 SAP Notes for the Installation

12/178 CUSTOMER 2013-04-02
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1680045&_NLANG=en&_NVERS=0http://service.sap.com/pamhttp://service.sap.com/pamhttp://service.sap.com/noteshttp://service.sap.com/noteshttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1680045&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1710950&_NLANG=en&_NVERS=0

SAP Note Number Title Description

1710995 Inst. SAP Systems Based on NW 7.1 and higher: Win Oracle

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

828268 Oracle 10g: New functions Information about Oracle 10g features released for the SAP system

1431800 Oracle 11.2.0: Central Technical Note Information about Oracle 11g with multiple links to notes on Oracle 11g

1448655 Inst. NetWeaver 7.3 - Diagnostics Agent installation

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

737368 Hardware requirements of Java Development

Information on the hardware requirements for usage type Development Infrastructure (DI), which depends on the size of your development team

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.4 Accessing the SAP Library

The references to SAP NetWeaver Library documentation in this installation guide always refer to

the following on SAP Help Portal:

SAP systems based on SAP NetWeaver Composition Environment 7.1:http://help.sap.com/nwce71 Application Help SAP Library: English

SAP systems based on SAP NetWeaver Composition Environment 7.1 including Enhancement Package 1:

http://help.sap.com/nwce71 Application Help SAP Library: English

SAP systems based on SAP NetWeaver Composition Environment 7.2:http://help.sap.com/nwce72 Application Help SAP Library: English

SAP systems based on SAP NetWeaver 7.3:http://help.sap.com/nw73 Application Help SAP Library: English

SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1:http://help.sap.com/nw731 Application Help SAP Library: English

SAP systems based on SAP NetWeaver 7.4:http://help.sap.com/nw74 Application Help SAP Library: English

1 Introduction

1.4 Accessing the SAP Library

2013-04-02 CUSTOMER 13/178
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1710995&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=828268&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1431800&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1448655&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=737368&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=855498&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=73606&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067221&_NLANG=en&_NVERS=0http://help.sap.com/nwce71http://help.sap.com/nwce71http://help.sap.com/nwce72http://help.sap.com/nw73http://help.sap.com/nw731http://help.sap.com/nw74

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

2 Installation Options Covered by this Guide

This section shows the installation options covered by this installation 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.

Standard system [page 15] (formerly known as central system) Distributed system [page 16] Only valid for: HA (MSCS) |

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

You can install one or more additional application server instances [page 17] to an existing standard, distributed, or high-availability system.

You can install an SAP Host Agent separately [page 19].

2.1 Standard System

You can install a standard system on a single host.

In a standard system, all main instances run on a single host:

There are the following instances:

Central services instance (SCS instance) Enqueue replication server instance (ERS instance) for the SCS instance (optional) Database instance (DB) Primary application server instance (PAS instance)


2.1 Standard System

2013-04-02 CUSTOMER 15/178

Figure 1: Standard Java System

2.2 Distributed System

An SAP system consists of SAP instances. An SAP instance is a group of processes that are started and

stopped at the same time.

In a distributed system, every instance can run on a separate host:

Central services instance for Java (SCS instance) Enqueue replication server instance (ERS instance) for the SCS instance (optional) Database instance (DB)

The Java stack uses its own database schema in the database

Primary application server instance (PAS)Optionally you can install one or more additional application server instances. For more information,

see Installation of an Additional Application Server Instance [page 17].


2.2 Distributed System

16/178 CUSTOMER 2013-04-02

Figure 2: Distributed Java System


2.3 High Availability System

For more information about the system components you have to install and how to distribute them

on the specific hosts, see System Configuration with Microsoft Failover Clustering [page 124].End of: HA (MSCS) |

2.4 Additional Application Server Instance

You can install one or more additional application server instances for an existing SAP system.

Additional application server instances are optional and can be installed on separate hosts.

An additional application server instance can run on:

The host of any instance of the existing SAP system On a dedicated host

NOTE

We do not recommend installing additional application server instances on the SAP global host.

NOTE

If you want to install an additional application server 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 38].


2.3 High Availability System

2013-04-02 CUSTOMER 17/178

Additional Application Server Instance for a Standard System

The following figure shows additional application server instances that are running on dedicated hosts.

Figure 3: Additional Application Server Instance for a Standard Java System

For more information, see Standard System [page 15].

Additional Application Server Instance for a Distributed System

The following figure shows additional application server instances that are running on dedicated hosts.


2.4 Additional Application Server Instance

18/178 CUSTOMER 2013-04-02

Figure 4: Additional Application Server Instance for a Distributed Java System

For more information, see Distributed System [page 16].


Additional Application Server Instance for a High-Availability System

In a high-availability system, you require apart from the primary application server instance at least

one additional application server instance. For more information about how to install and distribute

the application servers in an MSCS configuration, see section System Configuration in an MSCS

Configuration [page 124].End of: HA (MSCS) |

2.5 SAP Host Agent as a Separate Installation

Using 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 during the installation of all new SAP system instances

based on SAP NetWeaver 7.2 or higher. You only need to install an SAP 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.2 or higher.



2013-04-02 CUSTOMER 19/178

The section Installing the SAP Host Agent Separately [page 105] describes how to perform the installation.



20/178 CUSTOMER 2013-04-02

3 Planning

3.1 Planning Checklist

This section includes the planning steps that you have to perform for the following installation options:

Standard, distributed, or high-availability system Additional application server instanceDetailed information about the steps is available in the relevant chapter.

Prerequisites

1. You have chosen your installation scenario according to the Master Guide available at the

appropriate download location under http://service.sap.com/instguides.

For more information, refer to Before You Start [page 10].

2. You have decided which installation option [page 15] described in this guide you want to perform.

Standard, Distributed, or High-Availability System

NOTE

In a standard system, all mandatory instances are installed on one host. Therefore, if you are

installing a standard system, you can ignore references to other hosts.

1. You check the hardware and software requirements [page 22] on every installation host.

2. You identify basic SAP system installation parameters [page 29].

3. You decide whether you want to perform a domain or local installation [page 38].

4. For the database installation, you decide on how to distribute your database components to disk [page 39].

5. You decide on the transport host to use [page 41].

6. You decide whether you want to integrate LDAP Directory Services in your SAP system [page 91].

7. You decide if you want to use multiple Oracle homes [page 41].

8. Only valid for: HA (MSCS) |

To install a high-availability system with Microsoft Failover Clustering, you perform the HA-

specific planning steps [page 123].End of: HA (MSCS) |

9. Optionally, you decide whether you want to install multiple components in one database (MCOD) [page

98].

10. You can now continue with Preparation [page 43].

3 Planning

3.1 Planning Checklist

2013-04-02 CUSTOMER 21/178

Additional Application Server Instance

1. You check the hardware and software requirements [page 22] for every installation host on which you want

to install one or more additional application server instances.

2. You identify basic SAP system installation parameters [page 29].

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

3.2 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating system

and the SAP instances.

CAUTION

If your hosts do not fully meet the requirements, you might experience problems when working

with the SAP system.

Prerequisites

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

Process Flow

1. 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: Standalone (optional) before the installation process

For more information, see Running the Prerequisites Check Standalone [page 23].

Integrated in the installation tool (mandatory) as part of the installation processFor more information, see Running the Installer [page 66].

NOTE

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

If you want to install usage type Development Infrastructure (DI), also check SAP

Note 737368 for system requirements and sizing.

3 Planning


22/178 CUSTOMER 2013-04-02
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=611361&_NLANG=en&_NVERS=0http://service.sap.com/pamhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=855498&_NLANG=en&_NVERS=0http://service.sap.com/sizinghttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=737368&_NLANG=en&_NVERS=0

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 Prerequisites Check in Standalone Mode (Optional)

Before installing your SAP system, you can run Prerequisites Checks 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 Prerequisites Check and the requirements tables for reference.

NOTE

When installing your SAP system, the Installer automatically starts the Prerequisites Check and checks

the hardware and software requirements in the background.

Procedure

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

SWPM10SP_.SAR from http://

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 Preparations Prerequisites Check .

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

NOTE

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

3 Planning


2013-04-02 CUSTOMER 23/178
http://service.sap.com/swdchttp://service.sap.com/swdc

5. To start the prerequisites check, choose Next.

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.

3.2.2 Requirements for the SAP System Hosts

This section provides information about the hardware and software requirements for the:

Central services instance (SCS) Database instance Primary application server instance Additional application server instance

NOTE

The additional application server instance is optional in a non-HA system, but mandatory in

an HA system.

Enqueue Replication Server instance (ERS) 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. You can access the lists as follows:

3 Planning


24/178 CUSTOMER 2013-04-02

http://www.microsoft.com/whdc/hcl/default.mspx 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).

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 Oracle home directory, and the 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 four 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 132].

All disk controllers must be able to support hardware-based RAID.

CAUTION

You cannot use a host with a domain controller as an cluster node.

End of: HA (MSCS) |

Hardware and Software Requirements

The 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 MS 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 versions for your SAP product and database, see the Product Availability Matrix (PAM) at:

http://service.sap.com/pam.

3 Planning


2013-04-02 CUSTOMER 25/178
http://www.microsoft.com/whdc/hcl/default.mspxhttp://www.saponwin.comhttp://service.sap.com/pam

Hardware Requirements

Hardware Requirement Requirement How to Check

Minimum disk space

Database software:2 to 5 GB

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

Database instance (not including paging file):2 GB

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

Primary application server 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. Additional application server instance (not

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

NOTE

The additional application server instance is optional in a non-HA system, but mandatory in an HA system.

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

To check disk space: Windows Server 2012:

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

2. Check the value SizeRemaining of the disk you want to install on.

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

Administrative Tools StorageComputer Management Disk

Management .2. Right-click the drive and

choose Properties. Windows Server 2003:

1. Choose Start All ProgramsAdministrative Tools Computer

Management Disk Management .

2. Right-click the drive and choose Properties.

Minimum RAM All instances, except SAP host agent, and diagnostics agent:4 GB

SAP host agent:0.5 GB

Diagnostics agent:1 GB

To check RAM: Windows Server 2012:

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

Win32_ComputerSystem

Windows Server 2008 (R2) or Windows Server 2003:

3 Planning


26/178 CUSTOMER 2013-04-02


Choose Start Control PanelSystem .

NOTE

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

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

If you want to install usage type BI Java, see SAP Note 1736008 for current information on hardware sizing.End of: BI Java Components (BI-Java) |

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

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

System .

NOTE

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

NOTE

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


NOTE

You must adjust the size of the paging file on all cluster nodes.

End of: HA (MSCS) |

3 Planning


2013-04-02 CUSTOMER 27/178
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1736008&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1518419&_NLANG=en&_NVERS=0


Processing 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 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 Requirements

Software Requirement Requirement How to Check

Windows operating system

64-bit version of one of the following Windows Server Editions: Windows Server 2012:

Windows Server Standard Edition Windows Server Datacenter

Edition Windows Server 2008 (R2) or Windows

Server 2003: Only valid for: non-HA |

Windows Server Standard EditionEnd of: non-HA |

Windows Server Enterprise Edition

Windows Server Datacenter Edition

Windows Server 2008 (R2) only:Windows Server 2008 (R2) for Itanium-Based Systems Edition

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.

CAUTION

Make sure that you install the English language pack so that your

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 a

3 Planning


28/178 CUSTOMER 2013-04-02
http://service.sap.com/pamhttp://service.sap.com/pam

Software Requirement Requirement How to Check

support requests can be handled quickly.

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

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

dcladm, where Clustername=sapprdcl.

End of: HA (MSCS) |

Database software Database instance: Database server software for Oracle 11g Current Oracle patches, if available. Only valid for: HA (MSCS) |

Oracle Fail Safe softwareEnd of: HA (MSCS) |

CAUTION

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

3.3 Basic SAP System Installation Parameters

The 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:

TypicalIf you choose Typical, the installation is performed 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 Master password JCE Unlimited Strength Jurisdiction Policy files archive (only prompted if you install usage

type Adobe Document Services)

SAP system profile directory only for systems with instances on separate hosts UME ConfigurationIf you want to change any of the default settings, you can do so on the Parameter Summary screen.

Custom

3 Planning


2013-04-02 CUSTOMER 29/178
http://service.sap.com/pamhttp://service.sap.com/pam

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.

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 SAP system installation 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 Installation Parameters

Parameters Description

Unicode System A Java standalone system is always a Unicode system.

SAP System ID The SAP system ID identifies the entire SAP system.The installer prompts you for the when you execute the first installation option to install a new SAP system.If there are further installation options to be executed, the installer prompts you for the profile directory. For more information, see the description of the parameter SAP System Profile Directory.

EXAMPLE

This prompt appears when you install the central services instance, which is the first instance to be installed in a distributed system.

CAUTION

Choose your SAP system ID carefully. Renaming is difficult and requires you to reinstall the SAP system.

Make sure that your SAP system ID: Is unique throughout your organization. Do not use an existing

when installing a new SAP 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 an additional application server instance, make sure that no gateway instance with the same SAP System ID (SAPSID) exists in your SAP system landscape.

3 Planning


30/178 CUSTOMER 2013-04-02


Instance Number of the SAP System

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

CAUTION

Do 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

\\\sapmnt

\ \ SYS\ profile

The installer retrieves parameters from the SAP system profile directory of an existing SAP system.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 an additional application server instance to an existing SAP system. See also the description of the parameters SAP System ID and Database ID.

Destination drive Base directory for the SAP system.

NOTE

If you install a subsequent SAP system, the saploc share already exists and you cannot select the installation drive. The installer uses the installation drive where the saploc share points to.

Master Password Common password for all users that are 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, the installer creates them with the common master password (see table Operating System Users). In this case, make sure that the master password meets the requirements of your operating system.

Java users(for example Administrator)

Secure Store key phraseFor more information, see table Key Phrase for Secure Store Settings.

NOTE

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

3 Planning


2013-04-02 CUSTOMER 31/178

Parameters DescriptionPassword 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) It must not begin with a digit nor an underscore It can contain the following characters: _, #, $, a-z, A-Z, 0-9 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 CAUTION

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

Port Number of the SAP Message Server:If you do not specify a value, the default port number is used.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(TM) Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files Archive

If you want to install usage type Adobe Document Services, make sure that you download the unlimited version of the JCE Jurisdiction Policy Files 6 archive. For more information about where to download it, see SAP Note 1240081.

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, SAP creates the following users:

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

SAPServiceThis user is the Windows account to run the SAP system. It 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 although it is not 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 102]. For security

3 Planning


32/178 CUSTOMER 2013-04-02

Parameters Descriptionreasons, however, SAP strongly recommends you to create this user as a local user.

admThe diagnostics agent user adm is used to manage the diagnostics agent system. It is created on the primary application server instance host and on every additional application server instance host. The installer creates this user by default as a local user although it is not 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 102]. For security reasons, however, SAP strongly recommends you to create this user as a local user.

SAPServiceThis user is the Windows account to run the diagnostics agent system.

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 the password of these users is the same as the master password.

CAUTION

Make sure that you have the required user authorization [page 46] for these accounts before you start the installation.

UME Configuration The installer prompts you for how to configure the UME during the input phase of the installation.You can choose between the following options: Use Java Database

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.

Use ABAPIf 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.You must have created the required users manually on the external ABAP system.For more information, see Preparing User Management for an External ABAP System (Optional) [page 49].

For more information about supported UME data sources and change options, see SAP Note 718383.

NOTE

If you want to use LDAP as data source, choose Use Java Database and change to LDAP after the installation has finished.

3 Planning


2013-04-02 CUSTOMER 33/178
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=718383&_NLANG=en&_NVERS=0


If you want to use the User Management Engine for an existing ABAP system, choose Use ABAP.

If you install a PI system, you have the following options: If you want to install non-central Advanced Adapter Engine

(AAE) as optional standalone unit for a PI dual-stack installation, you have the following options: Use External ABAP System: This sets up the ABAP-based User

Management Engine on the Integration Server system. Use Java Database: This sets up "local" user management on the

system of the non-central AAE. If you want to install non-central Advanced Adapter Engine

(AAE) as optional standalone unit for an Advanced Adapter Engine Extended (AEX) installation or a Process Integration and Orchestration Package (PI-CP) installation, you have to choose Use Java Database. This sets up local user management on the system of the non-central AAE.

Using the Java Database:

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

Guest User The installer sets the user name Guest and the master password by default.The guest user is a user for anonymous access.

Using an External ABAP System Parameters for the ABAP Connection:

Application Server Instance Number

This is the instance number on the application server of the central ABAP system to which you want to connect the Application Server Java.To find out the number on the host of the primary application server instance, look under the SAP directory usr/sap//DVEBMGS. The value is the number assigned to the SAP system.

Application Server Host This is the host name of the relevant application server instance.To find out the host name, enter hostname at the command prompt of the host running the primary application server instance.

Communication User This is the name and password of the existing ABAP communication user. You must have created this user manually on the external ABAP system.

Using an External ABAP System Parameters for the Application Server Java Connection:

Administrator User This is the name and password of the administrator user that you created on the external ABAP system.

Administrator Role The role SAP_J2EE_ADMIN must exist on the external ABAP system.

Guest User This is the name and password of the guest user that you created on the external ABAP system.The guest user is a user for anonymous access.

Guest Role The role SAP_J2EE_GUEST must exist on the external ABAP system.

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.

3 Planning


34/178 CUSTOMER 2013-04-02

Parameters DescriptionThe 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

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

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.

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

SAP System Database Installation Parameters


Database ID The identifies the database instance. The installer prompts you for the when you are installing the database instance.

3 Planning


2013-04-02 CUSTOMER 35/178

Parameters DescriptionThe can be the same as the .

CAUTION

Choose your database ID carefully. Renaming is difficult and requires you to reinstall the SAP system.

If you want to install a new database:Make sure that your database ID: Is unique throughout your organization Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs:

ADD ADM ALL AMD AND ANY 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

MCOD only: If you want to use an existing database system, enter exactly the database ID of the existing database to which you want to add the system.For more information, see Installation of Multiple Components in One Database [page 98].

Database schema, Password The Java database schema is named SAPDB.Default name is SAPSR3DB.

RECOMMENDATION

Choose a that is different from your .It might cause problems when you copy a system where is the same as , and the database-specific method used for the copy does not allow you to rename the database schemas. In certain situations, you might create a system copy with a new , but where the database schema has the old . This is not a technical problem, but might confuse the system administrator.

Oracle parameters Oracle home SAPDATA drives Drives for redolog and archives (oraarch)

Oracle Listener Name, Oracle Listener Port, Oracle Listener Domain

If you install the database instance on a host where no other Oracle database is installed, you normally do not have to change the default values for Listener Name and Listener Port.

If you install the database instance on a host where another Oracle database is already installed you have the following options: If you install it in the same Oracle home, you use the default values for

Listener Name and Listener Port. If you install it in a different Oracle home, you specify an unused Listener

Name and Listener Port for the new Oracle Listener. All additional application server instances of an SAP system must use the

same Listener Port than the database instance. The default domain in the network configuration files is WORLD.

3 Planning


36/178 CUSTOMER 2013-04-02

Diagnostics Agent Parameters

The diagnostics agent is installed automatically with the SAP system.


System ID of 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.

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 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 95].The same restrictions apply as in Instance Number of the SAP System (see above).

System Landscape Directory (SLD) Destination

You can choose between the following options: Register in existing central SLD

The installer only prompts you for the parameters listed below in this table if you select this option.

RECOMMENDATION

We recommend that you select this option. No SLD destination

If you select this option: You have to configure the SLD destination for the diagnostics agent

manually after the installation with the installer has finished. The installer does not prompt you for the parameters listed below in

this table.

System Landscape Directory (SLD):HTTP Host

The host name of the SLD

System Landscape Directory (SLD):

The HTTP port of the Java system where the SLD is installed. The following naming convention applies:

3 Planning


2013-04-02 CUSTOMER 37/178

Parameters DescriptionHTTP Port 500.

EXAMPLE

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

System Landscape Directory (SLD) :Data Supplier User and password

You have to enter the existing SLD Data Supplier User and the password of the central SLD.

3.4 Domain or Local Installation

Before you install the SAP system, you have to decide whether you want to perform a domain or

local installation, since this affects how the user account information is stored and accessed.

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 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 Microsoft Failover Clustering.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 (standard 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 Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP NetWeaver at:


More Information

Required User Authorization for Running the Installer [page 46]

3 Planning

3.4 Domain or Local Installation

38/178 CUSTOMER 2013-04-02

3.5 Distribution of SAP System Components to Disks

When you install the SAP system, the main directories required for the system are automatically created.

However, during the installation procedure, the installer prompts you to enter drive letters for the

main components of the system. This gives you the opportunity to distribute components to disks in

the system as you wish. How you do this significantly affects system throughput and data security, and

must therefore be carefully planned. The best distribution depends on your specific environment and

must take into consideration factors such as the size of the components involved, security requirements,

and the expected workload.

When you work out the assignment of components to disks, you first need to get an overview of the

main components and their corresponding directories. Then, on the basis of sample configurations

and the recommendations provided in this documentation, you can decide which assignment is best

for your particular system.

SAP systems are normally installed on RAID arrays that ensure data redundancy. This documentation

therefore focuses on RAID subsystems and drives.

Minimal Configuration

The following figure illustrates an example for a disk configuration for a small test or demo system.

Since security and performance play a less crucial role in this type of system, many different

configurations are feasible.

CAUTION

Use the illustrated configuration exclusively for test or demo systems. It is unsuitable for

production systems because it only minimally satisfies security and performance requirements.

3 Planning


2013-04-02 CUSTOMER 39/178

Figure 5: Configuration for Test or Demo System

Distribution of Database Directories to Disks

Disk Directories

Disk 1 \ORACLE\\1120\ORACLE\\origlogA

\ORACLE\\origlogB

\ORACLE\\sapdata1

\ORACLE\\sapdata2

Disk 2 \ORACLE\\mirrlogA\ORACLE\\mirrlogB

\ORACLE\\sapreorg

\ORACLE\\saptrace

\ORACLE\\saparch

\ORACLE\\sapbackup

\ORACLE\\sapcheck

\ORACLE\\sapdata3

\ORACLE\\sapdata4

Disk 3 \ORACLE\\oraarch

Comments

The configuration ensures that no data can be lost, but the process for recovering a damaged database is complicated and time-consuming.

The redo logs and database files are located on the same disks. This means that a single disk failure can result in the loss of both the redo logs and database data.

3 Planning


40/178 CUSTOMER 2013-04-02

The I/O-intensive redo logs are on the same disk volumes as the data files. This can impede performance.

An equally good alternative would be to simply place all components on a single RAID 5 array.

3.6 SAP System Transport Host

The transport host contains the transport directory used by the SAP transport system to store transport

data and change SAP system information, such as software programs, data dictionary data, or

customization data. If you have several SAP systems, they are usually organized in transport domains.

In most cases, all SAP systems in a transport domain have a common transport directory.

When you install an SAP system, you have to decide which transport host and directory you want to

use for your SAP system:

Use the transport directory that the installer creates during the installation of the SAP system by default on the global host:

The installer by default creates the transport directory on the global host in \usr\sap\trans.

Use a transport directory located on a host other than the default host: You can use an existing transport directory and host in your SAP system landscape. You can set up a new transport directory on a different host.In either case, you must prepare this host for use by the new SAP system [page 48].

More Information

SAP Directories [page 95]

3.7 Multiple Oracle Homes

The Oracle database software is installed in a directory structure which is referenced as Oracle Home.

Before you install your Oracle database software, you need to decide whether you want to set up a

single or multiple Oracle Homes as this influences the installation procedure.

If you install more than one database instance on the same host you have the following options:

You use a single Oracle Home You can use a single Oracle Home, if you use the same Oracle database version on one host

for different database instances.

With a single Oracle Home, you have to install the database software only once. With a single Oracle Home, you cannot administer your databases independently.

You use multiple Oracle Homes If you use multiple Oracle Homes, you must set up one Oracle Listener for each Oracle Home.

Each listener must have a different TCP/IP port number.

With multiple Oracle Homes, you can administer your databases independently.

3 Planning

3.6 SAP System Transport Host

2013-04-02 CUSTOMER 41/178

Multiple Oracle Homes are necessary, if you need to install different Oracle databases versions on the same host.

Only valid for: HA (MSCS) |Windows Server 2008 (R2) and higher:

Multiple Oracle Homes are not supported in a Microsoft failover cluster.End of: HA (MSCS) |

More Information

Setting Up Multiple Oracle Homes [page 64]

3 Planning

3.7 Multiple Oracle Homes

42/178 CUSTOMER 2013-04-02

4 Preparation

4.1 Preparation Checklist

This section includes the preparation steps that you have to perform for the following installation

options:

Standard, distributed, or high-availability system Additional application server instanceDetailed information about the steps is available in the relevant section.

Standard, Distributed, or High-Availability System

NOTE

In a standard system, all mandatory instances are installed on one host. Therefore, if you are

installing a standard system, you can ignore references to other hosts.

1. Windows Server 2008 (R2) or higher: You disable the Windows Server firewall [page 44] on each host.

2. You perform basic preparations on Windows [page 44].

3. You check that you have the required user authorization for running the installer [page 46].

4. If required, you set up virtual host names [page 48].

5. If required, you prepare the SAP system transport host [page 48] for your SAP system.

6. If you need to configure the User Management Engine (UME) of Application Server Java for the

user management of a separate ABAP system, you have to

prepare user management for an external ABAP System [page 49].

7. You make sure that the required installation media [page 52] are available on each host.

8. Only valid for: HA (MSCS) |

To install a high-availability system with Microsoft Failover Clustering, you also perform the HA-

specific preparation steps [page 123].End of: HA (MSCS) |

9. You can continue with Installation [page 57] .

Add

inst sap nw java 7.3

Documents