sap netweaver 7.0 sr2 abap+java on solaris: oracle · 2019-11-12 · public installationguide sap...

PUBLIC

Installation Guide

SAP NetWeaver 7.0SR2 ABAP+Java onSolaris : OracleIncluding the following:

NetWeaver ABAP Application Server (AS ABAP)

NetWeaver Java Application Server (AS Java)

NetWeaver Business Intelligence Java Components (BI Java)

NetWeaver Development Infrastructure (DI)

NetWeaver EP Core (EPC)

NetWeaver Enterprise Portal (EP)

NetWeaver Mobile Infrastructure (MI)

NetWeaver Process Integration (PI)

Target Audience

n Technology consultants

n System administrators

Document version: 1.10 ‒ 08/31/2007

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

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

Version Date Description

1.00 4/12/2006 Initial Version

1.10 8/31/2007 Terminology Changes and Updates

2/176 PUBLIC 08/31/2007

http://service.sap.com/instguides



Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 71.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 81.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 111.3 Information Available on SAP Service Marketplace . . . . . . . . . . 121.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 172.1 Basic System Variants . . . . . . . . . . . . . . . . . . . . . 172.2 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . 202.3 Production Client Considerations . . . . . . . . . . . . . . . . 222.4 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 232.5 Multi-Language and Unicode Support . . . . . . . . . . . . . . . 302.6 Running Adobe Document Services on Non-Supported Platforms . . . . 312.7 High Availability: Planning the Switchover Cluster . . . . . . . . . . 32

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 353.1 High Availability: Switchover Preparations . . . . . . . . . . . . . 363.1.1 Preparing for Switchover . . . . . . . . . . . . . . . . . . . . 363.1.2 Setting Up File Systems . . . . . . . . . . . . . . . . . . . . 383.1.3 Configuring Network File System . . . . . . . . . . . . . . . . 393.2 Hardware and Software Requirements . . . . . . . . . . . . . . . 413.2.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 423.2.2 Requirements for Solaris . . . . . . . . . . . . . . . . . . . . 433.2.3 Requirements for a Central System . . . . . . . . . . . . . . . . 463.2.4 Requirements for a Distributed or a High Availability System . . . . . . 483.2.4.1 Requirements for the Central Services Instance . . . . . . . . . . . 483.2.4.2 Requirements for the Central Instance . . . . . . . . . . . . . . 493.2.4.3 Requirements for the Database Instance . . . . . . . . . . . . . . 493.2.5 Requirements for a Dialog Instance . . . . . . . . . . . . . . . . 513.2.6 Checking and Modifying Solaris Kernel Parameters and Resource Controls . 523.2.7 Setting up Swap Space for Solaris . . . . . . . . . . . . . . . . . 523.3 Creating Operating System Users . . . . . . . . . . . . . . . . 553.3.1 Network Information Service . . . . . . . . . . . . . . . . . . 553.3.2 Creating Operating System Users and Groups . . . . . . . . . . . . 553.3.3 Creating Operating System Users and Groups Manually . . . . . . . . 57

08/31/2007 PUBLIC 3/176

3.3.4 Creating Solaris Groups and Users (Optional) . . . . . . . . . . . . 583.4 Setting Up File Systems and Raw Devices . . . . . . . . . . . . . . 593.4.1 Setting Up File Systems . . . . . . . . . . . . . . . . . . . . 593.4.2 Oracle File Systems . . . . . . . . . . . . . . . . . . . . . . 653.4.3 Setting up File Systems and Raw Devices for Solaris . . . . . . . . . . 673.5 Exporting and Mounting the Global Transport Directory . . . . . . . . 683.6 Exporting and Mounting Directories via NFS for Solaris (Optional) . . . . 693.7 Installing the Front-End Software . . . . . . . . . . . . . . . . 703.8 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 713.9 Installing the Java Development Kit . . . . . . . . . . . . . . . . 713.10 Preparing and Mounting the Installation Media . . . . . . . . . . . 733.10.1 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 733.10.2 Downloading Installation DVDs from SAP Service Marketplace (Optional) . 753.10.3 Mounting a CD / DVD for Solaris . . . . . . . . . . . . . . . . 76

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 794.1 Performing a High-Availability Installation . . . . . . . . . . . . . 794.2 Prerequisites before Starting SAPinst . . . . . . . . . . . . . . . 814.2.1 Prerequisites before Starting SAPinst: All Instances . . . . . . . . . . 814.2.2 Prerequisites before Starting SAPinst: Distributed Instances . . . . . . . 834.2.3 Prerequisites Before Starting SAPinst: High Availability . . . . . . . . . 844.3 Installing an SAP System Using SAPinst . . . . . . . . . . . . . . 844.3.1 Running SAPinst on UNIX . . . . . . . . . . . . . . . . . . . 844.3.2 Installing the Java Add-In for an Existing ABAP System (Optional) . . . . 904.3.3 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 924.3.4 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 934.3.5 Performing a Remote Installation with SAPinst (Optional) . . . . . . . 954.3.6 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 964.3.7 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 984.4 Oracle Database Software Installation . . . . . . . . . . . . . . . 984.4.1 Updating SAP-Specific Files in the Oracle Staging Area . . . . . . . . . 994.4.2 Running the Oracle Universal Installer . . . . . . . . . . . . . . 994.4.3 Installing the Current Patch Set . . . . . . . . . . . . . . . . . 1014.4.4 Installing Required Interim Patches . . . . . . . . . . . . . . . . 101

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 1035.1 Logging On to the Application Server . . . . . . . . . . . . . . . 1055.2 Logging on to the Portal . . . . . . . . . . . . . . . . . . . . 1065.3 Logging on to the Development Infrastructure (DI) . . . . . . . . . . 1075.4 Installing the SAP License . . . . . . . . . . . . . . . . . . . 1085.5 Installing the SAP Online Documentation . . . . . . . . . . . . . 1095.6 Configuring Remote Connection to SAP Support . . . . . . . . . . 109

4/176 PUBLIC 08/31/2007

5.7 Performing Initial ABAP Configuration . . . . . . . . . . . . . . 1105.8 Performing Oracle-Specific Post-Installation Steps . . . . . . . . . . 1125.9 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 1125.10 Performing the Client Copy . . . . . . . . . . . . . . . . . . 1145.11 Performing a Full Installation Backup . . . . . . . . . . . . . . . 1155.12 Post-Installation Steps for Adobe Document Services . . . . . . . . . 1175.12.1 Assigning Roles to Users ADSUSER and ADS_AGENT . . . . . . . . . 1175.12.2 Checking the IIOP Service and the Startup Properties . . . . . . . . . 1185.12.3 Installation Check and Quick Tests for Adobe Document Services . . . . 1185.13 Configuring Access to Knowledge Warehouse Content from the SAP Internet

Knowledge Servlet . . . . . . . . . . . . . . . . . . . . . . 1195.14 Setting Environment Variable CPIC_MAX_CONV . . . . . . . . . . 1205.15 Post-Installation Steps for Usage Type Process Integration (PI) . . . . . . 1205.15.1 Performing PI-Specific Steps for SLD Configuration . . . . . . . . . . 1215.16 Post-Installation Steps for Application Sharing Server . . . . . . . . . 1215.17 High Availability: Post-Installation Steps . . . . . . . . . . . . . . 1225.17.1 Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . 1225.17.2 Taking Precautions for Transport . . . . . . . . . . . . . . . . 1235.18 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 1235.19 Running the Configuration Wizard . . . . . . . . . . . . . . . . 1275.20 Checking the SAP Java Documentation . . . . . . . . . . . . . . 1305.21 Accessing Configuration Documentation in the SAP Solution Manager . . 132

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 1356.1 Installation of Multiple Components in One Database (Optional) . . . . . 1356.2 Integration of LDAP Directory Services (Optional) . . . . . . . . . . 1376.3 Starting and Stopping the SAP System . . . . . . . . . . . . . . . 1406.3.1 Starting and Stopping the SAP System Using the SAP Management Console . 1406.3.2 Starting and Stopping the SAP System Using startsap stopsap Scripts . . . . 1446.4 Creating a User for LDAP Directory Access (Optional) . . . . . . . . . 1476.5 Configuring User Management to Use an LDAP Directory (Optional) . . . 1486.6 Usage Type-Specific Initial Technical Configuration . . . . . . . . . . 1486.6.1 Initial Technical Configuration for the Application Server Java (AS Java) . . 1496.6.1.1 Initial Technical Configuration for Adobe Document Services . . . . . . 1496.6.1.2 Initial Technical Configuration for Composite Application Framework Core

(CAF) . . . . . . . . . . . . . . . . . . . . . . . . . . 1506.6.1.3 Initial Technical Configuration for the System Landscape Directory (SLD) . 1516.6.2 Initial Technical Configuration for Development Infrastructure (DI) . . . 1516.6.3 Initial Technical Configuration for the Portal (Usage Types EPC and EP) . . 1536.6.4 Initial Technical Configuration for Process Integration (PI) . . . . . . . 1546.6.4.1 Importing the SAP Exchange Profile . . . . . . . . . . . . . . . 1546.6.4.2 Assigning SAP_ALL Rights to User PISUPER . . . . . . . . . . . . 155

08/31/2007 PUBLIC 5/176

6.6.4.3 Activating the ICF Services . . . . . . . . . . . . . . . . . . . 1566.6.4.4 Assigning Roles to Groups . . . . . . . . . . . . . . . . . . . 1566.6.5 Initial Technical Configuration for BI Java . . . . . . . . . . . . . 1576.6.5.1 Configuring BI Java Information Broadcasting . . . . . . . . . . . . 1576.6.5.2 Process Chains: Transporting Texts for the Alert Category . . . . . . . 1586.6.5.3 Renaming initialPermissionsBI.xml.template . . . . . . . . . . . . 1586.7 Heterogeneous SAP System Installation . . . . . . . . . . . . . . 1586.8 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 1596.8.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 1596.8.2 Troubleshooting for Portal Installation . . . . . . . . . . . . . . 1606.9 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 1616.9.1 Deleting an SAP System Using SAPinst . . . . . . . . . . . . . . . 1616.9.1.1 Running SAPinst to Delete an SAP System . . . . . . . . . . . . . 1626.9.1.2 Deleting the Oracle Database Software . . . . . . . . . . . . . . 1636.9.2 Deleting an SAP SystemManually . . . . . . . . . . . . . . . . 1646.9.2.1 Deleting an SAP Instance . . . . . . . . . . . . . . . . . . . 1656.9.2.2 Deleting Installation Files, Directories, and Users on a Host . . . . . . . 1656.9.2.3 Deleting the Java Part of an SAP System . . . . . . . . . . . . . . 1676.9.2.4 Deleting the Oracle Database Java Schema . . . . . . . . . . . . . 1686.9.2.5 Deleting an Oracle Database Instance . . . . . . . . . . . . . . . 169

6/176 PUBLIC 08/31/2007

1 Introduction

1 Introduction

This document explains how to install SAP NetWeaver 7.0 SR2 ABAP+Java.It also explains how to install the Java Add-In for an existing SAP NetWeaver 7.0 SR2 ABAP system.For more information about the SAP NetWeaver technology, see SAP Service Marketplace athttp://service.sap.com/netweaver.You can install SAP NetWeaver 7.0 SR2 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 following:l 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 ‒ <your product> Java on <OS> :<Database>.

End of: Enterprise Portal (EP)

n

Only valid for: BI Java Components (BI-Java)

SAP NetWeaver Business Intelligence Java Components (BI Java)

08/31/2007 PUBLIC 7/176

http://service.sap.com/netweaver



1 Introduction1.1 New Features

You also have to install SAP NetWeaver Application Server Java (AS Java), EP Core (EPC) andSAP NetWeaver Portal (EP).End of: BI Java Components (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)

Note

If you want to add additional usage types to an existing SAP system, follow SAP Note 883948.

For more information about the usage types of SAP NetWeaver and their interdependencies,see the document Master Guide ‒ SAP NetWeaver 7.0 on SAP Service Marketplace athttp://service.sap.com/instguidesNW70. For restrictions, see SAP Note 855534.

Constraints

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

n The database must be Oracle 10.2.0.2 or higher.n 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.

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

n For downward-compatible releases of DB/OS 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 releases.Note that for already shipped SAP components, we only support the installation for databaseversions proposed by the installation tool. Therefore, you must install a SAP component orperform a system copy using a downward-compatible database as follows:l Install the component with the old proposed database version.l Upgrade the old database version to the downward-compatible new version.

1.1 New Features

Here you can find the new features in this release.

8/176 PUBLIC 08/31/2007

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

http://service.sap.com/instguidesNW70





Caution

Make sure that you read the release notes for your SAP system. You can find these on SAP ServiceMarketplace at http://service.sap.som/releasenotes.

SAP System Installation

Area Description

SAPinst As of SAP NetWeaver 7.0, SAPinst has the following new features:n You can check the prerequisites for your SAP system installation with the

Prerequisite Checker [page 42].n You can install a central system in one of two modes:l 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 parameters.You 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 following:l Install the central services instance (SCS)l Add the Java database schema to the existing ABAP database instance.l Add the Java central instance with usage types to the existing ABAP central

instance.The installation of the Java Add-In for an existing ABAP system isdescribed in the documentation Installation Guide — <your product>ABAP+Java on <OS> : <Database> available on SAP Service Marketplace athttp://service.sap.com/instguides.

NoteYou cannot install the Java Add-In for the dialog instance(s) of the existingABAP system. Instead, you have to install new ABAP+Java dialog instance(s).

n The sapinst group ID must be the secondary group of the users root and<sapsid>adm. For more information, see Creating Operating System Users and GroupsManually [page 55].

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

SAPJSF during the input phase of the installation.n 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 phrase.n 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.

08/31/2007 PUBLIC 9/176

http://service.sap.som/releasenotes






Area Description

n You no longer have to manually activate sapcpe.The kernel is replicated automatically from/usr/sap/<SAPSID>/SYS/exe/run/DIR_CT_RUN to/usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for eachSAP system instance.For more information, see Setting Up File Systems [page 59].

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

Usage type EP Core(EPC)

As of SAP NetWeaver 7.0 SR2, usage type Enterprise Portal (EP) has been separatedinto two closely related usage types: EP Core (EPC) and Enterprise Portal (EP). Usagetype EPC provides the core portal capabilities available in the former usage type EP.Usage type EP now includes all portal add-on capabilities it provided before, butwithout the core portal functionality.n EP Core (EPC)

This usage type contains the core portal capabilities that were available in theformer usage type EP. This new usage type provides more flexibility whenimplementing a portal where the full enterprise portal capabilities, such asknowledge management and collaboration, are not needed. It contains theportal, Guided Procedures (GP), and Universal Worklist (UWL).

n Enterprise Portal (EP)This usage type includes Knowledge management, Collaboration, CompositeApplication Framework Core (CAF-Core), Visual Composer, Web Dynproextension, and .NET PDK.

For more information about EPC and about how to use it in IT scenarios, see theMaster Guide and SAP Note 982502.

SAP Solution ManagerKey

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

SAP NetWeaverAdministrator

SAP NetWeaver Administrator is a brand new solution for monitoring andadministering Java systems and their applications.For more information, see the SAP NetWeaver Master Guide and SAP ServiceMarketplace at http://service.sap.com/nwa.

Oracle Database

New functions inOracle Database 10g

n As of the installation of SAP NetWeaver 7.0 and SAP Business Suite 2005, newfunctions of the Oracle Database 10g release are used.For 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 Oracle,which you can find at:http://www.oracle.com/technology/products/database/oracle10g

10/176 PUBLIC 08/31/2007


http://service.sap.com/nwa

http://service.sap.com/nwa


http://www.oracle.com/technology/products/database/oracle10g

1 Introduction1.2 SAP Notes for the Installation

Operating Systems

Area Description

Support of OperatingSystems

See the Product Availability Matrix (PAM) on SAP Service Marketplace athttps://service.sap.com/pam

Documentation

Area Description

SAP Notes You can now access SAP Notes directly in SAP Service Marketplace from yourPDF. Place the cursor on the SAP Note “<number>” and double-click. Aseparate browser windows opens and the SAP Note is displayed.

Web Dispatcher Installation The installation of a Web Dispatcher is covered in a dedicated installationguide, available at http://service.sap.com/installNW70 Installation -Standalone Engines & Clients Installation Guide - Web Dispatcher on <platform>

Standalone GatewayInstallation

The installation of a standalone gateway is now covered in a dedicatedinstallation guide, available at http://service.sap.com/installNW70

Installation - Standalone Engines & Clients Installation Guide - Gateway on <platform>

Application Sharing ServerInstallation

The installation of Application Sharing Server is part of the Java installationguide for your product, available at http://service.sap.com/instguides

<choose your product>

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

table of contents at the beginning of the guide.n Click on an internet link such as http://service.sap.com to jump to

the corresponding internet page.

1.2 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 documentation.Make sure that you have the up-to-date version of each SAP Note which you can find in the SAPService Marketplace at https://service.sap.com/notes.

Note

You can directly access the SAP Notes that are related to the SAP NetWeaver installation athttps://service.sap.com/sapnotesNW70.

08/31/2007 PUBLIC 11/176

https://service.sap.com/pam

https://service.sap.com/pam

http://service.sap.com/installNW70






http://service.sap.com

https://service.sap.com/notes



https://service.sap.com/sapnotesNW70



1 Introduction1.3 Information Available on SAP Service Marketplace

SAP Notes for the Installation

SAP Note Number Title Description

972262 SAP NetWeaver 7.0 SR2 / BusinessSuite 2005 SR2 - UNIX

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

852008 Release Restrictions for SAPNetWeaver 7.0

Customer information on restrictionsconcerning the production use of certainfunctions.

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.

972263 SAP NetWeaver 7.0 SR2 / BusinessSuite 2005 SR2 - 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 iSeries:Checking OS Dependencies

937693 SAP Mobile Infrastructure 7.0 -Release Note to MAXDB

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

1.3 Information Available on SAP Service Marketplace

More information is available as follows on SAP Service Marketplace.

Documentation

Description Internet Address Title

Master Guide for SAPNetWeaver 7.0

http://service.sap.com/installNW70 Master Guide ‒ SAP NetWeaver 7.0(2004s)

Technical InfrastructureGuide for SAP NetWeaver7.0

http://service.sap.com/installNW70 Technical Infrastructure Guide ‒ SAPNetWeaver 7.0 (2004s)

12/176 PUBLIC 08/31/2007


















List of media forinstallation or upgradefor SAP NetWeaver 7.0

http://service.sap.com/installNW70 Media List ‒ SAP NetWeaver 7.0(2004s)

Installation of SAPSolution Manager


/solutionmanager Installation GuidesRelease <3.2 or 4.0>

Installation Guide ‒ SAP SolutionManager <release> on <OS>:<Database>

Configuration of SAPSolution Manager


/solutionmanager Installation GuidesRelease <3.2 or 4.0>

Configuration Guide ‒ SAP SolutionManager <release> <current stack>

Patching of SAPNetWeaver 7.0 scenarios

http://service.sap.com/maintenanceNW70 Support Package Stack Guide ‒ SAPNetWeaver 7.0 (2004s) SupportPackage Stack <current stack>

Maintenance Optimizer http://service.sap.com/solutionmanager

Functions in Detail Support Area MaintenanceOptimizer

All corrective software packages,including Support Packages(Stacks) for SAP NetWeaver 7.0(2004s) and subsequent versions,as well as all applications whichare based on this software(including SAP Business Suite2005), released after April 2,2007, will be available exclusivelythrough the MaintenanceOptimizer in SAP SolutionManager.

Upgrade to SAPNetWeaver 7.0

http://service.sap.com/upgrade70 Component Upgrade Guide ‒ SAPNetWeaver 7.0 (2004s) ApplicationServer ABAP

Installation of SAPNetWeaver DeveloperWorkplace

http://service.sap.com/installNW70 Installation Guide ‒ SAP NetWeaverDeveloper Workplace

Installation of SAPNetWeaver DeveloperStudio

http://service.sap.com/installNW70 Installation Guide ‒ SAP NetWeaverDeveloper Studio

Installation of the SystemLandscapeDirectory (SLD)


ConfigurationPost-Installation Guide ‒ SystemLandscape Directory of SAPNetWeaver 7.0 (2004s)

Installationof a standalonegateway


Installation - Standalone Engines & ClientsInstallation Guide ‒ Gateway on<platform> for SAP NetWeaver 7.0(2004s) SR2

Installation of WebDispatcher


Installation - Standalone Engines & ClientsInstallation Guide ‒ Web Dispatcheron <platform> for SAP NetWeaver7.0 (2004s) SR2

08/31/2007 PUBLIC 13/176




http://service.sap.com/solutionmanager








http://service.sap.com/maintenanceNW70





http://service.sap.com/upgrade70




















Front End installation http://service.sap.com/installNW70 Front End Installation Guide (this guideis also available on the PresentationDVD)

Homogeneous andheterogeneous systemcopy for SAP systems basedon NetWeaver 7.0

http://service.sap.com/installNW70 Homogeneous and Heterogeneous SystemCopy for SAP Systems based on SAPNetWeaver 7.0 (2004s)

SAP NetWeaver ProblemAnalysis Guide

http://help.sap.com/nw70 SAP NetWeaverLibrary SAP NetWeaver by Key Capability SolutionLife Cycle Management by Key Capability SAPNetWeaver Problem Analysis Guide (PAG)

SAP NetWeaver Problem AnalysisGuide (PAG)

General Quick Links

Description Internet Address

SAP Help Portal http://help.sap.com

SAP NetWeaver Library in SAPHelp Portal

http://help.sap.com/nw70

SAP Notes http://service.sap.com/notes

SAP Notes for SAP NetWeaver 7.0installation

http://service.sap.com/sapnotesnw70

Released platforms and operatingsystems

http://service.sap.com/platforms

Release notes http://service.sap.som/releasenotes

Unicode SAP systems and theiravailability

http://service.sap.com/unicode

System sizing (Quick Sizer tool) http://service.sap.com/sizing

High availability http://service.sap.com/ha

Security http://service.sap.com/security

Information on SAP SupportPackage Stacks

http://service.sap.com/sp-stacks

System Landscape Directory http://service.sap.com/sld

SAP Solution Manager http://service.sap.com/solutionmanager

Maintenance Optimizer http://service.sap.com/solman-mopz

14/176 PUBLIC 08/31/2007










http://help.sap.com



http://service.sap.com/notes

http://service.sap.com/notes








http://service.sap.com/sizing


http://service.sap.com/ha


http://service.sap.com/security

http://service.sap.com/security



http://service.sap.com/sld




http://service.sap.com/solman-mopz

http://service.sap.com/solman-mopz

1 Introduction1.4 Naming Conventions

1.4 Naming Conventions

Note

As of March 2007, SAP updated its release naming strategy to remove year designations. As a result,the product previously named SAP NetWeaver 2004s has been renamed to SAP NetWeaver 7.0. Beaware that this release may be referred to in several ways as SAP transitions to the new name. Thesenames may include: SAP NetWeaver 2004s, SAP NetWeaver 7.0 (2004s), or SAP NetWeaver 7.0.

In this documentation, the following naming conventions apply:

Terminology

n SAP system refers to SAP NetWeaver 7.0 SR3.n ABAP+Java system refers to SAP NetWeaver 7.0 SR3 ABAP+Java.n Java Add-In refers to the Java Add-In for an existing SAP NetWeaver 7.0 SR3 ABAP system.

Variables

Variables Description

<SAPSID> SAP system ID in uppercase letters

<sapsid> SAP system ID in lowercase letters

<DBSID> Database ID in uppercase letters

<dbsid> Database ID in lowercase letters

<host_name> Name of the corresponding host

<user_home> Home directory of the user performing the installation.

<INSTDIR> Installation directory for the SAP system

<DVD_DIR> Directory on which a DVD is mounted

<OS> Operating system name within a path

<SCHEMA_ID> Database schema ID

The following example shows how the variables are used:

Example

Log on as user <sapsid>adm and change to the directory /usr/sap/<SAPSID>.If your SAP system ID is C11, log on as user c11adm and change to the directory/usr/sap/C11.

08/31/2007 PUBLIC 15/176

This page is intentionally left blank.

2 Planning

2 Planning

This section tells you how to plan the installation of your SAP system.You have to complete the following planning activities:

1. You plan your SAP system landscape according to the Master Guide and the TechnicalInfrastructure Guide.

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 22].5. You identify basic SAP system parameters [page 23].

6.

Only valid for: SAP CRM 5.0;SAP SCM 5.0;SAP SRM Server 5.5

You decide whether you want to use Unicode and multi-language support [page 30].End of: SAP CRM 5.0;SAP SCM 5.0;SAP SRM Server 5.5

7. If you want to use Adobe Document Services (ADS), you check what you have to do in case your platform isnot supported for ADS [page 31].

8.

Only valid for: HA (UNIX)

You plan the switchover cluster [page 32] for a high-availability (HA) system.End of: HA (UNIX)

The following planning activity is optional:

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

Caution

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

2.1 Basic System Variants

The following section provides information about the basic system variants for an ABAP+Java systemand about the possibilities to distribute SAP instances within them.An 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.Mandatory instances of an ABAP+Java system are the central instance, the central services instance,and the database instance.

08/31/2007 PUBLIC 17/176

2 Planning2.1 Basic System Variants

Note

The Java central services instance is named SCS instance.The ABAP central services instance is named ASCS instance. The ASCS is only required for a highavailability installation.

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

Note

Each instance can reside on a separate host.

Figure 1: Minimum System Distribution (Central System)

For a minimum system distribution, all instances reside on one host.

18/176 PUBLIC 08/31/2007

2 Planning2.1 Basic System Variants

Figure 2: Maximum Distribution for a Distributed System

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


Figure 3: Maximum Distribution for a High-Availability System

End of: HA (UNIX)

08/31/2007 PUBLIC 19/176

2 Planning2.2 How to Distribute Instances to Hosts


For a maximum system distribution, each instance resides on a separate host.End of: HA (UNIX)

2.2 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 As a distributed system on several hostsThe following figure shows how to distribute your instances on several hosts:

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 steps:1. 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 will becreated during the installation of the primary application server instance (see below).

20/176 PUBLIC 08/31/2007

2 Planning2.2 How to Distribute Instances to Hosts

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 instance.7. On the central instance host, you mount the exported file systems from the SAP global host

and SAP transport host.8. On the central instance host, you run SAPinst and install the central instance.9. If required, you can now install one to <n> dialog instances. The procedure is the same as

installing a central instance (replace “central instance” with “dialog instance” in the procedure).

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:

08/31/2007 PUBLIC 21/176

2 Planning2.3 Production Client Considerations

Figure 5:

1. On the SAP global host, you run SAPinst and install the Java central services instance (SCS).2. On the database host, you run SAPinst and install the Java Add-In for the database instance.3. On the central instance host, you run SAPinst and install the Java Add-In for the central

instance.4. If required, you run SAPinst install one to <n> ABAP+Java dialog instances.

Caution

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

2.3 Production Client Considerations

A client is a self-contained unit in an SAP systemwith separate master records and its own set of tables.SAPinst creates three ABAP clients during the installation, client 000, client 001, and client 066.As of SAP NetWeaver 7.0 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 001.You 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 separately.n You install an ABAP+Java system and reconnect the Java part.n You install an ABAP+Java system and do not reconnect the Java part.

22/176 PUBLIC 08/31/2007

2 Planning2.4 Basic SAP System Parameters

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 ‒ <your SAP systemapplication> ABAP on <your OS>: <database>.

2. You perform the client copy [page 114].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 part.For more information about Java users, see the table User Management Engine (UME) in Basic SAP SystemParameters [page 23].

1. You install the ABAP+Java system as described in this documentation.2. You perform the client copy [page 114].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, you do not have to manuallyconfigure the connection of the Java part to the ABAP part.For more information about Java users, see the table User Management Engine (UME) in Basic SAP SystemParameters [page 23].

1. You install the ABAP+Java system as described in this documentation.2. You perform the client copy [page 114].

2.4 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 “Enter Your Values”, you write down the values that you plan to use, for example,theMessage Port Number.

08/31/2007 PUBLIC 23/176



SAP System ID and Database ID

Parameters Description Enter Your Values

SAP System ID<SAPSID>

The SAP System ID <SAPSID> 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 ID:n Is unique throughout your organizationn Consists of exactly three alphanumeric charactersn Contains only uppercase lettersn Has a letter for the first charactern Does not include any of the following, which are reserved

IDs:ADD ALL AND ANY ASC COM DBA END EPS FOR GID IBM

INT KEY LOG MON NIX NOT OFF OMS RAW ROW SAP SET

SGA SHG SID SQL SYS TMP UID USR VAR

...

Database ID <DBSID> The <DBSID> identifies the database instance.The database ID <DBSID> can be different from the SAPsystem ID.

...


Unicode or Non-Unicode System


Unicode System(recommended)

As default, this option is selected. We recommend you toinstall a Unicode system.If you choose to deselect this option, you should be awarethat you will not be able to install all usage types or softwareunits available.

NoteIf you want to install a Non-Unicode ABAP system, youhave to deselect this option.If you want to install a Unicode ABAP system, you mustleave this option selected.

For more information, seeMulti-Language and Unicode Support[page 30].

...

End of: SAP CRM 5.0;SAP SCM 5.0;SAP SRM Server 5.5

24/176 PUBLIC 08/31/2007


SAP System Instances, Hosts and Ports


Instance Number Instance Number:Technical identifier for internal processes, consisting of atwo-digit number from 00 to 97.The instance number must be unique on a host. That is, ifmore than one SAP instance is running on the same host, theseinstances must be assigned different numbers.To find out this number, look under the SAP directory/usr/sap/<SAPSID>/DVEBMGS<nn> on the host of the centralinstance.The value <nn> is the number assigned to the central instance.

...

Name of InstanceHost

Instance Host:Host name of the specific instance.To find out the host name, open a command prompt and enterhostname.For more information about the allowed host name length andcharacters, see SAP Note 611361.

...

Message Server PortCaution

Make sure that all message server port numbers on the samehost are unique.

Port number of the SAP Message Server:If you do not specify a value, the default port number is used.The message server port number must be unique for the SAPsystem on all hosts.ABAP Message Server PortThere is an external message server port using the parameterrdisp/msserv and an internal message server port using theparameter rdisp/msserv_internal.The ABAP message server uses both the internal and the externalmessage server ports. Both message server ports are configured inthe default profile.The external message server port uses the parameterrdisp/msserv with default value 36<nn>, where <nn> is theinstance number of the ABAP message server instance.The internal message server port uses the parameterrdisp/msserv_internal with default value 39<nn>, where <nn>is the instance number of the ABAP message server instance.Java Message Server PortThe Java message server only uses the internalmessage serverport. The Java message server is configured in the SCS instanceprofile.The parameter rdisp/msserv is set to 0, so that the external portis not open.The internal message server port uses the parameterrdisp/msserv_internal with default value 39<nn>, where <nn>is the instance number of the SCS message server instance.

...

08/31/2007 PUBLIC 25/176




For more information about the parameters used for internal andexternal message server ports, 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 14characters.Depending on your installation scenario there might be morerestrictions.

CautionIf you do not create the operating system users manually,SAPinst creates them with the common master password (see“Operating System Users”). In this case, make sure that themaster password meets the requirements of your operatingsystem and of your database.

...

Operating System User


System AdministratorUser

SAPinst creates the user <sapsid>adm.SAPinst assigns this user to the groups sapsys, oper, dba, sapinst.Make sure that the ID of this operating system user is unique andthe same on each application instance host.If you do not create operating system users manually before youstart the installation, SAPinst will create them automaticallyduring the installation.For more information, see Creating Operating System Users [page 55].

...

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.

CautionThis is only relevant for a Java Add-In installation.

...

26/176 PUBLIC 08/31/2007




Java AdministratorUser

This user is created by SAPinst in the ABAP system.After the installation, this user is available both in the ABAPand in the Java systemSAPinst sets the user name J2EE_ADMIN and the master passwordby default.If required, you can choose another user name and passwordaccording to your requirements.

...

Java Guest User This user is for employees who do not belong to a company orwho have registered as company users and are pending approval.Guest users belong to the default group Authenticated Users.This user is created by SAPinst in the ABAP system.After the installation, it is available both in the ABAP and inthe Java systemSAPinst sets the user name J2EE_GUEST and the master passwordby default.If required, you can choose another user name and passwordaccording to your requirements.

...

Communication User This user is created by SAPinst in the ABAP system.After 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 system.SAPinst sets the user name SAPJSF and the master password bydefault.If required, you can choose another user name and passwordaccording to your requirements.

...

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 Dispatcher.SAPinst sets the master password by default. If required, youcan choose another password.

...

Solution Manager Key


SAP Solution Managerkey

To install your SAP system, you need to generate a SAP SolutionManager key [page 71], which the installation requires to continue.For more information, see SAP Note 805390.

...

08/31/2007 PUBLIC 27/176



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 landscape.The usual case is to configure one SLD foryour complete system landscape.For more information, see Configuring SystemLandscape Directory [page 151].

...

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

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

...

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

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

...

28/176 PUBLIC 08/31/2007



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 the File System

Parameters Description Your Values

File system for the home directoryuser

/home/<username> ...

SAP systemmount directory /<sapmnt> is the base directory forthe SAP system.For /<sapmnt> you can use adirectory of your choice.Do not add <SAPSID> assubdirectory because the systemadds this directory automatically.

ExampleIf you enter /<sapmnt>, thesystem creates the directory/<sapmnt>/<SAPSID>.

...

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

...

Database schema,Passwords

The Java database schema is namedSAP<SCHEMA_ID>DB.Default name is SAPSR3DB.The ABAP database schema is named SAP<SCHEMA_ID>.Default name is SAPSR3.

...

DatabaseOSUser, Groups Oracle User ora<dbsid> , Oracle Group oper, dba

NoteThe user ora<dbsid> is only required on the host onwhich the database instance runs.

...

Database User Oracle User System ...

08/31/2007 PUBLIC 29/176

2 Planning2.5 Multi-Language and Unicode Support


Oracle Listener Name,Oracle 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 (in this case, see SAP Note 98252 formore information) or you have to specify an unusedListener Name and an unused Listener Port for the newlistener

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

...

Oracle Table Spaces See SAP Note 972263 ...


2.5 Multi-Language and Unicode Support

This section describes SAP support for multiple languages with or without Unicode:

n Unicode systemsl The default for all new installations is Unicode.

l Unicode (and the parallel ISO 10646 standard) defines the character set necessary for efficientlyprocessing text in any language and for maintaining text data integrity. In addition to globalcharacter coverage, the Unicode standard is unique among character set standards, because italso defines data and algorithms for efficient and consistent text processing. This enableshigh-level processing and ensures that all compliant software produces the same results.The widespread adoption of Unicode over the last decade has made text data truly portableand formed a cornerstone of the Internet.

l Unicode is the recommended system type for all SAP systems that deploy Unicode-enabledsolutions and components.

l Unicode is the only system type which is fully supported for:uSAP systems requiring a combination of languages that are based on more than one

non-Unicode code page

uSAP systems that deploy Java applications (for example Java applications, WebDynproapplications)

uSAP ABAP systems that communicate with Java components (for example via the SAPJava Connector)

30/176 PUBLIC 08/31/2007

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

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

2 Planning2.6 Running Adobe Document Services on Non-Supported Platforms

u


SAP systems with usage type Process Integration (PI)End of: Process Integration (PI)

Note

For information about restrictions in non-Unicode system installations refer to SAP Note838402.For information about code page support of SAP JAVA Connector refer to SAP Note 794411.

n Non-Unicode systemsSAP supports more than 30 languages in non-Unicode systems, but due to the technical limitationsof non-Unicode code pages, only certain combinations of languages can be used withoutrestrictions.

IntegrationThe default setup of the system is Unicode.

n If you want to use English only, you must activate the default language settings once.n If you want to use languages other than English, you must install them and activate the language

settings.

For more information on installing languages, see Performing Initial ABAP Configuration [page 110]Installing Languages .

More InformationFor more information, see SAP Notes 79991 and 73606.End of: SAP CRM 5.0;SAP SCM 5.0;SAP SRM Server 5.5

2.6 Running Adobe Document Services on Non-SupportedPlatforms

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

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

08/31/2007 PUBLIC 31/176






2 Planning2.7 High Availability: Planning the Switchover Cluster


2.7 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 “single points of failure”(SPOFs) ‒ across multiple host machines in the cluster. In the event of a failure on the primary node,proprietary switchover software automatically switches the failed software unit to another hardwarenode in the cluster. Manual intervention is not required. Applications accessing the failed softwareunit experience a short delay but can then resume processing as normal.Switchover 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 software.Without a switchover cluster, the SAP system SPOFs ‒ central services instance, the database instance,and the central file share ‒ are vulnerable to failure because they cannot be replicated. All of thesecan only exist once in a normal SAP system.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

SAP recommends switchover clusters to achieve 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 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).

32/176 PUBLIC 08/31/2007


PrerequisitesYou must first discuss switchover clusters with your hardware partner because this is a complextechnical area. In particular, you need to choose a proprietary switchover product that works withyour operating system.We recommend that you read the following documentation before you start:

n SAP High Availability at:http://service.sap.com/ha Media Library Documentation HA Documentation .

This covers HA for SAP systems based on SAP NetWeaver 7.0 and is part of the standard SAPdocumentation delivered with SAP NetWeaver 7.0.

n Technical Infrastructure Guide ‒ SAP NetWeaver 7.0 (2004s) at:http://service.sap.com/installNW70

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 system.For more information on how to install the standalone replicated enqueue server, see:http://help.sap.com SAP NetWeaver Library SAP NetWeaver by Key Capability Application

Platform by Key Capability ABAP Technology Client/Server Technology The SAP Lock Concept StandaloneEnqueue Server Installing the Standalone Enqueue Server

FeaturesThe following figure shows the essential features of a switchover setup:

Figure 6:

08/31/2007 PUBLIC 33/176







http://help.sap.com


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:

Figure 7:

ConstraintsThis documentation concentrates on the switchover solution for the central services instance.For more information on 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 partner.You 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 switchover.

More InformationFor more information on HA documentation, see:http://service.sap.com/ha

End of: HA (UNIX)

34/176 PUBLIC 08/31/2007




3 Preparation

3 Preparation

You have to complete the following preparations:

1.


You perform the switchover preparations [page 36] for a high-availability (HA) system.End of: HA (UNIX)

2. You check the hardware and software requirements [page 41].3. If required, you create operating system users manually [page 55].4. You set up file systems and raw devices [page 59].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 host,database instance host, and— if required— to the dialog instance host(s).

b) On the SAP global host, you export subdirectories exe, global, profile of /sapmnt/<SAPSID>to central instance host, database instance host, and— if required— to the dialog instancehost(s).

c) You mount subdirectories exe, global, profile of /sapmnt/<SAPSID> 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, see:n Exporting and Mounting the Global Transport Directory [page 68]n Exporting and Mounting Directories via NFS for Solaris [page 69]

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

Caution


7. You generate the SAP Solution Manager Key [page 71].

Caution


08/31/2007 PUBLIC 35/176

3 Preparation3.1 High Availability: Switchover Preparations

8. You install the Java Development Kit [page 71].9. You prepare and mount the installation media [page 73].


3.1 High Availability: Switchover Preparations


3.1.1 Preparing for Switchover

This section describes the extra preparations you need tomake for a high availability (HA) installation.For more information consult your HA partner.You 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 32].

Procedure

1. You check that your system meets the hardware and software requirements [page 41] for an HA setup,including the switchover software.

2. You set up file systems (that is, disk partitions), mount points, and (if required) NFS for your HAsystem on node A (before the installation of the SCS instance with SAPinst) and node B (after theinstallation of the SCS instance with SAPinst):

Caution


Recommendation

If possible, use journaled file systems (JFS), which allows much quicker recovery after a hostmachine crash. With JFS you can often reduce the switchover time because the hard diskmaintains data integrity in the event of a system crash or if the system is otherwise haltedabnormally.

a) You set up the required file systems [page 38] using mount points or NFS

36/176 PUBLIC 08/31/2007


b) If required, you configure NFS [page 39], making sure you are using the virtual host name for NFSto enable NFS switchover..

c) You assign the local file systems to mount points.d) 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 needs,consult 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.

Caution


08/31/2007 PUBLIC 37/176


Note

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

End of: HA (UNIX)


3.1.2 Setting Up File Systems

Caution


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.

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 [page 59].

Note

The file systems /sapmnt/<SID> and /usr/sap/trans are Network File Systems (NFS), whereas/usr/sap>SID> is a file system of the AS instance that is always mounted on the instance (notwith 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 operation,we recommend that you use a different approach for the /usr/sap/<SID> file system.The file system contains two subdirectories:n SYS contains links to the central directory /sapmnt/<SID>n <INSTTYPE><NR> (where the name is defined by the type of services and the application server

number, for example DVEBMSG00), which contains data for the local AS instance.Only the latter directory needs to be migrated with the AS instance during the switchover.As the SYS subdirectory contains only links that do not require any space, it can be createdlocally on each cluster node. Therefore, instead of /usr/sap/<SID>, create a file system/usr/sap/<SID>/<INSTTYPE><NR> with the usual <> substitutions. The file name for the CI isnormally DVEBMGS00. This avoids mount conflicts when switching over to a node on which an ASinstance is already running. The DVEBMGS00 directory can join the /usr/sap/<SID> tree insteadof mounting on top of it.

38/176 PUBLIC 08/31/2007


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 (in orderto use the resources efficiently). You must use this approach for integrated installations of the ASwith ABAP and Java stacks.

End of: HA (UNIX)


3.1.3 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 partner.We regard NFS as an extension to the operating system. The switchover product protects NFS andmakes it transparently available to the SAP system in switchover situations.You 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 system.These directories are:

n /sapmnt/<SID>/profile

Contains the different profiles to simplify maintenance

n /sapmnt/<SID>/global

Contains log files of batch jobs and central SysLog

n /usr/sap/trans

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.

n /sapmnt/<SID>/exe

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

08/31/2007 PUBLIC 39/176


The 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 DB.In 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 node.When exporting the directories with their original names, you might encounter the problem ofa “busy NFS mount” on the standby node. You can use the following workaround to solve thisproblem:a) On the primary server, mount the disks containing the directories:

/export/usr/sap/trans

/export/sapmnt/<SID>

b) The primary server creates soft links to the directories with the original SAP names:/usr/sap/trans —> /export/usr/sap/trans

/sapmnt/<SID> —> /export/sapmnt/<SID>

Alternatively the primary server can also mount the directories:/export/usr/sap/trans —> /usr/sap/trans

/export/sapmnt/SID —> /sapmnt/<SID>

c) The primary server exports:/export/usr/sap/trans


d) The standby NFS mounts:from virt.IP:/export/usr/sap/trans to /usr/sap/trans

from virt.IP:/export/sapmnt/<SID> to /sapmnt/<SID>

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

n These directories on the standby node become busy:/usr/sap/trans

/sapmnt/<SID>

n The standby node mounts disks to:/export/usr/sap/trans


n The standby node configures the virtual IP address virt.IPn The standby node exports:

/export/usr/sap/trans


n These directories on the standby node are accessible again:/usr/sap/trans

/sapmnt/<SID>

End of: HA (UNIX)

End of: HA (UNIX)

40/176 PUBLIC 08/31/2007

3 Preparation3.2 Hardware and Software Requirements

3.2 Hardware and Software Requirements

You check the hardware and software requirements for your operating system (OS) and the SAPinstances using the Prerequisite Checker tool. The Prerequisite Checker provides information aboutthe requirements that you need to meet before you start the installation. For example, it checks therequirements for the different installation services.

Note

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

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

You can run the Prerequisite Checker as follows:

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

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

We also recommend that you consult the requirements checklists tables, which provide values for theinstallation of development systems or quality assurance systems. Depending on the amount ofdata involved, the requirements might change. In addition, consider the following information:

n To get precise sizing values for production systems, you have to do one of the following:l You use the SAP Quick Sizer tool that is available on SAP Service Marketplace at

http://service.sap.com/sizing. You enter information about your planned system and thetool calculates the requirements.For more information, see Planning your System Landscape in theMaster Guide ‒ SAP NetWeaver 7.0,which is available on SAP Service Marketplace [page 12].

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

uThe set of applications to be deployed

uHow intensively the applications are to be used

uThe number of users

l


If you want to install usage type Development Infrastructure (DI), check SAP Note 737368for system requirements and sizing.End of: Development Infrastructure (DI)

n For supported operating system releases, see the Product Availability Matrix on SAP ServiceMarketplace at http://service.sap.com/pam.

n Contact your OS vendor for the latest OS patches.

08/31/2007 PUBLIC 41/176






http://service.sap.com/pam




n Make sure that the host name meets the requirements listed in SAP Note 611361.n Check your keyboard definitions.n 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. If required, you run the Prerequisite Checker standalone [page 42] to check the hardware and softwarerequirements.

Caution

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

2. In addition, we recommend that you check the hardware and software requirements for youroperating system and for the system variant that you want to install:n Solaris [page 43]n Central system [page 46]n Distributed or high availability system [page 48]

3. If youwant to install additional dialog instances, check the requirements for a dialog instance [page 51].

3.2.1 Running the Prerequisite Checker in Standalone Mode(Optional)

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

Recommendation

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

Note

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

Prerequisites

n You have installed the correct Java Development Kit (JDK) [page 71].n You have prepared the installation master DVD on the required installation host [page 73].n You make sure that therequired prerequisites are met before starting SAPinst [page 81].

42/176 PUBLIC 08/31/2007



Procedure

1. You start SAPinst [page 84].2. On theWelcome screen, choose <SAP System> Additional Software Lifecycle Tasks Additional Preparation

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

Note

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

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

4. To start the Prerequisite Checker, choose Start.

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

3.2.2 Requirements for Solaris

The host machine must meet the following requirements:

Note

The information here is not intended to replace the documentation of the Solaris operating system(OS). For more information, see the Solaris online documentation at http://docs.sun.com.

Requirements

RequirementType Requirement

Hardware n Tape driveWe recommed that you use a high‒capacity tape drive with hardware compression.You can test the drives with this command:/usr/bin/mt -f /dev/rmt/[0,1,2,..][n] status

This command displays drive type and whether a tape is loaded.Alternatively, you can use this command:/usr/bin/tar -cvf /dev/rmt/[0,1,2,..] \

[n] <testfile>

n Volume ManagerMount a CD or DVD with the following command:/bin/volcheck

Dismount and eject a CD or DVD with the following command:

08/31/2007 PUBLIC 43/176

http://docs.sun.com



/usr/bin/eject

Test whether the volume manager is running with the following command:/usr/bin/ps -ef |grep vold

Start the volume manager with the following command:/usr/sbin/vold &

n DisksEnter the following in your commands to specify a device name:dev/[r]dsk/c[0-99]t[0-99]d[0-99]s[0-7]

The parameters have the following meanings:rdsk for raw devicesc[0-99] specifies the number of the controllert[0-99] specifies the SCSI targetd[0-99] specifies the position in trays[0-7] specifies the number of the partition. s2 always specifies the full disk.Display the partitioning, for example, with the following command:/usr/sbin/prtvtoc <rawdevice>

Change the partitioning with this command:/usr/sbin/format

n RAMDisplay the available working memory with the following command:/usr/sbin/prtconf |grep Memory

n Swap Space3 to 4 * RAMFor information how to set up swap space, see Setting Up Swap Space for Solaris [page 52].

n CPUThe recommended minimum hardware is either two physical single core processorsor one physical dual core processor.Display the status and number of existing CPUs with the following command:/usr/sbin/psrinfo

Software n Operating systemCheck the operating system version with the following command:/bin/uname -r

n National Language Support (NLS)To display which locales are available, enter the following command:locale -a

The following files must be available: iso_8859_1, en_US.

n Lightweight Directory Access Protocol (LDAP)If you want to use LDAP, you required the following LDAP library:libldap.so

n PatchesTo check the installed patches, enter the following command:/bin/showrev -p

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

44/176 PUBLIC 08/31/2007



l Sun Solaris 9: SAP Note 550585l Sun Solaris 10: SAP Note 832871l Solaris 10 on x64: SAP Note 908334

n C++ runtime environmentThe Shared Library Patch for C++ must be installed.

n Solstice DiskSuiteCheck whether Solstice DiskSuite is installed with this command:/bin/pkginfo | /usr/bin/grep SUNWmd

For more information, see the documentation for Solstice DiskSuite.n Veritas Volume Manager

If you do not use Solstice DiskSuite, check whether Veritas Volume Manager isinstalled:/bin/pkginfo | /usr/bin/grep SUNWvx

For more information, see the documentation for Veritas Volume Manager.

Other n PrinterTo see the status of the spool for all printers in use, enter the following command:/bin/lpstat -t

To set up a printer enter this command:/bin/admintool

n NetworkingFor a list of all active network devices, enter the following commands:/usr/bin/netstat -I

/usr/sbin/ifconfig -a

To check routing information enter this command:/usr/bin/netstat -r

To check whether ISDN is installed enter this command:/bin/pkginfo |grep SUNWisdn

To check the status of the ISDN connection enter this command:/opt/SUNWconn/bin/isdnstat

To check whether Network File System (NFS) is running do the following:l Solaris 9u To check whether the NFS client is running, enter the following command:

/usr/bin/ps -ef |grep nfs

u If the processes statd and lockd are not running, start themwith the followingcommand:/etc/init.d/nfs.client start

u To check whether the NFS client is running, enter the following command:/usr/bin/ps -ef |grep nfs

u If the server is not running, start it with the following command:/etc/init.d/nfs.server start

l Solaris 10 and higheru To check whether the NFS client is running on Solaris, enter the following

command:svcs -H -o state svc:/network/nfs/client:default

08/31/2007 PUBLIC 45/176






u If the output is not “online”, start the NFS client service with the followingcommand (and configure it to start during each reboot):svcadm enable svc:/network/nfs/client:default

u To check whether the NFS server is running, enter the following command:svcs -H -o state svc:/network/nfs/server:default

u If the output is not “online”, start the NFS server service with the followingcommand (and configure it to start during each reboot):svcadm enable svc:/network/nfs/server:default

l Test the network connection to the database server with the following command:/usr/sbin/ping <DB-SERVER>

n C++ runtime environmentMake sure that the shared library patch for C++ is installed.

n Installation directoryIn a standard Solaris installation /tmp is a tmpfs file system.tmpfs is a memory-based file system that uses kernel resources relating to the VMsystem and page cache as a file system.Once mounted, a tmpfs file system provides standard file operations and semantics.tmpfs is so named because all files and directories are lost after reboot or unmounts.For this reason, we recommend that you create a directory /temp on a ufs file system.

3.2.3 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 requirements:The table below also lists themost relevant requirements for the Oracle database.You get the full list of hardware and software requirements from the relevant Oracle databaseinstallation guide for your operating system, which you can find athttp://www.oracle.com/technology/documentation

Note

You can access the complete Oracle documentation as a member of the Oracle Technology Network(OTN) at:http://www.oracle.com/documentation

For more information on joining OTN, see:http://www.oracle.com/technology

Recommendation

If you have access to Oracle Metalink we strongly recommend that you read document 169706.1.This document provides information on all operating system prerequisites and is regularly updated.

46/176 PUBLIC 08/31/2007

http://www.oracle.com/technology/documentation

http://www.oracle.com/documentation

http://www.oracle.com/technology


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 10.2 or higher.

RequirementType

Requirement

Hardware n DVD driven We recommend distribution of the Oracle database over three disks (RAID5) for

data security reasons.To decide howmany hard disks are required for your Oracle database, see the DatabaseSystem Configuration guide in SAP Database Guide: Oracle (BC-DB-ORA-DBA) in the SAPLibrary at https://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver byKey Capability Application Platform by Key Capability Platform-Wide Services DatabaseSupport Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA) Getting Started withOracle and the SAP System .

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

n Hard disk drives with sufficient space for swap: 3 to 4 * RAMn 4.3 GB of temporary disk space for every required installation DVD that you have

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

n 1.2 GB of temporary disk space for the installation.n RAM:

3 GB (minimum), 8 GB (recommended)Java Add-In (ABAP system already exists): 1.5 GB (minimum), 4 GB(recommended)


5.5 GB (minimum), 9 GB (recommended)End of: BI Java Components (BI-Java)


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


For more information, see SAP Note 927530.End of: BI Java Components (BI-Java)

Software n If application servers are installed decentralized, Network File System (NFS) must beinstalled.

n Make sure that the required fonts and code pages are installed.n Make sure that National Language Support (NLS) and corresponding saplocales are

installed.

08/31/2007 PUBLIC 47/176

https://help.sap.com/nw70




RequirementType

Requirement

n On the database host, a graphical user interface (GUI) is required for the Oracledatabase software installation with runInstaller.

n Check SAP Note 839182 whether you require an interim patch for the Oracle databaseinstallation. In this case, make sure you have the corresponding Perl version as statedin that SAP Note.

n Review the Oracle-recommended kernel parameters and shell limits for youroperating system with Oracle Database 10g Release 2 (10.2).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 accordingly.You can get the recommended shell limits and kernel parameters from the relevantOracle database installation guide for your operating system, which you can find at:http://www.oracle.com/technology/documentation

n If you want to install a Java Add-In for an upgraded ABAP system, make sure that theparameter compatible is set to 10.2.0 in the file ORACLE_HOME/dbs/init<dbsid>.ora.For more information, see Upgrade Guide ‒ SAP NetWeaver 7.0 Application Server ABAP onSAP Service Marketplace at http://service.sap.com/upgradeNW70.

3.2.4 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 differents hosts:

n Central services instance [page 48]n Central instance [page 49]n Database Instance [page 49]

Note

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

3.2.4.1 Requirements for the Central Services Instance

The central services instance host must meet the following requirements:

48/176 PUBLIC 08/31/2007



http://service.sap.com/upgradeNW70



Requirement Type Requirement

Hardware n DVD driven Hard disk drives with sufficient space for the central services instance

For more information, see Setting up File Systems [page 59].n Hard disk drives with sufficient space for swap: 3 to 4 * RAMn 4.3 GB of temporary disk space for every required installation DVD that you

have to copy to a local hard disk. For more information, see Preparing theInstallation DVDs [page 73].


0.5 GB (minimum), 1 GB (recommended)


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

Software n Network File System (NFS) must be installed.

3.2.4.2 Requirements for the Central Instance

The central instance host must meet the following requirements:

RequirementType

Requirement

Hardware n DVD driven Hard disk drives with sufficient space for the central instance.

For more information, see Setting Up File Systems [page 59] SAP File Systems .n Hard disk drives with sufficient space for swap: 3 to 4 * RAMn 4.3 GB of temporary disk space for every required installation DVD that you have

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


1.5 GB (minimum), 5 GB (recommended)Java Add-In (ABAP system already exists): 0.5 GB (minimum), 2 GB(recommended)

Software n If application servers are installed decentralized, Network File System (NFS) must beinstalled.

n Make sure that the required fonts and code pages are installed.n Make sure that National Language Support (NLS) and corresponding saplocales are

installed.

3.2.4.3 Requirements for the Database Instance

The database host must meet the following requirements:

08/31/2007 PUBLIC 49/176


The table below lists themost relevant requirements for the Oracle database instance host.You get the full list of hardware and software requirements from the relevant Oracle databaseinstallation guide for your operating system, which you can find athttp://www.oracle.com/technology/documentation

Note

You can access the complete Oracle documentation as a member of the Oracle Technology Network(OTN) at:http://www.oracle.com/documentation

For more information on joining OTN, see:http://www.oracle.com/technology

Recommendation

If you have access to Oracle Metalink we strongly recommend that you read document 169706.1.This document provides information on 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 10.2 or higher.


Hardware n DVD driven We recommend distribution over three disks (RAID5) for data security reasons.

To 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 http://help.sap.com/nw70 SAP NetWeaver LibrarySAP NetWeaver by Key Capability Application Platform by Key Capability Platform-WideServices Database Support Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA)Getting Started with Oracle and the SAP System .

n Hard disk drives with sufficient space for the database instance. For moreinformation, see Setting Up File Systems and Raw Devices ‒ Oracle File Systems [page 65].

n Hard disk drives with sufficient space for swap: 3 to 4 * RAMn 4.3 GB of temporary disk space for every required installation DVD you have

to copy to a local hard disk.n 1.2 GB of temporary disk space for the installation.n RAM:

1 GB (minimum), 3 GB (recommended)

50/176 PUBLIC 08/31/2007


http://www.oracle.com/documentation

http://www.oracle.com/technology





Java Add-In (ABAP system already exists): 500 MB (minimum), 2 GB(recommended)

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

n Make sure that the required fonts and code pages are installed.n Make sure that National Language Support (NLS) and corresponding saplocales

are installed.n On the database host, a graphical user interface (GUI), for example X11, is

required for the Oracle database software installation with runInstaller. Formore information, see the documentation of your operating system.

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

n Review the Oracle-recommended kernel parameters and shell limits for youroperating system with Oracle Database 10g Release 2 (10.2).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 accordingly.You can get the recommended shell limits and kernel parameters from therelevant Oracle database installation guide for your operating system, whichyou can find at:http://www.oracle.com/technology/documentation

n If you want to install a Java Add-In for an upgraded ABAP system,make sure that the parameter compatible is set to 10.2.0 in the fileORACLE_HOME/dbs/init<dbsid>.ora. For more information, see Upgrade Guide‒ SAP NetWeaver 7.0 Application Server ABAP on SAP Service Marketplace athttp://service.sap.com/upgradeNW70.

3.2.5 Requirements for a Dialog Instance

The dialog instance host must meet the following requirements:


Hardware n DVD driven Hard disk drives with sufficient space for the dialog instance.

For more information, see Setting up File Systems [page 59].n Hard disk drives with sufficient space for swap: 3 * RAM + 500 MBn 4.3 GB of temporary disk space for every required installation DVD that you

have to copy to a local hard disk. For more information, see Preparing theInstallation DVDs [page 73].


1 GB minimum, 3 GB recommended

Software n Make sure that the SAP kernel of the central instance has at least the patchlevel of the SAP kernel on the SAP Kernel DVD that is used for the installationof the dialog instance.

08/31/2007 PUBLIC 51/176







We recommend that you apply the most current SAP kernel from the SAPService Marketplace at http://service.sap.com/swdc.

n Network File System (NFS) must be installed.

3.2.6 Checking and Modifying Solaris Kernel Parameters andResource Controls

To run an SAP system, you must check and, if necessary, modify the Solaris kernel parameters orresource controls.

ProcedureFor more information about current Solaris kernel parameters and about how to modify them, seeSAP Note 395438 (Solaris 9) respectively SAP Note 724713 (Solaris 10).

3.2.7 Setting up Swap Space for Solaris

1. To check the size of the installed RAM, enter the following command:prtconf | grep "Memory"

2. To check the allocated swap space, enter the following command:swap -s

3. Check if there is sufficient swap space: 3 to 4 * RAM are recommended.4. If required, increase the swap space in one of the following ways:n Create a swap file, as described below in “Creating a Swap File”.n Use an entire disk or partition, as described below in “Using an Entire Disk or Partition”.

5. Check paging space size and kernel settings, as described below in “Check Paging Space Size andKernel Settings”.

Creating a Swap FileTo create additional swap space without reformatting a disk, first create a swap file using the mkfilecommand. mkfile creates a file that is suitable for use either as an NFS mounted or local area. Youcan specify the size in bytes (default), KB, blocks or MB using the k, b or m suffixes.

1. To make sure that you have enough free space on your system for the additional swap, enter thefollowing command:df -k

2. To create the swap file, enter the following command:mkfile <size>[ k | b | m ] <filename>

52/176 PUBLIC 08/31/2007

http://service.sap.com/swdc




Example

mkfile 500m /sap/newswap

3. When the swap file is created, you make it accessible using the swap command:swap -a <filename>

Example

swap -a /sap/newswap

4. To make the swap file available automatically each time the system boots, add an entry to the/etc/vfstab file.

Example

/sap/newswap - - swap - no -

Since the file systemmust be mounted before the swap file, make sure that the entry that mountsthe file system comes before the swap entry.

Using an Entire Disk or Partition

Note

Disk device namesThe disk naming convention is based on logical (not physical) device names. To specify a slice(partition) on a disk with a bus controller (SCSI), use a device name with these conventions:c<w>t<x>d<y>s<z>

Key:<w> logical controller number<x> physical bus target number (for example, SCSI-ID)<y> drive number<z> slice (partition) 0-7

To use an entire disk or partition:

1. Look for an unused partition or disk. Check that the partition is unused by looking at /etc/vfstaband /etc/opt/SUNWmd/md.tab or by using the vxprint tool.

2. To make your swap accessible, enter the following command:swap —a <blockdevice>

3. To make the swap partition available automatically each time the system boots, add an entry tothe /etc/vfstab file.

Example

<blockdevice> p - - swap - no

08/31/2007 PUBLIC 53/176


Setting up MetadevicesFor advanced disk management, use the Solstice DiskSuite package or the Veritas VolumeManagement Software. These provide performance (striping), high availability (mirroring, RAID 5)and maintenance (hotspares, growing file systems) using logical metadevices.

n Solstice DiskSuitel All information about the logical devices is kept in several replicas of a metadatabase. To access

a stripe, for example, use its nickname.l A <metadevice> is defined in the file /etc/opt/SUNWmd/md.tab with the format

/dev/md/dsk/d[0..n].l To access, for example, the raw partition of the metadevice d10, enter the following:

/dev/md/rdsk/d10

Caution

For striping and mirroring with Solstice DiskSuite equal physical partitions are required.

l To set up metadevices, proceed as follows:1. To check the metadatabase, enter the following command:

/usr/opt/SUNWmd/sbin/metadb

2. To define the metadevices, enter the following command:vi /etc/opt/SUNWmd/md.tab.

3. To initialize the metadevices, enter the following command:/usr/opt/SUNWmd/sbin/metainit -a

4. To check metadevices, enter the following command:/usr/opt/SUNWmd/sbin/metastat

5. Use raw metadevices:Instead of /dev/rdsk/<diskdevice> use /dev/md/rdsk/d[0..n].For more information, see the Solstice DiskSuite documentation.

n Veritas Volume Management Software:For more information, see the Veritas Volume Management Software documentation.

Check Paging Space Size and Kernel Settings

Note

If you are installing a standalone database server do not perform this step.

n Make sure that the UNIX kernel, paging space, and user limits are already configured for the SAPsystem as described in Requirements for Solaris [page 43].

n Execute memlimits to verify paging space size and kernel settings as follows:1. To unpack the file memlimits, enter the following commands:

a) cd <INSTDIR>

b) <DVD-DIR>/K0<x>/UNIX/<OS>/SAPCAR –xvfg \

54/176 PUBLIC 08/31/2007

3 Preparation3.3 Creating Operating System Users

c) <DVD-DIR>/K0<x>/UNIX/<OS>/SAPEXE.SAR memlimits

2. Start memlimits as follows:./memlimits -l 20000

If you see error messages, increase the paging space and rerun memlimits until there are nomore errors.

3.3 Creating Operating System Users

3.3.1 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 users,groups 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 55].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.SAPinst checks the NIS users, groups and services using NIS commands. However, SAPinst does notchange NIS configurations.

3.3.2 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 installation.If you want to use global accounts which are configured on a separate host, you start SAPinst andchoose Life Cycle Management Preparation Operating System Users and Groups . For more information,see Running SAPinst on UNIX [page 84].

08/31/2007 PUBLIC 55/176


Users and Groups

SAPinst checks whether the required users and groups already exist. If not, it creates new users andgroups as necessary.SAPinst 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 host.As 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 ora<dbsid> 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 ora<dbsid> user on the database server.Otherwise, 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 system.This 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, even if you do notintend to use the shells that these scripts are for.

Users and Their Primary Groups

User Primary Group

<sapsid>adm sapsys, oper, dba, sapinst

ora<dbsid> dba, oper, sapinst

Caution

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

Caution

If you install a distributed system and you do not use central user management (for example, NIS),and you use local operating system user accounts instead, user <sapsid>adm and the databaseoperating system usermust have the same password on all hosts.

Groups and Members

56/176 PUBLIC 08/31/2007


Groups Members

sapsys <sapsid>adm

oper <sapsid>adm, ora<dbsid>

dba <sapsid>adm, ora<dbsid>

sapinst <sapsid>adm, ora<dbsid>

The user ora<dbsid> is only required on the host on which the database instance runs.

More InformationCreating Solaris Groups and Users (Optional) [page 58]

3.3.3 Creating Operating System Users and Groups Manually

If you do not want SAPinst to create operating systems users, groups and services, you can optionallycreate them manually before the installation.

Users and Groups

SAPinst checks whether the required users and groups already exist. If not, it creates new users andgroups as necessary.SAPinst 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 host.As a general requirement, the user IDs and the group IDs must be the same on all hosts.

Caution

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

The following tables list the users and groups necessary for your database:

Users and Their Groups

User Primary Group Secondary Group(s)

<sapsid>adm sapsys

root sapsys sapinst

08/31/2007 PUBLIC 57/176


Groups and Members

Groups Members

sapsys n <sapsid>adm

n root

sapinst n <sapsid>adm

n root

3.3.4 Creating Solaris Groups and Users (Optional)

You can create groups and users manually by using the shell commands useradd and groupadd. Ifyou run a graphical user interface (GUI), you can use the admintool.

Caution

You cannot add the user root to the group dba using groupadd. You have to use the admintool forthis entry.

1. To add new groups and users, use the commands groupadd and useradd as follows:groupadd <new group>

useradd –g <login group> -d <homedirectory> \

-s <login shell> <new user>

2. Check the following values for the users:n In csh call limit

Output Properties Remarks

cputime unlimited

filesize unlimited

datasize 2097148 KB Important output property

stacksize 8192 KB

coredumpsize unlimited

descriptors 8192

memorysize unlimited Important output property

n In sh or ksh call ulimit -a


time(seconds) unlimited

file(blocks) unlimited

58/176 PUBLIC 08/31/2007

3 Preparation3.4 Setting Up File Systems and Raw Devices


data(kbytes) 2097148 Important output property

stack(kbytes) 8192

coredump(blocks) unlimited

nofiles(descriptors) 8192

memory(KBytes) unlimited Important output property

3. 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 follows:a) Add the following line to the .cshrc file after the line containing case Sun*:

limit descriptors 8192

b) Add the following line to the .profile file after the line containing Sun*) :ulimit -n 8192

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

3.4 Setting Up File Systems and Raw Devices

The following section(s) describe how to set up SAP file systems for the SAP instances and, if required,raw devices on operating system level:

n Setting Up File Systems [page 59]n Oracle File Systems [page 65]n Setting Up File Systems and Raw Devices for Solaris [page 67]

3.4.1 Setting Up File Systems

Depending on the installation option you have chosen, the following file systems listed in the figuresand tables below are required.SAPinst sets up most of these file systems automatically during installation. However, some filesystems you need to set up manually. For details see the following figures and tables.

08/31/2007 PUBLIC 59/176



Note

For more information on how to set up your file systems if you are performing an HA installation,see High Availability: Setting Up File Systems [page 38].

End of: HA (UNIX)

Caution

SAPinst uses sapcpe to replicate the kernel automaticallyfrom /usr/sap/<SAPSID>/SYS/exe/run/DIR_CT_RUN to/usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP system instance.The following entry in the start profile is responsible for this:Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF),where $(_PF) points to the instance profile.Do not delete DIR_CT_RUN from the instance profile in any case. Otherwise you will not be able torestart the system after patches have been applied.See also Applying the Latest Kernel and Support Packages [page 112].

Standard SAP File Systems for an ABAP + Java System

The ABAP part of an ABAP+Java system can be Unicode or Non-Unicode, whereas the Java part isalways Unicode.

60/176 PUBLIC 08/31/2007


Figure 9: SAP File Systems for an ABAP + Java System (Unicode)

Figure 10: SAP File Systems for an ABAP + Java System (ABAP Non-Unicode, Java Unicode)

08/31/2007 PUBLIC 61/176


The instance name (instance ID) of the ABAP+Java central instance is DVEBMGS<Instance_Number>,the instance name of an ABAP+Java dialog instance is D<Instance_Number>, and the instance nameof the Java central services instance is SCS<No>.


If you are performing an HA installation of your ABAP+Java system, there is also an ABAP centralservices instance called ASCS<Instance_Number>.End of: HA (UNIX)

Example

For example, the file system structure might look as follows:On a central instance with SAP system ID C11 and instance name DVEBMGS00, the J2EE Engineis installed to /usr/sap/C11/DVEBMGS00/j2ee, and the corresponding SDM is installed to/usr/sap/C11/DVEBMGS00/SDM.On a dialog instance with instance name D01, the J2EE Engine is installed to /usr/sap/C11/D01/j2ee.

SAP File Systems in Detail

Note

The listed file system sizes are initial SAP requirements.Depending on your operating system, you might also have to add space for administrative purposes.

The following file systems are global, that is, they are accessed by all hosts in the SAP system.

SAP File Systems

File System Name Description Space Required

<sapmnt>/<SAPSID> Software and data for one SAP systemThis directory is physically located on the SAPglobal host. In homogeneous systems, you needto mount it via NFS (Network File System) forall hosts belonging to the same SAP system. Itcontains the following subdirectories:n exe

Contains executable kernel programs

NoteSAP system ABAP (Non-Unicode) +Java only: exe contains a folder uc witha platform-specific subfolder: <sapmnt>/

n Central Instance:3.0 GBJava Add-In (ABAP systemalready exists): 1.5 GB

n Central Services Instance:1.0 GB

n Dialog instance:no file system required

62/176 PUBLIC 08/31/2007



<SAPSID>/exe/uc/<platform>

n global

Contains log filesn profile

Contains the start and operations profiles ofall instances

/usr/sap/<SAPSID> Instance-specific data, symbolic links to the datafor one systemThis directory contains files for the operation ofa local instance.There is a subdirectory <INSTANCE_NAME> foreach instance installed on the local instancehost, whereas data used by several instances arelocated in directory SYS.

NoteSAPinst creates the subfolder/usr/sap/<SAPSID>/<INSTANCE_NAME>/SDM onlyfor the central instance of ABAP+Java or Javasystems.For more information on SDM, see Checking theJava Documentation [page 130].

There are subdirectories of/usr/sap/<SAPSID>/SYS with symboliclinks to subdirectories of /<sapmnt>/<SAPSID>:n /usr/sap/<SAPSID>/SYS/profile is linked to

/<sapmnt>/<SAPSID>/profile

n /usr/sap/<SAPSID>/SYS/global is linked to/<sapmnt>/<SAPSID>/global

n /usr/sap/<SAPSID>/SYS/exe/run is linked to/usr/sap/<SAPSID>/SYS/exe/dbg which islinked to /<sapmnt>/<SAPSID>/exe

NoteSAP system ABAP (Non-Unicode) + Javaonly: /usr/sap/<SAPSID>/SYS/exe/run islinked to <sapmnt>/<SAPSID>/exe/uc

SAPinst sets up these directory structures duringthe installation.

n Central instancel AS ABAP:

2.0 GBl AS Java:

2.0 GBl For BI add 2.0 GB.l For EP add 2.0 GB.l For PI add 1.0 GB.l For MI add 0.5 GB.

n Dialog instance:See the space requirementsabove for the central instanceminus one third of the spacerequirements for Java softwareunits or usage types.

n Central Services Instance:1.0 GB

08/31/2007 PUBLIC 63/176



Executables locatedin/usr/sap/<SAPSID>/SYS/exe/run arereplicated by sapcpe to the exe directory ofinstances of the type <INSTANCE_NAME>, SCS<No>,ASCS<No>.

NoteSAP system ABAP (Non-Unicode)+ Java only: Executables for the exe

directory of instances of the typeSCS<No> are replicated by sapcpe from<sapmnt>/<SAPSID>/exe/uc/<platform>

NoteSince SAP traces for the instance are created indirectory /usr/sap/<SAPSID>/<INSTANCE_NAME>,you must make sure that sufficient space isavailable. Changes in SAP system profiles canalso affect the disk space.

/usr/sap/trans Global transport directory for all SAP systemsFor more information about exporting andmounting the global transport directory, seeExporting and Mounting the Global Transport Directory[page 68]The global transport directory is used by theChange and Transport System (CTS). The CTShelps you to organize development projects inthe ABAP Workbench and in Customizing, andthen transport the changes between the SAPSystems in your system landscape. For moreinformation, see:http://help.sap.com/nw70 SAP NetWeaver

Library SAP NetWeaver by Key Capability SolutionLife Cycle Management by Key Capability Software LifeCycle Management Software Logistics Change andTransport SystemIf you select the check box SAP System will be underNWDI control on the screen SAP System > NWDILandscape, SAPinst will copy all SCAs belonging tothe usage types / software units you install to theglobal transport directory.For more information, seehttp://help.sap.com/nw70 SAP NetWeaver

Library SAP NetWeaver by Key Capability SolutionLife Cycle Management by Key Capability SoftwareLife Cycle Management Software Logistics SAPNetWeaver Development Infrastructure Maintenance ofan NWDI-Driven System Landscape

n For the installation of allinstances: 500 MB

n For the use of all instances: 2 GB

64/176 PUBLIC 08/31/2007




Set up the file systems required for the database as described in Oracle File Systems [page 65].

3.4.2 Oracle File Systems

Note

Unicode systems require additional hardware resources. You can find more information aboutUnicode SAP systems on SAP Service Marketplace at http://service.sap.com/unicode.

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

Figure 11: Oracle File Systems

Oracle File Systems


/oracle Oracle base directory 50 MB for Oracle software

/oracle/client File system for Oracle client software.The directory /oracle/client/<102_32 or

102_64>/instantclient is created by SAPinstduring the installation.

100 MB

/oracle/stage/<102_32 or

102_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.

3.5 GB

08/31/2007 PUBLIC 65/176






/oracle/<DBSID> Home directory of user ora<dbsid>.We recommend that /oracle/<DBSID> doesnot reside in the root directory. It mustreside in a file system with support for largefiles.For more information about how to createfile systems larger than 2 GB on youroperating system, seeSetting Up File Systems and Raw Devices for Solaris[page 67].Therefore, either create /oracle/<DBSID>as a separate file system with support forlarge files or create /oracle as file systemwith support for large files and create/oracle/<DBSID> as a directory in /oracle.

100 MB for files of userora<dbsid> (for example,log files)

/oracle/<DBSID>/<102_32 or

102_64>

Home directory for Oracle instance <DBSID>(<ORACLE_HOME>).<ORACLE_HOME>must reside on a local disk. Itcannot be a softlink.

n Database instance : 4.0GB

n All other instances:200 MBMake sure that this filesystemhas permissions777.

/oracle/<DBSID>/origlogA Original set A of redo logs 200 MB

/oracle/<DBSID>/origlogB Original set B of redo logs 200 MB

/oracle/<DBSID>/mirrlogA Mirrored set A of redo logs 200 MB

/oracle/<DBSID>/mirrlogB Mirrored set B of redo logs 200 MB

/oracle/<DBSID>/oraarch New standard backup file system for Oracleoffline redo logs. Use a separate disk for thefile system /oracle/<DBSID>/oraarch.The file system /oracle/<SAPSID>/ saparch

still remains but now only contains brbackuplog files. /oracle/<SAPSID>/ saparch isautomatically created by SAPinst.

For the installation,the archive directory/oracle/<DBSID>/oraarch

requires at least 400 MBof free disk space. For theoperation of your SAPsystem, we recommendthat the archive directoryprovides enough spacefor archives between twobackups. In a productionsystem, between 300 MBand 1GB data is archiveddaily.

/oracle/<DBSID>/sapreorg Working directory for databaseadministration

1.5 GB

66/176 PUBLIC 08/31/2007



/oracle/<DBSID>/sapdata1 SAP data




For space requirementsof the SAP data filesystems required forthe installation, see thefollowing file:<Export_DVD>/EXP1/

DB/ORA/DBSIZE.XML.See also SAP Note972263 Pre-InstallationFile requirements of Oraclesapdata file systems

3.4.3 Setting up File Systems and Raw Devices for Solaris

Creating File Systems on Hard Disk Partitions

Note

To set up file systems larger than 2 GB, no special steps are required on Solaris.

1. Look for already configured and mounted file systems using the command:df -k

2. Look for the physical available disks and partitions using the format or/usr/sbin/prtvtoc <rawdevice> utility.

3. Verify that the partition is unused.4. Create new file systems using the command newfs:n Oracle (sapdata file systems):

newfs -i 20000 -m 1 -b 8192 -f 8192 <rawdevice>

n Standard SAP file systems:newfs <rawdevice>

Example

newfs /dev/rdsk/<diskdevice>

The disk naming convention is based on logical (not physical) device names. To specify aslice (partition) on a disk with a bus controller (SCSI), use a device name <diskdevice> withthese conventions: c<w>t<x>d<y>s<z>Key:<w> logical controller number<x> physical bus target number (for example, SCSI-ID)<y> drive number<z> slice (partition) 0-7

08/31/2007 PUBLIC 67/176


3 Preparation3.5 Exporting and Mounting the Global Transport Directory

Mounting File SystemsCreate directories (mkdir) and mount the file systems using the command:mount <blockdevice> <mountdir>

To make the file systems available automatically each time the system boots, add an entry to the/etc/vfstab file:

n If you do not use Solstice DiskSuite, add the following entry:/dev/dsk/<diskdevice> /dev/rdsk/>diskdevice> \

<mountdir> ufs <fsck pass#> yes —

where <fsck pass#> is a number greater than 6n If you use Solstice DiskSuite, add the following entry:

/dev/md/dsk/<metadevice> /dev/md/rdsk/<metadevice> \

<mountdir> ufs — no —

Accessing Raw Devices on SolarisFile systems and raw devices differ in the way that data is written to and read from disk:

n Buffering: Reads and writes to a file system are buffered in a UNIX system. To be absolutely surethat all data is physically present on a disk, the buffers and files must be synchronized.Unbuffered: Writes to a raw device are sent directly to the disk, which is faster and more secure.

n File access: Accessing files on a UNIX file system is transparent. Accessing data on a raw device isonly possible with a special application.

Some databases prefer raw devices.For Oracle it is not necessary to create symbolic links to access these raw devices. This also applies ifyou use Solstice DiskSuite or Veritas Volume Manager.

3.5 Exporting and Mounting the Global Transport Directory

Caution


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

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 follows:l Create the transport directory (either on the central instance host or on a file server).l Export it on the global transport directory host.l If you did not create the transport directory on your SAP instance installation host, mount it

there.

68/176 PUBLIC 08/31/2007

3 Preparation3.6 Exporting and Mounting Directories via NFS for Solaris (Optional)

Exporting the Transport Directory

1. Log on as user root to the host where the global transport directory /usr/sap/trans resides.2. Make sure that /usr/sap/trans belongs to the group sapsys and to the user root .3. If not already done, export the directory using Network File System (NFS) .

Mounting the Transport Directory

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 /usr/sap/trans is to be mounted.2. Create the mount point /usr/sap/trans.3. Mount /usr/sap/trans using Network File System (NFS) from the exporting host.

More InformationMounting Directories via NFS for Solaris [page 69]

3.6 Exporting and Mounting Directories via NFS for Solaris(Optional)

To mount directories via NFS from the host where the directory resides that you want mount, log onas user root and proceed as follows:

On the host on which the directory to be mounted resides:

1. Enter the command:/usr/sbin/share

2. To add file systems shared via NFS, edit file/etc/dfs/dfstab:vi /etc/dfs/dfstab

Add the following line for each file system:share -F nfs -o root=<nfsclient1>:<nfsclient2>,anon=0 \

-d "description" <file_system_to_be_shared>

Note

Depending on your configuration, a full qualified name may be required for nfsclient, forexample, myclient.mydomain.com.

08/31/2007 PUBLIC 69/176

3 Preparation3.7 Installing the Front-End Software

Caution

After your SAP system has been installed successfully, in the above line you have to change -oroot to -o rw (or remove anon=0, respectively) for all exported directories:share -F nfs -o rw=<nfsclient1>:<nfsclient2> \

-d "description" <file_system_to_be_shared>

3. If the/etc/dfs/dfstab was empty, the NFS server is not active.n On Solaris 9, start the NFS server with the following command:

/etc/init.d/nfs.server start

n On Solaris 10, start the NFS server with the following command:svcadm enable svc:/network/nfs/server:default

4. To see if the NFS server is active and which partitions are mountable, enter the command:showmount -e <NFS-server>

On the host on which the additional instance runs:

1. If you are mounting NFS disks for the first time, the NFS client software is not active.n On Solaris 9, start the NFS client software with the following command:

/etc/init.d/nfs.client start

n On Solaris 10, start the NFS client software with the following command:svcadm enable svc:/network/nfs/client:default

2. Edit the file /etc/vfstab to mount the directory:vi /etc/vfstab

Add the following line for each file system:<host_name_where_directory_resides>:<file_system_to_be_shared> \

- <mount point> nfs - yes -

If the mount point exists, mount <file_system_to_be_shared> with the command:mount <mount point>

3.7 Installing the Front-End Software

Caution


For the installation, make sure that the front-end software is installed on at least one computer inyour system environment.With 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 requirements,distribute patches, and set up automatic update processes for your clients.We recommend that you install SAP Front-end Release 7.10.

70/176 PUBLIC 08/31/2007

3 Preparation3.8 Generating the SAP Solution Manager Key

For more information on installing the front-end software, see the documentation SAP Front EndInstallation Guide - Release 7.10 on SAP ServiceMarketplace at http://service.sap.com/installNW70

Installation Installation - Clients .

3.8 Generating the SAP Solution Manager Key

Caution


You need to generate the Solution Manager key because SAPinst prompts for it during the inputphase of the installation. Without this key, the installation process cannot continue.You can generate all needed keys for your entire system landscape on one SAP Solution Managersystem. For more information, see SAP Note 805390.

PrerequisitesYou require SAP Solution Manager 3.2 SP 08 or higher.

Procedure

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

Manager <release> on <OS> : <Database> on SAP Service Marketplace at:http://service.sap.com/solutionmanager SAP Solution Manager Installation Guides Release

<3.2 or 4.0>2. Generate the SAP Solution Manager key as described in SAP Note 811923.

ResultThe system displays the key, which you need to enter during the input phase of the installation.

3.9 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 7.0 you must install the J2EE Engine with strong encryption.The J2EE Engine requires a Java Development Kit (Java™ 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.The JDK includes the Java Runtime Environment (JRE), which is required both for SAPinst andthe SAPinst GUI.

08/31/2007 PUBLIC 71/176










3 Preparation3.9 Installing the Java Development Kit

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 host.If you want to perform a remote installation, see Performing a Remote Installation with SAPinst [page 95]. 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 http://service.sap.com/pam.b) On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 7.0 (2004S) .c) Choose tab strip JSE Platforms.

Note

For additional information on 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 follows:n If the JDK is not already installed, you need to download and install it.n If the JDK is already installed

Check the installed version of the JDK by entering the following command:java -version

Note

SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment.If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME.

3. As of SAP NetWeaver 7.0 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 SAPinst:a) Download the JCE policy files for your platform at http://java.sun.com/products/jce/.b) SAPinst installs the JCE policy files during the installation process.

72/176 PUBLIC 08/31/2007





http://java.sun.com/products/jce/

3 Preparation3.10 Preparing and Mounting the Installation Media

3.10 Preparing and Mounting the Installation Media

3.10.1 Preparing the Installation DVDs

You use this procedure to prepare the installation DVDs. Normally you obtain the installation DVDsas part of the installation package that you receive from SAP. However, you can also download theinstallation DVDs from SAP Service Marketplace [page 75].

Recommendation

We recommend that you make all required DVDs available in parallel.

Note

If you copy the installation DVDs to disk, make sure that the paths to the location of the copiedDVDs do not contain any blanks.

Procedure

1. Identify the required DVDs for your installation as listed below and keep them separate from theremaining DVDs. This helps you to avoid mixing up DVDs during the installation.

Caution

The media names listed below are abbreviated.You can find the full names of all media shipped with SAP NetWeaver 7.0 SR3 inthe appropriate Media List for SAP NetWeaver 7.0 SR3 on SAP Service Marketplace athttp://service.sap.com/installNW70 Installation .

Note

If you are installing on an existing system using Multiple Components in One Database (MCOD),the required DVDs will 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.

08/31/2007 PUBLIC 73/176






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

End of: BI Java Components (BI-Java)

SAP Instance Installation Required DVDs

Central services instance, central instance,dialog instance

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

Oracle database instance (non-MCOD) n Installation Master DVDn Kernel DVDn SAP NetWeaver Java DVDn RDBMS DVDn RDBMS Client DVDn RDBMS patch DVDn Export DVD

Oracle database instance (MCOD) n Installation Master DVDn SAP NetWeaver Java DVDn 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 instance,dialog instance

n Installation Master DVDn SAP NetWeaver Java DVDn Kernel DVD

Oracle database schema (non-MCOD) n Installation Master DVDn NetWeaver Java DVDn Kernel DVDn RDBMS patch DVDn Export DVD

Oracle database schema (MCOD) n Installation Master DVDn SAP NetWeaver Java DVDn Kernel DVDn Export DVD

2. Use one of the following methods to make DVDs available in parallel:

74/176 PUBLIC 08/31/2007


n Before the installation:l Have sufficient DVD drives

l Copy DVDs manually to local hard disks

Caution

If you perform a local installation and there is only one DVD drive available on yourinstallation host, youmust copy at least the InstallationMaster DVD to the local file system.

n During the installation:Use the SAPinstMedia Browser screen. You can check the entered location in the Package Locationcolumn and then copy the entire DVD to the path you entered in the Copy Package To column.

3.10.2 Downloading Installation DVDs from SAP ServiceMarketplace (Optional)

You normally obtain the installation DVDs as part of the installation package from SAP.However, you can also download installation DVDs from SAP Service Marketplace at:https://service.sap.com/swdc Downloads Installations and Upgrades Entry by Application Group

<your solution> <release of your solution> <your operating system> <your database> .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 https://service.sap.com/swdc. 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.2. Identify all download objects that belong to one installation DVD according to one or both of the

following:n Material number

All download objects that are part of an installation DVD have the same material number andan individual sequence number:<material_number>_<sequence_number>

08/31/2007 PUBLIC 75/176

https://service.sap.com/swdc








Example

51031387_151031387_2...

n TitleAll objects that are part of an installation DVD have the same title, such as<solution><DVD_name><OS> or <database>RDBMS<OS> for RDBMS DVDs.

3. Download the objects to the download directory.4. Extract the individual download objects using SAPCAR, starting with the lowest sequence number

‒ for example 51031387_1, then 51031387_2, and so on.During the download SAPCAR sets up the structure of the installation DVD.

Note

SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always acceptwith Yes.

3.10.3 Mounting a CD / DVD for Solaris

In the Solaris operating system, a layer of software manages CDs / DVDs and other media. This is thevolume manager, which automates the interaction between you and your CDs / DVDs. Do not usethis volume manager to mount CDs / DVDs needed for the installation, as the manager does not usethe normal case option. Without this option, some files on CDs / DVDs cannot be found. Mount CDs/ DVDs for the installation manually as described in the following procedure.For more information about configuring the volume management, see the SunOS Routine SystemAdministration Guide.

Note

The placeholder <medium-mountdir> is used for either <cd-mountdir> or <dvd-mountdir>.

Procedure

1. Log on as user root.2. To check if vold (volume daemon) is running, enter the following command:

ps -ef | grep vold

3. If it is running, kill vold .4. Insert the CD / DVD into your disk drive.5. To create a mount point, enter the following command:

mkdir /<medium-mountdir>

76/176 PUBLIC 08/31/2007


Example

for example, <medium-mountdir> is /sapcd

6. To mount the CD / DVD, enter the following command:mount -F hsfs -o nomaplcase,ro /dev/dsk/c0t6d0s2 /<medium-mountdir>

After the installation, you can start vold using the following command:/usr/sbin/vold.

08/31/2007 PUBLIC 77/176

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

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

Note

This note does not apply to the installation of a Java Add-In to an existing ABAP system:Do not install the Oracle database software before you run SAPinst.SAPinst stops and prompts you to install the Oracle database [page 98] while the installation of thedatabase instance is running.If you install a system into an existing database (MCOD), this action is not required.


4.1 Performing a High-Availability Installation

This section describes how to perform a high-availability (HA) installation. For more information,consult your HA partner.

Prerequisites

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

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

08/31/2007 PUBLIC 79/176

4 Installation4.1 Performing a High-Availability Installation

Caution

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

virtual host name under which the central services instance is to run.l When you install the database instance, SAPINST_USE_HOSTNAMEmust point to the virtual

host name under which the database is installed.l 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 84] 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 36].

3. Set up the user environment on the standby node, host B.For more information, see Creating Operating System Users and Groups Manually [page 55]. 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 correctly.5. Install the database instance on the primary node, host A.6. Install the central instance with SAPinst [page 84] 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 servicesinstances (SCS and ASCS), which are protected by the cluster.

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

Note

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

End of: HA (UNIX)

80/176 PUBLIC 08/31/2007

4 Installation4.2 Prerequisites before Starting SAPinst

4.2 Prerequisites before Starting SAPinst

4.2.1 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 23] before you start the installation.

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

Procedure

1. If you want to install a dialog instance for an upgraded SAP system:a) Edit DEFAULT.PFL.b) Insert a line with the parameter rdisp/msserv_internal and set it to a free port number.c) Edit the instance profile of the central services instance.d) Set the parameter rdisp/msserv to 0.e) Insert a line with the parameter rdisp/msserv_internal and set it to the port number that was

assigned before to rdisp/msserv.f) Restart all instances of the SAP system.

Example

This shows the required change to the instance profiles:

n DEFAULT.PFL

Before the change:...rdisp/msserv = sapms<SAPSID>

...After the change:...rdisp/msserv = sapms<SAPSID>

rdisp/msserv_internal = <free port number>

...n Instance profile of the central services instance:

Before the change:...rdisp/msserv = 4711

08/31/2007 PUBLIC 81/176


...After the change:...rdisp/msserv = 0

rdisp/msserv_internal = 4711

...

2. Make sure that your operating system does not delete the contents of the temporary directory/tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, 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 uses/tmp as default installation directory.Make sure that the temporary directory has the permissions 777.The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. Theseexecutables are deleted again after SAPinst has stopped running.If required, you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C .

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 TEMP,TMP, or TMPDIR to another directory with 200 MB free space for the SAPinst executables.

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

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

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

Shell Used Command

Bourne shell (sh) DISPLAY=<host_name>:0.0

export DISPLAY

82/176 PUBLIC 08/31/2007


Shell Used Command

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

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

4.2.2 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 <sapmnt>/<SAPSID>/exe 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 158].

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 instance:<sapmnt>/<SAPSID>/exe

<sapmnt>/<SAPSID>/profile

<sapmnt>/<SAPSID>/global

For more information, seeMounting Directories via NFS for Solaris [page 69].

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 [page68]. Otherwise, the installation fails.

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

<sapmnt>/<SAPSID>/exe

<sapmnt>/<SAPSID>/profile

<sapmnt>/<SAPSID>/global

08/31/2007 PUBLIC 83/176

4 Installation4.3 Installing an SAP System Using SAPinst


4.2.3 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 SAPinst.If you do not set this environment variable now, you can specify an equivalent parameter for thevirtual host name when you run SAPinst [page 84].

ProcedureSet SAPINST_USE_HOSTNAME to the virtual host name of the machine on which you are installingan SAP instance.End of: HA (UNIX)

4.3 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 84]n Installing a Java Add-In for an Existing ABAP System with SAPinst [page 90]n Using SAPinst GUI [page 92]n Interrupted Installation with SAPinst [page 93]n Performing a Remote Installation with SAPinst (Optional) [page 95]n Starting SAPinst GUI Separately (Optional) [page 96].n Entries in the Services File Created by SAPinst [page 98]

4.3.1 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 Java.This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are runningon the same host. If required, you can instead perform a remote installation with SAPinst [page 95], whereSAPinst GUI is running on a separate host from SAPinst and the GUI server.When 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.

84/176 PUBLIC 08/31/2007


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 fail.For more information about mounting DVDs, seeMounting a CD / DVD for Solaris [page 76].

3. Start SAPinst from the Installation Master DVD in one of the following ways:n Using the default installation directory (recommended)

Enter the following commands:cd <Installation Master_DVD>/IM_<OS>

./sapinst


Note

If you are installing a high-availability system and you have not already set the environment parameterSAPINST_USE_HOSTNAME [page 84] to specify the virtual host name, you can start SAPinstas follows:./sapinst SAPINST_USE_HOSTNAME=<virtual host name>

End of: HA (UNIX)

Caution

Make sure that your operating system does not delete the contents of the temporary directory/tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, forexample by using a crontab entry.

Caution

Make sure that your current working directory is not an IM_<OS> directory belonging toanother operating system.For example, the following commands are incorrect and cause an error:$ cd /sapcd2/IM_HPUX_IA64

$ /sapcd2/IM_HPUX_PARISC/sapinst

The following commands are correct:$ cd /sapcd2/IM_HPUX_PARISC

08/31/2007 PUBLIC 85/176


$ /sapcd2/IM_HPUX_PARISC/sapinstn Using an alternative installation directory

If you want to use an alternative installation directory, set the environment variable TEMP,TMP, or TMPDIR.For more information, see Prerequisites before Starting SAPinst: All Instances [page 81].

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 service.In this case, you must execute sapinst using the following parameters:SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>.n To get a list of all available SAPinst properties, start SAPinst as described above with the option

-p:./sapinst -p.

4. In theWelcome screen, choose one of the following installation services:n SAP Systemsn Additional Software Life-Cycle TasksThe following tables provide more information about these installation services:n SAP Systems

You use this service to install a SAP system with usage types or software units by choosing<SAP system> SAP Systems <Database> <System Variant> Based on <technical stack> .

You can install the following system variants:l Central Systeml Distributed System

l


High Availability SystemEnd of: HA (UNIX)

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

86/176 PUBLIC 08/31/2007


Note

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

l You have to run the installation service Operating System Users and Groups before you startthe installation(see table Additional Software Life-Cycle Tasks below).

l If required, install a dialog instance for a central or distributed system by choosing theinstallation service <SAP System> Additional Software Life-Cycle Tasks Application ServerDialog Instance .

Installation Services for a Central System

Installation Service Remarks

Central System Installation Installs a complete SAP system including the followinginstances on one host:l Central services instance (SCS)l Database instancel Central instanceYou can install a central system in the following parametermodes:l Typical Mode

If you choose the “Typical” setting, automatic defaultsettings will be provided. You only have to respondto a small selection of prompts. However, you canchange any of the default settings on the parametersummary screen.

l Custom ModeIf you choose the “Custom” setting, all installationparameter will be prompted. In the end, you can stillchange any of these parameters on the parametersummary screen.

NoteYou require at least the usage types AS Java and AS ABAP.You can choose the usage types or software units on thescreen SAP System > 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 Java.Installs a central services instance (SCS) and prepares theSAP global host.

08/31/2007 PUBLIC 87/176



Database Instance Mandatory step in installing a distributed SAP system.Installs a database instance.You 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 hosts.Installs 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 > 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)

Database Instance Installs a database instance

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

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 > Software Units.

Dialog Instance Installs a dialog instance

n Additional Software Life-Cycle TasksYou use this service to perform the following tasks or to install the following components:

88/176 PUBLIC 08/31/2007


Installation Service Remarks

Additional Preparation Tasks These preparation tasks comprises:l Operating System Users and Groups

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

CautionPerform this task before you start the installation of your SAPsystem.

l Prerequisites CheckChecks your hardware and software requirements before youstart the installation.Otherwise, 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 [page42].

Application Server Choose Application Server <Database> Dialog Instance to installone or more dialog instance(s) in an already installed SAP system,if required.

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

System Copy Choose this service to perform a system copy.For more information, see the system copy guide,which is available at SAP Service Marketplace at:

http://service.sap.com/instguidesnw70 Installa-tion

Uninstall Choose this service to uninstall your SAP system, standalone engines,or optional standalone units.For more information, see Deleting an SAP System Using SAPinst [page 161]

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 screen.This screen shows both the parameters that you entered and those that SAPinst set by default.

6. If required, change the displayed parameters as follows:a) Select the parameters you want to change.

08/31/2007 PUBLIC 89/176

http://service.sap.com/instguidesnw70

http://service.sap.com/instguidesnw70


b) Choose Revise.SAPinst displays input screens for the selected parameters.

c) Enter the new values for the parameters.7. To start the installation choose Start.

SAPinst starts the installation and displays the progress of the installation.When 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 98].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_exe.xxxxxx.xxxx after SAPinst has finished.Sometimes these remain in the temporary directory.

Note

If there are errors with SAPinst Self-Extractor, you can find the Self-Extractor log filedev_selfex.out in the temporary directory.

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 <user_home>/.sdtgui/.10. 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 159].

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

90/176 PUBLIC 08/31/2007


Caution

Keep in mind that you cannot install the Java Add-In for the dialog instance(s) of the existingABAP system. Instead, you have to uninstall the old ABAP dialog instance(s) install new ABAP+Javadialog instance(s).

PrerequisitesYour ABAP system must be based on SAP NetWeaver 7.0 SR2.Make sure that the parameter compatible is set to 10.2.0 in the file init<dbsid>.ora.

Procedure

1. Start SAPinst [page 84].2. On theWelcome screen, choose <SAP system> Additional Software Life-Cycle Tasks Java Add-In for

ABAP <database> <system variant> .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:

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 service, uninstall the old ABAP dialog instance(s).

Installation Services for a Java Add-In for ABAP ‒ High-Availability 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

08/31/2007 PUBLIC 91/176



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

Dialog Instance Installs an ABAP+Java dialog instance in a high-availabilitysystem

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

4. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

Note

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

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

Caution

You cannot install the Java Add-In for the dialog instance(s) of the existing ABAP system. Instead,you have to install new ABAP+Java dialog instances as follows:On theWelcome screen, choose <SAP system> Additional Software Life-Cycle Tasks Application Server<database> Dialog Instance .

4.3.3 Using SAPinst GUI

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

92/176 PUBLIC 08/31/2007


SAPinst GUI Functions

Button / Function Key / Menu Entries Description

F1 Displays detailed information about each inputparameter.

Exit Cancels the installation with the following options:n Stop

Stops the installation (SAPinst GUI, SAPinst andthe GUI server) without further changing theinstallation files. You can restart and continue theinstallation later from this point.

n ContinueContinues the installation.

Log off Stops the SAPinst GUI, but SAPinst and the GUI servercontinue running.

NoteIf for some reason you need to log off during theinstallation from the host where you control theinstallation with SAPinst GUI, the installationcontinues while you are logged off. You can laterreconnect to the same SAPinst installation from thesame or another host. For more information, seeStarting SAPinst GUI Separately [page 96].

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

Stop Stops the installation without further changing theinstallation files. You can continue the installation laterfrom this point.

Continue Continues with the option you have chosen before.

4.3.4 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 phase:SAPinst 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:

08/31/2007 PUBLIC 93/176


Option Definition

Retry SAPinst retries the installation from the point of failure without repeatingany of the previous steps.This is possible because SAPinst records the installation progress in thekeydb.xml file.We recommend that you view the entries in the log files, try to solve theproblem and then choose Retry.If 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 server.SAPinst records the installation progress in the keydb.xml file. Therefore,you 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.

Note

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

3. Enter the following commands:cd <Installation_Master_DVD>/IM_<OS>

./sapinst

4. From the tree structure in theWelcome screen, select the installation service that you want tocontinue and choose Next.

94/176 PUBLIC 08/31/2007


Note

If there is only one component to install, theWelcome screen does not appear.

TheWhat do you want to do? screen appears.5. 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 installation.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds> (for example,log_01_Oct_2003_13_47_56).

Continue old installation SAPinst continues the interrupted installation from the point of failure.

4.3.5 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 81].n Both computers are in the same network and can “ping” each other.

To test this:l Log on to your remote host and enter the command ping <local host>.l Log on to the local host and enter the command ping <remote host>.

Procedure

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

Caution


2. Mount the Installation Master DVD.3. Enter the following commands:

cd <Installation_Master_DVD>/IM_<OS>

08/31/2007 PUBLIC 95/176


./sapinst -nogui

For more information, see Running SAPinst on UNIX [page 84].SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following atthe command prompt:guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation.

4. Start SAPinst GUI on your local host, as described in Starting SAPinst GUI Separately [page 96].

4.3.6 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 SAPinst.If 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 95].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 71] 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 group.2. Insert the SAP Installation Master DVD into your DVD drive.3. To change to the relevant directory enter the following command:

cd <DVD drive>:\IM_WINDOWS<platform>

4. Start SAPinst GUI in one of the following ways:n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following

command:startinstgui.bat

SAPinst GUI uses the local host as default.n If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation),

enter the following command:startinstgui.bat -host <host_name>

<host_name> is the host name of the installation host.

96/176 PUBLIC 08/31/2007


Note

l If you enter the command without additional parameters, SAPinst GUI uses the localhost as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. AsSAPinst and the GUI server are running on another host, SAPinst GUI cannot connect andthe SAP Installation GUI Connection dialog appears.In this case, enter the name of the host on which SAPinst is running and choose Log on.The 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 startinstgui.bat -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 command:cd <Installation_Master_DVD>/IM_<OS>

4. Start the SAPinst GUI in one of the following ways:n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following

command without additional parameters:./startInstGui.sh

SAPinst GUI uses as default the local host.n If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation),

enter the following command with additional parameters:./startInstGui.sh -host <host_name>

<host_name> is the host name of the installation host.

08/31/2007 PUBLIC 97/176

4 Installation4.4 Oracle Database Software Installation

Note

l If you enter the command without additional parameters, SAPinst GUI uses the localhost as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. AsSAPinst and GUI server are running on another host, SAPinst GUI cannot connect and theSAP Installation GUI Connection dialog appears.In this case, enter the name of host on which SAPinst is running and choose Log on.The 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 ./startInstGui.sh -h.

4.3.7 Entries in the Services File Created by SAPinst

After the installation has finished successfully, SAPinst has created the following entries in/etc/services:sapdpXX = 32XX/tcp

sapdbXXs = 47XX/tcp

sapgwXX = 33XX/tcp

sapgwXXs = 48XX/tcp

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.

4.4 Oracle Database Software Installation

SAPinst prompts you to install the Oracle database.

Caution


Proceed as follows to install the Oracle database software:

Process Flow

1. You update SAP-specific files in the Oracle stage area [page 99].2. You run the Oracle Universal Installer [page 99]3. You install the current patch set [page 101]4. You install required interim patches [page 101]

98/176 PUBLIC 08/31/2007


4.4.1 Updating SAP-Specific Files in the Oracle Staging Area

SAPinst extracts the Oracle RDBMS software to the staging area, usually /oracle/stage/<102_32or 102_64>/database.The SAP folder located in /oracle/stage/<102_32 or 102_64>/database contains SAP-specificscripts as well as the response files.Before 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 /oracle/stage/<102_32 or 102_64>/database/SAP

/oracle/stage/<102_32 or 102_64>/database/SAP_ORIG

n mv /oracle/stage/<102_32 or 102_64>/database/Disk1/SAP

/oracle/stage/<102_32 or 102_64>/database/Disk1/SAP_ORIG

2. Download the file RDBMS_SAP_32.zip (for 32-bit platforms) or RDBMS_SAP_64.zip (for 64-bitplatforms) attached to SAP Note 819830 and copy it to a temporary location such as /tmp.

3. Extract the zip file by performing one of the following:

n cd /oracle/stage/<102_32 or 102_64>/database

unzip /tmp/RDBMS_SAP.zip

n cd /oracle/stage/<102_32 or 102_64>/database/Disk1

unzip /tmp/RDBMS_SAP.zip

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

4.4.2 Running the Oracle Universal Installer

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

Procedure

1. Start the OUI with the user ora<dbsid> as follows:n For 32-bit systems, enter the following:

cd /oracle/stage/102_32/database/SAP

./RUNINSTALLER

n For 64-bit systems, enter one of the following:

l cd /oracle/stage/102_64/database/Disk1/SAP

./RUNINSTALLER

l cd /oracle/stage/102_64/database/SAP

./RUNINSTALLER

08/31/2007 PUBLIC 99/176



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

2. Respond to the OUI as follows:

Prompt or Condition Action

When you run the OUI for the first time on this host,a dialog box, Specify File Locations Destination..., appears.This dialog box proposes the inventory location as/oracle/oraInventory 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 failed,review the cause for the warning or failure on screenand fix the problem if possible.Alternatively 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_HOME/root.shwith the userroot, and confirm the dialog box by choosing OK.If this is the first time that the Oracle softwarehas been installed on this host, the OUIalso asks you to execute a second script,/oracle/oraInventory/orainstRoot.sh, as the rootuser. Execute this script as well.Continue by choosing Next.

3. 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 Assistant.You can ignore messages that some of the config assistants failed to complete successfully.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_HOME/install/portlist.ini file.

4. To exit the OUI, choose Exit and confirm the dialog box that appears.

Note

You can now access the Oracle 10.2 online documentation, which was installed duringthe last step. You can find the entry point to the Oracle online documentation at$ORACLE_BASE/doc/index.htm.

100/176 PUBLIC 08/31/2007


4.4.3 Installing the Current Patch Set

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

Prerequisites

n For more information on the latest patch set available for Oracle 10.2 see SAP Note 871735.n For more information on 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 patchset README file. Thepost-installation steps are to be performed only on an existing Oracle 10.2 database.At this stage you have only installed the Oracle 10.2 software. The database itself is still not Oracle10.2. 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 ora<dbsid> user.2. Download and extract the patch set as described in SAP Note 932251.3. Install the patch set as described on the patch set README file.

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

Prerequisites

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

Procedure

1. Log on at the operating system level as the ora<dbsid> user.2. Install the patches, following the instructions in SAP Note 839182.

08/31/2007 PUBLIC 101/176







Note

You can apply the patches in any order.We 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_HOME/OPatch/opatch lsinventory

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

102/176 PUBLIC 08/31/2007

5 Post-Installation

5 Post-Installation

You perform the following post-installation steps:

1. You check whether you can log on to the application server [page 105].

2.

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

You check whether you can log on to the portal [page 106].End of: Enterprise Portal (EP);EP Core (EPC)

3.


You check whether you can log on to SAP the Development Infrastructure [page 107].End of: Development Infrastructure (DI)

4. You install the SAP license [page 108].

Caution

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

5. You install the SAP Online Documentation [page 109].

Caution


6. You configure the remote connection to SAP support [page 109].

Caution


7. You perform initial ABAP configuration [page 110].

Caution


8. You perform the Oracle-specific post-installation steps [page 112].

Caution


08/31/2007 PUBLIC 103/176

5 Post-Installation

9. You apply the latest kernel and Support Packages [page 112].10. You perform the client copy [page 114]

Caution


11. You perform a full backup of the installation [page 115].12. You perform post-installation steps for Adobe Document Services [page 117].13. If required, you configure access to SAP Knowledge Warehouse content from the SAP Internet Knowledge Servlet

[page 119].

14.

Only valid for: BI Java Components (BI-Java);Process Integration (PI)

You set the environment variable CPIC_MAX_CONV [page 120].End of: BI Java Components (BI-Java);Process Integration (PI)

15.


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

16.


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

17.


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

Caution


End of: HA (UNIX)

18. You ensure user security [page 123].

19.

Only valid for: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Mobile Infrastructure

(MI);Process Integration (PI)

To perform basic configuration steps, you run the Configuration Wizard [page 127].

Caution


End of: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Mobile Infrastructure (MI);Process

Integration (PI)

20. You check the Java documentation [page 130] for information that is relevant for running your Java system.

104/176 PUBLIC 08/31/2007

5 Post-Installation5.1 Logging On to the Application Server

21. You may now start with the manual configuration of your IT scenarios for which you find theappropriate documentation in the SAP Solution Manager [page 132].

5.1 Logging On to the Application Server

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

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 running.n 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 follows:n 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 Java<Release> .

Note

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

The SAP Logon appears.2. Create a logon entry for the newly installed system in the SAP Logon.

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

08/31/2007 PUBLIC 105/176

5 Post-Installation5.2 Logging on to the Portal

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 URL:http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00

Note

You must always enter a two-digit number for <Instance_Number>. 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 URL:http://saphost06:50400

The start page of the SAP NetWeaver Application Server Java appears in the Web browser.2. 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 RZ11.2. In the instance profile of every installed SAP instance, set parameter rdisp/j2ee_start from 1

to 0.


5.2 Logging on to the Portal

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

Java User

User User Name Storage: ABAP System

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

106/176 PUBLIC 08/31/2007

5 Post-Installation5.3 Logging on to the Development Infrastructure (DI)

PrerequisitesThe SAP system is up and running.

ProcedureYou access the portal with a URL using a Web browser from your client machines.The default URL consists of the installation host name and the port on which the portal is listening.You 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 URL:http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00/irj

Note

You must always enter a two digit number for <Instance_Number>. 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 URL:http://saphost06:50400

2. Log on by entering the required user and password.

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


5.3 Logging on to the Development Infrastructure (DI)

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

Procedure

1. Start a Web browser and enter the following URL:http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00/devinf

Note

You must always enter a two-digit number for <Instance_Number>. For example, do not enter 1but instead enter 01.

08/31/2007 PUBLIC 107/176

5 Post-Installation5.4 Installing the SAP License

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 URL:http://saphost06:50400

2. Log on with the user NWDI_ADMIN.The start page SAP NetWeaver Development Infrastructure appears in the Web browser.You should see the following links:n 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 127] or by configuringyour system manually.

End of: Development Infrastructure (DI)

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

108/176 PUBLIC 08/31/2007

5 Post-Installation5.5 Installing the SAP Online Documentation

Caution

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

ProcedureFor information about the installation procedure for the SAP license, see:http://help.sap.com/nw70 SAP NetWeaver SAP NetWeaver Library Technology Consultant’s Guide

Cross-NetWeaver Configurations SAP License Key

More InformationFor more information about SAP license keys, see SAP Service Marketplace athttp://service.sap.com/licensekey.

5.5 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 SAP.You can always find the up-to-date SAP online documentation at http://help.sap.com.

ProcessInstall the SAP online documentation in your SAP system as described in the README.TXT filecontained in the root directory of the online documentation DVD, delivered as part of the installationpackage.

5.6 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 SAP.For more information, see SAP Service Marketplace at http://service.sap.com/remoteconnection.

08/31/2007 PUBLIC 109/176




http://service.sap.com/licensekey



http://help.sap.com

http://service.sap.com/remoteconnection



5 Post-Installation5.7 Performing Initial ABAP Configuration

5.7 Performing Initial ABAP Configuration

Caution


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

Procedure

1. Go to the following place in the SAP Library:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability

2. Check the documentation on the following configuration steps:n Configuring the transport management system

For more information, see Solution Life Cycle Management by Key Capability Software Life CycleManagement 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 Distribution SAP Logon

Set up administrators Background Processing Authorizations for Background Processing

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 work processesFor more information about instance profiles, which is where work processes are defined,see Solution Life Cycle Management by Key Capability System Management Configuration ProfilesProfile Files Instance Profiles .

Note

SAPinst 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 on thesystem resources and on the number of users working in each SAP system application. For adetailed configuration contact SAP Technical Consulting.

110/176 PUBLIC 08/31/2007




5 Post-Installation5.7 Performing Initial ABAP Configuration

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 on configuring the language settings, see the online documentationin transaction I18N I18N Menue I18N Customizing .

l Performing language transport using transation SMLT:For more information on performing the language transport using transaction SMLT.see Solution Life Cycle Management by Key Capability Software Life Cycle Management SoftwareLogistics Change and Transport System Language Transport. .

n Using and Configuring the ITS Integrated in ICMAs of SAP NetWeaver 2004 (’04), the SAP Internet Transaction Server (SAP ITS) is integratedin the SAP NetWeaver Application Server ABAP (AS ABAP) as an Internet CommunicationFramework (ICF) service, which you can access, 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 sources,such as service files, HTML templates, or MIME files, are now stored in the database of thesystem.The SAP ITS supports the following functions:l SAP GUI for HTML

l Internet Application Component (IAC) runtime or Web Transaction technologyl For information on how to congure the SAP integrated ITS, see

http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver Library:Function-Oriented View Application Server ABAP Presentation Development on AS ABAP ITS /SAP@Web Studio (BC-FES-ITS) SAP ITS in the SAP Web Application Server Conguration .

l For more information about memory requirements of the ITS, see SAP Note 742048.n Maintaining address data

For more information on maintaining the company address in your SAP system usingtransaction SU01, see Application Platform by Key Capability Business Services Business AddressServices (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 applications,which includes customizing the ABAP system and the business components, see Solution LifeCycle Management by Key Capability Customizing .

08/31/2007 PUBLIC 111/176





5 Post-Installation5.8 Performing Oracle-Specific Post-Installation Steps

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

n For information onOracle database configuration, see the documentation SAP Database Guide:Oracle (BC-DB-ORA-DBA) in the SAP Library at http://help.sap.com/nw70 SAP NetWeaverLibrary SAP NetWeaver by Key Capability Application Platform (SAP Web Application Server) ApplicationServer Infrastructure Databases Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA)

n For information on Oracle database administration using Computing CenterManagement System (CCMS), see the documentation CCMS: Oracle in the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Application

Platform by Key Capability Application Platform (SAP Web Application Server) Application Server InfrastructureDatabases Oracle CCMS: Oracle

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

112/176 PUBLIC 08/31/2007









5 Post-Installation5.9 Applying the Latest Kernel and Support Packages

Note

All corrective software packages, including Support Packages (Stacks) for SAP NetWeaver 7.0 (2004s)and subsequent versions, as well as all applications which are based on this software (includingSAP Business Suite 2005), released after April 2, 2007, will be available exclusively through theMaintenance Optimizer in SAP Solution Manager.For more information on the Maintenance Optimizer,see http://service.sap.com/solutionmanager Functions in Detail Support Area MaintenanceOptimizer .

Caution

Before you apply support packages, make sure that you read the release notes for your SAP system.You can find these on SAP Service Marketplace at http://service.sap.com/releasenotes. Therelease notes might include information about steps you have to perform after you have appliedthe support packages.

Caution

Make sure that the entry DIR_CT_RUN exists in the instance profile. Otherwise you cannot restart thesystem after patches have been applied.See also Setting Up File Systems [page 59].

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 packages.JSPM is a Java standalone tool that you can use with SAP NetWeaver 7.0. JSPM uses the SoftwareDeployment Manager (SDM) to apply support packages and patches and to deploy softwarecomponents.For more information about JSPM and how to use this tool, see http://help.sap.com/nw70 SAPNetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SoftwareLife Cycle Management Software Maintenance Java Support Package ManagerYou can also use the Support Package Manager to apply the latest ABAP support packages.For more information about the Support Package Manager and how to use this tool, seehttp://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life

Cycle Management by Key Capability Software Life Cycle Management Software Maintenance Support PackageManager

PrerequisitesTo extract the downloaded SAR files make sure that you use the latest SAPCAR version, which youcan find on SAP Service Marketplace at http://service.sap.com/swdc. You need at least SAPCAR

08/31/2007 PUBLIC 113/176




http://service.sap.com/releasenotes












5 Post-Installation5.10 Performing the Client Copy

700 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. Apply the latest kernel.You must always replace the installed kernel with the latest kernel from SAP Service Marketplace.In particular, you must replace the installed kernel if:n You installed the kernel executables locally on every host.n Your central instance host runs on a different operating system than your dialog instance host.For more information about how to download a kernel, see SAP Note 19466.To exchange the ABAP+Java kernel, you can use Java Support Package Manager (JSPM).

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

patches, see SAP Service Marketplace at:http://service.sap.com/sp-stacks

For up-to-date release information on Support Package Stacks and about how to apply them,see the documentation SAP NetWeaver 7.0 ‒ Support Package Stack Guide <current version> on SAPService Marketplace at http://service.sap.com/MaintenanceNW70.

b) Alternatively, you can download Support Packages from SAP Service Marketplace at:http://service.sap.com/patches

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 Marketplaceat:http://service.sap.com/ocs-schedules

Note

The SAP Note Assistant lets you load, implement, and organize individual SAP Notes efficiently. Italso recognizes dependencies between SAP Notes, Support Packages, and modifications.For more information, see the SAP Service Marketplace at:http://service.sap.com/noteassistant

5.10 Performing the Client Copy

SAPinst creates three ABAP clients during the installation, client 000, client 001, and client 066.Client 000 is the SAP reference client for ABAP.

114/176 PUBLIC 08/31/2007






http://service.sap.com/MaintenanceNW70



http://service.sap.com/patches



http://service.sap.com/ocs-schedules



http://service.sap.com/noteassistant



5 Post-Installation5.11 Performing a Full Installation Backup

If you chose to install an ABAP+Java system in one installation run, AS Java was configured againstclient 001 during the installation.Your production client must be a copy of the SAP reference client 000. For more information, seeProduction Client Considerations [page 22]


Caution

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

End of: Process Integration (PI)

Procedure

1. Maintain the new client with transaction SCC4.2. Activate kernel user SAP*:

a) Set the profile parameter login/no_automatic_user_sapstar to 0.b) Restart the application server.

3. Log on to the new client with kernel user SAP* and password PASS.4. Copy the client with transaction SCCL and profile SAP_CUST.5. Check the log files with transaction SCC3.6. 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 SAP*:a) Reset login/no_automatic_user_sapstar to 1.b) Restart the application server.

For more information, see:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life

Cycle Management by Key Capability Software Lifecycle Management Software Logistics Change and TransportSystem BC ‒ Client Copy and Transport

5.11 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 backed-up data for a restore.

Caution

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

08/31/2007 PUBLIC 115/176





5 Post-Installation5.11 Performing a Full Installation Backup

You need to back up the following directories and files:

n All SAP-specific directories:

l /usr/sap/<SAPSID>

l /usr/sap/trans

l <sapmnt>/<SAPSID>

l Home directory of the user <sapsid>admn All database-specific directoriesn The root file system

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

Note

This list is only valid for a standard installation.

Prerequisites

n If required, you have completed client maintenance, such as the client copy [page 114].n You have logged on [page 105] as user <sapsid>adm and stopped the SAP system and database [page 144].

This procedure works on all hardware platforms. For more information on operating system-specificbackup procedures, see your operating system documentation.

Backing Up the Installation

1. Log on as user root.2. Manually create a compressed tar archive that contains all installed files:n Saving to tape:

tar —cf — <file_system> | compress —c > <tape_device>

n Saving to the file system:tar —cf — <file_system> | compress —c > ARCHIVENAME.tar.Z

Restoring Your BackupIf 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 root.2. Execute the following commands ton restore the data from tape:

cat <tape_device> | compress —cd | tar —xf —

116/176 PUBLIC 08/31/2007

5 Post-Installation5.12 Post-Installation Steps for Adobe Document Services

n restore the data from the file system:cat ARCHIVENAME.tar.Z | compress —cd | tar —xf —

Performing a Full Database Backup

1. Configure your third-party backup tool, if used.2. Perform a full database backup (preferably offline).

If you use BR*TOOLS for the backup, refer to BR*Tools for Oracle DBA in the SAP DatabaseGuide: Oracle (BC-DB-ORA-DBA). This documentation is available in the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Application

Platform (SAP Web Application Server) Application Server Infrastructure Databases Oracle SAP DatabaseGuide: Oracle (BC-DB-ORA-DBA) .

5.12 Post-Installation Steps for Adobe Document Services

You perform the following post-installation steps:

n You assign the required roles to users ADSUSER and ADS_AGENT [page 117].n You check the IIOP service and the startup properties [page 118].n You perform quick tests for Adobe Document Services (ADS) [page 118].

5.12.1 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 environment.After 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 SAP*.2. Call transaction SU01.3. Enter ADS_AGENT in the User field.4. 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 105].2. Call transaction PFCG.3. Enter ADSCallers in the Role field.4. Choose Role Create .

08/31/2007 PUBLIC 117/176




5 Post-Installation5.12 Post-Installation Steps for Adobe Document Services

5. On the Create Roles screen, choose Role Save .6. Choose the User tab and assign the user ADSUSER in the User ID field.

5.12.2 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 running/usr/sap/<SAPSID>/<instance_name>/j2ee/configtool.sh.The Config Tool screen appears.

2. Check if the startup mode of the service iiop is set to always:a) In the left frame, open the tree Cluster data Cluster data Global dispatcher configuration Services .b) Choose service iiop.c) The field Startup mode in the right frame must be set to always. If it is not true, apply the value

always.d) Choose Apply changes.e) Repeat the steps b. to d. for the following path: Cluster data Cluster data Global server

configuration Services .3. Check if the Java startup property for Adobe document services is set as follows:

a) Select Cluster data Cluster data instance_<IDxxxx> server_<IDxxxx> .b) In the right frame, check if the following line exists in the Java Parameters area of the tab General:

-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine. services.ts.jts.ots.PortableInterceptor.JTSIni-tializerIf the line does not exist, add the line to this section.

4. Exit the configuration tool.5. If you have applied new values during the procedure above, you need to restart the AS Java

to adapt the new settings.

5.12.3 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 ABAP

118/176 PUBLIC 08/31/2007

5 Post-Installation5.13 Configuring Access to Knowledge Warehouse Content from the SAP Internet Knowledge Servlet

and 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 http://help.sap.com/nw70 SAP NetWeaverLibrary Technology Consultant’s Guide Business Task Management Adobe Document Services (Configuration)Adobe Document Services Configuration Guide Configuring the Web Service Securing Access to the Web ServiceConfiguration Check .If the tests are not successful, you might have to make some adjustments to the initial technicalconfiguration for ADS [page 149].

More InformationThe Adobe Document Services Configuration Guide is also available in PDF form athttp://service.sap.com/adobe SAP Interactive Forms by Adobe Media Library Documentation SAP

NetWeaver 7.0 (2004s) Configuration Guide ‒ SAP Interactive Forms by Adobe Adobe Document Services ‒ For SAP WebApplication Server 7.0 (Support Package SPS <current number>)

5.13 Configuring Access to Knowledge Warehouse Contentfrom the SAP Internet Knowledge Servlet

You need to perform this step if you want to use the variant Documentation Manuals and TrainingMaterials Management of the scenario Enterprise Knowledge Management.For more information, see SAP Library at http://help.sap.com/nw70 SAP NetWeaver LibraryIT Scenarios at a Glance Enterprise Knowledge Management Documentation, Manuals and Training MaterialsManagement .The SAP Internet Knowledge Servlet (IKS) is a Java servlet based on the J2EE Engine. It is used todisplay content stored in the Knowledge Warehouse (KW) in the browser.

PrerequisitesYou have completed the installation of AS ABAP and AS Java as described in this documentation.

Procedure

1. Create a user of type system in your ABAP system using transaction SU01 and assign this user tothe role SAP_KM_KW_RFC_CPIC_USER.This user is needed for the connection between the SAP IKS and the ABAP system.

08/31/2007 PUBLIC 119/176




http://service.sap.com/adobe




5 Post-Installation5.14 Setting Environment Variable CPIC_MAX_CONV

2. Make sure that the Administrator user of the J2EE Engine has the required authorizations toperform the configuration:a) Log on to the User Management Engine (UME) using the URL

http://<J2EE_host>:<J2EE_port>/useradmin/index.jsp.b) Assign either the role SAP_J2EE_ADMIN or KW_ADMINISTRATOR to the Administrator user.c) If none of these roles exists, you need to create one of them. You do not need to perform

further configuration of the newly created role.d) Log off from the UME.

3. Open a browser window and enter the following URL:http://<J2EE_host>:<J2EE_port>/SAPIKS2

The UME logon page appears.4. Log on as the Administrator user of the J2EE Engine.5. In the next screen, choose Direct Access to the SAP Knowledge Warehouse.6. Choose Continue.7. In the next screen, enter the connection parameters to the KW back-end system.8. Choose Test.9. If the connection was successfully established, save the parameters. If not, correct the parameters.10. After saving the parameters you can access the Knowledge Warehouse directly from the next

screen.

Only valid for: BI Java Components (BI-Java);Process Integration (PI)

5.14 Setting Environment Variable CPIC_MAX_CONV

1. Log on to your SAP system as a user with administration rights.2. Call transaction RZ10.3. Set the value gw/max_conn_per_wp to a higher value (at least 200) and restart the system.

End of: BI Java Components (BI-Java);Process Integration (PI)


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

120/176 PUBLIC 08/31/2007

5 Post-Installation5.16 Post-Installation Steps for Application Sharing Server

5.15.1 Performing PI-Specific Steps for SLD Configuration

Central SLD: Checking the CR Data in the SLD (optional)Since CR_Content.zip contains all available SAP components, the content of this file grows with time.The extensions contain information about new components (new releases and Support Packages, forexample). This content in the SLD has to be updated from time to time.You can download the most up-to-date files from the SAP Service Marketplace.For more information, see SAP Note 669669.

More InformationFor more information on SLD users and security roles, see the Post-Installation Guide - SLD of SAPNetWeaver 7.0 at http://service.sap.com/sld Media Library .End of: Process Integration (PI)


5.16 Post-Installation Steps for Application Sharing Server

After you have installed the necessary software, you must complete a number of configurationsteps in the portal to fully implement application sharing functionality in the portal. These stepsare valid if you installed Application Sharing Server as a standalone engine or are using the defaultserver installed on the portal machine.For more information, see:http://help.sap.com/nw70 SAP NetWeaver SAP NetWeaver by Key Capability People Integration

Collaboration Administration Guide Real-Time Collaboration Configuring Real-Time Collaboration Configuringthe Application Sharing Server (RTC) .This documentation includes information on how you define which Application Sharing Serverthe portal must use.If you do not intend to use Application Sharing Server, you can disable it. For more information, see:http://help.sap.com/nw70 SAP NetWeaver SAP NetWeaver by Key Capability People Integration

Collaboration Administration Guide Real-Time Collaboration Configuring Real-Time Collaboration Configuringthe 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 ‒ <your product> Java on <OS> : <Database>End of: Enterprise Portal (EP)

08/31/2007 PUBLIC 121/176







5 Post-Installation5.17 High Availability: Post-Installation Steps


5.17 High Availability: Post-Installation Steps

5.17.1 Setting Up Licenses

Caution


If your high-availability (HA) installation is running a two-node switchover cluster, you need toorder two SAP licenses [page 108]. When we receive confirmation from your vendor that you areimplementing a switchover environment, we provide two license keys for your system, one keyfor each machine.SAP has implemented a license mechanism for transparent and easy use with switchover solutionsand clustered environments. Your customer key is calculated on the basis of local information on themessage server host. This is the host machine where the central services (SCS) instance runs. Thereis no license problem when only the database is switched over.A switchover involving the central services (SCS) instance affects the licensing mechanism, so forthis case you must have two licenses, which you can install in parallel. There is no license problemwhen only the database is switched over.

Procedure

1. Execute the following as user <sid>adm on the primary and secondary node where the ABAP SCSinstance runs for every license key you obtain from SAP:saplicense -install

2. Run the SCS instance on the primary host, node A.3. To find the hardware ID of the primary host, run the Visual Administrator on node A and choose

CI Host License Adapter .The hardware ID is displayed in the Visual Administrator.

4. Switch over the SCS instance to the backup host, node B.5. To find the hardware ID of the backup host, run the Visual Administrator on node B and choose

CI Host License Adapter .The hardware ID is displayed in the Visual Administrator.

6. To obtain the two license keys, enter the hardware IDs for the primary and backup hosts in SAPService Marketplace at:http://service.sap.com/licensekey

7. Open the Visual Administrator on the node where the SCS instance is running and choose CIHost License Adapter and import the file containing the two licenses.

122/176 PUBLIC 08/31/2007




5 Post-Installation5.18 Ensuring User Security

ResultThe license is no longer a problem during switchover. This means you do not need to call saplicensein your switchover scripts.

5.17.2 Taking Precautions for Transport

Caution


With a high-availability (HA) installation you need to take precautions before you perform a transport.TPPARAM contains parameter settings for the transport control program tp, which is used for exportsand imports. It also includes the parameter <SID>/dbhost, which is used to address the database host.

ProcedureSet <SID>/dbhost to the virtual host name of the DB instance.This lets you use the transport system for the normal maintenance of ABAP programs, but still allowstransparent operation in the event of a switchover.End of: HA (UNIX)

5.18 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 network.Therefore, 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 RFC.For more information, see:http://help.sap.com/nw70 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.

08/31/2007 PUBLIC 123/176





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

Operating System and Database Users

User User Name Comment

<sapsid>adm SAP system administratorOperating system user

ora<dbsid> Oracle database administrator (thatis, the owner of the database files)

SAP<SCHEMA_ID> 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 SAP system clients000, 001 and 066.

DDIC User exists at least in SAP system clients000 and 001.

EARLYWATCH User exists at least in SAP system client066.

SAP system user

SAPCPIC User exists at least in SAP system clients000 and 001.

Administrator The name that you gave this userduring the installation or the defaultname J2EE_ADMIN

This user’s password is stored in securestorage. Therefore, whenever youchange the administrator’s password,you must also change the password insecure storage.For more information, see Checking theSAP Java Documentation [page 130].

124/176 PUBLIC 08/31/2007

http://service.sap.com/securityguide





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 SAP system clients000 and 001.

Users for AdobeDocument Services (ADS)

ADS_AGENT User exists at least in SAP system clients000 and 001.

Data supplier userfor System LandscapeDirectory (SLD)(optional)

The name that you gave this userduring the installation.The recommended name is SLDDSUSER.

User exists at least in SAP system clients000 and 001.

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 installation.The recommendedname is SLDAPIUSER.

User exists at least in SAP system clients000 and 001.


Java Add-In Users for Users Stored in the ABAP System

User User Name Storage: ABAP System Comment

Administrator The name that you gave this userduring the installation or the defaultname J2EE_ADMIN

This user’s password is stored in securestorage. Therefore, whenever youchange the administrator’s password,you must also change the password insecure storage.For more information, see Checking theSAP Java Documentation [page 130].

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

‒

08/31/2007 PUBLIC 125/176

5 Post-Installation5.19 Running the Configuration Wizard

User User Name Storage: ABAP System Comment

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 installation.The recommended name is SLDDSUSER.

User exists at least in the clients 000 and001 of the ABAP system.


ABAP API user for SystemLandscape Directory (SLD)(optional)

The name that you gave this userduring the installation.The recommendedname is SLDAPIUSER.

User exists at least in the clients 000 and001 of the ABAP system.



Users in the SAP NetWeaver Development Infrastructure (NWDI)


NWDI Administrator NWDI_ADM Administrator of the NWDI

NWDI Developer NWDI_DEV Developer in the NWDI

NWDI CMS TechnicalAdministrator

NWDI_CMSADM Administrator of the NWDIChange Management System(CMS)

CautionDo not log on with this user. Itis used by the system for internalcommunication.


126/176 PUBLIC 08/31/2007


Only valid for: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Mobile Infrastructure

(MI);Process Integration (PI)

5.19 Running the Configuration Wizard

This section provides information about how to run the Configuration Wizard for the SAP NetWeaverusage types.

Note

You can run the Configuration Wizard only once and only directly after you installed and patchedthe system.You cannot use the configuration wizard after:

n Upgrade

n 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.For more information , see Accessing Configuration Documentation in the SAP Solution Manager [page 132].You can also find configuration documentation in the Technology Consultant’s Guide in the SAPLibrary at:http://help.sap.com/nw70 SAP NetWeaver Technology Consultant’s Guide

For more information about how to start the Configuration Wizard, see the SAP Library at:http://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’s Guide Developing,

Configuring, and Adapting Applications Creating Java Applications Using Web Dynpro J2EE Engine ConfigurationConfiguration Wizard

Note

For more information on the Configuration Wizard and its limitations, see SAP Note 923359.


Note

You can run the configuration task for BI Java Components (BI-Java) several times and after alluse cases.


08/31/2007 PUBLIC 127/176









PrerequisitesBefore you run the configuration wizard, make sure you have applied the latest kernel and support packages[page 112] to your system.

Only valid for: Application Server (AS)

Usage Type: Application ServerYou need to run the following configuration tasks using the Configuration Wizard to automaticallyconfigure the SAP NetWeaver Administrator:

1. SLD system: Configure and activate SLD2. SLD system: Connect SLD to CEN (if CEN present)3. NWA system: Basic configuration4. NWA system: Connect NWA to CEN (if CEN present)5. NWA system: Store access data per each managed Java system (optional)6. NWA system: Register each managed ABAP system to SLD7. Managed Java system: Register system to SLD

Note

For more information about the NetWeaver Administrator, seehttp://service.sap.com/operationsnw70 Monitoring Monitoring Setup Guide

for NW 7.0 (2004s) SP Stack 09/SR2 .

End 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 PIPostInstallProcess using the ConfigurationWizard. To select the configuration task, change the scenario on the right of the page to PI.

Caution

If you are using a central SLD, you also have to perform the steps for SLD configurationmanuallyas described in SAP Note 939592.

Note

After the Configuration Wizard has finished, you need to restart your SAP system.


128/176 PUBLIC 08/31/2007

http://service.sap.com/operationsnw70






Usage Type: BI Java Components (BI-Java)After SAPinst has finished, you need to run the configuration task BIPostInstallProcess usingthe Configuration Wizard.For more information see SAP Note 917950.

Recommendation

We recommend that you check the configuration of BI-Java using SAP Note 937697.



Usage Type: Development InfrastructureAfter SAPinst has finished, you need to run the configuration task for usage typeDI using theConfiguration Wizard.

1. Under Scenario choose DI.2. Decide whether you want to install and run the entire NWDI on this system or configure the

services individually:

Recommendation

We recommend that use the first option shown below, to install and run the entire NWDI onthis system.

n To install and run the entire NWDI on this system, perform the following steps:a) Choose the Scenario DIb) Choose All-in-one Complete Configuration of DTR, CBS, and CMSc) Fill the open fields in the section Data Entry according to their label.d) To run the configuration task, choose Execute Template.

n To configure the services individually (DTR, CBS, CMS) ‒ for example, because you havedistributed the usage type DI to different servers ‒ perform the following steps:a) Choose the Scenario DIb) Choose the service you want to configure, Design Time Repository, Component Build Service, or

Change Management Service.c) Fill the open fields in the section Data Entry according to their label.d) To run the configuration task, choose Execute Task.e) Choose the items that you need from Design Time Repository Configuration, Component Build Service,

and Change Management Service.

08/31/2007 PUBLIC 129/176



5 Post-Installation5.20 Checking the SAP Java Documentation

Note

Before performing any database settings make sure that you have read SAP Note 889038.

3. If you are using a new Oracle database installation, perform the step Set Oracle Parameters for DI.

Caution

Do not use this for an already configured database because it overwrites previous settings.

4. After the Configuration Wizard has finished, you have to restart the engine as described in SAPNote 919942.


Only valid for: Mobile Infrastructure (MI)

Usage Type: Mobile InfrastructureAfter SAPinst has finished, you need to run the configuration task MI Post Installation Process

using the Configuration Wizard.End of: Mobile Infrastructure (MI)

End of: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Mobile Infrastructure (MI);Process

Integration (PI)

5.20 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 the following place in the documentation:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Application

Platform by Key Capability Java Technology .2. Check the following documentation for information relevant to running your Java system:

130/176 PUBLIC 08/31/2007






5 Post-Installation5.20 Checking the SAP Java Documentation

Manual Contents

Architecture Manual This manual describes the architecture of a Java or ABAP+Java system. Itcontains information on:n Java cluster architecture including central services, load balancing,

and high availability.n 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.

Administration Manual This manual describes how to administer the SAP system, focusing on theJ2EE Engine. It contains information on:n System landscape administrationn Software life-cycle management

NoteThis part of the manual contains important information about:l 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 Studio,which is the SAP Java development environment.

Migration Manual This manual contains all the information you need to migrate anapplication created in J2EE Engine 6.20.

More InformationFor troubleshooting the J2EE Engine, see the J2EE Engine Problem Analysis Guide at:

08/31/2007 PUBLIC 131/176

5 Post-Installation5.21 Accessing Configuration Documentation in the SAP Solution Manager

http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution LifeCycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) J2EE Engine ProblemAnalysis Scenarios

5.21 Accessing Configuration Documentation in the SAPSolution Manager

To access configuration documentation in the SAP Solution Manager, you have to connect yournewly-installed SAP system to the SAP Solution Manager.

Note

For SAP NetWeaver 7.0 usage types you can also find configuration documentation in the TechnologyConsultant’s Guide at: http://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’sGuide

Prerequisites

n You have installed an SAP Solution Manager system as described in the documentation InstallationGuide ‒ SAP Solution Manager <3.2 or 4.0> on <OS>: <Database>.

n You have connected your SAP system to the SAP Solution Manager as described in thedocumentation Configuration Guide ‒ SAP Solution Manager <3.2 or 4.0>.

You can find these documentations on SAP Service Marketplace athttp://service.sap.com/instguides SAP Components SAP Solution Manager Release <3.2 or

4.0> .

Procedure

1. Log on to your SAP Solution Manager system.2. To be able to access configuration documentation, create a project as follows:

a) Create your project with transaction SOLAR_PROJECT_ADMIN for project administration.b) Connect your SAP system to the SAP Solution Manager with transaction SMSY for the SAP

Solution Manager system landscape.c) Create a project structure and add the required scenarios for your SAP system to your project

structure with the Business Blueprint transaction SOLAR01,d) Add your SAP system configuration structures to your project structure with the configuration

transaction SOLAR02.For more information about creating projects, assigning scenarios to projects, and creatingconfiguration structures, see:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life

Cycle Management SAP Solution Manager Using the SAP Solution Manager in Projects

132/176 PUBLIC 08/31/2007













5 Post-Installation5.21 Accessing Configuration Documentation in the SAP Solution Manager

3. Go to the project structure folder <project name> using transaction SOLAR02.4. Access configuration documentation for SAP NetWeaver usage types at Configuration Structure

SAP NetWeaver 7.0 (2004s) .

ResultYou can now configure your SAP system according to the configuration documentation in theSAP Solution Manager.

08/31/2007 PUBLIC 133/176

6 Additional Information

6 Additional Information

The following sections provide additional information about optional preparation andpost-installation tasks.There is also a section describing how to delete an SAP system.

Preparation

n Installation of Multiple Components in One Database [page 135]n Integration of LDAP Directory Services [page 137]

Post-Installation

n Starting and stopping the SAP system [page 140].n If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access

[page 147].n Configuring User Management to Use an LDAP Directory [page 148].n Usage Type-Specific Initial Technical Configuration [page 148]n Heterogeneous SAP System Installation [page 158]n Troubleshooting [page 159]

Deleting an SAP System

n Deleting an SAP System [page 161]

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

Example

You install an SAP NetWeaver central system and an SAP CRM central system in a single database.

08/31/2007 PUBLIC 135/176

6 Additional Information6.1 Installation of Multiple Components in One Database (Optional)

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-independentsolutions.Using 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 installation.With 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 on MCOD and its availability on different platforms, see the SAP ServiceMarketplace at https://service.sap.com/mcod.

n MCOD is released for Unicode installations. A prerequisite is that the MCOD system containsUnicode 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. The same applies to memory resources and disk space.You 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 on the SAPQuick Sizer, see the SAP Service Marketplace at https://service.sap.com/sizing.

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.

136/176 PUBLIC 08/31/2007

https://service.sap.com/mcod



https://service.sap.com/sizing



6 Additional Information6.2 Integration of LDAP Directory Services (Optional)

Constraints

Recommendation

We strongly recommend that you test MCOD in a test or development system.We 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 affected.n Automated support in an MCOD landscape for the following administrative tasks depends on

your operating system and database:l Copying a single component from an MCOD landscape to another database at database level.l 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 https://service.sap.com/remoteconnection.

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 database.n For the second SAP system, you must use the same DBSID as for the first SAP system.n 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.

6.2 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 directory.LDAP 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 inconsistency.If 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.

08/31/2007 PUBLIC 137/176

https://service.sap.com/remoteconnection




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 at:http://help.sap.com <your product> SAP NetWeaver Library SAP NetWeaver by Key Capability

Security 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 at:http://service.sap.com/msplatforms Microsoft Windows Server

For more information about the SAP MC and about how to configure it to access LDAP Directories,see the documentation SAP Management Console on SAP Service Marketplace at:http://help.sap.com SAP Library SAP NetWeaver Library SAP NetWeaver by Key Capability

Application Platform by Key Capability Java Technology Administration Manual J2EE Engine J2EE EngineAdministration Tools SAP Management Console

138/176 PUBLIC 08/31/2007

http://help.sap.com

http://service.sap.com/msplatforms



http://help.sap.com


SAP Logon

Instead of using a fixed list of systems and message servers, you can configure the SAP Logon in thesapmsg.ini 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 systems.To use LDAP operation mode, make sure that the sapmsg.ini 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=“DirType=NT5ADS”. For moreinformation, see the SAP system profile parameter ldap/options.

n You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either ofthe following is true:l 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 ldap/servers.

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 ldap/saproot.

SAP MMC

The SAPMMC is a graphical user interface (GUI) for administering andmonitoring SAP systems froma central location. If the SAP system has been prepared correctly, the SAP MMC presents and analyzessystem information that it gathers from various sources, including the Active Directory.Integrating the Active Directory as a source of information has advantages for the SAP MMC. It 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 status,and parameter settings is always available in the SAP MMC.If you need to administer distributed systems, we especially recommend that you use the SAP MMCtogether with Active Directory services. For example, you can simplify administration by using theSAP MMC in a distributed environment that implements the mySAP Business Suite components.You can keep track of significant events in all of the systems from a single SAP MMC interface. Youdo not need to manually register changes in the system configuration. Instead, such changes areautomatically updated in the directory and subsequently reflected in the SAP MMC.

08/31/2007 PUBLIC 139/176

6 Additional Information6.3 Starting and Stopping the SAP System

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 the Generic LDAP Directory.Integrating the Generic LDAP Directory as a source of information has advantages for the SAP MC.It can read system information straight from the directory that automatically registers changes tothe system landscape. As a result, up-to-date information about all SAP application servers, theirstatus, and parameter settings is always available in the SAP MC.

Configuration Tasks for Active Directory

To enable an SAP system to make use of the features offered by the Active Directory, you mustconfigure the Active Directory so that it can store SAP data.This involves extending the schema for the SAP data types, creating a root container for the storage ofSAP-specific information, and defining accounts that allow directory access. You perform all thesetasks using SAPinst with the option Active Directory Configuration.For more information, see section Setting Up the Active Directory Services (Optional) in the Windowsinstallation guide for your SAP system solution and database.

Configuration Tasks for Generic LDAP Directories

To configure generic LDAP directories, refer to the documentation of your directory vendor.

6.3 Starting and Stopping the SAP System

You can start and stop the SAP system by using one of the following:

n The SAP Management Console (MC) [page 140]n The startsap and stopsap scripts [page 144]

6.3.1 Starting and Stopping the SAP System Using the SAPManagement Console

You can start and stop all SAP system instances using the SAP Management Console (MC) exceptthe database instance. You have to start and stop the database instance as described in Starting andStopping the SAP System Using startsap and stopsap [page 144].

140/176 PUBLIC 08/31/2007


Note

If your newly installed SAP system is part of a heterogeneous SAP system landscape that comprisessystems or instances on Windows platforms, you can also start and stop it from a Windows system orinstance using theMicrosoft Management Console (MMC).For more information about handling the MMC, see:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life

Cycle Management by Key Capability Solution Monitoring Monitoring in the CCMS Microsoft ManagementConsole: Windows

Prerequisites

n Make sure that the host on which you want to start SAP MCmeets the following requirements:l Java Runtime Environment (JRE) 5.0 is installed.l The browser supports Java.l The browser’s Java plug-in is installed and activated.

n You have logged on to the host as user <sapsid>adm.

Starting the Web-Based SAP Management Console

1. Start a Web browser and enter the following URL:http://<hostname>:5<instance_number>13

Example

If the instance number is 53and the host name is saphost06, you enter the following URL:http://saphost06:55313

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 Start.The SAP Management Console appears.By default, the instances installed on the host you have connected to are already added in the SAPManagement Console. If you want to change the configuration to display systems and instanceson other hosts, see Registering Systems and Instances below.

08/31/2007 PUBLIC 141/176



Starting and Stopping Systems and Instances

Starting an SAP System or Instance

1. In the navigation pane, open the tree structure and navigate to the system node that you want tostart.

2. Select the system or instance and then, from the context menu, choose Start.3. In the Start SAP System(s) dialog box, choose the required options.4. Choose OK. The SAP MC starts the specified system or system instances.

Note

The system may prompt you for the SAP system administrator credentials. To complete theoperation, you must have administration permissions. Log in as user <sapsid>adm.

Starting Instances Separately

If you need to start the instances of an SAP system separately, for example when you want to start adistributed or a high-availability system, proceed in the following sequence:

1. Start the database instance.2. Start the central services instance SCS<Instance_Number>.


If your system is a high-availability system, you first start the ABAP central servicesinstance ASCS<Instance_Number> and then you start the Java central services instanceSCS<Instance_Number>.End of: HA (UNIX)

3. Start the central instance DVEBMGS<Instance_Number>.4. Start dialog instance(s) D<Instance_Number> if there are any.

Stopping an SAP System or Instance

1. Select the system or instance you want to stop and choose Stop from the context menu.2. In the Stop SAP System(s) dialog box, choose the required options.3. Choose OK. The SAP MC stops the specified system or system instances.

Note

The system may prompt you for the SAP system administrator credentials. To complete theoperation, you must have administration permissions. Log in as user <sapsid>adm.

Similarly, you can start, stop or restart all SAP systems and individual instances registered in theSAP MC.

142/176 PUBLIC 08/31/2007


Stopping Instances Separately

If you need to stop the instances of an SAP system separately, for example when you want to start adistributed or a high-availability system, proceed in the following sequence:

1. Stop dialog instance(s) D<Instance_Number> if there are any.2. Stop the central instance DVEBMGS<Instance_Number>.3. Stop the central services instance SCS<Instance_Number>.


If your system is a high-availability system, you first stop the Java central servicesinstance SCS<Instance_Number> and then you stop the ABAP central services instanceASCS<Instance_Number>.End 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

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 theSystem’s 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 Individual Instances

1. In the SAP MC, choose File New .2. In the New System dialog box, enter the required data and deselect Always show all SAP Instances.3. The SAP MC displays the SAP system node, the instance node and the relevant database node in

a tree view in the navigation pane.

08/31/2007 PUBLIC 143/176


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 startup:1. In the Settings dialog box, select History.2. In the right-hand side pane, choose the instance you want the SAP MC to display on startup.3. Choose the << button.4. Choose Apply and then choose OK.Similarly, you can remove instances from the startup configuration.

n You can save the current configuration in a file:1. Choose File Save Landscape .2. In the Save dialog box, enter the required data.3. Choose Save.

n You can load a configuration from a file:1. Choose File Load Landscape .2. In the Open dialog box, select the configuration you want to load.3. Choose Open.

More InformationFor more information about the SAP Management Console, see:http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Application

Platform by Key Capability Java Technology -> Administration Manual J2EE Engine J2EE Engine AdministrationTools SAP Management Console

6.3.2 Starting and Stopping the SAP System Using startsapstopsap Scripts

You can start and stop the SAP system by running the startsap and stopsap scripts in the exedirectory.

Prerequisites

n You have checked the default profile /<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameterlogin/system client and set the value to the correct productive system client. For example, theentry must be login/system_client = 001 if your productive 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 <sapsid>adm.

144/176 PUBLIC 08/31/2007




n For more information about how to start or stop database-specific tools, see the database-specificinformation in this documentation and the documentation from the database manufacturer.

n If you want to use startsap or stopsap (for example, in a script) and require the fully qualifiedname of these SAP scripts, create a link to startsap or stopsap in the home directory of thecorresponding user.

Caution

If there aremultiple SAP instances on one host ‒ for example, a central instance and a dialoginstance ‒ you must add an extra parameter to the scripts:startsap <instanceID>

stopsap <instanceID>

For example, enter:startsap DVEBMGS00

Note

The instance name (instance ID) of the central instance is DVEBMGS<Instance_Number>, theinstance name of the central services instance is SCS<Instance_Number>, and the instance nameof a dialog instance is D<Instance_Number>.


The instance name of the ABAP central services instance is ASCS<Instance_Number>.End of: HA (UNIX)

Procedure

Starting the SAP system

n To start all instances on the central system host, enter the following command:startsap

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 commands:startsap DB

startsap R3 <instance ID of central services instance>

startsap R3 <instance ID of central instance>

startsap R3 <instance ID of dialog instance>

Make sure that you always start the database first because otherwise the other instances cannotstart.

08/31/2007 PUBLIC 145/176


Note

You can also use the parameter J2EE, which is a synonym for the parameter R3.For 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 follows:1. On the database host, enter:

startdb

2. On the central services and on the central instance host, enter:startsap

3. For dialog instance(s) enter the following on the relevant host:startsap R3 <instance ID of dialog instance>

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 the SAP System

Note

When you use stopsap in a Multiple Components in One Database (MCOD) systemwith two centralinstances, only one central instance and the database are shut down. Therefore, you must first stopthe other SAP system with stopsap R3 or make sure that it has already been stopped.For more information, see Installation of Multiple Components in one Database [page 135].

n If you have a central system, enter the following to stop all instances on the central system host:stopsap

This stops the central instance, central services instance, and database.

Note

You can stop the database and SAP system separately by entering the following commands:stopsap R3 <instance ID of dialog instance>

stopsap R3 <instance ID of central instance>

stopsap R3 <instance ID of central services instance>

stopsap DB

Make sure that you always stop the central instance first and the central services instance secondbecause otherwise the database cannot be stopped.

146/176 PUBLIC 08/31/2007

6 Additional Information6.4 Creating a User for LDAP Directory Access (Optional)

Note

You can also use the parameter J2EE, which is a synonym for the parameter R3.For 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 follows:1. On the dialog instance host, enter the following command:

stopsap <instance ID of dialog instance>

2. To stop the central services instance on the central services and on the central instance host,enter the following command:stopsap

3. To stop the database, enter the following command on the database host:stopdb

Caution

Make sure that no SAP instance is running before you enter stopdb on a standalone database server.No automatic check is made.

6.4 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 directory.For 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 <sapsid>adm.2. Enter:

ldappasswd pf=<path_and_name_of_instance_profile>

3. Enter the required data.

Example

The following is an example of an entry to create an LDAP Directory User:CN=sapldap,CN=Users,DC=nt5,DC=sap-ag,DC=de

08/31/2007 PUBLIC 147/176

6 Additional Information6.5 Configuring User Management to Use an LDAP Directory (Optional)

6.5 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 installation.For more information, see:https://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Security

Identity Management User Management Engine UME Configuration UME Data Sources LDAP Directory asData Source Configuring UME to Use an LDAP Server as Data Source

6.6 Usage Type-Specific Initial Technical Configuration

SAPinst performs initial technical configuration steps for the usage types shown below during theinstallation.However, 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 types:l 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 149]

n


Development Infrastructure (DI) [page 151]End of: Development Infrastructure (DI)

n


EP Core (EPC) and Enterprise Portal (EP) [page 153]End of: Enterprise Portal (EP);EP Core (EPC)

n


Business Intelligence (BI Java) [page 157]End of: BI Java Components (BI-Java)

148/176 PUBLIC 08/31/2007





6 Additional Information6.6 Usage Type-Specific Initial Technical Configuration

n


Process Integration (PI) [page 154]End of: Process Integration (PI)

6.6.1 Initial Technical Configuration for the ApplicationServer Java (AS Java)

SAPinst performs initial technical configuration steps for the AS Java components listed below duringthe installation.However, you might have to perform some of these steps manually after SAPinst has finished,depending on your installation scenario.For more information, see the following sections:

n Adobe Document Services (ADS) [page 149]n Composite Application Framework (CAF) [page 150]n System Landscape Directory (SLD) [page 151]

6.6.1.1 Initial Technical Configuration for Adobe DocumentServices

SAPinst automatically performs some initial technical configuration steps for Adobe DocumentServices (ADS) 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 parameters.SAPinst performs the following steps:

n SAPinst creates user ADSUser in AS ABAP for basic authentication and assigns it to groupADSCallers.For more information about this user, see Ensuring User Security [page 123].

n SAPinst 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 123].

n SAPinst creates service user ADS_AGENT in the ABAP Environment.n SAPinst creates an ABAP connection for basic authentication.

n SAPinst creates destination service FP_ICF_DATA_<SAPSID>.n SAPinst sets up basic authentication in the Java environment.

You can find a detailed description of how to perform these steps manually in the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’s Guide Business Task

Management Adobe Document Services (Configuration) Adobe Document Services Configuration Guide Configuringthe Web Service Securing Access to the Web Service Configuration of the Web Service for Basic Authentication .

08/31/2007 PUBLIC 149/176





More InformationThe document Adobe Document Services Configuration Guide is also available in PDF form on SAP ServiceMarketplace athttp://service.sap.com/adobe SAP Interactive Forms by Adobe Media Library Documentation Adobe

Document Services - Configuration Guide NW 7.0 (2004s)

6.6.1.2 Initial Technical Configuration for CompositeApplication Framework Core (CAF)

SAPinst automatically performs some initial technical configuration steps for Composite ApplicationFramework Core (CAF) 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 parameters.SAPinst performs the following steps:

n SAPinst creates the following roles with the required User Management Engine (UME) actions:

l CAFAdmin

l CAFUIAdmin

You can find a detailed description of how to perform these steps manually in the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’s Guide Developing,

Configuring, and Adapting Applications Creating Composite Applications Composite Application Framework CoreConfiguration Guide Setting Up Roles .

n SAPinst configures CAF runtime properties for Business Warehouse (BW) integration.You can find a detailed description of how to perform these steps manually in the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’s Guide Developing,

Configuring, and Adapting Applications Creating Composite Applications Composite Application FrameworkCore Configuration Guide Configuring CAF Core for BW Integration Configuring CAF Runtime Properties forBW Integration .

n SAPinst configures CAF runtime properties for knowledge management integration.You can find a detailed description of how to perform these steps manually in the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’s Guide Developing,

Configuring, and Adapting Applications Creating Composite Applications Composite Application Framework CoreConfiguration Guide Configuring CAF Core for Knowledge Management Integration Configuring CAF RepositoryManagers Configuring CAF Runtime Properties .

n SAPinst creates data sources to extract custom enumeration types.You can find a detailed description of how to perform these steps manually in the SAP Libraryat http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver Developer’s GuideFundamentals Creating Composite Applications Developing Composite Applications with CAF Core IntegrationCAF Core and SAP Business Information Warehouse Integration DataSources to Extract Custom Enumeration TypesDataSources to Extract Custom Enumeration Types .

150/176 PUBLIC 08/31/2007

















6.6.1.3 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 parameters.SAPinst performs the following steps:

n SAPinst configures SLD security roles.n SAPinst configures server and persistence parameters.n SAPinst performs the initial data import.n SAPinst configures the SLD bridge.

You can find a detailed description of how to perform these steps manually in the documentationPost Installation Guide ‒ System Landscape Directory of SAP NetWeaver 7.0 on SAP Service Marketplace athttp://service.sap.com/installNW70 Installation Configuration .

More Information

n For more information on working with and configuring the the SLD, see the SAP Libraryat http://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key CapabilitySolution Life Cycle Management by Key Capability Software Life Cycle Management System LandscapeDirectory . (This documentation is also available in PDF form on SAP Service Marketplace athttp://service.sap.com/sld System Landscape Directory Media Library Documentation System

Landscape Directory ).n For more information on security and on the role concept in the SLD, see the SAP Library at

http://help.sap.com/nw70 SAP NetWeaver Library Administrator’s Guide SAP NetWeaver SecurityGuide Security Aspects for System Management Security Guide for the SAP System Landscape Directory .


6.6.2 Initial Technical Configuration for DevelopmentInfrastructure (DI)

SAPinst automatically performs some initial technical configuration steps for usage type DevelopmentInfrastructure (DI) during the installation.

08/31/2007 PUBLIC 151/176














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 or

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 on these NWDI users, see the NWDI Users table in Ensuring User Security[page 123].

n SAPinst creates the following roles:

l NWDI.Administrator

l NWDI.Developer

n SAPinst adds the following actions to the NWDI.Administrator role:

l CBS.Administrator

l sap.com_com.sap.lcr.LcrInstanceWriterAll

n SAPinst adds the following actions to the NWDI.DEVELOPER role:

l CBS.Developer

l CMS.Display

l CMS.Export

l sap.com_com.sap.lcr.LcrInstanceWriterNR

n SAPinst creates the following groups:

l NWDI.Administrators

l NWDI.Developers

n SAPinst assigns the LcrInstanceWriterAll security role of the sap.com/com.sap.lcr*sldcomponent to the NWDI.Administrators group

n SAPinst assigns the LcrInstanceWriterNR security role of the sap.com/com.sap.lcr*sldcomponent to the NWDI.Developers group

n SAPinst assigns the NWDI.Administrator role to the NWDI.Administrators group.n SAPinst assigns the NWDI.Developer role to the NWDI.Developers group.n SAPinst assigns the NWDI.Administrators group to the NWDI_ADM user.n SAPinst assigns the NWDI.Developers group to the NWDI_DEV user.n SAPinst assigns the NWDI.Administrators group to the NWDI_CMSADM user.

You can find a detailed description of how to perform these steps manually in the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver Library Technology Consultant’s Guide Developing,

Configuring, and Adapting Applications Post Installation Steps of Usage Type DI Setting Up Privileges, Roles andGroups .

152/176 PUBLIC 08/31/2007






For more information on how to create and assign users, groups and roles, see the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver Library SAP NetWeaver by Key Capability Security

Identity Management Identity Management of the Application Server Java Administration of Users and RolesManaging Users, Groups, and Roles .End of: Development Infrastructure (DI)


6.6.3 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 EP.SAPinst automatically performs some initial technical configuration steps for the usage types EPC andEP during the installation.However, 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 You want to change existing parameters or if you want to set additional parameters.

SAPinst performs the following steps:

n SAPinst copies the CMS_MAPPING Properties file.n SAPinst renames the InitialPermissions.xml.template file to initialPermissions.xml.n SAPinst renames the initialPermissionsKMC.xml.template file to initialPermissionsKMC.xml.

Copying CMS_MAPPING Properties

1. Change to the following source directory/usr/sap/<sapsid>/<instance_name>/j2ee/cluster/server<x>/apps/sap.com/irj/

servlet_jsp/irj/root/WEB-INF/portal/system/pcd/Migration/mapping/

2. Copy filecms_mapping.properties from the source directory to the following target directory:/usr/sap/<sapsid>/SYS/global/pcd/Migration/mapping/.

Note

If the target directory does not exist, you have to create it as well.

Renaming InitialPermissions.xml.template

1. Go to directory/usr/sap/<sapsid>/<instance_name>/j2ee/cluster/server<x>/apps/sap.com/irj/

servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl .

08/31/2007 PUBLIC 153/176






2. Rename file initialPermissions.xml.template to initialPermissions.xml.

Renaming initialPermissionsKMC.xml.template

1. Go to directory/usr/sap/<sapsid>/<instance_name>/j2ee/cluster/server<x>/apps/sap.com/irj/

servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl

2. Rename file initialPermissionsKMC.xml.template to initialPermissionsKMC.xml.



6.6.4 Initial Technical Configuration for Process Integration(PI)

SAPinst automatically performs PI-specific initial technical configuration steps during the installation.However, you might have to perform some of these steps manually if:

n You upgraded your SAP system to NetWeaver 7.0 SR3.n 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 154]n Assign SAP_ALL Rights to User PISUPER [page 155]n Activate the ICF Services [page 156]n Assign roles to groups [page 156]n Run the configuration template installer for usage type PI [page 127]

6.6.4.1 Importing the SAP Exchange Profile

Note

If SAPinst has finished successfully, the exchange_profile.xml file does not exist on your system.In this case, you can skip this step.

Procedure

1. On your PI server host, open the following URL:http://<J2EE_host>:<J2EE_Port>/exchangeProfile

The following naming convention applies for <J2EE_Port>:5<J2EE_instance_number>00

154/176 PUBLIC 08/31/2007



50000, for example, if your J2EE instance is 002. Enter the logon information:

User Name: PISUPERPassword: <pisuper_password>The Exchange Profile page appears

3. Choose Connection.The Server Settings page appears.

4. Enter the required information for the PI host.Use the logon information of user PILDUSER.

5. Choose Save.The Exchange Profile page appears.

6. Choose Import.The Import Profile page appears.

7. Choose Browse and select the following file:/usr/sap/<SAPSID>/SYS/global/exchange_profile.xml

Caution

If you cannot run aWeb Browser on your PI host, you need to copy the file exchange_profile.xmlfrom the PI host to a host were a Web browser runs.

8. Choose Import Data.The profile will be imported.

Caution

As the file exchange_profile.xml contains secure information like passwords, we highlyrecommend that you delete the file after importing or to save it by using high security standards,such as encryption.

6.6.4.2 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 SU01.3. Select user PISUPER.4. Navigate to the Profiles tab and switch to edit mode.5. In the row Profile, add SAP_ALL.6. Save your settings.

08/31/2007 PUBLIC 155/176


6.6.4.3 Activating the ICF Services

The Internet Communication Framework (ICF) is a 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.

6.6.4.4 Assigning Roles to Groups

To assign the roles to the different groups, start the Visual Administrator of the J2EE Engine.

Assigning Role "Administer" to Group SAP_XI_ADMINISTRATORCheck whether group SAP_XI_ADMINISTRATOR is assigned to role administer.If this is not the case, proceed as follows:

1. Choose Cluster Server Services Security Provider sap.com.\com.sap.rprof.remoteprofileexchangeprofile .2. Select Security Roles.3. Select Administer.4. Select the group SAP_XI_ADMINISTRATOR.5. Choose Add and assign the role administer.6. Save your settings.

Assigning Security Role "LcrAdministrator" 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 sap.com/com.sap.lcr*sld.4. On the right, choose Security Roles and select the role LcrAdministrator.5. Select the role type Security Role.6. In the lower frame, add group SAP_SLD_ADMINISTRATOR.


156/176 PUBLIC 08/31/2007




6.6.5 Initial Technical Configuration for BI Java

SAPinst automatically performs BI Java-specific initial technical configuration steps during theinstallation.However, you might have to perform some of these steps manually if:

n You upgraded your SAP system to NetWeaver 7.0 SR3.n You have installed usage type BI Java as an additional usage type to an existing SAP system as

described in SAP Note 883948.

The following steps might be affected:

n Configure BI Java Information Broadcasting [page 157]n Process Chains: Transport texts for alert category [page 158]n Rename initialPermissionsBI.xml.template [page 158]n Run the configuration template installer for usage type BI Java [page 127]

6.6.5.1 Configuring BI Java Information Broadcasting

For the configuration of the BI Information Broadcasting you need to performt the following stepsin your ABAP system:

1. Call transaction SPRO and perform the following steps:a) Settings for Information Broadcasting:

Go to SAP NetWeaver Business Intelligence Reporting-relevant Settings Settings for InformationBroadcasting

b) Destinations for Web Dynpro ALV:Go 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 successfully.If the installation status is red, restart the installation by calling transaction RSTCO_ADMIN again.Check the installation log if you need further assistance or information.For more information, see SAP Note 834280.

08/31/2007 PUBLIC 157/176



6 Additional Information6.7 Heterogeneous SAP System Installation

Note

For the installation of SAP NetWeaver 7.0 BI Content Add-On 2 or higher on the AS ABAP system,see SAP Note 847019.

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

6.6.5.3 Renaming initialPermissionsBI.xml.template

If SAPinst does not rename the initialPermissionsBI.xml.template file automatically, you willneed to rename it yourself.

Procedure

1. Go to directory/usr/sap/<sapsid>/JCxx/j2ee/cluster/server<x>/apps/sap.com/irj/

servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl

2. Rename file initialPermissionsBI.xml.template to initialPermissionsBI.xml.


6.7 Heterogeneous SAP System Installation

This documentation describes how to install SAP instances in a heterogeneous UNIX environment,which is where you:

n Run instances on different UNIX platformsn Mix 32-bit instances and 64-bit instances in one landscape

158/176 PUBLIC 08/31/2007



6 Additional Information6.8 Troubleshooting

Note

See SAP Note 1067221 for information on

n supported combinations of operating systems and database systems

n installing an application server on Windows in a heterogeneous (UNIX) SAP system environment(ABAP, Java, or ABAP+Java) with SAPinst.

n Java EE engine installation on heterogeneous architectures

n heterogeneous Unix - Unix Systems

ProcedureProceed as follows to store the SAP executables locally:

1. Install the central instance and the database as described in the installation documentation.2. Log on as user root on the dialog instance host.3. Create <sapmnt>/<SAPSID>/exe as a local directory on the dialog instance.4. On the central instance host, export the directories <sapmnt>/<SAPSID>/global and

<sapmnt>/<SAPSID>/profile via NFS and mount them on each dialog instance host as describedin Preparing and Mounting the Installation Media [page 73].

5. Mount the CD or DVD drive using NFS and insert the CD / DVD with the SAP executables on thedialog instance host.

6. Install the dialog instance.

6.8 Troubleshooting

The following section(s) describe the steps that you need to performmanually if SAPinst fails:

n Troubleshooting with SAPinst [page 159]

n


Troubleshooting for Portal Installation [page 160]End of: Enterprise Portal (EP);EP Core (EPC)

6.8.1 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.If 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 Logs.

08/31/2007 PUBLIC 159/176


6 Additional Information6.8 Troubleshooting

2. If an error occurs during the dialog or processing phase, do either of the following:n Try to solve the problemn Abort the installation with Exit

For more information, see Interrupted Installation with SAPinst [page 93].n Continue the installation by choosing Retry.

3. Check the log and trace files of the GUI server and SAPinst GUI in the directory<user_home>/.sdtgui/ for errors.

4. If SAPinst GUI does not start, check the file sdtstart.err in the current <user_home> directory.5. If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as

described in Starting SAPinst GUI Separately.6. Ignore error messages such as the following in the SDM logs:

Error: <SCA name>: Location of software component ’<SCA name>’ / <SCA vendor>’

/ ’<SCA location>’ / ’<SCA counter> ’ unknown./ Error: <SCA name> : system

component version store not updated.

For more information, see SAP Note 828978.


6.8.2 Troubleshooting for Portal Installation

This section applies both when you install usage type EPC only and when you install it togetherwith usage type EP.If the iViews are not displayed correctly, or if the portal does not launch, the reason might be that theportal was not deployed completely.To check the deployment of the portal, proceed as follows :

Procedure

1. Open a new console with the user <sapsid>adm.2. Go to the directories deployment, pcd, and pcdContent, in the following paths:

n /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/cluster/server0/

apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment


apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd


apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent


apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/

pcdContent/no_overwrite

3. Look for files with the extension *.err.4. Do one of the following:

160/176 PUBLIC 08/31/2007


6 Additional Information6.9 Deleting an SAP System

n If error and log files do not appear, the portal installation has been completed successfullyand you can continue.

n Rename the *.err files:a) Remove the err extension; so the extensions of the files become *.ept or *.par.b) Restart the J2EE Engine, using the commands stopsap and startsap, to change the files

to *.bak.


6.9 Deleting an SAP System

The following sections describe how to delete an SAP system.

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 161]. However, you still have to delete the databasemanually.

n You delete the SAP system manually [page 164].

6.9.1 Deleting an SAP System Using SAPinst

You can use SAPinst to delete an SAP system.

Caution

SAPinst only stops local instances automatically.Before 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 run.1. Run SAPinst to delete the SAP system.2. Delete the Oracle database software [page 163] 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 sequence:1. Dialog instance(s), if there are any2. Database instance

08/31/2007 PUBLIC 161/176


SAPinst deletes the database instance but you have to delete the Oracle database software [page 163]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 users,groups, or service entries, make sure that they are no longer required.

Caution

When you delete an SAP system using SAPinst, system directories mounted from an NFS serverare not deleted.You must either delete them manually [page 164] or run SAPinst on the NFS server.

6.9.1.1 Running SAPinst to Delete an SAP System

This procedure tells you how to run the Uninstall service of SAPinst.

Prerequisites

n You are logged on as user root.n 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 -k.If there are other SAP systems on the host, log on as user <sid>adm of the other SAP system andstart saposcol from there using the command saposcol -l.

Procedure

1. Start SAPinst and on theWelcome screen, choose:<SAP System> Additional Software Life-Cycle Tasks Uninstall Uninstall System / Standalone Engine /

Optional Standalone Unit

Note

With this SAPinst service you do not delete the database software.

2. Follow the instructions in the SAPinst input dialogs.

162/176 PUBLIC 08/31/2007


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 delete.Make sure that you delete the SAP instances in the correct order, as described in Deleting an SAPSystem Using SAPinst [page 161].

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.

3. Delete the database software manually [page 163].4. If required, you can delete the directory /usr/sap/trans and its content manually.

SAPinst does not delete /usr/sap/trans because it might be shared.

6.9.1.2 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 SAPinst.If you delete your SAP system manually, you delete the Oracle database instance as described inDeleting an Oracle Database Instance [page 169].

Procedure

1. Start the OUI with the user ora<dbsid> as follows:n For 32-bit systems, enter the following:


./runInstaller



./runInstaller


./runInstaller

08/31/2007 PUBLIC 163/176


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

2. Choose Installed Products or Uninstall Products.

3.

Only valid for: SAP CRM 5.0;SAP CRM 5.1;SAP SCM 5.0;SAP SRM Server 5.5

Select the database schema you want to uninstall, <DBSID>_102_32 or <DBSID>_102_64.End of: SAP CRM 5.0;SAP CRM 5.1;SAP SCM 5.0;SAP SRM Server 5.5

4. Mark the Oracle 10G database within the selected product.5. Choose Remove.6. Confirm your selection with Yes.7. Choose EXIT.

6.9.2 Deleting an SAP System Manually

Deleting a Complete SAP System Manually

1. You delete the SAP instances [page 165] in the following sequence:a) Dialog instances, if there are anyb) 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 165].3. You delete the Oracle database instance [page 169].

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 167], if there are any.2. You delete the Java part of an SAP system [page 167].3. You delete the central services instance [page 165].4. You delete the Java database schema of your Oracle installation [page 168].

164/176 PUBLIC 08/31/2007


6.9.2.1 Deleting an SAP Instance

You use this procedure if you want to delete a single SAP instance or all instances of a 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 follows:a) Log on as user <sapsid>adm.b) Execute this command:

stopsap r3 <InstanceName>

2. Stop the sapstart service with the following command:sapcontrol -nr <InstanceNumber> -prot NI_HTTP -function StopService

3. Stop the saposcol process with the following command:saposcol -k

4. Remove the instance profiles as follows:rm /usr/sap/<SAPSID>/SYS/profile/<SAPSID>_<InstanceName>_<host_name>

rm /usr/sap/<SAPSID>/SYS/profile/START_<InstanceName>_<host_name>

Example

For example, enter the following commands:rm /usr/sap/C11/SYS/profile/START_D00_h0001

rm /usr/sap/C11/SYS/profile/C11_D00_h0001

5. Log on as user root and delete the local instance directory:rm -rf /usr/sap/<SAPSID>/<InstanceName>

6. Change to the directory /usr/sap, edit the file sapservices and delete the line that refers tothe instance to be deleted.

6.9.2.2 Deleting Installation Files, Directories, and Users ona 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.

08/31/2007 PUBLIC 165/176


Caution

If you are not deleting the entire SAP system (on all hosts), make sure that you do not delete files ordirectories that are used by other SAP instances by means of NFS mounts.

PrerequisitesYou must have deleted your SAP instance(s) as described in Deleting an SAP Instance [page 165].

Procedure

1. If the following directories are mounted with NFS, unmount them:/<sapmnt>/<SAPSID>/exe

/<sapmnt>/<SAPSID>/global

/<sapmnt>/<SAPSID>/profile

2. Tto delete directories, execute the following commands:rm -rf /usr/sap/<SAPSID>

rm -rf /<sapmnt>/<SAPSID>

3. Delete the local user <sapsid>adm, its home directory, and all subdirectories of the home directory.

Caution

Do not delete user <sapsid>adm 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 <sapsid>adm as described in your operating system documentation.b) If the home directory of the user was not deleted automatically in the previous step, execute

the following command to delete the directory:rm -rf <sapsid_adm_home>

Example

rm -rf /home/c11adm

4. Delete the user <sapsid>adm 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 /etc/services:a) Search for entries starting with sap

b) Check whether these entries are still required by other instances with the same or a different<SAPSID> on any server.

c) If not, start by generating a backup copy of the services file by entering the following command:

166/176 PUBLIC 08/31/2007


cp /etc/services /etc/services.sap

d) Delete superfluous entries from /etc/services.If 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 /usr/sap/sapservices.

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

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 users,groups, and service entries to be deleted are no longer required.

1. Stop the central services instance and all dialog instances of your SAP system:a) Log on to the corresponding instance host as user <sapsid>adm.b) Execute the following commands:n To stop the central services instance:

stopsap r3 <SCSinstanceName>

n To stop a dialog instance:stopsap r3 <DialogInstanceName>

2. Stop the J2EE Engine of the central instance:a) Log on to your SAP system.b) Call transaction SMICM.c) Choose Administration J2EE Instance (local) Send Hard Shutdown .

Note

You do not need to stop the central instance.

08/31/2007 PUBLIC 167/176


3. If lines beginning with the following parameters appear, delete these lines from the default profile,/usr/sap/<SAPSID>/SYS/profile/DEFAULT.PFL:j2ee/dbname =

j2ee/dbtype =

j2ee/dbhost =

j2ee/dbadminurl =

j2ee/scs/host =

j2ee/scs/system =

j2ee/ms/port =

4. If lines beginning with the following parameters appear, delete these linesfrom the central instance prole and from all dialog instance proles,/usr/sap/<SAPSID>/SYS/profile/<SAPSID>_<INSTANCE_NAME>_<host_name>:exe/j2ee =

exe/jlaunch =

rdisp/j2ee_start_control =

rdisp/j2ee_start =

rdisp/j2ee_timeout =

rdisp/j2ee_libpath =

rdisp/frfc_fallback =

jstartup/trimming_properties =

jstartup/instance_properties =

jstartup/protocol =

jstartup/vm/home =

jstartup/max_caches =

jstartup/release =

j2ee/dbdriver =

5. Delete the central services instance [page 165].6. Delete the Oracle Java database schema [page 168].7. Delete the following directories (<xx> is the central instance number):

n /usr/sap/<SAPSID>/DVEBMGS<xx>/SDM

n /usr/sap/<SAPSID>/DVEBMGS<xx>/j2ee

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

168/176 PUBLIC 08/31/2007


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 ora<dbsid>.2. Start sqlplus and connect to the database. Enter:

sqlplus /nolog

SQLPLUS>connect / as sysdba

3. Enter the following command to delete the database objects of the database schema:SQLPLUS> drop user SAP<SCHEMA_ID>DB cascade;

4. Enter the following command to get the file name of the corresponding data file in the file system:SQLPLUS> select file_name from dba_data_files where \

tablespace_name = ’PSAP<SCHEMA_ID>DB’;

5. Enter the following command to delete the tablespace of the database schema:SQLPLUS> drop tablespace PSAP<SCHEMA_ID>DB including contents;

6. Exit sqlplus:SQLPLUS> exit

7. Delete the data file of tablespace PSAP<SCHEMA_ID>DB from the file system

6.9.2.5 Deleting an Oracle Database Instance

This section describes how to delete an Oracle database that you have installed.

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.

08/31/2007 PUBLIC 169/176




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 ora<dbsid>.2. Start sqlplus and shutdown the database. Enter:

sqlplus /nolog

SQLPLUS> connect / as sysdba

SQLPLUS> shutdown immediate

SQLPLUS> exit

3. Kill the orasrv process if it is running:ps -ef | grep orasrv (note the process ID <PID>)kill —9 <PID>

4. Stop the listener process:lsnrctl stop

5. Use the uninstall functionality of the Oracle Universal Installer (OUI):a) Start the OUI with the user ora<dbsid> as follows:n For 32-bit systems, enter the following:


./runInstaller



./runInstaller


./runInstaller

You see a message that a response file is being generated. It might take several minutesbefore you see the OUI screen.

b) Choose Installed Products or Deinstall Products.c) Select the database schema you want to uninstall, <DBSID>_102_32 or <DBSID>_102_64.d) Mark the Oracle 10G database within the selected product.e) Choose Remove.f) Confirm your selection with Yes.g) Choose EXIT.

6. Log on as user root.7. Delete user ora<dbsid> along with its home directory and all subdirectories of this directory:

a) Delete UNIX user ora<dbsid> using the steps appropriate for your operating system.b) If the home directory of the user was not deleted automatically in the previous step, delete

this directory:

170/176 PUBLIC 08/31/2007


rm -rf <sapsid_adm_home>

Example

For example, enter:rm -rf /home/orac11

8. Delete user ora<dbsid> from group dba, if this was not done automatically in the previous step.If the group dba is now empty, delete the complete group using the steps appropriate for youroperating system.

9. Remove the directory /oracle/<DBSID> and sub-directoriesrm -rf /oracle/<DBSID>

10. If there are no other database instances with the same Oracle release installed on this host, removethe staging area directory:n 32-bit Oracle 10G: rm -rf /oracle/stage/102_32

n 64-bit Oracle 10G: rm -rf /oracle/stage/102_64

11. If there are no other Oracle instances on this host, remove the Oracle client software directorywith one of the following commands:n 32-bit Oracle 10G: rm -rf /oracle/client/102_32

n 64-bit Oracle 10G: rm -rf /oracle/client/102_64

08/31/2007 PUBLIC 171/176

Typographic Conventions

Example Description

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

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, http://www.sap.com

/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 titles,pushbutton 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 names,transaction 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

172/176 PUBLIC 08/31/2007

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks orregistered trademarks of IBM Corporation.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implementedby Netscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world. All other product and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specifications may vary.These 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 (V5.1beta [= 6.0 for E3]) and XSLT processor SAXON 6.5.2 fromMichael Kay (http://saxon.sf.net/), XSLT version 1.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressively prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified oraltered in any way.

08/31/2007 PUBLIC 173/176

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-transferrable, royalty-free license to use the STLport.org 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 that:n The conditions indicated in the above permissions notice are met;n The following copyright notices are retained when present, and conditions provided in accompanying

permission notices are met:Coypright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 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 “as is” withoutexpress or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes norepresentations about the suitability of this software for any purpose. It is provided “as is” without express orimplied warranty.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. Moscow Center for SPARC

174/176 PUBLIC 08/31/2007

makes no representations about the suitability of this software for any purpose. It is provided “as is” withoutexpress or implied warranty.Boris 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 notice.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. 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 included.All 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 rights.Technical 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 contract,due to the circumstances known to it at that point in time representing a typical transfer of the software.

C) In the case of Art. 4.2 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 5,000.

E) The Customer shall take adequate measures for the protection of data and programs, in particular by makingbackup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data andits recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided byobserving this obligation.

F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employeesor agents of SAP.

3. Adobe Document ServicesAdobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States and / or other countries. For information on Third Party software delivered withAdobe document services and Adobe LiveCycle Designer, see SAP Note 854621.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: https://service.sap.com/instguides

08/31/2007 PUBLIC 175/176


https://service.sap.com/instguides



SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2007 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

sap netweaver 7.0 sr2 abap+java on solaris: oracle · 2019-11-12 · public installationguide sap...

Documents