Ff4s Sap Install

Published on May 2016 | Categories: Documents | Downloads: 97 | Comments: 0 | Views: 1322
of 183
Download PDF   Embed   Report

sap install

Comments

Content


User Guide
FlexFrame™ for SAP® 4.1A
Installation Guide for SAP Solutions
English

FlexFrame™ for SAP
®

Version 4.1A
Installation Guide for SAP Solutions


Edition April 2008
Document Version 1.0



Fujitsu Siemens Computers GmbH

© Copyright Fujitsu Siemens Computers GmbH 2008
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.

Installation Guide for SAP Solutions
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
Contents
Installation Guide for SAP Solutions
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 “listener.ora” .................................................................................................... 38
8.1.3 Host Name Changes in "tnsnames.ora" .......................................................... 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 root.sh ................................................................................................... 42
8.3.2 Patch Installation ............................................................................................. 42
8.4 Installation of Oracle 10.2 (R2) ........................................................................ 43
8.5 Installation of SAPDB / MaxDB........................................................................ 43
8.5.1 XUSER............................................................................................................ 43
8.5.1.1 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
8.6 SAP Installation with Database DB2................................................................ 47
8.6.1 Software Requirements ................................................................................... 47
8.6.2 Pre-Installation Steps ...................................................................................... 48
8.6.3 Installing DB2 .................................................................................................. 48
8.6.4 Installing DB2 License..................................................................................... 49
8.6.5 LDAP-Plugin.................................................................................................... 50
8.6.6 Install SAP....................................................................................................... 50
8.6.7 Changes in System Files................................................................................. 51
8.6.8 Post Installation Steps ..................................................................................... 51
9 SAP in General ............................................................................................... 53
9.1 ASCS ABAP Central Service Instance in General ........................................... 53
9.2 SAP Java Cryptographic Toolkit ...................................................................... 53
9.2.1 Linux................................................................................................................ 53
9.2.2 Solaris ............................................................................................................. 54
10 Installing SAP 4.6C SR2................................................................................ 55
10.1 SAPDB / MaxDB / Oracle................................................................................ 56
11 Installing Web AS 6.20 .................................................................................. 61
11.1 Installating Web AS 6.20 with sapinst 642....................................................... 61
11.1.1 Installing the Central Instance (CI) .................................................................. 62
11.1.2 Installing the Database Instance (DB) ............................................................. 64
Contents
Installation Guide for SAP Solutions
12 Installing Web AS 6.40 with NetWeaver04 SR1........................................... 69
12.1 Description of Web AS 6.40 JAVA .................................................................. 70
12.2 Web AS 6.40 NetWeaver04SR1 JAVA MaxDB/Oracle ................................... 71
12.2.1 SCS................................................................................................................. 71
12.2.2 DB................................................................................................................... 75
12.2.3 JC.................................................................................................................... 76
12.2.4 J ...................................................................................................................... 76
12.2.5 Web AS 6.40 Deployment SP16 ..................................................................... 77
12.2.5.1 JC.................................................................................................................... 77
12.2.5.2 J ...................................................................................................................... 77
12.3 Web AS 6.40 NetWeaver04SR1 ABAP Oracle ............................................... 77
12.3.1 CI..................................................................................................................... 77
12.3.2 DB................................................................................................................... 81
12.3.3 APP................................................................................................................. 82
12.4 Web AS 6.40 ABAP + JAVA-AddIn NetWeaver04SR1 ................................... 82
12.4.1 CI..................................................................................................................... 82
12.4.2 DB................................................................................................................... 82
12.4.3 SCS................................................................................................................. 83
12.4.4 Web AS 6.40 Deployment SP16 ..................................................................... 87
12.4.4.1 DVEBMGS<id> (JAVA-AddIN) ........................................................................ 87
12.5 Web AS 6.40 Application Server JAVA-AddIn................................................. 87
13 Installing NetWeaver 7.0SR1/SR2 ................................................................ 89
13.1 Installation of SAP Solutions ........................................................................... 90
13.1.1 Prerequisite Checker (Linux) ........................................................................... 93
13.2 Sapinit File (Linux)........................................................................................... 94
13.3 installsapinit.sh – symlink (Linux) .................................................................... 95
13.4 Services File (Linux)........................................................................................ 96
13.5 NetWeaver 7.0SR1/SR2 and Oracle 10(R2) ................................................... 97
13.6 NetWeaver 7.0SR1/SR2 and MaxDB76.......................................................... 98
13.7 NetWeaver 7.0SR1/SR2 / MaxDB76 and SLES9_x86.................................... 99
13.8 NetWeaver 7.0SR1/SR2 MaxDB76 and Solaris9.......................................... 102
13.9 NetWeaver 7.0SR1/SR2 and EP................................................................... 102
13.10 NetWeaver 7.0SR1/SR2 ABAP+JAVA-AddIn ............................................... 104
13.11 NetWeaver 7.0SR1/SR2 JAVA only.............................................................. 109
13.12 LiveCache ..................................................................................................... 110
13.13 ERS – Enque Replicated Server ................................................................... 110
13.14 Installation of SAP Solutions – Post Phase................................................... 110
13.14.1 Linux.............................................................................................................. 110
13.14.2 Solaris ........................................................................................................... 111
13.14.3 Linux and Solaris........................................................................................... 111
13.14.4 Solaris 10 Preparations ................................................................................. 112
14 Post-SAP Installation Steps ....................................................................... 113
14.1 Configuring the Virtual Host Name Manually................................................. 113
Contents
Installation Guide for SAP Solutions
14.1.1 Central Instance (not valid for Web AS 6.40 J2EE) ....................................... 115
14.1.2 Database Instance (also valid for WebAS 6.40 J2EE)................................... 115
14.1.3 Application Instance (not valid for WebAS 6.40 J2EE) .................................. 116
14.1.4 SCS Instance................................................................................................. 117
14.1.5 ASCS Instance (WebAS 7.00)....................................................................... 119
14.1.6 NetWeaver 7.0 / NetWeaver 7.0SR1/SR2..................................................... 120
14.2 Configuring the Virtual Host Name for Web AS 6.40 ABAP and
JAVA-AddIn / WebAS 6.40 JAVA.................................................................. 121
14.3 Start Script startdb for Oracle and SAPDB/MaxDB ....................................... 138
14.4 Stop Script stopdb for Oracle and SAPDB/MaxDB........................................ 138
14.5 Scheduling of Batch Jobs (CCMS) ................................................................ 138
14.6 Profile Parameters for DEFAULT.PFL........................................................... 139
14.7 Profile Parameters for the Start Profile.......................................................... 140
14.8 Profile Parameters for the Instance Profile .................................................... 140
14.9 SAP Start and Stop Mechanism (Release 4.6CSR2) .................................... 141
14.10 SAP License.................................................................................................. 143
14.11 SAPLogon – SAPGUI .................................................................................... 143
14.12 SAPROUTER on the Control Node ............................................................... 146
15 SAP System Administration ....................................................................... 147
15.1 Upgrading Application Software .................................................................... 147
15.2 Software Administration................................................................................. 147
15.2.1 Starting and Stopping SAP Services ............................................................. 147
15.2.1.1 SAP Service Scripts ...................................................................................... 147
15.2.1.2 SAP Service Script Actions............................................................................ 149
15.2.1.3 Return Codes of the SAP Service Scripts ..................................................... 150
15.2.1.4 Joined SAP Service Scripts........................................................................... 150
15.2.2 Removing an Application from Monitoring by FA Agents............................... 151
15.2.3 Application Software...................................................................................... 151
15.3 SAP Release Upgrade .................................................................................. 152
15.3.1 Services Port ................................................................................................. 152
15.3.2 Group Sapinst................................................................................................ 152
15.3.3 FA-Agent ....................................................................................................... 153
15.4 Transport Directory........................................................................................ 153
15.5 Printing in FlexFrame .................................................................................... 153
15.5.1 Possible Printing Architectures and Methods ................................................ 153
15.5.2 Local Printing (Access Methods C and L)...................................................... 154
15.5.3 Remote Printing (Access Methods S and U) ................................................. 154
15.5.3.1 Architecture Prerequisites.............................................................................. 154
15.5.3.2 SAP System Prerequisites............................................................................. 155
15.5.3.3 Description..................................................................................................... 155
15.5.4 Front-end Printing on Local Printers.............................................................. 156


Contents
Installation Guide for SAP Solutions
16 BRBACKUP and SAPDBA/BRCONNECT................................................... 157
16.1 Solution 1 for Oracle and SAPDB/MaxDB..................................................... 157
16.2 Solution 2 for Oracle...................................................................................... 158
17 Troubleshooting .......................................................................................... 159
18 Abbreviations .............................................................................................. 161
19 Glossary ....................................................................................................... 165
20 Index............................................................................................................. 171

Installation Guide for SAP Solutions 1
1 Introduction
As we continue to improve the installation process, this document is permanently subject
to change.
The latest version can be found at
http://extranet.fujitsu-siemens.com/FlexFrame


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™ 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).
Introduction
2 Installation Guide for SAP Solutions
1.4 Notational Conventions
The following conventions are used in this manual:


Additional information that should be observed.

Warning that must be observed.
f i xed f ont Names of paths, files, commands, and system output.
<f i xed f ont > 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 2008-04-01

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
®
– myAMC.Messenger
FlexFrame™ for SAP
®
– Upgrading FlexFrame 3.2B or 4.0 to 4.1A
FlexFrame™ for SAP
®
– White Paper
PRIMECLUSTER Documentation
ServerView Documentation
SUSE Linux Enterprise Server Documentation
Solaris Documentation
Introduction
Installation Guide for SAP Solutions 3
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 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
No.
Client IP Server IP Storage IP Control IP (RSB) Heartbeat (PCL)
1 10.0.1.201 192.168.1.201 192.168.100.201 192.168.200.221 control1 192.168.200.201
2 10.0.2.201 192.168.2.201 192.168.101.201 192.168.200.221 control1
1 10.0.1.202 192.168.1.202 192.168.100.202 192.168.200.222 control2 192.168.200.202
2 10.0.2.202 192.168.2.202 192.168.101.202 192.168.200.222 control2
1 192.168.100.203 192.168.200.203 filer
2 192.168.101.203 192.168.200.203 filer
BX300-1
1 192.168.200.230 bx3001mg
mt

1 10.0.1.1 192.168.1.1 192.168.100.1 blade1
1 10.0.1.2 192.168.1.2 192.168.100.2 blade2
1 10.0.1.3 192.168.1.3 192.168.100.3 blade3
BX300-2
2 192.168.200.240 bx3002mg
mt

2 10.0.2.11 192.168.2.11 192.168.101.11 blade11
2 10.0.2.12 192.168.2.12 192.168.101.12 blade12
2 10.0.2.13 192.168.2.13 192.168.101.13 blade13
1 10.0.1.21 192.168.1.21 192.168.100.21 192.168.200.21 PW250_1
2 10.0.2.22 192.168.2.22 192.168.101.22 192.168.200.22 PW250_2
192.168.200.252 switch1
192.168.200.253 switch2
SAP
instance

1 10.0.1.101 192.168.1.101 cic11
Introduction
4 Installation Guide for SAP Solutions
Pool
No.
Client IP Server IP Storage IP Control IP (RSB) Heartbeat (PCL)
1 192.168.1.102 dbc11
1 10.0.1.103 192.168.1.103 app01c11
1 10.0.1.104 192.168.1.104 app02c11
1 10.0.1.105 192.168.1.105 app03c11
2 10.0.2.111 192.168.2.111 cibw1
2 192.168.2.112 dbbw1
2 10.0.2.113 192.168.2.113 app01bw1
2 10.0.2.114 192.168.2.114 app02bw1
1.8 Hotlinks for FlexFrame
PRIMECLUSTER™4
PRIMECLUSTER Wizards (downloads & documents)
http://extranet.fujitsu-siemens.com/My.htm
Primecluster RMS Home (information on the Reliant Monitor Services)
http://athen.mch.fsc.net/~kon/reliant.htm
PRIMECLUSTER
http://www.primecluster.com/

SAP on Linux
®
/ FlexFrame
SAP on Linux (released kernels, hardware and distributions for SAP)
http://www.sap.com/linux
SAP NetWeaver™ on Linux
http://www.sap.com/solutions/netweaver/
Official FlexFrame home page
http://www.fujitsu-siemens.com/flexframe
Information on FlexFrame for SAP
http://extranet.fujitsu-siemens.com/FlexFrame
PRIMERGY™ manuals
http://manuals.fujitsu-siemens.com/primergyservers.html

Introduction
Installation Guide for SAP Solutions 5
SAP on Solaris™ / FlexFrame
Global information and operating system manuals
Fujitsu Siemens Computers and SAP
http://manuals.fujitsu-siemens.com/unixservers.html
PRIMEPOWER™ manuals
http://manuals.fujitsu-siemens.com/unixservers.html

Knowledge
SNMP protocol information
http://www2.rad.com/networks/1995/snmp/snmp.htm
Linux Knowledge Portal
http://www.linux-knowledge-portal.org/de/index.php
Official Linux documentation project
http://www.tldp.org/
Official PRIMERGY documentation
http://manuals.fujitsu-siemens.com/serverbooks/start.htm
Internal information on PRIMERGY servers
http://extranet.fujitsu-siemens.com/products/primergy

Software
GNU Homepage
http://www.gnu.org/
Software by Fujitsu Siemens Computers
http://support.fujitsu-siemens.de/de/support/downloads.html
Open SSH website
http://www.openssh.org/
SSH download
http://www.ssh.com/

Installation Guide for SAP Solutions 7
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.
Overview
8 Installation Guide for SAP Solutions
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 FFPLAN. XLS). 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 Ser vi ces 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 SI D 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)
Overview
Installation Guide for SAP Solutions 9
● 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 f f _*. conf can be created by pressing the button labeled
Gener at e conf i gur at i on f i l es. 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 FFPLAN32.XLS spreadsheet.
The configuration file f f _ser vi ces. 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”.
Overview
10 Installation Guide for SAP Solutions

FlexFrame Instal lation Steps
2.10.2
Excel
FlexFrame
Planning Tool
FF Pr ep
CD
ff_wiring.pl
ff_switch_conf.pl
Cabli ng
Pl an
Network
Cabli ng
Hardware
Install ation
DVD
CN
Control Node 1
External
Medium:
Configuration
files; Patches
ff_wiring.pl
Switches
2.10.1
2.6.3
2.2
2.3
2.4
2.5
2.6
2.9
OS
Install ation
Control
Node
Swi tch
Confi -
gurati on
Configurati on Fi l es:
ff_cn.conf
ff_an.conf
ff_misc.conf
ff_services.conf
Manual
Setup
Control Node
LDAP
and SSH
Confi -
gurati on
Preparati ons
HW
Install ation
Control Node 1
ff_filer_qtree_create.sh
ff_slapd_init.sh
NAS
system
Fil er QTrees;
LDAP
Ini ti al ization
Boot from
DVD
Serial cable
ff_setup_cn.sh
ff_apply_settings_cn.sh
Serial cable
Enter
MAC adresses
ff_get_an_mac.pl ff_an_mac.conf
ff_ldap_conf.pl
ff_cn.conf;
ff_an.conf;
ff_services.conf;
ff_an_mac.conf
2.8
MAC
Addresses
Generates Scripts:
ff_slapd_init.sh
ff_filer_qtree_create.sh
NAS Confi -
gurati on
ff_cn.conf;
ff_an.conf;
ff_services.conf;
ff_an_mac.conf
The steps are
numbered according
to the sections in the
quick installation chapter
2.10.4
PRIME-
CLUSTER
Configurati on
Control Node
Commands:
cftool -n
sdtool -s
hvdisp -a
DVD
CN
Control Node 2
Boot from DVD
OS Instal l ati on 2nd
Control Node, see 2.4
NAS
system
Ser vi c e
CN
Overview
Installation Guide for SAP Solutions 11

Proceed with SAP Installation
ff_cn.conf
ff_an.conf
ff_an_mac.conf
ff_create_an_cfg.pl
netboot.cfg
LDAP Configuration Files
in /FlexFrame/volFF/FlexFrame/ldap/etc/
pools/<Pool Name>/ ;
/opt/FlexFrame/bin/ff_linux_ldap_client.sh
/tftpboot/config/netboot_<Poolname>_<Nodename>.cfg
ff_new_an.sh
Customi zed
Boot Image
ff_new_an.sh
Customi zed
Boot Image
/FlexFrame/volFF/
FlexFrame/ldap/
etc/pools/<Pool Name>/
solaris_ldap_client.sh
2.11.4
2.11.5
2.11.6
Appl ication Node Configuration
Setup Linux
Appli cati on
Nodes
Setup Sol ari s
Appli cati on
Nodes
2.11
Generati on of
netboot
confi g fil es
2.13
DVD AN
Li nux
DVD AN
Sol ar i s
Preparati on
for Sol ari s
Appli cati on
Nodes
2.11.3
2.11.2
Preparati on
for Linux
Appli cati on
Nodes
nb_unpack_bi
NAS
system
ff_install_an_linux_images.sh
/tftpboot/config/netboot_
<Poolname>_<Nodename>.cfg
NAS
system
NAS
system
NAS
system
NAS
system
Overview
12 Installation Guide for SAP Solutions
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: http://www.sap.com/solutions/netweaver/linux/platforms/fsc.asp
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:
http://extranet.fujitsu-siemens.com/flexframe



Installation Guide for SAP Solutions 13
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 sapr out er process:
Customer
SAP
Walldorf
Tokio
Foster City
SAPROUTER
TELNET
SAPGUI
Control Node 1
Control Node 2
Application Node 1
Gateway
Application Node 2
Application Node ...
Application Node n
TELNET
SSH
TELNET
SSH
SAPGUI
SSH
SAPGUI
SSH
SAPGUI
SSH
SAPGUI
SSH
TELNET
SAPGUI
Customer
SAP
Walldorf
Tokio
Foster City
SAPROUTER
TELNET
SAPGUI
Control Node 1
Control Node 2
Application Node 1
Gateway
Application Node 2
Application Node ...
Application Node n
TELNET
SSH
TELNET
SSH
SAPGUI
SSH
SAPGUI
SSH
SAPGUI
SSH
SAPGUI
SSH
TELNET
SAPGUI



Please enter the server SAPROUTER as Ext er nal Connect i vi t y in the FF
Planning tool to get a reservation of an IP address for the first pool.

SAP Service Connection
14 Installation Guide for SAP Solutions
3.2 OSS Network Connection without Dedicated
saprouter Server
The sapr out er 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 146).
In this case, a virtual IP address for the Client LAN has to be defined for the sapr out er
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
Ext er nal Connect i vi t y tab, select Add New, enter the pool name and Ot her as
selected type. Afterwards enter Sapr out er as comment and a valid host number. The
host name for the first pool is predefined as sapr out er I NT and has to be used (check
entry in / usr / opt / r el i ant / et c/ hvi pal i as).
To allow PRIMECLUSTER to control of the sapr out er service, it is necessary to get the
latest version of sapr out er from SAP (Service Marketplace) and to install it in the
directory / Fl exFr ame/ vol FF/ Fl exFr ame/ sapr out er on the active Control Node.
This directory must have been created, the sapr out er program must be copied to it and
the sapr out t ab 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 sapr out t ab file if there are
multiple pools!
SAP Service Connection
Installation Guide for SAP Solutions 15
Customer
SAP
Walldorf
Tokio
Foster City
TELNET
SAPGUI
Control Node 1
(saprouter)
Control Node 2
(saprouter)
Application Node 1
Gateway
Application Node 2
Application Node ...
Application Node n
SAPGUI
SSH
SAPGUI
SSH
SAPGUI
SSH
SAPGUI
SSH
TELNET
SAPGUI
Customer
SAP
Walldorf
Tokio
Foster City
TELNET
SAPGUI
Control Node 1
(saprouter)
Control Node 2
(saprouter)
Application Node 1
Gateway
Application Node 2
Application Node ...
Application Node n
SAPGUI
SSH
SAPGUI
SSH
SAPGUI
SSH
SAPGUI
SSH
TELNET
SAPGUI

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 17
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_Ct r l Agent )
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 19
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 / Fl exFr ame/ scr i pt s.

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)
saper s Enqueue Replicated Server
sapj J2EE Application server
sapj c J2EE Central Instance
sapl c LiveCache
sapscs Java central services instance
sapser vi ce_conf i g Global customer-specific parameters
sapser vi ce_f unct i ons Global parameters and functions
st ar t _al l _sapser vi ces Initial start of all configured applications
st op_al l _sapser vi ces Stops all running applications
st op_al l _sapser vi ces_l ocal Stops all running applications on the local node
st op_al l _sapser vi ces_SI D Stops all running applications of one SID
SAP Service Scripts for Virtualizing Applications
20 Installation Guide for SAP Solutions
5.1 Starting a Configuration
The st ar t _al l _sapser vi ces 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:
#! / bi n/ bash
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

# Rul e i s:
# Al l sapser vi ces i n one ' eval ' must st ar t one af t er anot her ,
# each ' eval ' may st ar t si mul t aneous.

# C11
eval "
ssh bl ade1 sapdb C11 st ar t
ssh bl ade1 sapci C11 st ar t
ssh bl ade2 sapapp 01 C11 st ar t
ssh bl ade3 sapapp 02 C11 st ar t
" &

# BW1
eval "
ssh PW250- 1 sapdb BW1 st ar t
ssh PW250- 1 sapci BW1 st ar t
" &

#echo ""
#echo "Al l ser vi ces shoul d be up now. "
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


The start sequence within a system ID must always be observed:
ABAP
ABAP +
ASCS
ABAP +
JAVA-AddIn
JAVA
ABAP + ASCS +
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.

SAP Service Scripts for Virtualizing Applications
Installation Guide for SAP Solutions 21
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.

SAP Service Scripts for Virtualizing Applications
22 Installation Guide for SAP Solutions
5.2 Configuring the Service Status Path
The SERVI CE_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 : <ser vi ce_t ype>_<si d>_host
For the service type app: app_<i d>_<si d>_host
Explanation: i d Consecutive two-digit number from 00-97
si d 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 j c: <ser vi ce_t ype>_<si d>_host
For the service type j: j _<i d>_<si d>_host
Explanation: i d Consecutive two-digit number from 00-97
si d 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 j c: <ser vi ce_t ype>_<si d>_host
For the service type j: j _<i d>_<si d>_host
Explanation: i d Consecutive two-digit number from 00-97
si d 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: saper s_<i d>_<si d>_host
Explanation: i d Consecutive two-digit number from 00-97
si d The lower-case three-digit system ID
SAP Service Scripts for Virtualizing Applications
Installation Guide for SAP Solutions 23
WebAS 7.0 with ABAP and MaxDB (Li veCache)
There is a additional service type which supports LiveCache.
Service type: l c_<si d>_host
Explanation: si d 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 sapser vi ce_conf i g include script shows the
connection between the LAN type, interface and netmask:
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# Net mask
#
#NETMASK_CLI ENT=”255. 255. 240. 0 l s3195: 255. 255. 255. 0”
NETMASK_CLI ENT=”255. 255. 255. 0”
NETMASK_SERVER=”255. 255. 255. 0”
#
# I nt er f ace
#
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# SunOS l i nk aggr egat i on
# ~~~~~~~~~~~~~~~~~~~~~~~
#
# r eal i nt er f aces l ook l i ke t hi s:
# f j gi 2005000 # t hi s i s t he f i r st i nt er f ace
# f j gi 2005001 # t hi s i s t he second i nt er f ace
# f j gi 2005000: 1 # t hi s i ndi cat es t hat t he f i r st i nt er f ace
# # i s act i ve
# f j gi 2005001: 1 # t hi s i ndi cat es t hat t he second i nt er f ace
# # i s act i ve
#
# These i nt er f ace names consi st of t hr ee par t s:
# f j gi 2005001: 1
# ^^^- - - - - - - - - - - i nt er f ace number
# ^^^^- - - - - - - - - - - - - - vl an
# ^^^^- - - - - - - - - - - - - - - - - - 1GB- model
#
# For our net wor k t o i nt er f ace r el at i on we use onl y t he f i r st t wo
# par t s of t he i nt er f ace names, t he model and t he vl an. I n our
# exampl e:
SAP Service Scripts for Virtualizing Applications
24 Installation Guide for SAP Solutions
# f j gi 2005
#
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#
# Recommendat i ons:
#
# f or a cl ean l i nux envi r onment wi t hout net wor k r edundancy,
# Fl exFr ame <= 3. 0. x
# ETH_CLI ENT= »et h0 l s3191 : et h1 l s3192 : et h1 l s3195 : et h1 »
# ETH_SERVER=“et h1 l s3191: et h0 l s3192: et h0 l s3195: et h0“
#
# f or a cl ean l i nux envi r onment wi t h net wor k r edundancy,
# Fl exFr ame >= 3. 1
# ETH_CLI ENT=”vl an2001”
# ETH_SERVER=”vl an2005”
#
# f or a cl ean sol ar i s envi r onment wi t h net wor k r edundancy,
# Fl exFr ame >= 3. 1
# ETH_CLI ENT=”f j gi 2001”
# ETH_SERVER=”f j gi 2005”
#
# f or a mi xed envi r onment wi t hout net wor k r edundancy,
# cust omer speci f i c
# ETH_CLI ENT=”et h0 bel ana: hme0 bel ana2: hme0”
# ETH_SERVER=”et h1 bel ana: hme1 bel ana2: hme1”
#
# f or a mi xed envi r onment wi t h net wor k r edundancy,
# Fl exFr ame >= 3. 1
# ETH_CLI ENT=”vl an2001 Baby_1: f j gi 2001 Baby_2: f j gi 2001
# kl i nge1: vl an2002”
# ETH_SERVER=”vl an2005 Baby_1: f j gi 2005 Baby_2: f j gi 2005
# kl i nge1: vl an2006”
#
# I n a Fl exFr ame >=3. 1 envi r onment wi t h mor e t han one pool ,
# we can have mor e t han one conf i gur at i on f i l e, l i nked i nt o an
# pool - i mage. Thi s avoi d t o def i ne t o much speci al s.
The LAN types Ser ver and Cl i ent 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 ser ver LAN; all of the subsequent elements are optional and describe a deviation
from this type.
SAP Service Scripts for Virtualizing Applications
Installation Guide for SAP Solutions 25
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<si d>- se
ci <si d>- se ci <si d>
ascs<si d>- se ascs<si d>
app<i d><si d>- se app<i d><si d>
scs<si d>- se scs<si d>
j c<si d>- se j c<si d>
j <i d><si d>- se j <i d><si d>
Explanation: i d Consecutive two-digit number 00-97
si d 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 27
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
SAPI NST_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 / Fl exFr ame/ vol FF/ Fl exFr ame/ st age/ SAP_SW/ <SAP- CD-
name>). The whole directory or each subdirectory has to be exported on the Filer with the
necessary r o or r woptions 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 f f _si d_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.
Pre-SAP Installation Steps
28 Installation Guide for SAP Solutions
cont r ol 1#ff_setup_sid_folder.sh <pool_name> <SID>
Check the folder structure as described in the SAP installation guide.
You may use ssh –X ser ver for the Sapinst GUI. $DI SPLAY should also be adequate,
like l ocal host : 10. 0.
The X connection can be tested with xcl ock.
RX600- 01: ~#xclock
An XCLOCK should pop up on your display. If not, check the DI SPLAY variable or
the. Xaut hor i t y file.
Check the JAVA JDK:
ser ver : ~ #java -version
j ava ver si on "1. 4. 2_11"
J ava( TM) 2 Runt i me Envi r onment , St andar d Edi t i on ( bui l d 1. 4. 2_11- b04)
J ava Hot Spot ( TM) Cl i ent VM( bui l d 1. 4. 2_11- b04, mi xed mode)
Check the JAVA environment on Linux:
ser ver : ~ #echo $JAVA_HOME
/ usr / j ava/ <j dk>
Set the JAVA environment on Solaris:
ser ver : ~ #echo $JAVA_HOME
ser ver : ~ #JAVA_HOME=/usr/j2sdk/<sdk_version_dir>
Create the SAP installation directory:
ser ver : / #mkdir /usr/sap/<SID>/install
ser ver : / #chmod 777 /usr/sap/<SID>/install
ser ver : / #cd /usr/sap/<SID>/install
Setup the following variables, before starting the installation:
ser ver : / #export JAVA_HOME=/usr/java/<jdk>
ser ver : / #export SAPINST_JRE_HOME=/usr/java/<jdk>
ser ver : / #export TMP=<INSTALL_DIR>
Pre-SAP Installation Steps
Installation Guide for SAP Solutions 29
How to configure the interfaces manually:
Solaris (client LAN: 10.1.7.106 server LAN: 20.1.7.106):
ser ver : / #ifconfig fjgi2001:2 plumb 10.1.7.106 netmask 0xffffff00
broadcast 10.1.7.255 up
ser ver : / #ifconfig fjgi2002:2 plumb 20.1.7.106 netmask 0xffffff00
broadcast 20.1.7.255 up
Linux (client LAN: 10.1.7.101 server LAN: 20.1.7.106):
ser ver : / #/sbin/ifconfig vlan2001:0 10.1.7.101 broadcast 10.1.7.255
netmask 0xffffff00
ser ver : / #/sbin/ifconfig vlan2002:0 20.1.7.101 broadcast 20.1.7.255
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 f f _san_mount . sh pr e sapdb SI D st ar t 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/ <SI D>/ sapdat a<n>for data volumes and / sapdb/ <SI D>/ sapl og<n>
for log volumes.
The access rights have to be set to the database user and database group.



Installation Guide for SAP Solutions 31
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 j st ar t up/ j vm/ home=<val ue>.
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 _j 2sdk 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/ bi n/ nb_get _j 2sdk.
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 _j 2sdk 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 / j 2sdk/ <sdk_ver si on_di r >directory (e.g. / usr / j 2sdk/ j 2sdk1. 4. 2_10) or
/ usr / j 2sdk/ <sdk_ver si on_di r >_j ce (e.g. / usr / j 2sdk/ j 2sdk1. 4. 2_10_j ce) -
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 J AVA_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.
Operating System in General
32 Installation Guide for SAP Solutions
1. The current J2SE SDK is loaded from
ht t p: / / j ava. sun. com/ j 2se/ 1. 4. 2/ downl oad. ht ml
or an older version of the SDK is loaded from
ht t p: / / j ava. sun. com/ pr oduct s/ ar chi ve/ i ndex. ht ml
The following files should always be fetched here:
● Solaris SPARC Platform: 32-bit self-extracting file and
● 64-bit self-extracting file

Example: j 2sdk- 1_4_2_11- sol ar i s- spar c. sh
j 2sdk- 1_4_2_11- sol ar i s- spar cv9. sh
If JCE should be installed too, the matching J ava Cr ypt ogr aphy Ext ensi on zip
file must be loaded from ht t p: / / j ava. sun. com/ j 2se/ 1. 4. 2/ downl oad. ht ml
Section Ot her Downl oads 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 _j 2sdk - s <SDK_ar chi ve_f i l e> - a <app_node> - i <i mage> - p
- s <SDK_ar chi ve_f i l e>
Complete path name of one of the two SUN Java SDK Solaris SPARC Platform
self-extracting files on the Control Node
(e.g. / t mp/ j 2sdk- 1_4_2_11- sol ar i s- spar cv9. sh)
- 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 <i mage>
Complete path name of the Boot Image in which the SUN Java SDK version is
to be stored in the / usr part, (e.g. / Fl exFr ame/ vol FF/ os/ Sol ar i s/
FSC_5. 8_202_20050211/ bi _FJ SV, GPUZC- M_PW- P)
- p requests the unpacking of the JCE package. The installation directory is
named / usr / j 2sdk/ <sdk_ver si on_di r >_j ce.
Operating System in General
Installation Guide for SAP Solutions 33
Files:
The script generates or modifies the / usr / j 2sdk/ <sdk_ver si on_di r >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 j avahome pattern from the archive and is designated as
<sdk_ver si on_di r >in this text.
● Check of the call parameter - a and its argument (Application Node)
– pi ng 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
/ et c/ boot par ams. The SDK archive is later unpacked into this root file
system under / J DK_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 j 2sdk 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 / J DK_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 j r e/ l i b/ secur i t y.
Operating System in General
34 Installation Guide for SAP Solutions
The original files in this directory will be saved by moving to <f i l e>_or i g. The
new files from the JCE archive will be copied to <f i l e>_j ce 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 / J DK_PACK/ <sdk_ver si on_di r > resp.
j 2sdk/ <sdk_ver si on_di r >_j ce (if JCE was installed too) directory which was
generated during unpacking is moved to j 2sdk/ <sdk_ver si on_di r >in the / usr
part of the Boot Image selected.
● Finally, a cleanup takes place on the Application Node that, among other things,
deletes the / J DK_PACK directory .
7.2 Linux

In case the startup of the l snr ct l should fail during the SAP installation on
Oracle, please check section “listener.ora” 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. (www.sap.com/linux/platforms)
Errors while executing shell scripts
The execution of shell scripts starting with ‘: ’ (instead of #! / bi n/ 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:
cont r ol 1#cd /FlexFrame/volFF/os/Linux/FSC_3.2/root_img
appnode1#mkdir /oracle/ora-config/ORCLfmap
Operating System in General
Installation Guide for SAP Solutions 35
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
ht t p: / / j ava. sun. com/ j 2se/ 1. 4. 2/ downl oad. ht ml
An older version of the SDK can be found at
ht t p: / / j ava. sun. com/ pr oduct s/ ar chi ve/ i ndex. ht ml

Example for an Application Node (IP address 172.16.2.19):
i nst al l <*SDK*>. r pm
Mount r oot f s as r w:
Export the root image as r wfor only the maintenance Application Node:
cont r ol 1: / Fl exFr ame/ <f i l er - name>/ vol 0/ et c # vi exports

> / vol / vol FF/ os/ <OS>/ <FF- Rel ease>/ r oot _i mg
> - r o=172. 16. 1. 0/ 24: 172. 16. 2. 0/ 24, anon=0, r w=172. 16. 2. 19

cont r ol 1: ~#rsh filer1_qa exportfs -a
Do not forget to export the root image as r o after the maintenance!
RX300- 01: / #remount rw /
Operating System in General
36 Installation Guide for SAP Solutions
Make sure that the RPM does not contain files for the var image!
RX300- 01: / #rpm -qilp <*SDK*>.rpm | less

> sear ch f or "/ var "

i nst al l t he RPM:
RX300- 01: / #rpm -i <*SDK*>.rpm

r emount t he r oot f i l e syst emr ead onl y:
RX300- 01: / #remount ro /

cont r ol 1: / Fl exFr ame/ <f i l er - name>/ vol 0/ et c # vi exports
modi f y t he ent r y cont ai ni ng t he l i ne:
AN 172. 16. 2. 19 "r w":
#/ vol / vol FF/ os/ <OS>/ <FF- Rel ease>/ r oot _i mg-
r o=172. 16. 1. 0/ 24: 172. 16. 2. 0/ 24, anon=0, r w=172. 16. 2. 19

/ vol / vol FF/ os/ <OS>/ <FF- Rel ease>/ r oot _i mg - r o=172. 16. 1. 0
/ 24: 172. 16. 2. 0/ 24, anon=0
cont r ol 1: ~#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:
ht t ps: / / www14. sof t war e. i bm. com/ webapp/ i wm/ web/ pr eLogi n. do?sour ce=j
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.

Installation Guide for SAP Solutions 37
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. nol ock:
ORA- 01102: cannot mount t he dat abase i n EXCLUSI VE mode
On Solaris it has to be l l ock 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 ( i ni t <SI D>. or a / spf i l e<SI D>. or a) :

di sk_asynch_i o=FALSE
f i l esyst emi o_opt i ons=di r ect i o


Before starting the Oracle RUNI NSTALLER (r unI nst al l er for patches or
opatch for interim patches) please check the value of the environment variable
ORACLE_BASE=/ or acl e/ <SI D>o for the or a<si d>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 l i st ener task (start and stop) is performed
automatically by the FlexFrame sapdb script .
Each TNS listener can have its own listener name. In the / Fl exFr ame/ scr i pt s/
or a_l i st ener _names configuration file, an individual listener name can be assigned to
each <si d>. If the entry for an <si d>is omitted, the standard listener name LI STENER
is valid. Example for / Fl exFr ame/ scr i pt s/ or a_l i st ener _names:
#<si d>: <l i st ener name>
C11: MY_LI STENER
C12: YOUR_THI NG
P10: LI STENER_P10
P12: P12
Database in General
38 Installation Guide for SAP Solutions
Technical background
This configuration file for the SAP Service start and stop scripts is
/ Fl exFr ame/ scr i pt s/ 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 l i st ener . or a, too.


Oracle 10 only
LSNRCTL:
Check if the correct host name is used in the following files:
/ or acl e/ <SI D>/ 10[ 1- 2] _64/ net wor k/ admi n/ l snr ct l . or a
/ or acl e/ <SI D>/ 10[ 1- 2] _64/ net wor k/ admi n/ t nsnames. or a
/ sapmnt / <SI D>/ pr of i l e/ or acl e/ t nsnames. or a
8.1.2 “ listener.ora”

Every database instance must have its own l i st ener . or a.
The relevant parameter is HOST in the section LI STENER.


The example below is valid for Solaris only. On a Linux platform the IP
address of db<si d>- se has to be entered. This also applies for
t nsnames. or a.
Otherwise the startup of the l snr ct l will fail with Segment at i on er r or .
Example for a virtual DB host:
LI STENER =
( ADDRESS_LI ST =
. .
. .
( ADDRESS =
( COMMUNI TY =SAP. WORLD)
( PROTOCOL =TCP)
( HOST = db<si d>- se) # Vi r t ual host of t he l i st ener
( PORT = 1527)
)
)
Database in General
Installation Guide for SAP Solutions 39
Example for the ADDRESS_LI ST section:
LI STENER =
( ADDRESS_LI ST =

( ADDRESS=
( PROTOCOL=I PC)
( KEY=<SI D>. WORLD)
)
( ADDRESS=
( PROTOCOL=I PC)
( KEY=<SI D>)
)
Example for the SI D_LI ST section:
( SI D_LI ST =

( SI D_DESC =
( SDU =32768)
( SI D_NAME = <SI D>)
( ORACLE_HOME = / or acl e/ <si d>/ <or acl e_r el ease>_<32/ 64>)
#Must be avai l abl e per aut omount
)

8.1.3 Host Name Changes in " tnsnames.ora"

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<si d>- se has to be entered. Otherwise the startup of the lsnrctl
will fail with Segment at i on er r or .
Database in General
40 Installation Guide for SAP Solutions
Example:
<SI D>. WORLD=
( DESCRI PTI ON =
( SDU =32768)
( ADDRESS_LI ST =
( ADDRESS =
( COMMUNI TY =SAP. WORLD)
( PROTOCOL =TCP)
( HOST = db<si d>- se) # Vi r t ual host of t he dat abase
( PORT = 1527)
)
)
( CONNECT_DATA =
( si d = <SI D>)
( GLOBAL_NAME =<SI D>. WORLD)
)
)

8.2 Installation of Oracle 9.2

During the Oracle DB installation, a password for ora<si d>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 9.2.0.7:
Check the existence of the following directory:
/ or acl e/ or a- conf i g/ ORCLf map


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 / or acl e/ <SI D>/ 920_<32/ 64>(Linux) or
/ or acl e/ <SI D>/ 920_64 (Solaris) and / or acl e/ cl i ent . All directories will be
configured automatically with LDAP. They are also part of the / et c/ aut o. mast er file.
Start installation as described in the SAP installation manual.
Database in General
Installation Guide for SAP Solutions 41
8.2.1 Post-Oracle 9.2 Installation Steps

After installation, execute r oot . sh and use the parameter / or acl e/ <SI D>
instead of the default value (/ usr / l ocal / bi n).

BLADE1: / or acl e/ C11/ 920_<32/ 64># ./root.sh
Runni ng Or acl e9 r oot . sh scr i pt . . .
The f ol l owi ng envi r onment var i abl es ar e set as:
ORACLE_OWNER= or aC11
ORACLE_HOME= / or acl e/ C11/ 920_<32/ 64>

Ent er t he f ul l pat hname of t he l ocal bi n di r ect or y: [ / usr / l ocal / bi n] :
/oracle/C11
Copyi ng dbhome t o / or acl e/ C11 . . .
Copyi ng or aenv t o / or acl e/ C11 . . .
Copyi ng cor aenv t o / or acl e/ C11 . . .

Addi ng ent r y t o / et c/ or at ab f i l e. . .
Ent r i es wi l l be added t o t he / et c/ or at ab f i l e as needed by
Dat abase Conf i gur at i on Assi st ant when a dat abase i s cr eat ed
Fi ni shed r unni ng gener i c par t of r oot . sh scr i pt .
Now pr oduct - speci f i c r oot act i ons wi l l be per f or med.

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:
/ or acl e/ or a- conf i g/ or acl e


LSNRCTL:
Check if the correct host name is used in the following files:
/ or acl e/ <SI D>/ 101_<32/ 64>/ net wor k/ admi n/ l snr ct l . or a
/ or acl e/ <SI D>/ 101_<32/ 64>/ net wor k/ admi n/ t nsnames. or a
/ sapmnt / <SI D>/ pr of i l e/ or acl e/ t nsnames. or a

Database in General
42 Installation Guide for SAP Solutions
8.3.1 Script root.sh

After installation, execute r oot . sh and use the parameter / or acl e/ <SI D>
instead of the default value (/ usr / l ocal / bi n).

Example: SID=OLP
BLADE1: / or acl e/ OLP/ 101_64 # ./root.sh
Runni ng Or acl e10 r oot . sh scr i pt . . .
The f ol l owi ng envi r onment var i abl es ar e set as:
ORACLE_OWNER= or aol p
ORACLE_HOME= / or acl e/ OLP/ 101_64

Ent er t he f ul l pat hname of t he l ocal bi n di r ect or y: [ / usr / bi n] :
/oracle/OLP
Copyi ng dbhome t o / or acl e/ OLP . . .
Copyi ng or aenv t o / or acl e/ OLP . . .
Copyi ng cor aenv t o / or acl e/ OLP . . .
Addi ng ent r y t o / et c/ or at ab f i l e. . .
Ent r i es wi l l be added t o t he / et c/ or at ab f i l e as needed by
Dat abase Conf i gur at i on Assi st ant when a dat abase i s cr eat ed
Fi ni shed r unni ng gener i c par t of r oot . sh scr i pt .
Now pr oduct - speci f i c r oot act i ons wi l l be per f or med.
Successf ul l y accumul at ed necessar y OCR keys.
Cr eat i ng OCR keys f or user ' r oot ' , pr i vgr p ' r oot ' . .
Oper at i on successf ul .
Or acl e Cl ust er Regi st r y f or cl ust er has been i ni t i al i zed

/ bi n/ cp: cannot cr eat e r egul ar f i l e `/ et c/ i ni t . d/ i ni t . cssd' : Read- onl y
f i l e syst em
/ bi n/ l n: cr eat i ng symbol i c l i nk `/ et c/ r c. d/ r c2. d/ S96i ni t . cssd' t o
`/ et c/ i ni t . d/ i ni t . cssd' : Read- onl y f i l e syst em
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 / or acl e/ <SI D>. However
you will not receive such an error message.

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).
Database in General
Installation Guide for SAP Solutions 43
8.4 Installation of Oracle 10.2 (R2)

After installation, execute root.sh 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:
/ or acl e/ <SI D>/ 102_<32/ 64>/ net wor k/ admi n/ l snr ct l . or a
/ or acl e/ <SI D>/ 102_<32/ 64>/ net wor k/ admi n/ t nsnames. or a
/ sapmnt / <SI D>/ pr of i l e/ or acl e/ t nsnames. or a
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:
Sumof al l dat adevspaces t o smal l f or t he SAP Syst em
Pl ease change t he val ue of t he par amet er MI N_DB_SI ZE i n t he
DATABASE. R3S f i l e:
Sect i on: [ ADMI NDBSI ZE_I ND_ADA]
MI N_DB_SI ZE=15000 <= change t he val ue t o 1500
Save t he f i l e and r est ar t R3SETUP.


MaxDB 7.5 / 7.6:
The description (gecos) of the sdb user and sqd<si d>users differs from
SAPDB/MaxDB version (or version of sapi nst ).
The LDAP entry of the depended user must be modified manually to the value
shown in the user mod which failed. To do so please use command
f f _user _adm. pl –op mod –gecos <descr i pt i on>
- - user <user _name> - - pool <pool _name>.
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.
Database in General
44 Installation Guide for SAP Solutions
The following screenshot shows an example for the SAPMS4 user:

Afterwards, the transaction db50 has to be called according to OSS note 588515.
8.5.1.1 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/ <SI D>/ XUSERD on both platforms (on the NetApp
Filer they will be located in different directories containing the OS).
● Move the corresponding file / home_sap/ <si d>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
Database in General
Installation Guide for SAP Solutions 45
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. ci ml 4,
dbml 4- 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 / et c/ opt / sdb.
If the file does not exist create it manually and insert these lines:
[ Gl obal s]
I ndepDat a=/ sapdb/ dat a
I ndepPr ogr ams=/ sapdb/ pr ogr ams
SdbOwner =sdb
SdbGr oup=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
Database in General
46 Installation Guide for SAP Solutions
8.5.3 MaxDB 7.6

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


Database in General
Installation Guide for SAP Solutions 47
8.5.4 IO Balancing
The SAPDB parameter _FBM_LOW_I O_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 / sapdat a/ sapdat a<n>(analogously for
SAPLOG); a link (only versions lower MaxDB 7.6) from / sapdb/ <SI D>/ sapdat a is
created automatically.
Except sapi nst from SAP Version 6.40, the SID has to be added. Please enter
/ sapdat a/ sapdat a1/ <SI D>, e.g.:
/sapdata/sapdata1/P11
Set the SAPLOG volumes accordingly.
/saplog/saplog1/P11

8.6 SAP Installation with Database DB2
We support DB2 database only at administrative level. That means you cannot specify a
SAP system with DB2 database within the Planning Tool.
8.6.1 Software Requirements
To run DB database within a SAP system you need at least the software shown below:
● FlexFrame for SAP, 4.1A00
● FlexFrame Autonomous Agents, V30K15 up
● SAP NetWeaver 2004s (SR1/SR2)
● R/3 4.7x200 with kernel release 640, Patch 189
● R/3 4.6C SR2 with Kernel 4.6D_EXT 64-Bit, Patch 23xx
● DB2 LUW 9.1 FP3SAP for Linux x86_64_Bit (Download from http.//service.sap.com)
● DB2 LUW 9.1 FP3SAP for Solaris (Download from http.//service.sap.com)
Optional it could be necessary to install DB2 LDAP-Plug-in from
http://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=swg
-dm-db2ldap
It needs a registration at IBM company.
Database in General
48 Installation Guide for SAP Solutions
8.6.2 Pre-Installation Steps
● Stop the FA-Autonomous Agents during installation time
● Create a new SID instance using f f _si d_adm. pl :
ff_sid_adm.pl --op add --pool pool1 –-sid LB4 --sapversion 7.0
--db DB2V91:dblb4-se:10.10.12.159
--sap ci:57:cilb4:10.10.10.57:cilb4-se:10.10.12.57
--sap ascs:55:ascslb4:10.10.10.55:ascslb4-se:10.10.12.55
--sap app:58:app58lb4:10.10.10.58:app58lb4-se:10.10.12.58
--sap scs:56:scslb4:10.10.10.56:scslb4-se:10.10.12.56
--db2srvsapdb2LB4:60000,DB2_db2lb4:60001,DB2_db2lb4_1:60002,
DB2_db2lb4_2:60003,DB2_db2lb4_END:60004
The script f f _si d_adm. pl prepares the system files / et c/ host s and
/ et c/ ser vi ces of the application nodes known in the specific pool.
The script writes a log file in / Fl exFr ame/ vol FF/ pool - pool 1/ db2 to show you
the changes made in system files. There will also a log file with LDIFs of all LDAP
modifications done with this SID.
● Run f f _si d_mnt _adm. pl if you want to relocate your directories for
SAPDATA/SAPLOG to a volume of your own.
● Run f f _set up_si d_f ol der . sh:
ff_setup_sid_folder.sh pool1 LB4

8.6.3 Installing DB2
Today the installation is not fully integrated within sapinst. So you need to perform an
additional step to make the DB2 software available for the installation of SAP later.
There are two ways to install the database software. Both methods are possible. The
second method should be sufficient with SAP installation.
We recommend you to install the software to an SID specific directory. Our
recommendation would be / db2/ <si d>/ <somet hi ng>.
● Install software using db2set up.
On the path your DB2 software DVD is available (example Linux) you make a switch
to / LI NUXX86_64/ ESE/ di sk1 and call
./db2setup.
You have to choose an standard installation with no creation of a DB2 instance. Use
the dasusr <#>for your installation. dasusr 1 is available with FlexFrame. If you
want to use another one you must fulfill the requirement of the user’s name,
Database in General
Installation Guide for SAP Solutions 49
dasusr <#>. You can create that user using f f _user _adm. pl . The primary group
of the user is always dasadm<#>. We recommend to use the predefined group
dasadm1. Otherwise you can create a group of your own by f f _gr oup_adm. pl
from the Toolbox-CD.
● Install software using response file
You create an response file with the following content:
PROD=ENTERPROSE_SERVER_EDI TI ON
FI LE=/ db2/ LB4/ db2sof t
LI C_AGREEMENT=ACCEPT
I NSTALL_TYPE=TYPI CAL
LANG=EN
CONFI G_ONLY=NO
and run
db2setup –I en –l <log> -t <trace> -r <full_path_to_response_file>
In both cases you are complaint that the installation could not handle the link from
/ usr / l ocal _bi n/ db2l s to / db2/ LB4/ db2sof t / i nst al l / db2l s. Please
create that link after running db2set up, not before !!! If you do not install DB2 for
the first time, delete the link before running db2set up and create it again
afterwards. Otherwise db2set up will not finish with a log message.
In Linux you create the link on control node using (example)
/ Fl exFr ame/ vol FF/ os/ Li nux/ <i mage_name>/ r oot _i mg/ usr / l ocal / bi n:
ln –s /db2/LB4/db2soft/installation/db2ls db2ls

8.6.4 Installing DB2 License
With R/3 4.7 the DB2 instance is created manually before SAPINST will be started with
DB2 instance installation and the license files must be applied before SAPINST is called
(see exceptions in document for R/3 4.7).
The unlimited DB2 license can be downloaded from http://service.sap.com (please refer
to SAP note 816773). Copy it to a file system that can be accessed from an application
node.
Install the license as db2<si d> user by the following commands:
db2licm –a db2ese_c.lic
db2licm –a db2dpf.lic
db2licm –a db2so.lic
db2licm –a db2hf.lic
Database in General
50 Installation Guide for SAP Solutions
You check the license installation with
db2licm –l
You should have installed permanent licenses for
● DB2 Enterprise Server Edition
● DB2 database partitioning
● DB2 storage optimization
● Homogeneous federation for DB2
8.6.5 LDAP-Plugin
Sometimes it is possible to get error messages while connecting to the database. In that
case we recommend to install the available LDAP-Plugin. You can request that Plugin
from IBM site
http://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=swg
-dm-db2ldap
Copy the I BMLDAPaut hser ver . so (example Linux) to
/ home_sap/ db2<si d>/ sql l i b/ secur i t y64/ pl ugi n/ ser ver .
Copy the I BMLDAPSecur i t y. i ni to / home_sap/ db2<si d>/ sql l i b/ cf g and adapt
the following lines to your system environment:
LDAP_HOST =<cont r ol Node1>- se <cont r ol Node2>- se
USER_BASEDN = ou=Peopl e, ou=pool 1, ou=Pool s, …, dc=…
GROUP_BASEDN = ou=Gr oup, ou=pool 1, ou=Pool s, …, dc=…
SEARCH_DN =cn=r oot , ou=LDAPadmi ns, ou=Fl exFr ame, …, dc=…
SEARCH_PW=<your _passwor d”
To enable the changes you perform
db2 update dbm cfg using SRVCON_PW_PLUGIN IBMLDAPauthserver

It is necessary to restart the database (db2st op, db2st ar t as user db2<si d>) for
activating the changes.
8.6.6 Install SAP
At this point it is possible to install SAP as known from other installations using Oracle or
MaxDB. Please refer to the corresponding explanations in this document concerning SAP
installations.
In most case it is a good idea to run the command chmod 777 for all files and directories
in installation directories.
Database in General
Installation Guide for SAP Solutions 51
8.6.7 Changes in System Files
The virtual db hostname (db<si d>- se) is written to / et c/ host s by f f _si d_adm. pl .
The services needed for DB2 are inserted into / et c/ ser vi ces (you can look for the
service names also into LDAP searching for services like DB2_db2<si d>and
sapdb2<SI D>).
f f _si d_adm. pl tries to modify the system files of all possible files in a pool. But if you
exchange your image or run f f _new_an. sh the changes are (maybe) lost. In that case
you should look into the logs written by f f _si d_adm. pl mentioned above and restore
the changes manually.
8.6.8 Post Installation Steps
After you installed your database you have to adapt the database catalog using
(executed as db2<si d>):
db2 uncatalog db <sid>
db2 cat al og db <si d> as <si d>l
db2 uncat al og node NODE<SI D>
db2 cat al og t cpi p node NODE<SI D> r emot e db<si d>- se ser ver sapdb2<SI D>
r emot e_i nst ance db2<si d>
db2 cat al og db <si d>l as <si d>at node NODE<SI D>

If you executed these command, you should have a configuration like this:
db2 list database directory
System Database Directory
Number of entries in the directory = 2
Database 1 entry:
Database alias = <SID>
Database name = <SID>L
Node name = NODE<SID>
Database release level = b.00
Comment =
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =
Database in General
52 Installation Guide for SAP Solutions
Database 2 entry:
Database alias = <SID>L
Database name = <SID>
Local database directory = /db2/<SID>
Database release level = b.00
Comment =
Directory entry type = Indirect
Catalog database partition number = 0
Alternate server hostname =
Alternate server port number =
db2 list node directory
Node Directory
Number of entries in the directory = 1
Node 1 entry:
Node name = NODE<SID>
Comment =
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = db<sid>-se
Service name = sapdb2<SID>


Installation Guide for SAP Solutions 53
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 / I BMxxxxxxxx
The example below shows SLES8 (SUN Java)

cont r ol 1: ~#>cd /FlexFrame/volFF/os/Linux/FSC3.2xxx/root_img/usr/java
cont r ol 1: ~#>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. <J AVA_DI R>=j 2sdk1. 4. 2_12)
Now the JAVA files are writeable.
SAP in General
54 Installation Guide for SAP Solutions
If the installation has finished successfully, do the following:
appnode1: ~#>umount /usr/java/<JAVA_DIR>
cont r ol 1: ~#>cd ..../var_img/var-xxxxxxxx/<JAVA_DIR>
cont r ol 1: ~#>cp -rp <JAVA_DIR>...os/Linux/FSC3.2xxx/root_img/usr/java
/<JAVA_DIR>
(e.g. <J AVA_DI R>=j 2sdk1. 4. 2_12)
9.2.2 Solaris
cont r ol 1: ~#>cd /FlexFrame/volFF/os/Solaris/<Solaris
Version>/bi..../Solaris_x/usr_sparc.all/usr/j2sdk
cont r ol 1: ~#>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>
cont r ol 1: ~#>cd /FlexFrame/volFF/os/Solaris/<Solaris_Version>/bi....
/Solaris_x/root/<hostname_storage_LAN>
cont r ol 1: ~#>cp -rp <JAVA_DIR>/FlexFrame/volFF/os/Solaris
/<Solaris_Version>/bi..../Solaris_x/usr_sparc.all/usr/j2sdk

Installation Guide for SAP Solutions 55
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 r oot : r oot / or acl e and
chmod - R 777 / or acl e 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
/ or acl e/ st age/ 920_32.


Please check the permissions of the users <si d>adm, or a<si d>and
sqd<si d>.

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 http://www.netapp.com/library/tr/3143.pdf
R3SETUP does not yet permit installation of SAP on NFS drives in this version.
If sapi nst 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.
Installing SAP 4.6C SR2
56 Installation Guide for SAP Solutions
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. 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.
Installing SAP 4.6C SR2
Installation Guide for SAP Solutions 57
Edit the *.R3S file and change STATUS=ERROR to STATUS=OK.
Restart R3SETUP.

Installing SAP 4.6C SR2
58 Installation Guide for SAP Solutions

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

Installing SAP 4.6C SR2
Installation Guide for SAP Solutions 59

Edit the *.R3S file and set the parameter BREAK_ON_NFS_PERMI SSI ON_ERROR=NO.

Restart R3SETUP.

Installation Guide for SAP Solutions 61
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 sapi nst Version 642 from NetWeaver04
SR1. In that case we suggest using the option SAPI NST_USE_HOSTNAME. See
also chapter “Installing Web AS 6.40 with NetWeaver04 SR1” on page 69.


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


During the installation, the file / et c/ ser vi ces will be copied under
/ et c/ ser vi ces. 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
keydb. xml . Change the entry to OK and restart the installation.


Please check the permissions of the users <si d>adm, or a<si d>, sqd<si d>
and sdb.


Starting SAPI NST directly from the ssh –X session will cause SAPI NST 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 113).
11.1 Installating Web AS 6.20 with sapinst 642
If you are not sure to have version 642 of the executable sapi nst , run the command
sapi nst –v; the output has to contain the string 642. Otherwise you have to continue
with the installation using the physical host name.
Installing Web AS 6.20
62 Installation Guide for SAP Solutions
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 ci osm:
# getent hosts ciosm
10. 1. 7. 106 ci osm<pool _name>- ci osm
Set the Client LAN interface up: Use the active interface which is not deprecated and
always has a virtual interface running, e.g. f j gi 2002001: 1.
Solaris:
# ifconfig fjgi2002001:2 plumb 10.1.7.106 netmask 0xffffff00 broadcast
10.1.7.255 up
Linux:
# /sbin/ifconfig vlan2001:0 10.1.6.101 broadcast 10.1.6.255 netmask
255.255.255.0

baby_3: ~ #cd / usr / sap/ OSM/ i nst al l
baby_3: ~ #mkdi r OSMCI
baby_3: ~ #chmod 777 OSMCI
baby_3: ~ #cd OSMCI

# . . . . / sapi nst - ext r act
Ext r act i ng i n / usr / sap/ OSM/ i nst al l / OSMCI . . .
sapi nst : ok
i acdl i b642. so: ok
i accdl i b. so: ok
i aej s642. so: ok
i akdbl i b642. so: ok
. . .
i ar f cl i b642. so: ok
Done
# SAPI NST_J RE_HOME=/ usr / j 2sdk/ j 2sdk1. 4. 2_10
# expor t SAPI NST_J RE_HOME
# . / sapi nst SAPI NST_USE_HOSTNAME=ci osm<MASTER- DVD/ pr oduct . cat al og
Installing Web AS 6.20
Installation Guide for SAP Solutions 63


Installing Web AS 6.20
64 Installation Guide for SAP Solutions

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
Ext r act i ng i n / usr / sap/ OSM/ i nst al l / OSMDB. . .
sapi nst : ok
i acdl i b642. so: ok
i accdl i b. so: ok
Installing Web AS 6.20
Installation Guide for SAP Solutions 65
i aej s642. so: ok
i akdbl i b642. so: ok
. . .
i ar f cl i b642. so: ok
Done
# SAPINST_JRE_HOME=/usr/j2sdk/<sdk_version_dir>
# export SAPINST_JRE_HOME
# ./sapinst SAPINST_USE_HOSTNAME=dbosm-se <MASTER-DVD>/product.catalog


Installing Web AS 6.20
66 Installation Guide for SAP Solutions
Due to a problem with sapi nst and virtual instances, the installation process will display
an error while starting the Central Instance with the wrong instance profile.

Installing Web AS 6.20
Installation Guide for SAP Solutions 67
To fix this problem use the following workaround:

Press St op.
Run the following commands:
baby_3: #su – osmadm
baby_3: #startsap r3
St ar t i ng SAP I nst ance DVEBMGS05
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
St ar t up- Log i s wr i t t en t o / home_sap/ osmadm/ st ar t sap_DVEBMGS05. l og
I nst ance on host Baby_3 st ar t ed
I GS on host Baby_3 st ar t ed
baby_3: #

# cd /usr/sap/OSM/install/OSMDB
# vi keydb.xml

Installing Web AS 6.20
68 Installation Guide for SAP Solutions
Search for the string ERROR in the section St ar t SAPSyst em.
Change ERROR to OK.


# ./sapinst SAPINST_USE_HOSTNAME=dbosm-se <MASTER-DVD>/product.catalog



Installation Guide for SAP Solutions 69
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
SAPI NST_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 / et c/ ser vi ces will be copied to
/ et c/ ser vi ces. 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
keydb. xml . 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<SI D>of the ABAP instance will be added to the
local / et c/ ser vi ces file. This has to be done manually on Linux from the
Control Nodes. Afterwards, the entry has to be removed.
Installing Web AS 6.40 with NetWeaver04 SR1
70 Installation Guide for SAP Solutions
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 112).

For installation of a J2EE instance or a J2EE Add-In in an existing ABAP
instance, the service sapms<SI D>of the ABAP instance will be added to the
local / et c/ ser vi ces file. This must be done manually on Linux from the
Control Nodes. Afterwards, the entry must be removed.
Installing Web AS 6.40 with NetWeaver04 SR1
Installation Guide for SAP Solutions 71
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_vi r t ual _host name>is up and
running (e.g. i f conf i g <i nt er f ace_name>pl umb <vi r t _I P_addr ess> 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

Installing Web AS 6.40 with NetWeaver04 SR1
72 Installation Guide for SAP Solutions

Installing Web AS 6.40 with NetWeaver04 SR1
Installation Guide for SAP Solutions 73

Type in the
virtual DB host
name
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
12.2.2 DB
Make sure that the IP interface address of the <db_vi r t ual _host name>is up and
running (e. g. i f conf i g <i nt er f ace_name>pl umb <vi r t _I P_addr ess> 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


Installing Web AS 6.40 with NetWeaver04 SR1
76 Installation Guide for SAP Solutions
If you install a J2EE engine using the pr oduct _ha. cat al og, 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 cont r ol . xml after
var cl i ent =new Cl i ent Mappi ng( ) ;
var i ds =[ "ci Host I sUni x", "sapmnt Pat h"] ; var gl obal Host SI D;
- i f ( par seBool ( i nst al l er . get Gl obal Par amet er ( "Separ at eSCS") ) &&
( cont ext . get Bool ( "ci ") | | cont ext
. get Bool ( "db") ) )
Insert:
i f ( i nst al l er . onWi ndows( ) &&
par seBool ( i nst al l er . get Gl obal Par amet er ( "Separ at eSCS") ) &&
( cont ext . get Bool ( "ci ") | | cont ext . get Bool ( "db") ) ) {
Now, restart SAPinst.
12.2.3 JC
Make sure that the IP interface address of the <j c_vi r t ual _host name>is up and
running (e. g. i f conf i g <i nt er f ace_name>pl umb <vi r t _I P_addr ess> 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 _i nst ance_number _vi r t ual _host name>is up and running
(e. g. i f conf i g <i nt er f ace_name>pl umb <vi r t _ I P_addr ess> 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

Installing Web AS 6.40 with NetWeaver04 SR1
Installation Guide for SAP Solutions 77
12.2.5 Web AS 6.40 Deployment SP16
After installing JAVA or JAVA-AddIn using the NW04 SR1 DVD/CD, proceed as follows:
12.2.5.1 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>
product.catalog

12.2.5.2 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>
product.catalog

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 _vi r t ual _host name>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>/product.catalog

Installing Web AS 6.40 with NetWeaver04 SR1
78 Installation Guide for SAP Solutions


Installing Web AS 6.40 with NetWeaver04 SR1
Installation Guide for SAP Solutions 79

Installing Web AS 6.40 with NetWeaver04 SR1
80 Installation Guide for SAP Solutions

Type in the
virtual DB host
name
Installing Web AS 6.40 with NetWeaver04 SR1
Installation Guide for SAP Solutions 81
12.3.2 DB
Make sure that the IP interface address of the <db_vi r t ual _host name>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>/product.catalog
After successful loading the database, the automatic startup of SAP may fail sometimes.
● Please start the SAP manually
● Stop the SAPINST
● Modify the keydb. xml (search for ERROR in the section StartSAPSystem)
● Change the Status from ERROR to OK and startup the SAPI NST

Installing Web AS 6.40 with NetWeaver04 SR1
82 Installation Guide for SAP Solutions
12.3.3 APP
Make sure that the IP interface address of the
<app_i nst ance_number _vi r t ual _host name>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>/product.catalog

12.4 Web AS 6.40 ABAP + JAVA-AddIn
NetWeaver04SR1
12.4.1 CI
Make sure that the IP interface address of the <ci _vi r t ual _host name>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>/product.catalog

12.4.2 DB
Make sure that the IP interface address of the <db_vi r t ual _host name>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>/product.catalog

Installing Web AS 6.40 with NetWeaver04 SR1
Installation Guide for SAP Solutions 83
12.4.3 SCS
Make sure that the IP interface address of the <ci _vi r t ual _host name>, DB and CI
are up and running (in Web AS 6.40 you have to use the <ci _vi r t ual _host name>).

Before starting the installation procedure, add the sapms<SI D>entry manually
in the / et c/ ser vi ces (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>/product.catalog
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>/product.catalog
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>/product.catalog
Installing Web AS 6.40 with NetWeaver04 SR1
84 Installation Guide for SAP Solutions

Installing Web AS 6.40 with NetWeaver04 SR1
Installation Guide for SAP Solutions 85

Type in the
virtual CI host
name
Installing Web AS 6.40 with NetWeaver04 SR1
86 Installation Guide for SAP Solutions


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 J ava
Dat abase Cont ent (step 19) with the error message no connect i on t o
net wor k adapt er , please proceed as follows:
Stop the Oracle listener process. Change the virtual host name db<si d>- se to
the real host name (uname –a) in the l i st ener . or a and t nsnames. or a.
Start the Oracle listener process and click the Ret r y button from the SAPINST
GUI.

Installing Web AS 6.40 with NetWeaver04 SR1
Installation Guide for SAP Solutions 87
Check and modify the following:
● Copy the . sapenv_ci <si d>. csh file to .sapenv_scs<si d>. 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
12.4.4.1 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>
product.catalog
If the installation of the SCS Installation aborts at the step Depl oy J DDI (step 19) with
the error message no connect i on t o net wor k adapt er , please proceed as follows:
Stop the Oracle listener process. Change the virtual host name db<si d>- se to the real
host name (uname –a) in the l i st ener . or a and t nsnames. or a. Start the Oracle
listener process and click the Ret r y 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 / et c/ ser vi ces 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 sapi nst in the installation directory
( . . . <pat h_t o_SAPI NST>/ sapi nst –ext r act )
appnode1: ~#>./sapinst
SAPINST_USE_HOSTNAME=<virtual_hostname_of_APP_Server>
<PATH_to_SAP_MASTER_DVD>/product.catalog
Installing Web AS 6.40 with NetWeaver04 SR1
88 Installation Guide for SAP Solutions
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 / et c/ ser vi ces entry of your installed system
before starting the APP.

Installation Guide for SAP Solutions 89
13 Installing NetWeaver 7.0SR1/SR2

Linux:
During the installation, the file / et c/ ser vi ces will be copied under
/ et c/ ser vi ces. 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
keydb. xml . 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 10: 29: 35
CJ Sl i bModul e: : wr i t eEr r or _i mpl ( )
CJ S- 20022 Coul d not st ar t i nst ance ' J C41' of SAP syst emOLP.
ERROR 2006- 05- 17 10: 29: 35
CJ Sl i bModul e: : wr i t eEr r or _i mpl ( )
CJ S- 20022 Coul d not st ar t i nst ance ' J C41' of SAP syst em
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 sapi nst is
requested. You need a group entry in LDAP database (pool specific) adapted to your FF
environment like the following (example):
dn: cn=sapi nst , ou=Gr oup, ou=p1, ou=Pool s, ou=Fl exFr ame, dc=f f 32, dc=wdf , dc=f sc
, dc=net
obj ect Cl ass: t op
obj ect Cl ass: posi xGr oup
cn: sapi nst
user Passwor d: : eA==
gi dNumber : 3606
member Ui d: or asm2
member Ui d: 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:
LDI FI N=/ t mp/ l dapi n
r m$LDI FI N
echo "dn: cn=sapi nst , ou=Gr oup, ou=pool 1, ou=Pool s, ou=Fl exFr ame,
dc=j er , dc=f uj i t su- si emens, dc=com" >>$LDI FI N
Installing NetWeaver 7.0SR1/SR2
90 Installation Guide for SAP Solutions
echo " obj ect Cl ass: t op" >> $LDI FI N
echo " obj ect Cl ass: posi xGr oup" >> $LDI FI N
echo " gi dNumber : 1234" >> $LDI FI N
echo " user Passwor d: l eer " >> $LDI FI N
echo " cn: sapi nst " >> $LDI FI N

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 pool 1):
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.
Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 91

Choose the Next Button. If the next screen appears, please abort the installation.
Modify the files cont r ol . xml and sapi nst in the installation directory.
cont r ol . xml :
t hi s. cr eat eSer vi ceUni x =f unct i on( ) {
NW. t r ace( "NWI nst anceI nst al l . cr eat eSer vi ceUni x( ) ") ;
var changed = t hi s. r emoveSer vi ceUni x( ) ;
var ol dUser = t hi s. get NW( ) . get User s( ) . asRol e( NWUser s. r ol es. SAPSys) ;
t r y {
var ser vi ces = FSPat h. get ( "/ usr / sap/ sapservices/sapser vi ces") ;
var exi st s =ser vi ces. i sExi st i ng( ) ;
Installing NetWeaver 7.0SR1/SR2
92 Installation Guide for SAP Solutions
var node =ser vi ces. cr eat eFi l e( ) ;
node. chmod( "0754") ;
i f ( exi st s && ! changed) {
node. saveVer si on( ) ;
}
…………

t hi s. r emoveSer vi ceUni x =f unct i on( ) {
NW. t r ace( "NWI nst anceI nst al l . r emoveSer vi ceUni x( ) ") ;
t hi s. st opSer vi ceUni x( ) ;
var ser vi ces =FSPat h. get ( "/ usr / sap/ sapservices/sapser vi ces") ;
i f ( ! ser vi ces. i sExi st i ng( ) ) {
NW. t r ace( "NWI nst anceI nst al l . r emoveSer vi ceUni x( ) done: ", ser vi ces,
" doesn' t exi st . ") ;
r et ur n;
}
…………

t hi s. r emoveSer vi ceUni x =f unct i on( ) {
NW. t r ace( "NWI nst anceI nst al l . r emoveSer vi ceUni x( ) ") ;
t hi s. st opSer vi ceUni x( ) ;
var ser vi ces =FSPat h. get ( "/ usr / sap/ sapservices/sapser vi ces") ;
i f ( ! ser vi ces. i sExi st i ng( ) ) {
NW. t r ace( "NWI nst anceI nst al l . r emoveSer vi ceUni x( ) done: ", ser vi ces,
" doesn' t exi st . ") ;
r et ur n;
} el se {
var ser vi cesNode =ser vi ces. get Node( ) ; / / r esol ves sof t l i nks!
var t ype =ser vi cesNode. get NodeType( ) ;
ASSERT( ar gument s. cal l ee, t ype ! = "LI NK", "LI NK
/ usr / sap/ sapservices/sapser vi ces shoul d al r eady be r esol ved. ") ;
i f ( t ype ! = "FI LE") {

i nst al l er . wr i t eEr r or ( "sysl i b. f i l esyst em. nodeCr eat i onFai l edAl r eadyEx",
ser vi ces. t oSt r i ng( ) , "FI LE") ;
}
Change the umask value entry in the sapi nst file to 022:
# set umask t o pr event unaut hor i zed r ead
umask 022
Restart the installation:
appnode1: ~#>./sapinst SAPINST_USE_HOSTNAME=<virtual_hostname>
Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 93
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.
Installing NetWeaver 7.0SR1/SR2
94 Installation Guide for SAP Solutions
13.2 Sapinit File (Linux)
WARNI NG 2006- 06- 09 10: 06: 51
CJ Sl i bModul e: : wr i t eWar ni ng_i mpl ( )
Execut i on of t he command "/ usr / sap/ OLP/ i nst al l / SCS/ i nst al l sapi ni t . sh"
f i ni shed wi t h r et ur n code 1. Out put :
mv: cannot move `/ et c/ i ni t . d/ sapi ni t ' t o `/ et c/ i ni t . d/ sapi ni t . ol d' :
Read- onl y f i l e syst em
cp: cannot cr eat e r egul ar f i l e `/ et c/ i ni t . d/ sapi ni t ' : Read- onl y f i l e
syst em

ERROR 2006- 06- 09 10: 06: 51
CJ Sl i bModul e: : wr i t eEr r or _i mpl ( )
MUT- 03011 Execut i on of t he command
"/ usr / sap/ OLP/ i nst al l / SCS/ i nst al l sapi ni t . sh" f i ni shed wi t h r et ur n code
1. Out put :
mv: cannot move `/ et c/ i ni t . d/ sapi ni t ' t o `/ et c/ i ni t . d/ sapi ni t . ol d' :
Read- onl y f i l e syst em
cp: cannot cr eat e r egul ar f i l e `/ et c/ i ni t . d/ sapi ni t ' : Read- onl y f i l e
syst em

ERROR 2006- 06- 09 10: 06: 51 [ i axxgeni mp. cpp: 736]
showDi al og( )
FCO- 00011 The st ep i nst al l SAPI ni t wi t h st ep key
| NW_J ava_SCS| i nd| i nd| i nd| i nd| 0| 0| NW_Syst em| i nd| i nd| i nd| i nd| 5| 0| i nst al l SA
PI ni t was execut ed wi t h st at us ERROR .

Please proceed as follows:
appnode1: <I NSTALL_DI R> > vi keydb.xml

</ r ow>
<r ow>
<f l d name="STEPKEY">

<st r val ><! [ CDATA[ | NW_J ava_SCS| i nd| i nd| i nd| i nd| 0| 0| NW_Syst em| i nd| i nd| i nd|
i nd| 5| 0| i nst al l SAPI ni t ] ] >
</ st r val >
</ f l d>
<f l d name="STATUS">
<st r val ><! [ CDATA[ ERROR] ] >t o OK
</ st r val >
</ f l d>
<f l d name="STOP_BEFORE">
<st r val ><! [ CDATA[ ] ] >
</ st r val >
Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 95
</ f l d>
<f l d name="STOP_AFTER">
<st r val ><! [ CDATA[ ] ] >
</ st r val >
</ f l d>
<f l d name="STATE_SET_BY_STEP_STATE_EDI TOR">
<st r val ><! [ CDATA[ ] ] >
</ st r val >
Restart the installation:
appnode1: <I NSTALL_DI R>> ./sapinst SAPINST_USE_HOSTNAME=<virt._hostname>
13.3 installsapinit.sh – symlink (Linux)
WARNI NG 2006- 06- 30 10: 43: 23
CJ Sl i bModul e: : wr i t eWar ni ng_i mpl ( )
Execut i on of t he command "/ usr / sap/ LO7/ i nst al l / ASCS/ i nst al l sapi ni t . sh"
f i ni shed wi t h r et ur n code 5. Out put :
i nsser v: can not syml i nk( . . / sapi ni t , r c3. d/ S14sapi ni t ) : Read- onl y f i l e
syst em
i nsser v: can not syml i nk( . . / sapi ni t , r c3. d/ K08sapi ni t ) : Read- onl y f i l e
syst em
i nsser v: can not syml i nk( . . / sapi ni t , r c5. d/ S14sapi ni t ) : Read- onl y f i l e
syst em
i nsser v: can not syml i nk( . . / sapi ni t , r c5. d/ K08sapi ni t ) : Read- onl y f i l e
syst em

ERROR 2006- 06- 30 10: 43: 23
CJ Sl i bModul e: : wr i t eEr r or _i mpl ( )
MUT- 03011 Execut i on of t he command
"/ usr / sap/ LO7/ i nst al l / ASCS/ i nst al l sapi ni t . sh" f i ni shed wi t h r et ur n code
5. Out put :
i nsser v: can not syml i nk( . . / sapi ni t , r c3. d/ S14sapi ni t ) : Read- onl y f i l e
syst em
i nsser v: can not syml i nk( . . / sapi ni t , r c3. d/ K08sapi ni t ) : Read- onl y f i l e
syst em
i nsser v: can not syml i nk( . . / sapi ni t , r c5. d/ S14sapi ni t ) : Read- onl y f i l e
syst em
i nsser v: can not syml i nk( . . / sapi ni t , r c5. d/ K08sapi ni t ) : Read- onl y f i l e
syst em

ERROR 2006- 06- 30 10: 43: 23 [ i axxgeni mp. cpp: 736]
showDi al og( )
Installing NetWeaver 7.0SR1/SR2
96 Installation Guide for SAP Solutions
FCO- 00011 The st ep i nst al l SAPI ni t wi t h st ep key
| NW_ABAP_ASCS| i nd| i nd| i nd| i nd| 0| 0| NW_Syst em| i nd| i nd| i nd| i nd| 5| 0| i nst al l S
API ni t was execut ed wi t h st at us ERROR .

Please proceed as follows:
appnode1: <I NSTALL_DI R> > vi keydb.xml

<f l d name="STEPKEY">

<st r val ><! [ CDATA[ | NW_ABAP_ASCS| i nd| i nd| i nd| i nd| 0| 0| NW_Syst em| i nd| i nd| i nd
| i nd| 5| 0| cr eat ePor t s] ] >
</ st r val >
</ f l d>
<f l d name="STATUS">
<st r val ><! [ CDATA[ OK] ] >
</ st r val >

appnode1: <I NSTALL_DI R>> ./sapinst SAPINST_USE_HOSTNAME=<virt._hostname>
13.4 Services File (Linux)
ERROR 2006- 06- 20 11: 22: 09 [ syxxsyshl p. cpp: 78]
sysl i b: : pr i nt OSEr r or ( const i ast r i ng &, i nt , DWORD, const
i ast r i ng &, CMessage: : eLogMessage)
FSL- 00001 Syst emcal l f ai l ed. Er r or 30 ( Read- onl y f i l e syst em) i n
execut i on of syst emcal l ' openU' wi t h par amet er ( / et c/ ser vi ces. SAPt mp,
O_WRONLY | O_TRUNC | O_CREAT, S_I RWXU | S_I RWXG | S_I RWXO) , l i ne ( 413)
i n f i l e ( syuxcf i l e. cpp) .

ERROR 2006- 06- 20 11: 22: 09 [ syuxcf i l e. cpp: 417]
CSyFi l eI mpl : : copy( const CSyPat h & / et c/ ser vi ces. SAPt mp,
I SyNode: : CopyMoveMode_t 0x3, I SyPr ogr essObser ver *) const
FSL- 02013 Unabl e t o access f i l e / et c/ ser vi ces. SAPt mp: cannot get wr i t e
access.

ERROR 2006- 06- 20 11: 22: 09 [ syxxcsent . cpp: 492]

CSySer vi cesEnt r yI mpl : : edi t Ser vi ces( I SySer vi cesEnt r y: : eWr i t eMode
REPLACE_NAME) const
FSL- 03006 Unknown except i on caught when t r yi ng t o add an ent r y t o t he
ser vi ce f i l e.

ERROR 2006- 06- 20 11: 22: 09
CJ Sl i bModul e: : wr i t eEr r or _i mpl ( )
Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 97
MUT- 03025 Caught ESyExcept i on i n Modul ecal l : ESAPi nst Except i on: er r or
t ext undef i ned.

Please abort the installtion and proceed as follows:
appnode1: <I NSTALL_DI R> > vi keydb.xml

<r ow>
<f l d name="STEPKEY">

<st r val ><! [ CDATA[ | NW_ABAP_ASCS| i nd| i nd| i nd| i nd| 0| 0| NW_Syst em| i nd| i nd| i nd
| i nd| 5| 0| cr eat ePor t s] ] >
</ st r val >
</ f l d>
<f l d name="STATUS">
<st r val ><! [ CDATA[ ERROR] ] >t o OK
</ st r val >
Restart the installation:
appnode1: <I NSTALL_DI R>> ./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 10: 24: 26 [ i axxi nscbk. cpp: 271]
abor t I nst al l at i on
CJ S- 00084 SQL st at ement or scr i pt f ai l ed. <br >DI AGNOSI S: Er r or message:
SP2- 0606: Cannot cr eat e SPOOL f i l e "r ecompi l e. l og"

' UTL_RECOMP_BEGI N: ' | | TO_CH
- - - - - - - - - - - - - - - - - - - - - - - - - -
ut l _r ecomp_begi n: 10: 06: 24

PL/ SQL pr ocedur e successf ul l y compl et ed.
PL/ SQL pr ocedur e successf ul l y compl et ed.

' UTL_RECOMP_END: ' | | TO_CH
- - - - - - - - - - - - - - - - - - - - - - - -
ut l _r ecomp_end: 10: 06: 25

Di sconnect ed f r omOr acl e Dat abase 10g Ent er pr i se Edi t i on Rel ease
10. 2. 0. 2. 0 - 64bi t Pr oduct i on
Wi t h t he Par t i t i oni ng and Dat a Mi ni ng opt i ons
Installing NetWeaver 7.0SR1/SR2
98 Installation Guide for SAP Solutions
. <br >SOLUTI ON: See or a_sql _r esul t s. l og and t he Or acl e document at i on f or
det ai l s.

ERROR 2006- 06- 27 10: 24: 26
CJ Sl i bModul e: : wr i t eEr r or _i mpl ( )
MUT- 03025 Caught ESAPi nst Except i on i n Modul ecal l : ESAPi nst Except i on:
er r or t ext undef i ned.
ERROR 2006- 06- 27 10: 24: 26 [ i axxgeni mp. cpp: 736]
showDi al og( )
FCO- 00011 The st ep r ecompi l eDDI C wi t h st ep key
| NW_Doubl est ack_DB| i nd| i nd| i nd| i nd| 0| 0| NW_Cr eat eDBandLoad| i nd| i nd| i nd| i n
d| 9| 0| NW_Cr eat eDB| i nd| i nd| i nd| i nd| 0| 0| NW_Or aDBCheck| i nd| i nd| i nd| i nd| 0| 0|
NW_Or aDBMai n| i nd| i nd| i nd| i nd| 0| 0| NW_Or aDBSt d| i nd| i nd| i nd| i nd| 3| 0| NW_Or aD
bBui l d| i nd| i nd| i nd| i nd| 5| 0| r ecompi l eDDI C was execut ed wi t h st at us 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 89) and restart the installation:
appnode1: <I NSTALL_DI R> > chmod 777 *
appnode1: <I NSTALL_DI R> > chmod 777 .
appnode1: <I NSTALL_DI R>> ./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.


I NFO[ E] 2006- 03- 14 10: 20: 53 [ syuxcuser . cpp: 1813]
CSyUser I mpl _get OsI nf os( I LogBook *m_l ogBook, i ast r i ng sName,
i ast r i ng sI D, t SyUser I nf o& msUser i nf o)
FSH- 00006 Ret ur n val ue of f unct i on get pwnam( undef i ned) i s NULL.

TRACE [ syuxcuser . cpp: 1493]
bool CSyUser I mpl : : i sExi st i ngOnOS( )
checki ng exi st ence of account user ="undef i ned" succeeded wi t h f al se.

ERROR 2006- 03- 14 10: 20: 53 [ syuxcuser . cpp: 278]
CSyUser I mpl : : CSyUser I mpl ( const CUser Dat a&, bool )
FSL- 01027 Account user ="undef i ned" does not exi st .

TRACE [ i axxej sbas. hpp: 379]
handl eExcept i on<ESyExcept i on>( )
Conver t i ng except i on i nt o J S Except i on ESyExcept i on.

Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 99
ERROR 2006- 03- 14 10: 20: 53
CJ Sl i bModul e: : wr i t eEr r or _i mpl ( )
MUT- 03025 Caught ESyExcept i on i n Modul ecal l : ESAPi nst Except i on: er r or
t ext undef i ned.

TRACE [ i axxej sbas. hpp: 451]
EJ S_Base: : di spat chFunct i onCal l ( )
J S Cal l back has t hr own unknown except i on. Ret hr owi ng.

ERROR 2006- 03- 14 10: 20: 53 [ i axxgeni mp. cpp: 653]
showDi al og( )
FCO- 00011 The st ep sdb_cr eat e_vol umes_f s wi t h st ep key
| NW_Doubl est ack_DB| i nd| i nd| i nd| i nd| 0| 0| NW_Cr eat eDB| i nd| i nd| i nd| i nd| 9| 0| N
W_ADA_DB| i nd| i nd| i nd| i nd| 6| 0| SdbPr eI nst anceDi al ogs| i nd| i nd| i nd| i nd| 2| 0| S
dbI nst anceDi al ogs| i nd| i nd| i nd| i nd| 1| 0| SDB_I NSTANCE_CREATE| i nd| i nd| i nd| i n
d| 0| 0| sdb_cr eat e_vol umes_f s was execut ed wi t h st at us ERROR .

TRACE [ i axxgeni mp. cpp: 651]
showDi al og( )

Logon to one of the control nodes:
cont r ol 1: ~#>cd /FlexFrame/volFF/os/Linux/<image_name>/root_img/etc/opt
cont r ol 1: ~#> ls –l sdb

If the sdb file does not exist, go to section “MaxDB 7.5/7.6 /etc/opt/sdb” on page 45.
cont r ol 1: ~#> rm sdb
cont r ol 1: ~#>
cp –p /FlexFrame/volFF/pool-<pool_name>/sapdb/<image_name>/sql/sdb .
Restart the installation:
appnode1: <I NSTALL_DI R>> ./sapinst SAPINST_USE_HOSTNAME=<virt._hostname>
If the installation finished succesfully change it back as it was originally:
cont r ol 1: ~#>cd /FlexFrame/volFF/os/Linux/<image_name>/root_img/etc/opt
cont r ol 1: ~#> rm sdb
cont r ol 1: ~#>ln –s /sapdb/sql/sdb .

13.7 NetWeaver 7.0SR1/SR2 / MaxDB76 and
SLES9_x86
During the ABAP import using MaxDB76 and SLES9_x86 the installation has permission
trouble:
Installing NetWeaver 7.0SR1/SR2
100 Installation Guide for SAP Solutions


Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 101
Execut i on of t he command "/ opt / I BMJ ava2- amd64- 142/ bi n/ j ava - cl asspat h
mi gmon. j ar - showver si on com. sap. i nst . mi gmon. i mp. I mpor t Moni t or - dbType
ADA - i mpor t Di r s
/ sapcd/ SAP_SW/ NW2004sSR1/ DVD_NW_2004s_SR1_I nst al l at i on_Expor t / EXP1
: / sapcd/ SAP_SW/ NW2004sSR1/ DVD_NW_2004s_SR1_I nst al l at i on_Expor t / EXP2: / sap
cd/ SAP_SW/ NW2004sSR1/ DVD_NW_2004s_SR1_I nst al l at i on_Expor t / EXP3 -
i nst al l Di r / usr / sap/ BLM/ i nst al l / DB - or der By "" - r 3l oadExe
/ usr / sap/ BLM/ SYS/ exe/ r un/ R3l oad - t skFi l es yes - ext Fi l es no - dbCodepage
4103 - j obNum3 - moni t or Ti meout 30 - l oadAr gs " - nol og - c 0" - t r ace al l -
sapi nst " f i ni shed wi t h r et ur n code 2. Out put :
j ava ver si on "1. 4. 2"
J ava( TM) 2 Runt i me Envi r onment , St andar d Edi t i on ( bui l d 2. 2)
I BMJ 9SE VM( bui l d 2. 2, J 2RE 1. 4. 2 I BMJ 9 2. 2 Li nux amd64- 64
j 9xa64142i f x- 20051125 ( J I T enabl ed)
J 9VM- 20050524_1742_LHdSMr
J I T - r 7_l evel 20050518_1803)

j ava. i o. Fi l eNot FoundExcept i on:
/ usr / sap/ BLM/ i nst al l / DB/ i mpor t _moni t or _cmd. pr oper t i es ( Per mi ssi on
deni ed)
Requi r ed syst emr esour ces ar e mi ssi ng or not avai l abl e:
DDL cont r ol f i l e ' / usr / sap/ BLM/ i nst al l / DB/ DDLADA. TPL' does not have
r ead access.

ERROR 2006- 06- 29 11: 27: 58
CJ Sl i bModul e: : wr i t eEr r or _i mpl ( )
CJ S- 30022 Pr ogr am' Mi gr at i on Moni t or ' exi t s wi t h er r or code 2. For
det ai l s see l og f i l e( s) i mpor t _moni t or . j ava. l og, i mpor t _moni t or . l og.

ERROR 2006- 06- 29 11: 27: 58 [ i axxgeni mp. cpp: 736]
showDi al og( )
FCO- 00011 The st ep r unMi gr at i onMoni t or wi t h st ep key
| NW_Doubl est ack_DB| i nd| i nd| i nd| i nd| 0| 0| NW_Cr eat eDBandLoad| i nd| i nd| i nd| i n
d| 9| 0| NW_ABAP_I mpor t _Di al og| i nd| i nd| i nd| i nd| 5| 0| NW_ABAP_I mpor t | i nd| i nd| i
nd| i nd| 0| 0| r unMi gr at i onMoni t or was execut ed wi t h st at us ERROR .

I NFO 2006- 06- 29 11: 31: 08 [ i axxgeni mp. cpp: 787]
Do not abort the installtion. Change the permissions of the file DDLADA.TPL and use the
RETRY Button to restart the installation.
appnode1: <I NSTALL_DI R>> chmod 777 DDLADA.TPL

Installing NetWeaver 7.0SR1/SR2
102 Installation Guide for SAP Solutions
13.8 NetWeaver 7.0SR1/SR2 MaxDB76 and
Solaris9
If you receive an error message sdb_cr eat e_db_i nst ance during the DB installation,
please proceed as follows:
ERROR 2006- 07- 06 11: 25: 45
FCO- 00011 The st ep sdb_cr eat e_db_i nst ance wi t h st ep key
| NW_Doubl est ack_DB| i nd| i nd| i nd| i nd| 0| 0| NW_Cr eat eDBandLoad| i nd| i nd| i nd| i n
d| 9| 0| NW_Cr eat eDB| i nd| i nd| i nd| i nd| 0| 0| NW_ADA_DB| i nd| i nd| i nd| i nd| 6| 0| SdbP
r eI nst anceDi al ogs| i nd| i nd| i nd| i nd| 3| 0| SdbI nst anceDi al ogs| i nd| i nd| i nd| i nd
| 1| 0| SDB_I NSTANCE_CREATE| i nd| i nd| i nd| i nd| 0| 0| sdb_cr eat e_db_i nst ance was
execut ed wi t h st at us ERROR .
XCMDOUT.LOG (Example: SID=CSM, Password=password)
XCMDOUT. LOG
> Subpr ocess st ar t s at 20060706112543

Execut e Command : / sapdb/ pr ogr ams/ bi n/ dbmcl i - n dbcsm- se - R
/ sapdb/ CSM/ db db_cr eat e CSMCONTROL, ******** sqdcsm, passwor d
St ar t subpr ocess as user wi t h ui d: r oot

> Subpr ocess st ops at 20060706112545

ERR
- 24875, ERR_NEEDADMI : The oper at i ng syst emuser i s not a member of t he
dat abase admi ni st r at or s gr oup
- 24994, ERR_RTE: Runt i me envi r onment er r or
20145, UNI X passwor d ********
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 t cp: t cp_conn_hash_si ze=23768 and
t cp: t cp_t i me_wai t _i nt er val =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 / et c/ syst emon all Application Nodes. With Solaris 10 you can set these
parameters SID specific with f f _pr oj ect _adm. pl .
If the installation stops with the following error do not abort the SAPINST installation:
Er r or : Abor t ed: devel opment component ' i r j ' / ' sap. com' / ' SAP
AG' / ' 7. 0004. 20050921183647. 0000' :
Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 103
Caught except i on whi l e checki ng t he l ogi n cr edent i al s f or SAP J 2EE
Engi ne. Check whet her t he SAP J 2EE Engi ne i s up and r unni ng.
com. sap. engi ne. depl oy. manager . Depl oyManager Except i on: ERROR: Cannot
connect t o Host : [ j col p] wi t h user name: [ Admi ni st r at or ]
Check your l ogi n i nf or mat i on.
Except i on i s:
com. sap. engi ne. ser vi ces. j ndi . per si st ent . except i ons. Nami ngExcept i on:
Except i on whi l e t r yi ng t o get I ni t i al Cont ext . [ Root except i on i s
com. sap. engi ne. ser vi ces. secur i t y. except i ons. BaseLogi nExcept i on: Cannot
cr eat e new Remot eLogi nCont ext i nst ance. ]
Use the configtool and change the bindHost settings as it is shown below:

p4 port: host name j c<si d>

Do not forget to restart the JC instance manually

Click the Retry button at the SAPINST screen.
Installing NetWeaver 7.0SR1/SR2
104 Installation Guide for SAP Solutions
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>I NFO_SHORT=com. sap. sl d. api . wbem. except i on. CI MCommuni cat i onExcept i on: com. sap. sl d. api . wbem. except i on. CI MCommuni cat i onExcept i on:
CI M_ERR_FAI LED: I O err or: Read t i med out
at com. sap. sl d. api . wbem. cl i ent . WBEMHt t pRequest Sender. send( WBEMHt t pRequest Sender . j ava: 158)
at com. sap. sl d. api . wbem. cl i ent . WBEMRemot eCl i ent . send( WBEMRemot eCl i ent . j ava: 720)
at com. sap. sl d. api . wbem. cl i ent . WBEMRemot eCl i ent . send( WBEMRemot eCl i ent . j ava: 694)
at com. sap. sl d. api . wbem. cl i ent . WBEMRemot eCl i ent . send( WBEMRemot eCl i ent . j ava: 638)
at com. sap. sl d. api . wbem. cl i ent . WBEMRemot eCl i ent . r ef er encesI mpl ( WBEMRemot eCl i ent . j ava: 375)
at com. sap. sl d. api . wbem. cl i ent . WBEMCl i ent . r ef erences( WBEMCl i ent . j ava: 1773)
at com. sap. sl d. api . wbem. cl i ent . WBEMCl i ent Ut i l . ref er encesCompl et e( WBEMCl i ent Ut i l . j ava: 490)
at com. sap. l cr . per s. del t a. i mpor t i ng. SAPCRUpgr ade. col l ect Associ at i onsFor Rest or at i on( SAPCRUpgr ade. j ava: 700)
at com. sap. l cr . per s. del t a. i mpor t i ng. SAPCRUpgr ade. del et e( SAPCRUpgr ade. j ava: 355)
at com. sap. l cr . per s. del t a. i mpor t i ng. I mport Handl er . l oadFul l I mpor t ( I mpor t Handl er . j ava: 1765)
at com. sap. l cr . per s. del t a. i mpor t i ng. I mport Handl er . l oadI mpl ( I mpor t Handl er. j ava: 1605)
at com. sap. l cr . per s. del t a. i mpor t i ng. I mport Handl er . l oad( I mpor t Handl er . j ava: 1573)
at com. sap. ct c. ut i l . SLDConf i g. i mpor t Sl dCont ent ( SLDConf i g. j ava: 812)
at com. sap. ct c. ut i l . SLDConf i g. perf or mFunct i on( SLDConf i g. j ava: 154)
at com. sap. ct c. ut i l . Conf i gSer vl et . doGet ( Conf i gSer vl et . j ava: 69)
at j avax. ser vl et . ht t p. Ht t pSer vl et . ser vi ce( Ht t pSer vl et . j ava: 740)
at j avax. ser vl et . ht t p. Ht t pSer vl et . ser vi ce( Ht t pSer vl et . j ava: 853)
at com. sap. engi ne. ser vi ces. servl et s_j sp. ser ver . Ht t pHandl erI mpl . r unServl et ( Ht t pHandl er I mpl . j ava: 390)
at com. sap. engi ne. ser vi ces. servl et s_j sp. ser ver . Ht t pHandl erI mpl . handl eRequest ( Ht t pHandl er I mpl . j ava: 264)
at com. sap. engi ne. ser vi ces. ht t pserver . server. Request Anal i zer . st ar t Servl et ( Request Anal i zer. j ava: 347)
Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 105

at com. sap. engi ne. ser vi ces. ht t pserver . server. Request Anal i zer . st ar t Servl et ( Request Anal i zer. j ava: 325)
at com. sap. engi ne. ser vi ces. ht t pserver . server. Request Anal i zer . i nvokeWebCont ai ner ( Request Anal i zer . j ava: 887)
at com. sap. engi ne. ser vi ces. ht t pserver . server. Request Anal i zer . handl e( Request Anal i zer. j ava: 241)
at com. sap. engi ne. ser vi ces. ht t pserver . server. Cl i ent . handl e( Cl i ent . j ava: 92)
at com. sap. engi ne. ser vi ces. ht t pserver . server. Processor . r equest ( Pr ocessor. j ava: 148)
at com. sap. engi ne. cor e. ser vi ce630. cont ext . cl ust er . sessi on. Appl i cat i onSessi onMessageLi st ener . process( Appl i cat i onSessi onMessageLi st ener . j ava: 33)
at com. sap. engi ne. cor e. cl ust er. i mpl 6. sessi on. MessageRunner. r un( MessageRunner. j ava: 41)
at com. sap. engi ne. cor e. t hr ead. i mpl 3. Act i onObj ect . r un( Act i onObj ect . j ava: 37)
at j ava. securi t y. AccessCont r ol l er. doPri vi l eged( Nat i ve Met hod)
at com. sap. engi ne. cor e. t hr ead. i mpl 3. Si ngl eThr ead. execut e( Si ngl eThread. j ava: 100)
at com. sap. engi ne. cor e. t hr ead. i mpl 3. Si ngl eThr ead. r un( Si ngl eThread. j ava: 170)
Caused by: j ava. net . Socket Ti meout Except i on: Read t i med out
at j ava. net . Socket I nput St r eam. socket Read0( Nat i ve Met hod)
at j ava. net . Socket I nput St r eam. r ead( Socket I nput St r eam. j ava: 129)
at j ava. net . Socket I nput St r eam. r ead( Socket I nput St r eam. j ava: 182)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . st r eams. ChunkedI nput St r eam. r eadLi ne( ChunkedI nput St r eam. j ava: 323)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . st r eams. ResponseSt r eam. readLi ne( ResponseSt ream. j ava: 271)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . i mpl . Response. i ni t i al i ze( Response. j ava: 476)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . Connect i on. get Response( Connect i on. j ava: 2604)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . Connect i on. sendI nt er nal ( Connect i on. j ava: 1578)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . Connect i on. send( Connect i on. j ava: 1427)
at com. sap. sl d. api . wbem. cl i ent . WBEMHt t pRequest Sender. send( WBEMHt t pRequest Sender . j ava: 142)
. . . 30 more
caused by:
j ava. net . Socket Ti meout Except i on: Read t i med out
at j ava. net . Socket I nput St r eam. socket Read0( Nat i ve Met hod)
at j ava. net . Socket I nput St r eam. r ead( Socket I nput St r eam. j ava: 129)
Installing NetWeaver 7.0SR1/SR2
106 Installation Guide for SAP Solutions

at j ava. net . Socket I nput St r eam. r ead( Socket I nput St r eam. j ava: 182)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . st r eams. ChunkedI nput St r eam. r eadLi ne( ChunkedI nput St r eam. j ava: 323)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . st r eams. ResponseSt r eam. readLi ne( ResponseSt ream. j ava: 271)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . i mpl . Response. i ni t i al i ze( Response. j ava: 476)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . Connect i on. get Response( Connect i on. j ava: 2604)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . Connect i on. sendI nt er nal ( Connect i on. j ava: 1578)
at com. t ssap. dt r. cl i ent . l i b. prot ocol . Connect i on. send( Connect i on. j ava: 1427)
at com. sap. sl d. api . wbem. cl i ent . WBEMHt t pRequest Sender. send( WBEMHt t pRequest Sender . j ava: 142)
at com. sap. sl d. api . wbem. cl i ent . WBEMRemot eCl i ent . send( WBEMRemot eCl i ent . j ava: 720)
at com. sap. sl d. api . wbem. cl i ent . WBEMRemot eCl i ent . send( WBEMRemot eCl i ent . j ava: 694)
at com. sap. sl d. api . wbem. cl i ent . WBEMRemot eCl i ent . send( WBEMRemot eCl i ent . j ava: 638)
at com. sap. sl d. api . wbem. cl i ent . WBEMRemot eCl i ent . r ef er encesI mpl ( WBEMRemot eCl i ent . j ava: 375)
at com. sap. sl d. api . wbem. cl i ent . WBEMCl i ent . r ef erences( WBEMCl i ent . j ava: 1773)
at com. sap. sl d. api . wbem. cl i ent . WBEMCl i ent Ut i l . ref er encesCompl et e( WBEMCl i ent Ut i l . j ava: 490)
at com. sap. l cr . per s. del t a. i mpor t i ng. SAPCRUpgr ade. col l ect Associ at i onsFor Rest or at i on( SAPCRUpgr ade. j ava: 700)
at com. sap. l cr . per s. del t a. i mpor t i ng. SAPCRUpgr ade. del et e( SAPCRUpgr ade. j ava: 355)
at com. sap. l cr . per s. del t a. i mpor t i ng. I mport Handl er . l oadFul l I mpor t ( I mpor t Handl er . j ava: 1765)
at com. sap. l cr . per s. del t a. i mpor t i ng. I mport Handl er . l oadI mpl ( I mpor t Handl er. j ava: 1605)
at com. sap. l cr . per s. del t a. i mpor t i ng. I mport Handl er . l oad( I mpor t Handl er . j ava: 1573)
at com. sap. ct c. ut i l . SLDConf i g. i mpor t Sl dCont ent ( SLDConf i g. j ava: 812)
at com. sap. ct c. ut i l . SLDConf i g. perf or mFunct i on( SLDConf i g. j ava: 154)
at com. sap. ct c. ut i l . Conf i gSer vl et . doGet ( Conf i gSer vl et . j ava: 69)
at j avax. ser vl et . ht t p. Ht t pSer vl et . ser vi ce( Ht t pSer vl et . j ava: 740)
at j avax. ser vl et . ht t p. Ht t pSer vl et . ser vi ce( Ht t pSer vl et . j ava: 853)
at com. sap. engi ne. ser vi ces. servl et s_j sp. ser ver . Ht t pHandl erI mpl . r unServl et ( Ht t pHandl er I mpl . j ava: 390)
at com. sap. engi ne. ser vi ces. servl et s_j sp. ser ver . Ht t pHandl erI mpl . handl eRequest ( Ht t pHandl er I mpl . j ava: 264)
at com. sap. engi ne. ser vi ces. ht t pserver . server. Request Anal i zer . st ar t Servl et ( Request Anal i zer. j ava: 347)
Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 107

at com. sap. engi ne. ser vi ces. ht t pserver . server. Request Anal i zer . st ar t Servl et ( Request Anal i zer. j ava: 325)
at com. sap. engi ne. ser vi ces. ht t pserver . server. Request Anal i zer . i nvokeWebCont ai ner ( Request Anal i zer . j ava: 887)
at com. sap. engi ne. ser vi ces. ht t pserver . server. Request Anal i zer . handl e( Request Anal i zer. j ava: 241)
at com. sap. engi ne. ser vi ces. ht t pserver . server. Cl i ent . handl e( Cl i ent . j ava: 92)
at com. sap. engi ne. ser vi ces. ht t pserver . server. Processor . r equest ( Pr ocessor. j ava: 148)
at com. sap. engi ne. cor e. ser vi ce630. cont ext . cl ust er . sessi on. Appl i cat i onSessi onMessageLi st ener . process( Appl i cat i onSessi onMessageLi st ener . j ava: 33)
at com. sap. engi ne. cor e. cl ust er. i mpl 6. sessi on. MessageRunner. r un( MessageRunner. j ava: 41)
at com. sap. engi ne. cor e. t hr ead. i mpl 3. Act i onObj ect . r un( Act i onObj ect . j ava: 37)
at j ava. securi t y. AccessCont r ol l er. doPri vi l eged( Nat i ve Met hod)
at com. sap. engi ne. cor e. t hr ead. i mpl 3. Si ngl eThr ead. execut e( Si ngl eThread. j ava: 100)
at com. sap. engi ne. cor e. t hr ead. i mpl 3. Si ngl eThr ead. r un( Si ngl eThread. j ava: 170)
/ / =>I mport i ng Dat a : / usr / sap/ XOS/ SYS/ gl obal / sl d/ model / CR_Cont ent . zi p URL=ht t p: / / ci xos: 59000 USER=J 2EE_ADMI N . . .
I mpor t St at us: PREPARI NG
#ERROR: CI M_ERR_FAI LED: I O er r or : Read t i med out
Installing NetWeaver 7.0SR1/SR2
108 Installation Guide for SAP Solutions
Use the configtool and change the bindHost settings as it is shown below:

p4 port: host name ci <si d>

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

Click the Retry button at the SAPINST screen.
Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 109
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:
Checki ng i f anot her SDMi s r unni ng on por t 57518
I nf o: Checki ng i f anot her SDMi s r unni ng on por t 57518
I nf o: St ar t t o add def i ni t i ons of Subst Var s.
I nf o: Used addmode="r epl ace_exi st i ng"
I nf o: Readi ng subst var f i l e "SUBS_PARAM_TO_BE_SET. XML".
Er r or : Can' t r ead f r omf i l e
/ usr / sap/ P11/ i nst al l / J C/ SUBS_PARAM_TO_BE_SET. XML.
Er r or : Coul d not add def i ni t i ons of Subst Var s.
Pr ocessi ng er r or . Ret ur n code: 4
Er r or : Pr ocessi ng er r or . Ret ur n code: 4

ERROR 2006- 06- 19 10: 26: 59 [ i axxi nscbk. cpp: 271]
abor t I nst al l at i on
MUT- 02041 SDMcal l of addsubst var s ends wi t h r et ur ncode 4

ERROR 2006- 06- 19 10: 26: 59
CJ Sl i bModul e: : wr i t eEr r or _i mpl ( )
MUT- 03025 Caught ESAPi nst Except i on i n Modul ecal l : ESAPi nst Except i on:
er r or t ext undef i ned.

ERROR 2006- 06- 19 10: 26: 59 [ i axxgeni mp. cpp: 736]
showDi al og( )
FCO- 00011 The st ep set Subst Var s wi t h st ep key
| NW_J ava_CI | i nd| i nd| i nd| i nd| 0| 0| NW_CI _I nst ance| i nd| i nd| i nd| i nd| 10| 0| NW_C
I _I nst ance_Conf i gur e_J ava| i nd| i nd| i nd| i nd| 3| 0| set Subst Var s was execut ed
wi t h st at us ERROR .

# set umask t o pr event unaut hor i zed r ead
umask 027

change t he val ue of umask t o 022
Restart the installation:
appnode1: ~#>./sapinst SAPINST_USE_HOSTNAME=<virt._hostname>

Installing NetWeaver 7.0SR1/SR2
110 Installation Guide for SAP Solutions
13.12 LiveCache
For LiveCache installation you have to
1. make the network interface available for l c<si d>- se
2. use l c<si d>- se for SAPI NST_USE_HOSTNAME
3. during installation use l c<si d>- se for liveCache host/server
4. use default password passwor d for user l caadm(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 SI D –n host –se –u cont r ol , passw–U c –S SAPR3 –t 0 –I 0
to create. To check creation use xuser l i st | mor e.
13.13 ERS – Enque Replicated Server
For installation hints please have a look into corresponding SAP sites (start at
http://help.sap.com/saphelp_nw2004s/helpdata/en/f0/b57338788f4d72e1000000
9b38f8cf/frameset.htm, Standalone Enqueue Server, High Availability, Configuration
the Replication Server).
The hostname must be set to er s<i nst ance#><si d>as defined by planning tool or
f f _si d_adm. pl command.
With NetWeaver 7.0SR1 the scripts st ar t sap or st opsap are (maybe) not prepared to
support ERS instances. Please check if the files contain lines like I NSTANCEer s.
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: / et c/ i ni t . d # cd /etc/init.d
appnode1: / et c/ i ni t . d # ls –l ./rc[3-5]/*sapinit*
l r wxr wxr wx 1 r oot r oot 10 May 18 14: 58 r c3. d/ K08sapi ni t - >. . / sapi ni t
l r wxr wxr wx 1 r oot r oot 10 May 18 14: 58 r c3. d/ S14sapi ni t - >. . / sapi ni t
l r wxr wxr wx 1 r oot r oot 10 May 18 14: 58 r c5. d/ K08sapi ni t - >. . / sapi ni t
l r wxr wxr wx 1 r oot r oot 10 May 18 14: 58 r c5. d/ S14sapi ni t - >. . / sapi ni t
Installing NetWeaver 7.0SR1/SR2
Installation Guide for SAP Solutions 111
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:
cont r ol 1: ~#>cd /FlexFrame/volFF/os/Linux/<image_name>/etc/init.d
cont r ol 1: ~#>mv ./rc3.d/S14sapinit ./rc3.d/s14sapinit
cont r ol 1: ~#>mv ./rc3.d/K08sapinit ./rc3.d/k08sapinit
cont r ol 1: ~#>mv ./rc5.d/S14sapinit ./rc5.d/s14sapinit
cont r ol 1: ~#>mv ./rc5.d/K08sapinit ./rc5.d/k08sapinit
13.14.2 Solaris
appnode1: ~#>ls –l /etc/rc[1-5].d/*sapinit*
l r wxr wxr wx 1 r oot sapi nst 19 J ul 6 17: 56
/ et c/ r c1. d/ K10sapi ni t - >/ et c/ i ni t . d/ sapi ni t
l r wxr wxr wx 1 r oot sapi nst 19 J ul 6 17: 56
/ et c/ r c2. d/ K10sapi ni t - >/ et c/ i ni t . d/ sapi ni t
l r wxr wxr wx 1 r oot sapi nst 19 J ul 13 15: 19
/ et c/ r c3. d/ S90sapi ni t - >/ et c/ i ni t . d/ sapi ni t
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 t he var i abl e USRSAP f r om/ usr / sap =>/ usr / sap/ sapser vi ces

PGM_PATH=$0
PGMNAME=sapst ar t sr v
ARG1=$1
ARG2=$2
ARGUMENTS=$*
USRSAP=/ usr / sap/ sapservices
SAPSERVI CE_PATH=${USRSAP}/ sapser vi ces


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

Installing NetWeaver 7.0SR1/SR2
112 Installation Guide for SAP Solutions
13.14.4 Solaris 10 Preparations
The setting of the operating system parameters changed with Solaris 10. Instead of
settings made in / et c/ syst emso 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 f f _pr oj ect _adm. pl and
f f _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 'project.max-sem-ids=(priv,...)' --users orat11,t11adm


Post-SAP Installation Steps
Installation Guide for SAP Solutions 113
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.
bl ade1: 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 SAPLOCALHOSTFULL.If you need FQDN you can
insert it using f f _host s. sh.
Example for Central instance host:
● Looking for IP@ of CI: get ent host s | gr ep ci <si d>
● Adding alias to LDAP: f f _host s. sh –p <pool _name>- a <i p@>- n <f qdn>
14.1 Configuring the Virtual Host Name Manually
The scripts of the start and stop mechanism for SAP solutions use the UNIX host name
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: t om1bx1
Virtual hostname: ci <si d> (SAP Central Instance)
Move . sapr c_t om1bx1. sh to . sapr c_ci <si d>. sh.
Check if . dbenv. [ c] sh and . sapenv. [ c] sh already exist. If the files do not exist
please create a softlink, e.g. l n –s . dbenv_db<si d>. [ c] sh . dbenv. [ c] sh.
With sapi nst from SAP 6.40 you have to create the softlink always.
Post-SAP Installation Steps
114 Installation Guide for SAP Solutions
To avoid changing all standard scripts that use the host name command, this command
is simply replaced by a script of the same name for the admand 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 . cshr c login script in $HOME of
<si d>adm, or a<si d>( Oracle) and sqd<si d>(SAPDB/MaxDB):
# Fi l e host name i s gener at ed t o enabl e t he vi r t ual host name,
# an al i as act i vat es i t .
# . cshr c and . pr of i l e must cont ai n:
# csh:
al i as host name "echo `~/ host name`"

# bash, ksh:
al i as host name="echo `~/ host name`"
If bash or sh is used as the login shell instead of csh, the relevant line has to be
activated for it.
The ~/ host name 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: or aosm56>vi .cshrc
#Fi l e host name i s gener at ed t o enabl e t he vi r t ual host name
#t he f ol l owi ng al i as act i vat e i t .

alias hostname "echo `~/hostname`"

appnode1: or aosm4%vi hostname
#! / bi n/ bash
i f [ ! - z "$VHOSTNAME" ]
t hen echo $VHOSTNAME
el se ~/ host name_def aul t
f i

appnode1: or aosm7%vi hostname_default
echo ciosm

Post-SAP Installation Steps
Installation Guide for SAP Solutions 115
14.1.1 Central Instance (not valid for Web AS 6.40 J2EE)
Proceed with the following modifications:
● / home_sap/ <si d>adm
After installation, rename the installed . *_<phys_host name>. *sh
to . *_ci <si d>. *sh.
● / sapmnt / <SI D>/ pr of i l e
Change the profile names from *_<phys_host name> to *_ci <si d>.
● DEFAULT. PFL
SAPGLOBALHOST=ci <si d>
DBHOSTNAME=db<si d>- se.
● Instance Profile
SAPLOCALHOST=ci <si d>
● Start Profile
Change all host names (containing the physical host names) to ci <si d>.
Additional for 4.6C SR2:
● / home_sap/ <si d>adm
Change the file names for start/stop to new the virtual host name ci <si d>.
● / home_sap/ <si d>adm
In all files change the host name to ci <si d>.
● / home_sap/ <si d>adm
Delete the following line in *. cshr c:
Case Li nux. . .
14.1.2 Database Instance (also valid for WebAS 6.40 J2EE)
Proceed with the following modifications:
● / or acl e/ <SI D>
After installation, rename the installed . *_<phys_host name>. *sh
to . *_db<si d>- se. *sh.
Create a symbolic link from . *_db<si d>. *sh to . *_db<si d>- se. *sh.
Post-SAP Installation Steps
116 Installation Guide for SAP Solutions
Example:
l r wxr wxr wx 1 or aq85 dba 19 2005- 04- 06 11: 30 . dbenv_dbq85. csh
- > . dbenv_dbq85- se. csh
l r wxr wxr wx 1 or aq85 dba 18 2005- 04- 06 11: 33 . dbenv_dbq85. sh
- > . dbenv_dbq85- se. sh

● / or acl e/ <SI D>/ <Or acl e_Ver si on>_<32/ 64>/ net wor k/ admi n
Linux:
Change the host name in the files l i st ener . or a and t nsnames. or a from
<phys host name> to the IP address of db<si d>- se
(don’t use the virtual host name!).
Solaris:
Change the host name in the files l i st ener . or a and t nsnames. or a from
<phys_host name>to the virtual host name db<si d>- se.
● / home_sap/ <si d>adm
With some SAP installations it could be necessary to create additional links
ln –s .sapenv_<host_name>_.csh .sapenv.csh
ln –s .sapenv_<host_name>_.sh .sapenv.sh
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 . cshr c of <si d>admto 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/ <si d>adm
After installation, rename the installed . *_<phys_host name>. *sh
to . *_app<i d><si d>. *sh.
● / sapmnt / <SI D>/ pr of i l e
Change the profile names from *_<phys_host name>to *_app<i d><si d>.
Set SAPLOCALHOST=app<i d><si d>in every application instance profile.
Change all host names (containing the physical host names) to app<si d>in the
start profile.
Post-SAP Installation Steps
Installation Guide for SAP Solutions 117
Additional Modifications for 4.6C SR2:
● / home_sap/ <si d>adm
Change the file names for start/stop to the new virtual host name app<i d><si d>.
● / home_sap/ <si d>adm
In all files change the host name to app<i d><si d>.
● / home_sap/ <si d>adm
Delete the following row in *. cshr c: “Case Li nux. . . ”.
14.1.4 SCS Instance
Proceed with the following modifications:
● / home_sap/ <si d>adm
After installation, rename the installed . *_<phys_host name>. *sh
to . *_scs<i d><si d>. *sh.
● / sapmnt / <SI D>/ pr of i l e
Change the profile names from *_<phys_host name>to *_scs<i d><si d>.
Set SAPLOCALHOST=scs<i d><si d>in every application instance profile.
Change all host names (containing the physical host names) to scs<si d>in the
start profile.
Example Instance Profile:
SID=LO7 Instance=68
SAPSYSTEMNAME =LO7
SAPSYSTEM=68
I NSTANCE_NAME =SCS68
DI R_CT_RUN =$( DI R_EXE_ROOT) / r un
DI R_EXECUTABLE =$( DI R_I NSTANCE) / exe
SAPLOCALHOST = scsl o7
OS_UNI CODE =uc
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# SAP Messagi ng Ser vi ce f or J ava
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
r di sp/ msser v = 0
r di sp/ msser v_i nt er nal =3968
ms/ st andal one =1
ms/ ser ver _por t _0 =PROT=HTTP, PORT=81$$
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Post-SAP Installation Steps
118 Installation Guide for SAP Solutions
# SAP Locki ng Ser vi ce
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
enque/ ser ver i nst =68
enque/ t abl e_si ze =4096
r di sp/ enqname =$( r di sp/ myname)
enque/ snapshot _pck_i ds =100

Example Start Profile :
SAPSYSTEMNAME =LO7
SAPSYSTEM=68
I NSTANCE_NAME =SCS68
DI R_CT_RUN =$( DI R_EXE_ROOT) / r un
DI R_EXECUTABLE =$( DI R_I NSTANCE) / exe
SAPLOCALHOST = scsl o7
DI R_PROFI LE = $( DI R_I NSTALL) / pr of i l e
_PF = $( DI R_PROFI LE) / LO7_SCS68_scsl o7
SETENV_00 =LD_LI BRARY_PATH=$( DI R_LI BRARY) : %( LD_LI BRARY_PATH)
SETENV_01 =SHLI B_PATH=$( DI R_LI BRARY) : %( SHLI B_PATH)
SETENV_02 =LI BPATH=$( DI R_LI BRARY) : %( LI BPATH)
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# Copy SAP Execut abl es
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
_CPARG0 =l i st : $( DI R_CT_RUN) / scs. l st
Execut e_00 =i mmedi at e $( DI R_CT_RUN) / sapcpe$( FT_EXE) pf =$( _PF)
$( _CPARG0)
OS_UNI CODE =uc
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# St ar t SAP messagi ng ser vi ce
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
_MS = ms. sap$( SAPSYSTEMNAME) _$( I NSTANCE_NAME)
Execut e_01 =l ocal r m- f $( _MS)
Execut e_02 =l ocal l n - s - f $( DI R_EXECUTABLE) / msg_ser ver $( FT_EXE) $( _MS)
St ar t _Pr ogr am_00 =l ocal $( _MS) pf =$( DI R_PROFI LE) / LO7_SCS68_scsl o7
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# St ar t SAP l ocki ng ser vi ce
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
_EN = en. sap$( SAPSYSTEMNAME) _$( I NSTANCE_NAME)
Execut e_03 =l ocal r m- f $( _EN)
Execut e_04 =l ocal l n - s - f $( DI R_EXECUTABLE) / enser ver $( FT_EXE) $( _EN)
St ar t _Pr ogr am_01 =l ocal $( _EN) pf =$( DI R_PROFI LE) / LO7_SCS68_scsl o7

Post-SAP Installation Steps
Installation Guide for SAP Solutions 119
14.1.5 ASCS Instance (WebAS 7.00)
Proceed with the following modifications:
● / home_sap/ <si d>adm
After installation, rename the installed . *_<phys_ host name>. *sh
to . *_ascs<i d><si d>. *sh.
● / sapmnt / <SI D>/ pr of i l e
Change the profile names from *_<phys_host name>to *_ascs<i d><si d>.
Set SAPLOCALHOST=ascs<i d><si d>in every application instance profile.
Change all host names (containing the physical host names) to ascs<si d>in the
start profile.
Example Instance Profile:
SID=LO7 Instance=67
SAPSYSTEMNAME =LO7
SAPSYSTEM=67
I NSTANCE_NAME =ASCS67
DI R_CT_RUN =$( DI R_EXE_ROOT) / r un
DI R_EXECUTABLE =$( DI R_I NSTANCE) / exe
SAPLOCALHOST = ascsl o7
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# SAP Messagi ng Ser vi ce par amet er s ar e set i n t he DEFAULT. PFL
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ms/ st andal one =1
ms/ ser ver _por t _0 =PROT=HTTP, PORT=81$$
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# SAP Locki ng Ser vi ce
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
enque/ t abl e_si ze =4096
r di sp/ enqname =$( r di sp/ myname)
enque/ snapshot _pck_i ds =100

Example Start Profile:
SAPSYSTEMNAME =LO7
SAPSYSTEM=67
I NSTANCE_NAME =ASCS67
DI R_CT_RUN =$( DI R_EXE_ROOT) / r un
DI R_EXECUTABLE =$( DI R_I NSTANCE) / exe
SAPLOCALHOST = ascsl o7
DI R_PROFI LE = $( DI R_I NSTALL) / pr of i l e
_PF = $( DI R_PROFI LE) / LO7_ASCS67_ascsl o7
Post-SAP Installation Steps
120 Installation Guide for SAP Solutions
SETENV_00 =LD_LI BRARY_PATH=$( DI R_LI BRARY) : %( LD_LI BRARY_PATH)
SETENV_01 =SHLI B_PATH=$( DI R_LI BRARY) : %( SHLI B_PATH)
SETENV_02 =LI BPATH=$( DI R_LI BRARY) : %( LI BPATH)
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# Copy SAP Execut abl es
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
_CPARG0 =l i st : $( DI R_CT_RUN) / scs. l st
Execut e_00 =i mmedi at e $( DI R_CT_RUN) / sapcpe$( FT_EXE) pf =$( _PF)
$( _CPARG0)
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# St ar t SAP messagi ng ser vi ce
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
_MS = ms. sap$( SAPSYSTEMNAME) _$( I NSTANCE_NAME)
Execut e_01 =l ocal r m- f $( _MS)
Execut e_02 =l ocal l n - s - f $( DI R_EXECUTABLE) / msg_ser ver $( FT_EXE) $( _MS)
St ar t _Pr ogr am_00 =l ocal $( _MS) pf =$( DI R_PROFI LE) / LO7_ASCS67_ascsl o7
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# St ar t SAP l ocki ng ser vi ce
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
_EN = en. sap$( SAPSYSTEMNAME) _$( I NSTANCE_NAME)
Execut e_03 =l ocal r m- f $( _EN)
Execut e_04 =l ocal l n - s - f $( DI R_EXECUTABLE) / enser ver $( FT_EXE) $( _EN)
St ar t _Pr ogr am_01 =l ocal $( _EN) pf =$( DI R_PROFI LE) / LO7_ASCS67_ascsl o7
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
- r w- r - - - - - 1 p11admsapsys 4818 2006- 06- 12 . dbenv_dbp11. csh
l r wxr wxr wx 1 p11admsapsys 16 2006- 06- 19 . dbenv_dbp11- se. csh
- > . dbenv_dbp11. csh
l r wxr wxr wx 1 p11admsapsys 15 2006- 06- 19 . dbenv_dbp11- se. sh
- > . dbenv_dbp11. sh
- r w- r - - - - - 1 p11admsapsys 4785 2006- 06- 12 . dbenv_dbp11. sh
- r w- r - - - - - 1 p11admsapsys 4818 2006- 06- 19 . dbenv_j 76p11. csh
- r w- r - - - - - 1 p11admsapsys 4786 2006- 06- 19 . dbenv_j 76p11. sh
- r w- r - - - - - 1 p11admsapsys 4818 2006- 06- 19 . dbenv_j cp11. csh
- r w- r - - - - - 1 p11admsapsys 4786 2006- 06- 19 . dbenv_j cp11. sh
- r w- r - - - - - 1 p11admsapsys 4818 2006- 06- 19 . dbenv_scsp11. csh
- r w- r - - - - - 1 p11admsapsys 4786 2006- 06- 19 . dbenv_scsp11. sh
- r w- r - - - - - 1 p11admsapsys 757 2006- 06- 19 . j 2eeenv_j 76p11. csh
- r w- r - - - - - 1 p11admsapsys 825 2006- 06- 19 . j 2eeenv_j 76p11. sh
- r w- r - - - - - 1 p11admsapsys 757 2006- 06- 09 . j 2eeenv_j cp11. csh
Post-SAP Installation Steps
Installation Guide for SAP Solutions 121
- r w- r - - - - - 1 p11admsapsys 825 2006- 06- 09 . j 2eeenv_j cp11. sh
- r w- r - - - - - 1 p11admsapsys 757 2006- 06- 09 . j 2eeenv_scsp11. csh
- r w- r - - - - - 1 p11admsapsys 825 2006- 06- 09 . j 2eeenv_scsp11. sh
l r wxr wxr wx 1 p11admsapsys 20 2006- 06- 19 . sapenv_dbp11. csh
- > . sapenv_dbp11- se. csh
- r w- r - - - - - 1 p11admsapsys 8325 2006- 06- 09 . sapenv_dbp11- se. csh
- r w- r - - - - - 1 p11admsapsys 7693 2006- 06- 09 . sapenv_dbp11- se. sh
l r wxr wxr wx 1 p11admsapsys 19 2006- 06- 19 . sapenv_dbp11. sh
- > . sapenv_dbp11- se. sh
- r w- r - - - - - 1 p11admsapsys 8325 2006- 06- 19 . sapenv_j 76p11. csh
- r w- r - - - - - 1 p11admsapsys 7693 2006- 06- 19 . sapenv_j 76p11. sh
- r w- r - - - - - 1 p11admsapsys 8325 2006- 06- 09 . sapenv_j cp11. csh
- r w- r - - - - - 1 p11admsapsys 7693 2006- 06- 09 . sapenv_j cp11. sh
- r w- r - - - - - 1 p11admsapsys 8325 2006- 06- 09 . sapenv_scsp11. csh
- r w- r - - - - - 1 p11admsapsys 7693 2006- 06- 09 . sapenv_scsp11. sh
- r w- r - - - - - 1 pl 1admsapsys 1322 2006- 06- 19 . sapsr c_j 76p11. csh
- r w- r - - - - - 1 pl 1admsapsys 1118 2006- 06- 19 . sapsr c_j 76p11. sh
- r w- r - - - - - 1 pl 1admsapsys 1322 2006- 06- 09 . sapsr c_j cp11. csh
- r w- r - - - - - 1 pl 1admsapsys 1118 2006- 06- 09 . sapsr c_j cp11. sh
- r w- r - - - - - 1 p11admsapsys 1322 2006- 06- 09 . sapsr c_scsp11. csh
- r w- r - - - - - 1 p11admsapsys 1118 2006- 06- 09 . sapsr c_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/ <si d>adm
After installation, rename the installed . *_<phys host name>. *sh to
*_ci <si d>. *sh (not valid for WebAS 6.40 JAVA only), j 2eeenv_xxx. * and
*J C<I D>_j c<si d>(only valid for WebAS 6.40 JAVA) files as well.

Post-SAP Installation Steps
122 Installation Guide for SAP Solutions

● / sapmnt / <SI D>/ pr of i l e
Change the profile name from *_DVEBMGS<I D>_<phys_host name>to
*_DVEBMGS<I D>_ci <si d>. (not valid for 6.40 JAVA only).
Change the profile name from *_SCS<I D>_< phys_host name>to
*_SCS<I D>_scs<si d>.

● WebAS 6.40 ABAP + JAVA-AddIn
Change the host name to ci <si d>in DEFAULT. PFL and in the CI start profile. Set
DBHOSTNAME=db<si d>- se. Set SAPLOCALHOST=ci <si d>in the CI profile.
Change the host name to scs<si d>in the SCS start profile. Set
SAPLOCALHOST=scs<si d>in the SCS profile.
Set SAPLOCALHOST=app<i d><si d>in every application instance profile.
● WebAS 6.40 JAVA:
Change the SAPJDBHOST and j2ee/dbhost to db<si d>- se in the DEFAULT. PFL.
Change the host name in the SCS start profile to scs<si d>.
Set the SAPLOCALHOST=scs<si d>in the SCS profile.
Set the SAPLOCALHOST=j c<si d>in the JC profile.
Post-SAP Installation Steps
Installation Guide for SAP Solutions 123
Set the SAPLOCALHOST=j <i d><si d>in every application instance profile.

DEFAULT.PFL (WebAS 6.40 ABAP + JAVA-AddIn):
bash- 2. 03#cat DEFAULT.PFL

SAPGLOBALHOST =ci os4
SAPDBHOST =dbos4- se
r di sp/ mshost = ci os4
SAPSYSTEMNAME =OS4
r di sp/ accept _r emot e_t r ace_l evel =0
r di sp/ sna_gat eway =ci os4
r di sp/ sna_gw_ser vi ce =sapgw67
r sl g/ col l ect _daemon/ l i st en_por t =3967
r sl g/ col l ect _daemon/ t al k_por t =4067
r di sp/ buf r ef mode =sendon, exeaut o
ms/ ser ver _por t _0 =PROT=HTTP, PORT=8167
dbs/ or a/ t nsname = OS4
DI R_CLI ENT_ORAHOME = / or acl e/ OS4/ 920_64
DI R_SERVER_ORAHOME = / or acl e/ OS4/ 920_64
j 2ee/ dbname = OS4
j 2ee/ dbt ype = or a
j 2ee/ dbhost = dbos4- se

DEFAULT.PFL (WebAS 6.40 JAVA):
bash- 2. 03#cat DEFAULT.PFL

SAPSYSTEMNAME =OLI
SAPJ DBHOST =dbol i - se
j 2ee/ dbname = OLI
j 2ee/ dbt ype = or a
j 2ee/ dbhost = dbol i - se

Start profile (e.g. START_SCS68_scsos4):
bash- 2. 03#cat START_SCS68_scsos4
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# Gl obal var i abl es
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SAPSYSTEMNAME =OS4
I NSTANCE_NAME =SCS68
DI R_EXECUTABLE =/ usr / sap/ OS4/ SYS/ exe/ r un
DI R_LI BRARY = / usr / sap/ OS4/ SYS/ exe/ r un

#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Post-SAP Installation Steps
124 Installation Guide for SAP Solutions
# St ar t SAP messagi ng ser vi ce
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
_MS = ms. sapOS4_SCS68
Execut e_00 =l ocal r m- f $( _MS)
Execut e_01 =l ocal l n - s - f $( DI R_EXECUTABLE) / msg_ser ver $( _MS)
St ar t _Pr ogr am_00 =l ocal $( _MS) pf =$( DI R_PROFI LE) / OS4_SCS68_scsos4

#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# St ar t SAP l ocki ng ser vi ce
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
_EN = en. sapOS4_SCS68
Execut e_02 =l ocal r m- f $( _EN)
Execut e_03 =l ocal l n - s - f $( DI R_EXECUTABLE) / enser ver $( _EN)
St ar t _Pr ogr am_01 =l ocal $( _EN) pf =$( DI R_PROFI LE) / OS4_SCS68_scsos4

Instance Profile (e.g. OS4_SCS68_scsos4) :
bash- 2. 03#cat OS4_SCS68_scsos4
SAPSYSTEMNAME =OS4
SAPLOCALHOST = scsos4
SAPLOCALHOSTFULL =scsos4
I NSTANCE_NAME =SCS68
SAPSYSTEM=68
DI R_GLOBAL =/ sapmnt / OS4/ gl obal
DI R_PROFI LE = / sapmnt / OS4/ pr of i l e
DI R_EXECUTABLE =/ usr / sap/ OS4/ SYS/ exe/ r un
r di sp/ msser v = 3668
enque/ t abl e_si ze =4096
enque/ deque_wai t _answer = FALSE
enque/ pr ocess_l ocat i on =LOCAL
enque/ encni / por t =3268
r di sp/ enqname =$( r di sp/ myname)
enque/ snapshot _pck_i ds =100
ms/ ser ver _por t _0 =PROT=HTTP, PORT=8168
Adapt the J2EE Configuration Tool

For WebAS 6.40 ABAP + Java-AddIn, use the host name ci <si d>and
j c<si d>for WebAS 6.40 JAVA.


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

Post-SAP Installation Steps
Installation Guide for SAP Solutions 125
cont r ol 1: ~#ssh -X os4adm@Baby_1
os4adm@Baby_1' s passwor d:
Baby_1: os4adm38> cd / usr / sap/ OS4/ DVEBMGS67/ j 2ee/ conf i gt ool /
[ Baby_1: ol i adm38>cd / usr / sap/ OLI / J C16/ j 2ee/ conf i gt ool / ] f or WebAS
6. 40 J AVA
Baby_1: os4adm39> ./configtool.sh
Connect t o DB? Yes


Post-SAP Installation Steps
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
Type in Value: <Cust omval ue>for each line and click on Set .
to change: profile
name + host
Post-SAP Installation Steps
Installation Guide for SAP Solutions 129

Post-SAP Installation Steps
130 Installation Guide for SAP Solutions
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.
to change: profile
name + host
Post-SAP Installation Steps
Installation Guide for SAP Solutions 131

Post-SAP Installation Steps
132 Installation Guide for SAP Solutions

Post-SAP Installation Steps
Installation Guide for SAP Solutions 133

Post-SAP Installation Steps
134 Installation Guide for SAP Solutions

Adapt the J2EE Offline Configuration Tool:
cont r ol 1: ~#ssh -X os4adm@Baby_1
os4adm@Baby_1' s passwor d:
Baby_1: os4adm38> cd /usr/sap/OS4/DVEBMGS67/j2ee/configtool/
Baby_1: os4adm39> ./offlinecfgeditor.sh
Post-SAP Installation Steps
Installation Guide for SAP Solutions 135
Click on the edit key.
Click Yes and afterwards double-click the Pr oper t ysheet Instance.
doubleclick
Post-SAP Installation Steps
136 Installation Guide for SAP Solutions
Click on OK and exit.
Post-SAP Installation Steps
Installation Guide for SAP Solutions 137
Change the following files:
Baby_1: os4adm59> cd /usr/sap/OS4/DVEBMGS67/SDM/program
Baby_1: os4adm63> vi localsdmgui.properties

wor ki ngHost =ci os4
wor ki ngDi r ect or y=/ usr / sap/ OS4/ DVEBMGS67/ SDM/ pr ogr am
wor ki ngPor t =50118
wor ki ngFr ogTheme=Br i ght Har moni c
wor ki ngLookAndFeel =com. sap. pl af . f r og. Fr ogLookAndFeel
~
~

Baby_1: os4adm64> cd config

Baby_1: os4adm66> vi sdmrepository.sdc
</ Admi nPor t >
<Host >
scsos4
</ Host >
<Root Di r >
/ usr / sap/ OS4/ DVEBMGS67/ SDM/ r oot
</ Root Di r >
<MaxBackups>
10
</ MaxBackups>
<Cur r ent Backup>
6
</ Cur r ent Backup>
<Cur r ent Fl owBackup>
8
</ Cur r ent Fl owBackup>
<HashedPasswor d>
yPLDEBe3oOb6H2mmj J 0zzt Ogw/ A=
</ HashedPasswor d>
<J St ar t up- Conf i gur at i on act i ve="t r ue">
<mshost >
scsos4
</ mshost >
<mspor t >
3600

: wq
Change hosts and directory.
Post-SAP Installation Steps
138 Installation Guide for SAP Solutions
14.3 Start Script startdb for Oracle and
SAPDB/MaxDB
The database (Oracle, SAPDB/MaxDB) is not started implicitly with the st ar t sap (and
st ar t db) standard script in the exe/ r un directory, but separately using the service
script from SAP. In sapdb, the standard script st ar t db/ st ar t j 2eedb is called.
Thanks to the automount mechanism, the exe/ r un directory is also available on the
database node.
14.4 Stop Script stopdb for Oracle and
SAPDB/MaxDB
The remarks on the start script st ar t db made in the previous section apply to the
st opdb 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 r emsh on your systems, you have to set the profile
parameter gw/ r emsh (or dt a/ r emsh/ 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 whi ch 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:
whi ch <pr ogr am_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 <si d>admmust have execute permission (‘x’) for the programs.
Change the parameter gw/ r emsh in every instance profile to / usr / bi n/ ssh (Linux) or
to / opt / SMAWPl us/ bi n/ ssh (Solaris8) or / usr / bi n/ ssh (Solaris9). To check
whether the program ssh is located, issue the whi ch command.
Post-SAP Installation Steps
Installation Guide for SAP Solutions 139
SSH Configuration:
The host the job is running on must have permission to start programs on the remote
host.
Baby_1: oacadm60%ssh-keygen -t rsa
Gener at i ng publ i c/ pr i vat e r sa key pai r .
Ent er f i l e i n whi ch t o save t he key ( / home_sap/ oacadm/ . ssh/ i d_r sa) :
Cr eat ed di r ect or y ‘ / home_sap/ oacadm/ . ssh
Ent er passphr ase ( empt y f or no passphr ase) :
Ent er same passphr ase agai n:
Your i dent i f i cat i on has been saved i n / home_sap/ oacadm/ . ssh/ i d_r sa. pub.
Your publ i c key has been saved i n / home_sap/ oacadm/ . ssh/ i d_r sa. pub.
The key f i nger pr i nt i s:
ea: 46: 0a: 17: e5: e9: 39: 54: c9: e8: 10: b0: d6: 84: c3: ce oacadm@Baby_1
Baby_1: oacadm61%cd .ssh
Baby_1: oacadm62%ls
i d_r sa. pub i d_r sa
Baby_1: oacadm63%cp –p id_rsa.pub authorized_keys

Baby_1: oacadm64%chmod 700 /home_sap/oacadm
Baby_1: oacadm65%chmod 700 /home_sap/oacadm/.ssh

14.6 Profile Parameters for DEFAULT.PFL
Example for “SID = O12” and “system number = 12”:
SAPSYSTEMNAME =O12
SAPDBHOST =dbo12- se
r di sp/ mshost = ci o12
r di sp/ sna_gat eway =ci o12
r di sp/ sna_gw_ser vi ce =sapgw12
r di sp/ vbname = ci o12_O12_12
dbs/ or a/ t nsname = O12
r di sp/ enqname =ci o12_O12_12
r di sp/ bt cname =ci o12_O12_12
r sl g/ col l ect _daemon/ l i st en_por t =3912
r sl g/ col l ect _daemon/ t al k_por t =4012
r di sp/ buf r ef mode =sendon, exeaut o

Post-SAP Installation Steps
140 Installation Guide for SAP Solutions
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):
START_D62_mhm305
O12_D62_mhm305
START_DVEBMGS12_mhm305
O12_DVEBMGS12_mhm305
Profile names (virtual installation):
START_D62_app62o12
O12_D62_app62o12
START_DVEBMGS12_ci o12
O12_DVEBMGS12_ci o12
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 <si d>
ABAP central services instance: ascs<si d>
Application instance: app<i d><si d>
Syntax for the host name (JAVA)
Java Control instance: j c<si d>
SAP common services: scs<si d>
Java application instance: j <i d><si d>
Example for a Central Instance with “SID = CB1”:
SAPLOCALHOST = ci cb1
Example for an Application Instance with “instance number = 01” and “SID = CB1”:
SAPLOCALHOST = app01cb1
Post-SAP Installation Steps
Installation Guide for SAP Solutions 141
Enable Memory Auto Management
Please check the parameters according to SAP Note 386605:
es/ i mpl ement at i on =map
PHYS_MEMSI ZE = 50%
The following profile parameters have to be disabled after this:
em/ max_si ze_MB = 1024
em/ i ni t i al _si ze_MB = 1024
em/ addr ess_space_MB = 1024
em/ bl ocksi ze_KB = 1024
em/ st at _l og_si ze_MB = 20
em/ st at _l og_t i meout = 600
r di sp/ ROLL_SHM = 128
r di sp/ ROLL_MAXFS = 32768
r di sp/ PG_SHM = 0
r di sp/ PG_MAXFS = 2048
zt t a/ r ol l _f i r st = 1024
zt t a/ r ol l _ar ea = 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
st ar t sap and st opsap are now located in the / usr / sap/ <si d>/ SYS/ exe/ r un
directory. For this reason, the aliases st ar t sap and st opsap, as well as the st ar t sap
<host name>_<sysnr >and st opsap_<host name>_<sysnr >start and stop scripts in
/ home/ <si d>admexist 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 st ar t sap_<host name>_<i nr >and
st opsap_<host name>_<i nr >scripts from $HOME of <si d>adm. They are both
replaced by a single new script.
Post-SAP Installation Steps
142 Installation Guide for SAP Solutions
Comment out the lines for the aliases st ar t sap and st opsap in the . sapenv_*. csh
scripts:
set host name=`host name`
# 12. 08. 02
#unset l i st
#set l i st =`$l scommand $HOME | gr ep ' ^st ar t sap_' ${host name}' _[ 0- 9]
[ 0- 9] $' `
#i f ( `echo $l i st | wc - w` == 1 ) t hen
# al i as st ar t sap $HOME/ $l i st
#el se
# al i as st ar t sap "echo ' To st ar t an i nst ance use one of t he f ol l owi ng
scr i pt s:
#endi f
#
#unset l i st
#set l i st =`$l scommand $HOME | gr ep ' ^st opsap_' ${host name}' _[ 0- 9] [ 0- 9] $' `
#i f ( `echo $l i st | wc - w` == 1 ) t hen
# al i as st opsap $HOME/ $l i st
#el se
# al i as st opsap "echo ' To st op an i nst ance use one of t he f ol l owi ng
scr i pt s: ' ;
#endi f
#
# end SAP R/ 3 Envi r onment
Place the st ar t sap and st opsap scripts of release 6.x in the / sapmnt / <si d>/ exe
directory.

Make sure that all the permissions of the SAP kernel in this directory are set to
<si d>adm: sapsys. After changing the rights with chown
<si d>adm: sapsys_*, start the sapr oot . sh <si d>script.

The new scripts should look like this:
#! / bi n/ sh
#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#
# NAME :
# st ar t sap
#
# PURPOSE :
# St ar t SAP Dat abase and SAP I nst ances
#
# USAGE: st ar t sap [ db| r 3| al l | check] [ <i nst ance>]
#
# Speci f y i nst ance i f you have i nst al l ed mul t i pl e
Post-SAP Installation Steps
Installation Guide for SAP Solutions 143
# i nst ances of t he same syst emon one host .
# Exampl e: st ar t sap r 3 DVEBGMS00
#
# ot her opt i onal par amet er s:
# check Check Dat abase and SAP I nst ance
# r 3 | R3 St ar t SAP I nst ance onl y
# db | DB | dB | Db St ar t Dat abase onl y
# ALL | al l St ar t Dat abase and SAP I nst ance

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
<host name>_<si d>_<i nr >. Instead, static routes may also be entered on the
Application Nodes; however, this would make it necessary to enable IP forwarding.
Post-SAP Installation Steps
144 Installation Guide for SAP Solutions

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

Logon group “PUBLIC”.
Post-SAP Installation Steps
Installation Guide for SAP Solutions 145

Enter the virtual IP address of the Client LAN.
Post-SAP Installation Steps
146 Installation Guide for SAP Solutions
14.12 SAPROUTER on the Control Node
The sapr out er (/ Fl exFr ame/ vol FF/ Fl exFr ame/ sapr out er ) routes the nodes
from the workstation network 100. 10. 100. * to the Client LAN of the virtual SAP
Services:
/ Fl exFr ame/ vol FF/ Fl exFr ame/ sapr out er / sapr out t ab
#
# f r om t o ser vi ce
#
# wor kst at i on- l an cl i ent - l an
P 100. 10. 100. * 10. 0. 190. * *
If the virtual host names are entered in sapl ogon instead of the IP addresses, the
names have to be resolved on the sapr out er :
Hosts in LDAP
10. 0. 190. 111 ci bw1
10. 0. 190. 101 ci cb1
10. 0. 190. 102 app01cb1
10. 0. 190. 103 app02cb1
Services in LDAP
sapdp01 3201/ t cp # SAP Syst emDi spat cher Por t
sapdp02 3202/ t cp # SAP Syst emDi spat cher Por t
sapmsCB1 3600/ t cp # SAP Syst emMessage Por t
sapdp20 3220/ t cp # SAP Syst emDi spat cher Por t
SAP System Administration
Installation Guide for SAP Solutions 147
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 <si d>adm
with st ar t sap, 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.

15.2.1.1 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
saper s Starting and stopping Enqueue Replicated Server
sapj Starting and stopping a J2EE application instance
sapj c Starting and stopping the J2EE central instance
SAP System Administration
148 Installation Guide for SAP Solutions
Script name Application
sapl c Starting and stopping LiveCache
sapscs Starting and stopping the SAP common services

The call syntax for sapascs, sapci , sapdb, sapl c and sapscs is:
<sci pt _name> <si d> <act i on> [ nosi gnal ]
The call syntax for sapapp, saper s and sapj is:
<sci pt _name> <i d> <si d> <act i on> [ nosi gnal ]

The call parameters are:
● <i d>
Distinction of several similar instances of a service type of an SID; 2 digits,
numerical.
● <si d>
System ID (SID), 3-digit, in lower case.
● <act i on>
The action to be performed with the application or service. The actions are st ar t ,
st op, r est ar t , st at us, cl eanup, wat ch and nowat ch.
● Nosi gnal
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 <Appl i cat i on_Node_name> sapapp <i d> <si d> <act i on> [ nosi gnal ]
Example
The application server of the system CB1 with the ID 01 is to be started on the node
bl ade3; let us assume that the Control Node is cont r ol 1.
Execute the following as r oot in the command shell of cont r ol 1:
cont r ol 1 #ssh blade3 sapapp 01 cb1 start
SAP System Administration
Installation Guide for SAP Solutions 149
15.2.1.2 SAP Service Script Actions
● st ar t
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 (i f conf i g <i f c> <i p- adr > net mask <net mask>
up). The application is started and the service control file is written.
● st op
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 ( i f conf i g <i f c> down).
● st at us
This checks the logical status of the application or service. The functional availability
is not tested.
● r est ar t
This merges the actions st op, cl eanup and st ar t in one call; r est ar t is
intended for restarting a malfunctioning application.
● cl eanup
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.
● nowat ch
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'.
● wat ch
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.
SAP System Administration
150 Installation Guide for SAP Solutions
15.2.1.3 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 sapser vi ce_f unct i ons file:
#=================================================================
# common exi t codes f or ser vi ce scr i pt s
#
no_er r or =0 #Bi t 0,
wr ong_par amet er _count =1 #Bi t 1, wr ong number of par amet er s
pl ausi bi l i t y_er r or =2 #Bi t 2, pl ausi bi l i t y er r or
i nt er f ace_ser ver _l an_er r or =4 #Bi t 3, er r or at ser ver l an i nt er f ace
up/ down
i nt er f ace_cl i ent _l an_er r or =8 #Bi t 4, er r or at cl i ent l an i nt er f ace
up/ down
any_er r or =32 #Bi t 5, any ot her er r or
san_mount _er r or =64 #Bi t 6, san mount er r or
user _scr i pt _er r or =128 #Bi t 7, user scr i pt er r or

# r ul e i s l ogi cal OR:
# l et exi t _code="exi t _code| new_exi t _code"
# i f [ `expr $exi t _code&4` - eq 4 ] ; t hen . . . . . .
# i f [ `l et xxx="$r c & 4"; echo $xxx` - ne 4 ] ; t hen . . .
#=================================================================
15.2.1.4 Joined SAP Service Scripts
The following scripts are provided for jointly starting and stopping applications and
services:
Script name Application Place of execution
st ar t _al l _sapser vi ces Initial start of all
configured applications
Only on a Control
Node
st op_al l _sapser vi ces Stopping of all active
applications
Only on a Control
Node
st op_al l _sapser vi ces_SI D Stopping of all active
applications of one SID
Only on a Control
Node
st op_al l _sapser vi ces_l ocal Stopping of all active
applications on the local
node
Only on an Application
Node

These scripts are called with call parameters.
To enable graceful shutdown of the node, the script st op_al l _sapser vi ces_l ocal
can be appended in the relevant run levels:
SAP System Administration
Installation Guide for SAP Solutions 151
# St op al l sapser vi ces

/ et c/ r c. d/ r c3. d # l n - s / Fl exFr ame/ scr i pt s/ st op_al l _sapser vi ces_l ocal
K02mySAP
/ et c/ r c. d/ r c5. d # l n - s / Fl exFr ame/ scr i pt s/ st op_al l _sapser vi ces_l ocal
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 nowat ch when the application is started.
Examples:
The central instance of BW1 is to be started without monitoring by the high-availability
software:
bl ade1 # sapci bw1 start nowatch
or from a Control Node:
cont r ol 1 #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 wat ch 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:
bl ade1 # sapci bw1 watch
or from a Control Node:
cont r ol 1 #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.
SAP System Administration
152 Installation Guide for SAP Solutions
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 f f _sap_shadowpor t . 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
<si d>users to the new group sapinst.
Example for group sapinst:
dn: cn=sapi nst , ou=Gr oup, ou=p1, ou=Pool s, ou=Fl exFr ame, dc=f f 32, dc=wdf , dc=f sc
, dc=net
obj ect Cl ass: t op
obj ect Cl ass: posi xGr oup
cn: sapi nst
user Passwor d: : eA==
gi dNumber : 3606
member Ui d: or asm2
member Ui d: 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:
LDI FI N=/ t mp/ l dapi n
r m$LDI FI N
echo "dn: cn=sapi nst , ou=Gr oup, ou=pool 1, ou=Pool s, ou=Fl exFr ame,
dc=j er , dc=f uj i t su- si emens, dc=com" >>$LDI FI N
echo "obj ect Cl ass: t op" >> $LDI FI N
echo "obj ect Cl ass: posi xGr oup" >>$LDI FI N
echo "gi dNumber : 1234" >> $LDI FI N
echo "user Passwor d: l eer " >>$LDI FI N
echo "cn: sapi nst " >>$LDI FI N

ldapmodify -x -D"cn=root,ou=LDAPadmins,ou=FlexFrame,
dc=jer,dc=fujitsu-siemens,dc=com" -w <yourPassword> -f $LDIFIN
SAP System Administration
Installation Guide for SAP Solutions 153
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/ <SI D>/ t r ans:
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 (<SI D> of Primary Domain Controller):
● Change DI R_TRANS to / usr / sap/ <SI D>/ t r ans
● Change DI R_EPS_ROOT to / usr / sap/ <SI D>/ t r ans/ EPS
Transport Management System:
● Change TRANSDI R to / usr / sap/ <SI D>/ t r ans
15.5 Printing in FlexFrame
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.
SAP System Administration
154 Installation Guide for SAP Solutions
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 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.
15.5.3.1 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.
SAP System Administration
Installation Guide for SAP Solutions 155
15.5.3.2 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)
15.5.3.3 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
SAP System Administration
156 Installation Guide for SAP Solutions
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.
BRBACKUP and SAPDBA/BRCONNECT
Installation Guide for SAP Solutions 157
16 BRBACKUP and
SAPDBA/BRCONNECT
When br backup is started for offline backup, it first stops the database with the
shut down i mmedi at e command. As the FA Agent recognizes that the Oracle
processes are missing, it will, by default, restart the database. The br connect 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 nowat ch and wat ch 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 / Fl exFr ame/ scripts
Implementation
Before starting the offline backup, the script sapdb should be called as user root with
arguments:
sudo / Fl exFr ame/ scr i pt s/ sabdb<SI D>nowat ch
When the backup is finished, the script sapdb should be called as user root with
arguments:
sudo / Fl exFr ame/ scr i pt s/ sabdb<SI D>wat ch
Calling script sapdb is also possible as <si d>admor for Oracle as or a<si d>user,
but then it has to be called with absolute path name.
BRBACKUP and SAPDBA/BRCONNECT
158 Installation Guide for SAP Solutions
16.2 Solution 2 for Oracle
This solution uses the options nowat ch and wat ch 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 br backup by
using the functionality meant for Oracle Fail Safe.
Requirements
● br - t ool s must be at least version 620 patch level 124
● Current SAP Service scripts in / Fl exFr ame/ scr i pt s
● group dba in LDAP must have or a<si d>as member of the group
Implementation
The following environment variables must set for <si d>admand or a<si d>users:
BR_OFS=1
FSCMD_CMD=/ Fl exFr ame/ scr i pt s/ sapbr backup

When the br backup is started directly, called from SAPDBA or a DB13 transaction, it
calls the script sapbr backup to shut down and start up the database, and the
sapbr backup will take care of calling sapdb with the nowat ch or wat ch option.
Known limitations
● works only with Oracle databases
● br backup needs to be version 620 even if using 4.6X kernel

Troubleshooting
Installation Guide for SAP Solutions 159
17 Troubleshooting
● Environment of <si d>admand or a<si d>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:
. cshr c
. sapenv_ci <si d>. csh
. sapenv_ci <si d>. sh
. dbenv_ci <si d>. csh
. dbenv_ci <si d>. sh
. sapenv_db<si d>- se. csh
. sapenv_db<si d>- se. sh
. dbenv_db<si d>- se. csh
. dbenv_db<si d>- se. sh

● When an application server is started, the following error message is issued:
Cent r al - I nst ance CB1 i s not r unni ng, pl ease st ar t i t f i r st .
/ Fl exFr ame/ scr i pt s/ sapapp done
exi t _code2

The log files under / Fl exFr ame/ scr i pt s/ l og are missing, as a result of which
the server does not know that a CI is already running.

● Account sdb is not locked (MaxDB 7.5, Solaris only)
During the preparation phase of the Database Kernel package you can get the
following messages:
WRN: changi ng sdb admi ni st r at or s gr oup …

Account sdb i s not l ocked, t hi s i s a secur i t y l eak
There are two workarounds to avoid the problem.
Solution 1:
Make the application image writetable and create the user sdb and the group sdba
locally. The necessary UID and GUID you can get from LDAP by get ent passwd |
gr ep sdb and get ent gr oup | gr ep sdba. You can create it using Solaris
admintool. After the installation you should withdraw your modifications.
Solution 2:
Set the password of user sdb in LDAP to *l k*.

Installation Guide for SAP Solutions 161
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
NIC Network Interface Card
Abbreviations
162 Installation Guide for SAP Solutions
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
SPOC Single Point Of Control
Abbreviations
Installation Guide for SAP Solutions 163
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 165
19 Glossary
Adapti ve 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 , agat e, wgat e, 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.
Glossary
166 Installation Guide for SAP Solutions
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, t f t p, l dap 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.
Glossary
Installation Guide for SAP Solutions 167
FlexFrame
TM
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 / bi n/ host name.
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".
Glossary
168 Installation Guide for SAP Solutions
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.
Glossary
Installation Guide for SAP Solutions 169
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.
Glossary
170 Installation Guide for SAP Solutions
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, agat e, wgat e 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.


Installation Guide for SAP Solutions 171
20 Index
A
Application Nodes released 12
ASCS ABAP central service
instance 53
B
BRBACKUP 157
C
configuration
interfaces 23
SAN 29
service status path server 22
virtual host name for Web AS 6.40
ABAP and JAVA-AddIn / WebAS
6.40 JAVA 121
virtual host name manually 113
configuring the virtual host name for
Web AS 6.40 ABAP and JAVA-AddIn
/ WebAS 6.40 JAVA 121
D
database
in general 37
description of Web AS 6.40 JAVA 70
document history 2
F
FA agents 17
ff_scripts 40, 46
FlexFrame installation diagram 9
G
gathering SAP services information 8
H
host names 25
hot links for FlexFrame 4
I
installation
NetWeaver 7.0SR1/SR2 89
Oracle 10.1 41
Oracle 10.2 43
Oracle 9.2 40
SAP 4.6C SR2 55
SAP solutions 90
SAPDB / MaxDB 43
Web AS 6.20 61
Web AS 6.20 with sapinst 61
Web AS 6.40 with NetWeaver04
SR1 69
with database DB2 47
IP addresses used in this document 3
M
MaxDB 45, 56, 157
N
notational conventions 2
O
online software service 13
operating system
in general 31
Linux 34
Solaris 8/9 31
Index
172 Installation Guide for SAP Solutions
ora<sid> 40, 46
Oracle 56, 157, 158
ORACLE 40, 46
OSS network connection
with dedicated saprouter server 13
without dedicated saprouter
server 14
overview 7
P
Post-SAP installation steps 113
preparations 8
pre-SAP installation steps 27
printing in FlexFrame 153
profile parameters for 139
profile parameters for the instance
profile 140
profile parameters for the start
profile 140
R
related documents 2
related SAP notes 15
RPM 36
S
SAP in general 53
SAP installation steps
overview 1
SAP Java cryptographic toolkit 53
SAP license 143
SAP release upgrade 152
SAP service connection 13
SAP service scripts 19
SAP start and stop mechanism
(Release 4.6CSR2) 141
SAP system administration 147
SAPDB 56, 157
SAPDBA 157
SAPLogon – SAPGUI 143
SAPROUTER on the Control
Node 146
software administration 147
start script 138
starting a configuration 20
stop script 138
T
TNS listener for Oracle 37
transport directory 153
troubleshooting 159
U
upgrading application software 147
V
virtualization of SAP services 7
W
Web AS 6.40 ABAP + JAVA-AddIn
NetWeaver04SR1 82
Web AS 6.40 application server JAVA-
AddIn 87
Web AS 6.40 NetWeaver04SR1 ABAP
Oracle 77
Web AS 6.40 NetWeaver04SR1 JAVA
MaxDB/Oracle 71

Installation Guide for SAP Solutions 173


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 …@ts.fujitsu.com.
The Internet pages of Fujitsu Technology Solutions are available at
http://ts.fujitsu.com/...
and the user documentation at http://manuals.ts.fujitsu.com.
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 …@ts.fujitsu.com.
Die Internetseiten von Fujitsu Technology Solutions finden Sie unter
http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die
Benutzerdokumentation.
Copyright Fujitsu Technology Solutions, 2009

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close