Installation Guide for SAP Solutions - Fujitsumanuals.ts.fujitsu.com/file/10480/FF51A00_SAP_Installation_Guide.pdf · 21.2 Software Administration ... 1 Introduction ®®, FlexFrame™

FlexFrame™ for SAP®

Version 5.1A

Installation Guide for SAP Solutions

Edition January 2013 Document Version 1.7

Fujitsu Limited

© Copyright Fujitsu Technology Solutions 2011

FlexFrame™ and PRIMERGY™ are trademarks or registered trademarks of Fujitsu Limited in

Japan and other countries.

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

Oracle™ and Java™ are trademarks of ORACLE Corporation and/or its affiliates

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® and the Network Appliance

® logo are registered trademarks and Network

Appliance™ and Data ONTAP™ are trademarks of NetApp, Inc. in the U.S. and other

countries.

EMC®, CLARiiON

®, Symmetrix

® and Celerra™ are trademarks or registered trademarks of

EMC Corporation in the United States and other countries

VMware®, ESX

®, ESXi, VMware vCenter, VMware vSphere are registered trademarks or

trademarks of VMware, Inc. in the United States and/or other jurisdictions.

Ethernet® is a registered trademark of XEROX, Inc., Digital Equipment Corporation and Intel

Corporation

Windows® and Word

® are registered trademarks of Microsoft Corporation

All other hardware and software names used are trademarks of their respective companies.

All rights, including rights of translation, reproduction by printing, copying or similar methods,

in part or in whole, are reserved.

Offenders will be liable for damages.

All rights, including rights created by patent grant or registration of a utility model or design,

are reserved.

Delivery subject to availability. Right of technical modification reserved.

Contents


Contents

1 Introduction ..................................................................................................... 1 1.1 Purpose of this Document ................................................................................. 1 1.2 General Usage of SAP Installation Guide During Installation ............................ 1 1.3 Special Hints for FlexFrame .............................................................................. 1 1.4 Overview ........................................................................................................... 2 1.5 Notational Conventions ..................................................................................... 2 1.6 Document History .............................................................................................. 2 1.7 Related Documents ........................................................................................... 4 1.8 Hotlinks for FlexFrame ...................................................................................... 4

2 Getting Started ................................................................................................ 7 2.1 FlexFrame ......................................................................................................... 7 2.2 Virtualization of SAP Services ........................................................................... 8 2.3 Preparations ...................................................................................................... 8 2.4 Gathering SAP Services Information ................................................................. 8 2.5 Supported Hardware for Application Nodes ...................................................... 9

3 SAP Service Connection............................................................................... 11 3.1 OSS Network Connection with Dedicated saprouter Server ........................... 11 3.2 OSS Network Connection without Dedicated saprouter Server....................... 12 3.3 Related SAP Notes ......................................................................................... 13

4 FA Agents ...................................................................................................... 15

5 SAP Service Scripts for Virtualizing Applications ...................................... 17 5.1 Starting a Configuration ................................................................................... 17 5.2 Configuring the Service Status Path ................................................................ 19 5.3 Configuring the Interfaces ............................................................................... 21 5.4 Host Names..................................................................................................... 22

6 Operating System in General ....................................................................... 25 6.1 Linux ................................................................................................................ 25

7 Preparations for Database Installation ........................................................ 27 7.1 SAP Installation with Database DB2 ............................................................... 27 7.1.1 Software Requirements ................................................................................... 27 7.1.2 Pre-Installation Steps ...................................................................................... 28 7.2 Mount Options ................................................................................................. 28 7.2.1 Database files (sapdata, saplog) ..................................................................... 29 7.2.2 Binaries and Configuration files ....................................................................... 29

Contents


8 Preparations for SAP Installation ................................................................. 31 8.1 General ............................................................................................................ 31 8.2 How to configure the interfaces manually ........................................................ 33 8.3 ASCS ABAP Central Service Instance in General ........................................... 33 8.4 SAP Java Cryptographic Toolkit ...................................................................... 34 8.5 Setting up SAP directories (Control Center) .................................................... 34 8.5.1 Standard Volumes ........................................................................................... 34 8.5.2 Specify volumes of your own ........................................................................... 35 8.5.3 SID/Poolspecific volumes ................................................................................ 35 8.5.4 Using SAN ....................................................................................................... 35 8.6 Usage of /dev/urandom ................................................................................... 36 8.7 Predefined global users ................................................................................... 37

9 SAP Installation - Overview .......................................................................... 38

10 Installing SAP 4.6C SR2 ................................................................................ 41 10.1 SAPDB / MaxDB / Oracle ................................................................................ 42 10.1.1 Installing the Central Instance (CI) .................................................................. 46

11 Installing Web AS 6.40 with NetWeaver04 SR1 ........................................... 49 11.1 Description of Web AS 6.40 JAVA ................................................................... 52 11.2 Web AS 6.40 NetWeaver04SR1 JAVA MaxDB/Oracle ................................... 53 11.2.1 SCS ................................................................................................................. 53 11.2.2 DB ................................................................................................................... 57 11.2.3 JC .................................................................................................................... 58 11.2.4 J ....................................................................................................................... 58 11.2.5 CI ..................................................................................................................... 59 11.2.6 DB ................................................................................................................... 62 11.2.7 APP ................................................................................................................. 62 11.3 Web AS 6.40 ABAP + JAVA-AddIn NetWeaver04SR1 .................................... 62 11.3.1 SCS ................................................................................................................. 62 11.3.2 DB ................................................................................................................... 63 11.3.3 CI ..................................................................................................................... 63 11.4 Web AS 6.40 Application Server JAVA-AddIn ................................................. 67

12 Installing NetWeaver 7.0SR3 ........................................................................ 69 12.1 Installation of SAP Solutions ............................................................................ 71 12.1.1 Prerequisite Checker (Linux) ........................................................................... 72 12.2 Sapinit File (Linux) ........................................................................................... 73 12.3 installsapinit.sh – symlink (Linux) .................................................................... 74 12.4 Services File (Linux) ........................................................................................ 75 12.5 NetWeaver 7.0SR3 and Oracle 10 .................................................................. 76 12.6 NetWeaver 7.0SR3 and MaxDB76 .................................................................. 77 12.7 NetWeaver 7.0SR3 MaxDB76 and SLES9_x86/SLES10_x86 ........................ 79

Contents


12.8 NetWeaver 7.0SR3 MaxDB76 ......................................................................... 80 12.9 NetWeaver 7.0SR3 and EP ............................................................................. 81 12.10 NetWeaver 7.0SR3 ABAP+JAVA-AddIn ......................................................... 83 12.11 NetWeaver 7.0SR3 JAVA only ........................................................................ 88 12.12 NetWeaver 7.01/SLES 9 ................................................................................. 88 12.13 SAP 7.0 EHP3 ................................................................................................. 89 12.13.1 Installation Media Label is wrong .................................................................... 89 12.13.2 Incompatibilities with Linux Kernel ................................................................... 89 12.14 LiveCache ....................................................................................................... 89 12.15 ERS – Enqueue Replicated Server (until NetWeaver 2004s SR3) .................. 89 12.16 Installation of SAP Solutions – Post Phase ..................................................... 91

13 Installing SAP 7.1 .......................................................................................... 92 13.1 Creating a New SID Using ff_sid_adm.pl ........................................................ 92 13.2 Service Cannot Be Started .............................................................................. 93 13.3 EHP Installer Issues ........................................................................................ 94 13.3.1 Mandatory SMD installation request ................................................................ 94 13.3.2 EHP Installer Requests Entries in /etc/services ............................................... 95 13.3.3 EHP Installer – JAVA process cannot be started ............................................ 95 13.4 ERS ................................................................................................................. 99 13.4.1 Installation hints ............................................................................................... 99 13.4.2 Post Installation Tasks (SAP 7.1 only) .......................................................... 102

14 Installing SAP 7.3 ........................................................................................ 103 14.1 Creating a New SID Using ff_sid_adm.pl ...................................................... 104 14.2 SCS/ASCS (SAP 7.3) .................................................................................... 104 14.2.1 Installation hints ............................................................................................. 104 14.3 ERS ............................................................................................................... 106 14.3.1 Installation hints ............................................................................................. 106 14.3.2 Post Installation Tasks .................................................................................. 109 14.4 SAP 7.3 EHP1 ............................................................................................... 109 14.5 SAP 7.3 – Linux kernel issue......................................................................... 110

15 Install nonclassic SAP services ................................................................. 111 15.1 BOBJ – Business Objects Enterprise ............................................................ 111 15.1.1 BOBJ – preparations ..................................................................................... 112 15.1.2 BOBJ – installation – 3.x ............................................................................... 112 15.1.3 BOBJ – Installation – 4.0 ............................................................................... 113 15.1.4 BOBJ – post installation ................................................................................ 114 15.1.5 BOBJ – Login to CMC (Central Management Console) ................................ 114 15.2 CMS – Content Server .................................................................................. 115 15.2.1 CMS – preparations ...................................................................................... 116 15.2.2 CMS – http server installation........................................................................ 116 15.2.3 CMS – installation ......................................................................................... 116 15.2.4 CMS – post installation .................................................................................. 117

Contents


15.2.5 CMS - Migration from project specific solutions ............................................ 117 15.3 MDM – Master Data Management ................................................................. 118 15.3.1 MDM – preparations ...................................................................................... 118 15.3.2 MDM – Database installation ......................................................................... 119 15.3.2.1 Oracle ............................................................................................................ 119 15.3.2.2 MaxDB ........................................................................................................... 120 15.3.2.3 DB2 ............................................................................................................... 121 15.3.3 MDM – installation ......................................................................................... 121 15.3.4 MDM – post installation ................................................................................. 122 15.3.5 MDM - Migration from project specific solutions ........................................... 122 15.4 SMD – Solution Manager Diagnostics ........................................................... 123 15.4.1 SMD - Migration from project specific solutions ............................................ 123 15.5 TREX – Search and Classification ................................................................. 124 15.5.1 TREX – preparations ..................................................................................... 124 15.5.2 TREX – installation ........................................................................................ 125 15.5.3 TREX – post installation ................................................................................ 125 15.5.4 TREX – trouble shooting................................................................................ 126 15.5.5 TREX - Migration from project specific solutions .......................................... 126

16 Database Installation ................................................................................... 128 16.1 Installation of Oracle in General .................................................................... 129 16.2 Installation of Oracle 9.2 ................................................................................ 130 16.2.1 Post-Oracle 9.2 Installation Steps ................................................................. 130 16.3 Installation of Oracle 10.2 .............................................................................. 132 16.3.1 Post-Oracle 10.2 Installation Steps ............................................................... 132 16.4 Oracle – general post installation steps ......................................................... 133 16.4.1 TNS Listener for Oracle ................................................................................. 133 16.4.2 listener.ora ..................................................................................................... 134 16.4.3 Host Name Changes in tnsnames.ora ........................................................... 135 16.4.4 Host specific /etc/oratab ................................................................................ 135 16.5 Oracle Patch Installation ................................................................................ 136 16.6 Installation of SAPDB / MaxDB ...................................................................... 136 16.6.1 XUSER .......................................................................................................... 137 16.6.1.1 Same SID on Different Platforms ................................................................... 138 16.6.2 MaxDB 7.5/7.6/7.7 /etc/opt/sdb ..................................................................... 139 16.6.3 MaxDB 7.6 ..................................................................................................... 140 16.6.4 MaxDB 7.7 ..................................................................................................... 141 16.6.5 MaxDB 7.8 ..................................................................................................... 142 16.6.6 MaxDB 7.9 ..................................................................................................... 142 16.6.6.1 MaxDB 7.9 (upgrade) - /etc/opt/sdb ............................................................... 144 16.6.7 IO Balancing .................................................................................................. 144 16.6.8 MaxDB configuration files .............................................................................. 144 16.6.9 Directories for sapdata / saplog ..................................................................... 145 16.6.10 MaxDB 7.8/7.9 – performance issue ............................................................. 145 16.7 SAP Installation with Database DB2 .............................................................. 147

Contents


16.7.1 Installing DB2 ................................................................................................ 147 16.7.2 LDAP-Plugin .................................................................................................. 148 16.7.3 Transparent LDAP ......................................................................................... 149 16.7.4 Install SAP ..................................................................................................... 150 16.7.5 Changes in System Files ............................................................................... 150 16.7.6 Post Installation Steps ................................................................................... 150 16.7.6.1 Installing DB2 License ................................................................................... 150 16.7.6.2 Modifying DB2 Catalog .................................................................................. 152 16.7.6.3 Preparations for backing up DB2 ................................................................... 153 16.7.6.4 DB2-Fixpack issues ....................................................................................... 154 16.7.7 Configuration of FA Agents ........................................................................... 154

17 Migration – SLES9 to SLES10 / SLES11 .................................................... 155

18 Post-SAP Installation Steps ....................................................................... 157 18.1 Configuring the Virtual Host Name Manually ................................................. 157 18.1.1 Central Instance (not valid for Web AS 6.40 J2EE) ....................................... 159 18.1.2 Database Instance (also valid for WebAS 6.40 J2EE) .................................. 159 18.1.3 Application Instance (not valid for WebAS 6.40 J2EE) .................................. 160 18.1.4 SCS Instance ................................................................................................ 161 18.1.5 ASCS Instance (WebAS 7.00)....................................................................... 163 18.1.6 NetWeaver 7.0 / NetWeaver 7.0SR1/SR2 ..................................................... 164 18.2 Configuring the Virtual Host Name for Web AS 6.40 ABAP and JAVA-AddIn /

WebAS 6.40 JAVA ......................................................................................................... 165 18.3 Start Script startdb for Oracle and SAPDB/MaxDB/DB2 ............................... 183 18.4 Stop Script stopdb for Oracle and SAPDB/MaxDB/DB2 ................................ 183 18.5 Scheduling of Batch Jobs (CCMS) ................................................................ 183 18.6 Profile Parameters for DEFAULT.PFL ........................................................... 184 18.7 Profile Parameters for the Start Profile .......................................................... 185 18.8 Profile Parameters for the Instance Profile .................................................... 185 18.9 SAP Start and Stop Mechanism (Release 4.6CSR2) .................................... 186 18.10 SAP License .................................................................................................. 188 18.11 SAPLogon – SAPGUI .................................................................................... 188 18.12 SAPROUTER on the Control Node ............................................................... 190 18.12.1 Configuration File for /etc/init.d/saprouter ...................................................... 190 18.12.2 Configuration File saprouter .......................................................................... 191

19 Image independent JAVA JDK ................................................................... 192 19.1 File structures and profiles ............................................................................ 192 19.2 Java Configuration Tool ................................................................................ 193 19.3 Java path settings for SDM ........................................................................... 193 19.4 Restart the services with new JAVA path ...................................................... 194

20 Usage of SAP JVM ...................................................................................... 195

Contents


21 SAP System Administration ....................................................................... 197 21.1 Upgrading Application Software .................................................................... 197 21.2 Software Administration ................................................................................. 197 21.2.1 Starting and Stopping SAP Services ............................................................. 197 21.2.1.1 SAP Service Scripts ...................................................................................... 197 21.2.2 Application Software ...................................................................................... 198 21.3 SAP Release Upgrade .................................................................................. 198 21.3.1 Services Port ................................................................................................. 198 21.3.2 Instance profile .............................................................................................. 199 21.4 Transport Directory ........................................................................................ 200 21.5 Printing in FlexFrame .................................................................................... 200 21.5.1 Possible Printing Architectures and Methods ................................................ 200 21.5.2 Local Printing (Access Methods C and L) ...................................................... 200 21.5.3 Remote Printing (Access Methods S and U) ................................................. 201 21.5.3.1 Architecture Prerequisites.............................................................................. 201 21.5.3.2 SAP System Prerequisites............................................................................. 201 21.5.3.3 Description ..................................................................................................... 202 21.5.4 Front-end Printing on Local Printers .............................................................. 203

22 BRBACKUP and SAPDBA/BRCONNECT ................................................... 205 22.1 Solution 1 for Oracle and SAPDB/MaxDB ..................................................... 205 22.2 Solution 2 for Oracle ...................................................................................... 206

23 Troubleshooting .......................................................................................... 207

24 Abbreviations ............................................................................................... 213

25 Glossary ....................................................................................................... 217

26 Index ............................................................................................................. 223

Introduction

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://manuals.ts.fujitsu.com/index.php?id=9215-9217

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™ or DB2™ 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 about installing SAP within a FlexFrame

environment is not intended as a stand-alone documentation. It solely describes the

differences to a standard SAP installation as described by SAP.

1.3 Special Hints for FlexFrame

In this document, you often will find console output, configuration data and installation

examples which are based on earlier FlexFrame versions. Please keep in mind that these

are examples and may look slightly different on the new operating systems introduced in

FlexFrame 4.2A.

The two Control Nodes (CN) of FlexFrame for SAP are also named as the FlexFrame

Control Center (CC). In this documentation the notation Control Node (CN) is used as a

synonym for Control Center (CC) and the other way round.


Introduction

2 Installation Guide for SAP Solutions

1.4 Overview

The SAP installation is performed in several steps depending on the SAP installation you

want to do:

1. Information about the SAP Services is collected in in the Management Tool; There is

a little overview in chapter 2.4, for details please have a look in the manual of the

new Management Tool

2. SAP installation tasks as described in the corresponding sections. You can start with

the chapter ―Getting Started‖ (see chapter 2) and follow the links depending on what

you want to do.

3. SAP Service scripts for virtualizing the applications (see chapter 5).

1.5 Notational Conventions

The following conventions are used in this manual:

Additional information that should be observed.

Warning that must be observed.

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

<fixed font> Names of variables

fixed font User input in command examples

(if applicable using <> with variables)

1.6 Document History

Document Version Changes Date

1.0 First Edition 2011-11-23

1.1 Support of SAP JVM

Support BOBJ 4.0

MaxDB installation hints

2011-11-30

1.2 Transparent LDAP 2012-03-15

1.3 Support maxDB 7.9 2012-05-14

Introduction


1.4 Installation hints:

SAP 7.0 EHP3, 7.3 EHP1

Global user list

2012-08-08

1.5 Performance issue MaxDB

7.8/7.9

2012-10-09

1.6 Troubleshooting (no CI/JC) 2012-11-08

1.7 Wrong command syntax

(SAP 7.3 EHP1)

2013-01-12

Introduction


1.7 Related Documents

FlexFrame™ for SAP® – Administration and Operation

FlexFrame™ for SAP® – HW Characteristics Quickguides

FlexFrame™ for SAP

® – Installation ACC 7.3

FlexFrame™ for SAP® – Installation Guide for SAP Solutions

FlexFrame™ for SAP® – Installation of a FlexFrame Environment

FlexFrame™ for SAP® – Management Tool


® – myAMC.FA_Agents Installation and Administration


® – myAMC.FA_Messenger Installation and Administration


® – myAMC.FA_LogAgent Installation and Administration

FlexFrame™ for SAP® – Network Design and Configuration Guide

FlexFrame™ for SAP® – Security Guide

FlexFrame™ for SAP® – Technical White Paper

FlexFrame™ for SAP® – Upgrading FlexFrame 4.2B or 5.0A to 5.1A

ServerView Documentation

SUSE Linux Enterprise Server Documentation

1.8 Hotlinks for FlexFrame

Global information on FlexFrame

FlexFrame for SAP manuals


Official FlexFrame home page

http://www.ts.fujitsu.com/flexframe

Dynamic Infrastructures and FlexFrame for SAP

https://partners.ts.fujitsu.com/com/products/infrastruc-solutions/FlexFrame

Service Partner Portal for FlexFrame for SAP

https://partners.ts.fujitsu.com/com/service/software/flexframe

SAP NetWeaver™

http://www.sap.com/solutions/netweaver/

Fujitsu and SAP

https://partners.ts.fujitsu.com/com/partners/strategic_partners/sap

FlexFrame for SAP on Linux®


http://www.ts.fujitsu.com/flexframe

https://partners.ts.fujitsu.com/com/products/infrastruc-solutions/FlexFrame

https://partners.fujitsu-siemens.com/com/service/software/flexframe

http://www.sap.com/solutions/netweaver/

https://partners.ts.fujitsu.com/com/partners/strategic_partners/sap

Introduction


Global information on FlexFrame

SAP on Linux (released kernels, hardware and distributions for SAP)

http://www.sap.com/linux

PRIMERGY™ manuals

http://manuals.ts.fujitsu.com/index.php?id=5406

PRIMERGY Information Center

https://partners.ts.fujitsu.com/com/products/servers/primergy

Knowledge

Documentation on ServerView Suite

http://manuals.ts.fujitsu.com/index.php?id=5406-5873-5925

Software

Software by Fujitsu

http://support.ts.fujitsu.com/DE/support/downloads.html

http://www.sap.com/linux

http://manuals.ts.fujitsu.com/index.php?id=5406

https://partners.ts.fujitsu.com/com/products/servers/primergy

http://manuals.ts.fujitsu.com/index.php?id=5406-5873-5925

http://support.ts.fujitsu.com/DE/support/downloads.html

Getting Started


2 Getting Started

If you want to get an overview about FlexFrame skip to FlexFrame Overview.

If you want to gather information about the principles of services please refer to

Virtualization of SAP Services.

For an initial configuration you have to specify your system landscape. The principles of

this operation are described in chapter 2.4.

You will find Information about supported hardware configurations in Supported hardware

for Application Nodes.

How to configure your system for SAP service connections is described in SAP Service

Connections.

To read about the principle of usage of the FlexFrame Autonomous Agents please have a

look into chapter 4.

Information about the support of virualization applications and the corresponding

interfaces you will find in SAP Service Scripts.

You should check your installation for usage of /dev/random or /dev/urandom. Please

refer to the corresponding information in ―Usage of /dev/urandom‖ in chapter 8.6

If you want to install a new SAP service please start at SAP installation overview.

Information about miscellaneous administration tasks and SAP issues you can find in the

SAP System Administration chapter.

Solutions for backing up your system with SAP-BRTools you will find in BRBACKUP and

SAPDBA/BRCONNECT.

Known errors and the corresponding workarounds are handled within Troubleshouting.

2.1 FlexFrame

FlexFrame is a revolutionary approach for creating and configuring the infrastructure

required to run a SAP environment.

An essential feature of FlexFrame is the division of the infrastructure into 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

Getting Started


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.

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. Every SAP

Service ca run on any required Application Node within FlexFrame, as FlexFrame

provides sufficient resources.

Technically speaking, virtualization is achieved by the fact that an SAP Service is able to

move to different application nodes by 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.

2.3 Preparations

Make sure that the basic installation of FF has been done according to the described

procedure in the ―FlexFrame™ for SAP® – Installation of a FlexFrame Environment‖

manual.

2.4 Gathering SAP Services Information

The FlexFrame Management Tool is a standalone JAVA-based GUI running on a

Windows PC. You can find the tool on the Service-DVD of FlexFrame. It has to be used

to configure your initial FlexFrame configuration.

After the basic installation using the FlexFrame Management Tool you can add further

SAP services using FlexFrame administration commands, e.g. ff_sid_adm.pl.

For further information about how to configure a FlexFrame system with the tool please

refer to the corresponding manual.

Getting Started


You will be asked for the following details:

SID

Select pool (dropdown list)

Select DB type (dropdown list)

Select SAP version (dropdown list)

Select the instances needed

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 you will get a XML file which has to be moved to the Control Node. Please refer to

the corresponding manual to setup your FlexFrame system using the XML configuration

file.

2.5 Supported Hardware for Application Nodes

A subset of SAP-certified, Intel®//AMD®-based servers from Fujitsu is supported.

Please refer to:

https://www.sdn.sap.com/irj/sdn/linux

and move to ―Supported Platforms – Supported Hardware‖ and select ―Fujitsu‖

Please check that list against the Support Matrix provided with FlexFrame.

https://www.sdn.sap.com/irj/sdn/linux

SAP Service Connection


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.

3.1 OSS Network Connection with Dedicated saprouter Server

The figure below shows an example of a possible network path from SAP to the

FlexFrame environment. This figure includes a (possibly existing) server SAPROUTER,

which runs the saprouter process:

CustomerSAP

Walldorf

Tokio

Foster City

SAPROUTERTELNET

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

CustomerSAP

Walldorf

Tokio

Foster City

SAPROUTERTELNET

SAPGUI

Control Node 1

Control Node 2

Application Node 1

Gateway

Application Node 2


Application Node n

TELNET

SSH

TELNET

SSH

SAPGUI

SSH

SAPGUI

SSH

SAPGUI

SSH

SAPGUI

SSH

TELNET

SAPGUI

Please enter the server SAPROUTER as External Connectivity in the

Management Tool to get a reservation of an IP address for the first pool.

This is the principle scenario if the saprouter is used from SAP users as default. In other

(administratice usage scenarios) please use configuration as described in chapter 3.2.



3.2 OSS Network Connection without Dedicated saprouter Server

The saprouter process can be configured on the Control Node cluster if there is no

dedicated server for it (see chapter section ―SAPROUTER on the Control Node‖ on page

190).

In this case, a virtual IP address for the Client LAN has to be defined for the saprouter

service and for every pool, and the Linux-HA cluster has to be configured accordingly.

To allow the Linux-HA cluster to control the saprouter service, it is necessary to get

the latest version of saprouter from SAP (Service Marketplace) and to install it in the

directory /FlexFrame/volFF/FlexFrame/saprouter on the active Control Node.

This directory has to be created, the saprouter program copied to it and saprouttab

created within this directory. The Linux-HA cluster should be reconfigured using the

saprouter user templates.

To add the saprouter application to the cluster configuration, call:

cn1:~ # ff_ha_tool.sh –a saprouter

For each virtual IP address, call:

cn1:~ # ff_ha_tool.sh –a saprouterip ip=a.b.c.d

Where a.b.c.d is the virtual IPv4 address for the saprouter service. It is necessary that

a fixed IPv4 address of the same subnet is already configured in the operation system

(which is usually the case for the Client-LAN), otherwise the resource script will not be

able to detect the correct interface.

The saprouter service and the IP address will be started immediately after being added to

the cluster configuration. This can be verified by executing:

cn1:~ # crm_mon -1 –r

If the saprouter is configured to explicitely listen on the virtual ip addresses, it might be

necessary to add the ip resources before adding the saprouter itself, otherwise the

saprouter may not be able to start and result in a failed state of the resource which has to

be cleaned up then.

Adding more virtual addresses is possible at any time by adding a new saprouterip

configuration template.

Removing ip addresses is possible by executing:

cn1:~ # ff_ha_tool.sh –d saprouterip ip=a.b.c.d



Removing the saprouter itself is possible by executing:

cn1:~ # ff_ha_tool.sh –d saprouter

Removing a user template configuration will automatically stop the resource.

To view all configured user templates with information how to delete, execute:

cn1:~ # ff_ha_tool.sh –d -l

Don‘t forget to check the correct permissions in the saprouttab file if there are

multiple pools!

CustomerSAP

Walldorf

Tokio

Foster City

TELNET

SAPGUI

Control Node 1(saprouter)


Application Node 1

Gateway

Application Node 2


Application Node n

SAPGUI

SSH

SAPGUI

SSH

SAPGUI

SSH

SAPGUI

SSH

TELNET

SAPGUI

CustomerSAP

Walldorf

Tokio

Foster City

TELNET

SAPGUI



Application Node 1

Gateway

Application Node 2


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

https://service.sap.com/sap/support/notes/35010


FA Agents


4 FA Agents

A FlexFrame Autonomous Agent (FA Agent) is an efficient component for highly

autonomous operation of systems with distributed instances. A FlexFrame solution

consists of Network Attached Storage, Application Nodes, and redundant Control Nodes.

The FA Agents product has been developed for this solution, consisting of storage,

servers, and connectivity.

It permits fast and flexible installation of solutions, which simplify the operation of the

applications and make them flexible. New nodes and application instances can be

integrated without any changes to the configuration.

Components of a FlexFrame Autonomous Agent:

FlexFrame Autonomous Application Agent (FA_AppAgent)

FlexFrame Autonomous CtrlAgent (FA_CtrlAgent)

The FlexFrame Autonomous Agent components also permit the highly available, partly

autonomous operation of distributed applications. The application instances can be

distributed over any required number of nodes within a FlexFrame solution. Monitoring of

several services is implemented via the FlexFrame Autonomous Agent.

The FA Application Agent components normally support SAP application instances (pure

application instances and central instances), as well as SAPDB/MaxDB and Oracle

databases.

For more information, please refer to the ―myAMC.FA_Agents Installation and

Administration‖ manual.

SAP Service Scripts for Virtualizing Applications


5 SAP Service Scripts for Virtualizing Applications

Scripts for starting, stopping and restarting the applications and services are provided by

SAP.

With FlexFrame 5.0 the interface to start and stop SAP services were changed.

The following scripts are installed:

Script name Application

ff_service.sh Central Script to start, stop, etc a SAP service

ff_service_functions Function library for ff_service.sh

ff_sapdb_functions Function library for ff_service.sh (databases)

ff_sapclassic_functions Function library for ff_service.sh (classic

services)

ff_sapnonclassic_functions Function library for ff_service.sh (new

services, e.g. CMS)

ff_service.config Configration file of ff_Service.sh

sapservice_config Global customer-specific parameters

sapservice_functions Global parameters and functions; still available

because of compatibility reasons

start_all_sapservices Initial start of all configured applications

stop_all_sapservices Stops all running applications

stop_all_sapservices_local Stops all running applications on the local node

stop_all_sapservices_SID Stops all running applications of one SID

5.1 Starting a Configuration

The start_all_sapservices start script defines which applications are to be started

in which sequence and on which virtual host. The script is executed on a Control Node.

The script below illustrates its syntax:

#!/bin/bash



#-----------------------------------------------------------------

# Rule is:

# All sapservices in one 'eval' must start one after another,

# each 'eval' may start simultaneous.

# C11

eval "

ssh applnode1 ff_service.sh –t db –s C11 –a start

ssh applnode1 ff_service.sh –t ci –s C11 –a start

ssh applnode2 ff_service.sh –t db –s C11 –i 01 –a start

ssh applnode3 ff_service.sh –t db –s C11 –i 02 –a start

" &

#echo ""

#echo "All services should be up now."

#-----------------------------------------------------------------

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

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.

The figure below shows the dependencies of the SAP Services (x y means ―x is

dependent on y‖).



The area containing JC and SCS is the minimal group of services for J2EE only. The

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

5.2 Configuring the Service Status Path

In the following naming conventions

id is the consecutive two-digit number from 00-97

sid is the lower-case three-digit system ID



The SERVICE_STATUS_PATH parameter (files usually stored in

/FlexFrame/scripts/log) describes the global location for the service control files of

the applications (services). If such a file exists, the application or service has been started

and therefore should be running. The naming convention is defined as follows:

For the service types db and ci: <service_type>_<sid>_host

For the service type app: app_<id>_<sid>_host

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

There are additional service types when you run a J2EE engine based on WebAS 6.40.

For the service types scs and jc: <service_type>_<sid>_host

For the service type j: j_<id>_<sid>_host

The content of the service control file is the name of the node the application or service is

running on.

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

There are additional service types when you run a J2EE engine based on WebAS 7.00.

For the service types scs, ascs and jc: <service_type>_<sid>_host

For the service type j: j_<id>_<sid>_host

WebAS 7.0 with JAVA/J2EE Engine and/or ABAP/ASCS Engine and ERS

There are optional service types bound on WebAS 7.00.

For the service types scs and ascs: sapers_<id>_<sid>_host

WebAS 7.0 with ABAP and MaxDB (LiveCache)

There is a additional service type which supports LiveCache.

Service type: lc_<sid>_host

SAP 7.1 with JAVA

The naming for the former service type jc has been changed:

Service type: j_<id>_<sid>_host



5.3 Configuring the Interfaces

Depending on which interfaces the nodes have, the LAN type must be assigned to the

interfaces.

The following section from the sapservice_config include script shows the

connection between the LAN type, interface and netmask:

#-----------------------------------------------------------------

# Netmask

#

#NETMASK_CLIENT=‖255.255.240.0 ls3195:255.255.255.0‖

NETMASK_CLIENT=‖255.255.255.0‖

NETMASK_SERVER=‖255.255.255.0‖

#

# Interface

#

#-----------------------------------------------------------------

# SunOS link aggregation

# ~~~~~~~~~~~~~~~~~~~~~~~

#

# real interfaces look like this:

# fjgi2005000 # this is the first interface

# fjgi2005001 # this is the second interface

# fjgi2005000:1 # this indicates that the first interface

# # is active

# fjgi2005001:1 # this indicates that the second interface

# # is active

#

# These interface names consist of three parts:

# fjgi2005001:1

# ^^^----------- interface number

# ^^^^-------------- vlan

# ^^^^------------------ 1GB-model

#

# For our network to interface relation we use only the first two

# parts of the interface names, the model and the vlan. In our

# example:

# fjgi2005

#

#-----------------------------------------------------------------

#

# Recommendations:

#



# for a clean linux environment without network redundancy,

# FlexFrame <= 3.0.x

# ETH_CLIENT= »eth0 ls3191 :eth1 ls3192 :eth1 ls3195 :eth1 »

# ETH_SERVER=―eth1 ls3191:eth0 ls3192:eth0 ls3195:eth0―

#

# for a clean linux environment with network redundancy,

# FlexFrame >= 3.1

# ETH_CLIENT=‖vlan2001‖

# ETH_SERVER=‖vlan2005‖

#

# In a FlexFrame >= 3.1 environment with more than one pool,

# we can have more than one configuration file, linked into an

# pool-image. This avoid to define to much specials.

The LAN types SERVER and CLIENT are used.

The syntax will be illustrated with reference to the example of Client and Server LAN.

For example, the ETH_SERVER parameter describes a list of assignments between the

node and the interface. The first element in the list is the standard interface for the LAN type server LAN; all of the subsequent elements are optional and describe a deviation

from this type.

5.4 Host Names

The following (virtual) host names for the SAP Services must be used and will be

generated by the Management Tool (fixed rule):

Server LAN Client LAN

db<sid>-se

lc<sid>-se

ci<sid>-se ci<sid>

ascs<sid>-se ascs<sid>

app<id><sid>-se app<id><sid>

scs<sid>-se scs<sid>

jc<sid>-se (SAP 7.1: j<id><sid>-se) jc<sid> (SAP 7.1: j<id><sid>)

ers<id><sid>-se ers<id><sid>

j<id><sid>-se j<id><sid>

N/A bobj<sid>



Server LAN Client LAN

N/A cms<sid>

mds<id><sid>-se mds<id><sid>

mdss<id><sid>-se mdss<id><sid>

mdis<id><sid>-se mdis<id><sid>

N/A <monitored host>

trx<id><sid>-se trx<id><sid>

Explanation: id Consecutive two-digit number 00-97

sid The lower-case three-digit system ID

In FlexFrame 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.

With SAP 7.1 the host names for the previous JAVA central Instance jc have been

changed from jc<sid>-se to j<id><sid>-se (Server LAN) and jc<sid> to

j<id><sid> (Client LAN).

Operating System in General


6 Operating System in General

If you have installed a JDK in an old Application Node image and you change to a new

image you have to install the previous JDK in the new image in the same way. You can

find the installation path and version of JDK in the instance profile entry

jstartup/jvm/home=<value>.

General hints about setting up Linux on Application Nodes you can find at Linux (see

chapter 6.1).

6.1 Linux

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

Setup User Environment

In the next step you set your user environment as requested. Either you set the

environment directly or you insert the definitions to the OS-specific user profile

(e.g. .bashrc with Linux).

server:/ # export JAVA_HOME=<your JAVA installation directory>

server:/ # export PATH=‖$PATH:$JAVA_HOME/bin‖

For installations with SAP releases less than SAP 7.0 you should also set

server:/ # SAPINST_JRE_HOME=/<your JAVA installation dir>/<jdk>

server:/ # export TMP=<INSTALL_DIR>


http://www.sap.com/linux/platforms

Preparations for Database Installation


7 Preparations for Database Installation

Installation of Oracle N/A

Installation of MaxDB N/A

Installation of DB2 All platforms

(see chapter 7.1)

software requirements

pre-installation steps

7.1 SAP Installation with Database DB2

With the current release of FlexFrame we support DB2 database also with the

Management Tool.

7.1.1 Software Requirements

To run DB database within a SAP system you need at least the software shown below:

FlexFrame for SAP, 5.0A

FlexFrame Autonomous Agents, V30K15 up

SAP NetWeaver 2004s (SR1/SR2) or SAP 7.0 SR3

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 or higher for Linux x86_64_Bit

(Download from http://service.sap.com)

DB2 Version 9.5 for Linux (Download from http://service.sap.com), released for SAP

7.0 SR3

DB2 Version 9.7 for Linux (Download from http://service.sap.com), released for SAP

Download the corresponding license files from SAP

You also need to install DB2 LDAP-Plug-in if you are not using DB2 Version 9.7 FixPack

1 or later from

http://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=swg

-dm-db2ldap

http://service.sap.com/



http://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=swg-dm-db2ldap




It needs a registration at IBM company. Before you download the package please check

if you have got it with the SAP Media Package for SAP installation.

With DB2 V9.7 FixPack 1 you can use the so-called ‖Transparent LDAP‖ described at

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.w

n.doc/doc/c0054120.html

7.1.2 Pre-Installation Steps

1. Stop the FA-Autonomous Agents during installation time.

2. Create a new SID instance using ff_sid_adm.pl (if it is not already specified with

the Management Tool):

ff_sid_adm.pl --op add --pool pool1 –-sid LB4 --sapversion 7.0

--db DB2V91:159

--sap ci:57:157:157

--sap ascs:55:155:155

--sap app:58:158:158

--sap scs:56:156:156

--db2srv sapdb2LB4:60000,DB2_db2lb4:60001,DB2_db2lb4_1:60002,

DB2_db2lb4_2:60003,DB2_db2lb4_END:60004

The script ff_sid_adm.pl prepares the system files /etc/hosts and

/etc/services of the application nodes known in the specific pool.

The script writes a log file in /FlexFrame/volFF/pool-pool1/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.

3. Run ff_sid_mnt_adm.pl if you want to relocate your directories for

SAPDATA/SAPLOG to a volume of your own.

4. Run ff_setup_sid_folder.sh (if SID was created manually as describe above):

ff_setup_sid_folder.sh –p pool1 –s LB4

7.2 Mount Options

FlexFrame tries to be consistent with the recommendations for NFS mount options of

storage and database software vendors. Sometimes however FlexFrame requires

different settings. This chapter should explain you how the mount options are set in

FlexFrame.

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.wn.doc/doc/c0054120.html




The most important options set for database and database software files are shown. For

detailed information please refer to NFS manpage.

7.2.1 Database files (sapdata, saplog)

Option Comment

rw read/write operations allowed; NFS default value.

hard, nointr No user interrupt is allowed. Process is always waits until server come back online. NFS default is nointr

rsize=32768, wsize=32768 Block size for reading/writing. FlexFrame specific

setting.

proto=tcp Communication protocol TCP is used; NFS default

value

nolock

No NFS file locking is requested. This is sufficient

since one server uses the files exclusively.

It means a better performance.

NFS default is lock.

vers=3 NFS version used.

timeo=600

Wait 60 sec until a retransmission is sent after

timeout. NFS default is 0.7, the maximum value is 60

sec.

retrans=2 At least two ‗minor timeouts‘ are accepted until a

operation is aborted. NFS default is 3.

suid Allow set-user-id or setgroup-id; NFS default value

bg Retrial of mount is performed in background

7.2.2 Binaries and Configuration files

Option Comment

rw NFS default value is used (rw).

hard, nointr No user interrupt is allowed.

rsize=32768, wsize=32768 FlexFrame specific setting.

proto=tcp Communication protocol default tcp is used.



nolock There is just a client site locking requested.

vers=3 NFS version is set to ‗3‘.

timeo - not set NFS default is used (0.7 s).

retrans - not set NFS default is used (3).

suid - not set NFS default value (suid)

Preparations for SAP Installation


8 Preparations for SAP Installation

Installation directories and virtual interfaces All platforms

(see chapter 8.1)

SAP JAVA Cryptographic Toolkit

(optional component)

Linux

(see chapter 6.1)

Setup directory structures (default)

(8.5.1)

Own volumes

(see chapter 8.5.2)

or

SID specific volumes

(see chapter 8.5.3)

or

Pool specific volumes

(see chapter 8.5.3)

or

SAN

(see chapter 8.5.4)

Configuration of virtual interfaces Setup interfaces manually

(see chapter 8.2)

/dev/urandom Configuration of /dev/urandom

(see chapter 8.6)

Pre-Installation hints SAP 7.0 EHP3 SAP 7.0 EHP3

(see chapter 12.13)

8.1 General

The customary instructions and guide lines apply to the installation of the software

components. The deviations from these which are required are described here.

Don‘t change the host name of the Application Node where you are going to

install the SAP and DB software.



After the installation is done, further steps are described in this document to

virtualize the SAP instance (except SAPINST 640 SR1 when used with the

SAPINST_USE_HOSTNAME parameter). Please install CI (J2EE: SCS) first, then

DB, (J2EE: JC 2nd) and the Application Server at the end.

Setup the virtual interfaces before installing the SAP solution. It is absolutly

essential to setup both virtual interfaces (client + server LAN) and make sure

that they up an running.

Please make sure that the FA Application Agents are stopped on the hosts while

you are installing SAP software:

/etc/init.d/myAMC.FA_AppAgent stop

Check the status with:

/etc/init.d/myAMC.FA_AppAgent status

The SAP Installation CDs/DVDs have to be copied to the NetApp Filer (from the Control

Node into the directory /FlexFrame/volFF/FlexFrame/stage/SAP_SW/<SAP-CD-

name>). The whole directory or each subdirectory has to be exported on the Filer with the

necessary ro or rw options for the Application Node(s). On the Application Node, the

mount will be done manually.

If an SAP Installation is done after the initial setup of the FlexFrame environment and

without entering the SAP Service data in the FF Management Tool before, the necessary LDAP data has to be created with the script ff_sid_adm.pl (see chapter ―Adding /

Removing SAP Systems and Application‖ in the Administration and Operation guide).

The directories that are necessary for SAP installation should have been created in a

step during the LDAP server setup. If necessary, create a script for the SID folder

structure.

cn1# ff_setup_sid_folder.sh –p <pool_name> -s <SID>

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

You may use ssh –X server for the Sapinst GUI. $DISPLAY will be automatically set to

something like localhost:10.0.

The X connection can be tested with xclock.

RX600-01:~ # xclock

An XCLOCK should pop up on your display. If not, check the DISPLAY variable or

the.Xauthority file.



Create the SAP installation directory into which the sapinst files are extracted:

server:/ # mkdir /usr/sap/<SID>/install

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

server:/ # cd /usr/sap/<SID>/install

8.2 How to configure the interfaces manually

Setup the required interfaces you can use the new interface ff_service.sh as shown

below (examples for SID ―OSM‖ and instance number ―25‖.

server:/ # ff_service.sh –t db –s osm –a istart

server:/ # ff_service.sh –t ci –s osm –a istart

server:/ # ff_service.sh –t ascs –s osm –a istart

server:/ # ff_service.sh –t app –i 25 –s osm –a istart

server:/ # ff_service.sh –t j –i 25 –s osm –a istart

server:/ # ff_service.sh –t jc –s osm –a istart

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

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

SLES10_x86: JAVA_HOME is /usr/lib64/jvm/java

The example below shows SLESnn (SUN Java)

cn1:~#> cd /FlexFrame/volFF/os/Linux/FSC5.0xxx/root_img/usr/lib64/java

cn1:~#> cp -rp <JAVA_DIR> ../../../../var_img/var-xxxxxxxx/<JAVA_DIR>

applnode1:~#> mount -t nfs filerxxxx:/........var-xxxxxxxx/<JAVA_DIR>

/usr/java/<JAVA_DIR>

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

Now the JAVA files are writeable.

If the installation has finished successfully, do the following:

applnode1:~#> umount /usr/java/<JAVA_DIR>

cn1:~#> cd ..../var_img/var-xxxxxxxx/<JAVA_DIR>

cn1:~#> cp -rp <JAVA_DIR>...os/Linux/FSC5.0xxx/root_img/usr/lib64/java

/<JAVA_DIR>

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

8.5 Setting up SAP directories (Control Center)

8.5.1 Standard Volumes

If you want to use the standard volumes ―sapdata‖ and ―saplog‖ or you have specified

specific volumes for this SID or its corresponding pool (by FF Configuration Tool) you just

need to call ff_setup_sid_folder.sh.



Example:

CN1# ff_setup_sid_folder.sh -p pool1 –s S03

8.5.2 Specify volumes of your own

If you want to store SAPDATA/SAPLOG on a volume different from default you need to

run ff_sid_mnt_adm.pl before running ff_setup_sid_folder.sh.

Further information about the commands see the corresponding chapter in the

Adminstration and Operation Guide.

Example:

CN1# ff_sid_mnt_adm.pl –op add –pool pool2 –sid S03 \

--sap --sapdata jer1na-st:/vol/<volumeName>/pool1/S03 \

--saplog jer1na-st:/vol/<volumeName>/pool1/S03


8.5.3 SID/Poolspecific volumes

SID- or pool-specific volumes are specified by FF Configuration Tool. So you just enter

ff_setup_sid_folder.sh.

Example:


8.5.4 Using SAN

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

can be installed you have to run

ff_san_ldap.pl

ff_setup_sid_folder.sh

ff_san_mount.sh

changing owner of database files

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 /sapdata/sapdata<n>/<SID> for data volumes and

/saplog/saplog<n>/<SID> for log volumes.

The access rights have to be set to the database user and database group.

Example:

CN1# ff_san_ldap_conf.pl --conf=/home/SAN/config/S03 --op add --pool pool1 –sid S03


CN1# ff_san_mount.sh pre sapdb S03 start

applnode# cd /var/FlexFrame/SAN/oracle/S03

applnode# chown -R oras03:dba

8.6 Usage of /dev/urandom

During operation SAP systems need random numbers. To get those numbers the system file /dev/urandom is used. FlexFrame is configured with /dev/urandom as default.

You are not allowed to change that setting to /dev/random! It would mean

problems during operation of SAP system (system hangs up).



8.7 Predefined global users

Depending on SAP reelase or used database type there are a small number of users

which are generally created. These are no specific users of FF4SAP. They are requested

by SAP services.

In case of the default pool they are created at pool creation time, with additional pools the

creation of a new SID (ff_sid_adm.pl) also creates missing global users.

Usually there should be no login possible to the system by these users. So you are

strongly recommended to change the standard password to a complex password string

for these users using ‗ff_user_adm.pl –op mod –pass ….‘

user name purpose

dasusr1/db2fenc1/

db2inst

Introduced with DB2 V9.1 to setup DB2 databases

sapadm SAP requested user needed in SMD environment (SAP

System Administrator)

sdb SAP requested user needed if SAPDB/MaxDB is used as

database type.

SMD_ADMIN/smd_admin SAP requested user needed in older configurations using

Diagnostic agents

SAP Installation - Overview


9 SAP Installation - Overview

This chapter gives you an overview about all necessary actions required to install a SAP

system. To get a detailed action list please follow the given hyperlinks depending on what

you want to do.

In general it is strongly recommended to read the corresponding SAP installation guides.

This manual cannot replace the whole SAP installation description. Independent from the

service type which should be installed you

Create a installation directory, e.g. /usr/sap<SID>/install

Create a further directory for each service you want to install,e.g.

/usr/sap<SID>/install/db, /usr/sap<SID>/install/scs)

Extract the installation files in each service installation directory

Start the installer sapinst in the corresponding service installation directory

The specific installation description always describes the issues which are new with the

specific SAP installation. If there will be an error which is not described at the specific

SAP installation description you should refer to older versions with the same installation

type.

If you will do an update of your software stack you may get more or less the

same problems as given with an installation from scratch. From our point of view

the descriptions to overcome those problems are described for installations from

scratch are also valid for updates.

1. Operating System settings Operating System in General

(see chapter 6 )

2. Make virtual IPs available for

Sap instances

General hint how to configure interfaces

manually please refer to ―Interface

Configuration‖

(see chapter 8.2)

3. Preparations for Database

Installation

Check correspoding installation hints

(see chapter 7)

4. Preparations for SAP

installation

Check corresponding installation hints

(see chapter 8)



5. Installation of SAP system 4.6CSR2

(see chapter 10 )

or

WebAS 6.40

(see chapter 11)

or

WebAS 6.40 JAVA

(see chapter 11.1)

or

WebAS 6.40 ABAP with Oracle

( see chapter 11.2)

or

WebAS 6.40 ABAP with JAVA-Addin

NW04SR1

(see chapter 11.3)

or

WebAS 6.40 with JAVA Addin

(see chapter 11.4 )

or

NetWeaver_7.0SR3

(see chapter 12)

or

LiveCache

(see chapter 12.14)

or

ERS 7.00

(see chapter 12.15)

or

SAP 7.1

(see chapter 13)

or



SAP 7.1 ERS

(see chapter 13.3 )

Or

SAP 7.3

(see chapter 14)

6. Post installation steps

(database)

Check corresponding installation hints

(see chapter15.3.1)

7. Post installation steps (SAP) Check corresponding installation hints

(see chapter16)

Installing SAP 4.6C SR2


10 Installing SAP 4.6C SR2

Before starting with the Installation of SAP 4.6C SR2 on FlexFrame, please refer

to the original SAP installation guides. Please also get the applicable SAP notes

from the SAP Marketplace.

R3SETUP has a problem with NFS mounted file systems.

NetApp has a script which is helpful to avoid such problems. The script must be

edited.

The lines which refers to chown -R root:root /oracle and

chmod -R 777 /oracle must be deleted.

Possible Error Message:

4.6C SR2 SAPCAR aborts with error 36: staging area is not empty.

Solution: Delete all files and subdirectories in directory

/oracle/stage/920_32.

Please check the permissions of the users <sid>adm, ora<sid> and

sqd<sid>.

A workaround must be observed if SAP is installed on the NetApp Filer using R3SETUP

(up to release 4.6C). This is described in the following technical report:

SAPDB http://www.netapp.com/library/tr/3143.pdf

R3SETUP does not yet permit installation of SAP on NFS drives in this version.

If sapinst is used for installation (release 4.7 and above or Web AS 6.20 or 6.40),

installation on the NetApp Filer with NFS is directly supported.

http://www.netapp.com/library/tr/3143.pdf



The following table shows you the steps you have to perform when you want to install

SAP 4.6C SR2

1. Introduction All Platforms

(see chapter 10)

2. Install DB service Oracle 9.2

(see chapter 16.2 )

2a. DB post installation step Oracle 9.2 only

(see chapter 15.2.1)

3. Setting virtual DB host All platforms

(see chapter16.1.2)

4. Install CI service All platforms

(see chapter 10.1.1

5. Setting virtual CI host All platforms

(see chapter16.1.1)

6. Install Application service

7. Setting virtual Application host All Platforms

(see chapter16.1)

8. Installation issues All platforms

(see chapter 10.1)

9. Post install – start/stop SAP All platforms

(see chapter16.9)

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



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.

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



Restart R3SETUP.

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



Restart R3SETUP.

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



Restart R3SETUP.

10.1.1 Installing the Central Instance (CI)

In case of a virtual installation the virtual interface must be up and running.

Setup the interfaces for central instance host ―ciosm‖ as shown in the examples.

baby_3:~ # cd /usr/sap/OSM/install

baby_3:~ # mkdir OSMCI

baby_3:~ # chmod 777 OSMCI

baby_3:~ # cd OSMCI

# ..../sapinst -extract

Extracting in /usr/sap/OSM/install/OSMCI...

sapinst: ok

iacdlib642.so: ok

iaccdlib.so: ok

iaejs642.so: ok

iakdblib642.so: ok

...

iarfclib642.so: ok

Done



# SAPINST_JRE_HOME=/usr/j2sdk/j2sdk1.4.2_10

# export SAPINST_JRE_HOME

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



Installing Web AS 6.40 with NetWeaver04 SR1


11 Installing Web AS 6.40 with NetWeaver04 SR1

This section is valid only for Web AS 6.40 installation prior to NW04 SR1.

Please refer to the original SAP installation guides and also get the applicable

SAP notes from the SAP Marketplace.

With the installation DVDs ―NetWeaver 04 SR1‖, Web AS 6.40 can be installed

on a virtual hostname. For this purpose SAP has introduced the parameter

SAPINST_USE_HOSTNAME.

You may start the installation directly from the Master DVD or create an

installation directory, extract the software into it and start the installation from

there. The second choice is described for the different SAP services.

During the installation, the file /etc/services will be copied to

/etc/services.x. This will fail because the root file system is mounted read-

only. In that case stop the installation and search for the string ERROR in

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<SID> of the ABAP instance will be added to the

local /etc/services file. This has to be done manually on Linux from the

Control Nodes. Afterwards, the entry has to be removed.



The following table shows you the steps you have to perform when you want to install Web AS 6.40 NetWeaver04SR1.

1. Introduction All types (see chapter 11)

2. Install SCS Service JAVA (see chapter 11.2.1)

JAVA+ABAP (see chapter 11.2.1)

3. Virtualize user environment for SCS host JAVA (see chapter16.1.4)

JAVA+ABAP (see chapter 16.1.4)

4. Install DB service ABAP (Oracle) (see chapter 11.2.6)

JAVA (see chapter 11.2.2)

JAVA-Addin (see chapter Fehler! Verweisquelle konnte nicht gefunden werden.)

5. Virtualize user environment for DB host ALL see chapter 18.1.2

ALL see chapter 18.1.2

ALL see chapter 18.1.2

6. Install Central Instance ABAP (Oracle) (see chapter 11.2.5)


JAVA-Addin (see chapter 11.3.3)

7. Virtualize user environment for CI host All see chapter 18.1.1

All see chapter 18.1.1


8. Install Application service ABAP (see chapter 11.2.7


9. Virtualize user environment for application host All see chapter 18.1.3





11.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 92).

For installation of a J2EE instance or a J2EE Add-In in an existing ABAP instance, the service sapms<SID> of the ABAP instance will be added to the

local /etc/services file. This must be done manually on Linux from the

Control Nodes. Afterwards, the entry must be removed.



11.2 Web AS 6.40 NetWeaver04SR1 JAVA MaxDB/Oracle

Start the installation using virtual host names.

The example shows a 6.40 JAVA NW04SR1 on MaxDB (SID=MLJ) installation.

11.2.1 SCS

Make sure that the IP interface address of the <scs_virtual_hostname> is up and

running. Setup the interfaces for host ―scsosm‖ as shown in the examples.

applnode1:~#> cd /usr/sap/<SID>/install_SCS

applnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst –extract

applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<scs_virtual_hostname>

<PATH_to_SAP_MASTER_DVD>/product_ha.catalog





Type in the virtual DB host

name





11.2.2 DB

Make sure that the IP interface address of the <db_virtual_hostname> is up and

running. Setup the interfaces for host ―dbosm‖ as shown in the examples.

applnode1:~#> cd /usr/sap/<SID>/install_DB


applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<db_virtual_hostname>




If you install a J2EE engine using the product_ha.catalog, and during the database

installation step you see a dialog asking for an installation drive, stop the installation and

insert the following three lines to your control.xml.

after:

var client = new ClientMapping();

var ids = ["ciHostIsUnix", "sapmntPath"]; var globalHostSID;

-if (parseBool(installer.getGlobalParameter("SeparateSCS")) &&

(context.getBool("ci") || context

.getBool("db")))

insert:

if (installer.onWindows() &&

parseBool(installer.getGlobalParameter("SeparateSCS")) &&

(context.getBool("ci") || context.getBool("db"))) {

Now, restart SAPinst.

11.2.3 JC

Make sure that the IP interface address of the <jc_virtual_hostname> is up and

running. Setup the interfaces for host ―jcosm‖ (until SAP 7.0) or ―j<nr>osm‖ (SAP 7.1 up)

as shown in the examples.

applnode1:~#> cd /usr/sap/<SID>/install_JC


applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<jc_virtual_hostname>


11.2.4 J

Make sure that the IP interface address of the Java application instance is up and

running.

Set up the interfaces for host ―j<nr>osm‖ as shown in the examples

applnode1:~#> cd /usr/sap/<SID>/install_J<xx>


applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<j_instance_number_virtual_hostname>




11.2.5 CI

Make sure that the IP interface address of the <ci_virtual_hostname> is up and

running.

applnode1:~#> cd /usr/sap/<SID>/install_CI


applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<ci_virtual_hostname>

<PATH_to_SAP_MASTER_DVD>/product.catalog





Type in the virtual DB host

name



11.2.6 DB

Make sure that the IP interface address of the <db_virtual_hostname> is up and

running. Setup the interfaces for host ―dbosm-se‖ as shown in example (chapter 8.2)





After successful loading the database, the automatic startup of SAP may fail sometimes.

Start the SAP manually

Stop the SAPINST

Restart the SAP installer using ―SAPINST_SKIP_ERRORSTEP true‖

11.2.7 APP

Make sure that the IP interface address of the virtual hostname of the application

instance is up and running. Setup the interfaces for host ―app<nr>osm‖ as shown in

example (chapter 8.2)

applnode1:~#> cd /usr/sap/<SID>/install_APP


applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<app_instance_number_virtual_hostname>


11.3 Web AS 6.40 ABAP + JAVA-AddIn NetWeaver04SR1

11.3.1 SCS

Make sure that the IP interface address of the virtual hostname of the SCS instance is up

and running. Setup the interfaces for host "scsosm" as shown in example (chapter 8.2)

Before starting the installation procedure, add the sapms<SID> entry

manually in the /etc/services (do not forget to remove the entry after the

installation!).



11.3.2 DB

Make sure that the IP interface address of the virtual host of the database instance is up

and running. Setup the interfaces for host "dbosm-se" as shown in example (chapter 8.2)





11.3.3 CI

Make sure that the IP interface address of the virtual host of the central instance is up

and running. Setup the interfaces for host ―ciosm‖ as shown in example (chapter 8.2)

applnode1:~#> cd /usr/sap/<SID>/install_CI




When installing on Oracle, there is one further option ―Distributed System‖, that allows

installing the database schema and the JAVA part separately:

Java Database Schema Installation:

applnode1:~#> cd /usr/sap/<SID>/install




Central Instance Finalization:





Example:

The example shows an installation on MaxDB.









Type in the

virtual CI host name



When the installation has finished successfully, you have to change the

hostname of the SCS instance manually.

If the installation of the SCS Installation aborts at the step Load Java

Database Content (step 19) with the error message no connection to

network adapter, please proceed as follows:

Stop the Oracle listener process. Change the virtual host name db<sid>-se to

the real host name (uname –a) in the listener.ora and tnsnames.ora.

Start the Oracle listener process and click the Retry button from the SAPINST

GUI.



Check and modify the following:

1. Copy the .sapenv_ci<sid>.csh file to .sapenv_scs<sid>.csh

(also for the .sh file).

2. Move the instance/start profile to the correct hostname.

3. Exchange the hostname in the instance/start profile.

4. Go to section 16.1 in this document to change the hostname for the SCS instance.

11.4 Web AS 6.40 Application Server JAVA-AddIn

We assume that all required components (DB, ABAP CI, JAVA-AddIn and SCS)

have already been installed.

An /etc/services entry for <SID> is necessary for the installation only

You have already installed a ABAP DI Instance

Use the CD/DVD of NW04 SR1 or higher

Start up the installation as follows:

1. Extract the sapinst in the installation directory

(...<path_to_SAPINST>/sapinst –extract)

applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME=<virtual_hostname_of_APP_Server>




The following message box opens:

2. Click on OK

The instance number is the same as you have chosen for the ABAP DI

3. Make sure that you have deleted the /etc/services entry of your installed system

before starting the APP.

Installing NetWeaver 7.0SR3


12 Installing NetWeaver 7.0SR3

During the installation, the file /etc/services will be copied under

/etc/services.x. This will fail because the root file system is mounted read-

only. In that case, stop the installation and search for the string ERROR in the

keydb.xml. Change the entry to OK and restart the installation.

For every SAP solution you have to follow the instructions of section 12.1.

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 2008-11-06 10:29:35

CJSlibModule::writeError_impl()

CJS-20022 Could not start instance 'JC41' of SAP system OLP.

ERROR 2008-11-06 10:29:35


CJS-20022 Could not start instance 'JC41' of SAP system

The following table shows you the steps you have to perform when you want to install

NetWeaver 7.0SR3

1. Introduction All Types

(see chapter 12)

2. Install SAP Service (e.g. SCS) Installation example

(see chapter 12.1)

4. Install DB service Database Installation - in general

(see chapter 15)

and

Oracle 10 specifics

(see chapter 12.5)

or

MaxDB76 / 77 specifics

(see chapter 12.6)

or



MaxDB76 / 77 on SLES9_x86/SLES10_x86

specifics

(see chapter 12.7)

5a. Standard installation Types

or

Enterprise Portal (EP)

(see chapter 12.9 )

or

ABAP + JAVA Addin

(see chapter 12.10)

or

JAVA only

(see chapter 12.11)

or

SAP 7.01/SLES9

(see chapter 12.12)

5b. Live Cache (MaxDB 76/77)

or

Additional installation requests

(see chapter 12.14

5c. Enqueue Replicated Server (ERS) Installation until NetWeaver 2004s SR3

(see chapter 12.15 )

6. General post installation steps

(SAP 7.0 only)

Linux

(see chapter 6.1)



12.1 Installation of SAP Solutions

1. Select one of the SAP solutions.

It has no effect which DB or SAP solution you want to install. This part is necessary

for every NetWeaver 7.0SR3 installation step.

2. Click on the Next button.

3. If the next screen appears, please abort the installation.

4. Modify the files control.xml and sapinst in the installation directory.

control.xml:



perl –i.bak –p –e ―s@/usr/sap/sapservices@/usr/sap/sapservices/sapservices@g‖

control.xml

sapinst file: change the umask value entry to 022:

perl –i.bak –p –e ―s/umask 027/umask 022/‖ sapinst

5. Restart the installation:

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

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

12.2 Sapinit File (Linux)

WARNING 2008-11-06 10:06:51

CJSlibModule::writeWarning_impl()

Execution of the command "/usr/sap/OLP/install/SCS/installsapinit.sh" finished with

return code 1. Output:

mv: cannot move `/etc/init.d/sapinit' to `/etc/init.d/sapinit.old': Read-only file

system

cp: cannot create regular file `/etc/init.d/sapinit': Read-only file system

ERROR 2008-11-06 10:06:51


MUT-03011 Execution of the command "/usr/sap/OLP/install/SCS/installsapinit.sh"

finished with return code 1. Output:

mv: cannot move `/etc/init.d/sapinit' to `/etc/init.d/sapinit.old': Read-only file

system

cp: cannot create regular file `/etc/init.d/sapinit': Read-only file system

ERROR 2008-11-06 10:06:51 [iaxxgenimp.cpp:736]

showDialog()

FCO-00011 The step installSAPInit with step key

|NW_Java_SCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5|0|installSAPInit was

executed with status ERROR .

1. Proceed as follows:

applnode1:<INSTALL_DIR> > vi keydb.xml

</row>

<row>

<fld name="STEPKEY">

<strval><![CDATA[|NW_Java_SCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5|

0|installSAPInit]]>

</strval>

</fld>

<fld name="STATUS">

<strval><![CDATA[ERROR]]> to OK

</strval>

</fld>

<fld name="STOP_BEFORE">

<strval><![CDATA[]]>



</strval>

</fld>

<fld name="STOP_AFTER">


</strval>

</fld>

<fld name="STATE_SET_BY_STEP_STATE_EDITOR">


</strval>


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

12.3 installsapinit.sh – symlink (Linux)

WARNING 2008-11-06 10:43:23

CJSlibModule::writeWarning_impl()

Execution of the command "/usr/sap/LO7/install/ASCS/installsapinit.sh" finished

with return code 5. Output:

insserv: can not symlink(../sapinit, rc3.d/S14sapinit): Read-only file system

insserv: can not symlink(../sapinit, rc3.d/K08sapinit): Read-only file system



ERROR 2008-11-06 10:43:23


MUT-03011 Execution of the command "/usr/sap/LO7/install/ASCS/installsapinit.sh"

finished with return code 5. Output:






showDialog()

FCO-00011 The step installSAPInit with step key

|NW_ABAP_ASCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5|0|installSAPInit was


1. Proceed as follows:





<strval><![CDATA[|NW_ABAP_ASCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5

|0|createPorts]]>

</strval>

</fld>

<fld name="STATUS">

<strval><![CDATA[OK]]>

</strval>


12.4 Services File (Linux)

ERROR 2008-11-06 11:22:09 [syxxsyshlp.cpp:78]

syslib::printOSError(const iastring &, int, DWORD, const iastring &,

CMessage::eLogMessage)

FSL-00001 System call failed. Error 30 (Read-only file system) in execution of

system call 'openU' with parameter (/etc/services.SAPtmp, O_WRONLY | O_TRUNC |

O_CREAT, S_IRWXU | S_IRWXG | S_IRWXO), line (413) in file (syuxcfile.cpp).

ERROR 2008-11-06 11:22:09 [syuxcfile.cpp:417]

CSyFileImpl::copy(const CSyPath & /etc/services.SAPtmp,

ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const

FSL-02013 Unable to access file /etc/services.SAPtmp: cannot get write access.

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

CSyServicesEntryImpl::editServices(ISyServicesEntry::eWriteMode

REPLACE_NAME) const

FSL-03006 Unknown exception caught when trying to add an entry to the service

file.

ERROR 2008-11-06 11:22:09


MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text

undefined.



1. Abort the installation and proceed as follows:


<row>


<strval><![CDATA[|NW_ABAP_ASCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5

|0|createPorts]]>

</strval>

</fld>

<fld name="STATUS">

<strval><![CDATA[ERROR]]> to OK

</strval>



12.5 NetWeaver 7.0SR3 and Oracle 10

The installation could fail due to the following eror:

ERROR 2008-11-06 10:24:26 [iaxxinscbk.cpp:271]

abortInstallation

CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: SP2-0606:

Cannot create SPOOL file "recompile.log"

'UTL_RECOMP_BEGIN:'||TO_CH

--------------------------

utl_recomp_begin: 10:06:24

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

'UTL_RECOMP_END:'||TO_CH

------------------------

utl_recomp_end: 10:06:25

Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit

Production

With the Partitioning and Data Mining options

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

ERROR 2008-11-06 10:24:26




MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text

undefined.


showDialog()

FCO-00011 The step recompileDDIC with step key

|NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_Cr

eateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|i

nd|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|recomp

ileDDIC was executed with status ERROR.

Abort the installtion and proceed as follows

1. Change the umask value entry in the sapinst file to 022

2. Restart the installation.


applnode1:<INSTALL_DIR> > chmod 777 *

applnode1:<INSTALL_DIR> > chmod 777 .


12.6 NetWeaver 7.0SR3 and MaxDB76

If the installation stops with the following error please abort the Installation.

Should be fixed since NetWeaver 7.0SR2.

INFO[E] 2006-03-14 10:20:53 [syuxcuser.cpp:1813]

CSyUserImpl_getOsInfos(ILogBook *m_logBook, iastring sName, iastring

sID, tSyUserInfo& msUserinfo)

FSH-00006 Return value of function getpwnam(undefined) is NULL.

TRACE [syuxcuser.cpp:1493]

bool CSyUserImpl::isExistingOnOS()

checking existence of account user="undefined" succeeded with false.

ERROR 2006-03-14 10:20:53 [syuxcuser.cpp:278]

CSyUserImpl::CSyUserImpl(const CUserData&, bool)

FSL-01027 Account user="undefined" does not exist.

TRACE [iaxxejsbas.hpp:379]

handleException<ESyException>()

Converting exception into JS Exception ESyException.

ERROR 2006-03-14 10:20:53




MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text

undefined.

TRACE [iaxxejsbas.hpp:451]

EJS_Base::dispatchFunctionCall()

JS Callback has thrown unknown exception. Rethrowing.


showDialog()

FCO-00011 The step sdb_create_volumes_fs with step key

|NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDB|ind|ind|ind|ind|9|0|NW_ADA_DB|in

d|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|2|0|SdbInstanceDialogs|ind|

ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_create_volumes_fs was


TRACE [iaxxgenimp.cpp:651]

showDialog()

1. Logon to one of the control nodes:

cn1:~#> cd /FlexFrame/volFF/os/Linux/<image_name>/root_img/etc/opt

cn1:~#> ls –l sdb

2. If the sdb file does not exist, go to section ―MaxDB 7.5/7.6/7.7 /etc/opt/sdb‖ on page

139.

cn1:~#> rm sdb

cn1:~#>

cp –p /FlexFrame/volFF/pool-<pool_name>/sapdb/<image_name>/sql/sdb .



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

cn1:~#> cd /FlexFrame/volFF/os/Linux/<image_name>/root_img/etc/opt

cn1:~#> rm sdb

cn1:~#> ln –s /sapdb/sql/sdb .



12.7 NetWeaver 7.0SR3 MaxDB76 and SLES9_x86/SLES10_x86

During the ABAP import using MaxDB76 and SLES9/SLES10 the installation has

permission trouble:



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

showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ADA -importDirs

/sapcd/SAP_SW/NW2004sSR1/DVD_NW_2004s_SR1_Installation_Export/EXP1

:/sapcd/SAP_SW/NW2004sSR1/DVD_NW_2004s_SR1_Installation_Export/EXP2:/sapcd/SAP_SW/N

W2004sSR1/DVD_NW_2004s_SR1_Installation_Export/EXP3 -installDir

/usr/sap/BLM/install/DB -orderBy "" -r3loadExe /usr/sap/BLM/SYS/exe/run/R3load -

tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs "

-nolog -c 0" -trace all -sapinst" finished with return code 2. Output:

java version "1.4.2"

Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)

IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142ifx-20051125

(JIT enabled)

J9VM - 20050524_1742_LHdSMr

JIT - r7_level20050518_1803)

java.io.FileNotFoundException:

/usr/sap/BLM/install/DB/import_monitor_cmd.properties (Permission denied)

Required system resources are missing or not available:

DDL control file '/usr/sap/BLM/install/DB/DDLADA.TPL' does not have read access.

ERROR 2008-11-06 11:27:58


CJS-30022 Program 'Migration Monitor' exits with error code 2. For details see log

file(s) import_monitor.java.log, import_monitor.log.


showDialog()

FCO-00011 The step runMigrationMonitor with step key

|NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_AB

AP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigratio

nMonitor was executed with status ERROR .

INFO 2008-11-06 11:31:08 [iaxxgenimp.cpp:787]

Do not abort the installtion.

1. Change the permissions of the file DDLADA.TPL

2. Click on the RETRY button to restart the installation.

applnode1:<INSTALL_DIR> > chmod 777 DDLADA.TPL

12.8 NetWeaver 7.0SR3 MaxDB76

If you receive an error message sdb_create_db_instance during the DB installation,

please proceed as follows:



ERROR 2008-11-06 11:25:45

FCO-00011 The step sdb_create_db_instance with step key

|NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_Cr

eateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|

ind|ind|ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|

ind|ind|0|0|sdb_create_db_instance was executed with status ERROR .

XCMDOUT.LOG (Example: SID=CSM, Password=password)

XCMDOUT.LOG

> Subprocess starts at 20060706112543

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

db_create CSM CONTROL,******** sqdcsm,password

Start subprocess as user with uid: root

> Subprocess stops at 20060706112545

ERR

-24875,ERR_NEEDADMI: The operating system user is not a member of the database

administrators group

-24994,ERR_RTE: Runtime environment error

20145,UNIX password ********

1. Follow the instructions of SAP note: 965346

2. Click on the RETRY button from the SAPINST screen.

12.9 NetWeaver 7.0SR3 and EP

The TCP kernel parameters tcp:tcp_conn_hash_size=23768 and

tcp:tcp_time_wait_interval=60000 are not set automatically in a FlexFrame

environment. These parameters should be set for EP.

If the installation stops with the following error do not abort the SAPINST installation:

Error: Aborted: development component 'irj'/'sap.com'/'SAP

AG'/'7.0004.20050921183647.0000':

Caught exception while checking the login credentials for SAP J2EE Engine. Check

whether the SAP J2EE Engine is up and running.

com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to

Host: [jcolp] with user name: [Administrator]

Check your login information.

Exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while

trying to get InitialContext. [Root exception is




com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new

RemoteLoginContext instance.]

1. Open the SAP J2EE Engine Config Tool

2. Change the bindHost settings as it is shown below:

p4 port: host name jc<sid>

Do not forget to restart the JC instance manually

3. Click on the RETRY button at the SAPINST screen.



12.10 NetWeaver 7.0SR3 ABAP+JAVA-AddIn

The installation steps of ASCS (if selected) and Database (Oracle or MaxDB) are fullfilled. During the installation of the CI instance the following error could occurre: steps

Example:

SID=XOS, ORACLE10R2, PI

TYPE=A<BR>STATE=<BR>INFO_SHORT=com.sap.sld.api.wbem.exception.CIMCommunicationException: com.sap.sld.api.wbem.exception.CIMCommunicationException:

CIM_ERR_FAILED: IO error: Read timed out

at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.send(WBEMHttpRequestSender.java:158)

at com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:720)



at com.sap.sld.api.wbem.client.WBEMRemoteClient.referencesImpl(WBEMRemoteClient.java:375)

at com.sap.sld.api.wbem.client.WBEMClient.references(WBEMClient.java:1773)

at com.sap.sld.api.wbem.client.WBEMClientUtil.referencesComplete(WBEMClientUtil.java:490)

at com.sap.lcr.pers.delta.importing.SAPCRUpgrade.collectAssociationsForRestoration(SAPCRUpgrade.java:700)

at com.sap.lcr.pers.delta.importing.SAPCRUpgrade.delete(SAPCRUpgrade.java:355)

at com.sap.lcr.pers.delta.importing.ImportHandler.loadFullImport(ImportHandler.java:1765)

at com.sap.lcr.pers.delta.importing.ImportHandler.loadImpl(ImportHandler.java:1605)

at com.sap.lcr.pers.delta.importing.ImportHandler.load(ImportHandler.java:1573)

at com.sap.ctc.util.SLDConfig.importSldContent(SLDConfig.java:812)

at com.sap.ctc.util.SLDConfig.performFunction(SLDConfig.java:154)

at com.sap.ctc.util.ConfigServlet.doGet(ConfigServlet.java:69)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)




at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)


at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(SocketInputStream.java:129)


at com.tssap.dtr.client.lib.protocol.streams.ChunkedInputStream.readLine(ChunkedInputStream.java:323)

at com.tssap.dtr.client.lib.protocol.streams.ResponseStream.readLine(ResponseStream.java:271)

at com.tssap.dtr.client.lib.protocol.impl.Response.initialize(Response.java:476)

at com.tssap.dtr.client.lib.protocol.Connection.getResponse(Connection.java:2604)

at com.tssap.dtr.client.lib.protocol.Connection.sendInternal(Connection.java:1578)

at com.tssap.dtr.client.lib.protocol.Connection.send(Connection.java:1427)


... 30 more

caused by:



java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)



at com.tssap.dtr.client.lib.protocol.streams.ChunkedInputStream.readLine(ChunkedInputStream.java:323)

at com.tssap.dtr.client.lib.protocol.streams.ResponseStream.readLine(ResponseStream.java:271)

at com.tssap.dtr.client.lib.protocol.impl.Response.initialize(Response.java:476)

at com.tssap.dtr.client.lib.protocol.Connection.getResponse(Connection.java:2604)

at com.tssap.dtr.client.lib.protocol.Connection.sendInternal(Connection.java:1578)

at com.tssap.dtr.client.lib.protocol.Connection.send(Connection.java:1427)





at com.sap.sld.api.wbem.client.WBEMRemoteClient.referencesImpl(WBEMRemoteClient.java:375)

at com.sap.sld.api.wbem.client.WBEMClient.references(WBEMClient.java:1773)

at com.sap.sld.api.wbem.client.WBEMClientUtil.referencesComplete(WBEMClientUtil.java:490)

at com.sap.lcr.pers.delta.importing.SAPCRUpgrade.collectAssociationsForRestoration(SAPCRUpgrade.java:700)

at com.sap.lcr.pers.delta.importing.SAPCRUpgrade.delete(SAPCRUpgrade.java:355)

at com.sap.lcr.pers.delta.importing.ImportHandler.loadFullImport(ImportHandler.java:1765)

at com.sap.lcr.pers.delta.importing.ImportHandler.loadImpl(ImportHandler.java:1605)

at com.sap.lcr.pers.delta.importing.ImportHandler.load(ImportHandler.java:1573)

at com.sap.ctc.util.SLDConfig.importSldContent(SLDConfig.java:812)

at com.sap.ctc.util.SLDConfig.performFunction(SLDConfig.java:154)

at com.sap.ctc.util.ConfigServlet.doGet(ConfigServlet.java:69)





at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)



at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

// => Importing Data : /usr/sap/XOS/SYS/global/sld/model/CR_Content.zip URL=http://cixos:59000 USER=J2EE_ADMIN ...

Import Status: PREPARING

# ERROR: CIM_ERR_FAILED: IO error: Read timed out



1. Open the SAP J2EE Engine Config Tool

2. Change the bindHost settings as it is shown below:

p4 port: host name ci<sid>

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

3. Click on the RETRY button at the SAPINST screen.



12.11 NetWeaver 7.0SR3 JAVA only

The steps installation of SCS and Database (Oracle or MaxDB) are fullfilled. During the

installation of the JC instance the following error could occurre:

Checking if another SDM is running on port 57518

Info: Checking if another SDM is running on port 57518

Info: Start to add definitions of SubstVars.

Info: Used addmode="replace_existing"

Info: Reading substvarfile "SUBS_PARAM_TO_BE_SET.XML".

Error: Can't read from file /usr/sap/P11/install/JC/SUBS_PARAM_TO_BE_SET.XML.

Error: Could not add definitions of SubstVars.

Processing error. Return code: 4

Error: Processing error. Return code: 4

ERROR 2008-11-06 10:26:59 [iaxxinscbk.cpp:271]

abortInstallation

MUT-02041 SDM call of addsubstvars ends with returncode 4

ERROR 2008-11-06 10:26:59


MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text

undefined.


showDialog()

FCO-00011 The step setSubstVars with step key

|NW_Java_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|10|0|NW_CI_Instance_

Configure_Java|ind|ind|ind|ind|3|0|setSubstVars was executed with status ERROR .

1. Change the umask value entry in the sapinst file to 022.



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

12.12 NetWeaver 7.01/SLES 9

Using NetWeaver 7.01 and SLES9 requires a special version of libstdc++ or

libgcc_s. Refer to SAP-Note 1021236.




12.13 SAP 7.0 EHP3

12.13.1 Installation Media Label is wrong

The installation media are not correct. During the installation of the Central Instance you

will get an error message about a wrong label on installation media. Please refer to the

corresponding SAP-Note 1562522

12.13.2 Incompatibilities with Linux Kernel

Installing and starting the SAP system or login via SAPGUI will cause an error message

that the current Linux kernel is not supported (transaction ‗sick‘ cannot be started).

SAPOSCOL may fail because of ‗… cannot determine current Linux …‘.

The behaviour is caused by SAP components which are not at the most current patch

level. Please refer to SAP-Note 1629558 which describes the required patch levels for

the corresponding components.

The SAP-Note 1310037 describes only a shortterm solution. It could affect other services.

12.14 LiveCache

For LiveCache installation you have to

1. make the network interface available for lc<sid>-se

2. use lc<sid>-se for SAPINST_USE_HOSTNAME

3. during installation use lc<sid>-se for liveCache host/server

4. use default password password for user lcaadm (after installation change the

default to a password of your own)

The FA Agents and the start and stop script expect the existence of an alias ―c‖ for xuser.

If it does not exist please use xuser –d SID –n host –se –u control,passw –U c –S SAPR3 –t 0 –I 0

to create. To check creation use xuser list | more.

12.15 ERS – Enqueue Replicated Server (until NetWeaver 2004s SR3)

For installation hints please have a look into corresponding SAP sites (start at http://help.sap.com/saphelp_nw2004s/helpdata/en/f0/b57338788f4d72e




http://help.sap.com/saphelp_nw2004s/helpdata/en/f0/b57338788f4d72e10000009b38f8cf/frameset.htm



10000009b38f8cf/frameset.htm, Standalone Enqueue Server, High Availability,

Configuration the Replication Server).

The hostname must be set to ers<instance#><sid> as defined by the Management

Tool or the ff_sid_adm.pl command.

With NetWeaver 7.0SR1 the scripts startsap or stopsap are (maybe) not prepared to

support ERS instances. Check if the files contain lines like INSTANCEers.



12.16 Installation of SAP Solutions – Post Phase

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

automatically.

1. Check the following links:

applnode1:/etc/init.d # cd /etc/init.d

applnode1:/etc/init.d # ls –l ./rc[3-5].d/*sapinit*

lrwxrwxrwx 1 root root 10 May 18 14:58 rc3.d/K08sapinit -> ../sapinit

lrwxrwxrwx 1 root root 10 May 18 14:58 rc3.d/S14sapinit -> ../sapinit

lrwxrwxrwx 1 root root 10 May 18 14:58 rc5.d/K08sapinit -> ../sapinit

lrwxrwxrwx 1 root root 10 May 18 14:58 rc5.d/S14sapinit -> ../sapinit

2. If the links exists with capital letter ―K‖ or ―S‖, change them to lower case.

Logon to one of the control nodes and proceed as follows:

cn1:~#> cd /FlexFrame/volFF/os/Linux/<image_name>/etc/init.d

cn1:~#> mv ./rc3.d/S14sapinit ./rc3.d/s14sapinit

cn1:~#> mv ./rc3.d/K08sapinit ./rc3.d/k08sapinit

cn1:~#> mv ./rc5.d/S14sapinit ./rc5.d/s14sapinit

cn1:~#> mv ./rc5.d/K08sapinit ./rc5.d/k08sapinit

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

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

PGM_PATH=$0

PGMNAME=sapstartsrv

ARG1=$1

ARG2=$2

ARGUMENTS=$*

USRSAP=/usr/sap/sapservices

SAPSERVICE_PATH=${USRSAP}/sapservices

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

root image read-only.

Installing SAP 7.1


13 Installing SAP 7.1

We only show the different behaviour of the installation in comparison to NetWeaver

2004s SR3. With SAP 7.1 the SAP system contains its own JVM and you do not set your

environment to use SDK from SUN/Novell.


(see chapter 10)

2. Install DB service



4. Install ASCS instance

5. Setting virtual ASCS host All platforms


6. Install CI service




9. Setting virtual Application host All Platforms


10. Install ERS instance

(optional)

All Platforms

(see chapter 13.3 )

Installation Issues Service cannot be started

(see chapter 13.2 )

Installation Issues (optional) EHP installer issues

(see chapter 13.3 )

13.1 Creating a New SID Using ff_sid_adm.pl

Specifying a new SID by ff_sid_adm.pl you can use a simplified syntax :

ff_sid_adm.pl --op add --pool pool1 –-sid S07 --sapversion 7.1

--db MaxDB77:159 --sap ci:57:157:157 --sap ascs:55:155:155

--sap app:58:158:158 --sap ascs:56:156:156

Installing SAP 7.1


The virtual server names are follow a specific syntax. ff_sid_adm.pl determines it by

itself and you do not need to specifiy it

13.2 Service Cannot Be Started

The installer tries to start the services. Sometimes this start request fails.

StartService

FAIL: Service definition not found in /usr/sap/sapservices.

WARNING[E] 2008-09-25 11:57:34.812

CJS-30223 Could not start instance service of instance M06/ASCS04

Please logon as <sid>adm and rename the profiles. Change the physical hostname to

the virtual hostname, e.g.

mv .sapsrc_jer1bx1.sh .sapsrc_ascsm06.sh

mv .sapsrc_jer1bx1.csh .sapsrc_ascsm06.csh

For the database/central instance please logon as <database_user> and rename the

profiles. Change the physical hostname to the virtual hostname (if available), e.g.

mv .dbenv_jer1bx1.sh .dbemv_cim06.sh

mv .dbenv_jer1bx1.csh .dbemv_cim06.csh

mv .dbsrc_jer1bx1.sh .dbsrc_dbm06-se.sh

mv .dbsrc_jer1bx1.csh .dbsrc_dbm06-se.csh

After changing the hostnames you have to start the instances with the start script of

FlexFrame (ff_service.sh …-a start ) and continue with the installation with SAPGUI.

Installing SAP 7.1


If using JAVA engine you have to make sure that all JAVA processes are running before

continuing installation. You can check it by

/usr/sap/M06/DVEBMGS00/exe/sapcontrol -prot NI_HTTP –nr 00

-function GetProcessList

01.10.2008 14:39:32

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

disp+work, Dispatcher, GREEN, Running, Message Server connection ok, Dialog Queue

time: 0.00 sec, AS Java: All processes running, 2008 10 01 14:33:50, 0:05:42, 29434

rslgcoll, Central Syslog Collector, GREEN, Running, 2008 10 01 14:33:50, 0:05:42,

29435

rslgsend, Central Syslog Sender, GREEN, Running, 2008 10 01 14:33:50, 0:05:42,

29436

igswd_mt, , GREEN, Running, 2008 10 01 14:33:50, 0:05:42, 29437

jer1bx5:~ #

With SLES9 you have to start sapcontrol under control of user <sid>adm.

13.3 EHP Installer Issues

13.3.1 Mandatory SMD installation request

With SAP 7.1 EHP1 the SAP installer requests an additional SMD-instance (Solution

Manager Diagostic Agent) to monitor a SAP service, e.g. CI. More information about the

Diagnostic Agent can be found in the corresponding SAP documents.

The SMD instance must be part of a different SID specification. You cannot use the SID

of the current installation. We recommend you to specify an additional SID which should

contain the requested SMD instances. You can use that SID for all SMD instance

requests depending on restrictions like the range of instance numbers.

Please take into account that the SMD instance has to run on the same host as the

monitored SAP instance.

With FlexFrame 5.0 we fully support services of type SMD (release 7.1). If you have used

SMD with older versions we recommend to update to the most current version of SMD

and update your LDAP database to the new requirements.

We recommend using the range of DAA to DAZ for the <sid>. But you are free to use

another range.

Installing SAP 7.1


13.3.2 EHP Installer Requests Entries in /etc/services

Some EHP installers complain:

ERROR> You have to login as root and enter the shadow gateway instance

sapgwxx in /etc/services with

number 33xx:

ERROR> You have to login as root and enter the shadow dispatcher instance

sapdpxx in /etc/services with

number 32xx

We recommend you to introduce the requested ports into /etc/services for the

installation procedure. After the installation is finished remove the entries from the file.

13.3.3 EHP Installer – JAVA process cannot be started

During installation the start of instances (CI, Dialog Instances) does not finish (JAVA

processes do not start). You will see a message box like below

Installing SAP 7.1


To solve the problem:

1. Stop the instance and modify SAP system parametes using configuration tool.

AN> cd /usr/sap/<SID>/<instance>/j2ee/configtool

AN> ./configtool.sh

Installing SAP 7.1


2. Change VM parameter java.security.egd to file /dev/./urandom like below

and click on the Set button:

Please take care for the dot in the path name.

Installing SAP 7.1


3. Click on the diskette symbol to save and restart instance:

Installing SAP 7.1


13.4 ERS

13.4.1 Installation hints

With SAP 7.1 the installation process of ERS is integrated in SAP GUI. If you install ERS

you have to install an ERS instance for ASCS and SCS separably. The screenshots

below show you the installation part for ASCS instance.

cd usr/sap/M02/install/ers01

/mnt/sapcds/Sap_7.1_PI_Sol_Maxdb/Installation/DataUnit/IM_LINUX_X86_64_ADA/sapinst

–extract

./sapinst SAPINST_USE_HOSTNAME=ers01m06 <path_to_product_catalog_file>

Some newer SAP installations require a hostname for ERS instances during installation.

Normally we do not specify a virtual IP for those instances. To prevent that ―sapinst‖ uses

the physical host name we recommend this workaround for all ERS installations:

CN1: ff_hosts.sh –a <virtual ip> -p <pool> -n ers<instnr><sid>

For the virtual IP you can use the IP of the physical host used for the installation.

Installing SAP 7.1


Installing SAP 7.1


1. Change the ERS instance number.

2. If you get the following message box

2.1 Click on Cancel

2.2 Start the instance by ff_service.sh –t ers –s M02 –i 01 –a start

2.3 Change the status value in keydb.xml from ERROR to OK.

Installing SAP 7.1


3. If you have an ERS instance for SCS you have to do the same procedure like in

step 2.

13.4.2 Post Installation Tasks (SAP 7.1 only)

After the installation is completed you remove the host definitions in LDAP by

CN1: ff_hosts.sh -p <pool> -r ers<instnr><sid>

With SAP 7.1 EHP the behaviour in case of a failure of the (A)SCS instance changes.

After the takeover of the replica of the (A)SCS instance the old ERS instance is only

terminated if the SAP profile of the ERS instance contains the line

Start_Program_00 = local $(_ER) pf=$(_PFL) NR=$(SCSID)

Instead of

Restart_Program_00 = local $(_ER) pf=$(_PFL) NR=$(SCSID)

Please check the corresponding profile (<SID>_ERS<instnr>_<host>) and

exchange the string if necessary

Installing SAP 7.3


14 Installing SAP 7.3

SAP 7.3 may be used with ORACLE 11, MAXDB 7.8 and DB2 9.7 only.

From SAP 7.1 on the SAP system contains its own JVM and you do not need to set your

environment to use SDK.


(see chapter 10)

2. SAP 7.3 EHP1 – Oracle ASM Setting up users and groups

(see chapter 14.4)

3. Install DB service



5. Install SCS/ASCS instance All Platforms

(see chapter 14.2)

6. Setting virtual ASCS host All platforms


7. Install CI service




10. Setting virtual Application

host

All Platforms


11. Install optional ERS (SAP

7.3)

All Platforms

(see chapter 14.3)

12. Install ERS instance

(optional)

All Platforms

(see chapter 13.3 )

13. Installation Issues Service cannot be started

(see chapter 13.2 )

14. Installation Issues (optional) EHP installer issues

(see chapter 13.3 )

Installing SAP 7.3


14.1 Creating a New SID Using ff_sid_adm.pl

Specifying a new SID by ff_sid_adm.pl you can use a simplified syntax:

ff_sid_adm.pl --op add --pool pool1 –-sid M02 --sapversion 7.3

--db MaxDB78:159 --sap ci:57:157:157 --sap scs:04:155:155

--sap app:58:158:158 --sap ascs:04:156:156

The virtual server names are following a specific syntax. ff_sid_adm.pl determines it

by itself and you do not need to specifiy it

14.2 SCS/ASCS (SAP 7.3)


.

With SAP 7.3 the ASCS and SCS instances are both installed within one SAPINST call.

We recommend the virtual hostname of the ASCS instance.

Despite of the possibility of SAPINST to install ERS instances with its corresponding

(A)SCS instance you are not allowed to do that within a FlexFrame environment.

Installation of ERS instances have to be an own separate step.

After having installed ASCS/SCS login as User <SID>adm and virtualize the filenames

which include the AN-Name, i.e. change the physical hostname (e.g. bx91-11) to the

virtual hostname (e.g. ascsm02).

In the following example with AN-Name bx91-11 and SID M02 they look like this:

bx91-11:m02adm 17> ls –al | grep bx

-rw-r—r 1 m02adm sapsys … .j2eeenv_bx91-11.csh

-rw-r—r 1 m02adm sapsys … .j2eeenv_bx91-11.sh

-rw-r—r 1 m02adm sapsys … .sapenv_bx91-11.csh

-rw-r—r 1 m02adm sapsys … .sapenv_bx91-11.sh

-rw-r—r 1 m02adm sapsys … .sapsrc_bx91-11.csh

-rw-r—r 1 m02adm sapsys … .sapsrc_bx91-11.sh

Installing SAP 7.3


After modifying the filenames they have to look like this:bx91-11:m02adm

17> ls –al | grep scs

-rw-r—r 1 m02adm sapsys … .j2eeenv_ascsm02.csh

-rw-r—r 1 m02adm sapsys … .j2eeenv_ascsm02.sh

-rw-r—r 1 m02adm sapsys … .j2eeenv_scsm02.csh

-rw-r—r 1 m02adm sapsys … .j2eeenv_scsm02.sh

-rw-r—r 1 m02adm sapsys … .sapenv_ascsm02.csh

-rw-r—r 1 m02adm sapsys … .sapenv_ascsm02.sh

-rw-r—r 1 m02adm sapsys … .sapenv_scsm02.csh

-rw-r—r 1 m02adm sapsys … .sapenv_scsm02.sh

-rw-r—r 1 m02adm sapsys … .sapsrc_ascsm02.csh

-rw-r—r 1 m02adm sapsys … .sapsrc_ascsm02.sh

-rw-r—r 1 m02adm sapsys … .sapsrc_scsm02.csh

-rw-r—r 1 m02adm sapsys … .sapsrc_scsm02.sh

Perform the next steps as User root.

Change the following entry in /usr/sap/sapservices/sapservices :

LD_LIBRARY_PATH=/usr/sap/M02/SCS03/exe:$LD_LIBRARY_PATH; export

LD_LIBRARY_PATH; /usr/sap/M02/SCS03/exe/sapstartsrv

pf=/usr/sap/M02/SYS/profile/M01_SCS03_ascs<sid> -D -u m02admto

LD_LIBRARY_PATH=/usr/sap/M02/SCS03/exe:$LD_LIBRARY_PATH; export

LD_LIBRARY_PATH; /usr/sap/M02/SCS03/exe/sapstartsrv

pf=/usr/sap/M02/SYS/profile/M02_SCS03_scs<sid> -D -u m02adm

In /sapmnt/<SID>/profile/DEFAULT.PFL change the entry

j2ee/scs/host = ascs<sid> to j2ee/scs/host = scs<sid>

In the directory /sapmnt/<SID>/profile change the filename

<SID>_SCS03_ascs<sid> to <SID>_SCS03_scs<sid>.

Installing SAP 7.3


In the file /sapmnt/<SID>/profile/ <SID>_SCS03_scs<sid> change ‗ascs’ to ‗scs’ .

14.3 ERS


With SAP 7.3 the installation process of ERS is integrated in SAP GUI. If you install ERS

you have to install an ERS instance for ASCS and SCS separately. The screenshots

below show you the installation part for ASCS instance.

cd usr/sap/M02/install/ers01

/mnt/sapcds/Sap_7.3_PI_Sol_Maxdb/Installation/DataUnit/IM_LINUX_X86_64_ADA/sapinst

–extract

./sapinst SAPINST_USE_HOSTNAME=ers01m02 <path_to_product_catalog_file>

Some newer SAP installations require a hostname for ERS instances during installation.

Normally we do not specify a virtual IP for those instances. To prevent that ―sapinst‖ uses

the physical host name we recommend this workaround for all ERS installations:

CN1: ff_hosts.sh –a <installation-host-ip> -p <pool> -n ers<instnr><sid>

For the virtual IP you cann use the IP of the physical host used for the installation.

Installing SAP 7.3


Installing SAP 7.3


4. Change the ERS instance number.

5. If you get the following message box

5.1 Click on Cancel

5.2 Start the instance by ff_service.sh –s m02 –t ers –i 01 –a start

5.3 Change the status value in keydb.xml from ERROR to OK.

Installing SAP 7.3


6. If you have an ERS instance for SCS you have to do the same procedure like in

step 2.

14.3.2 Post Installation Tasks

After the installation is completed you remove the host definitions in LDAP by

CN1: ff_hosts.sh -p <pool> -r ers<instnr><sid>

From SAP 7.1 EHP on the behaviour in case of a failure of the (A)SCS instance

changes. After the takeover of the replica of the (A)SCS instance the old ERS instance is

only terminated if the SAP profile of the ERS instance contains the line

Start_Program_00 = local $(_ER) pf=$(_PFL) NR=$(SCSID)instead of

Restart_Program_00 = local $(_ER) pf=$(_PFL) NR=$(SCSID)

Please check the corresponding profile (<SID>_ERS<instnr>_<host>) and

exchange the string if necessary

14.4 SAP 7.3 EHP1

The ‗sapinst‘ offers the options to use Oracle ASM. Whatever you chose the installation

script always tries to create

user ‗oracle‘

group ‗asmadmin‘

group ‗asmdba‘

group ‗asmoper‘

group ‗oinstall‘

Before you start your installation you have to create this user and these groups executing

ff_user_adm.pl –op add –pool <pool> --home /home_sap/oracle --user oracle -

uid <uid> --pass <passwort>

ff_group_adm.pl –op add –pool <pool> --name <group> –guid <guid> \

--member oracle

ff_user_adm.pl –op mod –pool <pool> --user oracle –group oinstall

Installing SAP 7.3


14.5 SAP 7.3 – Linux kernel issue

There are some requirements concerning patchlevel of SAP software with specific Linux

kernel releases. The start of SAP services may fail after upgrading to a newer OS image.

The behaviour is caused by SAP components which are not at the most current patch

level. Please refer to SAP-Note 1629558 which describes the required patch levels for

the corresponding components.

The SAP-Note 1310037 describes only a shortterm solution. It could affect other services.

Install nonclassic SAP services


15 Install nonclassic SAP services

Before starting with the Installation of SAP services on FlexFrame, please refer

to the original SAP installation guides. Please also get the applicable SAP notes

from the SAP Marketplace. This document will not cover the complete SAP

installation process. It shows you only the differences due to FlexFrame

specifics.

Beside classic SAP services, SAP supplies a number of additional services and Addons

which are different in the configuration requirements from classic services. So the

installation procedure changes from one service to another. FlexFrame now supports

some additional nonclassic services. These services are

BOBJ – Business Objects Enterprise 3.1/3.2/4.0

CMS – Content Server 6.40

MDM – Master Data Management 7.1

SMD – Solution Manager Diagnostics 7.1

TREX – Search and Classification 7.1

15.1 BOBJ – Business Objects Enterprise

BOBJ is an Addon services which cannot be installed by sapinst. It has its own

installation scripts. From the FlexFrame perspective it simply needs some configuration

data like a classic SAP service within FlexFrame.

FlexFrame only supports the standard SAP installation using mySQL database (BOBJ

3.x) or IBM DB2 (BOBJ 4.0) for storing BOBJ metadata. It also expects a Tomcat

installation as offered with installation script. All other configurations are handled as

project solutions.

BOBJ is installable within FlexFrame environment. From our point of view there is no

technical reason why it should not work with FlexFrame. But there is a SAP Note

1703318 which contains some hints about operating BOBJ within virtualized

environments.

We strongly recommend you to ask professional service if there are restrictions (defined

by SAP) using BOBJ which are not mentioned int the SAP Note.

This chapter does not cover a complete installation description. If there are specific

questions about installation procedure, e.g. usage of port numbers, please refer to the

origin documentation supplied by SAP.




A BOBJ installation consists of one client instance with the hostname bobj<sid>.

Please follow the main steps shown in the table below:

1. Installation preperations see chapter 15.1.1

2. Install BOBJ BOBJ 3.x: see chapter 15.1.2

BOBJ 4.0: see chapter 15.1.3

3. Post installation see chapter 15.1.4

15.1.1 BOBJ – preparations

Specify the new service either for the initial installation with the Management-Tool or use

ff_sid_adm.pl and setup the directory structures using ff_setup_sid_folder.sh.

CN: ff_sid_adm.pl --op add --pool <pool> –-sid BOB --sapversion 3.2

--bobj <host-ip>

CN: ff_setup_sid_folder.sh –s BOB –p <pool>

On installation node you

Stop the myAMC agents.

Start interface by ff_service.sh –t bobj –s <sid> -a istart.

Set hostname by hostname bobj<sid>.

Copy .cshrc, hostname and hostname_default from an other SAP installation to

/home_sap/<sid>adm.

Set bobj<sid> in hostname_default

Add setenv LC_ALL en_US.utf8 to /home_sap/<sid>adm/.cshrc.

Set bobj<sid> in the file hostname_default of user <sid>adm.

On the control node you add the IP address of bobj<sid> to pool specific

/FlexFrame/volFF/os/Linux/pool_img/<pool>/etc/hosts file.

15.1.2 BOBJ – installation – 3.x

To install the software you login to <sid>adm and

Execute cd /usr/sap/<SID> and use it as directory to install the software into.

Get a valid licence key (needed in installation script). Testlicenses for the installation

purpose can be downloaded from the SAP marketplace.

Execute <bobj-installation-dir>/install.sh to install BOBJ.



The installation of the mySQL database will ask you for a password for the database

administrator (only used for shutdown request). Either you can use a default (set

password to password) or you choose a string of your own. If you do not use the

default you have to create a file /FlexFrame/scripts/log/BOBJ/<sid>.ini

on application node which contains your own password string. That password file is

only considered if the shutdown request is initiated from FA monitoring software.

Install the latest patches (search at http://service.sap.com/swdc).

Download the corresponding process explorer (Polestar) from SAP software

download site

Execute <polestar-installation-dir>/Polstar/install.sh

/usr/sap/<SID>.

15.1.3 BOBJ – Installation – 4.0

SAP renamed the old BOBJ to SBOP (SAP Business Objects BI Platform). We still use

‗BOBJ‘ as service type. Before you start the installation you have to

request a valid licence key (needed in installation script). Testlicenses for the

installation purpose can be downloaded from the SAP marketplace.

After it you login as <sid>adm to install the software by

executing

―<bobj-installation-dir>/…/BusinessObjectsServer_linux/setup.sh

InstallDir=/usr/sap/<SID>‖

.

Instead of using mySQL to store metadata BOBJ 4.0 uses an IBM DB2 database as

default (created with full installation automatically). FlexFrame only supports that default

configuration.

install the latest patches (search at http://service.sap.com/swdc).

download the corresponding process explorer (Polestar; it is renamed to SBOP

Explorer) from SAP software download site.

execute ―<polestar-installation-dir>/…/Explorer_linux/setup.sh

InstallDir=/usr/sap/<SID>"

to install SBOP Explorer.

http://service.sap.com/swdc

http://service.sap.com/swdc



15.1.4 BOBJ – post installation

To install the software you login to <sid>adm and perform

Reset hostname to physical name

Remove entry from pool specific /etc/hosts file

Shutdown interface by ff_service.sh –t bobj –s <sid> -a istop

Restart myAMC agents

15.1.5 BOBJ – Login to CMC (Central Management Console)

You can login to CMC after completion of installation to setup your own environment. To

get the login screen you start your browser and connect to

http://bobj<sid>:8080/CmcApp/logon.faces (BOBJ 3.x)

http://bobj<sid>:8080/BOE/CMC (BOBJ 4.x)

If you will not get the login screen with the system string ‗bobj<sid>:<port>‘ you have to

change ‗bobj<sid>‘ to ‗localhost‘. The port is that one you specified in installation process.

If you specified a password for the login user you have to type in , too.



15.2 CMS – Content Server

Content server requires a http server which has to be installed if not already available in

FlexFrame configuration. Content server requires at least version 2.2.x or higher. It only

works with MaxDB 7.6 (we do not support storing data in a file system; this can only be

supported by a specific project solution). FlexFrame only supports release 6.40 of SAP

Content Server.

The installation process offers the possibility to install the http server into a directory of your own choice. FlexFrame expects the installation in /usr/sap/<SID>. During

installation with sapinst you are, may be, aks for two CMS specific users, ‗sapcs‘ and

‗sapcsc‘ FlexFrame installs the users ‘<sid>cs‘ and ‘<sid>csc‘ per default for CMS and

we recommend to use those ones.

If you want to install http in your own directory or if you want to use userids not equal the

FlexFrame specific actions, it has to be handle project specific.

A CMS installation consists of

a classic MaxDB database, hostname db<sid>-se

a client instance, hostname cms<sid>



Please follow the main steps shown in table below:


2. Install http server see chapter 15.2.2

3. Install CMS see chapter 15.2.3


15.2.1 CMS – preparations

Specify new services either for the initial installation by Management-Tool or using ff_sid_adm.pl and setup directory structures using ff_setup_sid_folder.sh for

later installations.

CN: ff_sid_adm.pl --op add --pool <pool> –-sid CMS --sapversion 6.40

--db maxdb76:<serverip> –cms <clientip>

CN: ff_setup_sid_folder.sh –s CMS –p <pool>

On the installation node you

Stop the myAMC agents

Set interface by ff_service.sh –t cms –s <sid> -a istart

15.2.2 CMS – http server installation

Download http server software (e.g. http-2.2.14.tar) and do the installation

cd <installationdir> /<http-software>

call ‗./configure –with-expat=builtin –prefix /usr/sap<SID>‘

call ‗make‘

call ‘make install‘

15.2.3 CMS – installation

To install the software you login to <sid>adm and execute

cd /usr/sap/<SID>

mkdir /usr/sap/<SID>/install/db

cd /usr/sap/<SID>/install/db

<installationdir>/sapinst -extract

# Prepare userprofile /home_sap/<sid>adm/.cshrc

source $HOME/.dbenv.csh or

source $HOME/.dbenv_`hostname`.csh



# Logon to <sid>adm and create XUSER by ‗xuser –d <SID> -n db<sid>-se –u

Control,control –U c –S SAPR3 –t0 –I 0‘

15.2.4 CMS – post installation

If the installation procedure is finished you

Modify /usr/sap/<SID>/conf/http.conf

● ServerRoot "/usr/sap/<SID>"

● DocumentRoot "/usr/sap/<SID>/htdocs

● Directory "/usr/sap/<SID>/htdocs

● ScriptAlias /cgi-bin "/usr/sap/<SID>/cgi-bin

● Exchange IP in httpd.conf with the IP of the database host in the Server

LAN


Reset interface by ‗ff_service.sh –t cms –s <sid> -a istop

15.2.5 CMS - Migration from project specific solutions

CMS 6.40 is integrated now in FlexFrame 5.0. With previous releases there are project

specific installations which should be migrated to the new environment. We will give you

some hints how to migrate, but dependeng on the project specific environment more or

less steps could be necessary.

Usually you should execute the following tasks

Read the properties of the SID created in project specific approach by

‗ff_sid_adm.pl –op list-all …‘. Note the instance numbers and IP addresses from

the client and server lan interface. Don‘t forget to note the hostnames used in

project‘s solution.

Read the properties of the SID specific users by ‗ff_user_adm.pl –op list …‘.

Users are <sid>adm and the users depending on databased used (ora<sid>,

sqd<sid>, etc.) Note the unique UID of the user.

If you have introduced CMS cache users please get also the data of <sid>cs

and <sid>scs (respective the user names you defined)

Stop the monitoring of the service specific services using ‗ff_service.sh … -a

nowatch‘



Stop the services by ‗ff_services.sh‘ (because of ‗abuse‘ of service type ‗ci‘ in

project specific solution you use ‗-t db‘ instead of ‗-t cms‘; may be you need to

stop the service using SAP‘s scripts manually)

Delete the project specific SID by ‗ff_sid_adm.pl –op del …‘

Add the SID once more using the properties read in previous step by

‗ff_sid_adm.pl –op add …. –users <user-1>:<uid-1,<user-2>:<uid-2> …‘

Do not forget to specify a corresponding client interface using option ‗—cms

<ip>‘.

Create aliases with the old hostnames noticed before by ‗ff_hosts.sh –p <pool> -

a <ip> -n <old-name>‘ for the hostnames used with CMS 6.40 project approach.

15.3 MDM – Master Data Management

MDM is a SAP service which consist of a special database and some services. The

database itself cannot be installed with classic SAP tools like ‗sapinst‘. The database

installation is done using the installation tools supplied by the database vendor or SAP

(see below).

A MDM installion consists of

a classic database service, hostname ‗db<sid>-se‘

one or more instances of type ‗mds‘, hostname ‗mds<nr><sid>‘ and

‗mds<nr><sid>-se‘

one or more instances of type ‗mdss‘, hostname ‗mdss<nr><sid>‘ and

‗mdss<nr><sid>-se‘

one or more instances of type ‗mdis‘, hostname ‗mdis<nr><sid>‘ and

‗mdis<nr><sid>-se‘



2. Iinstall database see chapter 15.3.2

3. Install MDM see chapter 15.3.3


15.3.1 MDM – preparations





A MDM installation can consist of multiple instances of type mds, mdis and mdss. The

type db is mandatory for the first invocation and at least one MDM instance type is

required.

CN: ff_sid_adm.pl --op add --pool <pool> –-sid MDX --sapversion 7.1

--db <dbtype>:<serverip>

-–mdm mds:<nr>:<clientip>:<serverip>

--mdm mdis:<nr>:<clientip>:<serverip>

--mdm mdss:<nr>:<clientip>:<serverip>

CN: ff_setup_sid_folder.sh –s MDX –p <pool>

CN: # Optionally you should create MDM specific groups if necessary

CN: ff_group_adm.pl –op add –pool <pool> --name DB2ADMNS_MDM [ --guid nnnn ]

CN: ff_group_adm.pl -op add -pool <pool> --name DB2USERS_MDM [ --guid mmmm ]



Start the interface by ff_service.sh –t db –s <sid> -a istart

Start the interface by ff_service.sh –t mds –s <sid> -i <nr> -a

istart

Start the interface by ff_service.sh –t mdis –s <sid> -i <nr> -a

istart

Start the interface by ff_service.sh –t mdss –s <sid> -i <nr> -a

istart

15.3.2 MDM – Database installation

MDM can use each type of database

Oracle

MaxDB

DB2

The installation of the database is not part of the SAP installation process. The database

software has to be installed manually.

15.3.2.1 Oracle

To install the Oracle database software you have to



Modify /etc/orainst.loc

inventory_loc=/oracle/<SID>/oraInventory

inst_group=dba

chown –R ora<sid>:dba /oracle/<SID>

login from Control Node to ssh –X <appNode> -l ora<sid>

set environment of ora<sid> setenv ORACLE_HOME /oracle/<SID>/<oraversion>

setenv ORACLE_SID <SID>

setenv ORACLE_BASE /oracle/<MDC> in .dbenv.sh

cd /oracle/stage/<oraversion>/database/SAP

./RUNINSTALLER

Configure Listener (<SID>_LISTENER with Oracle‘s netca

Modify /FlexFrame/vollFF/pool-

<pool>/pooldata/config/…/ora_listener_names on Control Node, insert:

MDC:MDC_LISTENER

Copy files from home_sap/<sid>adm/csh*‟ ,

„/home_sap/<sid>adm/.dbenv.csh‟ , „/home_sap/<sid>/.sapenv.csh

to /oracle/<SID>

In the files .cshrc and .dbenv.* you have to set the SID to the SID of your MDM

database installation.

15.3.2.2 MaxDB

To install the MaxDB database software you have to

Start SDBSETUP from SAP installation media to install server and client software

Follow the instructions of the installation GUI. For further details please use in the

corresponding SAP installation guide for MDM

Create /home_sap/<sid>adm/hostname and

/home_sap/<sid>adm/hostname_default (or copy it from an existing

installation)

Create a link in /home_sap/<sid>adm ‗ln –s .mdmdbenv.csh .dbenv.csh ‗

and ‗ln –s .mdmdbenv.sh .dbenv.sh‘

Insert ‗set dbms_type=ADA‘ into /home_sap/<sid>adm/.mdmdbenv.csh

if not available

Insert ‗source $HOME/.mdmdbenv.csh‘ into .cshrc if not

available



Create an alias for default database user dbm

/sapdb(programs/bin/xuser -d <SID> -n dbmdm-se -u

dbm,<passwort> -U c_J2EE -S SAPR3 -t 0 -I 0

15.3.2.3 DB2

To install the DB2 database software and to create a DB2 database please refer to the

corresponding SAP documentation. You will find the document SAP NetWeaver MDM 7.1

with IBM DB2 for Linux, …‖ at http://service:sap.com/installMDM71.

This document refers to DB2 V9.1 and V9.5. But it is also valid for DB2 V9.7.

The installation in FlexFrame4SAP is like an central server installation. With FlexFrame

there are some installation tasks which differ from the SAP document.

Set the home directory of db2<sid> to /home_sap/db2<sid>

For the DAS user you can use the predefined user ‗dasusr1‘

After the installation of the database software, create a link for db2ls (see chapter

16.7.1)

Insert ‗setenv dbms_type db6‘ and‘ setenv DB2INSTANCE db2<sid>‘ to the

/home_sap/sid<adm>/.cshrc

Extend the variable PATH by /home_sap/db2<sid>/<installdir>/bin and

/home_sap/db2<sid>/<installdir>/adm

Create the database as described in SAP document

Copy .dbenv* from another (DB2) installation to /home_sap/db2<sid> and create

a link for .mdmdbenv_<hostname>.csh or rename the environment files. Make

the changes described in SAP document

Install licenses using db2licm under control of user root.

Modify the DB2 catalog, see chapter 16.7.6.2

15.3.3 MDM – installation

The installation of the three different types differs only in the selection menus of sapinst

and the usage of the server hostname. So we describe here only the installation of type

mds. After each type you should virtualize the environment files of user <sid>adm. To

install the software you login to <sid>adm and execute

cd /usr/sap/<SID>

mkdir /usr/sap/<SID>/install/mds

cd /usr/sap/<SID>/install/mds


Change ‗umask 027‘ to ‗umask 022‘ in sapinst

https://websmp102.sap-ag.de/installMDM71



./sapinst SAPINST_USE_HOSTNAME=mds<nr><sid>

<installationdir>/product.catalog

15.3.4 MDM – post installation

If installation procedure is finished (first installation type) you have to

modify /home_sap/<sid>adm/.cshrc (add)

if ( -e $HOME/.dbenv.`hostname`.csh ) then

source $HOME/. dbenv.`hostname`.csh

else if ( -e $HOME/dbenv.csh ) then

source $HOME/dbenv.csh

endif

copy /home_sap/<sid>adm/csh*, /home_sap/<sid>adm/.dbenv.csh,

/home_sap/<sid>/.sapenv.csh to /oracle/<SID>

add setenv LD_LIBRARY_PATH

${LD_LIBRARY_PATH}:/usr/sap/<SID><typ><nr>/eex to .dbenv.csh

add SAPDBHOST = db<sid>-se to DEFAULT.PFL in directory

/usr/sap/<SID>/SYS/profile/

check if dbms_type is set to db6 in /home_sap/.db*


Reset interfaces by ff_service.sh

15.3.5 MDM - Migration from project specific solutions

MDM 7.1 is integrated now in FlexFrame 5.0. With previous releases there are project











sqd<sid>, etc.) Note the unique UID of the user




nowatch‘

Stop the services by ‗ff_services.sh‘





a <ip> -n <old-name>‘ for the hostnames used with MDM 7.1

Switch to /sapmnt/SID/profile and create links using the new hostnames, e.g.

‗ln –s <SID>_MDS<NN>_ci<sid> <SID>_MDS<NN>_mds<nn><sid>‘

15.4 SMD – Solution Manager Diagnostics

Some installations require a SMD instance per default. To fulfill that request you need to

install SMD instances with a SID not equal to the SID of the instance which should be

monitored. Please take into account that this request can mean a flood of instance

numbers.



After that you are ready to install your monitored instances as usual. If you are asked for

the SMD instance you just have to set it according to your specifications made for SMD

instances.

A SMD installation consists of one or multiple SMD client instances with no own

hostname. The client LAN hostname is always set to the client LAN hostname of the

monitored host (e.g. ci<sid>).

CN: ff_sid_adm.pl --op add --pool <pool> –-sid SMD --sapversion 7.1

–smd <nr>:<monitored hostname> …

CN: ff_setup_sid_folder.sh –s SMD –p <pool>

15.4.1 SMD - Migration from project specific solutions

SMD 7.1 is integrated now in FlexFrame 5.0. With previous releases there are project







Agents from SMD 7.1 are organized within an own SID (agents from different

SAP service SIDs can be putted into a ‗SMD-SID‘

Read the properties of the SID specific users by ‗ff_user_adm.pl –op list …‘. If

you have users specified in in project specific solution.

Make sure that the agents are stopped

Delete the project specific SID by ‗ff_sid_adm.pl –op del …‘ if there are SMD

agent instances available from project solution

Add the SID once more using the properties read in previous steps

corresponding to the SMD 7.1 requirements with FlexFrame 5.0


a <ip> -n <old-name>‘ for the hostnames used with project based SMD

installation if necessary

Switch to /sapmnt/SID/profile and create links using the new hostnames, e.g.

‗ln –s <SID>_MDS<NN>_ci<sid> <SID>_MDS<NN>_mds<nn><sid>‘ if profiles

available from project approach.

15.5 TREX – Search and Classification

A TREX installation consists of one or more TREX instances. The hostnames are set to

trx<nr><sid> and trx<nr><sid>-se.



2. Install TREX see chapter 15.5.2


4. Trouble shooting see chapter 15.5.4

15.5.1 TREX – preparations



CN: ff_sid_adm.pl --op add --pool <pool> –-sid TRX --sapversion 7.1

–trx <nr>:<clientip>:<serverip> …

CN: ff_setup_sid_folder.sh –s TRX –p <pool>



If you set a installation directory of your own it cannot reside in /usr/sap/<SID>

because the installer expects an empty /usr/sap/<SID> and /sapmnt/<SID>



Start the interface by ff_service.sh –t trx –i <instanznr> –s <sid>

-a istart

cd /<installationdir>/ …/support

modify occurrences of watifortrx and sapservices perl –i.bak -p \

-e ―s@/usr/sap/waitfortrex@/usr/sap/<SID>/waitfortrex@g;‖ \

-e

―s@/usr/sap/sapservices@/usr/sap/sapservices/sapservices@g;‖ \

setuplib.py cloneTrex.py uninstall.py

mv installsapinit.sh installsapinit.sh_default

create a new installsapinit.sh and insert exit 0

chmod 755 installsapinit.sh

15.5.2 TREX – installation

There are different ways to install TREX software. A method using ‗sapinst‘ is described

in this section. Please refer also to SAP notes which describe TREX installation issues.

To install the software you login to <sid>adm and perform

cd /<installationdir>


<installationdir>/sapinst SAPINST_USE_HOSTNAME=trx<nr><sid> \

<installationdir>/product.catalog

cd /usr/sap/<SID>/TRX<nr>

mkdir work

chown <sid>adm:sapsys work

15.5.3 TREX – post installation

If the installation procedure is finished you


Reset interface by ff_service.sh –t trx –s <sid> -i <nr> -a istop



15.5.4 TREX – trouble shooting

There are several ways available to install TREX either by a simple installation shell script

or integrated into an installation with ‗sapinst‘. Depending on it the installation can differ .

One known difference is that the profiles are either stored in ‗/sapmnt/<SID>/profiles‘ or in ‘/usr/sap/<SID>/SYS/profiles‘.

Therefore you get a complaint during start of service that the profiles directory is not

found. Then you should create a link to the real files.

Depending on the installation the location of some directories called ‗work‘ are different. If

you get a complaint about missing directory ‗work‘ during service start procesdure please

create the directory manually.

15.5.5 TREX - Migration from project specific solutions

TREX 7.1 is integrated now in FlexFrame 5.0. With previous releases there are project











sqd<sid>, etc.) Note the unique UID of the user


nowatch‘

Stop the services by ‗ff_services.sh‘





a <ip> -n <old-name>‘ for the hostnames used with MDM 7.1

Switch to /sapmnt/SID/profile and create links using the new hostnames,

With newer installations of TREX there will be no START-Profile. You only have

to create a symbolic link ‗ln –s <SID>_TRX<nn>_ci<sid>



<SID>_TRX<nn>_trx<instanznr><sid>‘

If there is a START-Profile you create an additional symbolic link by

‗ln –s START_TRX<nn>_ci<sid> START_TRX<instanznr>_trx<nn><sid>‘

Switch to /usr/sap/<SID>/TRX<instnr>

Create a symbolic link to bind new and old hostname syntax ‗ln –s ./ci<sid>

trx<nn><sid>‘

For user ‗<sid>adm‘ (/home_sap/‗<sid>adm) the files hostname and

hostname_default have to be copied from an other SAP Administrator User.

Modify hostname_default by executing ‗echo trx<instanzr><sid> >

hostname_default‘.

Database Installation


16 Database Installation

The table below shows specific actions necessary depending on the used database

software for your SAP installation.

If you will do an update of your software stack you may get more or less the

same problems as given with an installation from scratch. From our point of view

the descriptions to overcome those problems are described for installations from

scratch are also valid for updates. Sometimes the upgrade script supplied by

SAP is not interruptable like ‗sapinst‘. In case of problems, e.g. read only file

system, you have to execute the steps described to overcome the problems

before you start the upgrade script again.

Installation of Oracle 9.2 All platforms

(see chapter 16.2)

General installation hints

Post installation steps

Patch installation

Installation of Oracle 10.2 All platforms

(see chapter 16.3)



Patch installation

Installation of Oracle 11g

(fully integrated installation

process)

All platforms

(see chapter 16.3)



Patch installation

General post installation

steps for Oracle

TNS listener for Oracle


Contents of listener.ora


hostname in

tnsnames.ora

(see chapter 16.4.3 )

host specific /etc/oratab

(see chapter 16.4.4 )

Installation of SAPDB/MaxDB All platforms

(see chapter 16.6)

Handling of XUSER


Handling /etc/opt/sdb




MaxDB 7.6


MaxDb 7.7


MaxDB 7.8


IO Balancing

Directories for

sapdata/saplog

Installation of DB2 All platforms

(see chapter 7.1 )

Software Requirements

Pre-Installation steps

Installing DB2

LDAP-Plugin

Install SAP

Changes in file system

Install licences

Modification of DB2 catalog

Preparations for backup

Configuration of FA Agents

16.1 Installation of Oracle in General

Installing more then one Oracle databases on a host:

In a FlexFrame environment, Oracle binaries are installed into 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)

Oracle Parameter:

After successful installation of the Oracle software, please check the value of the

following parameters (init<SID>.ora / spfile<SID>.ora):

disk_asynch_io=FALSE

filesystemio_options=directio








Before starting the Oracle RUNINSTALLER (runInstaller for patches or

opatch for interim patches) please check the value of the environment variable

ORACLE_BASE=/oracle/<SID> for the ora<sid> user (.dbenv*.*sh).

In case the startup of the lsnrctl should fail during the SAP installation on

Oracle, please check section listener.ora on page 134.

16.2 Installation of Oracle 9.2

During the Oracle DB installation, a password for ora<sid> has to be set.

You may type in any password you want to, it has no effect.

Only ff_scripts can change a user password.

After the installation has been completed, make sure to import the latest patch

set (read the SAP Notes 539921, 539922, 355776, 509314, and 540021).

The installation procedure will ask for /oracle/<SID>/920_<32/64> and

/oracle/client. All directories will be configured automatically with LDAP. They are

also part of the /etc/auto.master file. Start installation as described in the SAP

installation manual.

16.2.1 Post-Oracle 9.2 Installation Steps

After installation, execute root.sh and use the parameter /oracle/<SID>

instead of the default value (/usr/local/bin).

APPLNODE1:/oracle/C11/920_<32/64> # ./root.sh

Running Oracle9 root.sh script...

The following environment variables are set as:

ORACLE_OWNER= oraC11

ORACLE_HOME= /oracle/C11/920_<32/64>

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

Copying dbhome to /oracle/C11 ...

Copying oraenv to /oracle/C11 ...

Copying coraenv to /oracle/C11 ...

Adding entry to /etc/oratab file...

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root.sh script.








Now product-specific root actions will be performed.



16.3 Installation of Oracle 10.2

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:

/oracle/<SID>/102_<32/64>/network/admin/lsnrctl.ora

/oracle/<SID>/102_<32/64>/network/admin/tnsnames.ora

/sapmnt/<SID>/profile/oracle/tnsnames.ora

16.3.1 Post-Oracle 10.2 Installation Steps

After installation, execute root.sh and use the parameter /oracle/<SID>

instead of the default value (/usr/local/bin).

Example:

SID=OLP

APPLNODE1:/oracle/OLP/101_64 # ./root.sh

Running Oracle10 root.sh script...

The following environment variables are set as:

ORACLE_OWNER= oraolp

ORACLE_HOME= /oracle/OLP/101_64

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

Copying dbhome to /oracle/OLP ...

Copying oraenv to /oracle/OLP ...

Copying coraenv to /oracle/OLP ...

Adding entry to /etc/oratab file...

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root.sh script.

Now product-specific root actions will be performed.

Successfully accumulated necessary OCR keys.

Creating OCR keys for user 'root', privgrp 'root'..

Operation successful.

Oracle Cluster Registry for cluster has been initialized



/bin/cp: cannot create regular file `/etc/init.d/init.cssd': Read-only file system

/bin/ln: creating symbolic link `/etc/rc.d/rc2.d/S96init.cssd' to

`/etc/init.d/init.cssd': Read-only file system

The deamon cssd is only necessary for ORACLE RAC. You can ignore the error

message regarding ―Read-only file system‖.

16.4 Oracle – general post installation steps

16.4.1 TNS Listener for Oracle

Virtualization of SAP Services means that it is possible to run any Oracle instance on any

Application Node. As a result, the listener task (start and stop) is performed

automatically by the FlexFrame sapdb script .

Each TNS listener can have its own listener name. In the /FlexFrame/scripts/

ora_listener_names configuration file, an individual listener name can be assigned to

each <sid>. If the entry for an <sid> is omitted, the standard listener name LISTENER

is valid. Example for /FlexFrame/scripts/ora_listener_names:

#<sid>:<listenername>

C11:MY_LISTENER

C12:YOUR_THING

P10:LISTENER_P10

P12:P12

Technical background

This configuration file for the SAP Service contains the name of the TNS listener if the

default listener name is not used for that DB service. The script to start/stop the Oracle

database uses that file to start the TNS listener in accordance with these entries.

To avoid TNS errors, please do not forget to configure these individual listener names in listener.ora, too.

Oracle 10 only

LSNRCTL:

Check if the correct host name is used in the following files:

/oracle/<SID>/10[1-2]_64/network/admin/lsnrctl.ora

/oracle/<SID>/10[1-2]_64/network/admin/tnsnames.ora

/sapmnt/<SID>/profile/oracle/tnsnames.ora



16.4.2 listener.ora

Every database instance must have its own listener.ora.

The relevant parameter is HOST in the section LISTENER.

On a Linux SLES-9 platform the IP address of db<sid>-se has to be entered .

All other platform accept the virtual hostname. This also applies for

tnsnames.ora.

Otherwise the startup of the lsnrctl will fail with Segmentation error.

Example:

Virtual DB host.

LISTENER =

(ADDRESS_LIST =

..

..

(ADDRESS =

(COMMUNITY = SAP.WORLD)

(PROTOCOL = TCP)

(HOST = db<sid>-se) # Virtual host of the listener

(PORT = 1527)

)

)

Example.

ADDRESS_LIST section:

LISTENER =

(ADDRESS_LIST =

(ADDRESS=

(PROTOCOL=IPC)

(KEY= <SID>.WORLD)

)

(ADDRESS=

(PROTOCOL=IPC)

(KEY= <SID>)

)

)



Example :

SID_LIST section:

(SID_LIST =

(SID_DESC =

(SDU = 32768)

(SID_NAME = <SID>)

(ORACLE_HOME = /oracle/<sid>/<oracle_release>_<32/64>)

# Must be available per automount

)

)

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

On a Linux platform the IP address of db<sid>-se has to be entered. Otherwise the

startup of the lsnrctl will fail with Segmentation error.

16.4.4 Host specific /etc/oratab

Some tools (e.g. dbhome from Oracle) rely on the content of /etc/oratab.

FlexFrame itself does not need /etc/oratab for operation until now.

SAP Solution Manager 7.1 in collaboration with SMD-Agents/SAP Hostagents send

queries to all Oracle database which are contained in pool-specific /etc/oratab. This may

cause a slow down of your system performance or in worst case it means that no further

automount operations are possible.

From patch N1 of FlexFrame 5.1A we will introduce a hostspecific /etc/oratab. Until now

there was a link to /oracle/ora-config/oratab from /etc/oratab. /etc/oratab is now linked to

/var/FlexFrame/etc/oratab. It contains only the SIDs of databases which are currently

running on the application node. The complete content of the old version of /etc/oratab is

available in /oracle/ora-config/oratab. You will find the file following /etc/oratab.shadow.

After installing Oracle database you have to insert the new SID in /etc/oratab.shadow

instead of the old /etc/oratab.



This change is only available with newer root images. If you still use older images you are

not concerned. If you also need this change (because of using new Solution Manager

Software) you have to do a maintenance cycle to introduce the links and files which are

described above.

16.5 Oracle 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).

16.6 Installation of SAPDB / MaxDB

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

required.

SAPDB 7.3:

If you receive the following error messages, the process for calculating the

database space could not check the available space on NFS mounted file

systems:

Sum of all datadevspaces to small for the SAP System

Please change the value of the parameter MIN_DB_SIZE in the

DATABASE.R3S file:

Section: [ADMINDBSIZE_IND_ADA]

MIN_DB_SIZE=15000 <= change the value to 1500

Save the file and restart R3SETUP.

MaxDB 7.5 / 7.6/ 7.7:

The description (gecos) of the sdb user and sqd<sid> users differs from

SAPDB/MaxDB version (or version of sapinst).

The LDAP entry of the depended user must be modified manually to the value

shown in the usermod which failed. To do so please use command

ff_user_adm.pl –op mod –gecos <description> \

--user <user_name> --pool <pool_name>.

MaxDB 7.7/7.8:

Some SAP installers 'sapinst' are not able to read password information from



LDAP correctly because of FlexFrame security enhancements. This should be

fixed by SAP in the near future. Until the fix is available you should use the

workaround described in SAP Note 1548438

There is also an issue using 'dbmverifypw' as described in chapter

Troubleshooting (see chapter 23).

16.6.1 XUSER

After virtualizing a SAPDB/MaxDB instance, the xuser command has to be called with

the correct parameters according to OSS note 39439 and 25591.






The following screenshot shows an example for the SAPMS4 user:

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

16.6.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 there is a problem with the compatibility of the file

.XUSER.62. To solve this problem, the following activities should be performed:

1. Create a subdirectory /sapdb/<SID>/XUSERD on both platforms.

(on the NetApp Filer they will be located in different directories containing the OS).

2. Move the corresponding file /home_sap/<sid>adm/.XUSER.62 to the

subdirectory you created

Repeat this step for the other platform.

3. Create a soft link as follows:

cd /home_sap/<sid>adm

ln -s /sapdb/<SID>/XUSERD/.XUSER.62

Due to the fact that LDAP recognizes the OS, the correct /sapdb directory will be

mounted.




During the installation of a dialog instance, you are asked to enter the host names of the

central and database instances. We recommended using the virtual names (e.g. ciml4,

dbml4-se) in this case since the file .XUSER.62 is replaced when the dialog instance is

installed and must contain the virtual database name.

16.6.2 MaxDB 7.5/7.6/7.7 /etc/opt/sdb

Before installing MaxDB check the existence of file named /etc/opt/sdb.

Take into account that some SAP installers do not follow links (with FlexFrame /etc/opt/sdb is linked to /sapdb/sql/sdb.

You have to

CN: cd /FlexFrame/volFF/os/Linux/<platform>/root_img

CN: mv etc/opt/sdb etc/opt/sdb.bak

CN: touch etc/opt/sdb

CN: ff_exports.pl -op list -nas <file> --path

/vol/volFF/os/<platform>/root_img

/vol/volFF/os/<platform>/root_img -sec=sys,ro,anon=0

CN: ff_exports.pl -op add -nas <file> --path \

/vol/volFF/os/<platform>/root_img \

--option "-sec=sys,ro,rw=<an1-st-lan-ip>,anon=0"

an1: /etc/init.d/autofs restart

an1: remount rw /

If you want to avoid opening root image for write operations and you are sure that the

suggested content fits to your environment you can fill the file /etc/opt/sdb (on Control

Node) with

[Globals]

IndepData=/sapdb/data

IndepPrograms=/sapdb/programs

SdbOwner=sdb

SdbGroup=sdba

After changing the content of the file installation procedure should not need to write into

/etc/opt/sdb.



Check / Create the following directories (from the Application Node):

an1:~# mkdir /sapdb/data/config

an1:~# mkdir /sapdb/data/config/install

If you have made the root directory writeable after the installation process you have to

CN: cd /FlexFrame/volFF/os/Linux/<platform>/root_img

CN: cp etc/opt/sdb /FlexFrame/volFF/pool-<pool>/<platform>/sql/sdb

CN: rm etc/opt/sdb

CN: ln -s /sapdb/sql/sdb /etc/opt/sdb

CN: ff_exports.pl -op add -nas <file> --path

/vol/volFF/os/<platform>/root_img \

--option ―-sec=sys,ro,anon=0"


an1: remount ro /

16.6.3 MaxDB 7.6

During the MaxDB 7.6 DB installation, a password for sqd<sid> has to be set.

Type in the correct password (defined in LDAP) of the user sqd<sid>.



16.6.4 MaxDB 7.7

For user sdb MaxDB 7.7 requires Database Software Owner for the gecos entry in

LDAP.

If you get a message

ERROR 2008-09-18 09:11:46.476

FSL-05014 Command '/usr/sbin/usermod' with parameters '-c "Database Software

Owner" sdb' failed with return code 5: Cannot lock password file: already locked.



set attribute gecos of user sdb in LDAP database to Database Software Owner

(using ff_user_adm.pl).

MaxDB 7.7 (built 02.32 up) requires the directory ―/var/lib/sdb‖. FlexFrame tries to

make that directory available. If the directory is missing please add the directory manually

at Control Node

(switch to /FlexFrame/volFF/os/Linux/<platform>/var_img/*).

16.6.5 MaxDB 7.8

The handling of ‗/etc/opt/sdb‘ fails because of FlexFrame read-only filesystem. You have

to execute

AN: mount <filer>:/vol/volFF/pool-<poolname>/sapdb/Linux.SLES-

<SLESversion>.x86_64/sql /etc/opt

AN: <installdir>/…/SDBINST –global_prog /sapdb/programs –global_data /sapdb/data –

path /sapdb/clients/<SID> -private_datapath /sapdb/clients/<SID>/data –profile

―Runtime For SAP AS‖ –o sdb –g sdba –I CL_<SID> -b

AN: umount /etc/opt

In case of pool specific volFF you have to substitute volFF by the pool specific volFF

volume name in the example above.

There is also a problem during installation by command ‗/usr/sbin/usermod –L sdb‘ You

will see a message like ‗Cannot lock password file: already locked‘. To overcome the

error please change the string ‗ERROR‘ to ‗OK‘ in the file ‗keydb.xml‘.

16.6.6 MaxDB 7.9

MaxDB 7.9 is available for updating current configurations. Until now there is no

integration made in SAP-Installer 'sapinst'.

FlexFrame 5.1A does not fully support MaxDB 7.9 at configuration and administration

level but MaxDB 7.9 can be used in the same way as a MaxDB 7.8 from our point of

view. Simply define MaxDB 7.9 as MaxDB 7.8 in the FlexFrame LDAP database.

We cannot check internally if your MaxDB installations are able to be

updated to MaxDB 7.9. Please refer to corresponding SAP documents to

clarify the dependencies. If there is at least one installation which could

not be updated do not update your installations within pool / pool group !

Upgrading to MaxDB 7.9 means a downtime of your current MaxDB

installations in the concerned pool / pool group because the server

software is changed.



We strongly recommend to take a backup of your current MaxDB

installations before starting the upgrade (executables, configuration files,

etc.).

Before starting the upgrade you should check

If you are using different MaxDB versions handled by splitting the installations

with the feature of pool groups (please read the corresponding best practice

paper) you may change your configuration

Usage of pool groups could mean that specific installations have to be moved to

an existing / new group which handles at least MaxDB versions from 7.8 up

If you want to install a new MaxDB 7.9 you should also check if it is necessary to

use the concept of pool groups. Maybe you need a new pool group which

services MaxDB 7.9.

For new installations use 'ff_sid_adm.pl … --db maxdb7.8:hostid ..' to create the

LDAP entries for new MaxDB.

/etc/opt/sdb file

The updater tries to write into /etc/opt/sdb. Please make sure that the file

is writable. Use the corresponding section 16.6.6.1 within this manual

which handles the issue.

Otherwise your update will fail anyway.

Please check also the latest SAP note 1492467 ‗Supplementary

Information for Upgrade to MaxDB 7.9.‘ and all other SAP notes

describing the upgrade operation for MaxDB 7.9

Now you are ready to update. Please follow the instructions made by the SAP document

"Upgrade to MaxDB Database 7.9: UNIX". Before you start the implementation, make

sure you have the latest version of this document. You can find it at the following location:

http://service.sap.com/instguides -> Database Upgrades -> SAP MaxDB

If the updater requires a running database please start it using 'ff_service.sh'.

After the successful upgrade to MaxDB 7.9 you have to use 'ff_sap_upgrade.pl' to modify

the LDAP setting to 'MaxDB 7.8' as database version.


http://service.sap.com/instguides



16.6.6.1 MaxDB 7.9 (upgrade) - /etc/opt/sdb

The SAP script used to update MaxDB software needs write access to file ‗/etc/opt/sdb‘.

Because of FlexFrame‘s readonly image you have to open the root_img for the timeslice

when running update procedure:

CN: ff_exports.pl -op list -nas <file> \

--path /vol/volFF/os/<platform>/root_img

/vol/volFF/os/<platform>/root_img -sec=sys,ro,anon=0

CN: ff_exports.pl -op add -nas <file> \

--path /vol/volFF/os/<platform>/root_img \

--option "-sec=sys,ro,rw=<an1-st-lan-ip>,anon=0"


an1: remount rw /

After the upgrade you reset the image into state ‗readonly‘:

CN: ff_exports.pl -op add -nas <file> \

--path /vol/volFF/os/<platform>/root_img \

--option ―-sec=sys,ro,anon=0"


an1: remount ro /

16.6.7 IO Balancing

The SAPDB parameter _FBM_LOW_IO_RATE (currently only valid for releases lower than

7.4) can be set to 0 to avoid any balancing of disk usage between devspaces and to

avoid higher snapshot sizes (the default value is 10). This means IO balancing will be

stopped if the IO rate of all devspaces per second is higher than the parameter value 10.

16.6.8 MaxDB configuration files

The configuration files of MaxDB are usually stored in /sapdb/data/config. This may

cause problems because there can be a difference between the snapshot content of

database files and the configuration files stored at default site.



If you want to get a consistent state of the files within snapshot you can move the

necessary configuration files nearby the database files, e.g. /sapdata/sapdata<n>.

You should

create a directory /sapdata/sapdata<n>/<SID>/config

cd /sapdb/data/config

for i in $(ls <SID>*);do

cp -p $i /sapdata/sapdata<n>/config/$i

mv $i ${i}.moved

ln -s /sapdata/sapdata<n>/<SID>/config/$i $i

done

16.6.9 Directories for sapdata / saplog

The path to the sapdata directories is /sapdata/sapdata<n> (analogously for

SAPLOG); a link (only versions lower MaxDB 7.6) from /sapdb/<SID>/sapdata is

created automatically.

Except sapinst from SAP Version 6.40, the SID has to be added.

1. Enter /sapdata/sapdata1/<SID>, e.g.:

/sapdata/sapdata1/P11

2. Set the SAPLOG volumes accordingly.

/saplog/saplog1/P11

16.6.10 MaxDB 7.8/7.9 – performance issue

If there a large number of SAP services using MaxDB 7.8/7.9 (appr. > 20 installations) it

may happen that the 'Service_MaxStartTime' from High Availability monitor expires while

starting a service. The reason is a loop implemented in '.dbenv.csh' which scans through

all installation pathes. You can get rid of the behaviour it you are modifying the script:

# ***********************************************************************

# *** SAP DB RDBMS Environment (R/3 >= 4.6C) ***

# ***********************************************************************

# THIS IS MODIFIED LOGIN SCRIPT TO SET MAXDB ENVIRONMENT



# BEFORE USING IT BE SURE THAT THE PATHES USED HERE ARE

# EXISTING AND THE CL_<SID> INSTALLATION IS EXISTING:

# /sapdb/programs/bin/sdbregview -i CL_$SAPSYSTEMNAME

# RETURNS VALID VALUES

# *********************************************************************

#

setenv dbms_type ADA

set path = (/sapdb/clients/${SAPSYSTEMNAME}/bin:/sapdb/programs/bin $path)

if ( ! $?LD_LIBRARY_PATH ) then

setenv LD_LIBRARY_PATH /sapdb/clients/${SAPSYSTEMNAME}/lib

else

setenv LD_LIBRARY_PATH

${LD_LIBRARY_PATH}:/sapdb/clients/${SAPSYSTEMNAME}/lib

endif

if ( ! $?SAPSYSTEMNAME ) then

switch (ùname`)

case Sun*:

case SIN*:

case Reliant*:

set prompt=´`/usr/ucb/hostname`:`/usr/ucb/whoami` \!% ´

breaksw

default:

set prompt=´`hostname`:$LOGNAME \!> ´

breaksw

endsw

endif



16.7 SAP Installation with Database DB2

With the current release of FlexFrame we support DB2 database also with the

Management Tool.

16.7.1 Installing DB2

The installation is not fully integrated within sapinst unitl NetWeaver 2004s SR2. With

SAP 7.0 SR 3 sapinst supports also installation of DB2. So you need to execute an

additional step to make the DB2 software available only if a SAP version older versions

than SAP 7.0 SR3 is used.

There are two ways to install the database software. Both methods are possible. The

second method should be sufficient with SAP installations.

We recommend you to install the software to an SID specific directory.

Our recommendation would be /db2/<sid>/<something>.

Install software using db2setup.

On the path your DB2 software DVD is available (example Linux) you make a switch to /LINUXX86_64/ESE/disk1 and call

./db2setup.

You have to choose an standard installation with no creation of a DB2 instance. Use the dasusr<#> for your installation. dasusr1 is available with FlexFrame. If you

want to use another one you must fulfill the requirement of the user‘s name, dasusr<#>. You can create that user using ff_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 ff_group_adm.pl.

Install software using a response file with the following content:

PROD=ENTERPRISE_SERVER_EDITION

FILE=/db2/LB4/db2soft

LIC_AGREEMENT=ACCEPT

INSTALL_TYPE=TYPICAL

LANG=EN

CONFIG_ONLY=NO

and run

db2setup –I en –l <log> -t <trace> -r <full_path_to_response_file>



In both cases you get a complaint that the installation could not handle the link from /usr/local/bin/db2ls to /db2/LB4/db2soft/install/db2ls.

Create that link after running db2setup, not before !!!

If you do not install DB2 for the first time, delete the link before running db2setup and

create it again afterwards. Otherwise db2setup will not finish with a log message.

In Linux you create the link on Control Node using (example)

/FlexFrame/volFF/os/Linux/<image_name>/root_img/usr/local/bin:

ln –s /db2/LB4/db2soft/installation/db2ls db2ls

16.7.2 LDAP-Plugin

Sometimes it is possible to get error messages while connecting to the database. It

seems that depends on the SAP installation package and the operating system you do

the installation. We recommend to install the available LDAP plugin. Upon the

recommendation of IBM the installation of the plugin is requested because of support

reasons. The availability of the LDAP-Plugin is also a request of IBM to get support in

cases of errors. You can request that Plugin from IBM site

http://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&so

urce=swg-dm-db2ldap

Copy the IBMLDAPauthserver.so (example Linux) to

/home_sap/db2<sid>/sqllib/security64/plugin/server.

Copy the IBMLDAPSecurity.ini to /home_sap/db2<sid>/sqllib/cfg and adapt

the following lines to your system environment:

LDAP_HOST = <controlNode1>-se <controlNode2>-se

USER_BASEDN = ou=People,ou=pool1,ou=Pools,…,dc=…

USER_OBJECTCLASS = posixAccount

GROUP_BASEDN = ou=Group,ou=pool1,ou=Pools,…,dc=…

GROUP_OBJECTCLASS = posixGroup

SEARCH_DN = cn=root,ou=LDAPadmins,ou=FlexFrame,…,dc=…

SEARCH_PW = <your_password>

To enable the changes you perform

db2 update dbm cfg using SRVCON_PW_PLUGIN IBMLDAPauthserver





It is necessary to restart the database (db2stop, db2start as user db2<sid>) to activate the changes.

16.7.3 Transparent LDAP

Security enhancements need a correct LDAP configuration. Otherwise

nobody can connect to DB2 databases furthermore.

As of DB2 Version 9.5, FixPack 5, DB2 introduces ‗Transparent LDAP authentication‘.

This means it should be used instead of the former configuration of the LDAP-Plugin.

Information about the new feature is available at

Transparent LDAP authentication at IBM sites.

From our current point of view there are the following actions available to use the

feature in FlexFrame environment:

Check if the file ‗/etc/pam.d/db2‘ exists on your application nodes hosting DB2

databases

If ‗/etc/pam.d/db2‘ does not exist change your image (maintenance cyle) and

create the file. The required content is:

#%PAM-1.0

auth sufficient pam_unix2.so

auth required pam_ldap.so usr_first_pass

account sufficient pam_unix2.so

account required pam_ldap.so

password required pam_pwcheck.so

password sufficient pam_unix2.so use_authtok use_first_pass

password required pam_ldap.so use_first_pass

session required pam_unix2.so

Make the new image(s) available to your Application Nodes

Stop monitoring DB instance by 'ff_service.sh'

Login as user ‗db2<sid>‘ and execute the following actions

db2set DB2AUTH=OSAUTHDB

db2stop

db2start




Test connection using ‗db2 connect to <SID> user <dbuser> using <password>‘

Activate monitoring DB instance by 'ff_service.sh'

For detailed information and if there are any trouble please refer to the IBM sites.

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

16.7.5 Changes in System Files

The virtual db hostname (db<sid>-se) is written to /etc/hosts by ff_sid_adm.pl.

The services needed for DB2 are inserted into /etc/services (you can look for the

service names also into LDAP searching for services like DB2_db2<sid> and

sapdb2<SID>).

ff_sid_adm.pl tries to modify the system files of all possible files in a pool. But if you

exchange your image or run ff_new_an.sh the changes are (maybe) lost. If a

ff_new_an.sh is called, FlexFrame tries to do an update of the corresponding system

files internally. No user action should be required. If the automatism with ff_new_an.sh

fail you have the possibility to enter

ff_sid_adm.pl –op db2adm –pool <pool> --sid <sid>

to start the modification manually.

16.7.6 Post Installation Steps

It is strongly recommended to do the following actions after the installation of all instances

are completed successfully. Otherwise the installation of some instances can fail. It

seems to be a problem when using JAVA instances, not with ABAP.

16.7.6.1 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 chapter 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.




1. Install the license of DB2 V9. 1 as db2<sid> user by the following commands:

db2licm –a db2ese_c.lic

db2licm –a db2dpf.lic

db2licm –a db2so.lic

db2licm –a db2hf.lic

2. Install the license of DB2 V9. 5 as db2<sid> user by the following commands:

db2licm –a db2ese_c.lic

db2licm –a db2poese.lic

db2licm –a db2dpf.lic

db2licm –a db2so.lic



3. 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 (DB2 V9.1 only)

Performance Optimization ESE (DB2 V9.5 only)

16.7.6.2 Modifying DB2 Catalog

After you installed your database you have to adapt the database catalog using

(executed as db2<sid>):

db2 uncatalog db <SID>

db2 uncatalog db <SID>L

db2 uncatalog node NODE<SID>

db2 catalog db <SID> as <SID> on /db2/<SID>

db2 catalog tcpip node NODE<SID> remote db<sid>-se server sapdb2<SID>

remote_instance db2<sid>

db2 catalog db <SID> as <SID>L at node NODE<SID>

The command db2 uncatalog node NODE<SID> may be causes errors. That can be

ignored.

After modifying the catalog entries you can only connect do the database using

db2 connect to <sid> user <name> using <password>. We recommend to do the

action if your instance installations are completed.

This behaviour is only given if you catalogued your DB2 database concerning the hints

made in FlexFrame 4.1A00. We recommend you to change the catalog with the

commands shown above to get rid of this behaviour.

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 = EH4

Database name = EH4

Local database directory = /db2/EH4

Database release level = c.00

Comment =

Directory entry type = Indirect

Catalog database partition number = 0

Alternate server hostname =

Alternate server port number =

Database 2 entry:

Database alias = EH4L

Database name = EH4

Node name = NODEEH4

Database release level = c.00

Comment =

Directory entry type = Remote

Catalog database partition number = -1

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 = NODEEH4

Comment =

Directory entry type = LOCAL

Protocol = TCPIP

Hostname = dbEH4-se

Service name = sapdb2EH4

16.7.6.3 Preparations for backing up DB2

DB2 installation process creates a directory /db2/<SID>/db2<sid> to store files for

administering backup operations. To support consistent backup operation you should

move the directory to /db2/<SID>/dbhome and create a link by

ln -s /sapdata/dbhome/<SID>/db2<sid> /db2/<SID>/db2<sid>



on an Application Node after the installation procedure.

With newer release of FlexFrame the link is already created by

ff_setup_sid_folder.sh.

In case of SAN configurations the path is adapted to the syntax used for pathes on SAN

(/var/FlexFrame/SAN/db2/DB2/dbhome/db2<sid>).

16.7.6.4 DB2-Fixpack issues

Installations of newer DB2 FixPacks (e.g. V9.7 FP4SAP) may cause the problem that the

database cannot be startet on a host not equal host of installation process (timeout of

command ‗db2gcf –u –i db2<sid>‘ to start database instance).

The reason could be the directory ‗var/db2‘. Please check the existence of that directory

on the other application nodes and if necessary copy it to all application nodes which

should run the database.

Because of FlexFrame‘s security options SAP installer will not work properly with DB2 9.7

FP4 (‗unable to determine whether account has password‘).. See also SAP Note

1548438. To overcome this installation issue you have to modify FlexFrame‘ security

options for period of the installation procedure (only if Note 1548438 does not solve your

problem).. You have to

In /FlexFrame/volFF/FlexFrame/ldap/common/slapd_acl.conf: exchange the

string 'by peername.ip…. auth' to 'by peername.ip…. read'

restart ldap master using 'ff_ha_cmd.sh restart ldap_master' (control node)

restart nscd using 'rcnscd restart' (application node)

restart SAP installation procedure

after finishing your database installation reset 'read' to 'auth' in

/FlexFrame/volFF/FlexFrame/ldap/common/slapd_acl.conf

restart ldap_master

restart nscd

16.7.7 Configuration of FA Agents

With FlexFrame 5.0 the DB2 support is part of the default installation of FA Agents.


Migration – SLES9 to SLES10 / SLES11


17 Migration – SLES9 to SLES10 / SLES11

Until FlexFrame 5.0A we make a difference between supported platforms for directories

to store executables. But now there is no difference made in the binaries installed by

SAP. If you plan a migration from SLES9 to SLES10 you can switch the directory

structure by introducing symbolic links.

We guess you installed your systems on SLES9 in the past and change now to

application nodes with SLES10. You do not copy any data from the SLES9- to SLES10-

directories.

The following directories are concerned

/FlexFrame/volFF/pool-<pool>/oracle

ln –s Linux.SLES-9.x86_64 Linux.SLES-10.x86_64

/FlexFrame/volFF/pool-<pool>/sap/sapmnt/<SID>


/FlexFrame/volFF/pool-<pool>/sap/hostctrl


/FlexFrame/volFF/pool-<pool>/sapdb


/FlexFrame/volFF/pool-<pool>/db2


For a migration to SLES11 you only change the the symbolic links to ‗Linux.SLES-

11.x86_64‘.There is furthermore no distinction between architectures using 64 Bit and 32

Bit.

OR

Migration – SLES9 to SLES10 / SLES11


for future use we recommend to create a new directory ‗SLES‘ in /FlexFrame/volFF/pool-

<pool>/<subdir> (values of subdir are: oracle, sapmnt/<SID>, sap/hostctrl, sapdb and

db2). Where needed you add a link to the new directory. The example shows you the

handling of Linux.SLES-11.x86_64

mkdir /FlexFrame/volFF/pool-<pool>/oracle/SLES

cd /FlexFrame/volFF/pool-<pool>/oracle

rm Linux.SLES11.x86_64

ln –s SLES Linux.SLES11.x86_64

mkdir /FlexFrame/volFF/pool-<pool>/ sap/sapmnt/<SID>/SLES

cd /FlexFrame/volFF/pool-<pool>/sap/sapmnt/<SID>



mkdir /FlexFrame/volFF/pool-<pool>/ sap/hostctrl/SLES

cd /FlexFrame/volFF/pool-<pool>/sap/hostctrl



mkdir /FlexFrame/volFF/pool-<pool>/sapdb/SLES

cd /FlexFrame/volFF/pool-<pool>/sapdb



mkdir /FlexFrame/volFF/pool-<pool>/db2/SLES

cd /FlexFrame/volFF/pool-<pool>/db2


ln –s SLES Linux.SLES11.x86_64.

Another possibility could be.that you have only installations using Linux.SLES-10.x86_64

and you will make no distinctions of the platforms in the future you rename the directory

‗Linux.SLES-10.x86_64‘ to ‗SLES‘ and set your links as shown before for this

configuration ‗ln –s SLES Linux.SLES-10.x84_64‘. If you plan to install in a environment

using ‗LINUX.SLES-11.x86_64‘ you just set a new link to ‗SLES‘ by ‗ln –s SLES

Linux.SLES-11.x84_64‘.

Post-SAP Installation Steps


18 Post-SAP Installation Steps

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

The example in chapter 18.1.6 is valid for all other SAP releases.

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

applnode1: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 ff_hosts.sh.

Example.

Central instance host:

Looking for IP address of CI: getent hosts | grep ci<sid>

Adding alias to LDAP: ff_hosts.sh –p <pool_name> -a <ip@> -n <fqdn>

18.1 Configuring the Virtual Host Name Manually

The scripts of the start and stop mechanism for SAP solutions use the UNIX hostname

command to determine on which host they are started. This command, however, supplies

the physical node name of the host and not the required virtual host name.

You have to check that every user profile file of the SAP Administrator or Database user

does not contain a physical hostname within user profile file name. If you find a real

hostname you have to change the physical hostname to the virtual hostname.

Example:

Physical hostname: tom1bx1

Virtual hostname: ci<sid> (SAP Central Instance)

Move .saprc_tom1bx1.sh to .saprc_ci<sid>.sh.

Check if .dbenv.[c]sh and .sapenv.[c]sh already exist. If the files do not exist

please create a softlink, e.g. ln –s .dbenv_db<sid>.[c]sh .dbenv.[c]sh.



With sapinst from SAP 6.40 you have always to create the softlink.

To avoid changing all standard scripts that use the hostname command, this command

is simply replaced by a script of the same name for the adm and db users. The script then

always supplies the desired virtual host name. This requires the following adaptation:

Insert the following line at the beginning of the .cshrc login script in $HOME of

<sid>adm, ora<sid>(Oracle) and sqd<sid> (SAPDB/MaxDB):

# File hostname is generated to enable the virtual hostname,

# an alias activates it.

# .cshrc and .profile must contain:

# csh:

alias hostname "echo `~/hostname`"

# bash, ksh:

alias hostname="echo `~/hostname`"

If bash or sh is used as the login shell instead of csh, the relevant line has to be

activated for it.

The ~/hostname script is generated again with the matching virtual host name each

time the application or service is started by means of the ―Start script for virtualizing the

applications‖.

Virtual host name

applnode1:oraosm 56> vi .cshrc

#File hostname is generated to enable the virtual hostname

#the following alias activate it.

alias hostname "echo `~/hostname`"

applnode1:oraosm 4% vi hostname

#!/bin/bash

if [ ! -z "$VHOSTNAME" ]

then echo $VHOSTNAME

else ~/hostname_default

fi

applnode1:oraosm 7% vi hostname_default

echo ciosm



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

Proceed with the following modifications:

/home_sap/<sid>adm

After installation, rename the installed .*_<phys_hostname>.*sh

to .*_ci<sid>.*sh.

/sapmnt/<SID>/profile

Change the profile names from *_<phys_hostname> to *_ci<sid>.

DEFAULT.PFL

SAPGLOBALHOST=ci<sid>

DBHOSTNAME=db<sid>-se.

Instance Profile

SAPLOCALHOST=ci<sid>

Start Profile

Change all host names (containing the physical host names) to ci<sid>.

Additional for 4.6C SR2:

/home_sap/<sid>adm

Change the file names for start/stop to new the virtual host name ci<sid>.

/home_sap/<sid>adm

In all files change the host name to ci<sid>.

/home_sap/<sid>adm

Delete the following line in *.cshrc:

Case Linux.

18.1.2 Database Instance (also valid for WebAS 6.40 J2EE)


/oracle/<SID>


to .*_db<sid>-se.*sh.

Create a symbolic link from .*_db<sid>.*sh to .*_db<sid>-se.*sh.



Example:

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

-> .dbenv_dbq85-se.csh

lrwxrwxrwx 1 oraq85 dba 18 2005-04-06 11:33 .dbenv_dbq85.sh

-> .dbenv_dbq85-se.sh

/oracle/<SID>/<Oracle_Version>_<32/64>/network/admin

Change the host name in the files listener.ora and tnsnames.ora from

<phys host name> to the IP address of db<sid>-se

(don‘t use the virtual host name!).

/home_sap/<sid>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 .cshrc of <sid>adm to look for the profile names and create the

corresponding link.

18.1.3 Application Instance (not valid for WebAS 6.40 J2EE)


/home_sap/<sid>adm


to .*_app<id><sid>.*sh.


Change the profile names from *_<phys_hostname> to *_app<id><sid>.

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

Change all host names (containing the physical host names) to app<sid> in the

start profile.



Additional Modifications for 4.6C SR2:

/home_sap/<sid>adm

Change the file names for start/stop to the new virtual host name app<id><sid>.

/home_sap/<sid>adm

In all files change the host name to app<id><sid>.

/home_sap/<sid>adm

Delete the following row in *.cshrc: ―Case Linux...‖.

18.1.4 SCS Instance


/home_sap/<sid>adm


to .*_scs<id><sid>.*sh.


Change the profile names from *_<phys_hostname> to *_scs<id><sid>.

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

Change all host names (containing the physical host names) to scs<sid> in the

start profile.

Example:

Instance Profile

SID=LO7 Instance=68

SAPSYSTEMNAME = LO7

SAPSYSTEM = 68

INSTANCE_NAME = SCS68

DIR_CT_RUN = $(DIR_EXE_ROOT)/run

DIR_EXECUTABLE = $(DIR_INSTANCE)/exe

SAPLOCALHOST = scslo7

OS_UNICODE = uc

#-----------------------------------------------------------------------

# SAP Messaging Service for Java

#-----------------------------------------------------------------------

rdisp/msserv = 0

rdisp/msserv_internal = 3968



ms/standalone = 1

ms/server_port_0 = PROT=HTTP,PORT=81$$

#-----------------------------------------------------------------------

# SAP Locking Service

#-----------------------------------------------------------------------

enque/serverinst = 68

enque/table_size = 4096

rdisp/enqname = $(rdisp/myname)

enque/snapshot_pck_ids = 100

Example:

Start Profile

SAPSYSTEMNAME = LO7

SAPSYSTEM = 68




SAPLOCALHOST = scslo7

DIR_PROFILE = $(DIR_INSTALL)/profile

_PF = $(DIR_PROFILE)/LO7_SCS68_scslo7

SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)

SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)

SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)

#-----------------------------------------------------------------------

# Copy SAP Executables

#-----------------------------------------------------------------------

_CPARG0 = list:$(DIR_CT_RUN)/scs.lst

Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)

OS_UNICODE = uc

#-----------------------------------------------------------------------

# Start SAP messaging service

#-----------------------------------------------------------------------

_MS = ms.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)

Execute_01 = local rm -f $(_MS)

Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/msg_server$(FT_EXE) $(_MS)

Start_Program_00 = local $(_MS) pf=$(DIR_PROFILE)/LO7_SCS68_scslo7

#-----------------------------------------------------------------------

# Start SAP locking service

#-----------------------------------------------------------------------

_EN = en.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)

Execute_03 = local rm -f $(_EN)

Execute_04 = local ln -s -f $(DIR_EXECUTABLE)/enserver$(FT_EXE) $(_EN)

Start_Program_01 = local $(_EN) pf=$(DIR_PROFILE)/LO7_SCS68_scslo7



18.1.5 ASCS Instance (WebAS 7.00)


/home_sap/<sid>adm

After installation, rename the installed .*_<phys_ hostname>.*sh

to .*_ascs<id><sid>.*sh.


Change the profile names from *_<phys_hostname> to *_ascs<id><sid>.

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

Change all host names (containing the physical host names) to ascs<sid> in the

start profile.

Example:

Instance Profile

SID=LO7 Instance=67

SAPSYSTEMNAME = LO7

SAPSYSTEM = 67

INSTANCE_NAME = ASCS67



SAPLOCALHOST = ascslo7

#-----------------------------------------------------------------------

# SAP Messaging Service parameters are set in the DEFAULT.PFL

#-----------------------------------------------------------------------

ms/standalone = 1

ms/server_port_0 = PROT=HTTP,PORT=81$$

#-----------------------------------------------------------------------

# SAP Locking Service

#-----------------------------------------------------------------------






Example:

Start Profile

SAPSYSTEMNAME = LO7

SAPSYSTEM = 67

INSTANCE_NAME = ASCS67



SAPLOCALHOST = ascslo7

DIR_PROFILE = $(DIR_INSTALL)/profile

_PF = $(DIR_PROFILE)/LO7_ASCS67_ascslo7

SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)

SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)

SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)

#-----------------------------------------------------------------------

# Copy SAP Executables

#-----------------------------------------------------------------------

_CPARG0 = list:$(DIR_CT_RUN)/scs.lst

Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)

#-----------------------------------------------------------------------


#-----------------------------------------------------------------------

_MS = ms.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)


Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/msg_server$(FT_EXE) $(_MS)

Start_Program_00 = local $(_MS) pf=$(DIR_PROFILE)/LO7_ASCS67_ascslo7

#-----------------------------------------------------------------------


#-----------------------------------------------------------------------

_EN = en.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)


Execute_04 = local ln -s -f $(DIR_EXECUTABLE)/enserver$(FT_EXE) $(_EN)

Start_Program_01 = local $(_EN) pf=$(DIR_PROFILE)/LO7_ASCS67_ascslo7

18.1.6 NetWeaver 7.0 / NetWeaver 7.0SR1/SR2

Example:

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

User: p11adm

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



lrwxrwxrwx 1 p11adm sapsys 16 2006-06-19 .dbenv_dbp11-se.csh

-> .dbenv_dbp11.csh

lrwxrwxrwx 1 p11adm sapsys 15 2006-06-19 .dbenv_dbp11-se.sh

-> .dbenv_dbp11.sh

-rw-r----- 1 p11adm sapsys 4785 2006-06-12 .dbenv_dbp11.sh

-rw-r----- 1 p11adm sapsys 4818 2006-06-19 .dbenv_j76p11.csh

-rw-r----- 1 p11adm sapsys 4786 2006-06-19 .dbenv_j76p11.sh

-rw-r----- 1 p11adm sapsys 4818 2006-06-19 .dbenv_jcp11.csh

-rw-r----- 1 p11adm sapsys 4786 2006-06-19 .dbenv_jcp11.sh

-rw-r----- 1 p11adm sapsys 4818 2006-06-19 .dbenv_scsp11.csh

-rw-r----- 1 p11adm sapsys 4786 2006-06-19 .dbenv_scsp11.sh

-rw-r----- 1 p11adm sapsys 757 2006-06-19 .j2eeenv_j76p11.csh

-rw-r----- 1 p11adm sapsys 825 2006-06-19 .j2eeenv_j76p11.sh

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

-rw-r----- 1 p11adm sapsys 825 2006-06-09 .j2eeenv_jcp11.sh

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

-rw-r----- 1 p11adm sapsys 825 2006-06-09 .j2eeenv_scsp11.sh

lrwxrwxrwx 1 p11adm sapsys 20 2006-06-19 .sapenv_dbp11.csh

-> .sapenv_dbp11-se.csh

-rw-r----- 1 p11adm sapsys 8325 2006-06-09 .sapenv_dbp11-se.csh

-rw-r----- 1 p11adm sapsys 7693 2006-06-09 .sapenv_dbp11-se.sh

lrwxrwxrwx 1 p11adm sapsys 19 2006-06-19 .sapenv_dbp11.sh

-> .sapenv_dbp11-se.sh

-rw-r----- 1 p11adm sapsys 8325 2006-06-19 .sapenv_j76p11.csh

-rw-r----- 1 p11adm sapsys 7693 2006-06-19 .sapenv_j76p11.sh

-rw-r----- 1 p11adm sapsys 8325 2006-06-09 .sapenv_jcp11.csh

-rw-r----- 1 p11adm sapsys 7693 2006-06-09 .sapenv_jcp11.sh

-rw-r----- 1 p11adm sapsys 8325 2006-06-09 .sapenv_scsp11.csh

-rw-r----- 1 p11adm sapsys 7693 2006-06-09 .sapenv_scsp11.sh

-rw-r----- 1 pl1adm sapsys 1322 2006-06-19 .sapsrc_j76p11.csh

-rw-r----- 1 pl1adm sapsys 1118 2006-06-19 .sapsrc_j76p11.sh

-rw-r----- 1 pl1adm sapsys 1322 2006-06-09 .sapsrc_jcp11.csh

-rw-r----- 1 pl1adm sapsys 1118 2006-06-09 .sapsrc_jcp11.sh

-rw-r----- 1 p11adm sapsys 1322 2006-06-09 .sapsrc_scsp11.csh

-rw-r----- 1 p11adm sapsys 1118 2006-06-09 .sapsrc_scsp11.sh

18.2 Configuring the Virtual Host Name for Web AS 6.40 ABAP and JAVA-AddIn / WebAS 6.40 JAVA


/home_sap/<sid>adm



After installation, rename the installed .*_<phys host name>.*sh to

*_ci<sid>.*sh (not valid for WebAS 6.40 JAVA only), j2eeenv_xxx.* and

*JC<ID>_jc<sid> (only valid for WebAS 6.40 JAVA) files as well.


1. Change the profile name from *_DVEBMGS<ID>_<phys_hostname> to

*_DVEBMGS<ID>_ci<sid>. (not valid for 6.40 JAVA only).

2. Change the profile name from *_SCS<ID>_< phys_hostname> to

*_SCS<ID>_scs<sid>.



WebAS 6.40 ABAP + JAVA-AddIn

1. Change the host name to ci<sid> in DEFAULT.PFL and in the CI start profile.

Set DBHOSTNAME=db<sid>-se. Set SAPLOCALHOST=ci<sid> in the CI

profile.

2. Change the host name to scs<sid> in the SCS start profile. Set

SAPLOCALHOST=scs<sid> in the SCS profile.

3. Set SAPLOCALHOST=app<id><sid> in every application instance profile.

WebAS 6.40 JAVA:

1. Change the SAPJDBHOST and j2ee/dbhost to db<sid>-se in the

DEFAULT.PFL.

2. Change the host name in the SCS start profile to scs<sid>.

3. Set the SAPLOCALHOST=scs<sid> in the SCS profile.

4. Set the SAPLOCALHOST=jc<sid> in the JC profile.

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

DEFAULT.PFL (WebAS 6.40 ABAP + JAVA-AddIn):

bash-2.03# cat DEFAULT.PFL

SAPGLOBALHOST = cios4

SAPDBHOST = dbos4-se

rdisp/mshost = cios4

SAPSYSTEMNAME = OS4

rdisp/accept_remote_trace_level = 0

rdisp/sna_gateway = cios4

rdisp/sna_gw_service = sapgw67

rslg/collect_daemon/listen_port = 3967

rslg/collect_daemon/talk_port = 4067

rdisp/bufrefmode = sendon,exeauto

ms/server_port_0 = PROT=HTTP, PORT=8167

dbs/ora/tnsname = OS4

DIR_CLIENT_ORAHOME = /oracle/OS4/920_64

DIR_SERVER_ORAHOME = /oracle/OS4/920_64

j2ee/dbname = OS4

j2ee/dbtype = ora

j2ee/dbhost = dbos4-se



DEFAULT.PFL (WebAS 6.40 JAVA):

bash-2.03# cat DEFAULT.PFL

SAPSYSTEMNAME = OLI

SAPJDBHOST = dboli-se

j2ee/dbname = OLI

j2ee/dbtype = ora

j2ee/dbhost = dboli-se

Start profile (e.g. START_SCS68_scsos4):

bash-2.03# cat START_SCS68_scsos4

#-----------------------------------------------------------------

# Global variables

#-----------------------------------------------------------------

SAPSYSTEMNAME = OS4


DIR_EXECUTABLE = /usr/sap/OS4/SYS/exe/run

DIR_LIBRARY = /usr/sap/OS4/SYS/exe/run

#-----------------------------------------------------------------


#-----------------------------------------------------------------

_MS = ms.sapOS4_SCS68


Execute_01 = local ln -s -f $(DIR_EXECUTABLE)/msg_server $(_MS)

Start_Program_00 = local $(_MS) pf=$(DIR_PROFILE)/OS4_SCS68_scsos4

#-----------------------------------------------------------------


#-----------------------------------------------------------------

_EN = en.sapOS4_SCS68


Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/enserver $(_EN)

Start_Program_01 = local $(_EN) pf=$(DIR_PROFILE)/OS4_SCS68_scsos4



Instance Profile (e.g. OS4_SCS68_scsos4):

bash-2.03# cat OS4_SCS68_scsos4

SAPSYSTEMNAME = OS4

SAPLOCALHOST = scsos4

SAPLOCALHOSTFULL = scsos4


SAPSYSTEM = 68

DIR_GLOBAL = /sapmnt/OS4/global

DIR_PROFILE = /sapmnt/OS4/profile

DIR_EXECUTABLE = /usr/sap/OS4/SYS/exe/run

rdisp/msserv = 3668


enque/deque_wait_answer = FALSE

enque/process_location = LOCAL

enque/encni/port = 3268



ms/server_port_0 = PROT=HTTP, PORT=8168

Adapt the J2EE Configuration Tool

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

jc<sid> for WebAS 6.40 JAVA.

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

cn1:~ # ssh -X os4adm@Baby_1

os4adm@Baby_1's password:

Baby_1:os4adm 38> cd /usr/sap/OS4/DVEBMGS67/j2ee/configtool/

[Baby_1:oliadm 38> cd /usr/sap/OLI/JC16/j2ee/configtool/] for WebAS 6.40 JAVA

Baby_1:os4adm 39> ./configtool.sh

Connect to DB? Yes









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

to change: profile

name + host





Check the host name of the SCS for all installed instances

Recommendation:

If you plan to install several DI Instances, finish the virtualization step of the ABAP +

JAVA-AddIn Instances. During the installation step you‘ll be asked for names of the DB

and CI, type in the virtual hostnames.

to change: profile

name + host









Adapt the J2EE Offline Configuration Tool:

cn1:~ # ssh -X os4adm@Baby_1

os4adm@Baby_1's password:

Baby_1:os4adm 38> cd /usr/sap/OS4/DVEBMGS67/j2ee/configtool/

Baby_1:os4adm 39> ./offlinecfgeditor.sh



Click on the edit icon. A Switch to Edit mode warning opens.

Click on Yes and afterwards double-click the Propertysheet instance.

doubleclick



Click on OK and exit.



Change the following files:

Baby_1:os4adm 59> cd /usr/sap/OS4/DVEBMGS67/SDM/program

Baby_1:os4adm 63> vi localsdmgui.properties

workingHost=cios4

workingDirectory=/usr/sap/OS4/DVEBMGS67/SDM/program

workingPort=50118

workingFrogTheme=Bright Harmonic

workingLookAndFeel=com.sap.plaf.frog.FrogLookAndFeel

~

~

Baby_1:os4adm 64> cd config

Baby_1:os4adm 66> vi sdmrepository.sdc

</AdminPort>

<Host>

scsos4

</Host>

<RootDir>

/usr/sap/OS4/DVEBMGS67/SDM/root

</RootDir>

<MaxBackups>

10

</MaxBackups>

<CurrentBackup>

6

</CurrentBackup>

<CurrentFlowBackup>

8

</CurrentFlowBackup>

<HashedPassword>

yPLDEBe3oOb6H2mmjJ0zztOgw/A=

</HashedPassword>

<JStartup-Configuration active="true">

<mshost>

scsos4

</mshost>

<msport>

3600

:wq

Change hosts and directory.



18.3 Start Script startdb for Oracle and SAPDB/MaxDB/DB2

The database (Oracle, SAPDB/MaxDB/DB2) is not started implicitly with the startsap

(and startdb) standard script in the exe/run directory, but separately using the service

script from SAP. In sapdb, the standard script startdb/startj2eedb is called.

Thanks to the automount mechanism, the exe/run directory is also available on the

database node.

18.4 Stop Script stopdb for Oracle and SAPDB/MaxDB/DB2

The remarks on the start script startdb made in the previous section apply to the

stopdb stop script analogously.

18.5 Scheduling of Batch Jobs (CCMS)

If no application server is present, the following applies:

If you do not have the remote shell remsh on your systems, you have to set the profile

parameter gw/remsh (or dta/remsh/cmd) in the instance profile of the application

server, on which the job is running, to the name of your remote shell program, for

example, ssh.

On a UNIX system, use the command which ssh to find out where the ssh command is

located. You can check this as a standard user by calling the following command:

$ which <program_name>

The SAP control program sapxpg has to be found in the search path of the standard

SAP user on the remote host. SAPXPG is stored in the SAP executables directory. If the

external program was not specified with an absolute path name, then the external

program also has to be found in the search path of the standard SAP user. In UNIX you

can check this in the standard user by calling the following command:

which <program_name> while logged on as the standard user.

Both the SAP control program sapxpg and the external program to be started has to be

executable under the standard SAP user. For example, on a UNIX machine this means

that <sid>adm must have execute permission (‗x‘) for the programs.

Change the parameter gw/remsh in every instance profile to /usr/bin/ssh. To check

where the program ssh is located, issue the which command.



SSH Configuration:

The host the job is running on must have permission to start programs on the remote

host.

Baby_1:oacadm 60% ssh-keygen -t rsa

Generating public/private rsa key pair.

Enter file in which to save the key (/home_sap/oacadm/.ssh/id_rsa):

Created directory ‗/home_sap/oacadm/.ssh

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in /home_sap/oacadm/.ssh/id_rsa.pub.

Your public key has been saved in /home_sap/oacadm/.ssh/id_rsa.pub.

The key fingerprint is:

ea:46:0a:17:e5:e9:39:54:c9:e8:10:b0:d6:84:c3:ce oacadm@Baby_1

Baby_1:oacadm 61% cd .ssh

Baby_1:oacadm 62% ls

id_rsa.pub id_rsa

Baby_1:oacadm 63% cp –p id_rsa.pub authorized_keys

Baby_1:oacadm 64% chmod 700 /home_sap/oacadm

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

18.6 Profile Parameters for DEFAULT.PFL

Example:

SID = O12

system number = 12

SAPSYSTEMNAME = O12

SAPDBHOST = dbo12-se

rdisp/mshost = cio12

rdisp/sna_gateway = cio12

rdisp/sna_gw_service = sapgw12

rdisp/vbname = cio12_O12_12

dbs/ora/tnsname = O12

rdisp/enqname = cio12_O12_12

rdisp/btcname = cio12_O12_12

rslg/collect_daemon/listen_port = 3912

rslg/collect_daemon/talk_port = 4012

rdisp/bufrefmode = sendon,exeauto



18.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. Start profiles only available until

SAP 7.0 (NetWeaver 2004s).

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:

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_cio12

O12_DVEBMGS12_cio12

18.8 Profile Parameters for the Instance Profile

The SAP instance runs with a virtual host name instead of the physical host name. The

SAPLOCALHOST parameter has to be set accordingly.

Syntax for the host name (ABAP)

Central instance: ci<sid>

ABAP central services instance: ascs<sid>

Application instance: app<id><sid>

Syntax for the host name (JAVA)

Java Control instance: jc<sid>

SAP common services: scs<sid>

Java application instance: j<id><sid>



Example:

Central Instance with SID = CB1

SAPLOCALHOST = cicb1

Example:

Application Instance with

instance number = 01

SID = CB1

SAPLOCALHOST = app01cb1

Enable Memory Auto Management

Please check the parameters according to SAP Note 386605:

es/implementation = map

PHYS_MEMSIZE = 50%

The following profile parameters have to be disabled after this:

em/max_size_MB = 1024

em/initial_size_MB = 1024

em/address_space_MB = 1024

em/blocksize_KB = 1024

em/stat_log_size_MB = 20

em/stat_log_timeout = 600

rdisp/ROLL_SHM = 128

rdisp/ROLL_MAXFS = 32768

rdisp/PG_SHM = 0

rdisp/PG_MAXFS = 2048

ztta/roll_first = 1024

ztta/roll_area = 9216000

18.9 SAP Start and Stop Mechanism (Release 4.6CSR2)

The SAP start and stop mechanism has changed in Kernel release 6.x. The scripts startsap and stopsap are now located in the /usr/sap/<sid>/SYS/exe/run

directory. For this reason, the aliases startsap and stopsap, as well as the startsap

<hostname>_<sysnr> and stopsap_<hostname>_<sysnr> start and stop scripts in

/home/<sid>adm exist no longer.



If you wish to use an older kernel release lower than WAS 6.10, it has to be

converted to the new start and stop mechanism first.

Procedure

Install and configure the virtual host name as described above, separately for the

database and the SAP instance. Remove the startsap_<hostname>_<inr> and

stopsap_<hostname>_<inr> scripts from $HOME of <sid>adm. They are both

replaced by a single new script.

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

scripts:

set hostname=`hostname`

# 12.08.02

#unset list

#set list=`$lscommand $HOME | grep '^startsap_'${hostname}'_[0-9]

[0-9]$'`

#if ( ècho $list | wc -w` == 1 ) then

# alias startsap $HOME/$list

#else

# alias startsap "echo 'To start an instance use one of the following scripts:

#endif

#

#unset list

#set list=`$lscommand $HOME | grep '^stopsap_'${hostname}'_[0-9][0-9]$'`

#if ( ècho $list | wc -w` == 1 ) then

# alias stopsap $HOME/$list

#else

# alias stopsap "echo 'To stop an instance use one of the following scripts:';

#endif

#

# end SAP R/3 Environment

Place the startsap and stopsap scripts of release 6.x in the /sapmnt/<sid>/exe

directory.

Make sure that all the permissions of the SAP kernel in this directory are set to

<sid>adm:sapsys. After changing the rights with chown

<sid>adm:sapsys_*, start the saproot.sh <sid> script.

The new scripts should look like this:

#!/bin/sh

#-----------------------------------------------------------------

#



# NAME :

# startsap

#

# PURPOSE :

# Start SAP Database and SAP Instances

#

# USAGE: startsap [db|r3|all|check] [<instance>]

#

# Specify instance if you have installed multiple

# instances of the same system on one host.

# Example: startsap r3 DVEBGMS00

#

# other optional parameters:

# check Check Database and SAP Instance

# r3 | R3 Start SAP Instance only

# db | DB | dB | Db Start Database only

# ALL | all Start Database and SAP Instance

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

18.11 SAPLogon – SAPGUI

Usage

An SAP application instance is accessed via the Client LAN and not via the Server LAN.

This means that SAPGUI or SAP Logon have to communicate with the virtual Client LAN

address of the application instance. If a specific application instance is entered in SAP

Logon with its virtual Client LAN address, access will function as before.

If a logon group is entered in SAP Logon, the Client LAN address has to be specified for

the application instance in the transaction SMLG so that the message server can report it

to SAP Logon. By default, the message server reports the Server LAN address to SAP

Logon on the basis of the naming convention for the instance name

<hostname>_<sid>_<inr>. Instead, static routes may also be entered on the

Application Nodes; however, this would make it necessary to enable IP forwarding.





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

Logon group ―PUBLIC‖.



Enter the virtual IP address of the Client LAN.

18.12 SAPROUTER on the Control Node

18.12.1 Configuration File for /etc/init.d/saprouter

The start configuration is done in /etc/init.d/saprouter. If necessary you can

specify additional parameters through SAPROUTER_EXTRA_PARAMS in

/FlexFrame/volFF/FlexFrame/saprouter/saprouter.config. But you have to

take care that the changes does not affect other parts of the FF system you do not want.

You can specify a specific port on your own requests for sparouter:

SAPROUTER_EXTRA_PARAMS="-S <portnumber>"

You can also specify a specific IP address for the hostroute to make sure that after a

reboot or other configuration changes SAPROUTER uses a valid address:

SAPROUTER_EXTRA_PARAMS=‖-I <ip>



Please note that many installations need certain features of the saprouter, some of this

features, like SNC, may require special environment variables set.

Those can be exported from the saprouter.config file as well.

Here is an example for this file using the SNC feature of saprouter:

SAPROUTER_EXTRA_PARAMS="-K '<snc-name string>'"

export SNC_LIB="/saprouter/linux-glibc2.2/libsapcrypto.so"

Specifying environment variables in the .bashrc or other profile configuration files will not

be seen by the cluster and its resources because it is usually startet during system boot

without any user environment.

18.12.2 Configuration File saprouter

The saprouter (/FlexFrame/volFF/FlexFrame/saprouter) routes the nodes

from the workstation network 100.10.100.* to the Client LAN of the virtual SAP

services:

/FlexFrame/volFF/FlexFrame/saprouter/saprouttab

#

# from to service

#

# workstation-lan client-lan

P 100.10.100.* 10.0.190.* *

If the virtual host names are entered in saplogon instead of the IP addresses, the

names have to be resolved on the saprouter:

Hosts in LDAP

10.0.190.111 cibw1

10.0.190.101 cicb1

10.0.190.102 app01cb1

10.0.190.103 app02cb1

Services in LDAP

sapdp01 3201/tcp # SAP System Dispatcher Port


sapmsCB1 3600/tcp # SAP System Message Port


Image independent JAVA JDK


19 Image independent JAVA JDK

With SAP 7.1 up SAP installation have a built-in Java Virtual Machine. So you

are not requested to install a specific JDK.

You should pay attention if you want to use your specific JDK, that the

configuration is a matter of your own. FlexFrame is not responsible for

misconfigurations done by the user.

Some installations of SAP services require a specific JAVA JDKs at runtime. That

request may conflict with the JDK version supplied with FlexFrame image. To become

independent from image you can install pool or SID specific JAVA JDKs. This chapter

will show you ‗how to do‘.

To decide if your SAP installation fits to the supplied JDK you should check the used

version of JDK by executing

applnode: su - <sid>adm –c ‗java –fullversion‘

java full version ―J2RE …‖

applnode: su - <sid>adm –c ‗which java‘

/opt/IBMJava2-amd64-142/bin/java

If it fits, you need not to install a specific JDK. Otherwise you can switch to a central path

of JDKs.

19.1 File structures and profiles

You have to create a pool specific directory for JDK installations if it is not part of your

installation

cn1: # logon as user root

cn1: cd /FlexFrame/volFF/pool-<pool>/sap/usr_sap

cn1: mkdir –p java/<jdk_dirname>

cn1: chmod 755 java/<jdk_dirname>

Now you install the JDK in the created directory.

Set a link at application node to your own JDK directory:



applnode: su - <sid>adm

applnode: cd /usr/sap/<SID>

applnode: ln –s /usr/sap/java/<jdk_dirname> ffjava

Now you have to set your own JAVA home in the instance profiles. This task is described

in SAP Note 718901 (Option 1).


applnode: cd /sapmnt/<SID>/profile

applnode: # edit profiles as described in SAP Note 718901, using ‗vi‘

applnode: grep ―/usr/java‖ * # check for further profiles containing java path

applnode: # edit further profiles if necessary using ‗vi‘

Now you have to modify user profiles setting JAVA_HOME. Possible users are <sid>adm

(and maybe db2<sid>)


applnode: cp –p j2eeenv.csh j2eeenv.csh.new

applnode: # cp –p j2eeenv.sh j2eeenv.sh.new

applnode: vi j2eeenv.csh.new

setenv JAVA_HOME /usr/sap/<SID>/ffjava

applnode: vi j2eeenv.sh.new

JAVA_HOME=/usr/sap/<SID>/ffjava; export JAVA_HOME

We recommend to create new files because of currently running system using those files.

To activate the new files you normally have to stop the instance, rename current files to

‗*.old‘ and the new files to the current file names. After that you can restart the instance.

19.2 Java Configuration Tool

There is an optional step to update also Java Configuration tool with the new Java path

(normally this path is overwritten by the specification done in instance profiles shown

before) . It is recommended to do the changes to ensure consistence.

Please follow the instructions made in SAP Note 718901 (Option 2). Before you start

modifying it is recommended to stop the Java instance (JC) using ff_service.sh.

19.3 Java path settings for SDM

If it needed to modify the JAVA path for SDM pelease follow the instructions made in SAP

Note 743583.






Additionally you have to modify JAVA property files. Please refer also to SAP Note

718901.

19.4 Restart the services with new JAVA path

You have to rename some files. If the JAVA stack starts again the files are created once

more.


applnode: cd /usr/sap/<SID>/<INSTANCE>/j2ee/cluster

applnode: mv instance.properties.vmprop instance.properties.vmprop.old

applnode: cd /usr/sap/<SID>/<INSTANCE>/SDN/program/config

applnode: mv sdm_jstartup.properties.vmprop sdm_jstartup.properties.vmprop.old

applnode: cd /home_sap/<sid>adm

applnode: mv j2eeenv.csh j2eeenv.csh.old

applnode: mv j2eeenv.sh j2eeenv.sh.old

applnode: mv j2eeenv.csh.new j2eeenv.csh

applnode: mv j2eeenv.sh.new j2eeenv.sh

Now you can restart your services with the new JAVA specifications. For the first trial we

recommend to set the services to ‗NOWATCH‘ by ff_service.sh to prevent unexpected

behaviour if there is a misconfiguration. If the services work well you reset the services to

‗WATCH‘ by ff_service.sh


Usage of SAP JVM


20 Usage of SAP JVM

Corresponding to SAP note 1495160 SAP Systems based on NetWeaver 04 and SAP

NetWeaver 7.0 running with vendor JDK (SUN/IBM) have to use SAP JVM 4.x because

the support of partner JDKs (1.4.2) ends in September 2012. Please refer to note

mentioned above and its related notes to change to SAP JVM.

SAP provides a tool to switch to SAP‘s JVM and from our point of view you should take

into account some hints for the migration. Before starting the migration please

set a host alias if you are using profile parameter ‗SAPFQDN‘ (DEFAULT.PFL)

by ‗ff_hosts.sh –p <pool> -a <applNodeIp> -n

<applNodeName>.<SAPFQDN>‘ on the control node

start the instances (including database) of your SAP System

start the migration

If you get a complaint that the installer cannot start your instances (last action of

installation procedure) you can ignore it and leave the installer. Restart the instances

manually. Do not forget to remove the alias by ‗ff_hosts.sh –p <pool> -r

<applNodeIp>‘ and stop your services.


SAP System Administration


21 SAP System Administration

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

21.2 Software Administration

21.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 a SAP Service script.

With FlexFrame 5.0 there is an incompatibility concerning starting and stopping

SAP services. The standard sapxx scripts are deprecated and all requests are

now handled by ‗ff_service.sh‘ script.

Only project specific solutions like sapxprint will be supported furthermore.

The SAP Services must not be started directly, e.g. for SAP R/3 as <sid>adm

with startsap, since in this case the interfaces are neither supplied with IP

addresses, nor is the service control file updated. The started application will not

work due to the lack of a network connection.

21.2.1.1 SAP Service Scripts

A detailed description of the usage of sapservice scripts can be found in manual

‗Administration and Operation Guide‘, chapter ‗Starting and Stopping Application

Services‘. The corresponding return codes are also described in that document.



Joined SAP Service Scripts

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

services:

Script name Application Place of execution

start_all_sapservices Initial start of all

configured applications

Only on a Control

Node

stop_all_sapservices Stopping of all active

applications

Only on a Control

Node

stop_all_sapservices_SID Stopping of all active

applications of one SID

Only on a Control

Node

stop_all_sapservices_local 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 stop_all_sapservices_local

can be appended in the relevant run levels:

# Stop all sapservices

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

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

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

21.3 SAP Release Upgrade

21.3.1 Services Port

If you plan an SAP Release upgrade, you have to add a special service port (called

shadow instance) to LDAP.

Please use the ff_sap_shadowport.sh script. If you issue the script the usage will be

shown.



21.3.2 Instance profile

Upgrading from older SAP releases to SAP PI 7.11 may cause problems to start a SAP

service.

After the upgrade procedure the instance profile looks like:

The problem is the reference to DIR_SEP in the entry DIR_EXECUTABLE. It has to be

removed.



21.4 Transport Directory

More than one transport directory per pool:

Create the following directories manually under /usr/sap/<SID>/trans:

applnode # cd /usr/sap/<SID>/trans

applnode # mkdir EPS EPS/in EPS/log EPS/out bin buffer cofiles data etc \ log

sapnames tmp

applnode # chown –R <sid>adm:sapsys *

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

Change DIR_TRANS to /usr/sap/<SID>/trans

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

Transport Management System:

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

21.5 Printing in FlexFrame

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

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.

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

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

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

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

http://help.sap.com/saphelp_erp2004/helpdata/en/b6/c0193c45f9fa13e10000000a114084/content.htm

http://help.sap.com/saphelp_erp2004/helpdata/en/b6/c0193c45f9fa13e10000000a114084/content.htm

http://help.sap.com/saphelp_erp2004/helpdata/en/4f/9c033cff903105e10000000a114084/content.htm



Access Method U:

UNIX systems; Microsoft Windows systems (using a TCP/IP Print Server an SAPlpd)

Access Method S:

Microsoft Windows systems (using SAPlpd)

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

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



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


22 BRBACKUP and SAPDBA/BRCONNECT

When brbackup is started for offline backup, it first stops the database with the

shutdown immediate command. As the FA Agent recognizes that the Oracle

processes are missing, it will, by default, restart the database. The brconnect will notice

that the database has been restarted, and the backup is aborted.

In order to avoid this situation, there are two solutions to make backup tools ―FlexFrame-

aware‖.

22.1 Solution 1 for Oracle and SAPDB/MaxDB

This solution uses the options nowatch and watch of the script sapdb to tell the FA

Agent that the database should not be monitored during the offline backup.

Requirements

Current SAP Service scripts in /FlexFrame/scripts

Implementation

Before starting the offline backup, the script sapdb should be called as user root with

arguments:

sudo /FlexFrame/scripts/ff_service.sh –t db –s <SID> -a

nowatch

When the backup is finished, the script sapdb should be called as user root with

arguments:

sudo /FlexFrame/scripts/ ff_service.sh –t db –s <SID> -a

nowatch

Calling script ff_service.sh is also possible as <sid>adm or for Oracle as ora<sid>

user, but then it has to be called with absolute path name.

BRBACKUP and SAPDBA/BRCONNECT


22.2 Solution 2 for Oracle

This solution uses the options nowatch and watch of the script ff_service.sh 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 ff_service.sh is called indirectly from

brbackup by using the functionality meant for Oracle Fail Safe.

Requirements

br-tools must be at least version 620 patch level 124

Current SAP Service scripts in /FlexFrame/scripts

group dba in LDAP must have ora<sid> as member of the group

Implementation

The following environment variables must set for <sid>adm and ora<sid> users:

BR_OFS=1

FSCMD_CMD=/FlexFrame/scripts/sapbrbackup

When the brbackup is started directly, called from SAPDBA or a DB13 transaction, it

calls the script sapbrbackup to shut down and start up the database, and the

sapbrbackup will take care of calling ff_service.sh with the nowatch or watch

option.

Known limitations

works only with Oracle databases

brbackup needs to be version 620 even if using 4.6X kernel

Troubleshooting


23 Troubleshooting

Environment of <sid>adm and ora<sid> users:

In order to obtain corresponding environment variables for the instances in question,

the following files must be present in the home directory of each user:

.cshrc

.sapenv_ci<sid>.csh

.sapenv_ci<sid>.sh

.dbenv_ci<sid>.csh

.dbenv_ci<sid>.sh

.sapenv_db<sid>-se.csh

.sapenv_db<sid>-se.sh

.dbenv_db<sid>-se.csh

.dbenv_db<sid>-se.sh

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

Central-Instance CB1 is not running, please start it first.

…..

exit_code 2 (plausibility error)

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

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

● When an external switchover is necessary sometimes the restart of CI instance have

timing problems if DB2 V9.5 is used. This may cause a second trial to start the CI

instance by FA agents. That restart operation normally succeed and you do not need

to do further actions.

Installation of SAP system on SuSE SLES10 or upgrade from older SuSE SLESnn

Using SAP software with LDAP environment requires some additional links. So you

need to create some symbolic links for that environment (see also SAP Note

958253)

CN: cd /FlexFrame/volFF/os/Linux/<image>/root_img/usr/lib64

CN: ln –l liblber-2.2.so.7 liblber.so.199 CN: ln –l libldap-2.2.so.7 libldap.so.199

● Installer ‗sapinst‘ proposes a 7th database directory ‗sapdata7‘. Please remove it

from the proposal list because FlexFrame does not support more than six SAP

specific database directories.

Central-Instance CB1 is not running, please start it first.

Troubleshooting


● Account sdb is not locked (MaxDB)

During the preparation phase of the Database Kernel package you can get the

following messages:WRN: changing sdb administrators group …

Account sdb is not locked, this is a security leak

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 getent passwd |

grep sdb and getent group | grep 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 *lk*. Either you are using ldapbrowser

tool or if not available you can use LDIFs directly to modify LDAP database entry.

You are strongly recommended to do a backup of your LDAP database before

running script to modify LDAP.

Create a file /tmp/ldif.sh and insert

ldapmodify –v –x \

-D ―cn=root,ou=LDAPadmins,ou=FlexFrame,…,dc=com \

-w <ldap_password> <<EOF

dn: cn=sdb,ou=People,ou=<poolname>,ou=FlexFrame, … ,dc=com

changetype: modify

replace: userPassword

userPassword: *LK*

EOF

Run /tmp/ldif.sh as user root.

● When an external switchover is necessary sometimes the restart of CI instance have

timing problems if DB2 V9.5 is used. This may cause a second trial to start the CI

instance by FA agents. That restart operation normally succeed and you do not need

to do further actions.

Troubleshooting


● Switch to root from <sid>adm user

Security enhancements does not allow to switch from an user which is not member

of the operating system group ‗wheel‘ to superuser ‗root‘.

Sometimes descriptions from SAP request a switch to ‗root‘ from, e.g. <sid>adm, to

to preserve the environment of the user to execute SAP scripts, e.g. ‗saproot.sh‘.

To prevent opening of the root image to insert the specific user into the group ‗wheel‘

(by modifying /etc/group), you create a group ‗wheel‘ within LDAP for the time of the

specific operation and remove it again after you are finished. You should take into

account that you make weak your system security.

cn: ff_group_adm.pl –-op add –pool <pool> --name wheel \

--member <user>

an: … perform your operation …

cn: ff_group_adm.pl –-op rem –pool <pool> --name wheel

If the group ‗wheel‘ already exists in LDAP and is used for further users you have to

cn: ff_group_adm.pl –-op mod –pool <pool> --name wheel \

--member <user>

an: … perform your operation …

cn: ff_group_adm.pl –op rem –pool <pool> --name wheel –member <user>

A further possible way to resolve the security restrictions would be to use a further

shell under control of user ‗root‘, set the requested environment and run the scripts.

Example:

root@an: export DB2DBDFT=<sid>

root@an: export SID=<SID>

root@an: saproot.sh

● SAP system cannot be startet.

Remove the DIR_SEP variable in the Instance profile.

● This variable prevents the start of the SAP system. It is included automatically into

the profile when executing an upgrade to 7.11.

Troubleshooting


● ‗dbmcli is missing‘

If there are problems using /etc/opt/sdb may be you can see this message:

ERROR ..

.... FCO-00011..../sapdb/programs exists, but

/sapdb/programs/bin/dbmcli is missing .....

..... software is inconsistent. ........

Please refer to the corresponding chapters describing handling of /etc/opt/sdb.

● ‗Warning: Could not found virtuell host in ifconfig list.‘ from startsap

Some configurations show the warning message above while starting a SAP service.

The message depends on the software stack used and can be ignored.

● Very high consumption of CPU power by MaxDB server processes

If you watch a comsumption of CPU power near to 100 % by MaxDB server

processes you should check if the workaround mentioned with SAP Note 1041650

may help you to get rid of it. The only requirement is that a local file system has to

be used. We recommend to /dev/shmfs.

● ‗Error: nnn: We have neither a ABAP CI nor a Java JC instance profile found‘

Sometimes there are special configurations which does not have a CI or JC

instance. This will cause an error if there is a trial to start database instance. In those

case you have a little workaround

touch /sapmnt/<SID>/profile/<SID>_DVEBMGS<instance_nr>_ci<sid>

chown <sid>adm:sapinst

/sapmnt/<SID>/profile/<SID>_DVEBMGS<instance_nr>_ci<sid>

chmod 644 /sapmnt/<SID>/profile/<SID>_DVEBMGS<instance_nr>_ci<sid>

● ‗UNIX password mismatch

Because of FlexFrame security enhancements sometimes it is possible that the

command 'dbmverifypw' from MaxDB installation does not work well. To overcome

this issue you have to modify FlexFrame's security options. But you have to take

into account that you weaken FlexFrame security features. You have to


Troubleshooting


exchange the string 'by peername.ip …. auth' to 'by peername.ip …. read'

in/FlexFrame/volFF/FlexFrame/ldap/common/slapd_acl.conf for the concerned

hosts

restart ldap_master using 'ff_ha_cmd.sh restart ldap_master' (Controlnode)

restart nscd using 'rcnscd restart' (Application Node)


24 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

FSC FlexFrame Software Container, name part used for

Images and CDs/DVDs

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

Abbreviations


NIC Network Interface Card

NVRAM Non-Volatile Random Access Memory

OBP Open Boot Prom

OLTP On-Line Transaction Processing

ONTAP Open Network Technology for Appliance Products

OSS Open Source Software

POST Power-On Self Test

PFS Production File System (on Celerra)

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

TELNET Telecommunications Network

Abbreviations


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


25 Glossary

Adaptive Computing Controller

SAP system for monitoring and controlling SAP environments.

Advanced Business Application Programming

Proprietary programming language of SAP.

Advanced Power Management

Advanced Power Management defines a layer between the hardware and the

operating system that effectively shields the programmer from hardware details.

Application Agent

A software program for monitoring and managing applications.

Application Node

A host for applications (e.g. SAP instances db, ci, agate, wgate, app etc.). This

definition includes Application Servers as well as Database Servers.

Automounter

The automounter is an NFS utility that automatically mounts directories on an NFS

client as they are needed, and unmounts them when they are no longer needed.

Autonomous Agent

Central system management and high availability software component of FlexFrame.

Blade

A special form factor for computer nodes.

BladeRunner

The working title for the solution part of SAP for FlexFrame.

BOOTPARAM

Boot time parameters of the kernel.

BRBACKUP

SAP backup and restore tools.

Celerra

NAS system of EMC.

Checkpoint Restore

On EMC Celerra a SnapSure feature that restores a PFS to a point in time using

checkpoint information. As a precaution, SnapSure automatically creates a new

checkpoint of the PFS before it performs the restore operation.

Client LAN

Virtual network segment within FlexFrame, used for client-server traffic.

Glossary


Common Internet File System

A protocol for the sharing of file systems (same as SMB).

Computing Node

From the SAP ACI perspective: A host that is used for applications.

Control Agent

A software program for monitoring and managing nodes within FlexFrame.

Control LAN

Virtual network segment within FlexFrame, used for system management traffic.

Control Node

A physical computer system, controlling and monitoring the entire FlexFrame

landscape and running shared services in the rack (dhcp, tftp, ldap etc.).

Control Station

A Control Node in an SAP ACI environment.

DART

Operating system of Celerra data movers (Data Access in Real Time).

Dynamic Host Configuration Protocol

DHCP is a protocol for assigning dynamic IP addresses to devices on a network.

Dynamic Host Configuration Protocol server

A DHCP server provides configuration parameters specific to the DHCP client host,

required by the host to participate on the Internet.

EMC NAS

Network attached storage for file systems of EMC.

Enterprise Resource Planning

Enterprise Resource Planning systems are management information systems that

integrate and automate many of the business practices associated with the

operations or production aspects of a company.

Ethernet

A Local Area Network which supports data transfer rates of 10 megabits per second.

Fiber Channel

Fiber Channel is a serial computer bus intended for connecting high-speed storage

devices to computers.

Filer

Network attached storage for file systems of NetApp.

FlexFrame

A joint project in which the main partners are SAP, Network Appliance, Intel and

Fujitsu.

Glossary


FlexFrameTM

for SAP®

FlexFrame TM

for SAP® is a radically new architecture for SAP environments. It

exploits the latest business-critical computing technology to deliver major cost

savings for SAP customers.

FlexFrame internal LAN Switch

Cisco network switches which are integral part of the FlexFrame for SAP hardware

configuration and which are automatically configured by the FlexFrame for SAP

software.

Gigabit Ethernet

A Local Area Network which supports data transfer rates of 1 gigabit (1,000

megabits) per second.

Host name

The name of a node (assigned to an interface) that is resolved to a unique IP

address. One node can have multiple host names (cf. node name).

In SAP environments host names are currently limited to 13 alphanumeric characters

including the hyphen (― - ―). The first character must be a letter. In the SAP

environment host names are case-sensitive.

Image

In the FlexFrame documentation, ―Image‖ is used as a synonym for ―Hard Disk

Image‖.

Internet Protocol Address

A unique number used by computers to refer to each other when sending information

through networks using the Internet Protocol.

Lightweight Directory Access Protocol

Protocol for accessing on-line directory services.

Local Area Network

A computer network that spans a relatively small area. Most LANs are confined to a

single building or group of buildings. However, one LAN can be connected to other

LANs over any distance via telephone lines and radio waves. A system of LANs

connected in this way is called a Wide Area Network (WAN).

Local host name

The name of the node (physical computer); it can be displayed and set using the

command /bin/hostname.

Logical Unit Number

An address for a single (SCSI) disk drive.

MAC address

Device identifier number of a Network Interface Card. In full: "media access control

address".

Glossary


MaxDB

A relational database system from mySQL (formerly ADABAS and SAPDB).

Media Access Control address

An identifier for network devices, usually unique. The MAC address is stored

physically on the device.

NAS system

Network Attached Storage of any vendor (in our context: EMC NAS or NetApp Filer).

NDMPcopy

NDMPcopy transfers data between Filers using the Network Data Management

Protocol (NDMP).

Netboot

A boot procedure for computers where the operating system is provided via a

network instead of local disks.

Netweaver

SAP NetWeaver is the technical foundation of SAP solutions.

Network Appliance Filer

See ―Filer‖.

Network Attached Storage

A data storage device that is connected via a network to one or multiple computers.

Network File System

A network protocol for network-based storage access.

Network Interface Card

A hardware device that allows computer communication via networks.

Node

A physical computer system controlled by an OS.

Node name

The name of a physical node as returned by the command uname -n. Each node

name within a FlexFrame environment must be unique.

Non-Volatile Random Access Memory

A type of memory that retains its contents when the power is turned off.

On-Line Transaction Processing

Transaction processing via computer networks.

OpenLDAP

An Open Source LDAP Service Implementation.

Open Network Technology for Appliance Products

The operating system of Network Appliance Filers.

Glossary


Open Source Software

Software that is distributed free of charge under an open source license, such as the

GNU Public License.

Oracle RAC

A cluster database by Oracle Corporation.

Physical host

Name of a physical computer system (node).

Power-On Self Test

Part of a computer's boot process; automatic testing of diverse hardware

components.

Preboot Execution Environment

An environment that allows a computer to boot from a network resource without

having a local operating system installed.

PRIMERGY

Fujitsu'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.

Server

A physical host (hardware), same as node.

Service

A software program providing functions to clients.

Glossary


Service type

The type of an application or service (db, ci, app, agate, wgate etc.).

Single Point of Control

In FlexFrame: One user interface to control a whole FlexFrame environment.

Storage LAN

A virtual LAN segment within a FlexFrame environment, carrying the traffic to NAS

systems.

SUSE Linux Enterprise Server

A Linux distribution by Novell, specializing in server installations.

Telecommunications Network

A terminal emulation program for TCP/IP networks such as the Internet.

Trivial File Transfer Protocol

A simple form of the File Transfer Protocol (FTP). TFTP uses the User Datagram

Protocol (UDP) and provides no security features. It is often used by servers to boot

diskless workstations, X-terminals, and routers.

TFTP server

A simple FTP implementation.

Virtual host

The name of the virtual host on which an application runs; it is assigned to a physical

node when an application is started.

Virtual Local Area Network

A VLAN is a logically segmented network mapped over physical hardware according

to the IEEE 802.1q standard.

Virtualization

Virtualization means the separation of hardware and processes. In a virtualized

environment (FlexFrame), a process can be moved between hardware nodes while

staying transparent to the user and application.


26 Index

A

Application Nodes released 9

ASCS ABAP central service

instance 33

B

BRBACKUP 205

C

configuration

interfaces 21

virtual host name for Web AS 6.40

ABAP and JAVA-AddIn / WebAS

6.40 JAVA 165

virtual host name manually 157

configuring the virtual host name for

Web AS 6.40 ABAP and JAVA-AddIn

/ WebAS 6.40 JAVA 165

D

description of Web AS 6.40 JAVA 52

document history 2

F

FA agents 15

ff_scripts 130, 140

G

gathering SAP services information 8

H

host names 22

hot links for FlexFrame 4

I

installation

NetWeaver 7.0SR1/SR2 69

Oracle 10.2 132

Oracle 9.2 130

SAP 4.6C SR2 38, 41, 195

SAP solutions 71

SAPDB / MaxDB 136

Web AS 6.40 with NetWeaver04

SR1 49

with database DB2 27, 30, 147, 192,

193, 194

M

MaxDB 42, 139, 205

N

notational conventions 2

O

online software service 11

operating system

in general 25

Linux 25

ora<sid> 130, 140

Oracle 42, 205, 206

ORACLE 130, 140

OSS network connection

with dedicated saprouter server 11

without dedicated saprouter

server 12

P

Post-SAP installation steps 157

Index


preparations 8

printing in FlexFrame 200

profile parameters for 184

profile parameters for the instance

profile 185

profile parameters for the start

profile 185

R

related documents 4

related SAP notes 13

S

SAP installation steps

overview 2

SAP Java cryptographic toolkit 34

SAP license 188

SAP release upgrade 198

SAP service connection 11

SAP service scripts 17

SAP start and stop mechanism

(Release 4.6CSR2) 186

SAP system administration 197

SAPDB 42, 205

SAPDBA 205

SAPLogon – SAPGUI 188

SAPROUTER on the Control

Node 190, 191

software administration 197

start script 183

starting a configuration 17

stop script 183

T

TNS listener for Oracle 133

transport directory 200

troubleshooting 207

U

upgrading application software 197

V

virtualization of SAP services 8

W

Web AS 6.40 ABAP + JAVA-AddIn

NetWeaver04SR1 62

Web AS 6.40 application server JAVA-

AddIn 67

Web AS 6.40 NetWeaver04SR1 JAVA

MaxDB/Oracle 53