sybase dr

Installation GuideDocument version: 1.6 2014-11-24

SAP Systems Based on SAP NetWeaver ABAP on UNIX: SAP Adaptive Server EnterpriseUsing Software Provisioning Manager 1.0

PUBLIC

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

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

PUBLIC Copyright 2015 SAP SE or an SAP affiliate company.All rights reserved.

SAP Systems Based on SAP NetWeaver ABAP on UNIX: SAP Adaptive Server EnterpriseAbout this Installation Guide

Typographic Conventions

Table 1

Example Description

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

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

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

SAP Systems Based on SAP NetWeaver ABAP on UNIX: SAP Adaptive Server EnterpriseTypographic Conventions

PUBLIC Copyright 2015 SAP SE or an SAP affiliate company.

All rights reserved. 3

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

Document History

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

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

Table 2

Version Date Description

1.0 2012-08-06 First version for software provisioning manager 1.0

1.1 2012-09-25 Updated Version




1.5 2014-07-07 Instead of a separate installation guide for each UNIX-based operating system, we now deliver a single installation guide for all UNIX-based operating systems. Sections that are only relevant for one or more specific operating systems are highlighted accordingly.


4


SAP Systems Based on SAP NetWeaver ABAP on UNIX: SAP Adaptive Server EnterpriseDocument History

http://service.sap.com/instguides

Content

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2 Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.1 Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2 Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.3 High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.4 Additional Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.5 Central Services Instance for ABAP Separate from Existing Primary Application Server Instance

of an Upgraded System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.6 SAP Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2 Installation Using a Stack Configuration File (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.3 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Running the Prerequisites Check in Standalone Mode (Optional) . . . . . . . . . . . . . . . . . . . . . . . . 26 Requirements for the SAP System Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.4 Planning User and Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.5 Diagnostics Agent Specific Planning Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Connection Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Direct SAP Solution Manager Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 System Landscape Directory Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.6 Basic Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 SAP System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Diagnostics Agent Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 SAP System Database Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Additional Parameters When Using a Stack Configuration File (Optional) . . . . . . . . . . . . . . . . . . . 50

3.7 Setup of Database Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.8 SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.9 Planning the Switchover Cluster for High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.2 Creating Operating System Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.3 Required File Systems and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Setting Up File Systems for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

4.4 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.5 Performing Switchover Preparations for High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704.6 Installing the SAP Front-End Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

SAP Systems Based on SAP NetWeaver ABAP on UNIX: SAP Adaptive Server EnterpriseContent



4.7 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.2 Exporting and Mounting the Transport Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795.3 Exporting and Mounting Global Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805.4 Specifying the Initial Data Source of the User Management Engine . . . . . . . . . . . . . . . . . . . . . . . . . . 815.5 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.6 Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Useful Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Interrupted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Entries in the Services File Created by the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Troubleshooting with the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996.2 Performing Post-Installation Steps for the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006.3 Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006.4 Performing the Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016.5 Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026.6 High Availability: Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036.7 Configuring the Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046.8 Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056.9 Applying the Latest Kernel and Support Package Stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056.10 Performing Post-Installation Steps for the ABAP Application Server . . . . . . . . . . . . . . . . . . . . . . . . 1066.11 SAP Kernel 7.40 and Higher: IP Multicast Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086.12 Configuring User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086.13 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096.14 SAP Systems Based on SAP NetWeaver 7.40 and Higher: Changing Keys for the Secure

Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116.15 Configuring the Change and Transport System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116.16 Enabling the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126.17 Performing a Full Installation Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

7 Disaster Recovery Setup with SAP Replication Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157.1 Implementation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167.3 Installing the Replication Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Co-Located Replication Topology: Central Instance at the Primary Site . . . . . . . . . . . . . . . . . . . 118 Co-Located Replication Topology: Central Instance on a Separate Server . . . . . . . . . . . . . . . . . 120 Dis-Located Replication Topology: Central Instance on a Separate Server . . . . . . . . . . . . . . . . . 122 Materializing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

7.4 Starting and Stopping DR Agent and Replication Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267.5 Removing the Replication Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277.6 Integration of SAP Replication Server into an OS Cluster Environment . . . . . . . . . . . . . . . . . . . . . . 128

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Defining Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

6



7.7 Defining Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337.8 Defining Node Failure Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

8 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348.1 Splitting Off a Central Services Instance for ABAP from an Existing Primary Application Server

Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348.2 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368.3 Setting Up File Systems for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1408.4 Exporting and Mounting Directories via NFS for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1438.5 Installing the SAP Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1448.6 Creating a User for LDAP Directory Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468.7 Heterogeneous SAP System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478.8 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150




8

PUBLIC Copyright 2015 SAP SE or an SAP affiliate company.All rights reserved. SAP Systems Based on SAP NetWeaver ABAP on UNIX: SAP Adaptive Server Enterprise

1 Introduction

This installation guide describes how to install an SAP NetWeaver ABAP system using the installation tool software provisioning manager 1.0 SP07 (installer for short), which is part of SL Toolset 1.0 SP12.

This guide is valid for the operating systems AIX, HP-UX, Linux, and Solaris.

It applies to the following releases:

NoteNote that not for each product listed in the following table a complete new system installation from scratch is available. For some products - such as SAP NetWeaver 7.4 - a complete new system installation from scratch is only provided for the highest available support release. If there are one or more support releases available, then a complete system installation is only available for the highest of these support releases. As for the lower support releases, only options for system copy and additional application server instances are provided.

Table 3

Product Release

SAP NetWeaver SAP NetWeaver 7.3

SAP NetWeaver 7.3 including Enhancement Package 1

SAP NetWeaver 7.4

SAP NetWeaver 7.4 Support Release 1

SAP NetWeaver 7.4 Support Release 2

SAP ERP SAP Enhancement Package 6 for SAP ERP 6.0, Version for SAP HANA based on SAP NetWeaver AS ABAP 7.4

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

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

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

SAP CRM SAP Enhancement Package 2 for SAP CRM 7.0, Version for SAP HANA based on SAP NetWeaver AS ABAP 7.4

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

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

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

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

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

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

SAP SCM SAP Enhancement Package 2 for SAP SCM 7.0, Version for SAP HANA based on SAP NetWeaver AS ABAP 7.4

SAP Enhancement Package 3 for SAP SCM 7.0 on SAP NetWeaver 7.4

SAP Enhancement Package 3 SR1 for SAP SCM 7.0 on SAP NetWeaver 7.4 SR1

SAP Enhancement Package 3 SR2 for SAP SCM 7.0 on SAP NetWeaver 7.4 SR2

SAP Systems Based on SAP NetWeaver ABAP on UNIX: SAP Adaptive Server EnterpriseIntroduction



NoteNot 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 have already been released. Always check SAP Note 1680045 to ensure that the installation options you want to perform are already supported.

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

Constraints

Your operating system platform must be 64-bit.

The SAP Adaptive Server Enterprise Cluster Edition is not supported.

Raw devices are not supported.

Naming Conventions

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 71] 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 and scn.sap.com/docs/DOC-30236.

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 Naming of command line parameters, for example SAPINST_USE_HOSTNAME Operating system user groups, for example additional group sapinst

usage type, technical usage, and product instance

As of software provisioning manager 1.0 SP07 (SL Toolset 1.0 SP12), the term product instance replaces the terms usage type and technical usage for SAP systems based on SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731. Note that there is no terminology change for older releases and all mentioned terms can be used as synonyms. As this guide is a generic document, the currently used terms remain but only product instance is going to be used from now on when referring to SAP NetWeaver 7.3 EHP1 and higher.

For more information, see New Features [page 12].

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 Application Server ABAP 7.4 / SAP NetWeaver 7.4 / 7.4 SR1.

ABAP system refers to SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver Application Server ABAP 7.4 / SAP NetWeaver 7.4 / 7.4 SR1.

10



http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1680045&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1680045&_NLANG=en&_NVERS=0http://scn.sap.com/docs/DOC-30236http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1877731&_NLANG=en&_NVERS=0

Diagnostics Agent refers to the SAP Solution Manager Diagnostics Agent which is the remote component of End-to-End Root Cause Analysis. It allows having a connection between SAP Solution Manager and managed systems, and then to collect information from the managed systems for reporting purposes.

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 service.sap.com/instguides:

Table 4

Document Internet Address

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

Master Guide SAP Enhancement Package 1 for SAP NetWeaver 7.3

service.sap.com/installNW73

Master Guide SAP NetWeaver 7.4 service.sap.com/installNW74

Master Guide - SAP Enhancement Package for SAP ERP 6.0

service.sap.com/erp-inst SAP ERP 6.0 Planning

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

service.sap.com/srm-inst

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

service.sap.com/crm-inst Plan

Master Guide SAP Supply Chain Management 7.0 Powered by SAP NetWeaver

service.sap.com/instguides SAP Business Suite Applications SAP

SCM Master Guide

Administrator's Guide EHP2 SAP SCM 7.0, version for SAP HANA

service.sap.com/instguides SAP Business Suite Applications SAP

SCM SAP SCM Server Using SAP EHP 2 for SAP SCM Server 7.0,

version for SAP HANA

Administrator's Guide SAP CRM 7.0 EHP2, Version for SAP HANA

service.sap.com/crm-ehp2hana-inst




http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/installNW73http://service.sap.com/installNW73http://service.sap.com/installNW74http://service.sap.com/erp-insthttp://service.sap.com/srm-insthttp://service.sap.com/crm-insthttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/crm-ehp2hana-inst

Document Internet Address

Administrator's Guide for SAP ERP 6.06, Version for SAP HANA

service.sap.com/erp-ehp6hana-inst

1.2 New Features

The table below provides an overview of the new features.

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

Table 5

Feature Description Availability

Usage Type Library Deprecation for SAP Systems Based on SAP NetWeaver 7.3 EHP1 and Higher

Software provisioning manager 1.0 no longer uses the Usage Types definitions in its business logic for SAP systems based on SAP NetWeaver 7.3 EHP1 and higher. This is done to unify modeling and terminology across all SAP tools used during the planning, installation and maintenance activities. The Product Instance definition replaces Usage Types regarding product modeling. For more information, see SAP Notes 1970349 and 1877731.

Software provisioning manager 1.0 SP07 (SL Toolset 1.0 SP12

Installation Using a Stack Configuration File

You can use a stack configuration file generated by the Landscape Planner. The stack configuration can then be consumed by the installer to get better integrated with SUM and to simplify the process of installation for a new system on a target software level.

For more information, see Installation Using a Stack Configuration File (Optional) [page 25]

Software provisioning manager 1.0 SP07 (SL Toolset 1.0 SP12)

Adaptive Installation

You can assign virtual host names to SAP system instances during the input phase of the installation directly on the screens where you define the instance parameters.


Feedback Evaluation Form

SAP SE's aim is to provide fast and efficient procedures. To evaluate the procedure you just carried out, we need information generated by the tool during process execution and your experience with the tool itself. A new evaluation form contains a simple questionnaire and XML data generated during the procedure.

For more information, see Useful Information About the Installer [page 88].


Option Verify Signed Media

The digital signature ensures that the signatory of a digital document can be identified unambiguously and signatorys name is documented together with the signed document, the date, and the time.

For more information, see SAP Note 1979965


Diagnostics Agent The Diagnostics Agent is no longer installed automatically with the SAP system. You can install it optionally by selecting the Install Diagnostics Agent check box on the Install Diagnostics Agent screen.


12



http://service.sap.com/erp-ehp6hana-insthttp://service.sap.com/releasenoteshttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1970349&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1877731&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1979965&_NLANG=en&_NVERS=0

Feature Description Availability

RecommendationWe recommend that you install the Diagnostics Agent separately and prior to the installation of your SAP system(s). If applicable we recommend to use the Agents On-the-fly feature.

For more information, see the Diagnostics Agent Installation Strategy attached to SAP Note 1365123, to SAP Note 1833501, and to SAP Note 1858920 and the there attached Diagnostics Agent Setup Guide.

The Diagnostics Agent Setup Guide has additional Diagnostics Agent-related information that is not included in this document for example, on kernel and JVM specifics, and on usage of the smdsetup script.

Support of Oracle Solaris 11

Oracle Solaris 11 is supported for SAP system installation.

For more information, see SAP Note 1669684.

NoteOracle Solaris 11 might not have been released yet for all database platforms and versions. If you want to install on Oracle Solaris 11, first check the product availability matrix (PAM) available at service.sap.com/pam to see whether your database platform or version is supported.


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 service.sap.com/notes.

Table 6: 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

1704753 Inst.Systems based on NetWeaver 7.1 and higher: UNIX

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

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

Software Provisioning Manager 1.0: SAP NetWeaver 7.3 and higher

1554717 Planning Information for SAP on ASE SAP release information for customers deploying SAP on ASE




http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1365123&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1833501&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1858920&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1669684&_NLANG=en&_NVERS=0http://service.sap.com/pamhttp://service.sap.com/noteshttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1680045&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1704753&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1748888&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1554717&_NLANG=en&_NVERS=0


1619967 SYB: DBA Cockpit Correction Collection SAP Basis 7.31

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

1882376 SYB: DBA Cockpit Correction Collection SAP Basis 7.40

The implementation of SAP Note 1882376 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 Backup Instructions for SAP on ASE Information about backup and recovery

1650511 High Availability Offerings with SAP ASE Information about high availability cluster solutions for SAP ASE

1365123 Installation of Diagnostics Agents Overview of the Diagnostics Agent installation strategies

1833501 Diagnostics Agent Installer Versions More information about available Diagnostics Agent installer versions

1858920 Diagnostics Agent installation with SWPM Installation and Post-installation steps for installers based on software provisioning manager 1.0 (SWPM)

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

1972803 SAP on AIX: Recommendations This SAP Note contains recommendations and clarifications for many topics relevant for SAP on AIX.

1075118 SAP on HP-UX: FAQ This SAP Note contains information that is specific to the SAP system installation on HP-UX

171356 SAP software on Linux: Essential comments This SAP Note contains Linux-specific information about the SAP system installation

1669684 SAP on Oracle Solaris 11 This SAP Note contains information and references to SAP Notes relevant for Solaris 11

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

789220 Support Package level for NetWeaver Installations/Upgrades

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

1990240 Support of mixed landscapes (Unicode and Non-Unicode)

Temporarily your system landscape is mixed with Unicode and Non-Unicode systems. You have third party software in your system landscape

14



http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1619967&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1619967&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1882376&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1882376&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1245200&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1585981&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1650511&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1365123&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1833501&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1858920&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=855498&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=73606&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1972803&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1075118&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=171356&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1669684&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067221&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=789220&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1990240&_NLANG=en&_NVERS=0


which does not support Unicode at all. You wonder whether such a heterogeneous system landscape is supported without restrictions.

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:

Table 7

Product and Release SAP Library Path

SAP systems based on SAP NetWeaver 7.3: help.sap.com/nw73 Application Help Function-Oriented View:

English

SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1

help.sap.com/nw731 Application Help Function-Oriented View:

English

SAP systems based on SAP NetWeaver Application Server ABAP 7.4

help.sap.com/soh Application Help SAP Library: English SAP NetWeaver

SAP systems based on SAP NetWeaver 7.4 help.sap.com/nw74 Application Help Function-Oriented View:

English




http://help.sap.com/nw73http://help.sap.com/nw731http://help.sap.com/sohhttp://help.sap.com/nw74

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 16] (formerly known as central system) Distributed system [page 17] Only valid for: HA (UNIX) |

High-availability system [page 18]End of: HA (UNIX) |

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

You can split off a central services instance for ABAP from an existing primary application server instance of an upgraded system [page 22].

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

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) Database instance (DB) Primary application server instance (PAS instance)

Additionally you can install one or more additional application server instances. For more information, see Additional Application Server Instance [page 19].

16


SAP Systems Based on SAP NetWeaver ABAP on UNIX: SAP Adaptive Server EnterpriseInstallation Options Covered by this Guide

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:

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

Central services instance for ABAP (ASCS instance)

Database instance (DB)

The ABAP stack uses its own database schema in the database.

Primary application server instance (PAS)

The graphics below assume that you use the global directories of the ASCS instance as global file system. That means that the host with the ASCS instance is the SAP global host. However, you can also separately install the global directories on any host of your SAP system landscape.

You can also use the SAP transport host or the host with the global file system (SAP global host) as your primary application server instance host.

Optionally you can install one or more additional application server instances. For more information, see Installation of an Additional Application Server Instance [page 19].




Figure 2: Distributed ABAP System

Only valid for: HA (UNIX) |

2.3 High-Availability 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 high-availability system, every instance can run on a separate host.

There are the following instances:

Central services instance for ABAP (ASCS instance) Enqueue replication server instance (ERS instance) for the ASCS instance (mandatory) Database instance (DB) Primary application server instance (PAS)

The graphics below assume that you run the ASCS instance on the switchover cluster infrastructure. However, you can also run other SAP system instances that are a single point of failure (SPOF) on a switchover cluster infrastructure, for example the database instance.

You can also use the SAP transport host or the host with the global file system (SAP global host) as your primary application server instance host.

We recommend that you run the ASCS instance in a switchover cluster infrastructure. The ASCS instance must have its own ERS instance.

To increase high availability by creating redundancy, we recommend that you install additional application server instances on hosts different from the primary application server instance host. For more information, see Installation of an Additional Application Server Instance [page 19].

The following figures show examples for the distribution of the SAP instances in a high-availability system.

18



Figure 3: High-Availability System

End of: HA (UNIX) |

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 (exceptions see below)

On a dedicated host

NoteIf you want to install additional application server instances running on an operating system other than the primary application server instance, see Heterogeneous SAP System Installation [page 147]. For example, you need to do this if your primary application server instance runs on Linux for System z but the additional application server instance is to run on Windows.

Additional Application Server Instance for a Standard System

For example, the following figure shows a standard system with additional application server instances that run:

On the main host of the SAP system, that is, on the host on which the primary application server instance and the database instance run

On dedicated hosts




Figure 4: Additional Application Server Instance for a Standard System

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

Additional Application Server Instance for a Distributed System

The following figure shows a distributed system with additional application server instances that run:

On the main host of the SAP system, that is, on the host on which the primary application server instance runs

On dedicated hosts

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

20



Figure 5: Additional Application Server Instance for a Distributed System

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

Additional Application Server Instance for a High-Availability System

The following figure shows a high-availability system with additional application server instances that run:

On the host of the primary application server instance On dedicated hosts

We do not recommend installing additional application server instances on the switchover cluster infrastructure.




Figure 6: Additional Application Server Instance for a High-Availability System

For more information, see High-Availability System [page 18].

End of: HA (UNIX) |

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. With a separate ASCS instance, it is easier for you to later turn your SAP system into a high-availability system.

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

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 134] 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).

22



2.6 SAP Host Agent as a Separate Installation

Using the SAP Host Agent, you can centrally monitor any host with the Alert Monitor or the SAP NetWeaver Administrator or the Landscape Virtualization Manager. In addition, the SAP Host Agent is used by the Landscape Virtualization Manager for starting, stopping, and relocating SAP instances and databases.

The SAP Host Agent is automatically installed during the installation of all new SAP system instances. You only need to install an SAP Host Agent separately in the following cases:

There is no SAP system or instance on the host. The SAP system or instance running on the host has a kernel release lower than SAP kernel 7.20 and the host

does not yet have an SAP Host Agent.

You have upgraded your SAP system to a release with a kernel release lower than SAP kernel 7.20 and the host of the upgraded system or instance does not yet have an SAP Host Agent.

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




3 Planning

3.1 Planning Checklist

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

Standard, distributed, or high-availability system

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 available at the appropriate download location under service.sap.com/instguides.

For more information, see Before You Start [page 11].

2. You have decided on your installation option (see Installation Options Covered by this Guide [page 16]).

Standard, Distributed, or High-Availability System

NoteIn 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. If you want the installer to consume a stack configuration file, read section Installation Using a Stack Configuration File (Optional) [page 25].

2. You check the Hardware and Software Requirements [page 26] on every installation host.

3. You identify Basic Installation Parameters [page 40].

4. You decide on the transport host to use [page 53].

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

6. If you want to install the Diagnostics Agent together with your SAP system, read the Diagnostics Agent specific planning steps [page 38].

7. Only valid for: HA (UNIX) |

To install a high-availability system, you read Planning the Switchover Cluster for High Availability [page 54].

End of: HA (UNIX) |

8. Continue with Preparation [page 57].

Additional Application Server Instance

1. You check the Hardware and Software Requirements [page 26] on every installation host.

2. You identify Basic Installation Parameters [page 40].

3. Continue with Preparation [page 57].

24


SAP Systems Based on SAP NetWeaver ABAP on UNIX: SAP Adaptive Server EnterprisePlanning

http://service.sap.com/instguides

3.2 Installation Using a Stack Configuration File (Optional)

SAP has improved the process of provisioning an up-to-date SAP system by creating a unified consumption experience and a direct close collaboration between the involved tools, namely software provisioning manager (the installer for short) and Software Update Manager (SUM).

Prerequisites

To be able to use the Landscape Planner, your SAP Solution Manager system must have at least the following release and Support Package (SP) level:

Release 7.1 SP06 or higher

Release 7.0 SP 23 and you must have the following SAP Notes applied: 1646604 , 1783371, 1743695

In addition, you need to have SAP Note 1940845 implemented in your SAP Solution Manager system.

Features

You can use a stack configuration file generated by the Landscape Planner. The stack configuration can then be consumed by the installer to get better integrated with SUM and to simplify the process of installation for a new system on a target software level. Processing that way eases the task of IT administrators by reducing the efforts in Total Cost of Ownership (TCO). For more information, see the best practice guide Planning Landscape Changes available at: scn.sap.com/docs/DOC-55363

When consuming a stack configuration file, the installer offers more possibilities for automation as compared to when running without it. For more information about the benefits by comparing the existing process with the new improved process, see scn.sap.com/docs/DOC-56626 .

Integration

For the additional input parameters that you need to specify, see Additional Parameters When Using a Stack Configuration File (Optional) [page 50].

In addition, each section in this guide describing steps that are completely or at least partially automatized when using a stack configuration files is therefore specified with an appropriate notification.

These are the following sections:

Preparing the Installation Media [page 71]

Running the Installer [page 82]

Configuring the Change and Transport System [page 111]

Applying the Latest Kernel and Support Package Stacks [page 105]




http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1646604&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1783371&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1743695&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1940845&_NLANG=en&_NVERS=0http://scn.sap.com/docs/DOC-55363http://scn.sap.com/docs/DOC-56626

3.3 Hardware and Software Requirements

Ensure that your hosts meet the hardware and software requirements for your operating system and the SAP instances. Otherwise you might experience problems when working with the SAP system.

Prerequisites

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

Contact your OS vendor for the latest OS patches.

Check your keyboard definitions.

Process Flow

1. Check the Product Availability Matrix at service.sap.com/pam for supported operating system releases.

2. Check the hardware and software requirements using:

The Prerequisite Checker:

Standalone (optional) before the installation process

For more information, see Running the Prerequisites Check Standalone.

Integrated in the installation tool (mandatory) as part of the installation process

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

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

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

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

When you install an SAP system, the installer automatically starts the prerequisites check and checks the hardware and software requirements in the background. As an optional step during planning, you can also run the prerequisites check in standalone mode to check the hardware and software requirements for your operating system and the SAP instances before the actual installation.

26



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

RecommendationWe recommend that you use both the prerequisites check and the requirements tables for reference.

Procedure

1. Copy the installer to the host where you want to run the prerequisites check as follows:

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

service.sap.com/swdc Support Packages and Patches A - Z Index S SL Toolset SL Toolset Entry by Component Software Provisioning Manager Software Provisioning Mgr 1.0

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

SAPCAR -xvf /.SAR -R 2. Start the installer as described in Running the Installer [page 82].

3. On the Welcome screen, choose Preparations Prerequisites Check .4. Follow the instructions in the installer dialogs and enter the required parameters.

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

After you have finished, the Parameter Summary screen appears. This screen summarizes all parameters that you have entered and that you want to have checked. If you want to make a change, select the relevant parameters and choose Revise.

5. To start the prerequisites check, choose Next.

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.3.2 Requirements for the SAP System Hosts

Every installation host must meet at least the requirements listed in the following tables. Most of the requirements are valid for every installation host whereas some requirements are instance-specific and are marked accordingly.

NoteThe information here is not intended to replace the operating system documentation. For more information, see your operating system documentation.




http://service.sap.com/swdc

Table 8

Operating System: More information:

AIX You can perform AIX-specific steps using the following tools:

Manually by entering AIX commands with the appropriate options

Using System Management Interface Tool (SMIT), a menu-driven system administration tool

If you have problems with the function keys, you can also use ESC and the corresponding number to simulate the function key (for example, F4 is equivalent to ESC and 4 ).

HP-UX For an SAP system installation on HP-UX, consider the following information:

SAP on ASE uses Concurrent I/O on HP-UX. The Veritas File System (Online JFS 5.0.1 or above) must be installed on your system prior to installing SAP on ASE and HP-UX. For more information, refer to SAP Note 1077887.

SAP Adaptive Server Enterprise 16.0: Install the following AioEnh patch: h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=AioEnh.

SAP only supports the use of native binaries. Always use the appropriate SAP binaries for your processor.

For recommendations and information about availability of HP-UX 11.31 (also known as HP-UX 11iv3), see SAP Note 1031960.

Linux For general information about the SAP system installation on Linux, see SAP Note 171356.

Oracle Solaris For more information, refer to scn.sap.com/community/oracle-solaris.

Table 9: Hardware Requirements

Requirement Values and Activities

Optical Media Drive

ISO 9660 compatible

Linux: Must be connected locally to your central instance host.

CPU Database instance:

The following hardware architectures are supported:

AIX, Solaris: All 64-bit processors that are capable of running the supported operating system version.Itanium-based integrity system (IA64) is not supported for Solaris

HP-UX: Itanium-based HP Integrity system

Linux: AMD64, Itanium-based integrity system (IA64) is not supported

All other instances:

The recommended minimum hardware is:

Two dual core CPUs or

Four single core CPUs

To display the number of CPUs in a system, enter the following command:

AIX: lparstat -i | grep "Entitled Capacity"HP-UX: ioscan -fnkCprocessorLinux: grep -c ^processor /proc/cpuinfo

28



http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1077887&_NLANG=en&_NVERS=0https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=AioEnhhttps://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=AioEnhhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1031960&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=171356&_NLANG=en&_NVERS=0http://scn.sap.com/community/oracle-solaris


Solaris: /usr/sbin/psrinfo -vp

Hard Disk Space General Requirements:

4.3 GB of temporary disk space for every required installation medium that you have to copy to a local hard disk. For more information, see Preparing the Installation Media [page 71].

1.2 GB of temporary disk space for the installation.

AIX:

For data security reasons, distribution over three disks is required. We recommend you to distribute over five disks.

To display available disks, enter the following command:

lspvDisks marked none in the 3rd column are unused.To display free space on a disk, enter the following command:

lspv -p Areas marked free in the 2nd column are unused.

Linux:

If an advanced disk array is available (for example, RAID), contact your hardware vendor to make sure that the data security requirements are covered by this technology.

To print and change the partitioning of the first SCSI disk, enter the following command:

/sbin/fdisk /dev/sdaTo print and change the partitioning of a RAID device, enter commands specific to your hardware.

ExampleThe following hardware-specific commands for RAID devices are typical:

/sbin/fdisk /dev/rd/c0d0/sbin/fdisk /dev/ida/c0d0

Solaris:

SAP ASE is available for Solaris 10 and Solaris 11.

For more information on SAP ASE on Solaris 11, refer to SAP Note 1716200.

For more information about specifying device names and about displaying and changing the partitioning, see the Solaris System Administrator Collection at the Sun website.

Instance-specific Requirements:

If you install several instances on one host, you have to add up the requirements accordingly.

For more information about space requirements for the file systems and directories of the instances, see SAP Directories [page 61] and the appropriate database-specific information listed below.

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

Central services instance for ABAP (ASCS) (high-availability only)

12 GB

End of: HA (MSCS);HA (UNIX) |




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


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

Enqueue replication server instance for the SCS (high-availability only)

2 GB

End of: HA (MSCS);HA (UNIX) |

Database Instance:

Minimum 12 GB

Database Software: 4 GB

4.5 GB of temporary disk space for every required installation medium you have to copy to a local hard disk.

1.2 GB of temporary disk space for the installation.

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

Central instance:

10 GB

Additional application server instance:

10 GB

SAP Host Agent:

1 GB

Diagnostics agent:

1.5 GB

RAM The following lists the RAM requirements for each instance.

If you install serveral instances on one host, you have to add up the requirements accordingly.

Database Instance:

Minimum 3 GB

Additional application server instance:

Minimum 3 GB

SAP Host Agent:

0.5 GB

Diagnostics agent:

1 GB

Linux:

To display RAM size in KB, enter the following command:

freeFor more information about how to interpret the output of this command correctly, see SAP Note 1382721.

HP-UX:

To display the RAM size on HP-UX, proceed as follows:

30





On HP-UX Itanium or all 11.31 systems, you can also use the following command:

/usr/contrib/bin/machinfo | grep Memory

Swap Space It is recommended that the swap space is at least twice as large as RAM.

Linux: For more information, see SAP Note 171356.

HP-UX: For the database instance, you need 3* RAM + 500 MB in addition, at least 20 GB recommended). For more information about HP-UX swap space recommendations, see SAP Note 1112627.

Table 10: Software Requirements


Database software / Client software

The following versions are supported: SAP Sybase ASE 15.7 and SAP ASE 16.0

(automatically installed by the installer)

Caution For the installation of the SAP system, only the English version of the SAP ASE database is

supported.

You must only use the SAP ASE software that is provided for the SAP Business Suite (Sybase ASE 15.7 for Bus.Suite, SAP ASE 16.0 for Bus.Suite).

Linux: Operating System Versions

Supported Linux versions:

SAP ASE 16.0

RHEL 6.1

SLES11

SAP Sybase ASE 15.7

RHEL 6

SLES11

To check the operating system version, enter the following command:

cat /etc/* -release

HP-UX: Operating System Versions

Supported HP-UX versions:

SAP ASE 16.0

Minimum requirement:

HP-UX 11.31

The following patches are required:

PHSS_37493, PHSS_36352, PHKL_37802, PHKL_42687

SAP ASE 15.7

Minimum requirement:

HP-UX 11.31


uname -r




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


AIX: Operating System Versions

SAP ASE 16.0

AIX 7.1, TL 0 and higher


oslevel -sTable 11

AIX Level: Required SP: oslevel -s

AIX 7.1 TL 0 SP8 7100-00-08-1241

AIX 7.1 TL 1 SP6 7100-01-06-1241

AIX 7.1 TL2 SP2 7100-02-02-1316

AIX 7.1 requires a patch that fixes APARIV10828. Contact IBM directly to obtain the patch.

SAP Sybase ASE 15.7

AIX 7.1

AIX 7.1 requires a patch that fixes APARIV10828. Contact IBM directly to obtain the patch.

Oracle Solaris: Operating System Versions

Supported Solaris versions:

SAP ASE 16.0

Solaris 10

The following patches are required:

120753-05, 120048-03, 144190-03

Solaris 11

SAP Sybase ASE 15.7

Solaris 10

Solaris 11


uname r

AIX: Kernel Parameters

To adjust the settings for asynchronous I/O (AIO) if the database is installed using file systems, see SAP Note 1048686.

Linux: Kernel Parameters

To check the Linux kernel version, enter the following command:

uname -r To check the Linux kernel parameter settings, enter the following command:

/sbin/sysctl a If you are using a Linux kernel version certified by SAP, you do not need to modify the Linux

kernel. To check the Linux kernel version, enter the following command:

uname rFor more information about the Linux kernel versions certified by SAP, see SAP Note 171356.

To check the Linux kernel parameters for your Linux distribution, see one of the following SAP Notes:

SLES11: SAP Note 1310037

32



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


RHEL 6: SAP Note 1496410

AIX: Additional Software

Make sure that the following additional file sets and the IOCP module are installed:

bos.adt Base Application Development bos.perf Performance and Dagnostics Tools perfagent.tools Performance Monitoring Tools bos.perf.libperfstat Performance Statistics Library

For an overview of the installed file sets, enter the following command:

lslpp L | more

Check whether the IOCP module version 6.1.5.0 or higher is installed on your system:

lslpp -l bos.iocp.rteThe output should be similar to the following example:

Path: /usr/lib/objreposbos.iocp.rte 6.1.5.0 APPLIED I/O Completion Ports APIPath: /etc/objreposbos.iocp.rte 6.1.5.0 COMMITTED I/O Completion Ports APIEnter the lsdev command to check whether the status of the IOCP port is Available:lsdev -Cc iocpThe output should match the following example:

iocp0 Available I/O Completion PortsIf the IOCP port status is Defined change the status to Available.

Log in to the server as root and issue the following command:

# smitty iocpSelect Change / Show Characteristics of I/O Completion Ports.

Change the configured state at system restart from Defined to Available. Enter the lsdev command again to confirm that the status of the IOCP port has changed to Available and reboot the system.

HP-UX: OS Patches To check the minimum required OS patches, see SAP Note 837670.

Solaris: OS Patches To check the installed patches, enter the following command:

/bin/showrev -p

NoteFor more information about relevant patches, see the following SAP Notes:

Solaris 10: SAP Note 908334

Solaris 11: SAP Note 1643799

Lightweight Directory Access Protocol (LDAP)

Linux:

If you want to use LDAP, you need the LDAP libraries that are usually installed with the openldap RPM. To check this, enter the following command:




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


rpm -qa | grep openldapMake sure that the output of this command contains the following RPM packages:

Red Hat Linux:

openldap2 SUSE LINUX

openldap2openldap2client

HP-UX:

LDAP library:

HP-UX on Itanium (11.31)

libldapss141.soSolaris:

LDAP library:

libldap.soAIX:

LDAP library:

libldap.a

Fonts and Code Pages HP-UX:

The directory /lib/X11/fonts contains the available fonts.You can select fonts in your default profiles for X11 and CDE.

Exampleiso_8859.1 or hp_roman8

Solaris:

Make sure that the required fonts and code pages are installed.

Solaris 10 and 11

For more information, see the Solaris System Administrator Collection at the Sun website.

National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding saplocales are installed.AIX:

Install the necessary local code set by adding an additional language environment as follows:

1. Start the System Management Interface Tool (SMIT) with the following command:

smitty mle_add_lang2. Select the following:

Cultural Conventions to install:ISO8859-1 German (Germany) [de_DE]

Language Translation to install:ISO8859-1 German [de_DE]

34




This step installs the required bos.loc and bos.iconv file sets.3. Check that all file sets are in a consistent state by entering the following command:

lppchk vHP-UX

Enter the following command to check whether National Language Support (NLS) is installed:

swlist -v | grep -i nlsThe output should contain the string NLS-AUX ...

Enter the following command to check which locales are available:

locale -aThe following files must be available: de_DE.iso88591, en_US.iso88591.

Linux:

To display available locales, enter the following command:locale -a

Check the output for locales such as the following:

de_DE, en_US SAP blended Code Pages are available as an attachment of SAP Note 171356.

For more information about NLS on Linux, see SAP Note 187864.

Solaris:

To display which locales are available, enter the following command:

locale -aThe following files must be available: iso_8859_1, en_US.

Linux: Additional Information

System Language:

For the installation, you must choose English as the operating system language on all Linux hosts that run SAP software.

Routing Information:

To check routing information, enter the following command:

netstat -rShared Memory File System:

To check the size of the shared memory file system, enter the following command:

df k /dev/shmActivated Hardware Drivers:

To check the activated hardware drivers, enter the following command:

lsmod

Table 12: Other Requirements


Host Name To find out physical host names, open a command prompt and enter hostname.For more information about the allowed host name length and characters allowed for SAP system instance hosts, see SAP Note 611361.




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


If you want to use virtual host names, see SAP Note 962955.

Login Shell The installer only prompts you for this parameter if you use a login shell other than the recommended C shell (csh).


Printer AIX, HP-UX:

To check whether a file can be printed, enter the following command:

lp -d To check the status of your spool and the printers, enter the following command:

lpstat -tLinux:

To check the status of spooling queues and printers, enter the following command:

lpc status To check whether you can print a file, enter the following command:

lpr P Solaris:

Solaris 10 and 11

For more information about how to set up a printer, see the Solaris System Administrator Collection at the Sun website.

Networking If application servers are installed decentralized, Network File System (NFS) must be installed.

AIX:

To test the network connection to the database server, enter the following command:

/etc/ping 100 10HP-UX:

To check the current kernel configuration files to make sure that the NFS driver is in the kernel, enter the following command:

grep nfs /stand/system To check whether NFS is running, enter the following commands:

ps -ef | grep nfsdps -ef | grep rpcbindgrep NFS_C /etc/rc.config.d/nfsconfgrep NFS_S /etc/rc.config.d/nfsconf

Either NFS_CLIENT, NFS_SERVER, or both should be set to 1. You can use SAM or SMH to start NFS or add the driver to the kernel.

Linux:

To check whether NFS is running, do one of the following:

On Red Hat Linux:

service nfs statusservice portmap status

36



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


On SuSE Linux:

rcnfs status Test the network connection to the database server with the following command:

ping -c 10 Solaris:

Solaris 10 and 11

For more information about how to set up and administer Network File System (NFS), see the System Administrator Collection at the Sun website.

AIX, HP-UX, Solaris: C++ Runtime Environment

Linux: C compiler

AIX:

Check the C++ runtime level with the following commands:

AIX 7.1:

#lslpp L xlC.aix71.rteThe output must be at least 11.1.0.0.#lslpp L xlC.rteThe output must be at least 11.1.0.0.HP-UX:

Make sure that the patch level of C++ runtime library is equal to or newer than the version recommended in the general HP-UX patch recommendations. For more information, see SAP Note 837670.

Solaris:

The Shared Library Patch for C++ must be installed.

Linux:

To check that the C compiler gcc is installed, enter the following command:

rpm -qa | grep gcc Make sure that the C compiler is installed.

3.4 Planning User and Access Management

You have to plan how to configure user and access management for the SAP system to be installed.

Before you add a newly installed SAP system to your system landscape, you must decide which kind of user management you want to use:

Use Central User Administration (CUA). Use an LDAP directory as the data source for user data.





Procedure

Using Central User Management

1. You install your SAP system as described in this installation guide.

2. Add the system to Central User Administration (CUA). For more information, see Configuring User Management [page 108].

Using an LDAP Directory as the Data Source for User Data

1. You install your SAP system as described in this installation guide.

2. Configure the user management of the newly installed SAP system to use an LDAP directory.

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

More Information

For more information about configuring the user management of your SAP system to be installed, see the SAP Library [page 15] at:

Function-Oriented View Security Identity Management Identity Management of the Application Server ABAP

3.5 Diagnostics Agent Specific Planning Steps

The Diagnostics Agent is no longer installed automatically with the SAP system. You can install it optionally by selecting the Install Diagnostics Agent check box on the Install Diagnostics Agent screen.

CautionThe check box on the Install Diagnostics Agent screen will be disabled if the kernel or JVM prerequisites for the Diagnostics Agent are not met. For more information refer to chapter Installing the Diagnostics Agent Optionally with the SAP System in the latest Diagnostics Agent Setup Guide attached to SAP Note 1858920.

RecommendationWe recommend that you install the Diagnostics Agent separately and prior to the installation of your SAP system(s). If applicable we recommend to use the Agents On-the-fly feature.

For more information refer to the Diagnostics Agent Installation Strategy attached to SAP Note 1365123, to SAP Note 1833501, and to SAP Note 1858920 and the there attached Diagnostics Agent Setup Guide.

The Diagnostics Agent Setup Guide holds further Diagnostics Agent related information that is not included in this document. For example on kernel and JVM specifics, and on usage of the smdsetup script.

38



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

3.5.1 Connection Selection

Before starting the installation make sure that you have identified which installation strategy you want to use. The below two scenarios are compatible, you can configure both connections, or only one of them, or none of them.

RecommendationWe recommend that you choose Direct SAP Solution Manager Connection.

Direct SAP Solution Manager Connection: In this scenario, the Diagnostics Agent establishes a direct connection to the SAP Solution Manager system. If you select Do not configure connection the Diagnostics Agent is not connected to the SAP Solution Manager system. For details see section Direct SAP Solution Manager Connection [page 39].

System Landscape Directory Registration: In this scenario the Diagnostics Agent is registered into the specified System Landscape Directory (SLD). This scenario should be used if SAP Solution Manager is not yet installed. For details see section System Landscape Directory Registration [page 39].

CautionIf you select neither Direct SAP Solution Manager Connection nor System Landscape Directory Registration you will have to configure the Diagnostics Agent connectivity via the smdsetup script after the installation is finished.


3.5.2 Direct SAP Solution Manager Connection

Connect the Diagnostics Agent directly to the SAP Solution Manager system. The below connection types are available.

For more information, see SAP Solution Manager Connectivity Parameters, which is available at Diagnostics Agent Parameters [page 45]

P4 connection via Java SCS Message Server: the Diagnostics Agent connects to the Java SCS Message Server and is redirected to one of the dispatcher nodes of the Java EE engine.

P4 SSL connection via Java SCS Message Server: the same as P4 connection via Java SCS Message Server, but with SSL support.

3.5.3 System Landscape Directory Registration

The System Landscape Directory (SLD) is designed for registering the systems and installed software of your landscape. It is recommended to register the Diagnostics Agent in an SLD. After registration the Diagnostics Agent must be assigned to the SAP Solution Manager system ( Transaction: SOLMAN_SETUP Scenario: System Preparation Step: Connect Diagnostics Agents to Solution Manager ). This allows installing a Diagnostics Agent even if the SAP Solution Manager system is not available.

For more information, see Diagnostics Agent SLD Parameters, which is available at Diagnostics Agent Parameters [page 45].





sybase dr

Documents

sap note

sap installation document

sap installation tools

names of installation

sap netweaver abap

sap affiliate company

sap technical consultants

sap service marketplace