SAP NetWeaver 7.0 SR3ABAP+JavaonAIX :Oracle... SAP Components SAPSolutionManager Release4.0 ConfigurationGuide‒SAPSolution Manager4.0asof PatchingofSAP NetWeaver7.0scenarios

PUBLIC

Installation Guide

SAP NetWeaver 70SR3 ABAP+Java on AIX OracleIncluding the following

SAP NetWeaver ABAP Application Server (AS ABAP)

SAP NetWeaver Java Application Server (AS Java)

SAP NetWeaver Business Intelligence Java Components (BI Java)

SAP NetWeaver Development Infrastructure (DI)

SAP NetWeaver EP Core (EPC)

SAP NetWeaver Enterprise Portal (EP)

SAP NetWeaver Mobile Infrastructure (MI)

SAP NetWeaver Process Integration (PI)

Target Audience

n Technology consultants

n System administrators

Document version 100 ‒ 03282008

Document History

Caution

Before you start the implementation make sure you have the latest version of this document Youcan find the latest version on SAP Service Marketplace httpservicesapcominstguides

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

Version Date Description

100 3282008 Initial Version

2198 PUBLIC 03282008

Table of Contents

Chapter 1 Introduction 711 New Features 912 SAP Notes for the Installation 1213 Online Information from SAP 1314 Naming Conventions 16

Chapter 2 Planning 1721 Basic System Variants 1722 How to Distribute Instances to Hosts 2023 Production Client Considerations 2324 SAP System Transport Host 2425 Basic SAP System Parameters 2426 Running Adobe Document Services on Nonsupported Platforms 3827 High Availability Planning the Switchover Cluster 38

Chapter 3 Preparation 4331 High Availability Switchover Preparations 44311 Preparing for Switchover 44312 Setting Up File Systems for a High-Availability System 46313 Configuring Network File System 4732 Hardware and Software Requirements 49321 Running the Prerequisite Checker in Standalone Mode (Optional) 50322 Requirements for AIX 51323 Requirements for a Central System 54324 Requirements for a Distributed or a High Availability System 563241 Requirements for the Central Services Instance 563242 Requirements for the Central Instance 573243 Requirements for the Database Instance 57325 Requirements for a Dialog Instance 60326 Checking and Modifying the AIX Kernel 60327 Setting up Swap Space for AIX 6233 Creating Operating System Users 62331 Network Information Service 62332 Creating Operating System Users and Groups 63333 Creating AIX Groups and Users (Optional) 64

03282008 PUBLIC 3198

34 Setting Up File Systems and Raw Devices 66341 SAP Directories 66342 Oracle Directories 73343 Setting Up File Systems and Raw Devices for AIX 7635 Exporting and Mounting the Global Transport Directory 7736 Exporting and Mounting Directories via NFS for AIX (Optional) 7837 Installing the Front-End Software 7938 Generating the SAP Solution Manager Key 8039 Installing the Java Development Kit 80310 Preparing and Mounting the Installation Media 823101 Preparing the Installation DVDs 823102 Downloading Installation DVDs from SAP Service Marketplace (Optional) 843103 Mounting a CD DVD for AIX 85

Chapter 4 Installation 8741 Performing a High-Availability Installation 8742 Prerequisites before Starting SAPinst 89421 Prerequisites before Starting SAPinst All Instances 89422 Prerequisites before Starting SAPinst Distributed Instances 92423 Prerequisites Before Starting SAPinst High Availability 9343 Installing an SAP System Using SAPinst 93431 Running SAPinst on UNIX 94432 Installing the Java Add-In for an Existing ABAP System (Optional) 101433 Using SAPinst GUI 103434 Interrupted Installation with SAPinst 104435 Performing a Remote Installation with SAPinst (Optional) 105436 Starting SAPinst GUI Separately (Optional) 106437 Entries in the Services File Created by SAPinst 10844 Oracle Database Software Installation 108441 Updating SAP-Specific Files in the Oracle Staging Area 109442 Performing Steps for the AIX Operating System 109443 Running the Oracle Universal Installer 110444 Installing the Current Patch Set 112445 Installing Required Interim Patches 112

Chapter 5 Post-Installation 11551 Updating Database Statistics 11752 Logging On to the Application Server 11753 Logging on to the Portal 11954 Logging on to SAP NetWeaver Development Infrastructure (NWDI) 12055 Installing the SAP License 12156 Installing the SAP Online Documentation 122

4198 PUBLIC 03282008

57 Configuring Remote Connection to SAP Support 12258 Applying the Latest Kernel and Support Packages 12359 Performing Initial ABAP Configuration 125510 Performing Oracle-Specific Post-Installation Steps 127511 Performing the Client Copy 128512 Performing a Full Installation Backup 129513 Post-Installation Steps for Adobe Document Services 1305131 Assigning Roles to Users ADSUSER and ADS_AGENT 1315132 Checking the IIOP Service and the Startup Properties 1315133 Installation Check and Quick Tests for Adobe Document Services 132514 Setting Environment Variable CPIC_MAX_CONV 133515 Post-Installation Steps for Usage Type Process Integration (PI) 1335151 Performing PI-Specific Steps for SLD Configuration 133516 Post-Installation Steps for the Application Sharing Server 134517 High Availability Post-Installation Steps 1345171 Setting Up Licenses 1345172 Taking Precautions for Transport 135518 Ensuring User Security 136519 Running the Configuration Wizard 142520 Checking the SAP Java Documentation 144521 Accessing Configuration Documentation in SAP Solution Manager 145522 Post-Installation Steps for the Diagnostics Agent 147

Chapter 6 Additional Information 14961 Installation of Multiple Components in One Database (Optional) 14962 Integration of LDAP Directory Services (Optional) 15163 Installation of Additional Software Units or Usage Types in an Existing SAP

System 15564 Starting and Stopping SAP System Instances 161641 Starting and Stopping SAP System Instances Using the SAP Management

Console 161642 Starting and Stopping SAP System Instances Using Scripts 165643 Starting and Stopping the Diagnostics Agent Using Scripts 16865 Creating a User for LDAP Directory Access (Optional) 16966 Configuring User Management to Use an LDAP Directory (Optional) 17067 Usage Type-Specific Initial Technical Configuration 170671 Initial Technical Configuration for the Application Server Java (AS Java) 1716711 Initial Technical Configuration for Adobe Document Services 1716712 Initial Technical Configuration for Composite Application Framework Core

(CAF) 1726713 Initial Technical Configuration for the System Landscape Directory (SLD) 173672 Initial Technical Configuration for Development Infrastructure (DI) 173

03282008 PUBLIC 5198

673 Initial Technical Configuration for the Portal (Usage Types EPC and EP) 175674 Initial Technical Configuration for Process Integration (PI) 1766741 Importing the SAP Exchange Profile 1766742 Assigning SAP_ALL Rights to User PISUPER 1776743 Activating the ICF Services 1786744 Assigning Roles to Groups 178675 Initial Technical Configuration for BI Java 1796751 Configuring BI Java Information Broadcasting 1796752 Process Chains Transporting Texts for the Alert Category 1806753 Renaming initialPermissionsBIxmltemplate 18068 Heterogeneous SAP System Installation 18069 Troubleshooting 181691 Troubleshooting with SAPinst 181692 Troubleshooting for Portal Installation 182610 Deleting an SAP System 1826101 Deleting an SAP System Using SAPinst 18361011 Running SAPinst to Delete an SAP System 18461012 Deleting the Oracle Database Software 1856102 Deleting an SAP SystemManually 18561021 Deleting an SAP Instance 18661022 Deleting Installation Files Directories and Users on a Host 18761023 Deleting the Java Part of an SAP System 18861024 Deleting the Oracle Database Java Schema 19061025 Deleting an Oracle Database Instance 191

6198 PUBLIC 03282008

1 Introduction

1 Introduction

This document explains how to install SAP NetWeaver 70 Support Release 3 (SR3) ABAP+JavaIt also explains how to install the Java Add-In for an existing SAP NetWeaver 70 SR3 ABAP systemSAP NetWeaver 70 Support Release 3 corresponds to SAP NetWeaver 70 Support Package Stack(SPS) 14For more information about the SAP NetWeaver technology seehttpsdnsapcomirjsdnnetweaverYou can install SAP NetWeaver 70 SR3 ABAP+Java with the following usage types in a singleinstallation run using SAPinst

n

Only valid for Application Server (AS)

SAP NetWeaver Application Server ABAP (AS ABAP)

Note

AS ABAP is not installed with the Java Add-In

End of Application Server (AS)

n SAP NetWeaver Application Server Java (AS Java)

n

Only valid for Development Infrastructure (DI)

SAP NetWeaver Development Infrastructure (DI)End of Development Infrastructure (DI)

n

Only valid for EP Core (EPC)

SAP NetWeaver EP Core (EPC)End of EP Core (EPC)

n

Only valid for Enterprise Portal (EP)

SAP NetWeaver Enterprise Portal (EP)If you install usage type EP note the followingl You must install SAP NetWeaver Application Server Java (AS Java) and EP Core (EPC)l The Application Sharing Server is installed automatically with usage type EP For production

use we recommend that you install the server as an optional standalone unit on a dedicatedhost as described in the documentation Installation Guide ‒ ltyour productgt Java on ltOSgtltDatabasegt

End of Enterprise Portal (EP)

03282008 PUBLIC 7198

1 Introduction

n

Only valid for BI Java

SAP NetWeaver Business Intelligence Java Components (BI Java)You also have to install SAP NetWeaver Application Server Java (AS Java) EP Core (EPC) andSAP NetWeaver Portal (EP)End of BI Java

n

Only valid for Mobile Infrastructure (MI)

SAP NetWeaver Mobile Infrastructure (MI)End of Mobile Infrastructure (MI)

n

Only valid for Process Integration (PI)

SAP NetWeaver Process Integration (PI)End of Process Integration (PI)

For more information about the usage types of SAP NetWeaver and their interdependencies seethe documentMaster Guide ‒ SAP NetWeaver 70 at httpservicesapcominstguidesNW70 Forrestrictions see SAP Note 852008

Installation of Additional Software Units or Usage Types in an Existing SAP System

If you want to install additional Java software units or usage types in an existing SAP system based onSAP NetWeaver 70 SR3 (Support Package Stack (SPS) 14) you have to use the Java Support PackageManager (JSPM) You cannot use SAPinst to install additional software units or usage types in anexisting SAP system ldquoExisting SAP systemrdquo means that it has at least AS JavaAs of SAP NetWeaver 70 SPS 12 you can use Install Additional Usage Types in JSPM to install and activateadditional software units or usage typesFor more information see Installation of Additional Software Units or Usage Types in an Existing SAP System[page 155]


Caution

You cannot install PI as an additional UT with the procedure described in SAP Note 852008 You canonly install an SAP system with PI as a new installation

End of Process Integration (PI)

Constraints

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

n Your operating system platform must be 64-bitn The database must be Oracle 10202 or highern Youmust only use the SAP installation tools according to the instructions and for the purposes

described in the SAP installation document Improper use of the SAP installation tools can damagefiles and systems already installed

8198 PUBLIC 03282008

1 Introduction11 New Features

n SAP system installations should only be performed by SAP Technical Consultants certified foryour 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 an 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 New Features

The following tables provide an overview of the new features related to the installation of this release

Caution

Make sure that you read the release notes for your SAP system You can find these athttpservicesapcomreleasenotes

SAP System Installation

Area Description

SAPinst As of SAP NetWeaver 70 SAPinst has the following new featuresn You can check the prerequisites for your SAP system installation with the

Prerequisite Checker [page 50]n You can install a central system in one of two modesl Typical Mode

If you choose Typical your SAP system is installed with default settings Asa result you only have to respond to a small selection of prompts If youwant to change any of the default settings you can do so on the parametersummary screen at the end of the installation

l Custom ModeIf you choose Custom you must manually enter all installation parametersYou can change your values on the parameter summary screen at the end ofthe installation

n You can uninstall an SAP system or an SAP component with the SAPinst serviceUninstall ‒ System Standalone Engines Optional Standalone Unit

n You can install the Java Add-In for an existing ABAP system This means that yourun SAPinst to execute the followingl Install the central services instance (SCS)l Add the Java database schema to the existing ABAP database instancel Add the Java central instance with usage types to the existing ABAP central

instance

03282008 PUBLIC 9198


Area Description

The installation of the Java Add-In for an existing ABAP system is described in thedocumentation Installation Guide ‒ ltyour productgt ABAP+Java on ltOSgt ltDatabasegtavailable at httpservicesapcominstguides

NoteYou cannot install the Java Add-In for existing ABAP dialog instance(s) Insteadyou have to install new ABAP+Java dialog instance(s)

n The sapinst group ID must be the secondary group of the users root andltsapsidgtadm For more information see Creating Operating System Users and GroupsManually [page 63]

n You can install SAP NetWeaver as a high-availability (HA) systemn You can change the default names of the Java users J2EE_ADMIN J2EE_GUEST and

SAPJSF during the input phase of the installationn You assign one master password to all users created by SAPinst This password is

used for all user accounts and for the secure store key phrasen SAPinst fills in most of the input parameter fields with default values

If required you can change the default values on the Parameter Summary screenbefore you start the actual installation

n You no longer have to manually activate sapcpeThe kernel is replicated automatically fromusrsapltSAPSIDgtSYSexerunDIR_CT_RUN tousrsapltSAPSIDgtltINSTANCEgtexeDIR_EXECUTABLE for eachSAP system instanceFor more information see Setting Up File Systems [page 66]

Installation DVDs You start the installation from a single Installation Master DVD

SAP Solution ManagerKey

You require a key to install your SAP system You generate this key with your SAP SolutionManager [page 80]

SAP NetWeaverAdministrator

SAP NetWeaver Administrator is a brand new solution for monitoring andadministering Java systems and their applicationsFor more information see the SAP NetWeaver Master Guide and the followinghttpwwwsdnsapcomirjsdnnetweaver Lifecycle Management Operations

Knowledge Center Administration

SAP Solution ManagerDiagnostics Agent

A SAP Solution Manager Diagnostics Agent (Diagnostics Agent) is a standaloneJava program that runs on each of the systems managed by SAP Solution ManagerDiagnostics It gathers information and reports to the SAP SolutionManager systemFor more information about the Diagnostics Agent seehttpservicesapcomdiagnostics

The installation of the Diagnostics Agent is now part of the InstallationMaster DVDThat is you can choose between the following optionsn If there is no Diagnostics Agent already installed on this physical or virtual host

it is installed automatically with an AS Java central instance and dialog instancen You can install it as a standalone engine

10198 PUBLIC 03282008


Area Description

64-bit support for allinstances except dialoginstances

If you want to use 32-bit SAP NetWeaver components first check whether thesecomponents can run on 64-bit operating systems If so we recommend that youuse 64-bit systemsIf not you can install an SAP dialog instance on 32-bit operating systems to runthese components For all other SAP instances you must use 64-bit systems

Only Unicode supportfor new installations

Every newly installed SAP system is a Unicode systemHowever non-Unicode is still supported for copied and upgraded systems

MaintenanceOptimizer

All downloadable software components based on SAP NetWeaver 70 and subsequentversions released after April 2 2007 are available exclusively through theMaintenance Optimizer in SAP Solution Manager This comprisesn Support Package Stacks Support Packages and patches for Java instances except

for kernel patchesn Legal changesn SAP applications and versions that arel Mandatory for SAP NetWeaver 70 (and subsequent versions) and all

applications based on this software including SAP Business Suite 2005 (andsubsequent versions)

l Optional for all SAP applicationsFor more information see httpservicesapcomsolman-mopz

Operating Systems and Platforms

Area Description

Support of OperatingSystems and Platforms

n For supported operating system and database releases see the Product AvailabilityMatrix at httpservicesapcompam

n For forums blogs content and community related to all of the supporteddatabases and operating systems see the Database and Operating Systems area athttpsdnsapcomirjsdndbos

Oracle Database

New functions inOracle Database 10g

n As of the installation of SAP NetWeaver 70 and SAP Business Suite 2005 newfunctions of the Oracle Database 10g release are usedFor more information about the integration of Oracle 10g in the SAPenvironment see SAP Note 720886

n For the complete list of new features see further documentation from Oraclewhich you can find athttpwwworaclecomtechnologyproductsdatabaseoracle10g

03282008 PUBLIC 11198

1 Introduction12 SAP Notes for the Installation

Documentation

Area Description

Installation of AdditionalSoftware Units or Usage Types

The documentation on how to install additional software units or usagetypes to an existing SAP system is now included in the installation guides Upto now this documentation was only available in SAP Note 883948

Application Sharing ServerInstallation

The installation of Application Sharing Server is part of the Java installationguide for your product available at httpservicesapcominstguides

ltchoose your productgt

SAP Notes You can now access SAP Notes directly in SAP Service Marketplace fromyour PDF Place the cursor on the SAP Note ltnumbergt and double-click Aseparate browser window opens to display the SAP Note

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

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

corresponding internet page

12 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 athttpservicesapcomnotes

SAP Notes for the Installation

SAP Note Number Title Description

1052298 SAP NetWeaver 70 SR3 BusinessSuite 2005 SR3 ‒ UNIX

UNIX-specific information about the SAP systemand corrections to this documentation

852008 Release Restrictions for SAPNetWeaver 70

Customer information on restrictions in theproduction use of certain functions

1094599 SAP NetWeaver 70 SR3 BusinessSuite 2005 SR3 ‒ UNIX Oracle

Oracle-specific information about the SAPsystem installation and corrections to thisdocumentation

828268 Oracle 10g New functions Information about new Oracle features releasedfor the SAP system

98252 Installing two Oracle databaseson a host

This SAP Note is only required if you plan toinstall more than one Oracle database on thesame host

855498 Installation Prerequisite Checker SAP Software on UNIX Windows and System iChecking OS Dependencies

12198 PUBLIC 03282008

1 Introduction13 Online Information from SAP


73606 Supported Languages and CodePages

Information on possible languages and languagecombinations in SAP systems

737368 Hardware requirements of JavaDevelopment Infrastructure

Information on the hardware requirements forusage type Development Infrastructure (DI)which depends on the size of your developmentteam

937693 SAP Mobile Infrastructure 70 ‒Release Note to MAXDB

This note contains additional information aboutSAP Mobile Infrastructure installation 70 for allsupport package stacks

1067221 Central Note for HeterogeneousInstallation

Heterogeneous ABAP system landscapes ondifferent operating systems have been releasedfor some time Heterogeneous Java systemlandscapes on different operating systems havenow also been released However not everycombination of operating system and databasesystem is released This SAP Note and its relatedSAP Notes describe the released operating systemand database combinations

1152408 Installing SAP Systems into anIndependent ASP (iASP)

Information on features and limitations forinstallations into independent ASP

13 Online Information from SAP

More information is available online as follows

Documentation

Description Internet Address Title

Master Guide for SAPNetWeaver 70

httpservicesapcominstallNW70 Master Guide ‒ SAP NetWeaver 70

Technical InfrastructureGuide for SAP NetWeaver70

httpservicesapcominstallNW70 Technical Infrastructure Guide ‒ SAPNetWeaver 70

Master Guide SAPSolution Manager 40

httpservicesapcominstguides SAPComponents SAP Solution Manager Release 40

Master Guide ‒ SAP SolutionManager 40

List of media forinstallation or upgradefor SAP NetWeaver 70

httpservicesapcominstallNW70 Media List ‒ SAP NetWeaver 70

Installation of SAPSolution Manager 40


Installation Guide ‒ SAP SolutionManager 40 onltOSgt ltDatabasegt

03282008 PUBLIC 13198



Configuration of SAPSolution Manager 40


Configuration Guide ‒ SAP SolutionManager 40 as of ltcurrent stackgt

Patching of SAPNetWeaver 70 scenarios

httpservicesapcommaintenanceNW70

SPS ltcurrent stackgt Support Package Stack Guide ‒SPS ltcurrent stackgt

Support Package Stack Guide ‒ SAPNetWeaver 70 SPS ltcurrent stackgt

Upgrade to SAPNetWeaver 70

httpservicesapcomupgradenw70

Installation Upgrade to SAP NetWeaver SystemsUpgrade Documentation - SAP NetWeaver 70 ltSRgt

Component Upgrade Guide ‒ SAPNetWeaver 70 Application ServerABAP

Installation of SAPNetWeaver DeveloperWorkplace

httpservicesapcominstallNW70

Installation Installation mdash Clients Installation ‒SAP Developer Workplace

Installation Guide ‒ DeveloperWorkplace for SAP NetWeaver

Installation of SAPNetWeaver DeveloperStudio


Installation Installation mdash Clients Installation ‒SAP NetWeaver Developer Studio

SAP NetWeaver Developer Studio mdashStandalone Installation Guide

Installation of the SystemLandscapeDirectory (SLD)


Configuration Post-Installation Guide ‒ SLD of SAPNetWeaver 70

Post-Installation Guide ‒ SystemLandscape Directory of SAPNetWeaver 70

Installationof a standalonegateway


Installation ‒ Standalone Engines Installation mdashGateway on ltplatformgt

Installation Guide ‒ Gateway onltplatformgt ‒ For SAP Systems Basedon SAP NetWeaver 70 (2004s)

Installation of WebDispatcher


Installation ‒ Standalone Engines Installation mdashWebDispatcher on ltplatformgt

Installation Guide ‒ Web Dispatcheron ltplatformgt ‒ For SAP SystemsBased on SAP NetWeaver 70 (2004s)

Front End installation httpservicesapcominstallNW70

Installation ‒ Clients Installation ‒ SAP Front EndltReleasegt

SAP Front End Installation GuideThis guide is also available onthe Presentation DVD

Homogeneous andheterogeneous systemcopy for SAP systems basedon NetWeaver 70


Installation ‒ SAP NetWeaver Systems System Copyfor SAP Systems Based on ltReleasegt ltTechnologygt

System Copy GuidemdashSystem Copy forSAP Systems based on SAPNetWeaverltReleasegt ltTechnologygt

SAP NetWeaver ProblemAnalysis Guide

httphelpsapcomnw70 SAP NetWeaver70 Library ‒ English SAP NetWeaver Library SAPNetWeaver by Key Capability Solution Life CycleManagement by Key Capability SAP NetWeaverProblem Analysis Guide (PAG)

SAP NetWeaver Problem AnalysisGuide (PAG)

General Quick Links

Description Internet Address

SAP Help Portal httphelpsapcom

SAP NetWeaver Library in SAPHelp Portal

httphelpsapcomnw70

14198 PUBLIC 03282008



SAP Notes httpservicesapcomnotes

SAP Notes for SAP NetWeaver 70installation

httpservicesapcomsapnotesnw70

Forums blogs and generalinformation related to all ofthe supported databases andoperating system platforms

httpsdnsapcomirjsdndbos

Product AvailabilityMatrix (PAM)for supported operating systemreleases

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

High Availability httpsdnsapcomirjsdnha

System Landscape Directory httpsdnsapcomirjsdnnw-sld

Software logistics for SAPNetWeaver

httpsdnsapcomirjsdnsoftwarelogistics

SAP NetWeaver operations httpsdnsapcomirjsdnoperations

SAP NetWeaver DevelopmentInfrastructure

httpsdnsapcomirjsdnnw-di

Security for SAP NetWeaver httpsdnsapcomirjsdnsecurity

Information on SAP SupportPackage Stacks

httpservicesapcomsp-stacks

SAP Solution Manager httpservicesapcomsolutionmanager

Maintenance Optimizer httpservicesapcomsolman-mopz

End-to-End Root Cause Analysis httpservicesapcomdiagnostics

03282008 PUBLIC 15198

1 Introduction14 Naming Conventions

14 Naming Conventions

In this documentation the following naming conventions apply

Terminology

n SAP system refers to SAP NetWeaver 70 SR3n ABAP+Java system refers to SAP NetWeaver 70 SR3 ABAP+Javan Java Add-In refers to the Java Add-In for an existing SAP NetWeaver 70 SR3 ABAP systemn Diagnostics Agent refers to SAP Solution Manager Diagnostics Agent

Variables

Variables Description

ltSAPSIDgt SAP system ID in uppercase letters

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

ltOSgt Operating system name within a path

ltSCHEMA_IDgt 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 directoryusrsapC11

16198 PUBLIC 03282008

2 Planning

2 Planning

This section tells you how to plan the installation of your SAP systemYou have to complete the following planning activities

1 You plan your SAP system landscape according to theMaster Guide and the Technical InfrastructureGuide available for your product

2 You choose your basic system variant [page 17]3 You plan how to distribute the instances to hosts [page 20]4 You decide on your production client [page 23]5 You decide on the transport host to use [page 24]6 You identify basic SAP system parameters [page 24]7 If you want to use Adobe Document Services (ADS) you check what you have to do in case your platform is

not supported for ADS [page 38]

8

Only valid for HA (UNIX)

You plan the switchover cluster [page 38] for a high-availability (HA) systemEnd of HA (UNIX)

The following planning activity is optional

n Installation of Multiple Components in One Database (MCOD) [page 149]

Caution

This step does not apply to the installation of a Java Add-In to an existing ABAP system

21 Basic System Variants

The following section provides information about the basic system variants for an ABAP+Java systemand how to distribute SAP instances within themAn ABAP+Java system can be the result either of an ABAP+Java installation or of the installation of aJava Add-In to an existing ABAP system

03282008 PUBLIC 17198

2 Planning21 Basic System Variants

Note

If you want to use 32-bit SAP NetWeaver components first check whether these components can runon 64-bit operating systems If so we recommend you to use 64-bit systems If not you can installan SAP dialog instance on 32-bit operating systems to run these components For all other SAPinstances you must use 64-bit systems

Mandatory instances of an ABAP+Java system are the central instance the central services instanceand the database instance

Note

The Java central services instance is called SCS instanceThe ABAP central services instance is called ASCS instance The ASCS is only required for ahigh-availability installation

You can then operate both the ABAP application server and the J2EE Engine on the SAP systemOptionally you can install one or more dialog instances if required

Caution

Note the following about dialog instances

n We do not support operating an ABAP dialog instance with an ABAP+Java system

n You cannot install the Java Add-In for existing ABAP dialog instance(s) Instead you have toinstall new ABAP+Java dialog instance(s)

Note

Each instance can reside on a separate host The ASCS and the SCS must reside on the same host

18198 PUBLIC 03282008


Figure 1 Minimum System Distribution (Central System)

For a minimum system distribution all instances reside on one host

Figure 2 Maximum Distribution for a Distributed System

For a maximum system distribution each instance resides on a separate host

03282008 PUBLIC 19198

2 Planning22 How to Distribute Instances to Hosts


Figure 3 Maximum Distribution for a High-Availability System

End of HA (UNIX)


For a maximum system distribution each instance resides on a separate hostEnd of HA (UNIX)

22 How to Distribute Instances to Hosts

The following provides information on how you can distribute the SAP instances for the different SAPsystem variants You use SAPinst to install the SAP instances as a

n Central system on a single hostYou run SAPinst and install all instances on one host

n A distributed system on several hostsThe following figure shows how to distribute your instances on several hosts

20198 PUBLIC 03282008


Figure 4 Distribution of Instances in an ABAP+Java System

Note

You can use the SAP transport host or the SAP global host as your central instance host

You perform the following steps1 If you want to share the transport directory trans from another system you have to mount it

from this system Otherwise we recommend that you share the trans directory that is createdduring the installation of the central instance (see below)

2 On the SAP global host you run SAPinst and install the Java central services instance (SCS)

3


On the SAP global host you run SAPinst and install the ABAP and Java central servicesinstances (ASCS and SCS)End of HA (UNIX)

4 On the SAP global host you export the required file systems to the database and centralinstance host

5 On the database host you mount the exported file systems from the SAP global host andSAP transport host

6 On the database host you run SAPinst and install the database instance7 On the central instance host you mount the exported file systems from the SAP global host

and SAP transport host8 On the central instance host you run SAPinst and install the central instance

03282008 PUBLIC 21198


9 If required you can now install one to ltngt dialog instances The procedure is the same asinstalling a central instance (replace ldquocentral instancerdquo with ldquodialog instancerdquo in the procedure)

Caution

We do not support operating an ABAP dialog instance with an ABAP+Java system

Java Add-In for an Existing ABAP System

If you want to install the Java Add-In for an existing ABAP system you proceed as follows on theinstance host(s) of the ABAP system

n Central system on a single hostYou run SAPinst and install the Java Add-In on one host

n Distributed system on several hostsThe following figure shows how to distribute your instances on several hosts

Figure 5

1 On the SAP global host you run SAPinst to install the Java central services instance (SCS)2 On the database host you run SAPinst to install the Java Add-In for the database instance3 On the central instance host you run SAPinst to install the Java Add-In for the central instance4 If required you run SAPinst to install one to ltngt ABAP+Java dialog instances

22198 PUBLIC 03282008

2 Planning23 Production Client Considerations

Caution

You cannot install the Java Add-In for existing ABAP dialog instance(s) Instead you have toinstall new ABAP+Java dialog instance(s)

23 Production Client Considerations

A client is a self-contained unit in an SAP systemwith separate master records and its own set of tablesSAPinst creates three ABAP clients during the installation client 000 client 001 and client 066As of SAP NetWeaver 70 and Business Suite 2005 you can install an ABAP+Java system in oneinstallation run This means that AS Java is configured by default against ABAP client 001You can choose one of the following methods to set up your new production client

n You install the ABAP and the Java part of your system separatelyn You install an ABAP+Java system and reconnect the Java partn You install an ABAP+Java system and do not reconnect the Java part

The following procedure describes the above methods

Installing the ABAP and the Java Part of your System Separately

1 You install the ABAP system as described in the documentation Installation Guide ‒ ltyour SAP systemapplicationgt ABAP on ltyour OSgt ltdatabasegt

2 You perform the client copy [page 128]3 You install the Java Add-In for ABAP as described in this installation guide

You can specify the production client to which you want to connect the Java Add-In duringthe input phase of the installation

Installing an ABAP+Java System and Reconnecting the Java PartIf you need the Java users in your ABAP production client you have to manually configure theconnection of the Java part to the ABAP partFor more information about Java users see the table User Management Engine (UME) in Basic SAP SystemParameters [page 24]

1 You install the ABAP+Java system as described in this documentation2 You perform the client copy [page 128]3 You reconnect the Java part to the production client as described in SAP Note 937323

Installing an ABAP+Java System Without Reconnecting the Java PartIf you do not need the Java users in your ABAP production client there is no need to manuallyconfigure the connection of the Java part to the ABAP partFor more information about Java users see the table User Management Engine (UME) in Basic SAP SystemParameters [page 24]

03282008 PUBLIC 23198

2 Planning24 SAP System Transport Host

1 You install the ABAP+Java system as described in this documentation2 You perform the client copy [page 128]

24 SAP System Transport Host

The transport host contains the transport directory that is used by the SAP transport system to storetransport data and change information of SAP systems such as software programs data dictionarydata or customization data If you have several SAP systems they are usually organized in transportdomains In most cases all SAP systems in a transport domain have a common transport directoryFor more information seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management SoftwareLogistics Change and Transport System Change and Transport System ‒ Overview (BC-CTS) Basics of the Changeand Transport System Transport Management System ‒ ConceptWhen you install an SAP system SAPinst by default creates the transport directory on the centralinstance host in usrsaptransYou have to prepare this host for use by the new SAP system if one of the following applies to you

n You want to locate the transport directory on another hostn You want to use an existing transport host and directory in your SAP system landscape

For more information see Exporting and Mounting the Global Transport Directory [page 77]

More InformationSetting Up File Systems and Raw Devices [page 66]

25 Basic SAP System Parameters

The tables below list the basic system parameters that you need to determine before installing yourSAP system For all other SAP system parameters use the F1 help in the SAPinst dialogs

Note

In the column ldquoEnter Your Valuesrdquo you write down the values that you plan to use for exampletheMessage Port Number

24198 PUBLIC 03282008

2 Planning25 Basic SAP System Parameters

SAP System ID and Database ID

Parameters Description Enter Your Values

SAP System IDltSAPSIDgt

The SAP System ID ltSAPSIDgt identifies the whole SAPsystem

CautionChoose your SAP system ID carefully You cannot changethe SAP system ID after the installation

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

IDsADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR

GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS

PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID

USR VAR

Database ID ltDBSIDgt The ltDBSIDgt identifies the database instance SAPinstprompts you for the ltDBSIDgt when you are installing thedatabase instanceThe ltDBSIDgt can be the same as the ltSAPSIDgt

CautionChoose your database ID carefully Renaming is difficultand requires you to reinstall the SAP system

n If you want to install a new databaseMake 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 IDsADD ALL AND ANY ASC AUX COM CON DBA END EPS

FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL

OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL

SYS TMP UID USR VAR

n If you want to use an existing database system

03282008 PUBLIC 25198



Enter exactly the database ID of the existing database towhich you want to add the system

System ID ltSMDSIDgt ofSAP SolutionManagerDiagnostics Agent

SAPinst sets ltSMDSIDgt to SMD by defaultIf SMD is already used by another SAP system that is nota Diagnostics Agent system ltSMDSIDgt is set to DAltxgtwhere ltxgt can be any letter from A to Z and DA stands forldquoDiagnosticsAgentrdquo)If required you can change ltSMDSIDgt to a value of yourchoice on the Parameter Summary screen If you do so thesame naming conventions as for ltSAPSIDgt apply For moreinformation see entry ldquoSAP System ID ltSAPSIDgtrdquo in thistable above

SAP System Instances Hosts and Ports

Parameters Description EnterYourValues

Instance Number ofthe SAP system

Technical identifier for internal processes It consists of a two-digitnumber from 00 to 98The instance number must be unique on a host That is if more thanone SAP instance is running on the same host these instances must beassigned different numbersTo find out this number look under the SAP directoryusrsapltSAPSIDgtDVEBMGSltnngt on the host of the central instanceThe value ltnngt is the number assigned to the central instance

Instance Number forthe Diagnostics Agent

Technical identifier for internal processes for the Diagnostics Agentconsisting of a two-digit number from 00 to 98The instance number is set automatically to the next free and validinstance number that has not yet been assigned to the SAP systemThe same restrictions apply as in ldquoInstance Number of the SAP systemrdquo(see above)

Name of InstanceHost

Instance HostHost name of the specific instanceTo find out the host name open a command prompt and enter hostnameThe host name must not exceed 12 characters For more informationabout the allowed host name length and characters see SAP Note 611361

Message Server PortCaution

The message server port number must be unique for the SAP systemon all hosts If there are several message port numbers on one hostall must be unique

Port number of the SAP Message ServerIf you do not specify a value the default port number is usedABAP Message Server Port

26198 PUBLIC 03282008



There is an external message server port and an internal message serverportThe ABAPmessage server uses both the internal and the external messageserver ports The default profile contains the configuration for bothmessage server portsThe externalmessage server port uses the parameter rdispmsserv withdefault value 36ltnngt where ltnngt is the instance number of the ABAPmessage server instanceThe internal message server port uses the parameterrdispmsserv_internal with default value 39ltnngt whereltnngt is the instance number of the ABAP message server instanceJava Message Server PortThe Java message server only uses the internalmessage server port TheSCS instance profile contains the configuration for the Java messageserverThe parameter rdispmsserv is set to 0 so that the external port is notopenThe internal message server port uses the parameterrdispmsserv_internal with default value 39ltnngt whereltnngt is the instance number of the SCS message server instanceFor more information about the parameters used for message serverports see SAP Note 821875

Master Password


Master Password This password is used for all user accounts SAPinst creates andfor the secure store key phrase The length has to be 8 to 14charactersDepending on your installation scenario there might be morerestrictions

CautionIf you do not create the operating system users manuallySAPinst creates them with the common master password (seeldquoOperating System Usersrdquo) In this case make sure that themaster password meets the requirements of your operatingsystem and of your database

03282008 PUBLIC 27198


Operating System Users


Password of OperatingSystem Users

SAPinst processes the passwords of operating system users asfollowsn If the operating system users do not exist SAPinst creates the

following usersl ltsapsidgtadm

This user is the SAP system administrator userl ltsmdsidgtadm

This user is dedicated to the Diagnostics Agent installationwith sufficient authorization to manage the agentIt is created on the central instance host and on everydialog instance host

SAPinst sets the master password for these users by defaultYou can overwrite and change the passwords either by usingthe parameter mode Custom or by changing them on theparameter summary screen

n If the operating system users already exist SAPinst promptsyou for the existing password except if the password of theseusers is the same as the master password

n Make sure that the user ID and group ID of these operatingsystem users are unique and the same on each relevantapplication server instance host

For more information see Creating Operating System Users [page 62]

User Management Engine (UME)

Parameter Description Enter Your Values

ABAP Client The production client of the ABAP system

CautionThis is only relevant for a Java Add-In installation

DDIC Password The existing password of the DDIC user


Java AdministratorUser

This user is created by SAPinst in the ABAP systemAfter the installation this user is available both in the ABAPand in the Java systemSAPinst sets the user name J2EE_ADMIN and the master passwordby defaultIf required you can choose another user name and passwordaccording to your requirementsFor more information about supported UME data sources andchange options see SAP Note 718383

28198 PUBLIC 03282008



Java Guest User This user is for employees who do not belong to a companyor who have registered as company users and who arewaiting for approval Guest users belong to the default groupAuthenticated UsersThis user is created by SAPinst in the ABAP systemAfter the installation it is available both in the ABAP and inthe Java systemSAPinst sets the user name J2EE_GUEST and the master passwordby defaultIf required you can choose another user name and passwordaccording to your requirementsFor more information about supported UME data sources andchange options see SAP Note 718383

Communication User This user is created by SAPinst in the ABAP systemAfter the installation it is available both in the ABAP and inthe Java systemThis user is used for the communication between the ABAPsystem and the Java systemSAPinst sets the user name SAPJSF and the master password bydefaultIf required you can choose another user name and passwordaccording to your requirementsFor more information about supported UME data sources andchange options see SAP Note 718383

Key Phrase for Secure Store Settings


Key Phrase for SecureStore Settings

This is a random word or phrase that is used to encrypt thesecure storeThe Java EE engine uses this phrase to generate the key that isused to encrypt the dataThe uniqueness of the phrase you use contributes to theuniqueness of the resulting key

RecommendationUse a long key phrase that cannot be guessed easily Use bothuppercase and lowercase letters in the phrase and includespecial characters

03282008 PUBLIC 29198


Internet Communication Manager (ICM) User Management


Password of webadm The administration user webadm is created to use the webadministration interface for Internet Communication Manager(ICM) and Web DispatcherSAPinst sets the master password by default If required youcan choose another password The length of the password mustbe between 5 and 128 characters

Solution Manager Key


SAP Solution Managerkey

To install your SAP system you need to generate an SAP SolutionManager key [page 80] which the installation requires to continueFor more information see SAP Note 805390

Parameters Relevant for the Connectivity to System Landscape Directory (SLD)


SLD Destination The System Landscape Directory (SLD) isdesigned for registering the systems (alongwith the installed software) of your wholesystem landscapeThe usual case is to configure one SLD foryour complete system landscapeFor more information see Configuring SystemLandscape Directory [page 173]

SLD HTTP Host The host name of the System LandscapeDirectory (SLD)

SLD HTTP Port The HTTP port of the Java system wherethe SLD is installed The following namingconvention applies 5ltinstance_numbergt00

ExampleIf the instance number of your Java system is01 the SLD HTTP Port is 50100

30198 PUBLIC 03282008



SLD Data Supplier Userand password

n If you want to install a local SLD SAPinstcreates this user during the installation

n If you want to connect your system to anexisting central SLD you have to enterthe existing SLD Data Supplier User andpassword of the central SLD during theinstallation

RecommendationWe recommend that you name this userSLDDSUSER

SLD ABAP API User andpassword



RecommendationWe recommend that you name this userSLDAPIUSER

RFC User Password The ABAP RFC user of the SLD

SLD Gateway Host The host on which the gateway instance ofthe SLD is running

SLD Gateway InstanceNumber

The instance number of the gateway instanceof the SLD

SAP System Client The client in which the ABAP RFC user exists

Parameters Relevant for Adobe Document Services (ADS)


User for basicauthentication

SAPinst sets the user name ADSUSER and the masterpassword by defaultIf required you can choose another password accordingto your requirements

User for processing formsbetween an ABAP and aJava environment

SAPinst sets the user name ADSAGENT and the masterpassword by defaultIf required you can choose another password accordingto your requirements

03282008 PUBLIC 31198



Parameters Relevant for SAP NetWeaver Development Infrastructure (NWDI)


Administrator of the SAPNetWeaver DevelopmentInfrastructure (NWDI)and Password

SAPinst sets the user name NWDI_ADM and the masterpassword by defaultIf required you can choose another password accordingto your requirements

Developer in the SAPNetWeaver DevelopmentInfrastructure (NWDI)and Password

SAPinst sets the user name NWDI_DEV and the masterpassword by defaultIf required you can choose another password accordingto your requirements

Landscape DirectoryService User in the SAPNetWeaver DevelopmentInfrastructure (NWDI)and Password

SAPinst sets the user name NWDI_CMSADM and the masterpassword by defaultIf required you can choose another password accordingto your requirements

End of Development Infrastructure (DI)


Parameters Relevant for Process Integration (PI)


Integration RepositoryService User and Password

SAPinst sets the user name PIREPUSER and the masterpassword by defaultIf required you can choose another user name andpassword according to your requirements

NoteIf you want to choose another user name make surethat this user name starts with ldquoPIrdquo

Integration DirectoryService User and Password

SAPinst sets the user name PIDIRUSER and the masterpassword by defaultIf required you can choose another user name andpassword according to your requirements


32198 PUBLIC 03282008



Landscape DirectoryService User and Password

SAPinst sets the user name PILDUSER and the masterpassword by defaultIf required you can choose another user name andpassword according to your requirements


Integration ServerApplication User andPassword

SAPinst sets the user name PIAPPLUSER and the masterpassword by defaultIf required you can choose another user name andpassword according to your requirements


Runtime WorkbenchService User and Password

SAPinst sets the user name PIRWBUSER and the masterpassword by defaultIf required you can choose another user name andpassword according to your requirements


Adapter Framework ServerService User and Password

SAPinst sets the user name PIAFUSER and the masterpassword by defaultIf required you can choose another user name andpassword according to your requirements


Integration Server ServiceUser and Password

SAPinst sets the user name PIISUSER and the masterpassword by defaultIf required you can choose another user name andpassword according to your requirements


03282008 PUBLIC 33198



Management ServerService User and Password

SAPinst sets the user name PILSADMIN and the masterpassword by defaultIf required you can choose another user name andpassword according to your requirements


Exchange InfrastructureAdministrator andPassword

This user has extensive authorizationsSAPinst sets the user name PISUPER and the masterpassword by defaultIf required you can choose another user name andpassword according to your requirements


Exchange InfrastructureCommunicator andPassword

SAPinst sets the user name PI_JCD_RFC and the masterpassword by defaultIf required you can choose another user name andpassword according to your requirements



Parameters Relevant for the File System

Parameters Description Your Values

File system for the home directoryuser

homeltusernamegt

34198 PUBLIC 03282008



SAP systemmount directory ltsapmntgt is the base directory forthe SAP systemFor ltsapmntgt you can use adirectory of your choiceDo not add ltSAPSIDgt assubdirectory because the systemadds this directory automatically

ExampleIf you enter ltsapmntgt thesystem creates the directoryltsapmntgtltSAPSIDgt

Oracle database file systems n Oracle homen sapdata homen Client destinationn sapdata directory

Parameters Relevant for the Database


Code page The code page that is used by your database (Unicode orNon-Unicode)

NoteThis parameter is only prompted if you perform a targetsystem installation as part of a system copy

Database schemaPasswords

The Java database schema is namedSAPltSCHEMA_IDgtDBDefault name is SAPSR3DBThe ABAP database schema is named SAPltSCHEMA_IDgtDefault name is SAPSR3

RecommendationChoose a ltSCHEMAIDgt that is different from your ltSAPSIDgtIt might cause problems when you copy a systemwhere ltSCHEMAIDgt is the same as ltSAPSIDgt and thedatabase-specific method used for the copy does not allowyou to rename the database schemas In certain situationsyou might create a system copy with a new ltSAPSIDgt butwhere the database schema has the old ltSAPSIDgt This isnot a technical problem but might confuse the systemadministrator

03282008 PUBLIC 35198



Password of Useroraltdbsidgt

User oraltdbsidgt is the database administrator userThis user is only required on the host on which thedatabase instance runsn If you created user oraltdbsidgtmanually before the

installation SAPinst prompts you for the existingpassword of this user

NoteIf you chose parameter mode Typical SAPinst onlyprompts you for the existing password of this user ifthe password is not the same as the Master Password

n If you did not create user oraltdbsidgtmanually beforethe installation SAPinst creates it automatically duringthe installation SAPinst then prompts you to enter andconfirm a password for this user In this case SAPinstsets the Master Password by default You can overwriteit

NoteIf you chose parameter mode Typical SAPinst doesnot prompt you for the existing password of this userbut creates this user and assigns the Master Passwordautomatically

Make sure that the user ID and group ID of this operatingsystem user are unique and the same on each applicationinstance hostFor more information see Creating Operating System Users[page 62]

User ID of Useroraltdbsidgt

If you chose parameter mode Typical and you did not createoraltdbsidgtmanually before the installation SAPinstautomatically creates this user with the appropriate userID In this case SAPinst does not prompt you for the userID of oraltdbsidgtMake sure that the user ID of user oraltdbsidgt is uniqueand the same on each application instance hostFor more information see Creating Operating System Users[page 62]

36198 PUBLIC 03282008



Group IDs of sys dba andoper

If you chose parameter mode Typical and you did not createoraltdbsidgtmanually before the installation SAPinstautomatically creates this user and assigns it to groups sysdba and oper In this case SAPinst does not prompt you forthe user ID of oraltdbsidgtMake sure that the group IDs of dba and oper are uniqueand the same on each application instance hostFor more information see Creating Operating System Users[page 62]

Database User Oracle User System

Oracle Listener NameOracle Listener Port

n If you install the database instance on a host where noother Oracle database is installed you normally do nothave to change the default values for Listener Nameand Listener Port

n If there is already an Oracle database installed on yourinstallation host you can either use one listener forboth databases or you have to specify an unused ListenerName and an unused Listener Port for the new listenerFor more information if you use one listener for bothdatabases see SAP Note 98252

n All dialog instances of an SAP systemmust use the sameListener Port than the database instance

Tablespaces Datafiles An Oracle database consists of one or more logical storageunits called tablespaces which collectively store all of thedatabasersquos dataEach tablespace in an Oracle database consists of one ormore files called datafiles which are physical structuresthat conform to the operating system in which Oracle isrunningMaxDatafileSize is the initial size of the tablespacedatafile and its mapping to the new tablespace layout whileimporting the external file DBSIZEXMLSAPinst prompts you to enter MaxDatafileSize in MBn 0 Datafile size defined in DBSIZEXML is not changedn 2000 Default datafile sizen 10000 Maximum datafile sizeFor more information about space requirements of the SAPdatafiles (sapdata 1 - 4) see Requirements for the DatabaseInstance [page 57]

03282008 PUBLIC 37198

2 Planning26 Running Adobe Document Services on Nonsupported Platforms


Database Instance RAM The RAM that is required for the database instanceinstallationThe default value used by SAPinst is 50 percent of the entireRAMFor more information about minimum RAM seeRequirements for the Database Instance [page 57]

Login Shell SAPinst only prompts you for this parameter if you use alogin shell other than the recommended C shell (csh)For more information see SAP Note 202227

26 Running Adobe Document Services on NonsupportedPlatforms

Adobe document services (ADS) are currently supported on a limited set of 64-bit platforms forSAP NetWeaver

ProcedureTo use ADS in SAP landscapes on nonsupported platforms you have to install an additionalstandalone SAP system with AS Java on a platform supported by ADSFor more information see SAP Note 925741


27 High Availability Planning the Switchover Cluster

You can reduce unplanned downtime for your high-availability (HA) SAP system by setting up aswitchover cluster This setup replicates critical software units ‒ known as ldquosingle points of failurerdquo(SPOFs) ‒ across multiple host machines in the cluster In the event of a failure on the primary nodeproprietary switchover software automatically switches the failed software unit to another hardwarenode in the cluster Manual intervention is not required Applications accessing the failed softwareunit experience a short delay but can then resume processing as normalSwitchover clusters also have the advantage that you can deliberately initiate switchover to free up aparticular node for planned systemmaintenance Switchover solutions can protect against hardwarefailure and operating system failure but not against human error such as operator errors or faultyapplication softwareWithout 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 system

38198 PUBLIC 03282008

2 Planning27 High Availability Planning the Switchover Cluster

You can protect software units that are not SPOFs against failure by simply replicating them Forexample you can add additional dialog instances (that is additional application servers) Thiscomplements the switchover solution and is an essential part of building HA into your SAP system

Recommendation

We recommend switchover clusters to ensure HA for 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)

Recommendation

If you want to install the Java Add-In to an existing ABAP High-Availability system we recommendthat you install the Java central services instance (SCS) in the switchover cluster of the ABAP centralservices instance (ASCS)

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 systemWe recommend that you read the following documentation before you start

n Check the informations and the installation guides that are available athttpsdnsapcomirjsdnha

n The standalone replicated enqueue server is a major contribution to an HA installation and isessential for a Java system We strongly recommend you to use it for an ABAP systemFor more information about how to install the standalone replicated enqueue server seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology ClientServerTechnology The SAP Lock Concept Standalone Enqueue Server Installing the Standalone Enqueue Server

FeaturesThe following figure shows the essential features of a switchover setup

03282008 PUBLIC 39198


Figure 6

Note

This figure and the figures in this section are only examples You need to discuss your individual HAsetup with your HA partner

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

40198 PUBLIC 03282008


Figure 7

ConstraintsThis documentation concentrates on the switchover solution for the central services instance Formore information about how to protect the NFS File System and the database instance by usingswitchover software or (for of the database) replicated database servers contact your HA partnerYou need tomake sure that your hardware is powerful enough to handle the increased workload aftera switchover Some reduction in performance might be acceptable after an emergency However it isnot acceptable if the system comes to a standstill because it is overloaded after switchoverEnd of HA (UNIX)

03282008 PUBLIC 41198

This page is intentionally left blank

3 Preparation

3 Preparation

You have to complete the following preparations

1


You perform the switchover preparations [page 44] for a high-availability (HA) systemEnd of HA (UNIX)

2 You check the hardware and software requirements [page 49]3 If required you create operating system users manually [page 62]4 You set up file systems and raw devices [page 66]5 If you want to perform a distributed installation you export and mount global directories

Caution

This section does not apply to the installation of a Java Add-In to an existing ABAP system

a) On the SAP trans host you export the trans directory to SAP global host central instance hostdatabase instance host andmdash if requiredmdash to the dialog instance host(s)

b) On the SAP global host you export subdirectories exe global profile of sapmntltSAPSIDgtto central instance host database instance host andmdash if requiredmdash to the dialog instancehost(s)

c) You mount subdirectories exe global profile of sapmntltSAPSIDgt and directory trans onthe database instance host and on the central instance host If you want to install one or moredialog instance(s) you also have to mount these directories on the dialog instance host

For more information about exporting and mounting directories seen Exporting and Mounting the Global Transport Directory [page 77]n Exporting and Mounting Directories via NFS for AIX [page 78]

6 You install the SAP front-end software [page 79]

Caution


7 You generate the SAP Solution Manager Key [page 80]

Caution


03282008 PUBLIC 43198

3 Preparation31 High Availability Switchover Preparations

8 You install the Java Development Kit [page 80]9 You prepare and mount the installation media [page 82]


31 High Availability Switchover Preparations


311 Preparing for Switchover

This section describes the extra preparations you need tomake for a high availability (HA) installationFor more information consult your HA partnerYou need to perform the preparations listed below on host A and ‒ after you have installed the centralservices (SCS) instance ‒ on host B

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 38]

Procedure

1 You check that your system meets the hardware and software requirements [page 49] for an HA setupincluding the switchover software

2 You set up file systems (that is disk partitions) mount points and (if required) NFS for yourHA system ona) Node A before the installation of the SCS instance with SAPinstb) Node B after the installation of the SCS instance with SAPinstTo do this proceed as follows

Caution


Recommendation

If possible use journaled file systems (JFS) which allows much quicker recovery after a hostmachine crash With JFS you can reduce the switchover time because the hard disk maintainsdata integrity in the event of a system crash or if the system is otherwise halted abnormally

44198 PUBLIC 03282008


a) You set up the required file systems [page 46] using mount points or NFSb) If required you configure NFS [page 47] making sure you are using the virtual host name for NFS

to enable NFS switchoverc) You assign the local file systems to mount pointsd) You assign the shared file systems to mount points in appropriate cluster packages

Example

The figure 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 needsconsult your HA partner

Figure 8

3 You set up Domain Name System (DNS) on the virtual host

Caution


4 You assign the virtual IP addresses and host names for SCS instance and (if required) NFS toappropriate cluster packages

03282008 PUBLIC 45198


Caution


Note

For more information on how to assign resources to cluster packages ask your HA partner

End of HA (UNIX)


312 Setting Up File Systems for a High-Availability System

When you prepare a high-availability (HA) installation you need to set up your file systems asdescribed here For more information consult your HA partner

Caution


Procedure

1 Create the file systems or raw partitions for the central services (SCS) instance on shared disks Formore information see Setting Up File Systems and Raw Devices [page 66]

Note

The directories ltsapmntgtltSAPSIDgt and usrsaptrans have to be mounted from a NetworkFile System (NFS) whereas usrsapltSAPSIDgt is a directory of the AS instance that is alwaysmounted on the instance (not with NFS)Therefore if the central instance host is not the NFS server host you might have to mount atleast the first two file systems on different physical disks from the third file system

2 If the node that takes over the central instance also runs an AS instance during normal operationwe recommend that you use a different approach for the file system for the usrsapltSAPSIDgtdirectoryusrsapltSAPSIDgt contains two subdirectoriesn SYS contains links to the central directory ltsapmntgtltSAPSIDgtn ltINSTTYPEgtltNRgt contains data for the local AS instance

The name ltINSTTYPEgtltNRgt is defined by the type of services and the application server numberfor example DVEBMSG00

Only the directory ltINSTTYPEgtltNRgt needs to be migrated with the AS instance during theswitchover Since the SYS subdirectory contains only links that do not require any space it can

46198 PUBLIC 03282008


be created locally on each cluster node Therefore instead of usrsapltSAPSIDgt create a filesystem for usrsapltSAPSIDgtltINSTTYPEgtltNRgt with the usual ltgt substitutions The file namefor the central instance is usually DVEBMGS00 This avoids mount conflicts when switching over toa node on which an AS instance is already running The DVEBMGS00 directory can join the treeusrsapltSAPSIDgt instead of mounting on top of it

Note

This approach becomes increasingly important when you want to cluster central services whileother instances run on the cluster hosts outside the control of the switchover software so as touse the resources efficiently Youmust use this approach for integrated installations of the ASwith ABAP and Java stacks

End of HA (UNIX)


313 Configuring Network File System

If required you configure Network File System (NFS) which is a system-wide Single Point-of-Failure(SPOF) for a high-availability (HA) installation For more information consult 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

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 Web AS systems (forexample development ‒ integration) This transport directory ought to be accessible by at leastone AS instance of each system but preferably by all

03282008 PUBLIC 47198


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 systemmight dictate how NFS has to be set up If required youcan configure the NFS server on the cluster node of the CI or 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 a dialog instance) it alsoneeds 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

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

48198 PUBLIC 03282008

3 Preparation32 Hardware and Software Requirements

n These directories on the standby node are accessible againusrsaptrans

sapmntltSIDgt

End of HA (UNIX)

End of HA (UNIX)

32 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating systemand the SAP instances

Caution

If your hosts do not fully meet the requirements you might experience problems when workingwith the SAP system

Prerequisites

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 central instance host (for example on a

separate database instance host) make sure that the printer can be accessed under UNIX

Process Flow

1 Check the Product Availability Matrix at httpservicesapcompam for supported operatingsystem releases

2 Check the hardware and software requirements usingn The Prerequisite Checkerl Standalone (optional) before the installation process

For more information see Running the Prerequisite Checker Standalone [page 50]l Integrated in SAPinst (mandatory) as part of the installation process

For more information see Running SAPinst on UNIX [page 94]

Note

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

n The hardware and software requirements checklists forl AIX [page 51]l Central system [page 54]l Distributed or high availability system [page 56]

03282008 PUBLIC 49198


l If you want to install dialog instance(s) check the requirements for a dialog instance [page 60]

Note

If you want to use 32-bit SAP NetWeaver components first check whether thesecomponents can run on 64-bit operating systems If so we recommend you to use 64-bitsystems If not you can install an SAP dialog instance on 32-bit operating systems to runthese components For all other SAP instances you must use 64-bit systems

3 If you are installing a production system the values provided by the Prerequisite Checker and thehardware and software requirements checklists are not sufficient In addition do the followingn You use the SAP Quick Sizer tool available at httpservicesapcomsizing

For more information about the SAP Quick Sizer and available sizing guides see theMaster Guide ‒SAP NetWeaver 70 at httpservicesapcominstallnw70 Planning


Note

If you want to install usage type Development Infrastructure (DI) also check SAP Note737368 for system requirements and sizing


n You contact your hardware vendor who can analyze the load and calculate suitable hardwaresizing depending onl The set of applications to be deployedl How intensively the applications are to be usedl The number of users

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

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 installed the correct Java Development Kit (JDK) [page 80]n You have prepared the installation master DVD on the required installation host [page 82]

50198 PUBLIC 03282008


n You make sure that the required prerequisites are met before starting SAPinst [page 89]

Procedure

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

Options 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 may also check theresults in file prerequisite_checker_resultshtml which you find in the installation directory

322 Requirements for AIX

The host machine must meet the following requirements

Note

The information here is not intended to replace the documentation of the AIX operating systemYou can perform AIX-specific steps as follows

n Manually by entering AIX commands with the appropriate options

n Using SystemManagement Interface Tool (SMIT) a menu-driven system administration tool

If you have problems with the function keys you can also use ESC and the corresponding numberto simulate the function key (for example F4 is equivalent to ESC and 4 )

03282008 PUBLIC 51198


Hardware Requirements

Requirement Values and Activities

Tape drive High-capacity tape drive with hardware compression is recommendedYou can test the drive devrmt0 with this commandtar -cvf devlttape_devicegt lttest_filegt

The device name is always rmt0 unless more than one tape drive exists

DVD drive n ISO 9660 compatiblen You can configure multiple CD DVD drives but you cannot mount all of them For

more information seeMounting a CD DVD for AIX [page 85]

Required disks For data security reasons distribution over three disks is required We recommendyou to distribute over five disksTo display available disks enter this commandlspv

Disks marked none in the 3rd column are unusedTo display free space on a disk enter this commandlspv -p ltdisk_namegt

Areas marked free in the 2nd column are unusedIf 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 To display RAM size in KB enter the following commandlsattr -El sys0 -a realmem

CPU The recommended minimum hardware is either two physical single core processors orone physical dual core processor

Software Requirements


C++ runtime level Check the C++ runtime level with the following commandsn AIX 6xl lslpp mdashL xlCaix61rte

The output must be at least 9001l lslpp mdashL xlCrte

The output must be at least 9001n AIX 5xl lslpp mdashL xlCaix50rte


The output must be at least 7000

Operating systemversion

Check the operating system version with the following commandlslpp -l bosrte

The output must include the following or a larger version numberbosrte 52050

52198 PUBLIC 03282008



AIX MaintenanceLevel (ML) andTechnology Level(TL)

n AIX 6x The output of the command oslevel -s should be at least 6100-00-01n AIX 53 The output of the command oslevel -s should be at least 5300-05-01

(TL 5 SP 1)n AIX 52 The output of the command oslevel -r should be at least 5200-04 (ML 4)

LDAP (LightweightDirectory AccessProtocol)

If you want to use LDAP you require the following LDAP librarylibldapa

Additional software Make sure that the following additional file sets are installedn bosadt Base Application Developmentn bosperfmdashperformance and diagnostics toolsn perfagenttoolsmdashperformance monitoring toolsn bosperflibperfstatmdashPerformance Statistics LibraryFor an overview of the installed file sets enter the following commandlslpp ndashL | more

Install the necessary local code set by adding an additional language environmentas follows

1 Start the SystemManagement Interface Tool (SMIT) with the following commandsmitty mle_add_lang

2 Select the followingn Cultural Conventions to install

ISO8859-1 German (Germany) [de_DE]

n Language Translation to install

ISO8859-1 German [de_DE]

This step installs the required bosloc and bosiconv file sets

3 Additionally check that all file sets are in a consistent state with this commandlppchk ndashv

Other Requirements


Printer Check whether a file can be printed with this commandlp -dltprinter_namegt lttest_filegt

Check the status of your spool and the printers with this commandlpstat -t

Keyboard You can set the keyboard by typing this command on the directly connected consolesmitty chkbd

You can select your keyboard under Motif by setting a language environment (LANG)for which a National Language Support (NLS) component is installed The settingstake effect after reboot

Network Test the network connection to the database server with this commandetcping ltdb_server_namegt 100 10

03282008 PUBLIC 53198


323 Requirements for a Central System

If you want to install a central system ‒ that is all instances reside on one host ‒ the host must meetthe following requirementsThe table below also lists themost relevant requirements for the Oracle databaseYou get the full list of hardware and software requirements from the relevantOracle database installation guide for your operating system which you can find athttpwwworaclecomtechnologydocumentation

Recommendation

If you have access to Oracle Metalink we strongly recommend that you read document 1697061 Thisdocument provides information about all operating system prerequisites and is regularly updated

Caution

If your database resides on Network Attached Storage (NAS) you need to review and implement theOracle NAS guidelines You need to mount network file systems with specific mount options whichyou can find in the Oracle installation guide

Caution

The database must be Oracle 102 or higher



Distribution of theOracle Database

We recommend distribution of the Oracle database over three disks (RAID5) fordata security reasonsTo decide how many hard disks are required for your Oracle database see thesection Database System Configuration in SAP Database Guide Oracle (BC-DB-ORA-DBA) inthe SAP Library at httphelpsapcomnw70 SAP NetWeaver 70 Library EnglishSAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by KeyCapability Platform-Wide Services Database Support Oracle SAP Database Guide Oracle(BC-DB-ORA-DBA) Getting Started with Oracle and the SAP System

Hard disk space n Hard disk drives with sufficient space for the SAP system and the databaseFor more information see Setting Up File Systems [page 66]

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 82]

n 12 GB of temporary disk space for the installation

54198 PUBLIC 03282008



RAM 3 GB (minimum) 8 GB (recommended)Java Add-In (ABAP system already exists) 15 GB (minimum) 4 GB(recommended)


55 GB (minimum) 9 GB (recommended)End of BI Java


Java Add-In (ABAP system already exists) 4 GB (minimum) 5 GB(recommended)End of BI Java


For more information see SAP Note 927530End of BI Java

Swap Space Hard disk drives with sufficient space for swap 3 to 4 RAM



Network File System(NFS)

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

National LanguageSupport (NLS)

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

GUI for Oracle DatabaseInstallation

On the database host a graphical user interface (GUI) for example X11 is requiredfor the Oracle database software installation with runInstaller For moreinformation see the documentation of your operating system

Oracle Interim Patches Check SAP Note 839182 whether you require an interim patch for the Oracledatabase installation In this case make sure you have the corresponding Perlversion as stated in that SAP Note

Oracle KernelParameters

Review the Oracle-recommended kernel parameters and shell limits for youroperating system with Oracle Database 10g Release 2 (102)These are only recommendations from Oracle for optimizing the systemperformance in production environments If the recommended settings are notsuitable for your system you must tune the kernel parameters accordinglyYou can get the recommended shell limits and kernel parameters from the relevantOracle database installation guide for your operating system athttpwwworaclecomtechnologydocumentation

Parameter compatible If you want to install a Java Add-In for an upgraded ABAP systemmake sure that the parameter compatible is set to 1020 in the fileORACLE_HOMEdbsinitltdbsidgtoraFormore information seeUpgrade Guide ‒ SAP NetWeaver 70 Application Server ABAP at

03282008 PUBLIC 55198



httpservicesapcomupgradeNW70 Upgrade to SAP NetWeaver Systems UpgradeDocumentation ‒ SAP NetWeaver 70 ltSRgt SAP NetWeaver 70 ltSRgt Application ServerABAP

324 Requirements for a Distributed or a High AvailabilitySystem

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

n Central services instance [page 56]n Central instance [page 57]n Database Instance [page 57]

Note

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

3241 Requirements for the Central Services Instance

The central services instance host must meet the following requirements



Hard disk space n Hard disk drives with sufficient space for the central services instanceFor more information see Setting up File Systems [page 66]

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 82]


RAM 05 GB (minimum) 1 GB (recommended)


1 GB (minimum) 3 GB (recommended)End of HA (UNIX)


56198 PUBLIC 03282008





Network File System (NFS) must be installed

3242 Requirements for the Central Instance

The central instance host must meet the following requirements



Hard disk space n Hard disk drives with sufficient space for the central instanceFor more information see Setting Up File Systems [page 66] SAP File Systems









Required fonts and codepages

Make sure that the required fonts and code pages are installed



3243 Requirements for the Database Instance

The database host must meet the following requirementsThe table below lists themost relevant requirements for the Oracle database instance host

03282008 PUBLIC 57198


You get the full list of hardware and software requirements from the relevantOracle database installation guide for your operating system which you can find athttpwwworaclecomtechnologydocumentation

Recommendation


Caution


Caution




Distribution of the OracleDatabase

We recommend distribution over three disks (RAID5) for data security reasonsTo decide how many hard disks are required for your Oracle database see theDatabase System Configuration guide in SAP Database Guide Oracle (BC-DB-ORA-DBA)in the SAP Library at httphelpsapcomnw70 SAP NetWeaver 70 LibraryEnglish SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platformby Key Capability Platform-Wide Services Database Support Oracle SAP DatabaseGuide Oracle (BC-DB-ORA-DBA) Getting Started with Oracle and the SAP System

Hard disk space n 20 GB plus space for the SAP data file systemsFor space requirements of the SAP data file systems (sapdata 1 - 4) see thefollowing fileltExport_DVDgtEXP1DBORADBSIZEXML

NoteThe values listed in DBSIZEXML are only guiding values Each sapdataltngt

file can grow up to 10 GB maximum

For more information about the required disk space per file system see SettingUp File Systems and Raw Devices ‒ Oracle File Systems [page 73]

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


58198 PUBLIC 03282008



RAM 1 GB (minimum) 3 GB (recommended)Java Add-In (ABAP system already exists) 500 MB (minimum) 2 GB(recommended)3 GBThe default value used by SAPinst is 50 percent of the entire RAMDepending on the amount of data involved the requirements might changeYou can do one of the following to get a more precise sizing definition thatreflects your particular system loadn Contact a hardware vendor The vendor analyzes the load and calculates

suitable hardware sizingn Contact the person in charge of installation or your Oracle Competence

Center




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



National Language Support(NLS)

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


On the database host a graphical user interface (GUI) for example X11 isrequired for the Oracle database software installation with runInstaller Formore information see the documentation of your operating system


Oracle Kernel Parameters Review the Oracle-recommended kernel parameters and shell limits for youroperating system with Oracle Database 10g Release 2 (102)These are only recommendations from Oracle for optimizing the systemperformance in production environments If the recommended settings arenot suitable for your system you must tune the kernel parameters accordinglyYou can get the recommended shell limits and kernel parameters from therelevant Oracle database installation guide for your operating system whichyou can find athttpwwworaclecomtechnologydocumentation

Parameter compatible If you want to install a Java Add-In for an upgraded ABAP systemmake sure that the parameter compatible is set to 1020 in the fileORACLE_HOMEdbsinitltdbsidgtora For more information see Upgrade Guide‒ SAP NetWeaver 70 Application Server ABAP on SAP Service Marketplace athttpservicesapcomupgradeNW70

03282008 PUBLIC 59198


325 Requirements for a Dialog Instance

The dialog instance host must meet the following requirements



Hard disk space n Hard disk drives with sufficient space for the dialog instanceFor more information see Setting up File Systems [page 66]



RAM 1 GB minimum 3 GB recommended




SAP kernel Make sure that the SAP kernel of the central instance has at least the patch levelof the SAP kernel on the SAP Kernel DVD that is used for the installation of thedialog instanceWe recommend that you apply the most current SAP kernel from the SAP ServiceMarketplace at httpservicesapcomswdc



326 Checking and Modifying the AIX Kernel

To run an SAP system on AIX with an Oracle database you must check andmdash if necessarymdashmodifythe UNIX operating system kernel

Recommendation

We recommend that all UNIX kernel modifications be performed by your UNIX systemadministrator

Procedure

1 Asynchronous IO If the database is installed using file systems the settings for asynchronous IO(aio) should be as followsmaxservers = minservers = 12 number of data files used for the databaseSet these values as follows

60198 PUBLIC 03282008


a) Entersmitty aio orsmit aio

b) Select Change Show Characteristics of Asynchronous IOc) Enter the appropriate numbers for MINIMUM and MAXIMUM number of servers

Note

If maxserver is greater than minserver the surplus asynchronous IO processes are chargedagainst the database system rather than root and have a lower scheduling priority Experienceshows that all processes become active very quickly and once active the asynchronous IOservers are never stopped Therefore it is simpler and more efficient to set them to the samevalue at startup

2 The setting forMaximum number of processes allowed per usermay need to be increased on the databaseserver If you have increased the number of maxservers then you should check this setting tomake sure that theMaximum number of processes allowed per user is at least greater than the maximumnumber of aioservers This is not an issue if the values set as recommended above Actuallyit must be greater than the sum of the maximum number of aioservers plus all of the otherprocesses of the oraltdbsidgt usera) As a rule of thumb set maxprocs to the followingn Small system 512n Medium system 2048n Large system 4096

If you are not sure which value is applicable choose the higher value

Note

Setting maxprocs to a higher value than the number of processes that are actually useddoes not cause any extra overhead

b) Set theMaximum number of Processes allowed per user to be greater than maxservers plus the resultfrom step aA) Enter

smitty orsmit

B) Select System EnvironmentsC) Select Change Show Characteristics of Operating SystemD) Enter the appropriate number forMaximum number of processes allowed per user and choose Enter

3 Adjust the minperm and maxperm settings according to SAP Note 973227

03282008 PUBLIC 61198

3 Preparation33 Creating Operating System Users

327 Setting up Swap Space for AIX

1 Check the allocated swap spacea) To start the SystemManagement Interface Tool (SMIT) enter the following command

smittyb) Perform one of the following stepsn Choose Physical amp Logical Storage Logical Volume Manager Paging Space List All Paging Spaces

n Enter this commandlsps mdasha

2 Check if there is sufficient swap space 3 to 4 RAM is recommended3 If required add another paging space using smitty

a) Choose Physical amp Logical Storage Logical Volume Manager Paging Space Add Another Paging SpaceA list of volume group names is displayed

b) Select a volume groupc) Enter the size of paging space in logical partitionsd) Set Start using this paging space NOW to YESe) Set Use this paging space each time the system is RESTARTED to YESf) To exit smitty choose F10 g) To check the results follow the procedure described above in step 1

33 Creating Operating System Users

331 Network Information Service

If you use Network Information Service (NIS) you need to distribute users over the network

Caution

If you do not create users manually SAPinst creates them automatically during the installationAll usersmust have identical environment settings If you change the environment delivered bySAP such as variables paths and so on SAP does not assume responsibility

SAPinst checks all required users groups and services on the local machine If you manage usersgroups or services network-wide in your company we recommend that you create the user andgroup NIS entries before running SAPinst as described in Creating Operating System Users and GroupsManually (Optional) [page 62]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 accordingly

62198 PUBLIC 03282008


SAPinst checks the NIS users groups and services using NIS commands However SAPinst does notchange NIS configurations

332 Creating Operating System Users and Groups

Caution


If you do not want SAPinst to create operating systems users groups and services you can optionallycreate them manually before the installationIf you want to use global accounts that are configured on a separate host you start SAPinst andchoose Life Cycle Management Preparation Operating System Users and Groups For more informationsee Running SAPinst on UNIX [page 94]

Users and Groups

SAPinst checks whether the required users and groups already exist If not it creates new users andgroups as necessarySAPinst chooses available user IDs and group IDs unless you are installing a dialog instance On adialog instance you have to enter the same IDs as on the central instance hostAs a general requirement the user IDs and the group IDs must be the same on all hosts

Caution

If you use NFS-V4 file system then you have to create the oraltdbsidgt user on the NFS server Youcan do this either manually or by running Operating System Users and Groups This user must have thesame user ID as the oraltdbsidgt user on the database serverOtherwise you get the error message FSL-02098 Could not change owner of during theinstallation of the database instance

Caution

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

Caution

Do not delete any shell initialization scripts in the home directory of the OS users This applies evenif you do not intend to use the shells that these scripts are for

Users and Groups

03282008 PUBLIC 63198


User Primary Group Additional Group(s) Comment

ltsapsidgtadm sapsys oper dba sapinst SAP system administrator

ltsmdsidgtadm sapsys sapinst Diagnostics Agentadministrator

oraltdbsidgt dba oper sapinst Database administrator

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 user ltsapsidgtadm and the databaseoperating system usermust have the same password on all hosts

Groups and Members

Groups Members

sapsys ltsapsidgtadm ltsmdsidgtadm

oper ltsapsidgtadm oraltdbsidgt

dba ltsapsidgtadm oraltdbsidgt

sapinst ltsapsidgtadm ltsmdsidgtadm oraltdbsidgt

The user oraltdbsidgt is only required on the host where the database instance runs

More InformationCreating AIX Groups and Users (Optional) [page 64]

333 Creating AIX Groups and Users (Optional)

Creating AIX Groups and UsersTo create AIX groups and users use the SystemManagement Interface Tool (SMIT)

1 Create groups as followsa) Enter the command smittyb) Choose Security and Users Groups Add a group c) Enter a group name ‒ for example sapsys ‒ and set administration group to trued) Press F3 until the Security amp Usersmenu appears

2 To create users proceed as followsa) Enter a user name for example ltsapsidgtadm

64198 PUBLIC 03282008


b) Enter all required values3 Set the initial password using the following command

passwd ltusergt

Example

passwd ltsapsidgtadm

Checking Created UsersAs user root check all existing users as follows

1 Enter the command smitty2 Choose Security amp Users Users ChangeShow Characteristics of a User 3 To get a list of users choose F4 4 For user root and each created user ltusergt perform the following steps

a) Select ltusergtb) Change field Soft CPU time to -1 (this is the default value)c) Change field Soft CORE file size to 2097151 (this is the default value)d) Change field Soft FILE size to 4194302

Note

If you are using large file enabled file systems set the field Soft FILE size to -1 (unlimited)

e) Change field Soft DATA segment to -1f) Change field Soft STACK size to -1

You must make sure that the system-wide default HARD values are not explicitly defined to belower than the values given above Check the file etcsecuritylimits under the defaultstanza If they are not explicitly set then the values are as shown in the table at the top of the file

Checking the Operating System

1 Enter the command smitty2 Choose System Environments ChangeShow Characteristics of Operating System 3 ChangeMaximum number of PROCESSES allowed per user to 5004 To exit SMIT choose F10

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

03282008 PUBLIC 65198

3 Preparation34 Setting Up File Systems and Raw Devices

34 Setting Up File Systems and Raw Devices

The following section(s) describe the directories that are required for the instances of an SAP systemhow to set up file systems and ‒ if required ‒ raw devices on operating system level

n SAP Directories [page 66]n Oracle Directories [page 73]n Setting Up File Systems and Raw Devices for AIX [page 76]

341 SAP Directories

Depending on the installation option you have chosen SAPinst automatically creates the directorieslisted in the following figures and tablesBefore running the installation you have to set up the required file systems manually In additionyou have to make sure that the required disk space for the directories to be installed is availableon the relevant hard disksThe figure below assumes that you have set up one file system for the SAP system mount directoryltsapmntgt and one file system for the usrsap directory However you have to decide for whichdirectories you want to set up separate file systems If you do not set up any file system on yourinstallation host SAPinst creates all directories in the root directory SAPinst prompts you only for the ltsapmntgt directory during the installation See also table ParametersRelevant for the File System in Basic SAP System Parameters [page 24]


Note

For more information about how to set up your file systems if you are performing an HA installationsee High Availability Setting Up File Systems [page 46]

End of HA (UNIX)

Caution

SAPinst uses sapcpe to replicate the kernel automaticallyfrom usrsapltSAPSIDgtSYSexerunDIR_CT_RUN tousrsapltSAPSIDgtltINSTANCEgtexeDIR_EXECUTABLE for each SAP system instanceThe following entry in the start profile is responsible for thisExecute_00 = immediate $(DIR_CT_RUN)sapcpe$(FT_EXE) pf=$(_PF)where $(_PF) points to the instance profileDo not delete DIR_CT_RUN from the instance profile Otherwise you cannot restart the system afterpatches have been appliedFor more information see Applying the Latest Kernel and Support Packages [page 123]

66198 PUBLIC 03282008


Standard SAP Directories for an ABAP + Java System

Both the ABAP part and the Java part of every new installation of an ABAP+Java system are UnicodeWe still support non-Unicode for ABAP but only if you perform the system copy for a non-Unicodesystem that has been upgraded to SAP NetWeaver 70 SR3

Figure 9 SAP Directories for an ABAP + Java System (Unicode)

03282008 PUBLIC 67198


Figure 10 SAP Directories for an ABAP + Java System (ABAP Non-Unicode Java Unicode)

The instance name (instance ID) of the ABAP+Java central instance is DVEBMGSltInstance_Numbergtthe instance name of an ABAP+Java dialog instance is DltInstance_Numbergt and the instance nameof the Java central services instance is SCSltNogt


If you are performing an HA installation of your ABAP+Java system there is also an ABAP centralservices instance called ASCSltInstance_NumbergtEnd of HA (UNIX)

Example

For example the file system structure might look as followsOn a central instance with SAP system ID C11 and instance name DVEBMGS00 the J2EE Engineis installed to usrsapC11DVEBMGS00j2ee and the corresponding SDM is installed tousrsapC11DVEBMGS00SDMOn a dialog instance with instance name D01 the J2EE Engine is installed to usrsapC11D01j2ee

SAP Directories for the Diagnostics Agent

The installation creates the following SAP directories for the Diagnostics Agent

68198 PUBLIC 03282008


Figure 11 SAP Directories for the Diagnostics Agent

SAPinst extracts the Diagnostics Agent to the directoryusrsapSMDJltinstance_numbergtSMDAgent

Example

usrsapSMDJ98SMDAgent

SAP Directories in Detail

Note

The listed space requirements are initial SAP requirementsDepending on your operating system you might also have to add space for administrative purposes

The following directories are global that is they are accessed by all hosts in the SAP system

SAP Directories

Directory Description Space Required

ltsapmntgtltSAPSIDgt Software and data for one SAP systemThis directory is physically located on the SAP global hostIn homogeneous systems you need to mount it via NFS(Network File System) for all hosts belonging to the sameSAP system It contains the following subdirectoriesn exe

This directory contains executable kernel programsIf you install an SAP systemwith distributed instancesyou have to share this directory for all hosts with

n Central instance30 GBJava Add-In (ABAPsystem already exists)15 GB

n Central services instance10 GB

n Dialog instance

03282008 PUBLIC 69198



the same operating system For more informationsee Prerequisites Before Starting SAPinst Distributed Instances[page 92]

NoteSAP system ABAP (Non-Unicode) + Java onlyexe contains a folder uc with a platform-specificsubfolder ltsapmntgtltSAPSIDgtexeucltplatformgt

n global

This directory contains log filesIf you install an SAP systemwith distributed instancesyou have to share this directory for all hosts Formore information see Prerequisites Before Starting SAPinstDistributed Instances [page 92]

n profile

This directory contains the start and operationsprofiles of all instancesIf you install an SAP systemwith distributed instancesyou have to share this directory for all hosts Formore information see Prerequisites Before Starting SAPinstDistributed Instances [page 92]

This directory ismounted from theglobal host

usrsapltSAPSIDgt Instance-specific data symbolic links to the data for onesystemThis directory contains files for the operation of a localinstanceThere is a subdirectory ltINSTANCE_NAMEgt for each instanceinstalled on the local instance host The directory SYScontains only soft links to appropriate directories inltsapmntgtltSAPSIDgt for storing data used by severalinstances

NoteSAPinst creates the subfolderusrsapltSAPSIDgtltINSTANCE_NAMEgtSDM

only for the central instance of ABAP+Java or JavasystemsFor more information about SDM see Checking the JavaDocumentation [page 144]

There are subdirectories of usrsapltSAPSIDgtSYS withsymbolic links to subdirectories of ltsapmntgtltSAPSIDgtn usrsapltSAPSIDgtSYSprofile is linked to

ltsapmntgtltSAPSIDgtprofile

n usrsapltSAPSIDgtSYSglobal is linked toltsapmntgtltSAPSIDgtglobal

n Central instancel AS ABAP

20 GBl AS Java

20 GBl For BI add 20 GBl For EP add 20 GBl For PI add 10 GBl For MI add 05 GB

n Dialog instanceSee the spacerequirements abovefor the central instanceminus one third of thespace requirements forJava software units orusage types


70198 PUBLIC 03282008



n usrsapltSAPSIDgtSYSexerun is linked tousrsapltSAPSIDgtSYSexedbg which is linked toltsapmntgtltSAPSIDgtexe

NoteSAP system ABAP (Non-Unicode) + Java onlyusrsapltSAPSIDgtSYSexerun is linked toltsapmntgtltSAPSIDgtexeuc

SAPinst sets up these directory structures during theinstallationExecutables located inusrsapltSAPSIDgtSYSexerunare replicated by sapcpe to the exe directory of instancesof the type ltINSTANCE_NAMEgt SCSltNogt ASCSltNogt

NoteSAP system ABAP (Non-Unicode) + Java onlyExecutables for the exe directory of instances ofthe type SCSltNogt are replicated by sapcpe fromltsapmntgtltSAPSIDgtexeucltplatformgt

NoteMake sure that sufficient space is available in directoryusrsapltSAPSIDgtltINSTANCE_NAMEgt since this storesSAP traces for the instance Changes in SAP systemprofiles can also affect the disk space

usrsaptrans Global transport directory for all SAP systems n For the installation ofall instances 500 MB

03282008 PUBLIC 71198



For more information about exporting and mountingthe global transport directory see Exporting and Mounting theGlobal Transport Directory [page 77]The global transport directory is used by the Change andTransport System (CTS) The CTS helps you to organizedevelopment projects in the ABAP Workbench and inCustomizing and then transport the changes betweenthe SAP systems in your system landscape For moreinformation seehttphelpsapcomnw70 SAP NetWeaver 70 Library

English SAP NetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by Key CapabilitySoftware Life Cycle Management Software Logistics Change andTransport SystemIf you select the checkbox Prepare SAP System for NWDIIntegration on the screen SAP System gt NWDI Landscapeduring the Define Parameters phase of the installationSAPinst copies all SCAs belonging to the usage typesor software units you install to the global transportdirectoryFormore information see httphelpsapcomnw70

SAP NetWeaver 70 Library English SAP NetWeaver LibrarySAP NetWeaver by Key Capability Solution Life Cycle

Management by Key Capability Software Life Cycle ManagementSoftware Logistics Working with the Development InfrastructureAdministration of the Development Infrastructure Setting Up theDevelopment Landscape Landscape Configurator

n For the use of allinstances 2 GB

For more information about the directories required for the database instance see Oracle Directories[page 73]

SAP Directories for the Diagnostics Agent in Detail

Note


72198 PUBLIC 03282008



Directory DescriptionSpaceRequired

usrsapltSMDSIDgtJltinstance_numbergt Instance-specific data of the Diagnostics AgentContains the following subdirectoriesn sapinst

Contains log files of the installationn SMD Agent

Contains the Diagnostics Agent software andproperties files

n script

Contains the following local scriptsl smdstartsh

This script is used to start the localDiagnostics Agent

l smdstopsh

This script is used to stop the local DiagnosticsAgent

l smdadminsh

This script is used to manage the localDiagnostics Agent

n work

This is the work directory of the DiagnosticsAgent

usrsapltSMDSIDgtSYSprofile Contains the profiles of the Diagnostics Agentinstance

usrsapltSMDSIDgtexe Contains the following global scriptsn smdstartsh

This script is used to start one or moreDiagnostics Agent(s) available in the systemlandscape

n smdstopsh

This script is used to stop one or moreDiagnostics Agent(s) available in the systemlandscape

n smdadminsh

This script is used to manage one or moreDiagnostics Agent(s) available in the systemlandscape

500 MB

342 Oracle Directories

The figure below assumes that you have set up one file system for the oracle directory However youhave to decide yourself for which directories you want to set up separate file systems If you do not setup any file system on your installation host SAPinst creates all directories in the root directory

03282008 PUBLIC 73198


Note

Unicode systems require additional hardware resources You can find more information aboutUnicode SAP systems at httpservicesapcomunicode

Set up the required file system nodes for the Oracle database before the installation

Figure 12 Oracle Directories

Oracle Directories


oracle Oracle base directory 50 MB for Oracle software

oracleclient File system for Oracle client softwareSAPinst creates the directoryoracleclient102_64instantclient

during the installation

100 MB

oraclestage102_64 Installation and upgrade directory fordatabase software (staging area)This directory is also used for Oracleupgrades We recommend that you do notdelete it after the installation

55 GB

74198 PUBLIC 03282008



oracleltDBSIDgt Home directory of user oraltdbsidgtWe recommend that oracleltDBSIDgt doesnot reside in the root directory It mustreside in a file system with support for largefilesFor more information about how to createfile systems larger than 2 GB on youroperating system seeSetting Up File Systems and Raw Devices for AIX[page 76]Therefore either create oracleltDBSIDgtas a separate file system with support forlarge files or create oracle as a file systemwith support for large files and createoracleltDBSIDgt as a directory in oracle

100 MB for files of useroraltdbsidgt (for examplelog files)

oracleltDBSIDgt102_64 Home directory for Oracle instance ltDBSIDgt(ltORACLE_HOMEgt)ltORACLE_HOMEgtmust reside on a local disk Itcannot be a softlink

n Database instance 40GB

n All other instances200 MBMake sure that this filesystemhas permissions777

oracleltDBSIDgtoriglogA Original set A of redo logs 200 MB

oracleltDBSIDgtoriglogB Original set B of redo logs 200 MB

oracleltDBSIDgtmirrlogA Mirrored set A of redo logs 200 MB

oracleltDBSIDgtmirrlogB Mirrored set B of redo logs 200 MB

oracleltDBSIDgtoraarch New standard backup file system for Oracleoffline redo logsUse a separate disk for the file systemoracleltDBSIDgtoraarchThe file system oracleltSAPSIDgtsaparch

still remains but now only contains brbackuplog files oracleltSAPSIDgtsaparch isautomatically created by SAPinst

For the installationthe archive directoryoracleltDBSIDgtoraarch

requires at least 400 MBfree disk space For theoperation of your SAPsystem we recommendthat the archive directoryprovides enough spacefor archives between twobackups In a productionsystem the amountarchived each day isbetween 300 MB and 1 GB

oracleltDBSIDgtsapreorg Working directory for databaseadministration

15 GB

03282008 PUBLIC 75198



oracleltDBSIDgtsapdata1 SAP data




For space requirementsof the SAP data filesystems required forthe installation see thefollowing fileltExport_DVDgtEXP1

DBORADBSIZEXMLSee also SAP Note 972263Pre-Installation File

requirements of Oracle sapdatafile systems

343 Setting Up File Systems and Raw Devices for AIX

Setting up File Systems

Note

If you want to create file systems larger than 2 GB see SAP Note 129439Note that large files can lead to performance degradation due to access synchronization over thenodes For performance reasons smaller files are recommended for very active data

1 Create one logical volume for each file system listed in the appropriate SAP profilea) Using SMIT choose Physical amp Logical Storage Logical Volume Manager Logical Volumes Add a

Logical Volume b) Enter a volume group name for example sapr3vgc) Enter a logical volume name for example lvsap01d) Enter the number of logical partitionse) Press F3 until the Physical amp Logical Storagemenu appears

2 Create the file systemsa) Using SMIT choose Physical amp Logical Storage File Systems AddChangeShowDelete File Systems

Journaled File Systems Add a Journaled File System on a previously defined Logical Volume Add a StandardJournaled File System If you want to use large enabled file systems for files larger than 2 GB you have to choose Add aLarge File Enabled Journaled File System instead of Add a Standard Journaled File SystemIf you want to use JFS2 file systems you have to choose Enhanced Journaled File System insteadof Journaled File System

b) To get a list of logical volumes choose F4

76198 PUBLIC 03282008

3 Preparation35 Exporting and Mounting the Global Transport Directory

c) Select one logical volume

Caution

Select the logical volume with the desired size

d) Enter mount point as given in the file system list files

Example

oracleltDBSIDgtsapdata1

e) Set mount automatically to yesf) To exit smitty choose F10

Setting up Raw Devices

1 Create volume group2 Create logical volume

a) Enter the command smittyb) Choose Physical amp Logical Storage Logical Volume Manager Logical Volumes Add a Logical Volume c) Enter volume group named) Enter logical volume name (for example lvsap02)e) Enter the number of logical partitionsf) Set the logical volume TYPE to r3data and press ENTERg) To exit SMIT choose F10

Note

The logical volume can be accessed through devrltname of raw logvolgt

Example

A logical volume called lvsap02 points to the device name devrlvsap02

3 Accessing raw devicesIt is not necessary to create a link to access the volume

35 Exporting and Mounting the Global Transport Directory

Caution


In your SAP system landscape a global transport directory for all SAP systems is required

03282008 PUBLIC 77198

3 Preparation36 Exporting and Mounting Directories via NFS for AIX (Optional)

n If this 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 this global transport directory does not exist proceed as followsl Create the transport directory (either on the central instance host or on a file server)l Export it on the global transport directory hostl If you did not create the transport directory on your SAP instance installation host mount it

there

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 central or dialog instance host where usrsaptrans is to be mounted2 Create the mount point usrsaptrans3 Mount usrsaptrans using Network File System (NFS) from the exporting host

More InformationMounting Directories via NFS for AIX (Optional) [page 78]

36 Exporting and Mounting Directories via NFS for AIX(Optional)

There are two ways of mounting directories via NFS

n Manuallyn Using the System Management Interface Tool (SMIT)

ProcedureTo mount directories via NFS from the host where the directory to be mounted resides

1 Log on as user root2 To start NFS services at the host where the directory to be mounted resides use SMIT as follows

a) Enter the command smitty

78198 PUBLIC 03282008

3 Preparation37 Installing the Front-End Software

b) Choose Communications Applications and Services NFS Network File System (NFS) Configure NFSon this System Start NFS

c) In the line Start NFS now on system restart or both enter bothd) Choose ENTER

3 Export the directory (for example ltsapmntgtltSAPSIDgtexe) with read or read-write access forthe host where the additional instance runsa) Enter the command smittyb) Choose Communications Applications and Services NFS Network File System (NFS) Add a Directory

to Exports List c) Enter the path of the directory that you want to export (for example ltsapmntgtltSAPSIDgtexe)d) Choose export mode (use read-write or read-only as required by SAP) In the line HOSTS allowed

root access enter the name of the host where the additional instance runs For security reasonsthis root access should be disabled after the installation

e) In the line Export directory now system restart or both enter bothf) Choose ENTER

4 Create the mount point at the host where the additional instance runs usrbinmkdirltsapmntgtltSAPSIDgtexe

5 Mount the directory on the host where the additional instance runsa) Enter the command smittyb) Choose Communications Applications and Services NFS Network File System (NFS) Add a File System

for Mounting c) Enter the path name of the mount pointd) Enter the path name of the remote directory (the directory of the central instance)e) Enter the host where the remote directory residesf) SetMount now add entry to etcfilesystems or both to bothg) Set etcfilesystems entry will mount the directory on system RESTART to yesh) ChangeMount file system soft or hard to soft and press ENTER

6 If you exported the directory with read-write access check if the host where the future additionalinstance is to run has write access to directory ltsapmntgtltSAPSIDgtexe using the followingcommandscd ltsapmntgtltSAPSIDgtexe

touch test (create a file called test)

ls -l test (check if file test is created)

rm test (remove the file test)

37 Installing the Front-End Software

Caution


03282008 PUBLIC 79198

3 Preparation38 Generating the SAP Solution Manager Key

For the installation make sure that the front-end software is installed on at least one computer inyour system environmentWith the SAP Front-End installation software NW SAPSetup you can optimize the deployment of SAPGUI to thousands of clients You can easily tailor installation packages to match your requirementsdistribute patches and set up automatic update processes for your clientsWe recommend that you install SAP Front-End release 710For more information about installing the front-end software see the documentation SAP Front EndInstallation Guide - Release 710 athttpservicesapcominstallNW70 Installation Installation - Clients

38 Generating the SAP Solution Manager Key

Caution


You need to generate the Solution Manager key because the installation tool prompts for it duringthe installation Without this key the installation process cannot continueFor more information see SAP Note 805390

Procedure

1 If SAP Solution Manager is not yet available in your system landscape proceed as followsa) Order SAP Solution Manager as described in SAP Note 628901b) Install SAP Solution Manager as described in the documentation Installation Guide ‒ SAP Solution

Manager ltCurrent Releasegt on ltOSgt ltDatabasegt which is available athttpservicesapcominstguides SAP Components SAP Solution Manager ltCurrent

Releasegt2 Generate the SAP Solution Manager key as described in SAP Note 811923

ResultThe SAP Solution Manager system displays the key for which you are prompted during theinstallation of your SAP system

39 Installing the Java Development Kit

You need to prepare the system for the J2EE Engine by installing the Java Development Kit (JDK)As of SAP NetWeaver 70 you must install the J2EE Engine with strong encryptionThe J2EE Engine requires a Java Development Kit (Javatrade 2 SDK Standard Edition = JDK) on everyhost where the J2EE Engine is to be installed You need this for the system variants [page 17] with Java

80198 PUBLIC 03282008

3 Preparation39 Installing the Java Development Kit

The JDK includes the Java Runtime Environment (JRE) which is required both for SAPinst andthe SAPinst GUI

Note

If required you can perform a remote installation using a standalone SAPinst GUI on a separateWindows or UNIX host This lets you perform the installation on a remote host controlling it withthe SAPinst GUI from a local hostIf you want to perform a remote installation see Performing a Remote Installation with SAPinst [page 105] Inthis case you need at least a JRE on the local host to start the SAPinst GUI there

Procedure

1 Check the JDK versions that are released for SAP systems in the Product Availability Matrix (PAM)a) Go to httpservicesapcompamb) On the right-hand panel choose SAP NetWeaver SAP NetWeaver 70 (2004S) c) Choose tabstrip JSE Platforms

Note

For more information about the recommended JDK version for your operating system andabout how to download it see SAP Note 723909

2 Make sure a valid JDK version is installed on every host on which you want to install an SAPinstance with the J2EE Engine as followsn If the JDK is not already installed you need to download and install itn If the JDK is already installed

Check the installed version of the JDK by entering the following commandjava -version

Note

SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environmentIf SAPINST_JRE_HOME is not found SAPinst also checks JAVA_HOME

3 As of SAP NetWeaver 70 strong encryption is mandatory for the J2EE Engine and for all usage typesthat are deployed on it You need to obtain the JCE policy files beforehand so that they can beinstalled by SAPinsta) Download the JCE policy files for your platform at

httpwww6softwareibmcomdljcesdkjcesdk-pb) SAPinst installs the JCE policy files during the installation processc) Copy the JCE policy files to directory usrjava14_64jrelibsecurity

03282008 PUBLIC 81198

3 Preparation310 Preparing and Mounting the Installation Media

310 Preparing and Mounting the Installation Media

3101 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 packagen You can also download the installation DVDs from SAP Service Marketplace [page 84]

Procedure

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

Caution

The media names listed below are abbreviatedYou can find the full names of all media shipped with SAP NetWeaver 70 SR3 in the appropriateMedia List for SAP NetWeaver 70 SR3 athttpservicesapcominstallNW70 Installation Installation ‒ SAP NetWeaver Systems

Media List ‒ SAP NetWeaver 70 SR3

Note

If you are installing on an existing system using Multiple Components in One Database (MCOD)the required DVDs differ

The following table shows the required DVDs for the installation of an SAP system based on theusage type AS ABAP and AS Java

Note

The Software Component Archives (SCAs) for the installation of Java-based SAP NetWeaver usagetypes are on the SAP NetWeaver Java DVD


Note

Do not use the Business Intelligence Content Add-On DVD for the installation of BI withSAPinst You have to install the BI Content Add-On later For more information see Configuring BIJava Information Broadcasting [page 179]

End of BI Java

82198 PUBLIC 03282008


Note

For a central system where all mandatory instances reside on one host you need the installationDVDs that are required for the central instance central services instance and database instance

SAP Instance Installation Required DVDs

Central services instance central instancedialog instance

n Installation Master DVDn Kernel DVDn NetWeaver Java SP14 DVDn RDBMS Client DVD

Database instance n Installation Master DVDn Kernel DVDn NetWeaver Java SP14 DVDn RDBMS DVDn RDBMS Patch DVD (if available)

NoteFor an MCOD system you require the RDBMS ClientDVD instead of the RDBMS DVD and the RDBMS PatchDVD (if available)

n RDBMS Client DVDn SAP NetWeaver Export DVD

The following table shows the required DVDs for the installation of the Java Add-In for anexisting ABAP System

SAP Instance Installation Required DVD

Central instance central services instancedialog instance

n Installation Master DVDn Kernel DVDn NetWeaver Java SP14 DVD

Database schema n Installation Master DVDn Kernel DVDn NetWeaver Java SP14 DVDn RDBMS Patch DVD (non-MCOD)n RDBMS Client DVD (MCOD)

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

03282008 PUBLIC 83198


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 central 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 Package 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

3102 Downloading Installation DVDs from SAP ServiceMarketplace (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 athttpservicesapcomswdc Download Installations and Upgrades Entry by Application Group ltSAP

solutiongt ltSAP productgt ltSAP releasegt Installation and Upgrade ltoperating systemgt ltdatabasegt If you download installation DVDs note that DVDs might be split into several files In this case youhave to reassemble the required files after the download

PrerequisitesTo 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

Procedure

1 Create a download directory on the host on which you want to run SAPinst

84198 PUBLIC 03282008


2 Identify all download objects that belong to one installation DVD according to one or both of thefollowingn 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

3103 Mounting a CD DVD for AIX

Note

ltmedium-mountdirgt refers to either ltcd-mountdirgt or ltdvd-mountdirgt

Use the following procedure to mount a CD DVD

Procedure

1 Log on as user root2 Add a CD DVD file system

a) Enter the command smittyb) Choose Physical amp Logical Storage File Systems Add Change Show Delete File Systems CDROM

File Systems Add a CDROM File System c) To get a list of device names choose F4

Select a device named) Enter the mount point ltmedium-mountdirgt

03282008 PUBLIC 85198


Example

ltmedium-mountdirgt is sapcd

e) Choose ENTER f) To exit smitty choose F10

3 Mount the CD DVD as follows

Note

Alternatively you can mount the CD DVDmanually with the following command mount -v

cdrfs -r devcd0 sapcd

a) Enter the command smittyb) Choose Physical amp Logical Storage File Systems Mount a File System c) Place the cursor on File System Name and choose F4 d) Select the CD DVD device devcd0e) Place the cursor on field Directory over which to mount and choose F4 f) Select sapcdg) Place the cursor on field Type of File System and choose F4 h) Select cdrfsi) ChangeMount as Read Only system to YESj) Choose ENTER k) To exit smitty choose F10

86198 PUBLIC 03282008

4 Installation

4 Installation

Note

Make sure that you have completed the planning and preparation activities before you start theinstallation

This section provides information about the steps that you have to perform to install your SAP system

Process Flow

1


If required you perform a high-availability installation [page 87]End of HA (UNIX)

2 You check the prerequisites for the instances that you want to install before starting SAPinst [page 89]3 You install your SAP system using SAPinst [page 93]

Note

This note does not apply to the installation of a Java Add-In to an existing ABAP systemDo not install the Oracle database software before you run SAPinstSAPinst stops and prompts you to install the Oracle database [page 108] while the installation of thedatabase instance is runningIf you install a system into an existing database (MCOD) this action is not required


41 Performing a High-Availability Installation

This section describes how to perform a high-availability (HA) installation For more informationconsult your HA partner

Prerequisites

n You have completed all preparations including preparing the installation of switchover units [page 44]n You have set the environment variable SAPINST_USE_HOSTNAME [page 93] to specify the virtual host

name for the installation Alternatively you can specify the virtual host name in the commandto start SAPinst

03282008 PUBLIC 87198

4 Installation41 Performing a High-Availability Installation

Caution

If you install the Java Add-In to an existing ABAP system note the followingl When you install the central services instance SAPINST_USE_HOSTNAMEmust point to the

virtual host name under which the central services instance is to runl When you install the database instance SAPINST_USE_HOSTNAMEmust point to the virtual

host name under which the database is installedl When you install the central instance SAPINST_USE_HOSTNAMEmust point to the virtual

host name under which the central instance is installed

Procedure

1 Run SAPinst [page 94] to install the central services instances (SCS and ASCS) using the virtual hostname on the primary cluster node host A

2 Prepare the standby node host B making sure that it meets the hardware and softwarerequirements and it has all the necessary file systems mount points and (if required) NetworkFile System (NFS) as described in Preparing for Switchover [page 44]

3 Set up the user environment on the standby node host BFor more information see Creating Operating System Users and Groups Manually [page 63] Make sure thatyou use the same user and group IDs as on the primary node Create the home directories of usersand copy all files from the home directory of the primary node

4 Configure the switchover software and test that switchover functions correctly5 Install the database instance on the primary node host A6 Install the central instance with SAPinst [page 94] on the primary node host A

Note

In a high-availability installation the central instance does not need to be part of the clusterbecause it is no longer a single point of failure (SPOF) The SPOF is now in the central servicesinstance (SCS) which is protected by the clusterIn a high-availability installation the central instance does not need to be part of the clusterbecause it is no longer a single point of failure (SPOF) The SPOF is now in the central servicesinstance (ASCS) which is protected by the clusterIn a high-availability installation the central instance does not need to be part of the clusterbecause it is no longer a single point of failure (SPOF) The SPOF is now in the central servicesinstances (SCS and ASCS) which are protected by the cluster

7 If required install additional dialog instances with SAPinst [page 94] to replicate the SAP system servicesthat are not a SPOF These nodes do not need to be part of the cluster

88198 PUBLIC 03282008

4 Installation42 Prerequisites before Starting SAPinst

Note

Make sure that you complete the activities described in High Availability Post-Installation Steps [page 134]

End of HA (UNIX)

42 Prerequisites before Starting SAPinst

421 Prerequisites before Starting SAPinst All Instances

This section provides information about running SAPinst that is valid for the installation of allinstances (central central services database and dialog instance)

Prerequisites

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

n Check that your installation hosts meets the requirements for the installation services that youwant to install For more information see Running the Prerequisite Checker [page 50]

Procedure

1 If you want to install a dialog instance for an upgraded SAP systema) Edit DEFAULTPFLb) Insert a line with the parameter rdispmsserv_internal and set it to a free port number

Note

Bear in mind that for AIX 53 the port 39ltSCS_instance numbergt is used by the NIM server ofAIX

c) Edit the instance profile of the central services instanced) Set the parameter rdispmsserv to 0e) Insert a line with the parameter rdispmsserv_internal and set it to the port number that was

assigned before to rdispmsserv

03282008 PUBLIC 89198


f) Restart all instances of the SAP system

Example

This shows the required change to the instance profiles

n DEFAULTPFL

Before the changerdispmsserv = sapmsltSAPSIDgt

After the changerdispmsserv = sapmsltSAPSIDgt

rdispmsserv_internal = ltfree port numbergt

n Instance profile of the central services instance

Before the changerdispmsserv = 4711

After the changerdispmsserv = 0

rdispmsserv_internal = 4711

2 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 entry

Note

SAPinst normally creates the installation directory sapinst_instdir directly below thetemporary directory SAPinst finds the temporary directory by checking the value of theenvironment variables TEMP TMP or TMPDIR If no value is set for these variables SAPinst usestmp as default installation directoryMake sure that the temporary directory has the permissions 777The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory Theseexecutables are deleted again after SAPinst has stopped runningIf required you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C

90198 PUBLIC 03282008


Caution

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

3 Make sure that you have at least 60MB of free space in the installation directory for each installationservice 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

Shell Used Command

Bourne shell (sh) TEMP=ltdirectorygt

export TEMP

C shell (csh) setenv TEMP ltdirectorygt

Korn shell (ksh) export TEMP=ltdirectorygt

4 If you are installing a second or subsequent SAP system into an existing database make surethat the database is up and running before starting the installation For more information seeInstallation of Multiple Components in One Database [page 149]

5 Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java RuntimeEnvironment (JRE)

6 If the operating system is AIX 64-bit make sure that the PATH variable points to a JDKJRE forAIX 64-bit

7 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

8 Check the following values for user rootn In csh execute limit

Output Properties

cputime unlimited

filesize unlimited

datasize 2097148 KB

stacksize 8192 KB

coredumpsize unlimited

03282008 PUBLIC 91198


Output Properties

descriptors 8192

memorysize unlimited

n In sh or ksh execute ulimit -a

Output Properties

time(seconds) unlimited

file(blocks) unlimited

data(kbytes) 2097148

stack(kbytes) 8192

coredump(blocks) unlimited

nofiles(descriptors) 8192

memory(KBytes) unlimited

If your parameter settings differ from the settings above change these values accordingly

Example

If you have to change the value for descriptors to 8192 proceed as followsl In csh execute

limit descriptors 8192

l In sh or ksh executeulimit -n 8192

422 Prerequisites before Starting SAPinst DistributedInstances

If you install a database or a dialog instance on a host other than the SAP Global host you mustmount directories from the SAP Global host

Prerequisites

n If you want to install the executables locally instead of sharing them do notmount the exedirectory with Network File System (NFS) Instead create ltsapmntgtltSAPSIDgtexe as a localdirectory (not a link) with a minimum of 1100 MB free space

n If you are installing a heterogeneous SAP system (that is the instances are installed on differentoperating-system platforms) do notmount the exe directory For more information seeHeterogeneous SAP System Installations [page 180]

92198 PUBLIC 03282008

4 Installation43 Installing an SAP System Using SAPinst

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


ltsapmntgtltSAPSIDgtglobal

For more information seeMounting Directories via NFS for AIX [page 78]

Caution

Make sure that the global transport directory is mounted on every host where you want to installan SAP instance For more information see Exporting and Mounting the Global Transport Directory [page77] Otherwise the installation fails

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

ltsapmntgtltSAPSIDgtexe




423 Prerequisites Before Starting SAPinst High Availability

For a high-availability (HA) SAP system you can set the environment variable SAPINST_USE_HOSTNAMEto specify the virtual host name before you 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 94]

ProcedureSet SAPINST_USE_HOSTNAME to the virtual host name of the machine on which you are installingan SAP instanceEnd of HA (UNIX)

43 Installing an SAP System Using SAPinst

The following sections tell you how to install the various instances of an SAP system or a standaloneengine

n Running SAPinst on UNIX [page 94]n Installing a Java Add-In for an Existing ABAP System with SAPinst [page 101]

03282008 PUBLIC 93198


n Using SAPinst GUI [page 103]n Interrupted Installation with SAPinst [page 104]n Performing a Remote Installation with SAPinst (Optional) [page 105]n Starting SAPinst GUI Separately (Optional) [page 106]n Entries in the Services File Created by SAPinst [page 108]

431 Running SAPinst on UNIX

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 105] 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

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 central instance a central services instance a database instance or a dialoginstance 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 AIX [page 85]

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

Enter the following commandscd ltInstallation Master_DVDgtIM_ltOSgt

sapinst

94198 PUBLIC 03282008



Note

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

End of HA (UNIX)

Caution

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 entry

Caution

Make sure that your current working directory is not an IM_ltOSgt directory belonging toanother operating systemFor example the following commands are incorrect and cause an error$ cd sapcd2IM_HPUX_IA64

$ sapcd2IM_HPUX_PARISCsapinst

The following commands are correct$ cd sapcd2IM_HPUX_PARISC


n Using an alternative installation directoryIf you want to use an alternative installation directory set the environment variable TEMPTMP or TMPDIRFor more information see Prerequisites before Starting SAPinst All Instances [page 89]

Note

n During the installation the default ports 21200 and 21212 are used for communication betweenSAPinst GUI server and SAPinst GUI SAPinst uses port 21200 to communicate with the GUIserver The GUI server uses port 21212 to communicate with SAPinst GUI You get an errormessage if 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_guigtn To get a list of all available SAPinst properties start SAPinst as described above with the option

-p

03282008 PUBLIC 95198


sapinst -p4 In theWelcome screen choose one of the following installation optionsn SAP Systems

n Software Life-Cycle OptionsThe following tables provide more information about these installation optionsn SAP Systems

You use this option to install an SAP system with usage types or software units by choosingl Central system

ltSAP systemgt SAP Systems ltDatabasegt Central System

l All other system variantsltSAP systemgt SAP Systems ltDatabasegt ltSystem Variantgt Based on lttechnical stackgt

You can install the following system variantsl Central Systeml Distributed System

l


High Availability SystemEnd of HA (UNIX)

The following tables provide an overview of the installation options available for these systemvariants

Note

l Choose the corresponding installation options from the tree structure exactly in theorder they appear for each system variant

l To use global accounts that are configured on a separate host you have to run theinstallation option Operating System Users and Groups before you start the installation

l If required to install a dialog instance for a central or distributed system chooseSoftware Life-Cycle Options Application Server Dialog Instance

See table Software Life-Cycle Options belowl On the SAPinst screens the term ldquosoftware unitrdquo generally applies to both SAP NetWeaver

usage types and SAP Business Suite software units

Installation Services for a Central System

Installation Service Remarks

Central System Installs a complete SAP system including the following instances on onehostl Central services instance (SCS)l Database instancel Central instanceYou can install a central system in the following parameter modesl Typical Mode

96198 PUBLIC 03282008



If you choose Typical the installation automatically uses defaultsettings You only have to respond to a small selection of promptsHowever you can change any of the default settings on the parametersummary screen

l Custom ModeIf you choose Custom the installation prompts you for all parametersAt the end you can change any parameter on the parameter summaryscreen

NoteYou require at least the usage types AS Java and AS ABAP You can choosethe usage types or software units on the screen SAP System gt Software Units

Installation Services for a Distributed System

Installation Services Remarks

Central Services Instance (SCS) Mandatory step in installing a distributed SAP system withusage types or software units based onASABAP and AS JavaInstalls a central services instance (SCS) and prepares theSAP global host

Database Instance Mandatory step in installing a distributed SAP systemInstalls a database instanceYou must have finished the Central Services Instance (SCS)installation before you can choose this installation service

Central Instance Mandatory step in installing a distributed SAP system onseveral hostsInstalls a central instance and enables additional usagetypes or software units

NoteYou require at least usage type AS Java or AS ABAP Youcan choose the usage types or software units on thescreen SAP System gt Software Units

You must have finished the database instance installation

Installation Services for a High Availability System


Central Services Instancefor ABAP (ASCS)

Installs a central services instance for ABAP (ASCS) and prepares the SAPglobal host

Central Services Instance(SCS)

Installs a central services instance (SCS)

03282008 PUBLIC 97198



Database Instance Installs a database instance

Central Instance Installs a central instance and enables additional usage types or softwareunits


Dialog Instance Installs a dialog instance

Notel If you want to use 32-bit SAP NetWeaver components first check

whether these components can run on 64-bit operating systems If sowe recommend you to use 64-bit systems If not you can install an SAPdialog instance on 32-bit operating systems to run these componentsFor all other SAP instances you must use 64-bit systems

l We do not support operating an ABAP dialog instance with anABAP+Java system

l You cannot install the Java Add-In for existing ABAP dialog instance(s)Instead you have to install new ABAP+Java dialog instance(s)

n Software Life-Cycle OptionsYou use this option to perform the following tasks or to install the following components


Additional PreparationOptions

These preparation tasks comprisel Operating System Users and Groups

Allows you to use global accounts that are configured on a separatehost

CautionPerform this SAPinst option before you start the installation ofyour SAP system

l Prerequisites CheckChecks your hardware and software requirements before youstart the installationOtherwise SAPinst automatically checks the hardware andsoftware requirements during the installation with the PrerequisiteChecker If any changes are necessary to the SAP system or operatingsystem settings SAPinst automatically prompts you For moreinformation see Running the Prerequisites Checker in Standalone Mode [page50]

98198 PUBLIC 03282008



Application Server Choose Application Server ltDatabasegt Dialog Instance to installone or more dialog instance(s) in an already installed SAP systemif required


whether these components can run on 64-bit operating systemsIf so we recommend you to use 64-bit systems If not you caninstall an SAP dialog instance on 32-bit operating systems to runthese components For all other SAP instances you must use64-bit systems


l You cannot install the Java Add-In for existing ABAP dialoginstance(s) Instead you have to install new ABAP+Java dialoginstance(s)

Java Add-In for ABAP Choose this service to install usage types based on AS Java to an alreadyinstalled SAP ABAP systemFor more information see Installing a Java Add-In for an Existing ABAPSystem with SAPinst [page 101]

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

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

You have to configure the directory server only once Afterwardsall SAP systems that should register in this directory server canuse this setup

NoteThe option Active Directory Configuration is only available forWindows

b) Installed an application server instanceFor more information about LDAP and Active Directory see Integrationof LDAP Directory Services [page 151]

System Copy Choose this service to perform a system copyFor more information see the system copy guide which is available athttpservicesapcominstguidesnw70 Installation Installation

‒ SAP NetWeaver Systems

03282008 PUBLIC 99198



Java Add-In for ABAP Choose this service to install usage types based on AS Java to anexisting ABAP systemFor more information see Installing a Java Add-In for an Existing ABAPSystem with SAPinst [page 101]

Uninstall Choose this service to uninstall your SAP system standalone enginesor optional standalone unitsFor more information see Deleting an SAP System Using SAPinst [page 183]

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 field of the respective parameter and press F1

After you have entered all requested input parameters SAPinst displays the Parameter Summary screenThis screen shows both the parameters that you entered and those that SAPinst set by default

6 If required change the displayed parameters as followsa) Select the parameters you want to changeb) Choose Revise

SAPinst displays input screens for the selected parametersc) Enter the new values for the parameters

7 To start the installation choose StartSAPinst starts the installation and displays the progress of the installationWhen the installation has successfully completed SAPinst displays the screen Finished successfully

Note

During the installation of the Oracle database instance SAPinst stops the installation and promptsyou to install the Oracle database software [page 108]This action is not required if you install a system into an existing database (MCOD)After you have finished the installation of the Oracle database you continue the database instanceinstallation by choosing OK in the SAPinst GUI of the database instance installation

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

Note

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

100198 PUBLIC 03282008


Recommendation

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

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

installation has successfully completed

More InformationIf you have problems during the installation see Troubleshooting with SAPinst [page 181]

432 Installing the Java Add-In for an Existing ABAP System(Optional)

This section describes how to install the Java Add-In for an existing ABAP system

Caution

Keep in mind that you cannot install the Java Add-In for existing ABAP dialog instance(s) Insteadyou have to uninstall the old ABAP dialog instance(s) and install new ABAP+Java dialog instance(s)as followsOn theWelcome screen in SAPinst choose ltSAP systemgt Software Life-Cycle Options ApplicationServer ltdatabasegt Dialog Instance

PrerequisitesYour ABAP system must be based on SAP NetWeaver 70 SR3 (SPS 14)Make sure that the parameter compatible is set to 1020 in the file initltdbsidgtora

Procedure

1 Start SAPinst [page 94]2 On theWelcome screen choose ltSAP systemgt Software Life-Cycle Options Java Add-In for ABAP

ltdatabasegt ltsystem variantgt 3 Choose the corresponding installation services from the tree structure exactly in the order they

appear for each system variant as shown in the following tables

03282008 PUBLIC 101198


Installation Services for a Java Add-In for ABAP ‒ Central or Distributed System


Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) and adds usagetypes or software units based on AS Java

Database Instance Java Add-In Installs the Java schema in the database of your ABAP system

Central Instance Java Add-In Adds usage types or software units based on AS Java

CautionWhen performing an upgrade installation before you usethis option uninstall the old ABAP dialog instance(s)

Installation Services for a Java Add-In for ABAP ‒ High-Availability System





Dialog Instance Installs an ABAP+Java dialog instance

Noten If you want to use 32-bit SAP NetWeaver components

first check whether these components can run on64-bit operating systems If so we recommend youto use 64-bit systems If not you can install an SAPdialog instance on 32-bit operating systems to run thesecomponents For all other SAP instances you must use64-bit systems

n We do not support operating an ABAP dialog instancewith an ABAP+Java system

n You cannot install the Java Add-In for existing ABAPdialog instance(s) Instead you have to install newABAP+Java dialog instance(s)When performing an upgrade installation beforeyou use this option uninstall the old ABAP dialoginstance(s)


Note

SAPinst prompts you for the production client of your ABAP system which is where you installthe Java Add-In

102198 PUBLIC 03282008


After you have entered all required input parameters SAPinst starts the installation and displaysthe progress of the installation

ResultAfter running these installation services your ABAP+Java system consists of the following instances

n Java central services instance (SCS)n ABAP+Java database instancen ABAP+Java central instance

433 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 input parameter

Menu option File Log off Stops the SAPinst GUI but SAPinst and the GUI server continuerunning

NoteIf for some reason you need to log off during the installationfrom the host where you control the installation with SAPinstGUI the installation continues while you are logged off You canlater reconnect to the same SAPinst installation from the same oranother host For more information see Starting SAPinst GUI Separately[page 106]

Menu option File View Log Displays the installation log (sapinst_devlog)

Menu option File Exit Cancels the installation with the following optionsn Stop

For more information see the description of the message buttonbelow

n ContinueFor more information see the description of the message buttonbelow

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

Message button View Log Displays the installation log (sapinst_devlog)

Message button Stop Stops the installation (SAPinst GUI SAPinst and the GUI server)without further changing the installation files You can continue theinstallation later from this point

Message button Continue Continues with the option you have chosen before

03282008 PUBLIC 103198


434 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

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

104198 PUBLIC 03282008


Note

Mount the DVD locally We do not recommend using Network File System (NFS)

3 Enter the following commandscd ltInstallation_Master_DVDgtIM_ltOSgt

sapinst

4 From the tree structure in theWelcome screen select the installation service 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

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

435 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 89]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

03282008 PUBLIC 105198


Procedure

1 Log on to your remote host as user root

Caution


2 Mount the Installation Master DVD3 Enter the following commands

cd ltInstallation_Master_DVDgtIM_ltOSgt

sapinst -nogui

For more information see Running SAPinst on UNIX [page 94]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 106]

436 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 105]If you want to run SAPinst GUI on a different host from SAPinst and the GUI server you have tostart SAPinst GUI separately

PrerequisitesYou have installed the Java Development Kit [page 80] on the host on which you want to start SAPinstwithout SAPinst GUI

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 Open a command prompt and change to the relevant directory

ltDVD drivegtIM_WINDOWS_ltplatformgt

4 Start SAPinst GUI in one of the following ways

106198 PUBLIC 03282008


n If SAPinst GUI runs on the same host as SAPinst and the GUI server enter the followingcommandstartinstguibat

SAPinst GUI uses the local host as defaultn If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation)

enter the following commandstartinstguibat -host lthost_namegt

lthost_namegt is the host name of the installation host

Note

l If you enter the command without additional parameters SAPinst GUI uses the local hostas default SAPinst GUI starts and tries to connect to the GUI server and SAPinst SinceSAPinst and the GUI server are running on another host SAPinst GUI cannot connect andthe SAP 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 installationfrom your local host

l For a list of options to start SAPinst GUI change to the same directory as your SAPinstexecutable and enter the command startinstguibat -h

Starting SAPinst GUI on a UNIX Platform

1 Log on as user root

Caution


2 Mount your installation DVD

Note

Mount the DVD locally We do not recommend that you use Network File System (NFS)

3 To change to the mount directory enter the following commandcd ltInstallation_Master_DVDgtIM_ltOSgt

4 Start the SAPinst GUI in one of the following waysn If SAPinst GUI runs on the same host as SAPinst and the GUI server enter the following

command without additional parametersstartInstGuish

SAPinst GUI uses as default the local host

03282008 PUBLIC 107198

4 Installation44 Oracle Database Software Installation

n If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation)enter the following command with additional parametersstartInstGuish -host lthost_namegt


Note

l If you enter the command without additional parameters SAPinst GUI uses the local hostas default SAPinst GUI starts and tries to connect to the GUI server and SAPinst SinceSAPinst and GUI server are running on another host SAPinst GUI cannot connect and theSAP Installation GUI Connection dialog appearsIn this case enter the name of host on which SAPinst is running and choose Log onThe first dialog of the installation appears and you can perform the remote installationfrom your local host

l For a list of options to start SAPinst GUI change to the same directory as your SAPinstexecutable and enter the command startInstGuish -h

437 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

44 Oracle Database Software Installation

SAPinst prompts you to install the Oracle database

Caution


Proceed as follows to install the Oracle database software

108198 PUBLIC 03282008


Process Flow

1 You update SAP-specific files in the Oracle stage area [page 109]2 You perform steps for the AIX operating system [page 109]3 You run the Oracle Universal Installer [page 110]4 You install the current patch set [page 112]5 You install required interim patches [page 112]

441 Updating SAP-Specific Files in the Oracle Staging Area

SAPinst extracts the Oracle RDBMS software to the staging area usuallyoraclestage102_64databaseThe SAP folder located in oraclestage102_64database contains SAP-specific scripts as wellas the response filesBefore starting the Oracle software installation you need to update this SAP folder so that the newestversions of the scripts or response files are used

Procedure

1 Rename the original SAP folder by performing one of the following

n mv oraclestage102_64databaseDisk1SAP

oraclestage102_64databaseDisk1SAP_ORIG

n mv oraclestage102_64databaseSAP

oraclestage102_64databaseSAP_ORIG

2 Download the file RDBMS_SAP_64zip attached to SAP Note 819830 and copy it to a temporarylocation such as tmp

3 Extract the zip file by performing one of the following

n cd oraclestage102_64database

unzip tmpRDBMS_SAPzip

n cd oraclestage102_64databaseDisk1


You should now see the directory SAP extracted with the updated version of SAP-specific files

442 Performing Steps for the AIX Operating System

To install the Oracle database software on the AIX operating system you need to run the rootpreshscript to adapt the AIX kernel and also execute a command as the root user

03282008 PUBLIC 109198


PrerequisitesIf several Oracle instances run on one computer you must shut these down before adapting thekernel

Procedure

1 Run the rootpresh script as followsa) Log on to the system with user oraltdbsidgt if you are not already logged onb) Change to the directory oraclestage102_64databaseDisk1rootpre using the following

commandcd oraclestage102_64databaseDisk1rootpre

c) Make sure that the user root is assigned the environment of oraltdbsidgtsu root

d) Call the script rootpreshrootpresh

e) Log off with the user rootexit

2 Remove any currently unused modules in kernel and library memory by entering the followingcommand as user root usrsbinslibclean

443 Running the Oracle Universal Installer

To install the Oracle database software you run the Oracle Universal Installer (OUI)

Procedure

1 Log on as user oraltdbsidgtSince you are already logged on as user root you can switch to user oraltdbsidgt by entering thefollowing commandsu ndash oraltdbsidgt

2 If you install Oracle database software with Release 10201 or 1020x on a new operating system ora new operating system version the Oracle Universal Installer might not yet recognize or supportthis operating system Follow the instructions in SAP Note 980426

3 Make sure that the DISPLAY environment variable is set to lthost_namegt00 where lthost_namegtis the host on which you want to display the GUI of the Oracle Universal Installer (OUI)

Shell Used Command


export DISPLAY

110198 PUBLIC 03282008


Shell Used Command



4 Start the OUI by entering one of the following

n cd oraclestage102_64databaseDisk1SAP

RUNINSTALLER

n cd oraclestage102_64databaseSAP

RUNINSTALLER

You see a message that a response file is being generated It might take several minutes before yousee the OUI screen

5 Respond to the OUI as follows

Prompt or Condition Action

When you run the OUI for the first time on this hosta dialog box Specify File Locations Destination appearsThis dialog box proposes the inventory location asoracleoraInventory and the installation groupas dba

Accept the OUI proposal and continue by choosingNext

Available Product Components Confirm the default selections by choosing Next

Product-Specific Prerequisite ChecksThis phase checks if all necessary requirements forinstalling and running the database have been met

For items that are flagged as warnings or failedreview the cause for the warning or failure on screenand fix the problem if possibleAlternatively you can verify the items manuallyand confirm them by clicking the checkbox Youcan find details about each check by clicking on therelevant item

Summary page Check the information on this page and then startthe installation

When the Install step has completed a dialog boxappears

Execute the file $ORACLE_HOMErootshwith the userroot and confirm the dialog box by choosing OKIf this is the first time that the Oracle softwarehas been installed on this host the OUIalso asks you to execute a second scriptoracleoraInventoryorainstRootsh as the rootuser Execute this script as wellContinue by choosing Next

6 At the end of the installation in case there are any Configuration Assistants that have been startedautomatically (for example Oracle Net) choose Cancel and terminate the Net Config AssistantYou can ignore messages that some of the config assistants failed to complete successfully

03282008 PUBLIC 111198


The Installer finishes reporting that the Oracle installation was successful It also informsyou about the services that it started You can find the port numbers for these services in the$ORACLE_HOMEinstallportlistini file

7 To exit the OUI choose Exit and confirm the dialog box that appears

Note

You can now access the Oracle 102 online documentation which was installed duringthe last step You can find the entry point to the Oracle online documentation at$ORACLE_BASEdocindexhtm

444 Installing the Current Patch Set

After the Oracle database software installation you need to install the current Oracle Database10g Release 2 (102) patch set

Prerequisites

n For more information on the latest patch set available for Oracle 102 see SAP Note 871735n For more information about how to install the patch set see the patch set README file

Caution

Do not perform any of the post-installation steps mentioned in the patch set README file Thepost-installation steps are to be performed only on an existing Oracle 102 databaseAt this stage you have only installed the Oracle 102 software The database itself is still not Oracle102 Therefore make sure that you do not perform the post-installation steps mentioned inthe README file

n You only have to install the latest (that is the current) patch set

Procedure

1 Log on at the operating system level with the oraltdbsidgt user2 Download and extract the patch set as described in SAP Note 9322513 Install the patch set as described on the patch set README file

445 Installing Required Interim Patches

After the Oracle database software installation you need to install required interim patches using theOracle tool OPatch You need these interim patches in addition to the current patch set

112198 PUBLIC 03282008


Prerequisites

n Make sure you have already installed the current patch set [page 112]n Check SAP Note 871096 to find the list of required patches to be installedn Check SAP Note 839182 for instructions on how to use OPatch

Procedure

1 Log on at the operating system level as the oraltdbsidgt user2 Install the patches following the instructions in SAP Note 839182

Note

You can apply the patches in any orderWe recommend that you first copy the patches to a directory called ora_patches in $ORACLE_HOME

3 After all the patches have been successfully applied you can query the status with the followingcommand$ORACLE_HOMEOPatchopatch lsinventory

This command lists all the patches that have been applied to the software installation

03282008 PUBLIC 113198


5 Post-Installation

5 Post-Installation

Note

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

You perform the following post-installation steps

1 If you have installed software units or usage types based on AS Java you update database statistics[page 117]

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

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

Only valid for Enterprise Portal (EP)EP Core (EPC)

You check whether you can log on to the portal [page 119]

Note

In a distributed or high-availability system you check whether your can log on to the portal fromevery instance of the SAP system that you installed

End of Enterprise Portal (EP)EP Core (EPC)

4


You check whether you can log on to SAP NetWeaver Development Infrastructure [page 120]End of Development Infrastructure (DI)

5 You install the SAP license [page 121]

Caution

This step does not apply to the installation of a Java Add-In for an existing ABAP system

6 You install the SAP Online Documentation [page 122]

Caution


03282008 PUBLIC 115198

5 Post-Installation

7 You configure the remote connection to SAP support [page 122]

Caution


8 On the central instance host you apply the latest kernel and Support Packages [page 123]9 You perform initial ABAP configuration [page 125]

Caution


10 On the database instance host you perform the Oracle-specific post-installation steps [page 127]

Caution


11 You perform the client copy [page 128]

Caution


12 You perform a full backup of the installation [page 129]13 You perform post-installation steps for Adobe Document Services [page 130]

14

Only valid for BI JavaProcess Integration (PI)

You set the environment variable CPIC_MAX_CONV [page 133]End of BI JavaProcess Integration (PI)

15


You perform the post-installation steps for usage type Process Integration (PI) [page 133]End of Process Integration (PI)

16


You perform the post-installation steps required for Application Sharing Server [page 134]End of Enterprise Portal (EP)

17


You perform the required post-installation steps for high availability [page 134]

Caution


End of HA (UNIX)

116198 PUBLIC 03282008

5 Post-Installation51 Updating Database Statistics

18 You ensure user security [page 136]

19

Only valid for Application Server (AS)BI JavaDevelopment Infrastructure (DI)Mobile Infrastructure (MI)Process Integration (PI)

To perform basic configuration steps on the central instance host you run the Configuration Wizard[page 142]

Caution


End of Application Server (AS)BI JavaDevelopment Infrastructure (DI)Mobile Infrastructure (MI)Process Integration (PI)

20 You check the Java documentation [page 144] for information that is relevant for running your Java system21 You can now start with the manual configuration of your IT scenarios for which you can find the

appropriate documentation in the SAP Solution Manager [page 145]22 If you want or need to implement the E2E Root Cause Analysis scenario you have to perform

post-installation steps for the Diagnostics Agent [page 147] on your central instance andor dialog instance(s)

51 Updating Database Statistics

You have to update database statistics if you have installed software units or usage types basedon AS Java

PrerequisitesThe database is up and running

Procedure

1 Log on as user oraltdbsidgt to the host where the database instance is running2 Open a command prompt and execute the following command

brconnect -u -c -f stats -t all -o SAPltSCHEMA_IDgt

Example

brconnect -u -c -f stats -t all -o SAPQO1DB

52 Logging On to the Application Server

You need to check that you can log on to the SAP system using the following standard users

03282008 PUBLIC 117198

5 Post-Installation52 Logging On to the Application Server

ABAP Users

User User Name Client

SAP 000 001 066SAP system user

DDIC 000 001

Java User

User User Name Storage ABAP System

Administrator J2EE_ADMIN (default) or the name you gave this user during theinstallation process

Prerequisites

n The SAP system is up and runningn You have already installed a front end

Logging On to the ABAP Application Server

1 Start SAP Logon on the host where you have installed the front end as followsn SAP GUI forWindows

Choose Start All Programs SAP Front End SAP Logon n SAP GUI for Java

Choose Start All Programs SAP Clients SAP GUI for JavaltReleasegt

Note

You can also enter the command guilogon in the SAP GUI installation directory to startSAP GUI for Java

The SAP Logon appears2 Create a logon entry for the newly installed system in the SAP Logon

For more information about creating new logon entries press F1 3 When you have created the entry log on as user SAP or DDIC

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_J2EE_Engine_Servergt5ltInstance_Numbergt00

118198 PUBLIC 03282008

5 Post-Installation53 Logging on to the Portal

Note

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

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 link of any of the provided applications for example the SAP NetWeaver

Administrator or the System Information

Note

To deactivate AS Java proceed as follows

1 Call transaction RZ112 In the instance profile of every installed SAP instance set parameter rdispj2ee_start from 1

to 0


53 Logging on to the Portal

You need to check that you can log on to the application server using the following standard usersThis procedure applies when you install usage type EPC only and when you install it together withusage type EP

Java User



PrerequisitesThe SAP system is up and running

ProcedureYou access the portal with a URL using a Web browser from your client machines

03282008 PUBLIC 119198

5 Post-Installation54 Logging on to SAP NetWeaver Development Infrastructure (NWDI)

The default URL consists of the installation host name and the port on which the portal is listeningYou can use the HTTP or HTTPS protocol HTTPS is relevant if you are using Secure Sockets Layer(SSL) communication

1 Start a Web browser and enter the following URLhttplthostname_of_J2EE_Engine_Servergt5ltInstance_Numbergt00irj

Note

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

Example

If you installed the portal on host saphost06 and the instance number of your SAP NetWeaverApplication Server Java is 04 enter the following URLhttpsaphost0650400

2 Log on by entering the required user and password



54 Logging on to SAP NetWeaver Development Infrastructure(NWDI)

You have to log on to the services of SAP NetWeaver Development Infrastructure (NWDI) to checkwhether the installation of the usage type DI was successful

Procedure

1 Start a Web browser and enter the following URLhttplthostname_of_J2EE_Engine_Servergt5ltInstance_Numbergt00devinf

Note


Example

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

120198 PUBLIC 03282008

5 Post-Installation55 Installing the SAP License

2 Log on with the user NWDI_ADMINThe start page SAP NetWeaver Development Infrastructure appears in the Web browserYou should see the following linksn Design Time Repository

n Component Build Service

n Change Management Service

n System Landscape Directory3 Log on to these services one after another by clicking the appropriate link

a) When you click Design Time Repository you should see the Design Time Repository page with theRepository Browser overview

b) When you click Component Build Service you should see the Component Build Service page with the CBSBuildspace Information

c) When you click Change Management Service you should see the Change Management Service pagewith the CBS Buildspace Information

d) When you click System Landscape Directory you should see the System Landscape Directory start page

Note

The tables displayed on the pages may be empty They are filled when you configure thedevelopment infrastructure either by running the Configuration Wizard [page 142] or by configuringyour system manually


55 Installing the SAP License

Caution


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 more information about the installation procedure for the SAP license see

03282008 PUBLIC 121198

5 Post-Installation56 Installing the SAP Online Documentation

httphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library TechnologyConsultantrsquos Guide Cross-NetWeaver Configurations SAP License Key


If you have installed a high-availability system proceed as described in High Availability Setting UpLicenses [page 134]End of HA (UNIX)

More InformationFor more information about SAP license keys see httpservicesapcomlicensekey

56 Installing the SAP Online Documentation

Caution


SAP currently provides an HTML-based solution for the online documentation including theApplication Help Glossary Implementation Guide (IMG) and Release Notes You can display thedocumentation with a Java-compatible Web browser on all front-end platforms supported by SAPYou can always find the up-to-date SAP online documentation at httphelpsapcom

ProcessInstall the SAP online documentation in your SAP system as described in the READMETXT filecontained in the root directory of the online documentation DVD delivered as part of the installationpackage

57 Configuring Remote Connection to SAP Support

Caution


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

122198 PUBLIC 03282008

5 Post-Installation58 Applying the Latest Kernel and Support Packages

58 Applying the Latest Kernel and Support Packages

You use this procedure to apply the latest kernel and Support Packages for your SAP system from SAPService Marketplace

Note

The following are available exclusively through the Maintenance Optimizer in SAP SolutionManager

n All corrective software packages including Support Packages (Stacks) for SAP NetWeaver 70 andsubsequent versions

n All applications based on this software (including SAP Business Suite 2005) released after April2 2007

For more information about the Maintenance Optimizer seehttpservicesapcomsolutionmanager SAP Solution Manager in Detail

Change Request Management Maintenance Optimizer

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 appliedSee also Setting Up File Systems [page 66]

Caution

You must have applied all ABAP Support Packages before you run the configuration wizard

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 70 JSPM uses the SoftwareDeployment Manager (SDM) to apply support packages and patches and to deploy softwarecomponentsFor more information about JSPM and how to use this tool see httphelpsapcomnw70

SAP NetWeaver 70 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution LifeCycle Management by Key Capability Software Life Cycle Management Software Maintenance Java SupportPackage Manager

03282008 PUBLIC 123198


You can also use the Support Package Manager to apply the latest ABAP support packagesFor more information about the Support Package Manager and how to use this tool seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management SoftwareMaintenance Support Package Manager


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

For up-to-date release information on Support Package Stacks and about how to apply themsee the documentation SAP NetWeaver 70 ‒ Support Package Stack Guide ltcurrent versiongt on SAPService Marketplace at httpservicesapcomMaintenanceNW70

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

c) Apply the ABAP Support Packages to your SAP system with the help of the Support PackageManager (formerly called SAP Patch Manager transaction SPAM)

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

124198 PUBLIC 03282008

5 Post-Installation59 Performing Initial ABAP Configuration

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

59 Performing Initial ABAP Configuration

Caution


Here you can find information about how to perform initial ABAP system configuration

Procedure

1 Go to the followinghttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability2 Check the documentation on the following configuration stepsn Performing a consistency check

When logging on to the system for the first time you need to trigger a consistency checkmanually The function is then called automatically whenever you start the system or anapplication serverFor more information seeSolution Life Cycle Management by Key Capability System Management Tools for Monitoring the System

Utilities Consistency Check

n Configuring the transport management systemFor more information seeSolution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics

Change and Transport System

n Performing basic operationsFor more information see the relevant section in Solution Life Cycle Management by Key CapabilitySystem Management

Operation Section in SAP Documentation

Set up operation modes ‒transaction RZ04

Configuration Operation Modes

Set up logon groups ‒transaction SMLG

Configuration Logon Load Balancing SAP Logon

Set up administrators Background Processing Authorizations for Background Processing

03282008 PUBLIC 125198



Schedule background jobs Background Processing

Install a printer SAP Printing Guide

Configure the system log Tools for Monitoring the System System log Configuring the System Log

n Configuring system parametersFor more information about system profiles which is where work processes and profileparameters are defined and how to configure them seeSolution Life Cycle Management by Key Capability System Management Configuration Profiles

l Configuring work processesSAPinst installs SAP systems with a minimum number of work processes This is only aninitial configuration to get you started after the installation It is not detailed enough for aproduction system because the optimal number of each type of work process depends onthe system resources and on the number of users working in each SAP system applicationFor more information about how many work processes to configure and how to set thenumber see SAP Notes 39412 and 9942

l Configuring Kernel parametersFor more information about kernel parameter recommendations see SAP Notes 146289and 835474

n Installing languages and performing language transportl Installing languages using transaction I18N

u If you want to use English only you must activate the default language settings once

u If you want to use languages other than English you must install them and activate thelanguage settings

For more information about configuring the language settings see the onlinedocumentation in transaction I18N at I18N Menue I18N Customizing

l Performing language transport using transaction SMLTFor more information about performing the language transport using transaction SMLTseeSolution Life Cycle Management by Key Capability Software Life Cycle Management Software Logistics

Change and Transport System Language Transport

n Using and Configuring the SAP ITS Integrated in ICMSince SAP NetWeaver 2004 (rsquo04) the SAP Internet Transaction Server (SAP ITS) is integratedin the SAP NetWeaver Application Server ABAP (AS ABAP) as an Internet CommunicationFramework (ICF) service You can access this like other services with the InternetCommunication Manager (ICM) With the SAP ITS integrated in AS ABAP the Web browsernow communicates directly with the SAP system Furthermore all SAP ITS-related sourcessuch as service files HTML templates or MIME files are now stored in the database of thesystem

126198 PUBLIC 03282008

5 Post-Installation510 Performing Oracle-Specific Post-Installation Steps

The SAP ITS supports the following functionsl SAP GUI for HTML

l Internet Application Component (IAC) runtime or Web Transaction technologyFor more information about how to configure the integrated SAP ITS seeApplication Platform by Key Capability ABAP Technology UI Technology Web UI Technology SAP

Internet Transaction Server SAP ITS in the SAP Web Application Server ConfigurationFor more information about the ITS memory requirements see SAP Note 742048

n Maintaining address dataFor more information about maintaining the company address in your SAP system usingtransaction SU01 seeApplication Platform by Key Capability Business Services Business Address Services (BC-SRV-ADR)

Addresses in User Administration Maintenance of Address Data

Note

You must maintain your company address to create ABAP system users

n Configuring business applicationsFor more information about how to prepare the SAP system for using business applicationswhich includes customizing the ABAP system and the business components see Solution LifeCycle Management by Key Capability Customizing

510 Performing Oracle-Specific Post-Installation Steps

Caution


You have to perform the following Oracle-specific post-installation steps

Security Setup for the Oracle ListenerIf the Oracle security setup defined by the standard installation is not restrictive enough for yourpurposes see SAP Note 186119 to configure the Oracle listener to accept only connections fromspecific hosts

Checking the Recommended Oracle Database ParametersWhen installing the Oracle database a standard database parameter set is used To take into accountthe size and configuration of your SAP system and to enable new Oracle features check and apply theparameter settings as described in SAP Note 830576

Configuring and Operating the Oracle DatabaseYou have to configure your Oracle database before you start operating it with the SAP system

03282008 PUBLIC 127198

5 Post-Installation511 Performing the Client Copy

For information on Oracle database configuration and administration see the documentation inthe SAP Library at httphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaverLibrary SAP NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide ServicesDatabase Support Oracle

511 Performing the Client Copy

SAPinst creates three ABAP clients during the installation client 000 client 001 and client 066Client 000 is the SAP reference client for ABAPIf you chose to install an ABAP+Java system in one installation run AS Java was configured againstclient 001 during the installationYour production client must be a copy of the SAP reference client 000 For more information seeProduction Client Considerations [page 23]


Caution

For client copy considerations for usage type Process Integration (PI) see SAP Note 940309


Procedure

1 Maintain the new client with transaction SCC42 Activate kernel user SAP

a) Set the profile parameter loginno_automatic_user_sapstar to 0b) Restart the application server

3 Log on to the new client with kernel user SAP and password PASS4 Copy the client with transaction SCCL and profile SAP_CUST5 Check the log files with transaction SCC36 Create the required users These users must have at least the authorizations required for user

administration and system administration Create a user SAP with all required authorizationsfor this user If you want to have other users for system administration you can also create userSAP without authorizations

7 Deactivate kernel user SAPa) Reset loginno_automatic_user_sapstar to 1b) Restart the application server

For more information see

128198 PUBLIC 03282008

5 Post-Installation512 Performing a Full Installation Backup

httphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP NetWeaverby Key Capability Solution Life Cycle Management by Key Capability Software Lifecycle Management SoftwareLogistics Change and Transport System BC ‒ Client Copy and Transport

512 Performing a Full Installation Backup

You must perform a full offline backup at the end of the installation This procedure also describeshow to use the back-up data for a restore

Caution

Make sure that you fully back up your database so that you can recover it later if necessary

Prerequisites

n If required you have completed client maintenance such as the client copy [page 128]n You have logged on [page 117] as user ltsapsidgtadm and stopped the SAP system and database [page 165]

ProcedureThe Unix commands used in this procedure work on all hardware platforms For more informationabout operating system-specific backup tools see your operating system documentation

Backing Up the Installation

Note

The following only applies to a standard installation

1 Back up the following file systems

n usrsapltSAPSIDgt

n usrsaptrans

n ltsapmntgtltSAPSIDgt

n Home directory of the user ltsapsidgtadmn All database-specific directoriesProceed as followsa) Log on as user rootb) 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

2 Back up the operating system using operating system means

03282008 PUBLIC 129198

5 Post-Installation513 Post-Installation Steps for Adobe Document Services

This saves the structure of the system and all configuration files such as file system size logicalvolume manager configuration and database configuration data

Restoring Your Backup

If required you can restore the data that you previously backed up

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

Performing a Full Database Backup

1 Configure your third-party backup tool if used2 Perform a full database backup (preferably offline)

If you use BRTOOLS for the backup refer to BRTools for Oracle DBA in the SAP Database Guide Oracle(BC-DB-ORA-DBA) This documentation is available in the SAP Library athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide Services DatabaseSupport Oracle SAP Database Guide Oracle (BC-DB-ORA-DBA)

513 Post-Installation Steps for Adobe Document Services

If you want to use Adobe document services (ADS) in your SAP system landscape you have toperform the following post-installation steps

Note

Adobe document services (ADS) are only supported on a limited set of 64-bit platforms for SAPNetWeaver For more information see Running Adobe Document Services on Non-Supported Platforms [page 38]

n You assign the required roles to users ADSUSER and ADS_AGENT [page 131]n You check the IIOP service and the startup properties [page 131]n You perform quick tests for Adobe Document Services (ADS) [page 132]

130198 PUBLIC 03282008


5131 Assigning Roles to Users ADSUSER and ADS_AGENT

During the installation SAPinst created the users ADSUSER for basic authentication and ADS_AGENT

for processing forms between an ABAP and a Java environmentAfter the installation you have to assign the required authorization roles manually to these users inthe ABAP system as described below

Assigning Role SAP_BC_FP_ICF to ADS_AGENT

1 Log on to the ABAP system with user DDIC or SAP2 Call transaction SU013 Enter ADS_AGENT in the User field4 Choose User Names Change 5 Choose the Roles tab and assign the role SAP_BC_FP_ICF to the user ADS_AGENT

Creating Role ADSCallers and Assigning it to ADSUSER

1 Log on to the ABAP system [page 117]2 Call transaction PFCG3 Enter ADSCallers in the Role field4 Choose Role Create 5 On the Create Roles screen choose Role Save 6 Choose the User tab and assign the user ADSUSER in the User ID field

5132 Checking the IIOP Service and the Startup Properties

After the installation of the Adobe document services and before performing any other configurationsteps you need to check special settings on the central instance host If necessary you need to adaptthese settings manually

Procedure

1 Start the conguration tool of the AS Java by runningusrsapltSAPSIDgtltinstance_namegtj2eeconfigtoolshThe Config Tool screen appears

2 Check if the startup mode of the service iiop is set to alwaysa) In the left frame open the tree Cluster data Cluster data Global dispatcher configuration Services b) Choose service iiopc) The field Startup mode in the right frame must be set to always If it is not true apply the value

alwaysd) Choose Apply changes

03282008 PUBLIC 131198


e) Repeat the steps b to d for the following path Cluster data Cluster data Global serverconfiguration Services

3 Check if the Java startup property for Adobe document services is set as followsa) Select Cluster data Cluster data instance_ltIDxxxxgt server_ltIDxxxxgt b) In the right frame check if the following line exists in the Java Parameters area of the tab General

-DorgomgPortableInterceptorORBInitializerClasscomsapengineservicestsjtsotsPortableInterceptorJTSInitializerIf the line does not exist add the line to this section

Caution

Due to layout restrictions this documentation cannot display the whole parameter in oneline We had to insert a line break in front of PortableInterceptorJTSInitializerIn reality this parameter must not contain any blank and must be entered in one line

4 Exit the configuration tool5 If you have applied new values during the procedure above you need to restart the AS Java

to adapt the new settings

5133 Installation Check and Quick Tests for AdobeDocument Services

Adobe document services (ADS) can run in different IT scenarios infrastructures and usage typesin a new or in an upgraded installation In some cases the installation process cannot perform allconfiguration settings that are necessary for the use of Adobe document services for example if ABAPand Java are not installed on the same server Use this process to check whether all configuration stepsare complete and to verify which ones you still need to perform manually

PrerequisitesAdobe document services are installed on your system

ProcedureCheck the ADS configuration as described in httphelpsapcomnw70 SAP NetWeaver 70 LibraryEnglish SAP NetWeaver Library Technology Consultantrsquos Guide Business Task Management Adobe DocumentServices (Configuration) Adobe Document Services Configuration Guide Configuring the Web Service Securing Accessto the Web Service Configuration Check If the tests are not successful you might have to make some adjustments to the initial technicalconfiguration for ADS [page 171]

132198 PUBLIC 03282008

5 Post-Installation514 Setting Environment Variable CPIC_MAX_CONV

More InformationThe Adobe Document Services Configuration Guide is also available in PDF form athttpsdnsapcomirjsdnadobe Installation amp Configuration SAP Interactive Forms Installation and

Configuration Guides Adobe Document Services - Configuration Guide NW 70


514 Setting Environment Variable CPIC_MAX_CONV

To set the CPIC_MAX_CONV variable proceed as follows

1 Set the system variable CPIC_MAX_CONVenv variable CPIC_MAX_CONV ltmaximum number of simultaneous RFCs to the SAP Systemgt

Note

We recommend that you set the value to at least 200

2 Restart the system3 Increase the profile value gwmax_conn and gwmax_sys on the SAP gateway to support more

parallel connections If you run into memory bottlenecks also increase gwmax_overflow_sizeand gwmax_shm_req Refer to report RSMONGWY_CHANGE_PARAMETER started from transaction SA38

End of BI JavaProcess Integration (PI)


515 Post-Installation Steps for Usage Type ProcessIntegration (PI)

You need to perform the following post-installation steps for usage type PI after SAPinst has finished

5151 Performing PI-Specific Steps for SLD Configuration

Central SLD Checking the CR Data in the SLD (optional)Since CR_Contentzip contains all available SAP components the content of this file grows with timeThe extensions contain information about new components (new releases and Support Packages forexample) This content in the SLD has to be updated from time to timeFor more information about how to download the most up-to-date files see SAP Note 669669

03282008 PUBLIC 133198

5 Post-Installation516 Post-Installation Steps for the Application Sharing Server

More InformationFor more information about SLD users and security roles see the Post-Installation Guide - SLD of SAPNetWeaver 70 at httpsdnsapcomirjsdnnw-sldEnd of Process Integration (PI)


516 Post-Installation Steps for the Application SharingServer

After you have installed the necessary software you must complete a number of configuration stepsin the portal to fully implement application sharing functions in the portal These steps are validif you installed the Application Sharing Server as a standalone engine or you are using the defaultserver installed on the portal machineFor more information seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability People Integration by Key Capability Collaboration Administration Guide Real-TimeCollaboration Configuring Real-Time Collaboration Configuring the Application Sharing Server (RTC) This documentation includes information on how you define which Application Sharing Serverthe portal must useIf you do not intend to use Application Sharing Server you can disable it For more information seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability People Integration by Key Capability Collaboration Administration Guide Real-TimeCollaboration Configuring Real-Time Collaboration Configuring the Application Sharing Server (RTC) Enabling Disabling the Application Sharing Server (RTC) The installation of Application Sharing Server as an optional standalone unit is described in thedocumentation Installation Guide ‒ ltyour productgt Java on ltOSgt ltDatabasegtEnd of Enterprise Portal (EP)


517 High Availability Post-Installation Steps

5171 Setting Up Licenses

Caution


134198 PUBLIC 03282008

5 Post-Installation517 High Availability Post-Installation Steps

Every SAP system needs a central license which is determined by the environment of the messageserver Since SAPrsquos high-availability (HA) solution stipulates two or more cluster nodes (hostmachines) where the message server is enabled to run you have to order as many license keys [page 121]as you have cluster nodesWhen we receive confirmation from your vendor that you are implementing a switchoverenvironment we provide the required license keys for your system one key for each machineSAP 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 ABAP central services instance (ASCS) runsThere is no license problem when only the database is switched over


Procedure

1 Make sure that the ABAP central services instance (ASCS) on the primary host node A is running2 To find the hardware ID of the primary host log on to any application server instance of the

SAP system and call transaction SLICENSE3 Perform a switchover of the ABAP central services instance (ASCS) to another node in the cluster

and repeat the previous stepRepeat this for all remaining nodes in the cluster

4 To obtain the two license keys enter the hardware IDs for the primary and backup hosts athttpservicesapcomlicensekey

5 To import the files containing the two licenses log on to any application server instance of theSAP system and call transaction SLICENSE

6 Perform a switchover of the ABAP central services instance (ASCS) to another node in the clusterand 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 scripts

5172 Taking Precautions for Transport

Caution


With a high-availability (HA) installation you need to take precautions before you perform a transport

03282008 PUBLIC 135198

5 Post-Installation518 Ensuring User Security

TPPARAM contains parameter settings for the transport control program tp which is used for exportsand imports It also includes the parameter ltSIDgtdbhost which is used to address the database host

ProcedureSet ltSIDgtdbhost to the virtual host name of the DB instanceThis lets you use the transport system for the normal maintenance of ABAP programs but still allowstransparent operation in the event of a switchoverEnd of HA (UNIX)

518 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

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 seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability 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

136198 PUBLIC 03282008


Operating System and Database Users

User User Name Comment

ltsapsidgtadm SAP system administrator

ltsmdsidgtadm Administrator for the DiagnosticsAgent

Operating system user

oraltdbsidgt Oracle database administrator (thatis the owner of the database files)

SAPltSCHEMA_IDgt Oracle database owner (that is theowner of the database tables)

SYSTEM ‒

SYS ‒

OUTLN ‒

Oracle database user

DBSNMP ‒

ABAP+Java Users


SAP User exists at least in the clients 000 001and 066 auf the ABAP system

CautionThis user has extensive authorizationsMake sure that you assign a securepassword

DDIC User exists at least in the clients 000 001and 066 auf the ABAP system


EARLYWATCH User exists at least in the client 066 ofthe ABAP system

SAP system user

SAPCPIC User exists at least in the clients 000 and001 of the ABAP system

03282008 PUBLIC 137198



Administrator The name that you gave this userduring the installation or the defaultname J2EE_ADMIN

User exists at least in the clients 000 and001 of the ABAP system


Guest The name that you gave this userduring the installation or the defaultname J2EE_GUEST


Communication user forthe J2EE Engine

The name that you gave this userduring the installation or the defaultname SAPJSF


ADSUser User exists at least in the clients 000 and001 of the ABAP system

Users for AdobeDocument Services (ADS)

ADS_AGENT User exists at least in the clients 000 and001 of the ABAP system

Data supplier userfor System LandscapeDirectory (SLD)(optional)

The name that you gave this userduring the installationThe recommended name is SLDDSUSER


NoteSAPinst created this user automaticallyif you chose Configure local SLD duringthe installation

ABAP API user for SystemLandscape Directory (SLD)(optional)

The name that you gave this userduring the installationThe recommendedname is SLDAPIUSER



Java Add-In Users for Users Stored in the ABAP System

User User Name Storage ABAP System Comment




138198 PUBLIC 03282008




None



None




Data supplier userfor System LandscapeDirectory (SLD) (optional)









Users in the SAP NetWeaver Development Infrastructure (NWDI)


Administrator of the SAPNetWeaver DevelopmentInfrastructure (NWDI) andpassword

NWDI_ADM Administrator of the NWDI

CautionThis user has extensiveauthorizations Make surethat you assign a secure password

03282008 PUBLIC 139198



Developer in the SAP NetWeaverDevelopment Infrastructure(NWDI) and password

NWDI_DEV Developer in the NWDI

Landscape Directory ServiceUser in the SAP NetWeaverDevelopment Infrastructure(NWDI) and password

NWDI_CMSADM Administrator of the NWDIChange Management System(CMS)

CautionDo not log on with this user Itis used by the system for internalcommunication



Users in Process Integration (PI)


Integration Repository ServiceUser

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

User exists in SAP system client 001


Integration Directory Service User The name that you gave this userduring the installation or thedefault name PIDIRUSER



Landscape Directory Service User The name that you gave this userduring the installation or thedefault name PILDUSER



Integration Server ApplicationUser

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


140198 PUBLIC 03282008

5 Post-Installation519 Running the Configuration Wizard


Runtime Workbench Service User The name that you gave this userduring the installation or thedefault name PIRWBUSER



Adapter Framework Server ServiceUser

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



Integration Server Service User The name that you gave this userduring the installation or thedefault name PIISUSER



Management Server Service User The name that you gave this userduring the installation or thedefault name PILSADMIN



Exchange InfrastructureAdministrator

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



Exchange InfrastructureCommunicator

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




03282008 PUBLIC 141198



519 Running the Configuration Wizard

This section provides information about how to run the Configuration Wizard for the SAP NetWeaverusage typesYou can run the Configuration Wizard only once and only directly after you installed and patchedthe system


Note

You can run the configuration task for BI Java several times and after all use cases

End of BI Java

You cannot use the configuration wizard after

n Upgraden Add-In installation

n Enablement of additional usage types

In these cases you need to perform the corresponding configuration steps as described in theconfiguration documentation seeAccessing Configuration Documentation in the SAP Solution Manager [page 145]You can also find configuration documentation in the Technology Consultantrsquos Guide in the SAP Library athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library Technology

Consultantrsquos Guide For more information about the Configuration Wizard itself see the SAP Library athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library Technology

Consultantrsquos Guide Developing Configuring and Adapting Applications Creating Java Applications Using WebDynpro J2EE Engine Configuration Configuration Wizard

Note

For more information about the Configuration Wizard and its limitations see SAP Note 923359

PrerequisitesYou have applied the latest kernel and support packages [page 123] to your systemYou can find the latest LMTOOLS patch at httpservicesapcomswdc Support Packages andPatches Search for Support Packages and Patches Search for LMTOOLSP Download and save the sca fileApply the patch using the SDM

142198 PUBLIC 03282008


1 Open the URL httplthostgtlthttpportgtnwa in a browser and logon to the SAP NetWeaverAdministrator with the user Administrator

2 In the SAP NetWeaver Administrator navigate to the Deploy and Change tab The system displays theconfiguration wizard and its configuration tasks

3 Depending on your installed system select a task from the list as described below and choose Start4 After the Configuration Wizard has finished you need to restart your SAP system


Usage Type Application ServerTo configure the SAP NetWeaver Administrator you need to run the configuration tasks NWA_lt01‒07gt using the Configuration WizardEnd of Application Server (AS)


Usage Type Process Integration (PI)After SAPinst has finished and you have performed the necessary post-installation steps for usagetype PI you need to run the configuration task PI_00 using the Configuration Wizard

Caution

If you are using a central SLD apply SAP Note 939592



Usage Type BI JavaAfter SAPinst has finished you need to run the configuration task BIPostInstallProcess using theConfiguration WizardFor more information see SAP Note 917950

Recommendation

We recommend that you check the configuration of BI Java using SAP Note 937697

End of BI Java


Usage Type Development InfrastructureAfter SAPinst has finished you need to run the configuration task for usage type Initial setup of functionalunit Development Infrastructure (DI all-in-one) using the Configuration Wizard

03282008 PUBLIC 143198

5 Post-Installation520 Checking the SAP Java Documentation

After the Configuration Wizard has finished you have to restart the engine as described in SAPNote 919942End of Development Infrastructure (DI)


Usage Type Mobile InfrastructureAfter SAPinst has finished you need to run the configuration taskMI Post Installation Process usingthe Configuration WizardEnd of Mobile Infrastructure (MI)


520 Checking the SAP Java Documentation

Here you can find information about the configuration and administration of the J2EE Engine andabout SAP Java technology in the SAP Library

Procedure

1 Go to httphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver LibrarySAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology

2 Check the following documentation for information relevant to running your Java system

Manual Contents

Architecture Manual This manual describes the architecture of a Java or ABAP+Java system Itcontains information onn Java cluster architecture including central services load balancing

and high availabilityn J2EE Engine system architecturen SAP NetWeaver Java development infrastructure including SAP

NetWeaver Developer Studio

NoteThe SAP NetWeaver Developer Studio is the SAP developmentinfrastructure for Java The Architecture Manual describes theintegration of the SAP NetWeaver Developer Studio into the SAPdevelopment infrastructure

144198 PUBLIC 03282008

5 Post-Installation521 Accessing Configuration Documentation in SAP Solution Manager

Manual Contents

Administration Manual This manual describes how to administer the SAP system focusing on theJ2EE Engine It contains information onn System landscape administrationn Software life-cycle management

NoteThis part of the manual contains important information aboutl Installation informationl System Landscape Directory (SLD)l Software Lifecycle Manager (SLM)l Java Support Package Managerl Administration of SAP NetWeaver Java Development

Infrastructure (JDI)

n J2EE Engine and J2EE Engine securityn Supportability and performance managementn Administration and configuration of Web Dynpro runtime

environmentn Administration of the XML Data Archiving Service (XML DAS)

CautionMake sure that you check the mandatory post-installation procedureslisted in the Administration Manual under J2EE Engine InstallationInformation Post-Installation Procedures

Java Development Manual This manual describes the technologies for developing Java-based businessapplications It explains how to use the SAP NetWeaver Developer Studiowhich is the SAP Java development environment

Migration Manual This manual contains all the information you need to migrate anapplication created in J2EE Engine 620

More InformationFor more information about troubleshooting for the J2EE Engine see the J2EE Engine Problem AnalysisGuide athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability Solution Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide(PAG) Usage Type Application Server Java J2EE Engine Problem Analysis Scenarios

521 Accessing Configuration Documentation in SAP SolutionManager

To access configuration documentation in SAP Solution Manager you have to connect yournewly-installed SAP system to SAP Solution Manager

03282008 PUBLIC 145198


Note

For SAP NetWeaver 70 usage types you can also find configuration documentation in the TechnologyConsultantrsquos Guide athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library Technology

Consultantrsquos Guide

Prerequisites

n You have installed an SAP Solution Manager system as described in the documentation InstallationGuide ‒ SAP Solution Manager 40 ltcurrent support releasegt on ltOSgt ltDatabasegt

n You have connected your SAP system to SAP Solution Manager as described in the documentationConfiguration Guide ‒ SAP Solution Manager ltCurrent Releasegt as of ltCurrent SP Levelgt

You can find this documentation athttpservicesapcominstguides SAP Components SAP Solution Manager Release 40

Procedure

1 Log on to your SAP Solution Manager system2 To be able to access configuration documentation create a project as follows

a) Create your project with transaction SOLAR_PROJECT_ADMIN for project administrationb) Connect your SAP system to SAP Solution Manager with transaction SMSY for the SAP Solution

Manager system landscapec) Create a project structure and add the required scenarios for your SAP system to your project

structure with the Business Blueprint transaction SOLAR01d) Add your SAP system configuration structures to your project structure with the configuration

transaction SOLAR02For more information about creating projects assigning scenarios to projects and creatingconfiguration structures seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP Solution ManagerUsing the SAP Solution Manager in Projects

3 Go to the project structure folder ltproject namegt using transaction SOLAR024 Access configuration documentation for SAP NetWeaver usage types at Configuration Structure

SAP NetWeaver 70

ResultYou can now configure your SAP system according to the configuration documentation in SAPSolution Manager

146198 PUBLIC 03282008

5 Post-Installation522 Post-Installation Steps for the Diagnostics Agent

522 Post-Installation Steps for the Diagnostics Agent

To implement the E2E Root Cause Analysis scenario you have to perform the followingpost-installation steps

PrerequisitesYou have installed an AS Java central instance or dialog instance

Procedure

1 Upgrade the JDK on AIX and Linux x86_64 operating systems as described in SAP Note 1093831This avoids connection problems between the Diagnostics Agent and the Diagnostics Managingsystem as well as out-of-memory errors and class-loader problems

2 Plan the implementation of the SAP Solution Manager Diagnostics Agent as described in the RootCause Analysis Installation and Upgrade Guide which you can find at one of the following

n httpservicesapcomdiagnostics

n httpservicesapcominstguides SAP Components SAP Solution Manager ltCurrentReleasegt

03282008 PUBLIC 147198


6 Additional Information


The following sections provide additional information about optional preparation installationand post-installation tasksThere is also a section describing how to delete an SAP system

Preparation

n Installation of Multiple Components in One Database [page 149]n Integration of LDAP Directory Services [page 151]

Installation

n Installation of Additional Software Units or Usage Types in an Existing SAP System [page 155]

Post-Installation

n Starting and stopping the SAP system [page 161]n If you decided to use a generic LDAP directory you have to create a user for LDAP directory access

[page 169]n Configuring User Management to Use an LDAP Directory [page 170]n Usage Type-Specific Initial Technical Configuration [page 170]n Heterogeneous SAP System Installation [page 180]n Troubleshooting [page 181]

Deleting an SAP System

n Deleting an SAP System [page 182]

61 Installation of Multiple Components in One Database(Optional)

Caution


You can installmultiple SAP systems in a single database This is called Multiple Componentsin One Database (MCOD)

03282008 PUBLIC 149198

6 Additional Information61 Installation of Multiple Components in One Database (Optional)

Example

You install an SAP NetWeaver central system and an SAP CRM central system in a single database

MCOD is available with all SAP components We are releasing this technology on all the majordatabases for the SAP system in line with our commitment to deliver platform-independentsolutionsUsing this technology is as easy as installing a separate component No extra effort is required becausethe MCOD installation is fully integrated into the standard installation procedure MCOD is not anadditional installation service Instead it is an option of the database instance installationWith MCOD we distinguish two scenarios

n The installation of an SAP system in a new databasen The installation of an additional SAP system in an existing database

Prerequisites

n For more information about MCOD and its availability on different platforms seehttpservicesapcommcod

n We have released MCOD for Unicode installations A prerequisite is that the MCOD systemcontains Unicode instances only SAP does not support mixed solutions

n Improved sizing requiredIn general you calculate the CPU usage for an MCOD database by adding up the CPU usage foreach individual SAP system You can do the same for memory resources and disk spaceYou can size multiple components in one database by sizing each individual component using theSAP Quick Sizer and then adding the requirements together For more information about the SAPQuick Sizer see httpservicesapcomsizing

Features

n Reduced administration effort

n Consistent system landscape for backup system copy administration and recoveryn Increased security and reduced database failure for multiple SAP systems due to monitoring and

administration of only one databasen Independent upgrade

In an MCOD landscape you can upgrade a single component independently from the othercomponents running in the same database assuming that the upgraded component runs onthe same database version However if you need to restore a backup be aware that all othercomponents are also affected

Note

Special MCOD considerations and differences from the standard procedure are listed where relevantin the installation documentation

150198 PUBLIC 03282008

6 Additional Information62 Integration of LDAP Directory Services (Optional)

Constraints

Recommendation

We strongly recommend that you test MCOD in a test or development systemWe recommend that you run MCOD systems in the same context We do not recommend that youmix test development and production systems in the same MCOD

n In the event of database failure all SAP systems running on the single database are affectedn Automated support in an MCOD landscape for the following administrative tasks depends on

your operating system and databasel Copying a single component from an MCOD landscape to another database at database levell De-installing a single component from an MCOD landscape requires some additional steps

You can use a remote connection to SAP support to request help with these tasks For moreinformation see httpservicesapcomremoteconnection

n When you use stopsap in an MCOD system with two central instances only one central instanceis stopped Therefore you must first stop the other SAP system with stopsap R3 to make sure thatthe database is also stopped

n You cannot install a Unicode SAP system with a non-Unicode SAP system in one databasen For the second SAP system you must use the same DBSID as for the first SAP systemn If you install a system into an existing database (MCOD) the SYSTEM tablespace must contain

at least 400 MB of free space If there is not enough space left increase the size of this tablespacewith BRSPACE or BRTOOLS

n If you decide to turn off archive log mode during the database load phase of the installation youneed to plan downtime for all MCOD systems sharing the database

62 Integration of LDAP Directory Services (Optional)

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

03282008 PUBLIC 151198


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

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 athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Security Identity Management Identity Management of the Application ServerABAP 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 at

152198 PUBLIC 03282008


httphelpsapcom SAP NetWeaver 70 Library English SAP NetWeaver Library SAP NetWeaver byKey Capability Application Platform by Key Capability Java Technology Administration Manual J2EE EngineJ2EE Engine Administration Tools SAP Management Console

SAP Logon

Instead of using a fixed list of systems and message servers you can configure the 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=

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 system

03282008 PUBLIC 153198


configuration 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 from acentral location If the SAP system has been prepared correctly the SAP MC presents and analyzessystem information that it gathers from various sources including 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

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

154198 PUBLIC 03282008

6 Additional Information63 Installation of Additional Software Units or Usage Types in an Existing SAP System

Enabling the SAP System LDAP Registration

Once you have correctly configured your directory server you can enable the LDAP registration ofthe SAP system by setting some profile parameters in the default profileTo do this run SAPinst 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

63 Installation of Additional Software Units or Usage Typesin an Existing SAP System

To install additional Java software units or usage types in an existing SAP system based on SAPNetWeaver 70 SR3 (Support Package Stack (SPS) 14) you cannot use SAPinst Instead you haveto use the Java Support Package Manager (JSPM) ldquoExisting SAP systemrdquo means that this SAPsystem has at least AS Java

Restrictions

n You can use the option Install Additional Usage Type only if the corresponding product is installed onthe host where you start JSPM For more information see section Installation

n JSPM cannot be used to install AS Java as a Java Add-In for an existing ABAP-only system Insteadyou have to use SAPinst If you install the Java Add-In in an existing ABAP only system you canalso install further Java usage types or Java software units using SAPinstIf you want to install the Java Add-In proceed as described in Installing the Java Add-In for an ExistingABAP System [page 101]

n


It is not possible to install Process Integration (PI) as an additional usage type or software unit usingJSPM Instead you can only install an SAP system with PI as a new installationEnd of Process Integration (PI)

Prerequisites

n The existing SAP system must have at least software unit or usage type Application Server Java(AS Java)

n You have planned your SAP system landscape according to the Master Guide and the TechnicalInfrastructure Guide [page 13] available for your product

03282008 PUBLIC 155198


Preparation

1 Make sure that the following documentation is available

Note

You do not need to read the whole documentation However make sure that you read thoseparts of it referred to below in this procedure

n For handling JSPM use the documentation Java Support Package Manager athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-CycleManagement Software Maintenance Java Support Package Manager

n Check theMaster Guide [page 13] for your SAP system application for supportedrecommendedcombinations of UT that can be run in one system Check the appropriate installation guide foryour SAP system application for space requirements for the additional software units or usagetypes you want to install

2 Check which software units or usage types are already installed on your systemYou can do this in one of the following waysn Start JSPM and choose the Deployed Components tabn Check the usage type system information page of your system using the URL

httplthostgtlthttp_portgtutlUsageTypesInfo

For more information see the SAP Libraryhttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life CycleManagement Software Maintenance Java Support Package Manager Viewing the Deployed Components

3 Check the dependencies for the software units or usage types you want to install

Usage Types of SAP NetWeaver 70

Usage Type Name (TechnicalName) Long Text Depends on

BI SAP NetWeaver BusinessIntelligence Java

AS Java

DI SAP NetWeaver DevelopmentInfrastructure

AS Java

EPC SAP NetWeaver Enterprise PortalCore Component

AS Java

EP SAP NetWeaver Enterprise Portal AS Java EPC

MI SAP NetWeaver MobileInfrastructure

AS ABAP AS Java

156198 PUBLIC 03282008


4 Check hardware and software requirements for the software units or usage types you wantto install

Note

You cannot use the Prerequisite Checker [page 50] to check the requirements of additional softwareunits or usage types

a) Check space requirements for the additional software units or usage types that you wantto installTo do this check the table SAP Directories in SAP Directories [page 66]

b) Check Java virtual memory settings according to SAP Note 723909c) Check requirements for the Java Support Package Manager as described in

httphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAPNetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-CycleManagement Software Maintenance Java Support Package Manager Requirements for Free Disk Space

5 Download the required Software Component Archives (SCAs) and the appropriate stackdefinition file using the Maintenance Optimizer in SAP Solution ManagerFor more information seehttphelpsapcom SAP Solution Manager ltCurrent Releasegt SAP Solution Manager Change

Management Maintenance Optimizer Planning and Monitoring Product Maintenance

Recommendation

We recommend that you also download the most current Support Package Stack for AS Java toupdate the JSPM to the most current SPS level


n


Components of Business Intelligence Java (UT_NAME = BI)

Name of SCA Description

BIIBC_SCA BI INFORM BROADCASTING 700

BIWEBAPP_SCA BI WEB APPLICATIONS 700 (SP XX)

BIBASES_SCA BI BASE SERVICES 700 (SP XX)

BIREPPLAN_SCA BI REPORTING AND PLANNING 700

BIWDALV_SCA VCKITBI

VCKITBI_SCA BI WEBDYNPRO ALV 700

End of BI Java

03282008 PUBLIC 157198


n


Components of Development Infrastructure (UT_NAME = DI)


DICBS_SCA DI COMPONENT BUILD SERVER 700

DICMS_SCA DI CHANGE MGMT SERVER 700

DIDTR_SCA DI DESIGN TIME REPOSITORY 700


n


Components of Enterprise Portal Core Component(UT_NAME = EPC)


EPBC_SCA PORTAL CORE SERVICES 700

EPBC2_SCA PORTAL FRAMEWORK 700

EPPSERV_SCA PORTAL 700

EPWDC_SCA PORTAL WEB DYNPRO 700

SAPEU_SCA CAF EU 700

UWLJWF_SCA UWL AND COLL PROCESS ENGINE 700

End of EP Core (EPC)

n


Components of Enterprise Portal (UT_NAME = EP)


NETPDK_SCA PDK PORTAL SERVICES 700

LMPORTAL_SCA LIFECYCLE MGMT PORTAL 700

CAFKM_SCA SAP CAF-KM 700

KMCCOLL_SCA KMC COLLABORATION 700

KMCCM_SCA KMC CONTENTMANAGEMENT 700

RTC_SCA RTC 700

RTCSTREAM_SCA STREAMING SERVER 700

KMCBC_SCA KMC BASE COMPONENTS 700

VCBASE_SCA VCBASE

VCFLEX_SCA VCFLEX

VCKITGP_SCA VCKITGP

158198 PUBLIC 03282008



VCKITXX_SCA VCKITXX

WDEXTENSIONS_SCA WDEXTENSIONS

VCFRAMEWORK_SCA VCFRAMEWORK


n


Components of Mobile Infrastructure (UT_NAME = MI)


NWMADMIN_SCA MI ADMINISTRATION 700

NWMWDLAP_SCA MI LAPTOP 700

NWMDRIVERS_SCA MI DRIVERS 700

NWMCLIENT_SCA MI CLIENT 700

End of Mobile Infrastructure (MI)

6 Copy the downloaded SCAs and the appropriate stack definition file to the JSPM inbox directoryFor more information seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-CycleManagement Software Maintenance Java Support Package Manager Detecting and Changing the JSPM InboxDirectory

7


You must check in the SDM RemoteGui whether the following two substitution variables oftype String are created properly

n comsapportaldeploypcd =

ltcomsapengineinstalldirgtclusterserver0appssapcomirjservlet_jspirjrootWEB-INFdeploymentpcd

n comsapportaldeploypcdcontent =

ltcomsapengineinstalldirgtclusterserver0appssapcomirjservlet_jspirjrootWEB-INFdeploymentpcdContent

Note

ltcomsapengineinstalldirgt is the current value of SDMvariable comsapengineinstalldir

If these substitution variables do not exist or have wrong values you must create themmanuallyas a prerequisite for the deployment of usage types EPC and EPFor more information see Software Deployment Manager at

03282008 PUBLIC 159198


httphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAPNetWeaver Developerrsquos Guide Fundamentals Using Java Core Development Tasks Deployment Putting It AllTogether Software Deployment Manager Deployment Substitution Variables ManagementEnd of Enterprise Portal (EP)EP Core (EPC)

Installation

1 Start JSPM as described inhttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-CycleManagement Software Maintenance Java Support Package Manager Starting JSPM

2 We strongly recommend that you update JSPM to the most recent Support Package stack levelas described inhttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-CycleManagement Software Maintenance Java Support Package Manager Applying Single Support Packages

3 Depending on your SAP system landscape you have to run different JSPM optionsn Run the option Install Additional Usage Type if the corresponding product is installed in the same

system in which you start JSPM as described inhttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-CycleManagement Software Maintenance Java Support Package Manager Installing an Additional Usage Type

n Run the option Deploying New Software Components if the corresponding product is not installedin the same system in which you start JSPM as described inhttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-CycleManagement Software Maintenance Java Support Package Manager Deploying New Software Components

Example

You want to install BI Java as an additional usage type in an existing SAP NetWeaver systemlandscape with software units AS ABAP AS Java EPC and EPn If AS ABAP AS Java EPC and EP in the same system you can choose the option Install Additional

Usage Type to install BI Javan However if AS ABAP is in one system and AS Java EPC and EP are in another system you

have to choose the option New Software Components In addition you have to activate the newlyinstalled software unit BI Java manually using the scripts attached to SAP Note 883948

Post-InstallationAfter you have finished the deployment with JSPM you need to perform initial configuration tocomplete the installation of additional software units or usage types before you perform the actualconfiguration

160198 PUBLIC 03282008

6 Additional Information64 Starting and Stopping SAP System Instances

Caution

You must not run the Configuration Wizard for the added software unit(s) or usage type(s) Insteadyou have to configure them manually

1 For initial configuration perform the steps listed in Usage Type-Specific Initial Configuration [page 170]

Note

SAPinst performs these steps during the installation of an SAP system with usage types JSPMdoes not perform these steps

2 For complete configuration use the configuration documentation for your product from thehelp portal or from SAP Solution Manager For more information see Accessing ConfigurationDocumentation [page 145]

64 Starting and Stopping SAP System Instances

You can start and stop SAP system instances and the Diagnostics Agent by using the SAP ManagementConsole (SAP MC) [page 161]Apart from using the SAP Management Console (SAP MC) you can also use scripts to

n Start or stop SAP system instances [page 165]n Start or stop the Diagnostics Agent [page 168]

641 Starting and Stopping SAP System Instances Using theSAP Management Console

You can start and stop all SAP system instances (except the database instance) and the DiagnosticsAgent using the SAP Management Console (MC) You have to start and stop the database instanceas described in Starting and Stopping the SAP System Using startsap and stopsap [page 165]

Note

If your newly installed SAP system is part of a heterogeneous SAP system landscape comprisingsystems or instances on Windows platforms you can also start and stop it from a Windows system orinstance using theMicrosoft Management Console (MMC)For more information about handling the MMC seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution Monitoring Monitoringin the CCMS SAP Microsoft Management Console Windows

03282008 PUBLIC 161198


Prerequisites

n Make sure that the host where you want to start SAP MCmeets the following requirementsl Java Runtime Environment (JRE) 50 is installedl The browser supports Javal The browserrsquos Java plug-in is installed and activated

n 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 53 and 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 theSAP Management Console

Note

If the instances have not been added or if you want to change the configuration to display systemsand instances on other hosts you have to register your systemmanually as described in RegisteringSystems and Instances in the SAP Management Console below

Starting and Stopping SAP System Instances

Starting SAP Systems or Instances

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 choose Start from the context menu3 In the Start SAP System(s) dialog box choose the required options4 Choose OK

The SAP MC starts the specified system or system instances

162198 PUBLIC 03282008


Note

The systemmight prompt you for the credentials of the SAP system administrator To completethe operation you must have administration permissions Log in as user ltsapsidgtadm

Starting the Instances of a Distributed SAP System Separately

If you need to start the instances of an SAP system separately ‒ for example when you want to starta distributed or a high-availability system ‒ proceed as follows

1 Start the database instance2 Start the central services instance SCSltInstance_Numbergt


If your system is a high-availability system first start the ABAP central services instanceASCSltInstance_Numbergt and then start the Java central services instance SCSltInstance_NumbergtEnd of HA (UNIX)

3 Start the central instance DVEBMGSltInstance_Numbergt4 Start dialog instance(s) DltInstance_Numbergt if there are any

Stopping SAP Systems or Instances

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

The system might prompt you for the SAP system administrator credentials To complete theoperation you must have administration permissions Log in as user ltsapsidgtadm

Similarly you can start stop or restart all SAP systems and individual instances registered in theSAP MC

Stopping the Instances of a Distributed SAP System Separately

If you need to stop the instances of an SAP system separately ‒ for example when you want to starta distributed or a high-availability system ‒ proceed as follows

1 Stop dialog instance(s) DltInstance_Numbergt if there are any2 Stop the central instance DVEBMGSltInstance_Numbergt3 Stop the central services instance SCSltInstance_Numbergt

03282008 PUBLIC 163198



If your system is a high-availability system first stop the Java central services instanceSCSltInstance_Numbergt and then stop the ABAP central services instance ASCSltInstance_NumbergtEnd of HA (UNIX)

4 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 or Instances

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

Registering the Instances of a Distributed SAP System Separately

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 pane choose the instance you want the SAP MC to display on startup

164198 PUBLIC 03282008


3 Choose the ltlt button4 Choose Apply and then 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 the SAP Management Console seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP NetWeaver

by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EEEngine J2EE Engine Administration Tools SAP Management Console

642 Starting and Stopping SAP System Instances UsingScripts

You can start and stop SAP system instances by running the startsap and stopsap scriptsYou can also use the SAP Management Console (SAP MC) [page 161] to start or stop the instances ofthe SAP system

Prerequisites

n You have checked the default profile ltsapmntgtltSAPSIDgtprofileDEFAULTPFL for parameterloginsystem client and set the value to the correct production system client For example theentry must be loginsystem_client = 001 if your production client is 001

n You have checked the settings for Java Virtual Machine parameters as described in SAP Note723909

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

03282008 PUBLIC 165198


Caution

If there aremultiple SAP instances on one host ‒ for example a central instance and a dialoginstance ‒ you must add an extra parameter to the scriptsstartsap ltinstanceIDgt

stopsap ltinstanceIDgt

For example enterstartsap DVEBMGS00

Note

The instance name (instance ID) of the central instance is DVEBMGSltInstance_Numbergt theinstance name of the central services instance is SCSltInstance_Numbergt and the instance nameof a dialog instance is DltInstance_Numbergt


The instance name of the ABAP central services instance is ASCSltInstance_NumbergtEnd of HA (UNIX)

Procedure

Starting SAP System Instances

n To start all instances on the central system host enter the following commandstartsap

This checks if the database is already running If not it starts the database first

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 central instancegt

startsap R3 ltinstance ID of dialog 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 database host enter

startdb

166198 PUBLIC 03282008


2 On the central services and on the central instance host enterstartsap

3 For dialog instances enter the following on the relevant hoststartsap R3 ltinstance ID of dialog instancegt

Note

Make sure that the SAP system and associated J2EE Engines are up and running before you start orrestart dialog instances and their J2EE Engines

Stopping SAP System Instances

Note

When you use stopsap in a system with Multiple Components in One Database (MCOD) that hastwo central instances only one central instance and the database shut down Therefore you mustfirst stop the other SAP system with stopsap R3 or make sure that it has already been stoppedFor more information see Installation of Multiple Components in one Database [page 149]

n If you have a central system enter the following to stop all instances on the central system hoststopsap

This stops the central 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 dialog instancegt

stopsap R3 ltinstance ID of central instancegt

stopsap R3 ltinstance ID of central services instancegt

stopsap DB

Make sure that you always stop the central instance first and the central services instance secondbecause 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 J2EE

n In a distributed system proceed as follows1 On the dialog instance host enter the following command

stopsap ltinstance ID of dialog instancegt

2 To stop the central services instance on the central services and on the central instance hostenter the following command

03282008 PUBLIC 167198


stopsap

3 To stop the database enter the following command on the database hoststopdb

Caution

Make sure that no SAP instance is running before you enter stopdb on a standalone database serverNo automatic check is made

643 Starting and Stopping the Diagnostics Agent UsingScripts

You can start and stop the Diagnostics Agent by running the smdstart and smdstop scriptsThe local versions of these scripts are located in usrsapltSMDSIDgtJltinstance_numbergtscriptThe global versions of these scripts are located in usrsapltSMDSIDgtexe

Note

You can only start or stop the Diagnostics Agent separately It is not started or stopped automaticallywith the SAP system

You can also use the SAP Management Console (SAP MC) [page 161] to start or stop the Diagnostics Agent

PrerequisitesYou have logged on to the central instance or dialog host as user ltsmdsidgtadm

Procedure

Starting a Diagnostics Agent Locally

1 Change to the following directoryusrsapltSMDSIDgtJltInstance_Numbergtscript

2 To start the Diagnostics Agent locally enter this commandsmdstartsh

Starting Diagnostics Agent(s) Globally

To start Diagnostics Agent(s) globally enter this commandsmdstart ltSMDSIDgt ltInstance_Numbergt

Example

smdstart SMD 98

168198 PUBLIC 03282008

6 Additional Information65 Creating a User for LDAP Directory Access (Optional)

Note

You do not have to specify the ltSMDSIDgt if there is only one Diagnostics Agent system on this host

Stopping a Diagnostics Agent Locally

1 Change to the following directoryusrsapltSMDSIDgtJltinstance_numbergtscript

2 To stop the Diagnostics Agent locally enter this commandsmdstopsh

Stopping Diagnostics Agent(s) Globally

To stop Diagnostics Agent(s) globally enter this commandsmdstop ltSMDSIDgt ltInstance_Numbergt

Example

smdstop SMD 98

Note


65 Creating a User for LDAP Directory Access (Optional)

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 Preparing the Active Directory (Optional) 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

03282008 PUBLIC 169198

6 Additional Information66 Configuring User Management to Use an LDAP Directory (Optional)

66 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 SAP Note 718383 and SAP Library athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Security Identity Management Identity Management of the Application Server JavaConfiguring Identity Management UME Data Sources LDAP Directory as Data Source Configuring UME toUse an LDAP Directory as Data Source

67 Usage Type-Specific Initial Technical Configuration

SAPinst performs initial technical configuration steps for the usage types shown below during theinstallationHowever you might have to perform these steps manually if

n you have installed an additional usage type to an existing SAP system as described in SAP Note883948

Note

This currently applies to the following usage typesl Development Infrastructure (DI)

l EP Core (EPC)

l Enterprise Portal (EP)

l Business Intelligence (BI Java)

n you want to change existing parameters or if you want to set additional parameters

The following usage type-specific sections provide the required information

n Application Server Java (AS Java) [page 171]

n


Development Infrastructure (DI) [page 173]End of Development Infrastructure (DI)

n


EP Core (EPC) and Enterprise Portal (EP) [page 175]End of Enterprise Portal (EP)EP Core (EPC)

n


Business Intelligence (BI Java) [page 179]End of BI Java

170198 PUBLIC 03282008

6 Additional Information67 Usage Type-Specific Initial Technical Configuration

n


Process Integration (PI) [page 176]End of Process Integration (PI)

671 Initial Technical Configuration for the ApplicationServer Java (AS Java)

SAPinst performs initial technical configuration steps for the AS Java components listed below duringthe installationHowever you might have to perform some of these steps manually after SAPinst has finisheddepending on your installation scenarioFor more information see the following

n Adobe Document Services (ADS) [page 171]n Composite Application Framework (CAF) [page 172]n System Landscape Directory (SLD) [page 173]

6711 Initial Technical Configuration for Adobe DocumentServices

SAPinst automatically performs some initial technical configuration steps for Adobe DocumentServices (ADS) during the installationHowever you might have to perform these steps manually if you want to change existing parametersor if you want to set additional parametersSAPinst performs the following steps

n Creates user ADSUser in AS ABAP for basic authentication and assigns it to group ADSCallersFor more information about this user see Ensuring User Security [page 136]

n Creates user ADSUser in AS Java for basic authentication and assigns it to group ADSCallers

For more information about this user see Ensuring User Security [page 136]n Creates service user ADS_AGENT in the ABAP Environmentn Creates an ABAP connection for basic authentication

n Creates destination service FP_ICF_DATA_ltSAPSIDgtn Sets up basic authentication in the Java environment

For more information about how to perform these steps manually seehttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library Technology

Consultantrsquos Guide Business Task Management Adobe Document Services (Configuration) Adobe Document ServicesConfiguration Guide Configuring the Web Service Securing Access to the Web Service Configuration of the WebService for Basic Authentication

03282008 PUBLIC 171198


More InformationThe Adobe Document Services Configuration Guide is also available in PDF form athttpsdnsapcomirjsdnadobe Installation amp Configuration SAP Interactive Formsmdash Configuration

Guides

6712 Initial Technical Configuration for CompositeApplication Framework Core (CAF)

SAPinst automatically performs some initial technical configuration steps for Composite ApplicationFramework Core (CAF) during the installationHowever you might have to perform these steps manually if you want to change existing parametersor if you want to set additional parametersSAPinst performs the following steps

n Creates the following roles with the required User Management Engine (UME) actions

l CAFAdmin

l CAFUIAdmin

For more information about how to perform these steps manually see the SAP Library athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library Technology

Consultantrsquos Guide Developing Configuring and Adapting Applications Creating Composite ApplicationsComposite Application Framework Core Configuration Guide Setting Up Roles

n Configures CAF runtime properties for Business Warehouse (BW) integrationFor more information about how to perform these steps manually see the SAP Library athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library Technology

Consultantrsquos Guide Developing Configuring and Adapting Applications Creating Composite ApplicationsComposite Application Framework Core Configuration Guide Configuring CAF Core for BW Integration ConfiguringCAF Runtime Properties for BW Integration

n Configures CAF runtime properties for knowledge management integrationFor more information about how to perform these steps manually see the SAP Library athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library Technology

Consultantrsquos Guide Developing Configuring and Adapting Applications Creating Composite ApplicationsComposite Application Framework Core Configuration Guide Configuring CAF Core for Knowledge ManagementIntegration Configuring CAF Repository Managers Configuring CAF Runtime Properties

n SAPinst creates data sources to extract custom enumeration typesFor more information about how to perform these steps manually see the SAP Library athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver Developerrsquos Guide Fundamentals Creating Composite Applications Developing Composite Applicationswith CAF Core Integration CAF Core and SAP Business Information Warehouse Integration DataSource Use inCAF and SAP BW Integration DataSources to Extract Custom Enumeration Types

172198 PUBLIC 03282008


6713 Initial Technical Configuration for the SystemLandscape Directory (SLD)

SAPinst automatically performs some initial technical configuration steps for the System LandscapeDirectory (SLD) during the installation

n If you chose the option Register in existing central SLD SAPinst automatically configures theconnection of the system being installed to an existing central SLD

n If you chose the option Configure a local SLD SAPinst automatically sets up and configures a localSLD during the installation

However you might have to perform these steps manually if you want to change existing parametersor if you want to set additional parametersSAPinst performs the following steps

n Configures SLD security rolesn Configures server and persistence parametersn Performs the initial data importn Configures the SLD bridge

For more information about how to perform these steps manually see the documentation PostInstallation Guide ‒ System Landscape Directory of SAP NetWeaver 70 athttpservicesapcominstallNW70 Installation Configuration

More Information

n For more information about working with and configuring the SLD see the SAP Library athttphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life CycleManagement System Landscape Directory

n For more information about SLD see httpwwwsdnsapcomirjsdnnw-sldn For more information about security and the role concept in the SLD see

httphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver LibraryAdministratorrsquos Guide SAP NetWeaver Security Guide Security Aspects for System Management Security Guidefor the SAP System Landscape Directory


672 Initial Technical Configuration for DevelopmentInfrastructure (DI)

SAPinst automatically performs some initial technical configuration steps for usage type DevelopmentInfrastructure (DI) during the installation

03282008 PUBLIC 173198


However you might have to perform these steps manually if

n You have installed usage type DI as an additional usage type to an existing SAP system as describedin SAP Note 883948

n You want to change existing parameters or if you want to set additional parameters

SAPinst performs the following steps

n SAPinst creates the following NWDI users

l NWDI_ADM

l NWDI_DEV

l NWDI_CMSADM

For more information about these NWDI users see the table NWDI Users in Ensuring User Security[page 136]

n SAPinst creates the following roles

l NWDIAdministrator

l NWDIDeveloper

n SAPinst adds the following actions to the role NWDIAdministrator

l CBSAdministrator

l sapcom_comsaplcrLcrInstanceWriterAll

n SAPinst adds the following actions to the role NWDIDEVELOPER

l CBSDeveloper

l CMSDisplay

l CMSExportOwn

l sapcom_comsaplcrLcrInstanceWriterNR

n SAPinst creates the following groups

l NWDIAdministrators

l NWDIDevelopers

n SAPinst assigns the security role LcrInstanceWriterAll of the componentsapcomcomsaplcrsld to the group NWDIAdministrators

n SAPinst assigns the security role LcrInstanceWriterNR of the componentsapcomcomsaplcrsld to the group NWDIDevelopers

n SAPinst assigns the role NWDIAdministrator to the group NWDIAdministratorsn SAPinst assigns the role NWDIDeveloper to the group NWDIDevelopersn SAPinst assigns the group NWDIAdministrators to the user NWDI_ADMn SAPinst assigns the group NWDIDevelopers to the user NWDI_DEVn SAPinst assigns the group NWDIAdministrators to the user NWDI_CMSADM


Consultantrsquos Guide Developing Configuring and Adapting Applications Post Installation Steps of Usage Type DISetting Up Privileges Roles and GroupsFor more information about how to create and assign users groups and roles see the SAP Library at

174198 PUBLIC 03282008


httphelpsapcomnw70 SAP NetWeaver 70 Library English SAP NetWeaver Library SAPNetWeaver by Key Capability Security Identity Management Identity Management of the Application Server JavaAdministration of Users and Roles Managing Users Groups and RolesEnd of Development Infrastructure (DI)


673 Initial Technical Configuration for the Portal (UsageTypes EPC and EP)

This section applies when you install usage type EPC only and when you install it together withusage type EPSAPinst automatically performs some initial technical configuration steps for the usage types EPC andEP during the installationHowever you might have to perform these steps manually if

n You have installed usage type EPC or EPC and EP as an additional usage type to an existing SAPsystem as described in SAP Note 883948



n SAPinst copies the CMS_MAPPING Properties filen SAPinst renames the InitialPermissionsxmltemplate file to initialPermissionsxmln SAPinst renames the initialPermissionsKMCxmltemplate file to initialPermissionsKMCxml

Copying CMS_MAPPING Properties

1 Change to the following source directoryusrsapltsapsidgtltinstance_namegtj2eeclusterserverltxgtappssapcomirj

servlet_jspirjrootWEB-INFportalsystempcdMigrationmapping

2 Copy filecms_mappingproperties from the source directory to the following target directoryusrsapltsapsidgtSYSglobalpcdMigrationmapping

Note

If the target directory does not exist you have to create it as well

Renaming InitialPermissionsxmltemplate

1 Go to directoryusrsapltsapsidgtltinstance_namegtj2eeclusterserverltxgtappssapcomirj

servlet_jspirjrootWEB-INFportalsystemxmlacl2 Rename file initialPermissionsxmltemplate to initialPermissionsxml

03282008 PUBLIC 175198


Renaming initialPermissionsKMCxmltemplate


servlet_jspirjrootWEB-INFportalsystemxmlacl

2 Rename file initialPermissionsKMCxmltemplate to initialPermissionsKMCxml



674 Initial Technical Configuration for Process Integration(PI)

SAPinst automatically performs PI-specific initial technical configuration steps during the installationHowever you might have to perform some of these steps manually if

n You upgraded your SAP system to the current releasen You have installed usage type PI as an additional usage type to an existing SAP system as described

in SAP Note 883948

The following steps might be affected

n Import the SAP Exchange profile [page 176]n Assign SAP_ALL Rights to User PISUPER [page 177]n Activate the ICF Services [page 178]n Assign roles to groups [page 178]n Run the configuration template installer for usage type PI [page 142]

6741 Importing the SAP Exchange Profile

Note

If SAPinst has finished successfully the exchange_profilexml file does not exist on your systemIn this case you can skip this step

Procedure

1 On your PI server host open the following URLhttpltJ2EE_hostgtltJ2EE_PortgtexchangeProfile

The following naming convention applies for ltJ2EE_Portgt5ltJ2EE_instance_numbergt00

50000 for example if your J2EE instance is 002 Enter the logon information

176198 PUBLIC 03282008


User Name PISUPERPassword ltpisuper_passwordgtThe Exchange Profile page appears

3 Choose ConnectionThe Server Settings page appears

4 Enter the required information for the PI hostUse the logon information of user PILDUSER

5 Choose SaveThe Exchange Profile page appears

6 Choose ImportThe Import Profile page appears

7 Choose Browse and select the following fileusrsapltSAPSIDgtSYSglobalexchange_profilexml

Caution

If you cannot run aWeb Browser on your PI host you need to copy the file exchange_profilexmlfrom the PI host to a host where a Web browser runs

8 Choose Import DataThe profile is imported

Caution

Since the file exchange_profilexml contains secure information like passwords we highlyrecommend that you delete the file after importing or to save it by using high security standardssuch as encryption

6742 Assigning SAP_ALL Rights to User PISUPER

1 Log on to your SAP NetWeaver AS ABAP host as user with SAP_ALL rights (use DDIC or SAP)2 Call transaction SU013 Select user PISUPER4 Navigate to the Profiles tab and switch to edit mode5 In the row Profile add SAP_ALL6 Save your settings

03282008 PUBLIC 177198


6743 Activating the ICF Services

The Internet Communication Framework (ICF) is an HTTP framework that provides an ABAPinterface for HTTP requests Via ICF services the SAP Web Application Server can use the HTTPprotocol for remote communication as client and as server

ProcedureTo activate the ICF services call transaction SE38 and execute the reportRSXMB_ACTIVATE_ICF_SERVICES For more information see SAP Note 736312

6744 Assigning Roles to Groups

To assign the roles to the different groups start the Visual Administrator of the J2EE Engine

Assigning Role ldquoAdministerrdquo to Group SAP_XI_ADMINISTRATORCheck whether group SAP_XI_ADMINISTRATOR is assigned to role administerIf this is not the case proceed as follows

1 Choose Cluster Server Services Security Provider sapcomcomsaprprofremoteprofileexchangeprofile 2 Select Security Roles3 Select Administer4 Select the group SAP_XI_ADMINISTRATOR5 Choose Add and assign the role administer6 Save your settings

Assigning Security Role ldquoLcrAdministratorrdquo to GroupSAP_SLD_ADMINISTRATOR

1 Choose Cluster Server Services Security Provider 2 On the Runtime tab in the right frame choose Policy Configuration Component 3 Select sapcomcomsaplcrsld4 On the right choose Security Roles and select the role LcrAdministrator5 Select the role type Security Role6 In the lower frame add group SAP_SLD_ADMINISTRATOR


178198 PUBLIC 03282008



675 Initial Technical Configuration for BI Java

SAPinst automatically performs BI Java-specific initial technical configuration steps during theinstallationHowever you might have to perform some of these steps manually if

n You upgraded your SAP system to the current releasen You have installed usage type BI Java as an additional usage type to an existing SAP system as

described in SAP Note 883948


n Configure BI Java Information Broadcasting [page 179]n Process Chains Transport texts for alert category [page 180]n Rename initialPermissionsBIxmltemplate [page 180]n Run the configuration template installer for usage type BI Java [page 142]

6751 Configuring BI Java Information Broadcasting

For the configuration of the BI Information Broadcasting you need to perform the following stepsin your ABAP system

1 Call transaction SPRO and perform the following stepsa) Settings for Information Broadcasting

Go to SAP NetWeaver Business Intelligence Reporting-relevant Settings Settings for InformationBroadcasting

b) Destinations for Web Dynpro ALVGo to SAP NetWeaver Application Server Web Dynpro for ABAP Set-Up Printing for Web DynproABAP ALV

n Create RFC destination in the SAP NetWeaver Portal

n Create RFC destination to the SAP NetWeaver Portal

n Set-Up Web Service destination for the Adobe Document Services2 Installation of BI Content

Call transaction RSTCO_ADMIN to check whether the installation has been carried out successfullyIf the installation status is red restart the installation by calling transaction RSTCO_ADMIN againCheck the installation log if you need further assistance or informationFor more information see SAP Note 834280

03282008 PUBLIC 179198

6 Additional Information68 Heterogeneous SAP System Installation

Note

For the installation of SAP NetWeaver 70 BI Content Add-On 2 or higher on the AS ABAP systemsee SAP Note 847019

6752 Process Chains Transporting Texts for the AlertCategory

Alerts can be triggered and sent for BI process chains that contain errors Defining the alert categoriesis necessary for this purpose Alert category BWAC_PROCESS_CHAIN_FRAMEWORK is returned for errorsin background processing of process chains This category has set texts that are not transportedwhen the alert category is transported

ProcedureTo manually transport the texts see SAP Note 601619

6753 Renaming initialPermissionsBIxmltemplate

If SAPinst does not rename the initialPermissionsBIxmltemplate file automatically you needto rename it yourself

Procedure

1 Go to directoryusrsapltsapsidgtJCxxj2eeclusterserverltxgtappssapcomirj


2 Rename file initialPermissionsBIxmltemplate to initialPermissionsBIxml

End of BI Java

68 Heterogeneous SAP System Installation

This section provides information on the installation of an SAP system in a heterogeneous systemlandscape ldquoHeterogeneous system landscaperdquo means that application servers run on differentoperating systems

ProcedureSee SAP Note 1067221 for information on

n supported combinations of operating systems and database systems

180198 PUBLIC 03282008

6 Additional Information69 Troubleshooting

n how to install an application server on Windows in a heterogeneous (UNIX) SAP systemenvironment

n heterogeneous SAP system landscapes with different UNIX operating systems

69 Troubleshooting

The following section(s) describe the steps that you need to performmanually if SAPinst fails

n Troubleshooting with SAPinst [page 181]

n


Troubleshooting for Portal Installation [page 182]End of Enterprise Portal (EP)EP Core (EPC)

691 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 either of the followingn Try to solve the problemn Abort the installation with Exit

For more information see Interrupted Installation with SAPinst [page 104]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 SAPinst GUI does not start check the file sdtstarterr in the current ltuser_homegt directory5 If SAPinst GUI aborts during the installation without an error message restart SAPinst GUI as

described in Starting SAPinst GUI Separately6 Ignore error messages such as the following in the SDM logs

Error ltSCA namegt Location of software component rsquoltSCA namegtrsquo ltSCA vendorgtrsquo

rsquoltSCA locationgtrsquo rsquoltSCA countergt rsquo unknown Error ltSCA namegt system component

version store not updated

For more information see SAP Note 828978

03282008 PUBLIC 181198

6 Additional Information610 Deleting an SAP System


692 Troubleshooting for Portal Installation

This section applies both when you install usage type EPC only and when you install it togetherwith usage type EPIf the iViews are not displayed correctly or if the portal does not launch the reason might be that theportal was not deployed completelyTo check the deployment of the portal proceed as follows

Procedure

1 Open a new console with the user ltsapsidgtadm2 Go to the directories deployment pcd and pcdContent in the following paths

n usrsapltSAPSIDgtDVEBMGSltinstance_numbergtj2eeclusterserver0

appssapcomirjservlet_jspirjrootWEB-INFdeployment


appssapcomirjservlet_jspirjrootWEB-INFdeploymentpcd


appssapcomirjservlet_jspirjrootWEB-INFdeploymentpcdContent



pcdContentno_overwrite

3 Look for files with the extension err4 Do one of the followingn If error and log files do not appear the portal installation has been completed successfully

and you can continuen Rename the err files

a) Remove the err extension so the extensions of the files become ept or parb) Restart the J2EE Engine using the commands stopsap and startsap to change the files

to bak


610 Deleting an SAP System

The following sections describe how to delete an SAP system

182198 PUBLIC 03282008


Note

This description assumes that the installation of your SAP system has been performed using SAPstandard tools according to the installation documentation

You can choose one of the following options

n You delete the SAP system using SAPinst [page 183] However you still have to delete the databasemanually

n You delete the SAP system manually [page 185]

6101 Deleting an SAP System Using SAPinst

You can use SAPinst to delete an SAP system

Caution

SAPinst only stops local instances automaticallyBefore you delete the database instance of a distributed systemmake sure that you stop all remaininginstances Youmust stop the instance with the message server only after having entered all SAPinstparameters for the deletion of the database instance

n If you want to delete a central system (all instances reside on the same host) you can do thisin one SAPinst run1 Run SAPinst to delete the SAP system2 Delete the Oracle database software [page 185] manually

n If you want to delete a distributed system you have to run SAPinst to delete the requiredinstances locally on each of the hosts belonging to the SAP system in the following sequence1 Dialog instance(s) if there are any2 Database instance

SAPinst deletes the database instance but you have to delete the Oracle database software [page 185]manually

3 Central instance4 Central services instance

Caution

You cannot delete an SAP system remotely

Caution

If you delete network-wide users groups or service entries in an environment with NetworkInformation System (NIS) other SAP installations might also be affected Before you delete usersgroups or service entries make sure that they are no longer required

03282008 PUBLIC 183198


Caution

When you delete an SAP system using SAPinst system directories mounted from an NFS serverare not deletedYou must either delete them manually [page 185] or run SAPinst on the NFS server

61011 Running SAPinst to Delete an SAP System

This procedure tells you how to run the Uninstall option of SAPinst

Prerequisites

n You are logged on as user rootn If the saposcol process on the host you are working on has been started from the SAP system you

want to delete stop it using the command saposcol -kIf there are other SAP systems on the host log on as user ltsidgtadm of the other SAP system andstart saposcol from there using the command saposcol -l

Procedure

1 Start SAPinst and on theWelcome screen chooseSoftware Life-Cycle Options Uninstall Uninstall System Standalone Engine Optional Standalone Unit

Note

With this SAPinst option you do not delete the database software

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

SAPinst first asks you which SAP instances you want to deleteMake sure that you delete the SAP instances in the correct order as described in Deleting an SAPSystem Using SAPinst [page 183]

Caution

SAPinst only stops local instances automatically Before you delete the database instance of adistributed system make sure that you stop all remaining instances You must stop the instancewith the message server only after having entered all SAPinst parameters for the deletion ofthe database instance

184198 PUBLIC 03282008


3 Delete the database software manually [page 185]4 If required you can delete the directory usrsaptrans and its content manually

SAPinst does not delete usrsaptrans because it might be shared

61012 Deleting the Oracle Database Software

You use the Uninstall functionality of the Oracle Universal Installer (OUI) to complete the deletionof the Oracle database software

Note

This section only applies if you have deleted your SAP system using the Uninstall service of SAPinstIf you delete your SAP system manually you delete the Oracle database instance as described inDeleting an Oracle Database Instance [page 191]

Procedure

1 Start the OUI with the user oraltdbsidgt by entering one of the following


runInstaller


runInstaller


2 Choose Installed Products or Uninstall Products3 Select the database schema you want to uninstall ltDBSIDgt_102_644 Mark the Oracle 10G database within the selected product5 Choose Remove6 Confirm your selection with Yes7 Choose EXIT

6102 Deleting an SAP System Manually

Deleting a Complete SAP System Manually

1 You delete the SAP instances [page 186] in the following sequencea) Dialog instances if there are any

03282008 PUBLIC 185198


b) Central instance

Note

The Java part of an SAP system is deleted automatically when you delete the central instanceof the ABAP system

c) Central services instance if there is one2 You delete the remaining installation files and directories on the host(s) where you deleted your SAP instance(s) [page 187]3 You delete the Oracle database instance [page 191]

Note

The Java database schema is automatically deleted together with the database instance

Deleting the Java Part of an SAP System

1 You delete the Java parts of all dialog instances [page 188] if there are any2 You delete the Java part of an SAP system [page 188]3 You delete the central services instance [page 186]4 You delete the Java database schema of your Oracle installation [page 190]

61021 Deleting an SAP Instance

You use this procedure if you want to delete a single SAP instance or all instances of an SAP system

Note

Make sure that you delete the instances in the following order

1 Dialog instance if there are any2 Central instance3 Central services instance if there is one

Procedure

1 Stop the SAP instance that you want to delete as followsa) Log on as user ltsapsidgtadmb) Execute this command

stopsap r3 ltInstanceNamegt

2 Stop the sapstart service with the following commandsapcontrol -nr ltInstanceNumbergt -prot NI_HTTP -function StopService

3 Stop the saposcol process with the following commandsaposcol -k

186198 PUBLIC 03282008


4 Remove the instance profiles as followsrm usrsapltSAPSIDgtSYSprofileltSAPSIDgt_ltInstanceNamegt_lthost_namegt

rm usrsapltSAPSIDgtSYSprofileSTART_ltInstanceNamegt_lthost_namegt

Example

For example enter the following commandsrm usrsapC11SYSprofileSTART_D00_h0001

rm usrsapC11SYSprofileC11_D00_h0001

5 Log on as user root and delete the local instance directoryrm -rf usrsapltSAPSIDgtltInstanceNamegt

6 Change to the directory usrsap Edit the file sapservices and delete the line that refers tothe instance to be deleted

61022 Deleting Installation Files Directories and Userson a Host

After you have deleted all SAP instances on a host you still have to delete the remaining installationfiles directories and users on this particular host You have to repeat this procedure for any hostwhere you previously deleted an SAP instance

Caution

Only delete files or directories that are used by other SAP instances by means of NFS mounts if youare deleting the entire SAP system (on all hosts)

PrerequisitesYou must have deleted your SAP instance(s) as described in Deleting an SAP Instance [page 186]

Procedure

1 If the following directories are mounted with NFS unmount themltsapmntgtltSAPSIDgtexe



2 To delete directories execute the following commandsrm -rf usrsapltSAPSIDgt

rm -rf ltsapmntgtltSAPSIDgt

3 Delete the local user ltsapsidgtadm its home directory and all subdirectories of the home directory

03282008 PUBLIC 187198


Caution

Do not delete user ltsapsidgtadm if this is a Network Information System (NIS) user and you donot want to delete the SAP system on all hosts

Recommendation

To delete users use the administration tools of your operating system if possible

a) Delete user ltsapsidgtadm as described in your operating system documentationb) If the home directory of the user was not deleted automatically in the previous step execute

the following command to delete the directoryrm -rf ltsapsid_adm_homegt

Example

rm -rf homec11adm

4 Delete the user ltsapsidgtadm from the groups sapsys oper and dba if this was not doneautomatically in the previous step If one of these groups is now empty delete the complete groupas described in your operating system documentation

5 Check whether you need to delete entries from the file etcservicesa) Search for entries starting with sap

b) Check whether these entries are still required by other instances with the same or a differentltSAPSIDgt on any server

c) If not start by generating a backup copy of the services file by entering the following commandcp etcservices etcservicessap

d) Delete superfluous entries from etcservicesIf you use NIS for the services file see your operating system documentation for moreinformation on how to delete entries from network-wide service entries

6 If there are no other SAP instances running on this host delete the file usrsapsapservices

61023 Deleting the Java Part of an SAP System

This section describes how to delete the Java part of an SAP system

Note

If you delete a Java part the ABAP part of the SAP system is not deleted

Caution

This description assumes that you installed the SAP system using SAP standard tools accordingto the installation documentation

188198 PUBLIC 03282008


Process

Caution

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 the usersgroups and service entries to be deleted are no longer required

1 Stop the central services instance and all dialog instances of your SAP systema) Log on to the corresponding instance host as user ltsapsidgtadmb) Execute the following commandsn To stop the central services instance

stopsap r3 ltSCSinstanceNamegt

n To stop a dialog instancestopsap r3 ltDialogInstanceNamegt

2 Stop the J2EE Engine of the central instancea) Log on to your SAP systemb) Call transaction SMICMc) Choose Administration J2EE Instance (local) Send Hard Shutdown

Note

You do not need to stop the central instance

3 If lines beginning with the following parameters appear delete these lines from the default profileusrsapltSAPSIDgtSYSprofileDEFAULTPFLj2eedbname =

j2eedbtype =

j2eedbhost =

j2eedbadminurl =

j2eescshost =

j2eescssystem =

j2eemsport =

4 If lines beginning with the following parameters appear delete these linesfrom the central instance prole and from all dialog instance prolesusrsapltSAPSIDgtSYSprofileltSAPSIDgt_ltINSTANCE_NAMEgt_lthost_namegtexej2ee =

exejlaunch =

rdispj2ee_start_control =

rdispj2ee_start =

rdispj2ee_timeout =

rdispj2ee_libpath =

rdispfrfc_fallback =

03282008 PUBLIC 189198


jstartuptrimming_properties =

jstartupinstance_properties =

jstartupprotocol =

jstartupvmhome =

jstartupmax_caches =

jstartuprelease =

j2eedbdriver =

5 Delete the central services instance [page 186]6 Delete the Oracle Java database schema [page 190]7 Delete the following directories (ltxxgt is the central instance number)

n usrsapltSAPSIDgtDVEBMGSltxxgtSDM

n usrsapltSAPSIDgtDVEBMGSltxxgtj2ee

61024 Deleting the Oracle Database Java Schema

For the ABAP+Java installation this section describes how to delete the Java database schema for anOracle database installed in the existing database of the ABAP system

Caution

If you have multiple components installed in one database (MCOD) delete the database only ifyou also want to delete all components Otherwise delete components selectively For moreinformation see SAP Note 399910

Prerequisites

n Before deleting the Java database schema stop all SAP instances belonging to this Java databaseschema

n We recommend you to delete the SAP instances before deleting the Java database schema

Procedure

Caution

Before deleting the Java database schema make sure that you have a recent offline database backup

1 Log on as user oraltdbsidgt2 Start sqlplus and connect to the database Enter

sqlplus nolog

SQLPLUSgtconnect as sysdba

3 Enter the following command to delete the database objects of the database schemaSQLPLUSgt drop user SAPltSCHEMA_IDgtDB cascade

190198 PUBLIC 03282008


4 Enter the following command to get the file name of the corresponding data file in the file systemSQLPLUSgt select file_name from dba_data_files where

tablespace_name = rsquoPSAPltSCHEMA_IDgtDBrsquo

5 Enter the following command to delete the tablespace of the database schemaSQLPLUSgt drop tablespace PSAPltSCHEMA_IDgtDB including contents

6 Exit sqlplusSQLPLUSgt exit

7 Delete the data file of tablespace PSAPltSCHEMA_IDgtDB from the file system

61025 Deleting an Oracle Database Instance

This section describes how to delete an Oracle database that you have installed

Caution


Prerequisites

n Before deleting the database stop all SAP instances belonging to this database or to this Javadatabase schema

n We recommend that you delete the SAP instances before deleting the database instance

Procedure

1 Log on as user oraltdbsidgt2 Start sqlplus and shutdown the database Enter

sqlplus nolog

SQLPLUSgt connect as sysdba

SQLPLUSgt shutdown immediate

SQLPLUSgt exit

3 Kill the orasrv process if it is runningps -ef | grep orasrv (note the process ID ltPIDgt)kill mdash9 ltPIDgt

4 Stop the listener processlsnrctl stop

5 Use the uninstall functionality of the Oracle Universal Installer (OUI)

03282008 PUBLIC 191198


a) Start the OUI with the user oraltdbsidgt by entering one of the following


runInstaller


runInstaller

You see a message that a response file is being generated It might take several minutes beforeyou see the OUI screen

b) Choose Installed Products or Deinstall Productsc) Select the database schema you want to uninstall ltDBSIDgt_102_64d) Mark the Oracle 10G database within the selected producte) Choose Removef) Confirm your selection with Yesg) Choose EXIT

6 Log on as user root7 Delete user oraltdbsidgt along with its home directory and all subdirectories of this directory

a) Delete UNIX user oraltdbsidgt using the steps appropriate for your operating systemb) If the home directory of the user was not deleted automatically in the previous step delete

this directoryrm -rf ltsapsid_adm_homegt

Example

For example enterrm -rf homeorac11

8 Delete user oraltdbsidgt from group dba if this was not done automatically in the previous stepIf the group dba is now empty delete the complete group using the steps appropriate for youroperating system

9 Remove the directory oracleltDBSIDgt and subdirectoriesrm -rf oracleltDBSIDgt

10 If there are no other database instances with the same Oracle release installed on this host removethe staging area directory using the following commandrm -rf oraclestage102_64

11 If there are no other Oracle instances on this host remove the Oracle client software directorywith one of the following commandsrm -rf oracleclient102_64

192198 PUBLIC 03282008

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

03282008 PUBLIC 193198

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2008 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

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 vendorsMicrosoft Windows Excel 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 NetscapeSAP R3 xApps xApp SAP NetWeaver Duet PartnerEdge ByDesign SAP Business ByDesign and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world All other product and service names mentioned are thetrademarks of their respective companies Data contained in this document serves informational purposes only Nationalproduct specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies(SAP Group) for informational purposes only without representation or warranty of any kind and SAP Group shall 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

194198 PUBLIC 03282008

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly 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

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 that

03282008 PUBLIC 195198

copyright 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 SPARCmakes 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 Services

196198 PUBLIC 03282008

Adobe 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

03282008 PUBLIC 197198

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2008 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 on SAP Service Marketplace httpservicesapcominstguides

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

Version Date Description

100 3282008 Initial Version

2198 PUBLIC 03282008

Table of Contents




03282008 PUBLIC 3198




4198 PUBLIC 03282008






03282008 PUBLIC 5198


6198 PUBLIC 03282008

1 Introduction

1 Introduction


n



Note




n



n



n





03282008 PUBLIC 7198

1 Introduction

n



n



n







Caution



Constraints




8198 PUBLIC 03282008




11 New Features


Caution



Area Description







instance

03282008 PUBLIC 9198


Area Description



















10198 PUBLIC 03282008


Area Description











Area Description




Oracle Database




03282008 PUBLIC 11198


Documentation

Area Description
























12198 PUBLIC 03282008















Documentation














03282008 PUBLIC 13198












































General Quick Links




httphelpsapcomnw70

14198 PUBLIC 03282008


































03282008 PUBLIC 15198




Terminology


Variables













Example


16198 PUBLIC 03282008

2 Planning

2 Planning





8





Caution




03282008 PUBLIC 17198


Note



Note



Caution




Note


18198 PUBLIC 03282008






03282008 PUBLIC 19198




End of HA (UNIX)







20198 PUBLIC 03282008



Note





3







03282008 PUBLIC 21198



Caution






Figure 5


22198 PUBLIC 03282008


Caution













03282008 PUBLIC 23198











Note


24198 PUBLIC 03282008











USR VAR







SYS TMP UID USR VAR


03282008 PUBLIC 25198

















26198 PUBLIC 03282008




Master Password




03282008 PUBLIC 27198





















28198 PUBLIC 03282008










03282008 PUBLIC 29198















30198 PUBLIC 03282008






















03282008 PUBLIC 31198





















32198 PUBLIC 03282008


















03282008 PUBLIC 33198
















homeltusernamegt

34198 PUBLIC 03282008













03282008 PUBLIC 35198












36198 PUBLIC 03282008











03282008 PUBLIC 37198











38198 PUBLIC 03282008



Recommendation






Recommendation







03282008 PUBLIC 39198


Figure 6

Note



40198 PUBLIC 03282008


Figure 7


03282008 PUBLIC 41198


3 Preparation

3 Preparation


1




Caution







Caution



Caution


03282008 PUBLIC 43198









Procedure



Caution


Recommendation


44198 PUBLIC 03282008




Example


Figure 8


Caution



03282008 PUBLIC 45198


Caution


Note


End of HA (UNIX)




Caution


Procedure


Note





46198 PUBLIC 03282008



Note


End of HA (UNIX)






Procedure






n usrsaptrans


03282008 PUBLIC 47198


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt





sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt

48198 PUBLIC 03282008



sapmntltSIDgt

End of HA (UNIX)

End of HA (UNIX)



Caution


Prerequisites



Process Flow





Note



03282008 PUBLIC 49198



Note





Note






Note


Prerequisites


50198 PUBLIC 03282008



Procedure



Note







Note





03282008 PUBLIC 51198























52198 PUBLIC 03282008

















Other Requirements







03282008 PUBLIC 53198




Recommendation


Caution


Caution









54198 PUBLIC 03282008
























03282008 PUBLIC 55198







Note













56198 PUBLIC 03282008

























03282008 PUBLIC 57198



Recommendation


Caution


Caution












58198 PUBLIC 03282008





Center














03282008 PUBLIC 59198


















Recommendation


Procedure


60198 PUBLIC 03282008




Note




Note



smitty orsmit



03282008 PUBLIC 61198












Caution



62198 PUBLIC 03282008




Caution



Users and Groups


Caution


Caution


Caution


Users and Groups

03282008 PUBLIC 63198






Caution


Caution


Groups and Members

Groups Members











64198 PUBLIC 03282008



passwd ltusergt

Example





Note







03282008 PUBLIC 65198





341 SAP Directories



Note


End of HA (UNIX)

Caution


66198 PUBLIC 03282008





03282008 PUBLIC 67198






Example




68198 PUBLIC 03282008




Example



Note



SAP Directories






n Dialog instance

03282008 PUBLIC 69198





n global


n profile










20 GBl AS Java




70198 PUBLIC 03282008









03282008 PUBLIC 71198










Note


72198 PUBLIC 03282008







n script



l smdstopsh


l smdadminsh


n work





n smdstopsh


n smdadminsh


500 MB



03282008 PUBLIC 73198


Note




Oracle Directories





100 MB


55 GB

74198 PUBLIC 03282008

















15 GB

03282008 PUBLIC 75198












Note







76198 PUBLIC 03282008



Caution



Example






Note


Example




Caution



03282008 PUBLIC 77198




there




Note










78198 PUBLIC 03282008
















Caution


03282008 PUBLIC 79198




Caution



Procedure







80198 PUBLIC 03282008



Note


Procedure


Note




Note




03282008 PUBLIC 81198






Procedure


Caution



Note



Note



Note


End of BI Java

82198 PUBLIC 03282008


Note














03282008 PUBLIC 83198


Note




Caution








Procedure


84198 PUBLIC 03282008




Example

51031387_151031387_2




Note



Note



Procedure





03282008 PUBLIC 85198


Example




Note




86198 PUBLIC 03282008

4 Installation

4 Installation

Note



Process Flow

1




Note





Prerequisites



03282008 PUBLIC 87198


Caution





Procedure





Note



88198 PUBLIC 03282008


Note


End of HA (UNIX)




Prerequisites



Procedure


Note




03282008 PUBLIC 89198



Example


n DEFAULTPFL









Note


90198 PUBLIC 03282008


Caution



Shell Used Command


export TEMP







Shell Used Command


export DISPLAY




Output Properties

cputime unlimited

filesize unlimited

datasize 2097148 KB

stacksize 8192 KB


03282008 PUBLIC 91198


Output Properties

descriptors 8192



Output Properties




stack(kbytes) 8192





Example






Prerequisites



92198 PUBLIC 03282008


Procedure





Caution













03282008 PUBLIC 93198





Procedure


Caution





sapinst

94198 PUBLIC 03282008



Note


End of HA (UNIX)

Caution


Caution






Note



-p

03282008 PUBLIC 95198








l




Note









96198 PUBLIC 03282008



















03282008 PUBLIC 97198


















98198 PUBLIC 03282008
















03282008 PUBLIC 99198






Note






Note



Note


100198 PUBLIC 03282008


Recommendation







Caution



Procedure




03282008 PUBLIC 101198



















Note


102198 PUBLIC 03282008




















03282008 PUBLIC 103198







Option Definition




Note




Caution



104198 PUBLIC 03282008


Note



sapinst


Note








Prerequisites



03282008 PUBLIC 105198


Procedure


Caution




sapinst -nogui













106198 PUBLIC 03282008






Note





Caution



Note






03282008 PUBLIC 107198




Note





sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note




Caution



108198 PUBLIC 03282008


Process Flow




Procedure















03282008 PUBLIC 109198



Procedure









Procedure




Shell Used Command


export DISPLAY

110198 PUBLIC 03282008


Shell Used Command





RUNINSTALLER


RUNINSTALLER













03282008 PUBLIC 111198




Note




Prerequisites


Caution



Procedure




112198 PUBLIC 03282008


Prerequisites


Procedure


Note




03282008 PUBLIC 113198


5 Post-Installation

5 Post-Installation

Note





Note


3



Note



4




Caution



Caution


03282008 PUBLIC 115198

5 Post-Installation


Caution



Caution



Caution



Caution



14



15



16



17



Caution


End of HA (UNIX)

116198 PUBLIC 03282008



19



Caution









Procedure



Example




03282008 PUBLIC 117198


ABAP Users



DDIC 000 001

Java User



Prerequisites






Note






118198 PUBLIC 03282008


Note


Example




Note



to 0




Java User





03282008 PUBLIC 119198




Note


Example







Procedure


Note


Example


120198 PUBLIC 03282008










Note




Caution



Caution



03282008 PUBLIC 121198







Caution





Caution



122198 PUBLIC 03282008




Note






Caution


Caution


Caution




03282008 PUBLIC 123198





Procedure









124198 PUBLIC 03282008


Note



Caution



Procedure














03282008 PUBLIC 125198
















126198 PUBLIC 03282008







Note




Caution






03282008 PUBLIC 127198






Caution



Procedure







128198 PUBLIC 03282008





Caution


Prerequisites




Note



n usrsapltSAPSIDgt

n usrsaptrans






03282008 PUBLIC 129198





Caution











Note



130198 PUBLIC 03282008











Procedure




03282008 PUBLIC 131198





Caution








132198 PUBLIC 03282008








Note










03282008 PUBLIC 133198











Caution


134198 PUBLIC 03282008




Procedure









Caution



03282008 PUBLIC 135198






Recommendation



Caution




136198 PUBLIC 03282008









SYSTEM ‒

SYS ‒

OUTLN ‒


DBSNMP ‒

ABAP+Java Users







SAP system user


03282008 PUBLIC 137198



























138198 PUBLIC 03282008




None



None


















03282008 PUBLIC 139198

























140198 PUBLIC 03282008

























03282008 PUBLIC 141198






Note


End of BI Java







Note



142198 PUBLIC 03282008









Caution





Recommendation


End of BI Java



03282008 PUBLIC 143198








Procedure



Manual Contents





144198 PUBLIC 03282008


Manual Contents













03282008 PUBLIC 145198


Note



Prerequisites




Procedure








SAP NetWeaver 70


146198 PUBLIC 03282008





Procedure





03282008 PUBLIC 147198





Preparation


Installation


Post-Installation






Caution



03282008 PUBLIC 149198


Example




Prerequisites




Features





Note


150198 PUBLIC 03282008


Constraints

Recommendation











03282008 PUBLIC 151198


Note





Caution








152198 PUBLIC 03282008



SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=






SAP MMC


03282008 PUBLIC 153198



SAP MC










Note




154198 PUBLIC 03282008







Restrictions



n



Prerequisites



03282008 PUBLIC 155198


Preparation


Note













AS Java


AS Java


AS Java



AS ABAP AS Java

156198 PUBLIC 03282008



Note







Recommendation



n








BIWDALV_SCA VCKITBI


End of BI Java

03282008 PUBLIC 157198


n








n











n









RTC_SCA RTC 700



VCBASE_SCA VCBASE

VCFLEX_SCA VCFLEX

VCKITGP_SCA VCKITGP

158198 PUBLIC 03282008



VCKITXX_SCA VCKITXX




n











7







Note



03282008 PUBLIC 159198



Installation










Example





160198 PUBLIC 03282008


Caution



Note








Note



03282008 PUBLIC 161198


Prerequisites





Example



Note



Note







162198 PUBLIC 03282008


Note











Note






03282008 PUBLIC 163198






Prerequisites




Note


3 Choose Finish




Note




164198 PUBLIC 03282008









Prerequisites






03282008 PUBLIC 165198


Caution




Note




Procedure




Note






Note



startdb

166198 PUBLIC 03282008




Note



Note




Note




stopsap DB


Note





03282008 PUBLIC 167198


stopsap


Caution




Note




Procedure






Example

smdstart SMD 98

168198 PUBLIC 03282008


Note







Example

smdstop SMD 98

Note





Procedure




Example


03282008 PUBLIC 169198








Note


l EP Core (EPC)






n



n



n



170198 PUBLIC 03282008


n














03282008 PUBLIC 171198



Guides




l CAFAdmin

l CAFUIAdmin









172198 PUBLIC 03282008









More Information








03282008 PUBLIC 173198







l NWDI_ADM

l NWDI_DEV

l NWDI_CMSADM



l NWDIAdministrator

l NWDIDeveloper


l CBSAdministrator



l CBSDeveloper

l CMSDisplay

l CMSExportOwn




l NWDIDevelopers






174198 PUBLIC 03282008














Note





03282008 PUBLIC 175198











in SAP Note 883948




Note


Procedure




176198 PUBLIC 03282008








Caution



Caution




03282008 PUBLIC 177198












178198 PUBLIC 03282008


















03282008 PUBLIC 179198


Note







Procedure




End of BI Java





180198 PUBLIC 03282008




69 Troubleshooting



n






Procedure










03282008 PUBLIC 181198





Procedure














to bak




182198 PUBLIC 03282008


Note







Caution






Caution


Caution


03282008 PUBLIC 183198


Caution




Prerequisites



Procedure


Note



Note



Caution


184198 PUBLIC 03282008






Note


Procedure



runInstaller


runInstaller






03282008 PUBLIC 185198


b) Central instance

Note



Note






Note



Procedure





186198 PUBLIC 03282008




Example







Caution



Procedure







03282008 PUBLIC 187198


Caution


Recommendation




Example

rm -rf homec11adm









Note


Caution


188198 PUBLIC 03282008


Process

Caution






Note



j2eedbtype =

j2eedbhost =

j2eedbadminurl =

j2eescshost =

j2eescssystem =

j2eemsport =


exejlaunch =


rdispj2ee_start =

rdispj2ee_timeout =

rdispj2ee_libpath =


03282008 PUBLIC 189198




jstartupprotocol =

jstartupvmhome =


jstartuprelease =

j2eedbdriver =






Caution


Prerequisites



Procedure

Caution



sqlplus nolog



190198 PUBLIC 03282008









Caution


Prerequisites



Procedure


sqlplus nolog



SQLPLUSgt exit




03282008 PUBLIC 191198




runInstaller


runInstaller






Example






192198 PUBLIC 03282008


Example Description














03282008 PUBLIC 193198



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom





194198 PUBLIC 03282008














03282008 PUBLIC 195198












196198 PUBLIC 03282008



03282008 PUBLIC 197198



Table of Contents




03282008 PUBLIC 3198




4198 PUBLIC 03282008






03282008 PUBLIC 5198


6198 PUBLIC 03282008

1 Introduction

1 Introduction


n



Note




n



n



n





03282008 PUBLIC 7198

1 Introduction

n



n



n







Caution



Constraints




8198 PUBLIC 03282008




11 New Features


Caution



Area Description







instance

03282008 PUBLIC 9198


Area Description



















10198 PUBLIC 03282008


Area Description











Area Description




Oracle Database




03282008 PUBLIC 11198


Documentation

Area Description
























12198 PUBLIC 03282008















Documentation














03282008 PUBLIC 13198












































General Quick Links




httphelpsapcomnw70

14198 PUBLIC 03282008


































03282008 PUBLIC 15198




Terminology


Variables













Example


16198 PUBLIC 03282008

2 Planning

2 Planning





8





Caution




03282008 PUBLIC 17198


Note



Note



Caution




Note


18198 PUBLIC 03282008






03282008 PUBLIC 19198




End of HA (UNIX)







20198 PUBLIC 03282008



Note





3







03282008 PUBLIC 21198



Caution






Figure 5


22198 PUBLIC 03282008


Caution













03282008 PUBLIC 23198











Note


24198 PUBLIC 03282008











USR VAR







SYS TMP UID USR VAR


03282008 PUBLIC 25198

















26198 PUBLIC 03282008




Master Password




03282008 PUBLIC 27198





















28198 PUBLIC 03282008










03282008 PUBLIC 29198















30198 PUBLIC 03282008






















03282008 PUBLIC 31198





















32198 PUBLIC 03282008


















03282008 PUBLIC 33198
















homeltusernamegt

34198 PUBLIC 03282008













03282008 PUBLIC 35198












36198 PUBLIC 03282008











03282008 PUBLIC 37198











38198 PUBLIC 03282008



Recommendation






Recommendation







03282008 PUBLIC 39198


Figure 6

Note



40198 PUBLIC 03282008


Figure 7


03282008 PUBLIC 41198


3 Preparation

3 Preparation


1




Caution







Caution



Caution


03282008 PUBLIC 43198









Procedure



Caution


Recommendation


44198 PUBLIC 03282008




Example


Figure 8


Caution



03282008 PUBLIC 45198


Caution


Note


End of HA (UNIX)




Caution


Procedure


Note





46198 PUBLIC 03282008



Note


End of HA (UNIX)






Procedure






n usrsaptrans


03282008 PUBLIC 47198


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt





sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt

48198 PUBLIC 03282008



sapmntltSIDgt

End of HA (UNIX)

End of HA (UNIX)



Caution


Prerequisites



Process Flow





Note



03282008 PUBLIC 49198



Note





Note






Note


Prerequisites


50198 PUBLIC 03282008



Procedure



Note







Note





03282008 PUBLIC 51198























52198 PUBLIC 03282008

















Other Requirements







03282008 PUBLIC 53198




Recommendation


Caution


Caution









54198 PUBLIC 03282008
























03282008 PUBLIC 55198







Note













56198 PUBLIC 03282008

























03282008 PUBLIC 57198



Recommendation


Caution


Caution












58198 PUBLIC 03282008





Center














03282008 PUBLIC 59198


















Recommendation


Procedure


60198 PUBLIC 03282008




Note




Note



smitty orsmit



03282008 PUBLIC 61198












Caution



62198 PUBLIC 03282008




Caution



Users and Groups


Caution


Caution


Caution


Users and Groups

03282008 PUBLIC 63198






Caution


Caution


Groups and Members

Groups Members











64198 PUBLIC 03282008



passwd ltusergt

Example





Note







03282008 PUBLIC 65198





341 SAP Directories



Note


End of HA (UNIX)

Caution


66198 PUBLIC 03282008





03282008 PUBLIC 67198






Example




68198 PUBLIC 03282008




Example



Note



SAP Directories






n Dialog instance

03282008 PUBLIC 69198





n global


n profile










20 GBl AS Java




70198 PUBLIC 03282008









03282008 PUBLIC 71198










Note


72198 PUBLIC 03282008







n script



l smdstopsh


l smdadminsh


n work





n smdstopsh


n smdadminsh


500 MB



03282008 PUBLIC 73198


Note




Oracle Directories





100 MB


55 GB

74198 PUBLIC 03282008

















15 GB

03282008 PUBLIC 75198












Note







76198 PUBLIC 03282008



Caution



Example






Note


Example




Caution



03282008 PUBLIC 77198




there




Note










78198 PUBLIC 03282008
















Caution


03282008 PUBLIC 79198




Caution



Procedure







80198 PUBLIC 03282008



Note


Procedure


Note




Note




03282008 PUBLIC 81198






Procedure


Caution



Note



Note



Note


End of BI Java

82198 PUBLIC 03282008


Note














03282008 PUBLIC 83198


Note




Caution








Procedure


84198 PUBLIC 03282008




Example

51031387_151031387_2




Note



Note



Procedure





03282008 PUBLIC 85198


Example




Note




86198 PUBLIC 03282008

4 Installation

4 Installation

Note



Process Flow

1




Note





Prerequisites



03282008 PUBLIC 87198


Caution





Procedure





Note



88198 PUBLIC 03282008


Note


End of HA (UNIX)




Prerequisites



Procedure


Note




03282008 PUBLIC 89198



Example


n DEFAULTPFL









Note


90198 PUBLIC 03282008


Caution



Shell Used Command


export TEMP







Shell Used Command


export DISPLAY




Output Properties

cputime unlimited

filesize unlimited

datasize 2097148 KB

stacksize 8192 KB


03282008 PUBLIC 91198


Output Properties

descriptors 8192



Output Properties




stack(kbytes) 8192





Example






Prerequisites



92198 PUBLIC 03282008


Procedure





Caution













03282008 PUBLIC 93198





Procedure


Caution





sapinst

94198 PUBLIC 03282008



Note


End of HA (UNIX)

Caution


Caution






Note



-p

03282008 PUBLIC 95198








l




Note









96198 PUBLIC 03282008



















03282008 PUBLIC 97198


















98198 PUBLIC 03282008
















03282008 PUBLIC 99198






Note






Note



Note


100198 PUBLIC 03282008


Recommendation







Caution



Procedure




03282008 PUBLIC 101198



















Note


102198 PUBLIC 03282008




















03282008 PUBLIC 103198







Option Definition




Note




Caution



104198 PUBLIC 03282008


Note



sapinst


Note








Prerequisites



03282008 PUBLIC 105198


Procedure


Caution




sapinst -nogui













106198 PUBLIC 03282008






Note





Caution



Note






03282008 PUBLIC 107198




Note





sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note




Caution



108198 PUBLIC 03282008


Process Flow




Procedure















03282008 PUBLIC 109198



Procedure









Procedure




Shell Used Command


export DISPLAY

110198 PUBLIC 03282008


Shell Used Command





RUNINSTALLER


RUNINSTALLER













03282008 PUBLIC 111198




Note




Prerequisites


Caution



Procedure




112198 PUBLIC 03282008


Prerequisites


Procedure


Note




03282008 PUBLIC 113198


5 Post-Installation

5 Post-Installation

Note





Note


3



Note



4




Caution



Caution


03282008 PUBLIC 115198

5 Post-Installation


Caution



Caution



Caution



Caution



14



15



16



17



Caution


End of HA (UNIX)

116198 PUBLIC 03282008



19



Caution









Procedure



Example




03282008 PUBLIC 117198


ABAP Users



DDIC 000 001

Java User



Prerequisites






Note






118198 PUBLIC 03282008


Note


Example




Note



to 0




Java User





03282008 PUBLIC 119198




Note


Example







Procedure


Note


Example


120198 PUBLIC 03282008










Note




Caution



Caution



03282008 PUBLIC 121198







Caution





Caution



122198 PUBLIC 03282008




Note






Caution


Caution


Caution




03282008 PUBLIC 123198





Procedure









124198 PUBLIC 03282008


Note



Caution



Procedure














03282008 PUBLIC 125198
















126198 PUBLIC 03282008







Note




Caution






03282008 PUBLIC 127198






Caution



Procedure







128198 PUBLIC 03282008





Caution


Prerequisites




Note



n usrsapltSAPSIDgt

n usrsaptrans






03282008 PUBLIC 129198





Caution











Note



130198 PUBLIC 03282008











Procedure




03282008 PUBLIC 131198





Caution








132198 PUBLIC 03282008








Note










03282008 PUBLIC 133198











Caution


134198 PUBLIC 03282008




Procedure









Caution



03282008 PUBLIC 135198






Recommendation



Caution




136198 PUBLIC 03282008









SYSTEM ‒

SYS ‒

OUTLN ‒


DBSNMP ‒

ABAP+Java Users







SAP system user


03282008 PUBLIC 137198



























138198 PUBLIC 03282008




None



None


















03282008 PUBLIC 139198

























140198 PUBLIC 03282008

























03282008 PUBLIC 141198






Note


End of BI Java







Note



142198 PUBLIC 03282008









Caution





Recommendation


End of BI Java



03282008 PUBLIC 143198








Procedure



Manual Contents





144198 PUBLIC 03282008


Manual Contents













03282008 PUBLIC 145198


Note



Prerequisites




Procedure








SAP NetWeaver 70


146198 PUBLIC 03282008





Procedure





03282008 PUBLIC 147198





Preparation


Installation


Post-Installation






Caution



03282008 PUBLIC 149198


Example




Prerequisites




Features





Note


150198 PUBLIC 03282008


Constraints

Recommendation











03282008 PUBLIC 151198


Note





Caution








152198 PUBLIC 03282008



SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=






SAP MMC


03282008 PUBLIC 153198



SAP MC










Note




154198 PUBLIC 03282008







Restrictions



n



Prerequisites



03282008 PUBLIC 155198


Preparation


Note













AS Java


AS Java


AS Java



AS ABAP AS Java

156198 PUBLIC 03282008



Note







Recommendation



n








BIWDALV_SCA VCKITBI


End of BI Java

03282008 PUBLIC 157198


n








n











n









RTC_SCA RTC 700



VCBASE_SCA VCBASE

VCFLEX_SCA VCFLEX

VCKITGP_SCA VCKITGP

158198 PUBLIC 03282008



VCKITXX_SCA VCKITXX




n











7







Note



03282008 PUBLIC 159198



Installation










Example





160198 PUBLIC 03282008


Caution



Note








Note



03282008 PUBLIC 161198


Prerequisites





Example



Note



Note







162198 PUBLIC 03282008


Note











Note






03282008 PUBLIC 163198






Prerequisites




Note


3 Choose Finish




Note




164198 PUBLIC 03282008









Prerequisites






03282008 PUBLIC 165198


Caution




Note




Procedure




Note






Note



startdb

166198 PUBLIC 03282008




Note



Note




Note




stopsap DB


Note





03282008 PUBLIC 167198


stopsap


Caution




Note




Procedure






Example

smdstart SMD 98

168198 PUBLIC 03282008


Note







Example

smdstop SMD 98

Note





Procedure




Example


03282008 PUBLIC 169198








Note


l EP Core (EPC)






n



n



n



170198 PUBLIC 03282008


n














03282008 PUBLIC 171198



Guides




l CAFAdmin

l CAFUIAdmin









172198 PUBLIC 03282008









More Information








03282008 PUBLIC 173198







l NWDI_ADM

l NWDI_DEV

l NWDI_CMSADM



l NWDIAdministrator

l NWDIDeveloper


l CBSAdministrator



l CBSDeveloper

l CMSDisplay

l CMSExportOwn




l NWDIDevelopers






174198 PUBLIC 03282008














Note





03282008 PUBLIC 175198











in SAP Note 883948




Note


Procedure




176198 PUBLIC 03282008








Caution



Caution




03282008 PUBLIC 177198












178198 PUBLIC 03282008


















03282008 PUBLIC 179198


Note







Procedure




End of BI Java





180198 PUBLIC 03282008




69 Troubleshooting



n






Procedure










03282008 PUBLIC 181198





Procedure














to bak




182198 PUBLIC 03282008


Note







Caution






Caution


Caution


03282008 PUBLIC 183198


Caution




Prerequisites



Procedure


Note



Note



Caution


184198 PUBLIC 03282008






Note


Procedure



runInstaller


runInstaller






03282008 PUBLIC 185198


b) Central instance

Note



Note






Note



Procedure





186198 PUBLIC 03282008




Example







Caution



Procedure







03282008 PUBLIC 187198


Caution


Recommendation




Example

rm -rf homec11adm









Note


Caution


188198 PUBLIC 03282008


Process

Caution






Note



j2eedbtype =

j2eedbhost =

j2eedbadminurl =

j2eescshost =

j2eescssystem =

j2eemsport =


exejlaunch =


rdispj2ee_start =

rdispj2ee_timeout =

rdispj2ee_libpath =


03282008 PUBLIC 189198




jstartupprotocol =

jstartupvmhome =


jstartuprelease =

j2eedbdriver =






Caution


Prerequisites



Procedure

Caution



sqlplus nolog



190198 PUBLIC 03282008









Caution


Prerequisites



Procedure


sqlplus nolog



SQLPLUSgt exit




03282008 PUBLIC 191198




runInstaller


runInstaller






Example






192198 PUBLIC 03282008


Example Description














03282008 PUBLIC 193198



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom





194198 PUBLIC 03282008














03282008 PUBLIC 195198












196198 PUBLIC 03282008



03282008 PUBLIC 197198






4198 PUBLIC 03282008






03282008 PUBLIC 5198


6198 PUBLIC 03282008

1 Introduction

1 Introduction


n



Note




n



n



n





03282008 PUBLIC 7198

1 Introduction

n



n



n







Caution



Constraints




8198 PUBLIC 03282008




11 New Features


Caution



Area Description







instance

03282008 PUBLIC 9198


Area Description



















10198 PUBLIC 03282008


Area Description











Area Description




Oracle Database




03282008 PUBLIC 11198


Documentation

Area Description
























12198 PUBLIC 03282008















Documentation














03282008 PUBLIC 13198












































General Quick Links




httphelpsapcomnw70

14198 PUBLIC 03282008


































03282008 PUBLIC 15198




Terminology


Variables













Example


16198 PUBLIC 03282008

2 Planning

2 Planning





8





Caution




03282008 PUBLIC 17198


Note



Note



Caution




Note


18198 PUBLIC 03282008






03282008 PUBLIC 19198




End of HA (UNIX)







20198 PUBLIC 03282008



Note





3







03282008 PUBLIC 21198



Caution






Figure 5


22198 PUBLIC 03282008


Caution













03282008 PUBLIC 23198











Note


24198 PUBLIC 03282008











USR VAR







SYS TMP UID USR VAR


03282008 PUBLIC 25198

















26198 PUBLIC 03282008




Master Password




03282008 PUBLIC 27198





















28198 PUBLIC 03282008










03282008 PUBLIC 29198















30198 PUBLIC 03282008






















03282008 PUBLIC 31198





















32198 PUBLIC 03282008


















03282008 PUBLIC 33198
















homeltusernamegt

34198 PUBLIC 03282008













03282008 PUBLIC 35198












36198 PUBLIC 03282008











03282008 PUBLIC 37198











38198 PUBLIC 03282008



Recommendation






Recommendation







03282008 PUBLIC 39198


Figure 6

Note



40198 PUBLIC 03282008


Figure 7


03282008 PUBLIC 41198


3 Preparation

3 Preparation


1




Caution







Caution



Caution


03282008 PUBLIC 43198









Procedure



Caution


Recommendation


44198 PUBLIC 03282008




Example


Figure 8


Caution



03282008 PUBLIC 45198


Caution


Note


End of HA (UNIX)




Caution


Procedure


Note





46198 PUBLIC 03282008



Note


End of HA (UNIX)






Procedure






n usrsaptrans


03282008 PUBLIC 47198


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt





sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt

48198 PUBLIC 03282008



sapmntltSIDgt

End of HA (UNIX)

End of HA (UNIX)



Caution


Prerequisites



Process Flow





Note



03282008 PUBLIC 49198



Note





Note






Note


Prerequisites


50198 PUBLIC 03282008



Procedure



Note







Note





03282008 PUBLIC 51198























52198 PUBLIC 03282008

















Other Requirements







03282008 PUBLIC 53198




Recommendation


Caution


Caution









54198 PUBLIC 03282008
























03282008 PUBLIC 55198







Note













56198 PUBLIC 03282008

























03282008 PUBLIC 57198



Recommendation


Caution


Caution












58198 PUBLIC 03282008





Center














03282008 PUBLIC 59198


















Recommendation


Procedure


60198 PUBLIC 03282008




Note




Note



smitty orsmit



03282008 PUBLIC 61198












Caution



62198 PUBLIC 03282008




Caution



Users and Groups


Caution


Caution


Caution


Users and Groups

03282008 PUBLIC 63198






Caution


Caution


Groups and Members

Groups Members











64198 PUBLIC 03282008



passwd ltusergt

Example





Note







03282008 PUBLIC 65198





341 SAP Directories



Note


End of HA (UNIX)

Caution


66198 PUBLIC 03282008





03282008 PUBLIC 67198






Example




68198 PUBLIC 03282008




Example



Note



SAP Directories






n Dialog instance

03282008 PUBLIC 69198





n global


n profile










20 GBl AS Java




70198 PUBLIC 03282008









03282008 PUBLIC 71198










Note


72198 PUBLIC 03282008







n script



l smdstopsh


l smdadminsh


n work





n smdstopsh


n smdadminsh


500 MB



03282008 PUBLIC 73198


Note




Oracle Directories





100 MB


55 GB

74198 PUBLIC 03282008

















15 GB

03282008 PUBLIC 75198












Note







76198 PUBLIC 03282008



Caution



Example






Note


Example




Caution



03282008 PUBLIC 77198




there




Note










78198 PUBLIC 03282008
















Caution


03282008 PUBLIC 79198




Caution



Procedure







80198 PUBLIC 03282008



Note


Procedure


Note




Note




03282008 PUBLIC 81198






Procedure


Caution



Note



Note



Note


End of BI Java

82198 PUBLIC 03282008


Note














03282008 PUBLIC 83198


Note




Caution








Procedure


84198 PUBLIC 03282008




Example

51031387_151031387_2




Note



Note



Procedure





03282008 PUBLIC 85198


Example




Note




86198 PUBLIC 03282008

4 Installation

4 Installation

Note



Process Flow

1




Note





Prerequisites



03282008 PUBLIC 87198


Caution





Procedure





Note



88198 PUBLIC 03282008


Note


End of HA (UNIX)




Prerequisites



Procedure


Note




03282008 PUBLIC 89198



Example


n DEFAULTPFL









Note


90198 PUBLIC 03282008


Caution



Shell Used Command


export TEMP







Shell Used Command


export DISPLAY




Output Properties

cputime unlimited

filesize unlimited

datasize 2097148 KB

stacksize 8192 KB


03282008 PUBLIC 91198


Output Properties

descriptors 8192



Output Properties




stack(kbytes) 8192





Example






Prerequisites



92198 PUBLIC 03282008


Procedure





Caution













03282008 PUBLIC 93198





Procedure


Caution





sapinst

94198 PUBLIC 03282008



Note


End of HA (UNIX)

Caution


Caution






Note



-p

03282008 PUBLIC 95198








l




Note









96198 PUBLIC 03282008



















03282008 PUBLIC 97198


















98198 PUBLIC 03282008
















03282008 PUBLIC 99198






Note






Note



Note


100198 PUBLIC 03282008


Recommendation







Caution



Procedure




03282008 PUBLIC 101198



















Note


102198 PUBLIC 03282008




















03282008 PUBLIC 103198







Option Definition




Note




Caution



104198 PUBLIC 03282008


Note



sapinst


Note








Prerequisites



03282008 PUBLIC 105198


Procedure


Caution




sapinst -nogui













106198 PUBLIC 03282008






Note





Caution



Note






03282008 PUBLIC 107198




Note





sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note




Caution



108198 PUBLIC 03282008


Process Flow




Procedure















03282008 PUBLIC 109198



Procedure









Procedure




Shell Used Command


export DISPLAY

110198 PUBLIC 03282008


Shell Used Command





RUNINSTALLER


RUNINSTALLER













03282008 PUBLIC 111198




Note




Prerequisites


Caution



Procedure




112198 PUBLIC 03282008


Prerequisites


Procedure


Note




03282008 PUBLIC 113198


5 Post-Installation

5 Post-Installation

Note





Note


3



Note



4




Caution



Caution


03282008 PUBLIC 115198

5 Post-Installation


Caution



Caution



Caution



Caution



14



15



16



17



Caution


End of HA (UNIX)

116198 PUBLIC 03282008



19



Caution









Procedure



Example




03282008 PUBLIC 117198


ABAP Users



DDIC 000 001

Java User



Prerequisites






Note






118198 PUBLIC 03282008


Note


Example




Note



to 0




Java User





03282008 PUBLIC 119198




Note


Example







Procedure


Note


Example


120198 PUBLIC 03282008










Note




Caution



Caution



03282008 PUBLIC 121198







Caution





Caution



122198 PUBLIC 03282008




Note






Caution


Caution


Caution




03282008 PUBLIC 123198





Procedure









124198 PUBLIC 03282008


Note



Caution



Procedure














03282008 PUBLIC 125198
















126198 PUBLIC 03282008







Note




Caution






03282008 PUBLIC 127198






Caution



Procedure







128198 PUBLIC 03282008





Caution


Prerequisites




Note



n usrsapltSAPSIDgt

n usrsaptrans






03282008 PUBLIC 129198





Caution











Note



130198 PUBLIC 03282008











Procedure




03282008 PUBLIC 131198





Caution








132198 PUBLIC 03282008








Note










03282008 PUBLIC 133198











Caution


134198 PUBLIC 03282008




Procedure









Caution



03282008 PUBLIC 135198






Recommendation



Caution




136198 PUBLIC 03282008









SYSTEM ‒

SYS ‒

OUTLN ‒


DBSNMP ‒

ABAP+Java Users







SAP system user


03282008 PUBLIC 137198



























138198 PUBLIC 03282008




None



None


















03282008 PUBLIC 139198

























140198 PUBLIC 03282008

























03282008 PUBLIC 141198






Note


End of BI Java







Note



142198 PUBLIC 03282008









Caution





Recommendation


End of BI Java



03282008 PUBLIC 143198








Procedure



Manual Contents





144198 PUBLIC 03282008


Manual Contents













03282008 PUBLIC 145198


Note



Prerequisites




Procedure








SAP NetWeaver 70


146198 PUBLIC 03282008





Procedure





03282008 PUBLIC 147198





Preparation


Installation


Post-Installation






Caution



03282008 PUBLIC 149198


Example




Prerequisites




Features





Note


150198 PUBLIC 03282008


Constraints

Recommendation











03282008 PUBLIC 151198


Note





Caution








152198 PUBLIC 03282008



SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=






SAP MMC


03282008 PUBLIC 153198



SAP MC










Note




154198 PUBLIC 03282008







Restrictions



n



Prerequisites



03282008 PUBLIC 155198


Preparation


Note













AS Java


AS Java


AS Java



AS ABAP AS Java

156198 PUBLIC 03282008



Note







Recommendation



n








BIWDALV_SCA VCKITBI


End of BI Java

03282008 PUBLIC 157198


n








n











n









RTC_SCA RTC 700



VCBASE_SCA VCBASE

VCFLEX_SCA VCFLEX

VCKITGP_SCA VCKITGP

158198 PUBLIC 03282008



VCKITXX_SCA VCKITXX




n











7







Note



03282008 PUBLIC 159198



Installation










Example





160198 PUBLIC 03282008


Caution



Note








Note



03282008 PUBLIC 161198


Prerequisites





Example



Note



Note







162198 PUBLIC 03282008


Note











Note






03282008 PUBLIC 163198






Prerequisites




Note


3 Choose Finish




Note




164198 PUBLIC 03282008









Prerequisites






03282008 PUBLIC 165198


Caution




Note




Procedure




Note






Note



startdb

166198 PUBLIC 03282008




Note



Note




Note




stopsap DB


Note





03282008 PUBLIC 167198


stopsap


Caution




Note




Procedure






Example

smdstart SMD 98

168198 PUBLIC 03282008


Note







Example

smdstop SMD 98

Note





Procedure




Example


03282008 PUBLIC 169198








Note


l EP Core (EPC)






n



n



n



170198 PUBLIC 03282008


n














03282008 PUBLIC 171198



Guides




l CAFAdmin

l CAFUIAdmin









172198 PUBLIC 03282008









More Information








03282008 PUBLIC 173198







l NWDI_ADM

l NWDI_DEV

l NWDI_CMSADM



l NWDIAdministrator

l NWDIDeveloper


l CBSAdministrator



l CBSDeveloper

l CMSDisplay

l CMSExportOwn




l NWDIDevelopers






174198 PUBLIC 03282008














Note





03282008 PUBLIC 175198











in SAP Note 883948




Note


Procedure




176198 PUBLIC 03282008








Caution



Caution




03282008 PUBLIC 177198












178198 PUBLIC 03282008


















03282008 PUBLIC 179198


Note







Procedure




End of BI Java





180198 PUBLIC 03282008




69 Troubleshooting



n






Procedure










03282008 PUBLIC 181198





Procedure














to bak




182198 PUBLIC 03282008


Note







Caution






Caution


Caution


03282008 PUBLIC 183198


Caution




Prerequisites



Procedure


Note



Note



Caution


184198 PUBLIC 03282008






Note


Procedure



runInstaller


runInstaller






03282008 PUBLIC 185198


b) Central instance

Note



Note






Note



Procedure





186198 PUBLIC 03282008




Example







Caution



Procedure







03282008 PUBLIC 187198


Caution


Recommendation




Example

rm -rf homec11adm









Note


Caution


188198 PUBLIC 03282008


Process

Caution






Note



j2eedbtype =

j2eedbhost =

j2eedbadminurl =

j2eescshost =

j2eescssystem =

j2eemsport =


exejlaunch =


rdispj2ee_start =

rdispj2ee_timeout =

rdispj2ee_libpath =


03282008 PUBLIC 189198




jstartupprotocol =

jstartupvmhome =


jstartuprelease =

j2eedbdriver =






Caution


Prerequisites



Procedure

Caution



sqlplus nolog



190198 PUBLIC 03282008









Caution


Prerequisites



Procedure


sqlplus nolog



SQLPLUSgt exit




03282008 PUBLIC 191198




runInstaller


runInstaller






Example






192198 PUBLIC 03282008


Example Description














03282008 PUBLIC 193198



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom





194198 PUBLIC 03282008














03282008 PUBLIC 195198












196198 PUBLIC 03282008



03282008 PUBLIC 197198








03282008 PUBLIC 5198


6198 PUBLIC 03282008

1 Introduction

1 Introduction


n



Note




n



n



n





03282008 PUBLIC 7198

1 Introduction

n



n



n







Caution



Constraints




8198 PUBLIC 03282008




11 New Features


Caution



Area Description







instance

03282008 PUBLIC 9198


Area Description



















10198 PUBLIC 03282008


Area Description











Area Description




Oracle Database




03282008 PUBLIC 11198


Documentation

Area Description
























12198 PUBLIC 03282008















Documentation














03282008 PUBLIC 13198












































General Quick Links




httphelpsapcomnw70

14198 PUBLIC 03282008


































03282008 PUBLIC 15198




Terminology


Variables













Example


16198 PUBLIC 03282008

2 Planning

2 Planning





8





Caution




03282008 PUBLIC 17198


Note



Note



Caution




Note


18198 PUBLIC 03282008






03282008 PUBLIC 19198




End of HA (UNIX)







20198 PUBLIC 03282008



Note





3







03282008 PUBLIC 21198



Caution






Figure 5


22198 PUBLIC 03282008


Caution













03282008 PUBLIC 23198











Note


24198 PUBLIC 03282008











USR VAR







SYS TMP UID USR VAR


03282008 PUBLIC 25198

















26198 PUBLIC 03282008




Master Password




03282008 PUBLIC 27198





















28198 PUBLIC 03282008










03282008 PUBLIC 29198















30198 PUBLIC 03282008






















03282008 PUBLIC 31198





















32198 PUBLIC 03282008


















03282008 PUBLIC 33198
















homeltusernamegt

34198 PUBLIC 03282008













03282008 PUBLIC 35198












36198 PUBLIC 03282008











03282008 PUBLIC 37198











38198 PUBLIC 03282008



Recommendation






Recommendation







03282008 PUBLIC 39198


Figure 6

Note



40198 PUBLIC 03282008


Figure 7


03282008 PUBLIC 41198


3 Preparation

3 Preparation


1




Caution







Caution



Caution


03282008 PUBLIC 43198









Procedure



Caution


Recommendation


44198 PUBLIC 03282008




Example


Figure 8


Caution



03282008 PUBLIC 45198


Caution


Note


End of HA (UNIX)




Caution


Procedure


Note





46198 PUBLIC 03282008



Note


End of HA (UNIX)






Procedure






n usrsaptrans


03282008 PUBLIC 47198


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt





sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt

48198 PUBLIC 03282008



sapmntltSIDgt

End of HA (UNIX)

End of HA (UNIX)



Caution


Prerequisites



Process Flow





Note



03282008 PUBLIC 49198



Note





Note






Note


Prerequisites


50198 PUBLIC 03282008



Procedure



Note







Note





03282008 PUBLIC 51198























52198 PUBLIC 03282008

















Other Requirements







03282008 PUBLIC 53198




Recommendation


Caution


Caution









54198 PUBLIC 03282008
























03282008 PUBLIC 55198







Note













56198 PUBLIC 03282008

























03282008 PUBLIC 57198



Recommendation


Caution


Caution












58198 PUBLIC 03282008





Center














03282008 PUBLIC 59198


















Recommendation


Procedure


60198 PUBLIC 03282008




Note




Note



smitty orsmit



03282008 PUBLIC 61198












Caution



62198 PUBLIC 03282008




Caution



Users and Groups


Caution


Caution


Caution


Users and Groups

03282008 PUBLIC 63198






Caution


Caution


Groups and Members

Groups Members











64198 PUBLIC 03282008



passwd ltusergt

Example





Note







03282008 PUBLIC 65198





341 SAP Directories



Note


End of HA (UNIX)

Caution


66198 PUBLIC 03282008





03282008 PUBLIC 67198






Example




68198 PUBLIC 03282008




Example



Note



SAP Directories






n Dialog instance

03282008 PUBLIC 69198





n global


n profile










20 GBl AS Java




70198 PUBLIC 03282008









03282008 PUBLIC 71198










Note


72198 PUBLIC 03282008







n script



l smdstopsh


l smdadminsh


n work





n smdstopsh


n smdadminsh


500 MB



03282008 PUBLIC 73198


Note




Oracle Directories





100 MB


55 GB

74198 PUBLIC 03282008

















15 GB

03282008 PUBLIC 75198












Note







76198 PUBLIC 03282008



Caution



Example






Note


Example




Caution



03282008 PUBLIC 77198




there




Note










78198 PUBLIC 03282008
















Caution


03282008 PUBLIC 79198




Caution



Procedure







80198 PUBLIC 03282008



Note


Procedure


Note




Note




03282008 PUBLIC 81198






Procedure


Caution



Note



Note



Note


End of BI Java

82198 PUBLIC 03282008


Note














03282008 PUBLIC 83198


Note




Caution








Procedure


84198 PUBLIC 03282008




Example

51031387_151031387_2




Note



Note



Procedure





03282008 PUBLIC 85198


Example




Note




86198 PUBLIC 03282008

4 Installation

4 Installation

Note



Process Flow

1




Note





Prerequisites



03282008 PUBLIC 87198


Caution





Procedure





Note



88198 PUBLIC 03282008


Note


End of HA (UNIX)




Prerequisites



Procedure


Note




03282008 PUBLIC 89198



Example


n DEFAULTPFL









Note


90198 PUBLIC 03282008


Caution



Shell Used Command


export TEMP







Shell Used Command


export DISPLAY




Output Properties

cputime unlimited

filesize unlimited

datasize 2097148 KB

stacksize 8192 KB


03282008 PUBLIC 91198


Output Properties

descriptors 8192



Output Properties




stack(kbytes) 8192





Example






Prerequisites



92198 PUBLIC 03282008


Procedure





Caution













03282008 PUBLIC 93198





Procedure


Caution





sapinst

94198 PUBLIC 03282008



Note


End of HA (UNIX)

Caution


Caution






Note



-p

03282008 PUBLIC 95198








l




Note









96198 PUBLIC 03282008



















03282008 PUBLIC 97198


















98198 PUBLIC 03282008
















03282008 PUBLIC 99198






Note






Note



Note


100198 PUBLIC 03282008


Recommendation







Caution



Procedure




03282008 PUBLIC 101198



















Note


102198 PUBLIC 03282008




















03282008 PUBLIC 103198







Option Definition




Note




Caution



104198 PUBLIC 03282008


Note



sapinst


Note








Prerequisites



03282008 PUBLIC 105198


Procedure


Caution




sapinst -nogui













106198 PUBLIC 03282008






Note





Caution



Note






03282008 PUBLIC 107198




Note





sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note




Caution



108198 PUBLIC 03282008


Process Flow




Procedure















03282008 PUBLIC 109198



Procedure









Procedure




Shell Used Command


export DISPLAY

110198 PUBLIC 03282008


Shell Used Command





RUNINSTALLER


RUNINSTALLER













03282008 PUBLIC 111198




Note




Prerequisites


Caution



Procedure




112198 PUBLIC 03282008


Prerequisites


Procedure


Note




03282008 PUBLIC 113198


5 Post-Installation

5 Post-Installation

Note





Note


3



Note



4




Caution



Caution


03282008 PUBLIC 115198

5 Post-Installation


Caution



Caution



Caution



Caution



14



15



16



17



Caution


End of HA (UNIX)

116198 PUBLIC 03282008



19



Caution









Procedure



Example




03282008 PUBLIC 117198


ABAP Users



DDIC 000 001

Java User



Prerequisites






Note






118198 PUBLIC 03282008


Note


Example




Note



to 0




Java User





03282008 PUBLIC 119198




Note


Example







Procedure


Note


Example


120198 PUBLIC 03282008










Note




Caution



Caution



03282008 PUBLIC 121198







Caution





Caution



122198 PUBLIC 03282008




Note






Caution


Caution


Caution




03282008 PUBLIC 123198





Procedure









124198 PUBLIC 03282008


Note



Caution



Procedure














03282008 PUBLIC 125198
















126198 PUBLIC 03282008







Note




Caution






03282008 PUBLIC 127198






Caution



Procedure







128198 PUBLIC 03282008





Caution


Prerequisites




Note



n usrsapltSAPSIDgt

n usrsaptrans






03282008 PUBLIC 129198





Caution











Note



130198 PUBLIC 03282008











Procedure




03282008 PUBLIC 131198





Caution








132198 PUBLIC 03282008








Note










03282008 PUBLIC 133198











Caution


134198 PUBLIC 03282008




Procedure









Caution



03282008 PUBLIC 135198






Recommendation



Caution




136198 PUBLIC 03282008









SYSTEM ‒

SYS ‒

OUTLN ‒


DBSNMP ‒

ABAP+Java Users







SAP system user


03282008 PUBLIC 137198



























138198 PUBLIC 03282008




None



None


















03282008 PUBLIC 139198

























140198 PUBLIC 03282008

























03282008 PUBLIC 141198






Note


End of BI Java







Note



142198 PUBLIC 03282008









Caution





Recommendation


End of BI Java



03282008 PUBLIC 143198








Procedure



Manual Contents





144198 PUBLIC 03282008


Manual Contents













03282008 PUBLIC 145198


Note



Prerequisites




Procedure








SAP NetWeaver 70


146198 PUBLIC 03282008





Procedure





03282008 PUBLIC 147198





Preparation


Installation


Post-Installation






Caution



03282008 PUBLIC 149198


Example




Prerequisites




Features





Note


150198 PUBLIC 03282008


Constraints

Recommendation











03282008 PUBLIC 151198


Note





Caution








152198 PUBLIC 03282008



SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=






SAP MMC


03282008 PUBLIC 153198



SAP MC










Note




154198 PUBLIC 03282008







Restrictions



n



Prerequisites



03282008 PUBLIC 155198


Preparation


Note













AS Java


AS Java


AS Java



AS ABAP AS Java

156198 PUBLIC 03282008



Note







Recommendation



n








BIWDALV_SCA VCKITBI


End of BI Java

03282008 PUBLIC 157198


n








n











n









RTC_SCA RTC 700



VCBASE_SCA VCBASE

VCFLEX_SCA VCFLEX

VCKITGP_SCA VCKITGP

158198 PUBLIC 03282008



VCKITXX_SCA VCKITXX




n











7







Note



03282008 PUBLIC 159198



Installation










Example





160198 PUBLIC 03282008


Caution



Note








Note



03282008 PUBLIC 161198


Prerequisites





Example



Note



Note







162198 PUBLIC 03282008


Note











Note






03282008 PUBLIC 163198






Prerequisites




Note


3 Choose Finish




Note




164198 PUBLIC 03282008









Prerequisites






03282008 PUBLIC 165198


Caution




Note




Procedure




Note






Note



startdb

166198 PUBLIC 03282008




Note



Note




Note




stopsap DB


Note





03282008 PUBLIC 167198


stopsap


Caution




Note




Procedure






Example

smdstart SMD 98

168198 PUBLIC 03282008


Note







Example

smdstop SMD 98

Note





Procedure




Example


03282008 PUBLIC 169198








Note


l EP Core (EPC)






n



n



n



170198 PUBLIC 03282008


n














03282008 PUBLIC 171198



Guides




l CAFAdmin

l CAFUIAdmin









172198 PUBLIC 03282008









More Information








03282008 PUBLIC 173198







l NWDI_ADM

l NWDI_DEV

l NWDI_CMSADM



l NWDIAdministrator

l NWDIDeveloper


l CBSAdministrator



l CBSDeveloper

l CMSDisplay

l CMSExportOwn




l NWDIDevelopers






174198 PUBLIC 03282008














Note





03282008 PUBLIC 175198











in SAP Note 883948




Note


Procedure




176198 PUBLIC 03282008








Caution



Caution




03282008 PUBLIC 177198












178198 PUBLIC 03282008


















03282008 PUBLIC 179198


Note







Procedure




End of BI Java





180198 PUBLIC 03282008




69 Troubleshooting



n






Procedure










03282008 PUBLIC 181198





Procedure














to bak




182198 PUBLIC 03282008


Note







Caution






Caution


Caution


03282008 PUBLIC 183198


Caution




Prerequisites



Procedure


Note



Note



Caution


184198 PUBLIC 03282008






Note


Procedure



runInstaller


runInstaller






03282008 PUBLIC 185198


b) Central instance

Note



Note






Note



Procedure





186198 PUBLIC 03282008




Example







Caution



Procedure







03282008 PUBLIC 187198


Caution


Recommendation




Example

rm -rf homec11adm









Note


Caution


188198 PUBLIC 03282008


Process

Caution






Note



j2eedbtype =

j2eedbhost =

j2eedbadminurl =

j2eescshost =

j2eescssystem =

j2eemsport =


exejlaunch =


rdispj2ee_start =

rdispj2ee_timeout =

rdispj2ee_libpath =


03282008 PUBLIC 189198




jstartupprotocol =

jstartupvmhome =


jstartuprelease =

j2eedbdriver =






Caution


Prerequisites



Procedure

Caution



sqlplus nolog



190198 PUBLIC 03282008









Caution


Prerequisites



Procedure


sqlplus nolog



SQLPLUSgt exit




03282008 PUBLIC 191198




runInstaller


runInstaller






Example






192198 PUBLIC 03282008


Example Description














03282008 PUBLIC 193198



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom





194198 PUBLIC 03282008














03282008 PUBLIC 195198












196198 PUBLIC 03282008



03282008 PUBLIC 197198




6198 PUBLIC 03282008

1 Introduction

1 Introduction


n



Note




n



n



n





03282008 PUBLIC 7198

1 Introduction

n



n



n







Caution



Constraints




8198 PUBLIC 03282008




11 New Features


Caution



Area Description







instance

03282008 PUBLIC 9198


Area Description



















10198 PUBLIC 03282008


Area Description











Area Description




Oracle Database




03282008 PUBLIC 11198


Documentation

Area Description
























12198 PUBLIC 03282008















Documentation














03282008 PUBLIC 13198












































General Quick Links




httphelpsapcomnw70

14198 PUBLIC 03282008


































03282008 PUBLIC 15198




Terminology


Variables













Example


16198 PUBLIC 03282008

2 Planning

2 Planning





8





Caution




03282008 PUBLIC 17198


Note



Note



Caution




Note


18198 PUBLIC 03282008






03282008 PUBLIC 19198




End of HA (UNIX)







20198 PUBLIC 03282008



Note





3







03282008 PUBLIC 21198



Caution






Figure 5


22198 PUBLIC 03282008


Caution













03282008 PUBLIC 23198











Note


24198 PUBLIC 03282008











USR VAR







SYS TMP UID USR VAR


03282008 PUBLIC 25198

















26198 PUBLIC 03282008




Master Password




03282008 PUBLIC 27198





















28198 PUBLIC 03282008










03282008 PUBLIC 29198















30198 PUBLIC 03282008






















03282008 PUBLIC 31198





















32198 PUBLIC 03282008


















03282008 PUBLIC 33198
















homeltusernamegt

34198 PUBLIC 03282008













03282008 PUBLIC 35198












36198 PUBLIC 03282008











03282008 PUBLIC 37198











38198 PUBLIC 03282008



Recommendation






Recommendation







03282008 PUBLIC 39198


Figure 6

Note



40198 PUBLIC 03282008


Figure 7


03282008 PUBLIC 41198


3 Preparation

3 Preparation


1




Caution







Caution



Caution


03282008 PUBLIC 43198









Procedure



Caution


Recommendation


44198 PUBLIC 03282008




Example


Figure 8


Caution



03282008 PUBLIC 45198


Caution


Note


End of HA (UNIX)




Caution


Procedure


Note





46198 PUBLIC 03282008



Note


End of HA (UNIX)






Procedure






n usrsaptrans


03282008 PUBLIC 47198


n sapmntltSIDgtexe



exportusrsaptrans

exportsapmntltSIDgt






exportsapmntltSIDgt





sapmntltSIDgt


exportsapmntltSIDgt


exportusrsaptrans

exportsapmntltSIDgt

48198 PUBLIC 03282008



sapmntltSIDgt

End of HA (UNIX)

End of HA (UNIX)



Caution


Prerequisites



Process Flow





Note



03282008 PUBLIC 49198



Note





Note






Note


Prerequisites


50198 PUBLIC 03282008



Procedure



Note







Note





03282008 PUBLIC 51198























52198 PUBLIC 03282008

















Other Requirements







03282008 PUBLIC 53198




Recommendation


Caution


Caution









54198 PUBLIC 03282008
























03282008 PUBLIC 55198







Note













56198 PUBLIC 03282008

























03282008 PUBLIC 57198



Recommendation


Caution


Caution












58198 PUBLIC 03282008





Center














03282008 PUBLIC 59198


















Recommendation


Procedure


60198 PUBLIC 03282008




Note




Note



smitty orsmit



03282008 PUBLIC 61198












Caution



62198 PUBLIC 03282008




Caution



Users and Groups


Caution


Caution


Caution


Users and Groups

03282008 PUBLIC 63198






Caution


Caution


Groups and Members

Groups Members











64198 PUBLIC 03282008



passwd ltusergt

Example





Note







03282008 PUBLIC 65198





341 SAP Directories



Note


End of HA (UNIX)

Caution


66198 PUBLIC 03282008





03282008 PUBLIC 67198






Example




68198 PUBLIC 03282008




Example



Note



SAP Directories






n Dialog instance

03282008 PUBLIC 69198





n global


n profile










20 GBl AS Java




70198 PUBLIC 03282008









03282008 PUBLIC 71198










Note


72198 PUBLIC 03282008







n script



l smdstopsh


l smdadminsh


n work





n smdstopsh


n smdadminsh


500 MB



03282008 PUBLIC 73198


Note




Oracle Directories





100 MB


55 GB

74198 PUBLIC 03282008

















15 GB

03282008 PUBLIC 75198












Note







76198 PUBLIC 03282008



Caution



Example






Note


Example




Caution



03282008 PUBLIC 77198




there




Note










78198 PUBLIC 03282008
















Caution


03282008 PUBLIC 79198




Caution



Procedure







80198 PUBLIC 03282008



Note


Procedure


Note




Note




03282008 PUBLIC 81198






Procedure


Caution



Note



Note



Note


End of BI Java

82198 PUBLIC 03282008


Note














03282008 PUBLIC 83198


Note




Caution








Procedure


84198 PUBLIC 03282008




Example

51031387_151031387_2




Note



Note



Procedure





03282008 PUBLIC 85198


Example




Note




86198 PUBLIC 03282008

4 Installation

4 Installation

Note



Process Flow

1




Note





Prerequisites



03282008 PUBLIC 87198


Caution





Procedure





Note



88198 PUBLIC 03282008


Note


End of HA (UNIX)




Prerequisites



Procedure


Note




03282008 PUBLIC 89198



Example


n DEFAULTPFL









Note


90198 PUBLIC 03282008


Caution



Shell Used Command


export TEMP







Shell Used Command


export DISPLAY




Output Properties

cputime unlimited

filesize unlimited

datasize 2097148 KB

stacksize 8192 KB


03282008 PUBLIC 91198


Output Properties

descriptors 8192



Output Properties




stack(kbytes) 8192





Example






Prerequisites



92198 PUBLIC 03282008


Procedure





Caution













03282008 PUBLIC 93198





Procedure


Caution





sapinst

94198 PUBLIC 03282008



Note


End of HA (UNIX)

Caution


Caution






Note



-p

03282008 PUBLIC 95198








l




Note









96198 PUBLIC 03282008



















03282008 PUBLIC 97198


















98198 PUBLIC 03282008
















03282008 PUBLIC 99198






Note






Note



Note


100198 PUBLIC 03282008


Recommendation







Caution



Procedure




03282008 PUBLIC 101198



















Note


102198 PUBLIC 03282008




















03282008 PUBLIC 103198







Option Definition




Note




Caution



104198 PUBLIC 03282008


Note



sapinst


Note








Prerequisites



03282008 PUBLIC 105198


Procedure


Caution




sapinst -nogui













106198 PUBLIC 03282008






Note





Caution



Note






03282008 PUBLIC 107198




Note





sapdbXXs = 47XXtcp

sapgwXX = 33XXtcp

sapgwXXs = 48XXtcp


Note




Caution



108198 PUBLIC 03282008


Process Flow




Procedure















03282008 PUBLIC 109198



Procedure









Procedure




Shell Used Command


export DISPLAY

110198 PUBLIC 03282008


Shell Used Command





RUNINSTALLER


RUNINSTALLER













03282008 PUBLIC 111198




Note




Prerequisites


Caution



Procedure




112198 PUBLIC 03282008


Prerequisites


Procedure


Note




03282008 PUBLIC 113198


5 Post-Installation

5 Post-Installation

Note





Note


3



Note



4




Caution



Caution


03282008 PUBLIC 115198

5 Post-Installation


Caution



Caution



Caution



Caution



14



15



16



17



Caution


End of HA (UNIX)

116198 PUBLIC 03282008



19



Caution









Procedure



Example




03282008 PUBLIC 117198


ABAP Users



DDIC 000 001

Java User



Prerequisites






Note






118198 PUBLIC 03282008


Note


Example




Note



to 0




Java User





03282008 PUBLIC 119198




Note


Example







Procedure


Note


Example


120198 PUBLIC 03282008










Note




Caution



Caution



03282008 PUBLIC 121198







Caution





Caution



122198 PUBLIC 03282008




Note






Caution


Caution


Caution




03282008 PUBLIC 123198





Procedure









124198 PUBLIC 03282008


Note



Caution



Procedure














03282008 PUBLIC 125198
















126198 PUBLIC 03282008







Note




Caution






03282008 PUBLIC 127198






Caution



Procedure







128198 PUBLIC 03282008





Caution


Prerequisites




Note



n usrsapltSAPSIDgt

n usrsaptrans






03282008 PUBLIC 129198





Caution











Note



130198 PUBLIC 03282008











Procedure




03282008 PUBLIC 131198





Caution








132198 PUBLIC 03282008








Note










03282008 PUBLIC 133198











Caution


134198 PUBLIC 03282008




Procedure









Caution



03282008 PUBLIC 135198






Recommendation



Caution




136198 PUBLIC 03282008









SYSTEM ‒

SYS ‒

OUTLN ‒


DBSNMP ‒

ABAP+Java Users







SAP system user


03282008 PUBLIC 137198



























138198 PUBLIC 03282008




None



None


















03282008 PUBLIC 139198

























140198 PUBLIC 03282008

























03282008 PUBLIC 141198






Note


End of BI Java







Note



142198 PUBLIC 03282008









Caution





Recommendation


End of BI Java



03282008 PUBLIC 143198








Procedure



Manual Contents





144198 PUBLIC 03282008


Manual Contents













03282008 PUBLIC 145198


Note



Prerequisites




Procedure








SAP NetWeaver 70


146198 PUBLIC 03282008





Procedure





03282008 PUBLIC 147198





Preparation


Installation


Post-Installation






Caution



03282008 PUBLIC 149198


Example




Prerequisites




Features





Note


150198 PUBLIC 03282008


Constraints

Recommendation











03282008 PUBLIC 151198


Note





Caution








152198 PUBLIC 03282008



SAP Logon


Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=






SAP MMC


03282008 PUBLIC 153198



SAP MC










Note




154198 PUBLIC 03282008







Restrictions



n



Prerequisites



03282008 PUBLIC 155198


Preparation


Note













AS Java


AS Java


AS Java



AS ABAP AS Java

156198 PUBLIC 03282008



Note







Recommendation



n








BIWDALV_SCA VCKITBI


End of BI Java

03282008 PUBLIC 157198


n








n











n









RTC_SCA RTC 700



VCBASE_SCA VCBASE

VCFLEX_SCA VCFLEX

VCKITGP_SCA VCKITGP

158198 PUBLIC 03282008



VCKITXX_SCA VCKITXX




n











7







Note



03282008 PUBLIC 159198



Installation










Example





160198 PUBLIC 03282008


Caution



Note








Note



03282008 PUBLIC 161198


Prerequisites





Example



Note



Note







162198 PUBLIC 03282008


Note











Note






03282008 PUBLIC 163198






Prerequisites




Note


3 Choose Finish




Note




164198 PUBLIC 03282008









Prerequisites






03282008 PUBLIC 165198


Caution




Note




Procedure




Note






Note



startdb

166198 PUBLIC 03282008




Note



Note




Note




stopsap DB


Note





03282008 PUBLIC 167198


stopsap


Caution




Note




Procedure






Example

smdstart SMD 98

168198 PUBLIC 03282008


Note







Example

smdstop SMD 98

Note





Procedure




Example


03282008 PUBLIC 169198








Note


l EP Core (EPC)






n



n



n



170198 PUBLIC 03282008


n














03282008 PUBLIC 171198



Guides




l CAFAdmin

l CAFUIAdmin









172198 PUBLIC 03282008









More Information








03282008 PUBLIC 173198







l NWDI_ADM

l NWDI_DEV

l NWDI_CMSADM



l NWDIAdministrator

l NWDIDeveloper


l CBSAdministrator



l CBSDeveloper

l CMSDisplay

l CMSExportOwn




l NWDIDevelopers






174198 PUBLIC 03282008














Note





03282008 PUBLIC 175198











in SAP Note 883948




Note


Procedure




176198 PUBLIC 03282008








Caution



Caution




03282008 PUBLIC 177198












178198 PUBLIC 03282008


















03282008 PUBLIC 179198


Note







Procedure




End of BI Java





180198 PUBLIC 03282008




69 Troubleshooting



n






Procedure










03282008 PUBLIC 181198





Procedure














to bak




182198 PUBLIC 03282008


Note







Caution






Caution


Caution


03282008 PUBLIC 183198


Caution




Prerequisites



Procedure


Note



Note



Caution


184198 PUBLIC 03282008






Note


Procedure



runInstaller


runInstaller






03282008 PUBLIC 185198


b) Central instance

Note



Note






Note



Procedure





186198 PUBLIC 03282008




Example







Caution



Procedure







03282008 PUBLIC 187198


Caution


Recommendation




Example

rm -rf homec11adm









Note


Caution


188198 PUBLIC 03282008


Process

Caution






Note



j2eedbtype =

j2eedbhost =

j2eedbadminurl =

j2eescshost =

j2eescssystem =

j2eemsport =


exejlaunch =


rdispj2ee_start =

rdispj2ee_timeout =

rdispj2ee_libpath =


03282008 PUBLIC 189198




jstartupprotocol =

jstartupvmhome =


jstartuprelease =

j2eedbdriver =






Caution


Prerequisites



Procedure

Caution



sqlplus nolog



190198 PUBLIC 03282008









Caution


Prerequisites



Procedure


sqlplus nolog



SQLPLUSgt exit




03282008 PUBLIC 191198




runInstaller


runInstaller






Example






192198 PUBLIC 03282008


Example Description














03282008 PUBLIC 193198



T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom





194198 PUBLIC 03282008














03282008 PUBLIC 195198












196198 PUBLIC 03282008



03282008 PUBLIC 197198



Documents

SAP NetWeaver 7.0 SR3ABAP+JavaonAIX :Oracle... SAP Components SAPSolutionManager Release4.0 ConfigurationGuide‒SAPSolution Manager4.0asof PatchingofSAP NetWeaver7.0scenarios