SAP Solution Manager 4.0 SR2 On Linux: Oracle: Installation Guide

PUBLIC
Installation Guide
SAP Solution Manager

4.0 SR2 on Linux :
Oracle
Target Audience
n Technology consultants
n System administrators
Document version: 1.0 02/02/2007
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
2/140
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.1) 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 SAPs Support Services and may not be
modified or altered in any way.
Legal Software Terms
Terms for Included Open Source Software
This SAP software contains also the third party open

source software products listed below. Please note that for
these third party products the following special terms and
conditions shall apply.
1. This software was developed using ANTLR.
2. gSOAP
PUBLIC
02/02/2007
Part of the software embedded in this product is gSOAP

software. Portions created by gSOAP are Copyright
(C) 2001-2004 Robert A. van Engelen, Genivia inc. All
Rights Reserved.
THE SOFTWARE IN THIS PRODUCT WAS IN PART
PROVIDED BY GENIVIA INC AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL THE AUTHOR BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
3. SAP License Agreement for STLport
SAP License Agreement for STLPort between
SAP Aktiengesellschaft
Systems, Applications, Products in Data Processing
Neurottstrasse 16
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
02/02/2007
PUBLIC
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.
sell this software and its documentation for any
purpose is hereby granted without fee, provided
that the above copyright notice appear in all
copies and that both that copyright notice and
this permission notice appear in supporting
documentation. Silicon Graphics makes no
representations about the suitability of this
software for any purpose. It is provided as is
without express or implied warranty.
sell this software and its documentation for
any purposes is hereby granted without fee,
provided that the above copyright notice appear
in all copies and that both that copyright notice
and this permission notice appear in supporting
documentation. Moscow Center for SPARC
makes no representations about the suitability
of this software for any purpose. It is provided
as is without express or implied warranty.
Boris Fomitchev makes no representations
about the suitability of this software for any
purpose. This material is provided "as is", with
absolutely no warranty expressed or implied.
Any use is at your own risk. Permission to
use or copy this software for any purpose is
3/140
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.
Permission to use, copy, modify, distribute
and sell this software and its documentation
for any purposes is hereby granted without
fee, provided that the above copyright notice
appear in all copies and that both that copyright
notice and this permission notice appear in
supporting documentation. SAP makes no
representations about the suitability of this
software for any purpose. It is provided with a
limited warranty and liability as set forth in the
License Agreement distributed with this copy.
SAP offers this liability and warranty obligations
only towards its customers and only referring
to its modifications.
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.
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.
F) The exclusion or the limitation of claims in

accordance with the present Art. 4 includes
claims against employees or agents of SAP.
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.
4. 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.
d) Limited Liability
Documentation in the SAP Service

Marketplace
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
4/140
You can find this document at the following address:

https://service.sap.com/instguides
PUBLIC
02/02/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
02/02/2007
PUBLIC
5/140
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
2/2/2007
Initial Version
6/140
PUBLIC
02/02/2007
Table of Contents
Chapter 1
1.1
1.2
1.3
1.4
Introduction . . . . . . . . . . . . .
New Features . . . . . . . . . . . . . .
SAP Notes for the Installation . . . . . . . .
Information Available on SAP Service Marketplace
Naming Conventions . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
11
11
13
14
15
Chapter 2
2.1
2.2
2.3
2.4
2.5
2.6
Planning . . . . . . . . . . . . . . . . . . . . .
Basic System Variants for SAP Solution Manager . . . . . . .
How to Distribute Instances to Hosts . . . . . . . . . . .
Basic SAP System Parameters . . . . . . . . . . . . . .
Multi-Language and Unicode Support . . . . . . . . . . .
Running Adobe Document Services on Non-Supported Platforms
High Availability: Planning the Switchover Cluster . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
17
17
20
22
29
30
30
Chapter 3
3.1
3.1.1
3.1.2
3.1.3
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.4.1
3.2.4.2
3.2.4.3
3.2.5
3.2.6
3.2.7
3.3
3.3.1
3.3.2
3.3.3
3.3.4
Preparation . . . . . . . . . . . . . . . . . . . .
High Availability: Switchover Preparations . . . . . . . . .
Preparing for Switchover . . . . . . . . . . . . . . . .
Setting Up File Systems . . . . . . . . . . . . . . . .
Configuring Network File System . . . . . . . . . . . .
Hardware and Software Requirements . . . . . . . . . . .
Running the Prerequisite Checker in Standalone Mode (Optional)
Requirements for Linux . . . . . . . . . . . . . . . .
Requirements for a Central System . . . . . . . . . . . .
Requirements for a Distributed or a High Availability System . .
Requirements for the Central Services Instance . . . . . . .
Requirements for the Central Instance . . . . . . . . . .
Requirements for the Database Instance . . . . . . . . . .
Requirements for a Dialog Instance . . . . . . . . . . . .
Checking and Modifying the Linux Kernel . . . . . . . . .
Setting up Swap Space for Linux . . . . . . . . . . . . .
Creating Operating System Users . . . . . . . . . . . .
Network Information Service . . . . . . . . . . . . . .
Creating Operating System Users and Groups . . . . . . . .
Creating Operating System Users and Groups Manually . . . .
Creating Linux Groups and Users (Optional) . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
35
36
36
38
39
41
42
43
45
46
46
47
47
49
50
50
51
51
51
53
54
02/02/2007
PUBLIC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7/140
3.4
3.4.1
3.4.2
3.4.3
3.5
3.6
3.7
3.8
3.9
3.9.1
3.9.2
3.9.3
Setting Up File Systems and Raw Devices . . . . . . . . . . . . .

Setting Up File Systems . . . . . . . . . . . . . . . . . . .
Oracle File Systems . . . . . . . . . . . . . . . . . . . . .
Setting Up Standard File Systems and Raw Devices for Linux . . . . .
Exporting and Mounting the Global Transport Directory . . . . . . .
Exporting and Mounting Directories via NFS for Linux (Optional) . . .
Installing the SAP Front-End Software . . . . . . . . . . . . . .
Installing the Java Development Kit . . . . . . . . . . . . . . .
Preparing and Mounting the Installation Media . . . . . . . . . .
Preparing the Installation DVDs . . . . . . . . . . . . . . . .
Downloading Installation DVDs from SAP Service Marketplace (Optional)
Mounting a CD / DVD for Linux . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
54
54
60
61
62
63
65
65
67
67
69
70
Chapter 4
4.1
4.2
4.2.1
4.2.2
4.2.3
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.7
4.4
4.4.1
4.4.2
4.4.3
4.4.4
Installation . . . . . . . . . . . . . . . . . . . .
Performing a High-Availability Installation . . . . . . . . .
Prerequisites before Starting SAPinst . . . . . . . . . . .
Prerequisites before Starting SAPinst: All Instances . . . . . .
Prerequisites before Starting SAPinst: Distributed Instances . . .
Prerequisites Before Starting SAPinst: High Availability . . . . .
Installing an SAP System Using SAPinst . . . . . . . . . .
Running SAPinst on UNIX . . . . . . . . . . . . . . .
Installing the Java Add-In for an Existing ABAP System (Optional)
Using SAPinst GUI . . . . . . . . . . . . . . . . . .
Interrupted Installation with SAPinst . . . . . . . . . . .
Performing a Remote Installation with SAPinst (Optional) . . .
Starting SAPinst GUI Separately (Optional) . . . . . . . . .
Entries in the Services File Created by SAPinst . . . . . . . .
Oracle Database Software Installation . . . . . . . . . . .
Updating SAP-Specific Files in the Oracle Staging Area . . . . .
Running the Oracle Universal Installer . . . . . . . . . .
Installing the Current Patch Set . . . . . . . . . . . . .
Installing Required Interim Patches . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
71
71
73
73
75
76
76
76
82
84
84
86
87
89
89
90
90
92
92
Chapter 5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
Post-Installation . . . . . . . . . . . . . . .
Starting and Stopping the SAP System . . . . . . . .
Logging On to the SAP System . . . . . . . . . .
Installing the SAP License . . . . . . . . . . . .
Installing the SAP Online Documentation . . . . . .
Configuring Remote Connection to SAP Support . . .
Performing Initial ABAP Configuration . . . . . . .
Completing and Checking the Oracle Database Installation
Applying the Latest Kernel and Support Packages . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
95
96
99
101
101
102
102
104
105
8/140
PUBLIC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
02/02/2007
5.9
5.10
5.10.1
5.10.2
5.11
5.11.1
5.11.2
5.12
5.13
5.14
Performing a Full Installation Backup . . . . . . . . . . .

Post-Installation Steps for Adobe Document Services . . . . .
Assigning Roles to Users ADSUSER and ADS_AGENT . . . . .
Installation Check and Quick Tests for Adobe Document Services
High Availability: Post-Installation Steps . . . . . . . . . .
Setting Up Licenses . . . . . . . . . . . . . . . . . .
Taking Precautions for Transport . . . . . . . . . . . .
Ensuring User Security . . . . . . . . . . . . . . . .
Checking the SAP Java Documentation . . . . . . . . . .
Configuring SAP Solution Manager . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
107
108
108
109
110
110
111
112
115
116
Chapter 6
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.8.1
6.8.1.1
6.8.1.2
6.8.2
6.8.2.1
6.8.2.2
6.8.2.3
6.8.2.4
6.8.2.5
6.9
6.9.1
Additional Information . . . . . . . . . . . . . . . .
Installation of Multiple Components in One Database (Optional) . .
Integration of LDAP Directory Services (Optional) . . . . . . .
Preparing User Management for an External ABAP System . . . .
Creating a User for LDAP Directory Access (Optional) . . . . . .
Configuring User Management to Use an LDAP Directory (Optional)
System Landscape Directory . . . . . . . . . . . . . . .
Heterogeneous SAP System Installation . . . . . . . . . . .
Deleting an SAP System . . . . . . . . . . . . . . . . .
Deleting an SAP System Using SAPinst . . . . . . . . . . . .
Running SAPinst to Delete an SAP System . . . . . . . . . .
Deleting the Oracle Database Software . . . . . . . . . . .
Deleting an SAP System Manually . . . . . . . . . . . . .
Deleting an SAP Instance . . . . . . . . . . . . . . . .
Deleting Installation Files, Directories, and Users on a Host . . . .
Deleting the Java Part of an SAP System . . . . . . . . . . .
Deleting the Oracle Database Java Schema . . . . . . . . . .
Deleting an Oracle Database Instance . . . . . . . . . . . .
Troubleshooting . . . . . . . . . . . . . . . . . . . .
Troubleshooting with SAPinst . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
119
119
121
124
127
127
128
128
129
129
130
131
132
132
133
135
136
137
139
139
02/02/2007
PUBLIC
9/140
10/140
PUBLIC
02/02/2007
Introduction
1 Introduction
This document explains how to install SAP Solution Manager 4.0 SR2 (support package stack 09).
SAP Solution Manager 4.0 SR2 is installed as an ABAP+Java system.
For more information about SAP Solution Manager, see SAP Service Marketplace at
https://service.sap.com/solutionmanager.
SAP Solution Manager 4.0 SR2 (SAP Solution Manager) is based on SAP NetWeaver
2004s 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 SAP Solution Manager ABAP
system upgraded to SAP Solution Manager 4.0 SR2.
Constraints
You need to consider the following constraints before you start your installation:
n You can install your SAP system with at least Oracle 10.2 only.
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.
1.1 New Features

You can find the new features of SAP Solution Manager 4.0 SR2 functionality on SAP Service
Marketplace at https://service.sap.com/solutionmanager.
The following tables give an overview of the new features that are related to the installation:
02/02/2007
PUBLIC
11/140
1
1.1
Introduction
New Features
SAP System Installation
Area
Description
SAPinst
As of SAP NetWeaver 2004s, SAPinst has the following new features:

n You can check the prerequisites for your SAP system installation with the Prerequisite
Checker [page 42].
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 51].
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
/usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP system instance.
For more information, see Setting Up File Systems [page 54].
Installation DVDs
12/140
You start the installation from a single Installation Master DVD.
PUBLIC
02/02/2007
1
1.2
Introduction
SAP Notes for the Installation
Oracle Database
New functions in
Oracle Database 10g
n As of the installation of SAP NetWeaver 2004s and SAP Business Suite 2005, new
functions of the Oracle Database 10g release are used.
For more information about the integration of Oracle 10g in the SAP
environment, see SAP Note 720886.
n For the complete list of new features, see further documentation from Oracle,
which you can find at:
http://www.oracle.com/technology/products/database/oracle10g
Operating Systems
Area
Description
Support of Operating
Systems
See the Product Availability Matrix (PAM) on SAP Service Marketplace at

https://service.sap.com/platforms Product Availability Matrix.
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
Installation
The installation of a standalone gateway is now covered in a dedicated

installation guide, available at https://service.sap.com/installnw2004s
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 https://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.
02/02/2007
PUBLIC
13/140
1
1.3
Introduction
Information Available on SAP Service Marketplace
SAP Notes for the Installation
Title
Description
1017542
SAP Solution Manager 4.0 SR2

Installation
Central installation note for SAP

Solution Manager 4.0 SR2.
855498
Installation Prerequisite Checker
SAP Software on UNIX and

Windows: Checking OS
Dependencies
1.3 Information Available on SAP Service Marketplace

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
List of media for

installation or upgrade
for SAP Solution
Manager 4.0 SR2
Master Guide SAP
Solution Manager 4.0
Internet Address
Title
SAP
Media List SAP Solution Manager

4.0 SR2
SAP
Master Guide SAP Solution

Manager 4.0
SAP
Upgrade Guide SAP Solution

Manager 4.0 <OS> <Database>
SAP
Configuration Guide SAP Solution

Manager 4.0 as of SP<SP level of
your SAP Solution Manager system>
Components SAP Solution Manager Release 4.0
Upgrade to SAP
Solution Manager 4.0
Configuration of SAP
Solution Manager
Front End installation
https://service.sap.com/installNW2004s
Front End Installation Guide (this guide

is also available on the Presentation
DVD)
Homogeneous and
heterogeneous system
copy for SAP systems
based on NetWeaver
2004s
Homogeneous and Heterogeneous

System Copy for SAP Systems based on
SAP NetWeaver 2004s
14/140
PUBLIC
02/02/2007
1
1.4
Introduction
Naming Conventions
Description
Internet Address
Migration Guide
Solution Manager
Diagnostics
Setup Advanced Guide

Solution Manager
Diagnostics 04s
System Landscape
Directory
Title
SAP
Migration Guide for Solution Manager

Diagnostics SAP NetWeaver 04s SP
Stack <current stack>
SAP
Advanced Supportability Setup Guide

for Solution Manager Diagnostics SAP
NetWeaver 04S
Installation
Configuration
Post-Installation Guide - System

Landscape Directory of SAP
NetWeaver 2004s
SAP NetWeaver
https://help.sap.com/nw2004s 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
https://help.sap.com
SAP NetWeaver Library in SAP

Help Portal
https://help.sap.com/nw2004s
SAP Notes
https://service.sap.com/notes
Released platforms and operating

systems
https://service.sap.com/platforms
Unicode SAP systems and their

availability
https://service.sap.com/unicode
System sizing (Quick Sizer tool)
https://service.sap.com/sizing
High availability
https://service.sap.com/ha
Security
https://service.sap.com/security
Information on SAP Support

Package Stacks
https://service.sap.com/sp-stacks
System Landscape Directory
https://service.sap.com/sld
SAP Solution Manager
https://service.sap.com/solutionmanager
1.4 Naming Conventions

In this documentation, the following naming conventions apply:
02/02/2007
PUBLIC
15/140
1
1.4
Introduction
Naming Conventions
Terminology
n SAP system refers to SAP Solution Manager.

n ABAP+Java system refers to the two stacks (ABAP and Java) of SAP Solution Manager.
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.
16/140
PUBLIC
02/02/2007
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.
2.
3.
4.
5.
You choose your basic system variant for SAP Solution Manager [page 17].
You plan how to distribute the instances to hosts [page 20].
You identify basic SAP system parameters [page 22].
You decide whether you want to use Unicode and multi-language support [page 29].
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 30].
Only valid for: HA (UNIX)
6. You plan the switchover cluster [page 30] 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 119]
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.
02/02/2007
PUBLIC
17/140
2
2.1
Planning
Basic System Variants for SAP Solution Manager
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.
18/140
PUBLIC
02/02/2007
2
2.1
Planning
Basic System Variants for SAP Solution Manager
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)
02/02/2007
PUBLIC
19/140
2
2.2
Planning
How to Distribute Instances to Hosts
For a maximum system distribution, each instance resides on a separate host.

End of: HA (UNIX)
2.2 How to Distribute Instances to Hosts

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).
20/140
PUBLIC
02/02/2007
2
2.2
Planning
How to Distribute Instances to Hosts
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:
02/02/2007
PUBLIC
21/140
2
2.3
Planning
Basic SAP System Parameters
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).
2.3 Basic SAP System Parameters

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.
22/140
PUBLIC
02/02/2007
2
2.3
Planning
SAP System ID and Database ID
Parameters
Description
Enter Your Values
SAP System ID
The SAP System ID <SAPSID> identifies the whole SAP

system.
...
<SAPSID>
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
Parameters
Description
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.
If you want to install an additional application server
instance, you must use exactly the same instance number as the
existing primary application server instance.
To find out this number, look under the SAP directory
/usr/sap/<SAPSID>/DVEBMGS<nn> on the host of the primary
application server instance.
The value <nn> is the number assigned to the primary application
server instance.
02/02/2007
Enter Your Values
PUBLIC
23/140
2
2.3
Planning
Parameters
Description
Enter Your Values
Name of Instance
Host
Instance Host:
Host name of the specific instance.
To find out the host name, open a command prompt and enter
hostname.
For more information about the allowed host name length and
characters, see SAP Note 611361.
...
Messaging Service
Port
...
Caution
Make sure that all messaging service port numbers on the same
host are unique.
Port number of the SAP Messaging Service:
If you do not specify a value, the default port number is used.
The messaging service port number must be unique for the SAP
system on all hosts.
ABAP Messaging Service Port
There is an external messaging service port using the parameter
rdisp/msserv and an internal messaging service port using the
parameter rdisp/msserv_internal.
The ABAP messaging service uses both the internal and the
external messaging service ports. Both messaging service ports
are configured in the default profile.
The external messaging service port uses the parameter
rdisp/msserv with default value 36<nn>, where <nn> is the
instance number of the ABAP messaging service instance.
The internal messaging service port uses the parameter
rdisp/msserv_internal with default value 39<nn>, where <nn>
is the instance number of the ABAP messaging service instance.
Java Messaging Service Port
The Java messaging service only uses the internal messaging
service port. The Java messaging service 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 messaging service port uses the parameter
rdisp/msserv_internal with default value 39<nn>, where <nn>
is the instance number of the SCS messaging service instance.
For more information about the parameters used for internal and
external messaging service ports, see SAP Note 821875.
24/140
PUBLIC
02/02/2007
2
2.3
Planning
Master Password
Parameters
Description
Enter Your Values
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
Parameters
Description
Enter Your Values
System Administrator SAPinst creates the user <sapsid>adm.

...
User
SAPinst assigns this user to the groups sapsys, oper, dba, sapinst.
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 51].
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.
02/02/2007
PUBLIC
25/140
2
2.3
Planning
Parameter
Description
Enter Your Values
Java Administrator
User
This user is created by SAPinst in the ABAP system.

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

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
Parameter
Description
Enter Your Values
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)
Parameters
Description
Enter Your Values
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.
...
26/140
PUBLIC
02/02/2007
2
2.3
Planning
Parameters
Description
Enter Your Values
For more information, see System Landscape

Directory [page 128].
SLD HTTP Host
The host name of the System Landscape

Directory (SLD)
...
SLD HTTP Port
The HTTP port of the Java system where

the SLD is installed. The following naming
convention applies: 5<instance_number>00.
...
Example
If the instance number of your Java system is

01, the SLD HTTP Port is 50100.
SLD Data Supplier User
and password
n If you want to install a local SLD, SAPinst ...

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

password
n If you want to install a local SLD, SAPinst ...

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

Number
The instance number of the gateway instance ...

of the SLD
SAP System Client
The client in which the ABAP RFC user exists ...
02/02/2007
PUBLIC
27/140
2
2.3
Planning
Parameters Relevant for the File System
Parameters
Description
Your Values
File system for the home directory

user
/home/<username>
...
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>.
n Oracle home
n sapdata home
n Client destination
n sapdata directory
Oracle database file systems
...
Parameters Relevant for the Database
Parameters
Description
Enter Your Values
Code page
The code page that is used by your database (Unicode or

Non-Unicode).
...
Database schemata,
Passwords
The Java database schema is namedSAP<SCHEMA_ID>DB.

Default name is SAPSR3DB.
The ABAP database schema is named SAP<SCHEMA_ID>.
Default name is SAPSR3.
...
Database OS User, Groups Oracle User Ora<dbsid> , Oracle Group oper, dba
...
Database User
Oracle User System
...
Oracle Listener Name,

Oracle Listener Port
n If you install the database instance on a host where no ...

other Oracle database is installed, you normally do not
have to change the default values for Listener Name
and Listener Port.
n If there is already an Oracle database installed on your
installation host, you can either use one listener for
both databases (in this case, see SAP Note 98252 for
more information) or you have to specify an unused
Listener Name and an unused Listener Port for the new
listener
28/140
PUBLIC
02/02/2007
2
2.4
Planning
Multi-Language and Unicode Support
Parameters
Description
Enter Your Values
n All dialog instances of an SAP system must use the same

Listener Port than the database instance.
Oracle Table Spaces
See SAP Note 972263
...
2.4 Multi-Language and Unicode Support

This section describes SAP support for multiple languages with or without Unicode:
n Unicode systems
l The default for all new installations is Unicode.
l Unicode (and the parallel ISO 10646 standard) defines the character set necessary for efficiently
processing text in any language and for maintaining text data integrity. In addition to global
character coverage, the Unicode standard is unique among character set standards, because it
also defines data and algorithms for efficient and consistent text processing. This enables
high-level processing and ensures that all compliant software produces the same results.
The widespread adoption of Unicode over the last decade has made text data truly portable
and formed a cornerstone of the Internet.
l Unicode is the recommended system type for all SAP systems that deploy Unicode-enabled
solutions and components.
l Unicode is the only system type which is fully supported for:
u SAP systems requiring a combination of languages that are based on more than one
non-Unicode code page
u SAP systems that deploy Java applications (for example Java applications, WebDynpro
applications)
u SAP ABAP systems that communicate with Java components (for example via the SAP
Java Connector)
Note
For information about restrictions in non-Unicode system installations refer to SAP Note
838402.
For information about code page support of SAP JAVA Connector refer to SAP Note 794411.
n Non-Unicode systems
SAP supports more than 30 languages in non-Unicode systems, but due to the technical limitations
of non-Unicode code pages, only certain combinations of languages can be used without
restrictions.
Integration
The default setup of the system is Unicode.

02/02/2007
PUBLIC
29/140
2
2.5
Planning
Running Adobe Document Services on Non-Supported Platforms
n If you want to use English only, you must activate the default language settings once.
n If you want to use languages other than English, you must install them and activate the language
settings.
For more information on installing languages, see Performing Initial ABAP Configuration [page 102]
Installing Languages .
More Information
For more information, see SAP Notes 79991 and 73606.
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.
For more information, see SAP Note 925741.
2.6 High Availability: Planning the Switchover Cluster

You can reduce unplanned downtime for your high-availability (HA) SAP system by setting up a
switchover cluster. This setup replicates critical software units known as single points of failure
(SPOFs) across multiple host machines in the cluster. In the event of a failure on the primary node,
proprietary switchover software automatically switches the failed software unit to another hardware
node in the cluster. Manual intervention is not required. Applications accessing the failed software
unit experience a short delay but can then resume processing as normal.
Switchover clusters also have the advantage that you can deliberately initiate switchover to free up a
particular node for planned system maintenance. Switchover solutions can protect against hardware
failure and operating system failure but not against human error, such as operator errors or faulty
application software.
Without a switchover cluster, the SAP system SPOFs central services instance, the database instance,
and the central file share are vulnerable to failure because they cannot be replicated. All of these
can only exist once in a normal SAP system.
30/140
PUBLIC
02/02/2007
2
2.6
Planning
High Availability: Planning the Switchover Cluster
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).
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:
Media Library Documentation HA Documentation .
This covers HA for SAP systems based on SAP NW 2004s and is part of the standard SAP
documentation delivered with SAP NW 2004s.
n Technical Infrastructure Guide: SAP NetWeaver 2004s at:
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:
https://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
02/02/2007
PUBLIC
31/140
2
2.6
Planning
Features
The following figure shows the essential features of a switchover setup:

Figure 6:
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:
32/140
PUBLIC
02/02/2007
2
2.6
Planning
Figure 7:
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:

End of: HA (UNIX)
02/02/2007
PUBLIC
33/140
This page is intentionally left blank.
Preparation
3 Preparation
You have to complete the following preparations:

1. You perform the switchover preparations [page 36] for a high-availability (HA) system.
End of: HA (UNIX)
2.
3.
4.
5.
You check the hardware and software requirements [page 41].

If required, you create operating system users manually [page 51].
You set up file systems and raw devices [page 54].
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 62]
n Exporting and Mounting Directories via NFS for Linux [page 63]
6. You install the SAP front-end software [page 65].
Caution
7. You install the Java Development Kit [page 65].
8. You prepare and mount the installation media [page 67].
If required, you can optionally prepare user management for an external ABAP system [page 124].
02/02/2007
PUBLIC
35/140
3
3.1
Preparation
High Availability: Switchover Preparations
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 30].
Procedure
1. You check that your system meets the hardware and software requirements [page 41] 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 38] using mount points or NFS
b) If required, you configure NFS [page 39], making sure you are using the virtual host name for NFS
to enable NFS switchover..
36/140
PUBLIC
02/02/2007
3
3.1
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 8:
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
02/02/2007
PUBLIC
37/140
3
3.1
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 54].
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.
38/140
PUBLIC
02/02/2007
3
3.1
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.
02/02/2007
PUBLIC
39/140
3
3.1
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)
40/140
PUBLIC
02/02/2007
3
3.2
Preparation
Hardware and Software Requirements
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 42].
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, you have to do one of the following:
l You use the SAP Quick Sizer tool that is available on SAP Service Marketplace at
https://service.sap.com/sizing. You enter information about your planned system and
the tool calculates the requirements.
For more information, see Planning your System Landscape in the Master Guide SAP NetWeaver 2004s,
which is available on SAP Service Marketplace [page 14].
l You contact your hardware vendor, who can analyze the load and calculate suitable hardware
sizing.
n For supported operating system releases, see the Product Availability Matrix on SAP Service
Marketplace at https://service.sap.com/pam.
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.
02/02/2007
PUBLIC
41/140
3
3.2
Preparation
Process Flow
1. If required, you run the Prerequisite Checker standalone [page 42] to check the hardware and software
requirements.
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 43]
n Central system [page 45]
n Distributed or high availability system [page 46]
3. If you want to install additional dialog instances, check the requirements for a Dialog instance
[page 49].
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 65].
n You have prepared the installation master DVD on the required installation host [page 67].
n You make sure that therequired prerequisites are met before starting SAPinst [page 73].
Procedure
1. You start SAPinst [page 76].

2. On the Welcome screen, choose <SAP System> Additional Software Lifecycle Tasks Additional Preparation
Tasks Prerequisites Check .
42/140
PUBLIC
02/02/2007
3
3.2
Preparation
3. Follow the instructions in the SAPinst dialogs and enter the required parameters.
Note
For more information about each parameter, position the cursor on the parameter field and
choose F1 in SAPinst.
When you have finished, the Parameter Summary screen appears summarizing all parameters you have
entered. 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
Hardware
Requirement
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 70].
Disks
n
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.
02/02/2007
PUBLIC
43/140
3
3.2
Preparation
Requirement
Type
Requirement
Example
Here are some examples of hardware-specific commands for RAID devices:

/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)
44/140
PUBLIC
02/02/2007
3
3.2
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
openldap2client
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.
n For the installation of Oracle on SUSE LINUX IA64 you must use at least SLES9 or
higher
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
Type
Requirement
Hardware
n DVD drive
n Hard disk drives with sufficient space for the central instance
For more information, see Setting Up File Systems [page 54] SAP File Systems .
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 67].
n 1.2 GB of temporary disk space for the installation.
n RAM:
3 GB (minimum), 8 GB (recommended)
02/02/2007
PUBLIC
45/140
3
3.2
Preparation
Requirement
Type
Requirement
Java Add-In (ABAP system already exists): 1.5 GB (minimum), 4 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.
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 46]
n Central instance [page 47]
n Database Instance [page 47]
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:
Requirement Type
Requirement
Hardware
n DVD drive
n Hard disk drives with sufficient space for the central services instance
For more information, see Setting up File Systems [page 54].
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 67].
n RAM:
0.5 GB (minimum), 1 GB (recommended)
46/140
PUBLIC
02/02/2007
3
3.2
Preparation
Requirement Type
Requirement
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:
Requirement
Type
Requirement
Hardware
n DVD drive
n Hard disk drives with sufficient space for the central instance.
For more information, see Setting Up File Systems [page 54] 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 67].
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.
3.2.4.3 Requirements for the Database Instance

The database host must meet the following requirements:
The table below lists the most relevant requirements for the Oracle database instance host.
You get the full list of hardware and software requirements from the relevant Oracle database
installation guide for your operating system, which you can find at
http://www.oracle.com/technology/documentation
02/02/2007
PUBLIC
47/140
3
3.2
Preparation
Note
You can access the complete Oracle documentation as a member of the Oracle Technology Network
(OTN) at:
http://www.oracle.com/documentation
For more information on joining OTN, see:

http://www.oracle.com/technology
Recommendation
If you have access to Oracle Metalink we strongly recommend that you read document 169706.1.
This document provides information on all operating system prerequisites and is regularly updated.
Caution
If your database resides on Network Attached Storage (NAS) you need to review and implement the
Oracle NAS guidelines. You need to mount network file systems with specific mount options, which
you can find in the Oracle installation guide.
Caution
Requirement Type
Requirement
Hardware
n DVD drive
n We recommend distribution over three disks (RAID5) for data security
reasons.
To decide how many hard disks are required for your Oracle
database, see the Database System Configuration guide in SAP
Database Guide: Oracle (BC-DB-ORA-DBA) in the SAP Library at
SAP NetWeaver Library SAP
NetWeaver by Key Capability Application Platform by Key Capability
Platform-Wide Services Database Support Oracle SAP Database Guide: Oracle
(BC-DB-ORA-DBA) Getting Started with Oracle and the SAP System .
n Hard disk drives with sufficient space for the database instance. For
more information, see Setting Up File Systems and Raw Devices Oracle File
Systems [page 60].
Recommended total size: Twice the main memory extension (2 x
RAM). For more information, see SAP Note 171356
n 4.3 GB of temporary disk space for every required installation DVD you
have to copy to a local hard disk.
n RAM:
Java Add-In (ABAP system already exists): 500 MB (minimum), 2
GB (recommended)
Software
n If application servers are installed decentralized, Network File System

(NFS) must be installed.
48/140
PUBLIC
02/02/2007
3
3.2
Preparation
Requirement Type
Requirement
n Make sure that the required fonts/code pages are installed.

n Make sure that NLS and corresponding saplocales are installed.
n On the database host, a graphical user interface (GUI) is required for the
Oracle database software installation with runInstaller.
n Check SAP Note 839182 whether you require an interim patch for
the Oracle database installation. In this case, make sure you have the
corresponding Perl version as stated in that SAP Note.
n Review the Oracle-recommended kernel parameters and shell limits
for your operating system with Oracle Database 10g Release 2 (10.2).
These are only recommendations from Oracle for optimizing the
system performance in production environments. If the recommended
settings are not suitable for your system you must tune the kernel
parameters accordingly.
You can get the recommended shell limits and kernel parameters from
the relevant Oracle database installation guide for your operating
system, which you can find at:
http://www.oracle.com/technology/documentation
n If you want to install a Java Add-In for an upgraded ABAP system,

make sure that the parameter compatible is set to 10.2.0 in the
file ORACLE_HOME/dbs/init<dbsid>.ora. For more information, see
Component Upgrade Guide SAP NetWeaver 2004s Application Server ABAP on
SAP Service Marketplace at https://service.sap.com/upgradeNW2004s.
3.2.5 Requirements for a Dialog Instance

The dialog instance host must meet the following requirements:
Requirement Type
Requirement
Hardware
n DVD drive
n Hard disk drives with sufficient space for the dialog instance.
For more information, see Setting up File Systems [page 54].
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 67].
n RAM:
1 GB minimum, 3 GB recommended
Software
n Network File System (NFS) must be installed.
02/02/2007
PUBLIC
49/140
3
3.2
Preparation
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 RHEL3 and RHEL4: SAP Note 722273
n SLES9: SAP Note 797084
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
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 43] and in Checking and Modifying the Linux Kernel [page 50].
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).

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.
50/140
PUBLIC
02/02/2007
3
3.3
Preparation
Creating Operating System Users
3.3 Creating Operating System Users
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
group NIS entries before running SAPinst as described in Creating Operating System Users and Groups
Manually (Optional) [page 51].
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 76].
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.
02/02/2007
PUBLIC
51/140
3
3.3
Preparation
Caution
If you use NFS-V4 file system, then you have to create the ora<dbsid> user on the NFS server. You
can do this either manually or by running Operating System Users and Groups. This user must have the
same user ID as the ora<dbsid> user on the database server.
Otherwise, you get the error message FSL-02098 Could not change owner of ... during the
installation of the database instance.
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.
Users and Their Primary Groups
User
Primary Group
<sapsid>adm
sapsys, oper, dba, sapinst
ora<dbsid>
dba, oper, sapinst
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
<sapsid>adm
oper
<sapsid>adm, ora<dbsid>
dba
sapinst
More Information
Creating Linux Groups and Users (Optional) [page 54]
52/140
PUBLIC
02/02/2007
3
3.3
Preparation
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.
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
n
<sapsid>adm
n
n
<sapsid>adm
sapinst
root
root
See Also
Creating Linux Groups and Users (Optional) [page 54]
02/02/2007
PUBLIC
53/140
3
3.4
Preparation
Setting Up File Systems and Raw Devices
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 RHEL3:
redhat-config-users
l >= RHEL3:
system-config-users
n SUSE LINUX: yast or yast2

Task
Command
Creating groups
groupadd
Modifying groups
groupmod
Deleting groups
groupdel
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 51].
3.4 Setting Up File Systems and Raw Devices

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 54]
n Oracle File Systems [page 60]
n Setting Up Standard File Systems for Linux [page 61]
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.
54/140
PUBLIC
02/02/2007
3
3.4
Preparation
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 38].
End of: HA (UNIX)
Caution
SAPinst uses sapcpe to replicate the kernel automatically

from /usr/sap/<SAPSID>/SYS/exe/run/DIR_CT_RUN to
/usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP system instance.
The following entry in the start profile is responsible for this:
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF),
where $(_PF) points to the instance profile.
Do not delete DIR_CT_RUN from the instance profile 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 105].
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.
02/02/2007
PUBLIC
55/140
3
3.4
Preparation
Figure 9:
SAP File Systems for an ABAP + Java System (Unicode)
Figure 10:
56/140
SAP File Systems for an ABAP + Java System (ABAP Non-Unicode, Java Unicode)
PUBLIC
02/02/2007
3
3.4
Preparation
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.
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

<sapmnt>/<SAPSID>
Space Required
Software and data for one SAP system

This directory is physically located on the SAP
global host. In homogeneous systems, you need
to mount it via NFS (Network File System) for
all hosts belonging to the same SAP system. It
contains the following subdirectories:
n exe
Contains executable kernel programs
n Central Instance:
3.0 GB
Java Add-In (ABAP system
already exists): 1.5 GB
n Central Services Instance:
1.0 GB
n Dialog instance:
no file system required
Note
SAP system ABAP (Non-Unicode) +

Java only: exe contains a folder uc with
a platform-specific subfolder: <sapmnt>/
02/02/2007
PUBLIC
57/140
3
3.4
Preparation
Space Required
<SAPSID>/exe/uc/<platform>
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

for one system
This directory contains files for the operation of
a local instance.
There is a subdirectory <INSTANCE_NAME> for
each instance installed on the local instance
host, whereas data used by several instances are
located in directory SYS.
n Central instance
3.0 GB (Non-Unicode ABAP), 4.0
GB (Unicode ABAP)
n Dialog instance:
2.0 GB (Non-Unicode ABAP), 3.0
GB (Unicode ABAP)
n Central Services Instance :
1.0 GB (non-High Availability)
2.0 GB (High Availability)
Note
SAPinst creates the subfolder

/usr/sap/<SAPSID>/<INSTANCE_NAME>/SDM only
for the central instance of ABAP+Java or Java

systems.
For more information on SDM, see Checking the
Java Documentation [page 115].
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
n
/<sapmnt>/<SAPSID>/profile
/usr/sap/<SAPSID>/SYS/global is
/<sapmnt>/<SAPSID>/global
/usr/sap/<SAPSID>/SYS/exe/run is linked to
linked to
which is
linked to /<sapmnt>/<SAPSID>/exe
/usr/sap/<SAPSID>/SYS/exe/dbg
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.
58/140
PUBLIC
02/02/2007
3
3.4
Preparation
Space Required
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
02/02/2007
Global transport directory for all SAP systems

n For the installation of all
instances: 500 MB
For more information about exporting and
mounting the global transport directory, see
n For the use of all instances: 2 GB
Exporting and Mounting the Global Transport Directory
[page 62]
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:
SAP
NetWeaver Library SAP NetWeaver by Key
Capability Solution Life Cycle Management by Key
Capability Software Life Cycle Management Software
Logistics Change and Transport System
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
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
PUBLIC
59/140
3
3.4
Preparation
Set up the file systems required for the database as described in Oracle File Systems [page 60].
3.4.2 Oracle File Systems

Note
Unicode systems require additional hardware resources. You can find more information about
Unicode SAP systems on SAP Service Marketplace at https://service.sap.com/unicode.
Set up the required file system for the Oracle database before the installation.
Oracle File Systems
File System Name
Description
Space Required
/oracle
Oracle base directory
50 MB for Oracle software
/oracle/client
File system for Oracle client software.

The directory
100 MB
/oracle/client/102_32/instantclient
or
is
created by SAPinst during the installation.
/oracle/client/102_64/instantclient
/oracle/stage/102_32
or
/oracle/stage/102_64
/oracle/<DBSID>
60/140
Installation and upgrade directory for

database software (staging area).
This directory is also used for Oracle
upgrades. We recommend that you do not
delete it after the installation.
3.5 GB
Home directory of user ora<dbsid>.

We recommend that /oracle/<DBSID> does
not reside in the root directory. It must
reside in a file system with support for large
files.
For more information about how to create
file systems larger than 2 GB on your
operating system, see
Setting Up File Systems and Raw Devices for Linux
[page 61].
Therefore, either create /oracle/<DBSID>
as a separate file system with support for
large files or create /oracle as file system
with support for large files and create
/oracle/<DBSID> as a directory in /oracle.
100 MB for files of user

ora<dbsid> (for example,
log files)
PUBLIC
02/02/2007
3
3.4
Preparation
File System Name
Description
Space Required
/oracle/<DBSID>/102_32
Home directory for Oracle instance <DBSID>

(<ORACLE_HOME>).
<ORACLE_HOME> must reside on a local disk. It
cannot be a softlink.
n Database instance : 4.0

GB
n All other instances:
200 MB
Make sure that this file
system has permissions
777.
/oracle/<DBSID>/origlogA
Original set A of redo logs
200 MB
/oracle/<DBSID>/origlogB
Original set B of redo logs
200 MB
/oracle/<DBSID>/mirrlogA
Mirrored set A of redo logs
200 MB
/oracle/<DBSID>/mirrlogB
Mirrored set B of redo logs
200 MB
/oracle/<DBSID>/oraarch
New standard backup file system for Oracle

offline redo logs. Use a separate disk for the
file system /oracle/<DBSID>/oraarch.
The file system /oracle/<SAPSID>/ saparch
still remains but now only contains brbackup
log files. /oracle/<SAPSID>/ saparch is
automatically created by SAPinst.
For the installation,

the archive directory
/oracle/<DBSID>/sapreorg
Working directory for database

administration
1.5 GB
/oracle/<DBSID>/sapdata1
SAP data
SAP data
SAP data
SAP data
For space requirements

of the SAP data file
systems required for
the installation, see the
following file:
or
/oracle/<DBSID>/102_64
/oracle/<DBSID>/oraarch
requires at least 400 MB

of free disk space. For the
operation of your SAP
system, we recommend
that the archive directory
provides enough space
for archives between two
backups. In a production
system, between 300 MB
and 1GB data is archived
daily.
<Export_DVD>/EXP1/
DB/ORA/DBSIZE.XML.
See also SAP Note

972263 Pre-Installation
File requirements of Oracle
sapdata file systems
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.
02/02/2007
PUBLIC
61/140
3
3.5
Preparation
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,/oracle/<DBSID>/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.
62/140
PUBLIC
02/02/2007
3
3.6
Preparation
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 63]
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:

yast2
02/02/2007
PUBLIC
63/140
3
3.6
Preparation
Exporting and Mounting Directories via NFS for Linux (Optional)
You can set up your host as NFS server as follows:

n On Red Hat Linux, enter the following command:
service nfs start
n On SUSE LINUX, enter the following command:

rcnfsserver start
3. To export a directory from a local file system, you can proceed as follows:
n Use one of the following tools:
l Red Hat Linux, RHEL3:
redhat-config-nfs
l Red Hat Linux, >= RHEL4:

system-config-nfs
l SUSE LINUX:
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)
b) To activate the changes (that is, inform the NFS daemon about the changes performed in
/etc/exports), enter the following command:
64/140
PUBLIC
02/02/2007
3
3.7
Preparation
Installing the SAP Front-End Software
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 SAP 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 https://service.sap.com/installNW2004s :
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 2004s 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.
02/02/2007
PUBLIC
65/140
3
3.8
Preparation
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 86]. 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 https://service.sap.com/pam.
b) On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 2004s .
c) Choose tab strip JSE Platforms.
For additional information on the recommended JDK version and about how to obtain it, see
SAP Note 709140.
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 JDK is not already installed
Since JDK is not part of the SAP shipment, you need to download and install it.
n If JDK is already installed
Check the installed version of 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 conguration 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 2004s 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.
c) SAPinst installs the JCE policy files during the installation process.
66/140
PUBLIC
02/02/2007
3
3.9
Preparation
Preparing and Mounting the Installation Media
3.9 Preparing and Mounting the Installation Media
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 69].
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 SAP Solution Manager 4.0 SR2 on SAP Service Marketplace at
https://service.sap.com/instguides SAP Components SAP Solution Manager Release 4.0 .
Note
If you are installing on an existing system using Multiple Components in One Database (MCOD),
the required DVDs will differ .
SAP Instance Installation
Required DVDs
Central services instance, central instance, n SAP Solution Manager 4.0 SR2 Installation Master DVD
dialog instance
n SAP NetWeaver 2004s SR2 Kernel DVD
n SAP Solution Manager 4.0 SR2 Java Components DVD
02/02/2007
PUBLIC
67/140
3
3.9
Preparation
Required DVDs
Oracle database instance (non-MCOD)
n
n
n
n
n
n
n
Oracle database instance (MCOD)
n SAP Solution Manager 4.0 SR2 Installation Master DVD

n SAP Solution Manager 4.0 SR2 Java Components DVD
n SAP Solution Manager 4.0 SR2 Installation Export DVD
SAP Solution Manager 4.0 SR2 Installation Master DVD

SAP NetWeaver 2004s SR2 Kernel DVD
SAP Solution Manager 4.0 SR2 Java Components DVD
RDBMS DVD
RDBMS Client DVD
RDBMS patch DVD
SAP Solution Manager 4.0 SR2 Installation Export DVD
The following table shows the required DVDs for the installation of the Java Add-In for an
existing ABAP System:
Required DVD
Central instance, central services instance, dialog

instance
n SAP Solution Manager 4.0 SR2 Installation

Master DVD
n SAP Solution Manager 4.0 SR2 Java Components
DVD
Oracle database schema (non-MCOD)

Master DVD
DVD
n RDBMS patch DVD
Export DVD
Oracle database schema (MCOD)

Master DVD
DVD
Export 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
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.
68/140
PUBLIC
02/02/2007
3
3.9
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.
02/02/2007
PUBLIC
69/140
3
3.9
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>
70/140
PUBLIC
02/02/2007
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 71].

End of: HA (UNIX)
2. You check the prerequisites for the instances that you want to install before starting SAPinst [page 73].
3. You install your SAP system using SAPinst [page 76].
Note
This note does not apply to the installation of a Java Add-In to an existing ABAP system:
Do not install the Oracle database software before you run SAPinst.
SAPinst stops and prompts you to install the Oracle database [page 89] while the installation of the
database instance is running.
If you install a system into an existing database (MCOD), this action is not required.
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 36].
n You have set the environment variable SAPINST_USE_HOSTNAME [page 76] to specify the virtual host
name for the installation. Alternatively you can specify the virtual host name in the command
to start SAPinst.
02/02/2007
PUBLIC
71/140
4
4.1
Installation
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. Install the central services (SCS) instance with SAPinst [page 76] using the virtual host name on the primary
node, host A.
2. 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 36].
3. Set up the user environment on the standby node, host B.
For more information, see Creating Operating System Users and Groups Manually [page 51]. 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.
4. You enable remote logons as follows:
a) To run certain operating system commands as user root and <sid>adm you have to allow
remote logons from user root to user <sid>adm.
b) You have to create the file .rhosts in the home directory of <sid>adm on each host machine
as follows:
host1 root
host2 root
This allows the user root to perform a remote logon to the <sid>adm account from both
host1 and host2.
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 76] 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.
8. If required, install additional dialog instances with SAPinst [page 76] to replicate the SAP system services that
are not a SPOF. These nodes do not need to be part of the cluster.
72/140
PUBLIC
02/02/2007
4
4.2
Installation
Prerequisites before Starting SAPinst
Note
Make sure that you complete the activities described in High Availability: Post-Installation Steps [page 110].
End of: HA (UNIX)
4.2 Prerequisites before Starting SAPinst
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 22] 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 42].
Procedure
1. If you want to install a dialog instance for an SAP system upgraded to SAP NetWeaver 2004s SR2
or Business Suite 2005 SR2, do the following:
a) Edit DEFAULT.PFL.
b) Set rdisp/msserv_internal to a free port number.
c) Edit the instance profile of the central services instance.
d) Set rdisp/msserv to 0.
e) Set rdisp/msserv_internal to the port number assigned 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 = sapmsSID
...
After the change:
...
rdisp/msserv = sapmsSID
02/02/2007
PUBLIC
73/140
4
4.2
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 119].
5. Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime
Environment (JRE).
74/140
PUBLIC
02/02/2007
4
4.2
Installation
6. Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where <host_name>
is the host where the SAPinst GUI is displayed.
4.2.2 Prerequisites before Starting SAPinst: Distributed

Instances
If you install a database or a dialog instance on a host other than the central instance, you must
mount directories from the central instance.
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 128].
Procedure
1. Log on to the central instance host as user root and export the following directories with root
access to the dialog instance host:
<sapmnt>/<SAPSID>/exe
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
For more information, see Exporting Directories via NFS for Linux [page 63].
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
62]. Otherwise, the installation fails.
2. Log on to the distributed instance host as user root.
3. Create the following mount points and mount them from the central instance host:
<sapmnt>/<SAPSID>/exe
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
02/02/2007
PUBLIC
75/140
4
4.3
Installation
Installing an SAP System Using SAPinst
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 76].
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)
4.3 Installing an SAP System Using SAPinst

The following sections tell you how to install the various instances of an SAP system, or a standalone
engine:
n
n
n
n
n
n
Running SAPinst on UNIX [page 76]

Using SAPinst GUI [page 84]
Interrupted Installation with SAPinst [page 84]
Performing a Remote Installation with SAPinst (Optional) [page 86]
Starting SAPinst GUI Separately (Optional) [page 87].
Entries in the Services File Created by SAPinst [page 89]
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 86], 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.
Procedure
1. Log on to your host as user root.
76/140
PUBLIC
02/02/2007
4
4.3
Installation
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 70].
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 76] 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
$ /sapcd2/IM_HPUX_PARISC/sapinst
n Using an alternative installation directory
02/02/2007
PUBLIC
77/140
4
4.3
Installation
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 73].
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_gui_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 2 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:
78/140
PUBLIC
02/02/2007
4
4.3
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 2 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.
02/02/2007
PUBLIC
79/140
4
4.3
Installation
Remarks
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
Remarks
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:
Remarks
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
80/140
PUBLIC
02/02/2007
4
4.3
Installation
Remarks
information, see Running the Prerequisites Checker in Standalone Mode [page

42].
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 82].
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:
https://service.sap.com/instguidesnw2004s
Installa-
tion
Uninstall
Choose this service to uninstall your SAP Solution Manager system.

For more information, see Deleting an SAP System Using SAPinst [page 129]
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.
When the installation has successfully completed, SAPinst displays the screen Finished successfully.
Note
During the installation of the Oracle database instance, SAPinst stops the installation and prompts
you to install the Oracle database software [page 89].
This action is not required if you install a system into an existing database (MCOD).
After you have finished the installation of the Oracle database, you continue the database instance
installation by choosing OK in the SAPinst GUI of the database instance installation.
02/02/2007
PUBLIC
81/140
4
4.3
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.
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 139].
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 SR2 ABAP.
Make sure that the parameter compatible is set to 10.2.0 in the file init<dbsid>.ora.
Procedure
1. Start SAPinst [page 76].

2. On the Welcome screen, choose SAP Solution Manager 4.0 SR2 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:
82/140
PUBLIC
02/02/2007
4
4.3
Installation
Installation Services for a Java Add-In for ABAP Central or Distributed System
Remarks
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

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
Remarks
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
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
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 .
02/02/2007
PUBLIC
83/140
4
4.3
Installation
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 87].
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.
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.
84/140
PUBLIC
02/02/2007
4
4.3
Installation
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.
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.
02/02/2007
PUBLIC
85/140
4
4.3
Installation
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 73].
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>.
Procedure
1. Log on to your remote host as user root.

Caution
database.
2. Mount the Installation Master DVD.
3. Enter the following commands:
86/140
PUBLIC
02/02/2007
4
4.3
Installation
./sapinst -nogui
For more information, see Running SAPinst on UNIX [page 76].

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 87].
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 86].
If SAPinst GUI runs 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 65] 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:

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.
02/02/2007
PUBLIC
87/140
4
4.3
Installation
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.

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
88/140
PUBLIC
02/02/2007
4
4.4
Installation
Oracle Database Software Installation
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.
4.4 Oracle Database Software Installation

SAPinst prompts you to install the Oracle database.
Caution
Proceed as follows to install the Oracle database software:
Process Flow
1.
2.
3.
4.
You update SAP-specific files in the Oracle stage area [page 90].
You run the Oracle Universal Installer [page 90]
You install the current patch set [page 92]
You install required interim patches [page 92]
02/02/2007
PUBLIC
89/140
4
4.4
Installation
4.4.1 Updating SAP-Specific Files in the Oracle Staging Area

SAPinst extracts the Oracle RDBMS software to the staging area, usually /oracle/stage/<102_32
or 102_64>/database.
The SAP folder located in /oracle/stage/<102_32 or 102_64>/database contains SAP-specific
scripts as well as the response files.
Before starting the Oracle software installation, you need to update this SAP folder so that the newest
versions of the scripts or response files are used.
Procedure
1. Rename the original SAP folder by performing one of the following:

n mv /oracle/stage/<102_32 or 102_64>/database/SAP
/oracle/stage/<102_32 or 102_64>/database/SAP_ORIG
mv /oracle/stage/<102_32 or 102_64>/database/Disk1/SAP
/oracle/stage/<102_32 or 102_64>/database/Disk1/SAP_ORIG
2. Download the file RDBMS_SAP_32.zip (for 32-bit platforms) or RDBMS_SAP_64.zip (for 64-bit
platforms) attached to SAP Note 819830 and copy it to a temporary location such as /tmp.
3. Extract the zip file by performing one of the following:
n cd /oracle/stage/<102_32 or 102_64>/database
unzip /tmp/RDBMS_SAP.zip
You should now see the directory SAP extracted with the updated version of SAP-specific files.
4.4.2 Running the Oracle Universal Installer

To install the Oracle database software you run the Oracle Universal Installer (OUI).
Procedure
1. Start the OUI with the user ora<dbsid> as follows:

n For 32-bit systems, enter the following:
cd /oracle/stage/102_32/database/SAP
./RUNINSTALLER
n For 64-bit systems, enter one of the following:

l cd /oracle/stage/102_64/database/Disk1/SAP
./RUNINSTALLER
./RUNINSTALLER
You see a message that a response file is being generated. It might take several minutes before
you see the OUI screen.
2. Respond to the OUI as follows:
90/140
PUBLIC
02/02/2007
4
4.4
Installation
Prompt or Condition
Action
When you run the OUI for the first time on this host, Accept the OUI proposal and continue by choosing
a dialog box, Specify File Locations Destination..., appears. Next.
This dialog box proposes the inventory location as
/oracle/oraInventory and the installation group
as dba.
Available Product Components
Confirm the default selections by choosing Next.
Product-Specific Prerequisite Checks

This phase checks if all necessary requirements for
installing and running the database have been met.
For items that are flagged as warnings or failed,

review the cause for the warning or failure on screen
and fix the problem if possible.
Alternatively you can verify the items manually
and confirm them by clicking the checkbox. You
can find details about each check by clicking on the
relevant item.
Summary page
Check the information on this page and then start

the installation.
When the Install step has completed, a dialog box

appears.
Execute the file $ORACLE_HOME/root.sh with the user

root, and confirm the dialog box by choosing OK.
If this is the first time that the Oracle software
has been installed on this host, the OUI
also asks you to execute a second script,
/oracle/oraInventory/orainstRoot.sh, as the root
user. Execute this script as well.
Continue by choosing Next.
3. At the end of the installation, in case there are any Configuration Assistants that have been started
automatically (for example, Oracle Net) choose Cancel and terminate the Net Config Assistant.
You can ignore messages that some of the config assistants failed to complete successfully.
The Installer finishes, reporting that the Oracle installation was successful. It also informs
you about the services that it started. You can find the port numbers for these services in the
$ORACLE_HOME/install/portlist.ini file.
4. To exit the OUI, choose Exit and confirm the dialog box that appears.
Note
You can now access the Oracle 10.2 online documentation, which was installed during
the last step. You can find the entry point to the Oracle online documentation at
$ORACLE_BASE/doc/index.htm.
02/02/2007
PUBLIC
91/140
4
4.4
Installation
4.4.3 Installing the Current Patch Set

After the Oracle database software installation , you need to install the current Oracle Database
10g Release 2 (10.2) patch set.
Prerequisites
n For more information on the latest patch set available for Oracle 10.2 see SAP Note 871735.
n For more information on how to install the patch set, see the patch set README file.
Caution
Do not perform any of the post-installation steps mentioned in the patchset README file. The
post-installation steps are to be performed only on an existing Oracle 10.2 database.
At this stage you have only installed the Oracle 10.2 software. The database itself is still not Oracle
10.2. Therefore, make sure that you do not perform the post-installation steps mentioned in
the README file.
n You only have to install the latest (that is, the current) patch set.
Procedure
1. Log on at the operating system level with the ora<dbsid> user.

2. Download and extract the patch set as described in SAP Note 932251.
3. Install the patch set as described on the patch set README file.
4.4.4 Installing Required Interim Patches

After the Oracle database software installation, you need to install required interim patches, using the
Oracle tool OPatch. You need these interim patches in addition to the current patch set.
Prerequisites
n Make sure you have already installed the current patch set [page 92].
n Check SAP Note 871096 to find the list of required patches to be installed.
n Check SAP Note 839182 for instructions on how to use OPatch.
Procedure
1. Log on at the operating system level as the ora<dbsid> user.

2. Install the patches, following the instructions in SAP Note 839182.
92/140
PUBLIC
02/02/2007
4
4.4
Installation
Note
You can apply the patches in any order.

We recommend that you first copy the patches to a directory called ora_patches in $ORACLE_HOME.
3. After all the patches have been successfully applied, you can query the status with the following
command:
$ORACLE_HOME/OPatch/opatch lsinventory
This command lists all the patches that have been applied to the software installation.
02/02/2007
PUBLIC
93/140
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:
https://service.sap.com/releasenotes.
You perform the following post-installation steps:
1. You start and stop the SAP system [page 96].
2. You log on to the SAP system [page 99].
3. You install the SAP license [page 101].
Caution
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
4. You install the SAP Online Documentation [page 101].
Caution
5. You configure the remote connection to SAP support [page 102].
Caution
6. You perform initial ABAP configuration [page 102].
Caution
7. You complete and check the Oracle Installation [page 104]
Caution
8. You apply the latest kernel and Support Packages [page 105].
02/02/2007
PUBLIC
95/140
5
5.1
Post-Installation
Starting and Stopping the SAP System
9. You perform a full backup of the installation [page 107].

10. You perform post-installation steps for Adobe Document Services [page 108].
11. You perform the required post-installation steps for high availability [page 110].
Caution
End of: HA (UNIX)
12. You ensure user security [page 112].

13. You check the Java documentation [page 115] for information that is relevant for running your Java system.
14. You configure SAP Solution Manager [page 116].
5.1 Starting and Stopping the SAP System

You check that 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
96/140
PUBLIC
02/02/2007
5
5.1
Post-Installation
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
start the SAP instance comprising both ABAP and Java.
J2EE to
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>
02/02/2007
PUBLIC
97/140
5
5.1
Post-Installation
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 119].
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
the SAP instance comprising both ABAP and J2EE.
J2EE to stop
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
98/140
PUBLIC
02/02/2007
5
5.2
Post-Installation
Logging On to the SAP System
Caution
Make sure that no SAP instance is running before you enter stopdb on a standalone database server.
No automatic check is made.
5.2 Logging On to the SAP System

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
ABAP+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 You have already started the SAP system.

n You have already installed a front end.
Logging On to the ABAP System
1. Start SAP Logon on the host where you have installed the front end as follows:
n SAP GUI for Windows:
Choose Start Programs SAP Front End SAP Logon .
n SAP GUI for Java:
Choose Start Programs SAP Clients SAP GUI for Java<Release> .
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.
02/02/2007
PUBLIC
99/140
5
5.2
Post-Installation
Logging On to the SAP System
Logging On to the J2EE Engine
You access the J2EE Engine with a URL using a Web browser from your client machines. To log on to
the J2EE engine for the first time, proceed as follows:
1. Establish the default J2EE Engine URL.
2. Log on to the J2EE Engine.
Establishing the J2EE Engine URL
The default URL consists of the installation host name and the port on which the J2EE Engine is
listening. You can use the HTTP or HTTPS protocol; HTTPS is relevant if you are using Secure
Sockets Layer (SSL) communication. To correctly establish the URL, you first have to calculate
the port number as follows:
Protocol
Formula
HTTP
The HTTP port number is based on the number of the J2EE instance on which you
have installed the J2EE Engine, and is calculated according to the following formula:
HTTP Port = 50000 + (100*<instance number>)
Example
If the J2EE Engine is installed on J2EE instance number 01, the port number is:
J2EE Engine HTTP Port = 50000 + (100 * 1) = 50100
HTTPS
The HTTPS port number is calculated according to the following formula:

HTTPS Port = 50000 + (100*<instance number>) + 1
Example
If the J2EE Engine is installed on J2EE instance number 01:

J2EE Engine HTTPS Port = 50000 + (100 * 1) + 1 = 50101
The default J2EE Engine URL looks as follows, depending on the protocol that you are using:
<protocol>://<fully qualified j2ee engine host name>:<protocol_port_number>
Example
If you installed the J2EE Engine on host saphost06 and the instance number of your J2EE Engine is 15,
enter the following URL: http://saphost06:51500
Logging on to the J2EE Engine
1. Open your Web browser, enter the J2EE Engine URL as described above and choose Enter.
The start page of the J2EE Engine appears in the Web browser.
2. Log on by choosing EXAMPLES in the upper right corner of the Web page.
3. In the Welcome screen, enter the following information:
100/140
PUBLIC
02/02/2007
5
5.3
Post-Installation
Installing the SAP License
n User ID: <J2EE Administrator name>

n Password: <J2EE Administrator password>
Note
To deactivate the J2EE Engine, 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.3 Installing the SAP License

Caution
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:
https://help.sap.com/nw2004s SAP NetWeaver SAP NetWeaver Library
Guide Cross-NetWeaver Configurations SAP License Key
Technology Consultant's
More Information
For more information about SAP license keys, see SAP Service Marketplace at
https://service.sap.com/licensekey.
5.4 Installing the SAP Online Documentation

Caution
02/02/2007
PUBLIC
101/140
5
5.5
Post-Installation
Configuring Remote Connection to SAP Support
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 https://help.sap.com/nw2004s.
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.5 Configuring Remote Connection to SAP Support

Caution
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 https://service.sap.com/remoteconnection.
5.6 Performing Initial ABAP Configuration

Caution
Here you find information about how to perform initial ABAP system configuration.
Procedure
1. Go to the following place in the SAP Library:

https://help.sap.com/nw2004s 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 :
102/140
PUBLIC
02/02/2007
5
5.6
Post-Installation
Performing Initial ABAP Configuration
Operation
Section in SAP Documentation
Set up operation modes

transaction RZ04
Configuration
Operation Modes
Set up logon groups

transaction SMLG
Configuration
Logon Load Distribution
Set up administrators
Background Processing
Schedule background jobs
Background Processing
Install a printer
SAP Printing Guide
Configure the system log
Tools for Monitoring the System
SAP Logon
Authorizations for Background Processing
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 .
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 Activating and configuring the integrated Internet Transaction Server (ITS)
l For more information on activating and configuring the ITS, which is installed
automatically with the SAP kernel, see Application Platform by Key Capability ABAP Technology
UI Technology ITS / SAP@Web Studio (BC-FES-ITS) .
l For more information about ITS, see SAP Note 742048, where you can find the necessary
information if you do not want to use the ITS.
02/02/2007
PUBLIC
103/140
5
5.7
Post-Installation
Completing and Checking the Oracle Database Installation
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.
n Configuring business applications
For more information about how to prepare the SAP system for using business applications,
which includes customizing the ABAP system and the business components, see Solution Life
Cycle Management by Key Capability Customizing .
5.7 Completing and Checking the Oracle Database Installation

Caution
The following tasks need to be executed to ensure the availability of important database tools and
to complete the Oracle database installation.
Caution
An Oracle SAP database has to be run in archive log mode. Only this mode guarantees recovery after
system failure. The database archive logs are written to the directory /oracle/<DBSID>/oraarch.
If the file system containing the archive directory is full, all database transactions are stopped
(archiver stuck). Use the tool brarchive to save the archives on tape. For more information, see
the documentation SAP Database Administration: Oracle that is part of the Online Documentation.
Checking Database Utilities brbackup and brarchive
Execute the following steps in order to check whether the database utilities brbackup and brarchive
are installed correctly:
1. Log on as UNIX user ora<dbsid>
2. Verify that the database is running.
3. Start an online backup of a single database file (control
file) to disk:
brbackup u / d disk t online m 0 -c
4. One of the following messages appears:

n BRBACKUP terminated successfully
n BRBACKUP terminated successfully with warnings
5. Start a dummy backup (query mode) of offline redo log files:
104/140
PUBLIC
02/02/2007
5
5.8
Post-Installation
Applying the Latest Kernel and Support Packages
brarchive -u / d disk v scratch q -c
6. One of the following messages appears:

n BRARCHIVE terminated successfully
n No offline redo log files found for
processing
BRARCHIVE terminated successfully with warnings
If brarchive or brbackup did not terminate successfully, refer to the documentation SAP Database
Administration: Oracle (supplied on the Online Documentation CD / DVD) to analyze error messages and to
obtain information on how to solve the problems.
Restricting DB Access to Specific Hosts
If the Oracle security setup defined by the standard installation is not restrictive enough for your
purposes, see SAP Note 186119 to configure the Oracle listener to accept only connections from
specific hosts.
Improving the Performance of the Database
Apply parameter settings as described in SAP Note 830576 to improve the performance of the database.
More Information
n For information on Oracle database configuration, see the documentation SAP Database Guide:
Oracle (BC-DB-ORA-DBA) in the SAP Library at https://help.sap.com/nw2004s SAP NetWeaver
Library SAP NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide Services
Database Support Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA)
n For information on Oracle database administration using Computing Center
Management System (CCMS), see the documentation CCMS: Oracle in the SAP Library at
https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability
Application Platform by Key Capability Platform-Wide Services Database Support Oracle CCMS: Oracle
5.8 Applying the Latest Kernel and Support Packages

You use this procedure to apply the latest kernel and Support Packages for your SAP system from SAP
Service Marketplace.
A newly installed SAP Solution Manager 4.0 SR2 system contains SAP Solution Manager 4.0 support
package stack (SPS) 09. 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 116]).
02/02/2007
PUBLIC
105/140
5
5.8
Post-Installation
Applying the Latest Kernel and Support Packages
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 54].
You can use Java Support Package Manager (JSPM) to apply both the latest ABAP+Java or Java kernel
and Java support packages.
JSPM is a Java standalone tool that you can use with SAP NetWeaver 2004s. 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 it, see https://help.sap.com/nw2004s 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
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. 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:
https://service.sap.com/sp-stacks
b) Alternatively, you can download Support Packages from SAP Service Marketplace at:
https://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:
106/140
PUBLIC
02/02/2007
5
5.9
Post-Installation
Performing a Full Installation Backup
https://service.sap.com/ocs-schedules
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:
https://service.sap.com/noteassistant
5.9 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
The
root file system
n
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 116].
n You have logged on [page 99] as user <sapsid>adm and stopped the SAP system and database [page 96].
n This procedure works on all hardware platforms. For more information on operating
system-specific backup procedures, see your operating system documentation.
02/02/2007
PUBLIC
107/140
5
Post-Installation
5.10 Post-Installation Steps for Adobe Document Services
Backing Up the Installation

2. Manually create a compressed tar archive that contains all installed files:
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 108].
n You perform quick tests for Adobe Document Services (ADS) [page 109].
5.10.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.
108/140
PUBLIC
02/02/2007
5
Post-Installation
4. Choose User Names Change .

5. Choose the Roles tab and assign the role SAP_BC_FP_ICF to the user ADS_AGENT.
Creating Role ADSCallers and Assigning it to ADSUSER
1.
2.
3.
4.
5.
6.
Log on to the ABAP system [page 99].

Call transaction PFCG.
Enter ADSCallers in the Role field.
Choose Role Create .
On the Create Roles screen, choose Role Save .
Choose the User tab and assign the user ADSUSER in the User ID field.
5.10.2 Installation Check and Quick Tests for Adobe

Document Services
This procedure shows you how to check your installation of Adobe Document Services (ADS) entries
for the correct user, security role, passwords, and RFC destination.
Note
This procedure contains only minimal configuration steps to check if the ADS installation with
SAPinst was successful.
For detailed configuration documentation, see the configuration guide for Adobe Document
Services:
n On SAP Service Marketplace at:
SAP Interactive Forms by Adobe Media Library Documentation
Adobe Document Services - Configuration Guide NW 2004s
n In the SAP Library at:
Technology Consultant's Guide
Cross-NetWeaver Configurations Adobe Document Services - Configuration .
https://service.sap.com/adobe
Checking the User and Password
1. Open a web browser and enter the following URL:

http://<J2EE_host>:<J2EE_port>/AdobeDocumentServices/Config
Note
Note that the entries in the URL are case-sensitive.

The web page of the Web service AdobeDocumentServices is displayed.
2. Choose Test.
02/02/2007
PUBLIC
109/140
5
Post-Installation
5.11 High Availability: Post-Installation Steps
3.
4.
5.
6.
Choose rpdata(test...).
Choose Send without entering any parameters.
Enter ADSUser as user name and the password you previously entered for this user .
Choose Submit.
If the setup is correct, the system displays the version number in the response area.
Note
You can ignore the message Required
stream:
PDFDocument not found.
If the setup is not correct, the page does not change and Submit remains on the screen.
Checking the ABAP Connection
1.
2.
3.
4.
Log on to your SAP system.

Call transaction SE38.
Enter the name of the test report FP_PDF_TEST_00.
Choose Execute ( F8 ).
If the setup is correct, the system displays the version number. Otherwise, the system displays a
dialog box with input fields for the user and password. In this case, check your settings for the
ABAP connection.
5.11.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 101]. 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.
110/140
PUBLIC
02/02/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:
https://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.11.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.
02/02/2007
PUBLIC
111/140
5
Post-Installation
5.12 Ensuring User Security
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)

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:
Security Network and Transport Layer Security
Caution
Make sure that you perform this procedure before the newly installed SAP system goes into
production.
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 https://service.sap.com/securityguide:
Operating System and Database Users
User
User Name
Comment
Operating system user
<sapsid>adm
SAP system administrator
ora<dbsid>
Oracle database administrator (that

is, the owner of the database files)
112/140
PUBLIC
02/02/2007
5
Post-Installation
User
User Name
Comment
Oracle database user
SAP<SCHEMA_ID>
Oracle database owner (that is, the

owner of the database tables)
SYSTEM
SYS
OUTLN
DBSNMP
ABAP+Java Users
User
User Name
Comment
SAP system user
SAP*
User exists at least in SAP system clients

000, 001 and 066.
DDIC

000 and 001.
EARLYWATCH
User exists at least in SAP system client

066.
SAPCPIC

000 and 001.
Administrator
The name that you gave this user

during the installation or the default
name J2EE_ADMIN
This users password is stored in secure

storage. Therefore, whenever you
change the administrators password,
you must also change the password in
secure storage.
For more information, see Checking the
SAP Java Documentation [page 115].
Guest

name J2EE_GUEST
Communication user for

the J2EE Engine

name SAPJSF.
Users for Adobe

Document Services (ADS)
ADSUSER

000 and 001.
ADS_AGENT

000 and 001.
02/02/2007
PUBLIC
113/140
5
Post-Installation
User
User Name
Comment
Data supplier user

for System Landscape
000 and 001.
Directory (SLD) (optional) The recommended name is SLDDSUSER.
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
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
Comment
Administrator

name J2EE_ADMIN
This users password is stored in secure

storage. Therefore, whenever you
change the administrators password,
you must also change the password in
secure storage.
For more information, see Checking the
SAP Java Documentation [page 115].
Guest

name J2EE_GUEST
Communication user for

the J2EE Engine

name SAPJSF
Users for Adobe

Document Services (ADS)
ADSUSER
User exists at least in the clients 000 and

001 of the ABAP system.
ADS_AGENT

114/140
PUBLIC
02/02/2007
5
Post-Installation
5.13 Checking the SAP Java Documentation
User
Comment
Data supplier user

for System Landscape
Directory (SLD) (optional) The recommended name is SLDDSUSER.
Note

the installation.
ABAP API user for System The name that you gave this user
Landscape Directory (SLD) during the installation.
(optional)
The recommended name is SLDAPIUSER.
Note

the installation.
5.13 Checking the SAP Java Documentation

Here you can find information about the configuration of the J2EE Engine and about SAP Java
technology in the SAP Library.
Procedure
1. Go to the following place in the documentation:

SAP NetWeaver by Key Capability
Application 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.
02/02/2007
PUBLIC
115/140
5
Post-Installation
5.14 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:
https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability Solution
Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) J2EE Engine Problem
Analysis Scenarios

To configure your SAP Solution Manager 4.0 SR2 system, you have to proceed as follows:
Procedure
1. Log on to the client 000 of the SAP Solution Manager system.

116/140
PUBLIC
02/02/2007
5
Post-Installation
2. Call transaction SPRO.

3. Choose SAP Reference IMG SAP Solution Manager Implementation Guide SAP Solution Manager
n All activities under Advanced Configuration 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
https://service.sap.com/solutionmanager SAP Solution Manager Installation Guides Release
4.0 .
02/02/2007
PUBLIC
117/140
Additional Information
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 119]

n Integration of LDAP Directory Services [page 121]
n Preparing User Management with an External ABAP system [page 124]
Post-Installation
n If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access
[page 127].
n Configuring User Management to Use an LDAP Directory [page 127].
n System Landscape Directory [page 128]
n Heterogeneous SAP System Installation [page 128]
n Deleting an SAP System [page 129]
n Troubleshooting [page 139]
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:
n The installation of an SAP system in a new database
02/02/2007
PUBLIC
119/140
6
6.1
Installation of Multiple Components in One Database (Optional)
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:
l Copying a single component from an MCOD landscape to another database at database level.
120/140
PUBLIC
02/02/2007
6
6.2
n
n
n
n
Integration of LDAP Directory Services (Optional)
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.
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.
You cannot install a Unicode SAP system with a non-Unicode SAP system in one database.
For the first SAP system, the database system ID can be different from the SAP system ID.
For the second SAP system, make sure that you use the same DBSID as for the first SAP system.
If you install a system into an existing database (MCOD), make sure that the SYSTEM tablespace
contains at least 350 MB of free space. If there is not enough space left, increase the size of this
tablespace with BRSPACE or BRTOOLS.
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.
6.2 Integration of LDAP Directory Services (Optional)

The Active Directory is a Lightweight Directory Access Protocol (LDAP) directory. LDAP is a feature of
Windows 2000 or higher that allows important information within a corporate network to be stored
centrally on a server. The advantage of storing information centrally for the entire network is that
you have to maintain data only once, thus avoiding 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.
This section explains the benefits of using the SAP system with the LDAP directory. In addition, it
gives an overview of the configuration steps required to use an SAP system with the directory.
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.
02/02/2007
PUBLIC
121/140
6
6.2
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 Microsoft Management Console (MMC)
For more information on the automatic registration of SAP components in LDAP directories and
the benefits of using it in SAP Logon and MMC, see the documentation SAP System Information in
Directory Services on SAP Service Marketplace at https://service.sap.com/msplatforms Microsoft
Windows Server
SAP Logon
Instead of using a fixed list of systems and message servers, you can configure the SAP Logon in the
sapmsg.ini configuration file to find SAP systems and their message servers from the directory. If
you configure SAP logon to use the LDAP directory, it queries the directory each time Server or Group
selection is chosen to fetch up-to-date information on available SAP systems.
To use LDAP operation mode, make sure that the sapmsg.ini file contains the following:
[Address]
Mode=LDAPdirectory
LDAPserver=
LDAPnode=
LDAPoptions=
Distinguish the following cases:

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.
122/140
PUBLIC
02/02/2007
6
6.2
MMC
The 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 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 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 MMC.
If you need to administer distributed systems, we especially recommend that you use the MMC
together with Active Directory services. For example, you can simplify administration by using the
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 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 MMC.
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.
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 prepare the SAP system to use generic LDAP services, you must perform the following steps:
1. You configure the LDAP directory to store SAP data.
This involves extending the directory schema and creating a container for the SAP data.
2. You set up a user with a password on the server where the SAP system is running to permit the
system to access and modify the LDAP directory.
You do this by running the script ldappasswd.
For more information on how to enable interaction between a generic LDAP directory and the SAP
system, see the documentation SAP System Information in Directory Services in the SAP Service Marketplace
at: https://service.sap.com/msplatforms Microsoft Windows Server
02/02/2007
PUBLIC
123/140
6
6.3
Preparing User Management for an External ABAP System
6.3 Preparing User Management for an External ABAP System

For a Java system, you can also deploy user management for an external ABAP system. In this case,
you configure the User Management Engine (UME) of the J2EE Engine for the user management
of a separate ABAP system.
If you want to connect more than one Java system to the same ABAP system, you need to work out a
concept for the communication, administrator, and guest users for each engine.
You can take one of the following approaches:
Approach
Advantages
Disadvantages
Each Java system uses different

users
No interdependencies between the Initially more administration to

connected engines
create the users in the ABAP system
All Java systems use the same

configuration
You create the users only once and Interdependencies between the
enter the same information for
connected engines:
every Java system that you install. n If you change the password of
any of the users on the ABAP
system, this change affects all
connected engines.
n If you change the administrator
users password, you must also
change the password in secure
storage on all of the connected
J2EE Engines
Recommendation
For security reasons, we recommend the first approach.

The procedures below assume that you are using the first approach.
Prerequisites
n The ABAP system is based on at least SAP Web AS ABAP release 6.20 SP25.
n In transaction PFCG, check that the roles SAP_BC_JSF_COMMUNICATION and
SAP_BC_JSF_COMMUNICATION_RO exist and make sure that their profiles are generated.
n In transaction PFCG, check that the roles SAP_J2EE_ADMIN, SAP_J2EE_GUEST and SAP_BC_FP_ICF
exist. Neither role contains any ABAP permissions, so you do not need to generate any profiles.
n In transaction PFCG, create a role named ADSCallers. You do not need to maintain authorization
data or generate any profiles for that role.
n For more information, see:
Security Identity Management User Management Engine
124/140
PUBLIC
02/02/2007
6
6.3
Note
For more information about role maintenance, see the SAP Library at
Security Identity Management Users and Roles (BC-SEC-USR) SAP Authorization Concept Organizing
Authorization Administration Organization if You Are Using the Profile Generator Role Maintenance Role
Maintenance Functions Changing Standard Roles
Administration of the ABAP system
Perform the following administration steps in the ABAP system:

1. In transaction SU01 create a new communication user and assign it to the role
SAP_BC_JSF_COMMUNICATION_RO.
Recommendation
We recommend that you assign this user the role SAP_BC_JSF_COMMUNICATION_RO for read-only
(display) access to user data with Java tools. If you intend to maintain user data (that is, to change,
create, or delete users) with Java tools, you need to assign the role SAP_BC_JSF_COMMUNICATION
instead.
We recommend that you name the user SAPJSF_<SAPSID_Java_System>.
You can use any password.
In addition, to make sure that this user can only be used for communication connections between
systems and not as a dialog user, assign it the type Communications under Logon data.
2. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_ADMIN. This is your
administrator user in the J2EE Engine.
Recommendation
We recommend that you name the user J2EE_ADM_<SAPSID_Java_System>. You can use any
password.
Caution
Log on to the SAP system once with this user to change its initial password. Because the installer
of the J2EE Engine verifies this password, the installation fails if this password is initial
3. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_GUEST. This is your
guest user in the J2EE Engine.
02/02/2007
PUBLIC
125/140
6
6.3
Recommendation
We recommend that you name the user J2EE_GST_<SAPSID_Java_System>. You can use any
password.
As this user is only used for anonymous access to the system, we recommend you to deactivate
the password and, if required, lock it after installation to prevent anyone from using it for explicit
named logons.
4. In transaction SU01 create the following dialog users :
Caution
You must have changed the initial passwords [page 112] of these users before you start the installation of
the Java system.
n Users for Adobe Document Services (ADS) (optional):
l ADSUSER:
In transaction PFCG, assign the role ADSCallers to this user.
l ADS_AGENT:
In transaction PFCG, assign the role SAP_BC_FP_ICF to this user.
n SLD Data supplier user (optional):
You only have to create this user if you want to install System Landscape Directory (SLD).
The SLD data supplier user name that you enter later on during the Java system installation
must be identical to this user.
Recommendation
We recommend that you name this user SLDDSUSER

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

Note
For more information on SLD users and security roles, see the Post-Installation Guide - SLD of SAP
NetWeaver 2004s at https://service.sap.com/sld Media Library .
Activities for the Java System
Perform the following steps in the Java system:
126/140
PUBLIC
02/02/2007
6
6.4
Creating a User for LDAP Directory Access (Optional)
1. Before the installation of the Java system, make sure that you have the correct user names and
passwords of the users listed above for the separate ABAP system.
2. During the installation of the Java system, make sure that you enter the correct users and
passwords in the corresponding SAPinst dialogs.
6.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/nw2004s 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
02/02/2007
PUBLIC
127/140
6
6.6
System Landscape Directory
6.6 System Landscape Directory

You can configure your SAP Solution Manager 4.0 system for System Landscape Directory (SLD)
as follows:
n As an SLD server (and client)
SLD is part of the installation of every SAP SAP Solution Manager 4.0 system. If you want to
activate SLD, no further installation is required. You only have to perform the configuration of
the SLD server side and the configuration of the SLD security roles.
n As an SLD client
For every system in your landscape that reports data to SLD, you have to configure a corresponding
SLD data supplier. The configuration of the SLD data suppliers can also be performed during the
installation of SAP systems.
SAPinst automatically configures the connection for System Landscape Directory (SLD) according to
the parameters you entered on the related SAPinst screens during the input phase of the installation.
However, you have to perform some of these steps manually if you want to change existing parameters
or if you want to set additional parameters.
6.7 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
This section does not apply to installations of SAP instances in a mixed UNIX and Microsoft
Windows environment.
If you want to install an application server on Windows in a heterogeneous (UNIX) SAP system
environment, you need to follow the instructions in SAP Note 680617.
Procedure
Proceed as follows to store the SAP executables locally:

1.
2.
3.
4.
Install the central instance and the database as described in the installation documentation.
Log on as user root on the dialog instance host.
Create <sapmnt>/<SAPSID>/exe as a local directory on the dialog instance.
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 67].
128/140
PUBLIC
02/02/2007
6
6.8
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.
6.8 Deleting an SAP System

The following sections describe how to delete an SAP system.
Note
This description assumes that the installation of your SAP system has been performed using SAP
standard tools according to the installation documentation.
You can choose one of the following options:
n You delete the SAP system using SAPinst [page 129]. However, you still have to delete the database
manually.
n You delete the SAP system manually [page 132].
6.8.1 Deleting an SAP System Using SAPinst

You can use SAPinst to delete an SAP system.
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.
n If you want to delete a central system (all instances reside on the same host) , you can do this
in one SAPinst run.
1. Run SAPinst to delete the SAP system.
2. Delete the Oracle database software [page 131] manually.
n If you want to delete a distributed system, you have to run SAPinst to delete the required
instances locally on each of the hosts belonging to the SAP system in the following sequence:
1. Dialog instance(s), if there are any
2. Database instance
SAPinst deletes the database instance but you have to delete the Oracle database software [page 131]
manually.
3. Central instance
4. Central services instance
02/02/2007
PUBLIC
129/140
6
6.8
Caution
You cannot delete an SAP system remotely.

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. Before you delete users,
groups, or service entries, make sure that they are no longer required.
Caution
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 132] or run SAPinst on the NFS server.
6.8.1.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
Optional Standalone Unit
Uninstall
Uninstall System / Standalone Engine /
Note
With this SAPinst service you do not delete the database software.
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.
130/140
PUBLIC
02/02/2007
6
6.8
SAPinst first asks you which SAP instances you want to delete.
Make sure that you delete the SAP instances in the correct order, as described in Deleting an SAP
System Using SAPinst [page 129].
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. Delete the database software manually [page 131].
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.8.1.2 Deleting the Oracle Database Software

You use the Uninstall functionality of the Oracle Universal Installer (OUI) to complete the deletion
of the Oracle database software.
Note
This section only applies if you have deleted your SAP system using the Uninstall service of SAPinst.
If you delete your SAP system manually, you delete the Oracle database instance as described in
Deleting an Oracle Database Instance [page 137].
Procedure
1. Start the OUI with the user ora<dbsid> as follows:

./runInstaller

./runInstaller
./runInstaller
You see a message that a response file is being generated. It might take several minutes before
you see the OUI screen.
2. Choose Installed Products or Uninstall Products.
3. Select the database schema you want to uninstall, <DBSID>_102_32 or <DBSID>_102_64.
4. Mark the Oracle 10G database within the selected product.
02/02/2007
PUBLIC
131/140
6
6.8
5. Choose Remove.
6. Confirm your selection with Yes.
7. Choose EXIT.
6.8.2 Deleting an SAP System Manually

Deleting a Complete SAP System Manually
1. You delete the SAP instances [page 132] in the following sequence:
a) Dialog instances, if there are any
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 133].
3. You delete the Oracle database instance [page 137].
Note
The Java database schema is automatically deleted together with the database instance.
Deleting the Java Part of an SAP System
1.
2.
3.
4.
You delete the Java parts of all dialog instances [page 135], if there are any.
You delete the Java part of an SAP system [page 135].
You delete the central services instance [page 132].
You delete the Java database schema of your Oracle installation [page 136].
6.8.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
132/140
PUBLIC
02/02/2007
6
6.8
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>
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.8.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 132].
Procedure
1. If the following directories are mounted with NFS, unmount them:

02/02/2007
PUBLIC
133/140
6
6.8
/<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.
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. Delete the user <sapsid>adm from the groups sapsys, oper, and dba, if this was not done
automatically in the previous step. If one of these groups is now empty, delete the complete group
as described in your operating system documentation.
5. 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.
6. If there are no other SAP instances running on this host, delete the file /usr/sap/sapservices.
134/140
PUBLIC
02/02/2007
6
6.8
6.8.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.
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 =
02/02/2007
PUBLIC
135/140
6
6.8
j2ee/scs/system =
j2ee/ms/port =
4. If lines beginning with the following parameters appear, delete these lines
from the central instance prole and from all dialog instance proles,
/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 =
j2ee/dbdriver =
5. Delete the central services instance [page 132].

6. Delete the Oracle Java database schema [page 136].
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.8.2.4 Deleting the Oracle Database Java Schema

For the ABAP+Java installation, this section describes how to delete the Java database schema for an
Oracle database installed in the existing database of the ABAP system.
Caution
If you have multiple components installed in one database (MCOD), delete the database only if
you also want to delete all components. Otherwise, delete components selectively. For more
information, see SAP Note 399910.
Prerequisites
n Before deleting the Java database schema, stop all SAP instances belonging to this Java database
schema.
n We recommend you to delete the SAP instances before deleting the Java database schema.
136/140
PUBLIC
02/02/2007
6
6.8
Procedure
Caution
Before deleting the Java database schema, make sure that you have a recent offline database backup.
1. Log on as user ora<dbsid>.
2. Start sqlplus and connect to the database. Enter:
sqlplus /nolog
SQLPLUS>connect / as sysdba
3. Enter the following command to delete the database objects of the database schema:
SQLPLUS> drop user SAP<SCHEMA_ID>DB cascade;
4. Enter the following command to get the file name of the corresponding data file in the file system:
SQLPLUS> select file_name from dba_data_files where \
tablespace_name = 'PSAP<SCHEMA_ID>DB';
5. Enter the following command to delete the tablespace of the database schema:
SQLPLUS> drop tablespace PSAP<SCHEMA_ID>DB including contents;
6. Exit sqlplus:
SQLPLUS> exit
7. Delete the data file of tablespace PSAP<SCHEMA_ID>DB from the file system
6.8.2.5 Deleting an Oracle Database Instance

This section describes how to delete an Oracle database that you have installed.
Caution
If you have multiple components installed in one database (MCOD), delete the database only if
you also want to delete all components. Otherwise, delete components selectively. For more
information, see SAP Note 399910.
Prerequisites
n Before deleting the database, stop all SAP instances belonging to this database or to this Java
database schema.
n We recommend that you delete the SAP instances before deleting the database instance.
Procedure
1. Log on as user ora<dbsid>.

2. Start sqlplus and shutdown the database. Enter:
sqlplus /nolog
SQLPLUS> connect / as sysdba
02/02/2007
PUBLIC
137/140
6
6.8
SQLPLUS> shutdown immediate
SQLPLUS> exit
3. Kill the orasrv process if it is running:

ps -ef | grep orasrv (note the process ID <PID>)
kill 9 <PID>
4. Stop the listener process:

lsnrctl stop
5. Use the uninstall functionality of the Oracle Universal Installer (OUI):

a) Start the OUI with the user ora<dbsid> as follows:
./runInstaller

./runInstaller
./runInstaller
You see a message that a response file is being generated. It might take several minutes
before you see the OUI screen.
b) Choose Installed Products or Deinstall Products.
c) Select the database schema you want to uninstall, <DBSID>_102_32 or <DBSID>_102_64.
d) Mark the Oracle 10G database within the selected product.
e) Choose Remove.
f) Confirm your selection with Yes.
g) Choose EXIT.
7. Delete user ora<dbsid> along with its home directory and all subdirectories of this directory:
a) Delete UNIX user ora<dbsid> using the steps appropriate for your operating system.
b) If the home directory of the user was not deleted automatically in the previous step, delete
this directory:
rm -rf <sapsid_adm_home>
Example
For example, enter:

rm -rf /home/orac11
8. Delete user ora<dbsid> from group dba, if this was not done automatically in the previous step.
If the group dba is now empty, delete the complete group using the steps appropriate for your
operating system.
9. Remove the directory /oracle/<DBSID> and sub-directories
rm -rf /oracle/<DBSID>
138/140
PUBLIC
02/02/2007
6
6.9
Troubleshooting
10. If there are no other database instances with the same Oracle release installed on this host, remove
the staging area directory:
n 32-bit Oracle 10G: rm -rf /oracle/stage/102_32
n 64-bit Oracle 10G: rm -rf /oracle/stage/102_64
11. If there are no other Oracle instances on this host, remove the Oracle client software directory
with one of the following commands:
n 32-bit Oracle 10G: rm -rf /oracle/client/102_32
n 64-bit Oracle 10G: rm -rf /oracle/client/102_64
6.9 Troubleshooting
The following section(s) describe the steps that you need to perform manually if SAPinst fails:
n Troubleshooting with SAPinst [page 139]
6.9.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 84].
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.
For more information, see SAP Note 828978.
02/02/2007
PUBLIC
139/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.

SAP Solution Manager 4.0 SR2 On Linux: Oracle: Installation Guide

Uploaded by

Copyright:

Available Formats

You might also like

SAP Solution Manager 4.0 SR2 On Linux: Oracle: Installation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Solution Manager 4.0 SR2 On Linux: Oracle: Installation Guide

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP Solution Manager

Copyright 2007 SAP AG. All rights reserved.

registered trademarks of SAP AG in Germany and in several

Some components of this product are based on Java. Any

Terms for Included Open Source Software

This SAP software contains also the third party open

Part of the software embedded in this product is gSOAP

E) The Customer may distribute original or

hereby granted without fee, provided the above

gross negligence or intent by SAP or (iii) if based

b) Support and Maintenance

F) The exclusion or the limitation of claims in

4. Adobe Document Services

Documentation in the SAP Service

A) Irrespective of the legal reasons, SAP shall only

You can find this document at the following address:

Emphasized words or expressions

Textual cross-references to an internet address, for example, http://www.sap.com

Quicklinks added to the internet address of a homepage to enable quick access to

Hyperlink to an SAP Note, for example, SAP Note 123456

n Output on the screen following a user action, for example, messages

Keys on the keyboard

Setting Up File Systems and Raw Devices . . . . . . . . . . . . .

Performing a Full Installation Backup . . . . . . . . . . .

1.1 New Features

SAP System Installation

As of SAP NetWeaver 2004s, SAPinst has the following new features:

You start the installation from a single Installation Master DVD.

See the Product Availability Matrix (PAM) on SAP Service Marketplace at

The installation of a standalone gateway is now covered in a dedicated

Links in PDF files

1.2 SAP Notes for the Installation

SAP Notes for the Installation

SAP Solution Manager 4.0 SR2

Central installation note for SAP

Installation Prerequisite Checker

SAP Software on UNIX and

1.3 Information Available on SAP Service Marketplace

List of media for

Media List SAP Solution Manager

Master Guide SAP Solution

Upgrade Guide SAP Solution

Configuration Guide SAP Solution

Components SAP Solution Manager Release 4.0

Components SAP Solution Manager Release 4.0

Components SAP Solution Manager Release 4.0

Components SAP Solution Manager Release 4.0

Front End installation

Front End Installation Guide (this guide

Homogeneous and Heterogeneous

Components SAP Solution Manager Release 4.0

Setup Advanced Guide

Components SAP Solution Manager Release 4.0

Migration Guide for Solution Manager

Advanced Supportability Setup Guide

Post-Installation Guide - System

SAP Help Portal