Nw731 Linux Db6 Java

8/21/2019 Nw731 Linux Db6 Java

1/132

Installation GuideSAP Systems Based on SAP NetWeaver 7.3 Application ServerJava including EhP1 on Linux: IBM DB2 for Linux, UNIX, andWindows

Target Audience

System administrators

Technology consultants

PUBLICDocument version: 1.00 2011-11-21


2/132

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 filesand 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 oldproposed database version or you upgrade the old database version to the downward-compatible new

version.

2/132 PUBLIC 2011-11-21


3/132

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 Description1.00 2011-11-21 First version

2011-11-21 PUBLIC 3/132
http://service.sap.com/instguides


4/132

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.3 SAP Notes f or the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.4 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . 11

2.1 Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2 Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.3 High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4 Additional Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.5 Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.2.1 Running the Prerequisite Checker in Standalone Mode

(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2.2 Hardware and Software Requirements Tables . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.3 Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.4 Setup of Database Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.4.1 Required File Systems for DB2 for Linux, UNIX, and Windows . . . . . . . . . . . . 34

3.4.2 Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.4.3 Directory Structure of the DB2 Client Connectivity . . . . . . . . . . . . . . . . . . . . 36

3.4.4 DB2 Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.4.5 Data Safety and Performance Considerations for Production

Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.5 SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.6 Planning the Switchover Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4/132 PUBLIC 2011-11-21


5/132

4.2 Creating Operating System Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.3 Required File Systems and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.3.1 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.3.2 Setting Up File Systems for a High-Availability System . . . . . . . . . . . . . . . . . . 54

4.4 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.5 Performing Switchover Preparations for High Availability . . . . . . . . . . . . . . . . 56

4.6 Preparing an External ABAP System as Source for User Data . . . . . . . . . . . . . . 57

4.7 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.2 Exporting and Mounting the Global Transport Directory . . . . . . . . . . . . . . . . 67

5.3 Exporting and Mounting Global Directories . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.4 Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.5 Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5.5.1 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.5.2 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . 79

5.5.3 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

5.5.4 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

5.5.5 Entries in the Services File Created by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . 83

5.5.6 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Chapter 6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

6.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

6.2 Performing Post-Installation Steps for the Operating System . . . . . . . . . . . . . . 88

6.3 Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

6.4 Logging on to the Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

6.5 Providing Access to the NetWeaver Administrator . . . . . . . . . . . . . . . . . . . . . . 90

6.6 Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

6.7 High Availability: Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

6.8 Configuring the Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . 92

6.9 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

6.10 Enabling the Database for Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

6.11 Enabling Recoverability of the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

6.12 Performing a Full Installation Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

7.1 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

2011-11-21 PUBLIC 5/132


6/132

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

7.3 MCOD Tablespaces and File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

7.4 Creating a User for LDAP Directory Access . . . . . . . . . . . . . . . . . . . . . . . . . . 105

7.5 Heterogeneous SAP System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

7.6 Creating Tablespaces Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

7.7 Installing the Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

7.8 Starting and Stopping SAP System Instances . . . . . . . . . . . . . . . . . . . . . . . . . 109

7.8.1 Starting and Stopping SAP System Instances Using the SAP Management

Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

7.8.2 Starting and Stopping SAP System Instances Using Commands . . . . . . . . . . . 113

7.9 Troubleshooting for Portal Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

7.10 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . 117

7.11 Deleting the Database Instance and Database Software Manually

(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

7.11.1 Deleting the Database and the DB2 Instance Manually (Optional) . . . . . . . . . 119

7.11.2 Deleting a Database Schema Manually (Optional) . . . . . . . . . . . . . . . . . . . . . 120

7.11.3 Deleting the DB2 Software Installation Manually (Optional) . . . . . . . . . . . . . 121

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

A.2 Online Information from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

6/132 PUBLIC 2011-11-21


7/132

1 Introduction

This document explains how to install an SAP system based on theJavaapplication 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

SAP systemrefers to SAP system based on the application server of SAP NetWeaver 7.3 including Enhancement Package

1.

Java systemrefers to SAP system based on the Java application server of SAP NetWeaver 7.3 including Enhancement

Package 1.

diagnosticsrefers to diagnostics in SAP Solution Manager.

diagnostics agentrefers to the agent of diagnostics in SAP Solution Manager.

DB2 V9.7refers 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

1 Introduction

1.1 Before You Start

2011-11-21 PUBLIC 7/132
http://service.sap.com/installNW73http://service.sap.com/instguides


8/132

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.SARis now available in the

DBINDEP subfolder of the UC Kernel (folder K__U_) medium and installed automatically by

SAPinst. You do not have to separately download SAPCRYPTO.SARany

longer. For more information, see Basic SAP System Installation Parameters

[page 25].

Process Integration and Orchestrationis available as an optional standalone unit

installation.

Supported database version The installation of SAP systems that are based on this SAP NetWeaver releaseand higher is onlysupported 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/db2_software.

Specification of connect user

name

As of Enhancement Package 1 for SAP NetWeaver 7.3, you can specify the name

of the Java connect user (sapdb) 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.

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 mustread the following SAP Notes beforeyou 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.

1 Introduction

1.2 New Features

8/132 PUBLIC 2011-11-21
http://service.sap.com/noteshttp://service.sap.com/noteshttp://service.sap.com/releasenotes


9/132

SAP Notes for the Installation

SAP Note Number Title Description

1407532 Release Restrictions for SAP NetWeaver 7.3 Customer information about restrictions

concerning the productive usage of certain

functions.

1552840 SAP NetWeaver 7.3 EHP1 Installation on

UNIX

UNIX-specific information about the

installation for SAP systems and corrections

to this documentation.

1584218 DB6: Inst. SAP NetWeaver 7.3 incl. EhP1

UNIX

Platform-specific information about the SAP

system installation and corrections to this

documentation.

101809 DB6: Supported Fix Packs for DB2 for LUW Provides information about the currently

released database and Fix Pack combinations

1363169 DB6: Installation of Fix Packs for DB2 V9.7

(Linux and UNIX)

UNIX-specific information about how you

update the database software and the globaldirectory.

702175 DB6: Supporting several database

partitions with DB2

Platform-specific additional information

about the support of multiple partitions with

DB2 for Linux, UNIX, and Windows

1448655 Inst. NetWeaver 7.3 - Diagnostics Agent

installation

Problems discovered after the publication of

the installation guide or post-installation

steps

737368 Hardware requirements of Java

Development

Information on the hardware requirements

for usage type Development Infrastructure

(DI), which depends on the size of your

development team.

855498 Installation Prerequisite Checker SAP Software on UNIX, Windows, and IBM i:

Checking OS Dependencies

73606 Supported Languages and Code Pages Information on possible languages and

language combinations in SAP systems

171356 Linux only: SAP software on Linux:

Essential comments

This SAP Note contains Linux-specific

information about the SAP system

installation.

1067221 Central Note for Heterogeneous

Installation

This SAP Note and its related SAP Notes

describe the released operating system and

database combinations for heterogeneousSAP systems landscapes.

1.4 Accessing the SAP Library

The references to SAP NetWeaver Librarydocumentation in this installation guide always refer to

the following on SAP Help Portal:

http://help.sap.com/nw731 Application Help SAP Library: English

1 Introduction

1.4 Accessing the SAP Library

2011-11-21 PUBLIC 9/132
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=101809&_NLANG=en&_NVERS=0http://help.sap.com/nw731http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067221&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=171356&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=73606&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=855498&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=737368&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1448655&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=702175&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1363169&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=101809&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1584218&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1552840&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1407532&_NLANG=en&_NVERS=0


10/132

This page is left blank for documentsthat are printed on both sides.


11/132

2 Installation Options Covered by thisGuide

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.

Standard system[page 11] (formerly known as central system)

Distributed system[page 12]

High-availability system[page 13]

You can install one or more additional application server instances[page 14] to an existing standard,

distributed, or high-availability system.

You can install a host agent separately[page 17].

2.1 Standard System

You can install a standardsystem on a singlehost.

In a standard system, all main instances run on a single host:There are the following instances:

Central services instance (SCS instance)

Enqueue replication server instance (ERS instance) for the SCS instance (optional)

Database instance (DB)

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].

2 Installation Options Covered by this Guide

2.1 Standard System

2011-11-21 PUBLIC 11/132


12/132

Figure 1: 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 distributedsystem, every instance can run on a separate host:

Central services instance for Java (SCS instance)

Enqueue replication server instance (ERS instance) for the SCS instance (optional)


The Java stack uses its own database schema in the database

Primaryapplication 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].


2.2 Distributed System

12/132 PUBLIC 2011-11-21


13/132

Figure 2: Distributed 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 andstopped at the same time.

In a high-availabilitysystem, every instance can run on a separate host:

There are the following instances:

Central servicesinstance for Java (SCS instance)

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.


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.


2.3 High-Availability System

2011-11-21 PUBLIC 13/132


14/132

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.

Figure 3: 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: The host of any instance of the existing SAP system (exceptions see below)

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


15/132

Additional Application Server Instance for a Standard System

For example, the following figure shows a standard system with additional application server instances

that run:

On the main host of the SAP system, that is on the host on which the primary application serverinstance and the database instance run

On dedicated hosts

Figure 4: 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:

On the main host of the SAP system, that is, on the host on which the primary application server

instance runs

On dedicated hosts

We do notrecommend you to install additional application server instances on the SAP global host.



2011-11-21 PUBLIC 15/132


16/132

Figure 5: Additional 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 thatrun:

On the host of the primary application server instance

On dedicated hosts

We do notrecommend you to install additional application server instances on the switchover cluster

infrastructure.



16/132 PUBLIC 2011-11-21


17/132

Figure 6: 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:

You want to manage a host that does not have an SAP instance or component.

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.


2.5 Host Agent as a Separate Installation

2011-11-21 PUBLIC 17/132


18/132

This page is left blank for documentsthat are printed on both sides.


19/132

3 Planning

3.1 Planning Checklist

This section includes the planning steps that you have to performfor 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. You have chosen your installation scenario according to theMaster Guide SAP NetWeaver 7.3 including

Enhancement Package 1available at http://service.sap.com/installnw73.

2. 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. You check the hardware and software requirements[page 20] on every installation host of the system

landscape that you want to install.

2. You identify basic SAP system installation parameters[page 25].

3. You carefully plan the setup of your database[page 33].

4. You decide on the transport host to use[page 40].

5. You decide whether you want to integrate LDAP Directory Services in your SAP system[page 99].

6. To install a high-availability system, you read Planning the Switchover Cluster[page 41].

7. Optionally, you decide whether you want to install multiple components in one database (MCOD)[page

103].

8. You can now continue with Preparation[page 45].

Additional Application Server Instance

1. 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.

2. You identify basic SAP system installation parameters[page 25].

3. You can now continue with Preparation[page 45].

3 Planning

3.1 Planning Checklist

2011-11-21 PUBLIC 19/132
http://service.sap.com/installnw73


20/132

3.2 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating system

and the SAP instances.

CAUTION

If your hosts do not fully meet the requirements, you might experience problems when working

with the SAP system.

Prerequisites

Make sure that the host name meets the requirements listed in SAP Note611361.

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. Check the Product Availability Matrixat http://service.sap.com/pamfor supported operating

system releases.

2. Check the hardware and software requirements using:

The Prerequisite Checker:

Standalone (optional) before the installation processFor more information, see Running the Prerequisite Checker Standalone[page 21].

Integrated in the installation tool (mandatory) as part of the installation process

For more information, see Running SAPinst[page 69].

NOTE

For the most recent updates to the Prerequisite Checker, always check SAP Note855498.

The Hardware and Software Requirements Tables[page 21]

3. If you want to install a productionsystem, the values provided by the Prerequisite Checker and

the hardware and software requirements checklists are not sufficient. In addition, do the following:

You use the Quick Sizertool available at http://service.sap.com/sizing.

You contact your hardware vendor, who can analyze the load and calculate suitable hardware

sizing depending on:

The set of applications to be deployed

How intensively the applications are to be used

The number of users

3 Planning


20/132 PUBLIC 2011-11-21
http://service.sap.com/pamhttp://service.sap.com/pamhttp://service.sap.com/sizinghttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=855498&_NLANG=en&_NVERS=0http://service.sap.com/pamhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=611361&_NLANG=en&_NVERS=0


21/132

3.2.1 Running the Prerequisite Checker in Standalone Mode(Optional)

Before installing your SAP system, you can run the Prerequisite Checkerin standalone mode to check the

hardware and software requirements for your operating system (OS) and the SAP instances.

RECOMMENDATION

We recommend that you use boththe Prerequisite Checkerand the requirements tables for reference.

NOTE

When installing your SAP system, SAPinst automatically starts the Prerequisite Checkerand checks

the hardware and software requirements in the background.

Procedure

1. Make the medium for the installation master (folder _IM__) available on the

installation host. For more information, see Preparing the Installation Media[page 59].

RECOMMENDATION

Make installation media locallyavailable. For example, reading media mounted with

Network File System (NFS) might fail.

Copy at least the medium for the installation master (folder

_IM__) to the local file system of the installation host.

2. Start SAPinst[page 69].

3. On the Welcomescreen, choose Preparations Prerequisites Check .4. Follow the instructions in the SAPinst dialogs and enter the required parameters.

NOTE

For more information about each parameter, position the cursor on the parameter field and

choose F1 in SAPinst.

When you have finished, the Parameter Summaryscreen 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.

5. To start the prerequisites check, choose Next.

Result

The Prerequisite Checker Resultsscreen 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.

3 Planning


2011-11-21 PUBLIC 21/132


22/132

NOTE

The information here is notintended 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 Note171356.

Hardware Requirements

Requirement Values and Activities

Hardware Your operating system platform must be 64-bit.

Processing Units The number or physical or virtual processing units usable by the operating system

image must be equal or greater than 2 for application server instances and database

instances.

For an SCS instance running on a separate host, 1 physical or virtual processing units

usable by the operating system image might be sufficient.

Examples for processing units are Processor Cores or Hardware Threads(Multithreading).

In a virtualized environment, you must take care that adequate processor resources

are available to support the workloads of the running SAP systems.

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 notsupported.

For more information, see the DB2-specific requirements for your database versionat http://www.ibm.com/software/data/db2/udb/sysreqs.html.

Optical Media Drive ISO 9660 compatible

Hard Disk Space General Requirements:

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].

1.2 GB of temporary disk space for the installation.

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 StorageManager (TSM) (for database backup/restore).

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.

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.

Instance-Specific Requirements:

If you install several instanceson one host, you have to add up the

requirements accordingly.

3 Planning


22/132 PUBLIC 2011-11-21
http://www.ibm.com/software/data/db2/udb/sysreqs.htmlhttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=171356&_NLANG=en&_NVERS=0


23/132


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.

Central services instance (SCS) for Java:Minimum 3.5 GB

Enqueue replication server instance for the SCS (if required):

Minimum 3.5 GB

Database Instance:

For specific disk space information required for an SAP system installation

on DB2 V9.7, see SAP Note1584218.

NOTE

For safety reasons (system failure), the file systems must be

physically distributed over several disks, or RAID-technology

must be used.

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].

Primary application server instance:

Minimum 6 GB

Additional application server instance:

Minimum 6 GB

Host agent:

Minimum 1 GB

Diagnostics agent:

Minimum 3 GB

RAM The following lists the RAM requirements for each instance.If you install several instanceson one host, you have to add up the requirements

accordingly.

Central services instance for Java (SCS)

Minimum 1 GB

Enqueue replication server instance for the SCS (if required)

Minimum 1 GB

Database Instance:

Minimum 2 GB

Primary application server instance:

Minimum 8 GB

For more information about RAM required for usage type BI Java, see SAPNote927530.

For more information about RAM required for usage type Development

Infrastructure (DI), see SAP Note737368.

Additional application server instance:

Minimum 8 GB

Host agent:

Minimum 0.5 GB

Diagnostics agent:

Minimum 1 GB

Refer to SAP Note1382721for the commands to display the RAM size on Linux.

3 Planning


2011-11-21 PUBLIC 23/132
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1382721&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1382721&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=737368&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=927530&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1584218&_NLANG=en&_NVERS=0


24/132


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 Note1597355. 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 executememlimitsas follows:

1. Make sure that the SAPCARprogram is available on the installation host. If

SAPCARis not available, you can download it from http://service.sap.com/

swdc.

2. Make the SAPEXE.SARarchive available on the installation host. This archive is

contained in the folder K___/DBINDEPof the

installation media.

3. To unpack the file memlimits, enter the following command:

SAPCAR -xvfg SAPEXE.SAR memlimits

4. Start memlimitsusing the following command:

./memlimits -l 20000In case of error messages, increase the paging space and rerun memlimitsuntil

there are no more errors.

Software Requirements


Database software /

Client software

DB2 V9.7 database software or DB2 V9.7 client software (automatically installed by

SAPinst)

CAUTION

For the installation of your SAP system, onlythe English versionof the

DB2 database is supported. You must onlyuse the DB2 software that is provided by the SAP

installation DVDs.

Operating System

Version

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 Note171356for Linux kernel versions certified by SAP.

To check the Linux kernel parameters for your Linux distribution, see one of the

following SAP Notes:

RHEL6: SAP Note1496410

SLES 11 SP1: SAP Note1310037

NOTE

Modify the kernel parameter msgmnias follows:

For SLES 11, see SAP Note1310037.

For RHEL6, see SAP Note1496410.

In file /etc/sysctl.conf, add the line kernel.msgmni=1024.

Activate the modified kernel parameters with the following command:

sysctl p

In most cases these steps are sufficient.

3 Planning


24/132 PUBLIC 2011-11-21
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1496410&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1310037&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1310037&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1496410&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=171356&_NLANG=en&_NVERS=0http://service.sap.com/pamhttp://service.sap.com/pamhttp://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1597355&_NLANG=en&_NVERS=0


25/132


For more information about required kernel parameter modifications on DB2,

see the IBM documentation Quick Beginnings for DB2 Servers.

National Language

Support (NLS)

Make sure that National Language Support (NLS) and corresponding localesare

installed.

Check that the required localessuch as the following are available:

de_DE, en_US

Check SAP Note187864for information about corrected operating system

locales and SAP blended Code Pages.

System Language For the installation, you must choose English as the operating system language on

all Linux hosts that run SAP software.

Other Requirements


Host Name To find out physicalhost names, open a command prompt and enterhostname.

For more information about the allowed host name length and characters

allowed for SAP system instance hosts, see SAP Note611361.

If you want to use virtualhost names, see SAP Note962955.

Login Shell 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 Note202227.

Required additional shell 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.

Shared file systems for

decentralized systems

If application servers are installed decentralized, then a shared file system must

be installed, for example Network File System (NFS).

C compiler Make sure that the C compiler gcc is installed.

3.3 Basic SAP System Installation Parameters

SAPinst prompts for input parameters during the Define Parametersphase of the installation.

You can install your SAP system either in Typicalor Custommode:

TypicalIf 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:

SAP system ID and Database Connectivity Parameters

Master password

JCE Unlimited Strength Jurisdiction Policy files archive (only prompted if you install usage

type Adobe Document Services)

SAP system profile directory only for systems with instances on separate hosts

UME Configuration

3 Planning


2011-11-21 PUBLIC 25/132
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=187864&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=202227&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=962955&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=611361&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=187864&_NLANG=en&_NVERS=0


26/132

If you want to change any of the default settings, you can do so on the Parameter Summaryscreen.

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 Summaryscreen.

NOTE

You cannot change from Customto Typicalmode or from Typicalto Custommode on the Parameter

Summaryscreen.

The following tables list the basic SAP system installation parameters that you need to specify before

installing your SAP system:

SAP System Parameters

SAP System Database Parameters

Diagnostics Agent Parameters

For all other installation parameters, use the F1 help in the SAPinst screens.

SAP System Parameters

Parameters Description

Unicode System A Java standalone system is always a Unicode system.

SAP System ID The SAP system ID identifies the entire SAP system.

SAPinst prompts you for the when you execute the firstinstallation

option to install a new SAP system.If there are further installation options to be executed, SAPinst prompts you for

theprofiledirectory. 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:

Is unique throughout your organization. Do not use an existing

when installing a new SAP system.

Consists of exactly three alphanumeric characters

Contains only uppercase letters

Has a letter for the first character

Does not include any of the following, which are reserved IDs:

ADD ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR

GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS

OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID

USE USR VAR

3 Planning


26/132 PUBLIC 2011-11-21


27/132


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

System

Technical identifier for internal processes. It consists of a two-digit number from

00 to 97.

The instance number must be unique on a host. That is, if more than one SAP

instance is running on the same host, these instances must be assigned different

numbers.

If you do not enter a specific value, the instance number is set automatically to

the next free and valid instance number that has not yet been assigned to the SAP

system to be installed or to SAP systems that already exist on the installation host.

To find out instance numbers of SAP systems that already exist on the installation

host, look for subdirectories ending with of local (not mounted) /usr/sap/

directories.

The value 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 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.

3 Planning


2011-11-21 PUBLIC 27/132


28/132


The Java message server port uses the parameter rdisp/msserv_internalwith

default value 39, where is the instance number of the SCS message

server instance.

For more information about the parameters used for message server ports, seeSAP Note821875.

Java(TM) Cryptography

Extension (JCE) Unlimited

Strength Jurisdiction Policy

Files Archive

If you want to install usage type Adobe Document Services, make sure that you

download the unlimitedversion of the JCE Jurisdiction Policy Files 6 archive. For

more information about where to download it, see SAP Note1240081.

CAUTION

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.SecurityExceptionduring the Create Secure Storestep,

stating that the jurisdiction policy files are not signed by trusted signers.

UME Configuration SAPinst prompts you for how to configure the UME during the input phase ofthe installation.

You can choose between the following options:

Use Java Database

If you choose this option, administrators can manage users and groups with

the UME Web admintool and SAP NetWeaver Administratoronly.

For LDAP, use this configuration for the installation and change the

configuration to LDAP after the installation.

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 tooland 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 Note718383.

NOTE

If you want to use LDAP as data source, choose Use Java Databaseand

change to LDAP after the installation has finished.

If you want to use the User Management Engine for an existing ABAP

system, choose Use ABAP.

If you install a PI system, you have the following options:

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:

Use External ABAP System: This sets up the ABAP-based User

Management Engine on the Integration Server system.

Use Java Database: This sets up "local" user management on the

system of the non-central AAE.

If you want to install non-central Advanced Adapter Engine

(AAE)as optional standalone unit for an Advanced Adapter

3 Planning


28/132 PUBLIC 2011-11-21
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=718383&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=718383&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1240081&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=821875&_NLANG=en&_NVERS=0


29/132


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 Administratorand 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 Guestand 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

Number

This is the instance number on the application server of the central ABAP system

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//DVEBMGS. The value 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 hostnameat 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_ADMINmust 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_GUESTmust exist on the external ABAP system.

Key Phrase for Secure Store

Settings

This is a random word or phrase that is used to encrypt the secure store.

The Java EE engine uses this phrase to generate the key that is used to encrypt the

data.

The uniqueness of the phrase you use contributes to the uniqueness of the

resulting key.

RECOMMENDATION

Use a long key phrase that cannot be guessed easily. Use both uppercase and

lowercase letters in the phrase and include special characters.

NOTE

If you choose Typicalmode, 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.

Path to SAPCRYPTO.SAR The SAP Cryptographic Library is required to enable Secure Sockets Layer (SSL)

encryption of HTTP connections. In most cases it is installed automatically from

3 Planning


2011-11-21 PUBLIC 29/132


30/132


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 thecountry 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 re-

export 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

System

If you want to use HTTP-based URL frameworks such as Web Dynpro applications,

you have to specify the DNS domain name for the SAP system.

The DNS Domain Name is used to calculate the Fully Qualified Domain Name

(FQDN), which is configured in profile parameter SAPLOCALHOSTFULL. FQDN is the

fully qualified domain name for an IP address. It consists of the host name and the

domain name:

.

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 Note654982.

EXAMPLE

If your application server host is called kirk.wdf.sap.com, the DNS Domain

Name is wdf.sap.com.

SAP System Database Parameters


Database ID The identifies the database instance. SAPinst prompts you for the

when you are installing the database instance.

The can be the same as the .

CAUTIONChoose your database ID carefully. Renaming is difficult and requires you

to reinstall the SAP system.

If you want to install a new database:

Make sure that your database ID:

Is unique throughout your organization





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

3 Planning


30/132 PUBLIC 2011-11-21
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=654982&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=455033&_NLANG=en&_NVERS=0


31/132


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

db2has the DB2 system administration authorities and belongs to group

dbadm, which has DB2 SYSADMauthorities. By default, user db2is a

member of group dbadm.

Java database connect user

(sapdb)

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 isdifferent from the schema name.

ID of the dbadm

group

NOTE

In a multipartitioned database environment, the group ID mustbe the same

on all database partition servers.

dbadmgroup Members of this group have DB2 SYSADMauthorities. By default, user db2

is a member of this group.

ID of the dbctl

group

NOTE



dbctlgroup Members of this group have DB2 SYSCTRLauthorities. By default, admisa member of this group.

ID of the dbmnt

group

NOTE



dbmntgroup Members of this group have DB2 SYSMAINTauthorities.

ID of the dbmon

group

NOTE



dbmongroup Members of this group have DB2 SYSMONauthorities.

By default, sapdb(the Java database connect user) is a member of thisgroup.

Database Communication

Port

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 5912as default value.

NOTE

SAPinst requests this value during the database instance installation.

Database Partition Group

Mapping

NOTE

SAPinst onlyasks this parameter if you are performing a heterogeneous

system copyand if the following condition is met: You run SAPinst to install

3 Planning


2011-11-21 PUBLIC 31/132


32/132


the target database in a multipartitioned database environment using the

R3Load method.

You can assign the displayed node groups to a database partition.Drive for Diagnostic Data Location of the db2diag.logthat contains diagnostic data required in case of, for

example, a database crash.

Add sapdata directories For an installation on DB2 V9.7, the tablespaces are stored in /db2//

sapdata.

By default, SAPinst creates four sapdata directories (sapdata1, sapdata2,

sapdata3, sapdata4).

NOTE

Be aware that the first part, for example /db2//is definite and you

can only enter a value for sapdata.

Use Change, that is, add or remove the names and number of thesapdatadirectories.

Database Memory or

Instance Memory

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_MEMORYincludes the database- and application-specific

memory segments that are used by DB2.

DB2 Software Path 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.


System ID of Diagnostics

Agent

SAPinst sets the system ID of the diagnostics agent, , to DAAby default.

IfDAAis already used, SAPinst assigns another default system ID. You can overwrite

the default system ID as required.

CAUTION

Choose the carefully. Renaming is difficult and requires you to

reinstall the diagnostics agent.

Make sure that the :

Either does not yet exist on the local installation host or does already exist

but was only used for a diagnostics agent installation





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

3 Planning


32/132 PUBLIC 2011-11-21


33/132


OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID

USE USR VAR

Instance Number of the

Diagnostics Agent

Technical identifier for internal processes for the diagnostics agent, consisting of

a two-digit number from 00 to 97. Default is 97.

If 97 is already used for an instance number, the diagnostics agent instance number

is set automatically to the next free and valid instance number.

The instance number is used to specify the name of the diagnostics agent instance

directory that SAPinst automatically creates during the installation.

The directory of the diagnostics agent instance is called SMDA.

For more information, see SAP Directories[page 49].

The same restrictions apply as in Instance Number of the SAP System (see above).

SLD Destination You can choose between the following options:

Register in existing central SLD

SAPinst only prompts you for the parameters listed below in this table if you

select this option.

RECOMMENDATION

We recommend that you select this option.

No SLD destination

If you select this option:

You have to configure the SLD destination for the diagnostics agent

manually after the installation with SAPinst has finished.

SAPinst does notprompt you for the parameters listed below in this

table.

SLD HTTP Host The host name of the System Landscape Directory (SLD)

SLD HTTP Port The HTTP port of the Java system where the SLD is installed. The following namingconvention applies:

500.

EXAMPLE

If the instance number of your Java system is 01, the SLD HTTP Port is 50100.

SLD Data Supplier User and

password

You have to enter the existing SLD Data Supplier User and password of the central

SLD.

3.4 Setup of Database LayoutNOTE

The following sections apply especiallyto 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:

3 Planning

3.4 Setup of Database Layout

2011-11-21 PUBLIC 33/132


34/132

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, andWindows

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 mustbe located on the shared disk.

For more information, see the document IBM DB2 High Availability Solution: IBM Tivoli System

Automation for Multiplatformsat:

http://service.sap.com/instguidesnw 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 Home directory of user db2and contains theDB2 instance data for and the DB2 software.

Size: at least 1 GB

/db2//log_dir Contains at least the online database log files.

Size: at least 1.4 GB

/db2//db2dump Contains DB2 diagnostic log files, DB2 dump files, and

further service engineer information.

Size: 100 MB

With DB2's automatic storage management:

/db2//sapdata

No automatic storage management:

/db2//sapdata

SAP data for container type database managed space (DMS)

FILEor for use of DB2's automatic storage

management. By default, SAPinst creates four

sapdatadirectories. If you require more or fewer

3 Planning


34/132 PUBLIC 2011-11-21
http://service.sap.com/instguidesnwhttp://service.sap.com/instguidesnw


35/132

File System/Logical Volume Description

sapdatadirectories, you can change this on the SAPinst

Sapdata Directoriesdialog.

Temporary tablespaces are equally distributed over the

sapdatadirectories. Make sure that you provideenough free space in your sapdatadirectories for

temporary data.

For more information about the size, see the current

installation note[page 8] for DB2 for Linux, UNIX, and

Windows.

NOTE

In a production system, you must make

sure that the sapdatadirectories are located

in different file systems. Otherwise, system

performance can decrease. For moreinformation, see Data Safety and Performance

Considerations for Database Directories[page 39].

If you add additional sapdatadirectories

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].

File System/Logical Volume Permissions Owner Group

/db2/ 755 db2 dbadm

/db2//log_dir 755 db2 dbadm

/db2//db2dump 755 db2 dbadm

With DB2's automatic storage

management:

/db2//sapdata

No automatic storage

management:

/db2//sapdata

750 db2 dbadm

More Information

SAP Directories[page 49]

3 Planning


2011-11-21 PUBLIC 35/132


36/132

3.4.2 Users and Groups

SAPinst creates the following users and groups as shown in the following table:

User Home Directory Group

db2 /db2/db2 dbadm

adm can be chosen sapsys(primary group),

dbctl(secondary)

DefaultJavadatabase connect user:

sapdb

You may change this user during

the installation.

/home/sapdb dbmon(primary group)

NOTE

As of Enhancement Package 1 for SAP NetWeaver 7.3, you can specify the name of the Java connectuser (sapdb) 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 ConnectivityWith 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:

Figure 7: Directory Structure of the Database Client

3 Planning


36/132 PUBLIC 2011-11-21


37/132

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 ofthe JDBC driver in the local exedirectory.

Therefore, by exchanging the JDBC driver in the globaldirectory, 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 Note1363169.

3.4.4 DB2 Tablespaces

During the dialog phase of the installation, SAPinst offers to create the following tablespace types:

Data and index tablespaces managed by DB2's automatic storage management (AutoStorage)

During the installation, SAPinst assigns the sapdatadirectories to the database, which

automatically distributes all tablespaces over the sapdatadirectories or file systems. In addition,

the database automatically adjusts the tablespace sizes as long as there is enough free space left in

the sapdatadirectories or file systems.

If one of the sapdatadirectories becomes full, new stripe sets are automatically created in the

remaining sapdatadirectories.

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 IBMDB2 for Linux, UNIX, and Windows Sapdata Directories dialog.

DMS File tablespaces in autoresizemode

SAPinst creates all DMS tablespaces with FILE containers in autoresizemode as well as one tablespace

container for each tablespace in every sapdatadirectory or file system. DB2 automatically extends

the size of all DMS FILE tablespaces in autoresizemode as long as there is space left in the sapdata

directories or file systems.

With DMS FILE tablespaces in autoresizemode, 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].

3 Planning


2011-11-21 PUBLIC 37/132
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1363169&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1363169&_NLANG=en&_NVERS=0


38/132

Other tablespace types

If you want to use other tablespace types, for example SMSor DMS DEVICE (raw devices), you have

to create them manually. Therefore, you deselect the option Create tablespaces with SAPinstduring

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 disableautoresizemode for databases that are not

set up in AutoStoragemode.

To move tablespaces of a DB2 release lower than DB2 V9.7 from AutoStorageto 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 endingcontainer001

.Therefore, #BTABDhas at least the container #BTABD.container001. The next

container is called #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].

3 Planning


38/132 PUBLIC 2011-11-21
http://service.sap.com/instguideshttp://service.sap.com/instguides


39/132

3.4.5 Data Safety and Performance Considerations forProduction 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:

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 retentionmode. Otherwise, log files

cannotbe applied to the database rollforward operations. You can set the database to log

retentionmode 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].

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.

Since transaction data is lost if online log files are damaged, we recommend that the online log

directory log_diris 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

Note409127.

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

3 Planning


2011-11-21 PUBLIC 39/132
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=409127&_NLANG=en&_NVERS=0


40/132

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.

By default, the SAP installation tool creates tablespaces that are managed by DB2s automatic storage

management (AutoStoragetablespaces). Tablespaces in AutoStoragemode offer maximum ease of use

and low administrative cost. In addition, modern file systems avoid most concurrency problems.

If you are not using AutoStoragetablespaces, 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:

Distribute heavily used tablespaces across separate disks.

Avoid putting multiple containers of one tablespace onto the same device.

Move heavily used tables into their own tablespaces that reside on dedicated disks. Put containers of index tablespaces and their respective data tablespaces on different disks.

Do not configure operating system I/O (for example, swap, paging or heavily spool) on DB2

data disks.

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

createdin 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 InformationSee the Administration Guide:Performancethat 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

Nw731 Linux Db6 Java

Documents

Transcript of Nw731 Linux Db6 Java