Installation Guide SAP NetWeaver 7.

0 Java including Enhancement Package 1 SR1 on AIX: IBM DB2 for Linux, UNIX, and Windows
Using SAPinst
Including the following: ■ SAP NetWeaver Application Server Java (AS Java) ■ SAP NetWeaver Business Intelligence Java Components (BI) ■ SAP NetWeaver Development Infrastructure (DI) ■ SAP NetWeaver EP Core (EPC) ■ SAP NetWeaver Enterprise Portal (EP) Target Audience ■ System administrators ■ Technology consultants

PUBLIC Document version: 1.0 – 2009-05-04

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 downwardcompatible 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/182

PUBLIC

2009-05-04

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace http://service.sap.com/ instguides. The following table provides an overview on the most important document changes:
Version Date Description

1.0

2009-05-04

Initial version

2009-05-04

PUBLIC

3/182

Table of Contents

Chapter 1 1.1 1.2 Chapter 2 2.1 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.3 2.3.1 2.3.2 2.3.3 2.3.3.1 2.3.3.2 2.3.3.3 2.3.4 2.4 2.5 2.6 2.7 2.7.1 2.7.2 2.7.3 2.7.4 2.8 Chapter 3

Introduction ........................................................................................................... New Features ............................................................................................................. SAP Notes for the Installation .................................................................................. Planning ................................................................................................................... Planning Checklist .................................................................................................... Installation Options Covered by this Guide ........................................................... Central System .......................................................................................................... Distributed System .................................................................................................... High-Availability System .......................................................................................... Dialog Instance .......................................................................................................... Installation of Additional Usage Types in an Existing SAP System ....................... Hardware and Software Requirements ................................................................... Running the Prerequisite Checker in Standalone Mode (Optional) .................... Requirements for a Central System ........................................................................ Requirements for a Distributed or a High Availability System ............................. Requirements for a Central Services Instance ........................................................ Requirements for the Central Instance .................................................................. Requirements for the Database Instance ................................................................ Requirements for a Dialog Instance ........................................................................ SAP System Transport Host ..................................................................................... Planning User and Access Management ................................................................. Basic SAP System Parameters ................................................................................... Setup of Database Layout ......................................................................................... Required File Systems for DB2 for Linux, UNIX, and Windows ........................... Users and Groups ...................................................................................................... DB2 Tablespaces ........................................................................................................ Data Safety and Performance Considerations for Production Systems ................ High Availability: Planning the Switchover Cluster .............................................. Preparation ..............................................................................................................

9 10 13 15 15 15 16 16 17 18 21 21 23 24 27 28 31 34 37 40 40 41 52 52 54 55 56 58 63

4/182

PUBLIC

2009-05-04

3.1 3.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.4 3.5 3.6 3.7 3.8 3.9 3.10 Chapter 4 4.1 4.2 4.3 4.4 4.5 Chapter 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14

Preparation Checklist ............................................................................................... Creating Operating System Users and Groups ....................................................... Setting Up File Systems and Raw Devices ............................................................... SAP Directories .......................................................................................................... Directory Structure of the New DB2 Client Connectivity .................................... Setting Up File Systems for a High-Availability System ......................................... Configuring Network File System for a High-Availability System ....................... Using Virtual Host Names ........................................................................................ Performing Switchover Preparations for High Availability ................................... Exporting and Mounting the Global Transport Directory ................................... Generating the SAP Solution Manager Key ............................................................ Installing the Java Development Kit ....................................................................... Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive ...... Preparing the Installation DVDs .............................................................................. Installation .............................................................................................................. Installation Checklist ................................................................................................ Exporting and Mounting Global Directories: Distributed and High-Availability Systems ...................................................................................................................... Performing a High-Availability Installation ............................................................ Running SAPinst ....................................................................................................... SAPinst Installation Options .................................................................................... Post-Installation ..................................................................................................... Post-Installation Checklist ....................................................................................... Logging On to the Application Server .................................................................... Logging On to the Portal .......................................................................................... Logging On to the SAP NetWeaver Development Infrastructure (NWDI) .......... Configuring User Management ............................................................................... Ensuring User Security ............................................................................................. Installing the SAP License ......................................................................................... High Availability: Setting Up Licenses ..................................................................... Applying the Latest Kernel and Support Package Stacks ...................................... Configuring Remote Connection to SAP Support ................................................ Performing Initial Java Configuration ..................................................................... Enabling Recoverability of the Database ................................................................. Performing Post-Installation Steps for Adobe Document Services ...................... Setting Environment Variable CPIC_MAX_CONV ..............................................

63 63 65 66 71 72 74 76 76 77 78 78 79 80 83 83 87 87 88 95 99 99 100 101 102 103 103 107 108 109 109 109 111 113 113

2009-05-04

PUBLIC

5/182

5.15 5.16 5.17 5.18 5.19 5.20 5.21 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.11.1 6.11.2 6.11.3 6.11.4 6.11.5 6.12 6.13 6.14 6.14.1 6.14.2 6.14.3 6.15 6.16 6.17

Configuring the Connection to a Central System Landscape Directory ............. Updating Component Repository Content in the System Landscape Directory .................................................................................................................... Configuring the Application Sharing Server .......................................................... Running the Configuration Wizard ........................................................................ Post-Installation Steps for the Diagnostics Agent .................................................. Performing a Full Installation Backup .................................................................... Accessing Configuration Documentation in SAP Solution Manager .................. Additional Information ........................................................................................ Installation of Multiple Components in One Database ......................................... MCOD Tablespaces and File Systems ...................................................................... Integration of LDAP Directory Services .................................................................. Preparing an External ABAP System as Source for User Data ............................... Setting up Swap Space for AIX ................................................................................. Creating AIX Groups and Users .............................................................................. Setting Up File Systems and Raw Devices for AIX ................................................. Dialog Instance Installation for an Upgraded System only: Updating Profiles ........................................................................................................................ Mounting a CD / DVD for AIX ................................................................................ Exporting and Mounting Directories via NFS for AIX ........................................... Additional Information About SAPinst .................................................................. Using SAPinst GUI .................................................................................................... Interrupted Installation with SAPinst ..................................................................... Performing a Remote Installation with SAPinst .................................................... Starting the SAPinst GUI Separately ....................................................................... Entries in the Services File Created by SAPinst ....................................................... Installation of Additional Software Units or Usage Types in an Existing SAP System ........................................................................................................................ Creating Tablespaces Manually (Optional) ............................................................ Starting and Stopping SAP System Instances ......................................................... Starting and Stopping SAP System Instances Using the SAP Management Console ...................................................................................................................... Starting and Stopping SAP System Instances Using Scripts .................................. Starting and Stopping the Diagnostics Agent Using Scripts ................................. Creating a User for LDAP Directory Access ............................................................ Accessing the SAP Java Documentation ................................................................. Usage Type-Specific Initial Technical Configuration ............................................

114 114 115 115 117 117 118 121 122 123 124 128 131 132 133 134 135 136 138 138 139 140 142 144 144 149 150 150 153 156 157 158 159

6/182

PUBLIC

2009-05-04

6.17.1 6.17.1.1 6.17.1.2 6.17.1.3 6.17.2 6.17.3 6.17.4 6.17.4.1 6.17.4.2 6.17.4.3 6.18 6.19 6.19.1 6.19.2 6.20 6.21 6.22 6.22.1 6.22.2 6.22.3 Chapter A A.1 A.2

Initial Technical Configuration for SAP NetWeaver Application Server Java (AS Java) ............................................................................................................................ Initial Technical Configuration for Adobe Document Services ........................... Initial Technical Configuration for Composite Application Framework Core (CAF) .......................................................................................................................... Initial Technical Configuration for the System Landscape Directory (SLD) ....... Initial Technical Configuration for Development Infrastructure (DI) ................ Initial Technical Configuration for the Portal (Usage Types EPC and EP) .......... Initial Technical Configuration for BI Java ............................................................. Configuring BI Java Information Broadcasting ...................................................... Process Chains: Transporting Texts for the Alert Category ................................. Renaming initialPermissionsBI.xml.template ........................................................ Heterogeneous SAP System Installation ................................................................. Troubleshooting ....................................................................................................... Troubleshooting with SAPinst ................................................................................ Troubleshooting for Portal Installation .................................................................. Deleting an SAP System ........................................................................................... Deleting a Diagnostics Agent ................................................................................... Deleting the Database Instance and Database Software Manually (Optional) .... Deleting a Database Schema Manually (Optional) ................................................ Deleting the Database and the DB2 Instance Manually (Optional) ..................... Deleting the DB2 Software Installation ..................................................................

159 160 160 161 162 164 165 165 166 166 166 166 167 167 169 171 172 172 173 174

Appendix .................................................................................................................. 175 Online Information from SAP ................................................................................. 175 Online Information from IBM ................................................................................. 177

2009-05-04

PUBLIC

7/182

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

1

Introduction

1 Introduction

This document explains how to install an SAP NetWeaver 7.0 Java system including enhancement package 1 SR1 (Support Release 1). You perform the installation using SAPinst. For more information about the current Support Package stack levels of SAP NetWeaver 7.0 including enhancement package 1 SR1, see SAP Note 789220. For more information about the SAP NetWeaver technology, see http://sdn.sap.com/irj/sdn/ netweaver. You can install SAP NetWeaver 7.0 Java including enhancement package 1 SR1 with the following usage types in a single installation run of SAPinst: ■ SAP NetWeaver Application Server Java (AS Java) ■ SAP NetWeaver Development Infrastructure (DI) ■ SAP NetWeaver EP Core (EPC) ■ SAP NetWeaver Enterprise Portal (EP) If you install usage type EP, note the following: ● You must install SAP NetWeaver Application Server Java (AS Java) and EP Core (EPC). ● The Application Sharing Server is installed automatically with usage type EP. For production use, we recommend that you install the server as an optional standalone unit on a dedicated host as described in this document. ■ SAP NetWeaver Business Intelligence Java Components (BI Java) You also have to install SAP NetWeaver Application Server Java (AS Java), EP Core (EPC) and SAP NetWeaver Portal (EP).
NOTE

This documentation describes how to install BI Java with a standalone Java system. We recommend that you install BI Java with a standalone Java system and that you configure the connection with BI ABAP on a standalone ABAP system after the installation. The software components of BI ABAP are contained in usage type AS ABAP. If you want to install BI Java with an SAP NetWeaver ABAP+Java system, proceed as described in SAP Note 1181025. For more information about the usage types of SAP NetWeaver and their interdependencies, see the document Master Guide – SAP NetWeaver 7.0 at http://service.sap.com/instguidesNW70. For restrictions, see SAP Note 1164532.
Constraints

You need to consider the following constraints before you start your installation:

2009-05-04

PUBLIC

9/182

1 1.1

Introduction New Features

■ Your operating system platform must be 64-bit.
NOTE

The only instance, you can still install on 32-bit is the dialog instance.
Naming Conventions

■ SAP system refers to SAP NetWeaver 7.0 system including enhancement package 1 SR1. ■ Java system refers to SAP NetWeaver 7.0 Java system including enhancement package 1 SR1. ■ Diagnostics Agent refers to SAP Solution Manager Diagnostics Agent.
IBM Product Terminology

■ DB2 V9.1 refers to IBM DB2 Version 9.1 for Linux, UNIX, and Windows. ■ DB2 V9.5 refers to IBM DB2 Version 9.5 for Linux, UNIX, and Windows.
NOTE

If content in this document relates to both versions, no version number is mentioned.

1.1 New Features
The following tables provide an overview of the new features related to the installation of this release:
CAUTION

Make sure that you read the release notes for your SAP system. You can find these at http://
service.sap.com/releasenotes SAP System Installation Area Description

SAPinst

64-bit support only for all instances except dialog instances

As of SAP NetWeaver 7.0 including enhancement package 1, SAPinst has the following new features: ■ You no longer have to install a Java Runtime Environment (JRE) to start the SAPinst GUI. However, you still have to install a Java Development Kit (JDK) to perform the installation with SAPinst (see Installing the Java Development Kit (JDK) [page 78]). ■ If you want to terminate SAPinst from the SAPinst GUI menu, you now have to choose SAPinst Cancel . If you choose File Exit , you only terminate the SAPinst GUI (see Using SAPinst GUI [page 138]). ■ You can directly access installation log files from the SAPinst GUI menu by choosing SAPinst Log Browser (see Using SAPinst GUI [page 138]). As of SAP NetWeaver 7.0 SR3, you must install an SAP system only on 64-bit operating systems. For the dialog instance, you can still use a 32-bit operating system. Therefore, you only see the folder Software Life-Cycle Options on the Welcome screen when you start the installation from a 32-bit installation master DVD. You might need to install dialog instances on 32-bit operating systems if you want to use 32-bit SAP NetWeaver components, such as Adobe document services. However,

10/182

PUBLIC

2009-05-04

1 1.1 Area

Introduction New Features Description

first check whether such 32-bit components can run on 64-bit operating systems. If so, we recommend running these 32-bit components on a 64-bit operating system. New dual stack (ABAP As of SAP NetWeaver 7.0 including enhancement package 1, you can install dual stack +Java) systems only for (ABAP+Java) systems only with usage type Process Integration (PI) or Mobile SAP NetWeaver Process Infrastructure (MI). This means you can only install a dual stack system either as a Integration (PI) and SAP Process Integration system or as a Mobile Infrastructure system. NetWeaver Mobile Infrastructure (MI) Installation option Java As of SAP NetWeaver 7.0 including enhancement package 1, the installation option Add-In for ABAP disabled Java Add-In for ABAP is disabled. That is, you can no longer install the Java Add-In to an existing ABAP system. SAP Solution Manager As of SAP NetWeaver 7.0 SR3, the installation of the Diagnostics Agent is part of the Diagnostics Agent Installation Master DVD. That is, you can choose between the following options: ■ If there is no Diagnostics Agent already installed on this physical or virtual host, it is installed automatically with an AS Java central instance and dialog instance. ■ You can also install it as a standalone engine, for example if you want a non-SAP system to be managed by SAP Solution Manager Diagnostics. The installation of the Diagnostics Agent as a standalone engine is not described in this installation guide, but in the Diagnostics Agent Setup Guide, which is available at http://service.sap.com/diagnostics Media Library . An SAP Solution Manager Diagnostics Agent (Diagnostics Agent) is a standalone Java program that runs on each of the systems managed by SAP Solution Manager Diagnostics. It gathers information and reports to the SAP Solution Manager system. For more information about the Diagnostics Agent, see http://service.sap.com/ diagnostics . Maintenance Optimizer All downloadable software components, released after April 2, 2007, are available exclusively through the Maintenance Optimizer in SAP Solution Manager. This comprises: ■ Support Package Stacks, Support Packages, and patches for Java instances, except for kernel patches ■ Legal changes ■ SAP applications and versions that are: ● Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and all applications based on this software, including SAP Business Suite 7 ● Optional for all SAP applications For more information, see http://service.sap.com/solman-mopz.
Operating Systems and Platforms Area Description

Support of Operating Systems and Platforms
Database-Specific Features Area

For supported operating system and database releases, see the Product Availability Matrix at http://service.sap.com/pam.

Description

SAP system installation

SAP systems that are based on SAP NetWeaver 7.0 SR3 and higher are installed on IBM DB2 Version 9.1 or Version 9.5 for Linux, UNIX, and Windows - in the following referred to as DB2 V9.1 and DB2 V9.5.

2009-05-04

PUBLIC

11/182

1 1.1 Area

Introduction New Features Description

DB2 software installation Support of IBM Tivoli System Automation for Multiplatforms (SA MP) by SAPinst

Self Tuning Memory Management (STMM) New DB2 Client Connectivity

As of DB2 V9.1, 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. SAPinst automatically installs and deinstalls the database software. SAPinst supports the use of IBM Tivoli System Automation for Multiplatforms (SA MP) to make your database high-available. For more information, see the document IBM DB2 High Availability Solution: IBM Tivoli System Automation for Multiplatforms at: http:// service.sap.com/instguidesnw70 Installation Installation – SAP NetWeaver Systems SAPinst automatically enables the DB2 feature Self Tuning Memory Management (STMM). STMM automatically tunes global memory depending on the workload of the database. ■ You no longer have to install DB2 software on the additional application server (formerly known as dialog instance). Instead, the CLI Driver that is centrally stored in the global directory is used. During the installation of the database instance, the DB2 CLI driver is automatically installed for the operating system of the database server. If you install an additional application server (that is, the first one on an additional operating system in your system landscape), SAPinst automatically installs the DB2 CLI driver for this operating system. Every time you start an SAP instance, the CLI driver is copied from the global directory to the local exe directory of this SAP instance. ■ The JDBC Driver is automatically installed by SAPinst into the global directory. You can update the JDBC driver automatically using a script whenever you install a new Fix Pack version of the database.
NOTE

Every time you start an SAP instance, the JDBC driver is copied from the global directory to the local exe directory of this SAP instance. For more information, see Directory Structure of the New DB2 Client Connectivity [page 71].
Documentation Area Description

Installation of Additional As of SAP NetWeaver 7.0 SR3, the documentation about how to install Software Units or Usage Types additional software units or usage types to an existing SAP NetWeaver system is included in section Additional Information of this installation guide. (see Installation of Additional Software Units or Usage Types in an Existing SAP System [page 144]).

12/182

PUBLIC

2009-05-04

1 1.2 Area

Introduction SAP Notes for the Installation Description

Separate installation guide for As of SAP NetWeaver 7.0 including enhancement package 1 SR1, the installation Application Sharing Server of Application Sharing Server as an optional standalone unit is no longer described in the installation guides for SAP NetWeaver Java, but in separate installation guides. The documentation Installation Guide – Application Sharing Server on <Operating System>: <Database> is available at: http://service.sap.com/installnw70 Installation - Standalone Engines

1.2 SAP Notes for the Installation
You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find at http:// service.sap.com/notes.
SAP Notes for the Installation SAP Note Number Title Description

1164532 1300536

Release Restrictions for SAP NetWeaver 7.0 EHP1 Inst. NetWeaver 7.0 EHP1 SR1 / Business Suite 7 SR1- UNIX

Customer information on restrictions in the production use of certain functions. UNIX-specific information about the SAP system and corrections to this documentation.
NOTE

1330707

702175

799699 1234384 855498 73606 737368

1067221

DB6: SAP NetWeaver 7.0 inc. EHP Database-specific information about the SAP 1 SR1/ Business Suite 7 SR1 – UNIX system installation (ABAP and Java) and corrections to this documentation. DB6: Supporting several database Platform-specific additional information about partitions with DB2 the support of multiple partitions with DB2 for Linux, UNIX, and Windows DB6: Required and Important information if your operating system recommended AIX fixes for DB2 is AIX. Inst. NetWeaver 7.0 EhP1 Problems discovered after the publication of the Diagnostics Agent installation installation guide or post-installation steps Installation Prerequisite Checker SAP Software on UNIX, Windows, and IBM i: Checking OS Dependencies Supported Languages and Code Information on possible languages and language Pages combinations in SAP systems Hardware requirements of Java Information on the hardware requirements for Development Infrastructure usage type Development Infrastructure (DI), which depends on the size of your development team. Central Note for Heterogeneous Heterogeneous ABAP system landscapes on Installation different operating systems have been released for some time. Heterogeneous Java system

2009-05-04

PUBLIC

13/182

1 1.2

Introduction SAP Notes for the Installation Title Description

SAP Note Number

1268493

925741

landscapes on different operating systems have now also been released. However, not every combination of operating system and database system is released. This SAP Note and its related SAP Notes describe the released operating system and database combinations. Installation of Additional Java Supplementary information for section Installation Usage Types / Software Units for of Additional Software Units or Usage Types in an Existing SAP Systems Based on SAP SAP System [page 144] NetWeaver 7.0 EHP1 Adobe Document Services with To use ADS in SAP landscapes on nonsupported Nonsupported Platforms platforms, you have to install an additional standalone SAP system with AS Java on a platform supported by ADS.

14/182

PUBLIC

2009-05-04

2 2.1

Planning Planning Checklist

2 Planning

2.1 Planning Checklist
You have to complete the following planning activities, which are described in more detail in the linked sections: 1. You plan your SAP system landscape according to the SAP NetWeaver Master Guide and the Technical Infrastructure Guide available at http://service.sap.com/installnw70 Planning . 2. You identify the required installation option for your system [page 15]. 3. You check the hardware and software requirements [page 21]. 4. You decide on the transport host to use [page 40]. 5. You plan user and access management [page 40]. 6. You identify basic SAP system parameters [page 41]. 7. You carefully plan the setup of your database [page 52]. 8. Only valid for: HA (UNIX) | You plan the switchover cluster [page 58] for a high-availability (HA) system.
End of: HA (UNIX) |

9. You can continue with Preparation [page 63]. The following planning activity is optional: ■ Installation of Multiple Components in One Database (MCOD) [page 122]

2.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. ■ Central system [page 16] ■ Distributed system [page 16] ■
Only valid for: HA (UNIX) |

High-availability system [page 17]
End of: HA (UNIX) |

■ You can install one or more dialog instances [page 18] to an existing central, distributed, or highavailability system. ■ You can install additional usage types in an existing SAP system [page 21].

2009-05-04

PUBLIC

15/182

2 2.2

Planning Installation Options Covered by this Guide

2.2.1 Central System
You can install a central system on a single host. In a central system, all main instances run on a single host: ■ Central services instance (SCS) ■ Database instance (DB) ■ Central instance

Figure 1:

Central Java System

Optionally you can install one or more dialog instances. For more information, see Dialog Instance [page 18].

2.2.2 Distributed System
In a distributed system, every instance can run on a separate host: ■ Central services instance (SCS) ■ Database instance (DB) ■ Central instance
NOTE

You can also use the SAP transport host or the SAP global host as your central instance host. Optionally you can install one or more dialog instances. For more information, see Installation of a Dialog Instance [page 18].

16/182

PUBLIC

2009-05-04

2 2.2

Planning Installation Options Covered by this Guide

Figure 2:

Distributed Java System

Only valid for: HA (UNIX) |

2.2.3 High-Availability System
In a high-availability system, every instance can run on a separate host: ■ Java Central Services Instance (SCS) ■ Database instance ■ Central instance We recommend that you run both the ASCS and the SCS in a switchover cluster infrastructure. Optionally you can install one to <n> dialog instances. For more information, see Installation of a Dialog Instance [page 18]. The following figures show examples for the distribution of the SAP instances in a high-availability system.

2009-05-04

PUBLIC

17/182

2 2.2

Planning Installation Options Covered by this Guide

Figure 3:

High-Availability System

End of: HA (UNIX) |

2.2.4 Dialog Instance
You can install one or more dialog instances for an existing SAP system. A dialog 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 dialog instances running on an operating system other than the central instance, see Heterogeneous SAP System Installation [page 166]. For example, you need to do this if your central instance runs on Solaris but the dialog instance is to run on Windows.
Dialog Instance for a Central System

For example, the following figure shows each of the three dialog instances that are running: ■ On the main host of the SAP system, that is on the host on which the central instance and the database instance run ■ On dedicated hosts

18/182

PUBLIC

2009-05-04

2 2.2

Planning Installation Options Covered by this Guide

Figure 4:

Dialog Instance for a Central System

For more information, see Central System [page 16].
Dialog Instance for a Distributed System

For example, the following figure shows each of the three dialog instances that are running: ■ On the main host of the SAP system, that is on the host on which the central instance and the database instance run ■ On dedicated hosts We do not recommend you to install dialog instances on the SAP global host.

2009-05-04

PUBLIC

19/182

2 2.2

Planning Installation Options Covered by this Guide

Figure 5:

Dialog Instance for a Distributed System

For more information, see Distributed System [page 16].
Only valid for: HA (UNIX) |

Dialog Instance for a High-Availability System

For example, the following figure shows each of the three dialog instances that are running on: ■ The host of the central instance ■ Dedicated hosts We do not recommend you to install dialog instances on the switchover cluster infrastructure.

20/182

PUBLIC

2009-05-04

2 2.3

Planning Hardware and Software Requirements

Figure 6:

Dialog Instance for a High-Availability System

For more information, see High-Availability System [page 17].
End of: HA (UNIX) |

2.2.5 Installation of Additional Usage Types in an Existing SAP System
If you want to install additional Java software units or usage types in an existing SAP system based on SAP NetWeaver 7.0 including enhancement package 1, you have to use the Java Support Package Manager (JSPM). You cannot use SAPinst to install additional software units or usage types in an existing SAP system. “Existing SAP system” means that it has at least AS Java. For more information, see Installation of Additional Software Units or Usage Types in an Existing SAP System [page 144]. Installation of Additional Software Units or Usage Types in an Existing SAP System [page 144]

2.3 Hardware and Software Requirements
You check that your hosts meet the hardware and software requirements for your operating system and the SAP instances.

2009-05-04

PUBLIC

21/182

2 2.3

Planning Hardware and Software Requirements CAUTION

If your hosts do not fully meet the requirements, you might experience problems when working with the SAP system.
Prerequisites

■ ■ ■ ■

Contact your OS vendor for the latest OS patches. Make sure that the host name meets the requirements listed in SAP Note 611361. Check your keyboard definitions. If you want to install a printer on a host other than the central 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: ■ The Prerequisite Checker in one of two modes: ● Standalone mode (optional) before the installation process For more information, see Running the Prerequisite Checker Standalone [page 23]. ● Integrated in SAPinst (mandatory) during the installation process For more information, see Running SAPinst [page 88].
NOTE

3.

For the most recent updates to the Prerequisite Checker, always check SAP Note 855498. ■ The hardware and software requirements checklists for: ● Central system [page 24] ● Distributed or high availability system [page 27] ● If you want to install one or more dialog instances, check the requirements for a dialog instance [page 37]. If you are installing a production system, the values provided by the Prerequisite Checker and the hardware and software requirements checklists are not sufficient. In addition, do the following: ■ You use the Quick Sizer tool available at http://service.sap.com/sizing. For more information about the Quick Sizer and available sizing guides, see the Master Guide – SAP NetWeaver 7.0 at http://service.sap.com/installnw70 Planning .
Only valid for: Development Infrastructure (DI) |

NOTE

If you want to install usage type Development Infrastructure (DI), also check SAP Note 737368 for system requirements and sizing.
End of: Development Infrastructure (DI) |

■ You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing depending on:

22/182

PUBLIC

2009-05-04

2 2.3

Planning Hardware and Software Requirements

● The set of applications to be deployed ● How intensively the applications are to be used ● The number of users

2.3.1 Running the Prerequisite Checker in Standalone Mode (Optional)
Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check the hardware and software requirements for your operating system (OS) and the SAP instances.
RECOMMENDATION

We recommend that you use both the Prerequisite Checker and the requirements tables for reference.
NOTE

When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks the hardware and software requirements in the background.
Prerequisites

■ You have prepared the installation master DVD on the required installation host [page 80]. ■ You make sure that the required prerequisites are met before starting SAPinst [page 88].
Procedure

1. 2. 3.

You start SAPinst [page 88]. On the Welcome screen, choose <Your SAP product> Software Life-Cycle Options Additional Preparations Prerequisites Check . Follow the instructions in the SAPinst dialogs and enter the required parameters.
NOTE

For more information about each parameter, position the cursor on the parameter field and choose F1 in SAPinst. When you have finished, the Parameter Summary screen appears summarizing all parameters you have entered and want to have checked. If you want to make a change, select the relevant parameters and choose Revise. To start the prerequisites check, choose Next.

4.

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.

2009-05-04

PUBLIC

23/182

2 2.3

Planning Hardware and Software Requirements RECOMMENDATION

We recommend making sure that your system meets all checked prerequisites before starting the installation. However, you can still start the installation even if your system does not meet all prerequisites. In this case, make sure that you know what you are doing.

2.3.2 Requirements for a Central System
If you want to install a central system – that is, all instances reside on one host – the host must meet the following requirements:
NOTE

The information here is not intended to replace the documentation of the AIX operating system. For more information, see IBM Systems Information Center AIX PDFs System management Operating system and device management at: ■ AIX 5.2: http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base/
aix52.htm

■ AIX 5.3: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?
topic=/com.ibm.aix.doc/doc/base/aixinformation.htm

■ AIX 6.1: http://publib.boulder.ibm.com/infocenter/systems/index.jsp You can perform AIX-specific steps as follows: ■ Manually by entering AIX commands with the appropriate options ■ Using System Management Interface Tool (SMIT), a menu-driven system administration tool If you have problems with the function keys, you can also use ESC and the corresponding number to simulate the function key (for example, F4 is equivalent to ESC and 4 ).
Hardware Requirements Requirement Values and Activities

DVD Drive

CPU

■ ISO 9660 compatible ■ You can configure multiple DVD drives, but you cannot mount all of them. For more information, see Mounting a CD / DVD for AIX [page 135]. The recommended minimum hardware is two physical processor cores. To check this, do the following: ■ On AIX 5.2, enter the following command:
prtconf | grep Processors

Check that the output looks as follows:
Number Of Processors: 2

■ On AIX 5.3 or higher, enter the following command:
lparstat -i | grep "Entitled Capacity"

Check that the output looks as follows:
Entitled Capacity : 2.00

Hard Disk Space

■ Hard disk drives with sufficient space for the SAP system and the database: 60 GB

24/182

PUBLIC

2009-05-04

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

For more information about space requirements for the separate file systems and directories, see Setting Up File Systems [page 66]. ■ For specific disk space information, see SAP Note 1330707 .
NOTE

■ ■ ■

■ ■

● For safety reasons (system failure), the file systems must be physically distributed over several disks or RAID-technology must be used. ● To ensure 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 52]. 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk For more information, see Preparing the Installation DVDs [page 80]. 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 the database backup command of DB2 and the archived database log files. Alternatively, you need to make sure there is access to network-based storage management products, such as Legato Networker or Tivoli Storage Manager (TSM) (for database backup/restore). For data security reasons, distribution over three disks is required. We recommend you to distribute over five disks. To display available disks, enter the following command:
lspv

Disks marked none in the 3rd column are unused. ■ To display free space on a disk, enter the following command:
lspv -p <disk_name>

RAM

Areas marked free in the 2nd column are unused. ■ 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. 6 GB For more information about RAM required for usage type BI Java, see SAP Note 927530. To display RAM size in KB, enter the following command:
lsattr -El sys0 -a realmem

Swap Space

You need hard disk drives with sufficient space for swap. You can calculate the required swap space as follows: ■ Optimistic strategy: In addition, you need at least 20 GB for the central instance and at least another 10 GB for the SCS instance and also for every dialog instance. ■ Defensive strategy: 3 * RAM, at least 20 GB In addition, for the database instance you need: ■ 0.75 * RAM, if RAM is greater than 8 GB ■ 1 * RAM, if RAM is less than 8 GB For more information about recommended paging space, see SAP Note 1121904. To display and – if required – modify the existing swap space, use the System Management Interface Tool (SMIT). For more information, see Setting up Swap Space for AIX [page 131]

2009-05-04

PUBLIC

25/182

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

Keyboard

■ You can set the keyboard by typing the following command on the directly connected console:
smitty chkbd

■ You can select your keyboard under Motif by setting a language environment (LANG), for which a National Language Support (NLS) component is installed. The settings take effect after reboot.
Software Requirements Requirement Values and Activities

Operating System Version

To check the operating system version, use the following command:
lslpp -l bos.rte

The output must include the following or a larger version number:
bos.rte 5.2.0.50

AIX Kernel Parameters

AIX Maintenance Level (ML) and Technology Level (TL)

Additional Software

■ To adjust AIX Virtual Memory Management settings, see SAP Note 973227. ■ To adjust the settings for asynchronous I/O (aio) if the database is installed using file systems, see SAP Note 1157425. ■ AIX 6.x The output of the command oslevel -s should be at least 6100-00-01. ■ AIX 5.3 The output of the command oslevel -s should be at least 5300-05-01 (TL 5 SP 1). ■ AIX 5.2 The output of the command oslevel -r should be at least 5200-04 (ML 4). Make sure that the following additional file sets are installed: ■ bos.adt Base Application Development ■ bos.perf — performance and diagnostics tools ■ perfagent.tools— performance monitoring tools ■ bos.perf.libperfstat — Performance Statistics Library For an overview of the installed file sets, enter the following command:
lslpp –L | more

Lightweight Directory Access Protocol (LDAP) C++ Runtime Environment

If you want to use LDAP, you require the following LDAP library:
libldap.a

Database Version

Check the C++ runtime level with the following commands: ■ AIX 6.x: ● #lslpp —L xlC.aix61.rte The output must be at least 9.0.0.1. ● #lslpp —L xlC.rte The output must be at least 9.0.0.1. AIX 5.x: ■ ● #lslpp —L xlC.aix50.rte The output must be at least 7.0.0.4. ● #lslpp —L xlC.rte The output must be at least 7.0.0.0. DB2 V9.1 or DB2 V9.5 for Linux, UNIX, and Windows (automatically installed by SAPinst).

26/182

PUBLIC

2009-05-04

2 2.3

Planning Hardware and Software Requirements Values and Activities CAUTION

Requirement

■ The installation with DB2 V9.1 and DB2 V9.5 is only supported with HPUX 11.23 and higher. ■ The installation of DB2 V9.5 is only supported on HP-UX Itanium ■ For the installation of your SAP system, only the English version of DB2 V9.1 or DB2 V9.5 is supported. ■ You must only use the DB2 software provided by the SAP installation DVDs. For more information, see SAP Note 101809. If application servers are installed decentralized, Network File System (NFS) must be installed. To test the network connection to the database server, enter the following command:
/etc/ping <db_server_name> 100 10

Networking

National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding saplocales are installed. Install the necessary local code set by adding an additional language environment as follows: 1. Start the System Management Interface Tool (SMIT) with the following command:
smitty mle_add_lang

2.

Select the following: ■ Cultural Conventions ■

to install:

ISO8859-1 German (Germany) [de_DE] Language Translation to install: ISO8859-1 German [de_DE]

3.

This step installs the required bos.loc and bos.iconv file sets. Additionally, check that all file sets are in a consistent state by entering the following command:
lppchk –v

Printer

■ To check whether a file can be printed, enter the following command:
lp -d<printer_name> <test_file>

■ To check the status of your spool and the printers, enter the following command:
lpstat -t

2.3.3 Requirements for a Distributed or a High Availability System
NOTE

The information here is not intended to replace the documentation of the AIX operating system. For more information, see IBM Systems Information Center AIX PDFs System management Operating system and device management at: ■ AIX 5.2: http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base/
aix52.htm

2009-05-04

PUBLIC

27/182

2 2.3

Planning Hardware and Software Requirements

■ AIX 5.3: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?
topic=/com.ibm.aix.doc/doc/base/aixinformation.htm

■ AIX 6.1: http://publib.boulder.ibm.com/infocenter/systems/index.jsp You can perform AIX-specific steps as follows: ■ Manually by entering AIX commands with the appropriate options ■ Using System Management Interface Tool (SMIT), a menu-driven system administration tool If you have problems with the function keys, you can also use ESC and the corresponding number to simulate the function key (for example, F4 is equivalent to ESC and 4 ). The following sections provide information about the hardware and software requirements in a distributed or high-availability system for these instances: ■ Central services instance [page 28] ■ Central instance [page 31] ■ Database Instance [page 34]
NOTE

If you install multiple SAP system instances on one host, you need to add up the requirements.

2.3.3.1 Requirements for a Central Services Instance
The central services instance host must meet the following requirements:
Hardware Requirements Requirement Values and Activities

DVD Drive

CPU

■ ISO 9660 compatible ■ You can configure multiple DVD drives, but you cannot mount all of them. For more information, see Mounting a CD / DVD for AIX [page 135]. The recommended minimum hardware is two physical processor cores. To check this, do the following: ■ On AIX 5.2, enter the following command:
prtconf | grep Processors

Check that the output looks as follows:
Number Of Processors: 2

■ On AIX 5.3 or higher, enter the following command:
lparstat -i | grep "Entitled Capacity"

Check that the output looks as follows:
Entitled Capacity : 2.00

Hard Disk Space

■ Hard disk drives with sufficient space for the central services instance: 4 GB For more information about space requirements for the separate file systems and directories, see Setting up File Systems [page 66]. ■ 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk For more information, see Preparing the Installation DVDs [page 80].

28/182

PUBLIC

2009-05-04

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

■ 1.2 GB of temporary disk space for the installation. ■ For data security reasons, distribution over three disks is required. We recommend you to distribute over five disks. ■ To display available disks, enter this command:
lspv

Disks marked none in the 3rd column are unused. ■ To display free space on a disk, enter this command:
lspv -p <disk_name>

RAM

Areas marked free in the 2nd column are unused. ■ 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. 4 GB To display RAM size in KB, enter the following command:
lsattr -El sys0 -a realmem

Swap Space

Keyboard

You need hard disk drives with sufficient space for swap. The required swap space can be calculated as follows: ■ Optimistic strategy: At least 20 GB for the first SAP instance to be installed on a server and at least 10 GB for each additional active SAP instance on the same server ■ Defensive strategy: 3 * RAM, at least 20 GB For more information about recommended paging space, see SAP Note 1121904. To display and – if required – modify the existing swap space, use the System Management Interface Tool (SMIT). For more information, see Setting up Swap Space for AIX [page 131] ■ You can set the keyboard by typing this command on the directly connected console:
smitty chkbd

■ You can select your keyboard under Motif by setting a language environment (LANG), for which a National Language Support (NLS) component is installed. The settings take effect after reboot.
Software Requirements Requirement Values and Activities

Operating System Version

To check the operating system version, enter the following command:
lslpp -l bos.rte

The output must include the following or a larger version number:
bos.rte 5.2.0.50

■ Adjust AIX Virtual Memory Management settings as described in SAP Note 973227. If the database is installed using file systems, adjust the settings for asynchronous ■ I/O (aio) as described in SAP Note 1157425. AIX Maintenance ■ AIX 6.x: The output of the command oslevel -s should be at least 6100-00-01. Level (ML) and ■ AIX 5.3: The output of the command oslevel -s should be at least 5300-05-01 Technology Level (TL) (TL 5 SP 1). AIX Kernel Parameters

2009-05-04

PUBLIC

29/182

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

Additional Software

■ AIX 5.2: The output of the command oslevel -r should be at least 5200-04 (ML 4). Make sure that the following additional file sets are installed: ■ bos.adt Base Application Development ■ bos.perf — performance and diagnostics tools ■ perfagent.tools— performance monitoring tools ■ bos.perf.libperfstat — Performance Statistics Library For an overview of the installed file sets, enter the following command:
lslpp –L | more

National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding saplocales are installed. Install the necessary local code set by adding an additional language environment as follows: 1. Start the System Management Interface Tool (SMIT) with the following command:
smitty mle_add_lang

2.

Select the following: ■ Cultural Conventions ■

to install:

ISO8859-1 German (Germany) [de_DE] Language Translation to install: ISO8859-1 German [de_DE]

3.

This step installs the required bos.loc and bos.iconv file sets. Additionally, check that all file sets are in a consistent state by entering the following command:
lppchk –v

Lightweight Directory If you want to use LDAP, you require the following LDAP library: Access Protocol libldap.a (LDAP) C++ runtime Check the C++ runtime level with the following commands: environment ■ AIX 6.x: ● #lslpp —L xlC.aix61.rte The output must be at least 9.0.0.1. ● #lslpp —L xlC.rte The output must be at least 9.0.0.1. AIX 5.x: ■ ● #lslpp —L xlC.aix50.rte The output must be at least 7.0.0.4. ● #lslpp —L xlC.rte The output must be at least 7.0.0.0. Networking If application servers are installed decentralized, Network File System (NFS) must be installed. Test the network connection to the database server with the following command:
/etc/ping <db_server_name> 100 10

Printer

■ To check whether a file can be printed, enter the following command:
lp -d<printer_name> <test_file>

■ Check the status of your spool and the printers with this command:
lpstat -t

30/182

PUBLIC

2009-05-04

2 2.3

Planning Hardware and Software Requirements

2.3.3.2 Requirements for the Central Instance
The central instance host must meet the following requirements:
Hardware Requirements Requirement Values and Activities

DVD Drive

CPU

■ ISO 9660 compatible ■ You can configure multiple DVD drives, but you cannot mount all of them. For more information, see Mounting a CD / DVD for AIX [page 135]. The recommended minimum hardware is two physical processor cores. To check this, do the following: ■ On AIX 5.2, enter the following command:
prtconf | grep Processors

Check that the output looks as follows:
Number Of Processors: 2

■ On AIX 5.3 or higher, enter the following command:
lparstat -i | grep "Entitled Capacity"

Check that the output looks as follows:
Entitled Capacity : 2.00

Hard Disk Space

■ Hard disk drives with sufficient space for the central instance: 4 GB For more information about space requirements for the separate file systems and directories, see Setting Up File Systems [page 66] SAP Directories . ■ 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk For more information, see Preparing the Installation DVDs [page 80]. ■ 1.2 GB of temporary disk space for the installation. ■ For data security reasons, distribution over three disks is required. We recommend you to distribute over five disks. ■ To display available disks, enter the following command:
lspv

Disks marked none in the 3rd column are unused. ■ To display free space on a disk, enter the following command:
lspv -p <disk_name>

RAM

Areas marked free in the 2nd column are unused. ■ 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. 4 GB For more information about RAM required for usage type BI Java, see SAP Note 927530. To display RAM size in KB, enter the following command:
lsattr -El sys0 -a realmem

Swap Space

You need hard disk drives with sufficient space for swap. You can calculate the required swap space as follows: ■ Optimistic strategy: At least 20 GB for the first SAP instance to be installed on a server and at least 10 GB for each additional active SAP instance on the same server ■ Defensive strategy:

2009-05-04

PUBLIC

31/182

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

Keyboard

3 * RAM, at least 20 GB For more information about recommended paging space, see SAP Note 1121904. To display and – if required – modify the existing swap space, use the System Management Interface Tool (SMIT). For more information, see Setting up Swap Space for AIX [page 131] ■ You can set the keyboard by typing the following command on the directly connected console:
smitty chkbd

■ You can select your keyboard under Motif by setting a language environment (LANG), for which a National Language Support (NLS) component is installed. The settings take effect after reboot.
Software Requirements Requirement Values and Activities
lslpp -l bos.rte

Operating System Version To check the operating system version, use the following command: The output must include the following or a larger version number:
bos.rte 5.2.0.50

AIX Kernel Parameters

AIX Maintenance Level (ML) and Technology Level (TL)

Additional Software

■ To adjust AIX Virtual Memory Management settings, see SAP Note 973227. ■ To adjust the settings for asynchronous I/O (aio) if the database is installed using file systems, see SAP Note 1157425. ■ AIX 6.x The output of the command oslevel -s should be at least 6100-00-01. ■ AIX 5.3 The output of the command oslevel -s should be at least 5300-05-01 (TL 5 SP 1). AIX 5.2 ■ The output of the command oslevel -r should be at least 5200-04 (ML 4). Make sure that the following additional file sets are installed: ■ bos.adt Base Application Development ■ bos.perf — performance and diagnostics tools ■ perfagent.tools— performance monitoring tools ■ bos.perf.libperfstat — Performance Statistics Library For an overview of the installed file sets, enter the following command:
lslpp –L | more

Lightweight Directory Access Protocol (LDAP) C++ Runtime Environment

If you want to use LDAP, you require the following LDAP library:
libldap.a

To check the C++ runtime level, enter the following commands: ■ AIX 6.x ● #lslpp —L xlC.aix61.rte The output must be at least 9.0.0.1. ● #lslpp —L xlC.rte The output must be at least 9.0.0.1. AIX 5.x ■ ● #lslpp —L xlC.aix50.rte The output must be at least 7.0.0.4.

32/182

PUBLIC

2009-05-04

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

DB2 Client Connectivity

The output must be at least 7.0.0.0. DB2 V9.1 CLI Driver / DB2 V9.1 JDBC Driver or DB2 V9.5 CLI Driver / DB2 V9.5 JDBC Driver (both are automatically installed by SAPinst)
CAUTION

#lslpp —L xlC.rte

You must only use the DB2 software provided by the SAP installation DVDs. For more information, see SAP Note 101809. If application servers are installed decentralized, Network File System (NFS) must be installed. To test the network connection to the database server, enter the following command:
/etc/ping <db_server_name> 100 10

Networking

National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding saplocales are installed. Install the necessary local code set by adding an additional language environment as follows: 1. Start the System Management Interface Tool (SMIT) with the following command:
smitty mle_add_lang

2.

Select the following: ■ Cultural Conventions ■

to install:

ISO8859-1 German (Germany) [de_DE] Language Translation to install: ISO8859-1 German [de_DE]

3.

This step installs the required bos.loc and bos.iconv file sets. Additionally, check that all file sets are in a consistent state by entering the following command:
lppchk –v

Printer

■ To check whether a file can be printed, enter the following command:
lp -d<printer_name> <test_file>

■ To check the status of your spool and the printers, enter the following command:
lpstat -t

DB2–Specific Software Requirements

■ For DB2–specific software requirements, see the IBM web page DB2 for Linux UNIX, and Windows — System Requirements at: http://www.ibm.com/software/data/db2/udb/sysreqs.html. ■ For more information about known issues for DB2 on AIX, see the following IBM web page:
http://www-1.ibm.com/support/docview.wss?uid=swg21165448

2009-05-04

PUBLIC

33/182

2 2.3

Planning Hardware and Software Requirements

2.3.3.3 Requirements for the Database Instance
The database host must meet the following requirements:
Hardware Requirements Requirement Value or Activity

DVD Drive

CPU

■ ISO 9660 compatible ■ You can configure multiple DVD drives, but you cannot mount all of them. For more information, see Mounting a CD / DVD for AIX [page 135]. All 64–bit processors that are capable of running the supported AIX operating system version. For more information, see the DB2–specific requirements for your database version at:
http://www.ibm.com/software/data/db2/udb/sysreqs.html

To display the number of CPUs in a system, enter the following command: ■ AIX 5.2:
prtconf | grep Processors

■ AIX 5.3 or higher:
lparstat -i | grep "Entitled Capacity"

Disk space

■ For more information about the required disk space for the database file systems, see SAP Note 1330707 .
NOTE

■ ■

■ ■

To ensure a good performance of your production system, create separate file systems for the directories listed in section Required File Systems for DB2 for Linux, UNIX, and Windows [page 52]. For safety reasons (system failure), the file systems must be distributed physically over several disks, or RAID-technology must be used. 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, access to network-based storage management products, such as Legato Networker or Tivoli Storage Manager (TSM) (for database backup or restore), is needed. At least 4.3 GB for each installation DVD that you have to copy to your local disk. For more information, see Preparing the Installation DVDs [page 80] To display available disks, enter the following command:
lspv

Disks marked none in the 3rd column are unused. ■ To display free space on a disk, enter the following command:
lspv -p <disk_name>

RAM

Areas marked free in the 2nd column are unused. Minimum 2 GB To display RAM size in KB, enter the following command:
lsattr -El sys0 -a realmem

34/182

PUBLIC

2009-05-04

2 2.3

Planning Hardware and Software Requirements Value or Activity

Requirement

Swap Space

To configure and set your swap space, proceed as follows: 1. Obtain the system RAM size by entering the following command:
lsattr -E -l sys0

2.

Obtain the size of the swap space by entering the following command:
lsps -a

3.

Set the swap space size to at least 1.5 to 2 times of either the amount of RAM of your system or use the MAXIMUM CACHE SIZE parameter that you provide in the CREATE INDEX command.
RECOMMENDATION

Keyboard

You can display and – if required – modify the existing swap space using the System Management Interface Tool (SMIT). For more information, see Setting up Swap Space for AIX [page 131] For more information about recommended paging space, see SAP Note 1121904. ■ You can set the keyboard by typing this command on the directly connected console:
smitty chkbd

■ You can select your keyboard under Motif by setting a language environment (LANG), for which a National Language Support (NLS) component is installed. The settings take effect after reboot.
Software Requirements Requirement Value or Activity

Database software

DB2 V9.1 or DB2 V9.5 for Linux, UNIX, and Windows (both are automatically installed by SAPinst)
CAUTION

■ For the installation of your SAP system, only the English version of DB2 V9.1 or DB2 V9.5 is supported. ■ You must only use the DB2 software provided by the SAP installation DVDs. For more information, see SAP Note 101809. ■ DB2 V9.5: AIX 5.3; AIX 6.1 ■ DB2 V9.1: AIX 5.2; AIX 5.3; AIX 6.1 For more information, see the IBM web page DB2 for Linux UNIX, and Windows — System Requirements at: http://www.ibm.com/software/data/db2/udb/sysreqs.html. To check the operating system version, enter the following command:
oslevel -s

Operating System Version

AIX settings (kernel parameter)

■ For more information about required AIX settings, see SAP Note 1048686

2009-05-04

PUBLIC

35/182

2 2.3

Planning Hardware and Software Requirements Value or Activity

Requirement

Additional software

■ Adjust AIX Virtual Memory Management settings as described in SAP Note 973227. ■ If the database is installed using file systems, adjust the settings for asynchronous I/O (aio) as described in SAP Note 1157425. Make sure that the following additional file sets are installed: ■ bos.adt Base Application Development ■ bos.perf – performance and diagnostics tools ■ perfagent.tools – performance monitoring tools ■ bos.perf.libperfstat – performance statistics library For an overview of the installed file sets, enter the following command:
lslpp –L | more

Lightweight Directory Access Protocol (LDAP) C++ runtime environment

If you want to use LDAP, you require the following LDAP library:
libldap.a

For the supported C++ runtime environment, see the DB2 system requirements at:
http://www.ibm.com/software/data/db2/udb/sysreqs.html

Networking

If application servers are installed decentralized, Network File System (NFS) must be installed. To test the network connection to the database server, enter the following command:
/etc/ping <db_server_name> 100 10

National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding saplocales are installed. Install the necessary local code set by adding an additional language environment as follows: 1. To start the System Management Interface Tool (SMIT), enter the following command:
smitty mle_add_lang

2.

Select the following: ■ Cultural Conventions ■

to install:

ISO8859-1 German (Germany) [de_DE] Language Translation to install: ISO8859-1 German [de_DE]

3.

This step installs the required bos.loc and bos.iconv file sets. Additionally, check that all file sets are in a consistent state by entering the following command:
lppchk –v

Printer

■ To check whether a file can be printed, enter the following command:
lp -d<printer_name> <test_file>

■ To check the status of your spool and the printers, enter the following command:
lpstat -t

36/182

PUBLIC

2009-05-04

2 2.3

Planning Hardware and Software Requirements

2.3.4 Requirements for a Dialog Instance
The dialog instance host must meet the following requirements:
NOTE

The information here is not intended to replace the documentation of the AIX operating system. You can perform AIX-specific steps as follows: ■ Manually by entering AIX commands with the appropriate options ■ Using System Management Interface Tool (SMIT), a menu-driven system administration tool If you have problems with the function keys, you can also use ESC and the corresponding number to simulate the function key (for example, F4 is equivalent to ESC and 4 ).
Hardware Requirements Requirement Values and Activities

DVD Drive

CPU

■ ISO 9660 compatible ■ You can configure multiple DVD drives, but you cannot mount all of them. For more information, see Mounting a CD / DVD for AIX [page 135]. The recommended minimum hardware is two physical processor cores. To check this, do the following: ■ On AIX 5.2, enter the following command:
prtconf | grep Processors

Check that the output looks as follows:
Number Of Processors: 2

■ On AIX 5.3 or higher, enter the following command:
lparstat -i | grep "Entitled Capacity"

Check that the output looks as follows:
Entitled Capacity : 2.00

Hard Disk Space

■ Hard disk drives with sufficient space for the dialog instance. 3 GB For more information about space requirements for the separate file systems and directories, see Setting Up File Systems [page 66]. ■ 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk For more information, see Preparing the Installation DVDs [page 80]. ■ 1.2 GB of temporary disk space for the installation. ■ For data security reasons, distribution over three disks is required. We recommend you to distribute over five disks. ■ To display available disks, enter the following command:
lspv

Disks marked none in the 3rd column are unused. ■ To display free space on a disk, enter the following command:
lspv -p <disk_name>

RAM

Areas marked free in the 2nd column are unused. ■ 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. 4 GB

2009-05-04

PUBLIC

37/182

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

For more information about RAM required for usage type BI Java, see SAP Note 927530. To display RAM size in KB, enter the following command:
lsattr -El sys0 -a realmem

Swap Space

Keyboard

You need hard disk drives with sufficient space for swap. You can calculate the required swap space as follows: ■ Optimistic strategy: At least 20 GB for the first SAP instance to be installed on a server and at least 10 GB for each additional active SAP instance on the same server ■ Defensive strategy: 3 * RAM, at least 20 GB For more information about recommended paging space, see SAP Note 1121904. To display and – if required – modify the existing swap space, use the System Management Interface Tool (SMIT). For more information, see Setting up Swap Space for AIX [page 131] ■ You can set the keyboard by typing the following command on the directly connected console:
smitty chkbd

■ You can select your keyboard under Motif by setting a language environment (LANG), for which a National Language Support (NLS) component is installed. The settings take effect after reboot.
Software Requirements Requirement Values and Activities

Operating System Version

To check the operating system version, use the following command:
lslpp -l bos.rte

The output must include the following or a larger version number:
bos.rte 5.2.0.50

■ To adjust AIX Virtual Memory Management settings, see SAP Note 973227. ■ To adjust the settings for asynchronous I/O (aio) if the database is installed using file systems, see SAP Note 1157425. AIX Maintenance Level ■ AIX 6.x (ML) and Technology The output of the command oslevel -s should be at least 6100-00-01. Level (TL) ■ AIX 5.3 The output of the command oslevel -s should be at least 5300-05-01 (TL 5 SP 1). AIX 5.2 ■ The output of the command oslevel -r should be at least 5200-04 (ML 4). Additional Software Make sure that the following additional file sets are installed: ■ bos.adt Base Application Development ■ bos.perf — performance and diagnostics tools ■ perfagent.tools— performance monitoring tools ■ bos.perf.libperfstat — Performance Statistics Library For an overview of the installed file sets, enter the following command: AIX Kernel Parameters
lslpp –L | more

38/182

PUBLIC

2009-05-04

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding saplocales are installed. Install the necessary local code set by adding an additional language environment as follows: 1. Start the System Management Interface Tool (SMIT) with the following command:
smitty mle_add_lang

2.

Select the following: ■ Cultural Conventions ■

to install:

ISO8859-1 German (Germany) [de_DE] Language Translation to install: ISO8859-1 German [de_DE]

3.

This step installs the required bos.loc and bos.iconv file sets. Additionally, check that all file sets are in a consistent state with the following command:
lppchk –v

Lightweight Directory If you want to use LDAP, you require the following LDAP library: Access Protocol (LDAP) libldap.a C++ runtime Check the C++ runtime level with the following commands: environment ■ AIX 6.x: ● #lslpp —L xlC.aix61.rte The output must be at least 9.0.0.1. ● #lslpp —L xlC.rte The output must be at least 9.0.0.1. AIX 5.x ■ ● #lslpp —L xlC.aix50.rte The output must be at least 7.0.0.4. ● #lslpp —L xlC.rte The output must be at least 7.0.0.0. SAP kernel Make sure that the SAP kernel of the central instance has at least the patch level of the SAP kernel on the SAP Kernel DVD that is used for the installation of the dialog instance. We recommend that you apply the most current SAP kernel from the SAP Service Marketplace at http://service.sap.com/swdc. Networking If application servers are installed decentralized, Network File System (NFS) must be installed. To test the network connection to the database server, enter the following command:
/etc/ping <db_server_name> 100 10

Printer

■ To check whether a file can be printed, enter the following command:
lp -d<printer_name> <test_file>

■ To check the status of your spool and the printers, enter the following command:
lpstat -t

DB2 Client Connectivity

DB2 V9.1 CLI Driver / DB2 V9.1 JDBC Driver or DB2 V9.5 CLI Driver / DB2 V9.5 JDBC Driver (both are automatically installed by SAPinst)

2009-05-04

PUBLIC

39/182

2 2.4

Planning SAP System Transport Host Values and Activities CAUTION

Requirement

You must only use the DB2 software provided by the SAP installation DVDs. For more information, see SAP Note 101809.

2.4 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: ■ 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. ■ Use a transport directory located on a host other than the default host: ● You can use an existing transport directory and host in your SAP system landscape. ● You can set up a new transport directory on a different host. In either case, you must prepare this host for use by the new SAP system. For more information, see Exporting and Mounting the Global Transport Directory [page 77].
More Information

■ Setting Up File Systems and Raw Devices [page 65] ■ See the SAP Library: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics Change and Transport System Change and Transport System – Overview (BC-CTS) Basics of the Change and Transport System Transport Management System – Concept

2.5 Planning User and Access Management
You have to plan how you want to configure user and access management for your SAP system to be installed. Before you add a newly installed SAP system to your system landscape, you must decide which kind of user management you want to use: ■ Use the database of AS Java.

40/182

PUBLIC

2009-05-04

2 2.6

Planning Basic SAP System Parameters

■ Use an external ABAP system as the data source for user data. ■ Use an LDAP directory as the data source for user data. You cannot configure the AS Java to access an LDAP directory and an AS ABAP as the data source simultaneously. The AS Java can also use its own database as the data source.
Procedure
Using the Database of AS Java

You install your SAP system as described in this installation guide. During the installation, you specify the Java database as data source for the User Management Engine (UME) (see table User Management Engine in Basic SAP System Parameters [page 41]): During the installation, the SAP system is automatically configured to use the Java database as data source for the UME. After the installation has finished, you can still change the user management configuration. For more information, see Configuring User Management [page 103].
Using an External SAP ABAP System as the Data Source for User Data.

1. 2.

3.

You prepare the external SAP ABAP system as described in Preparing an External ABAP System as Source for User Data. You install your SAP system as described in this installation guide. During the installation, you specify an external ABAP system as data source for the User Management Engine (UME) (see table User Management Engine in Basic SAP System Parameters [page 41]): After the installation has finished, you cannot change this configuration of the UME any more. For more information, see Configuring User Management [page 103].

Using an LDAP directory as the Data Source for User Data

1. 2.

You install your SAP system as described in this installation guide. Configure the user management of the newly installed SAP system to use and LDAP directory. For more information, see Configuring User Management [page 103].

More Information

For more information about configuring the user management of your SAP system to be installed, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management Identity Management for System Landscapes Integration of User Management in Your System Landscape

2.6 Basic SAP System Parameters
SAPinst prompts for input parameters during the Define Parameters phase of the installation.

2009-05-04

PUBLIC

41/182

2 2.6

Planning Basic SAP System Parameters

The tables below list the basic system parameters that you need to specify before installing your SAP system. For all other SAP system parameters, use the F1 help in the SAPinst screens. You can install your SAP system either in Typical or Custom mode: ■ 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: ● SAP system ID and database ID ● SAP system profile directory – only for systems with instances on separate hosts ● Master password ● JCE Unlimited Strength Jurisdiction Policy files archive ● System Landscape Directory (SLD) destination ● SAP Solution Manager Key If you want to change any of the default settings, you can do so on the Parameter Summary screen. ■ Custom If you choose Custom, you are prompted for all parameters. At the end, you can still change any of these parameters on the Parameter Summary screen.
RECOMMENDATION

If you want to configure the user management of your SAP system for an external ABAP system, as described in Preparing an External ABAP System as Source for User Data [page 128], we recommend that you select the Custom parameter mode. When you do this, you are prompted to select the appropriate option and to enter the required parameters If you do not choose the Custom parameter mode, you have to change the required parameters on the Parameter Summary screen.
NOTE

You cannot change from Custom to Typical mode or from Typical to Custom mode on the Parameter Summary screen. The tables below list the basic system parameters that you need to determine before installing your SAP system. For all other SAP system parameters, use the F1 help in the SAPinst dialogs.
Java Development Kit and JCE Unlimited Strength Jurisdiction Policy Files Archive Parameters Description

Java Development Kit (JDK)

JCE Unlimited Strength Jurisdiction Policy Files Archive

A valid JDK is required for the Java application server. For more information about JDK versions supported by SAP and about how to install them, see Installing the Java Development Kit [page 78]. You need to obtain the Java(TM) Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files for the JDK you are using beforehand so that SAPinst can install them.

42/182

PUBLIC

2009-05-04

2 2.6

Planning Basic SAP System Parameters Description

Parameters

For more information, see Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive [page 79].
SAP System ID and Database ID Parameters Description

SAP System ID <SAPSID>

The SAP System ID <SAPSID> identifies the whole SAP system.
CAUTION

Choose your SAP system ID carefully. You cannot change the SAP system ID after the installation. Make sure that your SAP system ID: ■ Is unique throughout your organization. Do not use an existing <SAPSID> when installing a new SAP system.
EXAMPLE

■ ■ ■ ■

If you have already installed an ABAP system and you want to install a new Java system on the same host, make sure that you enter a <SAPSID> that is different from the <SAPSID> of the existing ABAP system. Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP TOP UID USE USR VAR

Database ID <DBSID>

■ If you want to install a dialog instance, make sure that no gateway instance with the same SAP system ID (SAPSID) exists in your SAP system landscape. 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. ■ If you want to install a new database: Make sure that your database ID: ● Is unique throughout your organization ● Consists of exactly three alphanumeric characters ● Contains only uppercase letters ● Has a letter for the first character ● Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP TOP UID USE USR VAR

■ If you want to use an existing database system:

2009-05-04

PUBLIC

43/182

2 2.6

Planning Basic SAP System Parameters Description

Parameters

Enter exactly the database ID of the existing database to which you want to add the system. System ID <SMDSID> of SAP SAPinst sets the system ID of SAP Solution Manager Diagnostics Agent, Solution Manager Diagnostics <SMDSID>, to SMD by default. Agent If SMD is already used, SAPinst assigns another default system ID. You can overwrite the default system ID as required.
CAUTION

Choose the <SMDSID> carefully. Renaming is difficult and requires you to reinstall the Diagnostics Agent. Make sure that the <SMDSID>: ■ Either does not yet exist on the local installation host, or does already exist, but exclusively contains some Diagnostics Agent installation ■ Consists of exactly three alphanumeric characters ■ Contains only uppercase letters ■ Has a letter for the first character ■ Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP TOP UID USE USR VAR

SAP System Profile Directory Parameters
/<sapmnt>/<SAPSID>/profile or / usr/sap/<SAPSID>/SYS/profile

Description

The installation retrieves the parameters entered earlier from the SAP system profile directory. SAPinst prompts you to enter the location of the profile directory when the installation option that you execute is not the first one belonging to your SAP system installation. See also the description of the parameters SAP System ID and Database ID. /usr/sap/<SAPSID>/SYS/profile is the soft link referring to /<sapmnt>/ <SAPSID>/profile.
NOTE

If you install a dialog instance in an existing SAP system, SAPinst also prompts you for the profile directory of the existing SAP system.
SAP System Instances, Hosts, and Ports Parameters Description

Instance Number of the Technical identifier for internal processes. It consists of a two-digit number from 00 SAP system to 98. 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. To find out this number, look under the SAP directory /usr/sap/<SAPSID>/JC<nn> on the host of the central instance. The value <nn> is the number assigned to the central instance.

44/182

PUBLIC

2009-05-04

2 2.6

Planning Basic SAP System Parameters Description

Parameters

Instance Number for the Technical identifier for internal processes for the Diagnostics Agent, consisting of a Diagnostics Agent two-digit number from 00 to 98. The instance number is set automatically to the next free and valid instance number that has not yet been assigned to the SAP system. The same restrictions apply as in “Instance Number of the SAP system” (see above). Name of Instance Host Instance Host: Host name of the specific instance. To find out the host name, open a command prompt and enter hostname. The host name must not exceed 12 characters. For more information about the allowed host name length and characters, see SAP Note 611361. Virtual Host Name 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 may be useful when moving SAP servers or complete server landscapes to other new hardware within a short time frame without having to carry out a reinstallation or complicated reconfiguration. You need to specify the virtual host name before you start SAPinst. For more information, see Prerequisites in Running SAPinst [page 88]. You also need to specify the virtual host name before you start SAPinst if you want to install a high-availability (HA) system. For more information, see Performing a High-Availability Installation [page 87]. ■ For more information about the use of virtual TCP/IP host names, see SAP Note 962955. ■ For more information about the allowed host name length and characters, see SAP Note 611361. CAUTION Message Server Port The message server port number must be unique for the SAP system on all hosts. If there are several message port numbers on one host, all must be unique. Port number of the SAP Message Server: If you do not specify a value, the default port number is used. The SCS instance profile contains the configuration for the Java message server. The Java message server port uses the parameter rdisp/msserv_internal with default value 39<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.
Master Password Parameters Description

Master Password Common password for all users created during the installation: ■ Operating system users (for example <sapsid>adm)
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 and of your database. ■ Java users (for example Administrator)

2009-05-04

PUBLIC

45/182

2 2.6

Planning Basic SAP System Parameters Description

Parameters

■ Database users ■ 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 might apply (for example, the master password must not contain the name of a Java user created during the installation).
Operating System Users Parameters Description

Password of Operating System Users

SAPinst processes the passwords of operating system users as follows: ■ If the operating system users do not exist, SAPinst creates the following users: ● <sapsid>adm This user is the SAP system administrator user. ● <smdsid>adm This user is dedicated to the Diagnostics Agent installation with sufficient authorization to manage the agent. It is created on the central instance host and on every dialog instance host. SAPinst sets the master password for these users by default. You can overwrite and change the passwords either by using the parameter mode Custom or by changing them on the parameter summary screen. ■ If the operating system users already exist, SAPinst prompts you for the existing password, except if the password of these users is the same as the master password. ■ Make sure that the user ID and group ID of these operating system users are unique and the same on each relevant application server instance host. For more information, see Creating Operating System Users [page 63].

User Management Engine (UME) Parameter Description

UME Configuration

You are prompted for how to configure the UME during the input phase of the installation. You can choose between the following options: ■ Use Java database (default) ● If you choose this option, administrators can manage users and groups with the UME Web admin tool and SAP NetWeaver Administrator only. ● For LDAP, use this configuration for the installation and change the configuration to LDAP after the installation (see Configuring User Management to Use an LDAP Directory [page 103]). Use ABAP ■ ● If you choose this option, administrators can manage users with the transaction SU01 on the external ABAP system, and, depending on the

46/182

PUBLIC

2009-05-04

2 2.6

Planning Basic SAP System Parameters Description

Parameter

permissions of the communication user, also with the UME
tool and SAP NetWeaver Administrator.

Web admin

● Make sure that you have created the required users manually on the external ABAP system before you choose this option (see Preparing User Management for an External ABAP System [page 128]).
RECOMMENDATION

Select the Custom parameter mode. When you do this, you are prompted to select the appropriate option and to enter the required parameters. If you do not choose the Custom parameter mode, you have to change the required parameters on the Parameter Summary screen. For more information about supported UME data sources and change options, see SAP Note 718383. Using the Java Database: Java Administrator User and SAPinst sets the user name Administrator and the master password by default. Password This user has administrative permissions for user management. Java Guest User and Password SAPinst sets the user name Guest and the master password by default. This user is used for anonymous access. Using an External ABAP System – Parameters for the ABAP Connection: Application Server 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 central 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 central instance. Communication User and This is the name and password of the existing ABAP communication user. You Password must have created this user manually on the external ABAP system. SDM Password This user is used for the Software Deployment Manager (SDM). SAPinst sets the master password by default. Using an External ABAP System – Parameters for the Application Server Java Connection: Administrator User and This is the name and password of the administrator user that you must have Password created on the external ABAP system. This user has administrative permissions for user management. Administrator Role The role SAP_J2EE_ADMIN must exist on the external ABAP system. Guest User and Password This is the name and password of the guest user that you must have created on the external ABAP system. This user is used for anonymous access. Guest Role The role SAP_J2EE_GUEST must exist on the external ABAP system. Communication User and This is the name and password of the existing ABAP communication user. You Password must have created this user manually on the external ABAP system. SDM Password This user is used for the Software Deployment Manager (SDM). SAPinst sets the master password by default.

2009-05-04

PUBLIC

47/182

2 2.6

Planning Basic SAP System Parameters

Key Phrase for Secure Store Settings Parameters Description

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.
Parameters Description

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:
<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.
Solution Manager Key Parameters Description

SAP Solution Manager key

To install your SAP system, you need to generate an SAP Solution Manager key [page 78], which the installation requires to continue. For more information, see SAP Note 805390.

System Landscape Directory (SLD) Destination Parameters Description

SLD Destination

The System Landscape Directory (SLD) is designed for registering the systems (along with the installed software) of your whole system landscape. The usual case is to configure one SLD for your complete system landscape. You can choose between the following options: ■ Register in existing central SLD Select this option to register the SAP system you are installing in an existing SAP System Landscape Directory (SLD) by specifying the SLD connection parameters below. ■ Configure a local SLD Select Configure a local SLD if you want to use the local SLD on the J2EE engine of the SAP system that you are installing.

48/182

PUBLIC

2009-05-04

2 2.6

Planning Basic SAP System Parameters Description

Parameters

SLD HTTP Host SLD HTTP Port

For more information, see Initial Technical Configuration for the System Landscape Directory (SLD) [page 161]. 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

SLD Data Supplier User and password

If the instance number of your Java system is 01, the SLD HTTP Port is 50100. ■ If you want to install a local SLD, SAPinst creates this user during the installation. ■ If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation.
RECOMMENDATION

SLD ABAP API User and password

We recommend that you name this user SLDDSUSER ■ If you want to install a local SLD, SAPinst creates this user during the installation. ■ If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation.
RECOMMENDATION

We recommend that you name this user SLDAPIUSER RFC User, Password The ABAP RFC user of the SLD SLD Gateway Host The host on which the gateway instance of the SLD is running SLD Gateway Instance Number The instance number of the gateway instance of the SLD SAP System Client The client in which the ABAP RFC user exists
Prepare SAP System for NWDI Integration Parameters Description

Prepare SAP System for NWDI Integration

If you select check box Prepare SAP System for NWDI Integration on the NWDI Landscape screen, SAPinst copies all SCAs belonging to the software units that you installed to the global transport directory. For more information about the global transport directory, see SAP Directories [page 66]. The SAP NetWeaver Development Infrastructure (NWDI) has a set of services that provide central storage and distributed versioning of Java source code. It also has centralized build services and a predefined change management process that control the flow of software through the landscape. To integrate your SAP system into the development landscape, NWDI requires that all installed software components are available in the file system. For more information, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software

2009-05-04

PUBLIC

49/182

2 2.6

Planning Basic SAP System Parameters Description

Parameters

Logistics Working with the Development Infrastructure Administration of the Development Infrastructure Setting Up the Development Landscape: Landscape Configurator
Parameters Relevant for Adobe Document Services (ADS) Parameters Description

User for basic authentication

SAPinst sets the user name ADSUSER and the master password by default. If required, you can choose another password according to your requirements. User for processing forms between SAPinst sets the user name ADSAGENT and the master password by default. an ABAP and a Java environment If required, you can choose another password according to your requirements.
Parameters Relevant for Usage Type SAP NetWeaver Development Infrastructure (DI) Parameters Description

Administrator of the SAP NetWeaver Development Infrastructure (NWDI) and Password Developer in the SAP NetWeaver Development Infrastructure (NWDI) and Password Landscape Directory Service User in the SAP NetWeaver Development Infrastructure (NWDI) and Password
Parameters Relevant for the File System Parameters

SAPinst sets the user name NWDI_ADM and the master password by default. If required, you can choose another password according to your requirements. SAPinst sets the user name NWDI_DEV and the master password by default. If required, you can choose another password according to your requirements. SAPinst sets the user name NWDI_CMSADM and the master password by default. If required, you can choose another password according to your requirements.

Description
/home/<username> /<sapmnt> is the base directory for the SAP system.

File system for the home directory user SAP system mount directory

For /<sapmnt> you can use a directory of your choice. Do not add <SAPSID> as subdirectory because the system adds this directory automatically.
EXAMPLE

File systems of DB2 for Linux, UNIX, and Windows

If you enter /<sapmnt>, the system creates the directory /<sapmnt>/ <SAPSID>. ■ Database software ■ Database home ■ Database instance home ■ Database log files ■ Database diagnostic data ■ SAPDATA For more information, see Required File Systems for DB2 for Linux, UNIX, and Windows [page 52].

50/182

PUBLIC

2009-05-04

2 2.6

Planning Basic SAP System Parameters

Parameters Relevant for the Database Parameters Description
db2<dbsid> has the DB2 system administration authorities and

DB2 instance owner db2<dbsid>

Java database connect user (sap<sapsid>db) ID of the db<dbsid>adm group

belongs to group db<dbsid>adm, which has DB2 SYSADM authorities. By default, user db2<dbsid> is a member of group db<dbsid>adm. The user name corresponds to the database schema where J2EE tables are created.
NOTE

db<dbsid>adm group

In a multi partitioned 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

ID of the db<dbsid>ctl group

db<dbsid>ctl group

In a multi partitioned database environment, the group ID must be the same on all database partition servers. Members of this group have DB2 SYSCTRL authorities. By default, <sapsid>adm is a member of this group.
NOTE

ID of the db<dbsid>mnt group

db<dbsid>mnt group

Database Communication Port

In a multipartitioned database environment, the group ID must be the same on all database partition servers. Members of this group have DB2 SYSMNT 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

Add sapdata directories

SAPinst requests this value during the database instance installation. 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>. 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: ■ For DB2 V9.5, you set the database manager configuration parameter INSTANCE_MEMORY. Parameter INSTANCE_MEMORY

Database Memory or Instance Memory

2009-05-04

PUBLIC

51/182

2 2.7

Planning Setup of Database Layout Description

Parameters

includes the database- and application-specific memory segments that are used by DB2. ■ For DB2 V9.1, you have to specify the database memory by setting database manager configuration parameter DATABASE_MEMORY.
CAUTION

The database requires more memory than only the database-specific memory segments (which are specified by parameter DATABASE_MEMORY).

2.7 Setup of Database Layout
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: 1. Required File Systems for DB2 for Linux, UNIX, and Windows [page 52] 2. Users and Groups [page 54] 3. DB2 Tablespaces [page 55] 4. Data Safety and Performance Considerations for Production Systems [page 56]
NOTE

For more information about DB2 (for example, printable manuals or online information), see Online Information from IBM [page 177].

2.7.1 Required File Systems for DB2 for Linux, UNIX, and Windows
This section lists the file systems that are required by the DB2 database 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/instguidesnw70 Installation Installation – SAP NetWeaver Systems

52/182

PUBLIC

2009-05-04

2 2.7

Planning Setup of Database Layout

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
/db2/db2<dbsid>

Description

/db2/<DBSID>/log_dir

/db2/<DBSID>/db2dump

■ With DB2's automatic storage management:
/db2/<DBSID>/sapdata<n>

■ No automatic storage management:
/db2/<SAPSID>/sapdata<n>

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 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” for DB2 for Linux, UNIX, and Windows.
NOTE

■ 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 56]. ■ If you add additional sapdata directories during the dialog phase of SAPinst, the corresponding tablespace containers are equally distributed.

2009-05-04

PUBLIC

53/182

2 2.7

Planning Setup of Database Layout Description NOTE

File System/Logical Volume

On AIX, use large enabled file systems. For more information, see Setting Up File Systems and Raw Devices for AIX.

NOTE

For information about SAP files systems, see Setting Up File Systems [page 66].
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 63].
File System/Logical Volume
/db2/<DBSID> /db2/<DBSID>/log_dir /db2/<DBSID>/db2dump

Permissions
755 755 755 750

Owner
db2<dbsid> db2<dbsid> db2<dbsid> db2<dbsid>

Group
db<dbsid>adm db<dbsid>adm db<dbsid>adm db<dbsid>adm

■ With DB2's automatic storage management:
/db2/<DBSID>/sapdata<n>

■ No automatic storage management:
/db2/<SAPSID>/sapdata<n>

2.7.2 Users and Groups
SAPinst creates the following users and groups for the central, dialog, and database instance as shown in the following table:
User
db2<dbsid> <sapsid>adm

Home Directory
/db2/db2<dbsid> can be chosen

Group
db<dbsid>adm sapsys (primary group), db<dbsid>ctl (secondary) db<dbsid>mnt (primary group)

Default Java database connect user:
sap<sapsid>db

/home/sap<sapsid>db

You may change this user during the installation.

54/182

PUBLIC

2009-05-04

2 2.7

Planning Setup of Database Layout

2.7.3 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 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. ■ 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 for Production Systems [page 56]. ■ 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 149]. 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 from AutoStorage to other storage modes or the other way round, you have to perform a homogenous system copy. For more information, see the appropriate system copy guide that is available on SAP Service Marketplace at http://service.sap.com/instguidesNW <Your SAP NetWeaver Release> Installation Installation — SAP NetWeaver Systems .
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

2009-05-04

PUBLIC

55/182

2 2.7

Planning Setup of Database Layout

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

More Information

■ Creating Tablespaces Manually [page 149] ■ Data Safety and Performance Considerations for Production Systems [page 56]

2.7.4 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 obtain 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:

56/182

PUBLIC

2009-05-04

2 2.7

Planning Setup of Database Layout

■ 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 111]. ■ 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_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. ■ 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 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 (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: ● 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.

2009-05-04

PUBLIC

57/182

2 2.8

Planning High Availability: Planning the Switchover Cluster

■ 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 177].
Only valid for: HA (UNIX) |

2.8 High Availability: Planning the Switchover Cluster
You can reduce unplanned downtime for your high-availability (HA) SAP system by setting up a switchover cluster. This setup replicates 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 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. 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 dialog instances (that is, additional application servers). This complements the switchover solution and is an essential part of building HA into your SAP system.
RECOMMENDATION

We recommend switchover clusters to ensure HA for your SAP system. A switchover cluster consists of: ■ 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 ■ Switchover software to detect failure in a node and switch the affected software unit to the standby node, where it can continue operating

58/182

PUBLIC

2009-05-04

2 2.8

Planning High Availability: Planning the Switchover Cluster

■ 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: ■ Check the information and the installation guides available at http://sdn.sap.com/irj/sdn/ ha. ■ 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: DB2 High Availability with Tivoli System Automation at: http://service.sap.com/instguidesnw70 Installation Installation – SAP NetWeaver Systems ■ The standalone replicated enqueue server is a major contribution to an HA installation and is essential for a Java system. We strongly recommend you to use it for an ABAP system. For more information about how to install the standalone replicated enqueue server, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology Client/Server Technology The SAP Lock Concept Standalone Enqueue Server Installing the Standalone Enqueue Server
Features

The following figure shows the essential features of a switchover setup:

2009-05-04

PUBLIC

59/182

2 2.8

Planning High Availability: Planning the Switchover Cluster

Figure 7: NOTE

This figure and the figures in this section are only examples. Only the instances relevant to the switchover are shown – for example, the central 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 figure shows an example of a switchover cluster in more detail:

60/182

PUBLIC

2009-05-04

2 2.8

Planning High Availability: Planning the Switchover Cluster

Figure 8:

Constraints

This documentation concentrates on the switchover solution for the central services instance. For more information about how to protect the NFS File System 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 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.
End of: HA (UNIX) |

2009-05-04

PUBLIC

61/182

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

3 3.1

Preparation Preparation Checklist

3 Preparation

3.1 Preparation Checklist
You have to complete the following preparations, which are described in more detail in the linked sections: 1. You make sure that the required operating system users and groups [page 63] are created. 2. You set up file systems or – if required – raw devices [page 65] and make sure that the required disk space is available for the directories to be created during the installation. 3. If required, you set up virtual host names [page 76]. 4. If you want to install a high-availability system, you perform switchover preparations [page 76]. 5. If you want to share the transport directory trans from another system, export [page 77] this directory to your installation hosts. 6. You generate the SAP Solution Manager Key [page 78] for your SAP system. 7. You install the Java Development Kit [page 78]. 8. You download the JCE policy zip file [page 79]. 9. You make sure that the required installation media [page 80] are available on each host. 10. Dialog instance only: If you upgraded your SAP System from an earlier source release to a target release lower than SAP NetWeaver 7.0 SR3, then installed EHP 1 with the EHP Installer, and now want to install a dialog instance, you have to update instance profiles of the existing system [page 134]. 11. You can continue with Installation [page 83]. The following preparation activity is optional: ■ Preparing an External ABAP System as Source for User Data [page 128]

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

2009-05-04

PUBLIC

63/182

3 3.2

Preparation Creating Operating System Users and Groups

SAPinst checks the NIS users, groups, and services using NIS commands. However, SAPinst does not change NIS configurations.
Only valid for: HA (UNIX) |

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).
End of: HA (UNIX) |

If you want to use global accounts that are configured on a separate host, you can do this in one of the following ways: ■ You start SAPinst and choose Software Life-Cycle Options Additional Preparations Operating System Users and Groups . For more information, see Running SAPinst [page 88]. ■ You create operating system users and groups manually. If you need information about how to do this, see Creating AIX Groups and Users [page 132]
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.
CAUTION

■ 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. ■ 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. ■ 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. ■ If you are installing an SAP system where the instances are to run on several hosts (distributed or high-availability system), 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. Example: You are installing a dialog instance in an existing SAP system. You must make sure that the group ID of group sapinst created on the host of the dialog instance is different from the group ID of any other group (for example, of group sapsys) on the central instance host of the existing SAP system.

64/182

PUBLIC

2009-05-04

3 3.3

Preparation Setting Up File Systems and Raw Devices

Users and Groups User Primary Group

UNIX superuser root SAP system administrator<sapsid>adm Diagnostics Agent user <smdsid>adm Java connect user sap<sapsid>db
NOTE

No primary group assigned by SAPinst (group sapinst is assigned as secondary group) sapsys (db<dbsid>ctl as secondary group) sapsys (sapinst as secondary group)
db<dbsid>mnt

Only used on the database host.
db2<dbsid> db<dbsid>adm

NOTE

Only used on the database host.
CAUTION

If these operating system users already exist, make sure that they are assigned to group sapinst.
CAUTION

If you install a distributed system and 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.
Groups and Members Groups
sapsys sapinst db<dbsid>ctl db<dbsid>adm db<dbsid>mnt

Members
<sapsid>adm, <smdsid>adm root, <sapsid>adm, <smdsid>adm, db2<dbsid> <sapsid>adm db2<dbsid>

Java connect user sap<sapsid>db

3.3 Setting Up File Systems and Raw Devices
The following sections describe the directories that are required for the instances of an SAP system, how to set up file systems and – if required – raw devices on operating system level: ■ SAP Directories [page 66] ■ Directory Structure of the New DB2 Client Connectivity [page 71] ■ Setting Up File Systems for High-Availability [page 72] ■ Configuring Network File System for High Availability [page 74]
More Information

If you need information about how to set up file systems and raw devices, see Setting Up File Systems and Raw Devices for AIX [page 133].

2009-05-04

PUBLIC

65/182

3 3.3

Preparation Setting Up File Systems and Raw Devices

3.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. For more information, see also table Parameters Relevant for the File System in Basic SAP System Parameters [page 41].
Only valid for: HA (UNIX) |

NOTE

For more information about how to set up your file systems if you are performing an HA installation, see High Availability: Setting Up File Systems [page 72].
End of: HA (UNIX) |

CAUTION

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. The following entry in the start profile is responsible for this: Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF), where $(_PF) points to the instance profile. Do not delete DIR_CT_RUN from the instance profile. Otherwise, you cannot restart the system after patches have been applied. For more information, see Applying the Latest Kernel and Support Packages [page 109].
SAP Directories for a Java System (Unicode)

A Java standalone system is always a Unicode system.

66/182

PUBLIC

2009-05-04

3 3.3

Preparation Setting Up File Systems and Raw Devices

Figure 9:

The instance name (instance ID) of the central instance is JC<Instance_Number>, the instance name of a Java dialog instance is J<Instance_Number>, and the instance name of the Java central services instance is SCS01.
EXAMPLE

For example, the file system structure might look as follows: On a central instance with SAP system ID C11 and instance name JC00, the J2EE Engine is installed to /usr/sap/C11/JC00/j2ee, and the corresponding SDM is installed to /usr/sap/C11/JC00/ SDM. On a dialog instance with instance name J01, the J2EE Engine is installed to /usr/sap/C11/J01/ j2ee. No SDM is installed.
SAP Directories for the Diagnostics Agent

The installation creates the following SAP directories for the Diagnostics Agent.

2009-05-04

PUBLIC

67/182

3 3.3

Preparation Setting Up File Systems and Raw Devices

Figure 10:

SAP Directories for the Diagnostics Agent

SAPinst extracts the Diagnostics Agent to the directory /usr/sap/SMD/J<instance_number>/ SMDAgent.
EXAMPLE /usr/sap/SMD/J98/SMDAgent SAP Directories in Detail NOTE

The listed space requirements are initial SAP requirements. Depending on your operating system, you might also have to add space for administrative purposes. The following directories are global, that is, they are accessed by all hosts in the SAP system.
SAP Directories Directory
<sapmnt>/<SAPSID>

Description

Space Required

1.0 GB Software and data for one SAP system This directory is physically located on the SAP global host. In homogeneous systems, you need to mount it via NFS (Network File System) for all hosts belonging to the same SAP system. It contains the following subdirectories: ■ exe This directory contains executable kernel programs. If you install an SAP system with distributed instances, you have to share this directory for all hosts with the same operating system. For more information, see the Prerequisites in Running SAPinst [page 88]. ■ global This directory contains log files.

68/182

PUBLIC

2009-05-04

3 3.3

Preparation Setting Up File Systems and Raw Devices Description Space Required

Directory

If you install an SAP system with distributed instances, you have to share this directory for all hosts. For more information, see the Prerequisites in Running SAPinst [page 88]. This directory contains the start and operations profiles of all instances. If you install an SAP system with distributed instances, you have to share this directory for all hosts. For more information, see the Prerequisites in Running SAPinst [page 88]. 3.0 GB Instance-specific data, symbolic links to the data for one system This directory contains files for the operation of a local instance. There is a subdirectory <INSTANCE_NAME> for each instance installed on the local instance host. The directory SYS contains only soft links to appropriate directories in /<sapmnt>/<SAPSID>/ for storing data used by several instances.
NOTE

profile

/usr/sap/<SAPSID>

SAPinst creates the subfolder /usr/sap/<SAPSID>/ <INSTANCE_NAME>/SDM only for the central instance of ABAP +Java or Java systems. For more information about SDM, see Checking the Java Documentation [page 158]. There are subdirectories of /usr/sap/<SAPSID>/SYS with symbolic links to subdirectories of /<sapmnt>/<SAPSID>: ■ /usr/sap/<SAPSID>/SYS/profile is linked to /<sapmnt>/
<SAPSID>/profile

■ ■

/usr/sap/<SAPSID>/SYS/global is linked to /<sapmnt>/ <SAPSID>/global /usr/sap/<SAPSID>/SYS/exe/run is linked to /usr/sap/ <SAPSID>/SYS/exe/dbg, which is linked to /<sapmnt>/ <SAPSID>/exe

NOTE

SAP system ABAP (Non-Unicode) + Java only: /usr/ sap/<SAPSID>/SYS/exe/run is linked to <sapmnt>/
<SAPSID>/exe/uc

SAPinst sets up these directory structures during the installation. Executables located in/usr/sap/<SAPSID>/SYS/exe/run are replicated by sapcpe to the exe directory of instances of the type <INSTANCE_NAME> and SCS<No>.
NOTE

/usr/sap/trans

Make sure that sufficient space is available in directory /usr/ sap/<SAPSID>/<INSTANCE_NAME>, since this stores SAP traces for the instance. Changes in SAP system profiles can also affect the disk space. Global transport directory for all SAP systems 2.0 GB

2009-05-04

PUBLIC

69/182

3 3.3

Preparation Setting Up File Systems and Raw Devices Description Space Required

Directory

For more information about exporting and mounting the global transport directory, see Exporting and Mounting the Global Transport Directory [page 77] The global transport directory is used by the Change Management Service (CMS). The CMS helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP systems in your system landscape.

For more information about the directories required for the database instance, see Required Directories for DB2 for Linux, UNIX, and Windows [page 52].
SAP Directories for the Diagnostics Agent in Detail NOTE

The listed space requirements are initial SAP requirements. Depending on your operating system, you might also have to add space for administrative purposes.
SAP Directories for the Diagnostics Agent Directory
/usr/sap/<SMDSID>/ J<instance_number>

Description

Space Required

/usr/sap/<SMDSID>/SYS/profile /usr/sap/<SMDSID>/exe

Instance-specific data of the Diagnostics Agent 500 MB Contains the following subdirectories: ■ sapinst Contains log files of the installation ■ SMD Agent Contains the Diagnostics Agent software and properties files. ■ script Contains the following local scripts: ● smdstart.sh This script is used to start the local Diagnostics Agent. ● smdstop.sh This script is used to stop the local Diagnostics Agent. ● smdadmin.sh This script is used to manage the local Diagnostics Agent. work ■ This is the work directory of the Diagnostics Agent Contains the profiles of the Diagnostics Agent instance Contains the following global scripts: ■ smdstart.sh This script is used to start one or more Diagnostics Agents available in the system landscape. ■ smdstop.sh

70/182

PUBLIC

2009-05-04

3 3.3

Preparation Setting Up File Systems and Raw Devices Description Space Required

Directory

This script is used to stop one or more Diagnostics Agents available in the system landscape.
smdadmin.sh

This script is used to manage one or more Diagnostics Agents available in the system landscape.

More Information

For more information about sapcpe, see http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology Client/Server Technology Local Executables on SAP Instances Functions of the Automatic Synchronization Program sapcpe

3.3.2 Directory Structure of the New DB2 Client Connectivity
With DB2 V9.1, a new DB2 client connectivity was introduced with a new directory structure as shown in the following graphic:

Figure 11: 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.

2009-05-04

PUBLIC

71/182

3 3.3

Preparation Setting Up File Systems and Raw Devices

Thus, 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.
Updating the Global Directory During Fix Pack Installation

For information about how to update the DB2 CLI driver or the JDBC driver during the Fix Pack installation, see the respective SAP Note for your database version:
Database Version SAP Note

DB2 V9.5 DB2 V9.1
Only valid for: HA (UNIX) |

1138549 978554

3.3.3 Setting Up File Systems for a High-Availability System
When you prepare a high-availability (HA) installation, you need to set up your file systems as described here. For more information, consult your HA partner.
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 58].
Procedure

1.

Create the file systems or raw partitions for the central services (SCS) instance on shared disks. For more information, see Setting Up File Systems and Raw Devices [page 65].
NOTE

The directories /<sapmnt>/<SAPSID> and /usr/sap/trans have to be mounted from a Network File System (NFS), whereas /usr/sap/<SAPSID> is a directory of the AS instance that is always mounted on the instance (not with NFS). Therefore, if the central instance host is not the NFS server host, you might have to mount at least the first two file systems on different physical disks from the third file system.
CAUTION

2.

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. If the node that takes over the central instance also runs an AS instance during normal operation, we recommend that you use a different approach for the file system for the /usr/sap/<SAPSID> directory.

72/182

PUBLIC

2009-05-04

3 3.3

Preparation Setting Up File Systems and Raw Devices

The /usr/sap/<SAPSID> directory contains two subdirectories: ■ SYS contains links to the central directory /<sapmnt>/<SAPSID> ■ <INSTTYPE><NR> contains data for the local AS instance The name <INSTTYPE><NR> is defined by the type of services and the application server number, for example DVEBMSG00. Only the directory <INSTTYPE><NR> needs to be migrated with the AS instance during the switchover. Since the SYS subdirectory contains only links that do not require any space, it can be created locally on each cluster node. Therefore, instead of /usr/sap/<SAPSID>, create a file system for /usr/sap/<SAPSID>/<INSTTYPE><NR> with the usual <> substitutions. The file name for the central instance is usually DVEBMGS00. This avoids mount conflicts when switching over to a node on which an AS instance is already running. The DVEBMGS00 directory can join the tree /usr/sap/ <SAPSID> instead of mounting on top of it.
NOTE

3. 4.

This approach becomes increasingly important when you want to cluster central services while other instances run on the cluster hosts outside the control of the switchover software, so as to use the resources efficiently. You must use this approach for integrated installations of the AS with ABAP and Java stacks. You assign the local file systems to mount points. You assign the shared file systems to mount points in appropriate failover groups.
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.

2009-05-04

PUBLIC

73/182

3 3.3

Preparation Setting Up File Systems and Raw Devices

Figure 12:
End of: HA (UNIX) | Only valid for: HA (UNIX) |

3.3.4 Configuring Network File System for a High-Availability System
If required, you configure Network File System (NFS), which is a system-wide Single Point-of-Failure (SPOF), for a high-availability (HA) installation with switchover software. For more information, consult your HA partner. We regard NFS as an extension to the operating system. The switchover product protects NFS and makes it transparently available to the SAP system in switchover situations. You need to decide: ■ How to protect NFS ■ Which switchover cluster nodes NFS is to run on The NFS configuration might depend on your database system. The directories need to be available for the SAP system before and after a switchover.
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.

74/182

PUBLIC

2009-05-04

3 3.3

Preparation Setting Up File Systems and Raw Devices

Procedure

1.

Check the NFS directories, several of which need to be shared between all instances of a system. These directories are: ■ ■ ■
/<sapmnt>/<SAPSID>/profile

Contains the different profiles to simplify maintenance
/<sapmnt>/<SAPSID>/global

Contains log files of batch jobs and central SysLog
/usr/sap/trans

Contains data and log files for objects transported between different SAP Web AS systems (for example, development – integration). This transport directory ought to be accessible by at least one AS instance of each system, but preferably by all. ■
/<sapmnt>/<SAPSID>/exe

2.

Contains the kernel executables. The best solution is to store them locally on all AS instance hosts. Since you can protect NFS by a switchover product, it makes sense to install it on a cluster node. The requirements of your database system might dictate how NFS has to be set up. If required, you can configure the NFS server on the cluster node of the CI or the DB. In both cases the NFS clients use the virtual IP address to mount NFS. If the second node is used as an additional SAP instance during normal operation (for example, as a dialog instance), it also needs to mount the directories listed above from the primary node. When exporting the directories with their original names, you might encounter the problem of a “busy NFS mount” on the standby node. You can use the following workaround to solve this problem: 1. On the primary server, mount the disks containing the directories:
/export/usr/sap/trans /export/<sapmnt>/<SAPSID>

2.

The primary server creates soft links to the directories with the original SAP names:
/usr/sap/trans —> /export/usr/sap/trans /<sapmnt>/<SAPSID> —> /export/<sapmnt>/<SAPSID>

Alternatively the primary server can also mount the directories:
/export/usr/sap/trans —> /usr/sap/trans /export/<sapmnt>/SID —> /<sapmnt>/<SAPSID>

3.

The primary server exports:
/export/usr/sap/trans /export/<sapmnt>/<SAPSID>

4.

The standby NFS mounts: from virt.IP:/export/usr/sap/trans to /usr/sap/trans from virt.IP:/export/<sapmnt>/<SAPSID> to /<sapmnt>/<SAPSID>

2009-05-04

PUBLIC

75/182

3 3.4

Preparation Using Virtual Host Names

If the primary node goes down and a switchover occurs, the following happens: ■ These directories on the standby node become busy:
/usr/sap/trans /<sapmnt>/<SAPSID>

■ The standby node mounts disks to:
/export/usr/sap/trans /export/<sapmnt>/<SAPSID>

■ The standby node configures the virtual IP address virt.IP ■ The standby node exports:
/export/usr/sap/trans /export/<sapmnt>/<SAPSID>

■ These directories on the standby node are accessible again:
/usr/sap/trans /<sapmnt>/<SAPSID>
End of: HA (UNIX) |

3.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.
Only valid for: HA (UNIX);HA (z/OS) |

Virtual host names are also required for a high-availability installation. For more information, see Performing Switchover Preparations for High Availability [page 76].
End of: HA (UNIX);HA (z/OS) |

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.
Only valid for: HA (UNIX) |

3.5 Performing Switchover Preparations for High Availability
If you want to use a virtual host name, 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 88].

76/182

PUBLIC

2009-05-04

3 3.6

Preparation Exporting and Mounting the Global Transport Directory

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.
End of: HA (UNIX) |

3.6 Exporting and Mounting the Global Transport Directory
In your SAP system landscape, a global transport directory for all SAP systems is required. ■ If this 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. ■ If this global transport directory does not exist, proceed as follows: ● Create the transport directory (either on the central instance host or on a file server). ● Export it on the global transport directory host. ● 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 central or dialog instance host 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.

More Information

Mounting Directories via NFS for AIX [page 136]

2009-05-04

PUBLIC

77/182

3 3.7

Preparation Generating the SAP Solution Manager Key

3.7 Generating the SAP Solution Manager Key
You must generate the Solution Manager key because the installation tool prompts for it during the installation. Without this key, the installation process cannot continue. For more information about SAP Solution Manager and its role within your system landscape, see the Master Guide of your SAP application.
Procedure

1.

2.

If SAP Solution Manager is not yet available in your system landscape, proceed as follows: 1. Order SAP Solution Manager as described in SAP Note 628901. 2. Install SAP Solution Manager as described in the documentation Installation Guide – SAP Solution Manager <Current Release> on <OS>: <Database>, which is available at: http://service.sap.com/instguides SAP Components SAP Solution Manager <Current Release> Generate the SAP Solution Manager key as described in SAP Note 811923.

Result

The SAP Solution Manager system displays the key for which you are prompted during the installation of your SAP system.

3.8 Installing the Java Development Kit
You need to prepare the system for the Java EE Engine by installing the Java Development Kit (JDK). The Java Engine requires a Java Development Kit (Java™ 2 SDK, Standard Edition = JDK) on every host where the Java Engine is to be installed.
NOTE

If required, you can perform a remote installation using a standalone SAPinst GUI on a separate Windows or UNIX host. This lets you perform the installation on a remote host, controlling it with the SAPinst GUI from a local host. If you want to perform a remote installation, see Performing a Remote Installation with SAPinst [page 140]. In this case, you need at least a JRE on the local host to start the SAPinst GUI there.
Procedure

1.

Check the JDK versions that are released for SAP systems in the Product Availability Matrix (PAM): 1. Go to http://service.sap.com/pam. 2. Choose Start PAM with navigation by category. 3. On the right-hand panel, choose SAP NetWeaver SAP EHP1 FOR SAP NETWEAVER 7.0 . 4. Choose tabstrip JSE Platforms.

78/182

PUBLIC

2009-05-04

3 3.9

Preparation Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive NOTE

2.

For more information about how to download it, see the relevant SAP Note for your operating system, which is referenced near the beginning of SAP Note 723909. Make sure a valid JDK version is installed on every host on which you want to install an SAP instance with the J2EE Engine, as follows: ■ If the JDK is not already installed, you need to download and install it. ■ If the JDK is already installed Check the installed version of the JDK by entering the following command:
java -version NOTE

SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment. If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME.

3.9 Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive
As of SAP NetWeaver 7.0 strong encryption is mandatory for the Java EE Engine and for all usage types that are deployed on it. You need to obtain the Java(TM) Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files for the JDK you are using beforehand so that SAPinst can install them. The JCE Unlimited Strength Jurisdiction Policy Files archive (JCE policy zip file) is specific for each Java VM provider and is available as a free download from the corresponding vendor's site.
Prerequisites

■ You have installed the Java Development Kit (JDK) [page 78] for your platform. ■ Make sure there is not an older version of the JCE policy zip file for your platform on the installation host.
CAUTION

If there is an old JCE policy zip file, the Prerequisite Checker does not recognize this fact. For this reason, SAPinst throws a java.lang.SecurityException during the Create Secure Store step stating the jurisdiction policy files are not signed by trusted signers.
Procedure

1.

Download the JCE policy zip file for your platform at http://www6.software.ibm.com/dl/ jcesdk/jcesdk-p.
NOTE

2.

You must not unzip the archive. SAPinst installs the JCE policy files during the installation process.

2009-05-04

PUBLIC

79/182

3 3.10

Preparation Preparing the Installation DVDs

3.

Copy the JCE policy files to directory /usr/java14_64/jre/lib/security.

3.10 Preparing the Installation DVDs
This section describes how to prepare the installation DVDs, which are available as follows: ■ You obtain the installation DVDs as part of the installation package. ■ You can also download the installation DVDs from SAP Service Marketplace.
Procedure

1.

Identify the required DVDs for your installation as listed below. Keep them separate from the remaining DVDs as this helps you to avoid mixing up DVDs during the installation.
CAUTION

The media names listed below are abbreviated. You can find the full names of all media shipped with SAP NetWeaver 7.0 including Enhancement Package 1 in the document Media List – SAP NetWeaver 7.0 including Enhancement Package 1 at: http://service.sap.com/installNW70 Installation Installation – SAP NetWeaver Systems .
NOTE

The Software Component Archives (SCAs) for the installation of Java-based SAP NetWeaver usage types are on the SAP NetWeaver Java DVD.
Only valid for: BI Java |

NOTE

Do not use the Business Intelligence Content Add-On DVD for the installation of BI with SAPinst. You have to install the BI Content Add-On later. For more information, see Configuring BI Java Information Broadcasting [page 165].
End of: BI Java |

The following table shows the required DVDs for the installation of an SAP system based on the usage type AS Java:
NOTE

For a central system, where all mandatory instances reside on one host, you need the installation DVDs that are required for the central instance, central services instance, and database instance.
SAP Instance Installation Required DVDs

Central services instance, central instance, ■ Installation Master DVD dialog instance ■ Kernel DVD ■ SAP NetWeaver Java DVD Database instance ■ Installation Master DVD ■ Kernel DVD

80/182

PUBLIC

2009-05-04

3 3.10

Preparation Preparing the Installation DVDs SAP Instance Installation Required DVDs

■ SAP NetWeaver Java DVD ■ DB2 V9.1 or DB2 V9.5 RDBMS DVD
CAUTION

● For the installation of your SAP system, only the English version of DB2 V9.1 or DB2 V9.5 is supported. ● You must only use the DB2 software provided by the SAP installation DVDs.

2.

Make the required installation media available on each installation host. If you need information about how to mount DVDs on AIX, see Mounting a CD / DVD for AIX [page 135].
NOTE

Depending on your installation type, one or more instances can reside on the same host. You need to keep this in mind when you make the required installation media available on each installation host. For a central system, you need to make all required installation media available on the single installation host. Use one of the following methods to make DVDs available: ■ Before the installation, copy DVDs manually to local hard disks. ■ During the installation, use the SAPinst Media Browser dialog and copy the entire DVDs to the path you entered in the Copy Package To column.
CAUTION

■ Mount the DVDs locally. We do not recommend you to use Network File System (NFS), because reading from DVDs mounted with NFS might fail. ■ If you copy the DVDs to disk, make sure that the paths to the destination location of the copied DVDs do not contain any blanks. ■ If you perform a local installation and there is only one DVD drive available on your installation host, you must copy at least the Installation Master DVD to the local file system.
Downloading Installation DVDs from SAP Service Marketplace

You normally obtain the installation DVDs as part of the installation package from SAP. However, you can also download installation DVDs from: http://service.sap.com/swdc Download Installations and Upgrades Entry by Application Group <SAP solution> <SAP product> <SAP release> Installation and Upgrade <operating system> <database>
NOTE

If you download installation DVDs, note that DVDs might be split into several files. In this case, you have to reassemble the required files after the download.

2009-05-04

PUBLIC

81/182

3 3.10

Preparation Preparing the Installation DVDs CAUTION

To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you can find at http://service.sap.com/swdc. You need at least SAPCAR 700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR files. For more information, see SAP Note 212876. 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 DVD according to one or both of the following: ■ Material number All download objects that are part of an installation DVD have the same material number and an individual sequence number:
<material_number>_<sequence_number> EXAMPLE

51031387_1 51031387_2 ... ■ Title All objects that are part of an installation DVD have the same title, such as <solution><DVD_name><OS> or <database>RDBMS<OS> for RDBMS DVDs. Download the objects to the download directory. Extract the individual download objects using SAPCAR, starting with the lowest sequence number – for example 51031387_1, then 51031387_2, and so on. During the download SAPCAR sets up the structure of the installation DVD.
NOTE

3. 4.

SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always accept with Yes.

82/182

PUBLIC

2009-05-04

4 4.1

Installation Installation Checklist

4 Installation

4.1 Installation Checklist
This section includes the installation steps that you have to perform for the: ■ Central system ■ Distributed system ■ High-availability system ■ Dialog instance Detailed information about the steps is available in the appropriate section. For more information about the various installation options, see Installation Options Covered by This Guide [page 15].
Central System

1. 2.

You install the SAP system with SAPinst [page 88]. You continue with Post-Installation [page 99].

Distributed System

1.

2.

3.

4.

If you want to share the transport directory trans from another system, you have to mount [page 77] it from this system. Otherwise, we recommend that you share the trans directory that is created during the installation of the central instance (/usr/sap/trans). On the SAP global host, proceed as follows: 1. You run SAPinst [page 88] to install the central services instance (SCS). 2. You export the global directories [page 87] to the database instance host, to the central instance host, and – if required – to the hosts where you want to install one or more dialog instances. On the database instance host, proceed as follows: 1. You mount the exported global directories [page 87] from the SAP global host (<sapmnt>/<SAPSID>/ exe, <sapmnt>/<SAPSID>/profile, <sapmnt>/<SAPSID>/global) and SAP transport host (/ usr/sap/trans). 2. You run SAPinst [page 88] to install the database instance. On the central instance host, proceed as follows:
NOTE

You can use the SAP transport host or the SAP global host as your central instance host. 1. You mount the exported global directories [page 87] from the SAP global host (<sapmnt>/<SAPSID>/ exe, <sapmnt>/<SAPSID>/profile, <sapmnt>/<SAPSID>/global) and SAP transport host (/ usr/sap/trans).

2009-05-04

PUBLIC

83/182

4 4.1

Installation Installation Checklist

5.

6.

2. You run SAPinst [page 88] to install the central instance. If required, you install one or more dialog instances on the respective hosts as described later in this section. 1. You mount the exported global directories [page 87] from the SAP global host (<sapmnt>/<SAPSID>/ exe, <sapmnt>/<SAPSID>/profile, <sapmnt>/<SAPSID>/global) and SAP transport host (/ usr/sap/trans). 2. You run SAPinst [page 88] to install the dialog instance. You continue with Post-Installation [page 99].

Graphical Overview

The following figure shows how you install the various instances in a distributed system:

Figure 13:

Distribution of Instances in a Java System

Only valid for: HA (UNIX) |

High-Availability System

This section describes how you install a high-availability (HA) system consisting of two nodes (host A and host B). For more information, consult your HA partner. This procedure describes the steps that are required for a hardware cluster consisting of two nodes (host A and host B): 1. You need to make sure that your system meets the hardware and software requirements [page 27]. 2. If you want to share the transport directory trans from another system, you have to mount [page 77] it from this system. Otherwise, we recommend that you share the trans directory that is created during the installation of the central instance (see below).

84/182

PUBLIC

2009-05-04

4 4.1

Installation Installation Checklist

3.

4.

You set up the switchover cluster infrastructure as follows: 1. You run SAPinst [page 88] to install the central services instance (SCS) using the virtual host name [page 76] on the primary cluster node, host A. 2. You export global directories [page 87] in <sapmnt>/<SAPSID> to the database host and to the central instance host. 3. You prepare the standby cluster node, host B, and make sure that it has all the necessary file systems [page 72], mount points, and (if required) Network File System (NFS). 4. You set up the user environment on the standby node, host B as follows: 1. You make sure that you use the same user and group IDs as on the primary node. 2. 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 63]. 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 ERS. 2. You install the ERS as described in: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology Client/Server Technology The SAP Lock Concept Standalone Enqueue Server Installing the Standalone Enqueue Server On the database instance host, proceed as follows:
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. You prepare the database instance host and make sure that it has all the necessary file systems [page 72], mount points, and (if required) Network File System (NFS). 2. You run SAPinst [page 88] to install the database instance. On the central instance host, proceed as follows:
NOTE

5.

In a high-availability installation, the central 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. You prepare the central instance host and make sure that it has all the necessary file systems [page 72], mount points, and (if required) Network File System (NFS).

2009-05-04

PUBLIC

85/182

4 4.1

Installation Installation Checklist

2. 3. 6.

7.

You run SAPinst [page 88] to install the central instance. If you want to use the shared transport directory trans from another system, you also mount [page 77] this directory (see above). We recommend that you install dialog instances with SAPinst to create redundancy. The application server instances are not a SPOF. Therefore, you do not need to include these instances in the cluster. 1. You mount the global directories [page 87] in <sapmnt>/<SAPSID>. 2. You run SAPinst [page 88] to install the dialog instance. 3. If you want to use the shared transport directory trans from another system, you also mount [page 77] this directory (see above). You continue with Post-Installation [page 99].

Graphical Overview

The following figure provides an overview of how you install the various instances in a high-availability installation:

Figure 14:

Distribution of Instances in a High-Availability Java System

End of: HA (UNIX) |

Dialog Instance

You perform the following steps on each host where you install the dialog instances. 1. You make sure that the global directories of the SAP system for which you want to install the dialog instance are mounted [page 87] on the host on which you want to install the dialog instance.

86/182

PUBLIC

2009-05-04

4 4.2

Installation Exporting and Mounting Global Directories: Distributed and High-Availability Systems

2. 3.

You run SAPinst [page 88] to install the dialog instance. You continue with Post-Installation [page 99].

4.2 Exporting and Mounting Global Directories: Distributed and High-Availability Systems
If you install a central instance, a database instance, or a dialog instance on a host other than the SAP Global host, you must mount directories from the SAP Global Host. The SAP Global Host is in most cases the host on which the central services instance (SCS) runs.
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 1100 MB free space. ■ If you are installing a heterogeneous SAP system (that is, the instances are installed on different operating-system platforms), do not mount the exe directory. For more information, see Heterogeneous SAP System Installations [page 166].
Procedure

1.

Log on to the SAP Global host as user root and export the following directories with root access to the host on which you want to install the new instance:
<sapmnt>/<SAPSID>/exe <sapmnt>/<SAPSID>/profile <sapmnt>/<SAPSID>/global

2. 3.

For more information, see Mounting Directories via NFS for AIX [page 136]. Log on to the host of the new instance 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 these mount points are permanent. Otherwise automatic start of the instance services does not work when you reboot the system.
Only valid for: HA (UNIX) |

4.3 Performing a High-Availability Installation
This section describes how to perform a high-availability (HA) installation. For more information, consult your HA partner.

2009-05-04

PUBLIC

87/182

4 4.4

Installation Running SAPinst

Prerequisites

■ You have completed all preparations, including switchover preparations for high availability [page 76]. ■ For each installation option, specify the appropriate virtual host name with the SAPinst property SAPINST_USE_HOSTNAME, as described in Running SAPinst [page 88].
Procedure

1. 2.

3.

4. 5. 6.

Run SAPinst [page 88] to install the central services instance (SCS) using the virtual host name on the primary cluster node, host A. Prepare the standby node, host B. You need to make sure that it meets the hardware and software requirements and it has all the necessary file systems, mount points, and (if required) Network File System (NFS), as described in Performing Switchover Preparations for High Availability [page 76] Set up the user environment on the standby node, host B. For more information, see Creating Operating System Users [page 63]. Make sure that you use the same user and group IDs as on the primary node. Create the home directories of users and copy all files from the home directory of the primary node. Configure the switchover software and test that switchover functions correctly. Install the database instance on the primary node, host A. Install the central instance with SAPinst [page 88] on the primary node, host A.
NOTE

7.

In a high-availability installation, the central 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. If required, install additional dialog instances with SAPinst [page 88] to replicate the SAP system services that are not a SPOF. These nodes do not need to be part of the cluster.
NOTE

Make sure that you complete the post-installation activities for high availability.
End of: HA (UNIX) |

4.4 Running SAPinst
This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a GUI client and a GUI server, which both use Java. This section describes an installation where SAPinst, GUI client, and GUI server are running on the same host. If you need to see the installation on a remote display, we recommend you perform a remote installation with SAPinst [page 140], 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 like vncviewer or nxserver/nxclient – offered by various vendors or open source – for remote access to

88/182

PUBLIC

2009-05-04

4 4.4

Installation Running SAPinst

the GUI on Windows workstations. We recommend you use the Hummingbird Exceed X Server, which we use to validate installations with SAPinst. For more information, see SAP Note 1170809.
Useful Information About SAPinst

■ When you start SAPinst, it automatically starts the GUI server and the GUI client. ■ SAPinst creates the installation directory sapinst_instdir directly below the temporary directory. SAPinst finds the temporary directory by checking the value of the following environment variables in the following sequence: TEMP, TMP, and TMPDIR. If no value is set for these variables, SAPinst creates the installation directory sapinst_instdir directly below the /tmp directory by default. If you want SAPinst to create the installation directory sapinst_instdir in another directory, set the environment variable TEMP to this directory before you start SAPinst.
Shell Used Command
TEMP=<directory> export TEMP

Bourne shell (sh) C shell (csh) Korn shell (ksh)
CAUTION

setenv TEMP <directory> export TEMP=<directory>

Make sure that the installation directory is not mounted with NFS, or there might be problems when the Java Virtual Machine is started.
RECOMMENDATION

We recommend that you keep all installation directories until the system is completely and correctly installed. ■ SAPinst creates a subdirectory for each installation option called sapinst_instdir/ <installation_option_directory>. ■ SAPinst extracts itself to a temporary directory called sapinst_exe.xxxxxx.xxxx, which is located in the environment variables TEMP, TMP, or TMPDIR. These files are deleted after SAPinst has stopped running. The temporary directory sapinst_exe.xxxxxx.xxxx sometimes remains undeleted. You can safely delete it. The temporary directory also contains the log file dev_selfex.out from the extraction process, which might be useful if an error occurs.
CAUTION

If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058. ■ During the installation, the default ports 21200, 21212, and 4239 are used for communication between SAPinst, GUI server, GUI, and HTTP server, as follows: ● SAPinst uses port 21200 to communicate with the GUI server. ● The GUI server uses port 21212 to communicate with the GUI client.

2009-05-04

PUBLIC

89/182

4 4.4

Installation Running SAPinst

● 4239 is the port of the HTTP server, which is part of the GUI server. If the ports for SAPinst and the GUI server are already in use, SAPinst automatically searches for free port numbers. If the search fails, 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: ● SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server> ● GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_gui> ● GUISERVER_HTTP_PORT=<free_port_number_http_server> ■ To see a list of all available SAPinst properties, start SAPinst as described above with the option p: ./sapinst -p. ■ 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
Prerequisites

Ctrl

+

C

.

■ Make sure that you have carefully planned your database layout, in particular the tablespace layout, as described in Setup of Database Layout [page 52]. ■ If you are installing a second or subsequent SAP system into an existing database, 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 122]. ■ 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/instguidesnw70 Installation Installation – SAP NetWeaver Systems ■ Make sure that you have defined the most important SAP system parameters as described in Basic SAP System Parameters [page 41] before you start the installation. ■ 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 23]. ■ If you want to perform a distributed or a high-availability installation, make sure that you have exported and mounted global directories [page 87]. ■ Check the value of the environment variable TEMP, TMP, or TMPDIR: ● 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 variable TEMP, TMP, or TMPDIR points – for example, by using a crontab entry. ● Make sure that you have at least 60 MB of free space in the installation directory for each installation option. In addition, you need 200 MB free space for the SAPinst executables. If you cannot provide 200 MB free space in the temporary directory, you can set one of the

90/182

PUBLIC

2009-05-04

4 4.4

Installation Running SAPinst

environment variables TEMP, TMP, or TMPDIR to another directory with 200 MB free space for the SAPinst executables. ● Make sure that the temporary directory has the permissions 777. ■ Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime Environment (JRE). ■ If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE for AIX 64-bit. ■ 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 GUI.
Shell Used Command
DISPLAY=<host_name>:0.0 export DISPLAY

Bourne shell (sh) C shell (csh) Korn shell (ksh)

setenv DISPLAY <host_name>:0.0 export DISPLAY=<host_name>:0.0

■ Check the following values for user root: ● In csh, execute limit
Output
cputime filesize datasize stacksize coredumpsize descriptors memorysize

Properties
unlimited unlimited unlimited 8192 KB unlimited 8192 unlimited

● In sh or ksh, execute ulimit
Output
time(seconds) file(blocks) data(kbytes) stack(kbytes) coredump(blocks) nofiles(descriptors) memory(KBytes)

-a Properties
unlimited unlimited 2097148 8192 unlimited 8192 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: ◆ In csh, execute:
limit descriptors 8192

2009-05-04

PUBLIC

91/182

4 4.4

Installation Running SAPinst

◆ In sh or ksh execute:
ulimit -n 8192

■ If you want to install a dialog instance to an existing SAP system, make sure that: ● 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. ● 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.
CAUTION

Do not use the user <sapsid>adm.
CAUTION

2.

3.

Make sure that the root user has not set any environment variables for a different SAP system or database. Mount the Installation Master DVD Mount the DVDs locally. We do not recommend that you use Network File System (NFS), because reading from DVDs mounted with NFS might fail. For more information about mounting DVDs, see Mounting a CD / DVD for AIX [page 135]. Start SAPinst from the Installation Master DVD by entering the following commands:
cd <Installation Master_DVD>/IM_<OS> ./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

■ Make sure that the installation directory is not mounted with NFS, or there might be problems when the Java Virtual Machine is started. ■ Make sure that your current working directory is not an IM_<OS> directory belonging to another operating system. For example, the following commands are incorrect and cause an error:
$ cd /sapcd2/IM_HPUX_IA64 $ /sapcd2/IM_HPUX_PARISC/sapinst

The following commands are correct:

92/182

PUBLIC

2009-05-04

4 4.4

Installation Running SAPinst $ cd /sapcd2/IM_HPUX_PARISC $ /sapcd2/IM_HPUX_PARISC/sapinst

4.

In the Welcome screen, choose one of the following installation options:
NOTE

When you start the installation from a 32-bit installation master DVD, all you see is the folder Software Life-Cycle Options on the Welcome screen. <Your SAP product> SAP Application Server Java <Database> <System Variant> For more information about available installation options, see SAPinst Installation Options [page 95]. ■ Software Life-Cycle Options For more information about available installation options, see SAPinst Installation Options [page 95]. Follow the instructions in the SAPinst input screens and enter the required parameters.
NOTE

5.

6.

For more information about the input parameters, position the cursor on the parameter and press F1 . Make sure that you check the following parameters depending on the installation type that you have chosen: ■ If you are performing a typical installation, SAPinst creates by default four sapdata directories. If you require more or fewer 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 Summary screen and choosing Revise, SAPinst returns to the IBM DB2 for Linux, UNIX, and Windows –> Sapdata Directories screen. On this screen, you can also decide if you want SAPinst to create the regular table and index tablespaces with DB2's automatic storage management enabled. By default, the option for automatic storage management is preselected. For more information about DB2's automatic storage management, see DB2 Tablespaces [page 55]. ■ If you are performing a custom installation, you set these parameters during the Define Parameters 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 IBM DB2 for Linux and UNIX and Windows Sapdata Directories screen. 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.

2009-05-04

PUBLIC

93/182

4 4.4

Installation Running SAPinst 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 that 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 149]. After you have entered all requested input parameters, SAPinst displays the Summary screen. This screen shows both the parameters that you entered and those that SAPinst set by default. If required, change the displayed parameters as follows: 1. Select the parameters you want to change. 2. Choose Revise. SAPinst displays input screens for the selected parameters. 3. Enter the new values for the parameters. To start the installation, choose Start. SAPinst starts the installation and displays the progress of the installation. When the installation has successfully completed, SAPinst displays the Finished successfully screen. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after SAPinst has finished. Sometimes these remain in the temporary directory.
NOTE

7.

8.

9.

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. Save the copy to a physically separate medium, such as a DVD or a USB drive that is 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. 10. We recommend that you delete the directory <user_home>/.sdtgui/. 11. 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. 12. If you copied installation DVDs to your hard disk, you can delete these files when the installation has successfully completed.

94/182

PUBLIC

2009-05-04

4 4.5

Installation SAPinst Installation Options

More Information

■ ■ ■ ■ ■ ■

Using SAPinst GUI [page 138] Interrupted Installation with SAPinst [page 139] Performing a Remote Installation with SAPinst [page 140] Starting SAPinst GUI Separately [page 142]. Entries in the Services File Created by SAPinst [page 144] Troubleshooting with SAPinst [page 167]

4.5 SAPinst Installation Options
This section provides information about the following in SAPinst: ■ Installation Options ■ Software Life-Cycle Options
NOTE

■ Choose the required installation options from the tree structure exactly in the order they appear for each system variant. ■ If you want to use global accounts, which are configured on separate hosts, you must run the installation option Operating System Users and Groups before you start the installation of the SAP system (see table Software Life-Cycle Options below). ■ If required, install a dialog instance for a central system (all instances on one host) or distributed system by choosing <SAP System> Software Life-Cycle Options Application Server <Database> Dialog Instance .
Installation Options

You choose SAP Systems with <your database> to install an SAP system with usage types or software units. You can install the following system variants: ■ Central System
Installation Options for a Central System Installation Option Remarks

Central System

Installs a complete SAP system including the following instances on one host: ● Central services instance (SCS) ● Database instance ● Central instance You can install a central system in the following parameter modes: ● Typical Mode If you choose Typical, the installation is performed with default settings. As a result, you have to respond to only a small selection of prompts. If you want to change any of the default settings, you can do so on the Parameter Summary screen. ● Custom Mode

2009-05-04

PUBLIC

95/182

4 4.5

Installation SAPinst Installation Options Installation Option Remarks

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

If you change a parameter with the Revise button on the Parameter Summary screen, the installer takes you to the screen where you can change the parameter. Depending on the changes, the installer might guide you through other screens containing default parameters that it has already processed. This might also happen if you press Back instead of Next on the screen
NOTE

You require at least usage type AS Java or AS ABAP. You can choose the usage types on the SAP System > Software Units screen.

■ Distributed System
Installation Options for a Distributed System Installation Option Remarks

Central Services Instance (SCS)

Database Instance

Central Instance

Mandatory step in installing a distributed SAP system with usage types or software units based on AS Java. Installs a central services instance (SCS) and prepares the SAP global host. Mandatory step in installing a distributed SAP system. Installs a database instance. You must have finished the Central Services Instance (SCS) installation, before you can choose this installation service. Mandatory step in installing a distributed SAP system on several hosts. Installs a central instance with usage types or software units.
NOTE

You require at least usage type AS Java or AS ABAP. You can choose the usage types or software units on the SAP System > Software Units screen. You must have finished the database instance installation.

Only valid for: HA (MSCS);HA (UNIX);HA (z/OS) |

High-Availability System
Installation Options for a High Availability System Installation Option Remarks

Central Services Instance Installs a central services instance (SCS) (SCS) Database Instance Installs a database instance Central Instance Installs a central instance with usage types or software units
NOTE

Dialog Instance

You require at least usage type AS Java. You can choose the usage types or software units on the SAP System > Software Units screen. Installs a dialog instance

96/182

PUBLIC

2009-05-04

4 4.5

Installation SAPinst Installation Options Installation Option Remarks NOTE

You might need to install dialog instances on 32-bit operating systems if you want to use 32-bit SAP NetWeaver components, such as Adobe document services. However, first check whether such 32-bit components can run on 64-bit operating systems. If so, we recommend running these 32-bit components on a 64-bit operating system. If not, you can install an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP instances, you must use 64-bit systems.
End of: HA (MSCS);HA (UNIX);HA (z/OS) |

Software Life-Cycle Options

You use the options located in this folder to perform the following tasks or to install the following components:
Software Life-Cycle Options Installation Option Remarks

Additional Preparation Options

These preparation tasks comprise: ■ Operating System Users and Groups Allows you to use global accounts that are configured on a separate host.
CAUTION

Application Server

Perform this SAPinst option before you start the installation of your SAP system. ■ Prerequisites Check Checks your hardware and software requirements before you start the installation. Otherwise, SAPinst automatically checks the hardware and software requirements during the installation with the Prerequisite Checker. If any changes are necessary to the SAP system or operating system settings, SAPinst automatically prompts you. For more information, see Running the Prerequisites Checker in Standalone Mode [page 23]. Choose Application Server <Database> Dialog Instance to install one or more dialog instances in an already installed SAP system, if required.
NOTE

Database Tools LDAP Registration

You might need to install dialog instances on 32-bit operating systems if you want to use 32-bit SAP NetWeaver components, such as Adobe document services. However, first check whether such 32-bit components can run on 64-bit operating systems. If so, we recommend running these 32-bit components on a 64-bit operating system. If not, you can install an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP instances, you must use 64-bit systems. Choose the options available in this folder to add additional partitions. LDAP Support Sets up LDAP support for an application server instance. Choose this option once per SAP system and after you have:

2009-05-04

PUBLIC

97/182

4 4.5

Installation SAPinst Installation Options Remarks

Installation Option

1.

Configured the Active Directory on a Windows host by choosing LDAP Registration Active Directory Configuration You have to configure the directory server only once. Afterwards all SAP systems that should register in this directory server can use this setup.
NOTE

System Copy

Uninstall

The option Active Directory Configuration is only available for Windows. 2. Installed an application server instance For more information about LDAP and Active Directory, see Integration of LDAP Directory Services [page 124]. Choose this service to perform a system copy. For more information, see the system copy guide, which is available at: http://service.sap.com/instguidesnw70 Installation Installation – SAP NetWeaver Systems Choose this service to uninstall your SAP system, standalone engines, or optional standalone units. For more information, see Deleting an SAP System [page 169].

98/182

PUBLIC

2009-05-04

5 5.1

Post-Installation Post-Installation Checklist

5 Post-Installation

5.1 Post-Installation Checklist
NOTE

In a central system, all mandatory instances are installed on one host. Therefore, if you are installing a central system, you can ignore references to other hosts. You have to complete the following post-installation steps, which are described in more detail in the linked sections: 1. If required, you perform a full installation backup [page 117] immediately after the installation has finished. 2. You check whether you can log on to the application server [page 100].
NOTE

3.

In a distributed or high-availability system you check whether you can log on to every instance of the SAP system that you installed. If you have installed usage type EPC and / or usage type EP, you check whether you can log on to the portal [page 101].
NOTE

4. 5. 6. 7. 8.

In a distributed or high-availability system you check whether you can log on to the portal from every instance of the SAP system that you installed. If you have installed usage type DI, you check whether you can log on to the SAP NetWeaver Development Infrastructure [page 102]. You configure user management [page 103]. You ensure user security [page 103]. You install the SAP license [page 107].
Only valid for: HA (UNIX) |

If you installed a high-availability system, you set up the licenses for high availability [page 108].
End of: HA (UNIX) |

9. 10. 11. 12. 13.

You apply the latest kernel and Support Package stacks [page 109]. You configure the remote connection to SAP support [page 109]. You perform initial Java configuration [page 109]. You enable recoverability of the database [page 111]. If you want to use Adobe Document Services (ADS) in your newly installed SAP system or if you have installed this SAP system as a dedicated ADS server, you perform post-installation steps for Adobe Document Services [page 113].

2009-05-04

PUBLIC

99/182

5 5.2

Post-Installation Logging On to the Application Server

14. If you have installed usage type Business Intelligence Java (BI Java), you set the environment variable CPIC_MAX_CONV [page 113]. 15. To connect your SAP system to an existing central system landscape directory (SLD), you configure the connection to a central System Landscape Directory (SLD) [page 114]. 16. If you have installed usage type Development Infrastructure (DI), you check the component repository content (CR) data in the central System Landscape Directory [page 114]. 17. If you have installed usage type EP, you configure the Application Sharing Server [page 115]. 18. To perform basic configuration steps, you run the Configuration Wizard [page 115]. 19. If you need to implement the E2E Root Cause Analysis scenario, you have to perform post-installation steps for the Diagnostics Agent [page 117] on your central and dialog instances. 20. You perform a full backup of the installation [page 117].

5.2 Logging On to the Application Server
You need to check that you can log on to the SAP system with the appropriate administrator user, given in the table below. Depending on your SAP system installation, the administrator user can either reside in the database of your Java system or in an external ABAP system.
User User Name Storage: Database User Name Storage: External ABAP System

Administrator

The user name that you specified The user name that you specified during the installation. The when you created this user in the default name is Administrator. external ABAP system. The recommended name is
J2EE_ADM_<SAPSID_Java_System>

For more information, see Preparing User Management for an External ABAP System [page 128]. 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:
http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00

100/182

PUBLIC

2009-05-04

5 5.3

Post-Installation Logging On to the Portal 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 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 link of any of the provided applications, for example SAP NetWeaver Administrator or System Information.

5.3 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 EPC only and when you install it together with usage type EP:
User User Name Storage: Database User Name Storage: External ABAP System

Administrator

The user name that you specified The user name that you specified during the installation. The when you created this user in the default name is Administrator. external ABAP system. The recommended name is
J2EE_ADM_<SAPSID_Java_System>

For more information, see Preparing User Management for an External ABAP System [page 128]. 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_J2EE_Engine_Server>:5<Instance_Number>00/irj NOTE

You must always enter a two digit number for <Instance_Number>. For example, do not enter 1 but instead enter 01.

2009-05-04

PUBLIC

101/182

5 5.4

Post-Installation Logging On to the SAP NetWeaver Development Infrastructure (NWDI) 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

2.

Log on by entering the required user and password.

5.4 Logging On to the SAP NetWeaver Development Infrastructure (NWDI)
If you have installed usage type DI, you have to log on to the services of SAP NetWeaver Development Infrastructure (NWDI) to check whether the installation of the usage type DI was successful.
Procedure

1.

Start a Web browser and enter the following URL:
http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00/devinf NOTE

You must always enter a 2-digit number for <Instance_Number>. For example, do not enter 1 but instead enter 01.
EXAMPLE

If you installed SAP NetWeaver Application Server Java with DI on host saphost06 and the instance number of your SAP NetWeaver Application Server Java is 04, enter the following URL:
http://saphost06:50400

2.

3.

Log on with the NWDI_ADMIN user. The start page SAP NetWeaver Development Infrastructure appears in the Web browser. The following links appear: ■ Design Time Repository ■ Component Build Service ■ Change Management Service ■ System Landscape Directory Log on to these services one after another by clicking the appropriate link: 1. When you click Design Time Repository, the Design Time Repository page with the Repository Browser overview appears. 2. When you click Component Build Service, the Component Build Service page with the CBS Buildspace Information appears. 3. When you click Change Management Service, the Change Management Service page with the CBS Buildspace Information appears. 4. When you click System Landscape Directory, you should see the System Landscape Directory start page.

102/182

PUBLIC

2009-05-04

5 5.5

Post-Installation Configuring User Management NOTE

The tables displayed on the pages may be empty. They are filled when you configure the development infrastructure either by running the Configuration Wizard or by configuring your system manually.
More Information

■ For more information about running the Configuration Wizard, see Running the Configuration Wizard in Performing Initial Java Configuration [page 109]. ■ For more information about how to generate a project with configuration documentation in SAP Solution Manager, see Accessing Configuration Documentation in SAP Solution Manager [page 118].

5.5 Configuring User Management
During the installation of your SAP system, you specified the database of the AS Java as the initial data source of the User Management Engine (UME) (see table User Management Engine in Basic SAP System Parameters [page 41]). After the installation of your SAP system has finished, you can still change the data source of the UME to a directory service. During the installation of your SAP system, you specified one of the following initial data sources of the User Management Engine (UME) (see table User Management Engine in Basic SAP System Parameters [page 41]): ■ Database of the AS Java ■ External ABAP system After the installation of your SAP system has finished, you can still change the data source of the UME. The following data source changes are supported: ■ From the AS Java database to user management of an external ABAP system ■ From the AS Java database to a directory service For more information about changing the data source after installation and about related restrictions, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management User Management of the Application Server Java Configuring User Management UME Data Sources

5.6 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 these users: ■ Operating system users

2009-05-04

PUBLIC

103/182

5 5.6

Post-Installation Ensuring User Security

■ SAP system users ■ Users in the SAP NetWeaver Development Infrastructure (NWDI) During the installation, SAPinst by default assigned the master password to all users created during the installation unless you specified other passwords. If you change user passwords, be aware that SAP system users might exist in multiple SAP system clients (for example, if a user was copied as part of the client copy). Therefore, you need to change the passwords in all the relevant SAP system clients.
RECOMMENDATION

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. For more information, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Network and Transport Layer Security
CAUTION

Make sure that you perform this procedure before the newly installed SAP system goes into production. For security reasons, you also need to copy the installation directory to a separate, secure location – such as a DVD – and then delete the installation directory.
Procedure

For the users listed below, take the precautions described in the relevant SAP security guide, which you can find at http://service.sap.com/securityguide:
Operating System Users

After the installation, operating system users for SAP system and database are available as listed in the following table:
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: ■ If you chose 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 Visual Administrator only. If you want to use LDAP, you have to change the user configuration to LDAP. For more information, see Configuring User Management to Use an LDAP Directory [page 103].

104/182

PUBLIC

2009-05-04

5 5.6

Post-Installation Ensuring User Security

■ If you chose option Use ABAP, UME users are stored in an external ABAP system (ABAP UME) – see table Users Stored in an External ABAP System below. You can manage users with transaction SU01 in the external ABAP system and, depending on the permissions of the communication user, also with the UME Web admin tool and the Visual Administrator. For more information, see Preparing User Management for an External ABAP System [page 128]. The following tables show these users together with recommendations on how you can ensure the security of these users:
Users Stored in an External ABAP System User User Name Storage: External ABAP System Comment

Administrator

The name that you gave this user This user has administrative permissions for user when you created it manually in the management and its password is stored in secure external ABAP system storage. Therefore, whenever you change the administrator’s password, you must also change the password in secure storage with the J2EE Engine Config Tool.
RECOMMENDATION

We recommend that you use strong password and auditing policies for this user. Guest The name that you gave this user This user is used for anonymous access. when you created it manually in the Lock this user for interactive logon. external ABAP system SDM SDM This user is used to access the Software Deployment Manager (SDM) in the Java system. Communication The name that you gave this user This user is used for the communication between user for the J2EE when you created it manually in the the ABAP system and the Java system. Engine external ABAP system 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. Users for Adobe The name of this user is ADSUSER. This user exists in at least clients 000 and 001 of the Document Services This user resides in the external ABAP external ABAP system. (ADS) system. You must have created this user manually in the external ABAP system before you started the installation. ADS_AGENT This user exists in at least clients 000 and 001 of the This user resides in the external ABAP external ABAP system. system. You must have created this user manually in the external ABAP system before you started the installation. Data supplier user The name that you gave this user This user exists in at least clients 000 and 001 of the for System when you created it manually in the external ABAP system external ABAP system

2009-05-04

PUBLIC

105/182

5 5.6 User

Post-Installation Ensuring User Security User Name Storage: External ABAP System Comment

Landscape Directory (SLD) (optional) ABAP API user for The name that you gave this user This user exists in at least clients 000 and 001 of the System Landscape when you created it manually in the external ABAP system Directory (SLD) external ABAP system (optional)
Users Stored in the Java Database User User Name Storage: Database Comment

Administrator

The name that you gave this user This user has administrative permissions for during the installation or the user management and its password is stored in default name Administrator secure storage. Therefore, whenever you change the administrator’s password, you must also change the password in secure storage with the J2EE Engine Config Tool.
RECOMMENDATION

Guest

SDM Users for Adobe Document Services (ADS)

Data supplier user for System Landscape Directory (SLD) (optional)

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 SDM This user is used to access the Software Deployment Manager (SDM) in the Java system. ADSUSER This user’s password is stored in secure storage. Therefore, whenever you change the administrator’s password, you must also change the password in secure storage with the J2EE Engine Config Tool. ADS_AGENT This user’s password is stored in secure storage. Therefore, whenever you change the administrator’s password, you must also change the password in secure storage with the J2EE Engine Config Tool. NOTE The name that you gave this user during the installation SAPinst created this user automatically if The recommended name is you chose Configure local SLD during the SLDDSUSER. installation.

Users in the SAP NetWeaver Development Infrastructure (NWDI)

If you chose usage type (software unit) SAP NetWeaver Development Infrastructure (DI) during the installation, users in the SAP NetWeaver Development Infrastructure (NWDI) are available after the installation as listed in the following table:

106/182

PUBLIC

2009-05-04

5 5.7 User

Post-Installation Installing the SAP License User Name
NWDI_ADM

Comment

Administrator of the SAP NetWeaver Development Infrastructure (NWDI) and password

Administrator of the NWDI
CAUTION

Developer in the SAP NetWeaver Development Infrastructure (NWDI) and password Landscape Directory Service User in the SAP NetWeaver Development Infrastructure (NWDI) and password

NWDI_DEV

This user has extensive authorizations. Make sure that you assign a secure password. Developer in the NWDI

NWDI_CMSADM

Administrator of the NWDI Change Management System (CMS)
CAUTION

Do not log on with this user. It is used by the system for internal communication. More Information

■ For more information about managing Java users, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library Security Identity Management User Management of the Application Server Java ■ For more information about Java administration tools for user maintenance, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by KeyCapability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine Administration Tools

5.7 Installing the SAP License
You must install a permanent SAP license. When you install your SAP system, a temporary license is automatically installed. This temporary license allows you to use the system for only 4 weeks from the date of installation.
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 at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Cross-NetWeaver Configurations SAP License Keys

2009-05-04

PUBLIC

107/182

5 5.8

Post-Installation High Availability: Setting Up Licenses

Only valid for: HA (UNIX) |

If you have installed a high-availability system, proceed as described in High Availability: Setting Up Licenses [page 108].
End of: HA (UNIX) |

More Information

For more information about SAP license keys, see http://service.sap.com/licensekey.

5.8 High Availability: Setting Up Licenses
Every SAP system needs a central license, which is determined by the environment of the message server. Since SAP's high-availability (HA) solution stipulates 2 or more cluster nodes (host machines) where the message server is enabled to run, you have to order as many license keys [page 107] 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, 1 key for each machine. SAP has implemented a license mechanism for transparent and easy use with 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) runs. There is no license problem when only the database is switched over.
Prerequisites

The SAP system is up and running.
Procedure

1. 2.

3.

4. 5. 6.

Make sure that the SCS instance on the primary host, node A, is running. To find the hardware ID of the primary host, run the Visual Administrator on node A and choose CI Host License Adapter . The hardware ID is displayed in the Visual Administrator. 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

To import the files containing the two licenses, run the Visual Administrator on the node where the SCS instance is running and choose CI Host License Adapter . 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.

108/182

PUBLIC

2009-05-04

5 5.9

Post-Installation Applying the Latest Kernel and Support Package Stacks

Result

The license is no longer a problem during switchover. This means you do not need to call saplicense in your switchover scripts.

5.9 Applying the Latest Kernel and Support Package Stacks
We strongly recommend that you apply the latest kernel and Support Package stacks from SAP Service Marketplace before you start configuring your SAP system.
Prerequisites

Make sure that you read the release notes for your SAP system before you apply Support Package stacks. The release notes might include information about steps you have to perform after you have applied the Support Package stacks. For more information, see http://service.sap.com/releasenotes.
Procedure

Download and apply the latest kernel and Support Package stacks as described in the SAP NetWeaver 7.0 – Support Package Stack Guide <current version> at http://service.sap.com/maintenancenw70 .

5.10 Configuring Remote Connection to SAP Support
SAP offers its customers access to support and to a number of remote services such as the SAP EarlyWatch service or the SAP 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.

5.11 Performing Initial Java Configuration
When you have installed your SAP Java system, you have to perform the following initial configuration steps: ■ Create a second administrator user ■ Check and configure the necessary communication ports ■ Check the Java Virtual Machine (Java VM) settings ■ Make your newly installed SAP system known to your SAP Solution Manager For more information, see the appropriate sections below.
Procedure
Creating Another Administrator User

To prevent locking the administrator in case you change its password and forget to update the entry secure storage, we also recommend you create a second administrator user after installing a system based on AS Java.

2009-05-04

PUBLIC

109/182

5 5.11

Post-Installation Performing Initial Java Configuration

Create another administrator user and assign the appropriate group and role as described in the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver by Key Capability SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library Security Identity Management User Management of the Application Server Java Administration of Users and Roles Managing Users, Groups, and Roles
Checking and Configuring the Necessary Communication Ports

When you install a Java instance or create an additional server process, AS Java assigns default values to the communication ports. If some of these ports are being used by another program, you have to manually assign a different value to the relevant port. If necessary, you can change the assigned join port of a server process, on which the server process listens for connections (for example, when the port assigned to the cluster element is already in use by another program). ■ For more information about Java ports, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine Reference AS Java Ports ■ You can check and configure communication ports using the Visual Administrator or the Config Tool: ● For more information about how to start and handle the Visual Administrator, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine Administration Tools Visual Administrator ● For more information about how to start and handle the Config Tool, see the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine Administration Tools Config Tool
Checking the Java VM Memory Settings

You can find recommendations for Java VM Memory Settings in SAP Note 723909. You can check and modify Java VM memory settings using the Visual Administrator or the Config Tool: ■ For more information about how to start and handle the Visual Administrator, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine Administration Tools Visual Administrator

110/182

PUBLIC

2009-05-04

5 5.12

Post-Installation Enabling Recoverability of the Database

■ For more information about how to start and handle the Config Tool, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine Administration Tools Config Tool
Making your Newly Installed SAP System Known to your SAP Solution Manager

Make your newly installed SAP system known to your SAP Solution Manager as described in the SAP Library at: http://help.sap.com SAP Solution Manager SAP Solution Manager 7.0 <current SP> SAP Solution Manager Basic Settings Solution Manager System Landscape Create Systems Create Non-SAP (Java) Systems
More Information

For more information about the configuration and administration of the J2EE Engine and about SAP Java technology, see Accessing the SAP Java Documentation [page 158].

5.12 Enabling Recoverability of the Database
CAUTION

This section applies only 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 documentation Database Administration Guide — SAP on IBM DB2 for Linux, UNIX, and Windows at: http://service.sap.com/instguidesnw70 Operations Database-Specific Guides .
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: ■
LOGRETAIN

2009-05-04

PUBLIC

111/182

5 5.12

Post-Installation Enabling Recoverability of the Database

No log archiving takes place. Log files remain in the log directory. ■
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. ■ ■
TSM:<TSM_management_class>

Log files are archived to Tivoli Storage Management (TSM)
USEREXIT

For downward compatibility with the former user exit concept, you can specify value USEREXIT for parameter LOGARCHMETH1. ■
VENDOR:<path_to_vendor_lib>

Log files are archived to a library that is provided by your vendor storage management. 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 documentation Database Administration Guide — SAP on IBM DB2 for Linux, UNIX, and Windows at: http://service.sap.com/instguidesnw70 Operations Database-Specific Guides . 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 multipartitioned 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

■ For direct access to online information about DB2 that is provided by IBM, see Online Information from IBM [page 177]. ■ For access to more documentation for SAP systems on DB2 for Linux, UNIX, and Windows, Online Information from SAP [page 175].

112/182

PUBLIC

2009-05-04

5 5.13

Post-Installation Performing Post-Installation Steps for Adobe Document Services

5.13 Performing Post-Installation Steps for Adobe Document Services
Adobe document services (ADS) can run in different IT scenarios, infrastructures, and usage types in a new or in an upgraded installation. In some cases the installation process cannot perform all configuration settings that are necessary for the use of Adobe document services, for example, if ABAP and Java are not installed on the same server. Use this process to check whether all configuration steps are complete and to verify which steps you still need to perform manually.
Prerequisites

Adobe document services are installed on your system.
Procedure

■ Check the ADS configuration as described in the Adobe Document Services Configuration Guide at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Business Task Management Adobe Document Services (Configuration) Adobe Document Services Configuration Guide Configuring the Web Service Securing Access to the Web Service Configuration Check If the tests are not successful, you might have to make some adjustments to the initial technical configuration for ADS [page 160]. ■ If you have installed this SAP system as a dedicated application server for ADS, you need to perform the additional configuration steps described in SAP Note 925741. ■ If you want to configure ALV (ABAP List Viewer) list printing with ADS, you can run the Configuration Wizard [page 115]. ■ Perform manual configuration as described in the Adobe Document Services Configuration Guide at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Business Task Management Adobe Document Services (Configuration) Adobe Document Services Configuration Guide
More Information

A printable version of the document Configuration Guide for SAP Interactive Forms by Adobe is available at: http://sdn.sap.com/irj/sdn/adobe Installation & Configuration SAP Interactive Forms by Adobe – Configuration Guides Configuration Guide for SAP Interactive Forms by Adobe
Only valid for: BI Java;Process Integration (PI) |

5.14 Setting Environment Variable CPIC_MAX_CONV
If you have installed usage type Business Intelligence Java (BI Java), you have to set the CPIC_MAX_CONV variable, as described below.

2009-05-04

PUBLIC

113/182

5 5.15

Post-Installation Configuring the Connection to a Central System Landscape Directory

Procedure

1.

Set the system variable CPIC_MAX_CONV to:
env variable CPIC_MAX_CONV <maximum number of simultaneous RFCs to the SAP System> NOTE

2. 3.

We recommend that you set the value to at least 200. Restart the system. Increase the profile values gw/max_conn and gw/max_sys on the SAP Gateway to support more parallel connections. If you run into a memory bottleneck, also increase gw/max_overflow_size and gw/max_shm_req. See report RSMONGWY_CHANGE_PARAMETER, which is started from transaction SA38.

End of: BI Java;Process Integration (PI) |

5.15 Configuring the Connection to a Central System Landscape Directory
For each system in your landscape that reports data to a central System Landscape Directory (SLD), you have to configure a corresponding SLD data supplier.
Procedure

Configure the SLD data suppliers and the API for the SLD as described in the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management System Landscape Directory Configuring Systems to Connect to SLD
More Information

This documentation is also available in PDF form in the User Manual – SLD of SAP NetWeaver 7.0 at http:// www.sdn.sap.com/irj/sdn/nw-sld.
Only valid for: Development Infrastructure (DI);Process Integration (PI) |

5.16 Updating Component Repository Content in the System Landscape Directory
Only valid for: Development Infrastructure (DI) |

You have to update Component Repository Content in the System Landscape Directory (SLD) if the following conditions are true: ■ You have installed usage type Development Infrastructure (DI). ■ You have chosen option Register in existing central SLD for SLD destination during the Define Parameters phase of the installation.
End of: Development Infrastructure (DI) |

For more information about option Register in existing central SLD, see table Connectivity to System Landscape Directory (SLD) in Basic SAP System Parameters [page 41].

114/182

PUBLIC

2009-05-04

5 5.17

Post-Installation Configuring the Application Sharing Server

Procedure

Update the CR content in the central SLD as described in SAP Note 669669.
Result

You can now run the Configuration Wizard to perform wizard-based basic configuration steps. For more information, see Running the Configuration Wizard [page 115].
End of: Development Infrastructure (DI);Process Integration (PI) |

5.17 Configuring the Application Sharing Server
NOTE

These steps are valid if you installed usage type EP and if you are using the default server installed on the portal machine. If you do not intend to use Application Sharing Server, you can disable it as described in the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability Collaboration Administration Guide Real-Time Collaboration Configuring Real-Time Collaboration Configuring the Application Sharing Server (RTC) Enabling / Disabling the Application Sharing Server (RTC) The installation of Application Sharing Server as an optional standalone unit is described in the documentation Installation Guide – Application Sharing Server on <OS>: <Database>
Only valid for: Application Server (AS);BI Java;Development Infrastructure (DI);Mobile Infrastructure (MI);Process Integration (PI) |

5.18 Running the Configuration Wizard
This section provides information about how to run the Configuration Wizard for the SAP NetWeaver usage types.
CAUTION

You can run the Configuration Wizard only once and only directly after you installed and patched your SAP system. You cannot use the configuration wizard after: ■ Upgrade ■ Installation of additional usage types in an existing SAP system In these cases, you need to manually perform the corresponding configuration steps. This does not apply to connectivity configuration templates. You can run them several times and after all use cases.

2009-05-04

PUBLIC

115/182

5 5.18

Post-Installation Running the Configuration Wizard
Only valid for: BI Java |

This also applies to configuration tasks for BI Java. For more information about BI Java, see SAP Note 917950. We recommend that you check the configuration of BI Java using SAP Note 937697.
End of: BI Java |

For more information about how to access the configuration documentation, see Accessing Configuration Documentation in the SAP Solution Manager [page 118]. You can also find information about the automated configuration steps, connectivity configuration templates, and the Configuration Wizard itself in the Technology Consultant's Guide at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Developing, Configuring, and Adapting Applications Creating Java Applications Using Web Dynpro J2EE Engine Configuration Configuration Wizard
Prerequisites

■ You have applied the latest kernel and all ABAP and Java Support Packages to your system. For more information, see Applying the Latest Kernel and Support Packages [page 109]. ■ You can find the latest LMTOOLS patch at: http://service.sap.com/swdc Download Support Packages and Patches Search for Support Packages and Patches Do the following: 1. Search for LMTOOLS*P. 2. Download and save the sca file. 3. Apply the patch using the Software Deployment Manager (SDM).
Procedure

1. 2. 3. 4. 5. 6.

After SAPinst has finished, open the SAP NetWeaver Administrator by entering the URL http:// <host>:<httpport>/nwa in a browser. Log on as user j2ee_admin. In the SAP NetWeaver Administrator, choose Deploy and Change Configuration Wizard . Select the relevant task for your installed system from the list and choose Start. Follow the instructions. After the Configuration Wizard has finished, restart your SAP system.

More Information

■ For more information about the Configuration Wizard and the configuration documentation, see the configuration structure of your implementation project in SAP Solution Manager. ■ SAP Note 923359 Collective Note: Configuration Wizard – Template Installer
End of: Application Server (AS);BI Java;Development Infrastructure (DI);Mobile Infrastructure (MI);Process Integration (PI) |

116/182

PUBLIC

2009-05-04

5 5.19

Post-Installation Post-Installation Steps for the Diagnostics Agent

5.19 Post-Installation Steps for the Diagnostics Agent
To implement the E2E Root Cause Analysis scenario, you have to configure the Diagnostics Agent.
Prerequisites

You have installed an AS Java central instance or dialog instance.
Procedure

Plan the implementation of the SAP Solution Manager Diagnostics Agent as described in the Root Cause Analysis Installation and Upgrade Guide, which you can find at: http://service.sap.com/diagnostics End-to-End Root Cause Analysis Media Library

5.20 Performing a Full Installation Backup
You must perform a full offline backup at the end of the installation. This procedure also describes how to use the back-up data for a restore.
CAUTION

Make sure that you fully back up your database so that you can recover it later if necessary.
Prerequisites

■ You have logged on [page 100] as user <sapsid>adm and stopped the SAP system and database [page 153].
Procedure

The UNIX commands used in this procedure work on all hardware platforms. For more information about operating system-specific backup tools, see your operating system documentation.
Backing Up the Installation NOTE

The following only applies to a standard installation. 1. Back up the following file systems: ■ /usr/sap/<SAPSID> ■ /usr/sap/trans ■ <sapmnt>/<SAPSID> ■ Home directory of the user <sapsid>adm ■ Home directory of the user db2<dbsid>
CAUTION

When you back up the home directory of db2<dbsid>, make sure that you exclude all database containers, the database log files and other database metadata. Proceed as follows: 1. Log on as user root.

2009-05-04

PUBLIC

117/182

5 5.21

Post-Installation Accessing Configuration Documentation in SAP Solution Manager

2.

Manually create a compressed tar archive that contains all installed files: ■ Saving to tape:
tar —cf — <file_system> | compress —c > <tape_device>

■ Saving to the file system:
tar —cf — <file_system> | compress —c > ARCHIVENAME.tar.Z

2.

3.

Back up the operating system using operating system means. This saves the structure of the system and all configuration files, such as file system size, logical volume manager configuration and database configuration data. Perform your offline database backup. For more information about backups, see the DB2 documentation.

Restoring Your Backup

If required, you can restore the data that you previously backed up.
CAUTION

Check for modifications to 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. Execute the following commands to restore the data: ■ Restoring the data from tape:
cat <tape_device> | compress —cd | tar —xf —

■ Restoring the data from the file system:
cat ARCHIVENAME.tar.Z | compress —cd | tar —xf —

4.

Restore your offline database backup. For more information about how to restore backups, see the DB2 documentation [page 177].

5.21 Accessing Configuration Documentation in SAP Solution Manager
To access configuration documentation in SAP Solution Manager, you have to connect your newly installed SAP system to SAP Solution Manager.
NOTE

For SAP NetWeaver 7.0 usage types you can also find configuration documentation in the Technology Consultant's Guide at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide

118/182

PUBLIC

2009-05-04

5 5.21

Post-Installation Accessing Configuration Documentation in SAP Solution Manager

Prerequisites

■ You have installed an SAP Solution Manager system as described in the documentation Installation Guide – SAP Solution Manager <Current Release> on <OS>: <Database>. ■ You have connected your SAP system to SAP Solution Manager as described in the documentation Configuration Guide – SAP Solution Manager <Current Release> as of <Current SP Level>. You can find this documentation at: http://service.sap.com/instguides SAP Components SAP Solution Manager <Current Release>
Procedure

1. 2.

3. 4.

Log on to your SAP Solution Manager system. To be able to access configuration documentation, create a project as follows: 1. Create your project with transaction SOLAR_PROJECT_ADMIN for project administration. 2. Connect your SAP system to SAP Solution Manager with transaction SMSY for the SAP Solution Manager system landscape. 3. Create a project structure and add the required scenarios for your SAP system to your project structure with the Business Blueprint transaction SOLAR01, 4. Add your SAP system configuration structures to your project structure with the configuration transaction SOLAR02. Go to the project structure folder <project name> using transaction SOLAR02. Access configuration documentation for SAP NetWeaver usage types at Configuration Structure SAP NetWeaver 7.0 .

Result

You can now configure your SAP system according to the configuration documentation in SAP Solution Manager.
More Information

http://service.sap.com/solutionmanager

Media Library Technical Papers How to Create a

Configuration Guide using SAP Solution Manager ■ http://help.sap.com SAP Solutions SAP Solution Manager Documentation for SAP Solution Manager <current release> SAP Solution Manager Implementing and Upgrading SAP Solutions Projects Configuration

2009-05-04

PUBLIC

119/182

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

6

Additional Information

6 Additional Information

The following sections provide additional information about optional preparation, installation, and post-installation tasks. There is also a section describing how to delete an SAP system.
Preparation

■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Installation of Multiple Components in One Database [page 122] MCOD Tablespaces and File Systems [page 123] Integration of LDAP Directory Services [page 124] Preparing User Management with an External ABAP system [page 128] Setting up Swap Space for AIX [page 131] Creating AIX Groups and Users [page 132] Setting Up File Systems and Raw Devices for AIX [page 133] Dialog Instance Installation for an Upgraded System: Updating Instance Profiles [page 134] Mounting a CD / DVD for AIX [page 135] Exporting and Mounting Directories via NFS for AIX [page 136]

Installation

■ Additional Information about SAPinst [page 138] ■ Installation of Additional Software Units or Usage Types in an Existing SAP System [page 144] ■ Creating Tablespaces Manually [page 149]
Post-Installation

■ Starting and stopping the SAP system [page 150] ■ If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page 157] ■ Accessing the SAP Java documentation [page 158] ■ Usage Type-Specific Initial Technical Configuration [page 159] ■ Heterogeneous SAP System Installation [page 166] ■ Troubleshooting [page 166]
Deleting an SAP System or SAP Instance

■ Deleting an SAP System [page 169] ■ Deleting a Diagnostics Agent [page 171]

2009-05-04

PUBLIC

121/182

6 6.1

Additional Information Installation of Multiple Components in One Database

6.1 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).
EXAMPLE

You install an SAP NetWeaver central system and an SAP CRM central system in a single database. MCOD is available with all SAP components. We are releasing this technology on all the major databases for the SAP system, in line with our commitment to deliver platform-independent solutions. Using this technology is as easy as installing a separate component. 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
Prerequisites

■ For more information about MCOD and its availability on different platforms, see http:// www.sdn.sap.com/irj/sdn/dbos. ■ We have released MCOD for Unicode installations. A prerequisite is that the MCOD system contains Unicode instances only. SAP does not support mixed solutions. ■ Improved sizing required In general, you 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.

122/182

PUBLIC

2009-05-04

6 6.2

Additional Information MCOD Tablespaces and File Systems NOTE

Special MCOD considerations and differences from the standard procedure are listed where relevant in the installation documentation.
Constraints
RECOMMENDATION

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. ■ In the event of database failure, all SAP systems running on the single database are affected. ■ Automated support in an MCOD landscape for the following administrative tasks depends on your operating system and database: ● Copying a single component from an MCOD landscape to another database at database level. ● Uninstalling 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. ■ When you use stopsap in an MCOD system with two central instances, only one central instance is stopped. Therefore, you must first stop the other SAP system with stopsap R3 to make sure that the database is also stopped. ■ For the first SAP system, the database system ID can be different from the SAP system ID. ■ For the second SAP system, you must use the same DBSID as for the first SAP system. ■ 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.
More Information

■ SAP Note 669902: Setting the national character set to UTF8 ■ SAP Note 975768: Deprecation of Java features with non-Unicode Backend ■ SAP Note 838402: Problems within non-Unicode system landscapes

6.2 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

2009-05-04

PUBLIC

123/182

6 6.3

Additional Information Integration of LDAP Directory Services

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

There is only one database administrator
Required File Systems

db2<dbsid>.

The following table lists the file systems that are required for an additional SAP system.
File System/Logical Volume Description

■ With DB2's automatic storage management: Use the automatic storage paths that have already been configured in your database. ■ No automatic storage management:
/db2/<SAPSID2>/sapdata<n> /db2/<DBSID>/sapdata<n> /sapmnt/<SAPSID2> /usr/sap/<SAPSID2>

SAP data for container type database-managed space (DMS) FILE By default, four Sapdata directories are created (sapdata1, sapdata2, sapdata3, sapdata4). Contains the temporary tablespaces. 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

6.3 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

124/182

PUBLIC

2009-05-04

6 6.3

Additional Information Integration of LDAP 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: ■ The communication protocol between the SAP system and the directory ■ How data in the directory is structured, accessed, or modified 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.
CAUTION

This section does not provide information about the use of LDAP directories with the LDAP Connector. For more information about using and configuring the LDAP Connector for an ABAP system, see the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management User and Role Administration of AS ABAP Configuration of User and Role Administration Directory Services LDAP Connector
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.
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

2009-05-04

PUBLIC

125/182

6 6.3

Additional Information Integration of LDAP Directory Services

https://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 at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine Administration Tools SAP Management Console
SAP Logon

Instead of using a fixed list of systems and message servers, you can configure the 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] Mode=LDAPdirectory LDAPserver= LDAPnode= LDAPoptions=

Distinguish the following cases: ■ If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For more information, see the SAP system profile parameter ldap/options. ■ You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either of the following is true: ● The client is not located in the same domain forest as the Active Directory ● 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. ■ 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

126/182

PUBLIC

2009-05-04

6 6.3

Additional Information Integration of LDAP Directory Services

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. If the SAP system has been prepared correctly, the SAP MC presents and analyzes system information that it gathers from various sources, including generic LDAP Directory. 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: ■ Extend the Active Directory schema to include the SAP-specific data types ■ 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. ■ Create the root container where information related to SAP is stored ■ 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 <Your SAP product> Software Life-Cycle Options LDAP Registration Active Directory Configuration . For more information about running SAPinst on Windows, see the documentation Installation Guide — <Your SAP product> on Windows: <Database>.

2009-05-04

PUBLIC

127/182

6 6.4

Additional Information Preparing an External ABAP System as Source for User Data 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 once for your system and choose <Your SAP product> Software Life-Cycle Options 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 registered in your directory server. The registration protocols of the components are dev_ldap*. The registration is updated every time a component starts.

6.4 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 AS Java of your SAP Java system to be installed. Doing 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 engine. You can take one of the following approaches:
Approach Advantages Disadvantages

Each Java system uses different users No interdependencies between the connected engines All Java systems use the same You create the users only once and configuration 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: ■ If you change the password of any of the users on the ABAP system, this change affects all connected engines. ■ If you change the administrator user’s password, you must also change the password in secure storage on

128/182

PUBLIC

2009-05-04

6 6.4

Additional Information Preparing an External ABAP System as Source for User Data Advantages Disadvantages

Approach

all of the connected J2EE 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. ■ In transaction PFCG, check that the roles SAP_BC_JSF_COMMUNICATION and SAP_BC_JSF_COMMUNICATION_RO exist and make sure that their profiles are generated. ■ In transaction PFCG, 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. ■ In transaction PFCG, create a role named ADSCallers. You do not need to maintain authorization data or generate any profiles for that role. ■ For more information about UME, see http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management User Management of the Application Server Java User Management Engine ■ For more information about role maintenance, see http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management User and Role Administration of AS ABAP Configuration of User and Role Administration Role Administration Role Administration Functions Changing Standard Roles
Procedure
Administration of the ABAP system

Perform the following administration steps in the ABAP system: 1. In transaction SU01, create a new communication user and assign it to the role SAP_BC_JSF_COMMUNICATION_RO.
RECOMMENDATION

We recommend that you assign this user the role SAP_BC_JSF_COMMUNICATION_RO for readonly (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. We recommend that you name the user SAPJSF_<SAPSID_Java_System>. You can use any password.

2009-05-04

PUBLIC

129/182

6 6.4

Additional Information Preparing an External ABAP System as Source for User Data

2.

In addition, to make sure that this user can only be used for communication connections between systems and not as a dialog user, assign it the type Communications under Logon data. In transaction SU01, create a new dialog user and assign it to role SAP_J2EE_ADMIN. This is your administrator user in the J2EE Engine.
RECOMMENDATION

We recommend that you name the user J2EE_ADM_<SAPSID_Java_System>. You can use any password.
CAUTION

3.

Make sure that you have changed 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. In transaction SU01, create a new dialog user and assign it to role SAP_J2EE_GUEST. This is your guest user in the J2EE Engine.
RECOMMENDATION

4.

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. In transaction SU01, create the following dialog users:
CAUTION

Make sure that you have changed 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. ■ Users for Adobe Document Services (ADS) (optional): ● ADSUSER: In transaction PFCG, assign the role ADSCallers to this user. ● ADS_AGENT: In transaction PFCG, assign the role SAP_BC_FP_ICF to this user. ■ SLD Data supplier user (optional): You only have to create this user if you want to install System Landscape Directory (SLD). The SLD data supplier user name that you enter later on during the Java system installation must be identical to this user.
RECOMMENDATION

We recommend that you name this user SLDDSUSER ■ SLD ABAP API user (optional):

130/182

PUBLIC

2009-05-04

6 6.5

Additional Information Setting up Swap Space for AIX

You only have to create this user if you want to install System Landscape Directory (SLD). The SLD ABAP API user name that you enter later on during the Java system installation must be identical to this user.
RECOMMENDATION

We recommend that you name this user SLDAPIUSER
NOTE

For more information about SLD users and security roles, see the Post-Installation Guide System Landscape Directory of SAP NetWeaver 7.0 at http://sdn.sap.com/irj/sdn/nw-sld. ■
Only valid for: Development Infrastructure (DI) |

Users for usage type Development Infrastructure (DI): ● ● ●
NWDI_ADM NWDI_DEV NWDI_CMSADM

End of: Development Infrastructure (DI) |

Activities for the Java System

Perform the following steps in the Java system: 1. 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. 2. During the installation of the Java system, make sure that you enter the correct users and passwords in the corresponding SAPinst dialogs.

6.5 Setting up Swap Space for AIX
Procedure

1.

Check the allocated swap space: 1. To start the System Management Interface Tool (SMIT), enter the following command: smitty. 2. Perform one of the following steps: ■ Choose Physical & Logical Storage Logical Volume Manager Paging Space List All Paging Spaces ■ Enter this command:
lsps -a

2. 3.

Check if there is sufficient swap space (see Hardware and Software Requirements [page 21]). If required, add another paging space using smitty: 1. Choose Physical & Logical Storage Logical Volume Manager Paging Space Add Another Paging Space A list of volume group names is displayed. 2. Select a volume group.

2009-05-04

PUBLIC

131/182

6 6.6

Additional Information Creating AIX Groups and Users

3. 4. 5. 6. 7.

Enter the size of paging space in logical partitions. Set Start using this paging space NOW ? to YES. Set Use this paging space each time the system is RESTARTED to YES. To exit smitty, choose F10 . To check the results, follow the procedure described above in step 1.

6.6 Creating AIX Groups and Users
Procedure
Creating AIX Groups and Users

To create AIX groups and users, use the System Management Interface Tool (SMIT): 1. Create groups as follows: 1. Enter the command smitty. 2. Choose Security and Users Groups Add a group . 3. Enter a group name – for example, sapsys – and set administration group to true. 4. Press F3 until the Security & Users menu appears. 2. To create users, proceed as follows: 1. Enter a user name, for example <sapsid>adm. 2. Enter all required values. 3. Set the initial password using the following command:
passwd <user> EXAMPLE passwd <sapsid>adm Checking Created Users

As user root check all existing users as follows: 1. Enter the command smitty. 2. Choose Security & Users Users Change/Show Characteristics of a User . 3. To obtain a list of users, choose F4 . 4. For user root and each created user <user> perform the following steps: 1. Select <user>. 2. Change field Soft CPU time to -1 (this is the default value). 3. Change field Soft CORE file size to 2097151 (this is the default value). 4. Change field Soft FILE size to 4194302.
NOTE

5. 6.

If you are using large file enabled file systems, set the field Soft FILE size to -1 (unlimited). Change field Soft DATA segment to -1. Change field Soft STACK size to -1.

132/182

PUBLIC

2009-05-04

6 6.7

Additional Information Setting Up File Systems and Raw Devices for AIX

You must make sure that the system-wide default HARD values are not explicitly defined to be lower than the values given above. Check the file /etc/security/limits under the default: stanza. If they are not explicitly set, then the values are as shown in the table at the top of the file.
Checking the Operating System

1. 2. 3. 4.

Enter the command smitty. Choose System Environments Change/Show Characteristics of Operating System . Change Maximum number of PROCESSES allowed per user to 500. To exit SMIT, choose F10 .

More Information

For more information about the users and groups that are created either by SAPinst or manually, see Creating Operating System Users [page 63].

6.7 Setting Up File Systems and Raw Devices for AIX
Procedure
Setting up File Systems

1.

2.

Create one logical volume for each file system listed in the appropriate SAP profile: 1. Using SMIT, choose Physical & Logical Storage Logical Volume Manager Logical Volumes Add a Logical Volume . 2. Enter a volume group name, for example, sapr3vg. 3. Enter a logical volume name, for example, lvsap01. 4. Enter the number of logical partitions. 5. Press F3 until the Physical & Logical Storage menu appears. Create the file systems. 1. Using SMIT, choose Physical & Logical Storage File Systems Add/Change/Show/Delete File Systems Journaled File Systems Add a Journaled File System on a previously defined Logical Volume Add a Standard Journaled File System . If you want to use large enabled file systems for files larger than 2 GB, you have to choose Add a Large File Enabled Journaled File System instead of Add a Standard Journaled File System. If you want to use JFS2 file systems, you have to choose Enhanced Journaled File System instead of Journaled File System. 2. To obtain a list of logical volumes, choose F4 . 3. Select one logical volume.
CAUTION

Select the logical volume with the desired size.

2009-05-04

PUBLIC

133/182

6 6.8

Additional Information Dialog Instance Installation for an Upgraded System only: Updating Profiles

4.

Enter mount point as given in the file system list files.
EXAMPLE /db2/<DBSID>

5. 6.

Set mount automatically to yes. To exit smitty, choose F10 .

Setting up Raw Devices

1. 2.

Create volume group. Create logical volume: 1. Enter the command smitty. 2. Choose Physical & Logical Storage Logical Volume Manager Logical Volumes Add a Logical Volume . 3. Enter volume group name. 4. Enter logical volume name (for example: lvsap02). 5. Enter the number of logical partitions. 6. Set the logical volume TYPE to r3data and press ENTER. 7. To exit SMIT, choose F10 .
NOTE

The logical volume can be accessed through /dev/r<name
EXAMPLE

of raw log.vol>.

3.

A logical volume called lvsap02 points to the device name /dev/rlvsap02. Accessing raw devices: It is not necessary to create a link to access the volume.

6.8 Dialog Instance Installation for an Upgraded System only: Updating Profiles
You only need to perform the Procedure further below if you want to install a dialog instance and you have already performed the following steps: 1. You upgraded your SAP system from an earlier source release to a target release lower than SAP NetWeaver 7.0 SR3. 2. You installed Enhancement Package 1 with the SAP Enhancement Package Installer.
Procedure

1.

On the SAP Global host, go to folder /<sapmnt>/<SAPSID>/profile.
NOTE

SAP system profiles are named as follows: Instance profiles: <SAPSID>_<INSTANCE_ID>_<hostname>.pfl Start profiles: START_<INSTANCE_ID>_<hostname>.pfl

134/182

PUBLIC

2009-05-04

6 6.9

Additional Information Mounting a CD / DVD for AIX

2.

3.

Make sure that the parameter DIR_CT_RUN, if set, has identical values in the instance profile and the start profile of the central instance: ■ If it is set in the instance profile, it must also be set in the start profile. ■ If it is not set in the instance profile, it must not be set in the start profile either. Edit the default profile DEFAULT.PFL by setting rdisp/msserv_internal to a free port number.
NOTE

Note that for AIX 5.3, the port 39<SCS_instance
EXAMPLE DEFAULT.PFL

number> is used by the NIM server of AIX.

Before the change: ...
rdisp/msserv = sapms<SAPSID>

... After the change: ...
rdisp/msserv = sapms<SAPSID> rdisp/msserv_internal = <free port number>

4.

... Edit the instance profile of the central services instance (SCS) and do the following: ■ Set rdisp/msserv to 0. ■ Set rdisp/msserv_internal to the port number assigned to rdisp/msserv.
EXAMPLE

Instance profile of the central services instance: Before the change: ...
rdisp/msserv = 4711

... After the change: ...
rdisp/msserv = 0 rdisp/msserv_internal = 4711

5.

... Restart all SAP services and instances of your SAP system.

6.9 Mounting a CD / DVD for AIX
NOTE <medium-mountdir> refers to either <cd-mountdir> or <dvd-mountdir>.

2009-05-04

PUBLIC

135/182

6 6.10

Additional Information Exporting and Mounting Directories via NFS for AIX

Use the following procedure to mount a CD / DVD:
Procedure

1. 2.

Log on as user root. Add a CD / DVD file system. 1. Enter the command smitty. 2. Choose Physical & Logical Storage File Systems Add / Change / Show / Delete File Systems CDROM File Systems Add a CDROM File System . 3. To obtain a list of device names, choose F4 . Select a device name. 4. Enter the mount point <medium-mountdir>.
EXAMPLE <medium-mountdir> is /sapcd

3.

5. Choose ENTER . 6. To exit smitty, choose F10 . Mount the CD / DVD as follows:
NOTE

Alternatively, you can mount the CD / DVD manually with the following command: mount -v cdrfs -r /dev/cd0 /sapcd. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. Enter the command smitty. Choose Physical & Logical Storage File Systems Mount a File System . Place the cursor on File System Name and choose F4 . Select the CD / DVD device /dev/cd0. Place the cursor on field Directory over which to mount and choose F4 . Select /sapcd. Place the cursor on field Type of File System and choose F4 . Select cdrfs. Change Mount as Read Only system to YES Choose ENTER . To exit smitty, choose F10 .

6.10 Exporting and Mounting Directories via NFS for AIX
There are two ways of mounting directories via NFS: ■ Manually ■ Using the System Management Interface Tool (SMIT)
Procedure

To mount directories via NFS from the host where the directory to be mounted resides:

136/182

PUBLIC

2009-05-04

6 6.10

Additional Information Exporting and Mounting Directories via NFS for AIX

1. 2.

3.

4. 5.

Log on as user root. To start NFS services at the host where the directory to be mounted resides, use SMIT as follows: 1. Enter the command smitty. 2. Choose Communications Applications and Services NFS Network File System (NFS) Configure NFS on this System Start NFS . 3. In the line Start NFS now, on system restart or both, enter: both. 4. Choose ENTER . Export the directory (for example <sapmnt>/<SAPSID>/exe) with read or read-write access for the host where the additional instance runs: 1. Enter the command smitty. 2. Choose Communications Applications and Services NFS Network File System (NFS) Add a Directory to Exports List . 3. Enter the path of the directory that you want to export (for example, <sapmnt>/<SAPSID>/ exe). 4. Choose export mode (use read-write or read-only as required by SAP). In the line HOSTS allowed root access, enter the name of the host where the additional instance runs. For security reasons, this root access should be disabled after the installation. 5. In the line Export directory now, system restart or both, enter: both 6. Choose ENTER . Create the mount point at the host where the additional instance runs: /usr/bin/mkdir
<sapmnt>/<SAPSID>/exe

6.

Mount the directory on the host where the additional instance runs. 1. Enter the command smitty. 2. Choose Communications Applications and Services NFS Network File System (NFS) Add a File System for Mounting . 3. Enter the path name of the mount point. 4. Enter the path name of the remote directory (the directory of the central instance). 5. Enter the host where the remote directory resides. 6. Set Mount now, add entry to /etc/filesystems or both to both. 7. Set /etc/filesystems entry will mount the directory on system RESTART to yes. 8. Change Mount file system soft or hard to soft and press ENTER. If you exported the directory with read-write access, check if the host where the future additional instance is to run has write access to directory <sapmnt>/<SAPSID>/exe using the following commands:
cd <sapmnt>/<SAPSID>/exe touch test (create a file called test) ls -l test (check if file test is created) rm test (remove the file test)

2009-05-04

PUBLIC

137/182

6 6.11

Additional Information Additional Information About SAPinst

6.11 Additional Information About SAPinst
The following sections provide additional information about SAPinst: ■ Using SAPinst GUI [page 138] ■ Interrupted Installation with SAPinst [page 139] ■ Performing a Remote Installation with SAPinst [page 140] ■ Starting SAPinst GUI Separately [page 142]. ■ Entries in the Services File Created by SAPinst [page 144]

6.11.1 Using SAPinst GUI
The following table shows the most important functions that are available in SAPinst GUI:
SAPinst GUI Functions Input Type Label
F1

Description

Function key Menu option

File

Exit

Displays detailed information about each input parameter Stops the SAPinst GUI, but SAPinst and the GUI server continue running
NOTE

Menu option

SAPinst

Log Browser

Menu option

SAPinst

Cancel

If you need to log off during the installation from the host where you control the installation with SAPinst GUI, the installation continues while you are logged off. You can later reconnect to the same SAPinst installation from the same or another host. For more information, see Starting SAPinst GUI Separately [page 142]. Displays the Log Viewer dialog This dialog enables you to access the following log files directly: ■ Installation log (sapinst_dev.log) ■ Log files from the SAPinst GUI server These log files might help you during troubleshooting with SAPinst [page 167]. Cancels the installation with the following options: ■ Stop Stops the installation (SAPinst GUI, SAPinst, and the GUI server) without further changing the installation files You can restart and continue the installation later from this point. ■ Continue Continues the installation

138/182

PUBLIC

2009-05-04

6 6.11

Additional Information Additional Information About SAPinst Label Description

Input Type

Message button Message button

Retry Stop

Message button

Continue

Performs the installation step again (if an error has occurred) Stops the installation without further changing the installation files You can continue the installation later from this point. Continues with the option you chose previously

6.11.2 Interrupted Installation with SAPinst
The SAP system installation might be interrupted for one of the following reasons: ■ 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. ■ You interrupted the installation by choosing Cancel in the SAPinst menu. The following table describes the options in the dialog box:
Option Definition

Retry

Stop

Continue View Log
NOTE

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.

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

2009-05-04

PUBLIC

139/182

6 6.11

Additional Information Additional Information About SAPinst CAUTION

2.

Make sure that the root user has not set any environment variables for a different SAP system or database. Mount your Installation Master DVD.
NOTE

3.

Mount the DVD locally. We do not recommend using Network File System (NFS). Start SAPinst using the following commands:
cd <Installation_Master_DVD>/IM_<OS> ./sapinst

4.

From the tree structure in the Welcome screen, select the installation option that you want to continue and choose Next.
NOTE

If there is only 1 component to install, the Welcome screen does not appear. 5. The What do you want to do? screen appears. In the What do you want to do? screen, decide between the following alternatives and confirm with OK:
Behavior

Alternative

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>.
EXAMPLE
log_01_Oct_2008_13_47_56

CAUTION

Continue with the Old Option

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 option from the point of failure.

6.11.3 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 SAPinst GUI server run on the remote host, and SAPinst GUI client runs on the local host. The local host is the host from which you control the installation with the SAPinst GUI client. The GUI client connects using a secure SSL connection to the GUI server and the GUI server connects to SAPinst.

140/182

PUBLIC

2009-05-04

6 6.11

Additional Information Additional Information About SAPinst

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools such as VNC Viewer or NX Server / NX Client – offered by various vendors or open source – for remote access to SAPinst GUI on Windows workstations. We recommend that you use the Hummingbird Exceed X Server, which we use to validate installations with SAPinst. For more information, see SAP Note 1170809.
CAUTION

The behavior of SAPinst, GUI server and GUI client has changed compared to previous versions. SAP no longer delivers any JCE policy archives within the SAP Java Virtual Machine (SAP JVM). You have to download the required Java Cryptography Extension (JCE) policy zip file from SAP on the remote host. For more information, see SAP Note 1238121.
Prerequisites

■ The remote host meets the prerequisites as described in Prerequisites in Running SAPinst [page 88]. ■ 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>.
Procedure

1.

Log on to your remote host as user root.
CAUTION

2. 3. 4.

Make sure that the root user has not set any environment variables for a different SAP system or database. Mount the Installation Master DVD. Download the JCE policy zip file from SAP as described in SAP Note 1240081. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive as follows:
Shell Used Command
JCE_POLICY_ZIP=<policy zip archive> export JCE_POLICY_ZIP

Bourne shell (sh) C shell (csh) Korn shell (ksh)

setenv JCE_POLICY_ZIP <policy zip archive> export JCE_POLICY_ZIP=<policy zip archive>

5.

Change to the directory of the sapinst executable and start SAPinst without GUI using the following commands:
cd <mountpoint_of_Installation_Master_DVD>/IM_<OS> ./sapinst -nogui

For more information about SAPinst, see Running SAPinst [page 88]. SAPinst now starts and waits for the connection to the SAPinst GUI client. You see the following at the command prompt:

2009-05-04

PUBLIC

141/182

6 6.11

Additional Information Additional Information About SAPinst guiengine: no GUI connected; waiting for a connection on host <host_name>, port <port_number> to continue with the installation.

6.

Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 142].

6.11.4 Starting the SAPinst GUI Separately
You use this procedure to start the SAPinst GUI client separately. You might need to start the GUI client separately in the following cases: ■ You have logged off from SAPinst. If you logged off during the installation and you later want to reconnect to the installation while it is still running, you can start SAPinst GUI separately. ■ You want to perform a remote installation [page 140]. If the GUI client runs on a different host from SAPinst and the GUI server, you have to start the GUI client separately on the local host.
CAUTION

The behavior of SAPinst has changed compared to previous versions. SAP no longer delivers any JCE policy archives within the SAP JVM. You have to download the required JCE policy zip file from SAP on the local host. For more information, see SAP Note 1238121.
Procedure
Starting the GUI Client on Windows

1. 2. 3.

Log on as a member of the local administrators group. Download the JCE policy zip file from SAP as described in SAP Note 1240081. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive by entering the following command:
set JCE_POLICY_ZIP=<policy zip archive>

4. 5.

Insert the SAP Installation Master DVD into your DVD drive. Change to the directory of the sapinst executables:
<DVD drive>:\IM_WINDOWS_<platform> NOTE

If you want to start the GUI client on a Windows 32-bit operating system, change to the following directory:
<Installation_Master_DVD>\IM_WINDOWS_I386

6.

Start the GUI client by double-clicking sapinstgui.exe The GUI client starts and tries to connect to the GUI server and SAPinst, using the local host as default.

142/182

PUBLIC

2009-05-04

6 6.11

Additional Information Additional Information About SAPinst

If SAPinst and the GUI server are running on another host, the GUI client cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of the host on which SAPinst is running and choose Log on. The first screen of the installation appears and you can perform the remote installation from your local host.
NOTE

Optionally you can start sapinstgui.exe with the following parameters: ■ host=<host name>, where <host name> is the host name of the installation host ■ port=<nr>, where <nr> is the port number for the connection to the GUI server ■ -accessible enables accessibility mode Example: sapinstgui host=lsi1209 port=3000 -accessible ■ -h displays a list of all available parameters
Starting the GUI Client on UNIX

1.

Log on as user root.
CAUTION

2. 3.

Make sure that the root user has not set any environment variables for a different SAP system or database. Download the JCE policy zip file from SAP as described in SAP Note 1240081. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive as follows:
Shell Used Command
JCE_POLICY_ZIP=<policy zip archive> export JCE_POLICY_ZIP

Bourne shell (sh) C shell (csh) Korn shell (ksh)

setenv JCE_POLICY_ZIP <policy zip archive> export JCE_POLICY_ZIP=<policy zip archive>

4.

Mount your Installation Master DVD.
NOTE

5.

Mount the DVD locally. We do not recommend that you use Network File System (NFS). Change to the directory of the sapinst executables:
<mountpoint_of_Installation_Master_DVD>/IM_<OS> NOTE

If you want to start the GUI client on a Linux 32–bit platform, change to the following directory:
<mountpoint_of_Installation_Master_DVD>/IM_LINUX_I386

6.

Start the GUI client by executing ./sapinstgui The GUI client starts and tries to connect to the GUI server and SAPinst, using the local host as default.

2009-05-04

PUBLIC

143/182

6 6.12

Additional Information Installation of Additional Software Units or Usage Types in an Existing SAP System

If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of the host on which SAPinst is running and choose Log on. The first screen of the installation appears and you can perform the remote installation from your local host.
NOTE

Optionally, you can start sapinstgui with the following parameters: ■ host=<host name>, where <host name> is the host name of the installation host ■ port=<nr>, where <nr> is the port number for the connection to the GUI server ■ -accessible enables accessibility mode Example: ./sapinstgui host=lsi1209 port=3000 -accessible ■ -h displays a list of all available parameters

6.11.5 Entries in the Services File Created by SAPinst
After the installation has finished successfully, SAPinst has created the following entries in /etc/ services:
sapdpXX = 32XX/tcp sapdpXXs = 47XX/tcp sapgwXX = 33XX/tcp sapgwXXs = 48XX/tcp NOTE

XX is the instance number. The ports are created for all instance numbers, regardless of which

instance number you specified during the installation. For more information about instance numbers, see the table SAP System Instances, Hosts, and Ports in Basic SAP System Parameters [page 44]. ■ If there is more than 1 entry for the same port number, this is not an error.

6.12 Installation of Additional Software Units or Usage Types in an Existing SAP System
You perform the installation of additional software units or usage types in an existing Java system to optimize total cost of ownership (TCO). That is, you do not have to install a complete additional Java system to run these additional software units or usage types. To install additional Java software units or usage types in an existing SAP system based on SAP NetWeaver 7.0 including enhancement package 1 Support Release 1, you cannot use SAPinst. Instead, you have to use the Java Support Package Manager (JSPM). “Existing SAP system” means that this SAP system has at least AS Java.

144/182

PUBLIC

2009-05-04

6 6.12

Additional Information Installation of Additional Software Units or Usage Types in an Existing SAP System

Naming Conventions

In this section, the term SAP NetWeaver 7.0 EHP1 SR1 is used for SAP NetWeaver 7.0 including Enhancement Package 1 Support Release 1.
Restrictions

It is not possible to install SAP NetWeaver Process Integration (PI) or SAP NetWeaver Mobile Infrastructure (MI) as an additional usage type using JSPM in an existing dual-stack (ABAP+Java) system. Instead, you need to install a new SAP Process Integration system or a new SAP Mobile Infrastructure system from scratch using SAPinst. Use the documentation Installation Guide – SAP NetWeaver 7.0 ABAP +Java including Enhancement Package 1 SR1 on <OS>: <Database>, which is available at http:// service.sap.com/installnw70.
Prerequisites

■ The existing SAP system must have at least usage type Application Server Java (AS Java). ■ You have planned your SAP system landscape according to the Master Guide and the Technical Infrastructure Guide at http://service.sap.com/installnw70. ■ Make sure that you have read SAP Note 1268493 for more information about the installation of additional usage types.
Procedure
Preparation

1.

2.

Check which usage types are already installed on your system. You can do this in one of the following ways: ■ Start JSPM and choose the Deployed Components tab. ■ Check the usage type system information page of your system using the URL http:// <host>:<http_port>/utl/UsageTypesInfo. For more information about how to do this, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Maintenance Java Support Package Manager Viewing the Deployed Components Check the dependencies for the usage types you want to install:
Usage Types of SAP NetWeaver 7.0 EHP1 Usage Type Name Long Text Depends on

BI Java DI EP Core

SAP NetWeaver Business AS Java Intelligence Java SAP NetWeaver Development AS Java Infrastructure SAP NetWeaver Enterprise Portal AS Java Core Component

2009-05-04

PUBLIC

145/182

6 6.12

Additional Information Installation of Additional Software Units or Usage Types in an Existing SAP System Usage Type Name Long Text Depends on

EP

SAP NetWeaver Enterprise Portal AS Java, EP Core
NOTE

3.

Check hardware and software requirements: You cannot use the Prerequisite Checker to check the requirements of additional usage types. For more information about the installation prerequisite checker, see Running the Prerequisite Checker in Standalone Mode (Optional) [page 23]. ■ If you want to install additional usage types in a central system, check the hardware and software requirements as described in Requirements for a Central System [page 24]. ■ If you want to install additional usage types in a distributed or a high-availability system, check the hardware and software requirements for the central instance as described in Requirements for the Central Instance [page 31]. ■ Check Java virtual memory settings according to SAP Note 723909. ■ Check the requirements for the Java Support Package Manager as described in SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Requirements for Free Disk Space Download the required Software Component Archives (SCAs) and the appropriate stack definition file. For more information about how to use the Maintenance Optimizer, see SAP Library at: http://help.sap.com SAP Solution Manager <Current Release> SAP Solution Manager Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance
RECOMMENDATION

4.

We recommend that you also download the most current Support Package Stack for AS Java to update the JSPM to the most current SPS level. Usage Types of SAP NetWeaver 7.0 EHP1 SR1 ■ Components of Business Intelligence Java (UT_NAME = BI):
Name of SCA Description

BIIBC**_*.SCA BIWEBAPP**_*.SCA BIBASES**_*.SCA BIREPPLAN**_*.SCA BIWDALV**_*.SCA VCKITBI**_*.SCA

BI INFORM. BROADCASTING 7.00 BI WEB APPLICATIONS 7.00 (SP <current SP number>) BI BASE SERVICES 7.00 (SP <current SP number>) BI REPORTING AND PLANNING 7.00 BI WEBDYNPRO ALV 7.00 VCKITBI

■ Components of Development Infrastructure (UT_NAME = DI):
Name of SCA Description

DICBS**_*.SCA

DI COMPONENT BUILD SERVER 7.00

146/182

PUBLIC

2009-05-04

6 6.12

Additional Information Installation of Additional Software Units or Usage Types in an Existing SAP System Name of SCA Description

DICMS**_*.SCA DIDTR**_*.SCA

DI CHANGE MGMT SERVER 7.00 DI DESIGN TIME REPOSITORY 7.00

■ Components of Enterprise Portal Core Component (UT_NAME = EPC):
Name of SCA Description

EPBC**_*.SCA EPBC2**_*.SCA EPPSERV**_*.SCA EPWDC**_*.SCA UWLJWF**_*.SCA SAPEU**_*.SCA

PORTAL CORE SERVICES 7.00 PORTAL FRAMEWORK 7.00 PORTAL 7.00 PORTAL WEB DYNPRO 7.00 UWL AND COLL PROCESS ENGINE 7.00 CAF EU 7.00

■ Components of Enterprise Portal (UT_NAME = EP):
Name of SCA Description

NETPDK**_*.SCA LMPORTAL**_*.SCA CAFKM**_*.SCA KMCCOLL**_*.SCA KMCCM**_*.SCA RTC**_*.SCA RTCSTREAM**_*.SCA KMCBC**_*.SCA VCBASE**_*.SCA VCFLEX**_*.SCA VCKITGP**_*.SCA VCKITXX**_*.SCA WDEXTENSIONS**_*.SCA VCFRAMEWORK**_*.SCA

PDK PORTAL SERVICES 7.00 LIFECYCLE MGMT PORTAL 7.00 SAP CAF-KM 7.00 KMC COLLABORATION 7.00 KMC CONTENT MANAGEMENT 7.00 RTC 7.00 STREAMING SERVER 7.00 KMC BASE COMPONENTS 7.00 VCBASE VCFLEX VCKITGP VCKITXX WDEXTENSIONS VCFRAMEWORK

5.

6.

Copy the downloaded SCAs and the appropriate stack definition file to the JSPM inbox directory as described in SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Detecting and Changing the JSPM Inbox Directory Enterprise Portal Core Component, Enterprise Portal only: You must check in the SDM RemoteGui whether the following two substitution variables of type String are created properly: ■
com.sap.portal.deploy.pcd = <com.sap.engine.installdir>/cluster/server0/apps/ sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd

2009-05-04

PUBLIC

147/182

6 6.12

Additional Information Installation of Additional Software Units or Usage Types in an Existing SAP System

com.sap.portal.deploy.pcdcontent = <com.sap.engine.installdir>/cluster/ server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent NOTE <com.sap.engine.installdir> is the current value of SDM variable com.sap.engine.installdir

If these substitution variables do not exist or have incorrect values, you must create them manually as a prerequisite for the deployment of usage types EPC and EP. For more information, see Software Deployment Manager SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver Developer's Guide Fundamentals Using Java Core Development Tasks Deployment: Putting It All Together Software Deployment Manager Deployment Substitution Variables Management
Installation

1.

2.

3.

Start JSPM as described in SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Starting JSPM We strongly recommend that you update JSPM to the most recent Support Package stack level as described in SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Applying Single Support Packages Run option Install Additional Usage Type as described in SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle Management Software Maintenance Java Support Package Manager Installing an Additional Usage Type

Post-Installation

After you have finished the deployment with JSPM, you need to perform initial configuration to complete the installation of additional usage types before you perform the actual configuration.
CAUTION

You must not run the Configuration Wizard for the added software units or usage types. Instead, you have to configure them manually.

148/182

PUBLIC

2009-05-04

6 6.13

Additional Information Creating Tablespaces Manually (Optional)

1.

For initial configuration, perform the steps listed in Usage Type-Specific Initial Configuration [page 159].
NOTE

2.

SAPinst performs these steps during the installation of an SAP system with usage types. JSPM does not perform these steps. For complete configuration, use the configuration documentation for your SAP system application from the SAP Library or from SAP Solution Manager. For more information about how to create a project structure that contains the required configuration documentation, see Accessing Configuration Documentation in SAP Solution Manager [page 118].

6.13 Creating Tablespaces Manually (Optional)
If the tablespace layout used by SAPinst does not meet your requirements, you an 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.

3.

In a typical installation, this dialog does not appear. To reach the dialog, 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. 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

You must create all the tablespaces that are listed in the script.

2009-05-04

PUBLIC

149/182

6 6.14

Additional Information Starting and Stopping SAP System Instances

4. 5. 6.

Modify the CREATE statements according to your requirements. To execute the script, enter the following command:
db2 —tvf <script_name>

When you have finished, continue with the installation by choosing OK on the message box.

More Information

■ DB2 Tablespaces [page 55] ■ Data Safety and Performance Considerations for Production Systems [page 56]

6.14 Starting and Stopping SAP System Instances
You can start and stop SAP system instances and the Diagnostics Agent by using the SAP Management Console (SAP MC) [page 150]. Apart from using the SAP Management Console (SAP MC) you can also use scripts to: ■ Start or stop SAP system instances [page 153] ■ Start or stop the Diagnostics Agent [page 156].

6.14.1 Starting and Stopping SAP System Instances Using the SAP Management Console
You can start and stop all SAP system instances (except the database instance) and the Diagnostics Agent using the SAP Management Console (SAP MC). You have to start and stop the database instance as described in Starting and Stopping the SAP System Using startsap and stopsap [page 153].
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 (SAP MMC). For more information about handling the MMC, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS SAP Microsoft Management Console: Windows
Prerequisites

■ Make sure that the host where you want to start SAP MC meets the following requirements: ● Java Runtime Environment (JRE) 5.0 is installed. ● The browser supports Java. ● The browser's Java plug-in is installed and activated. ■ You have logged on to the host as user <sapsid>adm.

150/182

PUBLIC

2009-05-04

6 6.14

Additional Information Starting and Stopping SAP System Instances

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 53 and 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. By default, the instances installed on the host you have connected to are already added in the SAP Management Console.
NOTE

If the instances have not been added or if you want to change the configuration to display systems and instances on other hosts, you have to register your system manually. This is described in Registering Systems and Instances in the SAP Management Console below.
Starting and Stopping SAP System Instances Starting SAP Systems or Instances

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 choose Start from the context menu. 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 credentials of the SAP system administrator. To complete the operation, you must have administration permissions. Log in as user <sapsid>adm.
Starting the Instances of a Distributed SAP System 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 as follows: 1. Start the database instance. 2. Start the central services instance SCS<Instance_Number>.

2009-05-04

PUBLIC

151/182

6 6.14

Additional Information Starting and Stopping SAP System Instances

3. 4.

Start the central instance JC<Instance_Number>. Start dialog instances J<Instance_Number>, if there are any.

Stopping SAP Systems or Instances

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 the Instances of a Distributed SAP System 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 as follows: 1. Stop dialog instances J<Instance_Number>, if there are any. 2. Stop the central instance JC<Instance_Number>. 3. Stop the central services instance SCS<Instance_Number>. 4. 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.
Prerequisites

The SAP MC is started.
Registering SAP Systems or Instances

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 System’s 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 the Instances of a Distributed SAP System Separately

1.

In the SAP MC, choose File New .

152/182

PUBLIC

2009-05-04

6 6.14

Additional Information Starting and Stopping SAP System Instances

2. 3.

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

■ 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 pane, choose the instance you want the SAP MC to display on startup. 3. Choose the << button. 4. Choose Apply and then OK. Similarly, you can remove instances from the startup configuration. ■ 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. ■ 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 the SAP Management Console, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS SAP Management Console

6.14.2 Starting and Stopping SAP System Instances Using Scripts
You can start and stop SAP system instances by running the startsap and stopsap scripts. You can also use the SAP Management Console (SAP MC) to start or stop the instances of the SAP system (see Starting and Stopping SAP System Instances Using the SAP Management Console [page 150]).

2009-05-04

PUBLIC

153/182

6 6.14

Additional Information Starting and Stopping SAP System Instances

Prerequisites

■ You have checked the default profile /<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameter login/system client and set the value to the correct production system client. For example, the entry must be login/system_client = 001 if your production client is 001. ■ You have checked the settings for Java Virtual Machine parameters as described in SAP Note 723909. ■ You have logged on to the SAP system hosts as user <sapsid>adm. ■ 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. ■ 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 startsap or stopsap in the home directory of the corresponding user.
CAUTION

If there are multiple SAP instances on one host – for example, a central instance and a dialog instance – you must add an extra parameter to the scripts:
startsap <instanceID> stopsap <instanceID>

For example, enter:
startsap JC00 NOTE

The instance name (instance ID) of the central instance is JC<Instance_Number>, the instance name of the central services instance is SCS<Instance_Number>, and the instance name of a Java dialog instance is J<Instance_Number>.
Procedure
Starting SAP System Instances

■ To start all instances on the central system host, enter the following command:
startsap

This checks if the database is already running. If not, it starts the database first.
NOTE

You can start the database and SAP system separately by entering the following commands:
startsap DB startsap R3 <instance ID of central services instance> startsap R3 <instance ID of central instance> startsap R3 <instance ID of dialog instance>

Make sure that you always start the database first because otherwise the other instances cannot start.

154/182

PUBLIC

2009-05-04

6 6.14

Additional Information Starting and Stopping SAP System Instances NOTE

You can also use the parameter J2EE, which is a synonym for the parameter R3. For ABAP+Java systems, you can enter either the command startsap R3 or startsap J2EE to start the SAP instance comprising both ABAP and Java. ■ In a distributed system, proceed as follows: 1. On the database host, enter:
startdb

2. 3.

On the central services and on the central instance host, enter:
startsap

For dialog instances, enter the following on the relevant host:
startsap R3 <instance ID of dialog instance> NOTE

Make sure that the SAP system and associated J2EE Engines are up and running before you start or restart dialog instances and their J2EE Engines.
Stopping SAP System Instances NOTE

When you use stopsap in a system with Multiple Components in One Database (MCOD) that has two central instances, only one central instance and the database shut down. Therefore, you must first stop the other SAP system with stopsap R3 or make sure that it has already been stopped. For more information, see Installation of Multiple Components in one Database [page 122]. ■ If you have a central system, enter the following to stop all instances on the central system host:
stopsap

This stops the central instance, central services instance, and database.
NOTE

You can stop the database and SAP system separately by entering the following commands:
stopsap R3 <instance ID of dialog instance> stopsap R3 <instance ID of central instance> stopsap R3 <instance ID of central services instance> stopsap DB

Make sure that you always stop the central instance first and the central services instance second because otherwise the database cannot be stopped.
NOTE

You can also use the parameter J2EE, which is a synonym for the parameter R3. For ABAP+Java systems, you can enter either the command stopsap R3 or stopsap stop the SAP instance comprising both ABAP and J2EE. ■ In a distributed system, proceed as follows: 1. On the dialog instance host, enter the following command:

J2EE to

2009-05-04

PUBLIC

155/182

6 6.14

Additional Information Starting and Stopping SAP System Instances stopsap <instance ID of dialog instance>

2.

To stop the central services instance on the central services and on the central instance host, enter the following command:
stopsap

3.

To stop the database, enter the following command on the database host:
stopdb

CAUTION

Make sure that no SAP instance is running before you enter stopdb on a standalone database server. No automatic check is made.

6.14.3 Starting and Stopping the Diagnostics Agent Using Scripts
You can start and stop the Diagnostics Agent by running the smdstart and smdstop scripts. The local versions of these scripts are located in /usr/sap/<SMDSID>/J<instance_number>/script. The global versions of these scripts are located in /usr/sap/<SMDSID>/exe.
NOTE

You can only start or stop the Diagnostics Agent separately. It is not started or stopped automatically with the SAP system. You can also use the SAP Management Console (SAP MC) to start or stop the Diagnostics Agent (see Starting and Stopping SAP System Instances Using the SAP Management Console [page 150]).
Prerequisites

You have logged on to the central instance or dialog host as user <smdsid>adm.
Procedure
Starting a Diagnostics Agent Locally

1. 2.

Change to the following directory:
/usr/sap/<SMDSID>/J<Instance_Number>/script

To start the Diagnostics Agent locally, enter this command:
./smdstart.sh

Starting Diagnostics Agents Globally

To start Diagnostics Agents globally, enter this command:
smdstart <SMDSID> <Instance_Number> EXAMPLE smdstart SMD 98

156/182

PUBLIC

2009-05-04

6 6.15

Additional Information Creating a User for LDAP Directory Access NOTE

You do not have to specify the <SMDSID> if there is only one Diagnostics Agent system on this host.
Stopping a Diagnostics Agent Locally

1. 2.

Change to the following directory:
/usr/sap/<SMDSID>/J<instance_number>/script

To stop the Diagnostics Agent locally, enter this command:
./smdstop.sh

Stopping Diagnostics Agents Globally

To stop Diagnostics Agents globally, enter this command:
smdstop <SMDSID> <Instance_Number> EXAMPLE smdstop SMD 98 NOTE

You do not have to specify the <SMDSID> if there is only one Diagnostics Agent system on this host.

6.15 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 Preparing the Active Directory 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. 3.

Log on as user <sapsid>adm. Enter:
ldappasswd pf=<path_and_name_of_instance_profile>

Enter the required data.
EXAMPLE

The following is an example of an entry to create an LDAP Directory User:
CN=sapldap,CN=Users,DC=nt5,DC=sap-ag,DC=de

2009-05-04

PUBLIC

157/182

6 6.16

Additional Information Accessing the SAP Java Documentation

6.16 Accessing the SAP Java Documentation
Here you can find information about the configuration and administration of the J2EE Engine and about SAP Java technology in the SAP Library.
Procedure

1.

2.

Go to http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology . Check the following documentation for information relevant to running your Java system:
Manual Contents

Architecture Manual

This manual describes the architecture of a Java or ABAP+Java system. It contains information on: ■ Java cluster architecture including central services, load balancing, and high availability. ■ J2EE Engine system architecture ■ SAP NetWeaver Java development infrastructure, including the SAP NetWeaver Developer Studio
NOTE

Administration Manual

The SAP NetWeaver Developer Studio is the SAP development infrastructure for Java. The Architecture Manual describes the integration of the SAP NetWeaver Developer Studio into the SAP development infrastructure. This manual describes how to administer the SAP system, focusing on the J2EE Engine. It contains information on: ■ System landscape administration ■ Software life-cycle management
NOTE

■ ■ ■ ■

This part of the manual contains important information about: ● Installation information ● System Landscape Directory (SLD) ● Software Lifecycle Manager (SLM) ● Java Support Package Manager ● Administration of SAP NetWeaver Java Development Infrastructure (JDI) J2EE Engine and J2EE Engine security Supportability and performance management Administration and configuration of Web Dynpro runtime environment Administration of the XML Data Archiving Service (XML DAS)
CAUTION

Make sure that you check the mandatory post-installation procedures listed in the Administration Manual under J2EE Engine Installation Information Post-Installation Procedures .

158/182

PUBLIC

2009-05-04

6 6.17

Additional Information Usage Type-Specific Initial Technical Configuration Manual Contents

Java Development Manual

Migration Manual

This manual describes the technologies for developing Java-based business applications. It explains how to use the SAP NetWeaver Developer Studio, which is the SAP Java development environment. This manual contains all the information you need to migrate an application created in J2EE Engine 6.20.

More Information

For more information about troubleshooting for the J2EE Engine, see the J2EE Engine Problem Analysis Guide at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) Usage Type Application Server Java J2EE Engine Problem Analysis Scenarios

6.17 Usage Type-Specific Initial Technical Configuration
SAPinst performs initial technical configuration steps for the usage types shown below during the installation. However, you might have to perform these steps manually if: ■ You have installed an additional usage type to an existing SAP system as described in Installation of Additional Software Units or Usage Types in an Existing SAP System [page 144].
NOTE

This currently applies to the following usage types: ● Development Infrastructure (DI) ● EP Core (EPC) ● Enterprise Portal (EP) ● Business Intelligence (BI Java) ■ You want to change existing parameters or if you want to set additional parameters. The following usage type-specific sections provide the required information: ■ Application Server Java (AS Java) [page 159] ■ Development Infrastructure (DI) [page 162] ■ EP Core (EPC) and Enterprise Portal (EP) [page 164] ■ Business Intelligence (BI Java) [page 165]

6.17.1 Initial Technical Configuration for SAP NetWeaver Application Server Java (AS Java)
SAPinst performs initial technical configuration steps for some components of SAP NetWeaver Application Server Java (AS Java).

2009-05-04

PUBLIC

159/182

6 6.17

Additional Information Usage Type-Specific Initial Technical Configuration

However, you might have to perform some of these steps manually after SAPinst has finished, depending on your installation scenario. These are the following components: ■ Adobe Document Services (ADS) [page 160] ■ Composite Application Framework (CAF) [page 160] ■ System Landscape Directory (SLD) [page 161]

6.17.1.1 Initial Technical Configuration for Adobe Document Services
SAPinst automatically performs some initial technical configuration steps for Adobe Document Services (ADS) during the installation. However, you might have to perform these steps manually if you want to change existing parameters or if you want to set additional parameters.
Features

SAPinst performs the following steps: ■ SAPinst creates user ADSUser in AS Java for basic authentication and assigns it to group ADSCallers. For more information about this user, see Ensuring User Security [page 103]. ■ SAPinst sets up basic authentication in the Java environment.
More Information

For more information about how to perform these steps manually, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Business Task Management Adobe Document Services (Configuration) Adobe Document Services Configuration Guide Configuring the Web Service Securing Access to the Web Service Configuration of the Web Service for Basic Authentication The Adobe Document Services Configuration Guide is also available in PDF form at: http://sdn.sap.com/irj/sdn/adobe Installation & Configuration SAP Interactive Forms – Configuration Guides Configuration Guide for SAP Interactive Forms by Adobe

6.17.1.2 Initial Technical Configuration for Composite Application Framework Core (CAF)
SAPinst automatically performs some initial technical configuration steps for Composite Application Framework Core (CAF) during the installation. However, you might have to perform these steps manually if you want to change existing parameters or if you want to set additional parameters.

160/182

PUBLIC

2009-05-04

6 6.17

Additional Information Usage Type-Specific Initial Technical Configuration

Features

SAPinst performs the following steps: ■ SAPinst creates the following roles with the required User Management Engine (UME) actions: ● CAFAdmin ● CAFUIAdmin For more information about how to perform this step manually, see the SAP Library at http:// help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Developing, Configuring, and Adapting Applications Creating Composite Applications Composite Application Framework Core Configuration Guide Setting Up Roles . ■ SAPinst configures CAF runtime properties for Business Warehouse (BW) integration. For more information about how to perform this step manually, see the SAP Library at http:// help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Developing, Configuring, and Adapting Applications Creating Composite Applications Composite Application Framework Core Configuration Guide Configuring CAF Core for BW Integration Configuring CAF Runtime Properties for BW Integration . ■ SAPinst configures CAF runtime properties for knowledge management integration. For more information about how to perform this step manually, see the SAP Library at http:// help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Developing, Configuring, and Adapting Applications Creating Composite Applications Composite Application Framework Core Configuration Guide Configuring CAF Core for Knowledge Management Integration Configuring CAF Repository Managers Configuring CAF Runtime Properties . ■ SAPinst creates data sources to extract custom enumeration types. For more information about how to perform this step manually, see the SAP Library at http:// help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver Developer’s Guide Fundamentals Creating Composite Applications Developing Composite Applications with CAF Core Integration CAF Core and SAP Business Information Warehouse Integration DataSource Use in CAF and SAP BW Integration DataSources to Extract Custom Enumeration Types .

6.17.1.3 Initial Technical Configuration for the System Landscape Directory (SLD)
SAPinst automatically performs some initial technical configuration steps for the System Landscape Directory (SLD) during the installation: ■ If you chose the option Register in existing central SLD, SAPinst automatically configures the connection of the system being installed to an existing central SLD.

2009-05-04

PUBLIC

161/182

6 6.17

Additional Information Usage Type-Specific Initial Technical Configuration

■ If you chose the option Configure a local SLD, SAPinst automatically sets up and configures a local SLD during the installation. However, you might have to perform these steps manually if you want to change existing parameters or if you want to set additional parameters.
Features

SAPinst performs the following steps: ■ SAPinst configures SLD security roles. ■ SAPinst configures server and persistence parameters. ■ SAPinst performs the initial data import. ■ SAPinst configures the SLD bridge. For more information about how to perform these steps manually, see the documentation Post Installation Guide – System Landscape Directory of SAP NetWeaver 7.0 at http://service.sap.com/installNW70 Installation Configuration .
More Information

■ For more information about how to configure the SLD and about how to work with it, see the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management System Landscape Directory . ■ For more information about security and the role concept in the SLD, see the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Administrator’s Guide SAP NetWeaver Security Guide Security Aspects for System Management Security Guide for the SAP System Landscape Directory . ■ For more information about the SLD, see http://www.sdn.sap.com/irj/sdn/nw-sld.

6.17.2 Initial Technical Configuration for Development Infrastructure (DI)
SAPinst automatically performs some initial technical configuration steps for usage type Development Infrastructure (DI) during the installation. However, you might have to perform these steps manually if: ■ You have installed usage type DI as an additional usage type to an existing SAP system as described in Installation of Additional Software Units or Usage Types in an Existing SAP System [page 144]. ■ You want to change existing parameters or if you want to set additional parameters.
Features

SAPinst performs the following steps: ■ SAPinst creates the following NWDI users:

162/182

PUBLIC

2009-05-04

6 6.17

Additional Information Usage Type-Specific Initial Technical Configuration

● NWDI_ADM ● NWDI_DEV ● NWDI_CMSADM For more information about these NWDI users, see the table NWDI Users in Ensuring User Security [page 103]. ■ SAPinst creates the following roles: ● NWDI.Administrator ● NWDI.Developer ■ SAPinst adds the following actions to the role NWDI.Administrator: ● CBS.Administrator ● sap.com_com.sap.lcr.LcrInstanceWriterAll ■ SAPinst adds the following actions to the role NWDI.DEVELOPER: ● CBS.Developer ● CMS.Display ● CMS.ExportOwn ● sap.com_com.sap.lcr.LcrInstanceWriterNR ■ SAPinst creates the following groups: ● NWDI.Administrators ● NWDI.Developers SAPinst assigns the security role LcrInstanceWriterAll of the component sap.com/ com.sap.lcr*sld to the group NWDI.Administrators. SAPinst assigns the security role LcrInstanceWriterNR of the component sap.com/ com.sap.lcr*sld to the group NWDI.Developers. SAPinst assigns the role NWDI.Administrator to the group NWDI.Administrators. SAPinst assigns the role NWDI.Developer to the group NWDI.Developers. SAPinst assigns the group NWDI.Administrators to the user NWDI_ADM. SAPinst assigns the group NWDI.Developers to the user NWDI_DEV. SAPinst assigns the group NWDI.Administrators to the user NWDI_CMSADM.

■ ■ ■ ■ ■ ■ ■

More Information

For more information about how to perform these steps manually, see the SAP Library at: ■ http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Developing, Configuring, and Adapting Applications Post Installation Steps of Usage Type DI Setting Up Privileges, Roles and Groups ■ http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management Identity Management of the Application Server Java Administration of Users and Roles Managing Users, Groups, and Roles .

2009-05-04

PUBLIC

163/182

6 6.17

Additional Information Usage Type-Specific Initial Technical Configuration

6.17.3 Initial Technical Configuration for the Portal (Usage Types EPC and EP)
This section applies when you install usage type EPC only and when you install it together with usage type EP. SAPinst automatically performs some initial technical configuration steps for the usage types EPC and EP during the installation. However, you might have to perform these steps manually if: ■ You have installed usage type EPC or EPC and EP as an additional usage type to an existing SAP system as described in Installation of Additional Software Units or Usage Types in an Existing SAP System [page 144]. ■ You want to change existing parameters or if you want to set additional parameters.
Procedure

SAPinst performs the following steps: ■ SAPinst copies the CMS_MAPPING Properties file. ■ SAPinst renames the InitialPermissions.xml.template file to initialPermissions.xml. ■ SAPinst renames the initialPermissionsKMC.xml.template file to initialPermissionsKMC.xml.
Proceed as follows to copy CMS_MAPPING properties

1.

Change to the following source directory
/usr/sap/<sapsid>/<instance_name>/j2ee/cluster/server<x>/apps/sap.com/irj/ servlet_jsp/irj/root/WEB-INF/portal/system/pcd/Migration/mapping/

2.

Copy filecms_mapping.properties from the source directory to the following target directory: /usr/sap/<sapsid>/SYS/global/pcd/Migration/mapping/.
NOTE

If the target directory does not exist, you have to create it as well.
Proceed as follows to rename InitialPermissions.xml.template

1.

Go to directory
/usr/sap/<sapsid>/<instance_name>/j2ee/cluster/server<x>/apps/sap.com/irj/ servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl.

2.

Rename file initialPermissions.xml.template to initialPermissions.xml.

Renaming initialPermissionsKMC.xml.template

1.

Go to directory
/usr/sap/<sapsid>/<instance_name>/j2ee/cluster/server<x>/apps/sap.com/irj/ servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl

2.

Rename file initialPermissionsKMC.xml.template to initialPermissionsKMC.xml.

164/182

PUBLIC

2009-05-04

6 6.17

Additional Information Usage Type-Specific Initial Technical Configuration

6.17.4 Initial Technical Configuration for BI Java
SAPinst automatically performs BI Java-specific initial technical configuration steps during the installation. However, you might have to perform some of these steps manually if: ■ You upgraded your SAP system to the current release. ■ You have installed usage type BI Java as an additional usage type to an existing SAP system as described in Installation of Additional Software Units or Usage Types in an Existing SAP System [page 144]. The following steps might be affected: ■ Configure BI Java Information Broadcasting [page 165] ■ Process Chains: Transport texts for alert category [page 166] ■ Rename initialPermissionsBI.xml.template [page 166]

6.17.4.1 Configuring BI Java Information Broadcasting
Procedure

For the configuration of the BI Information Broadcasting you need to perform the following steps in your ABAP system: 1. Call transaction SPRO and perform the following steps: 1. Settings for Information Broadcasting: Go to SAP NetWeaver Business Intelligence Reporting-relevant Settings Settings for Information Broadcasting 2. Destinations for Web Dynpro ALV: Go to SAP NetWeaver Application Server Web Dynpro for ABAP Set-Up Printing for Web Dynpro ABAP ALV ■ Create RFC destination in the SAP NetWeaver Portal ■ Create RFC destination to the SAP NetWeaver Portal ■ Set-Up Web Service destination for the Adobe Document Services 2. Installation of BI Content: Call transaction RSTCO_ADMIN to check whether the installation has been carried out successfully. If the installation status is red, restart the installation by calling transaction RSTCO_ADMIN again. Check the installation log if you need further assistance or information. For more information, see SAP Note 834280.
NOTE

For the installation of SAP NetWeaver 7.0 BI Content Add-On 2 or higher on the AS ABAP system, see SAP Note 847019.

2009-05-04

PUBLIC

165/182

6 6.18

Additional Information Heterogeneous SAP System Installation

6.17.4.2 Process Chains: Transporting Texts for the Alert Category
Alerts can be triggered and sent for BI process chains that contain errors. Defining the alert categories is necessary for this purpose. Alert category BWAC_PROCESS_CHAIN_FRAMEWORK is returned for errors in background processing of process chains. This category has set texts that are not transported when the alert category is transported.
Procedure

To manually transport the texts, see SAP Note 601619.

6.17.4.3 Renaming initialPermissionsBI.xml.template
If SAPinst does not rename the initialPermissionsBI.xml.template file automatically, you need to rename it yourself.
Procedure

1.

Go to directory
/usr/sap/<sapsid>/JCxx/j2ee/cluster/server<x>/apps/sap.com/irj/ servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl

2.

Rename file initialPermissionsBI.xml.template to initialPermissionsBI.xml.

6.18 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 information on ■ supported combinations of operating systems and database systems, ■ how to install an application server on Windows in a heterogeneous (UNIX) SAP system environment, ■ heterogeneous SAP system landscapes with different UNIX operating systems.

6.19 Troubleshooting
The following sections describe the steps that you need to perform manually if SAPinst fails: ■ Troubleshooting with SAPinst [page 167]

166/182

PUBLIC

2009-05-04

6 6.19

Additional Information Troubleshooting
Only valid for: Enterprise Portal (EP);EP Core (EPC) |

Troubleshooting for Portal Installation [page 167]
End of: Enterprise Portal (EP);EP Core (EPC) |

6.19.1 Troubleshooting with SAPinst
This section tells you how to proceed when errors occur during the installation with SAPinst. If an error occurs, SAPinst: ■ Stops the installation. ■ Displays a dialog informing you about the error.
Procedure

1. 2.

3.

4.

To view the log file, choose View Logs. If an error occurs during the Define Parameters or Execute phase, do either of the following: ■ Try to solve the problem ■ Abort the installation by choosing Cancel in the SAPinst menu. For more information, see Interrupted Installation with SAPinst [page 139]. ■ After resolving the problem, you can 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. ■ If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current <user_home> directory. ■ If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as described in Starting SAPinst GUI Separately [page 142]. ■ 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. Ignore error messages such as the following in the SDM logs:
Error: <SCA name>: Location of software component '<SCA name>' / <SCA vendor>' / '<SCA location>' / '<SCA counter> ' unknown./ Error: <SCA name>: system component version store not updated.

For more information, see SAP Note 828978.
Only valid for: Enterprise Portal (EP);EP Core (EPC) |

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

2009-05-04

PUBLIC

167/182

6 6.19

Additional Information Troubleshooting

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: ■ ■ ■ ■
/usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/server0/ apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment /usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/server0/ apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd /usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/server0/ apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent /usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/server0/ apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/ pcdContent/no_overwrite

■ ■ ■ ■

/usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/cluster/server0/ apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/cluster/server0/ apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/cluster/server0/ apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/cluster/server0/ apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/ pcdContent/no_overwrite

■ ■ ■ ■

<drive>:\usr\sap\<SAPSID>\JC<instance_number>\j2ee\cluster\server0\ apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment <drive>:\usr\sap\<SAPSID>\JC<instance_number>\j2ee\cluster\server0\ apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd <drive>:\usr\sap\<SAPSID>\JC<instance_number>\j2ee\cluster\server0\ apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcdContent <drive>:\usr\sap\<SAPSID>\JC<instance_number>\j2ee\cluster\server0\ apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcdContent \no_overwrite

■ ■

<drive>:\usr\sap\<SAPSID>\DVEBMGS<instance_number>\j2ee\cluster\server0\ apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment <drive>:\usr\sap\<SAPSID>\DVEBMGS<instance_number>\j2ee\cluster\server0\ apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd

168/182

PUBLIC

2009-05-04

6 6.20

Additional Information Deleting an SAP System

■ ■

<drive>:\usr\sap\<SAPSID>\DVEBMGS<instance_number>\j2ee\cluster\server0\ apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcdContent <drive>:\usr\sap\<SAPSID>\DVEBMGS<instance_number>\j2ee\cluster\server0\ 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: ■ If error and log files do not appear, the portal installation has been completed successfully and you can continue. ■ Rename the *.err files: 1. Remove the err extension; so the extensions of the files become *.ept or *.par. 2. Restart the J2EE Engine, using the commands stopsap and startsap, to change the files to *.bak.

End of: Enterprise Portal (EP);EP Core (EPC) |

6.20 Deleting an SAP System
This section describes how to delete a single instance, a standalone engine, or a complete SAP system with the Uninstall option of SAPinst.
NOTE

We recommend that you delete an SAP system with SAPinst. However, you can also delete an SAP system manually. For more information, see SAP Note 1229586.
Prerequisites

■ You are logged on as user root. ■ If the saposcol process on the host you are working on has been started from the SAP system you want to delete, stop it using the command saposcol -k. If there are other SAP systems on the host, log on as user <sapsid>adm of the other SAP system and start saposcol from there using the command saposcol -l.
Procedure

1.

2.

Start SAPinst [page 88] and on the Welcome screen, choose: <Your SAP product> Software Life-Cycle Options Uninstall Uninstall System / Standalone Engine / Optional Standalone Unit Follow the instructions in the SAPinst input dialogs.
NOTE

For more information about the input parameters, place the cursor on the relevant field and press F1 in SAPinst.

2009-05-04

PUBLIC

169/182

6 6.20

Additional Information Deleting an SAP System

SAPinst first asks you which SAP instances you want to delete. Make sure that you delete the SAP instances in the order as described below.
CAUTION

SAPinst only stops local instances automatically. Before you delete the database instance of a distributed system make sure that 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. ■ If you want to delete a central system (all instances reside on the same host), you can do this in one SAPinst run. 1. Delete the SAP system. 2. To delete the database instance or one or more database schemas, choose one of the following options:
Options Remarks

Select this option if you want to delete the database content, including all database schemas, all tablespaces and their corresponding data files. Select the database schema that you want to delete Select this option in one of the following situations: ● 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 ● You want to delete the Java part of an ABAP+Java system. Drop database
NOTE

If you want to delete a schema in an MCOD environment using SAPinst, no DB2–specific file systems are deleted. Make sure that you manually delete/db2/<sapsid>/sapdata<1–n>.

■ 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. Dialog instances, if there are any 2. Central instance 3. Database instance To delete the database instance or one or more database schemas, choose one of the following options:
Options Remarks

Select this option if you want to delete the database content, including all database schemas, all tablespaces and their corresponding data files. Select the database schema that you want to delete Select this option in one of the following situations: Drop database

170/182

PUBLIC

2009-05-04

6 6.21

Additional Information Deleting a Diagnostics Agent Options Remarks

● 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 ● You want to delete the Java part of an ABAP+Java system.
NOTE

If you want to delete a schema in an MCOD environment using SAPinst, no DB2–specific file systems are deleted. Make sure that you manually delete/db2/<sapsid>/sapdata<1–n>.

3. 4.

■ Java Central services instance (SCS) ■ The relevant directory structure on the global host If required, you can delete the directory /usr/sap/trans and its content manually. SAPinst does not delete /usr/sap/trans because it might be shared. 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.

6.21 Deleting a Diagnostics Agent
This procedure tells you how to delete the Diagnostics Agent with SAPinst.
NOTE

We recommend that you delete a Diagnostics Agent with SAPinst. However, you can also delete a Diagnostics Agent manually. For more information, see SAP Note1229586.
Prerequisites

You are logged on as user root.
Procedure

1. 2.

3.

Start SAPinst [page 88]. On the Welcome screen, choose: <Your SAP product> Software Life-Cycle Options Uninstall Uninstall – Solution Manager Diagnostics Agent Follow the instructions in the SAPinst input dialogs.
NOTE

4.

For more information about the input parameters, place the cursor on the relevant field and press F1 in SAPinst. After the uninstall with SAPinst has finished successfully, you still have to manually delete the <smdsid>adm user.

2009-05-04

PUBLIC

171/182

6 6.22

Additional Information Deleting the Database Instance and Database Software Manually (Optional)

6.22 Deleting the Database Instance and Database Software Manually (Optional) 6.22.1 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. You delete a database schema in one of the following situations: ■ 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. ■ You want to delete the Java part of an ABAP+Java system.
Prerequisites

■ Make sure that any instance that uses the schema is stopped. ■ 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' “ | find “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' “ | find “DROP” > drop_<sap_system_schema>_views.txt

4. 5. 6.

where <SAP_SYSTEM_SCHEMA> is the connect user. Delete all tables by running the first script by entering the following command:
db2 —tvs drop_<sap_system_schema>_tables.txt

Delete all views by running the second script by entering the following command:
db2 —tvf drop_<sap_system_schema>_views.txt

Check for special DB2 functions by entering the following command:
db2 "select FUNCNAME from SYSCAT.FUNCTIONS WHERE funcschema='<SAP_SYSTEM_SCHEMA>'" <DB2_FUNCTION>

7.

If DB2 special functions exist, delete them using the following command:
db2 drop function <DB2_FUNCTION>

172/182

PUBLIC

2009-05-04

6 6.22

Additional Information Deleting the Database Instance and Database Software Manually (Optional)

8. 9.

Drop the database schema by entering the following command:
db2 drop schema <SAP_SYSTEM_SCHEMA> restrict

Delete all tablespaces by performing the following steps: 1. To see an overview, list all tablespaces by entering the following command:
db2 list tablespaces

2. 3. 4.

In an ABAP-only or Java-only system, 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>

6.22.2 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.
CAUTION

Do not delete the database in one of the following situations: ■ You are running multiple components on one database (MCOD) and you only want to delete one or more of your components but not the complete system ■ You only want to delete the Java part of an SAP system (ABAP+Java or Java Add-In). In this case you delete the corresponding database schema as described in Deleting a Database Schema Manually [page 172].
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. 4. 2. 3.

To delete the database <DBSID>, enter the following command:
db2 drop database <DBSID>

To stop the database, enter the following command:
db2stop

To delete the DB2 instance, log on as user root. Enter the following command:
%DB2PATH%/instance/db2idrop db2<dbsid>

2009-05-04

PUBLIC

173/182

6 6.22

Additional Information Deleting the Database Instance and Database Software Manually (Optional)

4. 5. 6.

Delete user db2<dbsid>. To remove the home directory of db2<dbsid> and all subdirectories, enter the following command.
rm —rf /db2/db2<dbsid>

Unmount and delete the following file systems:
/db2/<DBSID>/log_dir /db2/<DBSID>/db2dump /db2/<SAPSID>/sapdata<n> /db2/<DBSID>/saptemp1 /db2/<DBSID>

7. 8. 9.

Delete user sap<sapsid>, its home directory, and all subdirectories of this directory. Delete user sap<sapsid>db, its home directory, and all subdirectories of this directory. If they are empty and not longer required, delete the groups db<dbsid>adm, db<dbsid>mnt, db<dbsid>ctl. 10. Delete the /etc/services entries for sapdb2<DBSID>. In other words, delete the lines starting with sapdb2<DBSID>.

6.22.3 Deleting the DB2 Software Installation
Procedure

1.

Check that no 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 173]. Log on as user with root authority. Enter the following command:
%DB2PATH%/install/db2_deinstall -a

174/182

PUBLIC

2009-05-04

A A.1

Appendix Online Information from SAP

A Appendix

A.1 Online Information from SAP
More information is available online as follows.
Documentation Description Internet Address Title

Master Guide for SAP http://service.sap.com/installNW70 NetWeaver 7.0 Technical Infrastructure http://service.sap.com/installNW70 Guide for SAP NetWeaver 7.0 Master Guide SAP Solution http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 Manager 7.0 List of media for http://service.sap.com/installNW70 installation or upgrade for SAP NetWeaver 7.0 including Enhancement Package 1 Database administration http://service.sap.com/instguidesnw70 Operations Database-Specific Guides guide for SAP systems on IBM DB2 for Linux, UNIX, and Windows
NOTE

Master Guide – SAP NetWeaver 7.0 Technical Infrastructure Guide – SAP NetWeaver 7.0 Master Guide – SAP Solution Manager 7.0 Media List – SAP NetWeaver 7.0 including Enhancement Package 1

Database Administration Guide – SAP on IBM DB2 for Linux, UNIX, and Windows

This document applies to DB2 Version 9.1 and Version 9.5. http://service.sap.com/instguides SAP Installation of SAP Components SAP Solution Manager Release 7.0 Solution Manager 7.0 http://service.sap.com/instguides SAP Configuration of SAP Components SAP Solution Manager Release 7.0 Solution Manager 7.0 Patching of SAP NetWeaver http://service.sap.com/maintenanceNW70 SPS <current stack> Support Package Stack Guide – 7.0 scenarios SPS <current stack> Upgrade to SAP NetWeaver http://service.sap.com/upgradenw70 7.0 including Enhancement Package 1 Installation of SAP http://service.sap.com/installNW70 Installation Installation — Clients Installation – NetWeaver Developer SAP Developer Workplace Workplace

Installation Guide – SAP Solution Manager 7.0 on <OS>: <Database> Configuration Guide – SAP Solution Manager 7.0 as of <current stack> Support Package Stack Guide – SAP NetWeaver 7.0 SPS <current stack> Upgrade Master Guide – SAP NetWeaver 7.0 Installation Guide – Developer Workplace for SAP NetWeaver

2009-05-04

PUBLIC

175/182

A A.1

Appendix Online Information from SAP Internet Address Title

Description

Installation of SAP http://service.sap.com/installNW70 Installation Installation — Clients Installation – NetWeaver Developer SAP NetWeaver Developer Studio Studio Installation of the System http://service.sap.com/installNW70 Landscape Directory (SLD) Configuration Post-Installation Guide – SLD of SAP NetWeaver 7.0 Installation of Web http://service.sap.com/installNW70 Installation – Standalone Engines Installation — Web Dispatcher Dispatcher on <platform> Front End installation http://service.sap.com/installNW70 Installation – Clients Installation – SAP Front End <Release> Homogeneous and http://service.sap.com/installNW70 Installation – SAP NetWeaver Systems System Copy heterogeneous system copy for SAP systems based for SAP Systems Based on <Release> <Technology> on NetWeaver 7.0 http://help.sap.com/nw70 SAP NetWeaver SAP NetWeaver Problem 7.0 Library (including Enhancement Package 1) English Analysis Guide SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG)
General Quick Links Description Internet Address
http://help.sap.com http://help.sap.com/nw70

SAP NetWeaver Developer Studio — Standalone Installation Guide Post-Installation Guide – System Landscape Directory of SAP NetWeaver 7.0 Installation Guide – Web Dispatcher on <platform> – For SAP Systems Based on SAP NetWeaver 7.0 (2004s) SAP Front End Installation Guide This guide is also available on the Presentation DVD. System Copy Guide — System Copy for SAP Systems based on SAP NetWeaver <Release> <Technology> SAP NetWeaver Problem Analysis Guide (PAG)

SAP Help Portal SAP NetWeaver Library in SAP Help Portal SAP Notes SAP Notes for SAP NetWeaver 7.0 installation Forums, blogs, and general information related to all of the supported databases and operating system platforms Product Availability Matrix (PAM) for supported operating system releases Release notes Unicode SAP systems and their availability System sizing (Quick Sizer tool) SAP NetWeaver capabilities Life-cycle management for SAP NetWeaver

http://service.sap.com/notes http://service.sap.com/sapnotesnw70

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

176/182

PUBLIC

2009-05-04

A A.2

Appendix Online Information from IBM Internet Address
http://sdn.sap.com/irj/sdn/landscapedesign

Description

Landscape design for SAP NetWeaver Application management for SAP NetWeaver High Availability System Landscape Directory Software logistics for SAP NetWeaver SAP NetWeaver operations SAP NetWeaver Development Infrastructure Security for SAP NetWeaver Information on SAP Support Package Stacks SAP Solution Manager Maintenance Optimizer End-to-End Root Cause Analysis

http://sdn.sap.com/irj/sdn/applicationmanagement

http://sdn.sap.com/irj/sdn/ha http://sdn.sap.com/irj/sdn/nw-sld http://sdn.sap.com/irj/sdn/softwarelogistics

http://sdn.sap.com/irj/sdn/operations http://sdn.sap.com/irj/sdn/nw-di

http://sdn.sap.com/irj/sdn/security http://service.sap.com/sp-stacks

http://service.sap.com/solutionmanager http://service.sap.com/solman-mopz http://service.sap.com/diagnostics

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 database.
IBM Manuals Database Version Internet Address
http://www.ibm.com/software/data/db2/udb/support/manualsv9.html http://www-1.ibm.com/support/docview.wss?rs=71&uid=swg27009727

DB2 V9.1 DB2 V9.5

IBM DB2 Information Center Database Version Internet Address
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/

DB2 V9.1 DB2 V9.5
NOTE

The IBM DB2 Information Center also contains a detailed glossary explaining all IBM-specific terms.
More Information

For more information about web sites that contain important DB2-related documentation, see SAP Note 690471.

2009-05-04

PUBLIC

177/182

Typographic Conventions

Example
<Example>

Description

Example Example Example
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 Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. ■ Cross-references to other documentation or published works ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE Keys on the keyboard

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

178/182

PUBLIC

2009-05-04

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 2009 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. 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 is a registered trademark of Oracle Corporation. 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. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 in several other countries all over the world. 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 SAP’s Support Services and may not be modified or altered in any way.

2009-05-04

PUBLIC

179/182

Legal Software Terms 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 was developed using ANTLR. 2. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems, Applications, Products in Data Processing Dietmar-Hopp-Allee 16 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: ■ The conditions indicated in the above permissions notice are met; ■ 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 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 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. Silicon Graphics 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 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. 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.

180/182

PUBLIC

2009-05-04

3.

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. 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 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: https://service.sap.com/instguides

2009-05-04

PUBLIC

181/182

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 2009 SAP AG. All rights reserved. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Sign up to vote on this title
UsefulNot useful