installation guide erp6.0

Installation GuideSAP ERP 6.0 - EHP4 Ready ABAP on AIX: OracleBased on SAP NetWeaver 7.0 including Enhancement Package 1

Target Audience

n System administratorsn Technology consultants

PUBLICDocument version: 1.3 ‒ 05/25/2009

About this Installation Guide

SAP System Installation

SAP system installations should only beperformed by SAP Technical Consultantscertified for your operating system, yourdatabase, and the SAP system that you areinstalling

SAP Installation Tool

You must only use the SAP installation toolsaccording to the instructions and for thepurposes described in the SAP installationdocument. Improper use of the SAP installationtools can damage files and systems alreadyinstalled.

Downward Compatibility of Databases

For downward-compatible releases of DB/OSplatforms for SAP products, SAP plans to

regularly release the newest database (DB) andoperating-system (OS) versions of SAP products.These releases are downward-compatible withearlier SAP system releases.Note that for already shipped SAP components,we only support the installation for databaseversions proposed by the installationtool. Therefore, you must install an SAPcomponent or perform a system copy usinga downward-compatible database. Thatis, you either install the component withthe old proposed database version or youupgrade the old database version to thedownward-compatible new version.

2/140 PUBLIC 05/25/2009

Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan find the latest version at the following location:http://service.sap.com/erp-inst.

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

Version Date Description

1.30 5/25/2009 Minor Changes

1.20 2/17/2009 Updated information in Introduction [page 7]

1.10 2/5/2009 Removed information from Introduction [page 7]

1.0 11/21/2008 Initial Version

05/25/2009 PUBLIC 3/140

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



Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 71.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 81.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 10

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 Basic System Variants . . . . . . . . . . . . . . . . . . . . . 132.2 Hardware and Software Requirements . . . . . . . . . . . . . . . 152.2.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 162.2.2 Requirements for AIX . . . . . . . . . . . . . . . . . . . . 172.2.3 Requirements for a Central System . . . . . . . . . . . . . . . . 202.2.4 Requirements for a Distributed or a High Availability System . . . . . . 222.2.4.1 Requirements for a Central Services Instance . . . . . . . . . . . . 222.2.4.2 Requirements for the Central Instance . . . . . . . . . . . . . . 232.2.4.3 Requirements for the Database Instance . . . . . . . . . . . . . . 242.2.5 Requirements for a Dialog Instance . . . . . . . . . . . . . . . . 262.2.6 Checking and Modifying the AIX Kernel . . . . . . . . . . . . . . 272.2.7 Setting up Swap Space for AIX . . . . . . . . . . . . . . . . . . 282.3 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . 292.4 SAP System Transport Host . . . . . . . . . . . . . . . . . . . 312.5 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 312.6 High Availability: Planning the Switchover Cluster . . . . . . . . . . 38

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 433.1 High Availability: Switchover Preparations . . . . . . . . . . . . . 443.1.1 Preparing for Switchover . . . . . . . . . . . . . . . . . . . . 443.1.2 Setting Up File Systems for a High-Availability System . . . . . . . . . 463.1.3 Configuring Network File System . . . . . . . . . . . . . . . . 473.2 Creating Operating System Users . . . . . . . . . . . . . . . . 493.2.1 Creating AIX Groups and Users . . . . . . . . . . . . . . . . . 513.3 Setting Up File Systems and Raw Devices . . . . . . . . . . . . . . 523.3.1 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . 523.3.2 Oracle Directories . . . . . . . . . . . . . . . . . . . . . . 563.3.3 Setting Up File Systems and Raw Devices for AIX . . . . . . . . . . . 583.4 Exporting and Mounting the Global Transport Directory . . . . . . . . 603.5 Exporting and Mounting Directories via NFS for AIX . . . . . . . . . 61

4/140 PUBLIC 05/25/2009

3.6 Installing the Front-End Software . . . . . . . . . . . . . . . . 623.7 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 623.8 Installing the Java Runtime Environment . . . . . . . . . . . . . 633.9 Preparing and Mounting the Installation Media . . . . . . . . . . . 643.9.1 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 643.9.2 Downloading Installation DVDs from SAP Service Marketplace . . . . . 663.9.3 Mounting a CD / DVD for AIX . . . . . . . . . . . . . . . . . 67

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 694.1 Performing a High-Availability Installation . . . . . . . . . . . . . 694.2 Prerequisites before Starting SAPinst . . . . . . . . . . . . . . . 704.2.1 Prerequisites before Starting SAPinst: All Instances . . . . . . . . . . 704.2.2 Prerequisites before Starting SAPinst: Distributed Instances andHighAvailability 744.3 Installing an SAP System Using SAPinst . . . . . . . . . . . . . . 754.3.1 Running SAPinst on UNIX . . . . . . . . . . . . . . . . . . . 754.3.2 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 814.3.3 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 824.3.4 Performing a Remote Installation with SAPinst . . . . . . . . . . . 844.3.5 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . 854.3.6 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 884.4 Oracle Database Software Installation . . . . . . . . . . . . . . . 884.4.1 Updating SAP-Specific Files in the Oracle Staging Area . . . . . . . . . 894.4.2 Performing Steps for the AIX Operating System . . . . . . . . . . . 894.4.3 Running the Oracle Universal Installer . . . . . . . . . . . . . . 904.4.4 Installing the Current Patch Set . . . . . . . . . . . . . . . . . 924.4.5 Installing Required Interim Patches . . . . . . . . . . . . . . . . 92

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 955.1 Logging On to the Application Server . . . . . . . . . . . . . . . 965.2 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 965.3 Installing the SAP License . . . . . . . . . . . . . . . . . . . 995.4 High Availability: Setting Up Licenses . . . . . . . . . . . . . . . 995.5 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 1005.6 Configuring Remote Connection to SAP Support . . . . . . . . . . 1015.7 Installing the SAP Online Documentation . . . . . . . . . . . . . 1015.8 Performing Initial ABAP Configuration . . . . . . . . . . . . . . 1015.9 Performing Oracle-Specific Post-Installation Steps . . . . . . . . . . 1055.10 Configuring the Connection to a Central System Landscape Directory . . . 1065.11 Implementing ERP ABAP Add-On Components . . . . . . . . . . . 1065.12 Performing the Client Copy . . . . . . . . . . . . . . . . . . 1065.13 Performing a Full Installation Backup . . . . . . . . . . . . . . . 1075.14 Accessing Configuration Documentation in SAP Solution Manager . . . . 109

05/25/2009 PUBLIC 5/140

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 1116.1 Installation of Multiple Components in One Database . . . . . . . . . 1116.2 Integration of LDAP Directory Services . . . . . . . . . . . . . . 1136.3 Starting and Stopping SAP System Instances . . . . . . . . . . . . 1176.3.1 Starting and Stopping SAP System Instances Using the SAP Management

Console . . . . . . . . . . . . . . . . . . . . . . . . . . 1176.3.2 Starting and Stopping SAP System Instances Using Scripts . . . . . . . 1216.4 Creating a User for LDAP Directory Access . . . . . . . . . . . . . 1246.5 Heterogeneous SAP System Installation . . . . . . . . . . . . . . 1246.6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 1256.6.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 1256.7 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 1256.8 Deleting the Oracle Database Software . . . . . . . . . . . . . . 127

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . 129A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . 129

6/140 PUBLIC 05/25/2009

1 Introduction

1 Introduction

This document explains how to install SAP ERP 6.0 — EHP4 Ready (EHP4 for SAP ERP 6.0) ABAP.You perform the installation using SAPinst.SAP ERP 6.0 ‒ EHP4 Ready is based on the technology of SAP NetWeaver 7.0 including enhancementpackage 1. For more information about the technology provided by SAP ERP and SAP NetWeaver, seehttp://service.sap.com/erp and http://sdn.sap.com/irj/sdn/netweaver.Make sure you read the corresponding Master Guides before you start with this installation guide.The Master Guides are available as follows:http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP

enhancement package 4 for SAP ERP 6.0

Caution

See SAP Note 998833 for up-to-date information about release restrictions for EHP4 for SAP ERP 6.0.

You can install SAP ERP 6.0 - EHP4 Ready with the following software units:

n SAP ERP Central Component (ECC)

Note

SAP ERP Central Component (ECC) is not installed with the Java Add-In.

Note

You also install SAP NetWeaver Application Server ABAP (AS ABAP) with SAP ERP CentralComponent.

For more information about the usage types of SAP NetWeaver and their interdependencies, seethe documentMaster Guide ‒ SAP NetWeaver 7.0 at http://service.sap.com/instguidesNW70. Forrestrictions, see SAP Note 1164532.

Constraints

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

n Your operating system platform must be 64-bit.

Note

The only instance, you can still install on 32-bit is the dialog instance.

05/25/2009 PUBLIC 7/140

http://service.sap.com/erp



http://sdn.sap.com/irj/sdn/netweaver




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

http://service.sap.com/instguidesNW70




1 Introduction1.1 New Features

n The database must be Oracle 10.2.0.2 or higher.

You need to consider the following constraints after the installation:

n The installation of SAP ERP 6.0 - EHP4 Ready ABAP system based on SAP NetWeaver 7.0 includingenhancement package 1 contains only the basic EHP4 for SAP ERP 6.0 technical usage “ABAPTechnology for ERP EHP4”. To complete the installation process you have to install additionalEHP4 for SAP ERP 6.0 functionality in your SAP ERP 6.0 - EHP4 Ready ABAP system. You mustuse the Solution Manager Maintenance Optimizer to identify and download the correspondingsoftware components and the SAP enhancement package Installer to deploy the downloadedsoftware components in your system.For more information about the Solution Manager Maintenance Optimizer, see:http://service.sap.com/solman-mopz.For more information about the SAP enhancement package Installer, see the document InstallationGuide - SAP Enhancement Package Installation - Using SAP Enhancement Package Installer (SAPehpi) at:http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0

SAP enhancement package 4 for SAP ERP 6.0 Enhancement Package Installation on Existing SAP Systems

n You have to apply at least Support Package Stack (SPS) 1 of SAP enhancement package 4 forSAP ERP 6.0.

Naming Conventions

Terminology

n SAP system refers to EHP4 for SAP ERP 6.0.n ABAP system refers to EHP4 for SAP ERP 6.0 ABAP.

1.1 New Features

The following tables provide an overview of the new features related to the installation of this release:

Caution

Make sure that you read the release notes for your SAP system. You can find these athttp://service.sap.com/releasenotes

8/140 PUBLIC 05/25/2009

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







http://service.sap.com/releasenotes



1 Introduction1.1 New Features

SAP System Installation

Area Description

SAPinst As of SAP enhancement package 4 for SAP ERP 6.0, SAPinst has the following newfeatures:n You no longer have to install a Java Runtime Environment (JRE) to start the

SAPinst GUI.However, you still have to install a JRE to perform the installation with SAPinst(see Installing the Java Runtime Environment (JRE) [page 63]).

n If you want to terminate SAPinst from the SAPinst GUI menu, you now have tochoose SAPinst Cancel . If you choose File Exit , you only terminatethe SAPinst GUI (see Using SAPinst GUI [page 81]).

n You can directly access installation log files from the SAPinst GUI menu bychoosing SAPinst Log Browser (see Using SAPinst GUI [page 81]).

64-bit support onlyfor all instances exceptdialog instances

As of SAP ERP 6.0 SR3, you must install an SAP ERP system only on 64-bit operatingsystems.For the dialog instance, you can still use a 32-bit operating system. Therefore, youonly see the folder Software Life-Cycle Options on theWelcome screen when you start theinstallation from a 32-bit installation master DVD.You might need to install dialog instances on 32-bit operating systems if you want touse 32-bit SAP NetWeaver components, such as Adobe document services. However,first check whether such 32-bit components can run on 64-bit operating systems. Ifso, we recommend running these 32-bit components on a 64-bit operating system.

No new dual stack(ABAP+Java) systemsfor SAP enhancementpackage 4 for SAP ERP6.0

As of SAP enhancement package 4 for SAP ERP 6.0, you can no longer install SAPERP dual stack (ABAP+Java) systems. If you want to use both SAP ERP ABAP andJava Components in your system landscape, you have to proceed as follows:

1. Install a separate SAP ERP ABAP system.

2. Install a separate SAP ERP Java system.

3. Configure the connection of the SAP ERP Java system to the SAP ERP ABAPback-end system

Installation option JavaAdd-In for ABAP disabled

As of SAP enhancement package 4 for SAP ERP 6.0, the installation option JavaAdd-In for ABAP is disabled. That is, you can no longer install the Java Add-In to anexisting ABAP system.

MaintenanceOptimizer

All downloadable software components, released after April 2, 2007, are availableexclusively through the Maintenance Optimizer in SAP Solution Manager. Thiscomprises:n Support Package Stacks, Support Packages, and patches for Java instances, except

for kernel patchesn Legal changesn SAP applications and versions that are:l Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and all

applications based on this software, including SAP Business Suite 7l Optional for all SAP applications

For more information, see http://service.sap.com/solman-mopz.

05/25/2009 PUBLIC 9/140


1 Introduction1.2 SAP Notes for the Installation

Operating Systems and Platforms

Area Description

Support of OperatingSystems and Platforms

n For supported operating system and database releases, see the Product AvailabilityMatrix at http://service.sap.com/pam.

n For forums, blogs, content, and community related to all of the supporteddatabases and operating systems, see the Database and Operating Systems area athttp://sdn.sap.com/irj/sdn/dbos.

Oracle Database

New functions forOracle Database

n For a complete list of new Oracle features, see further documentation fromOracle, which you can find at:http://www.oracle.com/technology/products/database/oracle10g

n For a complete list of new features for SAP on Oracle, seehttp://sdn.sap.com/irj/sdn/ora.

1.2 SAP Notes for the Installation

Youmust read the following SAP Notes before you start the installation. These SAP Notes contain themost 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 athttp://service.sap.com/notes.

SAP Notes for the Installation

SAP Note Number Title Description

998833 Release Restrictions SAP ERP 6.0- Enhancement Packages

At the time of the release of EHP4 for SAP ERP6.0, limitations affect the productive usage ofcertain functions. This note provides customerinformation on these restrictions.

1165067 Release Info SAP EnhancementPackage 4 for SAP ERP 6.0

SAP Enhancement Package 4 for SAP ERP 6.0release information.

1164532 Release Restrictions for SAPNetWeaver 7.0 EHP1

Customer information on restrictions in theproduction use of certain functions.

1169801 Inst.NetWeaver 7.0 EHP1-Unix UNIX-specific information about the SAP systemand corrections to this documentation.

NoteThis note also contains UNIX-specificinformation referring to EHP4 for SAP ERP 6.0.

10/140 PUBLIC 05/25/2009

http://service.sap.com/pam

http://sdn.sap.com/irj/sdn/dbos

http://www.oracle.com/technology/products/database/oracle10g

http://sdn.sap.com/irj/sdn/ora

http://service.sap.com/notes







1 Introduction1.2 SAP Notes for the Installation

SAP Note Number Title Description

1169802 Inst. NetWeaver 7.0EHP1-UNIX/Oracle

Oracle-specific information about the SAPsystem installation and corrections to thisdocumentation.

NoteThis note also contains Oracle-specificinformation referring to EHP4 for SAP ERP 6.0.

828268 Oracle 10g: New functions Information about new Oracle features releasedfor the SAP system.

98252 Installing two Oracle databaseson a host

This SAP Note is only required if you plan toinstall more than one Oracle database on thesame host.

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

73606 Supported Languages and CodePages

Information on possible languages and languagecombinations in SAP systems

1067221 Central Note for HeterogeneousInstallation

Heterogeneous ABAP system landscapes ondifferent operating systems have been releasedfor some time. Heterogeneous Java systemlandscapes on different operating systems havenow also been released. However, not everycombination of operating system and databasesystem is released. This SAP Note and its relatedSAP Notes describe the released operating systemand database combinations.

789220 Support Packagelevel for NetWeaverInstallations/Upgrades

Information about the ABAP Support Packagelevels and kernel patch levels contained in thecurrent SAP NetWeaver release.

774615 Support Package levels ofERP/ECC installations/upgrades

Information about the ABAP Support Packagelevels and kernel patch levels contained in thecurrent SAP ERP release.

1258912 PLM Core 7.00 Release Notes andInformation

Information and references to other notes aboutinstalling PLM Core 7.00 and importing PLMCore 7.00 Support Packages.

05/25/2009 PUBLIC 11/140









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

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

2 Planning

2 Planning

This section tells you how to plan the installation of your SAP system.You have to complete the following planning activities, which are described in more detail in thelinked sections:

1. You plan your SAP system landscape according to theMaster Guide.In addition, we recommend that you read theTechnical Infrastructure Guide ‒ SAP NetWeaver 7.0, whichis available at: http://service.sap.com/installNW70.

2. You choose your basic system variant [page 13].3. You check the hardware and software requirements [page 15].4. You plan how to distribute the instances to hosts [page 29].5. You decide on the transport host to use [page 31].6. You identify basic SAP system parameters [page 31].

7.

Only valid for: HA (UNIX)

You plan the switchover cluster [page 38] for a high-availability (HA) system.End of: HA (UNIX)

The following planning activity is optional:

n Installation of Multiple Components in One Database (MCOD) [page 111]

2.1 Basic System Variants

The following section provides information about the basic system variants for an ABAP system andabout how to distribute SAP instances within them.Mandatory instances of an ABAP system are the central instance and the database instance.Optionally, you can install one or more dialog instances on a separate dialog instance host.

Note

Each instance can reside on a separate host.

05/25/2009 PUBLIC 13/140

http://service.sap.com/installNW70



2 Planning2.1 Basic System Variants

Figure 1: Minimum Distribution (Central System)

For a minimum system distribution, all instances reside on one host.

Figure 2: Maximum Distribution for a Distributed System

For a maximum system distribution, each instance resides on a separate host.

14/140 PUBLIC 05/25/2009

2 Planning2.2 Hardware and Software Requirements


Figure 3: Maximum Distribution for a High-Availability System

End of: HA (UNIX)

2.2 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating systemand the SAP instances.

Caution

If your hosts do not fully meet the requirements, you might experience problems when workingwith the SAP system.

Prerequisites

n Contact your OS vendor for the latest OS patches.n Make sure that the host name meets the requirements listed in SAP Note 611361.n Check your keyboard definitions.n If you want to install a printer on a host other than the central instance host (for example, on a

separate database instance host), make sure that the printer can be accessed under UNIX.

Process Flow

1. Check the Product Availability Matrix at http://service.sap.com/pam for supported operatingsystem releases.

2. Check the hardware and software requirements using:

05/25/2009 PUBLIC 15/140




n The Prerequisite Checker in one of two modes:l Standalone mode (optional) before the installation process

For more information, see Running the Prerequisite Checker Standalone [page 16].l Integrated in SAPinst (mandatory) during the installation process

For more information, see Running SAPinst on UNIX [page 75]

Note

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

n The hardware and software requirements checklists for:l AIX [page 17]l Central system [page 20]l Distributed or high availability system [page 22]l If you want to install dialog instance(s), check the requirements for a dialog instance [page 26].

Note

You might need to install dialog instances on 32-bit operating systems if you want to use32-bit SAP NetWeaver components, such as Adobe document services. However, first checkwhether such 32-bit components can run on 64-bit operating systems. If so, we recommendrunning these 32-bit components on a 64-bit operating system.

3. If you are installing a production system, the values provided by the Prerequisite Checker and thehardware and software requirements checklists are not sufficient. In addition, do the following:n You use the Quick Sizer tool available at http://service.sap.com/sizing.

For more information about the Quick Sizer and available sizing guides, see theMaster Guide ‒SAP NetWeaver 7.0 at http://service.sap.com/installnw70 Planning .

n You contact your hardware vendor, who can analyze the load and calculate suitable hardwaresizing depending on:l The set of applications to be deployedl How intensively the applications are to be usedl The number of users

2.2.1 Running the Prerequisite Checker in Standalone Mode(Optional)

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

16/140 PUBLIC 05/25/2009


http://service.sap.com/sizing



http://service.sap.com/installnw70


Recommendation

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

Note

When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks thehardware and software requirements in the background.

Prerequisites

n You have prepared the installation master DVD on the required installation host [page 64].n You make sure that the required prerequisites are met before starting SAPinst [page 70].

Procedure

1. You start SAPinst [page 75].2. On theWelcome screen, choose <Your SAP product> Software Life-Cycle Options Additional

Preparations Prerequisites Check .3. Follow the instructions in the SAPinst dialogs and enter the required parameters.

Note

For more information about each parameter, position the cursor on the parameter field andchoose F1 in SAPinst.

When you have finished, the Parameter Summary screen appears summarizing all parameters you haveentered and want to have checked. If you want to make a change, select the relevant parametersand choose Revise.

4. To start the prerequisites check, choose Next.

ResultThe Prerequisite Checker Results screen displays the results found. If required, you can also check theresults in file prerequisite_checker_results.html, which you can find in the installation directory.

Recommendation

We recommend making sure that your system meets all checked prerequisites before starting theinstallation. However, you can still start the installation even if your system does not meet allprerequisites. In this case, make sure that you know what you are doing.

2.2.2 Requirements for AIX

The host machine must meet the requirements listed in the tables below.

05/25/2009 PUBLIC 17/140


Note

The information here is not intended to replace the documentation of the AIX operating system.You can perform AIX-specific steps as follows:

n Manually by entering AIX commands with the appropriate options

n Using SystemManagement 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 numberto simulate the function key (for example, F4 is equivalent to ESC and 4 ).

Hardware Requirements

Requirement Values and Activities

Tape drive High-capacity tape drive with hardware compression is recommended.You can test the drive /dev/rmt0 with this command:tar -cvf /dev/<tape_device> <test_file>

The device name is always rmt0 unless more than one tape drive exists

DVD drive n ISO 9660 compatiblen You can configure multiple CD / DVD drives, but you cannot mount all of them. For

more information, seeMounting a CD / DVD for AIX [page 67].

Required disks For data security reasons, distribution over three disks is required. We recommendyou to distribute over five disks.To display available disks, enter this command:lspv

Disks marked none in the 3rd column are unused.To display free space on a disk, enter this command:lspv -p <disk_name>

Areas marked free in the 2nd column are unused.If an advanced disk array is available (for example, RAID), contact your hardware vendorto make sure that the data security requirements are covered by this technology.

RAM To display RAM size in KB, enter the following command:lsattr -El sys0 -a realmem

CPU The recommended minimum hardware is either two physical single core processors orone physical dual core processor.

Software Requirements


C++ runtime level Check the C++ runtime level with the following commands:n AIX 6.x:l #lslpp —L xlC.aix61.rte

The output must be at least 9.0.0.1.l #lslpp —L xlC.rte

The output must be at least 9.0.0.1.

18/140 PUBLIC 05/25/2009



n AIX 5.x:l #lslpp —L xlC.aix50.rte

The output must be at least 7.0.0.4.l #lslpp —L xlC.rte

The output must be at least 7.0.0.0.

Operating systemversion

Check the operating system version with the following command:lslpp -l bos.rte

The output must include the following or a larger version number:bos.rte 5.2.0.50

AIX MaintenanceLevel (ML) andTechnology Level(TL)

n AIX 6.x: The output of the command oslevel -s should be at least 6100-00-01.n AIX 5.3: The output of the command oslevel -s should be at least 5300-05-01

(TL 5 SP 1).n AIX 5.2: The output of the command oslevel -r should be at least 5200-04 (ML 4).

LDAP (LightweightDirectory AccessProtocol)

If you want to use LDAP, you require the following LDAP library:libldap.a

Additional software Make sure that the following additional file sets are installed:n bos.adt Base Application Developmentn bos.perf—performance and diagnostics toolsn perfagent.tools—performance monitoring toolsn bos.perf.libperfstat—Performance Statistics LibraryFor an overview of the installed file sets, enter the following command:lslpp –L | more

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

1. Start the SystemManagement Interface Tool (SMIT) with the following command:smitty mle_add_lang

2. Select the following:n Cultural Conventions to install:

ISO8859-1 German (Germany) [de_DE]

n Language Translation to install:

ISO8859-1 German [de_DE]

This step installs the required bos.loc and bos.iconv file sets.

3. Additionally, check that all file sets are in a consistent state with this command:lppchk –v

Other Requirements


Printer Check whether a file can be printed with this command:lp -d<printer_name> <test_file>

Check the status of your spool and the printers with this command:lpstat -t

05/25/2009 PUBLIC 19/140



Keyboard You can set the keyboard by typing this command on the directly connected console:smitty chkbd

You can select your keyboard under Motif by setting a language environment (LANG),for which a National Language Support (NLS) component is installed. The settingstake effect after reboot.

Network Test the network connection to the database server with this command:/etc/ping <db_server_name> 100 10

2.2.3 Requirements for a Central System

If you want to install a central system ‒ that is, all instances reside on one host ‒ the host must meetthe following requirements:The table below also lists themost relevant requirements for the Oracle database.You get the full list of hardware and software requirements from the relevantOracle database installation guide for your operating system, which you can find at:http://www.oracle.com/technology/documentation.

Recommendation

If you have access to Oracle Metalink we strongly recommend that you read document 169706.1. Thisdocument provides information about all operating system prerequisites and is regularly updated.

Caution

If your database resides on Network Attached Storage (NAS) you need to review and implement theOracle NAS guidelines. You need to mount network file systems with specific mount options, whichyou can find in the Oracle installation guide.

Caution

The database must be Oracle 10.2 or higher.



Distribution of theOracle Database

We recommend distribution of the Oracle database over three disks (RAID5) fordata security reasons.To decide how many hard disks are required for your Oracle database, see thesection Database System Configuration in SAP Database Guide: Oracle (BC-DB-ORA-DBA)in the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library(including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver byKey Capability Application Platform by Key Capability Platform-Wide Services Database

20/140 PUBLIC 05/25/2009

http://www.oracle.com/technology/documentation

http://help.sap.com/nw70




Support Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA) Getting Startedwith Oracle and the SAP System .

CPU At least one dual core CPU or two single core CPUs

Hard disk space n Hard disk drives with sufficient space for the SAP system and the database:60.0 GBFor more information about space requirements for the separate file systemsand directories, see Setting Up File Systems [page 52].

n 4.3 GB of temporary disk space for every required installation DVD thatyou have to copy to a local hard disk. For more information, see Preparing theInstallation DVDs [page 64].

n 1.2 GB of temporary disk space for the installation.

RAM 5.0 GB

Swap Space You need hard disk drives with sufficient space for swap. The required swap spacecan be calculated as follows:n Optimistic strategy:

For the database instance you need:l 0.75 * RAM, if RAM is greater than 8.0 GB.l 1 * RAM, if RAM is less than 8.0 GB.In addition, you need at least 20 GB for the central instance and at leastanother 10 GB for every dialog instance.

n Defensive strategy:3 * RAM, at least 20 GB

For more information, see SAP Note 1121904.



Network File System(NFS)

If application servers are installed decentralized, Network File System (NFS) mustbe installed.

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

National LanguageSupport (NLS)

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

GUI for Oracle DatabaseInstallation

On the database host, a graphical user interface (GUI), for example X11, is requiredfor the Oracle database software installation with runInstaller. For moreinformation, see the documentation of your operating system.

05/25/2009 PUBLIC 21/140




Oracle Interim Patches Check SAP Note 839182 whether you require an interim patch for the Oracledatabase installation. In this case, make sure you have the corresponding Perlversion as stated in that SAP Note.

Oracle KernelParameters

Review the Oracle-recommended kernel parameters and shell limits for youroperating system with Oracle Database 10g Release 2 (10.2).These are only recommendations from Oracle for optimizing the systemperformance in production environments. If the recommended settings are notsuitable for your system you must tune the kernel parameters accordingly.You can get the recommended shell limits and kernel parameters from the relevantOracle database installation guide for your operating system at:http://www.oracle.com/technology/documentation

2.2.4 Requirements for a Distributed or a High AvailabilitySystem

The following sections provide information about the hardware and software requirements in adistributed system, where the following SAP instances can reside on different hosts:

n Central services instance [page 22]


Note

The central services instance for ABAP (ASCS) is only required for a high availability installation.

End of: HA (UNIX)

n Central instance [page 23]n Database Instance [page 24]

Note

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

2.2.4.1 Requirements for a Central Services Instance

The central services instance host must meet the following requirements:

22/140 PUBLIC 05/25/2009





Note

The ASCS is only required for a high availability installation.

End of: HA (UNIX)




Hard disk space n Hard disk drives with sufficient space for the central services instance:4.0 GBFor more information about space requirements for the separate file systemsand directories, see Setting up File Systems [page 52].

n 4.3 GB of temporary disk space for every required installation DVD thatyou have to copy to a local hard disk. For more information, see Preparingthe Installation DVDs [page 64].


RAM 4.0 GB

Swap Space You need hard disk drives with sufficient space for swap. The required swap spacecan be calculated as follows:n Optimistic strategy:

At least 20 GB for the first SAP Instance to be installed on a server and at least10 GB for each additional active SAP Instance on that server






Network File System (NFS) must be installed.

2.2.4.2 Requirements for the Central Instance

The central instance host must meet the following requirements:

05/25/2009 PUBLIC 23/140






Hard disk space n Hard disk drives with sufficient space for the central instance:7.0 GBFor more information about space requirements for the separate filesystems and directories, see Setting Up File Systems [page 52] SAP Directories .



RAM 3.0 GB

Swap Space You need hard disk drives with sufficient space for swap. The required swapspace can be calculated as follows:n Optimistic strategy:

At least 20 GB for the first SAP Instance to be installed on a server and atleast 10 GB for each additional active SAP Instance on that server






If application servers are installed decentralized, Network File System (NFS) mustbe installed.

Required fonts and codepages

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

National LanguageSupport (NLS)

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

2.2.4.3 Requirements for the Database Instance

The database host must meet the following requirements:The table below lists themost relevant requirements for the Oracle database instance host.You get the full list of hardware and software requirements from the relevantOracle database installation guide for your operating system, which you can find at:http://www.oracle.com/technology/documentation

24/140 PUBLIC 05/25/2009




Recommendation

If you have access to Oracle Metalink we strongly recommend that you read document 169706.1. Thisdocument provides information about all operating system prerequisites and is regularly updated.

Caution

If your database resides on Network Attached Storage (NAS) you need to review and implement theOracle NAS guidelines. You need to mount network file systems with specific mount options, whichyou can find in the Oracle installation guide.

Caution

The database must be Oracle 10.2 or higher.



Distribution of the OracleDatabase

We recommend distribution over three disks (RAID5) for data security reasons.To decide how many hard disks are required for your Oracle database, see theDatabase System Configuration guide in SAP Database Guide: Oracle (BC-DB-ORA-DBA)in the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library(including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaverby Key Capability Application Platform by Key Capability Platform-Wide ServicesDatabase Support Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA) GettingStarted with Oracle and the SAP System .


Hard disk space n Hard disk drives with sufficient space for the database instance:50.0 GB (20.0 GB plus space for the SAP data file systems)For more information about space requirements for the separate file systemsand directories, see Setting Up File Systems and Raw Devices ‒ Oracle File Systems[page 56].

n 4.3 GB of temporary disk space for every required installation DVD you haveto copy to a local hard disk.For more information, see Preparing the Installation DVDs [page 64]


RAM 3.0 GB

Swap Space You need hard disk drives with sufficient space for swap. The required swap spacecan be calculated as follows:n 0.75 * RAM, if RAM is greater than 8.0 GBn 1 * RAM, if RAM is less than 8.0 GBFor more information, see SAP Note 1121904.

05/25/2009 PUBLIC 25/140







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

Required fonts and codepages

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

National Language Support(NLS)

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

GUI for Oracle DatabaseInstallation

On the database host, a graphical user interface (GUI), for example X11, isrequired for the Oracle database software installation with runInstaller. Formore information, see the documentation of your operating system.

Oracle Interim Patches Check SAP Note 839182 whether you require an interim patch for the Oracledatabase installation. In this case, make sure you have the corresponding Perlversion as stated in that SAP Note.

Oracle Kernel Parameters Review the Oracle-recommended kernel parameters and shell limits for youroperating system with Oracle Database 10g Release 2 (10.2).These are only recommendations from Oracle for optimizing the systemperformance in production environments. If the recommended settings arenot suitable for your system you must tune the kernel parameters accordingly.You can get the recommended shell limits and kernel parameters from therelevant Oracle database installation guide for your operating system, whichyou can find at:http://www.oracle.com/technology/documentation

2.2.5 Requirements for a Dialog Instance

The dialog instance host must meet the following requirements:




Hard disk space n Hard disk drives with sufficient space for the dialog instance.4.0 GBFor more information about space requirements for the separate file systemsand directories, see Setting Up File Systems [page 52].



26/140 PUBLIC 05/25/2009





RAM 3.0 GB

Swap Space You need hard disk drives with sufficient space for swap. The required swapspace can be calculated as follows:n Optimistic strategy:

At least 20 GB for the first SAP Instance to be installed on a server and at least10 GB for each additional active SAP Instance on that server





SAP kernel Make sure that the SAP kernel of the central instance has at least the patch levelof the SAP kernel on the SAP Kernel DVD that is used for the installation of thedialog instance.We recommend that you apply the most current SAP kernel from the SAP ServiceMarketplace at http://service.sap.com/swdc.


Network File System (NFS) must be installed.

2.2.6 Checking and Modifying the AIX Kernel

To run an SAP system on AIX with an Oracle database, you must check and— if necessary—modifythe UNIX operating system kernel.

Recommendation

We recommend that all UNIX kernel modifications be performed by your UNIX systemadministrator.

Procedure

1. Asynchronous I/O: If the database is installed using file systems, the settings for asynchronous I/O(aio) should be as follows:maxservers = minservers = 1.2 * number of data files used for the database.Set these values as follows:a) Enter:

smitty aio orsmit aio

b) Select Change / Show Characteristics of Asynchronous I/O.

05/25/2009 PUBLIC 27/140


http://service.sap.com/swdc


c) Enter the appropriate numbers for MINIMUM and MAXIMUM number of servers.

Note

If maxserver is greater than minserver, the surplus asynchronous I/O processes are chargedagainst the database system rather than root, and have a lower scheduling priority. Experienceshows that all processes become active very quickly and, once active, the asynchronous I/Oservers are never stopped. Therefore it is simpler and more efficient to set them to the samevalue at startup.

2. The setting forMaximum number of processes allowed per usermay need to be increased on the databaseserver. If you have increased the number of maxservers, then you should check this setting tomake sure that theMaximum number of processes allowed per user is at least greater than the maximumnumber of aioservers. This is not an issue if the values set as recommended above. Actually,it must be greater than the sum of the maximum number of aioservers plus all of the otherprocesses of the ora<dbsid> user.a) As a rule of thumb, set maxprocs to the following:n Small system: 512n Medium system: 2048n Large system: 4096

If you are not sure which value is applicable, choose the higher value.

Note

Setting maxprocs to a higher value than the number of processes that are actually useddoes not cause any extra overhead.

b) Set theMaximum number of Processes allowed per user to be greater than maxservers plus the resultfrom step a.:A) Enter:

smitty orsmit

B) Select System Environments.C) Select Change / Show Characteristics of Operating System.D) Enter the appropriate number forMaximum number of processes allowed per user, and choose Enter.

3. Adjust the minperm and maxperm settings according to SAP Note 973227.

2.2.7 Setting up Swap Space for AIX

1. Check the allocated swap space:a) To start the SystemManagement Interface Tool (SMIT), enter the following command:

28/140 PUBLIC 05/25/2009


2 Planning2.3 How to Distribute Instances to Hosts

smitty.b) Perform one of the following steps:n Choose Physical & Logical Storage Logical VolumeManager Paging Space List All Paging Spaces

n Enter this command:lsps -a

2. Check if there is sufficient swap space:n Optimistic strategy:

At least 20 GB for the first SAP Instance to be installed on a server and at least 10 GB for eachadditional active SAP Instance on that server

n Defensive strategy:3 * RAM

For more information, see SAP Note 1121904.3. If required, add another paging space using smitty:

a) Choose Physical & Logical Storage Logical VolumeManager Paging Space Add Another Paging SpaceA list of volume group names is displayed.

b) Select a volume group.c) Enter the size of paging space in logical partitions.d) Set Start using this paging space NOW ? to YES.e) Set Use this paging space each time the system is RESTARTED to YES.f) To exit smitty, choose F10 .g) To check the results, follow the procedure described above in step 1.

2.3 How to Distribute Instances to Hosts

The following provides information on how you can distribute the SAP instances for the different SAPsystem variants. You use SAPinst to install the SAP instances as a:

n Central system on a single hostYou run SAPinst and install all instances on one host.

n A distributed system on several hostsThe following figure shows how to distribute your instances on several hosts:

05/25/2009 PUBLIC 29/140


2 Planning2.3 How to Distribute Instances to Hosts

Figure 4: Distribution of Instances in an ABAP System

Note

You can use the SAP transport host or the SAP global host as your central instance host.

You perform the following steps:1. If you want to share the transport directory trans from another system, you have to mount it

from this system. Otherwise we recommend that you share the trans directory that is createdduring the installation of the central instance (see below).

2.

Only valid for: non-HA

On the SAP global host, you run SAPinst and prepare the global host.End of: non-HA

3.


On the SAP global host, you run SAPinst and install the ABAP central services instance (ASCS).End of: HA (UNIX)

4. On the SAP global host, you export the required file systems to the database and centralinstance host.

5. On the database host, you mount the exported file systems from the SAP global host andSAP transport host.

6. On the database host, you run SAPinst and install the database instance.7. On the central instance host, you mount the exported file systems from the SAP global host

and SAP transport host.8. On the central instance host, you run SAPinst and install the central instance.

30/140 PUBLIC 05/25/2009

2 Planning2.4 SAP System Transport Host

9. If required, you can now install one to <n> dialog instances. The procedure is the same asinstalling a central instance (replace “central instance” with “dialog instance” in the procedure).

2.4 SAP System Transport Host

The transport host contains the transport directory used by the SAP transport system to storetransport 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 transportdomains. 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 wantto use for your SAP system:

n Use the transport directory that SAPinst creates during the installation of the SAP system bydefault on the global host:SAPinst by default creates the transport directory on the global host in /usr/sap/trans.

n Use a transport directory located on a host other than the default host:l You can use an existing transport directory and host in your SAP system landscape.l 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 60].

More Information

n Setting Up File Systems and Raw Devices [page 52]n See the SAP Library:

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) EnglishSAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by KeyCapability Software Life Cycle Management Software Logistics Change and Transport System Change andTransport System ‒ Overview (BC-CTS) Basics of the Change and Transport System Transport ManagementSystem ‒ Concept

2.5 Basic SAP System Parameters

SAPinst prompts for input parameters during the Define Parameters phase of the installation.The tables below list the basic system parameters that you need to specify before installing your SAPsystem. For all other SAP system parameters, use the F1 help in the SAPinst screens.You can install your SAP system either in Typical or Custommode:

n Typical

05/25/2009 PUBLIC 31/140


2 Planning2.5 Basic SAP System Parameters

If you choose Typical, the installation is performed with default settings. This means that youonly have to respond to a small selection of prompts including at least the following, which aredescribed in the corresponding tables below:l SAP system ID and database IDl Master passwordl SAP system profile directory ‒ only for systems with instances on separate hostsIf you want to change any of the default settings, you can do so on the Parameter Summary screen.

n CustomIf you choose Custom, you are prompted for all parameters. At the end, you can still change any ofthese parameters on the Parameter Summary screen.

Note

If you change a parameter with the Revise button on the Parameter Summary screen, the installer takesyou to the screen where you can change the parameter. Depending on the changes, the installermight guide you through other screens with default parameters that it has so far processed. Thismight also happen if you press Back instead of Next on the screen

The tables below list the basic system parameters that you need to determine before installing yourSAP system. For all other SAP system parameters, use the F1 help in the SAPinst dialogs.

Java Runtime Environment

Parameters Description

Java Runtime Environment (JRE) A valid JRE is required for the installation with SAPinst. For moreinformation about JRE versions supported by SAP and about how toinstall them, see Installing the Java Runtime Environment [page 63].

SAP System ID and Database ID


SAP System ID <SAPSID> The SAP System ID <SAPSID> identifies the whole SAP system.

CautionChoose your SAP system ID carefully. You cannot change the SAP system IDafter the installation.

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

when installing a new SAP system.n Consists of exactly three alphanumeric charactersn Contains only uppercase lettersn Has a letter for the first charactern Does not include any of the following, which are reserved IDs:

32/140 PUBLIC 05/25/2009



ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY

LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID

SQL SYS TMP UID USR VAR

n If you want to install a dialog instance, make sure that no gateway instancewith the same SAP system ID (SAPSID) exists in your SAP system landscape.

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

CautionChoose your database ID carefully. Renaming is difficult and requires youto reinstall the SAP system.

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

ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT

KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA

SHG SID SQL SYS TMP UID USR VAR

n If you want to use an existing database system:Enter exactly the database ID of the existing database to which you want toadd the system.

Unicode or Non-Unicode System


Unicode System Every new installation of an SAP system is Unicode.You can only deselect this option if you perform the system copy for anon-Unicode SAP system that has been upgraded to SAP NetWeaver 7.0including Enhancement Package 1.

SAP System Instances, Hosts and Ports


Instance Number of theSAP system

Technical identifier for internal processes. It consists of a two-digit number from00 to 98.The instance number must be unique on a host. That is, if more than one SAPinstance is running on the same host, these instances must be assigned differentnumbers.To find out this number, look under the SAP directory/usr/sap/<SAPSID>/DVEBMGS<nn> on the host of the central instance.

05/25/2009 PUBLIC 33/140



Name of Instance Host Instance Host:Host name of the specific instance.To find out the host name, open a command prompt and enter hostname.The host name must not exceed 12 characters. For more information about theallowed host name length and characters, see SAP Note 611361.

Virtual Host Name You can use one or more virtual TCP/IP host names for SAP servers within anSAP server landscape to conceal their physical network identities from each other.This may be useful when moving SAP servers or complete server landscapes toother new hardware within a short time frame without having to carry out areinstallation or complicated reconfiguration. You need to specify the virtual hostname before you start SAPinst.For more information, see Prerequisites Before Starting SAPinst: All Instances [page 70]You also need to specify the virtual host name before you start SAPinst if you wantto install a high-availability (HA) system. For more information, see Performing aHigh-Availability Installation [page 69].n For more information about the use of virtual TCP/IP host names, see SAP

Note 962955.n For more information about the allowed host name length and characters,

see SAP Note 611361.

Message Server PortCaution

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

Port number of the SAP Message Server:If you do not specify a value, the default port number is used.ABAP Message Server PortThere is an external message server port and an internal message server port.The ABAP message server uses both the internal and the external message serverports. The default profile contains the configuration for both message server ports.The externalmessage server port uses the parameter rdisp/msserv with defaultvalue 36<nn>, where <nn> is the instance number of the ABAP message serverinstance.The internalmessage server port uses the parameter rdisp/msserv_internalwithdefault value 39<nn>, where <nn> is the instance number of the ABAP messageserver instance.For more information about the parameters used for message server ports, seeSAP Note 821875.

34/140 PUBLIC 05/25/2009






Master Password


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

CautionIf you did not create the operating system users manually before the installation,SAPinst creates them with the common master password (see table Operating SystemUsers). In this case, make sure that the master password meets the requirements ofyour operating system and of your database.

n ABAP users SAP* and DDIC

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

n Database users(for example ora<dbsid>

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

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

Operating System Users


User <sapsid>adm User <sapsid>adm is the system administrator user.If you did not create user <sapsid>admmanually before the installation, SAPinstcreates it automatically during the installation. SAPinst sets the Master Passwordby default, but you can overwrite it either by choosing parameter mode Customor by changing it on the parameter summary screen.Make sure that the user ID and group ID of this operating system user areunique and the same on each application server instance host.For more information, see Creating Operating System Users [page 49].

05/25/2009 PUBLIC 35/140


Solution Manager Key


SAP Solution Manager key To install your SAP system, you need to generate an SAP Solution Manager key [page62], which the installation requires to continue. For more information, seeSAP Note 805390.

Parameters Relevant for the File System


File system for the homedirectory user

/home/<username>

SAP systemmount directory /<sapmnt> is the base directory for the SAP system.For /<sapmnt> you can use a directory of your choice.Do not add <SAPSID> as subdirectory because the system adds this directoryautomatically.

ExampleIf you enter /<sapmnt>, the system creates the directory/<sapmnt>/<SAPSID>.

Oracle database file systems n Oracle homen sapdata homen Client destinationn sapdata directory

Parameters Relevant for the Database


Code page The code page that is used by your database (Unicode or Non-Unicode).

NoteYou only need to enter this parameter if you perform a target systeminstallation as part of a system copy.

Database schema, Passwords The ABAP database schema is named SAP<SCHEMA_ID>.Default name is SAPSR3.

RecommendationChoose a <SCHEMAID> that is different from your <SAPSID>.It might cause problems when you copy a system where <SCHEMAID> is thesame as <SAPSID>, and the database-specific method used for the copy doesnot allow you to rename the database schemas. In certain situations, youmight create a system copy with a new <SAPSID>, but where the databaseschema has the old <SAPSID>. This is not a technical problem, but mightconfuse the system administrator.

36/140 PUBLIC 05/25/2009




Password of User ora<dbsid> User ora<dbsid> is the database administrator user.This user is only required on the host on which the database instance runs.n If you created user ora<dbsid>manually before the installation, SAPinst

prompts you for the existing password of this user.

NoteIf you chose parameter mode Typical, SAPinst only prompts you for theexisting password of this user if the password is not the same as the MasterPassword.

n If you did not create user ora<dbsid>manually before the installation,SAPinst creates it automatically during the installation. SAPinst thenprompts you to enter and confirm a password for this user. In this case,SAPinst sets the Master Password by default. You can overwrite it.

NoteIf you chose parameter mode Typical, SAPinst does not prompt you for theexisting password of this user but creates this user and assigns the MasterPassword automatically.

Make sure that the user ID and group ID of this operating system user areunique and the same on each application instance host.For more information, see Creating Operating System Users [page 49].

User ID of User ora<dbsid> If you chose parameter mode Typical and you did not create ora<dbsid>manually before the installation, SAPinst automatically creates this user withthe appropriate user ID. In this case, SAPinst does not prompt you for the userID of ora<dbsid>.Make sure that the user ID of user ora<dbsid> is unique and the same on eachapplication instance host.For more information, see Creating Operating System Users [page 49].

Group IDs of sys, dba, andoper

If you chose parameter mode Typical and you did not create ora<dbsid>manually before the installation, SAPinst automatically creates this user.SAPinst also assigns the user to groups sys, dba and oper. In this case, SAPinstdoes not prompt you for the user ID of ora<dbsid>.Make sure that the group IDs of dba and oper are unique and the same oneach application instance host.For more information, see Creating Operating System Users [page 49].

Database User Oracle User System

05/25/2009 PUBLIC 37/140

2 Planning2.6 High Availability: Planning the Switchover Cluster


Oracle ListenerName, OracleListener Port

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

n If there is already an Oracle database installed on your installation host, youcan either use one listener for both databases or you have to specify anunused Listener Name and an unused Listener Port for the new listener.For more information if you use one listener for both databases, see SAPNote 98252.

n All dialog instances of an SAP systemmust use the same Listener Port thanthe database instance.

Tablespaces, Datafiles An Oracle database consists of one or more logical storage units calledtablespaces, which collectively store all of the database’s data.Each tablespace in an Oracle database consists of one or more files calleddatafiles, which are physical structures that conform to the operating systemin which Oracle is running.MaxDatafileSize is the initial size of the tablespace datafile and its mapping tothe new tablespace layout while importing the external file DBSIZE.XML.SAPinst prompts you to enter MaxDatafileSize in MB:n 0: Datafile size defined in DBSIZE.XML is not changed.n 2000: Default datafile size.n 10000: Maximum datafile size.For more information about space requirements of the SAP datafiles (sapdata1 - 4), see Requirements for the Database Instance [page 24].

Database Instance RAM The RAM that is required for the database instance installation.The default value used by SAPinst is 50 percent of the entire RAM.For more information about minimum RAM, see Requirements for the DatabaseInstance [page 24].

Login Shell SAPinst only prompts you for this parameter if you use a login shell otherthan the recommended C shell (csh).For more information, see SAP Note 202227.


2.6 High Availability: Planning the Switchover Cluster

You can reduce unplanned downtime for your high-availability (HA) SAP system by setting up aswitchover cluster. This setup replicates critical software units ‒ known as “single points of failure”(SPOFs) ‒ across multiple host 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 hardwarenode in the cluster. Manual intervention is not required. Applications accessing the failed softwareunit experience a short delay but can then resume processing as normal.

38/140 PUBLIC 05/25/2009

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



Switchover clusters also have the advantage that you can deliberately initiate switchover to free up aparticular node for planned systemmaintenance. Switchover solutions can protect against hardwarefailure and operating system failure but not against human error, such as operator errors or faultyapplication software.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 thesecan only exist once in a normal SAP system.You can protect software units that are not SPOFs against failure by simply replicating them. Forexample, you can add additional dialog instances (that is, additional application servers). Thiscomplements the switchover solution and is an essential part of building HA into your SAP system.

Recommendation

We recommend switchover clusters to ensure HA for your SAP system.

A switchover cluster consists of:

n A hardware cluster of two or more physically separate host machines to run multiple copies of thecritical software units, in an SAP system the SPOFs referred to above

n Switchover software to detect failure in a node and switch the affected software unit to the standbynode, where it can continue operating

n Amechanism to enable application software to seamlessly continue working with the switchedsoftware unit ‒ normally this is achieved by virtual addressing (although identity switchoveris also possible)

PrerequisitesYou must first discuss switchover clusters with your hardware partner because this is a complextechnical area. In particular, you need to choose a proprietary switchover product that works withyour operating system.We recommend that you read the following documentation before you start:

n Check the informations and the installation guides that are available athttp://sdn.sap.com/irj/sdn/ha.

n The standalone replicated enqueue server is a major contribution to an HA installation and isessential for a Java system. We strongly recommend you to use it for an ABAP system.For more information about how to install the standalone replicated enqueue server, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key CapabilityABAP Technology Client/Server Technology The SAP Lock Concept Standalone Enqueue Server Installingthe Standalone Enqueue Server

FeaturesThe following figure shows the essential features of a switchover setup:

05/25/2009 PUBLIC 39/140

http://sdn.sap.com/irj/sdn/ha





Figure 5:

Note

This figure and the figures in this section are only examples. You need to discuss your individual HAsetup with your HA partner.

The following figure shows an example of a switchover cluster in more detail:

40/140 PUBLIC 05/25/2009


Figure 6:

ConstraintsThis documentation concentrates on the switchover solution for the central services instance. Formore information about how to protect the NFS File System and the database instance by usingswitchover software or (for of the database) replicated database servers, contact your HA partner.You need tomake sure that your hardware is powerful enough to handle the increased workload aftera switchover. Some reduction in performance might be acceptable after an emergency. However, it isnot acceptable if the system comes to a standstill because it is overloaded after switchover.End of: HA (UNIX)

05/25/2009 PUBLIC 41/140

3 Preparation

3 Preparation

You have to complete the following preparations, which are described in more detail in the linkedsections:

1.


You perform the switchover preparations [page 44] for a high-availability (HA) system.End of: HA (UNIX)

2. If required, you create operating system users manually [page 49].3. You set up file systems or ‒ if required ‒ raw devices [page 52].4. If you want to perform a distributed installation, you export and mount global directories:

a) On the SAP trans host, you export the trans directory to SAP global host, central instance host,database instance host, and ‒ if required ‒ to the dialog instance host(s).

b) On the SAP global host, you export subdirectories exe, global, profile of /sapmnt/<SAPSID> tocentral instance host, database instance host, and ‒ if required ‒ to the dialog instance host(s).

c) You mount subdirectories exe, global, profile of /sapmnt/<SAPSID> and directory trans onthe database instance host and on the central instance host. If you want to install one or moredialog instance(s), you also have to mount these directories on the dialog instance host.

For more information about exporting and mounting directories, see:n Exporting and Mounting the Global Transport Directory [page 60]n Exporting and Mounting Directories via NFS for AIX [page 61]

5. You install the SAP front-end software [page 62].6. You generate the SAP Solution Manager Key [page 62].7. You install the Java Runtime Environment [page 63].8. You prepare and mount the installation media [page 64].

05/25/2009 PUBLIC 43/140

3 Preparation3.1 High Availability: Switchover Preparations


3.1 High Availability: Switchover Preparations


3.1.1 Preparing for Switchover

This section describes the extra preparations you need tomake for a high availability (HA) installation.For more information, consult your HA partner.You need to perform the preparations listed below on host A and ‒ after you have installed the centralservices (SCS) instance ‒ on host B.

PrerequisitesYou have already installed the hardware ‒ that is, hosts, disks, and network ‒ and decided howto distribute the database, SAP instances, and (if required) Network File System (NFS) server overthe cluster nodes (that is, over the host machines). For more information, see Planning the SwitchoverCluster [page 38].

Procedure

1. You check that your system meets the hardware and software requirements [page 15] for an HA setup,including the switchover software.

2. You set up file systems (that is, disk partitions), mount points, and (if required) NFS for yourHA system on:a) Node A before the installation of the SCS instance with SAPinstb) Node B after the installation of the SCS instance with SAPinstTo do this proceed as follows:

Recommendation

If possible, use journaled file systems (JFS), which allows much quicker recovery after a hostmachine crash. With JFS, you can reduce the switchover time because the hard disk maintainsdata integrity in the event of a system crash or if the system is otherwise halted abnormally.

a) You set up the required file systems [page 46] using mount points or NFSb) If required, you configure NFS [page 47], making sure you are using the virtual host name for NFS

to enable NFS switchover.c) You assign the local file systems to mount points.d) You assign the shared file systems to mount points in appropriate cluster packages.

44/140 PUBLIC 05/25/2009


Example

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

Figure 7:

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

4. You assign the virtual IP addresses and host names for SCS instance, and (if required) NFS toappropriate cluster packages.

Note

For more information on how to assign resources to cluster packages, ask your HA partner.

End of: HA (UNIX)

05/25/2009 PUBLIC 45/140



3.1.2 Setting Up File Systems for a High-Availability System

When you prepare a high-availability (HA) installation, you need to set up your file systems asdescribed here. For more information, consult your HA partner.

Procedure

1. Create the file systems or raw partitions for the central services (SCS) instance on shared disks. Formore information, see Setting Up File Systems and Raw Devices [page 52].

Note

The directories /<sapmnt>/<SAPSID> and /usr/sap/trans have to be mounted from a NetworkFile System (NFS), whereas /usr/sap/<SAPSID> is a directory of the AS instance that is alwaysmounted on the instance (not with NFS).Therefore, if the central instance host is not the NFS server host, you might have to mount atleast the first two file systems on different physical disks from the third file system.

2. If the node that takes over the central instance also runs an AS instance during normal operation,we recommend that you use a different approach for the file system for the /usr/sap/<SAPSID>directory./usr/sap/<SAPSID> contains two subdirectories:n SYS contains links to the central directory /<sapmnt>/<SAPSID>n <INSTTYPE><NR> contains data for the local AS instance

The name <INSTTYPE><NR> is defined by the type of services and the application server number,for example DVEBMSG00.

Only the directory <INSTTYPE><NR> needs to be migrated with the AS instance during theswitchover. Since the SYS subdirectory contains only links that do not require any space, it canbe created locally on each cluster node. Therefore, instead of /usr/sap/<SAPSID>, create a filesystem for /usr/sap/<SAPSID>/<INSTTYPE><NR> with the usual <> substitutions. The file namefor the central instance is usually DVEBMGS00. This avoids mount conflicts when switching over toa node on which an AS instance is already running. The DVEBMGS00 directory can join the tree/usr/sap/<SAPSID> instead of mounting on top of it.

46/140 PUBLIC 05/25/2009


Note

This approach becomes increasingly important when you want to cluster central services whileother instances run on the cluster hosts outside the control of the switchover software, so as touse the resources efficiently. Youmust use this approach for integrated installations of the ASwith ABAP and Java stacks.

End of: HA (UNIX)


3.1.3 Configuring Network File System

If required, you configure Network File System (NFS), which is a system-wide Single Point-of-Failure(SPOF), for a high-availability (HA) installation. For more information, consult your HA partner.We regard NFS as an extension to the operating system. The switchover product protects NFS andmakes it transparently available to the SAP system in switchover situations.You need to decide:

n How to protect NFSn Which switchover cluster nodes NFS is to run on

The NFS configuration might depend on your database system. The directories need to be availablefor the SAP system before and after a switchover.

Caution

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

Procedure

1. Check the NFS directories, several of which need to be shared between all instances of a system.These directories are:

n /<sapmnt>/<SAPSID>/profile

Contains the different profiles to simplify maintenance

n /<sapmnt>/<SAPSID>/global

Contains log files of batch jobs and central SysLog

n /usr/sap/trans

Contains data and log files for objects transported between different SAP Web AS systems (forexample, development ‒ integration). This transport directory ought to be accessible by at leastone AS instance of each system, but preferably by all.

05/25/2009 PUBLIC 47/140


n /<sapmnt>/<SAPSID>/exe

Contains the kernel executables. These executables ought to be accessible on all AS instanceslocally without having to use NFS. The best solution is to store them locally on all AS instancehosts.

2. Since you can protect NFS by a switchover product, it makes sense to install it on a cluster node.The requirements of your database systemmight dictate how NFS has to be set up. If required, youcan configure the NFS server on the cluster node of the CI or the DB.In both cases the NFS clients use the virtual IP address to mount NFS. If the second node is used asan additional SAP instance during normal operation (for example, as a dialog instance), it alsoneeds to mount the directories listed above from the primary node.When exporting the directories with their original names, you might encounter the problem ofa “busy NFS mount” on the standby node. You can use the following workaround to solve thisproblem:a) On the primary server, mount the disks containing the directories:

/export/usr/sap/trans

/export/<sapmnt>/<SAPSID>

b) The primary server creates soft links to the directories with the original SAP names:/usr/sap/trans —> /export/usr/sap/trans

/<sapmnt>/<SAPSID> —> /export/<sapmnt>/<SAPSID>

Alternatively the primary server can also mount the directories:/export/usr/sap/trans —> /usr/sap/trans

/export/<sapmnt>/SID —> /<sapmnt>/<SAPSID>

c) The primary server exports:/export/usr/sap/trans


d) The standby NFS mounts:from virt.IP:/export/usr/sap/trans to /usr/sap/trans

from virt.IP:/export/<sapmnt>/<SAPSID> to /<sapmnt>/<SAPSID>

If the primary node goes down and a switchover occurs, the following happens:

n These directories on the standby node become busy:/usr/sap/trans

/<sapmnt>/<SAPSID>

n The standby node mounts disks to:/export/usr/sap/trans


n The standby node configures the virtual IP address virt.IPn The standby node exports:

/export/usr/sap/trans


48/140 PUBLIC 05/25/2009

3 Preparation3.2 Creating Operating System Users

n These directories on the standby node are accessible again:/usr/sap/trans

/<sapmnt>/<SAPSID>

End of: HA (UNIX)

End of: HA (UNIX)

3.2 Creating Operating System Users

During the installation, SAPinst checks all required accounts (users, groups) and services on thelocal machine. SAPinst checks whether the required users and groups already exist. If not, it createsnew users and groups as necessary.If you do not want SAPinst to create operating systems users, groups, and services automatically, youcan optionally create them before the installation. This might be the case if you use central usermanagement such as Network Information System (NIS).SAPinst checks if the required services are available on the host and creates them if necessary. See thelog messages about the service entries and adapt the network-wide (NIS) entries accordingly.SAPinst checks the NIS users, groups, and services using NIS commands. However, SAPinst does notchange NIS configurations.

Recommendation

For a distributed or a high-availability system, we recommend that you distribute accountinformation (operating system users and groups) over the network, for example by using NetworkInformation Service (NIS).

Caution

All usersmust have identical environment settings. If you change the environment delivered bySAP, such as variables, paths, and so on, we do not assume responsibility.

If you want to use global accounts that are configured on a separate host, you can do this in oneof the following ways:

n You start SAPinst and choose Software Life-Cycle Tasks Additional Preparation Tasks Operating SystemUsers and Groups . For more information, see Running SAPinst on UNIX [page 75].

n You create operating system users and groups manually as described inCreating AIX Groups and Users [page 51]

Operating System Users and Groups

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

05/25/2009 PUBLIC 49/140


Caution

Do not delete any shell initialization scripts in the home directory of the OS users. This applies evenif you do not intend to use the shells that these scripts are for.

Caution

If you use NFS-V4 file system, you have to create the ora<dbsid> user on the NFS server. You can dothis either manually or by running Operating System Users and Groups. This user must have the same userID as the ora<dbsid> user on the database server.Otherwise, you get the error message FSL-02098 Could not change owner of ... during theinstallation of the database instance.

Caution

The user ID (UID) and group ID (GID) of each operating system user and group must be identical forall servers belonging to the same SAP system.This does not mean that all users and groups have to be installed on all SAP servers.

Users and Groups

User Primary Group Additional Group(s) Comment

root No primary group is assignedby SAPinst.

sapinst Superuser of the UNIXoperating system

<sapsid>adm sapsys oper, dba, sapinst SAP system administrator

<smdsid>adm sapsys sapinst Diagnostics Agentadministrator

ora<dbsid> dba oper, sapinst Database administrator

The user ora<dbsid> is only required on the host where the database instance runs.

Caution

If these operating system users already exist, make sure that they are assigned to group sapinst.

Caution

If you install a distributed system and you use local operating system user accounts instead of centraluser management (for example, NIS), user <sapsid>adm, sapadm, and the database operating systemuser must have the same password on all hosts.

50/140 PUBLIC 05/25/2009


Groups and Members

Groups Members

sapsys <sapsid>adm

oper <sapsid>adm, ora<dbsid>

dba <sapsid>adm, ora<dbsid>

sapinst root, <sapsid>adm, ora<dbsid>

3.2.1 Creating AIX Groups and Users

Creating AIX Groups and UsersTo create AIX groups and users, use the SystemManagement Interface Tool (SMIT) :

1. Create groups as follows:a) Enter the command smitty.b) Choose Security and Users Groups Add a group .c) Enter a group name ‒ for example, sapsys ‒ and set administration group to true.d) Press F3 until the Security & Usersmenu appears.

2. To create users, proceed as follows:a) Enter a user name, for example <sapsid>adm.b) Enter all required values.

3. Set the initial password using the following command:passwd <user>

Example

passwd <sapsid>adm

Checking Created UsersAs user root check all existing users as follows:

1. Enter the command smitty.2. Choose Security & Users Users Change/Show Characteristics of a User .3. To get a list of users, choose F4 .4. For user root and each created user <user> perform the following steps:

a) Select <user>.b) Change field Soft CPU time to -1 (this is the default value).c) Change field Soft CORE file size to 2097151 (this is the default value).

05/25/2009 PUBLIC 51/140

3 Preparation3.3 Setting Up File Systems and Raw Devices

d) Change field Soft FILE size to 4194302.

Note

If you are using large file enabled file systems, set the field Soft FILE size to -1 (unlimited).

e) Change field Soft DATA segment to -1.f) Change field Soft STACK size to -1.

You must make sure that the system-wide default HARD values are not explicitly defined to belower than the values given above. Check the file /etc/security/limits under the default:stanza. If they are not explicitly set, then the values are as shown in the table at the top of the file.

Checking the Operating System

1. Enter the command smitty.2. Choose System Environments Change/Show Characteristics of Operating System .3. ChangeMaximum number of PROCESSES allowed per user to 500.4. To exit SMIT, choose F10 .

More InformationFor more information about the users and groups that are created either by SAPinst or manually, seeCreating Operating System Users [page 49].

3.3 Setting Up File Systems and Raw Devices

The following section(s) describe the directories that are required for the instances of an SAP system,how to set up file systems and ‒ if required ‒ raw devices on operating system level:

n SAP Directories [page 52]n Oracle Directories [page 56]n Setting Up File Systems and Raw Devices for AIX [page 58]

3.3.1 SAP Directories

Depending on the installation option you have chosen, SAPinst automatically creates the directorieslisted 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 availableon 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

52/140 PUBLIC 05/25/2009


directories you want to set up separate file systems. If you do not set up any file system on yourinstallation host, SAPinst creates all directories in the root directory /.SAPinst prompts you only for the <sapmnt> directory during the installation. See also table ParametersRelevant for the File System in Basic SAP System Parameters [page 31].


Note

For more information about how to set up your file systems if you are performing an HA installation,see High Availability: Setting Up File Systems [page 46].

End of: HA (UNIX)

Caution

SAPinst uses sapcpe to replicate the kernel automaticallyfrom /usr/sap/<SAPSID>/SYS/exe/run/DIR_CT_RUN to/usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP system instance.The following entry in the start profile is responsible for this:Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF),where $(_PF) points to the instance profile.Do not delete DIR_CT_RUN from the instance profile. Otherwise, you cannot restart the system afterpatches have been applied.For more information, see Applying the Latest Kernel and Support Packages [page 100].

SAP Directories for an ABAP System

Every new installation of an ABAP standalone system is Unicode.Non-Unicode for ABAP is still supported only if you perform the system copy for a non-Unicodesystem that has been upgraded to SAP NetWeaver 7.0 SR3.

05/25/2009 PUBLIC 53/140


Figure 8: SAP Directories for an SAP ABAP System (Unicode or Non-Unicode)

The instance name (instance ID) of the ABAP central instance is DVEBMGS<Instance_Number>, and theinstance name of an ABAP dialog instance is D<Instance_Number>.


If you are performing an HA installation of your ABAP system, there is also an ABAP central servicesinstance called ASCS<Instance_Number>.End of: HA (UNIX)

Example

For example, the file system structure might look as follows:On a central instance with SAP system ID C11 and instance name DVEBMGS00.The ABAP dialog instance has the instance name D01.

SAP Directories in Detail

Note

The listed space requirements are initial SAP requirements.Depending on your operating system, you might also have to add space for administrative purposes.

The following directories are global, that is, they are accessed by all hosts in the SAP system.

54/140 PUBLIC 05/25/2009


SAP Directories

Directory Description Space Required

<sapmnt>/<SAPSID> Software and data for one SAP systemThis directory is physically located on the SAP global host. Inhomogeneous systems, you need to mount it via NFS (NetworkFile System) for all hosts belonging to the same SAP system. Itcontains the following subdirectories:n exe

This directory contains executable kernel programs.If you install an SAP system with distributed instances, youhave to share this directory for all hosts with the sameoperating system. For more information, see Prerequisites BeforeStarting SAPinst: Distributed Instances [page 74].

n global

This directory contains log files.If you install an SAP system with distributed instances,you have to share this directory for all hosts. For moreinformation, see Prerequisites Before Starting SAPinst: DistributedInstances [page 74].

n profile

This directory contains the start and operations profiles ofall instances.If you install an SAP system with distributed instances,you have to share this directory for all hosts. For moreinformation, see Prerequisites Before Starting SAPinst: DistributedInstances [page 74].

3.0 GB

/usr/sap/<SAPSID> Instance-specific data, symbolic links to the data for onesystemThis directory contains files for the operation of a local instance.There is a subdirectory <INSTANCE_NAME> for each instanceinstalled on the local instance host. The directory SYS containsonly soft links to appropriate directories in /<sapmnt>/<SAPSID>/

for storing data used by several instances.There are subdirectories of /usr/sap/<SAPSID>/SYSwith symboliclinks to subdirectories of /<sapmnt>/<SAPSID>:n /usr/sap/<SAPSID>/SYS/profile is linked to

/<sapmnt>/<SAPSID>/profile

n /usr/sap/<SAPSID>/SYS/global is linked to/<sapmnt>/<SAPSID>/global

n /usr/sap/<SAPSID>/SYS/exe/run is linked to/usr/sap/<SAPSID>/SYS/exe/dbg, which is linked to/<sapmnt>/<SAPSID>/exe

SAPinst sets up these directory structures during the installation.Executables located in/usr/sap/<SAPSID>/SYS/exe/run arereplicated by sapcpe to the exe directory of instances of the type<INSTANCE_NAME> and ASCS<No>.

NoteMake sure that sufficient space is available in directory

4.0 GB

05/25/2009 PUBLIC 55/140



/usr/sap/<SAPSID>/<INSTANCE_NAME>, since this stores SAPtraces for the instance. Changes in SAP system profiles can alsoaffect the disk space.

/usr/sap/trans Global transport directory for all SAP systemsFor more information about exporting and mounting the globaltransport directory, see Exporting and Mounting the Global TransportDirectory [page 60]The global transport directory is used by the Change andTransport System (CTS). The CTS helps you to organizedevelopment projects in the ABAP Workbench and inCustomizing, and then transport the changes between the SAPsystems in your system landscape. For more information, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including

Enhancement Package 1) English SAP NetWeaver Library SAPNetWeaver by Key Capability Solution Life Cycle Management by KeyCapability Software Life Cycle Management Software LogisticsChange and Transport System

2.0 GB

For more information about the directories required for the database instance, see Oracle Directories[page 56].

More InformationFor more information about sapcpe, see http://help.sap.com/nw70 SAP NetWeaver 7.0 Library(including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key CapabilityApplication Platform by Key Capability Application Server ABAP Client/Server Technology Local Executables onSAP Instances Functions of the Automatic Synchronization Program sapcpe

3.3.2 Oracle Directories

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

Note

Unicode systems require additional hardware resources. You can find more information aboutUnicode SAP systems at http://service.sap.com/unicode.

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

56/140 PUBLIC 05/25/2009





http://service.sap.com/unicode




Figure 9: Oracle Directories

Oracle Directories


/oracle Oracle base directory 50 MB for Oracle software

/oracle/client File system for Oracle client softwareSAPinst creates the directory/oracle/client/102_64/instantclient

during the installation.

100 MB

/oracle/stage/102_64 Installation and upgrade directory for databasesoftware (staging area)This directory is also used for Oracle upgrades.We recommend that you do not delete it afterthe installation.

5.5 GB

/oracle/<DBSID> Home directory of user ora<dbsid>We recommend that /oracle/<DBSID> does notreside in the root directory. It must reside in a filesystem with support for large files.For more information about how to create filesystems larger than 2 GB on your operatingsystem, see:Setting Up File Systems and Raw Devices for AIX [page 58]Therefore, either create /oracle/<DBSID> as aseparate file system with support for large filesor create /oracle as a file system with supportfor large files and create /oracle/<DBSID> as adirectory in /oracle.

100 MB for files of userora<dbsid> (for example, logfiles)

05/25/2009 PUBLIC 57/140



/oracle/<DBSID>/102_64 Home directory for Oracle instance <DBSID>(<ORACLE_HOME>).<ORACLE_HOME>must reside on a local disk. Itcannot be a softlink.

n Database instance: 4.0 GBn All other instances: 200

MBMake sure that this filesystem has permissions777.

/oracle/<DBSID>/origlogA Original set A of redo logs 200 MB

/oracle/<DBSID>/origlogB Original set B of redo logs 200 MB

/oracle/<DBSID>/mirrlogA Mirrored set A of redo logs 200 MB

/oracle/<DBSID>/mirrlogB Mirrored set B of redo logs 200 MB

/oracle/<DBSID>/oraarch New standard backup file system for Oracle offlineredo logsUse a separate disk for the file system/oracle/<DBSID>/oraarch.The file system /oracle/<SAPSID>/saparch stillremains but now only contains brbackup logfiles. /oracle/<SAPSID>/saparch is automaticallycreated by SAPinst.

For the installation,the archive directory/oracle/<DBSID>/oraarch

requires at least 400 MB freedisk space. For the operationof your SAP system, werecommend that the archivedirectory provides enoughspace for archives betweentwobackups. In a productionsystem, the amount archivedeach day is between 300 MBand 1 GB.

/oracle/<DBSID>/sapreorg Working directory for database administration 1.5 GB

/oracle/<DBSID>/sapdata1 SAP data




For space requirements ofthe SAP data file systemsrequired for the installation,see the following file:<Export_DVD>/DATA_UNITS/EXP1/

DB/ORA/DBSIZE.XML.See also the General section inSAP Note 1169802

3.3.3 Setting Up File Systems and Raw Devices for AIX

Setting up File Systems

Note

If you want to create file systems larger than 2 GB, see SAP Note 129439.Note that large files can lead to performance degradation due to access synchronization over thenodes. For performance reasons, smaller files are recommended for very active data.

58/140 PUBLIC 05/25/2009




1. Create one logical volume for each file system listed in the appropriate SAP profile:a) Using SMIT, choose Physical & Logical Storage Logical Volume Manager Logical Volumes Add a

Logical Volume .b) Enter a volume group name, for example, sapr3vg.c) Enter a logical volume name, for example, lvsap01.d) Enter the number of logical partitions.e) Press F3 until the Physical & Logical Storagemenu appears.

2. Create the file systems.a) Using SMIT, choose Physical & Logical Storage File Systems Add/Change/Show/Delete File Systems

Journaled File Systems Add a Journaled File System on a previously defined Logical Volume Add a StandardJournaled File System .If you want to use large enabled file systems for files larger than 2 GB, you have to choose Add aLarge File Enabled Journaled File System instead of Add a Standard Journaled File System.If you want to use JFS2 file systems, you have to choose Enhanced Journaled File System insteadof Journaled File System.

b) To get a list of logical volumes, choose F4 .c) Select one logical volume.

Caution

Select the logical volume with the desired size.

d) Enter mount point as given in the file system list files.

Example

/oracle/<DBSID>/sapdata1

e) Set mount automatically to yes.f) To exit smitty, choose F10 .

Setting up Raw Devices

1. Create volume group.2. Create logical volume:

a) Enter the command smitty.b) Choose Physical & Logical Storage Logical Volume Manager Logical Volumes Add a Logical Volume .c) Enter volume group name.d) Enter logical volume name (for example: lvsap02).e) Enter the number of logical partitions.f) Set the logical volume TYPE to r3data and press ENTER.

05/25/2009 PUBLIC 59/140

3 Preparation3.4 Exporting and Mounting the Global Transport Directory

g) To exit SMIT, choose F10 .

Note

The logical volume can be accessed through /dev/r<name of raw log.vol>.

Example

A logical volume called lvsap02 points to the device name /dev/rlvsap02.

3. Accessing raw devices:It is not necessary to create a link to access the volume.

3.4 Exporting and Mounting the Global Transport Directory

In your SAP system landscape, a global transport directory for all SAP systems is required.

n If this global transport directory already exists, make sure that it is exported on the global transportdirectory host and mount it on the SAP instance installation host.

n If this global transport directory does not exist, proceed as follows:l Create the transport directory (either on the central instance host or on a file server).l Export it on the global transport directory host.l If you did not create the transport directory on your SAP instance installation host, mount it

there.

Exporting the Transport Directory

1. Log on as user root to the host where the global transport directory /usr/sap/trans resides.2. Make sure that /usr/sap/trans belongs to the group sapsys and to the user root.3. 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 tomount it.

1. Log on as user root to the central or dialog instance host where /usr/sap/trans is to be mounted.2. Create the mount point /usr/sap/trans.3. Mount /usr/sap/trans using Network File System (NFS) from the exporting host.

More InformationMounting Directories via NFS for AIX [page 61]

60/140 PUBLIC 05/25/2009

3 Preparation3.5 Exporting and Mounting Directories via NFS for AIX

3.5 Exporting and Mounting Directories via NFS for AIX

There are two ways of mounting directories via NFS:

n Manuallyn Using the System Management Interface Tool (SMIT)

ProcedureTo mount directories via NFS from the host where the directory to be mounted resides:

1. Log on as user root.2. To start NFS services at the host where the directory to be mounted resides, use SMIT as follows:

a) Enter the command smitty.b) Choose Communications Applications and Services NFS Network File System (NFS) Configure NFS

on this System Start NFS .c) In the line Start NFS now, on system restart or both, enter: both.d) Choose ENTER .

3. Export the directory (for example <sapmnt>/<SAPSID>/exe) with read or read-write access forthe host where the additional instance runs:a) Enter the command smitty.b) Choose Communications Applications and Services NFS Network File System (NFS) Add a Directory

to Exports List .c) Enter the path of the directory that you want to export (for example, <sapmnt>/<SAPSID>/exe).d) Choose export mode (use read-write or read-only as required by SAP). In the line HOSTS allowed

root access, enter the name of the host where the additional instance runs. For security reasons,this root access should be disabled after the installation.

e) In the line Export directory now, system restart or both, enter: bothf) Choose ENTER .

4. Create the mount point at the host where the additional instance runs: /usr/bin/mkdir<sapmnt>/<SAPSID>/exe

5. Mount the directory on the host where the additional instance runs.a) Enter the command smitty.b) Choose Communications Applications and Services NFS Network File System (NFS) Add a File

System for Mounting .c) Enter the path name of the mount point.d) Enter the path name of the remote directory (the directory of the central instance).e) Enter the host where the remote directory resides.f) SetMount now, add entry to /etc/filesystems or both to both.g) Set /etc/filesystems entry will mount the directory on system RESTART to yes.h) ChangeMount file system soft or hard to soft and press ENTER.

05/25/2009 PUBLIC 61/140

3 Preparation3.6 Installing the Front-End Software

6. If you exported the directory with read-write access, check if the host where the future additionalinstance is to run has write access to directory <sapmnt>/<SAPSID>/exe using the followingcommands:cd <sapmnt>/<SAPSID>/exe

touch test (create a file called test)

ls -l test (check if file test is created)

rm test (remove the file test)

3.6 Installing the Front-End Software

For the installation, make sure that the front-end software is installed on at least one computer inyour system environment.With installation software NW SAPSetup for the SAP Front-End, you can optimize the deploymentof SAP GUI to thousands of clients. You can easily tailor installation packages to match yourrequirements, distribute patches, and set up automatic update processes for your clients.We recommend that you install SAP Front-End release 7.10.For more information about installing the front-end software, see the documentation SAP Front EndInstallation Guide - Release 7.10 at:http://service.sap.com/installNW70 Installation Installation - Clients

3.7 Generating the SAP Solution Manager Key

You must generate the Solution Manager key because the installation tool prompts for it during theinstallation. Without this key, the installation process cannot continue. For more informationabout SAP Solution Manager and its role within your system landscape, see the Master Guide ofyour SAP application.

Procedure

1. If SAP Solution Manager is not yet available in your system landscape, proceed as follows:a) Order SAP Solution Manager as described in SAP Note 628901.b) Install SAP Solution Manager as described in the documentation Installation Guide ‒ SAP Solution

Manager <Current Release> on <OS>: <Database>, which is available at:http://service.sap.com/instguides SAP Components SAP Solution Manager <Current

Release>2. Generate the SAP Solution Manager key as described in SAP Note 811923.

62/140 PUBLIC 05/25/2009





http://service.sap.com/instguides




3 Preparation3.8 Installing the Java Runtime Environment

ResultThe SAP Solution Manager system displays the key for which you are prompted during theinstallation of your SAP system.

3.8 Installing the Java Runtime Environment

You need to prepare your system for SAPinst. This includes the installation of a Java RuntimeEnvironment (JRE), which is required for SAPinst.

Note

If required, you can perform a remote installation using a standalone SAPinst GUI on a separateWindows or UNIX host. This lets you perform the installation on a remote host, controlling it withthe SAPinst GUI from a local host. If you want to perform a remote installation, see Performing aRemote Installation with SAPinst [page 84].

Procedure

1. Check the JRE versions that are released for SAP systems in the Product Availability Matrix (PAM):a) Go to http://service.sap.com/pam.b) On the right-hand panel, choose SAP Application Components <your product> .c) Choose tabstrip JSE Platforms.

Note

For more information about the recommended JRE version for your operating system and abouthow to download it, see SAP Note 723909.

2. Make sure a valid JRE version is installed, as follows:n If the JRE is not already installed, you need to download and install it.n If the JRE is not already installed

Since the JRE is not part of the SAP shipment, you need to download and install it. The JREis part of the JDK (Java Development Kit).

n If the JRE is already installedCheck the installed version of the JRE by entering:java -version

Note

SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment.If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME.

05/25/2009 PUBLIC 63/140





3 Preparation3.9 Preparing and Mounting the Installation Media

3.9 Preparing and Mounting the Installation Media

3.9.1 Preparing the Installation DVDs

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

n You obtain the installation DVDs as part of the installation package.n You can also download the installation DVDs from SAP Service Marketplace [page 66].

Procedure

1. Identify the required DVDs for your installation as listed below.Keep them separate from the remaining DVDs as this helps you to avoid mixing up DVDs duringthe installation.

Caution

The media names listed below are abbreviated.You can find the full names in sectionMedia Information in the corresponding Master Guides at:http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP

6.0 SAP enhancement package 4 for SAP ERP 6.0

Note

If you are installing on an existing system using Multiple Components in One Database (MCOD),the required DVDs differ.

The following table shows the required DVDs for the installation of an SAP system based onthe usage type AS ABAP:

Note

For a central system, where all mandatory instances reside on one host, you need the installationDVDs that are required for the central instance and database instance.

SAP Instance Installation Required DVDs

Global host preparation n Installation Master DVDn Kernel DVD

64/140 PUBLIC 05/25/2009





SAP Instance Installation Required DVDs

Central instance, dialog instance n Installation Master DVDn Kernel DVDn RDBMS Client DVD

Database instance n Installation Master DVDn Kernel DVDn SAP ERP Installation Export DVDn RDBMS DVDn RDBMS Patch DVD (if available)

NoteFor an MCOD system you require the RDBMS ClientDVD instead of the RDBMS DVD and the RDBMS PatchDVD (if available).

n RDBMS Client DVD

2. Make the required installation media available on each installation host.If you need information about how to mount DVDs on AIX, seeMounting a CD / DVD for AIX[page 67].

Note

Depending on your installation type, one or more instances can reside on the same host. Youneed to keep this in mind when you make the required installation media available on eachinstallation host.For a central system, you need to make all required installation media available on the singleinstallation host.

Use one of the following methods to make DVDs available:n Before the installation, copy DVDs manually to local hard disks.n During the installation, use the SAPinst Media Browser dialog and copy the entire DVDs to the

path you entered in the Copy Package To column.

Caution

n Mount the DVDs locally. We do not recommend you to use Network File System (NFS),because reading from DVDs mounted with NFS might fail.

n If you copy the DVDs to disk, make sure that the paths to the destination location of the copiedDVDs do not contain any blanks.

n If you perform a local installation and there is only one DVD drive available on yourinstallation host, you must copy at least the Installation Master DVD to the local file system.

05/25/2009 PUBLIC 65/140


3.9.2 Downloading Installation DVDs from SAP ServiceMarketplace

You normally obtain the installation DVDs as part of the installation package from SAP.However, you can also download installation DVDs from:http://service.sap.com/swdc Download Installations and Upgrades Entry by Application Group

<SAP solution> <SAP product> <SAP release> Installation and Upgrade <operating system><database>If you download installation DVDs, note that DVDs might be split into several files. In this case, youhave to reassemble the required files after the download.

PrerequisitesTo extract the downloaded SAR files make sure that you use the latest SAPCAR version, which youcan find at http://service.sap.com/swdc. You need at least SAPCAR 700 or SAPCAR 640 withpatch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR files.For more information, see SAP Note 212876.

Procedure

1. Create a download directory on the host on which you want to run SAPinst.2. Identify all download objects that belong to one installation DVD according to one or both of the

following:n Material number

All download objects that are part of an installation DVD have the same material number andan individual sequence number:<material_number>_<sequence_number>

Example

51031387_151031387_2...

n TitleAll objects that are part of an installation DVD have the same title, such as<solution><DVD_name><OS> or <database>RDBMS<OS> for RDBMS DVDs.

3. Download the objects to the download directory.4. Extract the individual download objects using SAPCAR, starting with the lowest sequence number

‒ for example 51031387_1, then 51031387_2, and so on.During the download SAPCAR sets up the structure of the installation DVD.

66/140 PUBLIC 05/25/2009









Note

SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always acceptwith Yes.

3.9.3 Mounting a CD / DVD for AIX

Note

<medium-mountdir> refers to either <cd-mountdir> or <dvd-mountdir>.

Use the following procedure to mount a CD / DVD:

Procedure

1. Log on as user root.2. Add a CD / DVD file system.

a) Enter the command smitty.b) Choose Physical & Logical Storage File Systems Add / Change / Show / Delete File Systems CDROM

File Systems Add a CDROM File System .c) To get a list of device names, choose F4 .

Select a device name.d) Enter the mount point <medium-mountdir>.

Example

<medium-mountdir> is /sapcd

e) Choose ENTER .f) To exit smitty, choose F10 .

3. Mount the CD / DVD as follows:

Note

Alternatively, you can mount the CD / DVDmanually with the following command: mount -v

cdrfs -r /dev/cd0 /sapcd.

a) Enter the command smitty.b) Choose Physical & Logical Storage File Systems Mount a File System .c) Place the cursor on File System Name and choose F4 .d) Select the CD / DVD device /dev/cd0.e) Place the cursor on field Directory over which to mount and choose F4 .f) Select /sapcd.g) Place the cursor on field Type of File System and choose F4 .

05/25/2009 PUBLIC 67/140


h) Select cdrfs.i) ChangeMount as Read Only system to YESj) Choose ENTER .k) To exit smitty, choose F10 .

68/140 PUBLIC 05/25/2009

4 Installation

4 Installation

Note

Make sure that you have completed the planning and preparation activities before you start theinstallation.

To install your SAP system, you have to perform the following steps, which are described in moredetail in the linked sections:

Process Flow

1.


If required, you perform a high-availability installation [page 69].End of: HA (UNIX)

2. You check the prerequisites for the instances that you want to install before starting SAPinst [page 70].3. You install your SAP system using SAPinst [page 75].

Note

Do not install the Oracle database software before you run SAPinst.SAPinst stops and prompts you to install the Oracle database [page 88] while the installation of thedatabase instance is running.If you install a system into an existing database (MCOD), this action is not required.


4.1 Performing a High-Availability Installation

This section describes how to perform a high-availability (HA) installation. For more information,consult your HA partner.

Prerequisites

n You have completed all preparations, including switchover preparations. For more informationabout how to do this, see High Availability: Switchover Preparations [page 44].

n You have set the environment variable SAPINST_USE_HOSTNAME to specify the virtual hostname for the installation. Alternatively you can specify the virtual host name in the command to

05/25/2009 PUBLIC 69/140

4 Installation4.2 Prerequisites before Starting SAPinst

start SAPinst. For more information about how to set this environment variable, see Prerequisitesbefore Starting SAPinst: All Instances [page 70].

Procedure

1. Run SAPinst [page 75] to install the central services instance (ASCS) using the virtual host name onthe primary cluster node, host A.

2. Prepare the standby node, host B, making sure that it meets the hardware and softwarerequirements and it has all the necessary file systems, mount points, and (if required) NetworkFile System (NFS), as described in Preparing for Switchover [page 44].

3. Set up the user environment on the standby node, host B.For more information, see Creating Operating System Users [page 49]. Make sure that you use the sameuser and group IDs as on the primary node. Create the home directories of users and copy all filesfrom the home directory of the primary node.

4. Configure the switchover software and test that switchover functions correctly.5. Install the database instance on the primary node, host A.6. Install the central instance with SAPinst [page 75] on the primary node, host A.

Note

In a high-availability installation, the central instance does not need to be part of the clusterbecause it is no longer a single point of failure (SPOF). The SPOF is now in the central servicesinstance (ASCS), which is protected by the cluster.

7. If required, install additional dialog instances with SAPinst [page 75] to replicate the SAP system services thatare not a SPOF. These nodes do not need to be part of the cluster.

Note

Make sure that you complete the post-installation activities for high availability.

End of: HA (UNIX)

4.2 Prerequisites before Starting SAPinst

4.2.1 Prerequisites before Starting SAPinst: All Instances

This section provides information about running SAPinst that is valid for the installation of allinstances (central, database, and dialog instance).

70/140 PUBLIC 05/25/2009


Prerequisites

n Make sure that you have defined the most important SAP system parameters as described in BasicSAP System Parameters [page 31] before you start the installation.

n Check that your installation hosts meets the requirements for the installation services that youwant to install. For more information, see Running the Prerequisite Checker [page 16].

Procedure

1. If you want to install a dialog instance for an upgraded SAP system:a) Edit DEFAULT.PFL.b) Insert a line with the parameter rdisp/msserv_internal and set it to a free port number.c) Restart all instances of the SAP system.

Example

This shows the required change to the instance profile:DEFAULT.PFL

Before the change:...rdisp/msserv = sapms<SAPSID>

...After the change:...rdisp/msserv = sapms<SAPSID>

rdisp/msserv_internal = <free port number>

...

2. Check the value of the environment variable TEMP, TMP, or TMPDIR: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 variable TEMP, TMP, or TMPDIR points ‒ forexample, by using a crontab entry.

n SAPinst normally creates the installation directory sapinst_instdir directly below thetemporary directory. SAPinst finds the temporary directory by checking the value of theenvironment variables TEMP, TMP, or TMPDIR. If no value is set for these variables, SAPinst 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 using the following commands:

Shell Used Command

Bourne shell (sh) TEMP=<directory>

export TEMP

05/25/2009 PUBLIC 71/140


Shell Used Command

C shell (csh) setenv TEMP <directory>

Korn shell (ksh) export TEMP=<directory>

n Make sure that you have at least 60 MB of free space in the installation directory for eachinstallation service. In addition, you need 200 MB free space for the SAPinst executables. Ifyou cannot provide 200 MB free space in the temporary directory, you can set one of theenvironment variables TEMP, TMP, or TMPDIR to another directory with 200 MB free space for theSAPinst executables.

n Make sure that the temporary directory has the permissions 777.The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory.These executables are deleted again after SAPinst has stopped running.If required, you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C .

Caution

If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.

3. If you are installing a second or subsequent SAP system into an existing database, make surethat the database is up and running before starting the installation. For more information, seeInstallation of Multiple Components in One Database [page 111].

4. Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java RuntimeEnvironment (JRE).

5. If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE forAIX 64-bit.

6. 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 SAPinst GUI.

Shell Used Command

Bourne shell (sh) DISPLAY=<host_name>:0.0

export DISPLAY

C shell (csh) setenv DISPLAY <host_name>:0.0

Korn shell (ksh) export DISPLAY=<host_name>:0.0

7. Check the following values for user root:n In csh execute limit

Output Properties

cputime unlimited

filesize unlimited

72/140 PUBLIC 05/25/2009


Output Properties

datasize 2097148 KB

stacksize 8192 KB

coredumpsize unlimited

descriptors 8192

memorysize unlimited

n In sh or ksh execute ulimit -a

Output Properties

time(seconds) unlimited

file(blocks) unlimited

data(kbytes) 2097148

stack(kbytes) 8192

coredump(blocks) unlimited

nofiles(descriptors) 8192

memory(KBytes) 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:l In csh execute:

limit descriptors 8192

l In sh or ksh execute:ulimit -n 8192

8. If you want to use a virtual host name, you have to set the environment variableSAPINST_USE_HOSTNAME to specify the required virtual host name before you start SAPinst.

Shell Used Command

Bourne shell (sh) SAPINST_USE_HOSTNAME=<directory>

export SAPINST_USE_HOSTNAME

C shell (csh) setenv SAPINST_USE_HOSTNAME <directory>

Korn shell (ksh) export SAPINST_USE_HOSTNAME=<directory>

If you do not set this environment variable now, you can specify an equivalent parameter for thevirtual host name when you run SAPinst [page 75].

05/25/2009 PUBLIC 73/140


4.2.2 Prerequisites before Starting SAPinst: DistributedInstances and High Availability

If you install a database or a dialog instance on a host other than the SAP Global host, you mustmount directories from the SAP Global host.

Prerequisites

n If you want to install the executables locally instead of sharing them, do notmount the exedirectory with Network File System (NFS). Instead, create <sapmnt>/<SAPSID>/exe as a localdirectory (not a link) with a minimum of 1100 MB free space.

n If you are installing a heterogeneous SAP system (that is, the instances are installed on differentoperating-system platforms), do notmount the exe directory. For more information, seeHeterogeneous SAP System Installations [page 124].

Procedure

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

<sapmnt>/<SAPSID>/profile

<sapmnt>/<SAPSID>/global

For more information, seeMounting Directories via NFS for AIX [page 61].

Caution

Make sure that the global transport directory is mounted on every host where you want to installan SAP instance. For more information, see Exporting and Mounting the Global Transport Directory [page60]. Otherwise, the installation fails.

2. Log on to the host of the new instance as user root.3. 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 these mount points are permanent. Otherwise automatic start of the instanceservices does not work when you reboot the system.

74/140 PUBLIC 05/25/2009

4 Installation4.3 Installing an SAP System Using SAPinst

4.3 Installing an SAP System Using SAPinst

The following sections tell you how to install the various instances of an SAP system, or a standaloneengine:

n Running SAPinst on UNIX [page 75]n Using SAPinst GUI [page 81]n Interrupted Installation with SAPinst [page 82]n Performing a Remote Installation with SAPinst [page 84]n Starting SAPinst GUI Separately [page 85].n Entries in the Services File Created by SAPinst [page 88]

4.3.1 Running SAPinst on UNIX

This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a SAPinst GUIand a GUI server, which both use Java.This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running onthe same host and on the local display: When you start SAPinst, SAPinst GUI and the GUI serveralso start. SAPinst GUI connects via a secure SSL connection to the GUI server and the GUI serverconnects to SAPinst.If you need to see the installation on a remote display, we recommend you perform a remote installation withSAPinst [page 84], where SAPinst GUI is running on a separate host from SAPinst and the GUI server.Alternatively you can use an X server for Microsoft Windows or other remote desktop tools likevncviewer or nxserver/nxclient ‒ offered by various vendors or open source ‒ for remote access toSAPinst GUI on Windows workstations. We recommend you use the Hummingbird Exceed X Server,which we use to validate installations with SAPinst. For more information, see SAP Note 1170809.

PrerequisitesMake sure that your installation host meets the prerequisites before starting SAPinst [page 70].

Procedure

1. Log on to your host as user root.

Caution

Make sure that the root user has not set any environment variables for a different SAP system ordatabase.

2. If you want to install a central instance, a central services instance, a database instance, or a dialoginstance, mount the Installation Master DVDMount the DVDs locally. We do not recommend that you use Network File System (NFS),because reading from DVDs mounted with NFS might fail.

05/25/2009 PUBLIC 75/140



For more information about mounting DVDs, seeMounting a CD / DVD for AIX [page 67].3. Start SAPinst from the Installation Master DVD by entering the following commands:

cd <Installation Master_DVD>/IM_<OS>

./sapinst

Note

n During the installation, the default ports 21200, 21212, and 4239 are used for communicationbetween SAPinst, GUI server, SAPinst GUI, and HTTP server, as follows:l SAPinst uses port 21200 to communicate with the GUI server.

l The GUI server uses port 21212 to communicate with SAPinst GUI.

l 4239 is the port of the HTTP server, which is part of the GUI server.You get an error message if one of these ports is already in use by another service. In this case,you must execute sapinst using the following parameters:SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>

GUISERVER_HTTP_PORT=<free_port_number_http_server>.n To get a list of all available SAPinst properties, start SAPinst as described above with the option

-p:./sapinst -p

n If you want to use a virtual host name and you have not set the environment variableSAPINST_USE_HOSTNAME [page 70], start SAPinst as follows:./sapinst SAPINST_USE_HOSTNAME=<virtual host name>

Caution

n Make sure that the installation directory is not mounted with NFS, or there might be problemswhen the Java Virtual Machine is started.

n Make sure that your current working directory is not an IM_<OS> directory belonging toanother operating system.For example, the following commands are incorrect and cause an error:$ cd /sapcd2/IM_HPUX_IA64

$ /sapcd2/IM_HPUX_PARISC/sapinst

The following commands are correct:$ cd /sapcd2/IM_HPUX_PARISC

$ /sapcd2/IM_HPUX_PARISC/sapinst

4. In theWelcome screen, choose one of the following installation options:

Note

When you start the installation from a 32-bit installation master DVD, all you see is the folderSoftware Life-Cycle Options on theWelcome screen.

76/140 PUBLIC 05/25/2009


n <Your SAP product> SAP Application Server ABAP <Database> <System Variant>For more information about the available installation options for each system variant, seethe tables below.

n Software Life-Cycle OptionsFor more information about the available options, see table Software Life-Cycle Options below.

Note

n Choose the corresponding installation options from the tree structure exactly in the orderthey appear for each system variant.

n To use global accounts that are configured on a separate host, you have to run the installationoption Operating System Users and Groups before you start the installation

n If required, to install a dialog instance for a central or distributed system, choose:Software Life-Cycle Options Application Server <Database> Dialog Instance

See table Software Life-Cycle Options below.

Installation Options for a Central System

Installation Option Remarks

Central System Installs a complete SAP system including the following instances on one host:n Database instancen Central instanceYou can install a central system in the following parameter modes:n Typical Mode

If you choose Typical, the installation is performed with default settings.As a result, you have to respond to only a small selection of prompts.If you want to change any of the default settings, you can do so on theParameter Summary screen.

n Custom ModeIf you choose Custom, you are prompted for all parameters. At the end, youcan still change any of these parameters on the Parameter Summary screen.

NoteIf you change a parameter with the Revise button on the Parameter Summaryscreen, the installer takes you to the screen where you can change theparameter. Depending on the changes, the installer might guide youthrough other screens containing default parameters that it has alreadyprocessed. This might also happen if you press Back instead of Next on thescreen

NoteYou require at least usage type AS Java or AS ABAP. You can choose theusage types on the screen SAP System > Software Units.

05/25/2009 PUBLIC 77/140


Installation Options for a Distributed System


Global Host Preparation Mandatory step in installing a distributed SAP system withusage types or software units based on AS ABAP.Prepares the SAP global host for your SAP system by doingthe following:n Preparing the file systemn Creating the profilesn Installing the executables

Database Instance Mandatory step in installing a distributed SAP system.Installs a database instance.You must have already completed the Global Host Preparation.

Central Instance Mandatory step in installing a distributed SAP system onseveral hosts.Installs a central instance.

NoteYou require at least usage type AS Java or AS ABAP. You canchoose the usage types or software units on the screen SAPSystem > Software Units.

You must have finished the database instance installation.

Installation Options for a High Availability System


Central Services Instancefor ABAP (ASCS)

Installs a central services instance for ABAP (ASCS) and prepares the SAPglobal host

Database Instance Installs a database instance

Central Instance Installs a central instance

Dialog Instance Installs a dialog instance

NoteYou might need to install dialog instances on 32-bit operating systems if youwant to use 32-bit SAP NetWeaver components, such as Adobe documentservices. However, first check whether such 32-bit components can runon 64-bit operating systems. If so, we recommend running these 32-bitcomponents on a 64-bit operating system. If not, you can install an SAPdialog instance on 32-bit operating systems to run these components. For allother SAP instances, you must use 64-bit systems.

78/140 PUBLIC 05/25/2009


Software Life-Cycle Options


Additional Preparation Options These preparation tasks comprise:n Operating System Users and Groups

Allows you to use global accounts that are configured on a separatehost.

CautionPerform this SAPinst option before you start the installation of yourSAP system.

n Prerequisites CheckChecks your hardware and software requirements before you startthe installation.Otherwise, SAPinst automatically checks the hardware and softwarerequirements during the installation with the Prerequisite Checker. Ifany changes are necessary to the SAP system or operating systemsettings, SAPinst automatically prompts you. For more information,see Running the Prerequisites Checker in Standalone Mode [page 16].

Application Server Choose Application Server <Database> Dialog Instance to install oneor more dialog instance(s) in an already installed SAP system, if required.

NoteYou might need to install dialog instances on 32-bit operatingsystems if you want to use 32-bit SAP NetWeaver components, such asAdobe document services. However, first check whether such 32-bitcomponents can run on 64-bit operating systems. If so, we recommendrunning these 32-bit components on a 64-bit operating system. If not,you can install an SAP dialog instance on 32-bit operating systems torun these components. For all other SAP instances, you must use 64-bitsystems.

LDAP Registration LDAP SupportSets up LDAP support for an application server instance.Choose this option once per SAP system and after you have:

a) Configured the Active Directory on a Windows host by choosingLDAP Registration Active Directory Configuration

You have to configure the directory server only once. Afterwardsall SAP systems that should register in this directory server can usethis setup.

NoteThe option Active Directory Configuration is only available for Windows.

b) Installed an application server instanceFor more information about LDAP and Active Directory, see Integrationof LDAP Directory Services [page 113].

05/25/2009 PUBLIC 79/140



System Copy Choose this service to perform a system copy.For more information, see the system copy guide, which is available at:http://service.sap.com/instguidesnw70 Installation Installation

‒ SAP NetWeaver Systems

Uninstall Choose this service to uninstall your SAP system, standalone engines, oroptional standalone units.For more information, see Deleting an SAP System [page 125].

5. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

Note

To find more information on each parameter during the input phase of the installation, positionthe cursor on the field of the respective parameter and press F1 .

After you have entered all requested input parameters, SAPinst displays the Parameter Summary screen.This screen shows both the parameters that you entered and those that SAPinst set by default.

6. If required, change the displayed parameters as follows:a) Select the parameters you want to change.b) Choose Revise.

SAPinst displays input screens for the selected parameters.c) Enter the new values for the parameters.

7. To start the installation, choose Start.SAPinst starts the installation and displays the progress of the installation.

Note

During the installation of the Oracle database instance, SAPinst stops the installation and promptsyou to install the Oracle database software [page 88].This action is not required if you install a system into an existing database (MCOD).After you have finished the installation of the Oracle database, you continue the database instanceinstallation by choosing OK in the SAPinst GUI of the database instance installation.

8. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after SAPinst has finished.Sometimes these remain in the temporary directory.

Note

If there are errors with SAPinst self-extractor, you can find the self-extractor log filedev_selfex.out in the temporary directory.

80/140 PUBLIC 05/25/2009

http://service.sap.com/instguidesnw70

http://service.sap.com/instguidesnw70


Recommendation

We recommend that you keep all installation directories until you are sure that the system iscompletely and correctly installed.

9. We recommend that you delete all files in the directory <user_home>/.sdtgui/.10. If you have copied installation DVDs to your hard disk, you can delete these files when the

installation has successfully completed.

More InformationIf you have problems during the installation, see Troubleshooting with SAPinst [page 125].

4.3.2 Using SAPinst GUI

The following table shows the most important functions that are available in SAPinst GUI:

SAPinst GUI Functions

Input Type Label Description

Function key F1 Displays detailed information about each inputparameter

Menu option File Exit Stops the SAPinst GUI, but SAPinst and the GUIserver continue running

NoteIf you need to log off during the installation fromthe host where you control the installation withSAPinst GUI, the installation continues while youare logged off. You can later reconnect to the sameSAPinst installation from the same or another host.For more information, see Starting SAPinst GUISeparately [page 85].

Menu option SAPinst Log Browser Displays the Log Viewer dialogThis dialog enables you to access the following logfiles directly:n Installation log (sapinst_dev.log)n Log files from the SAPinst GUI serverThese log files might help you during troubleshootingwith SAPinst [page 125].

05/25/2009 PUBLIC 81/140


Input Type Label Description

Menu option SAPinst Cancel Cancels the installation with the following options:n Stop

Stops the installation (SAPinst GUI, SAPinst, andthe GUI server) without further changing theinstallation filesYou can restart and continue the installationlater from this point.

n ContinueContinues the installation

Message button Retry Performs the installation step again (if an error hasoccurred)

Message button Stop Stops the installation without further changing theinstallation filesYou can continue the installation later from thispoint.

Message button Continue Continues with the option you chose previously

4.3.3 Interrupted Installation with SAPinst

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

n An error occurred during the Define Parameters or Execute phase:SAPinst does not abort the installation in error situations. If an error occurs, the installation pausesand a dialog box appears. The dialog box contains a short description of the choices listed in thetable below as well as a path to a log file that contains detailed information about the error.

n You interrupted the installation by choosing Cancel in the SAPinstmenu.

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeatingany of the previous steps.This is possible because SAPinst records the installation progress in thekeydb.xml file.We recommend that you view the entries in the log files, try to solve theproblem, and then choose Retry.If the same or a different error occurs, SAPinst displays the same dialogbox again.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, andthe GUI server.SAPinst records the installation progress in the keydb.xml file. Therefore,you can continue the installation from the point of failure withoutrepeating any of the previous steps (see the procedure below).

82/140 PUBLIC 05/25/2009


Option Definition

Continue SAPinst continues the installation from the current point.

View Log Access installation log files.

Note

You can also terminate SAPinst by choosing Ctrl + C . However, we do not recommend that youuse Ctrl + C , because this kills the process immediately.

ProcedureThis procedure describes the steps to restart an installation, which you stopped by choosing Stop, orto continue an interrupted installation after an error situation.

1. Log on to your local UNIX host as user root.

Caution


2. Mount your Installation Master DVD.

Note

Mount the DVD locally. We do not recommend using Network File System (NFS).

3. Enter the following commands:cd <Installation_Master_DVD>/IM_<OS>

./sapinst

4. From the tree structure in theWelcome screen, select the installation service that you want tocontinue and choose Next.

Note

If there is only 1 component to install, theWelcome screen does not appear.

TheWhat Do You Want to Do? screen appears.5. In theWhat Do You Want to Do? screen, decide between the following alternatives and confirm

with OK:

05/25/2009 PUBLIC 83/140


Alternative Behavior

Run a New Option SAPinst does not continue the interrupted installation option.Instead, it moves the content of the old installation directory and allinstallation-specific files to a backup directory. Afterwards, you can nolonger continue the old installation option.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds>.

Examplelog_01_Oct_2008_13_47_56

Continue with the Old Option SAPinst continues the interrupted installation option from the point offailure.

4.3.4 Performing a Remote Installation with SAPinst

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and theGUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is thehost from which you control the installation with SAPinst GUI.Alternatively you can use an X server for Microsoft Windows or other remote desktop tools suchas VNC Viewer or NX Server / NX Client ‒ offered by various vendors or open source ‒ for remoteaccess to SAPinst GUI on Windows workstations. We recommend you use the Hummingbird ExceedX Server, which we use to validate installations with SAPinst. For more information, see SAP Note1170809.

Caution

The behavior of SAPinst has changed compared to previous versions. SAP no longer delivers anyJCE policy archives within the SAP Java Virtual Machine (SAP JVM). You have to download therequired Java Cryptography Extension (JCE) policy zip file from SAP on the remote host. For moreinformation, see SAP Note 1238121.

Prerequisites

n The remote host meets the prerequisites as described in Prerequisites before Starting SAPinst [page 70].n 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>.

Procedure

1. Log on to your remote host as user root.

84/140 PUBLIC 05/25/2009




Caution


2. Mount the Installation Master DVD.3. Download the JCE policy zip file from SAP as described in SAP Note 1240081.4. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive

as follows:

Shell Used Command

Bourne shell (sh) JCE_POLICY_ZIP=<policy zip archive>

export JCE_POLICY_ZIP

C shell (csh) setenv JCE_POLICY_ZIP <policy zip archive>

Korn shell (ksh) export JCE_POLICY_ZIP=<policy zip archive>

5. Enter the following commands:cd <mountpoint_of_Installation_Master_DVD>/IM_<OS>

./sapinst -nogui

For more information about SAPinst, see Running SAPinst on UNIX [page 75].SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following atthe command prompt:guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation.

6. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 85].

4.3.5 Starting SAPinst GUI Separately

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUIseparately in the following cases:

n You have logged off from SAPinst.If you logged off during the installation and you later want to reconnect to the installation while itis still running, you can start SAPinst GUI separately.

n You want to perform a remote installation [page 84].If SAPinst GUI runs on a different host from SAPinst and the GUI server, you have to start SAPinstGUI separately on the local host.

05/25/2009 PUBLIC 85/140



Caution

The behavior of SAPinst has changed compared to previous versions. SAP no longer delivers any JCEpolicy archives within the SAP JVM. You have to download the required JCE policy zip file from SAPon the local host. For more information, see SAP Note 1238121.

Starting SAPinst GUI on Windows

1. Log on as a member of the local administrators group.2. Download the JCE policy zip file from SAP as described in SAP Note 1240081.3. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive

by entering the following command:set JCE_POLICY_ZIP=<policy zip archive>

4. Insert the SAP Installation Master DVD into your DVD drive.5. Change to the directory of the sapinst executables:

<DVD drive>:\IM_WINDOWS_<platform>

Note

If you want to start SAPinst GUI on a Windows 32-bit operating system, change to the followingdirectory:<Installation_Master_DVD>\IM_WINDOWS_I386

6. Start SAPinst GUI by double-clicking sapinstgui.exeSAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local hostas default.If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and theSAP Installation GUI Connection dialog appears.In this case, enter the name of the host on which SAPinst is running and choose Log on.The first dialog of the installation appears and you can perform the remote installation fromyour local host.

Note

Optionally you can start sapinstgui.exe with the following parameters:n host=<host name>, where <host name> is the host name of the installation host

n port=<nr>, where <nr> is the port number for the connection to the GUI server

n -accessible enables accessibility modeExample:./sapinstgui.exe host=lsi1209 port=3000 -accessible

Starting SAPinst GUI on UNIX

1. Log on as user root.

86/140 PUBLIC 05/25/2009




Caution


2. Download the JCE policy zip file from SAP as described in SAP Note 1240081.3. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive

as follows:

Shell Used Command

Bourne shell (sh) JCE_POLICY_ZIP=<policy zip archive>

export JCE_POLICY_ZIP

C shell (csh) setenv JCE_POLICY_ZIP <policy zip archive>

Korn shell (ksh) export JCE_POLICY_ZIP=<policy zip archive>

4. Mount your Installation Master DVD.

Note

Mount the DVD locally. We do not recommend that you use Network File System (NFS).

5. Change to the directory of the sapinst executables:<mountpoint_of_Installation_Master_DVD>/IM_<OS>

Note

If you want to start SAPinst GUI on a Linux 32‒bit platform, change to the following directory:<mountpoint_of_Installation_Master_DVD>/IM_LINUX_I386

6. Start SAPinst GUI by executing ./sapinstguiSAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local hostas default.If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and theSAP Installation GUI Connection dialog appears.In this case, enter the name of the host on which SAPinst is running and choose Log on.The first dialog of the installation appears and you can perform the remote installation fromyour local host.

05/25/2009 PUBLIC 87/140


4 Installation4.4 Oracle Database Software Installation

Note

Optionally, you can start sapinstgui with the following parameters:n host=<host name>, where <host name> is the host name of the installation host

n port=<nr>, where <nr> is the port number for the connection to the GUI server

n - accessible enables accessibility modeExample:./sapinstgui host=lsi1209 port=3000 -accessible

4.3.6 Entries in the Services File Created by SAPinst

After the installation has finished successfully, SAPinst has created the following entries in/etc/services:sapdpXX = 32XX/tcp

sapdpXXs = 47XX/tcp

sapgwXX = 33XX/tcp

sapgwXXs = 48XX/tcp

sapms<SAPSID> = 36NN/tcp (unless you specified another value during the installation)

Note

n XX is the instance number. The ports are created for all instance numbers, regardless of whichinstance number you specified during the installation.NN is the number of the instance in which the message server runs. In a central or distributedsystem, this is the central instance (DVEBMGS<nn>), in a high-availability system, this is the ABAPcentral services instance (ASCS<nn>).For more information about instance numbers, see the table SAP System Instances, Hosts, and Ports inBasic SAP System Parameters [page 33].

n If there is more than 1 entry for the same port number, this is not an error.

4.4 Oracle Database Software Installation

SAPinst prompts you to install the Oracle database.Proceed as follows to install the Oracle database software:

Process Flow

1. You update SAP-specific files in the Oracle stage area [page 89].2. You perform steps for the AIX operating system [page 89]3. You run the Oracle Universal Installer [page 90]

88/140 PUBLIC 05/25/2009


4. You install the current patch set [page 92]5. You install required interim patches [page 92]

4.4.1 Updating SAP-Specific Files in the Oracle Staging Area

SAPinst extracts the Oracle RDBMS software to the staging area, usually/oracle/stage/102_64/database.The SAP folder located in /oracle/stage/102_64/database contains SAP-specific scripts as wellas the response files.Before starting the Oracle software installation, you need to update this SAP folder so that the newestversions of the scripts or response files are used.

Procedure

1. Rename the original SAP folder by performing one of the following:

n mv /oracle/stage/102_64/database/Disk1/SAP

/oracle/stage/102_64/database/Disk1/SAP_ORIG

n mv /oracle/stage/102_64/database/SAP

/oracle/stage/102_64/database/SAP_ORIG

2. Download the file RDBMS_SAP_64.zip attached to SAP Note 819830 and copy it to a temporarylocation such as /tmp.

3. Extract the zip file by performing one of the following:

n cd /oracle/stage/102_64/database

unzip /tmp/RDBMS_SAP.zip

n cd /oracle/stage/102_64/database/Disk1

unzip /tmp/RDBMS_SAP.zip

You should now see the directory SAP extracted with the updated version of SAP-specific files.

4.4.2 Performing Steps for the AIX Operating System

To install the Oracle database software on the AIX operating system, you need to run the rootpre.shscript to adapt the AIX kernel and also execute a command as the root user.

PrerequisitesIf several Oracle instances run on one computer, you must shut these down before adapting thekernel.

Procedure

1. Run the rootpre.sh script as follows:

05/25/2009 PUBLIC 89/140



a) Log on to the system with user ora<dbsid> if you are not already logged on.b) Change to the directory /oracle/stage/102_64/database/Disk1/rootpre using the following

command:cd /oracle/stage/102_64/database/Disk1/rootpre

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

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

e) Log off with the user root:exit

2. Remove any currently unused modules in kernel and library memory by entering the followingcommand as user root:# /usr/sbin/slibclean

4.4.3 Running the Oracle Universal Installer

To install the Oracle database software you run the Oracle Universal Installer (OUI).

Procedure

1. Log on as user ora<dbsid>.Since you are already logged on as user root, you can switch to user ora<dbsid> by entering thefollowing command:su – ora<dbsid>.

2. If you install Oracle database software with Release 10.2.0.1 or 10.2.0.x on a new operating system ora new operating system version, the Oracle Universal Installer might not yet recognize or supportthis operating system. Follow the instructions in SAP Note 980426.

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

Bourne shell (sh) DISPLAY=<host_name>:0.0

export DISPLAY

C shell (csh) setenv DISPLAY <host_name>:0.0

Korn shell (ksh) export DISPLAY=<host_name>:0.0

4. Start the OUI by entering one of the following:

n cd /oracle/stage/102_64/database/Disk1/SAP

./RUNINSTALLER

90/140 PUBLIC 05/25/2009



n cd /oracle/stage/102_64/database/SAP

./RUNINSTALLER

You see a message that a response file is being generated. It might take several minutes before yousee the OUI screen.

5. Respond to the OUI as follows:

Prompt or Condition Action

When you run the OUI for the first time on this host,a dialog box, Specify File Locations Destination..., appears.This dialog box proposes the inventory location as/oracle/oraInventory and the installation groupas dba.

Accept the OUI proposal and continue by choosingNext.

Available Product Components Confirm the default selections by choosing Next.

Product-Specific Prerequisite ChecksThis phase checks if all necessary requirements forinstalling and running the database have been met.

For items that are flagged as warnings or failed,review the cause for the warning or failure on screenand fix the problem if possible.Alternatively you can verify the items manuallyand confirm them by clicking the checkbox. Youcan find details about each check by clicking on therelevant item.

Summary page Check the information on this page and then startthe installation.

When the Install step has completed, a dialog boxappears.

Execute the file $ORACLE_HOME/root.shwith the userroot, and confirm the dialog box by choosing OK.If this is the first time that the Oracle softwarehas been installed on this host, the OUIalso asks you to execute a second script,/oracle/oraInventory/orainstRoot.sh, as the rootuser. Execute this script as well.Continue by choosing Next.

6. At the end of the installation, in case there are any Configuration Assistants that have been startedautomatically (for example, Oracle Net) choose Cancel and terminate the Net Config Assistant.You can ignore messages that some of the config assistants failed to complete successfully.The Installer finishes, reporting that the Oracle installation was successful. It also informsyou about the services that it started. You can find the port numbers for these services in the$ORACLE_HOME/install/portlist.ini file.

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

Note

You can now access the Oracle 10.2 online documentation, which was installed duringthe last step. You can find the entry point to the Oracle online documentation at$ORACLE_BASE/doc/index.htm.

05/25/2009 PUBLIC 91/140


4.4.4 Installing the Current Patch Set

After the Oracle database software installation, you need to install the current Oracle Database10g Release 2 (10.2) patch set.

Prerequisites

n For more information on the latest patch set available for Oracle 10.2 see SAP Note 871735.n For more information about how to install the patch set, see the patch set README file.

Caution

Do not perform any of the post-installation steps mentioned in the patch set README file. Thepost-installation steps are to be performed only on an existing Oracle 10.2 database.At this stage you have only installed the Oracle 10.2 software. The database itself is still not Oracle10.2. Therefore, make sure that you do not perform the post-installation steps mentioned inthe README file.

n You only have to install the latest (that is, the current) patch set.

Procedure

1. Log on at the operating system level with the ora<dbsid> user.2. Download and extract the patch set as described in SAP Note 932251.3. Install the patch set as described on the patch set README file.

4.4.5 Installing Required Interim Patches

After the Oracle database software installation, you need to install required interim patches, using theOracle tool OPatch. You need these interim patches in addition to the current patch set.

Prerequisites

n Make sure you have already installed the current patch set [page 92].n Check SAP Note 871096 to find the list of required patches to be installed.n Check SAP Note 839182 for instructions on how to use OPatch.

Procedure

1. Log on at the operating system level as the ora<dbsid> user.2. Install the patches, following the instructions in SAP Note 839182.

92/140 PUBLIC 05/25/2009







Note

You can apply the patches in any order.We recommend that you first copy the patches to a directory called ora_patches in $ORACLE_HOME.

3. After all the patches have been successfully applied, you can query the status with the followingcommand:$ORACLE_HOME/OPatch/opatch lsinventory

This command lists all the patches that have been applied to the software installation.

05/25/2009 PUBLIC 93/140

5 Post-Installation

5 Post-Installation

Note

In a central system, all mandatory instances are installed on one host. Therefore, if you are installinga central system, you can ignore references to other hosts.

You perform the following post-installation steps, which are described in more detail in the linkedsections:

1. If required, you perform a full installation backup [page 107] immediately after the installation has finished.2. You check whether you can log on to the application server [page 96].

Note

In a distributed or high-availability system you check whether you can log on to every instance ofthe SAP system that you installed.

3. You ensure user security [page 96].4. You install the SAP license [page 99].

5.


If you installed a High Availability system, you set up the licenses for high availability [page 99].End of: HA (UNIX)

6. You apply the latest kernel and Support Packages [page 100].7. You configure the remote connection to SAP support [page 101].8. You install the SAP Online Documentation [page 101].9. You perform initial ABAP configuration [page 101].10. On the database instance host, you perform the Oracle-specific post-installation steps [page 105].11. To connect your SAP system to an existing central system landscape directory (SLD), you configure

the connection to a central System Landscape Directory (SLD) [page 106]12. You implement ERP ABAP Add-On Components [page 106].13. You perform the client copy [page 106]14. You perform a full backup of the installation [page 107].

05/25/2009 PUBLIC 95/140

5 Post-Installation5.1 Logging On to the Application Server

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

ABAP Users

User User Name Client

SAP* 000, 001, 066SAP system user

DDIC 000, 001

Prerequisites

n The SAP system is up and running.n You have already installed a front end.

Logging On to the ABAP Application Server

1. Start SAP Logon on the host where you have installed the front end as follows:n SAP GUI forWindows:

Choose Start All Programs SAP Front End SAP Logon .n SAP GUI for Java:

Choose Start All Programs SAP Clients SAP GUI for Java<Release> .

Note

You can alternatively enter the command guilogon in the SAP GUI installation directoryto start SAP GUI for Java.

The SAP Logon appears.2. Create a logon entry for the newly installed system in the SAP Logon.

For more information about creating new logon entries, press F1 .3. When you have created the entry, log on as user SAP* or DDIC.

5.2 Ensuring User Security

You need to ensure the security of the users that SAPinst created during the installation. The tablesbelow at the end of this section list these users:

n Operating system usersn SAP system users

96/140 PUBLIC 05/25/2009

5 Post-Installation5.2 Ensuring User Security

During the installation, SAPinst by default assigned the master password to all users created duringthe installation unless you specified other passwords.If you change user passwords, be aware that SAP system users might exist in multiple SAP systemclients (for example, if a user was copied as part of the client copy). Therefore, you need to change thepasswords in all the relevant SAP system clients.

Caution

SAPinst applied the master password to users SAP* and DDIC only for SAP system clients 000 and 001,but not to users SAP*, DDIC, and EARLYWATCH in client 066.Instead, SAPinst always assigns the following passwords to these users in client 066:SAP*: 06071992EARLYWATCH: supportSee alsoMaster Password in Basic SAP System Parameters [page 31].

Recommendation

User ID and password are encoded only when transported across the network. Therefore, werecommend 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 protocolsdialog and RFC.For more information, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Security Network and Transport Layer Security

Caution

Make sure that you perform this procedure before the newly installed SAP system goes intoproduction. For security reasons, you also need to copy the installation directory to a separate,secure location ‒ such as a DVD ‒ and then delete the installation directory.

For the users listed below, take the precautions described in the relevant SAP security guide, whichyou can find at http://service.sap.com/securityguide:

Operating System UsersAfter the installation, operating system users for SAP system and database are available as listedin the following table:

05/25/2009 PUBLIC 97/140




http://service.sap.com/securityguide



5 Post-Installation5.2 Ensuring User Security

Operating System and Database Users

User User Name Comment

<sapsid>adm SAP system administratorOperating system user

ora<dbsid> Oracle database administrator (thatis, the owner of the database files)

SAP<SCHEMA_ID> Oracle database owner (that is, theowner of the database tables)

SYSTEM Oracle standard database user

SYS Oracle standard database user

OUTLN Oracle standard database user

Oracle database user

DBSNMP Oracle standard database user

SAP System UsersAfter the installation, ABAP system users are available. The following table shows these users togetherwith recommendations on how you can ensure the security of these users.

ABAP Users

User User Name Comment

SAP* User exists in at least SAP systemclients 000, 001, and 066

CautionThis user has extensiveauthorizations. Make surethat you assign a secure password.

DDIC User exists in at least SAP systemclients 000 and 001

CautionThis user has extensiveauthorizations. Make surethat you assign a secure password.

EARLYWATCH User exists in at least SAP systemclient 066

SAP system user

SAPCPIC User exists in at least SAP systemclients 000 and 001

More InformationFor more information about managing ABAP users, see:

98/140 PUBLIC 05/25/2009

5 Post-Installation5.3 Installing the SAP License

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAPNetWeaver Library Security Identity Management User and Role Administration of AS ABAP

5.3 Installing the SAP License

You must install a permanent SAP license. When you install your SAP system, a temporary licenseis automatically installed. This temporary license allows you to use the system for only 4 weeksfrom the date of installation.

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

ProcedureInstall the SAP license as described in the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library Technology Consultant’s Guide Cross-NetWeaver Configurations SAP License Key


If you have installed a high-availability system, proceed as described in High Availability: Setting UpLicenses [page 99].End of: HA (UNIX)

More InformationFor more information about SAP license keys, see http://service.sap.com/licensekey.

5.4 High Availability: Setting Up Licenses

Every SAP system needs a central license, which is determined by the environment of the messageserver. Since SAP’s high-availability (HA) solution stipulates 2 or more cluster nodes (host machines)where the message server is enabled to run, you have to order as many license keys [page 99] as youhave cluster nodes.When we receive confirmation from your vendor that you are implementing a switchoverenvironment, we provide the required license keys for your system, 1 key for each machine.SAP has implemented a license mechanism for transparent and easy use with switchover solutionsand clustered environments. Your customer key is calculated on the basis of local information on themessage server host. This is the host machine where the ABAP central services instance (ASCS) runs.There is no license problem when only the database is switched over.

05/25/2009 PUBLIC 99/140







http://service.sap.com/licensekey



5 Post-Installation5.5 Applying the Latest Kernel and Support Packages

PrerequisitesThe SAP system is up and running.

Procedure

1. Make sure that the ABAP central services instance (ASCS) on the primary host, node A, is running.2. To find the hardware ID of the primary host, log on to any application server instance of the

SAP system and call transaction SLICENSE.3. 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.

4. To obtain the two license keys, enter the hardware IDs for the primary and backup hosts at:http://service.sap.com/licensekey

5. To import the files containing the two licenses, log on to any application server instance of theSAP system and call transaction SLICENSE.

6. Perform a switchover of the ABAP central services instance (ASCS) to another node in the clusterand repeat the previous step.Repeat this for all remaining nodes in the cluster.

ResultThe license is no longer a problem during switchover. This means you do not need to call saplicensein your switchover scripts.

5.5 Applying the Latest Kernel and Support Packages

You use this procedure to apply the latest kernel and Support Packages for your SAP system from SAPService Marketplace.

PrerequisitesMake sure that you read the release notes for your SAP system before you apply Support Packages.The release notes might include information about steps you have to perform after you have appliedthe Support Packages. For more information, see http://service.sap.com/releasenotes.

ProcedureDownload and apply the latest kernel and Support Packages as described in the SAP NetWeaver 7.0 ‒Support Package Stack Guide <current version> at http://service.sap.com/maintenancenw70 .For up-to-date release information on Support Package stacks, see SAP Note 849887.You have to apply at least Support Package Stack (SPS) 1 of SAP enhancement package 4 forSAP ERP 6.0.

100/140 PUBLIC 05/25/2009







http://service.sap.com/maintenancenw70


5 Post-Installation5.6 Configuring Remote Connection to SAP Support

5.6 Configuring Remote Connection to SAP Support

SAP offers its customers access to support and to a number of remote services such asthe SAP EarlyWatch service or the SAP GoingLive service. Therefore, you have to set up aremote network connection to SAP. For more information, see SAP Service Marketplace athttp://service.sap.com/remoteconnection.

5.7 Installing the SAP Online Documentation

SAP currently provides an HTML-based solution for the online documentation, including theApplication Help, Glossary, Implementation Guide (IMG), and Release Notes. You can display thedocumentation with a Java-compatible Web browser on all front-end platforms supported by SAP.You can always find the up-to-date SAP online documentation at http://help.sap.com.

ProcessInstall the SAP online documentation in your SAP system as described in the README.TXT filecontained in the root directory of the online documentation DVD, delivered as part of the installationpackage.

5.8 Performing Initial ABAP Configuration

When you have installed your SAP ABAP system, you have to perform the following initialconfiguration steps:

n Perform a consistency checkn Configure the transport management systemn Perform basic operationsn Configure system parametersn Configure the number of work processesn Configure kernel parametersn Install languages and performing language transportn Configure the integrated Internet Transaction Server (ITS)n Make your newly installed SAP system known to your SAP Solution Managern Maintain your company address for initial usersn Configure business applications

For more information, see the appropriate sections below.

05/25/2009 PUBLIC 101/140

http://service.sap.com/remoteconnection



http://help.sap.com

5 Post-Installation5.8 Performing Initial ABAP Configuration

PrerequisitesYou have logged on to the ABAP application server as described in Logging On to the Application Server[page 96].

Performing a Consistency CheckWe recommend that you check the consistency of the newly installed SAP ABAP system. Whenlogging on to the system for the first time, you need to trigger a consistency check manually. Thefunction is then called automatically whenever you start the system or an application server.This checks the following:

n Completeness of installationn Version compatibility between the SAP release and the operating system

The initial consistency check determines whether:l The release number in the SAP kernel matches the release number defined in the database

systeml The character set specified in the SAP kernel matches the character set specified in the database

systeml 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, andTFDIR.

n Accessibility of the message servern Availability of all work process typesn Information about the enqueue server and the update service

To perform a consistency check, you can either call transaction SICK (SAP initial consistency check)or choose:Tools Administration Administration Installation Check from the menu (?).

For more information, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySystem Management Tools for Monitoring the System Consistency Check

Configuring the Transport Management SystemYou have to perform some steps to be able to use the Transport Management System.

1. Perform post-installation steps for the transport organizer:a) Call transaction SE06.b) Select Standard Installation.c) Choose Perform Post-Installation Actions.

2. Call transaction STMS in the ABAP system to configure the domain controller in the TransportManagement System (TMS).

102/140 PUBLIC 05/25/2009





3.


In TPPARAM, set <SAPSID>/dbhost to the virtual host name of the DB instance.This lets you use the transport system for the normal maintenance of ABAP programs, but stillallows transparent operation in the event of a switchover in your high-availability system.End of: HA (UNIX)

For more information, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySoftware Life Cycle Management Software Logistics Change and Transport System

Performing Basic Operations

1. Go to the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

SAP NetWeaver Library SAP NetWeaver by Key Capability2. Choose the relevant sections to perform the following operations:

Operation Section in SAP Documentation

Set up operation modes ‒transaction RZ04

Solution Life Cycle Management by Key Capability System ManagementConfiguration Operation Modes

Set up logon groups ‒transaction SMLG

Solution Life Cycle Management by Key Capability System ManagementConfiguration Logon Load Balancing SAP Logon

Set up administrators Solution Life Cycle Management by Key Capability SystemManagement BackgroundProcessing Authorizations for Background Processing

Schedule background jobs Solution Life Cycle Management by Key Capability System ManagementBackground Processing

Install a printer Solution Life Cycle Management by Key Capability System Management SAPPrinting Guide

Configure the system log Tools for Monitoring the System System log Configuring the System Log

Configuring System ParametersFor more information about system profiles, which is where work processes and profile parametersare defined, and how to configure them, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySystem Management Configuration Profiles

Checking the Configured Number of Work ProcessesSAPinst installs ABAP systems with a minimum number of work processes. This is only an initialconfiguration so that you can start working after the installation. It is not detailed enough for a

05/25/2009 PUBLIC 103/140











production system because the optimal number of each type of work process depends on the systemresources and on the number of users working in each ABAP system application.For more information about how many work processes to configure and about how to set thenumber, see SAP Notes 39412 and 9942.

Configuring Kernel ParametersTo configure your kernel parameters, follow the recommendations in SAP Notes 146289 and 835474.

Installing Languages and Performing Language Transports

n Install languages using transaction I18N:l If you want to use English only, you must activate the default language settings once.l If you want to use languages other than English, you must install them and activate the

language settings.For more information about configuring the language settings, see the online documentation intransaction I18N at I18N Menue I18N Customizing .

n Perform language transport using transaction SMLT as described in the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by KeyCapability Software Life Cycle Management Software Logistics Change and Transport System LanguageTransport

Using and Configuring the SAP ITS Integrated ICMThe SAP Internet Transaction Server (SAP ITS) is integrated in the SAP NetWeaver Application ServerABAP (AS ABAP) as an Internet Communication Framework (ICF) service. You can access this, likeother services, with the Internet Communication Manager (ICM). With the SAP ITS integrated inAS ABAP, the Web browser now communicates directly with the SAP system. Furthermore, allSAP ITS-related sources, such as service files, HTML templates, or MIME files, are now stored inthe database of the system.The SAP ITS supports the following functions:

n SAP GUI for HTML

n Internet Application Component (IAC) runtime or Web Transaction technology

For more information about how to configure the integrated SAP ITS, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAPTechnology UI Technology Web UI Technology SAP ITS in the SAP NetWeaver Application ServerConfiguration

104/140 PUBLIC 05/25/2009











5 Post-Installation5.9 Performing Oracle-Specific Post-Installation Steps

Making your Newly Installed SAP System Known to your SAP SolutionManagerMake your newly installed SAP system known to your SAP Solution Manager as described in theSAP Library at:http://help.sap.com SAP Solution Manager SAP Solution Manager 7.0 <current SP> SAP Solution

Manager Basic Settings Solution Manager System Landscape Create Systems

Maintaining Your Company Address for Initial UsersMaintain your company address in your ABAP system using transaction SU01 as described in theSAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability BusinessServices Business Address Services (BC-SRV-ADR) Addresses in User Administration Maintenance of AddressData

Note

You must maintain your company address to create ABAP system users.

Configuring Business ApplicationsPrepare the SAP system for using business applications, which includes customizing the ABAP systemand the business components, as described in the SAP Library at http://help.sap.com/nw70 SAPNetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver byKey Capability Solution Life Cycle Management by Key Capability Customizing

5.9 Performing Oracle-Specific Post-Installation Steps

You have to perform the following Oracle-specific post-installation steps:

Security Setup for the Oracle ListenerIf the Oracle security setup defined by the standard installation is not restrictive enough for yourpurposes, see SAP Note 186119 to configure the Oracle listener to accept only connections fromspecific hosts.

Checking the Recommended Oracle Database ParametersWhen installing the Oracle database, a standard database parameter set is used. To take into accountthe size and configuration of your SAP system and to enable new Oracle features, check and apply theparameter settings as described in SAP Note 830576.

Configuring and Operating the Oracle DatabaseYou have to configure your Oracle database before you start operating it with the SAP system.

05/25/2009 PUBLIC 105/140

http://help.sap.com









5 Post-Installation5.10 Configuring the Connection to a Central System Landscape Directory

For information about Oracle database configuration and administration, see the documentationin the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including EnhancementPackage 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by KeyCapability Platform-Wide Services Database Support Oracle .

5.10 Configuring the Connection to a Central SystemLandscape Directory

For each system in your landscape that reports data to a central System Landscape Directory (SLD),you have to configure a corresponding SLD data supplier.

ProcedureConfigure the SLD data suppliers and the API for the SLD as described in the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySoftware Life Cycle Management System Landscape Directory Configuring Systems to Connect to SLD

More InformationThis documentation is also available in PDF form in the User Manual ‒ SLD of SAP NetWeaver 7.0 athttp://www.sdn.sap.com/irj/sdn/nw-sld.

5.11 Implementing ERP ABAP Add-On Components

You can install several Add-On Components to your ERP ABAP system.

ProcedureYou can find a detailed description on how to implement each available ERP Add-On Component inthe related SAP Notes on SAP Service Marketplace at https://service.sap.com/erp-inst SAPERP 6.0 SAP Notes .

5.12 Performing the Client Copy

SAPinst creates three ABAP clients during the installation, client 000, client 001, and client 066.Client 000 is the SAP reference client for ABAP.Use client 000 as source client for the client copy.

106/140 PUBLIC 05/25/2009







http://www.sdn.sap.com/irj/sdn/nw-sld

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



5 Post-Installation5.13 Performing a Full Installation Backup

Procedure

1. Maintain the new client with transaction SCC4.2. Activate kernel user SAP*:

a) Set the profile parameter login/no_automatic_user_sapstar to 0.b) Restart the application server.

3. Log on to the new client with kernel user SAP* and password PASS.4. Copy the client with transaction SCCL and profile SAP_CUST.5. Check the log files with transaction SCC3.6. Create the required users. These users must have at least the authorizations required for user

administration and system administration. Create a user SAP* with all required authorizationsfor this user. If you want to have other users for system administration, you can also create userSAP* without authorizations.

7. Deactivate kernel user SAP*:a) Reset login/no_automatic_user_sapstar to 1.b) Restart the application server.

More InformationFor more information about the client copy and about how to perform it, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySoftware Lifecycle Management Software Logistics Change and Transport System BC ‒ Client Copy and Transport

5.13 Performing a Full Installation Backup

You must perform a full offline backup at the end of the installation. This procedure also describeshow to use the back-up data for a restore.

Caution

Make sure that you fully back up your database so that you can recover it later if necessary.

Prerequisites

n If required, you have completed client maintenance, such as the client copy [page 106].n You have logged on [page 96] as user <sapsid>adm and stopped the SAP system and database [page 121].

ProcedureThe UNIX commands used in this procedure work on all hardware platforms. For more informationabout operating system-specific backup tools, see your operating system documentation.

05/25/2009 PUBLIC 107/140




5 Post-Installation5.13 Performing a Full Installation Backup

Backing Up the Installation

Note

The following only applies to a standard installation.

1. Back up the following file systems:

n /usr/sap/<SAPSID>

n /usr/sap/trans

n <sapmnt>/<SAPSID>

n Home directory of the user <sapsid>admn All database-specific directoriesProceed as follows:a) Log on as user root.b) Manually create a compressed tar archive that contains all installed files:n Saving to tape:

tar —cf — <file_system> | compress —c > <tape_device>

n Saving to the file system:tar —cf — <file_system> | compress —c > ARCHIVENAME.tar.Z

2. Back up the operating system using operating system means.This saves the structure of the system and all configuration files, such as file system size, logicalvolume manager configuration and database configuration data.

Restoring Your Backup

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

Caution

Check for modifications to the existing parameter files before you overwrite them when restoringthe backup.

1. Log on as user root.2. Go to the location in your file system where you want to restore the backup image.3. Execute the following commands to restore the data:n Restoring the data from tape:

cat <tape_device> | compress —cd | tar —xf —

n Restoring the data from the file system:cat ARCHIVENAME.tar.Z | compress —cd | tar —xf —

Performing a Full Database Backup

1. Configure your third-party backup tool, if used.2. Perform a full database backup (preferably offline).

108/140 PUBLIC 05/25/2009

5 Post-Installation5.14 Accessing Configuration Documentation in SAP Solution Manager

If you use BR*TOOLS for the backup, refer to BR*Tools for Oracle DBA in the SAP Database Guide: Oracle(BC-DB-ORA-DBA). This documentation is available in the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key CapabilityPlatform-Wide Services Database Support Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA)

5.14 Accessing Configuration Documentation in SAP SolutionManager

To access configuration documentation in SAP Solution Manager, you have to connect yournewly-installed SAP system to SAP Solution Manager.

Note

For SAP NetWeaver 7.0 usage types you can also find configuration documentation in the TechnologyConsultant’s Guide at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library Technology Consultant’s Guide

Prerequisites

n You have installed an SAP Solution Manager system as described in the documentation InstallationGuide ‒ SAP Solution Manager 7.0 on <OS>: <Database>.

n You have connected your SAP system to SAP Solution Manager as described in the documentationConfiguration Guide ‒ SAP Solution Manager <Current Release> as of <Current SP Level>.

You can find this documentation at:http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0

Procedure

1. Log on to your SAP Solution Manager system.2. To be able to access configuration documentation, create a project as follows:

a) Create your project with transaction SOLAR_PROJECT_ADMIN for project administration.b) Connect your SAP system to SAP Solution Manager with transaction SMSY for the SAP Solution

Manager system landscape.c) Create a project structure and add the required scenarios for your SAP system to your project

structure with the Business Blueprint transaction SOLAR01,d) Add your SAP system configuration structures to your project structure with the configuration

transaction SOLAR02.For more information about creating projects, assigning scenarios to projects, and creatingconfiguration structures, see:

05/25/2009 PUBLIC 109/140










5 Post-Installation5.14 Accessing Configuration Documentation in SAP Solution Manager

http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) EnglishSAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by KeyCapability SAP Solution Manager Using the SAP Solution Manager in Projects

3. Go to the project structure folder <project name> using transaction SOLAR02.4. Access configuration documentation for SAP NetWeaver usage types at Configuration Structure

SAP NetWeaver 7.0 .5. Access configuration documentation for all areas of SAP ERP at Configuration Structure SAP

ERP <release> .Here you can also find documentation about how to use the Extended ConfigurationManagement(XCM) Administration Tool.

ResultYou can now configure your SAP system according to the configuration documentation in SAPSolution Manager.

110/140 PUBLIC 05/25/2009




6 Additional Information

6 Additional Information

The following sections provide additional information about optional preparation, installationand post-installation tasks.There is also a section describing how to delete an SAP system.

Preparation

n Installation of Multiple Components in One Database [page 111]n Integration of LDAP Directory Services [page 113]

Post-Installation

n Starting and stopping the SAP system [page 117].n If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access

[page 124].n Heterogeneous SAP System Installation [page 124]n Troubleshooting [page 125]

Deleting an SAP System or SAP Instance

n Deleting an SAP System [page 125]

6.1 Installation of Multiple Components in One Database

You can installmultiple SAP systems in a single database. This is called Multiple Componentsin One Database (MCOD).

Example

You install an SAP ERP central system and an SAP CRM central system in a single database.

MCOD is available with all SAP components. We are releasing this technology on all the majordatabases for the SAP system, in line with our commitment to deliver platform-independentsolutions.Using this technology is as easy as installing a separate component. No extra effort is required becausethe MCOD installation is fully integrated into the standard installation procedure. MCOD is not anadditional installation service. Instead, it is an option of the database instance installation.With MCOD we distinguish two scenarios:

05/25/2009 PUBLIC 111/140

6 Additional Information6.1 Installation of Multiple Components in One Database

n The installation of an SAP system in a new databasen The installation of an additional SAP system in an existing database

Prerequisites

n For more information about MCOD and its availability on different platforms, seehttp://service.sap.com/mcod.

n We have released MCOD for Unicode installations. A prerequisite is that the MCOD systemcontains Unicode instances only. SAP does not support mixed solutions.

n Improved sizing requiredIn general, you calculate the CPU usage for an MCOD database by adding up the CPU usage foreach 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 theQuick Sizer tool and then adding the requirements together. For more information about theQuick Sizer, see http://service.sap.com/sizing.

Features

n Reduced administration effort

n Consistent system landscape for backup, system copy, administration, and recoveryn Increased security and reduced database failure for multiple SAP systems due to monitoring and

administration of only one databasen Independent upgrade

In an MCOD landscape, you can upgrade a single component independently from the othercomponents running in the same database, assuming that the upgraded component runs onthe same database version. However, if you need to restore a backup, be aware that all othercomponents are also affected.

Note

Special MCOD considerations and differences from the standard procedure are listed where relevantin the installation documentation.

Constraints

Recommendation

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 youmix test, development, and production systems in the same MCOD.

n In the event of database failure, all SAP systems running on the single database are affected.n Automated support in an MCOD landscape for the following administrative tasks depends on

your operating system and database:

112/140 PUBLIC 05/25/2009

http://service.sap.com/mcod






6 Additional Information6.2 Integration of LDAP Directory Services

l Copying a single component from an MCOD landscape to another database at database level.l 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 moreinformation, see http://service.sap.com/remoteconnection.

n When you use stopsap in an MCOD system with two central instances, only one central instanceis stopped. Therefore, you must first stop the other SAP system with stopsap R3 to make sure thatthe database is also stopped.

n You cannot install a Unicode SAP system with a non-Unicode SAP system in one database.n For the second SAP system, you must use the same DBSID as for the first SAP system.n 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 tablespacewith BRSPACE or BRTOOLS.

n If you decide to turn off archive log mode during the database load phase of the installation, youneed to plan downtime for all MCOD systems sharing the database.

6.2 Integration of LDAP Directory Services

This section explains the benefits of using the SAP system with the Lightweight Directory AccessProtocol (LDAP) directory and gives an overview of the configuration steps required to use an SAPsystem with the directory.LDAP defines a standard protocol for accessing directory services, which is supported by variousdirectory products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory servicesenables important information in a corporate network to be stored centrally on a server. Theadvantage of storing information centrally for the entire network is that you only have to maintaindata once, which avoids redundancy and inconsistency.If an LDAP directory is available in your corporate network, you can configure the SAP system to usethis feature. For example, a correctly configured SAP system can read information from the directoryand also store information there.

Note

The SAP system can interact with the Active Directory using the LDAP protocol, which defines:

n The communication protocol between the SAP system and the directory

n How data in the directory is structured, accessed, or modified

If a directory other than the Active Directory also supports the LDAP protocol, the SAP system cantake advantage of the information stored there. For example, if there is an LDAP directory on a UNIXor Windows server, you can configure the SAP system to use the information available there. In thefollowing text, directories other than the Active Directory that implement the LDAP protocol arecalled generic LDAP directories.

05/25/2009 PUBLIC 113/140





Caution

This section does not provide information about the use of LDAP directories with the LDAPConnector. For more information about using and configuring the LDAP Connector for an ABAPsystem, see the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (includingEnhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability SecurityIdentity Management User and Role Administration of AS ABAP Configuration of User and Role AdministrationDirectory Services LDAP Connector

PrerequisitesYou can only configure the SAP system for Active Directory services or other LDAP directories ifthese are already available on the network. As of Windows 2000 or higher, the Active Directoryis automatically available on all domain controllers. A generic LDAP directory is an additionalcomponent that you must install separately on a UNIX or Windows server.

FeaturesIn the SAP environment, you can exploit the information stored in an Active Directory or genericLDAP directory by using:

n SAP Logonn The SAP Microsoft Management Console (SAP MMC)n The SAP Management Console (SAP MC)

For more information about the automatic registration of SAP components in LDAP directories andthe benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information inDirectory Services at http://service.sap.com/msplatforms Microsoft Windows ServerFor more information about the SAP MC and about how to configure it to access LDAP Directories,see the documentation SAP Management Console at http://help.sap.com/nw70 SAP NetWeaver 7.0Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key CapabilityApplication Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE EngineAdministration Tools SAP Management Console

SAP Logon

Instead of using a fixed list of systems and message servers, you can configure the SAP Logon in thesapmsg.ini configuration file to find SAP systems and their message servers from the directory. Ifyou configure SAP logon to use the LDAP directory, it queries the directory each time Server or Groupselection 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=

114/140 PUBLIC 05/25/2009




http://service.sap.com/msplatforms







LDAPoptions=

Distinguish the following cases:

n If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For moreinformation, see the SAP system profile parameter ldap/options.

n You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either ofthe following is true:l The client is not located in the same domain forest as the Active Directoryl 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.

n For other directory services, you can use LDAPnode to specify the distinguished name of the SAProot node. For more information, see the SAP system profile parameter ldap/saproot.

SAP MMC

The SAPMMC is a graphical user interface (GUI) for administering andmonitoring SAP systems froma central location. It is automatically set up when you install an SAP system on Windows. If the SAPsystem has been prepared correctly, the SAP MMC presents and analyzes system information thatit gathers from various sources, including the Active Directory.Integrating the Active Directory as a source of information has advantages for the SAP MMC. It canread system information straight from the directory that automatically registers changes to thesystem landscape. As a result, up-to-date information about all SAP application servers, their status,and parameter settings is always available in the SAP MMC.If you need to administer distributed systems, we especially recommend that you use the SAP MMCtogether with Active Directory services. You can keep track of significant events in all of the systemsfrom a single SAP MMC interface. You do not need to manually register changes in the systemconfiguration. Instead, such changes are automatically updated in the directory and subsequentlyreflected in the SAP MMC.If your SAP system is part of a heterogeneous SAP system landscape that comprises systems orinstances both on UNIX andWindows operating systems, you can also use the SAPMMC for operatingand monitoring the instances running on UNIX.

SAP MC

The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems from acentral location. If the SAP system has been prepared correctly, the SAP MC presents and analyzessystem information that it gathers from various sources, including generic LDAP Directory.Integrating a generic LDAP Directory as a source of information has advantages for the SAP MC. Itcan read system information straight from the directory that automatically registers changes to thesystem 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.

05/25/2009 PUBLIC 115/140


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 theActive Directory so that it can store SAP system data.To prepare the directory, you use SAPinst to automatically:

n Extend the Active Directory schema to include the SAP-specific data typesn 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.n Create the root container where information related to SAP is stored

n Control access to the container for SAP data by giving members of the SAP_LDAP group permissionto read and write to the directory

You do this by running SAPinst on the Windows server on which you want to use Active DirectoryServices and choosing <Your SAP product> Software Life-Cycle Options LDAP RegistrationActive Directory Configuration . For more information about running SAPinst on Windows, see thedocumentation Installation Guide — <Your SAP product> on Windows: <Database>.

Note

You have to perform the directory server configuration only once. Then all SAP systems that needto 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 ofthe SAP system by setting some profile parameters in the default profile.To do this, run SAPinst once for your system and choose <Your SAP product> Software Life-CycleOptions LDAP Registration LDAP SupportIf you use a directory server other than Microsoft Active Directory and/or non-Windows applicationservers, you have to store the directory user and password information by using ldappasswdpf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and istherefore 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 aredev_ldap*. The registration is updated every time a component starts.

116/140 PUBLIC 05/25/2009

6 Additional Information6.3 Starting and Stopping SAP System Instances

6.3 Starting and Stopping SAP System Instances

You can start and stop SAP system instances by using the SAP Management Console (SAP MC) [page 117].Apart from using the SAP Management Console (SAP MC) you can also use scripts to start or stopSAP system instances [page 121]

6.3.1 Starting and Stopping SAP System Instances Using theSAP Management Console

You can start and stop all SAP system instances (except the database instance) and the DiagnosticsAgent using the SAP Management Console (SAP MC). You have to start and stop the databaseinstance as described in Starting and Stopping the SAP System Using startsap and stopsap [page 121].

Note

If your newly installed SAP system is part of a heterogeneous SAP system landscape comprisingsystems or instances on Windows platforms, you can also start and stop it from a Windows system orinstance using theMicrosoft Management Console (SAP MMC).For more information about handling the MMC, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySolution Monitoring Monitoring in the CCMS SAP Microsoft Management Console: Windows

Prerequisites

n Make sure that the host where you want to start SAP MCmeets the following requirements:l Java Runtime Environment (JRE) 5.0 is installed.l The browser supports Java.l The browser’s Java plug-in is installed and activated.

n You have logged on to the host as user <sapsid>adm.

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 53 and the host name is saphost06, you enter the following URL:http://saphost06:55313

This starts the SAP MC Java applet.

05/25/2009 PUBLIC 117/140



Note

If your browser displays a security warning message, choose the option that indicates that youtrust the applet.

2. Choose Start.The SAP Management Console appears.By default, the instances installed on the host you have connected to are already added in theSAP Management Console.

Note

If the instances have not been added or if you want to change the configuration to display systemsand instances on other hosts, you have to register your system manually. This is described inRegistering Systems and Instances in the SAP Management Console below.

Starting and Stopping SAP System Instances

Starting SAP Systems or Instances

1. In the navigation pane, open the tree structure and navigate to the system node that you want tostart.

2. Select the system or instance and choose Start from the context menu.3. In the Start SAP System(s) dialog box, choose the required options.4. Choose OK.

The SAP MC starts the specified system or system instances.

Note

The systemmight prompt you for the credentials of the SAP system administrator. To completethe operation, you must have administration permissions. Log in as user <sapsid>adm.

Starting the Instances of a Distributed SAP System Separately

If you need to start the instances of an SAP system separately ‒ for example when you want to starta distributed or a high-availability system ‒ proceed as follows:

1. Start the database instance.

2.


If your system is a high-availability system, start the ABAP central services instanceASCS<Instance_Number>.End of: HA (UNIX)

3. Start the central instance DVEBMGS<Instance_Number>.4. Start dialog instance(s) D<Instance_Number>, if there are any.

118/140 PUBLIC 05/25/2009


Stopping SAP Systems or Instances

1. Select the system or instance you want to stop and choose Stop from the context menu.2. In the Stop SAP System(s) dialog box, choose the required options.3. 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 theoperation, 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 theSAP MC.

Stopping the Instances of a Distributed SAP System Separately

If you need to stop the instances of an SAP system separately ‒ for example when you want to starta distributed or a high-availability system ‒ proceed as follows:

1. Stop dialog instance(s) D<Instance_Number>, if there are any.2. Stop the central instance DVEBMGS<Instance_Number>.

3.


If your system is a high-availability system, stop the ABAP central services instanceASCS<Instance_Number>.End of: HA (UNIX)

4. Stop the database instance.

Registering Systems and Instances in the SAP Management ConsoleYou can extend the list of systems and instances displayed in the SAPMC, so that you canmonitor andadminister all systems and instances from a single console. You can configure the SAP MC startupview to display the set of systems and instances you want to manage.

Prerequisites

The SAP MC is started.

Registering SAP Systems or Instances

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

05/25/2009 PUBLIC 119/140


Note

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

3. Choose Finish.

Registering the Instances of a Distributed SAP System Separately

1. In the SAP MC, choose File New .2. In the New System dialog box, enter the required data and deselect Always show all SAP Instances.3. 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 chooseAdd Application Server from the context menu.

Configuring the SAP MC View

n 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 pane, choose the instance you want the SAP MC to display on startup.3. Choose the << button.4. Choose Apply and then OK.Similarly, you can remove instances from the startup configuration.

n You can save the current configuration in a file:1. Choose File Save Landscape .2. In the Save dialog box, enter the required data.3. Choose Save.

n 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 InformationFor more information about the SAP Management Console, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySolution Monitoring Monitoring in the CCMS SAP Management Console

120/140 PUBLIC 05/25/2009



6.3.2 Starting and Stopping SAP System Instances UsingScripts

You can start and stop SAP system instances by running the startsap and stopsap scripts.You can also use the SAP Management Console (SAP MC) to start or stop the instances of the SAPsystem (see Starting and Stopping SAP System Instances Using the SAP Management Console [page 117]).

Prerequisites

n You have checked the default profile /<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameterlogin/system client and set the value to the correct production system client. For example, theentry must be login/system_client = 001 if your production client is 001.

n You have checked the settings for Java Virtual Machine parameters as described in SAP Note723909.

n You have logged on to the SAP system hosts as user <sapsid>adm.n 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.n 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 startsap or stopsap in the home directory of thecorresponding user.

Caution

If there aremultiple SAP instances on one host ‒ for example, a central instance and a dialoginstance ‒ you must add an extra parameter to the scripts:startsap <instanceID>

stopsap <instanceID>

For example, enter:

Note

The instance name (instance ID) of the central instance is DVEBMGS<Instance_Number>, theinstance name of a dialog instance is D<Instance_Number>.


The instance name of the ABAP central services instance is ASCS<Instance_Number>.End of: HA (UNIX)

Procedure

Starting SAP System Instances

n To start all instances on the central system host, enter the following command:startsap

05/25/2009 PUBLIC 121/140



This checks if the database is already running. If not, it starts the database first.

Note

You can start the database and SAP system separately by entering the following commands:startsap DB


startsap R3 <instance ID of central services instance>

End of: HA (UNIX)

startsap R3 <instance ID of central instance>

startsap R3 <instance ID of dialog instance>

Make sure that you always start the database first because otherwise the other instances cannotstart.

n In a distributed system, proceed as follows:1. On the database host, enter:

startdb

2.


On the central instance host enter:End of: non-HA


On the central services and on the central instance host, enter:End of: HA (UNIX)

startsap

3. For dialog instances, enter the following on the relevant host:startsap R3 <instance ID of dialog instance>

Note

Make sure that the SAP system is up and running before you start or restart dialog instances.

Stopping SAP System Instances

Note

When you use stopsap in a system with Multiple Components in One Database (MCOD) that hastwo central instances, only one central instance and the database shut down. Therefore, you mustfirst stop the other SAP system with stopsap R3 or make sure that it has already been stopped.For more information, see Installation of Multiple Components in one Database [page 111].

n If you have a central system, enter the following to stop all instances on the central system host:stopsap

122/140 PUBLIC 05/25/2009



This stops the central instance and database.End of: non-HA


This stops the central instance, central services instance, and database.End of: HA (UNIX)

Note

You can stop the database and SAP system separately by entering the following commands:stopsap R3 <instance ID of dialog instance>

stopsap R3 <instance ID of central instance>


stopsap R3 <instance ID of central services instance>

End of: HA (UNIX)

stopsap DB


Make sure that you always stop the central instance first because otherwise the database cannotbe stopped.End of: non-HA


Make sure that you always stop the central instance first and the central services instance secondbecause otherwise the database cannot be stopped.End of: HA (UNIX)

n In a distributed system, proceed as follows:1. On the dialog instance host, enter the following command:

stopsap <instance ID of dialog instance>

2.


On the central instance host, enter the following command:End of: non-HA


To stop the central services instance on the central services and on the central instance host,enter the following command:End of: HA (UNIX)

stopsap

3. To stop the database, enter the following command on the database host:stopdb

05/25/2009 PUBLIC 123/140

6 Additional Information6.4 Creating a User for LDAP Directory Access

Caution

Make sure that no SAP instance is running before you enter stopdb on a standalone database server.No automatic check is made.

6.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 theSAP system is running. This permits the SAP system to access and modify the LDAP directory.For more information, see Preparing the Active Directory in the Windows installation guide for your SAPsystem solution and database.

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

Procedure

1. Log on as user <sapsid>adm.2. Enter:

ldappasswd pf=<path_and_name_of_instance_profile>

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

6.5 Heterogeneous SAP System Installation

This section provides information on the installation of an SAP system in a heterogeneous systemlandscape. “Heterogeneous system landscape” means that application servers run on differentoperating systems.

ProcedureSee SAP Note 1067221 for information on

n supported combinations of operating systems and database systems,n how to install an application server on Windows in a heterogeneous (UNIX) SAP system

environment,n heterogeneous SAP system landscapes with different UNIX operating systems.

124/140 PUBLIC 05/25/2009


6 Additional Information6.6 Troubleshooting

6.6 Troubleshooting

The following section(s) describe the steps that you need to performmanually if SAPinst fails:

n Troubleshooting with SAPinst [page 125]

6.6.1 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.If an error occurs, SAPinst:

n Stops the installation.n Displays a dialog informing you about the error.

Procedure

1. To view the log file, choose View Logs.2. If an error occurs during the Define Parameters or Execute phase, do either of the following:n Try to solve the problemn Abort the installation by choosing Cancel in the SAPinstmenu.

For more information, see Interrupted Installation with SAPinst [page 82].n After resolving the problem, you can continue the installation by choosing Retry.

3. Check the log and trace files of the GUI server and SAPinst GUI in the directory<user_home>/.sdtgui/ for errors.n If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current

<user_home> directory.n If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as

described in Starting SAPinst GUI Separately [page 85].n If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote

Access of SAPinst GUI on Windows Workstations and you experience display problems suchas missing repaints or refreshes, contact your X Server vendor. The vendor can give youinformation about whether this X Server supports Java Swing-based GUIs and also tell youabout further requirements and restrictions. See also SAP Note 1170809.

6.7 Deleting an SAP System

This section describes how to delete a single instance, a standalone engine or a complete SAP systemwith the Uninstall option of SAPinst.

05/25/2009 PUBLIC 125/140


6 Additional Information6.7 Deleting an SAP System

Note

We recommend that you delete an SAP system with SAPinst. However, you can also delete an SAPsystem manually. For more information, see SAP Note1229586.

Prerequisites

n You are logged on as user root.n If the saposcol process on the host you are working on has been started from the SAP system you

want to delete, stop it using the command saposcol -k.If there are other SAP systems on the host, log on as user <sapsid>adm of the other SAP system andstart saposcol from there using the command saposcol -l.

Procedure

1. Start SAPinst and on theWelcome screen, choose:<Your SAP product> Software Life-Cycle Options Uninstall Uninstall System / Standalone Engine /

Optional Standalone Unit

Note

With this SAPinst option you do not delete the database software.

2. Follow the instructions in the SAPinst input dialogs.

Note

For more information about the input parameters, place the cursor on the relevant field andpress F1 in SAPinst.

SAPinst first asks you which SAP instances you want to delete. Make sure that you delete the SAPinstances in the order as described hereafter.

Caution

SAPinst only stops local instances automatically. Before you delete the database instance of adistributed system make sure that you stop all remaining instances. You must stop the instancewith the message server only after having entered all SAPinst parameters for the deletion ofthe database instance.

n If you want to delete a central system (all instances reside on the same host), you can do thisin one SAPinst run.a) Delete the SAP system.b) Delete the Oracle database software with the Oracle Universal Installer (OUI) as described in

Deleting the Oracle Database Software [page 127].

126/140 PUBLIC 05/25/2009


6 Additional Information6.8 Deleting the Oracle Database Software

n If you want to delete a distributed or high availability system, you have to run SAPinst todelete the required instances locally on each of the hosts belonging to the SAP system in thefollowing sequence:a) Dialog instance(s), if there are anyb) Central instancec) Database instance

SAPinst deletes the database instance but you have to delete the Oracle database softwaremanually as described in Deleting the Oracle Database Software [page 127].

n


ABAP central services instanceEnd of: HA (UNIX)

3. If required, you can delete the directory /usr/sap/trans and its content manually.SAPinst does not delete /usr/sap/trans because it might be shared.

4. If you created the directories /usr/sap/<SAPSID> and /<sapmnt>/<SAPSID> as mount points, butnot as directories on the local file system, you have to remove themmanually.

6.8 Deleting the Oracle Database Software

You have to delete the Oracle database software to complete the deletion of the Oracle databaseinstance.Here you find information how to delete the Oracle database software with the Oracle UniversalInstaller (OUI).

Note

This section only applies if you have deleted your SAP system using the Uninstall option of SAPinst.We recommend that you delete a database instance with SAPinst and then remove the databasesoftware manually. However, you can also delete the complete database instance manually. For moreinformation, see SAP Note1229689.

Procedure

1. Start the OUI with the user ora<dbsid> by entering one of the following:

n cd /oracle/stage/102_64/database/Disk1/SAP

./runInstaller

n cd /oracle/stage/102_64/database/SAP

./runInstaller

You see a message that a response file is being generated. It might take several minutes before yousee the OUI screen.

2. Choose Installed Products or Uninstall Products.

05/25/2009 PUBLIC 127/140


6 Additional Information6.8 Deleting the Oracle Database Software

3. Select the database schema you want to uninstall: <DBSID>_102_64.4. Mark the Oracle 10G database within the selected product.5. Choose Remove.6. Confirm your selection with Yes.7. Choose EXIT.

128/140 PUBLIC 05/25/2009

A Appendix

A Appendix

A.1 Online Information from SAP

More information is available online as follows.

Documentation

Description Internet Address Title

Master Guide for SAPenhancement package 4for SAP ERP 6.0

http://service.sap.com/erp-inst SAPERP 6.0 SAP enhancement packages for SAP ERP6.0 SAP enhancement package 4 for SAP ERP 6.0

Master Guide ‒ SAP EnhancementPackage 4 for SAP ERP 6.0 poweredby SAP NetWeaver

Master Guide for SAP ERP6.0

http://service.sap.com/erp-inst SAPERP 6.0 SAP enhancement packages for SAP ERP6.0 SAP enhancement package 4 for SAP ERP 6.0

Master Guide - SAP ERP 6.0

Master Guide SAPSolution Manager 7.0

http://service.sap.com/instguides SAPComponents SAP Solution Manager Release 7.0

Master Guide ‒ SAP SolutionManager 7.0

Installation of SAPSolution Manager 7.0


Installation Guide ‒ SAP SolutionManager 7.0 on <OS>: <Database>

Configuration of SAPSolution Manager 7.0


Configuration Guide ‒ SAP SolutionManager 7.0 as of <current stack>

Patching of SAPNetWeaver 7.0 scenarios

http://service.sap.com

/maintenanceNW70 SPS <current stack>Support Package Stack Guide ‒ SPS <current stack>

Support Package Stack Guide ‒ SAPNetWeaver 7.0 SPS <current stack>

Upgrade to EHP4 for SAPERP 6.0

http://service.sap.com/erp-inst SAPERP SAP ERP 6.0 SAP enhancement packages forSAP ERP 6.0 SAP enhancement package 4 for SAPERP 6.0

Upgrade Master Guide - SAP ERP6.0

Installation of SAPNetWeaver DeveloperWorkplace


Installation Installation — Clients Installation ‒SAP Developer Workplace

Installation Guide ‒ DeveloperWorkplace for SAP NetWeaver

Installation of SAPNetWeaver DeveloperStudio


Installation Installation — Clients Installation ‒SAP NetWeaver Developer Studio

SAP NetWeaver Developer Studio —Standalone Installation Guide

Installation of the SystemLandscapeDirectory (SLD)


Configuration Post-Installation Guide ‒ SLD of SAPNetWeaver 7.0

Post-Installation Guide ‒ SystemLandscape Directory of SAPNetWeaver 7.0

05/25/2009 PUBLIC 129/140















http://service.sap.com/maintenanceNW70















A AppendixA.1 Online Information from SAP

Description Internet Address Title

Installationof a standalonegateway


Installation ‒ Standalone Engines Installation —Gateway on <platform>

Installation Guide ‒ Gateway on<platform> ‒ For SAP Systems Basedon SAP NetWeaver 7.0 (2004s)

Installation of WebDispatcher


Installation ‒ Standalone Engines Installation—WebDispatcher on <platform>

Installation Guide ‒ Web Dispatcheron <platform> ‒ For SAP SystemsBased on SAP NetWeaver 7.0 (2004s)

Front End installation http://service.sap.com/installNW70

Installation ‒ Clients Installation ‒ SAP Front End<Release>

SAP Front End Installation GuideThis guide is also available onthe Presentation DVD.

Homogeneous andheterogeneous systemcopy for SAP systems basedon NetWeaver 7.0


Installation ‒ SAP NetWeaver Systems System Copyfor SAP Systems Based on <Release> <Technology>

System Copy Guide—System Copy forSAP Systems based on SAPNetWeaver<Release> <Technology>

SAP NetWeaver ProblemAnalysis Guide

http://help.sap.com/nw70 SAP NetWeaver7.0 Library (including Enhancement Package 1) EnglishSAP NetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by KeyCapability SAP NetWeaver Problem Analysis Guide(PAG)

SAP NetWeaver Problem AnalysisGuide (PAG)

General Quick Links

Description Internet Address

SAP Help Portal http://help.sap.com

SAP NetWeaver Library in SAPHelp Portal


SAP ERP Library in SAP HelpPortal

http://help.sap.com/erp

SAP Notes http://service.sap.com/notes

SAP Notes for SAP NetWeaver 7.0installation

http://service.sap.com/sapnotesnw70

Forums, blogs, and generalinformation related to all ofthe supported databases andoperating system platforms


Product AvailabilityMatrix (PAM)for supported operating systemreleases


Release notes http://service.sap.com/releasenotes

Unicode SAP systems and theiravailability


130/140 PUBLIC 05/25/2009
















http://help.sap.com
















A AppendixA.1 Online Information from SAP

Description Internet Address

System sizing (Quick Sizer tool) http://service.sap.com/sizing

SAP NetWeaver capabilities http://sdn.sap.com/irj/sdn/netweaver

Life-cycle management for SAPNetWeaver

http://sdn.sap.com/irj/sdn/lcm

Landscape design for SAPNetWeaver

http://sdn.sap.com/irj/sdn/landscapedesign

Application management for SAPNetWeaver

http://sdn.sap.com/irj/sdn/applicationmanagement

High Availability http://sdn.sap.com/irj/sdn/ha

System Landscape Directory http://sdn.sap.com/irj/sdn/nw-sld

Software logistics for SAPNetWeaver

http://sdn.sap.com/irj/sdn/softwarelogistics

SAP NetWeaver operations http://sdn.sap.com/irj/sdn/operations

SAP NetWeaver DevelopmentInfrastructure

http://sdn.sap.com/irj/sdn/nw-di

Security for SAP NetWeaver http://sdn.sap.com/irj/sdn/security

Information on SAP SupportPackage Stacks

http://service.sap.com/sp-stacks

SAP Solution Manager http://service.sap.com/solutionmanager

Maintenance Optimizer http://service.sap.com/solman-mopz

End-to-End Root Cause Analysis http://service.sap.com/diagnostics

05/25/2009 PUBLIC 131/140



http://sdn.sap.com/irj/sdn/netweaver

http://sdn.sap.com/irj/sdn/lcm

http://sdn.sap.com/irj/sdn/landscapedesign

http://sdn.sap.com/irj/sdn/applicationmanagement

http://sdn.sap.com/irj/sdn/ha

http://sdn.sap.com/irj/sdn/nw-sld

http://sdn.sap.com/irj/sdn/softwarelogistics

http://sdn.sap.com/irj/sdn/operations

http://sdn.sap.com/irj/sdn/nw-di

http://sdn.sap.com/irj/sdn/security



http://service.sap.com/solutionmanager

http://service.sap.com/solutionmanager



http://service.sap.com/diagnostics

http://service.sap.com/diagnostics

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

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

Example Emphasized words or expressions

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

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

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

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

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

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

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

EXAMPLE Keys on the keyboard

132/140 PUBLIC 05/25/2009

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2009 SAP AG. All rights reserved.

Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof 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 othersoftware vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

05/25/2009 PUBLIC 133/140

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified oraltered in any way.

Legal Software Terms

Terms for Included Open Source SoftwareThis SAP software contains also the third party open source software products listed below. Note that for these third partyproducts the following special terms and conditions shall apply.

1. This software was developed using ANTLR.

2. SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library(STLport) and its documentation without fee.

B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectualproperty laws, and to all of the terms and conditions of this Agreement.

C) The Customer may distribute binaries compiled with STLport (whether original or modified) without anyroyalties or restrictions.

D) Customer shall maintain the following copyright and permissions notices on STLport sources and itsdocumentation unchanged: Copyright 2001 SAP AG

E) The Customer may distribute original or modified STLport sources, provided that:n The conditions indicated in the above permissions notice are met;n The following copyright notices are retained when present, and conditions provided in accompanying

permission notices are met:Copyright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Companymakes no representations about the suitability of this software for any purpose. It is provided “as is” withoutexpress or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no

134/140 PUBLIC 05/25/2009

representations about the suitability of this software for any purpose. It is provided “as is” without express orimplied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARCmakes no representations about the suitability of this software for any purpose. It is provided “as is” withoutexpress or implied warranty.Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material isprovided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to useor copy this software for any purpose is hereby granted without fee, provided the above notices are retained on allcopies. Permission to modify the code and to distribute modified code is granted, provided the above notices areretained, 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 ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. SAP makes no representationsabout the suitability of this software for any purpose. It is provided with a limited warranty and liability as setforth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations onlytowards its customers and only referring to its modifications.

b) Support and MaintenanceSAP does not provide software maintenance for the STLport. Software maintenance of the STLport thereforeshall be not included.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditionsand shall be subject to a separate contract.

c) Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that theSTLport 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 anyassurance of particular attributes.

d) Limited Liability

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

B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerialemployees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shalldepend 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.

C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by adefect or lost profit.

D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceedEUR 5,000.

E) The Customer shall take adequate measures for the protection of data and programs, in particular by makingbackup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data andits recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided byobserving this obligation.

F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employeesor agents of SAP.

3. Adobe Document Services

05/25/2009 PUBLIC 135/140

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States and / or other countries. For information on Third Party software delivered withAdobe document services and Adobe LiveCycle Designer, see SAP Note 854621.

4. Apache License, Version 2.0

a) Definitions:n "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections

1 through 9 of this document.n "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the

License.n "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.

n "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.n "Source" form shall mean the preferred form for making modifications, including but not limited to software

source code, documentation source, and configuration files.n "Object" form shall mean any form resulting frommechanical transformation or translation of a Source form,

including but not limited to compiled object code, generated documentation, and conversions to other mediatypes.

n "Work" shall mean the work of authorship, whether in Source or Object form, made available under theLicense, as indicated by a copyright notice that is included in or attached to the work (an example is providedin the Appendix below).

n "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, asa whole, an original work of authorship. For the purposes of this License, Derivative Works shall not includeworks that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and DerivativeWorks thereof.

n "Contribution" shall mean any work of authorship, including the original version of the Work and anymodifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensorfor inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit onbehalf 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 tocommunication on electronic mailing lists, source code control systems, and issue tracking systems that aremanaged by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excludingcommunication that is conspicuously marked or otherwise designated in writing by the copyright owner as"Not a Contribution."

n "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution hasbeen received by Licensor and subsequently incorporated within the Work.

b) Grant of Copyright LicenseSubject 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 orObject form.

c) Grant of Patent LicenseSubject 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, havemade, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to thosepatent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or bycombination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institutepatent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a

136/140 PUBLIC 05/25/2009


Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patentlicenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

d) RedistributionYou may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or withoutmodifications, and in Source or Object form, provided that You meet the following conditions:

A) You must give any other recipients of the Work or Derivative Works a copy of this License; and

B) You must cause any modified files to carry prominent notices stating that You changed the files; and

C) 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 notpertain to any part of the Derivative Works; and

D) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distributemust include a readable copy of the attribution notices contained within such NOTICE file, excluding thosenotices that do not pertain to any part of the Derivative Works, in at least one of the following places: withina NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, ifprovided along with the Derivative Works; or, within a display generated by the Derivative Works, if and whereversuch third-party notices normally appear. The contents of the NOTICE file are for informational purposes onlyand do not modify the License. You may add Your own attribution notices within Derivative Works that Youdistribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additionalattribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different licenseterms and conditions for use, reproduction, or distribution of Your modifications, or for any such DerivativeWorks as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with theconditions stated in this License.

e) Submission of ContributionsUnless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You tothe 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 agreementyou may have executed with Licensor regarding such Contributions.

f) TrademarksThis License does not grant permission to use the trade names, trademarks, service marks, or product names of theLicensor, except as required for reasonable and customary use in describing the origin of the Work and reproducingthe content of the NOTICE file.

g) Disclaimer of WarrantyUnless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor providesits Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, eitherexpress 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 determiningthe appropriateness of using or redistributing the Work and assume any risks associated with Your exercise ofpermissions under this License.

h) Limitation of LiabilityIn no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unlessrequired by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall anyContributor be liable to You for damages, including any direct, indirect, special, incidental, or consequentialdamages of any character arising as a result of this License or out of the use or inability to use the Work (includingbut not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and allother commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

i) Accepting Warranty or Additional Liability

05/25/2009 PUBLIC 137/140

While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptanceof support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, inaccepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf ofany other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for anyliability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty oradditional liability.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: https://service.sap.com/instguides

138/140 PUBLIC 05/25/2009

https://service.sap.com/instguides



SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2009 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 bechanged without prior notice.

installation guide erp6.0

Documents