FlexFrame for SAP. Version 5.0A. Installation Guide for SAP Solutions. Edition March 2012 Document Version 1.10

Transcription

1 FlexFrame for SAP Version 5.0A Installation Guide for SAP Solutions Edition March 2012 Document Version 1.10

2 Fujitsu Limited Copyright Fujitsu Technology Solutions 2010 FlexFrame and PRIMERGY are trademarks of FujitsuSAP and NetWeaver are trademarks or registered trademarks of SAP AG in Germany and in several other countries Linux is a registered trademark of Linus Torvalds SUSE Linux is a registered trademark of Novell, Inc., in the United States and other countries Java is a trademark of Sun Microsystems, Inc. in the United States and other countries Intel and PXE are registered trademarks of Intel Corporation in the United States and other countries MaxDB is a registered trademark of MySQL AB, Sweden MySQL is a registered trademark of MySQL AB, Sweden NetApp, Network Appliance, Open Network Technology for Appliance Products, Write Anywhere File Layout and WAFL are trademarks or registered trademarks of Network Appilance, Inc. in the United States and other countries Oracle is a registered trademark of ORACLE Corporation EMC, CLARiiON, Symmetrix, PowerPath, Celerra and SnapSure are trademarks or registered trademarks of EMC Corporation in the United States and other countries VMware, the VMware "boxes" logo and design, Virtual SMP and VMotion are regis-tered trademarks or trademarks (the "Marks") 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.

3 Contents Contents 1 Introduction Purpose of this Document General Usage of SAP Installation Guide During Installation... 1 Special Hints for FlexFrame Overview Notational Conventions... 2 Document History Related Documents Hotlinks for FlexFrame Getting Started FlexFrame Virtualization of SAP Services Preparations Gathering SAP Services Information Supported Hardware for Application Nodes SAP Service Connection OSS Network Connection with Dedicated saprouter Server OSS Network Connection without Dedicated saprouter Server Related SAP Notes FA Agents SAP Service Scripts for Virtualizing Applications Starting a Configuration Configuring the Service Status Path Configuring the Interfaces Host Names Operating System in General Linux Preparations for Database Installation SAP Installation with Database DB Software Requirements Pre-Installation Steps Mount Options Database files (sapdata, saplog) Binaries and Configuration files Installation Guide for SAP Solutions

4 Contents 8 Preparations for SAP Installation General How to configure the interfaces manually ASCS ABAP Central Service Instance in General SAP Java Cryptographic Toolkit Setting up SAP directories (Control Center) Standard Volumes Specify volumes of your own SID/Poolspecific volumes Using SAN Usage of /dev/urandom SAP Installation - Overview Installing SAP 4.6C SR SAPDB / MaxDB / Oracle Installing the Central Instance (CI) Installing Web AS 6.40 with NetWeaver04 SR Description of Web AS 6.40 JAVA Web AS 6.40 NetWeaver04SR1 JAVA MaxDB/Oracle SCS DB JC J CI DB APP Web AS 6.40 ABAP + JAVA-AddIn NetWeaver04SR CI DB SCS Web AS 6.40 Application Server JAVA-AddIn Installing NetWeaver 7.0SR Installation of SAP Solutions Prerequisite Checker (Linux) Sapinit File (Linux) installsapinit.sh symlink (Linux) Services File (Linux) NetWeaver 7.0SR3 and Oracle NetWeaver 7.0SR3 and MaxDB NetWeaver 7.0SR3 MaxDB76 and SLES9_x86/SLES10_x NetWeaver 7.0SR3 MaxDB Installation Guide for SAP Solutions

5 Contents 12.9 NetWeaver 7.0SR3 and EP NetWeaver 7.0SR3 ABAP+JAVA-AddIn NetWeaver 7.0SR3 JAVA only NetWeaver 7.01/SLES LiveCache ERS Enque Replicated Server (until NetWeaver 2004s SR3) Installation of SAP Solutions Post Phase Installing SAP Creating a New SID Using ff_sid_adm.pl Service Cannot Be Started EHP Installer Issues Mandatory SMD installation request EHP Installer Requests Entries in /etc/services EHP Installer JAVA process cannot be started ERS Installation hints Post Installation Tasks (SAP 7.1 only) Installing SAP Creating a New SID Using ff_sid_adm.pl SCS/ASCS (SAP 7.3) Installation hints ERS Installation hints Post Installation Tasks Install nonclassic SAP services BOBJ Business Objects Enterprise BOBJ preparations BOBJ installation BOBJ post installation BOBJ Login to CMC (Central Management Console) CMS Content Server CMS preparations CMS http server installation CMS installation CMS post installation CMS - Migration from project specific solutions MDM Master Data Management MDM preperations MDM Database installation MDM installation MDM post installation MDM - Migration from project specific solutions Installation Guide for SAP Solutions

6 Contents 15.4 SMD Solution Manager Diagnostics SMD - Migration from project specific solutions TREX Search and Classification TREX preparations TREX installation TREX post installation TREX trouble shooting TREX - Migration from project specific solutions Database Installation Installation of Oracle in General Installation of Oracle Post-Oracle 9.2 Installation Steps Installation of Oracle Post-Oracle 10.2 Installation Steps Oracle general post installation steps TNS Listener for Oracle listener.ora Host Name Changes in tnsnames.ora Oracle Patch Installation Installation of SAPDB / MaxDB XUSER MaxDB 7.5/7.6/7.7 /etc/opt/sdb MaxDB MaxDB MaxDB IO Balancing MaxDB configuration files Directories for sapdata / saplog SAP Installation with Database DB Installing DB LDAP-Plugin Transparent LDAP authentication Install SAP Changes in System Files Post Installation Steps Configuration of FA Agents Migration SLES9 to SLES10 / SLES Image independent JAVA JDK File structures and profiles Java Configuration Tool Java path settings for SDM Restart the services with new JAVA path Installation Guide for SAP Solutions

7 Contents 19 Post-SAP Installation Steps Configuring the Virtual Host Name Manually Central Instance (not valid for Web AS 6.40 J2EE) Database Instance (also valid for WebAS 6.40 J2EE) Application Instance (not valid for WebAS 6.40 J2EE) SCS Instance ASCS Instance (WebAS 7.00) NetWeaver 7.0 / NetWeaver 7.0SR1/SR Configuring the Virtual Host Name for Web AS 6.40 ABAP and JAVA-AddIn / WebAS 6.40 JAVA Start Script startdb for Oracle and SAPDB/MaxDB/DB Stop Script stopdb for Oracle and SAPDB/MaxDB/DB Scheduling of Batch Jobs (CCMS) Profile Parameters for DEFAULT.PFL Profile Parameters for the Start Profile Profile Parameters for the Instance Profile SAP Start and Stop Mechanism (Release 4.6CSR2) SAP License SAPLogon SAPGUI SAPROUTER on the Control Node Configuration File for /etc/init.d/saprouter Configuration File saprouter SAP System Administration Upgrading Application Software Software Administration Starting and Stopping SAP Services Application Software SAP Release Upgrade Services Port Instance profile Transport Directory Printing in FlexFrame Possible Printing Architectures and Methods Local Printing (Access Methods C and L) Remote Printing (Access Methods S and U) Front-end Printing on Local Printers BRBACKUP and SAPDBA/BRCONNECT Solution 1 for Oracle and SAPDB/MaxDB Solution 2 for Oracle Troubleshooting Installation Guide for SAP Solutions

8 Contents 23 Abbreviations Glossary Index Installation Guide for SAP Solutions

9 Introduction 1 Introduction As we continue to improve the installation process, this document is permanently subject to change. The latest version can be found at 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. Installation Guide for SAP Solutions 1

10 Introduction 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 <fixed font> fixed font Names of paths, files, commands, and system output. Names of variables User input in command examples (if applicable using <> with variables) 1.6 Document History Document Version Changes Date 1.0 First Edition Update Multiple JDK NW New Entry in Troubleshooting Installation Guide for SAP Solutions

11 Introduction 1.6 MAXDB changes BOBJ installation hints/login to CMC DB2 Fixpack issues 1.7 Additional hints to SAP 7.3 installation 1.8 References to old scripts (sapdb) Handling of /etc/opt/sdb DB2-FP4: errors while reading user account s password MaxDB installation hints Transparent LDAP (DB2) Installation Guide for SAP Solutions 3

12 Introduction 1.7 Related Documents FlexFrame for SAP Administration and Operation FlexFrame for SAP HW Characteristics Quickguides FlexFrame for SAP Installation ACC 7.2 FlexFrame for SAP Installation Guide for SAP Solutions FlexFrame for SAP Installation of a FlexFrame Environment FlexFrame for SAP Management Tool FlexFrame for SAP myamc.fa_agents Installation and Administration FlexFrame for SAP myamc.fa_messenger Installation and Administration FlexFrame for SAP 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.1A, 4.2A or 4.2B to 5.0A ServerView Documentation SUSE Linux Enterprise Server Documentation 1.8 Hotlinks for FlexFrame Global information on FlexFrame FlexFrame for SAP manuals Official FlexFrame home page Dynamic Infrastructures and FlexFrame for SAP Service Partner Portal for FlexFrame for SAP SAP NetWeaver Fujitsu and SAP FlexFrame for SAP on Linux 4 Installation Guide for SAP Solutions

13 Introduction Global information on FlexFrame SAP on Linux (released kernels, hardware and distributions for SAP) PRIMERGY manuals PRIMERGY Information Center Knowledge Documentation on ServerView Suite Software Software by Fujitsu Installation Guide for SAP Solutions 5

14

15 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 Installation Guide for SAP Solutions 7

16 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. You will be asked for the following details: 8 Installation Guide for SAP Solutions

17 Getting Started 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: and move to Supported Platforms Supported Hardware and select Fujitsu Please check that list against the Support Matrix provided with FlexFrame. Installation Guide for SAP Solutions 9

18

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

20 SAP Service Connection 3.2 OSS Network Connection without Dedicated saprouter Server The saprouter process can be configured on the Control Node cluster if there is no dedicated server for it (see chapter section SAPROUTER on the Control Node on page 184). 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 12 Installation Guide for SAP Solutions

21 SAP Service Connection 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! SAP Walldorf Tokio Foster City TELNET SAPGUI Gateway TELNET SAPGUI Customer Control Node 1 (saprouter) Control Node 2 (saprouter) SAPGUI SSH SAPGUI SSH SAPGUI SSH SAPGUI SSH Application Node 1 Application Node 2 Application Node... Application Node n 3.3 Related SAP Notes A table of related SAP Notes is provided below: SAP OSS note number Title Service connections: Composite note (overview) Telnet link to customer systems Installation Guide for SAP Solutions 13

22

23 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. Installation Guide for SAP Solutions 15

24

25 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 ff_service.sh Application Central Script to start, stop, etc a SAP service ff_service_functions ff_sapdb_functions ff_sapclassic_functions Function library for ff_service.sh Function library for ff_service.sh (databases) 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 sapservice_config sapservice_functions start_all_sapservices stop_all_sapservices Configration file of ff_service.sh Global customer-specific parameters Global parameters and functions; still available because of compatibility reasons Initial start of all configured applications Stops all running applications stop_all_sapservices_local Stops all running applications on the local node stop_all_sapservices_sid 5.1 Starting a Configuration Stops all running applications of one SID 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 Installation Guide for SAP Solutions 17

26 SAP Service Scripts for Virtualizing Applications # # 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 1. DB 1. DB 1. DB 1. DB 1. DB ABAP + ASCS + JAVA-AddIn 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 ). 18 Installation Guide for SAP Solutions

27 SAP Service Scripts for Virtualizing Applications 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 sid is the lower-case three-digit system ID Installation Guide for SAP Solutions 19

28 SAP Service Scripts for Virtualizing Applications 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: For the service type app: <service_type>_<sid>_host 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 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 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 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 20 Installation Guide for SAP Solutions

29 SAP Service Scripts for Virtualizing Applications 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= ls3195: NETMASK_CLIENT= NETMASK_SERVER= # # Interface # # # SunOS link aggregation # ~~~~~~~~~~~~~~~~~~~~~~~ # # real interfaces look like this: # fjgi # this is the first interface # fjgi # this is the second interface # fjgi :1 # this indicates that the first interface # # is active # fjgi :1 # this indicates that the second interface # # is active # # These interface names consist of three parts: # fjgi :1 # ^^^ interface number # ^^^^ vlan # ^^^^ GB-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: # Installation Guide for SAP Solutions 21

30 SAP Service Scripts for Virtualizing Applications # 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 db<sid>-se lc<sid>-se ci<sid>-se ascs<sid>-se app<id><sid>-se scs<sid>-se jc<sid>-se (SAP 7.1: j<id><sid>-se) ers<id><sid>-se j<id><sid>-se N/A Client LAN ci<sid> ascs<sid> app<id><sid> scs<sid> jc<sid> (SAP 7.1: j<id><sid>) ers<id><sid> j<id><sid> bobj<sid> 22 Installation Guide for SAP Solutions

31 SAP Service Scripts for Virtualizing Applications Server LAN N/A mds<id><sid>-se mdss<id><sid>-se mdis<id><sid>-se N/A trx<id><sid>-se Client LAN cms<sid> mds<id><sid> mdss<id><sid> mdis<id><sid> <monitored host> trx<id><sid> Explanation: id Consecutive two-digit number 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). Installation Guide for SAP Solutions 23

32

33 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 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. ( 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 Installation Guide for SAP Solutions 25

34

35 Preparations for Database Installation 7 Preparations for Database Installation Installation of Oracle Installation of MaxDB Installation of DB2 N/A N/A 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 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 DB2 Version 9.5 for Linux (Download from released for SAP 7.0 SR3 DB2 Version 9.7 for Linux (Download from 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 -dm-db2ldap Installation Guide for SAP Solutions 27

36 Preparations for Database Installation 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 n.doc/doc/c html 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 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. 28 Installation Guide for SAP Solutions

37 Preparations for Database Installation The most important options set for database and database software files are shown. For detailed information please refer to NFS manpage Database files (sapdata, saplog) Option rw hard, nointr rsize=32768, wsize=32768 proto=tcp nolock vers=3 timeo=600 retrans=2 suid bg Comment read/write operations allowed; NFS default value. No user interrupt is allowed. Process is always waits until server come back online. NFS default is nointr Block size for reading/writing. FlexFrame specific setting. Communication protocol TCP is used; NFS default value 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. NFS version used. Wait 60 sec until a retransmission is sent after timeout. NFS default is 0.7, the maximum value is 60 sec. At least two minor timeouts are accepted until a operation is aborted. NFS default is 3. Allow set-user-id or setgroup-id; NFS default value Retrial of mount is performed in background Binaries and Configuration files Option rw hard, nointr rsize=32768, wsize=32768 proto=tcp Comment NFS default value is used (rw). No user interrupt is allowed. FlexFrame specific setting. Communication protocol default tcp is used. Installation Guide for SAP Solutions 29

38 Preparations for Database Installation 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) 30 Installation Guide for SAP Solutions

39 Preparations for SAP Installation 8 Preparations for SAP Installation Installation directories and virtual interfaces SAP JAVA Cryptographic Toolkit (optional component) All platforms (see chapter 8.1) Linux (see chapter 6.1) Setup directory structures (default) (8.5.1) Configuration of virtual interfaces /dev/urandom 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) Setup interfaces manually (see chapter 8.2) Configuration of /dev/urandom (see chapter 8.6) 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. Installation Guide for SAP Solutions 31

40 Preparations for SAP Installation 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-CDname>). 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 32 Installation Guide for SAP Solutions

41 Preparations for SAP Installation 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. Installation Guide for SAP Solutions 33

42 Preparations for SAP Installation 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. 34 Installation Guide for SAP Solutions

43 Preparations for SAP Installation 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) 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 S 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 CN1# ff_setup_sid_folder.sh -p pool1 s S SID/Poolspecific volumes SID- or pool-specific volumes are specified by FF Configuration Tool. So you just enter ff_setup_sid_folder.sh. Example: CN1# ff_setup_sid_folder.sh -p pool1 s S03 Installation Guide for SAP Solutions 35

44 Preparations for SAP Installation 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_setup_sid_folder.sh -p pool1 s 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). 36 Installation Guide for SAP Solutions

45 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 3. Preparations for Database Installation 4. Preparations for SAP installation General hint how to configure interfaces manually please refer to Interface Configuration (see chapter 8.2) Check correspoding installation hints (see chapter 7) Check corresponding installation hints (see chapter 8) Installation Guide for SAP Solutions 37

46 SAP Installation - Overview 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.13) or ERS 7.00 (see chapter 12.14) or SAP 7.1 (see chapter 13) or 38 Installation Guide for SAP Solutions

47 SAP Installation - Overview 6. Post installation steps (database) SAP 7.1 ERS (see chapter 13.3 ) or SAP 7.3 (see chapter 14) Check corresponding installation hints (see chapter15.3.1) 7. Post installation steps (SAP) Check corresponding installation hints (see chapter16) Installation Guide for SAP Solutions 39

48

49 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 R3SETUP does not yet permit installation of SAP on NFS drives in this version. If sapinst is used for installation (release 4.7 and above or Web AS 6.20 or 6.40), installation on the NetApp Filer with NFS is directly supported. Installation Guide for SAP Solutions 41

50 Installing SAP 4.6C SR2 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 0 ) 2a. DB post installation step Oracle 9.2 only (see chapter ) 3. Setting virtual DB host All platforms (see chapter16.1.2) 4. Install CI service All platforms (see chapter 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 Installation Guide for SAP Solutions

51 Installing SAP 4.6C SR2 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. Installation Guide for SAP Solutions 43

52 Installing SAP 4.6C SR2 Restart R3SETUP. Edit the *.R3S file and change STATUS=ERROR to STATUS=OK. 44 Installation Guide for SAP Solutions

53 Installing SAP 4.6C SR2 Restart R3SETUP. Edit the *.R3S file and set the parameter BREAK_ON_NFS_PERMISSION_ERROR=NO. Installation Guide for SAP Solutions 45

54 Installing SAP 4.6C SR2 Restart R3SETUP 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 46 Installation Guide for SAP Solutions

55 Installing SAP 4.6C SR2 # SAPINST_JRE_HOME=/usr/j2sdk/j2sdk1.4.2_10 # export SAPINST_JRE_HOME #./sapinst SAPINST_USE_HOSTNAME=ciosm <MASTER-DVD>/product.catalog Installation Guide for SAP Solutions 47

56 Installing SAP 4.6C SR2 48 Installation Guide for SAP Solutions

57 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 readonly. 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. Installation Guide for SAP Solutions 49

58

59 Installing Web AS 6.40 with NetWeaver04 SR1 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 ) 3. Virtualize user environment for SCS host JAVA (see chapter16.1.4) 4. Install DB service ABAP (Oracle) (see chapter ) 5. Virtualize user environment for DB host ALL see chapter Install Central Instance ABAP (Oracle) (see chapter ) 7. Virtualize user environment for CI host All see chapter Install Application service ABAP (see chapter Virtualize user environment for application host All see chapter JAVA+ABAP (see chapter ) JAVA+ABAP (see chapter ) JAVA (see chapter ) ALL see chapter JAVA (see chapter ) All see chapter JAVA (see chapter ) All see chapter JAVA-Addin (see chapter ) ALL see chapter JAVA-Addin (see chapter ) All see chapter All see chapter Installation Guide for SAP Solutions 51

60 Installing Web AS 6.40 with NetWeaver04 SR 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 91). 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. Installation Guide for SAP Solutions 52

61 Installing Web AS 6.40 with NetWeaver04 SR 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 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 Installation Guide for SAP Solutions 53

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

63 Installing Web AS 6.40 with NetWeaver04 SR1 Type in the virtual DB host name Installation Guide for SAP Solutions 55

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

65 Installing Web AS 6.40 with NetWeaver04 SR 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:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<db_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product_ha.catalog Installation Guide for SAP Solutions 57

66 Installing Web AS 6.40 with NetWeaver04 SR1 If you install a J2EE engine using the product_ha.catalog, and during the database installation step you see a dialog asking for an installation drive, stop the installation and insert the following three lines to your 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 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:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<jc_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product_ha.catalog 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:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<j_instance_number_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product_ha.catalog 58 Installation Guide for SAP Solutions

67 Installing Web AS 6.40 with NetWeaver04 SR 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:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<ci_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product.catalog Installation Guide for SAP Solutions 59

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

69 Installing Web AS 6.40 with NetWeaver04 SR1 Type in the virtual DB host name Installation Guide for SAP Solutions 61

70 Installing Web AS 6.40 with NetWeaver04 SR 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) applnode1:~#> cd /usr/sap/<sid>/install_db applnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<db_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product.catalog After successful loading the database, the automatic startup of SAP may fail sometimes. Start the SAP manually Stop the SAPINST Restart the SAP installer using SAPINST_SKIP_ERRORSTEP true 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:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<app_instance_number_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product.catalog 11.3 Web AS 6.40 ABAP + JAVA-AddIn NetWeaver04SR 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 applnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<ci_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product.catalog 62 Installation Guide for SAP Solutions

71 Installing Web AS 6.40 with NetWeaver04 SR 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) applnode1:~#> cd /usr/sap/<sid>/install_db applnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<db_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product.catalog 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!). 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 applnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<db_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product.catalog Central Instance Finalization: applnode1:~#> cd /usr/sap/<sid>/install applnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<ci_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product.catalog Example: The example shows an installation on MaxDB. applnode1:~#> cd /usr/sap/<sid>/install applnode1:~#> <PATH_to_SAP_MASTER_DVD>/sapinst extract applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<ci_virtual_hostname> <PATH_to_SAP_MASTER_DVD>/product.catalog Installation Guide for SAP Solutions 63

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

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

74 Installing Web AS 6.40 with NetWeaver04 SR1 When the installation has finished successfully, you have to change the hostname of the SCS instance manually. If the installation of the SCS Installation aborts at the step Load Java Database Content (step 19) with the error message no connection to network adapter, please proceed as follows: Stop the Oracle listener process. Change the virtual host name db<sid>-se to the real host name (uname a) in the listener.ora and tnsnames.ora. Start the Oracle listener process and click the Retry button from the SAPINST GUI. 66 Installation Guide for SAP Solutions

75 Installing Web AS 6.40 with NetWeaver04 SR1 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 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> <PATH_to_SAP_MASTER_DVD>/product.catalog Installation Guide for SAP Solutions 67

76 Installing Web AS 6.40 with NetWeaver04 SR1 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. 68 Installation Guide for SAP Solutions

77 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 readonly. 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 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 :29:35 CJSlibModule::writeError_impl() CJS Could not start instance 'JC41' of SAP system OLP. ERROR :29:35 CJSlibModule::writeError_impl() CJS 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 Installation Guide for SAP Solutions 69

78 Installing NetWeaver 7.0SR3 MaxDB76 / 77 on SLES9_x86/SLES10_x86 specifics (see chapter 12.7) 5a. Standard installation Types or 5b. Live Cache (MaxDB 76/77) 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) Additional installation requests (see chapter c. Enqueue Replicated Server (ERS) Installation until NetWeaver 2004s SR3 (see chapter ) 6. General post installation steps (SAP 7.0 only) Linux (see chapter 6.1) 70 Installation Guide for SAP Solutions

79 Installing NetWeaver 7.0SR 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: Installation Guide for SAP Solutions 71

80 Installing NetWeaver 7.0SR3 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/g sapinst 5. Restart the installation: applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<virtual_hostname> Prerequisite Checker (Linux) 72 Installation Guide for SAP Solutions

81 Installing NetWeaver 7.0SR3 suse-sapinit: SAP has renamed the name of the package into sapinit Kernel/Glibc Version: You can ignore the warning Sapinit File (Linux) WARNING :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 :06:51 CJSlibModule::writeError_impl() MUT 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 :06:51 [iaxxgenimp.cpp:736] showdialog() FCO 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[]]> Installation Guide for SAP Solutions 73

82 Installing NetWeaver 7.0SR3 </strval> </fld> <fld name="stop_after"> <strval><![cdata[]]> </strval> </fld> <fld name="state_set_by_step_state_editor"> <strval><![cdata[]]> </strval> 2. Restart the installation: applnode1:<install_dir> >./sapinst SAPINST_USE_HOSTNAME=<virt._hostname> 12.3 installsapinit.sh symlink (Linux) WARNING :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 insserv: can not symlink(../sapinit, rc5.d/s14sapinit): Read-only file system insserv: can not symlink(../sapinit, rc5.d/k08sapinit): Read-only file system ERROR :43:23 CJSlibModule::writeError_impl() MUT 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 insserv: can not symlink(../sapinit, rc5.d/s14sapinit): Read-only file system insserv: can not symlink(../sapinit, rc5.d/k08sapinit): Read-only file system ERROR :43:23 [iaxxgenimp.cpp:736] showdialog() FCO 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 executed with status ERROR. 1. Proceed as follows: applnode1:<install_dir> > vi keydb.xml <fld name="stepkey"> 74 Installation Guide for SAP Solutions

83 Installing NetWeaver 7.0SR3 <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> applnode1:<install_dir> >./sapinst SAPINST_USE_HOSTNAME=<virt._hostname> 12.4 Services File (Linux) ERROR :22:09 [syxxsyshlp.cpp:78] syslib::printoserror(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage) FSL 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 :22:09 [syuxcfile.cpp:417] CSyFileImpl::copy(const CSyPath & /etc/services.saptmp, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const FSL Unable to access file /etc/services.saptmp: cannot get write access. ERROR :22:09 [syxxcsent.cpp:492] CSyServicesEntryImpl::editServices(ISyServicesEntry::eWriteMode REPLACE_NAME) const FSL Unknown exception caught when trying to add an entry to the service file. ERROR :22:09 CJSlibModule::writeError_impl() MUT Caught ESyException in Modulecall: ESAPinstException: error text undefined. Installation Guide for SAP Solutions 75

84 Installing NetWeaver 7.0SR3 1. Abort the installation and proceed as follows: applnode1:<install_dir> > vi keydb.xml <row> <fld name="stepkey"> <strval><![cdata[ NW_ABAP_ASCS ind ind ind ind 0 0 NW_System ind ind ind ind 5 0 createports]]> </strval> </fld> <fld name="status"> <strval><![cdata[error]]> to OK </strval> 2. Restart the installation: applnode1:<install_dir> >./sapinst SAPINST_USE_HOSTNAME=<virt._hostname> 12.5 NetWeaver 7.0SR3 and Oracle 10 The installation could fail due to the following eror: ERROR :24:26 [iaxxinscbk.cpp:271] abortinstallation CJS 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 bit Production With the Partitioning and Data Mining options.<br>solution: See ora_sql_results.log and the Oracle documentation for details. ERROR :24:26 CJSlibModule::writeError_impl() 76 Installation Guide for SAP Solutions

85 Installing NetWeaver 7.0SR3 MUT Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined. ERROR :24:26 [iaxxgenimp.cpp:736] showdialog() FCO 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 Restart the installation. perl i.bak p e s/umask 027/umask 022/ sapinst applnode1:<install_dir> > chmod 777 * applnode1:<install_dir> > chmod 777. applnode1:<install_dir> >./sapinst SAPINST_USE_HOSTNAME=<virt._hostname> 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] :20:53 [syuxcuser.cpp:1813] CSyUserImpl_getOsInfos(ILogBook *m_logbook, iastring sname, iastring sid, tsyuserinfo& msuserinfo) FSH 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 :20:53 [syuxcuser.cpp:278] CSyUserImpl::CSyUserImpl(const CUserData&, bool) FSL Account user="undefined" does not exist. TRACE [iaxxejsbas.hpp:379] handleexception<esyexception>() Converting exception into JS Exception ESyException. ERROR :20:53 CJSlibModule::writeError_impl() Installation Guide for SAP Solutions 77

86 Installing NetWeaver 7.0SR3 MUT Caught ESyException in Modulecall: ESAPinstException: error text undefined. TRACE [iaxxejsbas.hpp:451] EJS_Base::dispatchFunctionCall() JS Callback has thrown unknown exception. Rethrowing. ERROR :20:53 [iaxxgenimp.cpp:653] showdialog() FCO 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 executed with status ERROR. 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 135. cn1:~#> rm sdb cn1:~#> cp p /FlexFrame/volFF/pool-<pool_name>/sapdb/<image_name>/sql/sdb. 3. Restart the installation: applnode1:<install_dir> >./sapinst SAPINST_USE_HOSTNAME=<virt._hostname> 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. 78 Installation Guide for SAP Solutions

87 Installing NetWeaver 7.0SR NetWeaver 7.0SR3 MaxDB76 and SLES9_x86/SLES10_x86 During the ABAP import using MaxDB76 and SLES9/SLES10 the installation has permission trouble: Installation Guide for SAP Solutions 79

88 Installing NetWeaver 7.0SR3 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 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 IBM J9 2.2 Linux amd64-64 j9xa64142ifx (JIT enabled) J9VM _1742_LHdSMr JIT - r7_level _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 :27:58 CJSlibModule::writeError_impl() CJS Program 'Migration Monitor' exits with error code 2. For details see log file(s) import_monitor.java.log, import_monitor.log. ERROR :27:58 [iaxxgenimp.cpp:736] showdialog() FCO 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 :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: 80 Installation Guide for SAP Solutions

89 Installing NetWeaver 7.0SR3 ERROR :25:45 FCO 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 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 ERR ,ERR_NEEDADMI: The operating system user is not a member of the database administrators group ,ERR_RTE: Runtime environment error 20145,UNIX password ******** 1. Follow the instructions of SAP note: Click on the RETRY button from the SAPINST screen 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'/' ': 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 Installation Guide for SAP Solutions 81

90 Installing NetWeaver 7.0SR3 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. 82 Installation Guide for SAP Solutions

91 Installing NetWeaver 7.0SR 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.send(wbemremoteclient.java:694) at com.sap.sld.api.wbem.client.wbemremoteclient.send(wbemremoteclient.java:638) 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 javax.servlet.http.httpservlet.service(httpservlet.java:853) Installation Guide for SAP Solutions 83

92 Installing NetWeaver 7.0SR3 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.startservlet(requestanalizer.java:325) 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 java.net.socketinputstream.read(socketinputstream.java:182) 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.wbemhttprequestsender.send(wbemhttprequestsender.java:142) more caused by: 84 Installation Guide for SAP Solutions

93 Installing NetWeaver 7.0SR3 java.net.sockettimeoutexception: Read timed out at java.net.socketinputstream.socketread0(native Method) at java.net.socketinputstream.read(socketinputstream.java:129) at java.net.socketinputstream.read(socketinputstream.java:182) 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.wbemhttprequestsender.send(wbemhttprequestsender.java:142) at com.sap.sld.api.wbem.client.wbemremoteclient.send(wbemremoteclient.java:720) at com.sap.sld.api.wbem.client.wbemremoteclient.send(wbemremoteclient.java:694) at com.sap.sld.api.wbem.client.wbemremoteclient.send(wbemremoteclient.java:638) 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 javax.servlet.http.httpservlet.service(httpservlet.java:853) Installation Guide for SAP Solutions 85

94 Installing NetWeaver 7.0SR3 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.startservlet(requestanalizer.java:325) 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= USER=J2EE_ADMIN... Import Status: PREPARING # ERROR: CIM_ERR_FAILED: IO error: Read timed out 86 Installation Guide for SAP Solutions

95 Installing NetWeaver 7.0SR3 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. Installation Guide for SAP Solutions 87

96 Installing NetWeaver 7.0SR 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 Info: Checking if another SDM is running on port 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 :26:59 [iaxxinscbk.cpp:271] abortinstallation MUT SDM call of addsubstvars ends with returncode 4 ERROR :26:59 CJSlibModule::writeError_impl() MUT Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined. ERROR :26:59 [iaxxgenimp.cpp:736] showdialog() FCO 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. perl i.bak p e s/umask 027/umask 022/ sapinst 2. Restart the installation: applnode1:~#>./sapinst SAPINST_USE_HOSTNAME=<virt._hostname> NetWeaver 7.01/SLES 9 Using NetWeaver 7.01 and SLES9 requires a special version of libstdc++ or libgcc_s. Refer to SAP-Note Installation Guide for SAP Solutions

97 Installing NetWeaver 7.0SR 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 ERS Enque Replicated Server (until NetWeaver 2004s SR3) For installation hints please have a look into corresponding SAP sites (start at /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. Installation Guide for SAP Solutions 89

98 Installing NetWeaver 7.0SR 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. 90 Installation Guide for SAP Solutions

99 Installing SAP 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. 1. Introduction All Platforms (see chapter 10) 2. Install DB service 3. Setting virtual DB host All platforms (see chapter ) 4. Install ASCS instance 5. Setting virtual ASCS host All platforms (see chapter ) 6. Install CI service 7. Setting virtual CI host All platforms (see chapter ) 8. Install Application service 9. Setting virtual Application host All platforms (see chapter ) 10. Install ERS instance (optional) All platforms (see chapter 13.4) 11. Installation Issues Service cannot be started (see chapter 13.2 ) 12. 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 (only valid with -sapversion 7.1): Installation Guide for SAP Solutions 91

100 Installing SAP 7.1 ff_sid_adm.pl --op add --pool pool1 -sid S07 --sapversion db MaxDB77:159 --sap ci:57:157:157 --sap ascs:55:155:155 --sap app:58:158:158 --sap ascs:56:156:156 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] :57: CJS 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. 92 Installation Guide for SAP Solutions

101 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 :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, :33:50, 0:05:42, rslgcoll, Central Syslog Collector, GREEN, Running, :33:50, 0:05:42, rslgsend, Central Syslog Sender, GREEN, Running, :33:50, 0:05:42, igswd_mt,, GREEN, Running, :33:50, 0:05:42, jer1bx5:~ # With SLES9 you have to start sapcontrol under control of user <sid>adm EHP Installer Issues 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. Installation Guide for SAP Solutions 93

102 Installing SAP 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 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 94 Installation Guide for SAP Solutions

103 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 Installation Guide for SAP Solutions 95

104 Installing SAP 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. 96 Installation Guide for SAP Solutions

105 Installing SAP Click on the diskette symbol to save and restart instance: Installation Guide for SAP Solutions 97

106 Installing SAP ERS 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/m01/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> 98 Installation Guide for SAP Solutions

107 Installing SAP 7.1 Installation Guide for SAP Solutions 99

108 Installing SAP 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 s M02 t ers i 01 a start 2.3 Change the status value in keydb.xml from ERROR to OK. 100 Installation Guide for SAP Solutions

109 Installing SAP If you have an ERS instance for SCS you have to do the same procedure like in step 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. Installation Guide for SAP Solutions 101

110 Installing SAP Installing SAP 7.3 SAP 7.3 may be used with ORACLE 11, MAXDB 7.8 and DB2 V9.7 only. Full support of SAP 7.3 in FlexFrame 5.0A is given with patch 40. From SAP 7.1 on the SAP system contains its own JVM and you do not set your environment to use SDK. 1. Introduction All Platforms (see chapter 10) 2. Install DB service 3. Setting virtual DB host All platforms (see chapter ) 4. Install SCS/ASCS instance All Platforms (see chapter 14.2) 5. Setting virtual ASCS host All platforms (see chapter ) 6. Install CI service 7. Setting virtual CI host All platforms (see chapter ) 8. Install Application service 9. Setting virtual Application host All Platforms (see chapter ) 10. Install optional ERS (SAP 7.3) All Platforms (see chapter 14.3) 11. Installation Issues Service cannot be started (see chapter 13.2 ) 12. Installation Issues (optional) EHP installer issues (see chapter 13.3 ) 102 Installation Guide for SAP Solutions

111 Installing SAP 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 M01 --sapversion db MaxDB78:159 --sap ci:57:157:157 --sap scs:04:155:155 --sap app:58:158:158 --sap ascs:04:156:156 Therefore 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) Installation hints 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 After modifying the filenames they have to look like this: bx91-11:m02adm 17> ls al grep scs Installation Guide for SAP Solutions 103

112 Installing SAP 7.3 -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 m02adm to 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>. In the file /sapmnt/<sid>/profile/ <SID>_SCS03_scs<sid> change ascs to scs. 104 Installation Guide for SAP Solutions

113 Installing SAP ERS Installation hints 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> Installation Guide for SAP Solutions 105

114 Installing SAP Installation Guide for SAP Solutions

115 Installing SAP 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 -s M02 -t ers -i 01 -a start 2.3 Change the status value in keydb.xml from ERROR to OK. Installation Guide for SAP Solutions 107

116 Installing SAP If you have an ERS instance for SCS you have to do the same procedure like in step 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. 108 Installation Guide for SAP Solutions

117 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 CMS Content Server 6.40 MDM Master Data Management 7.1 SMD Solution Manager Diagnostics 7.1 TREX Search and Classification 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 for storing BOBJ metadata. It also expects a Tomcat installation as offered with installation script. All other configurations are handled as project solutions. FlexFrame itself is able to install BOBJ within its virtualized environment. Please ask professional service about restrictions (defined by SAP) using BOBJ in a virtualized environment. 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>. Installation Guide for SAP Solutions 109

118 Install nonclassic SAP services Please follow the main steps shown in the table below: 1. Installation preperations see chapter Install BOBJ see chapter Post installation see chapter 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 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. 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/etc/hosts file BOBJ installation To install the software you login to <sid>adm and perform 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 110 Installation Guide for SAP Solutions

119 Install nonclassic SAP services 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 Download the corresponding process explorer (Polestar) from SAP software download site Execute <polestar-installation-dir>/polstar/install.sh /usr/sap/<sid> 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 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 ip to bobj<sid>>:8080/cmcapp/logon.faces If you will 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. Installation Guide for SAP Solutions 111

120 Install nonclassic SAP services 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 112 Installation Guide for SAP Solutions

121 Install nonclassic SAP services a client instance, hostname cms<sid> Please follow the main steps shown in table below: 1. Installation preperations see chapter Install http server see chapter Install CMS see chapter Post installation see chapter 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 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 CMS http server installation Download http server software (e.g. http tar) and do the installation cd <installationdir> /<http-software> call./configure with-expat=builtin prefix /usr/sap<sid> call make call make install 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 Installation Guide for SAP Solutions 113

122 Install nonclassic SAP services # Logon to <sid>adm and create XUSER by xuser d <SID> -n db<sid>-se u Control,control U c S SAPR3 t0 I 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 Restart myamc agents Reset interface by ff_service.sh t cms s <sid> -a istop 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 114 Installation Guide for SAP Solutions

123 Install nonclassic SAP services 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 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<nt><sid> and mds<nt><sid>-se one or more instances of type mdss, hostname mdss<nt><sid> and mdss<nt><sid>-se one or more instances of type mdis, hostname mdis<nt><sid> and mdis<nt><sid>-se Please follow the main steps shown in table below: 1. Installation preperations see chapter Iinstall database see chapter Install MDM see chapter Post installation see chapter MDM preperations 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. Installation Guide for SAP Solutions 115

124 Install nonclassic SAP services 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 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> On installation node you Stop the myamc agents 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 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 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> 116 Installation Guide for SAP Solutions

125 Install nonclassic SAP services 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 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 Installation Guide for SAP Solutions 117

126 Install nonclassic SAP services 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 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 ) 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 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 <installationdir>/sapinst -extract Change umask 027 to umask 022 in sapinst./sapinst SAPINST_USE_HOSTNAME=mds<nr><sid> <installationdir>/product.catalog 118 Installation Guide for SAP Solutions

127 Install nonclassic SAP services 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* Restart myamc agents Reset interfaces by ff_service.sh MDM - Migration from project specific solutions MDM 7.1 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 Stop the monitoring of the service specific services using ff_service.sh -a nowatch Stop the services by ff_services.sh Installation Guide for SAP Solutions 119

128 Install nonclassic SAP services 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> Create aliases with the old hostnames noticed before by ff_hosts.sh p <pool> - 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. 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. 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 accordingly 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> SMD - Migration from project specific solutions SMD 7.1 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 Agents from SMD 7.1 are organized within an own SID (agents from different SAP service SIDs can be putted into a SMD-SID 120 Installation Guide for SAP Solutions

129 Install nonclassic SAP services 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 Create aliases with the old hostnames noticed before by ff_hosts.sh p <pool> - 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 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. Please follow the main steps shown in table below: 1. Installation preperations see chapter Install TREX see chapter Post installation see chapter Trouble shooting see chapter TREX 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 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> On installation node you Installation Guide for SAP Solutions 121

130 Install nonclassic SAP services Stop the myamc agents 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 TREX installation There are different ways to install TREX software. A method using sapinst is described in this section. To install the software you login to <sid>adm and perform cd /<installationdir> <installationdir>/sapinst -extract <installationdir>/sapinst SAPINST_USE_HOSTNAME=trx<nt><sid> \ <installationdir>/product.catalog cd /usr/sap/<sid>/trx<nr> mkdir work chown <sid>adm:sapsys work TREX post installation If the installation procedure is finished you Restart myamc agents Reset interface by ff_service.sh t trx s <sid> -i <nr> -a istop 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. 122 Installation Guide for SAP Solutions

131 Install nonclassic SAP services One known difference is that the profiles are either stored in /sapmnt/<sid>/profiles or in /usr/sap/<sid>/sys/profiles. Therefore you are 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 are complaint about missing directory work during service start procesdure please create the directory manually TREX - Migration from project specific solutions TREX 7.1 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 Stop the monitoring of the service specific services using ff_service.sh -a nowatch Stop the services by ff_services.sh 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> Create aliases with the old hostnames noticed before by ff_hosts.sh p <pool> - 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> Installation Guide for SAP Solutions 123

132 Install nonclassic SAP services 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> In the home directory of user <sid>adm (/home_sap/ <sid>adm) there are some files which have to be copied and modified Copy hostname_default to hostname_default_trx<instanznr><sid> Write echo trx<instanzr><sid> to hostname_default_trx<instanznr><sid> into hostname_default_trx<instanznr><sid> 124 Installation Guide for SAP Solutions

133 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 Installation of Oracle 10.2 All platforms (see chapter 16.2) All platforms (see chapter 16.3) General installation hints Post installation steps Patch installation General installation hints Post installation steps Patch installation Installation of Oracle 11g All platforms Depending on SAP installation package installation of Oracle 11g is an upgrade procedure from or fully integrated in installation process. The updgrade from will be described in a specific Best Practice paper available at Fujitsu. You can request that paper by Sonderfreigabe Installation of Oracle 11g (fully integrated installation process) General post installation steps for Oracle All platforms (see chapter 16.3) TNS listener for Oracle (see chapter ) Contents of listener.ora (see chapter ) General installation hints Post installation steps Patch installation Installation Guide for SAP Solutions 125

134 Database Installation Installation of SAPDB/MaxDB Installation of DB2 hostname in tnsnames.ora (see chapter ) All platforms (see chapter 16.6) All platforms (see chapter 7.1 ) Handling of XUSER (see chapter ) Handling /etc/opt/sdb (see chapter ) MaxDB 7.6 (see chapter ) MaxDb 7.7 (see chapter ) MaxDB 7.8 (see chapter ) IO Balancing Directories for sapdata/saplog 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 (Listener), (orainventory) and (9i) or (10g) (Oracle client software) 126 Installation Guide for SAP Solutions

135 Database Installation 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 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 , , , , and ). 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 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 Installation Guide for SAP Solutions 127

136 Database Installation 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. 128 Installation Guide for SAP Solutions

137 Database Installation 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 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 Installation Guide for SAP Solutions 129

138 Database Installation /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 Oracle general post installation steps 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 130 Installation Guide for SAP Solutions

139 Database Installation listener.ora Every database instance must have its own listener.ora. The relevant parameter is HOST in the section LISTENER. Example: 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. 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>) ) Installation Guide for SAP Solutions 131

140 Database Installation 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 ) 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 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) 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 132 Installation Guide for SAP Solutions

141 Database Installation 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: 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 There is also an issue using dbmverifypw as described in Troubleshooting (see chapter 22) XUSER After virtualizing a SAPDB/MaxDB instance, the xuser command has to be called with the correct parameters according to OSS note and Installation Guide for SAP Solutions 133

142 Database Installation The following screenshot shows an example for the SAPMS4 user: Afterwards, the transaction db50 has to be called according to OSS note 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. 134 Installation Guide for SAP Solutions

143 Database Installation 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 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 <filer> --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 <filer> --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. After the installation is completed copy the file from /etc/opt/sdb to the /sapdb/sql/sdb directory and recreate the previous link. CN: cd /FlexFrame/volFF/os/Linux/<platform>/root_img CN: cp etc/opt/sdb /FlexFrame/volFF/pool-<pool>/<platform>/sapdb/sql/sdb Installation Guide for SAP Solutions 135

144 Database Installation CN: rm etc/opt/sdb CN: ln -s /sapdb/sql/sdb /etc/opt/sdb CN: ff_exports.pl -op add -nas <filer> \ --path /vol/volff/os/<platform>/root_img \ --option "-sec=sys,ro,anon=0 an1: /etc/init.d/autofs restart an1: remount ro / Check / Create the following directories (from the Application Node): an1:~# mkdir /sapdb/data/config an1:~# mkdir /sapdb/data/config/install 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>. 136 Installation Guide for SAP Solutions

145 Database Installation 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 :11: FSL Command '/usr/sbin/usermod' with parameters '-c "Database Software Owner" sdb' failed with return code 5: Cannot lock password file: already locked. Installation Guide for SAP Solutions 137

146 Database Installation set attribute gecos of user sdb in LDAP database to Database Software Owner (using ff_user_adm.pl). MaxDB 7.7 (built 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/*) 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 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 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 138 Installation Guide for SAP Solutions

147 Database Installation 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 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/p SAP Installation with Database DB2 With the current release of FlexFrame we support DB2 database also with the Management Tool 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>. Installation Guide for SAP Solutions 139

148 Database Installation 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 are 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 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 140 Installation Guide for SAP Solutions

149 Database Installation 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 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 Transparent LDAP authentication In future releases there will be some security enhancements which need a correct LDAP configuration to enable DB2 reading LDAP. 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 Installation Guide for SAP Solutions 141

150 Database Installation 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 o db2set DB2AUTH=OSAUTHDB o o 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 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 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 142 Installation Guide for SAP Solutions

151 Database Installation 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 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 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 (please refer to SAP note ). 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 Installation Guide for SAP Solutions 143

152 Database Installation Homogeneous federation for DB2 (DB2 V9.1 only) Performance Optimization ESE (DB2 V9.5 only) 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: 144 Installation Guide for SAP Solutions

153 Database Installation 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 = sapdb2eh 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 Installation Guide for SAP Solutions 145

154 Database Installation 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 To overcome this installation issue you have to modify FlexFrame' security options for period of the installation procedure. 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 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>) Configuration of FA Agents With FlexFrame 5.0 the DB2 support is part of the default installation of FA Agents. 146 Installation Guide for SAP Solutions

155 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 or SLES11 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> ln s Linux.SLES-9.x86_64 Linux.SLES-10.x86_64 /FlexFrame/volFF/pool-<pool>/sap/adaptive ln s Linux.SLES-9.x86_64 Linux.SLES-10.x86_64 /FlexFrame/volFF/pool-<pool>/sap/hostctrl ln s Linux.SLES-9.x86_64 Linux.SLES-10.x86_64 /FlexFrame/volFF/pool-<pool>/sapdb ln s Linux.SLES-9.x86_64 Linux.SLES-10.x86_64 /FlexFrame/volFF/pool-<pool>/db2 ln s Linux.SLES-9.x86_64 Linux.SLES-10.x86_64 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. Installation Guide for SAP Solutions 147

156 Image independent JAVA JDK 18 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 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 148 Installation Guide for SAP Solutions

157 Image independent JAVA JDK 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 (Option 1). applnode: su - <sid>adm applnode: cd /sapmnt/<sid>/profile applnode: # edit profiles as described in SAP Note , 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: su - <sid>adm 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 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 (Option 2). Before you start modifying it is recommended to stop the Java instance (JC) using ff_service.sh Java path settings for SDM If it needed to modify the JAVA path for SDM pelease follow the instructions made in SAP Note Installation Guide for SAP Solutions 149

158 Image independent JAVA JDK Additionally you have to modify JAVA property files. Please refer also to SAP Note 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: su - <sid>adm 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 behavior if there is a misconfiguration. If the services work well you reset the services to WATCH by ff_service.sh 150 Installation Guide for SAP Solutions

159 Post-SAP Installation Steps 19 Post-SAP Installation Steps Some parts are only valid for some SAP Releases and products. The example in chapter 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> 19.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: Virtual hostname: tom1bx1 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. Installation Guide for SAP Solutions 151

160 Post-SAP Installation Steps 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 152 Installation Guide for SAP Solutions

161 Post-SAP Installation Steps 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 Database Instance (also valid for WebAS 6.40 J2EE) Proceed with the following modifications: /oracle/<sid> After installation, rename the installed.*_<phys_hostname>.*sh to.*_db<sid>-se.*sh. Create a symbolic link from.*_db<sid>.*sh to.*_db<sid>-se.*sh. Installation Guide for SAP Solutions 153

162 Post-SAP Installation Steps Example: lrwxrwxrwx 1 oraq85 dba :30.dbenv_dbq85.csh ->.dbenv_dbq85-se.csh lrwxrwxrwx 1 oraq85 dba :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 Application Instance (not valid for WebAS 6.40 J2EE) Proceed with the following modifications: /home_sap/<sid>adm After installation, rename the installed.*_<phys_hostname>.*sh to.*_app<id><sid>.*sh. /sapmnt/<sid>/profile Change the profile names from *_<phys_hostname> to *_app<id><sid>. Set SAPLOCALHOST=app<id><sid> in every application instance profile. Change all host names (containing the physical host names) to app<sid> in the start profile. 154 Installation Guide for SAP Solutions

163 Post-SAP Installation Steps Additional Modifications for 4.6C SR2: /home_sap/<sid>adm Change the file names for start/stop to the new virtual host name app<id><sid>. /home_sap/<sid>adm In all files change the host name to app<id><sid>. /home_sap/<sid>adm Delete the following row in *.cshrc: Case Linux SCS Instance Proceed with the following modifications: /home_sap/<sid>adm After installation, rename the installed.*_<phys_hostname>.*sh to.*_scs<id><sid>.*sh. /sapmnt/<sid>/profile Change the profile names from *_<phys_hostname> to *_scs<id><sid>. Set SAPLOCALHOST=scs<id><sid> in every application instance profile. Change all host names (containing the physical host names) to scs<sid> in the start profile. Example: Instance Profile SID=LO7 Instance=68 SAPSYSTEMNAME = LO7 SAPSYSTEM = 68 INSTANCE_NAME = SCS68 DIR_CT_RUN = $(DIR_EXE_ROOT)/run DIR_EXECUTABLE = $(DIR_INSTANCE)/exe SAPLOCALHOST = scslo7 OS_UNICODE = uc # # SAP Messaging Service for Java # rdisp/msserv = 0 rdisp/msserv_internal = 3968 Installation Guide for SAP Solutions 155

164 Post-SAP Installation Steps 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 INSTANCE_NAME = SCS68 DIR_CT_RUN = $(DIR_EXE_ROOT)/run DIR_EXECUTABLE = $(DIR_INSTANCE)/exe SAPLOCALHOST = scslo7 DIR_PROFILE = $(DIR_INSTALL)/profile _PF = $(DIR_PROFILE)/LO7_SCS68_scslo7 SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH) SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH) SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH) # # Copy SAP Executables # _CPARG0 = list:$(dir_ct_run)/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 156 Installation Guide for SAP Solutions

165 Post-SAP Installation Steps ASCS Instance (WebAS 7.00) Proceed with the following modifications: /home_sap/<sid>adm After installation, rename the installed.*_<phys_ hostname>.*sh to.*_ascs<id><sid>.*sh. /sapmnt/<sid>/profile Change the profile names from *_<phys_hostname> to *_ascs<id><sid>. Set SAPLOCALHOST=ascs<id><sid> in every application instance profile. Change all host names (containing the physical host names) to ascs<sid> in the start profile. Example: Instance Profile SID=LO7 Instance=67 SAPSYSTEMNAME = LO7 SAPSYSTEM = 67 INSTANCE_NAME = ASCS67 DIR_CT_RUN = $(DIR_EXE_ROOT)/run DIR_EXECUTABLE = $(DIR_INSTANCE)/exe SAPLOCALHOST = ascslo7 # # SAP Messaging Service parameters are set in the DEFAULT.PFL # ms/standalone = 1 ms/server_port_0 = PROT=HTTP,PORT=81$$ # # SAP Locking Service # enque/table_size = 4096 rdisp/enqname = $(rdisp/myname) enque/snapshot_pck_ids = 100 Installation Guide for SAP Solutions 157

166 Post-SAP Installation Steps Example: Start Profile SAPSYSTEMNAME = LO7 SAPSYSTEM = 67 INSTANCE_NAME = ASCS67 DIR_CT_RUN = $(DIR_EXE_ROOT)/run DIR_EXECUTABLE = $(DIR_INSTANCE)/exe SAPLOCALHOST = ascslo7 DIR_PROFILE = $(DIR_INSTALL)/profile _PF = $(DIR_PROFILE)/LO7_ASCS67_ascslo7 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) # # 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_ascs67_ascslo7 # # 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_ascs67_ascslo 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 p11adm sapsys dbenv_dbp11.csh 158 Installation Guide for SAP Solutions

167 Post-SAP Installation Steps lrwxrwxrwx 1 p11adm sapsys dbenv_dbp11-se.csh ->.dbenv_dbp11.csh lrwxrwxrwx 1 p11adm sapsys dbenv_dbp11-se.sh ->.dbenv_dbp11.sh -rw-r p11adm sapsys dbenv_dbp11.sh -rw-r p11adm sapsys dbenv_j76p11.csh -rw-r p11adm sapsys dbenv_j76p11.sh -rw-r p11adm sapsys dbenv_jcp11.csh -rw-r p11adm sapsys dbenv_jcp11.sh -rw-r p11adm sapsys dbenv_scsp11.csh -rw-r p11adm sapsys dbenv_scsp11.sh -rw-r p11adm sapsys j2eeenv_j76p11.csh -rw-r p11adm sapsys j2eeenv_j76p11.sh -rw-r p11adm sapsys j2eeenv_jcp11.csh -rw-r p11adm sapsys j2eeenv_jcp11.sh -rw-r p11adm sapsys j2eeenv_scsp11.csh -rw-r p11adm sapsys j2eeenv_scsp11.sh lrwxrwxrwx 1 p11adm sapsys sapenv_dbp11.csh ->.sapenv_dbp11-se.csh -rw-r p11adm sapsys sapenv_dbp11-se.csh -rw-r p11adm sapsys sapenv_dbp11-se.sh lrwxrwxrwx 1 p11adm sapsys sapenv_dbp11.sh ->.sapenv_dbp11-se.sh -rw-r p11adm sapsys sapenv_j76p11.csh -rw-r p11adm sapsys sapenv_j76p11.sh -rw-r p11adm sapsys sapenv_jcp11.csh -rw-r p11adm sapsys sapenv_jcp11.sh -rw-r p11adm sapsys sapenv_scsp11.csh -rw-r p11adm sapsys sapenv_scsp11.sh -rw-r pl1adm sapsys sapsrc_j76p11.csh -rw-r pl1adm sapsys sapsrc_j76p11.sh -rw-r pl1adm sapsys sapsrc_jcp11.csh -rw-r pl1adm sapsys sapsrc_jcp11.sh -rw-r p11adm sapsys sapsrc_scsp11.csh -rw-r p11adm sapsys sapsrc_scsp11.sh 19.2 Configuring the Virtual Host Name for Web AS 6.40 ABAP and JAVA-AddIn / WebAS 6.40 JAVA Proceed with the following modifications: /home_sap/<sid>adm Installation Guide for SAP Solutions 159

168 Post-SAP Installation Steps 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. /sapmnt/<sid>/profile 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>. 160 Installation Guide for SAP Solutions

169 Post-SAP Installation Steps 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 Installation Guide for SAP Solutions 161

170 Post-SAP Installation Steps 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 INSTANCE_NAME = SCS68 DIR_EXECUTABLE = /usr/sap/os4/sys/exe/run DIR_LIBRARY = /usr/sap/os4/sys/exe/run # # Start SAP messaging service # _MS = ms.sapos4_scs68 Execute_00 = local rm -f $(_MS) Execute_01 = local ln -s -f $(DIR_EXECUTABLE)/msg_server $(_MS) Start_Program_00 = local $(_MS) pf=$(dir_profile)/os4_scs68_scsos4 # # Start SAP locking service # _EN = en.sapos4_scs68 Execute_02 = local rm -f $(_EN) Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/enserver $(_EN) Start_Program_01 = local $(_EN) pf=$(dir_profile)/os4_scs68_scsos4 162 Installation Guide for SAP Solutions

171 Post-SAP Installation Steps Instance Profile (e.g. OS4_SCS68_scsos4): bash-2.03# cat OS4_SCS68_scsos4 SAPSYSTEMNAME = OS4 SAPLOCALHOST = scsos4 SAPLOCALHOSTFULL = scsos4 INSTANCE_NAME = SCS68 SAPSYSTEM = 68 DIR_GLOBAL = /sapmnt/os4/global DIR_PROFILE = /sapmnt/os4/profile DIR_EXECUTABLE = /usr/sap/os4/sys/exe/run rdisp/msserv = 3668 enque/table_size = 4096 enque/deque_wait_answer = FALSE enque/process_location = LOCAL enque/encni/port = 3268 rdisp/enqname = $(rdisp/myname) enque/snapshot_pck_ids = 100 ms/server_port_0 = PROT=HTTP, PORT=8168 Adapt the J2EE Configuration Tool For WebAS 6.40 ABAP + Java-AddIn, use the host name ci<sid> and jc<sid> for WebAS 6.40 JAVA. The example below uses WebAS 6.40 ABAP + JAVA-AddIn (SID=OS4) 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 Installation Guide for SAP Solutions 163

172 Post-SAP Installation Steps 164 Installation Guide for SAP Solutions

173 Post-SAP Installation Steps Installation Guide for SAP Solutions 165

174 Post-SAP Installation Steps 166 Installation Guide for SAP Solutions

175 Post-SAP Installation Steps to change: profile name + host Type in Value: <Custom value> for each line and click on Set. Installation Guide for SAP Solutions 167

176 Post-SAP Installation Steps 168 Installation Guide for SAP Solutions

177 Post-SAP Installation Steps to change: profile name + host Check the host name of the SCS for all installed instances Recommendation: If you plan to install several DI Instances, finish the virtualization step of the ABAP + JAVA-AddIn Instances. During the installation step you ll be asked for names of the DB and CI, type in the virtual hostnames. Installation Guide for SAP Solutions 169

178 Post-SAP Installation Steps 170 Installation Guide for SAP Solutions

179 Post-SAP Installation Steps Installation Guide for SAP Solutions 171

180 Post-SAP Installation Steps 172 Installation Guide for SAP Solutions

181 Post-SAP Installation Steps 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 Installation Guide for SAP Solutions 173

182 Post-SAP Installation Steps doubleclick Click on the edit icon. A Switch to Edit mode warning opens. Click on Yes and afterwards double-click the Propertysheet instance. 174 Installation Guide for SAP Solutions

183 Post-SAP Installation Steps Click on OK and exit. Installation Guide for SAP Solutions 175

184 Post-SAP Installation Steps 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. 176 Installation Guide for SAP Solutions

185 Post-SAP Installation Steps 19.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 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 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. Installation Guide for SAP Solutions 177

186 Post-SAP Installation Steps SSH Configuration: The host the job is running on must have permission to start programs on the remote host. Baby_1:oacadm 60% ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/home_sap/oacadm/.ssh/id_rsa): Created directory /home_sap/oacadm/.ssh Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home_sap/oacadm/.ssh/id_rsa.pub. Your public key has been saved in /home_sap/oacadm/.ssh/id_rsa.pub. The key fingerprint is: ea:46:0a:17:e5:e9:39:54:c9:e8:10:b0:d6:84:c3:ce 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 19.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 178 Installation Guide for SAP Solutions

187 Post-SAP Installation Steps 19.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_cio 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: ABAP central services instance: Application instance: ci<sid> ascs<sid> app<id><sid> Syntax for the host name (JAVA) Java Control instance: SAP common services: Java application instance: jc<sid> scs<sid> j<id><sid> Installation Guide for SAP Solutions 179

188 Post-SAP Installation Steps 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 : 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 = rdisp/pg_shm = 0 rdisp/pg_maxfs = 2048 ztta/roll_first = 1024 ztta/roll_area = 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. 180 Installation Guide for SAP Solutions

189 Post-SAP Installation Steps 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` # #unset list #set list=`$lscommand $HOME grep '^startsap_'${hostname}'_[0-9] [0-9]$'` #if ( `echo $list wc -w` == 1 ) then # alias startsap $HOME/$list #else # alias startsap "echo 'To start an instance use one of the following scripts: #endif # #unset list #set list=`$lscommand $HOME grep '^stopsap_'${hostname}'_[0-9][0-9]$'` #if ( `echo $list wc -w` == 1 ) then # alias stopsap $HOME/$list #else # alias stopsap "echo 'To stop an instance use one of the following scripts:'; #endif # # end SAP R/3 Environment Place the startsap and stopsap scripts of release 6.x in the /sapmnt/<sid>/exe directory. Make sure that all the permissions of the SAP kernel in this directory are set to <sid>adm:sapsys. After changing the rights with chown <sid>adm:sapsys_*, start the saproot.sh <sid> script. The new scripts should look like this: #!/bin/sh # # Installation Guide for SAP Solutions 181

190 Post-SAP Installation Steps # 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 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 and for details on this matter 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. 182 Installation Guide for SAP Solutions

191 Post-SAP Installation Steps Example of CB1 with two Application Instances and a Logon Group. Logon group PUBLIC. Installation Guide for SAP Solutions 183

192 Post-SAP Installation Steps Enter the virtual IP address of the Client LAN SAPROUTER on the Control Node 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> 184 Installation Guide for SAP Solutions

193 Post-SAP Installation Steps 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 Configuration File saprouter The saprouter (/FlexFrame/volFF/FlexFrame/saprouter) routes the nodes from the workstation network * to the Client LAN of the virtual SAP services: /FlexFrame/volFF/FlexFrame/saprouter/saprouttab # # from to service # # workstation-lan client-lan P * * * 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 cibw cicb app01cb app02cb1 Services in LDAP sapdp /tcp # SAP System Dispatcher Port sapdp /tcp # SAP System Dispatcher Port sapmscb1 3600/tcp # SAP System Message Port sapdp /tcp # SAP System Dispatcher Port Installation Guide for SAP Solutions 185

194

195 SAP System Administration 20 SAP System Administration 20.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 Software Administration 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 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. Installation Guide for SAP Solutions 187

196 SAP System Administration 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 stop_all_sapservices stop_all_sapservices_sid Initial start of all configured applications Stopping of all active applications Stopping of all active applications of one SID stop_all_sapservices_local Stopping of all active applications on the local node Only on a Control Node Only on a Control Node Only on a Control 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 Application Software Please refer to the standard documents for SAP Services (R/3, BW, CRM, etc.) The virtual host name always has to be used for administering and configuring spool servers, batch servers, RFC connections, etc SAP Release Upgrade Services Port If you plan an SAP Release upgrade, you have to add a special service port (called shadow instance) to LDAP. 188 Installation Guide for SAP Solutions

197 SAP System Administration Please use the ff_sap_shadowport.sh script. If you issue the script the usage will be shown 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. Installation Guide for SAP Solutions 189