SAP NetWeaver 2004s SR2 Abapjavaaix Oracle

PUBLIC

Installation Guide

SAP NetWeaver 2004sSR2 ABAP+Java on AIX: 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)

Application Sharing Server (Optional Standalone Unit)

Target Audience

n Technology consultants

n System administrators

Document version: 1.0 ‒ 12/04/2006

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The information containedherein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPoint areregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,iSeries, pSeries, xSeries, zSeries, System i, System i5, Systemp, System p5, System x, System z, System z9, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,i5/OS, POWER, POWER5, POWER5+, OpenPower andPowerPC are trademarks or registered trademarks of IBMCorporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Readerare either trademarks or registered trademarks of AdobeSystems Incorporated in the United States and/or othercountries.

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 orregistered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarksor registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of SunMicrosystems,

Inc., used under license for technology invented andimplemented by 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 mentionedherein as well as their respective logos are trademarks or

registered trademarks of SAP AG in Germany and in severalother countries all over the world. All other productand service names mentioned are the trademarks of theirrespective companies. Data contained in this documentserves informational purposes only. National productspecifications may vary.

These materials are subject to change without notice.These materials are provided by SAP AG and its affiliatedcompanies (“SAP Group”) for informational purposesonly, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions withrespect to thematerials. The only warranties for SAP Groupproducts and services are those that are set forth in theexpress warranty statements accompanying such productsand services, if any. Nothing herein should be construed asconstituting an additional warranty.

This document was created using stylesheet 2006-06-15(V4.3) 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™. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product isonly to be used by SAP’s Support Services and may not bemodified or altered in any way.

Legal Software Terms

Terms for Included Open Source SoftwareThis SAP software contains also the third party opensource software products listed below. Please note that forthese third party products the following special terms andconditions shall apply.

1. This software was developed using ANTLR.

2. gSOAP

2/166 PUBLIC 12/04/2006

Part of the software embedded in this product is gSOAPsoftware. Portions created by gSOAP are Copyright(C) 2001-2004 Robert A. van Engelen, Genivia inc. AllRights Reserved.THE SOFTWARE IN THIS PRODUCT WAS IN PARTPROVIDED BY GENIVIA INC AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE ARE DISCLAIMED. INNO EVENT SHALL THE AUTHOR BE LIABLEFOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSEDAND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF SUCH DAMAGE.

3. SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingNeurottstrasse 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 usethe STLport.org C++ library (STLport) and itsdocumentation without fee.

B) By downloading, using, or copying STLport orany portion thereof Customer agrees to abideby the intellectual property laws, and to all ofthe terms and conditions of this Agreement.

C) The Customer may distribute binaries compiledwith STLport (whether original or modified)without any royalties or restrictions.

D) Customer shall maintain the followingcopyright and permissions notices on STLportsources and its documentation unchanged:Copyright 2001 SAP AG

E) The Customer may distribute original ormodified 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 inaccompanying permission notices are met:Coypright 1994 Hewlett-PackardCompanyCopyright 1996,97 Silicon GraphicsComputer Systems Inc.Copyright 1997 Moscow Center forSPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute andsell this software and its documentation forany purposes is hereby granted without fee,provided that the above copyright notice appearin all copies and that both that copyright noticeand this permission notice appear in supportingdocumentation. Hewlett-Packard Companymakes no representations about the suitabilityof this software for any purpose. It is provided“as is” without express or implied warranty.Permission to use, copy, modify, distribute andsell this software and its documentation for anypurpose is hereby granted without fee, providedthat the above copyright notice appear in allcopies and that both that copyright notice andthis permission notice appear in supportingdocumentation. Silicon Graphics makes norepresentations about the suitability of thissoftware for any purpose. It is provided “as is”without express or implied warranty.Permission to use, copy, modify, distribute andsell this software and its documentation forany purposes is hereby granted without fee,provided that the above copyright notice appearin all copies and that both that copyright noticeand this permission notice appear in supportingdocumentation. Moscow Center for SPARCmakes no representations about the suitabilityof this software for any purpose. It is provided“as is” without express or implied warranty.Boris Fomitchev makes no representationsabout the suitability of this software for anypurpose. This material is provided "as is", withabsolutely no warranty expressed or implied.Any use is at your own risk. Permission touse or copy this software for any purpose is

12/04/2006 PUBLIC 3/166

hereby granted without fee, provided the abovenotices are retained on all copies. Permissionto modify the code and to distribute modifiedcode is granted, provided the above noticesare retained, and a notice that the code wasmodified is included with the above copyrightnotice.Permission to use, copy, modify, distributeand sell this software and its documentationfor any purposes is hereby granted withoutfee, provided that the above copyright noticeappear in all copies and that both that copyrightnotice and this permission notice appear insupporting documentation. SAP makes norepresentations about the suitability of thissoftware for any purpose. It is provided with alimited warranty and liability as set forth in theLicense Agreement distributed with this copy.SAP offers this liability and warranty obligationsonly towards its customers and only referringto its modifications.

b) Support and MaintenanceSAP does not provide software maintenance for theSTLport. Software maintenance of the STLporttherefore shall be not included.All other services shall be charged according to therates for services quoted in the SAP List of Pricesand Conditions and shall be subject to a separatecontract.

c) Exclusion of warrantyAs the STLport is transferred to the Customer on aloan basis and free of charge, SAP cannot guaranteethat the STLport is error-free, without materialdefects or suitable for a specific application underthird-party rights. Technical data, sales brochures,advertising text and quality descriptions producedby SAP do not indicate any assurance of particularattributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall onlybe liable for damage, including unauthorizedoperation, if this (i) can be compensated underthe Product Liability Act or (ii) if caused due to

gross negligence or intent by SAP or (iii) if basedon the failure of a guaranteed attribute.

B) If SAP is liable for gross negligence or intentcaused by employees who are neither agents ormanagerial employees of SAP, the total liabilityfor such damage and a maximum limit on thescope of any such damage shall depend onthe extent to which its occurrence ought tohave anticipated by SAP when concluding thecontract, due to the circumstances known toit at that point in time representing a typicaltransfer of the software.

C) In the case of Art. 4.2 above, SAP shall notbe liable for indirect damage, consequentialdamage caused by a defect or lost profit.

D) SAP and the Customer agree that the typicalforeseeable extent of damage shall under nocircumstances exceed EUR 5,000.

E) The Customer shall take adequate measuresfor the protection of data and programs, inparticular by making backup copies at theminimum intervals recommended by SAP. SAPshall not be liable for the loss of data and itsrecovery, notwithstanding the other limitationsof the present Art. 4 if this loss could have beenavoided by observing this obligation.

F) The exclusion or the limitation of claims inaccordance with the present Art. 4 includesclaims against employees or agents of SAP.

4. Adobe Document ServicesAdobe, the Adobe logo, Acrobat, PostScript, and Readerare either registered trademarks or trademarks ofAdobe Systems Incorporated in the United States and/ or other countries. For information on Third Partysoftware delivered with Adobe document services andAdobe LiveCycle Designer, see SAP Note 854621.

Documentation in the SAP ServiceMarketplaceYou can find this document at the following address:service.sap.com/instguides

4/166 PUBLIC 12/04/2006

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

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

12/04/2006 PUBLIC 5/166

http://www.sap.com



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.0 12/4/2006 Initial Version

6/166 PUBLIC 12/04/2006

http://service.sap.com/instguides



Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 111.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 121.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 151.3 Information Available on SAP Service Marketplace . . . . . . . . . . 161.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 18

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 212.1 Basic System Variants . . . . . . . . . . . . . . . . . . . . . 212.2 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . 242.3 Production Client Considerations . . . . . . . . . . . . . . . . 262.4 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 272.5 Multi-Language and Unicode Support . . . . . . . . . . . . . . . 332.6 Running Adobe Document Services on Non-Supported Platforms . . . . 342.7 Application Sharing Server as an Optional Standalone Unit . . . . . . . 352.8 High Availability: Planning the Switchover Cluster . . . . . . . . . . 36

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 413.1 High Availability: Switchover Preparations . . . . . . . . . . . . . 423.1.1 Preparing for Switchover . . . . . . . . . . . . . . . . . . . . 423.1.2 Setting Up File Systems . . . . . . . . . . . . . . . . . . . . 443.1.3 Configuring Network File System . . . . . . . . . . . . . . . . 453.2 Hardware and Software Requirements . . . . . . . . . . . . . . . 473.2.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 483.2.2 Requirements for AIX . . . . . . . . . . . . . . . . . . . . 493.2.3 Requirements for a Central System . . . . . . . . . . . . . . . . 513.2.4 Requirements for a Distributed or a High Availability System . . . . . . 523.2.4.1 Requirements for the Central Services Instance . . . . . . . . . . . 523.2.4.2 Requirements for the Central Instance . . . . . . . . . . . . . . 533.2.4.3 Requirements for the Database Instance . . . . . . . . . . . . . . 533.2.5 Requirements for a Dialog Instance . . . . . . . . . . . . . . . . 553.2.6 Checking and Modifying the AIX Kernel . . . . . . . . . . . . . . 553.2.7 Setting up Swap Space for AIX . . . . . . . . . . . . . . . . . . 573.3 Creating Operating System Users . . . . . . . . . . . . . . . . 573.3.1 Network Information Service . . . . . . . . . . . . . . . . . . 573.3.2 Creating Operating System Users and Groups . . . . . . . . . . . . 58

12/04/2006 PUBLIC 7/166

3.3.3 Creating AIX Groups and Users (Optional) . . . . . . . . . . . . . 593.4 Setting Up File Systems and Raw Devices . . . . . . . . . . . . . . 603.4.1 Setting Up File Systems . . . . . . . . . . . . . . . . . . . . 613.4.2 Oracle File Systems . . . . . . . . . . . . . . . . . . . . . . 663.4.3 Setting Up File Systems and Raw Devices for AIX . . . . . . . . . . . 683.5 Exporting and Mounting the Global Transport Directory . . . . . . . . 693.6 Exporting and Mounting Directories via NFS for AIX (Optional) . . . . . 703.7 Installing the SAP Front-End Software . . . . . . . . . . . . . . . 713.8 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 723.9 Installing the Java Development Kit . . . . . . . . . . . . . . . . 723.10 Preparing and Mounting the Installation Media . . . . . . . . . . . 743.10.1 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 743.10.2 Downloading Installation DVDs from SAP Service Marketplace (Optional) . 763.10.3 Mounting a CD / DVD for AIX . . . . . . . . . . . . . . . . . 77

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 . . . . . . . . . . . . . . . . . . . 854.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 . . . . . . . . . . . . . . . 924.3.5 Performing a Remote Installation with SAPinst (Optional) . . . . . . . 944.3.6 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 954.3.7 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 974.4 Oracle Database Software Installation . . . . . . . . . . . . . . . 974.4.1 Updating SAP-Specific Files in the Oracle Staging Area . . . . . . . . . 984.4.2 Performing Steps for the AIX Operating System . . . . . . . . . . . 984.4.3 Running the Oracle Universal Installer . . . . . . . . . . . . . . 994.4.4 Installing the Current Patch Set . . . . . . . . . . . . . . . . . 1004.4.5 Installing Required Interim Patches . . . . . . . . . . . . . . . . 1014.5 Installing Application Sharing Server as an Optional Standalone Unit . . . 101

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 1035.1 Starting and Stopping the SAP System . . . . . . . . . . . . . . . 1055.2 Logging On to the SAP System . . . . . . . . . . . . . . . . . 1085.3 Logging on to the Portal . . . . . . . . . . . . . . . . . . . . 1105.4 Installing the SAP License . . . . . . . . . . . . . . . . . . . 111

8/166 PUBLIC 12/04/2006

5.5 Installing the SAP Online Documentation . . . . . . . . . . . . . 1125.6 Configuring Remote Connection to SAP Support . . . . . . . . . . 1125.7 Performing Initial ABAP Configuration . . . . . . . . . . . . . . 1135.8 Completing and Checking the Oracle Database Installation . . . . . . . 1155.9 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 1165.10 Performing the Client Copy . . . . . . . . . . . . . . . . . . 1175.11 Performing a Full Installation Backup . . . . . . . . . . . . . . . 1185.12 Post-Installation Steps for Adobe Document Services . . . . . . . . . 1205.12.1 Assigning Roles to Users ADSUSER and ADS_AGENT . . . . . . . . . 1205.12.2 Installation Check and Quick Tests for Adobe Document Services . . . . 1205.13 Performing Post-Installation Steps for Composite Application Framework Core

(CAF Core) . . . . . . . . . . . . . . . . . . . . . . . . 1225.14 Configuring Access to Knowledge Warehouse Content from the SAP Internet

Knowledge Servlet . . . . . . . . . . . . . . . . . . . . . . 1245.15 Setting Environment Variable CPIC_MAX_CONV . . . . . . . . . . 1255.16 Post-Installation Steps for Usage Type Process Integration (PI) . . . . . . 1255.16.1 Performing PI-Specific Steps for SLD Configuration . . . . . . . . . . 1255.17 Post-Installation Steps for Application Sharing Server . . . . . . . . . 1255.18 High Availability: Post-Installation Steps . . . . . . . . . . . . . . 1265.18.1 Setting Up Licenses . . . . . . . . . . . . . . . . . . . . . . 1265.18.2 Taking Precautions for Transport . . . . . . . . . . . . . . . . 1275.19 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 1275.20 Running the Template Installer . . . . . . . . . . . . . . . . . 1305.21 Checking the SAP Java Documentation . . . . . . . . . . . . . . 1335.22 Accessing Configuration Documentation in the SAP Solution Manager . . 135

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 1376.1 Installation of Multiple Components in One Database (Optional) . . . . . 1376.2 Integration of LDAP Directory Services (Optional) . . . . . . . . . . 1396.3 Preparing User Management for an External ABAP System . . . . . . . 1426.4 Creating a User for LDAP Directory Access (Optional) . . . . . . . . . 1456.5 Configuring User Management to Use an LDAP Directory (Optional) . . . 1456.6 Usage Type-Specific Initial Technical Configuration . . . . . . . . . . 1456.6.1 Initial Technical Configuration for Application Server . . . . . . . . . 1466.6.1.1 Initial Technical Configuration for Adobe Document Services . . . . . . 1466.6.1.2 Initial Technical Configuration for Composite Application Framework Core 1476.6.1.3 Configuring the Connection for System Landscape Directory . . . . . . 1476.6.2 Initial Technical Configuration for the Portal . . . . . . . . . . . . 1486.6.3 Initial Technical Configuration for Process Integration (PI) . . . . . . . 1496.6.3.1 Importing the SAP Exchange Profile . . . . . . . . . . . . . . . 1496.6.3.2 Assigning SAP_ALL Rights to User PISUPER . . . . . . . . . . . . 1506.6.3.3 Activating the ICF Services . . . . . . . . . . . . . . . . . . . 150

12/04/2006 PUBLIC 9/166

6.6.3.4 Assigning Roles to Groups . . . . . . . . . . . . . . . . . . . 1516.6.4 Initial Technical Configuration for BI Java . . . . . . . . . . . . . 1516.6.4.1 Configuring BI Java Information Broadcasting . . . . . . . . . . . . 1526.6.4.2 Process Chains: Transporting Texts for the Alert Category . . . . . . . 1526.6.4.3 Renaming initialPermissionsBI.xml.template . . . . . . . . . . . . 1536.7 Heterogeneous SAP System Installation . . . . . . . . . . . . . . 1536.8 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 1546.8.1 Deleting an SAP System Using SAPinst . . . . . . . . . . . . . . . 1546.8.1.1 Running SAPinst to Delete an SAP System . . . . . . . . . . . . . 1556.8.1.2 Deleting the Oracle Database Software . . . . . . . . . . . . . . 1566.8.2 Deleting an SAP SystemManually . . . . . . . . . . . . . . . . 1576.8.2.1 Deleting an SAP Instance . . . . . . . . . . . . . . . . . . . 1576.8.2.2 Deleting Installation Files, Directories, and Users on a Host . . . . . . . 1586.8.2.3 Deleting the Java Part of an SAP System . . . . . . . . . . . . . . 1596.8.2.4 Deleting the Oracle Database Java Schema . . . . . . . . . . . . . 1616.8.2.5 Deleting an Oracle Database Instance . . . . . . . . . . . . . . . 1626.9 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 1646.9.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 1646.9.2 Troubleshooting for Portal Installation . . . . . . . . . . . . . . 165

10/166 PUBLIC 12/04/2006

1 Introduction

1 Introduction

This document explains how to install SAP NetWeaver 2004s SR2 ABAP+Java.It also explains how to install the Java Add-In for an existing SAP NetWeaver 2004s SR2 ABAP

system.For more information about SAP NetWeaver technology, see SAP Service Marketplace at

https://service.sap.com/netweaver.You can install SAP NetWeaver 2004s SR2 ABAP+Java and the Java Add-In with the following

usage types in a single installation run using SAPinst:

n

Only valid for: Application Server (AS)

NetWeaver Application Server ABAP (AS ABAP)

Note

AS ABAP is not installed with the Java Add-In.

End of: Application Server (AS)

n NetWeaver Application Server Java (AS Java)

n

Only valid for: Development Infrastructure (DI)

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

n

Only valid for: EP Core (EPC)

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

n

Only valid for: Enterprise Portal (EP)

NetWeaver Enterprise Portal (EP)If you install usage type EP, note the following:l You must install 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 this document.

End of: Enterprise Portal (EP)

n

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

SAP NetWeaver Business Intelligence Java Components (BI Java)

12/04/2006 PUBLIC 11/166

https://service.sap.com/netweaver



1 Introduction1.1 New Features

You also have to install NetWeaver Application Server Java (AS Java), EP Core (EPC) and NetWeaverPortal (EP).End of: BI Java Components (BI-Java)

n

Only valid for: Mobile Infrastructure (MI)

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

n

Only valid for: Process Integration (PI)

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 thedocumentMaster Guide ‒ SAP NetWeaver 2004s on SAP Service Marketplace [page 16]. For restrictions,see SAP Note 855534.

Constraints

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

n You can install your SAP system with Oracle 10.2 only.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.

12/166 PUBLIC 12/04/2006




SAP System Installation

Area Description

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

Checker [page 48].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. As aresult, you only have to respond to a small selection of prompts. If you want tochange any of the default settings, you can do so on the parameter summaryscreen at the end of the installation.

l Custom ModeIf you choose Custom, you must manually enter all installation parameters. Youcan change your values on the parameter summary screen at the end of theinstallation.

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.

NoteYou cannot install the Java Add-In for the dialog instance(s) of the existing ABAPsystem. Instead, you have to install an 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 58].

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 screen beforeyou start the actual installation.

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 each SAP system instance.For more information, see Setting Up File Systems [page 61].

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

12/04/2006 PUBLIC 13/166


Area Description

Usage type EP Core(EPC)

As of SAP NetWeaver 2004s SR2, usage type Enterprise Portal (EP) is now divided intotwo different usage types, EP Core (EPC) and Enterprise Portal (EP).n EP Core (EPC)

This usage type contains the core portal capabilities that were available in the formerusage type EP. This new usage type provides more flexibility when implementing aportal where the full enterprise portal capabilities, such as knowledge managementand collaboration, are not needed.

n Enterprise Portal (EP)This usage type includes Knowledge management, Collaboration, CAF-Core, VisualComposer, Web Dynpro extension, and .NET PDK, while EPC contains the portal,GP, and UWL.

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

NoteCurrently EPC is not supported as a standalone usage type. You must install bothEPC and EP usage types.

SAP SolutionManager Key

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

Oracle Database

New functions inOracle Database 10g

n As of the installation of SAP NetWeaver 2004s 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

Operating Systems

Area Description

Support of OperatingSystems

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

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.

14/166 PUBLIC 12/04/2006


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

https://service.sap.com/platforms


1 Introduction1.2 SAP Notes for the Installation

Area Description

Web Dispatcher Installation The installation of a Web Dispatcher is covered in a dedicated installationguide, available at https://service.sap.com/installnw2004s 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 https://service.sap.com/installnw2004s

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

Application Sharing ServerInstallation

The installation of Application Sharing Server is part ofthe SAP NetWeaver Java installation guide, available at

https://service.sap.com/installnw2004s Installation - SAPNetWeaver 2004s Installation Documentation - SAP NetWeaver 2004s SR2<Database> <Operating System> Java

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 https://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 SAP

Service 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/sapnotesnw2004s.

SAP Notes for the Installation

SAP Note Number Title Description

972262 SAP NetWeaver 2004s SR2 / BusinessSuite 2005 SR2 - UNIX

UNIX-specific information about theSAP system and corrections to thisdocumentation.

852008 Release Restrictions for SAPNetWeaver 2004s

Customer information on restrictionsconcerning the production use ofcertain functions.

12/04/2006 PUBLIC 15/166

https://service.sap.com/installnw2004s






https://service.sap.com

https://service.sap.com/notes



https://service.sap.com/sapnotesnw2004s





1 Introduction1.3 Information Available on SAP Service Marketplace

SAP Note Number Title Description

737368 Hardware requirements of JavaDevelopment

Information on the hardwarerequirements for usage typeDevelopment Infrastructure (DI),which depends on the size of yourdevelopment team.

972263 SAP NetWeaver 2004s SR2 / BusinessSuite 2005 SR2 - UNIX : Oracle

Oracle-specific information aboutthe SAP system installation andcorrections to this documentation.

828268 Oracle 10g : New functions Information about new Oraclefeatures released for the SAP system.

98252 Installing two Oracle databases on ahost

This SAP Note is only required if youplan to install more than one Oracledatabase on the same host.

855498 Installation Prerequisite Checker SAP Software on UNIX, Windows andiSeries: Checking OS Dependencies

937693 SAP Mobile Infrastructure 7.0 -Release Note

This note contains additionalinformation about SAP MobileInfrastructure 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 2004s

https://service.sap.com/installNW2004s Master Guide ‒ SAP NetWeaver2004s

Technical InfrastructureGuide for SAP NetWeaver2004s

https://service.sap.com/installNW2004s Technical Infrastructure Guide ‒ SAPNetWeaver 2004s

List of media forinstallation or upgradefor SAP NetWeaver 2004s

https://service.sap.com/installNW2004s Media List ‒ SAP NetWeaver 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>

16/166 PUBLIC 12/04/2006







https://service.sap.com/installNW2004s









https://service.sap.com/solutionmanager








1 Introduction1.3 Information Available on SAP Service Marketplace

Description Internet Address Title

Patching of SAPNetWeaver 2004s scenarios


/maintenanceNW2004s

Support Package Stack Guide ‒ SAPNetweaver 2004s Support Package Stack<current stack>

Upgrade to SAPNetWeaver 2004s

https://service.sap.com/upgradeNW2004s Component Upgrade Guide ‒ SAPNetWeaver 2004s Application ServerABAP

Installation of SAPNetWeaver DeveloperWorkplace

https://service.sap.com/installNW2004s Installation Guide ‒ SAP NetWeaverDeveloper Workplace

Installation of SAPNetWeaver DeveloperStudio

https://service.sap.com/installNW2004s Installation Guide ‒ SAP NetWeaverDeveloper Studio

Installation of the SystemLandscapeDirectory (SLD)


/installNW2004s ConfigurationPost-Installation Guide ‒ SystemLandscape Directory of SAPNetWeaver 2004s

Installationof a standalonegateway


/installNW2004s Installation - StandaloneEngines & Clients

Installation Guide ‒ Gateway on<platform> for SAP NetWeaver2004s SR2

Installation of WebDispatcher


/installNW2004s Installation - StandaloneEngines & Clients

Installation Guide ‒ Web Dispatcheron <platform> for SAP NetWeaver2004s SR2

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

Homogeneous andheterogeneous systemcopy for SAP systems basedon NetWeaver 2004s

https://service.sap.com/installNW2004s Homogeneous and Heterogeneous SystemCopy for SAP Systems based on SAPNetWeaver 2004s

SAP NetWeaver ProblemAnalysis Guide

https://help.sap.com/nw2004s SAPNetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by KeyCapability SAP NetWeaver Problem Analysis Guide(PAG)

SAP NetWeaver Problem AnalysisGuide (PAG)

General Quick Links

Description Internet Address

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

SAP NetWeaver Library in SAPHelp Portal

https://help.sap.com/nw2004s

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

12/04/2006 PUBLIC 17/166

https://service.sap.com/maintenanceNW2004s




https://service.sap.com/upgradeNW2004s






























https://help.sap.com





1 Introduction1.4 Naming Conventions

Description Internet Address

SAP Notes for SAP NetWeaver2004s installation


Released platforms and operatingsystems


Unicode SAP systems and theiravailability

https://service.sap.com/unicode

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

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

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

Information on SAP SupportPackage Stacks

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

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

1.4 Naming Conventions

In this documentation, the following naming conventions apply:

Terminology

n SAP system refers to SAP NetWeaver 2004s SR2.n ABAP+Java system refers to SAP NetWeaver 2004s SR2 ABAP+Java.n Java Add-In refers to the Java Add-In for an existing SAP NetWeaver 2004s SR2 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

18/166 PUBLIC 12/04/2006







https://service.sap.com/sizing


https://service.sap.com/ha


https://service.sap.com/security

https://service.sap.com/security





1 Introduction1.4 Naming Conventions

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.

12/04/2006 PUBLIC 19/166

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 21].3. You plan how to distribute the instances to hosts [page 24].4. You decide on your production client [page 26].5. You identify basic SAP system parameters [page 27].6. You decide whether you want to use Unicode and multi-language support [page 33].7. If you want to use Adobe Document Services (ADS), you check what you have to do in case your platform is

not supported for ADS [page 34].

8.


You decide if you want to install Application Sharing Server as a standalone unit on a dedicated host [page 35].End of: Enterprise Portal (EP)

9.

Only valid for: HA (UNIX)

You plan the switchover cluster [page 36] 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 137]

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

a Java 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.

12/04/2006 PUBLIC 21/166

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

high availability 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.

22/166 PUBLIC 12/04/2006

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)

12/04/2006 PUBLIC 23/166

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

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

24/166 PUBLIC 12/04/2006

2 Planning2.2 How to Distribute Instances to Hosts

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:

Figure 5:

12/04/2006 PUBLIC 25/166

2 Planning2.3 Production Client Considerations

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 2004s and Business Suite 2005, you can install an ABAP+Java system in one

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

The following procedure describes the above methods.

Installing the ABAP and the Java Part of your System Separately1. You install the ABAP system as described in the documentation Installation Guide ‒ <your SAP system

application> ABAP on <your OS>: <database>.2. You perform the client copy [page 117].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

System Parameters [page 27].

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

26/166 PUBLIC 12/04/2006


2 Planning2.4 Basic SAP System Parameters

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

System Parameters [page 27].

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

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.

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.

...

12/04/2006 PUBLIC 27/166


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.If you want to install an additional application serverinstance, you must use exactly the same instance number as theexisting primary application server instance.To find out this number, look under the SAP directory/usr/sap/<SAPSID>/DVEBMGS<nn> on the host of the primaryapplication server instance.The value <nn> is the number assigned to the primary applicationserver 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.

...

Messaging ServicePort Caution

Make sure that all messaging service port numbers on the samehost are unique.

Port number of the SAP Messaging Service:If you do not specify a value, the default port number is used.The messaging service port number must be unique for the SAPsystem on all hosts.ABAP Messaging Service PortThere is an external messaging service port using the parameterrdisp/msserv and an internal messaging service port using theparameter rdisp/msserv_internal.The ABAP messaging service uses both the internal and theexternal messaging service ports. Both messaging service portsare configured in the default profile.The external messaging service port uses the parameterrdisp/msserv with default value 36<nn>, where <nn> is theinstance number of the ABAP messaging service instance.The internal messaging service port uses the parameterrdisp/msserv_internal with default value 39<nn>, where <nn>is the instance number of the ABAP messaging service instance.Java Messaging Service PortThe Java messaging service only uses the internalmessagingservice port. The Java messaging service is configured in the SCSinstance profile.

...

28/166 PUBLIC 12/04/2006




The parameter rdisp/msserv is set to 0, so that the external portis not open.The internal messaging service port uses the parameterrdisp/msserv_internal with default value 39<nn>, where <nn>is the instance number of the SCS messaging service instance.For more information about the parameters used for internal andexternal messaging service 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 57].

...

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.

...

12/04/2006 PUBLIC 29/166




DDIC Password The existing password of the DDIC user.

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

...

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.

...

30/166 PUBLIC 12/04/2006


Solution Manager Key


SAP Solution Managerkey

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

...

Parameters Relevant for the Connectivity to System Landscape Directory


SLD HTTP Host The host name of the SystemLandscape Directory (SLD)

...

SLD HTTP Port The HTTP port of the Java systemwhere the SLD is installed. Thefollowing naming conventionapplies: 5<instance_number>00.

ExampleIf the instance number of yourJava system is 01, the SLD HTTPPort is 50100.

...

SLD Data Supplier User andpassword

n If you want to install a localSLD, SAPinst creates this userduring the installation.

n If you want to connect yoursystem to an existing centralSLD, you have to enter theexisting SLD Data Supplier Userand password of the centralSLD during the installation.

RecommendationWe recommend that you namethis user SLDDSUSER

...

SLD ABAP API User and password n If you want to install a localSLD, SAPinst creates this userduring the installation.

n If you want to connect yoursystem to an existing centralSLD, you have to enter theexisting SLD Data Supplier Userand password of the centralSLD during the installation.

RecommendationWe recommend that you name

...

12/04/2006 PUBLIC 31/166




this user SLDAPIUSER

RFC User, Password The ABAP RFC user of the SLD ...

SLD Gateway Host The host on which the gatewayinstance of the SLD is running

...

SLD Gateway Instance Number The instance number of thegateway instance of the SLD

...

SAP System Client The client in which the ABAP RFCuser 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).

...

32/166 PUBLIC 12/04/2006

2 Planning2.5 Multi-Language and Unicode Support


Database schemata,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 ...

Database User Oracle User System ...

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)

12/04/2006 PUBLIC 33/166

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

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

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

More InformationFor more information, see SAP Notes 79991 and 73606.

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.

34/166 PUBLIC 12/04/2006






2 Planning2.7 Application Sharing Server as an Optional Standalone Unit


2.7 Application Sharing Server as an Optional Standalone Unit

Application Sharing Server for real-time collaboration provides data streaming services that enableapplication sharing capabilities provided by SAP NetWeaver collaboration. The server handles theflow of data between portal users collaborating through the real-time application sharing feature.Application Sharing Server lets users share their Windows desktop or individual applications

with other portal users in real time. Remote users can interact directly with the shared desktop orapplication as if they were sitting at the host machine.The server is installed automatically with usage type Enterprise Portal (EP) on the portal host. In

a cluster environment, the load generated by the Application Sharing Server is replicated to allinstances of the cluster. This generates load on all dialog instance hosts.

Note

You can only use Application Sharing Server with SAP NetWeaver systems with usage type EP.

Planning

For test or demo purposes, you can run the Application Sharing Server on the portal machine.

Recommendation

For production use, we recommend that you install the server as an optional standalone unit on adedicated host. To do this, you perform a separate installation as described in this documentation.By removing Application Sharing Server traffic from the portal host, you reduce the networking andJ2EE Engine demands on that machine, which improves the overall performance of the portal.

When you install usage type EP, the Application Sharing Server is installed automatically. If you donot intend to use the Application Sharing Server, you can disable it. For more information, seePost-Installation Tasks for Application Sharing Server [page 125].You can install Application Sharing Server on a dedicated host before or after installing the usage

type EP. However, you can only complete the post-installation steps after you have installed usagetype EP.

Preparation

Prepare the Application Sharing Server installation host for an AS Java central system installation:

1. Check hardware and software requirements [page 47].2. Set up file systems [page 61].3. Install the Java Development Kit [page 72].4. Prepare the installation DVDs [page 74].

12/04/2006 PUBLIC 35/166

2 Planning2.8 High Availability: Planning the Switchover Cluster

Installation

1. Run SAPinst to install Application Sharing Server as an optional standalone unit [page 101].2. During the installation of the Oracle database instance, SAPinst stops the installation and prompts

you to install the Oracle database software [page 97].

Post-Installation

Perform the post-installation steps for an AS Java central system installation on the ApplicationSharing Server installation host:

1. Start and stop the Application Sharing Server system [page 105].2. Check the SAP Java documentation [page 133].3. Apply the latest kernel and support packages [page 116].4. Perform post-installation steps for Adobe Document Services [page 120].5. Perform post-installation steps for Application Sharing Server [page 125].6. Ensure the security of Java standalone users stored in the database [page 127].

End of: Enterprise Portal (EP)


2.8 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 a particular node for planned system maintenance. Switchover solutions can protect againsthardware failure and operating system failure but not against human error, such as operator errors orfaulty application software.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 ofthese can only exist once in a normal SAP system.You can protect software units that are not SPOFs against failure by simply replicating them.

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

36/166 PUBLIC 12/04/2006


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

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:https://service.sap.com/ha Media Library Documentation HA Documentation .

This covers HA for SAP systems based on SAP NW 2004s and is part of the standard SAPdocumentation delivered with SAP NW 2004s.

n Technical Infrastructure Guide: SAP NetWeaver 2004s at:https://service.sap.com/installNW2004s

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:https://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:

12/04/2006 PUBLIC 37/166







https://help.sap.com


Figure 6:

Note

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

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

38/166 PUBLIC 12/04/2006


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 to make sure that your hardware is powerful enough to handle the increased workload

after a switchover. Some reduction in performancemight be acceptable after an emergency. However,it is not acceptable if the system comes to a standstill because it is overloaded after switchover.

More InformationFor more information on HA documentation, see:


End of: HA (UNIX)

12/04/2006 PUBLIC 39/166




This page is intentionally left blank.

3 Preparation

3 Preparation

You have to complete the following preparations:

1.


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

2. You check the hardware and software requirements [page 47].3. If required, you create operating system users manually [page 57].4. You set up file systems and raw devices [page 60].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 69]n Exporting and Mounting Directories via NFS for AIX [page 70]

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

Caution


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

Caution


12/04/2006 PUBLIC 41/166

3 Preparation3.1 High Availability: Switchover Preparations

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

If required, you can optionally prepare user management for an external ABAP system [page 142].


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

central services (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 36].

Procedure1. You check that your system meets the hardware and software requirements [page 47] 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 HA

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

42/166 PUBLIC 12/04/2006


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

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

12/04/2006 PUBLIC 43/166


Caution


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.

Procedure1. Create the file systems or raw partitions for the central services (SCS) instance on shared disks. For

more information, see Setting Up File Systems [page 61].

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 AS

44/166 PUBLIC 12/04/2006


instance is already running. The DVEBMGS00 directory can join the /usr/sap/<SID> tree insteadof mounting on top of it.

Note

This approach becomes increasingly important when you want to cluster central services whileother instances run on the cluster hosts outside the control of the switchover software (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 and

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

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

12/04/2006 PUBLIC 45/166


2. Since you can protect NFS by a switchover product, it makes sense to install it on a cluster node.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

46/166 PUBLIC 12/04/2006

3 Preparation3.2 Hardware and Software Requirements

/sapmnt/<SID>

End of: HA (UNIX)

End of: HA (UNIX)

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

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

https://service.sap.com/sizing. You enter information about your planned system andthe tool calculates the requirements.For more information, see Planning your System Landscape in theMaster Guide ‒ SAP NetWeaver 2004s,which is available on SAP Service Marketplace [page 16].

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

n For supported operating system and Java (JDK/JRE) releases, see the Product Availability Matrix onSAP Service Marketplace at https://service.sap.com/pam.

n Contact your OS vendor for the latest OS patches.n Make sure that the host name meets the requirements listed in SAP Note 611361.n Check your keyboard definitions.

12/04/2006 PUBLIC 47/166





https://service.sap.com/pam





n If you want to install a printer on a host other than the central instance host (for example, on aseparate 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 48] 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 AIX [page 49]n Central system [page 51]n Distributed or high availability system [page 52]

3. If you want to install additional dialog instances, check the requirements for a Dialog instance[page 55].

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.

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

Tasks Prerequisites Check .3. Enter the required parameters when prompted in the SAPinst dialogs.

48/166 PUBLIC 12/04/2006


Note

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

When you have finished, the Start Execution screen appears summarizing all parameters you haveentered. To change a parameter, choose Back and enter a new value.

4. To start the Prerequisite Checker choose Start.

ResultAfter the check has successfully completed, the Prerequisite Check Results screen appears displayingthe results found.If required, you can also check the results in file prerequisite_checker_results.html, which you

can find in the installation directory.

3.2.2 Requirements for AIX

The host machine must meet the following requirements:

Note

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

n Manually by entering AIX commands with the appropriate options

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

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

Requirement Type Requirement

Hardware n Tape driveHigh-capacity tape drive with hardware compression is recommended.You can test the drive /dev/rmt0 with this command:tar -cvf /dev/<tape_device> <test_file>

The device name is always rmt0 unless more than one tape drive existsn CD / DVD drivel ISO 9660 compatiblel You can configure multiple CD / DVD drives, but you cannot mount all of them.

For more information, seeMounting a CD / DVD for AIX [page 77].n Disks

For data security reasons, distribution over three disks is required. We recommendyou to distribute over five disks.To display available disks enter this command:lspv

Disks marked none in the 3rd column are unused.

12/04/2006 PUBLIC 49/166



To display free space on a disk enter this command:lspv -p <disk_name>

Areas marked free in the 2nd column are unused.If an advanced disk array is available (for example, RAID), contact your hardwarevendor to make sure that the data security requirements are covered by thistechnology.

n RAMTo display RAM size in KB enter this command:lsattr -El sys0 -a realmem

n Swap Space3 to 4 * RAM

n CPUThe recommended minimum hardware is either two physical single core processorsor one physical dual core processor.

Software n Check the C++ runtime level with the following commands:l #lslpp —L xlC.aix50.rte

The output must be at least 7.0.0.4.l #lslpp —L xlC.rte

The output must be at least 7.0.0.0.n Operating system

Check the operating system version with the following command:lslpp -l bos.rte

The output must include the following or a larger version number:bos.rte 5.2.0.50

n AIX Maintenance Level (ML) and Technology Level (TL)l AIX 5.2 : The output of the command oslevel -r should be at least 5200-03

(ML 3).l AIX 5.3 : The output of the command oslevel -s should be at least 5300-05-01

(TL 5 SP 1).n LDAP (Lightweight Directory Access Protocol)

If you want to use LDAP, you require the following LDAP library:libldap.a

n Additional softwareMake sure that the following additional file sets are installed:l bos.adt Base Application Developmentl bos.perf—performance and diagnostics toolsl perfagent.tools—performance monitoring toolsl bos.perf.libperfstat—Performance Statistics LibraryFor an overview of the installed file sets, enter this command:lslpp –L | more

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

1. Start the SystemManagement Interface Tool (SMIT) with this command:smitty mle_add_lang

2. Select the following:l Cultural Conventions to install:

ISO8859-1 German (Germany) [de_DE]

50/166 PUBLIC 12/04/2006



l Language Translation to install:

ISO8859-1 German [de_DE]

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

3. Additionally, check that all file sets are in a consistent state with this command:lppchk –v

Other n PrinterCheck whether a file can be printed with this command:lp -d<printer_name> <test_file>

Check the status of your spool and the printers with this command:lpstat -t

n KeyboardYou can set the keyboard by typing this command on the directly connected console:smitty chkbd

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

n NetworkTest the network connection to the database server with this command:/etc/ping <db_server_name> 100 10

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:

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 61] 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 74].

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)

12/04/2006 PUBLIC 51/166


RequirementType

Requirement


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.

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 52]n Central instance [page 53]n Database Instance [page 53]

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:


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

For more information, see Setting up File Systems [page 61].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 74].


0.5 GB (minimum), 1 GB (recommended)

52/166 PUBLIC 12/04/2006





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 61] 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 74].


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

installation guide for your operating system, which you can find athttp://www.oracle.com/technology/documentation

12/04/2006 PUBLIC 53/166

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

You can install SAP NetWeaver 2004s SR2 with Oracle 10.2 only.


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 Oracledatabase, see the Database System Configuration guide in SAPDatabase Guide: Oracle (BC-DB-ORA-DBA) in the SAP Library athttps://help.sap.com/nw2004s SAP NetWeaver Library SAP

NetWeaver by Key Capability Application Platform by Key CapabilityPlatform-Wide Services 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. Formore information, see Setting Up File Systems and Raw Devices ‒ Oracle FileSystems [page 66].

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.For more information, see Preparing the Installation DVDs [page 74]


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

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

54/166 PUBLIC 12/04/2006

http://www.oracle.com/documentation

http://www.oracle.com/technology





n Make sure that the required fonts/code pages are installed.n Make sure that NLS and corresponding saplocales are installed.n On the database host, a graphical user interface (GUI) is required for the

Oracle database software installation with runInstaller.n Check SAP Note 839182 whether you require an interim patch for

the Oracle database installation. In this case, make sure you have thecorresponding Perl version as stated in that SAP Note.

n Review the Oracle-recommended kernel parameters and shell limitsfor your operating system with Oracle Database 10g Release 2 (10.2).These are only recommendations from Oracle for optimizing thesystem performance in production environments. If the recommendedsettings are not suitable for your system you must tune the kernelparameters accordingly.You can get the recommended shell limits and kernel parameters fromthe relevant Oracle database installation guide for your operatingsystem, which you can find at:http://www.oracle.com/technology/documentation

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 61].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 74].


1 GB minimum, 3 GB recommended

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

3.2.6 Checking and Modifying the AIX Kernel

To run an SAP system on AIX with an Oracle database, you must check and if necessary modifythe UNIX operating system kernel.

Recommendation

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

12/04/2006 PUBLIC 55/166


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


Procedure1. Asynchronous I/O: If the database is installed using file systems, the settings for asynchronous I/O

(aio) should be as follows:maxservers = minservers = 1.2 * number of data files used for the database.Set these values as follows:a) Enter:

smitty aio orsmit aio

b) Select Change / Show Characteristics of Asynchronous I/O.c) Enter the appropriate numbers for MINIMUM and MAXIMUM number of servers.

Note

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

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

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

Note

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

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

smitty orsmit

B) Select System Environments.

56/166 PUBLIC 12/04/2006

3 Preparation3.3 Creating Operating System Users

C) Select Change / Show Characteristics of Operating System.D) Enter the appropriate number forMaximum number of processes allowed per user, and choose Enter.

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

3.2.7 Setting up Swap Space for AIX

1. Check the allocated swap space:a) To start the SystemManagement Interface Tool (SMIT), enter the following command :

smitty.b) Perform one of the following steps:n Choose Physical & Logical Storage Logical Volume Manager Paging Space List All Paging Spaces

n Enter this command:lsps —a

2. Check if there is sufficient swap space: 3 to 4 * RAM are recommended.3. If required, add another paging space using smitty:

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

b) Select a volume group.c) Enter the size of paging space in logical partitions.d) Set Start using this paging space NOW ? to YES.e) Set Use this paging space each time the system is RESTARTED to YES.f) To exit smitty, choose F10 .g) To check the results, follow the procedure described above in step 1.

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 by

SAP, 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 57].

12/04/2006 PUBLIC 57/166



SAPinst checks if the required services are available on the host and creates them if necessary. Seethe log 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 not

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

choose Life Cycle Management Preparation Operating System Users and Groups . For more information,see Running SAPinst on UNIX [page 85].

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 a

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

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

Users and Their Primary Groups

User Primary Group

<sapsid>adm sapsys, oper, dba, sapinst

ora<dbsid> dba, oper, sapinst

58/166 PUBLIC 12/04/2006


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

Groups Members

sapsys <sapsid>adm

oper <sapsid>adm, ora<dbsid>

dba <sapsid>adm, ora<dbsid>

sapinst <sapsid>adm, ora<dbsid>

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

3.3.3 Creating AIX Groups and Users (Optional)

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

1. Create groups as follows:a) Enter the command smitty.b) Choose Security and Users Groups Add a group .c) Enter a group name ‒ for example, sapsys ‒ and set administration group to true.d) Press F3 until the Security & Usersmenu appears.

2. To create users, proceed as follows:a) Enter a user name, for example <sapsid>adm.b) Enter all required values.

3. Set the initial password using the following command:passwd <user>

Example

passwd <sapsid>adm

Checking Created UsersAs user root check all existing users as follows:

12/04/2006 PUBLIC 59/166

3 Preparation3.4 Setting Up File Systems and Raw Devices

1. Enter the command smitty.2. Choose Security & Users Users Change/Show Characteristics of a User .3. To get a list of users, choose F4 .4. For user root and each created user <user> perform the following steps:

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

Note

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

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

You must make sure that the system-wide default HARD values are not explicitly defined to belower than the values given above. Check the file /etc/security/limits under the default:stanza. If they are not explicitly set, then the values are as shown in the table at the top of the file.

Checking the Operating System1. Enter the command smitty.2. Choose System Environments Change/Show Characteristics of Operating System .3. ChangeMaximum number of PROCESSES allowed per user to 500.4. To exit SMIT, choose F10 .

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

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 61]n Oracle File Systems [page 66]n Setting Up File Systems and Raw Devices for AIX [page 68]

60/166 PUBLIC 12/04/2006


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 file

systems you need to set up manually. For details see the following figures and tables.


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

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 to

restart the system after patches have been applied.See also Applying the Latest Kernel and Support Packages [page 116].

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.

12/04/2006 PUBLIC 61/166


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)

62/166 PUBLIC 12/04/2006


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 Engine

is 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

12/04/2006 PUBLIC 63/166



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

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:

1.5 GB (Non-Unicode), 2.0 GB(Unicode)

l AS Java:1.5 GB (Non-Unicode), 2.0 GB(Unicode)Java Add-In (ABAP systemalready exists): 1.0 GB

l For BI add 2.0 GB.l For EPC add 1.5 GB.l For EP add 1.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

64/166 PUBLIC 12/04/2006



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 69]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:

https://help.sap.com/nw2004s SAPNetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by KeyCapability Software Life Cycle Management SoftwareLogistics Change and Transport 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, see

https://help.sap.com/nw2004s SAPNetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by KeyCapability Software Life Cycle Management SoftwareLogistics SAP NetWeaver Development InfrastructureMaintenance of an NWDI-Driven System Landscape

n For the installation of allinstances: 500 MB

n For the use of all instances: 2 GB

12/04/2006 PUBLIC 65/166




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

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 https://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/instantclient

or/oracle/client/102_64/instantclient iscreated by SAPinst during the installation.

100 MB

66/166 PUBLIC 12/04/2006






/oracle/stage/102_32

or/oracle/stage/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.

5.5 GB

/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 AIX[page 68].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/oracle/<DBSID>/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.

12/04/2006 PUBLIC 67/166



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

1.5 GB

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

Setting up File Systems

Note

If you want to create file systems larger than 2 GB, see SAP Note 129439.Note that large files can lead to performance degradation due to access synchronization over the

nodes. For performance reasons, smaller files are recommended for very active data.

1. Create one logical volume for each file system listed in the appropriate SAP profile:a) Using SMIT, choose Physical & Logical Storage Logical Volume Manager Logical Volumes Add a

Logical Volume .b) Enter a volume group name, for example, sapr3vg.c) Enter a logical volume name, for example, lvsap01.d) Enter the number of logical partitions.e) Press F3 until the Physical & Logical Storagemenu appears.

2. Create the file systems.a) Using SMIT, choose Physical & Logical Storage File Systems Add/Change/Show/Delete File Systems

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

b) To get a list of logical volumes, choose F4 .

68/166 PUBLIC 12/04/2006



3 Preparation3.5 Exporting and Mounting the Global Transport Directory

c) Select one logical volume.

Caution

Select the logical volume with the desired size.

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

Example

/oracle/<DBSID>/sapdata1

e) Set mount automatically to yes.f) To exit smitty, choose F10 .

Setting up Raw Devices1. Create volume group.2. Create logical volume:

a) Enter the command smitty.b) Choose Physical & Logical Storage Logical Volume Manager Logical Volumes Add a Logical Volume .c) Enter volume group name.d) Enter logical volume name (for example: lvsap02).e) Enter the number of logical partitions.f) Set the logical volume TYPE to r3data and press ENTER.g) To exit SMIT, choose F10 .

Note

The logical volume can be accessed through /dev/r<name of raw log.vol>.

Example

A logical volume called lvsap02 points to the device name /dev/rlvsap02.

3. Accessing raw devices:It is not necessary to create a link to access the volume.

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.

12/04/2006 PUBLIC 69/166

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

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

n If this global transport directory does not exist, proceed as 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.

Exporting the Transport Directory1. 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 AIX (Optional) [page 70]

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

There are two ways of mounting directories via NFS:

n Manuallyn Using the System Management Interface Tool (SMIT)

ProcedureTo mount directories via NFS from the host on which the directory to be mounted resides:

1. Log on as user root.2. To start NFS services at the host on which the directory to bemounted resides, use SMIT as follows:

a) Enter the command smitty.b) Choose Communications Applications and Services NFS Network File System (NFS) Configure NFS

on this System Start NFS .c) In the line Start NFS now, on system restart or both, enter: both.

70/166 PUBLIC 12/04/2006

3 Preparation3.7 Installing the SAP Front-End Software

d) Choose ENTER .3. Export the directory (for example <sapmnt>/<SAPSID>/exe) with read or read-write access for the

host on which the additional instance runs:a) Enter the command smitty.b) Choose Communications Applications and Services NFS Network File System (NFS) Add a Directory

to Exports List .c) Enter the path of the directory which you want to export (for example,

<sapmnt>/<SAPSID>/exe).d) Choose export mode (use read-write or read-only as required by SAP). In the line HOSTS

allowed root access, enter the name of the host on which the additional instance runs. For securityreasons, this root access should be disabled after the installation.

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

4. Create the mount point at the host on which the additional instance runs: /usr/bin/mkdir<sapmnt>/<SAPSID>/exe

5. Mount the directory on the host on which the additional instance runs.a) Enter the command smitty.b) Choose Communications Applications and Services NFS Network File System (NFS) Add a File System

for Mounting .c) Enter the path name of the mount point.d) Enter the path name of the remote directory (the directory of the central instance).e) Enter the host where the remote directory resides.f) SetMount now, add entry to /etc/filesystems or both to both.g) Set /etc/filesystems entry will mount the directory on system RESTART to yes.h) ChangeMount file system soft or hard to soft and press ENTER.

6. If you exported the directory with read-write access, check if the host on which the futureadditional instance will run has write access to directory <sapmnt>/<SAPSID>/exe using thefollowing commands:cd <sapmnt>/<SAPSID>/exe

touch test (create a file called test)

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

rm test (remove the file test)

3.7 Installing the SAP Front-End Software

Caution


12/04/2006 PUBLIC 71/166

3 Preparation3.8 Generating the SAP Solution Manager Key

For the installation, make sure that the front-end software is installed on at least one host machine inyour system environment. To simplify the administration of your SAP system, we recommend youinstall the software on the central instance host.With the SAP front-end installation software, SAPSetup, you can optimize the deployment of SAP

GUI 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.For more information on installing the front-end software, see the documentation on SAP Service

Marketplace at https://service.sap.com/installNW2004s :

n SAP Front End Installation Guide (English version)n SAP Frontend-Installationsleitfaden (German version)

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 Manager

system. For more information, see SAP Note 805390.

PrerequisitesYou require SAP Solution Manager 3.2 SP 08 or higher.

Procedure1. 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:https://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).

72/166 PUBLIC 12/04/2006










3 Preparation3.9 Installing the Java Development Kit

As of SAP NetWeaver 2004s you must install the J2EE Engine with strong encryption.The J2EE Engine requires a Java Development Kit (Java™ 2 SDK, Standard Edition = JDK) on every

host where the J2EE Engine is to be installed. You need this for the system variants [page 21] with Java.The JDK includes the Java Runtime Environment (JRE), which is required both for SAPinst and

the SAPinst GUI.

Note

If required, you can perform a remote installation using a standalone SAPinst GUI on a separateWindows or UNIX host. This lets you perform the installation on a remote host, controlling it withthe SAPinst GUI from a local host.If you want to perform a remote installation, see Performing a Remote Installation with SAPinst [page 94].

In this case, you need at least a JRE on the local host to start the SAPinst GUI there.

Procedure1. Check the JDK versions that are released for SAP systems in the Product Availability Matrix (PAM):

a) Go to https://service.sap.com/pam.b) On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 2004s JSE Platforms .c) Choose tab strip JSE Platforms.For additional information on the recommended JDK version and about how to obtain it, seeSAP Note 709140.

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 JDK is not already installed

Since JDK is not part of the SAP shipment, you need to download and install it.n If JDK is already installed

Check the installed version of 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 2004s strong encryption is mandatory for the J2EE Engine and for all usagetypes that are deployed on it. You need to obtain the JCE policy files beforehand so that theycan be installed by SAPinst:a) Download the JCE policy files for your platform at

http://www6.software.ibm.com/dl/jcesdk/jcesdk-p.b) SAPinst installs the JCE policy files during the installation process.c) Copy the JCE policy files to directory /usr/java14_64/jre/lib/security.

12/04/2006 PUBLIC 73/166





http://www6.software.ibm.com/dl/jcesdk/jcesdk-p

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

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.

Procedure1. Identify the required DVDs for your installation as listed below and keep them separate from the

remaining 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 2004s SR2 inthe appropriate Media List for SAP NetWeaver 2004s SR2 on SAP Service Marketplace athttps://service.sap.com/installNW2004s 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

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

74/166 PUBLIC 12/04/2006






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

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 NetWeaver Java DVD

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

Oracle database instance (MCOD) n Installation Master DVDn 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, dialoginstance

n Installation Master DVDn NetWeaver Java DVDn Kernel DVD

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

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

2. Use one of the following methods to make DVDs available in parallel:n Before the installation:l Have sufficient DVD drives

l Copy DVDs manually to local hard disks

12/04/2006 PUBLIC 75/166


n During the installation:Use the SAPinst DVD / CD Browser dialog. You can check the entered location and then copythe 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 DVDsmight be split into several files. In this case, you

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

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

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.

76/166 PUBLIC 12/04/2006

https://service.sap.com/swdc








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 AIX

Note

<medium-mountdir> refers to either <cd-mountdir> or <dvd-mountdir>.

Use the following procedure to mount a CD / DVD:

Procedure1. Log on as user root.2. Add a CD / DVD file system.

a) Enter the command smitty.b) Choose Physical & Logical Storage File Systems Add / Change / Show / Delete File Systems CDROM

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

Select a device name.d) Enter the mount point <medium-mountdir>.

Example

<medium-mountdir> is /sapcd

e) Choose ENTER .f) To exit smitty, choose F10 .

3. Mount the CD / DVD as follows:

Note

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

cdrfs -r /dev/cd0 /sapcd.

a) Enter the command smitty.b) Choose Physical & Logical Storage File Systems Mount a File System .c) Place the cursor on File System Name and choose F4 .d) Select the CD / DVD device /dev/cd0.e) Place the cursor on field Directory over which to mount and choose F4 .f) Select /sapcd.

12/04/2006 PUBLIC 77/166


g) Place the cursor on field Type of File System and choose F4 .h) Select cdrfs.i) ChangeMount as Read Only system to YESj) Choose ENTER .k) To exit smitty, choose F10 .

78/166 PUBLIC 12/04/2006

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 97] while the installation of thedatabase instance is running.If you install a system into an existing database (MCOD), this action is not required.

4.


If required, you can install an Application Sharing Server as an optional standalone unit [page 101].End of: Enterprise Portal (EP)


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.

Prerequisitesn You have completed all preparations, including preparing the installation of switchover units [page 42].

12/04/2006 PUBLIC 79/166

4 Installation4.1 Performing a High-Availability Installation

n You have set the environment variable SAPINST_USE_HOSTNAME [page 84] to specify the virtual hostname for the installation. Alternatively you can specify the virtual host name in the commandto start SAPinst.

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.

Procedure1. Install the central services (SCS) instance with SAPinst [page 85] using the virtual host name on the primary

node, host A.2. Prepare the standby node, host B, making sure that it meets the hardware and software

requirements and it has all the necessary file systems, mount points, and (if required) NetworkFile System (NFS), as described in Preparing for Switchover [page 42].

3. Set up the user environment on the standby node, host B.For more information, see Creating Operating System Users and Groups Manually [page 58]. 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. You enable remote logons as follows:a) To run certain operating system commands as user root and <sid>adm you have to allow

remote logons from user root to user <sid>adm.b) You have to create the file .rhosts in the home directory of <sid>adm on each host machine

as follows:host1 root

host2 root

This allows the user root to perform a remote logon to the <sid>adm account from bothhost1 and host2.

5. Configure the switchover software and test that switchover functions correctly.6. Install the database instance on the primary node, host A.7. Install the central instance with SAPinst [page 85] 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 ABAP SCS, whichis protected by the cluster.

80/166 PUBLIC 12/04/2006

4 Installation4.2 Prerequisites before Starting SAPinst

8. If required, install additional dialog instances with SAPinst [page 85] 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 126].

End of: HA (UNIX)

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

Prerequisitesn Make sure that you have defined the most important SAP system parameters as described in Basic

SAP System Parameters [page 27] before you start the installation.n Check that your installation host(s) meets the requirements for the installation service(s) that you

want to install. For more information, see Running the Prerequisite Checker [page 48].

Procedure1. If you want to install a dialog instance for an SAP system upgraded to SAP NetWeaver 2004s SR2

or Business Suite 2005 SR2, do the following:a) Edit DEFAULT.PFL.b) Set rdisp/msserv_internal to a free port number.

Note

Bear in mind that for AIX 5.3 the port 39<SCS_instance number> is used by the NIM server ofAIX.

c) Edit the instance profile of the central services instance.d) Set rdisp/msserv to 0.e) Set rdisp/msserv_internal to the port number assigned to rdisp/msserv.

12/04/2006 PUBLIC 81/166


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

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

rdisp/msserv_internal = <free port number>

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

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

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

82/166 PUBLIC 12/04/2006


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

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

6. If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE forAIX 64-bit.

7. Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where <host_name>is the host where the SAPinst GUI is displayed.

4.2.2 Prerequisites before Starting SAPinst: DistributedInstances

If you install a database or a dialog instance on a host other than the central instance, you mustmount directories from the central instance.

Prerequisitesn If you want to install the executables locally instead of sharing them, do notmount the exe

directory 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 153].

Procedure1. Log on to the central instance host as user root and export the following directories with root

access to the dialog instance host:<sapmnt>/<SAPSID>/exe

<sapmnt>/<SAPSID>/profile

<sapmnt>/<SAPSID>/global

For more information, seeMounting Directories via NFS for AIX [page 70].

12/04/2006 PUBLIC 83/166

4 Installation4.3 Installing an SAP System Using SAPinst

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

2. Log on to the distributed instance host as user root.3. Create the following mount points and mount them from the central instance host:

<sapmnt>/<SAPSID>/exe

<sapmnt>/<SAPSID>/profile

<sapmnt>/<SAPSID>/global


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 the

virtual host name when you run SAPinst [page 85].

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 85]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 92]n Performing a Remote Installation with SAPinst (Optional) [page 94]n Starting SAPinst GUI Separately (Optional) [page 95].n Entries in the Services File Created by SAPinst [page 97]

84/166 PUBLIC 12/04/2006


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 running

on the same host. If required, you can instead perform a remote installation with SAPinst [page 94], 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

secure SSL connection to the GUI server and the GUI server connects to SAPinst.

Procedure1. 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 AIX [page 77].

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.

12/04/2006 PUBLIC 85/166


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

$ /sapcd2/IM_HPUX_PARISC/sapinst

n Using an alternative installation directoryIf 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_gui_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)

86/166 PUBLIC 12/04/2006


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

Note

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

l To use global accounts that are configured on a separate host, you have to run theinstallation service Operating System Users and Groups before you start the 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 usage type AS Java or AS ABAP. Youcan choose the usage types or software units on the nextscreen.

12/04/2006 PUBLIC 87/166


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.

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

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:


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.

88/166 PUBLIC 12/04/2006



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 [page48].

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:

https://service.sap.com/instguidesnw2004s 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 154]

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

12/04/2006 PUBLIC 89/166

https://service.sap.com/instguidesnw2004s

https://service.sap.com/instguidesnw2004s


Note

During the installation of the Oracle database instance, SAPinst stops the installation and promptsyou to install the Oracle database software [page 97].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 164].

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.

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

Procedure1. Start SAPinst [page 85].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:

90/166 PUBLIC 12/04/2006


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.

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

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

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 .

12/04/2006 PUBLIC 91/166


4.3.3 Using SAPinst GUI

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

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 without further changing theinstallation files. You can restart SAPinst to continuethe installation 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 95].

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.

92/166 PUBLIC 12/04/2006


The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeatingany of the previous 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 you useCtrl+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.

12/04/2006 PUBLIC 93/166


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.

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

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

./sapinst -nogui

94/166 PUBLIC 12/04/2006


For more information, see Running SAPinst on UNIX [page 85].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 95].

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 94].If SAPinst GUI runs on a different host from SAPinst and the GUI server, you have to start SAPinstGUI separately.

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

Starting SAPinst GUI on a Windows Platform1. 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.

12/04/2006 PUBLIC 95/166


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

96/166 PUBLIC 12/04/2006

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 98].2. You perform steps for the AIX operating system [page 98]3. You run the Oracle Universal Installer [page 99]4. You install the current patch set [page 100]5. You install required interim patches [page 101]

12/04/2006 PUBLIC 97/166


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

scripts as well as the response files.Before starting the Oracle software installation, you need to update this SAP folder so that the

newest versions of the scripts or response files are used.

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

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

4.4.2 Performing Steps for the AIX Operating System

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

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

Procedure1. Run the rootpre.sh script as follows:

a) Log on to the system with user ora<dbsid> if you are not already logged on.b) Change to the directory /oracle/stage/102_32/database/Disk1/rootpre using the following

command:cd /oracle/stage/102_32/database/Disk1/rootpre

c) Make sure that the user root is assigned the environment of ora<dbsid>:su root

d) Call the script rootpre.sh:./rootpre.sh

98/166 PUBLIC 12/04/2006



e) Log off with the user root:exit

2. Remove any currently unused modules in kernel and library memory by entering the followingcommand as user root:# /usr/sbin/slibclean

4.4.3 Running the Oracle Universal Installer

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

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

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.

12/04/2006 PUBLIC 99/166


Prompt or Condition Action

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.

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

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

100/166 PUBLIC 12/04/2006


4 Installation4.5 Installing Application Sharing Server as an Optional Standalone Unit

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

Procedure1. 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.5 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.

Prerequisitesn Make sure you have already installed the current patch set [page 100].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.

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

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.


4.5 Installing Application Sharing Server as an OptionalStandalone Unit

When you install Application Sharing Server as a standalone engine on a dedicated machine, theNetWeaver Java Application Server (AS Java) is also installed. In SAPinst, there are no specific inputscreens for Application Sharing Server; all input screens are related to the installation of the newAS Java.

12/04/2006 PUBLIC 101/166





4 Installation4.5 Installing Application Sharing Server as an Optional Standalone Unit

Note

If you install Application Sharing Server on a machine that already has an AS Java installed, anadditional Java system is installed on that machine. You then have two engines running on themachine. Typically, this is not recommended as Application Sharing Server requires a dedicatedmachine.

Prerequisitesn Make sure that you have read Application Sharing Server as an Optional Standalone Unit [page 35].n Your machine meets the hardware requirements for AS Java.

Procedure1. Start SAPinst [page 84] on the dedicated machine.2. In theWelcome screen, choose <SAP System> Optional Standalone Units Application Sharing Server

<Database> Application Sharing Server Installation .3. To start the installation, choose Next.4. Follow the instructions in the SAPinst dialogs and enter the required parameters.

More InformationPost-Installation Steps for Application Sharing Server [page 125]End of: Enterprise Portal (EP)

102/166 PUBLIC 12/04/2006

5 Post-Installation

5 Post-Installation

Note

Before you perform post-installation steps, make sure that you have read the release notes for thesoftware components that you have installed and that you want to use for your IT scenario. You canfind these release notes on SAP Service Marketplace at:

https://service.sap.com/releasenotes.

You perform the following post-installation steps:

1. You start and stop the SAP system [page 105].2. You log on to the SAP system [page 108].

3.

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

You log on to the portal [page 110].End of: Enterprise Portal (EP);EP Core (EPC)

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

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

Caution


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

Caution


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

Caution


8. You complete and check the Oracle Installation [page 115]

12/04/2006 PUBLIC 103/166

https://service.sap.com/releasenotes



5 Post-Installation

Caution


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

Caution


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

[page 124].

15.

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

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

16.


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

17.


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

18.


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

Caution


End of: HA (UNIX)

19. You ensure user security [page 127].

20.

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 Template Installer [page 130].

104/166 PUBLIC 12/04/2006

5 Post-Installation5.1 Starting and Stopping the SAP System

Caution


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

Integration (PI)

21. You check the Java documentation [page 133] for information that is relevant for running your Java system.22. You may now start with the manual configuration of your IT scenarios for which you find the

appropriate documentation in the SAP Solution Manager [page 135].

5.1 Starting and Stopping the SAP System

You check that you can start and stop the SAP system by running the startsap and stopsap scriptsin the exe directory.

Prerequisitesn You have checked the default profile /<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameter

login/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.n For more information about how to start or stop database-specific tools, see the database-specific

information in this documentation and the documentation from the database manufacturer.n If you want to use startsap or stopsap (for example, in a script) and require the fully qualified

name of these SAP scripts, create a link to startsap or stopsap in the home directory of thecorresponding user.

Caution

If there aremultiple SAP instances on one host ‒ for example, a central instance and a dialoginstance ‒ you must add an extra parameter to the scripts:startsap <instanceID>

stopsap <instanceID>

For example, enter:startsap DVEBMGS00

12/04/2006 PUBLIC 105/166



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)

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

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.

106/166 PUBLIC 12/04/2006


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

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.

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.

12/04/2006 PUBLIC 107/166

5 Post-Installation5.2 Logging On to the SAP System

5.2 Logging On to the SAP System

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

ABAP+Java User

User User Name Storage: ABAP System

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

Prerequisitesn You have already started the SAP system.n You have already installed a front end.

Logging On to the ABAP System1. Start SAP Logon on the host where you have installed the front end as follows:n SAP GUI forWindows:

Choose Start Programs SAP Front End SAP Logon .n SAP GUI for Java:

Choose Start 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.

Logging On to the J2EE EngineYou access the J2EE Engine with a URL using a Web browser from your client machines. To log on tothe J2EE engine for the first time, proceed as follows:

1. Establish the default J2EE Engine URL.2. Log on to the J2EE Engine.

108/166 PUBLIC 12/04/2006

5 Post-Installation5.2 Logging On to the SAP System

Establishing the J2EE Engine URL

The default URL consists of the installation host name and the port on which the J2EE Engine islistening. You can use the HTTP or HTTPS protocol; HTTPS is relevant if you are using SecureSockets Layer (SSL) communication. To correctly establish the URL, you first have to calculatethe port number as follows:

Protocol Formula

HTTP The HTTP port number is based on the number of the J2EE instance on which youhave installed the J2EE Engine, and is calculated according to the following formula:HTTP Port = 50000 + (100*<instance number>)

ExampleIf the J2EE Engine is installed on J2EE instance number 01, the port number is:J2EE Engine HTTP Port = 50000 + (100 * 1) = 50100

HTTPS The HTTPS port number is calculated according to the following formula:HTTPS Port = 50000 + (100*<instance number>) + 1

ExampleIf the J2EE Engine is installed on J2EE instance number 01:J2EE Engine HTTPS Port = 50000 + (100 * 1) + 1 = 50101

The default J2EE Engine URL looks as follows, depending on the protocol that you are using:<protocol>://<fully qualified j2ee engine host name>:<protocol_port_number>

Example

If you installed the J2EE Engine on host saphost06 and the instance number of your J2EE Engine is 15,enter the following URL: http://saphost06:51500

Logging on to the J2EE Engine

1. Open your Web browser, enter the J2EE Engine URL as described above and choose Enter.The start page of the J2EE Engine appears in the Web browser.

2. Log on by choosing EXAMPLES in the upper right corner of the Web page.3. In theWelcome screen, enter the following information:n User ID: <J2EE Administrator name>

n Password: <J2EE Administrator password>

12/04/2006 PUBLIC 109/166

5 Post-Installation5.3 Logging on to the Portal

Note

To deactivate the J2EE Engine, 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.3 Logging on to the Portal

This procedure applies when you install usage type EPC only and when you install it together withusage type EP.You access the portal with a URL using a Web browser from your client machines. To log on to

the portal for the first time, proceed as follows:

1. Establish the default portal URL.2. Log on to the portal.

Establishing the Portal URLThe 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. To correctly establish the URL, you first have to calculate the port numberas follows:

Protocol Formula

HTTP The HTTP port number is based on the number of the SAP J2EE instance on whichyou have installed the portal, and is calculated according to the following formula:HTTP Port = 50000 + (100*<instance number>)

ExampleIf the portal is installed on J2EE instance number 01, the port number is:Portal HTTP Port = 50000 + (100 * 1) = 50100

HTTPS The HTTPS port number is calculated according to the following formula:HTTPS Port = 50000 + (100*<instance number>) + 1

ExampleIf the portal is installed on J2EE instance number 01:Portal HTTPS Port = 50000 + (100 * 1) + 1 = 50101

The default portal URL looks as follows, depending on the protocol that you are using:<protocol>://<portal host name>:<protocol_port_number>/irj

110/166 PUBLIC 12/04/2006

5 Post-Installation5.4 Installing the SAP License

Example

If the portal is installed on a computer identified on the network as PORTAL01, and the J2EE instancenumber is 16, enter the following address:

<protocol>://Portal01.sap.corp:51600/irj

Logging on to the PortalUser names and passwords are registered in a directory server or a user list. When you log on to theportal for the first time, there is no directory server or user list associated with the portal. To connectto a user list, you have to create a user management configuration. Until you establish a connectionwith a user list, you log on to the portal using a default user. The default user is the J2EE systemadministrator. You provided the user name and password for this user during the SAP system installation.

Note

The default user logon provides you with access to the portal as administrator (super user). Afteryou have logged on, you can work as a portal administrator using your own name and password.To do so, make sure that you are registered in the directory server or user list to which your

security configuration points and that you are associated with the portal administrative role. Afterthe first logon, you access the portal with your own name and password.

Procedure

1. Open your Web browser, enter the portal URL as described above and choose Enter.2. In theWelcome screen, enter the following information:n User ID: <J2EE Administrator name>

n Password: <J2EE Administrator password>

Once you have logged on to the portal, the installation phase is complete. The portal is now readyto be configured for your chosen IT scenario.

3. Configure the portal as described in SAP Library at:https://help.sap.com/nw2004s SAP NetWeaver Library Technology Consultants Guide Running an

Enterprise Portal <your scenario variant>

Troubleshooting

If the iViews are not displayed correctly, or if the portal does not launch, see Troubleshooting for Usage TypeEnterprise Portal (EP) [page 165].End of: Enterprise Portal (EP);EP Core (EPC)

5.4 Installing the SAP License

Caution


12/04/2006 PUBLIC 111/166




5 Post-Installation5.5 Installing the SAP Online Documentation

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

Caution

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

your system.

ProcedureFor information about the installation procedure for the SAP license, see:

https://help.sap.com/nw2004s SAP NetWeaver SAP NetWeaver Library Technology Consultant'sGuide Cross-NetWeaver Configurations SAP License Key

More InformationFor more information about SAP license keys, see SAP Service Marketplace athttps://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 https://help.sap.com/nw2004s.

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


112/166 PUBLIC 12/04/2006




https://service.sap.com/licensekey






5 Post-Installation5.7 Performing Initial ABAP Configuration

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.Formore information, see SAP ServiceMarketplace at https://service.sap.com/remoteconnection.

5.7 Performing Initial ABAP Configuration

Caution


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

Procedure1. Go to the following place in the SAP Library:

https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability2. 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 .

12/04/2006 PUBLIC 113/166

https://service.sap.com/remoteconnection






5 Post-Installation5.7 Performing Initial ABAP Configuration

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.

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 Activating and configuring the integrated Internet Transaction Server (ITS)l For more information on activating and configuring the ITS, which is installed

automatically with the SAP kernel, see Application Platform by Key Capability ABAP TechnologyUI Technology ITS / SAP@Web Studio (BC-FES-ITS) .

l For more information about ITS, see SAP Note 742048, where you can find the necessaryinformation if you do not want to use the ITS.

n Maintaining address dataFor 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 .

114/166 PUBLIC 12/04/2006


5 Post-Installation5.8 Completing and Checking the Oracle Database Installation

5.8 Completing and Checking the Oracle Database Installation

Caution


The following tasks need to be executed to ensure the availability of important database tools andto complete the Oracle database installation.

Caution

An Oracle SAP database has to be run in archive log mode. Only this mode guarantees recovery aftersystem failure. The database archive logs are written to the directory /oracle/<DBSID>/oraarch.If the file system containing the archive directory is full, all database transactions are stopped(archiver stuck). Use the tool brarchive to save the archives on tape. For more information, seethe documentation SAP Database Administration: Oracle that is part of the Online Documentation.

Checking Database Utilities brbackup and brarchiveExecute the following steps in order to check whether the database utilities brbackup and brarchive

are installed correctly:

1. Log on as UNIX user ora<dbsid>2. Verify that the database is running.3. Start an online backup of a single database file (control file) to disk:

brbackup –u / —d disk –t online –m 0 -c

4. One of the following messages appears:

n BRBACKUP terminated successfully

n BRBACKUP terminated successfully with warnings

5. Start a dummy backup (query mode) of offline redo log files:brarchive -u / —d disk –v scratch –q -c

6. One of the following messages appears:

n BRARCHIVE terminated successfully

n No offline redo log files found for processing

BRARCHIVE terminated successfully with warnings

If brarchive or brbackup did not terminate successfully, refer to the documentation SAP DatabaseAdministration: Oracle (supplied on the Online Documentation CD / DVD) to analyze error messages and toobtain information on how to solve the problems.

Restricting DB Access to Specific HostsIf 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.

12/04/2006 PUBLIC 115/166


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

Improving the Performance of the DatabaseApply parameter settings as described in SAPNote 830576 to improve the performance of the database.

More Informationn For information onOracle database configuration, see the documentation SAP Database Guide:

Oracle (BC-DB-ORA-DBA) in the SAP Library at https://help.sap.com/nw2004s SAP NetWeaverLibrary SAP NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide ServicesDatabase Support 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 athttps://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability

Application Platform by Key Capability Platform-Wide Services Database Support 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.

Caution

Before you apply support packages, make sure that you have read the release notes for SAPNetWeaver, available on SAP Service Marketplace at https://service.sap.com/releasenotes.

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

Caution

You must have applied all ABAP Support Packages, before you run CTC online configuration.

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 2004s. JSPM uses the Software

Deployment Manager (SDM) to apply support packages and patches and to deploy softwarecomponents.For more information about JSPM and how to use it, see https://help.sap.com/nw2004s SAP

NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SoftwareLife Cycle Management Software Maintenance Java Support Package Manager

116/166 PUBLIC 12/04/2006














5 Post-Installation5.10 Performing the Client Copy

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.

Procedure1. 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:https://service.sap.com/sp-stacks

For up-to-date release information on Support Package Stacks, see the documentation SAPNetWeaver 2004s ‒ Support Package Stack Guide <current version> on SAP Service Marketplace athttps://service.sap.com/MaintenanceNW2004s.

b) Alternatively, you can download Support Packages from SAP Service Marketplace at:https://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:https://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:https://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.

12/04/2006 PUBLIC 117/166









https://service.sap.com/MaintenanceNW2004s



https://service.sap.com/patches



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



https://service.sap.com/noteassistant



5 Post-Installation5.11 Performing a Full Installation Backup

Client 000 is the SAP reference client for ABAP.If you chose to install an ABAP+Java system in one installation run, AS Java was configured against

client 001 during the installation.Your production client must be a copy of the SAP reference client 000. For more information,

see Setting Up a Different Production Client [page 26]


Caution

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

End of: Process Integration (PI)

Procedure1. 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:https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability

Solution Life Cycle Management by Key Capability Software Lifecycle Management Software Logistics Change andTransport System 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.

118/166 PUBLIC 12/04/2006





5 Post-Installation5.11 Performing a Full Installation Backup

You need to back up the following directories and files:

n All database-specific directoriesn All SAP-specific directories:

l /usr/sap/<SAPSID>

l /usr/sap/trans

l <sapmnt>/<SAPSID>

l Home directory of the user <sapsid>admn 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.

Prerequisitesn If required, you have completed client maintenance, such as the client copy [page 117].n You have logged on [page 108] as user <sapsid>adm and stopped the SAP system and database [page 105].n This procedure works on all hardware platforms. For more information on operating

system-specific backup procedures, see your operating system documentation.

Backing Up the Installation1. 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 Backup

Caution

Check for modifications in the existing parameter files before you overwrite them when restoringthe backup.

1. Log on as user root.2. Restore the data that you previously backed up:n Restoring the data from tape:

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

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

12/04/2006 PUBLIC 119/166

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

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 120].n You perform quick tests for Adobe Document Services (ADS) [page 120].

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 in

the ABAP system, as described below.

Assigning Role SAP_BC_FP_ICF to ADS_AGENT1. 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 ADSUSER1. Log on to the ABAP system [page 108].2. Call transaction PFCG.3. Enter ADSCallers in the Role field.4. Choose Role Create .5. On the Create Roles screen, choose Role Save .6. Choose the User tab and assign the user ADSUSER in the User ID field.

5.12.2 Installation Check and Quick Tests for AdobeDocument Services

This procedure shows you how to check your installation of Adobe Document Services (ADS) entriesfor the correct user, security role, passwords, and RFC destination.

120/166 PUBLIC 12/04/2006

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

Note

This procedure contains only minimal configuration steps to check if the ADS installation withSAPinst was successful.For detailed configuration documentation, see the configuration guide for Adobe Document

Services:

n On SAP Service Marketplace at:https://service.sap.com/adobe SAP Interactive Forms by Adobe Media Library Documentation

Adobe Document Services - Configuration Guide NW 2004s

n In the SAP Library at:https://help.sap.com/nw2004s SAP NetWeaver Library Technology Consultant's Guide

Cross-NetWeaver Configurations Adobe Document Services - Configuration .

Checking the User and Password1. Open a web browser and enter the following URL:

http://<J2EE_host>:<J2EE_port>/AdobeDocumentServices/Config

Note

Note that the entries in the URL are case-sensitive.

The web page of the Web service AdobeDocumentServices is displayed.2. Choose Test.3. Choose rpdata(test...).4. Choose Send without entering any parameters.5. Enter ADSUser as user name and the password you previously entered for this user .6. Choose Submit.

If the setup is correct, the system displays the version number in the response area.

Note

You can ignore the message Required stream: “PDFDocument” not found.

If the setup is not correct, the page does not change and Submit remains on the screen.

Checking the ABAP Connection1. Log on to your SAP system.2. Call transaction SE38.3. Enter the name of the test report FP_PDF_TEST_00.4. Choose Execute ( F8 ).

If the setup is correct, the system displays the version number. Otherwise, the system displays adialog box with input fields for the user and password. In this case, check your settings for theABAP connection.

12/04/2006 PUBLIC 121/166

https://service.sap.com/adobe






5 Post-Installation5.13 Performing Post-Installation Steps for Composite Application Framework Core (CAF Core)

TroubleshootingIf the tests are not successful, you might have to make some adjustments to the initial technicalconfiguration for ADS [page 146].

5.13 Performing Post-Installation Steps for CompositeApplication Framework Core (CAF Core)

In SLD1. In the System Landscape Directory (SLD), create a new project.2. Create a new software component (SC) to be developed.3. Create software components of the build plug-ins for the dependent development component

(DC). They are:

Archive Names

BI-MMR CAF-KM EPBC2 SAP_JTECHS

BI_UDI CAF-UM EP-PSERV SAP_PRT

BI-REPPLAN EC-JSTARTUP KMC-CM SAP-EU

BI-WDALV EP_BUILDT LM-TOOLS SAP-JEE

CAF EPBC SAP_BUILDT UWLJWF

Note

Only create SCs if they are missing from the project. These will be used when importing intoChange Management Service (CMS).

4. Define the build plug-in dependencies created in step 3 above.5. Define the SC dependencies created in step 2 above.

Note

When importing SLD content downloaded from SAP Service Marketplace into your NWDIlandscape, you also import necessary dependencies. There you can skip step 5.The SLD content can be downloaded from the SMP at: https://service.sap.com/patches

Entry by Application Group Support Packages and Patches Additional Components SAP Master Data forSLD SAP Master Data for SLD 2.0 .

122/166 PUBLIC 12/04/2006




5 Post-Installation5.13 Performing Post-Installation Steps for Composite Application Framework Core (CAF Core)

In CMSNote

For all documents referenced in this section, see the administration chapter of the SAP NetWeaver JavaDevelopment Infrastructure. You can find this documentation at https://help.sap.com/nw2004s

SAP NetWeaver Library Administrator's Guide Technical Operations Manual for SAP NetWeaver Administrationof SAP NetWeaver Systems Development Infrastructure .

1. In CMS, identify or create a domain.See Change Management Service Configuring Domains .

2. Identify an existing track or create a new track for composite application development inLandscape Configurator Creating a Development Track .

3. Add the SC created in step 2 in the section above to the track.4. Add the runtime system of the track.

See Landscape Configurator Creating a Development Track Configuring Runtime Systems .5. Check in the archives listed in the table below.

Archive Names

BI-MMR CAF-KM EPBC2 SAP_JTECHS

BI_UDI CAF-UM EP-PSERV SAP_PRT

BI-REPPLAN EC-JSTARTUP KMC-CM SAP-EU

BI-WDALV EP_BUILDT LM-TOOLS SAP-JEE

CAF EPBC SAP_BUILDT UWLJWF

6. Import the archives into the track.Fore more information, go to https://help.sap.com/nw2004s SAP NetWeaver LibraryAdministrator's Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaverSystems Development Infrastructure SAP NetWeaver Development Infrastructure Working with the SAPNetWeaver DI Administration of the SAP NetWeaver DI Transports with the NWDI Imports .

More InformationThe Composite Application Framework (CAF) Core Configuration Guide contains additional detailsabout setting up your CAF environment. You can find it at: https://help.sap.com/nw2004s SAPNetWeaver Library Technology Consultant's Guide Developing, Configuring and Adapting Applications CreatingComposite Applications Composite Application Framework Core Configuration Guide

12/04/2006 PUBLIC 123/166










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

5.14 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 https://help.sap.com/nw2004s SAP NetWeaver

Library IT Scenarios at a Glance Enterprise Knowledge Management Documentation, Manuals and TrainingMaterials Management .The SAP Internet Knowledge Servlet (IKS) is a Java servlet based on the J2EE Engine. It is used to

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

Procedure1. Create a user of type system in your ABAP system using transaction SU01 and assign this user to

the role SAP_KM_KW_RFC_CPIC_USER.This user is needed for the connection between the SAP IKS and the ABAP system.

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.

124/166 PUBLIC 12/04/2006


5 Post-Installation5.16 Post-Installation Steps for Usage Type Process Integration (PI)

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

5.15 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.16 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.

5.16.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 2004s at https://service.sap.com/sld Media Library .End of: Process Integration (PI)


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

12/04/2006 PUBLIC 125/166


https://service.sap.com/sld



5 Post-Installation5.18 High Availability: Post-Installation Steps

https://help.sap.com/nw2004s SAP NetWeaver SAP NetWeaver by Key Capability PeopleIntegration Collaboration Administration Guide Real-Time Collaboration Configuring Real-Time CollaborationConfiguring the Application Sharing Server (RTC) .This documentation includes information on how you define which Application Sharing Server

the portal must use.If you do not intend to use Application Sharing Server, you can disable it. For more information,

see:https://help.sap.com/nw2004s SAP NetWeaver SAP NetWeaver by Key Capability People

Integration Collaboration Administration Guide Real-Time Collaboration Configuring Real-Time CollaborationConfiguring the Application Sharing Server (RTC) Enabling / Disabling the Application Sharing Server (RTC) .End of: Enterprise Portal (EP)


5.18 High Availability: Post-Installation Steps

5.18.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 111]. 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 solutions

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

this case you must have two licenses, which you can install in parallel. There is no license problemwhen only the database is switched over.

Procedure1. Execute the following as user <sid>adm on the primary and secondary node where the ABAP SCS

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

126/166 PUBLIC 12/04/2006



5 Post-Installation5.19 Ensuring User Security

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:https://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.

ResultThe license is no longer a problem during switchover. This means you do not need to call saplicensein your switchover scripts.

5.18.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 exports

and 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

allows transparent operation in the event of a switchover.End of: HA (UNIX)

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

12/04/2006 PUBLIC 127/166





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:https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability

Security Network and Transport Layer Security

Caution

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

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

ProcedureFor the users listed below, take the precautions described in the relevant SAP security guide, whichyou can find on SAP Service Marketplace at https://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 ‒

128/166 PUBLIC 12/04/2006




https://service.sap.com/securityguide




ABAP+Java Users

User User Name Comment

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

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.


12/04/2006 PUBLIC 129/166

5 Post-Installation5.20 Running the Template Installer

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

Guest The name that you gave this userduring the installation or the defaultname J2EE_GUEST

‒

Communication user forthe J2EE Engine

The name that you gave this userduring the installation or the defaultname SAPJSF

‒

ADSUSER User exists at least in the clients 000 and001 of the ABAP system.

Users for AdobeDocument Services (ADS)

ADS_AGENT User exists at least in the clients 000 and001 of the ABAP system.

Data supplier userfor System LandscapeDirectory (SLD) (optional)

The name that you gave this userduring the 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.


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

(MI);Process Integration (PI)

5.20 Running the Template Installer

This section provides information about how to run the Template Installer for the SAP NetWeaverusage types.

130/166 PUBLIC 12/04/2006


Note

You can run the Template Installer only once and only directly after the installation.You cannot use the configuration template 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 135].You can also find configuration documentation in the Technology Consultant's Guide in the

SAP Library at:https://help.sap.com/nw2004s SAP NetWeaver Technology Consultant's Guide

For more information about how to start the Template Installer, see the SAP Library at:https://help.sap.com/nw2004s SAP NetWeaver Library Technology Consultant's Guide Developing,

Configuring, and Adapting Applications Creating Java Applications Using Web Dynpro J2EE Engine ConfigurationTemplate Installer

Note

For more information on the Template Installer and its limitations, see SAP Note 923359.

Only valid for: Application Server (AS)

Usage Type: Application ServerAfter SAPinst has finished, you need to run the following configuration templates using the TemplateInstaller to automatically configure the SAP NetWeaver Administrator (NWA):

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

12/04/2006 PUBLIC 131/166









Note

For more information about the NetWeaver Administrator, seehttps://service.sap.com/operationsnw2004s Monitoring Monitoring Setup

Guide for NW 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 template PIPostInstallProcess using the TemplateInstaller. To select the template, 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 Template Installer has finished, you need to restart your SAP system.



Usage Type: BI Java Components (BI-Java)After SAPinst has finished, you need to run the configuration template BIPostInstallProcessusing the Template Installer.End of: BI Java Components (BI-Java)

Only valid for: Development Infrastructure (DI)

Usage Type: Development InfrastructureAfter SAPinst has finished, you need to run the configuration template for usage typeDI using theTemplate Installer.

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.

132/166 PUBLIC 12/04/2006

https://service.sap.com/operationsnw2004s




5 Post-Installation5.21 Checking the SAP Java Documentation

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 template 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 template, choose Execute Template.e) Choose the items that you need from Design Time Repository Configuration, Component Build Service,

and Change Management Service.

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 Template Installer has finished, you might have to restart the engine as describedin SAP Note 919942.

End of: Development Infrastructure (DI)

Only valid for: Mobile Infrastructure (MI)

Usage Type: Mobile InfrastructureAfter SAPinst has finished, you need to run the configuration template MI Post Installation

Process using the Template Installer.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.21 Checking the SAP Java Documentation

Here you can find information about the configuration of the J2EE Engine and about SAP Javatechnology in the SAP Library.

12/04/2006 PUBLIC 133/166



5 Post-Installation5.21 Checking the SAP Java Documentation

Procedure1. Go to the following place in the documentation:

https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key CapabilityApplication Platform by Key Capability Java Technology .

2. Check the following documentation for information relevant to running your Java system:

Manual Contents

Architecture Manual This manual describes the architecture of a Java or ABAP+Java system. Itcontains information 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 .

134/166 PUBLIC 12/04/2006




5 Post-Installation5.22 Accessing Configuration Documentation in the SAP Solution Manager

Manual Contents

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:

https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key CapabilitySolution Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) J2EE EngineProblem Analysis Scenarios

5.22 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 2004s usage types you can also find configuration documentation in theTechnology Consultant's Guide at: https://help.sap.com/nw2004s SAP NetWeaver Library TechnologyConsultant's Guide

Prerequisitesn You have installed an SAP Solution Manager system as described in the documentation Installation

Guide ‒ 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 the

documentation Configuration Guide ‒ SAP Solution Manager <3.2 or 4.0>.

For more information, see SAP Service Marketplace at https://service.sap.com/instguides

SAP Components SAP Solution Manager Release <3.2 or 4.0> .

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

12/04/2006 PUBLIC 135/166







https://service.sap.com/instguides



5 Post-Installation5.22 Accessing Configuration Documentation in the SAP Solution Manager

c) Create a project structure and add the required scenarios for your SAP system to your projectstructure with the Business Blueprint transaction SOLAR01,

d) Add your SAP system configuration structures to your project structure with the configurationtransaction SOLAR02.

For more information about creating projects, assigning scenarios to projects, and creatingconfiguration structures, see:https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability Solution

Life Cycle Management by Key Capability SAP Solution Manager Using the SAP Solution Manager in Projects3. 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 2004s .

ResultYou can now configure your SAP system according to the configuration documentation in theSAP Solution Manager.

136/166 PUBLIC 12/04/2006




6 Additional Information

6 Additional Information

The following sections provide additional information about optional preparation andpost-installation tasks:

Preparation

n Installation of Multiple Components in One Database [page 137]n Integration of LDAP Directory Services [page 139]n Preparing User Management with an External ABAP system [page 142]

Post-Installation

n If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access[page 145].

n Configuring User Management to Use an LDAP Directory [page 145].n Usage Type-Specific Initial Technical Configuration [page 145]n Heterogeneous SAP System Installation [page 153]n Deleting an SAP System [page 154]n Troubleshooting [page 164]

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.

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.

12/04/2006 PUBLIC 137/166

6 Additional Information6.1 Installation of Multiple Components in One Database (Optional)

Using this technology is as easy as installing a separate component. No extra effort is requiredbecause the MCOD installation is fully integrated into the standard installation procedure. MCOD isnot an additional 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

Prerequisitesn For more information on MCOD and its availability on different platforms, see the SAP Service

Marketplace at https://service.sap.com/mcod.n MCOD is released for Unicode installations. A prerequisite is that the MCOD system contains

Unicode instances only. SAP does not support mixed solutions.n Improved sizing required

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

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

ConstraintsRecommendation

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

you mix 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.

138/166 PUBLIC 12/04/2006

https://service.sap.com/mcod






6 Additional Information6.2 Integration of LDAP Directory Services (Optional)

n Automated support in an MCOD landscape for the following administrative tasks depends onyour 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 first SAP system, the database system ID can be different from the SAP system ID.n For the second SAP system, make sure that you use the same DBSID as for the first SAP system.n If you install a system into an existing database (MCOD), make sure that the SYSTEM tablespace

contains at least 350 MB of free space. If there is not enough space left, increase the size of thistablespace with BRSPACE or BRTOOLS.

n If you decide to turn off database logging 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)

The Active Directory is a Lightweight Directory Access Protocol (LDAP) directory. LDAP is a feature ofWindows 2000 or higher that allows important information within a corporate network to be storedcentrally on a server. The advantage of storing information centrally for the entire network is thatyou have to maintain data only once, thus avoiding redundancy and inconsistency.If an LDAP directory is available in your corporate network, you can configure the SAP system

to use this feature. For example, a correctly configured SAP system can read information fromthe directory and also store information there.This section explains the benefits of using the SAP system with the LDAP directory. In addition, it

gives an overview of the configuration steps required to use an SAP system with the directory.

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.

12/04/2006 PUBLIC 139/166





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 Microsoft Management Console (MMC)

For more information on the automatic registration of SAP components in LDAP directories andthe benefits of using it in SAP Logon and MMC, see the documentation SAP System Information inDirectory Services on SAP Service Marketplace at https://service.sap.com/msplatforms MicrosoftWindows Server

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.

140/166 PUBLIC 12/04/2006

https://service.sap.com/msplatforms




MMC

The MMC is a graphical user interface (GUI) for administering and monitoring SAP systems froma central location. If the SAP system has been prepared correctly, the 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 MMC. It can read

system information straight from the directory that automatically registers changes to the systemlandscape. As a result, up-to-date information about all SAP application servers, their status, andparameter settings is always available in the MMC.If you need to administer distributed systems, we especially recommend that you use the MMC

together with Active Directory services. For example, you can simplify administration by using theMMC in a distributed environment that implements the mySAP Business Suite components. You cankeep track of significant events in all of the systems from a single MMC interface. You do not needto manually register changes in the system configuration. Instead, such changes are automaticallyupdated in the directory and subsequently reflected in the MMC.

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

of SAP-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 Windows

installation guide for your SAP system solution and database.

Configuration Tasks for Generic LDAP Directories

To prepare the SAP system to use generic LDAP services, you must perform the following steps:

1. You configure the LDAP directory to store SAP data.This involves extending the directory schema and creating a container for the SAP data.

2. You set up a user with a password on the server where the SAP system is running to permit thesystem to access and modify the LDAP directory.You do this by running the script ldappasswd.

For more information on how to enable interaction between a generic LDAP directory and the SAPsystem, see the documentation SAP System Information in Directory Services in the SAP Service Marketplaceat: https://service.sap.com/msplatforms Microsoft Windows Server

12/04/2006 PUBLIC 141/166




6 Additional Information6.3 Preparing User Management for an External ABAP System

6.3 Preparing User Management for an External ABAP System

For a Java system, you can also deploy user management for an external ABAP system. In this case,you configure the User Management Engine (UME) of the J2EE Engine for the user managementof a separate ABAP system.If you want to connect more than one Java system to the same ABAP system, you need to work out

a concept for the communication, administrator, and guest users for each engine.You can take one of the following approaches:

Approach Advantages Disadvantages

Each Java system uses differentusers

No interdependencies between theconnected engines

Initially more administration tocreate the users in the ABAP system

All Java systems use the sameconfiguration

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

Interdependencies between theconnected engines:n If you change the password of

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

n If you change the administratoruser’s password, you must alsochange the password in securestorage on all of the connectedJ2EE Engines

Recommendation

For security reasons, we recommend the first approach.

The procedures below assume that you are using the first approach.

Prerequisitesn The ABAP system is based on at least SAP Web AS ABAP release 6.20 SP25.n In transaction PFCG, check that the roles SAP_BC_JSF_COMMUNICATION and

SAP_BC_JSF_COMMUNICATION_RO exist and make sure that their profiles are generated.n In transaction PFCG, check that the roles SAP_J2EE_ADMIN, SAP_J2EE_GUEST and SAP_BC_FP_ICF

exist. Neither role contains any ABAP permissions, so you do not need to generate any profiles.n In transaction PFCG, create a role named ADSCallers. You do not need to maintain authorization

data or generate any profiles for that role.n For more information, see:

https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key CapabilitySecurity Identity Management User Management Engine

142/166 PUBLIC 12/04/2006





Note

For more information about role maintenance, see the SAP Library athttps://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability

Security Identity Management Users and Roles (BC-SEC-USR) SAP Authorization Concept OrganizingAuthorization Administration Organization if You Are Using the Profile Generator Role Maintenance RoleMaintenance Functions Changing Standard Roles

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

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

Recommendation

We recommend that you assign this user the role SAP_BC_JSF_COMMUNICATION_RO for read-only(display) access to user data with Java tools. If you intend to maintain user data (that is, to change,create, or delete users) with Java tools, you need to assign the role SAP_BC_JSF_COMMUNICATIONinstead.We recommend that you name the user SAPJSF_<SAPSID_Java_System>.You can use any password.

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

2. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_ADMIN. This is youradministrator user in the J2EE Engine.

Recommendation

We recommend that you name the user J2EE_ADM_<SAPSID_Java_System>. You can use anypassword.

Caution

Log on to the SAP system once with this user to change its initial password. Because the installerof the J2EE Engine verifies this password, the installation fails if this password is initial

3. In transaction SU01 create a new dialog user and assign it to role SAP_J2EE_GUEST. This is yourguest user in the J2EE Engine.

12/04/2006 PUBLIC 143/166





Recommendation

We recommend that you name the user J2EE_GST_<SAPSID_Java_System>. You can use anypassword.As this user is only used for anonymous access to the system, we recommend you to deactivatethe password and, if required, lock it after installation to prevent anyone from using it for explicitnamed logons.

4. In transaction SU01 create the following dialog users :

Caution

Youmust have changed the initial passwords [page 127] of these users before you start the installation ofthe Java system.

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

In transaction PFCG, assign the role ADSCallers to this user.l ADS_AGENT:

In transaction PFCG, assign the role SAP_BC_FP_ICF to this user.n SLD Data supplier user (optional):

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

Recommendation

We recommend that you name this user SLDDSUSER

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

Recommendation

We recommend that you name this user SLDAPIUSER

Note

For more information on SLD users and security roles, see the Post-Installation Guide - SLD of SAPNetWeaver 2004s at https://service.sap.com/sld Media Library .

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

144/166 PUBLIC 12/04/2006




6 Additional Information6.4 Creating a User for LDAP Directory Access (Optional)

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

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

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 installation

guide for your SAP system solution and database.

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

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

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/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability

Security Identity Management User Management Engine UME Configuration UME Data Sources LDAPDirectory as Data 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 some of these steps manually after SAPinst has

12/04/2006 PUBLIC 145/166




6 Additional Information6.6 Usage Type-Specific Initial Technical Configuration

finished, depending on your installation scenario. The following usage type-specific sections providethe required information:

n Application Server Java (AS Java) [page 146]

n


EP Core (EPC) and Enterprise Portal (EP) [page 148]End of: Enterprise Portal (EP);EP Core (EPC)

n


Business Intelligence (BI Java) [page 151]End of: BI Java Components (BI-Java)

n


Process Integration (PI) [page 149]End of: Process Integration (PI)

6.6.1 Initial Technical Configuration for Application Server

SAPinst performs initial technical configuration steps for the AS Java functional units listed belowduring the 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 functional unit-specific sections:

n Adobe Document Services (ADS) [page 146]n Composite Application Framework (CAF) [page 147]n Connection to System Landscape Directory (SLD) [page 147]

6.6.1.1 Initial Technical Configuration for Adobe DocumentServices

SAPinst automatically performs initial technical configuration steps specific to Adobe DocumentServices (ADS) during the installation.However, you have to perform some of these steps manually if:

n You have installed AS Java on a separate host and want to use ADS for a standalone ABAP system.n You want to change existing parameters or you want to set additional parameters.

FeaturesDepending on your installation scenario, you might have to perform one ore more of the followingsteps:

146/166 PUBLIC 12/04/2006


n Create user ADSUser for basic authentication.

n Create service user ADS_AGENT in the ABAP environmentn Create a web service destination

n Create an HTTP destination for ADS.

n Create an RFC destination for ADS.

You can find a detailed description of the manual procedure for these steps in section Configuring theWeb Service in the Adobe Document Services Configuration Guide, which you can find:

n On SAP Service Marketplace at:https://service.sap.com/adobe SAP Interactive Forms by Adobe Media Library Documentation

Adobe Document Services - Configuration Guide NW 2004s

n In the SAP Library at:https://help.sap.com/nw2004s SAP NetWeaver Library Technology Consultant's Guide

Cross-NetWeaver Configurations Adobe Document Services - Configuration .

6.6.1.2 Initial Technical Configuration for CompositeApplication Framework Core

During the installation, SAPinst automatically performs initial technical configuration steps specificto the Composite Application Framework Core (CAF). However, you have to perform some of thesesteps manually if you want to change existing parameters or you want to set additional parameters.Depending on your installation scenario, you might have to perform the following steps:

n Creating roles CAFAdmin and CAFUIAdmin

n Setting configuration parameters

For more information about your installation scenario and the steps you have to perform, see theSAP Library at: https://help.sap.com/nw2004s SAP NetWeaver Library Technology Consultant'sGuide Developing, Configuring, and Adapting Applications Creating Composite Applications Composite ApplicationFramework Core Configuration Guide

6.6.1.3 Configuring the Connection for System LandscapeDirectory

SAPinst automatically configures the connection for System Landscape Directory according to theparameters you entered on the related SAPinst screens during the input phase. However, you haveto perform some of these steps manually if you want to change existing parameters or if you wantto set additional parameters.You can now configure your SAP System for SLD as follows:

n As an SLD server (and client)

12/04/2006 PUBLIC 147/166











n As an SLD client

For more information, see:Configuration of Data Suppliers in the documentation Post Installation Guide ‒ System Landscape Directory SAP

NetWeaver 2004s on SAP Service Marketplace at https://service.sap.com/installNW2004s

Configuration .


6.6.2 Initial Technical Configuration for the Portal

This section applies when you install usage type EPC only and when you install it together withusage type EP.SAPinst automatically performs initial technical configuration steps that are specific for usage type

EPC and EP during the installation.However, you might have to perform some of 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.

The following steps might be affected:

n Copying CMS_MAPPING Properties

n Renaming InitialPermissions.xml.templaten Renaming initialPermissionsKMC.xml.template

Copying CMS_MAPPING Properties1. 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.template1. Go to directory


servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl .2. Rename file initialPermissions.xml.template to initialPermissions.xml.

148/166 PUBLIC 12/04/2006






Renaming initialPermissionsKMC.xml.template1. Go to directory


servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl

2. Rename file initialPermissionsKMC.xml.template to initialPermissionsKMC.xml.

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


6.6.3 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 2004s SR2.n You have installed usage type PI as an additional usage type to an existing SAP system as described

in SAP Note 883948.


n Import the SAP Exchange profile [page 149]n Assign SAP_ALL Rights to User PISUPER [page 150]n Activate the ICF Services [page 150]n Assign roles to groups [page 151]n Run the configuration template installer for usage type PI [page 130]

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

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

50000, for example, if your J2EE instance is 002. Enter the logon information:

User Name: PISUPER

12/04/2006 PUBLIC 149/166



Password: <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.3.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.

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

150/166 PUBLIC 12/04/2006


ProcedureTo activate the ICF services, call transaction SE38 and execute the reportRSXMB_ACTIVATE_ICF_SERVICES. For more information, see SAP Note 736312.

6.6.3.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_ADMINISTRATOR1. 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.



6.6.4 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 2004s SR2.n You have installed usage type BI Java as an additional usage type to an existing SAP system as

described in SAP Note 883948.


12/04/2006 PUBLIC 151/166




n Configure BI Java Information Broadcasting [page 152]n Process Chains: Transport texts for alert category [page 152]n Rename initialPermissionsBI.xml.template [page 153]n Run the configuration template installer for usage type BI Java [page 130]

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

Note

For the installation of SAP NetWeaver 2004s BI Content Add-On 2 or higher on the AS ABAPsystem, see SAP Note 847019.

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

152/166 PUBLIC 12/04/2006




6 Additional Information6.7 Heterogeneous SAP System Installation

6.6.4.3 Renaming initialPermissionsBI.xml.template

If SAPinst does not rename the initialPermissionsBI.xml.template file automatically, you willneed to rename it yourself.

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

End of: BI Java Components (BI-Java)

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

Note

This section does not apply to installations of SAP instances in a mixed UNIX and MicrosoftWindows environment.If you want to install an application server on Windows in a heterogeneous (UNIX) SAP system

environment, you need to follow the instructions in SAP Note 680617.

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

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.

12/04/2006 PUBLIC 153/166


6 Additional Information6.8 Deleting an SAP System

6.8 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 154]. However, you still have to delete the databasemanually.

n You delete the SAP system manually [page 157].

6.8.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 system make sure that you stop all

remaining instances. Youmust stop the instance with the message server only after having enteredall SAPinst parameters 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 156] 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

SAPinst deletes the database instance but you have to delete the Oracle database software [page 156]manually.

3. Central instance4. Central services instance

Caution

You cannot delete an SAP system remotely.

154/166 PUBLIC 12/04/2006


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 157] or run SAPinst on the NFS server.

6.8.1.1 Running SAPinst to Delete an SAP System

This procedure tells you how to run the Uninstall service of SAPinst.

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

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

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

12/04/2006 PUBLIC 155/166


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 156].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.8.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

in Deleting an Oracle Database Instance [page 162].

Procedure1. 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 minutes beforeyou see the OUI screen.

2. Choose Installed Products or Uninstall Products.3. Select the database schema you want to uninstall, <DBSID>_102_32 or <DBSID>_102_64.4. Mark the Oracle 10G database within the selected product.5. Choose Remove.6. Confirm your selection with Yes.7. Choose EXIT.

156/166 PUBLIC 12/04/2006


6.8.2 Deleting an SAP System ManuallyDeleting a Complete SAP System Manually

1. You delete the SAP instances [page 157] 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 158].3. You delete the Oracle database instance [page 162].

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 159], if there are any.2. You delete the Java part of an SAP system [page 159].3. You delete the central services instance [page 157].4. You delete the Java database schema of your Oracle installation [page 161].

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

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

12/04/2006 PUBLIC 157/166


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

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

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

158/166 PUBLIC 12/04/2006


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: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.8.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.

12/04/2006 PUBLIC 159/166


Caution

This description assumes that you installed the SAP system using SAP standard tools accordingto the installation documentation.

ProcessCaution

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.

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 =

160/166 PUBLIC 12/04/2006


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 157].6. Delete the Oracle Java database schema [page 161].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.8.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.

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.

Prerequisitesn Before deleting the Java database schema, stop all SAP instances belonging to this Java database

schema.n We recommend you to delete the SAP instances before deleting the Java database schema.

ProcedureCaution

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

12/04/2006 PUBLIC 161/166



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

Prerequisitesn Before deleting the database, stop all SAP instances belonging to this database or to this Java

database schema.n We recommend that you delete the SAP instances before deleting the database instance.

Procedure1. 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:

162/166 PUBLIC 12/04/2006




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

12/04/2006 PUBLIC 163/166

6 Additional Information6.9 Troubleshooting

n 32-bit Oracle 10G: rm -rf /oracle/client/102_32

n 64-bit Oracle 10G: rm -rf /oracle/client/102_64

6.9 Troubleshooting

The following section(s) describe the steps that you need to performmanually if SAPinst fails:

n Troubleshooting with SAPinst [page 164]

n


Troubleshooting for Portal Installation [page 165]End of: Enterprise Portal (EP);EP Core (EPC)

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

Procedure1. To view the log file, choose View Logs.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 92].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.

164/166 PUBLIC 12/04/2006


6 Additional Information6.9 Troubleshooting


6.9.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 the portal was not deployed completely.To check the deployment of the portal, proceed as follows :

Procedure1. 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:n If error and log files do not appear, the portal installation has been completed successfully

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

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

12/04/2006 PUBLIC 165/166

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2006 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.

Documents

SAP NetWeaver 2004s SR2 Abapjavaaix Oracle