SAP Solution Manager 4.0 SR3 On Linux MaxDB

PUBLIC
Installation Guide
SAP Solution Manager

4.0 SR3 on Linux :
MaxDB
Target Audience
n Technology consultants
n System administrators
Document version: 1.0 ‒ 08/27/2007

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 8/27/2007 Initial Version
2/140 PUBLIC 08/27/2007

Table of Contents
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 9
1.3 Information Available on SAP Service Marketplace . . . . . . . . . . 10
1.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 12
Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Basic System Variants for SAP Solution Manager . . . . . . . . . . . 13
2.2 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . 16
2.3 MaxDB System Configuration . . . . . . . . . . . . . . . . . . 18
2.4 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 20
2.5 Running Adobe Document Services on Non-Supported Platforms . . . . 26
2.6 High Availability: Planning the Switchover Cluster . . . . . . . . . . 27
Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 31
3.1 High Availability: Switchover Preparations . . . . . . . . . . . . . 32
3.1.1 Preparing for Switchover . . . . . . . . . . . . . . . . . . . . 32
3.1.2 Setting Up File Systems . . . . . . . . . . . . . . . . . . . . 34
3.1.3 Configuring Network File System . . . . . . . . . . . . . . . . 35
3.2 Hardware and Software Requirements . . . . . . . . . . . . . . . 37
3.2.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 38
3.2.2 Requirements for Linux . . . . . . . . . . . . . . . . . . . . 39
3.2.3 Requirements for a Central System . . . . . . . . . . . . . . . . 41
3.2.4 Requirements for a Distributed or a High Availability System . . . . . . 42
3.2.4.1 Requirements for the Central Services Instance . . . . . . . . . . . 42
3.2.4.2 Requirements for the Central Instance . . . . . . . . . . . . . . 43
3.2.4.3 Requirements for the Database Instance . . . . . . . . . . . . . . 44
3.2.5 Requirements for a Dialog Instance . . . . . . . . . . . . . . . . 44
3.2.6 Checking and Modifying the Linux Kernel . . . . . . . . . . . . . 45
3.2.7 Setting up Swap Space for Linux . . . . . . . . . . . . . . . . . 45
3.3 Creating Operating System Users . . . . . . . . . . . . . . . . 46
3.3.1 Network Information Service . . . . . . . . . . . . . . . . . . 46
3.3.2 Creating Operating System Users and Groups . . . . . . . . . . . . 47
3.3.3 Creating Operating System Users and Groups Manually . . . . . . . . 48
3.3.4 Creating Linux Groups and Users (Optional) . . . . . . . . . . . . 49
08/27/2007 PUBLIC 3/140

3.4 Setting Up File Systems and Raw Devices . . . . . . . . . . . . . . 50
3.4.1 Setting Up File Systems . . . . . . . . . . . . . . . . . . . . 50
3.4.2 MaxDB File Systems . . . . . . . . . . . . . . . . . . . . . 55
3.4.3 Setting Up Standard File Systems and Raw Devices for Linux . . . . . . 55
3.5 Exporting and Mounting the Global Transport Directory . . . . . . . . 56
3.6 Exporting and Mounting Directories via NFS for Linux (Optional) . . . . 57
3.7 Installing the Front-End Software . . . . . . . . . . . . . . . . 59
3.8 Installing the Java Development Kit . . . . . . . . . . . . . . . . 59
3.9 Preparing and Mounting the Installation Media . . . . . . . . . . . 61
3.9.1 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 61
3.9.2 Downloading Installation DVDs from SAP Service Marketplace (Optional) . 63
3.9.3 Mounting a CD / DVD for Linux . . . . . . . . . . . . . . . . . 64
Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 65
4.1 Performing a High-Availability Installation . . . . . . . . . . . . . 65
4.2 Prerequisites before Starting SAPinst . . . . . . . . . . . . . . . 67
4.2.1 Prerequisites before Starting SAPinst: All Instances . . . . . . . . . . 67
4.2.2 Prerequisites before Starting SAPinst: Distributed Instances . . . . . . . 69
4.2.3 Prerequisites Before Starting SAPinst: High Availability . . . . . . . . . 70
4.3 Installing an SAP System Using SAPinst . . . . . . . . . . . . . . 70
4.3.1 Running SAPinst on UNIX . . . . . . . . . . . . . . . . . . . 70
4.3.2 Installing the Java Add-In for an Existing ABAP System (Optional) . . . . 76
4.3.3 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 78
4.3.4 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 79
4.3.5 Performing a Remote Installation with SAPinst (Optional) . . . . . . . 80
4.3.6 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 81
4.3.7 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 83
Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 85
5.1 Logging On to the Application Server . . . . . . . . . . . . . . . 86
5.2 Installing the SAP License . . . . . . . . . . . . . . . . . . . 87
5.3 Installing the SAP Online Documentation . . . . . . . . . . . . . 88
5.4 Configuring Remote Connection to SAP Support . . . . . . . . . . 88
5.5 Performing Initial ABAP Configuration . . . . . . . . . . . . . . 89
5.6 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 91
5.7 Performing a Full Installation Backup . . . . . . . . . . . . . . . 93
5.8 Post-Installation Steps for Adobe Document Services . . . . . . . . . 94
5.8.1 Assigning Roles to Users ADSUSER and ADS_AGENT . . . . . . . . . 94
5.8.2 Checking the IIOP Service and the Startup Properties . . . . . . . . . 95
5.8.3 Installation Check and Quick Tests for Adobe Document Services . . . . 96
5.9 High Availability: Post-Installation Steps . . . . . . . . . . . . . . 96
5.9.1 Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . 96
4/140 PUBLIC 08/27/2007

5.9.2 Taking Precautions for Transport . . . . . . . . . . . . . . . . 97
5.10 Installing Administration Tools for MaxDB . . . . . . . . . . . . . 98
5.11 Secure Sockets Layer Protocol for Database Server Communication . . . . 100
5.11.1 Installing the SAP Cryptographic Library . . . . . . . . . . . . . . 100
5.11.2 Generating the Personal Security Environment . . . . . . . . . . . 101
5.12 Backing Up the MaxDB Database . . . . . . . . . . . . . . . . . 104
5.13 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 104
5.14 Checking the SAP Java Documentation . . . . . . . . . . . . . . 107
5.15 Configuring SAP Solution Manager . . . . . . . . . . . . . . . . 108
Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 111

6.1 Installation of Multiple Components in One Database (Optional) . . . . . 111
6.2 Integration of LDAP Directory Services (Optional) . . . . . . . . . . 113
6.3 Starting and Stopping the SAP System . . . . . . . . . . . . . . . 116
6.3.1 Starting and Stopping the SAP System Using the SAP Management Console . 116
6.3.2 Starting and Stopping the SAP System Using startsap stopsap Scripts . . . . 120
6.4 Creating a User for LDAP Directory Access (Optional) . . . . . . . . . 123
6.5 Configuring User Management to Use an LDAP Directory (Optional) . . . 123
6.6 Initial Configuration of Adobe Document Services . . . . . . . . . . 124
6.7 Initial Configuration for the System Landscape Directory (SLD) . . . . . 124
6.8 Heterogeneous SAP System Installation . . . . . . . . . . . . . . 125
6.9 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 126
6.9.1 Running SAPinst to Delete an SAP System . . . . . . . . . . . . . 127
6.9.2 Deleting an SAP System Manually . . . . . . . . . . . . . . . . 128
6.9.2.1 Deleting an SAP Instance . . . . . . . . . . . . . . . . . . . 128
6.9.2.2 Deleting Installation Files, Directories, and Users on a Host . . . . . . . 129
6.9.2.3 Deleting the Java Part of an SAP System . . . . . . . . . . . . . . 130
6.9.2.4 Deleting the Java Database Schema . . . . . . . . . . . . . . . . 132
6.9.2.5 Deleting the Database Installation . . . . . . . . . . . . . . . . 133
6.10 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 133
6.10.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 134
08/27/2007 PUBLIC 5/140

6/140 PUBLIC 08/27/2007
1 Introduction
1 Introduction
This document explains how to install SAP Solution Manager 4.0 SR3 (support package stack (SPS) 12).
SAP Solution Manager 4.0 SR3 is installed as an SAP system based on AS ABAP and AS Java.
The part of the system that is based on AS Java is used for the functions of Solution Manager
Diagnostics.
For more information about SAP Solution Manager, see SAP Service Marketplace at
http://service.sap.com/solutionmanager.
SAP Solution Manager 4.0 SR3 (SAP Solution Manager) is based on SAP NetWeaver 7.0 SR2 technology.
For more information, see SAP Service Marketplace at https://service.sap.com/netweaver.
This document also explains how to install the Java Add-In for an existing SAP Solution Manager
ABAP system. For example, you have upgraded your SAP Solution Manager 3.1 or 3.2 system to SAP
Solution Manager 4.0 and want to use the functions of Solution Manager Diagnostics.
Make sure you have read the documentation Master Guide ‒ SAP Solution Manager 4.0 before you
start with this installation guide. The Master Guide is available on SAP Service Marketplace at
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 4.0 .
Constraints
You need to consider the following constraints before you start your installation:
n 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.
n SAP system installations should only be performed by SAP Technical Consultants who are
certified for your operating system, your database, and the SAP system that you are installing.
n 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 a SAP component or
perform a system copy using a downward-compatible database as follows:
l Install the component with the old proposed database version.
l Upgrade the old database version to the downward-compatible new version.
08/27/2007 PUBLIC 7/140

1 Introduction
1.1 New Features
1.1 New Features
You can find the new features of SAP Solution Manager 4.0 SR3 functions on SAP Service Marketplace
at http://service.sap.com/solutionmanager.
The following tables provide an overview of the new features that are related to the installation:
SAP System Installation
Area Description
SAPinst As of SAP NetWeaver 7.0, SAPinst has the following new features:
n You can check the prerequisites for your SAP system installation with the
Prerequisite Checker [page 38].
n You can install a central system in one of two modes:
l Typical Mode
If you choose Typical, your SAP system is installed with default settings. As
a result, you only have to respond to a small selection of prompts. If you
want to change any of the default settings, you can do so on the parameter
summary screen at the end of the installation.
l Custom Mode
If you choose Custom, you must manually enter all installation parameters.
You can change your values on the parameter summary screen at the end of
the installation.
n You can uninstall an SAP system or an SAP component with the SAPinst service
Uninstall ‒ System / Standalone Engines / Optional Standalone Unit.
n You can install the Java Add-In for an existing ABAP system. This means that you
run SAPinst to execute the following:
l Install the central services instance (SCS)
l Add the Java database schema to the existing ABAP database instance.
l Add the Java central instance with usage types to the existing ABAP central
instance.
Note
You cannot install the Java Add-In for the dialog instance(s) of the existing
ABAP system. Instead, you have to install an ABAP+Java dialog instance(s).
n The sapinst group ID must be the secondary group of the users root and
<sapsid>adm. For more information, see Creating Operating System Users and Groups
Manually [page 47].
n You can install SAP NetWeaver as a high-availability (HA) system.
n You can change the default names of the Java users J2EE_ADMIN, J2EE_GUEST and
SAPJSF during the input phase of the installation.
n You assign one Master Password to all users created by SAPinst. This password is
used for all user accounts and for the secure store key phrase.
n SAPinst fills in most of the input parameter fields with default values.
If required, you can change the default values on the Parameter Summary screen
before you start the actual installation.
n You no longer have to manually activate sapcpe.
The kernel is replicated automatically from
/usr/sap/<SAPSID>/SYS/exe/run/DIR_CT_RUN to
8/140 PUBLIC 08/27/2007

1 Introduction
1.2 SAP Notes for the Installation
Area Description
/usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each
SAP system instance.
For more information, see Setting Up File Systems [page 50].
Installation DVDs You start the installation from a single Installation Master DVD.
SAP NetWeaver SAP NetWeaver Administrator is a brand new solution for monitoring and
Administrator administering Java systems and their applications.
For more information, see the SAP NetWeaver Master Guide and SAP Service
Marketplace at http://service.sap.com/nwa.
Operating Systems
Area Description
Support of Operating See the Product Availability Matrix (PAM) on SAP Service Marketplace at
Systems https://service.sap.com/pam
Documentation
Area Description
SAP Notes You can now access SAP Notes directly in SAP Service Marketplace from your
PDF. Place the cursor on the SAP Note “<number>” and double-click. A
separate browser windows opens and the SAP Note is displayed.
Standalone Gateway The installation of a standalone gateway is now covered in a dedicated
Installation installation guide, available at http://service.sap.com/installNW70
Installation - Standalone Engines & Clients Installation Guide - Gateway on <platform>
Links in PDF files You can use the new links in the PDF files of the guides as follows:
n Click on the section headings such as New Features to jump back to the
table of contents at the beginning of the guide.
n Click on an internet link such as http://service.sap.com to jump to
the corresponding internet page.
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 in the SAP
Service Marketplace at https://service.sap.com/notes.
08/27/2007 PUBLIC 9/140

1 Introduction
1.3 Information Available on SAP Service Marketplace
SAP Notes for the Installation Title Description

1071445 SAP Solution Manager 4.0 SR3 Central installation note for SAP
Installation Solution Manager 4.0 SR3.
855498 Installation Prerequisite Checker SAP Software on UNIX and
Windows: Checking OS
Dependencies
More information is available as follows on SAP Service Marketplace.
Note
Before you continue to read this installation guide, you must have read the Master Guide. Having
finished the installation and the required post-installation steps, you have to follow the instructions
in the configuration guide. The configuration guide will also point you to further documentation
that might be relevant for you.
Documentation
Description Internet Address Title

List of media for http://service.sap.com/instguides SAP Media List ‒ SAP Solution Manager
installation or upgrade Components SAP Solution Manager Release 4.0 4.0 SR3
for SAP Solution
Manager 4.0 SR3
Master Guide SAP http://service.sap.com/instguides SAP Master Guide ‒ SAP Solution
Solution Manager 4.0 Components SAP Solution Manager Release 4.0 Manager 4.0
Upgrade to SAP http://service.sap.com/instguides SAP Upgrade Guide ‒ SAP Solution
Solution Manager 4.0 Components SAP Solution Manager Release 4.0 Manager 4.0 <OS> <Database>
FAQ on upgrade to SAP http://service.sap.com/instguides SAP FAQ on Upgrade of SAP Solution
Solution Manager 4.0 Components SAP Solution Manager Release 4.0 Manager Release 3.1/3.2 to 4.0
Sizing Guide SAP http://service.sap.com/instguides SAP Sizing Guide ‒ Sizing SAP Solution
Solution Manager 4.0 Components SAP Solution Manager Release 4.0 Manager 4.0
Configuration of SAP http://service.sap.com/instguides SAP Configuration Guide ‒ SAP Solution
Solution Manager Components SAP Solution Manager Release 4.0 Manager 4.0 as of SP<SP level of
your SAP Solution Manager system>
Front End installation http://service.sap.com/installNW70 Front End Installation Guide (this guide
Installation - Clients is also available on the Presentation
DVD)
10/140 PUBLIC 08/27/2007

1 Introduction
Description Internet Address Title

Homogeneous and http://service.sap.com/installNW70 Homogeneous and Heterogeneous
heterogeneous system Installation - SAP NetWeaver Systems System Copy for SAP Systems based on
copy for SAP systems SAP NetWeaver 2004s
based on NetWeaver
2004s
Migration Guide http://service.sap.com/instguides SAP Migration Guide for Solution Manager
Solution Manager Components SAP Solution Manager Release 4.0 Diagnostics SAP NetWeaver 04s SP
Diagnostics Stack <current stack>
Advanced Setup Guide http://service.sap.com/instguides SAP Advanced Diagnostics Setup Guide as
for Solution Manager Components SAP Solution Manager Release 4.0 of <current SP>
Diagnostics 7.0 (04s)
System Landscape http://service.sap.com/installNW70 Post-Installation Guide - System
Directory Installation Configuration Landscape Directory of SAP
NetWeaver 7.0 (04s)
SAP NetWeaver http://help.sap.com/nw70 SAP NetWeaver SAP NetWeaver Problem Analysis
Problem Analysis Guide Library SAP NetWeaver by Key Capability Solution Life Guide (PAG)
(PAG) Cycle Management by Key Capability SAP NetWeaver
Problem Analysis Guide (PAG)
General Quick Links
Description Internet Address

SAP Help Portal http://help.sap.com
SAP NetWeaver Library in SAP http://help.sap.com/nw70

Help Portal
SAP Notes http://service.sap.com/notes
Released platforms and operating http://service.sap.com/platforms

systems
Unicode SAP systems and their http://service.sap.com/unicode
availability
System sizing (Quick Sizer tool) http://service.sap.com/sizing
High availability http://service.sap.com/ha
Security http://service.sap.com/security
Information on SAP Support http://service.sap.com/sp-stacks

Package Stacks
System Landscape Directory http://service.sap.com/sld
SAP Solution Manager http://service.sap.com/solutionmanager
SAP Solution Support http://service.sap.com/ssep

Enablement Package
08/27/2007 PUBLIC 11/140

1 Introduction
1.4 Naming Conventions
1.4 Naming Conventions
Note
As of March 2007, SAP updated its release naming strategy to remove year designations. As a result,
the product previously named SAP NetWeaver 2004s has been renamed to SAP NetWeaver 7.0. Be
aware that this release may be referred to in several ways as SAP transitions to the new name. These
names may include: SAP NetWeaver 2004s, SAP NetWeaver 7.0 (2004s), or SAP NetWeaver 7.0.
In this documentation, the following naming conventions apply:
Terminology
n SAP system refers to SAP Solution Manager 4.0 SR3 system.

n ABAP+Java system or system based on AS ABAP and AS Java refers to the two stacks (ABAP and Java) of
SAP Solution Manager 4.0 SR3.
n Java Add-In refers to the Java Add-In for an existing SAP Solution Manager ABAP system. For example,
you have upgraded your SAP Solution Manager 3.1 or 3.2 system to SAP Solution Manager 4.0 and
want to use the functions of Solution Manager Diagnostics.
Variables
Variables Description
<SAPSID> SAP system ID in uppercase letters
<sapsid> SAP system ID in lowercase letters
<DBSID> Database ID in uppercase letters
<dbsid> Database ID in lowercase letters
<host_name> Name of the corresponding host
<user_home> Home directory of the user performing the installation.
<INSTDIR> Installation directory for the SAP system
<DVD_DIR> Directory on which a DVD is mounted
<OS> Operating system name within a path
<SCHEMA_ID> Database schema ID
The following example shows how the variables are used:
Example
Log on as user <sapsid>adm and change to the directory /usr/sap/<SAPSID>.
If your SAP system ID is C11, log on as user c11adm and change to the directory
/usr/sap/C11.
12/140 PUBLIC 08/27/2007

2 Planning
2 Planning
This section tells you how to plan the installation of your SAP system.
You have to complete the following planning activities:
1. You choose your basic system variant for SAP Solution Manager [page 13].
2. You plan how to distribute the instances to hosts [page 16].
3. You plan your system configuration [page 18].
4. You identify basic SAP system parameters [page 20].
5. Solution Manager Diagnostics requires that your complete Solution Manager system is a Unicode
system [page ].
6. If you want to use Adobe Document Services (ADS), you check what you have to do in case your platform is
not supported for ADS [page 26].
Only valid for: HA (UNIX)
7. You plan the switchover cluster [page 27] for a high-availability (HA) system.
End of: HA (UNIX)
The following planning activity is optional:

n Installation of Multiple Components in One Database (MCOD) [page 111]
Caution
This step does not apply to the installation of a Java Add-In to an existing ABAP system.
2.1 Basic System Variants for SAP Solution Manager
The following section provides information about the basic SAP system variants for SAP Solution
Manager and about the possibilities to distribute SAP instances within them
SAP Solution Manager is an ABAP+Java system.
An ABAP+Java System can be the result of
n an ABAP+Java installation
n a Java Add-In installation for an already existing ABAP system
Mandatory instances of an ABAP+Java system are the central instance, the central services instance,
and the database instance.
08/27/2007 PUBLIC 13/140

2 Planning
Note
The Java central services instance is named SCS instance.
The ABAP central services instance is named ASCS instance. The ASCS is only available for a high
availability installation.
You can then operate both the ABAP application server and the J2EE Engine on the SAP system.
Optionally, you can install one or more dialog instances, if required.
Note
Each instance can reside on a separate host.
Figure 1: Minimum System Distribution (Central System)
For a minimum system distribution, all instances reside on one host.
14/140 PUBLIC 08/27/2007

2 Planning
Figure 2: Maximum Distribution for a Distributed System
For a maximum system distribution, each instance resides on a separate host.

Figure 3: Maximum Distribution for a High-Availability System
End of: HA (UNIX)
08/27/2007 PUBLIC 15/140

2 Planning
2.2 How to Distribute Instances to Hosts
For a maximum system distribution, each instance resides on a separate host.

End of: HA (UNIX)
The following provides information on how you can distribute the SAP instances for the different SAP
system variants. You use SAPinst to install the SAP instances as a:
n Central system on a single host
You run SAPinst and install all instances on one host.
n As a distributed system on several hosts
The following figure shows how to distribute your instances on several hosts:
Figure 4: Distribution of Instances in an ABAP+Java System
Note
You can use the SAP transport host or the SAP global host as your central instance host.
You perform the following steps:

1. If you want to share the transport directory trans from another system, you have to mount it
from this system. Otherwise we recommend that you share the trans directory that will be
created during the installation of the primary application server instance (see below).
16/140 PUBLIC 08/27/2007

2 Planning
2. On the SAP global host, you run SAPinst and install the Java central services instance (SCS).
3. On the SAP global host, you run SAPinst and install the ABAP and Java central services
instances (ASCS and SCS).
End of: HA (UNIX)
4. On the SAP global host, you export the required file systems to the database and central
instance host.
5. On the database host, you mount the exported file systems from the SAP global host and
SAP transport host.
6. On the database host, you run SAPinst and install the database instance.
7. On the central instance host, you mount the exported file systems from the SAP global host
and SAP transport host.
8. On the central instance host, you run SAPinst and install the central instance.
9. If required, you can now install one to <n> dialog instances. The procedure is the same as
installing a central instance (replace “central instance” with “dialog instance” in the procedure).
Java Add-In for an Existing ABAP System

If you want to install the Java Add-In for an existing ABAP system, you proceed as follows on the
instance host(s) of the ABAP system:
n Central system on a single host
You run SAPinst and install the Java Add-In on one host.
n Distributed system on several hosts
The following figure shows how to distribute your instances on several hosts:
08/27/2007 PUBLIC 17/140

2 Planning
2.3 MaxDB System Configuration
Figure 5:
1. On the SAP global host, you run SAPinst and install the Java central services instance (SCS).
2. On the database host, you run SAPinst and install the Java Add-In for the database instance.
3. On the central instance host, you run SAPinst and install the Java Add-In for the central
instance.
4. If required, you run SAPinst install one to <n> ABAP+Java dialog instances.
Caution
You cannot install the Java Add-In for the dialog instance(s) of the existing ABAP system.
Instead, you have to install new ABAP+Java dialog instance(s).
Security Issues
n For security reasons the logs must be mirrored using the operating system or hardware.
Caution
If a system runs without mirroring, you might lose all data since the last complete backup in the
event of a disk crash.
18/140 PUBLIC 08/27/2007

2 Planning
Recommendation
We recommend mirroring the logs using the operating system or hardware.
If this is not possible, then mirror the logs with the database mirroring provided by MaxDB.
n We recommend you to run the database with raw devices.
Caution
Never use RAID 5 systems for database log volumes.
n Do not replace file systems by softlinks.

n Raw devices are very secure in the event of a system crash.
Security Concept for Database Software Owner

As of MaxDB 7.5.00 there is a new security concept for the database software owner. Authorization to
access directories and files is restricted, and a new user and user group is required:
n User is sdb (MaxDB default)
n User group is sdba (MaxDB default)
This user and group are the only database software owners on the host. For security reasons, the
user does not have a logon for the system, which guarantees the physical integrity of the database
files. Database processes run under this user, which makes sure that several different users cannot
manipulate the database system.
Performance Issues
n Store database data files and logs on different disks

n As the logs are written synchronously, they produce the most I/O activity of all database files.
n It is possible to put the logs on the same disk as/sapmnt, but this is not recommended.
n Use the partitions DISKD<N> exclusively for data files of the database.
n If paging or swapping areas and log data reside on the same disk, the performance will be
extremely poor.
n For database volumes, raw devices are faster than files. The slowest disk drive determines the I/O
performance of the database.
Different MaxDB Systems

For performance reasons, we normally recommend that you do not install several database systems
(for different SAP systems) on one single host. If you still decide to do so, you must install each
database as described in this documentation.
Recommended Configuration
The following graphic shows an optimal distribution of the database data on different disks.
Optimal Distribution
08/27/2007 PUBLIC 19/140

2 Planning
2.4 Basic SAP System Parameters
Figure 6:
For more information on the file systems for the SAP system and the MaxDB database, see Setting
Up File Systems [page 50].
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.
Note
In the column “Enter Your Values”, you write down the values that you plan to use, for example,
the Message Port Number.
20/140 PUBLIC 08/27/2007

2 Planning
SAP System ID and Database ID
Parameters Description Enter Your Values

SAP System ID The SAP System ID <SAPSID> identifies the whole SAP ...
<SAPSID> 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:

n Is unique throughout your organization
n Consists of exactly three alphanumeric characters
n Contains only uppercase letters
n Has a letter for the first character
n Does not include any of the following, which are reserved
IDs:
ADD ALL AND ANY ASC COM DBA END EPS FOR GID IBM
INT KEY LOG MON NIX NOT OFF OMS RAW ROW SAP SET
SGA SHG SID SQL SYS TMP UID USR VAR
Database ID <DBSID> The <DBSID> identifies the database instance. ...

The database ID <DBSID> can be different from the SAP
system ID.
SAP System Instances, Hosts and Ports

Instance Number Instance Number: ...
Technical identifier for internal processes, consisting of a
two-digit number from 00 to 97.
The instance number must be unique on a host. That is, if
more than one SAP instance is running on the same host, these
instances must be assigned different numbers.
To find out this number, look under the SAP directory
/usr/sap/<SAPSID>/DVEBMGS<nn> on the host of the central
instance.
The value <nn> is the number assigned to the central instance.
08/27/2007 PUBLIC 21/140

2 Planning

Name of Instance Instance Host: ...
Host Host name of the specific instance.
To find out the host name, open a command prompt and enter
hostname.
For more information about the allowed host name length and
characters, see SAP Note 611361.
Message Server Port ...
Caution
Make sure that all message server port numbers on the same
host are unique.
Port number of the SAP Message Server:

If you do not specify a value, the default port number is used.
The message server port number must be unique for the SAP
system on all hosts.
ABAP Message Server Port
There is an external message server port using the parameter
rdisp/msserv and an internal message server port using the
parameter rdisp/msserv_internal.
The ABAP message server uses both the internal and the external
message server ports. Both message server ports are configured in
the default profile.
The external message server port uses the parameter
rdisp/msserv with default value 36<nn>, where <nn> is the
instance number of the ABAP message server instance.
The internal message server port uses the parameter
rdisp/msserv_internal with default value 39<nn>, where <nn>
is the instance number of the ABAP message server instance.
Java Message Server Port
The Java message server only uses the internal message server
port. The Java message server is configured in the SCS instance
profile.
The parameter rdisp/msserv is set to 0, so that the external port
is not open.
The internal 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 internal and
external message server ports, see SAP Note 821875.
22/140 PUBLIC 08/27/2007

2 Planning
Master Password

Master Password This password is used for all user accounts SAPinst creates and ...
for the secure store key phrase. The length has to be 8 to 14
characters.
Depending on your installation scenario there might be more
restrictions.
Caution
If you do not create the operating system users manually,
SAPinst creates them with the common master password (see
“Operating System Users”). In this case, make sure that the
master password meets the requirements of your operating
system and of your database.
Operating System User

System Administrator SAPinst creates the user <sapsid>adm. ...
User Make sure that the ID of this operating system user is unique and
the same on each application instance host.
If you do not create operating system users manually before you
start the installation, SAPinst will create them automatically
during the installation.
For more information, see Creating Operating System Users [page 46].
User Management Engine (UME)
Parameter Description Enter Your Values

ABAP Client The production client of the ABAP system. ...
Caution
This is only relevant for a Java Add-In installation.
DDIC Password The existing password of the DDIC user. ...
Caution
This is only relevant for a Java Add-In installation.
Java Administrator This user is created by SAPinst in the ABAP system. ...
User After the installation, this user is available both in the ABAP
and in the Java system
SAPinst sets the user name J2EE_ADMIN and the master password
by default.
If required, you can choose another user name and password
according to your requirements.
08/27/2007 PUBLIC 23/140

2 Planning

Java Guest User This user is for employees who do not belong to a company or ...
who have registered as company users and are pending approval.
Guest users belong to the default group Authenticated Users.
This user is created by SAPinst in the ABAP system.
After the installation, it is available both in the ABAP and in
the Java system
SAPinst sets the user name J2EE_GUEST and the master password
by default.
Communication User This user is created by SAPinst in the ABAP system. ...
After the installation, it is available both in the ABAP and in
the Java system
This user is used for the communication between the ABAP
system and the Java system.
SAPinst sets the user name SAPJSF and the master password by
default.
Internet Communication Manager (ICM) User Management

Password of webadm The administration user webadm is created to use the web ...
administration interface for Internet Communication Manager
(ICM) and Web Dispatcher.
SAPinst sets the master password by default. If required, you
can choose another password.
Parameters Relevant for the Connectivity to System Landscape Directory (SLD)

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.
For more information, see System Landscape
Directory [page 124].
SLD HTTP Host The host name of the System Landscape ...
Directory (SLD)
24/140 PUBLIC 08/27/2007

2 Planning

SLD HTTP Port The HTTP port of the Java system where ...
the SLD is installed. The following naming
convention applies: 5<instance_number>00.
Example
If the instance number of your Java system is
01, the SLD HTTP Port is 50100.
SLD Data Supplier User n If you want to install a local SLD, SAPinst ...
and password creates this user during the installation.
n 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
SLDDSUSER
SLD ABAP API User and n If you want to install a local SLD, SAPinst ...
password creates this user during the installation.
n 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 The instance number of the gateway instance ...
Number of the SLD
SAP System Client The client in which the ABAP RFC user exists ...
Parameters Relevant for the File System
Parameters Description Your Values

File system for the home directory /home/<username> ...
user
08/27/2007 PUBLIC 25/140

2 Planning
2.5 Running Adobe Document Services on Non-Supported Platforms
Parameters Description Your Values

SAP system mount directory /<sapmnt> is the base directory for ...
the SAP system.
For /<sapmnt> you can use a
directory of your choice.
Do not add <SAPSID> as
subdirectory because the system
adds this directory automatically.
Example
If you enter /<sapmnt>, the
system creates the directory
/<sapmnt>/<SAPSID>.
MaxDB file systems n MaxDB root directory, /sapdb ...

n For file system installations:
locations of SAP data and log
volumes
n For raw device installations:
locations of raw devices for data
and log volumes
Parameters Relevant for the Database

Database ID Identifier for the database [page 21]
Database schema
Database operating system users MaxDB software owner (default
and groups values):
n User: sdb
n Group: sdba
MaxDB database owner:
sqd<dbsid>
2.5 Running Adobe Document Services on Non-Supported

Platforms
Adobe document services (ADS) are currently not supported to run natively on all platforms
supported by SAP systems based on SAP NetWeaver, in particular on 64-bit platforms.
Procedure
To use ADS in SAP landscapes on non-supported platforms, install an additional standalone AS
Java on a platform supported by ADS.
26/140 PUBLIC 08/27/2007

2 Planning
2.6 High Availability: Planning the Switchover Cluster
For more information, see SAP Note 925741.

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 simply replicating them. 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
SAP recommends switchover clusters to achieve HA for your SAP system.
A switchover cluster consists of:

n 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
n Switchover software to detect failure in a node and switch the affected software unit to the standby
node, where it can continue operating
n 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)
Recommendation
If you want install the Java Add-In to an existing ABAP High-Availability system, we recommend
that you install the Java central services instance (SCS) in the switchover cluster of the ABAP central
services instance (ASCS).
08/27/2007 PUBLIC 27/140

2 Planning
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:
n SAP High Availability at:
http://service.sap.com/ha Media Library Documentation HA Documentation .
This covers HA for SAP systems based on SAP NetWeaver 7.0 and is part of the standard SAP
documentation delivered with SAP NetWeaver 7.0.
n Technical Infrastructure Guide: SAP NetWeaver 2004s at:
http://service.sap.com/installNW70
n 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 on how to install the standalone replicated enqueue server, see:
http://help.sap.com 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:
Figure 7:
28/140 PUBLIC 08/27/2007

2 Planning
Note
This figure and the figures in this section are only examples. 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:
Figure 8:
Constraints
This documentation concentrates on the switchover solution for the central services instance.
For more information on 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.
More Information
For more information on HA documentation, see:
http://service.sap.com/ha
End of: HA (UNIX)
08/27/2007 PUBLIC 29/140

This page is intentionally left blank.
3 Preparation
3 Preparation
You have to complete the following preparations:

1. You check the hardware and software requirements [page 37].
2. If required, you create operating system users manually [page 46].
3. You set up file systems and raw devices [page 50].
4. If you want to perform a distributed installation, you export and mount global directories:
Caution
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
a) On the SAP trans host, you export the trans directory to SAP global host, central instance host,
database instance host, and — if required — to the dialog instance host(s).
b) On the SAP global host, you export subdirectories exe, global, profile of /sapmnt/<SAPSID>
to central instance host, database instance host, and — if required — to the dialog instance
host(s).
c) You mount subdirectories exe, global, profile of /sapmnt/<SAPSID> and directory trans on
the database instance host and on the central instance host. If you want to install one or more
dialog instance(s), you also have to mount these directories on the dialog instance host.
For more information about exporting and mounting directories, see:
n Exporting and Mounting the Global Transport Directory [page 56]
n Exporting and Mounting Directories via NFS for Linux [page 57]
5. You install the SAP front-end software [page 59].
Caution
6. You install the Java Development Kit [page 59].

7. You prepare and mount the installation media [page 61].
08/27/2007 PUBLIC 31/140

3 Preparation
3.1 High Availability: Switchover Preparations

3.1.1 Preparing for Switchover
This section describes the extra preparations you need to make for a high availability (HA) installation.
For more information consult your HA partner.
You need to perform the preparations listed below on host A and ‒ after you have installed the central
services (SCS) instance ‒ on host B.
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 27].
Procedure
1. You check that your system meets the hardware and software requirements [page 37] for an HA setup,
including the switchover software.
2. You set up file systems (that is, disk partitions), mount points, and (if required) NFS for your HA
system on node A (before the installation of the SCS instance with SAPinst) and node B (after the
installation of the SCS instance with SAPinst):
Caution
Recommendation
If possible, use journaled file systems (JFS), which allows much quicker recovery after a host
machine crash. With JFS you can often reduce the switchover time because the hard disk
maintains data integrity in the event of a system crash or if the system is otherwise halted
abnormally.
a) You set up the required file systems [page 34] using mount points or NFS
b) If required, you configure NFS [page 35], making sure you are using the virtual host name for NFS
to enable NFS switchover..
32/140 PUBLIC 08/27/2007

3 Preparation
c) You assign the local file systems to mount points.

d) You assign the shared file systems to mount points in appropriate cluster packages.
Example
The figure 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.
Figure 9:
3. You set up Domain Name System (DNS) on the virtual host.
Caution
4. You assign the virtual IP addresses and host names for SCS instance, and (if required) NFS to
appropriate cluster packages.
Caution
08/27/2007 PUBLIC 33/140

3 Preparation
Note
For more information on how to assign resources to cluster packages, ask your HA partner.
End of: HA (UNIX)
3.1.2 Setting Up File Systems
Caution
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.
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 [page 50].
Note
The file systems /sapmnt/<SID> and /usr/sap/trans are Network File Systems (NFS), whereas
/usr/sap>SID> is a file system 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.
2. 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 /usr/sap/<SID> file system.
The file system contains two subdirectories:
n SYS contains links to the central directory /sapmnt/<SID>
n <INSTTYPE><NR> (where the name is defined by the type of services and the application server
number, for example DVEBMSG00), which contains data for the local AS instance.
Only the latter directory needs to be migrated with the AS instance during the switchover.
As 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/<SID>, create a file system
/usr/sap/<SID>/<INSTTYPE><NR> with the usual <> substitutions. The file name for the CI is
normally 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 /usr/sap/<SID> tree instead
of mounting on top of it.
34/140 PUBLIC 08/27/2007

3 Preparation
Note
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 (in order
to use the resources efficiently). You must use this approach for integrated installations of the AS
with ABAP and Java stacks.
End of: HA (UNIX)
3.1.3 Configuring Network File 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. 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:
n How to protect NFS
n 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.
Procedure
1. Check the NFS directories, several of which need to be shared between all instances of a system.
These directories are:
n /sapmnt/<SID>/profile
Contains the different profiles to simplify maintenance
n /sapmnt/<SID>/global
Contains log files of batch jobs and central SysLog
n /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.
n /sapmnt/<SID>/exe
Contains the kernel executables. These executables ought to be accessible on all AS instances
locally without having to use NFS. The best solution is to store them locally on all AS instance
hosts.
2. Since you can protect NFS by a switchover product, it makes sense to install it on a cluster node.
08/27/2007 PUBLIC 35/140

3 Preparation
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:
a) On the primary server, mount the disks containing the directories:
/export/usr/sap/trans
/export/sapmnt/<SID>
b) The primary server creates soft links to the directories with the original SAP names:
/usr/sap/trans —> /export/usr/sap/trans
/sapmnt/<SID> —> /export/sapmnt/<SID>
Alternatively the primary server can also mount the directories:
/export/usr/sap/trans —> /usr/sap/trans
/export/sapmnt/SID —> /sapmnt/<SID>
c) The primary server exports:
d) The standby NFS mounts:
from virt.IP:/export/usr/sap/trans to /usr/sap/trans
from virt.IP:/export/sapmnt/<SID> to /sapmnt/<SID>
If the primary node goes down and a switchover occurs, the following happens:
n These directories on the standby node become busy:
/usr/sap/trans
/sapmnt/<SID>
n The standby node mounts disks to:
n The standby node configures the virtual IP address virt.IP
n The standby node exports:
n These directories on the standby node are accessible again:
/usr/sap/trans
/sapmnt/<SID>
End of: HA (UNIX)
End of: HA (UNIX)
36/140 PUBLIC 08/27/2007

3 Preparation
3.2 Hardware and Software Requirements

You check the hardware and software requirements for your operating system (OS) and the SAP
instances using the Prerequisite Checker tool. The Prerequisite Checker provides information about
the requirements that you need to meet before you start the installation. For example, it checks the
requirements for the different installation services.
Note
n The values that are checked by the Prerequisite Checker apply to the installation of development
systems or quality assurance systems.
n For the most recent updates to the Prerequisite Checker, always check SAP Note 855498.
You can run the Prerequisite Checker as follows:

n Standalone (optional):
To check the hardware and software requirements of the host on which you want to later install
an SAP system, you can run the Prerequisite Checker standalone [page 38].
n Integrated in SAPinst (mandatory):
SAPinst automatically runs the Prerequisite Checker when you install your SAP system.
We also recommend that you consult the requirements checklists tables, which provide values for the
installation of development systems or quality assurance systems. Depending on the amount of
data involved, the requirements might change. In addition, consider the following information:
n To get precise sizing values for production systems, use the Sizing Guide ‒ Sizing SAP Solution Manager
4.0 which is available on SAP Service Marketplace at http://service.sap.com/instguides
SAP Components SAP Solution Manager Release 4.0 .
n For supported operating system releases, see the Product Availability Matrix on SAP Service
Marketplace at http://service.sap.com/pam SAP Technology Components SAP SOLUTION
MANAGER SAP SOLUTION MANAGER 4.0 .
n Contact your OS vendor for the latest OS patches.
n Make sure that the host name meets the requirements listed in SAP Note 611361.
n Check your keyboard definitions.
n 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. If required, you run the Prerequisite Checker standalone [page 38] to check the hardware and software
requirements.
08/27/2007 PUBLIC 37/140

3 Preparation
Caution
If you do not fully meet the requirements, you might experience problems when working with
the SAP system.
2. In addition, we recommend that you check the hardware and software requirements for your
operating system and for the system variant that you want to install:
n Linux [page 39]
n Central system [page 41]
n Distributed or high availability system [page 42]
3. If you want to install additional dialog instances, check the requirements for a Dialog instance
[page 44].
3.2.1 Running the Prerequisite Checker in Standalone Mode

(Optional)
Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check the
hardware and software requirements for your operating system (OS) and the SAP instances.
Recommendation
We recommend that you use both the Prerequisite Checker and the requirements tables for reference.
Note
When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks the
hardware and software requirements in the background.
Prerequisites
n You have installed the correct Java Development Kit (JDK) [page 59].
n You have prepared the installation master DVD on the required installation host [page 61].
n You make sure that therequired prerequisites are met before starting SAPinst [page 67].
Procedure
1. You start SAPinst [page 70].
2. On the Welcome screen, choose <SAP System> Additional Software Lifecycle Tasks Additional Preparation
Tasks Prerequisites Check .
3. Follow the instructions in the SAPinst dialogs and enter the required parameters.
38/140 PUBLIC 08/27/2007

3 Preparation
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. If you want to make a change, select the relevant parameters and choose Revise.
4. To start the Prerequisite Checker, choose Start.
Result
The Prerequisite Check Results screen displays the results found. If required, you may also check the
results in file prerequisite_checker_results.html, which you find in the installation directory.
3.2.2 Requirements for Linux
The host machine must meet the following requirements:
Note
The information here is not intended to replace the documentation of the Linux operating system
(OS).
Note
For more information about the installation on Linux, see SAP Note 171356.
Requirement
Type Requirement
Hardware n CD /DVD drive
l ISO 9660 compatible
l Must be connected locally to your central instance host.
l You can configure multiple CD / DVD drives. For more information, see Mounting
a CD / DVD for Linux [page 64].
n Disks
For data security reasons distribution over five disks is recommended (RAID5).
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.
To print and change the partitioning of the first SCSI disk enter this command:
/sbin/fdisk /dev/sda
To print and change the partitioning of a RAID device enter commands specific to
your hardware.
Example
Here are some examples of hardware-specific commands for RAID devices:
08/27/2007 PUBLIC 39/140

3 Preparation
Requirement
Type Requirement
/sbin/fdisk /dev/rd/c0d0
/sbin/fdisk /dev/ida/c0d0
n RAM
To display RAM size in KB enter this command:
free
n CPU
The recommended minimum hardware is either two physical single core processors or
one physical dual core processor.
Software n Operating system
Check the operating system version with this command:
cat /etc/*-release
n Linux kernel version
Check the Linux kernel version with this command:
uname -r
n Linux kernel parameter settings
Check the Linux kernel parameter settings with this command:
/sbin/sysctl –a
n Activated hardware drivers
Check the activated hardware drivers with this command:
lsmod
n Shared memory file system
Check the size of the shared memory file system with this command:
df –k /dev/shm
n Network File System (NFS)
Check whether NFS is running as follows:
l On Red Hat Linux
service nfs status
service portmap status
l On SUSE LINUX
rcnfs status
rcnfsserver status
rcportmap status
n To check routing information enter this command:
netstat -r
n System Language
For the installation, you must choose English as the operating system language on all
Linux hosts that run SAP software.
n National Language Support NLS)
To display available locales enter this command:
locale -a
Check the output for locales such as the following:
de_DE, en_US
n LDAP (Lightweight Directory Access Protocol)
40/140 PUBLIC 08/27/2007

3 Preparation
Requirement
Type Requirement
If you want to use LDAP, you need the LDAP libraries that are usually installed with the
openldap RPM. To check, enter this command:
rpm -qa | grep openldap
Make sure that the output of this command contains at least one of the following
RPM packages:
l Red Hat Linux:
openldap2
l SUSE LINUX
openldap2
openldap2–client
n C compiler
The C compiler gcc must be installed. To check, enter this command:
rpm -qa | grep gcc
Make sure that the output of this command contains a gcc RPM package.
Other n Printer
Check the status of spooling queues and printers with this command:
lpc status
Check whether you can print a file with this command:
lpr —P<printer_name> <test_file>
n Network
Test the network connection to the database server with this command:
ping -c 10 <db_server_name>
3.2.3 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:
Requirement Requirement
Type
Hardware n DVD drive
n Hard disk drives with sufficient space for the SAP system and the database
For more information, see Setting Up File Systems [page 50].
n Hard disk drives with sufficient space for swap.
Recommended total size: twice the main memory extension (2 * RAM). For more
information, see SAP Note 171356
n 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 61].
n 1.2 GB of temporary disk space for the installation.
n RAM:
3 GB (minimum), 8 GB (recommended)
08/27/2007 PUBLIC 41/140

3 Preparation
Type
Java Add-In (ABAP system already exists): 1.5 GB (minimum), 4 GB
(recommended)
Software n DB2 9 for Linux, UNIX, and Windows (automatically installed by SAPinst).
Caution
l For the installation of your SAP system, only the English version of DB2 9
is supported.
l You must only use the DB2 9 software provided by the SAP installation DVDs.
n If application servers are installed decentralized, Network File System (NFS) must be
installed.
n Make sure that the required fonts and code pages are installed.
n Make sure that National Language Support (NLS) and corresponding saplocales are
installed.
3.2.4 Requirements for a Distributed or a High Availability

System
The following sections provide information about the hardware and software requirements in a
distributed system, where the following SAP instances can reside on differents hosts:
n Central services instance [page 42]
n Central instance [page 43]
n Database Instance [page 44]
Note
If you install multiple SAP system instances on one host, you need to add up the requirements.
3.2.4.1 Requirements for the Central Services Instance
The central services instance host must meet the following requirements:
42/140 PUBLIC 08/27/2007

3 Preparation
Requirement Type Requirement

n Hard disk drives with sufficient space for the central services instance
For more information, see Setting up File Systems [page 50].
n Hard disk drives with sufficient space for swap:
Recommended total size: Twice the main memory extension (2 * RAM). For
more information, see SAP Note 171356
n 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 61].
n RAM:
0.5 GB (minimum), 1 GB (recommended)
1 GB (minimum), 3 GB (recommended)
End of: HA (UNIX)
Software n Network File System (NFS) must be installed.
3.2.4.2 Requirements for the Central Instance
The central instance host must meet the following requirements:

Type
n Hard disk drives with sufficient space for the central instance.
For more information, see Setting Up File Systems [page 50] SAP File Systems .
Recommended total size: Twice the main memory extension (2 * RAM). For more
n 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 61].
n RAM:
1.5 GB (minimum), 5 GB (recommended)
Java Add-In (ABAP system already exists): 0.5 GB (minimum), 2 GB
(recommended)
Software n If application servers are installed decentralized, Network File System (NFS) must be
installed.
n Make sure that the required fonts and code pages are installed.
n Make sure that National Language Support (NLS) and corresponding saplocales are
installed.
08/27/2007 PUBLIC 43/140

3 Preparation
3.2.4.3 Requirements for the Database Instance
The database host must meet the following requirements:

Require-
ment Type Requirement
n Disk space:
l 1.2 GB temporary disk space on separate disks
l 4.5 GB of temporary disk space for every required installation DVD or 650 MB for every
required installation CD that you have to copy to a local hard disk.
For more information, see Preparing the Installation DVDs [page 61].
l For swap:
u 3*RAM + 500 MB
u Minimum 1.25 GB
Note
For security reasons (system failure), the file systems must be distributed physically
over at least three (but five are recommended) disks.
n RAM:
l Non-Unicode SAP system: 512 MB
l Unicode SAP system: 1 GB
Software n MaxDB version 7.6.00 Build 18 or higher
n For supported operating system releases, see SAP Service Marketplace
athttp://service.sap.com/platforms Product Availability Matrix.
n Contact your operating system vendor for the latest OS patches.
n If application servers are installed decentralized, Network File System (NFS) is a
requirement.
n Make sure that the necessary fonts and code pages are installed.
n Make sure that Native Language Support (NLS) and corresponding saplocales are installed
Other If you want to install a printer on the database server for the SAP system, make sure that the
printer can be accessed under UNIX.
3.2.5 Requirements for a Dialog Instance
The dialog instance host must meet the following requirements:
44/140 PUBLIC 08/27/2007

3 Preparation
Requirement Type Requirement

n Hard disk drives with sufficient space for the dialog instance.
For more information, see Setting up File Systems [page 50].
Recommended total size is twice the main memory (2 * RAM). For more
n 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 61].
n RAM:
1 GB minimum, 3 GB recommended
Software n 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.
n Network File System (NFS) must be installed.
3.2.6 Checking and Modifying the Linux Kernel
If you are using a Linux kernel version certified by SAP, you do not need to modify the Linux kernel.
To check the Linux kernel version, enter this command:
uname –a
For more information about the Linux kernel versions certified by SAP, see SAP Note 171356.
Check the Linux kernel parameters for your Linux distribution according to one the following SAP
Notes:
n RHEL4: SAP Note 722273
n RHEL5: SAP Note 1048303
n SLES9: SAP Note 797084
n SLES10: SAP Note 958253
3.2.7 Setting up Swap Space for Linux
You created partitions of the type “swap” when you scheduled the hard disk(s) during the installation
of your Linux distribution.
The Linux kernel usually does not require much swap space, since other limits have already been
reached before the swap space has reached full capacity (“late swap allocation”). However, if you
08/27/2007 PUBLIC 45/140

3 Preparation
3.3 Creating Operating System Users
notice the need for more swap space when using SAP software, you can use the distribution-specific
tools to increase your swap space at any time.
Prerequisites
Make sure that the UNIX kernel is already configured and the other prerequisites are met as described
in Requirements for Linux [page 39] and in Checking and Modifying the Linux Kernel [page 45].
Procedure
1. To check the allocated swap space, enter the following command:
swapon -s
Recommended total size: Twice the main memory structure (2 x RAM).
For earlier 32-bit Linux Versions, the maximum size of a swap partition is 2 GB. If you require more
space, distribute the swap space onto multiple swap partitions.
If possible, use an entire physical disk as a swap space partition.
2. If required, configure swap space as follows:
n On Red Hat Linux:
Check the documentation provided by Red Hat.
n On SUSE LINUX, enter one of the following commands:
l yast
l yast2
Note
You can configure multiple swap partitions up to a maximum of 32.
3.3.1 Network Information Service
If you use Network Information Service (NIS), you need to distribute users over the network.
Caution
If you do not create users manually, SAPinst creates them automatically during the installation
All users must have identical environment settings. If you change the environment delivered by
SAP, such as variables, paths, and so on, SAP does not assume responsibility.
SAPinst checks all required users, groups, and services on the local machine. If you manage users,
groups or services network-wide in your company, we recommend that you create the user and
46/140 PUBLIC 08/27/2007

3 Preparation
group NIS entries before running SAPinst as described in Creating Operating System Users and Groups
Manually (Optional) [page 46].
SAPinst checks if the required services are available on the host and creates them if necessary. See the
log messages about the service entries and adapt the network-wide (NIS) entries accordingly.
SAPinst checks the NIS users, groups and services using NIS commands. However, SAPinst does not
change NIS configurations.
3.3.2 Creating Operating System Users and Groups
Caution
If you do not want SAPinst to create operating systems users, groups and services, you can optionally
create them manually before the installation.
If you want to use global accounts which are configured on a separate host, you start SAPinst and
choose Life Cycle Management Preparation Operating System Users and Groups . For more information,
see Running SAPinst on UNIX [page 70].
Users and Groups

SAPinst checks whether the required users and groups already exist. If not, it creates new users and
groups as necessary.
SAPinst chooses available user IDs and group IDs unless you are installing a dialog instance. On a
dialog instance you have to enter the same IDs as on the central instance host.
As a general requirement, the user IDs and the group IDs must be the same on all hosts.
Caution
If you create the sdb user manually, make sure that you lock it for the installation. SAPinst normally
locks this user after it has been created.
Caution
The user ID (UID) and group ID (GID) of SAP users and groups 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.
Caution
Do not delete any shell initialization scripts in the home directory of the OS users, even if you do not
intend to use the shells that these scripts are for.
Users and Their Primary Groups
08/27/2007 PUBLIC 47/140

3 Preparation
User Primary Group

<sapsid>adm sapsys
sqd<dbsid> sapsys
sdb sdba
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 do not use central user management (for example, NIS),
and you use local operating system user accounts instead, user <sapsid>adm and the database
operating system user must have the same password on all hosts.
Groups and Members

Groups Members
sapsys sqd<dbsid>, <sapsid>adm
sdba sdb, <sapsid>adm, sqd<dbsid>
More Information
Creating Linux Groups and Users (Optional) [page 49]
3.3.3 Creating Operating System Users and Groups Manually
If you do not want SAPinst to create operating systems users, groups and services, you can optionally
create them manually before the installation.
Users and Groups

SAPinst checks whether the required users and groups already exist. If not, it creates new users and
groups as necessary.
SAPinst chooses available user IDs and group IDs unless you are installing a dialog instance. On a
dialog instance you have to enter the same IDs as on the central instance host.
As a general requirement, the user IDs and the group IDs must be the same on all hosts.
Caution
The user ID (UID) and group ID (GID) of SAP users and groups must be identical for all servers
belonging to any SAP system.
This does not mean that all users and groups have to be installed on all SAP servers.
48/140 PUBLIC 08/27/2007

3 Preparation
The following tables list the users and groups necessary for your database:
Users and Their Groups
User Primary Group Secondary Group(s)

<sapsid>adm sapsys n sapinst
n You need the following
secondary DB2 Connect
groups:
l dasadm1
l db2grp1
(These names are merely a
recommendation.)
root sapsys sapinst
Groups and Members
Groups Members
sapsys n <sapsid>adm
n root
sapinst n <sapsid>adm
n root
See Also
Creating Linux Groups and Users (Optional) [page 49]
3.3.4 Creating Linux Groups and Users (Optional)
You can create and manage Linux users using one of the following graphical tools:
n Red Hat Linux:
l RHEL4 and higher:
system-config-users
n SUSE Linux:
l SLES9 and higher:
yast or yast2
Task Command
Creating groups groupadd
Modifying groups groupmod
Deleting groups groupdel
08/27/2007 PUBLIC 49/140

3 Preparation
3.4 Setting Up File Systems and Raw Devices
Task Command
Creating users useradd
Modifying users usermod
Deleting users userdel
More Information
For more information about the users and groups that are created either by SAPinst or manually, see
Creating Operating System Users and Groups Manually (Optional) [page 47].

The following section(s) describe how to set up SAP file systems for the SAP instances and, if required,
raw devices on operating system level:
n Setting Up File Systems [page 50]
n MaxDB File Systems [page 55]
n Setting Up Standard File Systems for Linux [page 55]
3.4.1 Setting Up File Systems
Depending on the installation option you have chosen, the following file systems listed in the figures
and tables below are required.
SAPinst sets up most of these file systems automatically during installation. However, some file
systems you need to set up manually. For details see the following figures and tables.
Note
For more information on how to set up your file systems if you are performing an HA installation,
see High Availability: Setting Up File Systems [page 34].
End of: HA (UNIX)
50/140 PUBLIC 08/27/2007

3 Preparation
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 in any case. Otherwise you will not be able to
restart the system after patches have been applied.
See also Applying the Latest Kernel and Support Packages [page 91].
Standard SAP File Systems for an ABAP + Java System

The ABAP part of an ABAP+Java system can be Unicode or Non-Unicode, whereas the Java part is
always Unicode.
Figure 10: SAP File Systems for an ABAP + Java System (Unicode)
08/27/2007 PUBLIC 51/140

3 Preparation
Figure 11: SAP File Systems for an ABAP + Java System (ABAP Non-Unicode, Java Unicode)
The instance name (instance ID) of the ABAP+Java central instance is DVEBMGS<Instance_Number>,
the instance name of an ABAP+Java dialog instance is D<Instance_Number>, and the instance name
of the Java central services instance is SCS<No>.
If you are performing an HA installation of your ABAP+Java system, there is also an ABAP central
services instance called ASCS<Instance_Number>.
End of: HA (UNIX)
Example
For example, the file system structure might look as follows:
On a central instance with SAP system ID C11 and instance name DVEBMGS00, the J2EE Engine
is installed to /usr/sap/C11/DVEBMGS00/j2ee, and the corresponding SDM is installed to
/usr/sap/C11/DVEBMGS00/SDM.
On a dialog instance with instance name D01, the J2EE Engine is installed to /usr/sap/C11/D01/j2ee.
SAP File Systems in Detail
Note
The listed file system sizes are initial SAP requirements.
Depending on your operating system, you might also have to add space for administrative purposes.
52/140 PUBLIC 08/27/2007

3 Preparation
The following file systems are global, that is, they are accessed by all hosts in the SAP system.
SAP File Systems
File System Name Description Space Required

<sapmnt>/<SAPSID> Software and data for one SAP system n Central Instance:
This directory is physically located on the SAP 3.0 GB
global host. In homogeneous systems, you need Java Add-In (ABAP system
to mount it via NFS (Network File System) for already exists): 1.5 GB
all hosts belonging to the same SAP system. It n Central Services Instance:
contains the following subdirectories: 1.0 GB
n exe n Dialog instance:
Contains executable kernel programs no file system required
Note
SAP system ABAP (Non-Unicode) +
Java only: exe contains a folder uc with
a platform-specific subfolder: <sapmnt>/
<SAPSID>/exe/uc/<platform>
n global
Contains log files
n profile
Contains the start and operations profiles of
all instances
/usr/sap/<SAPSID> Instance-specific data, symbolic links to the data n Central instance
for one system 3.0 GB (Non-Unicode ABAP), 4.0
This directory contains files for the operation of GB (Unicode ABAP)
a local instance. n Dialog instance:
There is a subdirectory <INSTANCE_NAME> for 2.0 GB (Non-Unicode ABAP), 3.0
each instance installed on the local instance GB (Unicode ABAP)
host, whereas data used by several instances are n Central Services Instance :
located in directory SYS. Only valid for: non-HA
1.0 GB (non-High Availability)
End of: non-HA
Note
SAPinst creates the subfolder Only valid for: HA (UNIX)
/usr/sap/<SAPSID>/<INSTANCE_NAME>/SDM only 2.0 GB (High Availability)
for the central instance of ABAP+Java or Java End of: HA (UNIX)
systems.
For more information on SDM, see Checking the
Java Documentation [page 107].
There are subdirectories of

/usr/sap/<SAPSID>/SYS with symbolic
links to subdirectories of /<sapmnt>/<SAPSID>:
n /usr/sap/<SAPSID>/SYS/profile is linked to
/<sapmnt>/<SAPSID>/profile
n /usr/sap/<SAPSID>/SYS/global is linked to
/<sapmnt>/<SAPSID>/global
08/27/2007 PUBLIC 53/140

3 Preparation

n /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>, SCS<No>,
ASCS<No>.
Note
SAP system ABAP (Non-Unicode)
+ Java only: Executables for the exe
directory of instances of the type
SCS<No> are replicated by sapcpe from
<sapmnt>/<SAPSID>/exe/uc/<platform>
Note
Since SAP traces for the instance are created in
directory /usr/sap/<SAPSID>/<INSTANCE_NAME>,
you must make sure that sufficient space is
available. Changes in SAP system profiles can
also affect the disk space.
/usr/sap/trans Global transport directory for all SAP systems n For the installation of all
For more information about exporting and instances: 500 MB
mounting the global transport directory, see n For the use of all instances: 2 GB
Exporting and Mounting the Global Transport Directory
[page 56]
The global transport directory is used by the
Change and Transport System (CTS). The CTS
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, see:
http://help.sap.com/nw70 SAP NetWeaver
Library SAP NetWeaver by Key Capability Solution
Life Cycle Management by Key Capability Software Life
54/140 PUBLIC 08/27/2007

3 Preparation

Cycle Management Software Logistics Change and
Transport System
If you select the check box SAP System will be under
NWDI control on the screen SAP System > NWDI
Landscape, SAPinst will copy all SCAs belonging to
the usage types / software units you install to the
global transport directory.
For more information, see
http://help.sap.com/nw70 SAP NetWeaver
Library SAP NetWeaver by Key Capability Solution
Life Cycle Management by Key Capability Software
Life Cycle Management Software Logistics SAP
NetWeaver Development Infrastructure Maintenance of
an NWDI-Driven System Landscape
Set up the file systems required for the database as described in MaxDB File Systems [page 55].
3.4.2 MaxDB File Systems
These are the file systems for the MaxDB database:
MaxDB File Systems

/<sapdata> MaxDB data See Requirements for the Database Instance [page 44].
Note
If the database data is installed on raw devices, you do
not need to set up /<sapdata>.
/sapdb MaxDB 400 MB
software
3.4.3 Setting Up Standard File Systems and Raw Devices

for Linux
This section describes how to set up standard files systems for Linux.
08/27/2007 PUBLIC 55/140

3 Preparation
3.5 Exporting and Mounting the Global Transport Directory
Note
We do not recommend that you perform the installation of an SAP system using raw devices. For
more information see SAP Note 405827.
If you still want to use raw devices, contact Linux support for information about how to set up
raw devices on Linux.
Prerequisites
The following table shows the variables and their corresponding values.
Variables in Standard File Systems
Variable Description
<diskname> Full path of disk, for example /dev/sda
<mountpointname> Full path of a mount point, for example, /sapdb/<SAPSID>/sapdata1
Procedure
1. Create an empty file system.
Example
Example for ext2 file system:
mke2fs —b 4096 /dev/<device>
2. Create a mount point.

mkdir <mountpointname>
3. Add a line to /etc/fstab.
Example
Example for the ext2 file system:
/dev/<device> <mountpointname> ext2 defaults 1 2
4. Mount the file system:

mount <mountpointname>
3.5 Exporting and Mounting the Global Transport Directory
Caution
In your SAP system landscape, a global transport directory for all SAP systems is required.
56/140 PUBLIC 08/27/2007

3 Preparation
3.6 Exporting and Mounting Directories via NFS for Linux (Optional)
n 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.
n If this global transport directory does not exist, proceed as follows:
l Create the transport directory (either on the central instance host or on a file server).
l Export it on the global transport directory host.
l If you did not create the transport directory on your SAP instance installation host, mount it
there.
Exporting the Transport Directory

1. Log on as user root to the host where the global transport directory /usr/sap/trans resides.
2. Make sure that /usr/sap/trans belongs to the group sapsys and to the user root .
3. 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. Log on as user root to the central or dialog instance host where /usr/sap/trans is to be mounted.
2. Create the mount point /usr/sap/trans.
3. Mount /usr/sap/trans using Network File System (NFS) from the exporting host.
More Information
Exporting Directories via NFS for Linux [page 57]
3.6 Exporting and Mounting Directories via NFS for Linux

(Optional)
To export directories via NFS, perform the following steps (the following assumes that the central
instance host is the NFS server):
1. Log on as user root to the NFS server.
2. Make sure that your host is configured as NFS server as follows:
n On Red Hat Linux, make sure that the output of the command:
chkconfig --list nfs
looks as follows:
nfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
n On SUSE Linux, enter the following command:
l SLES9 and higher:
08/27/2007 PUBLIC 57/140

3 Preparation
3.6 Exporting and Mounting Directories via NFS for Linux (Optional)
yast or yast2
You can set up your host as NFS server as follows:
n On Red Hat Linux, enter the following command:
l RHEL4 and higher:
system-config-users
n On SUSE Linux, enter the following command:
l SLES9 and higher:
yast or yast2
3. To export a directory from a local file system, you can proceed as follows:
n On Red Hat Linux, use the following tool:
l RHEL4 and higher:
system-config-nfs
n On SUSE Linux, use the following tool:
l SLES9 and higher:
yast2
n Perform the configuration manually.
To perform the configuration manually, proceed as follows:
a) To add a line to the local file /etc/exports, enter the following:
#/etc/exports
<directory> <hostname>(<options>)
Note
n There must not be a blank between <hostname> and <options>. Otherwise, the directory
is exported with default option (ro) (read-only) to the host specified by <hostname> and
with the option specified by <options> to all other hosts.
n To export directories on Linux with root permissions, use the option no_root_squash. For
security reason, only use this option during installation.
Example
n To export the directory /usr/sap/trans in read-only mode to the NFS client
host.wdf.sap-ag.de, enter the following:
#/etc/exports
/usr/sap/trans host.wdf.sap-ag.de(ro)
n To export the directory in read-write mode with root permissions, enter the following:
#/etc/exports
/usr/sap/trans host.wdf.sap-ag.de(rw,no_root_squash)
n To export the directory to all NFS clients of the domain using a wildcard (*), enter the
following:
#/etc/exports
/usr/sap/trans *.wdf.sap-ag.de(rw)
58/140 PUBLIC 08/27/2007

3 Preparation
3.7 Installing the Front-End Software
b) To activate the changes (that is, inform the NFS daemon about the changes performed in
/etc/exports), enter the following command:
exportfs -r
c) To get a list of all currently exported directories, enter the following command:
exportfs -v
For further details, consult the man page by entering man exports.
4. Log on as user root to the host where the file system should be imported.
5. To mount the file systems, enter the following command:
mount <nfs_server>:<file_system> <mount_point>
Example
mount <nfs_server>:/usr/sap/trans /usr/sap/trans
3.7 Installing the Front-End Software
Caution
For the installation, make sure that the front-end software is installed on at least one host machine in
your system environment. To simplify the administration of your SAP system, we recommend you
install the software on the central instance host.
With the SAP front-end installation software, SAPSetup, you can optimize the deployment of SAP
GUI to thousands of clients. You can easily tailor installation packages to match your requirements,
distribute patches, and set up automatic update processes for your clients.
For more information on installing the front-end software, see the documentation on SAP Service
Marketplace at http://service.sap.com/installNW70 :
n SAP Front End Installation Guide (English version)
n SAP Frontend-Installationsleitfaden (German version)
3.8 Installing the Java Development Kit
You need to prepare the system for the J2EE Engine by installing the Java Development Kit (JDK).
As of SAP NetWeaver 7.0 you must install the J2EE Engine with strong encryption.
The JDK includes the Java Runtime Environment (JRE), which is required both for SAPinst and
the SAPinst GUI.
08/27/2007 PUBLIC 59/140

3 Preparation
3.8 Installing the Java Development Kit
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 80]. 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):
a) Go to http://service.sap.com/pam.
b) On the right-hand panel, choose SAP Technology Components SAP SOLUTION MANAGER
SAP SOLUTION MANAGER 4.0 .
c) Choose tab strip JSE Platforms.
Note
For additional information on the recommended JDK version for your operating system and
about how to download it, see SAP Note 723909.
2. 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:
n If the JDK is not already installed, you need to download and install it.
n 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.
Note
If you use a Sun Java VM, you have to edit the conguration file
$JAVA_HOME/jre/lib/security/java.security, replacing entry
securerandom.source=file:/dev/random with securerandom.source=file:/dev/urandom.
3. As of SAP NetWeaver 7.0 strong encryption is mandatory for the J2EE Engine and for all usage types
that are deployed on it. You need to obtain the JCE policy files beforehand so that they can be
installed by SAPinst:
a) Download the JCE policy files for your platform at http://java.sun.com/products/jce/.
b) Download the JCE policy files for your platform at
http://www6.software.ibm.com/dl/jcesdk/jcesdk-p.
60/140 PUBLIC 08/27/2007

3 Preparation
3.9 Preparing and Mounting the Installation Media
c) SAPinst installs the JCE policy files during the installation process.
3.9.1 Preparing the Installation DVDs
You use this procedure to prepare the installation DVDs. Normally you obtain the installation DVDs
as part of the installation package that you receive from SAP. However, you can also download the
installation DVDs from SAP Service Marketplace [page 63].
Recommendation
We recommend that you make all required DVDs available in parallel.
Note
If you copy the installation DVDs to disk, make sure that the paths to the location of the copied
DVDs do not contain any blanks.
Procedure
1. Identify the required DVDs for your installation as listed below and keep them separate from the
remaining DVDs. 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 Solution Manager in the document
Media List for SAP Solution Manager 4.0 Upgrade / 4.0 Support Release 3 Installation on SAP Service
Marketplace at http://service.sap.com/instguides SAP Components SAP Solution Manager
Release 4.0 .
Note
You can find the Software Component Archives (SCAs) for the installation of SAP NetWeaver
usage types on the NetWeaver Java DVD and the SCAs for the installation of software units on the
SAP SCM 2007 Components DVD.
08/27/2007 PUBLIC 61/140

3 Preparation
SAP Instance Installation Required DVDs

Central services instance, central instance, n SAP Solution Manager 4.0 SR3 Installation Master DVD
dialog instance n SAP Kernel 7.00 SR2 DVD
n SAP Solution Manager 4.0 SR3 Java Components DVD
n RDBMS DVD
Database instance n SAP Solution Manager 4.0 SR3 Installation Master DVD
n SAP Kernel 7.00 SR2 DVD
n RDBMS DVD
n SAP Solution Manager 4.0 SR3 Installation Export DVD 1
n SAP Solution Manager 4.0 SR3 Installation Export DVD 2
The following table shows the required DVDs for the installation of the Java Add-In for an
existing ABAP System:
SAP Instance Installation Required DVD
Central instance, central services instance, n SAP Solution Manager 4.0 SR3 Installation Master DVD
dialog instance n SAP Solution Manager 4.0 SR3 Java Components DVD
n RDBMS DVD
Database schema n SAP Solution Manager 4.0 SR3 Installation Master DVD
n SAP Solution Manager 4.0 SR3 Installation Export DVD
n RDBMS DVD
2. Use one of the following methods to make DVDs available in parallel:

n Before the installation:
l Have sufficient DVD drives
l Copy DVDs manually to local hard disks
Caution
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.
n During the installation:

Use the SAPinst Media Browser screen. You can check the entered location in the Package Location
column and then copy the entire DVD to the path you entered in the Copy Package To column.
62/140 PUBLIC 08/27/2007

3 Preparation
3.9.2 Downloading Installation DVDs from SAP Service

Marketplace (Optional)
You normally obtain the installation DVDs as part of the installation package from SAP.
However, you can also download installation DVDs from SAP Service Marketplace at:
https://service.sap.com/swdc Downloads Installations and Upgrades Entry by Application Group
<your solution> <release of your solution> <your operating system> <your database> .
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.
Prerequisites
To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you
can find on SAP Service Marketplace at https://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.
Procedure
1. Create a download directory on the host on which you want to run SAPinst.
2. Identify all download objects that belong to one installation DVD according to one or both of the
following:
n 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
...
n 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.
3. Download the objects to the download directory.
4. 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.
08/27/2007 PUBLIC 63/140

3 Preparation
Note
SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always accept
with Yes.
3.9.3 Mounting a CD / DVD for Linux
Note
The placeholder <medium-mountdir> is used for either <cd-mountdir> or <dvd-mountdir>.
Procedure
1. Log on as user root.
2. To create a mount point for the CD / DVD, enter the following command:
mkdir <medium-mountdir>
Example
<medium-mountdir> is /sapcd
3. To mount the first CD / DVD device, enter the following command:

mount -t iso9660 -r <device> <medium-mountdir>
where <device> is /dev/cdrom for non-SCSI CD devices and /dev/scd<n> for SCSI drives with the
device number <n>.
If the file names on the mounted CD / DVD are written in lowercase letters, remount the CD /
DVD with the following commands:
umount <device>
mount -t iso9660 -r -o map=off <device> <medium-mountdir>
64/140 PUBLIC 08/27/2007

4 Installation
4 Installation
Note
Make sure that you have completed the planning and preparation activities before you start the
installation.
This section provides information about the steps that you have to perform to install your SAP system
Process Flow
1. If required, you perform a high-availability installation [page 65].

End of: HA (UNIX)
2. You check the prerequisites for the instances that you want to install before starting SAPinst [page 67].
3. You install your SAP system using SAPinst [page 70].
4.1 Performing a High-Availability Installation
This section describes how to perform a high-availability (HA) installation. For more information,
consult your HA partner.
Prerequisites
n You have completed all preparations, including preparing the installation of switchover units [page 32].
n You have set the environment variable SAPINST_USE_HOSTNAME [page 70] to specify the virtual host
name for the installation. Alternatively you can specify the virtual host name in the command
to start SAPinst.
08/27/2007 PUBLIC 65/140

4 Installation
4.1 Performing a High-Availability Installation
Caution
If you install the Java Add-In to an existing ABAP system, note the following:
l When you install the central services instance, SAPINST_USE_HOSTNAME must point to the
virtual host name under which the central services instance is to run.
l When you install the database instance, SAPINST_USE_HOSTNAME must point to the virtual
host name under which the database is installed.
l When you install the central instance, SAPINST_USE_HOSTNAME must point to the virtual
host name under which the central instance is installed.
Procedure
1. Run SAPinst [page 70] to install the central services instances (SCS and ASCS) using the virtual host
name on the primary cluster node, host A.
2. Install the central services (SCS) instance with SAPinst [page 70] using the virtual host name on the primary
node, host A.
3. Prepare the standby node, host B, making 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 Preparing for Switchover [page 32].
4. Set up the user environment on the standby node, host B.
For more information, see Creating Operating System Users and Groups Manually [page 47]. 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.
5. Configure the switchover software and test that switchover functions correctly.
6. Install the database instance on the primary node, host A.
7. Install the central instance with SAPinst [page 70] on the primary node, host A.
Note
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 ABAP SCS, which
is protected by the cluster.
Note
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
instances (SCS and ASCS), which are protected by the cluster.
8. If required, install additional dialog instances with SAPinst [page 70] to replicate the SAP system services
that are not a SPOF. These nodes do not need to be part of the cluster.
66/140 PUBLIC 08/27/2007

4 Installation
4.2 Prerequisites before Starting SAPinst
Note
Make sure that you complete the activities described in High Availability: Post-Installation Steps [page 96].
End of: HA (UNIX)
4.2.1 Prerequisites before Starting SAPinst: All Instances
This section provides information about running SAPinst that is valid for the installation of all
instances (central, central services, database, and dialog instance).
Prerequisites
n Make sure that you have defined the most important SAP system parameters as described in Basic
SAP System Parameters [page 20] before you start the installation.
n Check that your installation host(s) meets the requirements for the installation service(s) that you
want to install. For more information, see Running the Prerequisite Checker [page 38].
Procedure
1. If you want to install a dialog instance for an upgraded SAP system:
a) Edit DEFAULT.PFL.
b) Insert a line with the parameter rdisp/msserv_internal and set it to a free port number.
c) Edit the instance profile of the central services instance.
d) Set the parameter rdisp/msserv to 0.
e) Insert a line with the parameter rdisp/msserv_internal and set it to the port number that was
assigned before to rdisp/msserv.
f) Restart all instances of the SAP system.
Example
This shows the required change to the instance profiles:
n DEFAULT.PFL
Before the change:
...
rdisp/msserv = sapms<SAPSID>
...
After the change:
...
rdisp/msserv = sapms<SAPSID>
08/27/2007 PUBLIC 67/140

4 Installation
rdisp/msserv_internal = <free port number>

...
n Instance profile of the central services instance:
Before the change:
...
rdisp/msserv = 4711
...
After the change:
...
rdisp/msserv = 0
rdisp/msserv_internal = 4711
...
2. Make sure that your operating system does not delete the contents of the temporary directory
/tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for
example by using a crontab entry.
Note
SAPinst normally creates the installation directory sapinst_instdir directly below the
temporary directory. SAPinst finds the temporary directory by checking the value of the
environment variables TEMP, TMP, or TMPDIR. If no value is set for these variables, SAPinst uses
/tmp as default installation directory.
Make sure that the temporary directory has the permissions 777.
The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. These
executables are deleted again after SAPinst has stopped running.
If required, you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C .
Caution
If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.
3. Make sure that you have at least 60 MB of free space in the installation directory for each installation
service. 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 environment variables TEMP,
TMP, or TMPDIR to another directory with 200 MB free space for the SAPinst executables.
4. 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 111].
5. Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime
Environment (JRE).
68/140 PUBLIC 08/27/2007

4 Installation
6. Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where <host_name>
is the host on which you want to display the SAPinst GUI.
Shell Used Command
Bourne shell (sh) DISPLAY=<host_name>:0.0
export DISPLAY
C shell (csh) setenv DISPLAY <host_name>:0.0
Korn shell (ksh) export DISPLAY=<host_name>:0.0
4.2.2 Prerequisites before Starting SAPinst: Distributed

Instances
If you install a database or a dialog instance on a host other than the SAP Global host, you must
mount directories from the SAP Global host.
Prerequisites
n 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.
n 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 125].
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
For more information, see Exporting Directories via NFS for Linux [page 57].
Caution
Make sure that the global transport directory is mounted on every host where you want to install
an SAP instance. For more information, see Exporting and Mounting the Global Transport Directory [page
56]. Otherwise, the installation fails.
2. Log on to the host of the new instance as user root.

3. Create the following mount points and mount them from the SAP Global host:
<sapmnt>/<SAPSID>/exe
08/27/2007 PUBLIC 69/140

4 Installation
4.3 Installing an SAP System Using SAPinst
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
4.2.3 Prerequisites Before Starting SAPinst: High Availability
For a high-availability (HA) SAP system you can set the environment variable SAPINST_USE_HOSTNAME
to specify the virtual host name before you start SAPinst.
If you do not set this environment variable now, you can specify an equivalent parameter for the
virtual host name when you run SAPinst [page 70].
Procedure
Set SAPINST_USE_HOSTNAME to the virtual host name of the machine on which you are installing
an SAP instance.
End of: HA (UNIX)

The following sections tell you how to install the various instances of an SAP system, or a standalone
engine:
n Running SAPinst on UNIX [page 70]
n Using SAPinst GUI [page 78]
n Interrupted Installation with SAPinst [page 79]
n Performing a Remote Installation with SAPinst (Optional) [page 80]
n Starting SAPinst GUI Separately (Optional) [page 81].
n Entries in the Services File Created by SAPinst [page 83]
4.3.1 Running SAPinst on UNIX
This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a SAPinst GUI
and a GUI server, which both use Java.
This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running
on the same host. If required, you can instead perform a remote installation with SAPinst [page 80], where
SAPinst GUI is running on a separate host from SAPinst and the GUI server.
When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects via a secure
SSL connection to the GUI server and the GUI server connects to SAPinst.
70/140 PUBLIC 08/27/2007

4 Installation
Procedure
1. Log on to your host as user root.
Caution
Make sure that the root user has not set any environment variables for a different SAP system or
database.
2. If you want to install a central instance, a central services instance, a database instance, or a dialog
instance, 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 Linux [page 64].
3. Start SAPinst from the Installation Master DVD in one of the following ways:
n Using the default installation directory (recommended)
Enter the following commands:
cd <Installation Master_DVD>/IM_<OS>
./sapinst
Note
If you are installing a high-availability system and you have not already set the environment parameter
SAPINST_USE_HOSTNAME [page 70] to specify the virtual host name, you can start SAPinst
as follows:
./sapinst SAPINST_USE_HOSTNAME=<virtual host name>
End of: HA (UNIX)
Caution
Make sure that your operating system does not delete the contents of the temporary directory
/tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for
example by using a crontab entry.
Caution
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:
$ cd /sapcd2/IM_HPUX_PARISC
08/27/2007 PUBLIC 71/140

4 Installation
$ /sapcd2/IM_HPUX_PARISC/sapinst
n Using an alternative installation directory
If you want to use an alternative installation directory, set the environment variable TEMP,
TMP, or TMPDIR.
For more information, see Prerequisites before Starting SAPinst: All Instances [page 67].
Note
n During the installation, the default ports 21200 and 21212 are used for communication between
SAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to communicate with the GUI
server. The GUI server uses port 21212 to communicate with SAPinst GUI. You get an error
message if one of these ports is already in use by another service.
In this case, you must execute sapinst using the following parameters:
SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server>
GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>.
n To get a list of all available SAPinst properties, start SAPinst as described above with the option
-p:
./sapinst -p.
4. In the Welcome screen, choose one of the following installation services:

n SAP Systems
n Additional Software Life-Cycle Tasks
The following tables provide more information about these installation services:
n SAP Systems
You use this service to install a SAP system with usage types or software units by choosing
SAP Solution Manager 4.0 Support Release 3 SAP Systems <Database> <System Variant> Based
on AS ABAP and AS Java .
You can install the following system variants:
l Central System
l Distributed System
l High Availability System

End of: HA (UNIX)
The following tables provide an overview of the installation services available for these system
variants:
72/140 PUBLIC 08/27/2007

4 Installation
Note
l Choose the corresponding installation services from the tree structure exactly in the
order they appear for each system variant.
l To use global accounts that are configured on a separate host, you have to run the
installation service Operating System Users and Groups before you start the installation
(see table Additional Software Life-Cycle Tasks below).
l If required, install a dialog instance for a central or distributed system by choosing the
installation service SAP Solution Manager 4.0 Support Release 3 Additional Software Life-Cycle
Tasks Application Server Dialog Instance .
Installation Services for a Central System
Installation Service Remarks

Central System Installation Installs a complete SAP system including the following
instances on one host:
l Central services instance (SCS)
l Database instance
l Central instance
You can install a central system in the following parameter
modes:
l Typical Mode
If you choose the “Typical” setting, automatic default
settings will be provided. You only have to respond
to a small selection of prompts. However, you can
change any of the default settings on the parameter
summary screen.
l Custom Mode
If you choose the “Custom” setting, all installation
parameter will be prompted. In the end, you can still
change any of these parameters on the parameter
summary screen.
Installation Services for a Distributed System
Installation Services Remarks

Central Services Instance (SCS) Mandatory step in installing a distributed SAP system with
usage types or software units based on AS ABAP and AS Java.
Installs a central services instance (SCS) and prepares the
SAP global host.
08/27/2007 PUBLIC 73/140

4 Installation

Database Instance 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.
Central Instance Mandatory step in installing a distributed SAP system on
several hosts.
Installs a central instance and enables additional usage
types or software units.
You must have finished the database instance installation.
Installation Services for a High Availability System

Central Services Instance Installs a central services instance for ABAP (ASCS) and prepares the SAP
for ABAP (ASCS) global host
Central Services Instance Installs a central services instance (SCS)
(SCS)
Database Instance Installs a database instance
Central Instance Installs a central instance and enables additional usage types or software
units
Dialog Instance Installs a dialog instance
n Additional Software Life-Cycle Tasks

You use this service to perform the following tasks or to install the following components:
Additional Preparation Tasks These preparation tasks comprises:
l Operating System Users and Groups
Allows you to use global accounts that are configured on a separate
host.
Caution
Perform this task before you start the installation of your SAP
system.
l 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
74/140 PUBLIC 08/27/2007

4 Installation

information, see Running the Prerequisites Checker in Standalone Mode [page
38].
Application Server Choose Application Server <Database> Dialog Instance to install
one or more dialog instance(s) in an already installed SAP system,
if required.
Java Add-In for ABAP Choose this service to install usage types based on AS Java to an already
installed SAP ABAP system.
For more information, see Installing a Java Add-In for an Existing ABAP
System with SAPinst [page 76].
System Copy Choose this service to perform a system copy.
For more information, see the system copy guide,
which is available at SAP Service Marketplace at:
http://service.sap.com/instguidesnw70 Installa-
tion
Uninstall Choose this service to uninstall your SAP Solution Manager system.
For more information, see Deleting an SAP System Using SAPinst [page 126]
5. Follow the instructions in the SAPinst input dialogs and enter the required parameters.
Note
To find more information on each parameter during the input phase of the installation, position
the cursor on the field of the respective parameter and press F1 .
After you have entered all requested input parameters, SAPinst displays the Parameter Summary screen.
This screen shows both the parameters that you entered and those that SAPinst set by default.
6. If required, change the displayed parameters as follows:
a) Select the parameters you want to change.
b) Choose Revise.
SAPinst displays input screens for the selected parameters.
c) Enter the new values for the parameters.
7. To start the installation choose Start.
SAPinst starts the installation and displays the progress of the installation.
8. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after SAPinst has finished.
Sometimes these remain in the temporary directory.
Note
If there are errors with SAPinst Self-Extractor, you can find the Self-Extractor log file
dev_selfex.out in the temporary directory.
08/27/2007 PUBLIC 75/140

4 Installation
Recommendation
We recommend that you keep all installation directories until you are sure that the system is
completely and correctly installed.
9. We recommend you to delete all files in the directory <user_home>/.sdtgui/.

10. If you have copied installation DVDs to your hard disk , you can delete these files when the
installation has successfully completed.
More Information
If you have problems during the installation, see Troubleshooting with SAPinst [page 134].
4.3.2 Installing the Java Add-In for an Existing ABAP System

(Optional)
This section describes how to install a Java Add-In for an existing SAP Solution Manager ABAP
system.
Caution
Keep in mind that you cannot install the Java Add-In for the dialog instance(s) of the existing
ABAP system. Instead, you have to uninstall the old ABAP dialog instance(s) install new ABAP+Java
dialog instance(s).
Prerequisites
Your ABAP system must be on the support package level of SAP Solution Manager 4.0 SR3 ABAP:
support package stack (SPS) 12.
Procedure
1. Start SAPinst [page 70].
2. On the Welcome screen, choose SAP Solution Manager 4.0 Support Release 3 Additional Software Life-Cycle
Tasks Java Add-In for ABAP <database> <system variant> .
3. Choose the corresponding installation services from the tree structure exactly in the order they
appear for each system variant, as shown in the following tables:
Installation Services for a Java Add-In for ABAP ‒ Central or Distributed System

Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) and adds usage
types or software units based on AS Java
76/140 PUBLIC 08/27/2007

4 Installation

Database Instance Java Add-In Installs the Java schema in the database of your ABAP system
Central Instance Java Add-In Adds usage types or software units based on AS Java
Caution
When performing an upgrade installation, before you use
this service, uninstall the old ABAP dialog instance(s).
Installation Services for a Java Add-In for ABAP ‒ High-Availability System

Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) and adds usage
types or software units based on AS Java
Database Instance Java Add-In Installs the Java schema in the database of your ABAP system
Central Instance Java Add-In Adds usage types or software units based on AS Java
Dialog Instance Installs an ABAP+Java dialog instance in a high-availability
system
Caution
When performing an upgrade installation, before you use
this service, uninstall the old ABAP dialog instance(s).
4. Follow the instructions in the SAPinst input dialogs and enter the required parameters.
Note
SAPinst prompts you for the production client of your ABAP system, which is where you install
the Java Add-In.
After you have entered all required input parameters, SAPinst starts the installation and displays
the progress of the installation.
Result
After running these installation services, your ABAP+Java system consists of the following instances:
n Java central services instance (SCS)
n ABAP+Java database instance
n ABAP+Java central instance
08/27/2007 PUBLIC 77/140

4 Installation
Caution
You cannot install the Java Add-In for the dialog instance(s) of the existing ABAP system. Instead,
you have to install new ABAP+Java dialog instances as follows:
On the Welcome screen, choose <SAP system> Additional Software Life-Cycle Tasks Application Server
<database> Dialog Instance .
4.3.3 Using SAPinst GUI
The following table shows the most important functions that are available in SAPinst GUI:
SAPinst GUI Functions
Button / Function Key / Menu Entries Description

F1 Displays detailed information about each input
parameter.
Exit Cancels the installation with the following options:
n Stop
Stops the installation without further changing the
installation files. You can restart SAPinst to continue
the installation later from this point.
n Continue
Continues the installation.
Log off Stops the SAPinst GUI, but SAPinst and the GUI server
continue running.
Note
If for some reason 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 81].
Retry Performs the installation step again (if an error has
occurred).
Stop Stops the installation without further changing the
installation files. You can continue the installation later
from this point.
Continue Continues with the option you have chosen before.
78/140 PUBLIC 08/27/2007

4 Installation
4.3.4 Interrupted Installation with SAPinst
The SAP system installation might be interrupted for one of the following reasons:
n An error occurred during the dialog or processing 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 about the choices listed in
the table below as well as a path to a log file that contains detailed information about the error.
n You interrupted the installation by choosing Exit in the SAPinst menu.
The following table describes the options in the dialog box:
Option Definition
Retry SAPinst retries the installation from the point of failure without repeating
any of the previous steps.
This is possible because SAPinst records the installation progress in the
keydb.xml file.
We recommend that you view the entries in the log files, try to solve the
problem and then choose Retry.
If the same or a different error occurs again, SAPinst displays the same
dialog box again.
Stop 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.
Continue SAPinst continues the installation from the current point.
Note
You can also terminate SAPinst by choosing Ctrl + C . However, we do not recommend that you
use Ctrl + C , because this kills the process immediately .
Procedure
This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or
to continue an interrupted installation after an error situation.
1. Log on to your local UNIX host as user root.
Caution
database.
2. Mount your Installation Master DVD.
08/27/2007 PUBLIC 79/140

4 Installation
Note
Mount the DVD locally. We do not recommend using Network File System (NFS).
3. Enter the following commands:

cd <Installation_Master_DVD>/IM_<OS>
./sapinst
4. From the tree structure in the Welcome screen, select the installation service that you want to
continue and choose Next.
Note
If there is only one component to install, the Welcome screen does not appear.
The What do you want to do? screen appears.

5. In the What do you want to do? screen, decide between the following alternatives and confirm with OK.
Alternative Behavior
Run a new Installation SAPinst does not continue the interrupted installation. Instead, it moves
the content of the old installation directory and all installation-specific
files to the backup directory. Afterwards, you can no longer continue
the old installation.
For the backup directory, the following naming convention is used:
<log_day_month_year_hours_minutes_seconds> (for example,
log_01_Oct_2003_13_47_56).
Continue old installation SAPinst continues the interrupted installation from the point of failure.
4.3.5 Performing a Remote Installation with SAPinst

(Optional)
You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the
GUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is the
host from which you control the installation with SAPinst GUI.
Prerequisites
n The remote host meets the prerequisites before Starting SAPinst [page 67].
n Both computers are in the same network and can “ping” each other.
To test this:
l Log on to your remote host and enter the command ping <local host>.
l Log on to the local host and enter the command ping <remote host>.
80/140 PUBLIC 08/27/2007

4 Installation
Procedure
1. Log on to your remote host as user root.
Caution
database.
2. Mount the Installation Master DVD.
3. Enter the following commands:
./sapinst -nogui
For more information, see Running SAPinst on UNIX [page 70].
SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at
the command prompt:
guiengine: no GUI connected; waiting for a connection on host <host_name>, port
<port_number> to continue with the installation.
4. Start SAPinst GUI on your local host, as described in Starting SAPinst GUI Separately [page 81].
4.3.6 Starting SAPinst GUI Separately (Optional)
You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI
separately in the following cases:
n 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.
n You want to perform a remote installation [page 80].
If you want to run SAPinst GUI on a different host from SAPinst and the GUI server, you have to
start SAPinst GUI separately.
Prerequisites
You have installed the Java Development Kit [page 59] on the host on which you want to start SAPinst
without SAPinst GUI.
Starting SAPinst GUI on a Windows Platform

1. Log on as a member of the local administrators group.
2. Insert the SAP Installation Master DVD into your DVD drive.
3. To change to the relevant directory enter the following command:
cd <DVD drive>:\IM_WINDOWS<platform>
4. Start SAPinst GUI in one of the following ways:
08/27/2007 PUBLIC 81/140

4 Installation
n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following
command:
startinstgui.bat
SAPinst GUI uses the local host as default.
n If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation),
enter the following command:
startinstgui.bat -host <host_name>
<host_name> is the host name of the installation host.
Note
l If you enter the command without additional parameters, SAPinst GUI uses the local
host as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. As
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 dialog of the installation appears and you can perform the remote installation
from your local host.
l For a list of options to start SAPinst GUI, change to the same directory as your SAPinst
executable and enter the command startinstgui.bat -h.
Starting SAPinst GUI on a UNIX Platform

Caution
database.
2. Mount your installation DVD.
Note
Mount the DVD locally. We do not recommend that you use Network File System (NFS).
3. To change to the mount directory enter the following command:

4. Start the SAPinst GUI in one of the following ways:
n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following
command without additional parameters:
./startInstGui.sh
SAPinst GUI uses as default the local host.
82/140 PUBLIC 08/27/2007

4 Installation
n If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation),
enter the following command with additional parameters:
./startInstGui.sh -host <host_name>
<host_name> is the host name of the installation host.
Note
l If you enter the command without additional parameters, SAPinst GUI uses the local
host as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. As
SAPinst and 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 host on which SAPinst is running and choose Log on.
The first dialog of the installation appears and you can perform the remote installation
from your local host.
l For a list of options to start SAPinst GUI, change to the same directory as your SAPinst
executable and enter the command ./startInstGui.sh -h.
4.3.7 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
sapdbXXs = 47XX/tcp
sapgwXX = 33XX/tcp
sapgwXXs = 48XX/tcp
where XX is set from 00 to 99.
Note
If there is more than one entry for the same port number, this is not an error.
08/27/2007 PUBLIC 83/140

5 Post-Installation
5 Post-Installation
Note
Before you perform post-installation steps, make sure that you have read the release notes for the
software components that you have installed and that you want to use for your IT scenario. You can
find these release notes on SAP Service Marketplace at:
http://service.sap.com/releasenotes.
You perform the following post-installation steps:

1. You check whether you can log on to the application server [page 86].
2. You install the SAP license [page 87].
Caution
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
3. You install the SAP Online Documentation [page 88].
Caution
4. You configure the remote connection to SAP support [page 88].
Caution
5. You perform initial ABAP configuration [page 89].
Caution
6. You apply the latest kernel and Support Packages [page 91].
7. You perform a full backup of the installation [page 93].
8. You perform post-installation steps for Adobe Document Services [page 94].
9. You perform the required post-installation steps for high availability [page 96].
08/27/2007 PUBLIC 85/140

5 Post-Installation
5.1 Logging On to the Application Server
Caution
End of: HA (UNIX)
10. If required, you install MaxDB administration tools [page 98].

11. If required, you install Secure Sockets Layer (SSL) for MaxDB [page 100].
12. You back up the MaxDB database [page 104].
13. You ensure user security [page 104].
14. You check the Java documentation [page 107] for information that is relevant for running your Java system.
15. You configure SAP Solution Manager [page 108].
5.1 Logging On to the Application Server
You need to check that you can log on to the SAP system using the following standard users.
ABAP Users
User User Name Client

SAP system user SAP* 000, 001, 066
DDIC 000, 001
Java User
User User Name Storage: ABAP System

Administrator J2EE_ADMIN (default) or the name you gave this user during the
installation process.
Prerequisites
n The SAP system is up and running.
n You have already installed a front end.
Logging On to the ABAP Application Server

1. Start SAP Logon on the host where you have installed the front end as follows:
n SAP GUI for Windows:
Choose Start All Programs SAP Front End SAP Logon .
n SAP GUI for Java:
Choose Start All Programs SAP Clients SAP GUI for Java<Release> .
86/140 PUBLIC 08/27/2007

5 Post-Installation
5.2 Installing the SAP License
Note
You can also enter the command guilogon in the SAP GUI installation directory to start
SAP GUI for Java.
The SAP Logon appears.

2. Create a logon entry for the newly installed system in the SAP Logon.
For more information about creating new logon entries, press F1 .
3. When you have created the entry, log on as user SAP* or DDIC.
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
Note
You must always enter a two-digit number for <Instance_Number>. For example, do not enter 1
but instead enter 01.
Example
If you installed the SAP NetWeaver Application Server Java on host saphost06 and the instance
number of your SAP NetWeaver Application Server Java is 04, enter the following URL:
http://saphost06:50400
The start page of the SAP NetWeaver Application Server Java appears in the Web browser.
2. Log on by pressing the link of any of the provided applications, for example the SAP NetWeaver
Administrator or the System Information.
Note
To deactivate AS Java, proceed as follows:
1. Call transaction RZ11.
2. In the instance profile of every installed SAP instance, set parameter rdisp/j2ee_start from 1
to 0.
5.2 Installing the SAP License
Caution
08/27/2007 PUBLIC 87/140

5 Post-Installation
5.3 Installing the SAP Online Documentation
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 four 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
For information about the installation procedure for the SAP license, see:
http://help.sap.com/nw70 SAP NetWeaver SAP NetWeaver Library Technology Consultant’s Guide
Cross-NetWeaver Configurations SAP License Key
More Information
For more information about SAP license keys, see SAP Service Marketplace at
http://service.sap.com/licensekey.
5.3 Installing the SAP Online Documentation
Caution
SAP currently provides an HTML-based solution for the online documentation, including the
Application Help, Glossary, Implementation Guide (IMG), and Release Notes. You can display the
documentation with a Java-compatible Web browser on all front-end platforms supported by SAP.
You can always find the up-to-date SAP online documentation at http://help.sap.com.
Process
Install the SAP online documentation in your SAP system as described in the README.TXT file
contained in the root directory of the online documentation DVD, delivered as part of the installation
package.
5.4 Configuring Remote Connection to SAP Support
Caution
88/140 PUBLIC 08/27/2007

5 Post-Installation
5.5 Performing Initial ABAP Configuration
SAP offers its customers access to support and a number of remote services such as the EarlyWatch
Service or the GoingLive Service. Therefore, you have to set up a remote network connection to SAP.
For more information, see SAP Service Marketplace at http://service.sap.com/remoteconnection.
Caution
Here you find information about how to perform initial ABAP system configuration.
Procedure
1. Go to the following place in the SAP Library:
http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability
2. Check the documentation on the following configuration steps:
n Configuring the transport management system
For more information, see Solution Life Cycle Management by Key Capability Software Life Cycle
Management Software Logistics Change and Transport System .
n Performing basic operations
For more information, see the relevant section in Solution Life Cycle Management by Key Capability
System Management :
Operation Section in SAP Documentation
Set up operation modes ‒ Configuration Operation Modes
transaction RZ04
Set up logon groups ‒ Configuration Logon Load Distribution SAP Logon
transaction SMLG
Set up administrators Background Processing Authorizations for Background Processing
Schedule background jobs Background Processing
Install a printer SAP Printing Guide
Configure the system log Tools for Monitoring the System System log Configuring the System Log
n Configuring work processes

For more information about instance profiles, which is where work processes are defined,
see Solution Life Cycle Management by Key Capability System Management Configuration Profiles
Profile Files Instance Profiles .
08/27/2007 PUBLIC 89/140

5 Post-Installation
Note
SAPinst installs SAP systems with a minimum number of work processes. This is only an
initial configuration to get you started after the installation. It is not detailed enough for a
production system because the optimal number of each type of work process depends on the
system resources and on the number of users working in each SAP system application. For a
detailed configuration contact SAP Technical Consulting.
n Installing languages and performing language transport

l Installing languages using transaction I18N:
u If you want to use English only, you must activate the default language settings once.
u If you want to use languages other than English, you must install them and activate the
language settings.
For more information on configuring the language settings, see the online documentation
in transaction I18N I18N Menue I18N Customizing .
l Performing language transport using transation SMLT:
For more information on performing the language transport using transaction SMLT.
see Solution Life Cycle Management by Key Capability Software Life Cycle Management Software
Logistics Change and Transport System Language Transport. .
n Meeting the Requirements for the SAP Internet Solution
As of SAP NetWeaver ’04, the SAP Internet Transaction Server (SAP ITS) is integrated into
the SAP NetWeaver component SAP Web Application Server as an Internet Communication
Framework (ICF) service, which you can access, like other services, through the Internet
Communication Manager (ICM). With the SAP ITS integrated in the SAP Web Application
Server, the Web browser now communicates directly with the SAP system. Furthermore, all
SAP ITS-related sources, such as service files, HTML templates, or MIME files, are now stored in
the database of the system.
The SAP-integrated ITS supports the following functions:
l SAP GUI for HTML
l Internet Application Component (IAC) runtime or Web Transaction technology
The SAP-integrated ITS does not support the following functions:
l SAP ITS Flowlogic runtime
l WebRFC
l Web Reporting
l GUI XT
As of SAP NetWeaver 7.0, these functions are no longer supported at all. Applications based on
any of the no longer supported functions must be migrated.
SAP ITS 6.20 is compatible with SAP systems up to and including SAP systems based on SAP
NetWeaver ’04. However, it is not compatible with SAP systems based on SAP NetWeaver 7.0 or
higher. This means that as of SAP NetWeaver 7.0, each application based on ITS technology can
only be used via SAP integrated ITS.
90/140 PUBLIC 08/27/2007

5 Post-Installation
5.6 Applying the Latest Kernel and Support Packages
l For information on how to configure the SAP integrated ITS, see Application Platform by Key
Capability ABAP Technology UI Technology ITS / SAP@Web Studio (BC-FES-ITS) SAP ITS in
the SAP Web Application Server Configuration .
l For more information about memory requirements of the ITS, see SAP Note 742048.
n Maintaining address data
For more information on maintaining the company address in your SAP system using
transaction SU01, see Application Platform by Key Capability Business Services Business Address
Services (BC-SRV-ADR) Addresses in User Administration Maintenance of Address Data .
Note
You must maintain your company address to create ABAP system users.
You use this procedure to apply the latest kernel and Support Packages for your SAP system from SAP
Service Marketplace.
Note
All corrective software packages, including Support Packages (Stacks) for SAP NetWeaver 7.0 (2004s)
and subsequent versions, as well as all applications which are based on this software (including
SAP Business Suite 2005), released after April 2, 2007, will be available exclusively through the
Maintenance Optimizer in SAP Solution Manager.
For more information on the Maintenance Optimizer,
see http://service.sap.com/solutionmanager Functions in Detail Support Area Maintenance
Optimizer .
A newly installed SAP Solution Manager 4.0 SR3 system contains SAP Solution Manager 4.0 support
package stack (SPS) 12. You can run the system on this SPS level without applying further support
packages or you can apply further support packages that are available on SAP Service Marketplace. On
the SPS level of your SAP Solution Manager system depends the configuration guide which you have
to use later on (for more information, see Configuring SAP Solution Manager [page 108]).
Caution
Make sure that the entry DIR_CT_RUN exists in the instance profile. Otherwise you cannot restart the
system after patches have been applied.
See also Setting Up File Systems [page 50].
You can use Java Support Package Manager (JSPM) to apply both the latest ABAP+Java or Java kernel
and Java support packages.
08/27/2007 PUBLIC 91/140

5 Post-Installation
JSPM is a Java standalone tool that you can use with SAP NetWeaver 7.0. JSPM uses the Software
Deployment Manager (SDM) to apply support packages and patches and to deploy software
components.
For more information about JSPM and how to use this tool, see http://help.sap.com/nw70 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
You can also use the Support Package Manager to apply the latest ABAP support packages.
For more information about the Support Package Manager and how to use this tool, see
http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life
Cycle Management by Key Capability Software Life Cycle Management Software Maintenance Support Package
Manager
Prerequisites
To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you
can find on SAP Service Marketplace 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.
Procedure
1. Apply the latest kernel.
You must always replace the installed kernel with the latest kernel from SAP Service Marketplace.
In particular, you must replace the installed kernel if:
n You installed the kernel executables locally on every host.
n Your central instance host runs on a different operating system than your dialog instance host.
For more information about how to download a kernel, see SAP Note 19466.
To exchange the ABAP+Java kernel, you can use Java Support Package Manager (JSPM).
2. Apply Support Packages.
a) For up-to-date information about recommended combinations of Support Packages and
patches, see SAP Service Marketplace at:
http://service.sap.com/sp-stacks
b) Alternatively, you can download Support Packages from SAP Service Marketplace at:
http://service.sap.com/patches
c) Apply the ABAP Support Packages to your SAP system with the help of the Support Package
Manager (formerly called SAP Patch Manager, transaction SPAM).
d) Apply the Java Support Packages to your SAP system with the help of the Java Support Package
Manager (JSPM).
For more information about the availability of Support Packages, see the SAP Service Marketplace
at:
http://service.sap.com/ocs-schedules
92/140 PUBLIC 08/27/2007

5 Post-Installation
5.7 Performing a Full Installation Backup
Note
The SAP Note Assistant lets you load, implement, and organize individual SAP Notes efficiently. It
also recognizes dependencies between SAP Notes, Support Packages, and modifications.
For more information, see the SAP Service Marketplace at:
http://service.sap.com/noteassistant
5.7 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 backed-up data for a restore.
Caution
Make sure that you fully back up your database so that you can recover it later if necessary.
You need to back up the following directories and files:

n All database-specific directories
n All SAP-specific directories:
l /usr/sap/<SAPSID>
l /usr/sap/trans
l <sapmnt>/<SAPSID>
l Home directory of the user <sapsid>adm
n The root file system
This saves the structure of the system and all configuration files, such as file system size, logical
volume manager configuration, and database configuration data.
Note
This list is only valid for a standard installation.
Prerequisites
n You have completed client maintenance, such as the client copy. For more information, see
Configuring SAP Solution Manager [page 108].
n You have logged on [page 86] as user <sapsid>adm and stopped the SAP system and database [page 120].
n This procedure works on all hardware platforms. For more information on operating
system-specific backup procedures, see your operating system documentation.
Backing Up the Installation

2. Manually create a compressed tar archive that contains all installed files:
08/27/2007 PUBLIC 93/140

5 Post-Installation
5.8 Post-Installation Steps for Adobe Document Services
n Saving to tape:
tar —cf — <file_system> | compress —c > <tape_device>
n Saving to the file system:
tar —cf — <file_system> | compress —c > ARCHIVENAME.tar.Z
Restoring Your Backup
Caution
Check for modifications in the existing parameter files before you overwrite them when restoring
the backup.

2. Restore the data that you previously backed up:
n Restoring the data from tape:
cat <tape_device> | compress —cd | tar —xf —
n Restoring the data from the file system:
cat ARCHIVENAME.tar.Z | compress —cd | tar —xf —

You perform the following post-installation steps:
n You assign the required roles to users ADSUSER and ADS_AGENT [page 94].
n You check the IIOP service and the startup properties [page 95].
n You perform quick tests for Adobe Document Services (ADS) [page 96].
5.8.1 Assigning Roles to Users ADSUSER and ADS_AGENT
During the installation SAPinst created the users ADSUSER for basic authentication and ADS_AGENT
for processing forms between an ABAP and a Java environment.
After the installation you have to assign the required authorization roles manually to these users in
the ABAP system, as described below.
Assigning Role SAP_BC_FP_ICF to ADS_AGENT

1. Log on to the ABAP system with user DDIC or SAP*.
2. Call transaction SU01.
3. Enter ADS_AGENT in the User field.
4. Choose User Names Change .
5. Choose the Roles tab and assign the role SAP_BC_FP_ICF to the user ADS_AGENT.
94/140 PUBLIC 08/27/2007

5 Post-Installation
Creating Role ADSCallers and Assigning it to ADSUSER

1. Log on to the ABAP system [page 86].
2. Call transaction PFCG.
3. Enter ADSCallers in the Role field.
4. Choose Role Create .
5. On the Create Roles screen, choose Role Save .
6. Choose the User tab and assign the user ADSUSER in the User ID field.
5.8.2 Checking the IIOP Service and the Startup Properties
After the installation of the Adobe document services and before performing any other configuration
steps you need to check special settings on the central instance host. If necessary, you need to adapt
these settings manually.
Procedure
1. Start the conguration tool of the AS Java by running
/usr/sap/<SAPSID>/<instance_name>/j2ee/configtool.sh.
The Config Tool screen appears.
2. Check if the startup mode of the service iiop is set to always:
a) In the left frame, open the tree Cluster data Cluster data Global dispatcher configuration Services .
b) Choose service iiop.
c) The field Startup mode in the right frame must be set to always. If it is not true, apply the value
always.
d) Choose Apply changes.
e) Repeat the steps b. to d. for the following path: Cluster data Cluster data Global server
configuration Services .
3. Check if the Java startup property for Adobe document services is set as follows:
a) Select Cluster data Cluster data instance_<IDxxxx> server_<IDxxxx> .
b) In the right frame, check if the following line exists in the Java Parameters area of the tab General:
-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine. services.ts.jts.ots.PortableInterceptor.JTSIni-
tializer
If the line does not exist, add the line to this section.
4. Exit the configuration tool.
5. If you have applied new values during the procedure above, you need to restart the AS Java
to adapt the new settings.
08/27/2007 PUBLIC 95/140

5 Post-Installation
5.9 High Availability: Post-Installation Steps
5.8.3 Installation Check and Quick Tests 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 ones you still need to perform manually.
Prerequisites
Adobe document services are installed on your system.
Procedure
Check the ADS configuration as described in http://help.sap.com/nw70 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 .
More Information
The Adobe Document Services Configuration Guide is also available in PDF form at
http://service.sap.com/adobe SAP Interactive Forms by Adobe Media Library Documentation Adobe
Document Services - Configuration Guide NW 2004s
5.9.1 Setting Up Licenses
Caution
If your high-availability (HA) installation is running a two-node switchover cluster, you need to order
two SAP licenses [page 87]. When we receive confirmation from your vendor that you are implementing
a switchover environment, we provide two license keys for your system, one 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 (SCS) instance runs. There
is no license problem when only the database is switched over.
96/140 PUBLIC 08/27/2007

5 Post-Installation
A switchover involving the central services (SCS) instance affects the licensing mechanism, so for
this case you must have two licenses, which you can install in parallel. There is no license problem
when only the database is switched over.
Procedure
1. Execute the following as user <sid>adm on the primary and secondary node where the ABAP SCS
instance runs for every license key you obtain from SAP:
saplicense -install
2. Run the SCS instance on the primary host, node A.
3. 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.
4. Switch over the SCS instance to the backup host, node B.
5. To find the hardware ID of the backup host, run the Visual Administrator on node B and choose
CI Host License Adapter .
The hardware ID is displayed in the Visual Administrator.
6. To obtain the two license keys, enter the hardware IDs for the primary and backup hosts in SAP
Service Marketplace at:
http://service.sap.com/licensekey
7. Open the Visual Administrator on the node where the SCS instance is running and choose CI
Host License Adapter and import the file containing the two licenses.
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.2 Taking Precautions for Transport
Caution
With a high-availability (HA) installation you need to take precautions before you perform a transport.
TPPARAM contains parameter settings for the transport control program tp, which is used for exports
and imports. It also includes the parameter <SID>/dbhost, which is used to address the database host.
Procedure
Set <SID>/dbhost to the virtual host name of the DB instance.
08/27/2007 PUBLIC 97/140

5 Post-Installation
5.10 Installing Administration Tools for MaxDB
This lets you use the transport system for the normal maintenance of ABAP programs, but still allows
transparent operation in the event of a switchover.
End of: HA (UNIX)
This section describes how to install the following administration tools for MaxDB and SAP liveCache
on Windows front ends:
n Database Manager GUI
You can use Database Manager GUI to administer databases, including remote ones.
n SQL Studio (GUI)
You can use SQL Studio (GUI) to send SQL statements to the database and evaluate the results.
For more information on these tools, see the following documentation:
n Database Manager GUI
n SQL Studio (GUI)
You can find this documentation as well as information about additional MaxDB tools at:
http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Application
Platform by Key Capability Platform-Wide Services Databases MaxDB Tools
Prerequisites
n You can install these administration tools on any Windows PC in your network, even if your
database runs on UNIX. From the PC with the installed administration tool, you can then
administer the database or send queries to it.
n Your PC must meet the following minimum operating system requirements:
Installing Administration Tools for MaxDB
Operating System Version

Windows NT 4.0 SP 4
Windows 2000 Any
Windows 2003 Any
n Your PC must meet the following minimum hardware requirements:

l Pentium II
l 64 MB RAM
l 100 MB disk space
n You can get the required files from one of the following:
98/140 PUBLIC 08/27/2007

5 Post-Installation
l The MaxDB RDBMS or SAP liveCache DVD

l By downloading from SAP Service Marketplace at:
http://service.sap.com/patches Entry by Application Group Additional Components MaxDB
MaxDB GUI COMPONENTS/TOOLS
Caution
If MaxDB or liveCache is installed on the PC, you must not install the administration tools in the
same directory. You can check the directories used by MaxDB or liveCache as follows:
dbmcli -d <DBSID> -u <controluser>,<password> dbm_getpath
IndepDataPath
dbmcli -d <DBSID> -u <controluser>,<password> dbm_getpath
IndepProgPath
Procedure
1. Start the installation as follows:
n If you are using the MaxDB RDBMS DVD:
l DBMGUI
<DVD>:\MaxDB_Windows_<Processor>\SETUPS\DBM76.EXE
l SQL Studio
<DVD>:\MaxDB_Windows_<Processor>\SETUPS\SQLSTD76.EXE
n If you are using the liveCache DVD:
l DBMGUI
<DVD>:\LC_Windows_<Processor>\SETUPS\DBM76.EXE
l SQL Studio
<DVD>:\LC_Windows_<Processor>\SETUPS\SQLSTD76.EXE
n If you are using the files from SAP Service Marketplace, simply execute the downloaded
.EXE file.
An installation shield guides you through the installation.
Note
If you already have an older version of the administration tools installed on the PC, the
installation shield offers to upgrade it for you.
2. If you are prompted to restart the PC after the installation, make sure that you first bring down
any databases that are running as follows:
dbmcli -d <DBSID> -u <controluser>,<password> db_offline
08/27/2007 PUBLIC 99/140

5 Post-Installation
5.11 Secure Sockets Layer Protocol for Database Server Communication
5.11 Secure Sockets Layer Protocol for Database Server

Communication
The MaxDB database server supports the Secure Sockets Layer (SSL) protocol. You can use this
protocol to communicate between the database server and its client, here the Application Server
(AS). SSL guarantees encrypted data transfer between the MaxDB database server and its client
applications. In addition, the server authenticates itself to the client.
Caution
There is a performance cost for SSL since the data has to be encrpyted, which requires time and
processing power.
To use SSL you need to:

1. Install the SAP cryptographic library [page 100] on the client host and on the server host machines
2. Generate the Personal Security Environment [page 101] (PSE) on the server (SSL Server PSE) and on the
client (SSL Client PSE).
5.11.1 Installing the SAP Cryptographic Library
The cryptographic functions required to build a database server-client connection using Secure
Sockets Layer (SSL) protocol are supplied by the SAP Cryptographic Library. Therefore, you need to
install the SAP Cryptographic Library on the host machine of the MaxDB database server and the
SAP Application Server (AS).
The installation package sapcrypto.car consists of the following:
n SAP Cryptographic Library libsapcrypto.so/sl
n License ticket ticket
n Configuration tool sapgenpse.exe
You use the configuration tool to generate key pairs and PSEs.
Caution
The SAP Cryptographic Library is subject to German export regulations and might not be available
to some customers. In addition, the library might be subject to the local regulations of your country.
These regulations might further restrict import, use, and export or re-export of cryptographic
software.
For more information, contact your local SAP representative.
Prerequisites
Download the appropriate SAP Cryptographic Library installation package for your operating system
from SAP Service Marketplace at http://service.sap.com/swcenter.
100/140 PUBLIC 08/27/2007

5 Post-Installation
Procedure
1. Unpack the installation package for the SAP Cryptographic Library using sapcar.exe, which you
can find for example on your Installation Master DVD, using the following command:
car -xvf SAPCRYPTO.CAR
Note
The remainder of the procedure, as described below, does not apply to client applications such as
SQL Studio, which do not recognize an “independent” directory. In this case, you must copy the
SAPCRYPTO installation package to the installation directory of the application. In this directory
you need to create a directory sec, into which you copy the ticket file.
2. Copy the sapcrypto library to the lib subdirectory of the “independent program” directory.
You can find the value of the independent program directory by entering the following command:
dbmcli dbm_getpath IndepProgPath
Example
The independent program directory might be called the following:
/sapdb/programs/lib
3. Copy the configuration tool sapgenpse.exe to the directory <independent program>\lib.

4. Create a subdirectory called sec under the “independent data” directory and copy the ticket
file into it.
Example
The result might look like the following:
/sapdb/data/sec/ticket
5. Make sure that the directory and the files that the sec directory contains ‒ including the ticket
file and the SSL Server PSE ‒ belong to the user lcown and the group lcadm, and that the rights
are restricted to 0600.
Result
The SAP Cryptographic Library is copied to the application server and the environment is correctly
configured so that the server can find the library at run time.
5.11.2 Generating the Personal Security Environment
The information required by the database server or client application to communicate using Secure
Sockets Layer are stored in the Personal Security Environment (PSE). The required information differs
according to whether SSL PSE is for the server or client:
08/27/2007 PUBLIC 101/140

5 Post-Installation
n SSL Server PSE

This PSE contains the security information from the database server, for example, the
public-private cryptographic key pair and certificate chain. To install the SSL Server PSE you
need to generate the PSE. You can either do this for a single database server or system-wide. The
SSL Server PSE is called SDBSSLS.exe.
n SSL Client PSE
The client requires an anonymous certificate called SDBSSLA.exe, which contains the list of the
public keys of trustworthy database servers.
Procedure
To generate the SSL Server PSE, proceed as follows:
Note
You need to know the naming convention for the distinguished name of the database server.
The syntax of the distinguished name, which you enter in the procedure below, depends on the
Certification Authority (CA) that you are using.
1. Change to the <independent programs>\lib directory.

2. Set up the following environment variable:
SECUDIR=<independent data>\sec
3. Create a SSL Server PSE, SDBSSLS.pse, and generate a certificate request file, certreq, in the
directory defined by SECUDIR (see previous step):
sapgenpse gen_pse -v -r <SECUDIR>\certreq -p SDBSSLS.pse “<your distinguished
name>”
For each database server that uses a server-specific PSE, you must set up a unique certificate
request. If you are using a valid system-wide SSL Server PSE, you only need to set up a single
certificate request for all servers.
4. Send the certificate request to the CA for signing. You can either send it to the SAP CA or to
another CA.
You must make sure that the CA offers a certificate corresponding to the PKCS#7 certificate chain
format. Thawte CA at http://www.thawte.com offers a suitable certificate, either SSL Chained
CA Cert or PKCS#7 certificate chain format.
The CA validates the information contained in the certificate request, according to its own
guidelines, and sends a reply containing the public key certificate.
5. After you have received the reply from the CA, make sure that the contents of the certificate
request have not been destroyed during download.
For example, if you requested the certificate on a UNIX system and stored it on a Windows front
end, the formatting (that is, line indents and line breaks) is affected.
To check the contents, open the certificate request with a text editor (such as Notepad) and repair
the line indents and the line breaks.
102/140 PUBLIC 08/27/2007

5 Post-Installation
Example
This is an example of a certificate request:
-----BEGIN CERTIFICATE
REQUEST-----MIIBPzCBqQIBADAAMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD/302IT+/Y
wpignSw7U9FWneyWz3Wil0S18aFCYkRo00wCpD8UwcaC4dds4uGT6hl2WlJ0/FOtUg+EQxonZbaRrk9sTalkn1mqx3YA
-----END CERTIFICATE REQUEST-----
6. Import the reply to the SSL Server PSE:

a) Copy the text to a temporary file called srcert.
b) Enter the following command:
sapgenpse import_own_cert -c srcert -p SDBSSLS.pse
You have generated the SSL Server PSE. You can now start the XServer as usual (if it is already
running, you must stop and restart it).
7. To check whether the SSL functionality is working correctly, view the trace file niserver_<local
computer name>.trace in the <independent data>\wrk directory.
To generate the SSL Client PSE, proceed as follows:

1. Change to the <independent programs>\lib directory.
2. Set up the following environment variable:
SECUDIR=<independent data>\sec
3. Enter <independent program>/lib in the environment variable LD_LIBRARY_PATH.
4. Create an anonymous client SSL Client PSE, SDBSSLA.pse in the directory defined by SECUDIR (see
previous step):
sapgenpse gen_pse -v -noreq -p SDBSSLA.pse
You can leave the distinguished name empty.
Before you can establish an SSL connection to a database server, the server certificate must be
entered in the PK list of the anonymous client certificate.
5. To see the database server certificate, enter the following command:
„x_ping -n <servermode> -c[apture]
You can check whether to trust the database server certificate. The client certificate is not affected
by this.
6. Start the import with this command:
„x_ping -n <servermode> -i[import]
7. To administer the PSE, use the configuration tool sapgenpse. For more information enter the
following command:
sapgenpse -h
Note
For applications such as SQL Studio replace the independent data or independent program in the
above description with the installation directory.
08/27/2007 PUBLIC 103/140

5 Post-Installation
5.12 Backing Up the MaxDB Database
5.12 Backing Up the MaxDB Database
You need to define backup media and back up the MaxDB database using Database Manager GUI
(DBMGUI).
Prerequisites
n You have finished client maintenance.
n You have installed Database Manager GUI [page 98].
n You can find more information on backing up the database at:
Platform by Key Capability Platform-Wide Services Databases MaxDB Tools Database Manager
GUI Backup
Procedure
1. Define the backup medium as described in Managing the Backup Media in the above documentation.
2. Back up the database as described in Backing Procedures in the above documentation.
5.13 Ensuring User Security
You need to ensure the security of the users that SAPinst creates during the installation. 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.
Recommendation
In all cases, the user ID and password are only encoded 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 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.
104/140 PUBLIC 08/27/2007

5 Post-Installation
Prerequisites
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.
Procedure
For the users listed below, take the precautions described in the relevant SAP security guide, which
you can find on SAP Service Marketplace at http://service.sap.com/securityguide:
Operating System and Database Users
User Type User Comment

Operating system user sqd<dbsid> MaxDB database administrator
(that is, the owner of the database
files)
ABAP+Java Users
User User Name Comment

SAP system user SAP* User exists at least in SAP system clients
000, 001 and 066.
DDIC User exists at least in SAP system clients
000 and 001.
EARLYWATCH User exists at least in SAP system client
066.
SAPCPIC User exists at least in SAP system clients
000 and 001.
Administrator The name that you gave this user This user’s password is stored in secure
during the installation or the default storage. Therefore, whenever you
name J2EE_ADMIN change the administrator’s password,
you must also change the password in
secure storage.
For more information, see Checking the
SAP Java Documentation [page 107].
Guest The name that you gave this user ‒
during the installation or the default
name J2EE_GUEST
Communication user for The name that you gave this user ‒
the J2EE Engine during the installation or the default
name SAPJSF.
08/27/2007 PUBLIC 105/140

5 Post-Installation
User User Name Comment

Users for Adobe ADSUSER User exists at least in SAP system clients
Document Services (ADS) 000 and 001.
ADS_AGENT User exists at least in SAP system clients
000 and 001.
Data supplier user The name that you gave this user User exists at least in SAP system clients
for System Landscape during the installation. 000 and 001.
Directory (SLD) The recommended name is SLDDSUSER.
(optional)
Note
SAPinst created this user automatically
if you chose Configure local SLD during
the installation.
ABAP API user for System The name that you gave this user User exists at least in SAP system clients
Landscape Directory (SLD) during the installation. 000 and 001.
(optional) The recommended name is SLDAPIUSER.
Note
the installation.
Java Add-In Users for Users Stored in the ABAP System
User User Name Storage: ABAP System Comment

Administrator The name that you gave this user This user’s password is stored in secure
during the installation or the default storage. Therefore, whenever you
name J2EE_ADMIN change the administrator’s password,
you must also change the password in
secure storage.
For more information, see Checking the
SAP Java Documentation [page 107].
Guest The name that you gave this user ‒
during the installation or the default
name J2EE_GUEST
Communication user for The name that you gave this user ‒
the J2EE Engine during the installation or the default
name SAPJSF
Users for Adobe ADSUSER User exists at least in the clients 000 and
Document Services (ADS) 001 of the ABAP system.
ADS_AGENT User exists at least in the clients 000 and
001 of the ABAP system.
106/140 PUBLIC 08/27/2007

5 Post-Installation
5.14 Checking the SAP Java Documentation
User User Name Storage: ABAP System Comment

Data supplier user The name that you gave this user User exists at least in the clients 000 and
for System Landscape during the installation. 001 of the ABAP system.
Directory (SLD) (optional) The recommended name is SLDDSUSER.
Note
the installation.
ABAP API user for System The name that you gave this user User exists at least in the clients 000 and
Landscape Directory (SLD) during the installation. 001 of the ABAP system.
(optional) The recommended name is SLDAPIUSER.
Note
the installation.
5.14 Checking 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. Go to the following place in the documentation:
Platform by Key Capability Java Technology .
2. 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:
n Java cluster architecture including central services, load balancing,
and high availability.
n J2EE Engine system architecture
n SAP NetWeaver Java development infrastructure, including SAP
NetWeaver Developer Studio
Note
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.
08/27/2007 PUBLIC 107/140

5 Post-Installation
5.15 Configuring SAP Solution Manager
Manual Contents
Administration Manual This manual describes how to administer the SAP system, focusing on the
J2EE Engine. It contains information on:
n System landscape administration
n Software life-cycle management
Note
This part of the manual contains important information about:
l Installation information
l System Landscape Directory (SLD)
l Software Lifecycle Manager (SLM)
l Java Support Package Manager
l Administration of SAP NetWeaver Java Development
Infrastructure (JDI)
n J2EE Engine and J2EE Engine security

n Supportability and performance management
n Administration and configuration of Web Dynpro runtime
environment
n 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 .
Java Development 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.
Migration Manual This manual contains all the information you need to migrate an
application created in J2EE Engine 6.20.
More Information
For troubleshooting the J2EE Engine, see the J2EE Engine Problem Analysis Guide at:
Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) J2EE Engine Problem
Analysis Scenarios
To configure your SAP Solution Manager 4.0 SR3 system, you have to proceed as follows:
Procedure
1. Log on to the client 001 of the SAP Solution Manager system.
108/140 PUBLIC 08/27/2007

5 Post-Installation
2. Call transaction SPRO.

3. Choose SAP Reference IMG SAP Solution Manager Implementation Guide SAP Solution Manager
n Make sure that you have read the information in Read Me.You need to check all preparatory
steps for the Solution Manager system as well as for connected satellite systems.
n All activities under Configuration Basic Settings Standard Configuration of Basic Settings are
mandatory to ensure minimum SAP Solution Manager functionality.
n All activities under Advanced Configuration Scenario Specific Settings are optional and depend on
the functions of SAP Solution Manager that you want to use.
For more information, see the documentation Configuration Guide SAP Solution Manager
4.0 as of SP<SP level of your SAP Solution Manager system> on SAP Service Marketplace at
http://service.sap.com/solutionmanager SAP Solution Manager Installation Guides Release
4.0 .
08/27/2007 PUBLIC 109/140

6 Additional Information
The following sections provide additional information about optional preparation and
post-installation tasks:
Preparation
n Installation of Multiple Components in One Database [page 111]

n Integration of LDAP Directory Services [page 113]
Post-Installation
n Starting and stopping the SAP system [page 116].

n If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access
[page 123].
n Configuring User Management to Use an LDAP Directory [page 123].
n Initial Configuration for System Landscape Directory (SLD) [page 124]
n Initial Configuration of Adobe Document Services (ADS) [page 124]
n Heterogeneous SAP System Installation [page 125]
n Deleting an SAP System [page 126]
n Troubleshooting [page 133]
6.1 Installation of Multiple Components in One Database

(Optional)
Caution
You can install multiple SAP systems in a single database. This is called Multiple Components
in One Database (MCOD).
MCOD is available with all SAP components. 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 service. Instead, it is an option of the database instance installation.
With MCOD we distinguish two scenarios:
08/27/2007 PUBLIC 111/140

6.1 Installation of Multiple Components in One Database (Optional)
n The installation of an SAP system in a new database

n The installation of an additional SAP system in an existing database
Prerequisites
n For more information on MCOD and its availability on different platforms, see the SAP Service
Marketplace at https://service.sap.com/mcod.
n MCOD is released for Unicode installations. A prerequisite is that the MCOD system contains
Unicode instances only. SAP does not support mixed solutions.
n 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. The same applies to memory resources and disk space.
You can size multiple components in one database by sizing each individual component using the
SAP Quick Sizer and then adding the requirements together. For more information on the SAP
Quick Sizer, see the SAP Service Marketplace at https://service.sap.com/sizing.
Features
n Reduced administration effort
n Consistent system landscape for backup, system copy, administration, and recovery
n Increased security and reduced database failure for multiple SAP systems due to monitoring and
administration of only one database
n Independent upgrade
In an MCOD landscape you can upgrade a single component independently from the other
components running in the same database, assuming that the upgraded component runs on
the same database version. However, if you need to restore a backup, be aware that all other
components are also affected.
Note
Special MCOD considerations and differences from the standard procedure are listed where relevant
in the installation documentation.
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.
n In the event of database failure, all SAP systems running on the single database are affected.
n Automated support in an MCOD landscape for the following administrative tasks depends on
your operating system and database:
112/140 PUBLIC 08/27/2007

6.2 Integration of LDAP Directory Services (Optional)
l Copying a single component from an MCOD landscape to another database at database level.
l De-installing a single component from an MCOD landscape requires some additional steps.
You can use a remote connection to SAP support to request help with these tasks. For more
information see https://service.sap.com/remoteconnection.
n 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.
n You cannot install a Unicode SAP system with a non-Unicode SAP system in one database.
n For the first SAP system, the database system ID can be different from the SAP system ID.
n For the second SAP system, make sure that you use the same DBSID as for the first SAP system.
n 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.
This section explains the benefits of using the SAP system with the Lightweight Directory Access
Protocol (LDAP) directory and gives an overview of the configuration steps required to use an SAP
system with the directory.
LDAP defines a standard protocol for accessing directory services, which is supported by various
directory products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory services
enables important information in a corporate network to be stored centrally on a server. The
advantage of storing information centrally for the entire network is that you only have to maintain
data once, which avoids redundancy and inconsistency.
If an LDAP directory is available in your corporate network, you can configure the SAP system to use
this feature. For example, a correctly configured SAP system can read information from the directory
and also store information there.
Note
The SAP system can interact with the Active Directory using the LDAP protocol, which defines:
n The communication protocol between the SAP system and the directory
n 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.
08/27/2007 PUBLIC 113/140

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 <your product> SAP NetWeaver Library SAP NetWeaver by Key Capability
Security Identity Management 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:
n SAP Logon
n The SAP Microsoft Management Console (SAP MMC)
n 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 on SAP Service Marketplace at:
http://service.sap.com/msplatforms Microsoft Windows Server
For more information about the SAP MC and about how to configure it to access LDAP Directories,
see the documentation SAP Management Console on SAP Service Marketplace at:
http://help.sap.com SAP Library 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=
114/140 PUBLIC 08/27/2007

LDAPoptions=
Distinguish the following cases:
n If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For more
information, see the SAP system profile parameter ldap/options.
n You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either of
the following is true:
l The client is not located in the same domain forest as the Active Directory
l 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.
n 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. If the SAP system has been prepared correctly, the SAP MMC presents and analyzes
system information that it gathers from various sources, including the Active Directory.
Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can
read system information straight from the directory that automatically registers changes to the
system landscape. As a result, up-to-date information about all SAP application servers, their status,
and parameter settings is always available in the SAP MMC.
If you need to administer distributed systems, we especially recommend that you use the SAP MMC
together with Active Directory services. For example, you can simplify administration by using the
SAP MMC in a distributed environment that implements the mySAP Business Suite components.
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.
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 the Generic LDAP Directory.
Integrating the 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 Active Directory

To enable an SAP system to make use of the features offered by the Active Directory, you must
configure the Active Directory so that it can store SAP data.
08/27/2007 PUBLIC 115/140

6.3 Starting and Stopping the SAP System
This involves extending the schema for the SAP data types, creating a root container for the storage of
SAP-specific information, and defining accounts that allow directory access. You perform all these
tasks using SAPinst with the option Active Directory Configuration.
For more information, see section Setting Up the Active Directory Services (Optional) in the Windows
installation guide for your SAP system solution and database.
Configuration Tasks for Generic LDAP Directories

To configure generic LDAP directories, refer to the documentation of your directory vendor.

You can start and stop the SAP system by using one of the following:
n The SAP Management Console (MC) [page 116]
n The startsap and stopsap scripts [page 120]
6.3.1 Starting and Stopping the SAP System Using the SAP
Management Console
You can start and stop all instances of your SAP system using the SAP Management Console (MC).
Note
If your newly installed UNIX system is part of a heterogeneous SAP system landscape that comprises
systems or instances on Windows platforms, you can also start and stop it from a Windows system or
instance using the Microsoft Management Console (MMC).
For more information about handling the MMC, see:
Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS Microsoft Management
Console: Windows
Prerequisites
n Make sure that the host on which you want to start SAP MC meets the following requirements:
l Java Runtime Environment (JRE) 5.0 is installed.
l The browser supports Java.
l The browser’s Java plug-in is installed and activated.
n You have logged on to the host as user <sapsid>adm.
Starting the Web-Based SAP Management Console

1. Start a Web browser and enter the following URL:
116/140 PUBLIC 08/27/2007

http://<hostname>:5<instance_number>13
Example
If the instance number is 53and the host name is saphost06, you enter the following URL:
http://saphost06:55313
This starts the SAP MC Java applet.
Note
If your browser displays a security warning message, choose the option that indicates that you
trust the applet.
2. 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. If you want to change the configuration to display systems and instances
on other hosts, see Registering Systems and Instances below.
Starting and Stopping Systems and Instances
Starting an SAP System or Instance
1. In the navigation pane, open the tree structure and navigate to the system node that you want to
start.
2. Select the system or instance and then, from the context menu, choose Start.
3. In the Start SAP System(s) dialog box, choose the required options.
4. Choose OK. The SAP MC starts the specified system or system instances.
Note
The system may prompt you for the SAP system administrator credentials. To complete the
operation, you must have administration permissions. Log in as user <sapsid>adm.
Starting Instances Separately

If you need to start the instances of an SAP system separately, for example when you want to start a
distributed or a high-availability system, proceed in the following sequence:
1. Start the database instance.
2. Start the central services instance SCS<Instance_Number>.
08/27/2007 PUBLIC 117/140

If your system is a high-availability system, you first start the ABAP central services
instance ASCS<Instance_Number> and then you start the Java central services instance
SCS<Instance_Number>.
End of: HA (UNIX)
3. Start the primary application server instance DVEBMGS<Instance_Number>.

4. Start additional application server instance(s) D<Instance_Number> if there are any.
Stopping an SAP System or Instance
1. Select the system or instance you want to stop and choose Stop from the context menu.
2. In the Stop SAP System(s) dialog box, choose the required options.
3. Choose OK. The SAP MC stops the specified system or system instances.
Note
The system may prompt you for the SAP system administrator credentials. To complete the
operation, you must have administration permissions. Log in as user <sapsid>adm.
Similarly, you can start, stop or restart all SAP systems and individual instances registered in the
SAP MC.
Stopping Instances Separately

If you need to stop the instances of an SAP system separately, for example when you want to start a
distributed or a high-availability system, proceed in the following sequence:
1. Stop additional application server instance(s) D<Instance_Number> if there are any.
2. Stop the primary application server instance DVEBMGS<Instance_Number>.
3. Stop the central services instance SCS<Instance_Number>.
If your system is a high-availability system, you first stop the Java central services
instance SCS<Instance_Number> and then you stop the ABAP central services instance
ASCS<Instance_Number>.
End of: HA (UNIX)
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.
118/140 PUBLIC 08/27/2007

Prerequisites
The SAP MC is started.
Registering SAP Systems
1. In the SAP MC, choose File New .

2. In the New System dialog box, enter the required data.
Note
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.
3. Choose Finish.
Registering Individual Instances
1. In the SAP MC, choose File New .

2. In the New System dialog box, enter the required data and deselect Always show all SAP Instances.
3. 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
n You can choose the instances that the SAP MC displays automatically on startup:
1. In the Settings dialog box, select History.
2. In the right-hand side pane, choose the instance you want the SAP MC to display on startup.
3. Choose the << button.
4. Choose Apply and then choose OK.
Similarly, you can remove instances from the startup configuration.
n 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.
n 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.
08/27/2007 PUBLIC 119/140

More Information
For more information about the SAP Management Console, see:
Platform by Key Capability Java Technology -> Administration Manual J2EE Engine J2EE Engine Administration
Tools SAP Management Console
6.3.2 Starting and Stopping the SAP System Using startsap

stopsap Scripts
You can start and stop the SAP system by running the startsap and stopsap scripts in the exe
directory.
Prerequisites
n You have checked the default profile /<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameter
login/system client and set the value to the correct productive system client. For example, the
entry must be login/system_client = 001 if your productive client is 001.
n You have checked the settings for Java Virtual Machine parameters as described in SAP Note
723909.
n You have logged on to the SAP system hosts as user <sapsid>adm.
n 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.
n 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 DVEBMGS00
120/140 PUBLIC 08/27/2007

Note
The instance name (instance ID) of the central instance is DVEBMGS<Instance_Number>, the
instance name of the central services instance is SCS<Instance_Number>, and the instance name
of a dialog instance is D<Instance_Number>.
The instance name of the ABAP central services instance is ASCS<Instance_Number>.

End of: HA (UNIX)
Procedure
Starting the SAP system
n 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.
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.
n In a distributed system, proceed as follows:

1. On the database host, enter:
startdb
2. On the central services and on the central instance host, enter:
startsap
3. For dialog instance(s) enter the following on the relevant host:
startsap R3 <instance ID of dialog instance>
08/27/2007 PUBLIC 121/140

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 the SAP System
Note
When you use stopsap in a Multiple Components in One Database (MCOD) system with two central
instances, only one central instance and the database are 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 111].
n 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 J2EE to stop
the SAP instance comprising both ABAP and J2EE.
n In a distributed system, proceed as follows:

1. On the dialog instance host, enter the following command:
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
122/140 PUBLIC 08/27/2007

6.4 Creating a User for LDAP Directory Access (Optional)
Caution
Make sure that no SAP instance is running before you enter stopdb on a standalone database server.
No automatic check is made.
6.4 Creating a User for LDAP Directory Access (Optional)
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 section Preparing the Active Directory (Optional) 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. Log on as user <sapsid>adm.
2. Enter:
ldappasswd pf=<path_and_name_of_instance_profile>
3. Enter the required data.
Example
The following is an example of an entry to create an LDAP Directory User:
CN=sapldap,CN=Users,DC=nt5,DC=sap-ag,DC=de
6.5 Configuring User Management to Use an LDAP Directory

(Optional)
If your user data source is an LDAP directory, you need to configure the connection to the LDAP
directory after installation.
For more information, see:
https://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Security
Identity Management User Management Engine UME Configuration UME Data Sources LDAP Directory as
Data Source Configuring UME to Use an LDAP Server as Data Source
08/27/2007 PUBLIC 123/140

6.6 Initial Configuration of Adobe Document Services
6.6 Initial Configuration of Adobe Document Services
SAPinst automatically performs initial configuration steps specific to Adobe Document Services
(ADS) during the installation.
However, you have to perform some of these steps manually if
n you have installed AS Java on a separate host and want to use ADS for a standalone ABAP system or
n you want to change existing parameters or you want to set additional parameters.
Features
Depending on your installation scenario, you might have to perform one ore more of the following
steps:
n Create a user with the required authorizations for basic authentication.
n Create or change the web service destination.
n Activate the ICF service.
You can find a detailed description of the manual procedure for these steps in the SAP Library at
http://help.sap.com/nw70 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 .
More Information
The document Adobe Document Services Configuration Guide is also available in PDF form on SAP Service
Marketplace at
http://service.sap.com/adobe SAP Interactive Forms by Adobe Media Library Documentation Adobe
Document Services - Configuration Guide NW 2004s
6.7 Initial Configuration for the System Landscape Directory

(SLD)
If you chose the option Register in existing central SLD, SAPinst automatically configures the connection
of the system being installed to an existing central System Landscape Directory (SLD).
If you chose the option Configure a local SLD, SAPinst automatically sets up and configures a local
System Landscape Directory (SLD) during the installation. SAPinst
n configures SLD security roles,
n configures server and persistence parameters,
n performs the initial data import,
n configures the SLD bridge.
124/140 PUBLIC 08/27/2007

6.8 Heterogeneous SAP System Installation
For more information on the steps performed by SAPinst, see the documentation Post
Installation Guide ‒ System Landscape Directory of SAP NetWeaver 7.0 on SAP Service Marketplace at
http://service.sap.com/installNW70 Installation Configuration .
More Information
For more information on working with and configuring the SLD, see the SAP Library at
http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Software Life Cycle Management System Landscape
Directory . (This documentation is also available in PDF form on SAP Service Marketplace at
http://service.sap.com/sld System Landscape Directory Media Library Documentation System
Landscape Directory ).
For more information on security and on the role concept in SLD, see the SAP Library at
http://help.sap.com/nw70 SAP NetWeaver Library Administrator’s Guide SAP NetWeaver Security
Guide Security Aspects for System Management Security Guide for the SAP System Landscape Directory .
6.8 Heterogeneous SAP System Installation
This documentation describes how to install SAP instances in a heterogeneous UNIX environment,
which is where you:
n Run instances on different UNIX platforms
n Mix 32-bit instances and 64-bit instances in one landscape
Note
See SAP Note 1067221 for information on
n supported combinations of operating systems and database systems
n installing an application server on Windows in a heterogeneous (UNIX) SAP system environment
(ABAP, Java, or ABAP+Java) with SAPinst.
n Java EE engine installation on heterogeneous architectures
n heterogeneous Unix - Unix Systems
Procedure
Proceed as follows to store the SAP executables locally:
1. Install the central instance and the database as described in the installation documentation.
2. Log on as user root on the dialog instance host.
3. Create <sapmnt>/<SAPSID>/exe as a local directory on the dialog instance.
4. On the central instance host, export the directories <sapmnt>/<SAPSID>/global and
<sapmnt>/<SAPSID>/profile via NFS and mount them on each dialog instance host as described
in Preparing and Mounting the Installation Media [page 61].
08/27/2007 PUBLIC 125/140

6.9 Deleting an SAP System
5. Mount the CD or DVD drive using NFS and insert the CD / DVD with the SAP executables on the
dialog instance host.
6. Install the dialog instance.

The following sections describe how to delete an SAP system assuming that you have installed your
SAP system with standard SAP tools according to the installation documentation. You can choose
one of the following options:
n You delete the SAP system using SAPinst.
n You delete the SAP system manually.
Caution
n If you are running multiple components on one database (MCOD), do not delete the database.
n You cannot delete an SAP system remotely.
n If you delete network-wide users, groups, or service entries in an environment with Network
Information System (NIS), other SAP installations might also be affected. Before you delete users,
groups, or service entries, make sure that they are no longer required.
n When you delete an SAP system using SAPinst, system directories mounted from an NFS server
are not deleted.
You must either delete them manually [page 128] or run SAPinst on the NFS server.
Deleting an SAP System Using SAPinst

You delete the SAP system using SAPinst [page 127]as follows:.
n If you want to delete a central system, where all SAP instances reside on the same host, you can
do this in one SAPinst run [page 127].
n If you want to delete a distributed system, where the SAP instances reside on different hosts,
you have to run SAPinst [page 127] to delete the required instances locally on each host in the
following sequence:
1. You delete the dialog instance(s), if there are any.
2. You delete the database instance.
3. You delete the central instance.
4. You delete the central services instance.
Deleting an SAP System Manually

You delete the SAP system manually [page 128] as follows:
1. You delete the SAP instances [page 128] in the following sequence:
a) Dialog instances, if there are any
126/140 PUBLIC 08/27/2007

b) Central instance
Note
The Java part of an SAP system is deleted automatically when you delete the central instance
of the ABAP system.
c) Central services instance, if there is one
2. You delete the remaining installation files and directories on the host(s) where you deleted your SAP instance(s) [page 129].
3. You delete the MaxDB database instance [page 133].
Deleting the Java Part of an SAP System
1. You delete the Java parts of all dialog instances [page 130], if there are any.
2. You delete the Java part of an SAP system [page 130].
3. You delete the central services instance [page 128].
4. You delete the Java database schema of the MaxDB installation [page 132].
6.9.1 Running SAPinst to Delete an SAP System
This procedure tells you how to run the Uninstall service of SAPinst.
Prerequisites
n You are logged on as user root.
n 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 <sid>adm of the other SAP system and
start saposcol from there using the command saposcol -l.
Procedure
1. Start SAPinst and on the Welcome screen, choose:
<SAP System> Additional Software Life-Cycle Tasks Uninstall Uninstall System / Standalone Engine /
Optional Standalone Unit
2. 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.
SAPinst first asks you which SAP instances you want to delete.
08/27/2007 PUBLIC 127/140

Make sure that you delete the SAP instances in the correct order, as described in Deleting an SAP
System [page 126].
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.
3. Choose whether you want to drop the entire database or only one or more database schemas. If
you drop the entire database, SAPinst also asks whether you want to remove the database software.
4. 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.
6.9.2 Deleting an SAP System Manually
6.9.2.1 Deleting an SAP Instance
You use this procedure if you want to delete a single SAP instance or all instances of a SAP system.
Note
Make sure that you delete the instances in the following order:
1. Dialog instance if there are any
2. Central instance
3. Central services instance if there is one
Procedure
1. Stop the SAP instance that you want to delete as follows:
a) Log on as user <sapsid>adm.
b) Execute this command:
stopsap r3 <InstanceName>
2. Stop the sapstart service with the following command:
sapcontrol -nr <InstanceNumber> -prot NI_HTTP -function StopService
3. Stop the saposcol process with the following command:
saposcol -k
4. Remove the instance profiles as follows:
rm /usr/sap/<SAPSID>/SYS/profile/<SAPSID>_<InstanceName>_<host_name>
rm /usr/sap/<SAPSID>/SYS/profile/START_<InstanceName>_<host_name>
128/140 PUBLIC 08/27/2007

Example
For example, enter the following commands:
rm /usr/sap/C11/SYS/profile/START_D00_h0001
rm /usr/sap/C11/SYS/profile/C11_D00_h0001
5. Log on as user root and delete the local instance directory:

rm -rf /usr/sap/<SAPSID>/<InstanceName>
6. Change to the directory /usr/sap, edit the file sapservices and delete the line that refers to
the instance to be deleted.
6.9.2.2 Deleting Installation Files, Directories, and Users on

a Host
After you have deleted all SAP instances on a host, you still have to delete the remaining installation
files, directories, and users on this particular host. You have to repeat this procedure for any host
where you previously deleted an SAP instance.
Caution
If you are not deleting the entire SAP system (on all hosts), make sure that you do not delete files or
directories that are used by other SAP instances by means of NFS mounts.
Prerequisites
You must have deleted your SAP instance(s) as described in Deleting an SAP Instance [page 128].
Procedure
1. If the following directories are mounted with NFS, unmount them:
/<sapmnt>/<SAPSID>/exe
/<sapmnt>/<SAPSID>/global
/<sapmnt>/<SAPSID>/profile
2. Tto delete directories, execute the following commands:
rm -rf /usr/sap/<SAPSID>
rm -rf /<sapmnt>/<SAPSID>
3. Delete the local user <sapsid>adm, its home directory, and all subdirectories of the home directory.
Caution
Do not delete user <sapsid>adm if this is a Network Information System (NIS) user and you do
not want to delete the SAP system on all hosts.
08/27/2007 PUBLIC 129/140

Recommendation
To delete users, use the administration tools of your operating system if possible.
a) Delete user <sapsid>adm as described in your operating system documentation.

b) If the home directory of the user was not deleted automatically in the previous step, execute
the following command to delete the directory:
rm -rf <sapsid_adm_home>
Example
rm -rf /home/c11adm
4. Check whether you need to delete entries from the file /etc/services:
a) Search for entries starting with sap
b) Check whether these entries are still required by other instances with the same or a different
<SAPSID> on any server.
c) If not, start by generating a backup copy of the services file by entering the following command:
cp /etc/services /etc/services.sap
d) Delete superfluous entries from /etc/services.
If you use NIS for the services file, see your operating system documentation for more
information on how to delete entries from network-wide service entries.
5. If there are no other SAP instances running on this host, delete the file /usr/sap/sapservices.
6.9.2.3 Deleting the Java Part of an SAP System
This section describes how to delete the Java part of an SAP system.
Note
If you delete a Java part, the ABAP part of the SAP system is not deleted.
Caution
This description assumes that you installed the SAP system using SAP standard tools according
to the installation documentation.
Process
Caution
If you delete network-wide users, groups, or service entries in an environment with Network
Information System (NIS), other SAP installations might also be affected. Make sure that the users,
groups, and service entries to be deleted are no longer required.
130/140 PUBLIC 08/27/2007

1. Stop the central services instance and all dialog instances of your SAP system:
a) Log on to the corresponding instance host as user <sapsid>adm.
b) Execute the following commands:
n To stop the central services instance:
stopsap r3 <SCSinstanceName>
n To stop a dialog instance:
stopsap r3 <DialogInstanceName>
2. Stop the J2EE Engine of the central instance:
a) Log on to your SAP system.
b) Call transaction SMICM.
c) Choose Administration J2EE Instance (local) Send Hard Shutdown .
Note
You do not need to stop the central instance.
3. If lines beginning with the following parameters appear, delete these lines from the default profile,
/usr/sap/<SAPSID>/SYS/profile/DEFAULT.PFL:
j2ee/dbname =
j2ee/dbtype =
j2ee/dbhost =
j2ee/dbadminurl =
j2ee/scs/host =
j2ee/scs/system =
j2ee/ms/port =
4. If lines beginning with the following parameters appear, delete these lines
from the central instance prole and from all dialog instance proles,
/usr/sap/<SAPSID>/SYS/profile/<SAPSID>_<INSTANCE_NAME>_<host_name>:
exe/j2ee =
exe/jlaunch =
rdisp/j2ee_start_control =
rdisp/j2ee_start =
rdisp/j2ee_timeout =
rdisp/j2ee_libpath =
rdisp/frfc_fallback =
jstartup/trimming_properties =
jstartup/instance_properties =
jstartup/protocol =
jstartup/vm/home =
jstartup/max_caches =
jstartup/release =
08/27/2007 PUBLIC 131/140

j2ee/dbdriver =
5. Delete the central services instance [page 128].
6. Delete the MaxDB Java database schema [page 132].
7. Delete the following directories (<xx> is the central instance number):
n /usr/sap/<SAPSID>/DVEBMGS<xx>/SDM
n /usr/sap/<SAPSID>/DVEBMGS<xx>/j2ee
6.9.2.4 Deleting the Java Database Schema
You use this procedure to delete the Java database schema for a MaxDB database.
Caution
If you have Multiple Components in One Database (MCOD), only delete the database if you want to
delete all components. Otherwise, delete components as required.
Prerequisites
Before deleting the Java database schema, stop all SAP instances [page 120] belonging to this Java database
schema.
Caution
Make sure that you have a recent complete database backup.
Recommendation
We recommend that you delete the SAP instances before deleting the Java database schema.
For more information, see Deleting an SAP Instance [page 128].
Procedure
1. Log on as user <sid>adm.
2. Start a dbmcli session and connect to the database:
dbmcli -d <DBSID> -u <control_user_name,control_password> -uSQL
<admin_user,adm_password>
3. Delete the database schema:
dbmcli> sql_execute drop user SAP<SAPSID>DB
4. End the dbmcli session:
dbmcli> exit
132/140 PUBLIC 08/27/2007

6.10 Troubleshooting
6.9.2.5 Deleting the Database Installation
You use this procedure to remove a MaxDB database instance and uninstall the database software.
Prerequisites
Before deleting the database installation stop all SAP instances [page 120] belonging to this database.
Recommendation
We recommend that you delete the SAP instances before deleting the database installation. For
more information, see Deleting an SAP Instance [page 128].
Procedure
1. Log on as user sqd<dbsid>.
2. Stop the database:
dbmcli -d <SAPSID> -u control,control db_stop
3. Remove the database instance:
dbmcli -d <SAPSID> -u control,control db_drop
4. Uninstall the MaxDB software as follows:
a) Start the MaxDB uninstaller as user root with the following command:
/sapdb/programs/bin/sdbuninst –list
The program lists the software packages available to remove.
b) Remove the MaxDB software as follows:
n To remove all the MaxDB software, enter the following command:
/sapdb/programs/bin/sdbuninst –all
n To remove individual packages , enter the following command:
/sapdb/programs/bin/sdbuninst –package “<package_name>” -package_dir
“<package_location>”
5. Delete users sqd<dbsid> and <sapsid>adm from group sapsys if they have not already been
deleted automatically. If group sapsys is now empty, delete the complete group as described in
your operating system documentation.
The following section(s) describe the steps that you need to perform manually if SAPinst fails:
n Troubleshooting with SAPinst [page 134]
08/27/2007 PUBLIC 133/140

6.10.1 Troubleshooting with SAPinst
This section tells you how to proceed when errors occur during the installation with SAPinst.
If an error occurs, SAPinst:
n Stops the installation
n Displays a dialog informing you about the error
Procedure
1. To view the log file, choose View Logs.
2. If an error occurs during the dialog or processing phase, do either of the following:
n Try to solve the problem
n Abort the installation with Exit
For more information, see Interrupted Installation with SAPinst [page 79].
n Continue the installation by choosing Retry.
3. Check the log and trace files of the GUI server and SAPinst GUI in the directory
<user_home>/.sdtgui/ for errors.
4. If SAPinst GUI does not start, check the file sdtstart.err in the current <user_home> directory.
5. If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as
described in Starting SAPinst GUI Separately.
6. 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.
134/140 PUBLIC 08/27/2007

Typographic Conventions
Example Description
< > Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
Example Textual cross-references to an internet address, for example, http://www.sap.com
/example Quicklinks added to the internet address of a homepage to enable quick access to
specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example n Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
n Cross-references to other documentation or published works
Example n Output on the screen following a user action, for example, messages
n Source code or syntax quoted directly from a program
n File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE 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
EXAMPLE Keys on the keyboard
08/27/2007 PUBLIC 135/140

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 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,
xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or
registered trademarks of IBM Corporation.
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.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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.
This document was created using stylesheet 2006-12-31 (V5.1beta [= 6.0 for E3]) and XSLT processor SAXON 6.5.2 from
Michael Kay (http://saxon.sf.net/), XSLT version 1.
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 expressively 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.
136/140 PUBLIC 08/27/2007

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
69190 Walldorf, Germany
(hereinafter: SAP)
and
you
(hereinafter: Customer)
a) Subject Matter of the Agreement
A) SAP grants Customer a non-exclusive, non-transferrable, royalty-free license to use the STLport.org C++
library (STLport) and its documentation without fee.
B) 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.
C) The Customer may distribute binaries compiled with STLport (whether original or modified) without any
royalties or restrictions.
D) Customer shall maintain the following copyright and permissions notices on STLport sources and its
documentation unchanged: Copyright 2001 SAP AG
E) The Customer may distribute original or modified STLport sources, provided that:
n The conditions indicated in the above permissions notice are met;
n The following copyright notices are retained when present, and conditions provided in accompanying
permission notices are met:
Coypright 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
copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no
representations about the suitability of this software for any purpose. It is provided “as is” without express or
implied warranty.
copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC
08/27/2007 PUBLIC 137/140

makes no representations about the suitability of this software for any purpose. It is provided “as is” without
express or implied warranty.
Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is
provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use
or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all
copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are
retained, and a notice that the code was modified is included with the above copyright notice.
copyright notice and this permission notice appear in supporting documentation. SAP makes no representations
about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set
forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only
towards its customers and only referring to its modifications.
b) 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.
c) 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.
d) Limited Liability
A) 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.
B) 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.
C) 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.
D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed
EUR 5,000.
E) 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.
F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees
or agents of SAP.
3. 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
138/140 PUBLIC 08/27/2007

SAP AG
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2007 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.

SAP Solution Manager 4.0 SR3 On Linux MaxDB

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SAP Solution Manager 4.0 SR3 On Linux MaxDB

Hochgeladen von

Copyright:

Verfügbare Formate

PUBLIC

SAP Solution Manager

Document version: 1.0 ‒ 08/27/2007

1.0 8/27/2007 Initial Version

2/140 PUBLIC 08/27/2007

08/27/2007 PUBLIC 3/140

4/140 PUBLIC 08/27/2007

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 111

08/27/2007 PUBLIC 5/140

08/27/2007 PUBLIC 7/140

1.1 New Features

SAP System Installation

8/140 PUBLIC 08/27/2007

1.2 SAP Notes for the Installation

08/27/2007 PUBLIC 9/140

SAP Notes for the Installation Title Description

1.3 Information Available on SAP Service Marketplace

More information is available as follows on SAP Service Marketplace.

Description Internet Address Title

10/140 PUBLIC 08/27/2007

Description Internet Address Title

General Quick Links

Description Internet Address

SAP NetWeaver Library in SAP http://help.sap.com/nw70

Released platforms and operating http://service.sap.com/platforms

High availability http://service.sap.com/ha

Information on SAP Support http://service.sap.com/sp-stacks

SAP Solution Manager http://service.sap.com/solutionmanager

SAP Solution Support http://service.sap.com/ssep

08/27/2007 PUBLIC 11/140

1.4 Naming Conventions

In this documentation, the following naming conventions apply:

n SAP system refers to SAP Solution Manager 4.0 SR3 system.

The following example shows how the variables are used:

12/140 PUBLIC 08/27/2007

The following planning activity is optional:

2.1 Basic System Variants for SAP Solution Manager

08/27/2007 PUBLIC 13/140

Figure 1: Minimum System Distribution (Central System)

For a minimum system distribution, all instances reside on one host.

14/140 PUBLIC 08/27/2007

Figure 2: Maximum Distribution for a Distributed System

For a maximum system distribution, each instance resides on a separate host.

Figure 3: Maximum Distribution for a High-Availability System

End of: HA (UNIX)

08/27/2007 PUBLIC 15/140

Only valid for: HA (UNIX)

For a maximum system distribution, each instance resides on a separate host.

2.2 How to Distribute Instances to Hosts

Figure 4: Distribution of Instances in an ABAP+Java System

You perform the following steps:

16/140 PUBLIC 08/27/2007

Java Add-In for an Existing ABAP System

08/27/2007 PUBLIC 17/140

2.3 MaxDB System Configuration

18/140 PUBLIC 08/27/2007

n We recommend you to run the database with raw devices.

n Do not replace file systems by softlinks.

Security Concept for Database Software Owner

n Store database data files and logs on different disks

Different MaxDB Systems

08/27/2007 PUBLIC 19/140

2.4 Basic SAP System Parameters