adaptivecomputing controller 7.1 on hp-ux:maxdb

PUBLIC

Installation Guide

Adaptive ComputingController 71 onHP-UX MaxDBIncluding

SAP NetWeaver Application Server Java (AS Java)

Target Audience

n Technology Consultants

n System Administrators

Document version 10 ‒ 12142007

Document History

Caution

Before you start the implementation make sure you have the latest version of this document Youcan find the latest version at the following locationhttpservicesapcominstguides

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

Version Date Description

10 12142007 Initial Version

2148 PUBLIC 12142007

Table of Contents

Chapter 1 Introduction 711 How to Use This Guide 712 New Features 813 SAP Notes for the Installation 1014 Information Available on SAP Service Marketplace 1115 Accessing the SAP Library 1316 Naming Conventions 13

Chapter 2 Planning 1521 Installation Options Covered by this Guide 15211 Standard System 16212 Distributed System 16213 High-Availability System 17214 Additional Application Server Instance 18215 Standalone Host Agent 2122 Distribution of Components to Disks 2223 MaxDB System Configuration 2524 Running Adobe Document Services on Non-Supported Platforms 2625 Integration of LDAP Directory Services 2726 Planning the Switchover Cluster 31

Chapter 3 Preparation 3531 Basic SAP System Parameters 3732 Hardware and Software Requirements 43321 Running the Prerequisite Checker in Standalone Mode (Optional) 45322 Requirements for HP-UX 46323 Requirements for a Standard System 48324 Requirements for a Distributed System 483241 Requirements for a Central Services Instance 493242 Requirements for the Database Instance 493243 Requirements for the Primary Application Server Instance 50325 Requirements for a High Availability System 513251 Requirements for a Central Services Instance 513252 Requirements for an Enqueue Replication Server Instance 523253 Requirements for the Database Instance 53

12142007 PUBLIC 3148

3254 Requirements for the Primary Application Server Instance 54326 Requirements for an Additional Application Server Instance 54327 Requirements for a Standalone Host Agent 55328 Checking and Modifying the HP-UX Kernel 56329 Setting up Swap Space for HP-UX 5833 Performing Switchover Preparations for High Availability 6034 Creating Operating System Users and Groups 60341 Creating HP-UX Groups and Users (Optional) 6235 Preparing User Management for an External ABAP System 6336 Setting Up File Systems and Raw Devices 66361 SAP Directories 67362 MaxDB Directories 69363 Host Agent Directories 70364 Setting Up File Systems for a High-Availability System 70365 Configuring Network File System for a High-Availability System 72366 Setting Up File Systems and Raw Devices for HP-UX 7437 Exporting and Mounting the Global Transport Directory 8138 Exporting and Mounting Directories via NFS for HP-UX (Optional) 8239 Generating the SAP Solution Manager Key 86310 Preparing the Installation DVDs 87311 Creating a User for LDAP Directory Access 90

Chapter 4 Installation 9141 Exporting and Mounting Global Directories 9442 High Availability Specifying the Virtual Host Name 9443 Running SAPinst 9544 SAPinst Installation Options 100

Chapter 5 Post-Installation 10551 Logging On to the Application Server 10652 Installing the SAP License 10753 Configuring the Transport Management System 10754 Configuring the Remote Connection to SAP Support 10855 Applying the Latest Kernel and Support Packages 10856 High Availability Setting Up Licenses 10957 Installing Administration Tools for MaxDB 11158 Secure Sockets Layer Protocol for Database Server Communication 112581 Installing the SAP Cryptographic Library 113582 Generating the Personal Security Environment 11459 Backing Up the MaxDB Database 117510 Updating the Database Software to the Current Release 117511 Ensuring User Security 117

4148 PUBLIC 12142007

512 Configuring User Management to Use an LDAP Directory (Optional) 120513 Post-Installation Steps for the Host Agent 120514 Checking the SAP Java Documentation 121515 Configuring the Adaptive Computing Controller 122516 Performing a Full Installation Backup 123

Chapter 6 Additional Information 12561 Mounting a CD DVD for HP-UX 12562 Additional Information About SAPinst 127621 Interrupted Installation with SAPinst 127622 Performing a Remote Installation with SAPinst (Optional) 129623 Starting SAPinst GUI Separately (Optional) 130624 Entries in the Services File Created by SAPinst 132625 Troubleshooting with SAPinst 13363 Heterogeneous SAP System Installation 13364 Starting and Stopping the SAP System 134641 Starting and Stopping the SAP System Using the SAP Management Console 134642 Starting and Stopping the SAP System Using Scripts 13765 High Availability Finalizing the Enqueue Replication Server 14166 Deleting an SAP System 142

12142007 PUBLIC 5148

6148 PUBLIC 12142007

1 Introduction

1 Introduction

This document explains how to install the ldquoAdaptive Computing Controller in SAP NetWeaver71rdquo (ACC) using the installation tool SAPinstThe ACC is a system management like tool based on the Java EE engine of SAP NetWeaver 71Application Server (AS) Java It enables the system administrator to control the whole landscape froma single point through observation operation and dynamic resource distributionFor more information about the technology of ACC see httpsdnsapcomirjsdnadaptive

Constraints

You need to consider the following constraints before you start your installation

n Youmust only use the SAP installation tools according to the instructions and for the purposesdescribed in the SAP installation document Improper use of the SAP installation tools can damagefiles and systems already installed

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

n For downward-compatible releases of DBOS platforms for SAP products SAP plans to regularlyrelease the newest database (DB) and operating-system (OS) versions of SAP products Thesereleases are downward-compatible with earlier SAP system releasesNote that for already shipped SAP components we only support the installation for databaseversions proposed by the installation tool Therefore you must install a SAP component orperform a system copy using a downward-compatible database as followsl Install the component with the old proposed database versionl Upgrade the old database version to the downward-compatible new version

11 How to Use This Guide

At the beginning of each installation phase ‒ planning preparation installation and post-installation‒ you can find a list of the steps that you have to perform in that phase as well as additionalinformation Detailed information about the steps for each phase is available in the relevant chapterWhen you plan the installation you have to decide what exactly you want to install because the stepswithin each phase vary according to the installation option you chooseThe following installation options are described in this document

n Standard system (formerly known as central system)n Distributed system

12142007 PUBLIC 7148

1 Introduction12 New Features

n

Only valid for HA (UNIX)

High-availability systemEnd of HA (UNIX)

n One or more additional application server instance(s) for an existing standard distributed orhigh-availability system

n Standalone host agent

12 New Features

Here you can find the new features in this release

Caution

Make sure that you read the release notes for your SAP system You can find these on SAP ServiceMarketplace at httpservicesapcomreleasenotes

SAP System Installation

Area Description

SAPinst SAPinst has the following new featuresn The technical terms used for the instances of an SAP system have changed as followsl ldquoCentral instancerdquo (CI) is now called ldquoprimary application server instancerdquol ldquoDialog instancerdquo (DI) is now called ldquoadditional application server instancerdquo

NoteThe technical terms ldquoDatabase instancerdquo ldquoJava central services instancerdquo (SCS) andldquoABAP central services instancerdquo (ASCS) remain unchanged

n ldquoCentral systemrdquo ‒ meaning an SAP system running on one single host ‒ is nowcalled ldquostandard systemrdquo

nOnly valid for HA (UNIX)

You can now install the enqueue replication server (ERS) with SAPinst There is anew installation option Enqueue Replication Server Instance available for the installationoptions Distributed System and High-Availability SystemEnd of HA (UNIX)

n Host agentThe host agent contains all of the required elements for centrally monitoringany host with the Alert Monitor or the SAP NetWeaver Administrator It isautomatically installed during the installation of all SAP NetWeaver componentsexcept TREXThe host agent is automatically installed with your SAP systemYou can also install a standalone host agent with SAPinst There is a new installationoption Host Agent available under Software Life-Cycle Options Additional Preparations You only need to install a standalone host agent in the following cases

8148 PUBLIC 12142007


Area Description

l You want to centrally monitor a host that does not have an SAP componentl You want to perform an upgrade to SAP NetWeaver

n The locations of all installation DVDs can be entered on one screen

SoftwareDeploymentManager (SDM)no longer availablein the ApplicationServer Java

The Software Deployment Manager (SDM) is no longer part of the primary applicationserver instance of a Java-only system Therefore there is no longer any technicaldifference between the primary application server instance and the additionalapplication server instance of a Java-only systemThe SAP system directory of both instances is now called Jltinstance_numbergtJCltinstance_numbergt no longer existsFor more information see SAP Directories [page 67]

Usage type EP Core(EPC)

The usage type Enterprise Portal (EP) is divided into the usage types EP Core (EPC)and Enterprise Portal (EP)n EP Core (EPC)

This usage type contains the core portal capabilities that were available in the formerusage type EP This new usage type provides more flexibility when implementing aportal where the full enterprise portal capabilities such as knowledge managementand collaboration are not required It contains the portal GP and UWL

n Enterprise Portal (EP)This usage type includes Knowledge management Collaboration CAF-Core VisualComposer Web Dynpro extension and NET PDK

Usage type EPC is a prerequisite for usage type EP If you want to obtain the fullcapabilities of the former usage type EP you need both EP Core and EPThe configuration of EPC comprises only portal configuration steps

NoteThe standalone implementation of the new usage type EPC without usage type EP iscurrently limited to certain ERP scenarios as described in themySAP ERPMaster Guide

Installation DVDs You start the installation from the Installation Master DVD for your database

SAP Java VirtualMachine (SAP JVM)

You no longer have to download and install a Java Development Kit (JDK) from anothersoftware vendor as a prerequisite for the installation with SAPinstThe SAP JVM is a Java Development Kit (JDK) provided and supported by SAP The SAPJVM is fully compliant to the Java Standard Edition 5 It is available on the InstallationMaster DVD and is installed automatically by SAPinst when you start the installation

VisualAdministratortool integratedin SAP NetWeaverAdministrator

SAP NetWeaver Administrator is a brand new solution formonitoring and administeringJava systems and their applications It is a web-based tool for administrationconfiguration and monitoringThe Visual Administrator tool is no longer available as a separate tool It has beenintegrated in the SAP NetWeaver AdministratorSAP NetWeaver Administrator offers you most of the functions previously available inVisual Administrator but redesigned for the task-oriented approach of SAP NetWeaverAdministratorFor more information about SAP NetWeaver Administrator see the SAP NetWeaverMaster Guide and SAP Service Marketplace at httpservicesapcomnwa

12142007 PUBLIC 9148

1 Introduction13 SAP Notes for the Installation

Operating Systems

Area Description

Support of OperatingSystems

The database and operating systems area in the SAP Developer Networkat httpsdnsapcomirjsdndbos provides forums blogs content andcommunity for all databases and operating system platforms that SAP supports

Documentation

Area Description

SAP Notes You can now access SAP Notes directly in SAP Service Marketplace from yourPDF Place the cursor on the SAP Note ldquoltnumbergtrdquo and double-click Aseparate browser windows opens and the SAP Note is displayed

Links to the Internet You can use the new links in the PDF files of the guides as followsn Click on the section headings such as New Features to jump back to the

table of contents at the beginning of the guiden Click on an internet link such as httpservicesapcom to jump to

the corresponding internet page

13 SAP Notes for the Installation

Youmust read the following SAP Notes before you start the installation These SAP Notes contain themost recent information on the installation as well as corrections to the installation documentationMake sure that you have the up-to-date version of each SAP Note which you can find in the SAPService Marketplace at httpservicesapcomnotes

SAP Notes for the Installation

SAP Note Number Title Description

966416 SAP NetWeaver Installation Based onKernel 710 UNIX

UNIX-specific information about theinstallation for SAP systems based on kernel710 and corrections to this documentation

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

966525 SAP NetWeaver Installation based onKernel 710 MaxDBUNIX

Platform-specific information about the SAPsystem installation (ABAP and Java) andcorrections to this documentation

820824 FAQ MaxDB Frequently asked questions (FAQ) onMaxDB

855498 Installation Prerequisite Checker SAP Software on UNIX Windows andSystem i Checking OS Dependencies

10148 PUBLIC 12142007

1 Introduction14 Information Available on SAP Service Marketplace



1067221 Central Note for HeterogeneousInstallation

Heterogeneous ABAP system landscapeson different operating systems have beenreleased for some time Heterogeneous Javasystem landscapes on different operatingsystems have now also been releasedHowever not every combination ofoperating system and database system isreleased This SAP Note and its related SAPNotes describe the released operating systemand database combinations

14 Information Available on SAP Service Marketplace

More information is available as follows on SAP Service Marketplace

Documentation

Description Internet Address Title

Master Guide for SAPNetWeaver ProcessIntegration 71

httpservicesapcominstguidesNWPI71

InstallationMaster Guide - SAP NetWeaverProcess Integration 71

TechnicalInfrastructure Guidefor SAP NetWeaverProcess Integration71


InstallationTechnical Infrastructure Guide- SAP NetWeaver ProcessIntegration 71

Master Guide forSAP NetWeaverCompositionEnvironment 71

httpsdnsapcom SAP NetWeaver CompositionEnvironment

Master Guide ‒ SAP NetWeaverComposition Environment 71

Master Guide SAPSolution Manager 40

httpservicesapcominstguides SAPComponents SAP Solution Manager Release 40

Master Guide ‒ SAP SolutionManager 40

12142007 PUBLIC 11148



MaintenanceOptimizer

httpservicesapcomsolutionmanager Functionsin Detail Support Area Maintenance Optimizer

All corrective softwarepackages - includingSupport Packages (Stacks)for SAP NetWeaver 71 andsubsequent versions - as wellas all applications based onthis software (including SAPBusiness Suite 2005) releasedafter April 2 2007 will beavailable exclusively throughthe Maintenance Optimizerin SAP Solution Manager

System Copy for SAPNetWeaver PI 71

httpservicesapcominstguidesnw ltyourproductgt Installation

System Copy for SAP NetWeaverPI 71

General Quick Links

Description Internet Address

SAP Help Portal httphelpsapcom

SAP NetWeaver Library in SAPHelp Portal

httphelpsapcomnwpi71

SAP Notes httpservicesapcomnotes

Released platforms and operatingsystems

httpsdnsapcomirjsdndbos

Product AvailabilityMatrix (PAM) httpservicesapcompam

Release notes httpservicesapcomreleasenotes

Unicode SAP systems and theiravailability

httpservicesapcomunicode

System sizing (Quick Sizer tool) httpservicesapcomsizing

SAP NetWeaver capabilities httpsdnsapcomirjsdnnetweaver

Life-cycle management for SAPNetWeaver

httpsdnsapcomirjsdnlcm

Landscape design for SAPNetWeaver

httpsdnsapcomirjsdnlandscapedesign

Application management for SAPNetWeaver

httpsdnsapcomirjsdnapplicationmanagement

Software logistics for SAPNetWeaver

httpsdnsapcomirjsdnsoftwarelogistics

SAP NetWeaver operations httpsdnsapcomirjsdnoperations

Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity

12148 PUBLIC 12142007

1 Introduction15 Accessing the SAP Library


Information on SAP SupportPackage Stacks

httpservicesapcomsp-stacks

SAP Solution Manager httpservicesapcomsolutionmanager

Maintenance Optimizer httpservicesapcomsolman-mopz

15 Accessing the SAP Library

For more information about SAP NetWeaver access the SAP Library from the SAP Help Portal athttphelpsapcomThe references to SAP NetWeaver Library documentation in this documentation always refer to thefollowing entry point on the SAP Help Portalhttphelpsapcomnwpi71 KNOWLEDGE CENTER FOR SAP NETWEAVER PROCESS

INTEGRATION 71 SAP NetWeaver Process Integration Library English

16 Naming Conventions

In this documentation the following naming conventions apply

Terminology

n SAP system refers to Adaptive Computing Controller in SAP NetWeaver 71n Java system refers to the Java EE engine of Adaptive Computing Controller in SAP NetWeaver 71

Variables

Variables Description

ltSAPSIDgt SAP system ID in uppercase letters

ltsapsidgt SAP system ID in lowercase letters

ltsidgt and ltsapsidgt SAP system ID in lowercase letters

ltDBSIDgt Database ID in uppercase letters

ltdbsidgt Database ID in lowercase letters

lthost_namegt Name of the corresponding host

ltuser_homegt Home directory of the user performing the installation

ltINSTDIRgt Installation directory for the SAP system

ltDVD_DIRgt Directory on which a DVD is mounted

12142007 PUBLIC 13148

1 Introduction16 Naming Conventions


ltOSgt Operating system name within a path

ltSCHEMAIDgt Database schema ID

The following example shows how the variables are used

Example

Log on as user ltsapsidgtadm and change to the directory usrsapltSAPSIDgtIf your SAP system ID is C11 log on as user c11adm and change to the directory usrsapC11

14148 PUBLIC 12142007

2 Planning

2 Planning

This section provides general planning informationYou must first

1 Plan your SAP system landscape according to theMaster Guide and the Technical Infrastructure Guideavailable for your product

2 Decide on your installation option [page 15]

Now continue with the section for your chosen installation option below

Standard Distributed or High-Availability System

1 You plan your system configuration [page 25]2 If you want to use Adobe Document Services (ADS) you check what you have to do if your platform is

not supported for ADS [page 26]3 You decide whether you want to integrate LDAP Directory Services in your SAP system [page 27]

4


If you want to install a high-availability system you read Planning the Switchover Cluster [page 31]End of HA (UNIX)

5 You can now continue with Preparation [page 35]

Additional Application Server Instance

You do not have to perform any planning stepsYou can immediately continue with Preparation [page 35]

Host Agent as a Standalone Installation


21 Installation Options Covered by this Guide

This section shows the installation options covered by this installation guide

n Standard system [page 16] (formerly known as central system)n Distributed system [page 16]

12142007 PUBLIC 15148

2 Planning21 Installation Options Covered by this Guide

n


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

n You can install one or more additional application server instance(s) [page 18] to an existing standarddistributed or high-availability system

n You can install a standalone host agent [page 21]

211 Standard System

You can install a standard system on a single hostIn a standard system all main instances run on a single host

n Central services instance (SCS)n Database instance (DB)n Primary application server instance

Figure 1 Standard Java System

Optionally you can install one or more additional application server instances For more informationsee Additional Application Server Instance [page 18]

212 Distributed System

In a distributed system every instance can run on a separate host

16148 PUBLIC 12142007



Note

You can also use the SAP transport host or the SAP global host as your primary applicationserver instance host

Optionally you can install one or more additional application server instances For more informationsee Installation of an Additional Application Server Instance [page 18]

Figure 2 Distributed Java System


213 High-Availability System

In a high-availability system every instance can run on a separate host

n Java Central Services Instance (SCS)n Database instance

n Primary application server instance

12142007 PUBLIC 17148


We recommend that you run both the ASCS and the SCS in a switchover cluster infrastructure Boththe ASCS and the SCS must each have their own Enqueue Replication Server (ERS) instanceOptionally you can install one to ltngt additional application server instances For more informationsee Installation of an Additional Application Server Instance [page 18]The following figures show examples for the distribution of the SAP instances in a high-availabilitysystem

Figure 3 High-Availability System

End of HA (UNIX)

214 Additional Application Server Instance

You can install one or more additional application server instance(s) for an existing SAP systemAn additional application server instance can run on

n The host of any instance of the existing SAP system (exceptions see below)n On a dedicated host

Additional Application Server Instance for a Standard System

For example the following figure shows each of the three additional application server instancesthat are running

18148 PUBLIC 12142007


n On the main host of the SAP system that is on the host on which the primary application serverinstance and the database instance run

n On dedicated hosts

Figure 4 Additional Application Server Instance for a Standard System

For additional information see Standard System [page 16]

Additional Application Server Instance for a Distributed System




It is not recommended to install additional application server instance(s) on the SAP global host

12142007 PUBLIC 19148


Figure 5 Additional Application Server Instance for a Distributed System

For additional information see Distributed System [page 16]


Additional Application Server Instance for a High-Availability System

For example the following figure shows each of the three additional application server instancesthat are running on

n The host of the primary application server instancen Dedicated hosts

It is not recommended to install additional application server instance(s) on the switchover clusterinfrastructure

20148 PUBLIC 12142007


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

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

215 Standalone Host Agent

Using the host agent you can centrally monitor any host with the Alert Monitor or the SAPNetWeaver Administrator It is automatically installed during the installation of all SAP NetWeavercomponentsYou only need to install a standalone host agent in the following cases

n You want to centrally monitor a host that does not have an SAP componentn You want to perform an upgrade to SAP NetWeaver

12142007 PUBLIC 21148

2 Planning22 Distribution of Components to Disks

Figure 7 Host Agent

The host agents contain the following elements

n The control program saphostexec

n The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)n The sapacosprep executable of the Adaptive Computing Infrastructuren The operating system collector saposcol

Note

The installed programs are automatically started when the host is bootedThe automatic start is ensured by the startup script sapinit that starts the required executables

More Information

For more information about the host agent see the SAP Library [page 13]Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Monitoring in the

CCMS Infrastructure of the NetWeaver Management Agents

22 Distribution of Components to Disks

When you install the SAP system the installation tools prompt you to enter drive letters for the maincomponents of the system This lets you distribute components to disks in the system as requiredHow you do this significantly affects system throughput and data security so you need to plan itcarefully

22148 PUBLIC 12142007


The best distribution depends on your environment and must reflect factors such as the size of thecomponents involved security requirements and the expected workloadWhen you work out the assignment of components to disks you first need to get an overview ofthe main components and their corresponding directories On the basis of sample configurationsand the recommendations provided in this documentation you can then choose the best setupfor your particular systemSAP systems are normally installed on RAID arrays to guarantee data redundancy Therefore thisdocumentation focuses on RAID subsystems and drives

FeaturesThe following graphic shows how you can distribute the main directories created during theinstallation to Redundant Arrays of Independent Disks (RAID) The distribution is suitable for anaverage-sized production system Keep in mind that this is only an example and that no singlesolution fits all environments

Figure 8 Directory Distribution for RAID

This configuration is suitable for the main host of a central system or the database server of astandalone database system You can assign the components on the left to any of the arrays shownYou do not necessarily have to place the transport directory on the central instance host

12142007 PUBLIC 23148


Array 1 ltDRIVEgtsapdbltDBSIDgtsapdataDISKD001

ltDRIVEgtsapdbltDBSIDgtsapdataDISKD999

Array 2 ltDRIVEgtsapdbltDBSIDgtsaplogDISKL001

ltDRIVEgtsapdbltDBSIDgtsaplogM_DISKL001

usrsap

ltDRIVEgtsapdb

ltDRIVEgtsapdbltDBSIDgtsapsys

Array 3 ltDRIVEgtsapdbltDBSIDgtsaplogM_DISKL001

ltDRIVEgtsapdbltDBSIDgtsaplogDISKL001

This setup has the following key features

n Security of the LogsThe security of the logs is crucial The logs record all the changes made to the database and soprovide the information that is necessary to recover a damaged database Therefore it is importantthat they are stored very securely and are never lost at the same time as the database data Byplacing the redo logs on a different array to the database data you can make sure that they arenot lost if the array with the database data is severely damaged

n PerformanceYou can reduce IO bottlenecks by placing the original logical log on a different array than themirrored log Original and mirrored logs are written in parallel If they are located on the samearray this results in a high level of write activity that has to be handled by the same controllerBy separating original and mirrored logs you can distribute the write activity to two differentarrays so reducing IO bottlenecks

n RAIDBy using RAID 1 arrays for the original and mirrored logs you get high data security and goodperformance The data is written to a primary disk and duplicated identically to a second disk Ifone disk fails the data is still intact on the second diskThe use of RAID 5 for the database ensures fault tolerance The data is striped over all the disksin the array together with parity information If one disk fails the parity information is used toautomatically reconstruct the data lost on the damaged disk

n Number of RAID ArraysIn the example above three RAID 1 arrays are used for the redo logs to achieve optimalperformance and security If you do not need the disk capacity offered by three arrays and canaccept reduced performance consider using a single array In this case you can use a single RAID 1array for the original and mirrored logs

24148 PUBLIC 12142007

2 Planning23 MaxDB System Configuration

23 MaxDB System Configuration

Security Issues

n For security reasons the logs must be mirrored using the operating system or hardware

Caution

If a system runs without mirroring you might lose all data since the last complete backup in theevent of a disk crash

Recommendation

We recommend mirroring the logs using the operating system or hardwareIf this is not possible then mirror the logs with the database mirroring provided by MaxDB

n We recommend you to run the database with raw devices

Caution

Never use RAID 5 systems for database log volumes

n Do not replace file systems by softlinksn Raw devices are very secure in the event of a system crash

Security Concept for Database Software Owner

As of MaxDB 7500 there is a new security concept for the database software owner Authorization toaccess directories and files is restricted and a new user and user group is required

n User is sdb (MaxDB default)n User group is sdba (MaxDB default)

This user and group are the only database software owners on the host For security reasons theuser does not have a logon for the system which guarantees the physical integrity of the databasefiles Database processes run under this user which makes sure that several different users cannotmanipulate the database system

Performance Issues

n Store database data files and logs on different disksn As the logs are written synchronously they produce the most IO activity of all database filesn It is possible to put the logs on the same disk assapmnt but this is not recommendedn Use the partitions DISKDltNgt exclusively for data files of the databasen If paging or swapping areas and log data reside on the same disk the performance will be

extremely poorn For database volumes raw devices are faster than files The slowest disk drive determines the IO

performance of the database

12142007 PUBLIC 25148

2 Planning24 Running Adobe Document Services on Non-Supported Platforms

Different MaxDB Systems

For performance reasons we normally recommend that you do not install several database systems(for different SAP systems) on one single host If you still decide to do so you must install eachdatabase as described in this documentation

Recommended Configuration

The following graphic shows an optimal distribution of the database data on different disksOptimal Distribution

Figure 9

For more information on the file systems for the SAP system and the MaxDB database see SettingUp File Systems and Raw Devices [page 66]

24 Running Adobe Document Services on Non-SupportedPlatforms

Adobe document services (ADS) are currently not supported to run natively on all platformssupported by SAP systems based on SAP NetWeaver in particular on 64-bit platforms

26148 PUBLIC 12142007

2 Planning25 Integration of LDAP Directory Services

ProcedureTo use ADS in SAP landscapes on non-supported platforms install an additional standalone ASJava on a platform supported by ADSFor more information see SAP Note 925741

More InformationFor more information about running ADS on SAP systems based on SAP NetWeaver seehttpsdnsapcomirjsdnadobe

25 Integration of LDAP Directory Services

This section explains the benefits of using the SAP system with the Lightweight Directory AccessProtocol (LDAP) directory and gives an overview of the configuration steps required to use an SAPsystem with the directoryLDAP defines a standard protocol for accessing directory services which is supported by variousdirectory products such as Microsoft Active Directory and OpenLDAP slapd Using directory servicesenables important information in a corporate network to be stored centrally on a server Theadvantage of storing information centrally for the entire network is that you only have to maintaindata once which avoids redundancy and inconsistencyIf an LDAP directory is available in your corporate network you can configure the SAP system to usethis feature For example a correctly configured SAP system can read information from the directoryand also store information there

Note

The SAP system can interact with the Active Directory using the LDAP protocol which defines

n The communication protocol between the SAP system and the directory

n 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 cantake advantage of the information stored there For example if there is an LDAP directory on a UNIXor Windows server you can configure the SAP system to use the information available there In thefollowing text directories other than the Active Directory that implement the LDAP protocol arecalled generic LDAP directories

12142007 PUBLIC 27148


Caution

This section does not provide information about the use of LDAP directories with the LDAPConnector For more information about using and configuring the LDAP Connector for an ABAPsystem see the SAP Library [page 13]Function-Oriented View Security Identity Management Identity Management of the Application Server ABAP

Configuration of Identity Management Directory Services LDAP Connector

PrerequisitesYou can only configure the SAP system for Active Directory services or other LDAP directories ifthese are already available on the network As of Windows 2000 or higher the Active Directoryis automatically available on all domain controllers A generic LDAP directory is an additionalcomponent that you must install separately on a UNIX or Windows server

FeaturesIn the SAP environment you can exploit the information stored in an Active Directory or genericLDAP directory by using

n SAP Logonn The SAP Microsoft Management Console (SAP MMC)n The SAP Management Console (SAP MC)

For more information about the automatic registration of SAP components in LDAP directories andthe benefits of using it in SAP Logon and SAP MMC see the documentation SAP System Information inDirectory Services on SAP Service Marketplace athttpservicesapcommsplatforms Microsoft Windows Server

For more information about the SAP MC and about how to configure it to access LDAP Directoriessee the documentation SAP Management Console in the SAP Library [page 13]Administratorrsquos Guide Technical Operations for SAP NetWeaver Administration of SAP NetWeaver Systems AS

Java (Application Server Java) Administration Administration Tools SAP Management Console

SAP Logon

Instead of using a fixed list of systems and message servers you can configure SAP Logon in thesapmsgini configuration file to find SAP systems and their message servers from the directory Ifyou configure SAP logon to use the LDAP directory it queries the directory each time Server or Groupselection is chosen to fetch up-to-date information on available SAP systemsTo use LDAP operation mode make sure that the sapmsgini file contains the following[Address]

Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

28148 PUBLIC 12142007


Distinguish the following cases

n If you use an Active Directory you must set LDAPoptions=ldquoDirType=NT5ADSrdquo For moreinformation see the SAP system profile parameter ldapoptions

n You must specify the directory servers (for example LDAPserver=pcintel6 p24709) if either ofthe following is truel The client is not located in the same domain forest as the Active Directoryl 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 ldapservers

n For other directory services you can use LDAPnode to specify the distinguished name of the SAProot node For more information see the SAP system profile parameter ldapsaproot

SAP MMC

The SAPMMC is a graphical user interface (GUI) for administering andmonitoring SAP systems froma central location It is automatically set up when you install an SAP system on Windows If the SAPsystem has been prepared correctly the SAP MMC presents and analyzes system information thatit gathers from various sources including the Active DirectoryIntegrating the Active Directory as a source of information has advantages for the SAP MMC It canread system information straight from the directory that automatically registers changes to thesystem landscape As a result up-to-date information about all SAP application servers their statusand parameter settings is always available in the SAP MMCIf you need to administer distributed systems we especially recommend that you use the SAP MMCtogether with Active Directory services You can keep track of significant events in all of the systemsfrom a single SAP MMC interface You do not need to manually register changes in the systemconfiguration Instead such changes are automatically updated in the directory and subsequentlyreflected in the SAP MMCIf your SAP system is part of a heterogeneous SAP system landscape that comprises systems orinstances both on Unix and Windows platforms you can also use the SAP MMC for operating andmonitoring the instances running on Unix

SAP MC

The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems froma central location The SAP MC is automatically set up when you install an SAP system on anyplatform If the SAP system has been prepared correctly the SAP MC presents and analyzes systeminformation that it gathers from various sources including a generic LDAP DirectoryIntegrating a generic LDAP Directory as a source of information has advantages for the SAP MC Itcan read system information straight from the directory that automatically registers changes to thesystem landscape As a result up-to-date information about all SAP application servers their statusand parameter settings is always available in the SAP MC

12142007 PUBLIC 29148

2 Planning26 Planning the Switchover Cluster

Configuration Tasks for LDAP Directories

This section describes the configuration tasks you have to perform 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 must configure theActive Directory so that it can store SAP system dataTo prepare the directory you use SAPinst to automatically

n Extend the Active Directory schema to include the SAP-specific data typesn 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 sapldapn Create the root container where information related to SAP is stored

n Control access to the container for SAP data by giving members of the SAP_LDAP group permissionto read and write to the directory

You do this by running SAPinst on the Windows server on which you want to use Active DirectoryServices and choosing ltSAP Systemgt Software Life-Cycle Options LDAP Registration Active DirectoryConfiguration For more information about running SAPinst on Windows see documentationInstallation Guide mdash ltyour productgt on Windows ltDatabasegt

Note

You have to perform the directory server configuration only once Then all SAP systems that needto 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 your directory server is correctly configured you can enable the LDAP registration of the SAPsystem by setting some profile parameters in the default profileTo do this run SAPinst [page 95] once for your system and chooseltSAP Systemgt Software Life-Cycle Options LDAP Registration LDAP Support

If you use a directory server other than Microsoft Active Directory andor non-Windows applicationservers you have to store the directory user and password information by using ldappasswdpf=ltany_instance_profilegt The information is encrypted for storage in DIR_GLOBAL and istherefore valid for all application servers After restarting all application servers and start servicesthe system is registered in your directory server The registration protocols of the components aredev_ldap The registration is updated every time a component starts

30148 PUBLIC 12142007



26 Planning the Switchover Cluster

You can reduce unplanned downtime for your SAP system by setting up a switchover cluster Thissetup installs critical software units ‒ known as ldquosingle points of failurerdquo (SPOFs) ‒ across multiplehost machines in the cluster In the event of a failure on the primary node proprietary switchoversoftware automatically switches the failed software unit to another hardware node in the clusterManual intervention is not required Applications accessing the failed software unit normallyexperience a short delay but can then resume processing as normalSwitchover clusters also have the advantage that you can deliberately initiate switchover to freeup a particular node for planned system maintenance Switchover solutions can protect againsthardware failure and operating system failure but not against human error such as operator errors orfaulty application software Additional downtime might be caused by upgrading your SAP system orapplying patches to itWithout a switchover cluster the SAP system SPOFs ‒ central services instance the database instanceand the central file share ‒ are vulnerable to failure because they cannot be replicated All of thesecan only exist once in a normal SAP systemYou can protect software units that are not SPOFs against failure by making them redundant whichmeans simply installing multiple instances For example you can add additional application serverinstances This complements the switchover solution and is an essential part of building HA intoyour SAP system

Recommendation

SAP recommends switchover clusters to improve the availability of your SAP system

A switchover cluster consists of

n A hardware cluster of two or more physically separate host machines to run multiple copies of thecritical software units in an SAP system the SPOFs referred to above

n Switchover software to detect failure in a node and switch the affected software unit to the standbynode where it can continue operating

n Amechanism to enable application software to seamlessly continue working with the switchedsoftware unit ‒ normally this is achieved by virtual addressing (although identity switchoveris also possible)

PrerequisitesYou must first discuss switchover clusters with your hardware partner because this is a complextechnical area In particular you need to choose a proprietary switchover product that works withyour operating system

12142007 PUBLIC 31148


We recommend that you read the following documentation before you start

n Check the informations and the installation guides that are available in the High Availability area athttpsdnsapcomirjsdnlandscapedesign Technical Infrastructure

n The enqueue replication server (ERS) is a major contribution to an HA setup and is essential for aJava system We strongly recommend you to also use it for an ABAP system You need one ERS foreach Java SCS and one ERS for each ABAP SCS (ASCS) installed in your system

FeaturesThe following graphic shows the essential features of a switchover setup

Figure 10 Switchover Setup

Note

This graphic and the graphics in this section are only examples You need to discuss your individualHA setup with your HA partnerThese graphics summarize the overall setup and do not show the exact constellation for aninstallation based on one of the available technologies (ABAP ABAP+Java or Java)

The following graphic shows an example of a switchover cluster in more detail

32148 PUBLIC 12142007


Figure 11 Switchover Cluster

ConstraintsThis documentation concentrates on the switchover solution for the central services instance Formore information on how to protect the Network File System (NFS) software and the databaseinstance by using switchover software or (for of the database) replicated database servers contactyour HA partnerYou need to make sure that your hardware is powerful enough and your configuration is robustenough to handle the increased workload after a switchover Some reduction in performance mightbe acceptable after an emergency However it is not acceptable if the system comes to a standstillbecause it is overloaded after switchoverEnd of HA (UNIX)

12142007 PUBLIC 33148

This page is intentionally left blank

3 Preparation

3 Preparation

This section includes the preparation steps that you have to perform for the

n Standard distributed or high-availability systemn Standard distributed or high-availability systemn Additional application server instancen Standalone host agent

Preparation Steps for a Standard Distributed or High-Availability System

Note

In a standard system all mandatory instances are installed on one host Therefore if you areinstalling a standard system you can ignore references to other hosts

1 You identify basic SAP system parameters [page 37]2 You check the hardware and software requirements [page 43] for every installation host of the HA system

landscape that you want to install3 You make sure that the required operating system users and groups [page 60] are created4 If you want to configure the User Management Engine (UME) of Application Server Java (AS Java)

for the user management of a separate ABAP system you have toprepare user management for an external ABAP System [page 63]

5 You set up file systems and raw devices [page 66] and make sure that the required disk space is available forthe directories to be created during the installation

6 If you want to share the transport directory trans from another system export [page 81] thisdirectory to your installation hosts

7


If you want to install a high-availability system you perform switchover preparations [page 60]End of HA (UNIX)

8


If you want to install a high-availability system you set up the virtual host name and specify thiswhen you set the environment variable SAPINST_USE_HOSTNAME [page 94] Alternatively you canspecify the virtual host name in the command to start SAPinstEnd of HA (UNIX)

9 You generate the SAP Solution Manager Key [page 86]

12142007 PUBLIC 35148

3 Preparation

10 You make sure that the required installation media [page 87] are available on every host on which youwant to install an instance of your SAP system

11 If you decided to use a generic LDAP directory you have to create a user for LDAP directory access[page 90]

12 You can continue with Installation [page 91]

Preparation Steps for an Additional Application Server Instance

You have to perform the following preparations on the host where you install the additionalapplication server instance(s)

1 You identify basic SAP system parameters [page 37]2 You check the hardware and software requirements [page 43] for every installation host on which you want

to install one or more additional application server instances3 You make sure that the required operating system users and groups [page 60] are created4 You set up file systems and raw devices [page 66] and make sure that the required disk space is available for

the directories to be created during the installation5 If you want to share the transport directory trans from another system export [page 81] this

directory to your installation hosts6 You make sure that the required installation media [page 87] are available on every host on which you

want to install one or more additional application server instances7 You can continue with Installation [page 91]

Preparation Steps for a Standalone Host Agent

You have to perform the following preparations on the host where you install a standalone host agent

1 You identify basic SAP system parameters [page 37]You can find the parameters in the table Host Agent

2 You check the hardware and software requirements [page 43] on the installation hostYou can find the requirements for the Host Agent in section Requirements for a Standalone Host Agent

3 You make sure that the required operating system users and groups [page 60] are createdYou can find the operating system user for the Host Agent in the table Operating System User for theHost Agent

4 You set up file systems and raw devices [page 66] and make sure that the required disk space is available forthe directories to be created during the installationYou can find the directories for the Host Agent in section Host Agent Directories

5 You make sure that the required installation media [page 87] are available on the installation hostYou can find the installation media that are required for the installation of a standalone host agentin the row Host Agent (Standalone) of the media table


36148 PUBLIC 12142007

3 Preparation31 Basic SAP System Parameters

31 Basic SAP System Parameters

SAPinst asks whether you want to run the installation in Typical or CustommodeIf you choose Typical SAPinst provides automatic default settings and you only have to respond toa minimum number of prompts However you can still change any of the default settings on theparameter summary screenThe tables below list the basic system parameters that you always need to specify before installing yourSAP system both in typical and in custom modeFor all other SAP system parameters use the F1 help in the SAPinst dialogs

SAP System ID and Database ID

Parameters Description

SAP System ID ltSAPSIDgt The SAP system ID ltSAPSIDgt identifies the entire SAP systemSAPinst prompts your for the ltSAPSIDgt when you execute the first installationoption to install a new SAP systemIf there are further installation options to be executed SAPinst prompts youfor the profile directory For more information see the description of theparameter SAP System Profile Directory

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

CautionChoose your SAP system ID carefully Renaming is difficult and requires youto reinstall the SAP system

Make sure that your SAP system IDn Is unique throughout your organizationn Consists of exactly three alphanumeric charactersn Contains only uppercase lettersn Has a letter for the first charactern Does not include any of the following which are reserved IDs

ADD ALL AND ANY ASC COM CON DBA END EPS FOR GID IBM INT KEY LOG MON

NIX NOT NUL OFF OMS RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID

USR VAR

Database ID ltDBSIDgt The ltDBSIDgt identifies the database instance SAPinst prompts you for theltDBSIDgt when you are installing the database instanceThe ltDBSIDgt can be the same as the ltSAPSIDgt

CautionChoose your database ID carefully Renaming is difficult and requires youto reinstall the SAP system

n If you want to install a new database

12142007 PUBLIC 37148



Make sure that your database IDl Is unique throughout your organizationl Consists of exactly three alphanumeric charactersl Contains only uppercase lettersl Has a letter for the first characterl Does not include any of the following which are reserved IDs

ADD ALL AND ANY ASC COM CON DBA END EPS FOR GID IBM INT KEY LOG

MON NIX NOT NUL OFF OMS RAW ROW SAP SET SGA SHG SID SQL SYS TMP

UID USR VAR

n If you want to use an existing database systemEnter exactly the database ID of the existing database to which you want toadd the system

SAP System Profile Directory


ltsapmntgtltSAPSIDgtprofile orusrsapltSAPSIDgtSYSprofile

The installation retrieves the parameters entered earlier from the SAPsystem profile directorySAPinst prompts you to enter the location of the profile directorywhen the installation option that you execute is not the first onebelonging to your SAP system installation See also the description ofthe parameters SAP System ID and Database IDusrsapltSAPSIDgtSYSprofile is the soft link referring toltsapmntgtltSAPSIDgtprofile

NoteIf you install an additional application server instance in an existingSAP system SAPinst also prompts you for the profile directory ofthe existing SAP system

SAP System Instances Hosts and Ports


Instance Number Instance NumberTechnical identifier that is required for every instance of an SAP systemconsisting of a two-digit number from 00 to 97The instance number must be unique on a host That is if more than one SAPinstance is running on the same host these instances must be assigned differentnumbersTo find out this number look in the SAP directory usrsapltSAPSIDgtJltnngt onthe host of the primary application server instanceThe value ltnngt is the number assigned to the primary application server instance

CautionDo not use 75 for the instance number because this number is already used by

38148 PUBLIC 12142007



the operating system For more information see SAP Note 29972

Virtual Host Name For a high-availability (HA) system where you want to install the SCS instanceinto a cluster you need to specify the virtual host name [page 94] before you startSAPinstn For more information about the use of virtual TCPIP host names see SAP

Note 962955n For more information about the allowed host name length and characters

see SAP Note 611361To find out the host name open a command prompt and enter hostname

Message Server PortCaution

The message server port number must be unique for the SAP system on allhosts If there are severalmessage ports number on one host all must be unique

Port Number of the SAP Message ServerIf you do not specify a value the default port number is usedThe Java message server is configured in the SCS instance profileThe Java message server port uses the parameter rdispmsserv_internal withdefault value 39ltnngt where ltnngt is the instance number of the SCS messageserver instanceFor more information about the parameters used for message server ports seeSAP Note 821875

Master Password


Master Password This password is used for all new user accounts SAPinst creates and for thesecure store key phrase The length has to be 8 to 14 charactersDepending on your installation scenario there might be more restrictions

CautionIf you do not create the operating system users manually SAPinst createsthem with the common master password For more information see thedescription of the parameter Operating System Users In this case make sure thatthe master password meets the requirements of your operating system andof your database

12142007 PUBLIC 39148


Operating System Users of the SAP System


User ltsapsidgtadm User ltsapsidgtadm is the system administrator userIf you did not create user ltsapsidgtadmmanually before the installation SAPinstcreates it automatically during the installation SAPinst sets the Master Passwordby default but you can overwrite it either by choosing parameter mode Custom orby changing it on the parameter summary screenMake sure that the user ID and group ID of this operating system user are uniqueand the same on each application server instance hostFor more information see Creating Operating System Users [page 60]

User sapadm User sapadm is used for central monitoring servicesIf you did not create user sapadmmanually before the installation SAPinstcreates it automatically during the installation SAPinst sets the Master Passwordby default but you can overwrite it either by choosing parameter mode Custom orby changing it on the parameter summary screenMake sure that the user ID and group ID of sapadm are unique and the same oneach application server instance hostFor more information see Creating Operating System Users [page 60]

User Management Engine (UME)

Parameter Description

UME Configuration SAPinst prompts you for how to configure the UME during the input phase ofthe installationYou can choose between the following optionsn Use Java database (default)

If you choose this option administrators can manage users and groups withthe UME Web admin tool and SAP NetWeaver Administrator onlyFor LDAP use this configuration for the installation and change theconfiguration to LDAP after the installation

n Use an external ABAP systemIf you choose this option administrators can manage users with thetransaction SU01 on the external ABAP system and depending on thepermissions of the communication user also with the UME Web admin tool

and SAP NetWeaver AdministratorYou must have created the required users manually on the external ABAPsystemFor more information see Preparing User Management for an External ABAPSystem [page 63]

For more information on supported UME data sources and change optionssee SAP Note 718383

Using the Java Database

Java Administrator User SAPinst sets the user name Administrator and the master password by defaultIf required you can choose another user name and password according toyour requirements

40148 PUBLIC 12142007



Java Guest User SAPinst sets the user name Guest and the master password by defaultThe Guest user is for employees who do not belong to a company or who haveregistered as company users with pending approval Guest users belong to thedefault group Authenticated Users and have read access only

Using an External ABAP System ‒ Parameters for the ABAP Connection

Application Server InstanceNumber

This is the instance number on the application server of the central ABAPsystem to which you want to connect the Application Server JavaTo find out the number on the host of the primary application server instancelook under the SAP directory usrsapltSAPSIDgtDVEBMGSltnngt The value ltnngtis the number assigned to the SAP system

Application Server Host This is the host name of the relevant application server instanceTo find out the host name enter hostname at the command prompt of the hostrunning the primary application server instance

Communication User This is the name and password of the existing ABAP communication user Youmust have created this user manually on the external ABAP system

Using an External ABAP System ‒ Parameters for the Application Server Java Connection

Administrator User This is the name and password of the administrator user that you created onthe external ABAP system

Administrator Role The role SAP_J2EE_ADMINmust exist on the external ABAP system

Guest User This is the name and password of the guest user that you created on theexternal ABAP systemThe guest user is for employees who do not belong to a company or who haveregistered as company users with pending approval Guest users belong to thedefault group Authenticated Users and have read access only

Guest Role The role SAP_J2EE_GUESTmust exist on the external ABAP system

Key Phrase for Secure Store Settings


Key Phrase for SecureStore Settings

This is a random word or phrase that is used to encrypt the secure storeThe Java EE engine uses this phrase to generate the key that will be used to encryptthe dataThe uniqueness of the phrase you use contributes to the uniqueness of theresulting key

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

12142007 PUBLIC 41148


Internet Communication Manager (ICM) User Management


Password of webadm The administration user webadm is created to use the web administrationinterface for Internet Communication Manager (ICM) and Web DispatcherSAPinst sets themaster password by default If required you can choose anotherpassword The length of the password must be between 5 and 128 characters

Host Agent


Password of sapadm The administration user sapadm is created to use central monitoring servicesIf this user does not already exist SAPinst automatically creates itSAPinst prompts you to enter either the password of the existing user or a newpassword for the user to be created

Solution Manager Key


SAP Solution Manager key To install your SAP system you need to generate a SAP Solution Manager key [page86] which the installation requires to continue For more information seeSAP Note 805390

Parameters Relevant for the Directory Structure of the System


SAP systemmount directory The SAP system mount directory ltsapmntgt is the base directory for theSAP systemFor ltsapmntgt you can use a directory of your choice If you do not specifya directory SAPinst creates a directory named sapmnt by defaultDo not add ltSAPSIDgt as subdirectory because the installer adds thisdirectory automatically

ExampleIf you enter sapmount for ltsapmntgt and KB1 for ltSAPSIDgt duringthe input phase of the installation the installer creates the directorysapmountKB1

For more information see Setting Up File Systems and Raw Devices [page 66]

MaxDB file systems n MaxDB root directory sapdbn For file system installations locations of SAP data and log volumesn For raw device installations locations of raw devices for data and log

volumes

42148 PUBLIC 12142007

3 Preparation32 Hardware and Software Requirements

Parameters Relevant for the Database

Parameters Description Enter Your Values

Database ID Identifier for the database [page 37]

Database schema SAPltSAPSIDgtDB

Database operating system usersand groups

MaxDB software owner (defaultvalues)n User sdbn Group sdbaMaxDB database ownersqdltdbsidgt

32 Hardware and Software Requirements

You check the hardware and software requirements for your operating system (OS) and the SAPinstances using the Prerequisite Checker tool that provides information about the requirementsthat you need to meet before you start the installation For example it checks the requirementsfor the different installation options

Note

n The values that are checked by the Prerequisite Checker apply to the installation of developmentsystems or quality assurance systems

n For the most recent updates to the Prerequisite Checker always check SAP Note 855498

You can run the Prerequisite Checker as follows

n Standalone (optional)To check the hardware and software requirements of the host on which you want to later installan SAP system you can run the Prerequisite Checker in standalone mode [page 45]

n Integrated in SAPinst (mandatory)SAPinst automatically runs the Prerequisite Checker when you install your SAP system

Recommendation

We also recommend that you consult the requirements checklists tables which also provide valuesfor the installation of development systems or quality assurance systems Depending on theamount of data involved the requirements might change

In addition consider the following

n To get precise sizing values for production systems you choose one of the following options

12142007 PUBLIC 43148


l You use the SAP Quick Sizer tool available on SAP Service Marketplace athttpservicesapcomsizing You enter information about your planned system and thetool calculates the requirementsFor more information see Planning your System Landscape in theMaster Guide for your SAP systemwhich is available on SAP Service Marketplace [page 11]

l You contact your hardware vendor who can analyze the load and calculate suitable hardwaresizing depending on

uThe set of applications to be deployed

uHow intensively the applications are to be used

uThe number of users

n For supported operating system releases see the Product Availability Matrix on SAP ServiceMarketplace at httpservicesapcompam

n Contact your OS vendor for the latest OS patchesn Make sure that the host name meets the requirements listed in SAP Note 611361n Check your keyboard definitionsn If you want to install a printer on a host other than the host of the primary application server

instance (for example on a separate database instance host) make sure that the printer can beaccessed under UNIX

Process Flow

1 If required you run the Prerequisite Checker standalone [page 45] to check the hardware and softwarerequirements

Caution

If you do not fully meet the requirements you might experience problems when working withthe SAP system

2 In addition we recommend that you check the hardware and software requirements for youroperating system and for the system variant that you want to installn HP-UX [page 46]n Standard system [page 48]

Note

These requirements also apply if you want to install the Application Sharing Server as anOptional Standalone Unit

n Distributed system [page 48]n High availability system [page 51]n If you want to install additional application server instances check the requirements for an

additional application server instance [page 54]

44148 PUBLIC 12142007


n If you want to install the Application Sharing Server as an optional standalone unit see therequirements for a standard system [page 48]

n If you want to install the host agent on a host that does not have an SAP component check therequirements for the host agent as a separate installation [page 55]

321 Running the Prerequisite Checker in Standalone Mode(Optional)

Before installing your SAP system you can run the Prerequisite Checker in standalone mode to check thehardware and software requirements for your operating system (OS) and the SAP instances

Recommendation

We recommend that you use both the Prerequisite Checker and the requirements tables for reference

Note

When installing your SAP system SAPinst automatically starts the Prerequisite Checker and checks thehardware and software requirements in the background

Prerequisites

n You have prepared the Installation Master DVD on the required installation host [page 87]n You make sure that the required prerequisites are met before starting SAPinst [page 95]

Procedure

1 You start SAPinst [page 95]2 On theWelcome screen choose ltSAP Systemgt Software Life-Cycle Options Additional Preparation

Tasks Prerequisites Check 3 Follow the instructions in the SAPinst dialogs and enter the required parameters

Note

For more information about each parameter position the cursor on the parameter field andchoose F1 in SAPinst

When you have finished the Parameter Summary screen appears summarizing all parameters you haveentered If you want to make a change select the relevant parameters and choose Revise

4 To start the Prerequisite Checker choose Start

ResultThe Prerequisite Check Results screen displays the results found If required you can also check the resultsin file prerequisite_checker_resultshtml which you can find in the installation directory

12142007 PUBLIC 45148


322 Requirements for HP-UX

n The information here is not intended to replace the documentation of the HP-UX operatingsystem (OS) For more information on HP-UX see httpdocshpcom

n HP has released HP-UX 11i for the Itanium processor family HP-UX 11i for Itanium is built fromthe same code base as HP-UX 11i for PA-RISC and has the same look-and-feelIn general all OS requirements for HP-UX are valid for both the PA-RISC version and the ItaniumversionsThere are some exceptions due to new functionality of the latest HP-UX releases They are listed inthe appropriate sections of this documentation

n For more information on HP-UX 11iv3 and HP-UX 1131 see SAP Note 1031960n As of HP-UX 1131 HP offers a new web-based tool for systemmanagement SystemManagement

Homepage (SMH) You can start it in text mode or in web-based modeFor more information about how to start it in web-based mode see httpdocshpcom

The host machine must meet the following requirements

Hardware Requirements

Requirement Values and Activities

CD DVD drive ISO 9660 compatible You must connect the CD or DVD drive locally to your centralinstance host Many CD or DVD drives can be configured but not all can be mountedFor more information seeMounting a CD DVD for HP‒UX [page 125]

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

RAM n To display the RAM size on HP-UX PA-RISC enter the following commandecho selclass qualifier memoryinfowaitinfolog | cstm |grep Memory

|grep Total

n To display the RAM size on HP-UX Itanium or all 1131 systems enter the followingcommandusrcontribbinmachinfo |grep Memory

CPU The recommended minimum hardware is either two physical single core processors orone physical dual core processorTo display the number of CPUs in a system call enter the following commandioscan -fnkCprocessor

Software Requirements


Operating system(OS)

Check the operating system version with the following commanduname -r

46148 PUBLIC 12142007



Network File System(NFS)

The NFS driver must be in the kernelYou can check this using the current kernel configuration files Enter the followingcommandgrep nfs standsystem

To check whether NFS is running enter the following commandsps -ef | grep nfsd

ps -ef | grep rpcbind

grep NFS_C etcrcconfigdnfsconf

grep NFS_S etcrcconfigdnfsconf

Either NFS_CLIENT NFS_SERVER or both should be set to 1 You can use SAM or SMH tostart NFS orand add the driver to the kernel

National LanguageSupport (NLS)

Enter the following command to check whether National Language Support (NLS) isinstalledswlist -v | grep -i nls

The output should contain the string NLS-AUX

Enter the following command to heck which locales are availablelocale -a

The following files must be available de_DEiso88591 en_USiso88591

Minimum requiredOS patches

See SAP Note 837670

LDAP support To use Lightweight Directory Access Protocol (LDAP) directory services the followingLDAP libraries are requiredn HP-UX on PA-Risc (111111231131)

libldapssl40sl or libldap41sln HP-UX on Itanium (11231131)

libldapssl41so

Fonts The directory libX11fonts contains the available fontsYou can select fonts in your default profiles for X11 and CDE

Exampleiso_88591 or hp_roman8

Other Requirements


Printer To check whether a file can be printed enter the following commandlp -dltprinter_namegt lttest_filegt

To check the status of your spool and the printers enter the following commandlpstat -t

Keyboard You can set the keyboard on an ASCII console as follows A configuration menu bar isactivated via the UserSystem keyconfig keys terminal config

Select Default Values or make your selection in the fields Keyboard and Language

12142007 PUBLIC 47148


323 Requirements for a Standard System

If you want to install a standard system ‒ that is all instances reside on one host ‒ the host must meetthe following requirements



Hard disk space n Hard disk drives with sufficient space for the SAP system and the databaseFor more information see SAP Directories [page 67]

n For more information about the disk space requirements for MaxDB seeRequirements for the Database Instance [page 49]

n 43 GB of temporary disk space for every required installation DVD thatyou have to copy to a local hard disk For more information see Preparing theInstallation DVDs [page 87]

n 12 GB of temporary disk space for the installation

Minimum RAM 2 GB

Swap Space Hard disk drives with sufficient space for swap 3 RAM at least 20 GB




If application servers are installed decentralized Network File System (NFS) mustbe installed

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


Make sure that National Language Support (NLS) and corresponding saplocalesare installed

324 Requirements for a Distributed System

The following sections provide information about the hardware and software requirements for adistributed system where the following SAP instances can reside on different hosts

n Central services instance [page 49]n Database instance [page 49]n Primary application server instance [page 50]

Note

If you install multiple SAP system instances on one host you need to add up the requirements

48148 PUBLIC 12142007


3241 Requirements for a Central Services Instance

The central services instance host must meet the following requirements for the central servicesinstance



Hard disk space n Hard disk drives with sufficient space for the central services instanceFor more information see SAP Directories [page 67]

n 43 GB of temporary disk space for every required installation DVD that youhave to copy to a local hard diskFor more information see Preparing the Installation DVDs [page 87]


Minimum RAM 1 GB





Network File System (NFS) must be installed

3242 Requirements for the Database Instance

The database host must meet the following requirements



Disk space n Space requirements of the SAP data file systems see the following fileltExport_DVDgtDATA_UNITSEXPORT_1DBADADBSIZEXML

The XML table in this file contains a field called fDevSize whichcontains the size in MB of the element indicated in the previous fieldfDevName This shows you the size of the data (DBDATADEV) and thelog (DBLOGDEV) volumes

NoteThe values listed in DBSIZEXML are only for guidance

For more information about the required disk space per file systemsee Setting Up File Systems [page 66]

12142007 PUBLIC 49148



For security reasons (system failure) the file systems must bedistributed physically over at least three (but five are recommended)disks

n Database softwarel Version 76 500 MBl Version 77 700 MB

n 45 GB of temporary disk space for every required installation DVDyou have to copy to a local hard disk


RAM 1 GB

Swap space n Recommended 3RAM + 45 GBn Minimum 2RAM + 4 GBn Maximum 15 GB



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

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

National Language Support(NLS)

Make sure that National Language Support (NLS) and correspondingsaplocales are installed

Operating systems n For supported operating system releases see SAP Service Marketplaceat httpservicesapcomplatforms Product Availability Matrix

n Contact your operating system vendor for the latest OS patches

3243 Requirements for the Primary Application ServerInstance

The host where the primary application server instance runs must meet the following requirements



Hard disk space n Hard disk drives with sufficient space for the primary application serverinstanceFor more information see SAP Directories [page 67]

n 43 GB of temporary disk space for every required installation DVD thatyou have to copy to a local hard disk For more information see Preparingthe Installation DVDs [page 87]


50148 PUBLIC 12142007



Minimum RAM 1 GB






Required fonts and codepages

Make sure that the required fonts and code pages are installed



325 Requirements for a High Availability System

The following sections provide information about the hardware and software requirements fora high-availability system where the following SAP instances can reside on different hosts or on aswitchover cluster infrastucture

n Enqueue replication server instances [page 52]n Database instance [page 53]n Primary application server instance [page 54]


The central services instance host must meet the following requirements for the central servicesinstance (SCS)






Minimum RAM 1 GB


12142007 PUBLIC 51148







3252 Requirements for an Enqueue Replication ServerInstance

The host on which an enqueue replication server instance runs must meet the followingrequirements

Note

The enqueue replication server instance is only required for high-availability systemsYou need one ERS for each Java SCS and one ERS for each ABAP SCS (ASCS) installed in your system






Minimum RAM 1 GB






End of HA (UNIX)

52148 PUBLIC 12142007









For more information about the required disk space per file systemsee Setting Up File Systems [page 66]For security reasons (system failure) the file systems must bedistributed physically over at least three (but five are recommended)disks




RAM 1 GB










12142007 PUBLIC 53148









Minimum RAM 1 GB










326 Requirements for an Additional Application ServerInstance

The additional application server host must meet the following requirements

54148 PUBLIC 12142007




Hard disk space n Hard disk drives with sufficient space for the additional application serverinstanceFor more information see SAP Directories [page 67]



Minimum RAM 1 GB




SAP kernel Make sure that the SAP kernel of the primary application server instance has atleast the patch level of the SAP kernel on the SAP Kernel DVD that is used for theinstallation of the additional application server instanceWe recommend that you apply the most current SAP kernel from the SAP ServiceMarketplace at httpservicesapcomswdc



327 Requirements for a Standalone Host Agent

If you want to install a standalone host agent the installation host has to meet the followingrequirements



Hard Disk Space n Minimum disk spaceFor information about the required disk space per file system see Setting Up FileSystems [page 66]

n 43 GB of temporary disk space for every required installation DVD that you haveto copy to a local hard disk For more information see Preparing the Installation DVDs[page 87]


Minimum RAM 05 GB

Swap space Hard disk drives with sufficient space for swap 3 RAM

12142007 PUBLIC 55148






328 Checking and Modifying the HP-UX Kernel

To run an SAP system it is important to check and if necessary modify the HP-UX kernel

Caution

We recommend that a UNIX system administrator performs all kernel modifications

1 Check SAP Note 172747 for recommendations on current HP-UX kernel parameters

Caution

If a kernel value is already larger than the one suggested in the SAP Note do not automaticallyreduce it to match the SAP requirementYou have to analyze the exact meaning of such a parameter and if required to reduce theparameter 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 waysn Manually

For more information see SAP Note 172747n Using System Administrator Manager (SAM) forHP-UX 1111 andHP-UX 1123

For more information see section Configuring the Kernel Using SAM for HP-UX 1111 and 1123 belown Using kcweb for HP-UX 1123 and HP‒UX 1131

For more information see section Configuring the Kernel Using kcweb for HP-UX 1123 and HP‒UX113 below

n Using System Management Homepage (SMH) for HP-UX 1123For more information see section Configuring the Kernel Using kcweb for HP-UX 11221123 below

Configuring the Kernel Using SAM for HP-UX 1111 and HP‒UX 1123

1 Enter the following commandusrsbinsam

2 Choose Kernel Configuration Configurable Parameters 3 Select the parameter to be modified and choose Actions Modify Configurable Parameter4 Modify all kernel parameters according to the table above5 From the Actionsmenu choose Process New Kernel

56148 PUBLIC 12142007


6 Exit SAM7 Reboot the system

Configuring the Kernel Using kcweb for HP-UX 1123 and HP-UX 1131Kernel configuration using kcweb is a combination of a command set and a Web-based graphicaluser interface (GUI) that lets you configure an HP-UX kernel and monitor consumption of kernelresources controlled by parametersThe kcweb application replaces the kernel configuration portion of SAM and adds the followingcommands for kernel configuration and monitoring to the system

n kcweb(1M)

n kcusage(1M)

n kcalarm(1M)

There is also the daemon kcmond(1M) which replaces the obsolete krmond(1M)The kcweb application provides the following new features

n New Web-based PC-supported GUI that is faster and easier to use remotely than the currentSAM interface

n Kernel parameter documentation that you can view within the GUIn Support for dynamic (no reboot) kernel tuningn Parameter monitoring that lets you continually monitor the usage of kernel resources (with

kcmond) and pro-actively tune the kernel instead of waiting for an application to failParameter monitoring offers youl Tables and graphs of kernel resources controlled by kernel parametersl User-created threshold alarms that issue alerts when consumption of a kernel resource exceeds

a specified percentage of the parameter valuen Improved command line interface (CLI) that offers all functionality available in the GUIn Improved separation between GUI and kernel so that the application does not need to be patched

as often

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 1131

1 Enter one of the following commands

n usrsbinsmh

n httplthostnamegtltportgt

where ltportgt is either the default port 2381 or your defined port (for example 2301)2 Choose Kernel Configuration Tunables3 Select the parameter to be modified and enter m (m-Modify)4 Modify all kernel parameters according to the table above

12142007 PUBLIC 57148


5 ChooseModify6 Exit SMH7 Reboot the system

329 Setting up Swap Space for HP-UX

Here you can find information about how to set up swap space for HP-UX

1 Find out whether you have to increase the swap space

Recommendation

We recommend to set SWAP space to 2 RAM (minimum 20 GB)For more information see SAP Note 1075118

You can determine the size of the installed RAM in one of the following waysn Using the System Administration Manager (SAM)

Choose Performance Monitors System Properties Memory

n Manuallyl To display the RAM size on HP-UX PA-RISC enter the following command

echo selclass qualifier memoryinfowaitinfolog | cstm |grep Memory |grep

Total

l To display the RAM size on HP-UX Itanium or all HP‒UX 1131 systemsusrcontribbinmachinfo |grep Memory

2 To check whether enough swap space is currently configured on your system enter the followingcommand and add up the total device swap spaceusrsbinswapinfo ndashdm

Example

usrsbinswapinfo -dm

Mb Mb Mb PCT Mb

TYPE AVAIL USED FREE USED START RESERVE PRI NAME

dev 10000 82 9918 1 0 - 1 devvg00lvol2

dev 20000 83 19917 0 0 - 1 devvg01lvol9

In this case the total device swap space is 30000 MB

3 If necessary increase the swap space in one of the following waysn Manually as described below in Setting Up Swap Space Manually

n Using SAM as described below in Setting up Swap Space Using SAM for HP-UX 11111123

n Using SMH as described below in Setting up Swap Space Using SMH for HP-UX 1131

58148 PUBLIC 12142007


4 If you are not installing a standalone database server check the paging size and the kernel settingsas described below in Checking Paging Space Size and Kernel Settings

Setting up Swap Space Manually

1 To create a logical volume enter the following commandlvcreate ndashC y mdashn ltLVNamegt devltVGNamegt

2 To define the size and allocate the logical volume to a disk enter the following commandslvextend mdashL ltsize in MBgt devltVGNamegtltLVNamegt

devdskltdiskdevicegt

3 To enable automatic swap activation at boot time add the following entry to etcfstabdevltVGNamegtltLVNamegt swap swap defaults 0 0

4 To manually activate the swap devices space defined in etcfstab enter the following commandusrsbinswapon -a

5 To check if the swap space has been activated enter the following commandusrsbinswapinfo ndashtm

Setting up Swap Space Using SAM for HP-UX 11111123

1 To start SAM enter the following commandusrsbinsam

2 ChooseDisks and Filesystems Swap Actions Add Device Swap Using the LVM

3 Select a partition for swap and choose OK4 Exit SAM

Note

You cannot set the swap space on HP-UX 1131 with SMH On HP-UX 1131 you have to configure theswap space manually

Checking Paging Space Size and Kernel Settings

Note

If 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 theSAP system

2 Execute memlimits to verify paging space size and kernel settings as followsa) To unpack file memlimits enter the following commands

cd ltINSTDIRgt

ltDVD-DIRgtK0ltxgtUNIXltOSgtSAPCAR

mdashxvfg ltDVD-DIRgtK0ltxgtUNIXltOSgtSAPEXESAR memlimits

12142007 PUBLIC 59148

3 Preparation33 Performing Switchover Preparations for High Availability

b) To start memlimits enter the following commandmemlimits mdashl 20000

3 If you see error messages increase the paging space and rerun memlimits until there are no moreerrors


33 Performing Switchover Preparations for High Availability

Do the following to prepare the switchover cluster

Procedure

1 Set up Domain Name System (DNS) on the virtual host2 Assign the virtual IP addresses and host names for the SCS and ASCS instances and (if required)

NFS to appropriate failover groups

Note

For more information on virtual addresses and virtual host names and how to assign resources tofailover groups ask your HA partner

More InformationFor more information about the use of virtual TCPIP host names see SAP Note 962955End of HA (UNIX)

34 Creating Operating System Users and Groups

During the installation SAPinst checks all required accounts (users groups) and services on thelocal machine SAPinst checks whether the required users and groups already exist If not it createsnew users and groups as necessaryIf you do not want SAPinst to create operating systems users groups and services automatically youcan optionally create them before the installation This might be the case if you use central usermanagement such as Network Information System (NIS)SAPinst checks if the required services are available on the host and creates them if necessary See thelog messages about the service entries and adapt the network-wide (NIS) entries accordinglySAPinst checks the NIS users groups and services using NIS commands However SAPinst does notchange NIS configurations

60148 PUBLIC 12142007

3 Preparation34 Creating Operating System Users and Groups

Recommendation

For a distributed or a high-availability system we recommend that you distribute accountinformation (operating system users and groups) over the network for example by using NetworkInformation Service (NIS)

Caution

All usersmust have identical environment settings If you change the environment delivered bySAP such as variables paths and so on we do not assume responsibility

If you want to use global accounts that are configured on a separate host you can do this in oneof the following ways

n You start SAPinst and choose Software Life-Cycle Tasks Additional Preparation Tasks Operating SystemUsers and Groups For more information see Running SAPinst [page 95]

n You create operating system users and groups manually as described inCreating HP‒X Groups and Users (Optional) [page 62]

Operating System Users and Groups

SAPinst chooses available operating system user IDs and group IDs unless you are installing anadditional application server instance On an additional application server instance you have to enterthe same IDs as on the host of the primary application server instance

Caution

Do not delete any shell initialization scripts in the home directory of the OS users even if you do notintend to use the shells that these scripts are for

Caution

If you create the sdb user manually make sure that you lock it for the installation SAPinst normallylocks this user after it has been created

Caution

The user ID (UID) and group ID (GID) of each operating system user and group must be identical forall servers belonging to the same SAP systemThis does not mean that all users and groups have to be installed on all SAP servers

Users and Their Primary Groups

User Primary Group

ltsapsidgtadm sapsys

sqdltdbsidgt sapsys

sdb sdba

12142007 PUBLIC 61148


Operating System User for the Host Agent

User Primary Group

sapadm sapsys sapinst

Caution

If these operating system users already exist make sure that they are assigned to group sapinst

Caution

If you install a distributed system and you do not use central user management (for example NIS)and you use local operating system user accounts instead ltsapsidgtadm and the database operatingsystem user must have the same password on all hosts

Groups and Members

Groups Members

sapsys sqdltdbsidgt ltsapsidgtadm

sdba sdb ltsapsidgtadm sqdltdbsidgt


User Primary Group


341 Creating HP-UX Groups and Users (Optional)

Here you can find information about how to create operating system users and groups on HP-UX

Note

To prevent terminal query errors in the ltsapsidgtadm environment change the following shelltemplate as follows

1 Edit etcskellogin2 Comment out (with ) the following line

eval lsquotset -s -Q -m rsquohprsquo

For more information see SAP Note 1038842

Procedure for HP-UX 11111123

1 Enter the following command

62148 PUBLIC 12142007

3 Preparation35 Preparing User Management for an External ABAP System

usrsbinsam

2 Choose Accounts for Users and Groups Local Users Actions Add 3 Enter the required users4 Choose Accounts for Users and Groups Groups Actions Add 5 Enter the required groups6 Exit the System Administration Manager (SAM)7 Verify that the TZ settings in the following are consistent

etcTIMEZONE

etcprofile

etccshlogin



n usrsbinsmh


where ltportgt is either the default port 2381 or your defined port (for example 2301)2 Choose Accounts for Users and Groups Local Users Add User Account 3 Enter the required users4 Choose Accounts for Users and Groups Groups Add new Group 5 Enter the required groups6 Exit SMH7 Verify that the TZ settings in the following are consistent

etcTIMEZONE

etcprofile

etccshlogin

More InformationFor more information about the users and groups that are created either by SAPinst or manually seeCreating Operating System Users and Groups [page 60]

35 Preparing User Management for an External ABAP System

For a Java system you can also deploy user management for an external ABAP system In this caseyou configure the User Management Engine (UME) of Application Server Java (AS Java) for theuser management of a separate ABAP systemIf you want to connect more than one Java system to the same ABAP system you need to work out aconcept for the communication administrator and guest users for each systemYou can take one of the following approaches

12142007 PUBLIC 63148


Approach Advantages Disadvantages

Each Java system uses differentusers

No interdependencies between theconnected engines

Initially more administration tocreate the users in the ABAP system

All Java systems use the sameconfiguration

You create the users only once andenter the same information forevery Java systems that you install

Interdependencies between theconnected enginesn If you change the password of

any of the users on the ABAPsystem this change affects allconnected engines

n If you change the administratoruserrsquos password you must alsochange the password in securestorage on all of the connectedJava systems

Recommendation

For security reasons we recommend the first approach

The procedures below assume that you are using the first approach

Prerequisites

n The ABAP system is based on at least SAP Web AS ABAP release 620 SP25n In transaction PFCG check that the roles SAP_BC_JSF_COMMUNICATION and

SAP_BC_JSF_COMMUNICATION_RO exist and make sure that their profiles are generatedn In transaction PFCG check that the roles SAP_J2EE_ADMIN SAP_J2EE_GUEST and SAP_BC_FP_ICF

exist Neither role contains any ABAP permissions so you do not need to generate any profilesn For more information see the SAP Library [page 13]

Function-Oriented View Security Identity Management Identity Management of the Application Server JavaUser Management Engine

Note

For more information about role maintenance see the SAP Library [page 13] atFunction-Oriented View Security Identity Management Identity Management of the Application Server ABAP

AS ABAP Authorization Concept

Administration of the ABAP systemPerform the following administration steps in the ABAP system

1 In transaction SU01 create a new communication user and assign it to the roleSAP_BC_JSF_COMMUNICATION_RO

64148 PUBLIC 12142007


Recommendation

We recommend that you assign this user the role SAP_BC_JSF_COMMUNICATION_RO for read-only(display) access to user data with Java tools If you intend to maintain user data (that is to changecreate or delete users) with Java tools you need to assign the role SAP_BC_JSF_COMMUNICATIONinsteadWe recommend that you name the user SAPJSF_ltSAPSID_Java_SystemgtYou can use any password

In addition to make sure that this user can only be used for communication connections betweensystems and not as a dialog user assign it the type Communications under Logon data

2 In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_ADMIN This is youradministrator user in AS Java

Recommendation

We recommend that you name the user J2EE_ADM_ltSAPSID_Java_Systemgt You can use anypassword

Caution

Log on to the SAP system once with this user to change its initial password Because the installerof AS Java verifies this password the installation fails if this password is initial

3 In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_GUEST This is yourguest user in AS Java

Recommendation

We recommend that you name the user J2EE_GST_ltSAPSID_Java_Systemgt You can use anypasswordAs this user is only used for anonymous access to the system we recommend you to deactivatethe password and if required lock it after installation to prevent anyone from using it for explicitnamed logons

4 In transaction SU01 create the following dialog users

Caution

You must have changed the initial passwords of these users before you start the installation ofthe Java system

n Users for Adobe Document Services (ADS) (optional)l ADSUSER

In transaction PFCG assign the role ADSCallers to this user

12142007 PUBLIC 65148

3 Preparation36 Setting Up File Systems and Raw Devices

l ADS_AGENTIn transaction PFCG assign the role SAP_BC_FP_ICF to this user

n SLD Data supplier user (optional)You only have to create this user if you want to install System Landscape Directory (SLD)The SLD data supplier user name that you enter later on during the Java system installationmust be identical to this user

Recommendation

We recommend that you name this user SLDDSUSER

n SLD ABAP API user (optional)You only have to create this user if you want to install System Landscape Directory (SLD) TheSLD ABAP API user name that you enter later on during the Java system installation must beidentical to this user

Recommendation

We recommend that you name this user SLDAPIUSER

Note

For more information on SLD users and security roles see the SAP Library [page 13] atAdministratorrsquos Guide Technical Operations for SAP NetWeaver Software Life-Cycle Management

Configuring Working with and Administering System Landscape Directory Administrating the SLD

Activities for the Java SystemPerform the following steps in the Java system

1 Before the installation of the Java system make sure that you have the correct user names andpasswords of the users listed above for the separate ABAP system

2 During the installation of the Java system make sure that you enter the correct users andpasswords in the corresponding SAPinst dialogs

36 Setting Up File Systems and Raw Devices

The following section(s) describe the directory structures for the SAP system how to set up SAP filesystems for the SAP system and if required raw devices on operating system level

Note

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

n SAP Directories [page 67]n Performing Switchover Preparations for High Availability [page 60]

66148 PUBLIC 12142007


n MaxDB Directories [page 69]n Host Agent Directories [page 70]n Setting Up File Systems for High-Availability [page 70]n Configuring Network File System for High Availability [page 72]n Setting Up File Systems and Raw Devices for HP-UX [page 74]

361 SAP Directories

Here we describe the directories of a typical SAP systemSAPinst creates the following types of directories

n Physically shared directories which reside on the global host and are shared by Network FileSystem (NFS)

n Logically shared directories which reside on the local host(s) with symbolic links to the global hostn Local directories which reside on the local host(s)

FeaturesThe following figure shows the directory structure of the SAP system

Figure 12 Directory Structure for a Java System

Physically Shared Directories

SAPinst creates the following directories

12142007 PUBLIC 67148


n The directory ltsapmntgtltSAPSIDgt which contains SAP kernel and related files is created on thefirst installation host Normally the first installation host is the host on which the central servicesinstance is to run but you can also choose another host for ltsapmntgtltSAPSIDgtYou need to manually share this directory with Network File System (NFS) and ‒ for a distributedsystem ‒ mount it from the other installation hostsSAPinst creates the following shared directories during the SAP system installation

l global

Contains globally shared data

l profile

Contains the profiles of all instances

l exe

Contains executable kernel programsn The directory usrsaptrans which is the global transport directory

If you want to use an existing transport directory you have to mount it before you install theapplication server instance in question Otherwise SAPinst creates usrsaptrans locallyFor more information see Exporting and Mounting the Global Transport Directory [page 81]

Directory Required Disk Space

ltsapmntgtSAPSIDgt n Primary application server instance15 GB

n Central services instance10 GB

usrsaptrans This value heavily depends on the use of your SAP systemFor production systems we recommended to use as much free space as available (at least20 GB) because the space requirement normally grows dynamicallyFor the installation it is sufficient to use 200 MB for each SAP system instance You canenlarge the file system afterwards

Logically Shared Directories

SAPinst creates the directory usrsapltSAPSIDgtSYS on each host The sub-directories containsymbolic links to the corresponding sub-directories of ltsapmntgtltSAPSIDgt on the first installationhost as shown in the figure aboveWhenever a local instance is started the sapcpe program checks the executables against those in thelogically shared directories and if necessary replicates them to the local instance

Local Directories

The directory usrsapltSAPSIDgt contains files for the operation of a local instance as well assymbolic links to the data for one systemThis directory is physically located on each host in the SAP system and contains the followingsubdirectories

68148 PUBLIC 12142007


n SYS

Note

The subdirectories of usrsapltSAPSIDgtSYS have symbolic links to the correspondingsubdirectories of ltsapmntgtltSAPSIDgt as shown in the figure above

n ltINSTANCEgt for each instance installed on the hostThe instance-specific directories have the following namesl The directory both of the primary application server instance and of an additional application

server instance is called JltInstance_Numbergtl The directory of the central services instance is called SCSltInstance_Numbergt

l


The directory of the Enqueue Replication Server instance is called ERSltInstance_NumbergtEnd of HA (UNIX)


usrsapltSAPSIDgt Primary application server instance or additional application server instance25 GB

362 MaxDB Directories

These are the directories for the MaxDB database

MaxDB Directories

Directory Name Description Space Required

sapdbltDBSIDgtsapdata MaxDB data See the table Hardware Requirements in Requirements for theDatabase Instance [page 49]

NoteIf the database data is installed on raw devices you donot need to set up ltsapdatagt

sapdbltDBSIDgtsaplog MaxDBredologs

See the table Hardware Requirements in Requirements for theDatabase Instance [page 49]

NoteIf the database data is installed on raw devices you donot need to set up ltsapdbloggt

sapdb MaxDBsoftware


12142007 PUBLIC 69148


363 Host Agent Directories

For the host agent the following directories are required

Directories Description Required Disk Space

usrsaphostctrl Contains the following directoriesn exe

Contains the profilehost_profile

n work

Working directory of the hostagent

70 MB


364 Setting Up File Systems for a High-Availability System

When you prepare a high-availability (HA) installation with switchover software you need to set upyour file systems as described here For more information consult your HA partner

PrerequisitesYou have already installed the hardware ‒ that is hosts disks and network ‒ and decided howto distribute the database SAP instances and (if required) Network File System (NFS) server overthe cluster nodes (that is over the host machines) For more information see Planning the SwitchoverCluster [page 31]

Procedure

1 Create the file systems or raw partitions for the central services instance on shared disks For moreinformation see Setting Up File Systems and Raw Devices [page 66]

Note

The file systems sapmntltSAPSIDgt and usrsaptrans are Network File Systems (NFS)However usrsapltSAPSIDgtltINSTTYPEgtltNRgt which should be part of a cluster is a file systemof the AS instance that is always mounted on the cluster node currently running the instance(not with NFS)Therefore if the host running the primary application server instance is not the NFS server hostyou might have to mount the file systems sapmntltSAPSIDgt and usrsaptrans on differentphysical disks from the file system usrsapltSAPSIDgtltINSTTYPEgtltNRgt

2 Use the following approach for the usrsapltSAPSIDgtltINSTTYPEgtltNRgt file system

70148 PUBLIC 12142007


The file system contains at least two subdirectoriesn SYS which contains links to the central directory sapmntltSAPSIDgtn ltINSTTYPEgtltNRgt ‒ where the name is defined by the type of services and the application server

number for example SCSltNRgt ‒ which contains data for the local Java central services instanceOnly the latter directory needs to be migrated with the AS instance during the switchover Sincethe SYS subdirectory contains only links that do not require any space you can create it locally oneach cluster node Other local instances can also reside locally such as an Enqueue ReplicationServer instance in usrsapltSAPSIDgtERSltNRgt which should not be affected by a switchoverTherefore insteadof usrsapltSAPSIDgt create a file system usrsapltSAPSIDgtltINSTTYPEgtltNRgt

with the usual ltgt substitutionsThe instance-specific directory name for the central services instance is normally SCSltNRgtMigrating only this directory avoids mount conflicts when switching over to a node on whichanother AS instance is already running The SCSltNRgt directory can join the usrsapltSAPSIDgttree instead of mounting on top of it

Note

This approach becomes increasingly important when you want to cluster the central servicesinstances with other local instances running on the cluster hosts outside the control of theswitchover software This applies to the Enqueue Replication Server (ERS) and additional ABAPor Java application server instances The result is a more efficient use of resources You must usethis approach for integrated installations of the application server with ABAP and Java stacks

3 You assign the local file systems to mount points4 You assign the shared file systems to mount points in appropriate failover groups

Example

The graphic below shows an example of the file systems and disks in an HA setupNote that this is only an example For more information on a setup that meets your needs consult

12142007 PUBLIC 71148


your HA partner

Figure 13

End of HA (UNIX)


365 Configuring Network File System for a High-AvailabilitySystem

If required you configure Network File System (NFS) which is a system-wide Single Point-of-Failure(SPOF) for a high-availability (HA) installation with switchover software For more informationconsult your HA partnerWe regard NFS as an extension to the operating system The switchover product protects NFS andmakes it transparently available to the SAP system in switchover situationsYou need to decide

n How to protect NFSn Which switchover cluster nodes NFS is to run on

The NFS configuration might depend on your database system The directories need to be availablefor the SAP system before and after a switchover

72148 PUBLIC 12142007


Procedure

1 Check the NFS directories several of which need to be shared between all instances of a systemThese directories are

n sapmntltSIDgtprofile

Contains the different profiles to simplify maintenance

n sapmntltSIDgtglobal

Contains log files of batch jobs and central SysLog

n usrsaptrans

Contains data and log files for objects transported between different SAP systems (for exampledevelopment ‒ integration) This transport directory ought to be accessible by at least one ASinstance of each system but preferably by all

n sapmntltSIDgtexe

Contains the kernel executables These executables ought to be accessible on all AS instanceslocally without having to use NFS The best solution is to store them locally on all AS instancehosts

2 Since you can protect NFS by a switchover product it makes sense to install it on a cluster nodeThe requirements of your database system might dictate how NFS has to be set up If requiredyou can configure the NFS server on the cluster node of the clustered application server instanceor the DBIn both cases the NFS clients use the virtual IP address to mount NFS If the second node is used asan additional SAP instance during normal operation (for example as an additional applicationserver instance) it also needs to mount the directories listed above from the primary nodeWhen exporting the directories with their original names you might encounter the problem ofa ldquobusy NFS mountrdquo on the standby node You can use the following workaround to solve thisproblema) On the primary server mount the disks containing the directories

exportusrsaptrans

exportsapmntltSIDgt

b) The primary server creates soft links to the directories with the original SAP namesusrsaptrans mdashgt exportusrsaptrans

sapmntltSIDgt mdashgt exportsapmntltSIDgt

Alternatively the primary server can also mount the directoriesexportusrsaptrans mdashgt usrsaptrans

exportsapmntSID mdashgt sapmntltSIDgt

c) The primary server exportsexportusrsaptrans

exportsapmntltSIDgt

d) The standby NFS mountsfrom virtIPexportusrsaptrans to usrsaptrans

from virtIPexportsapmntltSIDgt to sapmntltSIDgt

12142007 PUBLIC 73148


If the primary node goes down and a switchover occurs the following happens

n These directories on the standby node become busyusrsaptrans

sapmntltSIDgt

n The standby node mounts disks toexportusrsaptrans

exportsapmntltSIDgt

n The standby node configures the virtual IP address virtIPn The standby node exports

exportusrsaptrans

exportsapmntltSIDgt

n These directories on the standby node are accessible againusrsaptrans

sapmntltSIDgt

End of HA (UNIX)

366 Setting Up File Systems and Raw Devices for HP-UX

Here you can find information about how to set up file systems and raw devices on HP-UXUsing a Logical Volume Manager (LVM) lets you distribute partitions (logical volumes) across severaldisks (physical volumes) The individual logical volumes are grouped together into volume groupsFile systems can be larger than physical disks but not larger than the volume group

Note

Consider the SAP recommendations for data security when planning the distribution of data in LVM

Setting up File Systems Manually using LVM for HP-UX 1111 and 1123

1 Examine the device configuration You can use the following commandsn This command provides the device filenames and the hardware addresses of all available

devices using the device class diskioscan -f -C disk

n This command scans all the disks for the current LVM configurationvgscan -pv

Note

Make sure that you use option -p (preview) otherwise etclvmtab will be updated

2 You can determine disk type and size using the following command

74148 PUBLIC 12142007


diskinfo devrdskltdiskdevicegt

Example

diskinfo devrdskc2t5d0

3 Prepare disks by assigning an unused disk to a physical volume using the following commandpvcreate devrdskltdiskdevicegt

Example

pvcreate devrdskc2t5d0

4 Create volume group directory ltVG Namegt and group device file For each volume group in thesystem there must be a volume group directory that has a character device file named group in itmkdir devltVG Namegt

mknod devltVG Namegtgroup c 64 0xltnngt000

Note

ltnngt cannot exceed the kernel parameter maxvgs

5 Create the volume group by specifying which physical volumes (disks) belong to the groupvgcreate devltVG Namegt devdskltdiskdevicegt

Note

For large disk sizes and large numbers of disks you might need to increase the physical extent (PE)size of the volume group with the ndashs option and the maximum physical volume option -p

To add another disk to an existing volume group entervgextend devltVG Namegt devdskltdiskdevicegt

6 To check the size and number of physical disks you have in a volume group enter the followingcommandvgdisplay -v devltVG Namegt

7 Calculate the free space in the volume group as followsFree space = Free physical extents Size of physical extents

8 Create logical volumesCreate one logical volume for each file system as followsa) Enter the following command

lvcreate devltVG Namegt

b) Allocate the logical volume to a disk with the commandlvextend -L ltsize in MBgt devltVGNamegtltLVNamegt


ltSize in MBgt needs to be a multiple of the physical extent size otherwise the size is rounded up

12142007 PUBLIC 75148


You can determine the size of the logical volume using either of the following commands

n vgdisplay -v devltVG Namegt

n lvdisplay devltVG NamegtltLV Namegt

Note

n Write down the device names of the logical volumes (for example lv12) You need the devicenames later when creating and mounting the file systems

n You only need the following steps for file systems not for raw devices If you set up raw devicessee section Accessing Raw Devices below for more information

For the required size for each file system see SAP Directories [page 67] 9 Create the file systems that are required by SAPn For sapdata1 to sapdataltngt use the following command

newfs -F vxfs -b 8192 devltVG NamegtrltLV Namegt

n For all others use the following commandnewfs -F vxfs ndasho largefiles devltVG NamegtrltLV Namegt

10 Create mount directories using the following commandmkdir ltmountdirgt

11 Add the new file system to etcfstab using the following commanddevltVG NamegtltLV Namegt ltmountdirgt vxfs delaylognodatainlog 0 2

12 Mount the file systems by entering the following commandmount -a

Note

For more detailed information on performance optimization of HP-UXmount options see SAPNote 1077887

Note

The mount sequence is determined from file etcfstab

Note

When defining themount order sequence in etcfstab consider themount order dependenciesFor example sapmntltSAPSIDgtmust be mounted before sapmntltSAPSIDgtprofile

Setting up File Systems using SAM for HP-UX 1111 and 1123

Note

To create file systems with support for files larger than 2 GB choose Disks and Filesystems File SystemsModify FS Defaults Allow Large Files when creating the file systems with SAM


76148 PUBLIC 12142007


usrsbinsam

2 Choose the followingDisks and Filesystems Volume Groups Actions Create

3 Create all volume groups4 Choose the following

Disks and Filesystems Logical Volumes Actions Create5 Create all logical volumes6 Choose the following

Disks and Filesystems File Systems Actions Add Local File System Using the LVM7 Create filesystems8 Exit SAM9 Since it is not possible with SAM to define 8 KB block sizes follow steps 9 to 12 for manual file

system creation for sapdata1 to sapdataltngt as described in section Setting up File Systems Manuallyusing LVM for HP-UX 1111 and 1123 above that is the following stepsn Create the file system required by SAPn Create mount directories

n Add the new file system to the etcfstabn Mount the file system

Setting up File Systems Manually Using LVM for HP-UX 1131HP-UX 11i v3 introduces a new agile addressing scheme for mass storage devices with opaqueminor numbers persistent device special files (DSFs) and new hardware path types and formatsThe addressing scheme used in previous HP-UX releases ‒ called ldquolegacy addressingrdquo ‒ coexistswith this new scheme to ensure backward compatibility The legacy addressing will be deprecatedin a future HP-UX releaseFor more information on the changes between HP-UX 1123 and 1131 check the documentHP-UX 11iv3 Mass Storage Device Naming at httpdocshpcom

1 Examine the device configurationn The ioscan command provides the device file name and the hardware addresses of all available

devices using the device class diskl For persistent device files enter

ioscan -m lun

l For legacy device files enterioscan -f -C disk

n To show the mapping of the legacy device files and the persistent device files enterioscan -m dsf

n The following command scans all disks for the current LVMvgscan -pv

12142007 PUBLIC 77148


Note

Make sure that you use option -p (preview) otherwise etclvmtab is updated

2 You can determine disk type and size using the following commandn For persistent device files enter

diskinfo devrdiskltdiskdevicegt

Example

diskinfo devrdiskdisk6

n For legacy device files enterdiskinfo devrdskltdiskdevicegt

Example

diskinfo devrdskdisk6

3 Prepare disks by assigning an unused disk to a physical volume using the following commandn For persistent device files enter

pvcreate devrdiskltdiskdevicegt

Example

pvcreate devrdiskdisk6

n For legacy device files enterpvcreate devrdskltdiskdevicegt

Example


4 Create one or more volume group directories ltVG Namegt and group device files For each volumegroup in the system there must be a volume group directory that has a character device filenamed group in itExecute the following commandsmkdir devltVG Namegt


Note


5 Create the volume group by specifying which physical volumes (disks) belong to the groupn For persistent device files enter the following command

vgcreate devltVG Namegt devdiskltdiskdevicegt

78148 PUBLIC 12142007


Note

For large disk sizes and large numbers of disks one might need to increase the volume groupphysical extent (PE) size with ‒s option and the maximum physical volume option -p

n For legacy device files enter the following commandvgcreate devltVG Namegt devdskltdiskdevicegt

n Proceed as follows to add another disk to an existing volume groupl For persistent device files enter the following command

vgextend devltVG Namegt devdiskltdiskdevicegt

l For legacy device files enter the following commandvgextend devltVG Namegt devdskltdiskdevicegt

6 To check the size and number of physical disks in a volume group enter the following commandvgdisplay -v devltVG Namegt

7 Calculate the free space in the volume group as followsFree space = number of free physical extents size of physical extents



b) Allocate the logical volume to a disk as followsn For persistent device files

lvextend -L ltsize in MBgt devltVGNamegtltltLVNamegt

devdiskltdiskdevicegt

n For legacy device fileslvextend -L ltsize in MBgt devltVGNamegtltltLVNamegt


ltsize in MBgt needs to be a multiple of the physical extent size otherwise the size is roundedupYou can determine the size of the logical volumes can be determined with either of thefollowing commands



Note

n Write down the device names of the logical volumes (for example lvo12) You need thedevice names later when creating and mounting the file systems

n You only need the following steps for file systems not for raw devices If you set up rawdevices see Accessing Raw Devices below for more information

For required size for each file system see SAP Directories [page 67]9 Create the file systems that are required by SAP as follows

12142007 PUBLIC 79148


n For sapdata1 to sapdataltngt enter the followingnewfs -F vxfs -b 8192 devltVG NamegtrltLV Namegt

n For all others enter the following commandnewfs -F vxfs devltVG NamegtrltLV Namegt


11 Add the new file system to etcfstab

Example

devltVG NamegtltLV Namegt ltmountdirgt vxfs delaylognodatainlog 0 2

Note


Note

When defining the mount order sequence in etcfstab you have to considermount order dependencies For example sapmntltSAPSIDgt must be mounted beforesapmntltSAPSIDgtprofile


Setting up File Systems using SMH for HP-UX 1131


n usrsbinsmh


where ltportgt is either the default port 2381 or your defined port (for example 2301)2 Choose the following to create a volume group

Disks and File Systems Volume Groups Create Volume Group You need to define your volume group name used disks and size

3 Choose Create4 Choose the following to create a logical volume

Disks and File Systems Logical Volumes Create LVCreate all logical volumes you need

5 Proceed as follows to create your file systema) Choose Disks and File Systems File Systems Add VxFS b) Enter your mountpointc) Select an Unused LV or Unused Diskd) Make sure that Enable large files(largefilesnolargefiles) is selected

80148 PUBLIC 12142007

3 Preparation37 Exporting and Mounting the Global Transport Directory

e) Choose Advanced VxFS Optionsn For sapdata1 to sapdataltngt select Block size 8192n For origlog and mirrlog select Block size 1024n For all other file systems select default Block size

f) Choose Add VxFS6 Exit SMH

Accessing Raw DevicesFile systems and raw devices differ in the way that data is written to and read from disk

n BufferedReads and writes to a file system are buffered in a UNIX system To be absolutely sure that all datais physically present on a disk the buffers and files must be synchronizedUnbuffereddirect IOIO to a raw device is sent directly to the disk which is faster and more secureUnbuffered IO is also possible via VxFS file systems For more information see SAP Note 1077887

n File accessAccessing files on a UNIX file system is transparent Accessing data on a raw device is only possiblewith a special application

Some databases prefer raw devicesFor MaxDB it is not necessary to create symbolic links to access raw devices because SAPinst createsthese links

37 Exporting and Mounting the Global Transport Directory

In your SAP system landscape a global transport directory for all SAP systems is requiredDuring the installation you can select the check box SAP System will be under NWDI control on the screenNWDI Landscape Then SAPinst copies all SCAs belonging to the software units that you installed to theglobal transport directoryFor more information see the SAP Library [page 13]Administratorrsquos Guide Software Life Cycle Management Software Logistics Using the Development and Production

Infrastructure

n If the global transport directory already exists make sure that it is exported on the global transportdirectory host and mount it on the SAP instance installation host

n If the global transport directory does not exist proceed as followsl Create the transport directory (either on the host where the primary application server

instance is running or on a file server)l Export it on the global transport directory host

12142007 PUBLIC 81148

3 Preparation38 Exporting and Mounting Directories via NFS for HP-UX (Optional)

l If you did not create the transport directory on your SAP instance installation host mount itthere

Exporting the Transport Directory

1 Log on as user root to the host where the global transport directory usrsaptrans resides2 Make sure that usrsaptrans belongs to the group sapsys and to the user root3 If not already done export the directory using Network File System (NFS)

Mounting the Transport Directory

Note

If the transport directory resides on your local SAP instance installation host you do not need tomount it

1 Log on as user root to the host of the primary or additional application server instance whereusrsaptrans is to be mounted

2 Create the mount point usrsaptrans3 Mount usrsaptrans using Network File System (NFS) from the exporting host

More InformationMounting Directories via NFS for HP-UX (Optional) [page 82]

38 Exporting and Mounting Directories via NFS for HP-UX(Optional)

You can mount directories via NFS in one of the following ways

n Using SAM (for HP-UX 11111123)n Using SMH (for HP-UX 1131)n Manually

Mounting Directories via NFS using SAM for HP-UX 11111123

Procedure on the Host Where the Main Instance Runs

1 To use SAM enter the following commandusrsbinsam

2 Choose Networking and Communications Networked File Systems Exported Local File Systems ActionsAdd

3 Enter the Local Directory Name to be exported

82148 PUBLIC 12142007


Example

sapmntC11

Select Specify UID for unknown user and enter at User ID the value 0Select Specify Root User Access and add the Remote System Names

4 Type OK5 Exit SAM

Procedure on the Host Where the Additional Instance Runs


2 Choose Networking and Communications Networked File Systems Mounted Remote File Systems ActionsAdd Remote File Systems Using NFS

3 Enter the following valuesn Local Directory Name

n Remote Server Name of the host exporting the file systemn Remote Directory Name

4 Enable the mount Now and On boot5 Specify Read-Write Access6 Type OK7 Exit SAM

Mounting Directories via NFS using SMH for HP-UX 1131



n usrsbinsmh


where ltportgt is either the default port 2381 or your defined port (for example 2301)2 Choose Tools Network Services Configuration Networked File Systems ShareUnshare File Systems (Export

FS) 3 Choose Share (Export) a File system4 Enter the local directory to be shared

Example

sapmntCUS

5 Enter your client host as the Root Access Client6 Select Specify UID for unknown user and enter at User ID the value 07 Enter OK

12142007 PUBLIC 83148


8 Exit SMH


1 Enter the following commandusrsbinsmh

2 Call httplthostnamegt2381 or your defined port such as 23013 Choose Disks and File System Tools File Systems Add NFS 4 Enter the following valuesn Mount pointn Remote server of the host exporting the file systemn Remote directory

5 Enable the optionMount now and save configuration in etcfstab6 Choose New NFS7 Exit SMH

Mounting Directories via NFS manually for HP-UX 11111123

Procedure on the Host where the Main Instance Runs

1 Add the file system that you want to export to the file etcexports using the option-root= ltnfs_cli_hostname_1gt lt nfs_cli_hostname_ngtgt

access= ltnfs_cli_hostname_1gtlt nfs_cli_hostname_ngt

Example

sapmntC11exe root=hw5111hw5115 access=hw5111hw5115

If you encounter problems with your input similar to the example above try the followinga) Use FQDN (Fully Qualified Domain Name)b) Check what the NFS server is exporting using the following command

showmount ndashe ltservernamegt

c) Try the anon option instead of rootsapmntC11exe anon=y access=hw5111hw5115

Note

For security reasons only use the following option during installation-root= ltnfs_cli__hostname_1gt ltnfs_cli_hostname_ngt

2 To make the file system available to NFS clients enter the following commandusrsbinexportfs -a

Procedure on the Host where the Additional Instance Runs

1 Add the remote file system to etcfstab

84148 PUBLIC 12142007


Example

hwi173sapmntC11 sapmntC11 nfs defaults 0 0

2 Mount the file system

Example

mount -a

Mounting Directories via NFS manually HP-UX 1131




Example

share ndashF nfs ndasho root=hw5111hw5115 access=hw511hw5115 sapmntC11exe

Note

If you are moving from a legacy system with the etcexportsNFS configuration file you can useusrcontribbinexp2dfs to automatically convert the legacy syntax to the new syntax



c) Try the anon option instead of rootshare -F nfs -o anon=y access=hw5111hw5115 sapmntC11exe

Note


2 To make the file system available to NFS clients enter the following commandusrsbinshareall



12142007 PUBLIC 85148

3 Preparation39 Generating the SAP Solution Manager Key

Example



Example

mount -a

39 Generating the SAP Solution Manager Key

The SAP Solution Manager is the strategic application management platform for customers and forcollaboration between customers and SAP You need a SAP Solution Manager to upgrade or installall SAP softwareDuring the installation of the primary application server instance you are prompted to enter theSAP Solution Manager KeyYou can generate all needed keys for your entire system landscape ‒ development quality assuranceand production systems ‒ in one SAP Solution Manager system Even if you plan to install severalsolution landscapes (for example in different countries) one SAP Solution Manager is still sufficientFor more information about SAP SolutionManager see httpservicesapcomsolutionmanager

Prerequisites

n You require at least SAP Solution Manager 40 Support Package Stack (SPS) 9n If required you can install SAP Solution Managerl You order SAP Solution Manager as described in SAP Note 628901l You install SAP Solution Manager as described in the documentation Installation Guide ‒ SAP

Solution Manager 40 on ltOSgt ltDatabasegt on SAP Service Marketplace athttpservicesapcominstguides SAP Components SAP Solution Manager Release 40

Procedure

1 In your SAP Solution Manager system call transaction SMSY (System Landscape Maintenance)2 To create your SAP system in the system landscape proceed as follows

a) Select the landscape component Systems and choose Create New System from the context menub) Enter the system ID in the dialog box as the systemc) Select the relevant product and the corresponding product version from the input help and

choose Saved) Fill in the system data as much as possible

For more information see the online help at Help Application Help e) Save your entries

3 To generate the key choose Other object from the menu System Landscape

86148 PUBLIC 12142007

3 Preparation310 Preparing the Installation DVDs

4 Set the indicator System and choose the system that you want to install from the input helpIf you created the system in the SAP Solution Manager in the previous step choose this system

5 Choose Generate Installation Upgrade Key6 Enter the requested information7 Choose Generate Key

ResultThe system displays the key Enter this key during the input phase of the installation

More InformationFor more information see also SAP Notes 805390 and 811923

310 Preparing the Installation DVDs

This section describes how to prepare the installation DVDs which are available as follows

n You obtain the installation DVDs as part of the installation package which is the normal casen You download the installation DVDs from SAP Service Marketplace as described at the end of

this section

1 Identify the required DVDs for your installation [page 15] as listed belowKeep them separate from the remaining DVDs as this helps you to avoid mixing up DVDs duringthe installation

Note

n The media names listed in the following table are abbreviatedYou can find the full names of all media shipped with SAP NetWeaver PI 71 in the appropriateMedia List (Media List ‒ SAP NetWeaver Process Integration 71) on SAP Service Marketplace athttpservicesapcominstguidesNWPI71 Installation

n You can find the Software Component Archives (SCAs) for the installation of SAP NetWeaverusage types on the NetWeaver Java DVD

SAP Instance Installation Required DVDs

Central services instance (SCS) n Installation Master DVDn NetWeaver Java DVDn Kernel DVD

Database instance n Installation Master DVDn Kernel DVDn NetWeaver Java DVDn RDBMS DVD

12142007 PUBLIC 87148



HA onlyEnqueue Replication Server

n Installation Master DVDn Kernel DVD

Primary application server instance n Installation Master DVDn NetWeaver Java DVDn Kernel DVDn RDBMS Client DVD

Additional application server instance n Installation Master DVDn NetWeaver Java DVDn Kernel DVDn RDBMS Client DVD

Host Agent (Standalone) n Installation Master DVDn Kernel DVD

2 Make the required installation media available on each installation hostIf you need information about how to mount DVDs on HP-UX seeMounting a CD DVD for HP-UX[page 125]

Note

Depending on your installation type one or more instances can reside on the same host Youneed to keep this in mind when you make the required installation media available on eachinstallation hostFor a standard system you need to make all required installation media available on the singleinstallation host

Use one of the following methods to make DVDs availablen Before the installation copy DVDs manually to local hard disksn During the installation use the SAPinst Media Browser dialog and copy the entire DVDs to

the path you entered in the Copy To column

Caution

n Mount the DVDs locally We do not recommend you to use Network File System (NFS)because reading from DVDs mounted with NFS might fail

n If you copy the DVDs to disk make sure that the paths to the destination location of the copiedDVDs do not contain any blanks

n If you perform a local installation and there is only one DVD drive available on yourinstallation host you must copy at least the Installation Master DVD to the local file system

Downloading Installation DVDs from SAP Service Marketplace (Optional)You normally obtain the installation DVDs as part of the installation package from SAPHowever you can also download installation DVDs from SAP Service Marketplace at

88148 PUBLIC 12142007


httpservicesapcomswdc Downloads Installations and Upgrades Entry by Application Groupltyour solutiongt ltrelease of your solutiongt ltyour operating systemgt ltyour databasegt

Note

If you download installation DVDs note that the DVDs might be split into several files In this caseyou have to reassemble the required files after the download

Caution

To extract the downloaded SAR files make sure that you use the latest SAPCAR version which youcan find on SAP Service Marketplace at httpservicesapcomswdc You need at least SAPCAR700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longerunpack current SAR files For more information see SAP Note 212876

1 Create a download directory on the host where you want to run SAPinst2 Identify all download objects that belong to one installation DVD according to one or both of the

followingn Material number

All download objects that are part of an installation DVD have the same material number andan individual sequence numberltmaterial_numbergt_ltsequence_numbergt

Example

51031387_151031387_2

n TitleAll objects that are part of an installation DVD have the same title such asltsolutiongtltDVD_namegtltOSgt or ltdatabasegtRDBMSltOSgt for RDBMS DVDs

3 Download the objects to the download directory4 Extract the individual download objects using SAPCAR starting with the lowest sequence number

‒ for example 51031387_1 then 51031387_2 and so onDuring the download SAPCAR sets up the structure of the installation DVD

Note

SAPCAR asks if you want to replace existing files for example LABELIDXASC Always acceptwith Yes

12142007 PUBLIC 89148

3 Preparation311 Creating a User for LDAP Directory Access

311 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 theSAP system is running This permits the SAP system to access and modify the LDAP directoryFor more information see section Setting Up the Active Directory Services in the Windows installationguide for your SAP system solution and database

PrerequisitesDuring the SAP instance installation you chose to configure the SAP system to integrate LDAP services

Procedure

1 Log on as user ltsapsidgtadm2 Enter

ldappasswd pf=ltpath_and_name_of_instance_profilegt

3 Enter the required data

Example

The following is an example of an entry to create an LDAP Directory UserCN=sapldapCN=UsersDC=nt5DC=sap-agDC=de

90148 PUBLIC 12142007

4 Installation

4 Installation

Installation Steps for a Standard System

1 You run SAPinst [page 95] to install the SAP system2 You can now continue withPost-Installation [page 105]

Installation Steps for a Distributed System

1 If you want to share the transport directory trans from another system you have to mount [page81] it from this system Otherwise we recommend that you share the trans directory that will becreated during the installation of the primary application server instance

2 On the SAP global host you do the followinga)b) You export global directories [page 94] in ltsapmntgtltSAPSIDgt to the database and primary

application server instance host3 On the database instance host you do the following

a) You mount the global directories [page 94] in ltsapmntgtltSAPSIDgt that you exported from the SAPglobal host and ‒ optionally ‒ the trans directory that you exported [page 81] from the SAPtransport host

b) You run SAPinst [page 95] to install the database instance4 On the primary application server instance host you do the following

a) You mount the global directories [page 94] in ltsapmntgtltSAPSIDgt that you exported from the SAPglobal host

b) You run SAPinst [page 95] to install the primary application server instancec) If you want to use the shared transport directory trans from another system also you also

mount [page 81] this directory5 If required you can now install one to n additional application server instance(s) [page 18]6 You can now continue with Post-Installation [page 105]

Installation Steps for a High-Availability System

1 If you want to share the transport directory trans from another system you have to mount [page81] it from this system Otherwise we recommend that you share the trans directory that will becreated during the installation of the primary application server instance (see below)

2 You set up the switchover cluster infrastructure as followsa) You run SAPinst [page 95] to install the central services instance (SCS) using the virtual host name

[page 94] on the primary cluster node host A

12142007 PUBLIC 91148

4 Installation

b) You prepare the standby cluster node host B making sure that it meets the hardware and softwarerequirements [page 43] and it has all the necessary file systems [page 70] mount points and (ifrequired) Network File System (NFS)

c) You set up the user environment on the standby node host BFor more information see Creating Operating System Users and Groups [page 60] You make sure thatyou use the same user and group IDs [page 60] as on the primary node You create the homedirectories of users and copy all files from the home directory of the primary node

d) You configure the switchover software and test that switchover functions correctly to allstandby nodes in the cluster

e) You perform the switchover to a node where you want to install the enqueue replicationserver (ERS)

f) You run SAPinst [page 95] to install the enqueue replication server (ERS)g) You repeat the previous two steps for all nodes in the cluster

3 You export global directories [page 94] in ltsapmntgtltSAPSIDgt to the database host and to the primaryapplication server instance host

4 On the database instance host you do the followinga) You make available the global directories in ltsapmntgtltSAPSIDgt from the switchover cluster

infrastructure and ‒ optionally ‒ from the SAP transport hostb) You run SAPinst [page 95] to install the database instance on the database instance host

5 On the primary application server instance host you do the following

Note

In a high-availability installation the primary application server instance does not need to bepart of the cluster because it is no longer a single point of failure (SPOF) The SPOF is now in thecentral services instance (SCS) which is protected by the cluster

a) You mount the global directories [page 94] in ltsapmntgtltSAPSIDgt that you exported from theswitchover cluster infrastructure

b) You run SAPinst [page 95] to install the primary application server instancec) If you want to use the shared transport directory trans from another system you also mount

[page 81] this directory (see above)6 We recommend you to install additional application server (AS) instances with SAPinst to create

redundancySince the AS instances are not a SPOF you do not need to include these instances in the cluster

7 You can now continue withPost-Installation [page 105]

Installation Steps for an Additional Application Server Instance

Installation Steps for Additional Application Server Instance(s) for a Standard System

1 On themain host on which your SAP system runs you do the following

92148 PUBLIC 12142007

4 Installation

You export global directories in ltsapmntgtltSAPSIDgt to the database and primary applicationserver instance host

2 On every additional application server instance host you do the followinga) You mount the global directories [page 94] in ltsapmntgtltSAPSIDgt that you exported from the SAP

global host b) You run SAPinst [page 95] to install the additional application server instance

3 You can now continue with Post-Installation [page 105]

Installation Steps for an Application Server Instance for a Distributed System


2 On the SAP global host you do the followingExport global directories in ltsapmntgtltSAPSIDgt to the database and primary application serverinstance host


global host b) You run SAPinst [page 95] to install the additional application server instancec) If you want to use the shared transport directory trans from another system also mount [page

81] this directory4 You can now continue with Post-Installation [page 105]

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 do the followingYou export global directories in ltsapmntgtltSAPSIDgt to every additional application server instancehost


global host b) You run SAPinst [page 95] to install the additional application server instancec) If you want to use the shared transport directory trans from another system you also mount

[page 81] this directory4 You can now continue with Post-Installation [page 105]

12142007 PUBLIC 93148

4 Installation41 Exporting and Mounting Global Directories

Installation Steps for a Standalone Host Agent

1 You run SAPinst [page 95] to install the host agent2 You can now continue with Post-Installation [page 105]

41 Exporting and Mounting Global Directories

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

PrerequisitesIf you want to install the executables locally instead of sharing them do notmount the exe directorywith Network File System (NFS) Instead create ltsapmntgtltSAPSIDgtexe as a local directory (nota link) with a minimum of 15 GB free space

Procedure

1 Log on to the SAP Global host as user root and export the following directories with root access tothe host on which you want to install the new instanceltsapmntgtltSAPSIDgtexe

ltsapmntgtltSAPSIDgtprofile

ltsapmntgtltSAPSIDgtglobal

For more information seeMounting Directories via NFS for HP-UX [page 82]Make sure that the user root of the host on which you want to install the new instance canaccess the exported directories

2 Log on to the host of the new instance that you want to install as user root3 Create the following mount points and mount them from the SAP Global host

ltsapmntgtltSAPSIDgtexe




42 High Availability Specifying the Virtual Host Name

For a high-availability (HA) system where you want to install the SCS or ASCS instance into a clusteryou can set the environment variable SAPINST_USE_HOSTNAME to specify the virtual host name beforeyou start SAPinstIf you do not set this environment variable now you can specify an equivalent parameter for thevirtual host name when you run SAPinst [page 95]

94148 PUBLIC 12142007

4 Installation43 Running SAPinst

ProcedureSet SAPINST_USE_HOSTNAME to the virtual host name of the machine on which you are installingan SAP instance


43 Running SAPinst

This procedure tells you how to install an SAP system with SAPinst SAPinst includes a SAPinst GUIand a GUI server which both use JavaThis section describes an installation where SAPinst SAPinst GUI and the GUI server are running onthe same host If required you can instead perform a remote installation with SAPinst [page 129] whereSAPinst GUI is running on a separate host from SAPinst and the GUI serverWhen you start SAPinst SAPinst GUI and the GUI server also start SAPinst GUI connects via a secureSSL connection to the GUI server and the GUI server connects to SAPinst

Note the following information about SAPinst

n SAPinst normally creates the installation directory sapinst_instdir directly below the temporarydirectory SAPinst finds the temporary directory by checking the value of the environmentvariables TEMP TMP or TMPDIR If no value is set for these variables SAPinst uses tmp as defaultinstallation directory

Recommendation

We recommend that you keep all installation directories until the system is completely andcorrectly installed

n SAPinst creates a subdirectory for each installation option calledltsapinst_instdirgtltinstallation_option_directorygt

n The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory Theseexecutables are deleted again after SAPinst has stopped runningDirectories called sapinst_exexxxxxxxxxx sometimes remain in the temporary directoryYou can safely delete themThe temporary directory also contains the SAPinst Self-Extractor log file dev_selfexout whichmight be useful if an error occurs

Caution

If SAPinst cannot find a temporary directory the installation terminates with the error FCO-00058

12142007 PUBLIC 95148


n During the installation the default ports 21200 21212 and 4239 are used for communicationbetween SAPinst GUI server SAPinst GUI and HTTP server SAPinst uses port 21200 tocommunicate with the GUI server The GUI server uses port 21212 to communicate with SAPinstGUI 4239 is the port of the HTTP server which is part of the GUI server You get an error messageif one of these ports is already in use by another serviceIn this case you must execute sapinst using the following parametersSAPINST_DIALOG_PORT=ltfree_port_number_sapinst_to_gui_servergt

GUISERVER_DIALOG_PORT=ltfree_port_number_gui_server_to_sapinst_guigt

GUISERVER_HTTP_PORT=ltfree_port_number_http_servergtn To get a list of all available SAPinst properties start SAPinst as described above with the option -p

sapinst -pn If required you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl + C

Using SAPinst GUI

The following table shows the most important functions that are available in SAPinst GUI

SAPinst GUI Functions

Input Type Label Description

Function key F1 Displays detailed information about each inputparameter

Menu option File Exit Stops the SAPinst GUI but SAPinst and the GUIserver continue running

NoteIf you need to log off during the installation fromthe host where you control the installation withSAPinst GUI the installation continues while youare logged off You can later reconnect to the sameSAPinst installation from the same or another hostFor more information see Starting SAPinst GUISeparately [page 130]

Menu option SAPinst Log Browser Displays the Log Viewer dialogThis dialog enables you to access the following logfiles directlyn Installation log (sapinst_devlog)n Log files from the SAPinst GUI serverThese log files might help you during troubleshootingwith SAPinst [page 133]

96148 PUBLIC 12142007



Menu option SAPinst Cancel Cancels the installation with the following optionsn Stop

Stops the installation (SAPinst GUI SAPinst andthe GUI server) without further changing theinstallation filesYou can restart and continue the installationlater from this point

n ContinueContinues the installation

Message button Retry Performs the installation step again (if an error hasoccurred)

Message button Stop Stops the installation without further changing theinstallation filesYou can continue the installation later from thispoint

Message button Continue Continues with the option you have chosen before

Prerequisites

n Make sure that your operating system does not delete the contents of the temporary directorytmp or the contents of the directories to which the variables TEMP TMP or TMPDIR point forexample by using a crontab entryMake sure that the temporary directory has the permissions 777

n Make sure that you have at least 60MB of free space in the installation directory for each installationoption In addition you need 200 MB free space for the SAPinst executables If you cannot provide200 MB free space in the temporary directory you can set one of the environment variables TEMPTMP or TMPDIR to another directory with 200 MB free space for the SAPinst executables

n Make sure that your DISPLAY environment variable is set to lthost_namegt00 where lthost_namegtis the host on which you want to display the SAPinst GUI

Shell Used Command

Bourne shell (sh) DISPLAY=lthost_namegt00

export DISPLAY

C shell (csh) setenv DISPLAY lthost_namegt00

Korn shell (ksh) export DISPLAY=lthost_namegt00

n Make sure that you have defined the most important SAP system parameters as described in BasicSAP System Parameters [page 37] before you start the installation

n Check that your installation host(s) meets the requirements for the installation option(s) that youwant to install For more information see Running the Prerequisite Checker [page 45]

12142007 PUBLIC 97148


Procedure

1 Log on to your host as user root

Caution

Make sure that the root user has not set any environment variables for a different SAP system ordatabase

2 If you want to install a primary application server instance a central services instance a databaseinstance or an additional application server instance mount the Installation Master DVDMount the DVDs locally We do not recommend that you use Network File System (NFS)because reading from DVDs mounted with NFS might failFor more information about mounting DVDs seeMounting a CD DVD for HP-UX [page 125]

3 Start SAPinst from the Installation Master DVD in one of the following waysn Using the default installation directory (recommended)

Enter the following commandscd ltmountpoint_of_Installation Master_DVDgtDATA_UNITSIM_ltOSgt_ltDBgt

sapinst

Example

For example if the mountpoint of the Installation Master DVD is sapcd2 the operating systemis LINUX_X86_64 and the database is Oracle the commands are as followscd sapcd2DATA_UNITSIM_LINUX_X86_64_ORA

sapinst


Note

If you are installing a high-availability system and you have not already set the environment parameterSAPINST_USE_HOSTNAME [page 94] to specify the virtual host name you can start SAPinstas followssapinst SAPINST_USE_HOSTNAME=ltvirtual host namegt

End of HA (UNIX)

98148 PUBLIC 12142007


Caution

Make sure that your current working directory is not an IM_ltOSgt_ltDBgt directory belonging toanother operating systemFor example if your operating system is HP-UX PARISC and your database is Oracle thefollowing commands are incorrect and cause an error$ cd sapcd2DATA_UNITSIM_HPUX_IA64_ORA

$ sapcd2DATA_UNITSIM_HPUX_PARISC_ORAsapinst

The following commands are correct$ cd sapcd2DATA_UNITSIM_HPUX_PARISC_ORA


n Using an alternative installation directoryIf you want to use an alternative installation directory set the environment variable TEMPTMP or TMPDIR

Shell Used Command

Bourne shell (sh) TEMP=ltdirectorygt

export TEMP

C shell (csh) setenv TEMP ltdirectorygt

Korn shell (ksh) export TEMP=ltdirectorygt

4 In theWelcome screen choose the required SAPinst installation option from the tree structureunder the SAP NetWeaver Process Integration 71 Adaptive Computing Controller with ltyour databasegtnodeFor more information see SAPinst Installation Options [page 100]

5 Follow the instructions in the SAPinst input dialogs and enter the required parameters

Note

To find more information on each parameter during the input phase of the installation positionthe cursor on the required parameter and press F1

After you have entered all requested input parameters SAPinst displays the Parameter Summaryscreen This screen shows both the parameters that you entered and those that SAPinst set bydefault If required you can revise the parameters before starting the installation

6 To start the installation choose StartSAPinst starts the installation and displays the progress of the installation When the installationhas successfully completed SAPinst shows the dialog Execution of ltoption_namegt has been completedsuccessfully

7 If required delete directories with the name sapinst_exexxxxxxxxxx after SAPinst has finishedSometimes these remain in the temporary directory

12142007 PUBLIC 99148

4 Installation44 SAPinst Installation Options

Note

If there are errors with SAPinst Self-Extractor you can find the Self-Extractor log filedev_selfexout in the temporary directory

Recommendation

We recommend that you keep all installation directories until you are sure that the system iscompletely and correctly installed

8 We recommend you to delete all files in the directory ltuser_homegtsdtgui9 If you have copied installation DVDs to your hard disk you can delete these files when the

installation has successfully completed

More Information

n Interrupted Installation with SAPinst [page 127]n Performing a Remote Installation with SAPinst (Optional) [page 129]n Starting SAPinst GUI Separately (Optional) [page 130]n Entries in the Services File Created by SAPinst [page 132]n Troubleshooting with SAPinst [page 133]

44 SAPinst Installation Options

This section provides information about the following installation options in SAPinst

n Installation Options

n Software Life-Cycle Options

Note

n Choose the required installation options from the tree structure exactly in the order they appearfor each system variant

n If you want to use global accounts which are configured on separate hosts you must run theinstallation option Operating System Users and Groups before you start the installation of the SAPsystem (see table Software Life-Cycle Options below)

n If required install an additional application server instance for a standard system (all instances onone host) or distributed system by choosing ltSAP Systemgt Software Life-Cycle Options AdditionalApplication Server Instance Additional Application Server Instance

Installation Options

You choose SAP Systems with ltyour databasegt to install a SAP system with usage types or software unitsYou can install the following system variants

100148 PUBLIC 12142007


n Standard System

Installation Options for a Standard System

Installation Option Remarks

Standard System Installs a complete SAP system including the followinginstances on one hostl Central services instance (SCS)l Database instancel Primary application server instanceYou can install a standard system in the following parametermodesl Typical Mode

If you choose Typical automatic default settings will beprovided You only have to respond to a small selectionof prompts However you can change any of the defaultsettings on the parameter summary screen

l Custom ModeIf you choose Custom all installation parameter will beprompted In the end you can still change any of theseparameters on the parameter summary screen

NoteYou require at least usage type AS Java or AS ABAP You canchoose the usage types or software units on the next screen

n Distributed System

Installation Options for a Distributed System

Installation Options Remarks

Central Services Instance (SCS) Installs a central services instance (SCS) and prepares theSAP global hostMandatory step in installing a distributed SAP system withusage types or software units based on AS Java

Database Instance Installs a database instanceMandatory step in installing a distributed SAP systemYou must have finished the Central Services Instance (SCS)installation before you can choose this installation option

Primary Application Server Instance Installs a primary application server instance and enablesadditional software unitsMandatory step in installing a distributed SAP system onseveral hostsYou must have finished the database instance installation

12142007 PUBLIC 101148


n

Only valid for HA (MSCS)HA (UNIX)HA (zOS)

High-Availability System

Installation Options for a High Availability System


Central Services Instance(SCS)

Installs a central services instance (SCS)

Database Instance Installs a database instance

Enqueue ReplicationServer Instance

Installs an enqueue replication server which contains a replica of the locktable (replication server)

NoteMake sure that you have configured the SCS instance for the switchovercluster before you start this installation option

Primary ApplicationServer Instance

Installs a primary application server instance and enables additional usagetypes or software units

Additional ApplicationServer Instance

Installs an additional application server instance

End of HA (MSCS)HA (UNIX)HA (zOS)

Software Life-Cycle Options

You use the options located in this folder to perform the following tasks or to install the followingcomponents


Additional Preparations n Host AgentChoose Additional Preparations Host Agent Host Agent to install thehost agent with the profiles SAPSystem=99 and SAPSystemName=SAPThe host agent contains all of the required elements for centrallymonitoring any hostNormally you do not need to install a standalone host agent because itis automatically installed during the installation of all SAP NetWeavercomponents except TREXYou only need to install a standalone host agent in the following casesl You want to centrally monitor a host that does not have an SAP

componentl You want to perform an upgrade to SAP NetWeaverFor more information see Standalone Host Agent [page 21]

n Operating system users and groupsAllows you to use global accounts that are configured on a separatehost

102148 PUBLIC 12142007



CautionPerform this SAPinst option before you start the installation of yourSAP system

n Prerequisites checkChoose Additional Preparations Prerequisites Check if you want tocheck your hardware and software requirements before you start theinstallationOtherwise SAPinst automatically checks the hardware and softwarerequirements during the installation with the Prerequisite Checker If anychanges are necessary to the SAP system or operating system settingsSAPinst automatically prompts you For more information see Runningthe Prerequisites Checker in Standalone Mode [page 45]

LDAP Registration LDAP SupportSets up LDAP support for an application server instanceChoose this option once per SAP system and after you have

1 Configured the Active Directory on a Windows host by choosingLDAP Registration Active Directory Configuration

You have to configure the directory server only once Afterwards all SAPsystems that should register in this directory server can use this setup

NoteThe option Active Directory Configuration is only available for Windows

2 Installed an application server instanceFor more information on LDAP and Active Directory see Integration of LDAPDirectory Services [page 27]

Additional Application ServerInstances

Choose Additional Application Server Instances Additional Application ServerInstance to install one or more additional application server instance(s)in an already installed SAP system if required

System Copy Choose this option to perform a system copyFor more information see the system copy guide for your SAP system onSAP Service Marketplace athttpservicesapcominstguides ltSAP systemgt Installation

NoteYou cannot perform a system copy for ACC

Uninstall Choose this option to uninstall your SAP system standalone engines oroptional standalone unitsFor more information see Deleting an SAP System [page 142]

12142007 PUBLIC 103148


5 Post-Installation

5 Post-Installation

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

n Standard distributed or high-availability systemn Additional application server instancen Standalone host agent


Note


1 If required you perform a full installation backup [page 123] immediately after the installation has finished2 You check whether you can log on to the SAP system [page 106]

Note

In a distributed or high-availability system you check whether your can log on to every instanceof the SAP system that you installed

3 You ensure user security [page 117]4 You install the SAP license [page 107]

5


You set up the licenses for high availability [page 109]End of HA (UNIX)

6 You configure the remote connection to SAP support [page 108]7 If required you install MaxDB administration tools [page 111]8 If required you install Secure Sockets Layer (SSL) for MaxDB [page 112]9 You back up the MaxDB database [page 117]10 You update the database software to the current release [page 117]11 On the primary application server instance host you apply the latest kernel and Support Packages [page 108]12 If required you configure user management to use an LDAP directory [page 120]13 You check the Java manuals [page 121] for information that is relevant for running your Java system14 You configure the Adaptive Computing Controller (ACC) [page 122]15 You perform a full installation backup [page 123]

12142007 PUBLIC 105148

5 Post-Installation51 Logging On to the Application Server


1 If required you perform a full installation backup [page 123] immediately after the installation has finished2 You check whether you can log on to the additional application server instance [page 106]3 If required you configure user management to use an LDAP directory [page 120]4 You perform a full installation backup [page 123]

Standalone Host Agent

You perform the post-installation steps for the Host Agent [page 120]

51 Logging On to the Application Server

You need to check that you can log on to the application server using the following standard users

Java Standalone Users

User User Name StorageDatabase

User Name StorageExternal ABAP System

Administrator Administrator You create this user manuallyduring the installation process

RecommendationWe recommend thatyou call the userJ2EE_ADM_ltSAPSID_Java_Systemgt

The maximum length is 12characters

Prerequisites

n The SAP system is up and running

Logging On to the Java Application ServerYou access AS Java with a URL using a Web browser from your client machines To log on to the Javaapplication server proceed as follows

1 Start a Web browser and enter the following URLhttplthostname_of_Java EE_Engine_Servergt5ltInstance_Numbergt00

Note

You must always enter a two-digit number for ltInstance_Numbergt For example do not enter 1but instead enter 01

106148 PUBLIC 12142007

5 Post-Installation52 Installing the SAP License

Example

If you installed the SAP NetWeaver Application Server Java on host saphost06 and the instancenumber of your SAP NetWeaver Application Server Java is 04 enter the following URLhttpsaphost0650400

The start page of the SAP NetWeaver Application Server Java appears in the Web browser2 Log on by pressing the icon of any of the provided applications for example the SAP NetWeaver

Administrator

52 Installing the SAP License

You must install a permanent SAP license When you install your SAP system a temporary licenseis automatically installed This temporary license allows you to use the system for only four weeksfrom the date of installation

Caution

Before the temporary license expires you must apply for a permanent license key from SAPWe recommend that you apply for a permanent license key as soon as possible after installing yoursystem

ProcedureFor information about the installation procedure for the SAP license see the SAP library [page 13]SAP NetWeaver Process Integration Library Administratorrsquos Guide Technical Operations Manual for SAP

NetWeaver (TOM) General Administration Tasks License Administration

More InformationFor more information about SAP license keys and how to obtain them see SAP Service Marketplace athttpservicesapcomlicensekey

53 Configuring the Transport Management System

You have to perform some steps to be able to use the Transport Management System

Procedure

1 Perform post-installation steps for the transport organizera) Call transaction SE06b) Select Standard Installationc) Choose Perform Post-Installation Actions

12142007 PUBLIC 107148

5 Post-Installation54 Configuring the Remote Connection to SAP Support

2 Call transaction STMS in your SAP Solution Manager system to configure the domain controllerin the Transport Management System (TMS)

ResultYou can now perform Java transports in the TMS of your SAP Solution Manager system

More InformationFor more information see the SAP Library [page 13]Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Change and Transport

System

54 Configuring the Remote Connection to SAP Support

SAP offers its customers access to support and a number of remote services such as the EarlyWatchService or the GoingLive Service Therefore you have to set up a remote network connection to SAPFor more information see SAP Service Marketplace at httpservicesapcomremoteconnection

55 Applying the Latest Kernel and Support Packages

You have to apply the latest kernel and Support Packages for your SAP system from SAP ServiceMarketplace

Caution

Before you apply support packages make sure that you read the release notes for your SAP systemYou can find these on SAP Service Marketplace at httpservicesapcomreleasenotes Therelease notes might include information about steps you have to perform after you have appliedthe support packages

Caution

Make sure that the entry DIR_CT_RUN exists in the instance profile Otherwise you cannot restart thesystem after patches have been applied

You can use Java Support Package Manager (JSPM) to apply both the latest ABAP+Java or Java kerneland Java support packagesJSPM is a Java standalone tool that you can use with SAP NetWeaver 71 JSPM uses the SoftwareDeployment Manager (SDM) to apply support packages and patches and to deploy softwarecomponents

108148 PUBLIC 12142007

5 Post-Installation56 High Availability Setting Up Licenses

Formore information about JSPM and how to use this tool see the SAP Library [page 13] AdministratorrsquosGuide Technical Operations for SAP NetWeaver General Administration Tasks Software Life-Cycle ManagementSoftware Logistics Application Server Java (AS Java) Software Logistics Software Maintenance Java Support

Package Manager (JSPM)

Procedure

1 Apply the latest kernelYou must always replace the installed kernel with the latest kernel from SAP Service MarketplaceIn particular you must replace the installed kernel ifn You installed the kernel executables locally on every hostn Your central instance host runs on a different operating system than your dialog instance hostFor more information about how to download a kernel see SAP Note 19466To exchange the ABAP+Java kernel you can use Java Support Package Manager (JSPM)

2 Apply Support Packagesa) For up-to-date information about recommended combinations of Support Packages and

patches see SAP Service Marketplace athttpservicesapcomsp-stacks

b) Alternatively you can download Support Packages from SAP Service Marketplace athttpservicesapcompatches

c) Apply the Java Support Packages to your SAP system with the help of the Java Support PackageManager (JSPM)

For more information about the availability of Support Packages see the SAP Service Marketplaceathttpservicesapcomocs-schedules

Note

The SAP Note Assistant lets you load implement and organize individual SAP Notes efficiently Italso recognizes dependencies between SAP Notes Support Packages and modificationsFor more information see the SAP Service Marketplace athttpservicesapcomnoteassistant


56 High Availability Setting Up Licenses

If your high-availability (HA) installation is running a two-node switchover cluster you need toorder two SAP licenses [page 107] When we receive confirmation from your vendor that you areimplementing a switchover environment we provide two license keys for your system one key for

12142007 PUBLIC 109148


each machine You need to order as many licenses as you plan to have cluster nodes running thecentral services instance


If your high-availability (HA) installation is running a two-node switchover cluster you need to ordertwo SAP licenses When we receive confirmation from your vendor that you are implementing aswitchover environment we provide two license keys for your system one key for each machine Youneed to order as many licenses as you plan to have cluster nodes running the central services instanceEnd of HA (UNIX)

SAP has implemented a license mechanism for transparent and easy use with switchover solutionsand clustered environments Your customer key is calculated on the basis of local information on themessage server host This is the host machine where the central services instance runsA switchover involving the central services instance affects the licensing mechanism so for this caseyou must have two licenses which you can install in parallel There is no license problem when onlythe database is switched over

Procedure

1 Run the central services instance on the primary host node A2 To find the hardware key of the primary host run the SAP NetWeaver Administrator (NWA) on

any application server instance and choose Configuration Management Infrastructure ManagementLicenses The hardware key is displayed in the NWA

3 Perform a switchover of the central services instance to another node in the cluster and repeatthe previous stepRepeat this for all remaining nodes in the cluster

4 To obtain the license keys enter the hardware keys for the cluster nodes in SAP ServiceMarketplace athttpservicesapcomlicensekey

5 Open the NWA on any application server instance and choose Configuration ManagementInfrastructure Management Licenses to import the file containing the licenses to the primary clusternode

6 Perform a switchover to another node in the cluster and repeat the previous stepRepeat this for all remaining nodes in the cluster

ResultThe license is no longer a problem during switchover This means you do not need to call saplicensein your switchover scriptsEnd of HA (UNIX)

110148 PUBLIC 12142007

5 Post-Installation57 Installing Administration Tools for MaxDB

57 Installing Administration Tools for MaxDB

This section describes how to install the following administration tools for MaxDB and SAP liveCacheon Windows front ends

n Database Manager GUIYou can use Database Manager GUI to administer databases including remote ones

n SQL Studio (GUI)You can use SQL Studio (GUI) to send SQL statements to the database and evaluate the results

For more information on these tools see the following documentation

n Database Manager GUI

n SQL Studio (GUI)

You can find this documentation as well as information about additional MaxDB tools in the SAPLibrary [page 13]Function-Oriented View Databases MaxDB Tools

Prerequisites

n You can install these administration tools on any Windows PC in your network even if yourdatabase runs on UNIX From the PC with the installed administration tool you can thenadminister the database or send queries to it

n Your PC must meet the following minimum operating system requirements

Installing Administration Tools for MaxDB

Operating System Version

Windows 2000 Any

Windows 2003 Any

n Your PC must meet the following minimum hardware requirementsl Pentium II

l 64 MB RAM

l 100 MB disk spacen You can get the required files from one of the followingl The MaxDB RDBMS or SAP liveCache DVD

l By downloading from SAP Service Marketplace athttpservicesapcompatches Entry by Application Group Additional Components MaxDB

MaxDB GUI COMPONENTSTOOLS

12142007 PUBLIC 111148

5 Post-Installation58 Secure Sockets Layer Protocol for Database Server Communication

Caution

If MaxDB or liveCache is installed on the PC you must not install the administration tools in thesame directory You can check the directories used by MaxDB or liveCache as followsdbmcli -d ltDBSIDgt -u ltcontrolusergtltpasswordgt dbm_getpath

IndepDataPath

dbmcli -d ltDBSIDgt -u ltcontrolusergtltpasswordgt dbm_getpath

IndepProgPath

Procedure

1 Start the installation as followsn If you are using theMaxDB RDBMS DVDl DBMGUI

ltDVDgtMaxDB_Windows_ltProcessorgtSETUPSDBM76EXE

l SQL StudioltDVDgtMaxDB_Windows_ltProcessorgtSETUPSSQLSTD76EXE

n If you are using the liveCache DVDl DBMGUI

ltDVDgtLC_Windows_ltProcessorgtSETUPSDBM76EXE

l SQL StudioltDVDgtLC_Windows_ltProcessorgtSETUPSSQLSTD76EXE

n If you are using the files from SAP Service Marketplace simply execute the downloadedEXE file

An installation shield guides you through the installation

Note

If you already have an older version of the administration tools installed on the PC theinstallation shield offers to upgrade it for you

2 If you are prompted to restart the PC after the installation make sure that you first bring downany databases that are running as followsdbmcli -d ltDBSIDgt -u ltcontrolusergtltpasswordgt db_offline

58 Secure Sockets Layer Protocol for Database ServerCommunication

The MaxDB database server supports the Secure Sockets Layer (SSL) protocol You can use thisprotocol to communicate between the database server and its client here the Application Server(AS) SSL guarantees encrypted data transfer between the MaxDB database server and its clientapplications In addition the server authenticates itself to the client

112148 PUBLIC 12142007


Caution

There is a performance cost for SSL since the data has to be encrpyted which requires time andprocessing power

To use SSL you need to

1 Install the SAP cryptographic library [page 113] on the client host and on the server host machines2 Generate the Personal Security Environment [page 114] (PSE) on the server (SSL Server PSE) and on the

client (SSL Client PSE)

581 Installing the SAP Cryptographic Library

The cryptographic functions required to build a database server-client connection using SecureSockets Layer (SSL) protocol are supplied by the SAP Cryptographic Library Therefore you need toinstall the SAP Cryptographic Library on the host machine of the MaxDB database server and theSAP Application Server (AS)The installation package sapcryptocar consists of the following

n SAP Cryptographic Library libsapcryptososln License ticket ticket

n Configuration tool sapgenpseexeYou use the configuration tool to generate key pairs and PSEs

Caution

The SAP Cryptographic Library is subject to German export regulations and might not be availableto some customers In addition the library might be subject to the local regulations of your countryThese regulations might further restrict import use and export or re-export of cryptographicsoftwareFor more information contact your local SAP representative

PrerequisitesDownload the appropriate SAP Cryptographic Library installation package for your operating systemfrom SAP Service Marketplace at httpservicesapcomswcenter

Procedure

1 Unpack the installation package for the SAP Cryptographic Library using sapcarexe which youcan find for example on your Installation Master DVD using the following commandcar -xvf SAPCRYPTOCAR

12142007 PUBLIC 113148


Note

The remainder of the procedure as described below does not apply to client applications such asSQL Studio which do not recognize an ldquoindependentrdquo directory In this case you must copy theSAPCRYPTO installation package to the installation directory of the application In this directoryyou need to create a directory sec into which you copy the ticket file

2 Copy the sapcrypto library to the lib subdirectory of the ldquoindependent programrdquo directoryYou can find the value of the independent program directory by entering the following commanddbmcli dbm_getpath IndepProgPath

Example

The independent program directory might be called the followingsapdbprogramslib

3 Copy the configuration tool sapgenpseexe to the directory ltindependent programgtlib4 Create a subdirectory called sec under the ldquoindependent datardquo directory and copy the ticket

file into it

Example

The result might look like the followingsapdbdatasecticket

5 Make sure that the directory and the files that the sec directory contains ‒ including the ticketfile and the SSL Server PSE ‒ belong to the user lcown and the group lcadm and that the rightsare restricted to 0600

ResultThe SAP Cryptographic Library is copied to the application server and the environment is correctlyconfigured so that the server can find the library at run time

582 Generating the Personal Security Environment

The information required by the database server or client application to communicate using SecureSockets Layer are stored in the Personal Security Environment (PSE) The required information differsaccording to whether SSL PSE is for the server or client

n SSL Server PSEThis PSE contains the security information from the database server for example thepublic-private cryptographic key pair and certificate chain To install the SSL Server PSE youneed to generate the PSE You can either do this for a single database server or system-wide TheSSL Server PSE is called SDBSSLSexe

114148 PUBLIC 12142007


n SSL Client PSEThe client requires an anonymous certificate called SDBSSLAexe which contains the list of thepublic keys of trustworthy database servers

ProcedureTo generate the SSL Server PSE proceed as follows

Note

You need to know the naming convention for the distinguished name of the database serverThe syntax of the distinguished name which you enter in the procedure below depends on theCertification Authority (CA) that you are using

1 Change to the ltindependent programsgtlib directory2 Set up the following environment variable

SECUDIR=ltindependent datagtsec

3 Create an SSL Server PSE SDBSSLSpse and generate a certificate request file certreq in thedirectory defined by SECUDIR (see previous step)sapgenpse gen_pse -v -r ltSECUDIRgtcertreq -p SDBSSLSpse ldquoltyour distinguised namegtrdquo

For each database server that uses a server-specific PSE you must set up a unique certificaterequest If you are using a valid system-wide SSL Server PSE you only need to set up a singlecertificate request for all servers

4 Send the certificate request to the CA for signing You can either send it to the SAP CA or toanother CAYou must make sure that the CA offers a certificate corresponding to the PKCS7 certificate chainformat Thawte CA at wwwthawtecom offers a suitable certificate either SSL Chained CA Certor PKCS7 certificate chain formatThe CA validates the information contained in the certificate request according to its ownguidelines and sends a reply containing the public key certificate

5 After you have received the reply from the CA make sure that the contents of the certificaterequest have not been destroyed during downloadFor example if you requested the certificate on a UNIX system and stored it on a Windows frontend the formatting (that is line indents and line breaks) is affectedTo check the contents open the certificate request with a text editor (such as Notepad) and repairthe line indents and the line breaks

12142007 PUBLIC 115148


Example

This is an example of a certificate request-----BEGIN CERTIFICATE

REQUEST-----MIIBPzCBqQIBADAAMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD302IT+Y

wpignSw7U9FWneyWz3Wil0S18aFCYkRo00wCpD8UwcaC4dds4uGT6hl2WlJ0FOtUg+EQxonZbaRrk9sTalkn1mqx3YAUegEaGdf1wvuYkb0gjMk81iMjb9BJd8srMPyoBy9jMC7v5u7+TZWmWa6RjnvClvYGgMwIDAQABoAAwDQYJKoZIhvcNAQEFBQADgYEAx2zuaTAOKPdGmxUKYlWdasUpim4vhfaHa7ZDBwipvKJ8akYCT+dpmVjhcph9E7cUjL806Rup5cnLAAO5FhVt5MS6zNJa9YYSN9XP+5MPF6Q4ayJ0VryTkSpbbPrWLbKh1Dds97LQVuQmyKIAHECwyW6t7sAFJWn4P0fdxmKo=

-----END CERTIFICATE REQUEST-----

6 Import the reply to the SSL Server PSEa) Copy the text to a temporary file called srcertb) Enter the following command

sapgenpse import_own_cert -c srcert -p SDBSSLSpse

You have generated the SSL Server PSE You can now start the XServer as usual (if it is alreadyrunning you must stop and restart it)

7 To check whether the SSL functionality is working correctly view the trace file niserver_ltlocalcomputer namegttrace in the ltindependent datagtwrk directory

To generate the SSL Client PSE proceed as follows



3 Enter ltindependent programgtlib in the environment variable LD_LIBRARY_PATH4 Create an anonymous client SSL Client PSE SDBSSLApse in the directory defined by SECUDIR (see

previous step)sapgenpse gen_pse -v -noreq -p SDBSSLApse

You can leave the distinguished name emptyBefore you can establish an SSL connection to a database server the server certificate must beentered in the PK list of the anonymous client certificate

5 To see the database server certificate enter the following commandbdquox_ping -n ltservermodegt -c[apture]

You can check whether to trust the database server certificate The client certificate is not affectedby this

6 Start the import with this commandbdquox_ping -n ltservermodegt -i[import]

7 To administer the PSE use the configuration tool sapgenpse For more information enter thefollowing commandsapgenpse -h

Note

For applications such as SQL Studio replace the independent data or independent program in theabove description with the installation directory

116148 PUBLIC 12142007

5 Post-Installation59 Backing Up the MaxDB Database

59 Backing Up the MaxDB Database

You need to define backup media and back up the MaxDB database using Database Manager GUI(DBMGUI)

Prerequisites

n You have finished client maintenance

n You have installed Database Manager GUI [page 111]n You can find more information on backing up the database in the SAP Library [page 13]

Function-Oriented View Databases MaxDB Tools Database Manager GUI Backup

Procedure

1 Define the backup medium as described inManaging the Backup Media in the above documentation2 Back up the database as described in Backing Procedures in the above documentation

510 Updating the Database Software to the Current Release

After the installation and before you start production operation we strongly recommend you toupdate the database software

Procedure

1 Download the latest MaxDB patches as followshttpservicesapcomswdc Download Database Patches MaxDB

For more information about upgrading to a MaxDB Support Package see SAP Note 735598

511 Ensuring User Security

You need to ensure the security of the users that SAPinst creates during the installation For securityreasons you also need to copy the installation directory to a separate secure location ‒ such as aDVD ‒ and then delete the installation directory

12142007 PUBLIC 117148

5 Post-Installation511 Ensuring User Security

Recommendation

In all cases the user ID and password are only encoded when transported across the networkTherefore we recommend using encryption at the network layer either by using the Secure SocketsLayer (SSL) protocol for HTTP connections or Secure Network Communications (SNC) for the SAPprotocols dialog and RFCFor more information see the SAP Library [page 13]Function-Oriented View Security Network and Transport Layer Security

Caution

Make sure that you perform this procedure before the newly installed SAP system goes intoproduction

PrerequisitesIf you change user passwords be aware that SAP system users might exist in multiple SAP systemclients (for example if a user was copied as part of the client copy) Therefore you need to change thepasswords in all the relevant SAP system clients

ProcedureFor the users listed below take the precautions described in the relevant SAP security guide whichyou can find on SAP Service Marketplace at httpservicesapcomsecurityguide

Operating System and Database Users

User Type User Comment

Operating system user sqdltdbsidgt MaxDB database administrator(that is the owner of the databasefiles)

SAPltSAPSIDgtDB MaxDB database owner (that is theowner of the database tables)

CONTROL MaxDB database manager operator

MaxDB database users

SUPERDBA MaxDB database systemadministrator

Operating system user ltsapsidgtadm SAP system administrator

118148 PUBLIC 12142007


Host Agent User

User User Name Comment

Operating system user sapadm SAP system administratorYou do not need to change thepassword of this user after theinstallationThis user is for administrationpurposes only

Note

You can set up Java standalone users with the SAP User Management Engine (UME) in one of thefollowing ways

n With the users stored in an external ABAP system ‒ see the first table below

n With the users stored in the database ‒ see the second table below

The next two tables show these ways of managing the users

SAP System Users Stored in an External ABAP System

User User Name Storage External ABAP System Comment

Administrator You create this user manually in the externalABAP system during the installation process

RecommendationWe recommend that you call the userJ2EE_ADM_ltSAPSID_Java_Systemgt

The maximum length is 12 characters

This userrsquos password is stored insecure storageTherefore whenever you change theadministratorrsquos password you mustalso change the password in securestorage with the Config Tool For more information see Checking theSAP Java Documentation [page 121]

Guest You create this user manually in the externalABAP system during the installation process

RecommendationWe recommend that you call the userJ2EE_GST_ltSAPSID_Java_Systemgt


Lock this user for interactive logon

Communicationuser for ApplicationServer Java

You create this user manually in the externalABAP system during the installation process

RecommendationWe recommend that you call the userSAPJSF_ltSAPSID_Java_Systemgt


Specify this user as a Communicationsuser and not as a dialog userThis user exists at least in the SAPsystem client that you specifiedduring the installation

12142007 PUBLIC 119148

5 Post-Installation512 Configuring User Management to Use an LDAP Directory (Optional)

SAP System Users Stored in the Database

User User Name Storage Database Comment

Administrator The name that you gave this userduring the installation or thedefault name Administrator

This userrsquos password is stored in securestorage Therefore whenever you changethe administratorrsquos password you must alsochange the password in secure storage with theAS Java Config ToolFor more information see Checking the SAP JavaDocumentation [page 121]

Guest The name that you gave this userduring the installation or thedefault name Guest


512 Configuring User Management to Use an LDAP Directory(Optional)

If your user data source is an LDAP directory you need to configure the connection to the LDAPdirectory after installationFor more information see the SAP Library [page 13]Function-Oriented View Security Identity Management Identity Management of the Application Server Java

Configuring Identity Management UME Data Sources LDAP Directory as Data Source Configuring the UMEto Use an LDAP Server as Data Source

513 Post-Installation Steps for the Host Agent

You have to perform the following steps on each host where the host agent is installed This applieswhether the host agent is installed on a host within the SAP system or standalone on another host

Procedure

1 You check whether the installed services are available as followsa) Log on as user sapadmb) Check whether the following services are availablen The control program saphostexec

n The operating system collector saposcoln The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)

120148 PUBLIC 12142007

5 Post-Installation514 Checking the SAP Java Documentation

Note

When the host is booted the startup script sapinit automatically starts the requiredexecutables

2 You configure the host agent according to your requirements

More InformationFor more information see the SAP Library [page 13]Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Monitoring in the

CCMS Infrastructure of the SAP NetWeaver Management Agents

514 Checking the SAP Java Documentation

Here you can find information in the SAP Library about the configuration of Application ServerJava (AS Java) and about SAP Java technology

Procedure

1 Go to the following place in the SAP library [page 13]Function-Oriented View Application Server Java AS Java (Application Server Java)

2 Check the following documentation for information relevant to running your Java system

Manual Contents

Application Server InfrastructureArchitecture of the SAP NetWeaver

Application Server Architecture ofAS Java

This documentation provides an overview of the architecture of theApplication Server Java (AS Java) It contains information onn Java cluster architecturen Application Server Java (AS Java) system architecturen Zero Administration (technical configuration within AS Java)

Application Server JavaAdministration

This documentation describes how to administer the SAP systemfocusing on AS Java It contains information onn Administration Toolsl SAP Management Console

The SAP Management Console (SAP MC) provides a commonframework for centralized system management It allows youto monitor and perform basic administration tasks on the SAPsystem centrally thus simplifying system administration

l SAP NetWeaver AdministratorSAP NetWeaver Administrator is a Web-based tool foradministration and monitoring that offers a single entry point toconfigure administer and monitor your SAP NetWeaver systemits components and the applications running on top of it

l Config ToolThe Config Tool provides offline configuration of the SAPNetWeaver Application Server Java (AS Java) instances It

12142007 PUBLIC 121148

5 Post-Installation515 Configuring the Adaptive Computing Controller

Manual Contents

allows you to modify the properties of all services managersand applications In addition it enables you to manage logconfigurations offline add filters and edit the JVM parameters

l Administration Using Telnetn SAP Java Virtual Machine (SAP JVM)n The Startup Framework for AS Javan Administration Functions for Information Lifecycle Management

Application Server Java IdentityManagement of the Application ServerJava

Identity Management of the SAP NetWeaver Application Server (AS) Javaenables you to manage users and roles for access to applications of the ASJava and the data which the applications require The user managementengine (UME) provides identity management as a service of the AS JavaThis documentation contains information onn User Management Enginen Authorization Concept of the AS Javan Configuring Identity Managementn Administration of Users and Roles

SAP High Availability This documentation contains information onn Cluster and Load Balancing (AS-Java)n Single points of failure for SAP NetWeaver AS Java

Security System Security This documentation contains information on additional system securityfunctions for AS Java

515 Configuring the Adaptive Computing Controller

You use the SAP NetWeaver Administrator and ACC application to perform the various configurationactivities related to adaptive computing The configuration consists of two phases

n Initial Configuration of ACC in NWAThe NWA Configuration Wizard is used for the initial configuration of ACC component

n Configuration of Adaptive Data in ACCThe ACC application is used to configure application services resources networks and adaptivepools

ProcedureTo configure the ACC perform the procedure described in the SAP Library [page 13]Function-Oriented View Application Server Infrastructure Adaptive Computing Adaptive Computing Controller

(ACC) Configuring ACC

More InformationYou can find detailed information about operating the ACC in theSAP Library [page 13]Function-Oriented View Application Server Infrastructure Adaptive Computing

122148 PUBLIC 12142007

5 Post-Installation516 Performing a Full Installation Backup

516 Performing a Full Installation Backup

You must perform a full offline backup after the configuration of your SAP system If requiredyou can also perform a full offline backup after the installation (recommended) In addition werecommend you to regularly back up your database

Caution

Make sure that you fully back up your database so that you can recover it later if necessary

You need to back up the following directories and files

n All SAP-specific directories

l usrsapltSAPSIDgt

l ltsapmntgtltSAPSIDgt

l Home directory of the user ltsapsidgtadmn All database-specific directoriesn The root file system

This saves the structure of the system and all configuration files such as file system size logicalvolume manager configuration and database configuration data

Note

This list is only valid for a standard installation

Prerequisites

n You have logged on [page 106] as user ltsapsidgtadm and stopped the SAP system and database [page 134]

Use the backup tool of your choice for example the HP DataProtector and refer to the backupsoftware documentation You can also use the standard UNIX tools as described below

Backing Up the Installation

1 Log on as user root2 Manually create a compressed tar archive that contains all installed filesn Saving to tape

tar mdashcf mdash ltfile_systemgt | compress mdashc gt lttape_devicegt

n Saving to the file systemtar mdashcf mdash ltfile_systemgt | compress mdashc gt ARCHIVENAMEtarZ

Restoring Your BackupIf required you can restore the data that you previously backed up

12142007 PUBLIC 123148


Caution

Check for modifications in the existing parameter files before you overwrite them when restoringthe backup

1 Log on as user root2 Go to the location in your file system where you want to restore the backup image3 Execute the following commands ton restore the data from tape

cat lttape_devicegt | compress mdashcd | tar mdashxf mdash

n restore the data from the file systemcat ARCHIVENAMEtarZ | compress mdashcd | tar mdashxf mdash

124148 PUBLIC 12142007

6 Additional Information


Here you find additional information about the installation of your SAP systemThere is also information about how to delete an SAP system

n Mounting a CD DVD for HP-UX [page 125]n Additional Information about SAPinst [page 127]n Starting and Stopping the SAP System [page 134]

n


High-Availability Finalizing the enqueue replication server for high availability [page 141]You have to perform this procedure only if you have installed the enqueue replication server(ERS) into an existing systemEnd of HA (UNIX)

n Deleting an SAP System [page 142]

61 Mounting a CD DVD for HP-UX

Proceed as follows to mount a CD or DVD

Note

The placeholder ltmedium-mountdirgt is used for either ltcd-mountdirgt or ltdvd-mountdirgt

Mounting a CD DVD Manually

1 Log on as user root2 To create a mount point for CD DVD enter the following command

mkdir ltmedium-mountdirgt

Example

ltmedium-mountdirgt is sapcd

3 To find out the hardware address of the CDDVD drive proceed as followsa) Enter the following command

ioscan -fnkCdisk

A list of all devices is displayedb) Note the hardware address of the CDDVD drive for example c0t4d0

12142007 PUBLIC 125148

6 Additional Information61 Mounting a CD DVD for HP-UX

4 To check that the driver is part of the kernel (skip this step if the CD DVD drive is alreadyworking) enter the following commandgrep cdfs standsystem

If the driver is not configured you have to add the string cdfs to the file standsystem andrebuild the kernel For more information about how to build a new kernel see Checking andModifying the HP-UX Kernel [page 56] After rebuilding the kernel reboot the system

5 To mount the CD DVD on HP-UX 1111 or 1123 enter the following commandmount -r -F cdfs -o rr devdskltdiskdevicegt ltmedium-mountdirgt

To mount the CD DVD on HP-UX 1131 enter the following commandmount -r -F cdfs -o rr devdiskltdiskdevicegt ltmedium-mountdirgt

Example

HP-UX 1111 or 1123 mount -r -F cdfs -o rr devdskc0t4d0 sapcd

HP-UX 1131 mount -r -F cdfs -o rr devdiskc0t4d0 sapcd

Mounting a CD DVD Using SAM for HP-UX 1111 or HP‒UX 1123

1 Enter the commandusrsbinsam

2 Choose Disks and Filesystems Disk Devices Actions Mount3 Enter the mount directory

ltmedium-mountdirgt

Example

For example ltmedium-mountdirgt is sapcd

4 Perform task5 Exit SAM

Mounting a CD DVD Using SMH for HP-UX 1131


n usrsbinsmh


where ltportgt is either the default port 2381 or your defined port (for example 2301)2 Choose Disks and Filesystems File Systems Add CDFS3 Enter the mount directory

ltmedium-mountdirgt

Example


126148 PUBLIC 12142007

6 Additional Information62 Additional Information About SAPinst

4 Choose the hardware path5 Choose New CDFS6 Exit SMH

62 Additional Information About SAPinst

The following sections provide additional information about SAPinst [page 95]


621 Interrupted Installation with SAPinst

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

n An error occurred during the dialog or processing phaseSAPinst does not abort the installation in error situations If an error occurs the installation pausesand a dialog box appears The dialog box contains a short description about the choices listed inthe table below as well as a path to a log file that contains detailed information about the error

n You interrupted the installation by choosing Exit in the SAPinst menu

The following table describes the options in the dialog box

Option Definition

Retry SAPinst retries the installation from the point of failure without repeatingany of the previous stepsThis is possible because SAPinst records the installation progress in thekeydbxml fileWe recommend that you view the entries in the log files try to solve theproblem and then choose RetryIf the same or a different error occurs again SAPinst displays the samedialog box again

Stop SAPinst stops the installation closing the dialog box the SAPinst GUI andthe GUI serverSAPinst records the installation progress in the keydbxml file Thereforeyou can continue the installation from the point of failure withoutrepeating any of the previous steps See the procedure below

Continue SAPinst continues the installation from the current point

12142007 PUBLIC 127148


Note

You can also terminate SAPinst by choosing Ctrl + C However we do not recommend that youuse Ctrl + C because this kills the process immediately

ProcedureThis procedure describes the steps to restart an installation which you stopped by choosing Stop orto continue an interrupted installation after an error situation

1 Log on to your local UNIX host as user root

Caution


2 Mount your Installation Master DVD

Note

Mount the DVD locally We do not recommend using Network File System (NFS)

3 Enter the following commandscd ltmountpoint_of_Installation Master_DVDgtDATA_UNITSIM_ltOSgt_ltDBgt

sapinst

Example

For example if the mountpoint of the Installation Master DVD is sapcd2 the operating system isLINUX_X86_64 and the database is Oracle the commands are as followscd sapcd2DATA_UNITSIM_LINUX_X86_64_ORA

sapinst

4 From the tree structure in theWelcome screen select the installation option that you want tocontinue and choose Next

Note

If there is only one component to install theWelcome screen does not appear

TheWhat do you want to do screen appears5 In theWhat do you want to do screen decide between the following alternatives and confirm with OK

128148 PUBLIC 12142007


Alternative Behavior

Run a new Installation SAPinst does not continue the interrupted installation Instead it movesthe content of the old installation directory and all installation-specificfiles to the backup directory Afterwards you can no longer continuethe old installationFor the backup directory the following naming convention is usedltlog_day_month_year_hours_minutes_secondsgt (for examplelog_01_Oct_2003_13_47_56)

Continue old installation SAPinst continues the interrupted installation from the point of failure

622 Performing a Remote Installation with SAPinst(Optional)

You use this procedure to install your SAP system on a remote host In this case SAPinst and theGUI server run on the remote host and SAPinst GUI runs on the local host The local host is thehost from which you control the installation with SAPinst GUI

Prerequisites

n The remote host meets the prerequisites before starting SAPinst [page 95]n Both computers are in the same network and can ldquopingrdquo each other

To test thisl Log on to your remote host and enter the command ping ltlocal hostgtl Log on to the local host and enter the command ping ltremote hostgt

Procedure

1 Log on to your remote host as user root

Caution


2 Mount the Installation Master DVD3 Enter the following commands

cd ltmountpoint_of_Installation_Master_DVDgtIM_ltOSgt_ltDBgt

sapinst -nogui

12142007 PUBLIC 129148


Example


sapinst -nogui

For more information see Running SAPinst [page 95]SAPinst now starts and waits for the connection to the SAPinst GUI You see the following atthe command promptguiengine no GUI connected waiting for a connection on host lthost_namegt port

ltport_numbergt to continue with the installation

4 Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 130]5 Log on to your remote host as user root

Caution



cd ltInstallation_Master_DVDgtIM_ltOSgt

sapinst -nogui



8 Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 130]

623 Starting SAPinst GUI Separately (Optional)

You use this procedure to start SAPinst GUI separately You might need to start SAPinst GUIseparately in the following cases

n You have logged off from SAPinstIf you logged off during the installation and you later want to reconnect to the installation while itis still running you can start SAPinst GUI separately

n You want to perform a remote installation [page 129]If SAPinst GUI runs on a different host from SAPinst and the GUI server you have to start SAPinstGUI separately

130148 PUBLIC 12142007


Starting SAPinst GUI on a Windows Platform

1 Log on as a member of the local administrators group2 Insert the SAP Installation Master DVD into your DVD drive3 Change to the directory of the sapinst executables

ltDVD drivegtDATA_UNITSIM_WINDOWS_ltplatformgt_ltDBgt

Note

If you want to start SAPinst GUI on a Windows 32-bit platform change to the following directoryltInstallation_Master_DVDgtDATA_UNITSSAPINSTGUI_710_WINDOWS_I386

4 Start SAPinst GUI by double-clicking sapinstguiexeSAPinst GUI starts and tries to connect to the GUI server and SAPinst using the local hostas defaultIf SAPinst and the GUI server are running on another host SAPinst GUI cannot connect and theSAP Installation GUI Connection dialog appearsIn this case enter the name of the host on which SAPinst is running and choose Log onThe first dialog of the installation appears and you can perform the remote installation fromyour local host

Note

Optionally you can start sapinstguiexe with the following parametersn host=lthost namegt where lthost namegt is the host name of the installation host

n port=ltnrgt where ltnrgt is the port number for the connection to the GUI server

n -accessible enables the Accessibility modeExamplesapinstguiexe host=lsi1209 port=3000 -accessible

Starting SAPinst GUI on a UNIX Platform

1 Log on as user root

Caution



Note

Mount the DVD locally We do not recommend that you use Network File System (NFS)

3 Change to the directory of the sapinst executables

12142007 PUBLIC 131148


ltmountpoint_of_Installation_Master_DVDgtDATA_UNITSIM_ltOSgt_ltDBgt

Note

If you want to start SAPinst GUI on a Linux 32‒bit platform change to the following directoryltmountpoint_of_Installation_Master_DVDgtDATA_UNITSSAPINSTGUI_710_LINUX_I386

4 Start SAPinst GUI by executing sapinstguiSAPinst GUI starts and tries to connect to the GUI server and SAPinst using the local hostas defaultIf SAPinst and the GUI server are running on another host SAPinst GUI cannot connect and theSAP Installation GUI Connection dialog appearsIn this case enter the name of the host on which SAPinst is running and choose Log onThe first dialog of the installation appears and you can perform the remote installation fromyour local host

Note

Optionally you can start sapinstgui with the following parametersn host=lthost namegt where lthost namegt is the host name of the installation host


n - accessible enables accessibility modeExamplesapinstgui host=lsi1209 port=3000 -accessible

624 Entries in the Services File Created by SAPinst

After the installation has finished successfully SAPinst has created the following entries inetcservicessapdpXX = 32XXtcp

sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp

where XX is set from 00 to 99

Note

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

132148 PUBLIC 12142007

6 Additional Information63 Heterogeneous SAP System Installation

625 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinstIf an error occurs SAPinst

n Stops the installationn Displays a dialog informing you about the error

Procedure

1 To view the log file choose View Logs2 If an error occurs during the dialog or processing phase do one of the followingn Try to solve the problemn Abort the installation with Exit

For more information see Interrupted Installation with SAPinst [page 127]n Continue the installation by choosing Retry

3 Check the log and trace files of the GUI server and SAPinst GUI in the directoryltuser_homegtsdtgui for errors

4 If GUI server or SAPinst GUI does not start check the file sdtstarterr in the currentltuser_homegt directory

5 If SAPinst GUI aborts during the installation without an error message restart SAPinst GUI asdescribed in Starting SAPinst GUI Separately

63 Heterogeneous SAP System Installation

This section provides information on how to install an SAP system in a heterogeneous systemlandscape ldquoHeterogeneous system landscaperdquo means that application servers run on differentoperating systems and or database systems

Note

See SAP Note 1067221 for information on

n supported combinations of operating systems and database systems

n installing an application server on Windows in a heterogeneous (UNIX) SAP system environment(ABAP Java or ABAP+Java) with SAPinst

n Java EE engine installation on heterogeneous architectures

n heterogeneous Unix - Unix Systems

The following procedure describes how to install SAP instances in a heterogeneous UNIXenvironment which is where you run instances on different UNIX platforms

12142007 PUBLIC 133148

6 Additional Information64 Starting and Stopping the SAP System

Procedure

1 Install the central services instance the primary application server instance and the database asdescribed in this installation guide

2 Log on as user root on the additional application server instance host3 On the SAP Global host (High Availability Switchover Cluster Infrastructure) export the

following directories

n ltsapmntgtltSAPSIDgtexe

n ltsapmntgtltSAPSIDgtglobal

n ltsapmntgtltSAPSIDgtprofile

4 Mount the directories listed in the previous step on each additional application server instancehost as described in Preparing the installation DVDs [page 87]

5 Mount the CD or DVD drive using NFS and insert the CD DVD with the SAP executables onthe additional application server instance host

6 Install the additional application server instance as described in this installation guide

64 Starting and Stopping the SAP System

You want to check that you can start and stop your SAP system using one of the following

n The SAP Management Console (SAP MC) [page 134]n The startsap and stopsap scripts [page 137]

641 Starting and Stopping the SAP System Using the SAPManagement Console

You can start and stop all instances of your SAP system using the SAPManagement Console (SAPMC)

Note

If your newly installed SAP system is part of a heterogeneous SAP system landscape that comprisessystems or instances on Windows platforms you can also start and stop it from a Windows systemor instance using the Microsoft Management Console (MMC)For more information about handling the MMC see the SAP Library [page 13]Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Monitoring in the

CCMS SAP Microsoft Management Console Windows

Prerequisites

n Make sure that the host on which you start SAP MCmeets the following requirementsl Java Runtime Environment (JRE) 50 is installedl The browser supports Java

134148 PUBLIC 12142007


l The browserrsquos Java plug-in is installed and activatedn You have logged on to the host as user ltsapsidgtadm

Starting the Web-Based SAP Management Console

1 Start a Web browser and enter the following URLhttplthostnamegt5ltinstance_numbergt13

Example

If the instance number is 53and the host name is saphost06 you enter the following URLhttpsaphost0655313

This starts the SAP MC Java applet

Note

If your browser displays a security warning message choose the option that indicates that youtrust the applet

2 Choose StartThe SAP Management Console appearsBy default the instances installed on the host you have connected to are already added in the SAPManagement Console If you want to change the configuration to display systems and instanceson other hosts see Registering Systems and Instances below

Starting and Stopping Systems and Instances

Starting an SAP System or Instance

1 In the navigation pane open the tree structure and navigate to the system node that you want tostart

2 Select the system or instance and then from the context menu choose Start3 In the Start SAP System(s) dialog box choose the required options4 Choose OK The SAP MC starts the specified system or system instances

Note

The system may prompt you for the SAP system administrator credentials To complete theoperation you must have administration permissions Log in as user ltsapsidgtadm

Starting Instances Separately

If you need to start the instances of an SAP system separately for example when you want to start adistributed or a high-availability system proceed in the following sequence

1 Start the database instance

12142007 PUBLIC 135148


2 Start the central services instance SCSltInstance_Numbergt3 Start application server instance(s) JltInstance_Numbergt

Stopping an SAP System or Instance

1 Select the system or instance you want to stop and choose Stop from the context menu2 In the Stop SAP System(s) dialog box choose the required options3 Choose OK The SAP MC stops the specified system or system instances

Note


Similarly you can start stop or restart all SAP systems and individual instances registered in theSAP MC

Stopping Instances Separately

If you need to stop the instances of an SAP system separately for example when you want to start adistributed or a high-availability system proceed in the following sequence

1 Stop application server instance(s) JltInstance_Numbergt2 Stop the central services instance SCSltInstance_Numbergt3 Stop the database instance

Registering Systems and Instances in the SAP Management ConsoleYou can extend the list of systems and instances displayed in the SAPMC so that you canmonitor andadminister all systems and instances from a single console You can configure the SAP MC startupview to display the set of systems and instances you want to manage

Prerequisites

The SAP MC is started

Registering SAP Systems

1 In the SAP MC choose File New 2 In the New System dialog box enter the required data

Note

If you have already registered systems in the SAP MC they are stored in the history To open theSystemrsquos History dialog box choose the browsing button next to the Instance Nr field Select aninstance of the system that you want to add and choose OK

3 Choose Finish

136148 PUBLIC 12142007


Registering Individual Instances

1 In the SAP MC choose File New 2 In the New System dialog box enter the required data and deselect Always show all SAP Instances3 The SAP MC displays the SAP system node the instance node and the relevant database node in

a tree view in the navigation pane

Note

To view all instances of the respective SAP system select the relevant system node and chooseAdd Application Server from the context menu

Configuring the SAP MC View

n You can choose the instances that the SAP MC displays automatically on startup1 In the Settings dialog box select History2 In the right-hand side pane choose the instance you want the SAP MC to display on startup3 Choose the ltlt button4 Choose Apply and then choose OKSimilarly you can remove instances from the startup configuration

n You can save the current configuration in a file1 Choose File Save Landscape 2 In the Save dialog box enter the required data3 Choose Save

n You can load a configuration from a file1 Choose File Load Landscape 2 In the Open dialog box select the configuration you want to load3 Choose Open

More InformationFor more information about how to handle the SAP MC see the SAP Library [page 13]Administratorrsquos Guide Technical Operations for SAP NetWeaver Administration of SAP NetWeaver Systems AS


642 Starting and Stopping the SAP System Using Scripts

You can start and stop the SAP system by running the startsap and stopsap scripts

12142007 PUBLIC 137148


Prerequisites

n You have checked the default profile ltsapmntgtltSAPSIDgtprofileDEFAULTPFL for parameterloginsystem client and set the value to the correct productive system client For example theentry must be loginsystem_client = 001 if your productive client is 001

n You have logged on to the SAP system hosts as user ltsapsidgtadmn 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 manufacturern 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 startsap or stopsap in the home directory of thecorresponding user

Caution

If there aremultiple SAP instances on one host ‒ for example a primary application serverinstance and an additional application server instance ‒ you must add an extra parameter tothe scriptsstartsap ltinstanceIDgt

stopsap ltinstanceIDgt

For example enterstartsap J00

Note

The instancename (instance ID) of the primary application server instance is JltInstance_Numbergtthe instance name of the central services instance is SCSltInstance_Numbergt and the instancename of a Java additional application server instance is JltInstance_Numbergt

n


In a high-availability system you must use the failover cluster software of your hardware vendorto start or stop all instances that are running on the switchover clusterYou can only use startsap and stopsap scripts for instances that are not running on theswitchover clusterEnd of HA (UNIX)

Procedure

Starting the SAP system

n To start all instances on the standard system host enter the following commandstartsap

This checks if the database is already running If not it starts the database first

138148 PUBLIC 12142007


Note

You can start the database and SAP system separately by entering the following commandsstartsap DB

startsap R3 ltinstance ID of central services instancegt

startsap R3 ltinstance ID of primary application server instancegt

startsap R3 ltinstance ID of additional application server instancegt

Make sure that you always start the database first because otherwise the other instances cannotstart

Note

You can also use the parameter J2EE which is a synonym for the parameter R3For ABAP+Java systems you can enter either the command startsap R3 or startsap J2EE tostart the SAP instance comprising both ABAP and Java

n In a distributed system proceed as follows1 On the host running the database instance enter

startdb

2 On the host running the central services instance enterstartsap

3 On the host running the primary application server instance enterstartsap

4 For additional application server instance(s) enter the following on the relevant hoststartsap R3 ltinstance ID of additional application server instancegt

Note

Make sure that the SAP system is up and running before you start or restart additional applicationserver instances

n In a high-availability system proceed as follows

Note

In the following example only the central services instance is running on the switchover cluster

1 On the database host enterstartdb

2 On the switchover cluster infrastructure use the failover cluster software to start the centralservices instance

3 On the host of the primary application server instance enterstartsap


12142007 PUBLIC 139148


Note


n For an additional application server instance enter the following on the relevant hoststartsap R3 ltinstance ID of additional application server instancegt

Note


Stopping the SAP System

n If you have a standard system enter the following to stop all instances on the standard systemhoststopsap

This stops the primary application server instance central services instance and database

Note

You can stop the database and SAP system separately by entering the following commandsstopsap R3 ltinstance ID of additional application server instancegt

stopsap R3 ltinstance ID of primary application server instancegt

stopsap R3 ltinstance ID of central services instancegt

stopsap DB

Make sure that you always stop the primary application server instance first and the centralservices instance second because otherwise the database cannot be stopped

Note

You can also use the parameter J2EE which is a synonym for the parameter R3For ABAP+Java systems you can enter either the command stopsap R3 or stopsap J2EE to stopthe SAP instance comprising both ABAP and Java

n In a distributed system proceed as follows1 On the host(s) running the additional application server instance(s) enter the following

commandstopsap ltinstance ID of additional application server instancegt

2 On the host running the primary application server instance enterstopsap

3 On the host running the central services instance enterstopsap

4 On the host running the database instance enter

140148 PUBLIC 12142007

6 Additional Information65 High Availability Finalizing the Enqueue Replication Server

stopdb

n In a high‒availability system proceed as follows

Note


1 On the host(s) running the additional application server instance(s) enter the followingcommandstopsap ltinstance ID of additional application server instancegt



4 On the host running the database instance enterstopdb

n For an additional application server instance enter the following on the relevant hoststopsap R3 ltinstance ID of additional application server instancegt

Note


Caution

Make sure that no SAP instance is running before you enter stopdb on a standalone database serverNo automatic check is made


65 High Availability Finalizing the Enqueue ReplicationServer

You have to perform this procedure only if you have installed the enqueue replication server (ERS)into an existing system This is necessary to ensure correct functioning of the ERS which depends onthe switchover software you are using

Procedure

1 Restart the central services instance associated with the ERSThis requires you to restart the primary application server and additional application serverinstance

12142007 PUBLIC 141148

6 Additional Information66 Deleting an SAP System

2 Contact your hardware partner to configure and test the ERS

More InformationSee the SAP Library [page 13] Function-Oriented Overview Application Server Infrastructure Standalone EnqueueServer Installing the Standalone Enqueue ServerEnd of HA (UNIX)

66 Deleting an SAP System

This section describes how to delete a single instance a standalone engine or a complete SAP systemwith the Uninstall option of SAPinst

Caution

n You cannot delete an SAP system remotely

n If you delete network-wide users groups or service entries in an environment with NetworkInformation System (NIS) other SAP installations might also be affected Make sure that theusers groups and service entries to be deleted are no longer required

Prerequisites

n This description assumes that you have installed your SAP system with standard SAP toolsaccording to the installation documentation

n You are logged on as user rootn If the saposcol process on the host where you are working has been started from the SAP system

that you want to delete stop the process using the command saposcol -kIf there are other SAP systems on the host log on as user ltsapsidgtadm of the other SAP system andstart saposcol from there using the command saposcol -l

Procedure

1 Start SAPinst [page 95] and on theWelcome screen chooseNetWeaver Process Integration 71 Software Life-Cycle Options Uninstall Uninstall ‒ SAP systems or single

instances 2 Follow the instructions in the SAPinst input dialogs

Note

For more information about the input parameters place the cursor on the relevant field andpress F1 in SAPinst

142148 PUBLIC 12142007


SAPinst first asks you which SAP instances you want to delete Make sure that you delete the SAPinstances in the order as described hereinaftern If you want to delete a standard system (all instances reside on the same host) you can do this

in one SAPinst runn If you want to delete a distributed system you have to run SAPinst to delete the required

instances locally on each of the hosts belonging to the SAP system in the following sequencea) Additional application server instance(s) if there are anyb) Database instance

Caution

SAPinst only stops local instances automatically Before you delete the database instanceof a distributed system make sure that you stop all remaining instances You must stopthe instance with the message server only after having entered all SAPinst parametersfor the deletion of the database instance

Choose whether you want to drop the entire database or only one or more databaseschemas If you drop the entire database SAPinst also asks whether you want to remove thedatabase software

c) Primary application server instanced) Central services instance

Note

To delete system directories mounted from an NFS server make sure that you run SAPinston the NFS server

3 If required you can delete the directory usrsaptrans and its content manuallySAPinst does not delete usrsaptrans because it might be shared

12142007 PUBLIC 143148

Typographic Conventions

Example Description

lt gt Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

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 thedocumentation

Example Textual cross-references to an internet address for example httpwwwsapcom

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

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example n Words or characters quoted from the screen These include field labels screen titlespushbutton labels menu names and menu options

n Cross-references to other documentation or published works

Example n Output on the screen following a user action for example messagesn Source code or syntax quoted directly from a programn 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 namestransaction codes database table names and key concepts of a programming languagewhen they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

144148 PUBLIC 12142007

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2007 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors

Microsoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeriesxSeries zSeries System i System i5 System p System p5 System x System z System z9 zOS AFP Intelligent MinerWebSphere Netfinity Tivoli Informix i5OS POWER POWER5 POWER5+ OpenPower and PowerPC are trademarks orregistered trademarks of IBM CorporationAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registeredtrademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web ConsortiumMassachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implementedby NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world All other product and service names mentioned are the trademarks of their respective companies Datacontained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall notbe liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services if any Nothing hereinshould be construed as constituting an additional warranty

This document was created using stylesheet 2006-12-31 (V51beta [= 60 for E3]) and XSLT processor SAXON 652 fromMichael Kay (httpsaxonsfnet) XSLT version 1

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressively prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified oraltered in any way

12142007 PUBLIC 145148

Legal Software Terms

Terms for Included Open Source SoftwareThis SAP software contains also the third party open source software products listed below Note that for these third partyproducts the following special terms and conditions shall apply

1 This software was developed using ANTLR

2 SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems Applications Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf Germany(hereinafter SAP)andyou(hereinafter Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive non-transferable royalty-free license to use the STLportorg C++ library(STLport) and its documentation without fee

B) By downloading using or copying STLport or any portion thereof Customer agrees to abide by the intellectualproperty laws and to all of the terms and conditions of this Agreement

C) The Customer may distribute binaries compiled with STLport (whether original or modified) without anyroyalties or restrictions

D) Customer shall maintain the following copyright and permissions notices on STLport sources and itsdocumentation unchanged Copyright 2001 SAP AG

E) The Customer may distribute original or modified STLport sources provided thatn The conditions indicated in the above permissions notice are metn The following copyright notices are retained when present and conditions provided in accompanying

permission notices are metCopyright 1994 Hewlett-Packard CompanyCopyright 199697 Silicon Graphics Computer Systems IncCopyright 1997 Moscow Center for SPARC TechnologyCopyright 19992000 Boris FomitchevCopyright 2001 SAP AG

Permission to use copy modify distribute and sell this software and its documentation for any purposes ishereby granted without fee provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation Hewlett-Packard Companymakes no representations about the suitability of this software for any purpose It is provided ldquoas isrdquo withoutexpress or implied warrantyPermission to use copy modify distribute and sell this software and its documentation for any purpose ishereby granted without fee provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation Silicon Graphics makes norepresentations about the suitability of this software for any purpose It is provided ldquoas isrdquo without express orimplied warrantyPermission to use copy modify distribute and sell this software and its documentation for any purposes ishereby granted without fee provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation Moscow Center for SPARC

146148 PUBLIC 12142007

makes no representations about the suitability of this software for any purpose It is provided ldquoas isrdquo withoutexpress or implied warrantyBoris Fomitchev makes no representations about the suitability of this software for any purpose This material isprovided as is with absolutely no warranty expressed or implied Any use is at your own risk Permission to useor copy this software for any purpose is hereby granted without fee provided the above notices are retained on allcopies Permission to modify the code and to distribute modified code is granted provided the above notices areretained and a notice that the code was modified is included with the above copyright noticePermission to use copy modify distribute and sell this software and its documentation for any purposes ishereby granted without fee provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation SAP makes no representationsabout the suitability of this software for any purpose It is provided with a limited warranty and liability as setforth in the License Agreement distributed with this copy SAP offers this liability and warranty obligations onlytowards its customers and only referring to its modifications

b) Support and MaintenanceSAP does not provide software maintenance for the STLport Software maintenance of the STLport thereforeshall be not includedAll other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditionsand shall be subject to a separate contract

c) Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge SAP cannot guarantee that theSTLport is error-free without material defects or suitable for a specific application under third-party rightsTechnical data sales brochures advertising text and quality descriptions produced by SAP do not indicate anyassurance of particular attributes

d) Limited Liability

A) Irrespective of the legal reasons SAP shall only be liable for damage including unauthorized operation if this (i)can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or(iii) if based on the failure of a guaranteed attribute

B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerialemployees of SAP the total liability for such damage and a maximum limit on the scope of any such damage shalldepend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contractdue to the circumstances known to it at that point in time representing a typical transfer of the software

C) In the case of Art 42 above SAP shall not be liable for indirect damage consequential damage caused by adefect or lost profit

D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceedEUR 5000

E) The Customer shall take adequate measures for the protection of data and programs in particular by makingbackup copies at the minimum intervals recommended by SAP SAP shall not be liable for the loss of data andits recovery notwithstanding the other limitations of the present Art 4 if this loss could have been avoided byobserving this obligation

F) The exclusion or the limitation of claims in accordance with the present Art 4 includes claims against employeesor agents of SAP

3 Adobe Document ServicesAdobe the Adobe logo Acrobat PostScript and Reader are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States and or other countries For information on Third Party software delivered withAdobe document services and Adobe LiveCycle Designer see SAP Note 854621

Documentation in the SAP Service MarketplaceYou can find this document at the following address httpsservicesapcominstguides

12142007 PUBLIC 147148

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2007 SAP AG All rights reservedNo 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 bechanged without prior notice

Document History

Caution

Before you start the implementation make sure you have the latest version of this document Youcan find the latest version at the following locationhttpservicesapcominstguides

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

Version Date Description

10 12142007 Initial Version

2148 PUBLIC 12142007

Table of Contents




12142007 PUBLIC 3148




4148 PUBLIC 12142007



12142007 PUBLIC 5148

6148 PUBLIC 12142007

1 Introduction

1 Introduction


Constraints








12142007 PUBLIC 7148


n





12 New Features


Caution



Area Description







8148 PUBLIC 12142007


Area Description
















12142007 PUBLIC 9148


Operating Systems

Area Description



Documentation

Area Description
















10148 PUBLIC 12142007








Documentation














12142007 PUBLIC 11148









General Quick Links
























12148 PUBLIC 12142007












Terminology


Variables











12142007 PUBLIC 13148






Example


14148 PUBLIC 12142007

2 Planning

2 Planning








4











12142007 PUBLIC 15148


n





211 Standard System







16148 PUBLIC 12142007



Note









12142007 PUBLIC 17148




End of HA (UNIX)






18148 PUBLIC 12142007











12142007 PUBLIC 19148









20148 PUBLIC 12142007







12142007 PUBLIC 21148


Figure 7 Host Agent




Note


More Information





22148 PUBLIC 12142007






12142007 PUBLIC 23148






usrsap

ltDRIVEgtsapdb









24148 PUBLIC 12142007



Security Issues


Caution


Recommendation



Caution







Performance Issues




12142007 PUBLIC 25148






Figure 9




26148 PUBLIC 12142007






Note





12142007 PUBLIC 27148


Caution









SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

28148 PUBLIC 12142007







SAP MMC


SAP MC


12142007 PUBLIC 29148










Note







30148 PUBLIC 12142007





Recommendation







12142007 PUBLIC 31148







Note



32148 PUBLIC 12142007




12142007 PUBLIC 33148


3 Preparation

3 Preparation




Note







7



8




12142007 PUBLIC 35148

3 Preparation



















36148 PUBLIC 12142007












USR VAR




12142007 PUBLIC 37148






UID USR VAR











38148 PUBLIC 12142007










Master Password




12142007 PUBLIC 39148















40148 PUBLIC 12142007



















12142007 PUBLIC 41148





Host Agent












volumes

42148 PUBLIC 12142007










Note






Recommendation




12142007 PUBLIC 43148










Process Flow


Caution



Note




44148 PUBLIC 12142007






Recommendation


Note


Prerequisites


Procedure



Note





12142007 PUBLIC 45148













|grep Total







46148 PUBLIC 12142007
















See SAP Note 837670



libldapssl41so



Other Requirements






12142007 PUBLIC 47148










Minimum RAM 2 GB












Note


48148 PUBLIC 12142007









Minimum RAM 1 GB














12142007 PUBLIC 49148







RAM 1 GB

















50148 PUBLIC 12142007



Minimum RAM 1 GB




















Minimum RAM 1 GB


12142007 PUBLIC 51148









Note







Minimum RAM 1 GB






End of HA (UNIX)

52148 PUBLIC 12142007













RAM 1 GB










12142007 PUBLIC 53148









Minimum RAM 1 GB












54148 PUBLIC 12142007







Minimum RAM 1 GB














Minimum RAM 05 GB


12142007 PUBLIC 55148








Caution



Caution










56148 PUBLIC 12142007




n kcweb(1M)

n kcusage(1M)

n kcalarm(1M)






as often




n usrsbinsmh



12142007 PUBLIC 57148






Recommendation






Total



Example

usrsbinswapinfo -dm

Mb Mb Mb PCT Mb


dev 10000 82 9918 1 0 - 1 devvg00lvol2

dev 20000 83 19917 0 0 - 1 devvg01lvol9





58148 PUBLIC 12142007














Note



Note




cd ltINSTDIRgt



12142007 PUBLIC 59148







Procedure



Note





60148 PUBLIC 12142007


Recommendation


Caution







Caution


Caution


Caution



User Primary Group


sqdltdbsidgt sapsys

sdb sdba

12142007 PUBLIC 61148



User Primary Group


Caution


Caution


Groups and Members

Groups Members




User Primary Group




Note







62148 PUBLIC 12142007


usrsbinsam


etcTIMEZONE

etcprofile

etccshlogin



n usrsbinsmh



etcTIMEZONE

etcprofile

etccshlogin




12142007 PUBLIC 63148











Recommendation



Prerequisites





Note





64148 PUBLIC 12142007


Recommendation




Recommendation


Caution



Recommendation



Caution




12142007 PUBLIC 65148




Recommendation



Recommendation


Note








Note



66148 PUBLIC 12142007



361 SAP Directories








12142007 PUBLIC 67148



l global


l profile


l exe









Local Directories


68148 PUBLIC 12142007


n SYS

Note




l







MaxDB Directories







sapdb MaxDBsoftware


12142007 PUBLIC 69148







n work


70 MB





Procedure


Note



70148 PUBLIC 12142007





Note



Example


12142007 PUBLIC 71148


your HA partner

Figure 13

End of HA (UNIX)






72148 PUBLIC 12142007


Procedure






n usrsaptrans


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt



12142007 PUBLIC 73148




sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt


sapmntltSIDgt

End of HA (UNIX)



Note






Note



74148 PUBLIC 12142007



Example



Example




Note



Note










12142007 PUBLIC 75148





Note









Note


Note


Note



Note



76148 PUBLIC 12142007


usrsbinsam










ioscan -m lun




12142007 PUBLIC 77148


Note




Example



Example




Example



Example




Note




78148 PUBLIC 12142007


Note


















Note




12142007 PUBLIC 79148






Example


Note


Note





n usrsbinsmh







80148 PUBLIC 12142007










Infrastructure




12142007 PUBLIC 81148






Note













82148 PUBLIC 12142007


Example

sapmntC11


4 Type OK5 Exit SAM










n usrsbinsmh




Example

sapmntCUS


12142007 PUBLIC 83148


8 Exit SMH









Example





Note





84148 PUBLIC 12142007


Example



Example

mount -a





Example


Note





Note





12142007 PUBLIC 85148


Example



Example

mount -a



Prerequisites



Procedure






86148 PUBLIC 12142007









this section


Note






12142007 PUBLIC 87148









Note




Caution





88148 PUBLIC 12142007



Note


Caution





Example

51031387_151031387_2




Note


12142007 PUBLIC 89148





Procedure




Example


90148 PUBLIC 12142007

4 Installation

4 Installation
















12142007 PUBLIC 91148

4 Installation










Note










92148 PUBLIC 12142007

4 Installation

















12142007 PUBLIC 93148







Procedure












94148 PUBLIC 12142007




43 Running SAPinst




Recommendation




Caution


12142007 PUBLIC 95148






Using SAPinst GUI








96148 PUBLIC 12142007









Prerequisites




Shell Used Command


export DISPLAY





12142007 PUBLIC 97148


Procedure


Caution





sapinst

Example


sapinst


Note


End of HA (UNIX)

98148 PUBLIC 12142007


Caution






Shell Used Command


export TEMP





Note





12142007 PUBLIC 99148


Note


Recommendation




More Information






Note






100148 PUBLIC 12142007


n Standard System













12142007 PUBLIC 101148


n






















102148 PUBLIC 12142007















12142007 PUBLIC 103148


5 Post-Installation

5 Post-Installation




Note



Note



5




12142007 PUBLIC 105148














Prerequisites




Note


106148 PUBLIC 12142007


Example



Administrator



Caution







Procedure


12142007 PUBLIC 107148





System





Caution


Caution



108148 PUBLIC 12142007




Procedure







Note





12142007 PUBLIC 109148






Procedure








110148 PUBLIC 12142007








n SQL Studio (GUI)


Prerequisites





Windows 2000 Any

Windows 2003 Any


l 64 MB RAM




12142007 PUBLIC 111148


Caution


IndepDataPath


IndepProgPath

Procedure









Note





112148 PUBLIC 12142007


Caution









Caution



Procedure


12142007 PUBLIC 113148


Note



Example



file into it

Example







114148 PUBLIC 12142007




Note








12142007 PUBLIC 115148


Example



















Note


116148 PUBLIC 12142007




Prerequisites




Procedure




Procedure





12142007 PUBLIC 117148


Recommendation


Caution












118148 PUBLIC 12142007


Host Agent User



Note




















12142007 PUBLIC 119148













Procedure



120148 PUBLIC 12142007


Note







Procedure



Manual Contents









12142007 PUBLIC 121148


Manual Contents














122148 PUBLIC 12142007




Caution




l usrsapltSAPSIDgt




Note


Prerequisites








12142007 PUBLIC 123148


Caution





124148 PUBLIC 12142007





n






Note





Example



ioscan -fnkCdisk


12142007 PUBLIC 125148






Example






ltmedium-mountdirgt

Example





n usrsbinsmh



ltmedium-mountdirgt

Example


126148 PUBLIC 12142007











Option Definition




12142007 PUBLIC 127148


Note




Caution



Note



sapinst

Example


sapinst


Note



128148 PUBLIC 12142007







Prerequisites



Procedure


Caution




sapinst -nogui

12142007 PUBLIC 129148


Example


sapinst -nogui




Caution




sapinst -nogui








130148 PUBLIC 12142007





Note



Note






Caution



Note



12142007 PUBLIC 131148



Note



Note






sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note


132148 PUBLIC 12142007





Procedure








Note







12142007 PUBLIC 133148


Procedure















Note



Prerequisites


134148 PUBLIC 12142007





Example



Note







Note





12142007 PUBLIC 135148





Note







Prerequisites




Note


3 Choose Finish

136148 PUBLIC 12142007





Note










12142007 PUBLIC 137148


Prerequisites





Caution




Note


n



Procedure




138148 PUBLIC 12142007


Note






Note



startdb




Note



Note






12142007 PUBLIC 139148


Note



Note





Note




stopsap DB


Note







140148 PUBLIC 12142007


stopdb


Note







Note


Caution





Procedure


12142007 PUBLIC 141148






Caution



Prerequisites




Procedure



Note


142148 PUBLIC 12142007





Caution




Note



12142007 PUBLIC 143148


Example Description














144148 PUBLIC 12142007



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom






12142007 PUBLIC 145148













146148 PUBLIC 12142007













12142007 PUBLIC 147148



Table of Contents




12142007 PUBLIC 3148




4148 PUBLIC 12142007



12142007 PUBLIC 5148

6148 PUBLIC 12142007

1 Introduction

1 Introduction


Constraints








12142007 PUBLIC 7148


n





12 New Features


Caution



Area Description







8148 PUBLIC 12142007


Area Description
















12142007 PUBLIC 9148


Operating Systems

Area Description



Documentation

Area Description
















10148 PUBLIC 12142007








Documentation














12142007 PUBLIC 11148









General Quick Links
























12148 PUBLIC 12142007












Terminology


Variables











12142007 PUBLIC 13148






Example


14148 PUBLIC 12142007

2 Planning

2 Planning








4











12142007 PUBLIC 15148


n





211 Standard System







16148 PUBLIC 12142007



Note









12142007 PUBLIC 17148




End of HA (UNIX)






18148 PUBLIC 12142007











12142007 PUBLIC 19148









20148 PUBLIC 12142007







12142007 PUBLIC 21148


Figure 7 Host Agent




Note


More Information





22148 PUBLIC 12142007






12142007 PUBLIC 23148






usrsap

ltDRIVEgtsapdb









24148 PUBLIC 12142007



Security Issues


Caution


Recommendation



Caution







Performance Issues




12142007 PUBLIC 25148






Figure 9




26148 PUBLIC 12142007






Note





12142007 PUBLIC 27148


Caution









SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

28148 PUBLIC 12142007







SAP MMC


SAP MC


12142007 PUBLIC 29148










Note







30148 PUBLIC 12142007





Recommendation







12142007 PUBLIC 31148







Note



32148 PUBLIC 12142007




12142007 PUBLIC 33148


3 Preparation

3 Preparation




Note







7



8




12142007 PUBLIC 35148

3 Preparation



















36148 PUBLIC 12142007












USR VAR




12142007 PUBLIC 37148






UID USR VAR











38148 PUBLIC 12142007










Master Password




12142007 PUBLIC 39148















40148 PUBLIC 12142007



















12142007 PUBLIC 41148





Host Agent












volumes

42148 PUBLIC 12142007










Note






Recommendation




12142007 PUBLIC 43148










Process Flow


Caution



Note




44148 PUBLIC 12142007






Recommendation


Note


Prerequisites


Procedure



Note





12142007 PUBLIC 45148













|grep Total







46148 PUBLIC 12142007
















See SAP Note 837670



libldapssl41so



Other Requirements






12142007 PUBLIC 47148










Minimum RAM 2 GB












Note


48148 PUBLIC 12142007









Minimum RAM 1 GB














12142007 PUBLIC 49148







RAM 1 GB

















50148 PUBLIC 12142007



Minimum RAM 1 GB




















Minimum RAM 1 GB


12142007 PUBLIC 51148









Note







Minimum RAM 1 GB






End of HA (UNIX)

52148 PUBLIC 12142007













RAM 1 GB










12142007 PUBLIC 53148









Minimum RAM 1 GB












54148 PUBLIC 12142007







Minimum RAM 1 GB














Minimum RAM 05 GB


12142007 PUBLIC 55148








Caution



Caution










56148 PUBLIC 12142007




n kcweb(1M)

n kcusage(1M)

n kcalarm(1M)






as often




n usrsbinsmh



12142007 PUBLIC 57148






Recommendation






Total



Example

usrsbinswapinfo -dm

Mb Mb Mb PCT Mb


dev 10000 82 9918 1 0 - 1 devvg00lvol2

dev 20000 83 19917 0 0 - 1 devvg01lvol9





58148 PUBLIC 12142007














Note



Note




cd ltINSTDIRgt



12142007 PUBLIC 59148







Procedure



Note





60148 PUBLIC 12142007


Recommendation


Caution







Caution


Caution


Caution



User Primary Group


sqdltdbsidgt sapsys

sdb sdba

12142007 PUBLIC 61148



User Primary Group


Caution


Caution


Groups and Members

Groups Members




User Primary Group




Note







62148 PUBLIC 12142007


usrsbinsam


etcTIMEZONE

etcprofile

etccshlogin



n usrsbinsmh



etcTIMEZONE

etcprofile

etccshlogin




12142007 PUBLIC 63148











Recommendation



Prerequisites





Note





64148 PUBLIC 12142007


Recommendation




Recommendation


Caution



Recommendation



Caution




12142007 PUBLIC 65148




Recommendation



Recommendation


Note








Note



66148 PUBLIC 12142007



361 SAP Directories








12142007 PUBLIC 67148



l global


l profile


l exe









Local Directories


68148 PUBLIC 12142007


n SYS

Note




l







MaxDB Directories







sapdb MaxDBsoftware


12142007 PUBLIC 69148







n work


70 MB





Procedure


Note



70148 PUBLIC 12142007





Note



Example


12142007 PUBLIC 71148


your HA partner

Figure 13

End of HA (UNIX)






72148 PUBLIC 12142007


Procedure






n usrsaptrans


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt



12142007 PUBLIC 73148




sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt


sapmntltSIDgt

End of HA (UNIX)



Note






Note



74148 PUBLIC 12142007



Example



Example




Note



Note










12142007 PUBLIC 75148





Note









Note


Note


Note



Note



76148 PUBLIC 12142007


usrsbinsam










ioscan -m lun




12142007 PUBLIC 77148


Note




Example



Example




Example



Example




Note




78148 PUBLIC 12142007


Note


















Note




12142007 PUBLIC 79148






Example


Note


Note





n usrsbinsmh







80148 PUBLIC 12142007










Infrastructure




12142007 PUBLIC 81148






Note













82148 PUBLIC 12142007


Example

sapmntC11


4 Type OK5 Exit SAM










n usrsbinsmh




Example

sapmntCUS


12142007 PUBLIC 83148


8 Exit SMH









Example





Note





84148 PUBLIC 12142007


Example



Example

mount -a





Example


Note





Note





12142007 PUBLIC 85148


Example



Example

mount -a



Prerequisites



Procedure






86148 PUBLIC 12142007









this section


Note






12142007 PUBLIC 87148









Note




Caution





88148 PUBLIC 12142007



Note


Caution





Example

51031387_151031387_2




Note


12142007 PUBLIC 89148





Procedure




Example


90148 PUBLIC 12142007

4 Installation

4 Installation
















12142007 PUBLIC 91148

4 Installation










Note










92148 PUBLIC 12142007

4 Installation

















12142007 PUBLIC 93148







Procedure












94148 PUBLIC 12142007




43 Running SAPinst




Recommendation




Caution


12142007 PUBLIC 95148






Using SAPinst GUI








96148 PUBLIC 12142007









Prerequisites




Shell Used Command


export DISPLAY





12142007 PUBLIC 97148


Procedure


Caution





sapinst

Example


sapinst


Note


End of HA (UNIX)

98148 PUBLIC 12142007


Caution






Shell Used Command


export TEMP





Note





12142007 PUBLIC 99148


Note


Recommendation




More Information






Note






100148 PUBLIC 12142007


n Standard System













12142007 PUBLIC 101148


n






















102148 PUBLIC 12142007















12142007 PUBLIC 103148


5 Post-Installation

5 Post-Installation




Note



Note



5




12142007 PUBLIC 105148














Prerequisites




Note


106148 PUBLIC 12142007


Example



Administrator



Caution







Procedure


12142007 PUBLIC 107148





System





Caution


Caution



108148 PUBLIC 12142007




Procedure







Note





12142007 PUBLIC 109148






Procedure








110148 PUBLIC 12142007








n SQL Studio (GUI)


Prerequisites





Windows 2000 Any

Windows 2003 Any


l 64 MB RAM




12142007 PUBLIC 111148


Caution


IndepDataPath


IndepProgPath

Procedure









Note





112148 PUBLIC 12142007


Caution









Caution



Procedure


12142007 PUBLIC 113148


Note



Example



file into it

Example







114148 PUBLIC 12142007




Note








12142007 PUBLIC 115148


Example



















Note


116148 PUBLIC 12142007




Prerequisites




Procedure




Procedure





12142007 PUBLIC 117148


Recommendation


Caution












118148 PUBLIC 12142007


Host Agent User



Note




















12142007 PUBLIC 119148













Procedure



120148 PUBLIC 12142007


Note







Procedure



Manual Contents









12142007 PUBLIC 121148


Manual Contents














122148 PUBLIC 12142007




Caution




l usrsapltSAPSIDgt




Note


Prerequisites








12142007 PUBLIC 123148


Caution





124148 PUBLIC 12142007





n






Note





Example



ioscan -fnkCdisk


12142007 PUBLIC 125148






Example






ltmedium-mountdirgt

Example





n usrsbinsmh



ltmedium-mountdirgt

Example


126148 PUBLIC 12142007











Option Definition




12142007 PUBLIC 127148


Note




Caution



Note



sapinst

Example


sapinst


Note



128148 PUBLIC 12142007







Prerequisites



Procedure


Caution




sapinst -nogui

12142007 PUBLIC 129148


Example


sapinst -nogui




Caution




sapinst -nogui








130148 PUBLIC 12142007





Note



Note






Caution



Note



12142007 PUBLIC 131148



Note



Note






sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note


132148 PUBLIC 12142007





Procedure








Note







12142007 PUBLIC 133148


Procedure















Note



Prerequisites


134148 PUBLIC 12142007





Example



Note







Note





12142007 PUBLIC 135148





Note







Prerequisites




Note


3 Choose Finish

136148 PUBLIC 12142007





Note










12142007 PUBLIC 137148


Prerequisites





Caution




Note


n



Procedure




138148 PUBLIC 12142007


Note






Note



startdb




Note



Note






12142007 PUBLIC 139148


Note



Note





Note




stopsap DB


Note







140148 PUBLIC 12142007


stopdb


Note







Note


Caution





Procedure


12142007 PUBLIC 141148






Caution



Prerequisites




Procedure



Note


142148 PUBLIC 12142007





Caution




Note



12142007 PUBLIC 143148


Example Description














144148 PUBLIC 12142007



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom






12142007 PUBLIC 145148













146148 PUBLIC 12142007













12142007 PUBLIC 147148






4148 PUBLIC 12142007



12142007 PUBLIC 5148

6148 PUBLIC 12142007

1 Introduction

1 Introduction


Constraints








12142007 PUBLIC 7148


n





12 New Features


Caution



Area Description







8148 PUBLIC 12142007


Area Description
















12142007 PUBLIC 9148


Operating Systems

Area Description



Documentation

Area Description
















10148 PUBLIC 12142007








Documentation














12142007 PUBLIC 11148









General Quick Links
























12148 PUBLIC 12142007












Terminology


Variables











12142007 PUBLIC 13148






Example


14148 PUBLIC 12142007

2 Planning

2 Planning








4











12142007 PUBLIC 15148


n





211 Standard System







16148 PUBLIC 12142007



Note









12142007 PUBLIC 17148




End of HA (UNIX)






18148 PUBLIC 12142007











12142007 PUBLIC 19148









20148 PUBLIC 12142007







12142007 PUBLIC 21148


Figure 7 Host Agent




Note


More Information





22148 PUBLIC 12142007






12142007 PUBLIC 23148






usrsap

ltDRIVEgtsapdb









24148 PUBLIC 12142007



Security Issues


Caution


Recommendation



Caution







Performance Issues




12142007 PUBLIC 25148






Figure 9




26148 PUBLIC 12142007






Note





12142007 PUBLIC 27148


Caution









SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

28148 PUBLIC 12142007







SAP MMC


SAP MC


12142007 PUBLIC 29148










Note







30148 PUBLIC 12142007





Recommendation







12142007 PUBLIC 31148







Note



32148 PUBLIC 12142007




12142007 PUBLIC 33148


3 Preparation

3 Preparation




Note







7



8




12142007 PUBLIC 35148

3 Preparation



















36148 PUBLIC 12142007












USR VAR




12142007 PUBLIC 37148






UID USR VAR











38148 PUBLIC 12142007










Master Password




12142007 PUBLIC 39148















40148 PUBLIC 12142007



















12142007 PUBLIC 41148





Host Agent












volumes

42148 PUBLIC 12142007










Note






Recommendation




12142007 PUBLIC 43148










Process Flow


Caution



Note




44148 PUBLIC 12142007






Recommendation


Note


Prerequisites


Procedure



Note





12142007 PUBLIC 45148













|grep Total







46148 PUBLIC 12142007
















See SAP Note 837670



libldapssl41so



Other Requirements






12142007 PUBLIC 47148










Minimum RAM 2 GB












Note


48148 PUBLIC 12142007









Minimum RAM 1 GB














12142007 PUBLIC 49148







RAM 1 GB

















50148 PUBLIC 12142007



Minimum RAM 1 GB




















Minimum RAM 1 GB


12142007 PUBLIC 51148









Note







Minimum RAM 1 GB






End of HA (UNIX)

52148 PUBLIC 12142007













RAM 1 GB










12142007 PUBLIC 53148









Minimum RAM 1 GB












54148 PUBLIC 12142007







Minimum RAM 1 GB














Minimum RAM 05 GB


12142007 PUBLIC 55148








Caution



Caution










56148 PUBLIC 12142007




n kcweb(1M)

n kcusage(1M)

n kcalarm(1M)






as often




n usrsbinsmh



12142007 PUBLIC 57148






Recommendation






Total



Example

usrsbinswapinfo -dm

Mb Mb Mb PCT Mb


dev 10000 82 9918 1 0 - 1 devvg00lvol2

dev 20000 83 19917 0 0 - 1 devvg01lvol9





58148 PUBLIC 12142007














Note



Note




cd ltINSTDIRgt



12142007 PUBLIC 59148







Procedure



Note





60148 PUBLIC 12142007


Recommendation


Caution







Caution


Caution


Caution



User Primary Group


sqdltdbsidgt sapsys

sdb sdba

12142007 PUBLIC 61148



User Primary Group


Caution


Caution


Groups and Members

Groups Members




User Primary Group




Note







62148 PUBLIC 12142007


usrsbinsam


etcTIMEZONE

etcprofile

etccshlogin



n usrsbinsmh



etcTIMEZONE

etcprofile

etccshlogin




12142007 PUBLIC 63148











Recommendation



Prerequisites





Note





64148 PUBLIC 12142007


Recommendation




Recommendation


Caution



Recommendation



Caution




12142007 PUBLIC 65148




Recommendation



Recommendation


Note








Note



66148 PUBLIC 12142007



361 SAP Directories








12142007 PUBLIC 67148



l global


l profile


l exe









Local Directories


68148 PUBLIC 12142007


n SYS

Note




l







MaxDB Directories







sapdb MaxDBsoftware


12142007 PUBLIC 69148







n work


70 MB





Procedure


Note



70148 PUBLIC 12142007





Note



Example


12142007 PUBLIC 71148


your HA partner

Figure 13

End of HA (UNIX)






72148 PUBLIC 12142007


Procedure






n usrsaptrans


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt



12142007 PUBLIC 73148




sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt


sapmntltSIDgt

End of HA (UNIX)



Note






Note



74148 PUBLIC 12142007



Example



Example




Note



Note










12142007 PUBLIC 75148





Note









Note


Note


Note



Note



76148 PUBLIC 12142007


usrsbinsam










ioscan -m lun




12142007 PUBLIC 77148


Note




Example



Example




Example



Example




Note




78148 PUBLIC 12142007


Note


















Note




12142007 PUBLIC 79148






Example


Note


Note





n usrsbinsmh







80148 PUBLIC 12142007










Infrastructure




12142007 PUBLIC 81148






Note













82148 PUBLIC 12142007


Example

sapmntC11


4 Type OK5 Exit SAM










n usrsbinsmh




Example

sapmntCUS


12142007 PUBLIC 83148


8 Exit SMH









Example





Note





84148 PUBLIC 12142007


Example



Example

mount -a





Example


Note





Note





12142007 PUBLIC 85148


Example



Example

mount -a



Prerequisites



Procedure






86148 PUBLIC 12142007









this section


Note






12142007 PUBLIC 87148









Note




Caution





88148 PUBLIC 12142007



Note


Caution





Example

51031387_151031387_2




Note


12142007 PUBLIC 89148





Procedure




Example


90148 PUBLIC 12142007

4 Installation

4 Installation
















12142007 PUBLIC 91148

4 Installation










Note










92148 PUBLIC 12142007

4 Installation

















12142007 PUBLIC 93148







Procedure












94148 PUBLIC 12142007




43 Running SAPinst




Recommendation




Caution


12142007 PUBLIC 95148






Using SAPinst GUI








96148 PUBLIC 12142007









Prerequisites




Shell Used Command


export DISPLAY





12142007 PUBLIC 97148


Procedure


Caution





sapinst

Example


sapinst


Note


End of HA (UNIX)

98148 PUBLIC 12142007


Caution






Shell Used Command


export TEMP





Note





12142007 PUBLIC 99148


Note


Recommendation




More Information






Note






100148 PUBLIC 12142007


n Standard System













12142007 PUBLIC 101148


n






















102148 PUBLIC 12142007















12142007 PUBLIC 103148


5 Post-Installation

5 Post-Installation




Note



Note



5




12142007 PUBLIC 105148














Prerequisites




Note


106148 PUBLIC 12142007


Example



Administrator



Caution







Procedure


12142007 PUBLIC 107148





System





Caution


Caution



108148 PUBLIC 12142007




Procedure







Note





12142007 PUBLIC 109148






Procedure








110148 PUBLIC 12142007








n SQL Studio (GUI)


Prerequisites





Windows 2000 Any

Windows 2003 Any


l 64 MB RAM




12142007 PUBLIC 111148


Caution


IndepDataPath


IndepProgPath

Procedure









Note





112148 PUBLIC 12142007


Caution









Caution



Procedure


12142007 PUBLIC 113148


Note



Example



file into it

Example







114148 PUBLIC 12142007




Note








12142007 PUBLIC 115148


Example



















Note


116148 PUBLIC 12142007




Prerequisites




Procedure




Procedure





12142007 PUBLIC 117148


Recommendation


Caution












118148 PUBLIC 12142007


Host Agent User



Note




















12142007 PUBLIC 119148













Procedure



120148 PUBLIC 12142007


Note







Procedure



Manual Contents









12142007 PUBLIC 121148


Manual Contents














122148 PUBLIC 12142007




Caution




l usrsapltSAPSIDgt




Note


Prerequisites








12142007 PUBLIC 123148


Caution





124148 PUBLIC 12142007





n






Note





Example



ioscan -fnkCdisk


12142007 PUBLIC 125148






Example






ltmedium-mountdirgt

Example





n usrsbinsmh



ltmedium-mountdirgt

Example


126148 PUBLIC 12142007











Option Definition




12142007 PUBLIC 127148


Note




Caution



Note



sapinst

Example


sapinst


Note



128148 PUBLIC 12142007







Prerequisites



Procedure


Caution




sapinst -nogui

12142007 PUBLIC 129148


Example


sapinst -nogui




Caution




sapinst -nogui








130148 PUBLIC 12142007





Note



Note






Caution



Note



12142007 PUBLIC 131148



Note



Note






sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note


132148 PUBLIC 12142007





Procedure








Note







12142007 PUBLIC 133148


Procedure















Note



Prerequisites


134148 PUBLIC 12142007





Example



Note







Note





12142007 PUBLIC 135148





Note







Prerequisites




Note


3 Choose Finish

136148 PUBLIC 12142007





Note










12142007 PUBLIC 137148


Prerequisites





Caution




Note


n



Procedure




138148 PUBLIC 12142007


Note






Note



startdb




Note



Note






12142007 PUBLIC 139148


Note



Note





Note




stopsap DB


Note







140148 PUBLIC 12142007


stopdb


Note







Note


Caution





Procedure


12142007 PUBLIC 141148






Caution



Prerequisites




Procedure



Note


142148 PUBLIC 12142007





Caution




Note



12142007 PUBLIC 143148


Example Description














144148 PUBLIC 12142007



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom






12142007 PUBLIC 145148













146148 PUBLIC 12142007













12142007 PUBLIC 147148





12142007 PUBLIC 5148

6148 PUBLIC 12142007

1 Introduction

1 Introduction


Constraints








12142007 PUBLIC 7148


n





12 New Features


Caution



Area Description







8148 PUBLIC 12142007


Area Description
















12142007 PUBLIC 9148


Operating Systems

Area Description



Documentation

Area Description
















10148 PUBLIC 12142007








Documentation














12142007 PUBLIC 11148









General Quick Links
























12148 PUBLIC 12142007












Terminology


Variables











12142007 PUBLIC 13148






Example


14148 PUBLIC 12142007

2 Planning

2 Planning








4











12142007 PUBLIC 15148


n





211 Standard System







16148 PUBLIC 12142007



Note









12142007 PUBLIC 17148




End of HA (UNIX)






18148 PUBLIC 12142007











12142007 PUBLIC 19148









20148 PUBLIC 12142007







12142007 PUBLIC 21148


Figure 7 Host Agent




Note


More Information





22148 PUBLIC 12142007






12142007 PUBLIC 23148






usrsap

ltDRIVEgtsapdb









24148 PUBLIC 12142007



Security Issues


Caution


Recommendation



Caution







Performance Issues




12142007 PUBLIC 25148






Figure 9




26148 PUBLIC 12142007






Note





12142007 PUBLIC 27148


Caution









SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

28148 PUBLIC 12142007







SAP MMC


SAP MC


12142007 PUBLIC 29148










Note







30148 PUBLIC 12142007





Recommendation







12142007 PUBLIC 31148







Note



32148 PUBLIC 12142007




12142007 PUBLIC 33148


3 Preparation

3 Preparation




Note







7



8




12142007 PUBLIC 35148

3 Preparation



















36148 PUBLIC 12142007












USR VAR




12142007 PUBLIC 37148






UID USR VAR











38148 PUBLIC 12142007










Master Password




12142007 PUBLIC 39148















40148 PUBLIC 12142007



















12142007 PUBLIC 41148





Host Agent












volumes

42148 PUBLIC 12142007










Note






Recommendation




12142007 PUBLIC 43148










Process Flow


Caution



Note




44148 PUBLIC 12142007






Recommendation


Note


Prerequisites


Procedure



Note





12142007 PUBLIC 45148













|grep Total







46148 PUBLIC 12142007
















See SAP Note 837670



libldapssl41so



Other Requirements






12142007 PUBLIC 47148










Minimum RAM 2 GB












Note


48148 PUBLIC 12142007









Minimum RAM 1 GB














12142007 PUBLIC 49148







RAM 1 GB

















50148 PUBLIC 12142007



Minimum RAM 1 GB




















Minimum RAM 1 GB


12142007 PUBLIC 51148









Note







Minimum RAM 1 GB






End of HA (UNIX)

52148 PUBLIC 12142007













RAM 1 GB










12142007 PUBLIC 53148









Minimum RAM 1 GB












54148 PUBLIC 12142007







Minimum RAM 1 GB














Minimum RAM 05 GB


12142007 PUBLIC 55148








Caution



Caution










56148 PUBLIC 12142007




n kcweb(1M)

n kcusage(1M)

n kcalarm(1M)






as often




n usrsbinsmh



12142007 PUBLIC 57148






Recommendation






Total



Example

usrsbinswapinfo -dm

Mb Mb Mb PCT Mb


dev 10000 82 9918 1 0 - 1 devvg00lvol2

dev 20000 83 19917 0 0 - 1 devvg01lvol9





58148 PUBLIC 12142007














Note



Note




cd ltINSTDIRgt



12142007 PUBLIC 59148







Procedure



Note





60148 PUBLIC 12142007


Recommendation


Caution







Caution


Caution


Caution



User Primary Group


sqdltdbsidgt sapsys

sdb sdba

12142007 PUBLIC 61148



User Primary Group


Caution


Caution


Groups and Members

Groups Members




User Primary Group




Note







62148 PUBLIC 12142007


usrsbinsam


etcTIMEZONE

etcprofile

etccshlogin



n usrsbinsmh



etcTIMEZONE

etcprofile

etccshlogin




12142007 PUBLIC 63148











Recommendation



Prerequisites





Note





64148 PUBLIC 12142007


Recommendation




Recommendation


Caution



Recommendation



Caution




12142007 PUBLIC 65148




Recommendation



Recommendation


Note








Note



66148 PUBLIC 12142007



361 SAP Directories








12142007 PUBLIC 67148



l global


l profile


l exe









Local Directories


68148 PUBLIC 12142007


n SYS

Note




l







MaxDB Directories







sapdb MaxDBsoftware


12142007 PUBLIC 69148







n work


70 MB





Procedure


Note



70148 PUBLIC 12142007





Note



Example


12142007 PUBLIC 71148


your HA partner

Figure 13

End of HA (UNIX)






72148 PUBLIC 12142007


Procedure






n usrsaptrans


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt



12142007 PUBLIC 73148




sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt


sapmntltSIDgt

End of HA (UNIX)



Note






Note



74148 PUBLIC 12142007



Example



Example




Note



Note










12142007 PUBLIC 75148





Note









Note


Note


Note



Note



76148 PUBLIC 12142007


usrsbinsam










ioscan -m lun




12142007 PUBLIC 77148


Note




Example



Example




Example



Example




Note




78148 PUBLIC 12142007


Note


















Note




12142007 PUBLIC 79148






Example


Note


Note





n usrsbinsmh







80148 PUBLIC 12142007










Infrastructure




12142007 PUBLIC 81148






Note













82148 PUBLIC 12142007


Example

sapmntC11


4 Type OK5 Exit SAM










n usrsbinsmh




Example

sapmntCUS


12142007 PUBLIC 83148


8 Exit SMH









Example





Note





84148 PUBLIC 12142007


Example



Example

mount -a





Example


Note





Note





12142007 PUBLIC 85148


Example



Example

mount -a



Prerequisites



Procedure






86148 PUBLIC 12142007









this section


Note






12142007 PUBLIC 87148









Note




Caution





88148 PUBLIC 12142007



Note


Caution





Example

51031387_151031387_2




Note


12142007 PUBLIC 89148





Procedure




Example


90148 PUBLIC 12142007

4 Installation

4 Installation
















12142007 PUBLIC 91148

4 Installation










Note










92148 PUBLIC 12142007

4 Installation

















12142007 PUBLIC 93148







Procedure












94148 PUBLIC 12142007




43 Running SAPinst




Recommendation




Caution


12142007 PUBLIC 95148






Using SAPinst GUI








96148 PUBLIC 12142007









Prerequisites




Shell Used Command


export DISPLAY





12142007 PUBLIC 97148


Procedure


Caution





sapinst

Example


sapinst


Note


End of HA (UNIX)

98148 PUBLIC 12142007


Caution






Shell Used Command


export TEMP





Note





12142007 PUBLIC 99148


Note


Recommendation




More Information






Note






100148 PUBLIC 12142007


n Standard System













12142007 PUBLIC 101148


n






















102148 PUBLIC 12142007















12142007 PUBLIC 103148


5 Post-Installation

5 Post-Installation




Note



Note



5




12142007 PUBLIC 105148














Prerequisites




Note


106148 PUBLIC 12142007


Example



Administrator



Caution







Procedure


12142007 PUBLIC 107148





System





Caution


Caution



108148 PUBLIC 12142007




Procedure







Note





12142007 PUBLIC 109148






Procedure








110148 PUBLIC 12142007








n SQL Studio (GUI)


Prerequisites





Windows 2000 Any

Windows 2003 Any


l 64 MB RAM




12142007 PUBLIC 111148


Caution


IndepDataPath


IndepProgPath

Procedure









Note





112148 PUBLIC 12142007


Caution









Caution



Procedure


12142007 PUBLIC 113148


Note



Example



file into it

Example







114148 PUBLIC 12142007




Note








12142007 PUBLIC 115148


Example



















Note


116148 PUBLIC 12142007




Prerequisites




Procedure




Procedure





12142007 PUBLIC 117148


Recommendation


Caution












118148 PUBLIC 12142007


Host Agent User



Note




















12142007 PUBLIC 119148













Procedure



120148 PUBLIC 12142007


Note







Procedure



Manual Contents









12142007 PUBLIC 121148


Manual Contents














122148 PUBLIC 12142007




Caution




l usrsapltSAPSIDgt




Note


Prerequisites








12142007 PUBLIC 123148


Caution





124148 PUBLIC 12142007





n






Note





Example



ioscan -fnkCdisk


12142007 PUBLIC 125148






Example






ltmedium-mountdirgt

Example





n usrsbinsmh



ltmedium-mountdirgt

Example


126148 PUBLIC 12142007











Option Definition




12142007 PUBLIC 127148


Note




Caution



Note



sapinst

Example


sapinst


Note



128148 PUBLIC 12142007







Prerequisites



Procedure


Caution




sapinst -nogui

12142007 PUBLIC 129148


Example


sapinst -nogui




Caution




sapinst -nogui








130148 PUBLIC 12142007





Note



Note






Caution



Note



12142007 PUBLIC 131148



Note



Note






sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note


132148 PUBLIC 12142007





Procedure








Note







12142007 PUBLIC 133148


Procedure















Note



Prerequisites


134148 PUBLIC 12142007





Example



Note







Note





12142007 PUBLIC 135148





Note







Prerequisites




Note


3 Choose Finish

136148 PUBLIC 12142007





Note










12142007 PUBLIC 137148


Prerequisites





Caution




Note


n



Procedure




138148 PUBLIC 12142007


Note






Note



startdb




Note



Note






12142007 PUBLIC 139148


Note



Note





Note




stopsap DB


Note







140148 PUBLIC 12142007


stopdb


Note







Note


Caution





Procedure


12142007 PUBLIC 141148






Caution



Prerequisites




Procedure



Note


142148 PUBLIC 12142007





Caution




Note



12142007 PUBLIC 143148


Example Description














144148 PUBLIC 12142007



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom






12142007 PUBLIC 145148













146148 PUBLIC 12142007













12142007 PUBLIC 147148



6148 PUBLIC 12142007

1 Introduction

1 Introduction


Constraints








12142007 PUBLIC 7148


n





12 New Features


Caution



Area Description







8148 PUBLIC 12142007


Area Description
















12142007 PUBLIC 9148


Operating Systems

Area Description



Documentation

Area Description
















10148 PUBLIC 12142007








Documentation














12142007 PUBLIC 11148









General Quick Links
























12148 PUBLIC 12142007












Terminology


Variables











12142007 PUBLIC 13148






Example


14148 PUBLIC 12142007

2 Planning

2 Planning








4











12142007 PUBLIC 15148


n





211 Standard System







16148 PUBLIC 12142007



Note









12142007 PUBLIC 17148




End of HA (UNIX)






18148 PUBLIC 12142007











12142007 PUBLIC 19148









20148 PUBLIC 12142007







12142007 PUBLIC 21148


Figure 7 Host Agent




Note


More Information





22148 PUBLIC 12142007






12142007 PUBLIC 23148






usrsap

ltDRIVEgtsapdb









24148 PUBLIC 12142007



Security Issues


Caution


Recommendation



Caution







Performance Issues




12142007 PUBLIC 25148






Figure 9




26148 PUBLIC 12142007






Note





12142007 PUBLIC 27148


Caution









SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

28148 PUBLIC 12142007







SAP MMC


SAP MC


12142007 PUBLIC 29148










Note







30148 PUBLIC 12142007





Recommendation







12142007 PUBLIC 31148







Note



32148 PUBLIC 12142007




12142007 PUBLIC 33148


3 Preparation

3 Preparation




Note







7



8




12142007 PUBLIC 35148

3 Preparation



















36148 PUBLIC 12142007












USR VAR




12142007 PUBLIC 37148






UID USR VAR











38148 PUBLIC 12142007










Master Password




12142007 PUBLIC 39148















40148 PUBLIC 12142007



















12142007 PUBLIC 41148





Host Agent












volumes

42148 PUBLIC 12142007










Note






Recommendation




12142007 PUBLIC 43148










Process Flow


Caution



Note




44148 PUBLIC 12142007






Recommendation


Note


Prerequisites


Procedure



Note





12142007 PUBLIC 45148













|grep Total







46148 PUBLIC 12142007
















See SAP Note 837670



libldapssl41so



Other Requirements






12142007 PUBLIC 47148










Minimum RAM 2 GB












Note


48148 PUBLIC 12142007









Minimum RAM 1 GB














12142007 PUBLIC 49148







RAM 1 GB

















50148 PUBLIC 12142007



Minimum RAM 1 GB




















Minimum RAM 1 GB


12142007 PUBLIC 51148









Note







Minimum RAM 1 GB






End of HA (UNIX)

52148 PUBLIC 12142007













RAM 1 GB










12142007 PUBLIC 53148









Minimum RAM 1 GB












54148 PUBLIC 12142007







Minimum RAM 1 GB














Minimum RAM 05 GB


12142007 PUBLIC 55148








Caution



Caution










56148 PUBLIC 12142007




n kcweb(1M)

n kcusage(1M)

n kcalarm(1M)






as often




n usrsbinsmh



12142007 PUBLIC 57148






Recommendation






Total



Example

usrsbinswapinfo -dm

Mb Mb Mb PCT Mb


dev 10000 82 9918 1 0 - 1 devvg00lvol2

dev 20000 83 19917 0 0 - 1 devvg01lvol9





58148 PUBLIC 12142007














Note



Note




cd ltINSTDIRgt



12142007 PUBLIC 59148







Procedure



Note





60148 PUBLIC 12142007


Recommendation


Caution







Caution


Caution


Caution



User Primary Group


sqdltdbsidgt sapsys

sdb sdba

12142007 PUBLIC 61148



User Primary Group


Caution


Caution


Groups and Members

Groups Members




User Primary Group




Note







62148 PUBLIC 12142007


usrsbinsam


etcTIMEZONE

etcprofile

etccshlogin



n usrsbinsmh



etcTIMEZONE

etcprofile

etccshlogin




12142007 PUBLIC 63148











Recommendation



Prerequisites





Note





64148 PUBLIC 12142007


Recommendation




Recommendation


Caution



Recommendation



Caution




12142007 PUBLIC 65148




Recommendation



Recommendation


Note








Note



66148 PUBLIC 12142007



361 SAP Directories








12142007 PUBLIC 67148



l global


l profile


l exe









Local Directories


68148 PUBLIC 12142007


n SYS

Note




l







MaxDB Directories







sapdb MaxDBsoftware


12142007 PUBLIC 69148







n work


70 MB





Procedure


Note



70148 PUBLIC 12142007





Note



Example


12142007 PUBLIC 71148


your HA partner

Figure 13

End of HA (UNIX)






72148 PUBLIC 12142007


Procedure






n usrsaptrans


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt



12142007 PUBLIC 73148




sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt


sapmntltSIDgt

End of HA (UNIX)



Note






Note



74148 PUBLIC 12142007



Example



Example




Note



Note










12142007 PUBLIC 75148





Note









Note


Note


Note



Note



76148 PUBLIC 12142007


usrsbinsam










ioscan -m lun




12142007 PUBLIC 77148


Note




Example



Example




Example



Example




Note




78148 PUBLIC 12142007


Note


















Note




12142007 PUBLIC 79148






Example


Note


Note





n usrsbinsmh







80148 PUBLIC 12142007










Infrastructure




12142007 PUBLIC 81148






Note













82148 PUBLIC 12142007


Example

sapmntC11


4 Type OK5 Exit SAM










n usrsbinsmh




Example

sapmntCUS


12142007 PUBLIC 83148


8 Exit SMH









Example





Note





84148 PUBLIC 12142007


Example



Example

mount -a





Example


Note





Note





12142007 PUBLIC 85148


Example



Example

mount -a



Prerequisites



Procedure






86148 PUBLIC 12142007









this section


Note






12142007 PUBLIC 87148









Note




Caution





88148 PUBLIC 12142007



Note


Caution





Example

51031387_151031387_2




Note


12142007 PUBLIC 89148





Procedure




Example


90148 PUBLIC 12142007

4 Installation

4 Installation
















12142007 PUBLIC 91148

4 Installation










Note










92148 PUBLIC 12142007

4 Installation

















12142007 PUBLIC 93148







Procedure












94148 PUBLIC 12142007




43 Running SAPinst




Recommendation




Caution


12142007 PUBLIC 95148






Using SAPinst GUI








96148 PUBLIC 12142007









Prerequisites




Shell Used Command


export DISPLAY





12142007 PUBLIC 97148


Procedure


Caution





sapinst

Example


sapinst


Note


End of HA (UNIX)

98148 PUBLIC 12142007


Caution






Shell Used Command


export TEMP





Note





12142007 PUBLIC 99148


Note


Recommendation




More Information






Note






100148 PUBLIC 12142007


n Standard System













12142007 PUBLIC 101148


n






















102148 PUBLIC 12142007















12142007 PUBLIC 103148


5 Post-Installation

5 Post-Installation




Note



Note



5




12142007 PUBLIC 105148














Prerequisites




Note


106148 PUBLIC 12142007


Example



Administrator



Caution







Procedure


12142007 PUBLIC 107148





System





Caution


Caution



108148 PUBLIC 12142007




Procedure







Note





12142007 PUBLIC 109148






Procedure








110148 PUBLIC 12142007








n SQL Studio (GUI)


Prerequisites





Windows 2000 Any

Windows 2003 Any


l 64 MB RAM




12142007 PUBLIC 111148


Caution


IndepDataPath


IndepProgPath

Procedure









Note





112148 PUBLIC 12142007


Caution









Caution



Procedure


12142007 PUBLIC 113148


Note



Example



file into it

Example







114148 PUBLIC 12142007




Note








12142007 PUBLIC 115148


Example



















Note


116148 PUBLIC 12142007




Prerequisites




Procedure




Procedure





12142007 PUBLIC 117148


Recommendation


Caution












118148 PUBLIC 12142007


Host Agent User



Note




















12142007 PUBLIC 119148













Procedure



120148 PUBLIC 12142007


Note







Procedure



Manual Contents









12142007 PUBLIC 121148


Manual Contents














122148 PUBLIC 12142007




Caution




l usrsapltSAPSIDgt




Note


Prerequisites








12142007 PUBLIC 123148


Caution





124148 PUBLIC 12142007





n






Note





Example



ioscan -fnkCdisk


12142007 PUBLIC 125148






Example






ltmedium-mountdirgt

Example





n usrsbinsmh



ltmedium-mountdirgt

Example


126148 PUBLIC 12142007











Option Definition




12142007 PUBLIC 127148


Note




Caution



Note



sapinst

Example


sapinst


Note



128148 PUBLIC 12142007







Prerequisites



Procedure


Caution




sapinst -nogui

12142007 PUBLIC 129148


Example


sapinst -nogui




Caution




sapinst -nogui








130148 PUBLIC 12142007





Note



Note






Caution



Note



12142007 PUBLIC 131148



Note



Note






sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note


132148 PUBLIC 12142007





Procedure








Note







12142007 PUBLIC 133148


Procedure















Note



Prerequisites


134148 PUBLIC 12142007





Example



Note







Note





12142007 PUBLIC 135148





Note







Prerequisites




Note


3 Choose Finish

136148 PUBLIC 12142007





Note










12142007 PUBLIC 137148


Prerequisites





Caution




Note


n



Procedure




138148 PUBLIC 12142007


Note






Note



startdb




Note



Note






12142007 PUBLIC 139148


Note



Note





Note




stopsap DB


Note







140148 PUBLIC 12142007


stopdb


Note







Note


Caution





Procedure


12142007 PUBLIC 141148






Caution



Prerequisites




Procedure



Note


142148 PUBLIC 12142007





Caution




Note



12142007 PUBLIC 143148


Example Description














144148 PUBLIC 12142007



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom






12142007 PUBLIC 145148













146148 PUBLIC 12142007













12142007 PUBLIC 147148



1 Introduction

1 Introduction


Constraints








12142007 PUBLIC 7148


n





12 New Features


Caution



Area Description







8148 PUBLIC 12142007


Area Description
















12142007 PUBLIC 9148


Operating Systems

Area Description



Documentation

Area Description
















10148 PUBLIC 12142007








Documentation














12142007 PUBLIC 11148









General Quick Links
























12148 PUBLIC 12142007












Terminology


Variables











12142007 PUBLIC 13148






Example


14148 PUBLIC 12142007

2 Planning

2 Planning








4











12142007 PUBLIC 15148


n





211 Standard System







16148 PUBLIC 12142007



Note









12142007 PUBLIC 17148




End of HA (UNIX)






18148 PUBLIC 12142007











12142007 PUBLIC 19148









20148 PUBLIC 12142007







12142007 PUBLIC 21148


Figure 7 Host Agent




Note


More Information





22148 PUBLIC 12142007






12142007 PUBLIC 23148






usrsap

ltDRIVEgtsapdb









24148 PUBLIC 12142007



Security Issues


Caution


Recommendation



Caution







Performance Issues




12142007 PUBLIC 25148






Figure 9




26148 PUBLIC 12142007






Note





12142007 PUBLIC 27148


Caution









SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

28148 PUBLIC 12142007







SAP MMC


SAP MC


12142007 PUBLIC 29148










Note







30148 PUBLIC 12142007





Recommendation







12142007 PUBLIC 31148







Note



32148 PUBLIC 12142007




12142007 PUBLIC 33148


3 Preparation

3 Preparation




Note







7



8




12142007 PUBLIC 35148

3 Preparation



















36148 PUBLIC 12142007












USR VAR




12142007 PUBLIC 37148






UID USR VAR











38148 PUBLIC 12142007










Master Password




12142007 PUBLIC 39148















40148 PUBLIC 12142007



















12142007 PUBLIC 41148





Host Agent












volumes

42148 PUBLIC 12142007










Note






Recommendation




12142007 PUBLIC 43148










Process Flow


Caution



Note




44148 PUBLIC 12142007






Recommendation


Note


Prerequisites


Procedure



Note





12142007 PUBLIC 45148













|grep Total







46148 PUBLIC 12142007
















See SAP Note 837670



libldapssl41so



Other Requirements






12142007 PUBLIC 47148










Minimum RAM 2 GB












Note


48148 PUBLIC 12142007









Minimum RAM 1 GB














12142007 PUBLIC 49148







RAM 1 GB

















50148 PUBLIC 12142007



Minimum RAM 1 GB




















Minimum RAM 1 GB


12142007 PUBLIC 51148









Note







Minimum RAM 1 GB






End of HA (UNIX)

52148 PUBLIC 12142007













RAM 1 GB










12142007 PUBLIC 53148









Minimum RAM 1 GB












54148 PUBLIC 12142007







Minimum RAM 1 GB














Minimum RAM 05 GB


12142007 PUBLIC 55148








Caution



Caution










56148 PUBLIC 12142007




n kcweb(1M)

n kcusage(1M)

n kcalarm(1M)






as often




n usrsbinsmh



12142007 PUBLIC 57148






Recommendation






Total



Example

usrsbinswapinfo -dm

Mb Mb Mb PCT Mb


dev 10000 82 9918 1 0 - 1 devvg00lvol2

dev 20000 83 19917 0 0 - 1 devvg01lvol9





58148 PUBLIC 12142007














Note



Note




cd ltINSTDIRgt



12142007 PUBLIC 59148







Procedure



Note





60148 PUBLIC 12142007


Recommendation


Caution







Caution


Caution


Caution



User Primary Group


sqdltdbsidgt sapsys

sdb sdba

12142007 PUBLIC 61148



User Primary Group


Caution


Caution


Groups and Members

Groups Members




User Primary Group




Note







62148 PUBLIC 12142007


usrsbinsam


etcTIMEZONE

etcprofile

etccshlogin



n usrsbinsmh



etcTIMEZONE

etcprofile

etccshlogin




12142007 PUBLIC 63148











Recommendation



Prerequisites





Note





64148 PUBLIC 12142007


Recommendation




Recommendation


Caution



Recommendation



Caution




12142007 PUBLIC 65148




Recommendation



Recommendation


Note








Note



66148 PUBLIC 12142007



361 SAP Directories








12142007 PUBLIC 67148



l global


l profile


l exe









Local Directories


68148 PUBLIC 12142007


n SYS

Note




l







MaxDB Directories







sapdb MaxDBsoftware


12142007 PUBLIC 69148







n work


70 MB





Procedure


Note



70148 PUBLIC 12142007





Note



Example


12142007 PUBLIC 71148


your HA partner

Figure 13

End of HA (UNIX)






72148 PUBLIC 12142007


Procedure






n usrsaptrans


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt



12142007 PUBLIC 73148




sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt


sapmntltSIDgt

End of HA (UNIX)



Note






Note



74148 PUBLIC 12142007



Example



Example




Note



Note










12142007 PUBLIC 75148





Note









Note


Note


Note



Note



76148 PUBLIC 12142007


usrsbinsam










ioscan -m lun




12142007 PUBLIC 77148


Note




Example



Example




Example



Example




Note




78148 PUBLIC 12142007


Note


















Note




12142007 PUBLIC 79148






Example


Note


Note





n usrsbinsmh







80148 PUBLIC 12142007










Infrastructure




12142007 PUBLIC 81148






Note













82148 PUBLIC 12142007


Example

sapmntC11


4 Type OK5 Exit SAM










n usrsbinsmh




Example

sapmntCUS


12142007 PUBLIC 83148


8 Exit SMH









Example





Note





84148 PUBLIC 12142007


Example



Example

mount -a





Example


Note





Note





12142007 PUBLIC 85148


Example



Example

mount -a



Prerequisites



Procedure






86148 PUBLIC 12142007









this section


Note






12142007 PUBLIC 87148









Note




Caution





88148 PUBLIC 12142007



Note


Caution





Example

51031387_151031387_2




Note


12142007 PUBLIC 89148





Procedure




Example


90148 PUBLIC 12142007

4 Installation

4 Installation
















12142007 PUBLIC 91148

4 Installation










Note










92148 PUBLIC 12142007

4 Installation

















12142007 PUBLIC 93148







Procedure












94148 PUBLIC 12142007




43 Running SAPinst




Recommendation




Caution


12142007 PUBLIC 95148






Using SAPinst GUI








96148 PUBLIC 12142007









Prerequisites




Shell Used Command


export DISPLAY





12142007 PUBLIC 97148


Procedure


Caution





sapinst

Example


sapinst


Note


End of HA (UNIX)

98148 PUBLIC 12142007


Caution






Shell Used Command


export TEMP





Note





12142007 PUBLIC 99148


Note


Recommendation




More Information






Note






100148 PUBLIC 12142007


n Standard System













12142007 PUBLIC 101148


n






















102148 PUBLIC 12142007















12142007 PUBLIC 103148


5 Post-Installation

5 Post-Installation




Note



Note



5




12142007 PUBLIC 105148














Prerequisites




Note


106148 PUBLIC 12142007


Example



Administrator



Caution







Procedure


12142007 PUBLIC 107148





System





Caution


Caution



108148 PUBLIC 12142007




Procedure







Note





12142007 PUBLIC 109148






Procedure








110148 PUBLIC 12142007








n SQL Studio (GUI)


Prerequisites





Windows 2000 Any

Windows 2003 Any


l 64 MB RAM




12142007 PUBLIC 111148


Caution


IndepDataPath


IndepProgPath

Procedure









Note





112148 PUBLIC 12142007


Caution









Caution



Procedure


12142007 PUBLIC 113148


Note



Example



file into it

Example







114148 PUBLIC 12142007




Note








12142007 PUBLIC 115148


Example



















Note


116148 PUBLIC 12142007




Prerequisites




Procedure




Procedure





12142007 PUBLIC 117148


Recommendation


Caution












118148 PUBLIC 12142007


Host Agent User



Note




















12142007 PUBLIC 119148













Procedure



120148 PUBLIC 12142007


Note







Procedure



Manual Contents









12142007 PUBLIC 121148


Manual Contents














122148 PUBLIC 12142007




Caution




l usrsapltSAPSIDgt




Note


Prerequisites








12142007 PUBLIC 123148


Caution





124148 PUBLIC 12142007





n






Note





Example



ioscan -fnkCdisk


12142007 PUBLIC 125148






Example






ltmedium-mountdirgt

Example





n usrsbinsmh



ltmedium-mountdirgt

Example


126148 PUBLIC 12142007











Option Definition




12142007 PUBLIC 127148


Note




Caution



Note



sapinst

Example


sapinst


Note



128148 PUBLIC 12142007







Prerequisites



Procedure


Caution




sapinst -nogui

12142007 PUBLIC 129148


Example


sapinst -nogui




Caution




sapinst -nogui








130148 PUBLIC 12142007





Note



Note






Caution



Note



12142007 PUBLIC 131148



Note



Note






sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note


132148 PUBLIC 12142007





Procedure








Note







12142007 PUBLIC 133148


Procedure















Note



Prerequisites


134148 PUBLIC 12142007





Example



Note







Note





12142007 PUBLIC 135148





Note







Prerequisites




Note


3 Choose Finish

136148 PUBLIC 12142007





Note










12142007 PUBLIC 137148


Prerequisites





Caution




Note


n



Procedure




138148 PUBLIC 12142007


Note






Note



startdb




Note



Note






12142007 PUBLIC 139148


Note



Note





Note




stopsap DB


Note







140148 PUBLIC 12142007


stopdb


Note







Note


Caution





Procedure


12142007 PUBLIC 141148






Caution



Prerequisites




Procedure



Note


142148 PUBLIC 12142007





Caution




Note



12142007 PUBLIC 143148


Example Description














144148 PUBLIC 12142007



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom






12142007 PUBLIC 145148













146148 PUBLIC 12142007













12142007 PUBLIC 147148




n





12 New Features


Caution



Area Description







8148 PUBLIC 12142007


Area Description
















12142007 PUBLIC 9148


Operating Systems

Area Description



Documentation

Area Description
















10148 PUBLIC 12142007








Documentation














12142007 PUBLIC 11148









General Quick Links
























12148 PUBLIC 12142007












Terminology


Variables











12142007 PUBLIC 13148






Example


14148 PUBLIC 12142007

2 Planning

2 Planning








4











12142007 PUBLIC 15148


n





211 Standard System







16148 PUBLIC 12142007



Note









12142007 PUBLIC 17148




End of HA (UNIX)






18148 PUBLIC 12142007











12142007 PUBLIC 19148









20148 PUBLIC 12142007







12142007 PUBLIC 21148


Figure 7 Host Agent




Note


More Information





22148 PUBLIC 12142007






12142007 PUBLIC 23148






usrsap

ltDRIVEgtsapdb









24148 PUBLIC 12142007



Security Issues


Caution


Recommendation



Caution







Performance Issues




12142007 PUBLIC 25148






Figure 9




26148 PUBLIC 12142007






Note





12142007 PUBLIC 27148


Caution









SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

28148 PUBLIC 12142007







SAP MMC


SAP MC


12142007 PUBLIC 29148










Note







30148 PUBLIC 12142007





Recommendation







12142007 PUBLIC 31148







Note



32148 PUBLIC 12142007




12142007 PUBLIC 33148


3 Preparation

3 Preparation




Note







7



8




12142007 PUBLIC 35148

3 Preparation



















36148 PUBLIC 12142007












USR VAR




12142007 PUBLIC 37148






UID USR VAR











38148 PUBLIC 12142007










Master Password




12142007 PUBLIC 39148















40148 PUBLIC 12142007



















12142007 PUBLIC 41148





Host Agent












volumes

42148 PUBLIC 12142007










Note






Recommendation




12142007 PUBLIC 43148










Process Flow


Caution



Note




44148 PUBLIC 12142007






Recommendation


Note


Prerequisites


Procedure



Note





12142007 PUBLIC 45148













|grep Total







46148 PUBLIC 12142007
















See SAP Note 837670



libldapssl41so



Other Requirements






12142007 PUBLIC 47148










Minimum RAM 2 GB












Note


48148 PUBLIC 12142007









Minimum RAM 1 GB














12142007 PUBLIC 49148







RAM 1 GB

















50148 PUBLIC 12142007



Minimum RAM 1 GB




















Minimum RAM 1 GB


12142007 PUBLIC 51148









Note







Minimum RAM 1 GB






End of HA (UNIX)

52148 PUBLIC 12142007













RAM 1 GB










12142007 PUBLIC 53148









Minimum RAM 1 GB












54148 PUBLIC 12142007







Minimum RAM 1 GB














Minimum RAM 05 GB


12142007 PUBLIC 55148








Caution



Caution










56148 PUBLIC 12142007




n kcweb(1M)

n kcusage(1M)

n kcalarm(1M)






as often




n usrsbinsmh



12142007 PUBLIC 57148






Recommendation






Total



Example

usrsbinswapinfo -dm

Mb Mb Mb PCT Mb


dev 10000 82 9918 1 0 - 1 devvg00lvol2

dev 20000 83 19917 0 0 - 1 devvg01lvol9





58148 PUBLIC 12142007














Note



Note




cd ltINSTDIRgt



12142007 PUBLIC 59148







Procedure



Note





60148 PUBLIC 12142007


Recommendation


Caution







Caution


Caution


Caution



User Primary Group


sqdltdbsidgt sapsys

sdb sdba

12142007 PUBLIC 61148



User Primary Group


Caution


Caution


Groups and Members

Groups Members




User Primary Group




Note







62148 PUBLIC 12142007


usrsbinsam


etcTIMEZONE

etcprofile

etccshlogin



n usrsbinsmh



etcTIMEZONE

etcprofile

etccshlogin




12142007 PUBLIC 63148











Recommendation



Prerequisites





Note





64148 PUBLIC 12142007


Recommendation




Recommendation


Caution



Recommendation



Caution




12142007 PUBLIC 65148




Recommendation



Recommendation


Note








Note



66148 PUBLIC 12142007



361 SAP Directories








12142007 PUBLIC 67148



l global


l profile


l exe









Local Directories


68148 PUBLIC 12142007


n SYS

Note




l







MaxDB Directories







sapdb MaxDBsoftware


12142007 PUBLIC 69148







n work


70 MB





Procedure


Note



70148 PUBLIC 12142007





Note



Example


12142007 PUBLIC 71148


your HA partner

Figure 13

End of HA (UNIX)






72148 PUBLIC 12142007


Procedure






n usrsaptrans


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt



12142007 PUBLIC 73148




sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt


sapmntltSIDgt

End of HA (UNIX)



Note






Note



74148 PUBLIC 12142007



Example



Example




Note



Note










12142007 PUBLIC 75148





Note









Note


Note


Note



Note



76148 PUBLIC 12142007


usrsbinsam










ioscan -m lun




12142007 PUBLIC 77148


Note




Example



Example




Example



Example




Note




78148 PUBLIC 12142007


Note


















Note




12142007 PUBLIC 79148






Example


Note


Note





n usrsbinsmh







80148 PUBLIC 12142007










Infrastructure




12142007 PUBLIC 81148






Note













82148 PUBLIC 12142007


Example

sapmntC11


4 Type OK5 Exit SAM










n usrsbinsmh




Example

sapmntCUS


12142007 PUBLIC 83148


8 Exit SMH









Example





Note





84148 PUBLIC 12142007


Example



Example

mount -a





Example


Note





Note





12142007 PUBLIC 85148


Example



Example

mount -a



Prerequisites



Procedure






86148 PUBLIC 12142007









this section


Note






12142007 PUBLIC 87148









Note




Caution





88148 PUBLIC 12142007



Note


Caution





Example

51031387_151031387_2




Note


12142007 PUBLIC 89148





Procedure




Example


90148 PUBLIC 12142007

4 Installation

4 Installation
















12142007 PUBLIC 91148

4 Installation










Note










92148 PUBLIC 12142007

4 Installation

















12142007 PUBLIC 93148







Procedure












94148 PUBLIC 12142007




43 Running SAPinst




Recommendation




Caution


12142007 PUBLIC 95148






Using SAPinst GUI








96148 PUBLIC 12142007









Prerequisites




Shell Used Command


export DISPLAY





12142007 PUBLIC 97148


Procedure


Caution





sapinst

Example


sapinst


Note


End of HA (UNIX)

98148 PUBLIC 12142007


Caution






Shell Used Command


export TEMP





Note





12142007 PUBLIC 99148


Note


Recommendation




More Information






Note






100148 PUBLIC 12142007


n Standard System













12142007 PUBLIC 101148


n






















102148 PUBLIC 12142007















12142007 PUBLIC 103148


5 Post-Installation

5 Post-Installation




Note



Note



5




12142007 PUBLIC 105148














Prerequisites




Note


106148 PUBLIC 12142007


Example



Administrator



Caution







Procedure


12142007 PUBLIC 107148





System





Caution


Caution



108148 PUBLIC 12142007




Procedure







Note





12142007 PUBLIC 109148






Procedure








110148 PUBLIC 12142007








n SQL Studio (GUI)


Prerequisites





Windows 2000 Any

Windows 2003 Any


l 64 MB RAM




12142007 PUBLIC 111148


Caution


IndepDataPath


IndepProgPath

Procedure









Note





112148 PUBLIC 12142007


Caution









Caution



Procedure


12142007 PUBLIC 113148


Note



Example



file into it

Example







114148 PUBLIC 12142007




Note








12142007 PUBLIC 115148


Example



















Note


116148 PUBLIC 12142007




Prerequisites




Procedure




Procedure





12142007 PUBLIC 117148


Recommendation


Caution












118148 PUBLIC 12142007


Host Agent User



Note




















12142007 PUBLIC 119148













Procedure



120148 PUBLIC 12142007


Note







Procedure



Manual Contents









12142007 PUBLIC 121148


Manual Contents














122148 PUBLIC 12142007




Caution




l usrsapltSAPSIDgt




Note


Prerequisites








12142007 PUBLIC 123148


Caution





124148 PUBLIC 12142007





n






Note





Example



ioscan -fnkCdisk


12142007 PUBLIC 125148






Example






ltmedium-mountdirgt

Example





n usrsbinsmh



ltmedium-mountdirgt

Example


126148 PUBLIC 12142007











Option Definition




12142007 PUBLIC 127148


Note




Caution



Note



sapinst

Example


sapinst


Note



128148 PUBLIC 12142007







Prerequisites



Procedure


Caution




sapinst -nogui

12142007 PUBLIC 129148


Example


sapinst -nogui




Caution




sapinst -nogui








130148 PUBLIC 12142007





Note



Note






Caution



Note



12142007 PUBLIC 131148



Note



Note






sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note


132148 PUBLIC 12142007





Procedure








Note







12142007 PUBLIC 133148


Procedure















Note



Prerequisites


134148 PUBLIC 12142007





Example



Note







Note





12142007 PUBLIC 135148





Note







Prerequisites




Note


3 Choose Finish

136148 PUBLIC 12142007





Note










12142007 PUBLIC 137148


Prerequisites





Caution




Note


n



Procedure




138148 PUBLIC 12142007


Note






Note



startdb




Note



Note






12142007 PUBLIC 139148


Note



Note





Note




stopsap DB


Note







140148 PUBLIC 12142007


stopdb


Note







Note


Caution





Procedure


12142007 PUBLIC 141148






Caution



Prerequisites




Procedure



Note


142148 PUBLIC 12142007





Caution




Note



12142007 PUBLIC 143148


Example Description














144148 PUBLIC 12142007



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom






12142007 PUBLIC 145148













146148 PUBLIC 12142007













12142007 PUBLIC 147148



adaptivecomputing controller 7.1 on hp-ux:maxdb

Documents