PUBLIC. Installation Guide. SR2 Java on Linux: Including the following:

Transcription

1 PUBLIC Installation Guide SAP NetWeaver 7.0 SR2 Java on Linux: IBM eserver iseries Including the following: NetWeaver Java Application Server (AS Java) NetWeaver Business Intelligence Java Components (BI Java) NetWeaver Development Infrastructure (DI) NetWeaver EP Core (EPC) NetWeaver Enterprise Portal (EP) Application Sharing Server (Optional Standalone Unit) Target Audience Technology consultants System administrators Document version: /31/2007

2 SAP AG Dietmar-Hopp-Allee Walldorf Germany T +49/18 05/ F +49/18 05/ Copyright 2007 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, System i, System i5, System p, System p5, System x, System z, System z9, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ( SAP Group ) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. This document was created using stylesheet (V5.1beta [= 6.0 for E3]) and XSLT processor SAXON from Michael Kay ( XSLT version 1. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. Legal Software Terms Terms for Included Open Source Software This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply. 1. This software was developed using ANTLR. 2. SAP License Agreement for STLport 2/100 PUBLIC 08/31/2007

3 SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems, Applications, Products in Data Processing Dietmar-Hopp-Allee Walldorf, Germany (hereinafter: SAP) and you (hereinafter: Customer) a) Subject Matter of the Agreement A) SAP grants Customer a non-exclusive, non-transferrable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee. B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement. C) The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. D) Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG E) The Customer may distribute original or modified STLport sources, provided that: The conditions indicated in the above permissions notice are met; The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met: Coypright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems Inc. Copyright 1997 Moscow Center for SPARC Technology. Copyright 1999,2000 Boris Fomitchev Copyright 2001 SAP AG Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications. b) Support and Maintenance SAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included. 08/31/2007 PUBLIC 3/100

4 All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract. c) Exclusion of warranty As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error-free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes. d) Limited Liability A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute. B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typical transfer of the software. C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect or lost profit. D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000. E) The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation. F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP. 3. Adobe Document Services Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see SAP Documentation in the SAP Service Marketplace You can find this document at the following address: 4/100 PUBLIC 08/31/2007

5 Typographic Conventions Example Description < > Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. Example Example Example /example Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address, for example, Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP, for example, SAP Example Example EXAMPLE EXAMPLE Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. Cross-references to other documentation or published works Output on the screen following a user action, for example, messages Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE Keys on the keyboard 08/31/2007 PUBLIC 5/100

6 Document History Caution 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 2.0 8/31/2007 Terminology Changes 6/100 PUBLIC 08/31/2007

7 Table of Contents Chapter 1 Introduction New Features SAP s for the Installation Information Available on SAP Service Marketplace Naming Conventions Chapter 2 Planning Basic SAP System Parameters Running Adobe Document Services on Non-Supported Platforms Chapter 3 Preparation Hardware and Software Requirements Running the Prerequisite Checker in Standalone Mode (Optional) Requirements for Linux Requirements for a Dialog Instance Checking and Modifying the Linux Kernel Setting up Swap Space for Linux Creating Operating System Users Network Information Service Creating Operating System Users and Groups Creating Operating System Users and Groups Manually Creating Linux Groups and Users (Optional) Setting Up File Systems and Raw Devices Setting Up File Systems Setting Up Standard File Systems and Raw Devices for Linux Exporting and Mounting the Global Transport Directory Exporting Directories via NFS for iseries 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 Linux Chapter 4 Installation Prerequisites before Starting SAPinst /31/2007 PUBLIC 7/100

8 4.1.1 Prerequisites before Starting SAPinst: All Instances Prerequisites before Starting SAPinst: Distributed Instances Installing an SAP System Using SAPinst Running SAPinst on UNIX 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 Starting and Stopping the SAP Instance Logging On to the SAP System Logging on to the Portal Configuring Remote Connection to SAP Support Applying the Latest Kernel and Support Packages Performing a Full Installation Backup Post-Installation Steps for Adobe Document Services Assigning Roles to Users ADSUSER and ADS_AGENT Installation Check and Quick Tests for Adobe Document Services Setting Environment Variable CPIC_MAX_CONV Post-Installation Steps for Application Sharing Server Ensuring User Security Running the Configuration Wizard Checking the SAP Java Documentation Accessing Configuration Documentation in the SAP Solution Manager.. 79 Chapter 6 Additional Information Integration of LDAP Directory Services (Optional) 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 Application Server Initial Technical Configuration for Adobe Document Services Initial Technical Configuration for Composite Application Framework Core Configuring System Landscape Directory Initial Technical Configuration for Development Infrastructure (DI) Initial Technical Configuration for the Portal Initial Technical Configuration for BI Java Configuring BI Java Information Broadcasting Process Chains: Transporting Texts for the Alert Category Renaming initialpermissionsbi.xml.template /100 PUBLIC 08/31/2007

9 6.5 Heterogeneous SAP System Installation Deleting an SAP System Deleting an SAP System Using SAPinst 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 Troubleshooting Troubleshooting with SAPinst Troubleshooting for Portal Installation /31/2007 PUBLIC 9/100

10 10/100 PUBLIC 08/31/2007

11 1 Introduction 1 Introduction This document only applies if you are installing on a Linux operating system against IBM DB2 Universal Database for iseries. This document explains how to install SAP NetWeaver 7.0 SR2 Java. For more information about SAP NetWeaver technology, see SAP Service Marketplace at You can install SAP NetWeaver 7.0 SR2 Java with the following usage types in a single installation run of SAPinst: 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 this document. End of: Enterprise Portal (EP) Only valid for: BI Java Components (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 Components (BI-Java) If you want to add additional usage types to an existing SAP system, follow SAP /31/2007 PUBLIC 11/100

12 1 Introduction 1.1 New Features For more information about the usage types of SAP NetWeaver and their interdependencies, see the document Master Guide SAP NetWeaver 7.0 on SAP Service Marketplace [page 15]. For restrictions, see SAP Constraints You need to consider the following constraints before you start your installation: 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. SAP system installations should only be performed by SAP Technical Consultants who are 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 a 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 Here you can find the new features in this release. SAP System Installation Area SAPinst Description As of SAP NetWeaver 7.0, SAPinst has the following new features: 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) 12/100 PUBLIC 08/31/2007

13 1 Introduction 1.1 New Features Area Description 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. You cannot install the Java Add-In for the dialog instance(s) of the existing ABAP system. Instead, you have to install an ABAP+Java dialog instance(s). You can install SAP NetWeaver as a high-availability (HA) system. 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 36]. Installation DVDs Usage type EP Core (EPC) You start the installation from a single Installation Master DVD. As of SAP NetWeaver 7.0 SR2, usage type Enterprise Portal (EP) has been separated into two closely related usage types: EP Core (EPC) and Enterprise Portal (EP). Usage type EPC provides the core portal capabilities available in the former usage type EP. Usage type EP now includes all portal add-on capabilities it provided before, but without the core portal functionality. As of SAP NetWeaver 7.0 SR2, usage type Enterprise Portal (EP) is now divided into two different usage types, EP Core (EPC) and Enterprise Portal (EP). EP Core (EPC) This usage type contains the core portal capabilities that were available in the former usage type EP. This new usage type provides more flexibility when implementing a portal where the full enterprise portal capabilities, such as knowledge management and collaboration, are not needed. It contains the portal, GP, and UWL. Enterprise Portal (EP) This usage type includes Knowledge management, Collaboration, CAF-Core, Visual Composer, Web Dynpro extension, and.net PDK. For more information about EPC and about how to use it in IT scenarios, see the Master Guide and SAP Operating Systems Area Support of Operating Systems Description See the Product Availability Matrix (PAM) on SAP Service Marketplace at 08/31/2007 PUBLIC 13/100

14 1 Introduction 1.2 SAP s for the Installation Documentation Area SAP s Web Dispatcher Installation Application Sharing Server Installation Links in PDF files Description 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 windows opens and the SAP is displayed. The installation of a Web Dispatcher is covered in a dedicated installation guide, available at Installation - Standalone Engines & Clients Installation Guide - Web Dispatcher on <platform> The installation of Application Sharing Server is part of the SAP NetWeaver Java installation guide, available at Installation - SAP NetWeaver 7.0 Installation Documentation - SAP NetWeaver 7.0 SR2 <Database> <Operating System> Java You can use the new links in the PDF files of the guides as follows: Click on the section headings such as New Features to jump back to the table of contents at the beginning of the guide. Click on 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 in the SAP Service Marketplace at You can directly access the SAP s that are related to the SAP NetWeaver installation at SAP s for the Installation SAP Number Title Description SAP NetWeaver 7.0 SR2 / Business Suite 2005 SR2 - UNIX Release Restrictions for SAP NetWeaver 7.0 UNIX-specific information about the SAP system and corrections to this documentation. Customer information on restrictions concerning the production use of certain functions. 14/100 PUBLIC 08/31/2007

15 1 Introduction 1.3 Information Available on SAP Service Marketplace SAP Number Title Description Hardware requirements of Java Development SAP NetWeaver 7.0 Installation on Linux: IBM eserver iseries Information on the hardware requirements for usage type Development Infrastructure (DI), which depends on the size of your development team. Platform-specific information about the SAP system installation (ABAP and Java) and corrections to this documentation iseries: Adjusting UIDs/GIDs for Linux AppServer This note also includes information for SAP NetWeaver 7.0 SR1 and SR2 on Linux. The UIDs and GIDS of users have to match on Linux and iseries Installation Prerequisite Checker SAP Software on UNIX, Windows and iseries: Checking OS Dependencies Linux only: SAP software on Linux: Essential comments This SAP is only required for installations on Linux. It contains Linux-specific information about the SAP system installation. 1.3 Information Available on SAP Service Marketplace More information is available as follows on SAP Service Marketplace. Documentation Description Internet Address Title Master Guide for SAP NetWeaver 7.0 Technical Infrastructure Guide for SAP NetWeaver 7.0 List of media for installation or upgrade for SAP NetWeaver 7.0 Installation of SAP Solution Manager Master Guide SAP NetWeaver Technical Infrastructure Guide SAP NetWeaver Media List SAP NetWeaver /solutionmanager Release <3.2 or 4.0> Installation Guides Installation Guide SAP Solution Manager <release> on <OS>: <Database> 08/31/2007 PUBLIC 15/100

16 1 Introduction 1.3 Information Available on SAP Service Marketplace Description Internet Address Title Configuration of SAP Solution Manager 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 Web Dispatcher /solutionmanager Release <3.2 or 4.0> Installation Guides Configuration Installation - Standalone Engines & Clients Configuration Guide SAP Solution Manager <release> <current stack> Support Package Stack Guide SAP NetWeaver 7.0 Support Package Stack <current stack> Component Upgrade Guide SAP NetWeaver 7.0 Application Server ABAP Installation Guide SAP NetWeaver Developer Workplace Installation Guide SAP NetWeaver Developer Studio Post-Installation Guide System Landscape Directory of SAP NetWeaver 7.0 Installation Guide Web Dispatcher on <platform> for SAP NetWeaver 7.0 SR2 Front End installation Front End Installation Guide (this guide is also available on the Presentation DVD) Homogeneous and heterogeneous system copy for SAP systems based on NetWeaver 7.0 SAP NetWeaver Problem Analysis Guide SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP NetWeaver 7.0 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 Internet Address /100 PUBLIC 08/31/2007

17 1 Introduction 1.4 Naming Conventions Description Released platforms and operating systems Unicode SAP systems and their availability System sizing (Quick Sizer tool) High availability Security Information on SAP Support Package Stacks System Landscape Directory SAP Solution Manager Internet Address Naming Conventions In this documentation, the following naming conventions apply: Terminology SAP system refers to SAP NetWeaver 7.0 SR2. Java system refers to SAP NetWeaver 7.0 SR2 Java. SAP System ID The SAP system ID is abbreviated to SID and SAPSID or sid and sapsid. For <sid> / <sapsid>, substitute your SAP system ID in lower case characters, for example, prd. For <SID> / <SAPSID>, substitute your SAP system ID in upper case characters, for example, PRD. IBM eserver iseries IBM eserver iseries is referred to as iseries. IBM eserver iseries was formerly called IBM AS/400. IBM DB2 Universal Database for iseries IBM DB2 Universal Database for iseries is referred to as DB2 UDB for iseries. IBM DB2 Universal Database for iseries was formerly called IBM Universal Database for AS/400. i5/os and OS/400 The iseries operating system is now called i5/os. In previous versions of this document, i5/os was referred to as OS/ /31/2007 PUBLIC 17/100

18 1 Introduction 1.4 Naming Conventions Variables Variables <SID> and <SAPSID> <sid> and <sapsid> <host_name> <INSTDIR> <DVD_DIR> <OS> Description SAP system ID in uppercase letters SAP system ID in lowercase letters Name of the corresponding host Installation directory for the SAP system Directory on which a DVD is mounted Operating system name within a path 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/c11. 18/100 PUBLIC 08/31/2007

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. 2. You identify basic SAP system parameters [page 19]. 3. 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 24]. 2.1 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. 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.... Caution 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: 08/31/2007 PUBLIC 19/100

20 2 Planning 2.1 Basic SAP System Parameters Parameters Description Enter Your Values Database ID <DBSID> ADD ALL AND ANY ASC COM DBA END EPS FOR GID IBM INT KEY LOG MON NIX NOT OFF OMS RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID USR VAR The <DBSID> identifies the database instance.... On iseries the <SAPSID> and the <DBSID> are always the same. SAP System Instances, Hosts and Ports Parameters Description Enter Your Values Instance Number Name of Instance Host Messaging Service Port Instance Number: Technical identifier for internal processes, consisting of a two-digit number from 00 to 97. 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>/jc<nn> on the host of the central instance. The value <nn> is the number assigned to the central instance. Instance Host: Host name of the specific instance. To find out the host name, open a command prompt and enter hostname. For more information about the allowed host name length and characters, see SAP Caution Make sure that all messaging service port numbers on the same host are unique. Port number of the SAP Messaging Service: If you do not specify a value, the default port number is used. The messaging service port number must be unique for the SAP system on all hosts. The Java messaging service is configured in the SCS instance profile. The Java messaging service port uses the parameter rdisp/msserv_internal with default value 39<nn>, where <nn> is the instance number of the SCS messaging service instance. For more information, see SAP /100 PUBLIC 08/31/2007

21 2 Planning 2.1 Basic SAP System Parameters 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.... Caution 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. Operating System User Parameters Description Enter Your Values Operating System Users and Groups User ID (UID) and Group ID (GID) for the OS user: Make sure that the ID is unique and the same on each instance host. For more information on changing UIDs or GIDs on the System i host, see SAP User Management Engine (UME) Parameter Description Enter Your Values Using the Java Database: Java Administrator User Java Guest User SAPinst sets the user name Administrator and the master password by default. If required, you can choose another user name and password according to your requirements. SAPinst sets the user name Guest and the master password by default. The Guest user is for employees who do not belong to a company or who have registered as company users with pending approval. Guest users belong to the default group Authenticated Users and have read access only. Using an External ABAP System Parameters for the ABAP Connection: /31/2007 PUBLIC 21/100

22 2 Planning 2.1 Basic SAP System Parameters Parameter Description Enter Your Values Application Server Number Application Server Host Communication User This is the instance number on the application server of the central ABAP system to which you want to connect the Application Server Java. To find out the number on the host of the primary application server instance, look under the SAP directory usr/sap/<sapsid>/dvebmgs<nn>. The value <nn> is the number assigned to the SAP system. This is the host name of the relevant application server instance. To find out the host name, enter hostname at the command prompt of the host running the primary application server instance. This is the name and password of the existing ABAP communication user. You must have created this user manually on the external ABAP system. Using an External ABAP System Parameters for the Application Server Java Connection: Administrator User Administrator Role Guest User Guest Role This is the name and password of the administrator user that you created on the external ABAP system. The role SAP_J2EE_ADMIN must exist on the external ABAP system. This is the name and password of the guest user that you created on the external ABAP system. The guest user is for employees who do not belong to a company or who have registered as company users with pending approval. Guest users belong to the default group Authenticated Users and have read access only. The role SAP_J2EE_GUEST must exist on the external ABAP system 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.... Solution Manager Key Parameters Description Enter Your Values 22/100 PUBLIC 08/31/2007

23 2 Planning 2.1 Basic SAP System Parameters 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 86]. 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> SLD Data Supplier User and password Example If the instance number of your Java system is 01, the SLD HTTP Port is 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 The host on which the gateway instance of the SLD is running... 08/31/2007 PUBLIC 23/100

24 2 Planning 2.2 Running Adobe Document Services on Non-Supported Platforms Parameters Description Enter Your Values SLD Gateway Instance Number 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 the File System Parameters Description Your Values File system for the home directory user /home/<username>... 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.... Example If you enter /<sapmnt>, the system creates the directory /<sapmnt>/<sapsid>. 2.2 Running Adobe Document Services on Non-Supported Platforms Adobe document services (ADS) are currently not supported to run natively on all platforms supported by SAP systems based on SAP NetWeaver, in particular on 64-bit platforms. Procedure To use ADS in SAP landscapes on non-supported platforms, install an additional standalone AS Java on a platform supported by ADS. For more information, see SAP /100 PUBLIC 08/31/2007

25 3 Preparation 3 Preparation You have to complete the following preparations: 1. You check the hardware and software requirements [page 25]. 2. If required, you create operating system users manually [page 32]. 3. You set up file systems and raw devices [page 36]. 4. You export and mount global directories: Exporting and Mounting the Global Transport Directory [page 40] Exporting and Mounting Directories via NFS for iseries [page 41] 5. You install the Java Development Kit [page 42]. 6. You prepare and mount the installation media [page 43]. 3.1 Hardware and Software Requirements You check the hardware and software requirements for your operating system (OS) and the SAP instances using the Prerequisite Checker tool. The Prerequisite Checker provides information about the requirements that you need to meet before you start the installation. For example, it checks the requirements for the different installation services. The values that are checked by the Prerequisite Checker apply to the installation of development systems or quality assurance systems. For the most recent updates to the Prerequisite Checker, always check SAP You can run the Prerequisite Checker as follows: Standalone (optional): To check the hardware and software requirements of the host on which you want to later install an SAP system, you can run the Prerequisite Checker standalone [page 26]. Integrated in SAPinst (mandatory): SAPinst automatically runs the Prerequisite Checker when you install your SAP system. We also recommend that you consult the requirements checklists tables, which provide values for the installation of development systems or quality assurance systems. Depending on the amount of data involved, the requirements might change. In addition, consider the following information: To get precise sizing values for production systems, you have to do one of the following: 08/31/2007 PUBLIC 25/100

26 3 Preparation 3.1 Hardware and Software Requirements You use the SAP Quick Sizer tool that is available on SAP Service Marketplace at You enter information about your planned system and the tool calculates the requirements. For more information, see Planning your System Landscape in the Master Guide SAP NetWeaver 7.0, which is available on SAP Service Marketplace [page 15]. You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing. For supported operating system releases, see the Product Availability Matrix on SAP Service Marketplace at 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. Process Flow 1. If required, you run the Prerequisite Checker standalone [page 26] to check the hardware and software requirements. Caution If you do not fully meet the requirements, you might experience problems when working with the SAP system. 2. You check the hardware and software requirements [page 25]. 3. If you want to install additional dialog instances, check the requirements for a Dialog instance [page 29] 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. Recommendation We recommend that you use both the Prerequisite Checker and the requirements tables for reference. When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks the hardware and software requirements in the background. 26/100 PUBLIC 08/31/2007

27 3 Preparation 3.1 Hardware and Software Requirements Prerequisites You have installed the correct Java Development Kit (JDK) [page 42]. You have prepared the installation master DVD on the required installation host [page 43]. You make sure that therequired prerequisites are met before starting SAPinst [page 47]. Procedure 1. You start SAPinst [page 50]. 2. On the Welcome screen, choose <SAP System> Additional Software Lifecycle Tasks Additional Preparation Tasks 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 Linux The host machine must meet the following requirements: The information here is not intended to replace the documentation of the Linux operating system (OS). For more information about the installation on Linux, see SAP /31/2007 PUBLIC 27/100

28 3 Preparation 3.1 Hardware and Software Requirements Requirement Type Hardware Requirement CD /DVD drive ISO 9660 compatible You can configure multiple CD / DVD drives. For more information, see Mounting a CD / DVD for Linux [page 46]. Disks For data security reasons distribution over five disks is recommended (RAID5). 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 print and change the partitioning of the first SCSI disk enter this command: /sbin/fdisk /dev/sda To print and change the partitioning of a RAID device enter commands specific to your hardware. Example Here are some examples of hardware-specific commands for RAID devices: /sbin/fdisk /dev/rd/c0d0 /sbin/fdisk /dev/ida/c0d0 Software RAM To display RAM size in KB enter this command: free CPU The recommended minimum hardware is either two physical single core processors or one physical dual core processor. Operating system Check the operating system version with this command: cat /etc/*-release Linux kernel version Check the Linux kernel version with this command: uname -r Linux kernel parameter settings Check the Linux kernel parameter settings with this command: /sbin/sysctl a Activated hardware drivers Check the activated hardware drivers with this command: lsmod Shared memory file system Check the size of the shared memory file system with this command: df k /dev/shm Network File System (NFS) Check whether NFS is running as follows: On SUSE LINUX rcnfs status rcnfsserver status rcportmap status To check routing information enter this command: netstat -r 28/100 PUBLIC 08/31/2007

29 3 Preparation 3.1 Hardware and Software Requirements Requirement Type Other Requirement System Language For the installation, you must choose English as the operating system language on all Linux hosts that run SAP software. National Language Support NLS) To display available locales enter this command: locale -a Check the output for locales such as the following: de_de, en_us LDAP (Lightweight Directory Access Protocol) If you want to use LDAP, you need the LDAP libraries that are usually installed with the openldap RPM. To check, enter this command: rpm -qa grep openldap Make sure that the output of this command contains at least one of the following RPM packages: Red Hat Linux: openldap2 SUSE LINUX openldap2 openldap2 client C compiler The C compiler gcc must be installed. To check, enter this command: rpm -qa grep gcc Make sure that the output of this command contains a gcc RPM package. Printer Check the status of spooling queues and printers with this command: lpc status Check whether you can print a file with this command: lpr P<printer_name> <test_file> Network Test the network connection to the database server with this command: ping -c 10 <db_server_name> Requirements for a Dialog Instance The dialog instance host must meet the following requirements: 08/31/2007 PUBLIC 29/100

30 3 Preparation 3.1 Hardware and Software Requirements Requirement Type Hardware Software Requirement DVD drive Hard disk drives with sufficient space for the dialog instance. For more information, see Setting up File Systems [page 36]. Hard disk drives with sufficient space for swap: Recommended total size is twice the main memory (2 * RAM). For more information, see SAP 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 43]. 1.2 GB of temporary disk space for the installation. RAM: 500 MB minimum, 1 GB recommended Network File System (NFS) must be installed. Series Access for Linux and 64bit EDRS Driver: To download the latest database driver, proceed as follows: 1. Go to the IBM Web page at 2. On the iseries Access for Linux site, choose Download. The iseries Access page appears. Follow links on this page to: I. Download the 32 bit iseries Access for Linux II. Download the 64-bit EDRS Driver 3. Install the items downloaded above. The iseries Access for Linux product and EDRS driver are delivered as RPM (Redhat Package Manager) archives. Use the setup tool of your Linux distribution to install them (SUSE: Yast), or call the rpm program directly from a Linux shell. Example rpm --install iseriesaccess-64bit ppc64.rpmrpm --query --list iseriesaccess-64bit Check the installation: iseries Access for Linux resides in /opt/ibm/iseriesaccess on the Linux host The 64-bit EDRS driver and supporting files reside in /opt/ibm/iseriesaccess/lib64: libcwbcore.so, libcwbrc.so, libcwbxda.so Checking and Modifying the Linux Kernel If you are using a Linux kernel version certified by SAP, you do not need to modify the Linux kernel. To check the Linux kernel version, enter this command: uname a 30/100 PUBLIC 08/31/2007