Preview only show first 10 pages with watermark. For full document please download

Installation Guide For Sap Solutions

Rating
Date

November 2018
Size

4.4MB
Views

8,852
Categories

Computers & electronics Software Computer utilities Database software

Transcript

FlexFrame™ for SAP® Version 5.1A Installation Guide for SAP Solutions Edition January 2013 Document Version 1.7 Fujitsu Limited © Copyright Fujitsu Technology Solutions 2011 FlexFrame™ and PRIMERGY™ are trademarks or registered trademarks of Fujitsu Limited in Japan and other countries. SAP® and NetWeaver™ are trademarks or registered trademarks of SAP AG in Germany and in several other countries Linux® is a registered trademark of Linus Torvalds SUSE® Linux is a registered trademark of Novell, Inc., in the United States and other countries Oracle™ and Java™ are trademarks of ORACLE Corporation and/or its affiliates Intel® and PXE® are registered trademarks of Intel Corporation in the United States and other countries MaxDB® is a registered trademark of MySQL AB, Sweden MySQL® is a registered trademark of MySQL AB, Sweden NetApp® and the Network Appliance® logo are registered trademarks and Network Appliance™ and Data ONTAP™ are trademarks of NetApp, Inc. in the U.S. and other countries. EMC®, CLARiiON®, Symmetrix® and Celerra™ are trademarks or registered trademarks of EMC Corporation in the United States and other countries VMware®, ESX®, ESXi, VMware vCenter, VMware vSphere are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Ethernet® is a registered trademark of XEROX, Inc., Digital Equipment Corporation and Intel Corporation Windows® and Word® are registered trademarks of Microsoft Corporation All other hardware and software names used are trademarks of their respective companies. All rights, including rights of translation, reproduction by printing, copying or similar methods, in part or in whole, are reserved. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Delivery subject to availability. Right of technical modification reserved. Contents Contents 1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 Introduction ..................................................................................................... 1 Purpose of this Document ................................................................................. 1 General Usage of SAP Installation Guide During Installation ............................ 1 Special Hints for FlexFrame .............................................................................. 1 Overview ........................................................................................................... 2 Notational Conventions ..................................................................................... 2 Document History .............................................................................................. 2 Related Documents ........................................................................................... 4 Hotlinks for FlexFrame ...................................................................................... 4 2 2.1 2.2 2.3 2.4 2.5 Getting Started ................................................................................................ 7 FlexFrame ......................................................................................................... 7 Virtualization of SAP Services ........................................................................... 8 Preparations ...................................................................................................... 8 Gathering SAP Services Information ................................................................. 8 Supported Hardware for Application Nodes ...................................................... 9 3 3.1 3.2 3.3 SAP Service Connection............................................................................... 11 OSS Network Connection with Dedicated saprouter Server ........................... 11 OSS Network Connection without Dedicated saprouter Server....................... 12 Related SAP Notes ......................................................................................... 13 4 FA Agents ...................................................................................................... 15 5 5.1 5.2 5.3 5.4 SAP Service Scripts for Virtualizing Applications ...................................... 17 Starting a Configuration ................................................................................... 17 Configuring the Service Status Path ................................................................ 19 Configuring the Interfaces ............................................................................... 21 Host Names..................................................................................................... 22 6 6.1 Operating System in General ....................................................................... 25 Linux................................................................................................................ 25 7 7.1 7.1.1 7.1.2 7.2 7.2.1 7.2.2 Preparations for Database Installation ........................................................ 27 SAP Installation with Database DB2 ............................................................... 27 Software Requirements ................................................................................... 27 Pre-Installation Steps ...................................................................................... 28 Mount Options ................................................................................................. 28 Database files (sapdata, saplog) ..................................................................... 29 Binaries and Configuration files ....................................................................... 29 Installation Guide for SAP Solutions Contents 8 8.1 8.2 8.3 8.4 8.5 8.5.1 8.5.2 8.5.3 8.5.4 8.6 8.7 Preparations for SAP Installation ................................................................. 31 General ............................................................................................................ 31 How to configure the interfaces manually ........................................................ 33 ASCS ABAP Central Service Instance in General ........................................... 33 SAP Java Cryptographic Toolkit ...................................................................... 34 Setting up SAP directories (Control Center) .................................................... 34 Standard Volumes ........................................................................................... 34 Specify volumes of your own ........................................................................... 35 SID/Poolspecific volumes ................................................................................ 35 Using SAN ....................................................................................................... 35 Usage of /dev/urandom ................................................................................... 36 Predefined global users ................................................................................... 37 9 SAP Installation - Overview .......................................................................... 38 10 10.1 10.1.1 Installing SAP 4.6C SR2 ................................................................................ 41 SAPDB / MaxDB / Oracle ................................................................................ 42 Installing the Central Instance (CI) .................................................................. 46 11 11.1 11.2 11.2.1 11.2.2 11.2.3 11.2.4 11.2.5 11.2.6 11.2.7 11.3 11.3.1 11.3.2 11.3.3 11.4 Installing Web AS 6.40 with NetWeaver04 SR1 ........................................... 49 Description of Web AS 6.40 JAVA ................................................................... 52 Web AS 6.40 NetWeaver04SR1 JAVA MaxDB/Oracle ................................... 53 SCS ................................................................................................................. 53 DB ................................................................................................................... 57 JC .................................................................................................................... 58 J ....................................................................................................................... 58 CI ..................................................................................................................... 59 DB ................................................................................................................... 62 APP ................................................................................................................. 62 Web AS 6.40 ABAP + JAVA-AddIn NetWeaver04SR1.................................... 62 SCS ................................................................................................................. 62 DB ................................................................................................................... 63 CI ..................................................................................................................... 63 Web AS 6.40 Application Server JAVA-AddIn ................................................. 67 12 12.1 12.1.1 12.2 12.3 12.4 12.5 12.6 12.7 Installing NetWeaver 7.0SR3 ........................................................................ 69 Installation of SAP Solutions............................................................................ 71 Prerequisite Checker (Linux) ........................................................................... 72 Sapinit File (Linux) ........................................................................................... 73 installsapinit.sh – symlink (Linux) .................................................................... 74 Services File (Linux) ........................................................................................ 75 NetWeaver 7.0SR3 and Oracle 10 .................................................................. 76 NetWeaver 7.0SR3 and MaxDB76 .................................................................. 77 NetWeaver 7.0SR3 MaxDB76 and SLES9_x86/SLES10_x86 ........................ 79 Installation Guide for SAP Solutions Contents 12.8 12.9 12.10 12.11 12.12 12.13 12.13.1 12.13.2 12.14 12.15 12.16 NetWeaver 7.0SR3 MaxDB76 ......................................................................... 80 NetWeaver 7.0SR3 and EP ............................................................................. 81 NetWeaver 7.0SR3 ABAP+JAVA-AddIn ......................................................... 83 NetWeaver 7.0SR3 JAVA only ........................................................................ 88 NetWeaver 7.01/SLES 9 ................................................................................. 88 SAP 7.0 EHP3 ................................................................................................. 89 Installation Media Label is wrong .................................................................... 89 Incompatibilities with Linux Kernel................................................................... 89 LiveCache ....................................................................................................... 89 ERS – Enqueue Replicated Server (until NetWeaver 2004s SR3) .................. 89 Installation of SAP Solutions – Post Phase ..................................................... 91 13 13.1 13.2 13.3 13.3.1 13.3.2 13.3.3 13.4 13.4.1 13.4.2 Installing SAP 7.1 .......................................................................................... 92 Creating a New SID Using ff_sid_adm.pl ........................................................ 92 Service Cannot Be Started .............................................................................. 93 EHP Installer Issues ........................................................................................ 94 Mandatory SMD installation request ................................................................ 94 EHP Installer Requests Entries in /etc/services............................................... 95 EHP Installer – JAVA process cannot be started ............................................ 95 ERS ................................................................................................................. 99 Installation hints............................................................................................... 99 Post Installation Tasks (SAP 7.1 only) .......................................................... 102 14 14.1 14.2 14.2.1 14.3 14.3.1 14.3.2 14.4 14.5 Installing SAP 7.3 ........................................................................................ 103 Creating a New SID Using ff_sid_adm.pl ...................................................... 104 SCS/ASCS (SAP 7.3) .................................................................................... 104 Installation hints............................................................................................. 104 ERS ............................................................................................................... 106 Installation hints............................................................................................. 106 Post Installation Tasks .................................................................................. 109 SAP 7.3 EHP1 ............................................................................................... 109 SAP 7.3 – Linux kernel issue......................................................................... 110 15 15.1 15.1.1 15.1.2 15.1.3 15.1.4 15.1.5 15.2 15.2.1 15.2.2 15.2.3 15.2.4 Install nonclassic SAP services ................................................................. 111 BOBJ – Business Objects Enterprise ............................................................ 111 BOBJ – preparations ..................................................................................... 112 BOBJ – installation – 3.x ............................................................................... 112 BOBJ – Installation – 4.0 ............................................................................... 113 BOBJ – post installation ................................................................................ 114 BOBJ – Login to CMC (Central Management Console) ................................ 114 CMS – Content Server .................................................................................. 115 CMS – preparations ...................................................................................... 116 CMS – http server installation........................................................................ 116 CMS – installation ......................................................................................... 116 CMS – post installation .................................................................................. 117 Installation Guide for SAP Solutions Contents 15.2.5 15.3 15.3.1 15.3.2 15.3.2.1 15.3.2.2 15.3.2.3 15.3.3 15.3.4 15.3.5 15.4 15.4.1 15.5 15.5.1 15.5.2 15.5.3 15.5.4 15.5.5 CMS - Migration from project specific solutions ............................................ 117 MDM – Master Data Management................................................................. 118 MDM – preparations ...................................................................................... 118 MDM – Database installation ......................................................................... 119 Oracle ............................................................................................................ 119 MaxDB ........................................................................................................... 120 DB2 ............................................................................................................... 121 MDM – installation ......................................................................................... 121 MDM – post installation ................................................................................. 122 MDM - Migration from project specific solutions ........................................... 122 SMD – Solution Manager Diagnostics ........................................................... 123 SMD - Migration from project specific solutions ............................................ 123 TREX – Search and Classification................................................................. 124 TREX – preparations ..................................................................................... 124 TREX – installation ........................................................................................ 125 TREX – post installation ................................................................................ 125 TREX – trouble shooting................................................................................ 126 TREX - Migration from project specific solutions .......................................... 126 16 16.1 16.2 16.2.1 16.3 16.3.1 16.4 16.4.1 16.4.2 16.4.3 16.4.4 16.5 16.6 16.6.1 16.6.1.1 16.6.2 16.6.3 16.6.4 16.6.5 16.6.6 16.6.6.1 16.6.7 16.6.8 16.6.9 16.6.10 16.7 Database Installation ................................................................................... 128 Installation of Oracle in General .................................................................... 129 Installation of Oracle 9.2 ................................................................................ 130 Post-Oracle 9.2 Installation Steps ................................................................. 130 Installation of Oracle 10.2 .............................................................................. 132 Post-Oracle 10.2 Installation Steps ............................................................... 132 Oracle – general post installation steps ......................................................... 133 TNS Listener for Oracle ................................................................................. 133 listener.ora ..................................................................................................... 134 Host Name Changes in tnsnames.ora ........................................................... 135 Host specific /etc/oratab ................................................................................ 135 Oracle Patch Installation ................................................................................ 136 Installation of SAPDB / MaxDB ...................................................................... 136 XUSER .......................................................................................................... 137 Same SID on Different Platforms ................................................................... 138 MaxDB 7.5/7.6/7.7 /etc/opt/sdb ..................................................................... 139 MaxDB 7.6 ..................................................................................................... 140 MaxDB 7.7 ..................................................................................................... 141 MaxDB 7.8 ..................................................................................................... 142 MaxDB 7.9 ..................................................................................................... 142 MaxDB 7.9 (upgrade) - /etc/opt/sdb............................................................... 144 IO Balancing .................................................................................................. 144 MaxDB configuration files .............................................................................. 144 Directories for sapdata / saplog ..................................................................... 145 MaxDB 7.8/7.9 – performance issue ............................................................. 145 SAP Installation with Database DB2 .............................................................. 147 Installation Guide for SAP Solutions Contents 16.7.1 16.7.2 16.7.3 16.7.4 16.7.5 16.7.6 16.7.6.1 16.7.6.2 16.7.6.3 16.7.6.4 16.7.7 Installing DB2 ................................................................................................ 147 LDAP-Plugin .................................................................................................. 148 Transparent LDAP......................................................................................... 149 Install SAP ..................................................................................................... 150 Changes in System Files ............................................................................... 150 Post Installation Steps ................................................................................... 150 Installing DB2 License ................................................................................... 150 Modifying DB2 Catalog .................................................................................. 152 Preparations for backing up DB2 ................................................................... 153 DB2-Fixpack issues ....................................................................................... 154 Configuration of FA Agents ........................................................................... 154 17 Migration – SLES9 to SLES10 / SLES11 .................................................... 155 18 Post-SAP Installation Steps ....................................................................... 157 18.1 Configuring the Virtual Host Name Manually ................................................. 157 18.1.1 Central Instance (not valid for Web AS 6.40 J2EE) ....................................... 159 18.1.2 Database Instance (also valid for WebAS 6.40 J2EE) .................................. 159 18.1.3 Application Instance (not valid for WebAS 6.40 J2EE) .................................. 160 18.1.4 SCS Instance ................................................................................................ 161 18.1.5 ASCS Instance (WebAS 7.00)....................................................................... 163 18.1.6 NetWeaver 7.0 / NetWeaver 7.0SR1/SR2 ..................................................... 164 18.2 Configuring the Virtual Host Name for Web AS 6.40 ABAP and JAVA-AddIn / WebAS 6.40 JAVA ......................................................................................................... 165 18.3 Start Script startdb for Oracle and SAPDB/MaxDB/DB2 ............................... 183 18.4 Stop Script stopdb for Oracle and SAPDB/MaxDB/DB2 ................................ 183 18.5 Scheduling of Batch Jobs (CCMS) ................................................................ 183 18.6 Profile Parameters for DEFAULT.PFL ........................................................... 184 18.7 Profile Parameters for the Start Profile .......................................................... 185 18.8 Profile Parameters for the Instance Profile .................................................... 185 18.9 SAP Start and Stop Mechanism (Release 4.6CSR2) .................................... 186 18.10 SAP License .................................................................................................. 188 18.11 SAPLogon – SAPGUI.................................................................................... 188 18.12 SAPROUTER on the Control Node ............................................................... 190 18.12.1 Configuration File for /etc/init.d/saprouter ...................................................... 190 18.12.2 Configuration File saprouter .......................................................................... 191 19 19.1 19.2 19.3 19.4 Image independent JAVA JDK ................................................................... 192 File structures and profiles ............................................................................ 192 Java Configuration Tool ................................................................................ 193 Java path settings for SDM ........................................................................... 193 Restart the services with new JAVA path ...................................................... 194 20 Usage of SAP JVM ...................................................................................... 195 Installation Guide for SAP Solutions Contents 21 21.1 21.2 21.2.1 21.2.1.1 21.2.2 21.3 21.3.1 21.3.2 21.4 21.5 21.5.1 21.5.2 21.5.3 21.5.3.1 21.5.3.2 21.5.3.3 21.5.4 SAP System Administration ....................................................................... 197 Upgrading Application Software .................................................................... 197 Software Administration ................................................................................. 197 Starting and Stopping SAP Services ............................................................. 197 SAP Service Scripts ...................................................................................... 197 Application Software ...................................................................................... 198 SAP Release Upgrade .................................................................................. 198 Services Port ................................................................................................. 198 Instance profile .............................................................................................. 199 Transport Directory ........................................................................................ 200 Printing in FlexFrame .................................................................................... 200 Possible Printing Architectures and Methods ................................................ 200 Local Printing (Access Methods C and L) ...................................................... 200 Remote Printing (Access Methods S and U) ................................................. 201 Architecture Prerequisites.............................................................................. 201 SAP System Prerequisites............................................................................. 201 Description..................................................................................................... 202 Front-end Printing on Local Printers .............................................................. 203 22 22.1 22.2 BRBACKUP and SAPDBA/BRCONNECT ................................................... 205 Solution 1 for Oracle and SAPDB/MaxDB ..................................................... 205 Solution 2 for Oracle ...................................................................................... 206 23 Troubleshooting .......................................................................................... 207 24 Abbreviations ............................................................................................... 213 25 Glossary ....................................................................................................... 217 26 Index ............................................................................................................. 223 Installation Guide for SAP Solutions 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 http://manuals.ts.fujitsu.com/index.php?id=9215-9217 Please make sure that you get the latest version before starting an installation, and always read the latest README file that contains further changes and fixes. 1.1 Purpose of this Document ® This document provides brief instructions for installing SAP with Oracle®, or SAPDB / MaxDB™ or DB2™ in a FlexFrame™ environment. It is absolutely essential to use the SAP Installation Guides and the latest SAP Notes for the SAP solution that is to be installed. It is intended for certified FlexFrame consultants only; sound knowledge of FlexFrame technology and its background is required. 1.2 General Usage of SAP Installation Guide During Installation Please note that the entire documentation about installing SAP within a FlexFrame environment is not intended as a stand-alone documentation. It solely describes the differences to a standard SAP installation as described by SAP. 1.3 Special Hints for FlexFrame In this document, you often will find console output, configuration data and installation examples which are based on earlier FlexFrame versions. Please keep in mind that these are examples and may look slightly different on the new operating systems introduced in FlexFrame 4.2A. The two Control Nodes (CN) of FlexFrame for SAP are also named as the FlexFrame Control Center (CC). In this documentation the notation Control Node (CN) is used as a synonym for Control Center (CC) and the other way round. Installation Guide for SAP Solutions 1 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 Names of paths, files, commands, and system output. Names of variables fixed font User input in command examples (if applicable using <> with variables) 1.6 Document History Document Version Changes Date 1.0 First Edition 2011-11-23 1.1 Support of SAP JVM Support BOBJ 4.0 MaxDB installation hints 2011-11-30 1.2 Transparent LDAP 2012-03-15 1.3 Support maxDB 7.9 2012-05-14 2 Installation Guide for SAP Solutions Introduction 1.4 Installation hints: SAP 7.0 EHP3, 7.3 EHP1 Global user list 2012-08-08 1.5 Performance issue MaxDB 7.8/7.9 2012-10-09 1.6 Troubleshooting (no CI/JC) 2012-11-08 1.7 Wrong command syntax (SAP 7.3 EHP1) 2013-01-12 Installation Guide for SAP Solutions 3 Introduction 1.7 Related Documents ® FlexFrame™ for SAP – Administration and Operation ® FlexFrame™ for SAP – HW Characteristics Quickguides ® FlexFrame™ for SAP – Installation ACC 7.3 ® FlexFrame™ for SAP – Installation Guide for SAP Solutions ® FlexFrame™ for SAP – Installation of a FlexFrame Environment ® FlexFrame™ for SAP – Management Tool ® 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.2B or 5.0A to 5.1A ServerView Documentation SUSE Linux Enterprise Server Documentation 1.8 Hotlinks for FlexFrame Global information on FlexFrame FlexFrame for SAP manuals http://manuals.ts.fujitsu.com/index.php?id=9215-9217 Official FlexFrame home page http://www.ts.fujitsu.com/flexframe Dynamic Infrastructures and FlexFrame for SAP https://partners.ts.fujitsu.com/com/products/infrastruc-solutions/FlexFrame Service Partner Portal for FlexFrame for SAP https://partners.ts.fujitsu.com/com/service/software/flexframe SAP NetWeaver™ http://www.sap.com/solutions/netweaver/ Fujitsu and SAP https://partners.ts.fujitsu.com/com/partners/strategic_partners/sap FlexFrame for SAP on Linux® 4 Installation Guide for SAP Solutions Introduction Global information on FlexFrame SAP on Linux (released kernels, hardware and distributions for SAP) http://www.sap.com/linux PRIMERGY™ manuals http://manuals.ts.fujitsu.com/index.php?id=5406 PRIMERGY Information Center https://partners.ts.fujitsu.com/com/products/servers/primergy Knowledge Documentation on ServerView Suite http://manuals.ts.fujitsu.com/index.php?id=5406-5873-5925 Software Software by Fujitsu http://support.ts.fujitsu.com/DE/support/downloads.html Installation Guide for SAP Solutions 5 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 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. 8 Installation Guide for SAP Solutions Getting Started You will be asked for the following details: SID Select pool (dropdown list) Select DB type (dropdown list) Select SAP version (dropdown list) Select the instances needed If you want to install a SAP component like CRM or R/3 (ERP), you won‘t find it in the dropdown list of the SAP versions. You have to enter the underlying SAP Basis (Web AS) release which must be one of the four listed versions. If you need another Basis release or another DB type for your SAP component, please ask our SAP Competence Center for project-specific support. Please make sure to have the latest version before starting an installation, and always read the latest README file that contains further changes and fixes. After all information for the complete SAP Services landscape has been entered in the tool you will get a XML file which has to be moved to the Control Node. Please refer to the corresponding manual to setup your FlexFrame system using the XML configuration file. 2.5 Supported Hardware for Application Nodes A subset of SAP-certified, Intel®//AMD®-based servers from Fujitsu is supported. Please refer to: https://www.sdn.sap.com/irj/sdn/linux and move to ―Supported Platforms – Supported Hardware‖ and select ―Fujitsu‖ Please check that list against the Support Matrix provided with FlexFrame. Installation Guide for SAP Solutions 9 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: Customer SAP Walldorf Tokio Foster City TELNET SAPGUI Gateway TELNET SAPGUI SAPROUTER Control Node 1 TELNET SAPGUI SSH SSH Application Node 1 Control Node 2 TELNET SAPGUI SSH 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 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 190). In this case, a virtual IP address for the Client LAN has to be defined for the saprouter service and for every pool, and the Linux-HA cluster has to be configured accordingly. To allow the Linux-HA cluster to control the saprouter service, it is necessary to get the latest version of saprouter from SAP (Service Marketplace) and to install it in the directory /FlexFrame/volFF/FlexFrame/saprouter on the active Control Node. This directory has to be created, the saprouter program copied to it and saprouttab created within this directory. The Linux-HA cluster should be reconfigured using the saprouter user templates. To add the saprouter application to the cluster configuration, call: cn1:~ # ff_ha_tool.sh –a saprouter For each virtual IP address, call: cn1:~ # ff_ha_tool.sh –a saprouterip ip=a.b.c.d Where a.b.c.d is the virtual IPv4 address for the saprouter service. It is necessary that a fixed IPv4 address of the same subnet is already configured in the operation system (which is usually the case for the Client-LAN), otherwise the resource script will not be able to detect the correct interface. The saprouter service and the IP address will be started immediately after being added to the cluster configuration. This can be verified by executing: cn1:~ # crm_mon -1 –r If the saprouter is configured to explicitely listen on the virtual ip addresses, it might be necessary to add the ip resources before adding the saprouter itself, otherwise the saprouter may not be able to start and result in a failed state of the resource which has to be cleaned up then. Adding more virtual addresses is possible at any time by adding a new saprouterip configuration template. Removing ip addresses is possible by executing: cn1:~ # ff_ha_tool.sh –d saprouterip ip=a.b.c.d 12 Installation Guide for SAP Solutions 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! Customer SAP Walldorf Tokio Foster City TELNET SAPGUI Gateway TELNET SAPGUI Control Node 1 (saprouter) Control Node 2 (saprouter) 3.3 SAPGUI SSH Application Node 1 SAPGUI SSH Application Node 2 SAPGUI SSH Application Node ... SAPGUI SSH Application Node n Related SAP Notes A table of related SAP Notes is provided below: SAP OSS note number Title 35010 Service connections: Composite note (overview) 37001 Telnet link to customer systems Installation Guide for SAP Solutions 13 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 SAP Service Scripts for Virtualizing Applications 5 SAP Service Scripts for Virtualizing Applications Scripts for starting, stopping and restarting the applications and services are provided by SAP. With FlexFrame 5.0 the interface to start and stop SAP services were changed. The following scripts are installed: Script name Application ff_service.sh Central Script to start, stop, etc a SAP service ff_service_functions Function library for ff_service.sh ff_sapdb_functions Function library for ff_service.sh (databases) ff_sapclassic_functions Function library for ff_service.sh (classic services) ff_sapnonclassic_functions Function library for ff_service.sh (new services, e.g. CMS) ff_service.config Configration file of ff_Service.sh sapservice_config Global customer-specific parameters sapservice_functions Global parameters and functions; still available because of compatibility reasons start_all_sapservices Initial start of all configured applications stop_all_sapservices Stops all running applications stop_all_sapservices_local Stops all running applications on the local node stop_all_sapservices_SID 5.1 Stops all running applications of one SID Starting a Configuration The start_all_sapservices start script defines which applications are to be started in which sequence and on which virtual host. The script is executed on a Control Node. The script below illustrates its syntax: #!/bin/bash Installation Guide for SAP Solutions 17 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 ssh applnode1 ssh applnode2 ssh applnode3 " & ff_service.sh ff_service.sh ff_service.sh ff_service.sh –t –t –t –t db ci db db –s –s –s –s C11 C11 C11 C11 –a –a –i –i start start 01 –a start 02 –a start #echo "" #echo "All services should be up now." #----------------------------------------------------------------- The start sequence within a system ID must always be followed: ABAP ABAP + ASCS ABAP + JAVA-AddIn JAVA ABAP + ASCS + JAVA-AddIn 1. DB 1. DB 1. DB 1. DB 1. DB 2. CI 1. ASCS 1. SCS 1. SCS 1. ASCS 3. APP 2. CI 2. CI 2. JC 1. SCS 3. APP 2. APP 2. J 2. CI 3. APP Equal numbers mean that the features can be started in parallel. The figure below shows the dependencies of the SAP Services (x  y means ―x is dependent on y‖). 18 Installation Guide for SAP Solutions 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 00-97 sid is the lower-case three-digit system ID Installation Guide for SAP Solutions 19 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: __host For the service type app: app___host Web AS 6.40 with JAVA/J2EE Engine and/or ABAP Engine There are additional service types when you run a J2EE engine based on WebAS 6.40. For the service types scs and jc: __host For the service type j: j___host The content of the service control file is the name of the node the application or service is running on. Web AS 7.00 with JAVA/J2EE Engine and/or ABAP/ASCS Engine There are additional service types when you run a J2EE engine based on WebAS 7.00. For the service types scs, ascs and jc: __host For the service type j: j___host WebAS 7.0 with JAVA/J2EE Engine and/or ABAP/ASCS Engine and ERS There are optional service types bound on WebAS 7.00. For the service types scs and ascs: sapers___host WebAS 7.0 with ABAP and MaxDB (LiveCache) There is a additional service type which supports LiveCache. Service type: lc__host SAP 7.1 with JAVA The naming for the former service type jc has been changed: Service type: j___host 20 Installation Guide for SAP Solutions 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=‖255.255.240.0 ls3195:255.255.255.0‖ NETMASK_CLIENT=‖255.255.255.0‖ NETMASK_SERVER=‖255.255.255.0‖ # # Interface # #----------------------------------------------------------------# SunOS link aggregation # ~~~~~~~~~~~~~~~~~~~~~~~ # # real interfaces look like this: # fjgi2005000 # this is the first interface # fjgi2005001 # this is the second interface # fjgi2005000:1 # this indicates that the first interface # # is active # fjgi2005001:1 # this indicates that the second interface # # is active # # These interface names consist of three parts: # fjgi2005001:1 # ^^^----------- interface number # ^^^^-------------- vlan # ^^^^------------------ 1GB-model # # For our network to interface relation we use only the first two # parts of the interface names, the model and the vlan. In our # example: # fjgi2005 # #----------------------------------------------------------------# # Recommendations: # Installation Guide for SAP Solutions 21 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 Client LAN db-se lc-se ci-se ci ascs-se ascs app-se app scs-se scs jc-se (SAP 7.1: j-se) jc (SAP 7.1: j) ers-se ers j-se j N/A bobj 22 Installation Guide for SAP Solutions SAP Service Scripts for Virtualizing Applications Server LAN Client LAN N/A cms mds-se mds mdss-se mdss mdis-se mdis N/A trx-se trx Explanation: id Consecutive two-digit number 00-97 sid The lower-case three-digit system ID In FlexFrame the following rules have to be regarded to define host names: 1. The host name in the Storage LAN is built using the host name and adding -st. 2. The host name in the Server LAN is built using the host name and adding -se. 3. The host name in the Control LAN is built using the host name and adding -co. 4. The host name in the Client LAN is built using the host name without an extension. 5. Host names are written in lower case exclusively. 6. Host names are supposed not to be longer than 13 characters. With SAP 7.1 the host names for the previous JAVA central Instance jc have been changed from jc-se to j-se (Server LAN) and jc to j (Client LAN). Installation Guide for SAP Solutions 23 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=. General hints about setting up Linux on Application Nodes you can find at Linux (see chapter 6.1). 6.1 Linux Relevant SAP Note for installation on Linux If you want to install an SAP R/3 system on Linux, refer to SAP Note 171356. SAP advice to use the most recent kernel Please be advised to use one of the most recent 2.6 kernels for your hardware platform and distribution. In case of problems with the operating system, please try to reproduce it on a tested kernel and contact the support organization of your Linux distributor if the problem persists. (www.sap.com/linux/platforms) Setup User Environment In the next step you set your user environment as requested. Either you set the environment directly or you insert the definitions to the OS-specific user profile (e.g. .bashrc with Linux). server:/ # export JAVA_HOME= 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=// server:/ # export TMP= Installation Guide for SAP Solutions 25 Preparations for Database Installation 7 Preparations for Database Installation Installation of Oracle N/A Installation of MaxDB N/A Installation of DB2 All platforms (see chapter 7.1) software requirements pre-installation steps 7.1 SAP Installation with Database DB2 With the current release of FlexFrame we support DB2 database also with the Management Tool. 7.1.1 Software Requirements To run DB database within a SAP system you need at least the software shown below: FlexFrame for SAP, 5.0A FlexFrame Autonomous Agents, V30K15 up SAP NetWeaver 2004s (SR1/SR2) or SAP 7.0 SR3 R/3 4.7x200 with kernel release 640, Patch 189 R/3 4.6C SR2 with Kernel 4.6D_EXT 64-Bit, Patch 23xx DB2 LUW 9.1 FP3SAP or higher for Linux x86_64_Bit (Download from http://service.sap.com) DB2 Version 9.5 for Linux (Download from http://service.sap.com), released for SAP 7.0 SR3 DB2 Version 9.7 for Linux (Download from http://service.sap.com), released for SAP Download the corresponding license files from SAP You also need to install DB2 LDAP-Plug-in if you are not using DB2 Version 9.7 FixPack 1 or later from http://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=swg -dm-db2ldap Installation Guide for SAP Solutions 27 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 http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.w n.doc/doc/c0054120.html 7.1.2 Pre-Installation Steps 1. Stop the FA-Autonomous Agents during installation time. 2. Create a new SID instance using ff_sid_adm.pl (if it is not already specified with the Management Tool): ff_sid_adm.pl --op add --pool pool1 –-sid LB4 --sapversion 7.0 --db DB2V91:159 --sap ci:57:157:157 --sap ascs:55:155:155 --sap app:58:158:158 --sap scs:56:156:156 --db2srv sapdb2LB4:60000,DB2_db2lb4:60001,DB2_db2lb4_1:60002, DB2_db2lb4_2:60003,DB2_db2lb4_END:60004 The script ff_sid_adm.pl prepares the system files /etc/hosts and /etc/services of the application nodes known in the specific pool. The script writes a log file in /FlexFrame/volFF/pool-pool1/db2 to show you the changes made in system files. There will also a log file with LDIFs of all LDAP modifications done with this SID. 3. Run ff_sid_mnt_adm.pl if you want to relocate your directories for SAPDATA/SAPLOG to a volume of your own. 4. Run ff_setup_sid_folder.sh (if SID was created manually as describe above): ff_setup_sid_folder.sh –p pool1 –s LB4 7.2 Mount Options FlexFrame tries to be consistent with the recommendations for NFS mount options of storage and database software vendors. Sometimes however FlexFrame requires different settings. This chapter should explain you how the mount options are set in FlexFrame. 28 Installation Guide for SAP Solutions 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. 7.2.1 Database files (sapdata, saplog) Option Comment rw read/write operations allowed; NFS default value. hard, nointr No user interrupt is allowed. Process is always waits until server come back online. NFS default is nointr rsize=32768, wsize=32768 Block size for reading/writing. FlexFrame specific setting. proto=tcp Communication protocol TCP is used; NFS default value nolock No NFS file locking is requested. This is sufficient since one server uses the files exclusively. It means a better performance. NFS default is lock. vers=3 NFS version used. timeo=600 Wait 60 sec until a retransmission is sent after timeout. NFS default is 0.7, the maximum value is 60 sec. retrans=2 At least two ‗minor timeouts‘ are accepted until a operation is aborted. NFS default is 3. suid Allow set-user-id or setgroup-id; NFS default value bg Retrial of mount is performed in background 7.2.2 Binaries and Configuration files Option Comment rw NFS default value is used (rw). hard, nointr No user interrupt is allowed. rsize=32768, wsize=32768 FlexFrame specific setting. proto=tcp Communication protocol default tcp is used. Installation Guide for SAP Solutions 29 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 Preparations for SAP Installation 8 Preparations for SAP Installation Installation directories and virtual interfaces All platforms (see chapter 8.1) SAP JAVA Cryptographic Toolkit (optional component) Linux (see chapter 6.1) Setup directory structures (default) (8.5.1) Own volumes (see chapter 8.5.2) or SID specific volumes (see chapter 8.5.3) or Pool specific volumes (see chapter 8.5.3) or SAN (see chapter 8.5.4) Configuration of virtual interfaces Setup interfaces manually (see chapter 8.2) /dev/urandom Configuration of /dev/urandom (see chapter 8.6) Pre-Installation hints SAP 7.0 EHP3 SAP 7.0 EHP3 (see chapter 12.13) 8.1 General The customary instructions and guide lines apply to the installation of the software components. The deviations from these which are required are described here. Don‘t change the host name of the Application Node where you are going to install the SAP and DB software. Installation Guide for SAP Solutions 31 Preparations for SAP Installation After the installation is done, further steps are described in this document to virtualize the SAP instance (except SAPINST 640 SR1 when used with the SAPINST_USE_HOSTNAME parameter). Please install CI (J2EE: SCS) first, then DB, (J2EE: JC 2nd) and the Application Server at the end. Setup the virtual interfaces before installing the SAP solution. It is absolutly essential to setup both virtual interfaces (client + server LAN) and make sure that they up an running. Please make sure that the FA Application Agents are stopped on the hosts while you are installing SAP software: /etc/init.d/myAMC.FA_AppAgent stop Check the status with: /etc/init.d/myAMC.FA_AppAgent status The SAP Installation CDs/DVDs have to be copied to the NetApp Filer (from the Control Node into the directory /FlexFrame/volFF/FlexFrame/stage/SAP_SW/). 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 -s 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. 32 Installation Guide for SAP Solutions Preparations for SAP Installation Create the SAP installation directory into which the sapinst files are extracted: server:/ # mkdir /usr/sap//install server:/ # chmod 777 /usr/sap//install server:/ # cd /usr/sap//install 8.2 How to configure the interfaces manually Setup the required interfaces you can use the new interface ff_service.sh as shown below (examples for SID ―OSM‖ and instance number ―25‖. server:/ # ff_service.sh –t db –s osm –a istart server:/ # ff_service.sh –t ci –s osm –a istart server:/ # ff_service.sh –t ascs –s osm –a istart server:/ # ff_service.sh –t app –i 25 –s osm –a istart server:/ # ff_service.sh –t j –i 25 –s osm –a istart server:/ # ff_service.sh –t jc –s osm –a istart 8.3 ASCS ABAP Central Service Instance in General A central services instance consists of the message server and the enqueue server: Message server Only one message server can run on each AS Java or AS ABAP usage type. The message server handles the communication between the dialog instances and also supplies information to the SAP Web dispatcher about load balancing. Enqueue server Installation Guide for SAP Solutions 33 Preparations for SAP Installation The enqueue server contains a lock table that handles logical database locks plus infrastructure locks set by Java server process. The enqueue server also synchronizes data in a Java cluster. In usage type AS ABAP, the enqueue server handles only locks on data objects. 8.4 SAP Java Cryptographic Toolkit During the SAPINST installation process you will be asked about the ―SAP Java Cryptographic Toolkit‖. If you select this option, some files of the JAVA directory have to be modifiable. However, the root file system (Linux) where the java directory is located is mounted read only and can not be modified. In that case, logon to the Control Node, mount the resources of the OS images and do the following steps: SLES10_x86: JAVA_HOME is /usr/lib64/jvm/java The example below shows SLESnn (SUN Java) cn1:~#> cd /FlexFrame/volFF/os/Linux/FSC5.0xxx/root_img/usr/lib64/java cn1:~#> cp -rp ../../../../var_img/var-xxxxxxxx/ applnode1:~#> mount -t nfs filerxxxx:/........var-xxxxxxxx/ /usr/java/ (e.g. = j2sdk1.4.2_12) Now the JAVA files are writeable. If the installation has finished successfully, do the following: applnode1:~#> umount /usr/java/ cn1:~#> cd ..../var_img/var-xxxxxxxx/ cn1:~#> cp -rp ...os/Linux/FSC5.0xxx/root_img/usr/lib64/java / (e.g. = j2sdk1.4.2_12) 8.5 Setting up SAP directories (Control Center) 8.5.1 Standard Volumes If you want to use the standard volumes ―sapdata‖ and ―saplog‖ or you have specified specific volumes for this SID or its corresponding pool (by FF Configuration Tool) you just need to call ff_setup_sid_folder.sh. 34 Installation Guide for SAP Solutions Preparations for SAP Installation Example: CN1# ff_setup_sid_folder.sh -p pool1 –s S03 8.5.2 Specify volumes of your own If you want to store SAPDATA/SAPLOG on a volume different from default you need to run ff_sid_mnt_adm.pl before running ff_setup_sid_folder.sh. Further information about the commands see the corresponding chapter in the Adminstration and Operation Guide. Example: CN1# ff_sid_mnt_adm.pl –op add –pool pool2 –sid S03 \ --sap --sapdata jer1na-st:/vol//pool1/S03 --saplog jer1na-st:/vol//pool1/S03 CN1# ff_setup_sid_folder.sh -p pool1 –s S03 8.5.3 \ SID/Poolspecific volumes SID- or pool-specific volumes are specified by FF Configuration Tool. So you just enter ff_setup_sid_folder.sh. Example: CN1# ff_setup_sid_folder.sh -p pool1 –s S03 8.5.4 Using SAN Before installing a SAP system you have to prepare the SAPDATA and SAPLOG concerning the SAN requirements. Please refer to chapter ―Creating Volumes and Filesystems‖ in the ―Administration and Operation Guide‖. Before the database instance can be installed you have to run ff_san_ldap.pl ff_setup_sid_folder.sh ff_san_mount.sh changing owner of database files Important: Especially for MaxDB database installations there is a special reference needed to address the data and log volumes. If you are asked for datafile directories you have to Installation Guide for SAP Solutions 35 Preparations for SAP Installation enter /sapdata/sapdata/ for data volumes and /saplog/saplog/ 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 Preparations for SAP Installation 8.7 Predefined global users Depending on SAP reelase or used database type there are a small number of users which are generally created. These are no specific users of FF4SAP. They are requested by SAP services. In case of the default pool they are created at pool creation time, with additional pools the creation of a new SID (ff_sid_adm.pl) also creates missing global users. Usually there should be no login possible to the system by these users. So you are strongly recommended to change the standard password to a complex password string for these users using ‗ff_user_adm.pl –op mod –pass ….‘ user name purpose dasusr1/db2fenc1/ db2inst Introduced with DB2 V9.1 to setup DB2 databases sapadm SAP requested user needed in SMD environment (SAP System Administrator) sdb SAP requested user needed if SAPDB/MaxDB is used as database type. SMD_ADMIN/smd_admin SAP requested user needed in older configurations using Diagnostic agents Installation Guide for SAP Solutions 37 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/install Create a further directory for each service you want to install,e.g. /usr/sap/install/db, /usr/sap/install/scs) Extract the installation files in each service installation directory Start the installer sapinst in the corresponding service installation directory The specific installation description always describes the issues which are new with the specific SAP installation. If there will be an error which is not described at the specific SAP installation description you should refer to older versions with the same installation type. If you will do an update of your software stack you may get more or less the same problems as given with an installation from scratch. From our point of view the descriptions to overcome those problems are described for installations from scratch are also valid for updates. 1. Operating System settings Operating System in General (see chapter 6 ) 2. Make virtual IPs available for Sap instances General hint how to configure interfaces manually please refer to ―Interface Configuration‖ (see chapter 8.2) 3. Preparations for Database Installation Check correspoding installation hints (see chapter 7) 4. Preparations for SAP installation Check corresponding installation hints (see chapter 8) 38 Installation Guide for SAP Solutions 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.14) or ERS 7.00 (see chapter 12.15) or SAP 7.1 (see chapter 13) or Installation Guide for SAP Solutions 39 SAP Installation - Overview SAP 7.1 ERS (see chapter 13.3 ) Or SAP 7.3 (see chapter 14) 6. Post installation steps (database) Check corresponding installation hints (see chapter15.3.1) 7. Post installation steps (SAP) Check corresponding installation hints (see chapter16) 40 Installation Guide for SAP Solutions 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 adm, ora and sqd. A workaround must be observed if SAP is installed on the NetApp Filer using R3SETUP (up to release 4.6C). This is described in the following technical report: SAPDB http://www.netapp.com/library/tr/3143.pdf R3SETUP does not yet permit installation of SAP on NFS drives in this version. If sapinst is used for installation (release 4.7 and above or Web AS 6.20 or 6.40), installation on the NetApp Filer with NFS is directly supported. Installation Guide for SAP Solutions 41 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 16.2 ) 2a. DB post installation step Oracle 9.2 only (see chapter 15.2.1) 3. Setting virtual DB host All platforms (see chapter16.1.2) 4. Install CI service All platforms (see chapter 10.1.1 5. Setting virtual CI host All platforms (see chapter16.1.1) 6. Install Application service 7. Setting virtual Application host All Platforms (see chapter16.1) 8. Installation issues All platforms (see chapter 10.1) 9. Post install – start/stop SAP All platforms (see chapter16.9) 10.1 SAPDB / MaxDB / Oracle During the installation of SAP 4.6CSR2, the R3SETUP will fail several times due to the fact that the necessary directories, links and ownerships have already been created in FlexFrame. The current *.R3S file (e.g. CENTRAL.R3S or DATABASE.R3S) has to be edited and R3SETUP needs to be restarted.07 42 Installation Guide for SAP Solutions Installing SAP 4.6C SR2 The requested file system is not mounted automatically. To mount the file system, issue the command cd /sapmnt//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 Installing SAP 4.6C SR2 Restart R3SETUP. Edit the *.R3S file and change STATUS=ERROR to STATUS=OK. 44 Installation Guide for SAP Solutions 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 Installing SAP 4.6C SR2 Restart R3SETUP. 10.1.1 Installing the Central Instance (CI) In case of a virtual installation the virtual interface must be up and running. Setup the interfaces for central instance host ―ciosm‖ as shown in the examples. baby_3:~ baby_3:~ baby_3:~ baby_3:~ # # # # cd /usr/sap/OSM/install mkdir OSMCI chmod 777 OSMCI 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 Installing SAP 4.6C SR2 # SAPINST_JRE_HOME=/usr/j2sdk/j2sdk1.4.2_10 # export SAPINST_JRE_HOME # ./sapinst SAPINST_USE_HOSTNAME=ciosm /product.catalog Installation Guide for SAP Solutions 47 Installing SAP 4.6C SR2 48 Installation Guide for SAP Solutions 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 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 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 11.2.1) JAVA+ABAP (see chapter 11.2.1) 3. Virtualize user environment for SCS host JAVA (see chapter16.1.4) JAVA+ABAP (see chapter 16.1.4) 4. Install DB service ABAP (Oracle) (see chapter 11.2.6) JAVA (see chapter 11.2.2) JAVA-Addin (see chapter Fehler! Verweisquelle konnte nicht gefunden werden.) 5. Virtualize user environment for DB host ALL see chapter 18.1.2 ALL see chapter 18.1.2 ALL see chapter 18.1.2 6. Install Central Instance ABAP (Oracle) (see chapter 11.2.5) JAVA (see chapter 11.2.3) JAVA-Addin (see chapter 11.3.3) 7. Virtualize user environment for CI host All see chapter 18.1.1 All see chapter 18.1.1 All see chapter 18.1.1 8. Install Application service ABAP (see chapter 11.2.7 JAVA (see chapter 11.2.4) 9. Virtualize user environment for application host All see chapter 18.1.3 All see chapter 18.1.3 Installation Guide for SAP Solutions 51 All see chapter 18.1.3 Installing Web AS 6.40 with NetWeaver04 SR1 11.1 Description of Web AS 6.40 JAVA Central Java Instance: Java Dispatcher: Receives client requests and forwards them to the server processes accordingly Java Server Processes: Actually process the requests Server processes hold the session data Central Services Instance: Java Enqueue Service: Manages logical locks Ensure server synchronization Java Message Service: Central service for cluster internal communication, like event notifications, broadcasts, exchange of cache content etc. Provides cluster state information the SAP Web Dispatcher Change to the SAP installation directory and start SAPINST. Use the physical host name of the installation server when you are asked for a host name of the CI, SCS or DB. After finishing the SAP installation, perform the post-installation steps (see chapter ―SAP System Administration‖ on page 92). For installation of a J2EE instance or a J2EE Add-In in an existing ABAP instance, the service sapms 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 Installing Web AS 6.40 with NetWeaver04 SR1 11.2 Web AS 6.40 NetWeaver04SR1 JAVA MaxDB/Oracle Start the installation using virtual host names. The example shows a 6.40 JAVA NW04SR1 on MaxDB (SID=MLJ) installation. 11.2.1 SCS Make sure that the IP interface address of the is up and running. Setup the interfaces for host ―scsosm‖ as shown in the examples. applnode1:~#> cd /usr/sap//install_SCS applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product_ha.catalog Installation Guide for SAP Solutions 53 Installing Web AS 6.40 with NetWeaver04 SR1 54 Installation Guide for SAP Solutions Installing Web AS 6.40 with NetWeaver04 SR1 Type in the virtual DB host name Installation Guide for SAP Solutions 55 Installing Web AS 6.40 with NetWeaver04 SR1 56 Installation Guide for SAP Solutions Installing Web AS 6.40 with NetWeaver04 SR1 11.2.2 DB Make sure that the IP interface address of the is up and running. Setup the interfaces for host ―dbosm‖ as shown in the examples. applnode1:~#> cd /usr/sap//install_DB applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product_ha.catalog Installation Guide for SAP Solutions 57 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. 11.2.3 JC Make sure that the IP interface address of the is up and running. Setup the interfaces for host ―jcosm‖ (until SAP 7.0) or ―josm‖ (SAP 7.1 up) as shown in the examples. applnode1:~#> cd /usr/sap//install_JC applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product_ha.catalog 11.2.4 J Make sure that the IP interface address of the Java application instance is up and running. Set up the interfaces for host ―josm‖ as shown in the examples applnode1:~#> cd /usr/sap//install_J applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product_ha.catalog 58 Installation Guide for SAP Solutions Installing Web AS 6.40 with NetWeaver04 SR1 11.2.5 CI Make sure that the IP interface address of the is up and running. applnode1:~#> cd /usr/sap//install_CI applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product.catalog Installation Guide for SAP Solutions 59 Installing Web AS 6.40 with NetWeaver04 SR1 60 Installation Guide for SAP Solutions Installing Web AS 6.40 with NetWeaver04 SR1 Type in the virtual DB host name Installation Guide for SAP Solutions 61 Installing Web AS 6.40 with NetWeaver04 SR1 11.2.6 DB Make sure that the IP interface address of the is up and running. Setup the interfaces for host ―dbosm-se‖ as shown in example (chapter 8.2) applnode1:~#> cd /usr/sap//install_DB applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /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‖ 11.2.7 APP Make sure that the IP interface address of the virtual hostname of the application instance is up and running. Setup the interfaces for host ―apposm‖ as shown in example (chapter 8.2) applnode1:~#> cd /usr/sap//install_APP applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product.catalog 11.3 Web AS 6.40 ABAP + JAVA-AddIn NetWeaver04SR1 11.3.1 SCS Make sure that the IP interface address of the virtual hostname of the SCS instance is up and running. Setup the interfaces for host "scsosm" as shown in example (chapter 8.2) Before starting the installation procedure, add the sapms entry manually in the /etc/services (do not forget to remove the entry after the installation!). 62 Installation Guide for SAP Solutions Installing Web AS 6.40 with NetWeaver04 SR1 11.3.2 DB Make sure that the IP interface address of the virtual host of the database instance is up and running. Setup the interfaces for host "dbosm-se" as shown in example (chapter 8.2) applnode1:~#> cd /usr/sap//install_DB applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product.catalog 11.3.3 CI Make sure that the IP interface address of the virtual host of the central instance is up and running. Setup the interfaces for host ―ciosm‖ as shown in example (chapter 8.2) applnode1:~#> cd /usr/sap//install_CI applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product.catalog 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//install applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product.catalog Central Instance Finalization: applnode1:~#> cd /usr/sap//install applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product.catalog Example: The example shows an installation on MaxDB. Installation Guide for SAP Solutions 63 Installing Web AS 6.40 with NetWeaver04 SR1 applnode1:~#> cd /usr/sap//install applnode1:~#> /sapinst –extract applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product.catalog 64 Installation Guide for SAP Solutions Installing Web AS 6.40 with NetWeaver04 SR1 Type in the virtual CI host name Installation Guide for SAP Solutions 65 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-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 Installing Web AS 6.40 with NetWeaver04 SR1 Check and modify the following: 1. Copy the .sapenv_ci.csh file to .sapenv_scs.csh (also for the .sh file). 2. Move the instance/start profile to the correct hostname. 3. Exchange the hostname in the instance/start profile. 4. Go to section 16.1 in this document to change the hostname for the SCS instance. 11.4 Web AS 6.40 Application Server JAVA-AddIn We assume that all required components (DB, ABAP CI, JAVA-AddIn and SCS) have already been installed. An /etc/services entry for 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 (.../sapinst –extract) applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= /product.catalog Installation Guide for SAP Solutions 67 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 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 12.1. During installation of any SAP solution the SAP or DB instance did not start up. In this case use the FlexFrame start scripts and start the instance manually, (e.g.): ERROR 2008-11-06 10:29:35 CJSlibModule::writeError_impl() CJS-20022 Could not start instance 'JC41' of SAP system OLP. ERROR 2008-11-06 10:29:35 CJSlibModule::writeError_impl() CJS-20022 Could not start instance 'JC41' of SAP system The following table shows you the steps you have to perform when you want to install NetWeaver 7.0SR3 1. Introduction All Types (see chapter 12) 2. Install SAP Service (e.g. SCS) Installation example (see chapter 12.1) 4. Install DB service Database Installation - in general (see chapter 15) and Oracle 10 specifics (see chapter 12.5) or MaxDB76 / 77 specifics (see chapter 12.6) or Installation Guide for SAP Solutions 69 Installing NetWeaver 7.0SR3 MaxDB76 / 77 on SLES9_x86/SLES10_x86 specifics (see chapter 12.7) 5a. Standard installation Types or Enterprise Portal (EP) (see chapter 12.9 ) or ABAP + JAVA Addin (see chapter 12.10) or JAVA only (see chapter 12.11) or SAP 7.01/SLES9 (see chapter 12.12) 5b. Live Cache (MaxDB 76/77) or Additional installation requests (see chapter 12.14 5c. Enqueue Replicated Server (ERS) Installation until NetWeaver 2004s SR3 (see chapter 12.15 ) 6. General post installation steps (SAP 7.0 only) Linux (see chapter 6.1) 70 Installation Guide for SAP Solutions Installing NetWeaver 7.0SR3 12.1 Installation of SAP Solutions 1. Select one of the SAP solutions. It has no effect which DB or SAP solution you want to install. This part is necessary for every NetWeaver 7.0SR3 installation step. 2. Click on the Next button. 3. If the next screen appears, please abort the installation. 4. Modify the files control.xml and sapinst in the installation directory. control.xml: Installation Guide for SAP Solutions 71 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/‖ sapinst 5. Restart the installation: applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= 12.1.1 Prerequisite Checker (Linux) 72 Installation Guide for SAP Solutions Installing NetWeaver 7.0SR3 suse-sapinit: SAP has renamed the name of the package into sapinit Kernel/Glibc Version: You can ignore the warning. 12.2 Sapinit File (Linux) WARNING 2008-11-06 10:06:51 CJSlibModule::writeWarning_impl() Execution of the command "/usr/sap/OLP/install/SCS/installsapinit.sh" finished with return code 1. Output: mv: cannot move `/etc/init.d/sapinit' to `/etc/init.d/sapinit.old': Read-only file system cp: cannot create regular file `/etc/init.d/sapinit': Read-only file system ERROR 2008-11-06 10:06:51 CJSlibModule::writeError_impl() MUT-03011 Execution of the command "/usr/sap/OLP/install/SCS/installsapinit.sh" finished with return code 1. Output: mv: cannot move `/etc/init.d/sapinit' to `/etc/init.d/sapinit.old': Read-only file system cp: cannot create regular file `/etc/init.d/sapinit': Read-only file system ERROR 2008-11-06 10:06:51 [iaxxgenimp.cpp:736] showDialog() FCO-00011 The step installSAPInit with step key |NW_Java_SCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5|0|installSAPInit was executed with status ERROR . 1. Proceed as follows: applnode1: > vi keydb.xml to OK Installation Guide for SAP Solutions 73 Installing NetWeaver 7.0SR3 2. Restart the installation: applnode1: > ./sapinst SAPINST_USE_HOSTNAME= 12.3 installsapinit.sh – symlink (Linux) WARNING 2008-11-06 10:43:23 CJSlibModule::writeWarning_impl() Execution of the command "/usr/sap/LO7/install/ASCS/installsapinit.sh" with return code 5. Output: insserv: can not symlink(../sapinit, rc3.d/S14sapinit): Read-only file insserv: can not symlink(../sapinit, rc3.d/K08sapinit): Read-only file insserv: can not symlink(../sapinit, rc5.d/S14sapinit): Read-only file insserv: can not symlink(../sapinit, rc5.d/K08sapinit): Read-only file finished system system system system ERROR 2008-11-06 10:43:23 CJSlibModule::writeError_impl() MUT-03011 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 2008-11-06 10:43:23 [iaxxgenimp.cpp:736] showDialog() FCO-00011 The step installSAPInit with step key |NW_ABAP_ASCS|ind|ind|ind|ind|0|0|NW_System|ind|ind|ind|ind|5|0|installSAPInit was executed with status ERROR . 1. Proceed as follows: applnode1: > vi keydb.xml 74 Installation Guide for SAP Solutions Installing NetWeaver 7.0SR3 applnode1: > ./sapinst SAPINST_USE_HOSTNAME= 12.4 Services File (Linux) ERROR 2008-11-06 11:22:09 [syxxsyshlp.cpp:78] syslib::printOSError(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage) FSL-00001 System call failed. Error 30 (Read-only file system) in execution of system call 'openU' with parameter (/etc/services.SAPtmp, O_WRONLY | O_TRUNC | O_CREAT, S_IRWXU | S_IRWXG | S_IRWXO), line (413) in file (syuxcfile.cpp). ERROR 2008-11-06 11:22:09 [syuxcfile.cpp:417] CSyFileImpl::copy(const CSyPath & /etc/services.SAPtmp, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const FSL-02013 Unable to access file /etc/services.SAPtmp: cannot get write access. ERROR 2008-11-06 11:22:09 [syxxcsent.cpp:492] CSyServicesEntryImpl::editServices(ISyServicesEntry::eWriteMode REPLACE_NAME) const FSL-03006 Unknown exception caught when trying to add an entry to the service file. ERROR 2008-11-06 11:22:09 CJSlibModule::writeError_impl() MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text undefined. Installation Guide for SAP Solutions 75 Installing NetWeaver 7.0SR3 1. Abort the installation and proceed as follows: applnode1: > vi keydb.xml to OK 2. Restart the installation: applnode1: > ./sapinst SAPINST_USE_HOSTNAME= 12.5 NetWeaver 7.0SR3 and Oracle 10 The installation could fail due to the following eror: ERROR 2008-11-06 10:24:26 [iaxxinscbk.cpp:271] abortInstallation CJS-00084 SQL statement or script failed.
DIAGNOSIS: Error message: SP2-0606: Cannot create SPOOL file "recompile.log" 'UTL_RECOMP_BEGIN:'||TO_CH -------------------------utl_recomp_begin: 10:06:24 PL/SQL procedure successfully completed. PL/SQL procedure successfully completed. 'UTL_RECOMP_END:'||TO_CH -----------------------utl_recomp_end: 10:06:25 Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production With the Partitioning and Data Mining options .
SOLUTION: See ora_sql_results.log and the Oracle documentation for details. ERROR 76 2008-11-06 10:24:26 CJSlibModule::writeError_impl() Installation Guide for SAP Solutions Installing NetWeaver 7.0SR3 MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined. ERROR 2008-11-06 10:24:26 [iaxxgenimp.cpp:736] showDialog() FCO-00011 The step recompileDDIC with step key |NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_Cr eateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|i nd|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|recomp ileDDIC was executed with status ERROR. Abort the installtion and proceed as follows 1. Change the umask value entry in the sapinst file to 022 2. Restart the installation. perl –i.bak –p –e ―s/umask 027/umask 022/‖ sapinst applnode1: > chmod 777 * applnode1: > chmod 777 . applnode1: > ./sapinst SAPINST_USE_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] 2006-03-14 10:20:53 [syuxcuser.cpp:1813] CSyUserImpl_getOsInfos(ILogBook *m_logBook, iastring sName, iastring sID, tSyUserInfo& msUserinfo) FSH-00006 Return value of function getpwnam(undefined) is NULL. TRACE [syuxcuser.cpp:1493] bool CSyUserImpl::isExistingOnOS() checking existence of account user="undefined" succeeded with false. ERROR 2006-03-14 10:20:53 [syuxcuser.cpp:278] CSyUserImpl::CSyUserImpl(const CUserData&, bool) FSL-01027 Account user="undefined" does not exist. TRACE [iaxxejsbas.hpp:379] handleException() Converting exception into JS Exception ESyException. ERROR 2006-03-14 10:20:53 CJSlibModule::writeError_impl() Installation Guide for SAP Solutions 77 Installing NetWeaver 7.0SR3 MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text undefined. TRACE [iaxxejsbas.hpp:451] EJS_Base::dispatchFunctionCall() JS Callback has thrown unknown exception. Rethrowing. ERROR 2006-03-14 10:20:53 [iaxxgenimp.cpp:653] showDialog() FCO-00011 The step sdb_create_volumes_fs with step key |NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDB|ind|ind|ind|ind|9|0|NW_ADA_DB|in d|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|2|0|SdbInstanceDialogs|ind| ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_create_volumes_fs was executed with status ERROR . TRACE 1. [iaxxgenimp.cpp:651] showDialog() Logon to one of the control nodes: cn1:~#> cd /FlexFrame/volFF/os/Linux//root_img/etc/opt cn1:~#> ls –l sdb 2. If the sdb file does not exist, go to section ―MaxDB 7.5/7.6/7.7 /etc/opt/sdb‖ on page 139. cn1:~#> rm sdb cn1:~#> cp –p /FlexFrame/volFF/pool-/sapdb//sql/sdb . 3. Restart the installation: applnode1: > ./sapinst SAPINST_USE_HOSTNAME= 4. If the installation finished succesfully change it back as it was originally: cn1:~#> cd /FlexFrame/volFF/os/Linux//root_img/etc/opt cn1:~#> rm sdb cn1:~#> ln –s /sapdb/sql/sdb . 78 Installation Guide for SAP Solutions Installing NetWeaver 7.0SR3 12.7 NetWeaver 7.0SR3 MaxDB76 and SLES9_x86/SLES10_x86 During the ABAP import using MaxDB76 and SLES9/SLES10 the installation has permission trouble: Installation Guide for SAP Solutions 79 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 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -nolog -c 0" -trace all -sapinst" finished with return code 2. Output: java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 2.2) IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142ifx-20051125 (JIT enabled) J9VM - 20050524_1742_LHdSMr JIT - r7_level20050518_1803) java.io.FileNotFoundException: /usr/sap/BLM/install/DB/import_monitor_cmd.properties (Permission denied) Required system resources are missing or not available: DDL control file '/usr/sap/BLM/install/DB/DDLADA.TPL' does not have read access. ERROR 2008-11-06 11:27:58 CJSlibModule::writeError_impl() CJS-30022 Program 'Migration Monitor' exits with error code 2. For details see log file(s) import_monitor.java.log, import_monitor.log. ERROR 2008-11-06 11:27:58 [iaxxgenimp.cpp:736] showDialog() FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_AB AP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigratio nMonitor was executed with status ERROR . INFO 2008-11-06 11:31:08 [iaxxgenimp.cpp:787] Do not abort the installtion. 1. Change the permissions of the file DDLADA.TPL 2. Click on the RETRY button to restart the installation. applnode1: > 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 Installing NetWeaver 7.0SR3 ERROR 2008-11-06 11:25:45 FCO-00011 The step sdb_create_db_instance with step key |NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_Cr eateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind| ind|ind|ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind| ind|ind|0|0|sdb_create_db_instance was executed with status ERROR . XCMDOUT.LOG (Example: SID=CSM, Password=password) XCMDOUT.LOG > Subprocess starts at 20060706112543 Execute Command : /sapdb/programs/bin/dbmcli -n dbcsm-se -R /sapdb/CSM/db db_create CSM CONTROL,******** sqdcsm,password Start subprocess as user with uid: root > Subprocess stops at 20060706112545 ERR -24875,ERR_NEEDADMI: The operating system user is not a member of the database administrators group -24994,ERR_RTE: Runtime environment error 20145,UNIX password ******** 1. Follow the instructions of SAP note: 965346 2. Click on the RETRY button from the SAPINST screen. 12.9 NetWeaver 7.0SR3 and EP The TCP kernel parameters tcp:tcp_conn_hash_size=23768 and tcp:tcp_time_wait_interval=60000 are not set automatically in a FlexFrame environment. These parameters should be set for EP. If the installation stops with the following error do not abort the SAPINST installation: Error: Aborted: development component 'irj'/'sap.com'/'SAP AG'/'7.0004.20050921183647.0000': Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running. com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [jcolp] with user name: [Administrator] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is Installation Guide for SAP Solutions 81 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 Do not forget to restart the JC instance manually 3. 82 Click on the RETRY button at the SAPINST screen. Installation Guide for SAP Solutions Installing NetWeaver 7.0SR3 12.10 NetWeaver 7.0SR3 ABAP+JAVA-AddIn The installation steps of ASCS (if selected) and Database (Oracle or MaxDB) are fullfilled. During the installation of the CI instance the following error could occurre: steps Example: SID=XOS, ORACLE10R2, PI TYPE=A
STATE=
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 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) ... 30 more caused by: 84 Installation Guide for SAP Solutions 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 at at at at at at at at at at at at at at at at at at at at at at at java.net.SocketInputStream.read(SocketInputStream.java:182) com.tssap.dtr.client.lib.protocol.streams.ChunkedInputStream.readLine(ChunkedInputStream.java:323) com.tssap.dtr.client.lib.protocol.streams.ResponseStream.readLine(ResponseStream.java:271) com.tssap.dtr.client.lib.protocol.impl.Response.initialize(Response.java:476) com.tssap.dtr.client.lib.protocol.Connection.getResponse(Connection.java:2604) com.tssap.dtr.client.lib.protocol.Connection.sendInternal(Connection.java:1578) com.tssap.dtr.client.lib.protocol.Connection.send(Connection.java:1427) com.sap.sld.api.wbem.client.WBEMHttpRequestSender.send(WBEMHttpRequestSender.java:142) com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:720) com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:694) com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:638) com.sap.sld.api.wbem.client.WBEMRemoteClient.referencesImpl(WBEMRemoteClient.java:375) com.sap.sld.api.wbem.client.WBEMClient.references(WBEMClient.java:1773) com.sap.sld.api.wbem.client.WBEMClientUtil.referencesComplete(WBEMClientUtil.java:490) com.sap.lcr.pers.delta.importing.SAPCRUpgrade.collectAssociationsForRestoration(SAPCRUpgrade.java:700) com.sap.lcr.pers.delta.importing.SAPCRUpgrade.delete(SAPCRUpgrade.java:355) com.sap.lcr.pers.delta.importing.ImportHandler.loadFullImport(ImportHandler.java:1765) com.sap.lcr.pers.delta.importing.ImportHandler.loadImpl(ImportHandler.java:1605) com.sap.lcr.pers.delta.importing.ImportHandler.load(ImportHandler.java:1573) com.sap.ctc.util.SLDConfig.importSldContent(SLDConfig.java:812) com.sap.ctc.util.SLDConfig.performFunction(SLDConfig.java:154) com.sap.ctc.util.ConfigServlet.doGet(ConfigServlet.java:69) javax.servlet.http.HttpServlet.service(HttpServlet.java:740) javax.servlet.http.HttpServlet.service(HttpServlet.java:853) Installation Guide for SAP Solutions 85 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=http://cixos:59000 USER=J2EE_ADMIN ... Import Status: PREPARING # ERROR: CIM_ERR_FAILED: IO error: Read timed out 86 Installation Guide for SAP Solutions 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 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 Installing NetWeaver 7.0SR3 12.11 NetWeaver 7.0SR3 JAVA only The steps installation of SCS and Database (Oracle or MaxDB) are fullfilled. During the installation of the JC instance the following error could occurre: Checking if another SDM is running on port 57518 Info: Checking if another SDM is running on port 57518 Info: Start to add definitions of SubstVars. Info: Used addmode="replace_existing" Info: Reading substvarfile "SUBS_PARAM_TO_BE_SET.XML". Error: Can't read from file /usr/sap/P11/install/JC/SUBS_PARAM_TO_BE_SET.XML. Error: Could not add definitions of SubstVars. Processing error. Return code: 4 Error: Processing error. Return code: 4 ERROR 2008-11-06 10:26:59 [iaxxinscbk.cpp:271] abortInstallation MUT-02041 SDM call of addsubstvars ends with returncode 4 ERROR 2008-11-06 10:26:59 CJSlibModule::writeError_impl() MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined. ERROR 2008-11-06 10:26:59 [iaxxgenimp.cpp:736] showDialog() FCO-00011 The step setSubstVars with step key |NW_Java_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|10|0|NW_CI_Instance_ Configure_Java|ind|ind|ind|ind|3|0|setSubstVars was executed with status ERROR . 1. Change the umask value entry in the sapinst file to 022. perl –i.bak –p –e ―s/umask 027/umask 022/‖ sapinst 2. Restart the installation: applnode1:~#> ./sapinst SAPINST_USE_HOSTNAME= 12.12 NetWeaver 7.01/SLES 9 Using NetWeaver 7.01 and SLES9 requires a special version of libstdc++ or libgcc_s. Refer to SAP-Note 1021236. 88 Installation Guide for SAP Solutions Installing NetWeaver 7.0SR3 12.13 SAP 7.0 EHP3 12.13.1 Installation Media Label is wrong The installation media are not correct. During the installation of the Central Instance you will get an error message about a wrong label on installation media. Please refer to the corresponding SAP-Note 1562522 12.13.2 Incompatibilities with Linux Kernel Installing and starting the SAP system or login via SAPGUI will cause an error message that the current Linux kernel is not supported (transaction ‗sick‘ cannot be started). SAPOSCOL may fail because of ‗… cannot determine current Linux …‘. The behaviour is caused by SAP components which are not at the most current patch level. Please refer to SAP-Note 1629558 which describes the required patch levels for the corresponding components. The SAP-Note 1310037 describes only a shortterm solution. It could affect other services. 12.14 LiveCache For LiveCache installation you have to 1. make the network interface available for lc-se 2. use lc-se for SAPINST_USE_HOSTNAME 3. during installation use lc-se for liveCache host/server 4. use default password password for user lcaadm (after installation change the default to a password of your own) The FA Agents and the start and stop script expect the existence of an alias ―c‖ for xuser. If it does not exist please use xuser –d SID –n host –se –u control,passw –U c –S SAPR3 –t 0 –I 0 to create. To check creation use xuser list | more. 12.15 ERS – Enqueue Replicated Server (until NetWeaver 2004s SR3) For installation hints please have a look into corresponding SAP sites (start at http://help.sap.com/saphelp_nw2004s/helpdata/en/f0/b57338788f4d72e Installation Guide for SAP Solutions 89 Installing NetWeaver 7.0SR3 10000009b38f8cf/frameset.htm, Standalone Enqueue Server, High Availability, Configuration the Replication Server). The hostname must be set to ers 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. 90 Installation Guide for SAP Solutions Installing NetWeaver 7.0SR3 12.16 Installation of SAP Solutions – Post Phase The FlexFrame start/stop scripts wil start/stop the SAP service sapstartsrv automatically. 1. Check the following links: applnode1:/etc/init.d # applnode1:/etc/init.d # lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root lrwxrwxrwx 1 root root 2. cd ls 10 10 10 10 /etc/init.d –l ./rc[3-5].d/*sapinit* May 18 14:58 rc3.d/K08sapinit May 18 14:58 rc3.d/S14sapinit May 18 14:58 rc5.d/K08sapinit May 18 14:58 rc5.d/S14sapinit -> -> -> -> ../sapinit ../sapinit ../sapinit ../sapinit 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:~#> cn1:~#> cn1:~#> cn1:~#> cn1:~#> cd mv mv mv mv /FlexFrame/volFF/os/Linux//etc/init.d ./rc3.d/S14sapinit ./rc3.d/s14sapinit ./rc3.d/K08sapinit ./rc3.d/k08sapinit ./rc5.d/S14sapinit ./rc5.d/s14sapinit ./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. Installation Guide for SAP Solutions 91 Installing SAP 7.1 13 Installing SAP 7.1 We only show the different behaviour of the installation in comparison to NetWeaver 2004s SR3. With SAP 7.1 the SAP system contains its own JVM and you do not set your environment to use SDK from SUN/Novell. 1. Introduction All Platforms (see chapter 10) 2. Install DB service 3. Setting virtual DB host All platforms (see chapter 18.1.2) 4. Install ASCS instance 5. Setting virtual ASCS host All platforms (see chapter 18.1.5) 6. Install CI service 7. Setting virtual CI host All platforms (see chapter 18.1.1) 8. Install Application service 9. Setting virtual Application host All Platforms (see chapter 18.1.3) 10. Install ERS instance (optional) All Platforms (see chapter 13.3 ) Installation Issues Service cannot be started (see chapter 13.2 ) Installation Issues (optional) EHP installer issues (see chapter 13.3 ) 13.1 Creating a New SID Using ff_sid_adm.pl Specifying a new SID by ff_sid_adm.pl you can use a simplified syntax : ff_sid_adm.pl --op add --pool pool1 –-sid S07 --sapversion 7.1 --db MaxDB77:159 --sap ci:57:157:157 --sap ascs:55:155:155 --sap app:58:158:158 --sap ascs:56:156:156 92 Installation Guide for SAP Solutions Installing SAP 7.1 The virtual server names are follow a specific syntax. ff_sid_adm.pl determines it by itself and you do not need to specifiy it 13.2 Service Cannot Be Started The installer tries to start the services. Sometimes this start request fails. StartService FAIL: Service definition not found in /usr/sap/sapservices. WARNING[E] 2008-09-25 11:57:34.812 CJS-30223 Could not start instance service of instance M06/ASCS04 Please logon as 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 and rename the profiles. Change the physical hostname to the virtual hostname (if available), e.g. mv mv mv mv .dbenv_jer1bx1.sh .dbenv_jer1bx1.csh .dbsrc_jer1bx1.sh .dbsrc_jer1bx1.csh .dbemv_cim06.sh .dbemv_cim06.csh .dbsrc_dbm06-se.sh .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. Installation Guide for SAP Solutions 93 Installing SAP 7.1 If using JAVA engine you have to make sure that all JAVA processes are running before continuing installation. You can check it by /usr/sap/M06/DVEBMGS00/exe/sapcontrol -prot NI_HTTP –nr 00 -function GetProcessList 01.10.2008 14:39:32 GetProcessList OK name, description, dispstatus, textstatus, starttime, elapsedtime, pid disp+work, Dispatcher, GREEN, Running, Message Server connection ok, Dialog Queue time: 0.00 sec, AS Java: All processes running, 2008 10 01 14:33:50, 0:05:42, 29434 rslgcoll, Central Syslog Collector, GREEN, Running, 2008 10 01 14:33:50, 0:05:42, 29435 rslgsend, Central Syslog Sender, GREEN, Running, 2008 10 01 14:33:50, 0:05:42, 29436 igswd_mt, , GREEN, Running, 2008 10 01 14:33:50, 0:05:42, 29437 jer1bx5:~ # With SLES9 you have to start sapcontrol under control of user adm. 13.3 EHP Installer Issues 13.3.1 Mandatory SMD installation request With SAP 7.1 EHP1 the SAP installer requests an additional SMD-instance (Solution Manager Diagostic Agent) to monitor a SAP service, e.g. CI. More information about the Diagnostic Agent can be found in the corresponding SAP documents. The SMD instance must be part of a different SID specification. You cannot use the SID of the current installation. We recommend you to specify an additional SID which should contain the requested SMD instances. You can use that SID for all SMD instance requests depending on restrictions like the range of instance numbers. Please take into account that the SMD instance has to run on the same host as the monitored SAP instance. With FlexFrame 5.0 we fully support services of type SMD (release 7.1). If you have used SMD with older versions we recommend to update to the most current version of SMD and update your LDAP database to the new requirements. We recommend using the range of DAA to DAZ for the . But you are free to use another range. 94 Installation Guide for SAP Solutions Installing SAP 7.1 13.3.2 EHP Installer Requests Entries in /etc/services Some EHP installers complain: ERROR> You have to login sapgwxx in /etc/services number 33xx: ERROR> You have to login sapdpxx in /etc/services number 32xx as root and enter the shadow gateway instance with as root and enter the shadow dispatcher instance with We recommend you to introduce the requested ports into /etc/services for the installation procedure. After the installation is finished remove the entries from the file. 13.3.3 EHP Installer – JAVA process cannot be started During installation the start of instances (CI, Dialog Instances) does not finish (JAVA processes do not start). You will see a message box like below Installation Guide for SAP Solutions 95 Installing SAP 7.1 To solve the problem: 1. Stop the instance and modify SAP system parametes using configuration tool. AN> cd /usr/sap///j2ee/configtool AN> ./configtool.sh 96 Installation Guide for SAP Solutions Installing SAP 7.1 2. Change VM parameter java.security.egd to file /dev/./urandom like below and click on the Set button: Please take care for the dot in the path name. Installation Guide for SAP Solutions 97 Installing SAP 7.1 3. 98 Click on the diskette symbol to save and restart instance: Installation Guide for SAP Solutions Installing SAP 7.1 13.4 ERS 13.4.1 Installation hints With SAP 7.1 the installation process of ERS is integrated in SAP GUI. If you install ERS you have to install an ERS instance for ASCS and SCS separably. The screenshots below show you the installation part for ASCS instance. cd usr/sap/M02/install/ers01 /mnt/sapcds/Sap_7.1_PI_Sol_Maxdb/Installation/DataUnit/IM_LINUX_X86_64_ADA/sapinst –extract ./sapinst SAPINST_USE_HOSTNAME=ers01m06 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 -p -n ers For the virtual IP you can use the IP of the physical host used for the installation. Installation Guide for SAP Solutions 99 Installing SAP 7.1 100 Installation Guide for SAP Solutions Installing SAP 7.1 1. Change the ERS instance number. 2. If you get the following message box 2.1 Click on Cancel 2.2 Start the instance by ff_service.sh –t ers –s M02 –i 01 –a start 2.3 Change the status value in keydb.xml from ERROR to OK. Installation Guide for SAP Solutions 101 Installing SAP 7.1 3. If you have an ERS instance for SCS you have to do the same procedure like in step 2. 13.4.2 Post Installation Tasks (SAP 7.1 only) After the installation is completed you remove the host definitions in LDAP by CN1: ff_hosts.sh -p -r ers 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 (_ERS_) and exchange the string if necessary 102 Installation Guide for SAP Solutions Installing SAP 7.3 14 Installing SAP 7.3 SAP 7.3 may be used with ORACLE 11, MAXDB 7.8 and DB2 9.7 only. From SAP 7.1 on the SAP system contains its own JVM and you do not need to set your environment to use SDK. 1. Introduction All Platforms (see chapter 10) 2. SAP 7.3 EHP1 – Oracle ASM Setting up users and groups (see chapter 14.4) 3. Install DB service 4. Setting virtual DB host All platforms (see chapter 18.1.2) 5. Install SCS/ASCS instance All Platforms (see chapter 14.2) 6. Setting virtual ASCS host All platforms (see chapter 18.1.5) 7. Install CI service 8. Setting virtual CI host All platforms (see chapter 18.1.1) 9. Install Application service 10. Setting virtual Application host All Platforms (see chapter 18.1.3) 11. Install optional ERS (SAP 7.3) All Platforms (see chapter 14.3) 12. Install ERS instance (optional) All Platforms (see chapter 13.3 ) 13. Installation Issues Service cannot be started (see chapter 13.2 ) 14. Installation Issues (optional) EHP installer issues (see chapter 13.3 ) Installation Guide for SAP Solutions 103 Installing SAP 7.3 14.1 Creating a New SID Using ff_sid_adm.pl Specifying a new SID by ff_sid_adm.pl you can use a simplified syntax: ff_sid_adm.pl --op add --pool pool1 –-sid M02 --sapversion 7.3 --db MaxDB78:159 --sap ci:57:157:157 --sap scs:04:155:155 --sap app:58:158:158 --sap ascs:04:156:156 The virtual server names are following a specific syntax. ff_sid_adm.pl determines it by itself and you do not need to specifiy it 14.2 SCS/ASCS (SAP 7.3) 14.2.1 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 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 104 Installation Guide for SAP Solutions Installing SAP 7.3 After modifying the filenames they have to look like this:bx91-11:m02adm 17> ls –al | grep scs -rw-r—r 1 m02adm sapsys … .j2eeenv_ascsm02.csh -rw-r—r 1 m02adm sapsys … .j2eeenv_ascsm02.sh -rw-r—r 1 m02adm sapsys … .j2eeenv_scsm02.csh -rw-r—r 1 m02adm sapsys … .j2eeenv_scsm02.sh -rw-r—r -rw-r—r -rw-r—r -rw-r—r 1 1 1 1 m02adm m02adm m02adm m02adm sapsys sapsys sapsys sapsys … … … … .sapenv_ascsm02.csh .sapenv_ascsm02.sh .sapenv_scsm02.csh .sapenv_scsm02.sh -rw-r—r -rw-r—r -rw-r—r -rw-r—r 1 1 1 1 m02adm m02adm m02adm m02adm sapsys sapsys sapsys sapsys … … … … .sapsrc_ascsm02.csh .sapsrc_ascsm02.sh .sapsrc_scsm02.csh .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 -D -u m02admto LD_LIBRARY_PATH=/usr/sap/M02/SCS03/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/M02/SCS03/exe/sapstartsrv pf=/usr/sap/M02/SYS/profile/M02_SCS03_scs -D -u m02adm In /sapmnt//profile/DEFAULT.PFL change the entry j2ee/scs/host = ascs to j2ee/scs/host = scs In the directory /sapmnt//profile change the filename _SCS03_ascs to Installation Guide for SAP Solutions _SCS03_scs. 105 Installing SAP 7.3 In the file /sapmnt//profile/ _SCS03_scs change ‗ascs’ to ‗scs’ . 14.3 ERS 14.3.1 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 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 -p -n ers For the virtual IP you cann use the IP of the physical host used for the installation. 106 Installation Guide for SAP Solutions Installing SAP 7.3 Installation Guide for SAP Solutions 107 Installing SAP 7.3 4. Change the ERS instance number. 5. If you get the following message box 5.1 Click on Cancel 5.2 Start the instance by ff_service.sh –s m02 –t ers –i 01 –a start 5.3 Change the status value in keydb.xml from ERROR to OK. 108 Installation Guide for SAP Solutions Installing SAP 7.3 6. If you have an ERS instance for SCS you have to do the same procedure like in step 2. 14.3.2 Post Installation Tasks After the installation is completed you remove the host definitions in LDAP by CN1: ff_hosts.sh -p -r ers 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 (_ERS_) and exchange the string if necessary 14.4 SAP 7.3 EHP1 The ‗sapinst‘ offers the options to use Oracle ASM. Whatever you chose the installation script always tries to create user ‗oracle‘ group ‗asmadmin‘ group ‗asmdba‘ group ‗asmoper‘ group ‗oinstall‘ Before you start your installation you have to create this user and these groups executing ff_user_adm.pl –op add –pool --home /home_sap/oracle --user oracle uid --pass ff_group_adm.pl –op add –pool --name –guid \ --member oracle ff_user_adm.pl –op mod –pool --user oracle –group oinstall Installation Guide for SAP Solutions 109 Installing SAP 7.3 14.5 SAP 7.3 – Linux kernel issue There are some requirements concerning patchlevel of SAP software with specific Linux kernel releases. The start of SAP services may fail after upgrading to a newer OS image. The behaviour is caused by SAP components which are not at the most current patch level. Please refer to SAP-Note 1629558 which describes the required patch levels for the corresponding components. The SAP-Note 1310037 describes only a shortterm solution. It could affect other services. 110 Installation Guide for SAP Solutions Install nonclassic SAP services 15 Install nonclassic SAP services Before starting with the Installation of SAP services on FlexFrame, please refer to the original SAP installation guides. Please also get the applicable SAP notes from the SAP Marketplace. This document will not cover the complete SAP installation process. It shows you only the differences due to FlexFrame specifics. Beside classic SAP services, SAP supplies a number of additional services and Addons which are different in the configuration requirements from classic services. So the installation procedure changes from one service to another. FlexFrame now supports some additional nonclassic services. These services are BOBJ – Business Objects Enterprise 3.1/3.2/4.0 CMS – Content Server 6.40 MDM – Master Data Management 7.1 SMD – Solution Manager Diagnostics 7.1 TREX – Search and Classification 7.1 15.1 BOBJ – Business Objects Enterprise BOBJ is an Addon services which cannot be installed by sapinst. It has its own installation scripts. From the FlexFrame perspective it simply needs some configuration data like a classic SAP service within FlexFrame. FlexFrame only supports the standard SAP installation using mySQL database (BOBJ 3.x) or IBM DB2 (BOBJ 4.0) for storing BOBJ metadata. It also expects a Tomcat installation as offered with installation script. All other configurations are handled as project solutions. BOBJ is installable within FlexFrame environment. From our point of view there is no technical reason why it should not work with FlexFrame. But there is a SAP Note 1703318 which contains some hints about operating BOBJ within virtualized environments. We strongly recommend you to ask professional service if there are restrictions (defined by SAP) using BOBJ which are not mentioned int the SAP Note. This chapter does not cover a complete installation description. If there are specific questions about installation procedure, e.g. usage of port numbers, please refer to the origin documentation supplied by SAP. Installation Guide for SAP Solutions 111 Install nonclassic SAP services A BOBJ installation consists of one client instance with the hostname bobj. Please follow the main steps shown in the table below: 1. Installation preperations see chapter 15.1.1 2. Install BOBJ BOBJ 3.x: see chapter 15.1.2 BOBJ 4.0: see chapter 15.1.3 3. Post installation see chapter 15.1.4 15.1.1 BOBJ – preparations Specify the new service either for the initial installation with the Management-Tool or use ff_sid_adm.pl and setup the directory structures using ff_setup_sid_folder.sh. CN: ff_sid_adm.pl --op add --pool –-sid BOB --sapversion 3.2 --bobj CN: ff_setup_sid_folder.sh –s BOB –p On installation node you Stop the myAMC agents. Start interface by ff_service.sh –t bobj –s -a istart. Set hostname by hostname bobj. Copy .cshrc, hostname and hostname_default from an other SAP installation to /home_sap/adm. Set bobj in hostname_default Add setenv LC_ALL en_US.utf8 to /home_sap/adm/.cshrc. Set bobj in the file hostname_default of user adm. On the control node you add the IP address of bobj to pool specific /FlexFrame/volFF/os/Linux/pool_img//etc/hosts file. 15.1.2 BOBJ – installation – 3.x To install the software you login to adm and Execute cd /usr/sap/ 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 /install.sh to install BOBJ. 112 Installation Guide for SAP Solutions Install nonclassic SAP services 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/.ini on application node which contains your own password string. That password file is only considered if the shutdown request is initiated from FA monitoring software. Install the latest patches (search at http://service.sap.com/swdc). Download the corresponding process explorer (Polestar) from SAP software download site Execute /Polstar/install.sh /usr/sap/. 15.1.3 BOBJ – Installation – 4.0 SAP renamed the old BOBJ to SBOP (SAP Business Objects BI Platform). We still use ‗BOBJ‘ as service type. Before you start the installation you have to request a valid licence key (needed in installation script). Testlicenses for the installation purpose can be downloaded from the SAP marketplace. After it you login as adm to install the software by executing ―/…/BusinessObjectsServer_linux/setup.sh InstallDir=/usr/sap/‖ . Instead of using mySQL to store metadata BOBJ 4.0 uses an IBM DB2 database as default (created with full installation automatically). FlexFrame only supports that default configuration. install the latest patches (search at http://service.sap.com/swdc). download the corresponding process explorer (Polestar; it is renamed to SBOP Explorer) from SAP software download site. execute ―/…/Explorer_linux/setup.sh InstallDir=/usr/sap/" to install SBOP Explorer. Installation Guide for SAP Solutions 113 Install nonclassic SAP services 15.1.4 BOBJ – post installation To install the software you login to 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 -a istop Restart myAMC agents 15.1.5 BOBJ – Login to CMC (Central Management Console) You can login to CMC after completion of installation to setup your own environment. To get the login screen you start your browser and connect to http://bobj:8080/CmcApp/logon.faces (BOBJ 3.x) http://bobj:8080/BOE/CMC (BOBJ 4.x) If you will not get the login screen with the system string ‗bobj:‘ you have to change ‗bobj‘ 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. 114 Installation Guide for SAP Solutions 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/. During installation with sapinst you are, may be, aks for two CMS specific users, ‗sapcs‘ and ‗sapcsc‘ FlexFrame installs the users ‘cs‘ and ‘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-se a client instance, hostname cms Installation Guide for SAP Solutions 115 Install nonclassic SAP services Please follow the main steps shown in table below: 1. Installation preperations see chapter 15.2.1 2. Install http server see chapter 15.2.2 3. Install CMS see chapter 15.2.3 4. Post installation see chapter 15.2.4 15.2.1 CMS – preparations Specify new services either for the initial installation by Management-Tool or using ff_sid_adm.pl and setup directory structures using ff_setup_sid_folder.sh for later installations. CN: ff_sid_adm.pl --op add --pool –-sid CMS --sapversion 6.40 --db maxdb76: –cms CN: ff_setup_sid_folder.sh –s CMS –p On the installation node you Stop the myAMC agents Set interface by ff_service.sh –t cms –s -a istart 15.2.2 CMS – http server installation Download http server software (e.g. http-2.2.14.tar) and do the installation cd / call ‗./configure –with-expat=builtin –prefix /usr/sap‘ call ‗make‘ call ‘make install‘ 15.2.3 CMS – installation To install the software you login to adm and execute cd /usr/sap/ mkdir /usr/sap//install/db cd /usr/sap//install/db /sapinst -extract # Prepare userprofile /home_sap/adm/.cshrc source $HOME/.dbenv.csh or source $HOME/.dbenv_`hostname`.csh 116 Installation Guide for SAP Solutions Install nonclassic SAP services # Logon to adm and create XUSER by ‗xuser –d -n db-se –u Control,control –U c –S SAPR3 –t0 –I 0‘ 15.2.4 CMS – post installation If the installation procedure is finished you Modify /usr/sap//conf/http.conf ● ServerRoot "/usr/sap/" ● DocumentRoot "/usr/sap//htdocs ● Directory "/usr/sap//htdocs ● ScriptAlias /cgi-bin "/usr/sap//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 -a istop 15.2.5 CMS - Migration from project specific solutions CMS 6.40 is integrated now in FlexFrame 5.0. With previous releases there are project specific installations which should be migrated to the new environment. We will give you some hints how to migrate, but dependeng on the project specific environment more or less steps could be necessary. Usually you should execute the following tasks Read the properties of the SID created in project specific approach by ‗ff_sid_adm.pl –op list-all …‘. Note the instance numbers and IP addresses from the client and server lan interface. Don‘t forget to note the hostnames used in project‘s solution. Read the properties of the SID specific users by ‗ff_user_adm.pl –op list …‘. Users are adm and the users depending on databased used (ora, sqd, etc.) Note the unique UID of the user. If you have introduced CMS cache users please get also the data of cs and scs (respective the user names you defined) Stop the monitoring of the service specific services using ‗ff_service.sh … -a nowatch‘ Installation Guide for SAP Solutions 117 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 :: …‘ Do not forget to specify a corresponding client interface using option ‗—cms ‘. Create aliases with the old hostnames noticed before by ‗ff_hosts.sh –p a -n ‘ for the hostnames used with CMS 6.40 project approach. 15.3 MDM – Master Data Management MDM is a SAP service which consist of a special database and some services. The database itself cannot be installed with classic SAP tools like ‗sapinst‘. The database installation is done using the installation tools supplied by the database vendor or SAP (see below). A MDM installion consists of a classic database service, hostname ‗db-se‘ one or more instances of type ‗mds‘, hostname ‗mds‘ and ‗mds-se‘ one or more instances of type ‗mdss‘, hostname ‗mdss‘ and ‗mdss-se‘ one or more instances of type ‗mdis‘, hostname ‗mdis‘ and ‗mdis-se‘ Please follow the main steps shown in table below: 1. Installation preperations see chapter 15.3.1 2. Iinstall database see chapter 15.3.2 3. Install MDM see chapter 15.3.3 4. Post installation see chapter 15.3.4 15.3.1 MDM – 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. 118 Installation Guide for SAP Solutions 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 –-sid MDX --sapversion 7.1 --db : -–mdm mds::: --mdm mdis::: --mdm mdss::: CN: ff_setup_sid_folder.sh –s MDX –p CN: # Optionally you should create MDM specific groups if necessary CN: ff_group_adm.pl –op add –pool --name DB2ADMNS_MDM [ --guid nnnn ] CN: ff_group_adm.pl -op add -pool --name DB2USERS_MDM [ --guid mmmm ] On installation node you Stop the myAMC agents Start the interface by ff_service.sh –t db –s -a istart Start the interface by ff_service.sh –t istart mds –s Start the interface by ff_service.sh –t istart mdis –s -i -a Start the interface by ff_service.sh –t istart mdss –s -i -a -i -a 15.3.2 MDM – Database installation MDM can use each type of database Oracle MaxDB DB2 The installation of the database is not part of the SAP installation process. The database software has to be installed manually. 15.3.2.1 Oracle To install the Oracle database software you have to Installation Guide for SAP Solutions 119 Install nonclassic SAP services Modify /etc/orainst.loc inventory_loc=/oracle//oraInventory inst_group=dba chown –R ora:dba /oracle/ login from Control Node to ssh –X -l ora set environment of ora setenv ORACLE_HOME /oracle// setenv ORACLE_SID setenv ORACLE_BASE /oracle/ in .dbenv.sh cd /oracle/stage//database/SAP ./RUNINSTALLER Configure Listener (_LISTENER with Oracle‘s netca Modify /FlexFrame/vollFF/pool/pooldata/config/…/ora_listener_names on Control Node, insert: MDC:MDC_LISTENER Copy files from home_sap/adm/csh*‟ , „/home_sap/adm/.dbenv.csh‟ , „/home_sap//.sapenv.csh to /oracle/ In the files .cshrc and .dbenv.* you have to set the SID to the SID of your MDM database installation. 15.3.2.2 MaxDB To install the MaxDB database software you have to Start SDBSETUP from SAP installation media to install server and client software Follow the instructions of the installation GUI. For further details please use in the corresponding SAP installation guide for MDM Create /home_sap/adm/hostname and /home_sap/adm/hostname_default (or copy it from an existing installation) Create a link in /home_sap/adm ‗ln –s .mdmdbenv.csh .dbenv.csh ‗ and ‗ln –s .mdmdbenv.sh .dbenv.sh‘ Insert ‗set dbms_type=ADA‘ into /home_sap/adm/.mdmdbenv.csh if not available Insert ‗source $HOME/.mdmdbenv.csh‘ into .cshrc if not available 120 Installation Guide for SAP Solutions Install nonclassic SAP services Create an alias for default database user dbm /sapdb(programs/bin/xuser -d -n dbmdm-se -u dbm, -U c_J2EE -S SAPR3 -t 0 -I 0 15.3.2.3 DB2 To install the DB2 database software and to create a DB2 database please refer to the corresponding SAP documentation. You will find the document SAP NetWeaver MDM 7.1 with IBM DB2 for Linux, …‖ at http://service:sap.com/installMDM71. This document refers to DB2 V9.1 and V9.5. But it is also valid for DB2 V9.7. The installation in FlexFrame4SAP is like an central server installation. With FlexFrame there are some installation tasks which differ from the SAP document. Set the home directory of db2 to /home_sap/db2 For the DAS user you can use the predefined user ‗dasusr1‘ After the installation of the database software, create a link for db2ls (see chapter 16.7.1) Insert ‗setenv dbms_type db6‘ and‘ setenv DB2INSTANCE db2‘ to the /home_sap/sid/.cshrc Extend the variable PATH by /home_sap/db2//bin and /home_sap/db2//adm Create the database as described in SAP document Copy .dbenv* from another (DB2) installation to /home_sap/db2 and create a link for .mdmdbenv_.csh or rename the environment files. Make the changes described in SAP document Install licenses using db2licm under control of user root. Modify the DB2 catalog, see chapter 16.7.6.2 15.3.3 MDM – installation The installation of the three different types differs only in the selection menus of sapinst and the usage of the server hostname. So we describe here only the installation of type mds. After each type you should virtualize the environment files of user adm. To install the software you login to adm and execute cd /usr/sap/

Installation Guide For Sap Solutions

Rating

Date

Size

Views

Categories

Share

Transcript

Forgot your password?.