›

Bài giảng SAP Basis Installation on UNIX: Oracle Database

pdf 236 trang huongle 7810
Download
Bạn đang xem 20 trang mẫu của tài liệu "Bài giảng SAP Basis Installation on UNIX: Oracle Database", để tải tài liệu gốc về máy bạn click vào nút DOWNLOAD ở trên

Tài liệu đính kèm:

  • pdfbai_giang_sap_basis_installation_on_unix_oracle_database.pdf

Nội dung text: Bài giảng SAP Basis Installation on UNIX: Oracle Database

  1. SAP Basis Installation on UNIX: Oracle Database Release 4.6D SAPđ AG • Neurottstr. 16 • D-69190 Walldorf 51 010 92 7
  2. SAP Basis Installation on UNIX: Oracle Database SAP AG Copyright âCopyright 2000 SAP AG. All rights reserved. No part of this brochure may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoftđ, WINDOWSđ, NTđ, EXCELđ, Wordđ and SQL Serverđ are registered trademarks of Microsoft Corporation. IBMđ, DB2đ, OS/2đ, DB2/6000đ, Parallel Sysplexđ, MVS/ESAđ, RS/6000đ, AIXđ, S/390đ, AS/400đ, OS/390đ, and OS/400đ are registered trademarks of IBM Corporation. ORACLEđ is a registered trademark of ORACLE Corporation, California, USA. INFORMIXđ-OnLine for SAP and Informixđ Dynamic Server are registered trademarks of Informix Software Incorporated. UNIXđ, X/Openđ, OSF/1đ, and Motifđ are registered trademarks of The Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3Cđ, World Wide Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of Technology, 545 Technology Square, Cambridge, MA 02139. JAVAđ is a registered trademark of Sun Microssystems, Inc. , 901 San Antonio Road, Palo Alto, CA 94303 USA. JAVASCRIPTđ is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. ADABASđ is a registered trademark of Software AG. SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit, SEM, SAP DB are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. Documentation in the SAP Service Marketplace You can find this documentation at the following address: 2 July 2000
  3. SAP AG SAP Basis Installation on UNIX: Oracle Database Typographic Conventions Type Style Represents Interface Text Words or characters that appear on the screen. This includes system messages, field names, screen titles, pushbuttons, menu names, and menu options. Document Title Cross-references to other documentation User Entry Exact user entry. These are words and characters that you enter exactly as they appear in the documentation. File Name File names, batch files, paths or directories, and screen messages replace these words and characters with appropriate entries. NAME Names of elements in the SAP System. These include report names, program names, transaction codes, table names, and ABAP language elements. KEY Keys on your keyboard. These include function keys (for example, F2) and the ENTER key. Icons Icon Meaning Caution Example Note Recommendation Syntax Tip July 2000 3
  4. SAP Basis Installation on UNIX: Oracle Database SAP AG SAP Basis Installation on UNIX: Oracle Database 10 Part I Standard SAP System Installation 13 1 Installation Planning 17 1.1 System Configuration 17 1.2 Distribution of Components to Disks 19 1.2.1 Recommended Configuration 22 1.2.2 Minimal Configuration 22 1.2.3 SAP File Systems 23 1.2.4 Oracle File Systems 26 1.3 Hardware and Software Requirements Check 28 1.3.1 Checking Requirements for a Central System 30 1.3.2 Checking Requirements for a Standalone DB System 31 1.3.3 Checking Requirements for a Central or Dialog Instance 32 1.3.4 Checking Requirements for AIX 33 1.3.5 Checking Requirements for Compaq Tru64 UNIX 36 1.3.6 Checking Requirements for HP-UX 39 1.3.7 Checking Requirements for Linux 42 1.3.8 Checking Requirements for Reliant (RM300/400/600) 44 1.3.9 Checking Requirements for IBM NUMA-Q 46 1.3.10 Checking Requirements for Solaris 47 2 Installation Preparations 50 2.1 Adapting UNIX Kernel Parameters and Swap Space 51 2.2 Integration of LDAP Directory Services 52 2.2.1 Preparing the Active Directory for SAP 54 2.3 Choosing an SAP System Name 55 2.4 Setting Up File Systems and Raw Devices 56 2.5 Setting Up the Transport Directory 56 2.6 Setting Up an Installation Directory 58 3 The SAP System Installation 59 3.1 Central System Installation 61 3.1.1 SAP Instance Installation for a Central System 62 Mounting the Kernel CD-ROM 63 Running the Shell Script INSTTOOL.SH 63 Customizing the Installation Command File 63 Configuring Tablespaces 64 Starting INSTGUI 64 Setting the Library Path Environment Variable 65 Running R3SETUP for Central System Installation 66 4 July 2000
  5. SAP AG SAP Basis Installation on UNIX: Oracle Database Setting the Password for User adm 68 Creating User for LDAP Directory Access 68 Checking Settings for OS Users (AIX only) 68 3.1.2 Oracle Database Instance Installation 69 Required CD-ROMs for Database Installation 70 Mounting the Kernel CD-ROM 70 Setting the Password for User ora 70 Starting the Script rootpre.sh (AIX only) 71 Oracle DB Software Installation 71 Installing the Oracle DB Software with orainst 72 Installing the Oracle DB Software with runInstaller 74 Creating and Loading the Database with R3SETUP - Central Instance with DB 77 Updating the MNLS Tables 77 Running R3SETUP for RFC Installation 78 3.2 Standalone DB System Installation 79 3.2.1 SAP Instance Installation for a Standalone DB 80 Mounting the Kernel CD-ROM 81 Running the Shell Script INSTTOOL.SH 81 Customizing the Installation Command File 81 Configuring Tablespaces 82 Starting INSTGUI 82 Setting the Library Path Environment Variable 83 Running R3SETUP for Central Instance Installation 84 Setting the Password for User adm 86 Setting the Password for User ora 86 Creating User for LDAP Directory Access 86 Checking Settings for OS Users (AIX only) 86 3.2.2 Oracle Standalone Database Instance Installation 87 Required CD-ROMs for Database Installation 89 Mounting the Kernel CD-ROM 89 Running the Shell Script INSTTOOL.SH 89 Starting INSTGUI 89 Setting the Library Path Environment Variable 90 Running R3SETUP for Database Instance Installation 91 Setting the Password for User adm 91 Setting the Password for User ora 91 Checking Settings for OS Users (AIX only) 92 Starting the Script rootpre.sh (AIX only) 92 Oracle DB Software Installation 92 Installing the Oracle DB Software with orainst 93 Installing the Oracle DB Software with runInstaller 95 Creating and Loading the Database with R3SETUP - Standalone DB 98 Updating the MNLS Tables 98 Running R3SETUP for RFC Installation 99 Enabling Remote Monitoring 99 July 2000 5
  6. SAP Basis Installation on UNIX: Oracle Database SAP AG 3.3 Dialog Instance Installation 101 3.3.1 Mounting Directories from the Central Instance 102 3.3.2 Checking the File System for the Client Software 103 3.3.3 Mounting the Kernel CD-ROM 103 3.3.4 Running the Shell Script INSTTOOL.SH 103 3.3.5 Customizing the Installation Command File 103 3.3.6 Starting INSTGUI 104 3.3.7 Setting the Library Path Environment Variable 104 3.3.8 Running R3SETUP for Dialog Instance Installation 105 3.3.9 Setting the Password for User adm 105 3.3.10 Setting the Password for User ora 106 3.3.11 Checking Settings for OS Users (AIX only) 106 3.3.12 Checking the Default Profile 106 3.3.13 Using startsap/stopsap Aliases 106 3.3.14 Activating sapcpe 107 3.4 Gateway Instance Installation 110 3.4.1 Mounting the Presentation CD-ROM 111 3.4.2 Running the Shell Script for a GW Installation 111 3.4.3 Customizing the Installation Command File 111 3.4.4 Starting INSTGUI 111 3.4.5 Setting the Library Path Environment Variable 112 3.4.6 Running R3SETUP for Gateway Instance Installation 112 3.4.7 Setting the Password for User adm 113 3.4.8 Checking Settings for OS Users (AIX only) 113 3.4.9 Configuring the SNA Communication Software 113 3.5 Additional Component Installation 114 3.5.1 Mounting the Presentation CD-ROM 115 3.5.2 Running the Shell Script for Additional Components 115 3.5.3 Starting INSTGUI 115 3.5.4 Running R3SETUP for Additional Component Installation 115 3.5.5 Installing Lotus Script Extension for SAP Systems 116 4 Post-Installation Activities 117 4.1 Starting and Stopping the SAP System 118 4.2 Logging on to the SAP System 120 4.3 Checking SAP System Services 121 4.4 Installing and Using the SAP License 121 4.5 Performing Operating System Adjustments 123 4.6 Performing File and Directory Adjustments 123 4.7 Installing the Online Documentation 123 4.8 Configuring SAProuter and SAPNet - R/3 Frontend 124 4.9 Completing and Checking the Oracle Installation 125 4.10 Performing a Full Backup of the Installation 127 4.11 SAP Internet Solution Installation 128 6 July 2000
  7. SAP AG SAP Basis Installation on UNIX: Oracle Database 5 The R3SETUP Tool 129 5.1 INSTGUI 131 5.2 R3SETUP Command Files 133 5.3 R3SETUP Messages 134 5.4 Using R3SETUP Online Help 135 5.5 Continuing an Interrupted Installation 136 5.6 Monitoring a Remote Installation 136 6 Additional Information 138 6.1 Installation Troubleshooting 138 6.1.1 Common Installation Troubleshooting 139 6.1.2 R3SETUP Troubleshooting 139 6.1.3 Database Installation Troubleshooting 140 6.2 Deletion of an SAP System Installation 143 6.2.1 Deleting a Dialog Instance 143 6.2.2 Deleting a Central Instance 145 6.2.3 Adapting the Configuration Description File 146 6.3 Deleting an Oracle Database Installation 147 6.4 Database Modifications for Very Large Databases 148 6.4.1 Configurations for Redo Log I/O 149 6.4.2 Separating Big Tables (Table Striping) 151 6.4.3 Enlarging/Moving the Redo Logs 153 6.4.4 Installing Additional Rollback Segments 154 6.4.5 Enlarging Rollback Segments 155 July 2000 7
  8. SAP Basis Installation on UNIX: Oracle Database SAP AG Part II OS-Dependent Installation Steps on UNIX 156 7 Network Information Service Environment 157 8 Preparations 159 8.1 AIX: Preparing the Installation 159 8.2 ReliantUNIX: Preparing the Installation 159 8.3 IBM NUMA-Q: Preparing the Installation 160 8.4 Solaris: Preparing the Installation 160 9 Mounting a CD-ROM 161 9.1 AIX: Mounting a CD-ROM 161 9.2 Compaq: Mounting a CD-ROM 162 9.3 HP-UX: Mounting a CD-ROM 163 9.4 Linux: Mounting a CD-ROM 164 9.5 ReliantUNIX: Mounting a CD-ROM 164 9.6 IBM NUMA-Q: Mounting a CD-ROM 165 9.7 Solaris: Mounting a CD-ROM 165 10 Checking and Modifying the UNIX Kernel 166 10.1 Compaq: Checking and Modifying the UNIX Kernel 166 10.2 HP-UX: Checking and Modifying the UNIX Kernel 168 10.3 Linux: Checking and Modifying the Linux Kernel 171 10.4 ReliantUNIX: Checking and Modifying the UNIX Kernel 172 10.5 IBM NUMA-Q: Checking System and Kernel Parameters 176 10.6 Solaris: Checking and Modifying the UNIX Kernel 178 11 File Systems, Raw Devices and Swap Space 181 11.1 AIX: Volume Groups, File Systems, Raw Devices, Swap Space 182 11.1.1 AIX: Size of a Logical Partition 182 11.1.2 AIX: Setting up Swap Space 182 11.1.3 AIX: Creating Volume Groups 183 11.1.4 AIX: Setting up File Systems 184 11.1.5 AIX: Setting up Raw Devices 185 11.2 Compaq: File Systems, Raw Devices and Swap Space 186 11.2.1 Compaq: Preparing Hard Disks 186 11.2.2 Compaq: Setting up Swap Space 189 11.2.3 Compaq: Setting up Standard File Systems 190 11.2.4 Compaq: Setting up Advanced File Systems 191 11.2.5 Compaq: Setting up Raw Devices 192 11.3 HP-UX: File Systems, Raw Devices and Swap Space 194 11.3.1 HP-UX: Setting up Swap Space 194 11.3.2 HP-UX: Setting up File Systems using LVM 195 11.3.3 HP-UX: Setting up File Systems using SAM 198 11.3.4 HP-UX: Accessing Raw Devices 199 8 July 2000
  9. SAP AG SAP Basis Installation on UNIX: Oracle Database 11.4 Linux: File Systems and Swap Space 200 11.4.1 Linux: Preparing Hard Disks 200 11.4.2 Linux: Setting up Swap Space 200 11.4.3 Linux: Setting up Standard File Systems 201 11.5 ReliantUNIX: File Systems, Raw Devices, Swap Space 202 11.5.1 ReliantUNIX: Setting up Swap Space 202 11.5.2 ReliantUNIX: File System 203 11.5.3 ReliantUNIX: Accessing Raw Devices 206 11.6 IBM NUMA-Q: File Systems, Raw Devices, Swap Space 208 11.6.1 IBM NUMA-Q: Preparing Hard Disks 208 11.6.2 IBM NUMA-Q: Setting up Swap Space 209 11.7 Solaris: File Systems, Raw Devices, Swap Space 210 11.7.1 Solaris: Preparing Hard Disks 210 11.7.2 Solaris: Setting up Swap Space 211 11.7.3 Solaris: Creating File Systems 214 11.7.4 Solaris: Accessing Raw Devices 216 12 Mounting Directories via NFS 217 12.1 AIX: Mounting Directories via NFS 217 12.2 Compaq: Mounting Directories via NFS 219 12.3 HP-UX: Mounting Directories via NFS 220 12.4 Linux: Exporting Directories via NFS 222 12.5 ReliantUNIX: Mounting Directories via NFS 223 12.6 Solaris: Mounting Directories via NFS 224 13 Creating UNIX Groups and Users 226 13.1 AIX: Creating UNIX Groups and Users 226 13.2 Compaq: Creating UNIX Groups and Users 228 13.3 HP-UX: Creating UNIX Groups and Users 229 13.4 Linux: Creating Linux Groups and Users 229 13.5 ReliantUNIX: Creating UNIX Groups and Users 230 13.6 IBM NUMA-Q: Creating UNIX Groups and Users 231 13.7 Solaris: Creating UNIX Groups and Users 231 14 Operating System Dependent Troubleshooting 233 14.1 AIX: Troubleshooting 233 14.2 Compaq: Troubleshooting 233 14.3 HP-UX: Troubleshooting 234 14.4 ReliantUNIX: Troubleshooting 234 14.5 IBM NUMA-Q: Troubleshooting 234 14.6 Solaris: Troubleshooting 234 15 Heterogeneous SAP System Installation 235 July 2000 9
  10. SAP Basis Installation on UNIX: Oracle Database SAP AG SAP Basis Installation on UNIX: Oracle Database Purpose This documentation explains how to install the SAP System on a UNIX operating system when your database is Oracle. Throughout this documentation, the term SAP System is the same as SAP Basis System. Also, SAP stands for SAP Basis in terms such as SAP profile or SAP instance. You c an install t he following types of standard SAP Systems: • Central system, in which the centr al ins tance and th e database instance are onsame the hos t m achine • Standalone database system, in whic h the centr al ins tance and the database ins tance are on different hos t m achines You als o ins tall dialog and gateway ins tances and ad diti onal compone nts . The ins tallation of frontends for the SAP System is described separately in the doc um entatInstalling ion SAP Frontend Software for PCs. Read the ins tallation not es before beginning the ins tallation. These not es conta in the m ost recent inf ormation r egarding t he ins tallation, as well as corrections to the ins tallatio n documentatio n. Make sure that you have the most recent ver sion of each no te. You can find the SAP Notes by using SAPNet - R/3 Front end. Table of Installation Notes for UNIX - Oracle Note number Title 31 13 05 SAP Basis Installation on UNIX 31 13 08 SAP Basis Installation on UNIX - Oracle Database 31 13 09 SAP Software on UNIX - OS Dependencies 1 50 23 Init ializing t able TCPDB 4 56 19 R/3 with s everal languages or typefaces Integration The doc umentation SAP Basis Installation on UNIX: Oracle Database is delivered in the follo wing formats: 10 July 2000
  11. SAP AG SAP Basis Installation on UNIX: Oracle Database Formats of the Installation Documentation Format Media Description / Usage PDF Installation Guides CD-ROM, • Online version of the documentation (Acrobat) see the README file in the • root directory for more Searchable information • Suitable for creating additional print-outs PlainHTML Installation Guides CD-ROM, • Platform independent format see the README file in the • HTML directory for more Hyperlinks within the document information • Searchable (if you want to use this feature, a Web server is required) HTMLHelp Installation Guides CD-ROM, • Can only be displayed on Microsoft see the README file in the Windows HTML directory for more • information Hyperlinks within the document • Searchable Depending on your preference and the equipment you have, use the format that best suits your requirements. The information contained within the documentation is the same. Features SAP Installation Tool For a standard SAP System installation, SAP provides the R3SETUP tool. This has a graphical user interface (GUI) called INSTGUI that allows you to watch the progress of the installation and see all messages issued by R3SETUP. You can call online help from the INSTGUI while you perform the installation. You can start INSTGUI on a remote computer if you want. For more information, see The R3SETUP Tool [page 129]. Variables The following table shows variables used throughout this documentation. Variables use throughout this documentation Placeholder Meaning SAP System name in uppercase letters SAP System name in lowercase letters Database name in uppercase letters Database name in lowercase letters Installation directory Directory on which a CD-ROM is mounted Operating system name within a path July 2000 11
  12. SAP Basis Installation on UNIX: Oracle Database SAP AG Log on as user adm and change to the directory /usr/sap/ . If your SAPSID is C11, log on as user c11adm and change to the directory /usr/sap/C11. Change to the directory /UNIX/ . If the CD-ROM is mounted on /sapcd1 and your operating system is AIX, change to /sapcd1/UNIX/AIX_32. Constraints Procedures that do not belong to the standard installation process are covered in other documentation. They include: • Copying an SAP System • Installing standby SAP Systems for high availability purposes (see the SAP Online Help, SAP Library → BC - Basis Components → Computing Center Management System → BC SAP High Availability). The SAP installation tools must only be used in accordance with the instructions and for the purposes described in the SAP System installation documentation. Improper use of the SAP installation tools can damage files and systems already installed. We recommend that SAP System installations only be done by SAP Technical Consultants who are certified for your operating system, your database and the relevant SAP System. This documentation only applies if you are installing an Oracle database with an UNIX operating system. If you do not have a suitable graphical display terminal (that is, X Windows on UNIX, Microsoft Windows NT 4.0 or Windows 95 and 98), you cannot use the INSTGUI. Therefore, certain limitations apply. 12 July 2000
  13. SAP AG SAP Basis Installation on UNIX: Oracle Database Part I Standard SAP System Installation Purpose When you set up an SAP System, you need to install the main components that enable the system to operate. These are the: • Central instance • Database instance • Dialog instances, if required Prerequisites Before you can begin with the installation of the main SAP components, you have to plan the configuration of the system. This involves deciding which components you need and working out how these must be distributed to hosts. Normally an SAP hardware partner can assist you in this task. On the basis of information about the expected workload, set of applications that are to be deployed and number of users, the partner can recommend a feasible configuration. As the system configuration fundamentally influences the installation procedure, it is important to have a clear configuration plan before you start the installation. There are two basic configuration types: • Central System The Central Instance and Database Instance are installed on a single host. Database Server Central Instance July 2000 13
  14. SAP Basis Installation on UNIX: Oracle Database SAP AG • Standalone Database System The Central Instance and Database Instance are installed on two different hosts. Central Database Instance Server The configuration plan must specify whether a central or standalone database system is to be installed and how many dialog instances are required. Once the plan is complete and the required hardware available, you can start with the installation process as summarized in the following. Keep in mind that the process differs, depending on the hardware configuration you have decided to implement. Process Flow The task of installing an SAP System can be subdivided into a number of phases: PlannningPlannning PreparationsPreparations SAPSAP Installation Installation Post-InstallationPost-Installation Activities Activities The following summarizes the actions that have to be performed in each of the phases. 1. In the planning phase, you have to: − Work out how the main system directories are to be distributed to disks in the system Before the installation, it is essential to get an overview of the directories involved and to decide how these can be best distributed to hard disks. An effective distribution takes 14 July 2000
  15. SAP AG SAP Basis Installation on UNIX: Oracle Database into account aspects such as the expected workload, the size of individual components, performance of the system and security of the data. − Check the hardware and software requirements SAP specifies hardware and software requirements for different system configurations in check lists. On the basis of these lists you can determine whether your hardware meets the minimal requirements for your planned configuration and find out which software versions are necessary for the subsequent installation process. For more information, see Installation Planning [page 17]. 2. In the preparations phase, before you run the installation utilities, it is necessary to perform a number of tasks that are a prerequisite for a successful installation: − Adapting UNIX Kernel Parameters and Swap Space − Integrating LDAP Directory Services − Choosing an SAP System Name − Setting up File Systems and Raw Devices − Setup of the Transport Directory − Setting up an Installation Directory For more information, see Installation Preparations [page 50]. 3. In the SAP System installation phase, you have to carry out the steps that are necessary to set up the core components of the SAP System. The installation procedure differs, depending on the planned system configuration. When you set up a central system, all the required steps are performed on the same host. When you set up a standalone database system some actions are carried out on the database host, others on the central instance host. The following summarizes the actions for both configuration types. Actions for central system and standalone database system configuration types: a. Installation of the central and database instance Central System Standalone Database System a) Actions on the central system host: a) Actions on the central instance host: − Run R3SETUP to install the central − Run R3SETUP to install the SAP instance. instance. − Run orainst to install the Oracle b) Actions on the database host: database software. − Run R3SETUP to install the DB instance. − Run R3SETUP for creating and − Run orainst to install the Oracle loading of the database. database software. − Run R3SETUP for creating and loading of the database. July 2000 15
  16. SAP Basis Installation on UNIX: Oracle Database SAP AG b. Installation of the dialog instances When the central and database instance have been installed, you can optionally install one or more dialog instances on further hosts in the system. You have to run R3SETUP to install the dialog instance. c. Installation of a gateway instance or additional components Once the central, database and dialog instances have been set up, you can install a gateway instance or additional components. For more information, see The SAP System Installation [page 59]. 4. In a final post-installation activities phase, you have to perform a number of tasks to complete the installation. Some of these tasks are mandatory, others are optional and serve to activate optional features that may be useful. − Necessary Tasks • Starting and stopping the system • Logging on to the system • Checking SAP System Services • Installing and Using the SAP License • Installing the online documentation • Configuring the SAProuter and SAPNet - R/3 Frontend • Completing and checking the Oracle installation • Configuring the domain controller in the Transport Management System (TMS) • Calling the System Administration Assistant transaction (SSAA) • Configuring the instance profiles after the installation • Performing a full backup of the installation − Optional Tasks • Performing operating system adjustments • Performing file and directory adjustments • Installing the SAP Internet Solution For more information, see Post-Installation Activities [page 117]. 16 July 2000
  17. SAP AG 1 Installation Planning 1.1 System Configuration 1 Installation Planning Purpose Before you begin with the practical installation tasks, it is essential to have a planning phase. in which you make a number of fundamental decisions that influence the subsequent installation procedure. Careful planning is a prerequisite for the successful installation of the system. Process Flow When you plan the installation you have to: • Decide on the optimal configuration for the system • Work out how the software components must be distributed to disks • Make sure that you can meet the hardware and software requirements specified by SAP SAP specifies minimal hardware and software requirements for different system configurations to make sure that a newly installed system performs well. These requirements are summarized in the hardware and software requirements check lists. In your planning stage, it is essential to consult the Hardware and Software Requirements Check [page 28] to find out the requirements and to make sure that they can be met. Read the installation notes before beginning the installation. These notes contain the most recent information regarding the installation, as well as corrections to the installation documentation. See the table of installation notes [10]. 1.1 System Configuration The configuration of the system is generally planned well in advance of the installation together with the hardware vendor. Configuration planning involves deciding whether a central system or standalone database system is to be installed, and how many dialog instances are required. The configuration is worked out with the hardware partner on the basis of sizing information that reflects the system workload. Details such as the set of applications that are to be deployed, how intensively these are to be used, and the number of users enable the hardware vendor to recommend a configuration that performs well. An SAP System consists of a database server, (optional) additional application servers, and a number of frontend computers. The graphic below shows a typical distribution of the instances of an SAP System over several computers. The database server is the computer on which the database is installed. It is named DBSERVER in the graphic. This server can also accommodate the central instance (the SAP instance that includes the message server and enqueue server processes). If the central instance is installed on a separate application server, the database server is called a standalone database server. Additional dialog instances (SAP instances including only dialog, batch, spool, or update processes) are installed on application servers. These servers are named D1 and D2 in the graphic. July 2000 17
  18. 1 Installation Planning SAP AG 1.1 System Configuration It is possible to install an SAP instance exclusively as a standalone gateway (not shown in the graphic). This type of instance does not contain normal work process types (dialog, background, update, enqueue or spool). Only the gateway process (gwrd) is started. If there is an SNA connection to an R/2 System, gateway work processes (gwwp) are also started. You can think of an SAP instance (central or dialog instance, or standalone gateway) as a group of processes that are started and stopped at the same time. Every instance has a two-digit identifier between 00 and 96 that must be unique on a computer. Application Server Database with Server Central Instance SAP Instance (DVEBMGS00) DB Host DBSERVER Host DBSERVER Host Application Server Application Server with one with two Dialog Instance Dialog Instances SAPSAP SAP SAP Host D1 Host D2 Host Host D1 Host Instance D2 Host Instances (D00) SystemSystem (D00+D01) . . . . . . SAP GUI SAP GUI SAP GUI SAP GUI Typical configuration of an SAP System When planning the configuration of your SAP System, consider the following recommendations: • Install only one SAP System per computer. You can install several SAP Systems on the same computer, but, if you upgrade one of them, a new version of the operating system might be required. In this case, you cannot run SAP Systems having different releases on this computer. • Install only one SAP instance per computer. You should only install more instances if the computer has enough RAM available. • Use the same instance number for all instances of an SAP System unless they are installed on the same computer. 18 July 2000
  19. SAP AG 1 Installation Planning 1.2 Distribution of Components to Disks If you plan to install instances of a single SAP System on different hardware platforms, see Heterogeneous SAP System Installations [page 235]. 1.2 Distribution of Components to Disks Purpose The way files are distributed to disk significantly affects system throughput and data security, and must therefore be carefully planned. The best distribution depends on your specific environment and must take into consideration factors such as the size of the components involved, security requirements and the expected workload. A good distribution of files to disks ensures that: • Enough free space is available for system growth • The data is secure • Performance is good When you work out the assignment of components to disks, you first need to get an overview of the main components and their corresponding directories. Then, on the basis of sample configurations and the recommendations provided in this documentation, you can decide which assignment is best for your particular system. • Customer Database Copy If your own database export instead of the standard SAP database export from CD-ROM will be used for the database load, refer to the documentation SAP Basis Homogeneous System Copy. • Very Large Database (VLDB) See Database Modifications for Very Large Databases [page 148] first if you expect one of the following: - A large amount of data (> 40 GB) - A large number of users ( > 300 users) - A large number of daily log files (> 1 GB) - A large number of transactions per hour (> 100,000) Contact a certified installation organization or a basis consultant if you expect to use a very large database. • Oracle Parallel Server (OPS) If you are installing Oracle Parallel Server (OPS), refer to the documentation R/3 Installation on UNIX - Oracle Parallel Server. July 2000 19
  20. 1 Installation Planning SAP AG 1.2 Distribution of Components to Disks Process Flow There is no single solution or any definite rules for the file distribution. To help you work out a good solution that suits your particular environment, the following topics cover important issues concerning Oracle file system configuration. To find a suitable file distribution configuration, check the following topics: • Oracle Redo Log Files • Security Issues • Performance Issues • Different Oracle Systems • Example Configurations • List of required file systems Oracle Redo Log Files There are four groups of Oracle transaction log files (redo log files). By default, each group contains one original and one mirrored redo log file. If you choose mirroring by UNIX, each group will consist of one original redo log file only. • GROUP 101 (redo1) /oracle/ /origlogA/log_g101m1.dbf /oracle/ /mirrlogA/log_g101m2.dbf • GROUP 102 (redo2) /oracle/ /origlogB/log_g102m1.dbf /oracle/ /mirrlogB/log_g102m2.dbf • GROUP 103 (redo3) /oracle/ /origlogA/log_g103m1.dbf /oracle/ /mirrlogA/log_g103m2.dbf • GROUP 104 (redo4) /oracle/ /origlogB/log_g104m1.dbf /oracle/ /mirrlogB/log_g104m2.dbf The log files are periodically written from redo log log_g101m?.dbf to redo log log_tg104m?.dbf and are archived if the file reaches its maximum size (20 MB), provided the database is running in archive log mode. If you consider the sets of Oracle transaction log files • Set A /oracle/ /*logA/log* • Set B /oracle/ /*logB/log* the redo log that is archived and the redo log that is written always belong to different sets. 20 July 2000
  21. SAP AG 1 Installation Planning 1.2 Distribution of Components to Disks For better performance, the following file systems should be located on different disks: /oracle/ /origlogA /oracle/ /mirrlogA /oracle/ /origlogB /oracle/ /mirrlogB Security Issues • For data security reasons, the redo logs should be mirrored on different disks. This can be achieved either by Oracle, by the hardware, or by the operating system. • A production system must run in archive log mode. • If a test system does not run in archive log mode, data written since the last complete backup will be lost after a system crash. Performance Issues • Store database files and redo logs on different disks, and arrange the redo log files as described above. Since the redo logs are written synchronously, they cause more I/O activity than any other database files. • It is possible to store the redo logs on the same disk as /sapmnt or /oracle/stage. • Use the file systems /oracle/ /sapdata exclusively for data files of the database. • The block size of the file system must be less than or equal to the Oracle block size, which is 8 KB. AIX only allows a block size of 4 KB. • Use a separate disk for the file system /oracle/ /saparch. • For performance and security reasons, archive files and redo log files must reside on separate disks. Different Oracle Systems For performance reasons, you generally should not install several database systems (for different SAP Systems) on one single host. If you decide to do so nevertheless, each database must be installed as described in this documentation. Make sure that the staging area (/oracle/stage/stage_ , Oracle 8.1.6: /oracle/stage/816_32 or /oracle/stage/816_64) corresponding to the Oracle version is used for every Oracle system. Use one staging area for Oracle systems with the same version. Examples The following shows you some examples and gives recommendations that may be useful: • For an overview of a basic distribution that provides adequate data security and performance in an average size production system, see the example Recommended Configuration [page 22]. July 2000 21
  22. 1 Installation Planning SAP AG 1.2 Distribution of Components to Disks • For a distribution that is suitable for a small test or demo system, see the example Minimal Configuration [page 22]. List of required file systems Refer to SAP File Systems [page 23] and Oracle File Systems [page 26] to get the minimum file system sizes required for the installation. 1.2.1 Recommended Configuration The following diagram shows an optimal distribution of the database data on different disks. Backup of DB data log files Mirrored Redo Redo Logs Logs Set B Mirrored Redo Redo Set B Logs Logs Set A Set A Optimal Distribution 1.2.2 Minimal Configuration This configuration should only be used for test or demo systems. Device 1: Backup of redo logs Device 2: Redo logs and database data Device 3: Mirrored redo logs and database data 22 July 2000
  23. SAP AG 1 Installation Planning 1.2 Distribution of Components to Disks Redo Mirrored Backup of logs Redo logs log files DB data DB data Minimal Configuration Although this "minimal configuration" satisfies the SAP security requirements, it has the following disadvantages: • Security − The minimal configuration does not ensure that both the database files and redo log files will not be lost if there is a single disk failure. − The minimal configuration makes sure that no data will be lost, but recovery will be complicated and time-consuming. • Performance − The I/O-intensive redo logs are on the same disk volumes as the data files. − This configuration should only be used at small installations. 1.2.3 SAP File Systems Definition You need to set up file systems for the SAP System before the installation. The file systems are global, that is, they are accessed by all hosts in the SAP System. File System Name Description Space Required / Software and data for one SAP Central instance and System standalone gateway: 300 MB Dialog instance (same platform as central instance): no file system necessary Dialog instance (different platform): 240 MB /usr/sap/ Instance-specific data, symbolic Dialog instance with sapcpe links to the data for one system in use: 380 MB Other instances: 350 MB /usr/sap/trans Global transport directory for all 100 MB for each SAP instance SAP Systems Database home directory Database-specific July 2000 23
  24. 1 Installation Planning SAP AG 1.2 Distribution of Components to Disks The listed file system sizes are SAP requirements. Depending on your operating system, you might have to add space for administrative purposes. The following graphic shows the standard SAP directory structure: / usr sap trans SYS exe profile global log data work dbg opt run File system you have to set up manually exe profile global Symbolic link Standard SAP Directory Structure Use Directory / / This directory is physically located on the central instance. In homogeneous systems, you need to mount it by Network File System (NFS) for all hosts belonging to the same SAP System. It contains the following sub-directories: • exe, containing executable kernel programs • global, containing log files • profile, containing the start and operations profiles of all instances 24 July 2000
  25. SAP AG 1 Installation Planning 1.2 Distribution of Components to Disks Directory /usr/sap/ This directory contains files for the operation of a local instance. There is a sub-directory for each instance installed on the local instance host, whereas data used by several instances is located in the directory SYS. There are sub-directories of /usr/sap/ /SYS with symbolic links to sub-directories of / / . R3SETUP sets up these directory structures during the installation. Since SAP traces for the instance are created in the directory /usr/sap/ / , sufficient space must be available in this directory. Changes in SAP System profiles can also affect the disk space. Directory /usr/sap/trans In an SAP network there must be a global directory, called /usr/sap/trans, for the transport of objects between SAP Systems. This directory is created on one SAP instance host in the SAP network (the transport host). It must be accessible by every host on which an SAP instance is installed and which belongs to this SAP network. The path on every host must be /usr/sap/trans. If you want to use the Change and Transport system, additional space is required in directory /usr/sap/trans. Since the required storage size differs depending on the transport volume, SAP cannot specify the required amount of free disk space. We recommend that you reserve 20 MB per user of the transport system, with a minimum of 200 MB. The directory /usr/sap/trans can be a soft link pointing to the transport directory, or it can be mounted using Network File System (NFS). It should be exported in read/write mode on the transport host with NFS and mounted on all central and dialog instance hosts. For more information, see Mounting Directories via NFS [page 217]. July 2000 25
  26. 1 Installation Planning SAP AG 1.2 Distribution of Components to Disks 1.2.4 Oracle File Systems The following table gives an overview of the file systems required for the Oracle database. For a description of the file systems that are required for the SAP System see SAP File Systems [page 23]. File systems required for the Oracle database File System Name Description Space Required Oracle 8.0.5, Oracle 8.0.6: Home directory for Oracle Central instance with DB: 950 MB /oracle/ instance Central or dialog instance: 140 MB Oracle 8.1.6: ($ORACLE_HOME) /oracle/ /816_32 or Standalone DB: 950 MB /oracle/ /816_64 /oracle/805_32 or Directory for Oracle client 20 MB /oracle/805_64 software. The directory has to be named 805_ even if you are using Oracle 8.0.6 or Oracle 8.1.6. Oracle 8.0.5: Installation and upgrade AIX: 600 MB /oracle/stage/stage_805 directory for database Compaq Tru64 UNIX: 680 MB software (staging area) Oracle 8.0.6: /oracle/stage/stage_806 HP-UX, Linux: 500 MB ReliantUNIX, Solaris: 650 MB Oracle 8.1.6: /oracle/stage/816_32 or /oracle/stage/816_64 /oracle/ /origlogA Original set A of redo logs 55 MB /oracle/ /origlogB Original set B of redo logs 45 MB /oracle/ /mirrlogA Mirrored set A of redo logs 55 MB /oracle/ /mirrlogB Mirrored set B of redo logs 45 MB /oracle/ /saparch Backup of redo logs 350 MB /oracle/ /sapreorg Work directory for 1400 MB database administration /oracle/ /sapdata1 SAP data Approximately 8 GB of space are required for all SAP data files. /oracle/ /sapdata2 SAP data See SAP Note 311308 for exact /oracle/ /sapdata3 SAP data space requirements of each /oracle/ /sapdata4 SAP data sapdata file system. /oracle/ /sapdata5 SAP data /oracle/ /sapdata6 SAP data 26 July 2000
  27. SAP AG 1 Installation Planning 1.2 Distribution of Components to Disks The file system $ORACLE_HOME (/oracle/ , Oracle 8.1.6: /oracle/ /816_32 or /oracle/ /816_64) must reside on a local disk. It cannot be a softlink. The file system • /oracle/stage/stage_805 (Oracle 8.0.5) • /oracle/stage/stage_806 (Oracle 8.0.6) • /oracle/stage/816_32 (32-bit Oracle 8.1.6) • /oracle/stage/816_64 (64-bit Oracle 8.1.6) is also used for Oracle upgrades and should not be deleted after the installation. During system operation, the database writes temporary files to the /oracle/ directory. SAP therefore reserves more space during installation than the Oracle software needs. The archive directory /oracle/ /saparch should provide enough space for archives between two backups. In a production system, between 300 MB and 1 GB data is archived daily. The listed file system sizes are SAP requirements. Depending on your operating system, you might have to add space for administrative purposes. July 2000 27
  28. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check 1.3 Hardware and Software Requirements Check Purpose SAP specifies minimal hardware and software requirements for different system configurations to ensure that a newly installed system performs well. These requirements are summarized in hardware and software requirements checklists. These checklists give the minimum requirements for small SAP system installations (database server and application server). Depending on the amount of data involved, the requirements might change. If you have any questions, contact the person in charge of installation or your Competence Center. The listed requirements are only valid for Release 4.6D. Prerequisites To get remote support, the remote connection specified in the contract agreement must be available before installation. The Internet address setup at SAP and registration are dealt with during the installation. Process Flow 1. You check the requirements on each machine where you intend to install the SAP System: − For a central system, you see the check list for: • Central system to install the central instance and database • Central instance or dialog instance if you want to install additional dialog instances − For a standalone database system, you see the check list for: • Standalone database system to install the database • Central instance or dialog instance to install the central instance and if you want to install additional dialog instances 2. You check the network requirements. The requirements for the SAP System network configuration are described in the documentation Integration of R/3 Servers in TCP/IP Networks and SAP Software in PC Networks. 3. You check the operating system requirements: − AIX [page 33] − Compaq Tru64 [page 36] − HP-UX [page 39] − IBM Numa-Q [page 46] − Linux [page 42] − ReliantUNIX [page 44] − Solaris [page 47] 28 July 2000
  29. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check If you do not fully meet the relevant requirements, you might experience problems when working with the SAP System. July 2000 29
  30. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check 1.3.1 Checking Requirements for a Central System Use For the installation of a central SAP System, be sure to meet the minimal requirements listed in this section. Prerequisites You are installing a standard SAP System as a central system. That is, the central instance and the Oracle database are on the same host machine. Procedure 1. Check that the host machine meets the following requirements: Requirement Type Requirement Hardware • CD drive Requirements • Disk Space for SAP System: 8 GB disk space + 1.2 GB temporary disk space on separate disks • For security reasons (system failure), the file systems must be distributed physically over at least 3 (recommended: 5) disks. • RAM for SAP System: At least 256 MB RAM • Disk space for swap: - 32-bit SAP Kernel: 3 * RAM, minimum 3 GB, maximum 20 GB - 64-bit SAP Kernel: At least 20 GB is recommended for standard installations (for more information, see SAP Note 153641). If you want to install only a small system, contact your Hardware Partner for appropriate swap space values. Software • Operating system version: The supported operating system Requirements releases are listed in SAP Note 156548. • Contact your operating system vendor for the latest OS patches. • For the Oracle installation and importing Oracle patches, a C compiler and the make utility must be installed. (Does not apply to Solaris.) • If application servers are installed decentralized, Network File System (NFS) is a requirement. • Ensure that the necessary fonts/code pages and NLS are installed. Other Requirements • Ensure that no hostname is longer than 8 characters. • Check your keyboard definitions. • If you want to install a printer on the database server for the SAP system: Ensure that the printer can be accessed under UNIX. 2. Check that the other requirements (network, dialog instance, operating system) are met. 30 July 2000
  31. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check 1.3.2 Checking Requirements for a Standalone DB System Use For the installation of a standalone database system, be sure to meet the minimal requirements listed in this section. Prerequisites You are installing a standalone database system. That is, the central instance and the Oracle database are on the different host machines. For the requirements of the central instance, see Checking Requirements for a Central or Dialog Instance [page 32]. Procedure 1. Check that the database host machine meets the following requirements: Requirement Type Requirement Hardware • CD drive Requirements • 8 GB disk space + 1.2 GB temporary disk space on separate disks • For security reasons (system failure), the file systems must be distributed physically over at least 3 (recommended: 5) disks. • At least 256 MB RAM • Disk space for swap: 3 * RAM + 500 MB, minimum 1,25 GB Software • Operating system version: The supported operating system Requirements releases are listed in SAP Note 156548. • Contact your operating system vendor for the latest OS patches. • For the Oracle installation and importing Oracle patches, a C compiler and the make utility must be installed. (Does not apply to Solaris.) • If application servers are installed decentralized, Network File System (NFS) is a requirement. • Ensure that the necessary fonts/code pages and NLS are installed. Other Requirements • Ensure that no hostname is longer than 8 characters. • Check your keyboard definitions. • If you want to install a printer on the database server for the SAP system: Ensure that the printer can be accessed under UNIX. 2. Check that the other requirements (network, dialog instance, operating system) are met. July 2000 31
  32. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check 1.3.3 Checking Requirements for a Central or Dialog Instance Use For the installation of a dialog instance or a central instance without database, be sure to meet the minimal requirements listed in this section. Prerequisites You are installing a dialog instance or a central instance without database for distributed SAP applications. Procedure 1. Check that the host machine meets the following requirements: Requirement Type Requirement Hardware • Disk space exclusively for the SAP System: Requirements − Central Instance: At least 790 MB − Dialog Instance (same platform as central instance): 520 MB − Dialog Instance (different platform as central instance): 730 MB • RAM for the SAP System: At least 256 MB RAM • Disk space for swap: − 32-bit SAP Kernel: 3 * RAM, minimum 3 GB, maximum 20 GB − 64-bit SAP Kernel: At least 20 GB is recommended for standard installations (for more information, see SAP Note 153641). If you want to install only a small system, contact your Hardware Partner for appropriate swap space values. Software • Operating system version: The supported operating system Requirements releases are listed in SAP Note 156548. • Network File System (NFS) must be installed. Other Requirements • Ensure that no hostname is longer than 8 characters. • Check your keyboard definitions. • If you want to install a printer on the database server for the SAP system: Ensure that the printer can be accessed under UNIX. 2. Check that the other requirements (network, dialog instance, operating system) are met. 32 July 2000
  33. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check 1.3.4 Checking Requirements for AIX Use This description is intended to help you to perform the necessary checks. If in doubt, consult your system manuals and the documentation for your network software. Procedure 1. Check the host hardware requirements on AIX: Hardware How to Check Requirements Tape drive EXAbyte 8mm drive with hardware compression is recommended. Capacity 5 GB. You can test the drive /dev/rmt0 as follows: tar -cvf /dev/ (The device name is always rmt0 unless more than one tape drive exists) CD drive ISO 9660 compatible. Many CD drives can be configured, but not all can be mounted. Try to mount it. Disks For data security reasons, distribution over three disks is required (over five is recommended). Display available disks: lspv (disks marked none in the 3rd column are unused) Display free space on a disk: lspv -p (areas marked free in the 2nd column are unused) RAM ( at least 256 MB) Display RAM size (in KB): lsattr -El sys0 -a realmem 64Bit CPU for 64Bit SAP Basis Kernel July 2000 33
  34. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check 2. Check the host software requirements on AIX: Software Req. How to Check Operating system Check the operating system version with the command: lslpp -l bos.rte Part of the output must be: bos.rte 4.3.2 (or a larger version number) NFS Check whether NFS is installed: lslpp -l "bos.net.nfs.*" Check whether NFS is running: lssrc -g nfs Then rpc.mountd and either biod or nfsd must have status activated. NLS Display which locales are available: locale -a The following files must be available: de_DE.ISO8859-1, en_US.ISO8859-1. LDAP support If you want to use LDAP (Lightweight Directory Access Protocol) directory services, the following LDAP library is required: libldap.a For more information, refer to the documentation available in the SAPNet under Solutions → mySAP.com Technology → System Management → Directory Access Services. Additional Software The following additional software components must be installed. To get an overview, use the following command as user root: lslpp -l | more bos.rte (Base Operating System Runtime) bos.adt (Base Application Development) bos.data (Base Operating System Data) bos.sysmgt (System Management) bos.diag.rte (Hardware Diagnostics Database) bos.msg.en_US (Base OS Runtime Messages - U.S. English) bos.net.nfs (Network File System) bos.net.tcp (TCP/IP) perfagent (Performance Agent) bos.loc.iso.en_US (Base System Locale Code Set - U.S. English) bos.loc.iso.de_DE (Base System Locale Code Set - German) bos.iconv.de_DE (Base Level Fileset (requ. for Local Code Set)) bos.iconv.com (Base Level Fileset (requ. for Local Code Set)) devices.* (Device Drivers for all installed Hardware) 34 July 2000
  35. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check printers.rte (Printer Backend (if Printer installed)) X11.base (AIXwindows Runtime) X11.apps (AIXwindows Applications) X11.motif (AIXwindows Motif) X11.fnt.iso1 (AIXwindows Latin 1 Fonts) X11.loc.en_US (AIXwindows Locale - U.S. English) X11.msg.en_US (AIXwindows Messages - U.S. English) X11.Dt (AIXwindows Desktop) xlC.rte (C Set ++ for AIX Application Runtime, Version 3.1.4.8 or higher) Oracle database only: A C linker is required (not a C compiler). A linker can be found in the bos.rte.bind_cmds fileset. A separate license is not required for the linker (beyond the AIX license). Use the following command to check the level and state of the linker: lslpp -L bos.rte.bind_cmds Additionally, check that all filesets are in a consistent state: lppchk -v Printer Try to print a file: lp -d Check the status of your spool and the printers: lpstat -t Keyboard You can set the keyboard by typing the command smitty chkbd on the directly connected console. You can select your keyboard under Motif by setting a language environment (LANG), for which an NLS component is installed. The settings will take effect after reboot. Network Test the network connection to the database server: /etc/ping 100 10 July 2000 35
  36. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check 1.3.5 Checking Requirements for Compaq Tru64 UNIX Use This description is intended to help you to perform the necessary checks. If in doubt, consult your system manuals and the documentation for your network software. Procedure 1. Check the host hardware requirements on Compaq Tru64 UNIX: Hardware How to Check Requirements Tape drive EXAbyte 8mm drive with hardware compression is recommended. Capacity 5 GB. You can test the drive /dev/rmt0 as follows: tar -cvf /dev/ (The device name is always rmt0 unless more than one tape drive exists) CD drive ISO 9660 compatible. The CD drive must be connected locally to your central instance host. Many CD drives can be configured but not all can be mounted. Try to mount it. Disks For data security reasons distribution over three disks is required (over five is recommended). Display available disks: uerf -R -r 300 | more (shows all devices recognized during startup) or at boot prompt: >>> SH DEV (information on type, size, port) To display the partitioning use disklabel (as shown by uerf, e.g. rz6) RAM Display RAM size (in MB): vmstat -P | head -2 Processor Only valid if your system has a Compaq Alpha Processor: Processor version EV5/6 (with 400 MHz) or higher is recommended. See SAP Note 165461. 36 July 2000
  37. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check 2. Check the host software requirements on Compaq Tru64 UNIX: Software How to Check Requirements Operating system Check the operating system version with the command: sizer -v C compiler The output of setld -i | grep OSFLIBA setld -I | grep OSFINCLUDE must contain, for example: OSFLIBA440 installed OSFINCLUDE440 installed (The last three digits in the subset name are UNIX version dependant). NLS Enter the commands: setld -i | grep OSFEURLOC4 and check the output which should read, for example: OSFEURLOC440 installed Display which locales are available: locale -a The following must be available: de_DE.ISO8859-1, en_US.ISO8859-1. NFS Check whether NFS is installed: setld -i | grep NFS The output must contain OSFNFS410 installed NFS(tm) Check whether NFS is running: ps -ef | grep nfsd ps -ef | grep portmap ps -ef | grep mountd Routing information: netstat -r You can use /usr/sbin/nfssetup to set up NFS. LDAP support If you want to use LDAP (Lightweight Directory Access Protocol) directory services, the following LDAP library is required: libldap30.a For more information, refer to the documentation available in the SAPNet under Solutions → mySAP.com Technology → System Management → Directory Access Services. July 2000 37
  38. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check Fonts Check if the necessary X fonts are installed: setld -i | grep FONT The output should contain, for example: OSFFONT410 installed DECwindows 75dpi Fonts OSFFONT15410 installed DECwindows 100dpi Fonts OSFMITFONT410 installed X Fonts Printer Try to print a file: lpr -P Check the status of your spool and the printers: lpc stat Keyboard Use the Session Manager to set the correct keyboard as follows: Options → Keyboard Choose the appropriate keyboard and confirm with OK or Apply. Save settings with Options → Save Current Settings Network Test the network connection to the database server: ping -c 10 38 July 2000
  39. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check 1.3.6 Checking Requirements for HP-UX Use This description is intended to help you to perform the necessary checks. If in doubt, consult your system manuals and the documentation for your network software. Procedure 1. Check the host hardware requirements on HP-UX: Hardware How to Check Requirements Tape drive EXAbyte 8mm drive with hardware compression is recommended. Capacity 5 GB You can test the drive /dev/rmt/0m as follows: tar -cvf /dev/rmt/ CD drive ISO 9660 compatible. The CD drive must be connected locally to your central instance host. Many CD drives can be configured but not all can be mounted. Try to mount it. Disks For data security reasons distribution over three disks is required (over five is recommended). Display available disks: ioscan -f -C disk (the CD-ROM is also displayed) To find out the size of the disks, use the command diskinfo: diskinfo /dev/rdsk/ RAM To display the RAM size, run SAM and choose: Performance Monitors → System Properties → Memory July 2000 39
  40. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check 2. Check the host software requirements on HP-UX: Software How to Check Requirements Operating system Check the operating system version with the following command: uname -r Fileset Oracle only Make sure that the fileset LANG-MIN is installed. Enter swlist -v | grep -i lang-min If nothing is displayed, the fileset is not installed yet. NFS The NFS driver must be in the kernel. You can check this using the current kernel configuration files: grep nfs /stand/system Check whether NFS is running: ps -ef | grep nfsd ps -ef | grep portmap (HP-UX 10.xx) ps -ef | grep rpcbind (HP-UX 11.xx) grep NFS_C /etc/rc.config.d/nfsconf grep NFS_S /etc/rc.config.d/nfsconf Either NFS_CLIENT, NFS_SERVER or both should be set to 1. You can use SAM to start NFS or/and add the driver to the kernel. NLS Check whether National Language Support (NLS) is installed. swlist -v | grep -i nls The output should contain the string NLS-AUX Display which locales are available: locale -a The following files must be available: de_DE.iso88591, en_US.iso88591. C++ Runtime Check whether the C++ runtime environment is installed: Environment swlist -l product | grep PHSS This command should show that the following patches are installed: HP-UX 10.xx: PHSS_12609 HP aC++ core library components PHSS_10053 HP aC++ dld.sl performance fix HP-UX 11.xx: PHSS_13390 HP aC++ runtime library components (A.03.05) A newer version of the patches listed here may exist. Contact your HP Response Center for information on the patches that are necessary for your machine. 40 July 2000
  41. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check LDAP support If you want to use LDAP (Lightweight Directory Access Protocol) directory services, the following LDAP library is required: • HP-UX 10.20: libldapssl30.sl • HP-UX 11.0: libldapssl40.sl For more information, refer to the documentation available in the SAPNet under Solutions → mySAP.com Technology → System Management → Directory Access Services. Fonts The directory /lib/X11/fonts contains the available fonts. You can choose these fonts in your default profiles for X11 and VUE. Example: iso_8859.1 or hp_roman8 Printer Try to print a file: lp -d Check the status of your spool and the printers: lpstat -t Keyboard You can set the keyboard on an ASCII console as follows. A configuration menu bar is activated via the User/System key: config keys → terminal config Select Default Values or make your selection in the fields Keyboard and Language . July 2000 41
  42. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check 1.3.7 Checking Requirements for Linux Use This description is intended to help you to perform the necessary checks. If in doubt, consult your system manuals and the documentation for your network software. Procedure For more information concerning installation on Linux, see SAP Note 171356. 1. Check the host hardware requirements on Linux: Hardware How to Check Requirements Tape drive EXAbyte 8mm drive with hardware compression is recommended Capacity 5 GB You can test the drive as follows: tar -cvf /dev/ CD drive ISO 9660 compatible. The CD drive must be connected locally to your central instance host. Many CD drives can be configured but not all can be mounted. Try to mount it. Disks For data security reasons distribution over three disks is required (over five is recommended). Display available disks: cat /proc/partitions RAM Display RAM size (in KB): free 42 July 2000
  43. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check 2. Check the host software requirements on Linux: Software How to Check Requirements Operating system Check the operating system version with the command: cat /proc/versions C compiler C-Development Package must be installed. NLS Display which locals are available: locale -a The following must be available: de_DE, en_US NFS Check wether NFS is running: /etc/rc.d/int.d/nfs status /etc/rc.d/int.d/portmap status Routing information: netstat -r LDAP support If you want to use LDAP (Lightweight Directory Access Protocol) directory services, the following LDAP libraries are required: libldap.so, liblber.so For more information, refer to the documentation available in the SAPNet under Solutions → mySAP.com Technology → System Management → Directory Access Services. Network Test the network connection to the database server: ping -c 10 Printer Try to print a file: lpr -P Check the status of spooling queues and printers: lpc stat July 2000 43
  44. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check 1.3.8 Checking Requirements for Reliant (RM300/400/600) Use This description is intended to help you to perform the necessary checks. If in doubt, consult your system manuals and the documentation for your network software. Procedure 1. Check the host hardware requirements on Reliant: Hardware How to Check Requirements Tape drive EXAbyte 8mm drive with hardware compression is recommended. Capacity 5 GB You can test the drive as follows: tar -cvf /dev/ios0/ Informix only: If ONARCHIVE is used then model 8500 (High Density Mode) or model 8505 is required. To check this, the output of autoconf -a | grep EXABYTE must contain EXB-8500- or EXB-8505- CD drive ISO 9660 compatible. The CD drive must be connected locally to your central instance host. Disks For data security reasons distribution over three disks is required (over five is recommended). To display the available disks: /sbin/autoconf -l | grep disk All disks and CD-ROM drives will be displayed. To see the disk size: /sbin/dkpart -l /dev/ios0/rsdiskXXXsX or display the used areas with: /sbin/dkmap RAM Display the RAM size (in MB): uname -M The command displays the number of CPUs and the RAM size, separated by a slash (/), for example 2/512. 44 July 2000
  45. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check 2. Check the host software requirements on Reliant: Software How to Check Requirements Operating system Check the operating system version and make sure that the latest EKS patches are installed. For the OS version, enter: uname -rv Patches Verify that the latest patches for your OS version are installed. Consult the technical support at SIEMENS(ITS). NFS Check whether your computer is configured for Network File System (NFS). pkginfo | grep -i nfs (whether NFS is installed) ps -ef | grep nfsd (whether NFS processes are running) ps -ef | grep mountd ps -ef | grep inetd NLS Display which locales are available: locale -a The following must be available: de_DE.88591, en_US.88591. C++ Runtime System Check whether the ReliantUNIX C++ Runtime System is installed: pkginfo -l CDS++RTS LDAP support If you want to use LDAP (Lightweight Directory Access Protocol) directory services, the following LDAP library is required: libldap30.so For more information, refer to the documentation available in the SAPNet under Solutions → mySAP.com Technology → System Management → Directory Access Services. Fonts To check the installed fonts: pkginfo -l siwinfs pkginfo -l sifosrc Printer Try to print a file: lp -d Check the status of your spool and the printers: lpstat t Network Test the network connection to the database server: /usr/sbin/ping 100 10 July 2000 45
  46. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check 1.3.9 Checking Requirements for IBM NUMA-Q Use This description is intended to help you to perform the necessary checks. If in doubt, consult your system manuals and the documentation for your network software. Procedure 1. Check the host hardware requirements on IBM NUMA-Q: Hardware How to Check Requirements Tape drive EXAbyte 8mm or HP 4mm drives with hardware compression are recommended. You can test the drive /dev/rmt/ as follows: tar -cvf /dev/rmt/ where tape_device can be determined from: /etc/dumpconf -d | grep “^t” CD drive ISO 9660 compatible. The CD drive must be connected locally to your central instance host. Many CD drives can be configured, but not all can be mounted. Try to mount it. RAM To display the RAM size: /etc/showcfg Disks Display available disks and sizes: /etc/diskid To find out the size of the disk partitions, use the command diskinfo: /etc/prtvtoc Printer Try to print a file: lp -d Check the status of your spool and the printers: lpstat -t 2. Check the host software requirements on IBM NUMA-Q: Software Req. How to Check Operating system Check the operating system version with the following command: uname -v Kernel Parameters To check kernel parameters: /etc/sysdef | more ANSI C compiler To check the defaults and the version of compiler: cc -### foo.c NLS Display which locales are available: locale -a The following file must be available: en_US. Network Test the network connection to the database server: /etc/ping 46 July 2000
  47. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check 1.3.10 Checking Requirements for Solaris Use This description is intended to help you to perform the necessary checks. If in doubt, consult your system manuals and the documentation for your network software. Procedure 1. Check the host hardware requirements on Solaris: Hardware Req. How to Check Tape drive 14 GB EXAbyte 8mm drive with hardware compression is recommended. You can test the drives as follows: /usr/bin/mt -f /dev/rmt/[0,1,2, ][n] status This tells you the type of drive and whether a tape is loaded. Alternatively, you can use: /usr/bin/tar -cvf /dev/rmt/[0,1,2, ] \ [n] CPU Display the status and number of existing CPUs: /usr/sbin/psrinfo RAM Display the available working memory: /usr/sbin/prtconf |grep Memory Disks Device name: dev/[r]dsk/c[0-39]t[0-14]d[0-4]s[0-7] Parameters: rdsk use for raw devices c[0-39] number of the controller t[0-14] SCSI target d[0-4] position in tray s[0-7] number of the partition (s2 is always the full disk) Display the partitioning, for example: /usr/sbin/prtvtoc Change the partitioning: /usr/sbin/format Volume Manager Mount a cdrom: /bin/volcheck Dismount and eject: /usr/bin/eject Test whether the volume manager is running: /usr/ucb/ps -ef |grep vold Start the volume manager: /usr/sbin/vold & Printer Status of the spool for all printers in use: /bin/lpstat -t To set up a printer: /bin/admintool July 2000 47
  48. 1 Installation Planning SAP AG 1.3 Hardware and Software Requirements Check 2. Check the host software requirements on Solaris: Software Requirements How to Check Operating system Check the operating system version with the command: /bin/uname -r Patches Check the installed patches: /bin/showrev -p NLS Display which locales are available: locale -a The following files must be available: iso_8859_1, en_US. C++ Runtime Environment The Shared Library Patch for C++ must be installed. LDAP support If you want to use LDAP (Lightweight Directory Access Protocol) directory services, the following LDAP library is required: libldap.so For more information, refer to the documentation available in the SAPNet under Solutions → mySAP.com Technology → System Management → Directory Access Services. Networking List of all active network devices: /usr/ucb/netstat -I /usr/sbin/ifconfig -a Routing information: /usr/ucb/netstat -r Check whether ISDN is installed: /bin/pkginfo |grep SUNWisdn Status of the ISDN connection: /opt/SUNWconn/bin/isdnstat Check whether NFS is running: • NFS client /usr/ucb/ps -ef |grep nfs The processes statd and lockd must run. Start them with: /etc/init.d/nfs.client start • NFS server /usr/ucb/ps -ef |grep mountd Start it with: /etc/init.d/nfs.server start Test the network connection to the database server: /usr/sbin/ping 48 July 2000
  49. SAP AG 1 Installation Planning 1.3 Hardware and Software Requirements Check Solstice DiskSuite Check whether Solstice DiskSuite is installed: /bin/pkginfo | /usr/bin/grep SUNWmd For a detailed description, see the standard documentation. Veritas Volume Manager If you don't use Solstice DiskSuite, check whether Veritas Volume Manager is installed: /bin/pkginfo | /usr/bin/grep SUNWvx For a detailed description, see the standard documentation. July 2000 49
  50. 2 Installation Preparations SAP AG 2 Installation Preparations Purpose Before you start the installation, you must prepare the operating system and the SAP System. You perform preparations on hosts that are to be used with the SAP System. The installation preparations apply to all instance types (central, dialog, and database instance, and standalone gateway), unless indicated otherwise. Prerequisites You have finished the planning phase. AIX only All operating system dependent steps for AIX can be performed as follows: − Manually by entering AIX commands with the appropriate options − Using SMIT, a menu-driven system administration tool The text for AIX steps describes the use of the AIX tool SMIT. If problems arise with the function keys, you can also use ESC and the corresponding number to simulate the function key (for example, F4 = ESC 4). Process Flow SAP recommends to use the C-shell (csh) as login shell. If you want to use the Bourne shell (sh) or the Korn shell (ksh), see SAP Note 202227 for more information. To prepare the installation, perform the tasks described below. Consult OS dependent information for each of these tasks. 1. You adapt UNIX kernel parameters and swap space [page 51]. 2. You integrate LDAP directory services [page 52] if required. 3. You choose an SAP System name [page 55]. 4. You set up file systems and raw devices [page 56] 5. You set up the transport directory [page 56]. 6. You set up an installation directory [page 58]. 50 July 2000
  51. SAP AG 2 Installation Preparations 2.1 Adapting UNIX Kernel Parameters and Swap Space 2.1 Adapting UNIX Kernel Parameters and Swap Space Use You need to check and, if necessary, modify the UNIX kernel of your host as described in Checking and Modifying the UNIX kernel [page 166] (AIX: Creating UNIX Groups and Users [page 226]). The swap space size is listed in Hardware and Software Requirements Check [page 28]. You use the memlimits tool to check the following parameters: • Maximum heap size (maximum data segment size per process) • Maximum mapped file size • Maximum protectable size • Maximum address space per process • Total available swap space Procedure 1. Unpack the file memlimits. As of R/3 Release 4.6C, the new archiving tool SAPCAR replaces the previous archiving tool CAR. See SAP Note 212876 for more information. Enter: / /UNIX/ /SAPCAR -xgvf \ / /UNIX/ /SAPEXE.SAR memlimits 2. Start memlimits by entering one of the following commands: - For a 32-bit SAP kernel, enter: ./memlimits - For a 64-bit SAP kernel, enter: ./memlimits -l 20000 3. If error messages occur, increase your swap space and rerun memlimits until there are no more errors. July 2000 51
  52. 2 Installation Preparations SAP AG 2.2 Integration of LDAP Directory Services 2.2 Integration of LDAP Directory Services Purpose The use of an LDAP (Lightweight Directory Access Protocol) directory allows important information within a corporate network to be stored centrally on a server where it can easily be accessed and administered. Storing information at one central location for the entire network has the advantage that data only has to be maintained once and will therefore not be redundant or inconsistent. If an LDAP directory is available in the corporate network, the SAP System can be configured to take advantage of it. An appropriately configured SAP system can read information from the directory and also store information there. The following explains how SAP Systems can benefit from using an LDAP directory and also gives an overview of steps the that are necessary to configure the system for the use of the directory. The SAP System is able to interact with the LDAP directory on the basis of the LDAP protocol. This defines how communication between the SAP System and the directory is conducted and how data in the directory is structured, accessed or modified. By using an LDAP directory, the SAP System can take advantage of the information stored. For example, if an LDAP directory is available on a Unix or NT machine, the SAP System can be configured so that it can use the information available in these directories. An example for a directory type that supports the LDAP protocol is the Active Directory Service of Microsoft Windows 2000. In the following, directories other than the Active directory that implement the LDAP protocol are referred to as generic LDAP directories. In the SAP environment, the information stored in an LDAP directory can be exploited by: • The LDAP Connector • SAP Logon (planned for the future) • The Microsoft Management Console (MMC) The LDAP Connector The LDAP Connector is an ABAP interface to LDAP directories that enables SAP applications to access and utilize information stored in the directory. For example, with the LDAP Connector the SAP Office application is able to fill and update its address book data by reading information from the directory. The Connector can be used by SAP applications, but also by customers that wish to develop enhancements for applications to integrate LDAP directory services. Before the LDAP Connector can be used, it has to be installed as described in SAP Note 188371. The SAP Logon In future, the configuration of the SAP Logon dialog box will be simplified with the help of an LDAP directory. At present, after the SAP installation, the SAP logon for each frontend has to be manually configured by entering technical details on available systems. A planned SAP feature will be able to automatically configure the logon for systems that integrate LDAP directory services. 52 July 2000
  53. SAP AG 2 Installation Preparations 2.2 Integration of LDAP Directory Services The MMC The MMC is a graphical user interface for administering and monitoring SAP Systems from a central location. This functionality is available for both SAP Systems on a Windows and (with some restrictions) on a UNIX platform. The MMC presents and analyses system information that is gathered from various sources. When the LDAP directory is used as a source of information this has advantages for the MMC. System information can be read straight from the directory which automatically registers all changes to the system landscape. Up-to-date information about all SAP application servers, their status and parameter settings is therefore always available in the MMC. Prerequisites The SAP System can only be configured to integrate LDAP directories if these are already available on the network: • A generic LDAP directory is an additional component that has to be installed separately on a Unix or Windows NT Server. • The Active directory is part of a Windows 2000 installation and is automatically available on all Domain Controllers. Process Flow Generic LDAP Directories The process of preparing the SAP System for the use of generic LDAP services involves a number of manual steps. Again, both the LDAP directory and the SAP System must be configured appropriately: • The LDAP directory has to be prepared so that it can store SAP data. This involves extending the directory schema and creating a container for the SAP data. • The SAP System has to be configured to enable interaction with the LDAP directory. The configuration steps are performed by the R3SETUP tool during the installation of the SAP central instance. R3SETUP is able to configure the system correctly on the basis of information related to the LDAP directory that has to be entered before the installation procedure begins. • A user with a password has to be set up on the machine where the SAP System is running to permit the SAP System to access and modify the LDAP directory. This is done by running the script ldappasswd. For detailed instructions on how to enable interaction between a generic LDAP directory and the SAP System, refer to the documentation available in the SAPNet under: Solutions → mySAP.com Technology → System Management → Directory Access Services. Active Directory To enable an SAP System to make use of the features offered by the Active directory, both the Active directory and the SAP System have to be configured appropriately. • In a first step, the Active Directory has to be prepared so that it can store SAP data. This involves extending the schema for the SAP data types, creating a root container for the storage of SAP-specific information and defining accounts that allow directory access. These tasks are all performed with the help of the R3SETUP tool which offers the option Configure Active directory for SAP. July 2000 53
  54. 2 Installation Preparations SAP AG 2.2 Integration of LDAP Directory Services For more information see Preparing the Active Directory for SAP [page 54]. • In a second step, the SAP System on a Windows 2000 platform has to be configured to enable interaction with the Active Directory. This is done during the installation of the SAP central instance with the help of the R3SETUP tool. The R3SETUP tool prompts for information related to the Active Directory and then configures the SAP System appropriately. For more information see the SAP Basis System Installation on Windows documentation. 2.2.1 Preparing the Active Directory for SAP Use The SAP System can only store and access data in the Active Directory, if the directory has been prepared appropriately. To prepare the directory, you use the R3SETUP tool which automatically performs the following tasks: • Extends the Active Directory schema to include the SAP-specific data types. • Creates domain accounts that are a prerequisite for enabling the SAP System to access and modify the Active Directory. These are the group SAP_LDAP and the user sapldap. • Creates the root container where information related to SAP is stored. • Regulates access to the container for SAP data by giving members of the SAP_LDAP group permission to read and write to the directory. Prerequisites A Windows 2000 Domain Controller with an Active Directory must be installed on the network. Procedure Installing R3SETUP Use the R3SETUP tool to prepare the Active Directory for the SAP System. In a first step, you install the R3SETUP tool on the domain controller where the Active Directory is located. 1. Log on to the Domain Controller as domain administrator. 2. Make sure that the TEMP environment variable has been set. To check the variable, choose Start → Settings → Control Panel → System. On the Environment tab, look under User Variables. TEMP is normally set to C:\temp. Make sure that the specified directory really exists in your file system. 3. Insert the Kernel CD-ROM. 4. Start the program R3SETUP.BAT from the directory :\NT\COMMON The R3SETUP window opens. 54 July 2000
  55. SAP AG 2 Installation Preparations 2.3 Choosing an SAP System Name 5. When you are prompted, enter the following: − The name of your SAP System − The directory on your hard disk that the R3SETUP files are to be copied to. The default directory is :\USERS\ ADM\INSTALL When you have made all the required entries, R3SETUP is automatically installed. 6. Enter Yes when a dialog box appears prompting you to log off or reboot. R3SETUP now automatically logs off or reboots. Configuring the Active Directory 1. Log on as the same user that installed the R3SETUP tool. 2. From the NT Start menu choose, Start → Programs → SAP System Setup for → Configure Active Directory for SAP. 3. When you are prompted: − Confirm the name of the domain where the SAP_LDAP group is to be created. This is the domain that you are logged on to. − Enter the password for the sapldap user. When you have made these entries, R3SETUP automatically configures the Active Directory. 2.3 Choosing an SAP System Name Use You need to choose a name for your SAP System. This does not apply when you install a dialog instance. Procedure Choose an SAP System name (SAPSID). The name for your SAP System must be unique throughout your organization and must consist of exactly three alphanumeric characters. Only uppercase letters are allowed. The first character must be a letter (not a digit). Since the following names are reserved, you cannot assign them to your SAP System: ADD ALL AND ANY ASC B20 B30 BCO BIN COM DBA END EPS FOR GID IBM INT KEY LOG MON NOT OFF OMS P30 RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID VAR Choose your SAP System name carefully. Renaming is complicated and requires you to re-install the SAP system. July 2000 55
  56. 2 Installation Preparations SAP AG 2.4 Setting Up File Systems and Raw Devices 2.4 Setting Up File Systems and Raw Devices Use You need to set up the file systems and/or raw devices for the SAP System and the database. For more information about the required file systems, see Installation Planning. The creation and mounting of file systems and the creation of raw devices are described in File Systems, Raw Devices and Swap Space [page 181]. The listed file system sizes are SAP requirements. Depending on your operating system, you might have to add space for administrative purposes. Prerequisites The file system / is physically stored on the central instance host. Procedure 1. Export the file system / in read/write mode to all dialog instance hosts and in read-only mode to all UNIX frontends. When installing a dialog instance on the same hardware platform as the central instance, you do not need to create the file system / . You can mount the directories that reside in this file system from the central instance host using Network File System (NFS). The file system /usr/sap/ must reside on a local disk. /usr/sap cannot be a softlink. 2. Set permissions for the directories and /usr/sap to 775. 2.5 Setting Up the Transport Directory Use In an SAP network there must be a global directory, called /usr/sap/trans, for the transport of objects between SAP Systems. You must create this directory on one SAP instance host in the SAP network (the transport host). It must be accessible by every host belonging to this SAP network on which an SAP instance is installed. The path on every host must be /usr/sap/trans. The directory /usr/sap/trans can be a softlink pointing to the transport directory, or it can be mounted using Network File System (NFS). It should be exported in read/write mode on the transport host using NFS and mounted on all central and dialog instance hosts. 56 July 2000
  57. SAP AG 2 Installation Preparations 2.5 Setting Up the Transport Directory Procedure To set up the transport directory, you perform the following steps. Creating the Transport Directory If the transport directory does not yet exist in your SAP network, perform the following steps: 1. Log on to the central instance host as user root. 2. Create the file system. 3. Mount the file system at /usr/sap/trans. Exporting the Transport Directory 1. Log on to the central instance host on which /usr/sap/trans resides as user root. 2. Make sure that /usr/sap/trans belongs to the group sapsys and has the permissions 775. 3. Export the directory using Network File System (NFS). For more information, see OS-Dependent Installation Steps on UNIX [page 156]. For security reasons, set the permissions of the directory /usr/sap/trans to 771 after the installation. Mounting the Transport Directory 1. Log on as user root to the central or dialog instance host on which /usr/sap/trans is to be mounted. 2. Create the mount point /usr/sap/trans. 3. Mount /usr/sap/trans using Network File System (NFS) from the exporting host. 4. Check that the user root has write permissions: touch /usr/sap/trans/write_test rm /usr/sap/trans/write_test For more information, see Mounting Directories via NFS [page 217]. July 2000 57
  58. 2 Installation Preparations SAP AG 2.6 Setting Up an Installation Directory 2.6 Setting Up an Installation Directory Use Create a new installation directory every time you start R3SETUP with another service (that is, with another command file identified by the ending .R3S). Otherwise, old log and command files could get lost. IBM NUMA-Q, ReliantUNIX and SOLARIS Do not use /tmp and its subdirectories because they are removed when the system is rebooted. For more information, see Preparations [page 159], section “Installation Directory” or “Required Directories”. Procedure 1. Set up an installation directory with 50 MB of free space available. You can choose any name for the installation directory. In this documentation, refers to the installation directory. 2. Set the permissions of the installation directory to 777. Because R3SETUP performs various installation steps with different user IDs, the installation directory requires write permissions for all users. 58 July 2000
  59. SAP AG 3 The SAP System Installation 3 The SAP System Installation Purpose Once you have planned and prepared the installation, you can begin with the actual installation steps. In this core part of the installation process, you set up the main components that enable the operation of an SAP System. These are: • The central instance • The database instance • If required, one or more dialog instances • If required, a standalone gateway instance A minimum SAP System consists of a central instance and a database. Optional dialog instances may be installed on different hosts once the installation of the central instance and the database has been completed. A standalone gateway can be installed on its own. It does not require a central instance to be installed. Central or Standalone Database System Installation You can install the core part of the SAP System – that is, the central instance and database – in one of the following ways: • As a central system In this type of configuration, you install central instance and database instance on a single host. This is the most commonly implemented configuration for an average-size system. • As a standalone database system In this type of configuration, you install the central instance on one host, and the database instance on a second host. This is usually implemented for larger systems with a high throughput. The best approach for your environment depends on various factors, such as the type of applications you intend to deploy, the size of the anticipated workload, and the number of expected concurrent users. Overview of the Installation Components The following components support the installation: • R3SETUP: Tool that performs the actual installation. • INSTGUI: Frontend for R3SETUP that enables you to: − Watch the installation progress − Continue the installation after manual installation steps − View log messages July 2000 59
  60. 3 The SAP System Installation SAP AG − Obtain help on installation steps • Shell script: Copies R3SETUP, INSTGUI and the installation command file to your hard disk. • Command file: Controls the installation process. For every installation step there is a corresponding section in the command file that holds all information required for this step. For more information, see The R3SETUP Tool [page 129]. Prerequisites You have: • Decided in a sizing phase, well in advance of the actual installation procedure, whether a central system or standalone database system best meets your business requirements. • Adapted the UNIX kernel parameters and the swap space settings • Created the required file systems and/or raw devices • Mounted the file system /usr/sap/trans from the transport host (not necessary for a standalone gateway) • Set up an installation directory For more information, see Installation Planning and Installation Preparation. Process Flow 1. You install the central instance and database in one of the following ways: − On a single host as a central system − On two different hosts as a standalone database system 2. If required, you install one or more dialog instances on additional hosts in the system 3. You install the SAP frontends. Refer to the documentation Installation of the SAP Frontend Software for PCs. This is included in the installation package. For more information concerning SAP frontends, see SAP Note 26417 and SAP Note 146505 (and the related notes). 4. If required, you install a standalone gateway instance. 60 July 2000
  61. SAP AG 3 The SAP System Installation 3.1 Central System Installation 3.1 Central System Installation Purpose When a small to medium-sized SAP System is set up, the core parts of the system, namely the central instance and database, are generally installed on a single machine. Process Flow The following graphic illustrates the actions required to install the central and database instance on a single machine. 11 Install SAP Instance Database Server 2 2 Install DB Instance and DB Software July 2000 61
  62. 3 The SAP System Installation SAP AG 3.1 Central System Installation 3.1.1 SAP Instance Installation for a Central System Purpose You want to install an SAP instance as part of the central system installation. Process Flow 1. Mount the Kernel CD-ROM [page 63]. 2. Run the shell script INSTTOOL.SH [page 63]. 3. Customize the installation command file [page 63] if required. 4. Configure tablespaces [page 64] if required. 5. Start INSTGUI [page 64]. 6. Set the library path environment variable [page 65]. 7. Run R3SETUP [page 66]. 8. Set the password for user adm [page 68]. 9. Create the user for LDAP directory access [page 68] if required. 10. AIX only: Check the settings for OS users [page 68]. Do not log on to the SAP System during the installation The SAP System is not in a complete and consistent state before the installation is completed. Do not log on until the installation is finished. 62 July 2000
  63. SAP AG 3 The SAP System Installation 3.1 Central System Installation Mounting the Kernel CD-ROM 1. Log on as user root. 2. Mount the SAP Kernel CD-ROM as described in Mounting a CD-ROM [page 161]. Mount the CD-ROM locally. It is not recommended to use NFS. Running the Shell Script INSTTOOL.SH 1. Log on as user root 2. Change to the installation directory: cd 3. Start the shell script from the CD by entering: /UNIX/INSTTOOL.SH Customizing the Installation Command File After you have run the shell script, you may modify the command file manually. You do not need to customize the installation command file in a standard installation. Command files can be recognized by the file ending .R3S. If you want to edit the command file, see R3SETUP Command Files [page 133]. The section [Z_ORACREATETSP] is no longer located in the command file .R3S as of R/3 Release 4.6A. See Configuring Tablespaces [page 64] if you want to change tablespace configuration. You must save the modified command file before starting R3SETUP. If you change the command file after R3SETUP has been started, the changes have no effect. If you have several CD-ROM drives available, you can enter the CD mount points in the command file before starting R3SETUP. See Required CD-ROMs for Database Installation [page 70]. July 2000 63
  64. 3 The SAP System Installation SAP AG 3.1 Central System Installation Configuring Tablespaces Use This procedure tells you how to alter the configuration of tablespaces in your Oracle database. During installation, R3SETUP uses the file DBSIZE.TPL to create a profile to build the database. For more information, see the step DBCREATETSP_IND_ORA and the class CoraCreateTsp in the online documentation for R3SETUP. To change the sizes of the tablespaces, you copy the DBSIZE.TPL file from the EXPORT CD to your installation directory and then edit it as required. R3SETUP always looks for the DBSIZE.TPL file in the installation directory first. Prerequisites Be sure to complete this procedure before starting R3SETUP. Procedure 1. Mount the EXPORT CD. 2. Copy the DBSIZE.TPL file to the installation directory as follows: cp /DB/ORA/DBSIZE.TPL 3. Edit the DBSIZE.TPL file in the installation directory as required. Do not change tablespace names. When you upgrade the database later on, the original tablespace names are required. Starting INSTGUI If you want to use INSTGUI, the graphical user interface for R3SETUP, and it has not been started by the shell script, you need to start it before starting R3SETUP. To do this, enter the command: cd ; ./INSTGUI You can start INSTGUI on a remote computer. If you are using INSTGUI, make sure that your DISPLAY environment variable is set correctly. If you are not using INSTGUI, make sure that default port 59595 is not used by any other application. See The R3SETUP Tool [page 129] for details and for information on using INSTGUI. 64 July 2000
  65. SAP AG 3 The SAP System Installation 3.1 Central System Installation Setting the Library Path Environment Variable Use You need to set the library path environment variable of user root before starting R3SETUP. Procedure Set the library path environment variable according to the following tables: Value of Library Path Environment Variable Oracle DB Version Operating System Variable Value 8.0.x AIX 64-Bit /sapmnt/ /exe: \ /oracle/ /lib64 All other UNIX /sapmnt/ /exe: \ operating systems /oracle/ /lib 8.1.6 All 32-Bit UNIX /sapmnt/ /exe: \ operating systems /oracle/ /816_32/lib 64-Bit AIX /sapmnt/ /exe: \ /oracle/ /816_64/lib64 64-Bit HP-UX 11.0, The library environment variable must not 64-Bit Sun Solaris be set before starting R3SETUP. Compaq Tru64 UNIX, /sapmnt/ /exe: \ 64-Bit ReliantUNIX /oracle/ /816_64/lib Name of Library Path Environment Variable Operating System Variable Name AIX LIBPATH HP-UX SHLIB_PATH All other UNIX operating systems LD_LIBRARY_PATH If you restart R3SETUP at a later time, make sure the variable is still set. July 2000 65
  66. 3 The SAP System Installation SAP AG 3.1 Central System Installation Running R3SETUP for Central System Installation Use If you install the central instance and the database on the same host, use the command file CENTRAL.R3S to install the central instance. Controlled by this command file, R3SETUP will continue with the database installation once the central instance is installed. As of release 4.6C, there is no longer a command file CENTRDB.R3S for the installation on UNIX - Oracle. Prerequisites If you want to use LDAP (Lightweight Directory Access Protocol) directory services, make sure you installed the required LDAP library (see Checking Requirements for in Hardware and Software Requirements Check [page 28]). Procedure 1. Start R3SETUP as user root. Enter: cd ; ./R3SETUP -f CENTRAL.R3S 2. When you are prompted for the version of the Oracle server software, make sure that you enter the correct version. 3. When you are prompted for LDAP support, take account of the following table. Prompt Entry Active Directory Select this option to integrate Windows 2000 Active Directory services. Service An Active Directory must be available on the network. If you select Active Directory Service, subsequent prompts ask for: • Management Domain SAP Systems can be organized in management domains which are containers for SAP Systems to simplify administration. Specify a container in the Active Directory where information related to the new SAP System is to be stored. Use the distinguished name syntax. The name of the container (management domain) can reflect the organizational structure of your company. For example, if the system is for corporate finances and located in Walldorf, the name can be: CN=Finance,CN=Walldorf • LDAP Servers Enter the DNS host name of the server on which the LDAP directory is running. If the directory is replicated on other servers in the network, specify these as well. For example: ldapsrv1 ldapsrv2 If your DNS server is running on a Windows 2000 machine, this entry is optional as the DNS server is able to find all LDAP servers by itself. • ADS Domain Specify the DNS domain which contains the LDAP servers for the Active Directory, e.g. nt5.sap.com. 66 July 2000