- 1. Installation Guide SAP ERP 6.0 Including SAP Enhancement
Package 5 - Technical Usage Central Applications Java on Windows:
Oracle Based on SAP NetWeaver 7.0 Including Enhancement Package 2
Target Audience {L System Administrators {L Technical Consultants
PUBLIC {;Ghsr4>H Q6H.D^f/,e_`g|LR)I
2. About this Installation Guide SAP System Installation SAP
system installations should only be performed by SAP Technical
Consultants certified for your operating system, your database, and
the SAP system that you are installing SAP Installation Tool You
must only use the SAP installation tools according to the
instructions and for the purposes
describedintheSAPinstallationdocument.ImproperuseoftheSAPinstallationtoolscandamagefiles
and systems already installed. Downward Compatibility of Databases
Fordownward-compatiblereleasesofDB/OSplatformsforSAPproducts,SAPplanstoregularlyrelease
the newest database (DB) and operating-system (OS) versions of SAP
products. These releases are downward-compatible with earlier SAP
system releases. Note that for already shipped SAP components, we
only support the installation for database versions proposed by the
installation tool. Therefore, you must install an SAP component or
perform a system copy using a downward-compatible database. That
is, you either install the component with the old proposed database
version or you upgrade the old database version to the
downward-compatible new version. 2/238 PUBLIC 2010-12-20 3.
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.0 2010-12-20 Initial Version 2010-12-20
PUBLIC 3/238 4. Table of Contents Chapter 1 Introduction . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . 11 1.1 New Features . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 13 1.2 SAP Notes for the Installation . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 14 1.3 How to Use
This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . 15 Chapter 2 Installation Options
Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . .
17 2.1 Central System . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.2
Distributed System . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . 18 2.3 High
Availability System . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . 19 2.4 Dialog Instance . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . 19 2.5 Installation of Additional Usage Types
or Software Units in an Existing SAP System . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . 21 2.6 Host Agent as a Separate Installation . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.1
Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . 23 3.2 Hardware and
Software Requirements . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . 24 3.2.1 Running the Prerequisite Checker in
Standalone Mode (Optional) . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2.2 Requirements for a Central System . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . 26 3.2.3 Requirements for a
Distributed System . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . 28 3.2.4 Requirements for a High-Availability System .
. . . . . . . . . . . . . . . . . . . . . . . . . 30 3.2.5
Requirements for the Dialog Instance . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 34 3.2.6 Requirements for the Host
Agent as a Separate Installation . . . . . . . . . . . . . . . 34
3.3 Planning User and Access Management . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 36 3.4 Basic SAP System
Installation Parameters . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . 37 3.5 Domain or Local Installation . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 3.6
Distribution of SAP System Components to Disks . . . . . . . . . .
. . . . . . . . . . . . 48 3.7 SAP Transport Host . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 50 3.8 Multiple Oracle Homes . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . 50 3.9 Internet
Pricing and Configurator . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . 51 4/238 PUBLIC 2010-12-20 5. Chapter 4
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . 53 4.1 Preparation
Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . 53 4.2 Disabling the Windows Server
2008 (R2) Firewall . . . . . . . . . . . . . . . . . . . . . . . 54
4.3 Performing Basic Windows Preparation Steps . . . . . . . . . .
. . . . . . . . . . . . . . . . 54 4.4 Required User Authorization
for Running SAPinst . . . . . . . . . . . . . . . . . . . . . 57
4.5 Preparing the SAP System Transport Host . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 58 4.6 Generating the SAP Solution
Manager Key . . . . . . . . . . . . . . . . . . . . . . . . . . .
59 4.7 Installing the Java Development Kit . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 60 4.8 Downloading JCE
Policy Files . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . 60 4.9 Preparing the Installation Media . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Chapter 5 Installation . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 5.1
Installation Checklist . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . 65 5.2 Installing the
Oracle Database Software . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . 66 5.2.1 Installing the Oracle 10g Database
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.2.1.1 Installing the Oracle 10g Database Software . . . . . . . .
. . . . . . . . . . . . . . . . . . . 66 5.2.1.2 Installing the
Current Patch Set . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . 68 5.2.1.3 Installing the Current Patch
Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 68 5.2.2 Installing the Oracle 11g Database Software . . . . .
. . . . . . . . . . . . . . . . . . . . . . 69 5.2.2.1 Installing
the Oracle 11g Server Software . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . 69 5.2.2.2 Installing Required Generic
Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . 71 5.2.2.3 Installing the Current Patch Set . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 71 5.2.2.4
Installing the Current Patch Collection . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 72 5.3 Setting Up Multiple Homes .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . 73 5.4 Running SAPinst . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 5.5
Additional Information About SAPinst . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . 78 5.5.1 How to Avoid Automatic
Logoff by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . .
. . 78 5.5.2 Interrupted Installation with SAPinst . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 79 5.5.3 Performing
a Remote Installation with SAPinst . . . . . . . . . . . . . . . .
. . . . . . . . 81 5.5.4 Starting SAPinst GUI Separately . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
5.5.5 Running SAPinst in Accessibility Mode . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . 84 5.5.6 Entries in the
Services File Created by SAPinst . . . . . . . . . . . . . . . . .
. . . . . . . . 85 Chapter 6 Post-Installation . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 87 6.1 Post-Installation Checklist . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 87 6.2 Logging
On to the Application Server . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . 89 6.3 Logging On to the Portal . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. 90 2010-12-20 PUBLIC 5/238 6. 6.4 Logging On to the SAP NetWeaver
Development Infrastructure (NWDI) . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . 91 6.5 Configuring User Management . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 92 6.6 Installing
the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . 92 6.7 Applying the Latest Kernel and
Support Package Stacks . . . . . . . . . . . . . . . . . 93 6.8
Creating Symbolic Links on Windows Server 2008 (R2) for Application
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . 94 6.9
Configuring Remote Connection to SAP Support . . . . . . . . . . .
. . . . . . . . . . . 94 6.10 Performing Post-Installation Steps
for the Java Application Server . . . . . . . . . 94 6.11 Ensuring
User Security . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 96 6.12 Performing Oracle-Specific
Post-Installation Steps . . . . . . . . . . . . . . . . . . . . .
100 6.13 Performing a Full System Backup . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 101 6.14 Setting
Environment Variable CPIC_MAX_CONV . . . . . . . . . . . . . . . .
. . . . 102 6.15 Configuring the Connection to a Central System
Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 6.16
Updating Component Repository Content in the System Landscape
Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . 103 6.17 Activating
Internet Pricing and Configurator . . . . . . . . . . . . . . . . .
. . . . . . . . 103 6.18 Checking the Availability of Back-End
Systems for Extended E-Selling Components . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . 103 6.18.1 Creating a Back-End User . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 104 6.18.2
Checking the Connection to the ABAP System . . . . . . . . . . . .
. . . . . . . . . . . 104 6.18.3 Configuring and Checking the TREX
Service . . . . . . . . . . . . . . . . . . . . . . . . . 106
6.18.4 Checking the Selling via eBay Processes . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . 106 6.19 Checking the
Availability of SAP ERP Biller Direct . . . . . . . . . . . . . . .
. . . . . . 107 6.20 Checking the Availability of SAP ERP Utility
Customer E-Services . . . . . . . . 107 6.21 Checking the
Availability of SAP ERP Retail Store Applications . . . . . . . . .
. . 108 6.22 Configuring SAP ERP Business Packages . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 108 6.23 Installation
Check and Configuration for SAP ERP Learning Solution Content
Player . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . 109 6.24 Configuring the
Application Sharing Server . . . . . . . . . . . . . . . . . . . .
. . . . . 109 6.25 Running the Configuration Wizard . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 110 6.26 Using
Extended Configuration Management (XCM) . . . . . . . . . . . . . .
. . . . . 110 6.26.1 Starting XCM . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
6.26.2 Changing the Language . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . 112 6.26.3 Printable
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . 113 6.26.4 General Settings . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . 113 6.26.5 Multiple Application
Configurations . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . 113 6/238 PUBLIC 2010-12-20 7. 6.26.6 Running the Web
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . 116 6.26.7 Uploading and Downloading XCM Settings .
. . . . . . . . . . . . . . . . . . . . . . . . . 117 6.26.8
Indication of Obsolete XCM Settings . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . 117 6.26.9 IPC Switch for XCM
Configuration of SAP E-Commerce . . . . . . . . . . . . . . . . 118
6.27 Post-Installation Steps for the Diagnostics Agent . . . . . .
. . . . . . . . . . . . . . . . 118 6.28 Post-Installation Steps
for the Host Agent . . . . . . . . . . . . . . . . . . . . . . . .
. . . 118 6.29 Accessing Configuration Documentation in SAP
Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Chapter
7 Additional Information . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . 121 7.1 SAP Directories . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . 121 7.2 Performing a Domain Installation
Without Being a Domain Administrator . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
125 7.3 Installation of Multiple Components in One Database . . . .
. . . . . . . . . . . . . . 128 7.4 Integration of LDAP Directory
Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
130 7.5 Preparing an External ABAP System as Source for User Data .
. . . . . . . . . . . . 133 7.6 Dialog Instance Installation for an
Upgraded System only: Updating Profiles . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . 136 7.7 Installing Additional Usage Types or Software
Units in an Existing SAP System . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 137 7.7.1 Installing Additional Usage Types Step By Step . . .
. . . . . . . . . . . . . . . . . . . . 138 7.7.2 Software
Component Archives of SAP NetWeaver 7.0 EHP2 Usage Types . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 144 7.7.3 Software Component
Archives of SAP ERP 6.0 EHP5 Usage Types . . . . . . . . . 145 7.8
Installing the Host Agent Separately . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . 149 7.9 Starting and Stopping the
SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 151 7.10 Configuring the Windows Server 2008 Firewall . . . . .
. . . . . . . . . . . . . . . . . . . 151 7.11 Usage Type-Specific
Initial Technical Configuration . . . . . . . . . . . . . . . . . .
. 153 7.11.1 Initial Technical Configuration for SAP NetWeaver
Application Server Java (AS Java) . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 153 7.11.1.1 Initial Technical Configuration for Adobe Document
Services . . . . . . . . . . . 154 7.11.1.2 Initial Technical
Configuration for Composite Application Framework Core (CAF) . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . 154 7.11.1.3 Initial Technical
Configuration for the System Landscape Directory (SLD) . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . 155 7.11.2 Initial Technical
Configuration for Development Infrastructure (DI) . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . 156 2010-12-20 PUBLIC 7/238 8. 7.11.3
Initial Technical Configuration for the Portal (Usage Types EPC and
EP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . 157 7.11.4
Initial Technical Configuration for BI Java . . . . . . . . . . . .
. . . . . . . . . . . . . . . 158 7.11.4.1 Configuring BI Java
Information Broadcasting . . . . . . . . . . . . . . . . . . . . .
. . . 159 7.11.4.2 Process Chains: Transporting Texts for the Alert
Category . . . . . . . . . . . . . . 159 7.11.4.3 Renaming
initialPermissionsBI.xml.template . . . . . . . . . . . . . . . . .
. . . . . . . . 159 7.12 SAP System Security on Windows . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 160 7.13
Automatic Creation of Accounts and Groups . . . . . . . . . . . . .
. . . . . . . . . . . 162 7.14 Troubleshooting . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . 163 7.14.1 Troubleshooting with SAPinst . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . 164 7.14.2
Troubleshooting for Portal Installation . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . 164 7.14.3 Troubleshooting for SAP
ERP Business Packages (Portal Content) . . . . . . . . . 166
7.14.3.1 Activating BI Templates Manually . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . 166 7.14.3.2
Troubleshooting when Importing PAR Files . . . . . . . . . . . . .
. . . . . . . . . . . . 167 7.14.3.3 Troubleshooting in SSO with
SAP Logon Tickets . . . . . . . . . . . . . . . . . . . . . . 167
7.15 Deleting an SAP System or Single Instances . . . . . . . . . .
. . . . . . . . . . . . . . . . 169 7.16 Deleting the Oracle
Database Software . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . 172 Chapter 8 High Availability with Microsoft Cluster
Service . . . . . . . . . . . . . . . . . . 175 8.1 Installation
Checklist for a High-Availability System . . . . . . . . . . . . .
. . . . . . 177 8.2 Planning . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
179 8.2.1 System Configuration in MSCS . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 179 8.2.1.1 SAP System
Components in an MSCS Configuration . . . . . . . . . . . . . . . .
. . 179 8.2.1.2 Multiple SAP Systems In One MSCS Cluster . . . . .
. . . . . . . . . . . . . . . . . . . . 182 8.2.1.3 Multiple SAP
Systems In Multiple MSCS Clusters . . . . . . . . . . . . . . . . .
. . . . 184 8.2.1.4 Enqueue Replication Server in an MSCS
Configuration . . . . . . . . . . . . . . . . . 185 8.2.2
Distribution of SAP System Components to Disks for MSCS . . . . . .
. . . . . . . 186 8.2.3 Directories in an MSCS Configuration . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . 190 8.2.4 IP
Addresses in an MSCS Configuration . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . 191 8.2.5 Obtaining and Determining IP
Addresses for MSCS . . . . . . . . . . . . . . . . . . . . 195 8.3
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . 197 8.3.1 Assigning
Drive Letters for MSCS . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . 197 8.3.2 Mapping Host Names to IP
Addresses for MSCS . . . . . . . . . . . . . . . . . . . . . . .
197 8.3.3 Checking the Mapping of Host Names for MSCS . . . . . . .
. . . . . . . . . . . . . . . 198 8.3.4 Windows Server 2003:
Preparing an Existing SAP System to Support Multiple Systems in one
Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . 199 8.3.5 Windows Server 2003: Preparing the
Installation of Multiple SAP Systems in MSCS . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . 202 8/238 PUBLIC 2010-12-20 9. 8.4 Installation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . 205 8.4.1 Installing the Oracle
Fail Safe Software . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . 205 8.4.1.1 Installing the Oracle 10g Fail Safe
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
8.4.1.2 Installing the Oracle 11g Fail Safe Software . . . . . . .
. . . . . . . . . . . . . . . . . . . . 207 8.4.2 Configuring the
First MSCS Node . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . 209 8.4.3 Installing the Database Instance . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
8.4.4 Configuring the Additional MSCS Node . . . . . . . . . . . .
. . . . . . . . . . . . . . . . 211 8.4.5 Additional Steps for the
Oracle Fail Safe Configuration . . . . . . . . . . . . . . . . .
212 8.4.6 Installing the Central Instance . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . 214 8.4.7 Creating
the Oracle Fail Safe Group . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . 215 8.4.8 Setting Up a Shared Database
Directory in Oracle Home . . . . . . . . . . . . . . . . 216 8.4.9
Adding the Oracle Database Resource to the Fail Safe Group . . . .
. . . . . . . . . 218 8.4.10 Installing the Dialog Instance . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
219 8.5 Post-Installation . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 220 8.5.1
Post-Installation Checks for Enqueue Replication Server . . . . . .
. . . . . . . . . . 220 8.5.1.1 Checking the Status of the Enqueue
Replication Server with ENSMON . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
220 8.5.1.2 Monitoring the Lock Table During Failover with ENQT . .
. . . . . . . . . . . . . . 221 8.6 Additional Information . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . 223 8.6.1 Moving MSCS Groups or Services and Applications . .
. . . . . . . . . . . . . . . . . . 223 8.6.2 Rebooting During the
Installation or Conversion for MSCS . . . . . . . . . . . . . 224
8.6.3 Starting and Stopping the SAP System in an MSCS Configuration
. . . . . . . . . 225 Chapter A Appendix . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . 227 A.1 Online Information from SAP . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . 227 A.2 Using
Powershell . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . 229 2010-12-20 PUBLIC 9/238 10.
This page is left blank for documents that are printed on both
sides. 11. 1 Introduction This document explains how to install SAP
ERP 6.0 including SAP enhancement package 5 - technical usage
Central Applications Java. You perform the installation using
SAPinst. SAP ERP 6.0 including SAP enhancement package 5 -
technical usage Central Applications is based on the technology of
SAP NetWeaver 7.0 including enhancement package 2. For more
information about the technology provided by SAP ERP and SAP
NetWeaver, see http://service.sap.com/erp and
http://sdn.sap.com/irj/sdn/netweaver. Make sure you read the
corresponding Master Guides before you start with this installation
guide. The Master Guides are available as follows:
http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement
packages for SAP ERP 6.0 SAP enhancement package for SAP ERP 6.0
You can install SAP ERP 6.0 including SAP enhancement package 5 -
technical usage Central Applications on SAP NetWeaver Application
Server Java (AS Java) with the following software units: xx SAP ERP
Biller Direct (BD) xx SAP ERP Utilities Customer E-Services (UCES)
xx SAP ERP Learning Solution Content Player (LSOCP) xx SAP ERP
Extended E-Selling Components (XECO) xx SAP ERP Retail Store
Applications (IS-R-SRS) xx SAP ERP Portal Content Common
(BP-Common) xx SAP ERP Self Services (XSS) xx SAP ERP Portal
Content Self Services (BP-XSS) xx SAP ERP Business Packages (Portal
Content) (BP ERP). For more information, see the SAP ERP Master
Guide. You also need to decide what level of portal functionality
you require because this affects what you have to install for these
software units: xx If you want to use the full portal functionality
of SAP NetWeaver usage type EP, you also have to install SAP
NetWeaver EP Core (EPC) and SAP NetWeaver Enterprise Portal (EP).
xx If you only need the core portal functionality of SAP NetWeaver
usage type EPC, you also have to install SAP NetWeaver EP Core
(EPC). NOTE You also install SAP NetWeaver Application Server Java
(AS Java) with the Java software units. 1 Introduction 2010-12-20
PUBLIC 11/238 12. In addition to the SAP ERP software units, you
can install the following SAP NetWeaver usage types with SAPinst: H
SAP NetWeaver Development Infrastructure (DI) H SAP NetWeaver EP
Core (EPC) H SAP NetWeaver Enterprise Portal (EP) H SAP NetWeaver
Business Intelligence Java Components (BI Java) NOTE This
documentation describes how to install BI Java with a standalone
Java system. We recommend that you install BI Java with a
standalone Java system and that you configure the connection with
BI ABAP on a standalone ABAP system after the installation. The
software components of BI ABAP are contained in usage type AS ABAP.
If you want to install BI Java with an SAP NetWeaver ABAP+Java
system, proceed as described in SAP Note 1181025. 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. Constraints You need to
consider the following constraints before you start your
installation: H Your operating system platform must be 64-bit. NOTE
The only instance, you can still install on 32-bit is the dialog
instance. H The database must be Oracle 10.2.0.4 or 11.2.0, and
higher. Naming Conventions H SAP system refers to SAP ERP 6.0
including SAP enhancement package 5 - technical usage "Central
Applications. H Java system refers to SAP ERP 6.0 including SAP
enhancement package 5 - technical usage "Central Applications Java.
H diagnostics refers to diagnostics in SAP Solution Manager. H
diagnostics agent refers to the agent of diagnostics in SAP
Solution Manager. Windows Operating System In this document,
Windows Server 2008 (R2) with (R2) written in parentheses means
that the information applies to both Windows Server 2008 and
Windows Server 2008 R2. Profiling for High Availability H $h
{PY$3X7$7 TGoKE)~#dH The profile bars with the wording Only valid
for: HA (MSCS) for example, as in this section refer to content
that is only valid if you are installing a high-availability (HA)
system with Windows Server Failover Clustering. The Windows cluster
feature was previously called Microsoft Cluster Service (MSCS). For
practical reasons we are continuing to use the abbreviation MSCS in
this guide. H .h"PIX$,T4K 1 Introduction 12/238 PUBLIC 2010-12-20
13. 1.1 New Features The table below provides an overview of the
new features related to the installation. Make sure that you also
read the release notes at http://service.sap.com/releasenotes. Area
Description SAPinst G5 Running SAPinst with accessibility mode: G5
Keyboard access: This feature is generally available for all
operating systems. G5 High-color contrast: This feature is derived
from the Windows display properties. For more information, see
Running SAPinst in Accessibility Mode [page 84]. G5 Custom font
setting: This feature is derived from the Windows display
properties. For more information, see Running SAPinst in
Accessibility Mode [page 84]. High Availability G5 New installation
options for a high-availability system in a Microsoft Cluster SAP
adapted the installation procedure for a high-availability system
on Windows to make it easier and less error-prone for customers: G5
First Cluster Node This installation option now includes the
previously separate options Central Services Instance for ABAP
(ASCS), Central Services Instance (SCS), Enqueue Replication Server
(ERS), and First MSCS Node. It performs the following steps: G5
Installs the central services instance (SCS) G5 Installs the
enqueue replication server instance (ERS) for the SCS instances G5
Installs the host agent G5 Creates the SAP cluster group on the
first cluster node and adds the SCS instance to the SAP cluster
group G5 Additional Cluster Node This installation option includes
the previous options Enqueue Replication Server, and Additional
MSCS Node. It performs the followings steps: G5 Configures the
additional cluster node to run the SAP cluster group G5 Installs
the enqueue replication server instance (ERS) for the SCS instance
on a local drive G5 Installs the host agent on a local drive G5 As
of Windows Server 2008 (R2), the Windows cluster feature is called
Failover Clustering. For practical reasons we are
continuingtousethegeneralabbreviationMSCSinthisguide. 1
Introduction 1.1 New Features 2010-12-20 PUBLIC 13/238 14. 1.2 SAP
Notes for the Installation You must read the following SAP Notes
before you start the installation. These SAP Notes contain the most
recent information on the installation, as well as corrections to
the installation documentation. Make sure that you have the
up-to-date version of each SAP Note, which you can find at http://
service.sap.com/notes. SAP Notes for the Installation SAP Note
Number Title Description 998833 Release Restrictions SAP ERP 6.0 -
Enhancement Packages AtthetimeofthereleaseofSAPERP6.0including SAP
enhancement package 5, limitations affect the productive usage of
certain functions. This note provides customer information on these
restrictions. 1323537 Release Info SAP Enhancement Package 5 for
SAP ERP 6.0 SAP Enhancement Package 5 for SAP ERP 6.0 release
information. 1313850 Release Restrictions for SAP EHP 2 for SAP
NetWeaver 7.0 Customer information on restrictions in the
production use of certain functions. 1387319 SAP NetWeaver
7.02/Business Suite 7i2010: Windows Windows-specific information
about the SAP system installation and corrections to this
documentation. 1387374 SAP NetWeaver 7.02/Business Suite 7i2010:
Win Oracle Oracle-specificinformationabouttheSAPsystem installation
and corrections to this documentation 828268 Oracle 10g: New
functions Information about new Oracle features released for the
SAP system 1431800 1431800 Oracle 11.2.0: Central Technical Note
InformationaboutOracle11gwithmultiplelinks to notes on Oracle 11g
1339460 Inst. NetWeaver 7.0 EHP2 - Diagnostics Agent installation
Problems discovered after the publication of the installation guide
or post-installation steps 855498 Installation Prerequisite Checker
SAP Software on UNIX, Windows, and IBM i: Checking OS Dependencies
73606 Supported Languages and Code Pages Information on possible
languages and language combinations in SAP systems 1067221 Central
Note for Heterogeneous Installation This SAP Note and its related
SAP Notes describe the released operating system and database
combinations for heterogeneous SAP systems landscapes. 1258912 PLM
Core 7.00 Release Notes and Information Information and references
to other notes about installingPLMCore7.00andimportingPLMCore 7.00
Support Packages. 1349080 NW 7.02/BS 7i2010: Inst.Add.Java Usage
Types/Software Units SupplementaryinformationforsectionInstallation
of Additional Software Units or Usage Types in an Existing SAP
System [page 138] 1 Introduction 1.2 SAP Notes for the Installation
14/238 PUBLIC 2010-12-20 15. SAP Note Number Title Description
925741 Adobe Document Services with Nonsupported Platforms To use
ADS in SAP landscapes on nonsupported platforms, you have to
install an additional standaloneSAPsystemwithASJavaonaplatform
supported by ADS. 1459119 Locked files in kernel staging directory
Information about the procedure you have to perform if there are
locked files in the SAP kernel staging directory after you have
finished the installation process. 1.3 How to Use This Guide 1. You
decide on the installation option that you want to install. The
following installation options are described in this installation
guide: 7mbv Central system 7mbv Distributed system 7mbv
7mSo?_@&py%:~HZL`_]w2gL6{/W High-availability system
7mSo?W@&?y5~ZL_-Zn 18. I|; High-availability system [page 19]
[=b{0AwZ4~}3->E^ [=b] You can install dialog instances [page 19]
to an existing system. [=b] You can install additional usage types
in an existing SAP system [page 21]. [=b] You can install a host
agent [page 22] separately. 2.1 Central System You can install a
central system on a single host. These are the following instances:
[=b] Central services instance for Java (SCS instance) [=b]
Database instance (DB instance) [=b] Central instance Optionally
you can install one or more dialog instances. For more information,
see Dialog Instance [page 19]. The following figure shows an
example of SAP instances in a central system. 2 Installation
Options Covered by this Guide 2.1 Central System 2010-12-20 PUBLIC
17/238 19. vMo1M}E"Central Java System Optionally you can install
one or more dialog instances. For more information, see Dialog
Instance [page 19]. 2.2 Distributed System In a distributed system,
every instance can run on a separate host. These are the following
instances: vM# Central services instance for Java (SCS instance)
vM# Database instance (DB instance) vM# Central instance Optionally
you can install one or more dialog instances. For more information,
see Installation of a Dialog Instance [page 19]. 2 Installation
Options Covered by this Guide 2.2 Distributed System 18/238 PUBLIC
2010-12-20 20. >>C!Distributed Java System 7-Ck!@t4 21. !ws
B8A;O,;^ 2.3 High Availability System For more information about
the system components you have to install and how to distribute
them on the specific hosts, see System Configuration in MSCS [page
179]. ==C0!et4 22. w9ss1Gd 2.4 Dialog Instance You can install one
or more dialog instances for an existing SAP system. Dialog
instances are optional and can be installed on separate hosts. You
can have one or more dialog instances. A dialog instance can run
on: D The host of any instance of the existing SAP system D On a
dedicated host NOTE If you install a dialog instance in an existing
non-Unicode system (that has been upgraded to the current release),
the dialog instance is automatically installed as a non-Unicode
instance. SAPinst determines if a non-Unicode system exists and
chooses the correct executables for the system type. 2 Installation
Options Covered by this Guide 2.3 High Availability System
2010-12-20 PUBLIC 19/238 23. NOTE We do not recommend installing
dialog instances on the SAP global host. NOTE If you want to
install a dialog instance on an existing SAP system, you must
perform a domain installation. You must also make sure that your
existing SAP system was installed as a domain installation. For
more information, see Domain or Local Installation [page 47].
Dialog Instance for a Central System The following figure shows
dialog instances that are running on dedicated hosts.
[4nn53LtDialog Instance for a Central System For more information,
see Central System [page 17]. Dialog Instance for a Distributed
System The following figure shows dialog instances that are running
on dedicated hosts. 2 Installation Options Covered by this Guide
2.4 Dialog Instance 20/238 PUBLIC 2010-12-20 24. k)Xg.CDialog
Instance for a Distributed System For more information, see
Distributed System [page 18]. k"X5=%GK p(6{ GjUjiK Dialog Instance
for a High-Availability System In a high-availability system, you
require at least one dialog instance apart from the central
instance. For more information about how to install and distribute
the application servers in an MSCS configuration, see System
Configuration in MSCS [page 179]. k*Xz-~Wfn pQ6lGj 2.5 Installation
of Additional Usage Types or Software Units in an Existing SAP
System You perform the installation of additional usage types or
software units in an existing Java system to optimize total cost of
ownership (TCO). That is, you do not have to install a complete
additional Java system to run these additional usage types or
software units. The section Installing Additional Usage Types or
Software Units in an Existing SAP System [page 137] describes how
to perform the installation. 2 Installation Options Covered by this
Guide 2.5 Installation of Additional Usage Types or Software Units
in an Existing SAP System 2010-12-20 PUBLIC 21/238 25. 2.6 Host
Agent as a Separate Installation
UsingthehostagentyoucancentrallymonitoranyhostwiththeAlertMonitorortheSAPNetWeaver
Administrator or the Adaptive Computing Controller (ACC). In
addition, the host agent is used by the ACC for starting, stopping,
and relocating SAP instances and databases. The host agent is
automatically installed during the installation of all new SAP
system instances based on SAP NetWeaver 7.0 including Enhancement
Package 2 or higher. You only need to install a host agent
separately in the following cases: !hE@9 You want to manage a host
that does not have an SAP instance or component. !hE@9 You have
upgraded your SAP system to SAP NetWeaver 7.0 including Enhancement
Package 2 or higher. The section Installing the Host Agent
Separately [page 149] describes how to perform the installation. 2
Installation Options Covered by this Guide 2.6 Host Agent as a
Separate Installation 22/238 PUBLIC 2010-12-20 26. 3 Planning 3.1
Planning Checklist
Thissectionincludestheplanningstepsthatyouhavetoperformforthefollowinginstallationoptions:
I Central, distributed, or high-availability system I Dialog
instance Detailed information about the steps is available in the
relevant chapter. Prerequisites 1. You have planned your SAP system
landscape according to the Master Guide at http://
service.sap.com/erp-inst and the Technical Infrastructure Guide at
https:// cw.sdn.sap.com/cw/community/docupedia/tig. 2. You have
decided on your installation option [page 17]. Central,
Distributed, or High-Availability System NOTE In a central system,
all mandatory instances are installed on one host. Therefore, if
you are installing a central system, you can ignore references to
other hosts. 1. You check the hardware and software requirements
[page 24] on each host. 2. You plan how to set up user and access
management [page 36]. 3. You identify basic SAP system installation
parameters [page 37]. 4. You decide whether you want to perform a
domain or local installation [page 47]. 5. For the database
installation, you decide how to distribute your database components
to disk [page 48]. 6. You decide on the transport host to use [page
50]. 7. You decide if you want to use Multiple Oracle Homes [page
50]. 8. You decide if you want to use Internet Pricing and
Configurator [page 51]. 9. I 27. ZsTrC4BR)].p4&US( To install a
high-availability system with Microsoft Cluster Service (MSCS), you
perform the MSCS-specific planning steps [page 177]. I {sTrC13)u
10. You can continue with Preparation [page 53]. Dialog Instance 1.
You check the hardware and software requirements [page 24] for the
installation host on which you want to install one or more dialog
instances. 3 Planning 3.1 Planning Checklist 2010-12-20 PUBLIC
23/238 28. 2. You identify basic SAP system installation parameters
[page 37]. 3. You can now continue with Preparation [page 53]. 3.2
Hardware and Software Requirements You check that your hosts meet
the hardware and software requirements for your operating system
and the SAP instances. CAUTION If your hosts do not fully meet the
requirements, you might experience problems when working with the
SAP system. Prerequisites [< Make sure that the host name meets
the requirements listed in SAP Note 611361. Process Flow 1. Check
the Product Availability Matrix at http://service.sap.com/pam for
supported operating system releases. 2. Check the hardware and
software requirements using: [< The Prerequisite Checker in one
of two modes: [g^Z Central system >g^Z Distributed system
>g^Z High-availability system >g^Z Dialog instance Detailed
information about the steps is available in the relevant chapter.
Central System 1. You install the Oracle database software [page
66]. 2. If required, you set up multiple Oracle Homes [page 73]. 3.
You install the SAP system with SAPinst [page 73]. 4. You continue
with Post-Installation [page 87]. Distributed System 1. On the
database instance host, you install the Oracle database software
[page 66]. 2. If required, you set up multiple Oracle Homes [page
73] on the database instance host. 3. On the central instance host,
you run SAPinst [page 73] to install the central services instance.
4. On the database instance host, you run SAPinst [page 73] to
install the database instance. 5. On the central instance host, you
run SAPinst [page 73] to install the central instance. 6. If
required, you install one or more dialog instances on the chosen
hosts as described later in this section. 7. You continue with
Post-Installation [page 87]. High-Availability System 1.
Toinstallahigh-availabilitysystemwithMicrosoftClusterService(MSCS),youperformtheMSCS-
specific installation tasks [page 177]. 2. You continue with
Post-Installation [page 87]. Dialog Instance You perform the
following steps on the host where you install the dialog instance.
1. You run SAPinst [page 73] to install the dialog instance. 2. You
continue with Post-Installation [page 87]. 5 Installation 5.1
Installation Checklist 2010-12-20 PUBLIC 65/238 76. 5.2 Installing
the Oracle Database Software Continue with the section relevant for
the release of the Oracle database that you want to install: Ig
Installing the Oracle 10g Database Software [page 66] Ig Installing
the Oracle 11g Database Software [page 69] 5.2.1 Installing the
Oracle 10g Database Software Proceed as follows to install the
Oracle 10g database software: Process Flow 1. You install the
Oracle 10g database server software [page 66]. 2. You install the
current patch set [page 68]. 3. You install the current patch
collection [page 68]. 5.2.1.1 Installing the Oracle 10g Database
Software This section describes how to install the database server
software for Oracle 10g on the database host. Ig
FormoreinformationaboutOracle10g,seethedocumentationprovidedbyOracleontheRDBMS
DVD under :NTdatabasedocindex.htm Ig If you have already installed
an Oracle database instance or the Oracle software, and you want to
install an additional database instance, you have to decide whether
you want to use single or multiple Oracle Homes [page 50].
I_By!@".4r@XX! 77. v&JrF9=) CAUTION Ig You have to install the
Oracle server software on all MSCS nodes. Ig
WindowsServer2003:IfyouusemultipleOracleHomes,youmusthaveoneORACLE_HOME
per database instance on every cluster node on local disks. Ig All
ORACLE_HOMES must use the same disks and directories and
ORACLE_HOME names on all database MSCS nodes. IUB !P"u4>aX+u 78.
Information about the Oracle Client Software Ig As of Oracle 10g,
you no longer need to manually install the Oracle client software
on the application server, as SAPinst asks you for the Oracle
Client DVD and automatically installs the client software in the
DIR_CT_RUN directory. Ig Make sure that you use the most up-to-date
version of the Oracle client DVD from SAP Service Marketplace. Ig
Windows Server 2008: You require the Oracle Instant Client Version
10.2.0.4.8. 5 Installation 5.2 Installing the Oracle Database
Software 66/238 PUBLIC 2010-12-20 79. Procedure 1.
Onthedatabaseserver,placetheOracleRDBMSDVDintheDVDdriveandchangetotheplatform-
specific directory: :NT. 2. Start the Oracle Universal Installer by
double-clicking the file sapserver.cmd. 3. In the command prompt
box, specify the drive letter of the local disk where you want to
install the Oracle software, and the . NOTE The command prompt box
only appears, if you perform a new installation (or under a
different user), or if and are not set. 4. In the Oracle Universal
Installer, enter the information as shown in the following table:
Window Entry Specify File Locations If this screen appears, do the
following: f Under Source: For Path: Shows the path to the Oracle
source software. Do not change the path. f Under Destination: ff
For Name: Enter the name of the new directory. We recommend that
you use the name , for example, C12102 ff For Path: Enter the path
of a new directory.Werecommendthatyouusethe path: :ORACLE, for
example, C: ORACLEC12102 NOTE Do not specify an already existing
directory. You must specify a new directory. Choose Next. Summary
Choose Install. Oracle Net Configuration Assistant: Welcome If this
dialog appears, select Perform typical configuration. Configuration
Assistants NOTE If you get an error message, choose OK. Ignore the
following Warning screen and choose OK. Choose Next. End of
Installation Choose Exit to close the Oracle Universal Installer.
5. Install the current patch set and patch collection (if
available). For more information, see SAP Note 839187. 5
Installation 5.2 Installing the Oracle Database Software 2010-12-20
PUBLIC 67/238 80. [ed{&e`u jtWe'HD@=Y:NYFl* NOTE You have to
install the current Oracle patch set and patch collection (if
available) on both nodes. [en"&u`. Y,jVv';D= 5.2.1.2 Installing
the Current Patch Set After the Oracle database software
installation, you need to install the current patch set for Oracle
Database 10g Release 2 (10.2). Prerequisites [e< For more
information on the latest patch set available for Oracle 10.2, see
SAP Note 839187. [e< For more information about how to install
the patch set, see the patch set README file. CAUTION Do not
perform any of the post-installation steps mentioned in the patch
set README file. Only perform the post-installation steps 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 steps mentioned in the README file. [e< You
only have to install the latest (that is, the current) patch set.
Procedure 1. Log on as adm user. 2. Install the patch set as
described in the patch set README file. For more information, see
SAP Note 839187. NOTE MSCS only: You have to install the current
Oracle patch set on all MSCS nodes. 5.2.1.3 Installing the Current
Patch Collection On Windows, you can install one patch collection
and additional generic patches at the same time if required.
Windows patch collections are cumulative and contain the most
current CPU. For information about the current patch collection and
the generic patches, see SAP Note 839187. You use OPatch to install
the patch collection and the generic patches. For more information,
see SAP Note 839182. Prerequisites Make sure you have already
installed the current patch set [page 68]. 5 Installation 5.2
Installing the Oracle Database Software 68/238 PUBLIC 2010-12-20
81. Procedure 1. Log on as the adm user. 2. Install the patch
collection, following the instructions in the README document of
the patch collection. Make sure that you complete the
post-installation steps described in the README document. NOTE JJd
The README file uses the term bundle patch instead of patch
collection. JJd MSCS only: You have to install the current Oracle
patch collection (if available) on all MSCS nodes. 5.2.2 Installing
the Oracle 11g Database Software Proceed as follows to install the
Oracle 11g database software: Process Flow 1. You install the
Oracle 11g database server software [page 69]. 2. You install the
required generic patches [page 71]. 3. You install the current
patch set [page 71]. 4. You install the current patch collection
[page 72]. 5.2.2.1 Installing the Oracle 11g Server Software
Procedure CAUTION If you copy the files from the DVD to a local
disk, do not use directory names containing blanks. NOTE MSCS only:
You have to install the Oracle database server software on all MSCS
nodes. 1. Onthedatabaseserver,placetheOracle RDBMS DVD
intheDVDdriveandchangetothedirectory: :databaseSAP 2. Start the
Oracle Universal Installer (OUI) by double-clicking the file
sapserver.cmd. NOTE JJd You cannot directly invoke sapserver.cmd,
if you use UNC paths (sapserver.cmd). Instead, you must map a drive
letter to the shared directory and start sapserver.cmd via the
drive letter. JJd You can also use the Powershell script
sapserver.ps1 which you can also use with UNC paths to start the
OUI. To run the script, do not double-click on it, since this by 5
Installation 5.2 Installing the Oracle Database Software 2010-12-20
PUBLIC 69/238 82. default in the Windows explorer opens theedit
mode. Instead, right-click on it and execute it with Powershell.
For more information about Powershell, see Using Powershell [page
229]. ByOz For support reasons, do not use the setup.exe file in
the directory : database. Using sapserver.cmd or sapserver.ps1
guarantees a unique setup of the ORACLE_HOME that is common to SAP
systems. ByOz Windows Server 2008 (R2) with activated UAC: If you
have drive letters that were
createdinunelevatedmode,youcannotaccesstheminelevatedmode.Therefore,ifyou
want to double-click sapserver.cmd, you have to copy the Oracle
RDBMS DVD to a local disk. If you want to invoke sapserver.cmd from
within a command prompt or Powershell window, you have to elevate
(run as administrator) the command prompt or Powershell window
before you create the network drive. If a command prompt window
appears, specify the drive letter of the local disk where you want
to install the Oracle software, and the . The command prompt window
only appears if you perform a new installation (under a different
user), or if the ORACLE_HOME and are not set. 3. In the Oracle
Universal Installer, enter the information as shown in the
following table: Installing the Oracle 11.2.0 Database Software
Window Task Configure Security Updates Do not select the check box.
Choose Next. The installer issues a warning. Choose Yes and then
Next. Select Installation Option Confirm the default selection
Install database software only and then choose Next. Grid
Installation Options Confirm the default selection Single instance
database installation and then choose Next. Select Product
Languages Confirm the default option English and then choose Next.
Select Database Edition Confirm the default option Enterprise
Edition and then choose Next. Specify Installation Location This
window displays the value for ORACLE_BASE, which should be set in
the environment to :oracle. It also displays the value for
ORACLE_HOME, which should be oracle 112. Select this option and
then Next. Perform Prerequisite Checks This window checks if all
the required system prerequisites for the
installationofthedatabasesoftwarehavebeenmet.Ifsomeofthechecks
aredisplayedasFailed,youcanfixtheseproblemsandrunthecheckagain by
choosing Check Again. RECOMMENDATION
Westronglyrecommendyoutomakesurethattherearenofailed checks before
starting the software installation. Summary Review the information
displayed in this window and choose Finish. 5 Installation 5.2
Installing the Oracle Database Software 70/238 PUBLIC 2010-12-20
83. Window Task Install Product This window shows the progress of
the installation. Finish After the installation has finished
successfully, choose Finish. and close the Oracle Universal
Installer. 4. Install the latest generic patches [page 71], patch
set [page 71] and patch collection [page 72] (if available). For
more information, refer to SAP Notes 1431799 and 1431795. NOTE MSCS
only: You have to install the current Oracle generic patches, patch
set and patch collection (if available) on all MSCS nodes. 5.2.2.2
Installing Required Generic Patches After the database software
installation, you need to install required generic patches. You
need these generic patches before the current patch set.
Prerequisites Y@l Check SAP Note 1431795 to find the list of
required patches to be installed. Y@l Download the patches from:
http://service.sap.com/oracle-download Oracle 11.2.0.1 Database
RDBMS MS Windows (32 bit) / MS Windows x64 Make sure that you
download all zip files. Y@l Check SAP Note 839182 for instructions
on how to use OPatch. Procedure 1. Log on as adm user. 2. Install
the patches, following the instructions in SAP Note 839182. NOTE
MSCS only: You have to install the generic patches on all MSCS
nodes. 3. After all the patches have been successfully applied, you
can query the status with the following command: Open a command
prompt and run following command: adm user. 2. Install the patch
set as described in the patch set README file. For more
information, see SAP Note 1431799. NOTE MSCS only: You have to
install the current Oracle patch set on all MSCS nodes. 5.2.2.4
Installing the Current Patch Collection Windows patch collections
are cumulative and contain the most current CPU. For more
information about the current patch collection, see SAP Note
1431795. You use OPatch to install the patch collection. For more
information, see SAP Note 839182. Prerequisites Make sure you have
already installed the current patch set [page 71]. Procedure 1. Log
on as adm user. 2. Install the patch collection, following the
instructions in the README file of the patch collection. Make sure
that you complete the post-installation steps described in the
README file. NOTE UG The README file uses the term bundle patch
instead of patch collection. UG MSCS only: You have to install the
current Oracle patch collection (if available) on all MSCS nodes.
3.
Afterthepatchcollectionhasbeensuccessfullyapplied,youcanquerythestatuswiththefollowing
command: Open a command prompt and run following command: bin from
the system environment variable PATH: 1. Start the Oracle Universal
Installer with Start All Programs Oracle - Oracle Installation
Products Universal Installer . 2. In the Welcome screen, choose
Installed Products. 3. In the Inventory screen, choose the
Environment tab. 4. Deselect all components and choose Apply. 2.
Update or create, if not available, the user environment variable
PATH of the user who performs the installation with SAPinst: 1.
Windows Server 2003: Choose Start Control Panel System Advanced
Environment Variables . 2. Windows Server 2008 (R2): Choose Start
Control Panel System Advanced system settings Environment Variables
. 3. Under User variable for modify or create, if not available,
the value PATH to include the bin, which you want to use for the
installation. NOTE You also have to modify the user environment
variable PATH for all other users using the Oracle software. 5.4
Running SAPinst This section describes how to run the installation
tool SAPinst. SAPinst includes a GUI client and a GUI server, which
both use Java. This section describes an installation where
SAPinst, GUI client, and GUI server are running on the same host.
In the following, GUI client and GUI server are addressed as
SAPinst GUI. Useful Information About SAPinst OAt When you start
SAPinst, it automatically starts the SAPinst GUI. 5 Installation
5.3 Setting Up Multiple Homes 2010-12-20 PUBLIC 73/238 87. qK+D
SAPinst creates the installation directory sapinst_instdir, which
is located directly in the % ProgramFiles% directory. If SAPinst is
not able to create sapinst_instdir there, it tries to create
sapinst_instdir in the directory defined by the environment
variable TEMP. RECOMMENDATION We recommend that you keep all
installation directories until the system is completely and
correctly installed. qK+D SAPinst creates a subdirectory for each
installation option called sapinst_instdir , which is located in
%ProgramFiles%. qK+D SAPinst extractsitselfto
atemporarydirectorycalledsapinst_exe.xxxxxx.xxxx,whichislocated in
%TEMP%, %TMP%, %TMPDIR%, or %SystemRoot%. These files are deleted
after SAPinst has stopped running.
Thetemporarydirectorysapinst_exe.xxxxxx.xxxxsometimesremainsundeleted.Youcansafely
delete it. The temporary directory also contains the log file
dev_selfex.out from the extraction process, which might be useful
if an error occurs. CAUTION If SAPinst cannot find a temporary
directory, the installation terminates with the error FCO-00058.
qK+D During the installation, the default ports 21200, 21212, and
4239 are used for communication between SAPinst, GUI server, GUI,
and HTTP server, as follows: qK++ SAPinst uses port 21200 to
communicate with the GUI server. qK++ The GUI server uses port
21212 to communicate with the GUI client. qK++ 4239 is the port of
the HTTP server, which is part of the GUI server. If the ports for
SAPinst and the GUI server are already in use, SAPinst
automatically searches for free port numbers. If the search fails,
SAPinst exits. In this case or if you want SAPinst to use specific
ports, open a command prompt and change to the required directory
as follows: cd /d :IM_WINDOWS_ Execute sapinst.exe with the
following command line parameters: qK++ SAPINST_DIALOG_PORT= qK++
GUISERVER_DIALOG_PORT= qK++ GUISERVER_HTTP_PORT= qK+D To see a list
of all available SAPinst properties, open a command prompt and
start SAPinst with command line parameter -p: sapinst.exe -p qK+D
If you need to run SAPinst in accessibility mode, make sure that
you have activated and adjusted accessibility settings as described
in Running SAPinst in Accessibility Mode [page 84]. qK+D If
required, you can stop SAPinst by choosing SAPinst Cancel in the
SAPinst GUI menu. 5 Installation 5.4 Running SAPinst 74/238 PUBLIC
2010-12-20 88. NOTE If you need to terminate SAPinst you can do
this by choosing File Exit in the menu of the Program Starter
window. Prerequisites D!5 Make sure that you use an account with
the required user authorization to run SAPinst [page 57]. D!5 Make
sure that you have specified the most important SAP system
parameters as described in Basic SAP System Installation Parameters
[page 37] before you start the installation. D!5 If you are
installing a second or subsequent SAP system into an existing
database (MCOD), make sure that the database is up and running
before starting the installation. Check that the SYSTEM tablespace
contains at least 400 MB of free space. If there is not enough
space left, increase the size of this tablespace with BRSPACE or
BRTOOLS. For more information, see Installation of Multiple
Components in One Database [page 128]. D!5 If you want to install a
dialog instance to an existing SAP system, make sure that: D!5m The
service definitions for the SAP start services are configured
correctly and refer to the correct profile files. D!5m There are no
profile backup files with an underscore _ in their profile name. If
so, you must replace the _ with a .. EXAMPLE Rename
usrsapS14SYSprofileS14_DVEBMGS20_wsi6408_12 to
usrsapS14SYSprofileS14_DVEBMGS20_wsi6408.12. Procedure 1. Log on to
the installation host using an account with the required user
authorization to run SAPinst [page 57]. CAUTION Do not use an
existing adm user. 2. Insert the Installation Master DVD into your
DVD drive or mount it locally. 3. Start SAPinst from the
Installation Master DVD by double-clicking sapinst.exe from the
following path: :IM_WINDOWS_ NOTE
Ifyouneedtoperformtheinstallationinaccessibilitymode,openacommandprompt,change
to the :IM_WINDOWS_ directory, and execute sapinst.exe accessible.
For more information, see Running SAPinst in Accessibility Mode
[page 84]. The GUI starts automatically by displaying the Welcome
screen. 4. In the Welcome screen, choose your SAP system. You can
do either one of the following: D!5 Install an SAP system 5
Installation 5.4 Running SAPinst 2010-12-20 PUBLIC 75/238 89.
Choose SAP Application Server Java> You can install the
following system variants: System Variants Remarks Central System
Installs an SAP system with all mandatory instances on one host
Distributed System Installs an SAP system with all mandatory
instances on different hosts
Performtheinstallationoptionsexactlyintheordertheyappear.You
havetorestartSAPinstontherelevanthostforeachinstallationoption.
High-Availability System Installs a high-availability SAP system
with all mandatory instances on different hosts
Performtheinstallationoptionsexactlyintheordertheyappear.You
havetorestartSAPinstontherelevanthostforeachinstallationoption.
NOTE When you start the installation from a 32-bit installation
master DVD, all you see is the folder Software Life-Cycle Options
on the Welcome screen. gO Perform other tasks or install additional
components Choose Software Life-Cycle Options . The following
software life-cycle options are available: Software Life-Cycle
Installation Options Remarks Additional Preparation Options These
options comprise the following tasks: gO Host Agent Installs a
standalone host agent. For more information, see Installing the
Host Agent Separately [page 149]. gO Operating System Users and
Groups Creates all operating system users for your SAP system if
they do not yet exist Run this installation option before you start
the installation of the SAP system. gO Prerequisites Check
Checksyourhardwareandsoftwarerequirementsbeforeyoustart the
installation. For more information, see Running the Prerequisites
Checker in Standalone Mode [page 25]. Application Server Installs
one or more dialog instances in an already installed SAP system, if
required LDAP Registration Configures the Active Directory and sets
up LDAP support for an application server instance
WerecommendyoutoconfiguretheActiveDirectorybeforeyouinstall the SAP
system or an application server. For more information about LDAP
and Active Directory, see Integration of LDAP Directory Services
[page 130]. System Copy Performs a system copy Uninstall Uninstalls
your SAP system, standalone engines, or optional standalone units
For more information, see Deleting an SAP System [page 169]. 5.
Choose Next. 5 Installation 5.4 Running SAPinst 76/238 PUBLIC
2010-12-20 90. 6. If SAPinst prompts you to log off from your
system, log off and log on again. SAPinst restarts automatically.
7. Follow the instructions in the SAPinst input screens and enter
the required parameters. NOTE For more information about the input
parameters, position the cursor on the parameter and press F1 .
NOTE If you chose Typical mode for the installation, SAPinst did
not automatically prompt you during the Define Parameters phase
whether you want to use the vendor JDK or the SAP JVM for the
diagnostics agent. If you want to use the SAP JVM, choose
Diagnostics Agent > Java Development Kit Use SAP JVM
(recommended) from the Parameter Summary Screen (see also table
Diagnostics Agent Parameters in Basic SAP System Installation
Parameters [page 37]).
Afteryouhaveenteredallrequestedinputparameters,SAPinstdisplaystheParameterSummaryscreen.
This screen shows both the parameters that you entered and those
that SAPinst set by default. If required, you can revise the
parameters before starting the installation. 8. To start the
installation, choose Start. SAPinst starts the installation and
displays the progress of the installation. CAUTION
MultipleOracleHomesonly:SAPinstusesdefaultvaluesfortheOracleHomeandListener
configuration.Therefore,ifyouusemultipleOracleHomes,youmustspecifythenewOracle
home, as well as the listener port number. You can change these
values on the SAPinst Summary screen during the database instance
installation. On the Summary screen, check both Oracle >
Database System and Oracle > Listener Configuration and use the
Revise button. On the upcoming screen, change the Oracle Home and
the Listener port number. Make sure that you use a free port
number, and do not use the numbers 1521 or 1527 as these might
already be in use by default. 9. If you want to install an SAP
system with the software units SAP ERP Self Services (XSS) and SAP
ERP Business Packages (Portal Content) (BP ERP) that are running
directly on SAP NetWeaver usage type EP Core (EPC) (without
installing usage type EP), proceed as follows: 1. On the SAP System
> Software Units screen, select from the table Additional
NetWeaver Software Units only NetWeaver usage types AS Java and EP
Core (EPC). CAUTION Do not select usage type EP. 2. Continue with
the installation. When the installation has successfully completed,
SAPinst displays the Finished successfully message. 10. If
required, install a dialog instance for a central system or
distributed system. 5 Installation 5.4 Running SAPinst 2010-12-20
PUBLIC 77/238 91. 11. We recommend that you delete the directory
%userprofile%.sdtgui. 12. If you copied installation DVDs to your
hard disk, you can delete these files when the installation has
successfully completed. More Information A} How to Avoid Automatic
Logoff by SAPinst [page 78] A} Interrupted Installation with
SAPinst [page 79] A} Performing a Remote Installation with SAPinst
[page 81] A} Starting SAPinst GUI Separately [page 81] A} Running
SAPinst in Accessibility Mode [page 84] A} Entries in the Services
File Created by SAPinst [page 85] A} Troubleshooting with SAPinst
[page 164] 5.5 Additional Information About SAPinst The following
sections provide additional information about SAPinst: A} How to
Avoid Automatic Logoff by SAPinst [page 78] A} Interrupted
Installation with SAPinst [page 79] A} Performing a Remote
Installation with SAPinst [page 81] A} Starting SAPinst GUI
Separately [page 81] A} Running SAPinst with Accessibility Mode
[page 84] A} Entries in the Services File Created by SAPinst [page
85] 5.5.1 How to Avoid Automatic Logoff by SAPinst When you install
the SAP system with SAPinst, the SAPinst installation tool checks
whether the user account used for the installation has the required
privileges and authorization. For a domain installation, the
account needs to be both a member of the local Administrators group
and the domain Admins group. For a local installation, the account
needs to be a member of the local group Administrators group. In
both cases, the user account must be authorized to do the
following: A} Act as part of the operating system A} Adjust memory
quotas for a process A} Replace a process level token If the user
account does not have these rights assigned, SAPinst assigns them
and automatically logs the account off to activate them. To avoid
SAPinst logging the account off, you can set these rights manually
before you start the installation. 5 Installation 5.5 Additional
Information About SAPinst 78/238 PUBLIC 2010-12-20 92. Procedure
You perform the following steps to assign these rights to the user
account used for the installation. CAUTION Be aware that domain
policies override locally defined policies. This means that if you
want to grant domain administrator rights to a user who belongs to
the local Administrators group, make sure that you have also
defined domain administrator rights for this user on domain level.
1. Choose Start Settings Control Panel Administrative Tools Local
Security Policy . 2. In the Local Security Settings window, choose
Local Policies User Rights Assignment. . 3. Double-click the
required right under Policy and choose Add User or Group. 4. In the
Select Users and Groups window, choose the required user and choose
Add. The selected user appears in the box below. 5. Confirm your
entry and then repeat the steps for each remaining policy that the
user requires for the installation. 6. Log off and log on again to
apply the changes. More Information Required User Authorization for
Running SAPinst [page 57] 5.5.2 Interrupted Installation with
SAPinst The SAP system installation might be interrupted for one of
the following reasons: ~:IM_WINDOWS_ 4. Double-click sapinst.exe.
5. From the tree structure in the Welcome screen, select the
installation option that you want to continue and choose Next. The
What do you want to do? screen appears. 6. In the What do you want
to do? screen, decide between the following alternatives and
continue with Next: Alternative Behavior Run a new option SAPinst
does not continue the interrupted installation option. Instead, it
moves the content of the old installation directory and all
installation- specificfilesto abackup directory. Afterwards,
youcannolongercontinue the old installation option. For the backup
directory, the following naming convention is used: EXAMPLE
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 any
processescurrentlyrunningonthesefilesandfolders,theymightno longer
function properly. Continue with the old option SAPinst continues
the interrupted installation option from the point of failure. 5
Installation 5.5 Additional Information About SAPinst 80/238 PUBLIC
2010-12-20 94. 5.5.3 Performing a Remote Installation with SAPinst
You use this procedure to install your SAP system on a remote host.
In this case, SAPinst runs on the remote host, and the SAPinst GUI
runs on the local host. The local host is the host from which you
controltheinstallationwiththeSAPinstGUI.TheSAPinstGUIconnectsusingasecureSSLconnection
to SAPinst. Alternatively you can use an X server for Microsoft
Windows or other remote desktop tools such as VNC Viewer orNX
Server / NX Client
offeredbyvariousvendorsoropensourceforremoteaccess to SAPinst GUI
on Windows workstations. We recommend that you use the Hummingbird
Exceed X Server, which we use to validate installations with
SAPinst. For more information, see SAP Note 1170809. You can run
the SAPinst GUI on a PC with 32-bit while SAPinst is running on a
64-bit installation host. For more information, see Starting
SAPinst GUI Separately [page 81]. Prerequisites CJ The remote host
meets the prerequisites for starting SAPinst as described in
Running SAPinst [page 73] CJ 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 . 2. Log on to the local host and
enter the command ping . Procedure 1. Log on to your remote host as
a user that is a member of the local administrators group. 2.
Insert the Installation Master DVD in the DVD drive on your remote
host. 3. Open a command prompt and change to the required directory
by entering the following commands: cd /d :IM_WINDOWS_ Execute
sapinst.exe -nogui SAPinst now starts and waits for the connection
to the SAPinst GUI. You see the following at the command prompt:
guiengine: no GUI connected; waiting for a connection on host ,
port to continue with the installation 4. Start the SAPinst GUI on
your local host as described in Starting SAPinst GUI Separately
[page 81]. 5.5.4 Starting SAPinst GUI Separately
YouusethisproceduretostarttheSAPinstGUIseparately.YouneedtostarttheSAPinstGUIseparately
in the following cases: 5 Installation 5.5 Additional Information
About SAPinst 2010-12-20 PUBLIC 81/238 95. xP You closed the
SAPinst GUI using File Exit from the SAPinst menu while SAPinst is
still running.xP You want to perform a remote installation, where
the SAPinst GUI runs on a different host from SAPinst. For more
information, see Performing a Remote Installation with SAPinst
[page 81]. Prerequisites The host on which you want to start the
SAPinst GUI meets the prerequisites for starting SAPinst as
described in Running SAPinst [page 73]. Procedure Starting SAPinst
GUI on Windows 1. Insert the SAP Installation Master DVD into your
DVD drive. 2. Change to the directory of the sapinstgui executable:
:IM_WINDOWS_ NOTE If you want to start the SAPinst GUI on a Windows
32-bit operating system, change to the following directory:
:IM_WINDOWS_I386 3. Start the SAPinst GUI from a command prompt by
executing sapinstgui.exe with the relevant command line
parameters:xP If you want to perform a remote installation, execute
the following command: sapinstgui.exe -host -port where is the name
of the remote host, and is the port the GUI server uses to
communicate with the GUI client (21212 by default).xP If you closed
the SAPinst GUI using File Exit and want to reconnect to SAPinst,
proceed as follows:xP If you are performing a local installation
with SAPinst and SAPinst GUI running on the same host, execute the
following command: sapinstgui.exe -port where is the port the GUI
server uses to communicate with the GUI client (21212 by
default).xP If you are performing a remote installation with
SAPinst and SAPinst GUI running on different hosts, execute the
following command: sapinstgui.exe -host -port 5 Installation 5.5
Additional Information About SAPinst 82/238 PUBLIC 2010-12-20 96.
where is the name of the remote host, and is the port the GUI
server uses to communicate with the GUI client (21212 by default).
The SAPinst GUI starts and connects to SAPinst. Starting SAPinst
GUI on UNIX 1. Mount the Installation Master DVD. NOTE Mount the
DVD locally. We do not recommend that you use Network File System
(NFS). 2. Change to the directory of the sapinstgui executable by
entering the following command: cd /IM_ NOTE
IfyouwanttostarttheSAPinstGUIonaLinux32bitplatform,enterthefollowingcommand:
cd /IM_LINUX_I386 3. Start the SAPinst GUI by executing
./sapinstgui with the relevant command line parameters: q}-T If you
want to perform a remote installation, execute the following
command: ./sapinstgui -host -port where is the name of the remote
host, and is the port the GUI server uses to communicate with the
GUI client (21212 by default). q}-T If you closed the SAPinst GUI
using File Exit and want to reconnect to SAPinst, proceed as
follows: q}-T If you are performing a local installation with
SAPinst and SAPinst GUI running on the same host, execute the
following command: sapinstgui -port where is the port the GUI
server uses to communicate with the GUI client (21212 by default).
q}-T If you are performing a remote installation with SAPinst and
SAPinst GUI running on different hosts, execute the following
command: sapinstgui -host -port where is the name of the remote
host, and is the port the GUI server uses to communicate with the
GUI client (21212 by default). The SAPinst GUI starts and connects
to SAPinst. 5 Installation 5.5 Additional Information About SAPinst
2010-12-20 PUBLIC 83/238 97. 5.5.5 Running SAPinst in Accessibility
Mode You can also run SAPinst in accessibility mode. The following
features are available: D Keyboard access: This feature is
generally available for all operating systems. D High-contrast
color: This feature is derived from the Windows display properties.
You can use it either for a local installation or for a remote
installation. D Custom font setting: This feature is derived from
the Windows display properties. You can use it either for a local
installation or for a remote installation. Procedure Activating and
Adjusting Accessibility Settings on Windows You first have to
activate and adjust the relevant settings for the font size and
color schemes before you start SAPinst or the SAPinst GUI. NOTE The
following procedure applies for Windows Server 2008 and might be
different when using another Windows operating system. 1. Right
click on your Windows desktop and choose Personalize. 2. Select
Adjust font size (DPI) and choose Larger scale (120 DPI). To define
other font size schemes, choose Custom DPI. 3. In the right-hand
pane, select Window Color and Appearance. Select a color scheme
from the Color scheme drop-down box. To define your own color
schemes, choose Advanced. Running SAPinst in Accessibility Mode You
can either perform a local installation, where SAPinst and SAPinst
GUI are running on the same host, or a remote installation, where
SAPinst and SAPinst GUI are running on different hosts. D Local
installation: Start SAPinst as described in Running SAPinst [page
73] by executing the following command: sapinst.exe accessible D
Remote installation: 1. Start SAPinst on the remote host by
executing the following command from the command line as described
in Performing a Remote Installation with SAPinst [page 81]:
sapinst.exe nogui 2. Start SAPinst GUI on the local host by
executing the following command from the command line as described
in Starting the SAPinst GUI Separately for a Remote Installation
[page 81]: 5 Installation 5.5 Additional Information About SAPinst
84/238 PUBLIC 2010-12-20 98. sapinstgui.exe -accessible host -port
5.5.6 Entries in the Services File Created by SAPinst
Aftertheinstallationhasfinishedsuccessfully,SAPinsthascreatedthefollowingentriesforportnames
in WINDOWSsystem32driversetcservices: sapdp = 32/tcp sapdps =
47/tcp sapgw = 33/tcp sapgws = 48/tcp NOTE e