User Guide English

FlexFrame™ for SAP® 4.0

Installation Guide for SAP Solutions
 ®
FlexFrame™ for SAP
Version 4.0

Installation Guide for SAP Solutions

Edition March 2007

Document Version 1.0
Fujitsu Siemens Computers GmbH

© Copyright Fujitsu Siemens Computers GmbH 2007

FlexFrame™, PRIMECLUSTER™. PRIMEPOWER™ and PRIMERGY™ are trademarks of
Fujitsu Siemens Computers
®
SPARC64 is a registered trademark of Fujitsu Ltd.
®
SAP and NetWeaver™ are trademarks or registered trademarks of SAP AG in Germany and
in several other countries
®
Linux is a registered trademark of Linus Torvalds
®
SUSE Linux is a registered trademark of Novell, Inc., in the United States and other
countries
Java™ and Solaris™ are trademarks of Sun Microsystems, Inc. in the United States and
other countries
® ®
Intel and PXE are registered trademarks of Intel Corporation in the United States and other
countries
®
MaxDB is a registered trademark of MySQL AB, Sweden
®
MySQL is a registered trademark of MySQL AB, Sweden
® ®
NetApp , Network Appliance , Open Network Technology for Appliance Products™, Write
Anywhere File Layout™ and WAFL™ are trademarks or registered trademarks of Network
Appilance, Inc. in the United States and other countries
®
Oracle is a registered trademark of ORACLE Corporation
® ® ® ®
EMC , CLARiiON , Symmetrix , PowerPath , Celerra™ and SnapSure™ are trademarks or
registered trademarks of EMC Corporation in the United States and other countries
SPARC™ is a trademark of SPARC International, Inc. in the United States and other
countries
®
Ethernet is a registered trademark of XEROX, Inc., Digital Equipment Corporation and Intel
Corporation
® ® ®
Windows , Excel and Word are registered trademarks of Microsoft Corporation
All other hardware and software names used are trademarks of their respective companies.

All rights, including rights of translation, reproduction by printing, copying or similar methods,
in part or in whole, are reserved.
Offenders will be liable for damages.
All rights, including rights created by patent grant or registration of a utility model or design,
are reserved. Delivery subject to availability. Right of technical modification reserved.
Contents
1 Introduction ..................................................................................................... 1
1.1 Purpose of this Document ................................................................................. 1
1.2 General Usage of SAP Installation Guide During Installation............................ 1
1.3 Overview ........................................................................................................... 1
1.4 Notational Conventions ..................................................................................... 2
1.5 Document History.............................................................................................. 2
1.6 Related Documents........................................................................................... 2
1.7 IP Addresses Used in this Document ................................................................ 3
1.8 Hotlinks for FlexFrame ...................................................................................... 4

2 Overview .......................................................................................................... 7
2.1 FlexFrame ......................................................................................................... 7
2.2 Virtualization of SAP Services ........................................................................... 7
2.3 Preparations ...................................................................................................... 8
2.4 Gathering SAP Services Information................................................................. 8
2.5 FlexFrame Installation Diagram Step by Step ................................................... 9
2.6 Application Nodes Released ........................................................................... 12
2.6.1 Linux................................................................................................................ 12
2.6.2 Solaris ............................................................................................................. 12

3 SAP Service Connection .............................................................................. 13

3.1 OSS Network Connection with Dedicated saprouter Server ........................... 13
3.2 OSS Network Connection without Dedicated saprouter Server....................... 14
3.3 Related SAP Notes ......................................................................................... 15

4 FA Agents ...................................................................................................... 17

5 SAP Service Scripts for Virtualizing Applications...................................... 19

5.1 Starting a Configuration................................................................................... 20
5.2 Configuring the Service Status Path................................................................ 22
5.3 Configuring the Interfaces ............................................................................... 23
5.4 Host Names..................................................................................................... 25

6 Pre-SAP Installation Steps ........................................................................... 27

6.1 General ........................................................................................................... 27
6.2 SAN Configuration........................................................................................... 29

7 Operating System in General ....................................................................... 31

7.1 Solaris 8/9 ....................................................................................................... 31
7.1.1 Integrating New Java SDK (JDK) in Solaris .................................................... 31
7.2 Linux................................................................................................................ 34
7.2.1 Integrating a new Java SDK (JDK) in Linux SLES8 / SLES9 32bit.................. 35

Installation Guide for SAP Solutions

Contents

7.2.2 Integrating New Java SDK (JDK) in SLES9_x86............................................. 36

8 Database in General ...................................................................................... 37

8.1 Installation of Oracle in General ...................................................................... 37
8.1.1 TNS Listener for Oracle ................................................................................... 37
8.1.2 “[Link]” .................................................................................................... 38
8.1.3 Host Name Changes in "[Link]" .......................................................... 39
8.2 Installation of Oracle 9.2 .................................................................................. 40
8.2.1 Post-Oracle 9.2 Installation Steps ................................................................... 41
8.2.2 Patch Installation ............................................................................................. 41
8.3 Installation of Oracle 10.1 (R1) ........................................................................ 41
8.3.1 Script [Link] ................................................................................................... 42
8.3.2 Patch Installation ............................................................................................. 43
8.4 Installation of Oracle 10.2 (R2) ........................................................................ 43
8.5 Installation of SAPDB / MaxDB........................................................................ 43
8.5.1 XUSER ............................................................................................................ 44
[Link] Same SID on Different Platforms..................................................................... 44
8.5.2 MaxDB 7.5/7.6 /etc/opt/sdb ............................................................................. 45
8.5.3 MaxDB 7.6....................................................................................................... 46
8.5.4 IO Balancing .................................................................................................... 47
8.5.5 Directories for sapdata / saplog ....................................................................... 47

9 SAP in General............................................................................................... 49
9.1 ASCS ABAP Central Service Instance in General........................................... 49
9.2 SAP Java Cryptographic Toolkit ...................................................................... 49
9.2.1 Linux................................................................................................................ 49
9.2.2 Solaris ............................................................................................................. 50

10 Installing SAP 4.6C SR2 ................................................................................ 51

10.1 SAPDB / MaxDB / Oracle ................................................................................ 52

11 Installing Web AS 6.20 .................................................................................. 57

11.1 Installating Web AS 6.20 with sapinst 642....................................................... 57
11.1.1 Installing the Central Instance (CI) .................................................................. 58
11.1.2 Installing the Database Instance (DB) ............................................................. 60

12 Installing Web AS 6.40 with NetWeaver04 SR1........................................... 65

12.1 Description of Web AS 6.40 JAVA................................................................... 66
12.2 Web AS 6.40 NetWeaver04SR1 JAVA MaxDB/Oracle ................................... 67
12.2.1 SCS ................................................................................................................. 67
12.2.2 DB ................................................................................................................... 71
12.2.3 JC .................................................................................................................... 72
12.2.4 J ...................................................................................................................... 72
12.2.5 Web AS 6.40 Deployment SP16...................................................................... 73

Installation Guide for SAP Solutions

 Contents

[Link] JC.................................................................................................................... 73
[Link] J ..................................................................................................................... 73
12.3 Web AS 6.40 NetWeaver04SR1 ABAP Oracle ............................................... 73
12.3.1 CI..................................................................................................................... 73
12.3.2 DB ................................................................................................................... 77
12.3.3 APP ................................................................................................................. 78
12.4 Web AS 6.40 ABAP + JAVA-AddIn NetWeaver04SR1 ................................... 78
12.4.1 CI..................................................................................................................... 78
12.4.2 DB ................................................................................................................... 78
12.4.3 SCS................................................................................................................. 79
12.4.4 Web AS 6.40 Deployment SP16 ..................................................................... 83
[Link] DVEBMGS<id> (JAVA-AddIN) ........................................................................ 83
12.5 Web AS 6.40 Application Server JAVA-AddIn................................................. 83

13 Installing NetWeaver 7.0SR1/SR2 ................................................................ 85

13.1 Installation of SAP Solutions ........................................................................... 86
13.1.1 Prerequisite Checker (Linux) ........................................................................... 89
13.2 Sapinit File (Linux)........................................................................................... 90
13.3 [Link] – symlink (Linux) .................................................................... 91
13.4 Services File (Linux)........................................................................................ 92
13.5 NetWeaver 7.0SR1/SR2 and Oracle 10(R2) ................................................... 93
13.6 NetWeaver 7.0SR1/SR2 and MaxDB76.......................................................... 94
13.7 NetWeaver 7.0SR1/SR2 / MaxDB76 and SLES9_x86 .................................... 96
13.8 NetWeaver 7.0SR1/SR2 MaxDB76 and Solaris9 ............................................ 98
13.9 NetWeaver 7.0SR1/SR2 and EP..................................................................... 98
13.10 NetWeaver 7.0SR1/SR2 ABAP+JAVA-AddIn ............................................... 100
13.11 NetWeaver 7.0SR1/SR2 JAVA only .............................................................. 105
13.12 LiveCache ..................................................................................................... 106
13.13 ERS – Enque Replicated Server ................................................................... 106
13.14 Installation of SAP Solutions – Post Phase ................................................... 106
13.14.1 Linux.............................................................................................................. 106
13.14.2 Solaris ........................................................................................................... 107
13.14.3 Linux and Solaris........................................................................................... 107
13.14.4 Solaris 10 Preparations ................................................................................. 108

14 Post-SAP Installation Steps ....................................................................... 109

14.1 Configuring the Virtual Host Name Manually................................................. 109
14.1.1 Central Instance (not valid for Web AS 6.40 J2EE)....................................... 111
14.1.2 Database Instance (also valid for WebAS 6.40 J2EE) .................................. 111
14.1.3 Application Instance (not valid for WebAS 6.40 J2EE).................................. 112
14.1.4 SCS Instance ................................................................................................ 113
14.1.5 ASCS Instance (WebAS 7.00)....................................................................... 115
14.1.6 NetWeaver 7.0 / NetWeaver 7.0SR1/SR2..................................................... 116
14.2 Configuring the Virtual Host Name for Web AS 6.40 ABAP and
JAVA-AddIn / WebAS 6.40 JAVA.................................................................. 117

Installation Guide for SAP Solutions

Contents

14.3 Start Script startdb for Oracle and SAPDB/MaxDB ....................................... 134
14.4 Stop Script stopdb for Oracle and SAPDB/MaxDB........................................ 134
14.5 Scheduling of Batch Jobs (CCMS) ................................................................ 134
14.6 Profile Parameters for [Link]........................................................... 135
14.7 Profile Parameters for the Start Profile .......................................................... 136
14.8 Profile Parameters for the Instance Profile .................................................... 136
14.9 SAP Start and Stop Mechanism (Release 4.6CSR2) .................................... 137
14.10 SAP License .................................................................................................. 139
14.11 SAPLogon – SAPGUI.................................................................................... 139
14.12 SAPROUTER on the Control Node ............................................................... 142

15 SAP System Administration ....................................................................... 143

15.1 Upgrading Application Software .................................................................... 143
15.2 Software Administration................................................................................. 143
15.2.1 Starting and Stopping SAP Services ............................................................. 143
[Link] SAP Service Scripts ...................................................................................... 143
[Link] SAP Service Script Actions............................................................................ 145
[Link] Return Codes of the SAP Service Scripts ..................................................... 146
[Link] Joined SAP Service Scripts ........................................................................... 146
15.2.2 Removing an Application from Monitoring by FA Agents............................... 147
15.2.3 Application Software...................................................................................... 147
15.3 SAP Release Upgrade .................................................................................. 148
15.3.1 Services Port ................................................................................................. 148
15.3.2 Group Sapinst................................................................................................ 148
15.3.3 FA-Agent ....................................................................................................... 149
15.4 Transport Directory........................................................................................ 149
15.5 Printing in FlexFrame 3.2 .............................................................................. 149
15.5.1 Possible Printing Architectures and Methods ................................................ 149
15.5.2 Local Printing (Access Methods C and L)...................................................... 150
15.5.3 Remote Printing (Access Methods S and U) ................................................. 150
[Link] Architecture Prerequisites.............................................................................. 150
[Link] SAP System Prerequisites............................................................................. 151
[Link] Description..................................................................................................... 151
15.5.4 Front-end Printing on Local Printers .............................................................. 152

16 BRBACKUP and SAPDBA/BRCONNECT................................................... 153

16.1 Solution 1 for Oracle and SAPDB/MaxDB ..................................................... 153
16.2 Solution 2 for Oracle...................................................................................... 154

17 Troubleshooting .......................................................................................... 155

18 Abbreviations............................................................................................... 157

19 Glossary ....................................................................................................... 161

Installation Guide for SAP Solutions

 Contents

20 Index............................................................................................................. 167

Installation Guide for SAP Solutions

1 Introduction
As we continue to improve the installation process, this document is permanently subject
to change.
The latest version can be found at
[Link]

Please make sure that you get the latest version before starting an installation,
and always read the latest README file that contains further changes and fixes.

1.1 Purpose of this Document

This document provides brief instructions for installing SAP® with Oracle® or
SAPDB / MaxDB™ in a FlexFrame™ 3.2 environment. It is absolutely essential to use the
SAP Installation Guides and the latest SAP Notes for the SAP solution that is to be
installed.
It is intended for certified FlexFrame consultants only; sound knowledge of FlexFrame
technology and its background is required.

1.2 General Usage of SAP Installation Guide

During Installation
Please note that the entire documentation on installing SAP on FlexFrame is not intended
as a stand-alone documentation. It solely describes the differences to a standard SAP
installation as described by SAP.

1.3 Overview
The SAP installation is performed in 5 steps:
®
1. Information about the SAP Services is collected in an Excel spreadsheet; a
configuration file is generated and stored on the LDAP server (Section 2.4).
2. SAP Service scripts for virtualizing the applications (Chapter 5).
3. Oracle 9.2/10.x and SAPDB (7.3 / 7.4) /MaxDB (7.5 / 7.6) installation, LDAP
configuration (Chapter 6).
4. Installation of SAP software depending on the release (Chapters 9, 10, 11 ,12, and
13).
5. Post-SAP installation steps have to perform (Chapter 14).

Installation Guide for SAP Solutions 1

Introduction

1.4 Notational Conventions

The following conventions are used in this manual:

Additional information that should be observed.

Warning that must be observed.

fixed font Names of paths, files, commands, and system output.

<fixed font> Names of variables
fixed font User input in command examples
(if applicable using <> with variables)

1.5 Document History

Document Version Changes Date
1.0 First Edition 2006-05-25

1.6 Related Documents

FlexFrame™ for SAP® – Planning Tool
FlexFrame™ for SAP® – Installation of a FlexFrame Environment
FlexFrame™ for SAP® – Administration and Operation
FlexFrame™ for SAP® – Network Design and Configuration Guide
FlexFrame™ for SAP® – FA Agents - Installation and Administration
FlexFrame™ for SAP® – Installation ACC 1.0 SP13
FlexFrame™ for SAP® – myAMC.FA_LogAgent - Concept and Usage
FlexFrame™ for SAP® – Upgrading FlexFrame 3.1 or 3.2 to 4.0
FlexFrame™ for SAP® – White Paper
PRIMECLUSTER Documentation
ServerView Documentation
SUSE Linux Enterprise Server Documentation
Solaris Documentation

2 Installation Guide for SAP Solutions

 Introduction

1.7 IP Addresses Used in this Document

All Application Nodes must belong to a dedicated FlexFrame pool; nevertheless it is
possible to have only one pool in a FlexFrame 3.2 environment. It is not permissible to
use a node in more than one pool at the same time. For this reason Application Nodes
belonging to the same pool use the same IP subnet.
All blades in the same cabinet can be members of different pools.
®
Control Nodes and the NetApp Filer have IP addresses for all pools.
The Control LAN is independent of the pool number and has its own IP subnet
addresses.

Pool Client IP Server IP Storage IP Control IP (RSB) Heartbeat (PCL)

No.
1 [Link] [Link] [Link] [Link] control1 [Link]
2 [Link] [Link] [Link] [Link] control1
1 [Link] [Link] [Link] [Link] control2 [Link]
2 [Link] [Link] [Link] [Link] control2
1 [Link] [Link] filer
2 [Link] [Link] filer
BX300-1
1 [Link] bx3001mg
mt
1 [Link] [Link] [Link] blade1
1 [Link] [Link] [Link] blade2
1 [Link] [Link] [Link] blade3
BX300-2
2 [Link] bx3002mg
mt
2 [Link] [Link] [Link] blade11
2 [Link] [Link] [Link] blade12
2 [Link] [Link] [Link] blade13
1 [Link] [Link] [Link] [Link] PW250_1
2 [Link] [Link] [Link] [Link] PW250_2
[Link] switch1
[Link] switch2
SAP
instance
1 [Link] [Link] cic11

Installation Guide for SAP Solutions 3

Introduction

Pool Client IP Server IP Storage IP Control IP (RSB) Heartbeat (PCL)

No.
1 [Link] dbc11
1 [Link] [Link] app01c11
1 [Link] [Link] app02c11
1 [Link] [Link] app03c11
2 [Link] [Link] cibw1
2 [Link] dbbw1
2 [Link] [Link] app01bw1
2 [Link] [Link] app02bw1

1.8 Hotlinks for FlexFrame

PRIMECLUSTER™4

PRIMECLUSTER Wizards (downloads & documents)

[Link]
Primecluster RMS Home (information on the Reliant Monitor Services)
[Link]
PRIMECLUSTER
[Link]

SAP on Linux® / FlexFrame

SAP on Linux (released kernels, hardware and distributions for SAP)
[Link]
SAP NetWeaver™ on Linux
[Link]
Official FlexFrame home page
[Link]
Information on FlexFrame for SAP
[Link]
PRIMERGY™ manuals
[Link]

4 Installation Guide for SAP Solutions

 Introduction

SAP on Solaris™ / FlexFrame

Global information and operating system manuals
Fujitsu Siemens Computers and SAP
[Link]
PRIMEPOWER™ manuals

[Link]

Knowledge
SNMP protocol information
[Link]
Linux Knowledge Portal
[Link]
Official Linux documentation project
[Link]
Official PRIMERGY documentation
[Link]
Internal information on PRIMERGY servers
[Link]

Software
GNU Homepage
[Link]
Software by Fujitsu Siemens Computers
[Link]
Open SSH website SSH download
[Link] [Link]

Installation Guide for SAP Solutions 5

2 Overview

2.1 FlexFrame
FlexFrame is a completely revolutionary solution for creating and configuring the
infrastructure required to run a SAP environment.
An essential feature of FlexFrame is that the infrastructure is divided into the following
elements:
● Computing, represented by the Application Nodes
● Network, completely implemented on the basis of IP networks
● Control and management, represented by the Control Nodes
● Storage, represented by the NetApp Filer
A number of fundamental features of FlexFrame are implemented on the basis of this
division into the areas of computing, network, control and storage:
● Virtualized SAP Services
● Central, shared operating system
● Embedded high availability
● Network attached storage (NAS)
For further details, please refer to the Technical White Paper for FlexFrame 4.0.

2.2 Virtualization of SAP Services

To enable high availability and scalability of SAP Services (database, SAP R/3, etc.), the
fixed assignment of SAP Services to Application Nodes has been abolished. Here, each
SAP Service can run not only on one host in the high-availability cluster, as has been the
case with customary high availability solutions to date, but on virtually any required
Application Node in FlexFrame, provided it has resources available for this.
Technically speaking, virtualization is achieved by the fact that an SAP Service is able to
move, taking its IP address with it and retaining its virtual host name.
Virtualization is achieved here by SAP Service scripts that ensure the virtual host names
and virtual IP addresses are set accordingly when SAP Services are started and stopped.

Installation Guide for SAP Solutions 7

Overview

2.3 Preparations
Make sure you have the following hardware and software available:
● Your FlexFrame hardware
● A notebook with Microsoft Excel 2003
● FlexFrame 3.2 Planning CD-ROM
● OS installation of Control Nodes and the necessary Application Nodes
(Linux/Solaris) must have been completed
● Installation DVDs/CDs from SAP for the required SAP Releases

2.4 Gathering SAP Services Information

The FlexFrame Planning Tool is a program based on Microsoft Excel 2003. It was used
during the setup of the hardware to collect all information for a FlexFrame landscape
(original file name [Link]). You may use the Excel sheet that has already been
completed or a copy of it. If all SAP Services were entered beforehand, you may skip the
rest of this section.
After you have opened the Excel sheet, go to the SAP Services tab at the bottom of the
document (scroll to the right in the tab list). If there are no SAP instances listed, click the
Add SID button and insert the SAP Services that have to be installed.
You will be asked for the following details:
● SID
● Select pool (dropdown list)
● Select DB type (dropdown list)
● Select SAP version (dropdown list)
● Select one of the following (only Web AS 6.40)
– CI (ABAP only)
– CI + SCS (ABAP/JAVA-AddIn)
– JC + SCS (JAVA only)

8 Installation Guide for SAP Solutions

 Overview

● Select one of the following (only Web AS 7.00)

– CI (ABAP only)
– CI + ASCS (ABAP/ASCS)
– CI + ASCS + SCS (ABAP/ASCS/JAVA-AddIn)
– CI + SCS (ABAP/JAVA-AddIn)
– JC + SCS (JAVA only)
– CI + ASCS + ERS (ABAP/ASCS/Enqueue Replicated Server)
– CI + ASCS + SCS + ERS
(ABAP/ASCS/JAVA-AddIn/Enqueue Replicated Server)
– JC +ERS (Enqueue Replicated Server only)
● Number of application instances (in addition to the CI/JC)
● LiveCache (WebAS 7.0/MaxDB only)

If you want to install a SAP component like CRM or R/3 (ERP), you won’t find it
in the dropdown list of the SAP versions. You have to enter the underlying SAP
Basis (Web AS) release which must be one of the four listed versions. If you
need another Basis release or another DB type for your SAP component, please
ask our SAP Competence Center for project-specific support.
Please make sure to have the latest version before starting an installation, and
always read the latest README file that contains further changes and fixes.

After all information for the complete SAP Services landscape has been entered in the
tool, the configuration files ff_*.conf can be created by pressing the button labeled
Generate configuration files. A dialog box will ask you for a directory where the
configuration files are stored. We recommend that you create a new directory for each
project and version of the files, including the [Link] spreadsheet.
The configuration file ff_services.conf now has all the information required to be
stored on the LDAP server. This step must currently be performed manually until a tool is
available to store this information in LDAP. For more information about LDAP please refer
to the LDAP Installation Guide.

2.5 FlexFrame Installation Diagram Step by Step

The following chart shows the installation steps of a complete FlexFrame installation. As
the final step of the platform basis, SAP installation is shown at the bottom of the second
chart (red frame).
The numbers in the grey bar on the left side of the chart refer to the sections of
the chapter “Quick Installation” in the manual “FlexFrame™ for SAP® -
Installation of a FlexFrame Environment”.

Installation Guide for SAP Solutions 9

Overview

The steps are

numbered according
to the sections in the
FF Prep
Excel Installation Steps FlexFrame 4.0
quick installation chapter FlexFrame
Planning Tool
Preparations CD
Configuration Files:
2.2 ff_cn.conf Cabling
ff_an.conf Plan
ff_misc.conf
ff_wiring.pl
ff_services.conf ff_switch_conf.pl

HW
Installation Hardware
Network
2.3 Installation
Cabling

OS
Installation
External DVD Service
Control
Node Medium:
Configuration CN Boot from CN
2.4 files; Patches DVD ff_setup_cn.sh
Control Node 1
ff_apply_settings_cn.sh

Switch
Confi-
Serial cable
guration ff_wiring.pl Switches
Control Node 1
2.5 DVD Boot from DVD
OS Installation 2nd Control Node 2
2.6 Control Node, see 2.4 CN

NAS Confi-
guration Serial cable
Control Node Manual
NAS
2.7 Setup
system

MAC
Addresses
Enter ff_get_an_mac.pl ff_an_mac.conf
2.8 MAC adresses

LDAP
and SSH
Confi- ff_cn.conf; Generates Scripts:
ff_an.conf; ff_ldap_conf.pl
guration ff_slapd_init.sh
ff_services.conf;
2.9.1 ff_an_mac.conf ff_filer_qtree_create.sh

2.6.3
Filer QTrees;
LDAP ff_cn.conf;
ff_filer_qtree_create.sh
Initialisation ff_an.conf;
ff_services.conf; ff_slapd_init.sh NAS
2.9.2 ff_an_mac.conf system

PRIME-
CLUSTER
Configuration Commands:
cftool -n
sdtool -s Control Node
2.9.4 hvdisp -a

10 Installation Guide for SAP Solutions

 Overview

Application Node Configuration

2.10

Preparation
for Linux
Application
Nodes DVD AN ff_install_an_linux_images.sh

2.10.2 Linux NAS

system

Preparation
for Solaris
Application DVD AN
Nodes
Solaris nb_unpack_bi
NAS
2.10.3 system

[Link]
Generation of
netboot
ff_cn.conf ff_create_an_cfg.pl NAS
config files
ff_an.conf system
ff_an_mac.conf
2.10.4 /tftpboot/config/netboot_
<Poolname>_<Nodename>.cfg

Setup Linux LDAP Configuration Files ff_new_an.sh

Customized
Application Boot Image
Nodes in /FlexFrame/volFF/FlexFrame/ldap/etc/
pools/<Pool Name>/ ;
/opt/FlexFrame/bin/ff_linux_ldap_client.sh
2.10.5 /tftpboot/config/netboot_<Poolname>_<Nodename>.cfg

NAS
system

/FlexFrame/volFF/ ff_new_an.sh Customized

FlexFrame/ldap/ Boot Image
Setup Solaris etc/pools/<Pool Name>/
Application solaris_ldap_client.sh
Nodes

2.10.6
NAS
system

2.12
Proceed with SAP Installation

Installation Guide for SAP Solutions 11

Overview

2.6 Application Nodes Released

2.6.1 Linux
All current SAP-certified, Intel®//AMD®-based servers from Fujitsu-Siemens Computers
have been released.
Please refer to: [Link]

2.6.2 Solaris
The PRIMEPOWER servers PW250/PW450 PW650/PW850 from Fujitsu-Siemens
Computers have been released.
Please note: Relevant source for supported components including Application Nodes is
the FlexFrame Support Matrix available at:
[Link]

12 Installation Guide for SAP Solutions

3 SAP Service Connection
It is very important that the customer’s FlexFrame environment can be accessed via
SAP’s OSS (Online Software Service). This is a mandatory requirement when customer
support is requested, particularly during the installation phase.

Please use the following OSS component for your customer calls to SAP about
FlexFrame: CA-ADA-FSC

3.1 OSS Network Connection with Dedicated

saprouter Server
The figure below shows an example of a possible network path from SAP to the
FlexFrame environment. This figure includes a (possibly existing) server SAPROUTER,
which runs the saprouter process:

Customer
SAP
Walldorf TELNET TELNET
Gateway SAPROUTER
SAPGUI SAPGUI
Tokio
Foster City

TELNET
Control Node 1 SAPGUI Application Node 1
SSH
SSH
TELNET
Control Node 2 SAPGUI Application Node 2
SSH
SSH

SAPGUI Application Node ...

SSH

SAPGUI Application Node n

SSH

Please enter the server SAPROUTER as External Connectivity in the FF

Planning tool to get a reservation of an IP address for the first pool.

Installation Guide for SAP Solutions 13

SAP Service Connection

3.2 OSS Network Connection without Dedicated

saprouter Server
The saprouter process can be configured on the Control Node cluster if there is no
dedicated server for it (see section “SAPROUTER on the Control Node” on page 142).
In this case, a virtual IP address for the Client LAN has to be defined for the saprouter
service and for every pool, and PRIMECLUSTER is configured accordingly (only for the
first pool today).
The virtual IP addresses will be generated with the FlexFrame Planning Tool: go to the
External Connectivity tab, select Add New, enter the pool name and Other as
selected type. Afterwards enter Saprouter as comment and a valid host number. The
host name for the first pool is predefined as saprouterINT and has to be used (check
entry in /usr/opt/reliant/etc/hvipalias).
To allow PRIMECLUSTER to control of the saprouter service, it is necessary to get the
latest version of saprouter from SAP (Service Marketplace) and to install it in the
directory /FlexFrame/volFF/FlexFrame/saprouter on the active Control Node.
This directory must have been created, the saprouter program must be copied to it and
the saprouttab file created in the same directory. The PRIMECLUSTER control of the
service is already predefined and has to be activated!
To add the saprouter application to RMS, call:
cn1:~ # pcstool -s -i /etc/PRIMECLUSTER/scripts/addSaprouter FlexFrame

To remove the saprouter application from RMS, call:

cn1:~ # pcstool -s -i /etc/PRIMECLUSTER/scripts/delSaprouter FlexFrame

To activate the modified configuration, first shut down RMS on both nodes:
cn1:~ # hvshut -L
cn2:~ # hvshut -L

The capital letter -L keeps all services running.

Then activate the modified configuration and distribute it to all Cluster Nodes:
cn1:~ # pcstool -a FlexFrame

Finally, start RMS on both Control Nodes:

cn1:~ # hvcm
cn2:~ # hvcm

Don’t forget to check the correct permissions in the saprouttab file if there are
multiple pools!

14 Installation Guide for SAP Solutions

 SAP Service Connection

Customer
SAP
Walldorf TELNET
Gateway
SAPGUI
Tokio
Foster City TELNET
SAPGUI

Control Node 1 Application Node 1

(saprouter) SAPGUI
SSH
Control Node 2 Application Node 2
(saprouter) SAPGUI
SSH

SAPGUI Application Node ...

SSH

SAPGUI Application Node n

SSH

3.3 Related SAP Notes

A table of related SAP Notes is provided below:

SAP OSS note number Title

35010 Service connections: Composite note (overview)
37001 Telnet link to customer systems

Installation Guide for SAP Solutions 15

4 FA Agents
A FlexFrame Autonomous Agent (FA Agent) is an efficient component for highly
autonomous operation of systems with distributed instances. A FlexFrame solution
consists of Network Attached Storage, Application Nodes, and redundant Control Nodes.
The FA Agents product has been developed for this solution, consisting of storage,
servers, and connectivity.
It permits fast and flexible installation of solutions, which simplify the operation of the
applications and make them flexible. New nodes and application instances can be
integrated without any changes to the configuration.
Components of a FlexFrame Autonomous Agent:
● FlexFrame Autonomous Application Agent (FA_AppAgent)
● FlexFrame Autonomous CtrlAgent (FA_CtrlAgent)
The FlexFrame Autonomous Agent components also permit the highly available, partly
autonomous operation of distributed applications. The application instances can be
distributed over any required number of nodes within a FlexFrame solution. Monitoring of
several services is implemented via the FlexFrame Autonomous Agent.
The FA Application Agent components normally support SAP application instances (pure
application instances and central instances), as well as SAPDB/MaxDB and Oracle
databases.
For more information, please refer to the “FA Agents - Installation and Administration”
manual.
Please make sure that the FA Application Agents are stopped on the hosts while
you are installing SAP software:
/etc/init.d/myAMC.FA_AppAgent stop (Linux/Solaris9)
svcadm disable -s smawfa-agents (Solars10)
Check the status with:
/etc/init.d/myAMC.FA_AppAgent status (Linux/Solaris9)
svcs smawfa-agents (Solars10)

Installation Guide for SAP Solutions 17

5 SAP Service Scripts for Virtualizing
Applications
Scripts for starting, stopping and restarting the applications and services are provided by
SAP.
Make sure that the scripts are located at /FlexFrame/scripts.

The following scripts are installed:

Script name Application

sapapp Application server (ABAP)
sapascs ABAP central services instance
sapci Central instance (ABAP)
sapdb Database instance (SAPDB, MaxDB, Oracle)
sapers Enqueue Replicated Server
sapj J2EE Application server
sapjc J2EE Central Instance
saplc LiveCache
sapscs Java central services instance
sapservice_config Global customer-specific parameters
sapservice_functions Global parameters and functions
start_all_sapservices Initial start of all configured applications
stop_all_sapservices Stops all running applications
stop_all_sapservices_local Stops all running applications on the local node
stop_all_sapservices_SID Stops all running applications of one SID

Installation Guide for SAP Solutions 19

SAP Service Scripts for Virtualizing Applications

5.1 Starting a Configuration

The start_all_sapservices start script defines which applications are to be started
in what sequence and on which virtual host. The script is executed on a Control Node.
The script below illustrates its syntax:

#!/bin/bash
#-----------------------------------------------------------------

# Rule is:
# All sapservices in one 'eval' must start one after another,
# each 'eval' may start simultaneous.

# C11
eval "
ssh blade1 sapdb C11 start
ssh blade1 sapci C11 start
ssh blade2 sapapp 01 C11 start
ssh blade3 sapapp 02 C11 start
" &

# BW1
eval "
ssh PW250-1 sapdb BW1 start
ssh PW250-1 sapci BW1 start
" &

#echo ""
#echo "All services should be up now."
#-----------------------------------------------------------------

The start sequence within a system ID must always be observed:

ABAP + ABAP + ABAP + ASCS +

ABAP JAVA
ASCS JAVA-AddIn JAVA-AddIn
1. DB 1. DB 1. DB 1. DB 1. DB
2. CI 1. ASCS 1. SCS 1. SCS 1. ASCS
3. APP 2. CI 2. CI 2. JC 1. SCS
3. APP 2. APP 2. J 2. CI
3. APP
Equal numbers mean that the features can be started in parallel.

20 Installation Guide for SAP Solutions

 SAP Service Scripts for Virtualizing Applications

The figure below shows the dependencies of the SAP Services (x Æ y means “x is
dependent on y”).

The field containing JC and SCS is the minimal group of services for J2EE only. The field
with CI and SCS is the minimum for ABAP and J2EE. Only ABAP is not mentioned here
but it would be CI only. However it is possible to have a combination of CI and ASCS
(ABAP central services instance). And still every service group needs its DB server.

Installation Guide for SAP Solutions 21

SAP Service Scripts for Virtualizing Applications

5.2 Configuring the Service Status Path

The SERVICE_STATUS_PATH parameter describes the global location for the service
control files of the applications (services). If such a file exists, the application or service
has been started and therefore should be running. The naming convention is defined as
follows:
For the service types db and ci: <service_type>_<sid>_host
For the service type app: app_<id>_<sid>_host
Explanation: id Consecutive two-digit number from 00-97
sid The lower-case three-digit system ID

Web AS 6.40 with JAVA/J2EE Engine and/or ABAP Engine

There are additional service types when you run a J2EE engine based on WebAS 6.40.
For the service types scs and jc: <service_type>_<sid>_host
For the service type j: j_<id>_<sid>_host
Explanation: id Consecutive two-digit number from 00-97
sid The lower-case three-digit system ID
The content of the service control file is the name of the node the application or service is
running on.

Web AS 7.00 with JAVA/J2EE Engine and/or ABAP/ASCS Engine

There are additional service types when you run a J2EE engine based on WebAS 7.00.
For the service types scs, ascs and jc: <service_type>_<sid>_host
For the service type j: j_<id>_<sid>_host
Explanation: id Consecutive two-digit number from 00-97
sid The lower-case three-digit system ID

WebAS 7.0 with JAVA/J2EE Engine and/or ABAP/ASCS Engine and ERS
There are optional service types bound on WebAS 7.00.
For the service types scs and ascs: sapers_<id>_<sid>_host
Explanation: id Consecutive two-digit number from 00-97
sid The lower-case three-digit system ID

22 Installation Guide for SAP Solutions

 SAP Service Scripts for Virtualizing Applications

WebAS 7.0 with ABAP and MaxDB (LiveCache)

There is a additional service type which supports LiveCache.
Service type: lc_<sid>_host
Explanation: sid The lower-case three-digit system ID

5.3 Configuring the Interfaces

Depending on which interfaces the nodes have, the LAN type must be assigned to the
interfaces.
The following section from the sapservice_config include script shows the
connection between the LAN type, interface and netmask:

#-----------------------------------------------------------------
# Netmask
#
#NETMASK_CLIENT=”[Link] ls3195:[Link]”
NETMASK_CLIENT=”[Link]”
NETMASK_SERVER=”[Link]”
#
# Interface
#
#-----------------------------------------------------------------
# SunOS link aggregation
# ~~~~~~~~~~~~~~~~~~~~~~~
#
# real interfaces look like this:
# fjgi2005000 # this is the first interface
# fjgi2005001 # this is the second interface
# fjgi2005000:1 # this indicates that the first interface
# # is active
# fjgi2005001:1 # this indicates that the second interface
# # is active
#
# These interface names consist of three parts:
# fjgi2005001:1
# ^^^----------- interface number
# ^^^^-------------- vlan
# ^^^^------------------ 1GB-model
#
# For our network to interface relation we use only the first two
# parts of the interface names, the model and the vlan. In our
# example:

Installation Guide for SAP Solutions 23

SAP Service Scripts for Virtualizing Applications

# fjgi2005
#
#-----------------------------------------------------------------
#
# Recommendations:
#
# for a clean linux environment without network redundancy,
# FlexFrame <= 3.0.x
# ETH_CLIENT= »eth0 ls3191 :eth1 ls3192 :eth1 ls3195 :eth1 »
# ETH_SERVER=“eth1 ls3191:eth0 ls3192:eth0 ls3195:eth0“
#
# for a clean linux environment with network redundancy,
# FlexFrame >= 3.1
# ETH_CLIENT=”vlan2001”
# ETH_SERVER=”vlan2005”
#
# for a clean solaris environment with network redundancy,
# FlexFrame >= 3.1
# ETH_CLIENT=”fjgi2001”
# ETH_SERVER=”fjgi2005”
#
# for a mixed environment without network redundancy,
# customer specific
# ETH_CLIENT=”eth0 belana:hme0 belana2:hme0”
# ETH_SERVER=”eth1 belana:hme1 belana2:hme1”
#
# for a mixed environment with network redundancy,
# FlexFrame >= 3.1
# ETH_CLIENT=”vlan2001 Baby_1:fjgi2001 Baby_2:fjgi2001
# klinge1:vlan2002”
# ETH_SERVER=”vlan2005 Baby_1:fjgi2005 Baby_2:fjgi2005
# klinge1:vlan2006”
#
# In a FlexFrame >= 3.1 environment with more than one pool,
# we can have more than one configuration file, linked into an
# pool-image. This avoid to define to much specials.

The LAN types Server and Client are used.

The syntax will be illustrated with reference to the example of Client and Server LAN.
For example, the ETH_SERVER parameter describes a list of assignments between the
node and the interface. The first element in the list is the standard interface for the LAN
type server LAN; all of the subsequent elements are optional and describe a deviation
from this type.

24 Installation Guide for SAP Solutions

 SAP Service Scripts for Virtualizing Applications

5.4 Host Names

The following (virtual) host names for the SAP Services must be used and will be
generated by the Excel planning tool:

Server LAN Client LAN

db<sid>-se
ci<sid>-se ci<sid>
ascs<sid>-se ascs<sid>
app<id><sid>-se app<id><sid>
scs<sid>-se scs<sid>
jc<sid>-se jc<sid>
j<id><sid>-se j<id><sid>

Explanation: id Consecutive two-digit number 00-97

sid The lower-case three-digit system ID

In FlexFrame 4.0, the following rules have to be regarded to define host names:
1. The host name in the Storage LAN is built using the host name and adding -st .
2. The host name in the Server LAN is built using the host name and adding -se .
3. The host name in the Control LAN is built using the host name and adding -co .
4. The host name in the Client LAN is built using the host name without an extension.
5. Host names are written in lower case exclusively.
6. Host names are supposed not to be longer than 13 characters.

Installation Guide for SAP Solutions 25

6 Pre-SAP Installation Steps

6.1 General
The customary instructions and guide lines apply to the installation of the software
components. The deviations from these which are required are described here.
Don’t change the host name of the Application Node where you are going to
install the SAP and DB software.

After the installation is done, further steps are described in this document to
virtualize the SAP instance (except SAPINST 640 SR1 when used with the
SAPINST_USE_HOSTNAME parameter). Please install CI (J2EE: SCS) first, then
DB, (J2EE: JC 2nd) and the Application Server at the end.
Setup the virtual interfaces before installing the SAP solution. It is absolutly
essential to setup both virtual interfaces (client + server LAN) and make sure
that they up an running.
Please make sure that the FA Application Agents are stopped on the hosts while
you are installing SAP software:
/etc/init.d/myAMC.FA_AppAgent stop (Linux/Solaris9)
svcadm disable -s smawfa-agents (Solars10)
Check the status with:
/etc/init.d/myAMC.FA_AppAgent status (Linux/Solaris9)
svcs smawfa-agents (Solars10)
The SAP Installation CDs/DVDs have to be copied to the NetApp Filer (from the Control
Node into the directory /FlexFrame/volFF/FlexFrame/stage/SAP_SW/<SAP-CD-
name>). The whole directory or each subdirectory has to be exported on the Filer with the
necessary ro or rw options for the Application Node(s). On the Application Node, the
mount will be done manually.
If an SAP Installation is done after the initial setup of the FlexFrame environment and
without entering the SAP Service data in the FF Planning tool before, the necessary
LDAP data has to be created with the script ff_sid_adm.pl (see chapter “Adding /
Removing SAP Systems and Application” in the manual “FlexFrame™ for SAP® -
Administration and Operation”).
The directories that are necessary for SAP installation should have been created in a
step during the LDAP server setup. A script will have been created to create the SID
folder structure, if necessary.

Installation Guide for SAP Solutions 27

Pre-SAP Installation Steps

control1# ff_setup_sid_folder.sh <pool_name> <SID>

Check the folder structure as described in the SAP installation guide.

You may use ssh –X server for the Sapinst GUI. $DISPLAY should also be adequate,
like localhost:10.0.
The X connection can be tested with xclock.

RX600-01:~ # xclock

An XCLOCK should pop up on your display. If not, check the DISPLAY variable or
[Link] file.
Check the JAVA JDK:
server:~ # java -version
java version "1.4.2_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_11-b04)
Java HotSpot(TM) Client VM (build 1.4.2_11-b04, mixed mode)

Check the JAVA environment on Linux:

server:~ # echo $JAVA_HOME
/usr/java/<jdk>

Set the JAVA environment on Solaris:

server:~ # echo $JAVA_HOME
server:~ # JAVA_HOME=/usr/j2sdk/<sdk_version_dir>

Create the SAP installation directory:

server:/ # mkdir /usr/sap/<SID>/install
server:/ # chmod 777 /usr/sap/<SID>/install
server:/ # cd /usr/sap/<SID>/install

Setup the following variables, before starting the installation:

server:/ # export JAVA_HOME=/usr/java/<jdk>
server:/ # export SAPINST_JRE_HOME=/usr/java/<jdk>
server:/ # export TMP=<INSTALL_DIR>

28 Installation Guide for SAP Solutions

 Pre-SAP Installation Steps

How to configure the interfaces manually:

Solaris (client LAN: [Link] server LAN: [Link]):
server:/ # ifconfig fjgi2001:2 plumb [Link] netmask 0xffffff00
broadcast [Link] up
server:/ # ifconfig fjgi2002:2 plumb [Link] netmask 0xffffff00
broadcast [Link] up

Linux (client LAN: [Link] server LAN: [Link]):

server:/ # /sbin/ifconfig vlan2001:0 [Link] broadcast [Link]
netmask 0xffffff00
server:/ # /sbin/ifconfig vlan2002:0 [Link] broadcast [Link]
netmask 0xffffff00

6.2 SAN Configuration

Before installing a SAP system you have to prepare the SAPDATA and SAPLOG
concerning the SAN requirements. Please refer to chapter “Creating Volumes and
Filesystems” in the “Administration and Operation Guide”. Before the database instance
is installed you have to execute ff_san_mount.sh pre sapdb SID start to make the
mountpoints accessible.
Important:
Especially for MaxDB database installations there is a special reference needed to
address the data and log volumes. If you are asked for datafile directories you have to
enter /sapdb/<SID>/sapdata<n> for data volumes and /sapdb/<SID>/saplog<n>
for log volumes.
The access rights have to be set to the database user and database group.

Installation Guide for SAP Solutions 29

7 Operating System in General
The following sections describe the installation of Java SDK (JDK). If you have installed
an JDK in an old Application Node image and you change to a new image you have to
install the previous JDK in the new image in the same way. You can find the installation
path and version of JDK in the instance profile entry jstartup/jvm/home=<value>.

7.1 Solaris 8/9

7.1.1 Integrating New Java SDK (JDK) in Solaris

This section describes how a new SUN Java SDK (JDK) can be integrated in a Solaris
Boot Image using the nb_get_j2sdk script. Starting a maintenance run is not required.
It runs independently of the customary FlexFrame procedure and the commands used
there on the Control Node.
The script works interactively. For legal reasons the EULA from the SUN Java
SDK archive must be displayed and acknowledged.

The script does not belong to the basic functionality of "Netboot for Solaris" but is a
project-specific script. It is therefore supplied in the SMAWnbpw-FF4mySAP package and
normally packed to /opt/SMAW/SMAWnbpw/bin/nb_get_j2sdk.
Because of legal problems it is not possible to distribute one or more versions of the SUN
Java SDK unpacked within our Solaris Boot Images. Nevertheless this script is provided
as a simple way of making one or more versions of the JDK available in parallel in a
Solaris Boot Image.
With version 12.3 of nb_get_j2sdk it is possible to install the "Java Cryptography
Extension" (JCE) too.
Now it is possible to make the same SUN Java SDK version available in parallel as a
version without JCE and as a version which includes JCE in the same Solaris Boot
Image. The versions will be distinguished by the directory name.
After the script has been called, the new SUN Java SDK version is available in the
/usr/j2sdk/<sdk_version_dir> directory (e.g. /usr/j2sdk/j2sdk1.4.2_10) or
/usr/j2sdk/<sdk_version_dir>_jce (e.g. /usr/j2sdk/j2sdk1.4.2_10_jce) -
if JCE is installed too on all Application Nodes which were booted from the Boot Image
specified in the script call. Setting the environment variable JAVA_HOME to this path then
enables this SDK version to be used by applications.
The script has to be called once for each SUN Java SDK version which is to be stored,
and also for each Boot Image in which a version is to be stored.

Installation Guide for SAP Solutions 31

Operating System in General

1. The current J2SE SDK is loaded from

[Link]
or an older version of the SDK is loaded from
[Link]
The following files should always be fetched here:
● Solaris SPARC Platform: 32-bit self-extracting file and
● 64-bit self-extracting file

Example: j2sdk-1_4_2_11-[Link]
j2sdk-1_4_2_11-[Link]
If JCE should be installed too, the matching Java Cryptography Extension zip
file must be loaded from [Link]
Section Other Downloads and must be put beside the two self-extracting files
mentioned above.
2. The script requires the SUN Java SDK version which is to be distributed to be locally
available on the Control Node. The two files are located adjacently on the Control
Node. In addition, an active Solaris Application Node which can be addressed via the
Storage LAN is available temporarily for unpacking these files.
3. Call parameters of the script:
nb_get_j2sdk -s <SDK_archive_file> -a <app_node> -i <image> -p
-s <SDK_archive_file>
Complete path name of one of the two SUN Java SDK Solaris SPARC Platform
self-extracting files on the Control Node
(e.g. /tmp/j2sdk-1_4_2_11-[Link])
-a <app_node>
Name of the active Solaris Application Node in the Storage LAN which can be
used temporarily for unpacking the self-extracting files (e.g. AN2-st)
-i <image>
Complete path name of the Boot Image in which the SUN Java SDK version is
to be stored in the /usr part, (e.g. /FlexFrame/volFF/os/Solaris/
FSC_5.8_202_20050211/bi_FJSV,GPUZC-M_PW-P)

-p requests the unpacking of the JCE package. The installation directory is

named /usr/j2sdk/<sdk_version_dir>_jce.

32 Installation Guide for SAP Solutions

 Operating System in General

Files:
The script generates or modifies the /usr/j2sdk/<sdk_version_dir> files in the
Boot Image.

Actions:
The script performs the following actions:
● Check of the call parameter -s and its argument (SDK archive)
– A check is made to see if an absolute path was specified and all the required
files exist.
– The name of the directory in which the data is stored automatically when it is
unpacked from the SDK archive is determined. The name must be ascertained
using the javahome pattern from the archive and is designated as
<sdk_version_dir> in this text.
● Check of the call parameter -a and its argument (Application Node)
– ping is used to check whether the Application Node can be addressed.
– The root file system of this Application Node is determined via the entry in
/etc/bootparams. The SDK archive is later unpacked into this root file
system under /JDK_PACK.
● Check of the call parameter -i and its argument (Image)
– A check is made to see if an absolute path was specified, if the directory does
exist on the Control Node and if it has a correct structure.
– If it does not yet exist, the j2sdk directory is created in the /usr part of this
Boot Image.
– Checks if the SUN Java SDK version does exist already . If a SUN Java SDK
version exists, it is not overwritten as it may already be in use by one of the
Application Nodes.
● The two SUN Java SDK archive files and the JCE archive file, if available, are now
copied to /JDK_PACK in the root file system of the Application Node which is to be
used temporarily.
Afterwards, the unpacking of the two archive files on the Application Node is
triggered by two ssh calls. Both times the EULA of the SUN Java SDK is displayed
and must be acknowledged with yes. The unpacking of the JCE archive file - if
available - on the Application Node is triggered by a ssh call. Afterwards, the
unpacked files from the JCE archive are copied into the just before unpacked SUN
Java SDK to jre/lib/security.

Installation Guide for SAP Solutions 33

Operating System in General

The original files in this directory will be saved by moving to <file>_orig. The
new files from the JCE archive will be copied to <file>_jce and then linked to the
"right" name. So it is possible to identify the orginal SUN Java SDK files and the new
JCE files.

● Subsequently the /JDK_PACK/<sdk_version_dir> resp.

j2sdk/<sdk_version_dir>_jce (if JCE was installed too) directory which was
generated during unpacking is moved to j2sdk/<sdk_version_dir> in the /usr
part of the Boot Image selected.
● Finally, a cleanup takes place on the Application Node that, among other things,
deletes the /JDK_PACK directory .

7.2 Linux
In case the startup of the lsnrctl should fail during the SAP installation on
Oracle, please check section “[Link]” on page 38.

Relevant SAP Note for installation on Linux

If you want to install an SAP R/3 system on Linux, refer to SAP Note 171356.

SAP advice to use the most recent kernel

Please be advised to use one of the most recent 2.6 or 2.4 kernels for your hardware
platform and distribution. In case of problems with the operating system, please try to
reproduce it on a tested kernel and contact the support organization of your Linux
distributor if the problem persists. ([Link]/linux/platforms)

Errors while executing shell scripts

The execution of shell scripts starting with ‘:’ (instead of #!/bin/sh) causes errors or
core dumps due to the Linux kernel. Try to solve this problem by rebooting your host or
installing a new Linux kernel (see “SAP Note 359566”).
Due to the fact that the root image of Linux is read-only, please check the existence of
the following links and directory:
control1# cd /FlexFrame/volFF/os/Linux/FSC_3.2/root_img
appnode1# mkdir /oracle/ora-config/ORCLfmap

34 Installation Guide for SAP Solutions

 Operating System in General

Create the DB instance installation directory:

BLADE1:~ # mkdir /usr/sap/C11/install
BLADE1:~ # cd /usr/sap/C11/install
BLADE1:~ # mkdir C11DB
BLADE1:~ # chmod 777 C11DB
BLADE1:~ # cd C11DB

7.2.1 Integrating a new Java SDK (JDK) in Linux SLES8 /

SLES9 32bit
This section describes how to integrate a new SUN Java SDK (JDK) into a Linux Boot
Image on the FlexFrame environment without going through a maintenance cycle.
The current J2SE SDK can be downloaded from
[Link]
An older version of the SDK can be found at
[Link]

Example for an Application Node (IP address [Link]):

install <*SDK*>.rpm
Mount root fs as rw:

Export the root image as rw for only the maintenance Application Node:

control1:/FlexFrame/<filer-name>/vol0/etc # vi exports

> /vol/volFF/os/<OS>/<FF-Release>/root_img
> -ro=[Link]/24:[Link]/24,anon=0,rw=[Link]

control1:~ # rsh filer1_qa exportfs -a

Do not forget to export the root image as ro after the maintenance!

RX300-01:/ # remount rw /

Installation Guide for SAP Solutions 35

Operating System in General

Make sure that the RPM does not contain files for the var image!
RX300-01:/ # rpm -qilp <*SDK*>.rpm | less

> search for "/var"

install the RPM:

RX300-01:/ # rpm -i <*SDK*>.rpm

remount the root file system read only:

RX300-01:/ # remount ro /

control1:/FlexFrame/<filer-name>/vol0/etc # vi exports
modify the entry containing the line:
AN [Link] "rw":
#/vol/volFF/os/<OS>/<FF-Release>/root_img-
ro=[Link]/24:[Link]/24,anon=0,rw=[Link]

/vol/volFF/os/<OS>/<FF-Release>/root_img -ro=[Link]
/24:[Link]/24,anon=0
control1:~ # rsh filer1_qa exportfs –a

7.2.2 Integrating New Java SDK (JDK) in SLES9_x86

This section describes how to integrate a new IBM Java SDK (JDK) into a Linux Boot
Image on the FlexFrame environment without going through a maintenance cycle.
The IBM SDK can be downloaded from:
[Link]
avasap
To install the IBM Java, refer to the section “Integrating a new Java SDK (JDK) in Linux
SLES8 / SLES9 32bit” on how to proceed the installation.

36 Installation Guide for SAP Solutions

8 Database in General

8.1 Installation of Oracle in General

Installing more then one Oracle databases on a host:
In a FlexFrame environment, Oracle binaries are installed to a shared
filesystem. Thus you have to read the following SAP notes before installing:
SAP note 98252 (Listener), 350251 (oraInventory) and 521230 (9i) or 819829
(10g) (Oracle client software)
Before you start installing Oracle, make sure that all the required directories
have been created.
If the following error occurs during installation, check the mount option of all
Oracle directories. nolock:
ORA-01102: cannot mount the database in EXCLUSIVE mode
On Solaris it has to be llock whereas on Linux it has to be nolock.
Oracle Parameter:
After successful installation of the oracle software, please check the value of the
following parameters (init<SID>.ora / spfile<SID>.ora):
disk_asynch_io=FALSE
filesystemio_options=directio
Before starting the Oracle RUNINSTALLER (runInstaller for patches or
opatch for interim patches) please check the value of the environment variable
ORACLE_BASE=/oracle/<SID> o for the ora<sid> user (.dbenv*.*sh).

8.1.1 TNS Listener for Oracle

Virtualization of SAP Services means that it is possible to run any Oracle instance on any
Application Node. As a result, the listener task (start and stop) is performed
automatically by the FlexFrame sapdb script .
Each TNS listener can have its own listener name. In the /FlexFrame/scripts/
ora_listener_names configuration file, an individual listener name can be assigned to
each <sid>. If the entry for an <sid> is omitted, the standard listener name LISTENER
is valid. Example for /FlexFrame/scripts/ora_listener_names:

#<sid>:<listenername>
C11:MY_LISTENER
C12:YOUR_THING
P10:LISTENER_P10
P12:P12

Installation Guide for SAP Solutions 37

Database in General

Technical background
This configuration file for the SAP Service start and stop scripts is
/FlexFrame/scripts/sapdb. sapdb starts the TNS listener in accordance with these
entries.
To avoid TNS errors, please do not forget to configure these individual listener
names in [Link], too.

Oracle 10 only
LSNRCTL:
Check if the correct host name is used in the following files:
/oracle/<SID>/10[1-2]_64/network/admin/[Link]
/oracle/<SID>/10[1-2]_64/network/admin/[Link]
/sapmnt/<SID>/profile/oracle/[Link]

8.1.2 “[Link]”
Every database instance must have its own [Link].
The relevant parameter is HOST in the section LISTENER.

The example below is valid for Solaris only. On a Linux platform the IP
address of db<sid>-se has to be entered. This also applies for
[Link].
Otherwise the startup of the lsnrctl will fail with Segmentation error.

Example for a virtual DB host:

LISTENER =
(ADDRESS_LIST =
..
..
(ADDRESS =
(COMMUNITY = [Link])
(PROTOCOL = TCP)
(HOST = db<sid>-se) # Virtual host of the listener
(PORT = 1527)
)
)

38 Installation Guide for SAP Solutions

 Database in General

Example for the ADDRESS_LIST section:

LISTENER =
(ADDRESS_LIST =

(ADDRESS=
(PROTOCOL=IPC)
(KEY= <SID>.WORLD)
)
(ADDRESS=
(PROTOCOL=IPC)
(KEY= <SID>)
)

Example for the SID_LIST section:

(SID_LIST =

(SID_DESC =
(SDU = 32768)
(SID_NAME = <SID>)
(ORACLE_HOME = /oracle/<sid>/<oracle_release>_<32/64>)
# Must be available per automount
)

8.1.3 Host Name Changes in "[Link]"

The physical node name must not be entered here as HOST. The virtual node
name has to be entered here; the database is not tied to a physical node, but
only to a virtual node.
The example below is valid only for Solaris. On a Linux platform the IP
address of db<sid>-se has to be entered. Otherwise the startup of the lsnrctl
will fail with Segmentation error.

Installation Guide for SAP Solutions 39

Database in General

Example:

<SID>.WORLD=
(DESCRIPTION =
(SDU = 32768)
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = [Link])
(PROTOCOL = TCP)
(HOST = db<sid>-se) # Virtual host of the database
(PORT = 1527)
)
)
(CONNECT_DATA =
(sid = <SID>)
(GLOBAL_NAME = <SID>.WORLD)
)
)

8.2 Installation of Oracle 9.2

During the Oracle DB installation, a password for ora<sid> has to be set.
You may type in any password you want to, it has no effect.
Only ff_scripts can change a user password.
Linux Installation of Oracle patch [Link]:
Check the existence of the following directory:
/oracle/ora-config/ORCLfmap
Solaris
Before you start the Oracle installation, create the following link and directory:
mkdir /oracle/ora-config/ORCLfmap
After the installation has been completed, make sure to import the latest patch
set (read the SAP Notes 539921, 539922, 355776, 509314, and 540021).

The installation procedure will ask for /oracle/<SID>/920_<32/64> (Linux) or

/oracle/<SID>/920_64 (Solaris) and /oracle/client. All directories will be
configured automatically with LDAP. They are also part of the /etc/[Link] file.
Start installation as described in the SAP installation manual.

40 Installation Guide for SAP Solutions

 Database in General

8.2.1 Post-Oracle 9.2 Installation Steps

After installation, execute [Link] and use the parameter /oracle/<SID>
instead of the default value (/usr/local/bin).

BLADE1:/oracle/C11/920_<32/64> # ./[Link]
Running Oracle9 [Link] script...
The following environment variables are set as:
ORACLE_OWNER= oraC11
ORACLE_HOME= /oracle/C11/920_<32/64>

Enter the full pathname of the local bin directory: [/usr/local/bin]:

/oracle/C11
Copying dbhome to /oracle/C11 ...
Copying oraenv to /oracle/C11 ...
Copying coraenv to /oracle/C11 ...

Adding entry to /etc/oratab file...

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of [Link] script.
Now product-specific root actions will be performed.

8.2.2 Patch Installation

Please have a look to corresponding SAP-Sites to get the newest Patches. Before
continuing SAP-Installation install the patches as described in corresponding readme files
(either patch contains own runinstaller or patch is installed with Oracle's opatch command
interface).

8.3 Installation of Oracle 10.1 (R1)

Linux Installation:
Check the existence of the following directory:
/oracle/ora-config/oracle
LSNRCTL:
Check if the correct host name is used in the following files:
/oracle/<SID>/101_<32/64>/network/admin/[Link]
/oracle/<SID>/101_<32/64>/network/admin/[Link]
/sapmnt/<SID>/profile/oracle/[Link]

Installation Guide for SAP Solutions 41

Database in General

8.3.1 Script [Link]

After installation, execute [Link] and use the parameter /oracle/<SID>
instead of the default value (/usr/local/bin).

Example: SID=OLP
BLADE1:/oracle/OLP/101_64 # ./[Link]
Running Oracle10 [Link] script...
The following environment variables are set as:
ORACLE_OWNER= oraolp
ORACLE_HOME= /oracle/OLP/101_64

Enter the full pathname of the local bin directory: [/usr/bin]:

/oracle/OLP
Copying dbhome to /oracle/OLP ...
Copying oraenv to /oracle/OLP ...
Copying coraenv to /oracle/OLP ...
Adding entry to /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of [Link] script.
Now product-specific root actions will be performed.
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
Oracle Cluster Registry for cluster has been initialized

/bin/cp: cannot create regular file `/etc/init.d/[Link]': Read-only

file system
/bin/ln: creating symbolic link `/etc/rc.d/rc2.d/[Link]' to
`/etc/init.d/[Link]': Read-only file system

The deamon cssd is only necessary for ORACLE RAC. You can ignore the error
message regarding “Read-only file system”.
Solaris:
The full pathname of the local bin directory is also /oracle/<SID>. However
you will not receive such an error message.

42 Installation Guide for SAP Solutions

 Database in General

8.3.2 Patch Installation

Please have a look to corresponding SAP-Sites to get the newest Patches. Before
continuing SAP-Installation install the patches as described in corresponding readme files
(either patch contains own runinstaller or patch is installed with Oracle's opatch command
interface).

8.4 Installation of Oracle 10.2 (R2)

After installation, execute [Link] and use the parameter /oracle/<SID> instead
of the default value (/usr/local/bin).

LSNRCTL:
Check if the correct host name is used in the following files:
/oracle/<SID>/102_<32/64>/network/admin/[Link]
/oracle/<SID>/102_<32/64>/network/admin/[Link]
/sapmnt/<SID>/profile/oracle/[Link]

8.5 Installation of SAPDB / MaxDB

For SAP DB 7.3 NetApp ONTAP Version 7.0.1R1P1 or higher GD release is
required.

SAPDB 7.3:
If you receive the following error messages, the process for calculating the
database space could not check the available space on NFS mounted file
systems:
Sum of all datadevspaces to small for the SAP System
Please change the value of the parameter MIN_DB_SIZE in the
DATABASE.R3S file:
Section: [ADMINDBSIZE_IND_ADA]
MIN_DB_SIZE=15000 <= change the value to 1500
Save the file and restart R3SETUP.
MaxDB 7.5 / 7.6:
The description (gecos) of the sdb user and sqd<sid> users differs from
SAPDB/MaxDB version (or version of sapinst).
The LDAP entry of the depended user must be modified manually to the value
shown in the usermod which failed. To do so please use command
ff_user_adm.pl –op mod –gecos <description>
--user <user_name> --pool <pool_name>.

Installation Guide for SAP Solutions 43

Database in General

8.5.1 XUSER
After virtualizing a SAPDB/MaxDB instance, the xuser command has to be called with
the correct parameters according to OSS note 39439 and 25591.
The following screenshot shows an example for the SAPMS4 user:

Afterwards, the transaction db50 has to be called according to OSS note 588515.

[Link] Same SID on Different Platforms

When installing a SAPDB/MaxDB database with the same SID on different platforms, i.e.
an application server on Linux and the central instance on Solaris, there is a problem with
the compatibility of the file .XUSER.62. To solve this problem, the following activities
should be performed:
● Create a subdirectory /sapdb/<SID>/XUSERD on both platforms (on the NetApp
Filer they will be located in different directories containing the OS).
● Move the corresponding file /home_sap/<sid>adm/.XUSER.62 to the
subdirectory you created (repeat this step for the other platform).
● Create a soft link as follows:
cd /home_sap/<sid>adm
ln -s /sapdb/<SID>/XUSERD/.XUSER.62

44 Installation Guide for SAP Solutions

 Database in General

Due to the fact that LDAP recognizes the OS, the correct /sapdb directory will be
mounted.
During the installation of a dialog instance, you are asked to enter the host names of the
central and database instances. We recommended using the virtual names (e.g. ciml4,
dbml4-se) in this case since the file .XUSER.62 is replaced when the dialog instance is
installed and must contain the virtual database name.

8.5.2 MaxDB 7.5/7.6 /etc/opt/sdb

Before installing MaxDB 7.5/7.6 check the existence of file named /etc/opt/sdb.
If the file does not exist create it manually and insert these lines:

[Globals]
IndepData=/sapdb/data
IndepPrograms=/sapdb/programs
SdbOwner=sdb
SdbGroup=sdba

Copy the file to the /sapdb/sql/sdb directory (from the Application Node).
Check / Create the following directories (from the Application Node):
an1:~# mkdir /sapdb/data/config
an1:~# mkdir /sapdb/data/config/install

Installation Guide for SAP Solutions 45

Database in General

8.5.3 MaxDB 7.6

During the MaxDB 7.6 DB installation, a password for sqd<sid> has to be set.
Please type in the correct password (defined in LDAP) of the user sqd<sid>.

46 Installation Guide for SAP Solutions

 Database in General

8.5.4 IO Balancing
The SAPDB parameter _FBM_LOW_IO_RATE (currently only valid for releases lower than
7.4) can be set to 0 to avoid any balancing of disk usage between devspaces and to
avoid higher snapshot sizes (the default value is 10). This means IO balancing will be
stopped if the IO rate of all devspaces per second is higher than the parameter value 10.

8.5.5 Directories for sapdata / saplog

The path to the SAPDATA directories is /sapdata/sapdata<n> (analogously for
SAPLOG); a link (only versions lower MaxDB 7.6) from /sapdb/<SID>/sapdata is
created automatically.
Except sapinst from SAP Version 6.40, the SID has to be added. Please enter
/sapdata/sapdata1/<SID>, e.g.:

/sapdata/sapdata1/P11

Set the SAPLOG volumes accordingly.

/saplog/saplog1/P11

Installation Guide for SAP Solutions 47

9 SAP in General

9.1 ASCS ABAP Central Service Instance in

General
A central services instance consists of the message server and the enqueue server:
● Message server
Only one message server can run on each AS Java or AS ABAP usage type. The
message server handles the communication between the dialog instances and also
supplies information to the SAP Web dispatcher about load balancing.
● Enqueue server
The enqueue server contains a lock table that handles logical database locks plus
infrastructure locks set by Java server process. The enqueue server also
synchronizes data in a Java cluster. In usage type AS ABAP, the enqueue server
handles only locks on data objects.

9.2 SAP Java Cryptographic Toolkit

During the SAPINST installation process you will be asked about the “SAP Java
Cryptographic Toolkit”. If you select this option, some files of the JAVA directory have to
be modifiable.
However, the root file system (Linux) where the java directory is located is mounted read
only (/usr file system at Solaris) and can not be modified. In that case, logon to the
Control Node, mount the resources of the OS images and do the following steps:

9.2.1 Linux
SLES9_x86: JAVA_HOME is /opt/IBMxxxxxxxx
The example below shows SLES8 (SUN Java)
control1:~#> cd /FlexFrame/volFF/os/Linux/FSC3.2xxx/root_img/usr/java
control1:~#> cp -rp <JAVA_DIR../../../var_img/var-xxxxxxxx/<JAVA_DIR>
appnode1:~#> mount -t nfs filerxxxx:/........var-xxxxxxxx/<JAVA_DIR>
/usr/java/<JAVA_DIR>

(e.g. <JAVA_DIR> = j2sdk1.4.2_12)

Now the JAVA files are writeable.

Installation Guide for SAP Solutions 49

SAP in General

If the installation has finished successfully, do the following:

appnode1:~#> umount /usr/java/<JAVA_DIR>
control1:~#> cd ..../var_img/var-xxxxxxxx/<JAVA_DIR>
control1:~#> cp -rp <JAVA_DIR>...os/Linux/FSC3.2xxx/root_img/usr/java
/<JAVA_DIR>

(e.g. <JAVA_DIR> = j2sdk1.4.2_12)

9.2.2 Solaris
control1:~#> cd /FlexFrame/volFF/os/Solaris/<Solaris
Version>/bi..../Solaris_x/usr_sparc.all/usr/j2sdk
control1:~#> cp -rp <JAVA_DIR> ../../../../root
/<hostname_storage_ LAN>/<JAVA_DIR>
appnode1:~#> mount -F nfs filerxxxx:/vol/volFF/os/Solaris
/<Solaris_Version>/bixxxxxxxx/root/
\<host name storage LAN>/<JAVA_DIR> /usr/j2sdk/<JAVA_DIR>

Now the JAVA files are writeable.

If the installation has finished succesfully, do the following:
appnode1:~#> umount /usr/java/<JAVA_DIR>
control1:~#> cd /FlexFrame/volFF/os/Solaris/<Solaris_Version>/bi....
/Solaris_x/root/<hostname_storage_LAN>
control1:~#> cp -rp <JAVA_DIR>/FlexFrame/volFF/os/Solaris
/<Solaris_Version>/bi..../Solaris_x/usr_sparc.all/usr/j2sdk

50 Installation Guide for SAP Solutions

10 Installing SAP 4.6C SR2
Before starting with the Installation of SAP 4.6C SR2 on FlexFrame, please refer
to the original SAP installation guides. Please also get the applicable SAP notes
from the SAP Marketplace.
R3SETUP has a problem with NFS mounted file systems.
NetApp has a script which is helpful to avoid such problems. The script must be
edited.
The lines which refers to chown -R root:root /oracle and
chmod -R 777 /oracle must be deleted.
Possible Error Message:
4.6C SR2 SAPCAR aborts with error 36: staging area is not empty.
Solution: Delete all files and subdirectories in directory
/oracle/stage/920_32.
Please check the permissions of the users <sid>adm, ora<sid> and
sqd<sid>.

A workaround must be observed if SAP is installed on the NetApp Filer using R3SETUP
(up to release 4.6C). This is described in the following technical report:
SAPDB [Link]
R3SETUP does not yet permit installation of SAP on NFS drives in this version.
If sapinst is used for installation (release 4.7 and above or Web AS 6.20 or 6.40),
installation on the NetApp Filer with NFS is directly supported.

Installation Guide for SAP Solutions 51

Installing SAP 4.6C SR2

10.1 SAPDB / MaxDB / Oracle

During the installation of SAP 4.6CSR2, the R3SETUP will fail several times due to the
fact that the necessary directories, links and ownerships have already been created in
FlexFrame 3.2. The current *.R3S file (e.g. CENTRAL.R3S or DATABASE.R3S) has to be
edited and R3SETUP needs to be restarted.

The requested file system is not mounted automatically. To mount the file system, issue
the command
cd /sapmnt/<SID>/exe

and repeat the R3SETUP process until the next error occurs.

52 Installation Guide for SAP Solutions

 Installing SAP 4.6C SR2

Edit the *.R3S file and change STATUS=ERROR to STATUS=OK.

Restart R3SETUP.

Installation Guide for SAP Solutions 53

Installing SAP 4.6C SR2

Edit the *.R3S file and change STATUS=ERROR to STATUS=OK.

Restart R3SETUP.

54 Installation Guide for SAP Solutions

 Installing SAP 4.6C SR2

Edit the *.R3S file and set the parameter BREAK_ON_NFS_PERMISSION_ERROR=NO.

Restart R3SETUP.

Installation Guide for SAP Solutions 55

11 Installing Web AS 6.20
Before starting with the Installation of an SAP Solution (e.g. SAP R/3 Enterprise
4.7x2.00) on FlexFrame, please refer to the original SAP installation guides and
also get the applicable SAP notes from the SAP Marketplace.
Some new SAP Solutions (e.g. Solution Manager 3.2) are based on Web AS
6.20 but they contain the executable sapinst Version 642 from NetWeaver04
SR1. In that case we suggest using the option SAPINST_USE_HOSTNAME. See
also chapter “Installing Web AS 6.40 with NetWeaver04 SR1” on page 65.
Change to the SAP installation directory and start INSTALL/SAPINST. Use the
physical host name of the installation server when you are asked for a host
name of the CI or DB. After finishing the SAP installation, perform the post-
installation steps. See also chapter “Post-SAP Installation Steps” on page 109.
During the installation, the file /etc/services will be copied under
/etc/services.x. This will fail because the root file system is mounted read-
only. In that case, stop the installation and search for the string ERROR in the
[Link]. Change the entry to OK and restart the installation.
Please check the permissions of the users <sid>adm, ora<sid>, sqd<sid>
and sdb.

Starting SAPINST directly from the ssh –X session will cause SAPINST to abort.

Use the physical host name of the installation server when you are asked for a host name
of the CI or DB. After finishing the SAP installation, perform the post-installation steps
(see chapter ““Post-SAP Installation Steps” on page 109).

11.1 Installating Web AS 6.20 with sapinst 642

If you are not sure to have version 642 of the executable sapinst, run the command
sapinst –v; the output has to contain the string 642. Otherwise you have to continue
with the installation using the physical host name.

Installation Guide for SAP Solutions 57

Installing Web AS 6.20

11.1.1 Installing the Central Instance (CI)

In case of a virtual installation the virtual interface must be up.
Find out the IP address of the virtual hostname ciosm:

# getent hosts ciosm

[Link] ciosm <pool_name>-ciosm

Set the Client LAN interface up: Use the active interface which is not deprecated and
always has a virtual interface running, e.g. fjgi2002001:1.
Solaris:
# ifconfig fjgi2002001:2 plumb [Link] netmask 0xffffff00 broadcast
[Link] up

Linux:
# /sbin/ifconfig vlan2001:0 [Link] broadcast [Link] netmask
[Link]

baby_3:~ # cd /usr/sap/OSM/install
baby_3:~ # mkdir OSMCI
baby_3:~ # chmod 777 OSMCI
baby_3:~ # cd OSMCI

# ..../sapinst -extract
Extracting in /usr/sap/OSM/install/OSMCI...
sapinst: ok
[Link]: ok
[Link]: ok
[Link]: ok
[Link]: ok
...
[Link]: ok
Done
# SAPINST_JRE_HOME=/usr/j2sdk/j2sdk1.4.2_10
# export SAPINST_JRE_HOME
# ./sapinst SAPINST_USE_HOSTNAME=ciosm <MASTER-DVD/[Link]

58 Installation Guide for SAP Solutions

 Installing Web AS 6.20

Installation Guide for SAP Solutions 59

Installing Web AS 6.20

11.1.2 Installing the Database Instance (DB)

In case of virtual installation the virtual interface has to be up.
baby_3:~ # cd /usr/sap/OSM/install
baby_3:~ # mkdir OSMDB
baby_3:~ # chmod 777 OSMDB
baby_3:~ # cd OSMDB

# ..../sapinst -extract
Extracting in /usr/sap/OSM/install/OSMDB...
sapinst: ok
[Link]: ok
[Link]: ok

60 Installation Guide for SAP Solutions

 Installing Web AS 6.20

[Link]: ok
[Link]: ok
...
[Link]: ok
Done
# SAPINST_JRE_HOME=/usr/j2sdk/<sdk_version_dir>
# export SAPINST_JRE_HOME
# ./sapinst SAPINST_USE_HOSTNAME=dbosm-se <MASTER-DVD>/[Link]

Installation Guide for SAP Solutions 61

Installing Web AS 6.20

Due to a problem with sapinst and virtual instances, the installation process will display
an error while starting the Central Instance with the wrong instance profile.

62 Installation Guide for SAP Solutions

 Installing Web AS 6.20

To fix this problem use the following workaround:

Press Stop.
Run the following commands:
baby_3: # su – osmadm
baby_3: # startsap r3
Starting SAP Instance DVEBMGS05
-------------------------------
Startup-Log is written to /home_sap/osmadm/startsap_DVEBMGS05.log
Instance on host Baby_3 started
IGS on host Baby_3 started
baby_3: #

# cd /usr/sap/OSM/install/OSMDB
# vi [Link]

Installation Guide for SAP Solutions 63

Installing Web AS 6.20

Search for the string ERROR in the section StartSAPSystem.

Change ERROR to OK.

# ./sapinst SAPINST_USE_HOSTNAME=dbosm-se <MASTER-DVD>/[Link]

64 Installation Guide for SAP Solutions

12 Installing Web AS 6.40 with
NetWeaver04 SR1
This section is valid only for Web AS 6.40 installation prior to NW04 SR1.

Please refer to the original SAP installation guides and also get the applicable
SAP notes from the SAP Marketplace.

With the installation DVDs “NetWeaver 04 SR1”, Web AS 6.40 can be installed
on a virtual hostname. For this purpose SAP has introduced the parameter
SAPINST_USE_HOSTNAME.

You may start the installation directly from the Master DVD or create an
installation directory, extract the software into it and start the installation from
there. The second choice is described for the different SAP services.
During the installation, the file /etc/services will be copied to
/etc/services.x. This will fail because the root file system is mounted read-
only. In that case stop the installation and search for the string ERROR in
[Link]. Change the entry to OK and restart the installation.
For installation of a J2EE instance or a J2EE Add-In in an existing ABAP
instance, the service sapms<SID> of the ABAP instance will be added to the
local /etc/services file. This has to be done manually on Linux from the
Control Nodes. Afterwards, the entry has to be removed.

Installation Guide for SAP Solutions 65

Installing Web AS 6.40 with NetWeaver04 SR1

12.1 Description of Web AS 6.40 JAVA

Central Java Instance:
Java Dispatcher:
Receives client requests and
forwards them to the server
processes accordingly
Java Server Processes:
Actually process the requests
Server processes hold the
session data
Central Services Instance:
Java Enqueue Service:
Manages logical locks
Ensure server synchronization
Java Message Service:
Central service for cluster
internal communication, like
event notifications, broadcasts,
exchange of cache content etc.
Provides cluster state
information the SAP Web
Dispatcher

Change to the SAP installation directory and start SAPINST. Use the physical host name
of the installation server when you are asked for a host name of the CI, SCS or DB. After
finishing the SAP installation, perform the post-installation steps (see chapter “SAP
System Administration” on page 108).
For installation of a J2EE instance or a J2EE Add-In in an existing ABAP
instance, the service sapms<SID> of the ABAP instance will be added to the
local /etc/services file. This must be done manually on Linux from the
Control Nodes. Afterwards, the entry must be removed.

66 Installation Guide for SAP Solutions

 Installing Web AS 6.40 with NetWeaver04 SR1

12.2 Web AS 6.40 NetWeaver04SR1 JAVA

MaxDB/Oracle
Start the installation using virtual host names.
There is no difference between Linux/Solaris for the installation process.
The example shows a 6.40 JAVA NW04SR1 on MaxDB (SID=MLJ) installation.

12.2.1 SCS
Make sure that the IP interface address of the <scs_virtual_hostname> is up and
running (e.g. ifconfig <interface_name> plumb <virt_IP_address> up).

appnode1:~#> cd /usr/sap/<SID>/install_SCS
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<scs_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/product_ha.catalog

Installation Guide for SAP Solutions 67

Installing Web AS 6.40 with NetWeaver04 SR1

68 Installation Guide for SAP Solutions

 Installing Web AS 6.40 with NetWeaver04 SR1

Type in the
virtual DB host
name

Installation Guide for SAP Solutions 69

Installing Web AS 6.40 with NetWeaver04 SR1

70 Installation Guide for SAP Solutions

 Installing Web AS 6.40 with NetWeaver04 SR1

12.2.2 DB
Make sure that the IP interface address of the <db_virtual_hostname> is up and
running (e. g. ifconfig <interface_name> plumb <virt_IP_address> up).

appnode1:~#> cd /usr/sap/<SID>/install_DB
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<db_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/product_ha.catalog

Installation Guide for SAP Solutions 71

Installing Web AS 6.40 with NetWeaver04 SR1

If you install a J2EE engine using the product_ha.catalog, and during the database
installation step you see a dialog asking for an installation drive, stop the installation and
insert the following three lines to your [Link] after

var client = new ClientMapping();

var ids = ["ciHostIsUnix", "sapmntPath"]; var globalHostSID;
-if (parseBool([Link]("SeparateSCS")) &&
([Link]("ci") || context
.getBool("db")))

Insert:

if ([Link]() &&
parseBool([Link]("SeparateSCS")) &&
([Link]("ci") || [Link]("db"))) {

Now, restart SAPinst.

12.2.3 JC
Make sure that the IP interface address of the <jc_virtual_hostname> is up and
running (e. g. ifconfig <interface_name> plumb <virt_IP_address> up).

appnode1:~#> cd /usr/sap/<SID>/install_JC
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<jc_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/product_ha.catalog

12.2.4 J
Make sure that the IP interface address of the
<j_instance_number_virtual_hostname> is up and running
(e. g. ifconfig <interface_name> plumb <virt_ IP_address> up).

appnode1:~#> cd /usr/sap/<SID>/install_J<xx>
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst
SAPINST_USE_HOSTNAME=<j_instance_number_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/product_ha.catalog

72 Installation Guide for SAP Solutions

 Installing Web AS 6.40 with NetWeaver04 SR1

12.2.5 Web AS 6.40 Deployment SP16

After installing JAVA or JAVA-AddIn using the NW04 SR1 DVD/CD, proceed as follows:

[Link] JC

appnode1:~#> cd /usr/sap/<SID>/install_SP<xx>
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<jc_virtual_hostname>
[Link]

[Link] J

appnode1:~#> cd /usr/sap/<SID>/install_SP<xx>
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst
SAPINST_USE_HOSTNAME=<j_instance_number_virtual_hostname>
[Link]

12.3 Web AS 6.40 NetWeaver04SR1 ABAP Oracle

Start the installation using virtual host names.
There is no difference between Linux/Solaris for the installation process.

12.3.1 CI
Make sure that the IP interface address of the <ci_virtual_hostname> is up and
running.
appnode1:~#> cd /usr/sap/<SID>/install_CI
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<ci_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/[Link]

Installation Guide for SAP Solutions 73

Installing Web AS 6.40 with NetWeaver04 SR1

74 Installation Guide for SAP Solutions

 Installing Web AS 6.40 with NetWeaver04 SR1

Installation Guide for SAP Solutions 75

Installing Web AS 6.40 with NetWeaver04 SR1

Type in the
virtual DB host
name

76 Installation Guide for SAP Solutions

 Installing Web AS 6.40 with NetWeaver04 SR1

12.3.2 DB
Make sure that the IP interface address of the <db_virtual_hostname> is up and
running.
appnode1:~#> cd /usr/sap/<SID>/install_DB
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<db_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/[Link]

After successful loading the database, the automatic startup of SAP may fail sometimes.
● Please start the SAP manually
● Stop the SAPINST
● Modify the [Link] (search for ERROR in the section StartSAPSystem)
● Change the Status from ERROR to OK and startup the SAPINST

Installation Guide for SAP Solutions 77

Installing Web AS 6.40 with NetWeaver04 SR1

12.3.3 APP
Make sure that the IP interface address of the
<app_instance_number_virtual_hostname> is up and running.

appnode1:~#> cd /usr/sap/<SID>/install_APP
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst
SAPINST_USE_HOSTNAME=<app_instance_number_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/[Link]

12.4 Web AS 6.40 ABAP + JAVA-AddIn

NetWeaver04SR1

12.4.1 CI
Make sure that the IP interface address of the <ci_virtual_hostname> is up and
running.
appnode1:~#> cd /usr/sap/<SID>/install_CI
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<ci_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/[Link]

12.4.2 DB
Make sure that the IP interface address of the <db_virtual_hostname> is up and
running.
appnode1:~#> cd /usr/sap/<SID>/install_DB
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<db_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/[Link]

78 Installation Guide for SAP Solutions

 Installing Web AS 6.40 with NetWeaver04 SR1

12.4.3 SCS
Make sure that the IP interface address of the <ci_virtual_hostname>, DB and CI
are up and running (in Web AS 6.40 you have to use the <ci_virtual_hostname>).
Before starting the installation procedure, add the sapms<SID> entry manually
in the /etc/services (do not forget to remove the entry after the installation!).

When installing on Oracle, there is one further option “Distributed System”, that allows to
install the database schema and the JAVA part separately:
Java Database Schema Installation:
appnode1:~#> cd /usr/sap/<SID>/install
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<db_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/[Link]

Central Instance Finalization:

appnode1:~#> cd /usr/sap/<SID>/install
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<ci_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/[Link]

The example below shows an installation on MaxDB.

appnode1:~#> cd /usr/sap/<SID>/install
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<ci_virtual_hostname>
<PATH_to_SAP_MASTER_DVD>/[Link]

Installation Guide for SAP Solutions 79

Installing Web AS 6.40 with NetWeaver04 SR1

80 Installation Guide for SAP Solutions

 Installing Web AS 6.40 with NetWeaver04 SR1

Type in the
virtual CI host
name

Installation Guide for SAP Solutions 81

Installing Web AS 6.40 with NetWeaver04 SR1

When the installation has finished successfully, you have to change the
hostname of the SCS instance manually.

If the installation of the SCS Installation aborts at the step Load Java
Database Content (step 19) with the error message no connection to
network adapter, please proceed as follows:
Stop the Oracle listener process. Change the virtual host name db<sid>-se to
the real host name (uname –a) in the [Link] and [Link].
Start the Oracle listener process and click the Retry button from the SAPINST
GUI.

82 Installation Guide for SAP Solutions

 Installing Web AS 6.40 with NetWeaver04 SR1

Check and modify the following:

● Copy the .sapenv_ci<sid>.csh file to .sapenv_scs<sid>.csh
(also for the .sh file).
● Move the instance/start profile to the correct hostname.
● Exchange the hostname in the instance/start profile.
● Go to section 14.1 in this document to change the hostname for the SCS instance.

12.4.4 Web AS 6.40 Deployment SP16

[Link] DVEBMGS<id> (JAVA-AddIN)

appnode1:~#> cd /usr/sap/<SID>/install_SPxx
appnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract
appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<ci_virtual_hostname>
[Link]

If the installation of the SCS Installation aborts at the step Deploy JDDI (step 19) with
the error message no connection to network adapter, please proceed as follows:
Stop the Oracle listener process. Change the virtual host name db<sid>-se to the real
host name (uname –a) in the [Link] and [Link]. Start the Oracle
listener process and click the Retry button from the SAPINST GUI.

12.5 Web AS 6.40 Application Server JAVA-AddIn

We assume that all required components (DB, ABAP CI, JAVA-AddIn and SCS)
have already been installed.
● An /etc/services entry for <SID> is necessary for the installation only
● You have already installed a ABAP DI Instance
● Use the CD/DVD of NW04 SR1 or higher
Start up the installation as follows:
1. Extract the sapinst in the installation directory
(...<path_to_SAPINST>/sapinst –extract)

appnode1:~#> ./sapinst
SAPINST_USE_HOSTNAME=<virtual_hostname_of_APP_Server>
<PATH_to_SAP_MASTER_DVD>/[Link]

Installation Guide for SAP Solutions 83

Installing Web AS 6.40 with NetWeaver04 SR1

2. The following screen appears:

3. Choose OK
4. The instance number is the same as you have chosen for the ABAP DI
Make sure that you have deleted the /etc/services entry of your installed system
before starting the APP.

84 Installation Guide for SAP Solutions

13 Installing NetWeaver 7.0SR1/SR2
Linux:
During the installation, the file /etc/services will be copied under
/etc/services.x. This will fail because the root file system is mounted read-
only. In that case, stop the installation and search for the string ERROR in the
[Link]. Change the entry to OK and restart the installation.
For every SAP solution you have to follow the instructions of section 0.

During installation of any SAP solution the SAP or DB instance did not start up. In this
case use the FlexFrame start scripts and start the instance manually, (e.g.):

ERROR 2006-05-17 [Link]

CJSlibModule::writeError_impl()
CJS-20022 Could not start instance 'JC41' of SAP system OLP.
ERROR 2006-05-17 [Link]
CJSlibModule::writeError_impl()
CJS-20022 Could not start instance 'JC41' of SAP system

Before starting the installation of a SAP solution you should take into account that with
NetWeaver 7.0/NetWeaver 7.0SR1/SR2 a new operating system group sapinst is
requested. You need a group entry in LDAP database (pool specific) adapted to your FF
environment like the following (example):

dn:cn=sapinst,ou=Group,ou=p1,ou=Pools,ou=FlexFrame,dc=ff32,dc=wdf,
dc=fsc,dc=net
objectClass: top
objectClass: posixGroup
cn: sapinst
userPassword:: eA==
gidNumber: 3606
memberUid: orasm2
memberUid: sm2adm

Please insert this entry before you start with the installation. During the upgrade from
FlexFrame V3.1A to V4.0 this new group is not inserted automatically.
Instruction how the entry can be brought into LDAP:

LDIFIN=/tmp/ldapin
rm $LDIFIN
echo "dn: cn=sapinst,ou=Group,ou=pool1,ou=Pools,ou=FlexFrame,
dc=jer,dc=fujitsu-siemens,dc=com" >> $LDIFIN

Installation Guide for SAP Solutions 85

Installing NetWeaver 7.0SR1/SR2

echo "objectClass: top" >> $LDIFIN

echo "objectClass: posixGroup" >> $LDIFIN
echo "gidNumber: 1234" >> $LDIFIN
echo "userPassword: leer" >> $LDIFIN
echo "cn: sapinst" >> $LDIFIN

ldapmodify -x -D"cn=root,ou=LDAPadmins,ou=FlexFrame,
dc=jer,dc=fujitsu-siemens,dc=com" -w <yourPassword> -f $LDIFIN

If you upgrade from a version less than 3.2B we recommend the following commands
(example for pool pool1):

ff_sid_adm.pl --op add --pool pool1 --sid DMY --sapversion 4.6

--db ORACLE9:dbdmy-se:\* --sap ci:25:cidmy:\*:cidmy-se:\*
ff_setup_sid_folder.sh pool1 DMY
ff_sap_upgrade.pl --pool pool1 --sid dmy --sapvo 4.6 --sapvn 7.0
--dbvo ORACLE9 --dbvn ORACLE10
ff_sid_adm.pl --op del --pool pool1 --sid dmy

13.1 Installation of SAP Solutions

Select one of the SAP solution, it has no effect which DB or SAP solution you want to
install. This part is necessary for every NetWeaver 7.0SR1/SR2 installation step.

86 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

Choose the Next Button. If the next screen appears, please abort the installation.
Modify the files [Link] and sapinst in the installation directory.
[Link]:

[Link] = function() {
[Link]("[Link]()");
var changed = [Link]();
var oldUser = [Link]().getUsers().asRole([Link]);
try {
var services = [Link]("/usr/sap/sapservices/sapservices");
var exists = [Link]();

Installation Guide for SAP Solutions 87

Installing NetWeaver 7.0SR1/SR2

var node = [Link]();

[Link]("0754");
if (exists && !changed) {
[Link]();
}
…………

[Link] = function() {
[Link]("[Link]()");
[Link]();
var services = [Link]("/usr/sap/sapservices/sapservices");
if (![Link]()) {
[Link]("[Link]() done: ", services,
" doesn't exist.");
return;
}
…………

[Link] = function() {
[Link]("[Link]()");
[Link]();
var services = [Link]("/usr/sap/sapservices/sapservices");
if (![Link]()) {
[Link]("[Link]() done: ", services,
" doesn't exist.");
return;
} else {
var servicesNode = [Link](); // resolves softlinks!
var type = [Link]();
ASSERT([Link], type != "LINK", "LINK
/usr/sap/sapservices/sapservices should already be resolved.");
if (type != "FILE") {

[Link]("[Link]",
[Link](), "FILE");
}

Change the umask value entry in the sapinst file to 022:

# set umask to prevent unauthorized read

umask 022

Restart the installation:

appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<virtual_hostname>

88 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

13.1.1 Prerequisite Checker (Linux)

suse-sapinit: SAP has renamed the name of the package into sapinit
Kernel/Glibc Version: You can ignore the warning.

Installation Guide for SAP Solutions 89

Installing NetWeaver 7.0SR1/SR2

13.2 Sapinit File (Linux)

WARNING 2006-06-09 [Link]
CJSlibModule::writeWarning_impl()
Execution of the command "/usr/sap/OLP/install/SCS/[Link]"
finished with return code 1. Output:
mv: cannot move `/etc/init.d/sapinit' to `/etc/init.d/[Link]':
Read-only file system
cp: cannot create regular file `/etc/init.d/sapinit': Read-only file
system

ERROR 2006-06-09 [Link]

CJSlibModule::writeError_impl()
MUT-03011 Execution of the command
"/usr/sap/OLP/install/SCS/[Link]" finished with return code
1. Output:
mv: cannot move `/etc/init.d/sapinit' to `/etc/init.d/[Link]':
Read-only file system
cp: cannot create regular file `/etc/init.d/sapinit': Read-only file
system

ERROR 2006-06-09 [Link] [[Link]]

showDialog()
FCO-00011 The step installSAPInit with step key
|NW_Java_SCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5|0|installSA
PInit was executed with status ERROR .

Please proceed as follows:

appnode1:<INSTALL_DIR> > vi [Link]

</row>
<row>
<fld name="STEPKEY">

<strval><![CDATA[|NW_Java_SCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|
ind|5|0|installSAPInit]]>
</strval>
</fld>
<fld name="STATUS">
<strval><![CDATA[ERROR]]> to OK
</strval>
</fld>
<fld name="STOP_BEFORE">
<strval><![CDATA[]]>

90 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

</strval>
</fld>
<fld name="STOP_AFTER">
<strval><![CDATA[]]>
</strval>
</fld>
<fld name="STATE_SET_BY_STEP_STATE_EDITOR">
<strval><![CDATA[]]>
</strval>

Restart the installation:

appnode1:<INSTALL_DIR> > ./sapinst SAPINST_USE_HOSTNAME=<virt._hostname>

13.3 [Link] – symlink (Linux)

WARNING 2006-06-30 [Link]
CJSlibModule::writeWarning_impl()
Execution of the command "/usr/sap/LO7/install/ASCS/[Link]"
finished with return code 5. Output:
insserv: can not symlink(../sapinit, rc3.d/S14sapinit): Read-only file
system
insserv: can not symlink(../sapinit, rc3.d/K08sapinit): Read-only file
system
insserv: can not symlink(../sapinit, rc5.d/S14sapinit): Read-only file
system
insserv: can not symlink(../sapinit, rc5.d/K08sapinit): Read-only file
system

ERROR 2006-06-30 [Link]

CJSlibModule::writeError_impl()
MUT-03011 Execution of the command
"/usr/sap/LO7/install/ASCS/[Link]" finished with return code
5. Output:
insserv: can not symlink(../sapinit, rc3.d/S14sapinit): Read-only file
system
insserv: can not symlink(../sapinit, rc3.d/K08sapinit): Read-only file
system
insserv: can not symlink(../sapinit, rc5.d/S14sapinit): Read-only file
system
insserv: can not symlink(../sapinit, rc5.d/K08sapinit): Read-only file
system

ERROR 2006-06-30 [Link] [[Link]]

showDialog()

Installation Guide for SAP Solutions 91

Installing NetWeaver 7.0SR1/SR2

FCO-00011 The step installSAPInit with step key

|NW_ABAP_ASCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5|0|installS
APInit was executed with status ERROR .

Please proceed as follows:

appnode1:<INSTALL_DIR> > vi [Link]

<fld name="STEPKEY">

<strval><![CDATA[|NW_ABAP_ASCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind
|ind|5|0|createPorts]]>
</strval>
</fld>
<fld name="STATUS">
<strval><![CDATA[OK]]>
</strval>

appnode1:<INSTALL_DIR> > ./sapinst SAPINST_USE_HOSTNAME=<virt._hostname>

13.4 Services File (Linux)

ERROR 2006-06-20 [Link] [[Link]]
syslib::printOSError(const iastring &, int, DWORD, const
iastring &, CMessage::eLogMessage)
FSL-00001 System call failed. Error 30 (Read-only file system) in
execution of system call 'openU' with parameter (/etc/[Link],
O_WRONLY | O_TRUNC | O_CREAT, S_IRWXU | S_IRWXG | S_IRWXO), line (413)
in file ([Link]).

ERROR 2006-06-20 [Link] [[Link]]

CSyFileImpl::copy(const CSyPath & /etc/[Link],
ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const
FSL-02013 Unable to access file /etc/[Link]: cannot get write
access.

ERROR 2006-06-20 [Link] [[Link]]

CSyServicesEntryImpl::editServices(ISyServicesEntry::eWriteMode
REPLACE_NAME) const
FSL-03006 Unknown exception caught when trying to add an entry to the
service file.

ERROR 2006-06-20 [Link]

CJSlibModule::writeError_impl()

92 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error

text undefined.

Please abort the installtion and proceed as follows:

appnode1:<INSTALL_DIR> > vi [Link]

<row>
<fld name="STEPKEY">

<strval><![CDATA[|NW_ABAP_ASCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind
|ind|5|0|createPorts]]>
</strval>
</fld>
<fld name="STATUS">
<strval><![CDATA[ERROR]]> to OK
</strval>

Restart the installation:

appnode1:<INSTALL_DIR> > ./sapinst SAPINST_USE_HOSTNAME=<virt._hostname>

13.5 NetWeaver 7.0SR1/SR2 and Oracle 10(R2)

The installation could fail due to the following eror:

ERROR 2006-06-27 [Link] [[Link]]

abortInstallation
CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message:
SP2-0606: Cannot create SPOOL file "[Link]"

'UTL_RECOMP_BEGIN:'||TO_CH
--------------------------
utl_recomp_begin: [Link]

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

'UTL_RECOMP_END:'||TO_CH
------------------------
utl_recomp_end: [Link]

Disconnected from Oracle Database 10g Enterprise Edition Release

[Link].0 - 64bit Production
With the Partitioning and Data Mining options

Installation Guide for SAP Solutions 93

Installing NetWeaver 7.0SR1/SR2

.<br>SOLUTION: See ora_sql_results.log and the Oracle documentation for

details.

ERROR 2006-06-27 [Link]

CJSlibModule::writeError_impl()
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException:
error text undefined.
ERROR 2006-06-27 [Link] [[Link]]
showDialog()
FCO-00011 The step recompileDDIC with step key
|NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|in
d|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|
NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraD
bBuild|ind|ind|ind|ind|5|0|recompileDDIC was executed with status ERROR
.
Please abort the installtion and proceed as follows:
Change the umask value in the sapinst file (see section “Installation of SAP Solutions” on
page 85) and restart the installation:
appnode1:<INSTALL_DIR> > chmod 777 *
appnode1:<INSTALL_DIR> > chmod 777 .
appnode1:<INSTALL_DIR> > ./sapinst SAPINST_USE_HOSTNAME=<virt._hostname>

13.6 NetWeaver 7.0SR1/SR2 and MaxDB76

If the installation stops with the following error please abort the Installation.
Should be fixed in NetWeaver 7.0SR2.

INFO[E] 2006-03-14 [Link] [[Link]]

CSyUserImpl_getOsInfos(ILogBook *m_logBook, iastring sName,
iastring sID, tSyUserInfo& msUserinfo)
FSH-00006 Return value of function getpwnam(undefined) is NULL.

TRACE [[Link]]
bool CSyUserImpl::isExistingOnOS()
checking existence of account user="undefined" succeeded with false.

ERROR 2006-03-14 [Link] [[Link]]

CSyUserImpl::CSyUserImpl(const CUserData&, bool)
FSL-01027 Account user="undefined" does not exist.

TRACE [[Link]]

94 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

handleException<ESyException>()
Converting exception into JS Exception ESyException.

ERROR 2006-03-14 [Link]

CJSlibModule::writeError_impl()
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error
text undefined.

TRACE [[Link]]
EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.

ERROR 2006-03-14 [Link] [[Link]]

showDialog()
FCO-00011 The step sdb_create_volumes_fs with step key
|NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDB|ind|ind|ind|ind|9|0|N
W_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|2|0|S
dbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|in
d|0|0|sdb_create_volumes_fs was executed with status ERROR .

TRACE [[Link]]
showDialog()

Logon to one of the control nodes:

control1:~#> cd /FlexFrame/volFF/os/Linux/<image_name>/root_img/etc/opt
control1:~#> ls –l sdb

If the sdb file does not exist, go to section “MaxDB 7.5/7.6 /etc/opt/sdb” on page 45.

control1:~#> rm sdb
control1:~#>
cp –p /FlexFrame/volFF/pool-<pool_name>/sapdb/<image_name>/sql/sdb .

Restart the installation:

appnode1:<INSTALL_DIR> > ./sapinst SAPINST_USE_HOSTNAME=<virt._hostname>

If the installation finished succesfully change it back as it was originally:

control1:~#> cd /FlexFrame/volFF/os/Linux/<image_name>/root_img/etc/opt
control1:~#> rm sdb
control1:~#> ln –s /sapdb/sql/sdb .

Installation Guide for SAP Solutions 95

Installing NetWeaver 7.0SR1/SR2

13.7 NetWeaver 7.0SR1/SR2 / MaxDB76 and

SLES9_x86
During the ABAP import using MaxDB76 and SLES9_x86 the installation has permission
trouble:

96 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

Execution of the command "/opt/IBMJava2-amd64-142/bin/java -classpath

[Link] -showversion [Link] -dbType
ADA -importDirs
/sapcd/SAP_SW/NW2004sSR1/DVD_NW_2004s_SR1_Installation_Export/EXP1
:/sapcd/SAP_SW/NW2004sSR1/DVD_NW_2004s_SR1_Installation_Export/EXP2:/sap
cd/SAP_SW/NW2004sSR1/DVD_NW_2004s_SR1_Installation_Export/EXP3 -
installDir /usr/sap/BLM/install/DB -orderBy "" -r3loadExe
/usr/sap/BLM/SYS/exe/run/R3load -tskFiles yes -extFiles no -dbCodepage
4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -nolog -c 0" -trace all -
sapinst" finished with return code 2. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64
j9xa64142ifx-20051125 (JIT enabled)
J9VM - 20050524_1742_LHdSMr
JIT - r7_level20050518_1803)

[Link]:
/usr/sap/BLM/install/DB/import_monitor_cmd.properties (Permission
denied)
Required system resources are missing or not available:
DDL control file '/usr/sap/BLM/install/DB/[Link]' does not have
read access.

ERROR 2006-06-29 [Link]

CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 2. For
details see log file(s) import_monitor.[Link], import_monitor.log.

ERROR 2006-06-29 [Link] [[Link]]

showDialog()
FCO-00011 The step runMigrationMonitor with step key
|NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|in
d|9|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|i
nd|ind|0|0|runMigrationMonitor was executed with status ERROR .

INFO 2006-06-29 [Link] [[Link]]

Do not abort the installtion. Change the permissions of the file [Link] and use the
RETRY Button to restart the installation.

appnode1:<INSTALL_DIR> > chmod 777 [Link]

Installation Guide for SAP Solutions 97

Installing NetWeaver 7.0SR1/SR2

13.8 NetWeaver 7.0SR1/SR2 MaxDB76 and Solaris9

If you receive an error message sdb_create_db_instance during the DB installation,
please proceed as follows:

ERROR 2006-07-06 [Link]

FCO-00011 The step sdb_create_db_instance with step key
|NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|in
d|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbP
reInstanceDialogs|ind|ind|ind|ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind
|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_create_db_instance was
executed with status ERROR .

[Link] (Example: SID=CSM, Password=password)

[Link]
> Subprocess starts at 20060706112543

Execute Command : /sapdb/programs/bin/dbmcli -n dbcsm-se -R

/sapdb/CSM/db db_create CSM CONTROL,******** sqdcsm,password
Start subprocess as user with uid: root

> Subprocess stops at 20060706112545

ERR
-24875,ERR_NEEDADMI: The operating system user is not a member of the
database administrators group
-24994,ERR_RTE: Runtime environment error
20145,UNIX password ********

Follow the instructions of SAP note: 965346

Use the RETRY Button from the SAPINST screen.

13.9 NetWeaver 7.0SR1/SR2 and EP

The TCP kernel parameters tcp:tcp_conn_hash_size=23768 and
tcp:tcp_time_wait_interval=60000 are not set automatically in a FlexFrame
environment. These parameters should be set for EP. With Solaris 8/9 you set the
parameter in /etc/system on all Application Nodes. With Solaris 10 you can set these
parameters SID specific with ff_project_adm.pl.
If the installation stops with the following error do not abort the SAPINST installation:
Error: Aborted: development component 'irj'/'[Link]'/'SAP
AG'/'7.0004.20050921183647.0000':

98 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

Caught exception while checking the login credentials for SAP J2EE
Engine. Check whether the SAP J2EE Engine is up and running.
[Link]: ERROR: Cannot
connect to Host: [jcolp] with user name: [Administrator]
Check your login information.
Exception is:
[Link]:
Exception while trying to get InitialContext. [Root exception is
[Link]: Cannot
create new RemoteLoginContext instance.]

Use the configtool and change the bindHost settings as it is shown below:

p4 port: host name jc<sid>

Do not forget to restart the JC instance manually

Click the Retry button at the SAPINST screen.

Installation Guide for SAP Solutions 99

Installing NetWeaver 7.0SR1/SR2

13.10 NetWeaver 7.0SR1/SR2 ABAP+JAVA-AddIn

The installation steps of ASCS (if selected) and Database (Oracle or MaxDB) are fullfilled. During the installation of the CI instance the following error could occurre: steps
Example: SID=XOS, ORACLE10R2, PI

TYPE=A<BR>STATE=<BR>INFO_SHORT=[Link]: [Link]:
CIM_ERR_FAILED: IO error: Read timed out
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link].servlets_jsp.[Link]([Link])
at [Link].servlets_jsp.[Link]([Link])
at [Link]([Link])

100 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link](Native Method)
at [Link]([Link])
at [Link]([Link])
Caused by: [Link]: Read timed out
at [Link].socketRead0(Native Method)
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
... 30 more
caused by:
[Link]: Read timed out
at [Link].socketRead0(Native Method)
at [Link]([Link])
at [Link]([Link])

Installation Guide for SAP Solutions 101

Installing NetWeaver 7.0SR1/SR2

at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link].servlets_jsp.[Link]([Link])
at [Link].servlets_jsp.[Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])

102 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link]([Link])
at [Link](Native Method)
at [Link]([Link])
at [Link]([Link])
// => Importing Data : /usr/sap/XOS/SYS/global/sld/model/CR_Content.zip URL=[Link] USER=J2EE_ADMIN ...
Import Status: PREPARING
# ERROR: CIM_ERR_FAILED: IO error: Read timed out

Installation Guide for SAP Solutions 103

Installing NetWeaver 7.0SR1/SR2

Use the configtool and change the bindHost settings as it is shown below:

p4 port: host name ci<sid>

Do not forget to restart the CI instance manually (e.g. sapci XOS restart)

Click the Retry button at the SAPINST screen.

104 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

13.11 NetWeaver 7.0SR1/SR2 JAVA only

The steps installation of SCS and Database (Oracle or MaxDB) are fullfilled. During the
installation of the JC instance the following error could occurre:

Checking if another SDM is running on port 57518

Info: Checking if another SDM is running on port 57518
Info: Start to add definitions of SubstVars.
Info: Used addmode="replace_existing"
Info: Reading substvarfile "SUBS_PARAM_TO_BE_SET.XML".
Error: Can't read from file
/usr/sap/P11/install/JC/SUBS_PARAM_TO_BE_SET.XML.
Error: Could not add definitions of SubstVars.
Processing error. Return code: 4
Error: Processing error. Return code: 4

ERROR 2006-06-19 [Link] [[Link]]

abortInstallation
MUT-02041 SDM call of addsubstvars ends with returncode 4

ERROR 2006-06-19 [Link]

CJSlibModule::writeError_impl()
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException:
error text undefined.

ERROR 2006-06-19 [Link] [[Link]]

showDialog()
FCO-00011 The step setSubstVars with step key
|NW_Java_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|10|0|NW_C
I_Instance_Configure_Java|ind|ind|ind|ind|3|0|setSubstVars was executed
with status ERROR .

# set umask to prevent unauthorized read

umask 027

change the value of umask to 022

Restart the installation:

appnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<virt._hostname>

Installation Guide for SAP Solutions 105

Installing NetWeaver 7.0SR1/SR2

13.12 LiveCache
For LiveCache installation you have to
1. make the network interface available for lc<sid>-se
2. use lc<sid>-se for SAPINST_USE_HOSTNAME
3. during installation use lc<sid>-se for liveCache host/server
4. use default password password for user lcaadm (after installation change the
default to a password of your own)
The FA-Agents and the start and stop script expect the existence of an alias “c” for xuser.
If it does not exist please use
xuser –d SID –n host –se –u control,passw –U c –S SAPR3 –t 0 –I 0
to create. To check creation use xuser list | more.

13.13 ERS – Enque Replicated Server

For installation hints please have a look into corresponding SAP sites (start at
[Link]
9b38f8cf/[Link], Standalone Enqueue Server, High Availability, Configuration
the Replication Server).
The hostname must be set to ers<instance#><sid> as defined by planning tool or
ff_sid_adm.pl command.
With NetWeaver 7.0SR1 the scripts startsap or stopsap are (maybe) not prepared to
support ERS instances. Please check if the files contain lines like INSTANCEers.

13.14 Installation of SAP Solutions – Post Phase

The FlexFrame start/stop scripts wil start/stop the SAP service sapstartsrv
automatically.

13.14.1 Linux
Check the following links:
appnode1:/etc/init.d # cd /etc/init.d
appnode1:/etc/init.d # ls –l ./rc[3-5]/*sapinit*
lrwxrwxrwx 1 root root 10 May 18 14:58 rc3.d/K08sapinit -> ../sapinit
lrwxrwxrwx 1 root root 10 May 18 14:58 rc3.d/S14sapinit -> ../sapinit
lrwxrwxrwx 1 root root 10 May 18 14:58 rc5.d/K08sapinit -> ../sapinit
lrwxrwxrwx 1 root root 10 May 18 14:58 rc5.d/S14sapinit -> ../sapinit

106 Installation Guide for SAP Solutions

 Installing NetWeaver 7.0SR1/SR2

If the links exists with capital letter “K” or “S”, please change them to lower case. Logon
to one of the control nodes and proceed as follows:
control1:~#> cd /FlexFrame/volFF/os/Linux/<image_name>/etc/init.d
control1:~#> mv ./rc3.d/S14sapinit ./rc3.d/s14sapinit
control1:~#> mv ./rc3.d/K08sapinit ./rc3.d/k08sapinit
control1:~#> mv ./rc5.d/S14sapinit ./rc5.d/s14sapinit
control1:~#> mv ./rc5.d/K08sapinit ./rc5.d/k08sapinit

13.14.2 Solaris
appnode1:~#> ls –l /etc/rc[1-5].d/*sapinit*
lrwxrwxrwx 1 root sapinst 19 Jul 6 17:56
/etc/rc1.d/K10sapinit -> /etc/init.d/sapinit
lrwxrwxrwx 1 root sapinst 19 Jul 6 17:56
/etc/rc2.d/K10sapinit -> /etc/init.d/sapinit
lrwxrwxrwx 1 root sapinst 19 Jul 13 15:19
/etc/rc3.d/S90sapinit -> /etc/init.d/sapinit
appnode1:~#> mv /etc/rc1.d/K10sapinit /etc/rc1.d/k10sapinit
appnode1:~#> mv /etc/rc2.d/K10sapinit /etc/rc2.d/k10sapinit
appnode1:~#> mv /etc/rc3.d/S90sapinit /etc/rc3.d/s90sapinit

13.14.3 Linux and Solaris

appnode1:~#> vi /etc/init.d/sapinit

change the variable USRSAP from /usr/sap => /usr/sap/sapservices

PGM_PATH=$0
PGMNAME=sapstartsrv
ARG1=$1
ARG2=$2
ARGUMENTS=$*
USRSAP=/usr/sap/sapservices
SAPSERVICE_PATH=${USRSAP}/sapservices

Do not forget to change back the exports regarding the root image. Remount the
root image read-only.

Installation Guide for SAP Solutions 107

Installing NetWeaver 7.0SR1/SR2

13.14.4 Solaris 10 Preparations

The setting of the operating system parameters changed with Solaris 10. Instead of
settings made in /etc/system so called Resource Controls are administered in project
specifications. For further information please see the corresponding sites at SUN or get
an overview in SAP note 724713.
To keep the information consistent you use ff_project_adm.pl and
ff_user_adm.pl. The system administrator is responsible to keep this consistence.
Further information about the commands you can find in the Administration and
Operation Guide.
Examples:
Create a new project for SID T11 and assign the project to users orat11 and t11adm:
ff_project_adm.pl --op add --pool pool2 --project t11 --pid 1000
--attr '[Link]-sem-ids=(priv,...)' --users orat11,t11adm

108 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

14 Post-SAP Installation Steps

Make sure to read SAP note 867788, saposcol nfs SOL.
SAPOSCOL does not work properly on Solaris with NFS!

Some parts are only valid for some SAP Releases and products.

The example in chapter 14.1.6 could be exemplarily for all other SAP releases.

Stop all services (also lsnrctl, saposcol) and the database.

blade1:c11adm 36> stopsap

As described in theTechnology Handbook “SAP Web Application Server in Switchover

Environments” the SAPLOCALHOSTFULL is equal SAPLOCALHOST. Some SAP
applications require the FQDN for the [Link] you need FQDN you can
insert it using ff_hosts.sh.
Example for Central instance host:
● Looking for IP@ of CI: getent hosts | grep ci<sid>
● Adding alias to LDAP: ff_hosts.sh –p <pool_name> -a <ip@> -n <fqdn>

14.1 Configuring the Virtual Host Name Manually

The scripts of the start and stop mechanism for SAP solutions use the UNIX hostname
command to determine on which host they are started. This command, however, supplies
the physical node name of the host and not the required virtual host name.
You have to check that every user profile file of the SAP Administrator or Database user
does not contain a physical hostname within user profile file name. If you find a real
hostname you have to change the physical hostname to the virtual hostname.
Example:
Physical hostname: tom1bx1
Virtual hostname: ci<sid> (SAP Central Instance)
Move .saprc_tom1bx1.sh to .saprc_ci<sid>.sh.
Check if .dbenv.[c]sh and .sapenv.[c]sh already exist. If the files do not exist
please create a softlink, e.g. ln –s .dbenv_db<sid>.[c]sh .dbenv.[c]sh.
With sapinst from SAP 6.40 you have to create the softlink always.

Installation Guide for SAP Solutions 109

Post-SAP Installation Steps

To avoid changing all standard scripts that use the hostname command, this command
is simply replaced by a script of the same name for the adm and db users. The script then
always supplies the desired virtual host name. This requires the following adaptation:
Insert the following line at the beginning of the .cshrc login script in $HOME of
<sid>adm, ora<sid>(Oracle) and sqd<sid> (SAPDB/MaxDB):

# File hostname is generated to enable the virtual hostname,

# an alias activates it.
# .cshrc and .profile must contain:
# csh:
alias hostname "echo `~/hostname`"

# bash, ksh:
alias hostname="echo `~/hostname`"

If bash or sh is used as the login shell instead of csh, the relevant line has to be
activated for it.
The ~/hostname script is generated again with the matching virtual host name each
time the application or service is started by means of the “Start script for virtualizing the
applications”.

Virtual host name

appnode1:oraosm 56> vi .cshrc

#File hostname is generated to enable the virtual hostname
#the following alias activate it.

alias hostname "echo `~/hostname`"

appnode1:oraosm 4% vi hostname
#!/bin/bash
if [ ! -z "$VHOSTNAME" ]
then echo $VHOSTNAME
else ~/hostname_default
fi

appnode1:oraosm 7% vi hostname_default
echo ciosm

110 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

14.1.1 Central Instance (not valid for Web AS 6.40 J2EE)

Proceed with the following modifications:
● /home_sap/<sid>adm
After installation, rename the installed .*_<phys_hostname>.*sh
to .*_ci<sid>.*sh.
● /sapmnt/<SID>/profile
Change the profile names from *_<phys_hostname> to *_ci<sid>.
● [Link]
SAPGLOBALHOST=ci<sid>
DBHOSTNAME=db<sid>-se.
● Instance Profile
SAPLOCALHOST=ci<sid>
● Start Profile
Change all host names (containing the physical host names) to ci<sid>.

Additional for 4.6C SR2:

● /home_sap/<sid>adm
Change the file names for start/stop to new the virtual host name ci<sid>.
● /home_sap/<sid>adm
In all files change the host name to ci<sid>.
● /home_sap/<sid>adm
Delete the following line in *.cshrc:
Case Linux...

14.1.2 Database Instance (also valid for WebAS 6.40 J2EE)

Proceed with the following modifications:
● /oracle/<SID>
After installation, rename the installed .*_<phys_hostname>.*sh
to .*_db<sid>-se.*sh.
Create a symbolic link from .*_db<sid>.*sh to .*_db<sid>-se.*sh.

Installation Guide for SAP Solutions 111

Post-SAP Installation Steps

Example:

lrwxrwxrwx 1 oraq85 dba 19 2005-04-06 11:30 .dbenv_dbq85.csh

-> .dbenv_dbq85-[Link]
lrwxrwxrwx 1 oraq85 dba 18 2005-04-06 11:33 .dbenv_dbq85.sh
-> .dbenv_dbq85-[Link]

● /oracle/<SID>/<Oracle_Version>_<32/64>/network/admin
Linux:
Change the host name in the files [Link] and [Link] from
<phys host name> to the IP address of db<sid>-se
(don’t use the virtual host name!).
Solaris:
Change the host name in the files [Link] and [Link] from
<phys_hostname> to the virtual host name db<sid>-se.
● /home_sap/<sid>adm
With some SAP installations it could be necessary to create additional links
ln –s .sapenv_<host_name>_.csh .[Link]
ln –s .sapenv_<host_name>_.sh .[Link]

to make sure that the database type is recognized correctly. Depending on the type
of SAP installation it could be necessary to have further/other links. Please have a
look into the file .cshrc of <sid>adm to look for the profile names and create the
corresponding link.

14.1.3 Application Instance (not valid for WebAS 6.40 J2EE)

Proceed with the following modifications:
● /home_sap/<sid>adm
After installation, rename the installed .*_<phys_hostname>.*sh
to .*_app<id><sid>.*sh.
● /sapmnt/<SID>/profile
Change the profile names from *_<phys_hostname> to *_app<id><sid>.
Set SAPLOCALHOST=app<id><sid> in every application instance profile.
Change all host names (containing the physical host names) to app<sid> in the
start profile.

112 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

Additional Modifications for 4.6C SR2:

● /home_sap/<sid>adm
Change the file names for start/stop to the new virtual host name app<id><sid>.
● /home_sap/<sid>adm
In all files change the host name to app<id><sid>.
● /home_sap/<sid>adm
Delete the following row in *.cshrc: “Case Linux...”.

14.1.4 SCS Instance

Proceed with the following modifications:
● /home_sap/<sid>adm
After installation, rename the installed .*_<phys_hostname>.*sh
to .*_scs<id><sid>.*sh.
● /sapmnt/<SID>/profile
Change the profile names from *_<phys_hostname> to *_scs<id><sid>.
Set SAPLOCALHOST=scs<id><sid> in every application instance profile.
Change all host names (containing the physical host names) to scs<sid> in the
start profile.
Example Instance Profile:
SID=LO7 Instance=68

SAPSYSTEMNAME = LO7
SAPSYSTEM = 68
INSTANCE_NAME = SCS68
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
SAPLOCALHOST = scslo7
OS_UNICODE = uc
#-----------------------------------------------------------------------
# SAP Messaging Service for Java
#-----------------------------------------------------------------------
rdisp/msserv = 0
rdisp/msserv_internal = 3968
ms/standalone = 1
ms/server_port_0 = PROT=HTTP,PORT=81$$
#-----------------------------------------------------------------------

Installation Guide for SAP Solutions 113

Post-SAP Installation Steps

# SAP Locking Service

#-----------------------------------------------------------------------
enque/serverinst = 68
enque/table_size = 4096
rdisp/enqname = $(rdisp/myname)
enque/snapshot_pck_ids = 100

Example Start Profile :

SAPSYSTEMNAME = LO7
SAPSYSTEM = 68
INSTANCE_NAME = SCS68
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
SAPLOCALHOST = scslo7
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/LO7_SCS68_scslo7
SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
_CPARG0 = list:$(DIR_CT_RUN)/[Link]
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF)
$(_CPARG0)
OS_UNICODE = uc
#-----------------------------------------------------------------------
# Start SAP messaging service
#-----------------------------------------------------------------------
_MS = [Link]$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_01 = local rm -f $(_MS)
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/msg_server$(FT_EXE) $(_MS)
Start_Program_00 = local $(_MS) pf=$(DIR_PROFILE)/LO7_SCS68_scslo7
#-----------------------------------------------------------------------
# Start SAP locking service
#-----------------------------------------------------------------------
_EN = [Link]$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_03 = local rm -f $(_EN)
Execute_04 = local ln -s -f $(DIR_EXECUTABLE)/enserver$(FT_EXE) $(_EN)
Start_Program_01 = local $(_EN) pf=$(DIR_PROFILE)/LO7_SCS68_scslo7

114 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

14.1.5 ASCS Instance (WebAS 7.00)

Proceed with the following modifications:
● /home_sap/<sid>adm
After installation, rename the installed .*_<phys_ hostname>.*sh
to .*_ascs<id><sid>.*sh.
● /sapmnt/<SID>/profile
Change the profile names from *_<phys_hostname> to *_ascs<id><sid>.
Set SAPLOCALHOST=ascs<id><sid> in every application instance profile.
Change all host names (containing the physical host names) to ascs<sid> in the
start profile.
Example Instance Profile:
SID=LO7 Instance=67

SAPSYSTEMNAME = LO7
SAPSYSTEM = 67
INSTANCE_NAME = ASCS67
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
SAPLOCALHOST = ascslo7
#-----------------------------------------------------------------------
# SAP Messaging Service parameters are set in the [Link]
#-----------------------------------------------------------------------
ms/standalone = 1
ms/server_port_0 = PROT=HTTP,PORT=81$$
#-----------------------------------------------------------------------
# SAP Locking Service
#-----------------------------------------------------------------------
enque/table_size = 4096
rdisp/enqname = $(rdisp/myname)
enque/snapshot_pck_ids = 100

Example Start Profile:

SAPSYSTEMNAME = LO7
SAPSYSTEM = 67
INSTANCE_NAME = ASCS67
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
SAPLOCALHOST = ascslo7
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/LO7_ASCS67_ascslo7

Installation Guide for SAP Solutions 115

Post-SAP Installation Steps

SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
_CPARG0 = list:$(DIR_CT_RUN)/[Link]
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF)
$(_CPARG0)
#-----------------------------------------------------------------------
# Start SAP messaging service
#-----------------------------------------------------------------------
_MS = [Link]$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_01 = local rm -f $(_MS)
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/msg_server$(FT_EXE) $(_MS)
Start_Program_00 = local $(_MS) pf=$(DIR_PROFILE)/LO7_ASCS67_ascslo7
#-----------------------------------------------------------------------
# Start SAP locking service
#-----------------------------------------------------------------------
_EN = [Link]$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_03 = local rm -f $(_EN)
Execute_04 = local ln -s -f $(DIR_EXECUTABLE)/enserver$(FT_EXE) $(_EN)
Start_Program_01 = local $(_EN) pf=$(DIR_PROFILE)/LO7_ASCS67_ascslo7

14.1.6 NetWeaver 7.0 / NetWeaver 7.0SR1/SR2

Example:
SID=P11 SAP-solution: NetWeaver 7.0SR1 JAVA only (DB + JC + SCS + J76) User:
p11adm

-rw-r----- 1 p11adm sapsys 4818 2006-06-12 .dbenv_dbp11.csh

lrwxrwxrwx 1 p11adm sapsys 16 2006-06-19 .dbenv_dbp11-[Link]
-> .dbenv_dbp11.csh
lrwxrwxrwx 1 p11adm sapsys 15 2006-06-19 .dbenv_dbp11-[Link]
-> .dbenv_dbp11.sh
-rw-r----- 1 p11adm sapsys 4785 2006-06-12 .dbenv_dbp11.sh
-rw-r----- 1 p11adm sapsys 4818 2006-06-19 .dbenv_j76p11.csh
-rw-r----- 1 p11adm sapsys 4786 2006-06-19 .dbenv_j76p11.sh
-rw-r----- 1 p11adm sapsys 4818 2006-06-19 .dbenv_jcp11.csh
-rw-r----- 1 p11adm sapsys 4786 2006-06-19 .dbenv_jcp11.sh
-rw-r----- 1 p11adm sapsys 4818 2006-06-19 .dbenv_scsp11.csh
-rw-r----- 1 p11adm sapsys 4786 2006-06-19 .dbenv_scsp11.sh
-rw-r----- 1 p11adm sapsys 757 2006-06-19 .j2eeenv_j76p11.csh
-rw-r----- 1 p11adm sapsys 825 2006-06-19 .j2eeenv_j76p11.sh

116 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

-rw-r----- 1 p11adm sapsys 757 2006-06-09 .j2eeenv_jcp11.csh

-rw-r----- 1 p11adm sapsys 825 2006-06-09 .j2eeenv_jcp11.sh
-rw-r----- 1 p11adm sapsys 757 2006-06-09 .j2eeenv_scsp11.csh
-rw-r----- 1 p11adm sapsys 825 2006-06-09 .j2eeenv_scsp11.sh
lrwxrwxrwx 1 p11adm sapsys 20 2006-06-19 .sapenv_dbp11.csh
-> .sapenv_dbp11-[Link]
-rw-r----- 1 p11adm sapsys 8325 2006-06-09 .sapenv_dbp11-[Link]
-rw-r----- 1 p11adm sapsys 7693 2006-06-09 .sapenv_dbp11-[Link]
lrwxrwxrwx 1 p11adm sapsys 19 2006-06-19 .sapenv_dbp11.sh
-> .sapenv_dbp11-[Link]
-rw-r----- 1 p11adm sapsys 8325 2006-06-19 .sapenv_j76p11.csh
-rw-r----- 1 p11adm sapsys 7693 2006-06-19 .sapenv_j76p11.sh
-rw-r----- 1 p11adm sapsys 8325 2006-06-09 .sapenv_jcp11.csh
-rw-r----- 1 p11adm sapsys 7693 2006-06-09 .sapenv_jcp11.sh
-rw-r----- 1 p11adm sapsys 8325 2006-06-09 .sapenv_scsp11.csh
-rw-r----- 1 p11adm sapsys 7693 2006-06-09 .sapenv_scsp11.sh
-rw-r----- 1 pl1adm sapsys 1322 2006-06-19 .sapsrc_j76p11.csh
-rw-r----- 1 pl1adm sapsys 1118 2006-06-19 .sapsrc_j76p11.sh
-rw-r----- 1 pl1adm sapsys 1322 2006-06-09 .sapsrc_jcp11.csh
-rw-r----- 1 pl1adm sapsys 1118 2006-06-09 .sapsrc_jcp11.sh
-rw-r----- 1 p11adm sapsys 1322 2006-06-09 .sapsrc_scsp11.csh
-rw-r----- 1 p11adm sapsys 1118 2006-06-09 .sapsrc_scsp11.sh

14.2 Configuring the Virtual Host Name for Web AS

6.40 ABAP and JAVA-AddIn / WebAS 6.40 JAVA
Proceed with the following modifications:
● /home_sap/<sid>adm
After installation, rename the installed .*_<phys host name>.*sh to
*_ci<sid>.*sh (not valid for WebAS 6.40 JAVA only), j2eeenv_xxx.* and
*JC<ID>_jc<sid> (only valid for WebAS 6.40 JAVA) files as well.

Installation Guide for SAP Solutions 117

Post-SAP Installation Steps

● /sapmnt/<SID>/profile
Change the profile name from *_DVEBMGS<ID>_<phys_hostname> to
*_DVEBMGS<ID>_ci<sid>. (not valid for 6.40 JAVA only).
Change the profile name from *_SCS<ID>_< phys_hostname> to
*_SCS<ID>_scs<sid>.

● WebAS 6.40 ABAP + JAVA-AddIn

Change the host name to ci<sid> in [Link] and in the CI start profile. Set
DBHOSTNAME=db<sid>-se. Set SAPLOCALHOST=ci<sid> in the CI profile.
Change the host name to scs<sid> in the SCS start profile. Set
SAPLOCALHOST=scs<sid> in the SCS profile.
Set SAPLOCALHOST=app<id><sid> in every application instance profile.
● WebAS 6.40 JAVA:
Change the SAPJDBHOST and j2ee/dbhost to db<sid>-se in the [Link].
Change the host name in the SCS start profile to scs<sid>.
Set the SAPLOCALHOST=scs<sid> in the SCS profile.
Set the SAPLOCALHOST=jc<sid> in the JC profile.

118 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

Set the SAPLOCALHOST=j<id><sid> in every application instance profile.

[Link] (WebAS 6.40 ABAP + JAVA-AddIn):

bash-2.03# cat [Link]

SAPGLOBALHOST = cios4
SAPDBHOST = dbos4-se
rdisp/mshost = cios4
SAPSYSTEMNAME = OS4
rdisp/accept_remote_trace_level = 0
rdisp/sna_gateway = cios4
rdisp/sna_gw_service = sapgw67
rslg/collect_daemon/listen_port = 3967
rslg/collect_daemon/talk_port = 4067
rdisp/bufrefmode = sendon,exeauto
ms/server_port_0 = PROT=HTTP, PORT=8167
dbs/ora/tnsname = OS4
DIR_CLIENT_ORAHOME = /oracle/OS4/920_64
DIR_SERVER_ORAHOME = /oracle/OS4/920_64
j2ee/dbname = OS4
j2ee/dbtype = ora
j2ee/dbhost = dbos4-se

[Link] (WebAS 6.40 JAVA):

bash-2.03# cat [Link]

SAPSYSTEMNAME = OLI
SAPJDBHOST = dboli-se
j2ee/dbname = OLI
j2ee/dbtype = ora
j2ee/dbhost = dboli-se

Start profile (e.g. START_SCS68_scsos4):

bash-2.03# cat START_SCS68_scsos4
#-----------------------------------------------------------------
# Global variables
#-----------------------------------------------------------------
SAPSYSTEMNAME = OS4
INSTANCE_NAME = SCS68
DIR_EXECUTABLE = /usr/sap/OS4/SYS/exe/run
DIR_LIBRARY = /usr/sap/OS4/SYS/exe/run

Installation Guide for SAP Solutions 119

Post-SAP Installation Steps

#-----------------------------------------------------------------
# Start SAP messaging service
#-----------------------------------------------------------------
_MS = ms.sapOS4_SCS68
Execute_00 = local rm -f $(_MS)
Execute_01 = local ln -s -f $(DIR_EXECUTABLE)/msg_server $(_MS)
Start_Program_00 = local $(_MS) pf=$(DIR_PROFILE)/OS4_SCS68_scsos4

#-----------------------------------------------------------------
# Start SAP locking service
#-----------------------------------------------------------------
_EN = en.sapOS4_SCS68
Execute_02 = local rm -f $(_EN)
Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/enserver $(_EN)
Start_Program_01 = local $(_EN) pf=$(DIR_PROFILE)/OS4_SCS68_scsos4

Instance Profile (e.g. OS4_SCS68_scsos4) :

bash-2.03# cat OS4_SCS68_scsos4

SAPSYSTEMNAME = OS4
SAPLOCALHOST = scsos4
SAPLOCALHOSTFULL = scsos4
INSTANCE_NAME = SCS68
SAPSYSTEM = 68
DIR_GLOBAL = /sapmnt/OS4/global
DIR_PROFILE = /sapmnt/OS4/profile
DIR_EXECUTABLE = /usr/sap/OS4/SYS/exe/run
rdisp/msserv = 3668
enque/table_size = 4096
enque/deque_wait_answer = FALSE
enque/process_location = LOCAL
enque/encni/port = 3268
rdisp/enqname = $(rdisp/myname)
enque/snapshot_pck_ids = 100
ms/server_port_0 = PROT=HTTP, PORT=8168

Adapt the J2EE Configuration Tool

For WebAS 6.40 ABAP + Java-AddIn, use the host name ci<sid> and
jc<sid> for WebAS 6.40 JAVA.

The example below uses WebAS 6.40 ABAP + JAVA-AddIn (SID=OS4)

120 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

control1:~ # ssh -X os4adm@Baby_1

os4adm@Baby_1's password:
Baby_1:os4adm 38> cd /usr/sap/OS4/DVEBMGS67/j2ee/configtool/
[Baby_1:oliadm 38> cd /usr/sap/OLI/JC16/j2ee/configtool/] for WebAS
6.40 JAVA
Baby_1:os4adm 39> ./[Link]
Connect to DB? Yes

Installation Guide for SAP Solutions 121

Post-SAP Installation Steps

122 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

Installation Guide for SAP Solutions 123

Post-SAP Installation Steps

to change: profile
name + host

Type in Value: <Custom value> for each line and click on Set.

124 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

Installation Guide for SAP Solutions 125

Post-SAP Installation Steps

to change: profile
name + host

Check the host name of the SCS for all installed instances

Recommendation:
If you plan to install several DI Instances, finish the virtualization step of the ABAP +
JAVA-AddIn Instances. During the installation step you’ll be asked for names of the DB
and CI, type in the virtual hostnames.

126 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

Installation Guide for SAP Solutions 127

Post-SAP Installation Steps

128 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

Installation Guide for SAP Solutions 129

Post-SAP Installation Steps

Adapt the J2EE Offline Configuration Tool:

control1:~ # ssh -X os4adm@Baby_1
os4adm@Baby_1's password:
Baby_1:os4adm 38> cd /usr/sap/OS4/DVEBMGS67/j2ee/configtool/
Baby_1:os4adm 39> ./[Link]

130 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

doubleclick

Click on the edit key.

Click Yes and afterwards double-click the Propertysheet Instance.

Installation Guide for SAP Solutions 131

Post-SAP Installation Steps

Click on OK and exit.

132 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

Change the following files:

Baby_1:os4adm 59> cd /usr/sap/OS4/DVEBMGS67/SDM/program
Baby_1:os4adm 63> vi [Link]

workingHost=cios4
workingDirectory=/usr/sap/OS4/DVEBMGS67/SDM/program
workingPort=50118
workingFrogTheme=Bright Harmonic
workingLookAndFeel=[Link]
~
~

Baby_1:os4adm 64> cd config

Baby_1:os4adm 66> vi [Link]

</AdminPort>
<Host>
scsos4
</Host>
<RootDir>
/usr/sap/OS4/DVEBMGS67/SDM/root
</RootDir>
<MaxBackups>
10
</MaxBackups>
<CurrentBackup>
6
</CurrentBackup>
<CurrentFlowBackup>
8
</CurrentFlowBackup>
<HashedPassword>
yPLDEBe3oOb6H2mmjJ0zztOgw/A=
</HashedPassword>
<JStartup-Configuration active="true">
<mshost>
scsos4
</mshost>
<msport>
3600

:wq

Change hosts and directory.

Installation Guide for SAP Solutions 133

Post-SAP Installation Steps

14.3 Start Script startdb for Oracle and

SAPDB/MaxDB
The database (Oracle, SAPDB/MaxDB) is not started implicitly with the startsap (and
startdb) standard script in the exe/run directory, but separately using the service
script from SAP. In sapdb, the standard script startdb/startj2eedb is called.
Thanks to the automount mechanism, the exe/run directory is also available on the
database node.

14.4 Stop Script stopdb for Oracle and

SAPDB/MaxDB
The remarks on the start script startdb made in the previous section apply to the
stopdb stop script analogously.

14.5 Scheduling of Batch Jobs (CCMS)

If no application server is present, the following applies:
If you do not have the remote shell remsh on your systems, you have to set the profile
parameter gw/remsh (or dta/remsh/cmd) in the instance profile of the application
server, on which the job is running, to the name of your remote shell program, for
example, ssh.
On a UNIX system, use the command which ssh to find out where the ssh command is
located. You can check this as a standard user by calling the following command:
$ which <program_name>

The SAP control program sapxpg has to be found in the search path of the standard
SAP user on the remote host. SAPXPG is stored in the SAP executables directory. If the
external program was not specified with an absolute path name, then the external
program also has to be found in the search path of the standard SAP user. In UNIX you
can check this in the standard user by calling the following command:
which <program_name> while logged on as the standard user.
Both the SAP control program sapxpg and the external program to be started has to be
executable under the standard SAP user. For example, on a UNIX machine this means
that <sid>adm must have execute permission (‘x’) for the programs.
Change the parameter gw/remsh in every instance profile to /usr/bin/ssh (Linux) or
to /opt/SMAWPlus/bin/ssh (Solaris8) or /usr/bin/ssh (Solaris9). To check
whether the program ssh is located, issue the which command.

134 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

SSH Configuration:
The host the job is running on must have permission to start programs on the remote
host.
Baby_1:oacadm 60% ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home_sap/oacadm/.ssh/id_rsa):
Created directory ‘/home_sap/oacadm/.ssh
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home_sap/oacadm/.ssh/id_rsa.pub.
Your public key has been saved in /home_sap/oacadm/.ssh/id_rsa.pub.
The key fingerprint is:
[Link] oacadm@Baby_1
Baby_1:oacadm 61% cd .ssh
Baby_1:oacadm 62% ls
id_rsa.pub id_rsa
Baby_1:oacadm 63% cp –p id_rsa.pub authorized_keys

Baby_1:oacadm 64% chmod 700 /home_sap/oacadm

Baby_1:oacadm 65% chmod 700 /home_sap/oacadm/.ssh

14.6 Profile Parameters for [Link]

Example for “SID = O12” and “system number = 12”:

SAPSYSTEMNAME = O12
SAPDBHOST = dbo12-se
rdisp/mshost = cio12
rdisp/sna_gateway = cio12
rdisp/sna_gw_service = sapgw12
rdisp/vbname = cio12_O12_12
dbs/ora/tnsname = O12
rdisp/enqname = cio12_O12_12
rdisp/btcname = cio12_O12_12
rslg/collect_daemon/listen_port = 3912
rslg/collect_daemon/talk_port = 4012
rdisp/bufrefmode = sendon,exeauto

Installation Guide for SAP Solutions 135

Post-SAP Installation Steps

14.7 Profile Parameters for the Start Profile

If the SAP instance is installed in accordance with the instructions given here, the start
profile of the Central Instance or the Application Instances should contain the virtual host
name, which is part of the start and instance profiles.
If the SAP instance has not been installed in accordance with these instructions, the
names of the start and instance profiles, and of course the associated parameters in the
start profiles, they have to be adapted accordingly.
Example with SID=O12, central instance number = 12, dialog instance number = 62, and
physical host name = mhm305:
Profile names (conventional installation): Profile names (virtual installation):
START_D62_mhm305 START_D62_app62o12
O12_D62_mhm305 O12_D62_app62o12
START_DVEBMGS12_mhm305 START_DVEBMGS12_cio12
O12_DVEBMGS12_mhm305 O12_DVEBMGS12_cio12

14.8 Profile Parameters for the Instance Profile

The SAP instance runs with a virtual host name instead of the physical host name. The
SAPLOCALHOST parameter has to be set accordingly.

Syntax for the host name (ABAP)

Central instance: ci<sid>
ABAP central services instance: ascs<sid>
Application instance: app<id><sid>

Syntax for the host name (JAVA)

Java Control instance: jc<sid>
SAP common services: scs<sid>
Java application instance: j<id><sid>

Example for a Central Instance with “SID = CB1”:

SAPLOCALHOST = cicb1

Example for an Application Instance with “instance number = 01” and “SID = CB1”:

SAPLOCALHOST = app01cb1

136 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

Enable Memory Auto Management

Please check the parameters according to SAP Note 386605:

es/implementation = map
PHYS_MEMSIZE = 50%

The following profile parameters have to be disabled after this:

em/max_size_MB = 1024
em/initial_size_MB = 1024
em/address_space_MB = 1024
em/blocksize_KB = 1024
em/stat_log_size_MB = 20
em/stat_log_timeout = 600
rdisp/ROLL_SHM = 128
rdisp/ROLL_MAXFS = 32768
rdisp/PG_SHM = 0
rdisp/PG_MAXFS = 2048
ztta/roll_first = 1024
ztta/roll_area = 9216000

14.9 SAP Start and Stop Mechanism (Release

4.6CSR2)
The SAP start and stop mechanism has changed in Kernel release 6.x. The scripts
startsap and stopsap are now located in the /usr/sap/<sid>/SYS/exe/run
directory. For this reason, the aliases startsap and stopsap, as well as the startsap
<hostname>_<sysnr> and stopsap_<hostname>_<sysnr> start and stop scripts in
/home/<sid>adm exist no longer.
If you wish to use an older kernel release lower than WAS 6.10, it has to be
converted to the new start and stop mechanism first.

Procedure
Install and configure the virtual host name as described above, separately for the
database and the SAP instance. Remove the startsap_<hostname>_<inr> and
stopsap_<hostname>_<inr> scripts from $HOME of <sid>adm. They are both
replaced by a single new script.

Installation Guide for SAP Solutions 137

Post-SAP Installation Steps

Comment out the lines for the aliases startsap and stopsap in the .sapenv_*.csh
scripts:

set hostname=`hostname`
# 12.08.02
#unset list
#set list=`$lscommand $HOME | grep '^startsap_'${hostname}'_[0-9]
[0-9]$'`
#if ( `echo $list | wc -w` == 1 ) then
# alias startsap $HOME/$list
#else
# alias startsap "echo 'To start an instance use one of the following
scripts:
#endif
#
#unset list
#set list=`$lscommand $HOME | grep '^stopsap_'${hostname}'_[0-9][0-9]$'`
#if ( `echo $list | wc -w` == 1 ) then
# alias stopsap $HOME/$list
#else
# alias stopsap "echo 'To stop an instance use one of the following
scripts:';
#endif
#
# end SAP R/3 Environment

Place the startsap and stopsap scripts of release 6.x in the /sapmnt/<sid>/exe
directory.
Make sure that all the permissions of the SAP kernel in this directory are set to
<sid>adm:sapsys. After changing the rights with chown
<sid>adm:sapsys_*, start the [Link] <sid> script.
The new scripts should look like this:

#!/bin/sh
#-----------------------------------------------------------------
#
# NAME :
# startsap
#
# PURPOSE :
# Start SAP Database and SAP Instances
#
# USAGE: startsap [db|r3|all|check] [<instance>]
#
# Specify instance if you have installed multiple

138 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

# instances of the same system on one host.

# Example: startsap r3 DVEBGMS00
#
# other optional parameters:
# check Check Database and SAP Instance
# r3 | R3 Start SAP Instance only
# db | DB | dB | Db Start Database only
# ALL | all Start Database and SAP Instance

14.10 SAP License

Since the SAP license of the active system becomes invalid after the Central Instance
has been switched over, a temporary license can always be used with the current SAP
license program. Please refer to SAP notes 538081 and 870871 for details on this matter.

14.11 SAPLogon – SAPGUI

Usage
An SAP application instance is accessed via the Client LAN and not via the Server LAN.
This means that SAPGUI or SAP Logon have to communicate with the virtual Client LAN
address of the application instance. If a specific application instance is entered in SAP
Logon with its virtual Client LAN address, access will function as before.
If a logon group is entered in SAP Logon, the Client LAN address has to be specified for
the application instance in the transaction SMLG so that the message server can report it
to SAP Logon. By default, the message server reports the Server LAN address to SAP
Logon on the basis of the naming convention for the instance name
<hostname>_<sid>_<inr>. Instead, static routes may also be entered on the
Application Nodes; however, this would make it necessary to enable IP forwarding.

Installation Guide for SAP Solutions 139

Post-SAP Installation Steps

Example of CB1 with two Application Instances and a Logon Group.

Logon group “PUBLIC”.

140 Installation Guide for SAP Solutions

 Post-SAP Installation Steps

Enter the virtual IP address of the Client LAN.

Installation Guide for SAP Solutions 141

Post-SAP Installation Steps

14.12 SAPROUTER on the Control Node

The saprouter (/FlexFrame/volFF/FlexFrame/saprouter) routes the nodes
from the workstation network 100.10.100.* to the Client LAN of the virtual SAP
Services:

/FlexFrame/volFF/FlexFrame/saprouter/saprouttab
#
# from to service
#
# workstation-lan client-lan
P 100.10.100.* 10.0.190.* *

If the virtual host names are entered in saplogon instead of the IP addresses, the
names have to be resolved on the saprouter:

Hosts in LDAP
[Link] cibw1
[Link] cicb1
[Link] app01cb1
[Link] app02cb1

Services in LDAP
sapdp01 3201/tcp # SAP System Dispatcher Port
sapdp02 3202/tcp # SAP System Dispatcher Port
sapmsCB1 3600/tcp # SAP System Message Port
sapdp20 3220/tcp # SAP System Dispatcher Port

142 Installation Guide for SAP Solutions

 SAP System Administration

15 SAP System Administration

15.1 Upgrading Application Software

The documentation for installing the application software also applies here.
One Application Node should be available exclusively for upgrading the application
software.
Provided this has been done, upgrading can be carried out in accordance with the
software vendor’s standard guidelines.

15.2 Software Administration

15.2.1 Starting and Stopping SAP Services

Virtualization of the SAP Services demands special measures for starting, stopping,
restarting them, etc. These measures are catered for by an SAP Service script for each
service type.
The SAP Services must not be started directly, e.g. for SAP R/3 as <sid>adm
with startsap, since in this case the interfaces are neither supplied with IP
addresses, nor is the service control file updated. The started application will not
work due to the lack of a network connection.

[Link] SAP Service Scripts

Each service type has its own script. The service type is part of the script name:

Script name Application

sapapp Starting and stopping an application server (ABAP)
sapascs Starting and stopping the ABAP central services instance
sapci Starting and stopping a central instance (ABAP)
sapdb Starting and stopping Oracle, SAPDB, MaxDB
sapers Starting and stopping Enqueue Replicated Server
sapj Starting and stopping a J2EE application instance
sapjc Starting and stopping the J2EE central instance

Installation Guide for SAP Solutions 143

SAP System Administration

Script name Application

saplc Starting and stopping LiveCache
sapscs Starting and stopping the SAP common services

The call syntax for sapascs, sapci, sapdb, saplc and sapscs is:
<scipt_name> <sid> <action> [nosignal]
The call syntax for sapapp, sapers and sapj is:
<scipt_name> <id> <sid> <action> [nosignal]

The call parameters are:

● <id>
Distinction of several similar instances of a service type of an SID; 2 digits,
numerical.
● <sid>
System ID (SID), 3-digit, in lower case.
● <action>
The action to be performed with the application or service. The actions are start,
stop, restart, status, cleanup, watch and nowatch.
● Nosignal
When the application is started, this has the effect that no monitoring by the high-
availability software FA Agent takes place.

Call from the Control Node using ssh with reference to the example of sapapp:

ssh <Application_Node_name> sapapp <id> <sid> <action> [nosignal]

Example
The application server of the system CB1 with the ID 01 is to be started on the node
blade3; let us assume that the Control Node is control1.
Execute the following as root in the command shell of control1:

control1 # ssh blade3 sapapp 01 cb1 start

144 Installation Guide for SAP Solutions

 SAP System Administration

[Link] SAP Service Script Actions

● start
This checks whether the application or service in question is already running. If it is,
it is not restarted. It also checks whether required applications or services are
running.
The required virtual IP addresses are assigned to the relevant interfaces for the
Client LAN and Server LAN (ifconfig <ifc> <ip-adr> netmask <netmask>
up). The application is started and the service control file is written.
● stop
This checks whether the application or service in question is running. If it is running,
it is stopped.
The application is terminated, the service control file is deleted and the virtual IP
addresses are separated again from the interfaces (ifconfig <ifc> down).
● status
This checks the logical status of the application or service. The functional availability
is not tested.
● restart
This merges the actions stop, cleanup and start in one call; restart is
intended for restarting a malfunctioning application.
● cleanup
This kills application processes that are still running and deletes occupied resources
such as shared memory, semaphores and the message queue.
Note that this action may only be performed after an attempt to stop the application
has failed.
● nowatch
This removes the application from monitoring by the high-availability software FA
Agent without the application having to be restarted. The application itself retains its
current status. The default status after application startup is 'watch'.
● watch
This includes the application again in monitoring by the high-availability software
(FA Agents) without having to restart the application. The application itself retains its
current status.

Installation Guide for SAP Solutions 145

SAP System Administration

[Link] Return Codes of the SAP Service Scripts

The SAP Service scripts issue a return code (exit code). The meaning of this code can be
looked up in the sapservice_functions file:

#=================================================================
# common exit codes for service scripts
#
no_error=0 # Bit 0,
wrong_parameter_count=1 # Bit 1, wrong number of parameters
plausibility_error=2 # Bit 2, plausibility error
interface_server_lan_error=4 # Bit 3, error at server lan interface
up/down
interface_client_lan_error=8 # Bit 4, error at client lan interface
up/down
any_error=32 # Bit 5, any other error
san_mount_error=64 # Bit 6, san mount error
user_script_error=128 # Bit 7, user script error

# rule is logical OR:

# let exit_code="exit_code|new_exit_code"
# if [ `expr $exit_code&4` -eq 4 ];then ......
# if [ `let xxx="$rc & 4";echo $xxx` -ne 4 ];then ...
#=================================================================

[Link] Joined SAP Service Scripts

The following scripts are provided for jointly starting and stopping applications and
services:

Script name Application Place of execution

start_all_sapservices Initial start of all Only on a Control
configured applications Node
stop_all_sapservices Stopping of all active Only on a Control
applications Node
stop_all_sapservices_SID Stopping of all active Only on a Control
applications of one SID Node
stop_all_sapservices_local Stopping of all active Only on an Application
applications on the local Node
node

These scripts are called with call parameters.

146 Installation Guide for SAP Solutions

 SAP System Administration

To enable graceful shutdown of the node, the script stop_all_sapservices_local

can be appended in the relevant run levels:

# Stop all sapservices

/etc/rc.d/rc3.d # ln -s /FlexFrame/scripts/stop_all_sapservices_local
K02mySAP
/etc/rc.d/rc5.d # ln -s /FlexFrame/scripts/stop_all_sapservices_local
K02mySAP

15.2.2 Removing an Application from Monitoring by FA

Agents
If the applications or services are started with the scripts for virtualization, they are
monitored by the FA Agents’ high-availability software. If you do not want this, be it for
tests, installation or upgrades, you have to inform the high-availability software of this
using the additional parameter nowatch when the application is started.
Examples:
The central instance of BW1 is to be started without monitoring by the high-availability
software:
blade1 # sapci bw1 start nowatch

or from a Control Node:

control1 # ssh blade1 sapci bw1 start nowatch

If an active application is to be included (again) in monitoring by the high-availability

software without being restarted, this is possible using the watch option. The application
then retains its current status.
The central instance of BW1 is to be included in monitoring by the high-availability
software while running:
blade1 # sapci bw1 watch

or from a Control Node:

control1 # ssh blade1 sapci bw1 watch

15.2.3 Application Software

Please refer to the standard documents for SAP Services (R/3, BW, CRM, etc.)
The virtual host name always has to be used for administering and configuring spool
servers, batch servers, RFC connections, etc.

Installation Guide for SAP Solutions 147

SAP System Administration

15.3 SAP Release Upgrade

15.3.1 Services Port

If you plan an SAP Release upgrade, you have to add a special service port (called
shadow instance) to LDAP.
Please use the ff_sap_shadowport.sh script. If you issue the script the usage will be
shown.

15.3.2 Group Sapinst

If you plan an SAP NetWeaver 7.0SR1 Release upgrade, you have to add the depended
<sid> users to the new group sapinst.
Example for group sapinst:

dn:cn=sapinst,ou=Group,ou=p1,ou=Pools,ou=FlexFrame,dc=ff32,dc=wdf,dc=fsc
,dc=net
objectClass: top
objectClass: posixGroup
cn: sapinst
userPassword:: eA==
gidNumber: 3606
memberUid: orasm2
memberUid: sm2adm

Please insert this entry before you start with the installation. During the upgrade from
FlexFrame V3.1A to V4.0 this new group is not inserted automatically.
Instruction how the entry can be brought into LDAP:
LDIFIN=/tmp/ldapin
rm $LDIFIN
echo "dn: cn=sapinst,ou=Group,ou=pool1,ou=Pools,ou=FlexFrame,
dc=jer,dc=fujitsu-siemens,dc=com" >> $LDIFIN
echo "objectClass: top" >> $LDIFIN
echo "objectClass: posixGroup" >> $LDIFIN
echo "gidNumber: 1234" >> $LDIFIN
echo "userPassword: leer" >> $LDIFIN
echo "cn: sapinst" >> $LDIFIN

ldapmodify -x -D"cn=root,ou=LDAPadmins,ou=FlexFrame,
dc=jer,dc=fujitsu-siemens,dc=com" -w <yourPassword> -f $LDIFIN

148 Installation Guide for SAP Solutions

 SAP System Administration

15.3.3 FA-Agent
Solaris 10 only:
Please make sure that the FA Application Agents are stopped on the hosts while you are
updateting the SAP software:
Stop the FA-Agent:
svcadm disable -s smawfa-agents

To check the status:

svcs smawfa-agents

15.4 Transport Directory

More than one transport directory per pool:
Create the following directories manually under /usr/sap/<SID>/trans:

appnode # cd /usr/sap/<SID>/trans
appnode # mkdir EPS EPS/in EPS/log EPS/out bin buffer cofiles data etc \
log sapnames tmp
appnode # chown –R <sid>adm:sapsys *

SAP Central / Application Instance profile (<SID> of Primary Domain Controller):

● Change DIR_TRANS to /usr/sap/<SID>/trans
● Change DIR_EPS_ROOT to /usr/sap/<SID>/trans/EPS

Transport Management System:

● Change TRANSDIR to /usr/sap/<SID>/trans

15.5 Printing in FlexFrame 3.2

15.5.1 Possible Printing Architectures and Methods

This chapter describes various printing architectures, i.e. the different constellations of
hardware and software components with the corresponding access methods. Each
architecture also requires a specific print method, such as:
Frontend printing:
Print data are to be printed on the default printer of the user’s PC.

Installation Guide for SAP Solutions 149

SAP System Administration

Remote printing:
The spool server and the host spool system are on different hosts.
Local printing:
The spool server (application server with a spool work process) and host spool
system (operating system spooler) are on the same host.

15.5.2 Local Printing (Access Methods C and L)

Use local printing if the host spool system (operating system spooler) and the spool work
process of the SAP System are on the same host.
In FlexFrame 3.2 we suggest to use the printing methods remote or front-end printing. If
you are using local printing, keep in mind the following:
● You have to configure every printer on every server, because the SAP Instances can
run on several servers
● The network throughput is higher than with remote printing.
– The spool work process writes its data to the file system.
– An OS spooler process copies the file to another directory.
– This file will be read again and is sent to the printer
● Another impact is the fail-over situation. Normally, the OS spooler writes its data to
the root file system. Each Solaris Application Node has its own root file system. If
one Solaris Application Node aborts and the SAP instances are taken over to
another Application Node, accessing the spool data is not possible anymore.

15.5.3 Remote Printing (Access Methods S and U)

Use remote printing if you are printing over a network; that is, when the host spool system
(operating system spooler) and the spool work process of the SAP System are on
different hosts.

[Link] Architecture Prerequisites

The system prints remotely if the host spool system (operating system spooler) and the
spool server of the SAP System (application server with a spool work process) are on
different hosts. There has to be a network to transfer the data to the print server.
For performance reasons, we recommend using remote printing (production and mass
printing) only for LAN connections.
Remote printing requires reliable communication partners so that timeouts do not occur.

150 Installation Guide for SAP Solutions

 SAP System Administration

[Link] SAP System Prerequisites

To be able to address an output device from the SAP System in which you are working,
you have to define the output device in this SAP System. This is done using a device
definition.

When configuring the output device in a device definition, it is specified how the printer is
connected to the SAP System using the access method. The access method defines, for
example, whether you are using local or remote printing. The access method is identified
by a letter and informs the system which architecture is in use and which operating
system you are using. In this way, the system knows the way in which data is to be
transferred.

The system uses the following access methods for remote printing, depending on the
operating system that you are using:
Access Method U:
UNIX systems; Microsoft Windows systems (using a TCP/IP Print Server an SAPlpd)
Access Method S:
Microsoft Windows systems (using SAPlpd)

[Link] Description

With remote printing, the SAP spool work process sends the formatted data stream to the
output device over a network connection.

The options for the data transfer to the output device are listed below:

Transfer to a network printer

Network printers simulate their own host spool system. They can be directly connected to
the network with a network card and receive SAP output data.
Consider the storage capacity of the network printer and the size of the print requests.

Access method “U” Unix

Transfer using a UNIX destination host
The host spool system is on a host that uses UNIX as its operating system. The data is
forwarded to the Line Printer Daemon (lpd).

Access method “U” Windows

Transfer using a Microsoft Windows PC as the destination host

Installation Guide for SAP Solutions 151

SAP System Administration

The host spool system is on a host that uses Microsoft Windows as its operating system.
Depending on the access method, you can use SAPlpd from SAP or, for Microsoft
Windows 2000/2003, the TCP/IP Print Server of Microsoft Windows 2000/2003. SAPlpd
and TCP/IP Print Server accept the data stream and forward it to the host spool system.
Access Methods:
● S (proprietary SAP protocol) for use with SAPlpd
● U (UNIX Berkeley protocol) for use with the TCP/IP Print Server of Microsoft
Windows 2000/2003 and with SAPlpd

While data is simply forwarded with the access method U, the access method S has the
following attributes:
● Encrypted transfer, for example for HR data
● Compressed transfer

15.5.4 Front-end Printing on Local Printers

Normally, all printers on which you want to print from the SAP system must be created in
the SAP System as output devices. Front-end printing is available to reduce the
significant administration effort associated with this. This means that a user logged on to
the SAP System through the SAP GUI can use the printers that are set up at his or her
front-end PC.

You only need to create a single output device in the SAP System to be able to address
all Microsoft Windows default printers. If users specify this output device for their print
requests, the system calls their default printers.

Front-end printing is therefore especially useful in the following cases:

● Users want to print directly at their workstation, without having to create a specific
device definition in the SAP System. This is especially the case for users that often
work at different work stations or log on to the SAP System on a mobile basis, and
want to print at their current location.
● Dynamic IP addresses are used for the front-end. Unlike remote printing, you do not
require any fixed IP addresses for front-end printing.

152 Installation Guide for SAP Solutions

 BRBACKUP and SAPDBA/BRCONNECT

16 BRBACKUP and
SAPDBA/BRCONNECT
When brbackup is started for offline backup, it first stops the database with the
shutdown immediate command. As the FA Agent recognizes that the Oracle
processes are missing, it will, by default, restart the database. The brconnect will notice
that the database has been restarted, and the backup is aborted.
In order to avoid this situation, there are two solutions to make backup tools “FlexFrame-
aware”.

16.1 Solution 1 for Oracle and SAPDB/MaxDB

This solution uses the options nowatch and watch of the script sapdb to tell the FA
Agent that the database should not be monitored during the offline backup.

Requirements
● Current SAP Service scripts in /FlexFrame/scripts

Implementation
Before starting the offline backup, the script sapdb should be called as user root with
arguments:
sudo /FlexFrame/scripts/sabdb<SID>nowatch
When the backup is finished, the script sapdb should be called as user root with
arguments:
sudo /FlexFrame/scripts/sabdb<SID>watch
Calling script sapdb is also possible as <sid>adm or for Oracle as ora<sid> user,
but then it has to be called with absolute path name.

Installation Guide for SAP Solutions 153

BRBACKUP and SAPDBA/BRCONNECT

16.2 Solution 2 for Oracle

This solution uses the options nowatch and watch of the script sapdb to tell the FA
Agent that the database should not be monitored during the offline backup. The
difference to solution 1 is that the script sapdb is called indirectly from brbackup by
using the functionality meant for Oracle Fail Safe.

Requirements
● br-tools must be at least version 620 patch level 124
● Current SAP Service scripts in /FlexFrame/scripts
● group dba in LDAP must have ora<sid> as member of the group

Implementation
The following environment variables must set for <sid>adm and ora<sid> users:
BR_OFS=1
FSCMD_CMD=/FlexFrame/scripts/sapbrbackup
When the brbackup is started directly, called from SAPDBA or a DB13 transaction, it
calls the script sapbrbackup to shut down and start up the database, and the
sapbrbackup will take care of calling sapdb with the nowatch or watch option.

Known limitations
● works only with Oracle databases
● brbackup needs to be version 620 even if using 4.6X kernel

154 Installation Guide for SAP Solutions

 Troubleshooting

17 Troubleshooting
● Environment of <sid>adm and ora<sid> users:
In order to obtain corresponding environment variables for the instances in question,
the following files must be present in the home directory of each user:
.cshrc
.sapenv_ci<sid>.csh
.sapenv_ci<sid>.sh
.dbenv_ci<sid>.csh
.dbenv_ci<sid>.sh
.sapenv_db<sid>-[Link]
.sapenv_db<sid>-[Link]
.dbenv_db<sid>-[Link]
.dbenv_db<sid>-[Link]

● When an application server is started, the following error message is issued:

Central-Instance CB1 is not running, please start it first.
/FlexFrame/scripts/sapapp done
exit_code2

The log files under /FlexFrame/scripts/log are missing, as a result of which

the server does not know that a CI is already running.

Installation Guide for SAP Solutions 155

18 Abbreviations

ABAP Advanced Business Application Programming

ACC Adaptive Computing Controller
ACI Adaptive Computing Infrastructure
ACPI Advanced Configuration and Power Interface
APM Advanced Power Management
APOLC Advanced Planner & Optimizer Life Cache
CCU Console Connection Unit
CIFS Common Internet File System
DART Data Access in Real Time
DHCP Dynamic Host Configuration Protocol
DIT Domain Information Tree
ERP Enterprise Resource Planning
ESF Enhanced System Facility
EULA End User License Agreement
FAA FlexFrame Autonomous Agent
FC Fiber Channel
FTP File Transfer Protocol
IP Internet Protocol
LAN Local Area Network
LDAP Lightweight Directory Access Protocol
LUN Logical Unit Number
MAC Media Access Control
MINRA Minimal Read Ahead
NAS Network Attached Storage
NDMP Network Data Management Protocol
NFS Network File System

Installation Guide for SAP Solutions 157

 Abbreviations

NIC Network Interface Card

NVRAM Non-Volatile Random Access Memory
OBP Open Boot Prom
OLTP On-Line Transaction Processing
ONTAP Open Network Technology for Appliance Products
OSS Open Source Software
POST Power-On Self Test
PCL PRIMECLUSTER
PFS Production File System (on Celerra)
PW PRIMEPOWER
PXE Preboot Execution Environment
PY PRIMERGY
QA Quality Assurance
QS Quality of Service
RAID Redundant Array of Independent (or Inexpensive) Disks
RARP Reverse Address Resolution Protocol
RDBMS Relational Database Management System
RHEL Red Hat Enterprise Linux
RSB Remote Service Board
SCS System Console Software
SAP BW SAP Business Warehouse
SAPGUI SAP Graphical User Interface
SAPOSS SAP Online System Service
SID System Identifier
SLD System Landscape Directory
SLES SUSE Linux Enterprise Server
SMB Server Message Block
SMC System Management Console
SNMP Simple Network Management Protocol

158 Installation Guide for SAP Solutions

 Abbreviations

SPOC Single Point Of Control

TELNET Telecommunications Network
TFTP Trivial File Transfer Protocol
UDP User Datagram Protocol
UPS Uninterruptible Power Supply
VLAN Virtual Local Area Network
VTOC Virtual Table Of Contents
WAN Wide Area Network
WAS Web Application Server
WAFL Write Anywhere File Layout
XSCF Extended System Control Facility

Installation Guide for SAP Solutions 159

19 Glossary
Adaptive Computing Controller
SAP system for monitoring and controlling SAP environments.
Advanced Business Application Programming
Proprietary programming language of SAP.
Advanced Power Management
Advanced Power Management defines a layer between the hardware and the
operating system that effectively shields the programmer from hardware details.
Application Agent
A software program for monitoring and managing applications.
Application Node
A host for applications (e.g. SAP instances db, ci, agate, wgate, app etc.). This
definition includes Application Servers as well as Database Servers.
Automounter
The automounter is an NFS utility that automatically mounts directories on an NFS
client as they are needed, and unmounts them when they are no longer needed.
Autonomous Agent
Central system management and high availability software component of FlexFrame.
Blade
A special form factor for computer nodes.
BladeRunner
The working title for the solution part of SAP for FlexFrame.
BOOTPARAM
Boot time parameters of the kernel.
BRBACKUP
SAP backup and restore tools.
Celerra
NAS system of EMC.
Checkpoint Restore
On EMC Celerra a SnapSure feature that restores a PFS to a point in time using
checkpoint information. As a precaution, SnapSure automatically creates a new
checkpoint of the PFS before it performs the restore operation.
Client LAN
Virtual network segment within FlexFrame, used for client-server traffic.

Installation Guide for SAP Solutions 161

 Glossary

Common Internet File System

A protocol for the sharing of file systems (same as SMB).
Computing Node
From the SAP ACI perspective: A host that is used for applications.
Control Agent
A software program for monitoring and managing nodes within FlexFrame.
Control LAN
Virtual network segment within FlexFrame, used for system management traffic.
Control Node
A physical computer system, controlling and monitoring the entire FlexFrame
landscape and running shared services in the rack (dhcp, tftp, ldap etc.).
Control Station
A Control Node in an SAP ACI environment.
DART
Operating system of Celerra data movers (Data Access in Real Time).
Dynamic Host Configuration Protocol
DHCP is a protocol for assigning dynamic IP addresses to devices on a network.
Dynamic Host Configuration Protocol server
A DHCP server provides configuration parameters specific to the DHCP client host,
required by the host to participate on the Internet.
EMC NAS
Network attached storage for file systems of EMC.
Enterprise Resource Planning
Enterprise Resource Planning systems are management information systems that
integrate and automate many of the business practices associated with the
operations or production aspects of a company.
Ethernet
A Local Area Network which supports data transfer rates of 10 megabits per second.
Fiber Channel
Fiber Channel is a serial computer bus intended for connecting high-speed storage
devices to computers.
Filer
Network attached storage for file systems of NetApp.
FlexFrame
A joint project in which the main partners are SAP, Network Appliance, Intel and
Fujitsu Siemens Computers.

162 Installation Guide for SAP Solutions

 Glossary

FlexFrameTM for SAP®

FlexFrame TM for SAP® is a radically new architecture for SAP environments. It
exploits the latest business-critical computing technology to deliver major cost
savings for SAP customers.
FlexFrame internal LAN Switch
Cisco network switches which are integral part of the FlexFrame for SAP hardware
configuration and which are automatically configured by the FlexFrame for SAP
software.
Gigabit Ethernet
A Local Area Network which supports data transfer rates of 1 gigabit (1,000
megabits) per second.
Host name
The name of a node (assigned to an interface) that is resolved to a unique IP
address. One node can have multiple host names (cf. node name).
In SAP environments host names are currently limited to 13 alphanumeric characters
including the hyphen (“ - “). The first character must be a letter. In the SAP
environment host names are case-sensitive.
Image
In the FlexFrame documentation, “Image” is used as a synonym for “Hard Disk
Image”.
Internet Protocol Address
A unique number used by computers to refer to each other when sending information
through networks using the Internet Protocol.
Lightweight Directory Access Protocol
Protocol for accessing on-line directory services.
Local Area Network
A computer network that spans a relatively small area. Most LANs are confined to a
single building or group of buildings. However, one LAN can be connected to other
LANs over any distance via telephone lines and radio waves. A system of LANs
connected in this way is called a Wide Area Network (WAN).
Local host name
The name of the node (physical computer); it can be displayed and set using the
command /bin/hostname.
Logical Unit Number
An address for a single (SCSI) disk drive.
MAC address
Device identifier number of a Network Interface Card. In full: "media access control
address".

Installation Guide for SAP Solutions 163

 Glossary

MaxDB
A relational database system from mySQL (formerly ADABAS and SAPDB).
Media Access Control address
An identifier for network devices, usually unique. The MAC address is stored
physically on the device.
NAS system
Network Attached Storage of any vendor (in our context: EMC NAS or NetApp Filer).
NDMPcopy
NDMPcopy transfers data between Filers using the Network Data Management
Protocol (NDMP).
Netboot
A boot procedure for computers where the operating system is provided via a
network instead of local disks.
Netweaver
SAP NetWeaver is the technical foundation of SAP solutions.
Network Appliance Filer
See “Filer”.
Network Attached Storage
A data storage device that is connected via a network to one or multiple computers.
Network File System
A network protocol for network-based storage access.
Network Interface Card
A hardware device that allows computer communication via networks.
Node
A physical computer system controlled by an OS.
Node name
The name of a physical node as returned by the command uname -n. Each node
name within a FlexFrame environment must be unique.
Non-Volatile Random Access Memory
A type of memory that retains its contents when the power is turned off.
On-Line Transaction Processing
Transaction processing via computer networks.
OpenLDAP
An Open Source LDAP Service Implementation.
Open Network Technology for Appliance Products
The operating system of Network Appliance Filers.

164 Installation Guide for SAP Solutions

 Glossary

Open Source Software

Software that is distributed free of charge under an open source license, such as the
GNU Public License.
Oracle RAC
A cluster database by Oracle Corporation.
Physical host
Name of a physical computer system (node).
Power-On Self Test
Part of a computer's boot process; automatic testing of diverse hardware
components.
Preboot Execution Environment
An environment that allows a computer to boot from a network resource without
having a local operating system installed.
PRIMECLUSTER
Fujitsu Siemens Computer’s high-availability and clustering software.
PRIMEPOWER
Fujitsu Siemens Computer's SPARC-based server product line.
PRIMERGY
Fujitsu Siemens Computer's i386-based server product line.
Red Hat Enterprise Linux
Linux distribution by Red Hat, Inc., targeting business customers.
Reverse Address Resolution Protocol
A protocol allowing resolution of an IP address corresponding to a MAC address.
SAP Service
In FlexFrame: SAP Service and DB Services.
SAP service script
An administration script for starting and stopping an SAP application on a virtual host.
SAP Solution Manager
Service portal for the implementation, operation and optimization of an SAP solution.
SAPLogon
Front-end software for SAPGUI.
SAPRouter
Router for SAP services like SAPGUI or SAPTELNET.
SavVol
A Celerra volume to which SnapSure copies original point-in-time data blocks from
the PFS before the blocks are altered by a PFS transaction.

Installation Guide for SAP Solutions 165

 Glossary

Server
A physical host (hardware), same as node.
Service
A software program providing functions to clients.
Service type
The type of an application or service (db, ci, app, agate, wgate etc.).
Single Point of Control
In FlexFrame: One user interface to control a whole FlexFrame environment.
Storage LAN
A virtual LAN segment within a FlexFrame environment, carrying the traffic to NAS
systems.
SUSE Linux Enterprise Server
A Linux distribution by Novell, specializing in server installations.
Telecommunications Network
A terminal emulation program for TCP/IP networks such as the Internet.
Trivial File Transfer Protocol
A simple form of the File Transfer Protocol (FTP). TFTP uses the User Datagram
Protocol (UDP) and provides no security features. It is often used by servers to boot
diskless workstations, X-terminals, and routers.
TFTP server
A simple FTP implementation.
Virtual host
The name of the virtual host on which an application runs; it is assigned to a physical
node when an application is started.
Virtual Local Area Network
A VLAN is a logically segmented network mapped over physical hardware according
to the IEEE 802.1q standard.
Virtualization
Virtualization means the separation of hardware and processes. In a virtualized
environment (FlexFrame), a process can be moved between hardware nodes while
staying transparent to the user and application.

166 Installation Guide for SAP Solutions

20 Index
A installing Web AS 6.20 57
Application Nodes released 12 installing Web AS 6.20 with sapinst 57
B installing Web AS 6.40 with
NetWeaver04 SR1 65
BRBACKUP 153
IP addresses used in this document 3
C
M
configuring
MaxDB 45, 52, 153
interfaces 23
N
service status path server 22
notational conventions 2
configuring the virtual host name for
Web AS 6.40 ABAP and JAVA-AddIn O
/ WebAS 6.40 JAVA 117
online software service 13
configuring the virtual host name
ora<sid> 40, 46
manually 109
Oracle 52, 153, 154
D
ORACLE 40, 46
description of Web AS 6.40 JAVA 66
OSS network connection
document history 2
without dedicated saprouter
F
server 14
FA agents 17
overview 7
ff_scripts 40, 46
P
FlexFrame installation diagram 9
Post-SAP installation steps Web AS
G 6.40 application server JAVA-
AddIn 109
gathering SAP services information 8
preparations 8
H
pre-SAP installation steps 27
host names 25
profile parameters for 135
hot links for FlexFrame 4
profile parameters for the instance
I
profile 136
installation of Oracle 9.2 40
profile parameters for the start
installing SAP 4.6C SR2 51 profile 136

Installation Guide for SAP Solutions 167

Index

R Solaris 31
related documents 2 start script 134
related SAP notes 15 starting a configuration 20
RPM 36 stop script 134
S T
SAP installation steps 1 TNS listener for Oracle 37
SAP license 139 troubleshooting 155
SAP release upgrade 148 U
SAP service connection 13 upgrading application software 143
SAP service scripts 19 V
SAP start and stop mechanism virtualization of SAP services 7
(Release 4.6CSR2) 137
W
SAP system administration 143
Web AS 6.40 ABAP + JAVA-AddIn
SAPDB 52, 153 NetWeaver04SR1 78
SAPDBA 153 Web AS 6.40 application server JAVA-
AddIn 83
SAPLogon – SAPGUI 139
Web AS 6.40 NetWeaver04SR1 ABAP
SAPROUTER on the Control
Oracle 73
Node 142
Web AS 6.40 NetWeaver04SR1 JAVA
software administration 143
MaxDB/Oracle 67

168 Installation Guide for SAP Solutions

Information on this document
On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Compu-
ters. This new subsidiary of Fujitsu has been renamed Fujitsu Technology So-
lutions.
This document from the document archive refers to a product version which
was released a considerable time ago or which is no longer marketed.
Please note that all company references and copyrights in this document have
been legally transferred to Fujitsu Technology Solutions.
Contact and support addresses will now be offered by Fujitsu Technology So-
lutions and have the format …@[Link].
The Internet pages of Fujitsu Technology Solutions are available at
[Link]
and the user documentation at [Link]
Copyright Fujitsu Technology Solutions, 2009

Hinweise zum vorliegenden Dokument

Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von
Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seit-
dem den Namen Fujitsu Technology Solutions.
Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine
bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche
Produktversion.
Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden
Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.
Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions
angeboten und haben die Form …@[Link].
Die Internetseiten von Fujitsu Technology Solutions finden Sie unter
[Link] und unter [Link] finden Sie die
Benutzerdokumentation.
Copyright Fujitsu Technology Solutions, 2009