Académique Documents
Professionnel Documents
Culture Documents
PUBLIC
?=X]rt>6Dc6vP@bQ,dhPn FLC^d
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
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/132
PUBLIC
2011-11-21
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/instguides
The following table provides an overview of the most important document changes.
Version
Date
Description
1.00
2011-11-21
First version
2011-11-21
PUBLIC
3/132
Table of Contents
Chapter 1
1.1
1.2
1.3
1.4
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
8
8
9
Chapter 2
2.1
2.2
2.3
2.4
2.5
11
11
12
13
14
17
Chapter 3
3.1
3.2
3.2.1
19
19
20
3.5
3.6
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running the Prerequisite Checker in Standalone Mode
(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware and Software Requirements Tables . . . . . . . . . . . . . . . . . . . . . . . . .
Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setup of Database Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required File Systems for DB2 for Linux, UNIX, and Windows . . . . . . . . . . . .
Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Directory Structure of the DB2 Client Connectivity . . . . . . . . . . . . . . . . . . . .
DB2 Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Safety and Performance Considerations for Production
Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning the Switchover Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4
4.1
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.2.2
3.3
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
4/132
PUBLIC
21
21
25
33
34
36
36
37
39
40
41
2011-11-21
4.2
4.3
4.3.1
4.3.2
4.4
4.5
4.6
4.7
46
49
49
54
56
56
57
59
Chapter 5
5.1
5.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
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting and Mounting the Global Transport Directory . . . . . . . . . . . . . . . .
Exporting and Mounting Global Directories . . . . . . . . . . . . . . . . . . . . . . . . . .
Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Information About 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
63
67
68
69
76
77
79
80
83
83
84
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
Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Post-Installation Steps for the Operating System . . . . . . . . . . . . . .
Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logging on to the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Providing Access to the NetWeaver Administrator . . . . . . . . . . . . . . . . . . . . . .
Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High Availability: Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . .
Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling the Database for Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling Recoverability of the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing a Full Installation Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
87
87
88
88
89
90
90
91
92
92
94
95
97
Chapter 7
7.1
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
2011-11-21
PUBLIC
5/132
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.8.1
7.11.1
7.11.2
7.11.3
Chapter A
A.1
A.2
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Online Information from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
7.8.2
7.9
7.10
7.11
6/132
PUBLIC
103
104
105
106
106
107
109
109
113
116
117
119
119
120
121
2011-11-21
Introduction
1.1
1 Introduction
This document explains how to install an SAP system based on the Java application server of SAP
NetWeaver 7.3 including Enhancement Package 1 using the installation tool SAPinst.
CAUTION
Make sure you have read the Before You Start [page 7] section before you continue with this
installation guide.
Naming Conventions
K'/ SAP system refers to SAP system based on the application server of SAP NetWeaver 7.3 including Enhancement Package
1.
K'/ Java system refers to SAP system based on the Java application server of SAP NetWeaver 7.3 including Enhancement
Package 1.
K'/ diagnostics refers to diagnostics in SAP Solution Manager.
K'/ diagnostics agent refers to the agent of diagnostics in SAP Solution Manager.
K'/ DB2 V9.7 refers to IBM DB2 Version 9.7 for Linux, UNIX, and Windows.
Internet Address
http://service.sap.com/installNW73
2011-11-21
PUBLIC
7/132
Introduction
1.2
New Features
Description
SAPinst
NOTE
If you are performing a system copy using database means, DB2 is not
able to change the schema name and you can then choose a connect
user name that is different from the schema name.
8/132
PUBLIC
2011-11-21
Introduction
1.4
Title
1407532
Release Restrictions for SAP NetWeaver 7.3 Customer information about restrictions
concerning the productive usage of certain
functions.
SAP NetWeaver 7.3 EHP1 Installation on UNIX-specific information about the
UNIX
installation for SAP systems and corrections
to this documentation.
DB6: Inst. SAP NetWeaver 7.3 incl. EhP1 Platform-specific information about the SAP
UNIX
system installation and corrections to this
documentation.
DB6: Supported Fix Packs for DB2 for LUW Provides information about the currently
released database and Fix Pack combinations
DB6: Installation of Fix Packs for DB2 V9.7 UNIX-specific information about how you
(Linux and UNIX)
update the database software and the global
directory.
DB6: Supporting several database
Platform-specific additional information
partitions with DB2
about the support of multiple partitions with
DB2 for Linux, UNIX, and Windows
Inst. NetWeaver 7.3 - Diagnostics Agent Problems discovered after the publication of
installation
the installation guide or post-installation
steps
Hardware requirements of Java
Information on the hardware requirements
Development
for usage type Development Infrastructure
(DI), which depends on the size of your
development team.
Installation Prerequisite Checker
SAP Software on UNIX, Windows, and IBM i:
Checking OS Dependencies
Supported Languages and Code Pages
Information on possible languages and
language combinations in SAP systems
Linux only: SAP software on Linux:
This SAP Note contains Linux-specific
Essential comments
information about the SAP system
installation.
Central Note for Heterogeneous
This SAP Note and its related SAP Notes
Installation
describe the released operating system and
database combinations for heterogeneous
SAP systems landscapes.
1552840
1584218
101809
1363169
702175
1448655
737368
855498
73606
171356
1067221
Description
2011-11-21
PUBLIC
9/132
2.1
Standard System
This section shows the installation options covered by this installation 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.
]ZG Standard system [page 11] (formerly known as central system)
]ZG Distributed system [page 12]
]ZG High-availability system [page 13]
]ZG You can install one or more additional application server instances [page 14] to an existing standard,
distributed, or high-availability system.
]ZG You can install a host agent separately [page 17].
2011-11-21
PUBLIC
11/132
2.2
Distributed System
12/132
PUBLIC
2011-11-21
2.3
High-Availability System
2011-11-21
PUBLIC
13/132
2.4
To increase high availability by creating redundancy, we recommend that you install additional
application server instances on hosts different from the primary application server instance host. For
more information, see Installation of an Additional Application Server Instance [page 14].
The following figures show examples for the distribution of the SAP instances in a high-availability
system.
If you want to install additional application server instances running on an operating system other
than the primary application server instance, see Heterogeneous SAP System Installation [page 106]. For
example, you need to do this if your primary application server instance runs on zLinux but the
additional application server instance is to run on Windows.
14/132
PUBLIC
2011-11-21
2.4
For example, the following figure shows a standard system with additional application server instances
that run:
0/O On the main host of the SAP system, that is on the host on which the primary application server
instance and the database instance run
0/O On dedicated hosts
The following figure shows a distributed system with additional application server instances that run:
0/O On the main host of the SAP system, that is, on the host on which the primary application server
instance runs
0/O On dedicated hosts
We do not recommend you to install additional application server instances on the SAP global host.
2011-11-21
PUBLIC
15/132
2.4
The following figure shows a high-availability system with additional application server instances that
run:
G " On the host of the primary application server instance
G " On dedicated hosts
We do not recommend you to install additional application server instances on the switchover cluster
infrastructure.
16/132
PUBLIC
2011-11-21
2.5
2011-11-21
PUBLIC
17/132
Planning
3.1
Planning Checklist
3 Planning
1.
2.
You have chosen your installation scenario according to the Master Guide SAP NetWeaver 7.3 including
Enhancement Package 1 available at http://service.sap.com/installnw73.
You have decided which installation option [page 11] described in this guide you want to perform.
In a standard system, all mandatory instances are installed on one host. Therefore, if you are
installing a standard system, you can ignore references to other hosts.
1.
2.
3.
4.
5.
6.
7.
8.
You check the hardware and software requirements [page 20] on every installation host of the system
landscape that you want to install.
You identify basic SAP system installation parameters [page 25].
You carefully plan the setup of your database [page 33].
You decide on the transport host to use [page 40].
You decide whether you want to integrate LDAP Directory Services in your SAP system [page 99].
To install a high-availability system, you read Planning the Switchover Cluster [page 41].
Optionally, you decide whether you want to install multiple components in one database (MCOD) [page
103].
You can now continue with Preparation [page 45].
1.
2.
3.
You check the hardware and software requirements [page 20] for every installation host on which you want
to install one or more additional application server instances.
You identify basic SAP system installation parameters [page 25].
You can now continue with Preparation [page 45].
2011-11-21
PUBLIC
19/132
Planning
3.2
If your hosts do not fully meet the requirements, you might experience problems when working
with the SAP system.
Prerequisites
@D
@D
@D
@D
Make sure that the host name meets the requirements listed in SAP Note 611361.
Contact your OS vendor for the latest OS patches.
Check your keyboard definitions.
If you want to install a printer on a host other than the primary application server instance host
(for example, on a separate database instance host), make sure that the printer can be accessed
under UNIX.
Process Flow
1.
2.
3.
For the most recent updates to the Prerequisite Checker, always check SAP Note 855498.
@D The Hardware and Software Requirements Tables [page 21]
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:
@D You use the Quick Sizer tool available at http://service.sap.com/sizing.
@D You contact your hardware vendor, who can analyze the load and calculate suitable hardware
sizing depending on:
@D The set of applications to be deployed
@D How intensively the applications are to be used
@D The number of users
20/132
PUBLIC
2011-11-21
Planning
3.2
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.
Procedure
1.
Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on the
installation host. For more information, see Preparing the Installation Media [page 59].
RECOMMENDATION
2.
3.
4.
"K7 Make installation media locally available. For example, reading media mounted with
Network File System (NFS) might fail.
"K7 Copy at least the medium for the installation master (folder
<Product>_IM_<OS>_<DB>) to the local file system of the installation host.
Start SAPinst [page 69].
On the Welcome screen, choose <SAP System> 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.
5.
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.
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.
2011-11-21
PUBLIC
21/132
Planning
3.2
The information here is not intended to replace the operating system documentation. For more
information, see your operating system documentation.
For general information about the SAP system installation on Linux, see SAP Note 171356.
Hardware Requirements
Requirement
Hardware
Processing Units
22/132
For more information, see the DB2-specific requirements for your database version
at http://www.ibm.com/software/data/db2/udb/sysreqs.html.
ISO 9660 compatible
f~m General Requirements:
f~ 4.3 GB of temporary disk space for every required installation medium that
you have to copy to a local hard disk. For more information, see Preparing
the Installation Media [page 59].
f~ 1.2 GB of temporary disk space for the installation.
f~ If there is no tape drive attached to your system, you need additional disk
space for the files created by DB2s database backup command and the
archived database log files. Alternatively, you need access to network-based
storage management products, such as Legato Networker or Tivoli Storage
Manager (TSM) (for database backup/restore).
f~ If an advanced disk array is available (for example, RAID), contact your
hardware vendor to make sure that the data security requirements are
covered by this technology.
f~ If an advanced disk array is available (for example, RAID), contact your
hardware vendor to make sure that the data security requirements are
covered by this technology.
f~m Instance-Specific Requirements:
If you install several instances on one host, you have to add up the
requirements accordingly.
PUBLIC
2011-11-21
Planning
3.2
Requirement
For more information about space requirements for the file systems and
directories of the instances, see SAP Directories [page 49] and the appropriate
database-specific information listed below.
N Central services instance (SCS) for Java:
Minimum 3.5 GB
N Enqueue replication server instance for the SCS (if required):
Minimum 3.5 GB
N Database Instance:
For specific disk space information required for an SAP system installation
on DB2 V9.7, see SAP Note 1584218.
NOTE
RAM
2011-11-21
N For safety reasons (system failure), the file systems must be
physically distributed over several disks, or RAID-technology
must be used.
N To ensure a good performance of your production system,
create separate file systems for the directories listed in Required
File Systems for DB2 for Linux, UNIX, and Windows [page 34].
N Primary application server instance:
Minimum 6 GB
N Additional application server instance:
Minimum 6 GB
N Host agent:
Minimum 1 GB
N Diagnostics agent:
Minimum 3 GB
The following lists the RAM requirements for each instance.
If you install several instances on one host, you have to add up the requirements
accordingly.
N Central services instance for Java (SCS)
Minimum 1 GB
N Enqueue replication server instance for the SCS (if required)
Minimum 1 GB
N Database Instance:
Minimum 2 GB
N Primary application server instance:
Minimum 8 GB
N For more information about RAM required for usage type BI Java, see SAP
Note 927530.
N For more information about RAM required for usage type Development
Infrastructure (DI), see SAP Note 737368.
N Additional application server instance:
Minimum 8 GB
N Host agent:
Minimum 0.5 GB
N Diagnostics agent:
Minimum 1 GB
Refer to SAP Note 1382721 for the commands to display the RAM size on Linux.
PUBLIC
23/132
Planning
3.2
Requirement
Swap Space
You need hard disk drives with sufficient space for swap. We recommend that you
use the amount of swap space as described in SAP Note 1597355. You might decide
to use more or less swap space based on your individual system configuration and
your own experience during daily usage of the SAP system.
To verify paging space size and kernel settings, you can execute memlimits as follows:
1. Make sure that the SAPCAR program is available on the installation host. If
SAPCAR is not available, you can download it from http://service.sap.com/
swdc.
2. Make the SAPEXE.SAR archive available on the installation host. This archive is
contained in the folder K_<Kernel Version>_<U/N>_<OS>/DBINDEP of the
installation media.
3. To unpack the file memlimits, enter the following command:
SAPCAR -xvfg SAPEXE.SAR memlimits
4.
In case of error messages, increase the paging space and rerun memlimits until
there are no more errors.
Software Requirements
Requirement
Database software /
Client software
DB2 V9.7 database software or DB2 V9.7 client software (automatically installed by
SAPinst)
CAUTION
Operating System
Version
(CL5 For the installation of your SAP system, only the English version of the
DB2 database is supported.
(CL5 You must only use the DB2 software that is provided by the SAP
installation DVDs.
SLES11, RHEL 6
To check the operating system version, enter the following command:
cat /etc/*-release
For more information, see the Product Availability Matrix (PAM) at http://
service.sap.com/pam.
Linux Kernel Parameters Check SAP Note 171356 for Linux kernel versions certified by SAP.
To check the Linux kernel parameters for your Linux distribution, see one of the
following SAP Notes:
(CL5 RHEL6: SAP Note 1496410
(CL5 SLES 11 SP1: SAP Note 1310037
NOTE
24/132
PUBLIC
2011-11-21
Planning
3.3
Requirement
National Language
Support (NLS)
System Language
iY Check SAP Note 187864 for information about corrected operating system
locales and SAP blended Code Pages.
For the installation, you must choose English as the operating system language on
all Linux hosts that run SAP software.
Other Requirements
Requirement
Host Name
To find out physical host names, open a command prompt and enter
hostname.
For more information about the allowed host name length and characters
allowed for SAP system instance hosts, see SAP Note 611361.
If you want to use virtual host names, see SAP Note 962955.
SAPinst only prompts you for this parameter if you use a login shell other than
the recommended C shell (csh).
For more information, see SAP Note 202227.
Make sure that the korn shell (ksh) is installed on the hosts where you install
the SAP system. If you perform a system copy, make sure that the korn shell
(ksh) is installed on the target system host.
If application servers are installed decentralized, then a shared file system must
be installed, for example Network File System (NFS).
Make sure that the C compiler gcc is installed.
Login Shell
2011-11-21
PUBLIC
25/132
Planning
3.3
If you want to change any of the default settings, you can do so on the Parameter Summary screen.
L 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.
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 SAP system installation parameters that you need to specify before
installing your SAP system:
L SAP System Parameters
L SAP System Database Parameters
L Diagnostics Agent Parameters
For all other installation parameters, use the F1 help in the SAPinst screens.
SAP System Parameters
Parameters
Description
Unicode System
SAP System ID <SAPSID>
This prompt appears when you install the central services instance, which
is the first instance to be installed in a distributed system.
CAUTION
26/132
PUBLIC
2011-11-21
Planning
3.3
Parameters
Description
The Master Password is not used as password for the Database Users
such as Database Administrator User or DB Connect User.
CAUTION
If you did not create the operating system users manually before the
installation, SAPinst creates them with the common master password
(see table Operating System Users). In this case, make sure that the master
password meets the requirements of your operating system.
Java
users
CAUTION
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.
2011-11-21
PUBLIC
27/132
Planning
3.3
Parameters
Description
The Java message server port uses the parameter rdisp/msserv_internal with
default value 39<nn>, where <nn> 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.
Java(TM) Cryptography
If you want to install usage type Adobe Document Services, make sure that you
Extension (JCE) Unlimited download the unlimited version of the JCE Jurisdiction Policy Files 6 archive. For
Strength Jurisdiction Policy more information about where to download it, see SAP Note 1240081.
Files Archive
CAUTION
UME Configuration
If there is an old JCE policy zip file, the Prerequisite Checker does not
recognize this fact. For this reason, SAPinst issues the error message
java.lang.SecurityException during the Create Secure Store step,
stating that the jurisdiction policy files are not signed by trusted signers.
SAPinst prompts you for how to configure the UME during the input phase of
the installation.
You can choose between the following options:
71T Use Java Database
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.
71T 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.
You must have created the required users manually on the external ABAP
system.
For more information, see Preparing User Management for an External ABAP System
(Optional) [page 57].
For more information about supported UME data sources and change options,
see SAP Note 718383.
NOTE
71T If you want to use LDAP as data source, choose Use Java Database and
change to LDAP after the installation has finished.
71T If you want to use the User Management Engine for an existing ABAP
system, choose Use ABAP.
71T If you install a PI system, you have the following options:
71T If you want to install non-central Advanced Adapter Engine
(AAE) as optional standalone unit for a PI dual-stack installation,
you have the following options:
71T Use External ABAP System: This sets up the ABAP-based User
Management Engine on the Integration Server system.
71T Use Java Database: This sets up "local" user management on the
system of the non-central AAE.
71T If you want to install non-central Advanced Adapter Engine
(AAE) as optional standalone unit for an Advanced Adapter
28/132
PUBLIC
2011-11-21
Planning
3.3
Parameters
Description
Use a long key phrase that cannot be guessed easily. Use both uppercase and
lowercase letters in the phrase and include special characters.
NOTE
Path to SAPCRYPTO.SAR
2011-11-21
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.
The SAP Cryptographic Library is required to enable Secure Sockets Layer (SSL)
encryption of HTTP connections. In most cases it is installed automatically from
PUBLIC
29/132
Planning
3.3
Parameters
Description
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.
DNS Domain Name for SAP If you want to use HTTP-based URL frameworks such as Web Dynpro applications,
System
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:
<host name>.<domain name>
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
Description
Database ID <DBSID>
The <DBSID> identifies the database instance. SAPinst prompts you for the
<DBSID> when you are installing the database instance.
The <DBSID> can be the same as the <SAPSID>.
CAUTION
30/132
PUBLIC
2011-11-21
Planning
3.3
Parameters
Description
OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP
TOP UID USE USR VAR
db2<dbsid> has the DB2 system administration authorities and belongs to group
db2<dbsid>
We recommend, however, that you keep the names of the connect user and
the database schema identical in standard use cases.
If you are performing a system copy using database means, DB2 is not able to
change the schema name and you can then choose a connect user name that is
different from the schema name.
ID of the db<dbsid>adm
group
db<dbsid>adm group
ID of the db<dbsid>ctl
group
db<dbsid>ctl group
ID of the db<dbsid>mnt
group
db<dbsid>mnt group
ID of the db<dbsid>mon
group
db<dbsid>mon group
Database Communication
Port
NOTE
2011-11-21
NOTE
PUBLIC
31/132
Planning
3.3
Parameters
Description
Be aware that the first part, for example /db2/<SAPSID>/ is definite and you
can only enter a value for sapdata<n>.
Database Memory or
Instance Memory
Use Change, that is, add or remove the names and number of the sapdata directories.
Specify the size of the memory that DB2 requires for the database instance. That
is, you set the database manager configuration parameter INSTANCE_MEMORY.
Parameter INSTANCE_MEMORY includes the database- and application-specific
memory segments that are used by DB2.
Specify the file system path where either an existing DB2 software installation
already resides or where you want the new copy of DB2 to be installed.
RECOMMENDATION
If you want to install a new copy of DB2, we recommend that you accept
the default path suggested by SAPinst.
Diagnostics Agent Parameters
Description
System ID of Diagnostics
Agent <DASID>
SAPinst sets the system ID of the diagnostics agent, <DASID>, 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
32/132
PUBLIC
2011-11-21
Planning
3.4
Parameters
Description
OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID
USE USR VAR
SLD Destination
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<Instance_Number>.
For more information, see SAP Directories [page 49].
The same restrictions apply as in Instance Number of the SAP System (see above).
You can choose between the following options:
/#KRu Register in existing central SLD
SAPinst only prompts you for the parameters listed below in this table if you
select this option.
RECOMMENDATION
If the instance number of your Java system is 01, the SLD HTTP Port is 50100.
SLD Data Supplier User and You have to enter the existing SLD Data Supplier User and password of the central
password
SLD.
2011-11-21
PUBLIC
33/132
Planning
3.4
1Ys
1Ys
1Ys
1Ys
1Ys
Required File Systems for DB2 for Linux, UNIX, and Windows [page 34]
Users and Groups [page 36]
Directory Structure of the DB2 Client Connectivity [page 36]
DB2 Tablespaces [page 37]
Data Safety and Performance Recommendations [page 39]
3.4.1 Required File Systems for DB2 for Linux, UNIX, and
Windows
This section lists the file systems that are required by DB2 as well as the permissions that you have to
set.
CAUTION
If you plan to set up a high availability database cluster (SA MP) that is based on a shared disk, all
the file systems listed in the table below must be located on the shared disk.
For more information, see the document IBM DB2 High Availability Solution: IBM Tivoli System
Automation for Multiplatforms at:
http://service.sap.com/instguidesnw <Your SAP NetWeaver Release> Installation
Installation SAP NetWeaver Systems
Required File Systems
NOTE
Description
/db2/db2<dbsid>
/db2/<DBSID>/log_dir
/db2/<DBSID>/db2dump
34/132
PUBLIC
2011-11-21
Planning
3.4
Description
sapdata directories, you can change this on the SAPinst
The file systems and logical volumes must have the permissions and owner shown in the following
table and they must be created and mounted before starting SAPinst. SAPinst then sets the required
permissions and owners.
NOTE
You can create the owners and groups manually if they do not exist yet. Otherwise, SAPinst creates
them automatically. For more information, see Creating Operating System Users Manually [page 46].
File System/Logical Volume
Permissions
Owner
Group
/db2/<DBSID>
755
db2<dbsid>
db<dbsid>adm
/db2/<DBSID>/log_dir
755
db2<dbsid>
db<dbsid>adm
/db2/<DBSID>/db2dump
755
db2<dbsid>
db<dbsid>adm
750
db2<dbsid>
db<dbsid>adm
/db2/<DBSID>/sapdata<n>
:M No automatic storage
management:
/db2/<SAPSID>/sapdata<n>
More Information
2011-11-21
PUBLIC
35/132
Planning
3.4
Home Directory
Group
db2<dbsid>
/db2/db2<dbsid>
db<dbsid>adm
<sapsid>adm
can be chosen
/home/sap<sapsid>db
sap<sapsid>db
As of Enhancement Package 1 for SAP NetWeaver 7.3, you can specify the name of the Java connect
user (sap<sapsid>db) independently from the SAP schema name during the dialog phase of
SAPinst.
We recommend, however, that you keep the names of the connect user and the database schema
identical in standard use cases. If you are performing a system copy using database means, DB2 is
not able to change the schema name and you can then choose a connect user name that is different
from the schema name.
36/132
PUBLIC
2011-11-21
Planning
3.4
JDBC Driver
During the installation of the database instance, the JDBC driver is stored in the global directory
(global/db6/jdbc) of your SAP system. Each time you start the SAP system, the JDBC driver is copied
from the global/db6 directory to the local exe directory, and the active SAP system uses these copies of
the JDBC driver in the local exe directory.
Therefore, by exchanging the JDBC driver in the global directory, you are able to update the JDBC
driver while the SAP system is up and running. Each time you restart the application server, the JDBC
driver is again copied to the local exe directory, and always the latest version is used.
More Information
For information about how to update the DB2 CLI driver or the JDBC driver during the Fix Pack
installation, see SAP Note 1363169.
As of DB2 V9.1 and higher, the database and the SYSCATSPACE tablespace are always created
with automatic storage management enabled even if you deselect this option on the IBM
DB2 for Linux, UNIX, and Windows Sapdata Directories dialog.
O`= DMS File tablespaces in autoresize mode
SAPinst creates all DMS tablespaces with FILE containers in autoresize mode as well as one tablespace
container for each tablespace in every sapdata directory or file system. DB2 automatically extends
the size of all DMS FILE tablespaces in autoresize mode as long as there is space left in the sapdata
directories or file systems.
With DMS FILE tablespaces in autoresize mode, you are more flexible to distribute heavily used
tablespaces to dedicated storage devices at a later point in time.
For more information, see Data Safety and Performance Considerations [page 39].
2011-11-21
PUBLIC
37/132
Planning
3.4
If you are using tablespaces managed by DB2's automatic storage management, DB2 creates and
administers the tablespace containers for you.
If you are using DMS FILE tablespaces in autoresize mode, each tablespace of your SAP installation
has at least one container. A container is a file that holds pages belonging to a tablespace. Since you
might want to add containers as your database grows in size, you should adhere to the following naming
scheme:
The first container of a tablespace is given the name of the tablespaces plus the ending container001.
Therefore, <SAPSID>#BTABD has at least the container <SAPSID>#BTABD.container001. The next
container is called <SAPSID>#BTABD.container002, and so on.
Container Sizes
Equal container sizes ensure the proper balancing of container access and therefore better performance,
if the containers reside on different disks. SAPinst creates all containers of a tablespace with the same
size.
Tablespace Sizes Without Autoresize
By default, the tablespaces are created with autoresize mode. If you are using tablespaces without the
autoresize mode, you must extend the tablespaces manually. If you do not increase your tablespace
sizes in time, the following error occurs:
Error occurred during DB access SQLException SQLCODE: -289
Tablespaces in an MCOD Environment
If you want to install additional SAP components into the same database, make sure that you consider
the information under MCOD Tablespaces and File Systems [page 104].
38/132
PUBLIC
2011-11-21
Planning
3.4
When you work out the assignment of components to disks, you first need to receive an overview
of the main components and their corresponding directories. Make sure that you have an overview
of the expected database size, the available disks and the I/O adapters that are used to attach the
disks to your system.
Data Safety and Performance Considerations
When you plan your SAP system installation, you must consider the following: