Installation Guide SAP Solution Manager 7.

0 including SAP Enhancement Package 1 on AIX : Oracle
Using SAPinst
Target Audience ■ Technology consultants ■ System administrators

PUBLIC Document version: 1.10 – 2009-04-30

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 1.0

2009-04-30 2009-04-08

Updated Version Initial Version

2/168

PUBLIC

2009-04-30

Table of Contents

Chapter 1 1.1 1.2 Chapter 2 2.1 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.3 2.3.1 2.3.2 2.3.3 2.3.3.1 2.3.3.2 2.3.3.3 2.3.4 2.4 2.5 2.6 2.7 2.8 Chapter 3 3.1 3.2 3.3 3.3.1 3.3.2

Introduction ........................................................................................................... New Features ............................................................................................................. SAP Notes for the Installation .................................................................................. Planning ................................................................................................................... Planning Checklist .................................................................................................... Installation Options Covered by this Guide ........................................................... Central System .......................................................................................................... Distributed System .................................................................................................... High-Availability System .......................................................................................... Dialog Instance .......................................................................................................... Hardware and Software Requirements ................................................................... Running the Prerequisite Checker in Standalone Mode (Optional) .................... Requirements for a Central System ........................................................................ Requirements for a Distributed or a High Availability System ............................. Requirements for a Central Services Instance ........................................................ Requirements for the Central Instance .................................................................. Requirements for the Database Instance ................................................................ Requirements for a Dialog Instance ........................................................................ System Landscape Directory .................................................................................... SAP System Transport Host ..................................................................................... Planning User and Access Management ................................................................. Basic SAP System Parameters ................................................................................... High Availability: Planning the Switchover Cluster .............................................. Preparation .............................................................................................................. Preparation Checklist ............................................................................................... Creating Operating System Users and Groups ....................................................... Setting Up File Systems and Raw Devices ............................................................... SAP Directories .......................................................................................................... Oracle Directories .....................................................................................................

7 8 10 13 13 13 14 14 15 16 19 20 21 25 26 28 31 35 37 39 39 40 51 55 55 55 57 58 64

2009-04-30

PUBLIC

3/168

3.3.3 3.3.4 3.4 3.5 3.6 3.7 3.8 3.9 3.10 Chapter 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.7.1 4.7.2 4.7.3 4.7.4 4.7.5 Chapter 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12

Setting Up File Systems for a High-Availability System ......................................... Configuring Network File System for a High-Availability System ....................... Using Virtual Host Names ........................................................................................ Performing Switchover Preparations for High Availability ................................... Exporting and Mounting the Global Transport Directory ................................... Installing the Front-End Software ........................................................................... Installing the Java Development Kit ....................................................................... Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive ...... Preparing the Installation DVDs ..............................................................................

66 68 70 70 70 71 72 72 73

Installation .............................................................................................................. 77 Installation Checklist ................................................................................................ 77 Installation Checklist — Java Add-In ..................................................................... 81 Exporting and Mounting Global Directories: Distributed and High-Availability Systems ...................................................................................................................... 85 Performing a High-Availability Installation ............................................................ 86 Running SAPinst ....................................................................................................... 87 SAPinst Installation Options .................................................................................... 93 Oracle Database Software Installation ..................................................................... 97 Updating SAP-Specific Files in the Oracle Staging Area ........................................ 97 Performing Steps for the AIX Operating System ................................................... 98 Running the Oracle Universal Installer .................................................................. 99 Installing the Current Patch Set .............................................................................. 100 Installing Required Interim Patches ........................................................................ 101 Post-Installation ..................................................................................................... Post-Installation Checklist ....................................................................................... Logging On to the Application Server .................................................................... Configuring User Management ............................................................................... Ensuring User Security ............................................................................................. Installing the SAP License ......................................................................................... High Availability: Setting Up Licenses ..................................................................... Applying the Latest Kernel and Support Package Stacks ...................................... Configuring Remote Connection to SAP Support ................................................ Installing the SAP Online Documentation ............................................................. Performing Initial ABAP Configuration ................................................................. Performing Initial Java Configuration ..................................................................... Performing Oracle-Specific Post-Installation Steps ................................................ 103 103 104 105 106 111 112 113 114 114 114 119 120

4/168

PUBLIC

2009-04-30

5.13 5.14 5.15 5.16 5.17 Chapter 6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.8.1 6.8.2 6.8.3 6.8.4 6.8.5 6.9 6.9.1 6.9.2 6.9.3 6.10 6.11 6.12 6.13 6.14 6.15 6.15.1 6.16 6.17 6.18 Chapter A

Performing Post-Installation Steps for Adobe Document Services ...................... Configuring the Connection to a Central System Landscape Directory ............. Installing the SAP Solution Manager Enterprise Edition Add-On (Optional) .... Performing a Full Installation Backup .................................................................... Configuring SAP Solution Manager ........................................................................ Additional Information ........................................................................................ Integration of LDAP Directory Services .................................................................. Setting up Swap Space for AIX ................................................................................. Creating AIX Groups and Users .............................................................................. Setting Up File Systems and Raw Devices for AIX ................................................. Dialog Instance Installation for an Upgraded System only: Updating Profiles ........................................................................................................................ Mounting a CD / DVD for AIX ................................................................................ Exporting and Mounting Directories via NFS for AIX ........................................... Additional Information About SAPinst .................................................................. Using SAPinst GUI .................................................................................................... Interrupted Installation with SAPinst ..................................................................... Performing a Remote Installation with SAPinst .................................................... Starting the SAPinst GUI Separately ....................................................................... Entries in the Services File Created by SAPinst ....................................................... Starting and Stopping SAP System Instances ......................................................... Starting and Stopping SAP System Instances Using the SAP Management Console ...................................................................................................................... Starting and Stopping SAP System Instances Using Scripts .................................. Starting and Stopping the Diagnostics Agent Using Scripts ................................. Creating a User for LDAP Directory Access ............................................................ Accessing the SAP Java Documentation ................................................................. Initial Technical Configuration for Adobe Document Services ........................... Initial Technical Configuration for the System Landscape Directory (SLD) ....... Heterogeneous SAP System Installation ................................................................. Troubleshooting ....................................................................................................... Troubleshooting with SAPinst ................................................................................ Deleting an SAP System ........................................................................................... Deleting the Oracle Database Software ................................................................... Deleting a Diagnostics Agent ...................................................................................

121 122 123 123 124 127 127 131 132 133 134 136 137 138 138 139 141 142 144 145 145 149 151 152 153 154 155 156 156 156 157 159 159

Appendix .................................................................................................................. 161

2009-04-30

PUBLIC

5/168

A.1

Online Information from SAP ................................................................................. 161

6/168

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: ■ 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 ■ Your operating system platform must be 64-bit.
NOTE

The only instance, you can still install on 32-bit is the dialog instance. ■ The database must be Oracle 10.2.0.2 or higher.

2009-04-30

PUBLIC

7/168

1 1.1

Introduction New Features

Naming Conventions

■ SAP Solution Manager refers to SAP Solution Manager 7.0 EHP1. ■ SAP system refers to SAP Solution Manager 7.0 EHP1 system. ■ 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. ■ 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). ■ Diagnostics Agent refers to Solution Manager Diagnostics Agent.
Profiling for High Availability
Only valid for: HA (UNIX) |

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

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

64-bit support only for all instances except dialog instances

As of SAP Solution Manager 7.0 EHP1, SAPinst has the following new features: ■ You no longer have to install a Java Runtime Environment (JRE) to start the SAPinst GUI. However, you still have to install a Java Development Kit (JDK) to perform the installation with SAPinst (see Installing the Java Development Kit (JDK) [page 72]). ■ If you want to terminate SAPinst from the SAPinst GUI menu, you now have to choose SAPinst Cancel . If you choose File Exit , you only terminate the SAPinst GUI (see Using SAPinst GUI [page 138]). ■ You can directly access installation log files from the SAPinst GUI menu by choosing SAPinst Log Browser (see Using SAPinst GUI [page 138]). As of SAP Solution Manager 7.0, you must install an SAP Solution Manager system only on 64-bit operating systems.

8/168

PUBLIC

2009-04-30

1 1.1 Area

Introduction New Features 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 ■ 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. ■ You can also install it as a standalone engine, for example if you want a non-SAP system to be managed by SAP Solution Manager Diagnostics. The installation of the Diagnostics Agent as a standalone engine is not described in this installation guide, but in the Diagnostics Agent Setup Guide, which is available at http://service.sap.com/diagnostics Media Library . An SAP Solution Manager Diagnostics Agent (Diagnostics Agent) is a standalone Java program that runs on each of the systems managed by SAP Solution Manager Diagnostics. It gathers information and reports to the SAP Solution Manager system. For more information about the Diagnostics Agent, see http://service.sap.com/ diagnostics . Maintenance Optimizer All downloadable software components, released after April 2, 2007, are available exclusively through the Maintenance Optimizer in SAP Solution Manager. This comprises: ■ Support Package Stacks, Support Packages, and patches for Java instances, except for kernel patches ■ Legal changes ■ SAP applications and versions that are: ● Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and all applications based on this software, including SAP Business Suite 7 ● Optional for all SAP applications For more information, see http://service.sap.com/solman-mopz.
Operating Systems and Platforms Area Description

Support of Operating Systems and Platforms

■ For supported operating system and database releases, see the Product Availability Matrix at http://service.sap.com/pam. 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.

Oracle Database

New functions for Oracle Database

■ For a complete list of new Oracle features, see further documentation from Oracle, which you can find at:
http://www.oracle.com/technology/products/database/oracle10g

■ For a complete list of new features for SAP on Oracle, see http://sdn.sap.com/ irj/sdn/ora.

2009-04-30

PUBLIC

9/168

1 1.2

Introduction 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 1088980

SAP Solution Manager 7.0 EHP1 Installation Documentation: SAP Solution Manager

1010428 1164532 828268 98252

1234384 855498 73606 1067221

781448

789220

Central installation note for SAP Solution Manager 7.0 EHP 1. Information about scenarios, configurations, implementation, upgrade, maintenance, security, sizing, end user usage, enhancements using Support Packages, or problem analyses with regard to SAP Solution Manager End-to-End Diagnostics Information about availability and limitations of End-to-End Diagnostics. Release Restrictions for SAP Customer information on restrictions in the NetWeaver 7.0 EHP1 production use of certain functions. Oracle 10g: New functions Information about new Oracle features released for the SAP system. Installing two Oracle databases on This SAP Note is only required if you plan to a host install more than one Oracle database on the same host. Inst. NetWeaver 7.0 EhP1 Problems discovered after the publication of the Diagnostics Agent installation installation guide or post-installation steps Installation Prerequisite Checker SAP Software on UNIX, Windows, and IBM i: Checking OS Dependencies Supported Languages and Code Information on possible languages and language Pages combinations in SAP systems 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. Support Package levels of Information about ABAP Support Package levels Solution Manager installations/ and the kernel patch level upgrades 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.

10/168

PUBLIC

2009-04-30

1 1.2

Introduction SAP Notes for the Installation Title Description

SAP Note Number

925741

Adobe Document Services with Nonsupported Platforms

To use ADS in SAP landscapes on nonsupported platforms, you have to install an additional standalone SAP system with AS Java on a platform supported by ADS.

2009-04-30

PUBLIC

11/168

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

2 2.1

Planning Planning Checklist

2 Planning

2.1 Planning Checklist
You have to complete the following planning activities, which are described in more detail in the linked sections: 1. You 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 13]. 3. You check the hardware and software requirements [page 19]. 4. You plan the setup of the System Landscape Directory [page 37]. 5. You decide on the transport host to use [page 39]. 6. You plan user and access management [page 39]. 7. You identify basic SAP system parameters [page 40]. 8. Only valid for: HA (UNIX) | You plan the switchover cluster [page 51] for a high-availability (HA) system.
End of: HA (UNIX) |

9.

You can continue with Preparation [page 55].

2.2 Installation Options Covered by this Guide
This section shows the installation options covered by this installation guide. You have to decide what exactly you want to install because the steps you have to perform vary according to the installation option you choose. ■ Central system [page 14] ■ Distributed system [page 14] ■
Only valid for: HA (UNIX) |

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

■ You can install one or more dialog instances [page 16] to an existing central, distributed, or highavailability system.

2009-04-30

PUBLIC

13/168

2 2.2

Planning Installation Options Covered by this Guide

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

Figure 1:

Central ABAP+Java System

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

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

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

14/168

PUBLIC

2009-04-30

2 2.2

Planning Installation Options Covered by this Guide

Figure 2:

Distributed ABAP+Java System

Only valid for: HA (UNIX) |

2.2.3 High-Availability System
In a high-availability system, every instance can run on a separate host: ■ 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 16]. The following figures show examples for the distribution of the SAP instances in a high-availability system.

2009-04-30

PUBLIC

15/168

2 2.2

Planning Installation Options Covered by this Guide

Figure 3:

High-Availability System

End of: HA (UNIX) |

2.2.4 Dialog Instance
You can install one or more dialog instances for an existing SAP system. A dialog instance can run on: ■ The host of any instance of the existing SAP system (exceptions see below) ■ On a dedicated host
NOTE

If you want to install dialog instances running on an operating system other than the central instance, see Heterogeneous SAP System Installation [page 156]. For example, you need to do this if your central instance runs on Solaris but the dialog instance is to run on Windows.
Dialog Instance for a Central System

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

16/168

PUBLIC

2009-04-30

2 2.2

Planning Installation Options Covered by this Guide

Figure 4:

Dialog Instance for a Central System

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

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

2009-04-30

PUBLIC

17/168

2 2.2

Planning Installation Options Covered by this Guide

Figure 5:

Dialog Instance for a Distributed System

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

Dialog Instance for a High-Availability System

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

18/168

PUBLIC

2009-04-30

2 2.3

Planning Hardware and Software Requirements

Figure 6:

Dialog Instance for a High-Availability System

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

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

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

■ ■ ■ ■

Contact your OS vendor for the latest OS patches. Make sure that the host name meets the requirements listed in SAP Note 611361. Check your keyboard definitions. If you want to install a printer on a host other than the central instance host (for example, on a separate database instance host), make sure that the printer can be accessed under UNIX.

Process Flow

1.

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

2009-04-30

PUBLIC

19/168

2 2.3

Planning Hardware and Software Requirements

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 20]. ● Integrated in SAPinst (mandatory) during the installation process For more information, see Running SAPinst [page 87].
NOTE

3.

For the most recent updates to the Prerequisite Checker, always check SAP Note 855498. ■ The hardware and software requirements checklists for: ● Central system [page 21] ● Distributed or high availability system [page 25] ● If you want to install one or more dialog instances, check the requirements for a dialog instance [page 35]. 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 73]. ■ You make sure that the required prerequisites are met before starting SAPinst [page 87].
Procedure

1. 2.

You start SAPinst [page 87]. On the Welcome screen, choose <Your SAP product> Software Life-Cycle Options Additional Preparations Prerequisites Check .

20/168

PUBLIC

2009-04-30

2 2.3

Planning Hardware and Software Requirements

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. To start the prerequisites check, choose Next.

4.

Result

The Prerequisite Checker Results screen displays the results found. If required, you can also check the results in file prerequisite_checker_results.html, which you can find in the installation directory.
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: The table below also lists the most relevant requirements for the Oracle database. You obtain the full list of hardware and software requirements from the relevant Oracle database installation guide for your operating system, which you can find at: http://www.oracle.com/ technology/documentation.
NOTE

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

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

■ AIX 6.1: http://publib.boulder.ibm.com/infocenter/systems/index.jsp You can perform AIX-specific steps as follows: ■ Manually by entering AIX commands with the appropriate options ■ Using System Management Interface Tool (SMIT), a menu-driven system administration tool

2009-04-30

PUBLIC

21/168

2 2.3

Planning Hardware and Software Requirements

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

If you have access to Oracle Metalink we strongly recommend that you read document 169706.1. This document provides information about all operating system prerequisites and is regularly updated.
CAUTION

If your database resides on Network Attached Storage (NAS) you need to review and implement the Oracle NAS guidelines. You need to mount network file systems with specific mount options, which you can find in the Oracle installation guide.
CAUTION

The database must be Oracle 10.2 or higher.
Hardware Requirements Requirement Values and Activities

■ 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 136]. Distribution of the Oracle We recommend distribution of the Oracle database over three disks (RAID5) for data Database security reasons. To decide how many hard disks are required for your Oracle database, see section Database System Configuration in SAP Database Guide: Oracle (BC-DB-ORA-DBA) 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 Platform-Wide Services Database Support Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA) Getting Started with Oracle and the SAP System . CPU The recommended minimum hardware is two physical processor cores. To check this, do the following: ■ On AIX 5.2, enter the following command: DVD Drive
prtconf | grep Processors

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

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

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

Hard Disk Space

■ Hard disk drives with sufficient space for the SAP system and the database: For more information about space requirements for the separate file systems and directories, see Setting Up File Systems [page 58]. ■ 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 73]. ■ 1.2 GB of temporary disk space for the installation.

22/168

PUBLIC

2009-04-30

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

■ For data security reasons, distribution over three disks is required. We recommend you to distribute over five disks. ■ To display available disks, enter the following command:
lspv

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

RAM

Areas marked free in the 2nd column are unused. ■ If an advanced disk array is available (for example, RAID), contact your hardware vendor to make sure that the data security requirements are covered by this technology. 11 GB To display RAM size in KB, enter the following command:
lsattr -El sys0 -a realmem

Swap Space

Keyboard

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

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

Operating System Version

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

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

AIX Kernel Parameters

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

■ To adjust AIX Virtual Memory Management settings, see SAP Note 973227. ■ To adjust the settings for asynchronous I/O (aio) if the database is installed using file systems, see SAP Note 1157425. ■ AIX 6.x The output of the command oslevel -s should be at least 6100-00-01. ■ AIX 5.3

2009-04-30

PUBLIC

23/168

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

Additional Software

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

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

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

Networking

Check the C++ runtime level with the following commands: ■ AIX 6.x: ● #lslpp —L xlC.aix61.rte The output must be at least 9.0.0.1. ● #lslpp —L xlC.rte The output must be at least 9.0.0.1. AIX 5.x: ■ ● #lslpp —L xlC.aix50.rte The output must be at least 7.0.0.4. ● #lslpp —L xlC.rte The output must be at least 7.0.0.0. If application servers are installed decentralized, Network File System (NFS) must be installed. To test the network connection to the database server, enter the following command:
/etc/ping <db_server_name> 100 10

National Language Support (NLS)

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

2.

Select the following: ■ Cultural Conventions ■

to install:

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

3.

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

GUI for Oracle Database On the database host, a graphical user interface (GUI), for example X11, is required Installation for the Oracle database software installation with runInstaller. For more information, see the documentation of your operating system.

24/168

PUBLIC

2009-04-30

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

Check SAP Note 839182 to find whether you require an interim patch for the Oracle database installation. If so, make sure you have the corresponding Perl version as stated in that SAP Note. Oracle Kernel Parameters Review the Oracle-recommended kernel parameters and shell limits for your operating system with Oracle Database 10g Release 2 (10.2). These are only recommendations from Oracle for optimizing the system performance in production environments. If the recommended settings are not suitable for your system, you must tune the kernel parameters accordingly. You can obtain the recommended shell limits and kernel parameters from the relevant Oracle database installation guide for your operating system at: Oracle Interim Patches
http://www.oracle.com/technology/documentation

Parameter compatible

Printer

If you want to install a Java Add-In for an upgraded ABAP system, make sure that the parameter compatible is set to 10.2.0 in the file ORACLE_HOME/dbs/ init<dbsid>.ora. For more information, see Upgrade Guide – SAP NetWeaver 7.0 including Enhancement Package 1 Application Server ABAP at: http://service.sap.com/upgradeNW70 Upgrade to SAP NetWeaver Systems Upgrade Documentation – SAP NetWeaver 7.0 incl. EHP1 SAP NetWeaver 7.0 incl. EHP1 Application Server ABAP ■ To check whether a file can be printed, enter the following command:
lp -d<printer_name> <test_file>

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

2.3.3 Requirements for a Distributed or a High Availability System
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

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

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

■ AIX 6.1: http://publib.boulder.ibm.com/infocenter/systems/index.jsp You can perform AIX-specific steps as follows: ■ Manually by entering AIX commands with the appropriate options ■ Using System Management Interface Tool (SMIT), a menu-driven system administration tool

2009-04-30

PUBLIC

25/168

2 2.3

Planning Hardware and Software Requirements

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 ). ■ Central services instance [page 26] ■ Central instance [page 28] ■ Database Instance [page 31]
NOTE

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

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

DVD Drive

CPU

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

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

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

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

Hard Disk Space

■ Hard disk drives with sufficient space for the central services instance: 4 GB For more information about space requirements for the separate file systems and directories, see Setting up File Systems [page 58]. ■ 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 73]. ■ 1.2 GB of temporary disk space for the installation. ■ For data security reasons, distribution over three disks is required. We recommend you to distribute over five disks. ■ To display available disks, enter this command:
lspv

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

Areas marked free in the 2nd column are unused.

26/168

PUBLIC

2009-04-30

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

RAM

■ If an advanced disk array is available (for example, RAID), contact your hardware vendor to make sure that the data security requirements are covered by this technology. 4 GB To display RAM size in KB, enter the following command:
lsattr -El sys0 -a realmem

Swap Space

Keyboard

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

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

Operating System Version

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

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

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

2009-04-30

PUBLIC

27/168

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

National Language Support (NLS)

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

2.

Select the following: ■ Cultural Conventions ■

to install:

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

3.

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

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

Printer

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

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

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

DVD Drive

■ ISO 9660 compatible

28/168

PUBLIC

2009-04-30

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

CPU

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

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

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

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

Hard Disk Space

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

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

RAM

Areas marked free in the 2nd column are unused. ■ If an advanced disk array is available (for example, RAID), contact your hardware vendor to make sure that the data security requirements are covered by this technology. 7 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: At least 20 GB for the first SAP instance to be installed on a server and at least 10 GB for each additional active SAP instance on the same server ■ Defensive strategy: 3 * RAM, at least 20 GB For more information about recommended paging space, see SAP Note 1121904. To display and – if required – modify the existing swap space, use the System Management Interface Tool (SMIT). For more information, see Setting up Swap Space for AIX [page 131]

2009-04-30

PUBLIC

29/168

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

Keyboard

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

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

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

AIX Kernel Parameters

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

Additional Software

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

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

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

Networking

To check the C++ runtime level, enter the following commands: ■ AIX 6.x ● #lslpp —L xlC.aix61.rte The output must be at least 9.0.0.1. ● #lslpp —L xlC.rte The output must be at least 9.0.0.1. ■ AIX 5.x ● #lslpp —L xlC.aix50.rte The output must be at least 7.0.0.4. ● #lslpp —L xlC.rte The output must be at least 7.0.0.0. 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:

30/168

PUBLIC

2009-04-30

2 2.3

Planning Hardware and Software Requirements Values and Activities
/etc/ping <db_server_name> 100 10

Requirement

National Language Support (NLS)

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

2.

Select the following: ■ Cultural Conventions ■

to install:

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

3.

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

Printer

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

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

2.3.3.3 Requirements for the Database Instance
The database host must meet the following requirements: The table below lists the most relevant requirements for the Oracle database instance host. You obtain the full list of hardware and software requirements from the relevant Oracle database installation guide for your operating system, which you can find at: http://www.oracle.com/
technology/documentation RECOMMENDATION

If you have access to Oracle Metalink, we strongly recommend that you read document 169706.1. This document provides information about all operating system prerequisites and is regularly updated.
CAUTION

If your database resides on Network Attached Storage (NAS), you need to review and implement the Oracle NAS guidelines. You need to mount network file systems with specific mount options, which you can find in the Oracle installation guide.
CAUTION

The database must be Oracle 10.2 or higher.

2009-04-30

PUBLIC

31/168

2 2.3

Planning Hardware and Software Requirements

Hardware Requirements Requirement Values and Activities

Distribution of the Oracle We recommend distribution over three disks (RAID5) for data security reasons. Database To decide how many hard disks are required for your Oracle database, see the Database System Configuration guide in SAP Database Guide: Oracle (BC-DB-ORA-DBA) in the SAP Library at: 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 Platform-Wide Services Database Support Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA) Getting Started with Oracle and the SAP System 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 136]. 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"

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

Hard Disk Space

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

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

RAM

Areas marked free in the 2nd column are unused. ■ If an advanced disk array is available (for example, RAID), contact your hardware vendor to make sure that the data security requirements are covered by this technology. 3 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. The required swap space can be calculated as follows: ■ 0.75 * RAM, if RAM is greater than 8 GB

32/168

PUBLIC

2009-04-30

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

Keyboard

■ 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). If you need information about how to do this, see Setting up Swap Space for AIX [page 131] ■ You can set the keyboard by typing this command on the directly connected console:
smitty chkbd

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

Operating System Version

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

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

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

Lightweight Directory Access If you want to use LDAP, you require the following LDAP library: Protocol (LDAP) libldap.a C++ Runtime Environment To check the C++ runtime level, enter the following commands: ■ AIX 6.x ● #lslpp —L xlC.aix61.rte The output must be at least 9.0.0.1. ● #lslpp —L xlC.rte The output must be at least 9.0.0.1. AIX 5.x ■ ● #lslpp —L xlC.aix50.rte The output must be at least 7.0.0.4.

2009-04-30

PUBLIC

33/168

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

Networking

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

#lslpp —L xlC.rte

National Language Support (NLS)

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

2.

Select the following: ■ Cultural Conventions ■

to install:

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

3.

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

GUI for Oracle Database Installation Oracle Interim Patches

Oracle Kernel Parameters

On the database host, a graphical user interface (GUI), for example X11, is required for the Oracle database software installation with runInstaller. For more information, see the documentation of your operating system. Check SAP Note 839182 to see whether you require an interim patch for the Oracle database installation. If so, make sure you have the corresponding Perl version as stated in that SAP Note. Review the Oracle-recommended kernel parameters and shell limits for your operating system with Oracle Database 10g Release 2 (10.2). These are only recommendations from Oracle for optimizing the system performance in production environments. If the recommended settings are not suitable for your system, you must tune the kernel parameters accordingly. You can obtain the recommended shell limits and kernel parameters from the relevant Oracle database installation guide for your operating system, which you can find at:
http://www.oracle.com/technology/documentation

Parameter compatible

If you want to install a Java Add-In for an upgraded ABAP system, make sure that the parameter compatible is set to 10.2.0 in the file ORACLE_HOME/dbs/ init<dbsid>.ora. For more information, see Upgrade Guide – SAP NetWeaver 7.0 Application Server ABAP on SAP Service Marketplace at:
http://service.sap.com/upgradeNW70

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

34/168

PUBLIC

2009-04-30

2 2.3

Planning Hardware and Software Requirements

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

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

DVD Drive

CPU

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

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

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

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

Hard Disk Space

■ Hard disk drives with sufficient space for the dialog instance. 6 GB For more information about space requirements for the separate file systems and directories, see Setting Up File Systems [page 58]. ■ 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 73]. ■ 1.2 GB of temporary disk space for the installation. ■ For data security reasons, distribution over three disks is required. We recommend you to distribute over five disks. ■ To display available disks, enter the following command:
lspv

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

RAM

Areas marked free in the 2nd column are unused. ■ If an advanced disk array is available (for example, RAID), contact your hardware vendor to make sure that the data security requirements are covered by this technology. 7 GB

2009-04-30

PUBLIC

35/168

2 2.3

Planning Hardware and Software Requirements Values and Activities

Requirement

To display RAM size in KB, enter the following command:
lsattr -El sys0 -a realmem

Swap Space

Keyboard

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

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

Operating System Version

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

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

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

National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding saplocales are installed.

36/168

PUBLIC

2009-04-30

2 2.4

Planning System Landscape Directory Values and Activities

Requirement

Install the necessary local code set by adding an additional language environment as follows: 1. Start the System Management Interface Tool (SMIT) with the following command:
smitty mle_add_lang

2.

Select the following: ■ Cultural Conventions ■

to install:

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

3.

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

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

Printer

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

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

2.4 System Landscape Directory
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

37/168

2 2.4

Planning System Landscape Directory

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 thirdparty 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: ■ 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. ■ 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: ■ http://service.sap.com/diagnostics End-to-End Root Cause Analysis Documentation Library Installation and Configuration Root Cause Analysis Installation and Upgrade Guide ■ http://service.sap.com/instguides SAP Components SAP Solution Manager <Current Release>

38/168

PUBLIC

2009-04-30

2 2.5

Planning SAP System Transport Host

2.5 SAP System Transport Host
The transport host contains the transport directory used by the SAP transport system to store transport data and change SAP system information, such as software programs, data dictionary data, or customization data. If you have several SAP systems, they are usually organized in transport domains. In most cases, all SAP systems in a transport domain have a common transport directory. When you install an SAP system, you have to decide which transport host and directory you want to use for your SAP system: ■ Use the transport directory that SAPinst creates during the installation of the SAP system by default on the global host: SAPinst by default creates the transport directory on the global host in /usr/sap/trans. ■ Use a transport directory located on a host other than the default host: ● You can use an existing transport directory and host in your SAP system landscape. ● You can set up a new transport directory on a different host. In either case, you must prepare this host for use by the new SAP system. For more information, see Exporting and Mounting the Global Transport Directory [page 70].
More Information

■ Setting Up File Systems and Raw Devices [page 57] ■ 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.6 Planning User and Access Management
You have to plan how you want to configure user and access management for your SAP system to be installed. Before you add a newly installed SAP system to your system landscape, you must decide which kind of user management you want to use: ■ Use AS ABAP. ■ 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 105].

2009-04-30

PUBLIC

39/168

2 2.7

Planning Basic SAP System Parameters

Using an LDAP directory as the Data Source for User Data

1. 2.

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

More Information

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

2.7 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: ■ Typical If you choose Typical, the installation is performed with default settings. This means that you only have to respond to a small selection of prompts including at least the following, which are described in the corresponding tables below: ● SAP system ID and database ID ● SAP system profile directory – only for systems with instances on separate hosts ● Master password ● JCE Unlimited Strength Jurisdiction Policy files archive ● System Landscape Directory (SLD) destination If you want to change any of the default settings, you can do so on the Parameter Summary screen. ■ Custom If you choose Custom, you are prompted for all parameters. At the end, you can still change any of these parameters on the Parameter Summary screen.
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.

40/168

PUBLIC

2009-04-30

2 2.7

Planning Basic SAP System Parameters

Java Development Kit and JCE Unlimited Strength Jurisdiction Policy Files Archive Parameters Description

Java Development Kit (JDK)

JCE Unlimited Strength Jurisdiction Policy Files Archive

A valid JDK is required for the Java application server. For more information about JDK versions supported by SAP and about how to install them, see Installing the Java Development Kit [page 72]. 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. For more information, see Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive [page 72].

SAP System ID and Database ID Parameters Description

SAP System ID <SAPSID>

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

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

■ ■ ■ ■

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

Database ID <DBSID>

■ If you want to install 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. The <DBSID> identifies the database instance. SAPinst prompts you for the <DBSID> when you are installing the database instance. The <DBSID> can be the same as the <SAPSID>.
CAUTION

Choose your database ID carefully. Renaming is difficult and requires you to reinstall the SAP system. ■ If you want to install a new database: Make sure that your database ID: ● Is unique throughout your organization ● Consists of exactly three alphanumeric characters

2009-04-30

PUBLIC

41/168

2 2.7

Planning Basic SAP System Parameters Description

Parameters

● Contains only uppercase letters ● Has a letter for the first character ● Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP TOP UID USE USR VAR

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

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

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

Description

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

If you install a dialog instance in an existing SAP system, SAPinst also prompts you for the profile directory of the existing SAP system.

42/168

PUBLIC

2009-04-30

2 2.7

Planning Basic SAP System Parameters

Unicode or Non-Unicode System Parameters Description

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

Instance Number of the Technical identifier for internal processes. It consists of a two-digit number from 00 SAP system to 98. The instance number must be unique on a host. That is, if more than one SAP instance is running on the same host, these instances must be assigned different numbers. To find out this number, look under the SAP directory /usr/sap/<SAPSID>/ 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 87]. 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 86]. ■ For more information about the use of virtual TCP/IP host names, see SAP Note 962955.

2009-04-30

PUBLIC

43/168

2 2.7

Planning Basic SAP System Parameters Description

Parameters

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

Master Password Common password for all users created during the installation: ■ Operating system users (for example <sapsid>adm)
CAUTION

If you did not create the operating system users manually before the installation, SAPinst creates them with the common master password (see table Operating System Users). In this case, make sure that the master password meets the requirements of your operating system and of your database. ■ 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 106]. ■ Java users

44/168

PUBLIC

2009-04-30

2 2.7

Planning Basic SAP System Parameters Description

Parameters

(for example J2EE_ADMIN) ■ Database users (for example ora<dbsid> ■ Secure Store key phrase For more information, see table Key Phrase for Secure Store Settings. Password policy The master password: ■ Must be 8 to 14 characters long ■ Must contain at least one letter (a-z, A-Z) ■ Must contain at least one digit (0-9) ■ Must not contain \ (backslash) and " (double quote) Depending on the installation option, additional restrictions might apply (for example, the master password must not contain the name of a Java user created during the installation).
Operating System Users Parameters Description

Password of Operating System Users

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

User Management Engine (UME) Parameter Description

ABAP Client

The production client of the ABAP system
CAUTION

DDIC Password

You only need to enter this parameter if you install the Java Add-In for an existing ABAP system. 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.

2009-04-30

PUBLIC

45/168

2 2.7

Planning Basic SAP System Parameters Description

Parameter

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, see SAP Note 718383. 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. For more information about supported UME data sources and change options, see SAP Note 718383. 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. For more information about supported UME data sources and change options, see SAP Note 718383. 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 Parameters Description

Key Phrase for Secure Store This is a random word or phrase that is used to encrypt the secure store. Settings The Java EE engine uses this phrase to generate the key that is used to encrypt the data. The uniqueness of the phrase you use contributes to the uniqueness of the resulting key.
RECOMMENDATION

Use a long key phrase that cannot be guessed easily. Use both uppercase and lowercase letters in the phrase and include special characters.
SAP Cryptographic Software Parameters Description

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 postinstallation 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 114]. 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

46/168

PUBLIC

2009-04-30

2 2.7

Planning Basic SAP System Parameters Description

Parameters

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

DNS Domain Name for SAP System

If you want to use HTTP-based URL frameworks such as Web Dynpro applications, you have to specify the DNS domain name for the SAP system. The DNS Domain Name is used to calculate the Fully Qualified Domain Name (FQDN), which is configured in profile parameter SAPLOCALHOSTFULL. FQDN is the fully qualified domain name for an IP address. It consists of the host name and the domain name:
<host name>.<domain name>

The DNS Domain Name is needed to define the URLs for the ABAP and Java application servers. It is appended to the server name to calculate the FQDN. For more information, see Configuring Fully Qualified Domain Names (FQDN) in Performing Initial ABAP Configuration [page 114].
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 Parameters Description

SLD Destination

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

SLD HTTP Host

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

2009-04-30

PUBLIC

47/168

2 2.7

Planning Basic SAP System Parameters Description

Parameters

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

SLD Data Supplier User and password

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

SLD ABAP API User and password

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

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

Prepare SAP System for NWDI Integration

If you select check box Prepare SAP System for NWDI Integration on the NWDI Landscape screen, SAPinst copies all SCAs belonging to the software units that you installed to the global transport directory. For more information about the global transport directory, see SAP Directories [page 58]. 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

48/168

PUBLIC

2009-04-30

2 2.7

Planning Basic SAP System Parameters

Parameters Relevant for Adobe Document Services (ADS) Parameters Description

User for basic authentication

SAPinst sets the user name ADSUSER and the master password by default. If required, you can choose another password according to your requirements. User for processing forms between SAPinst sets the user name ADSAGENT and the master password by default. an ABAP and a Java environment If required, you can choose another password according to your requirements.
Parameters Relevant for the File System Parameters Description
/home/<username> /<sapmnt> is the base directory for the SAP system.

File system for the home directory user SAP system mount directory

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

Oracle database file systems

■ ■ ■ ■

If you enter /<sapmnt>, the system creates the directory /<sapmnt>/ <SAPSID>. Oracle home sapdata home Client destination sapdata directory

Parameters Relevant for the Database Parameters Description

Code page

The code page that is used by your database (Unicode or Non-Unicode).
NOTE

You only need to enter this parameter if you perform a target system installation as part of a system copy. Database schema, Passwords The Java database schema is namedSAP<SCHEMA_ID>DB. Default name is SAPSR3DB. The ABAP database schema is named SAP<SCHEMA_ID>. Default name is SAPSR3.
RECOMMENDATION

Password of User ora<dbsid>

Choose a <SCHEMAID> that is different from your <SAPSID>. It might cause problems when you copy a system where <SCHEMAID> is the same as <SAPSID>, and the database-specific method used for the copy does not allow you to rename the database schemas. In certain situations, you might create a system copy with a new <SAPSID>, but where the database schema has the old <SAPSID>. This is not a technical problem, but might confuse the system administrator. User ora<dbsid> is the database administrator user. This user is only required on the host on which the database instance runs.

2009-04-30

PUBLIC

49/168

2 2.7

Planning Basic SAP System Parameters Description

Parameters

■ If you created user ora<dbsid> manually before the installation, SAPinst prompts you for the existing password of this user.
NOTE

If you chose parameter mode Typical, SAPinst only prompts you for the existing password of this user if the password is not the same as the Master Password. ■ If you did not create user ora<dbsid> manually before the installation, SAPinst creates it automatically during the installation. SAPinst then prompts you to enter and confirm a password for this user. In this case, SAPinst sets the Master Password by default. You can overwrite it.
NOTE

If you chose parameter mode Typical, SAPinst does not prompt you for the existing password of this user but creates this user and assigns the Master Password automatically. Make sure that the user ID and group ID of this operating system user are unique and the same on each application instance host. For more information, see Creating Operating System Users [page 55]. User ID of User ora<dbsid> If you chose parameter mode Typical and you did not create ora<dbsid> manually before the installation, SAPinst automatically creates this user with the appropriate user ID. In this case, SAPinst does not prompt you for the user ID of ora<dbsid>. Make sure that the user ID of user ora<dbsid> is unique and the same on each application instance host. For more information, see Creating Operating System Users [page 55]. Group IDs of sys, dba, and If you chose parameter mode Typical and you did not create ora<dbsid> manually oper before the installation, SAPinst automatically creates this user. SAPinst also assigns the user to groups sys, dba, and oper. In this case, SAPinst does not prompt you for the user ID of ora<dbsid>. Make sure that the group IDs of dba and oper are unique and the same on each application instance host. For more information, see Creating Operating System Users [page 55]. Database User Oracle User System Oracle Listener Name, Oracle ■ If you install the database instance on a host where no other Oracle database Listener Port is installed, you normally do not have to change the default values for Listener Name and Listener Port. ■ If there is already an Oracle database installed on your installation host, you can either use one listener for both databases or you have to specify an unused Listener Name and an unused Listener Port for the new listener. For more information if you use one listener for both databases, see SAP Note 98252. ■ All dialog instances of an SAP system must use the same Listener Port than the database instance. Tablespaces, Datafiles An Oracle database consists of one or more logical storage units called tablespaces, which collectively store all of the database's data. Each tablespace in an Oracle database consists of one or more files called datafiles, which are physical structures that conform to the operating system in which Oracle is running.

50/168

PUBLIC

2009-04-30

2 2.8

Planning High Availability: Planning the Switchover Cluster Description
MaxDatafileSize is the initial size of the tablespace datafile and its mapping to

Parameters

Database Instance RAM

Login Shell

the new tablespace layout while importing the external file DBSIZE.XML. SAPinst prompts you to enter MaxDatafileSize in MB: ■ 0: Datafile size defined in DBSIZE.XML is not changed. ■ 2000: Default datafile size. ■ 10000: Maximum datafile size. For more information about space requirements of the SAP datafiles (sapdata 1 - 4), see Oracle Directories [page 64]. The RAM that is required for the database instance installation. The default value used by SAPinst is 50 percent of the entire RAM. For more information about minimum RAM, see Hardware and Software Requirements [page 19]. SAPinst only prompts you for this parameter if you use a login shell other than the recommended C shell (csh). For more information, see SAP Note 202227.

Only valid for: HA (UNIX) |

2.8 High Availability: Planning the Switchover Cluster
You can reduce unplanned downtime for your high-availability (HA) SAP system by setting up a switchover cluster. This setup replicates critical software units – known as “single points of failure” (SPOFs) – across multiple host machines in the cluster. In the event of a failure on the primary node, proprietary switchover software automatically switches the failed software unit to another hardware node in the cluster. Manual intervention is not required. Applications accessing the failed software unit experience a short delay but can then resume processing as normal. Switchover clusters also have the advantage that you can deliberately initiate switchover to free up a particular node for planned system maintenance. Switchover solutions can protect against hardware failure and operating system failure but not against human error, such as operator errors or faulty application software. Without a switchover cluster, the SAP system SPOFs – central services instance, the database instance, and the central file share – are vulnerable to failure because they cannot be replicated. All of these can only exist once in a normal SAP system. You can protect software units that are not SPOFs against failure by making them redundant, which means simply installing multiple instances. For example, you can add additional dialog instances (that is, additional application servers). This complements the switchover solution and is an essential part of building HA into your SAP system.
RECOMMENDATION

We recommend switchover clusters to ensure HA for your SAP system. A switchover cluster consists of:

2009-04-30

PUBLIC

51/168

2 2.8

Planning High Availability: Planning the Switchover Cluster

■ A hardware cluster of two or more physically separate host machines to run multiple copies of the critical software units, in an SAP system the SPOFs referred to above ■ Switchover software to detect failure in a node and switch the affected software unit to the standby node, where it can continue operating ■ 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: ■ Check the information and the installation guides available at http://sdn.sap.com/irj/sdn/ ha. ■ The standalone replicated enqueue server is a major contribution to an HA installation and is essential for a Java system. We strongly recommend you to use it for an ABAP system. For more information about how to install the standalone replicated enqueue server, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology Client/Server Technology The SAP Lock Concept Standalone Enqueue Server Installing the Standalone Enqueue Server
Features

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

52/168

PUBLIC

2009-04-30

2 2.8

Planning High Availability: Planning the Switchover Cluster

Figure 7: NOTE

This figure and the figures in this section are only examples. Only the instances relevant to the switchover are shown – for example, the central instance is not shown. These graphics summarize the overall setup and do not show the exact constellation for an installation based on one of the available technologies (ABAP, ABAP+Java, or Java). You need to discuss your individual HA setup with your HA partner. The following figure shows an example of a switchover cluster in more detail:

2009-04-30

PUBLIC

53/168

2 2.8

Planning High Availability: Planning the Switchover Cluster

Figure 8:

Constraints

This documentation concentrates on the switchover solution for the central services instance. For more information about how to protect the NFS File System and the database instance by using switchover software or (for of the database) replicated database servers, contact your HA partner. You need to make sure that your hardware is powerful enough to handle the increased workload after a switchover. Some reduction in performance might be acceptable after an emergency. However, it is not acceptable if the system comes to a standstill because it is overloaded after switchover.
End of: HA (UNIX) |

54/168

PUBLIC

2009-04-30

3 3.1

Preparation Preparation Checklist

3 Preparation

3.1 Preparation Checklist
You have to complete the following preparations, which are described in more detail in the linked sections: 1. You make sure that the required operating system users and groups [page 55] are created. 2. You set up file systems or – if required – raw devices [page 57] 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 70]. 4. If you want to install a high-availability system, you perform switchover preparations [page 70]. 5. If you want to share the transport directory trans from another system, export [page 70] this directory to your installation hosts. 6. You install the SAP frontend software [page 71] on the desktop of the end user. 7. You install the Java Development Kit [page 72]. 8. You download the JCE policy zip file [page 72]. 9. You make sure that the required installation media [page 73] 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 134]. 11. You can continue with Installation [page 77].

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

55/168

3 3.2

Preparation Creating Operating System Users and Groups

Only valid for: HA (UNIX) |

RECOMMENDATION

For a distributed or a high-availability system, we recommend that you distribute account information (operating system users and groups) over the network, for example by using Network Information Service (NIS).
End of: HA (UNIX) |

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

SAPinst chooses available operating system user IDs and group IDs unless you are installing an additional application server instance. On an additional application server instance you have to enter the same IDs as on the host of the primary application server instance.
CAUTION

■ All users must have identical environment settings. If you change the environment delivered by SAP, such as variables, paths, and so on, we do not assume responsibility. ■ Do not delete any shell initialization scripts in the home directory of the OS users. This applies even if you do not intend to use the shells that these scripts are for. ■ If you use NFS-V4 file system, you have to create the ora<dbsid> user on the NFS server. You can do this either manually or by running Operating System Users and Groups. This user must have the same user ID as the ora<dbsid> user on the database server. Otherwise, you see the error message FSL-02098 Could not change owner of ... during the installation of the database instance. ■ The user ID (UID) and group ID (GID) of each operating system user and group must be identical for all servers belonging to the same SAP system. This does not mean that all users and groups have to be installed on all SAP servers. ■ If you are installing an SAP system where the instances are to run on several hosts (distributed or high-availability system), make sure that the group ID of group sapinst is always different from the group ID of any other group (for example, of group sapsys) used during the installation. Example: You are installing a dialog instance in an existing SAP system.

56/168

PUBLIC

2009-04-30

3 3.3

Preparation Setting Up File Systems and Raw Devices

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.
Users and Groups User
root

Primary Group

Additional Groups
sapinst

Comment

No primary group is assigned by SAPinst.
sapsys sapsys

<sapsid>adm <smdsid>adm

oper, dba, sapinst sapinst

ora<dbsid>

dba

oper, sapinst

Superuser of the UNIX operating system SAP system administrator Diagnostics Agent administrator Database administrator

The user ora<dbsid> is only required on the host where the database instance runs.
CAUTION

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

If you install a distributed system and you use local operating system user accounts instead of central user management (for example, NIS), user <sapsid>adm, sapadm, and the database operating system user must have the same password on all hosts.
Groups and Members Groups
sapsys oper dba sapinst

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

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

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

2009-04-30

PUBLIC

57/168

3 3.3

Preparation Setting Up File Systems and Raw Devices

3.3.1 SAP Directories
Depending on the installation option you have chosen, SAPinst automatically creates the directories listed in the following figures and tables. Before running the installation, you have to set up the required file systems manually. In addition, you have to make sure that the required disk space for the directories to be installed is available on the relevant hard disks. The figure below assumes that you have set up one file system for the SAP system mount directory <sapmnt> and one file system for the /usr/sap directory. However, you have to decide for which directories you want to set up separate file systems. If you do not set up any file system on your installation host, SAPinst creates all directories in the root directory /. SAPinst prompts you only for the <sapmnt> directory during the installation. For more information, see also table Parameters Relevant for the File System in Basic SAP System Parameters [page 40].
Only valid for: HA (UNIX) |

NOTE

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

CAUTION

SAPinst uses sapcpe to replicate the kernel automatically from /usr/sap/<SAPSID>/SYS/exe/ run/DIR_CT_RUN to /usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP system instance. The following entry in the start profile is responsible for this: Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF), where $(_PF) points to the instance profile. Do not delete DIR_CT_RUN from the instance profile. Otherwise, you cannot restart the system after patches have been applied. For more information, see Applying the Latest Kernel and Support Packages [page 113].
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.

58/168

PUBLIC

2009-04-30

3 3.3

Preparation Setting Up File Systems and Raw Devices

Figure 9:

SAP Directories for an ABAP + Java System (Unicode)

Figure 10:

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

59/168

3 3.3

Preparation Setting Up File Systems and Raw Devices

Only valid for: HA (UNIX) |

If you are performing an HA installation of your ABAP+Java system, there is also an ABAP central services instance called ASCS<Instance_Number>.
End of: HA (UNIX) |

EXAMPLE

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

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

Figure 11:

SAP Directories for the Diagnostics Agent

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

The listed space requirements are initial SAP requirements.

60/168

PUBLIC

2009-04-30

3 3.3

Preparation Setting Up File Systems and Raw Devices

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

Description

Space Required

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

SAP system ABAP (Non-Unicode) + Java only: exe contains a folder uc with a platform-specific subfolder:
<sapmnt>/<SAPSID>/exe/uc/<platform>

global

This directory contains log files. If you install an SAP system with distributed instances, you have to share this directory for all hosts. For more information, see the Prerequisites in Running SAPinst [page 87].
profile

/usr/sap/<SAPSID>

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

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

2009-04-30

PUBLIC

61/168

3 3.3

Preparation Setting Up File Systems and Raw Devices Description Space Required

Directory

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

/usr/sap/trans

Make sure that sufficient space is available in directory /usr/ sap/<SAPSID>/<INSTANCE_NAME>, since this stores SAP traces for the instance. Changes in SAP system profiles can also affect the disk space. 2.0 GB Global transport directory for all SAP systems For more information about exporting and mounting the global transport directory, see Exporting and Mounting the Global Transport Directory [page 70] 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 Oracle Directories [page 64].

62/168

PUBLIC

2009-04-30

3 3.3

Preparation Setting Up File Systems and Raw Devices

SAP Directories for the Diagnostics Agent in Detail NOTE

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

Description

Space Required

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

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

More Information

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

2009-04-30

PUBLIC

63/168

3 3.3

Preparation Setting Up File Systems and Raw Devices

3.3.2 Oracle Directories
The figure below assumes that you have set up one file system for the oracle directory. However, you have to decide yourself 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 /.
NOTE

Unicode systems require additional hardware resources. You can find more information about Unicode SAP systems at http://service.sap.com/unicode. Set up the required file system nodes for the Oracle database before the installation.

Figure 12:

Oracle Directories
Description Space Required

Oracle Directories Directory
/oracle /oracle/client

/oracle/stage/102_64

/oracle/<DBSID>

Oracle base directory File system for Oracle client software SAPinst creates the directory /oracle/ client/102_64/instantclient during the installation. Installation and upgrade directory for database software (staging area) This directory is also used for Oracle upgrades. We recommend that you do not delete it after the installation. Home directory of user ora<dbsid> We recommend that /oracle/<DBSID> does not reside in the root directory. It

50 MB for Oracle software 100 MB

5.5 GB

100 MB for files of user ora<dbsid> (for example, log files)

64/168

PUBLIC

2009-04-30

3 3.3

Preparation Setting Up File Systems and Raw Devices Description Space Required

Directory

/oracle/<DBSID>/102_64

/oracle/<DBSID>/origlogA /oracle/<DBSID>/origlogB /oracle/<DBSID>/mirrlogA /oracle/<DBSID>/mirrlogB /oracle/<DBSID>/oraarch

/oracle/<DBSID>/sapreorg

/oracle/<DBSID>/sapdata1 /oracle/<DBSID>/sapdata2 /oracle/<DBSID>/sapdata3 /oracle/<DBSID>/sapdata4

must reside in a file system with support for large files. For more information about how to create file systems larger than 2 GB on your operating system, see: Setting Up File Systems and Raw Devices for AIX [page 133] Therefore, either create /oracle/ <DBSID> as a separate file system with support for large files or create /oracle as a file system with support for large files and create /oracle/<DBSID> as a directory in /oracle. Home directory for Oracle instance ■ Database instance: 4.0 GB <DBSID> ■ All other instances: 200 MB (<ORACLE_HOME>). Make sure that this file system has <ORACLE_HOME> must reside on a local permissions 777. disk. It cannot be a softlink. Original set A of redo logs 200 MB Original set B of redo logs 200 MB Mirrored set A of redo logs 200 MB Mirrored set B of redo logs 200 MB New standard backup file system for For the installation, the archive Oracle offline redo logs directory /oracle/<DBSID>/oraarch Use a separate disk for the file system / requires at least 400 MB free disk space. oracle/<DBSID>/oraarch. For the operation of your SAP system, The file system /oracle/<SAPSID>/ we recommend that the archive saparch still remains but now only directory provides enough space for contains brbackup log files. /oracle/ archives between two backups. In a <SAPSID>/saparch is automatically production system, the amount created by SAPinst. archived each day is between 300 MB and 1 GB. Working directory for database 1.5 GB administration SAP data For space requirements of the SAP data file systems required for the installation SAP data of the ABAP system, see the following SAP data file: SAP data <Export_DVD>/DATA_UNITS/EXP1/
DB/ORA/DBSIZE.XML.

For space requirements of the SAP data file systems required for the installation of the Java system, see the following file:
<Java_DVD>/DATA_UNITS/JAVA_EXPORT/ DB/ORA/DBSIZE.XML.

See also the General section in SAP Note 1300538

2009-04-30

PUBLIC

65/168

3 3.3

Preparation Setting Up File Systems and Raw Devices

Only valid for: HA (UNIX) |

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 51].
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 57].
NOTE

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

2.

Make sure that the mount points under /<sapmnt>/<SAPSID>/ are permanent. Otherwise automatic start of the instance services does not work when you reboot the system. If the node that takes over the central instance also runs an AS instance during normal operation, we recommend that you use a different approach for the file system for the /usr/sap/<SAPSID> directory. The /usr/sap/<SAPSID> directory contains two subdirectories: ■ SYS contains links to the central directory /<sapmnt>/<SAPSID> ■ <INSTTYPE><NR> contains data for the local AS instance The name <INSTTYPE><NR> is defined by the type of services and the application server number, for example DVEBMSG00. Only the directory <INSTTYPE><NR> needs to be migrated with the AS instance during the switchover. Since the SYS subdirectory contains only links that do not require any space, it can be created locally on each cluster node. Therefore, instead of /usr/sap/<SAPSID>, create a file system for /usr/sap/<SAPSID>/<INSTTYPE><NR> with the usual <> substitutions. The file name for the

66/168

PUBLIC

2009-04-30

3 3.3

Preparation Setting Up File Systems and Raw Devices

central instance is usually DVEBMGS00. This avoids mount conflicts when switching over to a node on which an AS instance is already running. The DVEBMGS00 directory can join the tree /usr/sap/ <SAPSID> instead of mounting on top of it.
NOTE

3. 4.

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

The graphic below shows an example of the file systems and disks in an HA setup Note that this is only an example. For more information on a setup that meets your needs, consult your HA partner.

Figure 13:
End of: HA (UNIX) |

2009-04-30

PUBLIC

67/168

3 3.3

Preparation Setting Up File Systems and Raw Devices

Only valid for: HA (UNIX) |

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

Make sure that the mount points under /<sapmnt>/<SAPSID>/ are permanent. Otherwise automatic start of the instance services does not work when you reboot the system.
Procedure

1.

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

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

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

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

2.

Contains the kernel executables. The best solution is to store them locally on all AS instance hosts. Since you can protect NFS by a switchover product, it makes sense to install it on a cluster node. The requirements of your database system might dictate how NFS has to be set up. If required, you can configure the NFS server on the cluster node of the CI or the DB.

68/168

PUBLIC

2009-04-30

3 3.3

Preparation Setting Up File Systems and Raw Devices

In both cases the NFS clients use the virtual IP address to mount NFS. If the second node is used as an additional SAP instance during normal operation (for example, as a dialog instance), it also needs to mount the directories listed above from the primary node. When exporting the directories with their original names, you might encounter the problem of a “busy NFS mount” on the standby node. You can use the following workaround to solve this problem: 1. On the primary server, mount the disks containing the directories:
/export/usr/sap/trans /export/<sapmnt>/<SAPSID>

2.

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

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

3.

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

The standby NFS mounts: from virt.IP:/export/usr/sap/trans to /usr/sap/trans from virt.IP:/export/<sapmnt>/<SAPSID> to /<sapmnt>/<SAPSID> If the primary node goes down and a switchover occurs, the following happens: ■ These directories on the standby node become busy:
/usr/sap/trans /<sapmnt>/<SAPSID>

4.

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

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

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

2009-04-30

PUBLIC

69/168

3 3.4

Preparation Using Virtual Host Names

3.4 Using Virtual Host Names
You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to conceal their physical network identities from each other. This can be useful when quickly moving SAP servers or complete server landscapes to alternative hardware without having to reinstall or reconfigure.
Only valid for: HA (UNIX);HA (z/OS) |

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

Prerequisites

Make sure that the virtual host name can be correctly resolved in your Domain Name System (DNS) setup.
Procedure

Proceed as described in SAP Note 962955.
Only valid for: HA (UNIX) |

3.5 Performing Switchover Preparations for High Availability
If you want to use a virtual host name, you have to set the SAPinst propertySAPINST_USE_HOSTNAME to specify the required virtual host name before you start SAPinst. For more information, see Running SAPinst [page 87].
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.
End of: HA (UNIX) |

3.6 Exporting and Mounting the Global Transport Directory
CAUTION

This section does not apply to the installation of a Java Add-In to an existing ABAP system. In your SAP system landscape, a global transport directory for all SAP systems is required.

70/168

PUBLIC

2009-04-30

3 3.7

Preparation Installing the Front-End Software

■ If this global transport directory already exists, make sure that it is exported on the global transport directory host and mount it on the SAP instance installation host. ■ If this global transport directory does not exist, proceed as follows: ● Create the transport directory (either on the central instance host or on a file server). ● Export it on the global transport directory host. ● If you did not create the transport directory on your SAP instance installation host, mount it there.
Procedure
Exporting the Transport Directory

1. 2. 3.

Log on as user root to the host where the global transport directory /usr/sap/trans resides. Make sure that /usr/sap/trans belongs to the group sapsys and to the user root. If not already done, export the directory using Network File System (NFS).

Mounting the Transport Directory NOTE

If the transport directory resides on your local SAP instance installation host, you do not need to mount it. 1. 2. 3. Log on as user root to the central or dialog instance host where /usr/sap/trans is to be mounted. Create the mount point /usr/sap/trans. Mount /usr/sap/trans using Network File System (NFS) from the exporting host.

More Information

Mounting Directories via NFS for AIX [page 137]

3.7 Installing the Front-End Software
CAUTION

This section does not apply to the installation of a Java Add-In to an existing ABAP system. 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

2009-04-30

PUBLIC

71/168

3 3.8

Preparation Installing the Java Development Kit

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

2.

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

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

3.9 Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive
As of SAP NetWeaver 7.0 strong encryption is mandatory for the Java EE Engine and for all usage types that are deployed on it. You need to obtain the Java(TM) Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files for the JDK you are using beforehand so that SAPinst can install them. The JCE Unlimited Strength Jurisdiction Policy Files archive (JCE policy zip file)

72/168

PUBLIC

2009-04-30

3 3.10

Preparation Preparing the Installation DVDs

is specific for each Java VM provider and is available as a free download from the corresponding vendor's site.
Prerequisites

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

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

1.

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

2. 3.

You must not unzip the archive. SAPinst installs the JCE policy files during the installation process. Copy the JCE policy files to directory /usr/java14_64/jre/lib/security.

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

1.

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

The media names listed below are abbreviated. You can find the full names of all media shipped with SAP 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, ■ SAP Solution Manager Installation Master DVD dialog instance ■ SAP Kernel 7.00 SR3 <OS> DVD ■ SAP Solution Manager Java DVD

2009-04-30

PUBLIC

73/168

3 3.10

Preparation Preparing the Installation DVDs SAP Instance Installation Required DVDs

Database instance

■ ■ ■ ■ ■ ■ ■ ■ ■

RDBMS Client DVD SAP Solution Manager Installation Master DVD SAP Kernel 7.00 SR3 <OS> DVD SAP Solution Manager Java DVD SAP Solution Manager Installation Export 1 DVD SAP Solution Manager Installation Export 2 DVD RDBMS DVD RDBMS Patch DVD (if available) RDBMS Client 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, ■ SAP Solution Manager Installation Master DVD dialog instance ■ SAP Kernel 7.00 SR3 <OS> DVD ■ SAP Solution Manager Java DVD Database schema ■ SAP Solution Manager Installation Master DVD ■ SAP Kernel 7.00 SR3 <OS> DVD ■ SAP Solution Manager Java DVD ■ RDBMS Patch 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 136].
NOTE

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

■ Mount the DVDs locally. We do not recommend you to use Network File System (NFS), because reading from DVDs mounted with NFS might fail. ■ If you copy the DVDs to disk, make sure that the paths to the destination location of the copied DVDs do not contain any blanks.

74/168

PUBLIC

2009-04-30

3 3.10

Preparation Preparing the Installation DVDs

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

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

3. 4.

2009-04-30

PUBLIC

75/168

3 3.10

Preparation Preparing the Installation DVDs NOTE

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

76/168

PUBLIC

2009-04-30

4 4.1

Installation Installation Checklist

4 Installation

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

1.

You install the SAP system with SAPinst [page 87].
NOTE

2.

Do not install the Oracle database software before you run SAPinst. SAPinst stops and prompts you to install the Oracle database [page 97] while the installation of the database instance is running. You continue with Post-Installation [page 103].

Distributed System

1.

2.

3.

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

Do not install the Oracle database software before you run SAPinst.

2009-04-30

PUBLIC

77/168

4 4.1

Installation Installation Checklist

4.

SAPinst stops and prompts you to install the Oracle database software [page 97] while the installation of the database instance is running. On the central instance host, proceed as follows:
NOTE

You can use the SAP transport host or the SAP global host as your central instance host. 1. You mount the exported global directories [page 85] 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 87] to install the central instance. If required, you install one or more dialog instances on the respective hosts as described later in this section. 1. You mount the exported global directories [page 85] 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 87] to install the dialog instance. You continue with Post-Installation [page 103].

5.

6.

Graphical Overview

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

Figure 14:

Distribution of Instances in an ABAP+Java System

78/168

PUBLIC

2009-04-30

4 4.1

Installation Installation Checklist

Only valid for: HA (UNIX) |

High-Availability System

This section describes how you install a high-availability (HA) system consisting of two nodes (host A and host B). For more information, consult your HA partner. This procedure describes the steps that are required for a hardware cluster consisting of two nodes (host A and host B): 1. You need to make sure that your system meets the hardware and software requirements [page 25]. 2. If you want to share the transport directory trans from another system, you have to mount [page 70] 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 87] to install the ABAP central services instance (ASCS) using the virtual host name [page 70] on the primary cluster node, host A. 2. You run SAPinst [page 87] to install the central services instance (SCS) using the virtual host name [page 70] on the primary cluster node, host A. 3. You export global directories [page 85] 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 66], 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 55]. 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:

2009-04-30

PUBLIC

79/168

4 4.1

Installation Installation Checklist 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. 2. You prepare the database instance host and make sure that it has all the necessary file systems [page 66], mount points, and (if required) Network File System (NFS). You run SAPinst [page 87] to install the database instance.
NOTE

5.

Do not install the Oracle database software in advance. During the installation of the database instance, SAPinst stops the installation and prompts you to install the Oracle database software. On the central instance host, proceed as follows:
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 66], mount points, and (if required) Network File System (NFS). 2. You run SAPinst [page 87] to install the central instance. 3. If you want to use the shared transport directory trans from another system, you also mount [page 70] this directory (see above). We recommend that you install dialog instances with SAPinst to create redundancy. The application server instances are not a SPOF. Therefore, you do not need to include these instances in the cluster. 1. You mount the global directories [page 85] in <sapmnt>/<SAPSID>. 2. You run SAPinst [page 87] to install the dialog instance. 3. If you want to use the shared transport directory trans from another system, you also mount [page 70] this directory (see above). You continue with Post-Installation [page 103].

6.

7.

Graphical Overview

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

80/168

PUBLIC

2009-04-30

4 4.2

Installation Installation Checklist — Java Add-In

Figure 15:

Distribution of Instances in a High-Availability ABAP+Java System

End of: HA (UNIX) |

Dialog Instance

You perform the following steps on each host where you install the dialog instances. 1. You make sure that the global directories of the SAP system for which you want to install the dialog instance are mounted [page 85] on the host on which you want to install the dialog instance. 2. You run SAPinst [page 87] to install the dialog instance. 3. You continue with Post-Installation [page 103].

4.2 Installation Checklist — Java Add-In
This section includes the installation steps that you have to perform for the: ■ Java Add-In for an existing central ABAP system ■ Java Add-In for an existing distributed ABAP system ■ Java Add-In for an existing High-Availability ABAP system ■ 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 13].
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 87] to install the Java central services instance (SCS).

2009-04-30

PUBLIC

81/168

4 4.2

Installation Installation Checklist — Java Add-In

2.

2.

You run SAPinst [page 87] to install the database instance Java Add-In. This is to add the Java schema to the database. 3. You run SAPinst [page 87] to install the Java Add-In to the existing ABAP central instance. You continue with Post-Installation [page 103].

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 87] to install the Java central services instance (SCS). 2. On the database instance host of the existing ABAP system, you run SAPinst [page 87] 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 87] 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:
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 157] the existing ABAP dialog instances. 1. You mount the exported global directories [page 85] from the SAP global host (<sapmnt>/<SAPSID>/ exe, <sapmnt>/<SAPSID>/profile, <sapmnt>/<SAPSID>/global). 2. You run SAPinst [page 87] to install the required ABAP+Java dialog instance(s). You continue with Post-Installation [page 103].

3.

Graphical Overview

The following figure shows how to install the Java Add-In in an existing distributed ABAP system:

82/168

PUBLIC

2009-04-30

4 4.2

Installation Installation Checklist — Java Add-In

Figure 16:

Distributed Installation of a Java Add-In for an Existing ABAP System

Figure 17:

Distributed Installation of a Java Add-In for an Existing ABAP System

Only valid for: HA (UNIX) |

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):

2009-04-30

PUBLIC

83/168

4 4.2

Installation Installation Checklist — Java Add-In

1.

2. 3. 4.

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 87] to install the SCS using the virtual host name [page 70] 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 On the database instance host, you run SAPinst [page 87] to install the database instance Java Add-In. On the central instance host, you run SAPinst [page 87] to install the central instance Java AddIn. We recommend that you install ABAP+Java dialog instances to create redundancy. 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 85] in <sapmnt>/<SAPSID> of the SCS that you exported from the switchover cluster infrastructure. 2. You run SAPinst [page 87] to install the ABAP+Java dialog instance. You continue with Post-Installation [page 103].

5.

Graphical Overview

The following figure shows how to install the Java Add-In in an existing High-Availability ABAP system:

84/168

PUBLIC

2009-04-30

4 4.3

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

Figure 18:

High Availability Installation - Java Add-In

End of: HA (UNIX) |

ABAP+Java Dialog Instance

1. 2. 3.

You make sure that the global directories of the SAP system for which you want to install the dialog instance are mounted [page 85] on the host on which you want to install the dialog instance. You run SAPinst [page 87] to install the ABAP+Java dialog instance. You continue with Post-Installation [page 103].

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

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

2009-04-30

PUBLIC

85/168

4 4.4

Installation Performing a High-Availability Installation

■ 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 156].
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 137].
CAUTION

2. 3.

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 70]. Otherwise, the installation fails. Log on to the host of the new instance as user root. Create the following mount points and mount them from the SAP Global host:
<sapmnt>/<SAPSID>/exe <sapmnt>/<SAPSID>/profile <sapmnt>/<SAPSID>/global CAUTION

Make sure that these mount points are permanent. Otherwise automatic start of the instance services does not work when you reboot the system.
Only valid for: HA (UNIX) |

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

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

If you install the Java Add-In to an existing ABAP system, note the following: ● 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/168

PUBLIC

2009-04-30

4 4.5

Installation Running SAPinst

● When you install the database instance, SAPINST_USE_HOSTNAME must point to the virtual host name under which the database is installed. ● 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. 2.

3.

4. 5. 6.

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

7.

In a high-availability installation, the central instance does not need to be part of the cluster because it is no longer a single point of failure (SPOF). The SPOF is now in the central services instances (SCS and ASCS), which are protected by the cluster. If required, install additional dialog instances with SAPinst [page 87] to replicate the SAP system services that are not a SPOF. These nodes do not need to be part of the cluster.
NOTE

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

4.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 141], 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

2009-04-30

PUBLIC

87/168

4 4.5

Installation Running SAPinst

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

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

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

setenv TEMP <directory> export TEMP=<directory>

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

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

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

88/168

PUBLIC

2009-04-30

4 4.5

Installation Running SAPinst

● 4239 is the port of the HTTP server, which is part of the GUI server. If the ports for SAPinst and the GUI server are already in use, SAPinst automatically searches for free port numbers. If the search fails, you see an error message and SAPinst exits. In this case or if you want SAPinst to use specific ports, you can assign them by executing the sapinst executable with the following parameters: ● SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server> ● GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_gui> ● GUISERVER_HTTP_PORT=<free_port_number_http_server> ■ To see a list of all available SAPinst properties, start SAPinst as described above with the option p: ./sapinst -p. ■ If required, you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu.
NOTE

If you need to terminate SAPinst, you can do this by pressing
Prerequisites

Ctrl

+

C

.

■ Make sure that you have defined the most important SAP system parameters as described in Basic SAP System Parameters [page 40] before you start the installation. ■ Check that your installation hosts meets the requirements for the installation options that you want to install. For more information, see Running the Prerequisite Checker [page 20]. ■ If you want to perform a distributed or a high-availability installation, make sure that you have exported and mounted global directories [page 85]. ■ Check the value of the environment variable TEMP, TMP, or TMPDIR: ● Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variable TEMP, TMP, or TMPDIR points – for example, by using a crontab entry. ● Make sure that you have at least 60 MB of free space in the installation directory for each installation option. In addition, you need 200 MB free space for the SAPinst executables. If you cannot provide 200 MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or TMPDIR to another directory with 200 MB free space for the SAPinst executables. ● Make sure that the temporary directory has the permissions 777. ■ Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime Environment (JRE). ■ If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE for AIX 64-bit. ■ Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where <host_name> is the host on which you want to display the GUI.

2009-04-30

PUBLIC

89/168

4 4.5

Installation Running SAPinst Shell Used Command
DISPLAY=<host_name>:0.0 export DISPLAY

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

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

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

Properties
unlimited unlimited unlimited 8192 KB unlimited 8192 unlimited

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

-a Properties
unlimited unlimited 2097148 8192 unlimited 8192 unlimited

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

If you have to change the value for descriptors to 8192, proceed as follows: ◆ In csh, execute:
limit descriptors 8192

◆ In sh or ksh execute:
ulimit -n 8192

■ If you want to install a dialog instance to an existing SAP system, make sure that: ● There is exactly one entry in the /usr/sap/sapservices file for each SAP instance installed on this host. Be sure to check that the entry refers to the correct profile. ● There are no profile backup files with an underscore “_” in their profile name. If so, you must replace the “_” with a “.”.
EXAMPLE

Rename /usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2_D20081204 to / usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2.D20081204.

90/168

PUBLIC

2009-04-30

4 4.5

Installation Running SAPinst

Procedure

1.

Log on to the installation host as user root.
CAUTION

Do not use the user <sapsid>adm.
CAUTION

2.

3.

Make sure that the root user has not set any environment variables for a different SAP system or database. Mount the Installation Master DVD Mount the DVDs locally. We do not recommend that you use Network File System (NFS), because reading from DVDs mounted with NFS might fail. For more information about mounting DVDs, see Mounting a CD / DVD for AIX [page 136]. 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: ■ 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. ■ When you install the database instance, SAPINST_USE_HOSTNAME must point to the virtual host name under which the database is installed. ■ When you install the central instance, SAPINST_USE_HOSTNAME must point to the virtual host name under which the central instance is installed.
CAUTION

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

The following commands are correct:
$ cd /sapcd2/IM_HPUX_PARISC $ /sapcd2/IM_HPUX_PARISC/sapinst

4.

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

2009-04-30

PUBLIC

91/168

4 4.5

Installation Running SAPinst

5.

■ 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 . ■ 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> . ■ 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 93]. 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. If required, change the displayed parameters as follows: 1. Select the parameters you want to change. 2. Choose Revise. SAPinst displays input screens for the selected parameters. 3. Enter the new values for the parameters. To start the installation, choose Start. SAPinst starts the installation and displays the progress of the installation. When the installation has successfully completed, SAPinst displays the Finished successfully screen.
NOTE

6.

7.

8.

This note does not apply to the installation of a Java Add-In to an existing ABAP system: ■ During the installation of the Oracle database instance, SAPinst stops the installation and prompts you to install the Oracle database software [page 97]. After you have finished the installation of the Oracle database, you continue the database instance installation by choosing OK in the GUI of the database instance installation. ■ Check SAP Note 841728 for known installation problems with Oracle 10g. 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.

92/168

PUBLIC

2009-04-30

4 4.6

Installation SAPinst Installation Options 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 138] Interrupted Installation with SAPinst [page 139] Performing a Remote Installation with SAPinst [page 141] Starting SAPinst GUI Separately [page 142]. Entries in the Services File Created by SAPinst [page 144] Troubleshooting with SAPinst [page 156]

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

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

You choose SAP Systems with <your database> to install an SAP system with usage types or software units. You can install the following system variants:

2009-04-30

PUBLIC

93/168

4 4.6

Installation SAPinst Installation Options

■ 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 Installation Option Remarks

Central Services Instance (SCS)

Database Instance

Central Instance

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

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

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

Central Services Instance Installs a central services instance for ABAP (ASCS) and prepares the SAP global for ABAP (ASCS) host

94/168

PUBLIC

2009-04-30

4 4.6

Installation SAPinst Installation Options Installation Option Remarks

Central Services Instance (SCS) Database Instance Central Instance Dialog Instance

Installs a central services instance (SCS) Installs a database instance Installs a central instance with usage types or software units Installs a dialog instance
NOTE

● You might need to install dialog instances on 32-bit operating systems if you want to use 32-bit SAP NetWeaver components, such as Adobe document services. However, first check whether such 32bit 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. ● 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.
End of: HA (MSCS);HA (UNIX);HA (z/OS) |

Software Life-Cycle Options

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

Additional Preparation Options

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

Application Server

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

■ You might need to install dialog instances on 32-bit operating systems if you want to use 32-bit SAP NetWeaver components, such as Adobe

2009-04-30

PUBLIC

95/168

4 4.6

Installation SAPinst Installation Options Remarks

Installation Option

Java Add-In for ABAP

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. ■ 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. Choose the options available in this folder to install AS Java to an already installed SAP Solution Manager ABAP system: ■ Central or Distributed System ● Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS). ● Database Instance Java Add-In Installs the Java schema in the database of your ABAP system. ● 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. ■ High-Availability System ● Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) ● Database Instance Java Add-In Installs the Java schema in the database of your ABAP system ● Central Instance Java Add-In Adds AS Java to the existing ABAP system. ● Dialog Instance Installs an ABAP+Java dialog instance
NOTE

◆ 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 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:

96/168

PUBLIC

2009-04-30

4 4.7

Installation Oracle Database Software Installation Remarks

Installation Option

1.

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

System Copy

Uninstall

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

4.7 Oracle Database Software Installation
SAPinst prompts you to install the Oracle database.
CAUTION

This section does not apply to the installation of a Java Add-In to an existing ABAP system. Proceed as follows to install the Oracle database software:
Process Flow

1. 2. 3. 4. 5.

You update SAP-specific files in the Oracle stage area [page 97]. You perform steps for the AIX operating system [page 98] You run the Oracle Universal Installer [page 99] You install the current patch set [page 100] You install required interim patches [page 101]

4.7.1 Updating SAP-Specific Files in the Oracle Staging Area
SAPinst extracts the Oracle RDBMS software to the staging area, usually /oracle/stage/102_64/ database. The SAP folder located in /oracle/stage/102_64/database contains SAP-specific scripts as well as the response files. Before starting the Oracle software installation, you need to update this SAP folder so that the newest versions of the scripts or response files are used.

2009-04-30

PUBLIC

97/168

4 4.7

Installation Oracle Database Software Installation

Procedure

1.

Rename the original SAP folder by performing one of the following: ■ ■
mv /oracle/stage/102_64/database/Disk1/SAP /oracle/stage/102_64/database/Disk1/SAP_ORIG mv /oracle/stage/102_64/database/SAP /oracle/stage/102_64/database/SAP_ORIG

2. 3.

Download the file RDBMS_SAP_64.zip attached to SAP Note 819830 and copy it to a temporary location such as /tmp. Extract the zip file by performing one of the following: ■ ■
cd /oracle/stage/102_64/database unzip /tmp/RDBMS_SAP.zip cd /oracle/stage/102_64/database/Disk1 unzip /tmp/RDBMS_SAP.zip

You should now see the directory SAP extracted with the updated version of SAP-specific files.

4.7.2 Performing Steps for the AIX Operating System
To install the Oracle database software on the AIX operating system, you need to run the rootpre.sh script to adapt the AIX kernel and also execute a command as the root user.
Prerequisites

If several Oracle instances run on one computer, you must shut these down before adapting the kernel.
Procedure

1.

Run the rootpre.sh script as follows: 1. Log on to the system with user ora<dbsid> if you are not already logged on. 2. Change to the directory /oracle/stage/102_64/database/Disk1/rootpre using the following command:
cd /oracle/stage/102_64/database/Disk1/rootpre

3. 4. 5. 2.

Make sure that the user root is assigned the environment of ora<dbsid>:
su root

Call the script rootpre.sh:
./rootpre.sh

Log off with the user root:
exit

Remove any currently unused modules in kernel and library memory by entering the following command as user root:
# /usr/sbin/slibclean

98/168

PUBLIC

2009-04-30

4 4.7

Installation Oracle Database Software Installation

4.7.3 Running the Oracle Universal Installer
To install the Oracle database software you run the Oracle Universal Installer (OUI).
Procedure

1.

2.

3.

Log on as user ora<dbsid>. Since you are already logged on as user root, you can switch to user ora<dbsid> by entering the following command: su – ora<dbsid>. If you install Oracle database software with Release 10.2.0.1 or 10.2.0.x on a new operating system or a new operating system version, the Oracle Universal Installer might not yet recognize or support this operating system. Follow the instructions in SAP Note 980426. Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where <host_name> is the host on which you want to display the GUI of the Oracle Universal Installer (OUI).
Shell Used Command
DISPLAY=<host_name>:0.0 export DISPLAY

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

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

4.

Start the OUI with the user ora<dbsid> by entering one of the following: ■ ■
cd /oracle/stage/102_64/database/Disk1/SAP ./RUNINSTALLER cd /oracle/stage/102_64/database/SAP ./RUNINSTALLER

5.

You see a message that a response file is being generated. It might take several minutes before you see the OUI screen. Respond to the OUI as follows:
Prompt or Condition Action

When you run the OUI for the first time on this host, a dialog box, Specify File Locations Destination..., appears. This dialog box proposes the inventory location as / oracle/oraInventory and the installation group as dba. Available Product Components Product-Specific Prerequisite Checks This phase checks if all necessary requirements for installing and running the database have been met.

Accept the OUI proposal and continue by choosing Next.

Confirm the default selections by choosing Next. For items that are flagged as warnings or failed, review the cause for the warning or failure on screen and fix the problem if possible. Alternatively you can verify the items manually and confirm them by clicking the checkbox. You can find details about each check by clicking on the relevant item.

2009-04-30

PUBLIC

99/168

4 4.7

Installation Oracle Database Software Installation Prompt or Condition Action

Summary page When the Install step has completed, a dialog box appears.

Check the information on this page and then start the installation. Execute the file $ORACLE_HOME/root.sh with the user root, and confirm the dialog box by choosing OK. If this is the first time that the Oracle software has been installed on this host, the OUI also asks you to execute a second script, /oracle/oraInventory/ orainstRoot.sh, as the root user. Execute this script as well. Continue by choosing Next.

6.

7.

At the end of the installation, in case there are any Configuration Assistants that have been started automatically (for example, Oracle Net) choose Cancel and terminate the Net Config Assistant. You can ignore messages that some of the config assistants failed to complete successfully. The Installer finishes, reporting that the Oracle installation was successful. It also informs you about the services that it started. You can find the port numbers for these services in the $ORACLE_HOME/install/portlist.ini file. To exit the OUI, choose Exit and confirm the dialog box that appears.
NOTE

You can now access the Oracle 10.2 online documentation, which was installed during the last step. You can find the entry point to the Oracle online documentation at $ORACLE_BASE/ doc/index.htm.

4.7.4 Installing the Current Patch Set
After the Oracle database software installation, you need to install the current Oracle Database 10g Release 2 (10.2) patch set.
Prerequisites

■ For more information on the latest patch set available for Oracle 10.2 see SAP Note 871735. ■ For more information about how to install the patch set, see the patch set README file.
CAUTION

Do not perform any of the post-installation steps mentioned in the patch set README file. The post-installation steps are to be performed only on an existing Oracle 10.2 database. At this stage you have only installed the Oracle 10.2 software. The database itself is still not Oracle 10.2. Therefore, make sure that you do not perform the post-installation steps mentioned in the README file. ■ You only have to install the latest (that is, the current) patch set.
Procedure

1.

Log on at the operating system level with the ora<dbsid> user.

100/168

PUBLIC

2009-04-30

4 4.7

Installation Oracle Database Software Installation

2.

Install the patch set as described on the patch set README file. For more information, see SAP Note 839187.

4.7.5 Installing Required Interim Patches
After the Oracle database software installation, you need to install required interim patches, using the Oracle tool OPatch. You need these interim patches in addition to the current patch set.
RECOMMENDATION

You can install all the required interim patches in a single step using the Oracle tool MOPatch, which you can find at SAP Note 1027012. MOPatch can also download patches directly from SAP Service Marketplace and check for any potential patch conflicts.
Prerequisites

■ Make sure you have already installed the current patch set [page 100]. ■ Check SAP Note 871096 to find the list of required patches to be installed. ■ Check SAP Note 839182 for instructions on how to use OPatch.
Procedure

1. 2.

Log on at the operating system level as the ora<dbsid> user. Install the patches, following the instructions in SAP Note 839182.
NOTE

3.

You can apply the patches in any order. We recommend that you first copy the patches to a directory called ora_patches in $ORACLE_HOME. After all the patches have been successfully applied, you can query the status with the following command:
$ORACLE_HOME/OPatch/opatch lsinventory

This command lists all the patches that have been applied to the software installation.

2009-04-30

PUBLIC

101/168

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

5 5.1

Post-Installation Post-Installation Checklist

5 Post-Installation

5.1 Post-Installation Checklist
NOTE

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

3. 4. 5.

In a distributed or high-availability system you check whether you can log on to every instance of the SAP system that you installed. You configure user management [page 105]. You ensure user security [page 106]. You install the SAP license [page 111].
CAUTION

This step does not apply to the installation of a Java Add-In for an existing ABAP system. 6.
Only valid for: HA (UNIX) |

If you installed a high-availability system, you set up the licenses for high availability [page 112].
CAUTION

This step does not apply to the installation of a Java Add-In for an existing ABAP system.
End of: HA (UNIX) |

7. 8.

You apply the latest kernel and Support Package stacks [page 113]. You configure the remote connection to SAP support [page 114].
CAUTION

9.

This step does not apply to the installation of a Java Add-In for an existing ABAP system. You install the SAP Online Documentation [page 114].
CAUTION

This step does not apply to the installation of a Java Add-In for an existing ABAP system. 10. You perform initial ABAP configuration [page 114].
CAUTION

This step does not apply to the installation of a Java Add-In for an existing ABAP system.

2009-04-30

PUBLIC

103/168

5 5.2

Post-Installation Logging On to the Application Server

11. You perform initial Java configuration [page 119]. 12. On the database instance host, you perform the Oracle-specific post-installation steps [page 120].
CAUTION

13. 14. 15. 16.

This step does not apply to the installation of a Java Add-In for an existing ABAP system. If you want to use Adobe Document Services (ADS), you perform post-installation steps for Adobe Document Services [page 121]. If required, you can install the SAP Solution Manager Enterprise Edition Add-On [page 123]. You perform a full backup of the installation [page 123]. You configure SAP Solution Manager [page 124].

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 124]).
ABAP Users User User Name Client

SAP system user

SAP* DDIC

000, 001, 066 000, 001

Java User User User Name Storage: ABAP System
J2EE_ADMIN (default) or the name you gave this user during the

Administrator

installation process. Prerequisites

■ The SAP system is up and running. ■ 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: ■ SAP GUI for Windows: Choose Start All Programs SAP Front End SAP Logon . ■ SAP GUI for Java: Choose Start All Programs SAP Clients SAP GUI for Java<Release> .

104/168

PUBLIC

2009-04-30

5 5.3

Post-Installation Configuring User Management NOTE

You can alternatively enter the command guilogon in the SAP GUI installation directory to start SAP GUI for Java. 2. 3. The SAP Logon appears. Create a logon entry for the newly installed system in the SAP Logon. For more information about creating new logon entries, press F1 . 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

2.

The start page of the SAP NetWeaver Application Server Java appears in the Web browser. Log on by pressing the link of any of the provided applications, for example SAP NetWeaver Administrator or System Information.
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

105/168

5 5.4

Post-Installation Ensuring User Security

SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Identity Management User Management of the Application Server Java Configuring User Management UME Data Sources
http://help.sap.com/nw70

5.4 Ensuring User Security
You need to ensure the security of the users that SAPinst created during the installation. The tables below at the end of this section list these users: ■ Operating system users ■ SAP system users ■ 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: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Security Network and Transport Layer Security
CAUTION

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

106/168

PUBLIC

2009-04-30

5 5.4

Post-Installation Ensuring User Security

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 User Name
<sapsid>adm <smdsid>adm

Comment

Operating system user

ora<dbsid>

Oracle database user

SAP<SCHEMA_ID>

SYSTEM SYS OUTLN DBSNMP

SAP system administrator Administrator for the Diagnostics Agent Oracle database administrator (that is, the owner of the database files) Oracle database owner (that is, the owner of the database tables) Oracle standard database user Oracle standard database user Oracle standard database user Oracle standard database user

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
SAP*

Comment

SAP system user

This user exists in at least clients 000, 001, and 066 of the ABAP system.
RECOMMENDATION

DDIC

We recommend that you use strong password and auditing policies for this user. This user exists in at least clients 000, 001, and 066 of the ABAP system.
RECOMMENDATION

EARLYWATCH SAPCPIC

Administrator

The name that you gave this user during the installation or the default name J2EE_ADMIN

We recommend that you use strong password and auditing policies for this user. This user exists in at least client 066 of the ABAP system. This user exists in at least clients 000 and 001 of the ABAP system This user exists in at least clients 000 and 001 of the ABAP system and in the User Management Engine (UME) of

2009-04-30

PUBLIC

107/168

5 5.4 User

Post-Installation Ensuring User Security User Name Comment

the Java system. It has administrative permissions for user management.
RECOMMENDATION

Guest

Communication user for the J2EE Engine SDM Users for Adobe Document Services (ADS)

The name that you gave this user during the installation or the default name J2EE_GUEST The name that you gave this user during the installation or the default name SAPJSF SDM
ADSUser

ADS_AGENT

Data supplier user The name that you gave this for System user during the installation Landscape Directory The recommended name is (SLD) SLDDSUSER. (optional)

We recommend that you use strong password and auditing policies for this user. 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 anonymous access. 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 a remote function call (RFC) between the ABAP system and the Java system. This user is used to access the Software Deployment Manager (SDM) in the Java system. 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 basic authentication. 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. 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.
NOTE

ABAP API user for System Landscape Directory (SLD) (optional)

The name that you gave this user during the installation The recommended name is SLDAPIUSER.

SAPinst created this user automatically if you chose Configure local SLD during the installation. 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.
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.

108/168

PUBLIC

2009-04-30

5 5.4 User

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

Guest

The name that you gave this user during the installation or the default name
J2EE_GUEST

Communication user for the J2EE Engine

The name that you gave this user during the installation or the default name
SAPJSF

SDM

SDM

Users for Adobe Document Services (ADS)

ADSUser

ADS_AGENT

Data supplier user for The name that you gave this user during System Landscape the installation Directory (SLD) (optional) The recommended name is SLDDSUSER.

We recommend that you use strong password and auditing policies for this user. 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 anonymous access. 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 remote function call (RFC) between the ABAP system and the Java system. This user is used to access the Software Deployment Manager (SDM) in the Java system. 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 basic authentication. 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. 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.
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.

2009-04-30

PUBLIC

109/168

5 5.4

Post-Installation Ensuring User Security

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:
User User Name Comment

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
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 during the installation or the default 001. name PIDIRUSER
CAUTION

Landscape Directory Service User

Do not log on with this user. It is used by the system for internal communication. The name that you gave this user This user exists in SAP system client during the installation or the default 001. name PILDUSER
CAUTION

Do not log on with this user. It is used by the system for internal communication. 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 during the installation or the default 001. name PIRWBUSER
CAUTION

Do not log on with this user. It is used by the system for internal communication. 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 during installation or the default name PIISUSER

Do not log on with this user. It is used by the system for internal communication. This user exists in SAP system client 001.

110/168

PUBLIC

2009-04-30

5 5.5 User

Post-Installation Installing the SAP License User Name Comment CAUTION

Management Server Service User

The name that you gave this user during installation or the default name PILSADMIN

Do not log on with this user. It is used by the system for internal communication. This user exists in SAP system client 001.
CAUTION

Exchange Infrastructure Administrator

The name that you gave this user during installation or the default name PISUPER

Do not log on with this user. It is used by the system for internal communication. This user exists in SAP system client 001.
CAUTION

Exchange Infrastructure Communicator

The name that you gave this user during installation or the default name PI_JCD_RFC

This user has extensive authorizations. Make sure that you assign a secure password. This user exists in SAP system client 001.
CAUTION

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

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

5.5 Installing the SAP License
CAUTION

This section does not apply to the installation of a Java Add-In to an existing ABAP system.

2009-04-30

PUBLIC

111/168

5 5.6

Post-Installation High Availability: Setting Up Licenses

You must install a permanent SAP license. When you install your SAP system, a temporary license is automatically installed. This temporary license allows you to use the system for only 4 weeks from the date of installation.
CAUTION

Before the temporary license expires, you must apply for a permanent license key from SAP. We recommend that you apply for a permanent license key as soon as possible after installing your system.
Procedure

Install the SAP license as described in the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Cross-NetWeaver Configurations SAP License Keys
Only valid for: HA (UNIX) |

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

More Information

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

5.6 High Availability: Setting Up Licenses
CAUTION

This section does not apply to the installation of a Java Add-In to an existing ABAP system. 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 111] 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.

112/168

PUBLIC

2009-04-30

5 5.7

Post-Installation Applying the Latest Kernel and Support Package Stacks

Procedure

1. 2. 3.

4. 5. 6.

Make sure that the ABAP central services instance (ASCS) on the primary host, node A, is running. To find the hardware ID of the primary host, log on to any application server instance of the SAP system and call transaction SLICENSE. 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. To obtain the two license keys, enter the hardware IDs for the primary and backup hosts at:
http://service.sap.com/licensekey

To import the files containing the two licenses, log on to any application server instance of the SAP system and call transaction SLICENSE. 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.

2.

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. Apply the required Support Package stacks as follows: ■ Check SAP Note 1276022 for information about the required Support Package stacks and about how to obtain it. ■ Apply ABAP Support Package stacks using the Support Package Manager (SPAM). For more information, see the SAP Library at:

2009-04-30

PUBLIC

113/168

5 5.8

Post-Installation Configuring Remote Connection to SAP Support

3.

SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Maintenance Support Package Manager ■ Apply Java Support Package stacks using the Java Support Package Manager (JSPM). For more information, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Maintenance Java Support Package Manager You can now start configuring SAP Solution Manager. For more information, see Configuring SAP Solution Manager [page 124].
http://help.sap.com/nw70

5.8 Configuring Remote Connection to SAP Support
CAUTION

This section does not apply to the installation of a Java Add-In to an existing ABAP system. 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

This section does not apply to the installation of a Java Add-In to an existing ABAP system. 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

This section does not apply to the installation of a Java Add-In to an existing ABAP system.

114/168

PUBLIC

2009-04-30

5 5.10

Post-Installation Performing Initial ABAP Configuration

When you have installed your SAP ABAP system, you have to perform the following initial configuration steps: ■ Perform a consistency check ■ Configure the transport management system ■ Perform basic operations ■ Configure system parameters ■ Configure the number of work processes ■ Configure kernel parameters ■ Install languages and performing language transport ■ Configure the integrated Internet Transaction Server (ITS) ■ Maintain your company address for initial users ■ Configure AS ABAP to support Secure Socket Layer (SSL) ■ Configure Fully Qualified Domain Names (FQDN) ■ 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 104].
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: ■ Completeness of installation ■ Version compatibility between the SAP release and the operating system The initial consistency check determines whether: ● The release number in the SAP kernel matches the release number defined in the database system ● The character set specified in the SAP kernel matches the character set specified in the database system ● 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. ■ Accessibility of the message server ■ Availability of all work process types

2009-04-30

PUBLIC

115/168

5 5.10

Post-Installation Performing Initial ABAP Configuration

■ 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. For more information, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability 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. Only valid for: HA (UNIX) | 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.
End of: HA (UNIX) |

For more information, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics Change and Transport System
Performing Basic Operations

1.

Go to the SAP Library at: SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Choose the relevant sections to perform the following operations:
http://help.sap.com/nw70 Section in SAP Documentation

2.

Operation

Set up operation modes – transaction RZ04 Set up logon groups – transaction SMLG Set up administrators Schedule background jobs

Solution Life Cycle Management by Key Capability System Management Configuration Operation Modes Solution Life Cycle Management by Key Capability System Management Configuration Logon Load Balancing SAP Logon Solution Life Cycle Management by Key Capability System Management Background Processing Authorizations for Background Processing Solution Life Cycle Management by Key Capability System Management Background Processing

116/168

PUBLIC

2009-04-30

5 5.10

Post-Installation Performing Initial ABAP Configuration Section in SAP Documentation

Operation

Install a printer Configure the system log

Solution Life Cycle Management by Key Capability System Management SAP Printing Guide Solution Life Cycle Management by Key Capability System Management Tools for Monitoring the System System log Configuring the System Log

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: 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 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: ● If you want to use English only, you must activate the default language settings once. ● 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: 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 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-

2009-04-30

PUBLIC

117/168

5 5.10

Post-Installation Performing Initial ABAP Configuration

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 For more information about how to configure the integrated SAP ITS, 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 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: 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 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: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP 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:

118/168

PUBLIC

2009-04-30

5 5.11

Post-Installation Performing Initial Java Configuration

http://help.sap.com/nw70

NetWeaver Library Customizing

SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability

5.11 Performing Initial Java Configuration
When you have installed your SAP Java system, you have to perform the following initial configuration steps: ■ Create a second administrator user ■ Check and configure the necessary communication ports ■ Check the Java Virtual Machine (Java VM) settings 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). ■ For more information about Java ports, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine Reference AS Java Ports ■ You can check and configure communication ports using the Visual Administrator or the Config Tool: ● For more information about how to start and handle the Visual Administrator, see the SAP Library at:

2009-04-30

PUBLIC

119/168

5 5.12

Post-Installation Performing Oracle-Specific Post-Installation Steps

SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine Administration Tools Visual Administrator ● For more information about how to start and handle the Config Tool, see the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine Administration Tools Config Tool
http://help.sap.com/nw70 Checking the Java VM Memory Settings

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

5.12 Performing Oracle-Specific Post-Installation Steps
CAUTION

This section does not apply to the installation of a Java Add-In to an existing ABAP system. You have to perform the following Oracle-specific post-installation steps:
Procedure
Security Setup for the Oracle Listener

If the Oracle security setup defined by the standard installation is not restrictive enough for your purposes, see SAP Note 186119 to configure the Oracle listener to accept only connections from specific hosts.

120/168

PUBLIC

2009-04-30

5 5.13

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

Checking the Recommended Oracle Database Parameters

When installing the Oracle database, a standard database parameter set is used. To take into account the size and configuration of your SAP system and to enable new Oracle features, check and apply the parameter settings as described in SAP Note 830576. You can find an automated script in SAP Note 1171650 to help you check whether your SAP system complies with the database parameter recommendations at any given point in time.
Updating Oracle Optimizer Statistics

To update the Oracle optimizer statistics, perform the following: 1. Execute the following commands as the ora<dbsid> user:
brconnect -u / -c -f stats -t system_stats; brconnect -u / -c -f stats -t oradict_stats;

2.

Execute the following commands with SQLPlus:
SQL> exec dbms_scheduler.disable('GATHER_STATS_JOB'); SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB'); SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');

Checking the Version of the Oracle Instant Client

If necessary, install the most up-to-date version of the Oracle Instant Client, as described in SAP Note 819829.
Enabling Database Monitoring

Follow the instructions in SAP Note 706927 to enable database monitoring in the DBA Cockpit.
Configuring and Operating the Oracle Database

You have to configure your Oracle database before you start operating it with the SAP system. For information about Oracle database configuration and administration, see the documentation 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 Platform-Wide Services Database Support Oracle .

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

2009-04-30

PUBLIC

121/168

5 5.14

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

Prerequisites

Adobe document services are installed on your system.
Procedure

■ Check the ADS configuration as described in the Adobe Document Services Configuration Guide at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Business Task Management Adobe Document Services (Configuration) Adobe Document Services Configuration Guide Configuring the Web Service Securing Access to the Web Service Configuration Check ■ Perform manual configuration as described in the Adobe Document Services Configuration Guide at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Business Task Management Adobe Document Services (Configuration) Adobe Document Services Configuration Guide
More Information

A printable version of the document Configuration Guide for SAP Interactive Forms by Adobe is available at: http://sdn.sap.com/irj/sdn/adobe Installation & Configuration SAP Interactive Forms by Adobe – Configuration Guides Configuration Guide for SAP Interactive Forms by Adobe

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

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

This documentation is also available in PDF form in the User Manual – SLD of SAP NetWeaver 7.0 at http:// www.sdn.sap.com/irj/sdn/nw-sld.

122/168

PUBLIC

2009-04-30

5 5.15

Post-Installation Installing the SAP Solution Manager Enterprise Edition Add-On (Optional)

5.15 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.16 Performing a Full Installation Backup
You must perform a full offline backup at the end of the installation. This procedure also describes how to use the back-up data for a restore.
CAUTION

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

■ You have completed client maintenance, such as the client copy. For more information, see Configuring SAP Solution Manager [page 124]. ■ You have logged on [page 104] as user <sapsid>adm and stopped the SAP system and database [page 149].
Procedure

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

The following only applies to a standard installation. 1. Back up the following file systems: ■ /usr/sap/<SAPSID> ■ /usr/sap/trans ■ <sapmnt>/<SAPSID> ■ Home directory of the user <sapsid>adm ■ All database-specific directories Proceed as follows:

2009-04-30

PUBLIC

123/168

5 5.17

Post-Installation Configuring SAP Solution Manager

1. 2.

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

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

2.

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. 1. 2. 3. Log on as user root. Go to the location in your file system where you want to restore the backup image. Execute the following commands to restore the data: ■ Restoring the data from tape:
cat <tape_device> | compress —cd | tar —xf —

■ Restoring the data from the file system:
cat ARCHIVENAME.tar.Z | compress —cd | tar —xf — Performing a Full Database Backup

1. 2.

Configure your third-party backup tool, if used. Perform a full database backup (preferably offline). If you use BR*TOOLS for the backup, refer to BR*Tools for Oracle DBA in the SAP Database Guide: Oracle (BC-DB-ORA-DBA). This documentation is available 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 Platform-Wide Services Database Support Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA)

5.17 Configuring SAP Solution Manager
You have to perform initial basic configuration and scenario specific configuration for your newly installed SAP Solution Manager system.

124/168

PUBLIC

2009-04-30

5 5.17

Post-Installation Configuring SAP Solution Manager

Procedure

Proceed as described in the following documentations available at http://service.sap.com/ instguides SAP Components SAP Solution Manager Release 7.0 EHP1 : ■ 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. ■ SAP Enhancement Package 1 for SAP Solution Manager Security Guide

2009-04-30

PUBLIC

125/168

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

6 6.1

Additional Information Integration of LDAP Directory Services

6 Additional Information

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

■ ■ ■ ■ ■ ■ ■

Integration of LDAP Directory Services [page 127] Setting up Swap Space for AIX [page 131] Creating AIX Groups and Users [page 132] Setting Up File Systems and Raw Devices for AIX [page 133] Dialog Instance Installation for an Upgraded System: Updating Instance Profiles [page 134] Mounting a CD / DVD for AIX [page 136] Exporting and Mounting Directories via NFS for AIX [page 137]

Post-Installation

■ Starting and stopping the SAP system [page 145] ■ If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page 152] ■ Accessing the SAP Java documentation [page 153] ■ Initial Configuration for System Landscape Directory (SLD) [page 155] ■ Initial Configuration of Adobe Document Services (ADS) [page 154] ■ Heterogeneous SAP System Installation [page 156] ■ Troubleshooting [page 156]
Deleting an SAP System or SAP Instance

■ Deleting an SAP System [page 157] ■ Deleting a Diagnostics Agent [page 159]

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

2009-04-30

PUBLIC

127/168

6 6.1

Additional Information Integration of LDAP Directory Services

enables important information in a corporate network to be stored centrally on a server. The advantage of storing information centrally for the entire network is that you only have to maintain data once, which avoids redundancy and inconsistency. If an LDAP directory is available in your corporate network, you can configure the SAP system to use this feature. For example, a correctly configured SAP system can read information from the directory and also store information there.
NOTE

The SAP system can interact with the Active Directory using the LDAP protocol, which defines: ■ The communication protocol between the SAP system and the directory ■ How data in the directory is structured, accessed, or modified If a directory other than the Active Directory also supports the LDAP protocol, the SAP system can take advantage of the information stored there. For example, if there is an LDAP directory on a UNIX or Windows server, you can configure the SAP system to use the information available there. In the following text, directories other than the Active Directory that implement the LDAP protocol are called generic LDAP directories.
CAUTION

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

You can only configure the SAP system for Active Directory services or other LDAP directories if these are already available on the network. As of Windows 2000 or higher, the Active Directory is automatically available on all domain controllers. A generic LDAP directory is an additional component that you must install separately on a UNIX or Windows server.
Features

In the SAP environment, you can exploit the information stored in an Active Directory or generic LDAP directory by using: ■ SAP Logon ■ The SAP Microsoft Management Console (SAP MMC) ■ The SAP Management Console (SAP MC) For more information about the automatic registration of SAP components in LDAP directories and the benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information in Directory Services at

128/168

PUBLIC

2009-04-30

6 6.1

Additional Information Integration of LDAP Directory Services

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0a0d051eae2-2b10-e1ac-f3a7f6494c53

For more information about the SAP MC and about how to configure it to access LDAP Directories, see the documentation SAP Management Console at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE Engine Administration Tools SAP Management Console
SAP Logon

Instead of using a fixed list of systems and message servers, you can configure the SAP Logon in the sapmsg.ini configuration file to find SAP systems and their message servers from the directory. If you configure SAP logon to use the LDAP directory, it queries the directory each time Server or Group selection is chosen to fetch up-to-date information on available SAP systems. To use LDAP operation mode, make sure that the sapmsg.ini file contains the following:
[Address] Mode=LDAPdirectory LDAPserver= LDAPnode= LDAPoptions=

Distinguish the following cases: ■ If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For more information, see the SAP system profile parameter ldap/options. ■ You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either of the following is true: ● The client is not located in the same domain forest as the Active Directory ● The operating system does not have a directory service client (Windows NT and Windows 9X without installed dsclient). For more information, see the SAP system profile parameter ldap/servers. ■ For other directory services, you can use LDAPnode to specify the distinguished name of the SAP root node. For more information, see the SAP system profile parameter ldap/saproot.
SAP MMC

The SAP MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central location. It is automatically set up when you install an SAP system on Windows. If the SAP system has been prepared correctly, the SAP MMC presents and analyzes system information that it gathers from various sources, including the Active Directory. Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can read system information straight from the directory that automatically registers changes to the system

2009-04-30

PUBLIC

129/168

6 6.1

Additional Information Integration of LDAP Directory Services

landscape. As a result, up-to-date information about all SAP application servers, their status, and parameter settings is always available in the SAP MMC. If you need to administer distributed systems, we especially recommend that you use the SAP MMC together with Active Directory services. You can keep track of significant events in all of the systems from a single SAP MMC interface. You do not need to manually register changes in the system configuration. Instead, such changes are automatically updated in the directory and subsequently reflected in the SAP MMC. If your SAP system is part of a heterogeneous SAP system landscape that comprises systems or instances both on UNIX and Windows operating systems, you can also use the SAP MMC for operating and monitoring the instances running on UNIX.
SAP MC

The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central location. If the SAP system has been prepared correctly, the SAP MC presents and analyzes system information that it gathers from various sources, including generic LDAP Directory. Integrating a generic LDAP Directory as a source of information has advantages for the SAP MC. It can read system information straight from the directory that automatically registers changes to the system landscape. As a result, up-to-date information about all SAP application servers, their status, and parameter settings is always available in the SAP MC.
Configuration Tasks for LDAP Directories

This section describes the configuration tasks you have to perform for the Active Directory or other (generic) LDAP directories.
Configuration Tasks for Active Directory

To enable an SAP system to use the features offered by the Active Directory, you must configure the Active Directory so that it can store SAP system data. To prepare the directory, you use SAPinst to automatically: ■ Extend the Active Directory schema to include the SAP-specific data types ■ Create the domain accounts required to enable the SAP system to access and modify the Active Directory. These are the group SAP_LDAP and the user sapldap. ■ Create the root container where information related to SAP is stored ■ Control access to the container for SAP data by giving members of the SAP_LDAP group permission to read and write to the directory You do this by running SAPinst on the Windows server on which you want to use Active Directory Services and choosing <Your SAP product> Software Life-Cycle Options LDAP Registration Active Directory Configuration . For more information about running SAPinst on Windows, see the documentation Installation Guide — <Your SAP product> on Windows: <Database>.

130/168

PUBLIC

2009-04-30

6 6.2

Additional Information 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: ■ Choose Physical & Logical Storage Logical Volume Manager Paging Space List All Paging Spaces ■ Enter this command:
lsps -a

2. 3.

Check if there is sufficient swap space (see Hardware and Software Requirements [page 19]). 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

131/168

6 6.3

Additional Information Creating AIX Groups and Users

6. 7.

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

5. 6.

If you are using large file enabled file systems, set the field Soft FILE size to -1 (unlimited). Change field Soft DATA segment to -1. Change field Soft STACK size to -1. 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:

132/168

PUBLIC

2009-04-30

6 6.4

Additional Information 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

1. 2. 3. 4.

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

More Information

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

6.4 Setting Up File Systems and Raw Devices for AIX
Procedure
Setting up File Systems NOTE

If you want to create file systems larger than 2 GB, see SAP Note 129439. Note that large files can lead to performance degradation due to access synchronization over the nodes. For performance reasons, smaller files are recommended for very active data. 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. 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.

2.

2009-04-30

PUBLIC

133/168

6 6.5

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

4.

Select the logical volume with the desired size. Enter mount point as given in the file system list files.
EXAMPLE /oracle/<DBSID>/sapdata1

5. 6.

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

Setting up Raw Devices

1. 2.

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

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

of raw log.vol>.

3.

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

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

134/168

PUBLIC

2009-04-30

6 6.5

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

2.

3.

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

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

number> is used by the NIM server of AIX.

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

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

4.

... Edit the instance profile of the central services instance (SCS) and do the following:
Only valid for: HA (UNIX) |

NOTE

In a high-availability system, also do this for the instance profile of the ABAP central services instance (ASCS).
End of: HA (UNIX) |

■ Set rdisp/msserv to 0. ■ Set rdisp/msserv_internal to the port number assigned to rdisp/msserv.
EXAMPLE

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

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

2009-04-30

PUBLIC

135/168

6 6.6

Additional Information Mounting a CD / DVD for AIX

5.

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

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

1. 2.

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

3.

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

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

136/168

PUBLIC

2009-04-30

6 6.7

Additional Information Exporting and Mounting Directories via NFS for AIX

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

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

5.

Mount the directory on the host where the additional instance runs. 1. Enter the command smitty. 2. Choose Communications Applications and Services NFS Network File System (NFS) Add a File System for Mounting . 3. Enter the path name of the mount point. 4. Enter the path name of the remote directory (the directory of the central instance). 5. Enter the host where the remote directory resides. 6. Set Mount now, add entry to /etc/filesystems or both to both. 7. Set /etc/filesystems entry will mount the directory on system RESTART to yes. 8. Change Mount file system soft or hard to soft and press ENTER.

2009-04-30

PUBLIC

137/168

6 6.8

Additional Information 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)

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

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
F1

Description

Function key Menu option

File

Exit

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

Menu option

SAPinst

Log Browser

If you need to log off during the installation from the host where you control the installation with SAPinst GUI, the installation continues while you are logged off. You can later reconnect to the same SAPinst installation from the same or another host. For more information, see Starting SAPinst GUI Separately [page 142]. Displays the Log Viewer dialog This dialog enables you to access the following log files directly: ■ Installation log (sapinst_dev.log) ■ Log files from the SAPinst GUI server

138/168

PUBLIC

2009-04-30

6 6.8

Additional Information Additional Information About SAPinst Label Description

Input Type

Menu option

SAPinst

Cancel

Message button Message button

Retry Stop

Message button

Continue

These log files might help you during troubleshooting with SAPinst [page 156]. Cancels the installation with the following options: ■ Stop Stops the installation (SAPinst GUI, SAPinst, and the GUI server) without further changing the installation files You can restart and continue the installation later from this point. ■ Continue Continues the installation Performs the installation step again (if an error has occurred) Stops the installation without further changing the installation files You can continue the installation later from this point. Continues with the option you chose previously

6.8.2 Interrupted Installation with SAPinst
The SAP system installation might be interrupted for one of the following reasons: ■ An error occurred during the Define Parameters or Execute phase: SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error. ■ You interrupted the installation by choosing Cancel in the SAPinst menu. The following table describes the options in the dialog box:
Option Definition

Retry

Stop

Continue

SAPinst retries the installation from the point of failure without repeating any of the previous steps. This is possible because SAPinst records the installation progress in the keydb.xml file. We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry. If the same or a different error occurs, SAPinst displays the same dialog box again. SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server. SAPinst records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps (see the procedure below). SAPinst continues the installation from the current point.

2009-04-30

PUBLIC

139/168

6 6.8 Option

Additional Information Additional Information About SAPinst Definition

View Log
NOTE

Access installation log files.

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

This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to continue an interrupted installation after an error situation. 1. Log on to your local UNIX host as user root.
CAUTION

2.

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

3.

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

4.

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

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

Alternative

Run a New Option

SAPinst does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installationspecific files to a backup directory. Afterwards, you can no longer continue the old installation option. For the backup directory, the following naming convention is used: <log_day_month_year_hours_minutes_seconds>.
EXAMPLE
log_01_Oct_2008_13_47_56

CAUTION

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

140/168

PUBLIC

2009-04-30

6 6.8

Additional Information Additional Information About SAPinst Behavior

Alternative

Continue with the Old Option

processes currently running on these files and folders, they might no longer function properly. SAPinst continues the interrupted installation option from the point of failure.

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

■ The remote host meets the prerequisites as described in Prerequisites in Running SAPinst [page 87]. ■ Both computers are in the same network and can ping each other. To test this: 1. Log on to your remote host and enter the command ping <local host>. 2. Log on to the local host and enter the command ping <remote host>.
Procedure

1.

Log on to your remote host as user root.
CAUTION

2. 3. 4.

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

2009-04-30

PUBLIC

141/168

6 6.8

Additional Information Additional Information About SAPinst Shell Used Command
JCE_POLICY_ZIP=<policy zip archive> export JCE_POLICY_ZIP

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

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

5.

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

For more information about SAPinst, see Running SAPinst [page 87]. 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 142].

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: ■ You have logged off from SAPinst. If you logged off during the installation and you later want to reconnect to the installation while it is still running, you can start SAPinst GUI separately. ■ You want to perform a remote installation [page 141]. If the GUI client runs on a different host from SAPinst and the GUI server, you have to start the GUI client separately on the local host.
CAUTION

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

1. 2. 3.

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

142/168

PUBLIC

2009-04-30

6 6.8

Additional Information Additional Information About SAPinst

4. 5.

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

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

6.

Start the GUI client by double-clicking sapinstgui.exe The GUI client starts and tries to connect to the GUI server and SAPinst, using the local host as default. If SAPinst and the GUI server are running on another host, the GUI client cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of the host on which SAPinst is running and choose Log on. The first screen of the installation appears and you can perform the remote installation from your local host.
NOTE

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

1.

Log on as user root.
CAUTION

2. 3.

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

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

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

4.

Mount your Installation Master DVD.

2009-04-30

PUBLIC

143/168

6 6.8

Additional Information Additional Information About SAPinst NOTE

5.

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

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

6.

Start the GUI client by executing ./sapinstgui The GUI client starts and tries to connect to the GUI server and SAPinst, using the local host as default. 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.

144/168

PUBLIC

2009-04-30

6 6.9

Additional Information 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 43]. ■ If there is more than 1 entry for the same port number, this is not an error.

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

6.9.1 Starting and Stopping SAP System Instances Using the SAP Management Console
You can start and stop all SAP system instances (except the database instance) and the Diagnostics Agent using the SAP Management Console (SAP MC). You have to start and stop the database instance as described in Starting and Stopping the SAP System Using startsap and stopsap [page 149].
NOTE

If your newly installed SAP system is part of a heterogeneous SAP system landscape comprising systems or instances on Windows platforms, you can also start and stop it from a Windows system or instance using the Microsoft Management Console (SAP MMC). For more information about handling the MMC, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS SAP Microsoft Management Console: Windows
Prerequisites

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

2009-04-30

PUBLIC

145/168

6 6.9

Additional Information Starting and Stopping SAP System Instances

Procedure
Starting the Web-Based SAP Management Console

1.

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

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

This starts the SAP MC Java applet.
NOTE

2.

If your browser displays a security warning message, choose the option that indicates that you trust the applet. Choose Start. The SAP Management Console appears. By default, the instances installed on the host you have connected to are already added in the SAP Management Console.
NOTE

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

1. 2. 3. 4.

In the navigation pane, open the tree structure and navigate to the system node that you want to start. Select the system or instance and choose Start from the context menu. In the Start SAP System(s) dialog box, choose the required options. Choose OK. The SAP MC starts the specified system or system instances.
NOTE

The system might prompt you for the credentials of the SAP system administrator. To complete the operation, you must have administration permissions. Log in as user <sapsid>adm.
Starting the Instances of a Distributed SAP System Separately

If you need to start the instances of an SAP system separately – for example when you want to start a distributed or a high-availability system – proceed as follows: 1. Start the database instance. 2. Start the central services instance SCS<Instance_Number>.

146/168

PUBLIC

2009-04-30

6 6.9

Additional Information Starting and Stopping SAP System Instances
Only valid for: HA (UNIX) |

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

3. 4. 1. 2. 3.

Start the central instance DVEBMGS<Instance_Number>. Start dialog instances D<Instance_Number>, if there are any. Select the system or instance you want to stop and choose Stop from the context menu. In the Stop SAP System(s) dialog box, choose the required options. Choose OK. The SAP MC stops the specified system or system instances.
NOTE

Stopping SAP Systems or Instances

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

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

4.

Stop the database instance.

Registering Systems and Instances in the SAP Management Console

You can extend the list of systems and instances displayed in the SAP MC, so that you can monitor and administer all systems and instances from a single console. You can configure the SAP MC startup view to display the set of systems and instances you want to manage.
Prerequisites

The SAP MC is started.

2009-04-30

PUBLIC

147/168

6 6.9

Additional Information Starting and Stopping SAP System Instances

Registering SAP Systems or Instances

1. 2.

In the SAP MC, choose File New . In the New System dialog box, enter the required data.
NOTE

3.

If you have already registered systems in the SAP MC, they are stored in the history. To open the System’s History dialog box, choose the browsing button next to the Instance Nr. field. Select an instance of the system that you want to add and choose OK. Choose Finish.

Registering the Instances of a Distributed SAP System Separately

1. 2. 3.

In the SAP MC, choose File New . In the New System dialog box, enter the required data and deselect Always show all SAP Instances. The SAP MC displays the SAP system node, the instance node, and the relevant database node in a tree view in the navigation pane.
NOTE

To view all instances of the respective SAP system, select the relevant system node and choose Add Application Server from the context menu.
Configuring the SAP MC View

■ You can choose the instances that the SAP MC displays automatically on startup: 1. In the Settings dialog box, select History. 2. In the right-hand pane, choose the instance you want the SAP MC to display on startup. 3. Choose the << button. 4. Choose Apply and then OK. Similarly, you can remove instances from the startup configuration. ■ You can save the current configuration in a file: 1. Choose File Save Landscape . 2. In the Save dialog box, enter the required data. 3. Choose Save. ■ You can load a configuration from a file: 1. Choose File Load Landscape . 2. In the Open dialog box, select the configuration you want to load. 3. Choose Open.
More Information

For more information about the SAP Management Console, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS SAP Management Console

148/168

PUBLIC

2009-04-30

6 6.9

Additional Information Starting and Stopping SAP System Instances

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 145]).
Prerequisites

■ You have checked the default profile /<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameter login/system client and set the value to the correct production system client. For example, the entry must be login/system_client = 001 if your production client is 001. ■ You have checked the settings for Java Virtual Machine parameters as described in SAP Note 723909. ■ You have logged on to the SAP system hosts as user <sapsid>adm. ■ For more information about how to start or stop database-specific tools, see the database-specific information in this documentation and the documentation from the database manufacturer. ■ If you want to use startsap or stopsap (for example, in a script) and require the fully qualified name of these SAP scripts, create a link to startsap or stopsap in the home directory of the corresponding user.
CAUTION

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

For example, enter:
startsap 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>.
Only valid for: HA (UNIX) |

The instance name of the ABAP central services instance is ASCS<Instance_Number>.
End of: HA (UNIX) |

Procedure
Starting SAP System Instances

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

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

2009-04-30

PUBLIC

149/168

6 6.9

Additional Information Starting and Stopping SAP System Instances 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. ■ In a distributed system, proceed as follows: 1. On the database host, enter:
startdb

2. 3.

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

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

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

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

150/168

PUBLIC

2009-04-30

6 6.9

Additional Information Starting and Stopping SAP System Instances R3 or stopsap J2EE to

For ABAP+Java systems, you can enter either the command stopsap stop the SAP instance comprising both ABAP and J2EE. ■ In a distributed system, proceed as follows: 1. On the dialog instance host, enter the following command:
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 145]).
Prerequisites

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

1. 2.

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

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

Starting Diagnostics Agents Globally

To start Diagnostics Agents globally, enter this command:

2009-04-30

PUBLIC

151/168

6 6.10

Additional Information 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. 2.

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

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

Stopping Diagnostics Agents Globally

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

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

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

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

Enter the required data.

152/168

PUBLIC

2009-04-30

6 6.11

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

2.

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

Architecture Manual

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

Administration Manual

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

■ ■ ■ ■

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

2009-04-30

PUBLIC

153/168

6 6.12

Additional Information Initial Technical Configuration for Adobe Document Services Manual Contents CAUTION

Java Development Manual

Migration Manual

Make sure that you check the mandatory post-installation procedures listed in the Administration Manual under J2EE Engine Installation Information Post-Installation Procedures . This manual describes the technologies for developing Java-based business applications. It explains how to use the SAP NetWeaver Developer Studio, which is the SAP Java development environment. This manual contains all the information you need to migrate an application created in J2EE Engine 6.20.

More Information

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

6.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: ■ 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 106]. ■ 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 106]. ■ SAPinst creates service user ADS_AGENT in the ABAP Environment. ■ SAPinst creates an ABAP connection for basic authentication. ■ SAPinst creates destination service FP_ICF_DATA_<SAPSID>. ■ 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: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's Guide Business Task Management Adobe Document Services

154/168

PUBLIC

2009-04-30

6 6.13

Additional Information Initial Technical Configuration for the System Landscape Directory (SLD)

(Configuration) Adobe Document Services Configuration Guide Configuring the Web Service Web Service Configuration of the Web Service for Basic Authentication
More Information

Securing Access to the

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: ■ If you chose the option Register in existing central SLD, SAPinst automatically configures the connection of the system being installed to an existing central System Landscape Directory (SLD). ■ If you chose the option Configure a local SLD, SAPinst automatically sets up and configures a local System Landscape Directory (SLD) during the installation.
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 37]. 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: ■ SAPinst configures SLD security roles. ■ SAPinst configures server and persistence parameters. ■ SAPinst performs the initial data import. ■ 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

■ For more information about working with and configuring the SLD, see the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management System Landscape Directory More documentation is also available at http://www.sdn.sap.com/irj/sdn/nw-sld. ■ For more information about security and on the role concept in the SLD, see the SAP Library at:

2009-04-30

PUBLIC

155/168

6 6.14

Additional Information Heterogeneous SAP System Installation http://help.sap.com/nw70

SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Administrator’s Guide SAP NetWeaver Security Guide Security Aspects for System Management Security Guide for the SAP System Landscape Directory ■ For more information about the 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 156]

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

To view the log file, choose View Logs. If an error occurs during the Define Parameters or Execute phase, do either of the following: ■ Try to solve the problem ■ Abort the installation by choosing Cancel in the SAPinst menu. For more information, see Interrupted Installation with SAPinst [page 139].

156/168

PUBLIC

2009-04-30

6 6.16

Additional Information Deleting an SAP System

3.

4.

■ After resolving the problem, you can continue the installation by choosing Retry. Check the log and trace files of the GUI server and SAPinst GUI in the directory <user_home>/.sdtgui/ for errors. ■ If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current <user_home> directory. ■ If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as described in Starting SAPinst GUI Separately [page 142]. ■ If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote Access of SAPinst GUI on Windows Workstations and you experience display problems such as missing repaints or refreshes, contact your X Server vendor. The vendor can give you information about whether this X Server supports Java Swing-based GUIs and also tell you about further requirements and restrictions. See also SAP Note 1170809. Ignore error messages such as the following in the SDM logs:
Error: <SCA name>: Location of software component '<SCA name>' / <SCA vendor>' / '<SCA location>' / '<SCA counter> ' unknown./ Error: <SCA name>: system component version store not updated.

For more information, see SAP Note 828978.

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

With this SAPinst option you do not delete the database software.
NOTE

We recommend that you delete an SAP system with SAPinst. However, you can also delete an SAP system manually. For more information, see SAP Note 1229586.
Prerequisites

■ You are logged on as user root. ■ If the saposcol process on the host you are working on has been started from the SAP system you want to delete, stop it using the command saposcol -k. If there are other SAP systems on the host, log on as user <sapsid>adm of the other SAP system and start saposcol from there using the command saposcol -l.
Procedure

1.

Start SAPinst [page 87] and on the Welcome screen, choose:

2009-04-30

PUBLIC

157/168

6 6.16

Additional Information Deleting an SAP System

2.

<Your SAP product> Software Life-Cycle Options Uninstall Uninstall System / Standalone Engine / Optional Standalone Unit Follow the instructions in the SAPinst input dialogs.
NOTE

For more information about the input parameters, place the cursor on the relevant field and press F1 in SAPinst. SAPinst first asks you which SAP instances you want to delete. Make sure that you delete the SAP instances in the order as described below.
CAUTION

SAPinst only stops local instances automatically. Before you delete the database instance of a distributed system make sure that you stop all remaining instances. You must stop the instance with the message server only after having entered all SAPinst parameters for the deletion of the database instance. ■ If you want to delete a central system (all instances reside on the same host), you can do this in one SAPinst run. 1. Delete the SAP system. 2. Delete the Oracle database software with the Oracle Universal Installer (OUI) as described in Deleting the Oracle Database Software [page 159]. ■ 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 SAPinst deletes the database instance but you have to delete the Oracle database software manually as described in Deleting the Oracle Database Software [page 159]. ■ Java Central services instance (SCS) ■
Only valid for: HA (UNIX) |

ABAP central services instance (ASCS)
End of: HA (UNIX) |

3. 4.

■ The relevant directory structure on the global host If required, you can delete the directory /usr/sap/trans and its content manually. SAPinst does not delete /usr/sap/trans because it might be shared. If you created the directories /usr/sap/<SAPSID> and /<sapmnt>/<SAPSID> as mount points, but not as directories on the local file system, you have to remove them manually.

158/168

PUBLIC

2009-04-30

6 6.17

Additional Information Deleting the Oracle Database Software

6.17 Deleting the Oracle Database Software
You have to delete the Oracle database software to complete the deletion of the Oracle database instance. Here you find information how to delete the Oracle database software with the Oracle Universal Installer (OUI).
NOTE

This section only applies if you have deleted your SAP system using the Uninstall option of SAPinst. We recommend that you delete a database instance with SAPinst and then remove the database software manually. However, you can also delete the complete database instance manually. For more information, see SAP Note1229689.
Procedure

1.

Start the OUI with the user ora<dbsid> by entering one of the following: ■ ■
cd /oracle/stage/102_64/database/Disk1/SAP ./runInstaller cd /oracle/stage/102_64/database/SAP ./runInstaller

2. 3. 4. 5. 6. 7.

You see a message that a response file is being generated. It might take several minutes before you see the OUI screen. Choose Installed Products or Uninstall Products. Select the database schema you want to uninstall: <DBSID>_102_64. Mark the Oracle 10G database within the selected product. Choose Remove. Confirm your selection with Yes. Choose EXIT.

6.18 Deleting a Diagnostics Agent
This procedure tells you how to delete the Diagnostics Agent with SAPinst.
NOTE

We recommend that you delete a Diagnostics Agent with SAPinst. However, you can also delete a Diagnostics Agent manually. For more information, see SAP Note1229586.
Prerequisites

You are logged on as user root.
Procedure

1. 2.

Start SAPinst [page 87]. On the Welcome screen, choose:

2009-04-30

PUBLIC

159/168

6 6.18

Additional Information Deleting a Diagnostics Agent

3.

<Your SAP product> Software Life-Cycle Options Uninstall Uninstall – Solution Manager Diagnostics Agent Follow the instructions in the SAPinst input dialogs.
NOTE

4.

For more information about the input parameters, place the cursor on the relevant field and press F1 in SAPinst. After the uninstall with SAPinst has finished successfully, you still have to manually delete the <smdsid>adm user.

160/168

PUBLIC

2009-04-30

A A.1

Appendix Online Information from SAP

A Appendix

A.1 Online Information from SAP
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
http://service.sap.com/instguides

Available Documentation

Here you find all documentation about installation, update and SAP Components SAP Solution Manager upgrade : Release 7.0 EHP 1 ■ Media List ■ Master Guide ■ Installation guides for the installation of SAP Solution Manager 7.0 including SAP Enhancement Package 1 from scratch ■ Update guides for the installation of SAP Enhancement Package 1 on an existing SAP Solution Manager 7.0 system ■ Sizing Toolkit ■ Configuration Guide ■ 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 ■ Wily Introscope 8.0 Installation Guide ■ Diagnostics Agent Setup Guide ■ SAP Solution Manager 7.0 EhP1 Sizing Toolkit ■ Solution Concept and Design ■ User Administration Guide http://service.sap.com/installnw70 Here you find all documentation about installation, update, upgrade, and system copy for SAP NetWeaver: ■ Media List ■ Master Guide ■ Support Package Stack Guide ■ Installation guides for the installation of SAP NetWeaver 7.0 including SAP Enhancement Package 1 SR1 from scratch ■ Update guides for the installation of SAP Enhancement Package 1 on an existing SAP NetWeaver 7.0 system

2009-04-30

PUBLIC

161/168

A A.1

Appendix Online Information from SAP Available Documentation

Internet Address

http://service.sap.com/ solutionmanager

■ System copy guides for SAP systems based on SAP NetWeaver 7.0 including Enhancement Package 1 Support Release 1 Here you find all documentation about how to manager your entire SAP solution landscape with SAP Solution Manager.

General Quick Links Description Internet Address
http://help.sap.com http://help.sap.com/nw70

SAP Help Portal SAP NetWeaver Library in SAP Help Portal SAP Notes Forums, blogs, and general information related to all of the supported databases and operating system platforms Product Availability Matrix (PAM) for supported operating system releases Release notes Unicode SAP systems and their availability System sizing (Quick Sizer tool) SAP NetWeaver capabilities Life-cycle management for SAP NetWeaver Landscape design for SAP NetWeaver Application management for SAP NetWeaver High Availability System Landscape Directory Software logistics for SAP NetWeaver SAP NetWeaver operations SAP NetWeaver Development Infrastructure Security for SAP NetWeaver Information on SAP Support Package Stacks SAP Solution Manager Maintenance Optimizer End-to-End Root Cause Analysis

http://service.sap.com/notes http://sdn.sap.com/irj/sdn/dbos

http://service.sap.com/pam

http://service.sap.com/releasenotes http://service.sap.com/unicode

http://service.sap.com/sizing http://sdn.sap.com/irj/sdn/netweaver http://sdn.sap.com/irj/sdn/lcm

http://sdn.sap.com/irj/sdn/landscapedesign

http://sdn.sap.com/irj/sdn/applicationmanagement

http://sdn.sap.com/irj/sdn/ha http://sdn.sap.com/irj/sdn/nw-sld http://sdn.sap.com/irj/sdn/softwarelogistics

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

http://sdn.sap.com/irj/sdn/security http://service.sap.com/sp-stacks

http://service.sap.com/solutionmanager http://service.sap.com/solman-mopz http://service.sap.com/diagnostics

162/168

PUBLIC

2009-04-30

Typographic Conventions

Example
<Example>

Description

Example Example Example
Example

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

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

2009-04-30

PUBLIC

163/168

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.

164/168

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 Dietmar-Hopp-Allee 16 69190 Walldorf, Germany (hereinafter: SAP) and you (hereinafter: Customer) 1. Subject Matter of the Agreement 1. SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee. 2. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement. 3. The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. 4. Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG 5. The Customer may distribute original or modified STLport sources, provided that: ■ The conditions indicated in the above permissions notice are met; ■ The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met: Copyright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems Inc. Copyright 1997 Moscow Center for SPARC Technology. Copyright 1999,2000 Boris Fomitchev Copyright 2001 SAP AG Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty. Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice.

2009-04-30

PUBLIC

165/168

3.

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

Documentation in the SAP Service Marketplace

You can find this document at the following address: https://service.sap.com/instguides

166/168

PUBLIC

2009-04-30

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

© Copyright 2009 SAP AG. All rights reserved. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Sign up to vote on this title
UsefulNot useful