netwiewer for 7.4 unix

Installation GuideDocument version: 1.7 2014-07-07

SAP Systems Based on the Application Server Java of SAP NetWeaver on UNIX: OracleValid for SAP NetWeaver 7.1 to 7.4

CUSTOMER

About this Installation Guide

SAP System InstallationSAP systems should only be installed by SAP Technical Consultants certified for your operating system, your database, and the SAP system that you are installing.

SAP Installation ToolUse 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.

Downward Compatibility of DatabasesFor 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.Note that for already shipped SAP components, we only support the installation for database versions proposed by the installation tool. Therefore, you must install an SAP component or perform a system copy using a downward-compatible database. That is, you either install the component with the old proposed database version or you upgrade the old database version to the downward-compatible new version.

2

CUSTOMER Copyright 2014 SAP AG.All rights reserved.

SAP Systems Based on the Application Server Java of SAP NetWeaver on UNIX: OracleAbout this Installation Guide

Typographic Conventions

Table 1Example Description Angle brackets indicate that you replace these words or characters with appropriate entries to

make entries in the system, for example, Enter your .

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

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 worksExample 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

EXAMPLE 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

EXAMPLE Keys on the keyboard

SAP Systems Based on the Application Server Java of SAP NetWeaver on UNIX: OracleTypographic Conventions

CUSTOMER Copyright 2014 SAP AG.

All rights reserved. 3

Document History

CautionBefore you start the implementation, make sure you have the latest version of this document that is available at service.sap.com/instguides.

The following table provides an overview of the most important document changes.

Table 2Version Date Description1.7 2014-07-07 Updated Version

Instead of a separate installation guide for each UNIX-based operating system, we now deliver a single installation guide for all UNIX-based operating systems. Sections that are only relevant for one or more operating systems are highlighted accordingly.

1.6 2014-03-17 Updated Version1.5 2013-10-28 Updated Version1.4 2013-07-15 Updated Version1.3 2013-04-02 Updated Version1.2 2012-11-27 Updated Version1.1 2012-09-25 Updated Version1.0 2012-08-06 Initial Version

4


SAP Systems Based on the Application Server Java of SAP NetWeaver on UNIX: OracleDocument History

Content

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.4 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2 Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3 High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.4 Additional Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.5 SAP Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Running the Prerequisites Check in Standalone Mode (Optional) . . . . . . . . . . . . . . . . . . . . . . . . 20 Requirements for the SAP System Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.3 Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.4 SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.5 Diagnostics Agent Specific Planning Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Connection Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Direct SAP Solution Manager Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 System Landscape Directory Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.6 Planning the Switchover Cluster for High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.2 Creating Operating System Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.3 Required File Systems and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Oracle Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Setting Up File Systems for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4.4 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.5 Performing Switchover Preparations for High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.6 Preparing an External ABAP System as Source for User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.7 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.2 Exporting and Mounting the Transport Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.3 Exporting and Mounting Global Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.4 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.5 Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

SAP Systems Based on the Application Server Java of SAP NetWeaver on UNIX: OracleContent



Useful Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Interrupted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Entries in the Services File Created by the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Troubleshooting with the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

5.6 Oracle Database 11g Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Updating the SAP RUNINSTALLER Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Performing Pre-Installation Steps for the AIX Operating System . . . . . . . . . . . . . . . . . . . . . . . . . 90 Installing the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Installing the Required SAP Bundle Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946.2 Performing Post-Installation Steps for the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956.3 Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956.4 Logging On to the SAP Enterprise Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966.5 Providing Access to the NetWeaver Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976.6 Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976.7 High Availability: Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986.8 Configuring the Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996.9 Applying the Latest Kernel and Support Package Stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996.10 PI-PCK, PI-AF, PI-AEX, PI-CP: System Configuration After Installation . . . . . . . . . . . . . . . . . . . . . . 1006.11 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026.12 Performing Oracle-Specific Post-Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046.13 Performing a Full Installation Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087.1 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087.2 Installing Oracle Real Application Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127.3 Installing Database Instance on Oracle Automatic Storage Management . . . . . . . . . . . . . . . . . . . . . 1147.4 Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157.5 Creating a User for LDAP Directory Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177.6 Setting Up File Systems for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177.7 Exporting and Mounting Directories via NFS for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207.8 Heterogeneous SAP System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217.9 Installation of Additional Usage Types or Software Units in an Existing SAP System . . . . . . . . . . . . . 1217.10 Installing the SAP Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217.11 Starting and Stopping SAP System Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Starting and Stopping SAP System Instances Using the SAP Management Console . . . . . . . . . . 124 Starting and Stopping SAP System Instances Using Commands . . . . . . . . . . . . . . . . . . . . . . . . 126 Starting and Stopping the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

7.12 Troubleshooting for SAP Enterprise Portal Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307.13 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317.14 Deleting the Oracle Database 11g Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

6


SAP Systems Based on the Application Server Java of SAP NetWeaver on UNIX: OracleContent

1 Introduction

This document describes how to install an SAP system based on the Java application server of SAP NetWeaver using the installation tool software provisioning manager 1.0 SP06 (installer for short), which is part of SL Toolset 1.0 SP11.This guide is valid for the operating systems AIX, HP-UX, Linux, and Solaris.It applies to the following releases:Table 3Product Release

SAP NetWeaver Composition Environment

SAP NetWeaver Composition Environment 7.1 SAP NetWeaver Composition Environment 7.1 including Enhancement Package 1 SAP NetWeaver Composition Environment 7.2

SAP NetWeaver SAP NetWeaver 7.3 SAP NetWeaver 7.3 including Enhancement Package 1 SAP NetWeaver 7.4 SAP NetWeaver 7.4 Support Release 1

SAP ERP SAP Enhancement Package 4 for SAP ERP 6.0 on SAP NetWeaver 7.3 / 7.3 EHP1 / 7.4 Java

SAP Enhancement Package 5 for SAP ERP 6.0 on SAP NetWeaver 7.3 / 7.3 EHP1 / 7.4 Java

SAP Enhancement Package 6 for SAP ERP 6.0 on SAP NetWeaver 7.3 / 7.3 EHP1 / 7.4 Java

SAP Enhancement Package 7 for SAP ERP 6.0 on SAP NetWeaver 7.4 SAP Enhancement Package 7 SR1 for SAP ERP 6.0 on SAP NetWeaver 7.4 SR1

SAP CRM SAP CRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 / 7.4 Java SAP Enhancement Package 1 for SAP CRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 /

7.4 Java SAP Enhancement Package 2 for SAP CRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 /

7.4 Java SAP Enhancement Package 3 for SAP CRM 7.0 on SAP NetWeaver 7.4 SAP Enhancement Package 3 SR1 for SAP CRM 7.0 on SAP NetWeaver 7.4 SR1

SAP SRM SAP SRM 7.0 on SAP NetWeaver 7.3 / 7.3 / 7.4 EHP1 Java SAP Enhancement Package 1 for SAP SRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 /

7.4 Java SAP Enhancement Package 2 for SAP SRM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 /

7.4 Java SAP Enhancement Package 3 for SAP SRM 7.0 on SAP NetWeaver 7.4 SAP Enhancement Package 3 SR1 for SAP SRM 7.0 on SAP NetWeaver 7.4 SR1

SAP Systems Based on the Application Server Java of SAP NetWeaver on UNIX: OracleIntroduction



Product Release

SAP SCM SAP SCM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 Java SAP Enhancement Package 1 for SAP SCM 7.0 on SAP NetWeaver 7.3 / 7.3 EHP1 /

7.4 Java SAP Enhancement Package 3 for SAP SCM 7.0 on SAP NetWeaver 7.4 SAP Enhancement Package 3 SR1 for SAP SCM 7.0 on SAP NetWeaver 7.4 SR1

NoteNot all SAP NetWeaver releases or SAP Business Suite applications that are available in software provisioning manager 1.0 and are described in this installation guide have already been released. Always check SAP Note 1680045 to ensure that the installation options you want to perform are already supported.

CautionMake sure you have read Before You Start [page 8] before you continue with this installation guide.

Constraints Your operating system platform must be 64-bit.

Naming Conventions installer refers to software provisioning manager 1.0. SAP system refers to SAP system based on the application server of SAP NetWeaver CE 7.1 / 7.1 including

Enhancement Package 1 / SAP NetWeaver CE 7.2 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver 7.4 / 7.4 SR1.

Java system refers to SAP system based on the Java application server of SAP NetWeaver CE 7.1 / 7.1 including Enhancement Package 1 / SAP NetWeaver CE 7.2 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver 7.4 / 7.4 SR1.

Diagnostics Agent refers to the SAP Solution Manager Diagnostics Agent which is the remote component of End-to-End Root Cause Analysis. It allows having a connection between SAP Solution Manager and managed systems, and then to collect information from the managed systems for reporting purposes.

1.1 Before You StartMake sure that you have read the release-specific Master Guide for your SAP Business Suite application or SAP NetWeaver application and release before you continue with this installation guide.The Master Guide is the central document leading you through the overall implementation process for your SAP system installation. It contains crucial information about the overall implementation sequence, that is activities you have to perform before and after the installation process described in this installation guide.You can find a printed version of the Master Guide in your installation package or you can download the latest version from SAP Service Marketplace.The following table lists the Master Guides of the SAP system applications for which you can use this installation guide, along with the available quick link or path to the appropriate download location under service.sap.com/instguides:

8



Table 4Document Internet Address

Master Guide - SAP NetWeaver Composition Environment 7.1

service.sap.com/instguidesnwce71

Master Guide - SAP NetWeaver CE 7.1 Including EHP1 service.sap.com/instguidesnwce711 Installation Planning

Master Guide - SAP NetWeaver Composition Environment 7.2

service.sap.com/instguidesnwce72 Installation Planning

Master Guide SAP NetWeaver 7.3 service.sap.com/installNW73

Master Guide SAP Enhancement Package 1 for SAP NetWeaver 7.3

service.sap.com/installNW73

Master Guide SAP NetWeaver 7.4 service.sap.com/installNW74

Master Guide - SAP Enhancement Package for SAP ERP 6.0

service.sap.com/erp-inst SAP ERP 6.0 Planning

Master Guide (Including Upgrade Information) - SAP Supplier Relationship Management 7.0

service.sap.com/srm-inst

Master Guide (Including Upgrade Information) - SAP Customer Relationship Management 7.0

service.sap.com/crm-inst Plan

Master Guide SAP Supply Chain Management 7.0 Powered by SAP NetWeaver

service.sap.com/instguides SAP Business Suite Applications SAP SCM Master Guide

1.2 New FeaturesThe table below provides an overview of the new features.Make sure that you also read the release notes at service.sap.com/releasenotes.Table 5Area Description

Software Provisioning Manager Software provisioning manager is the successor of the product- and release-specific delivery of provisioning tools, such as SAPinst. Before you perform an installation or system copy, we recommend that you always download the latest version of the software provisioning manager [page 63] which is part of the Software Logistics Toolset (SL Toolset for short). This way, you automatically get the latest SAPinst version including latest fixes in the tool and supported processes. For more information about software provisioning manager as well as products and releases supported by it, see SAP Note 1680045.As a result, SAPinst has been renamed to software provisioning manager (installer for short) in this documentation.However, the term SAPinst is still used in:




Area Description Texts and screen elements in the software provisioning manager GUI Naming of executables, for example sapinst Naming of command line parameters, for example

SAPINST_USE_HOSTNAME Operating system user groups, for example additional group sapinst

You no longer require a Solution Manager Key for the installation. The SAP Cryptographic Library SAPCRYPTO.SAR is now available in the DBINDEP

subfolder of the UC kernel (folder K__U_) medium and installed automatically by software provisioning manager. You no longer have to separately download SAPCRYPTO.SAR. For more information, see Basic SAP System Installation Parameters [page 28].

Process Integration and Orchestration is available as an optional standalone unit installation.

New option Verify Signed Media:The digital signature ensures that the signatory of a digital document can be identified unambiguously and signatory's name is documented together with the signed document, the date, and the time.For more information, see SAP Note 1979965

Support of Oracle Linux Oracle Linux is supported for SAP system installation.For more information, see SAP Note 1565179.

Support of Oracle Solaris 11 Oracle Solaris 11 is supported for SAP system installation.For more information, see SAP Note 1669684.

NoteOracle Solaris 11 might not have been released yet for all database platforms and versions. If you want to install on Oracle Solaris 11, first check the product availability matrix (PAM) available at service.sap.com/pam to see whether your database platform or version is supported.

Diagnostics Agent The Diagnostics Agent is no longer installed automatically with the SAP system. You can install it optionally by selecting the Install Diagnostics Agent check box on the Install Diagnostics Agent screen.

RecommendationWe recommend that you install the Diagnostics Agent separately and prior to the installation of your SAP system(s). If applicable we recommend to use the Agents On-the-fly feature.For more information, see the Diagnostics Agent Installation Strategy attached to SAP Note 1365123, to SAP Note 1833501, and to SAP Note 1858920 and the there attached Diagnostics Agent Setup Guide.

10



Area DescriptionThe Diagnostics Agent Setup Guide has additional Diagnostics Agent-related information that is not included in this document - for example, on kernel and JVM specifics, and on usage of the smdsetup script.

Valid only for SAP NetWeaver Composition Environment 7.1:Enterprise Services Repository

You can install Enterprise Services Repository in an existing SAP NetWeaver Composition Environment 7.1 system using the Add ESR Capability installation option, which is available on the Welcome screen at:

SAP NetWeaver Composition Environment (CE) 7.1 SAP SystemsApplication Server Java Enterprise Services Repository Add-On

1.3 SAP Notes for the InstallationYou must read the following SAP Notes before you start the installation. These SAP Notes 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 Note, which you can find at service.sap.com/notes.Table 6: SAP Notes for the InstallationSAP Note Number Title Description

1680045 Release Note for Software Provisioning Manager 1.0

Software provisioning manager 1.0 with installation and system copy for SAP NetWeaver-based systems

1704753 Inst.Systems based on NetWeaver 7.1 and higher: UNIX

UNIX-specific information about the installation for SAP systems and corrections to this documentation

1704754 Inst.Systems based on NetWeaver 7.1 and higher: Unix Oracle

Oracle-specific information about the SAP system installation and corrections to this documentation

828268 Oracle 10g: New functions Information about Oracle 10g features released for the SAP system

1431800 Oracle 11.2.0: Central Technical Note Information about Oracle 11g with multiple links to notes on Oracle 11g

98252 Installing two Oracle databases on a host This SAP Note is only required if you plan to install more than one Oracle database on the same host

1365123 Installation of Diagnostics Agents Overview of the Diagnostics Agent installation strategies

1833501 Diagnostics Agent Installer Versions More information about available Diagnostics Agent installer versions

1858920 Diagnostics Agent installation with SWPM Installation and Post-installation steps for SWPM based installers




SAP Note Number Title Description

737368 Hardware requirements of Java Development Information on the hardware requirements for usage type Development Infrastructure (DI), which depends on the size of your development team

855498 Installation Prerequisite Checker SAP Software on UNIX, Windows, and IBM i: Checking OS Dependencies

73606 Supported Languages and Code Pages Information on possible languages and language combinations in SAP systems

1972803 SAP on AIX: Recommendations This SAP Note contains recommendations and clarifications for many topics relevant for SAP on AIX.

1075118 SAP on HP-UX: FAQ This SAP Note contains information that is specific to the SAP system installation on HP-UX

171356 SAP software on Linux: Essential comments This SAP Note contains Linux-specific information about the SAP system installation

1067221 Composite Note for Heterogeneous Installation This SAP Note and its related SAP Notes describe the released operating system and database combinations for heterogeneous SAP systems landscapes.

1.4 Accessing the SAP LibraryThe references to SAP NetWeaver Library documentation in this installation guide always refer to the following on SAP Help Portal:Table 7Product and Release SAP Library Path

SAP systems based on SAP NetWeaver Composition Environment 7.1

help.sap.com/nwce71 Application Help SAP Library: English

SAP systems based on SAP NetWeaver Composition Environment 7.1 including Enhancement Package 1


SAP systems based on SAP NetWeaver Composition Environment 7.2


SAP systems based on SAP NetWeaver 7.3 help.sap.com/nw73 Application Help Function-Oriented View: English

SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1

help.sap.com/nw731 Application Help Function-Oriented View: English

SAP systems based on SAP NetWeaver 7.4 help.sap.com/nw74 Application Help Function-Oriented View: English

12



2 Installation Options Covered by this Guide

This section shows the installation options covered by this installation guide. You have to decide what exactly you want to install because the steps you have to perform vary according to the installation option you choose. Standard system [page 13] (formerly known as central system) Distributed system [page 14] High-availability system [page 14] You can install one or more additional application server instances [page 15] to an existing standard,

distributed, or high-availability system. You can install an SAP Host Agent separately [page 18].

After you decide on the installation option that you want to use, continue with Planning [page 19].

2.1 Standard SystemYou can install a standard system on a single host.In a standard system, all main instances run on a single host.There are the following instances: Central services instance for Java (SCS instance) Database instance (DB) Primary application server instance (PAS instance)

Figure 1: Standard Java System

SAP Systems Based on the Application Server Java of SAP NetWeaver on UNIX: OracleInstallation Options Covered by this Guide



2.2 Distributed SystemAn SAP system consists of SAP instances. An SAP instance is a group of processes that are started and stopped at the same time.In a distributed system, every instance can run on a separate host: Central services instance for Java (SCS instance) Database instance (DB)

The Java stack uses its own database schema in the database. Primary application server instance (PAS)

The graphics below assume that you use the global directories of the SCS instance as global file system. That means that the host with the SCS instance is the SAP global host. However, you can also separately install the global directories on any host of your SAP system landscape.You can also use the SAP transport host or the host with the global file system (SAP global host) as your primary application server instance host.Optionally you can install one or more additional application server instances. For more information, see Installation of an Additional Application Server Instance [page 15].

Figure 2: Distributed Java System

2.3 High-Availability SystemAn SAP system consists of SAP instances. An SAP instance is a group of processes that are started and stopped at the same time.In a high-availability system, every instance can run on a separate host.

14



There are the following instances: Central services instance for Java (SCS instance) Enqueue replication server instance (ERS) for the SCS instance (mandatory)

The enqueue replication server instance contains the replication table, which is a copy of the lock table in the SCS instance.

Database instance (DB) Primary application server instance (PAS)

The graphics below assume that you run the SCS instance on the switchover cluster infrastructure. However, you can also run other SAP system instances that are a single point of failure (SPOF) on a switchover cluster infrastructure, for example the database instance.You can also use the SAP transport host or the host with the global file system (SAP global host) as your primary application server instance host.We recommend that you run the SCS instance in a switchover cluster infrastructure. The SCS instance must have its own ERS instance.To increase high availability by creating redundancy, we recommend that you install additional application server instances on hosts different from the primary application server instance host. For more information, see Installation of an Additional Application Server Instance [page 15].The following figures show examples for the distribution of the SAP instances in a high-availability system.

Figure 3: High-Availability System

2.4 Additional Application Server InstanceYou can install one or more additional application server instances for an existing SAP system. Additional application server instances are optional and can be installed on separate hosts.




An additional application server instance can run on: The host of any instance of the existing SAP system (exceptions see below) On a dedicated host

NoteIf you want to install additional application server instances running on an operating system other than the primary application server instance, see Heterogeneous SAP System Installation [page 121]. For example, you need to do this if your primary application server instance runs on Linux for System z but the additional application server instance is to run on Windows.

Additional Application Server Instance for a Standard SystemFor example, the following figure shows a standard system with additional application server instances that run: On the main host of the SAP system, that is, on the host on which the primary application server instance and

the database instance run On dedicated hosts

Figure 4: Additional Application Server Instance for a Standard System

For more information, see Standard System [page 13].

Additional Application Server Instance for a Distributed SystemThe following figure shows a distributed system with additional application server instances that run: On the main host of the SAP system, that is, on the host on which the primary application server instance runs On dedicated hosts

We do not recommend installing additional application server instances on the SAP global host.

16



Figure 5: Additional Application Server Instance for a Distributed System

For more information, see Distributed System [page 14].

Additional Application Server Instance for a High-Availability SystemThe following figure shows a high-availability system with additional application server instances that run: On the host of the primary application server instance On dedicated hosts

We do not recommend installing additional application server instances on the switchover cluster infrastructure.




Figure 6: Additional Application Server Instance for a High-Availability System

For more information, see High-Availability System [page 14].

2.5 SAP Host Agent as a Separate InstallationUsing the SAP Host Agent, you can centrally monitor any host with the Alert Monitor or the SAP NetWeaver Administrator or the Landscape Virtualization Manager. In addition, the SAP Host Agent is used by the Landscape Virtualization Manager for starting, stopping, and relocating SAP instances and databases.The SAP Host Agent is automatically installed during the installation of all new SAP system instances. You only need to install an SAP Host Agent separately in the following cases: There is no SAP system or instance on the host. The SAP system or instance running on the host has a kernel release lower than SAP kernel 7.20 and the host

does not yet have an SAP Host Agent. You have upgraded your SAP system to a release with a kernel release lower than SAP kernel 7.20 and the host

of the upgraded system or instance does not yet have an SAP Host Agent.The section Installing the SAP Host Agent Separately [page 121] describes how to perform the installation.

18



3 Planning

3.1 Planning ChecklistThis section includes the planning steps that you have to complete for the following installation options: Standard, distributed, or high-availability system Additional application server instance

Detailed information about the steps is available in the relevant chapter.

Prerequisites1. You have planned your SAP system landscape according to the Master Guide available at the appropriate

download location under service.sap.com/instguides.For more information, see Before You Start [page 8].

2. You have decided on your installation option (see Installation Options Covered by this Guide [page 13]).

Standard, Distributed, or High-Availability System

NoteIn a standard system, all mandatory instances are installed on one host. Therefore, if you are installing a standard system, you can ignore references to other hosts.

1. You check the hardware and software requirements [page 20] on every installation host.2. You identify basic SAP system installation parameters [page 28].3. For the database installation, we recommend that you check the information available in the SAP on Oracle

Knowledge Center at www.sdn.sap.com/irj/sdn/ora.4. You decide on the transport host to use [page 40].5. You decide whether you want to integrate LDAP Directory Services in your SAP system [page 108].6. If you want to install the Diagnostics Agent together with your SAP system, read the Diagnostics Agent specific

planning steps [page 40].7. To install a high-availability system, you read Planning the Switchover Cluster for High

Availability [page 42].8. Optionally, you decide whether you want to install multiple components in one database (MCOD) [page 115].9. Continue with Preparation [page 46].

Additional Application Server Instance1. You check the hardware and software requirements [page 20] for every installation host on which you want

to install one or more additional application server instances.2. You identify basic SAP system installation parameters [page 28].3. Continue with Preparation [page 46].

SAP Systems Based on the Application Server Java of SAP NetWeaver on UNIX: OraclePlanning



3.2 Hardware and Software RequirementsEnsure that your hosts meet the hardware and software requirements for your operating system and the SAP instances. Otherwise you might experience problems when working with the SAP system.

Prerequisites Make sure that the host name meets the requirements listed in SAP Note 611361. Contact your OS vendor for the latest OS patches. Check your keyboard definitions. If you want to install a printer on a host other than the primary application server instance host (for example,

on a separate database instance host), check whether the printer can be accessed under UNIX.

Process Flow1. Check the Product Availability Matrix at service.sap.com/pam for supported operating system releases.2. Check the hardware and software requirements using:

The Prerequisite Checker: Standalone (optional) before the installation process

For more information, see Running the Prerequisites Check Standalone [page 20]. Integrated in the installation tool (mandatory) as part of the installation process

For more information, see Running the Installer [page 74].

NoteFor the most recent updates to the Prerequisite Checker, always check SAP Note 855498.

The hardware and software requirements tables in Requirements for the SAP System Hosts [page 21].3. If you want to install a production system, the values provided by the Prerequisite Checker and the hardware

and software requirements checklists are not sufficient. In addition, do the following: You use the Quick Sizer tool available at service.sap.com/sizing. You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing

depending on: The set of applications to be deployed How intensively the applications are to be used The number of users

3.2.1 Running the Prerequisites Check in Standalone Mode (Optional)

When you install an SAP system, the installer automatically starts the prerequisites check and checks the hardware and software requirements in the background. As an optional step during planning, you can also run the prerequisites check in standalone mode to check the hardware and software requirements for your operating system and the SAP instances before the actual installation.

20



RecommendationWe recommend that you use both the prerequisites check and the requirements tables for reference.

Procedure1. Copy the installer to the host where you want to run the prerequisites check as follows:

1. Download the latest version of the software provisioning manager 1.0 archive SWPM10SP_.SAR from

service.sap.com/swdc Support Packages and Patches A - Z Index S SL Toolset SL Toolset Entry by Component Software Provisioning Manager Software Provisioning Mgr 1.0

2. Unpack the software provisioning manager 1.0 archive to a local directory using the following command:SAPCAR -xvf /.SAR -R

2. Start the installer as described in Running the Installer [page 74].3. On the Welcome screen, choose Preparations Prerequisites Check .4. Follow the instructions in the installer dialogs and enter the required parameters.

NoteFor more information about each parameter, position the cursor on the parameter field and choose F1 in the installer.

After you have finished, the Parameter Summary screen appears. This screen summarizes all parameters that you have entered and that you want to have checked. If you want to make a change, select the relevant parameters and choose Revise.

5. To start the prerequisites check, choose Next.

ResultThe Prerequisite Checker Results screen displays the results found. If required, you can also check the results in file prerequisite_checker_results.html, which you can find in the installation directory.

3.2.2 Requirements for the SAP System HostsEvery installation host must meet at least the requirements listed in the following tables. Most of the requirements are valid for every installation host whereas some requirements are instance-specific and are marked accordingly.

NoteThe information here is not intended to replace the operating system documentation. For more information, see your operating system documentation.




Table 8: General Installation Information for Your Operating SystemOperating System Information

AIX See SAP Note 1972803 and SAP on AIX at scn.sap.com/community/aix

HP-UX See SAP Note 1075118 and SAP on HP-UX Best Practices at scn.sap.com/community/hp-ux

Linux See SAP Note 171356 and SAP on Linux at scn.sap.com/community/linux

Solaris See SAP on Oracle Solaris at scn.sap.com/community/oracle-solaris

Table 9: SAP System Hardware RequirementsRequirement Values and Activities

Distribution of the Oracle database

We recommend using a redundant storage solution such as RAID5 for data security reasons.To calculate how much storage is required for your Oracle database, see section Database System Configuration in the SAP Library [page 12] at: SAP Composition Environment 7.1 / 7.1 including Enhancement Package 1 / 7.2:

Administrators Guide Administration of SAP NetWeaver CE General System Administration Administration of Databases Database Administration for Oracle SAP Database Guide: Oracle Getting Started with Oracle and the SAP System

SAP NetWeaver 7.3 and higher:SAP NetWeaver Library: Function-Oriented View Database Administration Database

Administration for Oracle SAP Database Guide: Oracle Getting Started with Oracle and the SAP System

Hardware Your operating system platform must be 64-bit.

Processing units For application server instances and database instances: The number of physical or virtual processing units usable by the operating system image must be equal to or greater than 2.For an SCS instance running on a separate host: One physical or virtual processing unit usable by the operating system image might be sufficient.Examples of processing units are processor cores or hardware threads (multithreading).In a virtualized environment, ensure that adequate processor resources are available to support the workloads of the running SAP systems.

Optical media drive ISO 9660 compatible

Hard disk space General Requirements: 4.3 GB of temporary disk space for every required installation medium that you have

to copy to a local hard disk. For more information, see Preparing the Installation Media [page 63].

1.2 GB of temporary disk space for the installation. 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.

Instance-Specific Requirements:If you install several instances on one host, you have to add up the requirements accordingly.

22



Requirement Values and ActivitiesFor more information about space requirements for the file systems and directories of the instances, see SAP Directories [page 50] and the appropriate database-specific information listed below. Central services instance (SCS):

Minimum 3.5 GB Enqueue replication server instance for the SCS (if required):

Minimum 3.5 GB Database Instance:

SAP NetWeaver: Minimum 10 GB SAP ERP: Minimum 60 GB SAP CRM: Minimum 40 GB SAP SRM: Minimum 40 GB SAP SCM: Minimum 40 GBFor more information about space requirements for the separate file systems and directories, see Oracle Directories [page 56].

Primary application server instance:Minimum 6 GB

Additional application server instance:Minimum 6 GB

SAP Host Agent:Minimum 0.5 GB

RAM Only valid for: AIX |

NoteKeep in mind that the operating system itself requires about 10% of the available RAM.

End of: AIX |The following lists the RAM requirements for each SAP instance.If you install several instances on one host, you have to add up the requirements accordingly. Central services instance for Java (SCS)

Minimum 1 GB Enqueue replication server instance for the SCS (if required)

Minimum 1 GB Database Instance:

Minimum 1.5 GB

NoteThe default value used by the installer is 50 percent of the entire RAM.

Primary application server instance:Minimum 8 GB




Requirement Values and Activities For more information about RAM required for usage type BI Java, see SAP Note

1736008. For more information about RAM required for usage type Development Infrastructure

(DI), see SAP Note 737368. Additional application server instance:

Minimum 8 GB SAP Host Agent:

Minimum 0.5 GBOnly valid for: HP-UX |Refer to SAP Note 1112627 for the commands to display the RAM size on HP-UX.End of: HP-UX |Only valid for: Linux |Refer to SAP Note 1382721 for the commands to display the RAM size on Linux.End of: Linux |

AIX: Paging space You need hard disk drives with sufficient paging space. You can calculate the required paging space as follows: Optimistic strategy:

In addition, you need at least 20 GB for the primary application server instance and at least another 10 GB for the SCS instance and also for every additional application server instance.

Defensive strategy:3 * RAM, at least 20 GB

In addition, for the database instance you need: 0.75 * RAM, if RAM is greater than 8 GB 1 * RAM, if RAM is less than 8 GB

For the latest information about recommended paging space, see SAP Note 1121904.

HP-UX: Swap space You need hard disk drives with sufficient space for swap. You can calculate the required swap space as follows:2 * RAM, at least 20 GBFor more information about HP-UX swap space recommendations and about how to set up swap space, see SAP Note 1112627.

Linux: Swap space You need hard disk drives with sufficient space for swap. We recommend that you use the amount of swap space as described in SAP Note 1597355. You might decide to use more or less swap space based on your individual system configuration and your own experience during daily usage of the SAP system.

Solaris: Swap space You need hard disk drives with sufficient space for swap. You can calculate the required swap space as follows:At least 20 GB are required. For more information, see SAP Note 570375.

Verifying paging space size and kernel settings using memlimits

To verify paging space size and kernel settings, you can execute memlimits as follows:1. Make sure that the SAPCAR program is available on the installation host. If SAPCAR is not

available, you can download it from service.sap.com/swdc.

24



Requirement Values and Activities2. Make the SAPEXE.SAR archive available on the installation host. This archive is contained

in the folder K___/DBINDEP of the installation media.

3. To unpack the file memlimits, enter the following command:SAPCAR -xvfg SAPEXE.SAR memlimits

4. Start memlimits using the following command:./memlimits -l 20000In case of error messages, increase the paging space and rerun memlimits until there are no more errors.

Table 10: Diagnostics Agent Hardware RequirementsCategory Requirement

Minimum disk space Depending on your platform: Up to 6 GB for installation media (packed and unpacked versions of SWPM SAR-file and

kernel ZIP-file) Up to 1.5 GB for the installed Diagnostics Agent Up to 1 GB of free space in the installation directory

Minimum RAM 256 MB

Table 11: Software RequirementsRequirement Values and Activities

Database software Check the Product Availability Matrix (PAM) at service.sap.com/pam for supported database platforms.

AIX: Operating system version Your operating system platform must be 64-bit.Check the Product Availability Matrix (PAM) at service.sap.com/pam for supported operating system versions.Contact your OS vendor for the latest OS patches.Minimal OS requirements for the specific SAP Kernel releases are listed in SAP Note 1780629.

HP-UX: Operating system version Your operating system platform must be 64-bit.Check the Product Availability Matrix (PAM) at service.sap.com/pam for supported operating system versions.To check the operating system version on your installation hosts, use the following command:uname -rSee SAP Note 939891 for information about support time frames of HP-UX.

Linux: Operating system version Your operating system platform must be 64-bit.Check the Product Availability Matrix (PAM) at service.sap.com/pam for supported operating system versions.Contact your OS vendor for the latest OS patches.




Requirement Values and ActivitiesTo check the operating system version on your installation hosts, use the following command:cat /etc/*-release

Solaris: Operating system version Your operating system platform must be 64-bit.Check the Product Availability Matrix (PAM) at service.sap.com/pam for supported operating system versions.To check the operating system version on your installation hosts, use the following command:/bin/uname -r

AIX: Kernel parameters To adjust AIX Virtual Memory Management settings, see SAP Note 973227.

HP-UX: Kernel parameters To run an SAP system, make sure that you check and, if necessary, modify the HP-UX kernel.

CautionWe recommend that a UNIX system administrator performs all kernel modifications.

Proceed as follows:1. Check SAP Note 172747 for recommendations on current HP-UX kernel

parameters.

CautionIf a kernel value is already larger than the one suggested in the SAP Note, do not automatically reduce it to match the SAP requirement.You have to analyze the exact meaning of such a parameter and, if required, to reduce the parameter value. In some cases this might improve the performance of your SAP applications.

2. If necessary, modify the kernel parameters in one of the following ways: Manually, as described in SAP Note 172747. Interactively, using the HP-UX System Administrator Manager (SAM) or

System Management Homepage (SMH).

Linux: Kernel parameters Check SAP Note 171356 for Linux kernel versions certified by SAP.To check the Linux kernel parameters for your Linux distribution, see one of the following SAP Notes: Oracle Linux 6: SAP Note 1565179 RHEL6: SAP Note 1496410 SLES 11 SP1: SAP Note 1310037

Solaris: Kernel parameters To run an SAP system, you must check and, if necessary, modify the Solaris kernel parameters or resource controls. Solaris 9: SAP Note 395438 Solaris 10: SAP Note 724713 Solaris 11: SAP Note 1669684

26



Requirement Values and Activities

HP-UX: OS patches To check the minimum required OS patches, see SAP Note 837670.

Solaris: OS patches Check the relevant SAP Note for required Solaris patches: Sun Solaris 9 on SPARC: SAP Note 550585 Sun Solaris 10 on SPARC: SAP Note 832871 Solaris 10 on x64: SAP Note 908334 Solaris 11: SAP Note 1669684

AIX: National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding locales are installed.

HP-UX: National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding locales are installed.You can check this as follows: Enter the following commands to check whether National Language Support

(NLS) is installed:swlist -v | grep -i nlsThe output should contain the string NLS-AUX ...

Enter the following commands to check which locales are available:locale -aThe following files must be available: de_DE.iso88591, en_US.iso88591.

Linux: National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding locales are installed.You can check this as follows: Ensure that the required locales such as the following are available:

de_DE, en_US Check SAP Note 187864 for information about corrected operating system

locales and SAP blended Code Pages.

Solaris: National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding locales are installed.You can check this by making sure that the following files are available: iso_8859_1, en_US.

Linux: System language For the installation, you must choose English as the operating system language on all Linux hosts that run SAP software.

HP-UX: Language libraries To make sure that the file set LANG-MIN is installed, enter the following command:swlist -v | grep -i lang-minIf nothing is displayed, the file set is not available, and needs to be installed.

Table 12: Other RequirementsRequirement Values and Activities

AIX: Additional software Make sure that the following additional file sets are installed:




Requirement Values and Activities bos.adt Base Application Development bos.perf performance and diagnostics tools perfagent.tools performance monitoring tools bos.perf.libperfstat Performance Statistics Library

Host name To find out physical host names, open a command prompt and enter hostname.For more information about the allowed host name length and characters allowed for SAP system instance hosts, see SAP Note 611361.Only valid for: HP-UX |For HP-UX, see SAP Note 1503149 in addition.End of: HP-UX |If you want to use virtual host names, see SAP Note 962955.

Login shell The installer only prompts you for this parameter if you use a login shell other than the recommended C shell (csh).For more information, see SAP Note 202227.Only valid for: HP-UX |For HP-UX, see SAP Note 1038842 in addition.End of: HP-UX |

Shared file systems for decentralized systems

If application servers are installed decentralized, a shared file system must be installed, for example Network File System (NFS).

AIX: C++ Runtime environment Minimal C++ runtime requirements for the specific SAP Kernel releases are listed in SAP Note 1780629.

Linux: C compiler Make sure that the C compiler gcc is installed.

3.3 Basic SAP System Installation ParametersThe installer prompts for input parameters during the Define Parameters phase of the installation.You can install your SAP system either in Typical or Custom mode: Typical

If you choose Typical, the installation is performed with default settings. This means that the installer prompts you only for a small selection of installation parameters. These parameters include at least the following: SAP system ID and database connectivity parameters Master password JCE Unlimited Strength Jurisdiction Policy files archive (only prompted if you install usage type Adobe

Document Services) SAP system profile directory only for systems with instances on separate hosts UME ConfigurationFor more information about the installation parameters, see the corresponding tables below in this document. If you want to change any of the default settings, you can do so on the Parameter Summary screen.

28



CustomIf 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.

NoteYou cannot change from Custom to Typical mode or from Typical to Custom mode on the Parameter Summary screen.

The following tables list the basic SAP system installation parameters that you need to specify before installing your SAP system: SAP system parameters SAP system database parameters Diagnostics Agent parameters

For all other installation parameters, use the F1 help on the installer screens.

SAP System ParametersTable 13Parameters Description

Unicode System A Java standalone system is always a Unicode system.

SAP System ID The SAP system ID identifies the entire SAP system.The installer prompts you for the when you execute the first installation option to install a new SAP system.If there are further installation options to be executed, the installer prompts you for the profile directory. For more information, see the description of the parameter SAP System Profile Directory.

ExampleThis prompt appears when you install the central services instance, which is the first instance to be installed in a distributed system.

CautionChoose your SAP system ID carefully. Renaming is difficult and might require a system reinstallation.

Make sure that your SAP system ID: Is unique throughout your organization. Do not use an existing when installing

a new SAP system. Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the reserved IDs listed in SAP Note 1979280. If you want to install an additional application server instance, make sure that no gateway

instance with the same SAP System ID (SAPSID) exists in your SAP system landscape.




Parameters Description

Instance Number of the SAP System

Technical identifier for internal processes. It consists 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.If you do not enter a specific value, the instance number is set automatically to the next free and valid instance number that has not yet been assigned to the SAP system to be installed or to SAP systems that already exist on the installation host.To find out the instance numbers of SAP systems that already exist on the installation host, look for subdirectories ending with of local (not mounted) /usr/sap/ directories.For more information about the naming of SAP system instances, see SAP Directories [page 50].Only valid for: HP-UX |

CautionDo not use 75 for the instance number because this number is already used by the operating system. For more information, see SAP Note 29972.

End of: HP-UX |

///profile or /usr/sap//SYS/profile

The installer retrieves parameters from the SAP system profile directory of an existing SAP system.SAP profiles are operating system files that contain instance configuration information.The installer prompts you to enter the location of the profile directory when the installation option that you execute is not the first one belonging to your SAP system installation, for example if you are installing a distributed system or an additional application server instance to an existing SAP system. See also the description of the parameters SAP System ID and Database ID./usr/sap//SYS/profile is the soft link referring to ///profile.

Master Password Common password for all users that are created during the installation: Operating system users (for example adm)

NoteThe Master Password is not used as password for the Database Users such as Database Administrator User or DB Connect User.

CautionIf you did not create the operating system users manually before the installation, the installer 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.

Java users(for example Administrator)

Secure Store key phrase

30



Parameters DescriptionFor more information, see table Key Phrase for Secure Store Settings.

Password policyThe master password must meet the following requirements: It must be 8 to 14 characters long It must contain at least one digit (0-9) It must not contain \ (backslash) and " (double quote) It must contain at least one letter (a-z, A-Z) It must not begin with a digit nor an underscore It can contain the following characters: _, #, $, a-z, A-Z, 0-9 Depending on the installation option, additional restrictions may apply (for example, the

master password must not contain the name of a Java user created during the installation).

Message Server Port CautionThe 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.The SCS instance profile contains the configuration for the Java message server.The Java message server port uses the parameter rdisp/msserv_internal with default value 39.For more information about the parameters used for message server ports, see SAP Note 821875.

Java(TM) Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files Archive

If you want to install usage type Adobe Document Services, make sure that you download the unlimited version of the JCE Jurisdiction Policy Files 6 archive. For more information about where to download it, see SAP Note 1240081.

Operating System Users and Groups

The installer processes the operating system users as follows: If the operating system users do not exist, the installer creates the following users:

The SAP system administrator user adm Database administrator usersThe installer sets the master password for these users by default. You can overwrite and change the passwords either by using the parameter mode Custom or by changing them on the parameter summary screen.

If the operating system users already exist, the installer prompts you for the existing password, except if the password of these users is the same as the master password.

Make sure that the user ID and group ID of these operating system users are unique and the same on each relevant application server instance host.

For more information, see Creating Operating System Users and Groups [page 47].

UME Configuration The installer prompts you for how to configure the UME during the input phase of the installation.You can choose between the following options:




Parameters Description Use Java Database

If you choose this option, administrators can manage users and groups with the UME Web admin tool and SAP NetWeaver Administrator only.For LDAP, use this configuration for the installation and change the configuration to LDAP after the installation.

Use ABAPIf you choose this option, administrators can manage users with the transaction SU01 on the external ABAP system, and, depending on the permissions of the communication user, also with the UME Web admin tool and SAP NetWeaver Administrator.You must have created the required users manually on the external ABAP system.For more information, see Preparing User Management for an External ABAP System (Optional) [page 61].

For more information about supported UME data sources and change options, see SAP Note 718383.

Note If you want to use LDAP as data source, choose Use Java Database and change to LDAP

after the installation has finished. If you want to use the User Management Engine for an existing ABAP system, choose

Use ABAP. If you install a PI system, you have the following options:

If you want to install non-central Advanced Adapter Engine (AAE) as optional standalone unit for a PI dual-stack installation, you have the following options: Use External ABAP System: This sets up the ABAP-based User Management

Engine on the Integration Server system. Use Java Database: This sets up local user management on the system of the

non-central AAE. If you want to install non-central Advanced Adapter Engine (AAE) as optional

standalone unit for an Advanced Adapter Engine Extended (AEX) installation or a Process Integration and Orchestration Package (PI-CP) installation, you have to choose Use Java Database. This sets up local user management on the system of the non-central AAE.

Using the Java Database:

Administrator User The installer 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.

Guest User The installer sets the user name Guest and the master password by default.The guest user is a user for anonymous access.

Using an External ABAP System Parameters for the ABAP Connection:

Application Server Instance Number

This is the instance number on the application server of the central ABAP system to which you want to connect the Application Server Java.

32



Parameters DescriptionTo find out the number on the host of the primary application server instance, look under the SAP directory usr/sap//DVEBMGS.

Application Server Host 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.

Communication User 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 This is the name and password of the administrator user that you created on the external ABAP system.

Administrator Role The role SAP_J2EE_ADMIN must exist on the external ABAP system.

Guest User This is the name and password of the guest user that you created on the external ABAP system.The guest user is a user for anonymous access.

Guest Role The role SAP_J2EE_GUEST must exist on the external ABAP system.

Key Phrase for Secure Store Settings

This is a random word or phrase that is used to encrypt the secure store.The Java EE engine uses this phrase to generate the key that is used to encrypt the data.The uniqueness of the phrase you use contributes to the uniqueness of the resulting key.

RecommendationUse a long key phrase that cannot be guessed easily. Use both uppercase and lowercase letters in the phrase and include special characters.

NoteIf you choose Typical mode, the installer sets the master password for the key phrase. In this case, make sure that you replace the master password with the required unique key phrase either on the Parameter Summary screen or after the installation has finished.

Path to SAPCRYPTO.SAR The SAP Cryptographic Library is required to enable Secure Sockets Layer (SSL) encryption of HTTP connections. In most cases it is installed automatically from the kernel medium. In case it is not installed automatically and you are prompted for it during the installation, you can download it as described in SAP Note 455033.This software product is subject to export control regulations in Germany as the country of origin and import regulations of your own country. SAP may not yet have a corresponding export license for your user or company. Contact the contract department in your local SAP company. To download the SAP Cryptographic Software from the SAP Service Marketplace, you need a customer user ID. Before any transfer of these software products to persons, companies or other organizations outside your company, in particular in the case of any re-export of the software products, authorization is required from the German export control authorities. This might also be required from your responsible national export control authorities. This also applies to transfers to affiliated companies. Corresponding laws and regulations in the recipient country may also exist which restrict the import or the use of these software products.




Parameters Description

DNS Domain Name for SAP System

If you want to use HTTP-based URL frameworks such as Web Dynpro applications, you have to specify the DNS domain name for the SAP system.The DNS Domain Name is used to calculate the Fully Qualified Domain Name (FQDN), which is configured in profile parameter SAPLOCALHOSTFULL. FQDN is the fully qualified domain name for an IP address. It consists of the host name and the domain name:.The DNS Domain Name is needed to define the URLs for the ABAP and Java application servers. It is appended to the server name to calculate the FQDN.For more information, see SAP Note 654982.

ExampleIf your application server host is called kirk.wdf.sap.com, the DNS Domain Name is wdf.sap.com.

SLD Destination for the System

The System Landscape Directory (SLD) registers the systems and the installed software of your entire system landscape.You can choose between the following options: Register in existing SLD

Choose this option to register the SAP system you are installing in an existing SAP System Landscape Directory (SLD) by specifying the SLD connection parameters listed below in this table.

No SLD destinationChoose this option if you do not want to register the SAP system you are installing in an existing SAP System Landscape Directory (SLD).You then have to configure the SLD destination manually after the installation has finished.

SLD Host The host name of the existing SLD.

SLD HTTP(S) Port The HTTP or HTTPS port of the existing SLD. The following naming convention applies: 500.

ExampleIf the instance number of your Java system is 01, the SLD HTTPS Port is 50100.

SLD Data Supplier User and password

The existing SLD Data Supplier user and password of the existing SLD

Diagnostics Agent ParametersYou can optionally install the Diagnostics Agent with the SAP system.Table 14: Diagnostics Agent System ID and Instance NumberParameters Description

Diagnostics Agent System ID (DASID)

By default the installer sets the Diagnostics Agent System ID (DASID) to DAA.

34



Parameters DescriptionIf a Diagnostics Agent with the same kernel version as the one you are currently installing is already present on the local installation host, the installer sets to the system ID of this already installed agent.If the kernel version you have selected for your installation is different from the kernel versions of already installed Diagnostics Agents, the installer assigns another default system ID, starting from DA1 to DA9.You can overwrite the proposed system ID as required.Diagnostics Agents installed on different logical hosts (but on the same physical or virtual host) can use the same .

CautionChoose the carefully. Renaming is difficult and requires you to reinstall the Diagnostics Agent.

Make sure that the : Either does not yet exist on the local installation host, or does already exist but was only

used for a Diagnostics Agent installation in the exact same version Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Is allowed according to SAP Note 1979280

Instance Number of the Diagnostics Agent

Technical identifier for internal processes for the Diagnostics Agent. It consists of a two-digit number from 98 to 00. Default is 98.If instance number 98 is already used, the Diagnostics Agent instance number is automatically set to the next free, lower, valid instance number.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.The instance number is used to specify the name of the Diagnostics Agent instance directory that the installer automatically creates during the installation. The directory of the Diagnostics Agent instance is called SMDA.For more information, see SAP Directories [page 50].To find out the instance numbers of SAP systems that already exist on the installation host, look for subdirectories ending with of local (not mounted) /usr/sap/ directories.The value is the number assigned to the instance.Only valid for: AIX |

CautionIf you are using NIM Service Handler (NIMSH), do not use 01 or 02 for the instance number. The installer uses the instance number for the internal message server port 39. The NIM client daemon uses reserved ports 3901 and 3902.

End of: AIX |




Parameters DescriptionOnly valid for: HP-UX |

CautionDo not use: 75 for the instance number because this number is already used by the operating system.

For more information, see SAP Note 29972. 02 as the instance number because this number is used to determine the port number

for report RSLGCOLL, which is 14 by default. However, port 1402 is already used by the OS process rstlisten. If you still decide to use 02 as the instance number, the instance fails to start during the installation process. You then have to manually change the port number for report RSLGCOLL to continue with the installation. For more information, see Running the Installer [page 74].

End of: HP-UX |

Table 15: Operating System UsersParameters Description

SAP System Administrator:adm

Administrator for the Diagnostics Agent.This user is dedicated to the Diagnostics Agent installation and has the authorization to manage the Diagnostics Agent.If you did not create user adm manually before the installation, the installer creates it automatically on every application server instance host during the installation. Make sure that the user ID and group ID of adm are unique and the same on each application server instance host.

SAP System Administrator:sapadm

SAP Host Agent administrator is the user for central monitoring services.This user is created only if the SAP Host Agent is automatically installed during the installation of the Diagnostics Agent.

Table 16: Diagnostics Agent SLD ParametersParameters Description

SLD Destination for the Diagnostics Agent You can choose between the following options: Register in existing central SLD

Choose this option to register the Diagnostics Agent you are installing in an SLD by specifying the SLD connection parameters listed below.

CautionYou cannot specify an SAP router route string for the SAP Solution Manager connection if you register the Diagnostics Agent into an SLD.

No SLD destinationIf you select this option, the installer does not prompt you for further SLD connection parameters.You may configure the SLD destination for the Diagnostics Agent via the smdsetup script after the installation has finished.For more information, see SAP Note 1833501.

36



Parameters DescriptionYou can select the check box Use HTTPS if you choose Register in existing central SLD.

SLD HTTP Host (SLD Host if Use HTTPS was selected)

The fully qualified host name of the SAP NetWeaver Java system with the SLD, e.g. sldhost.domain.corp.

RecommendationThe host name will be checked. It is recommended to input the fully qualified host name.

SLD HTTP Port (SLD HTTPS Port if Use HTTPS was selected)

The HTTP or HTTPS port of the SAP NetWeaver Java system with the SLD.For HTTP the following naming convention applies:500.For HTTPS the following naming convention applies:501.

ExampleIf the instance number of your SAP NetWeaver Java system is 01, the SLD HTTP Port is 50100 and the SLD HTTPS Port is 50101.

SLD Data Supplier User The SLD Data Supplier user (e.g. SLDDSUSER) for the specified SLD.

Password of SLD Data Supplier User The password of the specified SLD Data Supplier user.

Table 17: SAP Solution Manager Connectivity ParametersParameters Description

Connection of the Diagnostics Agent to SAP Solution Manager

You can choose between the following connection options: Configure standard connection: the Diagnostics Agent is connected to the SAP Solution

Manager system.The installer only prompts you for the connection type listed below in this table if you select this option.

Do not configure connection: the Diagnostics Agent is not connected to the SAP Solution Manager system.If you select this option, the installer does not prompt you for further SAP Solution Manager connection parameters.You may configure the SAP Solution Manager connection for the Diagnostics Agent via the smdsetup script after the installation has finished.For more information, see SAP Note 1833501 .

You can select the check box Use SSL connectivity if you choose Configure standard connection.

Connection Type for the Diagnostics Agent Caution

For productive usage the Diagnostics Agent must be connected to the SCS message server of the SAP Solution Manager system. The connection via a Java EE dispatcher node should only be used for testing and debugging purposes.

You can choose between the following options: P4 connection via SCS message server




Parameters Description Direct P4 connection via Java EE dispatcher node

If you select the check box Use SSL connectivity you can choose between the following options: P4 SSL connection via SCS message server Direct P4 SSL connection via Java EE dispatcher node

Host (FQN) The fully qualified host name of the SAP Solution Manager system, e.g. host.domain.corp

RecommendationThe host name will be checked. It is recommended to input the fully qualified host name.

Port Depending on the Connection Type, you have to specify one of the following ports of the Java Stack of your SAP Solution Manager system: HTTP SCS Message Server Port is 81, where is the instance number of the SAP

Solution Manager Java Central Services (SCS). HTTP SCS SSL Message Server Port is 443 or 444, where is the instance

number of the SAP Solution Manager Java Central Services (SCS). Dispatcher P4 Port is 504, where is the instance number of the SAP Solution

Manager Java central instance. Dispatcher P4 SSL Port is 506, where is the instance number of the SAP Solution

Manager Java central instance.

User (Administrator role) and Password

As of SAP Solution Manager 7.10 SP10 we recommend to use the SMD_AGT user of your SAP Solution Manager system. For earlier releases the SMD_ADMIN user is still recommended.

SAP Router (optional) Route and Password

The route string describes the stations of a connection required between the Diagnostics Agent and SAP Solution Manager.The route string contains a substring for each SAP router without the target server such as: /H/host/S/service/W/pass /H/ indicates the host name /S/ is used for specifying the service (port); it is an optional entry, the default value is 3299 /W/ indicates the password for the connection between the predecessor and successor on

the route and is also optional (default is "", no password)

ExampleThe route between the Diagnostics Agent and SAP Solution Manager can look like: /H/host.domain.corp/S/3299

CautionYou cannot specify a route string if you registered the Diagnostics Agent into SLD during the previous step.

38



SAP System Database ParametersTable 18Parameters Description

Database ID The identifies the database instance. The installer prompts you for the when you are installing the database instance.The can be the same as the .

CautionChoose your database ID carefully. Renaming is difficult and requires you to reinstall the SAP system.

If you want to install a new database:Make sure that your database ID: Is unique throughout your organization Consists of exactly three alphanumeric characters Contains only uppercase letters Has a letter for the first character Does not include any of the reserved IDs listed in SAP Note 1979280.

MCOD only: If you want to use an existing database system, enter exactly the database ID of the existing database to which you want to add the system.For more information, see Installation of Multiple Components in One Database [page 115].

Database schema, Password

The Java database schema is named SAPDB.Default name is SAPSR3DB.

RecommendationChoose a that is different from your .It might cause problems when you copy a system where is the same as , 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 , but where the database schema has the old . This is not a technical problem, but might confuse the system administrator.

Oracle Listener Name, Oracle Listener Port, Oracle Listener Domain

If you install the database instance on a host where no other Oracle database is installed, you normally do not have to change the default values for Listener Name and Listener Port.

If there is already an Oracle database installed on your installation host, you can either use one listener for both databases or you have to specify an unused Listener Name and an unused Listener Port for the new listener. For more information if you use one listener for both databases, see SAP Note 98252.

All additional application server instances of an SAP system must use the same Listener Port than the database instance.

The default domain in the network configuration files is WORLD.Tablespaces, Datafiles An Oracle database consists of one or more logical storage units called tablespaces, which

collectively store all of the database's data.




Parameters DescriptionEach tablespace in an Oracle database consists of one or more files called datafiles, which are physical structures that conform to the operating system in which Oracle is running.MaxDatafileSize is the initial size of the tablespace datafile and its mapping to the new tablespace layout while importing the external file DBSIZE.XML.The installer prompts you to enter MaxDatafileSize in MB: 0: Datafile size defined in

netwiewer for 7.4 unix

Documents

sap note

sap ag

sap installation document

sap installation tools

sap plans

sap components

names of installation

earlier sap system releases