Installation Guide

Web Dispatcher on UNIX

For SAP Systems Based on SAP NetWeaver 7.0 (2004s)

Target Audience
n Technology consultants
n System administrators

PUBLIC
Document version: 1.30 03/28/2008
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.00 4/10/2006 Initial version (SAP NetWeaver 2004s SR1)

1.10 12/4/2006 Updated version (SAP NetWeaver 2004s SR2)
1.20 3/9/2007 Updated version (Renaming SAP NetWeaver 2004s as SAP NetWeaver 7.0)
1.30 3/28/2008 Updated version (SAP NetWeaver 7.0 SR3)

2/58 PUBLIC 03/28/2008

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Web Dispatcher . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 6
1.3 Online Information from SAP . . . . . . . . . . . . . . . . . . 7
1.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Basic System Parameters . . . . . . . . . . . . . . . . . . . . 9

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1 Hardware and Software Requirements . . . . . . . . . . . . . . . 11
3.1.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 12
3.1.2 Requirements for AIX . . . . . . . . . . . . . . . . . . . . 13
3.1.3 Requirements for HP-UX . . . . . . . . . . . . . . . . . . . 16
3.1.4 Requirements for Linux . . . . . . . . . . . . . . . . . . . . 18
3.1.5 Requirements for Linux for System z . . . . . . . . . . . . . . . 20
3.1.6 Requirements for Solaris . . . . . . . . . . . . . . . . . . . . 22
3.1.7 Requirements for the Instance . . . . . . . . . . . . . . . . . 26
3.2 Creating Operating System Users Manually (Optional) . . . . . . . . . 26
3.3 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . 27
3.4 Installing the Java Runtime Environment . . . . . . . . . . . . . 28
3.5 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 29
3.5.1 Required Installation DVDs . . . . . . . . . . . . . . . . . . 29
3.5.2 Downloading Installation DVDs from SAP Service Marketplace (Optional) . 30

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 33
4.1 Running SAPinst . . . . . . . . . . . . . . . . . . . . . . 33
4.2 Performing a Remote Installation with SAPinst (Optional) . . . . . . . 37
4.3 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 38
4.4 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 40

Chapter 5 Post-Installation Activities . . . . . . . . . . . . . . . . . . 43

5.1 Logging on to the Web Dispatcher Management Console . . . . . . . . 43
5.2 Configuring and Operating the Web Dispatcher . . . . . . . . . . . 43

03/28/2008 PUBLIC 3/58

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 45
6.1 Mounting a CD / DVD for AIX . . . . . . . . . . . . . . . . . 45
6.2 Mounting a CD / DVD for HP-UX . . . . . . . . . . . . . . . . 46
6.3 Mounting a CD / DVD for Linux . . . . . . . . . . . . . . . . . 48
6.4 Mounting a CD / DVD for Linux for System z . . . . . . . . . . . . 49
6.5 Mounting a CD / DVD for Solaris . . . . . . . . . . . . . . . . 49
6.6 Starting and Stopping the Instance Using the SAP Management Console . . 50
6.7 Starting and Stopping the Instance Using Scripts . . . . . . . . . . . 51
6.8 Uninstalling the Instance . . . . . . . . . . . . . . . . . . . 52
6.9 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 52

4/58 PUBLIC 03/28/2008

1 Introduction

1 Introduction

This documentation describes how to install the Web Dispatcher for an existing SAP system.
We recommend to install the Web Dispatcher when you use an SAP system with several application
servers for web applications.

1.1 Web Dispatcher

The Web dispatcher is situated between the Internet and your SAP system. It is the entry point for
HTTP(s) requests into your system, which consists of one or more SAP NetWeaver application servers.

Figure 1:

As a "software web switch", the Web dispatcher can reject or accept connections. When it accepts a
connection, it balances the load to ensure an even distribution across the servers.
You can use the Web dispatcher in ABAP+Java systems as well as in pure Java systems and in pure
ABAP systems.

03/28/2008 PUBLIC 5/58

1 Introduction
1.2 SAP Notes for the Installation

Recommendation
The Web dispatcher is recommended when you use an SAP system with several SAP NetWeaver
application servers for Web applications.

The Web dispatcher can run on the machine that is connected directly to the Internet and requires
minimal configuration. You only have to enter the following data in the profile file:
n Port on which the HTTP(s) requests are to be received
Parameter icm/server_port_<xx>
n Host and HTTP port of the SAP message server
Parameters rdisp/mshost and ms/http_port)

Example
If you need to be able to call the Web application externally for example using the URL
www.shop.acme.com this host name must be mapped internally to the Web dispatcher, which
then forwards the HTTP(S) request to a suitable application server.

More Information

Recommendation
For more information see the Web Dispatcher documentation on the Help Portal:
help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life
Cycle Management by Key Capability System Management SAP Web Dispatcher .

1.2 SAP Notes for the Installation

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

SAP Notes for the Installation

SAP Note Number Title Description

928952 Web Dispatcher Installation Additional Information about Web
Dispatcher installation.
855498 Installation Prerequisite Checker Checking OS Dependencies for UNIX,
Windows and IBM i5/OS

6/58 PUBLIC 03/28/2008

1 Introduction
1.3 Online Information from SAP

1.3 Online Information from SAP

More information is available online as follows.

n SAP Help Portal:
http://help.sap.com
n Master Guide and installation guides for SAP NetWeaver 7.0 (2004s):
http://service.sap.com/installNW70.
n Upgrade Master Guide and upgrade guides to SAP NetWeaver 7.0 (2004s):
http://service.sap.com/upgradeNW70.
n Master Guide, installation guides and upgrade guides for SAP ERP:
http://service.sap.com/erp-inst.
n Master Guide, installation guides and upgrade guides for SAP CRM:
http://service.sap.com/crm-inst.
n Master Guide, installation guides and upgrade guides for SAP SRM:
http://service.sap.com/srm-inst.
n Master Guide, installation guides and upgrade guides for SAP SCM:
http://service.sap.com/instguides SAP Business Suite Applications SAP SCM .

1.4 Naming Conventions

In this documentation, the following naming conventions apply:

SAP system refers to the Web Dispatcher. From a technical point of view, the Web Dispatcher is set
up like an SAP system with its own SAP system ID (SAPSID), its own operating system users, and
its own directory structure.

Variables

Variables Description
<SAPSID> SAP system ID in uppercase letters
<sapsid> SAP system ID in lowercase letters
<DBSID> Database ID in uppercase letters
<dbsid> Database ID in lowercase letters
<host_name> Name of the corresponding host
<user_home> Home directory of the user performing the installation.
<INSTDIR> Installation directory for the SAP system
<DVD_DIR> Directory on which a DVD is mounted
<OS> Operating system name within a path
<SCHEMA_ID> Database schema ID

03/28/2008 PUBLIC 7/58

1 Introduction
1.4 Naming Conventions

The following example shows how the variables are used:

Example
Log on as user <sapsid>adm and change to the directory /usr/sap/<SAPSID>.
If your SAP system ID is C11, log on as user c11adm and change to the directory /usr/sap/C11.

8/58 PUBLIC 03/28/2008

2 Planning

2 Planning

2.1 Basic System Parameters

The tables below list the basic system parameters that you need to determine before you start the
installation. For all other SAP system parameters, use the F1 help in the SAPinst screens.
Parameters Description Your Value
File system for the home /home/<username> ...
directory user
Note
/home/ is only a recommendation.
SAP system mount /<sapmnt> is the base directory for the SAP system. ...
directory For /<sapmnt> you can use a directory of your choice.
Do not add <SAPSID> as subdirectory because the
system adds this directory automatically.

Example
If you enter /<sapmnt>, the system creates the
directory /<sapmnt>/<SAPSID>.
SAP System ID <SAPSID> The SAP System ID <SAPSID> identifies the whole SAP ...
system.

Caution
Choose your SAP system ID carefully. You cannot
change the SAP system ID after the installation.

Make sure that your SAP system ID:

n Is unique throughout your organization
n Consists of exactly three alphanumeric characters
n Contains only uppercase letters
n Has a letter for the first character
n Does not include any of the following, which are
reserved IDs:
ADD ALL AND ANY ASC 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 UID USR VAR

03/28/2008 PUBLIC 9/58

2 Planning
2.1 Basic System Parameters

Parameters Description Your Value

Instance Number Instance Number: ...
Technical identifier for internal processes. Consists of a
two-digit number from 00 to 97. The instance number
must be unique on a host. That is, if more than one SAP
instance is running on the same host, these instances
must be assigned different numbers.
Only valid for: HP-UX

Caution
Do not use 02, 75 for the instance number because:
n 02 is used to determine the port number for
report RSLGCOLL, which is 14<instance_number> by
default. The port 1402 however is already used by
the OS process rstlisten. If you decide to use 02 as
the instance number anyway, the instance fails to
start during the installation process. You then have
to change the port number for report RSLGCOLL
manually to continue with the installation.
n 75 is already used by the operating system. For
more information, see SAP Note 29972
End of: HP-UX

Operating System (OS) SAPinst will create the operating system user ...
User <sapsid>adm automatically unless you created it manually
[page 26] before starting SAPinst.
SAPinst prompts you to assign a password during the
input phase of the installation.
Message Server Host The host on which the message server is located (profile ...
parameter rdisp/mshost)
Message Server HTTP Port HTTP port of the message server (profile parameter ...
ms/server_port_<xx>)

Password for the In order to use the web administration interface for ...
Internet Communication the Internet Communication Manager (ICM) and
Management (ICM) user SAP Web Dispatcher, an administration user webadm is
created by SAPinst.
You have to assign a password for this user.

10/58 PUBLIC 03/28/2008

3 Preparation

3 Preparation

3.1 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating system
and the Web Dispatcher instance.

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

Process Flow

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

system releases.
2. Check the hardware and software requirements using:
n The Prerequisite Checker:
l Standalone (optional) before the installation process
For more information, see Running the Prerequisite Checker Standalone [page 12].
l Integrated in SAPinst (mandatory) as part of the installation process
For more information, see Running SAPinst [page 33].

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

n The hardware and software requirements checklists for:

Only valid for: AIX

l AIX [page 13]

End of: AIX

Only valid for: HP-UX

l HP-UX [page 16]

End of: HP-UX

Only valid for: Solaris

l Solaris [page 22]

End of: Solaris

03/28/2008 PUBLIC 11/58

3 Preparation
3.1 Hardware and Software Requirements

Only valid for: Linux IBM DB2 for z/OS

l Linux for System z [page 20]

End of: Linux IBM DB2 for z/OS

Only valid for: Linux

l Linux [page 18]

End of: Linux

l The Web Dispatcher Instance [page 26]

3. If you want to use the Web Dispatcher for a production system, the values provided by the
Prerequisite Checker and the hardware and software requirements checklists are not sufficient. In
addition, do the following:
n You use the hardware sizing information available at http://service.sap.com/sizing.
For the Web Dispatcher, there is a sizing guideline available at
http://service.sap.com/sizing Sizing Guidelines Solutions & Platform Sizing the SAP
Web Dispatcher
n You contact your hardware vendor, who can analyze the load and calculate suitable hardware
sizing depending on:
l The set of applications to be deployed
l How intensively the applications are to be used
l The number of users

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

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

Prerequisites
Only valid for: IBM DB2 for z/OS

n You have to select the operating system type of your central instance host when running the
Prerequisite Checker.
End of: IBM DB2 for z/OS

n You have installed the correct Java Runtime Environment (JRE) [page 28].
n You have prepared the installation master DVD on the required installation host [page 29].

12/58 PUBLIC 03/28/2008

3 Preparation
3.1 Hardware and Software Requirements

Procedure
1. You start SAPinst [page 33].
2. On the Welcome screen, choose Software Life-Cycle Options Additional Preparation Options Prerequisites
Check .
3. Follow the instructions in the SAPinst dialogs and enter the required parameters.

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

Result
The Prerequisite Check Results screen displays the results found. If required, you may also check the
results in file prerequisite_checker_results.html, which you find in the installation directory.
Only valid for: AIX

3.1.2 Requirements for AIX

The host machine must meet the following requirements:

Note
The information here is not intended to replace the documentation of the AIX operating system.
You can perform AIX-specific steps as follows:
n Manually by entering AIX commands with the appropriate options
n 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 ).

03/28/2008 PUBLIC 13/58

3 Preparation
3.1 Hardware and Software Requirements

Hardware Requirements

Requirement Values and Activities

Tape drive High-capacity tape drive with hardware compression is recommended.
You can test the drive /dev/rmt0 with this command:
tar -cvf /dev/<tape_device> <test_file>
The device name is always rmt0 unless more than one tape drive exists
DVD drive n ISO 9660 compatible
n You can configure multiple CD / DVD drives, but you cannot mount all of them. For
more information, see Mounting a CD / DVD for AIX [page 45].
Required disks For data security reasons, distribution over three disks is required. We recommend
you to distribute over five disks.
To display available disks, enter this command:
lspv
Disks marked none in the 3rd column are unused.
To display free space on a disk, enter this command:
lspv -p <disk_name>
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 To display RAM size in KB, enter the following command:
lsattr -El sys0 -a realmem

CPU The recommended minimum hardware is either two physical single core processors or
one physical dual core processor.

Software Requirements

Requirement Values and Activities

C++ runtime level Check the C++ runtime level with the following commands:
n AIX 6.x:
l #lslpp L xlC.aix61.rte
The output must be at least 9.0.0.1.
l #lslpp L xlC.rte
The output must be at least 9.0.0.1.
n AIX 5.x:
l #lslpp L xlC.aix50.rte
The output must be at least 7.0.0.4.
l #lslpp L xlC.rte
The output must be at least 7.0.0.0.
Operating system Check the operating system version with 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

14/58 PUBLIC 03/28/2008

3 Preparation
3.1 Hardware and Software Requirements

Requirement Values and Activities

AIX Maintenance n AIX 6.x: The output of the command oslevel -s should be at least 6100-00-01.
Level (ML) and n AIX 5.3: The output of the command oslevel -s should be at least 5300-05-01
Technology Level (TL 5 SP 1).
(TL) n AIX 5.2: The output of the command oslevel -r should be at least 5200-04 (ML 4).
LDAP (Lightweight If you want to use LDAP, you require the following LDAP library:
Directory Access libldap.a
Protocol)
Additional software Make sure that the following additional file sets are installed:
n bos.adt Base Application Development
n bos.perf performance and diagnostics tools
n perfagent.tools performance monitoring tools
n bos.perf.libperfstat Performance Statistics Library
For an overview of the installed file sets, enter the following command:
lslpp L | more
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:

n Cultural Conventions to install:
ISO8859-1 German (Germany) [de_DE]
n 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 with this command:
lppchk v

Other Requirements

Requirement Values and Activities

Printer Check whether a file can be printed with this command:
lp -d<printer_name> <test_file>
Check the status of your spool and the printers with this command:
lpstat -t

Keyboard You can set the keyboard by typing this command on the directly connected console:
smitty chkbd
You can select your keyboard under Motif by setting a language environment (LANG),
for which a National Language Support (NLS) component is installed. The settings
take effect after reboot.
Network Test the network connection to the database server with this command:
/etc/ping <db_server_name> 100 10

End of: AIX

03/28/2008 PUBLIC 15/58

3 Preparation
3.1 Hardware and Software Requirements

Only valid for: HP-UX

3.1.3 Requirements for HP-UX

n The information here is not intended to replace the documentation of the HP-UX operating
system (OS). For more information about HP-UX, see http://docs.hp.com.
n HP has released HP-UX 11i for the Itanium processor family. HP-UX 11i for Itanium is built from
the same code base as HP-UX 11i for PA-RISC and has the same look-and-feel.
In general, all OS requirements for HP-UX are valid for both the PA-RISC version and the Itanium
versions.
There are some exceptions due to new functionality of the latest HP-UX releases. They are listed in
the appropriate sections of this documentation.
n For more information about HP-UX 11iv3 and HP-UX 11.31, see SAP Note 1031960.
n As of HP-UX 11.31, HP offers a new web-based tool for system management, System Management
Homepage (SMH). You can start it in text mode or in web-based mode.
For more information about how to start it in web-based mode, see http://docs.hp.com.
The host machine must meet the following requirements:

Hardware Requirements

Requirement Values and Activities

CD / DVD drive ISO 9660 compatible. You must connect the CD or DVD drive locally to your central
instance host. Many CD or DVD drives can be configured but not all can be mounted.
For more information, see Mounting a CD / DVD for HPUX [page 46].
Disks 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 n To display the RAM size on HP-UX PA-RISC, enter the following command:
echo "selclass qualifier memory;info;wait;infolog" | cstm |grep Memory
|grep Total
n To display the RAM size on HP-UX Itanium or all 11.31 systems, enter the following
command:
/usr/contrib/bin/machinfo |grep Memory

CPU The recommended minimum hardware is either two physical single core processors or
one physical dual core processor.
To display the number of CPUs in a system call, enter the following command:
ioscan -fnkCprocessor

16/58 PUBLIC 03/28/2008

3 Preparation
3.1 Hardware and Software Requirements

Software Requirements

Requirement Values and Activities

Operating system Check the operating system version with the following command:
(OS) uname -r

Network File System The NFS driver must be in the kernel.

(NFS) You can check this using the current kernel configuration files. Enter the following
command:
grep nfs /stand/system
To check whether NFS is running, enter the following commands:
ps -ef | grep nfsd
ps -ef | grep rpcbind
grep NFS_C /etc/rc.config.d/nfsconf
grep NFS_S /etc/rc.config.d/nfsconf
Either NFS_CLIENT, NFS_SERVER, or both should be set to 1. You can use SAM or SMH to
start NFS or/and add the driver to the kernel.
National Language Enter the following command to check whether National Language Support (NLS) is
Support (NLS) installed.
swlist -v | grep -i nls
The output should contain the string NLS-AUX ...
Enter the following command to check which locales are available:
locale -a
The following files must be available: de_DE.iso88591, en_US.iso88591.
Minimum required See SAP Note 837670.
OS patches
LDAP support To use Lightweight Directory Access Protocol (LDAP) directory services, the following
LDAP libraries are required:
n HP-UX on Itanium (11.23/11.31):
libldapssl41.so

Fonts The directory /lib/X11/fonts contains the available fonts.

You can select fonts in your default profiles for X11 and CDE.

Example
iso_8859.1 or hp_roman8

Other Requirements

Requirement Values and Activities

Printer To check whether a file can be printed, enter the following command:
lp -d<printer_name> <test_file>
To check the status of your spool and the printers, enter the following command:
lpstat -t

Keyboard You can set the keyboard on an ASCII console as follows. A configuration menu bar is
activated via the User/System key:
config keys terminal config

03/28/2008 PUBLIC 17/58

3 Preparation
3.1 Hardware and Software Requirements

Requirement Values and Activities

Select Default Values or make your selection in the fields Keyboard and Language.

End of: HP-UX

Only valid for: Linux

3.1.4 Requirements for Linux

Note

n The information here is not intended to replace the documentation of the Linux operating
system (OS).
n For more information about the installation on Linux, see SAP Note 171356.
n For information about SAP on Linux, see http://sdn.sap.com/irj/sdn/linux.
The host machine must meet the following requirements:

Hardware Requirements

Requirement Values and Activities

DVD drive n DVD drive
l ISO 9660 compatible
Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS
SQL Server;Oracle
l Must be connected locally to your central instance host.
Only valid for: IBM DB2 for z/OS

Caution
On Linux for System z, the DVD drive cannot be connected to the central
instance host. However, you can connect the CD / DVD drive to any other host
that is connected to the central instance host.
End of: IBM DB2 for z/OS

End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL
Server;Oracle

l You can configure multiple DVD drives. For more information, see Mounting a CD /
DVD for Linux [page 48].

18/58 PUBLIC 03/28/2008

3 Preparation
3.1 Hardware and Software Requirements

Requirement Values and Activities

Disks For data security reasons, distribution over five disks is recommended (RAID5).
If an advanced disk array is available (for example, RAID), contact your hardware vendor
to make sure that the data security requirements are covered by this technology.
To print and change the partitioning of the first SCSI disk, enter this command:
/sbin/fdisk /dev/sda
To print and change the partitioning of a RAID device enter commands specific to your
hardware.

Example
Here are some examples of hardware-specific commands for RAID devices:
/sbin/fdisk /dev/rd/c0d0
/sbin/fdisk /dev/ida/c0d0

RAM To display RAM size in KB, enter the following command:

free

CPU The recommended minimum hardware is either two physical single core processors or
one physical dual core processor.

Software Requirements

Requirement Values and Activities

Operating system Check the operating system version with this command:
version cat /etc/*-release

Linux kernel version Check the Linux kernel version with this command:
uname -r

Linux kernel parameter Check the Linux kernel parameter settings with this command:
settings /sbin/sysctl a

Activated hardware Check the activated hardware drivers with this command:
drivers lsmod

Shared memory file Check the size of the shared memory file system with this command:
system df k /dev/shm

Network File System Check whether NFS is running as follows:

(NFS) Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS
SQL Server;Oracle
n On Red Hat Linux
service nfs status
service portmap status
End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL
Server;Oracle

n On SUSE LINUX
rcnfs status
rcnfsserver status
rcportmap status

03/28/2008 PUBLIC 19/58

3 Preparation
3.1 Hardware and Software Requirements

Requirement Values and Activities

Routing information To check routing information, enter the following command:
netstat -r

System language For the installation, you must choose English as the operating system language on
all Linux hosts that run SAP software.
National Language To display available locales, enter the following command:
Support (NLS) locale -a
Check the output for locales such as the following:
de_DE, en_US
locales are available as an attachment of SAP Note 171356.

LDAP (Lightweight If you want to use LDAP, you need the LDAP libraries that are usually installed with
Directory Access the openldap RPM. To check, enter this command:
Protocol) rpm -qa | grep openldap
Make sure that the output of this command contains at least one of the following
RPM packages:
n Red Hat Linux:
openldap2
n SUSE LINUX
openldap2
openldap2client

C compiler The C compiler gcc must be installed. To check, enter this command:
rpm -qa | grep gcc
Make sure that the output of this command contains a gcc RPM package.

Other Requirements

Requirement Values and Activities

Printer Check the status of spooling queues and printers with the following command:
lpc status
Check whether you can print a file with this command:
lpr P<printer_name> <test_file>

Network Test the network connection to the database server with the following command:
ping -c 10 <db_server_name>

End of: Linux

Only valid for: Linux IBM DB2 for z/OS

3.1.5 Requirements for Linux for System z

The information here is not intended to replace the documentation of the Linux operating system
(OS).
The host machine must meet the following requirements:

20/58 PUBLIC 03/28/2008

3 Preparation
3.1 Hardware and Software Requirements

Note
For more information about the installation of Linux for System z, see SAP Note 81737.

Hardware Requirements

Requirement Values and Activities

Hardware IBM eServer zSeries (64-Bit)
DVD Drive On Linux for System z, the DVD drive cannot be connected to the central instance
host. However, you can connect the DVD drive to any other host that is connected to
the central instance host.
RAM To display RAM size in KB, enter the following command:
free

CPU Your installation host must have at least two CPUs.

Software Requirements

Requirement Values and Activities

Operating system Supported Linux distributions are listed in SAP Note 81737.
To determine the operating system version, enter:
cat /etc/*-release

Linux kernel version Check the Linux kernel version with this command:
uname -r

Linux kernel Check the Linux kernel parameter settings with this command:
parameter settings /sbin/sysctl -a

SUSE Linux only: To check whether suse-sapinit is installed, enter the following command:
suse-sapinit must be rpm -qa | grep sapinit
installed The output must contain:
sapinit

Activated hardware Check the activated hardware drivers with the following command:
drivers lsmod

Shared memory file Check the size of the shared memory file system with the following command:
system df -k /dev/shm

Network File System Check whether NFS is running as follows:

(NFS) n On SUSE Linux, enter the following commands:
rcnfs status
rcnfsserver status
reportmap status

Routing information To check routing information, enter the following command:

netstat -r

03/28/2008 PUBLIC 21/58

3 Preparation
3.1 Hardware and Software Requirements

Requirement Values and Activities

National Language To display available locales, enter this command:
Support (NLS) locale -a
Check the output for locales such as the following:
de_DE, en_US

saplocales To check whether the required saplocales are installed, enter the following
command:
rpm -qa | grep saplocales
The output must contain the following:
saplocales-<GLIBC>-<VERS>
<GLIBC> is the installed glibc version
<VERS> is the saplocales version
saplocales are available as an attachment of SAP Note 171356.

LDAP (Lightweight If you want to use LDAP, you need the LDAP libraries that are usually installed with
Directory Access the openldap RPM. To check, enter this command:
Protocol) rpm -qa | grep openldap
Make sure that the output of this command contains at least one of the following
RPM packages:
n SUSE Linux
openldap2
openldap2client

C compiler The C compiler gcc must be installed. To check, enter the following command:
rpm -qa | grep gcc
Make sure that the output of this command contains a gcc RPM package.

Other Requirements

Requirement Values and Activities

Printer To check the status of spooling queues and printers, enter the following command:
lpc status
To check whether you can print a file, enter the following command:
lpr -P<printer_name> <test_file>

Network To test the network connection to the database server, enter the following command:
ping -c 10 <db_server_name>

End of: Linux IBM DB2 for z/OS

Only valid for: Solaris

3.1.6 Requirements for Solaris

The host machine must meet the following requirements:

22/58 PUBLIC 03/28/2008

3 Preparation
3.1 Hardware and Software Requirements

Note
The information here is not intended to replace the documentation of the Solaris operating system
(OS). For more information, see the Solaris online documentation at http://docs.sun.com.

Hardware Requirements

Requirement Values and Activities

Tape drive We recommend that you use a highcapacity tape drive with hardware
compression.
You can test the drives with this command:
/usr/bin/mt -f /dev/rmt/[0,1,2,..][n] status
This command displays drive type and whether a tape is loaded.
Alternatively, you can use this command:
/usr/bin/tar -cvf /dev/rmt/[0,1,2,..] \
[n] <testfile>

Volume Manager Mount a CD or DVD with this command:

/bin/volcheck
Dismount and eject a CD or DVD with this command:
/usr/bin/eject
Test whether the volume manager is running with this command:
/usr/bin/ps -ef |grep vold
Start the volume manager with this command:
/usr/sbin/vold &

Disks Enter the following in your commands to specify a device name:

dev/[r]dsk/c[0-99]t[0-99]d[0-99]s[0-7]
The parameters have the following meanings:
rdsk for raw devices
c[0-99] specifies the number of the controller
t[0-99] specifies the SCSI target
d[0-99] specifies the position in tray
s[0-7] specifies the number of the partition. s2 always specifies the full disk.
Display the partitioning, for example, with the following command:
/usr/sbin/prtvtoc <rawdevice>
Change the partitioning with this command:
/usr/sbin/format

RAM Display the available working memory with the following command:
/usr/sbin/prtconf |grep Memory

CPU The recommended minimum hardware is either two physical single core
processors or one physical dual core processor.
Display the status and number of existing CPUs with the following command:
/usr/sbin/psrinfo

03/28/2008 PUBLIC 23/58

3 Preparation
3.1 Hardware and Software Requirements

Software Requirements

Requirement Values and Activities

Operating system Check the operating system version with the following command:
/bin/uname -r

National Language To display which locales are available, enter the following command:
Support (NLS) locale -a
The following files must be available: iso_8859_1, en_US.

Lightweight Directory If you want to use LDAP, you required the following LDAP library:
Access Protocol (LDAP) libldap.so
Patches To check the installed patches, enter the following command:
/bin/showrev -p

Note
For more information about relevant patches, see the following SAP Notes:
n Sun Solaris 9: SAP Note 550585
n Sun Solaris 10: SAP Note 832871
n Solaris 10 on x64: SAP Note 908334
C++ runtime The Shared Library Patch for C++ must be installed.
environment
Solstice DiskSuite Check whether Solstice DiskSuite is installed with this command:
/bin/pkginfo | /usr/bin/grep SUNWmd
For more information, see the documentation for Solstice DiskSuite.
Veritas Volume If you do not use Solstice DiskSuite, check whether Veritas Volume Manager is
Manager installed:
/bin/pkginfo | /usr/bin/grep SUNWvx
For more information, see the documentation for Veritas Volume Manager.

Other Requirements

Requirement Values and Activities

Printer To see the status of the spool for all printers in use, enter the following command:
/bin/lpstat -t
To set up a printer enter this command:
/bin/admintool

24/58 PUBLIC 03/28/2008

3 Preparation
3.1 Hardware and Software Requirements

Requirement Values and Activities

Networking For a list of all active network devices, enter the following commands:
/usr/bin/netstat -I
/usr/sbin/ifconfig -a
To check routing information, enter the following command:
/usr/bin/netstat -r
To check whether ISDN is installed enter the following command:
/bin/pkginfo |grep SUNWisdn
To check the status of the ISDN connection enter the following command:
/opt/SUNWconn/bin/isdnstat
To check whether Network File System (NFS) is running do the following:
n Solaris 9
l To check whether the NFS client is running, enter the following command:
/usr/bin/ps -ef |grep nfs
l If the processesstatd and lockd are not running, start them with this
command:
/etc/init.d/nfs.client start
l To check whether the NFS client is running, enter the following command:
/usr/bin/ps -ef |grep nfs
l If the server is not running, start it with the following command:
/etc/init.d/nfs.server start
n Solaris 10 and higher
l To check whether the NFS client is running on Solaris, enter the following
command:
svcs -H -o state svc:/network/nfs/client:default
l If the output is not online, start the NFS client service with the following
command (and configure it to start during each reboot):
svcadm enable svc:/network/nfs/client:default
l To check whether the NFS server is running, enter the following command:
svcs -H -o state svc:/network/nfs/server:default
l If the output is not online, start the NFS server service with the following
command (and configure it to start during each reboot):
svcadm enable svc:/network/nfs/server:default
n Test the network connection to the database server with the following command:
/usr/sbin/ping <DB-SERVER>

C++ runtime Make sure that the shared library patch for C++ is installed.
environment
Installation In a standard Solaris installation, /tmp is a tmpfs file system.
directory tmpfs is a memory-based file system that uses kernel resources relating to the VM
system and page cache as a file system.
Once mounted, a tmpfs file system provides standard file operations and semantics.
tmpfs is so named because all files and directories are lost after reboot or unmounts.
For this reason, we recommend that you create a directory /temp on a ufs file system.

End of: Solaris

03/28/2008 PUBLIC 25/58

3 Preparation
3.2 Creating Operating System Users Manually (Optional)

3.1.7 Requirements for the Instance

The Web Dispatcher host must meet at least the following requirements for the Web Dispatcher
instance:
Requirement Values and Activities
Hard disk space n Hard disk drives with sufficient space for the Web Dispatcher instance.
For more information, see Setting up File Systems [page 27].
n 4.3 GB of temporary disk space for every required installation DVD that you
have to copy to a local hard disk. .
n 1.2 GB of temporary disk space for the installation.
Minimum RAM 500 MB
Swap space AIX, Solaris, z/OS: 3 * RAM
Linux, HP-UX: 2 * RAM
Network File System Network File System (NFS) must be installed.
(NFS)

3.2 Creating Operating System Users Manually (Optional)

If you do not want SAPinst to create operating systems users, groups and services, you can optionally
create them manually before the installation.
If you want to use global accounts which are configured on a separate host, you need to run the
installation service Operating System Users and Groups on this host.
For more information, see Running SAPinst [page 33].
SAPinst checks whether the required users and groups already exist. If not, it creates new users and
groups as necessary.
SAPinst chooses available user IDs and group IDs.
Users and Their Primary Groups
User Primary Group Additional Group Comment
<sapsid>adm sapsys sapinst SAP system administrator

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

Groups and Members

Groups Members
sapsys <sapsid>adm

sapinst <sapsid>adm

26/58 PUBLIC 03/28/2008

3 Preparation
3.3 SAP Directories

3.3 SAP Directories

SAPinst automatically creates the directories listed in the following figures and tables.
Before running the installation, you have to set up the required file systems manually. In addition,
you have to make sure that the required disk space for the directories to be installed is available
on the relevant hard disks.
The figure below assumes that you have set up one file system for the SAP system mount directory
<sapmnt> and one file system for the /usr/sap directory. However, you have to decide for which
directories you want to set up separate file systems. If you do not set up any file system on your
installation host, SAPinst creates all directories in the root directory /.
SAPinst prompts you only for the <sapmnt> directory during the installation. See also Basic SAP
System Parameters [page 9].

Figure 2:

The instance name (instance ID) of the Web Dispatcher instance is W<Instance_Number>, for example
W00.

SAP File Systems in Detail

Note
The listed file system sizes are initial SAP requirements.
Depending on your operating system, you might also have to add space for administrative purposes.

03/28/2008 PUBLIC 27/58

3 Preparation
3.4 Installing the Java Runtime Environment

File System Name Description Space Required

<sapmnt>/<SAPSID> The default name for the SAP system mount 400 MB
directory is sapmnt.
n exe
Contains executable kernel programs
n global
Contains log files
n profile
Contains the start and operations profiles of
all instances
/usr/sap/<SAPSID> There are subdirectories of 1 MB
/usr/sap/<SAPSID>/SYS with symbolic
links to subdirectories of /<sapmnt>/<SAPSID>:

3.4 Installing the Java Runtime Environment

You need to prepare your system for SAPinst. This includes the installation of a Java Runtime
Environment (JRE), which is required both for SAPinst and the SAPinst GUI.

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 37]. In this case, you need at least a JRE on the local host to
start the SAPinst GUI there.

Procedure
1. Check the JRE versions that are released for SAP systems in the Product Availability Matrix (PAM):
a) Go to http://service.sap.com/pam.
b) On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 7.0 (2004S) .
c) Choose tabstrip JSE Platforms.

Note
For more information about the recommended JRE version for your operating system and about
how to download it, see SAP Note 723909.

2. Make sure a valid JRE version is installed, as follows:

n If the JRE is not already installed, you need to download and install it.
n If the JRE is not already installed

28/58 PUBLIC 03/28/2008

3 Preparation
3.5 Preparing the Installation DVDs

Since the JRE is not part of the SAP shipment, you need to download and install it. The JRE
is part of the JDK (Java Development Kit).
n If the JRE is already installed
Check the installed version of the JRE by entering:
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.

Only valid for: Linux

Note
If you use a Sun Java VM, you have to perform the following:
Edit the configuration file $JAVA_HOME/jre/lib/security/java.security and replace entry
securerandom.source=file:/dev/random with securerandom.source=file:/dev/urandom.

End of: Linux

3.5 Preparing the Installation DVDs

3.5.1 Required Installation DVDs

You need the following installation DVDs for the Web Dispatcher installation:
Short Name of Required DVD Full Label of Required DVD
Installation Master DVD SAP NetWeaver 7.0 SR<support release number>
Installation Master
Kernel DVD SAP NETWEAVER 7.0 SR<support release
number> Kernel (DVD), according to operating
system

Note
Normally you obtain the installation DVDs as part of the installation package you received from SAP.
However, you can also download installation DVDs from SAP Service Marketplace [page 30].

03/28/2008 PUBLIC 29/58

3 Preparation
3.5 Preparing the Installation DVDs

More Information
You can find a complete list of all media shipped with SAP NetWeaver 7.0 in the document
Media List for SAP NetWeaver 7.0 SR<support release number> on SAP Service Marketplace at
http://service.sap.com/installNW70 Installation .

3.5.2 Downloading Installation DVDs from SAP Service

Marketplace (Optional)

You normally obtain the installation DVDs as part of the installation package from SAP.
However, you can also download installation DVDs from SAP Service Marketplace at:
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> .
If you download installation DVDs, note that DVDs might be split into several files. In this case, you
have to reassemble the required files after the download.

Prerequisites
To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you
can find on SAP Service Marketplace at http://service.sap.com/swdc. You need at least SAPCAR
700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longer
unpack current SAR files. For more information, see SAP Note 212876.

Procedure
1. Create a download directory on the host on which you want to run SAPinst.
2. Identify all download objects that belong to one installation DVD according to one or both of the
following:
n Material number
All download objects that are part of an installation DVD have the same material number and
an individual sequence number:
<material_number>_<sequence_number>

Example
51031387_1
51031387_2
...
n Title
All objects that are part of an installation DVD have the same title, such as
<solution><DVD_name><OS> or <database>RDBMS<OS> for RDBMS DVDs.

30/58 PUBLIC 03/28/2008

3 Preparation
3.5 Preparing the Installation 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.

03/28/2008 PUBLIC 31/58

This page is intentionally left blank.
4 Installation

4 Installation

4.1 Running SAPinst

You have to install the Web Dispatcher using the SAPinst tool.
Here you find information how to start and run SAPinst on your installation host.

Prerequisites
n Check that your installation hosts meets the requirements for the installation. For more
information, see Hardware and Software Requirements [page 11].
n Make sure that your operating system does not delete the contents of the temporary directory
/tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for
example by using a crontab entry.

Note
SAPinst normally creates the installation directory sapinst_instdir directly below the
temporary directory. SAPinst finds the temporary directory by checking the value of the
environment variables TEMP, TMP, or TMPDIR. If no value is set for these variables, SAPinst uses
/tmp as default installation directory.
The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. These
executables are deleted again after SAPinst has stopped running.
If required, you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C .

Caution
If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.

n Make sure that you have at least 60 MB of free space in the installation directory for each installation
service. In addition, you need 200 MB free space for the SAPinst executables. If you cannot provide
200 MB free space in the temporary directory, you can set one of the environment variables TEMP,
TMP, or TMPDIR to another directory with 200 MB free space for the SAPinst executables.

Shell Used Command

Bourne shell (sh) TEMP=<directory>
export TEMP

03/28/2008 PUBLIC 33/58

4 Installation
4.1 Running SAPinst

Shell Used Command

C shell (csh) setenv TEMP <directory>

Korn shell (ksh) export TEMP=<directory>

n Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime
Environment (JRE).
Only valid for: AIX

n If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE for
AIX 64-bit.
End of: AIX

n Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where <host_name>
is the host on which you want to display the SAPinst GUI.
Shell Used Command
Bourne shell (sh) DISPLAY=<host_name>:0.0
export DISPLAY

C shell (csh) setenv DISPLAY <host_name>:0.0

Korn shell (ksh) export DISPLAY=<host_name>:0.0

n Check the following values for user root:

l In csh execute limit
Output Properties
cputime unlimited

filesize unlimited

datasize 2097148 KB

stacksize 8192 KB

coredumpsize unlimited

descriptors 8192

memorysize unlimited

l In sh or ksh execute ulimit -a

Output Properties
time(seconds) unlimited

file(blocks) unlimited

data(kbytes) 2097148

34/58 PUBLIC 03/28/2008

4 Installation
4.1 Running SAPinst

Output Properties
stack(kbytes) 8192

coredump(blocks) unlimited

nofiles(descriptors) 8192

memory(KBytes) unlimited

If your parameter settings differ from the settings above, change these values accordingly.

Example
If you have to change the value for descriptors to 8192, proceed as follows:
u In csh execute:
limit descriptors 8192
u In sh or ksh execute:
ulimit -n 8192

Procedure
1. Mount the Installation Master DVD.
2. Start SAPinst from the Installation Master DVD in one of the following ways:
n Using the default installation directory (recommended)
Enter the following commands:
cd <Installation Master_DVD>/IM_<OS>
./sapinst

Caution
Make sure that your current working directory is not an IM_<OS> directory belonging to
another operating system.
For example, the following constellation causes an error:
$ cd /sapcd2/IM_HPUX_IA64
$ /sapcd2/IM_HPUX_PARISC/sapinst
The right constellation is as follows:
$ cd /sapcd2/IM_HPUX_PARISC
$ /sapcd2/IM_HPUX_PARISC/sapinst

n Using an alternative installation directory

If you want to use an alternative installation directory, set the environment variable TEMP,
TMP, or TMPDIR.

03/28/2008 PUBLIC 35/58

4 Installation
4.1 Running SAPinst

Note
n During the installation, the default ports 21200 and 21212 are used for communication between
SAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to communicate with the GUI
server. The GUI server uses port 21212 to communicate with SAPinst GUI. You get an error
message if one of these ports is already in use by another service.
In this case, you must execute sapinst using the following parameters:
SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server>
GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>.
n To get a list of all available SAPinst properties, start SAPinst as described above with the option
-p:
./sapinst -p.

3. On the Welcome screen, choose Standalone Engines Web Dispatcher Web Dispatcher Installation
4. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

Note
To find more information on each parameter during the Define Parameters phase of the installation,
position the cursor on the field of the respective parameter and press F1 .

After you have entered all requested input parameters, SAPinst displays the Parameter Summary screen.
This screen shows both the parameters that you entered and those that SAPinst set by default.
5. If required, change the displayed parameters as follows:
a) Select the parameters you want to change.
b) Choose Revise.
SAPinst displays input screens for the selected parameters.
c) Enter the new values for the parameters.
6. To start the installation, choose Start.
SAPinst starts the installation and displays the progress of the installation.
When the installation has successfully completed, SAPinst displays the screen Finished successfully.
7. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after SAPinst has finished.
Sometimes these remain in the temporary directory.

Note
If there are errors with SAPinst Self-Extractor, you can find the Self-Extractor log file
dev_selfex.out in the temporary directory.

Recommendation
We recommend that you keep all installation directories until you are sure that the system is
completely and correctly installed.

36/58 PUBLIC 03/28/2008

4 Installation
4.2 Performing a Remote Installation with SAPinst (Optional)

8. We recommend you to delete all files in the directory <user_home>/.sdtgui/.

9. If you copied installation DVDs to your hard disk, you can delete these files when the installation
has successfully completed.

More Information
If you have problems during the installation, see Troubleshooting with SAPinst [page 52].

4.2 Performing a Remote Installation with SAPinst (Optional)

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the
GUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is the
host from which you control the installation with SAPinst GUI.

Prerequisites
n The remote host meets the prerequisites before starting SAPinst [page 33].
n Both computers are in the same network and can ping each other.
To test this:
l Log on to your remote host and enter the command ping <local host>.
l Log on to the local host and enter the command ping <remote host>.

Procedure
1. Log on to your remote host as user root.

Caution
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.
3. Enter the following commands:
cd <Installation_Master_DVD>/IM_<OS>
./sapinst -nogui
For more information, see Running SAPinst [page 33].
SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at
the command prompt:
guiengine: no GUI connected; waiting for a connection on host <host_name>, port
<port_number> to continue with the installation.
4. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 38].

03/28/2008 PUBLIC 37/58

4 Installation
4.3 Starting SAPinst GUI Separately (Optional)

4.3 Starting SAPinst GUI Separately (Optional)

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI
separately in the following cases:
n You have logged off from SAPinst.
If you logged off during the installation and you later want to reconnect to the installation while it
is still running, you can start SAPinst GUI separately.
n You want to perform a remote installation [page 37].
If you want to run SAPinst GUI on a different host from SAPinst and the GUI server, you have to
start SAPinst GUI separately.

Prerequisites
You have installed the Java Runtime Environment [page 28] on the host on which you want to start SAPinst
without SAPinst GUI.

Starting SAPinst GUI on a Windows Platform

1. Log on as a member of the local administrators group.
2. Insert the SAP Installation Master DVD into your DVD drive.
3. Open a command prompt and change to the relevant directory:
Only valid for: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle

<DVD drive>:\IM_WINDOWS_<platform>
End of: IBM DB2 for Linux and UNIX and Windows;IBM DB2 for z/OS;MaxDB;MS SQL Server;Oracle

4. Start SAPinst GUI in one of the following ways:

n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following
command:
startinstgui.bat
SAPinst GUI uses the local host as default.
n If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation),
enter the following command:
startinstgui.bat -host <host_name>
<host_name> is the host name of the installation host.

38/58 PUBLIC 03/28/2008

4 Installation
4.3 Starting SAPinst GUI Separately (Optional)

Note
l If you enter the command without additional parameters, SAPinst GUI uses the local host
as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. Since
SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and
the SAP Installation GUI Connection dialog appears.
In this case, enter the name of the host on which SAPinst is running and choose Log on.
The first dialog of the installation appears and you can perform the remote installation
from your local host.
l For a list of options to start SAPinst GUI, change to the same directory as your SAPinst
executable and enter the command startinstgui.bat -h.

Starting SAPinst GUI on a UNIX Platform

1. Log on as user root.

Caution
Make sure that the root user has not set any environment variables for a different SAP system or
database.
2. Mount your installation DVD.

Note
Mount the DVD locally. We do not recommend that you use Network File System (NFS).

3. To change to the mount directory enter the following command:

cd <Installation_Master_DVD>/IM_<OS>
4. Start the SAPinst GUI in one of the following ways:
n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following
command without additional parameters:
./startInstGui.sh
SAPinst GUI uses as default the local host.
n If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation),
enter the following command with additional parameters:
./startInstGui.sh -host <host_name>
<host_name> is the host name of the installation host.

03/28/2008 PUBLIC 39/58

4 Installation
4.4 Interrupted Installation with SAPinst

Note
l If you enter the command without additional parameters, SAPinst GUI uses the local host
as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. Since
SAPinst and GUI server are running on another host, SAPinst GUI cannot connect and the
SAP Installation GUI Connection dialog appears.
In this case, enter the name of host on which SAPinst is running and choose Log on.
The first dialog of the installation appears and you can perform the remote installation
from your local host.
l For a list of options to start SAPinst GUI, change to the same directory as your SAPinst
executable and enter the command ./startInstGui.sh -h.

4.4 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:
n An error occurred during the dialog or processing phase:
SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses
and a dialog box appears. The dialog box contains a short description about the choices listed in
the table below as well as a path to a log file that contains detailed information about the error.
n You interrupted the installation by choosing Exit in the SAPinst menu.
The following table describes the options in the dialog box:
Option Definition
Retry SAPinst retries the installation from the point of failure without repeating
any of the previous steps.
This is possible because SAPinst records the installation progress in the
keydb.xml file.
We recommend that you view the entries in the log files, try to solve the
problem and then choose Retry.
If the same or a different error occurs again, SAPinst displays the same
dialog box again.
Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and
the GUI server.
SAPinst records the installation progress in the keydb.xml file. Therefore,
you can continue the installation from the point of failure without
repeating any of the previous steps. See the procedure below.
Continue SAPinst continues the installation from the current point.

Note
You can also terminate SAPinst by choosing Ctrl + C . However, we do not recommend that you
use Ctrl + C , because this kills the process immediately.

40/58 PUBLIC 03/28/2008

4 Installation
4.4 Interrupted Installation with SAPinst

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
Make sure that the root user has not set any environment variables for a different SAP system or
database.
2. Mount your Installation Master DVD.

Note
Mount the DVD locally. We do not recommend using Network File System (NFS).

3. Enter the following commands:

cd <Installation_Master_DVD>/IM_<OS>
./sapinst
4. From the tree structure in the Welcome screen, select the installation service that you want to
continue and choose Next.

Note
If there is only one component to install, the Welcome screen does not appear.

The What do you want to do? screen appears.

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

Continue old installation SAPinst continues the interrupted installation from the point of failure.

03/28/2008 PUBLIC 41/58

This page is intentionally left blank.
5 Post-Installation Activities

5 Post-Installation Activities

5.1 Logging on to the Web Dispatcher Management Console

You have to log on to the Web Dispatcher Management Console

n to check whether the Web Dispatcher was installed successfully,
n to change the password of the webadm user,
n to access monitoring and administration tools.

Procedure
1. Open a web browser.
2. Enter the following URL:
http://<web_dispatcher_host>:<web_dispatcher_port>/sap/admin
If you did not enter a specific port number, <web_dispatcher_port> is by default
81<instance_number>.
3. Log on as user webadm with the password that you entered during the input phase of the
installation.
The SAP Web Dispatcher Monitor screen appears.
4. We recommend that you change the password of webadm immediately after the installation for
security reasons.
For more information on how to change passwords of existing users using the Admin Handler,
see http://help.sap.com/nw70 Knowledge Center for SAP NetWeaver 7.0 (2004s) Functional View
[close] SAP NetWeaver by Key Capability Solution Lifecycle Management by Key Capability System
Management SAP Web Dispatcher Administration of the SAP Web Dispatcher Using the Web Administration
Interface Area menu Section HTTP Handler

5.2 Configuring and Operating the Web Dispatcher

After installing the Web Dispatcher you have to configure and operate it.
You find all important information in the SAP Web Dispatcher documentation on the Help Portal. See
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver by Key Capability
Solution Lifecycle Management by Key Capability System Management SAP Web Dispatcher

03/28/2008 PUBLIC 43/58

This page is intentionally left blank.
6 Additional Information

6 Additional Information

Only valid for: AIX

6.1 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
1. Log on as user root.
2. Add a CD / DVD file system.
a) Enter the command smitty.
b) Choose Physical & Logical Storage File Systems Add / Change / Show / Delete File Systems CDROM
File Systems Add a CDROM File System .
c) To get a list of device names, choose F4 .
Select a device name.
d) Enter the mount point <medium-mountdir>.

Example
<medium-mountdir> is /sapcd

e) Choose ENTER .
f) To exit smitty, choose F10 .
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.

a) Enter the command smitty.

b) Choose Physical & Logical Storage File Systems Mount a File System .
c) Place the cursor on File System Name and choose F4 .

03/28/2008 PUBLIC 45/58

6 Additional Information
6.2 Mounting a CD / DVD for HP-UX

d) Select the CD / DVD device /dev/cd0.

e) Place the cursor on field Directory over which to mount and choose F4 .
f) Select /sapcd.
g) Place the cursor on field Type of File System and choose F4 .
h) Select cdrfs.
i) Change Mount as Read Only system to YES
j) Choose ENTER .
k) To exit smitty, choose F10 .
End of: AIX

Only valid for: HP-UX

6.2 Mounting a CD / DVD for HP-UX

Proceed as follows to mount a CD or DVD.

Note
The placeholder <medium-mountdir> is used for either <cd-mountdir> or <dvd-mountdir>.

Mounting a CD / DVD Manually

1. Log on as user root.
2. To create a mount point for CD / DVD, enter the following command:
mkdir /<medium-mountdir>

Example
<medium-mountdir> is /sapcd

3. To find out the hardware address of the CD/DVD drive, proceed as follows:
a) Enter the following command:
ioscan -fnkCdisk
A list of all devices is displayed
b) Note the hardware address of the CD/DVD drive, for example c0t4d0.
4. To check that the driver is part of the kernel (skip this step if the CD / DVD drive is already
working), enter the following command:
grep cdfs /stand/system
5. To mount the CD / DVD on HP-UX 11.11 or 11.23, enter the following command:
mount -r -F cdfs -o rr /dev/dsk/<diskdevice> <medium-mountdir>
To mount the CD / DVD on HP-UX 11.31, enter the following command:
mount -r -F cdfs -o rr /dev/disk/<diskdevice> <medium-mountdir>

46/58 PUBLIC 03/28/2008

6 Additional Information
6.3 Mounting a CD / DVD for Linux

Example
HP-UX 11.11 or 11.23: mount -r -F cdfs -o rr /dev/dsk/c0t4d0 /sapcd
HP-UX 11.31: mount -r -F cdfs -o rr /dev/disk/c0t4d0 /sapcd

Mounting a CD / DVD Using SAM for HP-UX 11.11 or HPUX 11.23

1. Enter the command:
/usr/sbin/sam
2. Choose Disks and Filesystems Disk Devices Actions Mount
3. Enter the mount directory:
<medium-mountdir>

Example
For example, <medium-mountdir> is /sapcd.

4. Perform task.
5. Exit SAM.

Mounting a CD / DVD Using SMH for HP-UX 11.31

1. Enter one of the following commands:
n /usr/sbin/smh
n http://<hostname>:<port>
where <port> is either the default port 2381 or your defined port (for example 2301)
2. Choose Disks and Filesystems File Systems Add CDFS
3. Enter the mount directory:
<medium-mountdir>

Example
For example, <medium-mountdir> is /sapcd.

4. Choose the hardware path.

5. Choose New CDFS
6. Exit SMH.
End of: HP-UX

03/28/2008 PUBLIC 47/58

6 Additional Information
6.4 Mounting a CD / DVD for Linux for System z

Only valid for: Linux

6.3 Mounting a CD / DVD for Linux

Only valid for: IBM DB2 for z/OS

Note
The following is not valid for Linux for zSeries. If you need to mount your CD/DVD on Linux for
System z, see Mounting a CD/DVD for Linux for System z [page 49].

End of: IBM DB2 for z/OS

Note
The placeholder <medium-mountdir> is used for either <cd-mountdir> or <dvd-mountdir>.

Procedure
1. Log on as user root.
2. To create a mount point for the CD / DVD, enter the following command:
mkdir <medium-mountdir>

Example
<medium-mountdir> is /sapcd

3. To mount the first CD / DVD device, enter the following command:

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

End of: Linux

48/58 PUBLIC 03/28/2008

6 Additional Information
6.5 Mounting a CD / DVD for Solaris

Only valid for: Linux IBM DB2 for z/OS

6.4 Mounting a CD / DVD for Linux for System z

Mounting a CD / DVD can be achieved either by mounting a CD / DVD drive of a UNIX workstation
by using NFS, or by copying the contents to the Linux file system after mounting the CD / DVD
on a Windows workstation.

Using a CD / DVD Drive on a UNIX system

The CD / DVD file system has to be exported for NFS. Make sure that an NFS server is running
on the UNIX system.

Using a CD / DVD Drive on a Windows system

When using a CD / DVD drive on a Windows system, the following two alternatives are available:

NFS server
The Windows system must have third-party software installed providing the functions of an NFS
server. On Linux, the NFS client must be configured.

SAMBA
When using SAMBA, the CD / DVD cannot be accessed directly by Linux. Instead, the contents
must be copied to the Linux file system.
On Linux, SAMBA must be installed and configured. You have to provide a directory structure on
Linux for a copy of the CD / DVD. For every CD, a temporary disk space of about 650 MB is necessary,
and for every DVD a temporary disk space of about 4.3 GB. Define the directory as network share.
On the Windows system, map the share as network drive and copy the CD / DVD using the command:
xcopy <medium> <dest> /s/e
where <medium> is the CD / DVD drive and <dest> specifies the destination network drive and path.
End of: Linux IBM DB2 for z/OS

Only valid for: Solaris

6.5 Mounting a CD / DVD for Solaris

In the Solaris operating system, a layer of software manages CDs / DVDs and other media. This is the
volume manager, which automates the interaction between you and your CDs / DVDs. Do not use
this volume manager to mount CDs / DVDs needed for the installation, as the manager does not use
the normal case option. Without this option, some files on CDs / DVDs cannot be found. Mount CDs
/ DVDs for the installation manually as described in the following procedure.

03/28/2008 PUBLIC 49/58

6 Additional Information
6.6 Starting and Stopping the Instance Using the SAP Management Console

For more information about configuring the volume management, see the SunOS Routine System
Administration Guide.

Note
The placeholder <medium-mountdir> is used for either <cd-mountdir> or <dvd-mountdir>.

Procedure
1. Log on as user root.
2. To check if vold (volume daemon) is running, enter the following command:
ps -ef | grep vold
3. If it is running, kill vold.
4. Insert the CD / DVD into your disk drive.
5. To create a mount point, enter the following command:
mkdir /<medium-mountdir>

Example
for example, <medium-mountdir> is /sapcd

6. To mount the CD / DVD, enter the following command:

mount -F hsfs -o nomaplcase,ro /dev/dsk/c0t6d0s2 /<medium-mountdir>

After the installation, you can start vold using the following command:
/usr/sbin/vold.
End of: Solaris

6.6 Starting and Stopping the Instance Using the SAP

Management Console

You can start and stop the Web Dispatcher instance using the SAP Management Console (MC).

Prerequisites
Make sure that the SAP start service sapstartsrv is running:
For a new SAP system installation based on SAP NetWeaver 7.0 this service is still running after the
installation has finished successfully.

Procedure
1. Start a Web browser and enter the following URL:
http://<hostname>:5<instance_number>13

50/58 PUBLIC 03/28/2008

6 Additional Information
6.7 Starting and Stopping the Instance Using Scripts

Example
If the instance number is 53and the host name is saphost06, you enter the following URL:
http://saphost06:55313

2. Confirm the dialog asking you for your security certificate.

3. On the next screen, choose Start.
The SAP Management Console appears.
4. Choose File New from the menu and specify the SAP system parameters.
Your SAP system appears in the panel on the left.
5. On the main screen of the SAP Management Console expand the tree under SAP Systems on the left.
6. Right-click the SAP system node of the Web Dispatcher instance and choose Start or Stop.

More Information
For more information about the SAP Management Console, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library 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

6.7 Starting and Stopping the Instance Using Scripts

You can start and stop the Web Dispatcher instance by running the startsap and stopsap scripts.

Starting the Web Dispatcher Instance

1. Log on as user <sapsid>adm to the Web Dispatcher host.
2. Execute the command startsap all W<XX>, where <XX> is the instance number of the Web
Dispatcher.

Example
If the instance number is 01, then the command is startsap all W01.

The startup log is written to /home/<sapsid>adm/startsap_W<XX>.log.

Stopping the Web Dispatcher Instance

1. Log on as user <sapsid>adm to the Web Dispatcher host.
2. Execute the command stopsap all W<XX>, where< XX> is the instance number of the Web
Dispatcher.

Example
If the instance number is 01, then the command is stopsap all W01.

03/28/2008 PUBLIC 51/58

6 Additional Information
6.8 Uninstalling the Instance

The shutdown log is written to /home/<sapsid>adm/stopsap_W<XX>.log.

6.8 Uninstalling the Instance

The following procedure describes how to uninstall a Web Dispatcher instance using SAPinst.

Procedure
1. Start SAPinst [page 33].
2. On the Welcome screen, choose Software Life-Cycle Options Uninstall System / Standalone Engine /
Optional Standalone Unit .
3. Follow the instructions in the SAPinst input dialogs.

Note
To find more information on each parameter during the Define Parameters phase of uninstalling,
position the cursor on the field of the respective parameter and press F1 .

6.9 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.
If an error occurs, SAPinst:
n Stops the installation
n Displays a dialog informing you about the error

Procedure
1. To view the log file, choose View Logs.
2. If an error occurs during the dialog or processing phase, do either of the following:
n Try to solve the problem
n Abort the installation with Exit
For more information, see Interrupted Installation with SAPinst [page 40].
n Continue the installation by choosing Retry.
3. Check the log and trace files of the GUI server and SAPinst GUI in the directory
<user_home>/.sdtgui/ for errors.
4. If SAPinst GUI does not start, check the file sdtstart.err in the current <user_home> directory.
5. If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as
described in Starting SAPinst GUI Separately.

52/58 PUBLIC 03/28/2008

Typographic Conventions

Example Description

< > Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, Enter your <User Name>.
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
Example Textual cross-references to an internet address, for example, http://www.sap.com
/example Quicklinks added to the internet address of a homepage to enable quick access to
specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example n Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
n Cross-references to other documentation or published works
Example n Output on the screen following a user action, for example, messages
n Source code or syntax quoted directly from a program
n File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard

03/28/2008 PUBLIC 53/58

 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,
xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or
registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.
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.
This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2
from Michael Kay (http://saxon.sf.net/), XSLT version 1.

54/58 PUBLIC 03/28/2008

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 SAPs Support Services and may not be modified or
altered in any way.

Legal Software Terms

Terms for Included Open Source Software

This SAP software contains also the third party open source software products listed below. Note that for these third party
products the following special terms and conditions shall apply.

1. This software was developed using ANTLR.

2. SAP License Agreement for STLport
SAP License Agreement for STLPort between
SAP Aktiengesellschaft
Systems, Applications, Products in Data Processing
Dietmar-Hopp-Allee 16
69190 Walldorf, Germany
(hereinafter: SAP)
and
you
(hereinafter: Customer)
a) Subject Matter of the Agreement
A) SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library
(STLport) and its documentation without fee.
B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual
property laws, and to all of the terms and conditions of this Agreement.
C) The Customer may distribute binaries compiled with STLport (whether original or modified) without any
royalties or restrictions.
D) Customer shall maintain the following copyright and permissions notices on STLport sources and its
documentation unchanged: Copyright 2001 SAP AG
E) The Customer may distribute original or modified STLport sources, provided that:
n The conditions indicated in the above permissions notice are met;
n The following copyright notices are retained when present, and conditions provided in accompanying
permission notices are met:
Copyright 1994 Hewlett-Packard Company
Copyright 1996,97 Silicon Graphics Computer Systems Inc.
Copyright 1997 Moscow Center for SPARC Technology.
Copyright 1999,2000 Boris Fomitchev
Copyright 2001 SAP AG
Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is
hereby granted without fee, provided that the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company
makes no representations about the suitability of this software for any purpose. It is provided as is without
express or implied warranty.
Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is
hereby granted without fee, provided that the above copyright notice appear in all copies and that both that

03/28/2008 PUBLIC 55/58

 copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no
representations about the suitability of this software for any purpose. It is provided as is without express or
implied warranty.
Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is
hereby granted without fee, provided that the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC
makes no representations about the suitability of this software for any purpose. It is provided as is without
express or implied warranty.
Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is
provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use
or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all
copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are
retained, and a notice that the code was modified is included with the above copyright notice.
Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is
hereby granted without fee, provided that the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting documentation. SAP makes no representations
about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set
forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only
towards its customers and only referring to its modifications.
b) Support and Maintenance
SAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore
shall be not included.
All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions
and shall be subject to a separate contract.
c) Exclusion of warranty
As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the
STLport is error-free, without material defects or suitable for a specific application under third-party rights.
Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any
assurance of particular attributes.
d) Limited Liability
A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i)
can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or
(iii) if based on the failure of a guaranteed attribute.
B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial
employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall
depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract,
due to the circumstances known to it at that point in time representing a typical transfer of the software.
C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a
defect or lost profit.
D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed
EUR 5,000.
E) The Customer shall take adequate measures for the protection of data and programs, in particular by making
backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and
its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by
observing this obligation.
F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees
or agents of SAP.
3. Adobe Document Services

56/58 PUBLIC 03/28/2008

 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

03/28/2008 PUBLIC 57/58

 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.