Inst Guide Baselinebrv1606 Sybase Nw73

Installation GuideSAP NetWeaver ABAP on Windows: SAP Sybase Adaptive Server EnterpriseUsing Software Provisioning Manager 1.0

Valid for Systems Based On:■ SAP NetWeaver 7.3■ SAP NetWeaver 7.3 including SAP Enhancement Package 1■ SAP NetWeaver 7.4

Target Audience ■ System administrators ■ Technology consultants

PUBLICDocument version: 1.2 – 2013-07-15

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.

2/164 PUBLIC 2013-07-15

Document History

CAUTION

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

You can find the latest version on SAP Service Marketplace http://service.sap.com/

instguides.

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

Version Date Description

1.2 2013-07-15 Updated Version

1.1 2012-09-25 Updated Version

1.0 2012-08-06 Initial Version

2013-07-15 PUBLIC 3/164

http://service.sap.com/instguides


Table of Contents

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

1.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.4 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

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

2.1 Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2 Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3 High Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.4 Additional Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.5 Central Services Instance for ABAP Separate from Existing Primary

Application Server Instance of an Upgraded System . . . . . . . . . . . . . . . . . . . . 17

2.6 SAP Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.2.1 Running the Prerequisite Checker in Standalone Mode

(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2.2 Requirements for a Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.2.3 Requirements for a Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.2.4 Requirements for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.5 Requirements for the Additional Application Server Instance . . . . . . . . . . . . . 30

3.2.6 Requirements for the SAP Host Agent as a Separate Installation . . . . . . . . . . . 32

3.3 Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.4 Domain or Local Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.5 Setup of Database Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.6 SAP Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4/164 PUBLIC 2013-07-15

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

higher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.3 Performing Basic Windows Preparation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . 46

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

4.5 Preparing the SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.6 Installing the SAP Front-End Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4.7 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.2 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.3 Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5.3.1 How to Avoid Automatic Logoff by the Installer . . . . . . . . . . . . . . . . . . . . . . . 61

5.3.2 Interrupted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.3.3 Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.3.4 Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.3.5 Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.3.6 Entries in the Services File Created by the Installer . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

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

6.3 Configuring User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

6.4 Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

6.5 Creating Symbolic Links on Windows Server 2008 R2 and higher for

Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

6.6 Configuring Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . . . . 75

6.7 Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

6.8 Performing Post-Installation Steps for the ABAP Application

Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

6.9 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

6.10 Enabling the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

6.11 Performing a Full System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

6.12 Configuring the Connection to a Standard System Landscape

Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

6.13 Performing the Client Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

6.14 Post-Installation Steps for the SAP Host Agent . . . . . . . . . . . . . . . . . . . . . . . . . 84

2013-07-15 PUBLIC 5/164

6.15 Accessing Configuration Documentation in SAP Solution

Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Chapter 7 Disaster Recovery Setup with SAP Sybase Replication Server . . . . . . . . . 87

7.1 Implementation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7.3 Installing the Replication Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

7.3.1 Materializing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.3.1.1 Materialize the Master Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.3.1.2 Materialize the “saptools” Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

7.3.1.3 Materialize the SAP Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

7.3.1.4 Manual Materialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

7.3.1.4.1 Using Database Dump and Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

7.3.1.4.2 Using Transaction Dump and Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.3.1.4.3 Using Snapshot Materialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.4 Starting and Stopping DR Agent and Replication Server . . . . . . . . . . . . . . . . . 94

7.4.1 Connecting to the DR Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

7.4.2 Starting the DR Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.4.3 Stopping the DR Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.4.4 Starting the Replication Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.4.5 Stopping the Replication Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.5 Removing the Replication Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.6 Integration of SAP Sybase Replication Server into an OS Cluster

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

7.6.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

7.6.2 Defining Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

7.6.2.1 Defining the SAP Sybase Replication Server Resource . . . . . . . . . . . . . . . . . . . 98

7.6.2.2 Defining the DR Agent Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

7.7 Defining Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

7.8 Defining Node Failure Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

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

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

8.2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

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

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

8.2.1.2 Enqueue Replication Server in a Microsoft Failover Cluster . . . . . . . . . . . . . . 107

6/164 PUBLIC 2013-07-15

8.2.2 Distribution of SAP System Components to Disks for Failover

Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

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

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

8.2.5 Obtaining IP Addresses for a High-Availability System . . . . . . . . . . . . . . . . . . 114

8.3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

8.3.1 Assigning Drive Letters for MSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

8.3.2 Mapping Host Names to IP Addresses for High-Availability . . . . . . . . . . . . . . 116

8.4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

8.4.1 Configuring the First Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

8.4.2 Installing the Database on the First Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

8.4.3 Configuring the Database on the Additional Node . . . . . . . . . . . . . . . . . . . . . 119

8.4.4 Configuring the Additional Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

8.4.5 Installing the Central Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

8.4.6 Installing the Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

8.5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

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

8.5.1.1 Checking the Status of the Enqueue Replication Server with

ENSMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

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

8.6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

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

8.6.2 Starting and Stopping the SAP System in a Failover Cluster

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Chapter 9 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

9.1 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

9.2 Checking and Changing the Paging File Settings on Windows Server

2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

9.3 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

9.4 Installing the SAP Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

9.5 Splitting Off a Central Services Instance for ABAP from an Existing Primary

Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

9.6 Starting and Stopping the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

9.7 Configuring the Windows Server 2008 R2 Firewall . . . . . . . . . . . . . . . . . . . . . 145

9.8 Implementing Single Sign-On with Microsoft Kerberos SSP for Your SAP

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

9.9 SAP System Security on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

2013-07-15 PUBLIC 7/164

9.10 Automatic Creation of Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . . 150

9.11 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

A.1 Using PowerShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

A.2 Online Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

8/164 PUBLIC 2013-07-15

1 Introduction

This installation guide describes how to install an SAP NetWeaver ABAP system using the installation

tool software provisioning manager 1.0 (“installer” for short). This guide applies to the following

releases:

Product Release

SAP NetWeaver ■ SAP NetWeaver 7.3 ■ SAP NetWeaver 7.3 including enhancement package 1 ■ SAP NetWeaver 7.4

SAP ERP ■ SAP Enhancement Package 7 for SAP ERP 6.0 on SAP NetWeaver 7.4

SAP CRM ■ SAP Enhancement Package 3 for SAP CRM 7.0 on SAP NetWeaver 7.4

SAP SRM ■ SAP Enhancement Package 3 for SAP SRM 7.0 on SAP NetWeaver 7.4

SAP SCM ■ SAP Enhancement Package 3 for SAP SCM 7.0 on 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.

Constraints

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 7.3 / 7.3 including Enhancement

Package 1 / SAP NetWeaver 7.4.

■ ABAP system refers to 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.

1 Introduction

2013-07-15 PUBLIC 9/164

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

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 reason we are continuing to use the abbreviation MSCS in the profile bars

and in some sections of this guide.End of: HA (MSCS) |

1.1 Before You Start

Make sure that you have read the Master Guide for your 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 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:

Document Internet Address

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 NetWeaver 7.4 http://service.sap.com /installNW74

Master Guide - SAP Enhancement Package <Number> for SAP ERP 6.0

http://service.sap.com/ erp-ins SAP ERP 6.0 Planning

Master Guide (Including Upgrade Information) - SAP Supplier Relationship Management 7.0 <Including SAP Enhancement Package <Number>>

http://service.sap.com/ srm-inst <Your release and enhancement package>

Master Guide (Including Upgrade Information) - SAP Customer Relationship Management 7.0 <Including SAP Enhancement Package <Number>>

http://service.sap.com/ crm-inst <Your release and enhancement package> Plan

Master Guide SAP Supply Chain Management 7.0 <Including SAP Enhancement Package <Number>> Powered by SAP NetWeaver

http://service.sap.com/instguides SAP Business Suite Applications SAP SCM <Your release and enhancement package>

Master Guide

1.2 New Features

The table below provides an overview of the new features.

1 Introduction

1.1 Before You Start

10/164 PUBLIC 2013-07-15


http://service.sap.com/installNW73



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

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

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


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 51] 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 (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_<Version>_U_<Your Operating System Platform>) 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 34].

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.Systems based on SAP NetWeaver 7.3 and higher: Windows

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

1748888 SYB: Inst. Systems Based on NW 7.3 and higher: SAP Sybase ASE

Software Provisioning Manager 1.0: SAP NetWeaver 7.3 and higher

1554717 Planning Information for SAP on Sybase ASE

SAP release information for customers deploying SAP on Sybase ASE

1 Introduction

1.3 SAP Notes for the Installation

2013-07-15 PUBLIC 11/164

http://service.sap.com/releasenotes


http://service.sap.com/notes






SAP Note Number Title Description

1619967 SYB: DBA Cockpit Correction Collection SAP Basis 7.31

The implementation of SAP Note 1619967 directly after the installation is strongly recommended.

1245200 ICF Service Activation for Web Dynpro DBA

The Web browser-based version of the DBA Cockpit does not start correctly.

1585981 SYB: Backup Instructions for SAP on Sybase ASE

Information about backup and recovery

1650511 SYB: High Availability Offerings with Sybase ASE

Information about high availability cluster solutions for Sybase ASE

1407532 Release Restrictions for SAP NetWeaver 7.3 EHP1

Customer information on restrictions in the production use of certain functions

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

789220 Support Package level for SAP NetWeaver Installations/Upgrades

Information about the Support Package levels and kernel patch levels contained in the current SAP NetWeaver release

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

http://help.sap.com/nw73 Application Help Function-Oriented View: English

■ SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1:


■ SAP systems based on SAP NetWeaver 7.4:


1 Introduction

1.4 Accessing the SAP Library

12/164 PUBLIC 2013-07-15











http://help.sap.com/nw73



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 13] (formerly known as central system)

■ Distributed system [page 14]

■ Only valid for: HA (MSCS) |

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

■ You can install one or more additional application server instances [page 15] to an existing standard or

distributed system.

■ You can split off a central services instance for ABAP from an existing primary application server instance of an upgraded

system [page 17].

■ You can install a host agent separately [page 18].

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 for ABAP (ASCS instance)

■ Enqueue replication server instance (ERS instance) for the ASCS instance (optional)

■ Database instance (DB)

■ Primary application server instance (PAS)

Additionally you can install one or more additional application server instances. For more information,

see Additional Application Server Instance [page 15].


2.1 Standard System

2013-07-15 PUBLIC 13/164

Figure 1: Standard ABAP 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.

NOTE

We strongly recommend installing the ASCS instance on the same host as the primary application

server. The installation of the ASCS instance on a separate host is reserved for high-availability

configurations on Windows that are not using Microsoft Failover Clustering.

A distributed system consists of the following instances:

■ Central services instance for ABAP (ASCS instance)

■ Enqueue replication server instance (ERS instance) for the ASCS instance (optional)

■ Database instance (DB)

The ABAP 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 15].


2.2 Distributed System

14/164 PUBLIC 2013-07-15

Figure 2: Distributed ABAP 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 in MSCS [page 104].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 40].


2.3 High Availability System

2013-07-15 PUBLIC 15/164

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 ABAP System

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

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

16/164 PUBLIC 2013-07-15

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

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


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 104].End of: HA (MSCS) |

2.5 Central Services Instance for ABAP Separate from Existing Primary Application Server Instance of an Upgraded System

The central services instance for ABAP (ASCS instance) consists of the essential enqueue and message

system services only. This has been standard for the Java stack and is now also standard for the ABAP

stack.

The benefit of having a separate ASCS instance is mainly in the area of high-availability. This approach

concentrates the possible single points of failure of a system into a single instance and, therefore, restricts

failure to a single instance.

Every newly installed SAP system based on SAP NetWeaver 7.3 and higher is automatically installed

with an ASCS instance, even if you install all SAP system instances on one host (standard system).


2.5 Central Services Instance for ABAP Separate from Existing Primary Application Server Instance of an Upgraded System

2013-07-15 PUBLIC 17/164

However, if you upgraded your SAP system from a release based on a SAP NetWeaver release lower

than 7.3, your SAP system might not yet have a separate ASCS instance.

The section Splitting Off an ABAP Central Services Instance from an Existing Primary Application Server Instance [page

142] describes how you can move the message server and the enqueue work process from an existing

primary application server instance to a newly installed central services instance for ABAP (ASCS

instance).

2.6 SAP Host Agent as a Separate Installation

Using the host agent, you can centrally monitor any host with the Alert Monitor or the Landscape

Virtualization Manager. In addition, the host agent is used by the Landscape Virtualization Manager

for starting, stopping, and relocating SAP instances and databases.

The host agent is automatically installed during the installation of all new SAP system instances based

on SAP NetWeaver 7.2 or higher. You only need to install a host agent separately in the following cases:

■ You want to manage a host that does not have an SAP instance or component.

■ You have upgraded your SAP system to SAP NetWeaver 7.2 or higher.

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


2.6 SAP Host Agent as a Separate Installation

18/164 PUBLIC 2013-07-15

3 Planning

3.1 Planning Checklist

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

■ Standard System

■ Distributed System

■ Only valid for: HA (MSCS);HA (UNIX) |

High-Availability SystemEnd of: HA (MSCS);HA (UNIX) |

■ Additional application server instance

Detailed information about the steps is available in the relevant chapter.

Prerequisites

1. You have planned your SAP system landscape according to the Master Guide at :

http://service.sap.com/installnw73


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

Only valid for: HA (MSCS);HA (UNIX) |

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 20] on each host.

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

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

4. You carefully plan the setup of your database.

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

6. You can continue with Preparation.End of: HA (MSCS);HA (UNIX) |

Only valid for: non-HA |

Standard System or Distributed System

NOTE



3 Planning

3.1 Planning Checklist

2013-07-15 PUBLIC 19/164



1. You check the hardware and software requirements [page 20] on each host.

2. You plan how to set up user and access management.


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

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

6. You can continue with Preparation.End of: non-HA |

Additional Application Server Instance

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

to install one or more additional application server instances.


3. You can now continue with Preparation.

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.

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 in one of two modes:

● Standalone mode (optional) before the installation process

For more information, see Running the Prerequisite Checker Standalone [page 21].

● Integrated in the installer (mandatory) during the installation process

For more information, see Running the Installer [page 57].

NOTE

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

■ The hardware and software requirements checklists for:

● Standard system [page 22]

● Distributed system [page 24]

3 Planning


20/164 PUBLIC 2013-07-15


http://service.sap.com/pam


● Only valid for: HA (MSCS) |

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

● Additional application server instance [page 30]

● Host agent as a separate installation [page 32]

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.

■ You contact your hardware vendor, who can analyze the load and calculate suitable hardware

sizing depending on:

● The set of applications to be deployed

● How intensively the applications are to be used

● The number of users

3.2.1 Running the Prerequisite Checker in Standalone Mode (Optional)

Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check the

hardware and software requirements for your operating system (OS) and the SAP instances.

RECOMMENDATION

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

NOTE

When installing your SAP system, the installer automatically starts the Prerequisite Checker and

checks the hardware and software requirements in the background.

Prerequisites

■ You have prepared the installation master DVD on the required installation host [page 51].

Procedure

1. You start the installer [page 57].

2. On the Welcome screen, choose <Your SAP product> Software Life-Cycle Options Additional Preparations

Prerequisites Check .

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

3 Planning


2013-07-15 PUBLIC 21/164

http://service.sap.com/sizing

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.

4. 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 a Standard System

If you want to install a standard system, where all instances reside on one host, this host must meet

the following requirements:

NOTE

■ The listed values are sufficient for development systems or quality assurance systems but

not for production systems.

■ For up-to-date information on the released and supported operating system and database

versions for your SAP product and database, see the Product Availability Matrix (PAM) at

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

Hardware Requirements for a Standard System

Hardware Requirement Requirement How to Check

Minimum disk space ■ SAP system files (not including paging file):5 GB (x64)

■ Database InstanceFor more information about the required disk space, see SAP Note 1748888.

NOTE

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

■ 4.3 GB of temporary disk space for every required installation medium that you have to copy to a local hard disk

To check disk space:1. Windows Server 2012:

Open PowerShell in elevated mode, and enter the following command: get-volume.Check the value SizeRemaining of the disk you want to install on.

2. Windows Server 2008 R2:Choose Start All Programs

Administrative Tools StorageComputer Management Disk

Management .3. Right-click the drive and choose

Properties.

Minimum RAM 8 GB To check RAM:1. Windows Server 2012:

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

3 Planning


22/164 PUBLIC 2013-07-15



Hardware Requirement Requirement How to CheckGet-wmiobject.Win32_ComputerSystem

2. Windows Server 2008 R2:Choose Start Control Panel

System .

NOTE

Windows 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:1. Windows Server 2012:

For more information, see Checking and Changing the Paging File Settings on Windows Server 2012.

2. Windows Server 2008Choose Start Control Panel

System .

NOTE


3. Windows Server 2008 R2:Choose Advanced system settings.

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.

Suitable backup system - –

Software Requirements for a Standard System

Software Requirement Requirement How to Check

Windows operating system

■ English 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)

CAUTION

◆ Windows Server 2008 R2 for Itanium-based systems editions is not supported.

To check your Windows version:1. Windows Server 2012:

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

Win32_OperatingSystem |

select caption

2. Windows Server 2008

3 Planning


2013-07-15 PUBLIC 23/164



◆ Windows Server 2008 Standard Edition (for non-HA installations)

◆ Windows Server 2008 Enterprise Edition ◆ Windows Server 2008 Datacenter

Edition

NOTE

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

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

Choose Start All ProgramsAccessories Command

Prompt3. Enter the command winver

3.2.3 Requirements for a Distributed System

This section provides information about the hardware and software requirements in a distributed

system, where the SAP instances can reside on different hosts.

The tables show the requirements for the:

■ Database instance

■ Central instance

■ Additional application server instance (optional)

NOTE



■ If you install several SAP instances on one host, you need to add up the requirements.

■ For up-to-date information on the released and supported operating system versions for your

SAP product and database, see the Product Availability Matrix (PAM) at http://

service.sap.com/pam.

Hardware Requirements for a Distributed System


Minimum disk space ■ Database instanceFor more information about the required disk space, see SAP Note 1748888.

NOTE

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




Administrative Tools Storage

3 Planning


24/164 PUBLIC 2013-07-15







■ Central instance (not including paging file):5 GB (x64) ● In addition you require 4 GB

(x64),per additional platform. ● In addition you require 1.5 GB for

the diagnostics agent ■ Additional application server instance

(optional) (not including paging file):2.5 GB (x64)

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

Computer Management Disk Management .

3. Right-click the drive and choose Properties.

Minimum RAM 8 GB To check RAM:1. Windows Server 2012:

Open PowerShell in elevated mode, and enter the following command:Get-wmiobject.Win32_ComputerSystem

2. Windows Server 2008 (R2)Choose Start Control Panel

System .

NOTE


Paging file size For more information, see SAP Note 1518419.




System .

NOTE





3 Planning


2013-07-15 PUBLIC 25/164


Hardware Requirement Requirement How to CheckNOTE


Suitable backup system –

Software Requirements for a Distributed System




◆ Windows Server Standard Edition ◆ Windows Server Datacenter Edition

● Windows Server 2008 R2

CAUTION


◆ Windows Server 2008 R2 Standard Edition

◆ Windows Server 2008 R2 Enterprise Edition

◆ Windows Server 2008 R2 Datacenter Edition

CAUTION

Do not use any other locales than en_US. ■ For any version of Windows Server, you need the

latest supported service pack.



Win32_OperatingSystem |

select caption

2. Windows Server 2008Choose Start All Programs

Accessories Command Prompt

3. Enter the command winver


3.2.4 Requirements for a High-Availability System

General Requirements

■ 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 Failover Cluster Validation

Report must not show any warnings and errors.

■ The MSCS nodes of the cluster must be connected by a private and public network:

● The public network enables communication from the MSCS nodes of the cluster to other

resources in the local area network (LAN).

3 Planning


26/164 PUBLIC 2013-07-15

● The private network enables internal communication between the MSCS nodes. In particular,

it enables the Cluster Service running on all MSCS nodes to regularly exchange messages on

the state of the MSCS nodes so that the failure of resources is quickly detected.

■ Each of the MSCS nodes in the cluster must have its own local disks and have access to shared disks

that can be reached by the MSCS nodes via a shared bus.

All software – except the Windows operating system, the database executables, and the MSCS

software – is stored on the shared disks.

One of the shared disks must be used exclusively by the quorum (if a single quorum device cluster

is used) that stores the cluster registry and records information about the state of the cluster.

You require at least six shared disks.

For more information about the distribution of components to local and shared disk, see Distribution

of SAP System Components to Disks for MSCS [page 108].

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

CAUTION

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

Hardware and Software Requirements

The following tables show the hardware and software requirements for the:

■ Central services instance for ABAP (ASCS)

■ Database instance

■ Enqueue Replication Server instance (ERS)

■ Central instance


■ Diagnostics agent

NOTE



■ If you install several SAP instances on one host, you need to add up the requirements.

■ For up-to-date information on the released and supported operating system versions for your



Hardware Requirements for a High-Availability System


Minimum disk space

■ Central services instance for ABAP (ASCS)(not including paging file):5 GB (x64)8 GB (IA64)


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

3 Planning


2013-07-15 PUBLIC 27/164




● In addition you require 4 GB (x64), or 8 GB (IA64) per additional platform.

■ Database instanceFor more information about the required disk space, see SAP Note 1748888.

NOTE

All software – except the Windows operating system, the database executables, and the MSCS software – is stored on the shared disksYou require at least six shared disks.

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

■ Central instance (not including paging file):2.5 GB (x64)5 GB (IA64) ● In addition you require 4 GB (x64), or 8 GB (IA64)

per additional platform. ● In addition you require 1.5 GB for the diagnostics

agent ■ Additional application server instance (not including

paging file):2.5 GB (x64)5 GB (IA64)


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



Management .3. Right-click the disk and choose

Properties.

Minimum RAM

4 GB To check RAM:1. Windows Server 2012:


2. Windows Server 2008 (R2)Choose Start Control Panel

System .

NOTE


Paging file size

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

3 Planning


28/164 PUBLIC 2013-07-15






System .

NOTE





NOTE

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

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

Suitable backup system

–

Software Requirements for a High Availability System




◆ Windows Server Standard Edition

◆ Windows Server Datacenter Edition

● Windows Server 2008 R2 ◆ Windows Server

2008 R2 Enterprise Edition



Win32_OperatingSystem | select caption

2. Windows Server 2008Choose Start All Programs Accessories Command Prompt

3. Enter the command winver

NOTE

Windows Server 2008 R2:You must add the operating system feature Failover Clustering on all MSCS nodes.

3 Planning


2013-07-15 PUBLIC 29/164


◆ Windows Server 2008 R2 Datacenter Edition

CAUTION

Do not use any other locales than en_US.

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

End of: HA (MSCS) |

3.2.5 Requirements for the Additional Application Server Instance

If you want to install an additional application server instance separately, the installation host has to

meet the following hardware and software requirements:

Hardware Requirements for the Additional Application Server Instance


Minimum disk space: ■ Additional application server Instance (not including paging file):2.5 GB







Properties.

Minimum RAM: 8 GB To check RAM:1. Windows Server 2012:


2. Windows Server 2008 (R2)

3 Planning


30/164 PUBLIC 2013-07-15

Hardware Requirement Requirement How to CheckChoose Start Control Panel

System .

NOTE


Paging file size: For more information, see SAP Note 1518419.




System .

NOTE





NOTE



Software Requirements for the Additional Application Server Instance


Windows operating system:




● Windows Server 2008 R2 ◆ Windows Server 2008 R2

Enterprise Edition ◆ Windows Server 2008 R2

Datacenter Edition

1. Windows Server 2012:Open PowerShell in elevated mode, and enter the following command:Get-WmiObject

Win32_OperatingSystem | select

caption


Accessories Command Prompt3. Enter the command winver

3 Planning


2013-07-15 PUBLIC 31/164


Software Requirement Requirement How to CheckCAUTION


CAUTION


3.2.6 Requirements for the SAP Host Agent as a Separate Installation

If you want to install the host agent separately, the installation host has to meet the following hardware

and software requirements:

CAUTION

For up-to-date information on the released and supported operating system versions for your



Hardware Requirements for the SAP Host Agent


Minimum disk space: ■ SAP Host Agent:80 MB







Properties.

Minimum RAM: 40 MB To check RAM:1. Windows Server 2012:


2. Windows Server 2008 (R2)

3 Planning


32/164 PUBLIC 2013-07-15



Hardware Requirement Requirement How to CheckChoose Start Control Panel

System .

NOTE


Paging file size: For more information, see SAP Note 1518419.

To check paging file size: ■ Windows Server 2012:


■ Windows Server 2008 (R2)1. Choose Start Control Panel

System .

NOTE





NOTE



Software Requirements for the SAP Host Agent


Windows operating system:




● Windows Server 2008 R2 ◆ Windows Server 2008 R2

Enterprise Edition ◆ Windows Server 2008 R2

Datacenter Edition

1. Windows Server 2012:Open PowerShell in elevated mode, and enter the following command:Get-WmiObject

Win32_OperatingSystem | select

caption


Accessories Command Prompt3. Enter the command winver

3 Planning


2013-07-15 PUBLIC 33/164


Software Requirement Requirement How to CheckCAUTION


CAUTION


Database software: – –

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:

■ 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

● SAP system profile directory – only for systems with instances on separate hosts.

If you want to change any of the default settings, you can do so on the Parameter Summary screen.

■ Custom

If you choose Custom, you are prompted for all parameters. At the end, you can still change any of

these parameters on the Parameter Summary screen.

NOTE

You cannot change from Custom to Typical mode or from Typical to Custom mode on the Parameter

Summary screen.

The following tables list the basic system parameters that you need to specify before installing your

SAP system:

■ SAP System Parameters

■ SAP System Database Parameters

■ Diagnostics Agent Parameters

For all other installation parameters, use the F1 help in the installer screens.

3 Planning


34/164 PUBLIC 2013-07-15

SAP System Parameters

Parameters Description

SAP System ID <SAPSID>

The SAP System ID <SAPSID> identifies the whole SAP system.The installer prompts you for the <SAPSID> 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 primary application server instance, which is the first instance to be installed in a distributed system.

CAUTION

Choose your SAP system ID carefully. You cannot change the SAP system ID after the installation.

Make sure that your SAP system ID: ■ Is unique throughout your organization. Do not use an existing <SAPSID> 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 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.

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 <nn> of local \usr\sap\<SAPSID> directories.The value <nn> is the number assigned to the instance.For more information, see SAP Directories [page 131].

Master Password Common password for all users created during the installation: ■ Operating system users (for example <sapsid>adm, SAPService<SAPSID>)

CAUTION

If you did not create the operating system users manually before the installation, the installer creates them with the common master password. In this case, make sure that the master password meets the requirements of your operating system and of your database.

■ ABAP users SAP* and DDIC

3 Planning


2013-07-15 PUBLIC 35/164

Parameters DescriptionCAUTION

The installer applies the master password to users SAP*and DDIC for SAP system clients 000 and 001 only, but not to users SAP*, DDIC, and EARLYWATCH in SAP system client 066.Instead, the installer always assigns the following passwords to these users in client 066:SAP*: 06071992EARLYWATCH: supportSee also Ensuring User Security [page 80].

NOTE

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

Password policyThe master password: ■ Must be 8 to 14 characters long ■ Must contain at least one letter in uppercase (A-Z) ■ Must contain at least one letter in lowercase (a-z) ■ Must contain at least one digit (0-9) ■ Must not contain \ (backslash) and " (double quote)Depending on the installation option, additional restrictions might apply (for example, the master password must not contain the name of a Java user created during the installation).

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.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<nn>, where <nn> is the instance number of the ABAP message server instance.The internal message server port uses the parameter rdisp/msserv_internal with default value 39<nn>, where <nn> is the instance number of the ABAP message server instance.For more information about the parameters used for message server ports, see SAP Note 821875.

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:<host name>.<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 Configuring Fully Qualified Domain Names (FQDN) in Performing Post-Installation Steps for the ABAP Application Server [page 76].

3 Planning


36/164 PUBLIC 2013-07-15


Parameters DescriptionEXAMPLE

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

● <sapsid>adm

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

● SAPService<SAPSID>

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

● sapadm

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

● <dasid>adm

This user is dedicated to the diagnostics agent installation with sufficient authorization to manage the agent. It is created on the central instance host and on every additional application server 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.

NOTE

This does not apply if the <dasid>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.

3 Planning


2013-07-15 PUBLIC 37/164


Parameters DescriptionCAUTION

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

SAP System Database Parameters


Database ID <DBSID> The <DBSID> identifies the database instance.The installer prompts you for the <DBSID> when you are installing the database instance. The <DBSID> can be the same as the <SAPSID>.

CAUTION

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

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

ADD ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END

EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT

NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID

SQL SUM SYS TMP TOP UID USE USR VAR

ABAP Database User (SAPSR3)

The user name corresponds to the owner of the database tables.

Database Communication Port

The Sybase database server communication port is used for TCP/IP communication between the database server and remote clients. In a standard system installation and for the database instance in a distributed installation, The installer always proposes 4901 as default.

Other Database Communication Ports

Backup Server: 4902Job Scheduler: 4903

Add sapdata/saplog Directories

Database devices are stored in the following directories:<drive>:\sybase\<DBSID>\sapdata_<n> and<drive>:\sybase\<DBSID>\saplog_<n>

NOTE

Be aware, that the first part, for example \sybase\<DBSID> is definite.

You can create additional sapdata, saplog directories before you start the installer. To distribute database devices, use separate file systems for the directories.

Database Memory 2.1 GB RAM (hard-coded)

Diagnostics Agent Parameters

The diagnostics agent is installed automatically with the SAP system.

3 Planning


38/164 PUBLIC 2013-07-15


System ID of the Diagnostics Agent <DASID>

The installer sets the system ID of the diagnostics agent, <DASID>, 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 <DASID> carefully. Renaming is difficult and requires you to reinstall the diagnostics agent.

Make sure that the <DASID>: ■ Either does not yet exist on the local installation host or does already

exist but was only used for a diagnostics agent installation ■ Consists of exactly three alphanumeric characters ■ Contains only uppercase letters ■ Has a letter for the first character ■ Does not include any of the following, which are reserved IDs:

ADD ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END

EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT

NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID

SQL SUM SYS TMP TOP UID USE USR VAR

Instance Number of the Diagnostics Agent

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<Instance_Number>.For more information, see SAP Directories [page 131].The same restrictions apply as in “Instance Number of the SAP System” (see above).

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

Choose this option to register the diagnostics agent you are installing in an existing SAP System Landscape Directory (SLD) by specifying the SLD connection parameters listed below.

RECOMMENDATION

We recommend that you select this option. ■ No SLD destination

If you select this option, the installer does not prompt you for further SLD parameters.Choose this option if you do not want to register the diagnostics agent of the SAP system you are installing in an existing SAP System Landscape Directory (SLD).You then have to configure the SLD destination for the diagnostics agent manually after the installation with the installer has finished.

3 Planning


2013-07-15 PUBLIC 39/164


SLD HTTP Host (FQN) The fully qualified host name of the SAP system with the System Landscape Directory (SLD)

SLD HTTP Port The HTTP port of the SAP system with the System Landscape Directory (SLD). The following naming convention applies:5<instance_number>00.

EXAMPLE

If 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

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.

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.


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

■ You want to use Single Sign-On.

■ You use a common transport host for several SAP systems running on different computers.

Local Installation

In a local installation, all Windows account information is stored locally on one host and is not visible

to any other hosts in the system.

If the SAP system is to run on a single machine (standard system), you can perform a local installation.

More Information

■ Required User Authorization for Running the installer [page 48]

■ Implementing Single Sign-On with Microsoft Kerberos SSP [page 147]

3 Planning

3.4 Domain or Local Installation

40/164 PUBLIC 2013-07-15

3.5 Setup of Database Layout

NOTE

The 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

as storage consumption of the software components involved, safety requirements and expected

workload.

Required File Systems for SAP Sybase ASE

This section lists the file systems that are required by the SAP Sybase ASE database as well as the

permissions that you have to set.

NOTE

During the installation of your SAP system, you can specify the number and names of the sapdata

directories. The installer allows to place several data or log devices in one sapdata or saplog folder.

You can create additional sapdata and saplog directories before you start the installer. To distribute

database devices, use separate file systems for the directories. To ensure that your SAP system

performs well in a production environment, you have to define and control the distribution of

the database directories to physical disks. You do this by creating separate file systems manually

for the directories listed in the following table:

File System / Logical Volume Description

<drive>:\sybase\<DBSID> Sybase software ($SYBASE)Size: at least 4 GB

<drive>:\sybase\<DBSID>\sybsystem Location for Sybase devices master.dat, sybmgmtdb.dat, sybsysdb.dat, sysprocs.datSize: 1 GB

<drive>:\sybase\<DBSID>\sybtemp Location for Sybase device tempdbdev.datSize: 3 GB

<drive>:\sybase\<DBSID>\saptemp Location for Sybase device saptempdbdev.datSize: 3 GB

<drive>:\sybase\<DBSID>\sapdiag Location for Sybase devices containing the SAP Tools database (datasaptools_1.dat and logsaptools_1.datSize: 3 GB

<drive>:\sybase\<DBSID>\sapdata_<n> Location for Sybase devices containing data (data<DBSID>_1.dat)For more information, see SAP Note 1748888.

<drive>:\sybase\<DBSID>\saplog_<n> Location for Sybase devices containing logs (log<DBSID>_1.dat)For more information, see SAP Note 1748888.

3 Planning

3.5 Setup of Database Layout

2013-07-15 PUBLIC 41/164



NOTE

For information about SAP file systems, see SAP Directories.

File System Permissions

The file systems and logical volumes must have the permissions and owner shown in the following

table. They must be created before starting the installer. The installer then sets the required permissions

and owners.

NOTE

You can create the owners and groups manually if they do not exist. Otherwise, the installer

creates them automatically. For more information, see Creating Operating System Users Manually.

File System / Logical Volume Access Privilege Full Control for User/Group

<drive>:\sybase\<DBSID> syb<dbsid>, Administrators, SYSTEM, SAPLocalAdmin

<drive>:\sybase\<DBSID>\sybsystem syb<dbsid>, Administrators, SYSTEM, SAPLocalAdmin

<drive>:\sybase\<DBSID>\sybtemp syb<dbsid>, Administrators, SYSTEM, SAPLocalAdmin

<drive>:\sybase\<DBSID>\saptemp syb<dbsid>, Administrators, SYSTEM, SAPLocalAdmin

<drive>:\sybase\<DBSID>\sapdiag syb<dbsid>, Administrators, SYSTEM, SAPLocalAdmin

<drive>:\sybase\<DBSID>\sybdata_<n> syb<dbsid>, Administrators, SYSTEM, SAPLocalAdmin

<drive>:\sybase\<DBSID>\saplog_<n> syb<dbsid>, Administrators, SYSTEM, SAPLocalAdmin

Users and Groups

If it has not been created, the installer creates the user syb<dbsid>.

Group:Administrators

3.6 SAP Transport Host

The SAP 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, ABAP 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 in <Drive>:\usr\sap\trans.

■ Use a transport directory located on a host other than the global host (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 50].

3 Planning


42/164 PUBLIC 2013-07-15

More Information

■ SAP Directories [page 131]

■ See the SAP Library:

SAP NetWeaver <Release> Application Help Function-Oriented View: English Solution Life Cycle

Management Software Logistics Change and Transport System Change and Transport System – Overview

3 Planning


2013-07-15 PUBLIC 43/164

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

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



Standard, Distributed or High-Availability System

NOTE



1. If you use Windows Server 2008 R2, you disable the Windows Server 2008 R2 firewall [page 46] on each

host.

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

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

4. If you want to install a high-availability system, you perform switchover preparations.

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

6. You install the SAP frontend software [page 51] on the desktop of the end user.

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

8. Only valid for: HA (MSCS) |

To install a high-availability system with Microsoft Cluster Service (MSCS), you also perform the

MSCS-specific preparation tasks [page 103].End of: HA (MSCS) |

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


You have to perform the following preparations on the host where you install the additional application

server instance:

1. If you use Windows Server 2008 R2, you disable the Windows Server 2008 R2 firewall [page 46] on each

host.



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

4 Preparation

4.1 Preparation Checklist

2013-07-15 PUBLIC 45/164

5. You install the SAP frontend software [page 51] on the desktop of the end user.

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

7. You can continue with Installation [page 55].

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

The Windows firewall – which is turned on by default as of Windows Server 2008 (R2) – is configured

to allow only a small set of Windows-specific inbound IP connections. By default, outbound connections

are not limited to rules and are therefore not restricted by the firewall.

The default firewall settings are valid for the out-of-the-box installation of Windows Server 2008 (R2)

and higher. These settings apply to local policies. For domain policies that override local policies, other

rules might apply.

To avoid any problems with non-configured TCP/IP ports that are used by the SAP system, you need

to disable the firewall on all Windows hosts before you install the SAP system with the installer. We

recommend that you secure network access to the SAP application servers with a real physical firewall

or use a router Access Control List (ACL).

ProcedureOnly valid for: HA (MSCS) |

NOTE

In a high-availability system, you have to disable the firewall on all MSCS nodes.

End of: HA (MSCS) |

■ Windows Server 2012:

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

Set-NetFirewallProfile -enabled false

■ Windows Server 2008 (R2):

1. Choose Start Administrative Tools Windows Firewall with Advanced Security .

2. Right-click Windows Firewall with Advanced Security and choose Properties.

3. Choose the relevant profile (in most cases Domain Profile) and set the Firewall state to Off.

4.3 Performing Basic Windows Preparation Steps

This section informs you about basic preparation steps that you have to perform before you install the

SAP system, including the following:

■ Checking the Windows file system

■ Checking the Windows domain structure (domain installation only)

■ Windows Server 2008 R2: Ensuring performance

4 Preparation

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

46/164 PUBLIC 2013-07-15

Procedure

Checking the Windows File System

You need to check that you are using the Windows file system NTFS on hosts where you want to install

the SAP system. NTFS supports full Windows security and long file names.

NOTE

Do not install the SAP system on a FAT partition.

Perform the check as follows:


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

get-volume

2. Check that the value FileSystem is NTFS.

■ Windows Server 2008 (R2)_

1. Open the Windows Explorer.

2. Select the relevant disk.

3. Choose Properties General .

The system displays the type of file system in use.

4. Check that the file system is NTFS.

Checking the Windows Domain Structure

NOTE

You do not need this step for a local installation.

For a domain installation, we recommend that you check that all SAP system hosts are members of a

single Windows domain. We recommend this for all SAP system setups.

We assume that you are familiar with checking Windows domain structures. For more information,

see the Windows documentation.

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

■ Extra domain

In this model, the SAP system is embedded in its own domain, which is specially defined for SAP.

A second domain exists for the user accounts.

In Windows, the SAP domain and user domain must be incorporated in a domain tree. In this tree,

the user accounts must form the root domain and the SAP domain must be a child domain of this.

■ Single domain

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

CAUTION

You cannot create local users and groups on the host that is used as domain controller. Therefore,

we do not support running an SAP instance (including the database instance) on the host where

the domain controller is installed.

4 Preparation

4.3 Performing Basic Windows Preparation Steps

2013-07-15 PUBLIC 47/164

Windows Server 2008 R2: Ensuring Performance

Windows Server 2008 R2 provides these power plans to maximize performance and conserve energy:

■ Balanced (recommended)

■ High Performance

■ Power Saver

By default, Windows Server 2008 R2 sets the Balanced (recommended) power plan, which saves energy by

turning off or putting system resources (hardware) to sleep. However, resource intensive applications

might experience performance problems if they cannot fully use the available hardware resources. To

avoid this, make sure that you set the power plan on your Windows Server 2008 R2 host to High

Performance.

To change a power plan, proceed as follows:

1. Choose Start Control Panel Power Options

2. Select Power Options.

3. In the Select a power plan window, select High Performance.

4. If you do not see Power Options, type the word power in the Search Control Panel box, and select Choose a

power plan.

NOTE

By default, the option to change power plans is disabled.

To enable it, select the link Change settings that are currently unavailable.

Choose the High Performance option, and close the Power Option window.

4.4 Required User Authorization for Running the Installer

Although the installer automatically grants the required rights to the user account used for the

installation, you have to check whether this account has the required authorization to perform the

installation. The authorization required depends on whether you intend to perform a domain or

local installation. If necessary, you have to ask the system administrator to grant the account the

necessary authorization before you start the installation. If you attempt the installation with an

account that has not the required authorization, the installation aborts.

This section informs you about the authorization required for a domain and a local installation.

Procedure

CAUTION

Do not use the user <sapsid>adm for running the installer.

Domain Installation

For a domain installation the account used for the installation needs to be a member of the local

Administrators and the domain Admins group of the domain involved. All machines in the system

4 Preparation


48/164 PUBLIC 2013-07-15

must belong to the same domain. In a domain installation, the user information is stored centrally on

the domain controller and is accessible to all hosts in the system.

If the SAP system is to be distributed across more than one machine, SAP strongly recommends you

to perform a domain installation to avoid authorization problems.

CAUTION

■ If you install a distributed system as a local installation, this can lead to authorization problems

for the operating system users <sapsid>adm and SAPService<SAPSID>. It can also lead to

problems with the transport directory, which is usually shared by several SAP systems.

Therefore, SAP does not support a local installation for a distributed system and recommends

you to install a distributed system as a domain installation.

If you still want to perform a local installation for a distributed system, make sure that:

If you still want to perform a local installation for a system with additional application server

instances that run on hosts other than the host running the central instance, make sure that:

● You use the same password for the <sapsid>adm or the SAPService<SAPSID> user on all

hosts.

The password for the <sapsid>adm and SAPService<SAPSID> user can differ.

● You use the same master password on all hosts.

● All hosts belong to the same Windows work group.


In an MSCS configuration, you always have to perform a domain installation.End of: HA (MSCS) |

■ For performance and security reasons, SAP does not support an SAP system installation on

a domain controller.

■ If for any reason, the account used for the installation is not a member of the domain

Admins group, you can perform the installation with a domain user who is a member of the

local Administrators group. However, the domain administrator has to prepare the system

appropriately for you.

For a domain installation, you need to:

1. Check that the account used for the installation is a member of the domain Admins group.

2. If required, obtain these rights by asking the system administrator to enter the account as a member

of the domain Admins group.

Local Installation

For a local installation the account used for the installation needs to be a member of the local

Administrators group of the machine involved. In a local installation, all Windows account

information is stored locally on one host and is not visible to any other hosts in the system.

If the SAP system is to run on a single machine, you can perform a local installation.

4 Preparation


2013-07-15 PUBLIC 49/164

CAUTION

Do not use the Windows built-in account Administrator or the renamed built-in account to

install your SAP system with the installer. The built-in account only has restricted network access

rights that are required by the installer. If you renamed the built-in account Administrator, do

not create a new account named Administrator.

For a local installation, you need to:

1. Check that the account used for the installation is a member of the local Administrators group.

2. If required, obtain these rights by asking the system administrator to enter the account as a member

of the local Administrators group.

4.5 Preparing the SAP System Transport Host

The transport host has a directory structure that is used by the SAP transport system to store transport

data and metadata.

When you install an SAP system, the installer by default creates the transport directory on the global

host in \usr\sap\trans.

If you do not intend to use the directory structure of the system you are going to install, but want to

use another new transport directory on another host, or an existing transport directory in your system

landscape, you need to prepare that transport host:

■ If the directory structure already exists, you must set up its security to allow the new system to

write to it.

■ If it does not yet exist, you must create the core directory structure and a share to export it for

other computers as well as set the security on it.

The global transport directory \usr\sap\trans is used by the Change and Transport System (CTS).

The CTS helps you to organize development projects in the ABAP Workbench and in Customizing,

and then transport the changes between the SAP systems in your system landscape. For more

information, see:

http://help.sap.com SAP NetWeaver <Release> Application Help Function-Oriented View: English

Solution Life Cycle Management Software Logistics Change and Transport System

Procedure

1. If the transport directory does not yet exist, do the following:

1. Create the directory \usr\sap\trans on the host to be used as the transport host.

2. Share the usr\sap directory on the transport host as SAPMNT and set the permission for

Everyone to Full Control for this share.

This enables the installer to address the transport directory in the standard way as \

\SAPTRANSHOST\SAPMNT\trans.

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

4 Preparation

4.5 Preparing the SAP System Transport Host

50/164 PUBLIC 2013-07-15

http://help.sap.com

CAUTION

Remove the Full Control to Everyone permission after you have finished the installation with the

installer and only grant Full Control on this directory to the SAP_<SAPSID>_GlobalAdmin groups

of all the systems that are part of your transport infrastructure. The installer assigns the

appropriate rights with the help of an additional SAP_LocalAdmin group.

For more information, see Automatic Creation of Accounts and Groups [page 150].

4.6 Installing the SAP Front-End Software

For the installation, make sure that the front-end software is installed on at least one computer in your

system environment.

For information about the recommended versions of SAP GUI, check SAP Note 147519.

For more information about installing the front-end software, see the documentation SAP Front End

Installation Guide - <Current Release> at:

http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver <Release> Installation

Installation - Clients

4.7 Preparing the Installation Media

This section describes how to prepare the installation media, which are available as follows:

■ The software provisioning manager 1.0 archive containing the installer as such.

You always have to download the latest version of the software provisioning manager 1.0 archive.

■ The media containing the software to be installed, which are available as follows:

● You normally obtain the physical installation media as part of the installation package.

● You can also download the installation media apart from the software provisioning manager

1.0 archive from SAP Service Marketplace, as described at the end of this section.

For more information about the required media, see SAP Note 1680045.

Prerequisites

Make sure the latest version of the SAPCAR archiving tool is available on each installation host.

You require the SAPCAR archiving tool to be able to unpack software component archives (*.SAR files)

which is the format of software life-cycle media and tools that you can download from the SAP software

distribution center.

If required, you can download the latest version of SAPCAR from http://service.sap.com/swdc

Support Packages and Patches A – Z Index S SAPCAR .

For more information about SAPCAR, see SAP Note 212876

4 Preparation

4.6 Installing the SAP Front-End Software

2013-07-15 PUBLIC 51/164




http://service.sap.com/swdc


Procedure

1. Identify the required media for your installation [page 19] as listed below.

NOTE

The media names listed below are abbreviated. The full labels and the material numbers

of all media are listed in the media list for your component or in SAP Note 1748888. You can

find the location of the media list in the Master Guide for your SAP Business Suite application

or SAP NetWeaver application at http://service.sap.com/instguides.

SAP Instance Installation Required Software Packages from Installation Media

Central services instance for ABAP (ASCS)

■ Software provisioning manager 1.0 archive SWPM10SP<support package number>_<version number>.SAR

■ UC Kernel (folder K_U_<Version>_<OS>) where U means Unicode.

Database instance


■ UC Kernel (folder K_U_<Version>_<OS>) where U means Unicode. ■ Installation media for the RDBMS ■ Installation Export (folders EXP*)

Enqueue Replication Server



Primary application server instance



Additional application server instance


■ UC Kernel (folder K_U_<Version>_<OS>) where U means Unicode. ■ Installation media for the RDBMS

2. Make the installation media available on each installation host as follows:

1. Download the latest version of the software provisioning manager 1.0 archive

SWPM10SP<support package number>_<version number>.SAR from http://

service.sap.com/swdc Support Packages and Patches A – Z Index S SL Toolset SL Toolset

<release> Entry by Component Software Provisioning Manager Software Provisioning Manager 1.0

<Operating System>

2. Unpack the software provisioning manager archive to a local directory using the following

command: SAPCAR –xvf <download directory>/<path>/<Archive>.SAR -R <unpack

directory>.

3. Make the media containing the software to be installed available.

You can do this in one of the following ways:

■ Copy the required media folders directly to the installation hosts.

■ Mount media on a central media server that can be accessed from the installation hosts.

4 Preparation


52/164 PUBLIC 2013-07-15





CAUTION

■ If you copy the media to disk, make sure that the paths to the destination location

of the copied media do not contain any blanks.

■ If you perform a domain installation and do not want to copy the media but use

network drives for mapping the installation media, make sure that the

<sapsid>adm user has access to the UNC paths of the network drives. If the user does

not yet exist, you have to create the user manually before you install the SAP system.

Downloading Installation Media from SAP Service Marketplace

You normally obtain the installation media as part of the installation package from SAP.

However, you can also download installation media from the software distribution center on SAP

Service Marketplace using one of the following paths:

NOTE

You always have to download the software provisioning manager 1.0 archive (SWPM10SP<support

package number>_<version number>.SAR) from the software distribution center because you

have to use the latest version (see above).

■ http://service.sap.com/swdc Installations and Upgrades A-Z index <first letter of your product>

<your product version>

■ http://service.sap.com/swdc Installations and Upgrades Browse Our Download Catalog <your

product> <your product version>

NOTE

If you download installation media, note that they might be split into several files. In this case,

you have to reassemble the required files after the download.

1. Create a download directory on the host on which you want to run the installer.

2. Identify all download objects that belong to one installation medium according to one or both of

the following:

■ Material number

All download objects that are part of an installation medium have the same material number

and an individual sequence number:

<material_number>_<sequence_number>

EXAMPLE

51031387_1

51031387_2

...

■ Title

4 Preparation


2013-07-15 PUBLIC 53/164



All objects that are part of an installation medium have the same title, such as

<solution><media_name><OS> or <database>RDBMS<OS> for database media.

3. Download the objects to the download directory.

4. To correctly re-combine the media that are split into small parts, you must unpack all parts into

the same directory.

In the unpacking directory, the system creates a subdirectory with a short text describing the

medium and copies the data into it. The data is now all in the correct directory, the same as on the

medium that was physically produced. For more information, see SAP Note 1258173.

4 Preparation


54/164 PUBLIC 2013-07-15


5 Installation

5.1 Installation Checklist

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

■ Standard system

■ Distributed system

■ Only valid for: HA (MSCS);HA (UNIX) |

High-availability systemEnd of: HA (MSCS);HA (UNIX) |



Standard System

1. On the standard system installation host, you install the SAP system with the installer [page 57].

NOTE

In a standard system, all mandatory instances are installed on one host in one installation

run.

2. You continue with Post-Installation [page 71].

Distributed System

1. On the host where the primary application server instance is to run, you run the installer [page 57]

to prepare the SAP global host.

2. On the database instance host, you run the installer [page 57] to install the database instance.

3. On the primary application server instance host, you run the installer [page 57] to install the primary

application server instance.

4. If required, you install 1 to <n> additional application server instances on the respective hosts, as

described later in this section.


High-Availability System

1. You set up the switchover cluster as follows:

1. You perform the steps to set up the switchover cluster infrastructure as described in the

documentation of your HA partner.

2. On the database instance host, you do the following:

5 Installation


2013-07-15 PUBLIC 55/164

RECOMMENDATION

We recommend that the database instance is part of the hardware cluster or of any other

proprietary high-availability solution for the database.

1. You make sure that global directories are available. If you want to use the shared transport

directories from another system, make sure that this directory is also available.

2. You run the installer [page 57] to install the database instance on the database instance host.

3. On the primary application server instance host, you do the following:

NOTE

In a high-availability installation, the primary application server instance does not need to

be part of the cluster because it is no longer a single point of failure (SPOF). The SPOF is now

in the central services instance (ASCS instance), which is protected by the cluster.

1. You run the installer [page 57] to install the primary application server instance.

CAUTION

the installer generates a temporary SAP license when you install the primary application

server instance. This temporary license key is determined by the hardware environment

of the message server. Therefore, make sure that you do not perform a switchover of

the SCS instance until you have finished the installation of the primary application server

instance. Once you have finished the installation of the primary application server

instance, make sure that you install permanent SAP licenses for every cluster node (host

A and host B) before you perform a switchover. For more information, see High Availability:

Setting Up Licenses.

4. We recommend that you install additional application server instances to create redundancy.

Application server instances are not a SPOF. Therefore, you do not need to include them in the

cluster.

On every additional application server instance host, you do the following:

1. You run the installer [page 57] to install the additional application server instance.



High-Availability System

1. To install a high-availability system with Microsoft Cluster Service (MSCS), you perform the

MSCS-specific installation steps [page 103].

2. You continue with Post-Installation [page 71].End of: HA (MSCS) |


You perform the following steps on each host where you install the additional application server

instances.

1. You run the installer [page 57] to install the additional application server instances.

5 Installation


56/164 PUBLIC 2013-07-15


CAUTION

In a high-availability system, you must install at least one additional application server

instance.

End of: HA (MSCS) |


5.2 Running the Installer

This section describes how to run the installation tool software provisioning manager 1.0 (the “installer”

for short). Software provisioning manager 1.0 includes a GUI client and a GUI server, which both use

Java. In the following, GUI client and GUI server are called the “installer GUI”.

This procedure describes an installation where the installer and the installer GUI are running on the

same host.

Useful Information About the Installer

■ The installer creates the installation directory sapinst_instdir, where it keeps its log files, and

which is located directly in the %ProgramFiles% directory. If the installer is not able to create

sapinst_instdir there, it tries to create sapinst_instdir in the directory defined by the

environment variable TEMP.

■ The installer creates a subdirectory for each installation option called <sapinst_instdir>

\<installation_option_directory>, which is located in %ProgramFiles%.

■ The installer extracts itself to a temporary directory (TEMP, TMP, TMPDIR, or SystemRoot). These

executables are deleted after the installer has stopped running.

Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You

can safely delete them.

The temporary directory also contains the log file dev_selfex.out from the extraction process,

which might be useful if an error occurs.

CAUTION

If the installer cannot find a temporary directory, the installation terminates with the error

FCO-00058.

■ During the installation, the default ports 21200, 21212, and 4239 are used for communication

between the installer, the installer GUI server, the installer GUI client, and HTTP server, as follows:

● The installer uses port 21200 to communicate with the GUI server.

● The GUI server uses port 21212 to communicate with the GUI client.

● 4239 is the port of the HTTP server, which is part of the GUI server.

If these ports are already in use, the installer automatically searches for free port numbers. If the

search fails, you see an error message and the installer exits.

5 Installation


2013-07-15 PUBLIC 57/164

In this case or if you want the installer to use specific ports, open a command prompt and change

to the required directory as follows:

cd /d <drive>:\DATA_UNITS\IM_WINDOWS_<platform>

Execute sapinst.exe with the following commands:

● SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>

● GUISERVER_DIALOG_PORT=<port_number_gui_server_to_gui_client>

● GUISERVER_HTTP_PORT=<port_number_http_server>

■ To see a list of all available installer properties, go to the directory (%TEMP%

\sapinst_exe.xxxxxx.xxxx) after you have started the installer, and enter the following

command:

sapinst.exe -p

■ If you need to run the installer in accessibility mode, proceed as described in Running the Installer in

Accessibility Mode [page 67].

■ If required, you can stop the installer by choosing SAPinst Cancel in the installer GUI menu.

NOTE

If you need to terminate the installer, you can do this by choosing File Exit in the menu

of the Program Starter window.

Prerequisites

■ You need at least 300 MB of free space in the installation directory for each installation option. In

addition, you need 60 - 200 MB free space for the installer executables.

■ Make sure that you have defined the most important SAP system parameters as described in Basic

SAP System Installation Parameters [page 34] before you start the installation.

■ Check that your installation hosts meets the requirements for the installation options that you

want to install. For more information, see Running the Prerequisite Checker [page 21].

■ If you want to install an additional application server instance to an existing SAP system, make

sure that:

● The service definitions for the SAP start services are configured correctly and refer to the

correct profile files.

● There are no profile backup files with an underscore “_” in their profile name. If so, you must

replace the “_” with a “.”.

EXAMPLE

Rename <Drive:>\usr\sap\S14\SYS\profile\S14_DVEBMGS20_wsi6408_12 to

<Drive:>\usr\sap\S14\SYS\profile\S14_DVEBMGS20_wsi6408.12.

Procedure

1. Log on to the installation host using an account with the required user authorization to run the Installer

[page 48].

5 Installation


58/164 PUBLIC 2013-07-15

CAUTION

Do not use an existing <sapsid>adm user.

2. Make installation media available on the installation host.

3. Start the installer by double-clicking sapinst.exe from the directory:

<drive>:\DATA_UNITS\<product>_IM_WINDOWS_<your platform>_<your DB>

The installer GUI starts automatically by displaying the Welcome screen.

NOTE

If you need to perform the installation in accessibility mode, open a command prompt, change

to the directory <IM_WINDOWS_<your platform>_<your DB>, and execute sapinst.exe –

accessible.

For more information, see Running the Installer in Accessibility Mode [page 67].

4. In the Welcome screen, choose the required option:

■ Perform preparations

Go to one of the following:

● Go to Generic Installation Options <Database> Preparations and choose the required task:

Preparations Remarks

LDAP Registration Configures the Active Directory and sets up LDAP support for an application server instanceWe recommend you to configure the Active Directory before you install the SAP system or an application server.For more information about LDAP and Active Directory, see Integration of LDAP Directory Services [page 137].

SAP Host Agent Installs a standalone SAP Host Agent. For more information, see Standalone SAP Host Agent [page 18].

Operating System Users and Groups

Creates all operating system users for your SAP system if they do not yet existRun this installation option before you start the installation of the SAP system.

● Go to <SAP NetWeaver Release> <Database> Preparations and choose the required

task:

Preparations Remarks

Prerequisites Check Checks your hardware and software requirements before you start the installation. For more information, see Running the Prerequisites Checker in Standalone Mode [page 21].

■ Install an SAP system

To install an SAP system based on SAP NetWeaver application server ABAP, choose <SAP

Product> <Database> SAP Systems Application Server ABAP <System Variant> .

You can install the following system variants:

System Variants Remarks

Standard System Installs an SAP system with all mandatory instances on one host

Distributed System Installs an SAP system with all mandatory instances on different hosts

5 Installation


2013-07-15 PUBLIC 59/164

System Variants RemarksPerform the installation options exactly in the order they appear. You have to restart the installer on the relevant host for each installation option.

High-Availability System Installs a high-availability SAP system with all mandatory instances on different hostsPerform the installation options exactly in the order they appear. You have to restart the installer on the relevant host for each installation option.

■ Perform other tasks or install additional components

Go to one of the following:

● Go to <SAP Product> <Database> and choose the required task:

Other Options Remarks

Additional SAP System Instances ◆ Additional Application Server Instance:Installs one or more additional application server instances

◆ Enqueue Replication Server Instance:Installs an enqueue replication server (ERS) instance for an existing central services instance for Java (SCS) or central services instance for ABAP (ASCS)

◆ Split Off Primary Replication Server Instance:Splits off a central services instance for ABAP (ASCS) from the primary application server instance of an existing ABAP system or ABAP+Java (dual-stack) system. For more information, see Splitting Off an ABAP Central Services Instance from an Existing Primary Application Server Instance [page 142].

● Go to Generic Installation Options <Database> and choose the required task:

Other Options Remarks

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

5. Choose Next.

6. If the installer prompts you to log off from your system, log off and log on again.

The installer restarts automatically.

7. Follow the instructions in the installer screens and enter the required parameters.

NOTE

To find more information on each parameter during the input phase of the installation,

position the cursor on the required parameter and press F1 .

After you have entered all requested input parameters, the installer displays the Parameter Summary

screen. This screen shows both the parameters that you entered and those that the installer set by

default. If required, you can revise the parameters before starting the installation.

8. To start the installation, choose Start.

5 Installation


60/164 PUBLIC 2013-07-15

The installer starts the installation and displays the progress of the installation. When the

installation has finished, the installer shows the message Execution of <Option_Name> has completed.

9. If required install an additional application server instance for a standard (central) or distributed

system.

10. We recommend deleting all files in the directory %userprofile%\.sdtgui\.

11. If you copied the installer software to your hard disk, you can delete these files when the installation

has successfully completed.

5.3 Additional Information About the Installer

The following sections provide additional information about the installer:

■ How to Avoid Automatic Logoff by the Installer [page 61]

■ Interrupted Installation [page 62]

■ Performing a Remote Installation with the Installer [page 64]

■ Starting the Installer GUI Separately [page 65].

■ Running the Installer in Accessibility Mode [page 67]

■ Entries in the Services File Created by the Installer [page 68]

5.3.1 How to Avoid Automatic Logoff by the Installer

When you install the SAP system with the installer, the installer installation tool checks whether the

user account used for the installation has the required privileges and authorization.

For a domain installation, the account needs to be both a member of the local Administrators group

and the domain Admins group. For a local installation, the account needs to be a member of the local

Administrators group.

In both cases, the user account must be authorized to do the following:

■ Act as part of the operating system

■ Adjust memory quotas for a process

■ Replace a process level token

If the user account does not have these rights assigned, the installer assigns them and automatically

logs the account off to activate them. To avoid that the installer logs the account off, you can set these

rights manually before you start the installation.

ProcedureYou perform the following steps to assign these rights to the user account used for the installation.

CAUTION

Be aware that domain policies override locally defined policies. This means that if you want to

grant domain administrator rights to a user who belongs to the local Administrators group,

make sure that you have also defined domain administrator rights for this user on domain level.

5 Installation


2013-07-15 PUBLIC 61/164

1. Windows Server 2012: Press CTRL+ESC and choose Administrative Tools Local Security Policy

2. Windows Server 2008 (R2): Choose Start Settings Control Panel Administrative Tools Local Security

Policy

3. In the Local Security Settings window, choose Local Policies User Rights Assignment.

4. Double-click the required right under Policy and choose Add User or Group.

5. In the Select Users and Groups window, choose the required user and choose Add.

The selected user appears in the box below.

6. Confirm your entry and then repeat the steps for each remaining policy that the user requires for

the installation.

7. Log off and log on again to apply the changes.

More Information

Required User Authorization for Running the Installer [page 48]

5.3.2 Interrupted Installation

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

■ An error occurred during the Define Parameters or Execute phase:

The installer does not abort the installation in error situations. If an error occurs, the installation

pauses and a dialog box appears. The dialog box contains a short description of the choices listed

in the table below as well as a path to a log file that contains detailed information about the error.

■ You interrupted the installation by choosing Cancel in the Installer menu.

CAUTION

If you stop an option in the Execute phase, any system or component installed by this option

is incomplete and not ready to be used. Any system or component uninstalled by this option

is not completely uninstalled.

The following table describes the options in the dialog box:

Option Definition

Retry The installer retries the installation from the point of failure without repeating any of the previous steps.This is possible because the installer records the installation progress in the keydb.xml file.We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry.If the same or a different error occurs, the installer displays the same dialog box again.

Stop The installer stops the installation, closing the dialog box, the installer GUI, and the GUI server.The installer records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.

5 Installation


62/164 PUBLIC 2013-07-15

Option Definition

Continue The installer continues the installation from the current point.

View Log Access installation log files.

Procedure

This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to

continue an interrupted installation after an error situation.

1. Log on to your remote host as a user who is a member of the local administrators group.

2. Make available the installation master media.

3. Restart the installer by double-clicking sapinst.exe. You can also start the installer by entering

the following commands at the Windows command prompt:

cd /d <media_drive>:\IM_WINDOWS<platform>

sapinst.exe

4. From the tree structure in the Welcome screen, select the installation option that you want to

continue and choose Next.

The What do you want to do? screen appears.

5. In the What do you want to do? screen, decide between the following alternatives and continue with

Next:

Alternative Behavior

Run a new option The installer does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installation-specific files to a backup directory. Afterwards, you can no longer continue the old installation option.

NOTE

All action taken by the installation before you stopped it (like creating directories, or users) will not be revoked.

For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds>.

EXAMPLE

log_01_Oct_2008_13_47_56

CAUTION

The installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

Continue with the old option The installer continues the interrupted installation from the point of failure.

5 Installation


2013-07-15 PUBLIC 63/164

5.3.3 Performing a Remote Installation

You use this procedure to install your SAP system on a remote host. In this case, the installer and the

GUI server run on the remote host, and the installer GUI client (the “installer GUI” for short) runs on

the local host. The local host is the host from which you control the installation with the installer GUI.

If your security policy requires that the person performing the installation by running the installer

GUI on the local host is not allowed to know administrator credentials on the remote host, you can

specify another operating system user for authentication purposes. You do this using the

SAPINST_REMOTE_ACCESS_USER parameter when starting sapinst.exe from the command line.

You can run the installer GUI on a PC with 32-bit while the installer is running on a 64-bit installation

host. For more information, see Starting the Installer GUI Separately [page 65].

Prerequisites

■ The remote host meets the prerequisites for starting the installer as described in Running the

Installer. [page 57]

■ Both computers are in the same network and can ping each other.

To test this:

1. Log on to your remote host and enter the command ping <local host>.

2. Log on to the local host and enter the command ping <remote host>.

■ Make sure that the sapinst.exe on the remote host and the sapinstgui.exe on the local host

have exactly the same version. You can check this by using the option –version as described in

the procedure below and in the procedure in Starting the Installer GUI Separately [page 65].

■ If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER

command line parameter, make sure that this user exists on the remote host.

Procedure

1. Log on to your remote host as a user that is a member of the local administrators group.

2. Make installation media available on your remote host.

3. Open a command prompt and enter the following commands:

cd \d <media drive>:\DATA_UNITS\<product>_IM_WINDOWS_<platform>_<DB>

Run sapinst.exe -nogui

NOTE

If you need to specify another operating system user for authentication purposes, enter the

following command:

sapinst.exe -nogui SAPINST_REMOTE_ACCESS_USER=<specified OS user>

4. Execute the following command: sapinst.exe -nogui

The installer now starts and waits for the connection to the installer GUI. You see the following

at the command prompt:

5 Installation


64/164 PUBLIC 2013-07-15

guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation

5. Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page

65].

5.3.4 Starting the Installer GUI Separately

You use this procedure to start the installer GUI separately. You might need to start the installer GUI

separately in the following cases:

■ You closed the installer GUI using File Exit from the installer menu while the installer is still

running.

■ You want to perform a remote installation, where the installer GUI runs on a different host from

the installer. For more information, see Performing a Remote Installation [page 64].

Prerequisites

■ The host on which you want to start the installer GUI meets the prerequisites for starting the

installer as described in Running the Installer [page 57].

■ Make sure that the sapinst.exe on the remote host and the sapinstgui.exe on the local host

have exactly the same version. You can check this by using the option –version as described in

the procedure below and in the procedure in Performing a Remote Installation [page 64].

Procedure

NOTE

If you want to run the installer GUI on a remote host, it is mandatory to start the installer using

the -nogui property. If you have already started the installer without the –nogui property and

want to run the GUI on a different host, you have to exit the installation process by choosing

SAPinst Cancel and then follow the steps described in Interrupted Installation. Use the -nogui

property to restart the installer and start the installer GUI on the intended host.

Starting the Installer GUI on Windows

1. Make the installer software available on the host on which you want to start the installer GUI.

2. Start the installer by executing the following command:

<Drive:>\<path to unpack directory>\sapinstgui.exe

If required, use the appropriate command line parameters as described in the following:

■ If you want to perform a remote installation, proceed as follows:

1. Check the version of sapinstgui.exe by entering the following command:

sapinstgui.exe –version

The version of the sapinstgui executable must be exactly the same as the version of the

sapinst executable on the remote host (see also Performing a Remote Installation [page 64]).

5 Installation


2013-07-15 PUBLIC 65/164

2. Start the installer GUI by entering the following command:

sapinstgui.exe -host <remote_host> -port

<port_number_gui_server_to_gui_client>

– where <remote_host> is the name of the remote host, and

<port_number_gui_server_to_gui_client> is the port the GUI server uses to

communicate with the GUI client (21212 by default).

■ If you closed the installer GUI using File Exit and want to reconnect to the installer,

proceed as follows:

● If you are performing a local installation with the installer and the installer GUI running

on the same host, execute the following command:

sapinstgui.exe -standalone -port <port_number_gui_server_to_gui_client>

– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to


● If you are performing a remote installation with the installer and the installer GUI running

on different hosts, execute the following command:

sapinstgui.exe -host <remote_host> -port





The installer GUI starts and connects to the installer.

Starting the Installer GUI on UNIX

1. Make the installer software available on the host on which you want to start the installer GUI.

2. Start the installer by executing the following command: /<path to unpack directory>/

sapinstgui

If required, use the appropriate command line parameters as described in the following:

■ If you want to perform a remote installation, proceed as follows:

1. Check the version of the sapinstgui executable by entering the following command:

/<path to unpack directory>/sapinstgui –version

The version of the sapinstgui executable must be exactly the same as the version of the

sapinst executable on the remote host (see also Performing a Remote Installation [page 64]).

2. Start the installer GUI by entering the following command:

/<path to unpack directory>/sapinstgui -host <remote_host> -port





5 Installation


66/164 PUBLIC 2013-07-15

■ If you closed the installer GUI using File Exit and want to reconnect to the installer,

proceed as follows:

● If you are performing a local installation with the installer and the installer GUI running

on the same host, execute the following command:

/<path to unpack directory>/sapinstgui -port

<port_number_gui_server_to_gui>

– where <port_number_gui_server_to_gui> is the port the GUI server uses to


● If you are performing a remote installation with the installer and the installer GUI running

on different hosts, execute the following command:

/<path to unpack directory>/sapinstgui -host <remote_host> -port

<port_number_gui_server_to_gui>


<port_number_gui_server_to_gui> is the port the GUI server uses to communicate with

the GUI client (21212 by default).

The installer GUI starts and connects to the installer.

5.3.5 Running the Installer in Accessibility Mode

You can also run the installer in accessibility mode. The following features are available:

■ Keyboard access:

This feature is available for all operating systems.

■ High-contrast color:

This feature is derived from the Windows display properties. You can use it either for a local

installation or for a remote installation.

■ Custom font setting:

This feature is derived from the Windows display properties. You can use it either for a local

installation or for a remote installation.

Procedure

Activating and Adjusting Accessibility Settings on Windows

You first have to activate and adjust the relevant settings for the font size and color schemes before

you start the installer or the the installer GUI.

NOTE

The following procedure applies for Windows Server 2008 and might be different when using

another Windows operating system.

1. Right click on your Windows desktop and choose Personalize.

5 Installation


2013-07-15 PUBLIC 67/164

2. Choose Adjust font size (DPI) and choose Larger scale (120 DPI).

To define other font size schemes, choose Custom DPI.

3. In the right-hand pane, select Window Color and Appearance.

Select a color scheme from the Color scheme dropdown box.

To define your own color schemes, choose Advanced.

Running the Installer in Accessibility Mode

You can either perform a local installation, where the installer and the installer GUI are running on

the same host, or a remote installation, where the installer and the installer GUI are running on different

hosts.

■ Local installation:

Start the installer as described in Running the Installer [page 57] by executing the following command:

sapinst.exe –accessible

■ Remote installation:

1. Start the installer on the remote host by executing the following command from the

command line as described in Performing a Remote Installation with the Installer [page 64]:

sapinst.exe –nogui

2. Start the installer GUI on the local host by executing the following command from the

command line as described in Starting the Installer GUI Separately for a Remote Installation [page 65]:

sapinstgui.exe -accessible –host <remote_host> -port


5.3.6 Entries in the Services File Created by the Installer

After the installation has finished successfully, the installer has created the following entries for port

names in <drive:>\WINDOWS\system32\drivers\etc\services:

sapdp<nn> = 32<nn>/tcp

sapdp<nn>s = 47<nn>/tcp

sapgw<nn> = 33<nn>/tcp

sapgw<nn>s = 48<nn>/tcp

sapms<SAPSID> = 36<nn>/tcp (unless you specified another value during the installation)

NOTE

■ <nn> is the instance number. There is a port created for every possible instance number,

regardless of which instance number you specified during the installation. For example, for

sapgw<nn> = 33<nn>/tcp the following range of entries is created:

sapgw00 = 3300/tcp

sapgw01 = 3301/tcp

sapgw02 = 3302/tcp

5 Installation


68/164 PUBLIC 2013-07-15

[...]

sapgw98 = 3398/tcp

sapgw99 = 3399/tcp

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

5 Installation


2013-07-15 PUBLIC 69/164

6 Post-Installation

6.1 Post-Installation Checklist

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

options:

■ Standard, distributed or high-availability system



Standard, Distributed, or High-Availability System

NOTE



You have to complete the following post-installation steps, which are described in more detail in the

linked chapters:

1. If required, you perform a full system backup [page 82] immediately after the installation has finished.

2. You check whether you can log on to the application server [page 72].

NOTE

In a distributed system, you check whether you can log on to every instance of the SAP system

that you installed.

3. You install the SAP license [page 73].

4. Windows Server 2008 R2: If required, you set up symbolic links for application servers [page 74].

5. You configure the remote connection to SAP support [page 75].

6. You install the SAP Online Documentation [page 75].

7. You perform post-installation steps for the ABAP application server [page 76].

8. You ensure user security [page 80].

9. To connect your SAP system to an existing standard system landscape directory (SLD), you configure

the connection to a central System Landscape Directory (SLD) [page 83].

10. You perform the client copy [page 83].

11. You perform a full installation backup [page 82].

12. You check the Master Guide for your SAP NetWeaver application for further implementation and

configuration steps.

6 Post-Installation

6.1 Post-Installation Checklist

2013-07-15 PUBLIC 71/164

CAUTION

The Master Guide 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 have to complete the following post-installation steps, which are described in more detail in the

linked chapters:

1. If required, you perform a full system backup [page 82] immediately after the installation has finished.

2. You check whether you can log on to the application server [page 72] of the additional application server

instance.

3. You configure user management [page 73].

4. You ensure user security [page 80].

5. Windows Server 2008 R2: If required, you set up symbolic links for application servers [page 74].

6. You install the SAP Online Documentation [page 75].

7. You perform a full installation backup [page 82].

6.2 Logging On to the Application Server

You need to check that you can log on to the SAP system with the standard users, given in the table

below.

ABAP Users

User User Name Client

SAP system user SAP* 000, 001, 066

DDIC 000, 001

Prerequisites

■ The SAP system is up and running.

■ You have already installed a front end.

Procedure

Logging On to the ABAP Application Server

You access the application server ABAP using SAP Logon

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

■ SAP GUI for Windows:

● Windows Server 2012:

1. Press Windows + Q , and enter SAP Logon in the Search field.

2. Choose SAP Logon.

● Windows Server 2008 (R2):

6 Post-Installation

6.2 Logging On to the Application Server

72/164 PUBLIC 2013-07-15

Choose Start All Programs SAP Front End SAP Logon .

■ SAP GUI for Java:

● Windows Server 2012:

1. Press Press Windows + Q , and enter SAP GUI for Java <release>

2. Choose SAP GUI for Java <release>.

● Windows Server 2008 (R2):

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

The SAP Logon appears.

NOTE

You can alternatively enter the command guilogon in the SAP GUI installation directory

to start SAP GUI for Java.

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

For more information about creating new logon entries, press F1 .

3. When you have created the entry, log on as user SAP* or DDIC.

6.3 Configuring User Management

After the installation of your SAP system has finished, you must decide whether you want to do the

following:

■ Add the system to Central User Administration (CUA)

■ Use Lightweight Directory Access Protocol (LDAP) synchronization

For more information, see the SAP Library at:


Security Identity Management Identity Management for System Landscapes Integration of User Management in Your

System Landscape Adding an ABAP System to Your System Landscape

6.4 Installing the SAP License

You must install a permanent SAP license. When you install your SAP system, a temporary license

is automatically installed.

CAUTION

Before the temporary license expires, you must apply for a permanent license key from SAP.

We recommend that you apply for a permanent license key as soon as possible after installing

your system.

Procedure

Install the SAP license as described in the SAP Library at:

Solution Life Cycle Management SAP Licenses

6 Post-Installation

6.3 Configuring User Management

2013-07-15 PUBLIC 73/164

http://help.sap.com


NOTE

The license key is bound to the hardware key of the host where the message server is running.

In a high-availability system with MSCS, the message server is part of the (A)SCS instance that

can run on different MSCS node. Therefore you must install the SAP license on both nodes.

You have to do failover from the first MSCS node where the (A)SCS instance is installed to the

second MSCS node. Use the hardware key of the second MSCS node for the installation of the

second SAP license.

End of: HA (MSCS) |

More Information

For more information about SAP license keys and how to obtain them, see

http://service.sap.com/licensekey.

6.5 Creating Symbolic Links on Windows Server 2008 R2 and higher for Application Servers

As of Windows Server 2008 R2, you can create symbolic links for additional application server instances

to simplify their administration.


In a high-availability system, you can additionally create symbolic links for the central instance.End of: HA (MSCS) |

Symbolic links for application servers let you access from your local host the SYS directory that is located

on the global host, without having to specify its UNC path. Instead you can browse, for example, in

the Windows explorer on your local host to the SYS directory and its subdirectories on the global host.

Procedure

To create symbolic links, perform the following steps:

■ Windows Server 2012

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

in a single line:

cmd /c mklink /d <localdisk>:\usr\sap\<SAPSID>\SYS \\<sapglobalhost>\sapmnt

\<SAPSID>\SYS

NOTE

Enter a blank before \\<sapglobalhost>\....

2. If you use a central transport directory, you can also create the following link in PowerShell:

cmd /c mklink /d <localdisk>:\usr\sap\trans \\<trans_dir_host>\sapmnt\trans

6 Post-Installation

6.5 Creating Symbolic Links on Windows Server 2008 R2 and higher for Application Servers

74/164 PUBLIC 2013-07-15

http://service.sap.com/licensekey

NOTE

The transport directory host <trans_dir_host> and the <sapglobalhost> can be

identical.

CAUTION

The command mklink creates the link without checking whether the link target exists or is

accessible. If the link does not work after you created it, make sure that it exists and check

the accessibility of the UNC path.

■ Windows Server 2008 (R2)

1. In the Start menu, right-click on Command Prompt and choose Run as administrator.

2. Enter the following command in a single line:

mklink /d <localdisk>:\usr\sap\<SAPSID>\SYS \\<sapglobalhost>\sapmnt\<SAPSID>

\SYS

NOTE

Enter a blank before \\<sapglobalhost>\....

3. If you use a central transport directory, you can also create the following link:

mklink /d <localdisk>:\usr\sap\trans \\<trans_dir_host>\sapmnt\trans

NOTE

The transport directory host <trans_dir_host> and the <sapglobalhost> can be

identical.

CAUTION

The command mklink creates the link without checking whether the link target exists or is

accessible. If the link does not work after you created it, make sure that it exists and check the

accessibility of the UNC path.

6.6 Configuring Remote Connection to SAP Support

SAP offers its customers access to support and to a number of remote services such as the SAP EarlyWatch

service or the SAP GoingLive service. Therefore, you have to set up a remote network connection to

SAP. For more information, see SAP Service Marketplace at http://service.sap.com/

remoteconnection.

6.7 Installing the SAP Online Documentation

SAP currently provides an HTML-based solution for the online documentation, including the

Application Help, Glossary, Implementation Guide (IMG), and Release Notes. You can display the

documentation with a Java-compatible Web browser on all front-end platforms supported by SAP.

6 Post-Installation

6.6 Configuring Remote Connection to SAP Support

2013-07-15 PUBLIC 75/164

http://service.sap.com/remoteconnection

http://service.sap.com/remoteconnection

Process

Install the SAP online documentation in your SAP system as described in the README.TXT file contained

in the root directory of the online documentation DVD, delivered as part of the installation package.

6.8 Performing Post-Installation Steps for the ABAP Application Server

You have to perform the following post-installation steps for the ABAP application server:

■ Perform a consistency check

■ Maintain your company address for initial users

■ Configure the transport management system

■ Perform basic operations

■ Configure system parameters

■ Configure the number of work processes

■ Install languages and performing language transport

■ Configure the integrated Internet Transaction Server (ITS)

■ Make your newly installed SAP system known to your SAP Solution Manager

■ Configure AS ABAP to support Secure Socket Layer (SSL)

■ Configure Fully Qualified Domain Names (FQDN)

■ Configure business applications

For more information, see the appropriate sections below.

Prerequisites

You have logged on to the ABAP application server as described in Logging On to the Application Server [page

72].

Procedure

Performing a Consistency Check

We recommend that you check the consistency of the newly installed SAP ABAP system. When logging

on to the system for the first time, you need to trigger a consistency check manually. The function is

then called automatically whenever you start the system or an application server.

This checks the following:

■ Completeness of installation

■ Version compatibility between the SAP release and the operating system

The initial consistency check determines whether:

● The release number in the SAP kernel matches the release number defined in the database

system

● The character set specified in the SAP kernel matches the character set specified in the database

system

6 Post-Installation


76/164 PUBLIC 2013-07-15

● Critical structure definitions that are defined in both the data dictionary and the SAP kernel

are identical. The structures checked by this function include SYST, T100, TSTC, TDCT, and

TFDIR.

■ Accessibility of the message server

■ Availability of all work process types

■ Information about the enqueue server and the update service

To perform a consistency check, you can either call transaction SICK (SAP initial consistency check)

or choose Tools Administration Administration Installation Check from the menu.


http://help.sap.com Application Help Function-Oriented View: English Application Server Application

Server ABAP Administration of Application Server ABAP Monitoring and Administration Tools for Application Sesrver

ABAP Consistency Check

Maintaining Your Company Address for Initial Users

Maintain your company address in your ABAP system using transaction SU01 as described in the SAP

Library at:


Application Server Application Server ABAP Other Services Services for Business Users Business Address Services

(BC-SRV-ADR) Addresses in User Administration Maintenance of Address Data

NOTE

You must maintain your company address to create ABAP system users.

Configuring the Transport Management System

You have to perform some steps to be able to use the Transport Management System.

1. Perform post-installation steps for the transport organizer:

1. Call transaction SE06.

2. Select Standard Installation.

3. Choose Perform Post-Installation Actions.

2. Call transaction STMS in the ABAP system to configure the domain controller in the Transport

Management System (TMS).



Solution Life Cycle Management Software Logistics Change and Transport System

Performing Basic Operations

1. Go to the SAP Library at:

Application Help Function-Oriented View

2. Choose the relevant sections to perform the following operations:

6 Post-Installation


2013-07-15 PUBLIC 77/164

http://help.sap.com

http://help.sap.com

http://help.sap.com

Operation Section in SAP Documentation

Set up operation modes – transaction RZ04

Solution Life Cycle Management SAP NetWeaver Configuration Configuring SAP NetWeaver Configuring the CCMS Operation Modes

Set up logon groups – transaction SMLG

Solution Life Cycle Management SAP NetWeaver Configuration Configuring SAP NetWeaver Configuring the CCMS Logon Load Balancing SAP Logon

Set up administrators Application Server Application Server ABAP Administration of Application Server ABAP Background Processing Authorizations for Background Processing

Schedule background jobs Application Server Application Server ABAP Administration of Application Server ABAP Background Processing

Install a printer Application Server Application Server ABAP Administration of Application Server ABAP SAP Printing Guide

Configure the system log Application Server Application Server ABAP Administration of Application Server ABAP Monitoring and Administration Tools for Application Server ABAP System Log

Set up the DBA Planning Calendar and schedule jobs, for example, for backup and recovery.

For more information, see the online help in transaction DBACOCKPIT and SAP Note 1585386.

Configuring System Parameters

For more information about system profiles, which is where work processes and profile parameters are

defined, and how to configure them, see the SAP Library at:


Application Server Application Server ABAP Administration of Application Server ABAP Monitoring and

Administration Tools for Application Server ABAP Configuration in the CCMS Profiles

Checking the Configured Number of Work Processes

The installer installs ABAP systems with a minimum number of work processes. This is only an initial

configuration so that you can start working after the installation. You have to adapt the number of

work processes in a production system to the system resources and the number of users working in

each ABAP system application

For more information about how to configure work processes, see the SAP Library at http://

help.sap.com SAP NetWeaver <Release> Application Help Function-Oriented View: English Application

Server Application Server ABAP Administration of Application Server ABAP Monitoring and Administration Tools

for Application Server ABAP Monitoring in the CCMS Global Work Process Overview Displaying Detailed Work

Process Information

Configuring Kernel Parameters

To configure your kernel parameters, follow the recommendations in SAP Notes 146289 and 835474.

Installing Languages and Performing Language Transports

■ Install languages using transaction I18N:

● If you want to use English only, you must activate the default language settings once.

6 Post-Installation


78/164 PUBLIC 2013-07-15


http://help.sap.com

http://help.sap.com

http://help.sap.com



For more information about configuring the language settings, see the online documentation in

transaction I18N at I18N Menue I18N Customizing .

■ Perform language transport using transaction SMLT as described in the SAP Library at:

http://help.sap.com/nw731 Function-Oriented View Solution Life Cycle Management Software

Logistics Change and Transport System Language Transport

Using and Configuring the SAP ITS Integrated ICM

The SAP Internet Transaction Server (SAP ITS) is integrated in the SAP NetWeaver Application Server

ABAP (AS ABAP) as an Internet Communication Framework (ICF) service. You can access this, like

other services, with the Internet Communication Manager (ICM). With the SAP ITS integrated in AS

ABAP, the Web browser now communicates directly with the SAP system. Furthermore, all SAP ITS-

related sources, such as service files, HTML templates, or MIME files, are now stored in the database of

the system.

The SAP ITS supports the following functions:

■ SAP GUI for HTML

■ Internet Application Component (IAC) runtime or Web Transaction technology

For more information about how to configure the integrated SAP ITS, see the SAP Library at:


Application Server Application Server ABAP UI Technologies Web UI Technology SAP ITS in the SAP

NetWeaver Application Server Configuration

Configuring AS ABAP to Support Secure Socket Layer (SSL)

If you installed the SAP Cryptographic Library – see Basic SAP System Installation Parameters [page 34] – you

have to configure AS ABAP to support Secure Socket Layer (SSL), as described in the SAP Library at:

http://help.sap.com SAP NetWeaver <Release> Application Help Function-Oriented View Security

System Security System Security for SAP Web AS ABAP Only Trust Manager Example Configuring the SAP

Web AS for Supporting SSL

Configuring Fully Qualified Domain Names (FQDN)

If you want to use Web Dynpro ABAP as UI technology and you assigned a DNS Domain Name to your

SAP System – see Basic SAP System Installation Parameters [page 34] – you have to perform the required

configuration steps.

For more information, see SAP Note 654982 and the SAP Library at:


Application Server Application Server ABAP UI Technology Web UI Technology Web Dynpro ABAP Web

Dynpro ABAP Configuration Fully Qualified Domain Names (FQDN)

Configuring Business Applications

Prepare the SAP system for using business applications, which includes customizing the ABAP system

and the business components, as described in the SAP Library at:

6 Post-Installation


2013-07-15 PUBLIC 79/164


http://help.sap.com

http://help.sap.com


http://help.sap.com


Solution Life Cycle Management Customizing

6.9 Ensuring User Security

You need to ensure the security of the users that the installer created during the installation. The tables

below at the end of this section list these users:

■ Operating system users

■ SAP system users

During the installation, the installer by default assigned the master password to all users created during

the installation unless you specified other passwords.

If you change user passwords, be aware that SAP system users might exist in multiple SAP system clients

(for example, if a user was copied as part of the client copy). Therefore, you need to change the passwords

in all the relevant SAP system clients.

CAUTION

The installer applied the master password to users SAP* and DDIC only for SAP system clients 000

and 001, but not to users SAP*, DDIC, and EARLYWATCH in client 066.

Instead, the installer always assigns the following passwords to these users in client 066:

SAP*: 06071992

EARLYWATCH: support

See also Master Password in Basic SAP System Installation Parameters [page 34].

RECOMMENDATION

User ID and password are encoded only when transported across the network. Therefore, we

recommend using encryption at the network layer, either by using the Secure Sockets Layer (SSL)

protocol for HTTP connections or Secure Network Communications (SNC) for the SAP protocols

dialog and RFC.

For more information, see:

http://help.sap.com SAP NetWeaver <Release> Application Help Function-Oriented View:

English Security Network and Transport Layer Security

CAUTION

Make sure that you perform this procedure before the newly installed SAP system goes into

production. For security reasons, you also need to copy the installation directory to a separate,

secure location – such as a DVD – and then delete the installation directory.

Procedure

For the users listed below, take the precautions described in the relevant SAP security guide, which you

can find at http://service.sap.com/securityguide:

6 Post-Installation


80/164 PUBLIC 2013-07-15

http://help.sap.com

http://help.sap.com

http://service.sap.com/securityguide

Operating System Users

After the installation, operating system users for SAP system, database, diagnostics agent, and host

agent are available as listed in the following table:

User: Primary Group:

SAPService<SAPSID> This user is the Windows account that is used to run the SAP system and is not a member of the local Administrators group.

SAP system administrator <sapsid>adm sapsys (sapinst as secondary group)

Diagnostics agent administrator <dasid>adm sapsys (sapinst as secondary group)

syb<dbsid> sapsys (sapinst as secondary group)

SAP Host Agent User

User User Name Comment

Operating system user

sapadm SAP system administratorYou do not need to change the password of this user after the installation.This user is for administration purposes only.

SAP System Users

After the installation, ABAP system users are available. The following table shows these users together

with recommendations on how you can ensure the security of these users.

ABAP Users

User User Name Comment

SAP system user SAP* User exists in at least SAP system clients 000, 001, and 066

CAUTION

This user has extensive authorizations. Make sure that you assign a secure password.

DDIC User exists in at least SAP system clients 000 and 001

CAUTION

This user has extensive authorizations. Make sure that you assign a secure password.

EARLYWATCH User exists in at least SAP system client 066

SAPCPIC User exists in at least SAP system clients 000 and 001

More Information

For more information about managing ABAP users, see:

6 Post-Installation


2013-07-15 PUBLIC 81/164


Security Identity Management Identity Management of the Application Server ABAP

6.10 Enabling the Database

Proceed as follows:

1. Make sure that the version of your database is still supported. Refer to SAP Note 1554717.

2. Check if there are newer versions available. Refer to SAP Note 1590719.

3. You must enable the database for monitoring by setting up a data collection framework (DCF)

after the SAP system installation. The DCF provides a time-based collection and evaluation of

performance, configuration, and space-related data. It consists of:

■ a set of tables holding history data

■ a set of stored procedures to collect data on a regular basis

These stored procedures are scheduled by the ASE job scheduler.

In your SAP system, call transaction DBACOCKPIT to start the DBA Cockpit. Calling the DBA

Cockpit automatically checks the existence of the DCF.

RECOMMENDATION

To make sure that the DCF was set up correctly, we recommend that you go to the Collector

Configuration screen to check the status of the DCF.

For more information, refer to the database administration guide. You can find the

administration guide in the Service Marketplace: http://service.sap.com/instguides

SAP NetWeaver SAP NetWeaver <Release> Operations Database-Specific Guides

4. Manually activate the Internet Communication Framework (ICF) service to ensure that the DBA

Cockpit functions correctly. It is required to access Web Dynpro ABAP-based applications. It is not

activated by default. Refer to SAP Note 1245200.

5. Apply the latest patches for the DBA Cockpit. Refer to SAP Note 1558958.

6. Set up Automatic Table Maintenance in the DBA Cockpit. For more information, refer to http://

scn.sap.com/docs/DOC-15162.

7. Check whether the database configuration for an SAP installation complies with SAP's

requirements and recommendations. Refer to SAP Note 1539124.

8. For systems with high load, refer to SAP Note 1722359.

9. Ensure that you are able to recover the ASE server and all the server databases that are required

for running your SAP system. Refer to SAP Note 1585981.

6.11 Performing a Full System Backup

You must perform a full system backup after the configuration of your SAP system. If required, you

can also perform a full system backup after the installation (recommended). In addition, we

recommend you to regularly back up your database.

6 Post-Installation

6.10 Enabling the Database

82/164 PUBLIC 2013-07-15

http://help.sap.com






http://scn.sap.com/docs/DOC-15162





Prerequisites

■ You are logged on as user <sapsid>adm.

■ You have shut down the SAP system and database.

Procedure

For more information about backing up your SAP system on Windows, see http://help.sap.com

SAP NetWeaver <Release> Application Help Function-Oriented View: English Solution Life Cycle Management

Backup and Recovery Backing Up and Restoring your SAP System on Windows

6.12 Configuring the Connection to a Standard System Landscape Directory

For each system in your landscape that reports data to a central System Landscape Directory (SLD),

you have to configure a corresponding SLD data supplier.

Procedure

Configure the SLD data suppliers and the API for the SLD as described in the SAP Library at:


Solution Life Cycle Management System Landscape Directory Connecting Systems to the SLD

More Information

This documentation is also available in PDF form in the User Manual at:

http://www.sdn.sap.com/irj/sdn/nw-sld

6.13 Performing the Client Copy

The installer creates three ABAP clients during the installation, client 000, client 001, and client 066.

Client 000 is the SAP reference client for ABAP.

Use client 000 as source client for the client copy.

Only valid for: Process Integration (PI) |

CAUTION

For client copy considerations for Process Integration (PI), see SAP Note 940309.

End of: Process Integration (PI) |

Procedure

1. Maintain the new client with transaction SCC4.

2. Activate kernel user SAP*:

1. Set the profile parameter login/no_automatic_user_sapstar to 0.

2. Restart the application server.

6 Post-Installation

6.12 Configuring the Connection to a Standard System Landscape Directory

2013-07-15 PUBLIC 83/164

http://help.sap.com

http://help.sap.com

http://www.sdn.sap.com/irj/sdn/nw-sld


3. Log on to the new client with kernel user SAP* and password PASS.

4. Copy the client with transaction SCCL and profile SAP_CUST.

5. Check the log files with transaction SCC3.

6. Create the required users. These users must have at least the authorizations required for user

administration and system administration. Create a user SAP* with all required authorizations for

this user. If you want to have other users for system administration, you can also create user

SAP* without authorizations.

7. Deactivate kernel user SAP*:

1. Reset login/no_automatic_user_sapstar to 1.

2. Restart the application server.

More InformationFor more information about the client copy and about how to perform it, see the SAP Library at:


Solution Life Cycle Management Software Logistics Change and Transport System BC – Client Copy and

Transport

6.14 Post-Installation Steps for the SAP Host Agent

You have to perform the following steps on each host where the host agent is installed. This applies

whether the host agent is installed on a host within the SAP system or standalone on another host.

Procedure1. Log on as user sapadm.

2. Check whether the following services are available:

■ The control program saphostexec

■ The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)

3. Configure the host agent according to your requirements.

More InformationFor more information, see the SAP Library at:


Solution Life Cycle Management Solution Monitoring System Monitoring with CCMS Infrastructure of the

NetWeaver Management Agents

6.15 Accessing Configuration Documentation in SAP Solution Manager

To access configuration documentation in SAP Solution Manager, you have to connect your newly

installed SAP system to SAP Solution Manager.

6 Post-Installation

6.14 Post-Installation Steps for the SAP Host Agent

84/164 PUBLIC 2013-07-15

http://help.sap.com

http://help.sap.com

Procedure

Create a configuration project with the related configuration guide as described in the documentation.

http://service.sap.com/solutionmanager Media Library How-To Documents How to Create a

Configuration Guide using SAP Solution Manager

6 Post-Installation

6.15 Accessing Configuration Documentation in SAP Solution Manager

2013-07-15 PUBLIC 85/164

http://service.sap.com/solutionmanager

7 Disaster Recovery Setup with SAP Sybase Replication Server

In the following chapters you will learn how to set up a disaster recovery solution using SAP Sybase

ASE, the SAP Sybase Replication Server and the Disaster Recovery Agent Management utility. This

solution is not designed to support high availability, reporting, or other solutions that might be

supported by replication tools.

In a typical replication scenario, the SAP system updates data on the primary database. Transactions

are replicated to the standby database by the replication software. In a failover scenario, the SAP

application connections are switched to the standby database. Transactions generated on the standby

database continue to be saved by the replication server until the primary database comes back online.

Once the primary database returns to service, the saved standby database transactions are released and

applied to the primary host. Both databases are resynchronized.

The replication architecture consists of the primary and the standby environments. The database and

replication servers need to be run on the same hardware platform and operating system at both sites.

The hosts can be virtual or physical machines, or a mix of both.

Figure 5: Disaster recovery solution using SAP Sybase ASE, the SAP Sybase Replication Server and the

Disaster Recovery Agent Management utility

All components of an environment can run on the same host, but it is also possible to use several hosts.

The Replication Server and Disaster Recovery Agent must run on the same host.

For more information, refer to chapter Required File Systems and Directories.

The installation and uninstallation processes require having the SAP system mount directory (\

\<SAPGLOBALHOST>\sapmnt) available on that host.


2013-07-15 PUBLIC 87/164

For more information, refer to chapter SAP Directories.

Replication is set up to support a rebuild in both directions between the primary and the standby site,

although only one direction is available at any one point in time. Three databases are replicated between

the primary and the standby site:

■ SAP application database

■ saptools database

■ SAP Sybase ASE master database

The SAP Business Suite product must be installed with the SAP Sybase ASE database on the primary

site. The SAP NetWeaver Application Server can be installed on the database host or a separate host.

The standby database must be a copy of the database instance of the primary SAP system.

CAUTION

Do not enable a replication environment if you are not familiar with the SAP Sybase Replication

Server product. Particularly in outage situations, the database log of the primary database can run

out of space and the SAP System could face downtime as a result. Stopping the replication in an

inappropriate manner may require rematerialization of the standby database.

Read SAP Note 1891560 before you start the installation. The SAP Note contains the most recent

information on the installation, as well as corrections to the installation documentation.

7.1 Implementation Considerations

The standby database requires the same levels of protection and scheduled maintenance as the primary

database. Periodic reorganizations, generation of statistics, and other housekeeping tasks are also

required on the standby site. The standby site requires its own backup and recovery process. This

includes disk-based file backup and recovery, as well as dump creation and archiving at database level.

As a result of the logical replication method, the standby database might need more device space than

the primary site. Dump files from the primary host cannot be used for recovery of the standby site.

Once replication begins, the physical attributes of the primary and standby databases are no longer

equivalent and they can not share the same dump and load files for recovery.

During replication, additional information is written to the database transaction log for each database.

The transaction log volume will increase by 40 to 50 %.

The master and saptools databases will always be replicated. It is not possible to exclude them.

CAUTION

If you plan to upgrade your SAP system, you have to take into account that you have to tear down

the replication environment before the upgrade and to reinstall it after the upgrade.

7.2 Prerequisites

The following prerequisites must be fulfilled before you set up a disaster recovery solution:


7.1 Implementation Considerations

88/164 PUBLIC 2013-07-15


Area: Requirements:

Software The following software is required: ■ SAP Sybase ASE 15.7.0 SP 101 on the primary and standby hosts ■ SAP Sybase Replication Server 15.7.1 SP 100For more information, refer to http://help.sap.com/replication-server.

Hardware Database and replication server must use the same hardware platform. SAP recommends installing the replication server on a separate host to keep the impact on the database as low as possible.

Host Names Maximum length: 10 charactersUnderscores are not allowed.

Server Names The SAP Sybase ASE server name is based on the <SAPSID> value and is the same on both primary and standby sites.The SAP database name is the same on both sites.

Directories For an SAP installation, the replication environment must be installed in the following directory:<drive:>\sybase\<SID>_REP

Reserve at least 4 GB free space for software and configuration files.The initial replication server partition file is placed in a folder at:<drive:>\sybase\<SID>_REP\repdata_1

You can specify another folder for placing replication server partition files during installation. This allows distribution of disk I/O to several disks.The initial size of the partition file should be at least factor 1.5 of the log size of the SAP application database. Reserve additional 2 GB for replication server usage in this folder.

TCP/IP ports In addition to the ASE TCP/IP ports, the following ports are required for the replication environment: ■ Replication server: 4905 ■ Replication server system database: 4906 ■ Replication server system database replication agent: 4907 ■ DR agent RMI: 4908 ■ DR agent: 4909The values for the TCP/IP ports are default values. It is possible to customize the port numbers.

Database Time Synchronization

Both primary and standby databases must have the same UTC time. Otherwise the SAP application will not work properly, if the SAP system is using the standby database.

Database User The following users are required on both sites: ■ sapsa

■ sapsso

■ Replication user (<SID>_maint) ■ DR agent administrator (DR_admin)The sapsa and sapsso logins and their passwords must be identical across both databases. The replication user and the DR agent administrator are created by the SAP installer.Be aware that the database user DR_admin is included in the secure storage of the SAP system, should you want to change the password.

Operating system user

The replication server and the DR agent are started with OS user syb<sid>.Windows services are set up for the replication server and the DR agent. The services are installed with the logon information of OS user syb<sid>. Whenever the password of OS user syb<sid> is changed, you also have to change the services accordingly.


7.2 Prerequisites

2013-07-15 PUBLIC 89/164

http://help.sap.com/replication-server

7.3 Installing the Replication Environment

Perform the following installation steps to enable replication of an SAP system:

On the primary site:

1. Install a new SAP system or use an existing SAP source system.

2. Update the primary database to at least ASE 15.7.0 SP101.

For more information, refer to SAP Note 1607816.

3. Prepare the host that will run the replication server; update the OS libraries (if required for your

platform).

4. Verify that the SAP system mount directory is available on the host that will run the replication

server.

On the standby site:

1. Install a complete SAP System on the standby site, and only keep the database server up and running

after the installation. Use the same installation option as chosen for setting up the source SAP

System.

CAUTION

If the SAP System is started with the standby database, the standby database content will be

invalidated, replication will run into errors, and it will no longer be possible to use the standby

database for disaster recovery.

In the case of a failover, stop the SAP System using the primary database and start the SAP system

using the standby database.

The standby database content will be set up during the materialization phase of the installation.

2. Update the standby database to at least ASE 15.7.0 SP101.

3. Prepare the host that will run the replication server; update the OS libraries (if required for your

platform).

4. Verify that the SAP system mount directory is available on the host that will run the replication

server.

5. Choose the following installer options to set up the replication software and start the DR agent:

Generic Installation Options Sybase ASE Database Replication Setup of Replication Environment

NOTE

Disable Configure replication environment in the installer dialog screen.

A configuration of the replication environment is possible only if both primary and standby

DR agents are ready.

On the primary host:

1. Choose the following installer options to set up the replication software, start the DR agent, and

configure and activate replication (including database materialization):

Generic Installation Options Sybase ASE Database Replication Setup of Replication Environment



90/164 PUBLIC 2013-07-15


2. Enable Configure replication environment in the installer dialog screen and enter primary and standby

database connection information.

3. Choose the materialization method for the various databases to be replicated.

The materialization step performs the initial copy of database content from one site to the other.

Once completed, the replication software will maintain the data integrity of the target site by

continuously applying changes that occur after completion of the materialization process.

The procedure for materialization is dependent on the type and size of the database being

materialized (refer to the section Materializing Databases [page 91]).

The installer provides user interaction points that are used to synchronize the replication

environment with the end user's manual dump and load activities.

NOTE

In case of a disaster recovery to the standby node, the user environment and the profile of the

application server host names and ports must be adapted to the standby side.

Profiles:

Adapt dbs/syb/host and dbs/syb/port.

User environment:

Adapt dbs_syb_host and dbs_syb_port.

Unix:

1. Log in as user<sapsid>.adm.

2. Change to the <sapsid>adm home directory, and

adapt .dbenv.csh, .dbenv.sh, .dbenv_<hostname>.csh, .dbenv_<hostname>.sh.

3. Log in again to update the new environment.

Windows:

1. Adapt the user environment of <sapsid>adm using Control Panel System Advanced System

Settings Environment Variables

2. Restart the SAP<SAPSID>_<Instance_number> service.

7.3.1 Materializing Databases

This section describes how to materialize the following databases:

■ Master database

■ saptools database

■ SAP database

7.3.1.1 Materialize the Master Database

Some information in the master database is site-specific. The only master database changes that are

replicated are logins and roles for synchronizing users and credentials between the two sites. The DR



2013-07-15 PUBLIC 91/164

agent facilitates materialization of the master database providing an automated materialization

function.

The SAP installer materializes the master database automatically.

7.3.1.2 Materialize the “saptools” Database

SAP recommends that you materialize the saptools database before the SAP database. The size of the

database makes the materialization process relatively quick. During processing, there is further

validation that all replication processes are working correctly.

7.3.1.3 Materialize the SAP Database

Large databases, such as the SAP application database, may not fit for automatic materialization. Their

size requires timing and control that is best left to the attention of the administrator.

The SAP installer, by default, offers automatic database materialization through database dump and

load. It is also possible to perform customized database materialization. The SAP installer provides user

interaction points that are used to synchronize the replication environment with the end user's manual

database actions.

To guarantee recoverability, read SAP Note 1585981.

7.3.1.4 Manual Materialization

The following methods are available:

■ Using Database Dump and Load

■ Using Transaction Dump and Load

■ Using Snapshot Materialization

7.3.1.4.1 Using Database Dump and Load

If the database is small enough to support materialization using a single database dump file, the sequence

for performing this process is as follows:

1. The installer stops for manual loading of the standby database. The primary database contains the

necessary replication markers at this time.

2. Dump the database using the command dump database in the primary database server.

3. Copy the dump file to the standby site. You can use shared storage or FTP to make a copy of the

dump file available at the standby site.

4. Load the SAP database using the ASE command load database in the standby database server.



92/164 PUBLIC 2013-07-15


5. Bring the standby database online using the command online database to make the database

available for use in the standby system.

6. Confirm the installer dialog. The database will be checked for the dump marker.

7.3.1.4.2 Using Transaction Dump and Load

For large databases, it may be impractical to create a new dump of the entire database. Or the time

required to dump the database might create a backlog of hours or days that replication would need to

apply in order to get back in sync, thus creating an undesirable delay. To facilitate materialization for

large databases, the replication-related activity can be deferred until such time as a series of database

dump and subsequent transaction dumps have been loaded to the target database. Using this method,

which includes transaction dumps, means that the replication delay and backlog are kept to a

minimum.

The key difference in this technique is that the SAP installer is not involved until just before the last

transaction dump is to be created. This allows the replication products to only address activity that

occurs after the last transaction dump.

The sequence for performing materialization using transaction dump and load is as follows:

1. Dump the database on the primary database server. This can be a new dump or an existing dump

if your system is already configured to perform periodic dumps of the entire database. If you are

creating a new dump, use the ASE command dump database in the primary database server to

create a dump of the entire database.

2. Load the database on the standby database server. Use the ASE command load database in the

standby database server to load the dump.

3. Apply the transaction log dumps to the standby database with the ASE command load

transaction using existing or new transaction log dumps.

4. The installer stops for manual loading of the standby database. The primary database now contains

the necessary replication markers.

5. Dump the transaction log of the SAP database. Use the ASE command dump transaction in the

primary database server to create the last dump of the ASE transaction log.

6. Load the last SAP transaction log dump.

7. Bring the standby database online using the ASE command online database to make the database

available for use.


7.3.1.4.3 Using Snapshot Materialization

It is possible to materialize the standby database by using a snapshot of the primary database files with

the help of a hardware mirroring product.



2013-07-15 PUBLIC 93/164

The sequence for performing materialization using database device files is as follows:

1. The installer stops for manual materialization of the standby database. The primary database

contains the necessary replication markers at this time.

2. Quiesce the primary database.

Use the ASE command quiesce database to freeze the database by suspending all disk write

activities.

3. Generate a snapshot of the database files. The action to be performed depends on the hardware

mirror product you are using. You could also just copy the files, use shared storage or FTP to make

a copy of the dump file available at the standby site.

4. Unquiesce the primary database.

Use the ASE command quiesce database … release to enable disk write activities on the primary

database again.

5. Load the standby database with the snapshot files.

Use the ASE command mount database in the standby database to mount the database content.

6. Bring the database online using the ASE command online database in the standby database server

to make the database available for use.


7.4 Starting and Stopping DR Agent and Replication Server

To be able to stop and start the DR Agent and the replication server, you must have the credentials of

OS user syb<sid>.

7.4.1 Connecting to the DR Agent

Although there are two DR agents (one in primary and another in the standby environment), you will

only need to enter commands at one of the DR agents. The DR agents can connect to each other in

order to share configuration information or to execute any activity that requires local access to the

host. To set up and monitor replication, log on to the DR agent on the primary environment.

Use the DR agent’s host and port and the DR agent administrator’s security credentials to establish a

connection to the DR agent. The following example illustrates the use of ISQL to connect to the DR

agent. Open a command shell for OS user syb<sid>:

EXAMPLE

isql -X -U DR_admin -S <hostname>:<DR agent port>

The DR agent does not store its own security credentials, but rather, enforces authentication by pass-

through authentication to the database server, or replication server.


7.4 Starting and Stopping DR Agent and Replication Server

94/164 PUBLIC 2013-07-15

7.4.2 Starting the DR Agent

Start the Windows Service named SybaseDRAgent_<SID>.

7.4.3 Stopping the DR Agent

Stop the Windows Service named SybaseDRAgent_<SID>.

If you are using Microsoft Cluster Services, both the replication server and DR agent must be represented

by Windows Services, and they must be defined as services in all nodes of the cluster. If the services are

not defined on all nodes, attempts to fail-over will not be successful.

7.4.4 Starting the Replication Server

Start the Windows service named SYBREP_<SID>_REP.

7.4.5 Stopping the Replication Server

Stop the Windows service named SYBREP_<SID>_REP.

7.5 Removing the Replication Environment

The installer provides installation options for teardown and removal of a replication environment.

Start with the uninstallation of the current primary environment. Otherwise database connects will

be redirected and the installer will not be able to execute the necessary cleanup in the database.

As soon as the primary replication environment is removed, it is possible to uninstall the standby

replication environment.

Choose the following installer options to disable replication and remove the replication software on

the hosts running the replication servers.

Generic Installation Options SAP Sybase ASE Database Replication Removal of Replication Environment

Specify the kind of removal. Choose one of the following options:

■ Tear down replication system

This option

● disables replication in the ASE servers

● stops the replication servers

● deletes all directories and files created during setup, including the replication server instances

Data that was replicated to the standby databases will not be modified. The databases on the primary

and standby hosts will not be “unmarked” for replication. The state of the environment after


7.5 Removing the Replication Environment

2013-07-15 PUBLIC 95/164

teardown will allow the immediate recreation of the replication environment. Materialization will

again be required after setup.

NOTE

You can only tear down the replication environment if the DR Agent is up and running.

■ Unmark databases for replication and remove replication software

This option

● unmarks the databases

● drops the database users for replication

● removes the replication software

If the replication server was running on a separate host, it is possible to clean up remaining SAP

standalone units using the installer option Deleting an SAP System or Single Instances.

7.6 Integration of SAP Sybase Replication Server into an OS Cluster Environment

The replication server processes may run on the same machines hosting the ASE database servers. As

a result, if the ASE database servers are running in an OS cluster environment, the replication server

processes must be added to the definitions and instructions used by the cluster software.

This document describes the prerequisites and general requirements for allowing SAP Sybase

Replication Server to work successfully in an OS cluster environment. These cluster environments are

supported by hardware and software from third-party vendors. At this time, SAP Sybase Replication

Server support in a cluster environment is possibly not yet fully integrated in the vendors cluster. As

a result, the prerequisites and descriptions provided by this document provide general

recommendations on how to add support for SAP Sybase Replication Server in a cluster environment.

The primary assumption is that the cluster is already configured to support SAP Business Suite running

SAP Sybase ASE and that replication must be added to the configuration to make it complete. The

intent is that the replication server fails over or fails back in the OS cluster environment along with

SAP Sybase ASE.

7.6.1 Prerequisites

Cluster Prerequisites

The following general capabilities are expected to be provided by any OS cluster solution available in

order to allow the replication server to participate in the cluster.

NOTE

These are expected to be the same requirements that ASE requires; none of these requirements

is unique to the replication server.



96/164 PUBLIC 2013-07-15

■ Shared disk storage between nodes of the cluster is provided

This storage will be used for configuration files, executable files, and storage files.

■ Automatic IP address handling

When the cluster switches or moves activity from one node to another, the IP addresses used by

applications to access the servers will be automatically reassigned to the new cluster node by the

cluster software.

■ Process identification and manipulation

The cluster software provides the ability to identify an operating system process or server, and

exposes the ability to start and stop that process as part of the cluster failover process.

■ Dependencies

The cluster software provides the ability to identify dependencies between a process and other

resources in the cluster, so that any order of operations that relies on a preexisting process or

resources can be maintained.

SAP Sybase Replication Server Prerequisites

Once your SAP system is properly configured for your cluster, the replication server can be added to

the same cluster configuration to make the cluster environment complete. The intent is that the

replication server fail-over or fail-back in the cluster environment run in parallel with SAP Sybase ASE.

The replication server has the same disk device dependencies as SAP Sybase ASE. If the replication server

files need to be placed on a different device, be sure to add that additional device to the cluster resource

definitions and add that device as a dependency.

The following table shows the technical details for the replication server, depending on your OS cluster

software requirements:

Technical Details: Description.

Number of processes There are three individual operating processes: ■ Replication server ■ Replication server system database ■ DR (Disaster Recovery) agent

Number of cluster resources The replication server and its replication server system database are integrated. The replication server system database starts and stops with the replication server. As a result, it is sufficient to identify the replication server as a single resource for start, stop, and dependency configurations. The DR agent provides monitoring and configuration assistance for the replication server. It is not integrated with the replication server and is therefore required to be treated as an independent cluster resource.

Disk requirements The replication server includes all of the files installed under<drive:>\sybase\<SID>_REP

In addition, it is possible to configure the replication server to store its partition files in a separate location. All partition locations must be placed on devices shared between the nodes in the cluster. All of these devices must be identified as resources and dependencies for the cluster failover process.



2013-07-15 PUBLIC 97/164

Technical Details: Description.

Host name requirements During installation and configuration of the integrated Disaster Recovery solution for SAP Business Suite on ASE, the SAP installer prompts for the host names that will support the primary and standby instances. The host names supplied must, in each case, be the name of the cluster, and not the individual node names of the cluster.

NOTE

The SAP installer passes these same host names to the DR agent. If you are testing the DR agent

directly, the same host name of mycluster should be used whenever a host name is used.

NOTE

The replication server and DR agent resource availability should not be used to trigger cluster

failover. See the section Defining Node Failure Criteria [page 100].

7.6.2 Defining Resources

Two resources must be defined to include the replication server in your cluster solution. One resource

must be defined for the replication server. One additional resource must be defined for the DR agent

process. Before you can configure the resources for replication on the first OS cluster node, the ASE

database server must be running on this cluster node. Configuration of your cluster group to include

the replication server should not be performed until after the replication environment is successfully

installed.

7.6.2.1 Defining the SAP Sybase Replication Server Resource

Starting the Replication Server

Start the Windows service named: SYBREP_<SID>_REP.

Stopping the Replication Server

Stop the Windows service named: SYBREP_<SID>_REP.

Monitoring the Replication Server by Process

One method to determine whether the replication server is running is to look for the related system

processes running on the operating system. Two processes must exist – one for the replication server

and one for the replication server system database. Both processes should be running for you to be able

to determine whether the replication server is available.

Use the state of the Windows Service named: SYBREP_<SID>_REP.



98/164 PUBLIC 2013-07-15

Monitoring the Replication Server by Command

Use the state of the Windows Service named: SYBREP_<SID>_REP.

Stopping the Replication Server Forcefully

Some OS cluster software solutions require an option to forcefully terminate or remove a resource.

For the replication server, the operating system processes for the replication server and the replication

server system database can be terminated by sending a ‘kill’ signal to each of the processes.

Stop the Windows Service named: SYBREP_<SID>_REP.

7.6.2.2 Defining the DR Agent Resource

Starting the DR Agent

Start the Windows Service named: SybaseDRAgent_<SID>.

Stopping the DR Agent

Stop the Windows Service named:SybaseDRAgent_<SID>.

If you are using Microsoft Cluster Services, both the replication server and DR agent must be represented

by Windows Services, and they must be defined as services in all nodes of the cluster. If the services are

not defined on all nodes, attempts to fail-over will fail.

Monitoring the DR Agent by Process

One method to determine whether the DR agent is running is to look for the related system processes

running on the operating system.

Use the state of the Windows Service named: Sybase DRAgent_<SID>.

Stopping the DR Agent Forcefully

Some cluster software solutions require an option to forcefully terminate or remove a resource. For

the DR agent, the operating system processes for the DR agent can be terminated by sending a ‘kill’

signal to the operating system process.

Stop the Windows Service named: Sybase DRAgent_<SID>.

7.7 Defining Dependencies

Both resources for replication – the replication server and the DR agent resource – will have the same

dependencies. Each will be dependent on:

■ The shared disk resource(s)

■ The IP Address handling resource


7.7 Defining Dependencies

2013-07-15 PUBLIC 99/164

Use the appropriate commands for your cluster software to add these dependencies to both the

replication server and DR agent resources.

NOTE

There is no dependency between the replication server and DR agent. They can execute

independently of each other.

7.8 Defining Node Failure Criteria

Most cluster software allows the state of the different cluster resources to trigger an automatic fail-

over from one node in the cluster to another. The replication server and DR agent resource availability

should not be used to trigger cluster fail-over.

Since the replication server processing is considered part of the SAP Sybase ASE database solution, no

separate fault monitoring is required. If your existing hardware server or ASE monitoring determines

that fail-over should occur, this is sufficient for replication to participate. It is not suggested that you

add replication availability as a monitor for cluster node or ASE availability.

A failure by either of the replication resources will not affect the availability of your SAP application.

However, a failure of your ASE resources does affect your SAP application availability. It is recommended

that node failure continue to be triggered by ASE, but not include replication availability.


7.8 Defining Node Failure Criteria

100/164 PUBLIC 2013-07-15


8 High Availability with Microsoft Failover Clustering

You can install a high-availability SAP system with Microsoft Failover Clustering. The Failover Clustering

software improves the availability of the system and protects it against failure and unplanned downtime,

enabling 24-hour operation, 365 days a year.

With high availability you enable critical system components, known as “Single Points of Failure

(SPOFs)”, to be automatically switched from one machine to the other, if hardware or software problems

arise on one machine. With the help of this switchover – or failover – the system can continue

functioning.

Apart from enabling failover when hardware problems occur, you can also use Failover Clustering to

avoid downtime when you perform essential system maintenance. If you need to maintain one host

(failover cluster node), you can deliberately switch the cluster resources to the other host (failover

cluster node) and temporarily operate it there while maintenance is in progress. When maintenance

work is finished you can easily move the resources back to their original node and continue operating

them there.

When you are setting up the SAP system with Microsoft Failover Clustering, you combine standard

installation steps, described earlier in this documentation, with cluster-specific steps, described here.

CAUTION

Windows Server 2012:

As of Windows Server 2012, Microsoft replaces the Failover Cluster Commandline Interface

cluster.exe with the Failover Clustering module for Windows Powershell. However, for Windows Server

2012, you have to reactivate the tool manually. To do so, enter the following command:

add-windowsfeature RSAT-Clustering-CmdInterface

For more information, see SAP note 1715878.

You have the following options to install a high-availability SAP system with Microsoft Failover

Clustering:

■ You install one SAP system in one Microsoft failover cluster.

■ You install one SAP system in two Microsoft failover clusters.

■ You install several SAP systems in one or more Microsoft failover cluster(s) with two and more

Microsoft failover cluster nodes.


2013-07-15 PUBLIC 101/164


NOTE

If your database supports the installation on several Microsoft failover cluster nodes, you can

install the database instance on more than two Microsoft failover cluster nodes in one failover

cluster.

CAUTION

Make sure that you read SAP Note 1710950 before you begin the installation. It contains the most

recent information as well as corrections for a high-availability installation.

Restrictions

To install a new SAP system with Microsoft Failover Clustering, you have to perform a number of extra

steps specially required for the cluster and configure the SAP system so that it can take advantage of

the cluster functionality:

■ Since the cluster hardware has at least two nodes that have access to all local and shared storage

devices, you have to install some components on all nodes and pay attention to special rules for

distributing components to local or shared disks.

■ Since the correct configuration of network addresses is absolutely essential for the cluster to

function properly, you have to perform a number of additional steps that are necessary to set up

and check address resolution.

■ You have to install and configure the ASCS instance to run on two cluster nodes in one Microsoft

failover cluster.

NOTE

If you have an existing SAP system and plan to migrate to a cluster with new hardware, you install

the SAP system using a system copy.

For more information about the system copy, see the System Copy Guide for your SAP system at:

http://service.sap.com/instguides <Release> Installation

The system copy guide does not include the cluster-specific information, which is described here.

Terminology

■ In this documentation the hosts in a Microsoft failover cluster are referred to as first cluster node

and additional cluster node(s):

● The first cluster node is the cluster node where you perform the general installation of an

SAP system, for example where the database or (A)SCS instance is to be installed.

● The additional cluster node is the node where you configure the already installed SAP

instances to run in Microsoft Failover Clustering.

■ As of Windows Server 2008 there are the following terminology changes for a cluster configuration:

● The cluster feature is now called Failover Clustering. It might be that you still find the previous

terminology Microsoft Cluster Service and abbreviation MSCS in some sections of this guide.


102/164 PUBLIC 2013-07-15



● Cluster groups are now called services and applications (Windows Server 2008 (R2)), or roles (Windows

Server 2012).

In some sections we are continuing to use only the old term. In this case, “cluster group” also

means “service and application”, or “role”.

● The Cluster Administrator is now called Failover Cluster Manager.

8.1 Checklist for a High-Availability System

This section includes the steps that you have to perform for your SAP system using Microsoft Failover

Clustering. Detailed information about the steps is available in the relevant section.

Planning

1. You check that you have completed the same planning activities as for a non-HA system, including

the hardware and software requirements.

2. You decide how to set up your SAP system components in an HA configuration [page 104].

3. You decide how to distribute SAP system components to disks for HA [page 108].

4. You read Directories in an HA Configuration [page 110].

5. You read IP Addresses in an HA Configuration [page 111].

6. You obtain IP addresses for HA [page 114].

Preparation

1. You check that you have completed the same preparations [page 45] as for a non-HA system.

2. You map the IP addresses to host names [page 116] on the Domain Name System (DNS) Server or in the

hosts file on all cluster nodes.

3. To make sure that all preparation steps have been correctly performed, check that you can move

the disk resources from one cluster node to another so that they can be only accessed from a single

node at any time.

Installation

1. You make sure that:

1. You are logged on as domain administrator, unless otherwise specified.

2. You do not use the user <sapsid>adm unless specified.

3. If you are prompted during the installation process, log off and log on again.

4. When you reboot during the installation process on one MSCS node, you pause the other nodes before

the reboot. Otherwise, resources fail over to the other nodes.

2. In the Failover Cluster Manager you move all disk groups and the cluster group to the first MSCS node [page 125].

3. You install the database instance on an MSCS node.

4. You cluster the additional MSCS node [page 119].


8.1 Checklist for a High-Availability System

2013-07-15 PUBLIC 103/164

5. You install the central instance [page 120] on the central instance host or on a local disk on the MSCS

node.

6. You install at least one dialog instance [page 121] on the dialog instance host or on a local disk on the

MSCS node.

Post-Installation

1. You install the permanent SAP licenses on all cluster nodes.

2. You perform the post-installation checks for the enqueue replication server [page 122].

3. You perform the same post-installation steps as for a non-HA system.

Additional Information

■ Moving Cluster Groups, or Services and Applications, or Roles [page 125]

■ Starting and Stopping the SAP System in an HA Configuration [page 127].

8.2 Planning

The following sections provide information about how to plan the installation of the SAP system for

Microsoft Failover Clustering. For a complete list of all steps, see section Planning in the Installation Checklist

for a High-Availability System [page 103].

8.2.1 System Configuration with Microsoft Failover Clustering

The following chapters provide information about the configuration of your SAP system configuration

with Microsoft Failover Clustering. It describes the components you have to install for an SAP system

running in a Microsoft Failover Cluster, and how to distribute them on the specific host. For more

information, see:

■ SAP System Components in a Microsoft Failover Cluster [page 104]

■ Enqueue Replication Server in a Microsoft Failover Cluster [page 107]

8.2.1.1 SAP System Components in a Microsoft Failover Cluster

In a Microsoft Failover Cluster configuration you have the following components for your SAP system:

SAP System Components in an HA Configuration

Component

Number of Components per SAP System

Single Point of Failure (SPOF)

ASCS instance (message services and enqueue services) 1 yes

Database instance 1 yes


8.2 Planning

104/164 PUBLIC 2013-07-15

Component

Number of Components per SAP System

Single Point of Failure (SPOF)

Application server (central instance, dialog instance) 1-<n> no

■ To protect the SPOFs ((A)SCS instance, database instance) you have to use Microsoft Failover

Clustering.

If a hardware or software problem occurs on the first cluster node, the clustered (A)SCS instance

and the clustered database automatically fail over to the other node.

If you need to maintain the cluster node where the (A)SCS instance and database are running you

can switch these instances to the other node. When maintenance work is finished you move the

(A)SCS and database instance back to the original node.

■ To protect system components that are non-SPOFs, for example application servers, you have to

install them as multiple components. In this case you must install at least two application servers

(one central instance and at least one dialog instance) on two different hosts. You have the following

options:

● You install the central instance and the dialog instance on the cluster nodes of a Microsoft

failover cluster. You install them on a local disk. Any additional dialog instances are installed

on hosts outside of the Microsoft failover cluster.

If you have to maintain an cluster node, you have to stop the central or dialog instance on

that node. When you have finished maintenance, you restart the instances.

NOTE

If you install the central instance and the dialog instance on the cluster nodes, you must

perform the hardware sizing for the failover cluster host, as in this case the application

server is always running on this host. This increases system load and might impact

performance. Note that, as usual in an Microsoft failover cluster setup, the (A)SCS and

database instances also switch to run on the failover cluster host in the event of failover,

which temporarily also increases system load.

● You install the central instance and all dialog instances on hosts, which are not part of a

Microsoft cluster.

SAP System Components in One Microsoft Failover Cluster

The following figures show examples for the installation of SPOFs and non-SPOFs of an SAP system in

a Microsoft failover cluster with two nodes.

The first figure shows a Microsoft failover cluster configuration where the non-SPOFs components

(central instance, dialog instance) are installed locally on the cluster nodes. Any additional dialog

instances are installed outside the Microsoft failover cluster on separate hosts.


8.2 Planning

2013-07-15 PUBLIC 105/164

Figure 6: ABAP System with SPOFs, where non-SPOFs are installed locally on the Failover Cluster

Nodes

The following figure shows an cluster configuration, where the non-SPOFs components (central

instance, dialog instance) are installed on separate hosts that are not part of the Microsoft cluster.

Figure 7: ABAP System where the non-SPOFs are installed on hosts outside of the Microsoft Failover

Cluster


8.2 Planning

106/164 PUBLIC 2013-07-15

SAP System Components in Two Microsoft Failover Clusters

Besides installing your SAP system within one Microsoft Failover Cluster, you can also set up two

Microsoft Failover clusters and distribute the SPOF system components on these clusters to protect

them against system failure.

The following figure shows an example where the database instance for the SAP system is installed in

one Microsoft Failover Cluster, and the (A)SCS instance is installed on the second Microsoft Failover

Cluster. The application servers (central and dialog instance) can either be installed on a local disk on

the cluster nodes or on separate hosts that are not part of the Microsoft Failover Cluster.

Figure 8: ABAP System

8.2.1.2 Enqueue Replication Server in a Microsoft Failover Cluster

The enqueue replication server contains a replica of the lock table (replication table) and is an essential

component in a high-availability setup. It is installed on the two cluster nodes where the (A)SCS instance

is installed and configured to run.

In normal operation the replication enqueue server is always active on the host where the (A)SCS

instance is not running.

If an enqueue server in a Microsoft failover cluster with two nodes fails on the first cluster node, the

enqueue server on the additional cluster node is started. It retrieves the data from the replication table

on that node and writes it in its lock table. The enqueue replication server on the second cluster node


8.2 Planning

2013-07-15 PUBLIC 107/164

then becomes inactive. If the first cluster node is available again, the enqueue replication server on the

second cluster node becomes active again.

The following figure shows the enqueue replication server mechanism in an Microsoft failover cluster

configuration with two nodes:

Figure 9: Enqueue Replication Server Mechanism on One Microsoft Failover Cluster with Two Nodes

8.2.2 Distribution of SAP System Components to Disks for Failover Clustering

When planning the Microsoft failover cluster installation, keep in mind that the cluster hardware has

two different sets of disks:

■ Local disks that are connected directly to the cluster nodes

■ Shared disks that can be accessed by all cluster nodes via a shared interconnect

NOTE

Shared disk is a synonym for the cluster resource of Resource type Physical disk.

You need to install the SAP system components in both the following ways:

■ Separately on all cluster nodes to use the local storage on each node

■ On the shared storage used in common by all cluster nodes

You install the following on different shared disks:

● Database instance files

● (A)SCS instance

● SAP system executables


8.2 Planning

108/164 PUBLIC 2013-07-15

● Single quorum device, if used

CAUTION

You must not install any SAP or database components on the quorum disk.

Figure 10: Distribution of SAP System Components for one SAP System in a Failover Cluster

Quorum Configurations on Windows

On Windows there are several quorum configurations available. The configuration to use mainly

depends on the cluster setup, such as the number of cluster nodes, the storage type (single or

distributed), and the number of data centers. For more information, see the Windows documentation.

The default quorum configuration used on Windows Server 2008 (R2) and higher is called Node and Disk

Majority for clusters with more than two nodes.

With this quorum configuration, each node and the witness disk maintain its own copy of the cluster

configuration data. This ensures that the cluster configuration is kept running even if the witness disk

fails or is offline.

NOTE

The disk layout of the Node and Disk Majority and the Single Quorum Device Cluster is identical.

CAUTION

If you do not use the default quorum configuration for your operating system, contact your

hardware partner, who can help you to analyze your needs and set up your cluster model. SAP

supports these configurations if they are part of a cluster solution offered by your Original

Equipment Manufacturer (OEM), or Independent Hardware Vendor (IHV).


8.2 Planning

2013-07-15 PUBLIC 109/164

Geographically Dispersed Cluster (Geospan)

The standard cluster configuration consists of two cluster nodes and a shared disk storage with all

technical components located in the same data center. In a geographically dispersed cluster, also known

as a geospan cluster, the cluster nodes are distributed across at least two data centers to avoid the full

outage of a data center in the event of disaster.

A geospan configuration requires a more sophisticated disk storage architecture since a shared disk

storage can only be located in one data center and might therefore be a single point of failure (SPOF).

To prevent the disk storage becoming a SPOF, you have to configure the storage system in each data

center and to replicate its content to the storage system of the other data center.

Replication can either be synchronous or asynchronous, depending on the:

■ Functionality of the disk storage subsystem

■ Acceptable amount of data loss during a failover

■ Physical layout of the disk storage area network

This includes the distance between the storage systems, signal latency, capacity, and speed of the

network connection.

■ Customer budget

■ Functionality supported by the database vendor

The database components in geospan configurations are often no longer part of the cluster and the

database is replicated by pure database techniques, such as log shipping.

CAUTION

■ Currently, it is only possible to configure geospan clusters in the same subnet since on

Windows Server 2008 (R2), you must not change a virtual IP address during failover.

■ The numerous variants with geospan cluster configurations and the complex technical

requirements are the reasons why the installation and configuration of such high-availability

(HA) systems are not directly supported by SAP. Instead, the hardware vendors of this cluster

configuration are responsible for the installation, configuration, and operation of the HA

components running in geospan clusters. SAP only supports the standard operation and

function of the SAP components running in such cluster configurations.

All functionality to set up geospan clusters is already integrated in Windows Server 2008 (R2).

8.2.3 Directories in a Microsoft Failover Cluster Configuration

The following tables show the directories where the main software components for the SAP cluster

installation are stored:


8.2 Planning

110/164 PUBLIC 2013-07-15

Directories on Local Disks on Cluster Nodes

Component Default Directory

A supported operating system %windir%

Microsoft failover cluster software %windir%\Cluster

SAP cluster files %windir%\SAPCluster

Application server (if installed locally) <local_drive>:\usr\sap\<SAPSID>\<Instance>

Enqueue replication server <local_drive>:\usr\sap\<SAPSID>

\ERS<Instance_number>

Diagnostics agent <local_drive>:\usr\sap\SMD

SAP Host Agent %ProgramFiles%\SAP\hostctrl

Directories on Shared Disks

Component Default Directory

Cluster quorum resource (if used) <drive>:\Cluster (Windows Server 2008 (R2) and higher)

SAP global and instance directories <drive>:\usr\sap ...

SapCluster Directory

In an SAP cluster installation, an additional directory – %WINDIR%\SapCluster – is created under the

system directory.

This contains all the SAP files required by all cluster cluster nodes, independently of the cluster node

the SAP instance is running on. The files are database tools and program files (executables) used by the

operating system monitor (SAPOsCol).

The directory is added to the path variable of the user <sapsid>adm.

8.2.4 IP Addresses in a Failover Cluster Configuration

A part of the installation process that is unique to Microsoft Failover Clustering is the configuration

of host names and IP addresses in the network. This is a particularly important task because the

addressing plays a key role in the switchover procedure. Addressing must be set up correctly so that

the system can take advantage of the cluster functionality and switch between nodes when hardware

problems arise.

This section explains the different types of IP addresses and their function in the switchover mechanism

of one Microsoft failover cluster with two cluster nodes.

NOTE

As of Windows Server 2008, besides static IP addresses, you can also have DHCP-based (dynamic)

IP addresses.

Currently DHCP-based IP configurations are not supported for high-availability SAP systems. If

the virtual IP address of the SAP cluster group changes during a failover, your clients can no longer

reach the system due to DNS caching.


8.2 Planning

2013-07-15 PUBLIC 111/164

Types of IP Addresses

In a proper configured cluster with at least two nodes, there are at least seven IP addresses and

corresponding host names for your SAP system. You have two IP addresses for each cluster node, one

IP address for the cluster, one for the SAP cluster group, and one for the database cluster group.

Some of the addresses are assigned to the network adapters (network interface card, NIC) whereas

others are virtual IP addresses that are assigned to the cluster groups.

Physical IP Addresses Assigned to Network Adapters

A Microsoft failover configuration has two networks:

■ A public network that is used for the communication between the central instance, application

servers, and the LAN.

■ A private network that is used internally for communication between the nodes of the cluster ,

also called heartbeat.

The following figure shows a Microsoft failover cluster with two nodes and illustrates the adapters

required for the public and private networks, and their corresponding physical IP addresses. A physical

IP address, in contrast to a virtual one, is stationary and permanently mapped to the same adapter.

Figure 11: Adapters and IP Addresses Required for Public and Private Networks in an Microsoft Failover

Cluster with Two Nodes

Host Names Assigned to Network Adapters

Each of the physical IP addresses of the network adapters must have a corresponding host name. For

example, on the left-hand node in the figure above, you might assign the IP addresses of the public and

private network adapters as follows:

IP Addresses and Host Names

Network Adapter IP Address Host Name

Adapter 1 (private network) 10.1.1.1 clusA_priv

Adapter 3 (heartbeat network) 192.168.1.1 clusA


8.2 Planning

112/164 PUBLIC 2013-07-15

CAUTION

■ The IP address and host name of the public network adapter is also the IP address and name

of the machine. In our example, this means that the machine that is the cluster node on the

left in the figure has the name clusA.

■ Do not confuse the host name with the computer name. Each node also has a computer

name, which is often the same as the host name.

The computer name is displayed in the node column Failover Cluster Management. However, it

is not required for the TCP/IP communication in the cluster. When you configure IP addresses

and corresponding names, keep in mind that it is the host names that are important for the

cluster, not the computer names.

Virtual IP Addresses Assigned to Cluster Groups

After you have installed the SAP system and fully configured the cluster, the critical system resources

are bound together in three different groups. Each of these groups requires a virtual IP address and

network name that is permanently mapped to the group and not to a particular node. The advantage

of this is that, whenever a group is moved between nodes, its IP address and network name move

together with it.

A Microsoft failover configuration has the following groups:

■ SAP cluster group for each clustered SAP system

■ Database cluster group for each clustered SAP system

■ Cluster group

The following figure illustrates how the virtual IP addresses of the database group and SAP group can

move from one node to the other during a failover.

Figure 12: Failover of Virtual IP Addresses


8.2 Planning

2013-07-15 PUBLIC 113/164

8.2.5 Obtaining IP Addresses for a High-Availability System

This chapter describes how to obtain the IP addresses for the network adapters (cards) that are required

to install and run your cluster configuration.

For a clustered system, you have to configure IP addresses correctly. During the installation procedure

you have to assign at least seven IP addresses and host names. You normally obtain these names and

addresses from the system administrator.

Procedure

Ask the system administrator to give you the addresses and host names listed in the tables below, which

show an example for a configuration with one Microsoft failover cluster with two nodes. You need to

enter the addresses and host names later during the installation process.

The column Defined During indicates at which stage of the installation of the operating system and the

SAP system the addresses are defined in the system.

CAUTION

Use the names exactly as specified by the system administrator.

NOTE

Note: In the following tables we are only using the terminology cluster group, and not the Windows

Server 2008 (R2) terminology services and applications or the Windows Server 2012 terminology

Roles.

Physical IP Addresses

ComponentExample for Physical IP Address

Example for Physical Host Name Purpose Defined During

First cluster node:adapter for heartbeat network

10.1.1.1 clusA_priv Address for internode communication on the heartbeat network

Windows installation

First cluster node:adapter for public network

129.20.5.1 clusA Address of the first cluster node for communication with application servers and LAN (this is the same as the address of the first cluster node)


Additional cluster node:adapter for heartbeat network

10.1.1.2 clusB_priv Address for internode communication on the heartbeat network



8.2 Planning

114/164 PUBLIC 2013-07-15

ComponentExample for Physical IP Address

Example for Physical Host Name Purpose Defined During

Additional cluster node:adapter for public network

129.20.5.2 clusB Address of the additional cluster node for communication with application servers and LAN (this is the same as the address of the additional cluster node)


Virtual IP Addresses

ComponentExample for Virtual IP Address

Example for Host Name Purpose Defined During

Cluster group 129.20.5.3 clusgrp Virtual address and name of the cluster group. It identifies the cluster and is used for administration purposes.

Failover cluster software installation

SAP cluster group 129.20.5.4 sapgrp Virtual address and name for accessing the group of SAP resources, regardless of the node it is running on

Configuration of SAP system for high availability with the installer on the first node

Database cluster group

129.20.5.5 dbgrp Virtual address and name for accessing the group of database resources, regardless of the node it is running on

Execution of HA-wizard or database-specific cluster scripts

8.3 Preparation

The following sections provide information about how to prepare the installation of the SAP system

for Microsoft Failover Clustering. For a complete list of all steps, see section Preparation in the Installation

Checklist for a High-Availability System [page 103].

8.3.1 Assigning Drive Letters for MSCS

We recommend that you assign drive letters to the shared disks.


8.3 Preparation

2013-07-15 PUBLIC 115/164

In an MSCS cluster, the shared disks that can be accessed by all MSCS nodes via a common bus must

be addressed by all nodes with the same drive letters.

Procedure

1. Choose Start Control Panel Administrative Tools Computer Management Storage Disk

Management.

2. Select a disk and choose Action All tasks Change Drive Letter and Paths..

3. Enter a new drive letter.

8.3.2 Mapping Host Names to IP Addresses for High-Availability

To enable correct operation of the failover mechanism, you have to map all IP addresses in the Microsoft

failover cluster to host names.

The mapping enables the system to translate host names into IP addresses. Host names are normally

used for administrative tasks because they are easier to use than the long, numeric IP addresses. However,

the system can only respond to host names if they are translated into IP addresses.

Prerequisites

■ You have installed the Windows operating system.

■ You have the list of IP addresses [page 114].

■ You have correctly entered all IP addresses required for the failover cluster configuration.

CAUTION

Missing or incorrect entries for the IP addresses can cause problems later during the

installation.

Procedure

To map the host names to the IP addresses, do one of the following:

■ Map the host names to IP addresses on a Domain Name System (DNS) server.

■ Map the IP addresses in the Windows hosts file.

The file is located in the default Windows directory:

%SystemRoot%Drive\system32\drivers\etc

■ Check IPv4 host name resolution as described in SAP Note 1365796.

RECOMMENDATION

We strongly recommend that you perform the mapping on the DNS server because this only

requires a single entry.

If you perform the mapping in the hosts file, you have to maintain the hosts file on all cluster

nodes of the cluster, and on all application servers and front ends. This is necessary because each

host in the system has its own hosts file. However, note that this approach is more error-prone.


8.3 Preparation

116/164 PUBLIC 2013-07-15


8.4 Installation

The following sections provide information about how to install the SAP system in a high-availability

environment. For a complete list of all steps, see section Installation in the Installation Checklist for a High-

Availability System [page 103].

8.4.1 Configuring the First Cluster Node

The following procedure describes how to configure the first cluster node.

When you run the First Cluster Node option it:

■ Installs the central services instance for ABAP (ASCS) and prepares this host as the SAP global host

■ Creates the SAP cluster group and adds the ASCS instance to the SAP cluster group

■ Installs the enqueue replication server instance (ERS) for the ASCS instance

■ Installs the SAP Host Agent

CAUTION

When you reboot during the conversion to failover clustering, resources fail over to the other

cluster node. Therefore, after each reboot, you have to return the system to the state it was in

before the reboot, and move the resources back to the original node.

Prerequisites

■ You are logged on to the first cluster node as domain administrator or as a local user with domain

administration rights.

■ The ASCS installation drive must be online on the first cluster node.

■ You must install the ASCS instance on a shared disk, and the ERS instance and SAP Host Agent

on a local disk.

Procedure

1. Run the installer and choose:

<Your SAP product> <SAP technical stack> <Database> High-Availability System First Cluster

Node

NOTE

If the installer prompts you to log off from your system, log off, and log on again.

2. Enter the required parameter values.

NOTE

■ For more information about the input parameters, position the cursor on a parameter

and press F1 in the installer.

■ If you have a Microsoft cluster configuration with more than two nodes in one cluster,

you have to configure the ASCS instance on two nodes only. These are also the nodes

where you install the enqueue replication server.


8.4 Installation

2013-07-15 PUBLIC 117/164

More Information

Moving Cluster Groups or Services and Applications [page 125]

8.4.2 Installing the Database on the First Node

Procedure

CAUTION

The installer automatically creates a cluster group for the database instance. Do not create cluster

groups before the installation.

Perform the following steps to install the database on the first node:

1. Make sure that all shared disks of the cluster are available on this node.

2. Run the installer [page 57] and choose:

<Your SAP System> <SAP technical stack> <Database> High-Availability System Database

Instance

3. If you are installing the SAP Sybase ASE database with the installer for the first time and the installer

prompts you to log off, do the following:

1. Choose OK and log on again.

2. Perform step 1 above.

3. Select Run a new installation and choose OK.

4. Follow the instructions in the the installer dialogs and enter the required parameter values.

NOTE

■ Choose different destination drives for the database instance and the SAP instance.

■ Make sure that you distribute the database software and database devices correctly to

local and shared disks as described in Directories in an MSCS Configuration [page 110].

The SAP Sybase ASE database software can be installed on the shared disk.

As an alternative, the database software can also be installed on a local disk, provided the

database software is accessible through the same access path from all additional nodes

(see Configuring the Additional MSCS Node). If the database software is installed on a local disk,

a database software update can be performed on an inactive node without impairing the

productive database.

■ If you install database components like database software, data files and log files on more

than one shared disk, only the first shared disk will be added to the database cluster group

automatically. All other shared disks containing database components have to be added

manually to the database cluster group after the installation of the first database cluster

node.

■ Make a note of the disk drives that you choose during the installation, since you need to

enter these during the installation on additional nodes.


8.4 Installation

118/164 PUBLIC 2013-07-15

8.4.3 Configuring the Database on the Additional Node

Procedure

Perform the steps below to configure the database on the additional MSCS node.

CAUTION

Do not attempt to move the shared disks from node A to node B. the installer configures the

additional database cluster node. It is not necessary to move the shared disks before the installation

starts.

1. On the additional MSCS node, run the installer [page 57] and Welcome screen, choose <Your SAP

System> Installation Options Application Server <Stack> High-Availability System Additional Database

Cluster Node .

2. Follow the instructions in the the installer dialogs and enter the required parameter values.

CAUTION

■ Make sure that you enter the same drive as you did on the first database node.

■ Make sure that you distribute the database software and logs correctly to local and shared

disks as described in Directories in an MSCS Configuration [page 110].

8.4.4 Configuring the Additional Cluster Node

This procedure describes how to configure the additional cluster node.

When you run the Additional Cluster Node option it:

■ Configures the additional cluster node to run the SAP cluster group

■ Installs the enqueue replication server instance (ERS) for the ASCS instance

■ Installs the SAP Host Agent

CAUTION

■ You must install the ERS and SAP Host Agent on a local disk.

■ When you reboot during the conversion to failover clustering, resources fail over to the other

cluster node. Therefore, after each reboot, you have to return the system to the state it was

in before the reboot, and move the resources back to the original node.

Prerequisites

■ You are logged on to the additional cluster node as domain administrator or as a domain user

who is a local administrator on all cluster nodes.

■ You have already performed the First Cluster Node [page 117] option.

Procedure

1. Run the installer and choose:


8.4 Installation

2013-07-15 PUBLIC 119/164

<Your SAP product> <SAP technical stack> <Database> High-Availability System Additional Cluster

Node

NOTE

If the installer prompts you to log off from your system, log off and log on again.

2. Enter the required parameter values.

NOTE

■ For more information about the input parameters, position the cursor on the parameter


When you have made all required entries, the installer begins processing and converts the SAP

instances on the other cluster node for operation in Microsoft failover clustering.

More Information

Moving Cluster Groups or Services and Applications [page 125]

8.4.5 Installing the Central Instance

The following procedure describes how to install the central instance for Microsoft Failover Clustering.

You have the following options to install the central instance:

■ You install the central instance on a cluster node.

In this case, bring the SAP and the database cluster group online on this node, and make sure that

the central instance number is different from the (A)SCS instance number.

■ You install the central instance on a host outside of the Microsoft failover cluster.

In this case, you have to install the database client software on this host.

Procedure


<Your SAP product> <SAP technical stack> <Database> High-Availability System Central

Instance

2. If the installer prompts you to log off, choose OK and log on again.

3. Follow the instructions in the installer dialogs and enter the required parameter values.

NOTE



■ If you install the central instance on an cluster node, make sure that on the screen SAP

System > General Parameters for the:

● Profile Directory, you use the UNC path of the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile.


8.4 Installation

120/164 PUBLIC 2013-07-15

In a HA-system, the virtual host name of the (A)SCS instance is the same as the SAP

global host name.

● Installation Drive, you choose the local disk where you want to install the central

instance.

4. Check that the central instance is running.

8.4.6 Installing the Dialog Instance

You have to install at least one dialog instance for a high-availability configuration. You have the

following options to install the dialog instance:

■ You install the dialog instance on a cluster node.

In this case, bring the SAP and the database cluster group online on this node, and make sure that

the dialog instance number is different from the (A)SCS instance number.

■ You install the dialog instance on a host outside of the Microsoft failover cluster.

In this case, you have to install the database client software on this host.

Procedure


<Your SAP product> <SAP technical stack> <Database> High-Availability System Dialog

Instance

2. If the installer prompts you to log off, choose OK and log on again.

3. Follow the instructions in the installer dialogs and enter the required parameter values.

NOTE



■ If you install the dialog instance on an cluster node, make sure that on the screen SAP

System > General Parameters for the:

● Profile Directory, you use the UNC path of the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile

In a HA-system, the virtual host name of the (A)SCS instance is the same as the SAP

global host name.

● Dialog instance, you enter the same instance number as for the central instance.

● Installation Drive, you choose the local disk where you want to install the dialog

instance.

4. When you have finished, change the instance profile of the dialog instance so that the number of

its work processes equals the number of work processes of the central instance.

5. If required, install additional dialog instances outside of Microsoft failover cluster.


8.4 Installation

2013-07-15 PUBLIC 121/164

NOTE

Make sure that on the screen SAP System > General Parameters for the Profile Directory, you use the

UNC path of the virtual (A)SCS host name, for example:

\\<SAPGLOBALHOST>\sapmnt\<SAPSID>\SYS\profile

In a HA-system, the virtual host name of the (A)SCS instance is the same as the SAP global

host name.

8.5 Post-Installation

To complete and check the installation of the SAP system for a high-availability configuration, you

need to perform the following steps, which are described in more detail in the linked sections:

1. You perform the post-installation checks for the enqueue replication server [page 122].

2. If required, you perform the general post-installation steps listed in this guide.

8.5.1 Post-Installation Checks for Enqueue Replication Server

The following sections describe the tests you must perform to check whether the installed enqueue

replication server works properly. For these tests you use the ENQT and ENSMON command line tools,

which allow remote access to the enqueue server statistics. Before you can use these tools you must

copy them to the remote host where the Enqueue Replication Server is running and from where you

want to start the tests.

NOTE

Make sure that you have restarted the (A)SCS instance and service cluster resources SAP

<SAPSID> <(A)SCS_instance_number> Instance and SAP <SAPSID> <(A)SCS_instance_number>

Service. You can do this either with the installer while performing the installation, or the Failover

Cluster Manager

You perform the following steps:

1. You copy ENQT.exe and ENSMON.exe from your cluster’s binary directory on the sapmnt share \

\<host>\sapmnt\<SAPSID>\SYS\exe\<codepage>\<platform> to a directory on the remote host

from where you run the tests.

2. You check the status of the enqueue replication server with the ENSMON tool [page 123].

3. You check the fill status and ID of the lock table during failover with the ENQT tool [page 123].



122/164 PUBLIC 2013-07-15

8.5.1.1 Checking the Status of the Enqueue Replication Server with ENSMON

You use the ENSMON tool to check if the enqueue replication server and the enqueue server are

properly connected.

Prerequisites

■ You have started the (A)SCS instance of your SAP system.

■ You run the ENSMON tool from the host where you installed the Enqueue Replication Server.

Procedure

To check the status of the enqueue replication server enter the following command:

ensmon pf=<ERS_instance_profile> 2

where <ERS_instance_profile> is the profile created during the installation of the Enqueue

Replication Server.

■ If the enqueue replication server and the enqueue server are properly connected, the output is

similar to this:

Try to connect to host <Virtual (A)SCS host> service sapdp01 get replinfo request

executed successfully

Replication is enabled in server, repl. server is connected

Replication is active

...

■ If the enqueue replication server and the enqueue server are not properly connected, the output

is similar to this:

Try to connect to host <Virtual (A)SCS host> service sapdp01 get replinfo request

executed successfully

Replication is enabled in server, but no repl. server is connected

...

8.5.1.2 Monitoring the Lock Table During Failover with ENQT

With the following tests you monitor and check the fill status and the ID of the lock table using the

ENQT tool.

Prerequisites

■ You have started the (A)SCS instance of your SAP system.

■ You run the ENQT tool from the host where you installed the Enqueue Replication Server.

CAUTION

Only use the ENQT commands stated in this procedure otherwise you might damage the

enqueue server’s lock table.



2013-07-15 PUBLIC 123/164

Procedure

Monitoring the Lock Table Fill Status During Failover with ENQT

1. Use the following command to fill the lock table of the enqueue server with 20 locks:

enqt pf=<ERS_instance_profile> 11 20


Replication Server.

2. Monitor the fill status of the lock table with the following command:

enqt pf=<ERS_instance_profile> 20 1 1 9999

This command continuously reads the content of the enqueue server’s lock table and returns the

number of the table entries to the console.

3. Move the (A)SCS cluster group to another cluster node to simulate an enqueue server failover

while running the ENQT command.

The output is similar to this:

Number of selected entries: 20





Number of selected entries: 0 ( enqueue server fails over)

Number of selected entries: 20 ( enqueue server is running again)





...

4. Make sure that the lock count is the same before and after the failover.

Monitoring the Lock Table ID During Failover with ENQT

1. Monitor the lock table ID during the failover with the following command:


for (1..100000) | %{enqt pf=<ERS_instance_profile> 97}


for /l %i in (1,1,100000) do enqt pf=<ERS_instance_profile> 97


Replication Server.

2. Move the (A)SCS cluster group to another cluster node to simulate an enqueue server failover

while running the ENQT command.

The output is similar to this:



124/164 PUBLIC 2013-07-15

...

(Output before failover)

C:\WORK\HA\ENQU-Tests>enqt pf=BUG_ERS01_PCJ2EEV6 97

---REQ----------------------------------------------------------

EnqId: EnqTabCreaTime/RandomNumber = 25.10.2005 11:15:59 1130231759

/ 9288

...

(Output after failover)

C:\WORK\HA\ENQU-Tests>enqt pf=BUG_ERS01_PCJ2EEV6 97

---REQ----------------------------------------------------------

EnqId: EnqTabCreaTime/RandomNumber = 25.10.2005 11:15:59 1130231759

/ 9288

...

3. Make sure that the lock table ID (ENQID) is the same before and after the failover.

8.6 Additional Information

The following sections provide additional information about:

■ Moving Cluster Groups or Services and Applications [page 125]

■ Starting and Stopping the SAP System in a Failover Cluster Configuration [page 127].

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

When you reboot during the conversion to failover clustering, cluster resources fail over to the other

cluster node. Therefore, you have to return the system to the state it was in before the reboot, and

move the resources back to the original node.

To move the database, SAP, or disk cluster groups from one cluster node to the other, you use the

following:

■ PowerShell (Windows Server 2012)

■ Failover Cluster Manager (Windows Server 2008 (R2)

NOTE

As of Windows Server 2008 (R2) there are the following terminology changes:

■ Cluster groups are called services and applications (Windows Server 2008 (R2), or Roles (Windows

Server 2012))

We do not always use all names in this section.

■ The Cluster Administrator is now called Failover Cluster Manager.



2013-07-15 PUBLIC 125/164

Prerequisites

Windows Server 2008 (R2):

The services or applications you want to move are configured and are visible in the Failover Cluster

Manager.

Procedure

Moving Roles, or Services and Applications with the Failover Cluster Manager

To move the roles (Windows Server 2012), or services and applications (Windows Server 2008 (R2)),

proceed as follows:


1. To move a role, open PowerShell in elevated mode, and enter the following command:

move-clustergroup "<role name>"

2. Repeat these steps for each role that you want to move.


1. Start the Failover Cluster Manager with Start Administrative Tools Failover Cluster Manager .

2. In the Failover Cluster Manager, right click the service and application you want to move.

3. Choose Move this service or application to another node Move to <relevant node> .

4. Repeat the previous step for each service and application that you want to move.

NOTE

You can only move disks that are assigned to Services and Applications (Windows Server 2008 (R2)) or

Roles (Windows Server 2012).

The disks that are added to the cluster are automatically added to a group named Available

Storage. Although the groups Available Storage and Cluster Group exist in an failover cluster on Windows

Server 2008 (R2) or higher, they are not visible under Services and Applications (Windows Server 2008

(R2)) or Roles (Windows Server 2012). Therefore, you cannot move these groups with the Failover

Cluster Manager.

■ If you use Windows Server 2012 proceed as follows:

● To move Cluster Group, open PowerShell in elevated mode, and enter the following

command:

move-clustergroup "cluster group"

● To move Available Storage, open PowerShell in elevated mode, and enter the following

command:

move-clustergroup “Available Storage”

■ If you use Windows Server 2008 (R2) proceed as follows:

● To move Cluster Group, open a command prompt and enter:

cluster group “cluster group” /move

● To move Available Storage, open a command prompt and enter:

cluster group “Available Storage” /move



126/164 PUBLIC 2013-07-15

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

An SAP System in an HA configuration is typically configured into two HA groups: one cluster resource

group contains the database resources, the other group contains the SAP (A)SCS instance.

NOTE

When starting a whole SAP system, you first need to start the database instance and then the

remaining SAP instances.

When stopping a whole SAP system, you first need first to stop all SAP instances and then the

database instance.

With the SAP MMC, or SAPControl you can start and stop all SAP instances whether they are clustered

or not, except the database instance.

With certain HA administration tools (Cluster Administrator , Failover Cluster Manager , cluster.exe, or

PowerShell), you can only start or stop a clustered SAP instances, such as the (A)SCS instance or the

database instance.

Procedure

Starting and Stopping a Complete System or a Single Instance with SAP MMC or SAPControl

With the SAP MMC, or the command line tool SAPControl, you can start or stop the complete SAP

system or a single clustered or non-clustered SAP instance, except the database instance.

To start or stop the database instance, you have to use the tools described in “Starting and Stopping

the clustered (A)SCS and Database Instance”.

For more information about SAP MMC or SAPControl, see Starting and Stopping the SAP System [page 144].

NOTE

■ To use SAP MMC or SAPControl for starting or stopping a clustered SAP instance, the "SAP

<SID> <No> Service" resource of the clustered instance must be online. Therefore, SAP

recommends keeping the "SAP <SID><No> Service" cluster resource always online, and

using the SAP MMC or SAPControl to start or stop a clustered instance.

■ You can also start SAPControl in the PowerShell.

■ The SAP MMC is not available on the Server Core for Windows Server 2012.

Starting and Stopping the clustered (A)SCS and Database Instance

With certain HA administration tools, such as PowerShell (Windows Server 2012), and Failover Cluster

Manager (Windows Server 2008 (R2)), you can only start or stop a clustered SAP instances, such as the

(A)SCS instance or the database instance. For all other non-clustered instances, such as dialog instances

or the central instance, you must use the SAP MMC or SAPControl.



2013-07-15 PUBLIC 127/164

NOTE

You first have to start the (A)SCS instance and then the database instance, whereas you first have

to stop the database instance and then the (A)SCS instance.

■ Using PowerShell (Windows Server 2012)

To start or stop the clustered (A)SCS instance or the database instance with PowerShell do the

following:

1. To start the clustered database instance, open PowerShell in elevated mode, and enter the

following command:

start-clusterresource <database resource>

2. To start the clustered (A)SCS instance, open PowerShell in elevated mode, and enter the

following command:

start-clusterresource "SAP <SAPSID> <SAPSYSNR> Instance"

3. To stop the clustered (A)SCS instance, open PowerShell in elevated mode, and enter the

following command:

stop-clusterresource "SAP <SAPSID> <SAPSYSNR> Instance"

4. To stop the clustered database instance, open PowerShell in elevated mode, and enter the

following command:

stop-clusterresource <database resource>

■ Using Failover Cluster Manager (Windows Server 2008 (R2))

With the Failover Cluster Manager, you can only start or stop clustered instances such as the (A)SCS

instance or the database instance.

For all other non-clustered instances, such as dialog instances or the central instance, you must

use the SAP MMC or SAPControl.

To start or stop the clustered (A)SCS instance or the database instance with the Failover Cluster

Manager do the following:

1. Start the Failover Cluster Manager by choosing Start Administrative Tools Failover Cluster

Manager .

2. To start the database instance, right-click the database instance <database_resource>, and

choose Bring this resource online.

3. To start the (A)SCS instance, select the relevant service and application SAP <SAPSID>.

In the right-hand pane, under Other Resources, right-click the resource SAP <SAPSID>

<instance_no> Instance, and choose Bring this resource online.

4. To stop the (A)SCS instance, select the relevant service and application SAP <SAPSID>.

In the right-hand pane, under Other Resources, right-click the resource SAP <SAPSID>

<instance_no> Instance, and choose Take this resource offline.



128/164 PUBLIC 2013-07-15

5. To stop the database instance, right-click the database instance <database_resource>, and

choose Take this resource offline.End of: HA (MSCS) |



2013-07-15 PUBLIC 129/164

9 Additional Information

The following sections provide additional information about optional preparation, installation, and

post-installation tasks.

There is also a section describing how to delete an SAP system.

Planning

SAP Directories [page 131]

Preparation

■ Integration of LDAP Directory Services [page 137]

Installation

■ Installing the SAP Host Agent Separately [page 141]

Post-Installation

■ Starting and Stopping the SAP System [page 144]

■ Configuring the Windows Server 2008 R2 Firewall [page 145].

■ Implementing Single Sign-On with Microsoft Kerberos SSP [page 147]

■ SAP System Security on Windows [page 147]

■ Automatic Creation of Accounts and Groups [page 150]

Deleting an SAP System or SAP Instance

■ Deleting an SAP System [page 151]

9.1 SAP Directories

This section describes the SAP directories that the installer creates during the installation.


If you want to install a high-availability system, see also Directories in a Microsoft Failover Cluster

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

The installer automatically creates the following directories during the installation:

■ \usr\sap

This directory is created on the:

● Global host and shared with the network share sapmnt


9.1 SAP Directories

2013-07-15 PUBLIC 131/164


In a non-high-availability-system, you can install the central instance or the (A)SCS instance

on the global host or on any other host.End of: non-HA |


In a high-availability system, the ASCS instance is installed on the global host.End of: HA (MSCS) |

On global hosts, the \usr\sap directory contains general SAP software, global, and local

(instance-specific) data.

For this, the installer creates the global directory usr\sap\<SAPSID>\SYS, which physically

exists only once for each SAP system. It consists of the following subdirectories:

◆ global – contains globally shared data

◆ profile – contains the profiles for all instances

◆ exe – contains executable replication directory for all instances and platforms

● Local host and shared with the name saploc.


In a high availability system this directory is located on a local disk. You have at least two disk

drives with a usr\sap directory structure.End of: HA (MSCS) |

On local hosts, the \usr\sap\<SAPSID>\<instance_name> directory contains copies of the

SAP software and local (instance-specific) data.

During the installation of the primary application server or additional application server

instance host, and if not yet available, the installer also creates the \usr\sap\<DASID>\SYS

\global and \usr\sap\<DASID>\<instance_name> directory for the diagnostics agent on the

installation host, if not yet existing.

NOTE

◆ Since SAP traces for the instance are created in \usr\sap, make sure that there is

sufficient space available in this directory. Changes in SAP profiles can also affect the

disk space.

◆ The executables on the local host are replicated from those on the global host every

time the local instance is started. The SAP copy program sapcpe compares the

binaries in the <platform> directory on the global host and the binaries in the exe

directory on the application server. If the binaries in the exe directory are elder than

those in the <platform> directory, sapcpe replaces them with the newer version of

the global host. The sapcpe program also replicates the executables in the

\SMDA<instance_number\exe directory of the diagnostics agent.

Other application servers access the global data using the Universal Naming Convention (UNC)

path \\<SAPGLOBALHOST>\sapmnt. The SAP programs access their instance-specific data with the


9.1 SAP Directories

132/164 PUBLIC 2013-07-15

UNC path \\<SAPLOCALHOST>\saploc. If the UNC path points to a local directory, the local path

(and not the UNC path) is used to access the directory.

The parameters SAPGLOBALHOST and SAPLOCALHOST have the same values on the global host.


NOTE

Windows Server 2008 (R2) and higher:

In a high-availability system, file shares pointing to directories on shared disks are only visible

or can be accessed with the virtual host name of the cluster group the shared disks belong to.

This lets you have several shares with the same name pointing to different disks (multi-SID).

End of: HA (MSCS) |

■ \usr\sap\trans

The transport directory contains SAP software for the transport of objects between SAP systems.

The installer by default creates it on the SAPGLOBALHOST.

If you want to have it created on another host, or if you want to use an already existing transport

host of your SAP system landscape, you can specify another host during the installation. In this

case, you have to prepare that host to allow the new SAP system to use it as transport host. For

more information, see Preparing the SAP System Transport Host [page 50].

Directory Structure

The following figures show how the physical directory \usr\sap is shared on the global host in a

standard and in a distributed system. In both cases, the UNC paths are used as follows:

■ \\<SAPGLOBALHOST>\sapmnt to access global directories

■ \\<SAPLOCALHOST>\saploc to access local instance-specific data

There is also a figure showing the directory structure of the diagnostics agent.

NOTE

There are the following instance names available in an SAP system:

Central services instance for ABAP: ASCS<Instance_Number>.

Primary application server instance: DVEBMGS<Instance_Number>

Additional application server instance: D<Instance_Number>

Diagnostics agent instance: SMDA<Instance_Number>

Enqueue Replication Server instance: ERS<Instance_Number> (optional in a non-HA system)


9.1 SAP Directories

2013-07-15 PUBLIC 133/164

Figure 13: Directory Structure on the Global Host in a Standard (Central) ABAP System

Figure 14: Directory Structure for a Distributed ABAP System


9.1 SAP Directories

134/164 PUBLIC 2013-07-15


Figure 15: Directory Structure for a High-Availability ABAP SystemEnd of: HA (MSCS) |

Figure 16: Directory Structure of the Diagnostics Agent

9.2 Checking and Changing the Paging File Settings on Windows Server 2012

This section describes how to check and change the paging file size on Windows Server 2012 with

PowerShell.

The PowerShell commands also work in previous Windows versions where PowerShell is available.



2013-07-15 PUBLIC 135/164

NOTE

Some paging file operations require a reboot of the server to activate the changes you made. Wmi-

commands do not indicate whether a reboot is required or not. Therefore, we recommend

rebooting your system every time you change the paging file settings with PowerShell.

Prerequisites

Always start the PowerShell in elevated mode (run as administrator).

Procedure

Checking the Size of a Paging File

1. Start Windows PowerShell.

2. Check whether the default value Automatic manage pagefile size for all devices is activated.

NOTE

We do not support automatically managed page file sizes.

To check this, enter the following command:

(Get-WmiObject Win32_Pagefile) –eq $null

If Automatic manage pagefile size for all devices is enabled, the output value is True.

If necessary, disable Automatic manage pagefile size for all devices with the following command:

$sys = Get-WmiObject Win32_Computersystem –EnableAllPrivileges

$sys.AutomaticManagedPagefile = $false

$sys.put()

3. Check the size of the paging files with the following command:

Get-WmiObject WIN32_Pagefile | Select-Object Name, InitialSize, MaximumSize,

FileSize

The output looks like the following:

SYNTAX

Name InitialSize MaximumSize FileSize---- ----------- ----------- --------C:\pagefile.sys 0 0 41943040000E:\pagefile.sys 40000 80000 41943040000

In this example, in the first line, the InitialSize and MaximumSize values of a paging file are 0, which

means that the paging file size is system managed (not recommended).

In the second line, the paging file size has a minimum and a maximum size (recommended).

Changing the Size of a Single Paging File

Changing the InitialSize and MaximumSize values of a paging file to a size other than 0, will automatically

switch off system managed size.

In the following example, we change the size of the paging file on C: to the InitialSize of 40 GB and to

the MaximumSize of 80 GB.

Use the following commands in a PowerShell:



136/164 PUBLIC 2013-07-15

$Pagefile = Get-WmiObject Win32_PagefileSetting | Where-Object {$_.name -eq “C:

\pagefile.sys”}

$Pagefile.InitialSize = 40000

$Pagefile.MaximumSize = 80000

$Pagefile.put()

Typically, you choose the same value for InitialSize and MaximumSize.

NOTE

The sum of all paging files InitialSize values must be equal to or higher than the value recommended

for your SAP system.

Creating a Second Paging File on Another Disk

You might want to create a second or additional paging files to improve system performance, or if your

disk does not have enough space.

To do so, enter the following commands in a PowerShell:

$Pagefile = Get-WmiObject Win32_PagefileSetting

$pagefile.Name = “E:\pagefile.sys”

$pagefile.Caption = “E:\pagefile.sys”

$pagefile.Description = “’pagefile.sys’ @ E:\”

$pagefile.SettingID =”pagefile.sys @ E:”

$pagefile.InitialSize = 80000

$pagefile.MaximumSize = 80000

$pagefile.put()

Deleting a Paging File on a Specific Device

To delete a paging file, enter the following commands in a PowerShell:

$pagefile = Get-WmiObject Win32_PagefileSetting | Where-Object {$_.name -eq “E:

\pagefile.sys”}

$pagefile.delete()

9.3 Integration of LDAP Directory Services

This section explains the benefits of using the SAP system with the Lightweight Directory Access

Protocol (LDAP) directory and gives an overview of the configuration steps required to use an SAP

system with the directory.

LDAP defines a standard protocol for accessing directory services, which is supported by various

directory products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory services

enables important information in a corporate network to be stored centrally on a server. The advantage

of storing information centrally for the entire network is that you only have to maintain data once,

which avoids redundancy and inconsistency.



2013-07-15 PUBLIC 137/164

If an LDAP directory is available in your corporate network, you can configure the SAP system to use

this feature. For example, a correctly configured SAP system can read information from the directory

and also store information there.

NOTE

The SAP system can interact with the Active Directory using the LDAP protocol, which defines:

■ The communication protocol between the SAP system and the directory

■ How data in the directory is structured, accessed, or modified

If a directory other than the Active Directory also supports the LDAP protocol, the SAP system

can take advantage of the information stored there. For example, if there is an LDAP directory on

a UNIX or Windows server, you can configure the SAP system to use the information available

there. In the following text, directories other than the Active Directory that implement the LDAP

protocol are called generic LDAP directories.

CAUTION

This section does not provide information about the use of LDAP directories with the LDAP

Connector. For more information about using and configuring the LDAP Connector for an ABAP

system, see the SAP Library at:


English Security Identity Management User and Role Administration of AS ABAP Configuration of User

and Role Administration Directory Services LDAP Connector

PrerequisitesYou can only configure the SAP system for Active Directory services or other LDAP directories if these

are already available on the network. As of Windows 2000 or higher, the Active Directory is

automatically available on all domain controllers. A generic LDAP directory is an additional component

that you must install separately on a UNIX or Windows server.

FeaturesIn the SAP environment, you can exploit the information stored in an Active Directory or generic

LDAP directory by using:

■ SAP Logon

■ The SAP Microsoft Management Console (SAP MMC)

For more information about the automatic registration of SAP components in LDAP directories and

the benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information in

Directory Services at:


SAP Logon

Instead of using a fixed list of systems and message servers, you can configure the SAP Logon in the

sapmsg.ini configuration file to find SAP systems and their message servers from the directory. If you



138/164 PUBLIC 2013-07-15

http://help.sap.com


configure SAP logon to use the LDAP directory, it queries the directory each time Server or Group selection

is chosen to fetch up-to-date information on available SAP systems.

To use LDAP operation mode, make sure that the sapmsg.ini file contains the following:

[Address]

Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

Distinguish the following cases:

■ If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For more

information, see the SAP system profile parameter ldap/options.

■ You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either of

the following is true:

● The client is not located in the same domain forest as the Active Directory

● The operating system does not have a directory service client (Windows NT and Windows 9X

without installed dsclient).

For more information, see the SAP system profile parameter ldap/servers.

■ For other directory services, you can use LDAPnode to specify the distinguished name of the SAP

root node. For more information, see the SAP system profile parameter ldap/saproot.

SAP MMC

The SAP MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from

a central location. It is automatically set up when you install an SAP system on Windows. If the SAP

system has been prepared correctly, the SAP MMC presents and analyzes system information that it

gathers from various sources, including the Active Directory.

Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can

read system information straight from the directory that automatically registers changes to the system

landscape. As a result, up-to-date information about all SAP application servers, their status, and

parameter settings is always available in the SAP MMC.

If you need to administer distributed systems, we especially recommend that you use the SAP MMC

together with Active Directory services. You can keep track of significant events in all of the systems

from a single SAP MMC interface. You do not need to manually register changes in the system

configuration. Instead, such changes are automatically updated in the directory and subsequently

reflected in the SAP MMC.

If your SAP system is part of a heterogeneous SAP system landscape that comprises systems or instances

both on UNIX and Windows operating systems, you can also use the SAP MMC for operating and

monitoring the instances running on UNIX.



2013-07-15 PUBLIC 139/164

NOTE

You can also use the SAP Management Console (SAP MC) for administering and monitoring SAP

systems from a central location. For more information about the SAP MC and about how to

configure it to access LDAP directories, see the documentation SAP Management Console at:


English Application Server Administering Application Server Java Administration Administration Tools

SAP Management Console

Configuration Tasks for LDAP Directories

This section describes the configuration tasks you have to perform for the Active Directory or other

(generic) LDAP directories.

Configuration Tasks for Active Directory

To enable an SAP system to use the features offered by the Active Directory, you must configure the

Active Directory so that it can store SAP system data.

To prepare the directory, you use the installer to automatically:

■ Extend the Active Directory schema to include the SAP-specific data types

■ Create the domain accounts required to enable the SAP system to access and modify the Active

Directory. These are the group SAP_LDAP and the user sapldap.

■ Create the root container where information related to SAP is stored

■ Control access to the container for SAP data by giving members of the SAP_LDAP group permission

to read and write to the directory

You do this by running the installer and choosing <Your SAP product> Software Life-Cycle Options

LDAP Registration Active Directory Configuration .

NOTE

You have to perform the directory server configuration only once. Then all SAP systems that

need to register in this directory server can use this setup.

Configuration Tasks for Generic LDAP Directories

To configure other LDAP directories, refer to the documentation of your directory vendor. The

Installation Master DVD contains schema extensions for directory servers Netscape/iPlanet

(ldregns4.txt) and OpenLDAP slapd (ldregslapd.schema). Both files are located in the directory

\DATA_UNITS\IM_<platform>\COMMON\ADS. After you have applied the schema extension, you need to

create a root container to store the SAP-related information and create a directory user that the SAP

application server can use to write information to the directory.

For more information about how to set up a Netscape/iPlanet directory server, see the documentation

SAP System Information in Directory Services at: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/

docs/library/uuid/ d0a0d051-eae2-2b10-e1ac-f3a7f6494c53



140/164 PUBLIC 2013-07-15

http://help.sap.com

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0a0d051-eae2-2b10-e1ac-f3a7f6494c53

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0a0d051-eae2-2b10-e1ac-f3a7f6494c53

Enabling the SAP System LDAP Registration

Once you have correctly configured your directory server, you can enable the LDAP registration of the

SAP system by setting some profile parameters in the default profile.

To do this, run the installer once for your system and choose <Your SAP product> Software Life-Cycle

Options LDAP Registration LDAP Support

If you use a directory server other than Microsoft Active Directory and/or non-Windows application

servers, you have to store the directory user and password information by using ldappasswd

pf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and is therefore

valid for all application servers. After restarting all application servers and start services, the system is

registered in your directory server. The registration protocols of the components are dev_ldap*. The

registration is updated every time a component starts.

9.4 Installing the SAP Host Agent Separately

This procedure tells you how to install a host agent separately.

The host agent is automatically installed during the installation of all new SAP system instances based

on SAP NetWeaver 7.1 or higher. You only need to install a host agent separately in the following

cases if you want to manage a host that does not have an SAP instance or component.

Figure 17: Host Agent

The host agent contains the following elements:


■ The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)


9.4 Installing the SAP Host Agent Separately

2013-07-15 PUBLIC 141/164

■ The sapacosprep executable of the Adaptive Computing Infrastructure

■ The operating system collector saposcol

NOTE

The installed programs are automatically started when the host is booted.

ProcedureYou have to perform the following steps on the host where you install the host agent separately:

1. You check hardware and software requirements [page 20].



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

For more information, see Preparing the Installation Media [page 51].

5. You start the installer [page 57] to install the host agent.

On the Welcome screen, choose Software Life-Cycle Options Additional Preparation Options Host

Agent .

6. You perform the following post-installation steps:

1. Check whether the installed services are available as follows:

1. Log on as user sapadm.

2. Check whether the following services are available:


■ The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host

mode)

NOTE

2. You configure the monitoring architecture with the installed host agent as

described in the SAP Library at:

http://help.sap.com SAP NetWeaver <Release> Application Help Function-

Oriented View: English Solution Life Cycle Management Solution Monitoring System

Monitoring with CCMS Infrastructure of the NetWeaver Management Agents

9.5 Splitting Off a Central Services Instance for ABAP from an Existing Primary Application Server Instance


NOTE

This installation option is not supported in a high-availability system.

End of: HA (MSCS) |

With the installation option Split Off ASCS Instance from existing Primary Application Server Instance, you can

move the message server and the enqueue work process from an existing primary application server



142/164 PUBLIC 2013-07-15

http://help.sap.com

instance to a newly installed central services instance for ABAP (ASCS instance). The new ASCS instance

is installed while the split is done. Optionally, you can install an enqueue replication server (ERS)

instance with the ASCS instance.

Prerequisites

The existing SAP system of the primary application server instance must meet the following

requirements:

■ It was upgraded to an SAP system based on SAP NetWeaver 7.3 or higher

■ It does not yet have an ASCS instance

Before the Split

The primary application server instance includes:

■ ABAP dispatcher and work processes (dialog, batch, spool, enqueue, or update)

■ Gateway

■ Internet communication manager (ICM)

■ Internet graphics service (IGS)

■ ABAP message server

After the Split

A central services instance for ABAP (ASCS instance) has been split off from the existing primary

application server instance.

The primary application server instance now includes:

■ ABAP dispatcher and work processes (dialog, batch, spool, or update)

■ Gateway

■ Internet communication manager (ICM)

■ Internet graphics service (IGS)

The newly created central services instance for ABAP (ASCS instance) includes:

■ ABAP message server

■ ABAP standalone enqueue server

The ABAP enqueue work process is now replaced with the ABAP standalone enqueue server.

Procedure

1. Plan the basic parameters, as described in Basic SAP System Installation Parameters [page 34]:

■ Choose an instance number for the ASCS instance to be created.

■ Note that the message server port is not changed during the split.

2. Check the hardware and software requirements for the ASCS instance and the ERS instance to be

created as described in Hardware and Software Requirements [page 20].

3. Specify basic SAP system parameters [page 34] for the ASCS instance and the ERS instance to be created.

4. Start the installer as described in Running the Installer [page 57].



2013-07-15 PUBLIC 143/164

5. On the Welcome screen, choose <Your SAP Product> Additional SAP System Instances Split Off ASCS

Instance from existing Primary Application Server Instance .

6. Follow the instructions on the installer screens and enter the required parameters.

NOTE

To find more information on each parameter during the input phase of the installation,

position the cursor on the required parameter and choose F1 .

After you have entered all requested input parameters, the installer displays the Parameter Summary

screen. This screen shows both the parameters that you entered and those that the installer set by

default. If required, you can revise the parameters before starting the installation.

7. To start the installation, choose Start.

The installer starts the installation and displays the progress of the installation. When the

installation has successfully completed, the installer shows the dialog Execution of Split Off ASCS

Instance from existing Primary Application Server Instance has completed.

8. Check whether you can start and stop the SAP system [page 144] with the newly created ASCS instance

and SCS instance.

9. Check whether you can log on to the application server [page 72].

10. Ensure user security [page 80] for the operating system users of the newly created ASCS instance and

ERS instance if they were created by the installer.

9.6 Starting and Stopping the SAP System

You use this procedure to check that you can start and stop the SAP system or single instances after

the installation with the SAP Microsoft Management Console (SAP MMC) or SAPControl.

NOTE


You can only use the SAP MMC or SAPControl to start the database instance. To stop the database

instance, you must use the relevant database administration tools.End of: non-HA |


In an HA system, you can neither start nor stop the database instance. For more information, see

Starting and Stopping the SAP System in an HA Configuration [page 127]End of: HA (MSCS) |

Prerequisites

The user who wants to start and stop the SAP system with the SAP MMC, must be a member of the

local administrators group.


9.6 Starting and Stopping the SAP System

144/164 PUBLIC 2013-07-15

Procedure

Starting and Stopping the SAP System with the SAP MMC

With the SAP MMC, you can start or stop installed SAP instances # except the database instance #

locally on the host that you are logged on to. You can also start and stop the diagnostics agent with

the SAP MMC. If the SAP MMC is configured for central system administration, you can start or stop

the entire system from a single host.

NOTE

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

■ The SAP MMC is not available on Server Core for Windows Server 2012.

For more information about the SAP MMC, see the SAP Library at:


Solution Life Cycle Management SAP Microsoft Management Console: Windows .

To start or stop the SAP system with the SAP MMC, perform the following steps:

Starting and Stopping the SAP System with SAPControl

To start or stop the SAP system with SAPControl (sapcontrol.exe), perform the following steps:

■ To start or stop the complete SAP system, except the database instance with SAPControl, open a

PowerShell in elevated mode, and enter the following command:

sapcontrol -prot PIPE -nr <Instance No.> -function StartSystem

sapcontrol -prot PIPE -nr <Instance No.> -function StopSystem

■ To start or stop a single instance with SAPControl, open a PowerShell in elevated mode, and enter

the following command:

sapcontrol -prot PIPE -nr <Instance No.> -function Start

sapcontrol -prot PIPE -nr <Instance No.> -function Stop

9.7 Configuring the Windows Server 2008 R2 Firewall

The Windows Server 2008 R2 firewall is configured to allow only a small set of Windows-specific inbound

IP connections.

Therefore, SAP recommends that you do not turn on the Windows firewall after you have installed

your SAP system. Instead, we recommend that you secure network access to your SAP system with the

physical firewall or a router Access Control List (ACL) within your datacenter.

If, for some reason, you want to use the Windows Server firewall, you have to configure the Windows

firewall and define a set of Inbound Rules for the TCP/IP port numbers that are used by your system.

Otherwise, your SAP system might not operate.

For more information about the port numbers used, see the documentation TCP/IP Ports Used by SAP

Applications at:



2013-07-15 PUBLIC 145/164

http://help.sap.com

http://service.sap.com/security Security in Detail Infrastructure Security

Ports listed with the default value Not active in this document are not configured.


CAUTION

In a high-availability system, you have to configure the firewall on all MSCS nodes.

End of: HA (MSCS) |

Prerequisites

You turn on the disabled firewall [page 46] as follows:


2. Right-click Windows Firewall with Advanced Security and choose Properties.

3. Set the Firewall state to On.

Procedure

This procedure describes how to set Inbound Rules for the ports of an installed ABAP server that was

installed with instance number 00.


2. Right-click Inbound Rules and choose New Rule.

The New Inbound Rule Wizard starts.

3. For Rule Type, select Port and choose Next.

4. For Protocol and Ports, select port type TCP or UDP depending on the port type used.

Select Specific local ports, and enter the port numbers for which you want to apply the new rule.

Select Specific local ports, and enter the port numbers for which you want to apply the new rule, for

example:

3200,3300,4800,8000,3600,50013,50000

Note that the final two digits of the port number correspond to the instance number.

5. Choose Next.

6. For Action, select Allow the connection, and choose Next.

7. For Profile, keep Domain, Private and Public selected, and choose Next.

For more information, see the link Learn more about profiles on this screen.

8. Enter the Name, for example SAP ABAP Server 00, and Description for the new rule.

9. Choose Next.

10. Choose Finish to save the rule.

The new inbound rule appears in the Inbound Rules list. To modify the settings, right-click on the

rule and choose Properties.

NOTE

If you want to use, for example, a different IP scope for port 50013, which is used by the connection

SAP Start Service – SAP Management Console, you can restrict the IP access to a small number



146/164 PUBLIC 2013-07-15

http://service.sap.com/security

of SAP administrators. Then delete this port from the SAP ABAP Server 00 rule and create a new

rule for port 50013 with a more restrictive scope.

9.8 Implementing Single Sign-On with Microsoft Kerberos SSP for Your SAP System

Kerberos Single Sign-On (SSO) is a secure method of logging on to the SAP system that simplifies the

logon procedure.

When your system is configured for SSO, an authorized user who has logged on to Windows can access

the SAP system simply by selecting it in the SAP logon window or clicking the shortcut. There is no

need to enter the SAP system user name and password when you log on to your SAP system with SAP

GUI. SSO makes it significantly easier for you to manage SAP system users. The Microsoft Kerberos

Security Service Provider (SSP) provides secure authentication plus encryption of the network

communication.

Procedure

For more information about implementing Kerberos SSO for your SAP system, see:


Security Network and Transport Layer Security Secure Network Communications (SNC) Configuring the

Communication Partners to Use SNC Special Cases

9.9 SAP System Security on Windows

In a standard SAP system installation, the installer automatically performs all steps relevant for security.

Although the installer makes sure that the system is protected against unauthorized access, you must

still check that no security breaches can occur.

For central and straightforward administration of the SAP system, you have to install distributed SAP

systems with multiple application servers (central or additional application server instances) in a

Windows domain. This section describes the user accounts and groups that the installer creates during

a domain installation and shows how these are related to the SAP directories.

User Accounts

The installer creates the following accounts for SAP system administration:

■ <sapsid>adm

This is the SAP system administrator account that enables interactive administration of the system.

■ SAPService<SAPSID>

This is the user account that is required to start the SAP system. It has the local user right to log

on as a service.


9.8 Implementing Single Sign-On with Microsoft Kerberos SSP for Your SAP System

2013-07-15 PUBLIC 147/164

http://help.sap.com

The advantage of the additional SAPService<SAPSID> account is that it does not allow interactive

logon, which prevents abuse of the account. Therefore, you do not need to set an expiration date

for the password and you do not have to set the option user must change password at next logon.

■ sapadm

This is the user for the host agent. By default it is a local user and not a member of the local

Administrators group. You can change this user into a domain user on the parameter summary

screen. For security reasons, however, SAP strongly recommends to create this user as a local user.

The host agent contains all of the required elements for centrally monitoring any host with the

Alert Monitor or the SAP NetWeaver Administrator.

■ <dasid>adm

This is the diagnostics agent administrator user account that is required for the administration of

the diagnostic agent. By default it is a local user and not a member of the local Administrators

group. You can change this user into a domain user on the parameter summary screen. For security

reasons, however, SAP strongly recommends to create this user as a local user.

■ SAPService<DASID>

This is the user account that is required to start the diagnostic agent. It has the local user right to

log on as a service.

Groups

The only function of a domain group is to group users at the domain level so that they can be placed

in the appropriate local groups.

Only local groups are created and maintained on each local host. A local group can only be given

permissions and rights to the system where it is located. The system is part of a particular domain, and

the local group can contain users and domain (global) groups from this domain.

The installer creates the following domain and local groups during a domain installation:

■ SAP_<SAPSID>_GlobalAdmin

This domain (global) group is a domain-level SAP administration group for organizing SAP system

administrators.

■ SAP_<DASID>_GlobalAdmin

This domain group for the diagnostic agent is only created if you create the diagnostic agent user

<dasid>adm as a domain user.

■ SAP_SAP_GlobalAdmin

This domain group for the host agent is only created if you create the host agent user sapadm as a

domain user.

■ SAP_<SAPSID>_LocalAdmin

This local group is created on each host.

■ SAP_<DASID>_LocalAdmin



148/164 PUBLIC 2013-07-15

If you create the diagnostic agent user as domain user, the group SAP_<DASID>_LocalAdmin is also

created.

■ SAP_SAP_LocalAdmin

If you create the host agent user as domain user, the group SAP_SAP_LocalAdmin is also created.

■ SAP_LocalAdmin

This local group is created on all hosts, but is particularly important for the transport host.

Members of the group have full control over the transport directory (\usr\sap\trans) that allows

transports to take place between systems.

The SAP_<SAPSID>_GlobalAdmin groups of all the SAP systems that are part of the transport

infrastructure are added to the SAP_LocalAdmin group. Therefore, the users <sapsid>adm and

SAPService<SAPSID> of all systems in the transport infrastructure are members of the

SAP_LocalAdmin group and have the required authorizations necessary to initiate and execute

transports.

SAP Directories

The installer protects the SAP directories under \usr\sap\<SAPSID> by only granting the group

SAP_<SAPSID>_LocalAdmin full control over these directories.

The following figure illustrates the users and groups that are created by The installer for the

<sapsid>adm and SAPService<SAPSID> users in a system infrastructure consisting of two SAP systems.

Figure 18: User Groups and Accounts



2013-07-15 PUBLIC 149/164

NOTE

An access control list (ACL) controls access to SAP system objects. For maximum security in the

SAP system, only the following are members of all SAP system object ACLs:

■ Local group SAP_<SAPSID>_LocalAdmin

■ Group Administrators

■ Account SYSTEM

More Information

Automatic Creation of Accounts and Groups [page 150]

9.10 Automatic Creation of Accounts and Groups

The installer automatically creates the accounts and groups required for the secure operation of the

SAP system with Windows during the installation, as described in SAP System Security on Windows [page

147].

Features

The following figures show the steps that the installer performs to create the users and groups and

assign the required rights to SAP directories.

The first figure shows the users that are created during a domain installation, with the diagnostic agent

and host agent operating system users being local users.

Figure 19: Creating Users and Groups


9.10 Automatic Creation of Accounts and Groups

150/164 PUBLIC 2013-07-15

Figure 20: Assigning Rights to SAP Directories

9.11 Deleting an SAP System or Single Instances

This section describes how to delete a complete SAP system or single SAP instances with the Uninstall

option of the installer.

Note the following when deleting an SAP system or single instances:

■ When you uninstall an SAP system, the database content is also deleted.

■ You cannot delete an SAP system remotely.

■ During the uninstall process, all file systems and subdirectories of the selected SAP system or single

instance are deleted. Before you start uninstalling, make sure that you have saved a copy of all files

and directories that you want to keep to a secure location.

■ The uninstall process is designed to remove as much as possible of the SAP system to be deleted. If

an item cannot be removed, a message informs you that you have to remove this item manually.

You can do this either at once or after the uninstall process has finished. As soon as you confirm

the message, the uninstall process continues.

Prerequisites

■ You have installed your SAP system with standard SAP tools according to the installation

documentation.

■ You are logged on with a user account that has the required authorization to run the installer and

the SAP system. For more information, see Required User Authorization for Running the Installer [page 48].



2013-07-15 PUBLIC 151/164

CAUTION

Do not use the user <sapsid>adm to delete the SAP system.

■ Make sure that the SAP system, or single instance, or standalone engine, or optional standalone

unit to be deleted is down and that you are not logged on as one of the SAP system users. If there

is a lock on one of the SAP system objects, this breaks the uninstall. Make also sure that all SAP-

related processes are stopped.

NOTE

You do not have to stop the host agent. The host agent is stopped automatically during the

uninstall process.

■ When starting the uninstall, make sure that there are no SAP system user sessions still open.

Procedure

1. Start the installer as described in Running the Installer [page 57].

2. On the Welcome screen, choose:

Generic Installation Options <Database> Uninstall Uninstall – SAP Systems or Single Instances

3. Follow the instructions in the installer screens to delete a complete SAP system or single instances.

NOTE

For more information about the input parameters, place the cursor on the relevant field and

press F1 in the installer.

The following table provides information about deleting a complete system or single instances

with the installer.

Deletion of Remarks

Standard system You can delete a standard system (where all instances reside on the same host) in one installer run.

Distributed or high-availability system

If you want to delete a distributed or high-availability system, you have to run the installer to delete the required instances locally on each of the hosts belonging to the SAP system in the following sequence:1. Additional application server instances, if there are any

CAUTION

Do not select checkbox Uninstall all instances of the SAP system from this host if you do not want to uninstall the complete SAP system or standalone engine. For example, do not select this checkbox if you only want to uninstall an additional application server instance of an existing SAP system distributed over several hosts. Otherwise the contents of mounted global directories under /<sapmnt>/<SAPSID>/ , such as instance profiles and kernel executables, are also deleted.

2. Primary application server instanceIf the installer stops responding while trying to delete the primary application server instance, close the installer with Cancel and Exit. Log off and log on again. To complete the uninstall process of the primary application server instance, restart the installer.

3. Database instance



152/164 PUBLIC 2013-07-15

Deletion of RemarksSince the installer only stops local instances automatically, make sure that before deleting the database instance of a distributed system, you stop all remaining instances. You must stop the instance with the message server only after having entered all installer parameters for the deletion of the database instance.To delete the database instance or one or more database schemas, choose one of the following options: ■ Drop database

Select this option if you want to drop the database. ■ Select the database schema that you want to delete

Select this option if you want to delete the Java part of an SAP system (ABAP+Java or Java Add-In).

4. Central services instance (SCS) and – if it exists – the related enqueue replication server instance

5. Central services instance for ABAP (ASCS) and – if it exists – the related enqueue replication server instance

NOTE

To delete system directories mounted from an NFS server, make sure that you run the installer on the NFS server.

Additional application server

If you want to delete additional application server instances of an existing SAP system, you have to run the installer to delete them locally on each additional application server instance host.

Standalone host agent The host agent is automatically uninstalled from a host together with the last remaining SAP system instance.If you want to uninstall a standalone host agent, deselect Profiles Available and select Uninstall Standalone Host Agent on the General SAP System Parameters screen.

Diagnostics agent If you want to delete a diagnostics agent instance, enter the location of the profile directory of the diagnostics agent that you want to uninstall on the General SAP System Parameters screen:<Drive>:\usr\sap\<DASID>\SYS\profile

4. When you have finished, delete the relevant directory structure on the global host.

5. Delete the local user group SAP_<SAPSID>_LocalAdmin manually as follows:

1. Windows Server 2012:

Open a PoweShell in elevated mode and enter the following command:

net localgroup SAP_<SAPSID>_LocalAdmin /delete

2. Windows Server 2008 (R2):

Choose Start Programs Administrative Tools Computer Management

Choose Local Users and Groups Groups

Right-click the local group SAP_<SAPSID>_LocalAdmin and choose Delete.

6. If required, you can delete the directory \usr\sap\trans and its contents manually.

The installer does not delete \usr\sap\trans because it might be shared.

7. To remove obsolete SLD data, see the following document:



2013-07-15 PUBLIC 153/164

http://scn.sap.com/docs/DOC-8516 How-to Manage House-Cleaning in the System Landscape Directory

– Duplicate System Entries



154/164 PUBLIC 2013-07-15


A Appendix

A.1 Using PowerShell

For Windows Server 2012, SAP only uses Windows PowerShell to run and describe Windows commands.

Windows PowerShell is a powerful tool integrated in the Windows operating system. It uses object-

oriented methodology, which allows fast and stable script development.

For more information about the Windows PowerShell, see:

http://technet.microsoft.com/en-us/scriptcenter/dd742419.aspx

There you can find links to the online help, online documentation, scripting repository, downloads,

and blogs.

If you want to use the PowerShell feature, note the following:


Windows Server 2012 contains PowerShell 3.0.

■ Windows Server 2008 R2

Windows Server 2008 R2 contains PowerShell 2.0.

You can update to PowerShell 3.0 (search the internet for Windows Management Framework 3.0).


Windows Server 2008 contains PowerShell 1.0.

For more information about PowerShell 2.0, see http://support.microsoft.com/kb/968929.

You have to activate the PowerShell feature with Start Administrative Tools Server Manager

Features .

You can update to PowerShell 3.0 (search the internet for Windows Management Framework 3.0).

How to Start PowerShell

CAUTION

Make sure that you start the PowerShell in administrator mode.


Open the command prompt and enter the command:

powershell.exe

To start PowerShell on Windows Server 2008 (R2), you have the following options:

■ From the command prompt, by entering the command:

powershell.exe

■ From the Start Menu:

● PowerShell 1.0:

A Appendix


2013-07-15 PUBLIC 155/164

http://technet.microsoft.com/en-us/scriptcenter/dd742419.aspx

http://support.microsoft.com/kb/968929

Choose Start All Programs Windows PowerShell 1.0 Windows PowerShell .

● PowerShell 2.0:

Choose Start All Programs Windows PowerShell Windows PowerShell .

How to Work with PowerShell

Most commands that are used in cmd.exe are also available in the PowerShell (defined as aliases).

You can use well-known commands, such as cd, type, copy, move, mkdir, delete, rmdir. There is also

online help available, which you can access by typing the command: help (or help <command>).

This is a list of differences between PowerShell and cmd.exe:

■ Before you can run PowerShells scripts (text files with the file extension .ps1 that contain

PowerShell statements), you might have to change the default security setting to allow the

execution of non-signed scripts as follows:

set-executionpolicy ("unrestricted")

■ By default, when double-clicking PowerShell scripts (.PS1 files) in the Windows explorer, this does

not execute the script as is the default for .cmd files, but opens the script in an editor. If you want

to activate automatic script execution after a double-click, you have to change the value

HKEY_CLASSES_ROOT\Microsoft.Powershellscript.1\Shell\Open\Command from notepad.exe

to the full path of the PowerShell executable.

■ The output of PIPE commands is not just a stream of characters (strings) but a stream of objects.

You can easily access the properties and methods for these objects (see the process list DLL example

below).

■ The current working directory is not part of the directory search path that the PowerShell looks

at for scripts and programs. The PowerShell only searches directories listed in the environment

variable path. Therefore, you might have to run a local program with ./sapcontrol.exe or specify

its full path.

■ You can use the UNIX-like directory delimiters, such as cd /usr/sap/C11.

■ You can have your current working directory in a UNC path (cd \\sapglobalhost\sapmnt).

■ The shell distinguishes between environment variables and shell variables:

● Use of shell variables:

Definition: $x="hello"

Reference: write-host $x

● Use of an environment variable:

Definition: $env:x="hello"

Reference: write-host $env:x

■ The PowerShell has an interesting container concept called ps-drives. Within ps-drives you can

navigate in other objects, such as the registry or shell internal lists in the same way as you typically

navigate in a file system (cd, dir, del, and so on).

dir env: to get a list of environment variables

A Appendix


156/164 PUBLIC 2013-07-15

dir variable: to get the list of shell variables

dir HKLM: to get a list of registry keys in HKEY_LOCAL_MACHINE

get-psdrive to get a list of available ps-drives

■ Windows PowerShell has full access to the .NET runtime. You can directly access missing functions

in the PowerShell via .NET.

■ With Windows PowerShell, you can create GUI-class user interfaces using Windows forms.

A.2 Online Information

More information is available online as follows.

Documentation

Description Internet Address Title

Master Guide for SAP NetWeaver <Release>

http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver <Release>

Installation

Master Guide – SAP NetWeaver <Release>

System Copy for SAP systems based on SAP NetWeaver <Release>

http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver <Release>

Installation Installation – SAP NetWeaver Systems

Copying Systems Based on NW 7.1 or Higher – SW Prov.Mgr. 1.0

Front End installation http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver <Release>

Installation Installation – Clients SAP Front End Installation Guide

SAP Front End Installation Guide <Current Release>

General Quick Links

Description Internet Address

SAP Help Portal http://help.sap.com/adaptive-server-enterprise

SAP NetWeaver Library in SAP Help Portal

http://help.sap.com SAP NetWeaver <Release>

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

Forums, blogs, and general information related to SAP on Sybase ASE

http://scn.sap.com/community/sybase-ase

Product Availability Matrix (PAM) for supported operating system releases


General information, forums, and blogs about information related to SAP on Windows

http://sdn.sap.com/irj/sdn/windows

Release notes http://service.sap.com/releasenotes

Unicode SAP systems and their availability

http://service.sap.com/unicode

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

A Appendix


2013-07-15 PUBLIC 157/164




http://help.sap.com/adaptive-server-enterprise

http://help.sap.com


http://scn.sap.com/community/sybase-ase


http://sdn.sap.com/irj/sdn/windows

http://service.sap.com/releasenotes

http://service.sap.com/unicode

http://service.sap.com/sizing

Description Internet Address

SAP NetWeaver capabilities http://sdn.sap.com/irj/sdn/netweaver

Life-cycle management for SAP NetWeaver

http://sdn.sap.com/irj/sdn/lcm

Landscape design for SAP NetWeaver

http://sdn.sap.com/irj/sdn/landscapedesign

Application management for SAP NetWeaver

http://sdn.sap.com/irj/sdn/applicationmanagement

System Landscape Directory http://sdn.sap.com/irj/sdn/nw-sld

Software logistics for SAP NetWeaver

http://sdn.sap.com/irj/sdn/softwarelogistics

SAP NetWeaver operations http://sdn.sap.com/irj/sdn/operations

Security for SAP NetWeaver http://sdn.sap.com/irj/sdn/security

NOTE

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

A Appendix


158/164 PUBLIC 2013-07-15

http://sdn.sap.com/irj/sdn/netweaver

http://sdn.sap.com/irj/sdn/lcm

http://sdn.sap.com/irj/sdn/landscapedesign

http://sdn.sap.com/irj/sdn/applicationmanagement

http://sdn.sap.com/irj/sdn/nw-sld

http://sdn.sap.com/irj/sdn/softwarelogistics

http://sdn.sap.com/irj/sdn/operations

http://sdn.sap.com/irj/sdn/security

http://www.microsoft.com/security

Typographic Conventions

Example Description

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

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 works

Example ■ 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-07-15 PUBLIC 159/164

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

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

www.sap.com

© Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

160/164 PUBLIC 2013-07-15

Legal Software Terms

Terms for Included Open Source Software

This SAP software contains also the third party open source software products listed below. Note that for these third party products the following special terms and conditions shall apply.1. This software was developed using ANTLR.2. SAP License Agreement for STLport

SAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)1. Subject Matter of the Agreement

1. SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee.

2. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement.

3. The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions.

4. Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG

5. The Customer may distribute original or modified STLport sources, provided that: ■ The conditions indicated in the above permissions notice are met; ■ The following copyright notices are retained when present, and conditions provided in accompanying

permission notices are met:Copyright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice.

2013-07-15 PUBLIC 161/164

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications.

2. Support and MaintenanceSAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract.

3. Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error-free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes.

4. Limited Liability1. Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this

(i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute.

2. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typical transfer of the software.

3. In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect or lost profit.

4. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000.

5. The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation.

6. The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP.

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

162/164 PUBLIC 2013-07-15


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2013 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Inst Guide Baselinebrv1606 Sybase Nw73

Documents

Transcript of Inst Guide Baselinebrv1606 Sybase Nw73