Inst guide ehp4 erp6.0

7,487 views
7,351 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
7,487
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
370
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Inst guide ehp4 erp6.0

  1. 1. Installation GuideSAP ERP 6.0 - EHP4 Ready ABAP on Windows: OracleBased on SAP NetWeaver 7.0 including Enhancement Package 1Target Audiencen System Administratorsn Technical ConsultantsPUBLICDocument version: 1.3 ‒ 05/25/2009
  2. 2. About this Installation GuideSAP System Installation regularly release the newest database (DB) andSAP system installations should only be operating-system (OS) versions of SAP products.performed by SAP Technical Consultants These releases are downward-compatible withcertified for your operating system, your earlier SAP system releases.database, and the SAP system that you are Note that for already shipped SAP components,installing we only support the installation for database versions proposed by the installationSAP Installation Tool tool. Therefore, you must install an SAPYou must only use the SAP installation tools component or perform a system copy usingaccording to the instructions and for the a downward-compatible database. Thatpurposes described in the SAP installation is, you either install the component withdocument. Improper use of the SAP installation the old proposed database version or youtools can damage files and systems already upgrade the old database version to theinstalled. downward-compatible new version.Downward Compatibility of DatabasesFor downward-compatible releases of DB/OSplatforms for SAP products, SAP plans to2/170 PUBLIC 05/25/2009
  3. 3. Document History CautionBefore you start the implementation, make sure you have the latest version of this document. Youcan find the latest version at the following location:http://service.sap.com/erp-inst.The following table provides an overview of the most important document changes.Version Date Description1.30 5/25/2009 Minor Changes1.20 2/17/2009 Updated information in Introduction [page 7]1.10 2/5/2009 Removed information from Introduction [page 7]1.0 11/21/2008 Initial Version05/25/2009 PUBLIC 3/170
  4. 4. Table of ContentsChapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 71.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 81.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 10Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 Basic System Variants . . . . . . . . . . . . . . . . . . . . . 132.2 Hardware and Software Requirements . . . . . . . . . . . . . . . 142.2.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 162.2.2 Requirements for a Central System . . . . . . . . . . . . . . . . 172.2.3 Requirements for a Distributed System . . . . . . . . . . . . . . 192.2.4 Requirements for a High-Availability System . . . . . . . . . . . . 212.2.5 Requirements for the Dialog Instance . . . . . . . . . . . . . . . 252.3 Domain or Local Installation . . . . . . . . . . . . . . . . . . 252.4 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . 262.5 Distribution of SAP System Components to Disks . . . . . . . . . . 272.6 SAP System Transport Host . . . . . . . . . . . . . . . . . . . 292.7 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 302.8 Multiple Oracle Homes . . . . . . . . . . . . . . . . . . . . 36Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 393.1 Disabling the Windows Server 2008 Firewall Temporarily . . . . . . . . 393.2 Checking the Windows File System . . . . . . . . . . . . . . . . 403.3 Checking the Windows Domain Structure . . . . . . . . . . . . . 413.4 Reducing the Size of the File Cache . . . . . . . . . . . . . . . . 413.5 Required User Authorization for Running SAPinst . . . . . . . . . . 423.6 Preparing the SAP System Transport Host . . . . . . . . . . . . . 443.7 Installing the Front-End Software . . . . . . . . . . . . . . . . 453.8 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 453.9 Installing the Java Runtime Environment . . . . . . . . . . . . . 453.10 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 463.11 Downloading Installation DVDs from SAP Service Marketplace . . . . . 48Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 514.1 Installing the Oracle Database Software . . . . . . . . . . . . . . 514.2 Setting Up Multiple Homes (Optional) . . . . . . . . . . . . . . 534/170 PUBLIC 05/25/2009
  5. 5. 4.3 Installing an SAP System Using SAPinst . . . . . . . . . . . . . . 544.3.1 Running SAPinst on Windows . . . . . . . . . . . . . . . . . . 544.3.2 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 614.3.3 How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . 624.3.4 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 634.3.5 Performing a Remote Installation with SAPinst . . . . . . . . . . . 654.3.6 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . 664.3.7 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 69Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 715.1 Configuring the Windows Server 2008 Firewall . . . . . . . . . . . . 715.2 Logging On to the Application Server . . . . . . . . . . . . . . . 735.3 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 745.4 Installing the SAP License . . . . . . . . . . . . . . . . . . . 765.5 High Availability: Setting Up Licenses . . . . . . . . . . . . . . . 765.6 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 775.7 Creating Symbolic Links on Windows Server 2008 for Application Servers . . 785.8 Configuring Remote Connection to SAP Support . . . . . . . . . . 795.9 Installing the SAP Online Documentation . . . . . . . . . . . . . 795.10 Performing Initial ABAP Configuration . . . . . . . . . . . . . . 795.11 Performing Oracle-Specific Post-Installation Steps . . . . . . . . . . 835.12 Performing a Full System Backup . . . . . . . . . . . . . . . . 845.13 Configuring the Connection to a Central System Landscape Directory . . . 845.14 Implementing ERP ABAP Add-On Components . . . . . . . . . . . 855.15 Performing the Client Copy . . . . . . . . . . . . . . . . . . 855.16 Accessing Configuration Documentation in SAP Solution Manager . . . . 86Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 896.1 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . 896.2 Performing a Domain Installation Without Being a Domain Administrator . 936.3 Installation of Multiple Components in One Database . . . . . . . . . 966.4 Integration of LDAP Directory Services . . . . . . . . . . . . . . 986.5 Starting and Stopping the SAP System . . . . . . . . . . . . . . . 1016.6 Implementing Single Sign-On with Microsoft Kerberos SSP for Your SAP System 1026.7 SAP System Security on Windows . . . . . . . . . . . . . . . . 1036.8 Automatic Creation of Accounts and Groups . . . . . . . . . . . . 1056.9 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 1066.9.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 1066.10 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 1076.11 Deleting the Oracle Database Software . . . . . . . . . . . . . . 110Chapter 7 High Availability with Microsoft Cluster Service . . . . . . . . . 11305/25/2009 PUBLIC 5/170
  6. 6. 7.1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 1147.1.1 System Configuration in MSCS . . . . . . . . . . . . . . . . . 1157.1.1.1 SAP System Components in an MSCS Configuration . . . . . . . . . 1157.1.1.2 Enqueue Replication Server in an MSCS Configuration . . . . . . . . 1197.1.2 Distribution of SAP System Components to Disks for MSCS . . . . . . . 1207.1.3 Directories in an MSCS Configuration . . . . . . . . . . . . . . . 1257.1.4 IP Addresses in an MSCS Configuration . . . . . . . . . . . . . . 1267.1.5 Obtaining and Determining IP Addresses for MSCS . . . . . . . . . . 1297.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 1317.2.1 Assigning Drive Letters for MSCS . . . . . . . . . . . . . . . . 1327.2.2 Mapping Host Names to IP Addresses for MSCS . . . . . . . . . . . 1327.2.3 Checking the Mapping of Host Names for MSCS . . . . . . . . . . . 1337.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . 1347.3.1 Moving MSCS Groups or Services and Applications . . . . . . . . . . 1367.3.2 Rebooting During the Installation or Conversion for MSCS . . . . . . . 1377.3.3 Installing the Oracle Fail Safe Software in a 64-Bit System . . . . . . . . 1377.3.4 Installing the Central Services Instance for ABAP (ASCS) . . . . . . . . 1407.3.5 Configuring the First MSCS Node . . . . . . . . . . . . . . . . 1417.3.6 Installing the Database Instance . . . . . . . . . . . . . . . . . 1427.3.7 Configuring the Additional MSCS Node . . . . . . . . . . . . . . 1437.3.8 Additional Steps for the Oracle Fail Safe Configuration . . . . . . . . . 1447.3.9 Installing an Enqueue Replication Server . . . . . . . . . . . . . . 1457.3.10 Installing the Central Instance . . . . . . . . . . . . . . . . . 1477.3.11 Creating the Oracle Fail Safe Group . . . . . . . . . . . . . . . . 1487.3.12 Setting Up a Shared Database Directory in Oracle Home . . . . . . . . 1497.3.13 Adding the Oracle Database Resource to the Fail Safe Group . . . . . . . 1507.3.14 Installing the Dialog Instance . . . . . . . . . . . . . . . . . . 1517.4 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . 1527.4.1 Starting and Stopping the SAP System in an MSCS Configuration . . . . . 1537.4.2 Post-Installation Checks for Enqueue Replication Server . . . . . . . . 1547.4.2.1 Checking the Status of the Enqueue Replication Server with ENSMON . . . 1547.4.2.2 Monitoring the Lock Table During Failover with ENQT . . . . . . . . 155Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . 159A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . 1596/170 PUBLIC 05/25/2009
  7. 7. 1 Introduction1 IntroductionThis document explains how to install SAP ERP 6.0 — EHP4 Ready (EHP4 for SAP ERP 6.0) ABAP.You perform the installation using SAPinst.SAP ERP 6.0 ‒ EHP4 Ready is based on the technology of SAP NetWeaver 7.0 including enhancementpackage 1. For more information about the technology provided by SAP ERP and SAP NetWeaver, seehttp://service.sap.com/erp and http://sdn.sap.com/irj/sdn/netweaver.Make sure you read the corresponding Master Guides before you start with this installation guide.The Master Guides are available as follows: http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAPenhancement package 4 for SAP ERP 6.0 CautionSee SAP Note 998833 for up-to-date information about release restrictions for EHP4 for SAP ERP 6.0.You can install SAP ERP 6.0 - EHP4 Ready with the following software units:n SAP ERP Central Component (ECC) Note SAP ERP Central Component (ECC) is not installed with the Java Add-In. NoteYou also install SAP NetWeaver Application Server ABAP (AS ABAP) with SAP ERP CentralComponent.For more information about the usage types of SAP NetWeaver and their interdependencies, seethe document Master Guide ‒ SAP NetWeaver 7.0 at http://service.sap.com/instguidesNW70. Forrestrictions, see SAP Note 1164532.ConstraintsYou need to consider the following constraints before you start your installation:n Your operating system platform must be 64-bit. Note The only instance, you can still install on 32-bit is the dialog instance.05/25/2009 PUBLIC 7/170
  8. 8. 1 Introduction1.1 New Featuresn The database must be Oracle 10.2.0.2 or higher.You need to consider the following constraints after the installation:n The installation of SAP ERP 6.0 - EHP4 Ready ABAP system based on SAP NetWeaver 7.0 including enhancement package 1 contains only the basic EHP4 for SAP ERP 6.0 technical usage “ABAP Technology for ERP EHP4”. To complete the installation process you have to install additional EHP4 for SAP ERP 6.0 functionality in your SAP ERP 6.0 - EHP4 Ready ABAP system. You must use the Solution Manager Maintenance Optimizer to identify and download the corresponding software components and the SAP enhancement package Installer to deploy the downloaded software components in your system. For more information about the Solution Manager Maintenance Optimizer, see: http://service.sap.com/solman-mopz. For more information about the SAP enhancement package Installer, see the document Installation Guide - SAP Enhancement Package Installation - Using SAP Enhancement Package Installer (SAPehpi) at: http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 4 for SAP ERP 6.0 Enhancement Package Installation on Existing SAP Systemsn You have to apply at least Support Package Stack (SPS) 1 of SAP enhancement package 4 for SAP ERP 6.0.Naming ConventionsTerminologyn SAP system refers to EHP4 for SAP ERP 6.0.n ABAP system refers to EHP4 for SAP ERP 6.0 ABAP.1.1 New FeaturesThe following tables provide an overview of the new features related to the installation of this release: Caution Make sure that you read the release notes for your SAP system. You can find these at http://service.sap.com/releasenotes8/170 PUBLIC 05/25/2009
  9. 9. 1 Introduction1.1 New FeaturesSAP System Installation Area Description SAPinst As of SAP enhancement package 4 for SAP ERP 6.0, SAPinst has the following new features: n You no longer have to install a Java Runtime Environment (JRE) to start the SAPinst GUI. However, you still have to install a JRE to perform the installation with SAPinst (see Installing the Java Runtime Environment (JRE) [page 45]). n If you want to terminate SAPinst from the SAPinst GUI menu, you now have to choose SAPinst Cancel . If you choose File Exit , you only terminate the SAPinst GUI (see Using SAPinst GUI [page 61]). n You can directly access installation log files from the SAPinst GUI menu by choosing SAPinst Log Browser (see Using SAPinst GUI [page 61]). 64-bit support only As of SAP ERP 6.0 SR3, you must install an SAP ERP system only on 64-bit operating for all instances except systems. dialog instances For the dialog instance, you can still use a 32-bit operating system. Therefore, you only see the folder Software Life-Cycle Options on the Welcome screen when you start the installation from a 32-bit installation master DVD. You might need to install dialog instances on 32-bit operating systems if you want to use 32-bit SAP NetWeaver components, such as Adobe document services. However, first check whether such 32-bit components can run on 64-bit operating systems. If so, we recommend running these 32-bit components on a 64-bit operating system. No new dual stack As of SAP enhancement package 4 for SAP ERP 6.0, you can no longer install SAP (ABAP+Java) systems ERP dual stack (ABAP+Java) systems. If you want to use both SAP ERP ABAP and for SAP enhancement Java Components in your system landscape, you have to proceed as follows: package 4 for SAP ERP 1. Install a separate SAP ERP ABAP system. 6.0 2. Install a separate SAP ERP Java system. 3. Configure the connection of the SAP ERP Java system to the SAP ERP ABAP back-end system Installation option Java As of SAP enhancement package 4 for SAP ERP 6.0, the installation option Java Add-In for ABAP disabled Add-In for ABAP is disabled. That is, you can no longer install the Java Add-In to an existing ABAP system. High Availability Note As of Windows Server 2008, the Windows cluster terminology has changed. n The cluster feature is now called Failover Clustering. For practical reasons we are continuing to use the general abbreviation MSCS in this guide. n Cluster groups are now called services and applications. n The Cluster Administrator is now called Failover Cluster Management. Maintenance All downloadable software components, released after April 2, 2007, are available Optimizer exclusively through the Maintenance Optimizer in SAP Solution Manager. This comprises: n Support Package Stacks, Support Packages, and patches for Java instances, except for kernel patches n Legal changes n SAP applications and versions that are:05/25/2009 PUBLIC 9/170
  10. 10. 1 Introduction1.2 SAP Notes for the Installation Area Description l Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and all applications based on this software, including SAP Business Suite 7 l Optional for all SAP applications For more information, see http://service.sap.com/solman-mopz.Operating Systems and Platforms Area Description Support of Operating Note Systems and Platforms This document already includes information about the new Windows operating system, Windows Server 2008, although this is not yet supported by SAP at the time of publishing. n For supported operating system and database releases, see the Product Availability Matrix at http://service.sap.com/pam. n For forums, blogs, content, and community related to all of the supported databases and operating systems, see the Database and Operating Systems area at http://sdn.sap.com/irj/sdn/dbos.Oracle Database Area Description New features in Oracle 10g For the complete list of new features, see further documentation from Oracle, which you can find at: http://www.oracle.com/technology/products/database/oracle10g See also: n http://www.oracle.com/technology/documentation/ database10g.html View Library n The documentation provided by Oracle on the RDBMS DVD under <DVD_Drive>:NT<platform>databasedocindex.htm1.2 SAP Notes for the InstallationYou must read the following SAP Notes before you start the installation. These SAP Notes contain themost 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 Note, which you can find athttp://service.sap.com/notes.10/170 PUBLIC 05/25/2009
  11. 11. 1 Introduction1.2 SAP Notes for the InstallationSAP Notes for the Installation SAP Note Number Title Description 998833 Release Restrictions SAP ERP 6.0 At the time of the release of EHP4 for SAP ERP - Enhancement Packages 6.0, limitations affect the productive usage of certain functions. This note provides customer information on these restrictions. 1165067 Release Info SAP Enhancement SAP Enhancement Package 4 for SAP ERP 6.0 Package 4 for SAP ERP 6.0 release information. 1164532 Release Restrictions for SAP Customer information on restrictions in the NetWeaver 7.0 EHP1 production use of certain functions. 1171448 SAP NetWeaver 7.0 EHP Windows-specific information about the SAP 1/Business Suite 7: Windows system installation and corrections to this documentation. 1171451 SAP NetWeaver 7.0 EHP Oracle-specific information about the SAP 1/Business Suite 7: Win Oracle system installation and corrections to this documentation. 828268 Oracle 10g: New functions Information about new Oracle features released for the SAP system. 855498 Installation Prerequisite Checker SAP Software on UNIX, Windows and IBM i: Checking OS Dependencies 73606 Supported Languages and Code Information on possible languages and language Pages combinations in SAP systems 1067221 Central Note for Heterogeneous Heterogeneous ABAP system landscapes on Installation 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 Note and its related SAP Notes describe the released operating system and database combinations. 789220 Support Package Information about the ABAP Support Package level for NetWeaver levels and kernel patch levels contained in the Installations/Upgrades current SAP NetWeaver release. 774615 Support Package levels of Information about the ABAP Support Package ERP/ECC installations/upgrades levels and kernel patch levels contained in the current SAP ERP release. 1258912 PLM Core 7.00 Release Notes and Information and references to other notes about Information installing PLM Core 7.00 and importing PLM Core 7.00 Support Packages.05/25/2009 PUBLIC 11/170
  12. 12. This page is left blank for documents that are printed on both sides.
  13. 13. 2 Planning2 PlanningThis section tells you how to plan the installation of your SAP system.You have to complete the following planning activities, which are described in more detail in thelinked sections:1. You plan your SAP system landscape according to the Master Guide. In addition, we recommend that you read theTechnical Infrastructure Guide ‒ SAP NetWeaver 7.0, which is available at: http://service.sap.com/installNW70.2. You choose your basic system variant [page 13].3. You check the hardware and software requirements [page 14] on each host.4. You decide whether you want to perform a domain or local installation [page 25].5. You plan how to distribute the instances to hosts [page 26].6. For the database installation, you decide on how to distribute your database components to disk [page 27].7. You decide on the transport host to use [page 29].8. You identify basic SAP system parameters [page 30].9. You decide if you want to use Multiple Oracle Homes [page 36]. Only valid for: HA (MSCS)10. If you want to perform a high-availability installation with Microsoft Cluster Service (MSCS), see also the MSCS-specific planning activities [page 114]. End of: HA (MSCS)The following planning activity is optional:n Installation of Multiple Components in One Database (MCOD) [page 96]2.1 Basic System VariantsThis section describes the basic system variants and shows how you can distribute SAP systeminstances within these variants.Mandatory instances of an ABAP system are the central instance and the database instance. NoteOptionally, you can install one or more dialog instances on a separate dialog instance host.05/25/2009 PUBLIC 13/170
  14. 14. 2 Planning2.2 Hardware and Software RequirementsThe following graphics show examples for the distribution of the SAP instances in a central system,where the mandatory instances are installed on one host, and a distributed system, where themandatory instances are installed on separate hosts.Figure 1: ABAP SystemMore Information Only valid for: HA (MSCS)For more information about how to distribute SAP instances in a high-availability SAP system, seeSystem Configuration in MSCS [page 115]. End of: HA (MSCS)2.2 Hardware and Software RequirementsYou check that your hosts meet the hardware and software requirements for your operating systemand the SAP instances. CautionIf your hosts do not fully meet the requirements, you might experience problems when workingwith the SAP system.Prerequisitesn Contact your OS vendor for the latest OS patches.14/170 PUBLIC 05/25/2009
  15. 15. 2 Planning2.2 Hardware and Software Requirementsn Make sure that the host name meets the requirements listed in SAP Notes 611361 and 849423.Process Flow1. Check the Product Availability Matrix at http://service.sap.com/pam for supported operating system releases.2. Check the hardware and software requirements using: n The Prerequisite Checker in one of two modes: l Standalone mode (optional) before the installation process For more information, see Running the Prerequisite Checker Standalone [page 16]. l Integrated in SAPinst (mandatory) during the installation process For more information, see Running SAPinst on Windows [page 54] Note For the most recent updates to the Prerequisite Checker, always check SAP Note 855498. n The hardware and software requirements checklists for: l Central system [page 17] l Distributed system [page 19] Only valid for: HA (MSCS) l High availability system with MSCS [page 21] End of: HA (MSCS) l If you want to install dialog instance(s), check the requirements for a dialog instance [page 25]. Note You might need to install dialog instances on 32-bit operating systems if you want to use 32-bit SAP NetWeaver components, such as Adobe document services. However, first check whether such 32-bit components can run on 64-bit operating systems. If so, we recommend running these 32-bit components on a 64-bit operating system.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: n You use the Quick Sizer tool available at http://service.sap.com/sizing. For more information about the Quick Sizer and available sizing guides, see the Master Guide ‒ SAP NetWeaver 7.0 at http://service.sap.com/installnw70 Planning . n You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing depending on: l The set of applications to be deployed l How intensively the applications are to be used05/25/2009 PUBLIC 15/170
  16. 16. 2 Planning2.2 Hardware and Software Requirements l The number of users2.2.1 Running the Prerequisite Checker in Standalone Mode(Optional)Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check thehardware and software requirements for your operating system (OS) and the SAP instances. RecommendationWe recommend that you use both the Prerequisite Checker and the requirements tables for reference. NoteWhen installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks thehardware and software requirements in the background.Prerequisitesn You have prepared the installation master DVD on the required installation host [page 46].Procedure1. You start SAPinst [page 54].2. On the Welcome screen, choose <Your SAP product> Software Life-Cycle Options Additional Preparations Prerequisites Check .3. Follow the instructions in the SAPinst dialogs and enter the required parameters. Note 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 and want to have checked. If you want to make a change, select the relevant parameters and choose Revise.4. To start the prerequisites check, choose Next.ResultThe Prerequisite Checker Results screen displays the results found. If required, you can also check theresults in file prerequisite_checker_results.html, which you can find in the installation directory.16/170 PUBLIC 05/25/2009
  17. 17. 2 Planning2.2 Hardware and Software Requirements RecommendationWe recommend making sure that your system meets all checked prerequisites before starting theinstallation. However, you can still start the installation even if your system does not meet allprerequisites. In this case, make sure that you know what you are doing.2.2.2 Requirements for a Central SystemIf you want to install a central system, where all instances reside on one host, this host must meetthe following requirements: NoteThe listed values are sufficient for development systems or quality assurance systems but not forproduction systems.Hardware Requirements for a Central SystemHardware Requirement Requirement How to CheckMinimum disk space n Database Software: To check disk space: 1 GB (x64) 1. Choose Start Control Panel 2 GB (IA64) Administrative Tools Computer n SAP system files (not including paging Management Storage Disk file): Management . 5 GB (x64) 8 GB (IA64) 2. Right-click the drive and choose n SAP database files (not including paging Properties. file): 76 GB n 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard diskMinimum RAM 4 GB To check RAM: In the Windows Explorer, choose Help About Windows .05/25/2009 PUBLIC 17/170
  18. 18. 2 Planning2.2 Hardware and Software RequirementsHardware Requirement Requirement How to CheckPaging file size 1 times RAM plus 14 GB To check paging file size: 1. Choose Start Control Panel System . 2. Choose Advanced (Windows Server 2003) or Advanced system settings (Windows Server 2008). 3. Select Performance Settings Advanced . 4. If required, in section Virtual memory, choose Change.Suitable backup system ‒Software Requirements for a Central SystemSoftwareRequirement Requirement How to CheckWindows n English international 64-bit version of one of To check your Windows version:operating the following Windows Server Editions: 1. Choose Start All Programssystem l Windows Server 2003 Accessories Command Prompt18/170 PUBLIC 05/25/2009
  19. 19. 2 Planning2.2 Hardware and Software RequirementsSoftwareRequirement Requirement How to Check u Windows Server 2003 Standard Edition 2. Enter the command winver u Windows Server 2003 Enterprise Edition u Windows Server 2003 Datacenter Edition l Windows Server 2008 u Windows Server 2008 Standard Edition u Windows Server 2008 Enterprise Edition u Windows Server 2008 Datacenter Edition u Windows Server 2008 for Itanium-Based Systems Edition Caution Windows Server 2008 is not yet supported by SAP at the time of publishing. For up-to-date information on the released and supported operating system versions for your SAP product and database, see the Product Availability Matrix (PAM) at http://service.sap.com/pam . n For any version of Windows Server, you need the latest supported service pack n A suitable Windows Resource Kit is strongly recommended n Updated processor drivers For more information, see SAP Note 1036194.Database n Database server software for Oracle 10g ‒software n Current Oracle patch set and hot fix, if available Note For more information about the current patch set, see SAP Note 8717352.2.3 Requirements for a Distributed SystemThis section provides information about the hardware and software requirements in a distributedsystem, where the SAP instances can reside on different hosts.The tables show the requirements for the:n Database instancen Central instancen Dialog instance (optional)05/25/2009 PUBLIC 19/170
  20. 20. 2 Planning2.2 Hardware and Software Requirements Note n The listed values are sufficient for development systems or quality assurance systems but not for production systems. n If you install several SAP instances on one host, you need to add up the requirements.Hardware Requirements for a Distributed SystemHardwareRequirement Requirement How to CheckMinimum disk space n Database software: To check disk space: 1 GB (x64) 1. Choose Start Control Panel 2 GB (IA64) Administrative Tools Computer n Database instance (not including paging Management Storage Disk file): Management . 76 GB n Central instance (not including paging 2. Right-click the drive and choose file): Properties. 5 GB (x64) 8 GB (IA64) l In addition you require 4 GB (x64), or 8 GB (IA64) per additional platform. n Dialog instance (optional) (not including paging file): 2.5 GB (x64) 5 GB (IA64) n Temporary disk space for every required installation DVD that you have to copy to a local hard disk: 4.3 GBMinimum RAM 4 GB To check RAM: In the Windows Explorer, choose Help About Windows .Paging file size n Database instance: To check paging file size: 1.5 times RAM 1. Choose Start Control Panel n Central instance: System . 1 times RAM plus 14 GB n Dialog instance (optional): 2. Choose Advanced (Windows Server 1 times RAM plus 14 GB 2003) or Advanced system settings (Windows Server 2008). 3. Select Performance Settings Advanced . 4. If required, in section Virtual memory, choose Change.Suitable backup system ‒20/170 PUBLIC 05/25/2009
  21. 21. 2 Planning2.2 Hardware and Software RequirementsSoftware Requirements for a Distributed SystemSoftwareRequirement Requirement How to CheckWindows n English international 64-bit version of one of To check your Windows version:operating the following Windows Server Editions: 1. Choose Start All Programssystem l Windows Server 2003 Accessories Command Prompt u Windows Server 2003 Standard Edition 2. Enter the command winver u Windows Server 2003 Enterprise Edition u Windows Server 2003 Datacenter Edition l Windows Server 2008 u Windows Server 2008 Standard Edition u Windows Server 2008 Enterprise Edition u Windows Server 2008 Datacenter Edition u Windows Server 2008 for Itanium-Based Systems Edition Caution Windows Server 2008 is not yet supported by SAP at the time of publishing. For up-to-date information on the released and supported operating system versions for your SAP product and database, see the Product Availability Matrix (PAM) at http://service.sap.com/pam. n For any version of Windows Server, you need the latest supported service pack n A suitable Windows Resource Kit is strongly recommended n Updated processor drivers For more information, see SAP Note 1036194.Database n Database instance: ‒software l Database server software for Oracle 10g l Current Oracle patch set and hot fix, if available. For more information about the current patch set, see SAP Note 871735 Only valid for: HA (MSCS)2.2.4 Requirements for a High-Availability SystemThis section provides information about the hardware and software requirements in a high-availabilitysystem.05/25/2009 PUBLIC 21/170
  22. 22. 2 Planning2.2 Hardware and Software Requirements Note1. Windows Server 2003 only: You must check that your cluster hardware is certified. AddOn Technology Center for SAP (Add On TCS) certifies hardware platforms for SAP on Microsoft Windows. The cluster must be included in the Microsoft list of certified clusters and its components. You can access the lists as follows: n www.microsoft.com/whdc/hcl/default.mspx n www.saponwin.com2. Windows Server 2008 only: a) Check that your cluster hardware is certified for Windows Server 2008 and has the Windows Server 2008 logo. b) You must validate your failover cluster configuration by running the Validate a Configuration Wizard, which is included in the Failover Cluster Management snap-in. The Failover Cluster Validation Report must not show any warnings and errors.3. The MSCS nodes of the cluster must be connected by a private and public network: n The public network enables communication from the MSCS nodes of the cluster to other resources in the local area network (LAN). n The private network enables internal communication between the MSCS nodes. In particular, it enables the Cluster Service running on all MSCS nodes to regularly exchange messages on the state of the MSCS nodes so that the failure of resources is quickly detected.4. Each of the MSCS nodes in the cluster must have its own local disks and have access to shared disks that can be reached by the MSCS nodes via a shared bus. All software ‒ except the Windows operating system, the Oracle home directory, and the MSCS software ‒ is stored on the shared disks. One of the shared disks must be used exclusively by the quorum (if a single quorum device cluster is used) that stores the cluster registry and records information about the state of the cluster. You require at least four shared disks. For more information about the distribution of components to local and shared disk, see Distribution of SAP System Components to Disks for MSCS [page 120]. Caution n All disk controllers must be able to support hardware-based RAID. n You cannot use a host with a domain controller as an MSCS cluster node.The following tables show the hardware and software requirements for the:n ABAP central services instance (ASCS)n Database instancen Enqueue Replication Server instance (ERS)22/170 PUBLIC 05/25/2009
  23. 23. 2 Planning2.2 Hardware and Software Requirementsn Central instancen Dialog instance Note n The listed values are sufficient for development systems or quality assurance systems but not for production systems. n If you install several SAP instances on one host, you need to add up the requirements.Hardware Requirements for a High-Availability System Hardware Require- ment Requirement How to Check Minimum n Database Software: To check disk space: disk space 1 GB (x64) 1. Choose Start Control Panel 2 GB (IA64) Administrative Tools Computer n ABAP central services instance (ASCS) Management Storage Disk (not including paging file): Management . 5 GB (x64) 8 GB (IA64) 2. Right-click the drive and choose l In addition you require 4 GB (x64), or 8 GB (IA64) Properties. per additional platform. n Database instance (not including paging file): 76 GB n Enqueue replication server instance (ERS) (not including paging file): 5 GB (x64) 8 GB (IA64) n Central instance (not including paging file): 2.5 GB (x64) 5 GB (IA64) l In addition you require 4 GB (x64), or 8 GB (IA64) per additional platform. n Dialog instance (not including paging file): 2.5 GB (x64) 5 GB (IA64) n Temporary disk space for every required installation DVD that you have to copy to a local hard disk: 4.3 GB Minimum 4 GB To check RAM: RAM In the Windows Explorer, choose Help About Windows .05/25/2009 PUBLIC 23/170
  24. 24. 2 Planning2.2 Hardware and Software Requirements Hardware Require- ment Requirement How to Check Paging file n ABAP central services instance (ASCS): To check paging file size: size 1 times RAM plus 1 GB 1. Choose Start Control Panel n Database instance: System . 1.5 times RAM 2. Choose Advanced (Windows n Enqueue replication server instance (ERS): 1 times RAM plus 1 GB Server 2003) or Advanced system settings (Windows Server 2008). n Central instance: 1 times RAM plus 14 GB 3. Select Performance Settings n Dialog instance: Advanced . 1 times RAM plus 14 GB 4. If required, in section Virtual memory, choose Change. Note You must adjust the size of the paging file on all MSCS nodes. Suitable ‒ backup systemSoftware Requirements for a High Availability System Software Requirement Requirement How to Check Windows n English international 64-bit version of one To check your Windows version: operating of the following Windows Server Editions: 1. Choose Start All Programs system l Windows Server 2003 Accessories Command Prompt u Windows Server 2003 Enterprise Edition 2. Enter the command winver u Windows Server 2003 Datacenter Edition Note l Windows Server 2008 n Windows Server 2003 only: u Windows Server 2008 Enterprise Edition You must set up the MSCS Cluster Service as described in the Microsoft u Windows Server 2008 Datacenter Edition documentation. During this setup you are asked for a Windows u Windows Server 2008 for Itanium-Based Systems Edition Domain Account to run the Cluster Service. We strongly recommend creating an account different from Caution the <sapsid>adm user, for example Windows Server 2008 is not yet supported ClusterServiceuser=sapprdcladm, by SAP at the time of publishing. where Clustername=sapprdcl. For up-to-date information on the n Windows Server 2008 only: released and supported operating You must add the operating system system versions for your SAP feature Failover Clustering on all MSCS24/170 PUBLIC 05/25/2009
  25. 25. 2 Planning2.3 Domain or Local InstallationSoftwareRequirement Requirement How to Check product and database, see the nodes. Product Availability Matrix (PAM) at http://service.sap.com/pam n For any version of Windows Server, you need the latest supported service pack n A suitable Windows Resource Kit is strongly recommended n Updated processor drivers For more information, see SAP Note 1036194.Database n Database instance: ‒software l Oracle 10g database server software l Current Oracle patch set and hot fix, if available. For more information about the current patch set, see SAP Note 871735 l Oracle Fail Safe software version 3.3.4 End of: HA (MSCS)2.2.5 Requirements for the Dialog InstanceFor more information about the hardware and software requirements for the dialog instance(s), seeone of the following sections:n Requirements for a Distributed System [page 19] Only valid for: HA (MSCS)n Requirements for a High-Availability System [page 21] End of: HA (MSCS)2.3 Domain or Local InstallationBefore you install the SAP system, you have to decide whether you want to perform a domain orlocal installation, since this affects how the user account information is stored and accessed.05/25/2009 PUBLIC 25/170
  26. 26. 2 Planning2.4 How to Distribute Instances to HostsFor more information about the differences between a local and domain installation, see theMicrosoft article Deciding Between Workgroups and Domains at:http://technet2.microsoft.com/windowsserver/en/library/Domain InstallationIn a domain installation, the user account information is stored centrally in one database on thedomain controller and is accessible to all hosts in the system.You have to perform a domain installation if one of the following applies:n You install a distributed system (strongly recommended to avoid authorization problems). Only valid for: HA (MSCS)n You install a high-availability system with MSCS. End of: HA (MSCS)n You want to use Single Sign-On.n You use a common transport host for several SAP systems running on different computers.Local InstallationIn a local installation, all Windows account information is stored locally on one host and is notvisible to any other hosts in the system.If the SAP system is to run on a single machine (central system), you can perform a local installation. NoteIf your SAP system was installed as a local installation and you want to later change to a domaininstallation, you must perform a homogeneous system copy. For more information, see thedocumentation System Copy for SAP Systems based on SAP NetWeaver <release> <technology> at: http://service.sap.com/instguides <your product>More Informationn Required User Authorization for Running SAPinst [page 42]n Implementing Single Sign-On with Microsoft Kerberos SSP [page 102]2.4 How to Distribute Instances to HostsThe following provides information on how you can distribute the SAP instances for the different SAPsystem variants. You use SAPinst to install the SAP instances as a:n Central system on a single host You run SAPinst and install all instances on one host.n Distributed system on several hosts You perform the following steps:26/170 PUBLIC 05/25/2009
  27. 27. 2 Planning2.5 Distribution of SAP System Components to Disks 1. You specify or create a shared transport directory. 2. You run SAPinst and prepare the global host. 3. You run SAPinst and install the: l Database instance on the database host l Central instance on the global host l Dialog instance(s), if required, on the dialog instance host(s) The following figure shows how to distribute your instances to several hosts: Figure 2: Distribution of Instances in an ABAP System2.5 Distribution of SAP System Components to DisksWhen you install the SAP system, the main directories required for the system are automaticallycreated. However, during the installation procedure, SAPinst prompts you to enter drive letters forthe main components of the system. This gives you the opportunity to distribute components todisks in the system as you wish. How you do this significantly affects system throughput and datasecurity, and must therefore be carefully planned. The best distribution depends on your specificenvironment and must take into consideration factors such as the size of the components involved,security requirements and the expected workload.When you work out the assignment of components to disks, you first need to get an overview of themain components and their corresponding directories. Then, on the basis of sample configurationsand the recommendations provided in this documentation, you can decide which assignment is bestfor your particular system.05/25/2009 PUBLIC 27/170
  28. 28. 2 Planning2.5 Distribution of SAP System Components to DisksSAP systems are normally installed on RAID arrays that ensure data redundancy. This documentationtherefore focuses on RAID subsystems and drives.Minimal ConfigurationThe following figure illustrates an example for a disk configuration for a small test or demo system.Since security and performance play a less crucial role in this type of system, many differentconfigurations are feasible. CautionUse the illustrated configuration exclusively for test or demo systems. It is unsuitable for productionsystems because it only minimally satisfies security and performance requirements.Figure 3: Minimal ConfigurationDistribution of Directories to DisksDisk DirectoriesDisk 1 ORACLE<DBSID>102 ORACLE<DBSID>origlogA ORACLE<DBSID>origlogB ORACLE<DBSID>sapdata1 ORACLE<DBSID>sapdata228/170 PUBLIC 05/25/2009
  29. 29. 2 Planning2.6 SAP System Transport HostDisk DirectoriesDisk 2 ORACLE<DBSID>mirrlogA ORACLE<DBSID>mirrlogB ORACLE<DBSID>sapreorg ORACLE<DBSID>saptrace ORACLE<DBSID>saparch ORACLE<DBSID>sapbackup ORACLE<DBSID>sapcheck ORACLE<DBSID>sapdata3 ORACLE<DBSID>sapdata4Disk 3 ORACLE<DBSID>oraarchCommentsn The configuration ensures that no data can be lost, but the process for recovering a damaged database is complicated and time-consuming.n The redo logs and database files are located on the same disks. This means that a single disk failure can result in the loss of both the redo logs and database data.n The I/O-intensive redo logs are on the same disk volumes as the data files. This can impede performance.n An equally good alternative would be to simply place all components on a single RAID 5 array.2.6 SAP System Transport HostThe transport host contains the transport directory used by the SAP transport system to storetransport data and change SAP system information, such as software programs, data dictionary data,or customization data. If you have several SAP systems, they are usually organized in transportdomains. In most cases, all SAP systems in a transport domain have a common transport directory.When you install an SAP system, you have to decide which transport host and directory you wantto use for your SAP system:n Use the transport directory that SAPinst creates during the installation of the SAP system by default on the global host: SAPinst by default creates the transport directory on the global host in usrsaptrans.n Use a transport directory located on a host other than the default host: l You can use an existing transport directory and host in your SAP system landscape. l You can set up a new transport directory on a different host. In either case, you must prepare this host for use by the new SAP system [page 44].More Informationn SAP Directories [page 89]n See the SAP Library:05/25/2009 PUBLIC 29/170
  30. 30. 2 Planning2.7 Basic SAP System Parameters http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) 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 ‒ Concept2.7 Basic SAP System ParametersSAPinst prompts for input parameters during the Define Parameters phase of the installation.The tables below list the basic system parameters that you need to specify before installing your SAPsystem. For all other SAP system parameters, use the F1 help in the SAPinst screens.You can install your SAP system either in Typical or Custom mode:n Typical If you choose Typical, the installation is performed with default settings. This means that you only have to respond to a small selection of prompts including at least the following, which are described in the corresponding tables below: l SAP system ID and database ID l Master password l SAP system profile directory ‒ only for systems with instances on separate hosts If you want to change any of the default settings, you can do so on the Parameter Summary screen.n Custom If you choose Custom, you are prompted for all parameters. At the end, you can still change any of these parameters on the Parameter Summary screen. NoteIf you change a parameter with the Revise button on the Parameter Summary screen, the installer takesyou to the screen where you can change the parameter. Depending on the changes, the installermight guide you through other screens with default parameters that it has so far processed. Thismight also happen if you press Back instead of Next on the screenThe tables below list the basic system parameters that you need to determine before installing yourSAP system. For all other SAP system parameters, use the F1 help in the SAPinst dialogs.30/170 PUBLIC 05/25/2009
  31. 31. 2 Planning2.7 Basic SAP System ParametersJava Runtime EnvironmentParameters DescriptionJava Runtime Environment (JRE) A valid JRE is required for the installation with SAPinst. For more information about JRE versions supported by SAP and about how to install them, see Installing the Java Runtime Environment [page 45].SAP System ID and Database IDParameters DescriptionSAP 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: n Is unique throughout your organization. Do not use an existing <SAPSID> when installing a new SAP system. n Consists of exactly three alphanumeric characters n Contains only uppercase letters n Has a letter for the first character n 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 n If you want to install a dialog instance, make sure that no gateway instance with the same SAP system ID (SAPSID) exists in your SAP system landscape.Database ID <DBSID> 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>. Caution Choose your database ID carefully. Renaming is difficult and requires you to reinstall the SAP system. n If you want to install a new database: Make sure that your database ID: l Is unique throughout your organization l Consists of exactly three alphanumeric characters l Contains only uppercase letters l Has a letter for the first character l 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 n If you want to use an existing database system:05/25/2009 PUBLIC 31/170
  32. 32. 2 Planning2.7 Basic SAP System ParametersParameters Description Enter exactly the database ID of the existing database to which you want to add the system.Unicode or Non-Unicode SystemParameters DescriptionUnicode System Every new installation of an SAP system is Unicode. You can only deselect this option if you perform the system copy for a non-Unicode SAP system that has been upgraded to SAP NetWeaver 7.0 including Enhancement Package 1.SAP System Instances, Hosts and PortsParameters DescriptionInstance Number of the Technical identifier for internal processes. It consists of a two-digit number fromSAP system 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 <Drive>:usrsap<SAPSID>DVEBMGS<nn> on the host of the central instance. The value <nn> is the number assigned to the central instance. Caution Do not use 43, and 89 for the instance number because: n 43 is used by MSCS n 89 is used by Windows Terminal ServerName of Instance Host 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 Note 611361. In addition, see SAP Note 849423.32/170 PUBLIC 05/25/2009
  33. 33. 2 Planning2.7 Basic SAP System ParametersParameters DescriptionVirtual Host Name You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to conceal their physical network identities from each other. This may be useful when moving SAP servers or complete server landscapes to other new hardware within a short time frame without having to carry out a reinstallation or complicated reconfiguration. You need to specify the virtual host name before you start SAPinst. For more information, see Prerequisites in Running SAPinst on Windows [page 54]. Only valid for: HA (MSCS) You also need to specify the virtual host name before you start SAPinst if you want to install a high-availability (HA) system End of: HA (MSCS) n For more information about the use of virtual TCP/IP host names, see SAP Note 962955. n For more information about the allowed host name length and characters, see SAP Note 611361.Message Server Port Caution 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 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. For more information about the parameters used for message server ports, see SAP Note 821875.Master PasswordParameters DescriptionMaster Password Common password for all users created during the installation: n Operating system users (for example <sapsid>adm, SAPService<sapsid>) Caution If you did not create the operating system users manually before the installation, SAPinst creates them with the common master password (see table Operating System Users). In this case, make sure that the master password meets the requirements of05/25/2009 PUBLIC 33/170
  34. 34. 2 Planning2.7 Basic SAP System ParametersParameters Description your operating system and of your database. n ABAP users SAP* and DDIC Caution SAPinst applies the master password to users SAP*and DDIC for SAP system clients 000 and 001 only, but not to users SAP*, DDIC, and EARLYWATCH in SAP system client 066. Instead, SAPinst always assigns the following passwords to these users in client 066: SAP*: 06071992 EARLYWATCH: support See also Ensuring User Security [page 74]. n Database users n Secure Store key phrase For more information, see table Key Phrase for Secure Store Settings. Note If a user already exists, you are prompted to confirm the password for this user. Password policy The master password: n Must be 8 to 14 characters long n Must contain at least one letter (a-z, A-Z) n Must contain at least one digit (0-9) n Must not contain (backslash) and " (double quote) Depending on the installation option, additional restrictions might apply (for example, the master password must not contain the name of a Java user created during the installation).Operating System UsersParameters DescriptionPassword of Operating SAPinst processes the passwords of operating system users as follows:System Users n If the operating system users do not exist, SAPinst creates the following users: l <sapsid>adm This user is the SAP system administrator user and is a member of the local Administrators group. l SAPService<SAPSID> This user is the Windows account to run the SAP system and is not a member of the local Administrators group. 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.34/170 PUBLIC 05/25/2009
  35. 35. 2 Planning2.7 Basic SAP System ParametersParameters Description n 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. Caution Make sure that you have the required user authorization [page 42] for these accounts before you start the installation with SAPinst.Solution Manager KeyParameters DescriptionSAP Solution Manager key To install your SAP system, you need to generate an SAP Solution Manager key [page 45], which the installation requires to continue. For more information, see SAP Note 805390.Parameters for SAPDATA DrivesParameters DescriptionInstallation drive Base directory for the SAP system. Do not add <SAPSID> as subdirectory because the system adds this directory automatically. Example If you enter D:, the system adds the directory D:usrsapSAPSID. Note If you install a subsequent SAP system, the saploc share already exists and you cannot select the installation drive. SAPinst uses the installation drive where the saploc share points to.Parameters Relevant for the DatabaseParameters DescriptionCode page The code page that is used by your database (Unicode or Non-Unicode). Note You only need to enter this parameter if you perform a target system installation as part of a system copy.05/25/2009 PUBLIC 35/170
  36. 36. 2 Planning2.8 Multiple Oracle HomesParameters DescriptionDatabase schema, Passwords The ABAP database schema is named SAP<SCHEMA_ID>. Default name is SAPSR3. Recommendation Choose a <SCHEMAID> that is different from your <SAPSID>. It might cause problems when you copy a system where <SCHEMAID> is the same as <SAPSID>, and the database-specific method used for the copy does not allow you to rename the database schemas. In certain situations, you might create a system copy with a new <SAPSID>, but where the database schema has the old <SAPSID>. This is not a technical problem, but might confuse the system administrator.Oracle parameters n Oracle home n SAPDATA drives n Drives for redolog and archives (oraarch)Oracle Listener Name, Oracle n If you install the database instance on a host where no other OracleListener Port database is installed, you normally do not have to change the default values for Listener Name and Listener Port. n If you install the database instance on a host where already another Oracle database is installed you have the following options: l If you install it in the same Oracle home, you use the default values for Listener Name and Listener Port. l If you install it in a different Oracle home, you specify an unused Listener Name and Listener Port for the new Oracle Listener. n All dialog instances of an SAP system must use the same Listener Port than the database instance.2.8 Multiple Oracle HomesOracle lets you install multiple Oracle Homes on one host. Only valid for: HA (MSCS) NoteMSCS only:Multiple Oracle Homes for different database instances are not supported in an MSCS configuration. End of: HA (MSCS)Note the following about multiple Oracle Homes:n Multiple Oracle Homes are not required if you install a system into an existing database (MCOD) [page 96]n Multiple Oracle Homes are necessary, if you install different Oracle versions for two or more databases on the same host.n If you use multiple Oracle Homes, you must use different port numbers for each listener.36/170 PUBLIC 05/25/2009
  37. 37. 2 Planning2.8 Multiple Oracle Homesn If you install the same Oracle database version on one host for different database instances, you can use: l Multiple Oracle Homes With multiple Oracle Homes, you can administer your databases independently. For example, if you want to install a patch set, you do not have to install them on both databases. l One Oracle Home for two databases You have to install the database software only once. Note In case you later want to use two multiple homes instead of one, you either have to perform a new database instance installation or upgrade your database.Before you install your Oracle database software, you need to decide whether you want to set upmultiple Oracle Homes as this influences the installation procedure. For more information, seeSetting Up Multiple Oracle Homes [page 53].05/25/2009 PUBLIC 37/170
  38. 38. This page is left blank for documents that are printed on both sides.
  39. 39. 3 Preparation3 Preparation NoteIn a central system, all mandatory instances are installed on one host. Therefore, if you are installinga central system, you can ignore references to other hosts.You have to complete the following preparations, which are described in more detail in the linkedsections:1. If you use Windows Server 2008 you temporarily disable the Windows Server 2008 Firewall [page 39] on each host.2. You check the Windows file system [page 40] on each host.3. You check that your installation host belongs to the correct Windows domain [page 41].4. If you use Windows Server 2003, you reduce the size of the file cache [page 41] on each host.5. You check that you have the required user authorization for running SAPinst [page 42].6. If required, you prepare the SAP system transport host [page 44] for your SAP system.7. You install the SAP front-end software [page 45] on the desktop of the end user.8. You generate the SAP Solution Manager Key [page 45] for your SAP system.9. You install the Java Runtime Environment [page 45].10. You make the installation DVDs available [page 46] on each host.11. If required, you download the installation DVDs from SAP Service Marketplace [page 48]. Only valid for: HA (MSCS)12. For the installation of a high-availability system with Microsoft Cluster Service (MSCS), in addition, you have to perform MSCS-specific preparation tasks [page 131]. End of: HA (MSCS)3.1 Disabling the Windows Server 2008 Firewall TemporarilyAs of Windows Server 2008, the Windows firewall is turned on by default. It is configured to allowonly a small set of Windows-specific inbound IP connections. Outbound connections by default arenot limited to rules and are therefore not restricted by the firewall.The default firewall settings are valid for the out-of-the-box installation of Windows Server 2008 andapply to local policies. For domain policies that override local policies, other rules might apply.To avoid any problems with nonconfigured TCP/IP ports that are used by the SAP system, you need totemporarily disable the firewall before you install the SAP system with SAPinst.05/25/2009 PUBLIC 39/170
  40. 40. 3 Preparation3.2 Checking the Windows File System CautionWhen you have finished the installation with SAPinst, make sure that you turn on the firewallagain and configure it properly [page 71].Procedure Only valid for: HA (MSCS) NoteIn a high-availability system, you have to disable the firewall on all MSCS nodes. End of: HA (MSCS)1. Choose Start Administrative Tools Windows Firewall with Advanced Security .2. Right-click Windows Firewall with Advanced Security and choose Properties.3. Choose the relevant profile (in most cases Domain Profile) and set the Firewall state to Off. Note To turn on the firewall again, set the Firewall state to On.3.2 Checking the Windows File SystemYou need to check that you are using the Windows file system NTFS on hosts where you want toinstall the SAP system and database. NTFS supports full Windows security and long file names. NoteYou must use NTFS for an SAP system installation. Do not install the SAP directories on a FATpartition.Procedure1. Open the Windows Explorer.2. Select the relevant disk.3. Choose Properties General . The system displays the type of file system in use.4. Check that the file system is NTFS.40/170 PUBLIC 05/25/2009
  41. 41. 3 Preparation3.3 Checking the Windows Domain Structure3.3 Checking the Windows Domain Structure NoteYou do not need this step for a local installation.In Windows, you can implement either of the following domain models for the SAP system:n Extra domain In this model, the SAP system is embedded in its own domain, which is specially defined for SAP. A second domain exists for the user accounts. In Windows, the SAP domain and user domain must be incorporated in a domain tree. In this tree, the user accounts must form the root domain and the SAP domain must be a child domain of this.n Single domain In this model, the SAP system and the user accounts are included in a single domain.Prerequisitesn You are performing a domain installation.n You are familiar with checking Windows domain structures. For more information, see the Windows documentation. Caution You cannot create local users and groups on the host that is used as domain controller. Therefore, we do not support running an SAP instance (including the database instance) on the host where the domain controller is installed.ProcedureFor a domain installation, we recommend that you check that all SAP system and database hosts aremembers of a single Windows domain. We recommend this for all SAP system setups.3.4 Reducing the Size of the File Cache NoteThis step is not required if you use Windows Server 2008.The Windows file cache directly competes with SAP programs for memory. Therefore, you shouldadjust the file cache as described below.05/25/2009 PUBLIC 41/170
  42. 42. 3 Preparation3.5 Required User Authorization for Running SAPinst Only valid for: HA (MSCS) Note For a high-availability configuration, you must adjust the size of the file cache on all cluster nodes. End of: HA (MSCS)Procedure1. Choose Start Control Panel Network Connections Local Area Connections .2. In the Local Area Connection Status dialog box, choose Properties.3. In the Local Area Connection Properties dialog box, double-click File and Printer Sharing for Microsoft Networks.4. Select Maximize data throughput for network applications. Caution If you cannot select File and Printer Sharing for Microsoft Networks, this option has not yet been installed. To install it, you need the Windows Server CDs.5. To confirm your entries, choose OK.3.5 Required User Authorization for Running SAPinstAlthough SAPinst automatically grants the required rights to the user account used for theinstallation, you have to check whether this account has the required authorization to perform theinstallation. The authorization required depends on whether you intend to perform a domain orlocal installation. If necessary, you have to ask the system administrator to grant the account thenecessary authorization before you start the installation. If you attempt the installation with anaccount that has not the required authorization, the installation aborts.This section informs you about the authorization required for a domain and a local installation. Caution Do not use the user <sapsid>adm for running SAPinst.Domain InstallationFor a domain installation the account used for the installation needs to be a member of the localAdministrators and the domain Admins group of the domain involved. All machines in the systemmust belong to the same domain. In a domain installation, the user information is stored centrally onthe domain controller and is accessible to all hosts in the system.If the SAP system is to be distributed across more than one machine, SAP strongly recommends youto perform a domain installation to avoid authorization problems.42/170 PUBLIC 05/25/2009
  43. 43. 3 Preparation3.5 Required User Authorization for Running SAPinst Caution n If you install a distributed system as a local installation, this can lead to authorization problems for the operating system users <sapsid>adm and SAPService<SAPSID>. It can also lead to problems with the transport directory, which is usually shared by several SAP systems. Therefore, SAP does not support a local installation for a distributed system and recommends you to install a distributed system as a domain installation. If you still want to perform a local installation for a distributed system, make sure that: l You use the same password for the <sapsid>adm or the SAPService<SAPSID> user on all hosts. The password for the <sapsid>adm and SAPService<SAPSID> user can differ. l You use the same master password on all hosts. l All hosts belong to the same Windows work group. Only valid for: HA (MSCS) n In an MSCS configuration, you always have to perform a domain installation. End of: HA (MSCS) n For performance and security reasons, SAP does not support an SAP system installation on a domain controller. n If for any reason, the account used for the installation is not a member of the domain Admins group, you can perform the installation with a domain user who is a member of the local Administrators group. However, the domain administrator has to prepare the system appropriately for you. For more information, see Performing a Domain Installation without being a Domain Administrator [page 93].For a domain installation, you need to:1. Check that the account used for the installation is a member of the domain Admins group.2. If required, obtain these rights by asking the system administrator to enter the account as a member of the domain Admins group.Local InstallationFor a local installation the account used for the installation needs to be a member of the localAdministrators group of the machine involved. In a local installation, all Windows accountinformation is stored locally on one host and is not visible to any other hosts in the system.If the SAP system is to run on a single machine, you can perform a local installation.For a local installation, you need to:1. Check that the account used for the installation is a member of the local Administrators group.2. If required, obtain these rights by asking the system administrator to enter the account as a member of the local Administrators group.05/25/2009 PUBLIC 43/170
  44. 44. 3 Preparation3.6 Preparing the SAP System Transport Host3.6 Preparing the SAP System Transport HostThe transport host has a directory structure that is used by the SAP transport system to storetransport data and metadata.When you install an SAP system, SAPinst by default creates the transport directory on the globalhost in usrsaptrans.If you want to use another new transport directory located on a host other than the default host, oran existing transport directory in your SAP system landscape, you need to prepare that transporthost for the new SAP system:n If the directory structure already exists, you must set up its security to allow the new system to write to it.n If it does not yet exist, you must create the core directory structure and a share to export it for other computers as well as set the security on it.The global transport directory usrsaptrans is used by the Change and Transport System (CTS).The CTS helps you to organize development projects in the ABAP Workbench and in Customizing,and then transport the changes between the SAP systems in your system landscape. For moreinformation, see: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAPNetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key CapabilitySoftware Life Cycle Management Software Logistics Change and Transport SystemProcedure1. If the transport directory does not yet exist, do the following: a) Create the directory usrsaptrans on the host to be used as the transport host. b) Share the usrsap directory on the transport host as SAPMNT and put the security settings for Everyone to Full Control for this share. This enables SAPinst to address the transport directory in the standard way as SAPTRANSHOSTSAPMNTtrans.2. Grant Everyone the permission Full Control for the transport directory. Caution Remove the Full Control to Everyone permission after you have finished the installation with SAPinst and only grant Full Control on this directory to the SAP_<SAPSID>_GlobalAdmin groups of all the systems that are part of your transport infrastructure. SAPinst assigns the appropriate rights with the help of an additional SAP_LocalAdmin group. For more information, see Automatic Creation of Accounts and Groups [page 105].44/170 PUBLIC 05/25/2009

×