sap erp 6.0 sr3 abap

PUBLIC

Installation Guide

SAP ERP 6.0 SR3 ABAPon Linux: OracleIncluding the following:

ERP Central Component

Target Audience

n System administrators

n Technology consultants

Document version: 1.0 ‒ 03/28/2008

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.0 3/28/2008 Initial Version

2/140 PUBLIC 03/28/2008

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



Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 71.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 81.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 111.3 Online Information from SAP . . . . . . . . . . . . . . . . . . 121.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 172.1 Basic System Variants . . . . . . . . . . . . . . . . . . . . . 172.2 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . 192.3 SAP System Transport Host . . . . . . . . . . . . . . . . . . . 212.4 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 212.5 High Availability: Planning the Switchover Cluster . . . . . . . . . . 28

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 333.1 High Availability: Switchover Preparations . . . . . . . . . . . . . 343.1.1 Preparing for Switchover . . . . . . . . . . . . . . . . . . . . 343.1.2 Setting Up File Systems for a High-Availability System . . . . . . . . . 363.1.3 Configuring Network File System . . . . . . . . . . . . . . . . 373.2 Hardware and Software Requirements . . . . . . . . . . . . . . . 393.2.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 403.2.2 Requirements for Linux . . . . . . . . . . . . . . . . . . . . 413.2.3 Requirements for a Central System . . . . . . . . . . . . . . . . 433.2.4 Requirements for a Distributed or a High Availability System . . . . . . 443.2.4.1 Requirements for the Central Services Instance . . . . . . . . . . . 453.2.4.2 Requirements for the Central Instance . . . . . . . . . . . . . . 463.2.4.3 Requirements for the Database Instance . . . . . . . . . . . . . . 463.2.5 Requirements for a Dialog Instance . . . . . . . . . . . . . . . . 483.2.6 Checking and Modifying the Linux Kernel . . . . . . . . . . . . . 493.2.7 Setting up Swap Space for Linux . . . . . . . . . . . . . . . . . 503.3 Creating Operating System Users . . . . . . . . . . . . . . . . 513.3.1 Network Information Service . . . . . . . . . . . . . . . . . . 513.3.2 Creating Operating System Users and Groups . . . . . . . . . . . . 513.3.3 Creating Linux Groups and Users (Optional) . . . . . . . . . . . . 533.4 Setting Up File Systems and Raw Devices . . . . . . . . . . . . . . 533.4.1 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . 54

03/28/2008 PUBLIC 3/140

3.4.2 Oracle Directories . . . . . . . . . . . . . . . . . . . . . . 573.4.3 Setting Up Standard File Systems and Raw Devices for Linux . . . . . . 603.5 Exporting and Mounting the Global Transport Directory . . . . . . . . 613.6 Exporting and Mounting Directories via NFS for Linux (Optional) . . . . 613.7 Installing the Front-End Software . . . . . . . . . . . . . . . . 633.8 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 633.9 Installing the Java Runtime Environment . . . . . . . . . . . . . 643.10 Preparing and Mounting the Installation Media . . . . . . . . . . . 653.10.1 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 653.10.2 Downloading Installation DVDs from SAP Service Marketplace (Optional) . 673.10.3 Mounting a CD / DVD for Linux . . . . . . . . . . . . . . . . . 68

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 694.1 Performing a High-Availability Installation . . . . . . . . . . . . . 694.2 Prerequisites before Starting SAPinst . . . . . . . . . . . . . . . 714.2.1 Prerequisites before Starting SAPinst: All Instances . . . . . . . . . . 714.2.2 Prerequisites before Starting SAPinst: Distributed Instances . . . . . . . 734.2.3 Prerequisites Before Starting SAPinst: High Availability . . . . . . . . . 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 (Optional) . . . . . . . 844.3.5 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 854.3.6 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 874.4 Oracle Database Software Installation . . . . . . . . . . . . . . . 874.4.1 Updating SAP-Specific Files in the Oracle Staging Area . . . . . . . . . 884.4.2 Running the Oracle Universal Installer . . . . . . . . . . . . . . 884.4.3 Installing the Current Patch Set . . . . . . . . . . . . . . . . . 904.4.4 Installing Required Interim Patches . . . . . . . . . . . . . . . . 91

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 935.1 Logging On to the Application Server . . . . . . . . . . . . . . . 945.2 Installing the SAP License . . . . . . . . . . . . . . . . . . . 945.3 Installing the SAP Online Documentation . . . . . . . . . . . . . 955.4 Configuring Remote Connection to SAP Support . . . . . . . . . . 955.5 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 965.6 Performing Initial ABAP Configuration . . . . . . . . . . . . . . 975.7 Performing Oracle-Specific Post-Installation Steps . . . . . . . . . . 1005.8 Performing the Client Copy . . . . . . . . . . . . . . . . . . 1005.9 Performing a Full Installation Backup . . . . . . . . . . . . . . . 1015.10 Implementing ERP ABAP Add-On Components . . . . . . . . . . . 103

4/140 PUBLIC 03/28/2008

5.11 High Availability: Post-Installation Steps . . . . . . . . . . . . . . 1035.11.1 Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . 1035.11.2 Taking Precautions for Transport . . . . . . . . . . . . . . . . 1045.12 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 1045.13 Accessing Configuration Documentation in SAP Solution Manager . . . . 106

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 1096.1 Installation of Multiple Components in One Database (Optional) . . . . . 1096.2 Integration of LDAP Directory Services (Optional) . . . . . . . . . . 1116.3 Starting and Stopping SAP System Instances . . . . . . . . . . . . 1156.3.1 Starting and Stopping SAP System Instances Using the SAP Management

Console . . . . . . . . . . . . . . . . . . . . . . . . . . 1156.3.2 Starting and Stopping SAP System Instances Using Scripts . . . . . . . 1196.4 Creating a User for LDAP Directory Access (Optional) . . . . . . . . . 1226.5 Configuring the Connection to a Central System Landscape Directory (SLD) 1236.6 Heterogeneous SAP System Installation . . . . . . . . . . . . . . 1236.7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 1236.7.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 1236.8 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 1246.8.1 Deleting an SAP System Using SAPinst . . . . . . . . . . . . . . . 1246.8.1.1 Running SAPinst to Delete an SAP System . . . . . . . . . . . . . 1256.8.1.2 Deleting the Oracle Database Software . . . . . . . . . . . . . . 1266.8.2 Deleting an SAP SystemManually . . . . . . . . . . . . . . . . 1276.8.2.1 Deleting an SAP Instance . . . . . . . . . . . . . . . . . . . 1276.8.2.2 Deleting Installation Files, Directories, and Users on a Host . . . . . . . 1286.8.2.3 Deleting an Oracle Database Instance . . . . . . . . . . . . . . . 129

03/28/2008 PUBLIC 5/140

6/140 PUBLIC 03/28/2008

1 Introduction

1 Introduction

This document explains how to install SAP ERP 6.0 SR3 ABAP.SAP ERP 6.0 is based on SAP NetWeaver 7.0 technology. For more information about thetechnology provided by SAP ERP and SAP NetWeaver, see http://service.sap.com/erp andhttp://sdn.sap.com/irj/sdn/netweaver.Make sure you have read the documentationMaster Guide Support Release 3‒ SAP ERP 6.0 powered by SAPNetWeaver 7.0 Using Product Version SAP ERP 2005 before you start with this installation guide. The MasterGuide is available at http://service.sap.com/erp-inst SAP ERP 6.0 .

Caution

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

You can install SAP ERP 6.0 SR3 with the following software unit(s):

n SAP ERP Central Component (ECC)

Note

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

n If you want to add additional software units or usage types to an existing SAP system, followSAP Note 883948.

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

Constraints

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

n Your operating system platform must be 64-bit.n The database must be Oracle 10.2.0.2 or higher.n Youmust only use the SAP installation tools according to the instructions and for the purposes

described in the SAP installation document. Improper use of the SAP installation tools can damagefiles and systems already installed.

n SAP system installations should only be performed by SAP Technical Consultants certified foryour operating system, your database, and the SAP system that you are installing.

03/28/2008 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=852235&_NLANG=en&_NVERS=0


http://service.sap.com/instguidesNW70




1 Introduction1.1 New Features

n For downward-compatible releases of DB/OS platforms for SAP products, SAP plans to regularlyrelease the newest database (DB) and operating-system (OS) versions of SAP products. Thesereleases are downward-compatible with earlier SAP system releases.Note that for already shipped SAP components, we only support the installation for databaseversions proposed by the installation tool. Therefore, you must install an SAP component orperform a system copy using a downward-compatible database as follows:l Install the component with the old proposed database version.l Upgrade the old database version to the downward-compatible new version.

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.

SAP System Installation

Area Description

SAPinst As of SAP NetWeaver 7.0, SAPinst has the following new features:n You can check the prerequisites for your SAP system installation with the

Prerequisite Checker [page 40].n You can install a central system in one of two modes:l Typical Mode

If you choose Typical, your SAP system is installed with default settings. Asa result, you only have to respond to a small selection of prompts. If youwant to change any of the default settings, you can do so on the parametersummary screen at the end of the installation.

l Custom ModeIf you choose Custom, you must manually enter all installation parameters.You can change your values on the parameter summary screen at the end ofthe installation.

n You can uninstall an SAP system or an SAP component with the SAPinst serviceUninstall ‒ System / Standalone Engines / Optional Standalone Unit.

n You can install the Java Add-In for an existing ABAP system. This means that yourun SAPinst to execute the following:l Install the central services instance (SCS)l Add the Java database schema to the existing ABAP database instancel Add the Java central instance with usage types to the existing ABAP central

instanceThe installation of the Java Add-In for an existing ABAP system is described in thedocumentation Installation Guide ‒ <your product> ABAP+Java on <OS>: <Database>available at http://service.sap.com/instguides.

8/140 PUBLIC 03/28/2008

http://service.sap.com/releasenotes



http://service.sap.com/instguides



Area Description

NoteYou cannot install the Java Add-In for existing ABAP dialog instance(s). Instead,you have to install new ABAP+Java dialog instance(s).

n The sapinst group ID must be the secondary group of the users root and<sapsid>adm. For more information, see Creating Operating System Users and GroupsManually [page 51].

n You can install SAP NetWeaver as a high-availability (HA) system.n You assign one master password to all users created by SAPinst. This password is

used for all user accounts and for the secure store key phrase.n SAPinst fills in most of the input parameter fields with default values.

If required, you can change the default values on the Parameter Summary screenbefore you start the actual installation.

n You no longer have to manually activate sapcpe.The kernel is replicated automatically from/usr/sap/<SAPSID>/SYS/exe/run/DIR_CT_RUN to/usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for eachSAP system instance.For more information, see Setting Up File Systems [page 54].

Installation DVDs You start the installation from a single Installation Master DVD.

Usage type EP Core(EPC)

As of SAP NetWeaver 7.0 SR2, usage type Enterprise Portal (EP) has been separatedinto two closely related usage types: EP Core (EPC) and Enterprise Portal (EP). Usagetype EPC provides the core portal capabilities available in the former usage type EP.Usage type EP now includes all portal add-on capabilities it provided before, butwithout the core portal functionality.n EP Core (EPC)

This usage type contains the core portal capabilities that were available in theformer usage type EP. This new usage type provides more flexibility whenimplementing a portal where the full enterprise portal capabilities, such asknowledge management and collaboration, are not needed. It contains theportal, Guided Procedures (GP), and Universal Worklist (UWL).

n Enterprise Portal (EP)This usage type includes Knowledge management, Collaboration, CompositeApplication Framework Core (CAF-Core), Visual Composer, Web Dynproextension, and .NET PDK.

For more information about EPC and about how to use it in IT scenarios, see theMaster Guide and SAP Note 982502.

SAP SRM 5.0 as Add-OnComponent to SAPERP 6.0

In SAP ERP 6.0, you can deploy SAP SRM Server as one of the following:n An add-on to SAP ECC Server (product instance SAP ERP 6.0 ‒ SAP ECC) to

run SRM in one client of the ERP system. This deployment option is new inSAP ERP 6.0.

n A separate installation from SAP ECC Server. This deployment option is thesame as in mySAP ERP 2004.

For more information, see the documentationMaster Guide ‒ SAP ERP 6.0 powered bySAP NetWeaver 7.0 at http://service.sap.com/erp-inst.

03/28/2008 PUBLIC 9/140





Area Description

SAP Solution ManagerKey

You require a key to install your SAP system. You generate this key with your SAP SolutionManager [page 63].

64-bit support for allinstances except dialoginstances

If you want to use 32-bit SAP NetWeaver components, first check whether thesecomponents can run on 64-bit operating systems. If so, we recommend that youuse 64-bit systems.If not, you can install an SAP dialog instance on 32-bit operating systems to runthese components. For all other SAP instances, you must use 64-bit systems

Only Unicode supportfor new installations

Every newly installed SAP system is a Unicode system.However, non-Unicode is still supported for copied and upgraded systems.

MaintenanceOptimizer

All downloadable software components based on SAP NetWeaver 7.0 and subsequentversions released after April 2, 2007 are available exclusively through theMaintenance Optimizer in SAP Solution Manager. This comprises: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 2005 (andsubsequent versions)

l Optional for all SAP applicationsFor more information, see http://service.sap.com/solman-mopz.

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.

n For Linux distributions that are supported by SAP, seehttp://sdn.sap.com/irj/sdn/linux

Oracle Database

New functions inOracle Database 10g

n As of the installation of SAP NetWeaver 7.0 and SAP Business Suite 2005, newfunctions of the Oracle Database 10g release are used.For more information about the integration of Oracle 10g in the SAPenvironment, see SAP Note 720886.

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

10/140 PUBLIC 03/28/2008

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

http://service.sap.com/pam

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

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


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

1 Introduction1.2 SAP Notes for the Installation

Documentation

Area Description

Links in PDF files You can use the new links in the PDF files of the guides as follows:n Click the section headings such as New Features to jump back to the table of

contents at the beginning of the guide.n Click an internet link such as http://service.sap.com to jump to the

corresponding internet page.

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

852235 Release restrictions for SAP ERP6.0

At the time of the release of SAP ERP 6.0,limitations affect the productive usage ofcertain functions. This note provides customerinformation on these restrictions.

1052298 SAP NetWeaver 7.0 SR3 / BusinessSuite 2005 SR3 ‒ UNIX

UNIX-specific information about the SAP systemand corrections to this documentation.

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

852008 Release Restrictions for SAPNetWeaver 7.0

Customer information on restrictions in theproduction use of certain functions.

1094599 SAP NetWeaver 7.0 SR3 / BusinessSuite 2005 SR3 ‒ UNIX: Oracle

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

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

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

03/28/2008 PUBLIC 11/140

http://service.sap.com

http://service.sap.com/notes








1 Introduction1.3 Online Information from SAP

SAP Note Number Title Description

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 System i:Checking OS Dependencies

73606 Supported Languages and CodePages

Information on possible languages and languagecombinations in SAP systems

171356 Linux only: SAP software onLinux: Essential comments

This SAP Note is only required for installationson Linux. It contains Linux-specific informationabout the SAP system installation.

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.

1152408 Installing SAP Systems into anIndependent ASP (iASP)

Information on features and limitations forinstallations into independent ASP.

1.3 Online Information from SAP

More information is available online as follows.

Documentation

Description Internet Address Title

Master Guide for SAP ERP6.0

http://service.sap.com/erp-inst SAPERP 6.0 Installation Master Guide for SAP ERP6.0

Master Guide Support Release 3‒ SAP ERP 6.0 powered by SAPNetWeaver 7.0 — Using ProductVersion SAP ERP 2005

Master Guide SAPSolution Manager 4.0

http://service.sap.com/instguides SAPComponents SAP Solution Manager Release 4.0

Master Guide ‒ SAP SolutionManager 4.0

Installation of SAPSolution Manager 4.0


Installation Guide ‒ SAP SolutionManager 4.0 on<OS>: <Database>

Configuration of SAPSolution Manager 4.0


Configuration Guide ‒ SAP SolutionManager 4.0 as of <current stack>

12/140 PUBLIC 03/28/2008



















Description Internet Address Title

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 SAP ERP 6.0 http://service.sap.com/erp-inst SAPERP SAP ERP 6.0 Upgrade Upgrade MasterGuide — SAP ERP 6.0

Upgrade Master Guide — SAP ERP6.0 powered by SAP NetWeaver 7.0 ‒Using Product Version SAP ERP 2005

Installation of SAPNetWeaver DeveloperWorkplace

http://service.sap.com/installNW70

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

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 ‒ English SAP NetWeaver Library SAPNetWeaver by Key Capability Solution Life CycleManagement by Key Capability SAP NetWeaverProblem 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

http://help.sap.com/nw70

SAP ERP Library in SAP HelpPortal

http://help.sap.com/erp

03/28/2008 PUBLIC 13/140






























http://help.sap.com






Description Internet Address

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


General information, forums andblogs about information relatedto SAP on Linux


Release notes http://service.sap.com/releasenotes

Unicode SAP systems and theiravailability

http://service.sap.com/unicode

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

14/140 PUBLIC 03/28/2008













http://service.sap.com/sizing


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/diagnostics

http://service.sap.com/diagnostics

1 Introduction1.4 Naming Conventions

1.4 Naming Conventions

Note

We have renamed “mySAP ERP 2005” to “SAP ERP 6.0”. On the technical level, “SAP ERP 6.0” isassociated with product version “SAP ERP 2005”. The term “SAP ERP 2005” remains valid. In thisdocument, we use the term “SAP ERP 6.0” and the name of the product version “SAP ERP 2005” todepict the former release “mySAP ERP 2005”.

In this documentation, the following naming conventions apply:

Terminology

n SAP system refers to SAP ERP 6.0 SR3.n ABAP system refers to SAP ERP 6.0SR3 ABAP.

Variables

Variables Description

<SAPSID> SAP system ID in uppercase letters

<sapsid> SAP system ID in lowercase letters

<DBSID> Database ID in uppercase letters

<dbsid> Database ID in lowercase letters

<host_name> Name of the corresponding host

<user_home> Home directory of the user performing the installation.

<INSTDIR> Installation directory for the SAP system

<DVD_DIR> Directory on which a DVD is mounted

<OS> Operating system name within a path

<SCHEMA_ID> Database schema ID

The following example shows how the variables are used:

Example

Log on as user <sapsid>adm and change to the directory /usr/sap/<SAPSID>.If your SAP system ID is C11, log on as user c11adm and change to the directory/usr/sap/C11.

03/28/2008 PUBLIC 15/140

This page is intentionally left blank.

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:

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 17].3. You plan how to distribute the instances to hosts [page 19].4. You decide on the transport host to use [page 21].5. You identify basic SAP system parameters [page 21].

6.

Only valid for: HA (UNIX)

You plan the switchover cluster [page 28] 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 109]

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

If you want to use 32-bit SAP NetWeaver components, first check whether these components can runon 64-bit operating systems. If so, we recommend you to use 64-bit systems. If not, you can installan SAP dialog instance on 32-bit operating systems to run these components. For all other SAPinstances, you must use 64-bit systems.

Note

Each instance can reside on a separate host.

03/28/2008 PUBLIC 17/140




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.

18/140 PUBLIC 03/28/2008

2 Planning2.2 How to Distribute Instances to Hosts


Figure 3: Maximum Distribution for a High-Availability System

End of: HA (UNIX)

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

03/28/2008 PUBLIC 19/140

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

20/140 PUBLIC 03/28/2008

2 Planning2.3 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.3 SAP System Transport Host

The transport host contains the transport directory that is used by the SAP transport system to storetransport data and change information of SAP systems, such as software programs, data dictionarydata, 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.For more information, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management SoftwareLogistics Change and Transport System Change and Transport System ‒ Overview (BC-CTS) Basics of the Changeand Transport System Transport Management System ‒ ConceptWhen you install an SAP system, SAPinst by default creates the transport directory on the centralinstance host in /usr/sap/trans.You have to prepare this host for use by the new SAP system if one of the following applies to you:

n You want to locate the transport directory on another host.n You want to use an existing transport host and directory in your SAP system landscape.

For more information, see Exporting and Mounting the Global Transport Directory [page 61].

More InformationSetting Up File Systems and Raw Devices [page 53]

2.4 Basic SAP System Parameters

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.

Note

In the column “Enter Your Values”, you write down the values that you plan to use, for example,theMessage Port Number.

03/28/2008 PUBLIC 21/140




2 Planning2.4 Basic SAP System Parameters

SAP System ID and Database ID

Parameters Description Enter Your Values

SAP System ID<SAPSID>

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

CautionChoose your SAP system ID carefully. You cannot changethe SAP system ID after the installation.

Make sure that your SAP system ID:n Is unique throughout your organizationn 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: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

...

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

CautionChoose your database ID carefully. Renaming is difficultand requires you to 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 towhich you want to add the system.

...

22/140 PUBLIC 03/28/2008


Only valid for: SAP CRM 5.0;SAP SCM 5.0;SAP SRM Server 5.5

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 systemcopy for a non-Unicode SAP system that has been upgradedto SAP NetWeaver 7.0 SR3

...

End of: SAP CRM 5.0;SAP SCM 5.0;SAP SRM Server 5.5

SAP System Instances, Hosts and Ports

Parameters Description EnterYourValues

Instance Number ofthe SAP system

Technical identifier for internal processes. It consists of a two-digitnumber from 00 to 98.The instance number must be unique on a host. That is, if more thanone SAP instance is running on the same host, these instances must beassigned different numbers.To find out this number, look under the SAP directory/usr/sap/<SAPSID>/DVEBMGS<nn> on the host of the central instance.The value <nn> is the number assigned to the central instance.

...

Name of InstanceHost

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 informationabout 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 systemon 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 serverport.The ABAPmessage server uses both the internal and the external messageserver ports. The default profile contains the configuration for bothmessage server ports.The externalmessage server port uses the parameter rdisp/msserv withdefault value 36<nn>, where <nn> is the instance number of the ABAPmessage server instance.

...

03/28/2008 PUBLIC 23/140



Parameters Description EnterYourValues

The internal message server port uses the parameterrdisp/msserv_internal with default value 39<nn>, where<nn> is the instance number of the ABAP message server instance.For more information about the parameters used for message serverports, see SAP Note 821875.

Master Password


Master Password This password is used for all user accounts SAPinst creates andfor the secure store key phrase. The length has to be 8 to 14characters.Depending on your installation scenario there might be morerestrictions.

CautionIf you do not create the operating system users manually,SAPinst creates them with the common master password (see“Operating System Users”). In this case, make sure that themaster password meets the requirements of your operatingsystem and of your database.

...

Operating System Users


User <sapsid>adm User <sapsid>adm is the system administrator user.If you did not create user <sapsid>adm manually beforethe installation, SAPinst creates it automatically during theinstallation. SAPinst sets the Master Password by default, but youcan overwrite it either by choosing parameter mode Custom or bychanging it on the parameter summary screen.Make sure that the user ID and group ID of this operating systemuser are unique and the same on each application server instancehost.For more information, see Creating Operating System Users [page 51].

...

24/140 PUBLIC 03/28/2008



Internet Communication Manager (ICM) User Management

Parameter Description Enter Your Values

Password of webadm The administration user webadm is created to use the webadministration interface for Internet Communication Manager(ICM) and Web Dispatcher.SAPinst sets the master password by default. If required, youcan choose another password. The length of the password mustbe between 5 and 128 characters.

...

Solution Manager Key


SAP Solution Managerkey

To install your SAP system, you need to generate an SAP SolutionManager key [page 63], which the installation requires to continue.For more information, see SAP Note 805390.

...

Parameters Relevant for the File System

Parameters Description Your Values

File system for the home directoryuser

/home/<username> ...

SAP systemmount directory /<sapmnt> is the base directory forthe SAP system.For /<sapmnt> you can use adirectory of your choice.Do not add <SAPSID> assubdirectory because the systemadds this directory automatically.

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

...

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

...

03/28/2008 PUBLIC 25/140



Parameters Relevant for the Database


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

NoteThis parameter is only prompted if you perform a targetsystem installation 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 systemwhere <SCHEMAID> is the same as <SAPSID>, and thedatabase-specific method used for the copy does not allowyou to rename the database schemas. In certain situations,you might create a system copy with a new <SAPSID>, butwhere the database schema has the old <SAPSID>. This isnot a technical problem, but might confuse the systemadministrator.

...

Password of Userora<dbsid>

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

installation, SAPinst prompts you for the existingpassword of this user.

NoteIf you chose parameter mode Typical, SAPinst onlyprompts you for the existing password of this user ifthe password is not the same as the Master Password.

n If you did not create user ora<dbsid>manually beforethe installation, SAPinst creates it automatically duringthe installation. SAPinst then prompts you to enter andconfirm a password for this user. In this case, SAPinstsets the Master Password by default. You can overwriteit.

NoteIf you chose parameter mode Typical, SAPinst doesnot prompt you for the existing password of this userbut creates this user and assigns the Master Password

...

26/140 PUBLIC 03/28/2008



automatically.

Make sure that the user ID and group ID of this operatingsystem user are unique and the same on each applicationinstance host.For more information, see Creating Operating System Users[page 51].

User ID of Userora<dbsid>

If you chose parameter mode Typical and you did not createora<dbsid>manually before the installation, SAPinstautomatically creates this user with the appropriate userID. 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 uniqueand the same on each application instance host.For more information, see Creating Operating System Users[page 51].

...

Group IDs of sys, dba andoper

If you chose parameter mode Typical and you did not createora<dbsid>manually before the installation, SAPinstautomatically creates this user and assigns it to groups sys,dba and oper. In this case, SAPinst does not prompt you forthe user ID of ora<dbsid>.Make sure that the group IDs of dba and oper are uniqueand the same on each application instance host.For more information, see Creating Operating System Users[page 51].

...

Database User Oracle User System ...

Oracle Listener Name,Oracle Listener Port

n If you install the database instance on a host where noother Oracle database is installed, you normally do nothave to change the default values for Listener Nameand Listener Port.

n If there is already an Oracle database installed on yourinstallation host, you can either use one listener forboth databases or you have to specify an unused ListenerName and an unused Listener Port for the new listener.For more information if you use one listener for bothdatabases, see SAP Note 98252.

n All dialog instances of an SAP systemmust use the sameListener Port than the database instance.

...

03/28/2008 PUBLIC 27/140

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

2 Planning2.5 High Availability: Planning the Switchover Cluster


Tablespaces, Datafiles An Oracle database consists of one or more logical storageunits called tablespaces, which collectively store all of thedatabase’s data.Each tablespace in an Oracle database consists of one ormore files called datafiles, which are physical structuresthat conform to the operating system in which Oracle isrunning.MaxDatafileSize is the initial size of the tablespacedatafile and its mapping to the new tablespace layout whileimporting 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 SAPdatafiles (sapdata 1 - 4), see Requirements for the DatabaseInstance [page 46].

...

Database Instance RAM The RAM that is required for the database instanceinstallation.The default value used by SAPinst is 50 percent of the entireRAM.For more information about minimum RAM, seeRequirements for the Database Instance [page 46].

...

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

...


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

28/140 PUBLIC 03/28/2008



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 English SAP NetWeaver Library SAP

NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology Client/ServerTechnology The SAP Lock Concept Standalone Enqueue Server Installing the Standalone Enqueue Server

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

03/28/2008 PUBLIC 29/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:

30/140 PUBLIC 03/28/2008


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)

03/28/2008 PUBLIC 31/140

3 Preparation

3 Preparation

You have to complete the following preparations:

1.


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

2. You check the hardware and software requirements [page 39].3. If required, you create operating system users manually [page 51].4. You set up file systems and raw devices [page 53].5. 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>to central instance host, database instance host, and— if required— to the dialog instancehost(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 61]n Exporting and Mounting Directories via NFS for Linux [page 61]

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

03/28/2008 PUBLIC 33/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 28].

Procedure

1. You check that your system meets the hardware and software requirements [page 39] 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:

Caution

This step does not apply to the installation of a Java Add-In to an existing ABAP system.

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 36] using mount points or NFS

34/140 PUBLIC 03/28/2008


b) If required, you configure NFS [page 37], making sure you are using the virtual host name for NFSto 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.

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. You set up Domain Name System (DNS) on the virtual host.

Caution


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

Caution


03/28/2008 PUBLIC 35/140


Note

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

End of: HA (UNIX)


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

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.

36/140 PUBLIC 03/28/2008


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.

Procedure

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

n /sapmnt/<SID>/profile

Contains the different profiles to simplify maintenance

n /sapmnt/<SID>/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.

n /sapmnt/<SID>/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.

03/28/2008 PUBLIC 37/140


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/<SID>

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

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

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

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

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/<SID> to /sapmnt/<SID>

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/<SID>

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


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

/sapmnt/<SID>

End of: HA (UNIX)

End of: HA (UNIX)

38/140 PUBLIC 03/28/2008

3 Preparation3.2 Hardware and Software Requirements

3.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:n The Prerequisite Checker:l Standalone (optional) before the installation process

For more information, see Running the Prerequisite Checker Standalone [page 40].l Integrated in SAPinst (mandatory) as part of 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 Linux [page 41]l Central system [page 43]l Distributed or high availability system [page 44]l If you want to install dialog instance(s), check the requirements for a dialog instance [page 48].

Note

If you want to use 32-bit SAP NetWeaver components, first check whether thesecomponents can run on 64-bit operating systems. If so, we recommend you to use 64-bitsystems. If not, you can install an SAP dialog instance on 32-bit operating systems to runthese components. For all other SAP instances, you must use 64-bit systems.

03/28/2008 PUBLIC 39/140





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 SAP Quick Sizer tool available at http://service.sap.com/sizing.

For more information about the SAP 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

3.2.1 Running the Prerequisite Checker in Standalone Mode(Optional)

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

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 installed the correct Java Runtime Environment (JRE) [page 64].n You have prepared the installation master DVD on the required installation host [page 65].n You make sure that the required prerequisites are met before starting SAPinst [page 71].

Procedure

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

Options 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. If you want to make a change, select the relevant parameters and choose Revise.

4. To start the Prerequisite Checker, choose Start.

40/140 PUBLIC 03/28/2008




http://service.sap.com/installnw70


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

3.2.2 Requirements for Linux

Note

n The information here is not intended to replace the documentation of the Linux operatingsystem (OS).

n For more information about the installation on Linux, see SAP Note 171356.n For information about SAP on Linux, see http://sdn.sap.com/irj/sdn/linux.

The host machine must meet the following requirements:

Hardware Requirements

Requirement Values and Activities

DVD drive n DVD drivel ISO 9660 compatiblel Must be connected locally to your central instance host.l You can configure multiple DVD drives. For more information, seeMounting a CD /

DVD for Linux [page 68].

Disks For data security reasons, distribution over five disks is recommended (RAID5).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.To print and change the partitioning of the first SCSI disk, enter this command:/sbin/fdisk /dev/sda

To print and change the partitioning of a RAID device enter commands specific to yourhardware.

ExampleHere are some examples of hardware-specific commands for RAID devices:/sbin/fdisk /dev/rd/c0d0

/sbin/fdisk /dev/ida/c0d0

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

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

03/28/2008 PUBLIC 41/140




Software Requirements


Operating systemversion

Check the operating system version with this command:cat /etc/*-release

Linux kernel version Check the Linux kernel version with this command:uname -r

Linux kernel parametersettings

Check the Linux kernel parameter settings with this command:/sbin/sysctl –a

Activated hardwaredrivers

Check the activated hardware drivers with this command:lsmod

Shared memory filesystem

Check the size of the shared memory file system with this command:df –k /dev/shm

Network File System(NFS)

Check whether NFS is running as follows:n On Red Hat Linux

service nfs status

service portmap status

n On SUSE LINUXrcnfs status

rcnfsserver status

rcportmap status

Routing information To check routing information, enter the following command:netstat -r

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

National LanguageSupport (NLS)

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

Check the output for locales such as the following:de_DE, en_US

locales are available as an attachment of SAP Note 171356.

LDAP (LightweightDirectory AccessProtocol)

If you want to use LDAP, you need the LDAP libraries that are usually installed withthe openldap RPM. To check, enter this command:rpm -qa | grep openldap

Make sure that the output of this command contains at least one of the followingRPM packages:n Red Hat Linux:

openldap2

n SUSE LINUXopenldap2

openldap2–client

C compiler The C compiler gcc must be installed. To check, enter this command:rpm -qa | grep gcc

Make sure that the output of this command contains a gcc RPM package.

Oracle Database For the installation of Oracle on SUSE LINUX IA64, you must use at least SLES9or higher.

42/140 PUBLIC 03/28/2008



Other Requirements


Printer Check the status of spooling queues and printers with the following command:lpc status

Check whether you can print a file with this command:lpr —P<printer_name> <test_file>

Network Test the network connection to the database server with the following command:ping -c 10 <db_server_name>

3.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) inthe SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library EnglishSAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key

03/28/2008 PUBLIC 43/140

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





Capability Platform-Wide Services Database Support Oracle SAP Database Guide: Oracle(BC-DB-ORA-DBA) Getting Started with Oracle and the SAP System .

Hard disk space n Hard disk drives with sufficient space for the SAP system and the databaseFor more information, see Setting Up File Systems [page 54].

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

n 1.2 GB of temporary disk space for the installation.

RAM 1.5 GB (minimum), 4 GB (recommended)

Swap Space Hard disk drives with sufficient space for swap: 2 * RAMFor more information, see SAP Note 171356




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.


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.

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

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

44/140 PUBLIC 03/28/2008






Note

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

End of: HA (UNIX)

n Central instance [page 46]n Database Instance [page 46]

Note

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

3.2.4.1 Requirements for the Central Services Instance

The central services instance host must meet the following requirements:


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 instanceFor more information, see Setting up File Systems [page 54].

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


RAM Only valid for: HA (UNIX)

0.5 GB (minimum), 2 GB (recommended)End of: HA (UNIX)


03/28/2008 PUBLIC 45/140






Network File System (NFS) must be installed.

3.2.4.2 Requirements for the Central Instance

The central instance host must meet the following requirements:



Hard disk space n Hard disk drives with sufficient space for the central instance.For more information, see Setting Up File Systems [page 54] SAP File Systems .



RAM 1 GB (minimum), 3 GB (recommended)





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.


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

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

46/140 PUBLIC 03/28/2008




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 LibraryEnglish SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platformby Key Capability Platform-Wide Services Database Support Oracle SAP DatabaseGuide: Oracle (BC-DB-ORA-DBA) Getting Started with Oracle and the SAP System .

Hard disk space n 20 GB plus space for the SAP data file systemsFor space requirements of the SAP data file systems (sapdata 1 - 4), see thefollowing file:<Export_DVD>/EXP1/DB/ORA/DBSIZE.XML.

NoteThe values listed in DBSIZE.XML are only guiding values. Each sapdata<n>

file can grow up to 10 GB maximum.

For more information about the required disk space per file system, see SettingUp File Systems and Raw Devices ‒ Oracle File Systems [page 57]

n 4.3 GB of temporary disk space for every required installation DVD you haveto copy to a local hard disk.


03/28/2008 PUBLIC 47/140





RAM 500 MB (minimum), 1 GB (recommended)2 GBThe default value used by SAPinst is 50 percent of the entire RAM.Depending on the amount of data involved, the requirements might change.You can do one of the following to get a more precise sizing definition thatreflects your particular system load:n Contact a hardware vendor. The vendor analyzes the load and calculates

suitable hardware sizing.n Contact the person in charge of installation or your Oracle Competence

Center.

Swap Space Hard disk drives with sufficient space for swap: 2 * RAM, at least 20 GBHard disk drives with sufficient space for swap: 2 * RAMFor more information, see SAP Note 171356



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

3.2.5 Requirements for a Dialog Instance

The dialog instance host must meet the following requirements:

48/140 PUBLIC 03/28/2008







Hard disk space n Hard disk drives with sufficient space for the dialog instance.For more information, see Setting up File Systems [page 54].



RAM 500 MB minimum, 1 GB recommended

Swap Space Hard disk drives with sufficient space for swap: 2 * RAM, at least 20 GBFor more information, see SAP Note 171356



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.

3.2.6 Checking and Modifying the Linux Kernel

If you are using a Linux kernel version certified by SAP, you do not need to modify the Linux kernel.To check the Linux kernel version, enter this command:uname –a

For more information about the Linux kernel versions certified by SAP, see SAP Note 171356.Check the Linux kernel parameters for your Linux distribution according to one the following SAPNotes:

03/28/2008 PUBLIC 49/140


http://service.sap.com/swdc



n RHEL4: SAP Note 722273n RHEL5: SAP Note 1048303n SLES9: SAP Note 797084n SLES10: SAP Note 958253

3.2.7 Setting up Swap Space for Linux

You created partitions of the type “swap” when you scheduled the hard disk(s) during the installationof your Linux distribution.The Linux kernel usually does not require much swap space, since other limits have already beenreached before the swap space has reached full capacity (“late swap allocation”). However, if younotice the need for more swap space when using SAP software, you can use the distribution-specifictools to increase your swap space at any time.

PrerequisitesMake sure that the UNIX kernel is already configured and the other prerequisites are met as describedin Requirements for Linux [page 41] and in Checking and Modifying the Linux Kernel [page 49].

Procedure

1. To check the allocated swap space, enter the following command:swapon -s

Recommended total size: Twice the main memory structure (2 x RAM).If possible, use an entire physical disk as a swap space partition.

2. If required, configure swap space as follows:n On Red Hat Linux:

Check the documentation provided by Red Hat.n On SUSE LINUX, enter one of the following commands:

l yast

l yast2

Note

You can configure multiple swap partitions up to a maximum of 32.

50/140 PUBLIC 03/28/2008





3 Preparation3.3 Creating Operating System Users

3.3 Creating Operating System Users

3.3.1 Network Information Service

If you use Network Information Service (NIS), you need to distribute users over the network.

Caution

If you do not create users manually, SAPinst creates them automatically during the installationAll usersmust have identical environment settings. If you change the environment delivered bySAP, such as variables, paths, and so on, SAP does not assume responsibility.

SAPinst checks all required users, groups, and services on the local machine. If you manage users,groups or services network-wide in your company, we recommend that you create the user andgroup NIS entries before running SAPinst as described in Creating Operating System Users and GroupsManually (Optional) [page 51].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.

3.3.2 Creating Operating System Users and Groups

If you do not want SAPinst to create operating systems users, groups and services, you can optionallycreate them manually before the installation.If you want to use global accounts that are configured on a separate host, you start SAPinst andchoose Life Cycle Management Preparation Operating System Users and Groups . For more information,see Running SAPinst on UNIX [page 75].

Users and Groups

SAPinst checks whether the required users and groups already exist. If not, it creates new users andgroups as necessary.SAPinst chooses available user IDs and group IDs unless you are installing a dialog instance. On adialog instance you have to enter the same IDs as on the central instance host.As a general requirement, the user IDs and the group IDs must be the same on all hosts.

03/28/2008 PUBLIC 51/140

3 Preparation3.3 Creating Operating System Users

Caution

If you use NFS-V4 file system, then you have to create the ora<dbsid> user on the NFS server. Youcan do this either manually or by running Operating System Users and Groups. This user must have thesame user ID 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 SAP users and groups must be identical for all serversbelonging to the same SAP system.This does not mean that all users and groups have to be installed on all SAP servers.

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.

Users and Groups

User Primary Group Additional Group(s) Comment

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

<smdsid>adm sapsys sapinst Diagnostics Agentadministrator

ora<dbsid> dba oper, sapinst Database administrator

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 do not use central user management (for example, NIS),and you use local operating system user accounts instead, user <sapsid>adm and the databaseoperating system usermust have the same password on all hosts.

Groups and Members

Groups Members

sapsys <sapsid>adm

oper <sapsid>adm, ora<dbsid>

dba <sapsid>adm, ora<dbsid>

sapinst <sapsid>adm, ora<dbsid>

52/140 PUBLIC 03/28/2008

3 Preparation3.4 Setting Up File Systems and Raw Devices

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

More InformationCreating Linux Groups and Users (Optional) [page 53]

3.3.3 Creating Linux Groups and Users (Optional)

You can create and manage Linux users using one of the following graphical tools:

n Red Hat Linux:l RHEL4 and higher:

system-config-users

n SUSE Linux:l SLES9 and higher:

yast or yast2

Task Command

Creating groups groupadd

Modifying groups groupmod

Deleting groups groupdel

Creating users useradd

Modifying users usermod

Deleting users userdel

More Information

For more information about the users and groups that are created either by SAPinst or manually, seeCreating Operating System Users and Groups Manually (Optional) [page 51].

3.4 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 54]n Oracle Directories [page 57]n Setting Up Standard File Systems for Linux [page 60]

03/28/2008 PUBLIC 53/140


3.4.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 whichdirectories 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 21].


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

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

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.

54/140 PUBLIC 03/28/2008


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.

03/28/2008 PUBLIC 55/140


SAP Directories

Directory Description Space Required

<sapmnt>/<SAPSID> Software and data for one SAP systemThis directory is physically located on the SAP global host.In homogeneous systems, you need to mount it via NFS(Network File System) for all hosts belonging to the sameSAP system. It contains the following subdirectories:n exe

This directory contains executable kernel programs.If you install an SAP systemwith distributed instances,you have to share this directory for all hosts withthe same operating system. For more information,see Prerequisites Before Starting SAPinst: Distributed Instances[page 73].

n global

This directory contains log files.If you install an SAP systemwith distributed instances,you have to share this directory for all hosts. Formore information, see Prerequisites Before Starting SAPinst:Distributed Instances [page 73].

n profile

This directory contains the start and operationsprofiles of all instances.If you install an SAP systemwith distributed instances,you have to share this directory for all hosts. Formore information, see Prerequisites Before Starting SAPinst:Distributed Instances [page 73].

n Central instance:1.5 GB

nOnly valid for: HA (UNIX)

Central services instance(High Availability only):1.0 GBEnd of: HA (UNIX)

n Dialog instance:This directory ismounted from theglobal host.

/usr/sap/<SAPSID> Instance-specific data, symbolic links to the data for onesystemThis directory contains files for the operation of a localinstance.There is a subdirectory <INSTANCE_NAME> for each instanceinstalled on the local instance host. The directory SYScontains only soft links to appropriate directories in/<sapmnt>/<SAPSID>/ for storing data used by severalinstances.There are subdirectories of /usr/sap/<SAPSID>/SYS withsymbolic links 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 theinstallation.

n Central instance ordialog instance:1.5 GB

nOnly valid for: HA (UNIX)

central services instance(High Availability only):1.0 GBEnd of: HA (UNIX)

56/140 PUBLIC 03/28/2008



Executables located in/usr/sap/<SAPSID>/SYS/exe/runare replicated by sapcpe to the exe directory of instancesof the type <INSTANCE_NAME> and ASCS<No>.

NoteMake sure that sufficient space is available in directory/usr/sap/<SAPSID>/<INSTANCE_NAME>, since this storesSAP traces for the instance. Changes in SAP systemprofiles can also affect the disk space.

/usr/sap/trans Global transport directory for all SAP systemsFor more information about exporting and mountingthe global transport directory, see Exporting and Mounting theGlobal Transport Directory [page 61]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 betweenthe SAP systems in your system landscape. For moreinformation, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library

English SAP NetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key CapabilitySoftware Life Cycle Management Software Logistics Change andTransport System

n For the installation ofall instances: 500 MB

n For the use of allinstances: 2 GB

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

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

03/28/2008 PUBLIC 57/140






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 fordatabase software (staging area)This directory is also used for Oracleupgrades. We recommend that you do notdelete it after the installation.

3.5 GB

/oracle/<DBSID> Home directory of user ora<dbsid>We recommend that /oracle/<DBSID> doesnot reside in the root directory. It mustreside in a file system with support for largefiles.For more information about how to createfile systems larger than 2 GB on youroperating system, see:Setting Up File Systems and Raw Devices for Linux[page 60]Therefore, either create /oracle/<DBSID>as a separate file system with support forlarge files or create /oracle as a file system

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

58/140 PUBLIC 03/28/2008



with support for large files and create/oracle/<DBSID> as a directory in /oracle.

/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.0GB

n All other instances:200 MBMake sure that this filesystemhas 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 Oracleoffline redo logsUse a separate disk for the file system/oracle/<DBSID>/oraarch.The file system /oracle/<SAPSID>/saparch

still remains but now only contains brbackuplog files. /oracle/<SAPSID>/saparch isautomatically created by SAPinst.

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

requires at least 400 MBfree disk space. For theoperation of your SAPsystem, we recommendthat the archive directoryprovides enough spacefor archives between twobackups. In a productionsystem, the amountarchived each day isbetween 300 MB and 1 GB.

/oracle/<DBSID>/sapreorg Working directory for databaseadministration

1.5 GB

/oracle/<DBSID>/sapdata1 SAP data




For space requirementsof the SAP data filesystems required forthe installation, see thefollowing file:<Export_DVD>/EXP1/

DB/ORA/DBSIZE.XML.See also SAP Note 972263Pre-Installation File

requirements of Oracle sapdatafile systems

03/28/2008 PUBLIC 59/140



3.4.3 Setting Up Standard File Systems and Raw Devicesfor Linux

This section describes how to set up standard files systems for Linux.

Note

We do not recommend that you perform the installation of an SAP system using raw devices. Formore information, see SAP Note 405827.If you still want to use raw devices, contact Linux support for information about how to set upraw devices on Linux.

PrerequisitesThe following table shows the variables and their corresponding values.

Variables in Standard File Systems

Variable Description

<diskname> Full path of disk, for example /dev/sda

<mountpointname> Full path of a mount point, for example,/oracle/<DBSID>/sapdata1

Procedure

1. Create an empty file system.

Example

Example for ext2 file system:mke2fs —b 4096 /dev/<device>

2. Create a mount point.mkdir <mountpointname>

3. Add a line to /etc/fstab.

Example

Example for the ext2 file system:/dev/<device> <mountpointname> ext2 defaults 1 2

4. Mount the file system:mount <mountpointname>

60/140 PUBLIC 03/28/2008


3 Preparation3.5 Exporting and Mounting the Global Transport Directory

3.5 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 InformationExporting Directories via NFS for Linux [page 61]

3.6 Exporting and Mounting Directories via NFS for Linux(Optional)

To export directories via NFS, perform the following steps (the following assumes that the centralinstance host is the NFS server):

1. Log on as user root to the NFS server.2. Make sure that your host is configured as NFS server as follows:n On Red Hat Linux, make sure that the output of the command:

chkconfig --list nfs

looks as follows:

03/28/2008 PUBLIC 61/140

3 Preparation3.6 Exporting and Mounting Directories via NFS for Linux (Optional)

nfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off

n On SUSE Linux, enter the following command:l SLES9 and higher:

yast or yast2You can set up your host as NFS server as follows:n On Red Hat Linux, enter the following command:l RHEL4 and higher:

system-config-users

n On SUSE Linux, enter the following command:l SLES9 and higher:

yast or yast23. To export a directory from a local file system, you can proceed as follows:n On Red Hat Linux, use the following tool:l RHEL4 and higher:

system-config-nfs

n On SUSE Linux, use the following tool:l SLES9 and higher:

yast2

n Perform the configuration manually.To perform the configuration manually, proceed as follows:a) To add a line to the local file /etc/exports, enter the following:

#/etc/exports

<directory> <hostname>(<options>)

Note

n There must not be a blank between <hostname> and <options>. Otherwise, the directoryis exported with default option (ro) (read-only) to the host specified by <hostname> andwith the option specified by <options> to all other hosts.

n To export directories on Linux with root permissions, use the option no_root_squash. Forsecurity reason, only use this option during installation.

Example

n To export the directory /usr/sap/trans in read-only mode to the NFS clienthost.wdf.sap-ag.de, enter the following:#/etc/exports

/usr/sap/trans host.wdf.sap-ag.de(ro)

n To export the directory in read-write mode with root permissions, enter the following:#/etc/exports

/usr/sap/trans host.wdf.sap-ag.de(rw,no_root_squash)

n To export the directory to all NFS clients of the domain using a wildcard (*), enter the

62/140 PUBLIC 03/28/2008

3 Preparation3.7 Installing the Front-End Software

following:#/etc/exports

/usr/sap/trans *.wdf.sap-ag.de(rw)

b) To activate the changes (that is, inform the NFS daemon about the changes performed in/etc/exports), enter the following command:exportfs -r

c) To get a list of all currently exported directories, enter the following command:exportfs -v

For further details, consult the man page by entering man exports.4. Log on as user root to the host where the file system should be imported.5. To mount the file systems, enter the following command:

mount <nfs_server>:<file_system> <mount_point>

Example

mount <nfs_server>:/usr/sap/trans /usr/sap/trans

3.7 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 the SAP Front-End installation software NW SAPSetup you can optimize the deployment of SAPGUI to thousands of clients. You can easily tailor installation packages to match your requirements,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.8 Generating the SAP Solution Manager Key

You need to generate the Solution Manager key because the installation tool prompts for it duringthe installation. Without this key, the installation process cannot continue.For more information, see SAP Note 805390.

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.

03/28/2008 PUBLIC 63/140






3 Preparation3.9 Installing the Java Runtime Environment

b) Install SAP Solution Manager as described in the documentation Installation Guide ‒ SAP SolutionManager <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.

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

3.9 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 both for SAPinst and the SAPinst GUI.

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 itwith the SAPinst GUI from a local host. If you want to perform a remote installation, see Performinga Remote Installation with SAPinst [page 84]. In this case, you need at least a JRE on the local host tostart the SAPinst GUI there.

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:

64/140 PUBLIC 03/28/2008









3 Preparation3.10 Preparing and Mounting the Installation Media

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.

Note

If you use a Sun Java VM, you have to perform the following:Edit the configuration file $JAVA_HOME/jre/lib/security/java.security and replace entrysecurerandom.source=file:/dev/random with securerandom.source=file:/dev/urandom.

3.10 Preparing and Mounting the Installation Media

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

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 documentMaster Guide ‒ SAPERP 6.0 powered by SAP NetWeaver 7.0 at:http://service.sap.com/erp-inst SAP ERP 6.0 Master Guide 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:

03/28/2008 PUBLIC 65/140





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

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

Database instance n Installation Master DVDn Kernel 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 DVDn SAP ERP Central Component Export 1 DVDn SAP ERP Central Component Export 2 DVD

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

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.

66/140 PUBLIC 03/28/2008


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.

3.10.2 Downloading Installation DVDs from SAP ServiceMarketplace (Optional)

You normally obtain the installation DVDs as part of the installation package from SAP.However, you can also download installation DVDs from SAP Service Marketplace at: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 on SAP Service Marketplace at http://service.sap.com/swdc. You need at least SAPCAR700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longerunpack 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...

03/28/2008 PUBLIC 67/140









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.

Note

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

3.10.3 Mounting a CD / DVD for Linux

Note

The placeholder <medium-mountdir> is used for either <cd-mountdir> or <dvd-mountdir>.

Procedure

1. Log on as user root.2. To create a mount point for the CD / DVD, enter the following command:

mkdir <medium-mountdir>

Example

<medium-mountdir> is /sapcd

3. To mount the first CD / DVD device, enter the following command:mount -t iso9660 -r <device> <medium-mountdir>

where <device> is /dev/cdrom for non-SCSI CD devices and /dev/scd<n> for SCSI drives with thedevice number <n>.If the file names on the mounted CD / DVD are written in lowercase letters, remount the CD /DVD with the following commands:umount <device>

mount -t iso9660 -r -o map=off <device> <medium-mountdir>

68/140 PUBLIC 03/28/2008

4 Installation

4 Installation

Note

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

This section provides information about the steps that you have to perform to install your SAP system

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 71].3. You install your SAP system using SAPinst [page 75].

Note

This note does not apply to the installation of a Java Add-In to an existing ABAP system:Do not install the Oracle database software before you run SAPinst.SAPinst stops and prompts you to install the Oracle database [page 87] 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 preparing the installation of switchover units [page 34].n You have set the environment variable SAPINST_USE_HOSTNAME [page 74] to specify the virtual host

name for the installation. Alternatively you can specify the virtual host name in the commandto start SAPinst.

03/28/2008 PUBLIC 69/140

4 Installation4.1 Performing a High-Availability Installation

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

3. Set up the user environment on the standby node, host B.For more information, see Creating Operating System Users and Groups Manually [page 51]. Make sure thatyou use the same user and group IDs as on the primary node. Create the home directories of usersand copy all files from 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 (SCS), which is protected by the cluster.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.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 servicesinstances (SCS and ASCS), which are 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 activities described in High Availability: Post-Installation Steps [page 103].

End of: HA (UNIX)

70/140 PUBLIC 03/28/2008

4 Installation4.2 Prerequisites before Starting SAPinst

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

Prerequisites

n Make sure that you have defined the most important SAP system parameters as described in BasicSAP System Parameters [page 21] 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 40].

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. Make sure that your operating system does not delete the contents of the temporary directory/tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, forexample by using a crontab entry.

03/28/2008 PUBLIC 71/140


Note

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.Make sure that the temporary directory has the permissions 777.The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. Theseexecutables 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. Make sure that you have at least 60MB of free space in the installation directory for each installationservice. In addition, you need 200 MB free space for the SAPinst executables. If you cannot provide200 MB free space in the temporary directory, you can set one of the environment variables TEMP,TMP, or TMPDIR to another directory with 200 MB free space for the SAPinst executables.

Shell Used Command

Bourne shell (sh) TEMP=<directory>

export TEMP

C shell (csh) setenv TEMP <directory>

Korn shell (ksh) export TEMP=<directory>

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

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

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:

72/140 PUBLIC 03/28/2008


n In csh execute limit

Output Properties

cputime unlimited

filesize unlimited

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

4.2.2 Prerequisites before Starting SAPinst: DistributedInstances

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.

03/28/2008 PUBLIC 73/140


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

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, see Exporting Directories via NFS for Linux [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 [page61]. 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


4.2.3 Prerequisites Before Starting SAPinst: High Availability

For a high-availability (HA) SAP system you can set the environment variable SAPINST_USE_HOSTNAMEto specify the virtual host name before you start SAPinst.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].

74/140 PUBLIC 03/28/2008

4 Installation4.3 Installing an SAP System Using SAPinst

ProcedureSet SAPINST_USE_HOSTNAME to the virtual host name of the machine on which you are installingan SAP instance.End of: HA (UNIX)

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 (Optional) [page 84]n Starting SAPinst GUI Separately (Optional) [page 85].n Entries in the Services File Created by SAPinst [page 87]

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 runningon the same host. If required, you can instead perform a remote installation with SAPinst [page 84], whereSAPinst GUI is running on a separate host from SAPinst and the GUI server.When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects via a secureSSL connection to the GUI server and the GUI server connects to SAPinst.

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.For more information about mounting DVDs, seeMounting a CD / DVD for Linux [page 68].

03/28/2008 PUBLIC 75/140


3. Start SAPinst from the Installation Master DVD in one of the following ways:n Using the default installation directory (recommended)

Enter the following commands:cd <Installation Master_DVD>/IM_<OS>

./sapinst


Note

If you are installing a high-availability system and you have not already set the environment parameterSAPINST_USE_HOSTNAME [page 74] to specify the virtual host name, you can start SAPinstas follows:./sapinst SAPINST_USE_HOSTNAME=<virtual host name>

End of: HA (UNIX)

Caution

Make sure that your operating system does not delete the contents of the temporary directory/tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, forexample by using a crontab entry.

Caution

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

n Using an alternative installation directoryIf you want to use an alternative installation directory, set the environment variable TEMP,TMP, or TMPDIR.For more information, see Prerequisites before Starting SAPinst: All Instances [page 71].

76/140 PUBLIC 03/28/2008


Note

n During the installation, the default ports 21200 and 21212 are used for communication betweenSAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to communicate with the GUIserver. The GUI server uses port 21212 to communicate with SAPinst GUI. You get an errormessage 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>.n To get a list of all available SAPinst properties, start SAPinst as described above with the option

-p:./sapinst -p.

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

n Software Life-Cycle OptionsThe following tables provide more information about these installation options:n SAP Systems

You use this option to install an SAP system with usage types or software units by choosing:l Central system:

<SAP system> SAP Systems <Database> Central System

l All other system variants:<SAP system> SAP Systems <Database> <System Variant> Based on <technical stack>

You can install the following system variants:l Central Systeml Distributed System

l


High Availability SystemEnd of: HA (UNIX)

The following tables provide an overview of the installation options available for these systemvariants:

Note

l Choose the corresponding installation options from the tree structure exactly in theorder they appear for each system variant.

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

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

See table Software Life-Cycle Options below.

03/28/2008 PUBLIC 77/140


Installation Services for a Central System

Installation Service Remarks

Central System Installs a complete SAP system including the following instances on onehost:l Database instancel Central instanceYou can install a central system in the following parameter modes:l Typical Mode

If you choose Typical, the installation automatically uses defaultsettings. You only have to respond to a small selection of prompts.However, you can change any of the default settings on the parametersummary screen.

l Custom ModeIf you choose Custom, the installation prompts you for all parameters.At the end, you can change any parameter on the parameter summaryscreen.

Installation Services for a Distributed System

Installation Services Remarks

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:l Preparing the file systeml Creating the profilesl Installing the executables

Database Instance Mandatory step in installing a distributed SAP system.Installs a database instance.Youmust 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. Youcan choose the usage types or software units on thescreen SAP System > Software Units.

You must have finished the database instance installation.

78/140 PUBLIC 03/28/2008


Installation Services for a High Availability System

Installation Services Remarks

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

NoteIf you want to use 32-bit SAP NetWeaver components, first checkwhether these components can run on 64-bit operating systems. If so, werecommend you to use 64-bit systems. If not, you can install an SAP dialoginstance on 32-bit operating systems to run these components. For allother SAP instances, you must use 64-bit systems.

n Software Life-Cycle OptionsYou use this option to perform the following tasks or to install the following components:


Additional PreparationOptions

These preparation tasks comprise:l 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 ofyour SAP system.

l Prerequisites CheckChecks your hardware and software requirements before youstart the installation.Otherwise, SAPinst automatically checks the hardware andsoftware requirements during the installation with the PrerequisiteChecker. If any changes are necessary to the SAP system or operatingsystem settings, SAPinst automatically prompts you. For moreinformation, see Running the Prerequisites Checker in Standalone Mode [page40].

03/28/2008 PUBLIC 79/140



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

NoteIf you want to use 32-bit SAP NetWeaver components, first checkwhether these components can run on 64-bit operating systems. Ifso, we recommend you to use 64-bit systems. If not, you can installan SAP dialog instance on 32-bit operating systems to run thesecomponents. For all other SAP instances, youmust use 64-bit systems.

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 canuse this setup.

NoteThe option Active Directory Configuration is only available forWindows.

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

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,or optional standalone units.For more information, see Deleting an SAP System Using SAPinst [page 124]

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:

80/140 PUBLIC 03/28/2008

http://service.sap.com/instguidesnw70

http://service.sap.com/instguidesnw70


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

Recommendation

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

9. We recommend you to 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 123].

4.3.2 Using SAPinst GUI

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

03/28/2008 PUBLIC 81/140


SAPinst GUI Functions

Input Type Label Description

Function key F1 Displays detailed information about each input parameter.

Menu option File Log off Stops the SAPinst GUI, but SAPinst and the GUI server continuerunning.

NoteIf for some reason you need to log off during the installationfrom the host where you control the installation with SAPinstGUI, the installation continues while you are logged off. You canlater reconnect to the same SAPinst installation from the same oranother host. For more information, see Starting SAPinst GUI Separately[page 85].

Menu option File View Log Displays the installation log (sapinst_dev.log)

Menu option File Exit Cancels the installation with the following options:n Stop

For more information, see the description of the message buttonbelow.

n ContinueFor more information, see the description of the message buttonbelow.

Message button Retry Performs the installation step again (if an error has occurred).

Message button View Log Displays the installation log (sapinst_dev.log)

Message button Stop Stops the installation (SAPinst GUI, SAPinst and the GUI server)without further changing the installation files. You can continue theinstallation later from this point.

Message button Continue Continues with the option you have chosen before.

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 dialog or processing 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 about the choices listed inthe table below as well as a path to a log file that contains detailed information about the error.

n You interrupted the installation by choosing Exit in the SAPinst menu.

The following table describes the options in the dialog box:

82/140 PUBLIC 03/28/2008


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 again, SAPinst displays the samedialog box 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.

Continue SAPinst continues the installation from the current point.

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.

03/28/2008 PUBLIC 83/140


Note

If there is only one 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.

Alternative Behavior

Run a new Installation SAPinst does not continue the interrupted installation. Instead, it movesthe content of the old installation directory and all installation-specificfiles to the backup directory. Afterwards, you can no longer continuethe old installation.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds> (for example,log_01_Oct_2003_13_47_56).

Continue old installation SAPinst continues the interrupted installation from the point of failure.

4.3.4 Performing a Remote Installation with SAPinst(Optional)

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.

Prerequisites

n The remote host meets the prerequisites before Starting SAPinst [page 71].n Both computers are in the same network and can “ping” each other.

To test this:l Log on to your remote host and enter the command ping <local host>.l Log on to the local host and enter the command ping <remote host>.

Procedure

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

Caution


2. Mount the Installation Master DVD.3. Enter the following commands:

cd <Installation_Master_DVD>/IM_<OS>

84/140 PUBLIC 03/28/2008


./sapinst -nogui

For more information, 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.

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

4.3.5 Starting SAPinst GUI Separately (Optional)

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 you want to run SAPinst GUI on a different host from SAPinst and the GUI server, you have tostart SAPinst GUI separately.

PrerequisitesYou have installed the Java Runtime Environment [page 64] on the host on which you want to start SAPinstwithout SAPinst GUI.

Starting SAPinst GUI on a Windows Platform

1. Log on as a member of the local administrators group.2. Insert the SAP Installation Master DVD into your DVD drive.3. Open a command prompt and change to the relevant directory:

<DVD drive>:\IM_WINDOWS_<platform>

4. Start SAPinst GUI in one of the following ways:n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following

command:startinstgui.bat

SAPinst GUI uses the local host as default.n If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation),

enter the following command:startinstgui.bat -host <host_name>

<host_name> is the host name of the installation host.

03/28/2008 PUBLIC 85/140


Note

l If you enter the command without additional parameters, SAPinst GUI uses the local hostas default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. SinceSAPinst and the GUI server are running on another host, SAPinst GUI cannot connect andthe SAP 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 installationfrom your local host.

l For a list of options to start SAPinst GUI, change to the same directory as your SAPinstexecutable and enter the command startinstgui.bat -h.

Starting SAPinst GUI on a UNIX Platform

1. Log on as user root.

Caution


2. Mount your installation DVD.

Note

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

3. To change to the mount directory enter the following command:cd <Installation_Master_DVD>/IM_<OS>

4. Start the SAPinst GUI in one of the following ways:n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following

command without additional parameters:./startInstGui.sh

SAPinst GUI uses as default the local host.n If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation),

enter the following command with additional parameters:./startInstGui.sh -host <host_name>

<host_name> is the host name of the installation host.

86/140 PUBLIC 03/28/2008

4 Installation4.4 Oracle Database Software Installation

Note

l If you enter the command without additional parameters, SAPinst GUI uses the local hostas default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. SinceSAPinst and 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 host on which SAPinst is running and choose Log on.The first dialog of the installation appears and you can perform the remote installationfrom your local host.

l For a list of options to start SAPinst GUI, change to the same directory as your SAPinstexecutable and enter the command ./startInstGui.sh -h.

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

sapdbXXs = 47XX/tcp

sapgwXX = 33XX/tcp

sapgwXXs = 48XX/tcp

where XX is set from 00 to 99.

Note

If there is more than one 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 88].2. You run the Oracle Universal Installer [page 88]3. You install the current patch set [page 90]4. You install required interim patches [page 91]

03/28/2008 PUBLIC 87/140


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

88/140 PUBLIC 03/28/2008




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

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.

03/28/2008 PUBLIC 89/140


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.

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

90/140 PUBLIC 03/28/2008




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

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.

03/28/2008 PUBLIC 91/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:

1. You check whether you can log on to the application server [page 94].

Note

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

2. You install the SAP license [page 94].3. You install the SAP Online Documentation [page 95].4. You configure the remote connection to SAP support [page 95].5. On the central instance host, you apply the latest kernel and Support Packages [page 96].6. You perform initial ABAP configuration [page 97].7. On the database instance host, you perform the Oracle-specific post-installation steps [page 100].

Caution

This step does not apply to the installation of a Java Add-In for an existing ABAP system.

8. You perform the client copy [page 100]9. You perform a full backup of the installation [page 101].10. You implement ERP ABAP Add-On Components [page 103].

11.


You perform the required post-installation steps for high availability [page 103].End of: HA (UNIX)

12. You ensure user security [page 104].13. You can now start with the manual configuration of your IT scenarios for which you can find the

appropriate documentation in the SAP Solution Manager [page 106].

03/28/2008 PUBLIC 93/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 using the following standard users.

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 also enter the command guilogon in the SAP GUI installation directory to startSAP 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 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 four weeksfrom the date of installation.

94/140 PUBLIC 03/28/2008

5 Post-Installation5.3 Installing the SAP Online Documentation

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.

ProcedureFor more information about the installation procedure for the SAP license, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library 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 103].End of: HA (UNIX)

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

5.3 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.4 Configuring Remote Connection to SAP Support

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

03/28/2008 PUBLIC 95/140




http://service.sap.com/licensekey



http://help.sap.com

http://service.sap.com/remoteconnection



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

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.

Note

The following are available exclusively through the Maintenance Optimizer in SAP SolutionManager:

n All corrective software packages, including Support Packages (Stacks) for SAP NetWeaver 7.0 andsubsequent versions

n All applications based on this software (including SAP Business Suite 2005), released after April2, 2007

For more information about the Maintenance Optimizer, seehttp://service.sap.com/solutionmanager SAP Solution Manager in Detail

Change Request Management Maintenance Optimizer .

Caution

Before you apply support packages, make sure that you read the release notes for your SAP system.You can find these on SAP Service Marketplace at http://service.sap.com/releasenotes. Therelease notes might include information about steps you have to perform after you have appliedthe support packages.

Caution

Make sure that the entry DIR_CT_RUN exists in the instance profile. Otherwise you cannot restart thesystem after patches have been applied.See also Setting Up File Systems [page 54].

Caution

You must have applied all ABAP Support Packages, before you run the configuration wizard.

You use the Support Package Manager to apply the latest ABAP support packages.For more information about the Support Package Manager and how to use this tool, seehttp://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management SoftwareMaintenance Support Package Manager

PrerequisitesTo extract the downloaded SAR files make sure that you use the latest SAPCAR version, which youcan find on SAP Service Marketplace at http://service.sap.com/swdc. You need at least SAPCAR

96/140 PUBLIC 03/28/2008













5 Post-Installation5.6 Performing Initial ABAP Configuration

700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longerunpack current SAR files. For more information, see SAP Note 212876.

Procedure

1. Apply the latest kernel.You must always replace the installed kernel with the latest kernel from SAP Service Marketplace.In particular, you must replace the installed kernel if:n You installed the kernel executables locally on every host.n Your central instance host runs on a different operating system than your dialog instance host.For more information about how to download a kernel, see SAP Note 19466.

2. Apply Support Packages.a) For up-to-date information about recommended combinations of Support Packages and

patches, see SAP Service Marketplace at:http://service.sap.com/sp-stacks

For up-to-date release information on Support Package Stacks, see SAP Note 849887.b) Alternatively, you can download Support Packages from SAP Service Marketplace at:

http://service.sap.com/patches

c) Apply the ABAP Support Packages to your SAP system with the help of the Support PackageManager (formerly called SAP Patch Manager, transaction SPAM).

For more information about the availability of Support Packages, see the SAP Service Marketplaceat:http://service.sap.com/ocs-schedules

Note

The SAP Note Assistant lets you load, implement, and organize individual SAP Notes efficiently. Italso recognizes dependencies between SAP Notes, Support Packages, and modifications.For more information, see the SAP Service Marketplace at:http://service.sap.com/noteassistant

5.6 Performing Initial ABAP Configuration

Here you can find information about how to perform initial ABAP system configuration.

Procedure

1. Go to the following:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability2. Check the documentation on the following configuration steps:n Performing a consistency check

03/28/2008 PUBLIC 97/140










http://service.sap.com/ocs-schedules



http://service.sap.com/noteassistant







When logging on to the system for the first time, you need to trigger a consistency checkmanually. The function is then called automatically whenever you start the system or anapplication server.For more information, see:Solution Life Cycle Management by Key Capability System Management Tools for Monitoring the System

Utilities Consistency Check

n Configuring the transport management systemFor more information, see:Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics

Change and Transport System

n Performing basic operationsFor more information, see the relevant section in Solution Life Cycle Management by Key CapabilitySystem Management :

Operation Section in SAP Documentation

Set up operation modes ‒transaction RZ04

Configuration Operation Modes

Set up logon groups ‒transaction SMLG

Configuration Logon Load Balancing SAP Logon

Set up administrators Background Processing Authorizations for Background Processing

Schedule background jobs Background Processing

Install a printer SAP Printing Guide

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

n Configuring system parametersFor more information about system profiles, which is where work processes and profileparameters are defined, and how to configure them, see:Solution Life Cycle Management by Key Capability System Management Configuration Profiles

l Configuring work processesSAPinst installs SAP systems with a minimum number of work processes. This is only aninitial configuration to get you started after the installation. It is not detailed enough for aproduction system because the optimal number of each type of work process depends onthe system resources and on the number of users working in each SAP system application.For more information about how many work processes to configure and how to set thenumber, see SAP Notes 39412 and 9942.

l Configuring Kernel parametersFor more information about kernel parameter recommendations, see SAP Notes 146289and 835474.

n Installing languages and performing language transportl Installing languages using transaction I18N:

98/140 PUBLIC 03/28/2008






u If you want to use English only, you must activate the default language settings once.

u If you want to use languages other than English, you must install them and activate thelanguage settings.

For more information about configuring the language settings, see the onlinedocumentation in transaction I18N at I18N Menue I18N Customizing .

l Performing language transport using transaction SMLT:For more information about performing the language transport using transaction SMLT,see:Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics

Change and Transport System Language Transport

n Using and Configuring the SAP ITS Integrated in ICMSince SAP NetWeaver 2004 (’04), the SAP Internet Transaction Server (SAP ITS) is integratedin the SAP NetWeaver Application Server ABAP (AS ABAP) as an Internet CommunicationFramework (ICF) service. You can access this, like other services, with the InternetCommunication Manager (ICM). With the SAP ITS integrated in AS ABAP, the Web browsernow communicates directly with the SAP system. Furthermore, all SAP ITS-related sources,such as service files, HTML templates, or MIME files, are now stored in the database of thesystem.The SAP ITS supports the following functions:l SAP GUI for HTML

l Internet Application Component (IAC) runtime or Web Transaction technologyFor more information about how to configure the integrated SAP ITS, see:Application Platform by Key Capability ABAP Technology UI Technology Web UI Technology SAP

Internet Transaction Server SAP ITS in the SAP Web Application Server ConfigurationFor more information about the ITS memory requirements, see SAP Note 742048.

n Maintaining address dataFor more information about maintaining the company address in your SAP system usingtransaction SU01, see:Application Platform by Key Capability Business Services Business Address Services (BC-SRV-ADR)

Addresses in User Administration Maintenance of Address Data

Note

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

n Configuring business applicationsFor more information about how to prepare the SAP system for using business applications,which includes customizing the ABAP system and the business components, see Solution LifeCycle Management by Key Capability Customizing .

03/28/2008 PUBLIC 99/140


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

5.7 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.For information on Oracle database configuration and administration, see the documentation inthe SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaverLibrary SAP NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide ServicesDatabase Support Oracle .

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

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.

100/140 PUBLIC 03/28/2008






5 Post-Installation5.9 Performing a Full Installation Backup

7. Deactivate kernel user SAP*:a) Reset login/no_automatic_user_sapstar to 1.b) Restart the application server.

For more information, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability Solution Life Cycle Management by Key Capability Software Lifecycle Management SoftwareLogistics Change and Transport System BC ‒ Client Copy and Transport

5.9 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 100].n You have logged on [page 94] as user <sapsid>adm and stopped the SAP system and database [page 119].

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.

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:

03/28/2008 PUBLIC 101/140




5 Post-Installation5.9 Performing a Full Installation Backup

tar —cf — <file_system> | compress —c > <tape_device>

n Saving to the file system:tar —cf — <file_system> | compress —c > ARCHIVENAME.tar.Z

Note

You can also execute the following command to manually create a compressed GNU tar

archive that contains all installed files and save it to the file system:tar —czf <ARCHIVENAME>.tgz <file_system>

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 in 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 ton restore the data from tape:

cat <tape_device> | compress —cd | tar —xf —

n restore the data from the file system:cat ARCHIVENAME.tar.Z | compress —cd | tar —xf —

Note

If you want to restore the data from a GNU tar archive, you have to execute the followingcommand:tar —xzf <ARCHIVENAME>.tgz

Performing a Full Database Backup

1. Configure your third-party backup tool, if used.2. Perform a full database backup (preferably offline).

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 English SAP NetWeaver Library SAP

NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide Services DatabaseSupport Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA)

102/140 PUBLIC 03/28/2008




5 Post-Installation5.10 Implementing ERP ABAP Add-On Components

5.10 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.11 High Availability: Post-Installation Steps

5.11.1 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 two or more cluster nodes (hostmachines) where the message server is enabled to run, you have to order as many license keys [page 94]as you have cluster nodes.When we receive confirmation from your vendor that you are implementing a switchoverenvironment, we provide the required license keys for your system, one 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.

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

03/28/2008 PUBLIC 103/140

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






5 Post-Installation5.12 Ensuring User Security

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.11.2 Taking Precautions for Transport

With a high-availability (HA) installation you need to take precautions before you perform a transport.TPPARAM contains parameter settings for the transport control program tp, which is used for exportsand imports. It also includes the parameter <SID>/dbhost, which is used to address the database host.

ProcedureSet <SID>/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 still allowstransparent operation in the event of a switchover.End of: HA (UNIX)

5.12 Ensuring User Security

You need to ensure the security of the users that SAPinst creates during the installation. For securityreasons, you also need to copy the installation directory to a separate, secure location ‒ such as aDVD ‒ and then delete the installation directory.

Recommendation

In all cases, the user ID and password are only encoded when transported across the network.Therefore, we recommend using encryption at the network layer, either by using the Secure SocketsLayer (SSL) protocol for HTTP connections, or Secure Network Communications (SNC) for the SAPprotocols dialog and RFC.For more information, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Security Network and Transport Layer Security

104/140 PUBLIC 03/28/2008




5 Post-Installation5.12 Ensuring User Security

Caution

Make sure that you perform this procedure before the newly installed SAP system goes intoproduction.

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

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

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 ‒

SYS ‒

OUTLN ‒

Oracle database user

DBSNMP ‒

ABAP Users


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

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

DDIC User exists at least in SAP systemclients 000 and 001.

SAP system user

03/28/2008 PUBLIC 105/140

http://service.sap.com/securityguide



5 Post-Installation5.13 Accessing Configuration Documentation in SAP Solution Manager


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

EARLYWATCH User exists at least in SAP systemclient 066.

SAPCPIC User exists at least in SAP systemclients 000 and 001.

5.13 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 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 4.0 <current support release> 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 4.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.

106/140 PUBLIC 03/28/2008







5 Post-Installation5.13 Accessing Configuration Documentation in SAP Solution Manager

c) Create a project structure and add the required scenarios for your SAP system to your projectstructure with the Business Blueprint transaction SOLAR01,

d) Add your SAP system configuration structures to your project structure with the configurationtransaction SOLAR02.

For more information about creating projects, assigning scenarios to projects, and creatingconfiguration structures, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP Solution ManagerUsing 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.

03/28/2008 PUBLIC 107/140




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 109]n Integration of LDAP Directory Services [page 111]

Post-Installation

n Starting and stopping the SAP system [page 115].n If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access

[page 122].n Configuration of the Connection to a central System Landscape Directory (SLD) [page 123]n Heterogeneous SAP System Installation [page 123]n Troubleshooting [page 123]

Deleting an SAP System

n Deleting an SAP System [page 124]

6.1 Installation of Multiple Components in One Database(Optional)

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.

03/28/2008 PUBLIC 109/140

6 Additional Information6.1 Installation of Multiple Components in One Database (Optional)

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:

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 theSAP Quick Sizer and then adding the requirements together. For more information about the SAPQuick 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.

110/140 PUBLIC 03/28/2008

http://service.sap.com/mcod






6 Additional Information6.2 Integration of LDAP Directory Services (Optional)

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: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 (Optional)

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.

03/28/2008 PUBLIC 111/140





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.

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 English SAP NetWeaver Library SAP

NetWeaver by Key Capability Security Identity Management Identity Management of the Application ServerABAP Configuration of Identity Management Directory 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 on SAP Service Marketplace at:http://service.sap.com/msplatforms Microsoft Windows Server

For more information about the SAP MC and about how to configure it to access LDAP Directories,see the documentation SAP Management Console at:

112/140 PUBLIC 03/28/2008




http://service.sap.com/msplatforms




http://help.sap.com SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver byKey Capability Application Platform by Key Capability Java Technology Administration Manual J2EE EngineJ2EE Engine Administration 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=

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 system

03/28/2008 PUBLIC 113/140

http://help.sap.com


configuration. 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 and Windows platforms, you can also use the SAP MMC for operating andmonitoring 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.

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 <SAP System> Software Life-Cycle Options LDAP Registration Active DirectoryConfiguration . For more information about running SAPinst on Windows, see the documentationInstallation Guide — <your 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.

114/140 PUBLIC 03/28/2008

6 Additional Information6.3 Starting and Stopping SAP System Instances

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:<SAP System> Software Life-Cycle Options LDAP Registration LDAP Support

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

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 115].Apart from using the SAP Management Console (SAP MC) you can also use scripts to start or stopSAP system instances [page 119]

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 (MC). You have to start and stop the database instanceas described in Starting and Stopping the SAP System Using startsap and stopsap [page 119].

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 (MMC).For more information about handling the MMC, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution Monitoring Monitoringin 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.

03/28/2008 PUBLIC 115/140



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.

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 systemmanually as described in RegisteringSystems 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.

116/140 PUBLIC 03/28/2008


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.

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.

03/28/2008 PUBLIC 117/140


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.

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.

118/140 PUBLIC 03/28/2008


More InformationFor more information about the SAP Management Console, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EEEngine J2EE Engine Administration Tools SAP Management Console

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) [page 115] to start or stop the instances ofthe SAP system.

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:

03/28/2008 PUBLIC 119/140




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

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>

120/140 PUBLIC 03/28/2008


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

n If you have a central system, enter the following to stop all instances on the central system host:stopsap


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:

03/28/2008 PUBLIC 121/140

6 Additional Information6.4 Creating a User for LDAP Directory Access (Optional)

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

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 (Optional)

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 section Preparing the Active Directory (Optional) in the Windows installationguide for your SAP system 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

122/140 PUBLIC 03/28/2008

6 Additional Information6.5 Configuring the Connection to a Central System Landscape Directory (SLD)

6.5 Configuring the Connection to a Central SystemLandscape Directory (SLD)

For each system in your landscape that reports data to a central SLD, you have to configure acorresponding SLD data supplier. For more information about the configuration of the SLD datasuppliers and the SLD ABAP API, see the SAP Library at:http://help.sap.com/nw70 SAPNetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management SystemLandscape Directory Configuring Systems to Connect to SLD Connection Between Web AS ABAP Systems and SLDThis documentation is also available in PDF form in the User Manual ‒ SLD of SAP NetWeaver 7.0 at:http://www.sdn.sap.com/irj/sdn/nw-sld

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

6.7 Troubleshooting

The following section(s) describe the steps that you need to performmanually if SAPinst fails:

n Troubleshooting with SAPinst [page 123]

6.7.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 installationn Displays a dialog informing you about the error

03/28/2008 PUBLIC 123/140




http://www.sdn.sap.com/irj/sdn/nw-sld


6 Additional Information6.8 Deleting an SAP System

Procedure

1. To view the log file, choose View Logs.2. If an error occurs during the dialog or processing phase, do either of the following:n Try to solve the problemn Abort the installation with Exit

For more information, see Interrupted Installation with SAPinst [page 82].n 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.

4. If SAPinst GUI does not start, check the file sdtstart.err in the current <user_home> directory.5. If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as

described in Starting SAPinst GUI Separately.

6.8 Deleting an SAP System

The following sections describe how to delete an SAP system.

Note

This description assumes that the installation of your SAP system has been performed using SAPstandard tools according to the installation documentation.

You can choose one of the following options:

n You delete the SAP system using SAPinst [page 124]. However, you still have to delete the databasemanually.

n You delete the SAP system manually [page 127].

6.8.1 Deleting an SAP System Using SAPinst

You can use SAPinst to delete an SAP system.

Caution

SAPinst only stops local instances automatically.Before you delete the database instance of a distributed systemmake sure that you stop all remaininginstances. Youmust stop the instance with the message server only after having entered all SAPinstparameters for the deletion of the 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.1. Run SAPinst to delete the SAP system.

124/140 PUBLIC 03/28/2008


2. Delete the Oracle database software [page 126] manually.n If you want to delete a distributed system, you have to run SAPinst to delete the required

instances locally on each of the hosts belonging to the SAP system in the following sequence:1. Dialog instance(s), if there are any2. Database instance

SAPinst deletes the database instance but you have to delete the Oracle database software [page 126]manually.

3. Central instance

4.

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

High Availability only: Central services instanceEnd of: HA (MSCS);HA (UNIX)

Caution

You cannot delete an SAP system remotely.

Caution

If you delete network-wide users, groups, or service entries in an environment with NetworkInformation System (NIS), other SAP installations might also be affected. Before you delete users,groups, or service entries, make sure that they are no longer required.

Caution

When you delete an SAP system using SAPinst, system directories mounted from an NFS serverare not deleted.You must either delete them manually [page 127] or run SAPinst on the NFS server.

6.8.1.1 Running SAPinst to Delete an SAP System

This procedure tells you how to run the Uninstall option of SAPinst.

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 <sid>adm of the other SAP system andstart saposcol from there using the command saposcol -l.

Procedure

1. Start SAPinst and on theWelcome screen, choose:

03/28/2008 PUBLIC 125/140


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 SAP instances in the correct order, as described in Deleting an SAPSystem Using SAPinst [page 124].

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.

3. Delete the database software manually [page 126].4. 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.

6.8.1.2 Deleting the Oracle Database Software

You use the Uninstall functionality of the Oracle Universal Installer (OUI) to complete the deletionof the Oracle database software.

Note

This section only applies if you have deleted your SAP system using the Uninstall service of SAPinst.If you delete your SAP system manually, you delete the Oracle database instance as described inDeleting an Oracle Database Instance [page 129].

Procedure

1. Start the OUI with the user ora<dbsid> by entering one of the following:


./runInstaller

126/140 PUBLIC 03/28/2008



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

6.8.2 Deleting an SAP System Manually

Deleting a Complete SAP System Manually

1. You delete the SAP instances [page 127] in the following sequence:a) Dialog instances, if there are anyb) Central instancec) Central services instance, if there is one

2. You delete the remaining installation files and directories on the host(s) where you deleted your SAP instance(s) [page 128].3. You delete the Oracle database instance [page 129].

6.8.2.1 Deleting an SAP Instance

You use this procedure if you want to delete a single SAP instance or all instances of an SAP system.

Note

Make sure that you delete the instances in the following order:

1. Dialog instance if there are any2. Central instance3. Central services instance if there is one

Procedure

1. Stop the SAP instance that you want to delete as follows:a) Log on as user <sapsid>adm.b) Execute this command:

stopsap r3 <InstanceName>

2. Stop the sapstart service with the following command:

03/28/2008 PUBLIC 127/140


sapcontrol -nr <InstanceNumber> -prot NI_HTTP -function StopService

3. Stop the saposcol process with the following command:saposcol -k

4. Remove the instance profiles as follows:rm /usr/sap/<SAPSID>/SYS/profile/<SAPSID>_<InstanceName>_<host_name>

rm /usr/sap/<SAPSID>/SYS/profile/START_<InstanceName>_<host_name>

Example

For example, enter the following commands:rm /usr/sap/C11/SYS/profile/START_D00_h0001

rm /usr/sap/C11/SYS/profile/C11_D00_h0001

5. Log on as user root and delete the local instance directory:rm -rf /usr/sap/<SAPSID>/<InstanceName>

6. Change to the directory /usr/sap. Edit the file sapservices and delete the line that refers tothe instance to be deleted.

6.8.2.2 Deleting Installation Files, Directories, and Users ona Host

After you have deleted all SAP instances on a host, you still have to delete the remaining installationfiles, directories, and users on this particular host. You have to repeat this procedure for any hostwhere you previously deleted an SAP instance.

Caution

Only delete files or directories that are used by other SAP instances by means of NFS mounts if youare deleting the entire SAP system (on all hosts).

PrerequisitesYou must have deleted your SAP instance(s) as described in Deleting an SAP Instance [page 127].

Procedure

1. If the following directories are mounted with NFS, unmount them:/<sapmnt>/<SAPSID>/exe

/<sapmnt>/<SAPSID>/global

/<sapmnt>/<SAPSID>/profile

2. To delete directories, execute the following commands:rm -rf /usr/sap/<SAPSID>

rm -rf /<sapmnt>/<SAPSID>

128/140 PUBLIC 03/28/2008


3. Delete the local user <sapsid>adm, its home directory, and all subdirectories of the home directory.

Caution

Do not delete user <sapsid>adm if this is a Network Information System (NIS) user and you donot want to delete the SAP system on all hosts.

Recommendation

To delete users, use the administration tools of your operating system if possible.

a) Delete user <sapsid>adm as described in your operating system documentation.b) If the home directory of the user was not deleted automatically in the previous step, execute

the following command to delete the directory:rm -rf <sapsid_adm_home>

Example

rm -rf /home/c11adm

4. Delete the user <sapsid>adm from the groups sapsys, oper, and dba, if this was not doneautomatically in the previous step. If one of these groups is now empty, delete the complete groupas described in your operating system documentation.

5. Check whether you need to delete entries from the file /etc/services:a) Search for entries starting with sap

b) Check whether these entries are still required by other instances with the same or a different<SAPSID> on any server.

c) If not, start by generating a backup copy of the services file by entering the following command:cp /etc/services /etc/services.sap

d) Delete superfluous entries from /etc/services.If you use NIS for the services file, see your operating system documentation for moreinformation on how to delete entries from network-wide service entries.

6. If there are no other SAP instances running on this host, delete the following files if they exist:

n /etc/sapconf

n /usr/sap/trans/.sapconf

7. If there are no other SAP instances running on this host, delete the file /usr/sap/sapservices.8. If there are no other SAP systems running network-wide, delete the directory /usr/sap/trans

with all its subdirectories.Otherwise, adapt the SAP system configuration description.

6.8.2.3 Deleting an Oracle Database Instance

This section describes how to delete an Oracle database that you have installed.

03/28/2008 PUBLIC 129/140


Caution

If you have multiple components installed in one database (MCOD), delete the database only ifyou also want to delete all components. Otherwise, delete components selectively. For moreinformation, see SAP Note 399910.

Prerequisites

n Before deleting the database, stop all SAP instances belonging to this database or to this Javadatabase schema.

n We recommend that you delete the SAP instances before deleting the database instance.

Procedure

1. Log on as user ora<dbsid>.2. Start sqlplus and shutdown the database. Enter:

sqlplus /nolog

SQLPLUS> connect / as sysdba

SQLPLUS> shutdown immediate

SQLPLUS> exit

3. Kill the orasrv process if it is running:ps -ef | grep orasrv (note the process ID <PID>)kill —9 <PID>

4. Stop the listener process:lsnrctl stop

5. Use the uninstall functionality of the Oracle Universal Installer (OUI):a) Start the OUI with the user ora<dbsid> by entering one of the following:


./runInstaller


./runInstaller

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

b) Choose Installed Products or Deinstall Products.c) Select the database schema you want to uninstall: <DBSID>_102_64.d) Mark the Oracle 10G database within the selected product.e) Choose Remove.f) Confirm your selection with Yes.g) Choose EXIT.

6. Log on as user root.7. Delete user ora<dbsid> along with its home directory and all subdirectories of this directory:

a) Delete UNIX user ora<dbsid> using the steps appropriate for your operating system.

130/140 PUBLIC 03/28/2008



b) If the home directory of the user was not deleted automatically in the previous step, deletethis directory:rm -rf <sapsid_adm_home>

Example

For example, enter:rm -rf /home/orac11

8. Delete user ora<dbsid> from group dba, if this was not done automatically in the previous step.If the group dba is now empty, delete the complete group using the steps appropriate for youroperating system.

9. Remove the directory /oracle/<DBSID> and subdirectoriesrm -rf /oracle/<DBSID>

10. If there are no other database instances with the same Oracle release installed on this host, removethe staging area directory, using the following command:rm -rf /oracle/stage/102_64

11. If there are no other Oracle instances on this host, remove the Oracle client software directorywith one of the following commands:rm -rf /oracle/client/102_64

03/28/2008 PUBLIC 131/140

Typographic Conventions

Example Description

< > Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your <User Name>”.

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

Example Textual cross-references to an internet address, for example, http://www.sap.com

/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 03/28/2008

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

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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks orregistered trademarks of IBM Corporation.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 2006-12-31 (V5.1beta [= 6.0 for E3]) and XSLT processor SAXON 6.5.2 fromMichael Kay (http://saxon.sf.net/), XSLT version 1.

03/28/2008 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 03/28/2008

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

03/28/2008 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 03/28/2008


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

03/28/2008 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 03/28/2008

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

sap erp 6.0 sr3 abap

Documents