7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 1/142
Installation GuideSAP ERP 6.0 - EHP4 Ready SR1 ABAP on Solaris: OracleBased on SAP NetWeaver 7.0 including Enhancement Package 1
Target Audience■
System administrators■ Technology consultants
PUBLICDocument version: 1.1 – 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 2/142
About this Installation Guide
SAP System Installation
SAP system installations should only beperformed by SAP Technical Consultantscertified for your operating system, yourdatabase, and the SAP system that you areinstalling
SAP Installation Tool
You must only use the SAP installation toolsaccording to the instructions and for the purposesdescribed in the SAP installation document.Improper use of the SAP installation tools candamage files and systems already installed.
Downward Compatibility of Databases
For downward-compatible releases of DB/OSplatforms for SAP products, SAP plans toregularly release the newest database (DB) andoperating-system (OS) versions of SAP products.These releases are downward-compatible withearlier SAP system releases.Note that for already shipped SAP components,we only support the installation for databaseversions proposed by the installation tool.
Therefore, you must install an SAP componentor perform a system copy using a downward-compatible database. That is, you either install thecomponent with the old proposed databaseversion or you upgrade the old database versionto the downward-compatible new version.
2 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 3/142
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document.You can find the latest version at the following location:http://service.sap.com/erp-inst .
The following table provides an overview of the most important document changes.
Version Date Description
1.10 2009-05-25 Updated Version1.0 2009-05-04 Initial Version
2009-05-25 PUBLIC 3 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 4/142
Table of Contents
Chapter 1 Introduction ...........................................................................................................71.1 New Features .............................................................................................................81.2 SAP Notes for the Installation ..................................................................................10
Chapter 2 Planning ...................................................................................................................13
2.1 Planning Checklist ....................................................................................................132.2 Installation Options Covered by this Guide ...........................................................132.2.1 Central System ..........................................................................................................132.2.2 Distributed System ....................................................................................................142.2.3 High-Availability System ..........................................................................................152.2.4 Dialog Instance ..........................................................................................................162.3 Hardware and Software Requirements ...................................................................192.3.1 Running the Prerequisite Checker in Standalone Mode (Optional) .................... 202.3.2 Requirements for a Central System ........................................................................212.3.3 Requirements for a Distributed or a High Availability System .............................242.3.3.1 Requirements for a Central Services Instance ........................................................252.3.3.2 Requirements for the Central Instance ..................................................................272.3.3.3 Requirements for the Database Instance ................................................................292.3.4 Requirements for a Dialog Instance ........................................................................322.4 SAP System Transport Host .....................................................................................342.5 Planning User and Access Management .................................................................352.6 Basic SAP System Parameters ...................................................................................36
2.7 High Availability: Planning the Switchover Cluster ..............................................43
Chapter 3 Preparation ..............................................................................................................473.1 Preparation Checklist ...............................................................................................473.2 Creating Operating System Users and Groups .......................................................473.3 Setting Up File Systems and Raw Devices ...............................................................493.3.1 SAP Directories ..........................................................................................................503.3.2 Oracle Directories .....................................................................................................533.3.3 Setting Up File Systems for a High-Availability System .........................................55
4 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 5/142
3.3.4 Configuring Network File System for a High-Availability System .......................573.4 Using Virtual Host Names ........................................................................................593.5 Performing Switchover Preparations for High Availability ...................................60
3.6 Exporting and Mounting the Global Transport Directory ..... ..... ..... ..... ..... ..... ..... 603.7 Installing the Front-End Software ...........................................................................613.8 Generating the SAP Solution Manager Key ............................................................613.9 Installing the Java Runtime Environment .............................................................623.10 Preparing the Installation DVDs ..............................................................................62
Chapter 4 Installation ..............................................................................................................674.1 Installation Checklist ................................................................................................674.2 Exporting and Mounting Global Directories: Distributed and High-Availability
Systems ......................................................................................................................724.3 Performing a High-Availability Installation ............................................................734.4 Running SAPinst .......................................................................................................734.5 SAPinst Installation Options ....................................................................................794.6 Oracle Database Software Installation .....................................................................824.6.1 Updating SAP-Specific Files in the Oracle Staging Area ........................................824.6.2 Running the Oracle Universal Installer ..................................................................834.6.3 Installing the Current Patch Set ..............................................................................85
4.6.4 Installing Required Interim Patches ........................................................................85
Chapter 5 Post-Installation .....................................................................................................875.1 Post-Installation Checklist .......................................................................................875.2 Logging On to the Application Server ....................................................................875.3 Configuring User Management ...............................................................................885.4 Ensuring User Security .............................................................................................895.5 Installing the SAP License .........................................................................................915.6 High Availability: Setting Up Licenses .....................................................................915.7 Applying the Latest Kernel and Support Package Stacks ...... .. ... .. .. .. ... .. .. .. ... .. .. .. ...925.8 Configuring Remote Connection to SAP Support ................................................925.9 Installing the SAP Online Documentation .............................................................935.10 Performing Initial ABAP Configuration .................................................................935.11 Performing Oracle-Specific Post-Installation Steps ................................................975.12 Configuring the Connection to a Central System Landscape Directory ....... .. .. .. 985.13 Implementing ERP ABAP Add-On Components ..................................................995.14 Performing the Client Copy ....................................................................................99
5.15 Performing a Full Installation Backup ....................................................................99
2009-05-25 PUBLIC 5 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 6/142
5.16 Accessing Configuration Documentation in SAP Solution Manager ..... .. ... .. .. ... .101
Chapter 6 Additional Information ........................................................................................103
6.1 Installation of Multiple Components in One Database .........................................1036.2 Integration of LDAP Directory Services ..................................................................1056.3 Setting up Swap Space for Solaris ............................................................................1096.4 Creating Solaris Groups and Users ..........................................................................1096.5 Setting up File Systems and Raw Devices for Solaris .............................................1116.6 Dialog Instance Installation for an Upgraded System only: Updating
Profiles ........................................................................................................................1126.7 Mounting a CD / DVD for Solaris ...........................................................................1136.8 Exporting and Mounting Directories via NFS for Solaris ......................................1146.9 Additional Information About SAPinst ..................................................................1156.9.1 Using SAPinst GUI ....................................................................................................1156.9.2 Interrupted Installation with SAPinst .....................................................................1166.9.3 Performing a Remote Installation with SAPinst ....................................................1186.9.4 Starting SAPinst GUI Separately ..............................................................................1196.9.5 Entries in the Services File Created by SAPinst .......................................................1216.10 Starting and Stopping SAP System Instances .........................................................1226.10.1 Starting and Stopping SAP System Instances Using the SAP Management
Console ......................................................................................................................1226.10.2 Starting and Stopping SAP System Instances Using Scripts ..................................1266.11 Creating a User for LDAP Directory Access ............................................................1286.12 Heterogeneous SAP System Installation .................................................................1296.13 Troubleshooting .......................................................................................................1296.13.1 Troubleshooting with SAPinst ................................................................................1296.14 Deleting an SAP System ...........................................................................................1306.15 Deleting the Oracle Database Software ...................................................................131
Chapter A Appendix ..................................................................................................................133A.1 Online Information from SAP .................................................................................133
6 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 7/142
1 Introduction
This document explains how to install SAP ERP 6.0 – EHP4 Ready SR1 (EHP4 SR1 for SAP ERP 6.0)ABAP. You perform the installation using SAPinst.SAP ERP 6.0 – EHP4 Ready SR1 is based on the technology of SAP NetWeaver 7.0 including enhancementpackage 1. For more information about the technology provided by SAP ERP and SAP NetWeaver, seehttp://service.sap.com/erp and http://sdn.sap.com/irj/sdn/netweaver .Make sure you read the corresponding Master Guidesbefore you start with this installation guide.The Master Guides are available as follows:
http://service.sap.com/erp-inst SAP E RP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 4 for SAP ERP 6.0
CAUTION
SeeSAP Note 998833for up-to-date information about release restrictions for EHP4 SR1 for SAPERP 6.0.
You can install SAP ERP 6.0 - EHP4 Ready SR1 with the following software units:■ SAP ERP Central Component (ECC)
NOTE
SAP ERP Central Component (ECC) is not installed with the Java Add-In.
NOTE
You also install SAP NetWeaver Application Server ABAP (AS ABAP) with SAP ERP CentralComponent.
For more information about the usage types of SAP NetWeaver and their interdependencies, see the
document Master Guide – SAP NetWeaver 7.0 at http://service.sap.com/instguidesNW70 . Forrestrictions, seeSAP N ote 1164532.
Constraints
You need to consider the following constraints before you start your installation:■ Your operating system platform must be 64-bit .
NOTE
The only instance, you can still install on 32-bit is the dialog instance.■ The database must beOracle 10.2.0.2 or higher.
You need to consider the following constraints after the installation:
1 Introduction
2009-05-25 PUBLIC 7 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 8/142
■ The installation of SAP ERP 6.0 - EHP4 Ready SR1ABAPsystem based on SAP NetWeaver 7.0including enhancement package 1 contains only the basic EHP4 for SAP ERP 6.0 technical usage“ABAP Technology for ERP EHP4”. To complete the installation process you have to install
additional EHP4 for SAP ERP 6.0 functionality in your SAP ERP 6.0 - EHP4 Ready SR1ABAPsystem.You must use the Solution Manager Maintenance Optimizer to identify and download thecorresponding software components and the SAP enhancement package Installer to deploy thedownloaded software components in your system.For more information about the Solution Manager Maintenance Optimizer, see:http://
service.sap.com/solman-mopz .For more information about the SAP enhancement package Installer, see the documentInstallationGuide - SAP Enhancement Package Installation - Using SAP Enhancement Package Installer (SAPehpi)at:
http://service.sap.com /erp-instSAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 4 for SAP ERP 6.0 Enhancement Package Installation on Existing SAP Systems
Naming Conventions
■ SAP systemrefers to EHP4 SR1 for SAP ERP 6.0 .■ ABAP systemrefers to EHP4 SR1 for SAP ERP 6.0 ABAP .
Profiling for H igh Availability
Only valid for: HA (UNIX) |
The profile bars with the wordingOnly valid for: HA (UNIX)– for example, as in this section – refer tocontent that is only valid if you are installing a high-availability (HA) system on UNIX.End of: HA (UNIX) |
1.1 New Features
The following tables provide an overview of the new features related to the installation of this release:
C AUTION
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 enhancement package 4 for SAP ERP 6.0, SAPinst has the following newfeatures:
■ You no longer have to install a Java Runtime Environment (JRE) to start theSAPinst GUI.However, you still have to install a JRE to perform the installation with SAPinst
(seeInstalling the Java Runtime Environment (JRE)[page62]).
1 Introduction
1.1 New Features
8 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 9/142
Area Description■ If you want to terminate SAPinst from the SAPinst GUI menu, you now have to
choose SAPinst Cancel. If you choose File Exit , you only terminate theSAPinst GUI (seeUsing SAPinst GUI [page115]).
■ You can directly access installation log files from the SAPinst GUI menu bychoosing SAPinst Log Browser (seeUsing SAPinst GUI [page115]).
64-bit support only forall instances exceptdialog instances
As of SAP ERP 6.0 SR3, you must install an SAP ERP system only on 64-bit operatingsystems.For the dialog instance, you can still use a 32-bit operating system. Therefore, youonly see the folderSoftware Life-Cycle Optionson the Welcomescreen when you start theinstallation from a 32-bit installation master DVD.You might need to install dialog instances on 32-bit operating systems if you want touse 32-bit SAP NetWeaver components, such as Adobe document services. However,first check whether such 32-bit components can run on 64-bit operating systems. If so, we recommend running these 32-bit components on a 64-bit operating system.
No new dual stack(ABAP+Java) systemsfor SAP enhancementpackage 4 for SAP ERP6.0
As of SAP enhancement package 4 for SAP ERP 6.0, you can no longer install SAP ERPdual stack (ABAP+Java) systems. If you want to use both SAP ERP ABAP and JavaComponents in your system landscape, you have to proceed as follows:1. Install a separate SAP ERP ABAP system.2. Install a separate SAP ERP Java system.3. Configure the connection of the SAP ERP Java system to the SAP ERP ABAP back-
end systemInstallation option JavaAdd-In for ABAP disabled
As of SAP enhancement package 4 for SAP ERP 6.0, the installation option Java Add-In for ABAP is disabled. That is, you can no longer install the Java Add-In to an existingABAP system.
Maintenance Optimizer All downloadable software components, released after April 2, 2007, are availableexclusively through the Maintenance Optimizer in SAP Solution Manager. Thiscomprises:
■ Support Package Stacks, Support Packages, and patches for Java instances, exceptfor kernel patches
■ Legal changes■ SAP applications and versions that are:
● Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and allapplications based on this software, including SAP Business Suite 7
● Optional for all SAP applicationsFor more information, seehttp://service.sap.com/solman-mopz .
Operating Systems and Platforms
Area Description
Support of OperatingSystems and Platforms
■ For supported operating system and database releases, see theProduct AvailabilityMatrix at http://service.sap.com/pam .
■ For forums, blogs, content, and community related to all of the supporteddatabases and operating systems, see theDatabase and Operating Systemsarea athttp://sdn.sap.com/irj/sdn/dbos .
Oracle Database
New functions forOracle Database
■ For a complete list of new Oracle features, see further documentation fromOracle, which you can find at:
1 Introduction
1.1 New Features
2009-05-25 PUBLIC 9 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 10/142
http://www.oracle.com/technology/products/database/oracle10g■ For a complete list of new features for SAP on Oracle, seehttp://sdn.sap.com/
irj/sdn/ora .
1.2 SAP Notes for the Installation
You must read the following SAP Notesbefore you start the installation. These SAP Notes containthe most recent inf ormation on the installation, as well as corrections to the installationdocumentation.Make sure that you have the up-to-date version of each SAP Note, which you can find athttp://
service.sap .com /notes .
SAP Notes for the Installation
SAP Note Number Title Description
998833 Release Restrictions SAP ERP 6.0 -Enhancement Packages
At the time of the release of EHP4 for SAP ERP 6.0,limitations affect the productive usage of certainfunctions. This note provides customerinformation on these restrictions.
1165067 Release Info SAP EnhancementPackage 4 for SAP ERP 6.0
SAP Enhancement Package 4 for SAP ERP 6.0release information.
1164532 Release Restrictions for SAPNetWeaver 7.0 EHP1
Customer information on restrictions in theproduction use of certain functions.
1300536 Inst. NetWeaver 7.0 EHP1 SR1 /
Business Suite 7 SR1- UNIX
UNIX-specific information about the SAP system
and corrections to this documentation.
NOTE
This note also contains UNIX-specificinformation referring to EHP4 SR1 for SAPERP 6.0.
1300538 Inst. NetWeaver 7.0 EHP1 SR1 / Business Suite 7 SR1 - UNIX/ Oracle
Oracle-specific information about the SAP systeminstallation and corrections to thisdocumentation.
NOTE
This note also contains Oracle-specificinformation referring to EHP4 SR1 for SAPERP 6.0.
828268 Oracle 10g: New functions Information about new Oracle features releasedfor the SAP system.
98252 Installing two Oracle databases ona host
This SAP Note is only required if you plan toinstall more than one Oracle database on the samehost.
855498 Installation Prerequisite Checker SAP Software on UNIX, Windows, and IBM i:Checking OS Dependencies
73606 Supported Languages and CodePages
Information on possible languages and languagecombinations in SAP systems
1 Introduction
1.2 SAP Notes for the Installation
10 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 11/142
SAP Note Number Title Description
1067221 Central Note for HeterogeneousInstallation
Heterogeneous ABAP system landscapes ondifferent operating systems have been released forsome time. Heterogeneous Java systemlandscapes on different operating systems havenow also been released. However, not everycombination of operating system and databasesystem is released. This SAP Note and its relatedSAP Notes describe the released operating systemand database combinations.
789220 Support Package level forNetWeaver Installations/ Upgrades
Information about the ABAP Support Packagelevels and kernel patch levels contained in thecurrent SAP NetWeaver release.
774615 Support Package levels of ERP/ ECC installations/upgrades
Information about the ABAP Support Packagelevels and kernel patch levels contained in thecurrent SAP ERP release.
1258912 PLM Core 7.00 Release Notes andInformation
Information and references to other notes aboutinstalling PLM Core 7.00 and importing PLM Core7.00 Support Packages.
1 Introduction
1.2 SAP Notes for the Installation
2009-05-25 PUBLIC 11 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 12/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 13/142
2 Planning
2.1 Planning Checklist
You have to complete the following planning activities, which are described in more detail in the linkedsections:1. You plan your SAP system landscape according to theMaster Guide.
In addition, we recommend that you read the Technical Infrastructure Guide – SAP NetWeaver 7.0 , whichis available at: http://service.sap.com/ins ta llnw70 Planning .
2. Youidentify the required installation option for your system[page13].3. Youcheck the hardware and software requirements[page 19].4. Youdecide on the transport host to use[page34].5. You plan user and access management [page35].6. Youidentify basic SAP system parameters[page36].7. Only valid for: HA (UNIX) |
You plan the switchover cluster [page43] for a high-availability (HA) system.End of: HA (UNIX) |
8. You can continue with Preparation[page47].The following planning activity isoptional :
■ Installation of Multiple Components in One Database (MCOD)[page103]
2.2 Installation Options Covered by this Guide
This section shows the installation options covered by this installation guide. You have to decide whatexactly you want to install because the steps you have to performvary according to the installationoption you choose.
■
Central system[page13]■ Distributed system[page14]■ Only valid for: HA (UNIX) |
High-availability system[page15]End of: HA (UNIX) |
■ You can install one or more dialog instances[page16] to an existing central, distributed, or high-availability system.
2.2.1 Central System
You can install a central system on a single host.
2 Planning
2.1 Planning Checklist
2009-05-25 PUBLIC 13 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 14/142
In a central system, all main instances run on a single host:■ Database instance (DB)■ Central instance
Figure 1: Central ABAP System
Optionally you can install one or more dialog instances. For more information, seeDialog Instance[page16].
2.2.2 Distributed System
In a distributed system, every instance can run on a separate host:■ Database instance (DB)■ Central instance
NOTE
You can also use the SAP transport host or the SAP global host as your central instance host.
Optionally you can install one or more dialog instances. For more information, seeInstallation of a DialogInstance[page16].
2 Planning
2.2 Installation Options Covered by this Guide
14 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 15/142
Figure 2: Distributed ABAP System
Only valid for: HA (UNIX) |
2.2.3 High-Availability System
In a high-availability system, every instance can run on a separate host:■ ABAP Central Services Instance (ASCS)■ Database instance■ Central instance
We recommend that you run both the ASCS and the SCS in a switchover cluster infrastructure.Optionally you can install one to <n> dialog instances. For more information, seeInstallation of a DialogInstance[page16].The following figures show examples for the distribution of the SAP instances in a high-availability
system.
2 Planning
2.2 Installation Options Covered by this Guide
2009-05-25 PUBLIC 15 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 16/142
Figure 3: High-Availability System
End of: HA (UNIX) |
2.2.4 Dialog InstanceYou can install one or more dialog instances for an existing SAP system.A dialog instance can run on:
■ The host of any instance of the existing SAP system (exceptions see below)■ On a dedicated host
NOTE
If you want to install dialog instances running on an operating system other than the centralinstance, seeHeterogeneous SAP System Installation[page129]. For example, you need to do this if your
central instance runs on Solaris but the dialog instance is to run on Windows.
Dialog Instance for a Central System
For example, the following figure shows each of the three dialog instances that are running:■ On the main host of the SAP system, that is on the host on which the central instance and the
database instance run■ On dedicated hosts
2 Planning
2.2 Installation Options Covered by this Guide
16 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 17/142
Figure 4: Dialog Instance for a Central System
For more information, seeCentral System[page13].
Dialog Instance for a Distributed System
For example, the following figure shows each of the three dialog instances that are running:■ On the main host of the SAP system, that is on the host on which the central instance and the
database instance run■ On dedicated hosts
We do not recommend you to install dialog instances on the SAP global host.
2 Planning
2.2 Installation Options Covered by this Guide
2009-05-25 PUBLIC 17 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 18/142
Figure 5: Dialog Instance for a Distributed System
For more information, seeDistributed System[page14].Only valid for: HA (UNIX) |
Dialog Instance for a High-Availability System
For example, the following figure shows each of the three dialog instances that are running on:■ The host of the central instance■ Dedicated hosts
We do not recommend you to install dialog instances on the switchover cluster infrastructure.
2 Planning
2.2 Installation Options Covered by this Guide
18 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 19/142
Figure 6: Dialog Instance for a High-Availability System
For more information, seeHigh-Availability System[page15].End of: HA (UNIX) |
2.3 Hardwa re 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
■ Contact your OS vendor for the latest OS patches.■ Make sure that the host name meets the requirements listed in SAP Note 611361.■ Check your keyboard definitions.■ 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 Planning
2.3 Hardware and Software Requirements
2009-05-25 PUBLIC 19 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 20/142
2. Check the hardware and software requirements using:■ The Prerequisite Checker in one of two modes:
● Standalone mode (optional) before the installation process
For more information, seeRunning the Prerequisite Checker Standalone[page20].● Integrated in SAPinst (mandatory)during the installation process
For more information, seeRunning SAPinst [page73].NOTE
For the most recent updates to the Prerequisite Checker , always checkSAP Note 855498.■ The hardware and software requirements checklists for:
● Central system[page21]● Distributed or high availability system[page24]●
If you want to install one or more dialog instances, check the requirements for adialoginstance[page32].
3. If you are installing aproduction system, the values provided by the Prerequisite Checker andthe hardware and software requirements checklists are not sufficient. In addition, do the following:
■ You use the Quick Sizer tool available athttp://service.sap.com/sizing .For more information about t he Quick Sizer and available sizing guides, see theMaster Guide– SAP NetWeaver 7.0 at http://service.sap.com/installnw70 Planning .
■ You contact your hardware vendor, who can analyze the load and calculate suitable hardwaresizing depending on:
● The set of applications to be deployed● How intensively the applications are to be used● The number of users
2.3.1 Running the Prerequisite Checker in Standalone Mode(Optional)
Before installing your SAP system, you can run thePrerequisite Checker in standalone mode to check the
hardware and software requirements for your operating system (OS) and the SAP instances.
RECOMMENDATION
We recommend that you use both the Prerequisite Checker and the requirements tables for reference.
NOTE
When installing your SAP system, SAPinst automatically starts thePrerequisite Checker and checksthe hardware and software requirements in the background.
Prerequisites■ You have prepared the installation master DVD on the required installation host [page 62].
2 Planning
2.3 Hardware and Software Requirements
20 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 21/142
■ You make sure that the required prerequisites are met before starting SAPinst [page73].
Procedure
1. Youstart SAPinst [page73].2. On theWelcomescreen, choose <Your SAP product> Software Life-Cycle Options Additional Preparations
Prerequisites Check.3. Follow the instructions in the SAPinst dialogs and enter the required parameters.
NOTE
For more information about each parameter, position the cursor on the parameter field andchoose F1 in SAPinst.
When you have finished, theParameter Summaryscreen appears summarizing all parameters you have
entered and want to have checked. If you want to make a change, select the relevant parametersand choose Revise.4. To start the prerequisites check, chooseNext .
Result
The Prerequisite Checker Resultsscreen displays the results found. If required, you can also check the resultsin fileprerequisite _checker_results.html , which you can find in the installation directory.
RECOMMENDATION
We recommend making sure that your system meets all checked prerequisites before starting theinstallation. However, you can still start the installation even if your system does not meet allprerequisites. In this case, make sure that you know what you are doing.
2.3.2 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 obtain the full list of hardware and software requirements from the relevant Oracle databaseinstallation guide for your operating system, which you can find at:http://www.oracle.com/
technology/documentation .
NOTE
The information here is not intended to replace the documentation of the Solaris operatingsystem.
■ Solaris 9: For more information, see the Solaris 9 <Release> System Administrator Collection
at:http://docs.sun.com/app/docs/prod/solaris.9
2 Planning
2.3 Hardware and Software Requirements
2009-05-25 PUBLIC 21 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 22/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 23/142
Requirement Values and Activities
For more information about specifying device names and about displaying andchanging the partitioning, see the Solaris 10 <Release> System Administrator Collectionat the following:http://docs.sun.com/app/docs/prod/solaris.10
RAM 5 GBTo display the available working memory, enter the following command:/usr/sbin/prtconf |grep Memory
Swap Space You need hard disk drives with sufficient space for swap. You can calculate therequired swap space as follows:At least 20 GB are required.For more information, seeSAP Note 570375.You can display and – if required – modify the existing swap space.For more information, seeSetting up Swap Space for Solaris[page109]
Software Requirements
Requirement Values and Activities
Operating SystemVersion
To check the operating system version, use the following command:/bin/uname -r
Solaris Kernel Parameters To run an SAP system, you must check and, if necessary, modify the Solaris kernelparameters or resource controls.For more information about current Solaris kernel parameters and about how tomodify them, see the following:
■ Solaris 9: SAP Note 395438■ Solaris 10: SAP Note 724713
Solaris Patches To check the installed patches, enter the following command:/bin/showrev -p
NOTE
For more information about relevant patches, see the following SAP Notes:■ Sun Solaris 9:SAP Note 550585■ Sun Solaris 10:SAP Note 832871■ Solaris 10 on x64:SAP Note 908334
Lightweight DirectoryAccess Protocol (LDAP)
If you want to use LDAP, you require the following LDAP library:libldap.so
C++ RuntimeEnvironment
The Shared Library Patch for C++ must be installed.
Networking If application servers are installed decentralized, Network File System (NFS) must beinstalled.
■ Solaris 9For more information about how to set up and administer Network File System(NFS), see theSolaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about how to set up and administer Network File System(NFS), see theSolaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
Fonts and Code Pages Make sure that the required fonts and code pages are installed.
2 Planning
2.3 Hardware and Software Requirements
2009-05-25 PUBLIC 23 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 24/142
Requirement Values and Activities■ Solaris 9
For more information, see the Solaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information, see the Solaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
National LanguageSupport (NLS)
Make sure that National Language Support (NLS) and correspondingsaplocales areinstalled.To display which locales are available, enter the following command:locale -a
The following files must be available:iso_8859_1, en_US.
GUI for Oracle DatabaseInstallation
On the database host, a graphical user interface (GUI), for exampleX11 , is requiredfor the Oracle database software installation withrunInstaller . For moreinformation, see the documentation of your operating system.
Oracle Interim Patches Check SAP Note 839182to find whether you require an interim patch for the Oracledatabase installation. If so, make sure you have the correspondingPerl version asstated 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 onlyrecommendations 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 obtain the recommended shell limits and kernel parameters from therelevant Oracle databaseinstallation guide for your operating system at:http://www.oracle.com/technology/documentation
Printer ■ Solaris 9For more information about how to set up a printer, see the Solaris 9 <Release>System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about how to set up a printer, see theSolaris 10 <Release>System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
2.3.3 Requirements for a Distributed or a High Availability System
The following sections provide information about the hardware and software requirements in adistributed system, where the following SAP instances can reside on different hosts:
NOTE
The information here is not intended to replace the documentation of the Solaris operatingsystem.
■ Solaris 9: For more information, see the Solaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
2 Planning
2.3 Hardware and Software Requirements
24 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 25/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 26/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 27/142
Requirement Values and Activities■ Solaris 10: For more information about how to set up and administer Network
File System (NFS), see theSolaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
Fonts and Code Pages Make sure that the required fonts and code pages are installed.■ Solaris 9: For more information, see the Solaris 9 <Release> System Administrator
Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10: For more information, see the Solaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
Printer ■ Solaris 9: For more information about how to set up a printer, see the Solaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10: For more information about how to set up a printer, see the Solaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
2.3.3.2 Requirements for the Central Instance
The central instance host must meet the following requirements:
Hardware Requirements
Requirement Values and Activities
DVD Drive ISO 9660 compatibleCPU The recommended minimum hardware is at least one dual core CPU or two
single core CPUs.To display the status and number of existing CPUs, enter the followingcommand:/usr/sbin/psrinfo -vp
Hard Disk Space ■ Hard disk drives with sufficient space for the central instance:7 GBFor more information about space requirements for the separate filesystems and directories, seeSetting Up File Systems[page50] SAP Directories.
■ 4.3 GB of temporary disk space for every required installation DVD thatyou have to copy to a local hard diskFor more information, seePreparing the Installation DVDs[page62].
■ 1.2 GB of temporary disk space for the installation.■ Solaris 9
For more information about specifying device names, about displaying andchanging the partitioning, see the Solaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about specifying device names and about displayingand changing the partitioning, see theSolaris 10 <Release> System Administrator Collectionat:
2 Planning
2.3 Hardware and Software Requirements
2009-05-25 PUBLIC 27 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 28/142
Requirement Values and Activitieshttp://docs.sun.com/app/docs/prod/solaris.10
RAM 3 GBTo display the available working memory, enter the following command:/usr/sbin/prtconf |grep Memory
Swap Space You need hard disk drives with sufficient space for swap. You can calculate therequired swap space as follows:At least 20 GB are required.For more information, seeSAP Note 570375.You can display and – if required – modify the existing swap space.For more information, seeSetting up Swap Space for Solaris[page109]
Software Requirements
Requirement Values and Activities
Operating System Version To check the operating system version, use the following command:/bin/uname -r
Solaris Kernel Parameters To run an SAP system, you must check and, if necessary, modify the Solaris kernelparameters or resource controls.For more information about current Solaris kernel parameters and about how tomodify them, see the following:
■ Solaris 9: SAP Note 395438■ Solaris 10: SAP Note 724713
Solaris Patches To check the installed patches, enter the following command:/bin/showrev -p
NOTE
For more information about relevant patches, see the following SAP Notes:■ Sun Solaris 9:SAP Note 550585■ Sun Solaris 10:SAP Note 832871■ Solaris 10 on x64:SAP Note 908334
Lightweight DirectoryAccess Protocol (LDAP)
If you want to use LDAP, you require the following LDAP library:libldap.so
C++ RuntimeEnvironment
The Shared Library Patch for C++ must be installed.
Networking If application servers are installed decentralized, Network File System (NFS) must
be installed.■ Solaris 9For more information about how to set up and administer Network FileSystem (NFS), see theSolaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about how to set up and administer Network FileSystem (NFS), see theSolaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
Fonts and Code Pages Make sure that the required fonts and code pages are installed.■ Solaris 9
For more information, see the Solaris 9 <Release> System Administrator Collectionat:
2 Planning
2.3 Hardware and Software Requirements
28 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 29/142
Requirement Values and Activitieshttp://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information, see the Solaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
National LanguageSupport (NLS)
Make sure that National Language Support (NLS) and correspondingsaplocales
are installed.To display which locales are available, enter the following command:locale -a
The following files must be available:iso_8859_1, en_US.
Printer ■ Solaris 9For more information about how to set up a printer, see the Solaris 9 <Release>System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about how to set up a printer, see theSolaris 10 <Release>System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
2.3.3.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 obtain the full list of hardware and softwarerequirements from the relevant Oracle databaseinstallation 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.This document provides information about all operating system prerequisites and is regularlyupdated.
CAUTION
If your database resides on Network Attached Storage (NAS), you need to review and implementthe Oracle NAS guidelines. You need to mount network file systems with specific mount options,which you can find in the Oracle installation guide.
CAUTION
The database must beOracle 10.2 or higher.
2 Planning
2.3 Hardware and Software Requirements
2009-05-25 PUBLIC 29 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 30/142
Hardware Requirements
Requirement Values and Activities
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 Configurationguide inSAP Database Guide: Oracle (BC-DB-ORA-DBA)inthe SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability
Application Platform by Key Capability Platform-Wide Services Database Support OracleSAP Database Guide: Oracle (BC-DB-ORA-DBA) Getting Started with Oracle and the SAP
SystemDVD Drive ISO 9660 compatibleCPU The recommended minimum hardware is at least one dual core CPU or two single
core CPUs.To display the status and number of existing CPUs, enter the following command:/usr/sbin/psrinfo -vp
Hard Disk Space ■ Hard disk drives with sufficient space for the database instance:50 GB (20 GB plus space for the SAP data file systems)For more information about space requirements for the separate file systemsand directories, seeSetting Up File Systems and Raw Devices – Oracle File Systems[page53].
■ 4.3 GB of temporary disk space for every required installation DVD you haveto copy to a local hard disk.
■ 1.2 GB of temporary disk space for the installation.■ Solaris 9
For more information about specifying device names, about displaying andchanging the partitioning, see the Solaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about specifying device names, about displaying andchanging the partitioning, see the Solaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
RAM 3 GBTo display the available working memory, enter the following command:/usr/sbin/prtconf |grep Memory
Swap Space You need hard disk drives with sufficient space for swap. The required swap spacecan be calculated as follows:At least 20 GB are required.For more information, seeSAP Note 570375.You can display and – if required – modify the existing swap space.For more information, seeSetting up Swap Space for Solaris[page109]
Software Requirements
Requirement Values and Activities
Operating System Version To check the operating system version, enter the following command:/bin/uname -r
2 Planning
2.3 Hardware and Software Requirements
30 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 31/142
Requirement Values and Activities
Solaris Kernel Parameters To run an SAP system, you must check and, if necessary, modify the Solaris kernelparameters or resource controls.For more information about current Solaris kernel parameters and about howto modify them, see the following:
■ Solaris 9: SAP Note 395438■ Solaris 10: SAP Note 724713
Solaris Patches To check the installed patches, enter the following command:/bin/showrev -p
NOTE
For more information about relevant patches, see the following SAP Notes:■ Sun Solaris 9:SAP Note 550585■ Sun Solaris 10:SAP Note 832871■ Solaris 10 on x64:SAP Note 908334
Lightweight Directory AccessProtocol (LDAP)
If you want to use LDAP, you require the following LDAP library:libldap.so
C++ Runtime Environment The Shared Library Patch for C++ must be installed.Networking If application servers are installed decentralized, Network File System (NFS) must
be installed.■ Solaris 9
For more information about how to set up and administer Network FileSystem (NFS), see theSolaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about how to set up and administer Network FileSystem (NFS), see theSolaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
Fonts and Code Pages Make sure that the required fonts and code pages are installed.■ Solaris 9
For more information, see the Solaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information, see the Solaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
National Language Support(NLS)
Make sure that National Language Support (NLS) and correspondingsaplocales are installed.To display which locales are available, enter the following command:locale -a
The following files must be available:iso_8859_1, en_US.
GUI for Oracle DatabaseInstallation
On the database host, a graphical user interface (GUI), for exampleX11 , is requiredfor the Oracle database software installation withrunInstaller . For moreinformation, see the documentation of your operating system.
Oracle Interim Patches Check SAP Note 839182to see whether you require an interim patch for theOracle database installation. If so, make sure you have the correspondingPerl
version as stated in that SAP Note.
2 Planning
2.3 Hardware and Software Requirements
2009-05-25 PUBLIC 31 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 32/142
Requirement Values and Activities
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 onlyrecommendations 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 obtain the recommended shell limits and kernel parameters from therelevant Oracle databaseinstallation guide for your operating system, whichyou can find at:http://www.oracle.com/technology/documentation
Printer ■ Solaris 9For more information about how to set up a printer, see the Solaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about how to set up a printer, see the Solaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
2.3.4 Requirements for a Dialog Instance
The dialog instance host must meet the following requirements:
NOTE
The information here is not intended to replace the documentation of the Solaris operatingsystem.
■ Solaris 9: For more information, see the Solaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10: For more information, see the Solaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
Hardware Requirements
Requirement Values and Activities
DVD Drive ISO 9660 compatibleCPU The recommended minimum hardware is at least one dual core CPU or two single
core CPUs.To display the status and number of existing CPUs, enter the following command:/usr/sbin/psrinfo -vp
Hard Disk Space ■ Hard disk drives with sufficient space for the dialog instance.4 GBFor more information about space requirements for the separate file systemsand directories, seeSetting Up File Systems[page50].
■ 4.3 GB of temporary disk space for every required installation DVD that youhave to copy to a local hard diskFor more information, seePreparing the Installation DVDs[page62].
■ 1.2 GB of temporary disk space for the installation.
2 Planning
2.3 Hardware and Software Requirements
32 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 33/142
Requirement Values and Activities■ Solaris 9
For more information about specifying device names, about displaying andchanging the partitioning, see the Solaris 9 <Release> System Administrator Collectionat the following:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about specifying device names and about displayingand changing the partitioning, see the Solaris 10 <Release> System Administrator Collectionat the following:http://docs.sun.com/app/docs/prod/solaris.10
RAM 3 GBTo display the available working memory, enter the following command:/usr/sbin/prtconf |grep Memory
Swap Space You need hard disk drives with sufficient space for swap. You can calculate therequired swap space as follows:At least 20 GB are required.For more information, seeSAP Note 570375.You can display and – if required – modify the existing swap space.For more information, seeSetting up Swap Space for Solaris[page109]
Software Requirements
Requirement Values and Activities
Operating SystemVersion
To check the operating system version, use the following command:/bin/uname -r
Solaris KernelParameters
To run an SAP system, you must check and, if necessary, modify the Solaris kernelparameters or resource controls.For more information about current Solaris kernel parameters and about how tomodify them, see the following:
■ Solaris 9: SAP Note 395438■ Solaris 10: SAP Note 724713
Solaris Patches To check the installed patches, enter the following command:/bin/showrev -p
NOTE
For more information about relevant patches, see the following SAP Notes:■ Sun Solaris 9:SAP Note 550585■ Sun Solaris 10:SAP Note 832871■ Solaris 10 on x64:SAP Note 908334
National LanguageSupport (NLS)
Make sure that National Language Support (NLS) and correspondingsaplocales areinstalled.To display which locales are available, enter the following command:locale -a
The following files must be available:iso_8859_1, en_US.
Lightweight DirectoryAccess Protocol (LDAP)
If you want to use LDAP, you require the following LDAP library:libldap.so
C++ runtimeenvironment
The Shared Library Patch for C++ must be installed.
2 Planning
2.3 Hardware and Software Requirements
2009-05-25 PUBLIC 33 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 34/142
Requirement Values and Activities
SAP kernel Make sure that the SAP kernel of the central instance has at least the patch level of the SAP kernel on the SAP Kernel DVD that is used for the installation of the dialoginstance.We recommend that you apply the most current SAP kernel from the SAP ServiceMarketplace at http://service.sap.com/swdc .
Networking If application servers are installed decentralized, Network File System (NFS) must beinstalled.
■ Solaris 9For more information about how to set up and administer Network File System(NFS), see theSolaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about how to set up and administer Network File System(NFS), see theSolaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
Fonts and Code Pages Make sure that the required fonts and code pages are installed.■ Solaris 9
For more information, see the Solaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information, see the Solaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
Printer ■ Solaris 9For more information about how to set up a printer, see the Solaris 9 <Release>System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.9
■ Solaris 10For more information about how to set up a printer, see the Solaris 10 <Release>System Administrator Collectionat:http://docs.sun.com/app/docs/prod/solaris.10
2.4 SAP System Transport Host
The transport host contains the transport d irectory used by the SAP transport system to store transport
data and change SAP system information, such as software programs, data dictionary data, orcustomization data. If you have several SAP systems, they are usually organized in transport domains.In most cases, all SAP systems in a transport domain have a common transport directory.When you install an SAP system, you have to decide which transport host and directory you want touse for your SAP system:
■ Use the transport directory that SAPinst creates during the installation of the SAP system by defaulton the global host:SAPinst by default creates the transport directory on the global host in/usr/sap/trans .
■ Use a transport directory located on a host other than the default host:● You can use an existing transport directory and host in your SAP system landscape.
2 Planning
2.4 SAP System Transport Host
34 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 35/142
● You can set up a new transport directory on a different host.In either case, you must prepare this host for use by the new SAP system. For more information,seeExporting and Mounting the Global Transport Directory[page60].
More Information■ Setting Up File Systems and Raw Devices[page49]■ See the SAP Library:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) EnglishSAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapSoftware Life Cycle Management Software Logistics Change and Transport System Change and Transp
– Overview (BC-CTS) Basics of the Change and Transport System Transport Management System – Con
2.5 Planning User and Access Management
You have to plan how you want to configure user and access management for your SAP system to beinstalled.Before you add a newly installed SAP system to your system landscape, you must decide which kindof user management you want to use:
■ Use Central User Administration (CUA).■ Use an LDAP directory as the data source for user data.
Procedure
Using Central User Management
1. You install your SAP system as described in this installation guide.2. Add the system to Central User Administration (CUA). For more information, seeConfiguring User
Management [page88].
Using an LDAP directory as the Data Source for User Data
1. You install your SAP system as described in this installation guide.2. Configure the user management of the newly installed SAP system to use and LDAP directory.
For more information, seeConfiguring User Management [page88].
More Information
For more information about configuring the user management of your SAP system to be installed, seethe SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SANetWeaver Library SAP NetWeaver by Key Capability Security Identity Management Identity Manageme
System Landscapes Integration of User Management in Your System Landscape
2 Planning
2.5 Planning User and Access Management
2009-05-25 PUBLIC 35 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 36/142
2.6 Basic SAP System Parameters
SAPinst prompts for input parameters during the Define Parametersphase of the installation.The tables below list the basic system parameters that you need to specify before installing your SAPsystem. For all other SAP system parameters, use theF1 help in the SAPinst screens.You can install your SAP system either inTypicalor Custommode:
■ TypicalIf you chooseTypical, the installation is performed with default settings. This means that you onlyhave to respond to a small selection of prompts including at least the following, which are describedin the corresponding tables below:
● SAP system ID and database ID● SAP system profile directory – only for systems with instances on separate hosts● Master password● SAP Solution Manager Key
If you want to change any of the default settings, you can do so on theParameter Summaryscreen.■ Custom
If you chooseCustom, you are prompted for all parameters. At the end, you can still change any of these parameters on the Parameter Summaryscreen.
NOTE
You cannot change from Customto Typicalmode or from Typicalto Custommode on the Parameter
Summaryscreen.
The tables below list the basic system parameters that you need to determine before installing yourSAP system. For all other SAP system parameters, use the F1 help in the SAPinst dialogs.
Java Runtime Environment
Parameters Description
Java Runtime Environment (JRE) A valid JRE is required for the installation with SAPinst. For moreinformation about JRE versions supported by SAP and about how toinstall them, seeInstalling the Java Runtime Environment [page62].
SAP System ID and Database ID
Parameters Description
SAP System ID<SAPSID> The SAP System ID<SAPSID> identifies the whole SAP system.
CAUTION
Choose your SAP system ID carefully. Youcannot change the SAP systemID after the installation.
Make sure that your SAP system ID:■ Is unique throughout your organization. Do not use an existing
<SAPSID> when installing a new SAP system.■ Consists of exactly three alphanumeric characters
2 Planning
2.6 Basic SAP System Parameters
36 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 37/142
Parameters Description■ Contains only uppercase letters■ Has a letter for the first character■ Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INTKEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG
SID SQL SYS TMP TOP UID USE USR VAR■ If you want to install a dialog instance, make sure that no gateway instance
with the same SAP system ID (SAPSID) exists in your SAP system landscape.Database ID<DBSID> The <DBSID> identifies the database instance. SAPinst prompts you for the
<DBSID> when you are installing the database instance.The <DBSID> can be the same as the<SAPSID> .
C AUTION
Choose your database ID carefully. Renaming is difficult and requires you
to reinstall the SAP system.
■ If you want to install a new database:Make sure that your database ID:
● Is unique throughout your organization● Consists of exactly three alphanumeric characters● Contains only uppercase letters● Has a letter for the first character● Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY 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 TOP UID USE USR VAR■ If you want to use an existing database system:
Enter exactly the database ID of the existing database to which you wantto add the system.
SAP System Profile Directory
Parameters Description
/<sapmnt>/<SAPSID>/profile or /
usr/sap/<SAPSID>/SYS/profileThe installation retrieves the parameters entered earlier from the SAPsystem profile directory.SAPinst prompts you to enter the location of the profile directorywhen the installation option that you execute is not the first one
belonging to your SAP system installation. See also the description of the parameters SAP System IDand Database ID./usr/sap/<SAPSID>/SYS/profile is the soft link referring to/<sapmnt>/
<SAPSID>/profile .
NOTE
If you install a dialog instance in an existing SAP system, SAPinstalso prompts you for the profile directory of the existing SAPsystem.
2 Planning
2.6 Basic SAP System Parameters
2009-05-25 PUBLIC 37 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 38/142
Unicode or Non-Unicode System
Parameters Description
Unicode System Everynew installation of an SAP system is Unicode.You can only deselect this option if you perform the system copy for a non-Unicode SAP system that has been upgraded to SAP NetWeaver 7.0 includingEnhancement Package 1.
SAP System Instances, Hosts, and Ports
Parameters Description
Instance Number of theSAP system
Technical identifier for internal processes. It consists of a two-digit number from 00to 98.The instance number must be unique on a host. That is, if more than one SAP instanceis running on the same host, these instances must be assigned 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 Instance Host Instance Host:Host name of the specific instance.To find out the host name, open a command prompt and enter hostname .The host name must not exceed 12 characters. For more information about theallowed host name length and characters, seeSAP Note 611361.
Virtual Host Name You can use one or more virtual TCP/IP host names for SAP servers within an SAPserver landscape to conceal their physical network identities from each other. Thismay be useful when moving SAP servers or complete server landscapes to other newhardware within a short time frame without having to carry out a reinstallation or
complicated reconfiguration. You need to specify the virtual host name before youstart SAPinst.For more information, seePrerequisitesin Running SAPinst [page73].You also need to specify the virtual host name before you start SAPinst if you wantto install ahigh-availability (HA) system . For more information, seePerforming aHigh-Availability Installation[page73].
■ For more information about the use of virtual TCP/IP host names, seeSAPNote 962955.
■ For more information about the allowed host name length and characters, seeSAP Note 611361.
Message Server Port C AUTION
The message server port number must be unique for the SAP system on allhosts. If there are several message port numbers on one host, all must be unique.
Port number of the SAP Message Server:If you do not specify a value, the default port number is used.ABAP Message Server PortThere is an external message server port and an internal message server port.The ABAP message server uses both the internal and the external message serverports. The default profile contains the configuration for both message server ports.The external message server port uses the parameterrdisp/msserv with defaultvalue 36<nn>, where <nn> is the instance number of the ABAP message serverinstance.
2 Planning
2.6 Basic SAP System Parameters
38 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 39/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 40/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 41/142
Solution Manager Key
Parameters Description
SAP Solution Manager key To install your SAP system, you need to generate an SAP Solution Manager key[page61], which the installation requires to continue. For more information, seeSAPNote 805390.
Parameters Relevant for the File System
Parameters Description
File system for the homedirectory user
/home/<username>
SAP system mount directory /<sapmnt> is the base directory for the SAP system.For /<sapmnt> you can use a directory of your choice.Do not add <SAPSID> as subdirectory because the system adds this directoryautomatically.
EXAM P LE
If you enter /<sapmnt> , the system creates the directory/<sapmnt>/
<SAPSID> .Oracle database file systems ■ Oracle home
■ sapdata home■ Client destination■ sapdata directory
Parameters Relevant for the Database
Parameters Description
Code page The code page that is used by your database (Unicode or Non-Unicode).
NOTE
You only need to enter this parameter if you perform a target systeminstallation as part of a system copy.
Database schema, Passwords The ABAP database schema is namedSAP<SCHEMA_ID>.Default name isSAPSR3.
RECOMMENDATION
Choose a <SCHEMAID>that is different from your <SAPSID> .It might cause problems when you copy a system where<SCHEMAID>is thesame as<SAPSID> , and the database-specific method used for the copy doesnot allow you to rename the database schemas. In certain situations, youmight create a system copy with a new<SAPSID> , but where the databaseschema has the old <SAPSID> . This is not a technical problem, but mightconfuse the system administrator.
Password of Userora<dbsid> User ora<dbsid> is the database administrator user.This user is only required on the host on which the database instance runs.
■ If you created userora<dbsid> manually before the installation, SAPinstprompts you for the existing password of this user.
2 Planning
2.6 Basic SAP System Parameters
2009-05-25 PUBLIC 41 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 42/142
Parameters DescriptionNOTE
If you chose parameter modeTypical, SAPinst only prompts you forthe existing password of this user if the password is not the same asthe Master Password.
■ If you did not create userora<dbsid> manually before the installation,SAPinst creates it automatically during the installation. SAPinst thenprompts you to enter and confirm a password for this user. In this case,SAPinst sets the Master Password by default. You can overwrite it.
NOTE
If you chose parameter modeTypical, SAPinst does not prompt youfor the existing password of this user but creates this user and assignsthe Master Password automatically.
Make sure that the user ID and group ID of this operating system user are uniqueand the same on each application instance host.For more information, seeCreating Operating System Users[page47].
User ID of Userora<dbsid> If you chose parameter modeTypicaland you did not create ora<dbsid> manuallybefore the installation, SAPinst automatically creates this user with theappropriate user ID. In this case, SAPinst does not prompt you for the user ID of ora<dbsid> .Make sure that the user ID of userora<dbsid> is unique and the same on eachapplication instance host.For more information, seeCreating Operating System Users[page47].
Group IDs of sys , dba , andoper
If you chose parameter modeTypicaland you did not create ora<dbsid> manuallybefore the installation, SAPinst automatically creates this user. SAPinst alsoassigns the user to groupssys ,dba , andoper . In this case, SAPinst does not promptyou for the user ID of ora<dbsid> .Make sure that the group IDs of dba and oper are unique and the same on eachapplication instance host.For more information, seeCreating Operating System Users[page47].
Database User Oracle UserSystem
Oracle Listener Name, OracleListener Port
■ If you install the database instance on a host where no other Oracle databaseis installed, you normally do not have to change the default values forListener Name and Listener Port.
■ If there is already an Oracle database installed on your installation host, youcan either use one listener for both databases or you have to specify an
unused Listener Name and an unused Listener Port for the new listener. Formore information if you use one listener for both databases, seeSAPNote 98252.
■ All dialog instances of an SAP system must use the same Listener Port thanthe database instance.
Tablespaces, Datafiles An Oracle database consists of one or more logical storage units calledtablespaces , which collectively store all of the database's data.Each tablespace in an Oracle database consists of one or more files calleddatafiles , which are physical structures that conform to the operating systemin which Oracle is running.MaxDatafileSize is the initial size of thetablespace datafile and its mapping tothe new tablespace layout while importing the external file DBSIZE.XML.SAPinst prompts you to enter MaxDatafileSize in MB:
2 Planning
2.6 Basic SAP System Parameters
42 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 43/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 44/142
■ Switchover software to detect failure in a node and switch the affected software unit to the standbynode, where it can continue operating
■ A mechanism to enable application software to seamlessly continue working with the switched
software unit – normally this is achieved by virtual addressing (although identity switchover isalso 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:
■ Check the information and the installation guides available athttp://sdn.sap.com/irj/sdn/
ha .■ The standalone replicated enqueue server is a major contribution to an HA installation and is
essential for a Java system. We strongly recommend you to use it for an ABAP system.For more information about how to install the standalone replicated enqueue server, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) EnglishSAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP
Technology Client/Server Technology The SAP Lock Concept Standalone Enqueue Server Installing theStandalone Enqueue Server
FeaturesThe following figure shows the essential features of a switchover setup:
2 Planning
2.7 High Availability: Planning the Switchover Cluster
44 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 45/142
Figure 7:
NOTE
This figure and the figures in this section are onlyexamples . Only the instances relevant to theswitchover are shown – for example, the central instance is not shown.These graphics summarize the overall setup and do not show the exact constellation for aninstallation based on one of the available technologies (ABAP, ABAP+Java, or Java).You need to discuss your individual HA setup with your HA partner.
The following figure shows an example of a switchover cluster in more detail:
2 Planning
2.7 High Availability: Planning the Switchover Cluster
2009-05-25 PUBLIC 45 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 46/142
Figure 8:
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 to make 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) |
2 Planning
2.7 High Availability: Planning the Switchover Cluster
46 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 47/142
3 Preparation
3.1 Preparation Checklist
You have to complete the following preparations, which are described in more detail in the linkedsections:1. You make sure that the required operating system users and groups[page47] are created.2. Youset up file systems or – if required – raw devices[page49] and make sure that the required disk space
is available for the directories to be created during the installation.3. If required, youset up virtual host names[page59].4. If you want to install a high-availability system, you perform switchover preparations[page60].5. If you want to share the transport directory trans from another system, export [page60] this
directory to your installation hosts.6. Youinstall the SAP frontend software[page61] on the desktop of the end user.7. You generate the SAP Solution Manager Key[page61] for your SAP system.8. Youinstall the Java Runtime Environment [page62].9. You make sure that the required installation media[page62] are available on each host.
10. Dialog instance only: If you upgraded your SAP System from an earlier source release to a targetrelease lower than SAP ERP 6.0 SR3, then installed EHP 4 with the EHP Installer, and now want toinstall a dialog instance, you have toupdate instance profiles of the existing system[page112].
11. You can continue with Installation[page67].
3.2 Creating Operating System Users and Groups
During the installation, SAPinst checks all required accounts (users, groups) and services on the localmachine. SAPinst checks whether the required users and groups already exist. If not, it creates newusers and groups as necessary.If you do not want SAPinst to create operating systems users, groups, and services automatically, youcan optionally create them before the installation. This might be the caseif you use central usermanagement such as Network Information System (NIS).SAPinst checks if the required services are available on the host and creates them if necessary. See thelog messages about the service entries and adapt the network-wide (NIS) entries accordingly.SAPinst checks the NIS users, groups, and services using NIS commands. However, SAPinst doesnot
change NIS configurations.
3 Preparation
3.1 Preparation Checklist
2009-05-25 PUBLIC 47 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 48/142
Only valid for: HA (UNIX) |
RECOMMENDATION
For a distributed or a high-availability system, we recommend that you distribute accountinformation (operating system users and groups) over the network, for example by using NetworkInformation Service (NIS).
End of: HA (UNIX) |
If you want to use global accounts that are configured on a separate host, you can do this in one of thefollowing ways:
■ You start SAPinst and choose Software Life-Cycle Options Additional Preparations Operating System Usersand Groups. For more information, seeRunning SAPinst [page73].
■
You create operating system users and groups manually.If you need information about how to do this, seeCreating Solaris Groups and Users[page109]
Operating System Users and Groups
SAPinst chooses available operating system user IDs and group IDs unless you are installing an additionalapplication server instance. On an additional application server instance you have to enter the sameIDs as on the host of the primary application server instance.
C AUTION
■
All usersmust have identical environment settings. If you change the environment deliveredby SAP, such as variables, paths, and so on, we donot assume responsibility.■ Donot delete any shell initialization scripts in the home directory of the OS users. This applies
even if you do not intend to use the shells that these scripts are for.■ If you use NFS-V4 file system, you have to create theora<dbsid> user on the NFS server. You
can do this either manually or by running Operating System Users and Groups. This user must havethe same user ID as theora<dbsid> user on the database server.Otherwise, you see the error messageFSL-02098 Could not change owner of ... duringthe installation of the database instance.
■ The user ID (UID) and group ID (GID) of each operating system user and group must beidentical for all servers belonging to the same SAP system.This does not mean that all users and groups have to be installed on all SAP servers.
■ If you are installing an SAP system where the instances are to run onseveral hosts (distributedor high-availability system), make sure that the group ID of groupsapinst is always differentfrom the group ID of any other group (for example, of groupsapsys ) used during theinstallation.Example:You are installing a dialog instance in an existing SAP system.
3 Preparation
3.2 Creating Operating System Users and Groups
48 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 49/142
You must make sure that the group ID of group sapinst created on the host of the dialoginstance is different from the group ID of any other group (for example, of groupsapsys ) onthe central instance host of the existing SAP system.
Users and Groups
User Primary Group Additional Groups Comment
root No primary group is assignedby SAPinst.
sapinst Superuser of the UNIXoperating system
<sapsid>adm sapsys oper, dba, sapinst SAP system administrator<smdsid>adm sapsys sapinst Diagnostics Agent
administratorora<dbsid> dba oper, sapinst Database administrator
The user ora<dbsid> is only required on the host where the database instance runs.
CAUTION
If these operating system users already exist, make sure that they are assigned to groupsapinst .
CAUTION
If you install a distributed system and you use local operating system user accounts instead of central user management (for example, NIS), user<sapsid>adm , sapadm , and the databaseoperating system user must have the same password on all hosts.
Groups and MembersGroups Members
sapsys <sapsid>adm
oper <sapsid>adm, ora<dbsid>
dba <sapsid>adm, ora<dbsid>
sapinst root, <sapsid>adm, ora<dbsid>
3.3 Setting Up File Systems and Raw Devices
The following sections 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:
■ SAP Directories[page50]■ Oracle Directories[page53]■ Setting Up File Systems for High-Availability[page55]■ Configuring Network File System for High Availability[page57]
More Information
If you need information about how to set up file systems and raw devices, seeSetting Up File Systems and Raw Devices for Solaris[page111].
3 Preparation
3.3 Setting Up File Systems and Raw Devices
2009-05-25 PUBLIC 49 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 50/142
3.3.1 SAP Directories
Depending on the installation option you have chosen, SAPinst automatically creates the directorieslisted in the following figures and tables.Before running the installation, you have to set up the required file systems manually. In addition, youhave to make sure that the required disk space for the directories to be installed is available on therelevant 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 theroot directory / .SAPinst prompts you only for the<sapmnt> directory during the installation. For more information,
see also tableParameters Relevant for the File Systemin Basic SAP System Parameters[page36].Only valid for: HA (UNIX) |
NOTE
For more information about how to set up your file systems if you are performing anHAinstallation, seeHigh Availability: Setting Up File Systems[page55].
End of: HA (UNIX) |
C AUTION
SAPinst usessapcpe to replicate the kernel automatically from /usr/sap/<SAPSID>/SYS/exe/
run/DIR_CT_RUN to /usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP systeminstance.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 systemafter patches have been applied.For more information, seeApplying the Latest Kernel and Support Packages[page92].
SAP Directories for an ABAP System
Everynew installation of an ABAP standalone system is Unicode.Non-Unicode for ABAP is still supportedonly if you perform the system copy for a non-Unicodesystemthat has been upgraded to SAP NetWeaver 7.0 SR3.
3 Preparation
3.3 Setting Up File Systems and Raw Devices
50 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 51/142
Figure 9: SAP Directories for an SAP ABAP System (Unicode or Non-Unicode)
The instance name (instance ID) of the ABAP central instance isDVEBMGS<Instance_Number> , and theinstance name of an ABAP dialog instance isD<Instance_Number> .Only valid for: HA (UNIX) |
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) |
EXAM P LE
For example, the file system structure might look as follows:On a central instance with SAP system IDC11 and instance name DVEBMGS00.The ABAP dialog instance has the instance nameD01.
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 administrativepurposes.
The following directories are global, that is, they are accessed by all hosts in the SAP system.
SAP Directories
Directory Description Space Required
<sapmnt>/<SAPSID> Software and data for one SAP system 3.0 GB
3 Preparation
3.3 Setting Up File Systems and Raw Devices
2009-05-25 PUBLIC 51 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 52/142
Directory Description Space Required
This directory is physically located on the SAP global host. Inhomogeneous systems, you need to mount it via NFS (Network FileSystem) for all hosts belonging to the same SAP system. It containsthe following subdirectories:
■ exe
This directory contains executable kernel programs.If you install an SAP system with distributed instances, youhave to share this directory for all hosts with the sameoperating system. For more information, see thePrerequisitesinRunning SAPinst [page73].
■ global
This directory contains log files.If you install an SAP system with distributed instances, youhave to share this directory for all hosts. For more information,
see the Prerequisitesin Running SAPinst [page73].■ profile
This directory contains the start and operations profiles of allinstances.If you install an SAP system with distributed instances, youhave to share this directory for all hosts. For more information,see the Prerequisitesin Running SAPinst [page73].
/usr/sap/<SAPSID> Instance-specific data, symbolic links to the data for onesystemThis directory contains files for the operation of a local instance.There is a subdirectory<INSTANCE_NAME>for each instance installed
on the local instance host. The directorySYScontains only soft linksto appropriate directories in /<sapmnt>/<SAPSID>/ for storing dataused by several instances.There are subdirectories of /usr/sap/<SAPSID>/SYS with symboliclinks to subdirectories of /<sapmnt>/<SAPSID> :
■ /usr/sap/<SAPSID>/SYS/profile is linked to /<sapmnt>/
<SAPSID>/profile■ /usr/sap/<SAPSID>/SYS/global is linked to /<sapmnt>/
<SAPSID>/global■ /usr/sap/<SAPSID>/SYS/exe/run is linked to /usr/sap/
<SAPSID>/SYS/exe/dbg , which is linked to/<sapmnt>/
<SAPSID>/exe
SAPinst sets up these directory structures during the installation.Executables located in/usr/sap/<SAPSID>/SYS/exe/run arereplicated bysapcpe to the exe directory of instances of the type<INSTANCE_NAME>and ASCS<No>.
NOTE
Make sure that sufficient space is available in directory/usr/
sap/<SAPSID>/<INSTANCE_NAME> , since this stores SAP tracesfor the instance. Changes in SAP system profiles can also affectthe disk space.
4.0 GB
/usr/sap/trans Global transport directory for all SAP systems 2.0 GB
3 Preparation
3.3 Setting Up File Systems and Raw Devices
52 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 53/142
Directory Description Space Required
For more information about exporting and mounting the globaltransport directory, see Exporting and Mounting the Global Transport Directory[page60]The global transport directory is used by the Change and TransportSystem (CTS). The CTS helps you to organize developmentprojects in the ABAP Workbench and in Customizing, and thentransport the changes between the SAP systems in your systemlandscape. For more information, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (includingEnhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability
Software Life Cycle Management Software Logistics Change and Transport System
For more information about the directories required for the database instance, seeOracle Directories[page53].
More InformationFor more information about sapcpe , see http://help.sap.com/nw70 SAP NetWeaver 7.0 Library(including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability AppPlatform by Key Capability ABAP Technology Client/Server Technology Local Executables on SAP Instan
Functions of the Automatic Synchronization Program sapcpe
3.3.2 Oracle Directories
The figure below assumes that you have set up one file system for theoracle 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 theroot directory / .
NOTE
Unicode systems require additional hardware resources. You can find more information aboutUnicode SAP systems athttp://service.sap.com/unicode .
Set up the required filesystem nodes for the Oracle database before the installation.
3 Preparation
3.3 Setting Up File Systems and Raw Devices
2009-05-25 PUBLIC 53 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 54/142
Figure 10: Oracle Directories
Oracle Directories
Directory Description Space Required
/oracle Oracle base directory 50 MB for Oracle software/oracle/client File system for Oracle client software
SAPinst creates the directory/oracle/
client/102_64/instantclient duringthe 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 donot delete it after the installation.
3.5 GB
/oracle/<DBSID> Home directory of userora<dbsid>
We recommend that /oracle/<DBSID>
does not reside in the root directory. Itmust reside in a file system with supportfor large files.For more information about how tocreate file systems larger than 2 GB onyour operating system, see:Setting Up File Systems and Raw Devices for Solaris[page111]Therefore, either create /oracle/
<DBSID> as a separate file system withsupport for large files or create/oracle
as a file system with support for large filesand create /oracle/<DBSID> as adirectory in /oracle .
100 MB for files of userora<dbsid> (forexample, log files)
3 Preparation
3.3 Setting Up File Systems and Raw Devices
54 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 55/142
Directory Description Space Required
/oracle/<DBSID>/102_64 Home directory for Oracle instance<DBSID>
(<ORACLE_HOME>).<ORACLE_HOME>must reside on a localdisk. Itcannot be a softlink.
■ Database instance: 4.0 GB■ All other instances: 200 MB
Make sure that this file system haspermissions777 .
/oracle/<DBSID>/origlogA Original set A of redo logs 200 MB/oracle/<DBSID>/origlogB Original set B of redo logs 200 MB/oracle/<DBSID>/mirrlogA Mirrored set A of redo logs 200 MB/oracle/<DBSID>/mirrlogB Mirrored set B of redo logs 200 MB/oracle/<DBSID>/oraarch New standard backup file system for
Oracle offline redo logsUse a separate disk for the file system/oracle/<DBSID>/oraarch .
The file system/oracle/<SAPSID>/saparch still remains but now onlycontains brbackup log files./oracle/
<SAPSID>/saparch is automaticallycreated by SAPinst.
For the installation, the archivedirectory /oracle/<DBSID>/oraarch
requires at least 400 MB free disk space.For the operation of your SAP system,
we recommend that the archivedirectory provides enough space forarchives between two backups. In aproduction system, the amountarchived each day is between 300 MBand 1 GB.
/oracle/<DBSID>/sapreorg Working directory for databaseadministration
1.5 GB
/oracle/<DBSID>/sapdata1 SAP data For space requirements of the SAP datafile systems required for theinstallation, see the following file:<Export_DVD>/DATA_UNITS/EXP1/DB/ORA/DBSIZE.XML .See also theGeneralsection in SAPNote 1300538
/oracle/<DBSID>/sapdata2 SAP data/oracle/<DBSID>/sapdata3
SAP data/oracle/<DBSID>/sapdata4 SAP data
Only valid for: HA (UNIX) |
3.3.3 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 as describedhere. For more information, consult your HA partner.
PrerequisitesYou have already installed the hardware – that is, hosts, disks, and network – and decided how todistribute the database, SAP instances, and (if required) Network File System (NFS) server over thecluster nodes (that is, over the host machines). For more information, seePlanning the Switchover Cluster [page43].
3 Preparation
3.3 Setting Up File Systems and Raw Devices
2009-05-25 PUBLIC 55 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 56/142
Procedure1. Create the file systems or raw partitions for the central services (SCS) instance on shared disks. For
more information, see Setting Up File Systems and Raw Devices[page49].
NOTE
The directories /<sapmnt>/<SAPSID> and /usr/sap/trans have to be mounted from aNetwork File System (NFS), whereas/usr/sap/<SAPSID> is a directory of the AS instance thatis always mounted on the instance (not with NFS).Therefore, if the central instance host isnot the NFS server host, you might have to mountat least the first two file systems ondifferent physical disks from the third file system.CAUTION
Make sure that the mount points under /<sapmnt>/<SAPSID>/ are permanent. Otherwiseautomatic start of the instance services does not work when you reboot the 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.The /usr/sap/<SAPSID> directory contains two subdirectories:
■ SYS contains links to the central directory /<sapmnt>/<SAPSID>
■ <INSTTYPE><NR> contains data for the local AS instanceThe 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 theSYS subdirectory contains only links that do not require any space, it can becreated locally on each cluster node. Therefore, instead of /usr/sap/<SAPSID> , create a file systemfor /usr/sap/<SAPSID>/<INSTTYPE><NR> with the usual <> substitutions. The file name for thecentral instance is usuallyDVEBMGS00. This avoids mount conflicts when switching over to a nodeon which an AS instance is already running. TheDVEBMGS00directory can join the tree /usr/sap/
<SAPSID> instead of mounting on top of it.NOTE
This approach becomes increasingly important when you want to cluster central serviceswhile other instances run on the cluster hosts outside the control of the switchover software,so as to use the resources efficiently. Youmust use this approach for integrated installationsof the AS with ABAP and Java stacks.
3. You assign the local file systems to mount points.4. You assign the shared file systems to mount points in appropriate failover groups.
EXAM P LE
The graphic below shows an example of the file systems and disks in an HA setup
3 Preparation
3.3 Setting Up File Systems and Raw Devices
56 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 57/142
Note that this is only an example. For more information on a setup that meets your needs, consultyour HA partner.
Figure 11:
End of: HA (UNIX) |
Only valid for: HA (UNIX) |
3.3.4 Configuring Network File System for a High-Availability 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 with switchover software. 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:
■ How to protect NFS■ Which switchover cluster nodes NFS is to run on
The NFS configuration might depend on your database system. The directories need to be available forthe SAP system before and after a switchover.
3 Preparation
3.3 Setting Up File Systems and Raw Devices
2009-05-25 PUBLIC 57 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 58/142
C AUTION
Make sure that the mount points under /<sapmnt>/<SAPSID>/ are permanent. Otherwiseautomatic start of the instance services does not work when you reboot the system.
Procedure1. Check the NFS directories, several of which need to be shared between all instances of a system.
These directories are:■ /<sapmnt>/<SAPSID>/profile
Contains the different profiles to simplify maintenance■ /<sapmnt>/<SAPSID>/global
Contains log files of batch jobs and central SysLog■ /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 atleast one AS instance of each system, but preferably by all.
■ /<sapmnt>/<SAPSID>/exe
Contains the kernel executables. The best solution is to store them locally on all AS instancehosts.
2. Since you can protect NFS by a switchover product, it makes sense to install it on a cluster node.The requirements of your database system might 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 of a“busy NFS mount” on the standby node. You can use the following workaround to solve thisproblem:1. On the primary server, mount the disks containing the directories:
/export/usr/sap/trans
/export/<sapmnt>/<SAPSID>2. The primary server creates soft links to the directories with the original SAP names:
/usr/sap/trans —> /export/usr/sap/trans
/<sapmnt>/<SAPSID> —> /export/<sapmnt>/<SAPSID>
Alternatively the primary server can also mount the directories:/export/usr/sap/trans —> /usr/sap/trans
/export/<sapmnt>/SID —> /<sapmnt>/<SAPSID>
3. The primary server exports:/export/usr/sap/trans
3 Preparation
3.3 Setting Up File Systems and Raw Devices
58 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 59/142
/export/<sapmnt>/<SAPSID>
4. The standby NFS mounts:from virt.IP:/export/usr/sap/trans to /usr/sap/trans
from virt.IP:/export/<sapmnt>/<SAPSID> to /<sapmnt>/<SAPSID>
If the primary node goes down and a switchover occurs, the following happens:■ These directories on the standby node become busy:
/usr/sap/trans
/<sapmnt>/<SAPSID>
■ The standby node mounts disks to:/export/usr/sap/trans
/export/<sapmnt>/<SAPSID>
■ The standby node configures the virtual IP addressvirt.IP
■ The standby node exports:/export/usr/sap/trans
/export/<sapmnt>/<SAPSID>
■ These directories on the standby node are accessible again:/usr/sap/trans
/<sapmnt>/<SAPSID>
End of: HA (UNIX) |
3.4 Using Virtual Host Names
You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape toconceal their physical network identities from each other. This can be useful when quickly movingSAP servers or complete server landscapes to alternative hardware without having to reinstall orreconfigure.Only valid for: HA (UNIX);HA (z/OS) |
Virtual host names are also required for a high-availability installation. For more information, seePerforming Switchover Preparations for High Availability[page60].End of: HA (UNIX);HA (z/OS) |
PrerequisitesMake sure that the virtual host name can be correctly resolved in your Domain Name System (DNS)setup.
ProcedureProceed as described inSAP Note 962955.
3 Preparation
3.4 Using Virtual Host Names
2009-05-25 PUBLIC 59 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 60/142
Only valid for: HA (UNIX) |
3.5 Performing Switchover Preparations for High Availability
If you want to use a virtual host name, you have to set the SAPinst propertySAPINST_USE_HOSTNAMEtospecify the required virtual host name before you start SAPinst. For more information, seeRunningSAPinst [page73].
ProcedureAssign the virtual IP addresses and host names for the ASCS instance, and (if required) NFS toappropriate failover groups.
NOTE
For more information on virtual addresses and virtual host names and how to assign resourcesto failover groups, ask your HA partner.
End of: HA (UNIX) |
3.6 Exporting and Mounting the Global Transport Directory
In your SAP system landscape, a global transport directory for all SAP systems is required.■ If this global transport directory already exists, make sure that it is exported on the global transport
directory host and mount it on the SAP instance installation host.■ If this global transport directory does not exist, proceed as follows:
● Create the transport directory (either on the central instance host or on a file server).● Export it on the global transport directory host.● If you did not create the transport directory on your SAP instance installation host, mount it
there.
Procedure
Exporting the Transport Directory 1. Log on as userroot 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 userroot to the central or dialog instance host where /usr/sap/trans is to be mounted.
3 Preparation
3.5 Performing Switchover Preparations for High Availability
60 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 61/142
2. Create the mount point /usr/sap/trans .3. Mount /usr/sap/trans using Network File System (NFS) from the exporting host.
More InformationMounting Directories via NFS for Solaris[page114]
3.7 Installing the Front-End Software
For the installation, make sure that the front-end software is installed on at leastone comput er in yoursystem environment.With installation software NW SAPSetup for the SAP Front-End, you can optimize the deployment of SAP GUI 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 or higher.For more information about installing the front-end software, see the documentation SAP Front End Installation Guide - <Current Release>at:
http://service.sap.com/installNW70 Installation - Clients
3.8 Generating the SAP Solution Manager Key
You must generate the Solution Manager key because the installation tool prompts for it duringtheinstallation. Without this key, the installation process cannot continue . For more information aboutSAP Solution Manager and its role within your system landscape, see the Master Guide of your SAPapplication.
Procedure
1. If SAP Solution Manager is not yet available in your system landscape, proceed as follows:
1. Order SAP Solution Manager as described inSAP Note 628901.2. Install SAP Solution Manager as described in the documentationInstallation Guide – SAP Solution
Manager <Current Release> on <OS>: <Database>, which is available at:http://service.sap.com/instguides SAP Components SAP Solution Manager <Current
Release>2. Generate the SAP Solution Manager key as described inSAP Note 811923.
Result
The SAP Solution Manager system displays the key for which you are prompted during the installation
of your SAP system.
3 Preparation
3.7 Installing the Front-End Software
2009-05-25 PUBLIC 61 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 62/142
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 for SAPinst.
NOTE
If required, you can perform aremote 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, seePerforminga Remote Installation with SAPinst [page118].
Procedure
1. Check the JRE versions that are released for SAP systems in the Product Availability Matrix (PAM):1. Go tohttp://service.sap.com/pam .2. ChooseStart PAM with navigation by category.3. On the right-hand panel, choose SAP Application Components <your product>.4. Choose tabstrip JSE Platforms.
NOTE
For more information about how to download it, see the relevant SAP Note for your operatingsystem, which is referenced near the beginning of SAP Note 723909.
2. Make sure a valid JRE version is installed, as follows:■ If the JRE is not already installed, you need to download and install it.■ 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 JRE ispart of the JDK (Java Development Kit).
■ If the JRE is already installedCheck the installed version of the JRE by entering:java -version
NOTE
SAPinst checks environment variableSAPINST_JRE_HOME for a valid Java runtime environment.If SAPINST_JRE_HOME is not found, SAPinst also checksJAVA_HOME.
3.10 Preparing the Installation DVDs
This section describes how to prepare the installation DVDs, which are available as follows:■ You obtain the installation DVDs as part of the installation package.■ You can also download the installation DVDs from SAP Service Marketplace.
3 Preparation
3.9 Installing the Java Runtime Environment
62 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 63/142
Procedure1. 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 during
the installation.CAUTION
The media names listed below areabbreviated .You can find the full names in section Media Informationin the corresponding Master Guidesat:
http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package4 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 on theusage typeAS ABAP:
NOTE
For a central system, where all mandatory instances reside on one host, you need theinstallation DVDs that are required for the central instance and database instance.
SAP Instance Installation Required DVDs
Global host preparation ■ Installation Master DVD■ Kernel DVD
Central instance, dialog instance ■ Installation Master DVD■ Kernel DVD■ RDBMS Client DVD
Database instance ■ Installation Master DVD■ Kernel DVD■ SAP ERP Installation Export DVD■ RDBMS DVD■ RDBMS Patch DVD (if available)
NOTE
For an MCOD system you require the RDBMSClient DVD instead of the RDBMS DVD and theRDBMS Patch DVD (if available).
■ RDBMS Client DVD
2. Make the required installation media available on each installation host.If you need information about how to mount DVDs on Solaris, seeMounting a CD / DVD for Solaris[page113].
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.
3 Preparation
3.10 Preparing the Installation DVDs
2009-05-25 PUBLIC 63 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 64/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 65/142
51031387_2...
■ Title
All 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 exampleLABELIDX.ASC . Always accept
withYes
.
3 Preparation
3.10 Preparing the Installation DVDs
2009-05-25 PUBLIC 65 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 66/142
This page is left blank for documents that are printed on both sides.
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 67/142
4 Installation
4.1 Installation Checklist
This section includes the installation steps that you have to perform for the:■ Central system■ Distributed system■ High-availability system■ Dialog instance
Detailed information about the steps is available in the appropriate section. For more information aboutthe various installation options, seeInstallation Options Covered by This Guide[page13].
Central System
1. Youinstall the SAP system with SAPinst [page73].NOTE
Do not install the Oracle database software before you run SAPinst.SAPinst stops and prompts you toinstall the Oracle database[page82] while the installation of
the database instance is running.This action isnot required if you install an SAP system in anexisting database (MCOD)[page103].
2. You continue with Post-Installation[page87].
Distributed System
1. If you want to share the transport directory trans from another system, you have to mount [page60] it from this system. Otherwise, we recommend that you share thetrans directory that is createdduring the installation of the central instance ( /usr/sap/tra ns ).
2. On the SAP global host , proceed as follows:
1. Yourun SAPinst [page73] to prepare the global host.This is to set up the global directories<sapmnt>/<SAPSID>/exe , <sapmnt>/<SAPSID>/
profile , <sapmnt>/<SAPSID>/global .2. Youexport the global directories[page72] to the database instance host, to the central instance
host, and – if required – to the hosts where you want to install one or more dialog instances.3. On the database instance host , proceed as follows:
1. Youmount the exported global directories[page72] from the SAP global host (<sapmnt>/<SAPSID>/
exe , <sapmnt>/<SAPSID>/profile , <sapmnt>/<SAPSID>/global ) and SAP transport host (/usr/sap/tr ans ).
2. Yourun SAPinst [page73] to install the database instance.
4 Installation
4.1 Instal lation Checklist
2009-05-25 PUBLIC 67 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 68/142
NOTE
Do not install the Oracle database software before you run SAPinst.SAPinst stops and prompts you toinstall the Oracle database software[page82] while the
installation of the database instance is running.This action isnot required if you install an SAP system in an existing database (MCOD)[page103].
4. On the central instance host , proceed as follows:NOTE
You can use the SAP transport host or the SAP global host as your central instance host.
1. Youmount the exported global directories[page72] from the SAP global host (<sapmnt>/<SAPSID>/
exe , <sapmnt>/<SAPSID>/profile , <sapmnt>/<SAPSID>/global ) and SAP transport host (/
usr/sap/trans ).2. Yourun SAPinst [page73] to install the central instance.
5. If required, you install one or more dialog instances on the respective hosts as described later inthis section.1. Youmount the exported global directories[page72] from the SAP global host (<sapmnt>/<SAPSID>/
exe , <sapmnt>/<SAPSID>/profile , <sapmnt>/<SAPSID>/global ) and SAP transport host (/usr/sap/trans ).
2. Yourun SAPinst [page73] to install the dialog instance.6. You continue with Post-Installation[page87].
Graphical Overview
The following figure shows how you install the various instances in a distributed system:
4 Installation
4.1 Instal lation Checklist
68 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 69/142
Figure 12: Distribution of Instances in an ABAP System
Only valid for: HA (UNIX) |
High-Availability System
This section describes how you install a high-availability (HA) system consisting of two nodes (host
A and host B ). For more information, consult your HA partner.This procedure describes the steps that are required for a hardware cluster consisting of two nodes(host A and host B):1. You need to make sure that your system meets the hardware and software requirements[page24].2. If you want to share the transport directory trans from another system, you have to mount [page
60] it from this system. Otherwise, we recommend that you share thetrans directory that is createdduring the installation of the central instance (see below).
3. You set up the switchover cluster infrastructure as follows:1. Yourun SAPinst [page73] to install the ABAP central services instance (ASCS) using thevirtual
host name[page59] on the primary cluster node, host A .2. Youexport global directories[page72] in<sapmnt>/<SAPSID> to the database host and to the
central instance host.3. You prepare the standby cluster node, host B , and make sure that it has all the necessary file
systems[page55], mount points, and (if required) Network File System (NFS).4. You set up the user environment on the standby node, host B as follows:
1. You make sure that you use the same user and group IDs as on the primary node.2. You create the home directories of users and copy all files from the home directory of the
primary node.
4 Installation
4.1 Instal lation Checklist
2009-05-25 PUBLIC 69 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 70/142
For more information about the required operating system users and groups, seeCreatingOperating System Users[page47].
5. You configure the switchover software and test that switchover functions correctly to all
standby nodes in the cluster.6. You repeat the following steps until you have finished installing the enqueue replication server
(ERS) onall nodes in the cluster:1. You perform the switchover to a node where you want to install the ERS.2. You install the ERS as described in:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1)English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by KeyCapability ABAP Technology Client/Server Technology The SAP Lock Concept Standalone
Enqueue Server Installing the Standalone Enqueue Server 4. On the database instance host , proceed as follows:RECOMMENDATION
We recommend that the database instance is part of the hardware cluster or of any otherproprietary high-availability solution for the database.
1. You prepare the database instance host and make sure that it has all the necessary file systems[page55], mount points, and (if required) Network File System (NFS).
2. Yourun SAPinst [page73] to install the database instance.NOTE
Do not install the Oracle database software in advance. During the installation of thedatabase instance, SAPinst stops the installation and prompts you to install the Oracledatabase software.This action isnot required if you install an SAP system in an existing database (MCOD)[page103].
5. On the central instance host , proceed as follows:NOTE
In a high-availability installation, the central instance doesnot need to be part of the cluster
because it is no longer a single point of failure (SPOF). The SPOF is now in the central servicesinstance (ASCS), which is protected by the cluster.
1. You prepare the central instance host and make sure that it has all the necessary file systems[page55], mount points, and (if required) Network File System (NFS).
2. Yourun SAPinst [page73] to install the central instance.3. If you want to use the shared transport directory trans from another system, you also mount
[page60] this directory (see above).
4 Installation
4.1 Instal lation Checklist
70 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 71/142
6. We recommend that you install dialog instances with SAPinst to create redundancy. Theapplication server instances are not a SPOF. Therefore, you donot need to include these instancesin the cluster.
1. Youmount the global directories[page72] in<sapmnt>/<SAPSID> .2. Yourun SAPinst [page73] to install the dialog instance.3. If you want to use the shared transport directory trans from another system, you also mount
[page60] this directory (see above).7. You continue with Post-Installation[page87].
Graphical Overview
The following figure provides an overview of how you install the various instances in a high-availabilityinstallation:
Figure 13: Distribution of Instances in a High-Availability ABAP System
End of: HA (UNIX) |
Dialog Instance
You perform the following steps on each host where you install the dialog instances.1. You make sure that the global directories of the SAP system for which you want to install the dialog instance
mounted [page72] on the host on which you want to install the dialog instance.2. Yourun SAPinst [page73] to install the dialog instance.3. You continue with Post-Installat ion[page87].
4 Installation
4.1 Instal lation Checklist
2009-05-25 PUBLIC 71 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 72/142
4.2 Exporting and Mounting Global Directories: Distributedand High-Availability Systems
If you install a database or a dialog instance on a host other than the SAP Global host, you must mountdirectories from the SAP Global Host. The SAP Global Host is in most cases the host on which thecentral instance runs (In a High-Availability system, this is the host on which the ABAP central servicesinstance (ASCS) runs).
Prerequisites■ If you want to install the executables locally instead of sharing them, donot mount the exe
directory with Network File System (NFS). Instead, create<sapmnt>/<SAPSID>/exe as a localdirectory (not a link) with a minimum of 1100 MB free space.
■ If you are installing a heterogeneous SAP system (that is, the instances are installed on differentoperating-system platforms), do not mount the exe directory. For more information, seeHeterogeneous SAP System Installations[page129].
Procedure1. Log on to the SAP Global host as userroot and export the following directories with root access
to the host on which you want to install the new instance:<sapmnt>/<SAPSID>/exe
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
For more information, seeMounting Directories via NFS for Solaris[page114].CAUTION
Make sure that the global transport directory is mounted on every host where you want toinstall an SAP instance. For more information, seeExporting and Mounting the Global Transport Directory[page60]. Otherwise, the installation fails.
2. Log on to the host of the new instance as userroot .3. Create the following mount points and mount them from the SAP Global host:
<sapmnt>/<SAPSID>/exe
<sapmnt>/<SAPSID>/profile<sapmnt>/<SAPSID>/global
CAUTION
Make sure that these mount points are permanent. Otherwise automatic start of the instanceservices does not work when you reboot the system.
4 Installation
4.2 Exporting and Mounting Global Directories: Distributed and High-Availability Systems
72 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 73/142
Only valid for: HA (UNIX) |
4.3 Performing a High-Availability Installation
This section describes how to perform a high-availability (HA) installation. For more information,consult your HA partner.
Prerequisites■ You have completed all preparations, including switchover preparations for high availability[page60].■ For each installation option, specify the appropriate virtual host name with the SAPinst property
SAPINST_USE_HOSTNAME, as described inRunning SAPinst [page73].
Procedure1. Run SAPinst [page73] to install the central services instance (ASCS) using the virtual host name
on the primary cluster node, host A .2. Prepare the standby node,host B . You need to make sure that it meets the hardware and software
requirements and it has all the necessary file systems, mount points, and (if required) NetworkFile System (NFS), as described inPerforming Switchover Preparations for High Availability[page60]
3. Set up the user environment on the standby node, host B .For more information, seeCreating Operating System Users[page47]. Make sure that you use the sameuser and group IDs as on the primary node. Create the home directories of users and 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 [page73] on the primary node, host A.
NOTE
In a high-availability installation, the central instance doesnot need to be part of the clusterbecause it is no longer a single point of failure (SPOF). The SPOF is now in the central servicesinstance (ASCS), which is protected by the cluster.
7. If required,install additional dialog instances with SAPinst [page73] to replicate the SAP system services
that are not a SPOF. These nodes donot need to be part of the cluster.
NOTE
Make sure that you complete the post-installation activities for high availability.
End of: HA (UNIX) |
4.4 Running SAPinst
This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a GUI and a GUIserver, which both use Java.
4 Installation
4.3 Performing a High-Availability Installation
2009-05-25 PUBLIC 73 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 74/142
This section describes an installation where SAPinst, GUI, and the GUI server are running on thesame host and on the local display.If you need to see the installation on a remote display, we recommend you perform a remote installation with
SAPinst [page118], where the GUI is running on aseparate host from SAPinst and the GUI server.Alternatively you can use an X server for Microsoft Windows or other remote desktop tools likevncviewer or nxserver/nxclient – offered by various vendors or open source – for remote access to theGUI on Windows workstations. We recommend you use the Hummingbird Exceed X Server, whichwe use to validate installations with SAPinst. For more information, seeSAP Note 1170809.
Useful Information About SAPinst
■ When you start SAPinst, it automatically starts the GUI and GUI server. The GUI connects usinga secure SSL connection to the GUI server and the GUI server connects to SAPinst.
■ SAPinst creates the installation directorysapinst_instdir directly below the temporary directory.SAPinst finds the temporary directory by checking the value of theTEMP, TMP, or TMPDIR
environment variable. If no value is set for these variables, SAPinst creates the installation directorysapinst_instdir directly below the /tmp directory by default.If you want SAPinst to create the installation directorysapinst_instdir in another directorythan /tmp , set the environment variable TEMP, TMP, or TMPDIR to the appropriate directory beforeyou start SAPinst.
Shell Used Command
Bourne shell (sh)TEMP=<directory>
export TEMP
C shell (csh) setenv TEMP <directory>
Korn shell (ksh) export TEMP=<directory>
CAUTION
Make sure that the installation directory is not mounted with NFS, or there might be problemswhen the Java Virtual Machine is started.RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed.■ SAPinst creates a subdirectory for each installation option calledsapinst_instdir/
<installation_option_directory> .■ SAPinst extracts itself to the temporary directory. The extracted files are deleted again after SAPinst
has stopped running.Directories calledsapinst_exe.xxxxxx.xxxx sometimes remain undeleted in the temporarydirectory. You can safely delete them.The temporary directory also contains the SAPinst self-extractor log filedev_selfex.out , whichmight be useful if an error occurs.
4 Installation
4.4 Running SAPinst
74 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 75/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 76/142
environment variables TEMP, TMP, or TMPDIR to another directory with 200 MB free space forthe SAPinst executables.
● Make sure that the temporary directory has the permissions 777.■ Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime
Environment (JRE).■ 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 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
■ Check the following values for userroot :● In csh , execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
● 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) 8192memory(KBytes) unlimited
If your parameter settings differ from the settings above, change these values accordingly.EXAM P LE
If you have to change the value for descriptors to8192 , proceed as follows:In csh , execute:limit descriptors 8192
In sh or ksh execute:ulimit -n 8192
4 Installation
4.4 Running SAPinst
76 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 77/142
■ If you want to install a dialog instance to an existing SAP system, make sure that:● There is exactly one entry in the /usr/sap/sapservices file for each SAP instance installed
on this host. Be sure to check that the entry refers to the correct profile.● There are no profile backup files with an underscore “_” in their profile name. If so, you must
replace the “_” with a “.”.EXAM P LE
Rename /usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2_D20081204 to /
usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2.D20081204 .
Procedure
1. Log on to the installation host as userroot .CAUTION
Do not use the user <sapsid>adm .CAUTION
Make sure that the root user has not set any environment variables for a different SAP systemor database.
2. Mount the Installation Master DVDMount the DVDs locally . We donot recommend that you use Network File System (NFS), becausereading from DVDs mounted with NFS might fail.For more information about mounting DVDs, seeMounting a CD / DVD for Solaris[page113].
3. Start SAPinst from the Installation Master DVD by entering the following commands:cd <Installation Master_DVD>/IM_<OS>
./sapinst
NOTE
If you want to use a virtual host name, start SAPinst with the SAPinst propertySAPINST_USE_HOSTNAMEas follows:./sapinst SAPINST_USE_HOSTNAME=<virtual host name>
CAUTION
■
Make sure that the installation directory is not mounted with NFS, or there might beproblems when the Java Virtual Machine is started.■ Make sure that your current working directory is not an IM_<OS> directory belonging to
another operating system.For example, the following commands areincorrect and cause an error:$ cd /sapcd2/IM_HPUX_IA64
$ /sapcd2/IM_HPUX_PARISC/sapinst
The following commands arecorrect :$ cd /sapcd2/IM_HPUX_PARISC
$ /sapcd2/IM_HPUX_PARISC/sapinst
4 Installation
4.4 Running SAPinst
2009-05-25 PUBLIC 77 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 78/142
4. In the Welcomescreen, choose one of the following installation options:NOTE
When you start the installation from a 32-bit installation master DVD, all you see is the folder
Software Life-Cycle Optionson the Welcomescreen.■ <Your SAP product> SAP Application Server ABAP <Database> <System Variant>
For more information about available installation options, seeSAPinst Installation Options[page79].
■ Software Life-Cycle OptionsFor more information about available installation options, seeSAPinst Installation Options[page79].
5. Follow the instructions in the SAPinst input screens and enter the required parameters.
NOTEFor more information about the input parameters, position the cursor on the parameter andpress F1 .
After you have entered all requested input parameters, SAPinst displays theSummaryscreen. Thisscreen shows both the parameters that you entered and those that SAPinst set by default.
6. If required, change the displayed parameters as follows:1. Select the parameters you want to change.2. ChooseRevise.
SAPinst displays input screens for the selected parameters.3. 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 andprompts you to install the Oracle database software[page82].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
instance installation by choosingOK in the GUI of the database instance installation.■ Check SAP Note 841728for known installation problems with Oracle 10g.
8. If required, delete directories with the namesapinst_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
Keep all installation directories until you are sure that the system, including all instances, iscompletely and correctly installed. Once the system is completely and correctly installed,
4 Installation
4.4 Running SAPinst
78 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 79/142
make a copy of the installation directories with all their contents. Save the copy to a physicallyseparate medium, such as a DVD or a USB drive that is separate from your installation hosts.This might be useful for analyzing issues occurring later when you use the system. For security
reasons, do not keep installation directories on installation hosts, but make sure that youdelete them after saving them separately.
9. We recommend that you delete the directory <user_home>/.sdtgui/ .10. If you copied installation DVDs to your hard disk, you can delete these files when the installation
has successfully completed.
More Information■ Using SAPinst GUI [page115]■ Interrupted Installation with SAPinst [page116]■ Performing a Remote Installation with SAPinst [page118]■ Starting SAPinst GUI Separately[page119].■ Entries in the Services File Created by SAPinst [page121]■ Troubleshooting with SAPinst [page129]
4.5 SAPinst Installation Options
This section provides information about the following in SAPinst:■ Installation Options■ Software Life-Cycle Options
NOTE
■ Choose the required installation options from the tree structure exactly in the order theyappear for each system variant.
■ If you want to use global accounts, which are configured on separate hosts, you must run theinstallation option Operating System Users and Groups before you start the installation of the SAP
system (see tableSoftware Life-Cycle Optionsbelow).■ If required, install a dialog instance for a central system (all instances on one host) or
distributed system by choosing <SAP System> Software Lif e-C ycle Options Application Server <Database> Dialog Instance.
Installation Options
You choose SAP Systems with <your database>to install an SAP system with usage types or software units.You can install the following system variants:
■ Central System
4 Installation
4.5 SAPinst Installation Options
2009-05-25 PUBLIC 79 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 80/142
Installation Options for a Central System
Installation Option Remarks
Central System Installs a complete SAP system including the following instances on one host:● Database instance● Central instance
You can install a central system in the following parameter modes:● Typical Mode
If you chooseTypical, the installation is performed with default settings.As a result, you have to respond to only a small selection of prompts. If you want to change any of the default settings, you can do so on theParameter Summaryscreen.
● Custom ModeIf you chooseCustom, you are prompted for all parameters. At the end,you can still change any of these parameters on theParameter Summaryscreen.NOTE
If you change a parameter with theRevisebutton on the Parameter Summaryscreen, the installer takes you to the screen where you canchange the parameter. Depending on the changes, the installer mightguide you through other screens containing default parameters that ithas already processed. This might also happen if you pressBackinsteadof Next on the screenNOTE
You require at least usage type AS Java or AS ABAP. You can choose theusage types on theSAP System > Software Unitsscreen.
■
Distributed SystemInstallation Options for a Distributed System
Installation Option Remarks
Global Host Preparation Mandatory step in installing a distributed SAP system withusage types or software units based onAS ABAP.Prepares the SAP global host for your SAP system by doingthe following:
● Preparing the file system● Creating the profiles● Installing the executables
Database Instance Mandatory step in installing a distributed SAP system.Installs a database instance.You must have already completed the Global Host Preparation.
Central Instance Mandatory step in installing a distributed SAP system onseveral hosts.Installs a central instance.
NOTE
You require at least usage type AS Java or AS ABAP.You can choose the usage types or software units onthe SAP System > Software Unitsscreen.
You must have finished the database instance installation.
4 Installation
4.5 SAPinst Installation Options
80 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 81/142
■ Only valid for: HA (MSCS);HA (UNIX);HA (z/OS) |
High-Availability System
Installation Options for a High Availability System
Installation Option RemarksCentral Services Instancefor ABAP (ASCS)
Installs a central services instance for ABAP (ASCS) and prepares the SAP globalhost
Database Instance Installs a database instanceCentral Instance Installs a central instanceDialog Instance Installs a dialog instance
NOTE
You might need to install dialog instances on 32-bit operating systems if you want to use 32-bit SAP NetWeaver components, such as Adobedocument services. However, first check whether such 32-bit
components can run on 64-bit operating systems. If so, we recommendrunning these 32-bit components on a 64-bit operating system. 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-bitsystems.
End of: HA (MSCS);HA (UNIX);HA (z/OS) |
Software Life-Cycle Options
You use the options located in this folder to perform the following tasks or to install the followingcomponents:
Software Life-Cycle OptionsInstallation Option Remarks
Additional PreparationOptions
These preparation tasks comprise:■ Operating System Users and Groups
Allows you to use global accounts that are configured on a separate host.C AUTION
Perform this SAPinst optionbefore you start the installation of yourSAP system.
■ Prerequisites CheckChecks your hardware and software requirements before you start theinstallation.Otherwise, SAPinst automatically checks the hardware and softwarerequirements during the installation with the Prerequisite Checker . If any changesare necessary to the SAP system or operating system settings, SAPinstautomatically prompts you. For more information, see Running the PrerequisitesChecker in Standalone Mode[page20].
Application Server Choose Application Server <Database> Dialog Instanceto install one or moredialog instances in an already installed SAP system, if required.
NOTE
You might need to install dialog instances on 32-bit operating systems if youwant to use 32-bit SAP NetWeaver components, such as Adobe documentservices. However, first check whether such 32-bit components can run on
4 Installation
4.5 SAPinst Installation Options
2009-05-25 PUBLIC 81 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 82/142
Installation Option Remarks
64-bit operating systems. If so, we recommend running these 32-bitcomponents on a 64-bit operating system. If not, you can install an SAP dialoginstance on 32-bit operating systems to run these components. For all otherSAP instances, you must use 64-bit systems.
LDAP Registration LDAP SupportSets up LDAP support for an application server instance.Choose this option once per SAP system andafter you have:1. Configured the Active Directory on a Windows host by choosing LDAP
Registration Active Directory ConfigurationYou have to configure the directory server only once. Afterwards all SAPsystems that should register in this directory server can use this setup.
NOTE
The option Active Directory Configurationis only available for Windows.2. Installed an application server instanceFor more information about LDAP and Active Directory, seeIntegration of LDAP Directory Services[page105].
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 optionalstandalone units.For more information, seeDeleting an SAP System[page130].
4.6 Oracle Database Software Installation
SAPinst prompts you to install the Oracle database.Proceed as follows to install the Oracle database software:
Process Flow
1. Youupdate SAP-specific files in the Oracle stage area[page82].2. Yourun the Oracle Universal Installer [page83]3. Youinstall the current patch set [page85]
4. Youinstall required interim patches[page85]
4.6.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 well as theresponse files.Before starting the Oracle software installation, you need to update thisSAP folder so that the newestversions of the scripts or response files are used.
4 Installation
4.6 Oracle Database Software Installation
82 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 83/142
Procedure1. Rename the originalSAP folder by performing one of the following:
■ mv /oracle/stage/102_64/database/Disk1/SAP
/oracle/stage/102_64/database/Disk1/SAP_ORIG■ 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 819830and copy it to a temporarylocation such as /tmp .
3. Extract the zip file by performing one of the following:■ cd /oracle/stage/102_64/database
unzip /tmp/RDBMS_SAP.zip
■ 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.6.2 Running the Oracle Universal Installer
To install the Oracle database software you run the Oracle Universal Installer (OUI).
Procedure
1. Log on as userora<dbsid> .Since you are already logged on as userroot , you can switch to userora<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 systemor a new operating system version, the Oracle Universal Installer might not yet recognize or supportthis operating system. Follow the instructions in SAP Note 980426.
3. Make sure that the DISPLAY environment variable is set to<host_name>:0.0 , where<host_name> is the host on which you want to display the GUI of the Oracle Universal Installer
(OUI).
Shell Used Command
Bourne shell (sh) DISPLAY=<host_name>:0.0
export DISPLAY
C shell (csh) setenv DISPLAY <host_name>:0.0
Korn shell (ksh) export DISPLAY=<host_name>:0.0
4. Start the OUI with the userora<dbsid> by entering one of the following:■ cd /oracle/stage/102_64/database/Disk1/SAP
./RUNINSTALLER
■ cd /oracle/stage/102_64/database/SAP
4 Installation
4.6 Oracle Database Software Installation
2009-05-25 PUBLIC 83 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 84/142
./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 group asdba .
Accept the OUI proposal and continue by choosingNext .
Available Product Components Confirm the default selections by choosingNext .Product-Specific Prerequisite ChecksThis phase checks if all necessary requirements for
installing 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 screen
and fix the problem if possible.Alternatively you can verify the items manually andconfirm them by clicking the checkbox. You can finddetails about each check by clicking on the relevantitem.
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.sh with the userroot , and confirm the dialog box by choosingOK .If this is the first time that the Oracle software hasbeen installed on this host, the OUI also asks you toexecute a second script,/oracle/oraInventory/orainstRoot.sh , as theroot user. Execute this scriptas well.Continue by choosing Next .
6. At the end of the installation, in case there are any Configuration Assistants that have been startedautomatically (for example, Oracle Net) chooseCanceland terminate the Net Config Assistant. Youcan ignore messages that some of the config assistants failed to complete successfully.The Installer finishes, reporting that the Oracle installation was successful. It also informs youabout 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, chooseExit and confirm the dialog box that appears.
NOTE
You can now access the Oracle 10.2 online documentation, which was installed during thelast step. You can find the entry point to the Oracle online documentation at $ORACLE_BASE/
doc/index.htm .
4 Installation
4.6 Oracle Database Software Installation
84 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 85/142
4.6.3 Installing the Current Patch Set
After the Oracle database software installation, you need to install the current Oracle Database 10gRelease 2 (10.2) patch set.
Prerequisites■ For more information on the latest patch set available for Oracle 10.2 seeSAP N ote 871735.■ For more information about how to install the patch set, see the patch set READMEfile.
CAUTION
Do not perform any of the post-installation steps mentioned in the patch set READMEfile. 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
Oracle 10.2. Therefore, make sure that you do not perform the post-installation stepsmentioned in the READMEfile.■ You only have to install the latest (that is, the current) patch set.
Procedure
1. Log on at the operating system level with theora<dbsid> user.2. Install the patch set as described on the patch setREADMEfile.
For more information, seeSAP Note 839187.
4.6.4 Install ing Required Interim Patches
After the Oracle database software installation, you need to install required interim patches, using theOracle tool OPatch. You need these interim patchesin addition to the current patch set.
RECOMMENDATION
You can install all the required interim patches in a single step using the Oracle tool MOPatch,which you can find atSAP Note 1027012.MOPatch can also download patches directly from SAP Service Marketplace and check for anypotential patch conflicts.
Prerequisites■ Make sure you have alreadyinstalled the current patch set [page85].■ Check SAP Note 871096to find the list of required patches to be installed.■ Check SAP Note 839182for instructions on how to use OPatch.
Procedure
1. Log on at the operating system level as theora<dbsid> user.2. Install the patches, following the instructions in SAP Note 839182.
4 Installation
4.6 Oracle Database Software Installation
2009-05-25 PUBLIC 85 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 86/142
NOTE
You can apply the patches in any order.We recommend that you first copy the patches to a directory calledora_patches in
$ORACLE_HOME.3. After all the patches have been successfully applied, you can query the status with the following
command:$ORACLE_HOME/OPatch/opatch lsinventory
This command lists all the patches that have been applied to the software installation.
4 Installation
4.6 Oracle Database Software Installation
86 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 87/142
5 Post-Installation
5.1 Post-Installation ChecklistNOTE
In a central system, all mandatory instances are installed on one host. Therefore, if you areinstalling a central system, you can ignore references to other hosts.
You have to complete the following post-installation steps, which are described in more detail in the
linked sections:1. If required, you perform a full installation backup[page99] immediately after the installation has finished.2. You check whether you can log on to the application server [page87].
NOTE
In a distributed or high-availability system you check whether you can log on to every instanceof the SAP system that you installed.
3. Youconfigure user management [page88].4. Youensure user security[page89].5. Youinstall the SAP license[page91].6. Only valid for: HA (UNIX) |
If you installed a high-availability system, youset up the licenses for high availability[page91].End of: HA (UNIX) |
7. Youapply the latest kernel and Support Package stacks[page 92].8. Youconfigure the remote connection to SAP support [page92].9. Youinstall the SAP Online Documentation[page93].10. You perform initial ABAP configuration[page93].11. On the database instance host, you perform the Oracle-specific post-installation steps[page97].
12. To connect your SAP system to an existing central system landscape directory (SLD), youconfigurethe connection to a central System Landscape Directory (SLD)[page98].13. Youimplement ERP ABAP Add-On Components[page99].14. You perform the client copy[page99].15. You perform a full backup of the installation[page99].
5.2 Logging On to the Application Server
You need to check that you can log on to the SAP system with the standard users, given in the tablebelow.
5 Post-Installation
5.1 Post-Installation Checklist
2009-05-25 PUBLIC 87 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 88/142
ABAP Users
User User Name Client
SAP system user SAP* 000, 001, 066
DDIC 000, 001
Prerequisites■ The SAP system is up and running.■ You have already installed a front end.
Procedure
Logging On to the ABAP Application Server
1. Start SAP Logonon the host where you have installed the front end as follows:■
SAP GUI forWindows :Choose Start All Programs SAP Front End SAP Logon.
■ SAP GUI for Java:Choose Start All Programs SAP Clients SAP GUI for Java<Release>.
NOTE
You can alternatively enter the command guilogon in the SAP GUI installation directoryto start SAP GUI for Java.
The SAP Logonappears.2. Create a logon entry for the newly installed system in theSAP Logon.
For more information about creating new logon entries, press F1 .3. When you have created the entry, log on as userSAP* or DDIC.
5.3 Configuring User Management
After the installation of your SAP system has finished, you must decide whether you want to do thefollowing:
■ Add the system to Central User Administration (CUA)■ Use Lightweight Directory Access Protocol (LDAP) synchronization
For more information, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP
NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management Identity Management for System Landscapes Integration of User Management in Your System Landscape Adding an ABAP System to Your SysLandscape
5 Post-Installation
5.3 Configuring User Management
88 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 89/142
5.4 Ensuring User Security
You need to ensure the security of the users that SAPinst created during the installation. The tablesbelow at the end of this section list these users:
■ Operating system users■ SAP system users
During the installation, SAPinst by default assigned the master password to all users created during theinstallation unless you specified other passwords.If you change user passwords, be aware that SAP system users might exist in multiple SAP system clients(for example, if a user was copiedas part of the client copy). Therefore, you need to change the passwordsin all the relevant SAP system clients.
CAUTION
SAPinst applied the master password to usersSAP* and DDIC only for SAP system clients 000 and001, but not to usersSAP* , DDIC, and EARLYWATCHin client 066.Instead, SAPinst always assigns the following passwords to these users in client 066:SAP* : 06071992EARLYWATCH: supportSee alsoMaster Password in Basic SAP System Parameters[page36].
RECOMMENDATION
User ID and password are encoded only when transported across the network. Therefore, we
recommend using encryption at the network layer, either by using the Secure Sockets Layer (SSL)protocol for HTTP connections or Secure Network Communications (SNC) for the SAP protocolsdialog and RFC.For more information, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) EnglishSAP NetWeaver Library SAP NetWeaver by Key Capability Security Network and T ransport Layer
Security
CAUTION
Make sure that you perform this procedure before the newly installed SAP system goes intoproduction. For security reasons, you also need to copy the installation directory to a separate,secure location – such as a DVD – and then delete the installation directory.
ProcedureFor the users listed below, take the precautions described in the relevant SAP security guide, which youcan find at http://service.sap.com/securityguide :
Operating System Users
After the installation, operating system users for SAP system and database are available as listed in thefollowing table:
5 Post-Installation
5.4 Ensuring User Security
2009-05-25 PUBLIC 89 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 90/142
Operating System and Database Users
User User Name Comment
Operating system user <sapsid>adm SAP system administratorora<dbsid>
Oracle database administrator (thatis, the owner of the database files)Oracle database user SAP<SCHEMA_ID> Oracle database owner (that is, the
owner of the database tables)SYSTEM Oracle standard database userSYS Oracle standard database userOUTLN Oracle standard database userDBSNMP Oracle standard database user
SAP System Users
After the installation, ABAP system users are available. The following table shows these users togetherwith recommendations on how you can ensure the security of these users.
ABAP Users
User User Name Comment
SAP system user SAP* User exists in at least SAP systemclients 000, 001, and 066
CAUTION
This user has extensiveauthorizations. Make sure
that you assign a securepassword.DDIC User exists in at least SAP system
clients 000 and 001
CAUTION
This user has extensiveauthorizations. Make surethat you assign a securepassword.
EARLYWATCH User exists in at least SAP system
client 066SAPCPIC User exists in at least SAP system
clients 000 and 001
More InformationFor more information about managing ABAP users, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library Security Identity Management User and Role Administration of AS ABAP
5 Post-Installation
5.4 Ensuring User Security
90 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 91/142
5.5 Installing the SAP License
You must install a permanent SAP license. When you install your SAP system, atemporary licenseis automatically installed. This temporary license allows you to use the system foronly 4 weeks fromthe date of installation.
CAUTION
Before the temporary license expires, you must apply for a permanent license key from SAP.We recommend that you apply for a permanent license key as soon as possible after installing yoursystem.
Procedure
Install the SAP license as described in the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP
NetWeaver Library Technology Consultant's Guide Cross-NetWeaver Configurations SAP License KeysOnly valid for: HA (UNIX) |
If you have installed a high-availability system, proceed as described inHigh Availability: Setting UpLicenses[page91].End of: HA (UNIX) |
More Information
For more information about SAP license keys, seehttp://service.sap.com/licensekey .
5.6 High Availability: Setting Up Licenses
Every SAP system needs a central license, which is determined by the environment of the messageserver. Since SAP's high-availability (HA) solution stipulates 2 or more cluster nodes (host machines)where the message server is enabled to run, you have to order as manylicense keys[page91] as you havecluster nodes.When we receive confirmation from your vendor that you are implementing a switchover
environment, we provide the required license keys for your system, 1 key for each machine.SAP has implemented a license mechanism for transparent and easy use with switchover solutions andclustered 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.
Prerequisites
The 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.
5 Post-Installation
5.5 Instal ling the SAP License
2009-05-25 PUBLIC 91 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 92/142
2. To find the hardware ID of the primary host, log on to any application server instance of the SAPsystem and call transaction SLICENSE.
3. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster
and repeat the previous step.Repeat this for all remaining nodes in the cluster.
4. To obtain the two license keys, enter the hardware IDs for the primary and backup hosts at:http://service.sap.com/licensekey
5. To import the files containing the two licenses, log on to any application server instance of theSAP system and call transaction SLICENSE.
6. Performa 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.
Result
The license is no longer a problem during switchover. This means you donot need to callsaplicense in your switchover scripts.
5.7 Applying the Latest Kernel and Support Package Stacks
We strongly recommend that you apply the latest kernel and Support Package stacks from SAP ServiceMarketplace before you start configuring your SAP system.
Prerequisites
Make sure that you read the release notes for your SAP system before you apply Support Package stacks.The releasenotes might include information about steps you have to perform after you have appliedthe Support Package stacks. For more information, seehttp://service.sap.com/releasenotes .
Procedure
Download and apply the latest kernel and Support Package stacks as described in theSAP NetWeaver 7.0
– Support Package Stack Guide <current version>at http://service.sap.com/maintenancenw70 .For up-to-date release information on Support Package stacks, seeSAP Note 849887.
5.8 Configuring Remote Connection to SAP Support
SAP offers its customers access to support and to a number of remote services such as the SAP EarlyWatchservice or the SAP GoingLive service. Therefore, you have to set up a remote network connection toSAP. For more information, see SAP Service Marketplace athttp://service.sap.com/
remoteconnection .
5 Post-Installation
5.7 Applying the Latest Kernel and Support Package Stacks
92 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 93/142
5.9 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 athttp://help.sap.com .
ProcessInstall the SAP online documentation in your SAP system as described in theREADME.TXTfile containedin the root directory of the online documentation DVD, delivered as part of the installation package.
5.10 Performing Initial ABAP Configuration
When you have installed your SAP ABAP system, you have to perform the following initialconfiguration steps:
■ Perform a consistency check■ Configure the transport management system■ Perform basic operations■ Configure system parameters■ Configure the number of work processes■ Configure kernel parameters
■ Install languages and performing language transport■ Configure the integrated Internet Transaction Server (ITS)■ Make your newly installed SAP system known to your SAP Solution Manager■ Maintain your company address for initial users■ Configure AS ABAP to support Secure Socket Layer (SSL)■ Configure Fully Qualified Domain Names (FQDN)■ Configure business applications
For more information, see the appropriate sections below.
PrerequisitesYou have logged on to the ABAP application server as described inLogging On to the Application Server [page87].
Procedure
Performing a Consistency Check
We recommend that you check the consistency of the newly installed SAP ABAP system. When loggingon to the system for the first time, you need to trigger a consistency check manually. The function isthen called automatically whenever you start the system or an application server.This checks the following:
5 Post-Installation
5.9 Installing the SAP Online Documentation
2009-05-25 PUBLIC 93 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 94/142
■ Completeness of installation■ Version compatibility between the SAP release and the operating system
The initial consistency check determines whether:● The release number in the SAP kernel matches the release number defined in the database
system● The character set specified in the SAP kernel matches the character set specified in the database
system● Critical structure definitions that are defined in both the data dictionary and the SAP kernel
are identical. The structures checked by this function include SYST, T100, TSTC, TDCT, andTFDIR.
■ Accessibility of the message server■ Availability of all work process types■ Information about the enqueue server and the update service
To perform a consistency check, you can either call transaction SICK (SAP initial consistency check)or choose Tools Administration Administration Installation Checkfrom the menu.For more information, see the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SystemManagement Tools for Monitoring the System Consistency Check
Configuring the Transport Management System
You have to perform some steps to be able to use the Transport Management System.1. Perform post-installation steps for the transport organizer:
1. Call transaction SE06 .2. SelectStandard Installation.3. ChoosePerform Post-Installation Actions.
2. Call transaction STMS in the ABAP system to configure the domain controller in the TransportManagement System (TMS).
3. Only valid for: HA (UNIX) |
In TPPARAM, set<SAPSID>/dbhost to the virtual host name of the DB instance.This lets you use the transport system for the normal maintenance of ABAP programs, but stillallows transparent operation in the event of a switchover in your high-availability system.End of: HA (UNIX) |
For more information, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SoftwareLife Cycle Management Software Logistics Change and Transport System
5 Post-Installation
5.10 Performing Initial ABAP Configuration
94 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 95/142
Performing Basic Operations
1. Go to the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English
SAP NetWeaver Library SAP NetWeaver by Key Capability2. Choose the relevant sections to perform the following operations:
Operation Section in SAP Documentation
Set up operation modes – transaction RZ04
Solution Life Cycle Management by Key Capability System Management ConfiguratOperation Modes
Set up logon groups – transaction SMLG
Solution Life Cycle Management by Key Capability System Management ConfiguratLogon Load Balancing SAP Logon
Set up administrators Solution Life Cycle Management by Key Capability System Management BackgrouProcessing Authorizations for Background Processing
Schedule background jobs Solution Life Cycle Management by Key Capability System Management BackgrouProcessing
Install a printer Solution Life Cycle Management by Key Capability System Management SAP PrintiGuide
Configure the system log Solution Life Cycle Management by Key Capability System Management Tools forMonitoring the System System log Configuring the System Log
Configuring System Parameters
For more information about system profiles, which is where work processes and profile parameters aredefined, and how to configure them, see the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilityManagement Tools for Monitoring the System Configuration Profiles
Checking the Configured Number of Work Processes
SAPinst installs ABAP systems with a minimum number of work processes. This is only an initialconfiguration so that you can start working after the installation. It is not detailed enough for aproduction system because the optimal number of each type of work process depends on the systemresources and on the number of users working in each ABAP system application.
For more information about how many work processes to configure and about how to set the number,seeSAP Notes 39412and 9942.
Configuring Kernel Parameters
To configure your kernel parameters, follow the recommendations in SAP Notes 146289and 835474.
Installing Languages and Performing Language Transports
■ Install languages using transaction I18N:● If you want to use English only, you must activate the default language settings once.
5 Post-Installation
5.10 Performing Initial ABAP Configuration
2009-05-25 PUBLIC 95 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 96/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 97/142
Configuring AS ABAP to Support Secure Socket Layer (SSL)
If you installed the SAP Cryptographic Library – seeBasic SAP System Parameters[page36] – you have toconfigure AS ABAP to support Secure Socket Layer (SSL), as described in the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security System Security System Security for SAAS ABAP Only Trust Manager Example Configuring the SAP Web AS for Supporting SSL
Configuring Fully Qualified Domain Names (FQDN)
If want to use Web Dynpro ABAP as UI technology and you assigned a DNS Domain Name to your SAPSystem – seeBasic SAP System Parameters[page36]– you have to perform the required configuration steps.For more information, seeSAP Note 654982and the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeave
Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology UTechnology Web UI Technology Web Dynpro ABAP Web Dynpro ABAP Configuration Fully Qualified DomainNames (FQDN)
Configuring Business Applications
Prepare the SAP system for using business applications, which includes customizing the ABAP systemand the business components, as described in the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability
Customizing
5.11 Performing Oracle-Specific Post-Installation Steps
You have to perform the following Oracle-specific post-installation steps:
Procedure
Security Setup for the Oracle Listener
If the Oracle security setup defined by the standard installation is not restrictive enough for yourpurposes, seeSAP Note 186119to configure the Oracle listener to accept only connections from specifichosts.
Checking the Recommended Oracle Database Param eters
When 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 inSAP Note 830576.You can find an automated script in SAP Note 1171650to help you check whether your SAP systemcomplies with the database parameter recommendations at any given point in time.
5 Post-Installation
5.11 Performing Oracle-Specific Post-Installation Steps
2009-05-25 PUBLIC 97 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 98/142
Updating Oracle Optimizer Statistics
To update the Oracle optimizer statistics, perform the following:1. Execute the following commands as theora<dbsid> user:
brconnect -u / -c -f stats -t system_stats;
brconnect -u / -c -f stats -t oradict_stats;
2. Executethe following commands with SQLPlus:SQL> exec dbms_scheduler.disable('GATHER_STATS_JOB');
SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB');
SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');
Checking the Version of the Oracle Instant Client
If necessary, install the most up-to-date version of the Oracle Instant Client, as described in SAP Note
819829.
Enabling Database Monitoring
Follow the instructions in SAP Note 706927to enable database monitoring in the DBA Cockpit.
Configuring and Operating the Oracle Database
You have to configure your Oracle database before youstart operating it with the SAP system.For information about Oracle database configuration and administration, see the documentation inthe SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package
1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key CapabilityPlatform-Wide Services Database Support Oracle.
5.12 Configuring the Connection to a Central SystemLandscape Directory
For each system in your landscape that reports data to a central System Landscape Directory (SLD),you have to configure a corresponding SLD data supplier.
Procedure
Configure the SLDdata suppliers and the API for the SLD as described in the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SoftwareLife Cycle Management System Landscape Directory Configuring Systems to Connect to SLD
More Information
This documentation is also available in PDF form in theUser Manual – SLD of SAP NetWeaver 7.0 at http://
www.sdn.sap.com/irj/sdn/nw-sld .
5 Post-Installation
5.12 Configuring the Connection to a Central System Landscape Directory
98 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 99/142
5.13 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 athttps://service.sap.com/erp-inst SAP ERP 6.0 SAP Notes.
5.14 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.
Procedure1. Maintain the new client with transaction SCC4.2. Activate kernel userSAP* :
1. Set the profile parameterlogin/no_automatic_user_sapstar to 0 .2. Restart the application server.
3. Log on to the new client with kernel userSAP* and password PASS .4. Copy the client with transaction SCCL and profile SAP_CUST.
5. Check the log files with transactionSCC3.6. Create the required users. These users must have at least the authorizations required for user
administration and system administration. Create a user SAP* with all required authorizations forthis user. If you want to have other users for system administration, you can also create userSAP* without authorizations.
7. Deactivate kernel userSAP* :1. Resetlogin/no_automatic_user_sapstar to 1 .2. Restart the application server.
More InformationFor more information about the client copy and about how to perform it, see the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilityLifecycle Management Software Logistics Change and Transport System BC – Client Copy and Transport
5.15 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.
5 Post-Installation
5.13 Implementing ERP ABAP Add-On Components
2009-05-25 PUBLIC 99 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 100/142
C AUTION
Make sure that you fully back up your database so that you can recover it later if necessary.
Prerequisites■ If required, you have completed client maintenance, such as theclient copy[page99].■ You have logged on[page87] as user<sapsid>adm and stopped the SAP system and database[page126].
Procedure
The 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:■ /usr/sap/<SAPSID>
■ /usr/sap/trans
■ <sapmnt>/<SAPSID>
■ Home directory of the user <sapsid>adm
■ All database-specific directoriesProceed as follows:1. Log on as userroot .2. Manually create a compressedtar archive that contains all installed files:
■ Saving to tape:tar —cf — <file_system> | compress —c > <tape_device>
■ Saving to the file system:tar —cf — <file_system> | compress —c > ARCHIVENAME.tar.Z
2. Back up the operating system using operating system means.This saves the structure of the system and all configuration files, such as file system size, logical
volume manager configuration and database configuration data.
Restoring Your Backup
If required, you can restore the data that you previously backed up.
C AUTION
Check for modifications to the existing parameter files before you overwrite them when restoringthe backup.
1. Log on as userroot .2. Go to the location in your file system where you want to restore the backup image.
5 Post-Installation
5.15 Performing a Full Installation Backup
100 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 101/142
3. Execute the following commands to restore the data:■ Restoring the data from tape:
cat <tape_device> | compress —cd | tar —xf —
■ Restoring the data from the file system:cat ARCHIVENAME.tar.Z | compress —cd | tar —xf —
Performing a Full Database Backup
1. Configure your third-party backup tool, if used.2. Perform a full database backup (preferably offline).
If you use BR*TOOLS for the backup, refer toBR*Tools for Oracle DBAin the SAP Database Guide: Oracle(BC-DB-ORA-DBA). This documentation is available in the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) EnglishSAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key CapabilityPlatform-Wide Services Database Support Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA)
5.16 Accessing Configuration Documentation in SAP SolutionManager
To access configuration documentation in SAP Solution Manager, you have to connect your newlyinstalled SAP system to SAP Solution Manager.
NOTE
For SAP NetWeaver 7.0 usage types you can also find configuration documentation in theTechnologyConsultant's Guideat:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) EnglishSAP NetWeaver LibraryTechnology Consultant's Guide
Prerequisites■ You have installed an SAP Solution Manager system as described in the documentationInstallation
Guide – SAP Solution Manager <Current Release> on <OS>: <Database>.■ You have connected your SAP system to SAP Solution Manager as described in the documentation
Configuration 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 <Current Release>
Procedure
1. Log on to your SAP Solution Manager system.2. To be able to access configuration documentation, create a project as follows:
1. Create your project with transaction SOLAR_PROJECT_ADMINfor project administration.
5 Post-Installation
5.16 Accessing Configuration Documentation in SAP Solution Manager
2009-05-25 PUBLIC 101 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 102/142
2. Connect your SAP system to SAP Solution Manager with transactionSMSYfor the SAP SolutionManager system landscape.
3. Create a project structure and add the required scenarios for your SAP system to your project
structure with the Business Blueprint transaction SOLAR01,4. Add your SAP system configuration structures to your project structure with the
configuration transaction SOLAR02.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 atConfiguration Structure SAP ERP
<release> .
Here you can also find documentation about how to use the Extended Configuration Management(XCM) Administration Tool.
ResultYou can now configure your SAP system according to the configuration documentation in SAPSolution Manager.
More Information■ http://service.sap.com/solutionmanager Media Library Technical Papers How to Create a
Configuration Guide using SAP Solution Manager ■ http://help.sap.com SAP Solutions SAP Solution Manager Documentation for SAP Solution Manager
<current release> SAP Solution Manager Implementing and Upgrading SAP Solutions ProjectsConfiguration
5 Post-Installation
5.16 Accessing Configuration Documentation in SAP Solution Manager
102 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 103/142
6 Additional Information
The following sections provide additional information aboutoptional preparation, installation, andpost-installation tasks.There is also a section describing how to delete an SAP system.
Preparation
■ Installation of Multiple Components in One Database[page103]
■ Integration of LDAP Directory Services[page105]■ Setting up Swap Space for Solaris[page109]■ Creating Solaris Groups and Users[page109]■ Setting up File Systems and Raw Devices for Solaris[page111]■ Dialog Instance Installation for an Upgraded System: Updatin g Instance Profiles[page112]■ Mounting a CD / DVD for Solaris[page113].■ Exporting and Mounting Directories via NFS for Solaris[page114]
Post-Installation
■ Starting and stopping theSAP system[page122]■ If you decided to use a generic LDAP directory, you have tocreate a user for LDAP directory access[page
128]■ Heterogeneous SAP System Installation[page129]■ Troubleshooting[page129]
Deleting an SAP System or SAP Instance
■ Deleting an SAP System[page130]
6.1 Installation of Multiple Compo ne nts in One Database
You can install multiple SAP systems in asingle database. Thisis called Multiple Components in OneDatabase (MCOD).
EXAM P LE
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 major databasesfor the SAP system, in line with our commitment to deliver platform-independent solutions.
6 Additional Information
6.1 Installation of Multiple Components in One Database
2009-05-25 PUBLIC 103 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 104/142
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 option. Instead, it is an option of the database instance installation.
With MCOD we distinguish two scenarios:■ The installation of an SAP system in a new database■ The installation of an additional SAP system in an existing database
Prerequisites■ For more information about MCOD and its availability on different platforms, seehttp://
www.sdn.sap.com/irj/sdn/dbos .■ We have released MCOD for Unicode installations. A prerequisite is that the MCOD system contains
Unicode instances only. SAP does not support mixed solutions.■ Improved sizing required
In general, you calculate the CPU usage for an MCOD database by adding up the CPU usage foreach individual SAP system. You can do the same for memory resources and disk space.You can size multiple components in one database by sizing each individual component using theQuick Sizer tool and then adding the requirements together. For more information about theQuick Sizer , seehttp://service.sap.com/sizing .
Features■ Reduced administration effort■ Consistent system landscape for backup, system copy, administration, and recovery■ Increased security and reduced database failure for multiple SAP systems due to monitoring and
administration of only one database■ Independent upgrade
In an MCOD landscape, you can upgrade a single component independently from the othercomponents running in the s ame database, assuming that the upgraded component runs on thesame database version. However, if you need to restore a backup, be aware that all other componentsare also affected.
NOTE
Special MCOD considerations and differences from the standard procedure are listed whererelevant in the installation documentation.
Constraints
RECOMMENDATION
We strongly recommend that you test MCOD in a test or development system.We recommend that you run MCOD systems in the same context. We do not recommend thatyou mix test, development, and production systems in the same MCOD.
6 Additional Information
6.1 Installation of Multiple Components in One Database
104 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 105/142
■ In the event of database failure, all SAP systems running on the single database are affected.■ Automated support in an MCOD landscape for the following administrative tasks depends on your
operating system and database:● Copying a single component from an MCOD landscape to another database at database level.● Uninstalling 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 .
■ 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 withstopsap R3 to make sure thatthe database is also stopped.
■ You cannot install a Unicode ABAP system with a non-Unicode ABAP system in one database.■ For the second SAP system, you must use the sameDBSID as for the first SAP system.■ If you install a system into an existing database (MCOD), the SYSTEM tablespace must contain at
least 400 MB of free space. If there is not enough space left, increase the size of this tablespace withBRSPACE or BRTOOLS.
■ 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.
More Information■ SAP Note 669902: Setting the national character set to UTF8■
SAP Note 975768: Deprecation of Java features with non-Unicode Backend■ SAP Note 838402: Problems within non-Unicode system landscapes
6.2 Integration of LD AP D irectory Services
This section explains the benefits of using the SAP system with the Lightweight Directory AccessProtocol (LDAP) directory and gives an overview of the configuration steps required to use an SAPsystem with the directory.LDAP defines a standard protocol for accessing directory services, which is supported by variousdirectory products such as Microsoft Active Directory, andOpenLDAP slapd . Using directory servicesenables important information in a corporate network to be stored centrally on a server. The advantageof storing information centrally for the entire network is that you only have to maintain data once,which avoids redundancy and inconsistency.If an LDAP directory is available in your corporate network, you can configure the SAP system to usethis feature. For example, a correctly configured SAP system can read information from the directoryand also store information there.
NOTE
The SAP system can interact with the Active Directory using the LDAP protocol, which defines:
6 Additional Information
6.2 Integration of LDAP Directory Services
2009-05-25 PUBLIC 105 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 106/142
■ The communication protocol between the SAP system and the directory■ How data in the directory is structured, accessed, or modified
If a directory other than the Active Directory also supports the LDAP protocol, the SAP system
can take advantage of the information stored there. For example, if there is an LDAP directory ona UNIX or Windows server, you can configure the SAP system to use the information availablethere. In the following text, directories other than the Active Directory that implement the LDAPprotocol are called generic LDAP directories .
C AUTION
This section doesnot 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 (including
Enhancement Package 1) English SAP NetW eaver Library SAP NetWeaver by Key Capability SecurityIdentityManagement User and Role Administration of AS ABAP Configuration of User and Role
Administration Directory Services LDAP Connector
PrerequisitesYou can only configure the SAP system for Active Directory services or other LDAP directories if theseare already available on the network. As of Windows 2000 or higher, the Active Directory isautomatically available on all domain controllers. A generic LDAP directory is an additional componentthat 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:
■ SAP Logon■ The SAP Microsoft Management Console (SAP MMC)■ 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 documentationSAP System Information in
Directory Servicesathttps://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/ d0a0d051-
eae2-2b10-e1ac-f3a7f6494c53
For more information about the SAP MC and about how to configure it to access LDAP Directories,see the documentation SAP Management Consoleat http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability
Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE EngineAdministration Tools SAP Management Console
6 Additional Information
6.2 Integration of LDAP Directory Services
106 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 107/142
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. If you
configure SAP logon to use the LDAP directory, it queries the directory each timeServer or Groupselectionis chosen to fetch up-to-date information on available SAP systems.To use LDAP operation mode, make sure that thesapmsg.ini file contains the following:[Address]
Mode=LDAPdirectory
LDAPserver=
LDAPnode=
LDAPoptions=
Distinguish the following cases:■ If you use an Active Directory, you must setLDAPoptions=“DirType=NT5ADS” . For more
information, see the SAP system profile parameterldap/options .■ You must specify the directory servers (for example,LDAPserver=pcintel6 p24709 ) if either of
the following is true:● The client is not located in the same domain forest as the Active Directory● The operating system does not have a directory service client (Windows NT and Windows 9X
without installed dsclient ).For more information, see the SAP system profile parameterldap/servers .
■ For other directory services, you can useLDAPnodeto specify the distinguished name of the SAProot node. For more information, see the SAP system profile parameterldap/saproot .
SAP MMC
The SAP MMC is a graphical user interface (GUI) for administering and monitoring 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 that itgathers from various sources, including the Active Directory.Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can
read system information straight from the directory that automatically registers changes to the systemlandscape. As a result, up-to-date information about all SAP application servers, their status, andparameter settings is always available in the SAP MMC.If you need to administer distributed systems, we especially recommend that you use the SAP MMCtogether with Active Directory services. You can keep track of significant events in all of the systemsfrom a single SAP MMC interface. You do not need to manually register changes in the systemconfiguration. Instead, such changes are automatically updated in the directory and subsequentlyreflected in the SAP MMC.
6 Additional Information
6.2 Integration of LDAP Directory Services
2009-05-25 PUBLIC 107 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 108/142
If your SAP system is part of a heterogeneous SAP system landscape that comprises systems or instancesboth on UNIX and Windows operating systems, 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. It canread system information straight from the directory that automatically registers changes to the systemlandscape. As a result, up-to-date information about all SAP application servers, their status, andparameter 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:
■ Extend the Active Directory schema to include the SAP-specific data types■ Create the domain accounts required to enable the SAP system to access and modify the Active
Directory. These are the group SAP_LDAP and the user sapldap .■ Create the root container where information related to SAP is stored■ Control access to the container for SAP data by giving members of theSAP_LDAP group permission
to read and write to the directoryYou do this by running SAPinst on the Windows server on which you want to use Active DirectoryServices and choosing <Your SAP product> Software Life-Cycle Options LDAP Registration ActiveDirectory Configuration. For more information about running SAPinst on Windows, see the
documentation Installation Guide — <Your SAP product> on Windows: <Database>.NOTE
You have to perform the directory server configuration only once . Then all SAP systems thatneed to register in this directory server can use this setup.
Configuration Tasks for Generic LDAP Directories
To configure other LDAP directories, refer to the documentation of your directory vendor.
Enabling the SAP System LDAP Registration
Once you have correctly configured your directory server, you can enable the LDAP registration of theSAP system by setting some profile parameters in the default profile.
6 Additional Information
6.2 Integration of LDAP Directory Services
108 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 109/142
To do this, run SAPinstonce for your system and choose <Your SAP product> Software Life-Cycle OptionsLDAP Registration LDAP Support
If you use a directory server other than Microsoft Active Directory and/or non-Windows application
servers, you have to store the directory user and password information by usingldappasswd
pf=<any_instance_profile> . The information is encrypted for storage inDIR_GLOBALand is thereforevalid for all application servers. After restarting all application servers and start services, the system isregistered in your directory server. The registration protocols of the components are dev_ldap* . Theregistration is updated every time a component starts.
6.3 Setting up Swap Space for SolarisProcedure1. Check if there is sufficient swap space (seeHardware and Software Requirements[page19]).
To check the allocated swap space, enter the following command:swap -s
2. If required, increase swap space as described in the System Administrator Collection:■ Solaris 9: See theSolaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/
docs/prod/solaris.9
■ Solaris 10: See theSolaris 10 <Release> System Administrator Collectionat:http://docs.s un .com/
app/docs/prod/solaris.10
3. Check paging space size and kernel settings as follows:NOTE
If you are installing astandalone database server donot perform this step.■ Make sure that the UNIX kernel, paging space, and user limits are already configured for the
SAP system as described inHardware and Software Requirements[page19].■ Executememlimits to verify paging space size and kernel settings as follows:
1. To unpack the filememlimits , enter the following commands:<DVD-DIR>/<Kernel DVD>/<DATA_UNITS>/<Kernel Version>_<Solaris Product>/
DBINDEP/SAPCAR –xvfg <DVD-DIR>/<Kernel DVD>/<DATA_UNITS>/<KernelVersion>_<Solaris Product>/DBINDEP/SAPEXE.SAR memlimits
2. Start memlimits as follows:./memlimits -l 20000
If you see error messages, increase the paging space and rerunmemlimi ts until there areno more errors.
6.4 Creating Solaris Groups and Users
You can create groups and users manually by using the shell commandsuseradd and groupadd .
6 Additional Information
6.3 Setting up Swap Space for Solaris
2009-05-25 PUBLIC 109 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 110/142
Procedure1. To add new groups and users, use the commandsgroupadd and useradd as follows:
groupadd <new group>
useradd –g <login group> -d <homedirectory> \-s <login shell> <new user>
2. Check the following values for the users:■ In csh , execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
■ 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
3. If your parameter settings differ from the settings above, change these values accordingly.EXAM P LE
If you have to change the value for descriptors to8192 , proceed as follows:1. Add the following line to the.cshrc file after the line containingcase Sun* :
limit descriptors 8192
2. Add the following line to the.profile file after the line containingSun*) :ulimit -n 8192
More Information
For more information about the users and groups that are created either by SAPinst or manually, seeCreating Operating System Users[page47].
6 Additional Information
6.4 Creating Solaris Groups and Users
110 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 111/142
6.5 Setting up File Systems and Raw Devices for SolarisProcedure
Creating File Systems on Hard Disk Partitions
NOTE
To set up file systems larger than 2 GB, no special steps are required on Solaris.
1. Look for already configured and mounted file systems using the command:df -k
2. Look for the physical available disks and partitions using theformat or/usr/sbin/prtvtoc <rawdevice> utility.
3. Verify that the partition is unused.4. Create new file systems using the commandnewfs :
■ Oracle (sapdata file systems):newfs -i 20000 -m 1 -b 8192 -f 8192 <rawdevice>
■ Standard SAP file systems:newfs <rawdevice>
EXAM P LE
newfs /dev/rdsk/<diskdevice>
The disk naming convention is based on logical (not physical) device names.● Solaris 9: For more information about the appropriate disk naming convention, see
the Solaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/
docs/prod/solaris .9
● Solaris 10: For more information about the appropriate disk naming convention,see theSolaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/
docs/prod/solaris.10
Mounting File Systems
Create directories (mkdir ) and mount the file systems using the command:mount <blockdevice> <mountdir>
To make the file systems available automatically each time the system boots, add an entry to the/etc/
vfstab file as follows:/dev/dsk/<diskdevice> /dev/rdsk/<diskdevice>/<mountdir> ufs <fsck pass#> yes —
where <fsck pass#> is a number greater than 6If you use Solaris Volume Manager, for example Solstice DiskSuite, see the appropriate productdocumentation:
■ Solaris 9: See theSolaris 9 <Release> System Administrator Collectionat:http://docs.sun.com/app/
docs/prod/solaris.9
6 Additional Information
6.5 Setting up File Systems and Raw Devices for Solaris
2009-05-25 PUBLIC 111 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 112/142
■ Solaris 10: See theSolaris 10 <Release> System Administrator Collectionat:http://docs.sun.com/app/
docs/prod/solaris.10
Accessing Raw Devices on SolarisFile systems and raw devices differ in the way that data is written to and read from disk:
■ Buffering : Reads and writes to a file system are buffered in a UNIX system. To be absolutely surethat all data is physically present on a disk, the buffers and files must be synchronized.Unbuffered : Writes to a raw device are sent directly to the disk, which is faster and more secure.
■ File access : Accessing files on a UNIX file system is transparent. Accessing data on a raw device isonly possible with a special application.
Some databases prefer raw devices.For Oracle it is not necessary to create symbolic links to access these raw devices.
6.6 Dialog Instance Installation for an Upgraded System only:Updating Profiles
You only need to perform the Procedurefurther below if you want to install a dialog instance and youhave already performed the following steps:1. You upgraded your SAP system from an earlier source release to a target releaselower than SAP
ERP 6.0 SR3.
2. You installed Enhancement Package 4 with the SAP Enhancement Package Installer.Procedure1. On the SAP Global host, go to folder/<sapmnt>/<SAPSID>/profile .
NOTE
SAP system profiles are named as follows:Instance profiles:<SAPSID>_<INSTANCE_ID>_<hostname>.pfl
Start profiles:START_<INSTANCE_ID>_<hostname>.pfl
2. Make sure that the parameter DIR_CT_RUN, if set, has identical values in the instance profile and
the start profile of the central instance:■ If itis set in the instance profile, it mustalso be set in the start profile.■ If it isnot set in the instance profile, it mustnot be set in the start profile either.
3. Edit the default profileDEFAULT.PFL by setting rdisp/msserv_internal to a free port number.EXAM P LE
DEFAULT.PFL
Before the change:...rdisp/msserv = sapms<SAPSID>
...
6 Additional Information
6.6 Dialog Instance Installation for an Upgraded System only: Updating Profiles
112 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 113/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 114/142
2. To check if vold (volume daemon) is running, enter the following command:ps -ef | grep vold
3. If it is running, killvold .
4. Insert the CD / DVD into your disk drive.5. To create a mount point, enter the following command:
mkdir /<medium-mountdir>
EXAM P LE
for example,<medium-mountdir> is /sapcd
6. To mount the CD / DVD, enter the following command:mount -F hsfs -o nomaplcase,ro /dev/dsk/c0t6d0s2 /<medium-mountdir>
After the installation, you can start vold using the following command:/usr/sbin/vold
.
6.8 Exporting and Mounting Directories via NFS for SolarisProcedure
To mount directories via NFS from the host where the directory resides that you want to mount, logon as user root and proceed as follows:
On the host on which the directory to be mounted resides:
1. Enter the command:/usr/sbin/share
2. To add file systems shared via NFS, edit file/etc/dfs/dfstab :vi /etc/dfs/dfstab
Add the following line for each file system:share -F nfs -o root=<nfsclient1>:<nfsclient2>,anon=0 \
-d "description" <file_system_to_be_shared>
NOTE
Depending on your configuration, a full qualified name may be required fornfsclient , forexample, myclient.mydomain.com .CAUTION
After your SAP system has been installed successfully, in the above line you have to change-o root to -o rw (or remove anon=0 , respectively) for all exported directories:share -F nfs -o rw=<nfsclient1>:<nfsclient2> \
-d "description" <file_system_to_be_shared>
3. If the/etc/dfs/dfstab was empty, the NFS server is not active.■ On Solaris 9, start the NFS server with the following command:
/etc/init.d/nfs.server start
6 Additional Information
6.8 Exporting and Mounting Directories via NFS for Solaris
114 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 115/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 116/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 117/142
Option Definition
Retry SAPinst retries the installation from the point of failure without repeatingany of the previous steps.This is possible because SAPinst records the installation progress in thekeydb.xml file.We recommend that you view the entries in the log files, try to solve theproblem, and then choose Retry.If the same or a different error occurs, SAPinst displays the same dialog boxagain.
Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, andthe GUI server.SAPinst records the installation progress in thekeydb.xml file. Therefore, youcan continue the installation from the point of failure without repeating anyof the previous steps (see the procedure below).
Continue SAPinst continues the installation from the current point.View Log Access installation log files.
NOTE
You can also terminate SAPinst by choosing Ctrl + C . However, we donot recommend thatyou use Ctrl + C , because this kills the process immediately.
Procedure
This procedure describes the steps to restart an installation, which you stopped by choosingStop, or to
continue an interrupted installation after an error situation.1. Log on to your local UNIX host as userroot .CAUTION
Make sure that the root user has not set any environment variables for a different SAP systemor database.
2. Mount your Installation Master DVD.NOTE
Mount the DVD locally. We do not recommend using Network File System (NFS).3. Start SAPinst using the following commands:
cd <Installation_Master_DVD>/IM_<OS>
./sapinst
4. From the tree structure in the Welcomescreen, select the installation service that you want tocontinue and choose Next .
NOTE
If there is only 1 component to install, theWelcomescreen does not appear.
The What Do You Want to Do?screen appears.5. In the What Do You Want to Do?screen, decide between the following alternatives and confirm with
OK :
6 Additional Information
6.9 Additional Information About SAPinst
2009-05-25 PUBLIC 117 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 118/142
Alternative Behavior
Run a New Option SAPinst does not continue the interrupted installation option. Instead, itmoves the content of the old installation directory and all installation-specific files to a backup directory. Afterwards, you can no longer continuethe old installation option.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds> .
EXAM P LE
log_01_Oct_2008_13_47_56
CAUTION
SAPinst moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are anyprocesses currently running on these files and folders, they might no
longer function properly.Continue with the Old Option SAPinst continues the interrupted installation option from the point of
failure.
6.9.3 Performing a Remote Installation with SAPinst
You use this procedure to install your SAP system on aremote host. In this case, SAPinst and the GUIserver run on the remote host, and SAPinst GUI runs on thelocal host. The local host is the host from
which you control the installation with SAPinst GUI.Alternatively you can use an X server for Microsoft Windows or other remote desktop tools such asVNC Viewer or NX Server / NX Client – offered by various vendors or open source – for remote accessto SAPinst GUI on Windows workstations. We recommend you use the Hummingbird Exceed X Server,which we use to validate installations with SAPinst. For more information, see SAP Note1170809.
C AUTION
The behavior of SAPinst has changed compared to previous versions. SAP no longer delivers any JCE policy archives within the SAP Java Virtual Machine (SAP JVM). You have to download the
required Java Cryptography Extension (JCE) policy zip file from SAP on the remote host. For moreinformation, see SAP Note 1238121.
Prerequisites■ The remote host meets the prerequisites as described inPrerequisitesin Running SAPinst [page73].■ Both computers are in the same network and can ping each other.
To test this:1. Log on to your remote host and enter the command ping <local host> .2. Log on to the local host and enter the command ping <remote host> .
6 Additional Information
6.9 Additional Information About SAPinst
118 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 119/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 120/142
Procedure
Starting SAPinst GUI on Windows
1. Log on as a member of the local administrators group.2. Download the JCE policy zip file from SAP as described inSAP Note 1240081.3. Set the environment variableJCE_POLICY_ZIP to the location of the downloaded policy zip archive
by entering the following command:set JCE_POLICY_ZIP=<policy zip archive>
4. Insert the SAP Installation Master DVD into your DVD drive.5. Change to the directory of the sapinst executables:
<DVD drive>:\IM_WINDOWS_<platform>
NOTE
If you want to start SAPinst GUI on a Windows 32-bit operating system, change to the followingdirectory:<Installation_Master_DVD>\IM_WINDOWS_I386
6. Start SAPinst GUI by double-clickingsapinstgui.exe
SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host asdefault.If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and theSAP Installation GUI Connectiondialog appears.In this case, enter the name of the host on which SAPinst is running and chooseLog on.The first dialog of the installation appears and you can perform the remote installation from yourlocal host.
NOTE
Optionally you can start sapinstgui.exe with the following parameters:■ host=<host name> , where <host name> is the host name of the installation host■ port=<nr> , where <nr> is the port number for the connection to the GUI server■ -accessible enables accessibility mode
Example:sapinstgui host=lsi1209 port=3000 -accessible
■ -h displays a list of all available parameters
Starting SAPinst GUI on UNIX
1. Log on as userroot .CAUTION
Make sure that the root user has not set any environment variables for a different SAP systemor database.
2. Download the JCE policy zip file from SAP as described inSAP Note 1240081.3. Set the environment variableJCE_POLICY_ZIP to the location of the downloaded policy zip archive
as follows:
6 Additional Information
6.9 Additional Information About SAPinst
120 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 121/142
Shell Used Command
Bourne shell (sh) JCE_POLICY_ZIP=<policy zip archive>
export JCE_POLICY_ZIP
C shell (csh) setenv JCE_POLICY_ZIP <policy zip archive>
Korn shell (ksh) export JCE_POLICY_ZIP=<policy zip archive>
4. Mount your Installation Master DVD.NOTE
Mount the DVD locally. We donot recommend that you use Network File System (NFS).5. Change to the directory of the sapinst executables:
<mountpoint_of_Installation_Master_DVD>/IM_<OS>
NOTE
If you want to start SAPinst GUI on a Linux 32–bit platform, change to the following directory:<mountpoint_of_Installation_Master_DVD>/IM_LINUX_I386
6. Start SAPinst GUI by executing./sapinstgui
SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host asdefault.If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and theSAP Installation GUI Connectiondialog appears.In this case, enter the name of the host on which SAPinst is running and chooseLog on.The first dialog of the installation appears and you can perform the remote installation from yourlocal host.
NOTE
Optionally, you can start sapinstgui with the following parameters:■ host=<host name> , where <host name> is the host name of the installation host■ port=<nr> , where <nr> is the port number for the connection to the GUI server■ -accessible enables accessibility mode
Example:./sapinstgui host=lsi1209 port=3000 -accessible
■ -h displays a list of all available parameters
6.9.5 Entries in the Services File Created by SAPinst
After the installation has finished successfully, SAPinst has created the following entries in/etc/
services :sapdpXX = 32XX/tcp
sapdpXXs = 47XX/tcp
sapgwXX = 33XX/tcp
sapgwXXs = 48XX/tcp
sapms<SAPSID> = 36NN/tcp (unless you specified another value during the installation)
6 Additional Information
6.9 Additional Information About SAPinst
2009-05-25 PUBLIC 121 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 122/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 123/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 124/142
2. Only valid for: HA (UNIX) |
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 instancesD<Instance_Number> , if there are any.
Stopping SAP Systems or Instances
1. Select the system or instance you want to stop and chooseStopfrom the context menu.2. In the Stop SAP System(s)dialog box, choose the required options.3. ChooseOK .
The SAP MC stops the specified system or system instances.NOTE
The system might prompt you for the SAP system administrator credentials. To completethe operation, you must have administration permissions. Log in as user<sapsid>adm .
Similarly, you can start, stop, or restart all SAP systems and individual instances registered in the SAPMC.
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 start adistributed or a high-availability system – proceed as follows:1. Stop dialog instancesD<Instance_Number> , if there are any.2. Stop the central instanceDVEBMGS<Instance_Number> .3. Only valid for: HA (UNIX) |
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 Console
You can extend the list of systems and instances displayed in the SAP MC, so that you can monitor and
administer all systems and instances from a single console. You can configure the SAP MC startup viewto display the set of systems and instances you want to manage.
Prerequisites
The SAP MC is started.
Registering SAP Systems or Instances
1. In the SAP MC, choose File New .2. In the New Systemdialog box, enter the required data.
6 Additional Information
6.10 Starting and Stopping SAP System Instances
124 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 125/142
NOTE
If you have already registered systems in the SAP MC, they are stored in the history. To openthe System’s Historydialog box, choose the browsing button next to the Instance Nr.field. Select
an instance of the system that you want to add and choose OK .3. ChooseFinish.
Registering the Instances of a Distributed SAP System Separately
1. In the SAP MC, choose File New .2. In the New Systemdialog box, enter the required data and deselectAlways 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
■ You can choose the instances that the SAP MC displays automatically on startup:1. In the Settingsdialog box, selectHistory.2. In the right-hand pane, choose the instance you want the SAP MC to display on startup.3. Choose the << button.4. ChooseApplyand then OK .
Similarly, you can remove instances from the startup configuration.■ You can save the current configuration in a file:
1. Choose File Save Landscape.2. In the Save dialogbox, enter the required data.3. ChooseSave.
■ You can load a configuration from a file:1. Choose File Load Landscape.2. In the Opendialog box, select the configuration you want to load.3. ChooseOpen.
More InformationFor more information about the SAP Management Console, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilityMonitoring Monitoring in the CCMS SAP Management Console
6 Additional Information
6.10 Starting and Stopping SAP System Instances
2009-05-25 PUBLIC 125 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 126/142
6.10.2 Starting and Stopping SAP System Instances UsingScripts
You can start and stop SAP system instances by running thestartsap and stopsap scripts.You can also use the SAP Management Console (SAP MC) to start or stop the instances of the SAPsystem (seeStarting and Stopping SAP System Instances Using the SAP Management Console[page122]).
Prerequisites■ You have checked the default profile/<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameter
login/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.
■ You have checked the settings for Java Virtual Machine parameters as described inSAP Note723909.
■ You have logged on to the SAP system hosts as user<sapsid>adm .■ 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.■ If you want to usestartsap or stopsap (for example, in a script) and require the fully qualified
name of these SAP scripts, create a link tostartsap 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 dialog
instance – you must add an extra parameter to the scripts:startsap <instanceID>
stopsap <instanceID>
For example, enter:NOTE
The instance name (instance ID) of the central instance isDVEBMGS<Instance_Number> , theinstance name of a dialog instance isD<Instance_Number> .Only valid for: HA (UNIX) |
The instance name of the ABAP central services instance isASCS<Instance_Number> .End of: HA (UNIX) |
Procedure
Starting SAP S ystem Instances
■ 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
6 Additional Information
6.10 Starting and Stopping SAP System Instances
126 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 127/142
Only valid for: HA (UNIX) |
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.
■ In a distributed system , proceed as follows:1. On the database host, enter:
startdb
2. Only valid for: non-HA |
On the central instance host enter:End of: non-HA |Only valid for: HA (UNIX) |
On the central services and on the central instance host, enter:End of: HA (UNIX) |
startsap
3. For dialog instances, enter the following on the relevant host:startsap R3 <instance ID of dialog instance>
NOTE
Make sure that the SAP system is up and running before you start or restart dialog instances.
Stopping SAP System Instances
NOTE
When you use stopsap in a system with Multiple Components in One Database (MCOD) that hastwo central instances, onlyone central instance and the database shut down. Therefore, you mustfirst stop the other SAP system withstopsap R3 or make sure that it has already been stopped.For more information, see Installation of Multiple Components in one Database[page103].
■ If you have acentral system , enter the following to stop all instances on the central system host:stopsap
Only valid for: non-HA |
This stops the central instance and database.End of: non-HA |
Only valid for: HA (UNIX) |
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>
6 Additional Information
6.10 Starting and Stopping SAP System Instances
2009-05-25 PUBLIC 127 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 128/142
Only valid for: HA (UNIX) |
stopsap R3 <instance ID of central services instance>
End of: HA (UNIX) |
stopsap DBOnly valid for: non-HA |
Make sure that you always stop the central instance first because otherwise the databasecannot be stopped.End of: non-HA |
Only valid for: HA (UNIX) |
Make sure that you always stop the central instance first and the central services instancesecond because otherwise the database cannot be stopped.End of: HA (UNIX) |
■ In a distributed system , proceed as follows:1. On the dialog instance host, enter the following command:
stopsap <instance ID of dialog instance>
2. Only valid for: non-HA |
On the central instance host, enter the following command:End of: non-HA |
Only valid for: HA (UNIX) |
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
C AUTION
Make sure that no SAP instance is running before you enterstopdb on a standalone databaseserver. No automatic check is made.
6.11 Creating a User for LDAP Directory Access
If you use LDAP directory services, you have to set up a user with a password on the host where theSAP system is running. This permits the SAP system to access and modify the LDAP directory.For more information, seePreparing the Active Directoryin the Windows installation guide for your SAPsystem solution and database.
Prerequisites
During the SAP instance installation you chose to configure the SAP system to integrate LDAP services.
6 Additional Information
6.11 Creating a User for LDAP Directory Access
128 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 129/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 130/142
For more information, see Interrupted Installation with SAPinst [page116].■ After resolving the problem, you can continue the installation by choosingRetry.
3. Check the log and trace files of the GUI server and SAPinst GUI in the directory<user_home>/.sdtgui/ for errors.
■ If GUI server or SAPinst GUI do not start, check the filesdtstart.err in the current<user_home> directory.
■ If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUIas described inStarting SAPinst GUI Separately[page119].
■ If you use an X Server forMicrosoft Windows or other remote desktop tools for the RemoteAccess of SAPinst GUI on Windows Workstations and you experience display problems suchas missing repaints or refreshes, contact your X Server vendor. The vendor can give you
information about whether this X Server supports Java Swing-based GUIs and also tell youabout further requirements and restrictions. See also SAP Note 1170809.
6.14 Deleting an SAP System
This section describes how to delete a single instance, a standalone engine, or a complete SAP systemwith the Uninstalloption of SAPinst.
NOTE
With this SAPinst option you donot delete the database software.
NOTE
We recommend that you delete an SAP system with SAPinst. However, you can also delete an SAPsystem manually. For more information, see SAP Note 1229586.
Prerequisites■ You are logged on as userroot .■ If the saposcol process on the host you are working on has been started from the SAP system you
want to delete, stop it using the command saposcol -k .If there are other SAP systems on the host, log on as user<sapsid>adm of the other SAP systemand start saposcol from there using the command saposcol -l .
Procedure
1. Start SAPinst [page73] and on the Welcomescreen, choose:<Your SAP product> Software Life-Cycle Options Uninstall Uninstall System / Standalone Engine / Optional
Standalone Unit
2. Follow the instructions in the SAPinst input dialogs.
6 Additional Information
6.14 Deleting an SAP System
130 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 131/142
NOTE
For more information about the input parameters, place the cursor on the relevant field andpress F1 in SAPinst.
SAPinst first asks you which SAP instances you want to delete. Make sure that you delete the SAPinstances in the order as described below.
CAUTION
SAPinst only stopslocal instances automatically.Before you delete the database instance of a distributed system make sure that you stop allremaining instances. You must stop the instance with the message server only afterhavingentered all SAPinst parameters for the deletion of the database instance.
■ If you want to delete acentral system (all instances reside on the same host), you can do this
in one SAPinst run.1. Delete the SAP system.2. Delete the Oracle database software with the Oracle Universal Installer (OUI) as described
in Deleting the Oracle Database Software[page131].■ If you want to delete adistributed or high availability system, you have to run SAPinst to
delete the required instances locally on each of the hosts belonging to the SAP system in thefollowing sequence:1. Dialog instances, if there are any2. Central instance3. Database instance
SAPinst deletes the database instance but you have to delete the Oracle database softwaremanually as described inDeleting the Oracle Database Software[page131].
■ Only valid for: HA (UNIX) |
ABAP central services instance (ASCS)End of: HA (UNIX) |
■ The relevant directory structure on the global host3. If required, you can delete the directory/usr/sap/trans and its content manually.
SAPinst does not delete/usr/sap/trans because it might be shared.4. If you created the directories/usr/sap/<SAPSID> and /<sapmnt>/<SAPSID> as mount points, but
not as directories on the local file system, you have to remove them manually.
6.15 Deleting the Oracle Database Software
You have to delete the Oracle database software to complete the deletion of the Oracle database instance.Here you find information how to delete the Oracle database software with the Oracle Universal Installer
(OUI).
6 Additional Information
6.15 Deleting the Oracle Database Software
2009-05-25 PUBLIC 131 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 132/142
NOTE
This section only applies if you have deleted your SAP system using theUninstalloption of SAPinst.We recommend that you delete a database instance with SAPinst and then remove the database
software manually. However, you can also delete the complete database instance manually. Formore information, see SAP Note 1229689.
Procedure1. Start the OUI with the userora<dbsid> by entering one of the following:
■ cd /oracle/stage/102_64/database/Disk1/SAP
./runInstaller
■ cd /oracle/stage/102_64/database/SAP
./runInstaller
You see a message that a response file is being generated. It might take several minutes before yousee the OUI screen.
2. Choose Installed Productsor 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. ChooseRemove.6. Confirm your selection withYes.7. ChooseEXIT .
6 Additional Information
6.15 Deleting the Oracle Database Software
132 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 133/142
A Appendix
A.1 Online Information from SAP
More information is available online as follows.
Documentation
Description Internet Address Title
Master Guide for SAPenhancement package 4 for
SAP ERP 6.0
http://service.sap.com /erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0
SAP enhancement package 4 for SAP ERP 6.0
Master Guide – SAP Enhancement Package 4 for SAP ERP 6.0 powered by
SAP NetWeaver Master Guide for SAP ERP6.0
http://service.sap.com /erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0
SAP enhancement package 4 for SAP ERP 6.0
Master Guide - SAP ERP 6.0
Master Guide SAP SolutionManager 7.0
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0
Master Guide – SAP Solution Manager 7.0
Installation of SAPSolution Manager 7.0
http://service.sap.com /instguides SAP Components SAP Solution Manager Release 7.0
Installation Guide – SAP SolutionManager 7.0 on <OS>: <Database>
Configuration of SAPSolution Manager 7.0
http://service.sap.com /instguides SAP Components SAP Solution Manager Release 7.0
Configuration Guide – SAP SolutionManager 7.0 as of <current stack>
Patching of SAP NetWeaver7.0 scenarioshttp://service.sap.com /maintenanceNW70SPS <current stack> Support Package Stack Guide –
SPS <current stack>
Support Package Stack Guide – SAP NetWeaver 7.0 SPS <current stack>
Upgrade to EHP4 for SAPERP 6.0
http://service.sap.com/erp-inst SAP ERP SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 4 for SAP ERP 6.0 SAP ERP 6.0 Upgrade Master Guide
Upgrade Master Guide - SAP ERP 6.0
Installation of SAPNetWeaver DeveloperWorkplace
http://service.sap.com /installNW70
Installation Installation — Clients Installation – SAP Developer Workplace
Installation Guide – Developer Workplace for SAP NetWeaver
Installation of SAPNetWeaver DeveloperStudio
http://service.sap.com /installNW70
Installation Installation — Clients Installation – SAP NetWeaver Developer Studio
SAP NetWeaver Developer Studio — Standalone Installation Guide
Installation of the SystemLandscape Directory (SLD)
http://service.sap.com /installNW70
Configuration Post-Installation Guide – SLD of SAP NetWeaver 7.0
Post-Installation Guide – SystemLandscape Directory of SAP NetWeaver 7.0
Installation of a standalonegateway
http://service.sap.com /installNW70
Installation – Standalone Engines Installation — Gateway on <platform>
Installation Guide – Gateway on<platform> – For SAP Systems Based on SAP NetWeaver 7.0 (2004s)
Installation of WebDispatcher
http://service.sap.com /installNW70
Installation – Standalone Engines Installation — WebDispatcher on <platform>
Installation Guide – Web Dispatcher on<platform> – For SAP Systems Based on SAP NetWeaver 7.0 (2004s)
A Appendix
A.1 Online Information from SAP
2009-05-25 PUBLIC 133 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 134/142
Description Internet Address Title
Front End installation http://service.sap.com /installNW70
Installation – Clients Installation – SAP Front End <Release>
SAP Front End Installation GuideThis guide is also available on thePresentation DVD.
Homogeneous andheterogeneous systemcopy for SAP systems basedon NetWeaver 7.0
http://service.sap.com /installNW70
Installation – SAP NetWeaver Systems System Copy for SAP Systems Based on <Release> <Technology>
System Copy Guide — System Copy for SAP Systems based on SAP NetWeaver <Release> <Technology>
SAP NetWeaver ProblemAnalysis Guide
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English
SAP NetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by KeyCapability SAP NetWeaver Problem Analysis Guide(PAG)
SAP NetWeaver Problem AnalysisGuide (PAG)
General Quick Links
Description Internet Address
SAP Help Portal http://help.sap.com
SAP NetWeaver Library in SAPHelp Portal
http://help.sap.com/nw70
SAP ERP Library in SAP Help Portalhttp://help.sap.com/erp
SAP Notes http://service.sap.com/notes
SAP Notes for SAP NetWeaver 7.0installation
http://service.sap.com/sapnotesnw70
Forums, blogs, and generalinformation related to all of thesupported databases and operatingsystem platforms
http://sdn.sap.com/irj/sdn/dbos
Product Availability Matrix (PAM)for supported operating systemreleases
http://service.sap.com/pam
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
A Appendix
A.1 Online Information from SAP
134 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 135/142
Description Internet Address
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
A Appendix
A.1 Online Information from SAP
2009-05-25 PUBLIC 135 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 136/142
Typographic Conventions
Example Description
<Example > Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your<User Name >”.
ExampleExample
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressionsExample Words or characters that you enter in the system exactly as they appear in the
documentationhttp://www.sap.com Textual cross-references to an internet address/example Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web123456 Hyperlink to an SAP Note, for example, SAP Note123456Example ■ Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.■ Cross-references to other documentation or published works
Example ■ Output on the screen following a user action, for example, messages■ Source code or syntax quoted directly from a program■ File and directory names and their paths, names of variables and parameters, andnames 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
136 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 137/142
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +49/18 05/34 34 34
F +49/18 05/34 34 20 www.sap.com
© Copyright 2009 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express 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 other softwarevendors.
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 other softwarevendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germanyand in several other countries all over the world. All other product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves informational purposes only. National product specificationsmay 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.
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.
2009-05-25 PUBLIC 137 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 138/142
Legal Software Terms
Terms for Included Open Source Software
This SAP software contains also the third party open source software products listed below. Note that for these third party
products the following special terms and conditions shall apply.1. This software was developed using ANTLR .2. SAP License Agreement for STLport
SAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)1. Subject Matter of the Agreement
1. SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++library (STLport) and its documentation without fee.
2. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectualproperty laws, and to all of the terms and conditions of this Agreement.
3. The Customer may distribute binaries compiled with STLport (whether original or modified) without anyroyalties or restrictions.
4. Customer shall maintain the following copyright and permissions notices on STLport sources and itsdocumentation unchanged: Copyright 2001 SAP AG
5. The Customer may distribute original or modified STLport sources, provided that:■ The conditions indicated in the above permissions notice are met;■ The following copyright notices are retained when present, and conditions provided in accompanying
permission notices are met:Copyright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG
Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes 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 that
copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes norepresentations 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 materialis provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permissionto use or copy this software for any purpose is hereby granted without fee, provided the above notices areretained on all copies. Permission to modify the code and to distribute modified code is granted, provided theabove notices are retained, and a notice that the code was modified is included with the above copyright notice.
138 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 139/142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 140/142
■ "Object" form shall mean any form resulting from mechanical transformation or translation of a Sourceform, including but not limited to compiled object code, generated documentation, and conversions to othermedia types.
■ "Work" shall mean the work of authorship, whether in Source or Object form, made available under the
License, as indicated by a copyright notice that is included in or attached to the work (an example is providedin the Appendix below).■ "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 modificationsrepresent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shallnot include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Workand Derivative Works thereof.
■ "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 toLicensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized tosubmit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but notlimited to communication on electronic mailing lists, source code control systems, and issue tracking systemsthat are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, butexcluding communication that is conspicuously marked or otherwise designated in writing by the copyrightowner as "Not a Contribution."
■ "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.
2. 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.
3. 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 Workor a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then anypatent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. 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:1. You must give any other recipients of the Work or Derivative Works a copy of this License; and2. You must cause any modified files to carry prominent notices stating that You changed the files; and3. 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
4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that Youdistribute must include a readable copy of the attribution notices contained within such NOTICE file,excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the followingplaces: within a NOTICE text file distributed as part of the Derivative Works; within the Source form ordocumentation, if provided along with the Derivative Works; or, within a display generated by the DerivativeWorks, if and wherever such third-party notices normally appear. The contents of the NOTICE file are forinformational purposes only and do not modify the License. You may add Your own attribution noticeswithin Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from theWork, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different licenseterms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works
140 /142 PUBLIC 2009-05-25
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 141/142
as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditionsstated in this License.
5. Submission of ContributionsUnless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You
to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions.Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreementyou may have executed with Licensor regarding such Contributions.
6. TrademarksThis License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work andreproducing the content of the NOTICE file.
7. 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, either expressor 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 of permissions under this License.
8. 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.
9. Accepting Warranty or Additional LiabilityWhile 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,in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for anyliability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warrantyor additional liability.
Documentation in the SAP Service MarketplaceYou can find this document at the following address:https://service.sap.com/instguides
2009-05-25 PUBLIC 141 /142
7/29/2019 EHP4 SR1 Installation
http://slidepdf.com/reader/full/ehp4-sr1-installation 142/142
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany T +49/18 05/34 34 34F +49/18 05/34 34 20
www.sap.com