Nw731 Linux Db6 Java

Installation Guide
SAP Systems Based on SAP NetWeaver 7.3 Application Server

Java including EhP1 on Linux: IBM DB2 for Linux, UNIX, and
Windows
Target Audience
? System administrators
? Technology consultants
PUBLIC
?=X]rt>6Dc6vP@bQ,dhPn FLC^d
About this Installation Guide
SAP System Installation
SAP system installations should only be performed by SAP Technical Consultants certified for your
operating system, your database, and the SAP system that you are installing
SAP Installation Tool
You must only use the SAP installation tools according to the instructions and for the purposes
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
Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . .

Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
Creating Operating System Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . .

Required File Systems and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up File Systems for a High-Availability System . . . . . . . . . . . . . . . . . .
Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Switchover Preparations for High Availability . . . . . . . . . . . . . . . .
Preparing an External ABAP System as Source for User Data . . . . . . . . . . . . . .
Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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
Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . .

MCOD Tablespaces and File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a User for LDAP Directory Access . . . . . . . . . . . . . . . . . . . . . . . . . .
Heterogeneous SAP System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Tablespaces Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping SAP System Instances . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping SAP System Instances Using the SAP Management
Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping SAP System Instances Using Commands . . . . . . . . . . .
Troubleshooting for Portal Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting the Database Instance and Database Software Manually
(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting the Database and the DB2 Instance Manually (Optional) . . . . . . . . .
Deleting a Database Schema Manually (Optional) . . . . . . . . . . . . . . . . . . . . .
Deleting the DB2 Software Installation Manually (Optional) . . . . . . . . . . . . .
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
Before You Start
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.
1.1 Before You Start

Make sure you have read the Master Guide for your SAP Business Suite application or SAP NetWeaver
application before you continue with this installation guide.
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:
Document
Internet Address
Master Guide SAP NetWeaver 7.3 including

Enhancement Package 1
http://service.sap.com/installNW73
2011-11-21
PUBLIC
7/132
Introduction
1.2
New Features
1.2 New Features

The table below provides an overview of the new features.
Make sure that you also read the release notes at http://service.sap.com/releasenotes.
Area
Description
SAPinst
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_<Version>_U_<Your
Operating System Platform>) 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 25].
Process Integration and Orchestration is available as an optional standalone unit
installation.
The installation of SAP systems that are based on this SAP NetWeaver release
and higher is only supported on DB2 V9.7 for Linux, UNIX, and
Windows.
As of DB2 Version 9.1 or higher, you can have multiple DB2 installations on
one physical machine. The database installations are independent of each
other and can have different Fix Pack levels as well as different configuration
settings, and so on.
By default, the software is installed in the following directory: /db2/
db2<dbsid>/db2_software.
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.
Supported database version
Specification of connect user

name
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.
1.3 SAP Notes for the Installation

You must read the following SAP Notes before you start the installation. These SAP Notes contain
the most recent information on the installation, as well as corrections to the installation
documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find at http://
service.sap.com/notes.
8/132
PUBLIC
2011-11-21
Introduction
1.4
Accessing the SAP Library
SAP Notes for the Installation

SAP Note Number
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
1.4 Accessing the SAP Library

The references to SAP NetWeaver Library documentation in this installation guide always refer to
the following on SAP Help Portal:
http://help.sap.com/nw731 Application Help
SAP Library: English
2011-11-21
PUBLIC
9/132
This page is left blank for documents

that are printed on both sides.
Installation Options Covered by this Guide
2.1
Standard System
2 Installation Options Covered by this

Guide
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].
2.1 Standard System

You can install a standard system on a single host.
In a standard system, all main instances run on a single host:
There are the following instances:
]ZG Central services instance (SCS instance)
]ZG Enqueue replication server instance (ERS instance) for the SCS instance (optional)
]ZG Database instance (DB)
]ZG Primary application server instance (PAS instance)
Additionally you can install one or more additional application server instances. For more information,
see Additional Application Server Instance [page 14].
2011-11-21
PUBLIC
11/132
2.2
Distributed System
B#@:&vLXT;Standard Java System
2.2 Distributed System

An SAP system consists of SAP instances. An SAP instance is a group of processes that are started and
stopped at the same time.
In a distributed system, every instance can run on a separate host:
sg Central services instance for Java (SCS instance)
sg Enqueue replication server instance (ERS instance) for the SCS instance (optional)
sg Database instance (DB)
The Java stack uses its own database schema in the database
sg Primary application server instance (PAS)
The graphics below assume that you use the global directories of the SCS instance as global file system.
That means that the host with the SCS instance is the SAP global host. However, you can also separately
install the global directories on any host of your SAP system landscape.
You can also use the SAP transport host or the host with the global file system (SAP global host) as
your primary application server instance host.
Optionally you can install one or more additional application server instances. For more information,
see Installation of an Additional Application Server Instance [page 14].
12/132
PUBLIC
2011-11-21
2.3
High-Availability System
T\Kpo5L%yDistributed Java System
2.3 High-Availability System

An SAP system consists of SAP instances. An SAP instance is a group of processes that are started and
stopped at the same time.
In a high-availability system, every instance can run on a separate host:
There are the following instances:
o Central services instance for Java (SCS instance)
o Enqueue replication server instance (ERS) for the SCS instance (mandatory)
The enqueue replication server instance contains the replication table, which is a copy of the lock
table in the SCS instance.
o Database instance (DB)
o Primary application server instance (PAS)
The graphics below assume that you run the SCS instance on the switchover cluster infrastructure.
However, you can also run other SAP system instances that are a single point of failure (SPOF) on a
switchover cluster infrastructure, for example the database instance.
You can also use the SAP transport host or the host with the global file system (SAP global host) as
your primary application server instance host.
We recommend that you run the SCS instance in a switchover cluster infrastructure. The SCS instance
must have its own ERS instance.
2011-11-21
PUBLIC
13/132
2.4
Additional Application Server Instance
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.
IMaVhÀHigh-Availability System
2.4 Additional Application Server Instance

You can install one or more additional application server instances for an existing SAP system.
Additional application server instances are optional and can be installed on separate hosts.
An additional application server instance can run on:
IM5 The host of any instance of the existing SAP system (exceptions see below)
IM5 On a dedicated host
NOTE
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
Additional Application Server Instance for a Standard System
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
0b#M4@Additional Application Server Instance for a Standard System
For more information, see Standard System [page 11].

Additional Application Server Instance for a Distributed System
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
G mm+}*uAdditional Application Server Instance for a Distributed System
For more information, see Distributed System [page 12].

Additional Application Server Instance for a High-Availability System
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
Host Agent as a Separate Installation
8T&@ !L/Additional Application Server Instance for a High-Availability System
For more information, see High-Availability System [page 13].
2.5 Host Agent as a Separate Installation

Using 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.2 or higher. You only need to install a host agent separately in the following cases:
*V You want to manage a host that does not have an SAP instance or component.
*V You have upgraded your SAP system to SAP NetWeaver 7.2 or higher.
The section Installing the Host Agent Separately [page 107] describes how to perform the installation.
2011-11-21
PUBLIC
17/132

Planning
3.1
Planning Checklist
3 Planning
3.1 Planning Checklist

This section includes the planning steps that you have to perform for the following installation options:
Standard, distributed, or high-availability system
Additional application server instance
Detailed information about the steps is available in the relevant chapter.
Prerequisites
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.
Standard, Distributed, or High-Availability System

NOTE
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
Hardware and Software Requirements
3.2 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating system
and the SAP instances.
CAUTION
If your hosts do not fully meet the requirements, you might experience problems when working
with the SAP system.
Prerequisites
@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.
Check the Product Availability Matrix at http://service.sap.com/pam for supported operating

system releases.
Check the hardware and software requirements using:
@D The Prerequisite Checker:
@D Standalone (optional) before the installation process
For more information, see Running the Prerequisite Checker Standalone [page 21].
@D Integrated in the installation tool (mandatory) as part of the installation process
For more information, see Running SAPinst [page 69].
NOTE
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
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.
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.
3.2.2 Hardware and Software Requirements Tables

Every installation host must meet at least the requirements listed in the following tables. Most of the
requirements are valid for every installation host whereas some requirements are instance-specific and
are marked accordingly.
2011-11-21
PUBLIC
21/132
Planning
3.2

NOTE
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
Values and Activities
Hardware
Processing Units
Your operating system platform must be 64-bit.

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.
NOTE
The following hardware architecture is supported with DB2 V9.7:

PowerPC and x86_64
CAUTION
The installation of an SAP system on Intel IA64 is not supported.
Optical Media Drive

Hard Disk Space
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.
Start memlimits using the following command:

./memlimits -l 20000
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
Modify the kernel parameter msgmni as follows:

(CL5 For SLES 11, see SAP Note 1310037.
(CL5 For RHEL6, see SAP Note 1496410.
(CL5 In file /etc/sysctl.conf, add the line kernel.msgmni=1024.
(CL5 Activate the modified kernel parameters with the following command:
sysctl p
In most cases these steps are sufficient.
24/132
PUBLIC
2011-11-21
Planning
3.3
Basic SAP System Installation Parameters
Requirement
National Language
Support (NLS)
For more information about required kernel parameter modifications on DB2,

see the IBM documentation Quick Beginnings for DB2 Servers.
Make sure that National Language Support (NLS) and corresponding locales are
installed.
iY Check that the required locales such as the following are available:
de_DE, en_US
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
Required additional shell
Shared file systems for

decentralized systems
C compiler
3.3 Basic SAP System Installation Parameters

SAPinst prompts for input parameters during the Define Parameters phase of the installation.
You can install your SAP system either in Typical or Custom mode:
iY Typical
If you choose Typical, the installation is performed 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:
iY SAP system ID and Database Connectivity Parameters
iY Master password
iY JCE Unlimited Strength Jurisdiction Policy files archive (only prompted if you install usage
type Adobe Document Services)
iY SAP system profile directory only for systems with instances on separate hosts
iY UME Configuration
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>
A Java standalone system is always a Unicode system.

The SAP system ID <SAPSID> identifies the entire SAP system.
SAPinst prompts you for the <SAPSID> when you execute the first installation
option to install a new SAP system.
If there are further installation options to be executed, SAPinst prompts you for
the profile directory. For more information, see the description of the parameter
SAP System Profile Directory.
EXAMPLE
This prompt appears when you install the central services instance, which
is the first instance to be installed in a distributed system.
CAUTION
Choose your SAP system ID carefully. Renaming is difficult and requires

you to reinstall the SAP system.
Make sure that your SAP system ID:
L Is unique throughout your organization. Do not use an existing <SAPSID>
when installing a new SAP system.
Consists
of exactly three alphanumeric characters
L
L Contains only uppercase letters
L Has a letter for the first character
L 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
26/132
PUBLIC
2011-11-21
Planning
3.3
Parameters
Description
If you want to install an additional application server instance, make sure

that no gateway instance with the same SAP System ID (SAPSID) exists in
your SAP system landscape.
Instance Number of the SAP Technical identifier for internal processes. It consists of a two-digit number from
System
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 instance numbers of SAP systems that already exist on the installation
host, look for subdirectories ending with <nn> of local (not mounted) /usr/sap/
<SAPSID> directories.
The value <nn> is the number assigned to the instance.
For more information about the naming of SAP system instances, see SAP
Directories [page 49].
Master Password
Common password for all users that are created during the installation:
Operating system users (for example <sapsid>adm)
NOTE
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
(for example Administrator)

Secure Store key phrase
For more information, see table Key Phrase for Secure Store Settings.
Password policy
The master password:
Must be 8 to 14 characters long
Must contain at least one letter (a-z, A-Z)
Must contain at least one digit (0-9)
Must not contain \ (backslash) and " (double quote)
Depending on the installation option, additional restrictions may apply (for
example, the master password must not contain the name of a Java user created
during the installation).
Message Server Port
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
Engine Extended (AEX) installation or a Process Integration

and Orchestration Package (PI-CP) installation, you have to
choose Use Java Database. This sets up local user management on
the system of the non-central AAE.
Using the Java Database:
Administrator User
SAPinst sets the user name Administrator and the master password by default.
If required, you can choose another user name and password according to your
requirements.
Guest User
SAPinst sets the user name Guest and the master password by default.
The guest user is a user for anonymous access.
Using an External ABAP System Parameters for the ABAP Connection:
Application Server Instance This is the instance number on the application server of the central ABAP system
Number
to which you want to connect the Application Server Java.
To find out the number on the host of the primary application server instance,
look under the SAP directory usr/sap/<SAPSID>/DVEBMGS<nn>. The value <nn> is
the number assigned to the SAP system.
Application Server Host
This is the host name of the relevant application server instance.
To find out the host name, enter hostname at the command prompt of the host
running the primary application server instance.
Communication User
This is the name and password of the existing ABAP communication user. You
must have created this user manually on the external ABAP system.
Using an External ABAP System Parameters for the Application Server Java Connection:
Administrator User
This is the name and password of the administrator user that you created on the
external ABAP system.
Administrator Role
The role SAP_J2EE_ADMIN must exist on the external ABAP system.
Guest User
This is the name and password of the guest user that you created on the external
ABAP system.
The guest user is a user for anonymous access.
Guest Role
The role SAP_J2EE_GUEST must exist on the external ABAP system.
Key Phrase for Secure Store This is a random word or phrase that is used to encrypt the secure store.
Settings
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
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
If your application server host is called kirk.wdf.sap.com, the DNS Domain

Name is wdf.sap.com.
SAP System Database Parameters
Parameters
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
Choose your database ID carefully. Renaming is difficult and requires you

to reinstall the SAP system.
7sr If you want to install a new database:
Make sure that your database ID:
7sr Is unique throughout your organization
7sr Consists of exactly three alphanumeric characters
7sr Contains only uppercase letters
7sr Has a letter for the first character
7sr Does not include any of the following, which are reserved IDs:
ADD 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
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 instance owner
db2<dbsid> has the DB2 system administration authorities and belongs to group
db2<dbsid>
db<dbsid>adm, which has DB2 SYSADM authorities. By default, user db2<dbsid> is a
Java database connect user

(sap<sapsid>db)
member of group db<dbsid>adm.

The user name corresponds to the database schema where J2EE tables are created.
You can specify the name of the connect user independently from the SAP schema
name during the dialog phase of SAPinst.
RECOMMENDATION
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
In a multipartitioned database environment, the group ID must be the same

on all database partition servers.
Members of this group have DB2 SYSADM authorities. By default, user db2<dbsid>
is a member of this group.
NOTE

Members of this group have DB2 SYSCTRL authorities. By default, <sapsid>adm is
a member of this group.
NOTE

Members of this group have DB2 SYSMAINT authorities.
NOTE

Members of this group have DB2 SYSMON authorities.
By default, sap<sapsid>db (the Java database connect user) is a member of this
group.
The DB2 Communication Port is used for TCP/IP communication between the
database server and remote DB2 clients.
In a central system installation and for the database instance in a distributed
installation, SAPinst always proposes 5912 as default value.
NOTE
SAPinst requests this value during the database instance installation.

Database Partition Group
Mapping
2011-11-21
NOTE
SAPinst only asks this parameter if you are performing a heterogeneous

system copy and if the following condition is met: You run SAPinst to install
PUBLIC
31/132
Planning
3.3
Parameters
Description
the target database in a multipartitioned database environment using the

R3Load method.
Drive for Diagnostic Data

Add sapdata directories
You can assign the displayed node groups to a database partition.

Location of the db2diag.log that contains diagnostic data required in case of, for
example, a database crash.
For an installation on DB2 V9.7, the tablespaces are stored in /db2/<SAPSID>/
sapdata<n>.
By default, SAPinst creates four sapdata directories (sapdata1, sapdata2,
sapdata3, sapdata4).
NOTE
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
DB2 Software Path
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
The diagnostics agent is installed automatically with the SAP system.

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
Choose the <DASID> carefully. Renaming is difficult and requires you to

reinstall the diagnostics agent.
Make sure that the <DASID>:
"Y Either does not yet exist on the local installation host or does already exist
but was only used for a diagnostics agent installation
"Y Consists of exactly three alphanumeric characters
"Y Contains only uppercase letters
"Y Has a letter for the first character
"Y 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
32/132
PUBLIC
2011-11-21
Planning
3.4
Setup of Database Layout
Parameters
Description
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
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
SLD HTTP Host

SLD HTTP Port
We recommend that you select this option.

No
SLD
destination
/#KRu
If you select this option:
/#KR You have to configure the SLD destination for the diagnostics agent
manually after the installation with SAPinst has finished.
/#KR SAPinst does not prompt you for the parameters listed below in this
table.
The host name of the System Landscape Directory (SLD)
The HTTP port of the Java system where the SLD is installed. The following naming
convention applies:
5<instance_number>00.
EXAMPLE
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.
3.4 Setup of Database Layout

NOTE
The following sections apply especially to the installation of a production system.

When you plan your SAP system installation, it is essential to consider the setup of your database layout
with regard to the distribution of, for example, SAP directories or database file systems to disks. The
distribution depends on your specific environment and you must take factors into consideration, such
as storage consumption of the software components involved, safety requirements and expected
workload.
Make sure that you read the following sections before starting the SAP system installation:
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
Production systems only:

During the installation of your SAP system, you can specify the amount and names of the sapdata
directories. However, to ensure that your SAP system performs well in a production environment,
you have to define and control the distribution of the database directories to physical disks. You
do this by creating and mounting separate file systems manually for the directories listed in the
following table.
File System/Logical Volume
Description
/db2/db2<dbsid>
Home directory of user db2<dbsid> and contains the

DB2 instance data for <DBSID> and the DB2 software.
Size: at least 1 GB
Contains at least the online database log files.
Size: at least 1.4 GB
Contains DB2 diagnostic log files, DB2 dump files, and
further service engineer information.
Size: 100 MB
SAP data for container type database managed space (DMS)
FILE or for use of DB2's automatic storage
management. By default, SAPinst creates four
sapdata directories. If you require more or fewer
/db2/<DBSID>/log_dir
/db2/<DBSID>/db2dump
1Ys With DB2's automatic storage management:

/db2/<DBSID>/sapdata<n>
1Ys No automatic storage management:

/db2/<SAPSID>/sapdata<n>
34/132
PUBLIC
2011-11-21
Planning
3.4
Description
sapdata directories, you can change this on the SAPinst
Sapdata Directories dialog.

Temporary tablespaces are equally distributed over the
sapdata directories. Make sure that you provide
enough free space in your sapdata directories for
temporary data.
For more information about the size, see the current
installation note [page 8] for DB2 for Linux, UNIX, and
Windows.
NOTE
:M In a production system, you must make

sure that the sapdata directories are located
in different file systems. Otherwise, system
performance can decrease. For more
information, see Data Safety and Performance
Considerations for Database Directories [page 39].
:M If you add additional sapdata directories
during the dialog phase of SAPinst, the
corresponding tablespace containers are
equally distributed.
File System Permissions
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].
Permissions
Owner
Group
/db2/<DBSID>
755
db2<dbsid>
db<dbsid>adm
755
db2<dbsid>
db<dbsid>adm
755
db2<dbsid>
db<dbsid>adm
:M With DB2's automatic storage

management:
750
db2<dbsid>
db<dbsid>adm
:M No automatic storage
management:
More Information
SAP Directories [page 49]
2011-11-21
PUBLIC
35/132
Planning
3.4
3.4.2 Users and Groups

SAPinst creates the following users and groups as shown in the following table:
User
Home Directory
Group
db2<dbsid>
/db2/db2<dbsid>
db<dbsid>adm
<sapsid>adm
can be chosen
sapsys (primary group),

db<dbsid>ctl (secondary)
Default Java database connect user:
/home/sap<sapsid>db
db<dbsid>mon (primary group)
sap<sapsid>db
You may change this user during

the installation.
NOTE
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.
3.4.3 Directory Structure of the DB2 Client Connectivity

With DB2 V9.1, a new DB2 client connectivity (also known as DB2 Thin Client) was introduced with
a new directory structure as shown in the following graphic:
p%dpW$k)ADirectory Structure of the Database Client
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.
3.4.4 DB2 Tablespaces

During the dialog phase of the installation, SAPinst offers to create the following tablespace types:
O`= Data and index tablespaces managed by DB2's automatic storage management (AutoStorage)
During the installation, SAPinst assigns the sapdata directories to the database, which
automatically distributes all tablespaces over the sapdata directories or file systems. In addition,
the database automatically adjusts the tablespace sizes as long as there is enough free space left in
the sapdata directories or file systems.
If one of the sapdata directories becomes full, new stripe sets are automatically created in the
remaining sapdata directories.
Since the DB2 database automatically creates and administers the tablespace containers, the overall
administration effort for the database decreases considerably using tablespaces managed by
automatic storage management.
NOTE
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
:r Other tablespace types

If you want to use other tablespace types, for example SMS or DMS DEVICE (raw devices), you have
to create them manually. Therefore, you deselect the option Create tablespaces with SAPinst during
the dialog phase of SAPinst and proceed as described in Creating Tablespaces Manually [page 106].
At a later point in time, you can switch between DMS FILE and DMS DEVICE tablespaces using DB2s
redirected restore tool. In addition, you can enable and disable autoresize mode for databases that are not
set up in AutoStorage mode.
To move tablespaces of a DB2 release lower than DB2 V9.7 from AutoStorage to other storage modes, you
have to perform a homogenous system copy. For more information, see the appropriate system copy
guide that is available at:
http://service.sap.com/instguides .
With DB2 V9.7 and higher, you can move tablespaces from DMS to AutoStorage.
Container Type FILE
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
3.4.5 Data Safety and Performance Considerations for

Production Systems
During the installation of a production SAP system, you should control the distribution of database
directories or file systems to physical disks. On Windows operating systems, you assign drive letters to
the system components when running the installation tool. On UNIX operating systems, this is done
when you create file systems before you start the installation tool. The way you distribute your database
components to disk can significantly affect system throughput and data security, and must therefore
be carefully planned.
NOTE
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:
I1 In an emergency situation you must be able to perform a rollforward recovery of your database in
a production system.
In a production system, the DB2 database must run in log retention mode. Otherwise, log files
cannot be applied to the database rollforward operations. You can set the database to log
retention mode by changing database configuration parameters at the very end of the installation
process. After changing the parameters, you are automatically forced to perform an offline backup.
Otherwise, you cannot reconnect to the database, which is reported with an error message.
For information, see Enabling Recoverability of the Database [page 95].
I1 Keep the tablespace container files in directories sapdata* and the online log directory log_dir
on separate disks to be able to perform a full rollforward recovery if a database container file is
damaged or lost.
I1 Since transaction data is lost if online log files are damaged, we recommend that the online log
directory log_dir is stored on redundant storage.
You can perform hardware mirroring using RAID adapters or intelligent storage systems. For
performance reasons, hardware solutions for mirroring should be preferred over mirroring
solutions like logical volume managers that are offered by operating systems.
In addition, the DB2 product offers dual log file mechanism. For more information, see SAP
Note 409127.
I1 A high transaction volume can cause high I/O on the online log files. Therefore, the distribution
of the online log files is a crucial factor of performance considerations. Ideally, the online log files
should be located on fast physical volumes that do not have high I/O load coming from other
components. This allows efficient logging activity with a minimum of overhead such as waiting
2011-11-21
PUBLIC
39/132
Planning
3.5
SAP System Transport Host
for I/O. You should avoid storing the online log files on the same physical volume as the operating
system paging space, or a physical volume with high I/O activity.
xLI By default, the SAP installation tool creates tablespaces that are managed by DB2s automatic storage
management (AutoStorage tablespaces). Tablespaces in AutoStorage mode offer maximum ease of use
and low administrative cost. In addition, modern file systems avoid most concurrency problems.
If you are not using AutoStorage tablespaces, you have detailed but manual control over the
distribution of data on disk.
If this is the case and if you want to enhance performance of large databases, we recommend that
you:
xLI Distribute heavily used tablespaces across separate disks.
xLI Avoid putting multiple containers of one tablespace onto the same device.
xLI Move heavily used tables into their own tablespaces that reside on dedicated disks.
xLI Put containers of index tablespaces and their respective data tablespaces on different disks.
xLI Do not configure operating system I/O (for example, swap, paging or heavily spool) on DB2
data disks.
xLI You can run DB2 databases with multiple page sizes in a single database. But once specified for a
tablespace, the page size cannot be changed. For each page size a separate buffer pool has to be
created in your database. During a standard installation, SAPinst creates the database with a uniform
page size of 16 KB. As a result only buffer pools with 16 KB have to be created and administered.
More Information
See the Administration Guide: Performance that you can access using the link in section Online Information from
IBM [page 124].
3.5 SAP System Transport Host

The 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:
xLI Use the transport directory that SAPinst creates during the installation of the SAP system by default
on the global host:
SAPinst by default creates the transport directory on the global host in /usr/sap/trans.
xLI Use a transport directory located on a host other than the default host:
xLI You can use an existing transport directory and host in your SAP system landscape.
xLI You can set up a new transport directory on a different host.
40/132
PUBLIC
2011-11-21
Planning
3.6
Planning the Switchover Cluster
In either case, you must prepare this host for use by the new SAP system. For more information,
see Exporting and Mounting the Global Transport Directory [page 67].
More Information
a Required File Systems and Directories [page 49]

a See the SAP Library [page 9]:
SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Software Logistics Change
and Transport System Change and Transport System Overview Basics of the Change and Transport System
Transport Management System Concept
3.6 Planning the Switchover Cluster

You can reduce unplanned downtime for your SAP system by setting up a switchover cluster. This
setup installs critical software units known as single points of failure (SPOFs) across multiple host
machines in the cluster. In the event of a failure on the primary node, proprietary switchover software
automatically switches the failed software unit to another hardware node in the cluster. Manual
intervention is not required. Applications accessing the failed software unit might experience a short
delay but can then resume processing as normal.
Switchover clusters also have the advantage that you can deliberately initiate switchover to free up a
particular node for planned system maintenance. Switchover solutions can protect against hardware
failure and operating system failure but not against human error, such as operator errors or faulty
application software. Additional downtime might be caused by upgrading your SAP system or applying
patches to it.
Without a switchover cluster, the SAP system SPOFs central services instance, the database instance,
and the central file share are vulnerable to failure because they cannot be replicated. All of these can
only exist once in a normal SAP system.
You can protect software units that are not SPOFs against failure by making them redundant, which
means simply installing multiple instances. For example, you can add additional application server
instances. This complements the switchover solution and is an essential part of building high availability
(HA) into your SAP system.
RECOMMENDATION
We recommend switchover clusters to improve the availability of your SAP system.

A switchover cluster consists of:
a A hardware cluster of two or more physically separate host machines to run multiple copies of
the critical software units, in an SAP system the SPOFs referred to above
a Switchover software to detect failure in a node and switch the affected software unit to the standby
node, where it can continue operating
2011-11-21
PUBLIC
41/132
Planning
3.6
T v
_ A mechanism to enable application software to seamlessly continue working with the switched
software unit normally this is achieved by virtual addressing (although identity switchover is
also possible)
Prerequisites
You must first discuss switchover clusters with your hardware partner because this is a complex
technical area. In particular, you need to choose a proprietary switchover product that works with
your operating system.
We recommend that you read the following documentation before you start:
T v
_ Check the information and the installation guides that are available at http://sdn.sap.com/irj/
sdn/ha.
T v
_ The enqueue replication server (ERS) is essential for a high-availability system. You need one ERS
for the Java SCS installed in your system.
T v
_ On database level, IBM provides a high-availability cluster solution for Linux and AIX only that is
called IBM Tivoli System Automation for Multiplatforms (SA MP). IBM also provides a free two-node license
of SA MP for the DB2 database server. The corresponding installation guide describes how to set
up a switchover cluster with SA MP based on the DB2 feature High Availability and Disaster
Recovery (HADR) or a shared disk.
More information:
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
Features
The following graphic shows the essential features of a switchover setup:
42/132
PUBLIC
2011-11-21
Planning
3.6
IUZ/uPSwitchover Setup
NOTE
This figure and the figures in this section are only examples. Only the instances relevant to the
switchover are shown for example, the primary application server instance is not shown.
These graphics summarize the overall setup and do not show the exact constellation for an
installation based on one of the available technologies (ABAP, ABAP+Java, or Java).
You need to discuss your individual HA setup with your HA partner.
The following graphic shows an example of a switchover cluster in more detail:
2011-11-21
PUBLIC
43/132
Planning
3.6
W@:5X#Switchover Cluster
Constraints
This documentation concentrates on the switchover solution for the central services instance. For
more information about how to protect the Network File System (NFS) software and the database
instance by using switchover software or (for of the database) replicated database servers, contact your
HA partner.
You need to make sure that your hardware is powerful enough and your configuration is robust enough
to handle the increased workload after a switchover. Some reduction in performance might be
acceptable after an emergency. However, it is not acceptable if the system comes to a standstill because
it is overloaded after switchover.
44/132
PUBLIC
2011-11-21
Preparation
4.1
Preparation Checklist
4 Preparation
4.1 Preparation Checklist

This section includes the preparation steps that you have to perform for the following installation
options:
R Standard, distributed, or high-availability system
R Additional application server instance
Detailed information about the steps is available in the relevant section.
NOTE
1.
2.
3.
4.
5.
6.
7.
8.
9.
You make sure that the required operating system users and groups [page 46] are created.
You set up file systems [page 49] and make sure that the required disk space is available for the
directories to be created during the installation.
If required, you set up virtual host names [page 56].
If you want to install a high-availability system, you perform switchover preparations [page 56].
If you want to share the transport directory trans from another system, export [page 67] this
directory to your installation hosts.
If you need to configure the User Management Engine (UME) of Application Server Java for the
user management of a separate ABAP system, you have to
prepare user management for an external ABAP System [page 57].
You make sure that the required installation media [page 59] are available on each host.
If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page
105].
You can continue with Installation [page 63] .
You have to perform the following preparations on the host where you install the additional application
server instances:
1. You make sure that the required operating system users and groups [page 46] are created.
2. You set up file systems [page 49] and make sure that the required disk space is available for the
directories to be created during the installation.
2011-11-21
PUBLIC
45/132
Preparation
4.2
Creating Operating System Users and Groups
3.
4.
5.
6.
If you want to use virtual host names, you have to set the environment variable
SAPINST_USE_HOSTNAME [page 56]. Alternatively you can specify the virtual host name in the
command to start SAPinst.
If you want to share the transport directory trans from another system, export [page 67] this
directory to your installation hosts.
You make sure that the required installation media [page 59] are available.
You can continue with Installation [page 63].
4.2 Creating Operating System Users and Groups

During the installation, SAPinst checks all required accounts (users, groups) and services on the local
machine. SAPinst checks whether the required users and groups already exist. If not, it creates new
users and groups as necessary.
If you do not want SAPinst to create operating systems users, groups, and services automatically, you
can optionally create them before the installation. This might be the case if you use central user
management such as Network Information System (NIS).
SAPinst checks if the required services are available on the host and creates them if necessary. See the
log messages about the service entries and adapt the network-wide (NIS) entries accordingly.
SAPinst checks the NIS users, groups, and services using NIS commands. However, SAPinst does not
change NIS configurations.
RECOMMENDATION
For a distributed or a high-availability system, we recommend that you distribute account

information (operating system users and groups) over the network, for example by using Network
Information Service (NIS).
If you want to use global accounts that are configured on a separate host, you can do this in one of the
following ways:
b,M You start SAPinst and choose Preparations Operating System Users and Groups . For more information,
see Running SAPinst [page 69].
b,M You create operating system users and groups manually. Make sure that you also check the settings
for these operating system users.
Constraints
b,M Make sure that you set the limits for operating system users as follows:
b," Using csh shell, the output of command limit needs to be as follows:
46/132
Output
Properties
cputime
unlimited
filesize
unlimited
PUBLIC
2011-11-21
Preparation
4.2

Output
Properties
datasize
unlimited
stacksize
8192 KB
coredumpsize
unlimited
descriptors
8192
memorysize
unlimited
>]djb Using sh or ksh shell, the output of command ulimit
-a needs to be as follows:
Output
Properties
time(seconds)
unlimited
file(blocks)
unlimited
data(kbytes)
unlimited
stack(kbytes)
8192
coredump(blocks)
unlimited
nofiles(descriptors)
8192
memory(KBytes)
unlimited
>]djb All users must have identical environment settings. If you change the environment delivered by
SAP, such as variables, paths, and so on, we do not assume responsibility.
>]djb Do not delete any shell initialization scripts in the home directory of the OS users. This applies
even if you do not intend to use the shells that these scripts are for.
>]djb If you install an SAP system with instances distributed over several hosts, make sure that the
following requirements are met:
>]djb Make sure that the group ID of group sapinst is always different from the group ID of any
other group (for example, of group sapsys) used during the installation.
For example, if you want to install an additional application server instance for an existing SAP
system, you must make sure that the group ID of group sapinst created on the host of the
additional application server instance is different from the group ID of any other group on
the primary application server instance host of the existing SAP system.
>]djb If you use local operating system user accounts instead of central user management (for
example, NIS), user <sapsid>adm, sapadm, and the database operating system user must have
the same password on all hosts.
>]djb The user ID (UID) and group ID (GID) of each operating system user and group must be
identical for all servers belonging to the same SAP system.
This does not mean that all users and groups have to be installed on all SAP servers.
>]djb If operating system users already exist, make sure that they are assigned to group sapinst.
>]djb If you create operating system users manually or use already existing operating system users, make
sure that the home directory for each of these users is not the root directory ( / ) .
>]djb Make sure that the home directory of user <sapsid>adm is not critical for recursive changes on
permissions:
2011-11-21
PUBLIC
47/132
Preparation
4.2
When operating system users are created by the installer, the permissions on the home directories
of these users are changed recursively. This can cause unpredictable errors if you define a critical
home directory.
For example, the home directory must not be / or /usr/sap.
Operating System Users and Groups
SAPinst chooses available operating system user IDs and group IDs unless you are installing an additional
application server instance. On an additional application server instance you have to enter the same
IDs as on the host of the primary application server instance.
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.
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.
Users and Groups
User
Primary Group
Superuser of the UNIX operating system root
No primary group is assigned by SAPinst (additional

group is sapinst)
sapsys (db<dbsid>ctl as secondary group)
sapsys (sapinst as secondary group)
sapsys (sapinst as secondary group)
SAP system administrator<sapsid>adm

Host Agent administrator sapadm
Diagnostics Agent user <dasid>adm
Java connect user sap<sapsid>db
db<dbsid>mon
NOTE
Only used on the database host.

db<dbsid>adm (sapinst as secondary group)
db2<dbsid>
NOTE
Only used on the database host.

User and Groups of the Host Agent
User
Primary Group
Additional Group
Comment
sapadm
sapsys
sapinst
Host Agent administrator
Groups and Members

Groups
Members
sapsys
<sapsid>adm, sapadm, <dasid>adm
sapinst
root, <sapsid>adm, sapadm, <dasid>adm, db2<dbsid>
db<dbsid>ctl
<sapsid>adm
db<dbsid>adm
db2<dbsid>
db<dbsid>mon
Java connect user sap<sapsid>db
48/132
PUBLIC
2011-11-21
Preparation
4.3
Required File Systems and Directories
Groups and Members of the Host Agent User

Groups
Members
sapsys
sapadm
sapinst
sapadm
4.3 Required File Systems and Directories

The following sections describe the directory structures for the SAP system, how to set up SAP file
systems for the SAP system and, if required, raw devices on operating system level:
NOTE
The installation of any SAP system does not require a special file system setup or separate partitions.
+ SAP Directories [page 49]
+ Performing Switchover Preparations for High Availability [page 56]
+ Setting Up File Systems for High-Availability [page 54]
4.3.1 SAP Directories

Depending on the installation option you have chosen, SAPinst automatically creates the directories
listed in the following figures and tables. Before running the installation, you have to set up the required
file systems manually. In addition, you have to make sure that the required disk space for the directories
to be installed is available on the relevant hard disks. The figure below assumes that you have set up
one file system for the SAP system mount directory <sapmnt> and one file system for the /usr/sap
directory. However, you have to decide for which directories you want to set up separate file systems.
If you do not set up any file system on your installation host, SAPinst creates all directories in the root
directory ( / ). SAPinst prompts you only for the <sapmnt> directory during the installation. See also
table Parameters Relevant for the File System in Basic SAP System Installation Parameters [page 25].
SAPinst creates the following types of directories:
+ Physically shared directories for the SAP system
+ Logically shared directories for the SAP system and the diagnostics agent
+ Local directories for the SAP system and the diagnostics agent
The following figure shows the directory structure of the SAP system:
2011-11-21
PUBLIC
49/132
Preparation
4.3
q^B/FTTU`:Directory Structure for a Java System

Physically Shared Directories (SAP System)
Physically shared directories reside on the global host and are shared by Network File System (NFS).
SAPinst creates the following directories:
q The directory /<sapmnt>/<SAPSID>, which contains SAP kernel and related files, is created on the
first installation host. Normally, the first installation host is the host on which the central services
instance is to run, but you can also choose another host for /<sapmnt>/<SAPSID>.
You need to manually share this directory with Network File System (NFS) and for a distributed
system such as a HA System or a system with dialog instances mount it from the other installation
hosts.
SAPinst creates the following shared directories during the SAP system installation. If you install
an SAP system with instances distributed over several hosts, you have to share these directories for
all hosts with the same operating system (see Exporting and Mounting Global Directories [page 68]):
q
global
Contains globally shared data and database-specific directories. For more information,
see<Link>
q
profile
Contains the profiles of all instances

q
exe
Contains executable kernel programs

q The directory /usr/sap/trans, which is the global transport directory.
50/132
PUBLIC
2011-11-21
Preparation
4.3
If you want to use an existing transport directory, you have to mount it before you install the
application server instance in question. Otherwise SAPinst creates /usr/sap/trans locally.
For more information, see Exporting and Mounting the Global Transport Directory [page 67]
Physically Shared SAP Directories
Directory
Required Minimum Disk Space
<sapmnt>/SAPSID>
Minimum 2 GB
This value heavily depends on the use of your SAP system.
For production systems, we recommended to use as much free space as available (at least
2.0 GB), because the space requirement normally grows dynamically.
For the installation, it is sufficient to use 1 GB for each SAP system instance. You can enlarge
the file system afterwards.
/usr/sap/trans
Logically Shared Directories (SAP System)
Logically shared directories reside on the local hosts with symbolic links to the global host. SAPinst
creates the directory /usr/sap/<SAPSID>/SYS on each host. The subdirectories contain symbolic links
to the corresponding subdirectories of /<sapmnt>/<SAPSID> on the first installation host, as shown in
the figure above.
Whenever a local instance is started, the sapcpe program checks the executables against those in the
logically shared directories and, if necessary, replicates them to the local instance.
SAPinst uses sapcpe to replicate the kernel automatically from /usr/sap/<SAPSID>/SYS/exe/run/
DIR_CT_RUN to /usr/sap/<SAPSID>/<INSTANCE/exe/DIR_EXECUTABLE for each SAP system instance,
where <INSTANCE> is either DVEBMGS<Number> (central instance) or D<Number> (dialog instance)
Local Directories (SAP System)
SAPinst also creates local directories that reside on the local hosts. The directory /usr/sap/<SAPSID>
contains files for the operation of a local instance as well as symbolic links to the data for one system.
This directory is physically located on each host in the SAP system and contains the following
subdirectories:
.i]
SYS
NOTE
The subdirectories of /usr/sap/<SAPSID>/SYS have symbolic links to the corresponding

subdirectories of /<sapmnt>/<SAPSID>, as shown in the figure above.
.i] Instance-specific directories with the following names:
.i] The directory of an application server instance (primary application server instance or
additional application server instance) is called J<No>.
.i] The directory of the central services instance for Java (SCS instance) is called SCS<No>, where
<No> is the instance number.
.i] The directory of an enqueue replication server instance (ERS instance) is called ERS<No>, where
<No> is the instance number.
2011-11-21
PUBLIC
51/132
Preparation
4.3
The ERS instance can be installed for the SCS instance. If you install a high-availability system, you
must install an ERS instance for the SCS instance
Local SAP Directories
Required Minimum
Disk Space
Directory
Description
/usr/sap/<SAPSID>/J<No>
Application server instance directory

Minimum 6 GB
(primary application server instance or
additional application server instance)
Java central services instance (SCS) directory 1 GB
Enqueue replication server instance (ERS) 1 GB
directory for the SCS (high-availability only)
/usr/sap/<SAPSID>/SCS<No>
/usr/sap/<SAPSID>/ERS<No>
Local Directories (Diagnostics Agent)
The diagnostics agent has logically shared and local directories as shown in the following figure.
B9VZ}h
Wx;<C,Directory Structure for the Diagnostics Agent
The diagnostics agent directory /usr/sap/<DASID> requires 1.5 GB of disk space. It contains the
following subdirectories:
B9 SYS, which is a logically shared directory
B9 SMDA<No>, which is a local directory
Logically Shared Directories (Diagnostics Agent)
The logically shared directory SYS contains the following subdirectories:

B9
exe
52/132
PUBLIC
2011-11-21
Preparation
4.3

uo
global
Contains globally shared data

uo
profile
Contains the profiles of the Diagnostics Agent instance

Local Directories (Diagnostics Agent)
The local directory SMDA<No> contains the following subdirectories:

The instance directory of the Diagnostics Agent instance is called SMDA<No>, where <No> is the instance
number. It contains the instance-specific data of the Diagnostics Agent.
It contains the following subdirectories:
uo
script
Contains the smdsetup script

uo
SMDAgent
Contains the Diagnostics Agent software and properties files

uo
exe

uo
work
Contains log files

Directories of the Host Agent
The host agent has only local directories as shown in the following figure:
u-J"=1Mvza+YDirectory Structure for the Host Agent
2011-11-21
PUBLIC
53/132
Preparation
4.3
Local Directories (Host Agent)
The host agent directory /usr/sap/hostctrl requires 100 MB of disk space. It contains the following
subdirectories:
G/
exe
Contains the profile host_profile

G/
work
Working directory of the host agent
4.3.2 Setting Up File Systems for a High-Availability System

Third-party technology is used to make the SAP directories available to the SAP system. The
technologies of choice are NFS, shared disks, and cluster file system. If you have decided to use a highavailability (HA) solution for your SAP system, make sure that you properly address the HA
requirements of the SAP file systems in your SAP environment with the HA partner of your choice.
From the perspective of an SAP application, there are the following types of SAP Directories [page 49]:
G/ Physically shared directories: /<sapmnt>/<SAPSID> and /usr/sap/trans
G/ Logically shared directories that are bound to a node such as /usr/sap with the following local
directories:
G@ /usr/sap/<SAPSID>
G@ /usr/sap/<SAPSID>/SYS
G@ /usr/sap/hostctrl
G/ Local directories that contain the SAP instances, such as /usr/sap/<SAPSID>/SCS<NR>
Prerequisites
You have already installed the hardware that is, hosts, disks, and network and decided how to
distribute the database, SAP instances, and if required Network File System (NFS) server over the
cluster nodes (that is, over the host machines). For more information, see Planning the Switchover Cluster
[page 41] and contact your HA partner.
Procedure
1.
Create the file systems or raw partitions for the SAP instances you can switch over in such a way
that the content can be made available to all nodes that can run the service. At least the central
services (SCS) instance must be part of the switchover cluster.
The SAP directories /sapmnt/<SAPSID> and /usr/sap/trans are usually mounted from a Network
File System (NFS). However, an SAP instance directory /usr/sap/<SAPSID>/<INSTTYPE><NR> that
you want to prepare for HA has to be always mounted on the cluster node currently running the
instance. Do not mount such directories with NFS.
54/132
PUBLIC
2011-11-21
Preparation
4.3
Therefore, if the host running the primary application server instance is not the NFS server host,
you might have to mount the file systems for /sapmnt/<SAPSID> and /usr/sap/trans on
different physical disks from the file system for /usr/sap/<SAPSID>/<INSTTYPE><NR>.
CAUTION
2.
To start or stop an SAP instance, you have to either make the physically shared SAP directories
under /<sapmnt>/<SAPSID>/ available to the server beforehand or you have to replace the
links in /usr/sap/<SAPSID>/SYS by a physical copy. Consult your HA partner to clarify the
best solution for the cluster software.
Use the following approach for the file system for the /usr/sap/<SAPSID> directory:
The /usr/sap/<SAPSID> directory contains at least two subdirectories (see also SAP Directories [page
49]):
oh* SYS, which contains links to the central directory /sapmnt/<SAPSID>
oh* <INSTTYPE><Number> where the name is defined by the type of services and the application
server number:
oh*i J<Number> which contains data of an application server instance
oh*i SCS<Number> which contains data for the Java central services instance
Only <INSTTYPE><Number> directories need to be migrated with the SAP instances during the
switchover.
Therefore, instead of /usr/sap/<SAPSID>, create a file system for /usr/sap/<SAPSID>/
<INSTTYPE><Number> with the usual <> substitutions.
The instance-specific directory name for the central services instance is normally SCS<Number>.
Migrating only this directory avoids mount conflicts when switching over to a node on which
another AS instance is already running. The SCS<Number> directory can join the /usr/sap/
<SAPSID> tree instead of mounting on top of it.
NOTE
3.
4.
This approach becomes increasingly important when you want to cluster the central services
instances with other local instances running on the cluster hosts outside the control of the
switchover software. This applies to the Enqueue Replication Server (ERS) and additional
ABAP or Java application server instances. The result is a more efficient use of resources. You
must use this approach for integrated installations of the application server with ABAP and
Java stacks.
You assign the local (not switching) file systems to permanent mount points.
You assign the shared file systems as documented by your HA partner.
EXAMPLE
The graphic below shows an example of the file systems and disks in an HA setup
Note that this is only an example. For more information on a setup that meets your needs, consult
your HA partner.
2011-11-21
PUBLIC
55/132
Preparation
4.4
Using Virtual Host Names
P"Bu{'rFile Systems and Disks in an HA Setup
4.4 Using Virtual Host Names

You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to
conceal their physical network identities from each other. This can be useful when quickly moving
SAP servers or complete server landscapes to alternative hardware without having to reinstall or
reconfigure.
If you want to install a high-availability (HA) system [page 13], you need the virtual host name when you
install the SCS instance into a cluster.
Prerequisites
Make sure that the virtual host name can be correctly resolved in your Domain Name System (DNS)
setup.
Procedure
Proceed as described in SAP Note 962955.
4.5 Performing Switchover Preparations for High Availability

To be able to use the required virtual host names [page 56], you have to set the SAPinst
propertySAPINST_USE_HOSTNAME to specify the required virtual host name before you start SAPinst. For
more information, see Running SAPinst [page 69].
56/132
PUBLIC
2011-11-21
Preparation
4.6
Preparing an External ABAP System as Source for User Data
Procedure
Assign the virtual IP addresses and host names for the SCS instance, and (if required) NFS to appropriate
failover groups.
NOTE
For more information on virtual addresses and virtual host names and how to assign resources
to failover groups, ask your HA partner.
4.6 Preparing an External ABAP System as Source for User

Data
You can use an external ABAP system as the data source for user data for the Application Server Java
of your SAP Java system to be installed. To do so, you configure the User Management Engine (UME)
of the Java EE Engine for the user management of this external ABAP system.
If you want to connect more than one Java system to the same ABAP system, you need to work out a
concept for the communication, administrator, and guest users for each system.
You can take one of the following approaches when using an external ABAP system as source for user
data:
Approach
Advantages
Each Java system uses

different users
Disadvantages
No interdependencies
between the connected
engines
All Java systems use the You create the users only
same configuration
once and enter the same
information for every Java
system that you install.
Initially more administration to create the users in the

ABAP system
Interdependencies between the connected engines:
Y# If you change the password of any of the users on
the ABAP system, this change affects all connected
engines.
Y# If you change the administrator users password,
you must also change the password in secure
storage on all of the connected Java EE Engines
RECOMMENDATION
For security reasons, we recommend the first approach.

The procedures below assume that you are using the first approach.
Prerequisites
The ABAP system is based on at least SAP Web AS ABAP release 6.20 SP25.
Procedure
The following procedures describe the activities you have to perform in the existing ABAP system and
for the Java system to be installed.
2011-11-21
PUBLIC
57/132
Preparation
4.6
Preparing an External ABAP System as Source for User Data
Activities in the Existing ABAP System
1.
2.
3.
Call transaction PFCG to do the following:

G6B Check that the roles SAP_BC_JSF_COMMUNICATION and SAP_BC_JSF_COMMUNICATION_RO exist
and make sure that their profiles are generated.
G6B Check that the roles SAP_J2EE_ADMIN, SAP_J2EE_GUEST and SAP_BC_FP_ICF exist. Neither role
contains any ABAP permissions, so you do not need to generate any profiles.
Call transaction SU01 to do the following:
G6B Create a new communication user and assign it to the role SAP_BC_JSF_COMMUNICATION_RO.
We recommend that you do the following:
G6- Name this user SAPJSF. You can use any password.
G6- Assign this user the role SAP_BC_JSF_COMMUNICATION_RO for read-only (display) access to
user data with Java tools. If you intend to maintain user data (that is, to change, create,
or delete users) with Java tools, you need to assign the role SAP_BC_JSF_COMMUNICATION
instead.
G6- Assign this user the type Communications under Logon data to make sure that it can only be
used for communication connections between systems and not as a dialog user.
G6B Create a new administrator user for the Java EE Engine and assign it to role SAP_J2EE_ADMIN.
We recommend that you name the user J2EE_ADM_<SAPSID_Java_System>. You can use any
password.
G6B Create a new guest user for the Java EE Engine and assign it to role SAP_J2EE_GUEST. We
recommend that you name the user J2EE_GST_<SAPSID_Java_System>. You can use any
password.
Since this user is only used for anonymous access to the system, we recommend you to
deactivate the password and, if required, lock it after installation to prevent anyone from using
it for explicit named logons.
Make sure that you change the initial passwords of these users and taken the precautions described
in the relevant SAP security guide before you start the installation of the Java system. You can
find the security guides at http://service.sap.com/securityguide.
Activities for the Java System
1.
2.
Before the installation of the Java system, make sure that you have the correct user names and
passwords of the users listed above for the separate ABAP system.
During the installation of the Java system, make sure that you enter the correct users and
passwords in the corresponding SAPinst dialogs.
More Information
G6B For more information about UME, see the SAP Library [page 9] at:
Function-Oriented View Security Identity Management User Management of the Application Server Java
User Management Engine
58/132
PUBLIC
2011-11-21
Preparation
4.7
Preparing the Installation Media
_S{ For more information about role maintenance, see the SAP Library [page 9] at:
Function-Oriented View Security Identity Management User and Role Administration of Application Server
ABAP AS ABAP Authorization Concept
4.7 Preparing the Installation Media

This section describes how to prepare the installation media, which are available as follows:
_S{ You normally obtain the physical installation media as part of the installation package.
_S{ You can also download the installation media from SAP Service Marketplace, as described at the
end of this section.
Procedure
1.
Identify the required media for your installation [page 11] as listed below.
NOTE
The media names listed below are abbreviated. You can find the full names of all media
shipped with SAP NetWeaver 7.3 including Enhancement Package 1 in the document Media
List SAP NetWeaver 7.3 including Enhancement Package 1 on SAP Service Marketplace at http://
service.sap.com/installnw73
SAP Instance
Installation
Central
services
instance for
Java (SCS)
Database
instance
Required Software Packages from Media
_S{ Installation Master (folder <Product>_IM_<OS>_<DB>)

_S{ UC Kernel (folder K_U_<Version>_<OS>) where U means Unicode.

_S{ Installation media for the RDBMS and the CLI / JDBC driver
CAUTION
_S For the installation of your SAP system, only the English version of DB2
V9.7 is supported.
_S You must only use the DB2 V9.7 software provided by the SAP
installation media.
SAP
NetWeaver
Java Component (folders JAVA_*)
_S{
_S{ SAP Business Suite Java Applications only: SAP Business Suite Java Content
(folders JAVA_*)
NOTE
Enqueue
Replication
Server
Primary
application
2011-11-21
For an MCOD system you require the database client software instead of the database
software and the database patches (if available).
PUBLIC
59/132
Preparation
4.7

SAP Instance
Installation
Required Software Packages from Media
server
instance
]xg" UC or NUC Kernel (folder K_<N

N means non-Unicode.
or U>_<Version>_<OS>) where U means Unicode and
NOTE
]xg"
]xg"
]xg"
]xg"
]xg"
Every new installation of an SAP system is Unicode. You can only use the nonUnicode kernel if you perform the system copy for a non-Unicode SAP system
that has been upgraded to the current release.
UC Kernel (folder K_U_<Version>_<OS>) where U means Unicode.
SAP NetWeaver Java Component (folders JAVA_*)
SAP Business Suite Java Applications only: SAP Business Suite Java Content
(folders JAVA_*)
Database Client Software
CLI Driver / JDBC Driver
CAUTION
Additional
application
server
instance
]xg"
]xg"
]xg"
]xg"
]xg"
You must only use the DB2 software provided by the SAP installation
media.
Installation Master (folder <Product>_IM_<OS>_<DB>)
UC Kernel (folder K_U_<Version>_<OS>) where U means Unicode.
SAP NetWeaver Java Component (folders JAVA_*)
SAP Business Suite Java Applications only: SAP Business Suite Java Content
(folders JAVA_*)
CLI Driver / JDBC Driver
CAUTION
You must only use the DB2 software provided by the SAP installation
media.
2.
Make the required installation media available on each installation host.

You can do this in one of the following ways:
]xg" Copy the required media folders directly to the installation hosts.
]xg" Mount media on a central media server that can be accessed from the installation hosts.
CAUTION
If you copy the media to disk, make sure that the paths to the destination location of the
copied media do not contain any blanks.
Downloading Installation Media from SAP Service Marketplace
You normally obtain the installation media as part of the installation package from SAP.
However, you can also download installation media from the software distribution center on SAP
Service Marketplace using one of the following paths:
]xg" http://service.sap.com/swdc Installations and Upgrades My companys application components
<your product> <your product version>
]xg" http://service.sap.com/swdc Installations and Upgrades A-Z index <first letter of your product>
<your product version>
60/132
PUBLIC
2011-11-21
Preparation
4.7

NOTE
If you download installation media, note that they might be split into several files. In this case,
you have to reassemble the required files after the download.
1.
2.
Create a download directory on the host on which you want to run SAPinst.
Identify all download objects that belong to one installation medium according to one or both of
the following:
VJ1"k Material number
All download objects that are part of an installation medium have the same material number
and an individual sequence number:
<material_number>_<sequence_number>
EXAMPLE
51031387_1
51031387_2
...
3.
4.
VJ1"k Title
All objects that are part of an installation medium have the same title, such as
<solution><media_name><OS> or <database>RDBMS<OS> for database media.
Download the objects to the download directory.
To correctly re-combine the media that are split into small parts, you must unpack all parts into
the same directory.
In the unpacking directory, the system creates a subdirectory with a short text describing the
medium and copies the data into it. The data is now all in the correct directory, the same as on the
medium that was physically produced. For more information, see SAP Note 1258173.
2011-11-21
PUBLIC
61/132

Installation
5.1
Installation Checklist
5 Installation
5.1 Installation Checklist

This section includes the installation steps that you have to perform for the:
ko Standard system
ko Distributed system
ko High-availability system
ko Additional application server instance
Standard System
1.
You install the SAP system with SAPinst [page 69].

NOTE
2.
In a standard system, all mandatory instances are installed on one host in one installation
run.
You continue with Post-Installation [page 87].
Distributed System
1.
2.
3.
4.
If you want to share the transport directory trans from another system, you have to mount [page
67] it from this system. Otherwise, we recommend that you share the trans directory that is
created during the installation of the primary application server instance.
On the host with the global file system (SAP global host), you do the following:
1. You run SAPinst [page 69] to install the central services instance for Java (SCS) and optionally
the enqueue replication server instance (ERS) for the SCS..
2. You export global directories [page 68] in <sapmnt>/<SAPSID> to the database and primary
application server instance host.
On the database instance host, you do the following:
1. You mount the global directories [page 68] in <sapmnt>/<SAPSID> that you exported from the SAP
global host and optionally the trans directory that you exported [page 67] from the SAP
transport host.
2. You run SAPinst [page 69] to install the database instance.
On the primary application server instance host, you do the following:
global host.
2. You run SAPinst [page 69] to install the primary application server instance.
2011-11-21
PUBLIC
63/132
Installation
5.1
3.
5.
If you want to use the shared transport directory trans from another system, you also mount
[page 67] this directory.
Graphical Overview
The following figure shows how you install the various instances in a distributed system:
}kH :H_gDistribution of Instances in a Java System

1.
2.
3.
You need to make sure that you have already prepared the standby node, host B. You ought to
have already made sure that it meets the hardware and software requirements and that it has all
the necessary file systems, mount points, and (if required) Network File System (NFS). This is
described in Performing Switchover Preparations for High Availability [page 56] and Setting Up File Systems for a
High Availability System [page 54].
67] it from this system. Otherwise we recommend that you share the trans directory that is created
during the installation of the primary application server instance (see below).
You set up the switchover cluster infrastructure as follows:
1. You run SAPinst [page 69] to install the central services instance for Java (SCS) and the related
enqueue replication server instance (ERS) using the virtual host name [page 56] on the primary
cluster node, host A.
2. You export global directories [page 68] in <sapmnt>/<SAPSID> to the database host and to the
primary application server instance host.
64/132
PUBLIC
2011-11-21
Installation
5.1
You prepare the standby cluster node, host B, making sure that it meets the hardware and software
requirements [page 20] and it has all the necessary file systems [page 54], mount points, and (if
required) Network File System (NFS).
4. You set up the user environment on the standby node, host B.
R You make sure that you use the same user and group IDs as on the primary node.
R You create the home directories of users and copy all files from the home directory of the
primary node.
For more information about the required operating system users and groups, see Creating
Operating System Users [page 46].
5. You configure the switchover software and test that switchover functions correctly to all
standby nodes in the cluster.
6. You repeat the following steps until you have finished installing the enqueue replication server
(ERS) on all nodes in the cluster:
1. You perform the switchover to a node where you want to install the enqueue replication
server instance (ERS) for the SCS.
2. You run SAPinst [page 69] to install the enqueue replication server instance (ERS) for the
SCS.
7. You perform the switchover to a node where you want to install the enqueue replication
server instance (ERS) for the SCS.
8. You run SAPinst [page 69] to install the enqueue replication server instance (ERS) for the SCS.
9. You repeat the previous two steps for all nodes in the cluster.
On the database instance host, you do the following:
3.
4.
RECOMMENDATION
We recommend that the database instance is part of the hardware cluster or of any other
proprietary high-availability solution for the database.
1.
5.
You make available the global directories in <sapmnt>/<SAPSID> from the switchover cluster
infrastructure and optionally from the SAP transport host.
2. You run SAPinst [page 69] to install the database instance on the database instance host.
On the primary application server instance host, you do the following:
NOTE
In a high-availability installation, the primary application server instance does not need to
be part of the cluster because it is no longer a single point of failure (SPOF). The SPOF is now
in the central services instance (SCS), which is protected by the cluster.
1.
2.
You mount the global directories [page 68] in <sapmnt>/<SAPSID> that you exported from the
switchover cluster infrastructure.
You run SAPinst [page 69] to install the primary application server instance.
2011-11-21
PUBLIC
65/132
Installation
5.1
3.
6.
7.
If you want to use the shared transport directory trans from another system, you also mount
[page 67] this directory (see above).
We recommend you to install additional application server (AS) instances with SAPinst to create
redundancy.
The AS instances are not a SPOF. Therefore, you do not need to include these instances in the
cluster.
Graphical Overview
The following figure provides an overview of how you install the various instances in a high-availability
installation:
&yFd&N_SDistribution of Instances in a High-Availability Java System

Installation Steps for Additional Application Server Instances for a Standard System
1.
2.
3.
On the main host on which your SAP system runs, you export global directories in <sapmnt>/
<SAPSID> to the database and primary application server instance host.
On every additional application server instance host, you do the following:
global host.
2. You run SAPinst [page 69] to install the additional application server instance.
66/132
PUBLIC
2011-11-21
Installation
5.2
Exporting and Mounting the Global Transport Directory
Installation Steps for an Application Server Instance for a Distributed System
1.
2.
3.
4.
On the SAP global host, you export global directories in <sapmnt>/<SAPSID> to the database and
primary application server instance host.
global host.
3. If you want to use the shared transport directory trans from another system, also mount [page
67] this directory.
Installation Steps for an Additional Application Server Instance for a High-Availability System
1.
2.
3.
4.
On the primary node, host A, of the switchover cluster infrastructure, you export global
directories in <sapmnt>/<SAPSID> to every additional application server instance host.
global host.
3. If you want to use the shared transport directory trans from another system, you also mount
[page 67] this directory.
5.2 Exporting and Mounting the Global Transport Directory

In your SAP system landscape, a global transport directory for all SAP systems is required.
The global transport directory is used by the Change and Transport System (CTS). The CTS helps you
to organize development projects, and then transport the changes between the SAP systems in your
system landscape.
For more information, see the SAP Library [page 9] at:
Administrators Guide Technical Operations Manual for SAP NetWeaver General Administration Tasks Software
Life Cycle Management Software Logistics Change and Transport System Change and Transport System
Overview
2011-11-21
PUBLIC
67/132
Installation
5.3
Exporting and Mounting Global Directories
Yw If the global transport directory already exists, make sure that it is exported on the global transport
directory host and mount it on the SAP instance installation host.
Yw If the global transport directory does not exist, proceed as follows:
Yw Create the transport directory (either on the host where the primary application server
instance is running or on a file server).
Yw Export it on the global transport directory host.
Yw If you did not create the transport directory on your SAP instance installation host, mount it
there.
Procedure
Exporting the Transport Directory
1.
2.
3.
Log on as user root to the host where the global transport directory /usr/sap/trans resides.
Make sure that /usr/sap/trans belongs to the group sapsys and to the user root.
If not already done, export the directory using Network File System (NFS).
Mounting the Transport Directory

NOTE
If the transport directory resides on your local SAP instance installation host, you do not need to
mount it.
1.
2.
3.
Log on as user root to the host of the primary or additional application server instance, where /
usr/sap/trans is to be mounted.
Create the mount point /usr/sap/trans.
Mount /usr/sap/trans using Network File System (NFS) from the exporting host.
5.3 Exporting and Mounting Global Directories

If you install a database or an additional application server instance on a host other than the SAP Global
host, you must mount global directories from the SAP Global host.
NOTE
There is no need to create the directories prior to the installation when you install a Central
System. The global directories must be exported only in case of installing additional dialog
instances.
Prerequisites
If you want to install the executables locally instead of sharing them, do not mount the exe directory
with Network File System (NFS). Instead, create <sapmnt>/<SAPSID>/exe as a local directory (not a
link) with a minimum of 1.5 GB free space.
68/132
PUBLIC
2011-11-21
Installation
5.4
Running SAPinst
Procedure
1.
Log on to the SAP Global host as user root and export the following directories with root access
to the host where you want to install the new instance:
<sapmnt>/<SAPSID>/exe
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
2.
3.
Make sure that the user root of the host where you want to install the new instance can access the
exported directories.
Log on to the host of the new instance that you want to install as user root.
Create the following mount points and mount them from the SAP Global host:
<sapmnt>/<SAPSID>/exe
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
CAUTION
Make sure that the mount points under /<sapmnt>/<SAPSID>/ are permanent. Otherwise
automatic start of the instance services does not work when you reboot the system.
5.4 Running SAPinst

This section describes how to run the installation tool SAPinst. SAPinst includes a GUI client and a GUI
server, which both use Java. In the following, GUI client and GUI server are called SAPinst GUI.
This procedure describes an installation where SAPinst and SAPinst GUI are running on the same host.
If you need to see the installation on a remote display, we recommend that you perform a remote installation
with SAPinst [page 79], where the SAPinst GUI is running on a separate host from SAPinst.
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations. For more information, see SAP Note 1170809.
Useful Information About SAPinst
BJ SAPinst creates the installation directory sapinst_instdir directly below the temporary directory.
SAPinst finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR
environment variable. If no value is set for these variables, SAPinst uses /tmp as default installation
directory.
If you want to use an alternative installation directory, set the environment variable TEMP, TMP,
or TMPDIR to the required directory before you start SAPinst.
Shell Used
Command
Bourne shell (sh)
TEMP=<directory>
export TEMP
C shell (csh)
Korn shell (ksh)
2011-11-21
setenv TEMP <directory>

export TEMP=<directory>
PUBLIC
69/132
Installation
5.4
Running SAPinst
CAUTION
Make sure that the installation directory is not mounted with NFS, otherwise there might
be problems when the Java Virtual Machine is started.
J B| SAPinst creates a subdirectory for each installation option called <sapinst_instdir>/
<installation_option_directory>.
J B| SAPinst extracts itself to the temporary directory. These executables are deleted again after SAPinst
has stopped running.
Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You
can safely delete them.
The temporary directory also contains the log file dev_selfex.out from the extraction process,
which might be useful if an error occurs.
CAUTION
If SAPinst cannot find a temporary directory, the installation terminates with the error
FCO-00058.
J B| During the installation, the default ports 21200, 21212, and 4239 are used for communication
between SAPinst, GUI server, SAPinst GUI, and HTTP server, as follows:
J B|} SAPinst uses port 21200 to communicate with the GUI server.
J B|} The GUI server uses port 21212 to communicate with the GUI client.
J B|} 4239 is the port of the HTTP server, which is part of the GUI server.
If these ports are already in use, SAPinst automatically searches for free port numbers. If the search
fails, you see an error message and SAPinst exits.
In this case or if you want SAPinst to use specific ports, you can assign them by executing the
sapinst executable with the following parameters:
J B|} SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>
J B|} GUISERVER_DIALOG_PORT=<port_number_gui_server_to_gui_client>
J B|} GUISERVER_HTTP_PORT=<port_number_http_server>
J B| To see a list of all available SAPinst properties, start SAPinst as described above with the option p:
./sapinst -p.
J B| If you need to run SAPinst in accessibility mode, proceed as described in Running SAPinst in Accessibility
Mode [page 83].
J B| If required, you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu.
NOTE
If you need to terminate SAPinst, you can do this by pressing
Ctrl
Prerequisites
J B| We recommend that you use the csh shell for the installation with SAPinst. If you want to use
another shell, make sure that you have read SAP Note 202227.
70/132
PUBLIC
2011-11-21
Installation
5.4
Running SAPinst
SAPinst uses csh scripts during the installation to obtain the environment for user <sapsid>adm.
This is also true if user <sapsid>adm already exists from an earlier SAP system installation, and the
shell of this user is not csh. Before you start SAPinst, execute the following command as user
<sapsid>adm to make sure that the csh scripts are up-to-date:
/bin/csh -c "source /<home>/<sapsid>adm/.cshrc;env"
4|t Make sure that your operating system does not delete the contents of the temporary directory /
tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example
by using a crontab entry.
Make sure that the temporary directory has the permissions 1777.
4|t Make sure that you have at least 300 MB of free space in the installation directory for each installation
option. In addition, you need 300 MB free space for the SAPinst executables. If you cannot provide
300 MB free space in the temporary directory, you can set one of the environment variables TEMP,
TMP, or TMPDIR to another directory with 300 MB free space for the SAPinst executables.
You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation
directory as described above in section Useful Information About SAPinst.
4|t Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where
<host_name> is the host on which you want to display the SAPinst GUI.
You can set values for the DISPLAY environment variables as follows:
Shell Used
Command
Bourne shell (sh)
DISPLAY=<host_name>:0.0
export DISPLAY
C shell (csh)
Korn shell (ksh)
setenv DISPLAY <host_name>:0.0

export DISPLAY=<host_name>:0.0
4|t Make sure that umask is set to 022 for user root.
As user root, enter the following command: umask 022
4|t Make sure that you have checked the following values for user root:
4|t In csh, execute limit
Output
Properties
cputime
unlimited
filesize
unlimited
datasize
unlimited
stacksize
8192 KB
coredumpsize
unlimited
descriptors
8192
memorysize
unlimited
4|t In sh or ksh execute ulimit
-a
Output
Properties
time(seconds)
unlimited
file(blocks)
unlimited
2011-11-21
PUBLIC
71/132
Installation
5.4
Running SAPinst
Output
Properties
data(kbytes)
unlimited
stack(kbytes)
8192
coredump(blocks)
unlimited
nofiles(descriptors)
8192
memory(KBytes)
unlimited
If your parameter settings differ from the settings above, change these values accordingly.
EXAMPLE
If you have to change the value for descriptors to 8192, proceed as follows:
o In csh execute:
limit descriptors 8192
o In sh or ksh execute:

ulimit -n 8192
o Make sure that you have carefully planned your database layout, in particular the tablespace layout,
as described in Setup of Database Layout [page 33].
o If you want to set up DB2's high-availability cluster solution SA MP, make sure that you have read
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
o Make sure that you have defined the most important SAP system parameters as described in Basic
SAP System Installation Parameters [page 25] before you start the installation.
o Check that your installation hosts meets the requirements for the installation options that you
want to install. For more information, see Running the Prerequisite Checker [page 21].
o If you are installing a second or subsequent SAP system in an existing database (MCOD), make sure
that the database is up and running before starting the installation.
For more information, see Installation of Multiple Components in One Database [page 103].
o If you want to install an additional application server instance to an existing SAP system, make
sure that:
o There is exactly one entry in the /usr/sap/sapservices file for each SAP instance installed
on this host. Be sure to check that the entry refers to the correct profile.
o There are no profile backup files with an underscore _ in their profile name. If so, you must
replace the _ with a ..
EXAMPLE
Rename /usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2_D20081204 to /
usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2.D20081204.
Procedure
1.
Log on to the installation host as user root.
72/132
PUBLIC
2011-11-21
Installation
5.4
Running SAPinst
CAUTION
Do not use an existing <sapsid>adm user.

CAUTION
2.
Make sure that the root user has not set any environment variables for a different SAP system
or database.
installation host. For more information, see Preparing the Installation Media [page 59].
RECOMMENDATION
3.
Make installation media locally available. For example, if you use Network File System (NFS),
reading from media mounted with NFS might fail.
Change to the directory <product>_IM_<your OS>_<your DB> and start the sapinst executable
with the following command: ./sapinst
NOTE
If you want to use a virtual host name, start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows:
./sapinst SAPINST_USE_HOSTNAME=<virtual host name>
CAUTION
4.
Make sure that the installation directory is not mounted with NFS, or there might be problems
when the Java Virtual Machine is started.
In the Welcome screen, choose the required option:
n
Perform preparations
These comprise the following optional tasks:
Preparations
Remarks
Sets up LDAP support for an application server instance

For more information about LDAP and Active Directory, see Integration of
LDAP Directory Services [page 99].
Host Agent
Installs a standalone host agent. For more information, see Standalone Host
Agent [page 17].
Operating System Users and Allows you to use global accounts that are configured on a separate host
Groups
Run this installation option before you start the installation of the SAP
system.
Prerequisites Check
Checks your hardware and software requirements before you start the
installation. For more information, see Running the Prerequisites Checker in
Standalone Mode [page 21].
LDAP Registration
n
Install an SAP system:
Install an SAP system or an optional standalone unit (Advanced Adapter Engine, Advanced
Adapter Engine Extended, or Process Integration and Orchestration Package):
n
To install an SAP system based on SAP NetWeaver application server Java, choose <Your
SAP product> SAP Systems Application Server Java SAP NetWeaver 7.3 <System
Variant> .
2011-11-21
PUBLIC
73/132
Installation
5.4
Running SAPinst
8h To install an optional standalone unit, choose SAP NetWeaver 7.3 SAP Systems Optional
Standalone Units <Advanced Adapter Engine | Advanced Adapter Engine Extended | Process Integration
and Orchestration Package> <System Variant> .
You can install the following system variants:
System Variants
Remarks
Central System
Distributed System
Installs an SAP system with all mandatory instances on one host

Installs an SAP system with all mandatory instances on different hosts
Perform the installation options exactly in the order they appear. You
have to restart SAPinst on the relevant host for each installation option.
Installs a high-availability SAP system with all mandatory instances on
different hosts
Perform the installation options exactly in the order they appear. You
have to restart SAPinst on the relevant host for each installation option.
8h Perform other tasks or install additional components

Other Options
Remarks
Additional SAP System Instances
8h Additional Application Server Instance:

Installs one or more additional application server instances
8h Enqueue Replication Server Instance:
Installs an enqueue replication server (ERS) instance for an
existing central services instance for Java (SCS) or central services
instance for ABAP (ASCS)
Database Tools
System Copy
Uninstall
5.
6.
NOTE
These installation options are only useful in an SAP NetWeaver

BW environment.
8h Database Partitions
Choose this option if you want to add additional partitions to a
database instance in your BW system.
8h Install Near Line Storage Database
Choose this option if you want to install DB2 as near-line storage
database for your BW system.
Performs a system copy
For more information, see the system copy guide for your SAP system
at:
http://service.sap.com/instguides <SAP System>
Installation .
If you are performing a system copy and you have already exported the
source system, choose the following to start the target system
installation:
System Copy Target System <System Variant> <Technical Stack>
Choose this option to uninstall your SAP system, standalone engines,
or optional standalone units.
For more information, see Deleting an SAP System or Single Instances [page
117].
Choose Next.
Follow the instructions in the SAPinst screens and enter the required parameters.
74/132
PUBLIC
2011-11-21
Installation
5.4
Running SAPinst
NOTE
To find more information on each parameter during the input phase of the installation,
position the cursor on the required parameter and press F1 .
After you have entered all requested input parameters, SAPinst displays the Parameter Summary screen.
This screen shows both the parameters that you entered and those that SAPinst set by default. If
required, you can revise the parameters before starting the installation.
Make sure that you check the following parameters depending on the installation type that you
have chosen:
OHq If you are performing a typical installation, SAPinst creates by default four sapdata
directories. If you require a different number of sapdata directories, depending on the storage
devices you are using, you must change this parameter before you start the installation. By
selecting this parameter on the Parameter Summary screen and choosing Revise, SAPinst returns
to the dialog IBM DB2 for Linux, UNIX, and Windows > Sapdata Directories. In this dialog, you can
also decide if you want the installation tool to create the regular data and index tablespace
with DB2's automatic storage management enabled. By default, the option for automatic
storage management is preselected.
NOTE
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
dialog IBM DB2 for Linux, UNIX, and Windows > Sapdata Directories.
For more information, see DB2 Tablespaces [page 37].
OHq If you are performing a custom installation, you set these parameters during the dialog phase
of SAPinst.
NOTE
If the tablespace layout used by SAPinst does not meet your requirements, you can create
the tablespaces manually by deselecting the option Create Tablespaces with SAPinst on the
screen IBM DB2 for Linux and UNIX and Windows Sapdata Directories .
During the installation phase, SAPinst then displays the following message:
You must create the tablespaces now. To do so, use the
createTablespaces.sql script that is located in your installation
directory.
To continue the installation, choose OK. Alternatively, you can cancel
SAPinst here and restart it again.
SAPinst does not check the page size of tablespaces that have either been created manually
or already exist. If you create the tablespaces manually, you must make sure that you
use a page size of 16 KB.
For more information, see Creating Tablespaces Manually [page 106].
2011-11-21
PUBLIC
75/132
Installation
5.5
Additional Information About SAPinst
7.
To start the installation, choose Start.

SAPinst starts the installation and displays the progress of the installation. When the installation
has finished, SAPinst shows the message Execution of <Option_Name> has completed.
u4OO?QJByy,7F[)Em?A&
?^%J\</(
NOTE
During the last restart of Application Server Java performed by SAPinst, the portal starts the
processing and upload of the new portal archives. It takes approximately 15 to 90 minutes
before the deployment is completed and the portal is launched.
Do not stop SAPinst or Application Server Java during this phase.
u4O/QCJdyd7F[+ErzA&Q1"
8.
If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after SAPinst has finished.
Sometimes these remain in the temporary directory.
NOTE
If there are errors with the SAPinst extraction process, you can find the log file
dev_selfex.out in the temporary directory.
RECOMMENDATION
Keep all installation directories until you are sure that the system, including all instances, is
completely and correctly installed. Once the system is completely and correctly installed,
make a copy of the installation directories with all their contents and save it to a physically
separate medium, such as an optical media or a USB drive separate from your installation
hosts. This might be useful for analyzing issues occurring later when you use the system. For
security reasons, do not keep installation directories on installation hosts, but make sure that
you delete them after saving them separately.
9. We recommend that you delete all files in the directory <user_home>/.sdtgui/.
10. If not already done, install the DB2 license.
NOTE
If you have bought your DB2 license from SAP (OEM customers), install the DB2 license as
described in SAP Note 816773.
11. To make sure that SAPinst installed the most recent version of the database or the client software,
see SAP Note 101809. This SAP Note provides information about the currently released database
and Fix Pack combinations of DB2 for Linux, UNIX, and Windows.
12. If you copied the installation media to your hard disk, you can delete these files when the installation
has successfully completed.
5.5 Additional Information About SAPinst

The following sections provide additional information about SAPinst:
uvq Interrupted Installation with SAPinst [page 77]
76/132
PUBLIC
2011-11-21
Installation
5.5
h0
h0
h0
h0
h0
Performing a Remote Installation with SAPinst [page 79]

Starting SAPinst GUI Separately [page 80].
Running SAPinst in Accessibility Mode [page 83]
Entries in the Services File Created by SAPinst [page 83]
Troubleshooting with SAPinst [page 84]
5.5.1 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:
h0 An error occurred during the Define Parameters or Execute phase:
SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses
and a dialog box appears. The dialog box contains a short description of the choices listed in the
table below as well as a path to a log file that contains detailed information about the error.
h0 You interrupted the installation by choosing Cancel in the SAPinst menu.
CAUTION
If you stop an option in the Execute phase, any system or component installed by this option
is incomplete and not ready to be used. Any system or component uninstalled by this option
is not completely uninstalled.
The following table describes the options in the dialog box:
Option
Definition
Retry
SAPinst retries the installation from the point of failure without repeating
any of the previous steps.
This is possible because SAPinst records the installation progress in the
keydb.xml file.
We recommend that you view the entries in the log files, try to solve the
problem, and then choose Retry.
If the same or a different error occurs, SAPinst displays the same dialog box
again.
SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and
the GUI server.
SAPinst records the installation progress in the keydb.xml file. Therefore, you
can continue the installation from the point of failure without repeating any
of the previous steps. See the procedure below.
SAPinst continues the installation from the current point.
Access installation log files.
Stop
Continue
View Log
NOTE
You can also terminate SAPinst by choosing Ctrl + C . However, we do not recommend that
you use Ctrl + C , because this kills the process immediately.
2011-11-21
PUBLIC
77/132
Installation
5.5
Procedure
This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to
continue an interrupted installation after an error situation.
1. Log on to your local UNIX host as user root.
CAUTION
2.
or database.
installation host.
RECOMMENDATION
3.
4.
5.
with the following command: ./sapinst
From the tree structure in the Welcome screen, select the installation option that you want to
continue and choose Next.
The What do you want to do? screen appears.
In the What do you want to do? screen, decide between the following alternatives and continue with
Next:
Alternative
Behavior
Run a new option
SAPinst does not continue the interrupted installation option. Instead, it

moves the content of the old installation directory and all installationspecific files to a backup directory. Afterwards, you can no longer continue
the old installation option.
For the backup directory, the following naming convention is used:
<log_day_month_year_hours_minutes_seconds>.
NOTE
All actions taken by the installation before you stopped it (like

creating directories, or users) will not be revoked.
EXAMPLE
log_01_Oct_2008_13_47_56
CAUTION
Continue with the old option
78/132
SAPinst moves all the files and folders to a new log directory, even if
these files and folders are owned by other users. If there are any
processes currently running on these files and folders, they might no
longer function properly.
SAPinst continues the interrupted installation from the point of failure.
PUBLIC
2011-11-21
Installation
5.5
5.5.2 Performing a Remote Installation with SAPinst

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the GUI
server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from
which you control the installation with SAPinst GUI.
If your security policy requires that the person performing the installation by running the SAPinst GUI
on the local host is not allowed to know root credentials on the remote host, you can specify another
operating system user for authentication purposes. You do this using the
SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command
line.
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote
access to SAPinst GUI on Windows workstations. For more information, see SAP Note 1170809.
You can run the SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.
For more information, see Starting SAPinst GUI Separately [page 80].
Prerequisites
07 The remote host meets the prerequisites for starting SAPinst [page 69].
07 Both computers are in the same network and can ping each other.
To test this:
1. Log on to your remote host and enter the command ping <local host>.
2. Log on to the local host and enter the command ping <remote host>.
07 Make sure that the sapinst executable on the remote host and the sapinstgui executable on the
local host have exactly the same version. You can check this by using the option version as
described in the procedure below and in the procedure in Starting SAPinst GUI Separately [page 80].
07 If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter, make sure that this user exists on the remote host.
Procedure
1.
Log on to your remote host as user root.

CAUTION
2.
or database.
remote host.
RECOMMENDATION
3.
Make installation media locally available. For example, reading from media mounted with
Network File System (NFS) might fail.
Check the version of the sapinst executable by entering the following command:
./sapinst version
2011-11-21
PUBLIC
79/132
Installation
5.5
4.
The version of the sapinst executable must be exactly the same as the version of the
sapinstgui executable on the local host (see also Starting SAPinst GUI Separately [page 80]).
with the following command: ./sapinst -nogui
NOTE
If you need to specify another operating system user for authentication purposes, enter the
following command:
./sapinst -nogui SAPINST_REMOTE_ACCESS_USER=<specified OS user>
SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the
command prompt:
guiengine: no GUI connected; waiting for a connection on host <host_name>, port
<port_number> to continue with the installation
5.
Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 80].
5.5.3 Starting SAPinst GUI Separately

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI separately
in the following cases:
You closed SAPinst GUI using File Exit from the SAPinst menu while SAPinst is still running.
You want to perform a remote installation, where the SAPinst GUI runs on a different host from
SAPinst. For more information, see Performing a Remote Installation with SAPinst [page 79].
You want to run SAPinst in accessibility mode. In this case, you have to start the SAPinst GUI
separately on a Windows host as described below with the additional command line parameter
accessible.
For more information, see Running SAPinst in Accessibility Mode [page 83].
Prerequisites
The host on which you want to start the SAPinst GUI meets the prerequisites for starting SAPinst
as described in Running SAPinst [page 69].
Make sure that the sapinst executable on the remote host and the sapinstgui executable on the
local host have exactly the same version. You can check this by using the option version as
described in the procedure below and in the procedure in Performing a Remote Installation with SAPinst
[page 79].
Procedure
Starting SAPinst GUI on Windows
1.
host on which you want to start the SAPinst GUI.
80/132
PUBLIC
2011-11-21
Installation
5.5
2.
Change to the directory of the sapinstgui executable:

<product>_IM_<your OS>_<your DB>
NOTE
If you want to start SAPinst GUI on a Windows 32-bit operating system, change to the
following directory:
<product>_IM_SAPINSTGUI_WINDOWS_I386
3.
Start the SAPinst GUI from a command prompt by executing sapinstgui.exe with the relevant
command line parameters:
`+' If you want to perform a remote installation, proceed as follows:
1. Check the version of sapinstgui.exe by entering the following command:
sapinstgui.exe version
2.
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with SAPinst
[page 79]).
Start the SAPinst GUI by entering the following command:
sapinstgui.exe -host <remote_host> -port
<port_number_gui_server_to_gui_client>
where <remote_host> is the name of the remote host, and

<port_number_gui_server_to_gui_client> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
`+' If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed
as follows:
`+' If you are performing a local installation with SAPinst and SAPinst GUI running on the
same host, execute the following command:
sapinstgui.exe -standalone -port <port_number_gui_server_to_gui_client>
where <port_number_gui_server_to_gui_client> is the port the GUI server uses to

`+' If you are performing a remote installation with SAPinst and SAPinst GUI running on
different hosts, execute the following command:
sapinstgui.exe -host <remote_host> -port

The SAPinst GUI starts and connects to SAPinst.
2011-11-21
PUBLIC
81/132
Installation
5.5
Starting SAPinst GUI on UNIX
1.
host on which you want to start the SAPinst GUI.
RECOMMENDATION
2.
Change to the directory <product>_IM_<your OS>_<your DB> and start the sapinstgui executable
with the following command: ./sapinstgui
b|g0 If you want to start the SAPinst GUI on a Linux 32-bit platform, change to the directory
<product>_IM_SAPINSTGUI_LINUX_I386.
b|g0 If you want to perform a remote installation, proceed as follows:
1. Check the version of the sapinstgui executable by entering the following command:
./sapinstgui version
2.
The version of the sapinstgui executable must be exactly the same as the version of the
sapinst executable on the remote host (see also Performing a Remote Installation with SAPinst
[page 79]).
Start the SAPinst GUI by entering the following command:
./sapinstgui -host <remote_host> -port

b|g0 If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed
as follows:
b|g_ If you are performing a local installation with SAPinst and SAPinst GUI running on the
same host, execute the following command:
./sapinstgui -port <port_number_gui_server_to_gui>
where <port_number_gui_server_to_gui> is the port the GUI server uses to

b|g_ If you are performing a remote installation with SAPinst and SAPinst GUI running on
different hosts, execute the following command:
./sapinstgui -host <remote_host> -port <port_number_gui_server_to_gui>

<port_number_gui_server_to_gui> is the port the GUI server uses to communicate with
the GUI client (21212 by default).
The SAPinst GUI starts and connects to SAPinst.
82/132
PUBLIC
2011-11-21
Installation
5.5
5.5.4 Running SAPinst in Accessibility Mode

You can also run SAPinst in accessibility mode. The following features are available:
^lw Keyboard access:
This feature is available for all operating systems.
^lw High-contrast color:
This feature is derived from the Windows display properties. Therefore, to enable this feature, you
must perform a remote installation with the SAPinst GUI running on a Windows host.
^lw Custom font setting:
This feature is derived from the Windows display properties. Therefore, to enable this feature, you
must perform a remote installation with the SAPinst GUI running on a Windows host.
Procedure
Activating and Adjusting Accessibility Settings on Windows
You first have to activate and adjust the relevant settings for the font size and color schemes before
you start SAPinst or the SAPinst GUI.
NOTE
The following procedure applies for Windows Server 2008 and might be different when using
another Windows operating system.
1.
2.
3.
Right click on your Windows desktop and choose Personalize.

Choose Adjust font size (DPI) and choose Larger scale (120 DPI).
To define other font size schemes, choose Custom DPI.
In the right-hand pane, select Window Color and Appearance.
Select a color scheme from the Color scheme dropdown box.
To define your own color schemes, choose Advanced.
Running SAPinst in Accessibility Mode
You perform a remote installation as follows:

1. Start SAPinst on the remote host by executing the following command from the command line
as described in Performing a Remote Installation with SAPinst [page 79]:
./sapinst nogui
2.
Start SAPinst GUI on a local Windows host by executing the following command from the
command line as described in Starting the SAPinst GUI Separately for a Remote Installation [page 80]:
sapinstgui.exe -accessible host <remote_host> -port
5.5.5 Entries in the Services File Created by SAPinst

After the installation has completed, SAPinst has created the following entries in /etc/services:
2011-11-21
PUBLIC
83/132
Installation
5.5
sapdp<nn> = 32<nn>/tcp
sapdp<nn>s = 47<nn>/tcp
sapgw<nn> = 33<nn>/tcp
sapgw<nn>s = 48<nn>/tcp
NOTE
l
%
<nn> is the instance number. There is a port created for every possible instance number,
regardless of which instance number you specified during the installation. For example, for
sapgw<nn> = 33<nn>/tcp the following range of entries is created:
sapgw00 = 3300/tcp
sapgw01 = 3301/tcp
sapgw02 = 3302/tcp
[...]
sapgw98 = 3398/tcp
sapgw99 = 3399/tcp
l
% If there is more than one entry for the same port number, this is not an error.
5.5.6 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.
If an error occurs, SAPinst:
l
% Stops the installation
l
% Displays a dialog informing you about the error
Procedure
1.
2.
3.
4.
Check SAP Note 1548438 for known SAPinst issues.

To view the log file, choose View Logs.
If an error occurs during the dialog or processing phase, do one of the following:
l
% Try to solve the problem.
l
% Abort the installation with Exit.
For more information, see Interrupted Installation with SAPinst [page 77].
l
% Continue the installation by choosing Retry.
Check the log and trace files of the GUI server and SAPinst GUI in the directory
<user_home>/.sdtgui/ for errors.
l
% If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current
<user_home> directory.
l
% If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI
as described in Starting SAPinst GUI Separately [page 80].
84/132
PUBLIC
2011-11-21
Installation
5.5
5.
C', If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote
Access of SAPinst GUI on Windows Workstations and you experience display problems such
as missing repaints or refreshes, contact your X Server vendor. The vendor can give you
information about whether this X Server supports Java Swing-based GUIs and also tell you
about further requirements and restrictions. See also SAP Note 1170809.
If you cannot resolve the problem, create a customer message using component BC-INS.
2011-11-21
PUBLIC
85/132

Post-Installation
6.1
Post-Installation Checklist
6 Post-Installation
6.1 Post-Installation Checklist

This section includes the post-installation steps that you have to perform for the following:
oX/Rh Standard, distributed, or high-availability system
oX/Rh Additional application server instance
NOTE
1.
2.
3.
You perform post-installation steps for the operating system [page 88].
You check whether you can log on to the application server [page 88].
oXwg.x2r>6xK1mkorQ>dW\Uae# H,Ct=C-}rS)[rLYmGF
If you have installed enterprise portal, you check whether you can log on to the portal [page 89].
oXwg&xk=oezr1pkoyQ0>d_\J$p#RHcC6}S)+4pU
4.
5.
6.
7.
8.
9.
10.
You provide access to the NetWeaver Administrator [page 90].

You install the SAP license [page 90].
You set up the licenses for high availability [page 91].
You configure the remote connection to SAP support [page 92].
You ensure user security [page 92].
For a production system, you must enable the database for monitoring [page 94].
For a production system, you must enable your database for recoverability [page 95] immediately after
the installation.
11. You perform a full installation backup [page 97].
12. You check the Master Guide for your SAP NetWeaver application for further implementation and
configuration steps.
CAUTION
The Master Guide 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.
1.
You perform post-installation steps for the operating system [page 88].
2011-11-21
PUBLIC
87/132
Post-Installation
6.2
Performing Post-Installation Steps for the Operating System
2.
3.
You check whether you can log on to the additional application server instance [page 88].
/5'"HZGn/U,,zn,#o]0|BCwF7l` QR*`q% ~N)nA]fm*
You check whether you can log on to the portal [page 89] from the additional application server
instance host.
/?'V"XvMm2U',gh,<g]|C8F7F`;QR?`%
4.
You ensure user security [page 92].
6.2 Performing Post-Installation Steps for the Operating

System
You have to perform the following post-installation steps for the operating system.
Procedure
1.
2.
You check and if necessary modify the settings for the operating system users for your SAP system
if they were created by SAPinst.
For more information, see Creating Operating System Users and Groups [page 46].
You set the required permissions for sapstartsrv and sapuxuserchk in the /<sapmnt>/<SAPSID>/
exe, and /usr/sap/<SAPSID>/SYS/exe, and /usr/sap/<SAPSID>/<Instance_Name>/exe
directories as described in SAP Note 927637.
See also Starting and Stopping SAP System Instances Using the SAP Management Console [page 109].
6.3 Logging On to the Application Server

You need to check that you can log on to the application server using the following standard users:
Java Standalone Users
User
User Name Storage:

Database
User Name Storage:

External ABAP System
Administrator
Administrator
The user that you created manually

in the external ABAP system.
For more information, see Preparing
an External ABAP System as Source for User
Data [page 57].
Prerequisites
/ The SAP system is up and running.

Procedure
Logging On to the Java Application Server
You access AS Java with a URL using a Web browser from your client machines. To log on to the Java
application server, proceed as follows:
1. Start a Web browser and enter the following URL:
88/132
PUBLIC
2011-11-21
Post-Installation
6.4
Logging on to the Portal

http://<hostname_of_Java EE_Engine_Server>:5<Instance_Number>00
NOTE
You must always enter a two-digit number for <Instance_Number>. For example, do not
enter 1 but instead enter 01.
EXAMPLE
If you installed the SAP NetWeaver Application Server Java on host saphost06 and the
instance number of your SAP NetWeaver Application Server Java is 04, enter the following
URL:
http://saphost06:50400
2.
The start page of the SAP NetWeaver Application Server Java appears in the Web browser.
Log on by pressing the icon of any of the provided applications, for example the SAP NetWeaver
Administrator.
[.Bv?]g9X{8G\W|M]4Z0S 4QvRgdZt@" fiVk):6!f8*",|8\H&
6.4 Logging on to the Portal

You need to check that you can log on to the application server using the following standard users.
This procedure applies when you install usage type EP Core Application Portal (EPC) only and when
you install it together with usage type Enterprise Portal (EP):
Java Standalone Users
User
User Name Storage:

Database
User Name Storage:

External ABAP System
Administrator
Administrator
The user that you created manually

in the external ABAP system.
For more information, see Preparing
an External ABAP System as Source for User
Data [page 57].
Prerequisites
The SAP system is up and running.

Procedure
You access the portal with a URL using a Web browser from your client machines.
The default URL consists of the installation host name and the port on which the portal is listening.
You can use the HTTP or HTTPS protocol. HTTPS is relevant if you are using Secure Sockets Layer
(SSL) communication.
1. Start a Web browser and enter the following URL:
http://<hostname_of_Java EE_Engine_Server>:5<Instance_Number>00/irj
2011-11-21
PUBLIC
89/132
Post-Installation
6.5
Providing Access to the NetWeaver Administrator

NOTE
You must always enter a two digit number for <Instance_Number>. For example, do not
enter 1 but instead enter 01.
EXAMPLE
If you installed the portal on host saphost06 and the instance number of your SAP NetWeaver
Application Server Java is 04, enter the following URL:
http://saphost06:50400/irj
2.
Log on by entering the required user and password.
|xC]_6
}_Cp(sLw`?_l k5PmwuM&=Nc5o;NL
6.5 Providing Access to the NetWeaver Administrator

Due to security restrictions, the NetWeaver Administrator can only be accessed locally via http://
<hostname_of_Java EE_Engine_Server>:5<Instance_Number>00/nwa after the installation has
finished.
Procedure
Allow access to administration requests for the required network segments as described in SAP Note
1451753.
6.6 Installing the SAP License

You must install a permanent SAP license. When you install your SAP system, a temporary license
is automatically installed.
CAUTION
Before the temporary license expires, you must apply for a permanent license key from SAP.
We recommend that you apply for a permanent license key as soon as possible after installing
your system.
Procedure
Install the SAP license as described in the SAP library [page 9] at:
SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management SAP Licenses
More Information
For more information about SAP license keys and how to obtain them, see http://
service.sap.com/licensekey.
90/132
PUBLIC
2011-11-21
Post-Installation
6.7
High Availability: Setting Up Licenses
6.7 High Availability: Setting Up Licenses

SAP has implemented a license mechanism for switchover solutions and clustered environments. Your
customer key is calculated on the basis of local information on the message server host. This is the host
machine where the central services instance (SCS instance) runs.
To be able to perform a switchover, the temporary license that is installed automatically with the SCS
instance is not sufficient. You first need to install a permanent license, which is determined by the
hardware environment of the message server. Since SAP's high-availability (HA) solution stipulates
two or more cluster nodes (host machines) where the message server is enabled to run, you have to
order as many license keys [page 90] as you have cluster nodes.
When we receive confirmation from your vendor that you are implementing a switchover
environment, we provide the required license keys for your system, one key for each machine.
Prerequisites
The SAP system is up and running.

Procedure
1.
2.
3.
To find the hardware key of the primary host, run the SAP NetWeaver Administrator (NWA) on
any application server instance and choose Configuration Management Infrastructure Management
Licenses .
The hardware key is displayed in the NWA.
Perform a switchover of the central services instance (SCS) to another node in the cluster and
repeat the previous step.
Repeat this for all remaining nodes in the cluster.
To obtain the two license keys, enter the hardware IDs for the primary and backup hosts at:
http://service.sap.com/licensekey
4.
5.
To import the files containing the two licenses to the primary cluster node, run the NWA on any
application server instance and choose:
Configuration Management Infrastructure Management Licenses
Perform a switchover of the central services instance (SCS) to another node in the cluster and
repeat the previous step.
Repeat this for all remaining nodes in the cluster.
Result
The license is no longer a problem during switchover. This means you do not need to call
saplicense in your switchover scripts.
2011-11-21
PUBLIC
91/132
Post-Installation
6.8
Configuring the Remote Connection to SAP Support
6.8 Configuring the Remote Connection to SAP Support

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

You need to ensure the security of the users that SAPinst created during the installation. The tables
below at the end of this section list the following users:
|mA Operating system users
|mA SAP system users
During the installation, SAPinst by default assigned the master password to all users created during the
installation unless you specified other passwords.
RECOMMENDATION
In all cases, the user ID and password are encoded only when transported across the network.
Therefore, we recommend using encryption at the network layer, either by using the Secure
Sockets Layer (SSL) protocol for HTTP connections, or Secure Network Communications (SNC)
for the SAP protocols dialog and RFC.
CAUTION
Make sure that you perform this procedure before the newly installed SAP system goes into
production.
Procedure
For the users listed below, take the precautions described in the relevant SAP security guide, which you
can find on SAP Service Marketplace at http://service.sap.com/securityguide:
Operating System Users
After the installation, operating system users for SAP system, database, and host agent are available as
listed in the following table:
User Type
User
Comment
Operating system user

<sapsid>adm
Database and operating system user
db2<dbsid>
SAP system administrator

Administrator for the Diagnostics
Agent
Database administrator
Database connect user in an ABAP
system
You can specify the name of the Java
connect user (sap<sapsid>db)
independently from the SAP
<dasid>adm
sap<sapsid>db
92/132
PUBLIC
2011-11-21
Post-Installation
6.9
Ensuring User Security
User Type
User
Comment
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.
Host Agent User
User
User Name
Comment
sapadm
SAP system administrator

You do not need to change the password of this
user after the installation.
This user is for administration purposes only.
SAP System Users
Depending on the UME (User Management Engine) configuration that you specified during the
installation, the following UME users are available after the installation:
"4;= If you have chosen option Use Java Database, UME users are stored in the database (Java UME) see
table Users Stored in the Java Database below.
You can manage users and groups with the UME Web admin tool and the SAP NetWeaver
Administrator only.
"4;= If you have chosen option Use ABAP, UME users are stored in an external ABAP system (ABAP
UME) see table Users Stored in an External ABAP System below.
For more information, see Preparing an External ABAP System as Source for User Data [page 57].
The following tables show these users together with recommendations on how you can ensure the
security of these users:
SAP System Users Stored in an External ABAP System
User
User Name Storage: External ABAP System
Comment
Administrator
The name that you gave this user when you

created it manually in the external ABAP system
(see Preparing an External ABAP System as Source for User
Data [page 57])
This users password is stored in secure

storage.
Therefore, whenever you change the
administrators password, you must
also change the password in secure
storage with the Config Tool.
2011-11-21
PUBLIC
93/132
Post-Installation
6.10
Enabling the Database for Monitoring
User
User Name Storage: External ABAP System
Comment
RECOMMENDATION
Guest

created it manually in the external ABAP system
Data [page 57])
Communication
user for Application created it manually in the external ABAP system
Server Java
Data [page 57])
We recommend that you use

strong password and auditing
policies for this user.
Lock this user for interactive logon.
Specify this user as a Communications user

and not as a dialog user.
This user exists in at least the SAP
system client that you specified during
the installation.
SAP System Users Stored in the Database

User
User Name Storage: Database
Comment
Administrator
The name that you gave this user This users password is stored in secure storage.
during the installation or the
Therefore, whenever you change the
default name Administrator
administrators password, you must also change
the password in secure storage with the AS Java
Config Tool.
RECOMMENDATION
Guest
We recommend that you use strong

password and auditing policies for this
user.
The name that you gave this user This user is used for anonymous access.
during the installation or the
Lock this user for interactive logon.
default name Guest
6.10 Enabling the Database for Monitoring

After the SAP system installation, you must enable the database for monitoring by setting up a data
collection framework (DCF). The DCF provides a time-based collection and evaluation of performance,
configuration, and space-related data. The DCF consists of the following:
Y0Y A set of tables holding history data
Y0Y Tablespaces to store these monitoring tables
Y0Y A set of stored procedures to collect data on a regular basis
These stored procedures are scheduled by the DB2 administrative task scheduler (ATS).
You can only monitor the database of your SAP Java system remotely using SAP Solution Manager. To
do so, you must integrate your SAP Java system into the SAP Solution Manager system. During the
integration, the DCF is set up automatically for databases with automatic storage management by
the setup wizard of SAP Solution Manager.
94/132
PUBLIC
2011-11-21
Post-Installation
6.11
Enabling Recoverability of the Database

RECOMMENDATION
We recommend that you check the status of the DCF on the Collector Configuration screen of the
DBA Cockpit after the system has been integrated into the SAP Solution Manager landscape.
If you installed the database without automatic storage management, you perform the following steps:
1. In your SAP Solution Manager system, call transaction DBACOCKPIT.
2. On the Database tab page of the DBA Cockpit, choose Configuration Data Collection Framework
Collector Configuration .
3. Set up and configure the DCF as described in section Enabling the Database for the Data Collection
Framework in the Database Administration Guide: Database Administration Using the DBA Cockpit.
Any error during the installation process can result in the DCF not being automatically installed.
For example, if the installation failed due to missing tablespaces, create these tablespaces first and
retry the installation. If the installation completes successfully, the DCF also has been installed
and is available for monitoring.
More Information
Database Administration Guide: Database Administration Using the DBA Cockpit - IBM DB2 for Linux, UNIX, and
Windows at:
http://service.sap.com/instguidesnw <Your SAP NetWeaver Main Release> Operations
Database-Specific Guides
6.11 Enabling Recoverability of the Database

CAUTION
This section only applies to your database. You only have to perform the steps outlined in this
section once even if you install multiple SAP systems into one database.
Roll forward recovery provides the ability to recover lost data due to media failure, such as hard disk
failure, and applies log file information (log journal) against the restored database. These log files contain
the changes made to the database since the last backup.
CAUTION
A production system must run in log retention mode.

If a system is not running in log retention mode, all changes applied to the database since the last
complete backup are lost in the event of a disk failure.
In log retention mode, the log files remain in the log directory (log_dir). To archive the log files, you
can use DB2's own log file management solution. For more information, see the Database Administration
Guide SAP on IBM DB2 for Linux, UNIX, and Windows.
2011-11-21
PUBLIC
95/132
Post-Installation
6.11
Enabling Recoverability of the Database
Procedure
1.
2.
Log on to the database server as user db2<dbsid>.

To activate log retention mode and to specify the log archiving method, you must set configuration
parameter LOGARCHMETH1 to one of the following options:
u
LOGRETAIN
No log archiving takes place. Log files remain in the log directory.
u
DISK:<log_archive_path>
Log files are archived to a disk location. You can archive them to tape using the DB2 tape
manager (db2tapemgr) at a later point in time.
u
TSM:<TSM_management_class>
Log files are archived to Tivoli Storage Management (TSM)

u
VENDOR:<path_to_vendor_lib>
Log files are archived to a library that is provided by your vendor storage management
u
USEREXIT
For downward compatibility with the former user exit concept, you can specify value
USEREXIT for parameter LOGARCHMETH1.
To set configuration parameter LOGARCHMETH1 for your preferred archiving method, enter the
following command:
db2 update db cfg for <dbsid> using LOGARCHMETH1 <log_archiving_method>
3.
4.
For more information, see the Database Administration Guide SAP on IBM DB2 for Linux, UNIX, and
Windows.
To activate the settings, you must restart the database. The database is now in backup pending
mode. You need to take an offline backup before you can continue.
To start the offline backup for a single-partitioned database, enter the following command:
db2 backup db <dbsid> to <device>
EXAMPLE
For example, to perform an offline backup of database C11 to tapes in devices rmt0 and
rmt1, enter the following command:
db2 backup database C11 to /dev/rmt0, /dev/rmt1
NOTE
On a multi partition database, you must activate log retention mode on all database partitions.
In addition, you also have to perform an offline backup for all database partitions.
For more information about how to start a DB2 backup, see the DB2 online documentation.
More Information
Database Administration Guide SAP on IBM DB2 for Linux, UNIX, and Windows at:
http://service.sap.com/instguidesnw <Your SAP NetWeaver Release> Operations DatabaseSpecific Guides .
96/132
PUBLIC
2011-11-21
Post-Installation
6.12
Performing a Full Installation Backup
6.12 Performing a Full Installation Backup

You must perform a full offline backup after the configuration of your SAP system. If required, you
can also perform a full offline backup after the installation (recommended). In addition, we recommend
you to regularly back up your database.
CAUTION
Make sure that you fully back up your database so that you can recover it later if necessary.
You need to back up the following directories and files:
b#7 All SAP-specific directories:
b#7 /usr/sap/<SAPSID>
b#7 /usr/sap/trans
b#7 <sapmnt>/<SAPSID>
b#7 Home directory of the user <sapsid>adm
b#7 Perform a full offline database backup.
For more information about backups, see the IBM DB2 documentation.
b#7 Make sure that you back up the home directory of db2<dbsid>.
For more information about backups, see the IBM DB2 documentation.
b#7 The root file system
This saves the structure of the system and all configuration files, such as file system size, logical
volume manager configuration, and database configuration data.
NOTE
This list is only valid for a standard installation.

Prerequisites
You have logged on [page 88] as user <sapsid>adm and stopped the SAP system and database [page 109].
Procedure
This procedure works on all hardware platforms. For more information about operating system-specific
backup procedures, see your operating system documentation.
Backing Up the Installation
1.
2.
Log on as user root.

Manually create a compressed tar archive that contains all installed files:
b#7 Saving to tape:
tar cf <file_system> | compress c > <tape_device>
b#7 Saving to the file system:

tar cf <file_system> | compress c > ARCHIVENAME.tar.Z
2011-11-21
PUBLIC
97/132
Post-Installation
6.12
Performing a Full Installation Backup

NOTE
You can also execute the following command to manually create a compressed GNU
archive that contains all installed files and save it to the file system:
tar
tar czf <ARCHIVENAME>.tgz <file_system>
3.
Perform your offline database backup.

For more information, see the IBM DB2 documentation.
Restoring Your Backup
If required, you can restore the data that you previously backed up.
CAUTION
Check for modifications in the existing parameter files before you overwrite them when restoring
the backup.
1.
2.
3.
Log on as user root.

Go to the location in your file system where you want to restore the backup image.
Restore the data with the following commands:
inb From tape:
cat <tape_device> | compress cd | tar xf
inb From the file system:

cat ARCHIVENAME.tar.Z | compress cd | tar xf
NOTE
If you want to restore the data from a GNU

command:
tar archive, you have to execute the following
tar xzf <ARCHIVENAME>.tgz
4.
Restore your offline database backup.

For more information about how to restore backups, see the IBM DB2 documentation.
98/132
PUBLIC
2011-11-21
Additional Information
7.1
Integration of LDAP Directory Services
7 Additional Information
Here you can find additional information about the installation of your SAP system.
There is also information about how to delete an SAP system.
C(; Integration of LDAP Directory Services [page 99]
C(; Installing Multiple Components in One Database (MCOD) [page 103]
C(; MCOD Tablespaces and File Systems [page 104]
C(; Creating a User for LDAP Directory Access [page 105]
C(; Creating Tablespaces Manually [page 37]
C(; Installing the Host Agent Separately [page 107]
C(; Starting and Stopping the SAP System [page 109]
C(;
wL=9Ro _L]a% )K4KS[a[<

qCoa;yl$w9">O6kA
Troubleshooting for Usage Type Enterprise Portal (EP) [page 116]

.LruRoLâ%)I2CF[:U[$
q(ECwy*$"w
C(; Deleting an SAP System [page 117]

C(; Deleting the Database Instance and Database Software Manually [page 119]
7.1 Integration of LDAP Directory Services

This section explains the benefits of using the SAP system with the Lightweight Directory Access
Protocol (LDAP) directory and gives an overview of the configuration steps required to use an SAP
system with the directory.
LDAP defines a standard protocol for accessing directory services, which is supported by various
directory products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory services
enables important information in a corporate network to be stored centrally on a server. The advantage
of storing information centrally for the entire network is that you only have to maintain data once,
which avoids redundancy and inconsistency.
If an LDAP directory is available in your corporate network, you can configure the SAP system to use
this feature. For example, a correctly configured SAP system can read information from the directory
and also store information there.
NOTE
The SAP system can interact with the Active Directory using the LDAP protocol, which defines:
C(; The communication protocol between the SAP system and the directory
C(; How data in the directory is structured, accessed, or modified
2011-11-21
PUBLIC
99/132
7.1
If a directory other than the Active Directory also supports the LDAP protocol, the SAP system
can take advantage of the information stored there. For example, if there is an LDAP directory on
a UNIX or Windows server, you can configure the SAP system to use the information available
there. In the following text, directories other than the Active Directory that implement the LDAP
protocol are called generic LDAP directories.
Prerequisites
{ You can only configure the SAP system for Active Directory services or other LDAP directories if
these are already available on the network. As of Windows 2000 or higher, the Active Directory
is automatically available on all domain controllers. A generic LDAP directory is an additional
component that you must install separately on a UNIX or Windows server.
{ Make sure that you have at least the following RPM packages installed:
{ Red Hat Linux:
openldap2
{ SUSE LINUX
openldap2
openldap2client
Features
In the SAP environment, you can exploit the information stored in an Active Directory or generic
LDAP directory by using:
{ SAP Logon
{ The SAP Microsoft Management Console (SAP MMC)
{ The SAP Management Console (SAP MC)
For more information about the automatic registration of SAP components in LDAP directories and
the benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information in
Directory Services at:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0a0d051eae2-2b10-e1ac-f3a7f6494c53
For more information about the SAP MC and about how to configure it to access LDAP Directories,
see the documentation SAP Management Console in the SAP Library [page 9]:
Function-Oriented View Solution Life Cycle Management SAP Management Console
SAP Logon
Instead of using a fixed list of systems and message servers, you can configure SAP Logon in the
sapmsg.ini configuration file to find SAP systems and their message servers from the directory. If you
configure SAP logon to use the LDAP directory, it queries the directory each time Server or Group selection
is chosen to fetch up-to-date information on available SAP systems.
To use LDAP operation mode, make sure that the sapmsg.ini file contains the following:
[Address]
100/132
PUBLIC
2011-11-21
7.1
Mode=LDAPdirectory
LDAPserver=
LDAPnode=
LDAPoptions=
Distinguish the following cases:

G8 If you use an Active Directory, you must set LDAPoptions=DirType=NT5ADS. For more
information, see the SAP system profile parameter ldap/options.
G8 You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either of
the following is true:
G8l The client is not located in the same domain forest as the Active Directory
G8l The operating system does not have a directory service client (Windows NT and Windows 9X
without installed dsclient).
For more information, see the SAP system profile parameter ldap/servers.
G8 For other directory services, you can use LDAPnode to specify the distinguished name of the SAP
root node. For more information, see the SAP system profile parameter ldap/saproot.
SAP MMC
The SAP MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from
a central location. It is automatically set up when you install an SAP system on Windows. If the SAP
system has been prepared correctly, the SAP MMC presents and analyzes system information that it
gathers from various sources, including the Active Directory.
Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can
read system information straight from the directory that automatically registers changes to the system
landscape. As a result, up-to-date information about all SAP application servers, their status, and
parameter settings is always available in the SAP MMC.
If you need to administer distributed systems, we especially recommend that you use the SAP MMC
together with Active Directory services. You can keep track of significant events in all of the systems
from a single SAP MMC interface. You do not need to manually register changes in the system
configuration. Instead, such changes are automatically updated in the directory and subsequently
reflected in the SAP MMC.
If your SAP system is part of a heterogeneous SAP system landscape that comprises systems or instances
both on Unix and Windows operating systems, you can also use the SAP MMC for operating and
monitoring the instances running on Unix.
SAP MC
The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems from a
central location. The SAP MC is automatically set up when you install an SAP system on any platform.
If the SAP system has been prepared correctly, the SAP MC presents and analyzes system information
that it gathers from various sources, including a generic LDAP Directory.
2011-11-21
PUBLIC
101/132
7.1
Integrating a generic LDAP Directory as a source of information has advantages for the SAP MC. It can
read system information straight from the directory that automatically registers changes to the system
landscape. As a result, up-to-date information about all SAP application servers, their status, and
parameter settings is always available in the SAP MC.
Configuration Tasks for LDAP Directories
This section describes the configuration tasks you have to perform for the Active Directory or other
(generic) LDAP directories.
Configuration Tasks for Active Directory
To enable an SAP system to use the features offered by the Active Directory, you must configure the
Active Directory so that it can store SAP system data.
To prepare the directory, you use SAPinst to automatically:
&%-6A Extend the Active Directory schema to include the SAP-specific data types
&%-6A Create the domain accounts required to enable the SAP system to access and modify the Active
Directory. These are the group SAP_LDAP and the user sapldap.
&%-6A Create the root container where information related to SAP is stored
&%-6A Control access to the container for SAP data by giving members of the SAP_LDAP group permission
to read and write to the directory
You do this by running SAPinst on the Windows server on which you want to use Active Directory
Services and choosing <SAP System> Preparations LDAP Registration Active Directory Configuration .
For more information about running SAPinst on Windows, see documentation Installation Guide <your
SAP product> on Windows: <Database>.
NOTE
You have to perform the directory server configuration only once. Then all SAP systems that
need to register in this directory server can use this setup.
Configuration Tasks for Generic LDAP Directories
To configure other LDAP directories, refer to the documentation of your directory vendor.
Enabling the SAP System LDAP Registration
Once you have correctly configured your directory server, you can enable the LDAP registration of the
SAP system by setting some profile parameters in the default profile.
To do this, run SAPinst [page 69] once for your system and choose:
<SAP System> Preparations LDAP Registration LDAP Support
If you use a directory server other than Microsoft Active Directory and/or non-Windows application
servers, you have to store the directory user and password information by using ldappasswd
pf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and is therefore
valid for all application servers. After restarting all application servers and start services, the system is
102/132
PUBLIC
2011-11-21
7.2
Installation of Multiple Components in One Database
registered in your directory server. The registration protocols of the components are dev_ldap*. The
registration is updated every time a component starts.
7.2 Installation of Multiple Components in One Database

You can install multiple SAP systems in a single database. This is called Multiple Components in One
Database (MCOD). MCOD is available with all SAP components and all the major databases for the
SAP system. No extra effort is required because the MCOD installation is fully integrated into the
standard installation procedure. MCOD is not an additional installation option. Instead, it is an option
of the database instance installation.
With MCOD we distinguish two scenarios:
The installation of an SAP system in a new database
The installation of an additional SAP system in an existing database (MCOD)

Prerequisites
For more information about MCOD and its availability on different platforms, see http://
www.sdn.sap.com/irj/sdn/dbos Key Topics Multiple Components in One Database (MCOD) .
Since SAP does not support mixed solutions with MCOD, your SAP system must contain Unicode
SAP instances only.
Improved sizing required

You can calculate the CPU usage for an MCOD database by adding up the CPU usage for each
individual SAP system. You can do the same for memory resources and disk space.
You can size multiple components in one database by sizing each individual component using the
Quick Sizer tool and then adding the requirements together. For more information about the
Quick Sizer, see http://service.sap.com/sizing.
Features
Reduced administration effort
Consistent system landscape for backup, system copy, administration, and recovery
Increased security and reduced database failure for multiple SAP systems due to monitoring and
administration of only one database
Independent upgrade
In an MCOD landscape, you can upgrade a single component independently from the other
components running in the same database, assuming that the upgraded component runs on the
same database version. However, if you need to restore a backup, be aware that all other components
are also affected.
NOTE
Special MCOD considerations and differences from the standard procedure are listed where
relevant in the installation documentation.
2011-11-21
PUBLIC
103/132
7.3
MCOD Tablespaces and File Systems
Constraints
sk We strongly recommend that you test MCOD in a test or development system. We recommend
that you run MCOD systems in the same context. We do not recommend that you mix test,
development, and production systems in the same MCOD.
sk In the event of database failure, all SAP systems running on the single database are affected.
sk Automated support in an MCOD landscape for the following administrative tasks depends on your
operating system and database:
sk Copying a single component from an MCOD landscape to another database at database level.
sk De-installing a single component from an MCOD landscape requires some additional steps.
You can use a remote connection to SAP support to request help with these tasks. For more
information, see http://service.sap.com/remoteconnection.
sk For the first SAP system, the database system ID can be different from the SAP system ID.
sk For the second SAP system, you must use the same DBSID as for the first SAP system.
sk If you decide to turn off database logging during the database load phase of the installation, you
need to plan downtime for all MCOD systems sharing the database.
7.3 MCOD Tablespaces and File Systems

If you install additional SAP components into one database, each system has its own tablespaces. Only
SYSCATSPACE and temporary tablespaces are shared, for example, the additional SAP system
<SAPSID2> uses tablespaces, such as <SAPSID2>#BTABD and <SAPSID2>#BTABI
NOTE
During an installation of multiple components on one database, additional space is required for
tablespace SYSCATSPACE. If you are not using tablespaces with autoresize mode or DB2's automatic
storage management, you must extend SYSCATSPACE manually before you start the SAP system
installation.
If you are not using autostorage tablespaces, the tablespaces of the additional SAP system <SAPSID2>
are located in /db2/<SAPSID2>/sapdata<n>. If you are using autostorage tablespaces, the automatic
storage paths, which have already been configured in your database, are used.
The temporary tablespace of the additional SAP system <SAPSID2> is the same as for <SAPSID1>. If
temporary tablespaces with 16 KB page size do not exist, they are created in /db2/<DBSID>/
sapdata<n>.
CAUTION
If you are using a database in AutoStorage mode in an MCOD environment, you can choose if your
tablespaces are also AutoStorage or AutoResize. You can only choose this option for your tablespaces
if you are using a database in AutoStorage mode in an MCOD environment.
104/132
PUBLIC
2011-11-21
7.4
Creating a User for LDAP Directory Access
Each additional system works with its own SAP connect user sap<sapsid>db, that means all database
objects of SAP system <SAPSID2> are owned by sap<sapsid2>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.
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.
CAUTION
There is only one database administrator db2<dbsid>.

Required File Systems
The following table lists the file systems that are required for an additional SAP system.
Description
6L With DB2's automatic storage management:

Use the automatic storage paths that have already
been configured in your database.
6L No automatic storage management:
SAP data for container type database-managed space (DMS)

FILE
By default, four Sapdata directories are created
(sapdata1, sapdata2, sapdata3, sapdata4).
/db2/<SAPSID2>/sapdata<n>
/sapmnt/<SAPSID2>
/usr/sap/<SAPSID2>
Contains the temporary tablespace(s).

Contains the software and data for one SAP system
Contains the instance-specific data as well as symbolic
links to the data for one SAP system
7.4 Creating a User for LDAP Directory Access

If you use LDAP directory services, you have to set up a user with a password on the host where the
SAP system is running. This permits the SAP system to access and modify the LDAP directory.
For more information, see Integration of LDAP Directory Services in the Windows installation guide for your
SAP system solution and database.
Prerequisites
During the SAP instance installation you chose to configure the SAP system to integrate LDAP services.
Procedure
1.
2.
Log on as user <sapsid>adm.

Enter:
ldappasswd pf=<path_and_name_of_instance_profile>
3.
Enter the required data.

EXAMPLE
The following is an example of an entry to create an LDAP Directory User:
2011-11-21
PUBLIC
105/132
7.5
Heterogeneous SAP System Installation

CN=sapldap,CN=Users,DC=nt5,DC=sap-ag,DC=de
7.5 Heterogeneous SAP System Installation

This section provides information on the installation of an SAP system in a heterogeneous system
landscape. Heterogeneous system landscape means that application servers run on different
operating systems.
Procedure
See SAP Note 1067221 for more information on:

fE Supported combinations of operating systems and database systems
fE How to install an application server on Windows in a heterogeneous (UNIX) SAP system
environment
fE Heterogeneous SAP system landscapes with different UNIX operating systems
7.6 Creating Tablespaces Manually

If the tablespace layout used by SAPinst does not meet your requirements, you can optionally create
your tablespaces manually. During the dialog phase of SAPinst, you can specify if you want to use
tablespaces managed by DB2's automatic storage management and if you want SAPinst to create your
tablespaces.
Procedure
CAUTION
SAPinst does not check the page size of tablespaces that have either been created manually or are
already existing. If you create the tablespaces manually, you must make sure that you use a page
size of 16 KB.
1.
On the dialog IBM DB2 for Linux, UNIX, and Windows Sapdata Directories , you must deselect the
option Create Tablespaces with SAPinst.
NOTE
2.
In a typical installation, this dialog does not appear. To get to it, select this parameter on the
Parameter Summary screen and choose Revise.
Continue to enter all the required parameters and start SAPinst.
During the installation phase, the following message box appears:
You must create the tablespaces now. To do so, use the createTablespaces.sql script that is located in your installation
directory.
To continue the installation, choose OK. Alternatively, you can cancel SAPinst here and restart it again.
106/132
PUBLIC
2011-11-21
7.7
Installing the Host Agent Separately
3.
Go to your installation directory and search for script createTablespace.sql. This file content
depends on your selection during the dialog phase and the file contains the same commands for
the creation of tablespaces that SAPinst uses.
NOTE
4.
5.
You must create all the tablespaces that are listed in the script.
Modify the CREATE statements according to your requirements.
To execute the script, enter the following command:
db2 tvf <script_name>
6.
When you have finished, continue with the installation by choosing OK on the message box.
More Information
!PE DB2 Tablespaces [page 37]

!PE Data Safety and Performance Considerations [page 39]
7.7 Installing the Host Agent Separately

This procedure tells you how to install a host agent separately.
The host agent is automatically installed during the installation of all new SAP system instances based
on SAP NetWeaver 7.1 or higher. You only need to install a host agent separately in the following cases:
!PE You want to manage a host that does not have an SAP instance or component.
!PE You have upgraded an SAP system prior to SAP NetWeaver 7.1.
!è5'CHost Agent
The host agent contains the following elements:
2011-11-21
PUBLIC
107/132
7.7
Installing the Host Agent Separately
,J
,J
,J
,J
The control program saphostexec

The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)
The sapacosprep executable of the Adaptive Computing Infrastructure
The operating system collector saposcol
NOTE
The installed programs are automatically started when the host is booted.
The automatic start is ensured by the startup script sapinit, which starts the required executables.
Procedure
You have to perform the following steps on the host where you install the host agent separately:
1. Check the hardware and software requirements on the installation host.
The minimum requirements are as follows:
,J Hard Disk Space: 1 GB
,J RAM: 0.5 GB
,J Swap Space: 2 x RAM
For more information, see hardware and software requirements [page 20].
2. Make sure that the sapadm user is created.
During the installation, SAPinst checks all required accounts (users, groups) and services on the
local machine. SAPinst checks whether the required users and groups already exist. If not, it creates
new users and groups as necessary.
User and Groups of the Host Agent
User
Primary Group
Additional Group
Comment
sapadm
sapsys
sapinst
Host Agent administrator
Groups and Members of the Host Agent User
3.
Groups
Members
sapsys
sapadm
sapinst
sapadm
Set up the required file system for the host agent:

Directories
Description
/usr/sap/hostctrl
Contains the following directories: 100 MB

,J exe
Contains the profile
Required Disk Space
host_profile
,J
work
Working directory of the host

agent
For more information, see Setting up file systems and raw devices [page 49]
108/132
PUBLIC
2011-11-21
7.8
Starting and Stopping SAP System Instances
4.
5.
6.
Make sure that the medium for the installation master (folder <Product>_IM_<OS>_<DB>) and for
the UC kernel (folder K_U_<Version>_<OS>) are available on the installation host. For more
information, see Preparing the Installation Media [page 59].
To install the host agent, you start SAPinst [page 69] and choose Preparations Host Agent on the
Welcome screen of SAPinst.
Check whether the installed services are available:
1. Log on as user sapadm.
NOTE
2.
When the host is booted, the startup script sapinit automatically starts the required
executables.
Check whether the following services are available:
h| The control program saphostexec
h| The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)
More Information
For more information about the host agent, see the SAP Library [page 9] at:
SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Solution Monitoring Monitoring
in the CCMS Infrastructure of the SAP NetWeaver Management Agents
7.8 Starting and Stopping SAP System Instances

You can start or stop SAP system instances in one of the following ways:
h| Using the SAP Management Console (SAP MC) [page 109]
h| Using commands [page 113].
7.8.1 Starting and Stopping SAP System Instances Using the

SAP Management Console
You can start and stop all SAP system and diagnostics agent instances using the SAP Management
Console (MC) except the database instance. You have to start and stop the database instance as described
in Starting and Stopping the SAP System Using startsap and stopsap [page 113].
NOTE
If your newly installed SAP system is part of a heterogeneous SAP system landscape comprising
systems or instances on Windows platforms, you can also start and stop it from a Windows system
or instance using the Microsoft Management Console (MMC).
For more information about handling the MMC, see the SAP Library [page 9] at:
SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management SAP Microsoft
Management Console: Windows
2011-11-21
PUBLIC
109/132
7.8
Prerequisites
b Make sure that the host names defined in the DNS server match the names of the SAP system
instance hosts. In particular, keep in mind that host names are case-sensitive. For example, if the
names of the SAP system instance hosts are in upper case, but the same host names are defined in
the DNS server in lower case, starting and stopping the system does not work.
b Make sure that the host on which you start SAP MC meets the following requirements:
b At least Java Runtime Environment (JRE) 5.0 is installed.
b The browser supports Java.
b The browser's Java plug-in is installed and activated.
b You have set the required permissions for sapstartsrv and sapuxuserchk in the /<sapmnt>/
<SAPSID>/exe, and /usr/sap/<SAPSID>/SYS/exe, and /usr/sap/<SAPSID>/
<Instance_Name>/exe directories as described in SAP Note 927637.
See also Performing Post-Installation Steps for the Operating System [page 88].
b You have logged on to the host as user <sapsid>adm.
Procedure
Starting the Web-Based SAP Management Console
1.
Start a Web browser and enter the following URL:

http://<hostname>:5<instance_number>13
EXAMPLE
If the instance number is 53and the host name is saphost06, you enter the following URL:
http://saphost06:55313
This starts the SAP MC Java applet.

NOTE
2.
If your browser displays a security warning message, choose the option that indicates that
you trust the applet.
Choose Start.
The SAP Management Console appears.
NOTE
When you start the SAP MC for the first time for a newly installed SAP system, you have to
register your system as described in Registering Systems and Instances below. After you have done
this, the instances installed on the host you have connected to are already present in the SAP
Management Console when you next start the SAP MC.
By default, the instances installed on the host you have connected to are already present in the
SAP Management Console.
If you want to change the configuration to display systems and instances on other hosts, see
Registering Systems and Instances below.
110/132
PUBLIC
2011-11-21
7.8
Starting and Stopping Systems and Instances

Starting an SAP System or Instance
1.
2.
3.
4.
In the navigation pane, open the tree structure and navigate to the system node that you want to
start.
Select the system or instance and then, from the context menu, choose Start.
In the Start SAP System(s) dialog box, choose the required options.
Choose OK. The SAP MC starts the specified system or system instances.
NOTE
The system might prompt you for the SAP system administrator credentials. To complete
the operation, you must have administration permissions. Log in as user <sapsid>adm.
Starting Instances Separately
If you need to start the instances of an SAP system separately, for example when you want to start a
distributed or a high-availability system, proceed in the following sequence:
1. Start the database instance.
2. Start the central services instance SCS<Instance_Number>.
3. Start application server instance(s) J<Instance_Number>.
Stopping an SAP System or Instance
1.
2.
3.
Select the system or instance you want to stop and choose Stop from the context menu.
In the Stop SAP System(s) dialog box, choose the required options.
Choose OK. The SAP MC stops the specified system or system instances.
NOTE
The system might prompt you for the SAP system administrator credentials. To complete
the operation, you must have administration permissions. Log in as user <sapsid>adm.
Similarly, you can start, stop, or restart all SAP systems and individual instances registered in the SAP
MC.
Stopping Instances Separately
If you need to stop the instances of an SAP system separately, for example when you want to start a
distributed or a high-availability system, proceed in the following sequence:
1. Stop application server instance(s) J<Instance_Number>.
2. Stop the central services instance SCS<Instance_Number>.
3. Stop the database instance.
Registering Systems and Instances in the SAP Management Console
You can extend the list of systems and instances displayed in the SAP MC, so that you can monitor and
administer all systems and instances from a single console. You can configure the SAP MC startup view
to display the set of systems and instances you want to manage.
2011-11-21
PUBLIC
111/132
7.8
Prerequisites
The SAP MC is started.

Registering SAP Systems
1.
2.
In the SAP MC, choose File New .

In the New System dialog box, enter the required data.
NOTE
3.
If you have already registered systems in the SAP MC, they are stored in the history. To open
the Systems History dialog box, choose the browsing button next to the Instance Nr. field. Select
an instance of the system that you want to add and choose OK.
Choose Finish.
Registering Individual Instances
1.
2.
3.
In the SAP MC, choose File New .

In the New System dialog box, enter the required data and deselect Always show all SAP Instances.
The SAP MC displays the SAP system node, the instance node, and the relevant database node in
a tree view in the navigation pane.
NOTE
To view all instances of the respective SAP system, select the relevant system node and choose
Add Application Server from the context menu.
Configuring the SAP MC View
{6 You can choose the instances that the SAP MC displays automatically on startup:
1. In the Settings dialog box, select History.
2. In the right-hand side pane, choose the instance you want the SAP MC to display on startup.
3. Choose the << button.
4. Choose Apply and then choose OK.
Similarly, you can remove instances from the startup configuration.
{6 You can save the current configuration in a file:
1. Choose File Save Landscape .
2. In the Save dialog box, enter the required data.
3. Choose Save.
{6 You can load a configuration from a file:
1. Choose File Load Landscape .
2. In the Open dialog box, select the configuration you want to load.
3. Choose Open.
More Information
For more information about how to handle the SAP MC, see the SAP Library [page 9] at:
SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management SAP Management Console
112/132
PUBLIC
2011-11-21
7.8
7.8.2 Starting and Stopping SAP System Instances Using

Commands
You can start and stop SAP system instances using the startsap and stopsap commands.
You can use command line options to specify these commands. Command line options are available
in the new style or the old style.
Using New Style for Command Line Options and Parameters
Using the new style, the syntax is as follows:

stopsap | stopsap [-t | -task <task>] [-i | -instance <instance>] [-v | -vhost
"<virtual hostname>[ <virtual hostname>]*"][-c | -check] [-h | -help] [-V | -VERSION]
[-C | -checkVHost]
EXAMPLE
If you want to start an application server instance J00 that has the virtual host names cic11 and
cic12, enter the following commands:
startsap -t j2ee -i J00 -v "cic11 cic12"
The following command line options and parameters are available:

Command Line Options (New Style)
Parameter Name
Description
[-t | -task <task>]
Specify task
Specify SAP system instance
Specify virtual host names
[-i | -instance <instance>]

[-v | -vhost "<virtual hostname>
[ <virtual hostname>]*"]
Check database and SAP instance status

Display help
Display startsap script version
Check virtual host name
[-c | -check]
[-h | -help]
[-V | -VERSION]
[-C | -checkVHost]
Parameters for <task> (New Style)

Parameter Name
Description
check
Check status of database and SAP system instances

Start or stop SAP instances only
Start or stop database only
Start or stop database and SAP instance
Start or stop sapstartsrv program
j2ee
jdb
all | <blank>
startupsrv
Parameters for <instance> where <nn> is the instance number

Parameter Name
Description
SCS<nn>
Java central services instance (SCS instance)

Application server instance
J<nn>
2011-11-21
PUBLIC
113/132
7.8
Parameter Name
Description
ERS<nn>
Enqueue replication server instance (ERS instance)

Diagnostics agent instance
Web services instance
Gateway instance
SMDA<nn>
W<nn>
G<nn>
Using Old Style for Command Line Options and Parameters
Using the old style, the syntax is as follows:

stopsap | stopsap [db|j2ee|all|check|startupsrv] [<instance>] [<virtual hostname>]
EXAMPLE
If you want to start an application server instance DVEBGMS00 that has the virtual host names
cic11 and cic12, enter the following commands:
startsap j2ee J00 cic11 cic12
The following command line options and parameters are available:

Command Line Options (Old Style)
Parameter Name
Description
check [<instance>] [<virtual hostname>]
Check status of database and SAP system instances

Start or stop SAP instances only
Start or stop database only
Start or stop database and all SAP system instances
running on the same physical host
Start or stop sapstartsrv program
j2ee [<instance>] [<virtual hostname>]

jdb [<instance>] [<virtual hostname>]
all | <blank>
startupsrv
Parameters for <instance> where <nn> is the instance number

Parameter Name
Description
SCS<nn>
Java central services instance (SCS instance)

Application server instance
Enqueue replication server instance (ERS instance)
Diagnostics agent instance
Web services instance
Gateway instance
J<nn>
ERS<nn>
SMDA<nn>
W<nn>
G<nn>
Prerequisites
OjfzW Make sure that you have logged on to the physical host of the SAP system instances as user
<sapsid>adm.
OjfzW Make sure that the host names defined in the DNS server match the names of the SAP system
instance hosts. In particular, keep in mind that host names are case-sensitive. For example, if the
names of the SAP system instance hosts are in uppercase, but the same host names are defined in
the DNS server in lowercase, starting and stopping the system does not work.
114/132
PUBLIC
2011-11-21
7.8
t If you want to use startsap or stopsap (for example, in a script) and require the fully qualified
name of these SAP scripts, create a link to the startsap script in the home directory of the
corresponding user.
t You cannot use startsap or stopsap commands in a switchover cluster environment. Therefore
in a high-availability (HA) system you must use the failover cluster software of your HA partner
to start or stop instances running on the switchover cluster.
t You cannot use startsap or stopsap commands to start or stop database-specific tools. For more
information about how to start or stop database-specific tools, see the database-specific information
in this documentation and the documentation from the database manufacturer.
t Make sure that no SAP instance is running before you execute stopsap on a standalone database
server. No automatic check is made.
t When you use stopsap in a Multiple Components in One Database (MCOD) system with two
primary application server instances, only one primary application server instance and the database
are shut down. Therefore, you must first stop the other SAP system or make sure that it has already
been stopped.
Procedure
Starting an SAP System
t If you want to start all SAP system instances running on the same host, execute the following
command:
New style: startsap or startsap -t all
Old style:startsap or startsap all
t If you want to start SAP system instances separately, enter the following command:
New style:startsap -t j2ee -i <instance> [-v "<virtual host name>"]
Old style:startsap j2ee <instance> [<virtual host name>]
Make sure that you adhere to the following sequence when starting the instances:
1. Database instance
2. ERS instance for the SCS instance (if available)
3. SCS instance
4. Application server instances
Stopping an SAP System
t If you want to stop all SAP system instances running on the same host, execute the following
command:
New style: stopsap or stopsap -t all
Old style:stopsap or stopsap all
t If you want to stop SAP system instances separately, enter the following command:
New style:stopsap -t j2ee -i <instance> [-v "<virtual host name>"]
2011-11-21
PUBLIC
115/132
7.9
Troubleshooting for Portal Installation
Old style:stopsap j2ee <instance> [<virtual host name>]

Make sure that you adhere to the following sequence when stopping the instances:
1. Application server instances
2. SCS instance
3. ERS instance for the SCS instance (if available)
C*9Q?<ZbPz9a8^-@ |w %y&A-,:L=p6,|zaIa%6Or8
7.9 Troubleshooting for Portal Installation

This section applies both when you install usage type EPC only and when you install it together with
usage type EP.
If the iViews are not displayed correctly, or if the portal does not launch, the reason might be that the
portal was not deployed completely.
To check the deployment of the portal, proceed as follows:
Procedure
1.
2.
Open a new console with the user <sapsid>adm.

Go to the directories deployment, pcd, and pcdContent, in the following paths:
C*tT
/usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/server0/
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment
C*tT
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd
C*tT
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent
C*tT
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/
pcdContent/no_overwrite
3.
4.
Look for files with the extension *.err.

Do one of the following:
C*tT If error and log files do not appear, the portal installation has been completed successfully and
you can continue.
C*tT Rename the *.err files:
1. Remove the err extension; so the extensions of the files become *.ept or *.par.
2. Restart AS Java, using the commands stopsap and startsap, to change the files to
*.bak.
C*3Q?<rPz9M8]0 J#'<&Av,L=2`|onaI%
116/132
PUBLIC
2011-11-21
7.10
Deleting an SAP System or Single Instances
7.10 Deleting an SAP System or Single Instances

This section describes how to delete a complete SAP system or single SAP instances with the Uninstall
option of SAPinst.
Note the following when deleting an SAP system:
f3O We strongly recommend that you delete an SAP system using SAPinst. However, you can also
delete an SAP system manually. For more information, see SAP Note 1259982.
f3O When you uninstall an SAP system, the database content is also deleted.
f3O You must not uninstall all application server instances if you want to continue using the database
instance for another SAP system for example, if you want to perform a homogenous system
copy. Otherwise, you delete configuration-specific data in the database instance and you cannot
use the database instance anymore.
f3O You cannot delete an SAP system remotely.
f3O During the uninstall process, all file systems and subdirectories of the selected SAP system or single
instance are deleted. Before you start uninstalling, make sure that you have saved a copy of all files
and directories that you want to keep to a secure location.
f3O The uninstall process is designed to remove as much as possible of the SAP system to be deleted. If
an item cannot be removed, a message informs you that you have to remove this item manually.
You can do this either at once or after the uninstall process has finished. As soon as you confirm
the message, the uninstall process continues.
Prerequisites
f3O You have installed your SAP system with standard SAP tools according to the installation
documentation.
f3O You are logged on as user root.
f3O Make sure that the SAP system, or single instance, or standalone engine, or optional standalone
unit to be deleted is down and that you are not logged on as one of the SAP system users. If there
is a lock on one of the SAP system objects, this breaks the uninstall. Make also sure that all SAPrelated processes are stopped.
NOTE
You do not have to stop the host agent. The host agent is stopped automatically during the
uninstall process.
f3O Make sure that there are no open sessions by one of the SAP system users when starting the uninstall.
Procedure
1.
2.
3.
Start SAPinst as described in Running SAPinst [page 69].

On the Welcome screen, choose:
SAP NetWeaver 7.3 Uninstall Uninstall SAP Systems or Single Instances
Follow the instructions in the SAPinst screens to delete a complete SAP system or single instances.
2011-11-21
PUBLIC
117/132
7.10
Deleting an SAP System or Single Instances

NOTE
For more information about the input parameters, place the cursor on the relevant field and
press F1 in SAPinst.
The following table provides information about deleting a complete system or single instances
with SAPinst.
Deletion of
Remarks
Standard system
You can delete a standard system (where all instances reside on the same host),
in one SAPinst run.
If you want to delete a distributed or high-availability system, you have to run
SAPinst to delete the required instances locally on each of the hosts belonging
to the SAP system in the following sequence:
1. Additional application server instances, if there are any
Since SAPinst only stops local instances automatically, make sure that
before deleting the database instance of a distributed system, you stop all
remaining instances. You must stop the instance with the message server
only after having entered all SAPinst parameters for the deletion of the
database instance.
To delete the database instance or one or more database schemas, choose
one of the following options:
qh Drop database
Select this option if you want to drop the database.
qh Select the database schema that you want to delete
Select this option if you are running multiple components on one
database (MCOD) and you only want to delete the database schema
of the corresponding component to be deleted.
Distributed or highavailability system
NOTE
3.
4.
If you want to delete a schema of a non-automatic storage

database in an MCOD environment using SAPinst, no DB2specific file systems are deleted. Make sure that you manually
delete/db2/<sapsid>/sapdata<1n>.
Primary application server instance
Central services instance (SCS)
NOTE
To delete system directories mounted from an NFS server, make sure

that you run SAPinst on the NFS server.
CAUTION
Additional application
server
Standalone host agent
118/132
If you are running multiple components on one database (MCOD), do

not delete the database.
If you want to delete additional application server instances of an existing SAP
system, you have to run SAPinst to delete them locally on each additional
application server instance host.
The host agent is automatically uninstalled from a host together with the last
remaining SAP system instance.
If you want to uninstall a standalone host agent, deselect Profiles Available and
select Uninstall Standalone Host Agent on the General SAP System Parameters screen.
PUBLIC
2011-11-21
7.11
Deleting the Database Instance and Database Software Manually (Optional)

Deletion of
Remarks
Diagnostics agent
If you want to delete a diagnostics agent instance, enter the location of the
profile directory of the diagnostics agent that you want to uninstall on the
General SAP System Parameters screen:
/usr/sap/<DASID>/SYS/profile
4.
5.
When you have finished, delete the relevant directory structure on the global host.
If you created the directories /usr/sap/<SAPSID> and /<sapmnt>/<SAPSID> as mount points, but
not as directories on the local file system, you have to remove them manually.
7.11 Deleting the Database Instance and Database Software

Manually (Optional)
7.11.1 Deleting the Database and the DB2 Instance Manually
(Optional)
You use this procedure to manually delete the database and the DB2 instance of a complete SAP system.
Prerequisites
Before deleting the database, stop and delete all SAP instances belonging to the database.
Procedure
1.
To delete the database, proceed as follows:

1. Log on as user db2<dbsid>.
2. To start the database, enter the following command:
db2start
3.
To delete the database <DBSID>, enter the following command:

db2 drop database <DBSID>
4.
To stop the database, enter the following command:

db2stop
2.
3.
To delete the DB2 instance, log on as user root.

Enter the following command:
%DB2PATH%/instance/db2idrop db2<dbsid>
4.
5.
6.
Remove user db2<dbsid> from group db<dbsid>adm (if the group db<dbsid>adm is now empty,
remove it also).
Remove user db2<dbsid>.
To remove the home directory of db2<dbsid> and all subdirectories, enter the following command.
rm rf /db2/db2<dbsid>
7.
Unmount and delete the following file systems:

2011-11-21
PUBLIC
119/132
7.11
/db2/<DBSID>/saptemp1
/db2/<DBSID>
8.
Remove user sap<sapsid> from group db<dbsid>mon (if the group db<dbsid>mon is now empty,
remove it also).
9. Delete user sap<sapsid>, its home directory, and all subdirectories of this directory.
10. Remove user sap<sapsid>db from group db<dbsid>mon (if the group db<dbsid>mon is now empty,
remove it also).
11. Delete user sap<sapsid>db, its home directory, and all subdirectories of this directory.
12. Delete the /etc/services entries for sapdb2<DBSID>.
In other words, delete the lines starting with sapdb2<DBSID>.
7.11.2 Deleting a Database Schema Manually (Optional)

You use the following procedure to delete a database schema - but not the complete database. That is,
you have to delete all tables (and indexes), views, and tablespaces belonging to the schema (for example,
if you are running multiple components in one database).
You delete a database schema in one of the following situations:
vPr You are running multiple components on one database (MCOD) and you only want to delete the
database schema of the corresponding component to be deleted.
vPr You want to delete the Java part of an SAP system (ABAP+Java or Java Add-In).
Prerequisites
vPr Make sure that any instance that uses the schema is stopped.
vPr The database must be up and running.
Procedure
1.
2.
Log on to the database server as db2<dbsid> and open a command prompt.

Create a script to delete all tables of the database schema by entering the following SQL statement:
db2 SELECT 'DROP TABLE' || CHR(34) || VARCHAR(tabschema) || CHR(34) || '.' || CHR
(34) || tabname || CHR(34) || ';' from syscat.tables where
tabschema='<SAP_SYSTEM_SCHEMA>' AND TYPE='T' | grep DROP >
drop_<sap_system_schema>_tables.txt
3.
where <SAP_SYSTEM_SCHEMA> is the name of the connect user.

Create a second script to delete all views of the database schema by entering the following SQL
statement:
db2 SELECT 'DROP VIEW' || CHR(34) || VARCHAR(tabschema) || CHR(34) || '.' || CHR
(34) || tabname || CHR(34) || ';' from syscat.tables where
tabschema='<SAP_SYSTEM_SCHEMA>' AND TYPE='V' | grep DROP >
drop_<sap_system_schema>_views.txt
120/132
PUBLIC
2011-11-21
7.11
4.
where <SAP_SYSTEM_SCHEMA> is the connect user.

To delete all tables, run the first script by entering the following command:
db2 tvf drop_<sap_system_schema>_tables.txt
5.
To delete all views, run the second script by entering the following command:
db2 tvf drop_<sap_system_schema>_views.txt
6.
To drop the database schema, enter the following command:

db2 drop schema <SAP_SYSTEM_SCHEMA> restrict
7.
To delete all tablespaces, proceed as follows:

1. To display a list of all tablespaces, enter the following command:
db2 list tablespaces
2.
3.
4.
Delete all tablespaces starting with <SAPSID>#.

When deleting only a Java Add-In for ABAP, delete only the Add-In tablespaces, that is
<SAPSID>#DBD and <SAPSID>#DBI.
To delete the required tablespaces, enter the following command:
db2 drop tablespace <tablespace_name>
7.11.3 Deleting the DB2 Software Installation Manually

(Optional)
Procedure
1.
Check if any DB2 instance exists by entering the following command:

%DB2PATH%/instance/db2ilist
NOTE
2.
3.
If no instance is listed, you can continue with step 2. If any instance is listed, you must delete
this instance before you can delete the database software. For more information, see Deleting
the Database and DB2 Instance Manually [page 119].
Log on as user with root authority.
Enter the following command:
%DB2PATH%/install/db2_deinstall -a
2011-11-21
PUBLIC
121/132

Appendix
A.1
Online Information from SAP
A Appendix
A.1 Online Information from SAP

More information is available online as follows:
Documentation
Description
Internet Address
Title
http://www.sdn.sap.com/irj/sdn/dbos Multiple
Installation of
Multiple Components Components in One Database (MCOD)
in One Database
(MCOD) and its
availability on
different platforms
http://service.sap.com/instguidesnw <SAP NetWeaver
Database
administration guide Main Release> Operations Database-Specific Guides
for SAP systems on
IBM DB2 for Linux,
UNIX, and Windows
http://service.sap.com/instguidesnw <SAP NetWeaver
Database
administration using Main Release> Operations Database-Specific Guides
the DBA Cockpit
BW administration
tasks for SAP systems
on DB2 for Linux,
UNIX, and Windows
SAP Front End
installation Guide
System Copy for SAP
NetWeaver 7.3
including EHP1
Multiple Components in One

Database (MCOD)
Database Administration
Guide SAP on IBM DB2
for Linux, UNIX and
Windows
Database Administration
Using the DBA Cockpit:
IBM DB2 for Linux, UNIX,
and Windows
http://service.sap.com/instguidesnw <SAP NetWeaver SAP NetWeaver Business
Main Release> Operations Database-Specific Guides
Warehouse <Release> Administrative Tasks: IBM
DB2 for Linux, UNIX, and
Windows
http://service.sap.com/installnw73 Installation
SAP Front End Installation
Guide <Current Release>
http://service.sap.com/installnw73 Installation
System Copy for SAP
NetWeaver 7.3 including
EHP1
General Quick Links

Description
Internet Address
SAP Help Portal

SAP NetWeaver Library in SAP
Help Portal
Installation Guides
SAP Notes
http://help.sap.com
2011-11-21
http://help.sap.com/netweaver
http://service.sap.com/instguides
http://service.sap.com/notes
PUBLIC
123/132
Appendix
A.2
Online Information from IBM
Description
Internet Address
Supported platforms and

operating systems
Product Availability Matrix (PAM)
Release notes
Unicode SAP systems and their
availability
System sizing (Quick Sizer tool)
SAP NetWeaver capabilities
Life-cycle management for SAP
NetWeaver
Landscape design for SAP
NetWeaver
Application management for SAP
NetWeaver
Software logistics for SAP
NetWeaver
SAP NetWeaver operations
Security for SAP NetWeaver
Information on SAP Support
Package Stacks
SAP Solution Manager
Maintenance Optimizer
http://sdn.sap.com/irj/sdn/dbos
http://service.sap.com/pam
http://service.sap.com/releasenotes
http://service.sap.com/unicode
http://service.sap.com/sizing
http://sdn.sap.com/irj/sdn/netweaver
http://sdn.sap.com/irj/sdn/lcm
http://sdn.sap.com/irj/sdn/landscapedesign
http://sdn.sap.com/irj/sdn/applicationmanagement
http://sdn.sap.com/irj/sdn/softwarelogistics
http://sdn.sap.com/irj/sdn/operations
http://sdn.sap.com/irj/sdn/security
http://service.sap.com/sp-stacks
http://service.sap.com/solutionmanager
http://service.sap.com/solman-mopz
A.2 Online Information from IBM

The following tables provide information about how you can access IBM DB2 manuals and the
respective online documentation for your DB2 database.
IBM Manuals
Database Version
Internet Address
DB2 V9.7
http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg27015148
IBM DB2 Information Center

Database Version
Internet Address
DB2 V9.7
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7
NOTE
The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific
terms.
124/132
PUBLIC
2011-11-21
Appendix
A.2
Online Information from IBM
More Information
For more information about web sites that contain important DB2-related documentation, see SAP
Note 690471.
2011-11-21
PUBLIC
125/132
Typographic Conventions
Example
Description
<Example>
Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, Enter your <User Name>.
Arrows separating the parts of a navigation path, for example, menu options
Example
Example
Example
Example
http://www.sap.com
/example
123456
Example
Example
EXAMPLE
EXAMPLE
126/132
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
n\D Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
n\D Cross-references to other documentation or published works
n\D Output on the screen following a user action, for example, messages
n\D Source code or syntax quoted directly from a program
n\D 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
PUBLIC
2011-11-21
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,
z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle and Java are registered trademarks of Oracle.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP
AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius,
and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects Software Ltd. Business Objects is an SAP company
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
(SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
Disclaimer
Some components of this product are based on Java. Any code change in these components may cause unpredictable and
severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.
Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or
altered in any way.
Legal Software Terms
2011-11-21
PUBLIC
127/132
Terms for Included Open Source Software
This SAP software contains also the third party open source software products listed below. Note that for these third party
products the following special terms and conditions shall apply.
1. This software includes ANTLR, which is released under the following BSD license:
[The BSD License]
Copyright (c) 2010 Terence Parr
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
tT<N Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
tT<N Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
tT<N Neither the name of the author nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
2. SAP License Agreement for STLport
SAP License Agreement for STLPort between
SAP Aktiengesellschaft
Systems, Applications, Products in Data Processing
69190 Walldorf, Germany
(hereinafter: SAP)
and
you
(hereinafter: Customer)
1. Subject Matter of the Agreement
1. SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++
library (STLport) and its documentation without fee.
2. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual
property laws, and to all of the terms and conditions of this Agreement.
3. The Customer may distribute binaries compiled with STLport (whether original or modified) without any
royalties or restrictions.
4. Customer shall maintain the following copyright and permissions notices on STLport sources and its
documentation unchanged: Copyright 2001 SAP AG
5. The Customer may distribute original or modified STLport sources, provided that:
tT<N The conditions indicated in the above permissions notice are met;
tT<N The following copyright notices are retained when present, and conditions provided in accompanying
permission notices are met:
Copyright 1994 Hewlett-Packard Company
Copyright 1996,97 Silicon Graphics Computer Systems Inc.
Copyright 1997 Moscow Center for SPARC Technology.
Copyright 1999,2000 Boris Fomitchev
Copyright 2001 SAP AG
Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is
hereby granted without fee, provided that the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company
128/132
PUBLIC
2011-11-21
3.
makes no representations about the suitability of this software for any purpose. It is provided as is without
express or implied warranty.
Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is
copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no
representations about the suitability of this software for any purpose. It is provided as is without express or
implied warranty.
copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC
makes no representations about the suitability of this software for any purpose. It is provided as is without
express or implied warranty.
Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material
is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission
to use or copy this software for any purpose is hereby granted without fee, provided the above notices are
retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the
above notices are retained, and a notice that the code was modified is included with the above copyright notice.
copyright notice and this permission notice appear in supporting documentation. SAP makes no
representations about the suitability of this software for any purpose. It is provided with a limited warranty
and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and
warranty obligations only towards its customers and only referring to its modifications.
2. Support and Maintenance
SAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall
be not included.
All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions
and shall be subject to a separate contract.
3. Exclusion of warranty
As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the
STLport is error-free, without material defects or suitable for a specific application under third-party rights.
Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any
assurance of particular attributes.
4. Limited Liability
1. Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this
(i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by
SAP or (iii) if based on the failure of a guaranteed attribute.
2. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial
employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage
shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the
contract, due to the circumstances known to it at that point in time representing a typical transfer of the
software.
3. In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a
defect or lost profit.
4. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances
exceed EUR 5,000.
5. The Customer shall take adequate measures for the protection of data and programs, in particular by making
backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and
its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided
by observing this obligation.
6. The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against
employees or agents of SAP.
Adobe Document Services
2011-11-21
PUBLIC
129/132
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe
document services and Adobe LiveCycle Designer, see SAP Note 854621.
Documentation in the SAP Service Marketplace
You can find this document at the following address: http://service.sap.com/instguides
130/132
PUBLIC
2011-11-21
SAP AG
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained
herein may be changed without prior notice.

Nw731 Linux Db6 Java

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Nw731 Linux Db6 Java

Încărcat de

Drepturi de autor:

Formate disponibile

Installation Guide

SAP Systems Based on SAP NetWeaver 7.3 Application Server

About this Installation Guide

SAP System Installation

Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . .

Creating Operating System Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . .

Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . .

Before You Start

1.1 Before You Start

Master Guide SAP NetWeaver 7.3 including

1.2 New Features

You no longer require a Solution Manager Key for the installation.

Supported database version

Specification of connect user

1.3 SAP Notes for the Installation

Accessing the SAP Library

SAP Notes for the Installation

1.4 Accessing the SAP Library

This page is left blank for documents

Installation Options Covered by this Guide

2 Installation Options Covered by this

2.1 Standard System

Installation Options Covered by this Guide

B#@:&vLXT;Standard Java System

2.2 Distributed System

Installation Options Covered by this Guide

T\Kpo5L%yDistributed Java System

2.3 High-Availability System

Installation Options Covered by this Guide

Additional Application Server Instance

IMaVh `AHigh-Availability System

2.4 Additional Application Server Instance

Installation Options Covered by this Guide

Additional Application Server Instance

Additional Application Server Instance for a Standard System

0b#M4@Additional Application Server Instance for a Standard System

For more information, see Standard System [page 11].

Installation Options Covered by this Guide

Additional Application Server Instance

G mm+}*uAdditional Application Server Instance for a Distributed System

For more information, see Distributed System [page 12].

Installation Options Covered by this Guide

Host Agent as a Separate Installation

8T&@ !L/Additional Application Server Instance for a High-Availability System

For more information, see High-Availability System [page 13].

2.5 Host Agent as a Separate Installation

This page is left blank for documents

3.1 Planning Checklist

Standard, Distributed, or High-Availability System

Additional Application Server Instance

Hardware and Software Requirements

3.2 Hardware and Software Requirements

Check the Product Availability Matrix at http://service.sap.com/pam for supported operating

Hardware and Software Requirements

3.2.1 Running the Prerequisite Checker in Standalone Mode

3.2.2 Hardware and Software Requirements Tables

Hardware and Software Requirements

Values and Activities

Your operating system platform must be 64-bit.

The following hardware architecture is supported with DB2 V9.7:

The installation of an SAP system on Intel IA64 is not supported.

Optical Media Drive

Hardware and Software Requirements

Values and Activities

B#@:&vLXT;Standard Java System

T\Kpo5L%yDistributed Java System

IMaVh`AHigh-Availability System

G mm+}*uAdditional Application Server Instance for a Distributed System

8T&@ !L/Additional Application Server Instance for a High-Availability System

p%dpW$k)ADirectory Structure of the Database Client