NW Inst Guide ASE Linux

Installation GuideDocument version: 1.5 – 2014-07-07

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseUsing Software Provisioning Manager 1.0

PUBLIC

About this Installation Guide

SAP System Installation

SAP system installations should only be performed by SAP Technical Consultants certified for your operating system, your database, and the SAP system that you are installing

SAP Installation Tool

Only use the SAP installation tools according to the instructions and for the purposes described in the SAP installation document. Improper use of the SAP installation tools can damage files and systems already installed.

2

PUBLIC© Copyright 2014 SAP AG.All rights reserved.

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server Enterprise

About this Installation Guide

Typographic Conventions

Table 1

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

Example Example 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 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 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 ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseTypographic Conventions

PUBLIC© Copyright 2014 SAP AG.

All rights reserved. 3

http://www.sap.com

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0


Document History

CautionBefore you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace service.sap.com/instguides.

The following table provides an overview on the most important document changes:

Table 2

Version Date Description

1.0 2012-08-06 First version for software provisioning manager 1.0

1.1 2012-09-25 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 specific operating systems are highlighted accordingly.

4



Document History

http://service.sap.com/instguides

Content

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.2 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

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

3.3 Basic SAP System Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.4 Setup of Database Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.5 SAP System Transport Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.6 Planning the Switchover Cluster for High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.7 Diagnostics Agent – Specific Planning Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Connection Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Direct SAP Solution Manager Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 System Landscape Directory Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.2 Creating Operating System Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.3 Required File Systems and Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Setting Up File Systems for a High-Availability System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4.4 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.5 Performing Switchover Preparations for High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664.6 Installing the SAP Front-End Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664.7 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.2 Exporting and Mounting the Transport Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.3 Exporting and Mounting Global Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseContent



5.4 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.5 Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Useful Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Interrupted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Entries in the Services File Created by the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Troubleshooting with the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936.2 Performing Post-Installation Steps for the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946.3 Logging On to the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946.4 Performing the Consistency Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956.5 Installing the SAP License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966.6 High Availability: Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976.7 Configuring the Remote Connection to SAP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986.8 Installing the SAP Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986.9 Applying the Latest Kernel and Support Package Stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986.10 SAP Kernel 7.40 and Higher: IP Multicast Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996.11 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996.12 Configuring the Change and Transport System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016.13 Enabling the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026.14 Performing a Full Installation Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

7 Disaster Recovery Setup with SAP Replication Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057.1 Implementation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067.3 Installing the Replication Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Materializing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097.4 Starting and Stopping DR Agent and Replication Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117.5 Removing the Replication Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137.6 Integration of SAP Replication Server into an OS Cluster Environment . . . . . . . . . . . . . . . . . . . . . . . 114

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Defining Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

7.7 Defining Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187.8 Defining Node Failure Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

8 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208.1 Splitting Off a Central Services Instance for ABAP from an Existing Primary Application Server

Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208.2 Integration of LDAP Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238.3 Checking and Modifying the HP-UX Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1278.4 Setting up Swap Space for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288.5 Creating HP-UX Groups and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308.6 Setting Up File Systems for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318.7 Mounting Installation Media for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348.8 Exporting and Mounting Directories via NFS for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358.9 Installing the SAP Host Agent Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

6



Content

8.10 Starting and Stopping SAP System Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Starting and Stopping SAP System Instances Using the SAP Management Console . . . . . . . . . . 138 Starting and Stopping SAP System Instances Using Commands . . . . . . . . . . . . . . . . . . . . . . . . 141 Starting and Stopping the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

8.11 Creating a User for LDAP Directory Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1458.12 Heterogeneous SAP System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1458.13 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

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

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseContent



8



1 Introduction

This installation guide describes how to install an SAP NetWeaver ABAP system using the installation tool software provisioning manager 1.0 (“installer” for short). This guide applies to the following releases:

Table 3

Product Release

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 6 for SAP ERP 6.0, Version for SAP HANA based on SAP NetWeaver AS ABAP 7.4

● 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 Enhancement Package 2 for SAP CRM 7.0, Version for SAP HANA based on SAP NetWeaver AS ABAP 7.4

● 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 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 SCM ● SAP Enhancement Package 2 for SAP SCM 7.0, Version for SAP HANA based on SAP NetWeaver AS ABAP 7.4

● 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

Constraints

● Your operating system platform must be 64-bit.

● Not supported:

○ SAP Adaptive Server Enterprise Cluster Edition

○ Raw devices

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseIntroduction



Naming Conventions

● Sybase Adaptive Server Enterprise (Sybase ASE) has been replaced with SAP Adaptive Server Enterprise (SAP ASE).

● installer refers to software provisioning manager 1.0.

● SAP system refers to SAP system based on the application server of SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver Application Server ABAP 7.4 / SAP NetWeaver 7.4 / 7.4 SR1.

● ABAP system refers to SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / SAP NetWeaver Application Server ABAP 7.4 / 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.

Profiling for SAP Adaptive Server Enterprise

The profile bars with the wording Only vaild for: Sybase ASE refer to content that is valid for the database SAP Adaptive Server Enterprise (SAP ASE). The database was previously called Sybase Adaptive Server Enterprise (Sybase ASE). You might still find the abbreviation Sybase ASE in some sections of this guide.

1.1 Before You Start

Make 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 service.sap.com/instguides:

Table 4

Document Internet Address

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 <Number> for SAP ERP 6.0

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

Master Guide (Including Upgrade Information) - SAP Supplier Relationship Management 7.0 <Including SAP Enhancement Package <Number>>

service.sap.com/srm-inst <Your release and enhancement package>

10



Introduction



http://service.sap.com/installNW73



http://service.sap.com/erp-ins

http://service.sap.com/srm-inst

Document Internet Address

Master Guide (Including Upgrade Information) - SAP Customer Relationship Management 7.0 <Including SAP Enhancement Package <Number>>

service.sap.com/crm-inst <Your release and enhancement package> Plan

Master Guide SAP Supply Chain Management 7.0 <Including SAP Enhancement Package <Number>> Powered by SAP NetWeaver

service.sap.com/instguides SAP Business Suite Applications SAP SCM <Your release and enhancement package> Master Guide

1.2 New Features

The table below provides an overview of the new features.

Make sure that you also read the release notes at service.sap.com/releasenotes.

Table 5

Area 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 67] 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_<Version>_U_<Your Operating System Platform>) medium and installed automatically by software provisioning manager. You do not have to separately download SAPCRYPTO.SAR any longer. For more

information, see Basic SAP System Installation Parameters [page 35]

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.




http://service.sap.com/crm-inst


http://service.sap.com/releasenotes


Area Description

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.

Declustering and depooling of ABAP tables

Declustering and depooling of tables during the installation is now supported. It is relevant if you want to take advantage of optimizations for SAP Business Suite. For more information, see SAP Note 1892354.

Supported database versions The following database versions are supported:

● SAP Sybase Adaptive Server Enterprise 15.7 (SAP Sybase ASE 15.7)

● SAP Adaptive Server Enterprise 16.0 (SAP ASE 16.0)

Check SAP Note 1973241 - SYB: SAP Applications on SAP Adaptive Server Enterprise 16.0 for more information on the new database version.

1.3 SAP Notes for the Installation

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

SAP 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 SAP NetWeaver 7.1 and higher: UNIX

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

1748888 SYB: Inst. Systems Based on NW 7.3 and higher: SAP ASE

Software Provisioning Manager 1.0: SAP NetWeaver 7.3 and higher

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

1554717 Planning Information for SAP on ASE SAP release information for customers deploying SAP on ASE

12



Introduction






http://service.sap.com/notes







SAP Note Number Title Description

1619967 SYB: DBA Cockpit Correction Collection SAP Basis 7.31

The implementation of SAP Note 1619967 directly after the installation is strongly recommended.

1882376 SYB: DBA Cockpit Correction Collection SAP Basis 7.40

The implementation of SAP Note 1882376 directly after the installation is strongly recommended.

1245200 ICF Service Activation for Web Dynpro DBA

The Web browser-based version of the DBA Cockpit does not start correctly.

1585981 SYB: Backup Instructions for SAP on ASE

Information about backup and recovery

1650511 SYB: High Availability Offerings with SAP ASE

Information about high availability cluster solutions for SAP ASE

1407532 Release Restrictions for SAP NetWeaver 7.3 EHP1

Customer information on restrictions in the production use of certain functions

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

789220 Support Package level for SAP NetWeaver Installations/Upgrades

Information about the Support Package levels and kernel patch levels contained in the current SAP NetWeaver release

171356 SAP software on Linux: Essential comments

This SAP Note contains Linux-specific information about the SAP system installation.

1496410 Red Hat Enterprise Linux 6: Installation and Upgrade

This SAP Note contains information that is specific to the SAP system installation on Red Hat Enterprise Linux 6.

1541935 Using SAP Systems with AIX 7.1 This SAP Note contains information that is specific to the SAP system installation on AIX 7.1.

1067221 Central 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 Library

The references to SAP NetWeaver Library documentation in this installation guide always refer to the following on SAP Help Portal:



















Table 7

Product and Release SAP Library Path

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 Application Server ABAP 7.4

help.sap.com/soh <Product_and_Release> Application Help SAP

Library: English SAP NetWeaver

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

14



Introduction

http://help.sap.com/nw73


http://help.sap.com/soh


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]

● Only valid for: HA (UNIX) |

High-availability system [page 17]End of: HA (UNIX) |

● 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 System

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

● Database instance (DB)

● Primary application server instance (PAS instance)

Additionally you can install one or more additional application server instances. For more information, see Additional Application Server Instance [page 18].

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseInstallation Options Covered by this Guide



Figure 1: Standard ABAP System

2.2 Distributed System

An 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:

NoteWe strongly recommend installing the ASCS instance on the same host as the primary application server. The installation of the ASCS instance on a separate host is reserved for high-availability configurations on Windows that are not using Microsoft Failover Clustering.



The ABAP 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 ASCS instance as global file system. That means that the host with the ASCS 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 18].

16



Installation Options Covered by this Guide

Figure 2: Distributed ABAP System

Only valid for: HA (UNIX) |

2.3 High-Availability System

An 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:


● Enqueue replication server instance (ERS instance) for the ASCS instance (mandatory)


● Primary application server instance (PAS)

The graphics below assume that you run the ASCS 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 ASCS instance in a switchover cluster infrastructure. The ASCS 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 18].

The following figures show examples for the distribution of the SAP instances in a high-availability system.




Figure 3: High-Availability System

End of: HA (UNIX) |

2.4 Additional Application Server Instance

You 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

Additional Application Server Instance for a Standard System

For 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

18




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 System

The 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


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




Figure 5: Additional Application Server Instance for a Distributed System

For more information, see Distributed System [page 16].Only valid for: HA (UNIX) |

Additional Application Server Instance for a High-Availability System

The following figure shows a high-availability system with additional application server instances that run:

● On the host of the primary application server instance


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

20




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

For more information, see High-Availability System [page 17].End of: HA (UNIX) |

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

The central services instance for ABAP (ASCS instance) consists of the essential enqueue and message system services only. With a separate ASCS instance, it is easier for you to later turn your SAP system into a high-availability system.

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 120] describes how you can move the message server and the enqueue work process from an existing primary application server instance to a newly installed central services instance for ABAP (ASCS instance).




2.6 SAP Host Agent as a Separate Installation

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

22




3 Planning

3.1 Planning Checklist

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

Prerequisites

1. You have planned your SAP system landscape according to the Master Guide available at the appropriate download location under service.sap.com/instguides.

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

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 24] on every installation host.

2. You identify Basic SAP System Installation Parameters [page 35].

3. You plan the setup of your database [page 45].

4. You decide on the transport host to use [page 47].

5. You decide whether you want to integrate LDAP Directory Services in your SAP system [page 123].

6. If you want to install the Diagnostics Agent together with your SAP system, read the Diagnostics Agent – specific planning steps [page 50].

7. Only valid for: HA (UNIX) |

To install a high-availability system, you read Planning the Switchover Cluster for High Availability [page 48].End of: HA (UNIX) |

8. Continue with Preparation [page 53].

Additional Application Server Instance

1. You check the Hardware and Software Requirements [page 24] on every installation host.

2. You identify Basic SAP System Installation Parameters [page 35].

3. Continue with Preparation [page 53].

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterprisePlanning




3.2 Hardware and Software Requirements

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

Process Flow

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

○ Integrated in the installation tool (mandatory) as part of the installation process

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

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.

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.

24



Planning


http://service.sap.com/pam


http://service.sap.com/sizing

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

Procedure

1. 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<Support_Package_Number>_<Version_Number>.SAR from

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

2. Unpack the software provisioning manager 1.0 archive to a local directory using the following command:

SAPCAR -xvf <Path_To_Download_Directory>/<Archive>.SAR -R <Unpack_Directory>2. Start the installer as described in Running the Installer [page 77].

3. On the Welcome screen, choose <SAP_Product> <Database> 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.

Result

The 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 Hosts

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




http://service.sap.com/swdc

Table 8

Operating System: More information:

AIX You can perform AIX-specific steps using the following tools:

● Manually by entering AIX commands with the appropriate options

● Using System Management Interface Tool (SMIT), a menu-driven system administration tool

If you have problems with the function keys, you can also use ESC and the corresponding

number to simulate the function key (for example, F4 is equivalent to ESC and 4 ).

HP-UX For an SAP system installation on HP-UX, consider the following information:

● SAP on ASE uses Concurrent I/O on HP-UX. The Veritas File System (Online JFS 5.0.1 or above) must be installed on your system prior to installing SAP on ASE and HP-UX. For more information, refer to SAP Note 1077887.

● SAP Adaptive Server Enterprise 16.0: Install the following AioEnh patch: h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=AioEnh.

● SAP only supports the use of native binaries. Always use the appropriate SAP binaries for your processor.

● For recommendations and information about availability of HP-UX 11.31 (also known as HP-UX 11iv3), see SAP Note 1031960.

Linux For general information about the SAP system installation on Linux, see SAP Note 171356.

Solaris For more information, refer to scn.sap.com/community/oracle-solaris.

Table 9: Hardware Requirements

Requirement Values and Activities

Optical Media Drive

ISO 9660 compatible

Linux: Must be connected locally to your central instance host.

CPU Database instance:

The following hardware architectures are supported:

AIX, Solaris: All 64-bit processors that are capable of running the supported operating system version.Itanium-based integrity system (IA64) is not supported for Solaris

HP-UX: Itanium-based HP Integrity system

Linux: AMD64, Itanium-based integrity system (IA64) is not supported

All other instances:

The recommended minimum hardware is:

● Two dual core CPUs or

● Four single core CPUs

To display the number of CPUs in a system, enter the following command:

AIX: lparstat -i | grep "Entitled Capacity"HP-UX: ioscan -fnkCprocessorLinux: grep -c ^processor /proc/cpuinfo

26



Planning


https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=AioEnh

https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=AioEnh



http://scn.sap.com/community/oracle-solaris


Solaris: /usr/sbin/psrinfo -vp

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

1.2 GB of temporary disk space for the installation.

● AIX:

For data security reasons, distribution over three disks is required. We recommend you to distribute over five disks.

To display available disks, enter the following command:

lspvDisks marked none in the 3rd column are unused.

To display free space on a disk, enter the following command:

lspv -p <disk_name>Areas marked free in the 2nd column are unused.

● Linux:

If an advanced disk array is available (for example, RAID), contact your hardware vendor to make sure that the data security requirements are covered by this technology.

To print and change the partitioning of the first SCSI disk, enter the following command:

/sbin/fdisk /dev/sdaTo print and change the partitioning of a RAID device, enter commands specific to your hardware.

ExampleThe following hardware-specific commands for RAID devices are typical:

/sbin/fdisk /dev/rd/c0d0/sbin/fdisk /dev/ida/c0d0

● Solaris:

SAP ASE is available for Solaris 10 and Solaris 11.

For more information on SAP ASE on Solaris 11, refer to SAP Note 1716200.

For more information about specifying device names and about displaying and changing the partitioning, see the Solaris System Administrator Collection at the Sun website.

● 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 57] and the appropriate database-specific information listed below.

○ Only valid for: HA (MSCS);HA (UNIX) |

Central services instance for ABAP (ASCS) (high-availability only)

12 GB

End of: HA (MSCS);HA (UNIX) |

○ Only valid for: HA (MSCS);HA (UNIX) |

Enqueue replication server instance for the SCS (high-availability only)






2 GB

End of: HA (MSCS);HA (UNIX) |

○ Database Instance:

Minimum 12 GB

Database Software: 4 GB

4.5 GB of temporary disk space for every required installation medium you have to copy to a local hard disk.

1.2 GB of temporary disk space for the installation.

NoteFor safety reasons (system failure), the file systems must be physically distributed over several disks or RAID-technology must be used.

○ Central instance:

10 GB

○ Additional application server instance:

10 GB

○ SAP Host Agent:

1 GB

○ Diagnostics agent:

1.5 GB

RAM The following lists the RAM requirements for each instance.

If you install serveral instances on one host, you have to add up the requirements accordingly.

● Database Instance:

Minimum 3 GB

● Additional application server instance:

Minimum 3 GB

● SAP Host Agent:

0.5 GB

● Diagnostics agent:

1 GB

Linux:

To display RAM size in KB, enter the following command:

freeFor more information about how to interpret the output of this command correctly, see SAP Note 1382721.

HP-UX:

To display the RAM size on HP-UX, proceed as follows:

On HP-UX Itanium or all 11.31 systems, you can also use the following command:

/usr/contrib/bin/machinfo | grep Memory

28



Planning



Swap Space It is recommended that the swap space is at least twice as large as RAM.

Linux: For more information, see SAP Note 171356.

HP-UX: For the database instance, you need 3* RAM + 500 MB in addition, at least 20 GB recommended). For more information about HP-UX swap space recommendations, see SAP Note 1112627.

Table 10: Software Requirements


Database Software / Client Software

The following versions are supported: SAP Sybase ASE 15.7 and SAP ASE 16.0

(automatically installed by the installer)

Caution● For the installation of the SAP system, only the English version of the SAP ASE database is

supported.

● You must only use the SAP ASE software that is provided for the SAP Business Suite (Sybase ASE 15.7 for Bus.Suite, SAP ASE 16.0 for Bus.Suite).

Linux: Operating System Versions

Supported Linux versions:

● SAP ASE 16.0

RHEL 6.1

SLES11

● SAP Sybase ASE 15.7

RHEL 6

SLES11

To check the operating system version, enter the following command:

cat /etc/* -release

HP-UX: Operating System Versions

Supported HP-UX versions:

● SAP ASE 16.0

Minimum requirement:

HP-UX 11.31

The following patches are required:

PHSS_37493, PHSS_36352, PHKL_37802, PHKL_42687


Minimum requirement:

HP-UX 11.31


uname -r

AIX: Operating System Versions

● SAP ASE 16.0

AIX 7.1, TL 0 and higher


oslevel -s







Table 11

AIX Level: Required SP: oslevel -s

AIX 7.1 TL 0 SP8 7100-00-08-1241

AIX 7.1 TL 1 SP6 7100-01-06-1241

AIX 7.1 TL2 SP2 7100-02-02-1316

AIX 7.1 requires a patch that fixes APARIV10828. Contact IBM directly to obtain the patch.


AIX 7.1

AIX 7.1 requires a patch that fixes APARIV10828. Contact IBM directly to obtain the patch.

Oracle Solaris: Operating System Versions

Supported Solaris versions:

● SAP ASE 16.0

Solaris 10

The following patches are required:

120753-05, 120048-03, 144190-03

Solaris 11


Solaris 10

Solaris 11


uname – r

AIX: Kernel Parameters To adjust the settings for asynchronous I/O (AIO) if the database is installed using file systems, see SAP Note 1048686.

Linux: Kernel Parameters

● To check the Linux kernel version, enter the following command:

uname -r● To check the Linux kernel parameter settings, enter the following command:

/sbin/sysctl –a● If you are using a Linux kernel version certified by SAP, you do not need to modify the Linux

kernel. To check the Linux kernel version, enter the following command:

uname –rFor more information about the Linux kernel versions certified by SAP, see SAP Note 171356.

To check the Linux kernel parameters for your Linux distribution, see one of the following SAP Notes:

○ SLES11: SAP Note 1310037

○ RHEL 6: SAP Note 1496410

AIX: Additional Software

Make sure that the following additional file sets and the IOCP module are installed:

● bos.adt – Base Application Development

● bos.perf – Performance and Dagnostics Tools

30



Planning






● perfagent.tools – Performance Monitoring Tools

● bos.perf.libperfstat – Performance Statistics Library

For an overview of the installed file sets, enter the following command:

lslpp –L | more

Check whether the IOCP module version 6.1.5.0 or higher is installed on your system:

lslpp -l bos.iocp.rteThe output should be similar to the following example:

Path: /usr/lib/objreposbos.iocp.rte 6.1.5.0 APPLIED I/O Completion Ports APIPath: /etc/objreposbos.iocp.rte 6.1.5.0 COMMITTED I/O Completion Ports APIEnter the lsdev command to check whether the status of the IOCP port is Available:

lsdev -Cc iocpThe output should match the following example:

iocp0 Available I/O Completion PortsIf the IOCP port status is Defined change the status to Available.

Log in to the server as root and issue the following command:

# smitty iocpSelect Change / Show Characteristics of I/O Completion Ports.

Change the configured state at system restart from Defined to Available. Enter the lsdev command

again to confirm that the status of the IOCP port has changed to Available and reboot the system.

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

Solaris: OS Patches To check the installed patches, enter the following command:

/bin/showrev -p

NoteFor more information about relevant patches, see the following SAP Notes:

● Solaris 10: SAP Note 908334

● Solaris 11: SAP Note 1643799

Lightweight Directory Access Protocol (LDAP)

Linux:

If you want to use LDAP, you need the LDAP libraries that are usually installed with the openldap RPM. To check this, enter the following command:

rpm -qa | grep openldapMake sure that the output of this command contains the following RPM packages:

● Red Hat Linux:

openldap2● SUSE LINUX

openldap2








openldap2–clientHP-UX:

LDAP library:

HP-UX on Itanium (11.31)

libldapss141.soSolaris:

LDAP library:

libldap.soAIX:

LDAP library:

libldap.a

Fonts and Code Pages HP-UX:

The directory /lib/X11/fonts contains the available fonts.

You can select fonts in your default profiles for X11 and CDE.

Exampleiso_8859.1 or hp_roman8

Solaris:

Make sure that the required fonts and code pages are installed.

For more information, see the Solaris <Release> System Administrator Collection at the Sun website.

National Language Support (NLS)

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

AIX:

Install the necessary local code set by adding an additional language environment as follows:

1. Start the System Management Interface Tool (SMIT) with the following command:

smitty mle_add_lang2. Select the following:

○ Cultural Conventions to install:ISO8859-1 German (Germany) [de_DE]

○ Language Translation to install:ISO8859-1 German [de_DE]

This step installs the required bos.loc and bos.iconv file sets.

3. Check that all file sets are in a consistent state by entering the following command:

lppchk –vHP-UX

● Enter the following command to check whether National Language Support (NLS) is installed:

swlist -v | grep -i nlsThe output should contain the string NLS-AUX ...

● Enter the following command to check which locales are available:

32



Planning


locale -aThe following files must be available: de_DE.iso88591, en_US.iso88591.

Linux:

● To display available locales, enter the following command:

locale -a● Check the output for locales such as the following:

de_DE, en_US● SAP blended Code Pages are available as an attachment of SAP Note 171356.

For more information about NLS on Linux, see SAP Note 187864.

Solaris:

To display which locales are available, enter the following command:

locale -aThe following files must be available: iso_8859_1, en_US.

Linux: Additional Information

System Language:

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

Routing Information:

To check routing information, enter the following command:

netstat -rShared Memory File System:

To check the size of the shared memory file system, enter the following command:

df –k /dev/shmActivated Hardware Drivers:

To check the activated hardware drivers, enter the following command:

lsmod

Table 12: Other Requirements


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.

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.

Printer AIX, HP-UX:

● To check whether a file can be printed, enter the following command:

lp -d<printer_name> <test_file>● To check the status of your spool and the printers, enter the following command:










lpstat -tLinux:

● To check the status of spooling queues and printers, enter the following command:

lpc status● To check whether you can print a file, enter the following command:

lpr —P<printer_name> <test_file>Solaris:

● Solaris 10 and 11

For more information about how to set up a printer, see the Solaris <Release> System Administrator Collection at the Sun website.

Networking If application servers are installed decentralized, Network File System (NFS) must be installed.

AIX:

To test the network connection to the database server, enter the following command:

/etc/ping <db_server_name> 100 10HP-UX:

● To check the current kernel configuration files to make sure that the NFS driver is in the kernel, enter the following command:

grep nfs /stand/system● To check whether NFS is running, enter the following commands:

ps -ef | grep nfsdps -ef | grep rpcbindgrep NFS_C /etc/rc.config.d/nfsconfgrep NFS_S /etc/rc.config.d/nfsconf

● Either NFS_CLIENT, NFS_SERVER, or both should be set to 1. You can use SAM or SMH to start NFS or add the driver to the kernel.

Linux:

● To check whether NFS is running, do one of the following:

○ On Red Hat Linux:

service nfs statusservice portmap status

○ On SuSE Linux:

rcnfs status● Test the network connection to the database server with the following command:

ping -c 10 <db_server_name>Solaris:

● Solaris 10 and 11

For more information about how to set up and administer Network File System (NFS), see the <Release> System Administrator Collection at the Sun website.

34



Planning


AIX, HP-UX, Solaris: C++ Runtime Environment

Linux: C compiler

AIX:

Check the C++ runtime level with the following commands:

AIX 7.1:

#lslpp —L xlC.aix71.rteThe output must be at least 11.1.0.0.

#lslpp —L xlC.rteThe output must be at least 11.1.0.0.

HP-UX:

Make sure that the patch level of C++ runtime library is equal to or newer than the version recommended in the general HP-UX patch recommendations. For more information, see SAP Note 837670.

Solaris:

The Shared Library Patch for C++ must be installed.

Linux:

● To check that the C compiler gcc is installed, enter the following command:

rpm -qa | grep gcc● Make sure that the C compiler is installed.

3.3 Basic SAP System Installation Parameters

The 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 hosts

○ SAP systems based on SAP NetWeaver 7.40 and higher: Individual encryption key for the secure storage

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

● Custom

If you choose Custom, you are prompted for all parameters. At the end, you can still change any of these parameters on the Parameter Summary screen.

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 13

Parameters Description

SAP System ID <SAPSID> The SAP system ID <SAPSID> identifies the entire SAP system.

The installer prompts you for the <SAPSID> 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 primary application server 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 <SAPSID> 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.

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 <Instance_Number> of local (not mounted) /usr/sap/<SAPSID> directories.

36



Planning



For more information about the naming of SAP system instances, see SAP Directories [page 57].

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_Number (see

row “Message Server Port” in this table below). The NIM client daemon uses reserved ports 3901 and 3902.

End of: AIX |

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.

● 02 as the instance number because this number is used to determine the port number for report RSLGCOLL, which is 14<Instance_Number> 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 77].

End of: HP-UX |

/<sapmnt>/<SAPSID>/profile or /usr/sap/<SAPSID>/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/<SAPSID>/SYS/profile is the soft link referring to /<sapmnt>/<SAPSID>/profile.

Master Password Common password for all users that are created during the installation:

● Operating system users (for example <sapsid>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.

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

CautionThe installer applies the master password to users SAP*and DDIC for SAP system clients

000 and 001 only, but not to users SAP*, DDIC, and EARLYWATCH in SAP system client 066.

Instead, the installer always assigns the following passwords to these users in client 066:

SAP*: 06071992

EARLYWATCH: support

See also Ensuring user security.

Password policy

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

● Depending on the installation option, additional restrictions may apply.

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.

ABAP Message Server Port

There is an external message server port and an internal message server port.

The ABAP message server uses both the internal and the external message server ports. The default profile contains the configuration for both message server ports.

The external message server port uses the parameter rdisp/msserv with default value

36<ABAP_Message_Server_Instance_Number>.

The internal message server port uses the parameter rdisp/msserv_internal with default

value 39<ABAP_Message_Server_Instance_Number>.

For more information about the parameters used for message server ports, see SAP Note 821875.

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 <sapsid>adm○ Database administrator users

38



Planning



The 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 54].

SAP systems based on SAP NetWeaver 7.40 and higher:

Individual Encryption Key for the Secure Storage

You can set a randomly generated individual encryption key for the secure storage in the file system and the secure storage in the database. If you skip this step, the system is installed with a default key which provides obfuscation only, but it can be changed later.

For more information on the secure storage in the file system, see the SAP Library [page 13] at Security System Security System Security for SAP NetWeaver AS ABAP Only Secure

Storage in the File System (AS ABAP)

For more information on the secure storage in the database, see the SAP Library [page 13] at Security System Security System Security for SAP NetWeaver AS ABAP Only Secure

Storage (ABAP)

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.

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:

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






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 destination

Choose 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: 5<Instance_Number>00.

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 Parameters

You can optionally install the Diagnostics Agent with the SAP system.

Table 14: Diagnostics Agent System ID and Instance Number


Diagnostics 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 <DASID> 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 <DASID>.

CautionChoose the <DASID> carefully. Renaming is difficult and requires you to reinstall the

Diagnostics Agent.

Make sure that the <DASID>:

40



Planning


● 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<Instance_Number>.

For more information, see SAP Directories [page 57].

To find out the instance numbers of SAP systems that already exist on the installation host, look for subdirectories ending with <nn> of local (not mounted) /usr/sap/<SAPSID> directories.

The value <nn> is the number assigned to the instance.


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<Instance_Number>. The NIM client daemon uses reserved ports 3901 and 3902.

End of: AIX |


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<Instance_Number> 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 77].

End of: HP-UX |

Table 15: Operating System Users


SAP System Administrator: Administrator for the Diagnostics Agent.







<dasid>adm This user is dedicated to the Diagnostics Agent installation and has the authorization to manage the Diagnostics Agent.

If you did not create user <dasid>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 <dasid>adm are unique and the same on each application server

instance host.

SAP System Administrator:

sapadmSAP 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 Parameters


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 destination

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


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.

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:5<Instance_Number>00.

For HTTPS the following naming convention applies:5<Instance_Number>01.

42



Planning



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 Parameters


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

CautionFor 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

● 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<xx>, where <xx> is the instance number of the SAP

Solution Manager Java Central Services (SCS).






● HTTP SCS SSL Message Server Port is 443<xx> or 444<xx>, where <xx> is the instance

number of the SAP Solution Manager Java Central Services (SCS).

● Dispatcher P4 Port is 5<xx>04, where <xx> is the instance number of the SAP Solution

Manager Java central instance.

● Dispatcher P4 SSL Port is 5<xx>06, where <xx> 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 ParametersTable 18


Database ID <DBSID> The <DBSID> identifies the database instance. The installer prompts you for the <DBSID> when

you are installing the database instance.

The <DBSID> can be the same as the <SAPSID>.

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

44



Planning


○ Has a letter for the first character

○ Does not include any of the reserved IDs listed in SAP Note 1979280.

ABAP Database User (SAPSR3)

The user name corresponds to the owner of the database tables.

Database Communication Port

The database server communication port is used for TCP/IP communication between the database server and remote clients. In a standard system installation and for the database instance in a distributed installation, the installer always proposes 4901 as default.

Other Database Communication Ports

Backup Server: 4902

Job Scheduler: 4903

Add sapdata/saplog Directories

Database devices are stored in the following directories:

Only valid for: Linux |

/sybase/<DBSID>/sapdata_<n> and /sybase/<DBSID>/saplog_<n>

End of: Linux |

Only valid for: Linux |

NoteBe aware, that the first part, for example /sybase/<DBSID> is definite.

End of: Linux |

You can create additional sapdata, saplog directories before you start the installer. To distribute database devices, use separate file systems for the directories.

Database Memory 2.1 GB RAM (hard-coded)

3.4 Setup of Database Layout

NoteThe following sections apply especially to the installation of a production system.

When you plan your SAP system installation, it is essential to consider the setup of your database layout with regard to the distribution of, for example, SAP directories or database file systems, to disks. The distribution depends on your specific environment and you must take factors into consideration, such as storage consumption of the software components involved, safety requirements and expected workload.

Required File Systems for SAP ASE

This section lists the file systems that are required by the SAP ASE database as well as the permissions that you have to set.

NoteDuring the installation of your SAP system, you can specify the number and names of the sapdata directories. The installer allows to place several data or log devices in one sapdata or saplog folder. You can create additional sapdata and saplog directories before you start the installer. To distribute database devices, use separate file





systems for the directories. To ensure that your SAP system performs well in a production environment, you have to define and control the distribution of the database directories to physical disks. You do this by creating separate file systems manually for the directories listed in the following table:

Table 19

File System / Logical Volume: Description:

/sybase/<DBSID> SAP ASE software ($SYBASE)

Linux: Home directory for OS user on Linux

Size: at least 4 GB

/sybase/<DBSID>/sybsystem Location for devices master.dat, sybmgmtdb.dat,

sybsysdb.dat, sysprocs.datSize: 1 GB

/sybase/<DBSID>/sybtemp Location for device tempdbdev.datSize: 3 GB

/sybase/<DBSID>/saptemp Location for device saptempdbdev.datSize: 3 GB

/sybase/<DBSID>/sapdiag Location for devices containing the SAP tools database

(datasaptools_1.dat and logsaptools_1.datSize: 3 GB

/sybase/<DBSID>/sapdata_<n> Location for devices containing data (data<DBSID>_1.dat)


/sybase/<DBSID>/saplog_<n> Location for devices containing logs (log<DBSID>_1.dat)


NoteFor information about SAP file systems, see File Systems and Directories [page 57].

File System Permissions

The file systems and logical volumes must have the permissions and owner shown in the following table. They must be created before starting the installer. The installer then sets the required permissions and owners.

NoteYou can create the owners and groups manually if they do not exist. Otherwise, the installer creates them automatically.

Table 20

File System / Logical Volume Permissions Owner Group

/sybase/<DBSID> 750 syb<dbsid> sapsys

/sybase/<DBSID>/sybsystem

750 syb<dbsid> sapsys

/sybase/<DBSID>/sybtemp 750 syb<dbsid> sapsys

46



Planning



File System / Logical Volume Permissions Owner Group

/sybase/<DBSID>/saptemp 750 syb<dbsid> sapsys

/sybase/<DBSID>/sapdiag 750 syb<dbsid> sapsys

/sybase/<DBSID>/sapdata_<n>


/sybase/<DBSID>/saplog_<n>


Users and Groups

If it has not been created, the installer creates the user syb<dbsid>.

Linux: Group: sapsys (primary group)

3.5 SAP System Transport Host

The 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 it depends on your security requirements whether you want them to share a transport directory or whether you use separate directories.

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

More Information

● Required File Systems and Directories [page 57]

● See the SAP Library [page 13]:

Table 21

Release SAP Library Path


● SAP NetWeaver 7.3 including Enhancement Package 1

Solution Life Cycle Management Software Logistics Change and Transport System Change and Transport System –





● SAP NetWeaver 7.4 Overview Basics of the Change and Transport System Transport Management System – Concept


3.6 Planning the Switchover Cluster for High Availability

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

Prerequisites

You must first discuss switchover clusters with your hardware partner because this is a complex technical area. In particular, you need to choose a proprietary switchover product that works with your operating system.

We recommend that you read the following documentation before you start:

● Check the information and the installation guides that are available at scn.sap.com/docs/DOC-7848.

● The enqueue replication server (ERS) is essential for a high-availability system. You need one ERS for the ASCS installed in your system.

48



Planning

http://scn.sap.com/docs/DOC-7848

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.




Figure 8: Switchover Cluster

Constraints

This 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 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.End of: HA (UNIX) |

3.7 Diagnostics Agent – Specific Planning Steps

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.

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.

50



Planning


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.7.1 Connection Selection

Before 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 51].

● 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 52].

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.


3.7.2 Direct SAP Solution Manager Connection

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

Connect 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 35]

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

3.7.3 System Landscape Directory Registration

The 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 35].

52



Planning

4 Preparation

4.1 Preparation Checklist

This section includes the preparation steps that you have to perform for the following installation options:



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



1. You check that the required operating system users and groups [page 54] are created.

2. You set up file systems [page 57] 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 65].

4. If you want to install a high-availability system, you perform switchover preparations [page 66].

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

6. You install the SAP frontend software [page 66] on the desktop of the user.

7. You check that the required installation media [page 67] 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 145].

9. You continue with Installation [page 71] .


You 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 54] are created.

2. You set up file systems [page 57] and make sure that the required disk space is available for the directories to be created during the installation.

3. If you want to use virtual host names, you have to set the environment variable SAPINST_USE_HOSTNAME [page 65]. 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 75] this directory to your installation hosts.

5. You install the SAP frontend software [page 66] on the desktop of the user.

6. You check that the required installation media [page 67] are available.

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterprisePreparation



7. You continue with Installation [page 71] .

4.2 Creating Operating System Users and Groups

During 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.Only valid for: HA (UNIX) |

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

End of: HA (UNIX) |

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 <Database> Preparation Operating System Users and Groups . For more information, see Running the Installer [page 77].

● 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:

Table 22

Operating System

Action

AIX Proceed as described in SAP Note 323816.

HP-UX Check the output of command limit (if you use csh shell) or ulimit -a (if you use sh or ksh shell)

according to section OS Dependencies All Operating Systems of SAP Note 1704753.

Linux Check the output of command limit (if you use csh shell) or ulimit -a (if you use sh or ksh shell)


Solaris Check the output of command limit (if you use csh shell) or ulimit -a (if you use sh or ksh shell)


● All users must have identical environment settings. Any change to the environment – such as variables, or paths – is at your own responsibility.

54



Preparation





● If you have multiple operating system users with user ID (UID) 0, you must assign the sapinst group to all of them.

● Do not delete any shell initialization scripts in the home directory of the operating system users. This applies even if you do not intend to use the shells that these scripts are for.

● If you install an SAP system with instances distributed over several hosts, make sure that the following requirements are met:

○ The user ID (UID) and group ID (GID) of each operating system user must be unique and the same on each instance host which belongs to the same SAP system.

○ Make sure that the group ID of group sapinst is always different from the group ID of any other group (for example, of group sapsys) used during the installation.

For example, if you want to install an additional application server instance for an existing SAP system, you must make sure that the group ID of group sapinst created on the host of the additional application server instance is different from the group ID of any other group on the primary application server instance host of the existing SAP system.

○ If you use local operating system user accounts instead of central user management (for example, NIS), user <sapsid>adm, sapadm, and the database operating system user must have the same password on all hosts.

○ If you use local operating system user accounts, make sure that you install your SAP system in Custom mode and specify suitable IDs for user <sapsid>adm and group sapsys on all hosts. The IDs have to be the same on all hosts. If you choose Typical mode, you will not be asked to specify the user and group IDs.

● If operating system users already exist, make sure that they are assigned to group sapinst.

● If you create operating system users manually or use already existing operating system users, make sure that the home directory for each of these users is not the root directory ( / ) .

● Make sure that the home directory of user <sapsid>adm is not critical for recursive changes on permissions.

When operating system users are created by the installer, the permissions on the home directories of these users are changed recursively. This can cause unpredictable errors if you define a critical home directory.

For example, the home directory must not be / or /usr/sap.

● Only valid for: HP-UX |

To prevent terminal query errors in the <sapsid>adm environment, comment out the line eval 'tset -s -Q -m ':?hp' in the /etc/skel/.login script. For more information, see SAP Note 1038842.End of: HP-UX |


The installer chooses available operating system user IDs and group IDs unless you are installing an additional application server instance. On an additional application server instance you have to enter the same IDs as on the host of the primary application server instance.

If you have multiple operating system users with user ID (UID) 0, you must assign the sapinst group to all of them.

You can specify the name of the ABAP connect user (sap<sapsid>) independently from the SAP schema name during the dialog phase of the installer.

We recommend, however, that you keep the names of the connect user and the database schema identical in standard use cases.





Table 23: User and Groups of the Diagnostics Agent

User Primary Group Additional Group Comment

<dasid>adm sapsys sapinst Administrator for the Diagnostics Agent.

Table 24: User and Groups of the SAP Host Agent


sapadm sapsys – SAP Host Agent administrator

NoteIf sapadm does not exist, it is

created during the SAP Host Agent installation using /bin/false shell.

Make sure that /bin/false can

be used as a login shell.


Add /bin/false to the list of

valid login shells (attribute shells) in /etc/security/login.cfg.

End of: AIX |

Table 25: Users and Groups

User: Primary Group:

UNIX superuser root No primary group assigned by SAPinst (group sapinst is assigned as secondary group).

SAP system administrator <sapsid>adm sapsys (sapinst as secondary group)

syb<dbsid>

NoteOnly used on the database host.

sapsys (sapinst as secondary group)

Table 26: Groups and Members of the Diagnostics Agent User

Groups Members

sapsys <dasid>adm

sapinst <dasid>adm

Table 27: Groups and Members of the SAP Host Agent User

Groups Members

sapsys sapadm

sapinst sapadm

56



Preparation

4.3 Required File Systems and Directories

The following sections describe the directory structures for the SAP system, how to set up SAP file systems for the SAP system and, if required, raw devices on operating system level:

NoteThe installation of any SAP system does not require a special file system setup or separate partitions.

● SAP Directories [page 57]

● Performing Switchover Preparations for High Availability [page 66]

● Setting Up File Systems for High-Availability [page 62]

4.3.1 SAP Directories

Depending on the installation option you have chosen, the installer automatically creates the directories listed in the following figures and tables. Before running the installation, you have to set up the required file systems manually. In addition, you have to make sure that the required disk space for the directories to be installed is available on the relevant hard disks.

The installer creates the following types of directories:

● Physically shared directories

● Logically shared directories

● Local directories

Directories of the SAP System

The figure below assumes that you have set up one file system for the SAP system mount directory <sapmnt> and one file system for the /usr/sap directory. However, you have to decide for which directories you want to set up separate file systems. If you do not set up any file system on your installation host, the installer creates all directories in the root directory (/ ).

The installer prompts you only for the <sapmnt> directory during the installation.

The following figure shows the directory structure of the SAP system:




Figure 9: Directory Structure for an ABAP System

Every new installation of an ABAP standalone system is Unicode (directory uc – Unicode).

Physically Shared Directories (SAP System)

Physically shared directories reside on the global host and are shared by Network File System (NFS). The installer creates the following directories:

● The directory /<sapmnt>/<SAPSID>, which contains SAP kernel and related files, is created on the first installation host. Normally, the first installation host is the host on which the central services instance is to run, but you can also choose another host for /<sapmnt>/<SAPSID>.

You need to manually share this directory with Network File System (NFS) and – for a distributed system such as a high-availability system or a system with additional application server instances – mount it from the other installation hosts.

The installer creates the following shared subdirectories in /<sapmnt>/<SAPSID> during the SAP system installation. If you install an SAP system with instances distributed over several hosts, you have to share these directories for all hosts with the same operating system (see Exporting and Mounting Global Directories [page 76]):

○ globalContains globally shared data

○ profileContains the profiles of all instances

○ exeContains executable kernel programs. The kernel programs are replicated from directory <sapmnt>/<SAPSID>/exe/uc/<platform> to the exe directories of each Unicode system instance.

● The directory /usr/sap/trans, which is the global transport directory.

58



Preparation

If you want to use an existing transport directory, you have to mount it before you install the relevant application server instance. Otherwise, the installer creates /usr/sap/trans locally.

For more information, see Exporting and Mounting the Global Transport Directory [page 75].

Table 28: Physically Shared SAP Directories

Directory Required Minimum Disk Space

/<sapmnt>/SAPSID>

● SAP NetWeaver BW server only: Minimum 3 GB

● Other installations: Minimum 1 GB

/usr/sap/trans This value heavily depends on the use of your SAP system.

For production systems, we recommend to use as much free space as available (at least 2.0 GB), because the space requirement normally grows dynamically.

For the installation, it is sufficient to use 1 GB for each SAP system instance. You can enlarge the file system afterwards.

Logically Shared Directories (SAP System)

Logically shared directories reside on the local hosts with symbolic links to the global host. The installer creates the directory /usr/sap/<SAPSID>/SYS on each host.

This directory contains the following symbolic links to physically shared directories:

● Symbolic link profile points to /<sapmnt>/<SAPSID>/profile● Symbolic link global points to /<sapmnt>/<SAPSID>/global

This directory contains the exe subdirectory with symbolic links pointing to the corresponding subdirectories of /<sapmnt>/<SAPSID>/exe on the SAP global host:

● Symbolic link uc (for Unicode) points to /<sapmnt>/<SAPSID>/exe/uc● Symbolic link run points to another symbolic link /usr/sap/<SAPSID>/SYS/exe/dbg in the same directory,

and symbolic link dbg at last points to /<sapmnt>/<SAPSID>/exe/uc/<platform>Whenever a local instance is started, the sapcpe program checks the executables against those in the logically shared directories and, if necessary, replicates them to the local instance.

The installer uses sapcpe to replicate the kernel automatically from /usr/sap/<SAPSID>/SYS/exe/run/DIR_CT_RUN to /usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP system instance, where <INSTANCE> is either DVEBMGS<Instance_Number> (primary application server instance) or D<Instance_Number> (additional application server instance)

Local Directories (SAP System)

The installer also creates local directories that reside on the local hosts. The directory /usr/sap/<SAPSID> contains files for the operation of a local instance as well as symbolic links to the data for one system. This directory is physically located on each host in the SAP system and contains the following subdirectories:

● SYS

NoteThe subdirectories of /usr/sap/<SAPSID>/SYS have symbolic links to the corresponding subdirectories of /<sapmnt>/<SAPSID>, as shown in the figure above.

● Instance-specific directories with the following names:




○ The directory of the primary application server instance is called DVEBMGS<Instance_Number>, where <Instance_Number> is the instance number.

○ The directory of an additional application server instance is called D<Instance_Number>, where <Instance_Number> is the instance number.

● The directory of the central services instance for ABAP (ASCS instance) is called ASCS<Instance_Number>, where <Instance_Number> is the instance number.

● The directory of an enqueue replication server instance (ERS instance) is called ERS<Instance_Number>, where <Instance_Number> is the instance number.

If you install a high-availability system, you must install an ERS instance for the ASCS instance.

Table 29: Local SAP Directories

Directory Description Required Minimum Disk Space

/usr/sap/<SAPSID>/DVEBMGS<Instance_Number>

Primary application server instance directory

● SAP Business Warehouse server only: Minimum 12 GB


/usr/sap/<SAPSID>/D<Instance_Number>

Additional application server instance directory

● SAP Business Warehouse server only: Minimum 12 GB


/usr/sap/<SAPSID>/ASCS<Instance_Number>

ABAP central services instance (ASCS) directory (high-availability only)

1 GB

/usr/sap/<SAPSID>/ERS<Instance_Number>

Enqueue replication server instance (ERS) directory for the ASCS (high-availability only)

1 GB

Directories of the Diagnostics Agent

For the Diagnostics Agent the installer creates the following types of directories:

● Logically shared directories

● Local directories

Details are shown in the following figure.

60



Preparation

Figure 10: Directory Structure for the Diagnostics Agent

The Diagnostics Agent directory /usr/sap/<DASID> contains the following subdirectories:

● SYS, which is a logically shared directory

● SMDA<Instance_Number>, which is a local directory

CautionSince traces for the instance are created in this directory, sufficient space must be available in this directory.

Logically Shared Directories (Diagnostics Agent)

The logically shared directory SYS contains the following subdirectories:

● exeContains executable kernel programs

● globalContains globally shared data

● profileContains the profiles of the Diagnostics Agent instance

Local Directories (Diagnostics Agent)

The (local) instance directory of the Diagnostics Agent instance is called SMDA<Instance_Number>. It contains the instance-specific data of the Diagnostics Agent and has following subdirectories:

● scriptContains the smdsetup script

● SMDAgentContains the Diagnostics Agent software and properties files

● exeContains executable kernel programs




● workContains log files

Directories of the SAP Host Agent

The SAP Host Agent has only local directories as shown in the following figure:

Figure 11: Directory Structure for the SAP Host Agent

Local Directories (SAP Host Agent)

The SAP Host Agent directory /usr/sap/hostctrl requires 100 MB of disk space. It contains the following subdirectories:

● exeContains the profile host_profile

● workWorking directory of the SAP Host Agent

4.3.2 Setting Up File Systems for a High-Availability System

Third-party technology is used to make the SAP directories available to the SAP system. The technologies of choice are NFS, shared disks, and cluster file system. If you have decided to use a high-availability (HA) solution for your SAP system, make sure that you properly address the HA requirements of the SAP file systems in your SAP environment with the HA partner of your choice.

From the perspective of an SAP application, there are the following types of SAP Directories [page 57]:

● Physically shared directories: /<sapmnt>/<SAPSID> and /usr/sap/trans● Logically shared directories that are bound to a node such as /usr/sap with the following local directories:

62



Preparation

○ /usr/sap/<SAPSID>○ /usr/sap/<SAPSID>/SYS○ /usr/sap/hostctrl

● Local directories that contain the SAP instances such as /usr/sap/<SAPSID>/ASCS<InstanceNumber>

Prerequisites

You have already installed the hardware – that is, hosts, disks, and network – and decided how to distribute the database, SAP instances, and – if required – Network File System (NFS) server over the cluster nodes (that is, over the host machines). For more information, see Planning the Switchover Cluster [page 48] and contact your HA partner.

Procedure

1. Create the file systems or raw partitions for the SAP instances you can switch over in such a way that the content can be made available to all nodes that can run the service. At least the ABAP central services (ASCS) instance must be part of the switchover cluster.

The SAP directories /<sapmnt>/<SAPSID> and /usr/sap/trans are usually mounted from a Network File System (NFS). However, an SAP instance directory /usr/sap/<SAPSID>/<Instance_Type><Instance_Number> that you want to prepare for HA has to be always mounted on the cluster node currently running the instance. Do not mount such directories with NFS.

Therefore, if the host running the primary application server instance is not the NFS server host, you might have to mount the file systems for /sapmnt/<SAPSID> and /usr/sap/trans on different physical disks from the file system for /usr/sap/<SAPSID>/<Instance_Type><Instance_Number>.

CautionTo start or stop an SAP instance, you have to do one of the following:

○ Make the physically shared SAP directories under /<sapmnt>/<SAPSID>/ available to the server beforehand.

○ Replace the links in /usr/sap/<SAPSID>/SYS by a physical copy.

Consult your HA partner to clarify the best solution for the cluster software.

2. Use the following approach for the file system for the /usr/sap/<SAPSID> directory:

The /usr/sap/<SAPSID> directory contains at least two subdirectories (see also SAP Directories [page 57]):

○ SYS, which contains links to the central directory /sapmnt/<SAPSID>○ <Instance_Type><Instance_Number> – where the name is defined by the type of services and the

application server number:

○ DVEBMGS<Instance_Number> – which contains data for the primary application server instance

○ D<Instance_Number> – which contains data for an additional application server instance

○ ASCS<Instance_Number> – which contains data for the ABAP central services instance

Only <Instance_Type><Instance_Number> directories need to be migrated with the SAP instances during the switchover.




Therefore, instead of /usr/sap/<SAPSID>, create a file system for /usr/sap/<SAPSID>/<Instance_Type><Instance_Number> with the usual <> substitutions.

The instance-specific directory name for the central services instance for ABAP is normally ASCS<Instance_Number>. Migrating only these directories avoids mount conflicts when switching over to a node on which another application server instance is already running. The ASCS<Instance_Number> directory can join the /usr/sap/<SAPSID> tree instead of mounting on top of it.

NoteThis approach becomes increasingly important when you want to cluster the central services instances with other local instances running on the cluster hosts outside the control of the switchover software. This applies to the Enqueue Replication Server (ERS) and additional ABAP or Java application server instances. The result is a more efficient use of resources. Use this approach for integrated installations of the application server with ABAP and Java stacks.

3. You assign the local (not switching) file systems to permanent mount points.

4. You assign the shared file systems as documented by your HA partner.

ExampleThe graphic below shows an example of the file systems and disks in an HA setup

Note that this is only an example. For more information on a setup that meets your needs, consult your HA partner.

64



Preparation

Figure 12: File Systems and Disks in an HA Setup


More Information

For more information about how to set up file systems and raw devices, see Setting Up File Systems and Raw Devices for HP-UX [page 131].End of: HP-UX |

4.4 Using Virtual Host Names

You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to hide their physical network identities from each other. This can be useful when quickly moving SAP servers or complete server landscapes to alternative hardware without having to reinstall or reconfigure.Only valid for: HA (UNIX) |

If you want to install a high-availability (HA) system [page 17], you need the virtual host name when you install the ASCS instance into a cluster.End of: HA (UNIX) |




Prerequisites

Make sure that the virtual host name can be correctly resolved in your Domain Name System (DNS) setup.

Procedure

Proceed as described in SAP Note 962955.Only valid for: HA (UNIX) |

4.5 Performing Switchover Preparations for High Availability

To be able to use the required virtual host names [page 65], you have to set the installer property SAPINST_USE_HOSTNAME to specify the required virtual host name before you start the installer. For more information, see Running the Installer [page 77].

Procedure

Assign the virtual IP addresses and host names for the ASCS instance, and (if required) NFS to appropriate failover groups.

NoteFor more information on virtual addresses and virtual host names and how to assign resources to failover groups, ask your HA partner.

End of: HA (UNIX) |

4.6 Installing the SAP Front-End Software

Before you start the installation, make sure that the SAP front-end software is installed on at least one computer in your system environment to be able to log on to the SAP system after the installation has finished.

Procedure

1. Check SAP Note 147519 for the recommended SAP front-end release.

2. Install the SAP front-end software as described in the documentation SAP Front End Installation Guide - <Release> at:

service.sap.com/installNW73 Installation - Clients

66



Preparation




4.7 Preparing the Installation Media

This section describes how to prepare the installation media, which are available as follows:

● The software provisioning manager 1.0 archive containing the installer.

You always have to download the latest version of the software provisioning manager 1.0 archive.

● The media containing the software to be installed, which are available as follows:

○ You normally obtain the physical installation media as part of the installation package.

○ You can also download the installation media apart from the software provisioning manager 1.0 archive from SAP Service Marketplace, as described at the end of this section.

For more information about the required media, see SAP Note 1680045.

Prerequisites

Make sure the latest version of the SAPCAR archiving tool is available on each installation host.

You require the SAPCAR archiving tool to be able to unpack software component archives (*.SAR files) which is the format of software life-cycle media and tools that you can download from the SAP software distribution center.

If required, you can download the latest version of SAPCAR from:

service.sap.com/swdc Support Packages and Patches A - Z Index S SAPCAR .

For more information about SAPCAR, see SAP Note 212876.

Procedure

1. Identify the required media for your installation [page 15] as listed below.

Every installation of an SAP system on SAP Adaptive Server Enterprise is Unicode!

Table 30

SAP Instance Installation

Required Software Packages from Installation Media

Central services instance for ABAP (ASCS instance)

● Software provisioning manager 1.0 archive SWPM10SP<Support_Package_Number>_<Version_Number>.SAR

● UC or NUC Kernel (folder K_<Version>_<N or U>_<OS>) where U means Unicode and N means non-Unicode.

NoteEvery new installation of an SAP system is Unicode. You can only use the non-Unicode kernel if you perform the system copy for a non-Unicode SAP system that has been upgraded to the current release.

Database instance









SAP Instance Installation

Required Software Packages from Installation Media


● Database software

● Installation Export (folders EXP*)

Enqueue Replication Server




Primary application server instance




● Database Client Software

Additional application server instance



NoteIf you install an additional application server instance in an existing non-Unicode system, the additional application server instance is created automatically as a non-Unicode instance. The installer checks whether a non-Unicode system exists and chooses the right executables for the system type.

● Database Client Software

68



Preparation

Table 31: SAP Host Agent (Separate Installation Only)

SAP Instance Installation Required Media

SAP Host Agent (separate installation only) ● Software provisioning manager 1.0 archive SWPM10SP<Support_Package_Number>_<Version_Number>.SAR

● UC Kernel (folder K_<Version>_U_<OS>) where

U means Unicode.

2. Make the installation media available on each installation host as follows:

1. Download the latest version of the software provisioning manager 1.0 archive SWPM10SP<Support_Package_Number>_<Version_Number>.SAR from:

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

2. Unpack the software provisioning manager 1.0 archive to a local directory using the following command:

SAPCAR -xvf <Path_To_Download_Directory>/<Archive>.SAR -R <Unpack_Directory>

NoteMake sure that all users have read permissions for the directory where you want to unpack the installer.

3. Make the media containing the software to be installed available.

You can do this in one of the following ways:

○ Copy the required media folders directly to the installation hosts.

○ Mount the media on a central media server that can be accessed from the installation hosts.

CautionIf you copy the media to disk, make sure that the paths to the destination location of the copied media do not contain any blanks.

Downloading Installation Media from SAP Service Marketplace

You normally obtain the installation media as part of the installation package from SAP.

However, you can also download installation media from the software distribution center on SAP Service Marketplace using one of the following paths:

NoteYou always have to download the software provisioning manager 1.0 archive from the software distribution center because you have to use the latest version (see above).

● service.sap.com/swdc Installations and Upgrades A - Z Index <First_Letter_Of_Your_Product><Your_Product> <Your_Product_Version>

● service.sap.com/swdc Installations and Upgrades Browse our Download Catalog <Your_Product><Your_Product_Version>







NoteIf you download installation media, note that they might be split into several files. In this case, you have to reassemble the required files after the download.

1. Create a download directory on the host where you want to run the installer.

2. Identify all download objects that belong to one installation medium according to one or both of the following:

○ Material number

All download objects that are part of an installation medium have the same material number and an individual sequence number:

<Material_Number>_<Sequence_Number>

Example51031387_151031387_2...

○ Title

All objects that are part of an installation medium have the same title, such as <Solution><Media_Name><OS> or <Database>RDBMS<OS> for database media.

3. Download the objects to the download directory.

4. To correctly re-combine the media that are split into small parts, unpack all parts into the same directory.

In the unpacking directory, the system creates a subdirectory with a short text describing the medium and copies the data into it. The data is now all in the correct directory, the same as on the medium that was physically produced. For more information, see SAP Note 1258173.

70



Preparation


5 Installation

5.1 Installation Checklist

This section includes the installation steps for the following:

● Standard system

● Distributed system

● High-availability system



Standard System

1. You run the installer [page 77] to install the SAP system.

NoteIn a standard system, all mandatory instances are installed on one host in one installation run.

2. You continue with Post-Installation [page 93].

Distributed System

1. If you want to share the transport directory trans from another system, you have to mount [page 75] it from this system. Otherwise, we recommend that you share the trans directory that is created during the installation of the primary application server instance.

2. On the ASCS instance host, you do the following:

1. You run the installer [page 77] to install the ABAP central services instance (ASCS instance).

2. You export global directories [page 76] in <sapmnt>/<SAPSID> to the database and primary application server instance host.

3. On the database instance host, you do the following:

1. You mount the global directories [page 76] in <sapmnt>/<SAPSID> that you exported from the SAP global host and – optionally – the trans directory that you exported [page 75] from the SAP transport host.

2. You run the installer [page 77] to install the database instance.

4. On the primary application server instance host, you do the following:

1. You mount the global directories [page 76] in <sapmnt>/<SAPSID> that you exported from the SAP global host.

2. You run the installer [page 77] to install the primary application server instance.

3. If you want to use the shared transport directory trans from another system, you also mount [page 75] this directory.


SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseInstallation



Graphical Overview

The following figure shows how you install the various instances in a distributed system:

Figure 13: Distribution of Instances in an ABAP System

High-Availability System

1. You make sure that you have already prepared the standby node, host B. You ought to have already made sure that it meets the hardware and software requirements and that it has all the necessary file systems, mount points, and (if required) Network File System (NFS).

This is described in Performing Switchover Preparations for High Availability [page 66] and Setting Up File Systems for a High Availability System [page 62]

2. If you want to share the transport directory trans from another system, you have to mount [page 75] it from this system. Otherwise we recommend that you share the trans directory that is created during the installation of the primary application server instance (see below).

3. You set up the switchover cluster infrastructure as follows:

NoteThe following procedure is an example. In this example, we use only one primary cluster node, host A, and one standby cluster node, host B.

If required, you can also install the ASCS instance and the SCS instance on different hosts.

In this case, you require:

○ At least one primary cluster node, host A1, for the primary node with the ASCS instance, and at least one primary cluster node, host A2, for the primary node with the SCS instance.

○ At least one standby node, host B1, for the primary node with the ASCS instance, and at least one standby node, host B2, for the primary node with the SCS instance.

72



Installation

1. You run the installer [page 77] to install the ABAP central services instance (ASCS instance) and the related enqueue replication server instance (ERS instance) using the virtual host name [page 65] on the primary cluster node, host A.

2. You export global directories [page 76] in <sapmnt>/<SAPSID> to the database host and to the primary application server instance host.

3. You prepare the standby cluster node, host B, making sure that it meets the Hardware and Software Requirements [page 24] and it has all the necessary file systems [page 62], mount points, and (if required) Network File System (NFS).

4. You set up the user environment on the standby node, host B:

○ You use the same user and group IDs as on the primary node.

○ You create the home directories of users and copy all files from the home directory of the primary node.

For more information about the required operating system users and groups, see Creating Operating System Users [page 54].

5. You configure the switchover software and test that switchover functions correctly to all standby nodes in the cluster.

6. You repeat the following steps until you have finished installing the enqueue replication server (ERS instance) on all nodes in the cluster:

1. You perform the switchover to a node where you want to install the enqueue replication server instance (ERS instance) for the ASCS instance.

2. You run the installer [page 77] to install the enqueue replication server instance (ERS instance) for the ASCS instance on the standby node, host B.

4. On the database instance host, you do the following:

RecommendationWe recommend that the database instance is part of the hardware cluster or of any other proprietary high-availability solution for the database.

1. You make available the global directories in <sapmnt>/<SAPSID> from the switchover cluster infrastructure and – optionally – from the SAP transport host.

2. You run the installer [page 77] to install the database instance on the database instance host.

5. On the primary application server instance host, you do the following:

NoteIn a high-availability installation, the primary application server instance does not need to be part of the cluster because it is no longer a single point of failure (SPOF). The SPOF is now in the central services instance (SCS instance), which is protected by the cluster.

In a high-availability installation, the primary application server instance does not need to be part of the cluster because it is no longer a single point of failure (SPOF). The SPOF is now in the ABAP central services instance (ASCS instance), which is protected by the cluster.

In a high-availability installation, the primary application server instance does not need to be part of the cluster because it is no longer a single point of failure (SPOF). The SPOF is now in the central services instances (SCS instance and ASCS instance), which are protected by the cluster.

1. You mount the global directories [page 76] in <sapmnt>/<SAPSID> that you exported from the switchover cluster infrastructure.

2. You run the installer [page 77] to install the primary application server instance.




3. If you want to use the shared transport directory trans from another system, you also mount [page 75] this directory (see above).

6. We recommend you to install additional application server (AS) instances to create redundancy.

The AS instances are not a SPOF. Therefore, do not include these instances in the cluster.


Graphical Overview

The following figure provides an overview of how you install the various instances in a high-availability installation:

Figure 14: Distribution of Instances in a High-Availability ABAP System


Installation Steps for Additional Application Server Instances for a Standard System

1. On the main host on which your SAP system runs, you export global directories in <sapmnt>/<SAPSID> to the database and primary application server instance host.

2. On every additional application server instance host, you do the following:


2. You run the installer [page 77] to install the additional application server instance.


Installation Steps for an Application Server Instance for a Distributed System


74



Installation

2. On the SAP global host, you export global directories in <sapmnt>/<SAPSID> to the database and primary application server instance host.




3. If you want to use the shared transport directory trans from another system, also mount [page 75] this directory.


Installation Steps for an Additional Application Server Instance for a High-Availability System


2. On the primary node, host A, of the switchover cluster infrastructure, you export global directories in <sapmnt>/<SAPSID> to every additional application server instance host.




3. If you want to use the shared transport directory trans from another system, you also mount [page 75] this directory.


5.2 Exporting and Mounting the Transport Directory

Every SAP system must be assigned to a transport directory. All application server instances of an SAP system must point to the same transport directory. Multiple SAP system can use the same transport directory. However, it is not required to have one global transport directory in your SAP system landscape. Depending on your security requirements you must decide how you want to set up the transport directories in your landscape. Systems with lower security requirements can share a transport directory (DEV, QA, for example). For systems with higher security requirements (PROD, for example), you might want to have a separate transport directory.

The transport directory is used by the Change and Transport System (CTS). The CTS helps you to organize development projects, and then transport the changes between the SAP systems in your system landscape.

For more information, see the SAP Library [page 13] at:

Table 32





Function-Oriented View Application Server Application Server ABAP Administration of Application Server ABAPChange and Transport System Change and Transport System - Overview Basics of the Change and Transport System Transport Management System - Concept




Consider the following:

● If the transport directory already exists, make sure that it is exported on the transport directory host and mount it on the SAP instance installation host.

● If the transport directory does not exist, proceed as follows:

○ Create the transport directory (either on the host where the primary application server instance is running or on a file server).

○ Export it on the transport directory host.

○ If you did not create the transport directory on your SAP instance installation host, mount it there.

Procedure

Exporting the Transport Directory

1. Log on as user root to the host where the transport directory /usr/sap/trans resides.

2. Make sure that /usr/sap/trans belongs to the group sapsys and to the user root.

3. If not already done, export the directory using Network File System (NFS).

Mounting the Transport Directory

NoteIf the transport directory resides on your local SAP instance installation host, you do not need to mount it.

1. Log on as user root to the host of the primary or additional application server instance, where /usr/sap/trans is to be mounted.

2. Create the mount point /usr/sap/trans.

3. Mount /usr/sap/trans using Network File System (NFS) from the exporting host.


More Information

If you need information about how to export and mount directories, see Exporting and Mounting Directories via NFS for HP-UX [page 135].End of: HP-UX |

5.3 Exporting and Mounting Global Directories

If you install a database or an additional application server instance on a host other than the SAP Global host, mount global directories from the SAP Global host.

NoteThere is no need to create the directories prior to the installation when you install a primary application server instance. The global directories must be exported only if you install additional application server instances.

76



Installation

Prerequisites

If you want to install the executables locally instead of sharing them, do not mount the exe directory with Network File System (NFS). Instead, create <sapmnt>/<SAPSID>/exe as a local directory (not a link) with a minimum of 1.5 GB free space.

Procedure

1. Log on to the SAP Global host as user root and export the following directories with root access to the host where you want to install the new instance:

<sapmnt>/<SAPSID>/exe<sapmnt>/<SAPSID>/profile<sapmnt>/<SAPSID>/globalMake sure that the user root of the host where you want to install the new instance can access the exported directories.

CautionMake sure that the transport directory is mounted on every host where you want to install an SAP instance. Otherwise, the installation fails.

For more information, see Exporting and Mounting the Transport Directory [page 75].

2. Log on to the host of the new instance that you want to install as user root.

3. Create the following mount points and mount them from the SAP Global host:

<sapmnt>/<SAPSID>/exe<sapmnt>/<SAPSID>/profile<sapmnt>/<SAPSID>/global

CautionMake sure that the mount points under /<sapmnt>/<SAPSID>/ are permanent. Otherwise automatic start of the instance services does not work when you reboot the system.


More Information

If you need information about how to export and mount directories, see Exporting and Mounting Directories via NFS for HP-UX [page 135].End of: HP-UX |

5.4 Running the Installer

This section describes how to run the installation tool software provisioning manager 1.0 (the “installer” for short). Software provisioning manager 1.0 includes a GUI client and a GUI server, which both use Java. In the following, GUI client and GUI server are called the “installer GUI”.




This procedure describes an installation where the installer and the installer GUI are running on the same host.

If you need to see the installation on a remote display, we recommend that you perform a remote installation [page 86], where the installer GUI is running on a separate host from the installer.

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809.

Prerequisites

● We recommend that you use the csh shell for the installation with the installer. If you want to use another shell, make sure that you have read SAP Note 202227.

The installer uses csh scripts during the installation to obtain the environment for user <sapsid>adm. This is also true if user <sapsid>adm already exists from an earlier SAP system installation, and the shell of this user is not csh. Before you start the installer, execute the following command as user <sapsid>adm to make sure that the csh scripts are up-to-date:

/bin/csh -c "source /home/<sapsid>adm/.cshrc;env"● Make sure that your operating system does not delete the contents of the temporary directory /tmp or the

contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry.

Make sure that the temporary directory has the permissions 777.

● Make sure that you have at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the installer executables. If you cannot provide 300 MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or TMPDIR to another directory with 300 MB free space for the installer executables.

You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation directory as described in section Useful Information About the Installer [page 83].

● Make sure that your DISPLAY environment variable is set to <Host_Name>:0.0, where <Host_Name> is the host on which you want to display the installer GUI.

You can set values for the DISPLAY environment variables as follows:

Table 33

Shell Used Command

Bourne shell (sh) DISPLAY=<Host_Name>:0.0export DISPLAY

C shell (csh) setenv DISPLAY <Host_Name>:0.0

Korn shell (ksh) export DISPLAY=<Host_Name>:0.0

● Make sure that umask is set to 022 for user root.

As user root, enter the following command: umask 022● Make sure that the limits for user root are set correctly:

Table 34

Operating System

Action

AIX Proceed as described in SAP Note 323816.

78



Installation




Operating System

Action

HP-UX Check the output of command limit (if you use csh shell) or ulimit -a (if you use sh or ksh shell)


Linux Check the output of command limit (if you use csh shell) or ulimit -a (if you use sh or ksh shell)


Solaris Check the output of command limit (if you use csh shell) or ulimit -a (if you use sh or ksh shell)


● Make sure that you have defined the most important SAP system parameters as described in Basic SAP System Installation Parameters [page 35] before you start the installation.

● Check that your installation host meets the requirements for the installation options that you want to install.

For more information, see Running the Prerequisite Checker [page 24].

● If you want to install an additional application server instance in an existing SAP system, make sure that:

○ There is exactly one entry in the /usr/sap/sapservices file for each SAP instance installed on this host. Be sure to check that the entry refers to the correct profile.

○ There are no profile backup files with an underscore “_” in their profile name. If so, replace the “_” with a “.”.

ExampleRename /usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2_D20081204 to /usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2.D20081204.

Procedure

1. Log on to the installation host as user root.

CautionDo not use an existing <sapsid>adm user.

CautionMake sure that the root user has not set any environment variables for a different SAP system or database.

2. Make the installation media available. For more information, see Preparing the Installation Media [page 67].

RecommendationMake the installation media locally available. For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.







Only valid for: Solaris |

NoteIf you mount installation media, make sure that you do this with option nomaplcase.

End of: Solaris |

3. Note

If you want to use a virtual host name, start the installer with the SAPINST_USE_HOSTNAME property as follows:

<Path_To_Unpack_Directory>/sapinst SAPINST_USE_HOSTNAME=<Virtual_Host_Name>For more information, see Using Virtual Host Names [page 65].

CautionMake sure that the installation directory is not mounted with NFS, otherwise there might be problems when the Java Virtual Machine is started.

4. On the Welcome screen, choose the required option:

○ Perform preparations

Go to one of the following:

○ Go to Generic Installation Options and choose the required task:

Table 35

Generic Installation Options Remarks

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. It is recommended to check the software integrity by performing a digital signature check for downloaded media and packages before using it with software provisioning manager.

For more information, see SAP Note 1979965

○ Go to Generic Installation Options <Database> Preparations and choose the required task:

Table 36

Preparations Remarks

LDAP Registration Sets up LDAP support for an application server instance

For more information about LDAP and Active Directory, see Integration of LDAP Directory Services [page 123].

SAP Host Agent Installs a standalone SAP Host Agent. For more information, see Standalone SAP Host Agent [page 22].


Allows you to use global accounts that are configured on a separate host

Run this installation option before you start the installation of the SAP system.

○ Go to <Product> <Database> Preparations and choose the required task:

80



Installation


Table 37

Preparations Remarks

Prerequisites Check Checks your hardware and software requirements before you start the installation. For more information, see Running the Prerequisites Checker in Standalone Mode [page 24].

○ Install an SAP system:

To install an SAP system based on SAP NetWeaver application server ABAP, choose <Product><Database> SAP Systems Application Server ABAP <System_Variant> .

You can install the following system variants:

Table 38

System Variants Remarks

Standard System Installs an SAP system with all mandatory instances on one host

Distributed System Installs an SAP system with all mandatory instances on different hosts

Perform the installation options exactly in the order they appear. You have to restart the installer on the relevant host for each installation option.

High-Availability System Installs a high-availability SAP system with all mandatory instances on different hosts

Perform the installation options exactly in the order they appear. You have to restart the installer on the relevant host for each installation option.

○ Perform other tasks or install additional components

Go to one of the following:

○ Go to <Product> <Database> and choose the required task:

Table 39

Other Options Remarks

Additional SAP System Instances

● Additional Application Server Instance:

Installs one or more additional application server instances

● Split Off ASCS Instance from Existing Primary Application Server Instance:

Splits off a central services instance for ABAP (ASCS) from the primary application server instance of an existing ABAP system or ABAP+Java (dual-stack) system. For more information, see Splitting Off an ABAP Central Services Instance from an Existing Primary Application Server Instance [page 120].

○ Go to Generic Installation Options and choose the required task:

Table 40

Other Options Remarks

<Database> Uninstall Choose this option to uninstall your SAP system, standalone engines, or optional standalone units.

For more information, see Deleting an SAP System or Single Instances [page 146].

5. Choose Next.




6. Follow the instructions on the installer screens and enter the required parameters.

NoteTo find more information on each parameter during the input phase of the installation, position the cursor on the required parameter and press F1 .

After you have entered all requested input parameters, the installer displays the Parameter Summary screen. This screen shows both the parameters that you entered and those that the installer set by default. If required, you can revise the parameters before starting the installation.

7. To start the installation, choose Start.

The installer starts the installation and displays the progress of the installation. When the installation has finished, the installer shows the message: Execution of <Option_Name> has completed.


CautionIf you decided to use 02 as the instance number, the instance fails to start during the installation process. For more information about the cause, see the item Instance Number in Basic SAP System Installation Parameters [page 35]. You have to manually change the port number for report RSLGCOLL to continue with the installation.

Proceed as follows:

1. Go to directory /<sapmnt>/<SAPSID>/profile2. Edit DEFAULT.PFL.

3. Set the parameter rslg/collect_daemon/listen_port to a free port number.

End of: HP-UX |

8. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer has finished. Sometimes these remain in the temporary directory.

NoteIf there are errors with the extraction process of the installer, you can find the log file dev_selfex.out in the temporary directory.

RecommendationKeep all installation directories until you are sure that the system, including all instances, is completely and correctly installed. Once the system is completely and correctly installed, make a copy of the installation directories with all their contents and save it to a physically separate medium, such as an optical media or a USB drive separate from your installation hosts. This might be useful for analyzing issues occurring later when you use the system. For security reasons, do not keep installation directories on installation hosts, but make sure that you delete them after saving them separately.

9. We recommend that you delete all files in the directory <User_Home>/.sdtgui/.

10. If you copied the installer software to your hard disk, you can delete these files when the installation has successfully completed.

82



Installation

5.5 Additional Information About the Installer

The following sections provide additional information about the installer:

● Useful Information About the Installer [page 83]

● Interrupted Installation [page 84]

● Performing a Remote Installation [page 86]

● Starting the Installer GUI Separately [page 88]

● Running the Installer in Accessibility Mode [page 90]

● Entries in the Services File Created by the Installer [page 91]

● Troubleshooting with the Installer [page 91]

5.5.1 Useful Information About the Installer

● The installer creates the installation directory sapinst_instdir directly below the temporary directory. The installer finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environment variable. If no value is set for these variables, the installer uses /tmp as default installation directory.

If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR to the required directory before you start the installer.

Table 41

Shell Used Command

Bourne shell (sh) TEMP=<Directory>export TEMP

C shell (csh) setenv TEMP <Directory>

Korn shell (ksh) export TEMP=<Directory>

CautionMake sure that the installation directory is not mounted with NFS, otherwise there might be problems when the Java Virtual Machine is started.

● For each option, the installer creates a subdirectory located in the sapinst_instdir directory.

● The installer extracts itself to the temporary directory. These executables are deleted again after the installer has stopped running.

Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them.

The temporary directory also contains the log file dev_selfex.out from the extraction process, which might be useful if an error occurs.

CautionIf the installer cannot find a temporary directory, the installation terminates with the error FCO-00058.




● While the installer is running, the default port 21212 is used for communication between the installer GUI server and the installer GUI client. If this port is already in use, you see an error message.

In this case or if you want the installer to use a specific port, open a command prompt and change to the required directory to which you unpacked the software provisioning manager 1.0 archive.

Execute the sapinst executable with the following command line parameter:

GUISERVER_DIALOG_PORT=<Port_Number_Gui_Server_To_Gui_Client>● To see a list of all available installer properties, start the installer as described above with the option -p:

./sapinst -p● If you need to run the installer in accessibility mode, proceed as described in Running the Installer in Accessibility

Mode [page 90].

● If required, you can stop the installer by choosing SAPinst Cancel in the installer GUI menu.

NoteIf you need to terminate the installer, you can do this by pressing Ctrl + C .

● If you want to install an SAP system in unattended mode, see SAP Note 950619.

5.5.2 Interrupted Installation

The SAP system installation might be interrupted for one of the following reasons:

● An error occurred during the Define Parameters or Execute phase:

The installer does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

● You interrupted the installation by choosing Cancel in the SAPinst menu.

CautionIf you stop an option in the Execute phase, any system or component installed by this option is incomplete and not ready to be used. Any system or component uninstalled by this option is not completely uninstalled.

The following table describes the options in the dialog box:

Table 42

Option Definition

Retry The installer retries the installation from the point of failure without repeating any of the previous steps.

This is possible because the installer records the installation progress in the keydb.xml file.

We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry.

If the same or a different error occurs, the installer displays the same dialog box again.

Stop The installer stops the installation, closing the dialog box, the installer GUI, and the GUI server.

84



Installation


Option Definition

The installer records the installation progress in the keydb.xml file. Therefore, you

can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.

Continue The installer continues the installation from the current point.

View Log Access installation log files.

NoteYou can also terminate the installer by choosing Ctrl + C but we do not recommend this because it kills the process immediately.

Procedure

This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to continue an interrupted installation after an error situation.

1. Log on to your local UNIX host as user root.


2. Make sure that the installation media are still available on the installation host.

For more information, see Preparing the Installation Media [page 67].

RecommendationMake installation media locally available. For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.



End of: Solaris |

3. Restart the installer from the directory to which you unpacked the SWPM10SP<Support_Package_Number>_<Version_Number>.SAR file by executing the following command:

<Path_To_Unpack_Directory>/sapinst4. From the tree structure on the Welcome screen, select the installation option that you want to continue and

choose Next.

The What do you want to do? screen appears.

5. On the What do you want to do? screen, decide between the following alternatives and continue with Next:




Table 43

Alternative Behavior

Run a new option The installer does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installation-specific files to a backup directory. Afterwards, you can no longer continue the old installation option.

For the backup directory, the following naming convention is used:

log_<Day>_<Month>_<Year>_<Hours>_<Minutes>_<Seconds>

Examplelog_01_Oct_2008_13_47_56

NoteAll actions taken by the installation before you stopped it (like creating directories, or users) will not be revoked.

CautionThe installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

Continue with the old option The installer continues the interrupted installation from the point of failure.

5.5.3 Performing a Remote Installation

You use this procedure to install your SAP system on a remote host. In this case, the installer and the GUI server run on the remote host, and the installer GUI client (the “installer GUI” for short) runs on the local host. The local host is the host from which you control the installation with the installer GUI.

If your security policy requires that the person performing the installation by running the installer GUI on the local host is not allowed to know root credentials on the remote host, you can specify another operating system user for authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524.

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809.Only valid for: Linux;Windows |

You can run the installer GUI on a PC with 32-bit while the installer is running on a 64-bit installation host. For more information, see Starting the Installer GUI Separately [page 88].End of: Linux;Windows |

86



Installation



Prerequisites

● The remote host meets the prerequisites for starting the installer as described in Running the Installer [page 77].

● Both computers are in the same network and can ping each other.

To test this:

1. Log on to your remote host and enter the command: ping <Local_Host>2. Log on to the local host and enter the command: ping <Remote_Host>

● Make sure that the sapinst executable on the remote host and the sapinstgui executable on the local host have exactly the same version. You can check this by using the option -sfxver as described in the procedure below and in the procedure in Starting the Installer GUI Separately [page 88].

● If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER command line parameter, make sure that this user exists on the remote host.

Procedure

1. Log on to your remote host as user root.


2. Make the installation media available on the remote host.

RecommendationMake installation media locally available. For example, reading from media mounted with Network File System (NFS) might fail.



End of: Solaris |

3. Check the version of the sapinst executable by entering the following command:

<Path_To_Unpack_Directory>/sapinst -sfxverThe version of the sapinst executable must be exactly the same as the version of the sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 88]).

4. Start the installer from the directory to which you unpacked the software provisioning manager 1.0 archive by executing the following command:

<Path_To_Unpack_Directory>/sapinst -nogui

NoteIf you need to specify another operating system user for authentication purposes, enter the following command:




<Path_To_Unpack_Directory>/sapinst -nogui SAPINST_REMOTE_ACCESS_USER=<Specified_OS_User>

The installer now starts and waits for the connection to the installer GUI. You see the following at the command prompt:

guiengine: no GUI connected; waiting for a connection on host <Host_Name>, port <Port_Number> to continue with the installation

5. Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page 88].

5.5.4 Starting the Installer GUI Separately

You use this procedure to start the installer GUI separately. You might need to start the installer GUI separately in the following cases:

● You closed the installer GUI using File Exit from the installer menu while the installer is still running.

● You want to perform a remote installation, where the installer GUI runs on a different host from the installer. For more information, see Performing a Remote Installation [page 86].

● You want to run the installer in accessibility mode. In this case, you have to start the installer GUI separately on a Windows host as described below with the command line parameter -accessible.

For more information, see Running the Installer in Accessibility Mode [page 90].

Prerequisites

● The host on which you want to start the installer GUI meets the prerequisites for starting the installer as described in Running the Installer [page 77].

NoteIf you want to run the installer on a Windows host, make sure that you meet the prerequisites for the installer listed in the relevant Windows guide.

● Make sure that the sapinst executable on the remote host and the sapinstgui executable on the local host have exactly the same version. You can check this by using the option -sfxver as described in the procedure below and in the procedure in Performing a Remote Installation [page 86].

Procedure

In this procedure, the following variables are used: <Remote_Host> is the name of the remote host, and <Port_Number_Gui_Server_To_Gui_Client> is the port the GUI server uses to communicate with the GUI client (21212 by default).

NoteIf you want to run the installer GUI on a remote host, it is mandatory to start the installer using the -nogui property. If you have already started the installer without the -nogui property and want to run the GUI on a different host, you have to exit the installation process by choosing SAPinst Cancel and then follow the steps described in

88



Installation

Interrupted Installation [page 84]. Use the - nogui property to restart the installer and start the installer GUI on the intended host.

Starting the Installer GUI on Windows

1. Make the installer software available on the host on which you want to start the installer GUI.


2. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters:

○ If you want to perform a remote installation, proceed as follows:

1. Check the version of sapinstgui.exe by entering the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -sfxverThe version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also Performing a Remote Installation [page 86]).

2. Start the installer GUI by entering the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>

○ If you closed the installer GUI using File Exit and want to reconnect to the installer, proceed as follows:

1. If you are performing a local installation with the installer and the installer GUI running on the same host, execute the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -port <Port_Number_Gui_Server_To_Gui_Client>

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>

3. The installer GUI starts and connects to the installer.

Starting the Installer GUI on UNIX

1. Make the installer software available on the host on which you want to start the installer GUI.


2. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters:

○ If you want to perform a remote installation, proceed as follows:

1. Check the version of the sapinstgui executable by entering the following command:

<Path_To_Unpack_Directory>/sapinstgui -sfxverThe version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also Performing a Remote Installation [page 86]).

2. Start the installer GUI by entering the following command:

<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>

○ If you closed the installer GUI using File Exit and want to reconnect to the installer, proceed as follows:

1. If you are performing a local installation with the installer and the installer GUI running on the same host, execute the following command:

<Path_To_Unpack_Directory>/sapinstgui -port <Port_Number_Gui_Server_To_Gui_Client>




2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:

<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>

3. The installer GUI starts and connects to the installer.

5.5.5 Running the Installer in Accessibility Mode

You can also run the installer in accessibility mode. The following features are available:

● Keyboard access:

This feature is available for all operating systems.

● High-contrast color:

This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a remote installation with the installer GUI running on a Windows host.

● Custom font setting:

This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a remote installation with the installer GUI running on a Windows host.

Procedure

Activating and Adjusting Accessibility Settings on Windows

You first have to activate and adjust the relevant settings for the font size and color schemes before you start the installer or the installer GUI.

NoteThe following procedure applies for Windows Server 2008 and might be different when using another Windows operating system.

1. Right click on your Windows desktop and choose Personalize.

2. Choose Adjust font size (DPI) and choose Larger scale (120 DPI).

To define other font size schemes, choose Custom DPI.

3. In the right-hand pane, select Window Color and Appearance.

Select a color scheme from the Color scheme dropdown box.

To define your own color schemes, choose Advanced.

Running the Installer in Accessibility Mode

You perform a remote installation as follows:

1. Start the installer on the remote host by executing the following command from the command line as described in Performing a Remote Installation [page 86]:

./sapinst -nogui

90



Installation

2. Start the installer GUI on a local Windows host by executing the following command from the command line as described in Starting the Installer GUI Separately [page 88]:

sapinstgui.exe -accessible -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>

5.5.6 Entries in the Services File Created by the Installer

After the installation has completed, the installer has created the following entries in /etc/services:

sapdp<nn> = 32<nn>/tcpsapdp<nn>s = 47<nn>/tcpsapgw<nn> = 33<nn>/tcpsapgw<nn>s = 48<nn>/tcpsapms<SAPSID> = 36<nn>/tcp (unless you specified another value during the installation)

Note● <nn> is the instance number. There is a port created for every possible instance number, regardless of which

instance number you specified during the installation. For example, for sapgw<nn> = 33<nn>/tcp the following range of entries is created:

sapgw00 = 3300/tcpsapgw01 = 3301/tcpsapgw02 = 3302/tcp[...]sapgw98 = 3398/tcpsapgw99 = 3399/tcp

● If there is more than one entry for the same port number, this is not an error.

5.5.7 Troubleshooting with the Installer

This section tells you how to proceed when errors occur during the installation with the installer.

If an error occurs, the installer:

● Stops the installation

● Displays a dialog informing you about the error

Procedure

1. Check SAP Note 1548438 for known installer issues.

2. To view the log file, choose View Logs.

3. If an error occurs during the dialog or processing phase, do one of the following:





○ Try to solve the problem.

○ Abort the installation with Exit.

For more information, see Interrupted Installation [page 84].

○ Continue the installation by choosing Retry.

4. Check the log and trace files of the GUI server and the installer GUI in the directory <User_Home>/.sdtgui/ for errors.

○ If the GUI server or the installer GUI do not start, check the file sdtstart.err in the current <User_Home> directory.

○ If the installer GUI aborts during the installation without an error message, restart the installer GUI as described in Starting the Installer GUI Separately [page 88].

○ If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote Access of the installer GUI on Windows Workstations and you experience display problems such as missing repaints or refreshes, contact your X Server vendor. The vendor can give you information about whether this X Server supports Java Swing-based GUIs and also tell you about further requirements and restrictions. For more information, see SAP Note 1170809.

5. If you cannot resolve the problem, report an incident using component BC-INS.

For more information about using subcomponents of BC-INS, see SAP Note 1669327.

92



Installation



6 Post-Installation

6.1 Post-Installation Checklist

This section includes the post-installation steps that you have to perform for the following:






1. You perform post-installation steps for the operating system [page 94].

2. You check whether you can log on to the application server [page 94].

3. You perform the consistency check [page 95].

4. You install the SAP license [page 96].


You set up the licenses for high availability [page 97].End of: HA (UNIX) |

6. You configure the remote connection to SAP support [page 98].

7. You apply the latest kernel and Support Packages [page 98].

8. You install the SAP Online Documentation [page 98].

9. You configure the Transport Management System [page 101].

10. SAP Kernel Release 7.40 and Higher: You perform IP Multicast Configuration [page 99].

11. You ensure user security.

12. You perform a full installation backup [page 103].

13. You enable the database [page 102].

14. You check the Master Guide for your SAP NetWeaver application for further implementation and configuration steps.


1. You perform post-installation steps for the operating system [page 94].

2. You check whether you can log on to the additional application server instance [page 94].

3. You ensure user security.

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterprisePost-Installation



6.2 Performing Post-Installation Steps for the Operating System

You have to perform the following post-installation steps for the operating system.

Procedure

1. You check and if necessary modify the settings for the operating system users for your SAP system if they were created by the installer.

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

2. You set the required permissions for sapstartsrv and sapuxuserchk in the /<sapmnt>/<SAPSID>/exe, and /usr/sap/<SAPSID>/SYS/exe, and /usr/sap/<SAPSID>/<Instance_Name>/exe directories as described in SAP Note 927637.

See also Starting and Stopping SAP System Instances Using the SAP Management Console [page 138].

6.3 Logging On to the Application Server

You need to check that you can log on to the SAP system with the standard users, given in the table below.

Table 44: ABAP Users

User User Name Client

SAP system user SAP* 000, 001, 066

DDIC 000, 001

Prerequisites

● The SAP system is up and running.

● You have already installed a front end.

Procedure

Logging On to the ABAP Application Server

You access the application server ABAP using SAP Logon

1. Start SAP Logon on the host where you have installed the front end as follows:

○ SAP GUI for Windows:

○ Windows Server 2012 (R2):

1. Press Windows + Q , and enter SAP Logon in the Search field.

2. Choose SAP Logon.

○ Windows Server 2003 and Windows Server 2008 (R2):

Choose Start All Programs SAP Front End SAP Logon .

94




○ SAP GUI for Java:

○ Windows Server 2012 (R2):

1. Press Windows + Q , and enter SAP GUI for Java <Release>2. Choose SAP GUI for Java <Release>.

○ Windows Server 2003 and Windows Server 2008 (R2):

Choose Start All Programs SAP Clients SAP GUI for Java <Release> .

The SAP Logon appears.

NoteYou can alternatively enter the command guilogon in the SAP GUI installation directory to start SAP GUI for Java.

2. Create a logon entry for the newly installed system in the SAP Logon.

For more information about creating new logon entries, press F1 .

3. When you have created the entry, log on as user SAP* or DDIC.

6.4 Performing the Consistency Check

We recommend that you check the consistency of the newly installed SAP ABAP system. When logging on to the system for the first time, you need to trigger a consistency check manually. The function is then called automatically whenever you start the system or an application server.

The following checks are performed:

● Completeness of installation

● Version compatibility between the SAP release and the operating system

The initial consistency check determines whether:

○ The release number in the SAP kernel matches the release number defined in the database system

○ The character set specified in the SAP kernel matches the character set specified in the database system

○ Critical structure definitions that are defined in both the data dictionary and the SAP kernel are identical. The structures checked by this function include SYST, T100, TSTC, TDCT and TFDIR.

● Accessibility of the message server

● Availability of all work process types

● Information about the enqueue server and the update service

Prerequisites

● If the installation finished successfully, your SAP system should be up and running. Otherwise, start it as described in Starting and Stopping SAP System Instances [page 138].

● You have logged on to the SAP system [page 94].




Procedure

1. Perform a system check:

Call transaction SICK.

You should see the entry SAP System Check | no errors reported2. Perform a database check:

In the DBA Cockpit, check for missing tables or indexes by choosing Diagnostics →Missing Tables and Indexes.

6.5 Installing the SAP License

You must install a permanent SAP license. When you install your SAP system, a temporary license is automatically installed.

CautionBefore the temporary license expires, you must apply for a permanent license key from SAP.

We recommend that you apply for a permanent license key as soon as possible after installing your system.

Procedure

Install the SAP license as described in the SAP library [page 13] at:

Note

Table 45





Solution Life Cycle Management SAP Licenses

More Information

For more information about SAP license keys and how to obtain them, see service.sap.com/licensekey.

96



http://service.sap.com/licensekey


6.6 High Availability: Setting Up Licenses

SAP has implemented a license mechanism for switchover solutions and clustered environments. Your customer key is calculated on the basis of local information on the message server host. This is the host machine where the ABAP central services instance (ASCS instance) runs.

To be able to perform a switchover, the temporary license that is installed automatically with the ASCS instance is not sufficient. You first need to install a permanent license, which is determined by the hardware environment of the message server. Since SAP's high-availability (HA) solution stipulates two or more cluster nodes (host machines) where the message server is enabled to run, you have to order as many license keys [page 96] as you have cluster nodes.

When we receive confirmation from your vendor that you are implementing a switchover environment, we provide the required license keys for your system, one key for each machine.

Prerequisites

The SAP system is up and running.

Procedure

1. To find the hardware ID of the primary host, log on to any application server instance of the SAP system and call transaction SLICENSE.

2. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster and repeat the previous step.

Repeat this for all remaining nodes in the cluster.

3. To obtain the two license keys, enter the hardware IDs for each cluster node, where message server is enabled to run:

service.sap.com/licensekey

4. To import the files containing the two licenses, log on to any application server instance of the SAP system and call transaction SLICENSE.

5. Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster and repeat the previous step.

Repeat this for all remaining nodes in the cluster.

Result

The license is no longer a problem during switchover. This means you do not need to call saplicense in your switchover scripts.End of: HA (UNIX) |




http://service.sap.com/licensekey

6.7 Configuring the Remote Connection to SAP Support

SAP offers its customers access to support and a number of remote services such as the EarlyWatch Service or the GoingLive Service. Therefore, you have to set up a remote network connection to SAP. For more information, see SAP Service Marketplace at service.sap.com/remoteconnection.

6.8 Installing the SAP Online Documentation

SAP currently provides an HTML-based solution for the online documentation, including the Application Help, Glossary, Implementation Guide (IMG), and Release Notes. You can display the documentation with a Java-compatible Web browser on all front-end platforms supported by SAP.

Process

Install the SAP online documentation in your SAP system as described in the README.TXT file contained in the root directory of the online documentation media, delivered as part of the installation package.

6.9 Applying the Latest Kernel and Support Package Stacks

We strongly recommend that you apply the latest kernel and Support Package stacks from SAP Service Marketplace before you start configuring your SAP system.

For more information about release and roadmap information for the kernel versions and how this relates to SAP NetWeaver support packages, including important notes on downward compatibility and release dates, see the document Understanding Kernel Releases for the SAP NetWeaver AS ABAP at scn.sap.com/docs/DOC-54170.

Procedure

Download and apply the latest Kernel and Support Package stacks using the Software Update Manager (SUM) as described in the documentation Updating SAP Systems Using Software Update Manager 1.0 SP<Number> at:

service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation System Maintenance Updating SAP Systems Using Software Update Manager 1.0 SP<Number> Update of SAP Systems Using Software Update Manager (<ABAP Systems|ABAP+Java Systems|Java Systems>) <OS> <Database>If you want to update the kernel manually, proceed as described below:

1. Log on as user <sapsid>adm to the hosts of the SAP system instances to be updated.

2. Download the latest kernel for your operating system and database platform as described in SAP Note 19466.

3. Back up the kernel directory that is specified by the profile parameter DIR_CT_RUN.

4. Extract the SAR files of the kernel Support Packages of the target SP level to a temporary directory using the SAPCAR tool.

98



http://service.sap.com/remoteconnection


http://service.sap.com/sltoolset


5. Copy or move the extracted programs from the temporary directory to the local Kernel directory.

6. Adjust the ownership and permissions of the kernel binaries by entering the following command sequence (Execute the saproot.sh script that is located in the Kernel directory):

su - rootcd <Kernel_Directory>./saproot.sh <SAPSID>exit

6.10 SAP Kernel 7.40 and Higher: IP Multicast Configuration

Since SAP kernel release 7.40, the ABAP application server (AS ABAP) uses IP multicast datagrams with host local scope to wake up the internal processes (such as dispatcher, gateway, internet communication manager, work processes) when dispatching requests.

Since SAP kernel release 7.40 Patch Level (PL) 46 and 7.41 PL 13, the dispatcher checks during startup whether local IP multicast communication is working properly.

You have to adjust the network configuration of AS ABAP as described in SAP Note 1931675 to ensure that local IP multicast communication works properly.

6.11 Ensuring User Security

You need to ensure the security of the users that the installer created during the installation. The tables below at the end of this section list these users:

● Operating system users

● SAP system users

During the installation, the installer by default assigned the master password to all users created during the installation unless you specified other passwords.

If you change user passwords, be aware that SAP system users might exist in multiple SAP system clients (for example, if a user was copied as part of the client copy). Therefore, you need to change the passwords in all the relevant SAP system clients.

CautionThe installer applied the master password to users SAP* and DDIC only for SAP system clients 000 and 001, but not to users SAP*, DDIC, and EARLYWATCH in client 066.

Instead, the installer always assigns the following passwords to these users in client 066:

SAP*: 06071992

EARLYWATCH: support

See also Master Password in Basic SAP System Installation Parameters [page 35].





RecommendationUser ID and password are encoded only when transported across the network. Therefore, we recommend using encryption at the network layer, either by using the Secure Sockets Layer (SSL) protocol for HTTP connections or Secure Network Communications (SNC) for the SAP protocols dialog and RFC.

For more information, see:

help.sap.com SAP NetWeaver <Release> Application Help Function-Oriented View: English SecurityNetwork and Transport Layer Security

CautionMake sure that you perform this procedure before the newly installed SAP system goes into production. For security reasons, you also need to copy the installation directory to a separate, secure location – such as a DVD – and then delete the installation directory.

Procedure

For the users listed below, take the precautions described in the relevant SAP security guide, which you can find at service.sap.com/securityguide:

Operating System Users

After the installation, operating system users for SAP system, database, diagnostics agent, and host agent are available as listed in the following table:

Table 46

User: Primary Group:

UNIX superuser root No primary group assigned by the installer (group sapinst is assigned as secondary group).

SAP system administrator <sapsid>adm sapsys (sapinst as secondary group)

SAP System Users

After the installation, ABAP system users are available. The following table shows these users together with recommendations on how you can ensure the security of these users.

Table 47: ABAP Users

User User Name Comment

SAP system user SAP* User exists in at least SAP system clients 000, 001, and 066

CautionThis user has extensive authorizations. Make sure that you assign a secure password.

DDIC User exists in at least SAP system clients 000 and 001

100



http://help.sap.com

http://service.sap.com/securityguide

User User Name Comment

CautionThis user has extensive authorizations. Make sure that you assign a secure password.

EARLYWATCH User exists in at least SAP system client 066

SAPCPIC User exists in at least SAP system clients 000 and 001

More Information

For more information about managing ABAP users, see:

help.sap.com SAP NetWeaver <Release> Application Help Function-Oriented View: English SecurityIdentity Management Identity Management of the Application Server ABAP

6.12 Configuring the Change and Transport System

You have to perform some steps in the Transport Management System to be able to use the Change and Transport System.

Procedure

1. Call transaction STMS in the ABAP system to configure the domain controller in the Transport Management System (TMS).


Table 48





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

2. In addition, you must configure the system change options.


Table 49




Solution Life Cycle Management Software LogisticsChange and Transport System Transport Organizer (BC-




http://help.sap.com


● SAP NetWeaver 7.4 CTS-ORG) Requirements for Working with the Transport Organizer Setting the System Change Option

6.13 Enabling the Database

After the SAP system installation, you must enable the database. Proceed as follows:

1. Make sure that the version of your database is still supported. Refer to SAP Note 1554717.

2. Check if there are newer versions available. Refer to SAP Note 1590719.

3. You must enable the database for monitoring by setting up a Data Collection Framework (DCF) after the SAP system installation. The DCF provides a time-based collection and evaluation of performance, configuration, and space-related data. It consists of:

○ a set of tables holding history data

○ a set of stored procedures to collect data on a regular basis

These stored procedures are scheduled by the ASE job scheduler.

In your SAP system, call transaction DBACOCKPIT to start the DBA Cockpit. Calling the DBA Cockpit automatically checks the existence of the DCF.

RecommendationTo make sure that the DCF was set up correctly, we recommend that you go to the Collector Configuration screen to check the status of the DCF.

For more information, refer to the database administration guide. You can find the administration guide in the Service Marketplace: service.sap.com/instguides SAP NetWeaver SAP NetWeaver <Release>Operations Database-Specific Guides

4. Manually activate the Internet Communication Framework (ICF) service to ensure that the DBA Cockpit functions correctly. It is required to access Web Dynpro ABAP-based applications. It is not activated by default. Refer to SAP Note 1245200.

5. Apply the latest patches for the DBA Cockpit. Refer to SAP Note 1558958.

6. Set up Automatic Table Maintenance in the DBA Cockpit. For more information, refer to scn.sap.com/docs/DOC-15162.

7. Check whether the database configuration for an SAP installation complies with SAP's requirements and recommendations. Refer to SAP Note 1539124.

8. For systems with high load, refer to SAP Note 1722359.

9. Ensure that you are able to recover the ASE server and all the server databases that are required for running your SAP system. Refer to SAP Note 1585981.

102













6.14 Performing a Full Installation Backup

You must perform a full offline backup after the configuration of your SAP system. If required, you can also perform a full offline backup after the installation (recommended). In addition, we recommend you to regularly back up your database.

CautionMake sure that you fully back up your database so that you can recover it later if necessary.

The UNIX commands used in this procedure work on all hardware platforms. For more information about operating system-specific backup tools, see your operating system documentation.

You need to back up the following directories and files:

● All SAP-specific directories:

○ /usr/sap/<SAPSID>○ /usr/sap/trans○ <sapmnt>/<SAPSID>○ Home directory of the user <sapsid>adm

● All database-specific directories

● The root file system

This saves the structure of the system and all configuration files, such as file system size, logical volume manager configuration, and database configuration data.

NoteThis list is only valid for a standard installation.

Prerequisites

You have logged on [page 94] as user <sapsid>adm and stopped the SAP system and database [page 138].

Procedure


Use the backup tool of your choice, for example the HP DataProtector and refer to the backup software documentation. You can also use the standard UNIX commands as described below.End of: HP-UX |

Backing Up the Installation

1. Log on as user root.

2. Manually create a compressed tar archive that contains all installed files:

○ Saving to tape:

tar —cf — <file_system> | compress —c › <tape_device>○ Saving to the file system:




tar —cf — <file_system> | compress —c › ARCHIVENAME.tar.ZOnly valid for: Linux |

NoteYou can also execute the following command to manually create a compressed GNU tar archive that contains all installed files and save it to the file system:

tar —czf <ARCHIVENAME>.tgz <file_system>

End of: Linux |

Restoring Your Backup

If required, you can restore the data that you previously backed up.

CautionCheck for modifications in the existing parameter files before you overwrite them when restoring the backup.


2. Go to the location in your file system where you want to restore the backup image.

3. Restore the data with the following commands:

○ From tape:

cat <tape_device> | compress —cd | tar —xf —○ From the file system:

cat ARCHIVENAME.tar.Z | compress —cd | tar —xf —Only valid for: Linux |

NoteIf you want to restore the data from a GNU tar archive, you have to execute the following command:

tar —xzf <ARCHIVENAME>.tgz

End of: Linux |

104



7 Disaster Recovery Setup with SAP Replication Server

In the following chapters you will learn how to set up a disaster recovery solution using SAP ASE, the SAP Replication Server and the Disaster Recovery Agent Management utility. This solution is not designed to support high availability, reporting, or other solutions that might be supported by replication tools.

In a typical replication scenario, the SAP system updates data on the primary database. Transactions are replicated to the standby database by the replication software. In a failover scenario, the SAP application connections are switched to the standby database. Transactions generated on the standby database continue to be saved by the replication server until the primary database comes back online. Once the primary database returns to service, the saved standby database transactions are released and applied to the primary host. Both databases are resynchronized.

The replication architecture consists of the primary and the standby environments. The database and replication servers need to be run on the same hardware platform and operating system at both sites. The hosts can be virtual or physical machines, or a mix of both.

Figure 15: Disaster recovery solution using SAP ASE, the SAP Replication Server and the Disaster Recovery Agent Management utility

All components of an environment can run on the same host, but it is also possible to use several hosts. The Replication Server and Disaster Recovery Agent must run on the same host.

The installation and uninstallation processes require having the SAP system mount directory (/spmnt/<SAPSID>) available on that host.

For more information, refer to chapter Required File Systems and Directories [page 57].

Replication is set up to support a rebuild in both directions between the primary and the standby site, although only one direction is available at any one point in time. Three databases are replicated between the primary and the standby site:

● SAP application database

● saptools database

● SAP ASE master database

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseDisaster Recovery Setup with SAP Replication Server



The SAP Business Suite product must be installed with the SAP ASE database on the primary site. The SAP NetWeaver Application Server can be installed on the database host or a separate host. The standby database must be a copy of the database instance of the primary SAP system.

CautionThe disaster recovery setup with SAP Replication Server is only available for SAP Sybase ASE 15.7 and SAP Replication Server 15.7.1 SP 111 and higher.

CautionDo not enable a replication environment if you are not familiar with the SAP Replication Server product. Particularly in outage situations, the database log of the primary database can run out of space and the SAP System could face downtime as a result. Stopping the replication in an inappropriate manner may require rematerialization of the standby database.

Read SAP Note 1891560 before you start the installation. The SAP Note contains the most recent information on the installation, as well as corrections to the installation documentation.

7.1 Implementation Considerations

The standby database requires the same levels of protection and scheduled maintenance as the primary database. Periodic reorganizations, generation of statistics, and other housekeeping tasks are also required on the standby site. The standby site requires its own backup and recovery process. This includes disk-based file backup and recovery, as well as dump creation and archiving at database level.

As a result of the logical replication method, the standby database might need more device space than the primary site. Dump files from the primary host cannot be used for recovery of the standby site. Once replication begins, the physical attributes of the primary and standby databases are no longer equivalent and they can not share the same dump and load files for recovery.

During replication, additional information is written to the database transaction log for each database. The transaction log volume will increase by 40 to 50 %.

The master and saptools databases will always be replicated. It is not possible to exclude them.

CautionIf you plan to upgrade your SAP system, you have to take into account that you have to tear down the replication environment before the upgrade and to reinstall it after the upgrade.

7.2 Prerequisites

The following prerequisites must be fulfilled before you set up a disaster recovery solution:

Table 50

Area: Requirements:

Software The following software is required:

● SAP Sybase ASE 15.7.0 SP 110 and higher on the primary and standby hosts

106



Disaster Recovery Setup with SAP Replication Server


Area: Requirements:

● SAP Replication Server 15.7.1 SP 111 and higher

● Only valid for: AIX |

Operating system

Installation of fileset xlsmp.rte is required.

End of: AIX |

Hardware Database and replication server must use the same hardware platform. SAP recommends installing the replication server on a separate host to keep the impact on the database as low as possible.

Server Names The SAP ASE server name is based on the <SAPSID> value and is the same on both primary and standby

sites.

The SAP database name is the same on both sites.

Directories For an SAP installation, the replication environment must be installed in the following directory:

/sybase/<SID>_REPReserve at least 4 GB free space for software and configuration files.

The initial replication server partition file is placed in a folder at:

/sybase/<SID>_REP/repdata_1You can specify another folder for placing replication server partition files during installation. This allows distribution of disk I/O to several disks.

The initial size of the partition file should be at least factor 1.5 of the log size of the SAP application database. Reserve additional 2 GB for replication server usage in this folder.

TCP/IP ports In addition to the ASE TCP/IP ports, the following ports are required for the replication environment:

● Replication server: 4905

● Replication server system database: 4906

● Replication server system database replication agent: 4907

● DR agent RMI: 4908

● DR agent: 4909

The values for the TCP/IP ports are default values. It is possible to customize the port numbers.

Database Time Synchronization

Both primary and standby databases must have the same UTC time, otherwise the SAP application will not work properly, if the SAP system is using the standby database.

Database User The following users are required on both sites:

● sapsa● sapsso● Replication user (<SID>_maint)

● DR agent administrator (DR_admin)

The sapsa and sapsso logins and their passwords must be identical across both databases. The

replication user and the DR agent administrator are created by the SAP installer.

Be aware that the database user DR_admin is included in the secure storage of the SAP system, should

you want to change the password.




Area: Requirements:

Operating system user

The replication server and the DR agent are started with OS user syb<sid>.

7.3 Installing the Replication Environment

Perform the following installation steps to enable replication of an SAP system:

On the primary site:

1. Install a new SAP system or use an existing SAP source system.

2. Update the primary database to at least SAP Sybase ASE 15.7.0 SP110 and higher.

For more information, refer to SAP Note 1599814

3. Prepare the host that will run the replication server; update the OS libraries (if required for your platform).

4. Verify that the SAP system mount directory is available on the host that will run the replication server.

On the standby site:

1. Install an empty database instance on the standby site by using the installation option System Copy appropriate for the source SAP System. Choose the following installer option to create an empty database instance on the standby site:

SAP <product> SAP ASE System Copy Target System Distributed System Based on <AS>Database Instance

Choose the following options on the subsequent screens:

Table 51

Screen: Action:

SAP System > General Parameters Deselect Profiles are available.

SAP System > Database Select the installation method Homogeneous System Copy (SAP Sysbase ASE specific: Detach / Attach or Backup / Restore).

SAP ASE Database Load Method Select Load a database dump.

SAP ASE Database Dump Files Deselect Load database dump files from folder.

SAP ASE Database System Parameters Enter sizes for data and log database devices. The sizes should be at least as big as the ones from the source database server.

2. Prepare the host that will run the replication server; update the OS libraries (if required for your platform).

3. Verify that the SAP system mount directory is available on the host that will run the replication server.

4. Choose the following installer option to set up the replication software and start the DR agent:

Generic Installation Options SAP ASE Database Replication Setup of Replication Environment

Choose the following option:

108





Table 52

Screen: Action:

Replication System Parameters Deselect Configure replication environment.

NoteA configuration of the replication environment is possible if both primary and standby DR agents are ready.

On the primary host:

1. Choose the following installer option to set up the replication software, start the DR agent, and configure and activate replication (including database materialization):

Generic Installation Options SAP ASE Database Replication Setup of Replication Environment

Choose the following option:

Table 53

Screen: Action:

Replication System Parameters Select Configure replication environment.

2. Enter primary and standby database connection information.

3. Choose the materialization method for the various databases to be replicated.

The materialization step performs the initial copy of database content from one site to the other. Once completed, the replication software will maintain the data integrity of the target site by continuously applying changes that occur after completion of the materialization process.

The procedure for materialization is dependent on the type and size of the database being materialized (refer to the section Materializing Databases [page 109]).

The installer provides user interaction points that are used to synchronize the replication environment with the end user's manual dump and load activities.

7.3.1 Materializing Databases

This section describes how to materialize the following databases:

● Master database

● saptools database

● SAP database

Materialize the Master Database

Some information in the master database is site-specific. The only master database changes that are replicated are logins and roles for synchronizing users and credentials between the two sites. The DR agent facilitates materialization of the master database providing an automated materialization function.

The SAP installer materializes the master database automatically.

Materialize the 'saptools' Database

SAP recommends that you materialize the saptools database before the SAP database. The size of the database makes the materialization process relatively quick. During processing, there is further validation that all replication processes are working correctly.




Materialize the SAP Database

Large databases, such as the SAP application database, may not fit for automatic materialization. Their size requires timing and control that is best left to the attention of the administrator.

The SAP installer, by default, offers automatic database materialization through database dump and load. It is also possible to perform customized database materialization. The SAP installer provides user interaction points that are used to synchronize the replication environment with the end user's manual database actions.

To guarantee recoverability, read SAP Note 1585981.

7.3.1.1 Manual Materialization

The following methods are available:

● Using Database Dump and Load

● Using Transaction Dump and Load

● Using Snapshot Materialization

Using Database Dump and Load

If the database is small enough to support materialization using a single database dump file, the sequence for performing this process is as follows:

1. The installer stops for manual loading of the standby database. The primary database contains the necessary replication markers at this time.

2. Dump the database using the command dump database in the primary database server.

3. Copy the dump file to the standby site. You can use shared storage or FTP to make a copy of the dump file available at the standby site.

4. Load the SAP database using the ASE command load database in the standby database server.

5. Bring the standby database online using the command online database to make the database available for use in the standby system.

6. Confirm the installer dialog. The database will be checked for the dump marker.

Using Transaction Dump and Load

For large databases, it may be impractical to create a new dump of the entire database. Or the time required to dump the database might create a backlog of hours or days that replication would need to apply in order to get back in sync, thus creating an undesirable delay. To facilitate materialization for large databases, the replication-related activity can be deferred until such time as a series of database dump and subsequent transaction dumps have been loaded to the target database. Using this method, which includes transaction dumps, means that the replication delay and backlog are kept to a minimum.

The key difference in this technique is that the SAP installer is not involved until just before the last transaction dump is to be created. This allows the replication products to only address activity that occurs after the last transaction dump.

The sequence for performing materialization using transaction dump and load is as follows:

1. Dump the database on the primary database server. This can be a new dump or an existing dump if your system is already configured to perform periodic dumps of the entire database. If you are creating a new dump, use the ASE command dump database in the primary database server to create a dump of the entire database.

110





2. Load the database on the standby database server. Use the ASE command load database in the standby database server to load the dump.

3. Apply the transaction log dumps to the standby database with the ASE command load transaction using existing or new transaction log dumps.

4. The installer stops for manual loading of the standby database. The primary database now contains the necessary replication markers.

5. Dump the transaction log of the SAP database. Use the ASE command dump transaction in the primary database server to create the last dump of the ASE transaction log.

6. Load the last SAP transaction log dump.

7. Bring the standby database online using the ASE command online database to make the database available for use.


Using Snapshot Materialization

It is possible to materialize the standby database by using a snapshot of the primary database files with the help of a hardware mirroring product.

The sequence for performing materialization using database device files is as follows:

1. The installer stops for manual materialization of the standby database. The primary database contains the necessary replication markers at this time.

2. Quiesce the primary database.

Use the ASE command quiesce database to freeze the database by suspending all disk write activities.

3. Generate a snapshot of the database files. The action to be performed depends on the hardware mirror product you are using. You could also just copy the files, use shared storage or FTP to make a copy of the dump file available at the standby site.

4. Unquiesce the primary database.

Use the ASE command quiesce database … release to enable disk write activities on the primary database again.

5. Load the standby database with the snapshot files.

Use the ASE command mount database in the standby database to mount the database content.

6. Bring the database online using the ASE command online database in the standby database server to make the database available for use.


7.4 Starting and Stopping DR Agent and Replication Server

To be able to stop and start the DR Agent and the replication server, you must have the credentials of OS user syb<sid>.

Connecting to the DR Agent

Although there are two DR agents (one in primary and another in the standby environment), you will only need to enter commands at one of the DR agents. The DR agents can connect to each other in order to share configuration




information or to execute any activity that requires local access to the host. To set up and monitor replication, log on to the DR agent on the primary environment.

Use the DR agent’s host and port and the DR agent administrator’s security credentials to establish a connection to the DR agent. The following example illustrates the use of ISQL to connect to the DR agent. Open a command shell for OS user syb<sid>:

Exampleisql -X -U DR_admin -S <hostname>:<DR agent port>

The DR agent does not store its own security credentials, but rather, enforces authentication by pass-through authentication to the database server, or replication server.

Starting the DR Agent

When the replication server instance is created, a Bourne shell script is defined that can be used to start the DR agent.

Example of a Bourne shell script which should be started as OS user syb<sid>:

Example. /sybase/<SID>_REP/SYBASE.sh/sybase/<SID>_REP/SCC-3_2/bin/scc.sh

Stopping the DR Agent

A Bourne shell script can be used to stop the DR agent.

Example of a Bourne shell script which should be started as OS user syb<sid>:

Exampleisql –X –U DR_admin –S <hostname>:<DR agent port> <<EOF<DR_admin password>shutdowngoEOF

Starting the Replication Server

When the replication server instance is created, a Bourne shell script is defined that can be used to start the replication server.

Example of a Bourne shell script that should be started as OS user syb<sid>:

Example/sybase/<SID>_REP/<SID>_REP_<sitename>/RUN_<SID>_REP_<sitename>.sh

Stopping the Replication Server

Log on to the replication server and execute a ‘shutdown’ command.


112




Exampleisql –X –U DR_admin –S <hostname>:<replication server port> << EOF<DR_admin password>shutdowngoEOF

7.5 Removing the Replication Environment

The installer provides installation options for teardown and removal of a replication environment.

Start with the uninstallation of the current primary environment. Otherwise database connects will be redirected and the installer will not be able to execute the necessary cleanup in the database.

As soon as the primary replication environment is removed, it is possible to uninstall the standby replication environment.

Choose the following installer options to disable replication and remove the replication software on the hosts running the replication servers.

<SAP product> Software Lifecycle Options Database Tools SAP ASE Database Replication Removal of Replication Environment

Specify the kind of removal. Choose one of the following options:

● Tear down replication system

This option

○ disables replication in the ASE servers

○ stops the replication servers

○ deletes all directories and files created during setup, including the replication server instances

Data that was replicated to the standby databases will not be modified. The databases on the primary and standby hosts will not be “unmarked” for replication. The state of the environment after teardown will allow the immediate recreation of the replication environment. Materialization will again be required after setup.

NoteYou can only tear down the replication environment if the DR Agent is up and running.

● Unmark databases for replication and remove replication software

This option

○ unmarks the databases

○ drops the database users for replication

○ removes the replication software

If the replication server was running on a separate host, it is possible to clean up remaining SAP standalone units using the installer option Deleting an SAP System or Single Instances.




7.6 Integration of SAP Replication Server into an OS Cluster Environment

The replication server processes may run on the same machines hosting the ASE database servers. As a result, if the ASE database servers are running in an OS cluster environment, the replication server processes must be added to the definitions and instructions used by the cluster software.

This document describes the prerequisites and general requirements for allowing SAP Replication Server to work successfully in an OS cluster environment. These cluster environments are supported by hardware and software from third-party vendors. At this time, SAP Replication Server support in a cluster environment is possibly not yet fully integrated in the vendors cluster. As a result, the prerequisites and descriptions provided by this document provide general recommendations on how to add support for SAP Replication Server in a cluster environment. The primary assumption is that the cluster is already configured to support SAP Business Suite running SAP ASE and that replication must be added to the configuration to make it complete. The intent is that the replication server fails over or fails back in the OS cluster environment along with SAP ASE.

7.6.1 Prerequisites

Cluster Prerequisites

The following general capabilities are expected to be provided by any OS cluster solution available in order to allow the replication server to participate in the cluster.

NoteThese are expected to be the same requirements that ASE requires; none of these requirements is unique to the replication server.

● Shared disk storage between nodes of the cluster is provided

This storage will be used for configuration files, executable files, and storage files.

● Automatic IP address handling

When the cluster switches or moves activity from one node to another, the IP addresses used by applications to access the servers will be automatically reassigned to the new cluster node by the cluster software.

● Process identification and manipulation

The cluster software provides the ability to identify an operating system process or server, and exposes the ability to start and stop that process as part of the cluster failover process.

● Dependencies

The cluster software provides the ability to identify dependencies between a process and other resources in the cluster, so that any order of operations that relies on a preexisting process or resources can be maintained.

SAP Replication Server Prerequisites

Once your SAP system is properly configured for your cluster, the replication server can be added to the same cluster configuration to make the cluster environment complete. The intent is that the replication server fail-over or fail-back in the cluster environment run in parallel with SAP ASE.

114




The replication server has the same disk device dependencies as SAP ASE. If the replication server files need to be placed on a different device, be sure to add that additional device to the cluster resource definitions and add that device as a dependency.

The following table shows the technical details for the replication server, depending on your OS cluster software requirements:

Table 54

Technical Details: Description.

Number of processes There are three individual operating processes:

● Replication server

● Replication server system database

● DR (Disaster Recovery) agent

Number of cluster resources The replication server and its replication server system database are integrated. The replication server system database starts and stops with the replication server. As a result, it is sufficient to identify the replication server as a single resource for start, stop, and dependency configurations. The DR agent provides monitoring and configuration assistance for the replication server. It is not integrated with the replication server and is therefore required to be treated as an independent cluster resource.

Disk requirements The replication server includes all of the files installed under

/sybase/<SID>_REPIn addition, it is possible to configure the replication server to store its partition files in a separate location. All partition locations must be placed on devices shared between the nodes in the cluster. All of these devices must be identified as resources and dependencies for the cluster failover process.

Host name requirements During installation and configuration of the integrated Disaster Recovery solution for SAP Business Suite on ASE, the SAP installer prompts for the host names that will support the primary and standby instances. The host names supplied must, in each case, be the name of the cluster, and not the individual node names of the cluster.

NoteThe SAP installer passes these same host names to the DR agent. If you are testing the DR agent directly, the same host name of mycluster should be used whenever a host name is used.

NoteThe replication server and DR agent resource availability should not be used to trigger cluster failover. See the section Defining Node Failure Criteria [page 119].

7.6.2 Defining Resources

Two resources must be defined to include the replication server in your cluster solution. One resource must be defined for the replication server. One additional resource must be defined for the DR agent process. Before you can configure the resources for replication on the first OS cluster node, the ASE database server must be running on this




cluster node. Configuration of your cluster group to include the replication server should not be performed until after the replication environment is successfully installed.

7.6.2.1 Defining the SAP Replication Server Resource

Starting the Replication Server

When the replication server instance is created, a Bourne shell script is defined that can be used to start the replication server.


Example/sybase/<SID>_REP/<SID>_REP_<hostname>/RUN_<SID>_REP_<hostname>.sh

Stopping the Replication Server

Log on to the replication server and execute a shutdown command.


Exampleisql -X -U DR_admin -S <hostname>:<replication server port> << EOF<DR_admin password>shutdowngoEOF

Monitoring the Replication Server by Process

One method to determine whether the replication server is running is to look for the related system processes running on the operating system. Two processes must exist – one for the replication server and one for the replication server system database. Both processes should be running for you to be able to determine whether the replication server is available.

The executable name of the replication server process is repserver. In addition, the name of the replication server instance is passed as a parameter to the executable.

As an example, the following Linux command will return the process ID of a running replication server:

Exampleps -efa | grep <SID>_REP | grep repserver | awk '{print $2}'

The replication server system database process executable name is dbsrv12. In addition, the name of the replication server instance is passed as a startup parameter to the executable.

As an example, the following Linux command will return the process ID of a running replication server system database process:

116




Exampleps -efa | grep <SID>_REP | grep dbsrv12 | awk '{print $2}'

Monitoring the Replication Server by Command

An additional method for determining the state of the replication server is to log on to the replication server and issue a status command. This additional check assists in verifying that the server process is not just running but is also responsive to requests. You can write your own script or program to perform the monitoring. An example of a Bourne shell script that could check the results of the replication server admin health command would be similar to the following:

ExampleThe Bourne shell script which should be started as OS user syb<sid>:

isql -X -U DR_admin -S <hostname>:<replication server port> –o outfile.txt <<EOF<DR_admin password>admin healthgoEOFRS_STATUS='grep “NORMAL” outfile.txtif [ “//$RS_STATUS" = "//" ]; then// the replication server is not respondingfi

Stopping the Replication Server Forcefully

Some OS cluster software solutions require an option to forcefully terminate or remove a resource. For the replication server, the operating system processes for the replication server and the replication server system database can be terminated by sending a ‘kill’ signal to each of the processes.

Refer to the section Monitoring the Replication Server by Process to identify the process IDs; perform the following OS command for each process:

kill –9 <processID>

7.6.2.2 Defining the DR Agent Resource

Starting the DR Agent

When the replication server instance is created, a Bourne shell script is defined that can be used to start the DR agent.

Configure your cluster resource definition to execute this script to start the DR agent. Example of a Bourne shell script which should be started as OS user syb<sid>:




Example. /sybase/<SID>_REP/SYBASE.sh/sybase/<SID>_REP/SCC-3_2/bin/scc.sh

Stopping the DR Agent

Configure your cluster resource definition to execute this script to stop the DR agent. Example of a Bourne shell script which should be started as OS user syb<sid>:

Exampleisql –X –U DR_admin –S <hostname>:<DR agent port> <<EOF<DR_admin password>shutdowngoEOF

Monitoring the DR Agent by Process

One method to determine whether the DR agent is running is to look for the related system processes running on the operating system.

The DR agent is a Java process. The SID and startup class names are used to uniquely identify a DR agent process that is running on your host. As an example, the following Linux command will return the process ID of a running DR agent process:

Exampleps —efa | grep <SID>_REP | grep com.sybase.ua.startup.Startup | awk '{print $2}'

Stopping the DR Agent Forcefully

Some cluster software solutions require an option to forcefully terminate or remove a resource. For the DR agent, the operating system processes for the DR agent can be terminated by sending a ‘kill’ signal to the operating system process.

See Monitoring the DR Agent by Process to identify the process ID; perform the following OS command to kill the monitored process:

kill –9 <processID>

7.7 Defining Dependencies

Both resources for replication – the replication server and the DR agent resource – will have the same dependencies. Each will be dependent on:

● The shared disk resource(s)

● The IP Address handling resource

118




Use the appropriate commands for your cluster software to add these dependencies to both the replication server and DR agent resources.

NoteThere is no dependency between the replication server and DR agent. They can execute independently of each other.

7.8 Defining Node Failure Criteria

Most cluster software allows the state of the different cluster resources to trigger an automatic fail-over from one node in the cluster to another. The replication server and DR agent resource availability should not be used to trigger cluster fail-over.

Since the replication server processing is considered part of the SAP ASE database solution, no separate fault monitoring is required. If your existing hardware server or ASE monitoring determines that fail-over should occur, this is sufficient for replication to participate. It is not suggested that you add replication availability as a monitor for cluster node or ASE availability.

A failure by either of the replication resources will not affect the availability of your SAP application. However, a failure of your ASE resources does affect your SAP application availability. It is recommended that node failure continue to be triggered by ASE, but not include replication availability.




8 Additional Information

The following sections provide additional information about optional preparation, installation, and post-installation tasks.

There is also a section describing how to delete an SAP system.

Preparation

● Integration of LDAP Directory Services [page 123]


Checking and Modifying the HP-UX Kernel [page 127]End of: HP-UX |


Creating HP-UX Groups and Users [page 130]End of: HP-UX |


Setting Up File Systems for HP-UX [page 131]End of: HP-UX |


Mounting Installation Media for HP-UX [page 134]End of: HP-UX |


Exporting and Mounting Directories via NFS for HP-UX [page 135]End of: HP-UX |

Installation

● Installing the Host Agent Separately [page 136]

Post-Installation

● Starting and stopping SAP System Instances [page 138]

● If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access [page 145]

● Heterogeneous SAP System Installation [page 145]

Deleting an SAP System or SAP Instance

● Deleting an SAP System [page 146]

8.1 Splitting Off a Central Services Instance for ABAP from an Existing Primary Application Server Instance

With the installation option Split Off ASCS Instance from existing Primary Application Server Instance, you can move the message server and the enqueue work process from an existing primary application server instance to a newly

120



Additional Information

installed central services instance for ABAP (ASCS instance). The new ASCS instance is installed while the split is done.

Prerequisites

The existing SAP system of the primary application server instance must meet the following requirements:

● It was upgraded to an SAP system based on SAP NetWeaver 7.3 or higher

● It does not yet have an ASCS instance

Before the Split

The primary application server instance includes:

● ABAP dispatcher and work processes (dialog, batch, spool, enqueue, or update)

● Gateway

● Internet communication manager (ICM)

● Internet graphics service (IGS)

● ABAP message server

After the Split

A central services instance for ABAP (ASCS instance) has been split off from the existing primary application server instance.

The primary application server instance now includes:

● ABAP dispatcher and work processes (dialog, batch, spool, or update)

● Gateway

● Internet communication manager (ICM)

● Internet graphics service (IGS)

The newly created central services instance for ABAP (ASCS instance) includes:

● ABAP message server

● ABAP standalone enqueue server

The ABAP enqueue work process is now replaced with the ABAP standalone enqueue server.

The Effect of the Split

The following graphic provides an overview of the components contained in the primary application server instance before and after the split, along with the newly created ASCS instance:

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseAdditional Information



Figure 16

Procedure

1. Plan the basic parameters, as described in Basic SAP System Installation Parameters [page 35]:

○ Choose an instance number for the ASCS instance to be created.

○ Note that the message server port is not changed during the split.

2. Check the hardware and software requirements for the ASCS instance to be created as described in Hardware and Software Requirementss .

3. Specify basic SAP system parameters [page 35] for the ASCS instance to be created.

4. Set up the required file systems [page 57] for the ASCS instance to be created.

5. Start the installer as described in Running the Installer [page 77].

6. On the Welcome screen, choose <SAP Product> <Database> Additional SAP System Instances Split Off ASCS Instance from Existing Primary Application Server Instance .

7. Follow the instructions on the installer screens and enter the required parameters.

NoteTo find more information on each parameter during the input phase of the installation, position the cursor on the required parameter and choose F1 .

After you have entered all requested input parameters, the installer displays the Parameter Summary screen. This screen shows both the parameters that you entered and those that the installer set by default. If required, you can revise the parameters before starting the installation.

8. To start the installation, choose Start.

The installer starts the installation and displays the progress of the installation. When the installation has successfully completed, the installer shows the dialog Execution of Split Off ASCS Instance from existing Primary Application Server Instance has completed.

122




9. Check settings for operating system users [page 94] if they were created by the installer.

10. Check whether you can start and stop the SAP system [page 138] with the newly created ASCS instance and SCS instance.

11. Check whether you can log on to the application server [page 94].

12. Ensure user security for the operating system users of the newly created ASCS instance.

13. If required, perform an installation backup [page 103].

8.2 Integration of LDAP Directory Services

This section explains the benefits of using the SAP system with the Lightweight Directory Access Protocol (LDAP) directory and gives an overview of the configuration steps required to use an SAP system with the directory.

LDAP defines a standard protocol for accessing directory services, which is supported by various directory products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory services enables important information in a corporate network to be stored centrally on a server. The advantage of storing information centrally for the entire network is that you only have to maintain data once, which avoids redundancy and inconsistency.

If an LDAP directory is available in your corporate network, you can configure the SAP system to use this feature. For example, a correctly configured SAP system can read information from the directory and also store information there.

NoteThe SAP system can interact with the Active Directory using the LDAP protocol, which defines:

● The communication protocol between the SAP system and the directory

● How data in the directory is structured, accessed, or modified

If a directory other than the Active Directory also supports the LDAP protocol, the SAP system can take advantage of the information stored there. For example, if there is an LDAP directory on a UNIX or Windows server, you can configure the SAP system to use the information available there. In the following text, directories other than the Active Directory that implement the LDAP protocol are called generic LDAP directories.

This section does not provide information about the use of LDAP directories with the LDAP Connector. For more information about using and configuring the LDAP Connector for an ABAP system, see the SAP Library [page 13] at:

Table 55


● SAP NetWeaver 7.1 for Banking Services from SAP

● SAP NetWeaver 7.1 including Enhancement Package 1 for Banking Services from SAP

Function-Oriented View Security Identity ManagementIdentity Management of the Application Server ABAPConfiguration of User and Role Administration Directory Services LDAP Connector

● SAP NetWeaver Mobile 7.1

● SAP NetWeaver Mobile 7.1 including Enhancement Package 1

Security Identity Management Identity Management of the Application Server ABAP Configuration of User and Role Administration Directory Services LDAP Connector

● SAP NetWeaver Process Integration 7.1 Security Identity Management Identity Management of the Application Server ABAP Configuration of User and Role Administration Directory Services LDAP Connector





● SAP NetWeaver Process Integration 7.1 Including Enhancement Package 1




Security Identity Management User and Role Administration of Application Server ABAP Configuration of User and Role Administration Directory Services LDAP Connector

Prerequisites

● You can only configure the SAP system for Active Directory services or other LDAP directories if these are already available on the network. As of Windows 2000 or higher, the Active Directory is automatically available on all domain controllers. A generic LDAP directory is an additional component that you have to install separately on a UNIX or Windows server.

● Make sure that the required software is installed:

Table 56

Operating System Required Software

AIX IBM Tivoli Directory Server client packages

HP-UX The LDAP libraries listed in SAP Note 541344

Linux You must have at least the following RPM packages installed:

● Oracle Linux:

openldap2● Red Hat Linux:

openldap2● SUSE LINUX

openldap2openldap2-client

Solaris You must have at least the libldap.so library installed.

Features

In the SAP environment, you can exploit the information stored in an Active Directory or generic LDAP directory by using:

● SAP Logon

● The SAP Microsoft Management Console (SAP MMC)

● The SAP Management Console (SAP MC)

For more information about the automatic registration of SAP components in LDAP directories and the benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information in Directory Services at:

scn.sap.com/docs/DOC-14384

124






For more information about the SAP MC and about how to configure it to access LDAP Directories, see the documentation SAP Management Console in the SAP Library [page 13] at:

Table 57





Solution Life Cycle Management SAP Management Console

SAP Logon

Instead of using a fixed list of systems and message servers, you can configure SAP Logon in the sapmsg.ini configuration file to find SAP systems and their message servers from the directory. If you configure SAP logon to use the LDAP directory, it queries the directory each time Server or Group selection is chosen to fetch up-to-date information on available SAP systems.

To use LDAP operation mode, check that the sapmsg.ini file contains the following:

[Address]Mode=LDAPdirectoryLDAPserver=LDAPnode=LDAPoptions=Distinguish the following cases:

● If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For more information, see the SAP system profile parameter ldap/options.

● You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if one of the following is true:

○ The client is not located in the same domain forest as the Active Directory

○ The operating system does not have a directory service client (Windows NT and Windows 9X without installed dsclient).

For more information, see the SAP system profile parameter ldap/servers.

● For other directory services, you can use LDAPnode to specify the distinguished name of the SAP root node. For more information, see the SAP system profile parameter ldap/saproot.

SAP MMC

The SAP MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central location. It is automatically set up when you install an SAP system on Windows. If the SAP system has been prepared correctly, the SAP MMC presents and analyzes system information that it gathers from various sources, including the Active Directory.

Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can read system information straight from the directory that automatically registers changes to the system landscape. As a result, up-to-date information about all SAP application servers, their status, and parameter settings is always available in the SAP MMC.

If your SAP system is part of a heterogeneous SAP system landscape that comprises systems or instances both on Unix and Windows operating systems, you can also use the SAP MMC for operating and monitoring the instances running on Unix.




SAP MC

The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems from a central location. The SAP MC is automatically set up when you install an SAP system on any platform. If the SAP system has been prepared correctly, the SAP MC presents and analyzes system information that it gathers from various sources, including a generic LDAP Directory.

Integrating a generic LDAP Directory as a source of information has advantages for the SAP MC. It can read system information straight from the directory that automatically registers changes to the system landscape. As a result, up-to-date information about all SAP application servers, their status, and parameter settings is always available in the SAP MC.

Configuration Tasks for LDAP Directories

This section describes the configuration tasks for the Active Directory or other (generic) LDAP directories.

Configuration Tasks for Active Directory

To enable an SAP system to use the features offered by the Active Directory, you have to configure the Active Directory so that it can store SAP system data.

To prepare the directory, you use the installer to automatically:

● Extend the Active Directory schema to include the SAP-specific data types

● Create the domain accounts required to enable the SAP system to access and modify the Active Directory. These are the group SAP_LDAP and the user sapldap.

● Create the root container where information related to SAP is stored

● Control access to the container for SAP data by giving members of the SAP_LDAP group permission to read and write to the directory

You do this by running the installer on the Windows server on which you want to use Active Directory Services and choosing Generic Installation Options <Database> Preparations LDAP Registration Active Directory Configuration . For more information about running the installer on Windows, see the documentation Installation Guide – <your SAP product> on Windows: <Database>.

NoteYou have to configure the directory server only once. Then all SAP systems that need to register in this directory server can use this setup.

Configuration Tasks for Generic LDAP Directories

To configure other LDAP directories, refer to the documentation of your directory vendor.

Enabling the SAP System LDAP Registration

Once you have correctly configured your directory server, you can enable the LDAP registration of the SAP system by setting some profile parameters in the default profile.

To do this, run the installer [page 77] once for your system and choose:

Generic Installation Options <Database> Preparations LDAP Registration LDAP Support

If you use a directory server other than Microsoft Active Directory and/or non-Windows application servers, you have to store the directory user and password information by using ldappasswd pf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and is therefore valid for all application servers. After restarting all application servers and start services, the system is registered in your

126




directory server. The registration protocols of the components are dev_ldap*. The registration is updated every time a component starts.Only valid for: HP-UX |

8.3 Checking and Modifying the HP-UX Kernel

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

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

Procedure

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


○ Using kcweb for HP–UX 11.31

For more information, see section Configuring the Kernel Using kcweb for HP-UX 11.23 and HP–UX 11.31 below.

Configuring the Kernel Using kcweb for HP-UX 11.31

Kernel configuration using kcweb is a combination of a command set and a Web-based graphical user interface (GUI) that lets you configure an HP-UX kernel and monitor consumption of kernel resources controlled by parameters.

The kcweb application replaces the kernel configuration portion of SAM and adds the following commands for kernel configuration and monitoring to the system:

● kcweb(1M)● kcusage(1M)● kcalarm(1M)

There is also the daemon kcmond(1M), which replaces the obsolete krmond(1M).

The kcweb application provides the following new features:

● New Web-based, PC-supported GUI that is faster and easier to use remotely than the current SAM interface

● Kernel parameter documentation that you can view within the GUI

● Support for dynamic (no reboot) kernel tuning






● Parameter monitoring that lets you continually monitor the usage of kernel resources (with kcmond) and proactively tune the kernel instead of waiting for an application to fail

Parameter monitoring offers you:

○ Tables and graphs of kernel resources controlled by kernel parameters

○ User-created threshold alarms that issue alerts when consumption of a kernel resource exceeds a specified percentage of the parameter value

● Improved command line interface (CLI) that offers all functionality available in the GUI

● Improved separation between GUI and kernel so that the application does not need to be patched so frequently

Less than 12 MB of disk is necessary for kcweb, and minimal memory is required by CLIs (approximately 20 MB memory for HP Apache-based Web Server and Netscape).

Additionally, the kcweb application GUI offers online help.

Configuring the Kernel Using SMH for HP-UX 11.31

1. Enter one of the following commands:

○ /usr/sbin/smh○ http://<hostname>:<port>

where <port> is either the default port 2381 or your defined port (for example 2301)

2. Choose Kernel Configuration Tunables .

3. Select the parameter to be modified and enter m (m-Modify).

4. Modify all kernel parameters according to the table above.

5. Choose Modify.

6. Exit SMH.

7. Reboot the system.End of: HP-UX |


8.4 Setting up Swap Space for HP-UX

Here, you can find information about how to set up swap space for HP-UX.

Procedure

1. Find out whether you have to increase the swap space:

RecommendationWe recommend to set SWAP space to 2 * RAM (minimum 20 GB).


You can determine the size of the installed RAM in one of the following ways:

○ Using the System Administration Manager (SAM):

Choose Performance Monitors System Properties Memory

128





○ Manually:

○ To display the RAM size on HP-UX PA-RISC, enter the following command:

echo "selclass qualifier memory;info;wait;infolog" | cstm |grep Memory |grep Total

○ To display the RAM size on HP–UX 11.31 systems:

/usr/contrib/bin/machinfo |grep Memory2. To check whether enough swap space is currently configured on your system, enter the following command

and add up the total device swap space:

/usr/sbin/swapinfo –dm

Example/usr/sbin/swapinfo -dmMb Mb Mb PCT MbTYPE AVAIL USED FREE USED START RESERVE PRI NAMEdev 10000 82 9918 1% 0 - 1 /dev/vg00/lvol2dev 20000 83 19917 0% 0 - 1 /dev/vg01/lvol9In this case, the total device swap space is 30000 MB.

3. If necessary, increase the swap space in one of the following ways:

○ Manually, as described below in Setting Up Swap Space Manually

○ Using SMH, as described below in Setting up Swap Space Using SMH for HP-UX 11.31

4. If you are not installing a standalone database server, check the paging size and the kernel settings, as described below in Checking Paging Space Size and Kernel Settings.

Setting up Swap Space Manually

1. To create a logical volume, enter the following command:

lvcreate –C y —n <LVName> /dev/<VGName>2. To define the size and allocate the logical volume to a disk, enter the following commands:

lvextend —L <size in MB> /dev/<VGName>/<LVName> \/dev/dsk/<diskdevice>

3. To enable automatic swap activation at boot time, add the following entry to /etc/fstab:

/dev/<VGName>/<LVName> /swap swap defaults 0 04. To manually activate the space for the swap devices defined in /etc/fstab, enter the following command:

/usr/sbin/swapon -a5. To check if the swap space has been activated, enter the following command:

/usr/sbin/swapinfo –tm

Checking Paging Space Size and Kernel Settings

NoteIf you are installing a standalone database server do not execute this step.

1. Make sure that the UNIX kernel, paging space, and user limits are already configured for the SAP system.




2. Execute memlimits to verify paging space size and kernel settings as follows:

1. Mount the Installation Master and Kernel DVD.

2. Make sure that the SAPCAR program is available on the installation host.

If SAPCAR is not available, you can get it in one of the following ways:

○ Download it from service.sap.com/swdc.

○ Get it from the installer as follows:

Start the installer and wait until the Welcome screen is displayed.

The installer then extracts itself to a directory named sapinst_exe.xxxxxx.xxxx which is located in the temporary directory <TMPDIR> specified by the value of the TEMP, TMP, or TMPDIR environment variable.

3. To unpack the file memlimits, enter the following commands:

/<TMPDIR>/sapinst_exe.xxxxxx.xxxx/SAPCAR -xvfg \/<mountdir Inst. Master and Kernel DVD>/DATA_UNITS/K_720_<U/N>_<OS>/DBINDEP/SAPEXE.SAR memlimits

4. Start memlimits using the following command:

./memlimits -l 20000If you see error messages, increase the paging space and rerun memlimits until there are no more errors.

3. If you see error messages, increase the paging space and rerun memlimits until there are no more errors.End of: HP-UX |


8.5 Creating HP-UX Groups and Users

Here you can find information about how to create operating system users and groups on HP-UX.

NoteTo prevent terminal query errors in the <sapsid>adm environment, change the following shell template as follows:

1. Edit /etc/skel/.login,

2. Comment out (with #) the following line:

#eval `tset -s -Q -m ':?hp'For more information, see SAP Note 1038842.

Procedure

Creating Groups and Users for HP-UX 11.31




130






2. Choose Accounts for Users and Groups Local Users Add User Account .

3. Enter the required users.

4. Choose Accounts for Users and Groups Groups Add new Group .

5. Enter the required groups.

6. Exit SMH.

7. Verify that the TZ settings in the following are consistent:

/etc/TIMEZONE/etc/profile/etc/csh.login

More Information

For more information about required operating system users and groups, see Creating Operating System Users and Groups [page 54].End of: HP-UX |


8.6 Setting Up File Systems for HP-UX

Here you can find information about how to set up file systems for HP-UX.

Using a Logical Volume Manager (LVM) lets you distribute logical volumes across several disks or LUNs (physical volumes). The individual logical volumes are grouped together into volume groups.

HP-UX 11.31 (11i v3) introduces a new agile addressing scheme for mass storage devices, with opaque minor numbers, persistent device special files (DSFs), and new hardware path types and formats. The addressing scheme used in previous HP-UX releases – called “legacy addressing” – coexists with this new scheme to ensure backward compatibility. The legacy addressing is to be deprecated in a future HP-UX release.

For more information, check the document HP-UX 11i v3 Mass Storage Device Naming at the HP Manuals Business Support Center website.

Procedure

NoteConsider the SAP recommendations for data security when planning the distribution of data in LVM.

RecommendationFor recommendations about block size and mount option configuration, see SAP Note 1077887.

You can create file systems in one of the following ways:

● Manually, as described below in “Setting up File Systems Manually Using LVM”.

● Using the interactive tools SAM or SMH. See Table 2-4 in the document SAM-HP SMH Cross Reference Guide HP-UX 11i at the HP Manuals Business Support Center website.





Setting up File Systems Manually Using LVM

1. Examine the device configuration:

○ The ioscan command provides the device file name and the hardware addresses of all available devices, using the device class disk:

○ For persistent device files, enter:

ioscan -m lun○ For legacy device files, enter:

ioscan -f -C disk○ To show the mapping of the legacy device files and the persistent device files, enter:

ioscan -m dsf○ Device file name format:

○ Persistent device filenames have the following format:

/dev/disk/disk<number>

Example/dev/disk/disk6 (block device)

/dev/rdisk/disk6 (raw device)

○ Legacy device filenames have the following format:

/dev/dsk/c<number>t<number>d<number>

Example/dev/dsk/c2t5d0 (block device)

/dev/rdsk/c2t5d0 (raw device)

○ The following command scans all disks for the current LVM:

vgscan -pv

NoteMake sure that you use option -p (preview), otherwise /etc/lvmtab is updated.

2. You can determine disk or LUN size using the following command:

diskinfo /dev/rdisk/<raw_device_file_name>3. Prepare disks for LVM using the following command:

pvcreate /dev/rdisk/<diskdevice>4. Create one or more volume group directories <VG_Name> and group device files. For each volume group in the

system, there must be a volume group directory that has a character device file named group in it.

Execute the following commands:

mkdir /dev/<VG_Name>mknod /dev/<VG_Name>/group c 64 0x<nn>000

5. Create the volume group by specifying which physical volumes (disks or LUNs) belong to the group:

vgcreate /dev/<VG_Name> /dev/disk/<diskdevice>

132




NoteFor large disk sizes and large numbers of disks, you might need to increase the volume group physical extent (PE) size with the -s option and the maximum physical volume option -p.

Proceed as follows to add other disks or LUNs to an existing volume group:

vgextend /dev/<VG_Name><block_device_file_name>6. To check the size and number of physical volumes or disks in a volume group, use the following command:

vgdisplay -v /dev/<VG_Name>7. Create one logical volume for each file system as follows:

1. Enter the following command:

lvcreate /dev/<VG_Name>2. Allocate the required logical volume size to disks or LUNs as follows:

lvextend -L <size_in_MB> /dev/<VG_Name>/<LV_Name><block_device_filename><size_in_MB> needs to be a multiple of the physical extent size, otherwise the size is rounded up.

You can determine the size of the logical volumes with either of the following commands:

○ vgdisplay -v /dev/<VG_Name>○ lvdisplay /dev/<VG_Name>/<LV_Name>

For the required size for each file system, see SAP Directories [page 57].

8. Create the file systems that are required by SAP as follows:

newfs -F vxfs -b 8192 /dev/<VG_Name>/r<LV_Name>

NoteFor more information about database-dependent block size recommendations, see SAP Note 1077887.

9. Create mount directories using the following command:

mkdir <mountdir>10. Add the new file system to /etc/fstab.

Example/dev/<VG_Name>/<LV_Name> /<mountdir> vxfs delaylog,nodatainlog 0 2

NoteFor database file systems see SAP Note 1077887 “SAP on HP-UX: mount & file system options for best performance” (for example using concurrent I/O (CIO), direct I/O (DIO) or buffered I/O).

NoteWhen defining the mount order sequence in /etc/fstab, you have to consider mount order dependencies. For example, /sapmnt/<SAPSID> must be mounted before /sapmnt/<SAPSID>/profile.

11. Mount the file systems using the following command:

mount -aEnd of: HP-UX |







8.7 Mounting Installation Media for HP-UX

Proceed as follows to mount a CD or DVD.

NoteThe placeholder <medium-mountdir> is used for either <cd-mountdir> or <dvd-mountdir>.

Procedure

Mounting a CD / DVD Manually


2. To create a mount point for CD / DVD, enter the following command:

mkdir /<medium-mountdir>

Example<medium-mountdir> is /sapcd

3. To find out the hardware address of the CD/DVD drive, proceed as follows:

1. Enter the following command:

ioscan -fnkCdiskA list of all devices is displayed

2. Note the hardware address of the CD/DVD drive, for example c0t4d0.

4. To check that the driver is part of the kernel (skip this step if the CD / DVD drive is already working), enter the following command:

grep cdfs /stand/systemIf the driver is not configured, you have to add the string cdfs to the file /stand/system and rebuild the kernel. For more information about how to build a new kernel, see Checking and Modifying the HP-UX Kernel [page 127]. After rebuilding the kernel, reboot the system.

5. To mount the CD / DVD on HP-UX 11.31, enter the following command:

mount -r -F cdfs -o rr /dev/disk/<diskdevice> <medium-mountdir>

ExampleHP-UX 11.31: mount -r -F cdfs -o rr /dev/disk/c0t4d0 /sapcd

Mounting a CD / DVD Using SMH for HP-UX 11.31



134





2. Choose Disks and Filesystems File Systems Add CDFS

3. Enter the mount directory:

<medium-mountdir>

ExampleFor example, <medium-mountdir> is /sapcd.

4. Choose the hardware path.

5. Choose New CDFS

6. Exit SMH.End of: HP-UX |


8.8 Exporting and Mounting Directories via NFS for HP-UX

You can configure NFS on HP-UX 11.31 (11i v3) in one of the following ways:

● Manually as described below.

● Using the interactive tools SAM or SMH.

For more information about NFS for HP-UX 11.31, see the document NFS Services Administrator's Guide HP-UX 11i version 3 at the HP Manuals website.

Procedure

Procedure on the Host where the Main Instance Runs (export NFS volumes)

1. Add the file system that you want to export to the file /etc/dfs/dfstab using the following syntax:

share –F nfs –o root= <client_1>:<client_n>,> \access= <client_1>:<client_n> <file system to share>

Exampleshare –F nfs –o root=hw5111:hw5115, access=hw511:hw5115 /sapmnt/C11/exe

NoteIf you are moving from a legacy system with the /etc/exports NFS configuration file you can use /usr/contrib/bin/exp2dfs to automatically convert the legacy syntax to the new syntax in /etc/dfs/dfstab.

If you encounter problems, try using the FQDN (Fully Qualified Domain Name).

2. To make the file system available to NFS clients, enter the following command:

/usr/sbin/shareall




Procedure on the Host where the Additional Instance Runs (mount NFS volumes)

1. Add the remote file system to /etc/fstab.

Examplehwi173:/sapmnt/C11 /sapmnt/C11 nfs defaults 0 0

2. Mount the file system.

Examplemount –a

End of: HP-UX |

8.9 Installing the SAP Host Agent Separately

This procedure tells you how to install an SAP Host Agent separately.

The SAP Host Agent is installed automatically during the installation of new SAP instances with SAP kernel 7.20 or higher (integrated installation). This procedure is only for hosts with no SAP Host Agent running on them, due to the following reasons:

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

SAP Host Agent has the following executable programs and services:

● The SAPHostExec service

● The sapstartsrv service SAPHostControl● The operating system collector saposcol

Procedure

Perform the following steps on the host where you install the SAP Host Agent separately:

1. Make sure that the sapadm user is created.

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

Table 58: User and Groups of the SAP Host Agent


sapadm sapsys – SAP Host Agent administrator

136





NoteIf sapadm does not exist, it is

created during the SAP Host Agent installation using /bin/false shell.

Make sure that /bin/false can be used as a login shell.


Add /bin/false to the list of

valid login shells (attribute shells) in /etc/security/login.cfg.

End of: AIX |

Table 59: Groups and Members of the SAP Host Agent User

Groups Members

sapsys sapadm

sapinst sapadm

2. Set up the required file system for the SAP Host Agent:

Table 60

Directories Description Required Disk Space

/usr/sap/hostctrl Contains the following directories:

● exeContains the profile host_profile

● workWorking directory of the SAP Host Agent

100 MB

For more information, see Setting up file systems and raw devices [page 57]

3. Make available the unpacked software provisioning manager 1.0 archive SWPM10SP<Support_Package_Number>_<Version_Number>.SAR and the medium for the UC kernel (folder K_<Version>_U_<OS>) on the installation host.


4. To install the SAP Host Agent, you start the installer [page 77] and choose Generic Installation Options<Database> Preparations SAP Host Agent on the Welcome screen of the installer.

5. Check whether the installed services are available:

1. Check whether the following services are available:

○ The control program saphostexec○ The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)




More Information

For more information about the SAP Host Agent, see the SAP Library [page 13] at:

Table 61





Solution Life Cycle Management SAP Host Agent

8.10 Starting and Stopping SAP System Instances

8.10.1 Starting and Stopping SAP System Instances Using the SAP Management Console

You can start and stop all instances of your SAP system using the SAP Management Console (SAP MC).

RecommendationIf you experience any issues when starting or using the SAP MC, refer to SAP Note 1153713.

Prerequisites

● Make sure that the host names defined in the DNS server match the names of the SAP system instance hosts. In particular, keep in mind that host names are case-sensitive. For example, if the names of the SAP system instance hosts are in upper case, but the same host names are defined in the DNS server in lower case, starting and stopping the system does not work.


● Make sure that the host on which you start the SAP MC meets the following requirements:

○ At least Java Runtime Environment (JRE) 5.0 is installed.

○ The browser’s Java plug-in is installed and activated.

Procedure

Starting the Web-Based SAP Management Console

1. Start a Web browser and enter the following URL:

http://<Host_Name>:5<Instance_Number>13

138






ExampleIf the instance number is 53 and the host name is saphost06, you enter the following URL:

http://saphost06:55313

This starts the SAP MC Java applet.

NoteIf your browser displays a security warning message, choose the option that indicates that you trust the applet.

2. Choose Start.

The SAP MC appears.

NoteWhen you start the SAP MC for the first time for a newly installed SAP system, you have to register your system as described in Registering Systems and Instances below. After you have done this, the instances installed on the host you have connected to will be present in the SAP MC the next time you start it.

By default, the instances installed on the host you have connected to are already present in the SAP MC.

If you want to change the configuration to display systems and instances on other hosts, see Registering Systems and Instances below.

Starting and Stopping Systems and Instances

Similarly, you can start, stop, or restart all SAP systems and individual instances registered in the SAP MC.

Starting an SAP System or Instance

1. In the navigation pane, open the tree structure and navigate to the system node that you want to start.

2. Select the system or instance you want to start and choose Start from the context menu.

3. In the Start SAP System(s) dialog box, choose the required options.

4. Choose OK.

The SAP MC starts the specified system or system instances.

NoteThe system might prompt you for the SAP system administrator credentials. To complete the operation, you require administration permissions.

Log in as user <sapsid>adm.

Starting SAP System Instances Successively

If you need to start the instances of an SAP system successively, for example when you want to start a distributed or a high-availability system, proceed in the following sequence:

1. Start the database instance.


If your system is a high-availability system, start the ABAP central services instance ASCS<Instance_Number>.End of: HA (UNIX) |




3. Start the primary application server instance DVEBMGS<Instance_Number>.

4. Start additional application server instance(s) D<Instance_Number> if there are any.

Stopping an SAP System or Instance

1. In the navigation pane, open the tree structure and navigate to the system node that you want to stop.

2. Select the system or instance you want to stop and choose Stop from the context menu.

3. In the Stop SAP System(s) dialog box, choose the required options.

4. Choose OK.

The SAP MC stops the specified system or system instances.

NoteThe system might prompt you for the SAP system administrator credentials. To complete the operation, you require administration permissions.

Log in as user <sapsid>adm.

Stopping SAP System Instances Successively

If you need to stop the instances of an SAP system successively, for example when you want to start a distributed or a high-availability system, proceed in the following sequence:

1. Stop additional application server instance(s) D<Instance_Number> if there are any.

2. Stop the primary application server instance DVEBMGS<Instance_Number>.


If your system is a high-availability system, stop the ABAP central services instance ASCS<Instance_Number>.End of: HA (UNIX) |

4. Stop the database instance.

More Information

● For more information about handling the SAP MC, see the SAP Library [page 13] at:

Table 62





Solution Life Cycle Management SAP Management Console

● If your newly installed SAP system is part of a heterogeneous SAP system landscape comprising systems or instances on Windows platforms, you can also start and stop it from a Windows system or instance using the SAP Microsoft Management Console (SAP MMC).

For more information about handling the SAP MMC, see the SAP Library [page 13] at:

140




Table 63





Solution Life Cycle Management SAP Microsoft Management Console: Windows

8.10.2 Starting and Stopping SAP System Instances Using Commands

Start and stop SAP system instances using the startsap and stopsap commands.

You can use command line options to specify these commands. Command line options are available in the new style or the old style.

Using New Style for Command Line Options and Parameters

Using the new style, the syntax is as follows:

stopsap | stopsap [-t | -task <task>] [-i | -instance <instance>] [-v | -vhost "<virtual hostname>[ <virtual hostname>]*"][-c | -check] [-h | -help] [-V | -VERSION] [-C | -checkVHost]

ExampleIf you want to start a primary application server instance DVEBGMS00 that has the virtual host names cic11 and cic12, enter the following commands:

startsap -t r3 -i DVEBGMS00 -v "cic11 cic12"

The following command line options and parameters are available:

Table 64: Command Line Options (New Style)

Parameter Name Description

[-t | -task <task>] Specify task

[-i | -instance <instance>] Specify SAP system instance

[-v | -vhost "<virtual hostname>[ <virtual hostname>]*"]

Specify virtual host names

[-c | -check] Check database and SAP instance status

[-h | -help] Display help

[-V | -VERSION] Display startsap script version

[-C | -checkVHost] Check virtual host name

Table 65: Parameters for <task> (New Style)


check Check status of database and SAP system instances





r3 Start or stop SAP instances only

db Start or stop database only

all | <blank> Start or stop database and SAP instance

startupsrv Start or stop sapstartsrv program

Table 66: Parameters for <instance>


DVEBMGS<Instance_Number> Primary application server Instance

D<Instance_Number> Additional application server instance

ASCS<Instance_Number> ABAP central services instance (ASCS instance)

ERS<Instance_Number> Enqueue replication server instance (ERS instance)

SMDA<Instance_Number> Diagnostics Agent instance

W<Instance_Number> Web services instance

G<Instance_Number> Gateway instance

Using Old Style for Command Line Options and Parameters

Using the old style, the syntax is as follows:

stopsap | stopsap [db|r3|all|check|startupsrv] [<instance>] [<virtual hostname>]

ExampleIf you want to start a primary application server instance DVEBGMS00 that has the virtual host names cic11 and cic12, enter the following commands:

startsap r3 DVEBGMS00 cic11 cic12

The following command line options and parameters are available:

Table 67: Command Line Options (Old Style)


check [<instance>] [<virtual hostname>] Check status of database and SAP system instances

r3 [<instance>] [<virtual hostname>] Start or stop SAP instances only

db [<instance>] [<virtual hostname>] Start or stop database only

all | <blank> Start or stop database and all SAP system instances running on the same physical host

startupsrv Start or stop sapstartsrv program

Table 68: Parameters for <instance>


DVEBMGS<Instance_Number> Primary application server Instance

142





D<Instance_Number> Additional application server instance

ASCS<Instance_Number> ABAP central services instance (ASCS instance)

ERS<Instance_Number> Enqueue replication server instance (ERS instance)

SMDA<Instance_Number> Diagnostics Agent instance

W<Instance_Number> Web services instance

G<Instance_Number> Gateway instance

Prerequisites

● You have logged on to the physical host of the SAP system instances as user <sapsid>adm.

● Host names defined in the DNS server must match the names of the SAP system instance hosts. The host names are case-sensitive. For example, if the names of the SAP system instance hosts are in uppercase, but the same host names are defined in the DNS server in lowercase, starting and stopping the system does not work.

● If you want to use startsap or stopsap (for example, in a script) and require the fully qualified name of these SAP scripts, create a link to the startsap script in the home directory of the corresponding user.

● You cannot use startsap or stopsap commands in a switchover cluster environment. Therefore in a high-availability (HA) system you must use the failover cluster software of your HA partner to start or stop instances running on the switchover cluster.

● You cannot use startsap or stopsap commands to start or stop database-specific tools. For more information about how to start or stop database-specific tools, see the database-specific information in this documentation and the documentation from the database manufacturer.

● Make sure that no SAP instance is running before you execute stopsap on a standalone database server. No automatic check is made.

● When you use stopsap in a Multiple Components in One Database (MCOD) system with two primary application server instances, only one primary application server instance and the database are shut down. Therefore, first stop the other SAP system or check that it has already been stopped.

Procedure

Starting an SAP System

● If you want to start all SAP system instances running on the same host, execute the following command:

New style: startsap or startsap -t allOld style:startsap or startsap all

● If you want to start SAP system instances separately, enter the following command:

New style:startsap -t r3 -i <instance> [-v "<virtual host name>"]Old style:startsap r3 <instance> [<virtual host name>]Adhere to the following sequence when starting the instances:




1. Database instance

2. ERS instance for the ASCS instance (if available)

3. ASCS instance

4. Primary application server instance

5. Additional application server instances (if available)

Stopping an SAP System

● If you want to stop all SAP system instances running on the same host, execute the following command:

New style: stopsap or stopsap -t allOld style:stopsap or stopsap all

● If you want to stop SAP system instances separately, enter the following command:

New style:stopsap -t r3 -i <instance> [-v "<virtual host name>"]Old style:stopsap r3 <instance> [<virtual host name>]Adhere to the following sequence when stopping the instances:

1. Additional application server instances (if available)

2. Primary application server instance

3. ASCS instance

4. ERS instance for the ASCS instance (if available)

5. Database instance

8.10.3 Starting and Stopping the Diagnostics Agent

The Diagnostics Agent is started at the end of the installation. You can start and stop the Diagnostics Agent by running sapcontrol. The sapcontrol executable is located in the Diagnostics Agent instance specific exe directory:

● /usr/sap/<DASID>/SMDA<Instance_Number>/exeSee also section SAP Directories [page 57].

NoteYou can only start or stop the Diagnostics Agent separately. It is not started or stopped automatically with an SAP system that you start or stop.

You can also use the SAP Management Console (SAP MC) to start or stop the Diagnostics Agent. For more information see Starting and Stopping SAP System Instances Using the SAP Management Console [page 138].

Procedure

You have logged on to the host as <dasid>adm.

● To start or stop the Diagnostics Agent system (all instances) with sapcontrol, enter one of the following commands:

sapcontrol -prot PIPE -nr <Instance_Number> -function StartSystemsapcontrol -prot PIPE -nr <Instance_Number> -function StopSystem

144




● To start or stop a single Diagnostics Agent instance with sapcontrol, enter one of the following commands:

sapcontrol -prot PIPE -nr <Instance_Number> -function Startsapcontrol -prot PIPE -nr <Instance_Number> -function Stop

8.11 Creating a User for LDAP Directory Access

If you use LDAP directory services, you have to set up a user with a password on the host where the SAP system is running. This permits the SAP system to access and modify the LDAP directory.

For more information, see Integration of LDAP Directory Services in the Windows installation guide for your SAP system solution and database.

Prerequisites

During the SAP instance installation you chose to configure the SAP system to integrate LDAP services.

Procedure

1. Log on as user <sapsid>adm.

2. Enter:

ldappasswd pf=<path_and_name_of_instance_profile>3. Enter the required data.

ExampleThe following is an example of an entry to create an LDAP Directory User:

CN=sapldap,CN=Users,DC=nt5,DC=sap-ag,DC=de

8.12 Heterogeneous SAP System Installation

This section provides information on the installation of an SAP system in a heterogeneous system landscape. “Heterogeneous system landscape” means that application servers run on different operating systems.

Procedure

See SAP Note 1067221 for more information on:

● Supported combinations of operating systems and database systems

● How to install an application server on Windows in a heterogeneous (UNIX) SAP system environment

● Heterogeneous SAP system landscapes with different UNIX operating systems





8.13 Deleting an SAP System or Single Instances

This section describes how to delete a complete SAP system or single SAP instances with the Uninstall option of the installer.

Note the following when deleting an SAP system or single instances:

● We strongly recommend that you delete an SAP system or single instances using the installer. However, you can also delete an SAP system or single instance manually. For more information, see SAP Note 1259982.

● During the uninstall process, all file systems and subdirectories of the selected SAP system or single instance are deleted. Before you start uninstalling, check that you have saved a copy of all files and directories that you want to keep to a secure location.

● The uninstall process is designed to remove as much as possible of the SAP system to be deleted. If an item cannot be removed, a message informs you that you have to remove this item manually. You can do this either at once or after the uninstall process has finished. As soon as you confirm the message, the uninstall process continues.

Prerequisites

● You have installed your SAP system with standard SAP tools according to the installation documentation.

● You are logged on as user root.

● Make sure that the SAP system, or single instance, or standalone engine, or optional standalone unit to be deleted is down and that you are not logged on as one of the SAP system users. Also check that all SAP-related processes are stopped. If there is a lock on one of the SAP system objects, the uninstall fails.

NoteYou do not have to stop the SAP Host Agent. The SAP Host Agent is stopped automatically during the uninstall process.

● When starting the uninstall, make sure that there are no SAP system user sessions still open.

Procedure

1. Start the installer as described in Running the Installer [page 77].

2. On the Welcome screen, choose:

Generic Installation Options <Database> Uninstall Uninstall – SAP Systems or Single Instances

3. Follow the instructions on the installer screens to delete a complete SAP system or single instances.

NoteFor more information about the input parameters, place the cursor on the relevant field and press F1 in the installer.

The following table provides information about deleting a complete system or single instances with the installer.

146





Table 69

Deletion of Remarks

Additional application server If you want to delete additional application server instances of an existing SAP system, you have to run the installer to delete them locally on each additional application server instance host.

Diagnostics Agent If you want to delete a Diagnostics Agent instance, enter the location of the profile directory of the Diagnostics Agent that you want to uninstall on the General SAP System Parameters screen:

/usr/sap/<DASID>/SYS/profile

Standalone SAP Host Agent The SAP Host Agent is automatically uninstalled from a host together with the last remaining SAP system instance.

If you want to uninstall a standalone SAP Host Agent, deselect Profiles Available and select Uninstall Standalone SAP Host Agent on the General SAP System Parameters screen.

4. When you have finished, delete the relevant directory structure on the global host.

5. If you created the directories /usr/sap/<SAPSID> and /<sapmnt>/<SAPSID> as mount points, but not as directories on the local file system, you have to remove them manually.

6. To remove obsolete SLD data, see the following document:

scn.sap.com/docs/DOC-8516 How-to Manage House-Cleaning in the System Landscape Directory - Duplicate System Entries

A Appendix

A.1 Online Information from SAP

More information is available online as follows:

Table 70: Documentation

Description Internet Address Title

Database Administration Guide for SAP systems running with SAP Adaptive Server Enteprise

service.sap.com/instguidesnw <SAP

NetWeaver Release> Operations Database-

Specific Guides

Database Administration Guide: SAP Applications on SAP Adaptive Server Enterprise

SAP Security Guide for SAP systems running with SAP Adaptive Server Enterprise

service.sap.com/instguidesnw <SAP

NetWeaver Release> Operations Database-

Specific Guides

Security Guide for SAP Application on SAP Adaptive Server Enterprise

SAP Front End installation Guide service.sap.com/instguidesnw <SAP

NetWeaver Release> Installation Installation -

Clients

SAP Front End Installation Guide – <Current Release>

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseAppendix




http://service.sap.com/instguidesnw



Description Internet Address Title

Copying SAP Systems Based on SAP NetWeaver 7.1 or Higher Using Software Provisioning Manager 1.0

service.sap.com/sltoolset Software Logistics Toolset 1.0 System Provisioning

System Copy Guide — SAP Systems Based on the Application Server <Technology> of SAP NetWeaver on <OS>

Maintenance Planning Guide service.sap.com/mopz How-Tos and Guides Maintenance Planning Guide for SAP Solution Manager <Release, SP>

Table 71: General Quick Links

Description Internet Address

SAP Help Portal help.sap.com

SAP Help Portal - SAP Adaptive Server Enterprise

help.sap.com/adaptive-server-enterprise

SAP Applicatons on SAP Adaptive Server Enterprise

scn.sap.com/community/ase

SAP NetWeaver Library in SAP Help Portal

help.sap.com/netweaver

SL Toolset service.sap.com/sltoolset

Installation Guides service.sap.com/instguides

Software logistics in application lifecycle management

scn.sap.com/community/it-management/alm/software-logistics

SAP Notes service.sap.com/notes

Supported platforms and operating systems

scn.sap.com/community/database Related Resources

Product availability matrix (PAM) service.sap.com/pam

Release Notes service.sap.com/releasenotes

Unicode SAP systems and their availability

service.sap.com/unicode

System sizing (Quick sizer tool) service.sap.com/sizing

SAP NetWeaver capabilities scn.sap.com/community/netweaver

Application lifecycle management for SAP NetWeaver

scn.sap.com/community/it-management/alm

Security for SAP NetWeaver scn.sap.com/community/security

Information on SAP support package stacks

service.sap.com/sp-stacks

SAP Solution Manager service.sap.com/solutionmanager

148



Appendix


http://service.sap.com/mopz

http://help.sap.com

http://help.sap.com/adaptive-server-enterprise

http://scn.sap.com/community/ase

http://help.sap.com/netweaver



http://scn.sap.com/community/it-management/alm/software-logistics

http://service.sap.com/notes

http://scn.sap.com/community/database

http://service.sap.com/pam

http://service.sap.com/releasenotes

http://service.sap.com/unicode

http://service.sap.com/sizing

http://scn.sap.com/community/netweaver

http://scn.sap.com/community/it-management/alm

http://scn.sap.com/community/security

http://service.sap.com/sp-stacks

http://service.sap.com/solutionmanager

Description Internet Address

Maintenance optimizer service.sap.com/solman-mopz

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseAppendix



http://service.sap.com/solman-mopz

Legal Software Terms

Terms for Included Open Source Software

This document contains information respecting free and open-source software (collectively, “FOSS”) included in or provided with the product (“Product”) that this document accompanies. Any terms, conditions, and restrictions governing the use or distribution of FOSS that are offered or imposed by SAP and are not contained within the FOSS license(s) governing the use and distribution of the FOSS, are offered and imposed by SAP alone. The authors, licensors, and distributors of the FOSS have disclaimed all warranties relating to any liability arising from the use and distribution of the FOSS.

While SAP has sought to provide a complete and accurate listing of the FOSS components included in or provided with the Product, SAP does not represent or warrant that the listing of FOSS components and associated notices and licensing information provided herein are complete or error-free. Recipients of the Product should investigate the listed FOSS components to confirm the accuracy of the notices and licensing information provided herein. Recipients are encouraged to notify SAP of any inaccurate information or errors found in this document.

If you have any questions or concerns please contact SAP by email at [email protected] or via mail at Dietmar Hopp Allee 16, 69190 Walldorf, Germany, Attn: Global Legal.

● Mozilla SpiderMonkey

Licensor: Mozilla Developer Network and individual contributors

Website: developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey

License: Mozilla Public License version 2.0

1. Definitions

1. “Contributor”

means each individual or legal entity that creates, contributes to the creation of, or owns Covered Software.

2. “Contributor Version”

means the combination of the Contributions of others (if any) used by a Contributor and that particular Contributor’s Contribution.

3. “Contribution”

means Covered Software of a particular Contributor.

4. “Covered Software”

means Source Code Form to which the initial Contributor has attached the notice in Exhibit A, the Executable Form of such Source Code Form, and Modifications of such Source Code Form, in each case including portions thereof.

5. “Incompatible With Secondary Licenses” means

1. that the initial Contributor has attached the notice described in Exhibit B to the Covered Software; or

2. that the Covered Software was made available under the terms of version 1.1 or earlier of the License, but not also under the terms of a Secondary License.

6. “Executable Form”

150




https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey

means any form of the work other than Source Code Form.

7. “Larger Work”

means a work that combines Covered Software with other material, in a separate file or files, that is not Covered Software.

8. “License”

means this document.

9. “Licensable”

means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently, any and all of the rights conveyed by this License.

10. “Modifications”

means any of the following:

1. any file in Source Code Form that results from an addition to, deletion from, or modification of the contents of Covered Software; or

2. any new file in Source Code Form that contains any Covered Software.

11. “Patent Claims” of a Contributor

means any patent claim(s), including without limitation, method, process, and apparatus claims, in any patent Licensable by such Contributor that would be infringed, but for the grant of the License, by the making, using, selling, offering for sale, having made, import, or transfer of either its Contributions or its Contributor Version.

12. “Secondary License”

means either the GNU General Public License, Version 2.0, the GNU Lesser General Public License, Version 2.1, the GNU Affero General Public License, Version 3.0, or any later versions of those licenses.

13. “Source Code Form”

means the form of the work preferred for making modifications.

14. “You” (or “Your”)

means an individual or a legal entity exercising rights under this License. For legal entities, “You” includes any entity that controls, is controlled by, or is under common control with You. For purposes of this definition, “control” means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity.

2. License Grants and Conditions

1. Grants

Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license:

1. under intellectual property rights (other than patent or trademark) Licensable by such Contributor to use, reproduce, make available, modify, display, perform, distribute, and otherwise exploit its Contributions, either on an unmodified basis, with Modifications, or as part of a Larger Work; and

2. under Patent Claims of such Contributor to make, use, sell, offer for sale, have made, import, and otherwise transfer either its Contributions or its Contributor Version.

2. Effective Date

The licenses granted in Section 2.1 with respect to any Contribution become effective for each Contribution on the date the Contributor first distributes such Contribution.

3. Limitations on Grant Scope

SAP Systems Based on the Application Server ABAP of SAP NetWeaver on UNIX: SAP Adaptive Server EnterpriseLegal Software Terms



The licenses granted in this Section 2 are the only rights granted under this License. No additional rights or licenses will be implied from the distribution or licensing of Covered Software under this License. Notwithstanding Section 2.1.2 above, no patent license is granted by a Contributor:

1. for any code that a Contributor has removed from Covered Software; or

2. for infringements caused by: (i) Your and any other third party’s modifications of Covered Software, or (ii) the combination of its Contributions with other software (except as part of its Contributor Version); or

3. under Patent Claims infringed by Covered Software in the absence of its Contributions.

This License does not grant any rights in the trademarks, service marks, or logos of any Contributor (except as may be necessary to comply with the notice requirements in Section 3.4).

4. Subsequent Licenses

No Contributor makes additional grants as a result of Your choice to distribute the Covered Software under a subsequent version of this License (see Section 10.2) or under the terms of a Secondary License (if permitted under the terms of Section 3.3).

5. Representation

Each Contributor represents that the Contributor believes its Contributions are its original creation(s) or it has sufficient rights to grant the rights to its Contributions conveyed by this License.

6. Fair Use

This License is not intended to limit any rights You have under applicable copyright doctrines of fair use, fair dealing, or other equivalents.

7. Conditions

Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted in Section 2.1.

3. Responsibilities

1. Distribution of Source Form

All distribution of Covered Software in Source Code Form, including any Modifications that You create or to which You contribute, must be under the terms of this License. You must inform recipients that the Source Code Form of the Covered Software is governed by the terms of this License, and how they can obtain a copy of this License. You may not attempt to alter or restrict the recipients’ rights in the Source Code Form.

2. Distribution of Executable Form

If You distribute Covered Software in Executable Form then:

1. such Covered Software must also be made available in Source Code Form, as described in Section 3.1, and You must inform recipients of the Executable Form how they can obtain a copy of such Source Code Form by reasonable means in a timely manner, at a charge no more than the cost of distribution to the recipient; and

2. You may distribute such Executable Form under the terms of this License, or sublicense it under different terms, provided that the license for the Executable Form does not attempt to limit or alter the recipients’ rights in the Source Code Form under this License.

3. Distribution of a Larger Work

You may create and distribute a Larger Work under terms of Your choice, provided that You also comply with the requirements of this License for the Covered Software. If the Larger Work is a combination of Covered Software with a work governed by one or more Secondary Licenses, and the Covered Software is not Incompatible With Secondary Licenses, this License permits You to additionally distribute such Covered Software under the terms of such Secondary License(s), so that the recipient of the Larger

152




Work may, at their option, further distribute the Covered Software under the terms of either this License or such Secondary License(s).

4. Notices

You may not remove or alter the substance of any license notices (including copyright notices, patent notices, disclaimers of warranty, or limitations of liability) contained within the Source Code Form of the Covered Software, except that You may alter any license notices to the extent required to remedy known factual inaccuracies.

5. Application of Additional Terms

You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Software. However, You may do so only on Your own behalf, and not on behalf of any Contributor. You must make it absolutely clear that any such warranty, support, indemnity, or liability obligation is offered by You alone, and You hereby agree to indemnify every Contributor for any liability incurred by such Contributor as a result of warranty, support, indemnity or liability terms You offer. You may include additional disclaimers of warranty and limitations of liability specific to any jurisdiction.

4. Inability to Comply Due to Statute or Regulation

If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Software due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be placed in a text file included with all distributions of the Covered Software under this License. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it.

5. Termination

1. The rights granted under this License will terminate automatically if You fail to comply with any of its terms. However, if You become compliant, then the rights granted under this License from a particular Contributor are reinstated (a) provisionally, unless and until such Contributor explicitly and finally terminates Your grants, and (b) on an ongoing basis, if such Contributor fails to notify You of the non-compliance by some reasonable means prior to 60 days after You have come back into compliance. Moreover, Your grants from a particular Contributor are reinstated on an ongoing basis if such Contributor notifies You of the non-compliance by some reasonable means, this is the first time You have received notice of non-compliance with this License from such Contributor, and You become compliant prior to 30 days after Your receipt of the notice.

2. If You initiate litigation against any entity by asserting a patent infringement claim (excluding declaratory judgment actions, counter-claims, and cross-claims) alleging that a Contributor Version directly or indirectly infringes any patent, then the rights granted to You by any and all Contributors for the Covered Software under Section 2.1 of this License shall terminate.

3. In the event of termination under Sections 5.1 or 5.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or Your distributors under this License prior to termination shall survive termination.

6. Disclaimer of Warranty

Covered Software is provided under this License on an “as is” basis, without warranty of any kind, either expressed, implied, or statutory, including, without limitation, warranties that the Covered Software is free of defects, merchantable, fit for a particular purpose or non-infringing. The entire risk as to the quality and performance of the Covered Software is with You. Should any Covered Software prove defective in any respect, You (not any Contributor) assume the cost of any necessary servicing, repair, or correction. This disclaimer of warranty constitutes an essential part of this License. No use of any Covered Software is authorized under this License except under this disclaimer.




7. Limitation of Liability

Under no circumstances and under no legal theory, whether tort (including negligence), contract, or otherwise, shall any Contributor, or anyone who distributes Covered Software as permitted above, be liable to You for any direct, indirect, special, incidental, or consequential damages of any character including, without limitation, damages for lost profits, loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses, even if such party shall have been informed of the possibility of such damages. This limitation of liability shall not apply to liability for death or personal injury resulting from such party’s negligence to the extent applicable law prohibits such limitation. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so this exclusion and limitation may not apply to You.

8. Litigation

Any litigation relating to this License may be brought only in the courts of a jurisdiction where the defendant maintains its principal place of business and such litigation shall be governed by laws of that jurisdiction, without reference to its conflict-of-law provisions. Nothing in this Section shall prevent a party’s ability to bring cross-claims or counter-claims.

9. Miscellaneous

This License represents the complete agreement concerning the subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not be used to construe this License against a Contributor.

10. Versions of the License

1. This License represents the complete agreement concerning the subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not be used to construe this License against a Contributor. 10. Versions of the License 10.1. New Versions Mozilla Foundation is the license steward. Except as provided in Section 10.3, no one other than the license steward has the right to modify or publish new versions of this License. Each version will be given a distinguishing version number.

2. Effect of New Versions

You may distribute the Covered Software under the terms of the version of the License under which You originally received the Covered Software, or under the terms of any subsequent version published by the license steward.

3. Modified Versions

If you create software not governed by this License, and you want to create a new license for such software, you may create and use a modified version of this License if you rename the license and remove any references to the name of the license steward (except to note that such modified license differs from this License).

4. Distributing Source Code Form that is Incompatible With Secondary Licenses

If You choose to distribute Source Code Form that is Incompatible With Secondary Licenses under the terms of this version of the License, the notice described in Exhibit B of this License must be attached.

Exhibit A – Source Code Form License Notice

This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at mozilla.org/MPL/2.0/.

If it is not possible or desirable to put the notice in a particular file, then You may include the notice in a location (such as a LICENSE file in a relevant directory) where a recipient would be likely to look for such a notice.

154




http://mozilla.org/MPL/2.0/

5. You may add additional accurate notices of copyright ownership.

6. Exhibit B – “Incompatible With Secondary Licenses” Notice This Source Code Form is “Incompatible With Secondary Licenses”, as defined by the Mozilla Public License, v. 2.0.

● zlib

Licensor: Jean-loup Gailly and Mark Adler

Website: www.zlib.net/

License: Copyright (C) 1995-2013 Jean-loup Gailly and Mark Adler

zlib.h – interface of the “zlib” general purpose compression library version 1.2.8, April 28th, 2013

Copyright (C) 1995-2013 Jean-loup Gailly and Mark Adler

This software is provided “as-is”, without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

Jean-loup Gailly ([email protected])

Mark Adler ([email protected])

● STLPort

Licensor: Boris Fomitchev

WebSite: www.stlport.org/

License Agreement

Boris Fomitchev grants Licensee a non-exclusive, non-transferable, royalty-free license to use STLport and its documentation without fee.

By downloading, using, or copying STLport or any portion thereof, Licensee agrees to abide by the intellectual property laws and all other applicable laws of the United States of America, and to all of the terms and conditions of this Agreement.

Licensee shall maintain the following copyright and permission notices on STLport sources and its documentation unchanged:

Copyright 1999,2000 Boris Fomitchev

This material is provided “as is”, with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. The Licensee may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. The Licensee may distribute original or modified STLport sources, provided that:

○ The conditions indicated in the above permission notice are met;

○ The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met:

Copyright 1994 Hewlett-Packard Company




http://www.zlib.net/

http://www.stlport.org/

Copyright 1996,97 Silicon Graphics Computer Systems, Inc.

Copyright 1997 Moscow Center for SPARC Technology.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC Technology makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.

● Flexler 1.18

Copyright (c) 1993 The Regents of the University of California.

All rights reserved.

This code is derived from software contributed to Berkeley by Kent Williams and Tom Epperly.

Redistribution and use in source and binary forms are permitted provided that: (1) source distributions retain this entire copyright notice and comment, and (2) distributions including binaries display the following acknowledgement: “This product includes software developed by the University of California, Berkeley and its contributors” in the documentation or other materials provided with the distribution and in all advertising materials mentioning features or use of this software. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

156




www.sap.com

© Copyright 2014 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.Please see www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

http://www.sap.com

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx

Date post:	21-Dec-2015
Category:	Documents
Upload:	pamela-cristina-santos
View:	60 times
Download:	18 times

NW Inst Guide ASE Linux

Documents