Installation Guide for System Copy SAP Systems Based on the
Application Server Java of SAP NetWeaver 7.0 including EHP3 on
Windows: OracleTarget System Installation for System CopyTarget
Audience System Administrators Technical Consultants
PUBLIC Document version: 1.00 2011-11-08
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 installingSAP
Installation Tool
You must only use the SAP installation tools according to the
instructions and for the purposes described in the SAP installation
document. Improper use of the SAP installation tools can damage
files and systems already installed.Downward Compatibility of
Databases
For downward-compatible releases of DB/OS platforms for SAP
products, SAP plans to regularly release the newest database (DB)
and operating-system (OS) versions of SAP products. These releases
are downward-compatible with earlier SAP system releases. Note that
for already shipped SAP components, we only support the
installation for database versions proposed by the installation
tool. Therefore, you must install an SAP component or perform a
system copy using a downward-compatible database. That is, you
either install the component with the old proposed database version
or you upgrade the old database version to the downward-compatible
new version.
2/180
PUBLIC
2011-11-08
Typographic Conventions
Example
Description
Example Example ExampleExample
Angle brackets indicate that you replace these words or
characters with appropriate entries to make entries in the system,
for example, Enter your . Arrows separating the parts of a
navigation path, for example, menu options Emphasized words or
expressions Words or characters that you enter in the system
exactly as they appear in the documentation Textual
cross-references to an internet address Quicklinks added to the
internet address of a homepage to enable quick access to specific
content on the Web Hyperlink to an SAP Note, for example, SAP Note
123456 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 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, and names of installation, upgrade, and database tools
Technical names of system objects. These include report names,
program names, transaction codes, database table names, and key
concepts of a programming language when they are surrounded by body
text, for example, SELECT and INCLUDE Keys on the keyboard
http://www.sap.com /example
123456 Example
Example
EXAMPLE
EXAMPLE
2011-11-08
PUBLIC
3/180
Document History
CAUTION
Before you start the implementation, make sure you have the
latest version of this document. You can find the latest version on
SAP Service Marketplace http://service.sap.com/ instguides. The
following table provides an overview on the most important document
changes:Version Date Description
1.00
2011-11-08
Initial Version
4/180
PUBLIC
2011-11-08
Table of Contents
Chapter 1 1.1 1.2 1.3 Chapter 2 2.1 2.2 2.3 2.4 2.5 Chapter 3
3.1 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.3 3.4 3.5 3.6 3.7 3.8
Chapter 4 4.1 4.2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . Before You Start . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . New Features . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. SAP Notes for the Installation . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . Installation Options
Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . .
Central System . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . Distributed System .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . High Availability System . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dialog Instance . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . Host Agent as a
Separate Installation . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . Planning . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . Hardware and Software
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . Running the Prerequisite Checker in Standalone Mode
(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . Requirements for a
Central System . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . Requirements for a Distributed System . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . Requirements for a
High-Availability System . . . . . . . . . . . . . . . . . . . . .
. . . . . Requirements for the Dialog Instance . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . Requirements for the Host
Agent as a Separate Installation . . . . . . . . . . . . . . .
Planning User and Access Management . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . Basic SAP System Installation
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. Domain or Local Installation . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . Distribution of SAP System
Components to Disks . . . . . . . . . . . . . . . . . . . . . . SAP
Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . Multiple Oracle Homes . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . .
11 11 12 13 15 15 16 17 18 19 21 21 22 23 24 26 28 32 32 34 35
43 44 46 47
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . 49 Preparation
Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . 49 Disabling the Windows Server 2008
(R2) Firewall . . . . . . . . . . . . . . . . . . . . . . . 50
2011-11-08
PUBLIC
5/180
4.3 4.4 4.5 4.6 4.7 Chapter 5 5.1 5.2 5.2.1 5.2.2 5.3 5.4 5.5
5.5.1 5.5.2 5.5.3 5.5.4 5.5.5 5.5.6 5.5.7 Chapter 6 6.1 6.2 6.3 6.4
6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13
Performing Basic Windows Preparation Steps . . . . . . . . . . .
. . . . . . . . . . . . . . . Required User Authorization for
Running SAPinst . . . . . . . . . . . . . . . . . . . . . Using
Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . Preparing the SAP System Transport
Host . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing the Installation Media . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . Installation . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . Installation Checklist . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Oracle 11g Database Software . . . . . . . . . . . .
. . . . . . . . . . . . . . . Installing the Oracle 11g Server
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Required Patches . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . Setting Up Multiple Homes . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . Running SAPinst . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . Additional
Information About SAPinst . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . How to Avoid Automatic Logoff by SAPinst . . . .
. . . . . . . . . . . . . . . . . . . . . . . Interrupted
Installation with SAPinst . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . Performing a Remote Installation with SAPinst
. . . . . . . . . . . . . . . . . . . . . . . . Starting SAPinst
GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . Running SAPinst in Accessibility Mode . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . Entries in the
Services File Created by SAPinst . . . . . . . . . . . . . . . . .
. . . . . . . . Troubleshooting with SAPinst . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . Post-Installation
Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . Logging On to the Application Server . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . Logging On to
the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . Logging On to the SAP NetWeaver
Development Infrastructure (NWDI) . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . Providing Access to the NetWeaver Administrator . . . . . .
. . . . . . . . . . . . . . . . Installing the SAP License . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . Configuring User Management . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . Creating Symbolic Links on
Windows Server 2008 (R2) for Application Servers . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . Configuring Remote Connection to SAP
Support . . . . . . . . . . . . . . . . . . . . . . Ensuring User
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . Performing Oracle-Specific
Post-Installation Steps . . . . . . . . . . . . . . . . . . . . . .
Setting Environment Variable CPIC_MAX_CONV . . . . . . . . . . . .
. . . . . . . . . Post-Installation Steps for the Diagnostics Agent
. . . . . . . . . . . . . . . . . . . . . . .
50 52 54 54 55 59 59 60 60 62 62 63 67 68 68 70 71 74 75 75 77
77 78 79 80 81 81 82 83 83 83 88 89 89
6/180
PUBLIC
2011-11-08
6.14 6.15 Chapter 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10
7.10.1 7.10.1.1 7.10.1.2 7.10.1.3 7.10.2 7.10.3 7.10.4 7.10.4.1
7.10.4.2 7.10.4.3 7.11 7.12 7.13 7.14 7.15
Post-Installation Steps for the Host Agent . . . . . . . . . . .
. . . . . . . . . . . . . . . . . 90 Performing a Full System
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . 90 Additional Information . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 93 SAP Directories
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . 94 Performing a Domain Installation
Without Being a Domain Administrator . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
97 Installation of Multiple Components in One Database . . . . . .
. . . . . . . . . . . . 100 Integration of LDAP Directory Services
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Preparing an External ABAP System as Source for User Data . . . . .
. . . . . . . . 105 Dialog Instance Installation for an Upgraded
System only: Updating Profiles . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 108 Installing the Host Agent Separately . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 109 Starting and Stopping
the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . 111 Configuring the Windows Server 2008 (R2) Firewall . . .
. . . . . . . . . . . . . . . . . 112 Usage Type-Specific Initial
Technical Configuration . . . . . . . . . . . . . . . . . . . 113
Initial Technical Configuration for SAP NetWeaver Application
Server Java (AS Java) . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Initial Technical Configuration for Adobe Document Services . . . .
. . . . . . . 114 Initial Technical Configuration for Composite
Application Framework Core (CAF) . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . 115 Initial Technical Configuration for the System
Landscape Directory (SLD) . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
116 Initial Technical Configuration for Development Infrastructure
(DI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 116 Initial
Technical Configuration for the Portal (Usage Types EPC and EP) . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . 117 Initial Technical
Configuration for BI Java . . . . . . . . . . . . . . . . . . . . .
. . . . . . 118 Configuring BI Java Information Broadcasting . . .
. . . . . . . . . . . . . . . . . . . . . 119 Process Chains:
Transporting Texts for the Alert Category . . . . . . . . . . . . .
. 119 Renaming initialPermissionsBI.xml.template . . . . . . . . .
. . . . . . . . . . . . . . . . 119 SAP System Security on Windows
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
120 Automatic Creation of Accounts and Groups . . . . . . . . . . .
. . . . . . . . . . . . . 122 Troubleshooting for Portal
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . 124 Deleting an SAP System or Single Instances . . . . . . . .
. . . . . . . . . . . . . . . . . . 125 Deleting the Oracle
Database Software . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . 128
2011-11-08
PUBLIC
7/180
Chapter 8 8.1 8.2 8.2.1 8.2.1.1 8.2.1.2 8.2.1.3 8.2.1.4 8.2.2
8.2.3 8.2.4 8.2.5 8.3 8.3.1 8.4 8.4.1 8.4.2 8.4.3 8.4.4 8.4.5 8.4.6
8.4.7 8.4.8 8.4.9 8.4.10 8.5 8.5.1 8.5.1.1 8.5.1.2 8.6 8.6.1 8.6.2
8.6.3 Chapter A A.1
High Availability with Microsoft Cluster Service . . . . . . . .
. . . . . . . . . . Installation Checklist for a High-Availability
System . . . . . . . . . . . . . . . . . . . Planning . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . System Configuration in MSCS . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP System
Components in an MSCS Configuration . . . . . . . . . . . . . . . .
. . Multiple SAP Systems In One MSCS Cluster . . . . . . . . . . .
. . . . . . . . . . . . . . Multiple SAP Systems In Multiple MSCS
Clusters . . . . . . . . . . . . . . . . . . . . . Enqueue
Replication Server in an MSCS Configuration . . . . . . . . . . . .
. . . . . Distribution of SAP System Components to Disks for MSCS .
. . . . . . . . . . . . Directories in an MSCS Configuration . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . IP Addresses
in an MSCS Configuration . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . Obtaining IP Addresses for MSCS . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . Preparation . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . Mapping Host Names to IP Addresses for
MSCS . . . . . . . . . . . . . . . . . . . . . . . Installation . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . Installing the Oracle 11g Fail Safe
Software . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the First Cluster Node . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . Creating the Oracle Fail Safe Group
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Database Instance . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . Setting Up a Shared Database
Directory in Oracle Home . . . . . . . . . . . . . . . . Adding the
Oracle Database Resource to the Fail Safe Group . . . . . . . . . .
. . . Configuring the Additional Cluster Node . . . . . . . . . . .
. . . . . . . . . . . . . . . . Additional Steps for the Oracle
Fail Safe Configuration . . . . . . . . . . . . . . . . .
Installing the Central Instance . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . Installing the Dialog Instance
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . Post-Installation . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . Post-Installation
Checks for Enqueue Replication Server . . . . . . . . . . . . . . .
. Checking the Status of the Enqueue Replication Server with ENSMON
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . Monitoring the Lock Table
During Failover with ENQT . . . . . . . . . . . . . . . .
Additional Information . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . Moving MSCS Groups or
Services and Applications . . . . . . . . . . . . . . . . . . . .
Rebooting During the Installation or Conversion for MSCS . . . . .
. . . . . . . . Starting and Stopping the SAP System in an MSCS
Configuration . . . . . . . . .
131 133 134 134 134 137 139 140 141 144 145 148 150 150 151 151
152 153 155 156 156 157 158 160 161 162 162 163 163 165 165 166
167
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . 169 Online
Information from SAP . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . 169
8/180
PUBLIC
2011-11-08
A.2
Using Powershell . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . 171
2011-11-08
PUBLIC
9/180
This page is left blank for documents that are printed on both
sides.
1 1.1
Introduction Before You Start
1 Introduction
This document describes how to install an SAP system based on
the Java application server of SAP NetWeaver 7.0 including
Enhancement Package 3 using the installation tool
SAPinst.CAUTION
Make sure you have read the Before You Start [page 11] section
before you continue with this installation guide.Constraints
You need to consider the following constraints before you start
your installation: Your operating system platform must be 64-bit.
The database must be Oracle 11.2.0, and higher.Naming
Conventions
SAP system refers to SAP system based on the application server
of SAP NetWeaver 7.0 including enhancement package 3. Java system
refers to SAP system based on the Java application server of SAP
NetWeaver 7.0 including Enhancement Package 3. diagnostics refers
to diagnostics in SAP Solution Manager. 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
AvailabilityOnly valid for: HA (MSCS) |
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.End of: HA (MSCS) |
1.1 Before You StartMake sure you have read the Master Guide for
your SAP Business Suite application or SAP NetWeaver application
before you continue with this installation guide.
2011-11-08
PUBLIC
11/180
1 1.2
Introduction New Features
The Master Guide is the central document leading you through the
overall implementation process for you SAP system installation. It
contains crucial information about the overall implementation
sequence, that is activities you have to perform before and after
the installation process described in this installation guide. You
can find a printed version of the Master Guide in your installation
package or you can download the latest version from SAP Service
Marketplace. The following table lists the Master Guides of the SAP
system applications for which you can use this installation guide,
along with the available quick link or path to the appropriate
download location under http://service.sap.com/instguides:Title
Internet Address
Master Guide - SAP Enhancement Package 6 for SAP
http://service.sap.com/erp-inst ERP 6.0 powered by SAP NetWeaver
Master Guide (Including Upgrade Information)
http://service.sap.com/srm-inst SAP Supplier Relationship
Management 7.0 Including SAP Enhancement Package 2 Master Guide
(Including Upgrade Information) http://service.sap.com/crm-inst SAP
Customer Relationship Management 7.0 Including SAP Enhancement
Package 2 http://service.sap.com/instguides Master Guide SAP Supply
Chain Management 7.0 Including SAP Enhancement Package 2 Powered by
Suite Applications SAP SCM SAP NetWeaver
SAP Business
1.2 New FeaturesThe 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
SAP Java Virtual Machine (SAP JVM)
You no longer require a Solution Manager Key for the
installation. The SAP Cryptographic Library SAPCRYPTO.SAR is now
available in the DBINDEP subfolder of the UC Kernel (folder K__U_)
medium and installed automatically by SAPinst. You do not have to
separately download SAPCRYPTO.SAR any longer. For more information,
see Basic SAP System Installation Parameters [page 35]. You no
longer have to download and install a Java Development Kit (JDK)
from another software vendor as a prerequisite for the installation
with SAPinst. The SAP JVM 4 is a Java Development Kit (JDK)
provided and supported by SAP. The SAP JVM is fully compliant to
the Java Platform Standard Edition (JDK) 1.4. It is available on
the
12/180
PUBLIC
2011-11-08
1 1.3 Area
Introduction SAP Notes for the Installation Description
Installation Master DVD and is installed automatically by
SAPinst when you start the installation. The diagnostics agent is
installed automatically with SAP JVM 6.
1.3 SAP Notes for the InstallationYou 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
1565346
SAP NetWeaver 7.03/Business Suite 7i2011: Windows
1565348
1431800 1144737 855498 73606 737368
1067221
Windows-specific information about the SAP system installation
and corrections to this documentation. SAP NetWeaver 7.03/Business
Oracle-specific information about the SAP system Suite 7i2011: Win
Oracle installation and corrections to this documentation 1431800
Oracle 11.2.0: Central Information about Oracle 11g with multiple
links Technical Note to notes on Oracle 11g Inst. NetWeaver 7.0
EHP3 Problems discovered after the publication of the Diagnostics
Agent installation installation guide or post-installation steps
Installation Prerequisite Checker SAP Software on UNIX, Windows,
and IBM i: Checking OS Dependencies Supported Languages and Code
Information on possible languages and language Pages combinations
in SAP systems Hardware requirements of Java Information on the
hardware requirements for Development Infrastructure usage type
Development Infrastructure (DI), which depends on the size of your
development team. Central Note for Heterogeneous This SAP Note and
its related SAP Notes describe Installation the released operating
system and database combinations for heterogeneous SAP systems
landscapes.Only valid for: SAP ERP | Only valid for: SAP ERP |
Only valid for: SAP ERP |
1258912End of: SAP ERP |
PLM Core 7.00 Release Notes and Information and references to
other notes about Information installing PLM Core 7.00 and
importing PLM Core End of: SAP ERP | 7.00 Support Packages.End of:
SAP ERP | Only valid for: SAP SCM | Only valid for: SAP SCM |
Only valid for: SAP SCM |
915367End of: SAP SCM |
TDL: Automatic activation of the Information about a TDL
function and the transaction data areas settings you have to make
during a system setup.End of: SAP SCM | End of: SAP SCM |
2011-11-08
PUBLIC
13/180
1 1.3
Introduction SAP Notes for the Installation TitleOnly valid for:
SAP SCM |
SAP Note NumberOnly valid for: SAP SCM |
DescriptionOnly valid for: SAP SCM |
1178483End of: SAP SCM |
SNC 7.0 Order Documents: Required CustomizingEnd of: SAP SCM
|
Information about Supply Network Collaboration order
documents.End of: SAP SCM |
14/180
PUBLIC
2011-11-08
2 2.1
Installation Options Covered by this Guide Central System
2 Installation Options Covered by this Guide
This section shows the installation options covered by this
guide. You have to decide what exactly you want to install because
the steps you have to perform vary according to the installation
option you choose. Central system [page 15]Only valid for: SAP
NetWeaver |
NOTE
You can install the following optional standalone units only as
a central system, but not as a distributed or high-availability
system: Application Sharing Server Java EE Adapter Engine Partner
Connectivity KitEnd of: SAP NetWeaver |
Distributed system [page 16] Only valid for: HA (MSCS) |
High-availability system [page 17]End of: HA (MSCS) |
You can install dialog instances [page 18] to an existing
system. You can install a host agent [page 19] separately.
2.1 Central SystemYou can install a central system on a single
host.Only valid for: SAP NetWeaver |
NOTE
You can install the following optional standalone units only as
a central system, but not as a distributed or high-availability
system: Application Sharing Server Java EE Adapter Engine Partner
Connectivity KitEnd of: SAP NetWeaver |
These are the following instances:
2011-11-08
PUBLIC
15/180
2 2.2
Installation Options Covered by this Guide Distributed
System
Central services instance for Java (SCS instance) Database
instance (DB instance) Central instance Additionally you can
install one or more dialog instances. For more information, see
Dialog Instance [page 18]. The following figure shows an example of
SAP instances in a central system.
Figure 1:
Central Java System
2.2 Distributed SystemIn a distributed system, every instance
can run on a separate host. These are the following instances:
Central services instance for Java (SCS instance) Database instance
(DB instance) Central instance Optionally you can install one or
more dialog instances. For more information, see Installation of a
Dialog Instance [page 18].Only valid for: SAP NetWeaver |
NOTE
You can install the following optional standalone units only as
a central system [page 15], but not as a distributed or
high-availability system: Application Sharing Server Java EE
Adapter Engine
16/180
PUBLIC
2011-11-08
2 2.3
Installation Options Covered by this Guide High Availability
System
Partner Connectivity KitEnd of: SAP NetWeaver |
Figure 2:
Distributed Java System
Only valid for: HA (MSCS) |
2.3 High Availability SystemFor 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
134].Only valid for: SAP NetWeaver |
NOTE
You can install the following optional standalone units only as
a central system [page 15], but not as a distributed or
high-availability system: Application Sharing Server Java EE
Adapter Engine Partner Connectivity KitEnd of: SAP NetWeaver | End
of: HA (MSCS) |
2011-11-08
PUBLIC
17/180
2 2.4
Installation Options Covered by this Guide Dialog Instance
2.4 Dialog InstanceYou 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: The host of any instance
of the existing SAP system On a dedicated hostNOTE
We do not recommend installing dialog instances on the SAP
global host. 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 43].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.Dialog Instance for a
Central System
The following figure shows dialog instances that are running on
dedicated hosts.
Figure 3:
Dialog Instance for a Central System
For more information, see Central System [page 15].
18/180
PUBLIC
2011-11-08
2 2.5
Installation Options Covered by this Guide Host Agent as a
Separate Installation
Dialog Instance for a Distributed System
The following figure shows dialog instances that are running on
dedicated hosts.
Figure 4:
Dialog Instance for a Distributed System
For more information, see Distributed System [page 16].Only
valid for: HA (MSCS) |
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 134].End
of: HA (MSCS) |
2.5 Host Agent as a Separate InstallationUsing the host agent
you can centrally monitor any host with the Alert Monitor or the
SAP NetWeaver 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: You want to manage a host
that does not have an SAP instance or component.
2011-11-08
PUBLIC
19/180
2 2.5
Installation Options Covered by this Guide Host Agent as a
Separate Installation
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 109] describes how to perform the
installation.
20/180
PUBLIC
2011-11-08
3 3.1
Planning Planning Checklist
3 Planning
3.1 Planning ChecklistThis section includes the planning steps
that you have to perform for the following installation options:
Central, distributed, or high-availability system Dialog instance
Detailed information about the steps is available in the relevant
chapter.Prerequisites
1. 2.
You have planned your SAP system landscape according to the
process sequence in the Master Guide. You have decided on your
installation option [page 15].Only valid for: SAP NetWeaver |
NOTE
You can install the following optional standalone units only as
a central system [page 15], but not as a distributed or
high-availability system:End of: SAP NetWeaver |
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. 2. 3. 4. 5. 6. 7. 8. You
check the hardware and software requirements [page 22] on each
host. You plan how to set up user and access management [page 34].
You identify basic SAP system installation parameters [page 35].
You decide whether you want to perform a domain or local
installation [page 43]. For the database installation, you decide
how to distribute your database components to disk [page 44]. You
decide on the transport host to use [page 46]. You decide if you
want to use Multiple Oracle Homes [page 47].Only valid for: HA
(MSCS) |
To install a high-availability system with Microsoft Cluster
Service (MSCS), you perform the MSCS-specific planning steps [page
133].End of: HA (MSCS) |
9.
You can continue with Preparation [page 49].
2011-11-08
PUBLIC
21/180
3 3.2
Planning Hardware and Software Requirements
Dialog Instance
1. 2. 3.
You check the hardware and software requirements [page 22] for
the installation host on which you want to install one or more
dialog instances. You identify basic SAP system installation
parameters [page 35]. You can now continue with Preparation [page
49].
3.2 Hardware and Software RequirementsYou 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. 2.
Check the Product Availability Matrix at
http://service.sap.com/pam for supported operating system releases.
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,
see Running the Prerequisite Checker Standalone [page 23].
Integrated in SAPinst (mandatory) during the installation process
For more information, see Running SAPinst [page 63].NOTE
For the most recent updates to the Prerequisite Checker, always
check SAP Note 855498. The hardware and software requirements
checklists for: Central system [page 24] Distributed system [page
26] Only valid for: HA (MSCS) |
High availability system with MSCS [page 28]End of: HA (MSCS)
|
3.
Dialog instance [page 32] Host agent as a separate installation
[page 32] If you want to install a production system, the values
provided by the Prerequisite Checker and the hardware and software
requirements checklists are not sufficient. In addition, do the
following: You use the Quick Sizer tool available at
http://service.sap.com/sizing.
22/180
PUBLIC
2011-11-08
3 3.2
Planning Hardware and Software Requirements
For more information about the Quick Sizer and available sizing
guides, see the Master Guide SAP NetWeaver 7.0 at
http://service.sap.com/installnw70 Planning .NOTE
If you want to install usage type Development Infrastructure
(DI), also check SAP Note 737368 for system requirements and
sizing. You contact your hardware vendor, who can analyze the load
and calculate suitable hardware sizing depending on: The set of
applications to be deployed How intensively the applications are to
be used The number of users
3.2.1 Running the Prerequisite Checker in Standalone Mode
(Optional)Before installing your SAP system, you can run the
Prerequisite Checker in standalone mode to check 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
the Prerequisite Checker and checks the hardware and software
requirements in the background.Prerequisites
You have prepared the installation master DVD on the required
installation host [page 55].Procedure
1. 2. 3.
You start SAPinst [page 63]. On the Welcome screen, choose
Software Life-Cycle Options Additional Preparations Prerequisites
Check . 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 and choose F1 in SAPinst. When you have
finished, the Parameter Summary screen appears summarizing all
parameters you have entered and want to have checked. If you want
to make a change, select the relevant parameters and choose Revise.
To start the prerequisites check, choose Next.
4.
2011-11-08
PUBLIC
23/180
3 3.2
Planning Hardware and Software Requirements
Result
The Prerequisite Checker Results screen displays the results
found. If required, you can also check the results in file
prerequisite_checker_results.html, which you can find in the
installation directory.
3.2.2 Requirements for a Central SystemIf you want to install a
central system, where all instances reside on one host, this host
must meet the following requirements:NOTE
The listed values are sufficient for development systems or
quality assurance systems but not for production systems. For
up-to-date information on the released and supported operating
system and database versions for your SAP product and database, see
the Product Availability Matrix (PAM) at http://service.sap.com/pam
.Hardware Requirements for a Central System Hardware Requirement
Requirement How to Check
Minimum disk space
Database Software: 2 to 5 GB SAP system files (not including
paging file): 5 GB (x64) 8 GB (IA64) SAP database files (not
including paging file): 2 GB Only valid for: SAP CRM;SAP ERP;SAP
NetWeaver;SAP SCM;SAP SRM | Up to 2 GB for each usage type or
software unit you want to install.End of: SAP CRM;SAP ERP;SAP
NetWeaver;SAP SCM;SAP SRM |
To check disk space: 1. Choose Start All Programs Administrative
Tools Storage Computer Management Disk Management . 2. Right-click
the drive and choose Properties.
Minimum RAM
4.3 GB of temporary disk space for every required installation
medium that you have to copy to a local hard disk 4 GB To check
RAM: Choose Start Control PanelNOTE
System .
Paging file size
For more information, see SAP Note 1518419.
Windows Server 2008 R2: If System is not visible, change View
by: from Category into Large icons. To check paging file size: 1.
Choose Start Control Panel System .
24/180
PUBLIC
2011-11-08
3 3.2
Planning Hardware and Software Requirements Requirement How to
Check NOTE
Hardware Requirement
2. 3. 4.
Windows Server 2008 R2: If System is not visible, change View
by: from Category into Large icons. Choose Advanced system
settings. In section Performance, select Settings... Advanced . If
required, in section Virtual memory, choose Change.NOTE
Do not select Automatically managed paging file size for all
drives. Processing Units The number or physical or virtual
processing units usable by the operating system image must be equal
or greater than 2 for application server instances and database
instances. For an SCS instance running on a separate host, 1
physical or virtual processing units usable by the operating system
image might be sufficient. Examples for processing units are
Processor Cores or Hardware Threads (Multithreading). In a
virtualized environment you must take care that adequate processor
resources are available to support the workloads of the running SAP
systems.
Suitable backup system
Software Requirements for a Central System Software Requirement
Requirement How to Check
Windows operating system
To check your Windows version: 64-bit version of one of the
following Windows Server Editions: 1. Choose Start All Programs
Accessories Command Prompt Windows Server 2008 (R2) 2. Enter the
command winver Standard Edition Windows Server 2008 (R2) Enterprise
Edition Windows Server 2008 (R2) Datacenter Edition Windows Server
2008 (R2) for Itanium-Based Systems EditionCAUTION
Make sure that you install the English language pack so that
2011-11-08
PUBLIC
25/180
3 3.2
Planning Hardware and Software Requirements Requirement How to
Check
Software Requirement
Database software
your support requests can be handled quickly. For any version of
Windows Server, you need the latest supported service pack Database
server software for Oracle 11g Current Oracle patches, if
available.
3.2.3 Requirements for a Distributed SystemThis section provides
information about the hardware and software requirements in a
distributed system, where the SAP instances can reside on different
hosts. The tables show the requirements for the: Central services
instance Database instance Central instance Dialog instance
(optional)NOTE
The listed values are sufficient for development systems or
quality assurance systems but not for production systems. If you
install several SAP instances on one host, you need to add up the
requirements. For up-to-date information on the released and
supported operating system versions for your SAP product and
database, see the Product Availability Matrix (PAM) at http://
service.sap.com/pam.Hardware Requirements for a Distributed System
Hardware Requirement Requirement How to Check
Minimum disk space
To check disk space: Database software: 2 to 5 GB 1. Choose
Start All Programs Administrative Tools Storage Central services
instance (SCS) (not including paging file): Computer Management
Disk 5 GB (x64) Management . 8 GB (IA64) 2. Right-click the drive
and choose Properties. Database instance (not including paging
file): 2 GB Central instance (not including paging file): 5 GB
(x64) 8 GB (IA64)
26/180
PUBLIC
2011-11-08
3 3.2
Planning Hardware and Software Requirements Requirement How to
Check
Hardware Requirement
Minimum RAM
In addition you require 4 GB (x64), or 8 GB (IA64) per
additional platform. In addition you require 1.5 GB for the
diagnostics agent Up to 2 GB for each usage type or software unit
you want to install. Dialog instance (optional) (not including
paging file): 2.5 GB (x64) 5 GB (IA64) In addition you require 1.5
GB for the diagnostics agent Temporary disk space for every
required installation medium that you have to copy to a local hard
disk: 4.3 GB 4 GB To check RAM: Choose Start Control PanelNOTE
System .
Paging file size
For more information, see SAP Note 1518419.
Windows Server 2008 R2: If System is not visible, change View
by: from Category into Large icons. To check paging file size: 1.
Choose Start Control Panel System .NOTE
2. 3. 4.
Windows Server 2008 R2: If System is not visible, change View
by: from Category into Large icons. Choose Advanced system
settings. In section Performance, select Settings... Advanced . If
required, in section Virtual memory, choose Change.NOTE
Do not select Automatically managed paging file size for all
drives. Processing Units The number or physical or virtual
processing units usable by the operating system image must be equal
or greater than 2 for application server instances and database
instances. For an SCS instance running on a separate host, 1
physical or virtual processing units
2011-11-08
PUBLIC
27/180
3 3.2
Planning Hardware and Software Requirements Requirement How to
Check
Hardware Requirement
usable by the operating system image might be sufficient.
Examples for processing units are Processor Cores or Hardware
Threads (Multithreading). In a virtualized environment you must
take care that adequate processor resources are available to
support the workloads of the running SAP systems. Suitable backup
systemSoftware Requirements for a Distributed System Software
Requirement Requirement How to Check
Windows operating system
64-bit version of one of the following Windows Server Editions:
Windows Server 2008 (R2) Standard Edition Windows Server 2008 (R2)
Enterprise Edition Windows Server 2008 (R2) Datacenter Edition
Windows Server 2008 (R2) for Itanium-Based Systems
EditionCAUTION
To check your Windows version: 1. Choose Start All Programs
Accessories Command Prompt 2. Enter the command winver
Database software
Make sure that you install the English language pack so that
your support requests can be handled quickly. For any version of
Windows Server, you need the latest supported service pack Database
instance: Database server software for Oracle 11g Current Oracle
patches, if available.
Only valid for: HA (MSCS) |
3.2.4 Requirements for a High-Availability SystemGeneral
Requirements
Check that your cluster hardware is certified for Windows Server
2008 (R2) and has the Windows Server 2008 (R2) logo. You must
validate your failover cluster configuration by running the
Validate a Configuration Wizard, which is included in the Failover
Cluster Management snap-in. The Failover Cluster Validation Report
must not show any warnings and errors. The MSCS nodes of the
cluster must be connected by a private and public network: The
public network enables communication from the MSCS nodes of the
cluster to other resources in the local area network (LAN).
28/180
PUBLIC
2011-11-08
3 3.2
Planning Hardware and Software Requirements
The private network enables internal communication between the
MSCS nodes. In particular, it enables the Cluster Service running
on all MSCS nodes to regularly exchange messages on the state of
the MSCS nodes so that the failure of resources is quickly
detected. Each of the MSCS nodes in the cluster must have its own
local disks and have access to shared disks that can be reached by
the MSCS nodes via a shared bus. All software except the Windows
operating system, the Oracle home directory, and the MSCS software
is stored on the shared disks. One of the shared disks must be used
exclusively by the quorum (if a single quorum device cluster is
used) that stores the cluster registry and records information
about the state of the cluster. You require at least four shared
disks. For more information about the distribution of components to
local and shared disk, see Distribution of SAP System Components to
Disks for MSCS [page 141]. All disk controllers must be able to
support hardware-based RAID.CAUTION
You cannot use a host with a domain controller as an MSCS
cluster node.Hardware and Software Requirements
The following tables show the hardware and software requirements
for the: Central services instance (SCS) Database instance Enqueue
Replication Server instance (ERS) Central instance Dialog instance
Diagnostics agentNOTE
The listed values are sufficient for development systems or
quality assurance systems but not for production systems. If you
install several SAP instances on one host, you need to add up the
requirements. If you install multiple SAP systems in one MS
cluster, make sure that together with your hardware partner you
have set up the correct sizing for your system configuration. For
up-to-date information on the released and supported operating
system versions for your SAP product and database, see the Product
Availability Matrix (PAM) at http:// service.sap.com/pam.Hardware
Requirements for a High-Availability System Hardware Requirement
Requirement How to Check
Minimum disk space
Database Software: 2 to 5 GB Central services instance (SCS)
To check disk space: 1. Choose Start All Programs Administrative
Tools Storage
2011-11-08
PUBLIC
29/180
3 3.2
Planning Hardware and Software Requirements Requirement How to
Check
Hardware Requirement
Minimum RAM
Computer Management Disk (not including paging file): Management
. 5 GB (x64) 8 GB (IA64) 2. Right-click the disk and choose
Properties. Database instance (not including paging file): 2 GB
Enqueue replication server instance (ERS) (not including paging
file): 5 GB (x64) 8 GB (IA64) Central instance (not including
paging file): 2.5 GB (x64) 5 GB (IA64) In addition you require 4 GB
(x64), or 8 GB (IA64) per additional platform. In addition you
require 1.5 GB for the diagnostics agent Up to 2 GB for each usage
type or software unit you want to install. Dialog instance (not
including paging file): 2.5 GB (x64) 5 GB (IA64) In addition you
require 1.5 GB for the diagnostics agent Temporary disk space for
every required installation medium that you have to copy to a local
hard disk: 4.3 GB 4 GB To check RAM: Choose Start Control Panel
System .NOTE
Paging file size
For more information, see SAP Note 1518419
Windows Server 2008 R2: If System is not visible, change View
by: from Category into Large icons. To check paging file size: 1.
Choose Start Control Panel System .NOTE
2.
Windows Server 2008 R2: If System is not visible, change View
by: from Category into Large icons. Choose Advanced system
settings.
30/180
PUBLIC
2011-11-08
3 3.2
Planning Hardware and Software Requirements Requirement How to
Check
Hardware Requirement
3. 4.
In section Performance, select Settings... Advanced . If
required, in section Virtual memory, choose Change.NOTE
Do not select Automatically managed paging file size for all
drives. You must adjust the size of the paging file on all MSCS
nodes. Processing Units For an SCS instance running on a separate
host, 1 physical or virtual processing units usable by the
operating system image might be sufficient. Examples for processing
units are Processor Cores or Hardware Threads (Multithreading). In
a virtualized environment you must take care that adequate
processor resources are available to support the workloads of the
running SAP systems.
Suitable backup system
Software Requirements for a High Availability System Software
Requirement Requirement How to Check
Windows operating system
To check your Windows version: 64-bit version of one of the
following Windows Server Editions: 1. Choose Start All Programs
Accessories Command Prompt Windows Server 2008 (R2) 2. Enter the
command winver Enterprise Edition Windows Server 2008 (R2) NOTE
Datacenter Edition You must add the operating system Windows Server
2008 (R2) for feature Failover Clustering on all MSCS Itanium-Based
Systems nodes. EditionCAUTION
Database software
Make sure that you install the English language pack so that
your support requests can be handled quickly. For any version of
Windows Server, you need the latest supported service pack Database
instance: Oracle 11g database server software
2011-11-08
PUBLIC
31/180
3 3.2
Planning Hardware and Software Requirements Requirement How to
Check
Software Requirement
Current Oracle patches, if available. Oracle Fail Safe
softwareEnd of: HA (MSCS) |
3.2.5 Requirements for the Dialog InstanceFor more information
about the hardware and software requirements for the dialog
instance, see one of the following sections: Requirements for a
Distributed System [page 26] Only valid for: HA (MSCS) |
Requirements for a High-Availability System [page 28]End of: HA
(MSCS) |
3.2.6 Requirements for the Host Agent as a Separate
InstallationIf you want to install the host agent separately, the
installation host has to meet the following hardware and software
requirements:CAUTION
For up-to-date information on the released and supported
operating system versions for your SAP product and database, see
the Product Availability Matrix (PAM) at:http://service.sap.com/pam
Hardware Requirements for the Host Agent Hardware Requirement
Requirement How to Check
Minimum disk space:
Minimum RAM:
To check disk space: Host agent: 80 MB 1. Choose Start All
Programs Administrative Tools Storage Temporary disk space for
every required installation medium that Computer Management Disk
you have to copy to a local hard disk: Management . 4.3 GB 2.
Right-click the disk and choose Properties. 40 MB To check RAM:
Choose Start Control Panel System .NOTE
Windows Server 2008 R2: If System is not visible, change View
by: from Category into Large icons.
32/180
PUBLIC
2011-11-08
3 3.2
Planning Hardware and Software Requirements Requirement How to
Check
Hardware Requirement
Paging file size:
For more information, see SAP Note 1518419.
To check paging file size: 1. Choose Start Control Panel System
.NOTE
2. 3. 4.
Windows Server 2008 R2: If System is not visible, change View
by: from Category into Large icons. Choose Advanced system
settings. In section Performance, select Settings... Advanced . If
required, in section Virtual memory, choose Change.NOTE
Do not select Automatically managed paging file size for all
drives. Processing Units The number or physical or virtual
processing units usable by the operating system image must be equal
or greater than 2. Examples for processing units are Processor
Cores or Hardware Threads (Multithreading). In a virtualized
environment you must take care that adequate processor resources
are available to support the workloads of the running SAP systems.
Suitable backup system Software Requirements for the Host Agent
Software Requirement Requirement How to Check
Windows operating system:
To check your Windows version: 64-bit version of one of the
following Windows Server Editions: 1. Choose Start All Programs
Accessories Command Prompt . Windows Server 2008 (R2) Standard
Edition 2. Enter the command winver. Windows Server 2008 (R2)
Enterprise Edition Windows Server 2008 (R2) Datacenter Edition
Windows Server 2008 (R2) for Itanium-Based Systems
EditionCAUTION
Make sure that you install the English language pack so that
your support requests can be handled quickly.
2011-11-08
PUBLIC
33/180
3 3.3
Planning Planning User and Access Management Requirement How to
Check
Software Requirement
Database software:
For any version of Windows Server, you need the latest supported
service pack
3.3 Planning User and Access ManagementYou have to plan how you
want to configure user and access management for your SAP system to
be installed. Before you add a newly installed SAP system to your
system landscape, you must decide which kind of user management you
want to use: Use the database of AS Java. Use an external ABAP
system as the data source for user data. Use an LDAP directory as
the data source for user data. You cannot configure the AS Java to
access an LDAP directory and an AS ABAP as the data source
simultaneously. The AS Java can also use its own database as the
data source.ProcedureUsing the Database of AS Java
You install your SAP system as described in this installation
guide. During the installation, you specify the Java database as
data source for the User Management Engine (UME) (see Basic SAP
System Installation Parameters [page 35]): During the installation,
the SAP system is automatically configured to use the Java database
as data source for the UME. After the installation has finished,
you can still change the user management configuration. For more
information, see Configuring User Management [page 82].Using an
External SAP ABAP System as Source for User Data.
1. 2.
3.
You prepare the external SAP ABAP system as described in
Preparing an External ABAP System as Source for User Data [page
105]. You install your SAP system as described in this installation
guide. During the installation, you specify an external ABAP system
as data source for the User Management Engine (UME) (see Basic SAP
System Installation Parameters [page 35]). After the installation
has finished, you cannot change this configuration of the UME any
more. For more information, see Configuring User Management [page
82].
Using an LDAP directory as Source for User Data
1. 2.
You install your SAP system as described in this installation
guide. Configure the user management of the newly installed SAP
system to use and LDAP directory.
34/180
PUBLIC
2011-11-08
3 3.4
Planning Basic SAP System Installation Parameters
For more information, see Configuring User Management [page
82].More Information
For more information about configuring the user management of
your SAP system to be installed, see the SAP Library at:
http://help.sap.com/nw703 Application Help SAP LIbrary: 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
3.4 Basic SAP System Installation ParametersSAPinst prompts for
input parameters during the Define Parameters phase of the
installation. You can install your SAP system either in Typical or
Custom mode: Typical If you choose Typical, you perform the
installation with default settings. This means that you only have
to respond to a small selection of prompts including at least the
following, which are described in the corresponding tables below:
SAP System ID and Database Connectivity Parameters SAP system
profile directory only for systems with instances on separate hosts
Master password System Landscape Directory (SLD) destination If you
want to change any of the default settings, you can do so on the
Parameter Summary screen. Custom If you choose Custom, you are
prompted for all parameters. At the end, you can still change any
of these parameters on the Parameter Summary
screen.RECOMMENDATION
If you want to configure the user management of your SAP system
for an external ABAP system, as described in Preparing an External
ABAP System as Source for User Data [page 105], we recommend that
you select the Custom parameter mode. When you do this, you are
prompted to select the appropriate option and to enter the required
parameters If you do not choose the Custom parameter mode, you have
to change the required parameters on the Parameter Summary
screen.NOTE
You cannot change from Custom to Typical mode or from Typical to
Custom mode on the Parameter Summary screen. The following tables
list the basic system parameters that you need to specify before
installing your SAP system:
2011-11-08
PUBLIC
35/180
3 3.4
Planning Basic SAP System Installation Parameters
SAP System Parameters SAP System Database Parameters Diagnostics
Agent Parameters For all other installation parameters, use theSAP
System Parameters Parameters Description
F1
help in the SAPinst screens.
SAP System ID
The SAP System ID identifies the whole SAP system.CAUTION
Choose your SAP system ID carefully. You cannot change the SAP
system ID after the installation. Make sure that your SAP system
ID: Is unique throughout your organization. Do not use an existing
when installing a new SAP system.EXAMPLE
If you have already installed an ABAP system and you want to
install a new Java system on the same host, make sure that you
enter a that is different from the of the existing ABAP system.
Consists of exactly three alphanumeric characters Contains only
uppercase letters Has a letter for the first character Does not
include any of the following, which are reserved IDs:ADD ALL AMD
AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM
INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN
RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR
VAR
SAP System Instance Numbers
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. Technical identifier for internal
processes. It consists of a two-digit number from 00 to 97. The
instance number must be unique on a host. That is, if more than one
SAP instance is running on the same host, these instances must be
assigned different numbers. If you do not enter a specific value,
the instance number is set automatically to the next free and valid
instance number that has not yet been assigned to the SAP system to
be installed or to SAP systems that already exist on the
installation host. To find out the instance numbers of SAP systems
that already exist on the installation host, look for
subdirectories ending with of local \usr\sap\ directories. The
value is the number assigned to the instance. For more information,
see SAP Directories [page 94].CAUTION
Do not use 43, and 89 for the instance number because: 43 is
part of the port number for MSCS 89 is part of the port number for
Windows Terminal Server Master Password Common password for all
users created during the installation: Operating system users (for
example adm, SAPService)
36/180
PUBLIC
2011-11-08
3 3.4
Planning Basic SAP System Installation Parameters Description
CAUTION
Parameters
If you did not create the operating system users manually before
the installation, SAPinst creates them with the common master
password. In this case, make sure that the master password meets
the requirements of your operating system. Java users (for example
Administrator) Secure Store key phrase For more information, see
table line Key Phrase for Secure Store Settings.NOTE
If a user already exists, you are prompted to confirm the
password for this user. Password policy The master password: Must
be 8 to 14 characters long Must contain at least one letter in
uppercase (A-Z) Must contain at least one letter in lowercase (a-z)
Must contain at least one digit (0-9) Must not contain \
(backslash) and " (double quote) Depending on the installation
option, additional restrictions might apply (for example, the
master password must not contain the name of a Java user created
during the installation). Message Server PortCAUTION
The message server port number must be unique for the SAP system
on all hosts. If there are several message port numbers on one
host, all must be unique. Port number of the SAP Message Server: If
you do not specify a value, the default port number is used. The
SCS instance profile contains the configuration for the Java
message server. The Java message server port uses the parameter
rdisp/msserv_internal with default value 39, where is the instance
number of the SCS message server instance. For more information
about the parameters used for message server ports, see SAP Note
821875. This is a random word or phrase that is used to encrypt the
secure store. The Java EE engine uses this phrase to generate the
key that is used to encrypt the data. The uniqueness of the phrase
you use contributes to the uniqueness of the resulting
key.RECOMMENDATION
Key Phrase for Secure Store Settings
Use a long key phrase that cannot be guessed easily. Use both
uppercase and lowercase letters in the phrase and include special
characters.NOTE
DNS Domain Name for SAP System
If you choose Typical mode, SAPinst sets the master password for
the key phrase. In this case, make sure that you replace the master
password with the required unique key phrase either in the
Parameter Summary screen or after the installation has finished. If
you want to use HTTP-based URL frameworks such as Web Dynpro
applications, you have to specify the DNS domain name for the SAP
system. The DNS Domain Name is used to calculate the Fully
Qualified Domain Name (FQDN), which is configured in profile
parameter SAPLOCALHOSTFULL. FQDN is the fully qualified domain name
for an IP address. It consists of the host name and the domain
name:
2011-11-08
PUBLIC
37/180
3 3.4
Planning Basic SAP System Installation Parameters
Description.
Parameters
The DNS Domain Name is needed to define the URLs for the ABAP
and Java application servers. It is appended to the server name to
calculate the FQDN. For more information, see SAP Note
654982.EXAMPLE
Path toSAPCRYPTO.SAR
Password of Operating System Users
If your application server host is called kirk.wdf.sap.com, the
DNS Domain Name is wdf.sap.com. The SAP Cryptographic Library is
required to enable Secure Sockets Layer (SSL) encryption of HTTP
connections. In most cases it is installed automatically from the
kernel medium. In case it is not installed automatically and you
are prompted for it during the installation, you can download it as
described in SAP Note 455033. This software product is subject to
export control regulations in Germany as the country of origin and
import regulations of your own country. SAP may not yet have a
corresponding export license for your user or company. Contact the
contract department in your local SAP company. To download the SAP
Cryptographic Software from the SAP Service Marketplace, you need a
customer user ID. Before any transfer of these software products to
persons, companies or other organizations outside your company, in
particular in the case of any reexport of the software products,
authorization is required from the German export control
authorities. This might also be required from your responsible
national export control authorities. This also applies to transfers
to affiliated companies. Corresponding laws and regulations in the
recipient country may also exist which restrict the import or the
use of these software products. The passwords of the operating
system users must comply with the Windows password policy. SAPinst
processes the passwords of operating system users as follows: If
the operating system users do not exist, SAPinst creates the
following users: adm This user is the SAP system administrator user
and is a member of the local Administrators group. SAPService This
user is the Windows account to run the SAP system and is not a
member of the local Administrators group. sapadm The host agent
user sapadm is used for central monitoring services. SAPinst
creates this user by default as a local user without being a member
of the local Administrators group. If required, you can change this
user to become a domain user on the parameter summary screen. For
more information, see Performing a Domain Installation Without
Being a Domain Administrator [page 97]. For security reasons,
however, SAP strongly recommends to create this user as a local
user. adm This user is dedicated to the diagnostics agent
installation with sufficient authorization to manage the agent. It
is created on the central instance host and on every dialog
instance host. SAPinst creates this user by default as a local
user. If required, you can change this user to become a domain user
on the parameter summary screen. For security reasons, however, SAP
strongly recommends to create this user as a local user.
38/180
PUBLIC
2011-11-08
3 3.4
Planning Basic SAP System Installation Parameters
Description
Parameters
SAPinst sets the master password for these users by default. You
can overwrite and change the passwords either by using the
parameter mode Custom or by changing them on the parameter summary
screen. If the operating system users already exist, SAPinst
prompts you for the existing password, except if the password of
these users is the same as the master password.NOTE
This does not apply if the adm user already exists. SAPinst
prompts you for the password even if the password of this user is
the same as the master password.CAUTION
UME Configuration
Make sure that you have the required user authorization [page
52] for these accounts before you start the installation with
SAPinst. You are prompted for how to configure the UME during the
input phase of the installation. You can choose between the
following options: Use Java database (default) If you choose this
option, administrators can manage users and groups with the UME Web
admin tool and SAP NetWeaver Administrator only. For LDAP, use this
configuration for the installation and change the configuration to
LDAP after the installation (see Configuring User Management to Use
an LDAP Directory [page 82]). Use ABAP If you choose this option,
administrators can manage users with the transaction SU01 on the
external ABAP system, and, depending on the permissions of the
communication user, also with the UME Web admin tool and SAP
NetWeaver Administrator. Make sure that you have created the
required users manually on the external ABAP system before you
choose this option (see Preparing an External ABAP System as Source
for User Data [page 105]).RECOMMENDATION
Select the Custom parameter mode. When you do this, you are
prompted to select the appropriate option and to enter the required
parameters. If you do not choose the Custom parameter mode, you
have to change the required parameters on the Parameter Summary
screen.Only valid for: SAP NetWeaver |
NOTE
If you want to install Adapter Engine (Java EE) as an optional
standalone unit, we recommend that you configure the User
Management Engine (UME) for the ABAP UME of the SAP NetWeaver
Process Integration (PI) system.End of: SAP NetWeaver |
For more information about supported UME data sources and change
options, see SAP Note 718383. Using the Java Database: Java SAPinst
sets the user name Administrator and the master password by
default. Administrator This user has administrative permissions for
user management. User and Password
2011-11-08
PUBLIC
39/180
3 3.4
Planning Basic SAP System Installation Parameters
Description
Parameters
Java Guest User SAPinst sets the user name Guest and the master
password by default. and Password This user is used for anonymous
access. Using an External ABAP System Parameters for the ABAP
Connection: Application This is the instance number on the
application server of the central ABAP system to which Server
Number you want to connect the Application Server Java. To find out
the number on the host of the central instance, look under the SAP
directory usr/sap//DVEBMGS. The value is the number assigned to the
SAP system. Application This is the host name of the relevant
application server instance. Server Host To find out the host name,
enter hostname at the command prompt of the host running the
central instance. Communication This is the name and password of
the existing ABAP communication user. You must have User and
created this user manually on the external ABAP system. Password
SDM Password This user is used for the Software Deployment Manager
(SDM). SAPinst sets the master password by default. Using an
External ABAP System Parameters for the Application Server Java
Connection: Administrator This is the name and password of the
administrator user that you must have created on the User and
external ABAP system. Password This user has administrative
permissions for user management. Administrator The role
SAP_J2EE_ADMIN must exist on the external ABAP system. Role Guest
User and This is the name and password of the guest user that you
must have created on the external Password ABAP system. This user
is used for anonymous access. Guest Role The role SAP_J2EE_GUEST
must exist on the external ABAP system. Communication This is the
name and password of the existing ABAP communication user. You must
have User and created this user manually on the external ABAP
system. Password SDM Password This user is used for the Software
Deployment Manager (SDM). SAPinst sets the master password by
default. SLD Destination The System Landscape Directory (SLD) is
designed for registering the systems (along with the installed
software) of your whole system landscape. The usual case is to
configure one SLD for your complete system landscape. You can
choose between the following options: Register in existing central
SLD Choose this option to register the SAP system you are
installing in an existing SAP System Landscape Directory (SLD) by
specifying the SLD connection parameters listed below in this
table. No SLD destination Choose this option if you do not want to
register the SAP system you are installing in an existing SAP
System Landscape Directory (SLD). You then have to configure the
SLD destination manually after the installation with SAPinst has
finished. Configure a local SLD Choose this option if you want to
have a local SLD on the SAP Java system that you are installing.
Then the SAP system you are installing is the SLD server.
40/180
PUBLIC
2011-11-08
3 3.4
Planning Basic SAP System Installation Parameters Description
NOTE
Parameters
The usual case is to configure one central SLD for your whole
system landscape outside the SAP Solution Manager. However, we
strongly recommend that you check the Master Guide for
recommendations about which option to choose. Register in existing
central SLD SLD HTTP Host The host name of the existing central
SLD. SLD HTTP Port The HTTP port of the existing central SLD. The
following naming convention applies: 500.EXAMPLE
SLD Data Supplier User and password SLD ABAP API The existing
SLD ABAP API user and password of the existing central SLD User and
password Configure a local SLD SLD Data Specify the name of the SLD
Data Supplier user to be created. This user is used to send the
Supplier User self-registration data of your system to the SLD. and
passwordRECOMMENDATION
If the instance number of your Java system is 01, the SLD HTTP
Port is 50100. The existing SLD Data Supplier user and password of
the existing central SLD
Object Server Name
We recommend that you name this user SLDDSUSER The Object Server
Name together with the CIM namespace identifies the absolute
location of your System Landscape Directory. If you do not have a
prefix reserved on SAP Market Place for Object Server Name, or if
you just want to install a test or development system, enter the
central instance host of your system. For more information about
the Object Server Name parameter, see SAP Note 935245.
SAP System Database Parameters Parameters Description
Database ID
The identifies the database instance. SAPinst prompts you for
the when you are installing the database instance. The can be the
same as the .CAUTION
Choose your database ID carefully. Renaming is difficult and
requires that you 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:
2011-11-08
PUBLIC
41/180
3 3.4
Planning Basic SAP System Installation Parameters DescriptionADD
ALL AMD AND ANY ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID
IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD
PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE
USR7 VAR
Parameters
Database schema, Passwords
The Java database schema is named SAPDB. Default name is
SAPSR3DB.RECOMMENDATION
Oracle parameters
Database Instance RAM Oracle Listener Name, Oracle Listener
Port
Tablespaces, Datafiles
Choose a that is different from your . It might cause problems
when you copy a system where is the same as , and the
databasespecific method used for the copy does not allow you to
rename the database schemas. In certain situations, you might
create a system copy with a new , but where the database schema has
the old . This is not a technical problem, but might confuse the
system administrator. ORACLE_HOME SAPDATA drives Drives for
redolog, archives (oraarch), and saptraces For more information
about the distribution of files, see Distribution of SAP System
Components to Disks [page 44] The RAM that is required for the
database instance installation. The default value used by SAPinst
is 50 percent of the entire RAM. If you install the database
instance on a host where no other Oracle database is installed, you
normally do not have to change the default values for Listener Name
and Listener Port. If you install the database instance on a host
where already another Oracle database is installed you have the
following options: If you install it in the same Oracle home, you
use the default values for Listener Name and Listener Port. If you
install it in a different Oracle home, you specify an unused
Listener Name and Listener Port for the new Oracle Listener. All
dialog instances of an SAP system must use the same Listener Port
than the database instance. An Oracle database consists of one or
more logical storage units called tablespaces, which collectively
store all of the database's data. Each tablespace in an Oracle
database consists of one or more files called datafiles, which are
physical structures that conform to the operating system in which
Oracle is running. MaxDatafileSize is the initial size of the
tablespace datafile and its mapping to the new tablespace layout
while importing the external file DBSIZE.XML.
42/180
PUBLIC
2011-11-08
3 3.5
Planning Domain or Local Installation Description
Parameters
SAPinst prompts you to enter MaxDatafileSize in MB: 0: Datafile
size defined in DBSIZE.XML is not changed. 2000: Default datafile
size. 10000: Maximum datafile size.Diagnostics Agent Parameters
The diagnostics agent is installed automatically with the SAP
system.Parameters Description
System ID of the Diagnostics Agent
SAPinst sets the system ID of the diagnostics agent, , to DAA by
default. If DAA is already used, SAPinst assigns another default
system ID. You can overwrite the default system ID as
required.CAUTION
Choose the carefully. Renaming is difficult and requires you to
reinstall the diagnostics agent. Make sure that the : Either does
not yet exist on the local installation host or does already exist
but was only used for a diagnostics agent installation Consists of
exactly three alphanumeric characters Contains only uppercase
letters Has a letter for the first character Does not include any
of the following, which are reserved IDs:ADD ALL AMD AND ANY ARE
ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT KEY LOG
LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW
SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR
Instance Number of the Diagnostics Agent
Technical identifier for internal processes for the diagnostics
agent, consisting of a two-digit number from 00 to 97. Default is
97. If 97 is already used for an instance number, the diagnostics
agent instance number is set automatically to the next free and
valid instance number. The instance number is used to specify the
name of the diagnostics agent instance directory that SAPinst
automatically creates during the installation. The directory of the
diagnostics agent instance is called SMDA. For more information,
see SAP Directories [page 94]. The same restrictions apply as in
Instance Number of the SAP System (see above).
3.5 Domain or Local InstallationBefore you install the SAP
system, you have to decide whether you want to perform a domain or
local installation, since this affects how the user account
information is stored and accessed.
2011-11-08
PUBLIC
43/180
3 3.6
Planning Distribution of SAP System Components to Disks
For more information about the differences between a local and
domain installation, go to Start Help and Support and search for
What is the difference between a domain and a workgroup?.Domain
Installation
In a domain installation, the user account information is stored
centrally in one database on the domain controller and is
accessible to all hosts in the system. You have to perform a domain
installation if one of the following applies: You install a system
distributed over several hosts. Only valid for: HA (MSCS) |
You install a high-availability system with MSCS.End of: HA
(MSCS) |
You use a common transport host for several SAP systems running
on different computers.Local Installation
In a local installation, all Windows account information is
stored locally on one host and is not visible to any other hosts in
the system. If the SAP system is to run on a single machine
(central system), you can perform a local installation.NOTE
If your SAP system was installed as a local installation and you
want to later change to a domain installation, you must perform a
homogeneous system copy. For more information, see the
documentation System Copy for SAP Systems based on SAP NetWeaver
at: http://service.sap.com/instguides More Information
Required User Authorization for Running SAPinst [page 52]
3.6 Distribution of SAP System Components to DisksWhen you
install the SAP system, the main directories required for the
system are automatically created. However, during the installation
procedure, SAPinst prompts you to enter drive letters for the main
components of the system. This gives you the opportunity to
distribute components to disks in the system as you wish. How you
do this significantly affects system throughput and data security,
and must therefore be carefully planned. The best distribution
depends on your specific environment and must take into
consideration factors such as the size of the components involved,
security requirements, and the expected workload. When you work out
the assignment of components to disks, you first need to obtain an
overview of the main components and their corresponding
directories. Then, on the basis of sample configurations and the
recommendations provided in this documentation, you can decide
which assignment is best for your particular system.
44/180
PUBLIC
2011-11-08
3 3.6
Planning Distribution of SAP System Components to Disks
SAP systems are normally installed on RAID arrays that ensure
data redundancy. This documentation therefore focuses on RAID
subsystems and drives.Minimal Configuration
The following figure illustrates an example for a disk
configuration for a small test or demo system. Since security and
performance play a less crucial role in this type of system, many
different configurations are feasible.CAUTION
Use the illustrated configuration exclusively for test or demo
systems. It is unsuitable for production systems because it only
minimally satisfies security and performance requirements.
Figure 5:
Minimal Configuration
Distribution of Directories to Disks Disk
Directories\ORACLE\\1120 (Oracle 11g) \ORACLE\\origlogA
\ORACLE\\origlogB \ORACLE\\sapdata1 \ORACLE\\sapdata2
Disk 1
Disk 2
\ORACLE\\mirrlogA \ORACLE\\mirrlogB \ORACLE\\sapreorg
\ORACLE\\saptrace \ORACLE\\saparch
2011-11-08
PUBLIC
45/180
3 3.7 Disk
Planning SAP Transport Host Directories\ORACLE\\sapbackup
\ORACLE\\sapcheck \ORACLE\\sapdata3 \ORACLE\\sapdata4
Disk 3Comments
\ORACLE\\oraarch
The configuration ensures that no data can be lost, but the
process for recovering a damaged database is complicated and
time-consuming. The redo logs and database files are located on the
same disks. This means that a single disk failure can result in the
loss of both the redo logs and database data. The I/O-intensive
redo logs are on the same disk volumes as the data files. This can
impede performance. An equally good alternative would be to simply
place all components on a single RAID 5 array.
3.7 SAP Transport HostThe SAP transport host contains the
transport directory used by the SAP transport system to store
transport data and change SAP system information, such as software
programs, data dictionary data, or customization data. If you have
several SAP systems, they are usually organized in transport
domains. In most cases, all SAP systems in a transport domain have
a common transport directory. When you install an SAP system, you
have to decide which transport host and directory you want to use
for your SAP system: Use the transport directory that SAPinst
creates during the installation of the SAP system by default on the
global host in :\usr\sap\trans. Use a transport directory located
on a host other than the global host (default host): You can use an
existing transport directory and host in your SAP system landscape.
You can set up a new transport directory on a different host. In
either case, you must prepare this host for use by the new SAP
system [page 54].More Information
SAP Directories [page 94] See the SAP Library: Application Help
SAP Library: 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 Change and Transport System Overview (BCCTS)
Basics of the Change and Transport System Transport Management
System Concepthttp://help.sap.com/nw703
46/180
PUBLIC
2011-11-08
3 3.8
Planning Multiple Oracle Homes
3.8 Multiple Oracle HomesThe Oracle database software is
installed in a directory structure which is referenced as Oracle
Home. Before you install your Oracle database software, you need to
decide whether you want to set up a single or multiple Oracle Homes
as this influences the installation procedure. If you install more
than one database instance on the same host you have the following
options: You use a single Oracle Home You can use a single Oracle
Home, if you use the same Oracle database version on one host for
different database instances. With a single Oracle Home, you have
to install the database software only once. With a single Oracle
Home, you cannot administer your databases independently. You use
multiple Oracle Homes If you use multiple Oracle Homes, you must
set up one Oracle Listener for each Oracle Home. Each listener must
have a different TCP/IP port number. With multiple Oracle Homes,
you can administer your databases independently. Multiple Oracle
Homes are necessary, if you need to install different Oracle
databases versions on the same host. Only valid for: HA (MSCS)
|
Multiple Oracle Homes are not supported in an MSCS
configuration.End of: HA (MSCS) |
More Information
Setting Up Multiple Oracle Homes [page 62]
2011-11-08
PUBLIC
47/180
This page is left blank for documents that are printed on both
sides.
4 4.1
Preparation Preparation Checklist
4 Preparation
4.1 Preparation ChecklistThis section includes the preparation
steps that you have to perform for the following installation
options: Central, distributed, or high-availability system Dialog
instance Detailed information about the steps is available in the
relevant chapter.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. 2. 3. 4. 5. 6. 7. You
disable the Windows Server 2008 (R2) firewall [page 50] on each
host. You perform basic preparations on Windows [page 50]. You
check that you have the required user authorization for running
SAPinst [page 52]. If required, you set up virtual host names [page
54]. If required, you prepare the SAP system transport host [page
54] for your SAP system. You make sure that the required
installation media [page 55] are available on each host.Only valid
for: HA (MSCS) |
To install a high-availability system with Microsoft Cluster
Service (MSCS), you also perform the MSCS-specific preparation
tasks [page 133].End of: HA (MSCS) |
8. You can continue with Installation [page 59]. The following
preparation is optional: Preparing an External ABAP System as
Source for User Data [page 105]Dialog Instance
You have to perform the following preparations on the host where
you install the dialog instance: 1. You disable the Windows Server
2008 (R2) firewall [page 50] on each host. 2. You perform basic
preparations on Windows [page 50]. 3. You check that you have the
required user authorization for running SAPinst [page 52]. 4. If
required, you set up virtual host names [page 54]. 5. If required,
you prepare the SAP system transport host [page 54] for your SAP
system. 6. You make sure that the required installation media [page
55] are available on each host.
2011-11-08