installation guide sap netweaver abap+java (for process integration) on solaris oracle using...

Installation GuideSAP NetWeaver ABAP+Java (for Process Integration) on Solaris: OracleUsing Software Provisioning Manager 1.0

Valid for SAP Systems Based on: SAP NetWeaver Process Integration 7.1 SAP NetWeaver Process Integration 7.1 including Enhancement Package 1 SAP NetWeaver 7.3 SAP NetWeaver 7.3 including Enhancement Package 1 SAP NetWeaver 7.4 SAP NetWeaver 7.4 Support Release 1

Target Audience Technology consultants System administrators

CUSTOMERDocument version: 1.6 2014-03-17

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/142 CUSTOMER 2014-03-17

Typographic Conventions

Example Description Angle brackets indicate that you replace these words or characters with appropriate

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

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

Example Emphasized words or expressionsExample Words or characters that you enter in the system exactly as they appear in the

documentationhttp://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 Web123456 Hyperlink to an SAP Note, for example, SAP Note 123456Example Words or characters quoted from the screen. These include field labels, screen titles,

pushbutton labels, menu names, and menu options. Cross-references to other documentation or published works

Example 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 toolsEXAMPLE 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

2014-03-17 CUSTOMER 3/142

Document History

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

The following table provides an overview of the most important document changes.Version Date Description1.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/142 CUSTOMER 2014-03-17

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2 Installation Options Covered by this Guide . . . . . . . . . . . . . . . . . . . . . . . 152.1 Standard System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2 Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3 High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.4 Additional Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.5 Central Services Instance for ABAP Separate from Existing Primary

Application Server Instance of an Upgraded System . . . . . . . . . . . . . . . . . . . . 212.6 SAP Host Agent as a Separate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.2 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2.1 Running the Prerequisites Check in Standalone Mode (Optional) . . . . . . . . . . 253.2.2 Requirements for the SAP System Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.3 Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.4 SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.5 Diagnostics Agent Specific Planning Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.5.1 Connection Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.5.2 Direct SAP Solution Manager Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.5.3 System Landscape Directory Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.6 Planning the Switchover Cluster for High Availability . . . . . . . . . . . . . . . . . . . 41

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.2 Creating Operating System Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . 464.3 Required File Systems and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

2014-03-17 CUSTOMER 5/142

4.3.1 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.3.2 Oracle Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.3.3 Setting Up File Systems for a High-Availability System . . . . . . . . . . . . . . . . . . 574.4 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.5 Performing Switchover Preparations for High Availability . . . . . . . . . . . . . . . . 614.6 Installing the SAP Front-End Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.7 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675.2 Exporting and Mounting the Transport Directory . . . . . . . . . . . . . . . . . . . . . 735.3 Exporting and Mounting Global Directories . . . . . . . . . . . . . . . . . . . . . . . . . . 745.4 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.5 Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . 805.5.1 Useful Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815.5.2 Interrupted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.5.3 Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845.5.4 Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.5.5 Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 885.5.6 Entries in the Services File Created by the Installer . . . . . . . . . . . . . . . . . . . . . . 895.5.7 Troubleshooting with the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905.6 Oracle Database 11g Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905.6.1 Updating the SAP RUNINSTALLER Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . 915.6.2 Installing the Oracle Database Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915.6.3 Installing the Required SAP Bundle Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956.2 Performing Post-Installation Steps for the Operating System . . . . . . . . . . . . . . 966.3 Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966.4 Performing the Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976.5 Providing Access to the NetWeaver Administrator . . . . . . . . . . . . . . . . . . . . . . 986.6 Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996.7 High Availability: Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996.8 Configuring the Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . 1006.9 Applying the Latest Kernel and Support Package Stacks . . . . . . . . . . . . . . . . . 1006.10 PI: Configure the Process Integration System after Installation . . . . . . . . . . . 1016.11 Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

6/142 CUSTOMER 2014-03-17

6.12 Configuring the Transport Management System . . . . . . . . . . . . . . . . . . . . . . 1026.13 SAP Kernel 7.40 and Higher: IP Multicast Configuration . . . . . . . . . . . . . . . . 1026.14 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026.15 Performing Oracle-Specific Post-Installation Steps . . . . . . . . . . . . . . . . . . . . . 1056.16 Performing a Full Installation Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Chapter 7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097.1 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097.2 Installing a Database Instance on Oracle Automatic Storage Management or

Oracle Real Application Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137.3 Installation of Multiple Components in One Database . . . . . . . . . . . . . . . . . . 1137.4 Creating a User for LDAP Directory Access . . . . . . . . . . . . . . . . . . . . . . . . . . 1157.5 Heterogeneous SAP System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157.6 Splitting Off a Central Services Instance for ABAP from an Existing Primary

Application Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167.7 Installing the SAP Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187.8 Starting and Stopping SAP System Instances . . . . . . . . . . . . . . . . . . . . . . . . . 1217.8.1 Starting and Stopping SAP System Instances Using the SAP Management

Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217.8.2 Starting and Stopping SAP System Instances Using Commands . . . . . . . . . . . 1257.8.3 Starting and Stopping the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . 1297.9 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . 1297.10 Deleting the Oracle Database 11g Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

2014-03-17 CUSTOMER 7/142

This page is left blank for documents that are printed on both sides.

1 Introduction

This installation guide describes how to install an SAP NetWeaver Process Integration system using software provisioning manager 1.0 (installer for short). An SAP NetWeaver Process Integration system is an ABAP+Java (dual-stack) system comprising both an ABAP and a Java stack. This guide applies to the following releases:Product ReleaseSAP NetWeaver Process Integration

SAP NetWeaver Process Integration 7.1 SAP NetWeaver Process Integration 7.1 including enhancement package 1

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

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 10] before you continue with this installation guide.

Constraints Your operating system platform must be 64-bit. The installation of dual-stack SAP Business Suite and optional dual-stack application systems is

not supported. One exception to this rule is SAP NetWeaver Process Integration on a traditional database system, which still requires a dual-stack implementation.However, note that a single-stack SAP NetWeaver Process Integration Java (Advanced Adapter Engine Extended) offers almost all features of the classical dual-stack implementations. Therefore, you should investigate if a Java-only implementation of an SAP NetWeaver PI system is suitable for your use case. Due to the harmonized process orchestration stack (SAP NetWeaver PI and SAP NetWeaver BPM running on the same Java instance), many of the ccBPM features in an SAP NetWeaver PI system can be realized using SAP NetWeaver BPM capabilities instead.For more information about the discontinuation of optional dual-stack deployments, see the SAP Community Network at http://scn.sap.com/docs/DOC-33703.

1 Introduction

2014-03-17 CUSTOMER 9/142

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

Package 1 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver 7.4 / 7.4 SR1. ABAP+Java system refers to SAP NetWeaver PI 7.1 / 7.1 including Enhancement Package 1 / SAP NetWeaver 7.3 /

7.3 including Enhancement Package 1 / SAP NetWeaver 7.4 / 7.4 SR1 or SAP NetWeaver PI 7.1 / 7.1 including Enhancement Package 1 / SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver 7.4 / 7.4 SR1 (for Process Integration) system.

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 Master Guide for your 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 http://service.sap.com/instguides:Document Internet AddressMaster Guide - SAP NetWeaver PI 7.1 http://service.sap.com /instguidesnwpi71 Installation

PlanningMaster Guide SAP NetWeaver 7.3 http://service.sap.com /installNW73Master Guide SAP Enhancement Package 1 for SAP NetWeaver 7.3

http://service.sap.com /installNW73

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

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

1 Introduction1.1 Before You Start

10/142 CUSTOMER 2014-03-17

Area DescriptionSoftware 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 61] 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: 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 29].

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 http://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.The 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.

1 Introduction1.2 New Features

2014-03-17 CUSTOMER 11/142

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 http://service.sap.com/notes.SAP Notes for the InstallationSAP Note Number Title Description1680045 Release Note for Software Provisioning

Manager 1.0Software 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. Attached is the Diagnostics Agent Setup Guide.

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

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 Introduction1.3 SAP Notes for the Installation

12/142 CUSTOMER 2014-03-17

SAP Note Number Title Description789220 Support Package level for NetWeaver

Installations/UpgradesInformation about the ABAP Support Package levels and kernel patch levels contained in the current SAP NetWeaver release

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: SAP systems based on SAP NetWeaver Process Integration 7.1:

http://help.sap.com/nwpi71/ Application Help SAP Library: English SAP NetWeaver Process Integration Library

SAP systems based on SAP NetWeaver Process Integration 7.1 including Enhancement Package 1:http://help.sap.com/nwpi711/ Application Help SAP Library: English SAP NetWeaver Process

Integration Library SAP systems based on SAP NetWeaver 7.3:

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

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

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

1 Introduction1.4 Accessing the SAP Library

2014-03-17 CUSTOMER 13/142

This page is left blank for documents that are printed on both sides.

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 15] (formerly known as central system) Distributed system [page 16] High-availability system [page 17] You can install one or more additional application server instances [page 18] to an existing standard,

distributed, or high-availability system. You can split off a central services instance for ABAP from an existing primary application server instance of an upgraded

system [page 21]. You can install an SAP Host Agent separately [page 22].After you decide on the installation option that you want to use, continue with Planning [page 23].

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 ABAP (ASCS instance) Enqueue replication server instance (ERS instance) for the ASCS instance (optional) Central services instance for Java (SCS instance) Enqueue replication server instance (ERS instance) for the SCS instance (optional) Database instance (DB)

The ABAP stack and the Java stack use their own database schema in the same database. Primary application server instance (PAS instance)

2 Installation Options Covered by this Guide2.1 Standard System

2014-03-17 CUSTOMER 15/142

Figure 1: Standard ABAP+Java System

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, with the exception of the ASCS instance and the SCS instance. The ASCS instance and the SCS instance must run on the same host: Central services instance for ABAP (ASCS instance) Enqueue replication server instance (ERS instance) for the ASCS instance (optional) Central services instance for Java (SCS instance) Enqueue replication server instance (ERS instance) for the SCS instance (optional) Database instance (DB)

The ABAP stack and the Java stack use their own database schema in the same database. Primary application server instance (PAS)The graphics below assume that you use the global directories of the ASCS instance and SCS instance as global file system. That means that the host with the ASCS and SCS 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 18].

2 Installation Options Covered by this Guide2.2 Distributed System

16/142 CUSTOMER 2014-03-17

Figure 2: Distributed ABAP+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.There are the following instances: Central services instance for ABAP (ASCS instance) Enqueue replication server instance (ERS instance) for the ASCS instance (mandatory) 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)The ABAP stack and the Java stack use their own database schema in the same database.

Primary application server instance (PAS)The graphics below assume that you run the ASCS instance and SCS instance on a 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.

2 Installation Options Covered by this Guide2.3 High-Availability System

2014-03-17 CUSTOMER 17/142

We recommend that you run both the ASCS instance and the SCS instance in a switchover cluster infrastructure. Both the ASCS instance and the SCS instance must each have their 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 18].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 115]. 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.

2 Installation Options Covered by this Guide2.4 Additional Application Server Instance

18/142 CUSTOMER 2014-03-17

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 15].

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 hostsWe do not recommend you to install additional application server instances on the SAP global host.


2014-03-17 CUSTOMER 19/142

Figure 5: Additional Application Server Instance for a Distributed System

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

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 hostsWe do not recommend you to install additional application server instances on the switchover cluster infrastructure.


20/142 CUSTOMER 2014-03-17

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

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

2.5 Central Services Instance for ABAP Separate from Existing Primary Application Server Instance of an Upgraded System

A central services instance consists of the essential enqueue and message system services only. This has been standard for the Java stack and is now also standard for the ABAP stack.The benefit of having a separate ASCS instance is mainly in the area of high-availability. This approach concentrates the possible single points of failure of a system into a single instance and, therefore, restricts failure to a single instance.Every newly installed SAP system based on SAP NetWeaver 7.3 and higher is automatically installed with an ASCS instance, even if you install all SAP system instances on one host (standard system).However, if you upgraded your SAP system from a release based on a SAP NetWeaver release lower than 7.3, your SAP system might not yet have a separate ASCS instance.The section Splitting Off an ABAP Central Services Instance from an Existing Primary Application Server Instance [page 116] describes how you can move the message server and the enqueue work process from the ABAP stack of an existing primary application server instance to a newly installed central services instance for ABAP (ASCS instance).

2 Installation Options Covered by this Guide2.5 Central Services Instance for ABAP Separate from Existing Primary Application Server Instance of an

Upgraded System

2014-03-17 CUSTOMER 21/142

2.6 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 118] describes how to perform the installation.

2 Installation Options Covered by this Guide2.6 SAP Host Agent as a Separate Installation

22/142 CUSTOMER 2014-03-17

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 instanceDetailed 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 http://service.sap.com/instguides.For more information, see Before You Start [page 10].

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

Standard, Distributed, or High-Availability SystemNOTEIn 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 24] on every installation host.2. You identify basic SAP system installation parameters [page 29].3. For the database installation, we recommend that you check the information available in the SAP

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

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

41].8. Optionally, you decide whether you want to install multiple components in one database (MCOD) [page

113].9. Continue with Preparation [page 45].

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

want to install one or more additional application server instances.

3 Planning3.1 Planning Checklist

2014-03-17 CUSTOMER 23/142

2. You identify basic SAP system installation parameters [page 29].3. Continue with Preparation [page 45].

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 http://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 25]. Integrated in the installation tool (mandatory) as part of the installation process

For more information, see Running the Installer [page 75].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 26].

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 http://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 Planning3.2 Hardware and Software Requirements

24/142 CUSTOMER 2014-03-17

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.

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 fromhttp://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 75].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.


2014-03-17 CUSTOMER 25/142

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.

SAP System Hardware RequirementsRequirement Values and ActivitiesDistribution 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 the Database System Configuration guide in SAP Database Guide: Oracle in the SAP Library [page 13] at: SAP NetWeaver Process Integration 7.1 / 7.1 including Enhancement Package 1:

Function-Oriented View Database Administration Database Administration for Oracle

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

Administration for Oracle .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 ASCS instance and 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 compatibleHard 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 61].

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.For more information about space requirements for the file systems and directories of the instances, see SAP Directories [page 49] and the appropriate database-specific information listed below.


26/142 CUSTOMER 2014-03-17

Requirement Values and Activities Central services instance (SCS) for Java:

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

Minimum 3.5 GB Central services instance for ABAP (ASCS):

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

Minimum 3.5 GB Database Instance:

Minimum 80 GBFor more information about space requirements for the separate file systems and directories, see Oracle Directories [page 55].

Primary application server instance:Minimum 11 GB

Additional application server instance:Minimum 11 GB

SAP Host Agent:Minimum 0.5 GB

RAM The following lists the RAM requirements for each 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 Central services instance for ABAP (ASCS)

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

Minimum 1 GB Database Instance:

Minimum 1 GBNOTEThe default value used by the installer is 50 percent of the entire RAM.

Primary application server instance:Minimum 8 GB

Additional application server instance:Minimum 8 GB

SAP Host Agent:Minimum 0.5 GB

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 http://service.sap.com/swdc.


2014-03-17 CUSTOMER 27/142

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.

Diagnostics Agent Hardware RequirementsCategory RequirementMinimum 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

Software RequirementsRequirement Values and ActivitiesDatabase software Check the Product Availability Matrix (PAM) at http://service.sap.com/

pam for supported database platforms.Operating system version Your operating system platform must be 64-bit.

Check the Product Availability Matrix (PAM) at http://service.sap.com/pam for supported operating system versions.To check the operating system version on your installation hosts, enter the relevant command for your operating system: /bin/uname -r

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

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

National Language Support (NLS)

Make sure that National Language Support (NLS) and corresponding locales are installed.Make sure that the following files are available: iso_8859_1, en_US.


28/142 CUSTOMER 2014-03-17

Other RequirementsRequirement Values and ActivitiesHost 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.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.

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

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 SAP system profile directory only for systems with instances on separate hostsFor 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.

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 parametersFor all other installation parameters, use the F1 help on the installer screens.

3 Planning3.3 Basic SAP System Installation Parameters

2014-03-17 CUSTOMER 29/142

SAP System ParametersParameters 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 the current release.If you install an additional application server instance in an existing non-Unicode system (that has been upgraded to the current release), the additional application server instance is installed automatically as a non-Unicode instance. The installer checks whether a non-Unicode system exists and chooses the right executables for the system type.

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 following, which are reserved IDs:

ADD ADM ALL AMD AND ANY ARE ASC AUX AVG BIN BIT CDC COM CON DBA DTD END EPS EXE FOR GET GID IBM INT KEY LIB LOG LPT MAP MAX MEM MIG MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP TRC UID USE USR VAR

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.

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.


30/142 CUSTOMER 2014-03-17

Parameters DescriptionTo 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.For more information about the naming of SAP system instances, see SAP Directories [page 49].

///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 table Operating System Users). In this case, make sure that the master password meets the requirements of your operating system.

ABAP users: SAP*, DDIC, and EARLYWATCH. Java users

(for example J2EE_ADMIN) Secure Store key phrase

For 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).


2014-03-17 CUSTOMER 31/142

Parameters DescriptionMessage 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 PortThere 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, where 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, where is the instance number of the ABAP message server instance.Java Message Server PortThe Java message server only uses the internal message server port. The SCS instance profile contains the configuration for the Java message server.The parameter rdisp/msserv is set to 0, so that the external port is not open.The internal message server port uses the parameter rdisp/msserv_internal with default value 39, where is the instance number of the SCS message server instance.For more information about the parameters used for message server ports, see SAP Note 821875.

Java Administrator User The installer creates this user in the ABAP system.After the installation, this user is available both in the ABAP and in the Java system.The installer sets the user name J2EE_ADMIN and the master password by default.If required, you can choose another user name and password according to your requirements.

Java Guest User This user is for employees who do not belong to a company or who have registered as company users and who are waiting for approval. Guest users belong to the default group Authenticated Users.The installer creates this user in the ABAP system.After the installation, it is available both in the ABAP and in the Java system.The installer sets the user name J2EE_GUEST and the master password by default.If required, you can choose another user name and password according to your requirements.For more information about supported UME data sources and change options, see SAP Note 718383.


32/142 CUSTOMER 2014-03-17

Parameters DescriptionCommunication User The installer creates this user in the ABAP system.

After the installation, it is available both in the ABAP and in the Java systemThis user is used for the communication between the ABAP system and the Java system.The installer sets the user name SAPJSF and the master password by default.If required, you can choose another user name and password according to your requirements.For more information about supported UME data sources and change options, see SAP Note 718383.

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.

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.


2014-03-17 CUSTOMER 33/142

Parameters DescriptionThe 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.

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

Diagnostics Agent ParametersYou can optionally install the Diagnostics Agent with the SAP system.Diagnostics Agent System ID and Instance NumberParameters DescriptionDiagnostics Agent System ID (DASID)

By default the installer sets the Diagnostics Agent System ID (DASID) to DAA.If 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 Does not include any of the following, which are reserved IDs:

ADD ADM ALL AMD AND ANY ARE ASC AUX AVG BIN BIT CDC COM CON DBA DTD END EPS EXE FOR GET GID IBM INT KEY LIB LOG LPT MAP MAX MEM MIG MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP TRC UID USE USR VAR

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.


34/142 CUSTOMER 2014-03-17

Parameters DescriptionThe 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 49].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.

Operating System UsersParameters DescriptionSAP 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.

Diagnostics Agent SLD ParametersParameters DescriptionSLD Destination for the Diagnostics Agent You can choose between the following options:

Register in existing central SLDChoose 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.Refer to SAP Note 1833501 for details.

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


2014-03-17 CUSTOMER 35/142

Parameters DescriptionRECOMMENDATIONThe 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.

SAP Solution Manager Connectivity ParametersParameters DescriptionConnection 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.Refer to SAP Note 1833501 for details.

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

Connection Type for the Diagnostics Agent

You can choose between the following options: P4 connection via SCS message server Direct P4 connection via Java EE dispatcher nodeIf 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

RECOMMENDATIONIt is recommended to select a connection via the SCS message server.

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


36/142 CUSTOMER 2014-03-17

Parameters DescriptionRECOMMENDATIONThe 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.

SAP System Database ParametersParameters DescriptionDatabase 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


2014-03-17 CUSTOMER 37/142

Parameters Description Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs:

ADD ADM ALL AMD AND ANY ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR

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 113].

Database schema, Password The Java database schema is named SAPDB.Default name is SAPSR3DB.The ABAP database schema is named SAP.Default name is SAPSR3.

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.Each 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 DBSIZE.XML is not changed. 2000: Default datafile size. 10000: Maximum datafile size.For more information about space requirements of the SAP datafiles (sapdata 1 - 4), see Hardware and Software Requirements Tables [page 26].


38/142 CUSTOMER 2014-03-17

3.4 SAP System Transport HostThe transport host contains the transport directory used by the SAP transport system to store transport data and change SAP system information, such as software programs, write dictionary data, or Customizing data. If you have several SAP systems, they are usually organized in transport domains. In most cases, all SAP systems in a transport domain have a common transport directory.When you install an SAP system, you have to decide which transport host and directory you want to use for your SAP system: Use the transport directory that the installer creates during the installation of the SAP system by

default on the global host.The installer by default creates the transport directory on the global host in /usr/sap/trans.

Use a transport directory located on a host other than the default host: You can use an existing transport directory and host in your SAP system landscape. 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. For more information, see Exporting and Mounting the Global Transport Directory [page 73].

More Information Required File Systems and Directories [page 49] See the SAP Library [page 13]:

Release SAP Library Path SAP NetWeaver Process Integration

7.1 SAP NetWeaver Process Integration

7.1 Including Enhancement Package 1

Function-Oriented View ABAP Technology / Application Server ABAP Administration Tools for AS ABAP Transport and Change Management Change and Transport System Transport Management System (BC-CTS-TMS)

SAP NetWeaver 7.3 SAP NetWeaver 7.3 including

Enhancement Package 1 SAP NetWeaver 7.4

Solution Life Cycle Management Software Logistics Change and Transport System Change and Transport System Overview Basics of the Change and Transport System Transport Management System Concept

3.5 Diagnostics Agent Specific Planning StepsThe 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.

CAUTIONThe check box on the Install Diagnostics Agent screen will be disabled if the kernel or JVM prerequisites for the Diagnostics Agent are not met. For more information refer to chapter Installing the Diagnostics Agent Optionally with the SAP System in the latest Diagnostics Agent Setup Guide attached to SAP Note 1858920.

3 Planning3.4 SAP System Transport Host

2014-03-17 CUSTOMER 39/142

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 refer to 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.The Diagnostics Agent Setup Guide holds further 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.

3.5.1 Connection SelectionBefore starting the installation make sure that you have identified which installation strategy you want to use. The below two scenarios are compatible, you can configure both connections, or only one of them, or none of them.

RECOMMENDATIONWe recommend that you choose Direct SAP Solution Manager Connection.

Direct SAP Solution Manager Connection: In this scenario, the Diagnostics Agent establishes a direct connection to the SAP Solution Manager system. If you select Do not configure connection the Diagnostics Agent is not connected to the SAP Solution Manager system. For details see section Direct SAP Solution Manager Connection [page 40].

System Landscape Directory Registration: In this scenario the Diagnostics Agent is registered into the specified System Landscape Directory (SLD). This scenario may be used if SAP Solution Manager is not yet installed. If you select No SLD destination the Diagnostics Agent is not registered into the SLD. For details see section System Landscape Directory Registration [page 41].

CAUTIONIf you select neither Direct SAP Solution Manager Connection nor System Landscape Directory Registration you will have to configure the Diagnostics Agent connectivity via the smdsetup script after the installation is finished.Refer to SAP Note 1833501 for details.

3.5.2 Direct SAP Solution Manager ConnectionConnect the Diagnostics Agent directly to the SAP Solution Manager system. The below connection types are available.For more information, see SAP Solution Manager Connectivity Parameters, which is available at Basic SAP System Installation Parameters [page 29]

3 Planning3.5 Diagnostics Agent Specific Planning Steps

40/142 CUSTOMER 2014-03-17

P4 connection via SCS message server: the Diagnostics Agent connects to the SCS message server and is redirected to one of the dispatcher nodes of the Java EE engine.

P4 SSL connection via SCS message server: the same as P4 connection via SCS message server, but with SSL support. Direct P4 connection via Java EE dispatcher node: the Diagnostics Agent connects to the selected Java EE

dispatcher node. Direct P4 SSL connection via Java EE dispatcher node: the same as Direct P4 connection via Java EE dispatcher node,

but with SSL support.

RECOMMENDATIONIt is recommended to select a connection via the SCS message server.

3.5.3 System Landscape Directory RegistrationThe System Landscape Directory (SLD) is designed for registering the systems and installed software of your landscape. If you choose to register the Diagnostics Agent in an SLD, it must be assigned to the SAP Solution Manager system afterwards ( Transaction: SOLMAN_SETUP Scenario: System Preparation

Step: Connect Diagnostics Agents to Solution Manager ). This allows installing a Diagnostics Agent even if the SAP Solution Manager system is not available.For more information, see Diagnostics Agent SLD Parameters, which is available at Basic SAP System Installation Parameters [page 29].

3.6 Planning the Switchover Cluster for High AvailabilityYou can reduce unplanned downtime for your SAP system by setting up a switchover cluster. This setup installs critical software units known as single points of failure (SPOFs) across multiple host machines in the cluster. In the event of a failure on the primary node, proprietary switchover software automatically switches the failed software unit to another hardware node in the cluster. Manual intervention is not required. Applications trying to access the failed software unit might experience a short delay but can then resume processing as normal.Switchover clusters also have the advantage that you can deliberately initiate switchover to release a particular node for planned system maintenance. Switchover solutions can protect against hardware failure and operating system failure but not against human error, such as operator errors or faulty application software. Additional downtime might be caused by upgrading your SAP system or applying patches to it.Without a switchover cluster, the SAP system SPOFs central services instance, the database instance, and the central file share are vulnerable to failure because they cannot be replicated. All of these can only exist once in a normal SAP system.You can protect software units that are not SPOFs against failure by making them redundant, which means simply installing multiple instances. For example, you can add additional application server

3 Planning3.6 Planning the Switchover Cluster for High Availability

2014-03-17 CUSTOMER 41/142

instances. This complements the switchover solution and is an essential part of building high availability (HA) into your SAP system.

RECOMMENDATIONWe recommend switchover clusters to improve the availability of your SAP system.

A switchover cluster consists of: A hardware cluster of two or more physically separate host machines to run multiple copies of

the critical software units, in an SAP system the SPOFs referred to above Switchover software to detect failure in a node and switch the affected software unit to the standby

node, where it can continue operating A mechanism to enable application software to seamlessly continue working with the switched

software unit normally this is achieved by virtual addressing (although identity switchover is also possible)

PrerequisitesYou must first discuss switchover clusters with your hardware partner because this is a complex technical area. In particular, you need to choose a proprietary switchover product that works with your operating system.We recommend that you read the following documentation before you start: Check the information and the installation guides that are available at http://scn.sap.com/docs/

DOC-7848. The enqueue replication server (ERS) is essential for a high-availability system. You need one ERS

for the Java SCS and one ERS for the ASCS installed in your system.


42/142 CUSTOMER 2014-03-17

Features

Figure 7: Switchover Setup

NOTEThis figure and the figures in this section are only examples. Only the instances relevant to the switchover are shown for example, the primary application server instance is not shown.These graphics summarize the overall setup and do not show the exact constellation for an installation based on one of the available technologies (ABAP, ABAP+Java, or Java).You need to discuss your individual HA setup with your HA partner.


2014-03-17 CUSTOMER 43/142

Figure 8: Switchover Cluster

ConstraintsThis documentation concentrates on the switchover solution for the central services instance. For more information about how to protect the Network File System (NFS) software and the database instance by using switchover software or (for of the database) replicated database servers, contact your HA partner.This documentation concentrates on the switchover solution for the central services instance. For more information about how to protect the central file share and the database instance by using switchover software or (for of the database) replicated database servers, contact your HA partner.Make sure that your hardware is powerful enough and your configuration is robust enough to handle the increased workload after a switchover. Some reduction in performance might be acceptable after an emergency. However, it is not acceptable if the system comes to a standstill because it is overloaded after switchover.


44/142 CUSTOMER 2014-03-17

4 Preparation

4.1 Preparation ChecklistThis section includes the preparation steps that you have to perform for the following installation options: Standard, distributed, or high-availability system Additional application server instanceDetailed information about the steps is available in the relevant section.

Standard, Distributed, or High-Availability SystemNOTEIn 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 that the required operating system users and groups [page 46] are created.2. You set up file systems [page 49] and make sure that the required disk space is available for the

directories to be created during the installation.3. If required, you set up virtual host names [page 60].4. If you want to install a high-availability system, you perform switchover preparations [page 61].5. If you want to share the transport directory trans from another system, export [page 73] this

directory to your installation hosts.6. You install the SAP frontend software [page 61] on the desktop of the user.7. You check that the required installation media [page 61] are available on each host.8. If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page

115].9. You continue with Installation [page 67] .

Additional Application Server InstanceYou have to perform the following preparations on the host where you install the additional application server instances:1. You check that the required operating system users and groups [page 46] are created.2. You set up file systems [page 49] and make sure that the required disk space is available for the

directories to be created during the installation.

4 Preparation4.1 Preparation Checklist

2014-03-17 CUSTOMER 45/142

3. If you want to use virtual host names, you have to set the environment variable SAPINST_USE_HOSTNAME [page 60]. Alternatively you can specify the virtual host name in the command to start the installer.

4. If you want to share the transport directory trans from another system, export [page 73] this directory to your installation hosts.

5. You install the SAP frontend software [page 61] on the desktop of the user.6. You check that the required installation media [page 61] are available.7. You continue with Installation [page 67] .

4.2 Creating Operating System Users and GroupsDuring the installation, the installer checks all required accounts (users, groups) and services on the local machine. The installer checks whether the required users and groups already exist. If not, it creates new users and groups as necessary.If you do not want the installer to create operating systems users, groups, and services automatically, you can optionally create them before the installation is started. This might be the case if you use central user management such as Network Information System (NIS).The installer checks if the required services are available on the host and creates them if necessary. See the log messages about the service entries and adapt the network-wide (NIS) entries accordingly.The installer checks the NIS users, groups, and services using NIS commands. However, the installer does not change NIS configurations.

RECOMMENDATIONFor a distributed or a high-availability system, we recommend that you distribute account information (operating system users and groups) over the network, for example by using Network Information Service (NIS).

If you want to use global accounts that are configured on a separate host, you can do this in one of the following ways: You start the installer and choose Generic Installation Options Preparation Operating

System Users and Groups . For more information, see Running the Installer [page 75]. You create operating system users and groups manually. Check the settings for these operating

system users.

Constraints You have to set the limits for operating system users as follows:

Using csh shell, the output of command limit needs to be as follows:Output Propertiescputime unlimited

4 Preparation4.2 Creating Operating System Users and Groups

46/142 CUSTOMER 2014-03-17

Output Propertiesfilesize unlimiteddatasize unlimitedstacksize 8192 KBcoredumpsize unlimiteddescriptors 8192memorysize unlimited

Using sh or ksh shell, the output of command ulimit -a needs to be as follows:Output Propertiestime(seconds) unlimitedfile(blocks) unlimiteddata(kbytes) unlimitedstack(kbytes) 8192coredump(blocks) unlimitednofiles(descriptors) 8192memory(KBytes) unlimited

All users must have identical environment settings. Any change to the envir

installation guide sap netweaver abap+java (for process integration) on solaris oracle using...

Documents

sap note

sap installation document

sap plans

sap components

sap installation tools

names of installation

earlier sap system releases

sap technical consultants