SR3 ABAP+Java on AIX: IBM DB2 for Linux,

Transcription

1 PUBLIC Installation Guide SAP NetWeaver 7.0 SR3 ABAP+Java on AIX: IBM DB2 for Linux, UNIX, and Windows Including the following: SAP NetWeaver ABAP Application Server (AS-ABAP) SAP NetWeaver Java Application Server (AS-Java) SAP NetWeaver Business Intelligence Java Components (BI) SAP NetWeaver Development Infrastructure (DI) SAP NetWeaver EP Core (EPC) SAP NetWeaver Enterprise Portal (EP) SAP NetWeaver Mobile Infrastructure (MI) SAP NetWeaver Process Integration (PI) Application Sharing Server (Optional Standalone Unit) Target Audience System administrators Technology consultants Document version: /28/2008

2 Document History Before you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace The following table provides an overview on the most important document changes: Version Date Description 1.0 3/28/2008 Initial version 2/206 PUBLIC 03/28/2008

3 Table of Contents Chapter 1 Introduction New Features SAP s for the Installation Online Information from SAP Naming Conventions DB2 Product Documentation Chapter 2 Planning Basic System Variants How to Distribute Instances to Hosts Production Client Considerations SAP System Transport Host Basic SAP System Parameters Running Adobe Document Services on Nonsupported Platforms Setup of Database Layout Required File Systems for DB2 for Linux, UNIX, and Windows Users and Groups DB2 Tablespaces Creating Tablespaces Manually (Optional) MCOD Tablespaces and File Systems Optimization of Database Size on Disk Data Safety and Performance Considerations for Database Directories Performance Considerations for Large Databases High Availability: Planning the Switchover Cluster Chapter 3 Preparation High Availability: Switchover Preparations Preparing for Switchover Setting Up File Systems for a High-Availability System Configuring Network File System Hardware and Software Requirements Running the Prerequisite Checker in Standalone Mode (Optional) Requirements for AIX Requirements for a Central System Requirements for a Distributed or a High Availability System /28/2008 PUBLIC 3/206

4 Requirements for the Central Services Instance Requirements for the Central Instance Requirements for the Database Instance Requirements for a Dialog Instance Setting up Swap Space for AIX Creating Operating System Users Network Information Service Creating Operating System Users and Groups Creating AIX Groups and Users (Optional) Setting Up File Systems and Raw Devices SAP Directories Directory Structure of the New DB2 Client Connectivity Setting Up File Systems and Raw Devices for AIX Exporting and Mounting the Global Transport Directory Exporting and Mounting Directories via NFS for AIX (Optional) Installing the Front-End Software Generating the SAP Solution Manager Key Installing the Java Development Kit Preparing and Mounting the Installation Media Preparing the Installation DVDs Downloading Installation DVDs from SAP Service Marketplace (Optional) Mounting a CD / DVD for AIX Chapter 4 Installation Enabling a Non-Unicode Database for the Installation of a Java Add-In for ABAP Performing a High-Availability Installation Prerequisites before Starting SAPinst Prerequisites before Starting SAPinst: All Instances Prerequisites before Starting SAPinst: Distributed Instances Prerequisites Before Starting SAPinst: High Availability Installing an SAP System Using SAPinst Running SAPinst on UNIX Installing the Java Add-In for an Existing ABAP System (Optional) Using SAPinst GUI Interrupted Installation with SAPinst Performing a Remote Installation with SAPinst (Optional) Starting SAPinst GUI Separately (Optional) Entries in the Services File Created by SAPinst Chapter 5 Post-Installation Logging On to the Application Server Logging on to the Portal /206 PUBLIC 03/28/2008

5 5.3 Logging on to SAP NetWeaver Development Infrastructure (NWDI) Installing the SAP License Installing the SAP Online Documentation Configuring Remote Connection to SAP Support Applying the Latest Kernel and Support Packages Performing Initial ABAP Configuration Performing the Client Copy Enabling Recoverability of the Database Performing a Full Installation Backup Post-Installation Steps for Adobe Document Services Assigning Roles to Users ADSUSER and ADS_AGENT Checking the IIOP Service and the Startup Properties Installation Check and Quick Tests for Adobe Document Services Setting Environment Variable CPIC_MAX_CONV Post-Installation Steps for Usage Type Process Integration (PI) Performing PI-Specific Steps for SLD Configuration Post-Installation Steps for the Application Sharing Server High Availability: Post-Installation Steps Setting Up Licenses Taking Precautions for Transport Ensuring User Security Running the Configuration Wizard Checking the SAP Java Documentation Accessing Configuration Documentation in SAP Solution Manager Post-Installation Steps for the Diagnostics Agent Chapter 6 Additional Information Installation of Multiple Components in One Database (Optional) Integration of LDAP Directory Services (Optional) Installation of Additional Software Units or Usage Types in an Existing SAP System Starting and Stopping SAP System Instances Starting and Stopping SAP System Instances Using the SAP Management Console Starting and Stopping SAP System Instances Using Scripts Starting and Stopping the Diagnostics Agent Using Scripts Creating a User for LDAP Directory Access (Optional) Configuring User Management to Use an LDAP Directory (Optional) Usage Type-Specific Initial Technical Configuration Initial Technical Configuration for the Application Server Java (AS Java) Initial Technical Configuration for Adobe Document Services /28/2008 PUBLIC 5/206

6 Initial Technical Configuration for Composite Application Framework Core (CAF) Initial Technical Configuration for the System Landscape Directory (SLD) Initial Technical Configuration for Development Infrastructure (DI) Initial Technical Configuration for the Portal (Usage Types EPC and EP) Initial Technical Configuration for Process Integration (PI) Importing the SAP Exchange Profile Assigning SAP_ALL Rights to User PISUPER Activating the ICF Services Assigning Roles to Groups Initial Technical Configuration for BI Java Configuring BI Java Information Broadcasting Process Chains: Transporting Texts for the Alert Category Renaming initialpermissionsbi.xml.template Heterogeneous SAP System Installation Adding Database Partitions to a Database Instance Troubleshooting Troubleshooting with SAPinst Troubleshooting for Portal Installation Deleting an SAP System Running SAPinst to Delete an SAP System Deleting an SAP System Manually Deleting an SAP Instance Deleting Installation Files, Directories, and Users on a Host Deleting the Java Part of an SAP System Deleting a Database Schema Manually (Optional) Deleting the Database and the DB2 Instance Manually (Optional) Deleting the DB2 Software Installation /206 PUBLIC 03/28/2008

7 1 Introduction 1 Introduction This document explains how to install SAP NetWeaver 7.0 Support Release 3 (SR3) ABAP+Java. It also explains how to install the Java Add-In for an existing SAP NetWeaver 7.0 SR3 ABAP system. SAP NetWeaver 7.0 Support Release 3 corresponds to SAP NetWeaver 7.0 Support Package Stack (SPS) 14. For more information about the SAP NetWeaver technology, see You can install SAP NetWeaver 7.0 SR3 ABAP+Java with the following usage types in a single installation run using SAPinst: Only valid for: Application Server (AS) SAP NetWeaver Application Server ABAP (AS ABAP) AS ABAP is not installed with the Java Add-In. End of: Application Server (AS) SAP NetWeaver Application Server Java (AS Java) Only valid for: Development Infrastructure (DI) SAP NetWeaver Development Infrastructure (DI) End of: Development Infrastructure (DI) Only valid for: EP Core (EPC) SAP NetWeaver EP Core (EPC) End of: EP Core (EPC) Only valid for: Enterprise Portal (EP) SAP NetWeaver Enterprise Portal (EP) If you install usage type EP, note the following: You must install SAP NetWeaver Application Server Java (AS Java) and EP Core (EPC). The Application Sharing Server is installed automatically with usage type EP. For production use, we recommend that you install the server as an optional standalone unit on a dedicated host as described in the documentation Installation Guide <your product> Java on <OS>: <Database>. End of: Enterprise Portal (EP) 03/28/2008 PUBLIC 7/206

8 1 Introduction Only valid for: BI Java SAP NetWeaver Business Intelligence Java Components (BI Java) You also have to install SAP NetWeaver Application Server Java (AS Java), EP Core (EPC) and SAP NetWeaver Portal (EP). End of: BI Java Only valid for: Mobile Infrastructure (MI) SAP NetWeaver Mobile Infrastructure (MI) End of: Mobile Infrastructure (MI) Only valid for: Process Integration (PI) SAP NetWeaver Process Integration (PI) End of: Process Integration (PI) For more information about the usage types of SAP NetWeaver and their interdependencies, see the document Master Guide SAP NetWeaver 7.0 at For restrictions, see SAP Installation of Additional Software Units or Usage Types in an Existing SAP System If you want to install additional Java software units or usage types in an existing SAP system based on SAP NetWeaver 7.0 SR3 (Support Package Stack (SPS) 14), you have to use the Java Support Package Manager (JSPM). You cannot use SAPinst to install additional software units or usage types in an existing SAP system. Existing SAP system means that it has at least AS Java. As of SAP NetWeaver 7.0 SPS 12, you can use Install Additional Usage Types in JSPM to install and activate additional software units or usage types. For more information, see Installation of Additional Software Units or Usage Types in an Existing SAP System [page 161]. Only valid for: Process Integration (PI) You cannot install PI as an additional UT with the procedure described in SAP You can only install an SAP system with PI as a new installation. End of: Process Integration (PI) Constraints You need to consider the following constraints before you start your installation: Your operating system platform must be 64-bit. You must only use the SAP installation tools according to the instructions and for the purposes described in the SAP installation document. Improper use of the SAP installation tools can damage files and systems already installed. 8/206 PUBLIC 03/28/2008

9 1 Introduction 1.1 New Features SAP system installations should only be performed by SAP Technical Consultants certified for your operating system, your database, and the SAP system that you are installing. For downward-compatible releases of DB/OS platforms for SAP products, SAP plans to regularly release the newest database (DB) and operating-system (OS) versions of SAP products. These releases are downward-compatible with earlier SAP system releases. that for already shipped SAP components, we only support the installation for database versions proposed by the installation tool. Therefore, you must install an SAP component or perform a system copy using a downward-compatible database as follows: Install the component with the old proposed database version. Upgrade the old database version to the downward-compatible new version. 1.1 New Features The following tables provide an overview of the new features related to the installation of this release: Make sure that you read the release notes for your SAP system. You can find these at SAP System Installation Area SAPinst Description As of SAP NetWeaver 7.0, SAPinst has the following new features: You can check the prerequisites for your SAP system installation with the Prerequisite Checker [page 62]. You can install a central system in one of two modes: Typical Mode If you choose Typical, your SAP system is installed with default settings. As a result, you only have to respond to a small selection of prompts. If you want to change any of the default settings, you can do so on the parameter summary screen at the end of the installation. Custom Mode If you choose Custom, you must manually enter all installation parameters. You can change your values on the parameter summary screen at the end of the installation. You can uninstall an SAP system or an SAP component with the SAPinst service Uninstall System / Standalone Engines / Optional Standalone Unit. You can install the Java Add-In for an existing ABAP system. This means that you run SAPinst to execute the following: Install the central services instance (SCS) Add the Java database schema to the existing ABAP database instance Add the Java central instance with usage types to the existing ABAP central instance 03/28/2008 PUBLIC 9/206

10 1 Introduction 1.1 New Features Area Description The installation of the Java Add-In for an existing ABAP system is described in the documentation Installation Guide <your product> ABAP+Java on <OS>: <Database> available at You cannot install the Java Add-In for existing ABAP dialog instance(s). Instead, you have to install new ABAP+Java dialog instance(s). Installation DVDs SAP Solution Manager Key SAP NetWeaver Administrator SAP Solution Manager Diagnostics Agent The sapinst group ID must be the secondary group of the users root and <sapsid>adm. For more information, see Creating Operating System Users and Groups Manually [page 73]. You can install SAP NetWeaver as a high-availability (HA) system. You can change the default names of the Java users J2EE_ADMIN, J2EE_GUEST and SAPJSF during the input phase of the installation. You assign one master password to all users created by SAPinst. This password is used for all user accounts and for the secure store key phrase. SAPinst fills in most of the input parameter fields with default values. If required, you can change the default values on the Parameter Summary screen before you start the actual installation. You no longer have to manually activate sapcpe. The kernel is replicated automatically from /usr/sap/<sapsid>/sys/exe/run/dir_ct_run to /usr/sap/<sapsid>/<instance>/exe/dir_executable for each SAP system instance. For more information, see Setting Up File Systems [page 76]. You start the installation from a single Installation Master DVD. You require a key to install your SAP system. You generate this key with your SAP Solution Manager [page 89]. SAP NetWeaver Administrator is a brand new solution for monitoring and administering Java systems and their applications. For more information, see the SAP NetWeaver Master Guide and the following: Lifecycle Management Operations Knowledge Center Administration A SAP Solution Manager Diagnostics Agent (Diagnostics Agent) is a standalone Java program that runs on each of the systems managed by SAP Solution Manager Diagnostics. It gathers information and reports to the SAP Solution Manager system. For more information about the Diagnostics Agent, see The installation of the Diagnostics Agent is now part of the Installation Master DVD. That is, you can choose between the following options: If there is no Diagnostics Agent already installed on this physical or virtual host, it is installed automatically with an AS Java central instance and dialog instance. You can install it as a standalone engine. 10/206 PUBLIC 03/28/2008

11 1 Introduction 1.1 New Features Area 64-bit support for all instances except dialog instances Only Unicode support for new installations Maintenance Optimizer Description If you want to use 32-bit SAP NetWeaver components, first check whether these components can run on 64-bit operating systems. If so, we recommend that you use 64-bit systems. If not, you can install an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP instances, you must use 64-bit systems Every newly installed SAP system is a Unicode system. However, non-unicode is still supported for copied and upgraded systems. All downloadable software components based on SAP NetWeaver 7.0 and subsequent versions released after April 2, 2007 are available exclusively through the Maintenance Optimizer in SAP Solution Manager. This comprises: Support Package Stacks, Support Packages, and patches for Java instances, except for kernel patches Legal changes SAP applications and versions that are: Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and all applications based on this software, including SAP Business Suite 2005 (and subsequent versions) Optional for all SAP applications For more information, see Operating Systems and Platforms Area Support of Operating Systems and Platforms Description For supported operating system and database releases, see the Product Availability Matrix at For forums, blogs, content, and community related to all of the supported databases and operating systems, see the Database and Operating Systems area at Database-Specific Features Area SAP system installation Description SAP systems that are based on SAP NetWeaver 7.0 SR3 and higher are installed on IBM DB2 Version 9.1 or Version 9.5 for Linux, UNIX, and Windows - in the following referred to as DB2 V9.1 and DB2 V9.5. As of DB2 V9, you can have multiple DB2 installations on one physical machine. The database installations are independent of each other and can have different Fix Pack levels as well as different configuration settings and so on. By default, the software is installed in the following directory: /db2/db2<dbsid>/db2_software. 03/28/2008 PUBLIC 11/206

12 1 Introduction 1.1 New Features Area Reduction of database size Description You can significantly reduce the size of your database by selecting the following options in SAPInst during the dialog phase: Use DB2 s Row Compression DB2 s row compression (also known as deep compression) transparently compresses table data in your database, using a dictionary-based compression algorithm. Using row compression typically reduces the size of tables by 60 to 80%. As a result, the size of the database decreases by approximately 30 to 55 %. Use Deferred Table Creation Before you use this function, make sure that you read SAP The SAP function deferred table creation delays the creation of empty database tables until the first row is inserted. That is, until the first row is inserted, the table is substituted by a virtual table (which effectively is a special database view). As soon as the first row is inserted, the SAP kernel transparently replaces the virtual table with a database table. Depending on the number of tables that remain empty over your system lifetime, the use of deferred table creation can reduce the size of your database by several GB. For more information, see Optimization of Database Size on Disk [page 47]. DB2 software installation Support of IBM Tivoli System Automation for Multiplatforms (SA MP) by SAPinst Self Tuning Memory Management (STMM) New DB2 Client Connectivity SAPinst automatically installs and deinstalls the database software. SAPinst supports the use of IBM Tivoli System Automation for Multiplatforms (SA MP) to make your database high-available. For more information, see the document IBM DB2 High Availability Solution: IBM Tivoli System Automation for Multiplatforms that you can find at SAP on DB2 for Linux, UNIX, and Windows Knowledge Center Key Topics Installation and Upgrade SAPinst automatically enables the DB2 feature Self Tuning Memory Management (STMM). STMM automatically tunes global memory depending on the workload of the database. You no longer have to install DB2 software on the additional application server (formerly known as dialog instance). Instead, the CLI Driver that is centrally stored in the global directory is used. During the installation of the database instance, the DB2 CLI driver is automatically installed for the operating system of the database server. If you install an additional application server (that is, the first one on an additional operating system in your system landscape), SAPinst automatically installs the DB2 CLI driver for this operating system. 12/206 PUBLIC 03/28/2008

13 1 Introduction 1.2 SAP s for the Installation Area Description Every time you start an SAP instance, the CLI driver is copied from the global directory to the local exe directory of this SAP instance. The JDBC Driver is automatically installed by SAPinst into the global directory. You can update the JDBC driver automatically using a script whenever you install a new Fix Pack version of the database. Every time you start an SAP instance, the JDBC driver is copied from the global directory to the local exe directory of this SAP instance. For more information, see Directory Structure of the New DB2 Client Connectivity [page 83]. Documentation Area Installation of Additional Software Units or Usage Types SAP s Links in PDF files Description The documentation on how to install additional software units or usage types to an existing SAP system is now included in the installation guides. Up to now this documentation was only available in SAP You can now access SAP s directly in SAP Service Marketplace from your PDF. Place the cursor on the SAP <number> and double-click. A separate browser window opens to display the SAP. You can use the new links in the PDF files of the guides as follows: Click the section headings such as New Features to jump back to the table of contents at the beginning of the guide. Click an internet link such as to jump to the corresponding internet page. 1.2 SAP s for the Installation You must read the following SAP s before you start the installation. These SAP s contain the most recent information on the installation, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP, which you can find at 03/28/2008 PUBLIC 13/206

14 1 Introduction 1.3 Online Information from SAP SAP s for the Installation SAP Number Title Description SAP NetWeaver 7.0 SR3 / Business Suite 2005 SR3 UNIX Release Restrictions for SAP NetWeaver DB6: SAP NetWeaver 7.0 SR3 / Business Suite 2005 SR3 - UNIX DB6: Supporting several database partitions with DB DB6: Required and recommended AIX fixes for DB2 UNIX-specific information about the SAP system and corrections to this documentation. Customer information on restrictions in the production use of certain functions. Database-specific information about the SAP system installation (ABAP and Java) and corrections to this documentation. Platform-specific additional information about the support of multiple partitions with DB2 for Linux, UNIX, and Windows Important information if your operating system is AIX Installation Prerequisite Checker SAP Software on UNIX, Windows and System i: Checking OS Dependencies Supported Languages and Code Pages Hardware requirements of Java Development Infrastructure SAP Mobile Infrastructure 7.0 Release to MAXDB Central for Heterogeneous Installation Installing SAP Systems into an Independent ASP (iasp) Information on possible languages and language combinations in SAP systems Information on the hardware requirements for usage type Development Infrastructure (DI), which depends on the size of your development team. This note contains additional information about SAP Mobile Infrastructure installation 7.0 for all support package stacks. Heterogeneous ABAP system landscapes on different operating systems have been released for some time. Heterogeneous Java system landscapes on different operating systems have now also been released. However, not every combination of operating system and database system is released. This SAP and its related SAP s describe the released operating system and database combinations. Information on features and limitations for installations into independent ASP. 1.3 Online Information from SAP More information is available online as follows. 14/206 PUBLIC 03/28/2008

15 1 Introduction 1.3 Online Information from SAP Documentation Description Internet Address Title Master Guide for SAP NetWeaver 7.0 Technical Infrastructure Guide for SAP NetWeaver 7.0 Master Guide SAP Solution Manager 4.0 List of media for installation or upgrade for SAP NetWeaver 7.0 Installation of SAP Solution Manager 4.0 Configuration of SAP Solution Manager 4.0 Patching of SAP NetWeaver 7.0 scenarios Upgrade to SAP NetWeaver 7.0 Installation of SAP NetWeaver Developer Workplace Installation of SAP NetWeaver Developer Studio Installation of the System Landscape Directory (SLD) Installation of a standalone gateway Installation of Web Dispatcher Front End installation Master Guide SAP NetWeaver SAP Components SAP Solution Manager Release 4.0 Technical Infrastructure Guide SAP NetWeaver 7.0 Master Guide SAP Solution Manager Media List SAP NetWeaver SAP Components SAP Solution Manager Release SAP Components SAP Solution Manager Release SPS <current stack> Support Package Stack Guide SPS <current stack> Installation Upgrade to SAP NetWeaver Systems Upgrade Documentation - SAP NetWeaver 7.0 <SR> Installation Installation Clients Installation SAP Developer Workplace Installation Installation Clients Installation SAP NetWeaver Developer Studio Configuration Post-Installation Guide SLD of SAP NetWeaver Installation Standalone Engines Installation Gateway on <platform> Installation Standalone Engines Dispatcher on <platform> Installation Web Installation Clients <Release> Installation SAP Front End Installation Guide SAP Solution Manager 4.0 on <OS>: <Database> Configuration Guide SAP Solution Manager 4.0 as of <current stack> Support Package Stack Guide SAP NetWeaver 7.0 SPS <current stack> Component Upgrade Guide SAP NetWeaver 7.0 Application Server ABAP Installation Guide Developer Workplace for SAP NetWeaver SAP NetWeaver Developer Studio Standalone Installation Guide Post-Installation Guide System Landscape Directory of SAP NetWeaver 7.0 Installation Guide Gateway on <platform> For SAP Systems Based on SAP NetWeaver 7.0 (2004s) Installation Guide Web Dispatcher on <platform> For SAP Systems Based on SAP NetWeaver 7.0 (2004s) SAP Front End Installation Guide This guide is also available on the Presentation DVD. 03/28/2008 PUBLIC 15/206

16 1 Introduction 1.3 Online Information from SAP Description Internet Address Title Homogeneous and heterogeneous system copy for SAP systems based on NetWeaver 7.0 SAP NetWeaver Problem Analysis Guide Installation SAP NetWeaver Systems System Copy for SAP Systems Based on <Release> <Technology> SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) System Copy Guide System Copy for SAP Systems based on SAP NetWeaver <Release> <Technology> SAP NetWeaver Problem Analysis Guide (PAG) General Quick Links Description SAP Help Portal SAP NetWeaver Library in SAP Help Portal SAP s SAP s for SAP NetWeaver 7.0 installation Forums, blogs, and general information related to all of the supported databases and operating system platforms Product Availability Matrix (PAM) for supported operating system releases Release notes Unicode SAP systems and their availability System sizing (Quick Sizer tool) SAP NetWeaver capabilities Life-cycle management for SAP NetWeaver Landscape design for SAP NetWeaver Application management for SAP NetWeaver High Availability System Landscape Directory Internet Address /206 PUBLIC 03/28/2008

17 1 Introduction 1.4 Naming Conventions Description Software logistics for SAP NetWeaver SAP NetWeaver operations SAP NetWeaver Development Infrastructure Security for SAP NetWeaver Information on SAP Support Package Stacks SAP Solution Manager Maintenance Optimizer End-to-End Root Cause Analysis Internet Address Naming Conventions In this documentation, the following naming conventions apply: Terminology SAP system refers to SAP NetWeaver 7.0 SR3. ABAP+Java system refers to SAP NetWeaver 7.0 SR3 ABAP+Java. Java Add-In refers to the Java Add-In for an existing SAP NetWeaver 7.0 SR3 ABAP system. Diagnostics Agent refers to SAP Solution Manager Diagnostics Agent. IBM DB2 Version 9.1 for Linux, UNIX, and Windows is referred to as DB2 V9.1. IBM DB2 Version 9.5 for Linux, UNIX, and Windows is referred to as DB2 V9.5. If content in this document relates to both versions, no version number is mentioned. Variables Variables <SAPSID> <sapsid> <DBSID> <dbsid> <host_name> <user_home> Description SAP system ID in uppercase letters SAP system ID in lowercase letters Database ID in uppercase letters Database ID in lowercase letters Name of the corresponding host Home directory of the user performing the installation. 03/28/2008 PUBLIC 17/206

18 1 Introduction 1.5 DB2 Product Documentation Variables <INSTDIR> <DVD_DIR> <OS> <SCHEMA_ID> Description Installation directory for the SAP system Directory on which a DVD is mounted Operating system name within a path Database schema ID The following example shows how the variables are used: Example Log on as user <sapsid>adm and change to the directory /usr/sap/<sapsid>. If your SAP system ID is C11, log on as user c11adm and change to the directory /usr/sap/c DB2 Product Documentation PDF Format You can access information on all DB2 manuals (provided as PDF files) at: DB2 V9.1: DB2 V9.5: HTML Format You can access the HTML version of DB2 product documentation at: DB2 V9.1: DB2 V9.5: More Information For more information about web sites that contain important DB2-related documentation, see SAP /206 PUBLIC 03/28/2008

19 2 Planning 2 Planning This section tells you how to plan the installation of your SAP system. You have to complete the following planning activities: 1. You plan your SAP system landscape according to the Master Guide and the Technical Infrastructure Guide available for your product. 2. You choose your basic system variant [page 19]. 3. You plan how to distribute the instances to hosts [page 22]. 4. You decide on your production client [page 25]. 5. You decide on the transport host to use [page 26]. 6. You identify basic SAP system parameters [page 26]. 7. If you want to use Adobe Document Services (ADS), you check what you have to do in case your platform is not supported for ADS [page 39]. 8. You carefully plan the setup of your database [page 40]. 9. Only valid for: HA (UNIX) You plan the switchover cluster [page 51] for a high-availability (HA) system. End of: HA (UNIX) The following planning activity is optional: Installation of Multiple Components in One Database (MCOD) [page 155] This step does not apply to the installation of a Java Add-In to an existing ABAP system. 2.1 Basic System Variants The following section provides information about the basic system variants for an ABAP+Java system and how to distribute SAP instances within them. An ABAP+Java system can be the result either of an ABAP+Java installation or of the installation of a Java Add-In to an existing ABAP system. 03/28/2008 PUBLIC 19/206

20 2 Planning 2.1 Basic System Variants If you want to use 32-bit SAP NetWeaver components, first check whether these components can run on 64-bit operating systems. If so, we recommend you to use 64-bit systems. If not, you can install an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP instances, you must use 64-bit systems. Mandatory instances of an ABAP+Java system are the central instance, the central services instance, and the database instance. The Java central services instance is called SCS instance. The ABAP central services instance is called ASCS instance. The ASCS is only required for a high-availability installation. You can then operate both the ABAP application server and the J2EE Engine on the SAP system. Optionally, you can install one or more dialog instances, if required. the following about dialog instances: We do not support operating an ABAP dialog instance with an ABAP+Java system. You cannot install the Java Add-In for existing ABAP dialog instance(s). Instead, you have to install new ABAP+Java dialog instance(s). Each instance can reside on a separate host. The ASCS and the SCS must reside on the same host. 20/206 PUBLIC 03/28/2008

21 2 Planning 2.1 Basic System Variants Figure 1: Minimum System Distribution (Central System) For a minimum system distribution, all instances reside on one host. Figure 2: Maximum Distribution for a Distributed System For a maximum system distribution, each instance resides on a separate host. 03/28/2008 PUBLIC 21/206

22 2 Planning 2.2 How to Distribute Instances to Hosts Only valid for: HA (UNIX) Figure 3: Maximum Distribution for a High-Availability System End of: HA (UNIX) Only valid for: HA (UNIX) For a maximum system distribution, each instance resides on a separate host. End of: HA (UNIX) 2.2 How to Distribute Instances to Hosts The following provides information on how you can distribute the SAP instances for the different SAP system variants. You use SAPinst to install the SAP instances as a: Central system on a single host You run SAPinst and install all instances on one host. A distributed system on several hosts The following figure shows how to distribute your instances on several hosts: 22/206 PUBLIC 03/28/2008

23 2 Planning 2.2 How to Distribute Instances to Hosts Figure 4: Distribution of Instances in an ABAP+Java System You can use the SAP transport host or the SAP global host as your central instance host. You perform the following steps: 1. If you want to share the transport directory trans from another system, you have to mount it from this system. Otherwise we recommend that you share the trans directory that is created during the installation of the central instance (see below). 2. On the SAP global host, you run SAPinst and install the Java central services instance (SCS). 3. Only valid for: HA (UNIX) On the SAP global host, you run SAPinst and install the ABAP and Java central services instances (ASCS and SCS). End of: HA (UNIX) 4. On the SAP global host, you export the required file systems to the database and central instance host. 5. On the database host, you mount the exported file systems from the SAP global host and SAP transport host. 6. On the database host, you run SAPinst and install the database instance. 7. On the central instance host, you mount the exported file systems from the SAP global host and SAP transport host. 8. On the central instance host, you run SAPinst and install the central instance. 03/28/2008 PUBLIC 23/206

24 2 Planning 2.2 How to Distribute Instances to Hosts 9. If required, you can now install one to <n> dialog instances. The procedure is the same as installing a central instance (replace central instance with dialog instance in the procedure). We do not support operating an ABAP dialog instance with an ABAP+Java system. Java Add-In for an Existing ABAP System If you want to install the Java Add-In for an existing ABAP system, you proceed as follows on the instance host(s) of the ABAP system: Central system on a single host You run SAPinst and install the Java Add-In on one host. Distributed system on several hosts The following figure shows how to distribute your instances on several hosts: Figure 5: 1. On the SAP global host, you run SAPinst to install the Java central services instance (SCS). 2. On the database host, you run SAPinst to install the Java Add-In for the database instance. 3. On the central instance host, you run SAPinst to install the Java Add-In for the central instance. 4. If required, you run SAPinst to install one to <n> ABAP+Java dialog instances. 24/206 PUBLIC 03/28/2008

25 2 Planning 2.3 Production Client Considerations You cannot install the Java Add-In for existing ABAP dialog instance(s). Instead, you have to install new ABAP+Java dialog instance(s). 2.3 Production Client Considerations A client is a self-contained unit in an SAP system with separate master records and its own set of tables. SAPinst creates three ABAP clients during the installation, client 000, client 001, and client 066. As of SAP NetWeaver 7.0 and Business Suite 2005, you can install an ABAP+Java system in one installation run. This means that AS Java is configured by default against ABAP client 001. You can choose one of the following methods to set up your new production client: You install the ABAP and the Java part of your system separately. You install an ABAP+Java system and reconnect the Java part. You install an ABAP+Java system and do not reconnect the Java part. The following procedure describes the above methods. Installing the ABAP and the Java Part of your System Separately 1. You install the ABAP system as described in the documentation Installation Guide <your SAP system application> ABAP on <your OS>: <database>. 2. You perform the client copy [page 133]. 3. You install the Java Add-In for ABAP as described in this installation guide. You can specify the production client to which you want to connect the Java Add-In during the input phase of the installation. Installing an ABAP+Java System and Reconnecting the Java Part If you need the Java users in your ABAP production client, you have to manually configure the connection of the Java part to the ABAP part. For more information about Java users, see the table User Management Engine (UME) in Basic SAP System Parameters [page 26]. 1. You install the ABAP+Java system as described in this documentation. 2. You perform the client copy [page 133]. 3. You reconnect the Java part to the production client as described in SAP Installing an ABAP+Java System Without Reconnecting the Java Part If you do not need the Java users in your ABAP production client, there is no need to manually configure the connection of the Java part to the ABAP part. For more information about Java users, see the table User Management Engine (UME) in Basic SAP System Parameters [page 26]. 03/28/2008 PUBLIC 25/206

26 2 Planning 2.4 SAP System Transport Host 1. You install the ABAP+Java system as described in this documentation. 2. You perform the client copy [page 133]. 2.4 SAP System Transport Host The transport host contains the transport directory that is used by the SAP transport system to store transport data and change information of SAP systems, such as software programs, data dictionary data, or customization data. If you have several SAP systems they are usually organized in transport domains. In most cases, all SAP systems in a transport domain have a common transport directory. For more information, see: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics Change and Transport System Change and Transport System Overview (BC-CTS) Basics of the Change and Transport System Transport Management System Concept When you install an SAP system, SAPinst by default creates the transport directory on the central instance host in /usr/sap/trans. You have to prepare this host for use by the new SAP system if one of the following applies to you: You want to locate the transport directory on another host. You want to use an existing transport host and directory in your SAP system landscape. For more information, see Exporting and Mounting the Global Transport Directory [page 87]. More Information Setting Up File Systems and Raw Devices [page 76] 2.5 Basic SAP System Parameters The tables below list the basic system parameters that you need to determine before installing your SAP system. For all other SAP system parameters, use the F1 help in the SAPinst dialogs. In the column Enter Your Values, you write down the values that you plan to use, for example, the Message Port Number. 26/206 PUBLIC 03/28/2008

27 2 Planning 2.5 Basic SAP System Parameters SAP System ID and Database ID Parameters Description Enter Your Values SAP System ID <SAPSID> The SAP System ID <SAPSID> identifies the whole SAP system.... Database ID <DBSID> Choose your SAP system ID carefully. You cannot change the SAP system ID after the installation. Make sure that your SAP system ID: Is unique throughout your organization Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs: ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID USR VAR The <DBSID> identifies the database instance. SAPinst prompts you for the <DBSID> when you are installing the database instance. The <DBSID> can be the same as the <SAPSID>.... Choose your database ID carefully. Renaming is difficult and requires you to reinstall the SAP system. If you want to install a new database: Make sure that your database ID: Is unique throughout your organization Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs: ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID USR VAR If you want to use an existing database system: 03/28/2008 PUBLIC 27/206

28 2 Planning 2.5 Basic SAP System Parameters Parameters Description Enter Your Values Enter exactly the database ID of the existing database to which you want to add the system. System ID <SMDSID> of SAP Solution Manager Diagnostics Agent SAPinst sets <SMDSID> to SMD by default. If SMD is already used by another SAP system that is not a Diagnostics Agent system, <SMDSID> is set to DA<x>, where <x> can be any letter from A to Z, and DA stands for DiagnosticsAgent ). If required, you can change <SMDSID> to a value of your choice on the Parameter Summary screen. If you do so, the same naming conventions as for <SAPSID> apply. For more information, see entry SAP System ID <SAPSID> in this table above.... SAP System Instances, Hosts and Ports Parameters Description Enter Your Values Instance Number of the SAP system Instance Number for the Diagnostics Agent Name of Instance Host Message Server Port Technical identifier for internal processes. It consists of a two-digit number from 00 to 98. The instance number must be unique on a host. That is, if more than one SAP instance is running on the same host, these instances must be assigned different numbers. To find out this number, look under the SAP directory /usr/sap/<sapsid>/dvebmgs<nn> on the host of the central instance. The value <nn> is the number assigned to the central instance. Technical identifier for internal processes for the Diagnostics Agent, consisting of a two-digit number from 00 to 98. The instance number is set automatically to the next free and valid instance number that has not yet been assigned to the SAP system. The same restrictions apply as in Instance Number of the SAP system (see above). Instance Host: Host name of the specific instance. To find out the host name, open a command prompt and enter hostname. The host name must not exceed 12 characters. For more information about the allowed host name length and characters, see SAP The message server port number must be unique for the SAP system on all hosts. If there are several message port numbers on one host, all must be unique. Port number of the SAP Message Server: If you do not specify a value, the default port number is used. ABAP Message Server Port /206 PUBLIC 03/28/2008

29 2 Planning 2.5 Basic SAP System Parameters Parameters Description Enter Your Values There is an external message server port and an internal message server port. The ABAP message server uses both the internal and the external message server ports. The default profile contains the configuration for both message server ports. The external message server port uses the parameter rdisp/msserv with default value 36<nn>, where <nn> is the instance number of the ABAP message server instance. The internal message server port uses the parameter rdisp/msserv_internal with default value 39<nn>, where <nn> is the instance number of the ABAP message server instance. Java Message Server Port The Java message server only uses the internal message server port. The SCS instance profile contains the configuration for the Java message server. The parameter rdisp/msserv is set to 0, so that the external port is not open. The internal message server port uses the parameter rdisp/msserv_internal with default value 39<nn>, where <nn> is the instance number of the SCS message server instance. For more information about the parameters used for message server ports, see SAP Master Password Parameters Description Enter Your Values Master Password This password is used for all user accounts SAPinst creates and for the secure store key phrase. The length has to be 8 to 14 characters. Depending on your installation scenario there might be more restrictions.... If you do not create the operating system users manually, SAPinst creates them with the common master password (see Operating System Users ). In this case, make sure that the master password meets the requirements of your operating system and of your database. 03/28/2008 PUBLIC 29/206

30 2 Planning 2.5 Basic SAP System Parameters Operating System Users Parameters Description Enter Your Values Password of Operating System Users SAPinst processes the passwords of operating system users as follows: If the operating system users do not exist, SAPinst creates the following users: <sapsid>adm This user is the SAP system administrator user. <smdsid>adm This user is dedicated to the Diagnostics Agent installation with sufficient authorization to manage the agent. It is created on the central instance host and on every dialog instance host. SAPinst sets the master password for these users by default. You can overwrite and change the passwords either by using the parameter mode Custom or by changing them on the parameter summary screen. If the operating system users already exist, SAPinst prompts you for the existing password, except if the password of these users is the same as the master password. Make sure that the user ID and group ID of these operating system users are unique and the same on each relevant application server instance host. For more information, see Creating Operating System Users [page 72].... User Management Engine (UME) Parameter Description Enter Your Values ABAP Client The production client of the ABAP system... DDIC Password This is only relevant for a Java Add-In installation. The existing password of the DDIC user... Java Administrator User This is only relevant for a Java Add-In installation. This user is created by SAPinst in the ABAP system. After the installation, this user is available both in the ABAP and in the Java system SAPinst sets the user name J2EE_ADMIN and the master password by default. If required, you can choose another user name and password according to your requirements. For more information about supported UME data sources and change options, see SAP /206 PUBLIC 03/28/2008

31 2 Planning 2.5 Basic SAP System Parameters Parameter Description Enter Your Values Java Guest User Communication User This user is for employees who do not belong to a company or who have registered as company users and who are waiting for approval. Guest users belong to the default group Authenticated Users. This user is created by SAPinst in the ABAP system. After the installation, it is available both in the ABAP and in the Java system SAPinst sets the user name J2EE_GUEST and the master password by default. If required, you can choose another user name and password according to your requirements. For more information about supported UME data sources and change options, see SAP This user is created by SAPinst in the ABAP system. After the installation, it is available both in the ABAP and in the Java system This user is used for the communication between the ABAP system and the Java system. SAPinst sets the user name SAPJSF and the master password by default. If required, you can choose another user name and password according to your requirements. For more information about supported UME data sources and change options, see SAP Key Phrase for Secure Store Settings Parameters Description Enter Your Values Key Phrase for Secure Store Settings This is a random word or phrase that is used to encrypt the secure store. The Java EE engine uses this phrase to generate the key that is used to encrypt the data. The uniqueness of the phrase you use contributes to the uniqueness of the resulting key.... Recommendation Use a long key phrase that cannot be guessed easily. Use both uppercase and lowercase letters in the phrase and include special characters. 03/28/2008 PUBLIC 31/206

32 2 Planning 2.5 Basic SAP System Parameters Internet Communication Manager (ICM) User Management Parameter Description Enter Your Values Password of webadm The administration user webadm is created to use the web administration interface for Internet Communication Manager (ICM) and Web Dispatcher. SAPinst sets the master password by default. If required, you can choose another password. The length of the password must be between 5 and 128 characters.... Solution Manager Key Parameters Description Enter Your Values SAP Solution Manager key To install your SAP system, you need to generate an SAP Solution Manager key [page 89], which the installation requires to continue. For more information, see SAP Parameters Relevant for the Connectivity to System Landscape Directory (SLD) Parameters Description Enter Your Values SLD Destination SLD HTTP Host SLD HTTP Port The System Landscape Directory (SLD) is designed for registering the systems (along with the installed software) of your whole system landscape. The usual case is to configure one SLD for your complete system landscape. For more information, see Configuring System Landscape Directory [page 179]. The host name of the System Landscape Directory (SLD) The HTTP port of the Java system where the SLD is installed. The following naming convention applies: 5<instance_number> Example If the instance number of your Java system is 01, the SLD HTTP Port is /206 PUBLIC 03/28/2008

33 2 Planning 2.5 Basic SAP System Parameters Parameters Description Enter Your Values SLD Data Supplier User and password If you want to install a local SLD, SAPinst creates this user during the installation. If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation.... SLD ABAP API User and password Recommendation We recommend that you name this user SLDDSUSER If you want to install a local SLD, SAPinst creates this user during the installation. If you want to connect your system to an existing central SLD, you have to enter the existing SLD Data Supplier User and password of the central SLD during the installation.... Recommendation We recommend that you name this user SLDAPIUSER RFC User, Password The ABAP RFC user of the SLD... SLD Gateway Host SLD Gateway Instance Number The host on which the gateway instance of the SLD is running The instance number of the gateway instance of the SLD SAP System Client The client in which the ABAP RFC user exists Parameters Relevant for Adobe Document Services (ADS) Parameters Description Enter Your Values User for basic authentication User for processing forms between an ABAP and a Java environment SAPinst sets the user name ADSUSER and the master password by default. If required, you can choose another password according to your requirements. SAPinst sets the user name ADSAGENT and the master password by default. If required, you can choose another password according to your requirements /28/2008 PUBLIC 33/206

34 2 Planning 2.5 Basic SAP System Parameters Only valid for: Development Infrastructure (DI) Parameters Relevant for SAP NetWeaver Development Infrastructure (NWDI) Parameters Description Enter Your Values Administrator of the SAP NetWeaver Development Infrastructure (NWDI) and Password Developer in the SAP NetWeaver Development Infrastructure (NWDI) and Password Landscape Directory Service User in the SAP NetWeaver Development Infrastructure (NWDI) and Password SAPinst sets the user name NWDI_ADM and the master password by default. If required, you can choose another password according to your requirements. SAPinst sets the user name NWDI_DEV and the master password by default. If required, you can choose another password according to your requirements. SAPinst sets the user name NWDI_CMSADM and the master password by default. If required, you can choose another password according to your requirements End of: Development Infrastructure (DI) Only valid for: Process Integration (PI) Parameters Relevant for Process Integration (PI) Parameters Description Enter Your Values Integration Repository Service User and Password SAPinst sets the user name PIREPUSER and the master password by default. If required, you can choose another user name and password according to your requirements.... Integration Directory Service User and Password If you want to choose another user name, make sure that this user name starts with PI. SAPinst sets the user name PIDIRUSER and the master password by default. If required, you can choose another user name and password according to your requirements.... If you want to choose another user name, make sure that this user name starts with PI. 34/206 PUBLIC 03/28/2008

35 2 Planning 2.5 Basic SAP System Parameters Parameters Description Enter Your Values Landscape Directory Service User and Password SAPinst sets the user name PILDUSER and the master password by default. If required, you can choose another user name and password according to your requirements.... Integration Server Application User and Password If you want to choose another user name, make sure that this user name starts with PI. SAPinst sets the user name PIAPPLUSER and the master password by default. If required, you can choose another user name and password according to your requirements.... Runtime Workbench Service User and Password If you want to choose another user name, make sure that this user name starts with PI. SAPinst sets the user name PIRWBUSER and the master password by default. If required, you can choose another user name and password according to your requirements.... Adapter Framework Server Service User and Password If you want to choose another user name, make sure that this user name starts with PI. SAPinst sets the user name PIAFUSER and the master password by default. If required, you can choose another user name and password according to your requirements.... Integration Server Service User and Password If you want to choose another user name, make sure that this user name starts with PI. SAPinst sets the user name PIISUSER and the master password by default. If required, you can choose another user name and password according to your requirements.... If you want to choose another user name, make sure that this user name starts with PI. 03/28/2008 PUBLIC 35/206

36 2 Planning 2.5 Basic SAP System Parameters Parameters Description Enter Your Values Management Server Service User and Password SAPinst sets the user name PILSADMIN and the master password by default. If required, you can choose another user name and password according to your requirements.... Exchange Infrastructure Administrator and Password If you want to choose another user name, make sure that this user name starts with PI. This user has extensive authorizations. SAPinst sets the user name PISUPER and the master password by default. If required, you can choose another user name and password according to your requirements.... Exchange Infrastructure Communicator and Password If you want to choose another user name, make sure that this user name starts with PI. SAPinst sets the user name PI_JCD_RFC and the master password by default. If required, you can choose another user name and password according to your requirements.... If you want to choose another user name, make sure that this user name starts with PI. End of: Process Integration (PI) Parameters Relevant for the File System Parameters Description Your Values File system for the home directory user /home/<username>... 36/206 PUBLIC 03/28/2008

37 2 Planning 2.5 Basic SAP System Parameters Parameters Description Your Values SAP system mount directory /<sapmnt> is the base directory for the SAP system. For /<sapmnt> you can use a directory of your choice. Do not add <SAPSID> as subdirectory because the system adds this directory automatically.... File systems of DB2 V9.1 and DB2 V9.5 Example If you enter /<sapmnt>, the system creates the directory /<sapmnt>/<sapsid>. Database software Database home Database instance home Database log files Database diagnostic data SAPDATA For more information, see Required File Systems for DB2 for Linux, UNIX, and Windows [page 40].... Parameters Relevant for the Database Parameters Description Enter Your Values DB2 instance owner db2<dbsid> ABAP database connect user (sap<sapsid>) Java database connect user (sap<sapsid>db) ID of the db<dbsid>adm group db<dbsid>adm group db2<dbsid> has the DB2 system administration authorities and belongs to group db<dbsid>adm, which has DB2 SYSADM authorities. By default, user db2<dbsid> is a member of group db<dbsid>adm. The user name corresponds to the database schema where ABAP tables are created. The user name corresponds to the database schema where J2EE tables are created. In a multi-partitioned database environment, the group ID must be the same on all database partition servers. Members of this group have DB2 SYSADM authorities. By default, user db2<dbsid> is a member of this group /28/2008 PUBLIC 37/206

38 2 Planning 2.5 Basic SAP System Parameters Parameters Description Enter Your Values ID of the db<dbsid>ctl group db<dbsid>ctl group ID of the db<dbsid>mnt group db<dbsid>mnt group Database Communication Port In a multi-partitioned database environment, the group ID must be the same on all database partition servers. Members of this group have DB2 SYSCTRL authorities. By default, <sapsid>adm is a member of this group. In a multipartitioned database environment, the group ID must be the same on all database partition servers. Members of this group have DB2 SYSMNT authorities. By default, sap<sapsid>db (the Java database connect user) and sap<sapsid> (the ABAP database connect user) are members of this group. The DB2 Communication Port is used for TCP/IP communication between the database server and remote DB2 clients. In a central system installation and for the database instance in a distributed installation, SAPinst always proposes 5912 as default value First Port SAPinst requests this value during the database instance installation. The database partition servers communicate using registered services. During the installation a port range is assigned for this communication. SAPinst proposes default values. You must make sure that these values correspond to the values of your database partition servers. If necessary, adapt them according to your settings.... The value for First Port must be the same for all database partition servers. The range between First Port and Last Port must correspond to the maximum number of partitions on a database partition server. 38/206 PUBLIC 03/28/2008

39 2 Planning 2.6 Running Adobe Document Services on Nonsupported Platforms Parameters Description Enter Your Values Last Port The database partition servers communicate using registered services. During the installation a port range is assigned for this communication. SAPinst proposes default values. You must make sure that these values correspond to the values of your database partition servers. If necessary, adapt them according to your settings.... Add sapdata directories The range between First Port and Last Port must correspond to the maximum number of partitions on a database partition server. For an installation on DB2 V9, the tablespaces are stored in /db2/<sapsid>/sapdata<n>. By default, SAPinst creates four sapdata directories (sapdata1, sapdata2, sapdata3, sapdata4).... Be aware that the first part, for example /db2/<sapsid>/ is definite and you can only enter a value for sapdata<n>. Use Change, that is, add or remove the names and number of the sapdata directories. 2.6 Running Adobe Document Services on Nonsupported Platforms Adobe document services (ADS) are currently supported on a limited set of 64-bit platforms for SAP NetWeaver. Procedure To use ADS in SAP landscapes on nonsupported platforms, you have to install an additional standalone SAP system with AS Java on a platform supported by ADS. For more information, see SAP /28/2008 PUBLIC 39/206

40 2 Planning 2.7 Setup of Database Layout 2.7 Setup of Database Layout When you plan your SAP system installation, it is essential to consider the setup of your database layout with regard to the distribution of, for example, SAP directories or database file systems, to disks. The distribution depends on your specific environment and you must take factors into consideration, such as storage consumption of the software components involved, safety requirements and expected workload. Make sure that you read the following sections before starting the SAP system installation: 1. Required File Systems for DB2 for Linux, UNIX, and Windows [page 40] 2. Users and Groups [page 42] 3. DB2 Tablespaces [page 43] 4. Creating Tablespaces Manually (Optional) [page 44] 5. MCOD Tablespaces and File Systems [page 45] 6. Optimization of Database Size on Disk [page 47] 7. Data Safety and Performance Recommendations for Database Directories [page 49] 8. Performance Recommendations for Large Databases [page 50] Required File Systems for DB2 for Linux, UNIX, and Windows This section lists the file systems that are required by the DB2 database as well as the permissions that you have to set. If you plan to set up a high availability database cluster (SA MP) that is based on a shared disk, all the file systems listed in the table below must be located on the shared disk. For more information, see the document IBM DB2 High Availability Solution: IBM Tivoli System Automation for Multiplatforms at SAP on DB2 for Linux, UNIX, and Windows Knowledge Center Key Topics Installation and Upgrade Required File Systems Production systems only: During the installation of your SAP system, you can specify the amount and names of the sapdata directories. However, to ensure that your SAP system performs well in a production environment, you have to define and control the distribution of the database directories to physical disks. You do this by creating and mounting separate file systems manually for the directories listed in the following table. 40/206 PUBLIC 03/28/2008

41 2 Planning 2.7 Setup of Database Layout File System/Logical Volume /db2/db2<dbsid> /db2/<dbsid>/log_dir /db2/<dbsid>/db2dump With DB2 s automatic storage management: /db2/<dbsid>/sapdata<n> No automatic storage management: /db2/<sapsid>/sapdata<n> Description Home directory of user db2<dbsid> and contains the DB2 instance data for <DBSID> and the DB2 software. Size: at least 1 GB Contains at least the online database log files. Size: at least 1.4 GB Optionally, you can use DB2 dual logging feature. If you want to use this feature, you have to create the file system/db2/<dbsid>/log_dir2 with the same size as /db2/<dbsid>/log_dir. For more information, see the Database Administration Guide: IBM DB2 Universal Database for UNIX and Windows - New Log File Management at SAP on DB2 for Linux, UNIX, and Windows Knowledge Center Key Topics Administration Contains DB2 diagnostic log files, DB2 dump files and further service engineer information. Size: 100 MB SAP data for container type database managed space (DMS) FILE or for use of DB2 s automatic storage management. By default, SAPinst creates four sapdata directories. If you require more or fewer sapdata directories, you can change this on the SAPinst Sapdata Directories dialog. Temporary tablespaces are equally distributed over the sapdata directories. Make sure that you provide enough free space in your sapdata directories for temporary data. For more information about the size, see the current installation note for DB2 for Linux, UNIX, and Windows. In a production system, you must make sure that the sapdata directories are located in different file systems. Otherwise, system performance can decrease. For more information, see Data Safety and Performance Considerations for Database Directories [page 49]. If you add additional sapdata directories during the dialog phase of SAPinst, the corresponding tablespace containers are equally distributed. On AIX, use large enabled file systems. For more information, see Setting Up File Systems and Raw Devices 03/28/2008 PUBLIC 41/206

42 2 Planning 2.7 Setup of Database Layout File System/Logical Volume Description for AIX. For information about SAP files systems, see Setting Up File Systems [page 76]. File System Permissions The file systems and logical volumes must have the permissions and owner shown in the following table and they must be created and mounted before starting SAPinst. SAPinst then sets the required permissions and owners. You can create the owners and groups manually if they do not exist yet. Otherwise, SAPinst creates them automatically. For more information, see Creating Operating System Users Manually [page 72]. File System/Logical Volume Permissions Owner Group /db2/<dbsid> 755 db2<dbsid> db<dbsid>adm /db2/<dbsid>/log_dir 755 db2<dbsid> db<dbsid>adm /db2/<dbsid>/db2dump 755 db2<dbsid> db<dbsid>adm With DB2 s automatic storage management: /db2/<dbsid>/sapdata<n> No automatic storage management: /db2/<sapsid>/sapdata<n> 750 db2<dbsid> db<dbsid>adm Users and Groups SAPinst creates the following users and groups for the central, dialog and database instance as shown in the following table: User Home Directory Group db2<dbsid> /db2/db2<dbsid> db<dbsid>adm <sapsid>adm can be chosen sapsys (primary group), db<dbsid>ctl (secondary) 42/206 PUBLIC 03/28/2008

43 2 Planning 2.7 Setup of Database Layout User Home Directory Group Default ABAP connect user: sap<sapsid> You may change this user during the installation. Default Java database connect user: sap<sapsid>db You may change this user during the installation. can be chosen /home/sap<sapsid>db db<dbsid>mnt (primary group) db<dbsid>mnt (primary group) DB2 Tablespaces During the dialog phase of the installation, SAPinst offers to create the following tablespace types: Data and index tablespaces managed by DB2 s automatic storage management (AutoStorage) During the installation, SAPinst assigns the sapdata directories to the database, which automatically distributes all tablespaces over the sapdata directories or file systems. In addition, the database automatically adjusts the tablespace sizes as long as there is enough free space left in the sapdata directories or file systems. If one of the sapdata directories becomes full, new stripe sets are automatically created in the remaining sapdata directories. Since the DB2 database automatically creates and administers the tablespace containers, the overall administration effort for the database decreases considerably using tablespaces managed by automatic storage management. As of DB2 V9.1 and higher, the database and the SYSCATSPACE tablespace are always created with automatic storage management enabled even if you deselect this option on the IBM DB2 for Linux, UNIX, and Windows > Sapdata Directories dialog. DMS File tablespaces in autoresize mode SAPinst creates all DMS tablespaces with FILE containers in autoresize mode as well as one tablespace container for each tablespace in every sapdata directory or file system. DB2 automatically extends the size of all DMS FILE tablespaces in autoresize mode as long as there is space left in the sapdata directories or file systems. With DMS FILE tablespaces in autoresize mode, you are more flexible to distribute heavily used tablespaces to dedicated storage devices at a later point in time. For more information, see Performance Recommendations for Large Databases [page 50]. Other tablespace types 03/28/2008 PUBLIC 43/206

44 2 Planning 2.7 Setup of Database Layout If you want to use other tablespace types, for example SMS or DMS DEVICE (raw devices), you have to create them manually. Therefore, you deselect the option Create tablespaces with SAPinst during the dialog phase of SAPinst and proceed as described in Creating Tablespaces Manually [page 44]. At a later point in time, you can switch between DMS FILE and DMS DEVICE tablespaces using DB2 s redirected restore tool. In addition, you can enable and disable autoresize mode for databases that are not set up in AutoStorage mode. To move tablespaces from AutoStorage to other storage modes or vice versa, you have to perform a homogenous system copy. For more information, see the appropriate system copy guide that is available on SAP Service Marketplace at Container Type FILE If you are using tablespaces managed by DB2 s automatic storage management, DB2 creates and administers the tablespace containers for you. If you are using DMS FILE tablespaces in autoresize mode, each tablespace of your SAP installation has at least one container. A container is a file that holds pages belonging to a tablespace. Since you might want to add containers as your database grows in size, you should adhere to the following naming scheme: The first container of a tablespace is given the name of the tablespaces plus the ending container001. Therefore, <SAPSID>#BTABD has at least the container <SAPSID>#BTABD.container001. The next container is called <SAPSID>#BTABD.container002, and so on. Container Sizes Equal container sizes ensure the proper balancing of container access and therefore better performance, if the containers reside on different disks. SAPinst creates all containers of a tablespace with the same size. Tablespace Sizes Without Autoresize By default, the tablespaces are created with autoresize mode. If you are using tablespaces without the autoresize mode, you must extend the tablespaces manually. If you do not increase your tablespace sizes in time, the following error occurs: Error occurred during DB access SQLException SQLCODE: Creating Tablespaces Manually (Optional) If the tablespace layout used by SAPinst does not meet your requirements, you an optionally create your tablespaces manually. During the dialog phase of SAPinst, you can specify if you want to use tablespaces managed by DB2 s automatic storage management and if you want SAPinst to create your tablespaces. 44/206 PUBLIC 03/28/2008

45 2 Planning 2.7 Setup of Database Layout Procedure SAPinst does not check the page size of tablespaces that have either been created manually or are already existing. If you create the tablespaces manually, you must make sure that you use a page size of 16 KB. 1. On the dialog IBM DB2 for Linux, UNIX, and Windows Sapdata Directories, you must deselect the option Create Tablespaces with SAPinst. In a typical installation, this dialog does not appear. To get to it, select this parameter on the Parameter Summary screen and choose Revise. 2. Continue to enter all the required parameters and start SAPinst. During the installation phase, the following message box appears: You must create the tablespaces now. To do so, use the createtablespaces.sql script that is located in your installation directory. To continue the installation, choose OK. Alternatively, you can cancel SAPinst here and restart it again. 3. Go to your installation directory and search for script createtablespace.sql. This file content depends on your selection during the dialog phase and the file contains the same commands for the creation of tablespaces that SAPinst uses. You must create all the tablespaces that are listed in the script. 4. Modify the CREATE statements according to you requirements. 5. To execute the script, enter the following command: db2 tvf <script_name> 6. When you have finished, continue with the installation by choosing OK on the message box. More Information DB2 Tablespaces [page 43] Performance Recommendations for Large Databases [page 50] MCOD Tablespaces and File Systems If you install additional SAP components into one database, each system has its own tablespaces. Only SYSCATSPACE and temporary tablespaces are shared, for example, the additional SAP system <SAPSID2> uses tablespaces, such as <SAPSID2>#BTABD and <SAPSID2>#BTABI 03/28/2008 PUBLIC 45/206

46 2 Planning 2.7 Setup of Database Layout During an installation of multiple components on one database, additional space is required for tablespace SYSCATSPACE. If you are not using tablespaces with autoresize mode or DB2 s automatic storage management, you must extend SYSCATSPACE manually before you start the SAP system installation. If you are not using autostorage tablespaces, the tablespaces of the additional SAP system <SAPSID2> are located in /db2/<sapsid2>/sapdata<n>. If you are using autostorage tablespaces, the automatic storage paths, which have already been configured in your database, are used. The temporary tablespace of the additional SAP system <SAPSID2> is the same as for <SAPSID1>. If temporary tablespaces with 16 KB page size do not exist, they are created in /db2/<dbsid>/sapdata<n>. If you are using a database in AutoStorage mode in an MCOD environment, you can choose if your tablespaces are also AutoStorage or AutoResize. You can only choose this option for your tablespaces if you are using a database in AutoStorage mode in an MCOD environment. Each additional system works with the ABAP connect user sap<sapsid> and the Java connect user sap<sapsid>db. This means that all database objects of SAP system <SAPSID2> are owned by either sap<sapsid2> or sap<sapsid2>db. There is only one database administrator db2<dbsid>. Required File Systems The following table lists the file systems that are required for an additional SAP system. File System/Logical Volume With DB2 s automatic storage management: Use the automatic storage paths that have already been configured in your database. No automatic storage management: /db2/<sapsid2>/sapdata<n> /db2/<dbsid>/sapdata<n> /sapmnt/<sapsid2> /usr/sap/<sapsid2> Description SAP data for container type database-managed space (DMS) FILE By default, four Sapdata directories are created (sapdata1, sapdata2, sapdata3, sapdata4). Contains the temporary tablespace(s). Contains the software and data for one SAP system Contains the instance-specific data as well as symbolic links to the data for one SAP system 46/206 PUBLIC 03/28/2008

47 2 Planning 2.7 Setup of Database Layout Optimization of Database Size on Disk With the increasing cost for managed storage, database sizes become more and more a concern. You can significantly reduce the size of your database by selecting the following options in SAPInst during the dialog phase: Use DB2 s Row Compression DB2 s row compression (also known as deep compression) transparently compresses table data in your database, using a dictionary-based compression algorithm. Using row compression typically reduces the size of tables by 60 to 80%. As a result, the size of the database decreases by approximately 30 to 55 %. If you want to use row compression, make sure that you have a valid license for this function. If you purchased your DB2 license from SAP (an SAP OEM license), DB2 row compression is already part of your license agreement. Use Deferred Table Creation Before you use this function, make sure that you read SAP The SAP function deferred table creation delays the creation of empty database tables until the first row is inserted. That is, until the first row is inserted, the table is substituted by a virtual table (which effectively is a special database view). As soon as the first row is inserted, the SAP kernel transparently replaces the virtual table with a database table. To reverse this status and to create the empty tables that have not yet been created after the installation, use the DBA Cockpit: 1. In your SAP system, call transaction DBACOCKPIT and choose Space Virtual Tables in the navigation frame. The screen Space: Virtual Tables appears. 2. To replace a virtual table with a real table, select one or more virtual tables and choose Materialize. Depending on the number of tables that remain empty over your system lifetime, the use of deferred table creation can reduce the size of your database by several GB. Minimizing the Database Size after the Installation If you choose to install your SAP system without selecting the options Use DB2 s Row Compression and Use Deferred Table Creation, you can still activate both functions after the installation using the DBA Cockpit. 03/28/2008 PUBLIC 47/206

48 2 Planning 2.7 Setup of Database Layout Activating DB2 s Row Compression Activating row compression after the installation requires a high administrative effort and is time consuming. Furthermore, it can only be performed for single tables. 1. Identify the table candidates that are suitable for row compression using the REORGCHK for all Tables job with option With Compression Check in the DBA Planning Calendar. For more information about this job, see Scheduling a REORGCHK for All Tables in the document Database Administration Using the DBA Cockpit: IBM DB2 for Linux, UNIX, and Windows at: SAP on DB2 for Linux, UNIX, and Windows Knowledge Center Key Topics Administration 2. In your SAP system, call transaction DBACOCKPIT and choose Space Tables and Indexes. 3. On the Selection Criteria dialog, select Candidates for Row Compression. A list of table candidates are displayed. 4. Double-click the table that you want to enable for row compression. The screen Space: Tables and Indexes Details appears. 5. Choose Compression On/Off. Be aware that after you have enabled the table for row compression, the table must be reorganized to benefit from the compression. Activating Deferred Table Creation Before you use this function, make sure that you read SAP In your SAP system, call transaction DBACOCKPIT and choose Space Virtual Tables. 2. On the screen Space: Virtual Tables, choose Candidates for Virtualization. 3. Choose Convert Empty Tables. A job is scheduled that checks every table if it is empty. If a table is empty, the table is converted to a virtual table. 48/206 PUBLIC 03/28/2008

49 2 Planning 2.7 Setup of Database Layout The following tables are excluded from the conversion: Volatile tables MDC tables Partitioned tables Data Safety and Performance Considerations for Database Directories The following information is only relevant for the installation of a production system. During the installation of an SAP system you can control the distribution of database directories or file systems to physical disks. On Windows operating systems, you assign drive letters to the system components when running the installation tool. On UNIX operating systems, this is done when you create file systems before starting the installation tool. The way you distribute your database components to disk can significantly affect system throughput and data security, and must therefore be carefully planned. 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. Make sure that you have an overview of the expected database size, the available disks and the I/O adapters that are used to attach the disks to your system. The following sections provide important information about: Data integrity requirements Performance considerations Disk space consumption and storage management Data Integrity Requirements When you plan your SAP system installation, you must consider the following: In an emergency situation you must be able to perform a rollforward recovery of your database in a production system. In a production system, the DB2 database must run in log retention mode. Otherwise, log files cannot be applied to the database rollforward operations. 03/28/2008 PUBLIC 49/206

50 2 Planning 2.7 Setup of Database Layout You can set the database to log retention mode by changing database configuration parameters at the very end of the installation process. After changing the parameters, you are automatically forced to perform an offline backup. Otherwise, you cannot reconnect to the database, which is reported with an error message. For information, Enabling Recoverability of the Database [page 134]. Keep the tablespace container files in directories sapdata* and the online log directory log_dir on separate disks to be able to perform a full rollforward recovery if a database container file is damaged or lost. Since transaction data is lost if online log files are damaged, we recommend that the online log directory log_dir is stored on redundant storage. Hardware mirroring can be done using RAID adapters or intelligent storage systems. For performance reasons, hardware solutions for mirroring should be preferred over mirroring solutions like logical volume managers that are offered by operating systems. In addition, the DB2 product offers dual log file mechanism. For more information, see SAP Performance Considerations A high transaction volume can cause high I/O on the online log files. Therefore, the distribution of the online log files is a crucial factor of performance considerations. Ideally, the online log files should be located on fast physical volumes that do not have high I/O load coming from other components. This allows efficient logging activity with a minimum of overhead such as waiting for I/O. You should avoid storing the online log files on the same physical volume as the operating system paging space, or a physical volume with high I/O activity Performance Considerations for Large Databases Tablespaces in AutoStorage mode offer maximum ease of use and low administrative cost. In addition, modern file systems avoid most concurrency problems. If you are not running your database in AutoStorage mode, you have detailed but manual control over the distribution of data on disk. In this case and to enhance performance of large databases, we give the following recommendations: Distribute heavily used tablespaces across separate disks. Avoid putting multiple containers of one tablespace onto the same device. Move heavily used tables into their own tablespaces that reside on dedicated disks. Put containers of index tablespaces and their respective data tablespaces on different disks. Do not configure operating system I/O (for example, swap, paging or heavily spool) on DB2 data disks. 50/206 PUBLIC 03/28/2008

51 2 Planning 2.8 High Availability: Planning the Switchover Cluster You can run DB2 databases with multiple page sizes in a single database. But once specified for a tablespace, the page size cannot be changed. For each page size, a separate buffer pool has to be created in your database. During a standard installation, SAPinst creates the database with a uniform page size of 16 KB. As a result only buffer pools with 16 KB have to be created and administered. More Information DB2 product documentation [page 18] Administration Guide: Performance Only valid for: HA (UNIX) 2.8 High Availability: Planning the Switchover Cluster You can reduce unplanned downtime for your high-availability (HA) SAP system by setting up a switchover cluster. This setup replicates critical software units known as single points of failure (SPOFs) across multiple host machines in the cluster. In the event of a failure on the primary node, proprietary switchover software automatically switches the failed software unit to another hardware node in the cluster. Manual intervention is not required. Applications accessing the failed software unit experience a short delay but can then resume processing as normal. Switchover clusters also have the advantage that you can deliberately initiate switchover to free up a particular node for planned system maintenance. Switchover solutions can protect against hardware failure and operating system failure but not against human error, such as operator errors or faulty application software. Without a switchover cluster, the SAP system SPOFs central services instance, the database instance, and the central file share are vulnerable to failure because they cannot be replicated. All of these can only exist once in a normal SAP system. You can protect software units that are not SPOFs against failure by simply replicating them. For example, you can add additional dialog instances (that is, additional application servers). This complements the switchover solution and is an essential part of building HA into your SAP system. Recommendation We recommend switchover clusters to ensure HA for your SAP system. A switchover cluster consists of: A hardware cluster of two or more physically separate host machines to run multiple copies of the critical software units, in an SAP system the SPOFs referred to above Switchover software to detect failure in a node and switch the affected software unit to the standby node, where it can continue operating A mechanism to enable application software to seamlessly continue working with the switched software unit normally this is achieved by virtual addressing (although identity switchover is also possible) 03/28/2008 PUBLIC 51/206

52 2 Planning 2.8 High Availability: Planning the Switchover Cluster Recommendation If you want to install the Java Add-In to an existing ABAP High-Availability system, we recommend that you install the Java central services instance (SCS) in the switchover cluster of the ABAP central services instance (ASCS). Prerequisites You must first discuss switchover clusters with your hardware partner because this is a complex technical area. In particular, you need to choose a proprietary switchover product that works with your operating system. We recommend that you read the following documentation before you start: Check the informations and the installation guides that are available at On database level, IBM provides a high-availability cluster solution for Linux and AIX only that is called IBM Tivoli System Automation for Multiplatforms (SA MP). IBM also provides a free two-node license of SA MP for the DB2 database server. The corresponding installation guide describes how to set up a switchover cluster with SA MP based on the DB2 feature High Availability and Disaster Recovery (HADR) or a shared disk. More information: IBM DB2 High Availability Solution: IBM Tivoli System Automation for Multiplatforms at SAP on DB2 for Linux, UNIX, and Windows Knowledge Center Key Topics Installation and Upgrade The standalone replicated enqueue server is a major contribution to an HA installation and is essential for a Java system. We strongly recommend you to use it for an ABAP system. For more information about how to install the standalone replicated enqueue server, see: SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology Client/Server Technology The SAP Lock Concept Standalone Enqueue Server Installing the Standalone Enqueue Server Features The following figure shows the essential features of a switchover setup: 52/206 PUBLIC 03/28/2008

53 2 Planning 2.8 High Availability: Planning the Switchover Cluster Figure 6: This figure and the figures in this section are only examples. You need to discuss your individual HA setup with your HA partner. The following figure shows an example of a switchover cluster in more detail: 03/28/2008 PUBLIC 53/206

54 2 Planning 2.8 High Availability: Planning the Switchover Cluster Figure 7: Constraints This documentation concentrates on the switchover solution for the central services instance. For more information about how to protect the NFS File System and the database instance by using switchover software or (for of the database) replicated database servers, contact your HA partner. You need to make sure that your hardware is powerful enough to handle the increased workload after a switchover. Some reduction in performance might be acceptable after an emergency. However, it is not acceptable if the system comes to a standstill because it is overloaded after switchover. End of: HA (UNIX) 54/206 PUBLIC 03/28/2008

55 3 Preparation 3 Preparation You have to complete the following preparations: 1. Only valid for: HA (UNIX) You perform the switchover preparations [page 56] for a high-availability (HA) system. End of: HA (UNIX) 2. You check the hardware and software requirements [page 61]. 3. If required, you create operating system users manually [page 72]. 4. You set up file systems and raw devices [page 76]. 5. If you want to perform a distributed installation, you export and mount global directories: This section does not apply to the installation of a Java Add-In to an existing ABAP system. a) On the SAP trans host, you export the trans directory to SAP global host, central instance host, database instance host, and if required to the dialog instance host(s). b) On the SAP global host, you export subdirectories exe, global, profile of /sapmnt/<sapsid> to central instance host, database instance host, and if required to the dialog instance host(s). c) You mount subdirectories exe, global, profile of /sapmnt/<sapsid> and directory trans on the database instance host and on the central instance host. If you want to install one or more dialog instance(s), you also have to mount these directories on the dialog instance host. For more information about exporting and mounting directories, see: Exporting and Mounting the Global Transport Directory [page 87] Exporting and Mounting Directories via NFS for AIX [page 88] 6. You install the SAP front-end software [page 89]. This step does not apply to the installation of a Java Add-In to an existing ABAP system. 7. You generate the SAP Solution Manager Key [page 89]. This step does not apply to the installation of a Java Add-In to an existing ABAP system. 03/28/2008 PUBLIC 55/206

56 3 Preparation 3.1 High Availability: Switchover Preparations 8. You install the Java Development Kit [page 90]. 9. If you already know that you want to install additional Java applications before or after the installation the Java part, make sure that you define the size of tablespaces <SAPSID>#DBD and <SAPSID>#DBI. For more information, see DB2 Tablespaces [page 43]. 10. You prepare and mount the installation media [page 91]. Only valid for: HA (UNIX) 3.1 High Availability: Switchover Preparations Only valid for: HA (UNIX) Preparing for Switchover This section describes the extra preparations you need to make for a high availability (HA) installation. For more information, consult your HA partner. You need to perform the preparations listed below on host A and after you have installed the central services (SCS) instance on host B. Prerequisites You have already installed the hardware that is, hosts, disks, and network and decided how to distribute the database, SAP instances, and (if required) Network File System (NFS) server over the cluster nodes (that is, over the host machines). For more information, see Planning the Switchover Cluster [page 51]. Procedure 1. You check that your system meets the hardware and software requirements [page 61] for an HA setup, including the switchover software. 2. You set up file systems (that is, disk partitions), mount points, and (if required) NFS for your HA system on: a) Node A before the installation of the SCS instance with SAPinst b) Node B after the installation of the SCS instance with SAPinst To do this proceed as follows: This step does not apply to the installation of a Java Add-In to an existing ABAP system. 56/206 PUBLIC 03/28/2008

57 3 Preparation 3.1 High Availability: Switchover Preparations Recommendation If possible, use journaled file systems (JFS), which allows much quicker recovery after a host machine crash. With JFS, you can reduce the switchover time because the hard disk maintains data integrity in the event of a system crash or if the system is otherwise halted abnormally. a) You set up the required file systems [page 58] using mount points or NFS b) If required, you configure NFS [page 59], making sure you are using the virtual host name for NFS to enable NFS switchover.. c) You assign the local file systems to mount points. d) You assign the shared file systems to mount points in appropriate cluster packages. Example The figure below shows an example of the file systems and disks in an HA setup that this is only an example. For more information on a setup that meets your needs, consult your HA partner. Figure 8: 3. You set up Domain Name System (DNS) on the virtual host. This step does not apply to the installation of a Java Add-In to an existing ABAP system. 03/28/2008 PUBLIC 57/206

58 3 Preparation 3.1 High Availability: Switchover Preparations 4. You assign the virtual IP addresses and host names for SCS instance, and (if required) NFS to appropriate cluster packages. This step does not apply to the installation of a Java Add-In to an existing ABAP system. For more information on how to assign resources to cluster packages, ask your HA partner. End of: HA (UNIX) Only valid for: HA (UNIX) Setting Up File Systems for a High-Availability System When you prepare a high-availability (HA) installation, you need to set up your file systems as described here. For more information, consult your HA partner. This section does not apply to the installation of a Java Add-In to an existing ABAP system. Procedure 1. Create the file systems or raw partitions for the central services (SCS) instance on shared disks. For more information, see Setting Up File Systems and Raw Devices [page 76]. The directories /<sapmnt>/<sapsid> and /usr/sap/trans have to be mounted from a Network File System (NFS), whereas /usr/sap/<sapsid> is a directory of the AS instance that is always mounted on the instance (not with NFS). Therefore, if the central instance host is not the NFS server host, you might have to mount at least the first two file systems on different physical disks from the third file system. 2. If the node that takes over the central instance also runs an AS instance during normal operation, we recommend that you use a different approach for the file system for the /usr/sap/<sapsid> directory. /usr/sap/<sapsid> contains two subdirectories: SYS contains links to the central directory /<sapmnt>/<sapsid> 58/206 PUBLIC 03/28/2008

59 3 Preparation 3.1 High Availability: Switchover Preparations <INSTTYPE><NR> contains data for the local AS instance The name <INSTTYPE><NR> is defined by the type of services and the application server number, for example DVEBMSG00. Only the directory <INSTTYPE><NR> needs to be migrated with the AS instance during the switchover. Since the SYS subdirectory contains only links that do not require any space, it can be created locally on each cluster node. Therefore, instead of /usr/sap/<sapsid>, create a file system for /usr/sap/<sapsid>/<insttype><nr> with the usual <> substitutions. The file name for the central instance is usually DVEBMGS00. This avoids mount conflicts when switching over to a node on which an AS instance is already running. The DVEBMGS00 directory can join the tree /usr/sap/<sapsid> instead of mounting on top of it. This approach becomes increasingly important when you want to cluster central services while other instances run on the cluster hosts outside the control of the switchover software, so as to use the resources efficiently. You must use this approach for integrated installations of the AS with ABAP and Java stacks. End of: HA (UNIX) Only valid for: HA (UNIX) Configuring Network File System If required, you configure Network File System (NFS), which is a system-wide Single Point-of-Failure (SPOF), for a high-availability (HA) installation. For more information, consult your HA partner. We regard NFS as an extension to the operating system. The switchover product protects NFS and makes it transparently available to the SAP system in switchover situations. You need to decide: How to protect NFS Which switchover cluster nodes NFS is to run on The NFS configuration might depend on your database system. The directories need to be available for the SAP system before and after a switchover. Procedure 1. Check the NFS directories, several of which need to be shared between all instances of a system. These directories are: /sapmnt/<sid>/profile Contains the different profiles to simplify maintenance 03/28/2008 PUBLIC 59/206

60 3 Preparation 3.1 High Availability: Switchover Preparations /sapmnt/<sid>/global Contains log files of batch jobs and central SysLog /usr/sap/trans Contains data and log files for objects transported between different SAP Web AS systems (for example, development integration). This transport directory ought to be accessible by at least one AS instance of each system, but preferably by all. /sapmnt/<sid>/exe Contains the kernel executables. These executables ought to be accessible on all AS instances locally without having to use NFS. The best solution is to store them locally on all AS instance hosts. 2. Since you can protect NFS by a switchover product, it makes sense to install it on a cluster node. The requirements of your database system might dictate how NFS has to be set up. If required, you can configure the NFS server on the cluster node of the CI or the DB. In both cases the NFS clients use the virtual IP address to mount NFS. If the second node is used as an additional SAP instance during normal operation (for example, as a dialog instance), it also needs to mount the directories listed above from the primary node. When exporting the directories with their original names, you might encounter the problem of a busy NFS mount on the standby node. You can use the following workaround to solve this problem: a) On the primary server, mount the disks containing the directories: /export/usr/sap/trans /export/sapmnt/<sid> b) The primary server creates soft links to the directories with the original SAP names: /usr/sap/trans > /export/usr/sap/trans /sapmnt/<sid> > /export/sapmnt/<sid> Alternatively the primary server can also mount the directories: /export/usr/sap/trans > /usr/sap/trans /export/sapmnt/sid > /sapmnt/<sid> c) The primary server exports: /export/usr/sap/trans /export/sapmnt/<sid> d) The standby NFS mounts: from virt.ip:/export/usr/sap/trans to /usr/sap/trans from virt.ip:/export/sapmnt/<sid> to /sapmnt/<sid> If the primary node goes down and a switchover occurs, the following happens: These directories on the standby node become busy: /usr/sap/trans /sapmnt/<sid> The standby node mounts disks to: 60/206 PUBLIC 03/28/2008

61 3 Preparation 3.2 Hardware and Software Requirements /export/usr/sap/trans /export/sapmnt/<sid> The standby node configures the virtual IP address virt.ip The standby node exports: /export/usr/sap/trans /export/sapmnt/<sid> These directories on the standby node are accessible again: /usr/sap/trans /sapmnt/<sid> End of: HA (UNIX) End of: HA (UNIX) 3.2 Hardware and Software Requirements You check that your hosts meet the hardware and software requirements for your operating system and the SAP instances. If your hosts do not fully meet the requirements, you might experience problems when working with the SAP system. Prerequisites Contact your OS vendor for the latest OS patches. Make sure that the host name meets the requirements listed in SAP Check your keyboard definitions. If you want to install a printer on a host other than the central instance host (for example, on a separate database instance host), make sure that the printer can be accessed under UNIX. Process Flow 1. Check the Product Availability Matrix at for supported operating system releases. 2. Check the hardware and software requirements using: The Prerequisite Checker: Standalone (optional) before the installation process For more information, see Running the Prerequisite Checker Standalone [page 62]. Integrated in SAPinst (mandatory) as part of the installation process For more information, see Running SAPinst on UNIX [page 104] 03/28/2008 PUBLIC 61/206

62 3 Preparation 3.2 Hardware and Software Requirements For the most recent updates to the Prerequisite Checker, always check SAP The hardware and software requirements checklists for: AIX [page 63] Central system [page 66] Distributed or high availability system [page 67] If you want to install dialog instance(s), check the requirements for a dialog instance [page 71]. If you want to use 32-bit SAP NetWeaver components, first check whether these components can run on 64-bit operating systems. If so, we recommend you to use 64-bit systems. If not, you can install an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP instances, you must use 64-bit systems. 3. If you are installing a production system, the values provided by the Prerequisite Checker and the hardware and software requirements checklists are not sufficient. In addition, do the following: You use the SAP Quick Sizer tool available at For more information about the SAP Quick Sizer and available sizing guides, see the Master Guide SAP NetWeaver 7.0 at Planning. Only valid for: Development Infrastructure (DI) If you want to install usage type Development Infrastructure (DI), also check SAP for system requirements and sizing. End of: Development Infrastructure (DI) You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing depending on: The set of applications to be deployed How intensively the applications are to be used The number of users Running the Prerequisite Checker in Standalone Mode (Optional) Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check the hardware and software requirements for your operating system (OS) and the SAP instances. 62/206 PUBLIC 03/28/2008

63 3 Preparation 3.2 Hardware and Software Requirements When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks the hardware and software requirements in the background. Prerequisites You have installed the correct Java Development Kit (JDK) [page 90]. You have prepared the installation master DVD on the required installation host [page 91]. You make sure that the required prerequisites are met before starting SAPinst [page 99]. Procedure 1. You start SAPinst [page 104]. 2. On the Welcome screen, choose <SAP System> Software Life-Cycle Options Additional Preparation Options Prerequisites Check. 3. Follow the instructions in the SAPinst dialogs and enter the required parameters. For more information about each parameter, position the cursor on the parameter field and choose F1 in SAPinst. When you have finished, the Parameter Summary screen appears summarizing all parameters you have entered. If you want to make a change, select the relevant parameters and choose Revise. 4. To start the Prerequisite Checker, choose Start. Result The Prerequisite Check Results screen displays the results found. If required, you may also check the results in file prerequisite_checker_results.html, which you find in the installation directory Requirements for AIX The host machine must meet the following requirements: The information here is not intended to replace the documentation of the AIX operating system. You can perform AIX-specific steps as follows: Manually by entering AIX commands with the appropriate options Using System Management Interface Tool (SMIT), a menu-driven system administration tool If you have problems with the function keys, you can also use ESC and the corresponding number to simulate the function key (for example, F4 is equivalent to ESC and 4 ). 03/28/2008 PUBLIC 63/206

64 3 Preparation 3.2 Hardware and Software Requirements Hardware Requirements Requirement Tape drive DVD drive Required disks RAM CPU Values and Activities High-capacity tape drive with hardware compression is recommended. You can test the drive /dev/rmt0 with this command: tar -cvf /dev/<tape_device> <test_file> The device name is always rmt0 unless more than one tape drive exists ISO 9660 compatible You can configure multiple CD / DVD drives, but you cannot mount all of them. For more information, see Mounting a CD / DVD for AIX [page 95]. For data security reasons, distribution over three disks is required. We recommend you to distribute over five disks. To display available disks, enter this command: lspv Disks marked none in the 3rd column are unused. To display free space on a disk, enter this command: lspv -p <disk_name> Areas marked free in the 2nd column are unused. If an advanced disk array is available (for example, RAID), contact your hardware vendor to make sure that the data security requirements are covered by this technology. To display RAM size in KB, enter the following command: lsattr -El sys0 -a realmem The recommended minimum hardware is either two physical single core processors or one physical dual core processor. Software Requirements Requirement C++ runtime level Operating system version Values and Activities Check the C++ runtime level with the following commands: AIX 6.x: #lslpp L xlc.aix61.rte The output must be at least #lslpp L xlc.rte The output must be at least AIX 5.x: #lslpp L xlc.aix50.rte The output must be at least #lslpp L xlc.rte The output must be at least Check the operating system version with the following command: lslpp -l bos.rte The output must include the following or a larger version number: bos.rte /206 PUBLIC 03/28/2008

65 3 Preparation 3.2 Hardware and Software Requirements Requirement AIX Maintenance Level (ML) and Technology Level (TL) LDAP (Lightweight Directory Access Protocol) Additional software DB2 specific software requirements Values and Activities AIX 6.x: The output of the command oslevel -s should be at least AIX 5.3: The output of the command oslevel -s should be at least (TL 5 SP 1). AIX 5.2: The output of the command oslevel -r should be at least (ML 4). If you want to use LDAP, you require the following LDAP library: libldap.a Make sure that the following additional file sets are installed: bos.adt Base Application Development bos.perf performance and diagnostics tools perfagent.tools performance monitoring tools bos.perf.libperfstat Performance Statistics Library For an overview of the installed file sets, enter the following command: lslpp L more Install the necessary local code set by adding an additional language environment as follows: 1. Start the System Management Interface Tool (SMIT) with the following command: smitty mle_add_lang 2. Select the following: Cultural Conventions to install: ISO German (Germany) [de_de] Language Translation to install: ISO German [de_de] This step installs the required bos.loc and bos.iconv file sets. 3. Additionally, check that all file sets are in a consistent state with this command: lppchk v For DB2 speci c software requirements, see the IBM web page DB2 for Linux UNIX, and Windows System Requirements at For important information about known issues for DB2 on AIX, see the following IBM web page: Other Requirements Requirement Printer Values and Activities Check whether a file can be printed with this command: lp -d<printer_name> <test_file> Check the status of your spool and the printers with this command: lpstat -t 03/28/2008 PUBLIC 65/206

66 3 Preparation 3.2 Hardware and Software Requirements Requirement Keyboard Network Values and Activities You can set the keyboard by typing this command on the directly connected console: smitty chkbd You can select your keyboard under Motif by setting a language environment (LANG), for which a National Language Support (NLS) component is installed. The settings take effect after reboot. Test the network connection to the database server with this command: /etc/ping <db_server_name> Requirements for a Central System If you want to install a central system that is, all instances reside on one host the host must meet the following requirements: Hardware Requirements Requirement Hard disk space Values and Activities Hard disk drives with sufficient space for the SAP system and the database For more information, see Setting Up File Systems [page 76]. For specific disk space information, see SAP For safety reasons (system failure), the file systems must be physically distributed over several disks, or RAID-technology must be used. To ensure a good performance of your production system, create separate file systems for the directories listed in section Required File Systems for DB2 for Linux, UNIX, and Windows [page 40]. 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk. For more information, see Preparing the Installation DVDs [page 91]. 1.2 GB of temporary disk space for the installation. If there is no tape drive attached to your system, you need additional disk space for the files created by DB2s database backup command and the archived database log files. Alternatively, access to network-based storage management products, such as Legato Networker or Tivoli Storage Manager (TSM) (for database backup/restore), is needed. 66/206 PUBLIC 03/28/2008

67 3 Preparation 3.2 Hardware and Software Requirements Requirement RAM Values and Activities 3 GB (minimum), 8 GB (recommended) Java Add-In (ABAP system already exists): 1.5 GB (minimum), 4 GB (recommended) Only valid for: BI Java 5.5 GB (minimum), 9 GB (recommended) End of: BI Java Only valid for: BI Java Java Add-In (ABAP system already exists): 4 GB (minimum), 5 GB (recommended) End of: BI Java Only valid for: BI Java For more information, see SAP End of: BI Java Swap Space Hard disk drives with sufficient space for swap: 3 to 4 * RAM Software Requirements Requirement Database version Values and Activities DB2 V9.1 or DB2 V9.5 for Linux, UNIX, and Windows (automatically installed by SAPinst). For the installation of your SAP system, only the English version of DB2 V9.1 or DB2 V9.5 is supported. You must only use the DB2 software provided by the SAP installation DVDs. For more information, see SAP Network File System (NFS) Fonts and code pages National Language Support (NLS) If application servers are installed decentralized, Network File System (NFS) must be installed. Make sure that the required fonts and code pages are installed. Make sure that National Language Support (NLS) and corresponding saplocales are installed Requirements for a Distributed or a High Availability System The following sections provide information about the hardware and software requirements in a distributed system, where the following SAP instances can reside on different hosts: Central services instance [page 68] Central instance [page 68] 03/28/2008 PUBLIC 67/206

68 3 Preparation 3.2 Hardware and Software Requirements Database Instance [page 69] If you install multiple SAP system instances on one host, you need to add up the requirements Requirements for the Central Services Instance The central services instance host must meet the following requirements: Hardware Requirements Requirement Hard disk space RAM Values and Activities Hard disk drives with sufficient space for the central services instance For more information, see Setting up File Systems [page 76]. 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk. For more information, see Preparing the Installation DVDs [page 91]. 1.2 GB of temporary disk space for the installation. 0.5 GB (minimum), 1 GB (recommended) Only valid for: HA (UNIX) 1 GB (minimum), 3 GB (recommended) End of: HA (UNIX) Swap Space Hard disk drives with sufficient space for swap: 3 to 4 * RAM Software Requirements Requirement Network File System (NFS) Values and Activities Network File System (NFS) must be installed Requirements for the Central Instance The central instance host must meet the following requirements: 68/206 PUBLIC 03/28/2008

69 3 Preparation 3.2 Hardware and Software Requirements Hardware Requirements Requirement Hard disk space RAM Swap Space Values and Activities Hard disk drives with sufficient space for the central instance. For more information, see Setting Up File Systems [page 76] SAP File Systems. 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk. For more information, see Preparing the Installation DVDs [page 91]. 1.2 GB of temporary disk space for the installation. 1.5 GB (minimum), 5 GB (recommended) Java Add-In (ABAP system already exists): 0.5 GB (minimum), 2 GB (recommended) Hard disk drives with sufficient space for swap: 3 to 4 * RAM Software Requirements Requirement DB2 client connectivity Values and Activities DB2 V9.1 CLI Driver / DB2 V9.1 JDBC Driver or DB2 V9.5 CLI Driver / DB2 V9.5 JDBC Driver (both are automatically installed by SAPinst) You must only use the DB2 software provided by the SAP installation DVDs. For more information, see SAP Network File System (NFS) Required fonts and code pages National Language Support (NLS) If application servers are installed decentralized, Network File System (NFS) must be installed. Make sure that the required fonts and code pages are installed. Make sure that National Language Support (NLS) and corresponding saplocales are installed Requirements for the Database Instance The database host must meet the following requirements: 03/28/2008 PUBLIC 69/206

70 3 Preparation 3.2 Hardware and Software Requirements Requirement Disk space Value or Activity For specific information about the required disk space for the database file systems, see SAP To ensure a good performance of your production system, create separate file systems for the directories listed in section Required File Systems for DB2 for Linux, UNIX, and Windows [page 40]. If there is no tape drive attached to your system, you need additional disk space for the files created by DB2s database backup command and the archived database log files. Alternatively, access to network-based storage management products, such as Legato Networker or Tivoli Storage Manager (TSM) (for database backup/restore), is needed. At least 4.3 GB for each installation DVD that you have to copy to your local disk. For more information, see Preparing the Installation DVDs [page 91] RAM Swap Space Distribution of database-specific file systems Database software Minimum 2 GB 3*RAM MB, minimum 2 GB For safety reasons (system failure), the file systems must be distributed physically over several disks, or RAID-technology must be used. DB2 V9.1 or DB2 V9.5 for Linux, UNIX, and Windows (both are automatically installed by SAPinst) For the installation of your SAP system, only the English version of DB2 V9.1 or DB2 V9.5 is supported. You must only use the DB2 software provided by the SAP installation DVDs. For more information, see SAP Kernel parameters Network File System (NFS) Required fonts and code pages National Language Support (NLS) Operating systems Check the kernel parameters for AIX. For more information, see the IBM documentation Quick Beginnings for DB2 Servers. Otherwise, there might be unpredictable problems with your system during or after installation. If application servers are installed decentralized, Network File System (NFS) must be installed. Make sure that the required fonts and code pages are installed. Make sure that National Language Support (NLS) and corresponding saplocales are installed. For supported operating system releases, see the Product Availability Matrix at Contact your operating system vendor for the latest OS patches. 70/206 PUBLIC 03/28/2008

71 3 Preparation 3.2 Hardware and Software Requirements Requirements for a Dialog Instance The dialog instance host must meet the following requirements: Hardware Requirements Requirement Hard disk space RAM Swap Space Values and Activities Hard disk drives with sufficient space for the dialog instance. For more information, see Setting up File Systems [page 76]. 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk. For more information, see Preparing the Installation DVDs [page 91]. 1.2 GB of temporary disk space for the installation. 1 GB minimum, 3 GB recommended Hard disk drives with sufficient space for swap: 3 to 4 * RAM Software Requirements Requirement SAP kernel Network File System (NFS) DB2 client connectivity Values and Activities Make sure that the SAP kernel of the central instance has at least the patch level of the SAP kernel on the SAP Kernel DVD that is used for the installation of the dialog instance. We recommend that you apply the most current SAP kernel from the SAP Service Marketplace at Network File System (NFS) must be installed. DB2 V9.1 CLI Driver / DB2 V9.1 JDBC Driver or DB2 V9.5 CLI Driver / DB2 V9.5 JDBC Driver (both are automatically installed by SAPinst) You must only use the DB2 software provided by the SAP installation DVDs. For more information, see SAP Setting up Swap Space for AIX 1. Check the allocated swap space: a) To start the System Management Interface Tool (SMIT), enter the following command: smitty. b) Perform one of the following steps: 03/28/2008 PUBLIC 71/206

72 3 Preparation 3.3 Creating Operating System Users Choose Physical & Logical Storage Logical Volume Manager Paging Space List All Paging Spaces Enter this command: lsps a 2. Check if there is sufficient swap space: 3 to 4 * RAM is recommended. 3. If required, add another paging space using smitty: a) Choose Physical & Logical Storage Logical Volume Manager Paging Space Add Another Paging Space A list of volume group names is displayed. b) Select a volume group. c) Enter the size of paging space in logical partitions. d) Set Start using this paging space NOW? to YES. e) Set Use this paging space each time the system is RESTARTED to YES. f) To exit smitty, choose F10. g) To check the results, follow the procedure described above in step Creating Operating System Users Network Information Service If you use Network Information Service (NIS), you need to distribute users over the network. If you do not create users manually, SAPinst creates them automatically during the installation All users must have identical environment settings. If you change the environment delivered by SAP, such as variables, paths, and so on, SAP does not assume responsibility. SAPinst checks all required users, groups, and services on the local machine. If you manage users, groups or services network-wide in your company, we recommend that you create the user and group NIS entries before running SAPinst as described in Creating Operating System Users and Groups Manually (Optional) [page 72]. SAPinst checks if the required services are available on the host and creates them if necessary. See the log messages about the service entries and adapt the network-wide (NIS) entries accordingly. SAPinst checks the NIS users, groups and services using NIS commands. However, SAPinst does not change NIS configurations. 72/206 PUBLIC 03/28/2008

73 3 Preparation 3.3 Creating Operating System Users Creating Operating System Users and Groups This section does not apply to the installation of a Java Add-In to an existing ABAP system. If you do not want SAPinst to create operating systems users, groups and services, you can optionally create them manually before the installation. If you want to use global accounts that are configured on a separate host, you start SAPinst and choose Life Cycle Management Preparation Operating System Users and Groups. For more information, see Running SAPinst on UNIX [page 104]. Users and Groups SAPinst checks whether the required users and groups already exist. If not, it creates new users and groups as necessary. SAPinst chooses available user IDs and group IDs unless you are installing a dialog instance. On a dialog instance you have to enter the same IDs as on the central instance host. As a general requirement, the user IDs and the group IDs must be the same on all hosts. The user ID (UID) and group ID (GID) of SAP users and groups must be identical for all servers belonging to the same SAP system. This does not mean that all users and groups have to be installed on all SAP servers. Do not delete any shell initialization scripts in the home directory of the OS users. This applies even if you do not intend to use the shells that these scripts are for. Users and Groups User SAP system administrator<sapsid>adm Diagnostics Agent user <smdsid>adm ABAP connect user sap<sapsid> Primary Group sapsys (db<dbsid>ctl as secondary group) sapsys (sapinst as secondary group) db<dbsid>mnt Only used on the database host. 03/28/2008 PUBLIC 73/206

74 3 Preparation 3.3 Creating Operating System Users User Java connect user sap<sapsid>db Primary Group db<dbsid>mnt Only used on the database host. db2<dbsid> db<dbsid>adm Only used on the database host. If these operating system users already exist, make sure that they are assigned to group sapinst. If you install a distributed system and you do not use central user management (for example, NIS), and you use local operating system user accounts instead, user <sapsid>adm and the database operating system user must have the same password on all hosts. Groups and Members Groups sapsys db<dbsid>ctl db<dbsid>adm db<dbsid>mnt Members <sapsid>adm, <smdsid>adm <sapsid>adm db2<dbsid> ABAP connect user sap<sapsid> Java connect user sap<sapsid>db More Information Creating AIX Groups and Users (Optional) [page 74] Creating AIX Groups and Users (Optional) Creating AIX Groups and Users To create AIX groups and users, use the System Management Interface Tool (SMIT) : 1. Create groups as follows: a) Enter the command smitty. b) Choose Security and Users Groups Add a group. c) Enter a group name for example, sapsys and set administration group to true. 74/206 PUBLIC 03/28/2008

75 3 Preparation 3.3 Creating Operating System Users d) Press F3 until the Security & Users menu appears. 2. To create users, proceed as follows: a) Enter a user name, for example <sapsid>adm. b) Enter all required values. 3. Set the initial password using the following command: passwd <user> Example passwd <sapsid>adm Checking Created Users As user root check all existing users as follows: 1. Enter the command smitty. 2. Choose Security & Users Users Change/Show Characteristics of a User. 3. To get a list of users, choose F4. 4. For user root and each created user <user> perform the following steps: a) Select <user>. b) Change field Soft CPU time to -1 (this is the default value). c) Change field Soft CORE file size to (this is the default value). d) Change field Soft FILE size to If you are using large file enabled file systems, set the field Soft FILE size to -1 (unlimited). e) Change field Soft DATA segment to -1. f) Change field Soft STACK size to -1. You must make sure that the system-wide default HARD values are not explicitly defined to be lower than the values given above. Check the file /etc/security/limits under the default: stanza. If they are not explicitly set, then the values are as shown in the table at the top of the file. Checking the Operating System 1. Enter the command smitty. 2. Choose System Environments Change/Show Characteristics of Operating System. 3. Change Maximum number of PROCESSES allowed per user to To exit SMIT, choose F10. More Information For more information about the users and groups that are created either by SAPinst or manually, see Creating Operating System Users and Groups Manually (Optional) [page 73]. 03/28/2008 PUBLIC 75/206

76 3 Preparation 3.4 Setting Up File Systems and Raw Devices 3.4 Setting Up File Systems and Raw Devices The following section(s) describe the directories that are required for the instances of an SAP system, how to set up file systems and if required raw devices on operating system level: SAP Directories [page 76] Directory Structure of the New DB2 Client Connectivity [page 83] Setting Up File Systems and Raw Devices for AIX [page 85] SAP Directories Depending on the installation option you have chosen, SAPinst automatically creates the directories listed in the following figures and tables. Before running the installation, you have to set up the required file systems manually. In addition, you have to make sure that the required disk space for the directories to be installed is available on the relevant hard disks. The figure below assumes that you have set up one file system for the SAP system mount directory <sapmnt> and one file system for the /usr/sap directory. However, you have to decide for which directories you want to set up separate file systems. If you do not set up any file system on your installation host, SAPinst creates all directories in the root directory /. SAPinst prompts you only for the <sapmnt> directory during the installation. See also table Parameters Relevant for the File System in Basic SAP System Parameters [page 26]. Only valid for: HA (UNIX) For more information about how to set up your file systems if you are performing an HA installation, see High Availability: Setting Up File Systems [page 58]. End of: HA (UNIX) SAPinst uses sapcpe to replicate the kernel automatically from /usr/sap/<sapsid>/sys/exe/run/dir_ct_run to /usr/sap/<sapsid>/<instance>/exe/dir_executable for each SAP system instance. The following entry in the start profile is responsible for this: Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_pf), where $(_PF) points to the instance profile. Do not delete DIR_CT_RUN from the instance profile. Otherwise, you cannot restart the system after patches have been applied. For more information, see Applying the Latest Kernel and Support Packages [page 128]. 76/206 PUBLIC 03/28/2008

77 3 Preparation 3.4 Setting Up File Systems and Raw Devices Standard SAP Directories for an ABAP + Java System Both the ABAP part and the Java part of every new installation of an ABAP+Java system are Unicode. We still support non-unicode for ABAP but only if you perform the system copy for a non-unicode system that has been upgraded to SAP NetWeaver 7.0 SR3. Figure 9: SAP Directories for an ABAP + Java System (Unicode) 03/28/2008 PUBLIC 77/206

78 3 Preparation 3.4 Setting Up File Systems and Raw Devices Figure 10: SAP Directories for an ABAP + Java System (ABAP Non-Unicode, Java Unicode) The instance name (instance ID) of the ABAP+Java central instance is DVEBMGS<Instance_Number>, the instance name of an ABAP+Java dialog instance is D<Instance_Number>, and the instance name of the Java central services instance is SCS<No>. Only valid for: HA (UNIX) If you are performing an HA installation of your ABAP+Java system, there is also an ABAP central services instance called ASCS<Instance_Number>. End of: HA (UNIX) Example For example, the file system structure might look as follows: On a central instance with SAP system ID C11 and instance name DVEBMGS00, the J2EE Engine is installed to /usr/sap/c11/dvebmgs00/j2ee, and the corresponding SDM is installed to /usr/sap/c11/dvebmgs00/sdm. On a dialog instance with instance name D01, the J2EE Engine is installed to /usr/sap/c11/d01/j2ee. SAP Directories for the Diagnostics Agent The installation creates the following SAP directories for the Diagnostics Agent. 78/206 PUBLIC 03/28/2008