SAP NetWeaver ABAP+Java

Installation Guide SAP NetWeaver ABAP+Java (for Process Integration) on AIX: Oracle
Using Software Provisioning Manager 1.0
Valid for SAP Systems Based on: ■ SAP NetWeaver Process Integration 7.1 ■ SAP NetWeaver Process Integration 7.1 including Enhancement Package 1 ■ SAP NetWeaver 7.3 ■ SAP NetWeaver 7.3 including Enhancement Package 1 ■ SAP NetWeaver 7.4 Target Audience ˙åJ˝ÛÊ Technology consultants ˙åJ˝ÛÊ System administrators

CUSTOMER ˙åJøþÀxŽ†jeDÅ©T−¢Ömf6Í#TÕ^‚U±æà€¤XVDNË[ı<|C܇ı¨ßëWwƒºÿ¦5t*‚

About this Installation Guide

SAP System Installation

SAP system installations should only be performed by SAP Technical Consultants certified for your operating system, your database, and the SAP system that you are installing
SAP Installation Tool

You must only use the SAP installation tools according to the instructions and for the purposes described in the SAP installation document. Improper use of the SAP installation tools can damage files and systems already installed.
Downward Compatibility of Databases

For downward-compatible releases of DB/OS platforms for SAP products, SAP plans to regularly release the newest database (DB) and operating-system (OS) versions of SAP products. These releases are downward-compatible with earlier SAP system releases. Note that for already shipped SAP components, we only support the installation for database versions proposed by the installation tool. Therefore, you must install an SAP component or perform a system copy using a downward-compatible database. That is, you either install the component with the old proposed database version or you upgrade the old database version to the downward-compatible new version.

2/132

CUSTOMER

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 at the following location: http://service.sap.com/instguides The following table provides an overview of the most important document changes.
Version Date Description

1.4 1.3 1.2 1.1 1.0

2013-07-15 2013-04-02 2012-11-27 2012-09-25 2012-08-06

Updated Version Updated Version Updated Version Updated Version Initial Version

2013-07-15

CUSTOMER

3/132

Table of Contents

Chapter 1 1.1 1.2 1.3 1.4 Chapter 2 2.1 2.2 2.3 2.4 2.5 2.6 Chapter 3 3.1 3.2 3.2.1 3.2.2 3.3 3.4 3.5 Chapter 4 4.1 4.2 4.3 4.3.1 4.3.2 4.3.3 4.4

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central Services Instance for ABAP Separate from Existing Primary Application Server Instance of an Upgraded System . . . . . . . . . . . . . . . . . . . . SAP Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Prerequisites Check in Standalone Mode (Optional) . . . . . . . . . . Requirements for the SAP System Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning the Switchover Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Operating System Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . Required File Systems and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up File Systems for a High-Availability System . . . . . . . . . . . . . . . . . . Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11 12 13 14 17 18 19 19 20 21 22 25 33 33 39 39 40 43 43 48 50 53

4/132

CUSTOMER

2013-07-15

4.5 4.6 4.7 Chapter 5 5.1 5.2 5.3 5.4 5.5 5.5.1 5.5.2 5.5.3 5.5.4 5.5.5 5.5.6 5.6 5.6.1 5.6.2 5.6.3 5.6.4 Chapter 6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14

Performing Switchover Preparations for High Availability . . . . . . . . . . . . . . . . 53 Installing the SAP Front-End Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting and Mounting the Global Transport Directory . . . . . . . . . . . . . . . . Exporting and Mounting Global Directories . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . Interrupted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . Entries in the Services File Created by the Installer . . . . . . . . . . . . . . . . . . . . . . Troubleshooting with the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Database 11g Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating the Oracle Installation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Pre-Installation Steps for the AIX Operating System . . . . . . . . . . . Installing the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Required SAP Bundle Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Post-Installation Steps for the Operating System . . . . . . . . . . . . . . Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing the Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Providing Access to the NetWeaver Administrator . . . . . . . . . . . . . . . . . . . . . . Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High Availability: Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . Applying the Latest Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Transport Management System . . . . . . . . . . . . . . . . . . . . . . . Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Oracle-Specific Post-Installation Steps . . . . . . . . . . . . . . . . . . . . . . Performing a Full Installation Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 59 65 66 66 73 73 75 76 79 80 80 81 81 82 83 85 87 87 88 88 90 90 91 91 92 92 93 93 94 95 97

2013-07-15

CUSTOMER

5/132

Chapter 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.8.1 7.8.2 7.8.3 7.9 7.10 Chapter A A.1

Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Installing a Database Instance on Oracle Automatic Storage Management or Oracle Real Application Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . . 103 Creating a User for LDAP Directory Access . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Heterogeneous SAP System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Splitting Off a Central Services Instance for ABAP from an Existing Primary Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Installing the SAP Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Starting and Stopping SAP System Instances . . . . . . . . . . . . . . . . . . . . . . . . . 111 Starting and Stopping SAP System Instances Using the SAP Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Starting and Stopping SAP System Instances Using Commands . . . . . . . . . . . 115 Starting and Stopping the Diagnostics Agent Using Scripts . . . . . . . . . . . . . . 118 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Deleting the Oracle Database 11g Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

6/132

CUSTOMER

2013-07-15

1

Introduction

1 Introduction

This installation guide describes how to install an SAP NetWeaver Process Integration system using software provisioning manager 1.0 (“installer” for short). An SAP NetWeaver Process Integration system is an ABAP+Java (dual-stack) system comprising both an ABAP and a Java stack. This guide applies to the following releases:
Product Release

SAP NetWeaver Process Integration SAP NetWeaver

¶kÀ: ¶kÀ: ¶kÀ: ¶kÀ: ¶kÀ:

SAP NetWeaver Process Integration 7.1 SAP NetWeaver Process Integration 7.1 including enhancement package 1 SAP NetWeaver 7.3 SAP NetWeaver 7.3 including enhancement package 1 SAP NetWeaver 7.4

NOTE

Not all SAP NetWeaver releases or SAP Business Suite applications that are available in software provisioning manager 1.0 and are described in this installation guide might have been released already. Always check SAP Note 1680045 to ensure that the installation options you want to perform are already supported.
CAUTION

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

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

¶kÀ: installer refers to software provisioning manager 1.0. ¶kÀ: SAP system refers to SAP system based on the application server of SAP NetWeaver PI 7.1 / 7.1 including Enhancement Package 1 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver 7.4. ¶kÀ: ABAP+Java system refers to SAP NetWeaver PI 7.1 / 7.1 including Enhancement Package 1 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver 7.4 or SAP NetWeaver PI 7.1 / 7.1 including Enhancement Package 1 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver 7.4 (for Process Integration) system. ¶kÀ: diagnostics refers to diagnostics in SAP Solution Manager. ¶kÀ: diagnostics agent refers to the agent that performs the diagnostics in SAP Solution Manager.

2013-07-15

CUSTOMER

7/132

1 1.1

Introduction Before You Start

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

Master Guide - SAP NetWeaver PI 7.1 Master Guide – SAP NetWeaver 7.3 Master Guide – SAP Enhancement Package 1 for SAP NetWeaver 7.3 Master Guide – SAP NetWeaver 7.4

Installation

Planning
http://service.sap.com/installNW73 http://service.sap.com/installNW73

http://service.sap.com/installNW74

1.2 New Features
The table below provides an overview of the new features. Make sure that you also read the release notes at http://service.sap.com/releasenotes.
Area Description

Software Provisioning Manager »RÒÎt 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 54] 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: »RÒÎtc Texts and screen elements in the software provisioning manager GUI »RÒÎtc Naming of executables, for example sapinst. »RÒÎtc Naming of Command line parameters, for example
SAPINST_USE_HOSTNAME

8/132

CUSTOMER

2013-07-15

1 1.3 Area

Introduction SAP Notes for the Installation Description

⁄¼˛Ł‹ Operating system user groups, for example additional group
sapinst

⁄¼˛Ł‹h You no longer require a Solution Manager Key for the installation. ⁄¼˛Ł‹h 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 25].

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

1704753

1704754

828268 1431800 98252

1365123 1833501 737368

855498

Software provisioning manager 1.0 with installation and system copy for SAP NetWeaver-based systems Inst.Systems based on NetWeaver 7.1 and UNIX-specific information about the higher: UNIX installation for SAP systems and corrections to this documentation Inst.Systems based on NetWeaver 7.1 and Oracle-specific information about the SAP higher: Unix Oracle system installation and corrections to this documentation Oracle 10g: New functions Information about Oracle 10g features released for the SAP system Oracle 11.2.0: Central Technical Note Information about Oracle 11g with multiple links to notes on Oracle 11g Installing two Oracle databases on a host This SAP Note is only required if you plan to install more than one Oracle database on the same host Installation of Diagnostics Agents Overview of the Diagnostics Agent Installation Diagnostics Agent - Installer Versions More information about Diagnostics Agent Hardware requirements of Java Information on the hardware requirements Development for usage type Development Infrastructure (DI), which depends on the size of your development team Installation Prerequisite Checker SAP Software on UNIX, Windows, and IBM i: Checking OS Dependencies

2013-07-15

CUSTOMER

9/132

1 1.4

Introduction Accessing the SAP Library Title Description

SAP Note Number

73606 1067221

Supported Languages and Code Pages Central Note for Heterogeneous Installation

789220

Support Package level for NetWeaver Installations/Upgrades

Information on possible languages and language combinations in SAP systems This SAP Note and its related SAP Notes describe the released operating system and database combinations for heterogeneous SAP systems landscapes. Information about the ABAP Support Package levels and kernel patch levels contained in the current SAP NetWeaver release

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: %çŽÔZ¡ SAP systems based on SAP NetWeaver Process Integration 7.1: http://help.sap.com/nwpi71/ Application Help SAP Library: English SAP NetWeaver Process Integration Library %çŽÔZ¡ SAP systems based on SAP NetWeaver Process Integration 7.1 including Enhancement Package 1: http://help.sap.com/nwpi711/ Application Help SAP Library: English SAP NetWeaver Process Integration Library %çŽÔZ¡ SAP systems based on SAP NetWeaver 7.3: http://help.sap.com/nw73 Application Help Function-Oriented View: English %çŽÔZ¡ SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1: http://help.sap.com/nw731 Application Help Function-Oriented View: English %çŽÔZ¡ SAP systems based on SAP NetWeaver 7.4: http://help.sap.com/nw74 Application Help Function-Oriented View: English

10/132

CUSTOMER

2013-07-15

2 2.1

Installation Options Covered by this Guide Standard System

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. 3
Íiƒ Standard system [page 11] (formerly known as central system) 3
Íiƒ Distributed system [page 12] 3
Íiƒ High-availability system [page 13] 3
Íiƒ You can install one or more additional application server instances [page 14] to an existing standard, distributed, or high-availability system. 3
Íiƒ You can split off a central services instance for ABAP from an existing primary application server instance of an upgraded system [page 17]. 3
Íiƒ You can install an SAP Host Agent separately [page 18]. After you decide on the installation option that you want to use, continue with Planning [page 19].

2.1 Standard System
You can install a standard system on a single host. In a standard system, all main instances run on a single host.: There are the following instances: 3
Íiƒ Central services instance for ABAP (ASCS instance) 3
Íiƒ Enqueue replication server instance (ERS instance) for the ASCS instance (optional) 3
Íiƒ Central services instance for Java (SCS instance) 3
Íiƒ Enqueue replication server instance (ERS instance) for the SCS instance (optional) 3
Íiƒ Database instance (DB) The ABAP stack and the Java stack use their own database schema in the same database 3
Íiƒ Primary application server instance (PAS instance)

2013-07-15

CUSTOMER

11/132

2 2.2

Installation Options Covered by this Guide Distributed System

2x0Dü÷»˚ÇÃì ÂëÄŸBSlflStandard ABAP+Java System

2.2 Distributed System
An SAP system consists of SAP instances. An SAP instance is a group of processes that are started and stopped at the same time. In a distributed system, every instance can run on a separate host, with the exception of the ASCS instance and the SCS instance. The ASCS instance and the SCS instance must run on the same host: 2xÖa5 Central services instance for ABAP (ASCS instance) (optional) 2xÖa5 Enqueue replication server instance (ERS instance) for the ASCS instance (optional) 2xÖa5 Central services instance for Java (SCS instance) 2xÖa5 Enqueue replication server instance (ERS instance) for the SCS instance (optional) 2xÖa5 Database instance (DB) The ABAP stack and the Java stack use their own database schema in the same database 2xÖa5 Primary application server instance (PAS) The graphics below assume that you use the global directories of the ASCS instance and SCS instance as global file system. That means that the host with the ASCS and SCS 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 14].

12/132

CUSTOMER

2013-07-15

2 2.3

Installation Options Covered by this Guide High-Availability System

WUBˇ¼1NbÆfi˙(œNcflï-Distributed ABAP+Java System

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: W³gÐ Central services instance for ABAP (ASCS instance) W³gÐ Enqueue replication server instance (ERS instance) for the ASCS instance (mandatory) W³gÐ Central services instance for Java (SCS instance) W³gÐ Enqueue replication server instance (ERS) for the SCS instance (mandatory) The enqueue replication server instance contains the replication table, which is a copy of the lock table in the SCS instance. W³gÐ Database instance (DB) The ABAP stack and the Java stack use their own database schema in the same database. W³gÐ Primary application server instance (PAS) The graphics below assume that you run the ASCS instance and SCS instance on a 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.

2013-07-15

CUSTOMER

13/132

2 2.4

Installation Options Covered by this Guide Additional Application Server Instance

We recommend that you run both the ASCS instance and the SCS instance in a switchover cluster infrastructure. Both the ASCS instance and the SCS instance must each have their 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 14]. The following figures show examples for the distribution of the SAP instances in a high-availability system.

•,=^—AW˛½¨+xe⁄>⁄ge?ÁõHigh-Availability System

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: •,Û{M The host of any instance of the existing SAP system (exceptions see below) •,Û{M On a dedicated host
NOTE

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

14/132

CUSTOMER

2013-07-15

2 2.4

Installation Options Covered by this Guide Additional Application Server Instance

Additional Application Server Instance for a Standard System

For example, the following figure shows a standard system with additional application server instances that run: = ÕVŠ¶ 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 = ÕVŠ¶ On dedicated hosts

= Õ°²v
÷˘fðz¯−Ø'ƒ´9PAdditional Application Server Instance for a Standard System

For more information, see Standard System [page 11].
Additional Application Server Instance for a Distributed System

The following figure shows a distributed system with additional application server instances that run: = ÕVŠ¶ On the main host of the SAP system, that is, on the host on which the primary application server instance runs = ÕVŠ¶ On dedicated hosts We do not recommend you to install additional application server instances on the SAP global host.

2013-07-15

CUSTOMER

15/132

2 2.4

Installation Options Covered by this Guide Additional Application Server Instance

">efi”
.¾Eœ›fChcÀ¤"RAdditional Application Server Instance for a Distributed System

For more information, see Distributed System [page 12].
Additional Application Server Instance for a High-Availability System

The following figure shows a high-availability system with additional application server instances that run: ">…¶G On the host of the primary application server instance ">…¶G On dedicated hosts We do not recommend you to install additional application server instances on the switchover cluster infrastructure.

16/132

CUSTOMER

2013-07-15

2 2.5

Installation Options Covered by this Guide Central Services Instance for ABAP Separate from Existing Primary Application Server Instance of an Upgraded System

•t5ÇÅm©\ÓBD‹¹—÷;hÁz¯~Additional Application Server Instance for a High-Availability System

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

2.5 Central Services Instance for ABAP Separate from Existing Primary Application Server Instance of an Upgraded System
A central services 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). 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 106] describes how you can move the message server and the enqueue work process from the ABAP stack of an existing primary application server instance to a newly installed central services instance for ABAP (ASCS instance).

2013-07-15

CUSTOMER

17/132

2 2.6

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

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: ¥˝Łrx‹ You want to manage a host that does not have an SAP instance or component. ¥˝Łrx‹ You have upgraded your SAP system. The section Installing the SAP Host Agent Separately [page 108] describes how to perform the installation.

18/132

CUSTOMER

2013-07-15

3 3.1

Planning Planning Checklist

3 Planning

3.1 Planning Checklist
This section includes the planning steps that you have to perform for the following installation options: ÁA›îÏ Standard, distributed, or high-availability system ÁA›îÏ Additional application server instance Detailed information about the steps is available in the relevant chapter.
Prerequisites

1.

2.

You have chosen your installation scenario according to the Master Guide available at the appropriate download location under http://service.sap.com/instguides. For more information, refer to Before You Start [page 8]. You have decided which installation option [page 11] described in this guide you want to perform.

Standard, Distributed, or High-Availability System NOTE

In a standard system, all mandatory instances are installed on one host. Therefore, if you are installing a standard system, you can ignore references to other hosts. 1. 2. 3. 4. 5. 6. 7. 8. You check the hardware and software requirements [page 20] on every installation host. You identify basic SAP system installation parameters [page 25]. For the database installation, we recommend that you check the information available in the SAP on Oracle Knowledge Center at http://www.sdn.sap.com/irj/sdn/ora. You decide on the transport host to use [page 33]. You decide whether you want to integrate LDAP Directory Services in your SAP system [page 99]. To install a high-availability system, you read Planning the Switchover Cluster [page 33]. Optionally, you decide whether you want to install multiple components in one database (MCOD) [page 103]. You can now continue with Preparation [page 39].

Additional Application Server Instance

1. 2. 3.

You check the hardware and software requirements [page 20] for every installation host on which you want to install one or more additional application server instances. You identify basic SAP system installation parameters [page 25]. You can now continue with Preparation [page 39].

2013-07-15

CUSTOMER

19/132

3 3.2

Planning Hardware and Software Requirements

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

Pº›bM„ Pº›bM„ Pº›bM„ Pº›bM„

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. If you want to install a printer on a host other than the primary application server instance host (for example, on a separate database instance host), make sure that the printer can be accessed under UNIX.

Process Flow

1. 2.

Check the Product Availability Matrix at http://service.sap.com/pam for supported operating system releases. Check the hardware and software requirements using: Pº›bM„ The Prerequisite Checker: Pº›bMã Standalone (optional) before the installation process For more information, see Running the Prerequisites Check Standalone [page 21]. Pº›bMã Integrated in the installation tool (mandatory) as part of the installation process For more information, see Running the Installer [page 66].
NOTE

3.

For the most recent updates to the Prerequisite Checker, always check SAP Note 855498. Pº›bM„ The hardware and software requirements tables in Requirements for the SAP System Hosts [page 22]. 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: Pº›bM„ You use the Quick Sizer tool available at http://service.sap.com/sizing. Pº›bM„ You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing depending on: Pº›bMã The set of applications to be deployed Pº›bMã How intensively the applications are to be used Pº›bMã The number of users

20/132

CUSTOMER

2013-07-15

3 3.2

Planning Hardware and Software Requirements

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

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

When installing your SAP system, the Installer automatically starts the Prerequisites Check and checks the hardware and software requirements in the background.
Procedure

1.

2. 3. 4.

Make the installer available on the host where you want to run the Prerequisites Check: 1. Download the latest version of the software provisioning manager 1.0 archive SWPM10SP<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 1.0 archive to a local directory using the following command: SAPCAR –xvf <download directory>/<path>/<Archive>.SAR -R <unpack directory>. Start the installer as described in Running the Installer [page 66]. On the Welcome screen, choose <SAP product> <Database> Preparations Prerequisites Check . Follow the instructions in the installer dialogs and enter the required parameters.
NOTE

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

5.

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.

2013-07-15

CUSTOMER

21/132

3 3.2

Planning Hardware and Software Requirements

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

The information here is not intended to replace the operating system documentation. For more information, see your operating system documentation. You can perform AIX-specific steps using the following tools: ªïÓˇmP Manually by entering AIX commands with the appropriate options ªïÓˇmP 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 ).
Hardware Requirements Requirement Values and Activities

Distribution of the Oracle We recommend using a redundant storage solution such as RAID5 for data security Database reasons. To calculate how much storage is required for your Oracle database, see the Database System Configuration guide in SAP Database Guide: Oracle in the SAP Library [page 10] at: ªïÓˇmP SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1: Function-Oriented View Database Administration Database Administration for Oracle ªïÓˇmP SAP NetWeaver 7.3 and higher: SAP NetWeaver Library: Function-Oriented View Administration of Databases Database Administration for Oracle . Hardware Your operating system platform must be 64-bit. Processing Units The number or physical or virtual processing units usable by the operating system image must be equal or greater than 2 for application server instances and database instances. For an ASCS instance and SCS instance running on a separate host, 1 physical or virtual processing units usable by the operating system image might be sufficient. Examples for processing units are Processor Cores or Hardware Threads (Multithreading). In a virtualized environment, you must take care that adequate processor resources are available to support the workloads of the running SAP systems. Optical Media Drive ISO 9660 compatible Hard Disk Space ªïÓˇmP General Requirements: ªïÓˇm? 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 54]. ªïÓˇm? 1.2 GB of temporary disk space for the installation. ªïÓˇm? 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.

22/132

CUSTOMER

2013-07-15

3 3.2

Planning Hardware and Software Requirements Values and Activities

Requirement

RAM

Èn·ÃÅÂ 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 43] and the appropriate database-specific information listed below. Èn·ÃÅ Central services instance (SCS) for Java: Minimum 3.5 GB Èn·ÃÅ Enqueue replication server instance for the SCS (if required): Minimum 3.5 GB Èn·ÃÅ Central services instance for ABAP (ASCS): Minimum 3.5 GB Èn·ÃÅ Enqueue replication server instance for the ASCS (if required): Minimum 3.5 GB Èn·ÃÅ Database Instance: Minimum 80 GB For more information about space requirements for the separate file systems and directories, see Oracle Directories [page 48]. Èn·ÃÅ Primary application server instance: Minimum 11 GB Èn·ÃÅ Additional application server instance: Minimum 11 GB Èn·ÃÅ SAP Host Agent: Minimum 1 GB Èn·ÃÅ Diagnostics agent: Minimum 3 GB The following lists the RAM requirements for each instance. If you install several instances on one host, you have to add up the requirements accordingly. Èn·ÃÅÂ Central services instance for Java (SCS) Minimum 1 GB Èn·ÃÅÂ Enqueue replication server instance for the SCS (if required) Minimum 1 GB Èn·ÃÅÂ Central services instance for ABAP (ASCS) Minimum 1 GB Èn·ÃÅÂ Enqueue replication server instance for the ASCS (if required) Minimum 1 GB Èn·ÃÅÂ Database Instance: Minimum 1 GB
NOTE

Èn·ÃÅÂ Èn·ÃÅÂ Èn·ÃÅÂ Èn·ÃÅÂ

The default value used by the installer is 50 percent of the entire RAM. Primary application server instance: Minimum 8 GB Additional application server instance: Minimum 8 GB SAP Host Agent: Minimum 0.5 GB Diagnostics agent: Minimum 1 GB

2013-07-15

CUSTOMER

23/132

3 3.2

Planning Hardware and Software Requirements Values and Activities

Requirement

Swap Space

sû€ÌB. You need hard disk drives with sufficient space for swap. You can calculate the required swap space as follows: sû€ÌBA Optimistic strategy: In addition, you need at least 20 GB for the primary application server instance and at least another 10 GB for the SCS instance and also for every additional application server instance. sû€ÌBA Defensive strategy: 3 * RAM, at least 20 GB sû€ÌBA In addition, for the database instance you need: sû€ÌBH 0.75 * RAM, if RAM is greater than 8 GB sû€ÌBH 1 * RAM, if RAM is less than 8 GB sû€ÌBH For the latest information about recommended paging space, see SAP Note 1121904. You can execute memlimits to verify paging space size and kernel settings as follows: 1. Make sure that the SAPCAR program is available on the installation host. If SAPCAR is not available, you can download it from http://service.sap.com/ swdc. 2. Make the SAPEXE.SAR archive available on the installation host. This archive is contained in the folder K_<Kernel Version>_<U/N>_<OS>/DBINDEP of the installation media. 3. To unpack the file memlimits, enter the following commands:
SAPCAR -xvfg SAPEXE.SAR memlimits

4.

Start memlimits using the following command:
./memlimits -l 20000

If you see error messages, increase the paging space and rerun memlimits until there are no more errors.
Software Requirements Requirement Values and Activities

Database software Operating system version

Check the Product Availability Matrix (PAM) at http://service.sap.com/ pam for supported database platforms. Your operating system platform must be 64-bit. Check the Product Availability Matrix (PAM) at http://service.sap.com/ pam for supported operating system versions. To check the operating system version on your installation hosts, enter the relevant command for your operating system release: sû€ÌB. For AIX 7.1, enter the following command:
oslevel -s

Depending on the SAP kernel version, the output should be at least: 7.20 kernel: 7100-00-00–0000 7.20_EXT kernel: 7100-00-00–0000 sû€ÌB. For AIX 6.1, enter the following command:
oslevel -s

AIX kernel parameters

Depending on the SAP kernel version, the output should be at least: 7.20 kernel: 6100-00-01 7.20_EXT kernel: 6100-02-08-1015 sû€ÌB. To adjust AIX Virtual Memory Management settings, see SAP Note 973227.

24/132

CUSTOMER

2013-07-15

3 3.3

Planning Basic SAP System Installation Parameters Values and Activities

Requirement

National Language Support (NLS)
Other Requirements Requirement

Make sure that National Language Support (NLS) and corresponding locales are installed.

Values and Activities

Additional software

Make sure that the following additional file sets are installed: ^Ufi¶€ bos.adt – Base Application Development ^Ufi¶€ bos.perf – performance and diagnostics tools ^Ufi¶€ perfagent.tools – performance monitoring tools ^Ufi¶€ bos.perf.libperfstat – Performance Statistics Library 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. 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). For more information, see SAP Note 202227. Shared file systems for If application servers are installed decentralized, a “shared” file system must be decentralized systems installed, for example Network File System (NFS). C++ Runtime environment Check the C++ runtime level with the following commands: ^Ufi¶€ AIX 7.1: ^Ufi¶Ï #lslpp —L xlC.aix*.rte Depending on the SAP kernel version, the output should be at least: 7.20 kernel: 11.1.0.1. 7.20_EXT kernel: 12.1.0.1. ^Ufi¶Ï #lslpp —L xlC.rte Depending on the SAP kernel version, the output should be at least: 7.20 kernel: 11.1.0.1. 7.20_EXT kernel: 12.1.0.1. ^Ufi¶€ AIX 6.1: ^Ufi¶Ï #lslpp —L xlC.aix*.rte Depending on the SAP kernel version, the output should be at least: 7.20 kernel: 9.0.0.10. 7.20_EXT kernel: 12.1.0.1. ^Ufi¶Ï #lslpp —L xlC.rte Depending on the SAP kernel version, the output should be at least: 7.20 kernel: 9.0.0.10. 7.20_EXT kernel: 12.1.0.1.

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: ^Ufi¶€ Typical

2013-07-15

CUSTOMER

25/132

3 3.3

Planning Basic SAP System Installation Parameters

If you choose Typical, the installation is performed with default settings. This means that you only have to respond to a small selection of prompts including at least the following, which are described in the corresponding tables below: tä}
Ô SAP system ID and Database Connectivity Parameters tä}
Ô Master password tä}
Ô 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. tä}
» 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 SAP system installation parameters that you need to specify before installing your SAP system: tä}
» SAP System Parameters tä}
» SAP System Database Parameters tä}
» Diagnostics Agent Parameters For all other installation parameters, use the F1 help in the installer screens.
SAP System Installation Parameters Parameters Description

Unicode System

SAP System ID <SAPSID>

Every new installation of an SAP system is Unicode. You can only deselect this option if you perform the system copy for a nonUnicode SAP system that has been upgraded to the current release. If you install an additional application server instance in an existing non-Unicode system (that has been upgraded to the current release), the additional application server instance is installed automatically as a non-Unicode instance. The installer determines if a non-Unicode system exists and chooses the right executables for the system type. The SAP system ID <SAPSID> identifies the entire 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 central services instance, which is the first instance to be installed in a distributed system.

26/132

CUSTOMER

2013-07-15

3 3.3

Planning Basic SAP System Installation Parameters Description CAUTION

Parameters

Choose your SAP system ID carefully. Renaming is difficult and requires you to reinstall the SAP system. Make sure that your SAP system ID: É˚†[\© Is unique throughout your organization. Do not use an existing <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 ADM ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR

É˚†[\© If you want to install an additional application server instance, make sure that no gateway instance with the same SAP System ID (SAPSID) exists in your SAP system landscape. Instance Number of the SAP Technical identifier for internal processes. It consists of a two-digit number from System 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 instance numbers of SAP systems that already exist on the installation host, look for subdirectories ending with <nn> of local (not mounted) /usr/sap/ <SAPSID> directories. The value <nn> is the number assigned to the instance. For more information about the naming of SAP system instances, see SAP Directories [page 43].
CAUTION

/<sapmnt>/<SAPSID>/ profile or /usr/sap/ <SAPSID>/SYS/profile

If you are using NIM Service Handler (NIMSH), do not use 01 or 02 for the instance number. The installer uses the instance number for the internal message server port 39<instance number> (see row “Message Server Port” in this table below). The NIM client daemon uses reserved ports 3901 and 3902. The installer retrieves parameters from the SAP system profile directory of an existing SAP system. SAP profiles are operating system files that contain instance configuration information. The installer prompts you to enter the location of the profile directory when the installation option that you execute is not the first one belonging to your SAP system installation, for example if you are performing a distributed installation or if you are installing an additional application server instance to an existing SAP system. See also the description of the parameters SAP System ID and Database ID.

2013-07-15

CUSTOMER

27/132

3 3.3

Planning Basic SAP System Installation Parameters Description
/usr/sap/<SAPSID>/SYS/profile is the soft link referring to /<sapmnt>/<SAPSID>/ profile.

Parameters

Master Password

Common password for all users that are created during the installation: =µö“ÂH Operating system users (for example <sapsid>adm)
NOTE

The Master Password is not used as password for the Database Users such as Database Administrator User or DB Connect User.
CAUTION

If you did not create the operating system users manually before the installation, the installer creates them with the common master password (see table Operating System Users). In this case, make sure that the master password meets the requirements of your operating system. =µö“ÂH ABAP users: SAP*, DDIC, and EARLYWATCH. =µö“ÂH Java users (for example J2EE_ADMIN) =µö“ÂH Secure Store key phrase For more information, see table Key Phrase for Secure Store Settings. Password policy The master password must meet the following requirements: =µö“ÂH It must be 8 to 14 characters long =µö“ÂH It must contain at least one digit (0-9) =µö“ÂH It must not contain \ (backslash) and " (double quote) =µö“ÂH It must contain at least one letter (a-z, A-Z) =µö“ÂH It must not begin with a digit nor an underscore =µö“ÂH It can contain the following characters: _, #, $, a-z, A-Z, 0-9 =µö“ÂH Depending on the installation option, additional restrictions may apply (for example, the master password must not contain the name of a Java user created during the installation). Message Server Port
CAUTION

The message server port number must be unique for the SAP system on all hosts. If there are several message port numbers on one host, all must be unique. Port Number of the SAP Message Server: If you do not specify a value, the default port number is used. ABAP Message Server Port There 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. Java Message Server Port The Java message server only uses the internal message server port. The SCS instance profile contains the configuration for the Java message server.

28/132

CUSTOMER

2013-07-15

3 3.3

Planning Basic SAP System Installation Parameters Description

Parameters

The parameter rdisp/msserv is set to 0, so that the external port is not open. The internal message server port uses the parameter rdisp/msserv_internal with default value 39<nn>, where <nn> is the instance number of the SCS message server instance. For more information about the parameters used for message server ports, see SAP Note 821875. Java Administrator User The installer creates this user in the ABAP system. After the installation, this user is available both in the ABAP and in the Java system. The installer sets the user name J2EE_ADMIN and the master password by default. If required, you can choose another user name and password according to your requirements. Java Guest User This user is for employees who do not belong to a company or who have registered as company users and who are waiting for approval. Guest users belong to the default group Authenticated Users. The installer creates this user in the ABAP system. After the installation, it is available both in the ABAP and in the Java system. The installer sets the user name J2EE_GUEST and the master password by default. If required, you can choose another user name and password according to your requirements. For more information about supported UME data sources and change options, see SAP Note 718383. Communication User The installer creates this user in the ABAP system. After the installation, it is available both in the ABAP and in the Java system This user is used for the communication between the ABAP system and the Java system. The installer sets the user name SAPJSF and the master password by default. If required, you can choose another user name and password according to your requirements. For more information about supported UME data sources and change options, see SAP Note 718383. Key Phrase for Secure Store This is a random word or phrase that is used to encrypt the secure store. Settings The Java EE engine uses this phrase to generate the key that is used to encrypt the data. The uniqueness of the phrase you use contributes to the uniqueness of the resulting key.
RECOMMENDATION

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

Path to SAPCRYPTO.SAR

If you choose Typical mode, the installer sets the master password for the key phrase. In this case, make sure that you replace the master password with the required unique key phrase either in the Parameter Summary screen or after the installation has finished. 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

2013-07-15

CUSTOMER

29/132

3 3.3

Planning Basic SAP System Installation Parameters Description

Parameters

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 reexport of the software products, authorization is required from the German export control authorities. This might also be required from your responsible national export control authorities. This also applies to transfers to affiliated companies. Corresponding laws and regulations in the recipient country may also exist which restrict the import or the use of these software products. DNS Domain Name for SAP If you want to use HTTP-based URL frameworks such as Web Dynpro applications, System 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.
EXAMPLE

If your application server host is called kirk.wdf.sap.com, the DNS Domain Name is wdf.sap.com.
SAP System Database Installation Parameters Parameters Description

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 you to reinstall the SAP system. 3]°“ If you want to install a new database: Make sure that your database ID: 3]°“a Is unique throughout your organization 3]°“a Consists of exactly three alphanumeric characters 3]°“a Contains only uppercase letters 3]°“a Has a letter for the first character 3]°“a Does not include any of the following, which are reserved IDs:
ADD ADM ALL AMD AND ANY ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF

30/132

CUSTOMER

2013-07-15

3 3.3

Planning Basic SAP System Installation Parameters Description
OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR

Parameters

_5xg˚9 MCOD only: If you want to use an existing database system, enter exactly the database ID of the existing database to which you want to add the system. For more information, see Installation of Multiple Components in One Database [page 103]. Database schema, Password The Java database schema is named SAP<SCHEMAID>DB. Default name is SAPSR3DB. The ABAP database schema is named SAP<SCHEMAID>. Default name is SAPSR3.
RECOMMENDATION

Choose a <SCHEMAID> that is different from your <SAPSID>. It might cause problems when you copy a system where <SCHEMAID> is the same as <SAPSID>, and the database-specific method used for the copy does not allow you to rename the database schemas. In certain situations, you might create a system copy with a new <SAPSID>, but where the database schema has the old <SAPSID>. This is not a technical problem, but might confuse the system administrator. Oracle Listener Name, _5xg˚9 If you install the database instance on a host where no other Oracle database Oracle Listener Port, Oracle is installed, you normally do not have to change the default values for Listener Listener Domain Name and Listener Port. _5xg˚9 If there is already an Oracle database installed on your installation host, you can either use one listener for both databases or you have to specify an unused Listener Name and an unused Listener Port for the new listener. For more information if you use one listener for both databases, see SAP Note 98252. _5xg˚9 All additional application server instances of an SAP system must use the same Listener Port than the database instance. _5xg˚9 The default domain in the network configuration files is WORLD. Tablespaces, Datafiles An Oracle database consists of one or more logical storage units called tablespaces, which collectively store all of the database's data. Each tablespace in an Oracle database consists of one or more files called datafiles, which are physical structures that conform to the operating system in which Oracle is running. MaxDatafileSize is the initial size of the tablespace datafile and its mapping to the new tablespace layout while importing the external file DBSIZE.XML. The installer prompts you to enter MaxDatafileSize in MB: _5xg˚9 0: Datafile size defined in DBSIZE.XML is not changed. _5xg˚9 2000: Default datafile size. _5xg˚9 10000: Maximum datafile size. For more information about space requirements of the SAP datafiles (sapdata 1 - 4), see Hardware and Software Requirements Tables [page 22].
Diagnostics Agent Parameters

The diagnostics agent is installed automatically with the SAP system.

2013-07-15

CUSTOMER

31/132

3 3.3

Planning Basic SAP System Installation Parameters Description

Parameters

System ID of 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 ADM ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR

Instance Number of the Diagnostics Agent

Technical identifier for internal processes for the diagnostics agent, consisting of a two-digit number from 00 to 97. Default is 97. If 97 is already used for an instance number, the diagnostics agent instance number is set automatically to the next free and valid instance number. The instance number is used to specify the name of the diagnostics agent instance directory that the installer automatically creates during the installation. The directory of the diagnostics agent instance is called SMDA<Instance_Number>. For more information, see SAP Directories [page 43]. The same restrictions apply as in “Instance Number of the SAP System” (see above). System Landscape Directory You can choose between the following options: (SLD) Destination ³ð¬#¶ Register in existing central SLD The installer only prompts you for the parameters listed below in this table if you select this option.
RECOMMENDATION

We recommend that you select this option. No SLD destination ³ð¬#¶ If you select this option: ³ð¬#Ù You have to configure the SLD destination for the diagnostics agent manually after the installation with the installer has finished. ³ð¬#Ù The installer does not prompt you for the parameters listed below in this table. System Landscape Directory The host name of the SLD (SLD): HTTP Host System Landscape Directory The HTTP port of the Java system where the SLD is installed. The following naming (SLD): convention applies: HTTP Port 5<instance_number>00.

32/132

CUSTOMER

2013-07-15

3 3.4

Planning SAP System Transport Host Description EXAMPLE

Parameters

If the instance number of your Java system is 01, the SLD HTTP Port is 50100. System Landscape Directory You have to enter the existing SLD Data Supplier User and the password of the (SLD) : central SLD. Data Supplier User and password

3.4 SAP System Transport Host
The transport host contains the transport directory used by the SAP transport system to store transport data and change SAP system information, such as software programs, data dictionary data, or customization data. If you have several SAP systems, they are usually organized in transport domains. In most cases, all SAP systems in a transport domain have a common transport directory. When you install an SAP system, you have to decide which transport host and directory you want to use for your SAP system: üôıçùÛ Use the transport directory that the installer creates during the installation of the SAP system by default on the global host: The installer by default creates the transport directory on the global host in /usr/sap/trans. üôıçùÛ Use a transport directory located on a host other than the default host: üôıçù´ You can use an existing transport directory and host in your SAP system landscape. üôıçù´ You can set up a new transport directory on a different host. In either case, you must prepare this host for use by the new SAP system. For more information, see Exporting and Mounting the Global Transport Directory [page 65].
More Information

üôıçùÛ Required File Systems and Directories [page 43] üôıçùÛ See the SAP Library [page 10]: üôıçù´ SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1: Function-Oriented View ABAP Technology / Application Server ABAP Administration Tools for AS ABAP Transport and Change Management Change and Transport System Transport Management System (BC-CTS-TMS) üôıçù´ SAP NetWeaver 7.3 and higher: Solution Life Cycle Management Software Logistics Change and Transport System Change and Transport System – Overview Basics of the Change and Transport System Transport Management System – Concept

3.5 Planning the Switchover Cluster
You can reduce unplanned downtime for your SAP system by setting up a switchover cluster. This setup installs critical software units – known as “single points of failure” (SPOFs) – across multiple host

2013-07-15

CUSTOMER

33/132

3 3.5

Planning Planning the Switchover Cluster

machines in the cluster. In the event of a failure on the primary node, proprietary switchover software automatically switches the failed software unit to another hardware node in the cluster. Manual intervention is not required. Applications accessing the failed software unit might experience a short delay but can then resume processing as normal. Switchover clusters also have the advantage that you can deliberately initiate switchover to free up a particular node for planned system maintenance. Switchover solutions can protect against hardware failure and operating system failure but not against human error, such as operator errors or faulty application software. Additional downtime might be caused by upgrading your SAP system or applying patches to it. Without a switchover cluster, the SAP system SPOFs – central services instance, the database instance, and the central file share – are vulnerable to failure because they cannot be replicated. All of these can only exist once in a normal SAP system. You can protect software units that are not SPOFs against failure by making them redundant, which means simply installing multiple instances. For example, you can add additional application server instances. This complements the switchover solution and is an essential part of building high availability (HA) into your SAP system.
RECOMMENDATION

We recommend switchover clusters to improve the availability of your SAP system. A switchover cluster consists of: ÂUÅ"D A hardware cluster of two or more physically separate host machines to run multiple copies of the critical software units, in an SAP system the SPOFs referred to above ÂUÅ"D Switchover software to detect failure in a node and switch the affected software unit to the standby node, where it can continue operating ÂUÅ"D A mechanism to enable application software to seamlessly continue working with the switched software unit – normally this is achieved by virtual addressing (although identity switchover is also possible)
Prerequisites

You must first discuss switchover clusters with your hardware partner because this is a complex technical area. In particular, you need to choose a proprietary switchover product that works with your operating system. We recommend that you read the following documentation before you start: ÂUÅ"D Check the information and the installation guides that are available at http://scn.sap.com/docs/ DOC-7848. ÂUÅ"D On database level, IBM provides a high-availability cluster solution for Linux and AIX only that is called IBM Tivoli System Automation for Multiplatforms (SA MP). IBM also provides a free two-node license of SA MP for the DB2 database server. The corresponding installation guide describes how to set

34/132

CUSTOMER

2013-07-15

3 3.5

Planning Planning the Switchover Cluster

−1snŽ‰

−1snŽ‰ −1snŽ‰ −1snŽ‰

up a switchover cluster with SA MP based on the DB2 feature “High Availability and Disaster Recovery (HADR)” or a shared disk. More information: IBM DB2 High Availability Solution: IBM Tivoli System Automation for Multiplatforms at http:// service.sap.com/instguidesnw <Your SAP NetWeaver release> Installation Installation – SAP NetWeaver Systems Solaris SPARC only: On database level, IBM provides a high-availability cluster solution for Linux and AIX only that is called IBM Tivoli System Automation for Multiplatforms (SA MP). IBM also provides a free two-node license of SA MP for the DB2 database server. The corresponding installation guide describes how to set up a switchover cluster with SA MP based on the DB2 feature “High Availability and Disaster Recovery (HADR)” or a shared disk. More information: IBM DB2 High Availability Solution: IBM Tivoli System Automation for Multiplatforms at http:// service.sap.com/instguidesnw <Your SAP NetWeaver release> Installation Installation – SAP NetWeaver Systems The enqueue replication server (ERS) is essential for a high-availability system. You need one ERS for the Java SCS and one ERS for the ASCS installed in your system. The enqueue replication server (ERS) is essential for a high-availability system. You need one ERS for the ASCS installed in your system. The enqueue replication server (ERS) is essential for a high-availability system. You need one ERS for the Java SCS installed in your system.

2013-07-15

CUSTOMER

35/132

3 3.5

Planning Planning the Switchover Cluster

Features

\ÆdЂBˇë7–ÝñÒ“Ä@Pª%C<Switchover Setup NOTE

This figure and the figures in this section are only examples. Only the instances relevant to the switchover are shown – for example, the primary application server instance is not shown. These graphics summarize the overall setup and do not show the exact constellation for an installation based on one of the available technologies (ABAP, ABAP+Java, or Java). These graphics summarize the overall setup and do not show the exact constellation for an installation based on one of the available technologies (ABAP or Java). You need to discuss your individual HA setup with your HA partner.

36/132

CUSTOMER

2013-07-15

3 3.5

Planning Planning the Switchover Cluster

+U›¹Þ €ÄFko*¥VÁ¡ªèHSwitchover Cluster

Constraints

This documentation concentrates on the switchover solution for the central services instance. For more information about how to protect the Network File System (NFS) software and the database instance by using switchover software or (for of the database) replicated database servers, contact your HA partner. This documentation concentrates on the switchover solution for the central services instance. For more information about how to protect the central file share and the database instance by using switchover software or (for of the database) replicated database servers, contact your HA partner. You need to make sure that your hardware is powerful enough and your configuration is robust enough to handle the increased workload after a switchover. Some reduction in performance might be acceptable after an emergency. However, it is not acceptable if the system comes to a standstill because it is overloaded after switchover.

2013-07-15

CUSTOMER

37/132

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

4 4.1

Preparation Preparation Checklist

4 Preparation

4.1 Preparation Checklist
This section includes the preparation steps that you have to perform for the following installation options: 1‡®¶ñ½ Standard, distributed, or high-availability system 1‡®¶ñ½ Additional application server instance Detailed information about the steps is available in the relevant section.
Standard, Distributed, or High-Availability System NOTE

In a standard system, all mandatory instances are installed on one host. Therefore, if you are installing a standard system, you can ignore references to other hosts. 1. 2. 3. 4. 5. 6. 7. 8. 9. You make sure that the required operating system users and groups [page 40] are created. You set up file systems [page 43] and make sure that the required disk space is available for the directories to be created during the installation. If required, you set up virtual host names [page 53]. If you want to install a high-availability system, you perform switchover preparations [page 53]. If you want to share the transport directory trans from another system, export [page 65] this directory to your installation hosts. You install the SAP frontend software [page 54] on the desktop of the user. You make sure that the required installation media [page 54] are available on each host. If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page 105]. You can continue with Installation [page 59] .

Additional Application Server Instance

You have to perform the following preparations on the host where you install the additional application server instances: 1. You make sure that the required operating system users and groups [page 40] are created. 2. You set up file systems [page 43] and make sure that the required disk space is available for the directories to be created during the installation.

2013-07-15

CUSTOMER

39/132

4 4.2

Preparation Creating Operating System Users and Groups

3.

4. 5. 6. 7.

If you want to use virtual host names, you have to set the environment variable SAPINST_USE_HOSTNAME [page 53]. Alternatively you can specify the virtual host name in the command to start the installer. If you want to share the transport directory trans from another system, export [page 65] this directory to your installation hosts. You install the SAP frontend software [page 54] on the desktop of the user. You make sure that the required installation media [page 54] are available. You can continue with Installation [page 59] .

4.2 Creating Operating System Users and Groups
During the installation, the installer checks all required accounts (users, groups) and services on the local machine. The installer checks whether the required users and groups already exist. If not, it creates new users and groups as necessary. If you do not want the installer to create operating systems users, groups, and services automatically, you can optionally create them before the installation. This might be the case if you use central user management such as Network Information System (NIS). The installer checks if the required services are available on the host and creates them if necessary. See the log messages about the service entries and adapt the network-wide (NIS) entries accordingly. The installer checks the NIS users, groups, and services using NIS commands. However, the installer does not change NIS configurations.
RECOMMENDATION

For a distributed or a high-availability system, we recommend that you distribute account information (operating system users and groups) over the network, for example by using Network Information Service (NIS). If you want to use global accounts that are configured on a separate host, you can do this in one of the following ways: +¹úY You start the installer and choose Generic Installation Options <Database> Preparation Operating System Users and Groups . For more information, see Running the Installer [page 66]. +¹úY You create operating system users and groups manually. Make sure that you also check the settings for these operating system users.
Constraints

+¹úY Make sure that you set the limits for operating system users as described in SAP Note 323816. +¹úY All users must have identical environment settings. If you change the environment delivered by SAP, such as variables, paths, and so on, we do not assume responsibility.

40/132

CUSTOMER

2013-07-15

4 4.2

Preparation Creating Operating System Users and Groups

¡n½üfi† Do not delete any shell initialization scripts in the home directory of the OS users. This applies even if you do not intend to use the shells that these scripts are for. ¡n½üfi† If you use NFS-V4 file system, you have to create the ora<dbsid> user on the NFS server. You can do this either manually or by running Operating System Users and Groups. This user must have the same user ID as the ora<dbsid> user on the database server. Otherwise, you see the error message FSL-02098 Could not change owner of ... during the installation of the database instance. ¡n½üfi† If you install an SAP system with instances distributed over several hosts, make sure that the following requirements are met: ¡n½üfiî The user ID (UID) and group ID (GID) of each operating system user must be unique and the same on each instance host which belongs to the same SAP system. ¡n½üfiî Make sure that the group ID of group sapinst is always different from the group ID of any other group (for example, of group sapsys) used during the installation. For example, if you want to install an additional application server instance for an existing SAP system, you must make sure that the group ID of group sapinst created on the host of the additional application server instance is different from the group ID of any other group on the primary application server instance host of the existing SAP system. ¡n½üfiî If you use local operating system user accounts instead of central user management (for example, NIS), user <sapsid>adm, sapadm, and the database operating system user must have the same password on all hosts. ¡n½üfiî If you use local operating system user accounts, make sure that you install your SAP system in Custom mode and specify suitable IDs for user <sapsid>adm and group sapsys on all hosts. The IDs have to be the same on all hosts. If you choose Typical mode, you will not be asked to specify the user and group IDs. ¡n½üfi† If operating system users already exist, make sure that they are assigned to group sapinst. ¡n½üfi† If you create operating system users manually or use already existing operating system users, make sure that the home directory for each of these users is not the root directory ( / ) . ¡n½üfi† Make sure that the home directory of user <sapsid>adm is not critical for recursive changes on permissions: When operating system users are created by the installer, the permissions on the home directories of these users are changed recursively. This can cause unpredictable errors if you define a critical home directory. For example, the home directory must not be / or /usr/sap.
Operating System Users and Groups

The installer chooses available operating system user IDs and group IDs unless you are installing an additional application server instance. On an additional application server instance you have to enter the same IDs as on the host of the primary application server instance.

2013-07-15

CUSTOMER

41/132

4 4.2

Preparation Creating Operating System Users and Groups

Users and Groups of the SAP System User
root

Primary Group

Additional Groups
sapinst

Comment

No primary group is assigned.
sapsys sapsys

<sapsid>adm <dasid>adm

oper, dba, sapinst sapinst

sapadm ora<dbsid>

sapsys dba

sapinst oper, sapinst

Superuser of the UNIX operating system SAP system administrator Diagnostics agent administrator SAP host agent administrator Database administrator This user is only required on the host where the database instance runs.

User and Groups of the SAP Host Agent User
sapadm

Primary Group
sapsys

Additional Group
sapinst

Comment

SAP Host Agent administrator
NOTE

If sapadm does not exist, it is created during the SAP Host Agent installation using /bin/ false shell. Make sure that /bin/false can be used as a login shell. Add /bin/false to the list of valid login shells (attribute shells) in /
etc/security/ login.cfg.

Groups and Members of the SAP System Users Groups
sapsys oper dba sapinst

Members
<sapsid>adm, sapadm, <dasid>adm <sapsid>adm, ora<dbsid> <sapsid>adm, ora<dbsid> root, <sapsid>adm, ora<dbsid>, sapadm, <dasid>adm

Groups and Members of the SAP Host Agent User Groups
sapsys sapinst

Members
sapadm sapadm

42/132

CUSTOMER

2013-07-15

4 4.3

Preparation Required File Systems and Directories

4.3 Required File Systems and Directories
The following sections describe the directory structures for the SAP system, how to set up SAP file systems for the SAP system and, if required, raw devices on operating system level:
NOTE

The installation of any SAP system does not require a special file system setup or separate partitions. gMhÝ-Œ gMhÝ-Œ gMhÝ-Œ gMhÝ-Œ SAP Directories [page 43] Performing Switchover Preparations for High Availability [page 53] Oracle Directories [page 48] Setting Up File Systems for High-Availability [page 50]

4.3.1 SAP Directories
Depending on the installation option you have chosen, the installer automatically creates the directories listed in the following figures and tables. Before running the installation, you have to set up the required file systems manually. In addition, you have to make sure that the required disk space for the directories to be installed is available on the relevant hard disks. The figure below assumes that you have set up one file system for the SAP system mount directory <sapmnt> and one file system for the /usr/sap directory. However, you have to decide for which directories you want to set up separate file systems. If you do not set up any file system on your installation host, the installer creates all directories in the root directory (/ ) . The installer prompts you only for the <sapmnt> directory during the installation. The installer creates the following types of directories: gMhÝ-Œ Physically shared directories – for the SAP system gMhÝ-Œ Logically shared directories – for the SAP system and the diagnostics agent gMhÝ-Œ Local directories – for the SAP system and the diagnostics agent The following figure shows the directory structure of the SAP system:

2013-07-15

CUSTOMER

43/132

4 4.3

Preparation Required File Systems and Directories

þÃS#+u*ŽúÝ4?hÀÖ7&¢â*Directory Structure for an ABAP+Java System Physically Shared Directories (SAP System)

Physically shared directories reside on the global host and are shared by Network File System (NFS). The installer creates the following directories: þÃSż The directory /<sapmnt>/<SAPSID>, which contains SAP kernel and related files, is created on the first installation host. Normally, the first installation host is the host on which the central services instance is to run, but you can also choose another host for /<sapmnt>/<SAPSID>. You need to manually share this directory with Network File System (NFS) and – for a distributed system such as a high-availability system or a system with dialog instances – mount it from the other installation hosts. The installer creates the following shared directories during the SAP system installation. If you install an SAP system with instances distributed over several hosts, you have to share these directories for all hosts with the same operating system (see Exporting and Mounting Global Directories [page 66]): þÃSÅÓ þÃSÅÓ þÃSÅÓ
global

Contains globally shared data
profile

Contains the profiles of all instances
exe

þÃSÅÚ Contains a folder uc and a folder nuc, each with a platform-specific subfolder: þÃSŪ <sapmnt>/<SAPSID>/exe/uc/<platform> is used in Unicode systems.

44/132

CUSTOMER

2013-07-15

4 4.3

Preparation Required File Systems and Directories

Executable kernel programs are replicated from this directory to the exe directories of each Unicode system instance. Łêñº <sapmnt>/<SAPSID>/exe/nuc/<platform> is used in non-Unicode systems (see below). Executable kernel programs are replicated from this directory to the exe directories of each non-Unicode system instance (see below). ŁêñÊ Contains a folder jvm with the SAP JVM files Łêñ¬ The directory /usr/sap/trans, which is the global transport directory. If you want to use an existing transport directory, you have to mount it before you install the application server instance in question. Otherwise, the installer creates /usr/sap/trans locally. For more information, see Exporting and Mounting the Global Transport Directory [page 65].
Physically Shared SAP Directories Directory
<sapmnt>/SAPSID> /usr/sap/trans

Required Minimum Disk Space

Minimum 2 GB This value heavily depends on the use of your SAP system. For production systems, we recommend to use as much free space as available (at least 2.0 GB), because the space requirement normally grows dynamically. For the installation, it is sufficient to use 1 GB for each SAP system instance. You can enlarge the file system afterwards.

Logically Shared Directories (SAP System)

Logically shared directories reside on the local hosts with symbolic links to the global host. The installer creates the directory /usr/sap/<SAPSID>/SYS on each host. This directory contains the following symbolic links to physically shared directories: Łêñ¬ Soft link profile points to /sapmnt/<SAPSID>/profile Łêñ¬ Soft link global points to /sapmnt/<SAPSID>/global This directory contains the exe subdirectory with symbolic links pointing to the corresponding subdirectories of /<sapmnt>/<SAPSID>/exe on the SAP global host: Łêñ¬ Symbolic link uc (for Unicode) points to /sapmnt/<SAPSID>/exe/uc Łêñ¬ Symbolic link nuc (for non-Unicode) points to /sapmnt/<SAPSID>/exe/nuc Łêñ¬ Symbolic link run points to another symbolic link /usr/sap/<SAPSID>/SYS/exe/dbg in the same directory, and symbolic link dbg at last points to /sapmnt/<SAPSID>/exe/uc/<platform> Whenever a local instance is started, the sapcpe program checks the executables against those in the logically shared directories and, if necessary, replicates them to the local instance. The installer uses sapcpe to replicate the kernel automatically from /usr/sap/<SAPSID>/SYS/exe/ run/DIR_CT_RUN to /usr/sap/<SAPSID>/<INSTANCE/exe/DIR_EXECUTABLE for each SAP system instance, where <INSTANCE> is either DVEBMGS<Number> (primary application server instance) or D<Number> (additional application server instance)

2013-07-15

CUSTOMER

45/132

4 4.3

Preparation Required File Systems and Directories

Local Directories (SAP System)

The installer also creates local directories that reside on the local hosts. The directory /usr/sap/ <SAPSID> contains files for the operation of a local instance as well as symbolic links to the data for one system. This directory is physically located on each host in the SAP system and contains the following subdirectories: 1ÁÁÔ B
SYS NOTE

1ÁÁÔ B

1ÁÁÔ B 1ÁÁÔ B 1ÁÁÔ B

The subdirectories of /usr/sap/<SAPSID>/SYS have symbolic links to the corresponding subdirectories of /<sapmnt>/<SAPSID>, as shown in the figure above. Instance-specific directories with the following names: 1ÁÁÔ - The directory of the primary application server instance is called DVEBMGS<No>, where <No> is the instance number. 1ÁÁÔ - The directory of an additional application server instance is called D<No>, where <No> is the instance number. The directory of the central services instance for Java (SCS instance) is called SCS<No>, where <No> is the instance number. The directory of the central services instance for ABAP (ASCS instance) is called ASCS<No>, where <No> is the instance number. The directory of an enqueue replication server instance (ERS instance) is called ERS<No>, where <No> is the instance number. One ERS instance can be installed for the SCS instance, and one for the ASCS instance. If you install a high-availability system, you must install an ERS instance each for the ASCS instance and for the SCS instance.
Required Minimum Disk Space

Local SAP Directories Directory
/usr/sap/<SAPSID>/DVEBMGS<No> /usr/sap/<SAPSID>/D<No>

Description

/usr/sap/<SAPSID>/ASCS<No>

/usr/sap/<SAPSID>/ERS<No>

/usr/sap/<SAPSID>/SCS<No> /usr/sap/<SAPSID>/ERS<No>

Primary application server instance directory Additional application server instance directory ABAP central services instance (ASCS) directory (high-availability only) Enqueue replication server instance (ERS) directory for the ASCS (high-availability only) Java central services instance (SCS) directory Enqueue replication server instance (ERS) directory for the SCS (high-availability only)

Minimum 11 GB Minimum 11 GB 1 GB 1 GB

1 GB 1 GB

Local Directories (Diagnostics Agent)

The diagnostics agent has logically shared and local directories as shown in the following figure.

46/132

CUSTOMER

2013-07-15

4 4.3

Preparation Required File Systems and Directories

|5útÛªBV
èÞÿ%s$µfi⁄äÙDirectory Structure for the Diagnostics Agent

The diagnostics agent directory /usr/sap/<DASID> requires 1.5 GB of disk space. It contains the following subdirectories: |5ú™þc SYS, which is a logically shared directory |5ú™þc SMDA<No>, which is a local directory
Logically Shared Directories (Diagnostics Agent)

The logically shared directory SYS contains the following subdirectories: |5ú™þc |5ú™þc |5ú™þc
exe

Contains executable kernel programs
global

Contains globally shared data
profile

Contains the profiles of the Diagnostics Agent instance
Local Directories (Diagnostics Agent)

The local directory SMDA<No> contains the following subdirectories: The instance directory of the Diagnostics Agent instance is called SMDA<No>, where <No> is the instance number. It contains the instance-specific data of the Diagnostics Agent. It contains the following subdirectories: |5ú™þc |5ú™þc
script

Contains the smdsetup script
SMDAgent

2013-07-15

CUSTOMER

47/132

4 4.3

Preparation Required File Systems and Directories

Contains the Diagnostics Agent software and properties files ⁄ò¶
⁄ò¶

exe

Contains executable kernel programs
work

Contains log files
Directories of the SAP Host Agent

The SAP Host Agent has only local directories as shown in the following figure:

⁄òP2È3[9»÷pd˜#\?{Ò÷ÀøO›Directory Structure for the SAP Host Agent Local Directories (SAP Host Agent)

The SAP Host Agent directory /usr/sap/hostctrl requires 100 MB of disk space. It contains the following subdirectories: ⁄ò¶
⁄ò¶

exe

Contains the profile host_profile
work

Working directory of the SAP Host Agent

4.3.2 Oracle Directories
The figure below assumes that you have set up one file system for the oracle directory. However, you have to decide yourself for which directories you want to set up separate file systems. If you do not set up any file system on your installation host, the installer creates all directories in the root directory /.

48/132

CUSTOMER

2013-07-15

4 4.3

Preparation Required File Systems and Directories

Set up the required file system nodes for the Oracle database before the installation.

À¿¹ò{k=wøUsìH˜ÀÕM=Ú-ª’ÍOracle Directories (Graphical Overview)

The following table provides more information about the Oracle directories in detail, such as about their usage and disk space requirements.
Oracle Directories in Detail Directory
/oracle

Description

Required Minimum Disk Space

/oracle/client

Oracle base directory 43 GB Make sure that the /oracle file system has the permissions 755. File system for Oracle client software 100 MB The installer creates directory /
oracle/client/112_64/ instantclient during the

/oracle/stage/112_64

/oracle/<DBSID>

installation. Installation and upgrade directory 5.5 GB for database software (staging area) This directory is also used for Oracle upgrades. We recommend that you do not delete it after the installation. Home directory of user ora<dbsid> 100 MB for files of user ora<dbsid> (for We recommend that /oracle/ example, log files) <DBSID> does not reside in the root directory. It must reside in a file system with support for large files. Therefore, either create /oracle/ <DBSID> as a separate file system with support for large files or create /

2013-07-15

CUSTOMER

49/132

4 4.3

Preparation Required File Systems and Directories Description
oracle as a file system with support

Directory

Required Minimum Disk Space

/oracle/<DBSID>/112_64

/oracle/<DBSID>/origlogA /oracle/<DBSID>/origlogB /oracle/<DBSID>/mirrlogA /oracle/<DBSID>/mirrlogB /oracle/<DBSID>/oraarch

/oracle/<DBSID>/sapreorg

/oracle/<DBSID>/sapdata1 /oracle/<DBSID>/sapdata2 /oracle/<DBSID>/sapdata3 /oracle/<DBSID>/sapdata4

for large files and create /oracle/ <DBSID> as a directory in /oracle. Home directory for Oracle instance Ó)Tü“` Database instance: 4.0 GB <DBSID> Ó)Tü“` All other instances: 200 MB (<ORACLE_HOME>). Original set A of redo logs 200 MB Original set B of redo logs 200 MB Mirrored set A of redo logs 200 MB Mirrored set B of redo logs 200 MB New standard backup file system for For the installation, the archive Oracle offline redo logs directory /oracle/<DBSID>/oraarch Use a separate disk for the file requires at least 400 MB free disk space. system /oracle/<DBSID>/oraarch. For the operation of your SAP system, The file system /oracle/<SAPSID>/ we recommend that the archive saparch still remains but now only directory provides enough space for contains brbackup log files. /oracle/ archives between two backups. In a <SAPSID>/saparch is automatically production system, the amount created by the installer. archived each day is between 300 MB and 1 GB. Working directory for database 1.5 GB administration SAP data 30 GB For details, see the DBSIZE.XML file at the SAP data medium for the installation export SAP data (folder EXP1/DB/ORA/) and the SAP data DBSIZE.XML file at the medium for the Java component (folderJAVA_EXPORT/ DB/ORA) See also the Pre-Installation section in SAP Note 1704754.

4.3.3 Setting Up File Systems for a High-Availability System
Third-party technology is used to make the SAP directories available to the SAP system. The technologies of choice are NFS, shared disks, and cluster file system. If you have decided to use a highavailability (HA) solution for your SAP system, make sure that you properly address the HA requirements of the SAP file systems in your SAP environment with the HA partner of your choice. From the perspective of an SAP application, there are the following types of SAP Directories [page 43]: Ó)Tü“` Physically shared directories: /<sapmnt>/<SAPSID> and /usr/sap/trans Ó)Tü“` Logically shared directories that are bound to a node such as /usr/sap with the following local directories: Ó)Tü“
/usr/sap/<SAPSID>

50/132

CUSTOMER

2013-07-15

4 4.3

Preparation Required File Systems and Directories

Ó´Y$p /usr/sap/<SAPSID>/SYS Ó´Y$p /usr/sap/hostctrl Ó´Y$˜ Local directories that contain the SAP instances such as /usr/sap/<SAPSID>/ASCS<NR> Local directories that contain the SAP instances, such as /usr/sap/<SAPSID>/SCS<NR>
Prerequisites

You have already installed the hardware – that is, hosts, disks, and network – and decided how to distribute the database, SAP instances, and – if required – Network File System (NFS) server over the cluster nodes (that is, over the host machines). For more information, see Planning the Switchover Cluster [page 33] and contact your HA partner.
Procedure

1.

Create the file systems or raw partitions for the SAP instances you can switch over in such a way that the content can be made available to all nodes that can run the service. At least the central services (SCS) instance and the ABAP central services (ASCS) instance must be part of the switchover cluster. The SAP directories /sapmnt/<SAPSID> and /usr/sap/trans are usually mounted from a Network File System (NFS). However, an SAP instance directory /usr/sap/<SAPSID>/<INSTTYPE><NR> that you want to prepare for HA has to be always mounted on the cluster node currently running the instance. Do not mount such directories with NFS. Therefore, if the host running the primary application server instance is not the NFS server host, you might have to mount the file systems for /sapmnt/<SAPSID> and /usr/sap/trans on different physical disks from the file system for /usr/sap/<SAPSID>/<INSTTYPE><NR>.
CAUTION

2.

To start or stop an SAP instance, you have to either make the physically shared SAP directories under /<sapmnt>/<SAPSID>/ available to the server beforehand or you have to replace the links in /usr/sap/<SAPSID>/SYS by a physical copy. Consult your HA partner to clarify the best solution for the cluster software. Use the following approach for the file system for the /usr/sap/<SAPSID> directory: The /usr/sap/<SAPSID> directory contains at least two subdirectories (see also SAP Directories [page 43]): Ó´Y$˜ SYS, which contains links to the central directory /sapmnt/<SAPSID> Ó´Y$˜ <INSTTYPE><Number> – where the name is defined by the type of services and the application server number: Ó´Y$p DVEBMGS<Number> – which contains data for the primary application server instance Ó´Y$p D<Number> – which contains data for an additional application server instance Ó´Y$p J<Number> – which contains data of an application server instance Ó´Y$p ASCS<Number> – which contains data for the ABAP central services instance Ó´Y$p SCS<Number> – which contains data for the Java central services instance

2013-07-15

CUSTOMER

51/132

4 4.3

Preparation Required File Systems and Directories

Only <INSTTYPE><Number> directories need to be migrated with the SAP instances during the switchover. Therefore, instead of /usr/sap/<SAPSID>, create a file system for /usr/sap/<SAPSID>/ <INSTTYPE><Number> with the usual <> substitutions. The instance-specific directory name for the central services instance is normally ASCS<Number>. Migrating only these directories avoids mount conflicts when switching over to a node on which another application server instance is already running. The ASCS<Number> directory can join the /usr/sap/<SAPSID> tree instead of mounting on top of it. The instance-specific directory names for the central services instances are normally SCS<Number> for the Java central services instance and ASCS<NR> for the ABAP central services instance. Migrating only these directories avoids mount conflicts when switching over to a node on which another application server instance is already running. The ASCS<NR> and SCS<Number> directories can join the /usr/sap/<SAPSID> tree instead of mounting on top of it. The instance-specific directory name for the central services instance is normally SCS<Number>. Migrating only this directory avoids mount conflicts when switching over to a node on which another AS instance is already running. The SCS<Number> directory can join the /usr/sap/ <SAPSID> tree instead of mounting on top of it.
NOTE

3. 4.

This approach becomes increasingly important when you want to cluster the central services instances with other local instances running on the cluster hosts outside the control of the switchover software. This applies to the Enqueue Replication Server (ERS) and additional ABAP or Java application server instances. The result is a more efficient use of resources. You must use this approach for integrated installations of the application server with ABAP and Java stacks. You assign the local (not switching) file systems to permanent mount points. You assign the shared file systems as documented by your HA partner.
EXAMPLE

The graphic below shows an example of the file systems and disks in an HA setup Note that this is only an example. For more information on a setup that meets your needs, consult your HA partner.

52/132

CUSTOMER

2013-07-15

4 4.4

Preparation Using Virtual Host Names

˘mÂœP¥Ô¬à˚2⁄³&ÇÓ 9ÐVFile Systems and Disks in an HA Setup

4.4 Using Virtual Host Names
You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to conceal their physical network identities from each other. This can be useful when quickly moving SAP servers or complete server landscapes to alternative hardware without having to reinstall or reconfigure. If you want to install a high-availability (HA) system [page 13], you need the virtual host name when you install the ASCS instance and the SCS instance into a cluster.
Prerequisites

Make sure that the virtual host name can be correctly resolved in your Domain Name System (DNS) setup.
Procedure

Proceed as described in SAP Note 962955.

4.5 Performing Switchover Preparations for High Availability
To be able to use the required virtual host names [page 53], you have to set the installer property SAPINST_USE_HOSTNAME to specify the required virtual host name before you start the installer. For more information, see Running the Installer [page 66].

2013-07-15

CUSTOMER

53/132

4 4.6

Preparation Installing the SAP Front-End Software

Procedure

Assign the virtual IP addresses and host names for the SCS and ASCS instances, and (if required) NFS to appropriate failover groups.
NOTE

For more information on virtual addresses and virtual host names and how to assign resources to failover groups, ask your HA partner.

4.6 Installing the SAP Front-End Software
Before you start the installation, make sure that the SAP Front-end software is installed on at least one computer in your system environment to be able to log on to the SAP system after the installation has finished.
Procedure

1. 2.

Check SAP Note 147519 for the recommended SAP Front-end release. Install the SAP front-end software as described in the documentation SAP Front End Installation Guide - <Release> at: http://service.sap.com/installNW73 Installation - Clients

4.7 Preparing the Installation Media
This section describes how to prepare the installation media, which are available as follows: Fã‹Ñ© 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. Fã‹Ñ© The media containing the software to be installed, which are available as follows: Fã‹ÑÆ You normally obtain the physical installation media as part of the installation package. Fã‹ÑÆ 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.

54/132

CUSTOMER

2013-07-15

4 4.7

Preparation Preparing the Installation Media

Procedure

1.

Identify the required media for your installation [page 11] 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 release-specific media list for your SAP NetWeaver application. You can find the location of the media list in the Master Guide for your SAP Business Suite application or SAP NetWeaver application and release at http://service.sap.com/ instguides.
SAP Instance Installation Required Software Packages from Installation Media

Central ł©ˇ
Îù Software provisioning manager 1.0 archive SWPM10SP<support package services number>_<version number>.SAR instance for ł©ˇ
Îù UC or NUC Kernel (folder K_<N or U>_<Version>_<OS>) where U means Unicode and ABAP (ASCS) N means non-Unicode.
NOTE

Central services instance for Java (SCS) Database instance

Every new installation of an SAP system is Unicode. You can only use the nonUnicode kernel if you perform the system copy for a non-Unicode SAP system that has been upgraded to the current release. ł©ˇ
Îù Software provisioning manager 1.0 archive SWPM10SP<support package
number>_<version number>.SAR

ł©ˇ
Îù UC Kernel (folder K_U_<Version>_<OS>) where U means Unicode. ł©ˇ
Îù Software provisioning manager 1.0 archive SWPM10SP<support
number>_<version number>.SAR package

ł©ˇ
Îù UC or NUC Kernel (folder K_<N N means non-Unicode.
NOTE

or U>_<Version>_<OS>) where U means Unicode and

ł©ˇ
Îù ł©ˇ
Îù ł©ˇ
Îù ł©ˇ
Îù

Every new installation of an SAP system is Unicode. You can only use the nonUnicode kernel if you perform the system copy for a non-Unicode SAP system that has been upgraded to the current release. Database software Database patches (if available) Installation Export (folders EXP*) SAP NetWeaver Java Component (folders JAVA_*)
NOTE

Enqueue Replication Server

For an MCOD system you require the database client software instead of the database software and the database patches (if available). ł©ˇ
Îù Software provisioning manager 1.0 archive SWPM10SP<support package
number>_<version number>.SAR

ł©ˇ
Îù UC or NUC Kernel (folder K_<N N means non-Unicode.
NOTE

or U>_<Version>_<OS>) where U means Unicode and

Every new installation of an SAP system is Unicode. You can only use the nonUnicode kernel if you perform the system copy for a non-Unicode SAP system that has been upgraded to the current release.

2013-07-15

CUSTOMER

55/132

4 4.7

Preparation Preparing the Installation Media SAP Instance Installation

Required Software Packages from Installation Media

Primary application server instance

çdŽE˝ Software provisioning manager 1.0 archive SWPM10SP<support
number>_<version number>.SAR

package

çdŽE˝ UC or NUC Kernel (folder K_<N N means non-Unicode.
NOTE

or U>_<Version>_<OS>) where U means Unicode and

Additional application server instance

çdŽE˝ çdŽE˝ çdŽE˝ çdŽE˝

Every new installation of an SAP system is Unicode. You can only use the nonUnicode kernel if you perform the system copy for a non-Unicode SAP system that has been upgraded to the current release. SAP NetWeaver Java Component (folders JAVA_*) Database Client Software CLI Driver / JDBC Driver Software provisioning manager 1.0 archive SWPM10SP<support package
number>_<version number>.SAR or U>_<Version>_<OS>) where U means Unicode and

çdŽE˝ UC or NUC Kernel (folder K_<N N means non-Unicode.
NOTE

Every new installation of an SAP system is Unicode. You can only use the nonUnicode kernel if you perform the system copy for a non-Unicode SAP system that has been upgraded to the current release. SAP NetWeaver Java Component (folders JAVA_*) çdŽE˝ Database Client Software çdŽE˝
SAP Host Agent (Separate Installation Only) SAP Instance Installation Required Media

SAP Host Agent (separate installation only)

çdŽE˝ Software provisioning manager 1.0 archive
SWPM10SP<support package number>_<version number>.SAR

çdŽE˝ UC Kernel (folder K_U_<Version>_<OS>) where U means Unicode.

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

3.

Make sure that all users have read permissions for the directory where you want to unpacked the installer. Make the media containing the software to be installed available. You can do this in one of the following ways:

56/132

CUSTOMER

2013-07-15

4 4.7

Preparation Preparing the Installation Media

OÄœôQé Copy the required media folders directly to the installation hosts. OÄœôQé Mount media on a central media server that can be accessed from the installation hosts.
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.
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). Installations and Upgrades A-Z index <first letter of your product> <your product> <your product version> OÄœôQé http://service.sap.com/swdc Installations and Upgrades Browse our Download Catalog <your product> <your product version>
http://service.sap.com/swdc NOTE

OÄœôQé

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. 2. Create a download directory on the host where you want to run the installer. Identify all download objects that belong to one installation medium according to one or both of the following: OÄœôQé 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

3. 4.

51031387_1 51031387_2 ... Download the objects to the download directory. To correctly re-combine the media that are split into small parts, you must unpack all parts into the same directory.

2013-07-15

CUSTOMER

57/132

4 4.7

Preparation Preparing the Installation Media

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.

58/132

CUSTOMER

2013-07-15

5 5.1

Installation Installation Checklist

5 Installation

5.1 Installation Checklist
This section includes the installation steps that you have to perform for the: |v ¹( Standard system |v ¹( Distributed system |v ¹( High-availability system |v ¹( Additional application server instance Detailed information about the steps is available in the relevant chapter.
Standard System

1.

You install the SAP system [page 66].
NOTE

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

2.

Do not install the Oracle database software in advance. During the installation of the database instance, the installer stops the installation and prompts you to install the Oracle database software. This action is not required if you install an SAP system in an existing database (MCOD) [page 103]. You continue with Post-Installation [page 87].

Distributed System

1.

2.

3.

If you want to share the transport directory trans from another system, you have to mount [page 65] it from this system. Otherwise, we recommend that you share the trans directory that is created during the installation of the primary application server instance. On the host with the global file system (SAP global host), you do the following: 1. You run the installer [page 66] to install the central services instance for ABAP (ASCS instance) and – optionally – the enqueue replication server instance (ERS instance) for the ASCS instance. 2. You run the installer [page 66] to install the central services instance for Java (SCS instance) and – optionally – the enqueue replication server instance (ERS instance) for the SCS instance. 3. You export global directories [page 66] in <sapmnt>/<SAPSID> to the database and primary application server instance host. On the database instance host, you do the following:

2013-07-15

CUSTOMER

59/132

5 5.1

Installation Installation Checklist

1.

2.

You mount the global directories [page 66] in <sapmnt>/<SAPSID> that you exported from the SAP global host and – optionally – the trans directory that you exported [page 65] from the SAP transport host. You run the installer [page 66] to install the database instance.
NOTE

4.

5.

Do not install the Oracle database software in advance. During the installation of the database instance, the installer stops the installation and prompts you to install the Oracle database software. This action is not required if you install an SAP system in an existing database (MCOD) [page 103]. On the primary application server instance host, you do the following: 1. You mount the global directories [page 66] in <sapmnt>/<SAPSID> that you exported from the SAP global host. 2. You run the installer [page 66] to install the primary application server instance. 3. If you want to use the shared transport directory trans from another system, you also mount [page 65] this directory. You continue with Post-Installation [page 87].

Graphical Overview

The following figure shows how you install the various instances in a distributed system:

jýØáR÷àÙ½=˘í>÷鱪K˚WUÈDistribution of Instances in an ABAP+Java System

60/132

CUSTOMER

2013-07-15

5 5.1

Installation Installation Checklist

High-Availability System

1.

2.

3.

You need to make sure that you have already prepared the standby node, host B. You ought to have already made sure that it meets the hardware and software requirements and that it has all the necessary file systems, mount points, and (if required) Network File System (NFS). This is described in Performing Switchover Preparations for High Availability [page 53] and Setting Up File Systems for a High Availability System [page 50] If you want to share the transport directory trans from another system, you have to mount [page 65] it from this system. Otherwise we recommend that you share the trans directory that is created during the installation of the primary application server instance (see below). You set up the switchover cluster infrastructure as follows:
NOTE

4.

5.

6. 7.

8.

The following procedure is an example. In this example, we use only one primary cluster node, host A, and one standby cluster node, host B. If required, you can also install the ASCS instance and the SCS instance on different hosts. In this case, you require:
Ð…ãÊM At least one primary cluster node, host A1, for the primary node with the ASCS instance, and at least one primary cluster node, host A2, for the primary node with the SCS instance.
Ð…ãÊM At least one standby node, host B1, for the primary node with the ASCS instance, and at least one standby node, host B2, for the primary node with the SCS instance. You run the installer [page 66] to install the central services instance for ABAP (ASCS instance) and the related enqueue replication server instance (ERS instance) using the virtual host name [page 53] on the primary cluster node, host A. You run the installer [page 66] to install the central services instance for Java (SCS instance) and the related enqueue replication server instance (ERS instance) using the virtual host name [page 53] on the primary cluster node, host A. You export global directories [page 66] in <sapmnt>/<SAPSID> to the database host and to the primary application server instance host. You prepare the standby cluster node, host B, making sure that it meets the hardware and software requirements [page 20] and it has all the necessary file systems [page 50], mount points, and (if required) Network File System (NFS). You set up the user environment on the standby node, host B:
Ð…ãÊM You make sure that you use the same user and group IDs as on the primary node.
Ð…ãÊM You create the home directories of users and copy all files from the home directory of the primary node. For more information about the required operating system users and groups, see Creating Operating System Users [page 40].

2013-07-15

CUSTOMER

61/132

5 5.1

Installation Installation Checklist

You configure the switchover software and test that switchover functions correctly to all standby nodes in the cluster. 10. You repeat the following steps until you have finished installing the enqueue replication server (ERS instance) on all nodes in the cluster: 1. You perform the switchover to a node where you want to install the enqueue replication server instance (ERS instance) for the ASCS instance. 2. You run the installer [page 66] to install the enqueue replication server instance (ERS instance) for the ASCS instance on the standby node, host B. 3. You perform the switchover to a node where you want to install the enqueue replication server instance (ERS instance) for the SCS instance. 4. You run the installer [page 66] to install the enqueue replication server instance (ERS instance) for the SCS instance on the standby node, host B. 11. On the database instance host, you do the following: 9.
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. 2. You make available the global directories in <sapmnt>/<SAPSID> from the switchover cluster infrastructure and – optionally – from the SAP transport host. You run the installer [page 66] to install the database instance on the database instance host.
NOTE

Do not install the Oracle database software in advance. During the installation of the database instance, the installer stops and prompts you to install the Oracle database software. This action is not required if you install an SAP system in an existing database (MCOD) [page 103]. 12. 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 (SCS instance), which is protected by the cluster. 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. 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 instances (SCS instance and ASCS instance), which are protected by the cluster.

62/132

CUSTOMER

2013-07-15

5 5.1

Installation Installation Checklist

1. 2.

You mount the global directories [page 66] in <sapmnt>/<SAPSID> that you exported from the switchover cluster infrastructure. You run the installer [page 66] to install the database instance on the database instance host.
RECOMMENDATION

We recommend that the database instance is part of the hardware cluster or of any other proprietary high-availability solution for the database. 3. You run the installer [page 66] to install the primary application server instance. 4. If you want to use the shared transport directory trans from another system, you also mount [page 65] this directory (see above). 13. We recommend you to install additional application server (AS) instances to create redundancy. The AS instances are not a SPOF. Therefore, you do not need to include these instances in the cluster. 14. You continue with Post-Installation [page 87].
Graphical Overview

The following figure provides an overview of how you install the various instances in a high-availability installation:

’eÂ;L’+˙†döx_h;˜õêuø¸à|\Distribution of Instances in a High-Availability ABAP+Java System

2013-07-15

CUSTOMER

63/132

5 5.1

Installation Installation Checklist

Additional Application Server Instance Installation Steps for Additional Application Server Instances for a Standard System

1. 2.

3. 1.

On the main host on which your SAP system runs, you export global directories in <sapmnt>/ <SAPSID> to the database and primary application server instance host. On every additional application server instance host, you do the following: 1. You mount the global directories [page 66] in <sapmnt>/<SAPSID> that you exported from the SAP global host. 2. You run the installer [page 66] to install the additional application server instance. You continue with Post-Installation [page 87]. If you want to share the transport directory trans from another system, you have to mount [page 65] it from this system. Otherwise, we recommend that you share the trans directory that is created during the installation of the primary application server instance. On the SAP global host, you export global directories in <sapmnt>/<SAPSID> to the database and primary application server instance host. On every additional application server instance host, you do the following: 1. You mount the global directories [page 66] in <sapmnt>/<SAPSID> that you exported from the SAP global host. 2. You run the installer [page 66] to install the additional application server instance. 3. If you want to use the shared transport directory trans from another system, also mount [page 65] this directory. You continue with Post-Installation [page 87]. If you want to share the transport directory trans from another system, you have to mount [page 65] it from this system. Otherwise, we recommend that you share the trans directory that is created during the installation of the primary application server instance. On the primary node, host A, of the switchover cluster infrastructure, you export global directories in <sapmnt>/<SAPSID> to every additional application server instance host. On every additional application server instance host, you do the following: 1. You mount the global directories [page 66] in <sapmnt>/<SAPSID> that you exported from the SAP global host. 2. You run the installer [page 66] to install the additional application server instance. 3. If you want to use the shared transport directory trans from another system, you also mount [page 65] this directory. You continue with Post-Installation [page 87].

Installation Steps for an Application Server Instance for a Distributed System

2. 3.

4. 1.

Installation Steps for an Additional Application Server Instance for a High-Availability System

2. 3.

4.

64/132

CUSTOMER

2013-07-15

5 5.2

Installation Exporting and Mounting the Global Transport Directory

5.2 Exporting and Mounting the Global Transport Directory
In your SAP system landscape, a global transport directory for all SAP systems is required. The global transport directory is used by the Change and Transport System (CTS). The CTS helps you to organize development projects, and then transport the changes between the SAP systems in your system landscape. For more information, see the SAP Library [page 10] at: łá˚ÉbÚ SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1: Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Change and Transport System Transport Management System (BC-CTS-TMS) łá˚ÉbÚ SAP NetWeaver 7.3 and higher: Solution Life Cycle Management Software Logistics Change and Transport System Change and Transport System – Overview Basics of the Change and Transport System Transport Management System – Concept Consider the following: łá˚ÉbÚ If the global transport directory already exists, make sure that it is exported on the global transport directory host and mount it on the SAP instance installation host. łá˚ÉbÚ If the global transport directory does not exist, proceed as follows: łá˚Ébµ Create the transport directory (either on the host where the primary application server instance is running or on a file server). łá˚Ébµ Export it on the global transport directory host. łá˚Ébµ If you did not create the transport directory on your SAP instance installation host, mount it there.
Procedure
Exporting the Transport Directory

1. 2. 3.

Log on as user root to the host where the global transport directory /usr/sap/trans resides. Make sure that /usr/sap/trans belongs to the group sapsys and to the user root. If not already done, export the directory using Network File System (NFS).

Mounting the Transport Directory NOTE

If the transport directory resides on your local SAP instance installation host, you do not need to mount it. 1. 2. 3. Log on as user root to the host of the primary or additional application server instance, where / usr/sap/trans is to be mounted. Create the mount point /usr/sap/trans. Mount /usr/sap/trans using Network File System (NFS) from the exporting host.

2013-07-15

CUSTOMER

65/132

5 5.3

Installation Exporting and Mounting Global Directories

5.3 Exporting and Mounting Global Directories
If you install a database or an additional application server instance on a host other than the SAP Global host, you must mount global directories from the SAP Global host.
NOTE

There is no need to create the directories prior to the installation when you install a Central System. The global directories must be exported only in case of installing additional dialog instances.
Prerequisites

If you want to install the executables locally instead of sharing them, do not mount the exe directory with Network File System (NFS). Instead, create <sapmnt>/<SAPSID>/exe as a local directory (not a link) with a minimum of 1.5 GB free space.
Procedure

1.

Log on to the SAP Global host as user root and export the following directories with root access to the host where you want to install the new instance:
<sapmnt>/<SAPSID>/exe <sapmnt>/<SAPSID>/profile <sapmnt>/<SAPSID>/global

Make sure that the user root of the host where you want to install the new instance can access the exported directories.
CAUTION

2. 3.

Make sure that the global transport directory is mounted on every host where you want to install an SAP instance. For more information, see Exporting and Mounting the Global Transport Directory [page 65]. Otherwise, the installation fails. Log on to the host of the new instance that you want to install as user root. Create the following mount points and mount them from the SAP Global host:
<sapmnt>/<SAPSID>/exe <sapmnt>/<SAPSID>/profile <sapmnt>/<SAPSID>/global CAUTION

Make sure that the mount points under /<sapmnt>/<SAPSID>/ are permanent. Otherwise automatic start of the instance services does not work when you reboot the system.

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

66/132

CUSTOMER

2013-07-15

5 5.4

Installation Running the Installer

This procedure describes an installation where the installer and the installer GUI are running on the same host. If you need to see the installation on a remote display, we recommend that you perform a remote installation [page 75], where the installer GUI is running on a separate host from the installer. Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809.
Useful Information About the Installer

Y]«1…ç The installer creates the installation directory sapinst_instdir directly below the temporary directory. The installer finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environment variable. If no value is set for these variables, the installer uses /tmp as default installation directory. If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR to the required directory before you start the installer.
Shell Used Command
TEMP=<directory> export TEMP

Bourne shell (sh) C shell (csh) Korn shell (ksh)
CAUTION

setenv TEMP <directory> export TEMP=<directory>

Make sure that the installation directory is not mounted with NFS, otherwise there might be problems when the Java Virtual Machine is started. Y]«1…ç The installer creates a subdirectory for each installation option called <sapinst_instdir>/ <installation_option_directory>. Y]«1…ç The installer extracts itself to the temporary directory. These executables are deleted again 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. Y]«1…ç During the installation, the default port 21212 is used for communication between the installer GUI server and the installer GUI client. If this port is already in use, you see an error message. In this case or if you want the installer to use a specific port, open a command prompt and change to the required directory to which you unpacked the SWPM10SP<support package number>_<version number>.SAR file

2013-07-15

CUSTOMER

67/132

5 5.4

Installation Running the Installer

Execute the sapinst executable with the following command line parameter:
GUISERVER_DIALOG_PORT=<port_number_gui_server_to_gui_client>

8D)U}N To see a list of all available installer properties, start the installer as described above with the option -p: ./sapinst -p. 8D)U}N If you need to run the installer in accessibility mode, proceed as described in Running the Installer in Accessibility Mode [page 79]. 8D)U}N 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 pressing Ctrl + 8D)U}N If you want to install an SAP system in unattended mode, see SAP Note 950619.
Prerequisites

C

.

8D)U}N We recommend that you use the csh shell for the installation with the installer. If you want to use another shell, make sure that you have read SAP Note 202227. The installer uses csh scripts during the installation to obtain the environment for user <sapsid>adm. This is also true if user <sapsid>adm already exists from an earlier SAP system installation, and the shell of this user is not csh. Before you start the installer, execute the following command as user <sapsid>adm to make sure that the csh scripts are up-to-date:
/bin/csh -c "source /<home>/<sapsid>adm/.cshrc;env"

8D)U}N Make sure that your operating system does not delete the contents of the temporary directory / tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry. Make sure that the temporary directory has the permissions 777. 8D)U}N Make sure that you have at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the installer executables. If you cannot provide 300 MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or TMPDIR to another directory with 300 MB free space for the installer executables. You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation directory as described above in section Useful Information About the Installer. 8D)U}N Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where <host_name> is the host on which you want to display the installer GUI. You can set values for the DISPLAY environment variables as follows:
Shell Used Command
DISPLAY=<host_name>:0.0 export DISPLAY

Bourne shell (sh) C shell (csh) Korn shell (ksh)

setenv DISPLAY <host_name>:0.0 export DISPLAY=<host_name>:0.0

8D)U}N Make sure that umask is set to 022 for user root.

68/132

CUSTOMER

2013-07-15

5 5.4

Installation Running the Installer

As user root, enter the following command: umask 022 ,gQÊí Make sure that you have checked the following values for user root: ,gQʇ In csh, execute limit
Output
cputime filesize datasize stacksize coredumpsize descriptors memorysize

Properties
unlimited unlimited unlimited 8192 KB unlimited 8192 unlimited

,gQʇ In sh or ksh execute ulimit
Output
time(seconds) file(blocks) data(kbytes) stack(kbytes) coredump(blocks) nofiles(descriptors) memory(KBytes)

-a Properties
unlimited unlimited unlimited 8192 unlimited 8192 unlimited

If your parameter settings differ from the settings above, change these values accordingly.
EXAMPLE

If you have to change the value for descriptors to 8192, proceed as follows: ,gQʇ In csh execute:
limit descriptors 8192

,gQʇ In sh or ksh execute:
ulimit -n 8192

,gQÊí Make sure that you have defined the most important SAP system parameters as described in Basic SAP System Installation Parameters [page 25] before you start the installation. ,gQÊí 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]. ,gQÊí If you are installing a second or subsequent SAP system in an existing database (MCOD), make sure that the database is up and running before starting the installation. Check that the SYSTEM tablespace contains at least 400 MB of free space. If there is not enough space left, increase the size of this tablespace with BRSPACE or BRTOOLS. For more information, see Installation of Multiple Components in One Database [page 103]. ,gQÊí If you want to install an additional application server instance in an existing SAP system, make sure that:

2013-07-15

CUSTOMER

69/132

5 5.4

Installation Running the Installer

¥m-Ôp¸ There is exactly one entry in the /usr/sap/sapservices file for each SAP instance installed on this host. Be sure to check that the entry refers to the correct profile. ¥m-Ôp¸ There are no profile backup files with an underscore “_” in their profile name. If so, you must replace the “_” with a “.”.
EXAMPLE

Rename /usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2_D20081204 to / usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2.D20081204.
Procedure

1.

Log on to the installation host as user root.
CAUTION

Do not use an existing <sapsid>adm user.
CAUTION

2.

Make sure that the root user has not set any environment variables for a different SAP system or database. Make the installation media available on the installation host. For more information, see Preparing the Installation Media [page 54].
RECOMMENDATION

3.

Make the installation media locally available. For example, if you use Network File System (NFS), reading from media mounted with NFS might fail. Start the installer from the directory to which you unpacked the SWPM10SP<support package number>_<version number>.SAR file by executing the following command: /<path to unpack
directory>/sapinst NOTE

If you want to use a virtual host name, start the installer with the SAPINST_USE_HOSTNAME property as follows:
/<path to unpack directory>/sapinst SAPINST_USE_HOSTNAME=<virtual host name> CAUTION

4.

Make sure that the installation directory is not mounted with NFS, or there might be problems when the Java Virtual Machine is started. In the Welcome screen, choose the required option: ¥m-Ôp× Perform preparations Go to one of the following: ¥m-Ôp¸ Go to Generic Installation Options <Database> Preparations and choose the required task:
Preparations Remarks

LDAP Registration

Sets up LDAP support for an application server instance For more information about LDAP and Active Directory, see Integration of LDAP Directory Services [page 99].

70/132

CUSTOMER

2013-07-15

5 5.4

Installation Running the Installer Preparations Remarks

Installs a standalone SAP Host Agent. For more information, see Standalone SAP Host Agent [page 18]. Operating System Users and Allows you to use global accounts that are configured on a separate host Groups Run this installation option before you start the installation of the SAP system. SAP Host Agent

zmåz−r Go to <SAP NetWeaver Release> <Database> Preparations task:
Preparations Remarks

and choose the required

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

zmåz−˛ Install an SAP system To install an SAP Process Integration system, choose <SAP NetWeaver Release> <Database> SAP Systems Process Integration <System Variant> . You can install the following system variants:
System Variants Remarks

Standard System Distributed System

High-Availability System

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

zmåz−˛ Perform other tasks or install additional components Go to one of the following: zmåz−r Go to <SAP Product> <Database> and choose the required task:
Other Options Remarks

Additional SAP System Instances zmåz−{ Additional Application Server Instance: Installs one or more additional application server instances zmåz−{ 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) zmåz−{ 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 106].

zmåz−r Go to Generic Installation Options <Database>

and choose the required task:

2013-07-15

CUSTOMER

71/132

5 5.4

Installation Running the Installer 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 119].

5. 6.

Choose Next. 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. To start the installation, choose Start. 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.
NOTE

7.

8.

Ù¡<#Q¢ During the installation of the Oracle database instance, the installer stops the installation and prompts you to install the Oracle database software [page 81]. If you install an SAP system in an existing database (MCOD) [page 103], the installer prompts you for the existing database. After you have finished the installation of the Oracle database, you continue the database instance installation by choosing OK in the installer GUI of the database instance installation. Ù¡<#Q¢ Check SAP Note 1431800 for technical information about Oracle Release 11.2 in SAP environments. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer has finished. Sometimes these remain in the temporary directory.
NOTE

If there are errors with the extraction process of the installer, you can find the log file dev_selfex.out in the temporary directory.
RECOMMENDATION

Keep all installation directories until you are sure that the system, including all instances, is completely and correctly installed. Once the system is completely and correctly installed, make a copy of the installation directories with all their contents and save it to a physically separate medium, such as an optical media or a USB drive separate from your installation hosts. This might be useful for analyzing issues occurring later when you use the system. For

72/132

CUSTOMER

2013-07-15

5 5.5

Installation Additional Information About the Installer

security reasons, do not keep installation directories on installation hosts, but make sure that you delete them after saving them separately. 9. We recommend that you delete all files in the directory <user_home>/.sdtgui/. 10. If you copied the installer software to your hard disk, you can delete these files when the installation has successfully completed.

5.5 Additional Information About the Installer
The following sections provide additional information about the installer: V{Üf4 Interrupted Installation [page 73] V{Üf4 Performing a Remote Installation [page 75] V{Üf4 Starting the Installer GUI Separately [page 76] V{Üf4 Running the Installer in Accessibility Mode [page 79] V{Üf4 Entries in the Services File Created by the Installer [page 80] V{Üf4 Troubleshooting with the Installer [page 80]

5.5.1 Interrupted Installation
The SAP system installation might be interrupted for one of the following reasons: V{Üf4 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. V{Üf4 You interrupted the installation by choosing Cancel in the SAPinst 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

Stop

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. The installer stops the installation, closing the dialog box, the installer GUI, and the GUI server.

2013-07-15

CUSTOMER

73/132

5 5.5 Option

Installation Additional Information About the Installer Definition

Continue View Log
NOTE

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. The installer continues the installation from the current point. Access installation log files.

You can also terminate the installer by choosing Ctrl + C . However, we do not recommend that you use Ctrl + C , because this kills the process immediately.
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 local UNIX host as user root.
CAUTION

2.

Make sure that the root user has not set any environment variables for a different SAP system or database. Make sure that the installation media are still available on the installation host. For more information, see Preparing the Installation Media [page 54].
RECOMMENDATION

3.

Make installation media locally available. For example, if you use Network File System (NFS), reading from media mounted with NFS might fail. Restart the installer from the directory to which you unpacked the SWPM10SP<support package number>_<version number>.SAR file by executing the following command:
/<path to unpack directory>/sapinst

4.

5.

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. In the What do you want to do? screen, decide between the following alternatives and continue with Next:
Behavior

Alternative

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 installationspecific files to a backup directory. Afterwards, you can no longer continue the old installation option. 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

74/132

CUSTOMER

2013-07-15

5 5.5

Installation Additional Information About the Installer Behavior NOTE

Alternative

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

Continue with the old option

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. The installer continues the interrupted installation from the point of failure.

5.5.2 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 root 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 the sapinst executable from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524. Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809.
Prerequisites

([ŠíŠ The remote host meets the prerequisites for starting the installer [page 66]. ([ŠíŠ 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 executable on the remote host and the sapinstgui executable on the local host have exactly the same version. You can check this by using the option –sfxver as described in the procedure below and in the procedure in Starting the Installer GUI Separately [page 76]. ([ŠíŠ 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.

2013-07-15

CUSTOMER

75/132

5 5.5

Installation Additional Information About the Installer

Procedure

1.

Log on to your remote host as user root.
CAUTION

2.

Make sure that the root user has not set any environment variables for a different SAP system or database. Make the installation media available on the remote host.
RECOMMENDATION

3.

Make installation media locally available. For example, reading from media mounted with Network File System (NFS) might fail. Check the version of the sapinst executable by entering the following command:
./sapinst –sfxver

4.

The version of the sapinst executable must be exactly the same as the version of the sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 76]). Start the installer from the directory to which you unpacked the SWPM10SP<support package number>_<version number>.SAR file by executing the following command: /<path to unpack
directory>/sapinst -nogui NOTE

If you need to specify another operating system user for authentication purposes, enter the following command:
./sapinst -nogui SAPINST_REMOTE_ACCESS_USER=<specified OS user>

The installer now starts and waits for the connection to the installer GUI. You see the following at the command prompt:
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 76].

5.5.3 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: ËÊS·ÈH You closed the installer GUI using File Exit from the installer menu while the installer is still running. ËÊS·ÈH 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 75]. ËÊS·ÈH You want to run the installer in accessibility mode. In this case, you have to start the installer GUI separately on a Windows host as described below with the additional command line parameter – accessible.

76/132

CUSTOMER

2013-07-15

5 5.5

Installation Additional Information About the Installer

For more information, see Running the Installer in Accessibility Mode [page 79].
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 66]. %Ò»Åô Make sure that the sapinst executable on the remote host and the sapinstgui executable on the local host have exactly the same version. You can check this by using the option –sfxver as described in the procedure below and in the procedure in Performing a Remote Installation [page 75].
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 [page 73]. 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. For more information, see Preparing the Installation Media [page 54].
NOTE

2.

If you want to start the installer GUI on a Windows operating system that is able to run 32bit programs, you can use the SWPM10SP<support package number>_<version number>.SAR file for Windows I386. Start the installer GUI by executing <Drive>:\<path to unpack directory>\sapinstgui.exe with the appropriate command line parameters: %Ò»Åô 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 –sfxver

2.

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 75]). 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:

2013-07-15

CUSTOMER

77/132

5 5.5

Installation Additional Information About the Installer

1.

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 -port <port_number_gui_server_to_gui_client>

2.

– where <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 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 <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). 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. For more information, see Preparing the Installation Media [page 54].
NOTE

2.

If you want to start the installer GUI on a Linux 32-bit operating system, make the SWPM10SP<support package number>_<version number>.SAR file for Linux I386 available. Start the installer by executing the following command: /<path to unpack directory>/ sapinstgui using the appropriate command line parameters: ಇ¸ð 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 –sfxver

2.

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 75]). Start the installer GUI by entering the following command:
/<path to unpack directory>/sapinstgui -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: 1. If you are performing a local installation with the installer and the installer GUI running on the same host, execute the following command:

78/132

CUSTOMER

2013-07-15

5 5.5

Installation Additional Information About the Installer /<path to unpack directory>/sapinstgui -port <port_number_gui_server_to_gui>

2.

– where <port_number_gui_server_to_gui> is the port the GUI server uses to communicate with the GUI client (21212 by default). 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>

– where <remote_host> is the name of the remote host, and <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.5.4 Running the Installer in Accessibility Mode
You can also run the installer in accessibility mode. The following features are available: oCÁÈ Keyboard access: This feature is available for all operating systems. oCÁÈ High-contrast color: This feature is derived from the Windows display properties. Therefore, to enable this feature, you must perform a remote installation with the installer GUI running on a Windows host. oCÁÈ Custom font setting: This feature is derived from the Windows display properties. Therefore, to enable this feature, you must perform a remote installation with the installer GUI running on a Windows host.
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 installer GUI.
NOTE

The following procedure applies for Windows Server 2008 and might be different when using another Windows operating system. 1. 2. 3. Right click on your Windows desktop and choose Personalize. Choose Adjust font size (DPI) and choose Larger scale (120 DPI). To define other font size schemes, choose Custom DPI. In the right-hand pane, select Window Color and Appearance. Select a color scheme from the Color scheme dropdown box.

2013-07-15

CUSTOMER

79/132

5 5.5

Installation Additional Information About the Installer

To define your own color schemes, choose Advanced.
Running the Installer in Accessibility Mode

You perform a remote installation as follows: 1. Start the installer on the remote host by executing the following command from the command line as described in Performing a Remote Installation [page 75]:
./sapinst –nogui

2.

Start the installer GUI on a local Windows host by executing the following command from the command line as described in Starting the Installer GUI Separately [page 76]:
sapinstgui.exe -accessible –host <remote_host> -port <port_number_gui_server_to_gui_client>

5.5.5 Entries in the Services File Created by the Installer
After the installation has completed, the installer has created the following entries in /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

ôüSYL

<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 [...] sapgw98 = 3398/tcp sapgw99 = 3399/tcp

ôüSYL If there is more than one entry for the same port number, this is not an error.

5.5.6 Troubleshooting with the Installer
This section tells you how to proceed when errors occur during the installation with the installer. If an error occurs, the installer: ôüSYL Stops the installation

80/132

CUSTOMER

2013-07-15

5 5.6

Installation Oracle Database 11g Software Installation

hü8à Displays a dialog informing you about the error
Procedure

1. 2. 3.

4.

5.

Check SAP Note 1548438 for known installer issues. To view the log file, choose View Logs. If an error occurs during the dialog or processing phase, do one of the following: hü8à Try to solve the problem. hü8à Abort the installation with Exit. For more information, see Interrupted Installation [page 73]. hü8à Continue the installation by choosing Retry. Check the log and trace files of the GUI server and the installer GUI in the directory <user_home>/.sdtgui/ for errors. hü8à If GUI server or the installer GUI do not start, check the file sdtstart.err in the current <user_home> directory. hü8à If the installer GUI aborts during the installation without an error message, restart the installer GUI as described in Starting the Installer GUI Separately [page 76]. hü8à If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote Access of the installer GUI on Windows Workstations and you experience display problems such as missing repaints or refreshes, contact your X Server vendor. The vendor can give you information about whether this X Server supports Java Swing-based GUIs and also tell you about further requirements and restrictions. See also SAP Note 1170809. If you cannot resolve the problem, create a customer message using component BC-INS. For more information about using subcomponents of BC-INS, see SAP Note 1669327.

5.6 Oracle Database 11g Software Installation
The installer prompts you to install the Oracle database. Proceed as follows to install the Oracle 11 database software:
Process Flow

1. 2. 3. 4.

You update the Oracle installation scripts [page 81]. You perform steps for the AIX operating system [page 82]. You run the Oracle Universal Installer [page 83]. You install the required SAP bundle patch [page 85].

5.6.1 Updating the Oracle Installation Scripts
If a newer version is available, we recommend that you update the Oracle Installation scripts, which are attached to SAP Note 1524205. From there you can download the relevant package for your release.

2013-07-15

CUSTOMER

81/132

5 5.6

Installation Oracle Database 11g Software Installation

After you have extracted the Oracle software to the staging area, you need to update the installation scripts.
Prerequisites

The SAP-specific installation scripts RUNINSTALLER, RUNINSTALLER_CHECK, and 11ginstall.sh are located in directory SAP in the Oracle database software stage: Ù¹œ ÛÅ
RUNINSTALLER

This script installs the software with the following command:
./RUNINSTALLER

For help, enter:
./RUNINSTALLER -help

Ù¹œ ÛÅ

RUNINSTALLER_CHECK

This script performs product-specific prerequisite checks with the following command:
./RUNINSTALLER_CHECK

Ù¹œ ÛÅ

11ginstall.sh

This is the main script behind RUNINSTALLER and RUNINSTALLER_CHECK. This script supports installation in response file mode (interactive) and silent mode, generates the response file, and starts the Oracle installer.
Procedure
Updating the Installation Scripts

1.

2. 3. 4. 5.

Download the file 11ginstall_<release>_<patch_level>_complete.zip, which is attached to SAP Note 1524205. The zip file contains the current version of the installation scripts. Copy the file to the database directory in the Oracle software stage directory:
$ cp 11ginstall-<release>-<patch-level>-complete.zip /oracle/stage/112_64/database

Go to this directory:
$ cd /oracle/stage/112_64/database

Rename the existing SAP directory as follows so that you have a saved copy of the previous version:
mv SAP SAP.old

Extract the zip file:
$ unzip 11ginstall-<release>-<patch-level>-complete.zip

5.6.2 Performing Pre-Installation Steps for the AIX Operating System
To install the Oracle database software on the AIX operating system, you need to run the rootpre.sh script to adapt the AIX kernel and also execute a command as the root user.

82/132

CUSTOMER

2013-07-15

5 5.6

Installation Oracle Database 11g Software Installation

Prerequisites

If several Oracle instances run on one computer, you must shut these down before adapting the kernel.
Procedure

Run the rootpre.sh script as follows: 1. Log on to the system with user ora<dbsid> if you are not already logged on. 2. Change to the directory /oracle/stage/112_64/database using the following command:
cd /oracle/stage/112_64/database

3. 4. 5.

Make sure that the user root is assigned the environment of ora<dbsid>:
su root

Call the script rootpre.sh:
./rootpre.sh

Log off with the user root:
exit

5.6.3 Installing the Oracle Database Software
Starting with the first patch set for Oracle Database 11g Release 2 (11.2.0.2), Oracle Database patch sets are full installations of the Oracle database software. You only need to install the current Oracle database patch set. For more information about the current patch set, see SAP note 1431799. For more information about how to install Oracle database 11.2 software, see SAP note 1524205.
CAUTION

Before starting to install the Oracle software, make sure that you have updated the installation scripts as described in Updating the Oracle Installation Scripts [page 81].
Prerequisites

A graphical user interface (GUI), for example X11, is required for the Oracle database software installation with runInstaller. For more information, see the documentation of your operating system.
Procedure

1.

2.

Log on as user ora<dbsid> or oracle (Oracle software owner). Since you are already logged on as user root, you can switch to user ora<dbsid> by entering the following command: su – ora<dbsid>. Make sure that umask is set to 022 by entering the following command:
umask 022

2013-07-15

CUSTOMER

83/132

5 5.6

Installation Oracle Database 11g Software Installation

3.

Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where <host_name> is the host on which you want to display the GUI of the Oracle Universal Installer (OUI).
Shell Used Command
DISPLAY=<host_name>:0.0 export DISPLAY

Bourne shell (sh) C shell (csh) Korn shell (ksh)

setenv DISPLAY <host_name>:0.0 export DISPLAY=<host_name>:0.0

4.

~â1¸ÊÕ 11.2.0.2: ~â1¸ÊÕ 11.2.0.3: Start the OUI with the user ora<dbsid> by entering the following command:
cd /oracle/stage/112_64/database/SAP ./RUNINSTALLER

5.

Respond to the OUI as follows:
Prompt or Condition Action

Configure Security Updates

Select Installation Option Grid Installation Options Select Product Language Select Database Edition Specify Installation Location

Privileged OS Groups

Perform Prerequisite Checks

Do not select the checkbox. The runInstaller issues a warning. Choose OK and then Next. Confirm the default selections by choosing Next. Confirm the default selection Single Instance Installation and then choose Next. Confirm the default option English and then choose Next. Confirm the default option Enterprise Edition and then choose Next. This screen displays the value for ORACLE_BASE which is set in the environment. It also displays the value for ORACLE_HOME, which should be /oracle/DBSID/ <release>. See SAP Note 1521371 to set ORACLE_BASE for your configuration. Select this option and then Next. This screen displays the operating system groups for the DBA and the operator. Normally, these are dba and oper. This screen checks if all the required system prerequisites for installation of the database software have been met. If some of the checks are displayed as Failed, you can fix these problems (either by installing the missing patches or configuring the kernel parameters) and run the check again by choosing Check Again.

84/132

CUSTOMER

2013-07-15

5 5.6

Installation Oracle Database 11g Software Installation Prompt or Condition Action RECOMMENDATION

Summary Finish

We strongly recommend you to make sure that there are no failed checks before starting the software installation. Review the information displayed on this screen and choose Finish. Finish the software installation by executing the root.sh script as the root user from another session.

6.

To exit the OUI, choose Exit and confirm the dialog box that appears.

Result

The patch set software is now installed in the installation Oracle home. This is referred to – for example, in SAP Notes – as <IHRDBMS>.

5.6.4 Installing the Required SAP Bundle Patch
After the Oracle database software installation, you need to install the required SAP bundle patch, using the Oracle tool MOPatch.
NOTE

You must install the SAP bundle patch using the Oracle tool MOPatch, which you can find at SAP Note 1027012. You only need to install the latest SAP bundle patch because these patches are cumulative. After installing the SAP bundle patch, you do not need to install any critical patch updates (CPUs). The SAP bundle patch also delivers a set of upgrade scripts that automate most of the pre-upgrade and post-upgrade tasks. For more information, see SAP Note 1431793.
Prerequisites

Check SAP Note 1431800 to find a cross-reference to the current SAP Note with the list of required patches to be installed.
Procedure

1. 2.

Log on at the operating system level as the ora<dbsid> user. Set ORACLE_HOME to the new installation Oracle Home <IHRDBMS>.
EXAMPLE setenv ORACLE_HOME /oracle/<DBSID>/11203

3. 4.

Install the SAP bundle patch according to the instructions in the SAP bundle patch README file.
NOTE

This step is only required for the update to Oracle 11.2.0.2.

2013-07-15

CUSTOMER

85/132

5 5.6

Installation Oracle Database 11g Software Installation

After the software installation has finished, create a symbolic link in $ORACLE_HOME/lib as follows:
cd $ORACLE_HOME/lib ln –s libnnz11.so libnnz10.so

For more information, see SAP Note 1449619.

86/132

CUSTOMER

2013-07-15

6 6.1

Post-Installation Post-Installation Checklist

6 Post-Installation

6.1 Post-Installation Checklist
This section includes the post-installation steps that you have to perform for the following: KmmÌł Standard, distributed, or high-availability system KmmÌł Additional application server instance Detailed information about the steps is available in the relevant chapter.
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. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. You perform post-installation steps for the operating system [page 88]. You check whether you can log on to the application server [page 88]. You perform the consistency check [page 90]. You provide access to the NetWeaver Administrator [page 90]. You install the SAP license [page 91]. You set up the licenses for high availability [page 91]. You configure the remote connection to SAP support [page 92]. You apply the latest kernel and Support Packages [page 92]. You install the SAP Online Documentation [page 93]. You configure the Transport Management System [page 93]. You ensure user security [page 94]. On the database instance host, you perform Oracle-specific post-installation steps [page 95]. You perform a full installation backup [page 97]. You check the Master Guide for your SAP NetWeaver application for further implementation and configuration steps.
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.
Additional Application Server Instance

1.

You perform post-installation steps for the operating system [page 88].

2013-07-15

CUSTOMER

87/132

6 6.2

Post-Installation Performing Post-Installation Steps for the Operating System

2. 3.

You check whether you can log on to the additional application server instance [page 88]. You ensure user security [page 94].

6.2 Performing Post-Installation Steps for the Operating System
You have to perform the following post-installation steps for the operating system.
Procedure

1.

2.

You check and if necessary modify the settings for the operating system users for your SAP system if they were created by the installer. For more information, see Creating Operating System Users and Groups [page 40]. You set the required permissions for sapstartsrv and sapuxuserchk in the /<sapmnt>/<SAPSID>/ exe, and /usr/sap/<SAPSID>/SYS/exe, and /usr/sap/<SAPSID>/<Instance_Name>/exe directories as described in SAP Note 927637. See also Starting and Stopping SAP System Instances Using the SAP Management Console [page 111].

6.3 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* DDIC

000, 001, 066 000, 001

Java User User User Name Storage: ABAP System
J2EE_ADMIN (default) or the name you gave this user during the

Administrator

installation process. Prerequisites

]8B{¸ý The SAP system is up and running. ]8B{¸ý 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:

88/132

CUSTOMER

2013-07-15

6 6.3

Post-Installation Logging On to the Application Server

Õ‡i¬à‚ SAP GUI for Windows: Õ‡i¬àþ Windows Server 2012: 1. Press Windows + Q , and enter SAP Logon in the Search field. 2. Choose SAP Logon. Õ‡i¬àþ Windows Server 2003 and Windows Server 2008 (R2): Choose Start All Programs SAP Front End SAP Logon . Õ‡i¬à‚ SAP GUI for Java: Õ‡i¬àþ Windows Server 2012: 1. Press Press Windows + Q , and enter SAP GUI for Java <release> 2. Choose SAP GUI for Java <release>. Õ‡i¬àþ Windows Server 2003 and Windows Server 2008 (R2): Choose Start All Programs SAP Clients SAP GUI for Java<Release> . The SAP Logon appears.
NOTE

2. 3.

You can alternatively enter the command guilogon in the SAP GUI installation directory to start SAP GUI for Java. Create a logon entry for the newly installed system in the SAP Logon. For more information about creating new logon entries, press F1 . When you have created the entry, log on as user SAP* or DDIC.

Logging On to the Java Application Server

You access AS Java with a URL using a Web browser from your client machines. To log on to the Java application server, proceed as follows: 1. Start a Web browser and enter the following URL:
http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00 NOTE

You must always enter a two-digit number for <Instance_Number>. For example, do not enter 1 but instead enter 01.
EXAMPLE

If you installed SAP NetWeaver Application Server Java on host saphost06 and the instance number of your SAP NetWeaver Application Server Java is 04, enter the following URL:
http://saphost06:50400

2.

The start page of the SAP NetWeaver Application Server Java appears in the Web browser. Log on by pressing the link of any of the provided applications, for example SAP NetWeaver Administrator or System Information.

2013-07-15

CUSTOMER

89/132

6 6.4

Post-Installation Performing the Consistency Check

6.4 Performing the 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. The following checks are performed: ^˙Ë! Completeness of installation ^˙Ë! Version compatibility between the SAP release and the operating system The initial consistency check determines whether: ^˙ËN The release number in the SAP kernel matches the release number defined in the database system ^˙ËN The character set specified in the SAP kernel matches the character set specified in the database system ^˙ËN 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
Prerequisites

^˙Ë! If the installation finished successfully, your SAP system should be up and running. Otherwise start it as described in Starting and Stopping SAP System Instances [page 111]. ^˙Ë! You have logged on to the SAP system [page 88].
Procedure

1.

2.

Perform a system check: Call transaction SICK. You should see the entry SAP Perform a database check:

System Check | no errors reported

In the DBA Cockpit, check for missing tables or indexes by choosing Diagnostics →Missing Tables and Indexes.

6.5 Providing Access to the NetWeaver Administrator
Due to security restrictions, the NetWeaver Administrator can only be accessed locally via http:// <hostname_of_Java EE_Engine_Server>:5<Instance_Number>00/nwa after the installation has finished.

90/132

CUSTOMER

2013-07-15

6 6.6

Post-Installation Installing the SAP License

Procedure

Allow access to administration requests for the required network segments as described in SAP Note 1451753.

6.6 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 [page 10] at: $_Ù~ SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1: Administrator's Guide Configuration of SAP NetWeaver General Configuration Tasks License Configuration $_Ù~ SAP NetWeaver 7.3 and higher: Solution Life Cycle Management SAP Licenses
More Information

For more information about SAP license keys and how to obtain them, see http:// service.sap.com/licensekey.

6.7 High Availability: Setting Up Licenses
SAP has implemented a license mechanism for switchover solutions and clustered environments. Your customer key is calculated on the basis of local information on the message server host. This is the host machine where the ABAP central services instance (ASCS instance) runs. To be able to perform a switchover, the temporary license that is installed automatically with the ASCS instance is not sufficient. You first need to install a permanent license, which is determined by the hardware environment of the message server. Since SAP's high-availability (HA) solution stipulates two or more cluster nodes (host machines) where the message server is enabled to run, you have to order as many license keys [page 91] as you have cluster nodes. When we receive confirmation from your vendor that you are implementing a switchover environment, we provide the required license keys for your system, one key for each machine.
Prerequisites

The SAP system is up and running.

2013-07-15

CUSTOMER

91/132

6 6.8

Post-Installation Configuring the Remote Connection to SAP Support

Procedure

1. 2.

3.

To find the hardware ID of the primary host, log on to any application server instance of the SAP system and call transaction SLICENSE. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster and repeat the previous step. Repeat this for all remaining nodes in the cluster. To obtain the two license keys, enter the hardware IDs for each cluster node, where message server is enabled to run:
http://service.sap.com/licensekey

4. 5.

To import the files containing the two licenses, log on to any application server instance of the SAP system and call transaction SLICENSE. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster and repeat the previous step. Repeat this for all remaining nodes in the cluster.

Result

The license is no longer a problem during switchover. This means you do not need to call saplicense in your switchover scripts.

6.8 Configuring the Remote Connection to SAP Support
SAP offers its customers access to support and a number of remote services such as the EarlyWatch Service or the 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.9 Applying the Latest Kernel
We strongly recommend that you replace the installed kernel with the latest kernel from SAP Service Marketplace.
Procedure

1. 2. 3. 4. 5.

Log on as user <SAP>ADM to the hosts of the SAP system instances to be updated. Download the latest kernel for your operating system and database platform as described in SAP Note 19466. Back up the kernel directory that is specified by the profile parameter DIR_CT_RUN. Extract the SAR files of the kernel Support Packages of the target SP level to a temporary directory using the SAPCAR tool. Copy or move the extracted programs from the temporary directory to the local kernel directory.

92/132

CUSTOMER

2013-07-15

6 6.10

Post-Installation Installing the SAP Online Documentation

6.

Adjust the ownership and permissions of the kernel binaries by entering the following command sequence (Execute the saproot.sh script that is located in the kernel directory):
su - root cd <kernel directory> ./saproot.sh <SAPSID> exit

6.10 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.
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 media, delivered as part of the installation package.

6.11 Configuring the Transport Management System
You have to perform some steps to be able to use the Transport Management System.
Procedure

1.

2.

Perform post-installation steps for the transport organizer: 1. Call transaction SE06. 2. Select Standard Installation. 3. Choose Perform Post-Installation Actions. Call transaction STMS in the ABAP system to configure the domain controller in the Transport Management System (TMS). For more information, see the SAP Library [page 10] at: ë# ‚/ SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1: Function-Oriented View ABAP Technology / Application Server ABAP Administration Tools for AS ABAP Transport and Change Management Change and Transport System Transport Management System (BC-CTS-TMS) Configuring TMS ë# ‚/ SAP NetWeaver 7.3 and higher: Solution Life Cycle Management Software Logistics Change and Transport System Change and Transport System – Overview Basics of the Change and Transport System Transport Management System – Concept

2013-07-15

CUSTOMER

93/132

6 6.12

Post-Installation Ensuring User Security

6.12 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 the following users: C´“T†ÿ Operating system users C´“T†ÿ SAP system users C´“T†ÿ Users for SAP NetWeaver Process Integration (PI) During the installation, the installer by default assigned the master password to all users created during the installation unless you specified other passwords.
RECOMMENDATION

In all cases, the 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.
CAUTION

Make sure that you perform this procedure before the newly installed SAP system goes into production.
Procedure

For the users listed below, take the precautions described in the relevant SAP security guide, which you can find on SAP Service Marketplace at http://service.sap.com/securityguide:
Operating System Users

After the installation, operating system users for SAP system, database, and SAP Host Agent are available as listed in the following table:
Operating System and Database Users User User Name
<sapsid>adm <dasid>adm

Comment

Operating system user

sapadm ora<dbsid>

Oracle database user

SAP<SCHEMA_ID>

SYSTEM SYS OUTLN DBSNMP

SAP system administrator Administrator for the diagnostics agent User for central monitoring services Oracle database administrator (that is, the owner of the database files) Oracle database owner (that is, the owner of the database tables) Oracle standard database user Oracle standard database user Oracle standard database user Oracle standard database user

94/132

CUSTOMER

2013-07-15

6 6.13

Post-Installation Performing Oracle-Specific Post-Installation Steps

SAP Host Agent User User User Name
sapadm

Comment

Operating system user

SAP system administrator You 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 and Java system users are available. The following table shows these users together with recommendations on how you can ensure the security of these users;
SAP System Users User User Name
SAP*

Comment

SAP system user

Administrator

User exists in at least SAP system clients 000, 001, and 066. DDIC User exists in at least SAP system clients 000 and 001. EARLYWATCH User exists in at least SAP system client 066. The name that you gave this user during This user exists in at least clients 000 and the installation or the default name 001 of the ABAP system and in the User J2EE_ADMIN (see Basic SAP System Installation Management Engine (UME) of the Java system. It has administrative Parameters [page 25]) permissions for user management. This user’s password is stored in secure storage. Therefore, whenever you change the administrator’s password, you must also change the password in secure storage.
RECOMMENDATION

Guest

Communication user for Application Server Java

We recommend that you use strong password and auditing policies for this user. The name that you gave this user during This user exists in at least clients 000 and the installation or the default name 001 of the ABAP system and in the User J2EE_GUEST (see Basic SAP System Installation Management Engine (UME) of the Java system. It is used for anonymous access. Parameters [page 25]) The name that you gave this user during This user exists in at least clients 000 and the installation or the default name 001 of the ABAP system and in the User SAPJSF (see Basic SAP System Installation Management Engine (UME) of the Java system. It is used for a remote function Parameters [page 25]) call (RFC) between the ABAP system and the Java system.

6.13 Performing Oracle-Specific Post-Installation Steps
You have to perform the following Oracle-specific post-installation steps:

2013-07-15

CUSTOMER

95/132

6 6.13

Post-Installation Performing Oracle-Specific Post-Installation Steps

Procedure
Security Setup for the Oracle Listener

If the Oracle security setup defined by the standard installation is not restrictive enough for your purposes, see SAP Note 186119 to configure the Oracle listener to accept only connections from specific hosts.
Checking the Recommended Oracle Database Parameters

When installing the Oracle database, a standard database parameter set is used. To take into account the size and configuration of your SAP system, and to enable new Oracle features, check and apply the parameter settings as described in SAP Note 1431798. You can find an automated script in SAP Note 1171650 to help you check whether your SAP system complies with the database parameter recommendations at any given point in time.
Configuring Database User Profiles

If the SAP-specific database user profile SAPUPROF is not yet installed in the database, configure it as described in SAP Note 1519872.
Updating Oracle Optimizer Statistics

To update the Oracle optimizer statistics, perform the following: 1. Execute the following commands as the ora<dbsid> user:
brconnect -u / -c -f stats -t system_stats; brconnect -u / -c -f stats -t oradict_stats;

2.

Execute the following commands with SQLPlus:
SQL> exec dbms_scheduler.disable('GATHER_STATS_JOB'); SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB'); SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');

For Oracle 11g, also execute the following command:
SQL> exec DBMS_AUTO_TASK_ADMIN.DISABLE

For more information, see SAP Note 974781.
Checking the Version of the Oracle Instant Client

If necessary, install the most up-to-date version of the Oracle Instant Client, as described in SAP Note 819829.
Configuring and Administering the Oracle Database

You have to configure your Oracle database before you start operating it with the SAP system. For more information about Oracle database consfiguration and administration, see the SAP Library [page 10] at: «Í•ôÜù SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1: Function-Oriented View Database Administration Database Administration for Oracle

96/132

CUSTOMER

2013-07-15

6 6.14

Post-Installation Performing a Full Installation Backup

F§
To¿ SAP NetWeaver 7.3 and higher: Database Administration Database Administration for Oracle .

6.14 Performing a Full Installation Backup
You must perform a full offline backup after the configuration of your SAP system. If required, you can also perform a full offline backup after the installation (recommended). In addition, we recommend you to regularly back up your database.
CAUTION

Make sure that you fully back up your database so that you can recover it later if necessary. You need to back up the following directories and files: F§
To¿ All SAP-specific directories: F§
ToÐ /usr/sap/<SAPSID> F§
ToÐ /usr/sap/trans F§
ToÐ <sapmnt>/<SAPSID> F§
ToÐ Home directory of the user <sapsid>adm F§
To¿ All database-specific directories F§
To¿ The root file system This saves the structure of the system and all configuration files, such as file system size, logical volume manager configuration, and database configuration data.
NOTE

This list is only valid for a standard installation.
Prerequisites

You have logged on [page 88] as user <sapsid>adm and stopped the SAP system and database [page 111].
Procedure

This procedure works on all hardware platforms. For more information about operating system-specific backup procedures, see your operating system documentation.
Backing Up the Installation

1. 2.

Log on as user root. Manually create a compressed tar archive that contains all installed files: F§
To¿ Saving to tape:
tar —cf — <file_system> | compress —c > <tape_device>

F§
To¿ Saving to the file system:
tar —cf — <file_system> | compress —c > ARCHIVENAME.tar.Z

2013-07-15

CUSTOMER

97/132

6 6.14

Post-Installation Performing a Full Installation Backup

Restoring Your Backup

If required, you can restore the data that you previously backed up.
CAUTION

Check for modifications in the existing parameter files before you overwrite them when restoring the backup. 1. 2. 3. Log on as user root. Go to the location in your file system where you want to restore the backup image. Restore the data with the following commands: ÁÔ
Iœ From tape:
cat <tape_device> | compress —cd | tar —xf —

ÁÔ
Iœ From the file system:
cat ARCHIVENAME.tar.Z | compress —cd | tar —xf — Performing a Full Database Backup

1. 2.

Configure your third-party backup tool, if used. Perform a full database backup (preferably offline). If you use BR*TOOLS for the backup, refer to BR*Tools for Oracle DBA in the documentation SAP Database Guide: Oracle (BC-DB-ORA-DBA), available in the SAP Library [page 10] at: ÁÔ
Iœ SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1: Function-Oriented View Database Administration Database Administration for Oracle ÁÔ
Iœ SAP NetWeaver 7.3 and higher: Database Administration Database Administration for Oracle .

98/132

CUSTOMER

2013-07-15

7 7.1

Additional Information Integration of LDAP Directory Services

7 Additional Information

Here you can find additional information about the installation of your SAP system, including information about how to delete an SAP system: ‡ı~œ%ç Integration of LDAP Directory Services [page 99] ‡ı~œ%ç Installing a Database Instance on Oracle Automatic Storage Management or Oracle Real Application Cluster [page 103] ‡ı~œ%ç Installing Multiple Components in One Database (MCOD) [page 103] ‡ı~œ%ç Creating a User for LDAP Directory Access [page 105] ‡ı~œ%ç Heterogeneous SAP System Installation [page 105] ‡ı~œ%ç Splitting Off a Central Services Instance for ABAP from an Existing Primary Application Server Instance [page 106] ‡ı~œ%ç Installing the SAP Host Agent Separately [page 108] ‡ı~œ%ç Starting and Stopping SAP System Instances [page 111] ‡ı~œ%ç Deleting an SAP System or Single Instances [page 119] ‡ı~œ%ç Deleting the Oracle Database Software [page 122]

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

2013-07-15

CUSTOMER

99/132

7 7.1

Additional Information Integration of LDAP Directory Services

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 [page 10]: ⁄w
Á SAP NetWeaver Process Integration 7.1 Including Enhancement Package 1: Security Identity Management Identity Management of the Application Server ABAP Configuration of Identity Management Directory Services LDAP Connector ⁄w
Á SAP NetWeaver Process Integration 7.1: Security Identity Management Identity Management of the Application Server ABAP Configuration of User and Role Administration Directory Services LDAP Connector ⁄w
Á SAP NetWeaver 7.3 and higher: Security Identity Management User and Role Administration of Application Server ABAP Configuration of User and Role Administration Directory Services LDAP Connector
Prerequisites

⁄w
Á You 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. ⁄w
Á Make sure that you have the IBM Tivoli Directory Server client packages installed.
Features

In the SAP environment, you can exploit the information stored in an Active Directory or generic LDAP directory by using: ⁄w
Á SAP Logon ⁄w
Á The SAP Microsoft Management Console (SAP MMC) ⁄w
Á The SAP Management Console (SAP MC) 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:
http://scn.sap.com/docs/DOC-14384

For more information about the SAP MC and about how to configure it to access LDAP Directories, see the documentation SAP Management Console in the SAP Library [page 10]:

100/132

CUSTOMER

2013-07-15

7 7.1

Additional Information Integration of LDAP Directory Services

×-*êþ SAP NetWeaver Process Integration 7.1 Including Enhancement Package 1: Function-Oriented View Application Server Infrastructure SAP Management Console ×-*êþ SAP NetWeaver Process Integration 7.1: Function-Oriented View Application Server Infrastructure SAP Management Console ×-*êþ SAP NetWeaver 7.3 and higher: Solution Life Cycle Management SAP Management Console
SAP Logon

Instead of using a fixed list of systems and message servers, you can configure SAP Logon in the sapmsg.ini configuration file to find SAP systems and their message servers from the directory. If you 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.

2013-07-15

CUSTOMER

101/132

7 7.1

Additional Information Integration of LDAP Directory Services

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

The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central location. The SAP MC is automatically set up when you install an SAP system on any platform. If the SAP system has been prepared correctly, the SAP MC presents and analyzes system information that it gathers from various sources, including a generic LDAP Directory. Integrating a generic LDAP Directory as a source of information has advantages for the SAP MC. 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 MC.
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 on the Windows server on which you want to use Active Directory Services and choosing Generic Installation Options <Database> Preparations LDAP Registration Active Directory Configuration . For more information about running the installer on Windows, see documentation Installation Guide Р<your SAP product> on Windows: <Database>.

102/132

CUSTOMER

2013-07-15

7 7.2

Additional Information Installing a Database Instance on Oracle Automatic Storage Management or Oracle Real Application Cluster 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.
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 [page 66] once for your system and choose: Generic Installation Options <Database> Preparations 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.

7.2 Installing a Database Instance on Oracle Automatic Storage Management or Oracle Real Application Cluster
This section provides information on the installation of a database instance on an Oracle Automatic Storage Management (ASM) or Oracle Real Application Cluster (RAC).
Installing a Database Instance on Oracle Automatic Storage Management (ASM)

Proceed as described in SAP Note 1738053 and the document SAP Databases on Oracle Automatic Storage Management 11g, which is available at http://scn.sap.com/community/oracle.
Installing a Database Instance on Oracle Real Application Cluster (RAC)

Proceed as described in the document SAP on Oracle Real Application Clusters (RAC), which is available at http://scn.sap.com/community/oracle.

7.3 Installation of Multiple Components in One Database
You can install multiple SAP systems in a single database. This is called Multiple Components in One Database (MCOD). MCOD is available with all SAP components and all the major databases for the SAP system. No extra effort is required because the MCOD installation is fully integrated into the standard installation procedure. MCOD is not an additional installation option. Instead, it is an option of the database instance installation.

2013-07-15

CUSTOMER

103/132

7 7.3

Additional Information Installation of Multiple Components in One Database

With MCOD we distinguish two scenarios: E•Eîå The installation of an SAP system in a new database The system then creates new tablespaces and a new database schema. E•Eîå The installation of an additional SAP system in an existing database (MCOD) The system then automatically creates additional tablespaces in the existing database and a schema user in the existing database.
Prerequisites

E•Eîå For more information about MCOD and its availability on different platforms, see http:// scn.sap.com/docs/DOC-8559 . E•Eîå Since SAP does not support mixed solutions with MCOD, your SAP system must contain Unicode SAP instances only. E•Eîå Improved sizing required You can calculate the CPU usage for an MCOD database by adding up the CPU usage for each individual SAP system. You can do the same for memory resources and disk space. You can size multiple components in one database by sizing each individual component using the Quick Sizer tool and then adding the requirements together. For more information about the Quick Sizer, see http://service.sap.com/sizing.
Features

E•Eîå Reduced administration effort E•Eîå Consistent system landscape for backup, system copy, administration, and recovery E•Eîå Increased security and reduced database failure for multiple SAP systems due to monitoring and administration of only one database E•Eîå Independent upgrade In an MCOD landscape, you can upgrade a single component independently from the other components running in the same database, assuming that the upgraded component runs on the same database version. However, if you need to restore a backup, be aware that all other components are also affected.
NOTE

Special MCOD considerations and differences from the standard procedure are listed where relevant in the installation documentation.
Constraints

E•Eîå We strongly recommend that you test MCOD in a test or development system. We recommend that you run MCOD systems in the same context. We do not recommend that you mix test, development, and production systems in the same MCOD. E•Eîå In the event of database failure, all SAP systems running on the single database are affected.

104/132

CUSTOMER

2013-07-15

7 7.4

Additional Information Creating a User for LDAP Directory Access

Éš¡âÅF Automated support in an MCOD landscape for the following administrative tasks depends on your operating system and database: Éš¡âÅ) Copying a single component from an MCOD landscape to another database at database level. Éš¡âÅ) De-installing a single component from an MCOD landscape requires some additional steps. You can use a remote connection to SAP support to request help with these tasks. For more information, see http://service.sap.com/remoteconnection. Éš¡âÅF You cannot install a Unicode ABAP system with a non-Unicode ABAP system in one database. Éš¡âÅF For the second SAP system, you must use the same DBSID as for the first SAP system. Éš¡âÅF If you install a system into an existing database (MCOD), the SYSTEM tablespace must contain at least 400 MB of free space. If there is not enough space left, increase the size of this tablespace with BRSPACE or BRTOOLS. Éš¡âÅF If you decide to turn off archive log mode during the database load phase of the installation, you need to plan downtime for all MCOD systems sharing the database.

7.4 Creating a User for LDAP Directory Access
If you use LDAP directory services, you have to set up a user with a password on the host where the SAP system is running. This permits the SAP system to access and modify the LDAP directory. For more information, see Integration of LDAP Directory Services in the Windows installation guide for your SAP system solution and database.
Prerequisites

During the SAP instance installation you chose to configure the SAP system to integrate LDAP services.
Procedure

1. 2. 3.

Log on as user <sapsid>adm. Enter:
ldappasswd pf=<path_and_name_of_instance_profile>

Enter the required data.
EXAMPLE

The following is an example of an entry to create an LDAP Directory User:
CN=sapldap,CN=Users,DC=nt5,DC=sap-ag,DC=de

7.5 Heterogeneous SAP System Installation
This section provides information on the installation of an SAP system in a heterogeneous system landscape. “Heterogeneous system landscape” means that application servers run on different operating systems.

2013-07-15

CUSTOMER

105/132

7 7.6

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

Procedure

See SAP Note 1067221 for more information on: WÞÔÐHÄ Supported combinations of operating systems and database systems WÞÔÐHÄ How to install an application server on Windows in a heterogeneous (UNIX) SAP system environment WÞÔÐHÄ Heterogeneous SAP system landscapes with different UNIX operating systems

7.6 Splitting Off a Central Services Instance for ABAP from an Existing Primary Application Server Instance
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 the ABAP stack of an existing primary application server 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: WÞÔÐHÄ It was upgraded to an SAP system based on SAP NetWeaver 7.3 or higher WÞÔÐHÄ It does not yet have an ASCS instance
Before the Split

The ABAP stack of the primary application server instance includes: WÞÔÐHÄ ABAP dispatcher and work processes (dialog, batch, spool, enqueue, or update) WÞÔÐHÄ Gateway WÞÔÐHÄ Internet communication manager (ICM) WÞÔÐHÄ Java server processes WÞÔÐHÄ Internet graphics service (IGS) WÞÔÐHÄ ABAP message server
After the Split

The ABAP stack of the primary application server instance now includes: WÞÔÐHÄ ABAP dispatcher and work processes (dialog, batch, spool, or update) WÞÔÐHÄ Gateway WÞÔÐHÄ Internet communication manager (ICM) WÞÔÐHÄ Java server processes WÞÔÐHÄ Internet graphics service (IGS) The newly created central services instance for ABAP (ASCS instance) includes:

106/132

CUSTOMER

2013-07-15

7 7.6

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

MÚb¡ ABAP message server MÚb¡ ABAP standalone enqueue server The ABAP enqueue work process is now replaced with the ABAP standalone enqueue server.
The Effect of the Split

The following graphic provides an overview of the components contained in the primary application server instance before and after the split, along with the newly created ASCS instance:

MÚ—Zh —™=‚É›B#4ÏÎXõõ÷

Procedure

1.

2. 3. 4. 5. 6. 7.

Plan the basic parameters, as described in Basic SAP System Installation Parameters [page 25]: MÚb¡ Choose an instance number for the ASCS instance to be created. MÚb¡ Note that the message server port is not changed during the split. 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]s . Specify basic SAP system parameters [page 25] for the ASCS instance and the ERS instance to be created. Set up the required file systems [page 43] for the ASCS instance and the ERS instance to be created. Start the installer as described in Running the Installer [page 66]. On the Welcome screen, choose <SAP Product> <Database> Additional SAP System Instances Split Off ASCS Instance from Existing Primary Application Server Instance . Follow the instructions on the installer screens and enter the required parameters.

2013-07-15

CUSTOMER

107/132

7 7.7

Additional Information Installing the SAP Host Agent Separately 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. 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. Check settings for operating system users [page 88] if they were created by the installer. Check whether you can start and stop the SAP system [page 111] with the newly created ASCS instance and SCS instance. Check whether you can log on to the application server [page 88]. Ensure user security [page 94] for the operating system users of the newly created ASCS instance and ERS instance if they were created by the installer. If required, perform an installation backup [page 97].

8.

9. 10. 11. 12. 13.

7.7 Installing the SAP Host Agent Separately
This procedure tells you how to install an SAP Host Agent separately. The SAP Host Agent is automatically installed with every SAP system instance based on SAP NetWeaver 7.0 including EHP2 or higher (integrated installation). So if you have an SAP system or instance based on SAP NetWeaver 7.0 including EHP2 or higher on the host, you do not need to apply the procedure described in the section. This procedure is only for hosts with no SAP Host Agent running on them, due to the following reasons: ÚíÉ9Ł* There is no SAP system or instance on the host. ÚíÉ9Ł* The SAP system running on the host is based on SAP NetWeaver 7.0 including EHP1 or lower. ÚíÉ9Ł* You have upgraded your SAP system to SAP NetWeaver 7.0 including Enhancement Package 2 or higher and the upgraded system does not have yet a SAP Host Agent.

108/132

CUSTOMER

2013-07-15

7 7.7

Additional Information Installing the SAP Host Agent Separately

àùá¿7¨µãJTLQcÒJ¼x²1¶Õ
SAP Host Agent

The SAP Host Agent contains the following elements: àùáY&þ The control program saphostexec àùáY&þ The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode) àùáY&þ The sapacosprep executable of the Adaptive Computing Infrastructure àùáY&þ The operating system collector saposcol
NOTE

The installed programs are automatically started when the host is booted. The automatic start is ensured by the startup script sapinit, which starts the required executables.
Procedure

You have to perform the following steps on the host where you install the SAP Host Agent separately: 1. Check the hardware and software requirements on the installation host. The minimum requirements are as follows: àùáY&þ Hard Disk Space: 1 GB àùáY&þ RAM: 0.5 GB àùáY&þ Swap Space: 2 x RAM For more information, see hardware and software requirements [page 20]. 2. Make sure that the sapadm user is created. During the installation, the installer checks all required accounts (users, groups) and services on the local machine. The installer checks whether the required users and groups already exist. If not, it creates new users and groups as necessary.

2013-07-15

CUSTOMER

109/132

7 7.7

Additional Information Installing the SAP Host Agent Separately User and Groups of the SAP Host Agent User
sapadm

Primary Group
sapsys

Additional Group
sapinst

Comment

SAP Host Agent administrator
NOTE

If sapadm does not exist, it is created during the SAP Host Agent installation using /bin/false shell. Make sure that / bin/false can be used as a login shell. Add /bin/false to the list of valid login shells (attribute shells) in /
etc/security/ login.cfg.

Groups and Members of the SAP Host Agent User Groups
sapsys sapinst

Members
sapadm sapadm

3.

Set up the required file system for the SAP Host Agent:
Directories
/usr/sap/hostctrl

Description

Required Disk Space

Contains the following directories: 100 MB ÒÏê¡’× exe Contains the profile
host_profile

ÒÏê¡’×

work

Working directory of the SAP Host Agent

4.

5. 6.

For more information, see Setting up file systems and raw devices [page 43] Make sure that the unpacked Software provisioning manager 1.0 archive SWPM10SP<support package number>_<version number>.SAR and the medium for the UC kernel (folder K_U_<Version>_<OS>) are available on the installation host. For more information, see Preparing the Installation Media [page 54]. To install the SAP Host Agent, you start the installer [page 66] and choose Generic Installation Options <Database> Preparations SAP Host Agent on the Welcome screen of the installer. Check whether the installed services are available: 1. Log on as user sapadm.
NOTE

When the host is booted, the startup script sapinit automatically starts the required executables.

110/132

CUSTOMER

2013-07-15

7 7.8

Additional Information Starting and Stopping SAP System Instances

2.

Check whether the following services are available: ©¿Çž
™ The control program saphostexec ©¿Çž
™ The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)

More Information

For more information about the SAP Host Agent, see the SAP Library [page 10] at: ©¿Çž
™ SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1: Function-Oriented View Application Server ABAP Administration Tools for AS ABAP CCMS Infrastructure of the SAP NetWeaver Management Agents ©¿Çž
™ SAP NetWeaver 7.3 and higher: Solution Life Cycle Management SAP Microsoft Management Console: Windows

Monitoring in the

7.8 Starting and Stopping SAP System Instances
You can start or stop SAP system instances in one of the following ways: ©¿Çž
™ Using the SAP Management Console (SAP MC) [page 111] ©¿Çž
™ Using commands [page 115].

7.8.1 Starting and Stopping SAP System Instances Using the SAP Management Console
You can start and stop all SAP system and diagnostics agent instances using the SAP Management Console (MC) except the database instance. You have to start and stop the database instance as described in Starting and Stopping the SAP System Using startsap and stopsap [page 115].
NOTE

If your newly installed SAP system is part of a heterogeneous SAP system landscape comprising systems or instances on Windows platforms, you can also start and stop it from a Windows system or instance using the Microsoft Management Console (MMC). For more information about handling the MMC, see the SAP Library [page 10] at: ©¿Çž
™ SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1: Function-Oriented View Application Server Infrastructure SAP Microsoft Management Console: Windows ©¿Çž
™ SAP NetWeaver 7.3 and higher: Solution Life Cycle Management SAP Microsoft Management Console: Windows
Prerequisites

©¿Çž
™ Make sure that the host names defined in the DNS server match the names of the SAP system instance hosts. In particular, keep in mind that host names are case-sensitive. For example, if the

2013-07-15

CUSTOMER

111/132

7 7.8

Additional Information Starting and Stopping SAP System Instances

names of the SAP system instance hosts are in upper case, but the same host names are defined in the DNS server in lower case, starting and stopping the system does not work. ýŸ⁄·0¤ Make sure that the host on which you start SAP MC meets the following requirements: ýŸ⁄·0Ë At least Java Runtime Environment (JRE) 5.0 is installed. ýŸ⁄·0Ë The browser supports Java. ýŸ⁄·0Ë The browser's Java plug-in is installed and activated. ýŸ⁄·0Ë You have set the required permissions for sapstartsrv and sapuxuserchk in the /<sapmnt>/ <SAPSID>/exe, and /usr/sap/<SAPSID>/SYS/exe, and /usr/sap/<SAPSID>/ <Instance_Name>/exe directories as described in SAP Note 927637. See also Performing Post-Installation Steps for the Operating System [page 88]. ýŸ⁄·0¤ You have logged on to the host as user <sapsid>adm.
Procedure
Starting the Web-Based SAP Management Console

1.

Start a Web browser and enter the following URL:
http://<hostname>:5<instance_number>13 EXAMPLE

If the instance number is 53and the host name is saphost06, you enter the following URL:
http://saphost06:55313

This starts the SAP MC Java applet.
NOTE

2.

If your browser displays a security warning message, choose the option that indicates that you trust the applet. Choose Start. The SAP Management Console appears.
NOTE

When you start the SAP MC for the first time for a newly installed SAP system, you have to register your system as described in Registering Systems and Instances below. After you have done this, the instances installed on the host you have connected to are already present in the SAP Management Console when you next start the SAP MC. By default, the instances installed on the host you have connected to are already present in the SAP Management Console. If you want to change the configuration to display systems and instances on other hosts, see Registering Systems and Instances below.

112/132

CUSTOMER

2013-07-15

7 7.8

Additional Information Starting and Stopping SAP System Instances

Starting and Stopping Systems and Instances Starting an SAP System or Instance

1. 2. 3. 4.

In the navigation pane, open the tree structure and navigate to the system node that you want to start. Select the system or instance and then, from the context menu, choose Start. In the Start SAP System(s) dialog box, choose the required options. Choose OK. The SAP MC starts the specified system or system instances.
NOTE

The system might prompt you for the SAP system administrator credentials. To complete the operation, you must have administration permissions. Log in as user <sapsid>adm.
Starting Instances Separately

If you need to start the instances of an SAP system separately, for example when you want to start a distributed or a high-availability system, proceed in the following sequence: 1. Start the database instance. 2. Start the central services instance SCS<Instance_Number>. If your system is a high-availability system, you first start the ABAP central services instance ASCS<Instance_Number> and then you start the Java central services instance SCS<Instance_Number>. 3. Start the primary application server instance DVEBMGS<Instance_Number>. 4. Start additional application server instance(s) D<Instance_Number> if there are any.
Stopping an SAP System or Instance

1. 2. 3.

Select the system or instance you want to stop and choose Stop from the context menu. In the Stop SAP System(s) dialog box, choose the required options. Choose OK. The SAP MC stops the specified system or system instances.
NOTE

The system might prompt you for the SAP system administrator credentials. To complete the operation, you must have administration permissions. Log in as user <sapsid>adm. Similarly, you can start, stop, or restart all SAP systems and individual instances registered in the SAP MC.
Stopping Instances Separately

If you need to stop the instances of an SAP system separately, for example when you want to start a distributed or a high-availability system, proceed in the following sequence: 1. Stop additional application server instance(s) D<Instance_Number> if there are any. 2. Stop the primary application server instance DVEBMGS<Instance_Number>. 3. Stop the central services instance SCS<Instance_Number>.

2013-07-15

CUSTOMER

113/132

7 7.8

Additional Information Starting and Stopping SAP System Instances

4.

If your system is a high-availability system, you first stop the Java central services instance SCS<Instance_Number> and then you stop the ABAP central services instance ASCS<Instance_Number>. Stop the database instance.

Registering Systems and Instances in the SAP Management Console

You can extend the list of systems and instances displayed in the SAP MC, so that you can monitor and administer all systems and instances from a single console. You can configure the SAP MC startup view to display the set of systems and instances you want to manage.
Prerequisites

The SAP MC is started.
Registering SAP Systems

1. 2.

In the SAP MC, choose File New . In the New System dialog box, enter the required data.
NOTE

3.

If you have already registered systems in the SAP MC, they are stored in the history. To open the System’s History dialog box, choose the browsing button next to the Instance Nr. field. Select an instance of the system that you want to add and choose OK. Choose Finish.

Registering Individual Instances

1. 2. 3.

In the SAP MC, choose File New . In the New System dialog box, enter the required data and deselect Always show all SAP Instances. The SAP MC displays the SAP system node, the instance node, and the relevant database node in a tree view in the navigation pane.
NOTE

To view all instances of the respective SAP system, select the relevant system node and choose Add Application Server from the context menu.
Configuring the SAP MC View

ÅX−Š You can choose the instances that the SAP MC displays automatically on startup: 1. In the Settings dialog box, select History. 2. In the right-hand side pane, choose the instance you want the SAP MC to display on startup. 3. Choose the << button. 4. Choose Apply and then choose OK. Similarly, you can remove instances from the startup configuration. ÅX−Š You can save the current configuration in a file: 1. Choose File Save Landscape .

114/132

CUSTOMER

2013-07-15

7 7.8

Additional Information Starting and Stopping SAP System Instances

2. In the Save dialog box, enter the required data. 3. Choose Save. Ý
(°< You can load a configuration from a file: 1. Choose File Load Landscape . 2. In the Open dialog box, select the configuration you want to load. 3. Choose Open.
More Information

For more information about how to handle the SAP MC, see the SAP Library [page 10] at: Ý
(°< SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1: Function-Oriented View Application Server Infrastructure SAP Management Console Ý
(°< SAP NetWeaver 7.3 and higher: Solution Life Cycle Management SAP Management Console

7.8.2 Starting and Stopping SAP System Instances Using Commands
You can start and stop SAP system instances using the startsap and stopsap commands. You can use command line options to specify these commands. Command line options are available in the new style or the old style.
Using New Style for Command Line Options and Parameters

Using the new style, the syntax is as follows:
stopsap | stopsap [-t | -task <task>] [-i | -instance <instance>] [-v | -vhost "<virtual hostname>[ <virtual hostname>]*"][-c | -check] [-h | -help] [-V | -VERSION] [-C | -checkVHost] EXAMPLE

If you want to start a primary application server instance DVEBGMS00 that has the virtual host names cic11 and cic12, enter the following commands:
startsap -t r3 -i DVEBGMS00 -v "cic11 cic12"

The following command line options and parameters are available:
Command Line Options (New Style) Parameter Name
[-t | -task <task>] [-i | -instance <instance>] [-v | -vhost "<virtual hostname> [ <virtual hostname>]*"] [-c | -check]

Description

Specify task Specify SAP system instance Specify virtual host names Check database and SAP instance status

2013-07-15

CUSTOMER

115/132

7 7.8

Additional Information Starting and Stopping SAP System Instances Description

Parameter Name
[-h | -help] [-V | -VERSION] [-C | -checkVHost]

Display help Display startsap script version Check virtual host name

Parameters for <task> (New Style) Parameter Name
check r3 db all | <blank> startupsrv

Description

Check status of database and SAP system instances Start or stop SAP instances only Start or stop database only Start or stop database and SAP instance Start or stop sapstartsrv program

Parameters for <instance> where <nn> is the instance number Parameter Name
DVEBMGS<nn> D<nn> ASCS<nn> SCS<nn> ERS<nn> SMDA<nn> W<nn> G<nn>

Description

Primary application server Instance Additional application server instance ABAP central services instance (ASCS instance) Java central services instance (SCS instance) Enqueue replication server instance (ERS instance) Diagnostics agent instance Web services instance Gateway instance

Using Old Style for Command Line Options and Parameters

Using the old style, the syntax is as follows:
stopsap | stopsap [db|r3|all|check|startupsrv] [<instance>] [<virtual hostname>] EXAMPLE

If you want to start a primary application server instance DVEBGMS00 that has the virtual host names cic11 and cic12, enter the following commands:
startsap r3 DVEBGMS00 cic11 cic12

The following command line options and parameters are available:
Command Line Options (Old Style) Parameter Name
check [<instance>] [<virtual hostname>] r3 [<instance>] [<virtual hostname>] db [<instance>] [<virtual hostname>] all | <blank>

Description

startupsrv

Check status of database and SAP system instances Start or stop SAP instances only Start or stop database only Start or stop database and all SAP system instances running on the same physical host Start or stop sapstartsrv program

116/132

CUSTOMER

2013-07-15

7 7.8

Additional Information Starting and Stopping SAP System Instances

Parameters for <instance> where <nn> is the instance number Parameter Name
DVEBMGS<nn> D<nn> ASCS<nn> SCS<nn> ERS<nn> SMDA<nn> W<nn> G<nn>

Description

Primary application server Instance Additional application server instance ABAP central services instance (ASCS instance) Java central services instance (SCS instance) Enqueue replication server instance (ERS instance) Diagnostics agent instance Web services instance Gateway instance

Prerequisites

Dý±¢¥ô Make sure that you have logged on to the physical host of the SAP system instances as user <sapsid>adm. Dý±¢¥ô Make sure that the host names defined in the DNS server match the names of the SAP system instance hosts. In particular, keep in mind that host names are case-sensitive. For example, if the names of the SAP system instance hosts are in uppercase, but the same host names are defined in the DNS server in lowercase, starting and stopping the system does not work. Dý±¢¥ô If you want to use startsap or stopsap (for example, in a script) and require the fully qualified name of these SAP scripts, create a link to the startsap script in the home directory of the corresponding user. Dý±¢¥ô You cannot use startsap or stopsap commands in a switchover cluster environment. Therefore in a high-availability (HA) system you must use the failover cluster software of your HA partner to start or stop instances running on the switchover cluster. Dý±¢¥ô You cannot use startsap or stopsap commands to start or stop database-specific tools. For more information about how to start or stop database-specific tools, see the database-specific information in this documentation and the documentation from the database manufacturer. Dý±¢¥ô Make sure that no SAP instance is running before you execute stopsap on a standalone database server. No automatic check is made. Dý±¢¥ô When you use stopsap in a Multiple Components in One Database (MCOD) system with two primary application server instances, only one primary application server instance and the database are shut down. Therefore, you must first stop the other SAP system or make sure that it has already been stopped.
Procedure
Starting an SAP System

Dý±¢¥ô If you want to start all SAP system instances running on the same host, execute the following command: New style: startsap or startsap -t all

2013-07-15

CUSTOMER

117/132

7 7.8

Additional Information Starting and Stopping SAP System Instances

Old style:startsap or startsap all _N‚JÞ“ If you want to start SAP system instances separately, enter the following command: New style:startsap -t r3 -i <instance> [-v "<virtual host name>"] Old style:startsap r3 <instance> [<virtual host name>] Make sure that you adhere to the following sequence when starting the instances: 1. Database instance 2. ERS instance for the SCS instance (if available) 3. ERS instance for the ASCS instance (if available) 4. SCS instance 5. ASCS instance 6. Primary application server instance 7. Additional application server instances (if available)
Stopping an SAP System

_N‚JÞ“ If you want to stop all SAP system instances running on the same host, execute the following command: New style: stopsap or stopsap -t all Old style:stopsap or stopsap all _N‚JÞ“ If you want to stop SAP system instances separately, enter the following command: New style:stopsap -t r3 -i <instance> [-v "<virtual host name>"] Old style:stopsap r3 <instance> [<virtual host name>] Make sure that you adhere to the following sequence when stopping the instances: 1. Additional application server instances (if available) 2. Primary application server instance 3. ASCS instance 4. SCS instance 5. ERS instance for the ASCS instance (if available) 6. ERS instance for the SCS instance (if available) 7. Database instance

7.8.3 Starting and Stopping the Diagnostics Agent Using Scripts
You can start and stop the diagnostics agent by running the startsap and stopsap scripts.
NOTE

You can only start or stop the diagnostics agent separately. It is not started or stopped automatically with the SAP system.

118/132

CUSTOMER

2013-07-15

7 7.9

Additional Information Deleting an SAP System or Single Instances

You can also use the SAP Management Console (SAP MC) to start or stop the diagnostics agent. For more information, see Starting and Stopping SAP System Instances Using the SAP Management Console [page 111].
Prerequisites

You have logged on to the host of the primary application server instance or of an additional application server instance as user <dasid>adm.
Procedure
Starting a Diagnostics Agent

To start a diagnostics agent, enter the following command:
startsap SMDA<Instance_Number> EXAMPLE startsap SMDA98 Stopping a Diagnostics Agent

To stop a diagnostics agent, enter the following command:
stopsap SMDA<Instance_Number> EXAMPLE stopsap SMDA98

7.9 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

With this installer option you do not delete the database software. Note the following when deleting an SAP system or single instances: (Æ Ô~Ł We strongly recommend that you delete an SAP system or single instances using the installer. However, you can also delete an SAP system or single instance manually. For more information, see SAP Note 1259982. (Æ Ô~Ł You cannot delete an SAP system remotely. (Æ Ô~Ł If you delete network-wide users, groups or service entries in an environment with Network Information System (NIS), other SAP installations might also be affected. Make sure that the users, groups, and service entries to be deleted are no longer required. (Æ Ô~Ł 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.

2013-07-15

CUSTOMER

119/132

7 7.9

Additional Information Deleting an SAP System or Single Instances

Í«M¶1Ï 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

Í«M¶1Ï You have installed your SAP system with standard SAP tools according to the installation documentation. Í«M¶1Ï You are logged on as user root. Í«M¶1Ï 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 SAPrelated processes are stopped.
NOTE

You do not have to stop the SAP Host Agent. The SAP Host Agent is stopped automatically during the uninstall process. Í«M¶1Ï When starting the uninstall, make sure that there are no SAP system user sessions still open.
Procedure

1. 2. 3.

Start the installer as described in Running the Installer [page 66]. On the Welcome screen, choose: Generic Installation Options <Database> Uninstall Uninstall – SAP Systems or Single Instances 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 Distributed or highavailability system

You can delete a standard system (where all instances reside on the same host) in one installer run. 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

120/132

CUSTOMER

2013-07-15

7 7.9

Additional Information Deleting an SAP System or Single Instances Deletion of Remarks

2. 3.

4. 5.

the contents of mounted global directories under /<sapmnt>/ <SAPSID>/ , such as instance profiles and kernel executables, are also deleted. Primary application server instance Database instance Choose whether you want to drop the entire database instance or only one or more database schemas. Since 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. Before deleting any database schema, make sure that: -k~9ƒ You have performed a recent offline database backup. -k~9ƒ You have stopped or deleted all SAP instances belonging to this database schema. -k~9ƒ You only delete the tablespaces that belong to the selected schema. The Java schema SAP<SCHEMAID>DB by default belongs to the database tablespace PSAP<SCHEMAID<DB. All other SAP tablespaces belong to the ABAP schema SAP<SCHEMAID> (or SAPR3 for older SAP systems). Central services instance (SCS) and Рif it exists Рthe related enqueue replication server instance 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 If you want to delete additional application server instances of an existing SAP server system, you have to run the installer to delete them locally on each additional application server instance host. Standalone SAP Host Agent The SAP Host Agent is automatically uninstalled from a host together with the last remaining SAP system instance. If you want to uninstall a standalone SAP 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:
/usr/sap/<DASID>/SYS/profile

4. 5. 6. 7.

When you have finished, delete the relevant directory structure on the global host. Delete the Oracle database software with the Oracle Universal Installer (OUI). For more information, see Deinstalling the Oracle Database Software [page 122]. If you created the directories /usr/sap/<SAPSID> and /<sapmnt>/<SAPSID> as mount points, but not as directories on the local file system, you have to remove them manually. To remove obsolete SLD data, see the following document:

2013-07-15

CUSTOMER

121/132

7 7.10

Additional Information Deleting the Oracle Database 11g Software http://scn.sap.com/docs/DOC-8516

How-to Manage House-Cleaning in the System Landscape Directory

- Duplicate System Entries

7.10 Deleting the Oracle Database 11g Software
This procedure tells you how to delete the database software, starting with Oracle Database 11g Release 2 (11.2). For more information, see SAP Note 1525025.
CAUTION

Do not use RunInstaller or the new uninstall tool to remove an Oracle 11.2 database installation. The uninstall tool might not only delete the software from the Oracle home, but also other files (database files, logs, traces, configuration files, inventory) in <ORACLE_BASE>. Therefore, we strongly recommend you to use the procedure below to remove the 11.2 Oracle home software.
Procedure

1.

Back up the central Oracle inventory, which is normally located at $ORACLE_BASE:
OS> cd $ORACLE_BASE OS> zip -r oraInventory.zip oraInventory

2.

Check whether Oracle home is registered in the central Oracle inventory:
OS> $ORACLE_HOME/OPatch/opatch \ lsinventory -all -invPtrLoc $ORACLE_HOME/oraInst.loc

3.

If Oracle home is registered, it appears in the displayed List returns error code 73. Oracle home must be registered in order to detach it. Detach Oracle home from the central Oracle inventory:
OS> $ORACLE_HOME/oui/bin/runInstaller \ -silent \ -detachHome ORACLE_HOME=$ORACLE_HOME \ -waitForCompletion \ -invPtrLoc $ORACLE_HOME/oraInst.loc

of Oracle Homes. Otherwise, opatch

At the end of the procedure, you see the message:
'DetachHome' was successful

4.

Remove the Oracle home software from the file system:
OS> rm -rf $ORACLE_HOME

122/132

CUSTOMER

2013-07-15

A A.1

Appendix Online Information from SAP

A Appendix

A.1 Online Information from SAP
More information is available online as follows:
Documentation Description Internet Address Title

Installation of Multiple http://scn.sap.com/docs/DOC-8559 Components in One Database (MCOD) and its availability on different platforms http://service.sap.com/instguidesnw <SAP SAP Front End installation NetWeaver release> Installation Installation - Clients Guide Copying SAP Systems Based http://service.sap.com/sltoolset Toolset 1.0 Software Provisioning Manager on SAP NetWeaver 7.1 or Higher Using Software Provisioning Manager 1.0 Maintenance Planning Guide
http://service.sap.com/mopz

Multiple Components in One Database (MCOD)

Software Logistics

How-Tos and Guides

SAP Front End Installation Guide – <Current Release> System Copy Guide — SAP Systems Based on the Application Server <Technology> of SAP NetWeaver on <OS> Maintenance Planning Guide: Using SAP Solution Manager <Release, SP> including Landscape Management Database (LMDB)

General Quick Links Description Internet Address
http://help.sap.com http://help.sap.com/netweaver

SAP Help Portal SAP NetWeaver Library in SAP Help Portal SAP ERP Library in SAP Help Portal SAP CRM Library in SAP Help Portal SAP SRM Library in SAP Help Portal SAP SCM Library in SAP Help Portal SL toolset Installation Guides

http://help.sap.com/erp http://help.sap.com/crm

http://help.sap.com/srm

http://help.sap.com/scm

http://service.sap.com/sltoolset http://service.sap.com/instguides

2013-07-15

CUSTOMER

123/132

A A.1

Appendix Online Information from SAP Internet Address
http://scn.sap.com/community/it-management/alm/softwarelogistics http://service.sap.com/notes http://scn.sap.com/community/database

Description

Software logistics in application lifecycle management SAP Notes Supported platforms and operating systems Product availability matrix (PAM) Release notes Unicode SAP systems and their availability System sizing (Quick sizer tool) SAP NetWeaver capabilities Application lifecycle management for SAP NetWeaver Security for SAP NetWeaver Information on SAP support package stacks SAP Solution Manager Maintenance optimizer

Related Resources

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

http://service.sap.com/sizing http://scn.sap.com/community/netweaver http://scn.sap.com/community/it-management/alm

http://scn.sap.com/community/security http://service.sap.com/sp-stacks

http://service.sap.com/solutionmanager http://service.sap.com/solman-mopz

124/132

CUSTOMER

2013-07-15

Typographic Conventions

Example
<Example>

Description

Example Example Example
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>”. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 ÷Ïu¢@ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. ÷Ïu¢@ Cross-references to other documentation or published works ÷Ïu¢@ Output on the screen following a user action, for example, messages ÷Ïu¢@ Source code or syntax quoted directly from a program ÷Ïu¢@ File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools 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 Keys on the keyboard

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

2013-07-15

CUSTOMER

125/132

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +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. 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. National product specifications may vary. 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. SAP 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. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Disclaimer

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.
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 includes ANTLR, which is released under the following BSD license: [The BSD License] Copyright (c) 2010 Terence Parr All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: >&Łþ'¨ Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. >&Łþ'¨ Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. >&Łþ'¨ Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF

126/132

CUSTOMER

2013-07-15

2.

SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems, Applications, Products in Data Processing Dietmar-Hopp-Allee 16 69190 Walldorf, Germany (hereinafter: SAP) and you (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: #I>4± The conditions indicated in the above permissions notice are met; #I>4± The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met: Copyright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems Inc. Copyright 1997 Moscow Center for SPARC Technology. Copyright 1999,2000 Boris Fomitchev Copyright 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. 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

2013-07-15

CUSTOMER

127/132

3.

4.

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 Maintenance SAP 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 warranty As 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 Liability 1. 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. Adobe Document Services Adobe, 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. Apache License, Version 2.0 1. Definitions: ÃElqÉÀ "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. ÃElqÉÀ "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. ÃElqÉÀ "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. ÃElqÉÀ "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. ÃElqÉÀ "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. ÃElqÉÀ "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

128/132

CUSTOMER

2013-07-15

i†s,_³

2.

3.

4.

5.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). i†s,_³ "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. i†s,_³ "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." i†s,_³ "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. Grant of Copyright License Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. Grant of Patent License Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. Redistribution You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: 1. You must give any other recipients of the Work or Derivative Works a copy of this License; and 2. You must cause any modified files to carry prominent notices stating that You changed the files; and 3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and 4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. Submission of Contributions

2013-07-15

CUSTOMER

129/132

6.

7.

8.

9.

Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. Trademarks This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. Disclaimer of Warranty Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. Limitation of Liability In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. Accepting Warranty or Additional Liability While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguides

130/132

CUSTOMER

2013-07-15

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +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.