Installation GuideSAP Solution Manager 7.0 Including SAP Enhancement Package 1 On AIX MaxDB

Installation Guide
SAP Solution Manager 7.0 including SAP Enhancement Package

1 on AIX : MaxDB
Using SAPinst
Target Audience
Œ‹Ãÿ\ Technology consultants
Œ‹Ãÿ\ System administrators
PUBLIC
Œ‹ÃçÚfi™Ž#<‹É˛@*ÈRÈG�^àþOß;=šì êTÙýÅvyÂ−E"×»Ð‰Ø”uwˇHê¤±èµ!Š)³h˜ö¾þ¦ñ
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.10 2009-04-30 Updated Version
1.0 2009-04-08 Initial Version
2/162 PUBLIC 2009-04-30

Table of Contents
:*ßfl½ˇ˚-¬−−fFà‚»ÎFÞ4x’ Introduction ........................................................................................................... 7

1.1 New Features ............................................................................................................. 8
1.2 SAP Notes for the Installation .................................................................................. 10
:*ßfl½ˇ˚-¬−−fFà‚»ÎFÞ4xfi Planning ................................................................................................................... 11

2.1 Planning Checklist .................................................................................................... 11
2.2 Installation Options Covered by this Guide ........................................................... 11
2.2.1 Central System .......................................................................................................... 12
2.2.2 Distributed System .................................................................................................... 12
2.2.3 High-Availability System .......................................................................................... 13
2.2.4 Dialog Instance .......................................................................................................... 14
2.3 Hardware and Software Requirements ................................................................... 17
2.3.1 Running the Prerequisite Checker in Standalone Mode (Optional) .................... 18
2.3.2 Requirements for a Central System ........................................................................ 19
2.3.3 Requirements for a Distributed or a High Availability System ............................. 22
2.3.3.1 Requirements for a Central Services Instance ........................................................ 23
2.3.3.2 Requirements for the Central Instance .................................................................. 25
2.3.3.3 Requirements for the Database Instance ................................................................ 28
2.3.4 Requirements for a Dialog Instance ........................................................................ 31
2.4 System Landscape Directory .................................................................................... 33
2.5 Distribution of Components to Disks ..................................................................... 35
2.6 SAP MaxDB System Configuration ......................................................................... 37
2.7 SAP System Transport Host ..................................................................................... 38
2.8 Planning User and Access Management ................................................................. 39
2.9 Basic SAP System Parameters ................................................................................... 40
2.10 High Availability: Planning the Switchover Cluster .............................................. 49
:*ßfl½ˇ˚-¬−−fFà‚»ÎFÞ4x™ Preparation .............................................................................................................. 53

3.1 Preparation Checklist ............................................................................................... 53
3.2 Creating Operating System Users and Groups ....................................................... 53
3.3 Setting Up File Systems and Raw Devices ............................................................... 55
2009-04-30 PUBLIC 3/162

3.3.1 SAP Directories .......................................................................................................... 55
3.3.2 SAP MaxDB Directories ............................................................................................ 62
3.3.3 Setting Up File Systems for a High-Availability System ......................................... 62
3.3.4 Configuring Network File System for a High-Availability System ....................... 64
3.4 Using Virtual Host Names ........................................................................................ 66
3.5 Performing Switchover Preparations for High Availability ................................... 66
3.6 Exporting and Mounting the Global Transport Directory ................................... 67
3.7 Installing the Front-End Software ........................................................................... 68
3.8 Installing the Java Development Kit ....................................................................... 68
3.9 Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive ...... 69
3.10 Preparing the Installation DVDs .............................................................................. 70
%6r®ªuŠùƒ×Łâ©ÆGdîÖ‚ì] Installation .............................................................................................................. 73

4.1 Installation Checklist ................................................................................................ 73
4.2 Installation Checklist — Java Add-In ..................................................................... 77
4.3 Exporting and Mounting Global Directories: Distributed and High-Availability
Systems ...................................................................................................................... 81
4.4 Performing a High-Availability Installation ............................................................ 82
4.5 Running SAPinst ....................................................................................................... 83
4.6 SAPinst Installation Options .................................................................................... 88
%6r®ªuŠùƒ×Łâ©ÆGdîÖ‚ì\ Post-Installation ..................................................................................................... 93

5.1 Post-Installation Checklist ....................................................................................... 93
5.2 Logging On to the Application Server .................................................................... 94
5.3 Configuring User Management ............................................................................... 95
5.4 Ensuring User Security ............................................................................................. 96
5.5 Installing the SAP License ......................................................................................... 101
5.6 High Availability: Setting Up Licenses ..................................................................... 102
5.7 Applying the Latest Kernel and Support Package Stacks ...................................... 103
5.8 Configuring Remote Connection to SAP Support ................................................ 104
5.9 Installing the SAP Online Documentation ............................................................. 104
5.10 Performing Initial ABAP Configuration ................................................................. 104
5.11 Performing Initial Java Configuration ..................................................................... 109
5.12 Performing Post-Installation Steps for Adobe Document Services ...................... 110
5.13 Configuring the Connection to a Central System Landscape Directory ............. 111
5.14 Installing or Upgrading Database Studio for SAP MaxDB ..................................... 111
5.15 Secure Sockets Layer Protocol for Database Server Communication .................. 113
5.15.1 Installing the SAP Cryptographic Library ............................................................... 113
4/162 PUBLIC 2009-04-30

5.15.2 Generating the Personal Security Environment .................................................... 115
5.16 Backing Up the SAP MaxDB Database .................................................................... 117
5.17 Updating the Database Software to the Current Release ...................................... 117
5.18 Installing the SAP Solution Manager Enterprise Edition Add-On (Optional) .... 118
5.19 Performing a Full Installation Backup .................................................................... 118
5.20 Configuring SAP Solution Manager ........................................................................ 119
´&Œª\Øl‰v>ˇ§$ Â²Æ7ÙY£ Additional Information ........................................................................................ 121

6.1 Integration of LDAP Directory Services .................................................................. 121
6.2 Setting up Swap Space for AIX ................................................................................. 125
6.3 Creating AIX Groups and Users .............................................................................. 126
6.4 Setting Up File Systems and Raw Devices for AIX ................................................. 127
6.5 Dialog Instance Installation for an Upgraded System only: Updating
Profiles ........................................................................................................................ 128
6.6 Mounting a CD / DVD for AIX ................................................................................ 130
6.7 Exporting and Mounting Directories via NFS for AIX ........................................... 130
6.8 Additional Information About SAPinst .................................................................. 132
6.8.1 Using SAPinst GUI .................................................................................................... 132
6.8.2 Interrupted Installation with SAPinst ..................................................................... 133
6.8.3 Performing a Remote Installation with SAPinst .................................................... 135
6.8.4 Starting the SAPinst GUI Separately ....................................................................... 136
6.8.5 Entries in the Services File Created by SAPinst ....................................................... 138
6.9 Starting and Stopping SAP System Instances ......................................................... 139
6.9.1 Starting and Stopping SAP System Instances Using the SAP Management
Console ...................................................................................................................... 139
6.9.2 Starting and Stopping SAP System Instances Using Scripts .................................. 143
6.9.3 Starting and Stopping the Diagnostics Agent Using Scripts ................................. 145
6.10 Creating a User for LDAP Directory Access ............................................................ 146
6.11 Accessing the SAP Java Documentation ................................................................. 147
6.12 Initial Technical Configuration for Adobe Document Services ........................... 148
6.13 Initial Technical Configuration for the System Landscape Directory (SLD) ....... 149
6.14 Heterogeneous SAP System Installation ................................................................. 150
6.15 Troubleshooting ....................................................................................................... 150
6.15.1 Troubleshooting with SAPinst ................................................................................ 150
6.16 Deleting an SAP System ........................................................................................... 151
6.17 Deleting a Diagnostics Agent ................................................................................... 152
´&Œª\Øl‰v>ˇ§$ Â²Æ7ÙYÔ Appendix .................................................................................................................. 155
2009-04-30 PUBLIC 5/162

A.1 Online Information from SAP ................................................................................. 155
6/162 PUBLIC 2009-04-30

1 Introduction
1 Introduction
This document explains how to install SAP Solution Manager 7.0 including SAP Enhancement Package
1 (SAP Solution Manager 7.0 EHP 1) using SAPinst in one installation run.
SAP Solution Manager 7.0 EHP 1 is an SAP system based on AS ABAP and AS Java with support package
stack (SPS) 18.
For more information about the current ABAP Support Package stack levels and the kernel patch level
contained in SAP Solution Manager 7.0 EHP 1, see SAP Note 781448.
For more information about the current Java Support Package stack levels contained in SAP Solution
Manager 7.0 EHP 1, see SAP Note 1010428.
The part of the system that is based on AS Java is used for the functions of SAP Solution Manager
Diagnostics.
For more information about SAP Solution Manager, see http://service.sap.com/
solutionmanager.
SAP Solution Manager 7.0 EHP 1 is based on the technology of SAP NetWeaver 7.0 including
Enhancement Package 1 Support Release 1 (SAP NetWeaver 7.0 EHP1 SR1). For more information about
SAP NetWeaver technology, see http://sdn.sap.com/irj/sdn/netweaver.
For more information about the current Support Package stack levels of SAP NetWeaver 7.0 EHP1 SR1,
see SAP Note 789220.
This document also explains how to install the Java Add-In for an existing SAP Solution Manager
ABAP system upgraded to SAP Solution Manager 7.0 EHP 1.
Make sure you have read the documentation Master Guide – SAP Enhancement Package 1 for SAP Solution
Manager 7.0 before you start with this installation guide. The Master Guide is available at:
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1
Constraints
You need to consider the following constraints before you start your installation:
šÀª¡eÂ This document does not describe the installation of SAP enhancement package 1 in an existing
SAP Solution Manager 7.0 system. If you want to do this, use the documentation Update to SAP
Solution Manager 7.0 Enhancement Package 1 – Using SAINT / JSPM, which is also available at http://
service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EHP1
šÀª¡eÂ Your operating system platform must be 64-bit.

NOTE
The only instance, you can still install on 32-bit is the dialog instance.
2009-04-30 PUBLIC 7/162

1 Introduction
1.1 New Features
Naming Conventions
{iı@Ë† SAP Solution Manager refers to SAP Solution Manager 7.0 EHP1.
{iı@Ë† SAP system refers to SAP Solution Manager 7.0 EHP1 system.
{iı@Ë† ABAP+Java system or system based on AS ABAP and AS Java refers to the two stacks (ABAP and Java) of
SAP Solution Manager 7.0 EHP1.
{iı@Ë† Java Add-In refers to the Java Add-In for an existing SAP Solution Manager ABAP system. For example,
you have upgraded your SAP Solution Manager 3.1 or 3.2 system to SAP Solution Manager 7.0
EHP1 and want to use the functionality of diagnostics in SAP Solution Manager.(SAP Solution
Manager Diagnostics).
{iı@Ë† Diagnostics Agent refers to Solution Manager Diagnostics Agent.
Profiling for High Availability

{iı¯îOÔÀÞØ
?ôr1±kï^ßŁ°¦úqFXˇ¼†˛“T—úò¾“ŁW'hD€u–Æ½−‰ŒÓ{Œ
The profile bars with the wording Only valid for: HA (UNIX) – for example, as in this section – refer to
content that is only valid if you are installing a high-availability (HA) system on UNIX.
{iı¥îOÔÈÞ†
pôb1êk£^þŁŁ¦úqX#¼½˛þTüúfi_“É
1.1 New Features

You can find the new features of SAP Solution Manager 7.0 EHP1 at http://service.sap.com/
solutionmanager
The following tables provide an overview of the new features related to the installation:
CAUTION
Make sure that you read the release notes for your SAP system. You can find these at http://
service.sap.com/releasenotes
SAP System Installation

Area Description
SAPinst As of SAP Solution Manager 7.0 EHP1, SAPinst has the following new features:
{iı@Ë† You no longer have to install a Java Runtime Environment (JRE) to start the
SAPinst GUI.
However, you still have to install a Java Development Kit (JDK) to perform the
installation with SAPinst (see Installing the Java Development Kit (JDK) [page 68]).
{iı@Ë† If you want to terminate SAPinst from the SAPinst GUI menu, you now have to
choose SAPinst Cancel . If you choose File Exit , you only terminate the
SAPinst GUI (see Using SAPinst GUI [page 132]).
{iı@Ë† You can directly access installation log files from the SAPinst GUI menu by
choosing SAPinst Log Browser (see Using SAPinst GUI [page 132]).
64-bit support only for As of SAP Solution Manager 7.0, you must install an SAP Solution Manager system
all instances except only on 64-bit operating systems.
dialog instances
8/162 PUBLIC 2009-04-30

1 Introduction
1.1 New Features
Area Description
For the dialog instance, you can still use a 32-bit operating system. Therefore, you
only see the folder Software Life-Cycle Options on the Welcome screen when you start the
installation from a 32-bit installation master DVD.
You might need to install dialog instances on 32-bit operating systems if you want to
use 32-bit SAP NetWeaver components, such as Adobe document services. However,
first check whether such 32-bit components can run on 64-bit operating systems. If
so, we recommend running these 32-bit components on a 64-bit operating system.
SAP Solution Manager 1úøè1( If there is no Diagnostics Agent already installed on this physical or virtual host,
Diagnostics Agent it is installed automatically with an AS Java central instance and dialog instance.
1úøè1( You can also install it as a standalone engine, for example if you want a non-SAP
system to be managed by SAP Solution Manager Diagnostics.
The installation of the Diagnostics Agent as a standalone engine is not described
in this installation guide, but in the Diagnostics Agent Setup Guide, which is available
at http://service.sap.com/diagnostics Media Library .
An SAP Solution Manager Diagnostics Agent (Diagnostics Agent) is a standalone Java
program that runs on each of the systems managed by SAP Solution Manager
Diagnostics. It gathers information and reports to the SAP Solution Manager system.
For more information about the Diagnostics Agent, see http://service.sap.com/
diagnostics .
Maintenance Optimizer All downloadable software components, released after April 2, 2007, are available
exclusively through the Maintenance Optimizer in SAP Solution Manager. This
comprises:
1úøè1( Support Package Stacks, Support Packages, and patches for Java instances, except
for kernel patches
1úøè1( Legal changes
1úøè1( SAP applications and versions that are:
1úøè1G Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and all
applications based on this software, including SAP Business Suite 7
1úøè1G Optional for all SAP applications
For more information, see http://service.sap.com/solman-mopz.
Operating Systems and Platforms

Area Description
Support of Operating 1úøè1( For supported operating system and database releases, see the Product Availability
Systems and Platforms Matrix at http://service.sap.com/pam.
1úøè1( For forums, blogs, content, and community related to all of the supported
databases and operating systems, see the Database and Operating Systems area at
http://sdn.sap.com/irj/sdn/dbos.
Database-Specific Features
Area Description
Database name “MaxDB” is now called “SAP MaxDB”.
2009-04-30 PUBLIC 9/162

1 Introduction
1.2 SAP Notes for the Installation
1.2 SAP Notes for the Installation

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

SAP Note Number Title Description
1276022 SAP Solution Manager 7.0 EHP1 Central installation note for SAP Solution
Installation Manager 7.0 EHP 1.
1088980 Documentation: SAP Solution Information about scenarios, configurations,
Manager implementation, upgrade, maintenance,
security, sizing, end user usage, enhancements
using Support Packages, or problem analyses with
regard to SAP Solution Manager
1010428 End-to-End Diagnostics Information about availability and limitations of
End-to-End Diagnostics.
1164532 Release Restrictions for SAP Customer information on restrictions in the
NetWeaver 7.0 EHP1 production use of certain functions.
820824 FAQ: MaxDB Frequently asked questions (FAQ) on MaxDB
1234384 Inst. NetWeaver 7.0 EhP1 - Problems discovered after the publication of the
Diagnostics Agent installation installation guide or post-installation steps
855498 Installation Prerequisite Checker SAP Software on UNIX, Windows, and IBM i:
Checking OS Dependencies
73606 Supported Languages and Code Information on possible languages and language
Pages combinations in SAP systems
1067221 Central Note for Heterogeneous Heterogeneous ABAP system landscapes on
Installation different operating systems have been released for
some time. Heterogeneous Java system
landscapes on different operating systems have
now also been released. However, not every
combination of operating system and database
system is released. This SAP Note and its related
SAP Notes describe the released operating system
and database combinations.
781448 Support Package levels of Information about ABAP Support Package levels
Solution Manager installations/ and the kernel patch level
upgrades
789220 Support Package level for Information about the ABAP Support Package
NetWeaver Installations/ levels and kernel patch levels contained in the
Upgrades current SAP NetWeaver release.
925741 Adobe Document Services with To use ADS in SAP landscapes on nonsupported
Nonsupported Platforms platforms, you have to install an additional
standalone SAP system with AS Java on a platform
supported by ADS.
10/162 PUBLIC 2009-04-30

2 Planning
2.1 Planning Checklist
2 Planning
2.1 Planning Checklist

You have to complete the following planning activities, which are described in more detail in the linked
sections:
1. You read the documentation Master Guide – SAP Enhancement Package 1 for SAP Solution Manager 7.0 for
an overview of the documents and information resources that you need for the installation and
configuration of SAP Solution Manager 7.0 EHP1. The Master Guide is available at:
http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0
EHP1
2. You identify the required installation option for your system [page 11].
3. You check the hardware and software requirements [page 17].
4. You plan the setup of the System Landscape Directory [page 33].
5. You plan your system configuration [page 37].
6. You decide on the transport host to use [page 38].
7. You plan user and access management [page 39].
8. You identify basic SAP system parameters [page 40].
9. Xdw!4Ÿèł¦_⁄_à�«ÜÐ�:%Q\<ö¦êËï×øC~Í~þÔûã/¥îb˛M«Ì1qÛ4[lêÊ
You plan the switchover cluster [page 49] for a high-availability (HA) system.
Xdw+4Ÿèfi¦⁄à‘ðÜœ�˙%t\<öèêñïëø0~µ~�Ôˆãs
10. You can continue with Preparation [page 53].
2.2 Installation Options Covered by this Guide

This section shows the installation options covered by this installation guide. You have to decide what
exactly you want to install because the steps you have to perform vary according to the installation
option you choose.
XdwÎV Central system [page 12]
XdwÎV Distributed system [page 12]
XdwÎV Xdw!4Ÿèł¦_⁄_à�«ÜÐ�:%Q\<ö¦êËï×øC~Í~þÔûã/¥îb˛M«Ì1qÛ4[lêÊ
High-availability system [page 13]

Xdw+4Ÿèfi¦⁄à‘ðÜœ�˙%t\<öèêñïëø0~µ~�Ôˆãs
XdwÎV You can install one or more dialog instances [page 14] to an existing central, distributed, or high-
availability system.
2009-04-30 PUBLIC 11/162

2 Planning
2.2.1 Central System

You can install a central system on a single host.
In a central system, all main instances run on a single host:
zf§óQ Central services instance (SCS)
zf§óQ Database instance (DB)
zf§óQ Central instance
zfAÖŸõµïfiäO 0ÙÏ
4¾'ýÉCentral ABAP+Java System
Optionally you can install one or more dialog instances. For more information, see Dialog Instance [page
14].
2.2.2 Distributed System

In a distributed system, every instance can run on a separate host:
zf§óQ Central services instance (SCS)
zf§óQ Database instance (DB)
zf§óQ Central instance
NOTE
You can also use the SAP transport host or the SAP global host as your central instance host.
Optionally you can install one or more dialog instances. For more information, see Installation of a Dialog
Instance [page 14].
12/162 PUBLIC 2009-04-30

2 Planning
ó´âAŁtÔBÆ#LÀ{jŸJZfÞgµˇDistributed ABAP+Java System
ó´âHŁsÔIÆ/L™{yŸ‰Z8Þ4µ]7ßùg¯dfi¤%¦Í2>„álþÞ”O§ÓÎzuûUzL%×−
2.2.3 High-Availability System

In a high-availability system, every instance can run on a separate host:
ó´â§°½ ABAP Central Services Instance (ASCS)
ó´â§°½ Java Central Services Instance (SCS)
ó´â§°½ Database instance
ó´â§°½ Central instance
We recommend that you run both the ASCS and the SCS in a switchover cluster infrastructure.
Optionally you can install one to <n> dialog instances. For more information, see Installation of a Dialog
Instance [page 14].
The following figures show examples for the distribution of the SAP instances in a high-availability
system.
2009-04-30 PUBLIC 13/162

2 Planning
];›�?ënŒiÃÀ9~@ ˘ÞAßHigh-Availability System
];›�8è;ŒtÃÃ9ä@3˘¬A¾Õç|Jl($8p,YGö…⁄N
2.2.4 Dialog Instance

You can install one or more dialog instances for an existing SAP system.
A dialog instance can run on:
];›îZö The host of any instance of the existing SAP system (exceptions see below)
];›îZö On a dedicated host
NOTE
If you want to install dialog instances running on an operating system other than the central
instance, see Heterogeneous SAP System Installation [page 150]. For example, you need to do this if your
central instance runs on Solaris but the dialog instance is to run on Windows.
Dialog Instance for a Central System
For example, the following figure shows each of the three dialog instances that are running:
];›îZö On the main host of the SAP system, that is on the host on which the central instance and the
database instance run
];›îZö On dedicated hosts
14/162 PUBLIC 2009-04-30

2 Planning
¡s7\Ùfl?˝¤%\Å‚²Ü† O‘®Dialog Instance for a Central System
For more information, see Central System [page 12].
Dialog Instance for a Distributed System
For example, the following figure shows each of the three dialog instances that are running:
¡s7ºüÙ On the main host of the SAP system, that is on the host on which the central instance and the
database instance run
¡s7ºüÙ On dedicated hosts
We do not recommend you to install dialog instances on the SAP global host.
2009-04-30 PUBLIC 15/162

2 Planning
L‹º |ðÃ°Ø…õŽ"_b‰%ÐYê¿Dialog Instance for a Distributed System
For more information, see Distributed System [page 12].

L‹º)|÷Ã»Ô…§Ž1_£‰|Ð
êû÷˜¬EtŒfØW7ZÍ¦õ¸5ïwá9’f)Í¢™£Ò˝
Dialog Instance for a High-Availability System
For example, the following figure shows each of the three dialog instances that are running on:
L‹ºÆY9 The host of the central instance
L‹ºÆY9 Dedicated hosts
We do not recommend you to install dialog instances on the switchover cluster infrastructure.
16/162 PUBLIC 2009-04-30

2 Planning
2.3 Hardware and Software Requirements
Á™tnGÈ.ó¬Þ¨ªýÝ\˝ç÷ÚDialog Instance for a High-Availability System
For more information, see High-Availability System [page 13].

Á™tmGÏ.ðùÃ¨©ýG\
ç–»æÁ¶?8·ÀÍ`V)o:

You check that your hosts meet the hardware and software requirements for your operating system
and the SAP instances.
CAUTION
If your hosts do not fully meet the requirements, you might experience problems when working
with the SAP system.
Prerequisites
Á™t‹b Contact your OS vendor for the latest OS patches.

Á™t‹b Make sure that the host name meets the requirements listed in SAP Note 611361.
Á™t‹b Check your keyboard definitions.
Á™t‹b If you want to install a printer on a host other than the central instance host (for example, on a
separate database instance host), make sure that the printer can be accessed under UNIX.
Process Flow
1. Check the Product Availability Matrix at http://service.sap.com/pam for supported operating

system releases.
2009-04-30 PUBLIC 17/162

2 Planning
2. Check the hardware and software requirements using:

–ł˛� The Prerequisite Checker in one of two modes:
–ł˛ð Standalone mode (optional) before the installation process
For more information, see Running the Prerequisite Checker Standalone [page 18].
–ł˛ð Integrated in SAPinst (mandatory) during the installation process
For more information, see Running SAPinst [page 83].
NOTE
For the most recent updates to the Prerequisite Checker, always check SAP Note 855498.
–ł˛� The hardware and software requirements checklists for:
–ł˛ð Central system [page 19]
–ł˛ð Distributed or high availability system [page 22]
–ł˛ð If you want to install one or more dialog instances, check the requirements for a dialog
instance [page 31].
3. If you are installing a production system, the values provided by the Prerequisite Checker and
the hardware and software requirements checklists are not sufficient. In addition, check the precise
sizing values in the Sizing Guide – Sizing SAP Solution Manager <Current Release>, which is available at:
http://service.sap.com/instguides SAP Components SAP Solution Manager <Current
Release>
2.3.1 Running the Prerequisite Checker in Standalone Mode

(Optional)
Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check the
hardware and software requirements for your operating system (OS) and the SAP instances.
RECOMMENDATION
We recommend that you use both the Prerequisite Checker and the requirements tables for reference.
NOTE
When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks
the hardware and software requirements in the background.
Prerequisites
–ł˛� You have prepared the installation master DVD on the required installation host [page 70].
–ł˛� You make sure that the required prerequisites are met before starting SAPinst [page 83].
Procedure
1. You start SAPinst [page 83].
2. On the Welcome screen, choose <Your SAP product> Software Life-Cycle Options Additional Preparations
Prerequisites Check .
18/162 PUBLIC 2009-04-30

2 Planning
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 and want to have checked. If you want to make a change, select the relevant parameters
and choose Revise.
4. To start the prerequisites check, choose Next.
Result
The Prerequisite Checker Results screen displays the results found. If required, you can also check the results
in file prerequisite_checker_results.html, which you can find in the installation directory.
RECOMMENDATION
We recommend making sure that your system meets all checked prerequisites before starting the
installation. However, you can still start the installation even if your system does not meet all
prerequisites. In this case, make sure that you know what you are doing.
2.3.2 Requirements for a Central System

If you want to install a central system – that is, all instances reside on one host – the host must meet
the following requirements:
NOTE
The information here is not intended to replace the documentation of the AIX operating system.
For more information, see IBM Systems Information Center AIX PDFs System management Operating
system and device management at:
Ê2v“Ù€ AIX 5.2: http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base/
aix52.htm
Ê2v“Ù€ AIX 5.3: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?

topic=/com.ibm.aix.doc/doc/base/aixinformation.htm
Ê2v“Ù€ AIX 6.1: http://publib.boulder.ibm.com/infocenter/systems/index.jsp

You can perform AIX-specific steps as follows:
Ê2v“Ù€ Manually by entering AIX commands with the appropriate options
Ê2v“Ù€ Using System Management Interface Tool (SMIT), a menu-driven system administration tool
If you have problems with the function keys, you can also use ESC and the corresponding number
to simulate the function key (for example, F4 is equivalent to ESC and 4 ).
2009-04-30 PUBLIC 19/162

2 Planning
Hardware Requirements
Requirement Values and Activities
DVD Drive ÝŒ[¼' ISO 9660 compatible
ÝŒ[¼' You can configure multiple DVD drives, but you cannot mount all of them.
For more information, see Mounting a CD / DVD for AIX [page 130].
CPU The recommended minimum hardware is two physical processor cores.
To check this, do the following:
ÝŒ[¼' On AIX 5.2, enter the following command:
prtconf | grep Processors
Check that the output looks as follows:
Number Of Processors: 2
ÝŒ[¼' On AIX 5.3 or higher, enter the following command:
lparstat -i | grep "Entitled Capacity"
Entitled Capacity : 2.00
Hard Disk Space ÝŒ[¼' Hard disk drives with sufficient space for the SAP system and the database:
For more information about space requirements for the separate file systems
and directories, see Setting Up File Systems [page 55].
ÝŒ[¼' 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 70].
ÝŒ[¼' 1.2 GB of temporary disk space for the installation.
ÝŒ[¼' For data security reasons, distribution over three disks is required. We
recommend you to distribute over five disks.
ÝŒ[¼' To display available disks, enter the following command:
lspv
Disks marked none in the 3rd column are unused.
ÝŒ[¼' To display free space on a disk, enter the following command:
lspv -p <disk_name>
Areas marked free in the 2nd column are unused.
ÝŒ[¼' If an advanced disk array is available (for example, RAID), contact your hardware
vendor to make sure that the data security requirements are covered by this
technology.
RAM 11 GB
To display RAM size in KB, enter the following command:
lsattr -El sys0 -a realmem
Swap Space You need hard disk drives with sufficient space for swap. You can calculate the
required swap space as follows:
ÝŒ[¼' Optimistic strategy:
In addition, you need at least 20 GB for the central instance and at least another
10 GB for the SCS instance and also for every dialog instance.
ÝŒ[¼' Defensive strategy:
3 * RAM, at least 20 GB
In addition, for the database instance you need:
ÝŒ[¼' 0.75 * RAM, if RAM is greater than 8 GB
ÝŒ[¼' 1 * RAM, if RAM is less than 8 GB
For more information about recommended paging space, see SAP Note 1121904.
To display and – if required – modify the existing swap space, use the System
Management Interface Tool (SMIT).
20/162 PUBLIC 2009-04-30

2 Planning

For more information, see Setting up Swap Space for AIX [page 125]
Keyboard î3ÇÃpW You can set the keyboard by typing the following command on the directly
connected console:
smitty chkbd
î3ÇÃpW You can select your keyboard under Motif by setting a language environment
(LANG), for which a National Language Support (NLS) component is installed.
The settings take effect after reboot.
Software Requirements
Operating System To check the operating system version, use the following command:
Version lslpp -l bos.rte
The output must include the following or a larger version number:
bos.rte 5.2.0.50
AIX Kernel Parameters î3ÇÃpW To adjust AIX kernel parameters, see SAP Note 628131.
î3ÇÃpW To adjust the settings for asynchronous I/O (aio) if the database is installed using
file systems, see SAP Note 1157425.
AIX Maintenance Level î3ÇÃpW AIX 6.x
(ML) and Technology The output of the command oslevel -s should be at least 6100-00-01.
Level (TL) î3ÇÃpW AIX 5.3
The output of the command oslevel -s should be at least 5300-05-01 (TL 5 SP
1).
î3ÇÃpW AIX 5.2
The output of the command oslevel -r should be at least 5200-04 (ML 4).
Additional Software Make sure that the following additional file sets are installed:
î3ÇÃpW bos.adt Base Application Development
î3ÇÃpW bos.perf — performance and diagnostics tools
î3ÇÃpW perfagent.tools— performance monitoring tools
î3ÇÃpW bos.perf.libperfstat — Performance Statistics Library
For an overview of the installed file sets, enter the following command:
lslpp –L | more
Lightweight Directory If you want to use LDAP, you require the following LDAP library:
Access Protocol (LDAP) libldap.a
C++ Runtime Check the C++ runtime level with the following commands:
Environment î3ÇÃpW AIX 6.x:
î3ÇÃp8 #lslpp —L xlC.aix61.rte
The output must be at least 9.0.0.1.
î3ÇÃp8 #lslpp —L xlC.rte
î3ÇÃpW AIX 5.x:
î3ÇÃp8 #lslpp —L xlC.aix50.rte
î3ÇÃp8 #lslpp —L xlC.rte
Networking If application servers are installed decentralized, Network File System (NFS) must be
installed.
To test the network connection to the database server, enter the following command:
2009-04-30 PUBLIC 21/162

2 Planning

/etc/ping <db_server_name> 100 10
National Language Make sure that National Language Support (NLS) and corresponding saplocales are
Support (NLS) installed.
Install the necessary local code set by adding an additional language environment as
follows:
1. Start the System Management Interface Tool (SMIT) with the following
command:
smitty mle_add_lang
2. Select the following:
*ðA2‘+ Cultural Conventions to install:
ISO8859-1 German (Germany) [de_DE]
*ðA2‘+ Language Translation to install:
ISO8859-1 German [de_DE]
This step installs the required bos.loc and bos.iconv file sets.
3. Additionally, check that all file sets are in a consistent state by entering the
following command:
lppchk –v
Printer *ðA2‘+ To check whether a file can be printed, enter the following command:
lp -d<printer_name> <test_file>
*ðA2‘+ To check the status of your spool and the printers, enter the following
command:
lpstat -t
2.3.3 Requirements for a Distributed or a High Availability

System
The following sections provide information about the hardware and software requirements in a
distributed system, where the following SAP instances can reside on different hosts:
NOTE
For more information, see IBM Systems Information Center AIX PDFs System management Operating
system and device management at:
*ðA2‘+ AIX 5.2: http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base/
aix52.htm
*ðA2‘+ AIX 5.3: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?

topic=/com.ibm.aix.doc/doc/base/aixinformation.htm
*ðA2‘+ AIX 6.1: http://publib.boulder.ibm.com/infocenter/systems/index.jsp

*ðA2‘+ Manually by entering AIX commands with the appropriate options
*ðA2‘+ Using System Management Interface Tool (SMIT), a menu-driven system administration tool
22/162 PUBLIC 2009-04-30

2 Planning
HkÒ[A0 Central services instance [page 23]

HkÒ[A0 Central instance [page 25]
HkÒ[A0 Database Instance [page 28]
NOTE
If you install multiple SAP system instances on one host, you need to add up the requirements.
2.3.3.1 Requirements for a Central Services Instance

The central services instance host must meet the following requirements:
DVD Drive HkÒ[A0 ISO 9660 compatible
HkÒ[A0 You can configure multiple DVD drives, but you cannot mount all of them.
HkÒ[A0 On AIX 5.2, enter the following command:
HkÒ[A0 On AIX 5.3 or higher, enter the following command:
Hard Disk Space HkÒ[A0 Hard disk drives with sufficient space for the central services instance:
4 GB
and directories, see Setting up File Systems [page 55].
HkÒ[A0 4.3 GB of temporary disk space for every required installation DVD that you
HkÒ[A0 1.2 GB of temporary disk space for the installation.
HkÒ[A0 For data security reasons, distribution over three disks is required. We
HkÒ[A0 To display available disks, enter this command:
lspv
HkÒ[A0 To display free space on a disk, enter this command:
lspv -p <disk_name>
2009-04-30 PUBLIC 23/162

2 Planning

1ð×9£G 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.
RAM 4 GB
Swap Space You need hard disk drives with sufficient space for swap. The required swap space
can be calculated as follows:
1ð×9£G Optimistic strategy:
At least 20 GB for the first SAP instance to be installed on a server and at least
10 GB for each additional active SAP instance on the same server
1ð×9£G Defensive strategy:
For more information about recommended paging space, see SAP Note 1121904.
Keyboard 1ð×9£G You can set the keyboard by typing this command on the directly connected
console:
smitty chkbd
1ð×9£G You can select your keyboard under Motif by setting a language environment
Operating System To check the operating system version, enter the following command:
bos.rte 5.2.0.50
AIX Kernel 1ð×9£G See SAP Note 628131 for more information about kernel parameters with AIX.
Parameters 1ð×9£G Adjust AIX Virtual Memory Management settings as described in SAP Note
973227.
1ð×9£G If the database is installed using file systems, adjust the settings for asynchronous
I/O (aio) as described in SAP Note 1157425.
AIX Maintenance 1ð×9£G AIX 6.x: The output of the command oslevel -s should be at least 6100-00-01.
Level (ML) and 1ð×9£G AIX 5.3: The output of the command oslevel -s should be at least 5300-05-01
Technology Level (TL) (TL 5 SP 1).
1ð×9£G AIX 5.2: The output of the command oslevel -r should be at least 5200-04 (ML
4).
1ð×9£G bos.adt Base Application Development
1ð×9£G bos.perf — performance and diagnostics tools
1ð×9£G perfagent.tools— performance monitoring tools
1ð×9£G bos.perf.libperfstat — Performance Statistics Library
lslpp –L | more
24/162 PUBLIC 2009-04-30

2 Planning

follows:
command:
smitty mle_add_lang
àÈ2z~‰ Cultural Conventions to install:
àÈ2z~‰ Language Translation to install:
following command:
lppchk –v
Access Protocol libldap.a
(LDAP)
C++ runtime Check the C++ runtime level with the following commands:
environment àÈ2z~‰ AIX 6.x:
àÈ2z~ä #lslpp —L xlC.aix61.rte
àÈ2z~ä #lslpp —L xlC.rte
àÈ2z~‰ AIX 5.x:
àÈ2z~ä #lslpp —L xlC.aix50.rte
àÈ2z~ä #lslpp —L xlC.rte
installed.
Test the network connection to the database server with the following command:
Printer àÈ2z~‰ To check whether a file can be printed, enter the following command:
àÈ2z~‰ Check the status of your spool and the printers with this command:
lpstat -t
2.3.3.2 Requirements for the Central Instance

The central instance host must meet the following requirements:
DVD Drive àÈ2z~‰ ISO 9660 compatible
2009-04-30 PUBLIC 25/162

2 Planning

§g3Ú| You can configure multiple DVD drives, but you cannot mount all of
them. For more information, see Mounting a CD / DVD for AIX [page 130].
§g3Ú| On AIX 5.2, enter the following command:
§g3Ú| On AIX 5.3 or higher, enter the following command:
Hard Disk Space §g3Ú| Hard disk drives with sufficient space for the central instance:
9 GB
For more information about space requirements for the separate file
systems and directories, see Setting Up File Systems [page 55] SAP
Directories .
§g3Ú| 4.3 GB of temporary disk space for every required installation DVD that
you have to copy to a local hard disk
§g3Ú| 1.2 GB of temporary disk space for the installation.
§g3Ú| For data security reasons, distribution over three disks is required. We
§g3Ú| To display available disks, enter the following command:
lspv
§g3Ú| To display free space on a disk, enter the following command:
lspv -p <disk_name>
§g3Ú| 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.
RAM 7 GB
§g3Ú| Optimistic strategy:
At least 20 GB for the first SAP instance to be installed on a server and at
least 10 GB for each additional active SAP instance on the same server
§g3Ú| Defensive strategy:
For more information about recommended paging space, see SAP Note
1121904.
26/162 PUBLIC 2009-04-30

2 Planning

Keyboard ój#=31 You can set the keyboard by typing the following command on the directly
connected console:
smitty chkbd
ój#=31 You can select your keyboard under Motif by setting a language
environment (LANG), for which a National Language Support (NLS)
component is installed. The settings take effect after reboot.
Operating System Version To check the operating system version, use the following command:
lslpp -l bos.rte
bos.rte 5.2.0.50
AIX Kernel Parameters ój#=31 To adjust AIX kernel parameters, see SAP Note 628131.
ój#=31 To adjust the settings for asynchronous I/O (aio) if the database is installed
using file systems, see SAP Note 1157425.
AIX Maintenance Level ój#=31 AIX 6.x
Level (TL) ój#=31 AIX 5.3
The output of the command oslevel -s should be at least 5300-05-01 (TL 5
SP 1).
ój#=31 AIX 5.2
ój#=31 bos.adt Base Application Development
ój#=31 bos.perf — performance and diagnostics tools
ój#=31 perfagent.tools— performance monitoring tools
ój#=31 bos.perf.libperfstat — Performance Statistics Library
lslpp –L | more
C++ Runtime To check the C++ runtime level, enter the following commands:
Environment ój#=31 AIX 6.x
ój#=3^ #lslpp —L xlC.aix61.rte
ój#=3^ #lslpp —L xlC.rte
ój#=31 AIX 5.x
ój#=3^ #lslpp —L xlC.aix50.rte
ój#=3^ #lslpp —L xlC.rte
Networking If application servers are installed decentralized, Network File System (NFS) must
be installed.
To test the network connection to the database server, enter the following
command:
2009-04-30 PUBLIC 27/162

2 Planning

National Language Make sure that National Language Support (NLS) and corresponding saplocales
Support (NLS) are installed.
Install the necessary local code set by adding an additional language environment
as follows:
command:
smitty mle_add_lang
0mı˘´ Cultural Conventions to install:
0mı˘´ Language Translation to install:
following command:
lppchk –v
Printer 0mı˘´ To check whether a file can be printed, enter the following command:
0mı˘´ To check the status of your spool and the printers, enter the following
command:
lpstat -t
2.3.3.3 Requirements for the Database Instance

The database host must meet the following requirements:
DVD Drive 0mı˘´ ISO 9660 compatible
0mı˘´ You can configure multiple DVD drives, but you cannot mount all of them. For
more information, see Mounting a CD / DVD for AIX [page 130].
0mı˘´ On AIX 5.2, enter the following command:
0mı˘´ On AIX 5.3 or higher, enter the following command:
Disk space 0mı˘´ Space requirements for SAP data:

0mı˘´ Database software:
0mı˘Û Version 7.6: 500 MB
0mı˘Û Version 7.7: 700 MB
28/162 PUBLIC 2009-04-30

2 Planning

{-³WVL 4.5 GB of temporary disk space for every required installation DVD you have to
copy to a local hard disk.
{-³WVL 1.2 GB of temporary disk space for the installation.
{-³WVL For data security reasons, distribution over three disks is required. We recommend
you to distribute over five disks.
{-³WVL To display available disks, enter the following command:
lspv
{-³WVL To display free space on a disk, enter the following command:
lspv -p <disk_name>
{-³WVL 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.
RAM 1 GB
Swap space {-³WVL 0.75 * RAM if RAM is greater than 8 GB

{-³WVL 1 * RAM if RAM is less than 8 GB
For more information, see SAP Note 1121904.
Keyboard {-³WVL You can set the keyboard by typing this command on the directly connected
console:
smitty chkbd
{-³WVL You can select your keyboard under Motif by setting a language environment
(LANG), for which a National Language Support (NLS) component is installed. The
settings take effect after reboot.
Operating System Version To check the operating system version, enter the following command:
lslpp -l bos.rte
bos.rte 5.2.0.50
AIX Kernel Parameters {-³WVL To adjust AIX kernel parameters, see SAP Note 628131.
{-³WVL To adjust AIX Virtual Memory Management settings, see SAP Note
973227.
AIX Maintenance Level (ML) and {-³WVL AIX 6.x: The output of the command oslevel -s should be at least
Technology Level (TL) 6100-00-01.
{-³WVL AIX 5.3: The output of the command oslevel -s should be at least
5300-05-01 (TL 5 SP 1).
{-³WVL AIX 5.2: The output of the command oslevel -r should be at least
5200-04 (ML 4).
Additional software Make sure that the following additional file sets are installed:
2009-04-30 PUBLIC 29/162

2 Planning

Álm"4ß bos.adt Base Application Development
Álm"4ß bos.perf — performance and diagnostics tools
Álm"4ß perfagent.tools— performance monitoring tools
Álm"4ß bos.perf.libperfstat — Performance Statistics Library
lslpp –L | more
Lightweight Directory Access If you want to use LDAP, you require the following LDAP library:
Protocol (LDAP) libldap.a
C++ runtime environment Check the C++ runtime level with the following commands:
Álm"4ß AIX 6.x
Álm"4° #lslpp —L xlC.aix61.rte
Álm"4° #lslpp —L xlC.rte
Álm"4ß AIX 5.x
Álm"4° #lslpp —L xlC.aix50.rte
Álm"4° #lslpp —L xlC.rte
Networking If application servers are installed decentralized, Network File System (NFS)
must be installed.
To test the network connection to the database server, enter the following
command:
National Language Support (NLS) Make sure that National Language Support (NLS) and corresponding
saplocales are installed.
Install the necessary local code set by adding an additional language
environment as follows:
1. Start the System Management Interface Tool (SMIT) with the
following command:
smitty mle_add_lang
Álm"4ß Cultural Conventions to install:
Álm"4ß Language Translation to install:
3. Additionally, check that all file sets are in a consistent state with this
command:
lppchk –v
Printer Álm"4ß To check whether a file can be printed, enter the following command:
Álm"4ß To check the status of your spool and the printers, enter the following
command:
lpstat -t
30/162 PUBLIC 2009-04-30

2 Planning
2.3.4 Requirements for a Dialog Instance

The dialog instance host must meet the following requirements:
NOTE
\—Q…£h Manually by entering AIX commands with the appropriate options
\—Q…£h Using System Management Interface Tool (SMIT), a menu-driven system administration tool
DVD Drive \—Q…£h ISO 9660 compatible
\—Q…£h You can configure multiple DVD drives, but you cannot mount all of them.
\—Q…£h On AIX 5.2, enter the following command:
\—Q…£h On AIX 5.3 or higher, enter the following command:
Hard Disk Space \—Q…£h Hard disk drives with sufficient space for the dialog instance.
6 GB
and directories, see Setting Up File Systems [page 55].
\—Q…£h 4.3 GB of temporary disk space for every required installation DVD that you
\—Q…£h 1.2 GB of temporary disk space for the installation.
\—Q…£h For data security reasons, distribution over three disks is required. We
\—Q…£h To display available disks, enter the following command:
lspv
\—Q…£h To display free space on a disk, enter the following command:
lspv -p <disk_name>
\—Q…£h 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.
RAM 7 GB
2009-04-30 PUBLIC 31/162

2 Planning

Ä⁄ˇ<Ž Optimistic strategy:
At least 20 GB for the first SAP instance to be installed on a server and at least
10 GB for each additional active SAP instance on the same server
Ä⁄ˇ<Ž Defensive strategy:
For more information about recommended paging space, see SAP Note
1121904.
Keyboard Ä⁄ˇ<Ž You can set the keyboard by typing the following command on the directly
connected console:
smitty chkbd
Ä⁄ˇ<Ž You can select your keyboard under Motif by setting a language environment
Operating System To check the operating system version, use the following command:
bos.rte 5.2.0.50
AIX Kernel Parameters Ä⁄ˇ<Ž To adjust AIX kernel parameters, see SAP Note 628131.
Ä⁄ˇ<Ž To adjust the settings for asynchronous I/O (aio) if the database is installed using
file systems, see SAP Note 1157425.
AIX Maintenance Level Ä⁄ˇ<Ž AIX 6.x
Level (TL) Ä⁄ˇ<Ž AIX 5.3
The output of the command oslevel -s should be at least 5300-05-01 (TL 5 SP
1).
Ä⁄ˇ<Ž AIX 5.2
Ä⁄ˇ<Ž bos.adt Base Application Development
Ä⁄ˇ<Ž bos.perf — performance and diagnostics tools
Ä⁄ˇ<Ž perfagent.tools— performance monitoring tools
Ä⁄ˇ<Ž bos.perf.libperfstat — Performance Statistics Library
lslpp –L | more
32/162 PUBLIC 2009-04-30

2 Planning
2.4 System Landscape Directory

follows:
command:
smitty mle_add_lang
$5/Ï¤‰ Cultural Conventions to install:
$5/Ï¤‰ Language Translation to install:
3. Additionally, check that all file sets are in a consistent state with the following
command:
lppchk –v
C++ runtime Check the C++ runtime level with the following commands:
environment $5/Ï¤‰ AIX 6.x:
$5/Ï¤ä #lslpp —L xlC.aix61.rte
$5/Ï¤ä #lslpp —L xlC.rte
$5/Ï¤‰ AIX 5.x
$5/Ï¤ä #lslpp —L xlC.aix50.rte
$5/Ï¤ä #lslpp —L xlC.rte
SAP kernel Make sure that the SAP kernel of the central instance has at least the patch level of
the SAP kernel on the SAP Kernel DVD that is used for the installation of the dialog
instance.
We recommend that you apply the most current SAP kernel from the SAP Service
Marketplace at http://service.sap.com/swdc.
installed.
To test the network connection to the database server, enter the following command:
Printer $5/Ï¤‰ To check whether a file can be printed, enter the following command:
$5/Ï¤‰ To check the status of your spool and the printers, enter the following command:
lpstat -t

The System Landscape Directory (SLD) is the central directory of system landscape information relevant
for the management of your software lifecycle. It contains a description of your system landscape (that
2009-04-30 PUBLIC 33/162

2 Planning
is, software components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape.
In this way, the System Landscape Directory acts as a central information provider for SAP and third-
party tools that use this data to deliver the services you need to keep your landscape up and running.
The System Landscape Directory is automatically installed with the SAP Solution Manager 7.0 EHP1
system.
There are two options to set up your SAP Solution Manager system landscape:
¢_3ð„] Manual maintenance of the system landscape:
No production SLD is required, instead you have to maintain the SAP Solution Manager system
landscape manually in transaction SMSY.
ABAP systems can provide their system information via trusted RFC connections to SAP Solution
Manager.
CAUTION
Manual maintenance of transaction SMSY causes a high effort for initial data entry (approx
1,5h per non ABAP system) and ongoing maintenance for each change to the non ABAP
system. Therefore we do not recommend this option.
¢_3ð„] Automatic maintenance of the system landscape:
You have to install a local SLD on the SAP Solution Manager system with connection and
replication from the production SLD instances in your existing landscape.
SAP Solution Manager expects that you already run System Landscape Directories (SLDs) for
production usage like for WebDynpro or Process Exchange (XI). On top, SAP Solution Manager
needs an SLD (called local SLD) itself as a complete catalog of technical systems and complete
catalog of installed software components as data provider for transaction SMSY and as persistence
for own WebDynpro connection data.
RECOMMENDATION
To avoid conflicts between the availability of your production SLDs and SAP Solution Manager
(such as SAP Solution Manager upgrade or Root Cause Analysis on the production SLD),
install this local SLD on the SAP Solution Manager system.
More Information
For more information, see the Root Cause Analysis Installation and Upgrade Guide, which you can find at one
of the following:
¢_3ð„] http://service.sap.com/diagnostics End-to-End Root Cause Analysis Documentation Library
Installation and Configuration Root Cause Analysis Installation and Upgrade Guide
¢_3ð„] http://service.sap.com/instguides SAP Components SAP Solution Manager <Current
Release>
34/162 PUBLIC 2009-04-30

2 Planning
2.5 Distribution of Components to Disks

When you install the SAP system, the installation tools prompt you to enter drive letters for the main
components of the system. This lets you distribute components to disks in the system as required. How
you do this significantly affects system throughput and data security, so you need to plan it carefully.
The best distribution depends on your environment and must reflect factors such as the size of the
components involved, security requirements, and the expected workload.
When you work out the assignment of components to disks, you first need to obtain an overview of
the main components and their corresponding directories. On the basis of sample configurations and
the recommendations provided in this documentation, you can then choose the best setup for your
particular system.
In most situations, SAP systems are installed on RAID arrays to guarantee data redundancy. Therefore,
this documentation focuses on RAID subsystems and drives.
Features
The following graphic shows how you can distribute the main directories created during the installation
to Redundant Arrays of Independent Disks (RAID). The distribution is suitable for an average-sized
production system. Keep in mind that this is only an example and that no single solution fits all
environments.
"−Åtãæ½‹BÆÅ^ê<^�y§¥RAID Distribution
2009-04-30 PUBLIC 35/162

2 Planning
This configuration is suitable for the main host of a central system or the database server of a standalone
database system. You can assign the components on the left to any of the arrays shown. You do not
necessarily have to place the transport directory on the central instance host.
Array 1 <DRIVE>:\sapdb\<DBSID>\sapdata\DISKD001
...
<DRIVE>:\sapdb\<DBSID>\sapdata\DISKD999
Array 2 <DRIVE>:\sapdb\<DBSID>\saplog\DISKL001
<DRIVE>:\sapdb\<DBSID>\saplog\M_DISKL001
\usr\sap
<DRIVE>:\sapdb
<DRIVE>:\sapdb\<DBSID>\sapsys
Array 3 <DRIVE>:\sapdb\<DBSID>\saplog\M_DISKL001
<DRIVE>:\sapdb\<DBSID>\saplog\DISKL001
This setup has the following key features:

$˘ðn%° Security of the Logs
The security of the logs is crucial. The logs record all the changes made to the database and so
provide the information that is necessary to recover a damaged database. Therefore, it is important
that they are stored securely and that you never lose them at the same time as the database data.
By placing the redo logs on a different array to the database data, you can make sure that they
are not lost if the array with the database data is severely damaged.
$˘ðn%° Performance
You can reduce I/O bottlenecks by placing the original logical log on a different array than the
mirrored log. Original and mirrored logs are written in parallel. If they are located on the same
array, this results in a high level of write activity that has to be handled by the same controller. By
separating original and mirrored logs, you can distribute the write activity to two different arrays,
so reducing I/O bottlenecks.
$˘ðn%° RAID
By using RAID 1 arrays for the original and mirrored logs, you obtain high data security and good
performance. The data is written to a primary disk and duplicated identically to a second disk. If
one disk fails, the data is still intact on the second disk.
The use of RAID 5 for the database ensures fault tolerance. The data is striped over all the disks in
the array together with parity information. If one disk fails, the parity information is used to
automatically reconstruct the data lost on the damaged disk.
$˘ðn%° Number of RAID Arrays
In the example above, three RAID 1 arrays are used for the redo logs to ensure optimal performance
and security. If you do not need the disk capacity offered by three arrays and can accept reduced
performance, consider using a single array. In this case, you can use a single RAID 1 array for the
original and mirrored logs.
36/162 PUBLIC 2009-04-30

2 Planning
2.6 SAP MaxDB System Configuration
2.6 SAP MaxDB System Configuration

Security Issues
ûGÓk For security reasons the logs must be mirrored using the operating system or hardware.
CAUTION
If a system runs without mirroring, you might lose all data since the last complete backup in
the event of a disk crash.
RECOMMENDATION
We recommend mirroring the logs using the operating system or hardware.

If this is not possible, then mirror the logs with the database mirroring provided by SAP
MaxDB.
ûGÓk We recommend you to run the database with raw devices.
CAUTION
Never use RAID 5 systems for database log volumes.

ûGÓk Do not replace file systems by softlinks.
ûGÓk Raw devices are secure in the event of a system crash.
Security Concept for Database Software Owner
As of SAP MaxDB 7.5.00 there is a new security concept for the database software owner. Authorization
to access directories and files is restricted, and a new user and user group is required:
ûGÓk User is sdb (SAP MaxDB default)
ûGÓk User group is sdba (SAP MaxDB default)
This user and group are the only database software owners on the host. For security reasons, the user
does not have a logon for the system, which guarantees the physical integrity of the database files.
Database processes run under this user, which makes sure that several different users cannot manipulate
the database system.
Performance Issues
ûGÓk Store database data files and logs on different disks

ûGÓk Since the logs are written synchronously, they produce the most I/O activity of all database files.
ûGÓk It is possible to put the logs on the same disk as/sapmnt, but this is not recommended.
ûGÓk Use the partitions DISKD<N> exclusively for data files of the database.
ûGÓk If paging or swapping areas and log data reside on the same disk, the performance is poor.
ûGÓk For database volumes, raw devices are faster than files. The slowest disk drive determines the I/O
performance of the database.
Different SAP MaxDB Systems
For performance reasons, we recommend that you do not install several database systems (for different
SAP systems) on one single host. If you still decide to do so, you must install each database as described
in this documentation.
2009-04-30 PUBLIC 37/162

2 Planning
2.7 SAP System Transport Host
Recommended Configuration
The following graphic shows an optimal distribution of the database data on different disks.
Optimal Distribution
T·
³Y£M«Øðé"¹§¤;³f=
For more information about the file systems for the SAP system and the SAP MaxDB database, see Setting
Up File Systems [page 55].
2.7 SAP System Transport Host

The transport host contains the transport directory used by the SAP transport system to store transport
data and change SAP system information, such as software programs, data dictionary data, or
customization data. If you have several SAP systems, they are usually organized in transport domains.
In most cases, all SAP systems in a transport domain have a common transport directory.
When you install an SAP system, you have to decide which transport host and directory you want to
use for your SAP system:
T·
U|j Use the transport directory that SAPinst creates during the installation of the SAP system by default
on the global host:
SAPinst by default creates the transport directory on the global host in /usr/sap/trans.
T·
U|j Use a transport directory located on a host other than the default host:
T·
U| You can use an existing transport directory and host in your SAP system landscape.
T·
U| You can set up a new transport directory on a different host.
38/162 PUBLIC 2009-04-30

2 Planning
2.8 Planning User and Access Management
In either case, you must prepare this host for use by the new SAP system. For more information,
see Exporting and Mounting the Global Transport Directory [page 67].
More Information
KÍf.¨“ Setting Up File Systems and Raw Devices [page 55]
KÍf.¨“ See the SAP Library:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English
SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability
Software Life Cycle Management Software Logistics Change and Transport System Change and Transport System
– Overview (BC-CTS) Basics of the Change and Transport System Transport Management System – Concept
2.8 Planning User and Access Management

You have to plan how you want to configure user and access management for your SAP system to be
installed.
Before you add a newly installed SAP system to your system landscape, you must decide which kind
of user management you want to use:
KÍf.¨“ Use AS ABAP.
KÍf.¨“ Use an LDAP directory as the data source for user data.
Procedure
Using AS ABAP
You install your SAP system as described in this installation guide. During the installation, the SAP
system is automatically configured to use AS ABAP as data source for the User Management Engine
(UME). After the installation has finished, you can still change the user management configuration.
For more information, see Configuring User Management [page 95].
Using an LDAP directory as the Data Source for User Data
1. You install your SAP system as described in this installation guide.

2. Configure the user management of the newly installed SAP system to use and LDAP directory.
For more information, see Configuring User Management [page 95].
More Information
For more information about configuring the user management of your SAP system to be installed, see
the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP
NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management Identity Management for
System Landscapes Integration of User Management in Your System Landscape
2009-04-30 PUBLIC 39/162

2 Planning
2.9 Basic SAP System Parameters

SAPinst prompts for input parameters during the Define Parameters phase of the installation.
The tables below list the basic system parameters that you need to specify before installing your SAP
system. For all other SAP system parameters, use the F1 help in the SAPinst screens.
You can install your SAP system either in Typical or Custom mode:
Ñ-›í]X Typical
If you choose Typical, the installation is performed with default settings. This means that you only
have to respond to a small selection of prompts including at least the following, which are described
in the corresponding tables below:
Ñ-›í]7 SAP system ID and database ID
Ñ-›í]7 SAP system profile directory – only for systems with instances on separate hosts
Ñ-›í]7 Master password
Ñ-›í]7 JCE Unlimited Strength Jurisdiction Policy files archive
Ñ-›í]7 System Landscape Directory (SLD) destination
If you want to change any of the default settings, you can do so on the Parameter Summary screen.
Ñ-›í]X Custom
If you choose Custom, you are prompted for all parameters. At the end, you can still change any of
these parameters on the Parameter Summary screen.
NOTE
You cannot change from Custom to Typical mode or from Typical to Custom mode on the Parameter
Summary screen.
The tables below list the basic system parameters that you need to determine before installing your
SAP system. For all other SAP system parameters, use the F1 help in the SAPinst dialogs.
Java Development Kit and JCE Unlimited Strength Jurisdiction Policy Files Archive
Parameters Description
Java Development Kit (JDK) A valid JDK is required for the Java application server. For more
information about JDK versions supported by SAP and about how to
install them, see Installing the Java Development Kit [page 68].
JCE Unlimited Strength Jurisdiction You need to obtain the Java(TM) Cryptography Extension (JCE)
Policy Files Archive Unlimited Strength Jurisdiction Policy Files for the JDK you are using
beforehand so that SAPinst can install them.
For more information, see Downloading the JCE Unlimited Strength Jurisdiction
Policy Files Archive [page 69].
SAP System ID and Database ID

SAP System ID <SAPSID> The SAP System ID <SAPSID> identifies the whole SAP system.
40/162 PUBLIC 2009-04-30

2 Planning
CAUTION
Choose your SAP system ID carefully. You cannot change the SAP system
ID after the installation.
Make sure that your SAP system ID:

éMè”˘þ Is unique throughout your organization. Do not use an existing
<SAPSID> when installing a new SAP system.
EXAMPLE
If you have already installed an ABAP system and you want to install
a new Java system on the same host, make sure that you enter a
<SAPSID> that is different from the <SAPSID> of the existing ABAP
system.
éMè”˘þ Consists of exactly three alphanumeric characters
éMè”˘þ Contains only uppercase letters
éMè”˘þ Has a letter for the first character
éMè”˘þ Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT
KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG
SID SQL SYS TMP TOP UID USE USR VAR
éMè”˘þ If you want to install the Java Add-In for an existing ABAP system or a dialog
instance, make sure that no gateway instance with the same SAP system
ID (SAPSID) exists in your SAP system landscape.
Database ID <DBSID> The <DBSID> identifies the database instance. SAPinst prompts you for the
<DBSID> when you are installing the database instance.
The <DBSID> can be the same as the <SAPSID>.
CAUTION
Choose your database ID carefully. Renaming is difficult and requires you
to reinstall the SAP system.
éMè”˘þ If you want to install a new database:

Make sure that your database ID:
éMè”˘‚ Is unique throughout your organization
éMè”˘‚ Consists of exactly three alphanumeric characters
éMè”˘‚ Contains only uppercase letters
éMè”˘‚ Has a letter for the first character
éMè”˘‚ Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM
INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET
SGA SHG SID SQL SYS TMP TOP UID USE USR VAR
éMè”˘þ If you want to use an existing database system:
Enter exactly the database ID of the existing database to which you want
to add the system.
System ID <SMDSID> of SAP SAPinst sets the system ID of SAP Solution Manager Diagnostics Agent,
Solution Manager Diagnostics <SMDSID>, to SMD by default.
Agent If SMD is already used, SAPinst assigns another default system ID. You can
overwrite the default system ID as required.
2009-04-30 PUBLIC 41/162

2 Planning
CAUTION
Choose the <SMDSID> carefully. Renaming is difficult and requires you to
reinstall the Diagnostics Agent.
Make sure that the <SMDSID>:

~á¦à"9 Either does not yet exist on the local installation host, or does already exist,
but exclusively contains some Diagnostics Agent installation
~á¦à"9 Consists of exactly three alphanumeric characters
~á¦à"9 Contains only uppercase letters
~á¦à"9 Has a letter for the first character
~á¦à"9 Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT
KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG
SID SQL SYS TMP TOP UID USE USR VAR
SAP System Profile Directory

/<sapmnt>/<SAPSID>/profile or / The installation retrieves the parameters entered earlier from the SAP
usr/sap/<SAPSID>/SYS/profile system profile directory.
SAPinst prompts you to enter the location of the profile directory
when the installation option that you execute is not the first one
belonging to your SAP system installation. See also the description of
the parameters SAP System ID and Database ID.
/usr/sap/<SAPSID>/SYS/profile is the soft link referring to /<sapmnt>/
<SAPSID>/profile.
NOTE
If you install a dialog instance in an existing SAP system, SAPinst
also prompts you for the profile directory of the existing SAP
system.
Unicode or Non-Unicode System

Unicode System End-to-End Root Cause Analysis requires an SAP Solution Manager 7.0 EHP1
with AS ABAP and AS Java in one SAP system. We recommend that you run
SAP Solution Manager on Unicode. Every new installation of SAP Solution
Manager 7.0 is Unicode. For customers that have upgraded from SAP Solution
Manager 3.1 and 3.2 and are not yet on Unicode, we recommend to perform a
Unicode conversion. If this is not possible, SAP supports End-to-End Root Cause
Analysis with an ABAP stack on non-Unicode as of SAP Solution Manager 7.0
SPS 13, until the customer has completed the Unicode conversion. For more
information, see http://service.sap.com/unicode.
SAP System Instances, Hosts, and Ports

Instance Number of the Technical identifier for internal processes. It consists of a two-digit number from 00
SAP system to 98.
42/162 PUBLIC 2009-04-30

2 Planning
The instance number must be unique on a host. That is, if more than one SAP instance
is running on the same host, these instances must be assigned different numbers.
To find out this number, look under the SAP directory /usr/sap/<SAPSID>/
DVEBMGS<nn> on the host of the central instance.
The value <nn> is the number assigned to the central instance.
CAUTION
If you are using NIM Service Handler (NIMSH), do not use 01 or 02 for the
instance number. SAPinst uses the instance number for the internal message
server port 39<instance number> (see row “Message Server Port” in this table
below). The NIM client daemon uses reserved ports 3901 and 3902.
Instance Number for the Technical identifier for internal processes for the Diagnostics Agent, consisting of a
Diagnostics Agent two-digit number from 00 to 98.
The instance number is set automatically to the next free and valid instance number
that has not yet been assigned to the SAP system.
The same restrictions apply as in “Instance Number of the SAP system” (see above).
Name of Instance Host Instance Host:
Host name of the specific instance.
To find out the host name, open a command prompt and enter hostname.
The host name must not exceed 12 characters. For more information about the
allowed host name length and characters, see SAP Note 611361.
Virtual Host Name You can use one or more virtual TCP/IP host names for SAP servers within an SAP
server landscape to conceal their physical network identities from each other. This
may be useful when moving SAP servers or complete server landscapes to other new
hardware within a short time frame without having to carry out a reinstallation or
complicated reconfiguration. You need to specify the virtual host name before you
start SAPinst.
For more information, see Prerequisites in Running SAPinst [page 83].
You also need to specify the virtual host name before you start SAPinst if you want
to install a high-availability (HA) system. For more information, see Performing a
High-Availability Installation [page 82].
&_ó˘g For more information about the use of virtual TCP/IP host names, see SAP
Note 962955.
&_ó˘g For more information about the allowed host name length and characters, see
SAP Note 611361.
Message Server Port CAUTION
The message server port number must be unique for the SAP system on all
hosts. If there are several message port numbers on one host, all must be unique.
Port number of the SAP Message Server:

If you do not specify a value, the default port number is used.
ABAP Message Server Port
There is an external message server port and an internal message server port.
The ABAP message server uses both the internal and the external message server
ports. The default profile contains the configuration for both message server ports.
The external message server port uses the parameter rdisp/msserv with default
value 36<nn>, where <nn> is the instance number of the ABAP message server
instance.
2009-04-30 PUBLIC 43/162

2 Planning
The internal message server port uses the parameter rdisp/msserv_internal with
default value 39<nn>, where <nn> is the instance number of the ABAP message
server instance.
Java Message Server Port
The Java message server only uses the internal message server port. The SCS instance
profile contains the configuration for the Java message server.
The parameter rdisp/msserv is set to 0, so that the external port is not open.
The internal message server port uses the parameter rdisp/msserv_internal with
default value 39<nn>, where <nn> is the instance number of the SCS message server
instance.
For more information about the parameters used for message server ports, see SAP
Note 821875.
Master Password
Master Password Common password for all users created during the installation:
Cl¸àł— Operating system users (for example <sapsid>adm)
CAUTION
If you did not create the operating system users manually before the installation,
SAPinst creates them with the common master password (see table Operating System
Users). In this case, make sure that the master password meets the requirements
of your operating system and of your database.
Cl¸àł— ABAP users SAP* and DDIC
CAUTION
SAPinst applies the master password to users SAP*and DDIC for SAP system clients
000 and 001 only, but not to users SAP*, DDIC, and EARLYWATCH in SAP system client
066.
Instead, SAPinst always assigns the following passwords to these users in client
066:
SAP*: 06071992
EARLYWATCH: support
See also Ensuring User Security [page 96].
Cl¸àł— Java users
(for example J2EE_ADMIN)
Cl¸àł— Database users
Cl¸àł— Secure Store key phrase
For more information, see table Key Phrase for Secure Store Settings.
Password policy
The master password:
Cl¸àł— Must be 8 to 9 characters long
Cl¸àł— Can contain the following characters: @, _, #, $, a-z, A-Z, 0-9
Cl¸àł— Must contain at least one letter (a-z, A-Z)
Cl¸àł— Must contain at least one digit (0-9), but must not begin with a digit
Cl¸àł— Must not contain \ (backslash) and " (double quote)
Depending on the installation option, additional restrictions might apply (for example, the
master password must not contain the name of a Java user created during the installation).
44/162 PUBLIC 2009-04-30

2 Planning
Operating System Users

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

Parameter Description
ABAP Client The production client of the ABAP system
CAUTION
You only need to enter this parameter if you install the Java Add-In for an
existing ABAP system.
DDIC Password The existing password of the DDIC user
CAUTION
You only need to enter this parameter if you install the Java Add-In for an
existing ABAP system.
Java Administrator User and This user has administrative permissions for user management.
Password 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.
For more information about supported UME data sources and change options,
Java Guest User and Password This user is used for anonymous access.
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 and This user is used for the communication between the ABAP system and the Java
Password system.
After the installation, it is available both in the ABAP and in the Java system
SAPinst sets the user name SAPJSF and the master password by default.
2009-04-30 PUBLIC 45/162

2 Planning
Parameter Description
SDM Password This user is used for the Software Deployment Manager (SDM).
SAPinst sets the master password by default.
Key Phrase for Secure Store Settings

Key Phrase for Secure Store This is a random word or phrase that is used to encrypt the secure store.
Settings The Java EE engine uses this phrase to generate the key that is used to encrypt
the data.
The uniqueness of the phrase you use contributes to the uniqueness of the
resulting key.
RECOMMENDATION
Use a long key phrase that cannot be guessed easily. Use both uppercase and
lowercase letters in the phrase and include special characters.
SAP Cryptographic Software

Path to SAPCRYPTO.SAR The SAP Cryptographic Library is required to enable Secure Sockets
Layer (SSL) encryption of HTTP connections. If you do not have
SAPCRYPTO.SAR available, you can download it from:
http://service.sap.com/swdc Download SAP Cryptographic
Software
After the installation has finished, you have to perform some post-
installation steps to configure AS ABAP for supporting SSL. For more
information, see Configuring AS ABAP to Support Secure Socket Layer (SSL) in
Performing Initial ABAP Configuration [page 104].
This software product is subject to export control regulations in
Germany as the country of origin and import regulations of your own
country. SAP may not yet have a corresponding export license for your
user or company. Contact the contract department in your local SAP
company. To download the SAP Cryptographic Software from the SAP
Service Marketplace, you need a customer user ID. Before any transfer
of these software products to persons, companies or other
organizations outside your company, in particular in the case of any
re-export of the software products, authorization is required from the
German export control authorities. This might also be required from
your responsible national export control authorities. This also applies
to transfers to affiliated companies. Corresponding laws and
regulations in the recipient country may also exist which restrict the
import or the use of these software products.
DNS Domain Name for SAP If you want to use HTTP-based URL frameworks such as Web Dynpro
System applications, you have to specify the DNS domain name for the SAP system.
46/162 PUBLIC 2009-04-30

2 Planning
The DNS Domain Name is used to calculate the Fully Qualified Domain Name
(FQDN), which is configured in profile parameter SAPLOCALHOSTFULL. FQDN is
the fully qualified domain name for an IP address. It consists of the host name
and the domain name:
<host name>.<domain name>
The DNS Domain Name is needed to define the URLs for the ABAP and Java
application servers. It is appended to the server name to calculate the FQDN.
For more information, see Configuring Fully Qualified Domain Names (FQDN) in
Performing Initial ABAP Configuration [page 104].
EXAMPLE
If your application server host is called kirk.wdf.sap.com, the DNS
Domain Name is wdf.sap.com.
System Landscape Directory (SLD) Destination

SLD Destination The System Landscape Directory (SLD) is designed for registering the systems
(along with the installed software) of your whole system landscape. The usual
case is to configure one SLD for your complete system landscape.
You can choose between the following options:
”⁄x®= Register in existing central SLD
Select this option to register the SAP system you are installing in an
existing SAP System Landscape Directory (SLD) by specifying the SLD
connection parameters below.
”⁄x®= Configure a local SLD
Select Configure a local SLD if you want to use the local SLD on the J2EE
engine of the SAP system that you are installing.
CAUTION
We strongly recommend that you install a local SLD on the SAP
Solution Manager system with connection and replication from
the productive SLD instances in your existing landscape. For more
information, see System Landscape Directory [page 33].
For more information, see Initial Technical Configuration for the System Landscape
Directory (SLD) [page 149].
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 ”⁄x®= If you want to install a local SLD, SAPinst creates this user during the
password installation.
”⁄x®= 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.
2009-04-30 PUBLIC 47/162

2 Planning
RECOMMENDATION
We recommend that you name this user SLDDSUSER
SLD ABAP API User and í^Œ˜fl/ If you want to install a local SLD, SAPinst creates this user during the
password installation.
í^Œ˜fl/ If you want to connect your system to an existing central SLD, you have
to enter the existing SLD Data Supplier User and password of the central
SLD during the installation.
RECOMMENDATION
We recommend that you name this user SLDAPIUSER
RFC User, Password The ABAP RFC user of the SLD
SLD Gateway Host The host on which the gateway instance of the SLD is running
SLD Gateway Instance Number The instance number of the gateway instance of the SLD
SAP System Client The client in which the ABAP RFC user exists
Prepare SAP System for NWDI Integration

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

User for basic authentication SAPinst sets the user name ADSUSER and the master password by default.
If required, you can choose another password according to your
requirements.
User for processing forms between SAPinst sets the user name ADSAGENT and the master password by default.
an ABAP and a Java environment If required, you can choose another password according to your
requirements.
48/162 PUBLIC 2009-04-30

2 Planning
2.10 High Availability: Planning the Switchover Cluster
Parameters Relevant for the File System

File system for the home /home/<username>
directory user
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>.
SAP MaxDB file systems û�Y®qe SAP MaxDB root directory, /sapdb
û�Y®qe For file system installations: locations of SAP data and log volumes
û�Y®qe For raw device installations: locations of raw devices for data and log
volumes
Parameters Relevant for the Database

Database ID Identifier for the database [page 40]
Database schema
Database operating system users SAP MaxDB software owner (default values):
and groups û�Y®qe User: sdb
û�Y®qe Group: sdba
SAP MaxDB database owner: sqd<dbsid>
û�YAT«úÅÖš‚~ó¾ž©˙Ó7ƒÒªü`W€UV‘5Ñ˙4hÆêøQzÉ%•Og˝¶¥[jÍæ%dpt

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.
2009-04-30 PUBLIC 49/162

2 Planning
You can protect software units that are not SPOFs against failure by making them redundant, which
means simply installing multiple instances. For example, you can add additional dialog instances (that
is, additional application servers). This complements the switchover solution and is an essential part
of building HA into your SAP system.
RECOMMENDATION
We recommend switchover clusters to ensure HA for your SAP system.
A switchover cluster consists of:

ã*‰X½ 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
ã*‰X½ Switchover software to detect failure in a node and switch the affected software unit to the standby
node, where it can continue operating
ã*‰X½ 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 to 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:
ã*‰X½ Check the information and the installation guides available at http://sdn.sap.com/irj/sdn/
ha.
ã*‰X½ The standalone replicated enqueue server is a major contribution to an HA installation and is
essential for a Java system. We strongly recommend you to use it for an ABAP system.
For more information about how to install the standalone replicated enqueue server, see:
SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP
Technology Client/Server Technology The SAP Lock Concept Standalone Enqueue Server Installing the
Standalone Enqueue Server
Features
The following figure shows the essential features of a switchover setup:
50/162 PUBLIC 2009-04-30

2 Planning
eÙ®‰%ß#é+Y|hŁê2p:ö©
NOTE
This figure and the figures in this section are only examples. Only the instances relevant to the
switchover are shown – for example, the central instance is not shown.
These graphics summarize the overall setup and do not show the exact constellation for an
installation based on one of the available technologies (ABAP, ABAP+Java, or Java).
You need to discuss your individual HA setup with your HA partner.
The following figure shows an example of a switchover cluster in more detail:
2009-04-30 PUBLIC 51/162

2 Planning
ëé½•áPv˙˜5k⁄`Ú>im£ ˇoU
Constraints
This documentation concentrates on the switchover solution for the central services instance. For
more information about how to protect the NFS File System and the database instance by using
switchover software or (for of the database) replicated database servers, contact your HA partner.
You need to make sure that your hardware is powerful enough to handle the increased workload after
a switchover. Some reduction in performance might be acceptable after an emergency. However, it is
not acceptable if the system comes to a standstill because it is overloaded after switchover.
ëé½…áWv˘˜`kı`Ù>óm² ao.ÍÈHËc‘=ô˙0ç±øe¨
52/162 PUBLIC 2009-04-30

3 Preparation
3.1 Preparation Checklist
3 Preparation
3.1 Preparation Checklist

You have to complete the following preparations, which are described in more detail in the linked
sections:
1. You make sure that the required operating system users and groups [page 53] are created.
2. You set up file systems or – if required – raw devices [page 55] and make sure that the required disk space
is available for the directories to be created during the installation.
3. If required, you set up virtual host names [page 66].
4. If you want to install a high-availability system, you perform switchover preparations [page 66].
5. If you want to share the transport directory trans from another system, export [page 67] this
directory to your installation hosts.
6. You install the SAP frontend software [page 68] on the desktop of the end user.
7. You install the Java Development Kit [page 68].
8. You download the JCE policy zip file [page 69].
9. You make sure that the required installation media [page 70] are available on each host.
10. Dialog instance only: If you upgraded your SAP Solution Manager System from an earlier source
release to a target release lower than SAP Solution Manager 7.0, then installed EHP 1 with the EHP
Installer, and now want to install a dialog instance, you have to update instance profiles of the existing
system [page 128].
11. You can continue with Installation [page 73].
3.2 Creating Operating System Users and Groups

During the installation, SAPinst checks all required accounts (users, groups) and services on the local
machine. SAPinst checks whether the required users and groups already exist. If not, it creates new
users and groups as necessary.
If you do not want SAPinst to create operating systems users, groups, and services automatically, you
can optionally create them before the installation. This might be the case if you use central user
management such as Network Information System (NIS).
SAPinst checks if the required services are available on the host and creates them if necessary. See the
log messages about the service entries and adapt the network-wide (NIS) entries accordingly.
SAPinst checks the NIS users, groups, and services using NIS commands. However, SAPinst does not
change NIS configurations.
2009-04-30 PUBLIC 53/162

3 Preparation
3.2 Creating Operating System Users and Groups
¼P0Àœ0çÌ{Ñ¸<4° ½í1<×èXûAÑÜ$³¥‰C:ÌþÜ{E‚ÏùA‚fl−4ñswòFvX
RECOMMENDATION
For a distributed or a high-availability system, we recommend that you distribute account

information (operating system users and groups) over the network, for example by using Network
Information Service (NIS).
¼P:Àœ0ïÌ"Ñ÷<$°R½¡1˛×ÍXûA�Ü˚³:Ö‰;:�þ={ˇ
If you want to use global accounts that are configured on a separate host, you can do this in one of the
following ways:
¼PßåR You start SAPinst and choose Software Life-Cycle Options Additional Preparations Operating System Users
and Groups . For more information, see Running SAPinst [page 83].
¼PßåR You create operating system users and groups manually.
If you need information about how to do this, see Creating AIX Groups and Users [page 126]
Operating System Users and Groups
SAPinst chooses available operating system user IDs and group IDs unless you are installing an additional
application server instance. On an additional application server instance you have to enter the same
IDs as on the host of the primary application server instance.
CAUTION
¼PßåR All users must have identical environment settings. If you change the environment delivered
by SAP, such as variables, paths, and so on, we do not assume responsibility.
¼PßåR Do not delete any shell initialization scripts in the home directory of the OS users. This applies
even if you do not intend to use the shells that these scripts are for.
¼PßåR If you create the sdb user manually, make sure that you lock it for the installation. SAPinst
normally locks this user after it has been created.
¼PßåR The user ID (UID) and group ID (GID) of each operating system user and group must be
identical for all servers belonging to the same SAP system.
This does not mean that all users and groups have to be installed on all SAP servers.
¼PßåR If you are installing an SAP system where the instances are to run on several hosts (distributed
or high-availability system), make sure that the group ID of group sapinst is always different
from the group ID of any other group (for example, of group sapsys) used during the
installation.
Example:
You are installing a dialog instance in an existing SAP system.
You must make sure that the group ID of group sapinst created on the host of the dialog
instance is different from the group ID of any other group (for example, of group sapsys) on
the central instance host of the existing SAP system.
54/162 PUBLIC 2009-04-30

3 Preparation
3.3 Setting Up File Systems and Raw Devices
Users and Groups

User Primary Group Additional Group Description
root None sapinst Superuser of the UNIX
operating system
<sapsid>adm sapsys sapinst SAP system administrator
<smdsid>adm sapsys sapinst Diagnostics Agent
administrator
sqd<dbsid> sapsys sapinst, sdba Owner of database
instance <DBSID>
sdb sdba Database software owner
CAUTION
If these operating system users already exist, make sure that they are assigned to group sapinst.
CAUTION
If you install a distributed system and you use local operating system user accounts instead of
central user management (for example, NIS), user <sapsid>adm, sapadm, and the database
operating system user must have the same password on all hosts.
Groups and Members

Groups Members
sapsys <sapsid>adm, <smdsid>adm, sqd<dbsid>
sapinst root, <sapsid>adm, <smdsid>adm, sqd<dbsid>
sdba sqd<dbsid>, sdb

The following sections describe the directories that are required for the instances of an SAP system,
how to set up file systems and – if required – raw devices on operating system level:
iªÈ˜ü` SAP Directories [page 55]
iªÈ˜ü` SAP MaxDB Directories [page 62]
iªÈ˜ü` Setting Up File Systems for High-Availability [page 62]
iªÈ˜ü` Configuring Network File System for High Availability [page 64]
More Information
If you need information about how to set up file systems and raw devices, see Setting Up File Systems and
Raw Devices for AIX [page 127].
3.3.1 SAP Directories

Depending on the installation option you have chosen, SAPinst automatically creates the directories
listed in the following figures and tables.
2009-04-30 PUBLIC 55/162

3 Preparation
Before running the installation, you have to set up the required file systems manually. In addition, you
have to make sure that the required disk space for the directories to be installed is available on the
relevant hard disks.
The figure below assumes that you have set up one file system for the SAP system mount directory
<sapmnt> and one file system for the /usr/sap directory. However, you have to decide for which
directories you want to set up separate file systems. If you do not set up any file system on your
installation host, SAPinst creates all directories in the root directory /.
SAPinst prompts you only for the <sapmnt> directory during the installation. For more information,
see also table Parameters Relevant for the File System in Basic SAP System Parameters [page 40].
\¸Ær}…ÉölŁRóòSÜ†d+¨S$V×Ü±‹¢ß•›>Î+ÊM‰łgýŽCø&!²Ÿ%^Ý‘{åÀ
NOTE
For more information about how to set up your file systems if you are performing an HA
installation, see High Availability: Setting Up File Systems [page 62].
\¸Æx}…ÉþlÌ˛ãòÜÍd
¨7S$VŽÜ‰‹žßó›FÎJÊ¬‰Ç
CAUTION
SAPinst uses sapcpe to replicate the kernel automatically from /usr/sap/<SAPSID>/SYS/exe/

run/DIR_CT_RUN to /usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP system
instance.
The following entry in the start profile is responsible for this:
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF),
where $(_PF) points to the instance profile.
Do not delete DIR_CT_RUN from the instance profile. Otherwise, you cannot restart the system
after patches have been applied.
For more information, see Applying the Latest Kernel and Support Packages [page 103].
Standard SAP Directories for an ABAP + Java System
Both the ABAP part and the Java part of every new installation of an ABAP+Java system are Unicode.
We still support non-Unicode for ABAP but only if you perform the system copy for a non-Unicode
system that has been upgraded to SAP NetWeaver 7.0 SR3.
56/162 PUBLIC 2009-04-30

3 Preparation
¿|B%tP
−3øb‘™T»3^0Z0·¼½SAP Directories for an ABAP + Java System (Unicode)
¿|B%tP
−3øb‘™T»3^0Y0·¼½SAP Directories for an ABAP + Java System (ABAP Non-Unicode, Java Unicode)
The instance name (instance ID) of the ABAP+Java central instance is DVEBMGS<Instance_Number>, the
instance name of an ABAP+Java dialog instance is D<Instance_Number>, and the instance name of the
Java central services instance is SCS<No>.
2009-04-30 PUBLIC 57/162

3 Preparation
�—²¿£|)Àž€èE•ˇf„¡ó:L§fi®y=⁄QN-cÍjÜf4®ÁPˇE¼*ÁQç¸—Fv·Ñkôò
If you are performing an HA installation of your ABAP+Java system, there is also an ABAP central
services instance called ASCS<Instance_Number>.
�—²µ£|)Èžùè
•ˇ=À¡Ò:i§fi®7=½Qr-ÍÜ4OÁ
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 Directories for the Diagnostics Agent
The installation creates the following SAP directories for the Diagnostics Agent.
�—²¶£{)Ëž¬è•ˇ§Ñ¡©:§fiSAP Directories for the Diagnostics Agent
SAPinst extracts the Diagnostics Agent to the directory /usr/sap/SMD/J<instance_number>/

SMDAgent.
EXAMPLE
/usr/sap/SMD/J98/SMDAgent
SAP Directories in Detail

NOTE
The listed space requirements are initial SAP requirements.
58/162 PUBLIC 2009-04-30

3 Preparation
Depending on your operating system, you might also have to add space for administrative
purposes.
The following directories are global, that is, they are accessed by all hosts in the SAP system.
SAP Directories
Directory Description Space Required
<sapmnt>/<SAPSID> Software and data for one SAP system 4.0 GB
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:
:eD−~ exe
This directory contains executable kernel programs.
If you install an SAP system with distributed instances, you
have to share this directory for all hosts with the same
operating system. For more information, see the Prerequisites in
Running SAPinst [page 83].
NOTE
SAP system ABAP (Non-Unicode) + Java only: exe
contains a folder uc with a platform-specific subfolder:
<sapmnt>/<SAPSID>/exe/uc/<platform>
:eD−~ global
This directory contains log files.
have to share this directory for all hosts. For more information,
see the Prerequisites in Running SAPinst [page 83].
:eD−~ profile
This directory contains the start and operations profiles of all
instances.
have to share this directory for all hosts. For more information,
see the Prerequisites in Running SAPinst [page 83].
/usr/sap/<SAPSID> Instance-specific data, symbolic links to the data for one 6.0 GB
system
This directory contains files for the operation of a local instance.
There is a subdirectory <INSTANCE_NAME> for each instance installed
on the local instance host. The directory SYS contains only soft links
to appropriate directories in /<sapmnt>/<SAPSID>/ for storing data
used by several instances.
NOTE
SAPinst creates the subfolder /usr/sap/<SAPSID>/
<INSTANCE_NAME>/SDM only for the central instance of ABAP
+Java or Java systems.
For more information about SDM, see Checking the Java
Documentation [page 147].
2009-04-30 PUBLIC 59/162

3 Preparation
Directory Description Space Required

There are subdirectories of /usr/sap/<SAPSID>/SYS with symbolic
links to subdirectories of /<sapmnt>/<SAPSID>:
ã›¾,„Ï /usr/sap/<SAPSID>/SYS/profile is linked to /<sapmnt>/
<SAPSID>/profile
ã›¾,„Ï /usr/sap/<SAPSID>/SYS/global is linked to /<sapmnt>/
<SAPSID>/global
ã›¾,„Ï /usr/sap/<SAPSID>/SYS/exe/run is linked to /usr/sap/
<SAPSID>/SYS/exe/dbg, which is linked to /<sapmnt>/
<SAPSID>/exe
NOTE
SAP system ABAP (Non-Unicode) + Java only: /usr/
sap/<SAPSID>/SYS/exe/run is linked to <sapmnt>/
<SAPSID>/exe/uc
SAPinst sets up these directory structures during the installation.
Executables located in/usr/sap/<SAPSID>/SYS/exe/run are
replicated by sapcpe to the exe directory of instances of the type
<INSTANCE_NAME>, 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
Make sure that sufficient space is available in directory /usr/
sap/<SAPSID>/<INSTANCE_NAME>, since this stores SAP traces
for the instance. Changes in SAP system profiles can also affect
the disk space.
/usr/sap/trans Global transport directory for all SAP systems 2.0 GB
For more information about exporting and mounting the global
transport directory, see Exporting and Mounting the Global Transport
Directory [page 67]
The global transport directory is used by the Change and Transport
System (CTS). The CTS helps you to organize development
projects in the ABAP Workbench and in Customizing, and then
transport the changes between the SAP systems in your system
landscape. For more information, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including
Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver
by Key Capability Solution Life Cycle Management by Key Capability
Software Life Cycle Management Software Logistics Change and Transport
System
For more information about the directories required for the database instance, see SAP MaxDB
Directories [page 62].
60/162 PUBLIC 2009-04-30

3 Preparation
SAP Directories for the Diagnostics Agent in Detail

NOTE
The listed space requirements are initial SAP requirements.

Depending on your operating system, you might also have to add space for administrative
purposes.
SAP Directories for the Diagnostics Agent

Space
Directory Description Required
/usr/sap/<SMDSID>/ Instance-specific data of the Diagnostics Agent 500 MB
J<instance_number> Contains the following subdirectories:
ı•Im!Ú sapinst
Contains log files of the installation
ı•Im!Ú SMD Agent
Contains the Diagnostics Agent software and
properties files.
ı•Im!Ú script
Contains the following local scripts:
ı•Im!µ smdstart.sh
This script is used to start the local Diagnostics
Agent.
ı•Im!µ smdstop.sh
This script is used to stop the local Diagnostics
Agent.
ı•Im!µ smdadmin.sh
This script is used to manage the local
Diagnostics Agent.
ı•Im!Ú work
This is the work directory of the Diagnostics Agent
/usr/sap/<SMDSID>/SYS/profile Contains the profiles of the Diagnostics Agent instance
/usr/sap/<SMDSID>/exe Contains the following global scripts:
ı•Im!Ú smdstart.sh
This script is used to start one or more Diagnostics
Agents available in the system landscape.
ı•Im!Ú smdstop.sh
This script is used to stop one or more Diagnostics
Agents available in the system landscape.
ı•Im!Ú smdadmin.sh
This script is used to manage one or more
Diagnostics Agents available in the system
landscape.
More Information
For more information about sapcpe, see http://help.sap.com/nw70 SAP NetWeaver 7.0 Library
(including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application
Platform by Key Capability ABAP Technology Client/Server Technology Local Executables on SAP Instances
Functions of the Automatic Synchronization Program sapcpe
2009-04-30 PUBLIC 61/162

3 Preparation
3.3.2 SAP MaxDB Directories

These are the directories for the SAP MaxDB database:
SAP MaxDB Directories
Directory Name Description Space Required
/sapdb/<DBSID>/sapdata SAP MaxDB See the table Hardware Requirements in Requirements for the
data Database Instance [page 28].
NOTE
If the database data is installed on raw devices, you do
not need to set up /<sapdata>.
/sapdb/<DBSID>/sapdblog SAP MaxDB See the table Hardware Requirements in Requirements for the
redologs Database Instance [page 28].
NOTE
If the database data is installed on raw devices, you do
not need to set up /sapdblog.
/sapdb/<DBSID>/sapdb SAP MaxDB See the table Hardware Requirements in Requirements for the
software Database Instance [page 28].
Y“¬Ì-Ê®ìº³5�'µ[ «¸õ£[×ñ[¿S@ÿÝ:ªb·åm(¡• ,¼Àb©ºq™ºÛ½9e+
3.3.3 Setting Up File Systems for a High-Availability System

When you prepare a high-availability (HA) installation, you need to set up your file systems as described
here. For more information, consult your HA partner.
CAUTION
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
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 49].
Procedure
1. Create the file systems or raw partitions for the central services (SCS) instance on shared disks. For
more information, see Setting Up File Systems and Raw Devices [page 55].
NOTE
The directories /<sapmnt>/<SAPSID> and /usr/sap/trans have to be mounted from a

Network File System (NFS), whereas /usr/sap/<SAPSID> is a directory of the AS instance that
is always mounted on the instance (not with NFS).
62/162 PUBLIC 2009-04-30

3 Preparation
Therefore, if the central instance host is not the NFS server host, you might have to mount
at least the first two file systems on different physical disks from the third file system.
CAUTION
Make sure that the mount points under /<sapmnt>/<SAPSID>/ are permanent. Otherwise
automatic start of the instance services does not work when you reboot the system.
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 file system for the /usr/sap/<SAPSID>
directory.
The /usr/sap/<SAPSID> directory contains two subdirectories:
»û¿I|! SYS contains links to the central directory /<sapmnt>/<SAPSID>
»û¿I|! <INSTTYPE><NR> contains data for the local AS instance
The name <INSTTYPE><NR> is defined by the type of services and the application server number,
for example DVEBMSG00.
Only the directory <INSTTYPE><NR> needs to be migrated with the AS instance during the
switchover. Since the SYS subdirectory contains only links that do not require any space, it can be
created locally on each cluster node. Therefore, instead of /usr/sap/<SAPSID>, create a file system
for /usr/sap/<SAPSID>/<INSTTYPE><NR> with the usual <> substitutions. The file name for the
central instance is usually DVEBMGS00. This avoids mount conflicts when switching over to a node
on which an AS instance is already running. The DVEBMGS00 directory can join the tree /usr/sap/
<SAPSID> instead of mounting on top of it.
NOTE
This approach becomes increasingly important when you want to cluster central services
while other instances run on the cluster hosts outside the control of the switchover software,
so as to use the resources efficiently. You must use this approach for integrated installations
of the AS with ABAP and Java stacks.
3. You assign the local file systems to mount points.
4. You assign the shared file systems to mount points in appropriate failover groups.
EXAMPLE
The graphic below shows an example of the file systems and disks in an HA setup
Note that this is only an example. For more information on a setup that meets your needs, consult
your HA partner.
2009-04-30 PUBLIC 63/162

3 Preparation
¿Þ˙y±Ÿ´{º´ ËÓx3ïš)
¿Þ˘y¶Ÿ´.º©
ËIx"ïá)[Lö�1ÀÛ%•Ì›Ã�m� r
¿Þy¶Ÿˆ´wºæˆËxnïÀ)~Lö��Àá%¼ÌúÃ}��à .+ìþÎ.ð=Õmx3ªXêt÷
3.3.4 Configuring Network File System for a High-Availability

System
If required, you configure Network File System (NFS), which is a system-wide Single Point-of-Failure
(SPOF), for a high-availability (HA) installation with switchover software. For more information,
consult your HA partner.
We regard NFS as an extension to the operating system. The switchover product protects NFS and
makes it transparently available to the SAP system in switchover situations.
You need to decide:
¿Þý\x How to protect NFS
¿Þý\x Which switchover cluster nodes NFS is to run on
The NFS configuration might depend on your database system. The directories need to be available for
the SAP system before and after a switchover.
CAUTION
Make sure that the mount points under /<sapmnt>/<SAPSID>/ are permanent. Otherwise
automatic start of the instance services does not work when you reboot the system.
64/162 PUBLIC 2009-04-30

3 Preparation
Procedure
1. Check the NFS directories, several of which need to be shared between all instances of a system.
These directories are:
ÓÖ'±› /<sapmnt>/<SAPSID>/profile
Contains the different profiles to simplify maintenance
ÓÖ'±› /<sapmnt>/<SAPSID>/global
Contains log files of batch jobs and central SysLog
ÓÖ'±› /usr/sap/trans
Contains data and log files for objects transported between different SAP Web AS systems (for
example, development – integration). This transport directory ought to be accessible by at
least one AS instance of each system, but preferably by all.
ÓÖ'±› /<sapmnt>/<SAPSID>/exe
Contains the kernel executables. 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.
The requirements of your database system might dictate how NFS has to be set up. If required, you
can configure the NFS server on the cluster node of the CI or the DB.
In both cases the NFS clients use the virtual IP address to mount NFS. If the second node is used as
an additional SAP instance during normal operation (for example, as a dialog instance), it also
needs to mount the directories listed above from the primary node.
When exporting the directories with their original names, you might encounter the problem of a
“busy NFS mount” on the standby node. You can use the following workaround to solve this
problem:
1. On the primary server, mount the disks containing the directories:
/export/usr/sap/trans
/export/<sapmnt>/<SAPSID>
2. The primary server creates soft links to the directories with the original SAP names:
/usr/sap/trans —> /export/usr/sap/trans
/<sapmnt>/<SAPSID> —> /export/<sapmnt>/<SAPSID>
Alternatively the primary server can also mount the directories:
/export/usr/sap/trans —> /usr/sap/trans
/export/<sapmnt>/SID —> /<sapmnt>/<SAPSID>
3. The primary server exports:
4. The standby NFS mounts:
from virt.IP:/export/usr/sap/trans to /usr/sap/trans
from virt.IP:/export/<sapmnt>/<SAPSID> to /<sapmnt>/<SAPSID>
2009-04-30 PUBLIC 65/162

3 Preparation
3.4 Using Virtual Host Names
If the primary node goes down and a switchover occurs, the following happens:
e-y‘h/ These directories on the standby node become busy:
/usr/sap/trans
/<sapmnt>/<SAPSID>
e-y‘h/ The standby node mounts disks to:

e-y‘h/ The standby node configures the virtual IP address virt.IP

e-y‘h/ The standby node exports:
e-y‘h/ These directories on the standby node are accessible again:

/usr/sap/trans
/<sapmnt>/<SAPSID>
e-yjMáMâL%Èðˆ´;&£Ë»ÀÀ†X YMäMéb^Öæ#Ÿñ
3.4 Using Virtual Host Names

You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to
conceal their physical network identities from each other. This can be useful when quickly moving
SAP servers or complete server landscapes to alternative hardware without having to reinstall or
reconfigure.
e-y`MáMê%XÈàˆï;M&‡ËžÀÀ† cMØMréˆ^·æÂŸ�¹˚¥ØY\'¿Œ¤%€^‰•d¼³Ú„ÜTfld¿£˘ ‡ƒŽh;÷
Virtual host names are also required for a high-availability installation. For more information, see
Performing Switchover Preparations for High Availability [page 66].
e-yjMáMâL%Èðˆ´;&£Ë»ÀÀ†X YMäMéb^Öæ¸ŸÅ¹w¥�Y:'„ŒÓ%Æ^ã•¼RÚÐ
Prerequisites
Make sure that the virtual host name can be correctly resolved in your Domain Name System (DNS)
setup.
Procedure
Proceed as described in SAP Note 962955.
e-y`MáMê%XÈàˆï;M&‡ËžÀÀ† cMØMréˆ^·æÂŸ�¹˚¥ØY\'¿Œ¤%€^•P
3.5 Performing Switchover Preparations for High Availability

If you want to use a virtual host name, you have to set the SAPinst propertySAPINST_USE_HOSTNAME to
specify the required virtual host name before you start SAPinst. For more information, see Running
SAPinst [page 83].
66/162 PUBLIC 2009-04-30

3 Preparation
3.6 Exporting and Mounting the Global Transport Directory
Procedure
Assign the virtual IP addresses and host names for the SCS and ASCS instances, and (if required) NFS
to appropriate failover groups.
NOTE
For more information on virtual addresses and virtual host names and how to assign resources
to failover groups, ask your HA partner.
To enable a failover in a double-stack system (ABAP+Java), both central services instances – SCS
and ASCS – have to use the same virtual host name.
¡ÍRÅ ˜·öÏIÄ¦Îç]%˚ÃW§kłhñ#-™Jœ}ò×UÆD„'ûöA
3.6 Exporting and Mounting the Global Transport Directory

CAUTION
In your SAP system landscape, a global transport directory for all SAP systems is required.
¡ÍR Ñ 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.
¡ÍR Ñ If this global transport directory does not exist, proceed as follows:
¡ÍR ¾ Create the transport directory (either on the central instance host or on a file server).
¡ÍR ¾ Export it on the global transport directory host.
¡ÍR ¾ If you did not create the transport directory on your SAP instance installation host, mount it
there.
Procedure
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.
2009-04-30 PUBLIC 67/162

3 Preparation
3.7 Installing the Front-End Software
More Information
Mounting Directories via NFS for AIX [page 130]
3.7 Installing the Front-End Software

CAUTION
For the installation, make sure that the front-end software is installed on at least one computer in your
system environment.
With installation software NW SAPSetup for the SAP Front-End, 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.
We recommend that you install SAP Front-End release 7.10 or higher.
For more information about installing the front-end software, see the documentation SAP Front End
Installation Guide - <Current Release> at:
http://service.sap.com/installNW70 Installation - Clients
3.8 Installing the Java Development Kit

You need to prepare the system for the Java EE Engine by installing the Java Development Kit (JDK).
The Java Engine requires a Java Development Kit (Java™ 2 SDK, Standard Edition = JDK) on every host
where the Java Engine is to be installed.
NOTE
If required, you can perform a remote installation using a standalone SAPinst GUI on a separate
Windows or UNIX host. This lets you perform the installation on a remote host, controlling it
with the SAPinst GUI from a local host. If you want to perform a remote installation, see Performing
a Remote Installation with SAPinst [page 135]. In this case, you need at least a JRE on the local host to
start the SAPinst GUI there.
Procedure
1. Check the JDK versions that are released for SAP systems in the Product Availability Matrix (PAM):
1. Go to http://service.sap.com/pam.
2. Choose Start PAM with navigation by category.
3. Choose tabstrip JSE Platforms.
NOTE
For more information about how to download it, see the relevant SAP Note for your operating
system, which is referenced near the beginning of SAP Note 723909.
68/162 PUBLIC 2009-04-30

3 Preparation
3.9 Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive
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:
„òB‡—¾ If the JDK is not already installed, you need to download and install it.
„òB‡—¾ If the JDK is already installed
Check the installed version of the JDK by entering the following command:
java -version
NOTE
SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime

environment.
If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME.
3.9 Downloading the JCE Unlimited Strength Jurisdiction

Policy Files Archive
As of SAP NetWeaver 7.0 strong encryption is mandatory for the Java EE Engine and for all usage types
that are deployed on it. You need to obtain the Java(TM) Cryptography Extension (JCE) Unlimited
Strength Jurisdiction Policy Files for the JDK you are using beforehand so that SAPinst can
install them. The JCE Unlimited Strength Jurisdiction Policy Files archive (JCE policy zip file)
is specific for each Java VM provider and is available as a free download from the corresponding vendor's
site.
Prerequisites
„òB‡—¾ You have installed the Java Development Kit (JDK) [page 68] for your platform.
„òB‡—¾ Make sure there is not an older version of the JCE policy zip file for your platform on the installation
host.
CAUTION
If there is an old JCE policy zip file, the Prerequisite Checker does not recognize this fact. For
this reason, SAPinst throws a java.lang.SecurityException during the Create Secure
Store step stating the jurisdiction policy files are not signed by trusted signers.
Procedure
1. Download the JCE policy zip file for your platform at http://www6.software.ibm.com/dl/
jcesdk/jcesdk-p.
NOTE
You must not unzip the archive.

2. SAPinst installs the JCE policy files during the installation process.
3. Copy the JCE policy files to directory /usr/java14_64/jre/lib/security.
2009-04-30 PUBLIC 69/162

3 Preparation
3.10 Preparing the Installation DVDs

This section describes how to prepare the installation DVDs, which are available as follows:
ÙKµ±å6 You obtain the installation DVDs as part of the installation package.
ÙKµ±å6 You can also download the installation DVDs from SAP Service Marketplace.
Procedure
1. Identify the required DVDs for your installation as listed below.
Keep them separate from the remaining DVDs as this helps you to avoid mixing up DVDs during
the installation.
CAUTION
The media names listed below are abbreviated.

You can find the full names of all media shipped with SAP Solution Manager in the document
Media List for SAP Solution Manager 7.0 EHP 1 at:
http://service.sap.com/instguides SAP Components SAP Solution Manager Release
7.0
SAP Instance Installation Required DVDs
Central services instance, central instance, ÙKµ±å6 SAP Solution Manager Installation Master DVD
dialog instance ÙKµ±å6 SAP Kernel 7.00 SR3 <OS> DVD
ÙKµ±å6 SAP Solution Manager Java DVD
ÙKµ±å6 RDBMS DVD
Database instance ÙKµ±å6 SAP Solution Manager Installation Master DVD
ÙKµ±å6 SAP Kernel 7.00 SR3 <OS> DVD
ÙKµ±å6 SAP Solution Manager Installation Export 1 DVD
ÙKµ±å6 SAP Solution Manager Installation Export 2 DVD
ÙKµ±å6 RDBMS DVD
The following table shows the required DVDs for the installation of the Java Add-In for an existing
ABAP System:
SAP Instance Installation Required DVD
Central instance, central services instance, ÙKµ±å6 SAP Solution Manager Installation Master DVD
dialog instance ÙKµ±å6 SAP Kernel 7.00 SR3 <OS> DVD
Database schema ÙKµ±å6 SAP Solution Manager Installation Master DVD
ÙKµ±å6 SAP Kernel 7.00 SR3 <OS> DVD
2. Make the required installation media available on each installation host.
If you need information about how to mount DVDs on AIX, see Mounting a CD / DVD for AIX [page
130].
70/162 PUBLIC 2009-04-30

3 Preparation
NOTE
Depending on your installation type, one or more instances can reside on the same host. You
need to keep this in mind when you make the required installation media available on each
installation host.
For a central system, you need to make all required installation media available on the single
installation host.
Use one of the following methods to make DVDs available:
LPÁ£(` Before the installation, copy DVDs manually to local hard disks.
LPÁ£(` During the installation, use the SAPinst Media Browser dialog and copy the entire DVDs to
the path you entered in the Copy Package To column.
CAUTION
LPÁ£(` Mount the DVDs locally. We do not recommend you to use Network File System (NFS),
because reading from DVDs mounted with NFS might fail.
LPÁ£(` If you copy the DVDs to disk, make sure that the paths to the destination location of the
copied DVDs do not contain any blanks.
LPÁ£(` If you perform a local installation and there is only one DVD drive available on your
installation host, you must copy at least the Installation Master DVD to the local file
system.
Downloading Installation DVDs from SAP Service Marketplace
You normally obtain the installation DVDs as part of the installation package from SAP.
However, you can also download installation DVDs from:
http://service.sap.com/swdc Download Installations and Upgrades Entry by Application Group <SAP
solution> <SAP product> <SAP release> Installation and Upgrade <operating system> <database>
NOTE
If you download installation DVDs, note that DVDs might be split into several files. In this case,
you have to reassemble the required files after the download.
CAUTION
To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which
you can find at http://service.sap.com/swdc. You need at least SAPCAR 700 or SAPCAR 640
with patch level 4 or higher because older versions of SAPCAR can no longer unpack current SAR
files. For more information, see SAP Note 212876.
1. 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:
LPÁ£(` Material number
2009-04-30 PUBLIC 71/162

3 Preparation
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
...
Ð€<S>q 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.
NOTE
SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always accept
with Yes.
72/162 PUBLIC 2009-04-30

4 Installation
4.1 Installation Checklist
4 Installation

This section includes the installation steps that you have to perform for the:
ÜßflÊ� Central system
ÜßflÊ� Distributed system
ÜßflÊ� High-availability system
ÜßflÊ� Dialog instance
Detailed information about the steps is available in the appropriate section. For more information about
the various installation options, see Installation Options Covered by This Guide [page 11].
Central System
1. You install the SAP system with SAPinst [page 83].

2. You continue with Post-Installation [page 93].
Distributed System
1. If you want to share the transport directory trans from another system, you have to mount [page
67] it from this system. Otherwise, we recommend that you share the trans directory that is created
during the installation of the central instance (/usr/sap/trans).
2. On the SAP global host, proceed as follows:
1. You run SAPinst [page 83] to install the central services instance (SCS).
2. You export the global directories [page 81] to the database instance host, to the central instance
host, and – if required – to the hosts where you want to install one or more dialog instances.
3. On the database instance host, proceed as follows:
1. You mount the exported global directories [page 81] from the SAP global host (<sapmnt>/<SAPSID>/
exe, <sapmnt>/<SAPSID>/profile, <sapmnt>/<SAPSID>/global) and SAP transport host (/
usr/sap/trans).
2. You run SAPinst [page 83] to install the database instance.
4. On the central instance host, proceed as follows:
NOTE
You can use the SAP transport host or the SAP global host as your central instance host.
usr/sap/trans).
2009-04-30 PUBLIC 73/162

4 Installation
2. You run SAPinst [page 83] to install the central instance.

5. If required, you install one or more dialog instances on the respective hosts as described later in
this section.
usr/sap/trans).
2. You run SAPinst [page 83] to install the dialog instance.
Graphical Overview
The following figure shows how you install the various instances in a distributed system:
˘‹u6Ä³fÌËqY«łÏŒłò°™lƒDistribution of Instances in an ABAP+Java System
˘‹u6Ã³mÌÇq«‹ŒÆòì™2ƒËlàÒóÕRÌ;;ŸŸoˇŒÓ§ì²‹yÿ€wÁ
High-Availability System
This section describes how you install a high-availability (HA) system consisting of two nodes (host
A and host B). For more information, consult your HA partner.
This procedure describes the steps that are required for a hardware cluster consisting of two nodes
(host A and host B):
1. You need to make sure that your system meets the hardware and software requirements [page 22].
74/162 PUBLIC 2009-04-30

4 Installation
2. If you want to share the transport directory trans from another system, you have to mount [page
67] it from this system. Otherwise, we recommend that you share the trans directory that is created
during the installation of the central instance (see below).
3. You set up the switchover cluster infrastructure as follows:
1. You run SAPinst [page 83] to install the ABAP central services instance (ASCS) using the virtual
host name [page 66] on the primary cluster node, host A.
2. You run SAPinst [page 83] to install the central services instance (SCS) using the virtual host
name [page 66] on the primary cluster node, host A.
3. You export global directories [page 81] in <sapmnt>/<SAPSID> to the database host and to the
central instance host.
4. You prepare the standby cluster node, host B, and make sure that it has all the necessary file
systems [page 62], mount points, and (if required) Network File System (NFS).
5. You set up the user environment on the standby node, host B as follows:
1. You make sure that you use the same user and group IDs as on the primary node.
2. You create the home directories of users and copy all files from the home directory of the
primary node.
For more information about the required operating system users and groups, see Creating
Operating System Users [page 53].
6. You configure the switchover software and test that switchover functions correctly to all
standby nodes in the cluster.
7. You repeat the following steps until you have finished installing the enqueue replication server
(ERS) on all nodes in the cluster:
1. You perform the switchover to a node where you want to install the ERS.
2. You install the ERS as described in:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1)
English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key
Capability ABAP Technology Client/Server Technology The SAP Lock Concept Standalone
Enqueue Server Installing the Standalone Enqueue Server
4. On the database instance host, proceed as follows:
RECOMMENDATION
We recommend that the database instance is part of the hardware cluster or of any other
proprietary high-availability solution for the database.
1. You prepare the database instance host and make sure that it has all the necessary file systems
[page 62], mount points, and (if required) Network File System (NFS).
2. You run SAPinst [page 83] to install the database instance.
5. On the central instance host, proceed as follows:
2009-04-30 PUBLIC 75/162

4 Installation
NOTE
In a high-availability installation, the central instance does not need to be part of the cluster
because it is no longer a single point of failure (SPOF). The SPOF is now in the central services
instances (SCS and ASCS), which are protected by the cluster.
1. You prepare the central instance host and make sure that it has all the necessary file systems
[page 62], mount points, and (if required) Network File System (NFS).
2. You run SAPinst [page 83] to install the central instance.
3. If you want to use the shared transport directory trans from another system, you also mount
[page 67] this directory (see above).
6. We recommend that you install dialog instances with SAPinst to create redundancy. The
application server instances are not a SPOF. Therefore, you do not need to include these instances
in the cluster.
1. You mount the global directories [page 81] in <sapmnt>/<SAPSID>.
3. If you want to use the shared transport directory trans from another system, you also mount
[page 67] this directory (see above).
Graphical Overview
The following figure provides an overview of how you install the various instances in a high-availability
installation:
ý˜Ó…ÚVï'ÊÅsÁWwÝ½a8@¹…ŒDistribution of Instances in a High-Availability ABAP+Java System
ý˜Ó•ÚQï$Ê’sÜWwG¬aF@Â…ŒV›ÐËı,`÷fix·CúŁ
76/162 PUBLIC 2009-04-30

4 Installation
4.2 Installation Checklist — Java Add-In
Dialog Instance
You perform the following steps on each host where you install the dialog instances.
1. You make sure that the global directories of the SAP system for which you want to install the dialog instance are
mounted [page 81] on the host on which you want to install the dialog instance.

This section includes the installation steps that you have to perform for the:
ˇ"s®Łˇ Java Add-In for an existing central ABAP system
ˇ"s®Łˇ Java Add-In for an existing distributed ABAP system
ˇ"s®Łˇ Java Add-In for an existing High-Availability ABAP system
ˇ"s®Łˇ ABAP+Java Dialog instance
Detailed information about the steps is available in the appropriate section. For more information about
the various installation options, see Installation Options Covered by This Guide [page 11].
Java Add-In for an Existing Central ABAP System
1. You perform the following installation steps in exactly this sequence:

1. You run SAPinst [page 83] to install the Java central services instance (SCS).
2. You run SAPinst [page 83] to install the database instance Java Add-In. This is to add the Java
schema to the database.
3. You run SAPinst [page 83] to install the Java Add-In to the existing ABAP central instance.
Java Add-In for an Existing Distributed ABAP System
If you want to install the Java Add-In for an existing ABAP system, you proceed as follows on the instance
hosts of the ABAP system:
1. To install the Java Add-In, you perform the following installation steps in exactly this sequence:
1. You determine a host as the SAP global host. On this host, you run SAPinst [page 83] to install
the Java central services instance (SCS).
2. On the database instance host of the existing ABAP system, you run SAPinst [page 83] to
install the database instance Java Add-In, which adds the Java schema to the database.
3. On the central instance host of the existing ABAP system, you run SAPinst [page 83] to install
the Java Add-In to the existing ABAP central instance.
2. If required, you install one or more ABAP+Java dialog instances. On the dialog instance host
(s) you proceed as follows:
2009-04-30 PUBLIC 77/162

4 Installation
CAUTION
You cannot install the Java Add-In for the existing ABAP dialog instances. Instead, you have
to install new ABAP+Java dialog instances. Before you do so, you must uninstall [page 151] the
existing ABAP dialog instances.
exe, <sapmnt>/<SAPSID>/profile, <sapmnt>/<SAPSID>/global).
2. You run SAPinst [page 83] to install the required ABAP+Java dialog instance(s).
Graphical Overview
The following figure shows how to install the Java Add-In in an existing distributed ABAP system:
ˆó�õ¢úc*êû˘§aa„¹qx1R,—Distributed Installation of a Java Add-In for an Existing ABAP System
78/162 PUBLIC 2009-04-30

4 Installation
›ßë“å…1+A†#ìwˇÓ•2yY=µDistributed Installation of a Java Add-In for an Existing ABAP System
›ßë—å—1 A“qÿwØÓÝ2(=µ'fi*Üû™^*ƒ,q•žÎæm¨Àßó[ IüÃm¸³�x(
Java Add-In for an Existing High-Availability ABAP System
This section describes how to install the Java Add-In for an existing high-availability (HA) ABAP system.
This procedure describes the steps that are required for a hardware cluster consisting of two nodes
(host A and host B):
1. You add the Java central services instance (SCS) for the Java Add-In to the switchover cluster
infrastructure as follows:
1. You run SAPinst [page 83] to install the SCS using the virtual host name [page 66] on the primary
cluster node, host A.
2. You repeat the following steps until you have finished installing the enqueue replication server
(ERS) on all nodes in the cluster:
1. You perform the switchover to a node where you want to install the ERS for the SCS.
2. You install the ERS as described in the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1)
English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key
Capability ABAP Technology Client/Server Technology The SAP Lock Concept Standalone
Enqueue Server Installing the Standalone Enqueue Server
2. On the database instance host, you run SAPinst [page 83] to install the database instance Java
Add-In.
3. On the central instance host, you run SAPinst [page 83] to install the central instance Java Add-
In.
4. We recommend that you install ABAP+Java dialog instances to create redundancy.
2009-04-30 PUBLIC 79/162

4 Installation
The dialog instances are not a single point of failure (SPOF). Therefore, you do not need to include
these instances in the cluster.
CAUTION
You cannot install the Java Add-In for existing ABAP dialog instances. Instead, you have to
install new ABAP+Java dialog instances.
1. You mount the global directories [page 81] in <sapmnt>/<SAPSID> of the SCS that you exported
from the switchover cluster infrastructure.
2. You run SAPinst [page 83] to install the ABAP+Java dialog instance.
Graphical Overview
The following figure shows how to install the Java Add-In in an existing High-Availability ABAP system:
ł�ð(�‹JóskÏyºaïÏ¦¡W/ˇøHigh Availability Installation - Java Add-In
ł�ð+�‘Jðs>ÏdºbuÏ·¡&/bøÞ"ö£ðùß©˙¶îÆ€h
ABAP+Java Dialog Instance
1. You make sure that the global directories of the SAP system for which you want to install the dialog instance are
mounted [page 81] on the host on which you want to install the dialog instance.
2. You run SAPinst [page 83] to install the ABAP+Java dialog instance.
80/162 PUBLIC 2009-04-30

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

and High-Availability Systems
If you install a central instance, a database instance, or a dialog instance on a host other than the SAP
Global host, you must mount directories from the SAP Global Host. The SAP Global Host is in most
cases the host on which the central services instance (SCS) (High-Availability: and the ABAP central
services instance (ASCS)) runs.
Prerequisites
Z à¿öv 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.
Z à¿öv 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 150].
Procedure
1. Log on to the SAP Global host as user root and export the following directories with root access
to the host on which you want to install the new instance:
<sapmnt>/<SAPSID>/exe
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
For more information, see Mounting Directories via NFS for AIX [page 130].
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 67]. Otherwise, the installation fails.
2. Log on to the host of the new instance as user root.
3. Create the following mount points and mount them from the SAP Global host:
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
CAUTION
Make sure that these mount points are permanent. Otherwise automatic start of the instance
services does not work when you reboot the system.
2009-04-30 PUBLIC 81/162

4 Installation
4.4 Performing a High-Availability Installation
U9éóîÏj©†§iyáqP˝ôOEÎ¯©»ºÿfiî¦è‹åÖ ÀíÁÞıÒí¿ÃŁyþø
4.4 Performing a High-Availability Installation

This section describes how to perform a high-availability (HA) installation. For more information,
consult your HA partner.
Prerequisites
U9é˝Ë You have completed all preparations, including switchover preparations for high availability [page 66].
U9é˝Ë For each installation option, specify the appropriate virtual host name with the SAPinst property
SAPINST_USE_HOSTNAME, as described in Running SAPinst [page 83].
CAUTION
If you install the Java Add-In to an existing ABAP system, note the following:
U9é˝Ën 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.
U9é˝Ën When you install the database instance, SAPINST_USE_HOSTNAME must point to the virtual
host name under which the database is installed.
U9é˝Ën When you install the central instance, SAPINST_USE_HOSTNAME must point to the virtual
host name under which the central instance is installed.
Procedure
1. Run SAPinst [page 83] to install the central services instances (SCS and ASCS) using the virtual host
name on the primary cluster node, host A.
2. Prepare the standby node, host B. You need to make sure that it meets the hardware and software
requirements and it has all the necessary file systems, mount points, and (if required) Network
File System (NFS), as described in Performing Switchover Preparations for High Availability [page 66]
3. Set up the user environment on the standby node, host B.
For more information, see Creating Operating System Users [page 53]. 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. Configure the switchover software and test that switchover functions correctly.
5. Install the database instance on the primary node, host A.
6. Install the central instance with SAPinst [page 83] 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 central services
instances (SCS and ASCS), which are protected by the cluster.
7. If required, install additional dialog instances with SAPinst [page 83] to replicate the SAP system services
that are not a SPOF. These nodes do not need to be part of the cluster.
82/162 PUBLIC 2009-04-30

4 Installation
4.5 Running SAPinst
NOTE
Make sure that you complete the post-installation activities for high availability.
¦ˇX¨êÌœ
‚fiJ˛ãÃn¼ŒËìbä/Jñ'²ìVrôâYfl
4.5 Running SAPinst

This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a GUI client and
a GUI server, which both use Java.
This section describes an installation where SAPinst, GUI client, and GUI server are running on the
same host.
If you need to see the installation on a remote display, we recommend you perform a remote installation with
SAPinst [page 135], where the SAPinst GUI is running on a separate host from SAPinst.
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools like
vncviewer or nxserver/nxclient – offered by various vendors or open source – for remote access to
the GUI on Windows workstations. We recommend you use the Hummingbird Exceed X Server, which
we use to validate installations with SAPinst. For more information, see SAP Note 1170809.
Useful Information About SAPinst
¦ˇXMÏ When you start SAPinst, it automatically starts the GUI server and the GUI client.
¦ˇXMÏ SAPinst creates the installation directory sapinst_instdir directly below the temporary directory.
SAPinst finds the temporary directory by checking the value of the following environment variables
in the following sequence: TEMP, TMP, and TMPDIR. If no value is set for these variables, SAPinst
creates the installation directory sapinst_instdir directly below the /tmp directory by default.
If you want SAPinst to create the installation directory sapinst_instdir in another directory, set
the environment variable TEMP to this directory before you start SAPinst.
Shell Used Command
Bourne shell (sh) TEMP=<directory>
export TEMP
C shell (csh) setenv TEMP <directory>
Korn shell (ksh) export TEMP=<directory>
CAUTION
Make sure that the installation directory is not mounted with NFS, or there might be problems
when the Java Virtual Machine is started.
RECOMMENDATION
We recommend that you keep all installation directories until the system is completely and
correctly installed.
¦ˇXMÏ SAPinst creates a subdirectory for each installation option called sapinst_instdir/
<installation_option_directory>.
2009-04-30 PUBLIC 83/162

4 Installation
4.5 Running SAPinst
®:UÞ)è SAPinst extracts itself to a temporary directory called sapinst_exe.xxxxxx.xxxx, which is located
in the environment variables TEMP, TMP, or TMPDIR. These files are deleted after SAPinst has stopped
running.
The temporary directory sapinst_exe.xxxxxx.xxxx sometimes remains undeleted. You can safely
delete it.
The temporary directory also contains the log file dev_selfex.out from the extraction process,
which might be useful if an error occurs.
CAUTION
If SAPinst cannot find a temporary directory, the installation terminates with the error
FCO-00058.
®:UÞ)è During the installation, the default ports 21200, 21212, and 4239 are used for communication
between SAPinst, GUI server, GUI, and HTTP server, as follows:
®:UÞ)⁄ SAPinst uses port 21200 to communicate with the GUI server.
®:UÞ)⁄ The GUI server uses port 21212 to communicate with the GUI client.
®:UÞ)⁄ 4239 is the port of the HTTP server, which is part of the GUI server.
If the ports for SAPinst and the GUI server are already in use, SAPinst automatically searches for
free port numbers. If the search fails, you see an error message and SAPinst exits.
In this case or if you want SAPinst to use specific ports, you can assign them by executing the
sapinst executable with the following parameters:
®:UÞ)⁄ SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server>
®:UÞ)⁄ GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_gui>
®:UÞ)⁄ GUISERVER_HTTP_PORT=<free_port_number_http_server>
®:UÞ)è To see a list of all available SAPinst properties, start SAPinst as described above with the option -
p:
./sapinst -p.
®:UÞ)è If required, you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu.
NOTE
If you need to terminate SAPinst, you can do this by pressing Ctrl + C .
Prerequisites
®:UÞ)è Make sure that you have defined the most important SAP system parameters as described in Basic
SAP System Parameters [page 40] before you start the installation.
®:UÞ)è Check that your installation hosts meets the requirements for the installation options that you
want to install. For more information, see Running the Prerequisite Checker [page 18].
®:UÞ)è If you want to perform a distributed or a high-availability installation, make sure that you have
exported and mounted global directories [page 81].
®:UÞ)è Check the value of the environment variable TEMP, TMP, or TMPDIR:
84/162 PUBLIC 2009-04-30

4 Installation
4.5 Running SAPinst
b•J;î Make sure that your operating system does not delete the contents of the temporary
directory /tmp or the contents of the directories to which the variable TEMP, TMP, or TMPDIR
points – for example, by using a crontab entry.
b•J;î Make sure that you have at least 60 MB of free space in the installation directory for each
installation option. In addition, you need 200 MB free space for the SAPinst executables. If you
cannot provide 200 MB free space in the temporary directory, you can set one of the
environment variables TEMP, TMP, or TMPDIR to another directory with 200 MB free space for
the SAPinst executables.
b•J;î Make sure that the temporary directory has the permissions 777.
b•J;† Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime
Environment (JRE).
b•J;† If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE for AIX
64-bit.
b•J;† Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where
<host_name> is the host on which you want to display the GUI.
Shell Used Command

Bourne shell (sh) DISPLAY=<host_name>:0.0
export DISPLAY
C shell (csh) setenv DISPLAY <host_name>:0.0
Korn shell (ksh) export DISPLAY=<host_name>:0.0
b•J;† Check the following values for user root:

b•J;î In csh, execute limit
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memorysize unlimited
b•J;î In sh or ksh, execute ulimit -a
Output Properties
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 2097148
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 8192
memory(KBytes) unlimited
2009-04-30 PUBLIC 85/162

4 Installation
4.5 Running SAPinst
If your parameter settings differ from the settings above, change these values accordingly.
EXAMPLE
If you have to change the value for descriptors to 8192, proceed as follows:
BÀrÆè� In csh, execute:
limit descriptors 8192
BÀrÆè� In sh or ksh execute:

ulimit -n 8192
BÀrÆèù If you want to install a dialog instance to an existing SAP system, make sure that:
BÀrÆèŒ There is exactly one entry in the /usr/sap/sapservices file for each SAP instance installed
on this host. Be sure to check that the entry refers to the correct profile.
BÀrÆèŒ There are no profile backup files with an underscore “_” in their profile name. If so, you must
replace the “_” with a “.”.
EXAMPLE
Rename /usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2_D20081204 to /
usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2.D20081204.
Procedure
1. Log on to the installation host as user root.
CAUTION
Do not use the user <sapsid>adm.

CAUTION
Make sure that the root user has not set any environment variables for a different SAP system
or database.
2. Mount the Installation Master DVD
Mount the DVDs locally. We do not recommend that you use Network File System (NFS), because
reading from DVDs mounted with NFS might fail.
For more information about mounting DVDs, see Mounting a CD / DVD for AIX [page 130].
3. Start SAPinst from the Installation Master DVD by entering the following commands:
cd <Installation Master_DVD>/IM_<OS>
./sapinst
NOTE
If you want to use a virtual host name, start SAPinst with the SAPinst property
SAPINST_USE_HOSTNAME as follows:
./sapinst SAPINST_USE_HOSTNAME=<virtual host name>
If you install the Java Add-In to an existing ABAP system, note the following:
BÀrÆèù 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.
86/162 PUBLIC 2009-04-30

4 Installation
4.5 Running SAPinst
´·OâFÀ When you install the database instance, SAPINST_USE_HOSTNAME must point to the virtual
host name under which the database is installed.
´·OâFÀ When you install the central instance, SAPINST_USE_HOSTNAME must point to the virtual
host name under which the central instance is installed.
CAUTION
´·OâFÀ Make sure that the installation directory is not mounted with NFS, or there might be
problems when the Java Virtual Machine is started.
´·OâFÀ 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
4. In the Welcome screen, choose one of the following installation options:
´·OâFÀ If you want to install a new SAP Solution Manager system from scratch, choose SAP Solution
Manager <Current Release> SAP Systems <Database> <System Variant> Based on AS ABAP and
AS Java .
´·OâFÀ If you want to install the Java Add-In for an existing SAP Solution Manager ABAP system,
choose SAP Solution Manager <Current Release> Software Life-Cycle Options Java Add-In for ABAP
<database> <system variant> .
´·OâFÀ Further Software Life-Cycle options are available under SAP Solution Manager <Current Release>
Software Life-Cycle Options .
For more information about available installation options, see the respective table in SAPinst
Installation Options [page 88].
5. Follow the instructions in the SAPinst input screens and enter the required parameters.
NOTE
For more information about the input parameters, position the cursor on the parameter and
press F1 .
After you have entered all requested input parameters, SAPinst displays the Summary screen. This
screen shows both the parameters that you entered and those that SAPinst set by default.
6. If required, change the displayed parameters as follows:
1. Select the parameters you want to change.
2. Choose Revise.
SAPinst displays input screens for the selected parameters.
3. Enter the new values for the parameters.
2009-04-30 PUBLIC 87/162

4 Installation
4.6 SAPinst Installation Options
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 Finished successfully screen.
8. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after SAPinst has finished.
Sometimes these remain in the temporary directory.
NOTE
If there are errors with the SAPinst extraction process, you can find the log file
dev_selfex.out in the temporary directory.
RECOMMENDATION
Keep all installation directories until you are sure that the system, including all instances, is
completely and correctly installed. Once the system is completely and correctly installed,
make a copy of the installation directories with all their contents. Save the copy to a physically
separate medium, such as a DVD or a USB drive that is separate from your installation hosts.
This might be useful for analyzing issues occurring later when you use the system. For security
reasons, do not keep installation directories on installation hosts, but make sure that you
delete them after saving them separately.
9. We recommend that you delete the directory <user_home>/.sdtgui/.
10. If you copied installation DVDs to your hard disk, you can delete these files when the installation
has successfully completed.
More Information
®‚™Ý:% Using SAPinst GUI [page 132]
®‚™Ý:% Interrupted Installation with SAPinst [page 133]
®‚™Ý:% Performing a Remote Installation with SAPinst [page 135]
®‚™Ý:% Starting SAPinst GUI Separately [page 136].
®‚™Ý:% Entries in the Services File Created by SAPinst [page 138]
®‚™Ý:% Troubleshooting with SAPinst [page 150]

This section provides information about the following in SAPinst:
®‚™Ý:% Installation Options
®‚™Ý:% Software Life-Cycle Options
NOTE
®‚™Ý:% Choose the required installation options from the tree structure exactly in the order they
appear for each system variant.
88/162 PUBLIC 2009-04-30

4 Installation
Û—Ù}“‹ If you want to use global accounts, which are configured on separate hosts, you must run the
installation option Operating System Users and Groups before you start the installation of the SAP
system (see table Software Life-Cycle Options below).
Û—Ù}“‹ If required, install a dialog instance for a central system (all instances on one host) or
distributed system by choosing <SAP System> Software Life-Cycle Options Application Server
<Database> Dialog Instance .
Installation Options
You choose SAP Systems with <your database> to install an SAP system with usage types or software units.
You can install the following system variants:
Û—Ù}“‹ Central System
Installation Options for a Central System
Installation Option Remarks
Central System Installs a complete SAP system including the following instances on one host:
Û—Ù}“ç Central services instance (SCS)
Û—Ù}“ç Database instance
Û—Ù}“ç Central instance
You can install a central system in the following parameter modes:
Û—Ù}“ç Typical Mode
If you choose Typical, the installation is performed with default settings.
As a result, you have to respond to only a small selection of prompts. If
you want to change any of the default settings, you can do so on the
Parameter Summary screen.
Û—Ù}“ç Custom Mode
If you choose Custom, you are prompted for all parameters. At the end,
you can still change any of these parameters on the Parameter Summary
screen.
NOTE
If you change a parameter with the Revise button on the Parameter
Summary screen, the installer takes you to the screen where you can
change the parameter. Depending on the changes, the installer might
guide you through other screens containing default parameters that it
has already processed. This might also happen if you press Back instead
of Next on the screen
Û—Ù}“‹ Distributed System
Installation Options for a Distributed System
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.
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.
2009-04-30 PUBLIC 89/162

4 Installation

Central Instance Mandatory step in installing a distributed SAP system on
several hosts.
Installs a central instance with usage types or software units.
You must have finished the database instance installation.
fÄ1R’û fÄ1½µ5ˇˆ\£2˘Ö[:BÈ¬Ú/ÔÍ”ÉÔ½Ï�.−Œ#�Ò„H˝J–²ÞW8ð»ò|:—ŠŁy-ªA<?²á©Ø
Ð5Ãu¬ú8¼È¢¼⁄"RfiÅ¶fõd£¢çgŸÒ
High-Availability System
Installation Options for a High Availability System
Central Services Instance Installs a central services instance for ABAP (ASCS) and prepares the SAP global
for ABAP (ASCS) host
Central Services Instance Installs a central services instance (SCS)
(SCS)
Database Instance Installs a database instance
Central Instance Installs a central instance with usage types or software units
Dialog Instance Installs a dialog instance
NOTE
fÄ1R’fl You might need to install dialog instances on 32-bit operating
systems if you want to use 32-bit SAP NetWeaver components, such
as Adobe document services. However, first check whether such 32-
bit components can run on 64-bit operating systems. If so, we
recommend running these 32-bit components on a 64-bit operating
system. If not, you can install an SAP dialog instance on 32-bit
operating systems to run these components. For all other SAP
instances, you must use 64-bit systems.
fÄ1R’fl We do not support operating an ABAP dialog instance with an ABAP
+Java system.
fÄ1R’fl You cannot install the Java Add-In for existing ABAP dialog
instances. Instead, you have to install new ABAP+Java dialog
instances.
fÄ1·µ5ˇ\ú2WÖK:ˇÈàÚÔè”ÉÔóÏ‘.«ŒZ�¡„p2˝"–ÛÞ:8‰»äa:äŠö˘-ÐAT?ÛáÜØlÐÃ¬œ8ÔÈÃ¼f"
Software Life-Cycle Options
You use the options located in this folder to perform the following tasks or to install the following
components:
Software Life-Cycle Options
Additional Preparation These preparation tasks comprise:
Options fÄ1R’û Operating System Users and Groups
Allows you to use global accounts that are configured on a separate host.
CAUTION
Perform this SAPinst option before you start the installation of your
SAP system.
fÄ1R’û Prerequisites Check
Checks your hardware and software requirements before you start the
installation.
90/162 PUBLIC 2009-04-30

4 Installation

Otherwise, SAPinst automatically checks the hardware and software
requirements during the installation with the Prerequisite Checker. If any changes
are necessary to the SAP system or operating system settings, SAPinst
automatically prompts you. For more information, see Running the Prerequisites
Checker in Standalone Mode [page 18].
Application Server Choose Application Server <Database> Dialog Instance to install one or more
dialog instances in an already installed SAP system, if required.
NOTE
˛q©cÀ× You might need to install dialog instances on 32-bit operating systems
if you want to use 32-bit SAP NetWeaver components, such as Adobe
document services. However, first check whether such 32-bit
components can run on 64-bit operating systems. If so, we recommend
running these 32-bit components on a 64-bit operating system. If not,
you can install an SAP dialog instance on 32-bit operating systems to
run these components. For all other SAP instances, you must use 64-bit
systems.
˛q©cÀ× We do not support operating an ABAP dialog instance with an ABAP
+Java system.
˛q©cÀ× You cannot install the Java Add-In for existing ABAP dialog instances.
Instead, you have to install new ABAP+Java dialog instances.
Java Add-In for ABAP Choose the options available in this folder to install AS Java to an already installed
SAP Solution Manager ABAP system:
˛q©cÀ× Central or Distributed System
˛q©cÀ¸ Central Services Instance (SCS) Java Add-In
Installs a central services instance (SCS).
˛q©cÀ¸ Database Instance Java Add-In
Installs the Java schema in the database of your ABAP system.
˛q©cÀ¸ Central Instance Java Add-In
Adds AS Java to the existing ABAP system.
CAUTION
When performing an upgrade installation, before you use this
option, uninstall the old ABAP dialog instances.
˛q©cÀ× High-Availability System
˛q©cÀ¸ Central Services Instance (SCS) Java Add-In
Installs a central services instance (SCS)
˛q©cÀ¸ Database Instance Java Add-In
Installs the Java schema in the database of your ABAP system
˛q©cÀ¸ Central Instance Java Add-In
Adds AS Java to the existing ABAP system.
˛q©cÀ¸ Dialog Instance
Installs an ABAP+Java dialog instance
NOTE
˛q©cÀ± If you want to use 32-bit SAP NetWeaver components, first
check whether these components can run on 64-bit operating
systems. If so, we recommend you to use 64-bit systems. If not,
you can install an SAP dialog instance on 32-bit operating
2009-04-30 PUBLIC 91/162

4 Installation

systems to run these components. For all other SAP instances,
you must use 64-bit systems.
:’…§!¬ We do not support operating an ABAP dialog instance with
an ABAP+Java system.
:’…§!¬ You cannot install the Java Add-In for existing ABAP dialog
instances. Instead, you have to install new ABAP+Java dialog
instances.
When performing an upgrade installation, before you use this
option, uninstall the old ABAP dialog instances.
LDAP Registration LDAP Support
Sets up LDAP support for an application server instance.
Choose this option once per SAP system and after you have:
1. Configured the Active Directory on a Windows host by choosing LDAP
Registration Active Directory Configuration
You have to configure the directory server only once. Afterwards all SAP
systems that should register in this directory server can use this setup.
NOTE
The option Active Directory Configuration is only available for Windows.
2. Installed an application server instance
For more information about LDAP and Active Directory, see Integration of LDAP
Directory Services [page 121].
System Copy Choose this service to perform a system copy.
For more information, see the system copy guide, which is available at:
http://service.sap.com/instguidesnw70 Installation Installation – SAP
NetWeaver Systems
Uninstall Choose this service to uninstall your SAP Solution Manager system.
For more information, see Deleting an SAP System [page 151].
92/162 PUBLIC 2009-04-30

5 Post-Installation
5.1 Post-Installation Checklist
5 Post-Installation
5.1 Post-Installation Checklist

NOTE
In a central system, all mandatory instances are installed on one host. Therefore, if you are
installing a central system, you can ignore references to other hosts.
You have to complete the following post-installation steps, which are described in more detail in the
linked sections:
1. If required, you perform a full installation backup [page 118] immediately after the installation has finished.
2. You check whether you can log on to the application server [page 94].
NOTE
In a distributed or high-availability system you check whether you can log on to every instance
of the SAP system that you installed.
3. You configure user management [page 95].
4. You ensure user security [page 96].
5. 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.
6. ˇ�+ÔÊ+M|+±È¥¥í:¹ã~ŒŁj¿ÖNÎ¸moÜ?ÓÚ-}¦6ŁMK†Ö•êmü†éˆ
If you installed a high-availability system, you set up the licenses for high availability [page 102].
CAUTION
ˇ�+ÞÊ+Mt+èÈê¥ý:â¯~)Œ°j¿ŸNô¸Qo¯GÓ»Ì!
7. You apply the latest kernel and Support Package stacks [page 103].
8. You configure the remote connection to SAP support [page 104].
CAUTION
9. You install the SAP Online Documentation [page 104].
CAUTION
10. You perform initial ABAP configuration [page 104].
CAUTION
2009-04-30 PUBLIC 93/162

5 Post-Installation
5.2 Logging On to the Application Server
11. You perform initial Java configuration [page 109].

12. If you want to use Adobe Document Services (ADS), you perform post-installation steps for Adobe Document
Services [page 110].
13. If required, you install SAP MaxDB administration tools [page 111].
14. If required, you install Secure Sockets Layer (SSL) for SAP MaxDB [page 113].
15. You back up the SAP MaxDB database [page 117].
16. You update the database software to the current release [page 117].
17. If required, you can install the SAP Solution Manager Enterprise Edition Add-On [page 118].
18. You perform a full backup of the installation [page 118].
19. You configure SAP Solution Manager [page 119].
5.2 Logging On to the Application Server

You need to check that you can log on to the SAP system with the standard users, given in the table
below.
NOTE
You can log on to SAP Solution Manager Diagnostics only after you have configured SAP Solution
Manager (see Configuring SAP Solution Manager [page 119]).
ABAP Users
User User Name Client
SAP system user SAP* 000, 001, 066
DDIC 000, 001
Java User
User User Name Storage: ABAP System
Administrator J2EE_ADMIN (default) or the name you gave this user during the
installation process.
Prerequisites
\Û“r-i The SAP system is up and running.
\Û“r-i You have already installed a front end.
Procedure
Logging On to the ABAP Application Server
1. Start SAP Logon on the host where you have installed the front end as follows:
\Û“r-i SAP GUI for Windows:
Choose Start All Programs SAP Front End SAP Logon .
\Û“r-i SAP GUI for Java:
94/162 PUBLIC 2009-04-30

5 Post-Installation
5.3 Configuring User Management
Choose Start All Programs SAP Clients SAP GUI for Java<Release> .
NOTE
You can alternatively enter the command guilogon in the SAP GUI installation directory
to start SAP GUI for Java.
The SAP Logon appears.
2. Create a logon entry for the newly installed system in the SAP Logon.
For more information about creating new logon entries, press F1 .
3. When you have created the entry, log on as user SAP* or DDIC.
Logging On to the Java Application Server
You access AS Java with a URL using a Web browser from your client machines. To log on to the Java
application server, proceed as follows:
1. Start a Web browser and enter the following URL:
http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00
NOTE
You must always enter a two-digit number for <Instance_Number>. For example, do not
enter 1 but instead enter 01.
EXAMPLE
If you installed SAP NetWeaver Application Server Java on host saphost06 and the instance
number of your SAP NetWeaver Application Server Java is 04, enter the following URL:
http://saphost06:50400
The start page of the SAP NetWeaver Application Server Java appears in the Web browser.
2. Log on by pressing the link of any of the provided applications, for example SAP NetWeaver
Administrator or System Information.
NOTE
To deactivate AS Java, proceed as follows:

1. Call transaction RZ11.
2. In the instance profile of every installed SAP instance, set parameter rdisp/j2ee_start from
1 to 0.
5.3 Configuring User Management

During the installation, the UME of your SAP system was configured to use AS ABAP as data source
(see table User Management Engine in Basic SAP System Parameters [page 40]). However, you can still change
the data source of the UME to a directory service.
For more information about changing the data source after installation and about related restrictions,
see the SAP Library at:
2009-04-30 PUBLIC 95/162

5 Post-Installation
5.4 Ensuring User Security
NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management User Management of the
Application Server Java Configuring User Management UME Data Sources

You need to ensure the security of the users that SAPinst created during the installation. The tables
below at the end of this section list these users:
l@ì»U Operating system users
l@ì»U SAP system users
l@ì»U Users for SAP NetWeaver Process Integration (PI)
During the installation, SAPinst by default assigned the master password to all users created during the
installation unless you specified other passwords.
If you change user passwords, be aware that SAP system users might exist in multiple SAP system clients
(for example, if a user was copied as part of the client copy). Therefore, you need to change the passwords
in all the relevant SAP system clients.
CAUTION
SAPinst applied the master password to users SAP* and DDIC only for SAP system clients 000 and
001, but not to users SAP*, DDIC, and EARLYWATCH in client 066.
Instead, SAPinst always assigns the following passwords to these users in client 066:
SAP*: 06071992
EARLYWATCH: support
See also Master Password in Basic SAP System Parameters [page 40].
RECOMMENDATION
User ID and password are encoded only when transported across the network. Therefore, we
recommend using encryption at the network layer, either by using the Secure Sockets Layer (SSL)
protocol for HTTP connections or Secure Network Communications (SNC) for the SAP protocols
dialog and RFC.
For more information, see:
SAP NetWeaver Library SAP NetWeaver by Key Capability Security Network and Transport Layer
Security
CAUTION
Make sure that you perform this procedure before the newly installed SAP system goes into
production. For security reasons, you also need to copy the installation directory to a separate,
secure location – such as a DVD – and then delete the installation directory.
96/162 PUBLIC 2009-04-30

5 Post-Installation
Procedure
For the users listed below, take the precautions described in the SAP Solution Manager security guide,
which you can find at http://service.sap.com/securityguide:
Operating System Users
After the installation, operating system users for SAP system and database are available as listed in the
following table:
Operating System and Database Users
User Type User Comment
Operating system user <sapsid>adm SAP system administrator
<smdsid>adm Administrator for the Diagnostics Agent
sqd<dbsid> SAP MaxDB database administrator
SAP System Users
After the installation, ABAP and Java system users are available. The following table shows these users
together with recommendations on how you can ensure the security of these users
ABAP and Java Users
User User Name Comment
SAP system user SAP* This user exists in at least clients 000, 001, and 066 of the
ABAP system.
RECOMMENDATION
We recommend that you use strong password
and auditing policies for this user.
DDIC This user exists in at least clients 000, 001, and 066 of the
ABAP system.
RECOMMENDATION
EARLYWATCH This user exists in at least client 066 of the ABAP system.
SAPCPIC This user exists in at least clients 000 and 001 of the ABAP
system
Administrator The name that you gave this This user exists in at least clients 000 and 001 of the ABAP
user during the installation or system and in the User Management Engine (UME) of
the default name J2EE_ADMIN the Java system. It has administrative permissions for
user management.
RECOMMENDATION
Guest The name that you gave this This user exists in at least clients 000 and 001 of the ABAP
user during the installation or system and in the User Management Engine (UME) of
the default name J2EE_GUEST the Java system. It is used for anonymous access.
2009-04-30 PUBLIC 97/162

5 Post-Installation

Communication The name that you gave this This user exists in at least clients 000 and 001 of the ABAP
user for the J2EE user during the installation or system and in the User Management Engine (UME) of
Engine the default name SAPJSF the Java system. It is used for a remote function call
(RFC) between the ABAP system and the Java system.
SDM SDM This user is used to access the Software Deployment
Manager (SDM) in the Java system.
Users for Adobe ADSUser This user exists in at least clients 000 and 001 of the ABAP
Document Services system and in the User Management Engine (UME) of
(ADS) the Java system. It is used for basic authentication.
ADS_AGENT This user exists in at least clients 000 and 001 of the ABAP
system and in the User Management Engine (UME) of
the Java system. It is used for processing forms between
an ABAP and a Java environment.
Data supplier user The name that you gave this This user exists in at least clients 000 and 001 of the ABAP
for System user during the installation system and in the User Management Engine (UME) of
Landscape Directory The recommended name is the Java system.
(SLD) SLDDSUSER.
(optional) NOTE
SAPinst created this user automatically if you
chose Configure local SLD during the installation.
ABAP API user for The name that you gave this This user exists in at least clients 000 and 001 of the ABAP
System Landscape user during the installation system and in the User Management Engine (UME) of
Directory (SLD) The recommended name is the Java system.
(optional) SLDAPIUSER.
NOTE
SAPinst created this user automatically if you
chose Configure local SLD during the installation.
Java Add-In Users for Users Stored in the ABAP System

User User Name Storage: ABAP System Comment
Administrator The name that you gave this user during This user exists in at least clients 000 and
the installation or the default name 001 of the ABAP system and in the User
J2EE_ADMIN Management Engine (UME) of the Java
system. It has administrative
permissions for user management.
RECOMMENDATION
We recommend that you use
strong password and auditing
policies for this user.
Guest The name that you gave this user during This user exists in at least clients 000 and
the installation or the default name 001 of the ABAP system and in the User
J2EE_GUEST Management Engine (UME) of the Java
system. It is used for anonymous access.
Communication user for The name that you gave this user during This user exists in at least clients 000 and
the J2EE Engine the installation or the default name 001 of the ABAP system and in the User
SAPJSF Management Engine (UME) of the Java
98/162 PUBLIC 2009-04-30

5 Post-Installation
User User Name Storage: ABAP System Comment

system. It is used for remote function call
(RFC) between the ABAP system and the
Java system.
SDM SDM This user is used to access the Software
Deployment Manager (SDM) in the Java
system.
Users for Adobe Document ADSUser This user exists in at least clients 000 and
Services (ADS) 001 of the ABAP system and in the User
Management Engine (UME) of the Java
system. It is used for basic
authentication.
ADS_AGENT This user exists in at least clients 000 and
001 of the ABAP system and in the User
Management Engine (UME) of the Java
system. It is used for processing forms
between an ABAP and a Java
environment.
Data supplier user for The name that you gave this user during This user exists in at least clients 000 and
System Landscape the installation 001 of the ABAP system and in the User
Directory (SLD) (optional) The recommended name is SLDDSUSER. Management Engine (UME) of the Java
system.
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 during This user exists in at least clients 000 and
Landscape Directory (SLD) the installation 001 of the ABAP system and in the User
(optional) The recommended name is SLDAPIUSER. Management Engine (UME) of the Java
system.
NOTE
SAPinst created this user
automatically if you chose Configure
local SLD during the installation.
Users for SAP NetWeaver Process Integration (PI)
If you chose installation option SAP NetWeaver Process Integration during the installation, users for SAP
NetWeaver Process Integration are available after the installation as listed in the following table:
Integration Repository Service User The name that you gave this user This user exists in SAP system client
during the installation or the default 001.
name PIREPUSER
2009-04-30 PUBLIC 99/162

5 Post-Installation

CAUTION
Do not log on with this user.
It is used by the system for
internal communication.
Integration Directory Service User The name that you gave this user This user exists in SAP system client
name PIDIRUSER
CAUTION
Landscape Directory Service User The name that you gave this user This user exists in SAP system client
name PILDUSER
CAUTION
Integration Server Application User The name you gave this user during This user exists in SAP system client
the installation or the default name 001.
PIAPPLUSER
Runtime Workbench Service User The name that you gave this user This user exists in SAP system client
name PIRWBUSER
CAUTION
Adapter Framework Server Service The name that you gave this user This user exists in SAP system client
User during the installation or the default 001.
name PIAFUSER
CAUTION
Integration Server Service User The name that you gave this user This user exists in SAP system client
during installation or the default 001.
name PIISUSER
CAUTION
Management Server Service User The name that you gave this user This user exists in SAP system client
during installation or the default 001.
name PILSADMIN
100/162 PUBLIC 2009-04-30

5 Post-Installation
5.5 Installing the SAP License

CAUTION
Exchange Infrastructure The name that you gave this user This user exists in SAP system client
Administrator during installation or the default 001.
name PISUPER
CAUTION
This user has extensive
authorizations. Make sure
that you assign a secure
password.
Exchange Infrastructure The name that you gave this user This user exists in SAP system client
Communicator during installation or the default 001.
name PI_JCD_RFC
CAUTION
More Information
ïkÑ:hy For more information about managing ABAP users, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP
NetWeaver Library Security Identity Management User and Role Administration of AS ABAP
ïkÑ:hy For more information about managing Java users, see:
NetWeaver Library Security Identity Management User Management of the Application Server Java
ïkÑ:hy For more information about Java administration tools for user maintenance, see:
NetWeaver Library SAP NetWeaver by KeyCapability Application Platform by Key Capability Java Technology
Administration Manual J2EE Engine J2EE Engine Administration Tools
5.5 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 4 weeks from
the date of installation.
CAUTION
Before the temporary license expires, you must apply for a permanent license key from SAP.
2009-04-30 PUBLIC 101/162

5 Post-Installation
5.6 High Availability: Setting Up Licenses
We recommend that you apply for a permanent license key as soon as possible after installing your
system.
Procedure
Install the SAP license as described in the SAP Library at:
NetWeaver Library Technology Consultant's Guide Cross-NetWeaver Configurations SAP License Keys
¹´ËPbï¿É°õÇFQN/t9Lujó5ßƒøÂ‹;ëÜ™
õº¸± ˝XG_˚åK˛&ŒmH
If you have installed a high-availability system, proceed as described in High Availability: Setting Up
Licenses [page 102].
¹´ÁPbï·Ééõ‹FA/89muOó5ßÈø-Â´;Ÿ¤™kõ[¸X
More Information
For more information about SAP license keys, see http://service.sap.com/licensekey.
5.6 High Availability: Setting Up Licenses

CAUTION
Every SAP system needs a central license, which is determined by the environment of the message
server. Since SAP's high-availability (HA) solution stipulates 2 or more cluster nodes (host machines)
where the message server is enabled to run, you have to order as many license keys [page 101] as you have
cluster nodes.
When we receive confirmation from your vendor that you are implementing a switchover
environment, we provide the required license keys for your system, 1 key for each machine.
SAP has implemented a license mechanism for transparent and easy use with switchover solutions and
clustered environments. Your customer key is calculated on the basis of local information on the
message server host. This is the host machine where the ABAP central services instance (ASCS) runs.
There is no license problem when only the database is switched over.
Prerequisites
The SAP system is up and running.
Procedure
1. Make sure that the ABAP central services instance (ASCS) on the primary host, node A, is running.
2. To find the hardware ID of the primary host, log on to any application server instance of the SAP
system and call transaction SLICENSE.
3. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster
and repeat the previous step.
102/162 PUBLIC 2009-04-30

5 Post-Installation
5.7 Applying the Latest Kernel and Support Package Stacks
Repeat this for all remaining nodes in the cluster.

4. To obtain the two license keys, enter the hardware IDs for the primary and backup hosts at:
http://service.sap.com/licensekey
5. To import the files containing the two licenses, log on to any application server instance of the
SAP system and call transaction SLICENSE.
6. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster
and repeat the previous step.
Repeat this for all remaining nodes in the cluster.
Result
The license is no longer a problem during switchover. This means you do not need to call
saplicense in your switchover scripts.
5.7 Applying the Latest Kernel and Support Package Stacks

Before you start configuring your newly installed SAP Solution Manager system, you have to make
sure that you have applied the latest kernel and Support Package stacks to your newly installed SAP
Solution Manager system.
Prerequisites
Make sure that you read the release notes for your SAP system before you apply Support Package stacks.
The release notes might include information about steps you have to perform after you have applied
the Support Package stacks. For more information, see http://service.sap.com/releasenotes.
Procedure
1. We recommend that you replace the installed kernel with the latest kernel from SAP Service
Marketplace.
For more information about how to download a kernel, see SAP Note 19466.
2. Apply the required Support Package stacks as follows:
§"½O• Check SAP Note 1276022 for information about the required Support Package stacks and
about how to obtain it.
§"½O• Apply ABAP Support Package stacks using the Support Package Manager (SPAM).
For more information, see the SAP Library at:
SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key
Capability Software Life Cycle Management Software Maintenance Support Package Manager
§"½O• Apply Java Support Package stacks using the Java Support Package Manager (JSPM).
2009-04-30 PUBLIC 103/162

5 Post-Installation
5.8 Configuring Remote Connection to SAP Support

Capability Software Life Cycle Management Software Maintenance Java Support Package Manager
3. You can now start configuring SAP Solution Manager.
For more information, see Configuring SAP Solution Manager [page 119].
5.8 Configuring Remote Connection to SAP Support

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

CAUTION
SAP currently provides an HTML-based solution for the online documentation, including the
Application Help, Glossary, Implementation Guide (IMG), and Release Notes. You can display the
documentation with a Java-compatible Web browser on all front-end platforms supported by SAP.
You can always find the up-to-date SAP online documentation at http://help.sap.com.
Process
Install the SAP online documentation in your SAP system as described in the README.TXT file contained
in the root directory of the online documentation DVD, delivered as part of the installation package.
5.10 Performing Initial ABAP Configuration

CAUTION
When you have installed your SAP ABAP system, you have to perform the following initial
configuration steps:
F–ÒAÌ Perform a consistency check
F–ÒAÌ Configure the transport management system
F–ÒAÌ Perform basic operations
104/162 PUBLIC 2009-04-30

5 Post-Installation
ÕM÷Gç¿ Configure system parameters

ÕM÷Gç¿ Configure the number of work processes
ÕM÷Gç¿ Configure kernel parameters
ÕM÷Gç¿ Install languages and performing language transport
ÕM÷Gç¿ Configure the integrated Internet Transaction Server (ITS)
ÕM÷Gç¿ Maintain your company address for initial users
ÕM÷Gç¿ Configure AS ABAP to support Secure Socket Layer (SSL)
ÕM÷Gç¿ Configure Fully Qualified Domain Names (FQDN)
ÕM÷Gç¿ Configure business applications
For more information, see the appropriate sections below.
Prerequisites
You have logged on to the ABAP application server as described in Logging On to the Application Server [page
94].
Procedure
Performing a Consistency Check
We recommend that you check the consistency of the newly installed SAP ABAP system. When logging
on to the system for the first time, you need to trigger a consistency check manually. The function is
then called automatically whenever you start the system or an application server.
This checks the following:
ÕM÷Gç¿ Completeness of installation
ÕM÷Gç¿ Version compatibility between the SAP release and the operating system
The initial consistency check determines whether:
ÕM÷GçÐ The release number in the SAP kernel matches the release number defined in the database
system
ÕM÷GçÐ The character set specified in the SAP kernel matches the character set specified in the database
system
ÕM÷GçÐ Critical structure definitions that are defined in both the data dictionary and the SAP kernel
are identical. The structures checked by this function include SYST, T100, TSTC, TDCT, and
TFDIR.
ÕM÷Gç¿ Accessibility of the message server
ÕM÷Gç¿ Availability of all work process types
ÕM÷Gç¿ Information about the enqueue server and the update service
To perform a consistency check, you can either call transaction SICK (SAP initial consistency check)
or choose Tools Administration Administration Installation Check from the menu.
2009-04-30 PUBLIC 105/162

5 Post-Installation
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability System
Management Tools for Monitoring the System Consistency Check
Configuring the Transport Management System
You have to perform some steps to be able to use the Transport Management System.
1. Perform post-installation steps for the transport organizer:
1. Call transaction SE06.
2. Select Standard Installation.
3. Choose Perform Post-Installation Actions.
2. Call transaction STMS in the ABAP system to configure the domain controller in the Transport
Management System (TMS).
3. 9‚Ý−hŸð)´öØñvB*ð”.ªxÔ—˛¾F÷ïq¶Ç$»äÄ˘]Þ~I³Cˇ˙—ø"¸)2·ïÖ/†½
In TPPARAM, set <SAPSID>/dbhost to the virtual host name of the DB instance.
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 in your high-availability system.
9‚Ýˆ−hŸø)íöŠñfBqðÂ.‰xñ—˛¾÷Õq−ÇW»œÄy]?~
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software
Life Cycle Management Software Logistics Change and Transport System
Performing Basic Operations
1. Go to the SAP Library at:

SAP NetWeaver Library SAP NetWeaver by Key Capability
2. Choose the relevant sections to perform the following operations:
Operation Section in SAP Documentation
Set up operation modes – Solution Life Cycle Management by Key Capability System Management Configuration
transaction RZ04 Operation Modes
Set up logon groups – Solution Life Cycle Management by Key Capability System Management Configuration
transaction SMLG Logon Load Balancing SAP Logon
Set up administrators Solution Life Cycle Management by Key Capability System Management Background
Processing Authorizations for Background Processing
Schedule background jobs Solution Life Cycle Management by Key Capability System Management Background
Processing
Install a printer Solution Life Cycle Management by Key Capability System Management SAP Printing
Guide
Configure the system log Solution Life Cycle Management by Key Capability System Management Tools for
Monitoring the System System log Configuring the System Log
106/162 PUBLIC 2009-04-30

5 Post-Installation
Configuring System Parameters
For more information about system profiles, which is where work processes and profile parameters are
defined, and how to configure them, see the SAP Library at:
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability System
Management Tools for Monitoring the System Configuration Profiles
Checking the Configured Number of Work Processes
SAPinst installs ABAP systems with a minimum number of work processes. This is only an initial
configuration so that you can start working 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 ABAP system application.
For more information about how many work processes to configure and about how to set the number,
see SAP Notes 39412 and 9942.
Configuring Kernel Parameters
To configure your kernel parameters, follow the recommendations in SAP Notes 146289 and 835474.
Installing Languages and Performing Language Transports
@éß@/˛ Install languages using transaction I18N:

@éß@/r If you want to use English only, you must activate the default language settings once.
@éß@/r If you want to use languages other than English, you must install them and activate the
language settings.
For more information about configuring the language settings, see the online documentation in
transaction I18N at I18N Menue I18N Customizing .
@éß@/˛ Perform language transport using transaction SMLT as described in the SAP Library at:
Software Life Cycle Management Software Logistics Change and Transport System Language Transport
Using and Configuring the SAP ITS Integrated ICM
The SAP Internet Transaction Server (SAP ITS) is integrated in the SAP NetWeaver Application Server
ABAP (AS ABAP) as an Internet Communication Framework (ICF) service. You can access this, like
other services, with the Internet Communication Manager (ICM). With the SAP ITS integrated in AS
ABAP, the Web browser now communicates directly with the SAP system. Furthermore, all SAP ITS-
related sources, such as service files, HTML templates, or MIME files, are now stored in the database of
the system.
The SAP ITS supports the following functions:
@éß@/˛ SAP GUI for HTML
@éß@/˛ Internet Application Component (IAC) runtime or Web Transaction technology
2009-04-30 PUBLIC 107/162

5 Post-Installation
For more information about how to configure the integrated SAP ITS, see the SAP Library at:
NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology
UI Technology Web UI Technology SAP ITS in the SAP NetWeaver Application Server Configuration
Maintaining Your Company Address for Initial Users
Maintain your company address in your ABAP system using transaction SU01 as described in the SAP
Library at:
NetWeaver Library SAP NetWeaver by Key Capability 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.
Configuring AS ABAP to Support Secure Socket Layer (SSL)
If you installed the SAP Cryptographic Library – see Basic SAP System Parameters [page 40] – you have to
configure AS ABAP to support Secure Socket Layer (SSL), as described in the SAP Library at:
NetWeaver Library SAP NetWeaver by Key Capability Security System Security System Security for SAP Web
AS ABAP Only Trust Manager Example Configuring the SAP Web AS for Supporting SSL
Configuring Fully Qualified Domain Names (FQDN)
If want to use Web Dynpro ABAP as UI technology and you assigned a DNS Domain Name to your SAP
System – see Basic SAP System Parameters [page 40]– you have to perform the required configuration steps.
For more information, see SAP Note 654982 and the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver
Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology UI
Technology Web UI Technology Web Dynpro ABAP Web Dynpro ABAP Configuration Fully Qualified Domain
Names (FQDN)
Configuring Business Applications
Prepare the SAP system for using business applications, which includes customizing the ABAP system
and the business components, as described in the SAP Library at:
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability
Customizing
108/162 PUBLIC 2009-04-30

5 Post-Installation
5.11 Performing Initial Java Configuration
5.11 Performing Initial Java Configuration

When you have installed your SAP Java system, you have to perform the following initial configuration
steps:
3ÿł®À§ Create a second administrator user
3ÿł®À§ Check and configure the necessary communication ports
3ÿł®À§ Check the Java Virtual Machine (Java VM) settings
For more information, see the appropriate sections below.
Procedure
Creating Another Administrator User
To prevent locking the administrator in case you change its password and forget to update the entry
secure storage, we also recommend you create a second administrator user after installing a system
based on AS Java.
Create another administrator user and assign the appropriate group and role as described in the SAP
Library at:
http://help.sap.com/nw70 SAP NetWeaver by Key Capability SAP NetWeaver 7.0 Library (including
Enhancement Package 1) SAP NetWeaver Library Security Identity Management User Management of the
Application Server Java Administration of Users and Roles Managing Users, Groups, and Roles
Checking and Configuring the Necessary Communication Ports
When you install a Java instance or create an additional server process, AS Java assigns default values
to the communication ports. If some of these ports are being used by another program, you have to
manually assign a different value to the relevant port. If necessary, you can change the assigned join
port of a server process, on which the server process listens for connections (for example, when the
port assigned to the cluster element is already in use by another program).
3ÿł®À§ For more information about Java ports, see:
NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java
Technology Administration Manual J2EE Engine Reference AS Java Ports
3ÿł®À§ You can check and configure communication ports using the Visual Administrator or the Config
Tool:
3ÿł®ÀÈ For more information about how to start and handle the Visual Administrator, see the SAP
Library at:
Technology Administration Manual J2EE Engine J2EE Engine Administration Tools Visual
Administrator
3ÿł®ÀÈ For more information about how to start and handle the Config Tool, see the SAP Library at
2009-04-30 PUBLIC 109/162

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

Technology Administration Manual J2EE Engine J2EE Engine Administration Tools Config Tool
Checking the Java VM Memory Settings
You can find recommendations for Java VM Memory Settings in SAP Note 723909.
You can check and modify Java VM memory settings using the Visual Administrator or the Config
Tool:
’¹\/ For more information about how to start and handle the Visual Administrator, see the SAP Library
at:
Technology Administration Manual J2EE Engine J2EE Engine Administration Tools Visual
Administrator
’¹\/ For more information about how to start and handle the Config Tool, see the SAP Library at:
Technology Administration Manual J2EE Engine J2EE Engine Administration Tools Config Tool
More Information
For more information about the configuration and administration of the J2EE Engine and about SAP
Java technology, see Accessing the SAP Java Documentation [page 147].
5.12 Performing Post-Installation Steps for Adobe Document

Services
Adobe document services (ADS) can run in different IT scenarios, infrastructures, and usage types in
a new or in an upgraded installation. In some cases the installation process cannot perform all
configuration settings that are necessary for the use of Adobe document services, for example, if ABAP
and Java are not installed on the same server. Use this process to check whether all configuration steps
are complete and to verify which steps you still need to perform manually.
Prerequisites
Adobe document services are installed on your system.
Procedure
’¹\/ Check the ADS configuration as described in the Adobe Document Services Configuration Guide
at:
SAP NetWeaver Library Technology Consultant's Guide Business Task Management Adobe Document Services
110/162 PUBLIC 2009-04-30

5 Post-Installation
5.13 Configuring the Connection to a Central System Landscape Directory
(Configuration) Adobe Document Services Configuration Guide Configuring the Web Service Securing Access to
the Web Service Configuration Check
¤%v›Ã Perform manual configuration as described in the Adobe Document Services Configuration Guide
at:
SAP NetWeaver Library Technology Consultant's Guide Business Task Management Adobe Document Services
(Configuration) Adobe Document Services Configuration Guide
More Information
A printable version of the document Configuration Guide for SAP Interactive Forms by Adobe is available at:
http://sdn.sap.com/irj/sdn/adobe Installation & Configuration SAP Interactive Forms by Adobe –
Configuration Guides Configuration Guide for SAP Interactive Forms by Adobe
5.13 Configuring the Connection to a Central System

Landscape Directory
For each system in your landscape that reports data to a central System Landscape Directory (SLD),
you have to configure a corresponding SLD data supplier.
Procedure
Configure the SLD data suppliers and the API for the SLD as described in the SAP Library at:
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software
Life Cycle Management System Landscape Directory Configuring Systems to Connect to SLD
More Information
This documentation is also available in PDF form in the User Manual – SLD of SAP NetWeaver 7.0 at http://
www.sdn.sap.com/irj/sdn/nw-sld.
5.14 Installing or Upgrading Database Studio for SAP MaxDB

This section describes how to install or upgrade Database Studio for SAP MaxDB and SAP liveCache on
Windows front ends. Database Studio is the database administration tool for SAP MaxDB.
For more information about Database Studio, see one of the following:
¤%v›Ã http://maxdb.sap.com/doc/7_7/default.htm Tools Database Studio
¤%v›Ã http://www.sdn.sap.com/irj/sdn/maxdb SAP MaxDB Knowledge Center The Complete SAP
MaxDB Documentation Set SAP MaxDB 7.7 Library Tools Database Studio
2009-04-30 PUBLIC 111/162

5 Post-Installation
5.14 Installing or Upgrading Database Studio for SAP MaxDB
NOTE
Database Studio replaces Database Manager GUI and SQL Studio, which were available in previous
releases.
Prerequisites
˘è.,¬ You can install Database Studio on Linux or Windows in your network, even if your database runs
on a different operating system. You can then remotely administer the database on a different host.
The instructions below refer mainly to the Windows version.
NOTE
To run Database Studio on Linux, you need to meet the requirements for the MaxDB database
server.
˘è.,¬ Your PC must meet the following minimum requirements:
˘è.,Ã Software requirements:
Operating System Requirements for Database Studio
Operating System Version
Windows XP Professional Service Pack 2
Windows 2003 Server Service Pack 1
˘è.,Ã Hardware requirements (currently only 32-bit platforms are supported):
˘è.,Ê RAM: 512 MB ( recommended RAM: 1 GB)
˘è.,Ê Processor speed: 1.5 GHz
˘è.,Ê Free disk space: 200 MB
˘è.,Ê Monitor: 1024x768 pixels, 256 colors
˘è.,¬ You can obtain the required files from one of the following:
˘è.,Ã The DVD for MaxDB RDBMS or SAP liveCache
˘è.,Ã By downloading from:
http://service.sap.com/patches Entry by Application Group Additional Components
MaxDB MaxDB GUI COMPONENTS/TOOLS MAXDB DATABASE STUDIO 7.7
˘è.,¬ You need Java Runtime Environment (JRE) version 5 (also known as 1.5) or higher.
To check your Java version, enter the following command:
java -version
To download Java, go to http://java.com/en/download.
˘è.,¬ To uninstall the database manager GUI, which is the tool replaced by Database Studio, choose
Start Settings Control Panel - Add/Remove Programs .
Procedure
1. Start the installation or upgrade as follows:
˘è.,¬ If you are using the MaxDB RDBMS DVD:
<DVD>/MAXDB_LINUX_I386\SDBSETUP
˘è.,¬ If you are using the liveCache DVD:
112/162 PUBLIC 2009-04-30

5 Post-Installation
5.15 Secure Sockets Layer Protocol for Database Server Communication
<DVD>/LC_LINUX_I386\SDBSETUP
¢a C — If you are using the downloaded files, simply execute the downloaded SDBSETUP file.
The Installation Manager starts.
2. Choose Start Installation/Upgrade and then Custom.
You see a list of the components to be installed.
3. Deselect all components except Database Studio.
4. Choose Install.
The installation manager installs Database Studio.
5. If you are prompted to restart your computer after the installation, make sure that you first shut
down any databases that are running.
More Information
For more information about Database Studio, including troubleshooting, see SAP Note 1097311.
5.15 Secure Sockets Layer Protocol for Database Server

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

1. Install the SAP cryptographic library [page 113] on the client host and on the server host machines
2. Generate the Personal Security Environment [page 115] (PSE) on the server (SSL Server PSE) and on the
client (SSL Client PSE).
5.15.1 Installing the SAP Cryptographic Library

The SAP Cryptographic Library supplies the cryptographic functions required to build a database server-
client connection using Secure Sockets Layer (SSL) protocol. Therefore, you need to install the SAP
Cryptographic Library on the host machine of the SAP MaxDB database server and the SAP Application
Server (AS).
The installation package sapcrypto.car consists of the following:
¢a C — SAP Cryptographic Library: libsapcrypto.so/sl
2009-04-30 PUBLIC 113/162

5 Post-Installation
a¥Ò„¾ License ticket: ticket

a¥Ò„¾ Configuration tool: sapgenpse.exe
You use the configuration tool to generate key pairs and PSEs.
CAUTION
The SAP Cryptographic Library is subject to German export regulations and might not be available
to some customers. In addition, the library might be subject to the local regulations of your
country. These regulations might further restrict import, use, and export or re-export of
cryptographic software.
For more information, contact your local SAP representative.
Prerequisites
Download the appropriate SAP Cryptographic Library installation package for your operating system
from http://service.sap.com/swdc.
Procedure
1. Unpack the installation package for the SAP Cryptographic Library using sapcar.exe, which you
can find for example on your Installation Master DVD, using the following command:
car -xvf SAPCRYPTO.CAR
NOTE
The remainder of the procedure (as described below) does not apply to client applications
such as SQL Studio, which do not recognize an “independent” directory. In this case, you
must copy the SAPCRYPTO installation package to the installation directory of the application.
In this directory you need to create a directory sec, into which you copy the ticket file.
2. Copy the sapcrypto library to the lib subdirectory of the “independent program” directory.
You can find the value of the independent program directory by entering the following command:
dbmcli dbm_getpath IndepProgPath
EXAMPLE
The independent program directory might be called the following:

/sapdb/programs/lib
3. Copy the configuration tool sapgenpse.exe to the directory <independent program>\lib.
4. Create a subdirectory called sec under the “independent data” directory and copy the ticket file
into it.
EXAMPLE
The result might look as follows:

/sapdb/data/sec/ticket
5. Make sure that the directory and the files that the sec directory contains – including the ticket
file and the SSL Server PSE – belong to the user lcown and the group lcadm, and that the rights are
restricted to 0600.
114/162 PUBLIC 2009-04-30

5 Post-Installation
Result
The system copies the SAP Cryptographic Library is copied to the application server and configures the
environment correctly so that the server can find the library at runtime.
5.15.2 Generating the Personal Security Environment

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

2. Set up the following environment variable:
SECUDIR=<independent data>\sec
3. Create a SSL Server PSE, SDBSSLS.pse, and generate a certificate request file, certreq, in the
directory defined by SECUDIR (see previous step):
sapgenpse gen_pse -v -r <SECUDIR>\certreq -p SDBSSLS.pse “<your distinguished
name>”
For each database server that uses a server-specific PSE, you must set up a unique certificate request.
If you are using a valid system-wide SSL Server PSE, you only need to set up a single certificate
request for all servers.
4. Send the certificate request to the CA for signing. You can either send it to the SAP CA or to another
CA.
2009-04-30 PUBLIC 115/162

5 Post-Installation
You must make sure that the CA offers a certificate corresponding to the PKCS#7 certificate chain
format. Thawte CA at http://www.thawte.com offers a suitable certificate, either SSL Chained CA
Cert or PKCS#7 certificate chain format.
The CA validates the information contained in the certificate request, according to its own
guidelines, and sends a reply containing the public key certificate.
5. After you have received the reply from the CA, make sure that the contents of the certificate
request have not been destroyed during download.
For example, if you requested the certificate on a UNIX system and stored it on a Windows front
end, the formatting (that is, line indents and line breaks) is affected.
To check the contents, open the certificate request with a text editor (such as Notepad) and repair
the line indents and the line breaks.
EXAMPLE
This is an example of a certificate request:

-----BEGIN CERTIFICATE REQUEST-----
MIIBPzCBqQIBADAAMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD/302IT+/Y
wpignSw7U9FWneyWz3Wil0S18aFCYkRo00wCpD8UwcaC4dds4uGT6hl2WlJ0/FOtUg
+EQxonZbaRrk9sTalkn1mqx3YAUe/gEaGdf1wvuYkb0gjMk81iM/jb9BJd8srMPyoBy9jMC7v5u7
+TZWmWa6RjnvClvYGgMwIDAQABoAAwDQYJKoZIhvcNAQEFBQADgYEAx2zuaTAOKPdGmxUKYlWdasU
pim4vhfaHa7ZDBwipvKJ8akYCT
+dpmVjhcph9E7cUjL80/6Rup5cnLAAO5FhVt5MS6zNJa9YYSN9XP+5/
MPF6Q4ayJ0VryTkSpbbPrWLbKh1Dds97LQVuQ/myKIAHECwyW6t7sAFJWn4P0fdxmKo= -----END
CERTIFICATE REQUEST-----
6. Import the reply to the SSL Server PSE:
1. Copy the text to a temporary file called srcert.
2. Enter the following command:
sapgenpse import_own_cert -c srcert -p SDBSSLS.pse
You have generated the SSL Server PSE. You can now start the XServer as usual (if it is already
running, you must stop and restart it).
7. To check whether the SSL functionality is working correctly, view the trace file niserver_<local
computer name>.trace in the <independent data>\wrk directory.
To generate the SSL Client PSE, proceed as follows:
1. Change to the <independent programs>\lib directory.
2. Set up the following environment variable:
SECUDIR=<independent data>\sec
3. Enter <independent program>/lib in the environment variable LD_LIBRARY_PATH.
4. Create an anonymous client SSL Client PSE, SDBSSLA.pse in the directory defined by SECUDIR (see
previous step):
sapgenpse gen_pse -v -noreq -p SDBSSLA.pse
116/162 PUBLIC 2009-04-30

5 Post-Installation
5.16 Backing Up the SAP MaxDB Database
You can leave the distinguished name empty.

Before you can establish an SSL connection to a database server, the server certificate must be
entered in the PK list of the anonymous client certificate.
5. To see the database server certificate, enter the following command:
„x_ping -n <servermode> -c[apture]
You can check whether to trust the database server certificate. The client certificate is not affected
by this.
6. Start the import with this command:
„x_ping -n <servermode> -i[import]
7. To administer the PSE, use the configuration tool sapgenpse. For more information, enter the
following command:
sapgenpse -h
NOTE
For applications such as SQL Studio replace the independent data or independent program
in the above description with the installation directory.
5.16 Backing Up the SAP MaxDB Database

You need to define backup media and back up the SAP MaxDB database using Database Manager GUI
(DBMGUI).
Prerequisites
tãfù You have finished client maintenance.
tãfù You have installed Database Studio [page 111].
tãfù You can find more information on backing up the database at:
https://www.sdn.sap.com/irj/sdn/maxdb SAP MaxDB Knowledge Center The Complete SAP
MaxDB Documentation Set SAP MaxDB 7.7 Library Glossary Backup
Procedure
1. Define the backup template as described in Glossary Backup Templates in the above
documentation.
2. Back up the database as described in Glossary Data Backup and Log Backup in the above
documentation.
5.17 Updating the Database Software to the Current Release

After the installation and before you start production operation, we strongly recommend you to update
the database software.
2009-04-30 PUBLIC 117/162

5 Post-Installation
5.18 Installing the SAP Solution Manager Enterprise Edition Add-On (Optional)
Procedure
1. Download the latest SAP MaxDB patches as follows:
http://service.sap.com/swdc Download Database Patches MaxDB
For more information about upgrading to a MaxDB Support Package, see SAP Note 735598.
5.18 Installing the SAP Solution Manager Enterprise Edition

Add-On (Optional)
If you want to use the functionality of SAP Solution Manager Enterprise Edition, you have to install
the SAP Solution Manager Enterprise Edition Add-On.
Procedure
Proceed as described in SAP Note 1109650.
More Information
For more information, see the SAP Solution Manager Master Guide at:
http://service.sap.com/instguides SAP Components SAP Solution Manager <Current Release>
Master Guide SAP Solution Manager <Current Release>
5.19 Performing a Full Installation Backup

You must perform a full offline backup at the end of the installation. This procedure also describes
how to use the back-up data for a restore.
CAUTION
Make sure that you fully back up your database so that you can recover it later if necessary.
Prerequisites
¬#`SX You have completed client maintenance, such as the client copy. For more information, see
Configuring SAP Solution Manager [page 119].
¬#`SX You have logged on [page 94] as user <sapsid>adm and stopped the SAP system and database [page 143].
Procedure
The UNIX commands used in this procedure work on all hardware platforms. For more information
about operating system-specific backup tools, see your operating system documentation.
Backing Up the Installation

NOTE
The following only applies to a standard installation.
1. Back up the following file systems:
118/162 PUBLIC 2009-04-30

5 Post-Installation
5.20 Configuring SAP Solution Manager
3 _¤@ /usr/sap/<SAPSID>
3 _¤@ /usr/sap/trans
3 _¤@ <sapmnt>/<SAPSID>
3 _¤@ Home directory of the user <sapsid>adm
3 _¤@ All database-specific directories
Proceed as follows:
1. Log on as user root.
2. Manually create a compressed tar archive that contains all installed files:
3 _¤@ Saving to tape:
tar —cf — <file_system> | compress —c > <tape_device>
3 _¤@ Saving to the file system:

tar —cf — <file_system> | compress —c > ARCHIVENAME.tar.Z
2. Back up the operating system using operating system means.
This saves the structure of the system and all configuration files, such as file system size, logical
volume manager configuration and database configuration data.
Restoring Your Backup
If required, you can restore the data that you previously backed up.
CAUTION
Check for modifications to the existing parameter files before you overwrite them when restoring
the backup.

2. Go to the location in your file system where you want to restore the backup image.
3. Execute the following commands to restore the data:
3 _¤@ Restoring the data from tape:
cat <tape_device> | compress —cd | tar —xf —
3 _¤@ Restoring the data from the file system:

cat ARCHIVENAME.tar.Z | compress —cd | tar —xf —

You have to perform initial basic configuration and scenario specific configuration for your newly
installed SAP Solution Manager system.
Procedure
Proceed as described in the following documentations available at http://service.sap.com/
instguides SAP Components SAP Solution Manager Release 7.0 EHP1 :
2009-04-30 PUBLIC 119/162

5 Post-Installation
k–ZcD1 SAP Enhancement Package 1 for SAP Solution Manager 7.0 Configuration Guide
NOTE
This documentation also describes how to perform automatic configuration using

transaction SOLMAN_SETUP.
k–ZcD1 SAP Enhancement Package 1 for SAP Solution Manager Security Guide
120/162 PUBLIC 2009-04-30

6 Additional Information
6.1 Integration of LDAP Directory Services
The following sections provide additional information about optional preparation, installation, and
post-installation tasks.
There is also a section describing how to delete an SAP system.
Preparation
/†G¦É÷ Integration of LDAP Directory Services [page 121]

/†G¦É÷ Setting up Swap Space for AIX [page 125]
/†G¦É÷ Creating AIX Groups and Users [page 126]
/†G¦É÷ Setting Up File Systems and Raw Devices for AIX [page 127]
/†G¦É÷ Dialog Instance Installation for an Upgraded System: Updating Instance Profiles [page 128]
/†G¦É÷ Mounting a CD / DVD for AIX [page 130]
/†G¦É÷ Exporting and Mounting Directories via NFS for AIX [page 130]
Post-Installation
/†G¦É÷ Starting and stopping the SAP system [page 139]

/†G¦É÷ If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page
146]
/†G¦É÷ Accessing the SAP Java documentation [page 147]
/†G¦É÷ Initial Configuration for System Landscape Directory (SLD) [page 149]
/†G¦É÷ Initial Configuration of Adobe Document Services (ADS) [page 148]
/†G¦É÷ Heterogeneous SAP System Installation [page 150]
/†G¦É÷ Troubleshooting [page 150]
Deleting an SAP System or SAP Instance
/†G¦É÷ Deleting an SAP System [page 151]

/†G¦É÷ Deleting a Diagnostics Agent [page 152]

This section explains the benefits of using the SAP system with the Lightweight Directory Access
Protocol (LDAP) directory and gives an overview of the configuration steps required to use an SAP
system with the directory.
LDAP defines a standard protocol for accessing directory services, which is supported by various
directory products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory services
2009-04-30 PUBLIC 121/162

enables important information in a corporate network to be stored centrally on a server. The advantage
of storing information centrally for the entire network is that you only have to maintain data once,
which avoids redundancy and inconsistency.
If an LDAP directory is available in your corporate network, you can configure the SAP system to use
this feature. For example, a correctly configured SAP system can read information from the directory
and also store information there.
NOTE
The SAP system can interact with the Active Directory using the LDAP protocol, which defines:
m{.�1 The communication protocol between the SAP system and the directory
m{.�1 How data in the directory is structured, accessed, or modified
If a directory other than the Active Directory also supports the LDAP protocol, the SAP system
can take advantage of the information stored there. For example, if there is an LDAP directory on
a UNIX or Windows server, you can configure the SAP system to use the information available
there. In the following text, directories other than the Active Directory that implement the LDAP
protocol are called generic LDAP directories.
CAUTION
This section does not provide information about the use of LDAP directories with the LDAP
Connector. For more information about using and configuring the LDAP Connector for an ABAP
system, see the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including
Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security
Identity Management User and Role Administration of AS ABAP Configuration of User and Role
Administration Directory Services LDAP Connector
Prerequisites
You can only configure the SAP system for Active Directory services or other LDAP directories if these
are already available on the network. As of Windows 2000 or higher, the Active Directory is
automatically available on all domain controllers. A generic LDAP directory is an additional component
that you must install separately on a UNIX or Windows server.
Features
In the SAP environment, you can exploit the information stored in an Active Directory or generic
LDAP directory by using:
m{.�1 SAP Logon
m{.�1 The SAP Microsoft Management Console (SAP MMC)
m{.�1 The SAP Management Console (SAP MC)
For more information about the automatic registration of SAP components in LDAP directories and
the benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information in
Directory Services at
122/162 PUBLIC 2009-04-30

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0a0d051-
eae2-2b10-e1ac-f3a7f6494c53
For more information about the SAP MC and about how to configure it to access LDAP Directories,
see the documentation SAP Management Console at http://help.sap.com/nw70 SAP NetWeaver 7.0
Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability
Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine
Administration Tools SAP Management Console
SAP Logon
Instead of using a fixed list of systems and message servers, you can configure the SAP Logon in the
sapmsg.ini configuration file to find SAP systems and their message servers from the directory. If you
configure SAP logon to use the LDAP directory, it queries the directory each time Server or Group selection
is chosen to fetch up-to-date information on available SAP systems.
To use LDAP operation mode, make sure that the sapmsg.ini file contains the following:
[Address]
Mode=LDAPdirectory
LDAPserver=
LDAPnode=
LDAPoptions=
Distinguish the following cases:
’Pä†±ˆ If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For more
information, see the SAP system profile parameter ldap/options.
’Pä†±ˆ You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either of
the following is true:
’Pä†±u The client is not located in the same domain forest as the Active Directory
’Pä†±u 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.
’Pä†±ˆ For other directory services, you can use LDAPnode to specify the distinguished name of the SAP
root node. For more information, see the SAP system profile parameter ldap/saproot.
SAP MMC
The SAP MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from
a central location. It is automatically set up when you install an SAP system on Windows. If the SAP
system has been prepared correctly, the SAP MMC presents and analyzes system information that it
gathers from various sources, including the Active Directory.
Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can
read system information straight from the directory that automatically registers changes to the system
2009-04-30 PUBLIC 123/162

landscape. As a result, up-to-date information about all SAP application servers, their status, and
parameter settings is always available in the SAP MMC.
If you need to administer distributed systems, we especially recommend that you use the SAP MMC
together with Active Directory services. You can keep track of significant events in all of the systems
from a single SAP MMC interface. You do not need to manually register changes in the system
configuration. Instead, such changes are automatically updated in the directory and subsequently
reflected in the SAP MMC.
If your SAP system is part of a heterogeneous SAP system landscape that comprises systems or instances
both on UNIX and Windows operating systems, you can also use the SAP MMC for operating and
monitoring the instances running on UNIX.
SAP MC
The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems from a
central location. If the SAP system has been prepared correctly, the SAP MC presents and analyzes
system information that it gathers from various sources, including generic LDAP Directory.
Integrating a generic LDAP Directory as a source of information has advantages for the SAP MC. It can
read system information straight from the directory that automatically registers changes to the system
landscape. As a result, up-to-date information about all SAP application servers, their status, and
parameter settings is always available in the SAP MC.
Configuration Tasks for LDAP Directories
This section describes the configuration tasks you have to perform for the Active Directory or other
(generic) LDAP directories.
Configuration Tasks for Active Directory
To enable an SAP system to use the features offered by the Active Directory, you must configure the
Active Directory so that it can store SAP system data.
To prepare the directory, you use SAPinst to automatically:
-Nì¡£ Extend the Active Directory schema to include the SAP-specific data types
-Nì¡£ Create the domain accounts required to enable the SAP system to access and modify the Active
Directory. These are the group SAP_LDAP and the user sapldap.
-Nì¡£ Create the root container where information related to SAP is stored
-Nì¡£ Control access to the container for SAP data by giving members of the SAP_LDAP group permission
to read and write to the directory
You do this by running SAPinst on the Windows server on which you want to use Active Directory
Services and choosing <Your SAP product> Software Life-Cycle Options LDAP Registration Active
Directory Configuration . For more information about running SAPinst on Windows, see the
documentation Installation Guide — <Your SAP product> on Windows: <Database>.
124/162 PUBLIC 2009-04-30

6.2 Setting up Swap Space for AIX
NOTE
You have to perform the directory server configuration only once. Then all SAP systems that
need to register in this directory server can use this setup.
Configuration Tasks for Generic LDAP Directories
To configure other LDAP directories, refer to the documentation of your directory vendor.
Enabling the SAP System LDAP Registration
Once you have correctly configured your directory server, you can enable the LDAP registration of the
SAP system by setting some profile parameters in the default profile.
To do this, run SAPinst once for your system and choose <Your SAP product> Software Life-Cycle Options
LDAP Registration LDAP Support
If you use a directory server other than Microsoft Active Directory and/or non-Windows application
servers, you have to store the directory user and password information by using ldappasswd
pf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and is therefore
valid for all application servers. After restarting all application servers and start services, the system is
registered in your directory server. The registration protocols of the components are dev_ldap*. The
registration is updated every time a component starts.
6.2 Setting up Swap Space for AIX

Procedure
1. Check the allocated swap space:
1. To start the System Management Interface Tool (SMIT), enter the following command:
smitty.
2. Perform one of the following steps:
Lz(Ô„ Choose Physical & Logical Storage Logical Volume Manager Paging Space List All Paging
Spaces
Lz(Ô„ Enter this command:
lsps -a
2. Check if there is sufficient swap space (see Hardware and Software Requirements [page 17]).
3. If required, add another paging space using smitty:
1. Choose Physical & Logical Storage Logical Volume Manager Paging Space Add Another Paging
Space
A list of volume group names is displayed.
2. Select a volume group.
3. Enter the size of paging space in logical partitions.
4. Set Start using this paging space NOW ? to YES.
5. Set Use this paging space each time the system is RESTARTED to YES.
2009-04-30 PUBLIC 125/162

6.3 Creating AIX Groups and Users
6. To exit smitty, choose F10 .

7. To check the results, follow the procedure described above in step 1.
6.3 Creating AIX Groups and Users

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

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

5. Change field Soft DATA segment to -1.
6. Change field Soft STACK size to -1.
You must make sure that the system-wide default HARD values are not explicitly defined to be
lower than the values given above. Check the file /etc/security/limits under the default:
126/162 PUBLIC 2009-04-30

6.4 Setting Up File Systems and Raw Devices for AIX
stanza. If they are not explicitly set, then the values are as shown in the table at the top of the
file.
Checking the Operating System

2. Choose System Environments Change/Show Characteristics of Operating System .
3. Change Maximum number of PROCESSES allowed per user to 500.
4. To exit SMIT, choose F10 .
More Information
For more information about the users and groups that are created either by SAPinst or manually, see
Creating Operating System Users [page 53].
6.4 Setting Up File Systems and Raw Devices for AIX

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

4. Enter mount point as given in the file system list files.
2009-04-30 PUBLIC 127/162

6.5 Dialog Instance Installation for an Upgraded System only: Updating Profiles
EXAMPLE
/sapdb/<SAPSID>/sapdata
5. Set mount automatically to yes.
Setting up Raw Devices
1. Create volume group.

2. Create logical volume:
2. Choose Physical & Logical Storage Logical Volume Manager Logical Volumes Add a Logical
Volume .
3. Enter volume group name.
4. Enter logical volume name (for example: lvsap02).
5. Enter the number of logical partitions.
6. Set the logical volume TYPE to r3data and press ENTER.
7. To exit SMIT, choose F10 .
NOTE
The logical volume can be accessed through /dev/r<name of raw log.vol>.
EXAMPLE
A logical volume called lvsap02 points to the device name /dev/rlvsap02.

3. Accessing raw devices:
It is not necessary to create a link to access the volume, because SAPinst creates the links.
6.5 Dialog Instance Installation for an Upgraded System only:

Updating Profiles
You only need to perform the Procedure further below if you want to install a dialog instance and you
have already performed the following steps:
1. You upgraded your SAP Solution Manager system from an earlier source release to a target release
lower than SAP Solution Manager 7.0.
2. You installed Enhancement Package 1 with the SAP Enhancement Package Installer.
Procedure
1. On the SAP Global host, go to folder /<sapmnt>/<SAPSID>/profile.
NOTE
SAP system profiles are named as follows:

Instance profiles: <SAPSID>_<INSTANCE_ID>_<hostname>.pfl
Start profiles: START_<INSTANCE_ID>_<hostname>.pfl
128/162 PUBLIC 2009-04-30

6.5 Dialog Instance Installation for an Upgraded System only: Updating Profiles
2. Make sure that the parameter DIR_CT_RUN, if set, has identical values in the instance profile and
the start profile of the central instance:
›Ñk*‘ If it is set in the instance profile, it must also be set in the start profile.
›Ñk*‘ If it is not set in the instance profile, it must not be set in the start profile either.
3. Edit the default profile DEFAULT.PFL by setting rdisp/msserv_internal to a free port number.
NOTE
Note that for AIX 5.3, the port 39<SCS_instance number> is used by the NIM server of AIX.
EXAMPLE
DEFAULT.PFL
Before the change:
...
rdisp/msserv = sapms<SAPSID>
...
After the change:
...
rdisp/msserv = sapms<SAPSID>
rdisp/msserv_internal = <free port number>
...
4. Edit the instance profile of the central services instance (SCS) and do the following:
›ÑkÅªË^öAäÚs×ìQ“ÊÓ¾ø8�µœMÊcæ“7¢yÚ”€Qüý°»</ø@šït±Ïšj°ÌŁ
NOTE
In a high-availability system, also do this for the instance profile of the ABAP central services
instance (ASCS).
›ÑkÏªË^þA½Ú<×üQW“ƒÓ�ø˛�µœÊYæ±7Ñy¢”ÁQ˛ýì
›Ñk*‘ Set rdisp/msserv to 0.

›Ñk*‘ Set rdisp/msserv_internal to the port number assigned to rdisp/msserv.
EXAMPLE
Instance profile of the central services instance:

Before the change:
...
rdisp/msserv = 4711
...
After the change:
...
rdisp/msserv = 0
rdisp/msserv_internal = 4711
...
5. Restart all SAP services and instances of your SAP system.
2009-04-30 PUBLIC 129/162

6.6 Mounting a CD / DVD for AIX
6.6 Mounting a CD / DVD for AIX

NOTE
<medium-mountdir> refers to either <cd-mountdir> or <dvd-mountdir>.
Use the following procedure to mount a CD / DVD:
Procedure
2. Add a CD / DVD file system.
2. Choose Physical & Logical Storage File Systems Add / Change / Show / Delete File Systems CDROM
File Systems Add a CDROM File System .
3. To obtain a list of device names, choose F4 .
Select a device name.
4. Enter the mount point <medium-mountdir>.
EXAMPLE
<medium-mountdir> is /sapcd
5. Choose ENTER .
3. Mount the CD / DVD as follows:
NOTE
Alternatively, you can mount the CD / DVD manually with the following command: mount
-v cdrfs -r /dev/cd0 /sapcd.

2. Choose Physical & Logical Storage File Systems Mount a File System .
3. Place the cursor on File System Name and choose F4 .
4. Select the CD / DVD device /dev/cd0.
5. Place the cursor on field Directory over which to mount and choose F4 .
6. Select /sapcd.
7. Place the cursor on field Type of File System and choose F4 .
8. Select cdrfs.
9. Change Mount as Read Only system to YES
10. Choose ENTER .
6.7 Exporting and Mounting Directories via NFS for AIX

There are two ways of mounting directories via NFS:
130/162 PUBLIC 2009-04-30

6.7 Exporting and Mounting Directories via NFS for AIX
×ëSäø˜ Manually
×ëSäø˜ Using the System Management Interface Tool (SMIT)
Procedure
To mount directories via NFS from the host where the directory to be mounted resides:
2. To start NFS services at the host where the directory to be mounted resides, use SMIT as follows:
2. Choose Communications Applications and Services NFS Network File System (NFS) Configure NFS
on this System Start NFS .
3. In the line Start NFS now, on system restart or both, enter: both.
4. Choose ENTER .
3. Export the directory (for example <sapmnt>/<SAPSID>/exe) with read or read-write access for the
host where the additional instance runs:
2. Choose Communications Applications and Services NFS Network File System (NFS) Add a Directory
to Exports List .
3. Enter the path of the directory that you want to export (for example, <sapmnt>/<SAPSID>/
exe).
4. Choose export mode (use read-write or read-only as required by SAP). In the line HOSTS allowed
root access, enter the name of the host where the additional instance runs. For security reasons,
this root access should be disabled after the installation.
5. In the line Export directory now, system restart or both, enter: both
6. Choose ENTER .
4. Create the mount point at the host where the additional instance runs: /usr/bin/mkdir
5. Mount the directory on the host where the additional instance runs.
2. Choose Communications Applications and Services NFS Network File System (NFS) Add a File System
for Mounting .
3. Enter the path name of the mount point.
4. Enter the path name of the remote directory (the directory of the central instance).
5. Enter the host where the remote directory resides.
6. Set Mount now, add entry to /etc/filesystems or both to both.
7. Set /etc/filesystems entry will mount the directory on system RESTART to yes.
8. Change Mount file system soft or hard to soft and press ENTER.
2009-04-30 PUBLIC 131/162

6.8 Additional Information About SAPinst
6. If you exported the directory with read-write access, check if the host where the future additional
instance is to run has write access to directory <sapmnt>/<SAPSID>/exe using the following
commands:
cd <sapmnt>/<SAPSID>/exe
touch test (create a file called test)
ls -l test (check if file test is created)
rm test (remove the file test)

The following sections provide additional information about SAPinst:
¾ÑÓðEá Using SAPinst GUI [page 132]
¾ÑÓðEá Interrupted Installation with SAPinst [page 133]
¾ÑÓðEá Performing a Remote Installation with SAPinst [page 135]
¾ÑÓðEá Starting SAPinst GUI Separately [page 136].
¾ÑÓðEá Entries in the Services File Created by SAPinst [page 138]
6.8.1 Using SAPinst GUI

The following table shows the most important functions that are available in SAPinst GUI:
SAPinst GUI Functions
Input Type Label Description
Function key F1 Displays detailed information about each input
parameter
Menu option File Exit Stops the SAPinst GUI, but SAPinst and the GUI server
continue running
NOTE
If you need to log off during the installation from
the host where you control the installation with
SAPinst GUI, the installation continues while
you are logged off. You can later reconnect to
the same SAPinst installation from the same or
another host.
For more information, see Starting SAPinst GUI
Separately [page 136].
Menu option SAPinst Log Browser Displays the Log Viewer dialog
This dialog enables you to access the following log files
directly:
¾ÑÓðEá Installation log (sapinst_dev.log)
¾ÑÓðEá Log files from the SAPinst GUI server
132/162 PUBLIC 2009-04-30

Input Type Label Description

These log files might help you during troubleshooting with
SAPinst [page 150].
Menu option SAPinst Cancel Cancels the installation with the following options:
Ó�3¦_³ Stop
Stops the installation (SAPinst GUI, SAPinst, and
the GUI server) without further changing the
installation files
You can restart and continue the installation
later from this point.
Ó�3¦_³ Continue
Continues the installation
Message button Retry Performs the installation step again (if an error has
occurred)
Message button Stop Stops the installation without further changing the
installation files
You can continue the installation later from this
point.
Message button Continue Continues with the option you chose previously
6.8.2 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:
Ó�3¦_³ An error occurred during the Define Parameters or Execute phase:
SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses
and a dialog box appears. The dialog box contains a short description of the choices listed in the
table below as well as a path to a log file that contains detailed information about the error.
Ó�3¦_³ You interrupted the installation by choosing Cancel in the SAPinst menu.
The following table describes the options in the dialog box:
Option Definition
Retry SAPinst retries the installation from the point of failure without repeating
any of the previous steps.
This is possible because SAPinst records the installation progress in the
keydb.xml file.
We recommend that you view the entries in the log files, try to solve the
problem, and then choose Retry.
If the same or a different error occurs, 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.
2009-04-30 PUBLIC 133/162

Option Definition
View Log Access installation log files.
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
or database.
2. Mount your Installation Master DVD.
NOTE
Mount the DVD locally. We do not recommend using Network File System (NFS).
3. Start SAPinst using the following commands:
cd <Installation_Master_DVD>/IM_<OS>
./sapinst
4. From the tree structure in the Welcome screen, select the installation option that you want to
continue and choose Next.
NOTE
If there is only 1 component to install, the Welcome screen does not appear.
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 Option SAPinst does not continue the interrupted installation option. Instead, it
moves the content of the old installation directory and all installation-
specific files to a backup directory. Afterwards, you can no longer continue
the old installation option.
For the backup directory, the following naming convention is used:
<log_day_month_year_hours_minutes_seconds>.
EXAMPLE
log_01_Oct_2008_13_47_56
CAUTION
SAPinst moves all the files and folders to a new log directory, even if
these files and folders are owned by other users. If there are any
134/162 PUBLIC 2009-04-30

Alternative Behavior
processes currently running on these files and folders, they might no
longer function properly.
Continue with the Old Option SAPinst continues the interrupted installation option from the point of
failure.
6.8.3 Performing a Remote Installation with SAPinst

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the
SAPinst GUI server run on the remote host, and SAPinst GUI client runs on the local host. The local
host is the host from which you control the installation with the SAPinst GUI client. The GUI client
connects using a secure SSL connection to the GUI server and the GUI server connects to SAPinst.
Alternatively you can use an X server for Microsoft Windows or other remote desktop tools such as
VNC Viewer or NX Server / NX Client – offered by various vendors or open source – for remote access
to SAPinst GUI on Windows workstations. We recommend that you use the Hummingbird Exceed X
Server, which we use to validate installations with SAPinst. For more information, see SAP Note
1170809.
CAUTION
The behavior of SAPinst, GUI server and GUI client has changed compared to previous versions.
SAP no longer delivers any JCE policy archives within the SAP Java Virtual Machine (SAP JVM).
You have to download the required Java Cryptography Extension (JCE) policy zip file from SAP
on the remote host. For more information, see SAP Note 1238121.
Prerequisites
v0'ó+ The remote host meets the prerequisites as described in Prerequisites in Running SAPinst [page 83].
v0'ó+ Both computers are in the same network and can ping each other.
To test this:
1. Log on to your remote host and enter the command ping <local host>.
2. Log on to the local host and enter the command ping <remote host>.
Procedure
1. Log on to your remote host as user root.
CAUTION
or database.
2. Mount the Installation Master DVD.
3. Download the JCE policy zip file from SAP as described in SAP Note 1240081.
4. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive
as follows:
2009-04-30 PUBLIC 135/162

Shell Used Command

Bourne shell (sh) JCE_POLICY_ZIP=<policy zip archive>
export JCE_POLICY_ZIP
C shell (csh) setenv JCE_POLICY_ZIP <policy zip archive>
Korn shell (ksh) export JCE_POLICY_ZIP=<policy zip archive>
5. Change to the directory of the sapinst executable and start SAPinst without GUI using the
following commands:
cd <mountpoint_of_Installation_Master_DVD>/IM_<OS>
./sapinst -nogui
For more information about SAPinst, see Running SAPinst [page 83].
SAPinst now starts and waits for the connection to the SAPinst GUI client. 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.
6. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 136].
6.8.4 Starting the SAPinst GUI Separately

You use this procedure to start the SAPinst GUI client separately. You might need to start the GUI
client separately in the following cases:
o•ž%G, 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.
o•ž%G, You want to perform a remote installation [page 135].
If the GUI client runs on a different host from SAPinst and the GUI server, you have to start the
GUI client separately on the local host.
CAUTION
The behavior of SAPinst has changed compared to previous versions. SAP no longer delivers any
JCE policy archives within the SAP JVM. You have to download the required JCE policy zip file
from SAP on the local host. For more information, see SAP Note 1238121.
Procedure
Starting the GUI Client on Windows
1. Log on as a member of the local administrators group.

by entering the following command:
set JCE_POLICY_ZIP=<policy zip archive>
136/162 PUBLIC 2009-04-30

4. Insert the SAP Installation Master DVD into your DVD drive.
5. Change to the directory of the sapinst executables:
<DVD drive>:\IM_WINDOWS_<platform>
NOTE
If you want to start the GUI client on a Windows 32-bit operating system, change to the
following directory:
<Installation_Master_DVD>\IM_WINDOWS_I386
6. Start the GUI client by double-clicking sapinstgui.exe
The GUI client starts and tries to connect to the GUI server and SAPinst, using the local host as
default.
If SAPinst and the GUI server are running on another host, the GUI client cannot connect and the
SAP Installation GUI Connection dialog appears.
In this case, enter the name of the host on which SAPinst is running and choose Log on.
The first screen of the installation appears and you can perform the remote installation from your
local host.
NOTE
Optionally you can start sapinstgui.exe with the following parameters:

ò¿`%¸» host=<host name>, where <host name> is the host name of the installation host
ò¿`%¸» port=<nr>, where <nr> is the port number for the connection to the GUI server
ò¿`%¸» -accessible enables accessibility mode
Example: sapinstgui host=lsi1209 port=3000 -accessible
ò¿`%¸» -h displays a list of all available parameters
Starting the GUI Client on UNIX

CAUTION
or database.
as follows:
Shell Used Command
Bourne shell (sh) JCE_POLICY_ZIP=<policy zip archive>
export JCE_POLICY_ZIP
C shell (csh) setenv JCE_POLICY_ZIP <policy zip archive>
Korn shell (ksh) export JCE_POLICY_ZIP=<policy zip archive>
4. Mount your Installation Master DVD.
2009-04-30 PUBLIC 137/162

NOTE
Mount the DVD locally. We do not recommend that you use Network File System (NFS).
5. Change to the directory of the sapinst executables:
<mountpoint_of_Installation_Master_DVD>/IM_<OS>
NOTE
If you want to start the GUI client on a Linux 32–bit platform, change to the following
directory:
<mountpoint_of_Installation_Master_DVD>/IM_LINUX_I386
6. Start the GUI client by executing ./sapinstgui
The GUI client starts and tries to connect to the GUI server and SAPinst, using the local host as
default.
If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and the
SAP Installation GUI Connection dialog appears.
In this case, enter the name of the host on which SAPinst is running and choose Log on.
The first screen of the installation appears and you can perform the remote installation from your
local host.
NOTE
Optionally, you can start sapinstgui with the following parameters:

"⁄·¶³¯ host=<host name>, where <host name> is the host name of the installation host
"⁄·¶³¯ port=<nr>, where <nr> is the port number for the connection to the GUI server
"⁄·¶³¯ -accessible enables accessibility mode
Example: ./sapinstgui host=lsi1209 port=3000 -accessible
"⁄·¶³¯ -h displays a list of all available parameters
6.8.5 Entries in the Services File Created by SAPinst

After the installation has finished successfully, SAPinst has created the following entries in /etc/
services:
sapdpXX = 32XX/tcp
sapdpXXs = 47XX/tcp
sapgwXX = 33XX/tcp
sapgwXXs = 48XX/tcp
sapms<SAPSID> = 36NN/tcp (unless you specified another value during the installation)
NOTE
"⁄·¶³¯ XX is the instance number. The ports are created for all instance numbers, regardless of which
instance number you specified during the installation.
138/162 PUBLIC 2009-04-30

6.9 Starting and Stopping SAP System Instances
NN is the number of the instance in which the message server runs. In a central or distributed
system, this is the central instance (DVEBMGS<nn>), in a high-availability system, this is the
ABAP central services instance (ASCS<nn>).
For more information about instance numbers, see the table SAP System Instances, Hosts, and
Ports in Basic SAP System Parameters [page 42].
¿ZšÚ&£ If there is more than 1 entry for the same port number, this is not an error.

You can start and stop SAP system instances and the Diagnostics Agent by using the SAP Management
Console (SAP MC) [page 139].
Apart from using the SAP Management Console (SAP MC) you can also use scripts to:
¿ZšÚ&£ Start or stop SAP system instances [page 143]
¿ZšÚ&£ Start or stop the Diagnostics Agent [page 145].
6.9.1 Starting and Stopping SAP System Instances Using the

SAP Management Console
You can start and stop all instances of your SAP system using the SAP Management Console (MC).
NOTE
If your newly installed SAP system is part of a heterogeneous SAP system landscape comprising
systems or instances on Windows platforms, you can also start and stop it from a Windows system
or instance using the Microsoft Management Console (SAP MMC).
For more information about handling the MMC, see:
Capability Solution Monitoring Monitoring in the CCMS SAP Microsoft Management Console: Windows
Prerequisites
¿ZšÚ&£ Make sure that the host where you want to start SAP MC meets the following requirements:
¿ZšÚ&Ì Java Runtime Environment (JRE) 5.0 is installed.
¿ZšÚ&Ì The browser supports Java.
¿ZšÚ&Ì The browser's Java plug-in is installed and activated.
¿ZšÚ&£ You have logged on to the host as user <sapsid>adm.
Procedure
Starting the Web-Based SAP Management Console
1. Start a Web browser and enter the following URL:
2009-04-30 PUBLIC 139/162

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

NOTE
If your browser displays a security warning message, choose the option that indicates that
you trust the applet.
2. Choose Start.
The SAP Management Console appears.
By default, the instances installed on the host you have connected to are already added in the SAP
Management Console.
NOTE
If the instances have not been added or if you want to change the configuration to display
systems and instances on other hosts, you have to register your system manually. This is
described in Registering Systems and Instances in the SAP Management Console below.
Starting and Stopping SAP System Instances

Starting SAP Systems or Instances
1. In the navigation pane, open the tree structure and navigate to the system node that you want to
start.
2. Select the system or instance and choose Start from the context menu.
3. In the Start SAP System(s) dialog box, choose the required options.
4. Choose OK.
The SAP MC starts the specified system or system instances.
NOTE
The system might prompt you for the credentials of the SAP system administrator. To
complete the operation, you must have administration permissions. Log in as user
<sapsid>adm.
Starting the Instances of a Distributed SAP System Separately
If you need to start the instances of an SAP system separately – for example when you want to start a
distributed or a high-availability system – proceed as follows:
1. Start the database instance.
2. Start the central services instance SCS<Instance_Number>.
140/162 PUBLIC 2009-04-30

•é*€lF¶7&Û–µýqhAUW–¦ðÿŁÚÂP¼Û3˚È9žªÖ›R¦£ÔÐGã¶IéOdnas
If your system is a high-availability system, first start the ABAP central services instance
ASCS<Instance_Number> and then start the Java central services instance
SCS<Instance_Number>.
•é*ªlF¶?&‡–úýahÛ@W¤¦ÕÿŁÚ„PƒÛ˚»9æª·hH
3. Start the central instance DVEBMGS<Instance_Number>.
4. Start dialog instances D<Instance_Number>, if there are any.
Stopping SAP Systems or Instances
1. Select the system or instance you want to stop and choose Stop from the context menu.
2. In the Stop SAP System(s) dialog box, choose the required options.
3. Choose OK.
The SAP MC stops the specified system or system instances.
NOTE
The system might prompt you for the SAP system administrator credentials. To complete
the operation, you must have administration permissions. Log in as user <sapsid>adm.
Similarly, you can start, stop, or restart all SAP systems and individual instances registered in the SAP
MC.
Stopping the Instances of a Distributed SAP System Separately
If you need to stop the instances of an SAP system separately – for example when you want to start a
distributed or a high-availability system – proceed as follows:
1. Stop dialog instances D<Instance_Number>, if there are any.
2. Stop the central instance DVEBMGS<Instance_Number>.
3. Stop the central services instance SCS<Instance_Number>.
•é*€lF¶7&Û–µýqhAUW–¦ðÿŁÚÂP¼Û3˚È9žªÖ›R¦£ÔÐGã¶IéOdnas
If your system is a high-availability system, first stop the Java central services instance
SCS<Instance_Number> and then stop the ABAP central services instance
ASCS<Instance_Number>.
•é*ªlF¶?&‡–úýahÛ@W¤¦ÕÿŁÚ„PƒÛ˚»9æª·hH
4. Stop the database instance.
Registering Systems and Instances in the SAP Management Console
You can extend the list of systems and instances displayed in the SAP MC, so that you can monitor and
administer all systems and instances from a single console. You can configure the SAP MC startup view
to display the set of systems and instances you want to manage.
Prerequisites
The SAP MC is started.
2009-04-30 PUBLIC 141/162

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

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

2. In the New System dialog box, enter the required data and deselect Always show all SAP Instances.
3. The SAP MC displays the SAP system node, the instance node, and the relevant database node in
a tree view in the navigation pane.
NOTE
To view all instances of the respective SAP system, select the relevant system node and choose
Add Application Server from the context menu.
Configuring the SAP MC View
bá�Š— You can choose the instances that the SAP MC displays automatically on startup:
1. In the Settings dialog box, select History.
2. In the right-hand pane, choose the instance you want the SAP MC to display on startup.
3. Choose the << button.
4. Choose Apply and then OK.
Similarly, you can remove instances from the startup configuration.
bá�Š— You can save the current configuration in a file:
1. Choose File Save Landscape .
2. In the Save dialog box, enter the required data.
3. Choose Save.
bá�Š— You can load a configuration from a file:
1. Choose File Load Landscape .
2. In the Open dialog box, select the configuration you want to load.
3. Choose Open.
More Information
For more information about the SAP Management Console, see:
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution
Monitoring Monitoring in the CCMS SAP Management Console
142/162 PUBLIC 2009-04-30

6.9.2 Starting and Stopping SAP System Instances Using

Scripts
You can start and stop SAP system instances by running the startsap and stopsap scripts.
You can also use the SAP Management Console (SAP MC) to start or stop the instances of the SAP
system (see Starting and Stopping SAP System Instances Using the SAP Management Console [page 139]).
Prerequisites
z‡C9J You have checked the default profile /<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameter
login/system client and set the value to the correct production system client. For example, the
entry must be login/system_client = 001 if your production client is 001.
z‡C9J You have checked the settings for Java Virtual Machine parameters as described in SAP Note
723909.
z‡C9J You have logged on to the SAP system hosts as user <sapsid>adm.
z‡C9J 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.
z‡C9J 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
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>.
z‡¬˝—ñ;ë+˜0ßfBööD=˚™¥!Ó(˙´Æ—WG[I%0VdþUÅ@˜‰™fi®¢‹‰=fi@
The instance name of the ABAP central services instance is ASCS<Instance_Number>.

z‡¦˝—ñ3ër˜�ßvBPöºD˝˚&™¥!š(!´ú—$G#ID0·dH
Procedure
Starting SAP System Instances
z‡C9J 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.
2009-04-30 PUBLIC 143/162

NOTE
You can start the database and SAP system separately by entering the following commands:
startsap DB
startsap R3 <instance ID of central services instance>
startsap R3 <instance ID of central instance>
startsap R3 <instance ID of dialog instance>
Make sure that you always start the database first because otherwise the other instances cannot
start.
NOTE
You can also use the parameter J2EE, which is a synonym for the parameter R3.
For ABAP+Java systems, you can enter either the command startsap R3 or startsap
J2EE to start the SAP instance comprising both ABAP and Java.
Ô“ãy 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 instances, enter the following on the relevant host:
startsap R3 <instance ID of dialog instance>
NOTE
Make sure that the SAP system and associated J2EE Engines are up and running before you
start or restart dialog instances and their J2EE Engines.
Stopping SAP System Instances
Ô“ãy 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.
144/162 PUBLIC 2009-04-30

For ABAP+Java systems, you can enter either the command stopsap R3 or stopsap J2EE to
stop the SAP instance comprising both ABAP and J2EE.
L)Ô)7˛ 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
CAUTION
Make sure that no SAP instance is running before you enter stopdb on a standalone database
server. No automatic check is made.
6.9.3 Starting and Stopping the Diagnostics Agent Using

Scripts
You can start and stop the Diagnostics Agent by running the smdstart and smdstop scripts.
The local versions of these scripts are located in /usr/sap/<SMDSID>/J<instance_number>/script.
The global versions of these scripts are located in /usr/sap/<SMDSID>/exe.
NOTE
You can only start or stop the Diagnostics Agent separately. It is not started or stopped
automatically with the SAP system.
You can also use the SAP Management Console (SAP MC) to start or stop the Diagnostics Agent (see
Starting and Stopping SAP System Instances Using the SAP Management Console [page 139]).
Prerequisites
You have logged on to the central instance or dialog host as user <smdsid>adm.
Procedure
Starting a Diagnostics Agent Locally
1. Change to the following directory:

/usr/sap/<SMDSID>/J<Instance_Number>/script
2. To start the Diagnostics Agent locally, enter this command:
./smdstart.sh
Starting Diagnostics Agents Globally
To start Diagnostics Agents globally, enter this command:
2009-04-30 PUBLIC 145/162

6.10 Creating a User for LDAP Directory Access
smdstart <SMDSID> <Instance_Number>
EXAMPLE
smdstart SMD 98
NOTE
You do not have to specify the <SMDSID> if there is only one Diagnostics Agent system on this
host.
Stopping a Diagnostics Agent Locally
1. Change to the following directory:

/usr/sap/<SMDSID>/J<instance_number>/script
2. To stop the Diagnostics Agent locally, enter this command:
./smdstop.sh
Stopping Diagnostics Agents Globally
To stop Diagnostics Agents globally, enter this command:

smdstop <SMDSID> <Instance_Number>
EXAMPLE
smdstop SMD 98
NOTE
You do not have to specify the <SMDSID> if there is only one Diagnostics Agent system on this
host.
6.10 Creating a User for LDAP Directory Access

If you use LDAP directory services, you have to set up a user with a password on the host where the
SAP system is running. This permits the SAP system to access and modify the LDAP directory.
For more information, see Preparing the Active Directory in the Windows installation guide for your SAP
system solution and database.
Prerequisites
During the SAP instance installation you chose to configure the SAP system to integrate LDAP services.
Procedure
1. Log on as user <sapsid>adm.
2. Enter:
ldappasswd pf=<path_and_name_of_instance_profile>
3. Enter the required data.
146/162 PUBLIC 2009-04-30

6.11 Accessing the SAP Java Documentation
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.11 Accessing the SAP Java Documentation

Here you can find information about the configuration and administration of the J2EE Engine and
about SAP Java technology in the SAP Library.
Procedure
1. Go to http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1)
SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java
Technology .
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:
¹˛⁄b*Ò Java cluster architecture including central services, load
balancing, and high availability.
¹˛⁄b*Ò J2EE Engine system architecture
¹˛⁄b*Ò SAP NetWeaver Java development infrastructure, including the
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.
Administration Manual This manual describes how to administer the SAP system, focusing on the
J2EE Engine. It contains information on:
¹˛⁄b*Ò System landscape administration
¹˛⁄b*Ò Software life-cycle management
NOTE
This part of the manual contains important information about:
¹˛⁄b*½ Installation information
¹˛⁄b*½ System Landscape Directory (SLD)
¹˛⁄b*½ Software Lifecycle Manager (SLM)
¹˛⁄b*½ Java Support Package Manager
¹˛⁄b*½ Administration of SAP NetWeaver Java Development
Infrastructure (JDI)
¹˛⁄b*Ò J2EE Engine and J2EE Engine security
¹˛⁄b*Ò Supportability and performance management
¹˛⁄b*Ò Administration and configuration of Web Dynpro runtime
environment
¹˛⁄b*Ò Administration of the XML Data Archiving Service (XML DAS)
2009-04-30 PUBLIC 147/162

6.12 Initial Technical Configuration for Adobe Document Services
Manual Contents
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 more information about troubleshooting for the J2EE Engine, see the J2EE Engine Problem Analysis
Guide at:
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP
NetWeaver Problem Analysis Guide (PAG) Usage Type Application Server Java J2EE Engine Problem Analysis
Scenarios
6.12 Initial Technical Configuration for Adobe Document

Services
SAPinst automatically performs some initial technical configuration steps for Adobe Document
Services (ADS) during the installation.
However, you might have to perform these steps manually if you want to change existing parameters
or if you want to set additional parameters.
SAPinst performs the following steps:
‰AÎÍD SAPinst creates user ADSUser in AS ABAP for basic authentication and assigns it to group
ADSCallers.
For more information about this user, see Ensuring User Security [page 96].
‰AÎÍD SAPinst creates user ADSUser in AS Java for basic authentication and assigns it to group
ADSCallers.
For more information about this user, see Ensuring User Security [page 96].
‰AÎÍD SAPinst creates service user ADS_AGENT in the ABAP Environment.
‰AÎÍD SAPinst creates an ABAP connection for basic authentication.
‰AÎÍD SAPinst creates destination service FP_ICF_DATA_<SAPSID>.
‰AÎÍD SAPinst sets up basic authentication in the Java environment.
You can find a detailed description of how to perform these steps manually in the SAP Library at:
NetWeaver Library Technology Consultant's Guide Business Task Management Adobe Document Services
148/162 PUBLIC 2009-04-30

6.13 Initial Technical Configuration for the System Landscape Directory (SLD)
(Configuration) Adobe Document Services Configuration Guide Configuring the Web Service Securing Access to the
Web Service Configuration of the Web Service for Basic Authentication
More Information
The Adobe Document Services Configuration Guide is also available in PDF form at:
http://sdn.sap.com/irj/sdn/adobe Installation & Configuration SAP Interactive Forms – Configuration
Guides Configuration Guide for SAP Interactive Forms by Adobe
6.13 Initial Technical Configuration for the System

Landscape Directory (SLD)
SAPinst automatically performs some initial technical configuration steps for the System Landscape
Directory (SLD) during the installation:
Â_Í˚P$ If you chose the option Register in existing central SLD, SAPinst automatically configures the connection
of the system being installed to an existing central System Landscape Directory (SLD).
Â_Í˚P$ If you chose the option Configure a local SLD, SAPinst automatically sets up and configures a local
System Landscape Directory (SLD) during the installation.
CAUTION
We strongly recommend that you set up a local SLD on the SAP Solution Manager system
with connection and replication from the productive SLD instances in your existing
landscape. For more information, see System Landscape Directory [page 33].
However, you might have to perform these steps manually if you want to change existing parameters
or if you want to set additional parameters.
SAPinst performs the following steps:
Â_Í˚P$ SAPinst configures SLD security roles.
Â_Í˚P$ SAPinst configures server and persistence parameters.
Â_Í˚P$ SAPinst performs the initial data import.
Â_Í˚P$ SAPinst configures the SLD bridge.
You can find a detailed description of how to perform these steps manually in the documentation Post
Installation Guide – System Landscape Directory of SAP NetWeaver 7.0 at http://service.sap.com/
installNW70 Installation Configuration .
More Information
Â_Í˚P$ For more information about working with and configuring the SLD, see the SAP Library at:
Software Life Cycle Management System Landscape Directory
More documentation is also available at http://www.sdn.sap.com/irj/sdn/nw-sld.
Â_Í˚P$ For more information about security and on the role concept in the SLD, see the SAP Library at:
2009-04-30 PUBLIC 149/162

6.14 Heterogeneous SAP System Installation

SAP NetWeaver Library Administrator’s Guide SAP NetWeaver Security Guide Security Aspects for System
Management Security Guide for the SAP System Landscape Directory
ÉÝ¥ãì± For more information about the configuration of SLD in the context of root cause analysis, see the
Root Cause Analysis Installation and Upgrade Guide, which you can find at:
http://service.sap.com/diagnostics End-to-End Root Cause Analysis Media Library
6.14 Heterogeneous SAP System Installation

This section provides information on the installation of an SAP system in a heterogeneous system
landscape. “Heterogeneous system landscape” means that application servers run on different
operating systems.
Procedure
See SAP Note 1067221 for information on
ÉÝ¥ãì± supported combinations of operating systems and database systems,
ÉÝ¥ãì± how to install an application server on Windows in a heterogeneous (UNIX) SAP system
environment,
ÉÝ¥ãì± heterogeneous SAP system landscapes with different UNIX operating systems.
6.15 Troubleshooting
The following sections describe the steps that you need to perform manually if SAPinst fails:
ÉÝ¥ãì± Troubleshooting with SAPinst [page 150]
6.15.1 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.
If an error occurs, SAPinst:
ÉÝ¥ãì± Stops the installation.
ÉÝ¥ãì± Displays a dialog informing you about the error.
Procedure
1. To view the log file, choose View Logs.
2. If an error occurs during the Define Parameters or Execute phase, do either of the following:
ÉÝ¥ãì± Try to solve the problem
ÉÝ¥ãì± Abort the installation by choosing Cancel in the SAPinst menu.
For more information, see Interrupted Installation with SAPinst [page 133].
150/162 PUBLIC 2009-04-30

6.16 Deleting an SAP System
ê7Óôt After resolving the problem, you can 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.
ê7Óôt If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current
<user_home> directory.
ê7Óôt If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI
as described in Starting SAPinst GUI Separately [page 136].
ê7Óôt If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote
Access of SAPinst GUI on Windows Workstations and you experience display problems such
as missing repaints or refreshes, contact your X Server vendor. The vendor can give you
information about whether this X Server supports Java Swing-based GUIs and also tell you
about further requirements and restrictions. See also SAP Note 1170809.
4. 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.
6.16 Deleting an SAP System

This section describes how to delete a single instance, a standalone engine, or a complete SAP system
with the Uninstall option of SAPinst.
NOTE
We recommend that you delete an SAP system with SAPinst. However, you can also delete an SAP
system manually. For more information, see SAP Note 1229586.
Prerequisites
ê7Óôt You are logged on as user root.
ê7Óôt If the saposcol process on the host you are working on has been started from the SAP system you
want to delete, stop it using the command saposcol -k.
If there are other SAP systems on the host, log on as user <sapsid>adm of the other SAP system
and start saposcol from there using the command saposcol -l.
Procedure
1. Start SAPinst [page 83] and on the Welcome screen, choose:
<Your SAP product> Software Life-Cycle Options Uninstall Uninstall System / Standalone Engine / Optional
Standalone Unit
2. Follow the instructions in the SAPinst input dialogs.
2009-04-30 PUBLIC 151/162

6.17 Deleting a Diagnostics Agent
NOTE
For more information about the input parameters, place the cursor on the relevant field and
press F1 in SAPinst.
SAPinst first asks you which SAP instances you want to delete. Make sure that you delete the SAP
instances in the order as described below.
CAUTION
SAPinst only stops local instances automatically.

Before you delete the database instance of a distributed system make sure that you stop all
remaining instances. You must stop the instance with the message server only after having
entered all SAPinst parameters for the deletion of the database instance.
çbâ¶Ö* If you want to delete a central system (all instances reside on the same host), you can do this
in one SAPinst run.
1. Delete the SAP system.
2. Choose whether you want to drop the entire database or only one or more database
schemas. If you drop the entire database, SAPinst also asks whether you want to remove
çbâ¶Ö* If you want to delete a distributed or high availability system, you have to run SAPinst to
delete the required instances locally on each of the hosts belonging to the SAP system in the
following sequence:
1. Dialog instances, if there are any
2. Central instance
3. Database instance
Choose whether you want to drop the entire database or only one or more database
schemas. If you drop the entire database, SAPinst also asks whether you want to remove
çbâ¶Ö* Java Central services instance (SCS)
çbâ¶Ö* çbâYóä|B0Ë�)#N0zOÐ¥è8˘œö?Õè^Â÷<&ÃØ¡-;¬¸y›˛²Ò¼mˇ¯³zŽý˜À
ABAP central services instance (ASCS)

çbâSóä|J0™�f#^0!Oœ¥#è˛˘œöqÕÒ^þ÷O&»ØÀ-Ú¬ä
çbâ¶Ö* The relevant directory structure on the global host

3. 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.
4. If you created the directories /usr/sap/<SAPSID> and /<sapmnt>/<SAPSID> as mount points, but
not as directories on the local file system, you have to remove them manually.

This procedure tells you how to delete the Diagnostics Agent with SAPinst.
152/162 PUBLIC 2009-04-30

NOTE
We recommend that you delete a Diagnostics Agent with SAPinst. However, you can also delete
a Diagnostics Agent manually. For more information, see SAP Note1229586.
Prerequisites
You are logged on as user root.
Procedure
1. Start SAPinst [page 83].
2. On the Welcome screen, choose:
<Your SAP product> Software Life-Cycle Options Uninstall Uninstall – Solution Manager Diagnostics
Agent
3. 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.
4. After the uninstall with SAPinst has finished successfully, you still have to manually delete the
<smdsid>adm user.
2009-04-30 PUBLIC 153/162

This page is left blank for documents
that are printed on both sides.
A Appendix
A.1 Online Information from SAP
A Appendix

More information is available online as follows.
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 also points you to further
documentation that might be relevant for you.
Documentation
Internet Address Available Documentation
http://service.sap.com/instguides Here you find all documentation about installation, update and
SAP Components SAP Solution Manager upgrade :
Release 7.0 EHP 1 Æ2ÃþTU Media List
Æ2ÃþTU Master Guide
Æ2ÃþTU Installation guides for the installation of SAP Solution
Manager 7.0 including SAP Enhancement Package 1 from
scratch
Æ2ÃþTU Update guides for the installation of SAP Enhancement
Package 1 on an existing SAP Solution Manager 7.0 system
Æ2ÃþTU Sizing Toolkit
Æ2ÃþTU Configuration Guide
Æ2ÃþTU Security Guide
http://service.sap.com/diagnostics Here you find all documentation about installation and upgrade
Root Cause Analysis Installation and Upgrade with of End-to-End Root Cause Analysis:
SOLMAN_SETUP Æ2ÃþTU Wily Introscope 8.0 Installation Guide
Æ2ÃþTU Diagnostics Agent Setup Guide
Æ2ÃþTU SAP Solution Manager 7.0 EhP1 Sizing Toolkit
Æ2ÃþTU Solution Concept and Design
Æ2ÃþTU User Administration Guide
http://service.sap.com/installnw70 Here you find all documentation about installation, update,
upgrade, and system copy for SAP NetWeaver:
Æ2ÃþTU Media List
Æ2ÃþTU Master Guide
Æ2ÃþTU Support Package Stack Guide
Æ2ÃþTU Installation guides for the installation of SAP NetWeaver 7.0
including SAP Enhancement Package 1 SR1 from scratch
Æ2ÃþTU Update guides for the installation of SAP Enhancement
Package 1 on an existing SAP NetWeaver 7.0 system
2009-04-30 PUBLIC 155/162

A Appendix
Internet Address Available Documentation

ZC]ıŸ System copy guides for SAP systems based on SAP
NetWeaver 7.0 including Enhancement Package 1 Support
Release 1
http://service.sap.com/ Here you find all documentation about how to manager your
solutionmanager entire SAP solution landscape with SAP Solution Manager.
General Quick Links

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

Help Portal
SAP Notes http://service.sap.com/notes
Forums, blogs, and general http://sdn.sap.com/irj/sdn/dbos

information related to all of the
supported databases and operating
system platforms
Product Availability Matrix (PAM) http://service.sap.com/pam
for supported operating system
releases
Release notes http://service.sap.com/releasenotes
Unicode SAP systems and their http://service.sap.com/unicode

availability
System sizing (Quick Sizer tool) http://service.sap.com/sizing
SAP NetWeaver capabilities http://sdn.sap.com/irj/sdn/netweaver
Life-cycle management for SAP http://sdn.sap.com/irj/sdn/lcm

NetWeaver
Landscape design for SAP http://sdn.sap.com/irj/sdn/landscapedesign
NetWeaver
Application management for SAP http://sdn.sap.com/irj/sdn/applicationmanagement
NetWeaver
High Availability http://sdn.sap.com/irj/sdn/ha
System Landscape Directory http://sdn.sap.com/irj/sdn/nw-sld
Software logistics for SAP http://sdn.sap.com/irj/sdn/softwarelogistics

NetWeaver
SAP NetWeaver operations http://sdn.sap.com/irj/sdn/operations
SAP NetWeaver Development http://sdn.sap.com/irj/sdn/nw-di

Infrastructure
Security for SAP NetWeaver http://sdn.sap.com/irj/sdn/security
Information on SAP Support http://service.sap.com/sp-stacks

Package Stacks
SAP Solution Manager http://service.sap.com/solutionmanager
Maintenance Optimizer http://service.sap.com/solman-mopz
End-to-End Root Cause Analysis http://service.sap.com/diagnostics
156/162 PUBLIC 2009-04-30

Typographic Conventions
Example Description
<Example> Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
http://www.sap.com Textual cross-references to an internet address
/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 £°ëŁL Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
£°ëŁL Cross-references to other documentation or published works
Example £°ëŁL Output on the screen following a user action, for example, messages
£°ëŁL Source code or syntax quoted directly from a program
£°ëŁL 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
2009-04-30 PUBLIC 157/162

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,
z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany
and in several other countries all over the world. All other product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
Disclaimer
Some components of this product are based on Java™. Any code change in these components may cause unpredictable and
severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.
Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or
altered in any way.
158/162 PUBLIC 2009-04-30

Legal Software Terms
Terms for Included Open Source Software

This SAP software contains also the third party open source software products listed below. Note that for these third party
products the following special terms and conditions shall apply.
1. This software was developed using ANTLR.
2. SAP License Agreement for STLport
SAP License Agreement for STLPort between
SAP Aktiengesellschaft
Systems, Applications, Products in Data Processing
69190 Walldorf, Germany
(hereinafter: SAP)
and
you
(hereinafter: Customer)
1. Subject Matter of the Agreement
1. SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++
library (STLport) and its documentation without fee.
2. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual
property laws, and to all of the terms and conditions of this Agreement.
3. The Customer may distribute binaries compiled with STLport (whether original or modified) without any
royalties or restrictions.
4. Customer shall maintain the following copyright and permissions notices on STLport sources and its
documentation unchanged: Copyright 2001 SAP AG
5. The Customer may distribute original or modified STLport sources, provided that:
˚7€Ó?Ý The conditions indicated in the above permissions notice are met;
˚7€Ó?Ý The following copyright notices are retained when present, and conditions provided in accompanying
permission notices are met:
Copyright 1994 Hewlett-Packard Company
Copyright 1996,97 Silicon Graphics Computer Systems Inc.
Copyright 1997 Moscow Center for SPARC Technology.
Copyright 1999,2000 Boris Fomitchev
Copyright 2001 SAP AG
Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is
hereby granted without fee, provided that the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company
makes no representations about the suitability of this software for any purpose. It is provided “as is” without
express or implied warranty.
Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is
copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no
representations about the suitability of this software for any purpose. It is provided “as is” without express or
implied warranty.
copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC
makes no representations about the suitability of this software for any purpose. It is provided “as is” without
express or implied warranty.
Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material
is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission
to use or copy this software for any purpose is hereby granted without fee, provided the above notices are
retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the
above notices are retained, and a notice that the code was modified is included with the above copyright notice.
2009-04-30 PUBLIC 159/162

copyright notice and this permission notice appear in supporting documentation. SAP makes no
representations about the suitability of this software for any purpose. It is provided with a limited warranty
and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and
warranty obligations only towards its customers and only referring to its modifications.
2. Support and Maintenance
SAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall
be not included.
All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions
and shall be subject to a separate contract.
3. Exclusion of warranty
As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the
STLport is error-free, without material defects or suitable for a specific application under third-party rights.
Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any
assurance of particular attributes.
4. Limited Liability
1. Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this
(i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by
SAP or (iii) if based on the failure of a guaranteed attribute.
2. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial
employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage
shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the
contract, due to the circumstances known to it at that point in time representing a typical transfer of the
software.
3. In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a
defect or lost profit.
4. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances
exceed EUR 5,000.
5. The Customer shall take adequate measures for the protection of data and programs, in particular by making
backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and
its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided
by observing this obligation.
6. The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against
employees or agents of SAP.
3. Adobe Document Services
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe
document services and Adobe LiveCycle Designer, see SAP Note 854621.
Documentation in the SAP Service Marketplace

You can find this document at the following address: https://service.sap.com/instguides
160/162 PUBLIC 2009-04-30

™x~ ™x~ SAP AG
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
™x~ ™x~
© Copyright 2009 SAP AG. All rights reserved.
™x~ ™x~ Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung
durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Installation GuideSAP Solution Manager 7.0 Including SAP Enhancement Package 1 On AIX MaxDB

Uploaded by

Document Information

Original Description:

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

Installation GuideSAP Solution Manager 7.0 Including SAP Enhancement Package 1 On AIX MaxDB

Uploaded by

Copyright:

Available Formats

Installation Guide

SAP Solution Manager 7.0 including SAP Enhancement Package

2/162 PUBLIC 2009-04-30

:*ßﬂ½ˇ˚-¬−−fFà‚»ÎFÞ4x’ Introduction ........................................................................................................... 7

:*ßﬂ½ˇ˚-¬−−fFà‚»ÎFÞ4xﬁ Planning ................................................................................................................... 11

:*ßﬂ½ˇ˚-¬−−fFà‚»ÎFÞ4x™ Preparation .............................................................................................................. 53

2009-04-30 PUBLIC 3/162

%6r®ªuŠùƒ×Łâ©ÆGdîÖ‚ì] Installation .............................................................................................................. 73

%6r®ªuŠùƒ×Łâ©ÆGdîÖ‚ì\ Post-Installation ..................................................................................................... 93

4/162 PUBLIC 2009-04-30

´&Œª\Øl‰v>ˇ§$ Â²Æ7ÙY£ Additional Information ........................................................................................ 121

´&Œª\Øl‰v>ˇ§$ Â²Æ7ÙYÔ Appendix .................................................................................................................. 155

2009-04-30 PUBLIC 5/162

6/162 PUBLIC 2009-04-30

šÀª¡eÂ Your operating system platform must be 64-bit.

2009-04-30 PUBLIC 7/162

Profiling for High Availability

1.1 New Features

SAP System Installation

8/162 PUBLIC 2009-04-30

Operating Systems and Platforms

2009-04-30 PUBLIC 9/162

1.2 SAP Notes for the Installation

SAP Notes for the Installation

10/162 PUBLIC 2009-04-30

2.1 Planning Checklist

2.2 Installation Options Covered by this Guide

High-availability system [page 13]

2009-04-30 PUBLIC 11/162

2.2.1 Central System

2.2.2 Distributed System

12/162 PUBLIC 2009-04-30

ó´âAŁtÔBÆ#LÀ{jŸJZfÞgµˇDistributed ABAP+Java System

2.2.3 High-Availability System

2009-04-30 PUBLIC 13/162

];›�?ënŒiÃÀ9~@ ˘ÞAßHigh-Availability System

2.2.4 Dialog Instance

Dialog Instance for a Central System

14/162 PUBLIC 2009-04-30

¡s7\Ùﬂ?˝¤%\Å‚²Ü† O‘®Dialog Instance for a Central System

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

Dialog Instance for a Distributed System

2009-04-30 PUBLIC 15/162

L‹º |ðÃ°Ø…õŽ"_b‰%ÐYê¿Dialog Instance for a Distributed System

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

Dialog Instance for a High-Availability System

16/162 PUBLIC 2009-04-30

Á™tnGÈ.ó¬Þ¨ªýÝ\˝ç÷ÚDialog Instance for a High-Availability System

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

2.3 Hardware and Software Requirements

Á™t‹b Contact your OS vendor for the latest OS patches.

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

2009-04-30 PUBLIC 17/162

2. Check the hardware and software requirements using:

2.3.1 Running the Prerequisite Checker in Standalone Mode

18/162 PUBLIC 2009-04-30

2.3.2 Requirements for a Central System

Ê2v“Ù€ AIX 5.3: http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?

Ê2v“Ù€ AIX 6.1: http://publib.boulder.ibm.com/infocenter/systems/index.jsp

2009-04-30 PUBLIC 19/162

20/162 PUBLIC 2009-04-30

Requirement Values and Activities

%6r®ªuŠùƒ×Łâ©ÆGdîÖ‚ì] Installation .............................................................................................................. 73

%6r®ªuŠùƒ×Łâ©ÆGdîÖ‚ì\ Post-Installation ..................................................................................................... 93

´&Œª\Øl‰v>ˇ§$ Â²Æ7ÙY£ Additional Information ........................................................................................ 121

´&Œª\Øl‰v>ˇ§$ Â²Æ7ÙYÔ Appendix .................................................................................................................. 155

];›�?ënŒiÃÀ9~@ ˘ÞAßHigh-Availability System

¡s7\Ùﬂ?˝¤%\Å‚²Ü† O‘®Dialog Instance for a Central System

L‹º |ðÃ°Ø…õŽ"_b‰%ÐYê¿Dialog Instance for a Distributed System

Á™tnGÈ.ó¬Þ¨ªýÝ\˝ç÷ÚDialog Instance for a High-Availability System

Disk space 0mı˘´ Space requirements for SAP data:

ûGÓk Store database data files and logs on different disks