ADM110+ +SAP+R 3+Enterprise+Installation

ADM110 SAP R/3 Enterprise Installation ADM110

Release 630 05.01.2004

ADM110 SAP R/3 Enterprise Installation ....................................................................................................................0-1

Copyright ..................................................................................................................................................................0-2

Target Audience....................................................................................................................................................0-4

Course Prerequisites..............................................................................................................................................0-5

Course Content......................................................................................................................................................0-6

SAP R/3 Enterprise Architecture, New Features ......................................................................................................1-1

Content and Objectives .........................................................................................................................................1-2

SAP R/3 Enterprise Architecture, New Features ..................................................................................................1-3

SAP R/3 Development Strategy............................................................................................................................1-4

Building Blocks of SAP Systems..........................................................................................................................1-5

Release Strategy of SAP R/3 Enterprise ...............................................................................................................1-6

SAP Web AS 6.20: Architecture and Connectivity...............................................................................................1-7

SAP R/3 Enterprise Architecture, New Features ..................................................................................................1-8

SAP J2EE Engine: Web Access............................................................................................................................1-9

SAP J2EE Engine: Installation Variants .............................................................................................................1-10

SAP R/3 Enterprise Architecture, New Features ................................................................................................1-11

Unicode (1/2) ......................................................................................................................................................1-12

Unicode (2/2) ......................................................................................................................................................1-13

Unicode and SAP Web AS .................................................................................................................................1-14


MCOD (1/2)........................................................................................................................................................1-16

MCOD (2/2)........................................................................................................................................................1-17


Directory Server (1/2) .........................................................................................................................................1-20

Directory Server (2/2) .........................................................................................................................................1-21


New Features with SAPinst ................................................................................................................................1-23

Further Information.............................................................................................................................................1-24

SAP R/3 Enterprise Architecture, New Features: Unit Summary.......................................................................1-25

Installation Planning .................................................................................................................................................2-1


Sizing Your System ..............................................................................................................................................2-3

Sizing is an Ongoing Process ................................................................................................................................2-4

Sizing and Unicode ...............................................................................................................................................2-5

Supported Platforms..............................................................................................................................................2-6

Sizing SAP R/3 4.6C against SAP R/3 Enterprise ................................................................................................2-7

Installation Options ...............................................................................................................................................2-8

Technical Requirements........................................................................................................................................2-9

Network: External Ports Used by SAP Systems .................................................................................................2-10

Network: Load Caused by SAP Communication................................................................................................2-11

Database: Disk Layout and High Availability ....................................................................................................2-12

Recommendations on Database Disk Layout......................................................................................................2-13

SAP System Installation: SID .............................................................................................................................2-14

Database Users for SAP Systems........................................................................................................................2-15

Installation Variants ............................................................................................................................................2-16


Installation Planning: Unit Summary..................................................................................................................2-18

Installation Preparation .............................................................................................................................................3-1


Installation Preparation .........................................................................................................................................3-3

Order Installation CDs ..........................................................................................................................................3-4

Download of Installation Guides...........................................................................................................................3-5

Download Relevant SAP Notes! ...........................................................................................................................3-6

Install SAP Front-End Software............................................................................................................................3-7

Prepare Installation CDs .......................................................................................................................................3-8

Installation Preparation .........................................................................................................................................3-9

Windows File System: NTFS..............................................................................................................................3-10

Windows NT: Update Dynamic Link Libraries ..................................................................................................3-11

Windows: Reducing Size of File Cache..............................................................................................................3-12

Windows: User for Installation ...........................................................................................................................3-13

Windows: SAP System Transport Host ..............................................................................................................3-14

Windows: Preparing SAPinst Installation...........................................................................................................3-15

Windows: Java SDK Installation (1/2)................................................................................................................3-16

Windows: Java SDK Installation (2/2)................................................................................................................3-17

Windows: Environment Variable JAVA_HOME (1/2) ......................................................................................3-18

Windows: Environment Variable JAVA_HOME (2/2) ......................................................................................3-19

Installation Preparation .......................................................................................................................................3-20

UNIX: Checking UNIX Kernel and Swap Space................................................................................................3-21

UNIX: Setting Up File Systems ..........................................................................................................................3-22

UNIX: Preparing SAPinst Installation ................................................................................................................3-23

UNIX: Setting Environment Variables ...............................................................................................................3-24

Preparation Checklist for Windows ...................................................................................................................3-25

Preparation Checklist for UNIX..........................................................................................................................3-26


Installation Preparation: Unit Summary..............................................................................................................3-28

Installation Preparation Exercises .......................................................................................................................3-29

Installation Preparation Installation Preparation Solutions ...............................................................................3-30

Installing SAP GUI ...................................................................................................................................................4-1


Variants of SAP GUI ............................................................................................................................................4-3

Local Installation SAP GUI for Windows (1/3)....................................................................................................4-4



Installing an SAP GUI Installation Server (1/9)) ..................................................................................................4-7

Installing an SAP GUI Installation Server (2/9)....................................................................................................4-8

Installing an SAP GUI Installation Server (3/9)....................................................................................................4-9

Installing an SAP GUI Installation Server (4/9)..................................................................................................4-10






Patching the SAP GUI (1/4)................................................................................................................................4-16




Installing SAP GUI for Java (1/3).......................................................................................................................4-20




Installing SAP GUI: Unit Summary....................................................................................................................4-24

Installing SAP GUI Installing SAP GUI Exercises............................................................................................4-25

Installing SAP GUI Installing SAP GUI Solutions.............................................................................................4-27

Installation Process ...................................................................................................................................................5-1


Installation Process ...............................................................................................................................................5-3

Prerequisites for SAPinst ......................................................................................................................................5-4

Start SAPinst .........................................................................................................................................................5-5

Start Menu Entries ................................................................................................................................................5-6

SAPinst Welcome Screen .....................................................................................................................................5-7

SAPinst Installation Default Parameters ...............................................................................................................5-8

SAPInst Installation Finished................................................................................................................................5-9

Remote Installation with SAPinst .......................................................................................................................5-10

SAPinst - Output Files ........................................................................................................................................5-11

SAPinst Building Blocks.....................................................................................................................................5-12

Appendix: Preparing SAPinst Software ..............................................................................................................5-13

Appendix: SAPinst Input Files: dialog.xml ........................................................................................................5-14

Appendix: SAPinst Input Files: keydb.xml.........................................................................................................5-15

Appendix: SAPinst Input Files: control.xml .......................................................................................................5-16

Appendix: SAPinst Properties.............................................................................................................................5-17

Appendix: Oracle Software.................................................................................................................................5-18

Appendix: Settings for OS Users (AIX Only).....................................................................................................5-19

Installation Process .............................................................................................................................................5-20

Start Installation of the Central Instance .............................................................................................................5-21

Instance Installation Type, SID, Instance Number..............................................................................................5-22

Database Parameters ...........................................................................................................................................5-23

Windows Domain Information and RAM...........................................................................................................5-24

LDAP (Unicode Installation Only) .....................................................................................................................5-25

Instance Directory and Transport Host ...............................................................................................................5-26

Set Passwords for Operating System User ..........................................................................................................5-27

CD Browser and Message Server Port ................................................................................................................5-28

CD Browser: RDBMS CD..................................................................................................................................5-29

Installation Steps .................................................................................................................................................5-30

Finish Central Instance Installation.....................................................................................................................5-31


Preparation for Database Instance Installation....................................................................................................5-33

Start of Database Instance Installation ................................................................................................................5-34

Instance Installation Type and SID .....................................................................................................................5-35

Database Installation Method and Type..............................................................................................................5-36

Database and Central Instance Parameters..........................................................................................................5-37




CD Browser: Kernel, RDBMS and Export CD...................................................................................................5-41

Installation Directory: Database Client Software................................................................................................5-42

Database Parameters and Operation Mode .........................................................................................................5-43

LOG and DATA Devspace Settings, Unicode....................................................................................................5-44

LOG and DATA Devspace Settings, Non-Unicode............................................................................................5-45

SYSTEM Devspace Settings, Unicode ...............................................................................................................5-46

SYSTEM Devspace Settings, Non-Unicode .......................................................................................................5-47

CD Browser: Export CDs....................................................................................................................................5-48

Database Load Parameters, Unicode...................................................................................................................5-49

Database Load Parameters, Non-Unicode...........................................................................................................5-50

Multi National Language Support (Non-Unicode)..............................................................................................5-51


Logfile sapinst.log...............................................................................................................................................5-53

Prepare Multi National Language Support (Non-Unicode) ................................................................................5-54

Change Passwords of ABAP Super Users ..........................................................................................................5-55

Finish Installation of Database Instance..............................................................................................................5-56


SAP J2EE Engine................................................................................................................................................5-58

Preparation for SAP J2EE Engine Installation (1/2) ...........................................................................................5-59

Preparation SAP J2EE Engine Installation (2/2).................................................................................................5-60

Start SAP J2EE Engine Installation ....................................................................................................................5-61

CD Browser ........................................................................................................................................................5-62

Parameters for Java Core ....................................................................................................................................5-63


Finish Installation of SAP J2EE Engine..............................................................................................................5-65


Preparation for Dialog Instance Installation........................................................................................................5-67

Start Dialog Instance Installation ........................................................................................................................5-68

Instance Installation Type, SID, Instance Number..............................................................................................5-69

Central Instance and Database Parameters..........................................................................................................5-70




CD Browser and Message Server Port ................................................................................................................5-74

Database Schema and CD Browser.....................................................................................................................5-75

Parameter for SAP J2EE Engine.........................................................................................................................5-76


Finish Dialog Instance Installation......................................................................................................................5-78

Appendix: Installing Client Software..................................................................................................................5-79


Appendix: Preparation for Gateway Instance Installation (1/2) ..........................................................................5-81

Appendix: Preparation for Gateway Instance Installation (2/2) ..........................................................................5-82

Appendix: Start Gateway Instance Installation ...................................................................................................5-83

Appendix: Installation Parameter........................................................................................................................5-84

Appendix: LDAP ................................................................................................................................................5-85

Appendix: Windows Domain Information and RAM.........................................................................................5-86

Appendix: SAP System Directory.......................................................................................................................5-87

Appendix: Set Passwords for Operating System User ........................................................................................5-88

Appendix: CD Browser and Ports.......................................................................................................................5-89

Appendix: Installation Steps and End of Gateway Installation...........................................................................5-90


Installation Process: Unit Summary....................................................................................................................5-92

Installation Process Installation Process Exercises .............................................................................................5-93

Installation Process Installation Process Solutions.............................................................................................5-98

Post-Installation Activities ........................................................................................................................................6-1


Post-Installation Activities ....................................................................................................................................6-3

Start and Stop the SAP System .............................................................................................................................6-4

Checking SAP System Services............................................................................................................................6-5


SAP License..........................................................................................................................................................6-7

Installing SAP Licenses ........................................................................................................................................6-8


Installing the SAP Online Documentation ..........................................................................................................6-10

General Information to Install the Helpfiles........................................................................................................6-11

Installation of Help Type HtmHelpFile...............................................................................................................6-12

Installation of PlainHtmlHttp, PlainHtmlFile (1/2).............................................................................................6-13

Installation of PlainHtmlHttp, PlainHtmlFile (2/2).............................................................................................6-14

Setup Variants and Browser for Online Help......................................................................................................6-15

Post-Installation Activities ..................................................................................................................................6-16

SAProuter and SAPNet–R/3 Frontend................................................................................................................6-17

Configuring SAProuter and SAPNet–R/3 Frontend............................................................................................6-18

Configuring SAProuter and SAPNet–R/3 Frontend............................................................................................6-19

SAProuter and SAPNet–R/3 Frontend................................................................................................................6-20


Post-Installation Activities for Transport Organizer ...........................................................................................6-22

TMS Configuration: Transport Domain..............................................................................................................6-23

TMS Configuration: Transport Routes ...............................................................................................................6-24

Basic Configuration: Import of Profiles..............................................................................................................6-25

Basic Configuration: Number of Work Processes...............................................................................................6-26

Basic Configuration: Set Up Operation Modes...................................................................................................6-27

Basic Configuration: Background Jobs...............................................................................................................6-28

Basic Configuration: User and Roles ..................................................................................................................6-29

Basic Configuration ............................................................................................................................................6-30


Installation Check ...............................................................................................................................................6-32

Activation of SAP R/3 Enterprise Extension Set ................................................................................................6-33

Installation of Additional Languages (1/3) .........................................................................................................6-35



Language Import: New Features .........................................................................................................................6-38

Implementation of Packages ...............................................................................................................................6-39

Client Copy .........................................................................................................................................................6-40

Client Copy with SAP R/3 Enterprise.................................................................................................................6-41

Perform a Full Backup: Windows.......................................................................................................................6-42

Perform a Full Backup: UNIX ............................................................................................................................6-43

Checking the RFC Destination............................................................................................................................6-44

SAP J2EE Engine................................................................................................................................................6-45

SAP J2EE Engine: User SAPJSF........................................................................................................................6-46

Additional Information for SAP J2EE Engine and SDM....................................................................................6-47

SAP Load Generator (SGEN) .............................................................................................................................6-48

UNICODE Post-Installation Procedure ..............................................................................................................6-49


Windows: SAP Accounts....................................................................................................................................6-51

Installing Administration Tools for a Database ..................................................................................................6-52

Completing and Checking Oracle Installation ....................................................................................................6-53

Informix Administrative Tools ...........................................................................................................................6-54

UNIX: Performing File and Directory Adjustments ...........................................................................................6-55

UNIX: Performing Operating System Adjustments............................................................................................6-56


Post-Installation Activities: Unit Summary ........................................................................................................6-58

Post-Installation Activities Post-Installation Activities Exercises .....................................................................6-59

Post-Installation Activities Solutions ..................................................................................................................6-62

Implementing Patches ...............................................................................................................................................7-1


Applying a Kernel Patch (incl. DB-Dependent Part) ............................................................................................7-3

Applying a Kernel Patch, Screenshots (1/2) .........................................................................................................7-4

Applying a Kernel Patch, Screenshots (2/2) .........................................................................................................7-5

Patching the SAP J2EE Engine (1/2) ....................................................................................................................7-6

Patching the SAP J2EE Engine (2/2) ....................................................................................................................7-7

Apply Support Packages using Transaction SPAM ..............................................................................................7-8

Applying a Database Patch ...................................................................................................................................7-9

Appendix: Installation of dbmgui for SAP DB (1/2) ..........................................................................................7-10

Appendix: Installation of dbmgui for SAP DB (2/2) ..........................................................................................7-11

Appendix: Configuring dbmgui ..........................................................................................................................7-12

Appendix: Stopping the Database using dbmgui ................................................................................................7-13

Appendix: Applying a Database Patch for SAP DB ..........................................................................................7-14


Implementing Patches: Unit Summary ...............................................................................................................7-16

Implementingof Patches Implementing Patches Exercises ................................................................................7-17

Implementing Patches Implementing Patches Solutions.....................................................................................7-18

Converting Non-Unicode to Unicode .......................................................................................................................8-1


Default Conversion Method..................................................................................................................................8-3

Important Notes for an Unicode Conversion ........................................................................................................8-4

Prerequisites on the Source System ......................................................................................................................8-5

Actions on the Source System...............................................................................................................................8-6

Transferring the Export Files to the Target Host...................................................................................................8-7

Actions on the Target System (1/2).......................................................................................................................8-8

Actions on the Target System (2/2).......................................................................................................................8-9

Final Activities on the Target System (1/3) ........................................................................................................8-10




Converting Non-Unicode to Unicode: Unit Summary........................................................................................8-14

Troubleshooting ........................................................................................................................................................9-1


Troubleshooting ....................................................................................................................................................9-3

Guideline to Solve Problems.................................................................................................................................9-4

Restart Installation (1/5)........................................................................................................................................9-5





SAP Notes with Known Installation Problems ...................................................................................................9-10

Flow Trace ..........................................................................................................................................................9-11

Troubleshooting ..................................................................................................................................................9-12

Example 1: SAPinst and Ports ............................................................................................................................9-13

Example 2: Local Settings ..................................................................................................................................9-14

Example 3: Library Path .....................................................................................................................................9-15

Troubleshooting ..................................................................................................................................................9-16

Example 1: R/3 Load ..........................................................................................................................................9-17

Example 2: Oracle Redologs...............................................................................................................................9-18

Example 3: Installation CDs ...............................................................................................................................9-19

Example 4: SAP J2EE Engine ............................................................................................................................9-20

Example 5: Communication User SAPJSF.........................................................................................................9-21

Restriction ...........................................................................................................................................................9-22


Installation Processes: Unit Summary.................................................................................................................9-24

© SAP AG 2003

<leave this slide blank>

ADM110 SAP R/3 Enterprise Installation

Diese Seite wird von Andrea für euch noch erstell!

FS310 Inkasso/Exkasso

THE BEST-RUN BUSINESSES RUN SAP

© SAP AG 2003

ADM110SAP R/3 Enterprise Installation

SAP Web Application Server 6.20 2003/Q3 Material number: 50063703

© SAP AG 2003

Copyright

Copyright 2003 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

All rights reserved.

Trademarks: Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.

© SAP AG 2003

This course is intended for the following audiences:

SAP system administrators

Technology consultants

Duration:

Two days

Target Audience

This course is not a self-study program. These materials complement the course instructor's explanations. The material includes space for recording classroom notes.

The exercises offer additional examples of material covered in the course. There may not be enough time to do all the exercises included in this course during the classroom training. Participants are encouraged to complete any exercises not covered during the classroom training to deepen their knowledge of the subject matter.

© SAP AG 2003

Required Knowledge:

SAPTEC – SAP NetWeaver: Fundamentals of the Application Platform

ADM100 – SAP Web AS Administration I

Recommended Knowledge:

Working experience with SAP system administration

Course Prerequisites

© SAP AG 2003

Unit 5 Installation Process

Unit 6 Post-Installation Activities

Unit 7 Implementing Patches

Unit 8 Converting Non-Unicode to Unicode

Unit 9 Troubleshooting Installation Problems

Unit 1 SAP R/3 Enterprise Architecture, New Features

Unit 2 Installation Planning

Unit 3 Installation Preparation

Unit 4 Installing SAP GUI

Preface

Course Content

(C) SAP AG ADM110 1-1

© SAP AG 2003

SAP R/3 Enterprise Architecture, New Features

Post-Installation Activities

Installation Preparation

Installation Planning

Installation Process

23

56

Installing SAP GUI4

SAP R/3 Enterprise Architecture, New Features1

Troubleshooting Installation Problems

Converting Non-Unicode to Unicode

Implementing Patches789


© SAP AG 2003

Content and Objectives

Content:Overview of SAP R/3 Enterprise architecture and SAP J2EE Engine

New features with SAP R/3 Enterprise: Unicode, MCOD, LDAP

New features of SAPinst

Objectives:At the conclusion of this unit, you will be able to:

Describe the architecture of SAP R/3 Enterprise and SAP J2EE Engine

Explain and use the terms Unicode, MCOD, Directory Server

List differences between SAPinst and R3setup


© SAP AG 2003


SAP R/3 Enterprise Architecture

SAP J2EE Engine

Unicode

Directory Server

MCOD

SAPINST


© SAP AG 2003

New developments in SAP R/3 Enterprise are encapsulated in extensions and can be optionally and flexibly deployed

The SAP R/3 Enterprise Extensions will also be available to all SAP R/3 customers as part of SAP R/3 maintenance

SAP R/3 Enterprise Extensions have a separate release cycle from the SAP R/3 Enterprise Core

SAP R/3 3.1

SAPR/3 4.0

SAPR/3 4.5

SAPR/3 4.6

SAP R/3Enterprise

SAP R/3 Development Strategy

The SAP R/3 Enterprise strategy follows a structured approach from both a technical and functional perspective.

From a technical perspective, the latest version of SAP NetWeaver was used as the foundation for SAP R/3 Enterprise. Specifically, this is SAP Web Application Server 6.20.

From a functional perspective, the previous application release, SAP R/3 4.6C, was used as the application basis for SAP R/3 Enterprise. Infrastructure developments (such as performance or continuous improvement) and legally required changes are made in SAP R/3 Enterprise Core. Functional developments now take place separately in SAP R/3 Enterprise Extensions.

New developments in SAP R/3 Enterprise are encapsulated in extensions and can be optionally and flexibly deployed. These extensions do not modify the core (whereas some previous industry add-ons did). The extensions will be continuously developed.

The SAP R/3 Enterprise Extensions will also be available to all SAP R/3 customers as part of SAP R/3 maintenance, at no extra cost.

The release cycle for SAP R/3 Enterprise Extensions is separate from that of the SAP R/3 Enterprise Core.

The SAP Web Application Server is downward compatible, that is, customers can now upgrade the technology infrastructure only without doing any functional upgrade.


© SAP AG 2003

Plug-InIn

dust

ry S

olut

ion

SAP

R/3

Ent

erpr

ise

GLT

RA

DE

Exte

nsio

n

SAP

R/3

Ent

erpr

ise

FIN

SER

V Ex

tens

ion

SAP_APPL SAP_HR

SAP R/3 Enterprise Core 4.70

SAP Web AS 6.20

SAP R/3 EnterpriseExtension Set 1.10

Building Blocks of SAP Systems

SAP_BASIS SAP_ABA

Plug-In

SAP_BW

SAP BW 3.10

SAP Web AS 6.20

SAP_BASIS SAP_ABA

...

From a technical point of view, the first SAP R/3 Enterprise release consists of three parts, each containing different software components. (Note: All building blocks can have different release numbers.) SAP Web Application Server (Web AS) 6.20 consists of, among other things, the SAP kernel and the SAP_BASIS 620 and SAP_ABA 620 software components.

SAP R/3 Enterprise Core 4.70 consists of the SAP_APPL 470 and SAP_HR 470 software components.

SAP R/3 Enterprise Extension Set 1.10 consists of the EA-HR 110, EA-APPL 110, EA-IPPE 110, EA- RETAIL 110, EA-GLTRADE 110, EA-PS 110 and EA-FINSERV 110 software components.

In addition, SAP R/3 Enterprise 47x110 contains the PI 2002_1_470 SAP R/3 plug-in and the PI_BASIS 2002_1_620 SAP Basis Plug-In. These components guarantee the integration of the SAP R/3 Enterprise Extension Set and the SAP R/3 Enterprise Core.

For more information about SAP R/3 Enterprise software architecture, refer to SAP Note 538887. Other SAP systems (such as SAP BW 3.1 or SAP CRM 4.0) also include the SAP Web Application Server but they have different application functions.


© SAP AG 2003

Release Strategy of SAP R/3 Enterprise

2002 2003 2004 2005 2006 2007

SAP Web AS 6.20

SAP R/3 Enterprise Core (4.7)


Maintenance

Maintenance


SAP Web AS 6.30

SP SP SP

Maintenance

Maintenance

SP SP


Maintenance

SAP Web AS 6.40

Maintenance

SP SP SP

Maintenance

SAP uses the following release strategy for the different parts of SAP R/3 Enterprise: SAP R/3 Enterprise Extensions are delivered in an SAP R/3 Enterprise Extension Set. When customers upgrade to a higher level of an extension, they must upgrade the extension set.

SAP R/3 Enterprise Core is maintained through support packages (HR support packages and non HR support packages).


© SAP AG 2003

Database Server

Database System

RFC

SOA

P/XM

L

HTT

P(S)

SMTP

Browser

Operating SystemLinuxUnix

OS/400OS/390

Windows

SAP DBInformixMicrosoft SQL Server

OracleDB2

(DB4, DB6)

DIAGSAP GUI

ABAPABAP

external systems, SAP GUI

Internet Communication ManagerInternet Communication Manager

SAP Web AS

SAP Web AS 6.20: Architecture and Connectivity

SAP J2EEEngine

SAP J2EEEngine fast RFC

The SAP Web Application Server supports many open technical standards. The Internet Communication Manager (ICM) is a new process in SAP Web AS 6.10. The ICM enables SAP systems to communicate directly with the Internet. It can also direct an HTTP request from an SAP system to a Web server and send the response back to the SAP system. It also handles SMTP requests for mail exchange with a mail server.

The SAP J2EE Engine can be integrated into the framework of the SAP Web Application Server starting with release 6.20.


© SAP AG 2003



SAP J2EE Engine

Unicode

Directory Server

MCOD

SAPINST


© SAP AG 2003

ICM

WPWP

Dispatcher

MSMS

SAP Web Application Server

Web Browser/Web Server

SAP J2EE Engine

MPI

fast RFC, JCo

http

Dispatcher

... ...Server Server

SAP J2EE Engine: Web Access

SAP J2EE Engine fulfills the J2EE 1.2 standard and has integrated standard APIs (JDBC, JNDI, RMI, and so on).

ICM ensures the client connection with SAP Web servers (ABAP and Java). If the request turns out to be a Java request, ICM redirects the HTTP request from the client to the SAP J2EE Engine unchanged.

Data exchange between ICM and the ABAP Dispatcher is done by memory pipes (MPI).

Connectivity between SAP J2EE Engine and SAP Web AS is available via SAP Java Connector (JCo) and fast RFC.

The SAP Java Connector is a toolkit that allows a Java application to communicate with any SAP system. Calls from Java to ABAP system and from SAP system to Java are supported.

Fast RFC provides an additional fast, local communication channel for JAVA-ABAP components via shared memory and an efficient representation response mapping of the data types of both systems.

SDM (Software Delivery Manager) is a standalone tool, shipped with SAP Web AS 6.20. SDM is used to deploy your self-developed and SAP shipped software. SDM provides tools, which provide functions similar to the transporttools tp and R3trans, to deploy SDA (Software Delivery Archives).

For more information, refer to SAP Note 544979.


© SAP AG 2003

SAP J2EE Engine Cluster Installation

Java Virtual Machine (java.exe)

Server1

Dispatcher2

Server3

Server2

Server4

Dispatcher1

Host 1 Host 2

ClientClient ClientVisual

Administrator

Server1

Dispatcher1

ClientVisual

Administrator

SAP J2EE Engine StandaloneInstallation

Dispatcher and Server consist of: Managers (Thread, Memory, ...)

Services (log, http, deploy, ...)

SAP J2EE Engine: Installation Variants

Variant 1: Web Application Server with SAP J2EE cluster version • This variant is integrated with SAP Web Application Server. • Administration and monitoring is done via transaction SMICM. • The J2EE engines belonging to one SAP system form a cluster. • The host on which the central instance (CI) runs serves as cluster host.

Variant 2: SAP J2EE standalone • This variant is used to set up a pure Java development environment including tools. • This variant does not require a connection to an SAP system • This is a pure J2EE Engine (one dispatcher and one server on one host), without ICM and SAP Web

Application Server. • Administration, monitoring, and deployment are done with J2EE admin and deploy tool.

Variant 1: • The SAP J2EE Engine can be started only by starting the SAP system. This guarantees the

communication between ICM and J2EE Engine. • The SAP J2EE Engine on a dialog instance (DI) starts only if the CI and the J2EE Engine on the CI is

running. The user SAPJSF (type: communication) is required for the RFC communication authentication between the J2EE service, security, and the SAP system. SAPJSF is automatically installed during a central instance installation.


© SAP AG 2003



SAP J2EE Engine

Unicode

Directory Server

MCOD

SAPINST


© SAP AG 2003

Languages within an ellipse can be combined in one SAP system using a standard code page

SAP systems support more than 30 different languages.

Only languages belonging to the same code page are usable without restriction.

SAP supports multiple languages with MDMP (Multi-Display/Multi-Processing) systems

Unicode (1/2)

Unlike other standard code pages, Unicode defines a character set that includes virtually all characters used in the world and therefore provides consistent, global character encoding. Unicode is defined by the Unicode consortium (see http://www.unicode.org for more information) consisting of world-leading companies in the IT industry.

Until now SAP has provided multiple language support using single code pages, as well as multiple code pages in a single installation with MDMP (Multi-Display-Multi-Processing), which permits the application server to dynamically switch code pages according to the logon language and language keys (see SAP Note 73606). Yet even in a MDMP system, an individual user can use only characters belonging to one code page at a time. To further enhance language support for the mySAP Business Suite, SAP considers Unicode the appropriate development direction and strategy because Unicode offers a single, consistent, and standard character set encoding for virtually all languages in the world.

A code page describes the assignment of one character to one hexadecimal (HEX) value. One (normal: 1 byte) code page represents 256 characters.


© SAP AG 2003

Unicode (2/2)

Character set describes the type of storage for one character:Single byte (one byte per character)Double byte (one or two bytes per character)Unicode (one or more bytes per character)

Unicode:International standard (Internet is based on Unicode)Each character is assigned to unique numberIncrease in resource consumption

CPU, memory, network: +30% Database size: +30% (depending on database type)

For more information about Unicode SAP systems and their availability, refer to SAP Notes 79991, 540911, and 379940. Go to the SAP Service Marketplace on the Web at http://service.sap.com/unicode.


© SAP AG 2003

Unicode and SAP Web AS

Unicode supported since SAP Web Application Server 6.10

SAP Web AS 6.20 Enhancements:

All languages in ISO-639 standard can be used as language tag

RFC communication between Unicode systems and MDMP systems

Maintain all characters from all languages in SAP GUI simultaneously

Improved (printer) code page maintenance

Unicode supports the following: Characters from virtually every language and script to be used (this does not mean that localized versions or translations exist for all languages).

RFC: Multi Display Multi Processing (MDMP) handling enables RFC communication between Unicode systems and MDMP systems without data loss due to code page incompatibility.

SAP GUI: Unicode is supported on Unicode systems as a front-end character set for core functionality in SAPGUI for Windows and in SAPGUI for Java. It is possible to maintain all characters from all languages. A single GUI can be used to access both Unicode and Non-Unicode systems.

Code Page maintenance: Enhanced, Unicode-based code page architecture improves (printer) code page maintenance.


© SAP AG 2003



SAP J2EE Engine

Unicode

Directory Server

MCOD

SAPINST


© SAP AG 2003

Simplification using MCOD option:n SAP systems, 1 Database

Traditional system setup:n SAP systems, n Databases

MCOD (1/2)

RDBMS

RDBMSRDBMS

RDBMS RDBMS

RDBMS

SAP BW

SAP SEMSAP CRM

SAP R/3

SAP EBP

SAP BW

SAP SEMSAP CRM

SAP R/3

SAP EBP

You can install multiple SAP systems in a single database using Multiple Components in One Database (MCOD). MCOD will be available with all mySAP Business Suite components. SAP is releasing this technology on all databases for the SAP system, in line with our commitment to deliver platform-independent solutions.

Using MCOD technology is as easy as installing a separate component. No extra effort is required because the MCOD installation is fully integrated into the standard installation procedure. MCOD is not an additional installation service. Instead, it is an option of the SAP system installation.

SAP recommends running MCOD systems in the same context. SAP does not recommend mixing test, development, and productive systems in the same MCOD database. The mixing of productive and non-productive systems is not supported.

When MCOD became generally available in 2002, for performance reasons SAP recommended separating OLTP applications (such as SAP R/3) and OLAP applications (such as SAP BW). Now combined installations of both component types are also supported under special conditions.

Multiple Components in One Database (MCOD), which is a powerful way to install several mySAP Business Suite components in one physical database, offers these main advantages: Full flexibility and independence of the installed components Simplified administration, backup and recovery Additive sizing approach Data consistency across systems Reduced maintenance and operating costs

For more information, go to /mcod from the SAP Service Marketplace.


© SAP AG 2003

MCOD (2/2)

DB User: SAPER4T100 (SAPER4)

T100 (SAPCM1)

SAP R/3 SAP CRM

bus

iness daX ta

business data

SID = ER4 SID = CM1

DB User: SAPCM1

Administrative opportunities: Multiple independent and different software solutions are located in one database (multiple identical software components, such as multiple SAP R/3 systems, are also possible).

There is one logical and physical database instance. Point-in-time recovery of semantically related systems such as SAP R/3 and SAP CRM is possible. Migration of existing systems is possible.

All systems use the same OS/DB release. Each mySAP Business Suite component connects the database with one single database user. This user is independent of the user logged on to the SAP system itself. Databases support schema. Tables with the same name can exist independently in different schema with different contents.

Using a one-to-one correspondence between the database user and the database schema, each mySAP Business Suite component uses its own schema by accessing the database with a unique dedicated database user.

The technical realization in detail depends on the database product. For more information on released platforms and availability, go to /mcod and /platforms on the SAP Service Marketplace.

Data exchange between different SAP systems is done on application level, not database level, to ensure the following: Integrity of business data No locking conflicts on database tables No special coding for MCOD installations


No additional educational effort (for companies already familiar with the exchange of data between SAP systems)


© SAP AG 2003



SAP J2EE Engine

Unicode

Directory Server

MCOD

SAPINST


© SAP AG 2003

Central UserAdministration

CorporateDirectory

ServerExchange ofRoles

SAP systems Other applications

Operating System

Phone / Fax

EMail

SAP orNon-SAP

HRsystem

SAPWeb AS

SAP Enterprise

Portal

Directory Server (1/2)

A directory server acts as a central repository for data that is used by different applications. The data is important in a heterogeneous system environment.

Usually information concerning users, documents or hardware is stored, but other objects can be stored as well.

Access is possible via standard protocol such as LDAP (Lightweight Directory Access Protocol). In contrast to relational database management systems (RDBMS), directory servers use a hierarchical structure to organize the data.

SAP has been working on integrating the directory server using LDAP for years: With SAP Basis 4.6A, the LDAP connector is an integrated part of the SAP application server. With SAP Web AS 6.10, easy-to-use customizing was added (transaction LDAP). The SAP Enterprise Portal 5.0 requires a corporate directory server (as user persistence store).

The concepts of directory server integration and Central User Administration (CUA) can be implemented independently of one another or combined.

In August 2001, the SAP Web AS 6.10 got the "Works with LDAP" certificate of the OpenGroup. Go to /partnerdirectory on the SAP Service Marketplace for SAP-certified vendors of directory servers.


© SAP AG 2003

Createin DS

Deletein SAP

Lock in SAP

Ignore

CompareTime Stamp

IgnoreTime Stamp

IgnoreObjects

Createin SAP

Deletein DS

Ignore

LDAP

SAP DS

SAP

SAP/DSSAP/DS

SAP/DSDS

Directory Server (DS)SAP Web AS

Directory Server (2/2)

Technically, setting up integration of a directory server is done in Customizing (performed via the Implementation Guide (IMG) or using transaction LDAP).

During synchronization, three user groups are distinguished. Each group will be processed based on synchronization flags that are maintained in the SAP system: User that exists only in the SAP system User that exists only in the directory server User that exists both in the SAP system and in the directory server. For this user, it is possible to

select either delta synchronization (compare time stamps) or full synchronization (ignore time stamp).

For further information, refer to Quick Link /security on the SAP Service Marketplace (choose Security in Detail → Identity Management → Directory Service Integration) and SAP course ADM102.


© SAP AG 2003



SAP J2EE Engine

Unicode

Directory Server

MCOD

SAPINST


© SAP AG 2003

New Features with SAPinst

SAP provides a new installation tool:

System Landscape Implementation Manager: SAPinstSAPinstThe main advantages compared to R3SETUP are:

Step back possible without restarting the installation

No abort due to errors

Fewer log files (such as sapinst.log)

SAPinst GUI allows you to monitor the installation progress and see all messages issued by SAPinst.

Other Features:Aborted installations can be resumed.

SAPinst GUI can be started on a remote computer.

SAPinst GUI requires a Java Runtime Environment (JRE) and a Java Development Environment (JDK).

The System Landscape Implementation Manager (SAPinst) offers these main advantages compared to R3SETUP (the previous tool): SAPinst lets you step back to correct your entries during the input phase without restarting the

installation. SAPinst does not abort because of errors. Instead, it stops the installation and you can retry the

installation after solving the problem. Alternatively, you can abort the installation manually if you want.

SAPinst continues an aborted installation directly from the point of failure. SAPinst records installation progress in a single log file, sapinst.log. SAPinst has a graphical user interface (GUI), SAPinst GUI, which allows you to monitor the progress

of the installation and see all messages issued by SAPinst. Because SAPinst GUI is Java based, you need a Java Runtime Environment (JRE).

You can start SAPinst GUI on a remote computer if you want. For more information about SAPinst, refer to the documentation, SAPinst Troubleshooting Guide at http://service.sap.com/sapinstfeedback.


© SAP AG 2003

Further Information

SAP J2EE Engine:SAP Library at http://help.sap.com: SAP NetWeaver →SAP Web Application Server 6.20 → mySAP Technology Components → SAP Web Application Server -> SAP J2EE Engine

service.sap.com/j2ee

SAP R/3 Enterprise: service.sap.com/enterprise

Unicode: service.sap.com/unicode

MCOD: service.sap.com/mcod

Directory Server: service.sap.com/security

service.sap.com/partnerdirectory


© SAP AG 2003

SAP R/3 Enterprise Architecture, New Features: Unit Summary

Describe the architecture of SAP R/3 Enterprise and SAP J2EE Engine

Explain and use the terms Unicode, MCOD, LDAP

List differences between SAPinst and R3setup

Now you are able to:


© SAP AG 2003






23

56

Installing SAP GUI4






© SAP AG 2003


Content:Sizing

Installation Options

Technical Requirements


List the requirements for an installation of SAP R/3 Enterprise

Explain some technical choices to be made

This unit explains the general approach for installing an SAP system. There are several questions you need to clarify before you can begin the installation of an SAP system. Typically this phase begins several weeks before the actual installation takes place.


© SAP AG 2003

Sizing Your System

Sizing determines the hardware you need to host your system:

For sizing information see http://service.sap.com/sizing

SAPSystem

SAPSystem

SAPSystem

SAPSystem

SAPSystemHardware too

small to host the planned system

Hardware OK!

Hardware too large

Consider the following potential issues: Hardware that is sized too small costs performance because it leads to high response times and inefficient production.

Adequate hardware prevents performance losses and avoids unnecessary hardware costs. Hardware sized too large means you invested too much money to reach your goal of good performance.


© SAP AG 2003

Sizing is an Ongoing Process

Sizing is an ongoing process!

SAPSystem

Hardware OK!

initially

SAPSystem

Hardware no longer OK

some time later

SAPSystem

after hardware resizing

Hardware OK again!

time

new users added

Sizing plays a role very early in the planning of your SAP system landscape. It determines what hardware resources you will need for your SAP system. The resources needed are influenced by several factors: Number of concurrent users in the system and activity level of users Your company's goals for average dialog answer time (1.5 seconds OK or 0.6 second required?) The amount of high availability needed (full blown solutions may cost a fortune) Type of system (SAP R/3 Enterprise, SAP BW, SAP CRM, and so on) Functions used in the system (for example SAP R/3): lean (HR, FI) or complex (PP) Release of system (SAP R/3 4.0B, SAP R/3 4.6C, SAP R/3 Enterprise, and so on) Type of OS (32-bit, 64-bit OS / Linux, HP-UX, Solaris, AIX, Win NT, W2K, and so on) Type of database used (SAP DB, DB2 UDB, Microsoft SQL Server, Oracle, and so on) Type of access to the system (LAN, WAN, GUI type, and so on) Preferred backup concept (for example, online backup parallel to productive use requires more hardware)

If one or more of the above factors are subject to change, a new sizing (or hardware improvement) might become necessary.


© SAP AG 2003

Sizing and Unicode

Unicode influences the following factors:

Load of applications on hardware (CPU & RAM)See http://service.sap.com/unicodeSee http://service.sap.com/performanceResult: about + 35% CPU, + 50% RAM

Size of databaseSee http://service.sap.com/unicodeResult depends on usage of UTF-8 or UTF-16

Performance of databaseAsk database vendor for performance results of database using Unicode

Unicode systems use between 1 and 5 bytes of space for storing single characters (depending on the character and its Unicode representation). Therefore, in a very simple estimate, the resources of the system could be doubled to be prepared for some worst-case scenario.

Actually the load on the CPU caused by the applications, in this case, the SAP software, increased by about 35%. The load on RAM (again caused by the application software, not the database software) increased by about 50%.

The size of the the database of Unicode systems, compared to non-Unicode systems, depends largely on the type of Unicode representation chosen. UTF-16 requires more space than UTF-8.

The performance of the database system is affected as well. For performance data on the database systems under Unicode, contact your database manufacturer. For information about SAP DB, refer to http://www.sapdb.org.


© SAP AG 2003

Supported Platforms

The supported platforms for SAP R/3 Enterprise are identical to thosefor SAP Web AS 6.20. For details see:

Released Operating Systems SAP Web AS 6.20 SAP DB (SAP Note 0407320) Released Operating Systems SAP Web AS 6.20 DB2/UDB (SAP Note 0407322) Released Operating Systems SAP Web AS 6.20 DB2/390 (SAP Note 0407325) Released Operating Systems SAP Web AS 6.20 DB2/400 (SAP Note 0410783) Released Operating Systems SAP Web AS 6.20 Informix (SAP Note 0407317) Released Operating Systems SAP Web AS 6.20 MS SQL Server (SAP Note 0407328) Released Operating Systems SAP Web AS 6.20 Oracle (SAP Note 0407314)

See also http://service.sap.com/platforms

The SAP Notes listed in the figure provide details about the availability of operating systems for different databases with SAP Web AS 6.20. There are a few differences between the availability of SAP Web AS 6.20 and SAP R/3 Enterprise. For these differences, check out the difference matrix found at http://service.sap.com/platforms.

Here you find the typical hardware requirements for a central system-type installation of an SAP R/3 Enterprise system on SAP DB and Windows 2000 (taken from paragraph 3.5.1 of the corresponding installation guide): For a system used for sandbox purposes: Disk space: 12 gigabytes (GB) on at least three separate physical disks Random access memory (RAM): 256 megabytes (MB) minimum, 4 times this value as page file

For a productive system: Disk space: 20 GB on at least three separate physical disks RAM: 2 GB minimum on Windows OS, 1.5 GB on UNIX Page/Swap: 4 times RAM on Windows OS (max. 20 GB), 3 times RAM on UNIX (32-bit: 20 GB Swap max., 64-bit: 20 GB Swap recommended)

64 to 512 MB RAM for SAP J2EE Engine (for both Windows OS and UNIX) For UNIX, see also SAP Note 407317.


© SAP AG 2003

Sizing SAP R/3 4.6C against SAP R/3 Enterprise

For its non-Unicode version, SAP R/3 Enterprise requires no more hardware than SAP R/3 4.6C if the same core business processes are used.

Live installations and upgrades show usually less than 5% increase in hardware consumption.

SAPR/3 4.6C

Hardware OK!

SAPR/3 Enterprise

Same Hardware: OK!

Upgrade

Aside from the additional resources needed for Unicode, an SAP R/3 Enterprise system does not require more hardware resources than SAP R/3 4.6C.

Actually, because of some further improvements made (using state-of-the-art techniques available with SAP Web AS 6.20), some core business processes even run somewhat faster than before.


© SAP AG 2003

Installation Options

Stand-alone database instance:

part of PRD system

Dispatcher

Central system:

the complete DEV system

Dispatcher

Dialog instance:

part of QAS system

SAP software can be distributed in several ways on the available hardware. This decision may also be influenced by the result of the sizing because the distribution of the software can affect system performance. Some examples and considerations follow.

Central system: All software needed for an SAP system is installed on one machine (except the SAP GUI software for the end users). This setup is useful in small companies in which one server is able to offer all hardware resources needed for the system.

Stand-alone database instance: In this scenario the database gets "its own" hardware. This way interferences from the SAP instance on the database performance are excluded. Because this central hardware can be sized very large, this setup can be used in very large installations with several thousands of users.

Dialog instance: If you decide to install a central system and the need for additional SAP system users arises, an additional dialog instance is a possible solution. If you are using a stand-alone database instance, you need at least one dialog instance. A dialog instance may host as many users as their corresponding hardware allows, SAP systems may have lots of dialog instances. Productive systems with more than 20 dialog instances can be found. Also it is possible (and shown in this workshop) to install more than one instance on one server.

Gateway instance (not shown): A gateway instance can be (optionally) set up to offer powerful communication performance for SAP systems that are exchanging data with external systems with a very high load.


© SAP AG 2003

Technical Requirements

A well-designed technical infrastructure ensures lowest cost of ownership and the system's

Performance

Functionality

Availability

Scalability

Security

Find more information at http://service.sap.com/ti

(ti = Technical Infrastructure)

The following slides present some factors that affect the parameters listed above.

The technical infrastructure describes the technical setup of the SAP system. The technical setup includes network layout, server layout, disk layout of the database, type of computer interface used and many more details.

The technical infrastructure influences the technical areas listed in the figure.


© SAP AG 2003

Network: External Ports Used by SAP Systems

DialogService

(Dispatcherand

Workproc.)

InfoService

(MessageServer)

GatewayService

(Gateway)

PrintService

(Spool)

SAP Web Application Server

DispatcherPort

MessageServerPort

GatewayPort

GatewayPort

Printer Port

differentSAP

System

Externalprogramsusing SAP

CommunicationAPI

Print Service(SAPlpd)

SAP GUI for Windows

SAP GUI for Windows

32<nn> 36<xx> 33<nn> 515* ***

* = can be made more secure by using SAProuter

As shown in the figure, the SAP system uses several different ports for external communication. All these ports should be secured by some means (for example, firewall, router, SAProuter) to ensure the SAP system's security. Furthermore, several internal connections are used in SAP systems for communicating with the database. How many connections and which ports are used depends on the type of database employed.

For more information, go to http://intranet.sap.com/network and choose Network Integration of SAP Servers.


© SAP AG 2003

Network: Load Caused by SAP Communication

Dispatcher

SAP GUI for Windows

SAP GUI for Windows

recommended: 100 megabits per second or more

Dispatcher

bandwidth needed per dialog step: below 7KB*

* for SAP R/3 Enterprise, SAP GUI for Windowsand low-speed connection option

The bandwidth needed between the computer interface and the application layer depends on the following parameters: Type of GUI used (BEx for SAP BW, SAP GUI for HTML, SAP GUI for Windows, and so on) Type of application (within SAP R/3 Enterprise: FI, HR, SD, and so on) Type of product used (mySAP CRM, mySAP BI, and so on) Low-speed connection flag used (SAP Note 161053) Other applications on the front end (office products) using the same connection

For more information, go to http://service.sap.com/sizing. From the menu choose Media Library → Literature. From here you can download the document, Frontend Network Requirements for SAP Solutions.

The load between the application layer and the database layer is considerable. Therefore, SAP recommends offering a bandwidth of at least 100 megabits per second for this communication. It is usually not possible to separate the database by more than LAN width from the application layer.

For more information on network layout for SAP servers, go to http://intranet.sap.com/network and display or download the document, Network Integration of SAP Servers, from this page.


© SAP AG 2003

Database: Disk Layout and High Availability

Databases of SAP systems hold different types of data:Business data (master data, transaction data and so on) and corresponding index dataLogging data for the database (needed for recovery)Configuration data for the database

Databases of SAP systems are usually storedon disks combined to some RAID level (usually 1 or 5)

resides on RAID arrayof several physical disks

For recommendations of disk layout, see next page

Databases used for SAP systems can hold up to several terabytes of business data. Because you are practically not able to restore such a large database, you have to ensure that data loss is avoided under almost all circumstances.

The disk layout for databases used for SAP systems affects not only system performance, but also reliability and availability.

To ensure maximum availability of your system, you have to take into account several scenarios: disk failure RAID controller failure network card failure network failure power supply failure massive environmental damages (fire, flood, earthquake, and so on)

For more information on these issues, go to http://service.sap.com/ha. The next slide provides some recommendations concerning the disk layout.


© SAP AG 2003

Recommendations on Database Disk Layout

Separate the following database data physically, as shown:

Business data and index data

Current logging data

Database configuration data

RAID 5

RAID 1

RAID 1

Using the configuration shown above, you get an optimum of hardware costs, availability and performance. If costs are not a factor, higher-performing configurations are possible. For these options, you can inform yourself at http://service.sap.com/ha and by contacting your hardware, operating system and /or database vendor.

You should not store the historical log files of your database on any of the arrays listed in the figure; instead, you should save these historical log files to tape (or wherever) twice before deleting them (historical log files are referred to as Offline Redo Log Files by Oracle).


© SAP AG 2003

SAP System Installation: SID

Your SAP system ID (SID) and your database system ID must be unique.

The system ID must consist of three alphanumeric characters.

Some system IDs are reserved for SAP use only: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

Note: The set of reserved names may differ between different

database and operating system combinations

The ID for your SAP system (<SAPSID> or SID) and for your database system (<DBSID>) must be unique throughout your organization. The ID must consist of three alphanumeric characters. Only uppercase letters are allowed. The first character must be a letter, subsequent characters may be digits.

The following system IDs are reserved for SAP use and cannot be used: 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

The database of the SAP system should have the same name as the SAP system it belongs to. Database management systems can host more than one database (exception: when MCOD is used).


© SAP AG 2003

Database Users for SAP Systems

Depending on the database you use,

you need the following database users:

SAP DB: SAP<SID> Control, SUPERDBA

Oracle (9.20): SAP<SID> SYSTEM, SYS

Microsoft SQL Server: <sid>adm SAPService<SID>

DB2 UDB: SAP<SID> db2<dbSID>

DB2 (zOS): <sid>adm and see Installation Guide

DB2 (iSeries): <sid>OFR

Informix: informix sapr3

Important: Read the installation guide and the related notes carefully. There are critical differences in the naming conventions. For example, for Microsoft SQL Server the user <sid>adm must be named with lowercase <sid>, for example, tstadm, whereas the user SAPService<SID> must be named with uppercase <SID>, for example, SAPServiceTST.

When higher security settings are used on iSeries machines, password entries become case sensitive. Therefore, SAP Note 495433 explains that the default password, using the higher security settings, must be entered as SAPOFR.


© SAP AG 2003

Installation Variants

New installation installs a new system

Homogeneous/heterogeneous system copy migrates an existing system without or with changes in operating system and/or database

DispatcherHP-UX Oracle 9.20

HP-UX Oracle 9.20

Linux SAP DB 7.3(on new hardware)

EXAMPLE!

homogeneous

heterogeneousDispatcher

Dispatcher

Dispatcher

HP-UX Oracle 9.20(on new hardware)

You can choose between two installation variants for your system: a new installation or a homogeneous or heterogeneous system copy.

For more information, go to http://service.sap.com/osdbmigration and http://service.sap.com/instguides. Choose SAP Web Application Server → Release 6.20 and display, print or download SAP Web AS Homogeneous and Heterogeneous System Copy.


© SAP AG 2003

Further Information

SAP Service Marketplace http://service.sap.com:

Quick Links: /sizing, /network, /performance, /ha, /ti, /unicode, /platforms, /instguides, /osdbmigrationSAP Notes as listed in this unit


© SAP AG 2003

Installation Planning: Unit Summary

List the requirements for an installation of SAP R/3 Enterprise

Explain some technical choices to be made



© SAP AG 2003






23

56

Installing SAP GUI4






© SAP AG 2003


Content:General Preparation Steps

Further Preparation Steps under Windows

Further Preparation Steps under UNIX


Perform the necessary preparations for the installation of SAP R/3 Enterprise


© SAP AG 2003


General Preparation Steps




© SAP AG 2003

Order Installation CDs

http://service.sap.com/swcat

Or download CDs athttp://service.sap.com/installations


© SAP AG 2003

Download of Installation Guides

http://service.sap.com/instguides

For each installation, you should download the up-to-date installation guide for your specific combination of operating system and database system from the SAP Service Marketplace (http://service.sap.com/instguides).

You should print out the installation guide and read it carefully before starting the installation process. Have the installation guide ready during the installation to follow each successive step of the procedure.


© SAP AG 2003

Download Relevant SAP Notes!

• 534334 - Composite SAP note Installation/Upgrade SAP R/3

• 492222 - SAP Software on UNIX - OS Dependencies • 523505 - SAP R/3 Enterprise Installation under UNIX • 523502 - INST: SAP R/3 Enterprise 4.7 Inst. under UNIX - SAP DB • 523503 - INST: SAP R/3 Enterprise 4.7 Inst. under UNIX - Informix • 523504 - INST: SAP R/3 Enterprise 4.7 Inst. under UNIX - Oracle

• 496251 - INST: SAP Web AS 6.20 on Windows - General • 529151 - SAP R/3 Enterprise Installation under Windows -

General • 529076 - INST: SAP R/3 Enterprise 4.7 under Windows: Oracle • 529118 - INST:SAP R/3 Enterprise 4.7 under Windows- MS Cluster • 529150 - INST:SAP R/3 Enterprise 4.7 under Windows- MS SQL

Server • 531349 - INST: SAP R/3 Enterprise 4.7 under Windows - Informix • 531372 - INST: SAP R/3 Enterprise 4.7 under Windows - SAP DB

• 533728 - SAP R/3 Enterprise 4.7 Inst. under UNIX - IBM DB2 UDB for UNIX and Windows

• 533715 - SAP R/3 Enterprise 4.7 Inst. under Windows 2000 - IBM DB2 UDB for UNIX and Windows

Download the SAP Notes relevant for your specific installation. For example, if you install an SAP R/3 Enterprise system under Windows and SAP DB you should download SAP Notes 534334, 529151, 496251 and 531372. You should also download the SAP Notes mentioned in your installation guide.

Print out the relevant SAP Notes and read them carefully before beginning to install so you can avoid known problems.

Have the relevant SAP Notes at hand during the installation so you can quickly solve potentially occurring problems.


© SAP AG 2003

Install SAP Front-End Software

SAP GUI on at least one host machine (host of central instance)

SAP GUISAP GUI

SAP GUISAP GUI

Make sure that the front-end software is installed on at least one host machine in your system environment. To simplify administration of your SAP system, we recommend that you do this on the central instance host.

For more information on installing the front-end software, refer to Unit 4, “Installing SAP GUI," of this course and the separate documentation: SAP FrontEnd Installation Guide (English version) SAP Frontend-Installationsleitfaden (German version)


© SAP AG 2003

Prepare Installation CDs

or copy to disk

share / mount CDs

The CDs you need for the installation are listed in the installation guide in the section "Preparing required CDs."

Because you need at least one central instance and one database instance for an SAP system, SAP recommends making all required CDs available in parallel. The EXPORT CDs (1-7) must be available in parallel anyway.

Make sure you have sufficient CD drives or copy the CDs to hard disks. Caution: Don't use spaces in directory names when copying the CDs to disk!

Some UNIX operating systems change during the copy process the directory names to lowercases. SAPinst wants to have all directory names and files in upper cases.

You can copy an entire CD during the installation by using the SAPinst dialog CD Browser. SAPinst will copy the CD to the path you entered in the Copy Package to column.


© SAP AG 2003

Windows File System: NTFS

You must use

NTFS for an SAP system installation. Do not install the SAP directories on a FAT partition.

An SAP system must be installed on an NTFS file system. Check the partition on which you plan to install the SAP system for the correct file system.

Follow this procedure to check the file system of the installation partition: - Open Windows Explorer. - Select the root directory, G:, for example. - Choose Properties. - Switch to the General tab to see the type of file system that is in use.

SAP recommends that all SAP system and database hosts are members of a single Windows domain. This is valid for all SAP system setups, whether standalone central systems or distributed systems. In this single domain model, the SAP system and the user accounts are included in a single domain. For performance and security reasons, no SAP instance (and no database instance) should run on the domain controller.

If you want to use the Change and Transport System to move objects between different SAP systems (that is, SAP systems with different SAPSIDs), make sure that all these systems are either a member of one single domain or members of different domains with a trust relationship established between them. Only SAP application and database servers (no other software) should be members of these domains.


© SAP AG 2003

Windows NT: Update Dynamic Link Libraries

For Windows NT only!

SAP Kernel CD r3dllins.exe

Windows NT

This step is necessary for Windows NT only. It does not have to be done for Windows 2000. You must install up-to-date dynamic link libraries (DLLs) on all hosts in the system where you intend

to run an SAP instance. This includes hosts where a standalone database or gateway instance are to run. The DLLs are required for correct functioning of the SAP system.

Follow this procedure to install the dynamic link libraries (DLLs): Insert the SAP Kernel CD in the CD-ROM drive. Switch to the directory <CD_DRIVE>:\NT\I386\NTPATCH. Start the program r3dllins.exe. When the installation has finished, you are prompted to reboot the system to activate the changes.

If your DLLs were already up-to-date before you started the r3dllins.exe program, no new DLLs are installed and you are not prompted to reboot.


© SAP AG 2003

Windows: Reducing Size of File Cache

Start Settings (Control Panel ) Network and Dial-Up ConnectionsLocal Area Connections

When the option Maximize data throughput for network applications is selected among other settings, the Windows file cache is reduced in size so application server software such as an SAP system has more resources available. This also decreases the time needed for the installation, especially for the database import.


© SAP AG 2003

Windows: User for Installation

Set minimum password lenght="0"

Installation user needs administration rights!

For the installation, you need a user with administration rights. To check if your user is a member of the Adminstrators group, choose Start → Settings → ControlPanel → Administrative Tools → Computer Management and select the folder Local Users and Groups → Users. Double-click on your user and switch to the Member Of tab. If this is a domain installation, you should perform this check on the domain controller. For a local installation, your user needs local administration rights; for a domain installation, your user needs domain administration rights.

Set the minimum user password length to 0. Reset the password length to the original value after you have finished the installation. To check this setting, choose Start → Settings → ControlPanel → Administrative Tools → Local Security Policy. In the following window, choose Account Policies → Password Policy. To set the Minimum password length, double-click on the entry.


© SAP AG 2003

Windows: SAP System Transport Host

Get IP address of host

Edit hosts file on each host

You need to prepare one host in the SAP system for the role of transport host. This host has the function of controlling the import or export of files between the current SAP system and other SAP systems (for example, a test or development system).

Find out the IP address of the host by using the command ping <host_name> (pay attention if DHCP is enabled).

If a DNS server is available for your system, map the IP address of the transport host to the alias SAPTRANSHOST. If no DNS server is available, you can map the IP address to the alias SAPTRANSHOST in the hosts file.

Follow this procedure to map the IP address to the alias (no DNS server). - Go to <Drive>:\WINNT\system32\drivers\etc. - Open the hosts file with an editor and add the line:

<IP_address> <hostname> SAPTRANSHOST The result of this step is to assign the alias SAPTRANSHOST to the transport host.

- Copy the newly edited hosts file to all hosts where an SAP instance is to run. If you experience problems with the alias SAPTRANSHOST in UNC paths (\\<hostname>), refer to

SAP Note 360515.


© SAP AG 2003

Windows: Preparing SAPinst Installation

1. Install Java Development Kit on every host on which you want to run SAPinst

2. Clean up the JDK \ext directory

3. Set the JAVA_HOME environment variable

4. Add %JAVA_HOME%\bin to your system path.

Java-based installation tool SAPinst

Before installing SAPinst, the System Landscape Implementation Manager, some preparations are necessary.

Because SAPinst is a Java-based tool, the Java Software Development Kit (abbreviated as SDK or JDK) must be installed on all hosts where SAPinst will run. After installing the Java SDK, some rework is mandatory.

You can find the released JDK versions in the SAP Service Marketplace at http://service.sap.com/platforms. Choose Availablility of SAP components in Detail → SAP Web AS / Basis / Kernel → OS/DB/JDK releases for SAP Web AS 6.20.

The steps in the figure are described in detail on the following pages.


© SAP AG 2003

Windows: Java SDK Installation (1/2)

1

3

2

4

Because SAPinst is a Java-based tool, the Java Software Development Kit (Java SDK) must be installed. If you are not certain that the Java SDK is installed already, you can check under Start → Settings → ControlPanel → Add/Remove Programs. The software is present if there is an entry for "Java 2 SDK Standard Edition..." Caution: The Java 2 Runtime Environment (JRE) is not sufficient for the SAPinst tool. A command line check with java -version yields only the Java version, but not if the JRE or the JDK is installed!


© SAP AG 2003

Windows: Java SDK Installation (2/2)

5 6

7 8

After the successful installation, check the Java \ext directory to see if there are already <parser_name>.jar files, for example, xerces.jar. The default path is <JAVA_HOME>\JRE\lib\ext.

If you find any .jar files, do the following: Rename them to, for example xerces.xxx. This is only possible if the application to which the JAR files belong is not running during the installation.

Remember to rename the files back to their original names after the installation procedure is complete.


© SAP AG 2003

Windows: Environment Variable JAVA_HOME (1/2)

SAPinst needs the JAVA_HOME environment variable to be set on the host(s) where SAPinst will run. To check the JAVA_HOME environment variable, choose Start → Settings → ControlPanel → System

and switch to the Advanced tab. Then click on Environment Variables. Check if the system variable JAVA_HOME is set to the Java home directory (the directory in which the

JDK is installed). If it is not set, create a new variable. Follow this procedure to create a new variable:

Choose New. Set Variable Name to JAVA_HOME. Set Variable Value to the Java home directory, C:\jdk1.3.1_07, for example. Click OK The JAVA_HOME variable is now present in the system variables list (see next slide).


© SAP AG 2003

Windows: Environment Variable JAVA_HOME (2/2)

After setting the JAVA_HOME variable, you have to add the Java home directory to the Path variable. Follow this procedure to add the Java home directory to the Path variable:

- Click Path entry in the list of system variables. - Choose Edit. - Enter %JAVA_HOME%\bin at the end of the Variable Value field. Use a semicolon (;) to

separate the entry from the previous entry! - Click OK.


© SAP AG 2003

UNIX: Checking UNIX Kernel and Swap Space

Check the documentation, SAP Software on UNIX: OS Dependencies, to modify the UNIX kernel parameters and swap space.

See following sections in the documentation:

"<Your OS>: Checking and Modifying the UNIX Kernel"

For Linux: "Linux: Checking the Linux Kernel"

For many UNIX operation system and database system combinations, you have to modify the kernel parameters. You should read the section for your UNIX operation system in the document, SAP Software on UNIX: OS Dependencies.

In addition to this document, you should carefully read SAP Note 492222 - SAP Software on UNIX: OS Dependencies 6.20.


© SAP AG 2003

UNIX: Setting Up File Systems

xxx

symbolic link

File system youhave to set upmanually

usr

<sapsid>

sapmnt

<SID>

SYS <Instance name>

log data workexe profile global

exe profile global

dgbopt run

... trans<sapsid>sap

You have to set up the file systems and/or raw devices for the SAP system and the database. You have to set up the file systems selected in the figure manually; SAPinst will do the rest during the installation process.

For space required by the different file systems, refer to your installation guide. Creation and mounting of file systems and creation of raw devices for the SAP system and for the different databases are described in the documentation, SAP Software on UNIX: OS Dependencies, in the "File Systems, Raw Devices and Swap Space" section.


© SAP AG 2003

UNIX: Preparing SAPinst Installation

1. Install Java Development Kit on every host on which you like to run SAPinst

2. Clean up the JDK /ext directory

3. Set the JAVA_HOME environment variable (for user root)

4. Check that the DISPLAY environment variable is setto <host_name>:0.0

Java based installation tool SAPinst

Before installing SAPinst, the System Landscape Implementation Manager, you must perform some preparations.

Because SAPinst is a Java-based tool, the Java Development Kit (JDK) must be installed on all hosts where SAPinst will run. After installing the JDK, you must perform some rework.

You can find the released JDK versions in the SAP Service Marketplace at http://service.sap.com/platforms. Choose Availablility of SAP components in Detail → SAP Web AS / Basis / Kernel → OS/DB/JDK releases for SAP Web AS 6.20.

After the successful JDK installation, check the Java /ext directory to see if there are already <parser_name>.jar files, for example, xerces.jar. The default path is <JAVA_HOME>/JRE/lib/ext.

If you find any .jar files, do the following: Rename them to xerces.xxx,for example. This is possible only if the application to which the JAR

files belong is not running during the installation. Remember to rename the files back to their original names after the installation procedure is

complete.


© SAP AG 2003

UNIX: Setting Environment Variables

SAPinst needs the JAVA_HOME environment variable to be set on the host(s) where SAPinst will run.

Set the JAVA_HOME environment variable (for user root) to <JAVA_HOME>.

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

For Unicode installation only: Add /sapmnt/<SAPSID>/profile to the library path environment variable

Use the following commands (dependent on your shell) for setting the environment variables: Bourne Shell (bsh) JAVA_HOME=<JAVA_HOME> export JAVA_HOME

DISPLAY=<Host_name>:0.0 export DISPLAY C Shell (csh) setenv JAVA_HOME <JAVA_HOME>

setenv DISPLAY <Host_name>:0.0 Korn Shell (ksh) export JAVA_HOME=<JAVA_HOME>

export DISPLAY=<Host_name>:0.0 Name of the library path environment variable:

AIX: LIB_PATH HP-UX: SHLIB_PATH LD_LIBRARY_PATH (for all other UNIX operating systems)


© SAP AG 2003

Preparation Checklist for Windows

SAPTRANSHOST set

JDK installed

Java \ext directory cleaned up

User has admin rights / min. passw. length=0

JAVA_HOME set

Size of file cache reduced

WIN NT only: Dynamic link libraries updated

File system is NTFS

CDs available (copied to disk / in CD drive)

SAP Front End available

Installation guide and SAP Notes read

SAP Notes downloaded and printed out

Installation guide downloaded and printed out


© SAP AG 2003

Preparation Checklist for UNIX

JAVA_HOME set

DISPLAY set

Java /ext directory cleaned up

JDK installed

File system setup

kernel parameters checked / set

OPT.: Users created

CDs available (copied to disk / in CD drive)

SAP Front End available

Installation guide and SAP Notes read

SAP Notes downloaded and printed out

Installation guide downloaded and printed out


© SAP AG 2003

Further Information

SAP Service Marketplace http://service.sap.com:

Quick Links /platforms, /instguides


© SAP AG 2003

Installation Preparation: Unit Summary

Perform the necessary preparations for the installation of SAP R/3 Enterprise



Exercises

Unit 3: Installation Preparation

At the conclusion of this exercise, you will be able to:

• Perform the necessary preparations for the installation of the SAP R/3 Enterprise system

You would like to prepare the installation of SAP R/3 Enterprise.

3-1 Check if the installation CDs are available.

3-1-1 To log on to your host, use the host name, user name, and password given to you by your instructor.

Note: Use pcAnywhere to connect to your host.

You find the installation CDs under G:\SETUP. The following CDs should be there: Export_1 to _7, Kernel, Language_1, Presentation, RDBMS_SAP_DB, SAP_J2EE_Engine, SAPINST, Server_Comp_1 and _2.

3-2 Check and/or adjust necessary operating system settings and prepare the SAP system transport host.

3-2-1 Check if the file system of the installation partition (G:) is NTFS.

3-2-2 Reduce the size of the Windows file cache by editing the properties of the local area connection.

3-2-3 Check if your user has administration rights.

3-2-4 Check if the minimum password length is set to 0. If not, change it to 0.

3-2-5 Prepare your host to be the SAP system transport host.

3-3 Prepare the SAPinst installation by installing the Java 2 SDK and setting the JAVA_HOME environment variable.

3-3-1 Install the Java 2 SDK.

3-3-2 Set the JAVA_HOME environment variable to the just installed Java Home directory.

3-3-3 Add the Java home directory to the Path environment variable.


Installation Preparation Solutions

Unit 3: Installation Preparation


• Perform the necessary preparations for the installation of the SAP R/3 Enterprise system

You would like to prepare the installation of SAP R/3 Enterprise.

3-1 Check if the installation CDs are available.

3-1-1 To log on to your host use the host name, user name and password given to you by your instructor.

Note: Use pcAnywhere to connect to your host.

You find the installation CDs under G:\SETUP. The following CDs should be there: Export_1 to _7, Kernel, Language_1, Presentation, RDBMS_SAP_DB, SAP_J2EE_Engine, SAPINST, Server_Comp_1 and _2.

Follow the exercise description.

3-2 Check and/or adjust necessary operating system settings and prepare the SAP system transport host.

3-2-1 Check if the file system of the installation partition (G:) is NTFS.

Follow the directions given on slide and notes to slide "Windows File System: NTFS."

3-2-2 Reduce the size of the Windows file cache by editing the properties of the local area connection.

Follow the directions given on slide "Windows: Reducing Size of File Cache."

3-2-3 Check if your user has administration rights.

Follow the directions given on slide and notes to slide "Windows: User for Installation."

3-2-4 Check if the minimum password length is set to 0. If not, change it to 0.

Follow the directions given on slide and notes to slide "Windows: User for Installation."


3-2-5 Prepare your host to be the SAP system transport host. Follow the directions given on slide and notes to slide "Windows: SAP System Transport Host."

3-3 Prepare the SAPinst installation by installing the Java 2 SDK and setting the JAVA_HOME environment variable.

3-3-1 Install the Java 2 SDK.

Go to G:\SETUP\ADM110\J2SDK and double-click on the j2sdk-1_3_1_07-windows-i586.exe file. As a help, you can refer to the slides "Windows: Java SDK Installation" (two slides).

3-3-2 Set the JAVA_HOME environment variable to the just installed Java Home directory.

Follow the directions given on slide "Windows: Environment Variable JAVA_HOME (1/2)."

3-3-3 Add the Java home directory to the Path environment variable.

Follow the directions given on slide "Windows: Environment Variable JAVA_HOME (2/2)."


© SAP AG 2003

Installing SAP GUI





23

56

4





Installing SAP GUI


© SAP AG 2003


Content:Installation of SAP GUI for Windows (local/Server)

Patching SAP GUI for Windows

Installation of SAP GUI for Java


Prepare and execute an installation of SAP GUI for Windows


© SAP AG 2003

Variants of SAP GUI

SAP GUI for Windows

SAP GUI for Windows

SAP GUI for HTML

SAP GUI for HTML

SAP ITS

CommonServer

CGI* TCP/IP AGateWGateWeb-Server

SAP GUI for Java

SAP GUI for Java

Dispatcher

DIAG / RFC

DIAG / RFC

DIAG / RFC

HTML

More information on http://service.sap.com/ui

There are three classical GUI (graphical user interface) variants for accessing SAP systems: SAP GUI for Windows SAP GUI for HTML SAP GUI for Java

There are other options for accessing SAP systems, not covered here: portal interfaces (such as iViews), Business Explorer (BEx) for accessing SAP BW systems, and more.

SAP GUI for HTML requires the SAP Internet Transaction Server (SAP ITS) for providing access to an SAP system. The use and implementation of the SAP ITS is covered in other courses, for example, ITS170 and ADM102.

One common aspect for SAP GUI for Windows and SAP GUI for Java is that both GUIs use the SAP protocol DIAG for communicating with the SAP system (more specifically, with one instance of an SAP system). This protocol requires a very small bandwidth, thus reducing network load.

You will find more SAP GUI related information on http://service.sap.com/ui.


© SAP AG 2003

Local Installation SAP GUI for Windows (1/3)

Follow these steps for a local installation SAP GUI for Windows:

1. Start setup.exe in \GUI\Windows\Win32 on the Presentation CD2. Follow the screenshots given here

The next slides describe the local installation of SAP GUI for Windows.


© SAP AG 2003


Select the installation directory

Select the installation directory for the local installation of the SAP GUI.


© SAP AG 2003


Select front-end components to be installed

After you select the components to be installed, the installation runs and closes with the second screen shown above.


© SAP AG 2003

Installing an SAP GUI Installation Server (1/9))

Follow these steps:

1. Start admsetup.exe in \GUI\Windows\Win32\setupon the Presentation CD

2. Follow the instructions in the SAP Front End Installation Guide, which you will find on the Presentation CD in the folder \DOCU: pc620_EN.pdf

3. Follow the screenshots given here

Name a shared directory

Another option to install SAP GUI for Windows on many front-end computers (in addition to the local installation on each front-end as shown in the previous slides) is much more performant and desirable: Install an installation server for SAP GUI for Windows and let the system do the distribution work of the SAP GUI software.

For this installation server, you need a shared directory, as shown above.


© SAP AG 2003

Installing an SAP GUI Installation Server (2/9)

Configure the Distribution Service

Next you need to configure the distribution service.


© SAP AG 2003



This distribution service requires users (and their passwords) to be used during the remote installation.


© SAP AG 2003



After installing the distribution services, you must define packages of software to be distributed (as explained in the next few slides).


© SAP AG 2003


Observe SAP Note 587533"[...] This list of files can be ignored. […]"

You can ignore the error message shown in the figure. Refer to SAP Note 587533 for details.


© SAP AG 2003


Create a new SAP GUI Installation package

Double-click SapAdmin.exe

To set up installation packages, you start the SapAdmin.exe program. You can use this program to create new installation packages for SAP GUI for Windows.


© SAP AG 2003


Select front-end components to be installed

You need to define the components to be included in the new package.


© SAP AG 2003


Use server-based installation in LANLocal Installation in WAN and on mobile front ends

For the installation packages, you have two options for defining where the installation should reside: The local installation puts all necessary software on the front end, leaving a footprint of up to 200 MB. In this case, the amount of work for updating the local installations is higher than for the second option.

The server-based installation leaves many files on the server and puts only essential files on the front-end computers (some a few MB in size). During startup of the SAP GUI, the remaining files are transferred from the server to the front-end via the network. Because the amount of data transferred is quite high, this option should be used in LAN environments only, whereas the first option is the first choice in WAN environments.


© SAP AG 2003


Give the location of the SAP GUI patch file, see next slides

The installation server can be updated in the similar way to a stand-alone SAP GUI. The same file is used. See the next slides.


© SAP AG 2003

Patching the SAP GUI (1/4)

Steps to be executed:

1. Download the newest SAP GUI patch from http://service.sap.com/patches to your server

2. Follow the screenshots given on the next pages

SAP Logon About SAP Logon

Start sapgui –v

In SAP GUI: Customizing of local layout About

On the screenshots, you see the versions for the primary SAP GUI components: SAPLogon.exe, SAPGUI.exe and Front.exe.

The patch level of the build in the example in the figure is 22. This build can be patched with a later version available on the SAP Service Marketplace.


© SAP AG 2003


Double-click GUI-patch

Simply start the patch application by starting the patch executable.


© SAP AG 2003


Restart the computer

After applying the patch, you have to restart your front-end computer because some essential .dlls were exchanged.


© SAP AG 2003


Check new patch level

After the patch is applied, the new patch level of the components shown in the figure is 32.


© SAP AG 2003

Installing SAP GUI for Java (1/3)

Double-click PlatinGUI-###.jar

Name the installation directory

Download the SAP GUI for Java installation (Rev 8) files from ftp://ftp.sap.com/pub/sapgui/java/620r8 and select your platform.

Start the installation by executing the downloaded file and proceed as shown in the figure.


© SAP AG 2003


Configure SAP GUI for Java

You can find the configuration details for SAP GUI for Java in the documentation. The documentation is installed together with the SAP GUI and can be found in the folder [Installation directory]\6.20rev8\doc\manual.htm (correct for SAP GUI for Java Rev 8).


© SAP AG 2003


Check version of SAP GUI for Java

To get information about the version of SAP GUI for Java in use, click the question mark (?) icon in the upper-right corner of the GUI.


© SAP AG 2003

Further Information

SAP Service Marketplace, http://service.sap.com/patchesand http://service.sap.com/uiPresentation CD 1, folder DOCUSAP Notes as listed in this unit


© SAP AG 2003

Installing SAP GUI: Unit Summary

Prepare and execute an installation of SAP GUI for Windows



Installing SAP GUI Exercises

Unit 4: Installing SAP GUI


• Install a local SAP GUI for Windows

• Patch a local SAP GUI for Windows

You would like to install SAP GUI for Windows and update it.

4-1 Install a local SAP GUI for Windows on the server you are using for the training, for example, on twdf0###.

4-1-1 Start the program setup.exe from the Presentation CD folder \GUI\Windows\Win32 and use the default installation directory.

4-1-2 Choose some SAP GUI components of your choice (should contain at least SAP GUI with SAP Logon) to be installed and finish the installation.

4-2 Raise the patch level of your locally installed SAP GUI for Windows.

4-2-1 Check the current patch level of your SAP GUI components.

4-2-2 You find the patch to be applied in the following location:

G:\SETUP\ADM110\SAP_GUI_Patch_32

Proceed as described in this training material on the pages "Patching the SAP GUI (2/4)" and "Patching the SAP GUI (3/4)."

4-2-3 Check the new patch level of your SAP GUI components.

4-3 Optional: Install and configure SAP GUI for Java on the server you are using for the training, for example, on twdf0###..

4-3-1 Install the SAP GUI for the Java Environment. You find the installation files in the following location:

G:\SETUP\ADM110\ SAP_GUI_For_Java

Proceed as described in the training material.


4-3-2 Configure the SAP GUI for Java exactly with the same configuration files as shown on slide "Installing SAP GUI for Java (2/3)." You have to adapt the content of the configuration files to fit your system environment (<SID>, <server>).


Installing SAP GUI Solutions

Unit 4: Installing SAP GUI


• Install a local SAP GUI for Windows

• Patch a local SAP GUI for Windows

You would like to install SAP GUI for Windows and update it.

4-1 Install a local SAP GUI for Windows on the server you are using for the training, for example, on twdf0###.

4-1-1 Start the program setup.exe from the Presentation CD folder \GUI\Windows\Win32 and use the default installation directory.

Start the program setup.exe from G:\SETUP\presentation\GUI\Windows\Win32.

4-1-2 Choose some SAP GUI components of your choice (should contain at least SAP GUI with SAP Logon) to be installed and finish the installation.


4-2 Raise the patch level of your locally installed SAP GUI for Windows.

4-2-1 Check the current patch level of your SAP GUI components.

Follow the directions given on slide "Patching the SAP GUI (1/4)."


G:\SETUP\ADM110\SAP_GUI_Patch_32. Proceed as described in this training material on the pages "Patching the SAP GUI (2/4)" and "Patching the SAP GUI (3/4)."


4-2-3 Check the new patch level of your SAP GUI components.

See 4-2-1.


4-3 Optional: Install and configure SAP GUI for Java on the server you are using for the training, for example, on twdf0###.

4-3-1 Install the SAP GUI for the Java Environment. You find the installation files in the following location:

G:\SETUP\ADM110\ SAP_GUI_For_Java.

Proceed as described in the training material.


4-3-2 Configure the SAP GUI for Java exactly with the same configuration files as shown on slide "Installing SAP GUI for Java (2/3)." You have to adapt the content of the configuration files to fit your system environment (<SID>, <server>).



© SAP AG 2003






23

56

Installing SAP GUI4






© SAP AG 2003


Content:Central and dialog instance installation

Database installation

SAP J2EE Engine installation


Install a central instance

Install a database instance

Install an SAPJ2EE Engine instance

Install a dialog instance


© SAP AG 2003


SAPinst Installation

Central Instance Installation

Database Instance Installation

SAP J2EE Engine Installation

Dialog Instance Installation

Appendix: Gateway Instance Installation


© SAP AG 2003

Prerequisites for SAPinst

Prerequisites to run SAPinst: Windows:

Do not use Microsoft Terminal Server for any installation procedure with SAPInst. To connect remotely to server hosts, use applications such as Symantec pcAnywhere or VNC.

Install Java Development Kit (SDK)Set the environment variable JAVA_HOMECheck SAPinst host for .jar-files to avoid SAPinst errors

UNIX: Non-Unicode SAP system installation: - The setting of the library path environment variable is required only for the central system and the

database instance installation. Unicode SAP system installation: - The setting of the library path environment variable is required for all SAP instance installations.

As user root, set the library path environment variable on your installation host depending on the used shell. (See Unit 3 Installation Preparation and installation guide for more information)


© SAP AG 2003

Start SAPinst

Operating System:Each SAP component is installed separately:

Central InstanceDB InstanceDialog InstanceSAP J2EE Engine

Start the SAPinst for the first time from the SAPinst CD.

UNIX: <SAPinst CD>/SAPINST/UNIX/<platform>/INSTALL

Windows:<CD drive>:\SAPinst\NT\setup.cmd

Because the SAPinst installation directory contains important log and command files for the installation, make sure that you use a separate installation directory for every instance you are going to install. Otherwise, you might lose previous log and command files stored in the SAPinst installation directory.

When you install an SAP instance with SAPinst for the very first time on your host, start SAPinst from the SAPinst CD. SAPinst is copied to the directory you have specified. This directory is also used as the installation directory for the instance you are installing.

If you install an SAP system with SAPinst for the very first time on a host, you have to start SAPinst from the Kernel CD with setup.cmd. Afterwards, you can use the Windows Start menu to install additional SAP or database instances on the same host.


© SAP AG 2003

Start Menu Entries

Use the Windows Start menu to install additional SAP or databaseinstances on the same host

Prepare new installationRemove SAPinst filesSAPinst GUISAPinst server onlySAPinst server with GUI

After the first installation of SAPinst, SAPinst is copied to <SAPinst_INSTDIR> and the start menu entries are created.

You can install SAPinst with one of the following five options: Prepare new installation: Backup all old installation files and logs and create a new installation control file.

Remove SAPinst files: Delete all the files in the installation directory. SAPinst GUI: Use this GUI for a remote installation. SAPinst Server only: Start scroll mode but wait for remote installation call. SAPinst server with GUI: Use GUI for local installation.


© SAP AG 2003

SAPinst Welcome Screen

SAPinst uses the default ports 21212 and 21213 for the communication with SAPinst GUI

The port numbers can be customized by editing the setup.cmd file

The following slides describe preparations for a local installation with SAPinst. However, you can also perform a remote installation using a standalone SAPinst GUI on a separate

Windows or UNIX host. This enables you to perform the installation on a remote host while monitoring it with SAPinst GUI from a local host (more information on the following slides).

Accept the license agreement for STLport. You agree to use an SAP granted license for STLport.org C++ library (STLport) and its documentation. The company STLport has extended the standard C++ library. (STL = standard template library)

SAPinst uses the ports 21212 and 21213 during the installation for communication with SAPinst GUI. You get an error message if one of these ports is already in use (refer to Unit 9, "Troubleshooting Installation Problems").


© SAP AG 2003

SAPinst Installation Default Parameters

Select Custom not Standard for Installation DirectoryOn Windows 2000, create a separate menu item

Don’t overwrite other installation directories

SAPinst asks to perform a standard or custom installation. If you select Standard installation, the default settings for the installation directory and the start menu entry, which are mentioned in the first lines of the screen, are used.

If you select a Custom installation, you can define the installation directory and the start menu entry for SAPinst. SAPinst defines SAPinst folder in the start menu. For example, enter 'R3_Enterprise_47' as the start menu during the installation. Then SAPinst creates this start menu: Start → Programs → R3_Enterprise_47.

When running SAPinst, you should use the Custom installation mode to set up an installation directory, which should have no spaces in its name.

Connection parameters are not relevant for a local installation.


© SAP AG 2003

SAPInst Installation Finished

SAPinst is successfully installed

Start menu entries are made

In the Preparing the installation program phase, all necessary control files are copied to the installation directory. SAPinst writes the logfile sapinst.log in directory C:\WINNT\Temp\SAPinst. All actions that are executed during the SAPinst installation process are stored there.

Reboot on Windows 2000 because SAPinst overwrites system DLLs.


© SAP AG 2003

Remote Installation with SAPinst

PC

SAPinst GUI

SAP-Server

SAPinst

CommunicationPort: 21212, 21213

local remote

Basic steps:1. Install SAPinst on your remote host and SAPinst GUI on your

local host.2. Start SAPinst server on your remote host.3. Start SAPinst GUI on your local host.4. Perform the installation using SAPinst GUI.

You can run SAPinst GUI in standalone mode. This allows you to install an SAP system on another host (the remote host) while monitoring the installation with SAPinst GUI on your local Windows or UNIX computer (the local host). To perform a remote installation, you do not need to set the JAVA_HOME environment variable on the instance host.

Prerequisites to perform a remote installation with SAPinst: Both computers are on the LAN and can ping each other. SAPinst uses the ports 21212 and 21213 during the installation for communication with SAPinst GUI. If one of these ports is already used by another service, SAPinst aborts the installation. In this case, start SAPinst or SAPinst GUI from the command prompt as follows: - For UNIX:

SAPinst: ./sapinst SAPINST_DIALOG_PORT=<free_port_number> SAPinst GUI: ./sapinstgui.sh -port <free_port_number>

- For Windows: SAPinst: sapinst SAPINST_DIALOG_PORT=<free_port_number> SAPinst GUI: sapinstgui.bat -port <free_port_number>


© SAP AG 2003

SAPinst - Output Files

sapinst.log

sapinst_dev.log Contains most important and detailed messages

Displays the component (phase) in which the error occurred

sapinstkdb.dmp

instgui.log

Additional log files might be written during the installation process. These additional logs are referenced in sapinst.log. Additionally, there are other log files, sapinst_dev.log and instgui.log (SAPinst GUI host only), but these files are not relevant for analyzing error situations. They are for support purposes only.


© SAP AG 2003

SAPinst Building Blocks

Server

ModulesSysLib

OS

Control

KeyDB

Dialogs

Messages

SAPinst GUI

Pack

ages

XML

File

s

Inst

alla

tion

para

met

ers

User input

Inst

alla

tion

arch

ives

PackageCD‘sStart

CD

SAPinst is designed to install components and re-usable sub-components with steps of each component. R3Setup was designed to install on component within steps.

Control Flow: The Installation Controller performs three main phases: PREPARE, ASK, and DO. Dialogs are not assigned to individual steps, so all dialogs can take part before the DO phase runs dark and are written in JavaScript.

The DO phase contains all steps contained in the control file. The steps within the Control Flow (DO Phase) are the restart points when the installation is aborted.

Installation modules are the equivalent to R3SETUP step classes and are written in C++ or Java. Syslib provides platform-independent access to common installation tasks related to the operating systems (creating users, running executables, changing environment variables, manipulating the file system, and so on). Syslib supports these operating systems: UNIX, LINUX, Windows, OS/400, OS/390. Syslib uses these file names on Windows: sylib.dll; on Unix: sylib.so (Sun). Syslib builds the basis for platform-independent installation modules.


© SAP AG 2003

Appendix: Preparing SAPinst Software

For dialog design: dialog.xmlDefinitions of screens, input fields, and so on

Fields can be activated/deactivated for input by setting thevariable enabled = true/false in the respective section

For persistency layer (KeyDB): keydb.xmlKeeps track of the installation progress

Contains status of each step

For logging/tracing service: messages.xml

For software package administration: packages.xml

For control flow: control.xmlContains the input values provided by the user

SAPinst offers these main advantages compared to R3SETUP, the previous tool: SAPinst lets you step back to correct your entries during the input phase without restarting the

installation. SAPinst does not abort due to errors. Instead, it stops the installation and you can retry the installation

after solving the problem. Alternatively, you can abort the installation manually if you want. SAPinst continues an aborted installation directly from the point of failure. SAPinst records installation progress in a single log file, sapinst.log. SAPinst has a graphical user interface (GUI), SAPinst GUI, that allows you to monitor the progress

of the installation and see all messages issued by SAPinst. As SAPinst GUI is Java based, you need a Java Runtime Environment (JRE).

You can start SAPinst GUI on a remote computer if you want. For more information on SAPinst, see the documentation, SAPinst Troubleshooting Guide at http://service.sap.com/sapinstfeedback.


© SAP AG 2003

Appendix: SAPinst Input Files: dialog.xml

<dialog sid="diSAPSystemCommonParameters">

<title>SAP System Common Parameters</title>

<frame sid="fr1">

<frame sid="fr2">

<caption>SAP System</caption>

<label>Enter the SAP System name (three upper alphanumeric characters)</label>

<field sid="fiSAPSysID">

<caption>SAP System Id</caption>

<whatsthishelp>The three-digit SAP system id</whatsthishelp>

<value type=“alphanumeric" minlength=“3" maxlength=“3“/>

</field>

</frame>

...

</frame>

</dialog>


© SAP AG 2003

Appendix: SAPinst Input Files: keydb.xml

<tables><table name="SAPINST_INST_STATUS" namespaces="IA_CONTROLLER">

<columns><column name="STEPKEY“/><column name="STATUS“/>

</columns><rows>

<row><fld name="STEPKEY">

<strval><![CDATA[SUS_WPS|ind|ind|ind|SUS|ind|0|default_connection]]> </strval></fld><fld name="STATUS">

<strval><![CDATA[OK]]> </strval></fld>

</row></rows>

</table></tables>

SAPinst stores status information in keydb.xml

If phase ended successful, the STATUS is set to OK, otherwise to ERROR

When SAPinst is restarted after an error, it first saves keydb.xml to keydb.xml.<no>, and then resumes with the phase which has STATUS ERROR or “ “ (blank)


© SAP AG 2003

Appendix: SAPinst Input Files: control.xml<component name="DIALOG_INSTANCE" os-type="windows" os="ind" db="ind" product="bw" release=“30A">

...

<parameters>

<parameter name="HOSTNAME" defval="p77777">

<description>This is only a test parameter</description>

</parameter>

<parameter name="INSTANCE_NUMBER" defval="01">

<description>...and this is also a test parameter</description>

</parameter>

<subcomponents>

<subcomponent name="CREATE_DB" os-type="ind" os="sun" db="ind" product="bw" release=“10" table="c_TAB_CREAT_DB">

</subcomponents>

</component>

SAPinst components are the major building blocks of an installation

Components have attributes like OS type and DB type

Components have parameters which make up their context

Contexts are represented as rows in a components context table

SAPinst components are the major building blocks of an installation. SAPinst components have attributes such as OS type and DB type. SAPinst components have parameters; the set of parameters of a component makes up its context. Contexts are represented as rows in a component's context table. When a component is referenced as a subcomponent, the parent component has to provide a context table.


© SAP AG 2003

Appendix: SAPinst Properties

SAPinst properties can be used to fine-tune SAPinst behavior:Specifying input files (overriding defaults)

Setting ports for communication with GUI

Start sapinst -p or sapinst -properties to see a complete list of all supported properties

Set the properties in the control.xml file as environmentvariables or on the SAPinst command line


© SAP AG 2003

Appendix: Oracle Software

For Oracle software:Install the Oracle database software

Install patch set

Windows procedure:Start on database client, sapclient.cmd

Start on database server, sapserver.cmd

UNIX procedure:./RUNINSTALLER

Enter the information: File locations: Do not change the path of the Oracle source software. Destination: Enter the name of the new Oracle Home directory. SAP recommends <DBSID><ORACLE_VERSION>

Destination: Enter the path of a new Oracle Home directory. SAP recommends <DRIVE>:\ORACLE\<DBSID>\<ORA_VERS>.

Create Database: NO Install the current Oracle 9i patchset:

See SAP Note 539921 for the number of the current patchset and SAP Note 355776 for more information on installing the current patchset. You need only install the latest Oracle patchset. Install this patchset using the Oracle Universal Installer.

You need 2.2 GB disk space for the Oracle 9.2.0 server software and about 250 MB for the Oracle 9.2.0 client software

Install the current Oracle 8x patchset: Refer to SAP Note 362060 for the number of the current patchset and the import instructions. Download it from sapserv<x> as described in SAP Note 362060.


© SAP AG 2003

Appendix: Settings for OS Users (AIX Only)

Checking Settings for OS Users (AIX only)

Check and, if necessary, modify the settings for the OS user root and users <sapsid>adm and sqd<sapsid> that were created by SAPinst.

root

<sapsid>adm

sqd<sapsid>


© SAP AG 2003

Start Installation of the Central Instance

Select:Unicode ... -Default to install a central, dialog or DB instance

Unicode Export ... to perform a system copy

Accept the license agreement for STLport

After SAPinst is successfully installed, SAPinst automatically starts the installation of your component (for example R/3 Enterprise Unicode). First the Welcome screen displays the possible actions (for example, installation or export of a R/3 Enterprise Unicode system).

If the installation does not start automatically, start it manually. To start the installation with SAPinst, choose Start → Programs → SAPinst_menu_entry → SAPinst server with GUI.

Accept the license agreement for STLport.


© SAP AG 2003

Instance Installation Type, SID, Instance Number

Enter an instance numberAssign a value from 0 to 97 as instance number

Avoid the numbers 02, 25, 72, or 89 because they might be used by other programs

Enter the system ID

Select Central instance

SAP system ID: Enter the SAP system <SAPSID>, for example, C11. The ID (identifier) for your SAP system (<SAPSID>) and for your database system (<DBSID>) must be unique throughout your organization and must consist of exactly three alphanumeric characters. Only uppercase letters are allowed. The first character must be a letter (not a digit).

Because the following IDs are reserved, you cannot assign them to your SAP system: - 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 Renaming is complicated and requires you to re-install the SAP system.

Instance number: Enter the instance number of the central instance. The number must be two digits and must be unique for this host. Assign a value from 0 to 97. Port 98 and 99 are reserved for SAProuter.

For Windows installations, do not use port 02, 25, 72 and 89. The reason is that there are known problems with other applications (for example, Windows Terminal Server Manager), which also use these ports. SAPinst does not check for occupied ports during the installation.

Already installed instances are not affected. If an instance works properly, there is obviously no port conflict.


© SAP AG 2003

Database Parameters

Enter the database system ID Recommendation: Use the same IDs for databasesystem and SAP system

Enter the database host

Enter the ID of the database instance <DBSID>. SAP recommends that you use the same IDs for the database system and the SAP system. However it is possible to use a database instance ID that is different from the SAP system ID.

To find out the host name, enter hostname at the command prompt of the database host.


© SAP AG 2003

Windows Domain Information and RAM

Windows only:Domain information for SAP system user account on operating system

Select RAM quantity

Random Access Memory (RAM) and swap space for the central instance: The default value is the entire RAM or swap space. Reserve some RAM for the database instance and SAP J2EE Engine. Be sure to reserve at least the minimum values required for the instance (at least 256 MB for a non-unicode SAP system; at least 384 MB for a unicode SAP system).

This value is two-thirds of the machine RAM on a distributed system (central and database instances on different hosts) and one-third of the machine RAM on a central system (central and database instances on same host).

For installations on the Windows operating system, use the following information. Domain information for the SAP system accounts: - Local installation: All Windows account and user information is stored locally. Perform a local

installation for an SAP system to run on a single host (for a distributed system authorization problems can occure).

- Installation in a different domain - Installation in the domain of the current user

In a domain installation, the user information is stored centrally on the domain controller and is accessible from all hosts in the system. If the system is to be distributed across more than one machine, SAP strongly recommends a domain installation.


© SAP AG 2003

LDAP (Unicode Installation Only)

Select No LDAP if you do not want to use an LDAP service

LDAP (lightweight directory access protocol) allows important information within a corporate network to be stored centrally on a server where it can be easily accessed and administered. If an LDAP directory is available in the corporate network, you can configure the SAP system to use this feature. For example, a configured SAP system can read information from the directory and also can store information there.

Active Directory: Select this option to integrate Windows 2000 Active Directory services. The Active Directory is a feature of Windows 2000 and is automatically available on all domain controllers.

To enable an SAP system to make use of the features offered by the Active Directory, you must configure both the Active Directory and the SAP system. You must decide whether you want to use Active Directory before the installation because it influences the installation process.

Generic LDAP Directories Select this option to configure the system to support LDAP directories that are running on Windows or UNIX machines.

The process of preparing the SAP system for using generic LDAP services involves a number of manual steps. Both the LDAP directory and the SAP system must be configured.

No LDAP: Select this option if you do not want to use LDAP at all.


© SAP AG 2003

Instance Directory and Transport Host

Select the drive for the SAP base directory tree \usr\sap\

Enter the name of the host where the central transport directory \usr\sap\trans is located

Windows: Drive for SAP system Select the drive for the SAP base directory tree. For example, if you select 'D', the directory \usr\sap\ is created under drive D. If saploc already exists, you cannot select the local instance directories.

UNIX: SAP system mount directory Enter or confirm the base directory for the SAP system. Do not add <SAPSID> as subdirectory because the system automatically creates this directory. That is, if you enter '/sapmnt', the system creates the directory /sapmnt/<SAPSID> .

Host with transport directory: Here you must enter the name of the host where the central transport directory is located.


© SAP AG 2003

Set Passwords for Operating System User

Enter and confirm:Password for <SID>adm

Password for SAPService<SID>

System administrator <sapsid>adm: Enter and confirm the password for the SAP system administrator <sapsid>adm.

SAP system service administrator: Enter and confirm the password for the SAP system administrator SAPService<sapsid>.


© SAP AG 2003

CD Browser and Message Server Port

Enter the Message server port

Enter the port number, 36<##> ##: instance number of central instance

Select location of Kernel CD

During the installation procedure, SAPinst first checks and finally verifies the availability and location of the required installation CDs. SAPinst does this by displaying the CD Browser window, asking for the LABEL.ASC file that contains information about the software package to be installed.

SAPinst checks the availability of the software package. You can recognize this situation by the Check Location flag displayed in the CD Browser window.

Message port: Enter the port number for the message server. The default value is 36## where ## stands for the instance number of the central instance. The port number must be identical for all instances belonging to the same SAP system.


© SAP AG 2003

CD Browser: RDBMS CD

Select:Location of RDBMS CD


© SAP AG 2003

Installation Steps

SAPinst displays the progress of the installation by highlighting the currently active installation phase


© SAP AG 2003

Finish Central Instance Installation


© SAP AG 2003

Preparation for Database Instance Installation

SAPinst:

1. Prepare new installation

2. SAPinst Server with GUI (to start SAPinst)

It is also possible to start SAPinst from the SAPINST CD with the command SETUP.CMD on Windows and INSTALL on UNIX. SAPinst will be reinstalled and you can select a new installation directory.


© SAP AG 2003

Start of Database Instance Installation

Select:Unicode SAP R/3 Enterprise 4.71 for SAP DB – Default to perform the installation of the DB instance



© SAP AG 2003

Instance Installation Type and SID

Enter the SAP system ID that you used during central instance installation

Select Database instance to install your database


© SAP AG 2003

Database Installation Method and Type

Select Standard Installation to start a database load from "Export" Installation CDs

Select System Copy / Migration to perform a database load of an export file from an existing SAP system

Normal database installation:

Select Install (first) SAP system into a new database

MCOD database installation:

Select Install (additional) SAP system into an existing database

Follow this procedure to install the database instance: If you want to copy or migrate an existing SAP system, select System Copy/Migration (for more information, see the documentation, SAP Web Application Server Homogeneous and Heterogeneous System Copy). Otherwise, choose Standard Installation.

If you select System Copy/Migration, you must do the following: - Leave the Migration Key field blank if you want to import the database dump of another SAP

system as part of a homogeneous SAP system copy. - Enter the migration key if you want to import the database dump of another SAP system as part of a

heterogeneous SAP system copy. - Refer to SAP Note 516246 for the latest information for homogeneous and heterogeneous system

copy. How to select the database instance type:

If you install a system into an existing database (MCOD), select Install (additional) SAP system into an existing database. In all other cases, select Install (first) SAP system into a new database.


© SAP AG 2003

Database and Central Instance Parameters

Enter the database system ID

Recommendation: Database ID should be identical to SAP system ID

Enter

Central instance number

Central instance host

Enter exactly the same ID of the database instance <DBSID> that you entered during the central instance installation.

Enter exactly the same central instance number that you entered during the central instance installation. To find out the number, look under the SAP directory \usr\sap\<SAPSID>\DVEBMGS<##>. The value <##> is the number assigned to the central instance.

Enter exactly the same name of the central instance host that you entered during the central instance installation.


© SAP AG 2003



Select RAM quantity


© SAP AG 2003


Enter:Name of the host where the central transport directory \usr\sap\trans is located

In the Host with transport directory field, enter the name of the host where the central transport directory is located.


© SAP AG 2003


Enter and confirm:Password for <sapsid>adm


System Administrator <sid>adm: Enter and confirm the password for the SAP system administrator. The password can be different from <sid>adm on the central instance.

System Administrator SAPService<SID>: Enter and confirm the password for the SAP system administrator SAPService<SID>. The password can be different from SAPService<SID> on the central instance.


© SAP AG 2003

CD Browser: Kernel, RDBMS and Export CD

Select:Location of Kernel CD

Location of RDBMS CD

Location of Export 1 CD


© SAP AG 2003

Installation Directory: Database Client Software

Select drive for database client software

Select the disk drive on which you want to install the database client software.


© SAP AG 2003

Database Parameters and Operation Mode

Select:Database log mode

Number of work processes

CPU

RAM

These instructions are valid for an SAPDB installation only: Select a database logging mode:

Demo – Logs are overwritten and insecure. Single – Logs are written but not mirrored. This is recommended in combination with hardware mirroring. Dual – Logs are written and mirrored; this causes performance overhead.

Number of work processes: If you have additional dialog instances, enter the number of workprocesses accordingly.

In the Max CPU field, enter the number of physical CPUs on your system that can be used by the database.


© SAP AG 2003

LOG and DATA Devspace Settings, Unicode

Select:Location and size of LOG devspace

Select:Location and size of DATA devspace

Enter a size for the LOG devspace. The maximum size depends on the operating system. If you are mirroring the devspace (dual mode), enter the drive.

You must enter at least one LOG devspace. The sum of the LOG devspaces that you specify must exceed minimum LOG size in MB.

You must enter at least one DATA devspace. The sum of the DATA devspaces that you specify must exceed minimum DATA size in MB.


© SAP AG 2003

LOG and DATA Devspace Settings, Non-Unicode

Select:Location and size of LOG devspace

Select:Location and size of DATA devspace


© SAP AG 2003

SYSTEM Devspace Settings, Unicode

Select:Location and size of SYSTEM devspace

Select whether to accept the default location or enter a self defined location. If you want to use your self defined location, enter the directory for the system devspace.


© SAP AG 2003

SYSTEM Devspace Settings, Non-Unicode

Select:Location and size of SYSTEM devspace


© SAP AG 2003

CD Browser: Export CDs

Select:Location of Export 2 CD, Export 3 CD, Export 4 CD, and so on


© SAP AG 2003

Database Load Parameters, Unicode

Select:Default settings

Select how you want to load packages. Select your DB code page. Select how many parallel jobs you want to run. For the Number of parallel jobs, SAP recommends that you enter the number of processors of the server.

Advanced database configuration should be performed by certified database administrators only. SAP recommends that you use the default settings if possible.


© SAP AG 2003

Database Load Parameters, Non-Unicode

Select:Default settings


© SAP AG 2003

Multi National Language Support (Non-Unicode)

You need an SAP system with multi national language support if you plan to work with more than one code page in your SAP system. If you want to install Multi National Language Support (MNLS), select MNLS Support required. Then, the installation will stop before starting the SAP system to let you update the MNLS tables as described in SAP Note 45619 before continuing the installation.

If you do not want to install Multi National Language Support (MNLS), select No MNLS Support required.


© SAP AG 2003

Installation Steps



© SAP AG 2003

Logfile sapinst.log


© SAP AG 2003

Prepare Multi National Language Support (Non-Unicode)

To prepare for multi national language support, use the R3_languages.pdf file, which is attached to SAP Note 73606.


© SAP AG 2003

Change Passwords of ABAP Super Users

Enter:Password of ABAP super user DDIC

Password of ABAP super user SAP*

Enter and confirm a new password for user DDIC. The default password for user DDIC in client 000 will be changed.

Enter and confirm a new password for user SAP*. The default password for user SAP* in client 000 will be changed.


© SAP AG 2003

Finish Installation of Database Instance


© SAP AG 2003

SAP J2EE Engine

SAP Web AS 6.20 and SAP J2EE Engine:SAP J2EE Engine is implemented automatically during installation of SAP Web Application Server 6.20.

SAP R/3 Enterprise and SAP J2EE Engine:The SAP J2EE Engine is not required for SAP R/3 Enterprise 4.70. SAP J2EE Engine is not installed automatically with SAP R/3 Enterprise 4.70.

The SAP J2EE Engine is not required for SAP R/3 Enterprise 4.70. To use the system resources of your production environment in an optimal way, the SAP J2EE Engine is therefore not installed automatically with SAP R/3 Enterprise 4.70. Nevertheless, if you require the SAP J2EE Engine, you can install it as described in SAP Note 545422.


© SAP AG 2003

Preparation for SAP J2EE Engine Installation (1/2)

SAPinst:1. Prepare new installation

2. Copy TOPLEVEL.XML (overwrite existing file)

<SAPinstCD>/<Platform>/COMMON/INSTALL/TOPLEVEL.XML to the newly created installation directory (for example, G:\INSTALL_J2EE)


© SAP AG 2003

Preparation SAP J2EE Engine Installation (2/2)

3. Restart the installation:Start Programs SAPinst ... SAPinst server with GUI


© SAP AG 2003

Start SAP J2EE Engine Installation


Select:Unicode Upgrade SAP Central Instance Java Core 6.20 if you want to install SAP J2EE Engine for an existing SAP R/3 Enterprise central instance.


© SAP AG 2003

CD Browser

The SAP J2EE kits are shipped in three separate directories on one CD:

The J2EE-ENG contains the SAP J2EE Engine.

The JLIBS contains the J2EE development tools.

The SDM contains the Software Delivery Manager.

When SAPinst prompts for the SAP J2EE JAVA-COMPONENTS CD: CD J2EE-JAVA-COMPONENTS folder J2EE-ENG: Enter the path to the J2EE-ENG directory on the SAP J2EE CD (<SAP J2EE CD>\J2EE-ENG).

CD J2EE-JAVA-COMPONENTS folder JLIBS: Enter the path to the JLIBS directory on the SAP J2EE CD (<SAP J2EE CD>\JLIBS).

CD J2EE-JAVA-COMPONENTS folder SDM: Enter the path to the SDM directory on the SAP J2EE CD (<SAP J2EE CD>\SDM).


© SAP AG 2003

Parameters for Java Core

In production environments, specify 512 MB

Check the cmdline.properties file afterward for the entry: JavaParameters= -Xmx512m -Dmemory.manager=512m -Classpath

The User SAPJSF is required to enable communication between ABAP and the Java stack. User SAPJSF will be created using the function module PRGN_J2EE_CREATE_SERVICE_USE. For this reason you have to enter a user (for example, DDIC) with valid password.

For the SAP J2EE Engine, between 64 MB and 4096 MB of RAM are required, depending on the load of your SAP system.

Be sure to do the following: Check the memory settings that are entered for the J2EE-Server during Web AS installation. Check if the memory settings are applied to the file, cmdline.properties and not to the go.bat script.

New memory settings will be activated after the SAP J2EE server is restarted.


© SAP AG 2003

Installation Steps

SAPinst displays the progress of the installation by highlighting the currently active installation phase.

SAPinst prompts to restart the SAP system to activate instance profile changes.

During the adaption of the instance profile, the central instance profile is changed and parameters (for example, exe/j2ee, icm/HTTP/j2ee_0, rdisp/j2EE_*) are inserted.

During SAP J2EE Engine installation, you are prompted to restart the SAP system to activate the changes in profiles and continue the installation.


© SAP AG 2003

Finish Installation of SAP J2EE Engine


© SAP AG 2003

Preparation for Dialog Instance Installation

SAPinst:1. Prepare new

installation

2. SAPinst server with GUI (to start SAPinst)

It is also possible to start SAPinst from SAPINST CD with the command SETUP.CMD on Windows and INSTALL on UNIX. SAPinst will be reinstalled and you can select a new installation directory.

For a Dialog Instance only (UNIX): Mount directories from the central instance. If you want to install the executables locally instead of sharing them, create <sapmnt>/<SAPSID>/exe as a local directory (not a link) with a minimum of 240 MB of free space.

Follow this procedure to mount directories from the central instance host: 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

Log on to the dialog instance host as user root. Create the mount points with permissions 777: <sapmnt>/<SAPSID>/exe; <sapmnt>/<SAPSID>/profile; <sapmnt>/<SAPSID>/global and mount these directories. Check whether the dialog instance host has write access to the directories exe, profile and global: touch <sapmnt>/<SAPSID>/exe/nfs_test and rm <sapmnt>/<SAPSID>/exe/nfs_test


© SAP AG 2003

Start Dialog Instance Installation


Select:Unicode SAP R/3 Enterprise 4.71 Dialog Instance – Java if you want to install a dialog instance with SAP J2EE Engine.


© SAP AG 2003

Instance Installation Type, SID, Instance Number

Enter an instance number If the dialog instance is installed on the same host as the central instance, enter an instance number that is different from the centralinstance number

Enter system ID

Select Dialog instance

Enter exactly the same name of the SAP system <SAPSID> that you entered during the central instance installation.

Enter an instance number for the dialog instance. You can specify a value from 0 to 97. If more than one SAP instance is running on the same host, both instances must be assigned different numbers.


© SAP AG 2003

Central Instance and Database Parameters

Enter:Central instance number

Central instance host

Database system ID

Database host

Enter exactly the same instance number of the central instance. To find out the number, look under the SAP directory <DRIVE>:\usr\sap\<SAPSID>\DVEBMGS<##>. The value <##> is the number assigned to the central instance.

Enter exactly the same name of the central instance host that you entered during the central instance installation. To find out the host name, enter hostname at the command prompt of the central instance host.

Enter exactly the same name of the database instance <DBSID> that you entered during the central instance installation.

Enter exactly the same name of the database instance host that you entered during the central instance installation.


© SAP AG 2003



Select RAM quantity


© SAP AG 2003


Enter the name of the host where the central transport directory \usr\sap\trans is located


© SAP AG 2003


Enter and confirm:Password for <sapsid>adm


System Administrator <sapsid>adm: Enter and confirm the password for the SAP system administrator. The password can be different from <sapsid>adm on the central instance.

System Administrator SAPService<SID>: Enter and confirm the password for the SAP system administrator SAPService<SID>. The password can be different from SAPService<SID> on the central instance.


© SAP AG 2003

CD Browser and Message Server Port

Select location of Kernel CD

Enter the message server port 36<##>

## = instance number of central instance

Select location of RDBMS CD

The port number of the message server port must be the same as the one on the central instance host.


© SAP AG 2003

Database Schema and CD Browser

Select the required database schema (owner of SAP database tables)

User sapr3 for SAP systems with releases earlier than 4.6DUser sap<sid> for SAP systems with releases later than 4.6C

SelectThe J2EE-ENG contains the SAP J2EE Engine

The JLIBS contains the J2EE development tools

Verify that you are using the correct database schema definition. SAP DB user new style (sap<sid>): This SAP database user is used for connecting the SAP system to the SAP database.

SAP DB user sapr3: This SAP database user is used for connecting the SAP system to the SAP database. This user is always used for SAP systems based on releases earlier than 4.6D.


© SAP AG 2003

Parameter for SAP J2EE Engine

SelectMemory for SAP J2EE Engine of the dialog instance

EnterClient and password of user SAPJSF (created during SAP J2EE Engine installation for central instance)


© SAP AG 2003

Installation Steps



© SAP AG 2003

Finish Dialog Instance Installation


© SAP AG 2003

Appendix: Installing Client Software

Dialog instance installation:First install the client software for Microsoft SQL Server and Oracle on all hosts without the database before you start to install a dialog instance. The client software enables the communication between a host and the database.

For all other databases, the client software installation is integrated in the SAPinst installation.

Installation of the client software forMicrosoft SQL Server and Oracle only

For more information, see the installation guide, SAP J2EE Engine Installation/Dialog Instance Installation/Standalone Gateway Instance Installation on <platform>.


© SAP AG 2003

Appendix: Preparation for Gateway Instance Installation (1/2)

See SAP Note 492305: Windows GW Instance Inst. with SAP Pres. CD 6.20 Compilation 3 (C3). Proceed as follows:

Move the directory Presentation\NT\I386\MMC to Presentation\GATEWAY\NT\I386

To install a standalone SAP Gateway, run SAPinst(Setup.cmd) from the Presentation CD.



© SAP AG 2003

Appendix: Preparation for Gateway Instance Installation (2/2)

1. Install SAPinst 2. Choose installation directory

3. Finish SAPinst installation


© SAP AG 2003

Appendix: Start Gateway Instance Installation

Select:Install SAP Gateway if you want to install a gateway instance



© SAP AG 2003

Appendix: Installation Parameter

Enter:New SAP system ID

New instance number

Enter a new SAP system ID in the SAP System ID field. Do not use an SAP system ID that you entered during a central instance installation.

In the Instance Hostname field, enter the name of the gateway instance host. In the Instance Number field, enter the number of the gateway instance. You can assign a number from 0 to 97, but not the numbers 2, 25, 72, or 89.


© SAP AG 2003

Appendix: LDAP

Select No LDAP if you do not want to use an LDAP service


© SAP AG 2003

Appendix: Windows Domain Information and RAM


Select RAM quantity


© SAP AG 2003

Appendix: SAP System Directory

Select:Drive for SAP system directory


© SAP AG 2003

Appendix: Set Passwords for Operating System User

Enter and confirm:Password for <sid>adm



© SAP AG 2003

Appendix: CD Browser and Ports

Select:Location of Presentation CD folder Gateway


© SAP AG 2003

Appendix: Installation Steps and End of Gateway Installation


© SAP AG 2003

Further Information

SAP Service Marketplace, http://service.sap.com/instguides


© SAP AG 2003

Installation Process: Unit Summary

Install a central instance

Install a database instance

Install an SAPJ2EE Engine instance

Install a dialog instance



Installation Process Exercises

Unit 5: Installation Process


• Install SAPinst

• Install a central instance, database instance, SAP J2EE Engine instance, dialog instance

• Install a gateway instance

You perform an installation of an SAP system including SAP J2EE Engine and gateway instance.

5-1 Install SAPinst on the server you are using for the training, e.g. on twdf0###. 5-1-1 Create an installation directory named INSTALL. Use drive G:.

5-1-2 Start the program SETUP.CMD from the SAPinst CD in folder \SAPINST\NT\.

5-1-3 Perform the SAPinst installation.

5-2 Install the central instance on the server you are using for the training, for example, on twdf0###.

5-2-1 On the welcome screen, select SAP R/3 Enterprise 4.71 for SAP DB – Default to start the installation.

5-2-2 Install the central instance. Use the following information to perform the installation.

Note: Always use drive G: to install the software. You can select the following parameters freely with respect to the restrictions mentioned in the training material: SAP System ID Instance number Password for user <sid>adm Password for user SAPService<SID>

Make a note of the parameters because they are needed later on.


Select the values for the following parameters as indicated here:

Instance to install Central Instance Database System ID = SAP System ID Database Host Host name of your server

twdf#### Domain Information for the SAP System accounts

Local Installation

Instance RAM 800MB Drive for SAP System directory G: Host with Transport Directory Host name of your server

twdf#### Kernel CD G:\SETUP\Kernel Message port 3600 + central instance

number RDBMS CD G:\SETUP\RDBMS_SAP_DB

5-3 Install the database instance on the server you are using for the training, for example, on twdf0###.

5-3-1 Restart SAPinst.


5-3-3 Install the database instance. Use the following information to perform the installation.

Note: Always use drive G: to install the software.

You can select the following parameters freely with respect to the restrictions mentioned in the training material: Password for user DDIC (client 000)

Password for user SAP* (client 000)


Select the values for the following parameters as indicated here:

SAP System ID Same <SID> as for central

instance installation Instance to install Database Instance Database Installation Method Select Standard Installation Database Installation Type Install (first) SAP system into

a new database Database System ID = SAP System ID Instance number Enter instance number of

previously installed central instance


Instance Host Host name of your server twdf####

Domain Information for the SAP System accounts

Select Local Installation

Instance RAM 800MB (= RAM for central Instance)

Host with Transport Directory Host name of your server twdf####

Password for user <sid>adm Same password you used for central instance installation

Password for user SAPService<SID>

Same password you used for central instance installation

Kernel CD G:\SETUP\Kernel RDBMS CD G:\SETUP\RDBMS_SAP_DBExport CD 1 G:\SETUP\Export_1 Drive for the client software installation

G:

Log Mode for the Database Instance

Demo

Number of Work Processes 30 Max CPU 2 RAM for database caches 500MB Log Devspace Drive: G:

Size: 1000 Data Devspace Drive: G:

Size: 25000 System Devspace Drive: G: Export CDs (2 - 7) G:\SETUP\Export_2, _3, _4,

_5, _6, _7 Prepare multi national language support

Choose Continue installation

5-4 Install the SAP J2EE Engine instance on the server you are using for the training, for example, on twdf0###.


5-4-2 On the welcome screen, select Upgrade SAP Central Instance JAVA Core 6.20 to start the installation.

5-4-3 Install the SAP J2EE Engine instance. Use the following information to perform the installation:

You can choose the following parameters freely with respect to the restrictions mentioned in the training material: Password for user SAPJSF

Make a note of the password because it is needed later on.

Select the values for the following parameters as described: SAP J2EE Engine CD G:\SETUP\SAP_J2EE_E


ngine\J2EE-ENG G:\SETUP\SAP_J2EE_Engine\JLIBS G:\SETUP\SAP_J2EE_Engine\SDM G:\SETUP\SAP_J2EE_Engine\WASCOMP

Central Instance Profile G:\usr\sap\<SID>\SYS\profile\ <SID>_D*_<hostname>

SAP Web AS Administrator Account

User: DDIC Client: 000 Password: use same password as in database instance installation

SAP J2EE Engine Parameters JAVA VM maximum heap size: 64 MB

5-5 Optional: Install the dialog instance on the server you are using for the training, for example, on twdf0###.


5-5-2 On the welcome screen, select SAP R/3 Enterprise 4.71 Dialog Instance - Java to start the installation.

5-5-3 Install the dialog instance. Use the following information to perform the installation.


Select the values for the following parameters as described: SAP System ID Same <SID> you used for

central instance installation Instance number (dialog instance parameters)

Other than central instance number

Instance number (central instance parameters)

Enter instance number of previously installed central instance


Database System ID = SAP System ID Database Host Host name of your server



Instance RAM 350MB Host with Transport Directory Host name of your server

twdf#### Password for user <sid>adm Same password you used for

central instance installation




Kernel CD G:\SETUP\Kernel Message port Same port you used for

central instance installation RDBMS CD G:\SETUP\RDBMS_SAP_

DB Database schema SAP DB user new style SAP J2EE Engine CD G:\SETUP\SAP_J2EE_En

gine\J2EE-ENG G:\SETUP\SAP_J2EE_Engine\JLIBS

Maximum memory (MB) 64 SAP J2EE Engine communication user SAPJSF

Client: 000 Password: Same password you used for SAP J2EE Engine installation (on central instance)


Installation Process Solutions

Unit 5: Installation Process


• Install SAPinst

• Install a central instance, database instance, SAP J2EE Engine instance, dialog instance

• Install a gateway instance

You perform an installation of an SAP system including SAP J2EE Engine and gateway instance.

5-1 Install SAPinst on the server you are using for the training, for example, on twdf0###.

5-1-1 Create an installation directory named INSTALL. Use drive G:. Follow the exercise description.

5-1-2 Start the program SETUP.CMD from the SAPinst CD in folder \SAPINST\NT\. Start the program SETUP.CMD from G:\SETUP\SAPINST\SAPINST\NT.

5-1-3 Perform the SAPinst installation.

Proceed as described on the slides “SAPinst Welcome Screen,” “SAPinst Installation Default Parameters” and “SAPinst Installation Finished.”

5-2 Install the central instance on the server you are using for the training, for example, on twdf0###.




5-2-2 Install the central instance. Use the following information to perform the installation.


You can choose the following parameters freely with respect to the restrictions mentioned in the training material:

SAP System ID

Instance number

Password for user <sid>adm



Select the values for the following parameters as described:

Instance to install Central Instance Database System ID = SAP System ID Database Host Host name of your server



Instance RAM 800MB Drive for SAP System directory G: Host with Transport Directory Host name of your server

twdf#### Kernel CD G:\SETUP\Kernel Message port 3600 + central instance

number RDBMS CD G:\SETUP\RDBMS_SAP_DB

Proceed as described on the slides “Start Installation of the Central Instance,” “Instance Installation Type, SID, Instance Number,” “Database Parameters,” “Windows Domain Information and RAM,” “Instance Directory and Transport Host,” “Set Passwords for Operating System Users,” “CD Browser and Message Server Port,” “CD Browser: RDBMS CD,” “Installation Steps,” “Finish Central Instance Installation.”

5-3 Install the database instance on the server you are using for the training, for example, on twdf0###.


Proceed as described on the slide “Preparation for Database Instance Installation.”

(C) SAP AG ADM110 5-100



5-3-3 Install the database instance. Use the following information to perform the installation.



Password for user DDIC (client 000)

Password for user SAP* (client 000)

Make a note of the parameters because this information is needed later on.

Select the values for the following parameters as described:

SAP System ID Same <SID> as for central

instance installation Instance to install Database Instance Database Installation Method Select Standard Installation Database Installation Type Install (first) SAP system into

a new database Database System ID = SAP System ID Instance number Enter instance number of

previously installed central instance


Domain Information for the SAP System accounts


Instance RAM 800MB (= RAM for central Instance)

Host with Transport Directory Host name of your server twdf####

Password for user <sid>adm Same password you used for central instance installation



Kernel CD G:\SETUP\Kernel RDBMS CD G:\SETUP\RDBMS_SAP_DB Export CD 1 G:\SETUP\Export_1 Drive for the client software G:

(C) SAP AG ADM110 5-101

installation Log Mode for the Database Instance

Demo

Number of Work Processes 30 Max CPU 2 RAM for database caches 500MB Log Devspace Drive: G:

Size: 1000 Data Devspace Drive: G:

Size: 25000 System Devspace Drive: G: Export CDs (2 - 7) G:\SETUP\Export_2, _3, _4,

_5, _6, _7 Prepare multi national language support

Choose Continue installation

Proceed as described on the slides “Start of Database Instance Installation,” “Instance Installation Type and SID,” “Database Installation Method and Type,” “Database and Central Instance Parameters,” “Windows Domain Information and RAM,” “Instance Directory and Transport Host,” “Set Passwords for Operating System User,” “Installation Directory: Database Client Software,” “Database Parameters and Operation Mode,” “LOG and DATA Devspace Settings, Non-Unicode,” “SYSTEM Devspace Settings, Non-Unicode,” “CD Browser: Export CDs,” “Database Load Parameters, Non-Unicode,” “Multi National Language Support (Non-Unicode),” “Installation Steps,” “Prepare Multi National Language Support (Non-Unicode),” “Change Password of ABAP Super Users,” “Finish Database Instance Installation.”

5-4 Install the SAP J2EE Engine instance on the server you are using for the training, for example, on twdf0###.


Proceed as described on the two slides on “Preparation for SAP J2EE Engine Installation.”

5-4-2 On the welcome screen, select Upgrade SAP Central Instance JAVA Core 6.20 to start the installation.


5-4-3 Install the SAP J2EE Engine instance. Use the following information to perform the installation.



Password for user SAPJSF

(C) SAP AG ADM110 5-102

Make a note of the parameters, because it is needed later on. Select the values for the following parameters as described: SAP J2EE Engine CD G:\SETUP\SAP_J2EE_Engine\J2EE-

ENG G:\SETUP\SAP_J2EE_Engine\JLIBS G:\SETUP\SAP_J2EE_Engine\SDM G:\SETUP\SAP_J2EE_Engine\WASCOMP

Central Instance Profile G:\usr\sap\<SID>\SYS\profile\ <SID>_D*_<hostname>

SAP Web AS Administrator Account

User: DDIC Client: 000 Password: use same password as in database instance installation

SAP J2EE Engine Parameters JAVA VM maximum heap size: 64 MB

Proceed as described on the slides “Start of SAP J2EE Engine Installation,” “CD Browser,” “Parameters for Java Core,” “Installation Steps,” “Finish Installation of SAP J2EE Engine.”

Use the shortcut on the desktop, “SAP R/3 Management Console,” to restart the SAP system.

5-5 Optional: Install the dialog instance on the server you are using for the training, for example, on twdf0###.


Proceed as described on the slide “Preparation for Dialog Instance Installation.”

5-5-2 On the welcome screen, select SAP R/3 Enterprise 4.71 Dialog Instance - Java to start the installation.


5-5-3 Install the dialog instance. Use the following information to perform the installation.


Select the values for the following parameters as described: SAP System ID Same <SID> you used for

central instance installation Instance number (dialog instance parameters)

Other than central instance number

Instance number (central instance parameters)

Enter instance number of previously installed central instance


Database System ID = SAP System ID Database Host Host name of your server

(C) SAP AG ADM110 5-103



Instance RAM 350MB Host with Transport Directory Host name of your server

twdf#### Password for user <sid>adm Same password you used for

central instance installation Password for user SAPService<SID>


Kernel CD G:\SETUP\Kernel Message port Same port you used for central

instance installation RDBMS CD G:\SETUP\RDBMS_SAP_DB Database schema SAP DB user new style SAP J2EE Engine CD G:\SETUP\SAP_J2EE_Engine

\J2EE-ENG G:\SETUP\SAP_J2EE_Engine\JLIBS

Maximum memory (MB) 64 SAP J2EE Engine communication user SAPJSF

Client: 000 Password: Same password you used for SAP J2EE Engine installation (on central instance)

Proceed as described on the slides “Start Dialog Instance Installation,” “Instance Installation Type, SID, Instance Number,” “Central Instance and Database Parameters,” “Windows Domain Information and RAM,” “Instance Directory and Transport Host,” “Set Passwords for Operating System User,” “CD Browser and Message Server Port,” “Database Schema and CD Browser,” “Parameter for SAP J2EE Engine,” “Installation Steps,” “Finish Dialog Instance Installation.”


© SAP AG 2003






23

56

Installing SAP GUI4






© SAP AG 2003


Content:Installation SAP License, SAP Online Documentation and SAProuter

Configuring TMS and Basic Configuration

Additional tasks


Perform all necessary post-installation activities


© SAP AG 2003


Restart SAP System and Final Checks

SAP License

SAP Online Documentation

SAProuter

Additional Tasks

TMS and Basic Configuration

Appendix


© SAP AG 2003

Log on to operating system with user <sapsid>adm and start the command or alias startsap.

Check whether database and SAP system are running.

Log on to SAP system with standard user SAP* or DDIC.

Stop SAP system using the command or alias stopsapfrom operating system level.

Start and Stop the SAP System

You can use this procedure to see if you can start and stop the SAP system after the installation. To log on, install an interface such as SAP GUI. There are two standard users, SAP*and DDIC, in the SAP system after the installation: SAP* in client 000, 066 DDIC in client 000


© SAP AG 2003

Check the following operating system files in directory \usr\sap\<SID>\DVEBMGS<no>\WORK\:

dev_ms

dev_disp

dev_w0

dev_rd

Check transactions:SM50 (all available work processes for the instance)

SM51 (all available instances)

SM21 (systemlog)

Checking SAP System Services

Check SAP system services to solve initial problems that might occur when trying to log on or run the system for the first time.


© SAP AG 2003



SAP License


SAProuter

Additional Tasks


Appendix


© SAP AG 2003

SAP License

Install a new permanent license after you do the following:

Perform a new SAP system installation

Rename your SAP system ID

Change the message server host

Change an existing hardware configuration (change of hardware key, database type)

SAP license number must be 18 characters (enlarge with leading zeros)

To work with the SAP system, an SAP license is required. After the installation of the central instance, a temporary license is active for four weeks only. During this period, you must install a permanent license. If the temporary license is expired, only the user SAP* can log on to the SAP system. With this temporary license you cannot create new repository objects or modify SAP repository objects.

You can install several licenses. When you change the installation number, all dependent information (for example, SSCR) is lost.

To request license keys, go to service.sap.com/licensekey. Choose mySAP Business Suite to reach the request page for license keys.

For more information, see also SAP Note 94998.


© SAP AG 2003

Installing SAP Licenses

Use transaction SLICENSE to install a new SAP license

hardware key

11

22

You can use transaction SLICENSE to determine the hardware key on all computers to which an RFC connection is maintained.

In the initial screen of transaction SLICENSE, choose Goto → Determine hardware key. This executes saplicense –get on the computer in question and the result is returned.

You can install a new SAP license in your SAP system using the SLICENSE transaction. After the license is installed, the license key is activated immediately. Then saplicense –install is executed on the computer.


© SAP AG 2003



SAP License


SAProuter

Additional Tasks


Appendix


© SAP AG 2003

Installing the SAP Online Documentation

Online help on the CD-ROM SAP Library is delivered in two file formats:

Standard HTML (PlainHtml, DynamicHelp)

Compiled HTML (HtmlHelp)

For online access from the SAP system, both formats require the following steps:

1. Installing the help files

2. Customizing setup variants for Online Help

3. Installing a Web browser or viewer

There is one CD for each language containing both formats (standard HTML and compiled HTML). With help type PlainHtmlHttp (installation of help files on a Web server), you also need to maintain Web server settings.

For more information about installing the SAP Online Documentation, refer to "Installing the Online Documentation" in the root directory of the SAP Library - Online Documentation CD.


© SAP AG 2003

General Information to Install the Helpfiles

General information for help types HtmlHelpFile, PlainHtmlHttp, PlainHtmlFile:

Use separate directories for different language versions of the documentation

Use two-character language key (EN for English, FR for French, and so on) for directory name

files

When accessing the documentation online, the help processor expects directories that are named with respective two-character language keys (EN for English, FR for French, and so on).


© SAP AG 2003

Install help files from directory Htmlhelp\Helpdata on the SAP Library CD-ROM:

1. Create a directory on your file server.

2. Copy the directory Htmlhelp\Helpdata\<language key> with all its subdirectories from the CD to the documentation directory on the server.

Installation of Help Type HtmHelpFile

Compiled HTML (HTML Help): HtmlHelpFile Compiled HTML provides direct access to files with Microsoft HTML-Help Viewer. Disk space for one language version should be 250 MB for SAP Web Application Server For performance reasons, copy help files to local hard disks or a file server.

About 500 MB of disk space is needed for the German and English language versions.


© SAP AG 2003

Installation of PlainHtmlHttp, PlainHtmlFile (1/2)

Install the help files and the search engine and search index from the directory Plainhtm on the SAP Library CD .

1. Create a directory on the Web server

2. Use the install program on the CD-ROM that matches the operating system of your Web server (directory Plainhtm/Install/<operating system>).

Standard HTML: PlainHtmlHttp, PlainHtmlFile Files cannot be viewed directly from the CD. Files are stored in a packed format on the CD-ROM. Unpack the files on the local hard disk or on a file server.

A Web search engine and index data for full-text search are delivered on the CD-ROM. Documentation directory:

Approximately 600 MB of disk space are required for one language version (Windows NTFS). Storage requirements depend on the particular file system and can amount up to 2 GB (UNIX).

Complete installation for SAP Web AS includes about 200 thousand files in about 100 thousand directories for one language version.

To be able to use the search function, your Web server must run on one of these platforms: IBM AIX, Digital Unix, HP-UX, SUN Solaris, Windows.

The online help cannot be installed on a Microsoft FAT32 file system because it cannot handle the large number of files and directories. If your Web server runs under Microsoft Windows NT or Windows 2000, do not install the SAP Library on the system partition, instead choose another partition.

The install program uses the insthelp program and is available only for Windows and UNIX (with graphical user interface). Under OS/2 and OS/400 you have to use insthelp directly.


© SAP AG 2003

Installation of PlainHtmlHttp, PlainHtmlFile (2/2)


© SAP AG 2003

Setup Variants and Browser for Online Help

Maintaining setup variants for Online Help:IMG activity: Transaction SPRO General Settings

Setup variants for online help (SAP Library)

Installing one of these Web Browsers or Viewers:HTML-Help Viewer with Microsoft Internet Explorer

Microsoft Internet Explorer

Netscape Navigator

For a given front-end platform, a setup variant specifies a help type, the location of the help files (server and/or path), and the language version of the help files.

The language version specified in the currently active setup variant determines which language version of the online help is displayed, regardless of the user’s logon language.

As of Release 4.6C, maintenance of SAP profile parameters for the online help has no effect. The HTML-based online documentation can be displayed with a Web browser on all front-end platforms supported by SAP. Certain requirements and restrictions must be observed, however, depending on the particular platform. For more information, refer to the installation guide, Installing the SAP Library.

For more information about setup variants for Online Help, see course ADM100.


© SAP AG 2003



SAP License


SAProuter

Additional Tasks


Appendix


© SAP AG 2003

SAProuter and SAPNet–R/3 Frontend

You require SAProuter if you are using any of the following:

SAPNet–R/3 Frontend

EarlyWatch

Remote Consulting

Connections from SAP to your SAP system are controlled by SAProuter

SAP Customer

SAPSystemSAProuterSAProuter

SAPSystem

SAProuter increases network security and simplifies network configuration. SAProuter allows you to make indirect network connections. The SAProuter software is included in the standard SAP kernel. No additional installation is required.

SAPNet–R/3 Frontend is the SAP-based service system and provides the technical link between SAP customers and SAP. SAPNet–R/3 Frontend was known as the Online Service System. Connection from SAP to your SAP system are controlled by SAProuter.

SAProuter is started as a demon under UNIX, as a service under Windows.


© SAP AG 2003

Configuring SAProuter and SAPNet–R/3 Frontend

Install SAProuter (see SAP Note 30289).

Configure routing table (see SAP Note 30289).

Start SAProuter (see SAP Note 30289).

Configure connection using transaction OSS1(see SAP Note 17285)

For information about installing SAProuter on the AS400 platform, read SAP Note 86329. For more information about using SAProuter, see course ADM960.


© SAP AG 2003

Configuring SAProuter and SAPNet–R/3 Frontend

Select the suitable SAProuter at SAP


© SAP AG 2003

SAProuter and SAPNet–R/3 Frontend

For more information on setting up and using SAPNet–R/3 Frontend, refer to:

SAP Service Marketplace at http://service.sap.com/sapnet-guide

SAP Library (choose Help → SAP Library in your SAP system or access the SAPLibrary at http://help.sap.com)

For more information on setting up and using SAPNet–R/3 Frontend, refer to the documentation in the following locations: SAP Service Marketplace at http://service.sap.com/sapnet-guide SAP Library (choose Help → SAP Library in your SAP system or access the SAP Library at http://help.sap.com)

For information on installing SAProuter as a Microsoft Windows service, see SAP Note 41054. See also SAP Notes:

Remote connection: SAP Note 14716 Log on to Online Service System: SAP Note 17285 SAProuter: SAP Note 30289 Security aspects for remote access: SAP Note 46902


© SAP AG 2003



SAP License


SAProuter

Additional Tasks


Appendix


© SAP AG 2003

Post-Installation Activities for Transport Organizer

Transaction SE06 provides the following functions for processing after installation:

Generating basic settings of the Change and Transport System

Closing foreign requests and tasks

If you have installed an SAP system as a copy of an existing SAP system, it is necessary to configure the CTS after installation.

If you have installed your SAP system from the SAP CD, you should not configure the CTS after installation. Basic settings for the CTS are generated during the configuration of the transport management system

If you have installed your SAP system as a copy of an existing SAP system, you must configure the CTS after installation.

Select Standard installation, if the SAP system was installed from the SAP CD using SAPinst. It is assumed that the SAP system is running as a correct, delivered version. No adjustments based on corrections or repairs have been made. If you set up an SAP system that originated from a database copy using Standard installation, problems could arise when you upgrade the system or modify objects with the Transport Organizer.

Select Database Copy or Database Migration, if the SAP system was created based on a copy. SAPinst provides utilities for copying and migrating databases.


© SAP AG 2003

TMS Configuration: Transport Domain

On transport domain controller:Log on in client 000, DDIC (not SAP*)Start transaction STMSTransaction STMS in client 000 will:

Assign the SAP system as the transport domain controllerCreate transport domain name DOMAIN_<SID> Create transport group GROUP_<SID> Create communication user TMSADM in client 000Create RFC destinations Set up file DOMAIN.CFG in directory

Check and maintain (if necessary) permissions to directory /usr/sap/trans

For more information, see course ADM325.


© SAP AG 2003

TMS Configuration: Transport Routes

After establishing a transport domain:Create transport routes from the domain controller, using the

default standard configurationsOne-system landscapeTwo-system landscapeThree-system landscape

Start transaction STMS and choose Overview Transport Routes, change mode, Configuration Standard ConfigurationSet the system change options (transaction SE06)

To create transport routes, drag the appropriate SAP systems from the node area and drop them in the display area. To create a transport route between these SAP systems, from the Display Transport Routes screen, choose Configuration → Transport Route → Create Transport Route. Draw a line connecting the two SAP systems between which you want to set up a transport route. In the Create Transport Route dialog box, enter the required information for either the consolidation or delivery route. Choose Save.



© SAP AG 2003

Basic Configuration: Import of Profiles

INSTANCE-PROFIL

START-PROFIL

DEFAULT-PROFIL

during installation generated profiles

SAP systemOperating system

Import

Transaction RZ10

Start import using transaction RZ10:

After installation, the profile parameters are present at file level only. To be able to use the profile administration of the SAP system, the profiles must be imported into the database. During this import, the system performs a consistency check and a check of the way in which the parameters interact. Changes to profile parameters can then be performed in the SAP system. These profile parameters are then stored in the database and written back to file system level. These changes take effect only when they are read by the system (when the system is restarted).

Perform the administration and maintenance of profiles in transaction RZ10. In the first step, you import the profiles into the database by choosing Utilities → Import Profiles → Of active servers. After selecting the profile to edit, you can change individual profile parameters.



© SAP AG 2003

Basic Configuration: Number of Work Processes

Change

transaction RZ10

After the installation, an initial configuration is available

Optimize the number of work processes depending on:

System resources

The number of users working in each SAP system application

Instance Profile

SAPinst installs SAP systems with a minimum number of work processes calculated using the following formula: Number of dialog work process = RAM / 256 (min 2, max 18) Number of update work process = RAM / 768 (min 1, max 6) Number of update2 work process = RAM / 1024 (min 1, max 3) Number of batch work process = RAM / 1024 (min 2, max 3) Number of enqueue work process = 1 Number of spool work process = 1

SAP recommends that you adapt SAP profiles using transaction RZ10. Nevertheless, it is possible to change SAP parameters in the corresponding files on the operating system.


© SAP AG 2003

DAY

NIGHT

background processing

12

9

6

3

11 1

7 58 4

210

BGD

dialogprocessing

Basic Configuration: Set Up Operation Modes

Transaction RZ04:Create operation modes as empty containers Assign all work processes defined in the instance profile to the operation modes as default valuesChange the distribution of work processes in the individual operation modes

Transaction SM63:Maintain the timetable to specify the periods for which the operation modes are valid and when the switch between the operation modes should occur

The operation modes are set up in a number of steps: First, the operation modes are created as empty containers in transaction RZ04. Next, all active instances of the system are recorded and the work processes defined in the instance profile are assigned to the operation modes as default values.

Next distribute the individual operation modes in the total number of work processes taken from the instance profile. The distribution should be made primarily between the dialog and background work processes.

In the timetable (transaction SM63), you specify the periods for which the operation modes are valid and when the switch between the operation modes should occur.



© SAP AG 2003

Basic Configuration: Background Jobs

Schedule background jobs with transaction SM36Standard jobs for all used applications, such as basis

Configure SAP profile parameters for background processing, for example, rdisp/max_wprun_time, rdisp/btc*



© SAP AG 2003

Basic Configuration: User and Roles

Set up user and role administration for the SAP system

Preparatory steps for role maintenance (transaction PFCG)

1. Check parameter auth/no_check_in_some_cases = Y

2. Start transaction SU25 and choose menu entry 1: Initially fill the customer tables

transactionSU25

Create roles: transaction PFCG

Users must be set up and roles assigned to user master records before you can use the SAP system. Roles are collections of activities that allow a user to use one or more business scenarios of an organization. Use profile generator (transaction PFCG) to create and maintain roles.

The profile generator (transaction PFCG) is active in the standard system (the system profile parameter auth/no_check_in_some_cases is set).

Perform the following steps in the Implementation Guide (IMG): Start transaction SU25: • Default values for authorizations are delivered by SAP in tables USOBX and USOBT. Transaction

SU25 is used to fill the customer tables (tables USOBX_C and USOBT_C) of the Profile Generator the first time the Profile Generator is used.

• Copy SAP default settings for check indicators and authorization field values using transaction SU25 (step 1: Initially fill the customer tables).

Schedule background job for time limits: You can set a time limit on the assignment of users to roles. To ensure that these changes are reflected in the user master record, you need to schedule a background job to make the relevant adjustments daily.

For more information about transaction PFCG, see courses ADM100 and CA940.


© SAP AG 2003

Basic Configuration

Additional Tasks:

Set up logon groups with transaction SMLG

Install printers with transaction SPAD

Configure system log with transaction SM21

Set up logon groups: Go to SAP Library → mySAP Technology Components → SAP Web Application Server → CCMS

Configuration → Logon Load Balancing Install printers:

Refer to the SAP Printing Guide in online documentation. Go to SAP Library → mySAP Technology Components → SAP Web Application Server → CCMS →

SAP Printing Guide Configure systemlog: Set up a central systemlog, specify log file pathnames For more information, see course ADM100.


© SAP AG 2003

Installation Check

Installation check:Checks the consistency of the newly installed system:

Completeness of installation

Version compatibility (between SAP release and operating system)

Accessibility of the message server

Availability of all work process types

Information about enqueue server and update service

Choose Tools Administration Administration Installation

check or transaction SICK

The consistency check is used to determine inconsistencies in your system. This function is also called automatically whenever you start your system or start an application server.

The installation check checks whether the following are true: The release number in the SAP kernel matches the release number stored in the database system. The character set specified in the SAP kernel matches the character set specified in the database system.

The critical structure definitions that are defined in both the data dictionary and the SAP kernel are identical. The structures that are checked include structures SYST, T100, TSTC, TDCT, TFDIR, and others.


© SAP AG 2003

Activation of SAP R/3 Enterprise Extension Set

Activation of extension set:1. Call transaction SPRO (IMG)

2. Choose SAP Reference IMG

From a technical point of view, the SAP R/3 Enterprise Extensions are delivered and installed as part of an Add-on for the SAP R/3 Enterprise Core, that is, the SAP R/3 Enterprise Extension Set. Client-independent activation switches allow you to use the functions contained in the SAP R/3 Enterprise Extension Set components.

The functions are activated by selecting the relevant activation switch in the IMG activity, "Activation switch for the SAP R/3 Enterprise Extension Set." After the activation, the Business Transaction Events (BTEs) and the BAdI implementations marked as SAP-internal and already activated in a static way are also executed at runtime. After the activation, additional entries are displayed in the tree structures of the IMG, of the Application Component Hierarchy (AKH), and of the SAP Enterprise menu, depending on the component activated.

Generally, you cannot deactivate an activated switch because data is updated in a different way than it would be if the relevant component was not active (depending on the component and the actions performed in the system after the activation). However, in a test system without production data, you can deactivate the switch without problems.

Refer to SAP Note 532499 for information on activating various components simultaneously. An error message is issued when you activate one or more switches for parts of the SAP R/3 Enterprise Extension Set. Before you activate parts of SAP R/3 Enterprise, make sure that no clients are marked as being "productive" in the system: Check table T000 to see whether an entry exists with CCCATEGORY = 'P'. Change the setting to 'T' and then activate the switches. Afterward, reset the setting in table T000.


© SAP AG 2003

Installation of Additional Languages (1/3)

Perform the following steps:1. Classification of the language

2. Scheduling of the language transport

3. Scheduling of the language supplementation

1. Classification of the languagetransaction SMLT:

Follow this procedure to classify a language: Click Classify Language or choose Language → Classify. On the next dialog box, choose the language you want to import and the corresponding

supplementation language. The imported languages must be defined in the default profiles so you can log on in these languages.

The relevant parameter is zcsa/installed_languages. SAP recommends that you use the language supplementation program, which (as of SAP Web

Application Server 6.20) integrates the program RSREFILL and the client maintenance function. See course ADM102 for more information about updating a translation language for the customizing

settings of an existing customer client (other than client 000).


© SAP AG 2003


2. Scheduling of the language transport

transaction SMLT

11 22

33

44

The languages English and German are completely available in all newly installed systems. You do not need to import them into newly installed systems.

Follow this procedure to import language packages: Select the language for which you want to install extra packages and choose Language → Import

package. Enter the path for the language packages. Choose Find package(s) to search for any available

packages in the path you have entered. The green, yellow and red lights next to the packages indicate whether you can import them:

• green light: all import conditions are met • yellow light: there are warnings • red light: package cannot be imported because checks have detected errors Select one or more language packages with green or yellow lights for import. Specify a start time and

(optional) target server and choose Execute to import the language packages. This action schedules a background job that performs the import.

Check the log files. If an action terminates for technical reasons, you can restart it.


© SAP AG 2003


3. Scheduling of the language supplementation

1122

33

44

transaction SMLT

Use the language supplementation function to fill in the gaps in a language that have not been translated completely. Supplementation actions are client-specific. The languages are supplemented in the client in which you are logged on.

Follow this procedure to schedule language supplementation: Choose Language → Supplement Language. Enter conditions that control which tables are selected for supplementation. These fields are set with

SAP default values that depend on the logon client. Client-specific customizing tables are subject to special handling during language imports. This has resulted in the following supplementation strategies being created:

• Combined with RSREFILL (standard setting when logging on to clients other than 000) • Combined with Client Maintenance • Supplement Only

Enter a start time and choose Execute. This action schedules a background job that performs the supplementation.

Monitor the supplementation and check log files. For more information on these strategies, choose Information on Table Selection in the system.


© SAP AG 2003

Language Import: New Features

New features:SAP Web Application Server 6.20:

Client maintenance function (RSREFILL program) is integrated into the language supplementation program.

Basis Release 4.6D:Transport processes (import and export) can be started in parallel.

Basis Release 4.6C Languages are now transported with the SAP transport programs R3trans and tp.

For more information, see course ADM102 or go to service.sap.com/instguides and choose SAP Web AS 6.20 → SAP Web AS 6.20: Language Transport.


© SAP AG 2003

Implementation of Packages

Import support packages

Implement latest versions of SAP executables (kernel)

Implement patches for the SAP J2EE Engine

Implement patches for the SAP GUI

Implement patches for the database

For more information about package implementation, refer to unit 6, "Implementing Patches."


© SAP AG 2003

Client Copy

SAP strongly recommends:To create your first client, use the profile SAP_CUST to copy client 000. Consistency of the application data in the SAP delivery client is not guaranteed.

Use client copy to create new clients for productive usage from the reference client 000

Client copy steps:Maintain the client (transaction SCC4)

Copy the client (transaction SCCL)

Copy the log files (transaction SCC3)

After the installation client 000 and 066 are available. Client 066 is used only for remote support from SAP.

If you perform a client copy, you should also change the SAP system client of user SAPJSF after the client copy. Starting with SAP J2EE Engine 6.20 patch level 8, integration of ABAP and Java security services in SAP J2EE Engine were enhanced by introducing the new SAP Integration Manager into the SAP J2EE Engine's security service, which supersedes the previously used R/3 Properties Manager.

As a result, the information required for changing the SAP communication user SAPJSF in the "Configuring the Connection of the SAP Web AS to the SAP J2EE Engine" section of the SAP Library is no longer valid. Instead, if you want to change the SAP system client of the communication user SAPJSF, adapt the connection parameters for every SAPJ2EE Engine instance of your SAP system (that is, for the SAP J2EE Engine of every SAP central instance and every SAP dialog instance)

For more information concerning client copies, see course ADM325.


© SAP AG 2003

Client Copy with SAP R/3 Enterprise

Customizingdata

Customizing andapplication data

> 17000 Tables> 17000 Tables> 1.5 > 1.5 –– 2 GB2 GB

> 25000 Tables> 25000 Tables>> 5 GB>> 5 GB

Customizing clientin SAP R/3 Enterprise

Production clientin SAP R/3 Enterprise

Target client


© SAP AG 2003

Perform a Full Backup: Windows

WindowsPrerequisites

Stop SAP system, database, SAP-related services (SAP<SAPSID>_<instance> and SAPOSCol)

Procedure:Save the registry

Save the system state data

Back up all SAP-specific and all database-related directories:

\usr\sap

\usr\sap\trans

<HOMEDIR> of <sapsid>adm

\WINNT

Save the Registry: Choose Start → Programs → Accessories → System → Tools → Backup → Emergency Repair

Disk. Select Also Backup the Registry to the Repair directory… When you confirm your entry, the

Registry is written to disk. Save the System State Data:

Choose Start → Programs → Accessories → System → Tools → Backup → Backup Wizard. Select Only backup the System State Data and specify the Backup media type and the destination of

the backup. Back up all SAP-specific and all database-related directories:

Choose Start → Programs → Accessories → System → Tools → Backup → Backup Wizard. Select Backup selected files, drives or network data. Select the Windows directory and all SAP and database-related directories, including: \USR\SAP;

\USR\SAP\TRANS; <HOMEDIR> of <sapsid>adm; \WINNT - On the Where to Store the Backup screen, specify the media type and destination for the backup.


© SAP AG 2003

Perform a Full Backup: UNIX

UNIXPrerequisites

Stop SAP system and database

Procedure Log on as user root. Manually create a compressed tar archive containing all installed files

1. Create the archive:tar -cf <ARCHIVNAME> <filesystem / filename> -uf<ARCHIVNAME> <filesystem / filename> ....

2. Compress the archive:compress <ARCHIVNAME>

3. Store the archive on tape:tar -cf <tape_device> <ARCHIVNAME>.Z

You need to back up the following directories and files: All database-specific directories All SAP-specific directories: - /usr/sap/<SAPSID> - /usr/sap/trans - <sapmnt>/<SAPSID> - home directory of the user <sapsid>adm - root file system

This saves the structure of the system and all configuration files (for example, file system size, logical volume manager configuration, database configuration data).

This procedure works on all hardware platforms. See your system administration guide for details and for operating system-specific backup procedures.


© SAP AG 2003

Checking the RFC Destination

In distributed installation (central and database instance run on different hosts), check whether the database host was correctly set up as an RFC destination to get monitoring data for the database and operating system.

Procedure:Choose Tools → Administration → Network → RFC destinations or transaction SM59

Go to TCP/IP connections and select SAPOSCOL_<DB_hostname>

(if database and central instance are located on different hosts)

Choose Test Connection


© SAP AG 2003

SAP J2EE Engine

After the installation, the SAP J2EE Engine is activated.

Choose:Transaction SMICM

Goto

Http application server

Display data

Deactivate SAP J2EE Engine: Set parameter rdisp/j2ee_start to 0 in the instance profile of every installed SAP instance.

After the installation, make sure that user SAPJSF exists, is not locked, and its password is set correctly to the one you entered during the installation by calling transaction SU01.

To change the SAP Communication, use SAPJSF (a new tool). Starting with SAP J2EE Engine 6.20 patch level 8, integration of ABAP and Java security services in

SAP J2EE Engine was enhanced by introducing the new SAP Integration Manager into the SAP J2EE Engine's security service, which supersedes the previously used R/3 Properties Manager.

As a result, the information required for changing the SAP communication user SAPJSF in the "Configuring the Connection of the SAP Web AS to the SAP J2EE Engine" section of the SAP Library is no longer valid. Instead, if you want to change the SAP system client of the communication user SAPJSF, adapt the connection parameters for every SAP J2EE Engine instance according to the "Configuring the Connection of the SAP Web AS to the SAP J2EE Engine" section in the documentation, Security Integration SAP Web AS and SAP J2EE Engine. This documentation is available in SAP Service Marketplace at http://service.sap.com/security. Choose Security in Detail → Hot Topic: J2EE. For more information, see SAP Note 569560.


© SAP AG 2003

SAP J2EE Engine: User SAPJSF

Make sure that user SAPJSF was created correctly and is not locked. Use transaction SU01 (User Maintenance).

If the user does not exist:1. Start transaction SE37 and enter the function module

PRGN_J2EE_CREATE_SERVICE_USER.

2. Choose Single Test

3. Specify the import parameter IF_PASSWORD and choose Execute.


© SAP AG 2003

Additional Information for SAP J2EE Engine and SDMFile System Structure:

/usr/sap/<SAPSID>/<Instance Name>/j2ee

/usr/sap/<SAPSID>/<Instance Name>/sdm

SDM is installed only on the central instance.

Ports used by the SAP J2EE Engine:The ports used by the SAP J2EE Engine are listed in the file prepconf.log. This is located in the installation directory of the SAP J2EE Engine.

Administration of the SAP J2EE Engine:Administration of SAP J2EE Engine is done from within the SAP system using transaction SMICM.


© SAP AG 2003

SAP Load Generator (SGEN)

1. Select Generate All Objects of SelectedSoftware Components

2. Choose components to generate

Use transaction SGEN to generate ABAP loads of programs, function groups, classes, and so on.

You can use transaction SGEN to generate the ABAP loads of a number of programs, function groups, classes, and so on, and Business Server Page applications (BSP applications).

Before the generation is started, consecutive screens give you options regarding: Task of the generation Selection of generation set (= number of objects to be generated) Use parallel generation

The generation is started on the job monitor screen. In addition, this screen gives you information about current generation jobs or jobs that may have already run (predictions regarding the duration of the generation, for example).

If you want to generate loads, make sure that there is enough space available in the database. The space required can be several hundred MB. Generation over all components requires more than 2 GB of free space.


© SAP AG 2003

UNICODE Post-Installation Procedure

After installing Unicode, follow these steps:

1. Log on to your SAP system.

2. Start transaction SE38.

3. Execute the UMG_POOL_TABLE program.



© SAP AG 2003

Windows: SAP Accounts

Check that created SAP accounts never expireIn user management, the Password never expiresoption should be set for the created SAP accounts <sapsid>adm and SAPService<SID>.

If this option is not selected, the installed system will not start anymore after 42 days have passed since the installation.

After the installation, make sure that the created SAP accounts <sapsid>adm and SAPService<SID> have the Password never expires option selected in the user management. If this option is not selected, the installed system will not start anymore after 42 days have passed since the installation. In this case, after trying to access the system, the SAP management console reports the error, "The service did not start due to a logon failure." To fix the problem, you must set the Password never expires option for the SAP accounts.

Log on to operating system. Choose Start → Programs → Administrative Tools → Computer Management.


© SAP AG 2003

Installing Administration Tools for a Database

SAPDB Administration tools on Windows systems:

You can use Database Manager GUI (DBMGUI) to administer databases, including remote ones.Install DBMGUI:

<CD drive>:\NT\SETUPS\DBM74.EXE

You can use SQL Studio to send SQL statements to the database and evaluate the results. Install SQL Studio:

<CD drive>:\NT\SETUPS\SQLSTD74.EXE

You can install the SAPDB administration tools, DBMGUI and SQL Studio, on any Windows computer in your network, even if your database runs on UNIX. From the computer with the installed administration tool, you can then administer the database or send queries to it.

Your computer must meet the following minimum operating system requirements: Windows NT 4.0 SP4 or Windows 2000 Pentium II, 64 MB RAM, 100 MB of free disk space

If you are prompted to restart the computer after the installation, be sure to bring down all databases that are running as follows: dbmcli –d <SID> -u <controluser>,<password> db_offline

If SAP DB or liveCache is installed on the computer, you must not install the administration tools in the same directory. You can check the directories used by SAP DB or liveCache as follows: dbmcli –d <SID> -u <controluser>,<password> dbm_getpath IndepDataPath dbmcli –d <SID> -u <controluser>,<password> dbm_getpath IndepProgPath


© SAP AG 2003

Make sure the database utilities brbackup and brarchive were installed correctly

Install Legato Storage Manager for Oracle 9.2.x

Completing and Checking Oracle Installation

Database backupDatabase backupBRBACKUP

BRARCHIVEOffline redo logfile backup

Execute the following steps in order to check whether the database utilities brbackup and brarchive are installed correctly: Log on as UNIX user ora<dbsid> . Verify that the database is running. Load a new tape in the tape station. Initialize all tapes defined by the profile parameters volume_backup and volume_archive in the

init<SAPSID>.sap file with this statement: brbackup -i force brarchive -i force Use SAPDBA to start a online backup for one tablespace. Use SAPDBA to start an archive backup.

Install the SAP Backup Library or the Legato Storage Manager if you are using Oracle 9.2.x. For more information on how to install and use the SAP backup library and the Legato Storage Manager, see SAP Note 142635.


© SAP AG 2003

Informix Administrative Tools

Only members of the Informix-Admin group can access administrative tools for Informix database

Therefore, you have to adapt the user environment to use Informix database tools as a user other than <sapsid>adm

Before you use SAPDBA for the first time as user informix, you must perform this procedure.

1. Log on as <new_user>

2. Go to <DRIVE>:\USR\SAP\<SAPSID>\SYS\EXE\RUN and start NTREG2ENV.EXE

3. In window ntreg2env, check the selected system and choose OK


© SAP AG 2003

UNIX: Performing File and Directory Adjustments

UNIX

For security reasons, set the permissions of the transport directory /usr/sap/trans to 771:

Log on as user root on the host that exports the transport directory.

Enter chmod 771 /usr/sap/trans

For security reasons, you have to set the permissions of the transport directory /usr/sap/trans to 771. To do this, follow these steps: Log on as user root on the host that exports the transport directory. Enter chmod 771 /usr/sap/trans.


© SAP AG 2003

UNIX: Performing Operating System Adjustments

UNIX:These adjustments are required if your operating system is AIX or HP-UX on HP/HPPA.

AIXCheck that perfagent is installed as follows: lslpp -l perfagent.server

The AIX software perfagent must be installed for saposcol on AIX.

HP-UX on HP/HPPA or AIX on IBM/RS6000 (32 bit)Improve performance by reducing the number of shared memories. To do this, group shared memories together as shared memory pools. (SAP Note 37537)


Post-Installation Activities Exercises

Unit 6: Post-Installation Activities


• Perform the necessary post installation activities

After installing the system you will perform some important post-installation steps, such as adapt SAP profiles, install SAP license, and perform CTO and TMS activities.

6-1 Restart SAP system and final checks.

6-1-1 Stop and restart SAP system using the Microsoft Management Console. To do this, log on to the server for your training system using the Terminal Server Client or pcAnywhere.

6-1-2 Check the developer traces on operating system. Then log on to SAP system and perform in SAP system transaction SM50, SM51 and SM21 to check work processes and the systemlog for errors.

6-2 Check the installed license.

6-2-1 Check whether a temporary license is installed.

6-2-2 Request the hardware key.

6-3 Optional: Install, start and configure SAProuter for SAPNet–R/3 Frontend access.

SAP note 30289 is stored on your server used for the course, for example, twdf####, in directory G:\SETUP\Adm110\SAP_Notes.

6-3-1 Install SAProuter and create permission file saprouttab.

6-3-2 Proceed as described in SAP note 30289 unit 3.2 (Installation under Windows) step 1 and 2. Use the executables saprouter.exe and niping.exe from directory G:\usr\sap\<SID>\SYS\exe\run.

6-3-3 Create route permission table saprouttab.

Create file saprouttab in directory G:\usr\sap\saprouter and add the entry: “P * * * “


6-3-4 Start SAProuter

Proceed as described in SAP note 30289 step 4.1 (Starting SAProuter).

6-3-5 Implement SAProuter as service.

Stop saprouter with the command saprouter –s.

Proceed as described in SAP note 30289 unit 3.2 (Installation under windows) step 4 and 5.

6-3-6 Check the technical settings in transaction OSS1.

6-4 Optional: Perform the post-installation activities, “Change and Transport Organizer” (CTO) and “Transport Management System” (TMS).

6-4-1 Perform post installation action in transaction SE06.

6-4-2 Configure TMS.

6-5 Optional: Import and change the SAP profiles.

6-5-1 Import all profiles into your SAP system.

6-5-2 Change the values of the parameters concerning number of work processes (rdisp/wp_no_*), for example, enter twice the number for dialog and batch work processes.

6-6 Optional: Configure operation modes.

6-6-1 Set up operation modes.

6-6-2 Maintain timetable for operation mode.

6-7 Optional: Check standard background jobs

6-7-1 Schedule the standard background jobs.

6-8 Preparation steps before using profile generator (transaction PFCG).

6-8-1 Check profile parameter auth/no_check_in_some_cases.

6-8-2 Initialize profile generator.

6-9 Installation check and activation of SAP R/3 Enterprise extension set

6-9-1 Perform the installation check

6-9-2 Activate the SAP R/3 Enterprise extension set.

6-10 Optional: Perform a client copy

6-10-1 Create a new client in your SAP system.

6-10-2 Log on in your system to your new client and start a local client copy with Profile SAP_CUST in background (start time: tomorrow 8 a.m.).


6-11 Check status of SAP J2EE Engine and of user SAPJSF.

6-11-1 Check the profile parameter rdisp/j2ee_start.

6-11-2 Check current state of SAP J2EE Engine using transaction SMICM.

6-11-3 Check whether user SAPJSF is locked.

6-12 SAP Load Generator

6-12-1 Start the SAP Load Generator and schedule the load generator for tomorrow 8 p.m.

6-13 Optional: Check the SAP account on windows.

6-13-1 Check whether the user option Password never expires is set for the SAP accounts <sid>adm and SAPService<SID>.


Solutions

Unit 6: Post-Installation Activities


• Perform the necessary post installation activities

After installing the system you will perform some important post-installation steps, such as adapt SAP profiles, install SAP license, and perform CTO and TMS activities.

6-1 Restart SAP system and final checks.

6-1-1 Stop and restart SAP system using the Microsoft Management Console. To do this, log on to the server for your training system using the Terminal Server Client or pcAnywhere.

Start the Terminal Server Client or pcAnywhere and enter the physical host name. Log on to the operating system as user <sid>adm.

Start the Microsoft Management Console by double-clicking the appropriate icon. Select the desired instance(s), right-click and choose the Stop function from the context menu. Depending on whether you have chosen an individual instance or the SAP system, either an individual instance or the entire SAP system is stopped.

Choose the node for the central instance in the Microsoft Management Console tree. Select the desired instance(s), right-click and choose Start. Start the dialog instance in the same way.


6-1-2 Check the developer traces on operating system. Then log on to SAP system and perform in SAP system transaction SM50, SM51 and SM21 to check work processes and the systemlog for errors.

On operating system, open the files dev_ms, dev_disp, dev_rd, dev_w# (#= 0, 1), which are located in the instance directory (G:\usr\sap\<SID>\D*\work), using the windows explorer. Check the files due to errors.

Log on to your SAP system. The SAP server (Tools → Administration → Monitor → System Monitoring → Servers or transaction SM51) displays the active SAP instances. The process overview (Tools → Administration → Monitor → System Monitoring → Process Overview or transaction SM50) displays a list of work processes of the instance to which you are logged on. Check system log to find errors (Tools → Administration → Monitor → System log or transaction SM21).

6-2 Check the installed license.

6-2-1 Check whether a temporary license is installed.

Start transaction SLICENSE (Tools → Administration → Administration → SAP Licenses) and have a look at the table “Installed Licenses” to see the installed temporary license for your <SID>.

6-2-2 Request the hardware key.

Start transaction SLICENSE (Tools → Administration → Administration → SAP Licenses) and choose Goto → Determine Hardware Key. Select your server, choose Determn and choose Continue (green arrow).

6-3 Optional: Install, start and configure SAProuter for SAPNet–R/3 Frontend access.

SAP note 30289 is stored on your server for the training, for example, twdf####, in directory G:\SETUP\Adm110\SAP_Notes.

6-3-1 Install SAProuter.

Proceed as described in SAP note 30289 unit 3.2 (Installation under Windows) step 1 and 2. Use the executables saprouter.exe and niping.exe from directory G:\usr\sap\<SID>\SYS\exe\run. Read the SAP note and follow its instructions in unit 3.2 (Installation under Windows) step 1 and 2.

6-3-2 Create route permission table saprouttab

Create file saprouttab in directory G:\usr\sap\saprouter and add the entry:

“P * * * “

Create a file with the name saprouttab in directory G:\usr\sap\saprouter. Open the file and add the content P * * *.

6-3-3 Start SAProuter

Proceed as described in SAP note 30289 step 4.1. (Starting SAProuter)

Read the SAP note and follow its instructions in unit 4.1 (Starting SAProuter).


6-3-4 Implement SAProuter as service.

Stop saprouter with the command saprouter –s.

Proceed as described in SAP note 30289 unit 3.2 (Installation under windows) step 4 and 5.

Read the SAP note and follow its instructions in unit 3.2 (Installation under Windows) step 4 and 5.

6-3-5 Check the technical settings in transaction OSS1.

Proceed as described in this training material on the page “Configuring SAProuter and SAPNet–R/3 Frontend.”

6-4 Optional: Perform the post-installation activities, “Change and Transport Organizer” (CTO) and “Transport Management System” (TMS).

6-4-1 Perform post installation action in transaction SE06.

Proceed as described in this training material on the page “Post-Installation Activities for Transport Organizer” with the setting Standard Installation. Do not select Database Copy ….

6-4-2 Configure TMS.

Proceed as described in this training material on the pages “TMS Configuration: Transport Domain” and “TMS Configuration: Transport Routes.”

6-5 Optional: Import and change the SAP profiles.

6-5-1 Import all profiles into your SAP system.

Call profile maintenance (Tools → CCMS → Configuration → Profile Maintenance or transaction RZ10). All profile files can be imported together by choosing Utilities → Import Profiles → Of active servers. A check log displays the result of the import.

6-5-2 Change the values of the parameters concerning number of work processes (rdisp/wp_no_*), for example, enter twice the number for dialog and batch work processes.

To change the values of individual parameters, select the instance profile and change this in extended maintenance.

6-6 Optional: Configure operation modes.

6-6-1 Set up operation modes.

Create operation modes in transaction RZ04 (Tools → CCMS → Configuration → Operation Modes/Instances). Choose Create and enter the name. Choose Save. Switch to the Instances/Operation Modes view by choosing Instances/Operation Modes. You define work process distribution for all instances of your system by choosing Settings → Based on current status → New instances→ Create. To change the distribution of the work processes for


the operation modes of the instances, double-click the operation modes entries. You change and then save the distribution of the work processes in the Maintain Work Process Distribution window by choosing + and -. After you have changed the distribution for all operation modes and instances, choose Save.

6-6-2 Maintain timetable for operation mode.

Schedule operation modes using the operation mode calendar (Tools → CCMS → Configuration → Operation Mode Calendar, Transaction SM63). Choose Normal Operation and then Change. Select the start and end of the period for operation mode by double-clicking the appropriate lines. Choose Assign and then select operation mode. After you have assigned the entire 24-hour period to your operation modes, choose Save.

6-7 Optional: Check standard background jobs

6-7-1 Schedule the standard background jobs.

Choose transaction SM36 (Tools → CCMS → Jobs → Definition) and choose Goto → Standard jobs. To schedule the standard jobs, choose Reorg. Jobs → Default scheduling.

6-8 Preparation steps before using profile generator (transaction PFCG).

6-8-1 Check profile parameter auth/no_check_in_some_cases.

Use transaction RSPFPAR to check the value of the parameter. It must be set to Y. Change the value if necessary using transaction RZ10 (see exercise 5)

6-8-2 Initialize profile generator.

Proceed as described in this training material on the pages “Basic Configuration: User and Roles.”

6-9 Installation check and activation of SAP R/3 Enterprise extension set

6-9-1 Perform the installation check.

Proceed as described in this training material on the pages “Installation Check.”

6-9-2 Activate the SAP R/3 Enterprise extension set.

Proceed as described in this training material on page “Activation of SAP R/3 Enterprise Extension Set.”

6-10 Optional: Perform a client copy

6-10-1 Create a new client in your SAP system.

Create a new client named 100. Choose Tools → Administration → Administration → Client Administration → Client Maintenance or start transaction SCC4. Switch to change mode. Choose New Entries. Enter 100 in the Client field. Enter a client description and enter a city. Adapt the change options for customizing.


6-10-2 Log on in your system to your new client and start a local client copy with Profile SAP_CUST in background (start time: tomorrow 8 a.m.).

Log on to your new client with user SAP* and password pass. Choose Tools → Administration → Administration → Client Administration → Client Copy → Local Copy. Select as source client 000. Choose Schedule as Background Job (start time: tomorrow 8 a.m.).

6-11 Check status of SAP J2EE Engine and of user SAPJSF.

6-11-1 Check the profile parameter rdisp/j2ee_start.

Use transaction RSPFPAR to check the value of the parameter. The default setting is 1, so SAP J2EE Engine will be started within the normal SAP system start procedure. Change the value if necessary using transaction RZ10 (see exercise 1-5).

6-11-2 Check current state of SAP J2EE Engine using transaction SMICM.

Proceed as described in this training material on page “SAP J2EE Engine.”

6-11-3 Check whether user SAPJSF is locked.

Choose transaction SU01 (Tools → Administration → User maintenance → Users) and enter user SAP JSF. Choose User names → Lock to check whether the user SAPJSF is locked.

6-12 SAP Load Generator

6-12-1 Start the SAP Load Generator and schedule the load generator for tomorrow 8 p.m.

Proceed as described in this training material on page “SAP Load Generator (SGEN).”


6-13 Optional: Check the SAP account on windows.

6-13-1 Check whether the user option Password never expires is set for the SAP accounts <sid>adm and SAPService<SID>.

Log on to operating system and choose Start → Programs → Administrative Tools → Computer Management. Proceed as described in this training material on page “Windows: SAP Accounts.”


© SAP AG 2003


Content:Applying kernel patches

Applying SAP J2EE Engine Patches

Applying Support Packages

Applying database patches

Objectives:At the conclusion of this, unit you will be able to:

List the elements of the SAP system that need patches

Apply patches to the SAP system


© SAP AG 2003

Applying a Kernel Patch (incl. DB-Dependent Part)


1. Download the latest kernel patch from http://service.sap.com/patches to your server

2. Follow SAP Note 194663. Follow the screenshots given here

Kernel: Before statusDB patch 35

Supportpackages status

These screenshots show the content of System → Status of an SAP R/3 Enterprise system SR1 that has been installed and in which the SAP DB has already been patched from patch level 28 (after installation) to patch level 35. Note the kernel patch level (623) and the Support Package level for the BASIS Support Packages and ABA Support Packages (17 for both).

For updating the kernel, follow the instructions given in SAP Note 19466 carefully.


© SAP AG 2003

Applying a Kernel Patch, Screenshots (1/2)


1. Decompress the kernel patch files to some temporary folder2. Follow SAP Note 19466

(stopping the system, services, SAPOsCol...)3. Save the old kernel, replace parts of the old kernel with the new files

In the screenshots, you see that you will replace kernel files in the following directories: \usr\sap\<SID>\SYS\exe\run \usr\sap\<SID>\<Instance>\j2ee\os_libs \usr\sap\<SID>\<Instance>\j2ee\cluster\server\additional-lib (shown on the next slide)

For information about the use of an SAP Web AS 6.20 kernel for SAP Web AS 6.10-based systems, read the SAP Note 502999 carefully.

You should apply the kernel patches to all instance-specific exe directories.


© SAP AG 2003

Applying a Kernel Patch, Screenshots (2/2)

After status

In the \usr\sap\<SID>\<Instance>\j2ee\cluster\server\additional-lib directory, you can find such files as sapjco.jar, the communication program between SAP J2EE Engine and ABAP kernel. This directory contains some files that need to be updated during a kernel patch.

The kernel patch (in the example above) brought the kernel up to patch level 783, as can be seen in System → Status.


© SAP AG 2003

Patching the SAP J2EE Engine (1/2)


1. Download the latest SAP J2EE Engine patch from http://service.sap.com/patches to your server

2. Follow SAP Note 5290883. Follow the screenshots given here

Before status

The SAP J2EE Engine also needs to be updated to ensure a stable environment. It is best to apply these patches when updating the kernel. After downloading and decompressing the patch file, follow the instructions in SAP Note 529088.


© SAP AG 2003

Patching the SAP J2EE Engine (2/2)

After status

Always choose Upgrade!Choose correct folder

Start visual.bat

Follow the instructions in SAP Note 529088. Select the correct folder for the update of the SAP J2EE Engine. When applying a patch to an existing SAP J2EE Engine always select Upgrade; otherwise, you would lose applications already deployed!

You should upgrade all instance-specific SAP J2EE Engine directories in this manner.


© SAP AG 2003

Apply Support Packages using Transaction SPAM

Read SAP Note 447925Note that TMS needs to be configured

The use of transaction SPAM is explained in great detail in the course ADM100 – SAP Web AS Administration I. This screenshots reminds you how Support Packages are applied.

In the example in the screenshots, only the BASIS and ABA Support Packages are applied to the SAP R/3 Enterprise system. There are several other Support Package types.


© SAP AG 2003

Applying a Database Patch


Download the latest database patchhttp://service.sap.com/patches to your server.Follow SAP Note 530567 for installing Patches for SAP DB.Follow SAP Note 544304 for installing FixPaks for DB2 UDB, for DB2 on iSeries/zSeries see notes.Follow SAP Note 45876 for installing Patches for Informix.Follow SAP Note 159268 for installing Service Packs for Microsoft SQL Server.Follow SAP Note 306408 for installing Interims Patches for Oracle using OPatch.

Because different database releases might have different patch strategies, please check http://service.sap.com/instguides and go to Database Upgrades

There are different procedures for applying patches for the different databases supported by SAP systems. When applying patches, you will notice that even databases from the same vendor can differ significantly between releases. Therefore, make sure that you are using the patch description that fits your database release. Also check the SAP Notes noted in the figure before applying a database patch. The content of these notes might have been revised.

For DB2 on iSeries, refer to http://www.4soi.de/Infoapar.htm. For DB2 on zSeries, follow the instructions on how to fix the operating system. SAP Note 81737 lists the operating system fixes that should be applied in an SAP environment.


© SAP AG 2003

Appendix: Installation of dbmgui for SAP DB (1/2)


1. Download latest dbmgui version fromhttp://service.sap.com/patches to your server

2. Execute DBM7403_10-10001730.EXE (example given)3. Follow the screenshots given here

On the SAP Service Marketplace, you will find patches for dbmgui. These patches contain actually updated, full installs.


© SAP AG 2003

Appendix: Installation of dbmgui for SAP DB (2/2)

The installation procedure is straight-forward. Simply choose an installation directory and proceed as the installation procedure proposes.


© SAP AG 2003

Appendix: Configuring dbmgui

Perform these steps to configure dbmgui:

1. Double-click:

2. Register the database as shown in the screenshot:

After successful installation, you can start dbmgui by double-clicking the icon just created by the setup procedure.

To administer databases using dbmgui, you must first register the databases to be controlled. For registration you may also choose remote servers where SAP DB engines reside. For most purposes, you will work with the <Local> setting (refer to the screenshot).

Click in the box next to the database name and choose Register. You are asked to provide the control user for the SAP DB named control and the correct password for this user. By default this password is control.

SAP Note 25591 describes how you can change the password for user control and sapr3 and SUPERDBA.


© SAP AG 2003

Appendix: Stopping the Database using dbmgui


3. After stopping the SAP system, you can shut down the database:

4. Start the SAP system. The database will be started automatically.

After registering the database, you can stop it by right-clicking the database icon in dbmgui and then choosing Set Offline. The database should switch into offline mode fairly soon unless some special activities (backup, restore, recovery and so on) are running on the database. Select the shutdown option Quick only under special circumstances. For more information on SAP DB, take the course ADM515 – Database Administration SAP DB.


© SAP AG 2003

Appendix: Applying a Database Patch for SAP DB


1. Download the latest database patchhttp://service.sap.com/patches to your server.

2. Follow SAP Note 530567 for SAP DB (before executing step 3).It may be necessary to adapt the environment variable PATH and reboot the server.

3. Follow the steps in the screenshots.

dialog free updateusing the syntax:"SDBUPD –d <SID>-u control,control"

Result:

After downloading and decompressing the database patch (using sapcar –xvf <filename>), follow the instructions in SAP Note 530567.

It might be necessary to add a new entry to the system environment variable Path and reboot the server. Using the dialog free patch syntax for the SDBUPD program, you should get the result message shown in the screenshot really fast.


© SAP AG 2003

Further Information

SAP Service Marketplace, http://service.sap.com/patches

SAP Notes as listed in this unit


© SAP AG 2003

Implementing Patches: Unit Summary

List the elements of the SAP system that need patches

Apply patches to the SAP system



Implementing Patches Exercises

Unit 7: Implementing Patches


• Apply a kernel patch

• Apply an SAP J2EE Engine patch

After installing the system, you will patch some of its components to the latest version available.

7-1 Apply a kernel patch to your newly installed SAP system.

7-1-1 Check the current kernel patch level of your SAP system.


G:\SETUP\ADM110\Kernel_Patch

Proceed as described in SAP Note 19466. You find this SAP Note as a document in folder G:\SETUP\ADM110\SAP_Notes.

Note: You can skip steps 1 and 2 of the procedure described under "Copying and installing a patch."

7-1-3 Check the new kernel patch level of your SAP system.

7-2 Optional: Apply a patch to the SAP J2EE Engine of your SAP system.

7-2-1 Check the current patch level of the SAP J2EE Engine.


G:\SETUP\ADM110\ SAP_J2EE_Engine_Patch.


You can start immediately with the step "Installing the patch."

7-2-3 Check the new patch level of the SAP J2EE Engine.


Implementing Patches Solutions

Unit 7: Implementing Patches


• Apply a kernel patch

• Apply an SAP J2EE Engine patch

After installing the system, you will patch some of its components to the latest version available.

7-1 Apply a kernel patch to your newly installed SAP system.

7-1-1 Check the current kernel patch level of your SAP system.

Use System → Status and choose Other kernel info → Sup.Pkg lvl to find the information.

Alternatively, you can start transaction SM51, select one instance and choose Release notes. You find the kernel patch level under Kernel patch number.


G:\SETUP\ADM110\Kernel_Patch


Note: You can skip steps 1 and 2 of the procedure described under "Copying and installing a patch."

Again, follow the instructions given in the SAP Note.

7-1-3 Check the new kernel patch level of your SAP system.

See 7-1-1.

7-2 Optional: Apply a patch to the SAP J2EE Engine of your SAP system.

7-2-1 Check the current patch level of the SAP J2EE Engine.

Find the file version.txt in the directory <Drive>:\usr\sap\<SID>\<Instance>\j2ee\cluster\dispatcher\managers. Read the PatchLevel number.



G:\SETUP\ADM110\SAP_J2EE_Engine_Patch.


Note: You can start with the step "Installing the patch."

Again, follow the instructions given in the SAP Note.

7-2-3 Check the new patch level of the SAP J2EE Engine.

See 7-2-1.


© SAP AG 2003


Content:Preparation for the conversion to Unicode

Procedure to perform a conversion non-Unicode to Unicode

Post-conversion tasks


List the necessary steps to convert non-Unicode to Unicode


© SAP AG 2003

Default Conversion Method

This is the default conversion method:

Start an export of the entire database using R3LoadInstall a new Unicode databaseImport the database using R3Load again


© SAP AG 2003

Important Notes for an Unicode Conversion

Conversion from Unicode to non-Unicode is not possible

MCOD (more than one SAP system in one database):

A Unicode SAP system is not compatible with a non-Unicode SAP system

Unicode SAP systems are not released for Informix

Upgrade with simultaneous Unicode conversion is currently not possible

If the source system is an MDMP system, perform the additional steps that are described in SAP Note 551344.

If you are using HR functionality within SAP R/3 Enterprise, additional steps are mandatory. These steps are described in SAP Note 573044.

Currently SAP does not support an upgrade with simultaneous Unicode conversion. Therefore you must first upgrade a non-Unicode system with a Basis release earlier than 6.20 to 6.20 or later. You can convert to Unicode as soon as the non-Unicode system uses Basis release 6.20 or later.


© SAP AG 2003

Prerequisites on the Source System

Perform the following steps on the source system(see SAP note 548016) :Preparation step in transaction SPUMG

Initialize the worklist

Initialize the language set

Plan worker jobs for consistency check

Correct any inconsistencies

Prepare table pool conversion

Check code pages that are used in your system by referring to table TCPDB (see SAP Note 42305)

To be able to perform the conversion from non-Unicode to Unicode, you require a non-Unicode Kernel CD for the export and a Unicode Kernel CD for the import. Thus you need both the Non-Unicode and the Unicode installation packages.


© SAP AG 2003

Actions on the Source System

Perform an export of the source databaseSee SAP note 548016 for some database dependent steps

See documentation SAP Web Application Server 6.20: Homogeneous and Heterogeneous System Copy, the "R3load Procedure on Windows or Unix" section

Prepare the SAPinst installation

Run SAPinst to export the database


© SAP AG 2003

Transferring the Export Files to the Target Host

On the target host, create a directory <EXPDIR> with sufficient space for the database export files available.

Copy all files and directories (recursively) that are located on the source host in the migration export directory from the source host to the target host.

If you use ftp, make sure you use ASCII mode for transferring the directory <EXPDIR>/DB and use binary mode for transferring all other files.

file filecopy

target systemsource system


© SAP AG 2003

Actions on the Target System (1/2)

1. Check free space for the database load:To find out the size of the export and the sizes of the tablespaces or dbspaces that will be created, look at the file DBSIZE.XML located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE> (Windows) or <EXPDIR>/DB/<DATABASE> (UNIX)

2. Install the target database systemSelect System Copy / Migration in the Selecting the database instance installation method screen

For instructions on how to install the target database system, refer to the installation guide, SAP Web Application Server on <Platform>: <Database>, the "Input for the Installation" section.


© SAP AG 2003

Actions on the Target System (2/2)

In the General Load Parameters window, make the following import settings:

Load Packages from MIGRATION CD.Enter the following parameters:

Migration Key: Leave this field blank.Migration Export Directory: Enter <EXPDIR>.

Continue the target database system installation as described in the installation guide.


© SAP AG 2003

Final Activities on the Target System (1/3)

Activate logging mechanism of the databaseRun installation check: Installation Check (transaction SM28)Perform post installation activities (transaction SE06) with the Database Copy option

This releases all transport, repair, and customizing requests that have not been released in the source system.

Delete all entries from the following tables: ALCONSEG,ALSYSTEMS, DBSNP, MONI, OSMON, PAHI, SDBAD, SDBAH, SDBAP, SDBAR.Execute the RSBTCDEL program and select the Delete with forced mode field to delete cancelled and finished jobsCheck the consistency of the Temporary Sequential Objects (TemSe) using transaction SP12. For more information, see SAP Note 16875

Refer to the installation guide, SAP Web Application Server 6.20: Homogeneous and Heterogeneous System Copy, the "Final Activities" section.


© SAP AG 2003


Adapt the definition of the printers to meet the new system requirementsDelete entries in table DDLOG for buffer synchronization. Synchronize the buffers as described in SAP Note 25380Adapt the client information for the logical systemsAdapt the RFC destinations (transaction SM59) and clean the transactional RFCs (transaction SM58) Create new operation modes, remove old ones, adapt the operation mode time tables (transactions RZ04 and SM63) Check the consistency of the database (transaction DB02)Delete all entries from tables TPFET and TPFHT. These contain information about changes made to the profile of your source systemDelete all entries from table TLOCK, which holds the repair requests from your source system.



© SAP AG 2003


Reschedule cancelled jobs

Redefine database actions (backup, update statistics, etc.) (transaction DB13)

Check entries of the following tables in all involved systems:

TXCOM (SM54)

THOST (SM55)

Post-processing concerning customer objects:If customer objects are not original in the new system, modify the corresponding entries in table TADIR.

If you encounter problems modifying a customer package using transaction SMTS or SM31, use Validate (ENTER) instead of Save to save your changes.



© SAP AG 2003

Further Information

SAP Service Marketplace, http: //service.sap.com/unicode


SAP Web Application Server: Homogeneous and Heterogeneous System Copy

SAP Web Application Server on <Platform>: <Database>

SAP notes as listed in this unit


© SAP AG 2003

Converting Non-Unicode to Unicode: Unit Summary

List the necessary steps to convert non-Unicode to Unicode

Now you are able to


© SAP AG 2003


Content:Solve SAPinst and installation problems

Restart installation procedure

Goal:At the conclusion of this unit, you will be able to:

Handle SAPinst and installation problems

Restart an installation


© SAP AG 2003

Troubleshooting

Guideline and Restart of the Installation

Examples: Problems with SAPinst

Examples: Problems during Installation


© SAP AG 2003

Guideline to Solve Problems

Try these steps to solve problems:

1. Check the file sapinst.log for the message type ERROR

2. Check if it is a known problem:SAP notes mentioned in installation guide

SAPinst troubleshooting guide

SAP notes located on service.sap.com/notes

3. Check if it is a unknown problem:Repeat the command on the operating system, check if the return code gives more information

Create a customer message

Copy files keydb.xml, sapinst_dev.log, … to SAP ftp server sapservX

4. Implement the solution and continue the installation.

Go to the end of sapinst.log and search for the message type ERROR. You can find details about the error situation and the step that failed. If sapinst.log refers to other log files in the relevant sections, check these log files too.

Known problem: Search for SAP notes using SAP Service Marketplace containing possible solutions. Search in SAP notes provided by the installation guide or other troubleshooting guides (go to

service.sap.com/sapinstfeedback and find the SAPinst troubleshooting guide). Unknown problem:

Try to find the reason for the error by repeating the command on the operating system level and checking if the return code gives more information.

Copy the following files from your installation directory <SAPinst_INSTDIR> to sapserv<X> (see SAP Note 40024):

- keydb.xml, sapinst_dev.log - Additional log file(s), if sapinst.log reference the file(s) in the error message.

Create a customer message via SAP Service Marketplace (http://service.sap.com/message) or SAP Net - R/3 Frontend using the component BC-INS.


© SAP AG 2003

Restart Installation (1/5)

SAPinst does not abort the installation in error situations.

SAPinst records the installation progress in file keydb.xml.

The installation can be contuinued from the failed step without repeating previous steps.


© SAP AG 2003


1. Continue an installation that was not cancelled:Error dialog box is still displayed and SAPinst is waiting for your input.

Choose Retry.


© SAP AG 2003


2. Continue an installation that was cancelledInstallation was aborted, problem is solved, and you want to restart.

There are two alternatives:

a. Continuing the installation

Unix:

Start SAPinst from <SAPinst_INSTDIR> with: ./sapinst

Windows:


© SAP AG 2003


b. Restart from scratch, that is, start the installation with the default keydb.xml file as delivered.

Windows:

1

2

UNIX:

Rename keydb.1.xml file (delivered by SAP) to keydb.xml

Delete all keydb.<no>.xml files

Start SAPinst from your <SAPinst_INSTDIR> with: ./sapinst


© SAP AG 2003


Dialog phase:Reset the installation after using the Cancel button in the dialog phase of SAPinst (that is, the phase in which you enter the parameters).

Processing phase: The installation can be cancelled and continued in the processing phase.

Restart Installation

Reset the installation after using the Cancel button. If you cancel the installation in the dialog phase of SAPinst with Cancel, you have to restart the installation from CD with SETUP.CMD (Windows). The cancelled installation cannot be continued during the dialog phase (that is, the phase in which you enter the parameters). An installation in the processing phase can be cancelled and continued.


© SAP AG 2003

SAP Notes with Known Installation Problems

SAP Notes:492305: INST: SAP J2EE Engine / Dialog Inst. / Gateway Inst. 6.20 545422: INST: SAP J2EE Engine Inst. for SAP R/3 Enterprise 4.70 534334: Composite SAP note Installation/Upgrade SAP R/3 Enterprise 523505: INST: SAP R/3 Enterprise 4.70 / 4.70 SR1 on UNIX 529151: INST: SAP R/3 Enterprise 4.70 on Windows -General 531372: INST: SAP R/3 Enterprise 4.70 on Windows - SAP DB Other SAP Notes for other databases


© SAP AG 2003

Flow Trace

Flow Trace provides more detailed information about the installation progress and success.

For detailed information during error situations, restart SAPinst as follows:1. Set environment variable FLOW_TRACE to enabled.

2. Start SAPinst as follows:

sapinst SAPINST_MESSAGE_THRESHOLD=flow_trace


© SAP AG 2003

Example 1: SAPinst and Ports

SAPinst uses the ports 21212 and 21213 for communication with SAPinst GUI

Error message occurs if ports are already in use:

There are two ways to solve the problem and start SAPinst, one on Windows and one on UNIX: Press any key to continue and choose an unused port on this host. On Windows, start SAPinst with special parameters: .\sapinst.exe SAPINST_CONTROL_URL=control_bootstrap.xml

SAPINST_DIALOG_PORT=<port> (where <port> is an unused port on your host) On UNIX, start SAPinst with special parameters: <SAPinst CD>/SAPINST/UNIX/ \ <platform>/INSTALL -port \ <free_port_number>


© SAP AG 2003

Example 2: Local Settings

ERROR Messages:

Trace [iaoxcguist.cpp:110] dostart GUI( ): dostart GUI( ) returns...

Cause: SAPinst GUI start-up error due to local settings. Known reasons are:

Pre-existing *.jar files from Non-SAP-XML parsers (for example, xerces.jar) in your JRE ext directory

UNIX: You use an Xserver with incorrect permissions to perform the installation on another UNIX host (Xhost)

SolutionCheck if there are already <xml_parser>.jar files in the ext directory. <JAVA_HOME>\JRE\lib\ext (on Windows) / <JAVA_HOME>/JRE/lib/ext (on UNIX). Rename those files to xerces.xxx.

On the Xserver, enter xhost +<name> where <name> is the host name of the Xhost.


© SAP AG 2003

Example 3: Library Path

ERROR Messages:

ERROR: fatal: sapcppstd.so open failed: no such file or directory

CauseYou have started SAPinst on operating system Solaris or Compaq True 64, but the library path environment variable is not set correctly.

Solution1. Extend your LD_LIBRARY_PATH environment variable with " .": setenv

LD_LIBRARY_PATH .

2. Run SAPinst again: ./sapinst


© SAP AG 2003

Example 1: R/3 Load

ERROR Messages:

ERROR in SAP<TABART>.log :

file /../<SID>/DB/SAPAPPL0.TSK.bck already seems to exist a previous run may not have been finished cleanly

file /../<SID>/DB/SAPAPPL0.TSK possibly corrupted

/sapmnt/<SID>/exe/R3load: job finished with 1 error(s)

/sapmnt/<SID>/exe/R3load: END OF LOG: 20011213092725

CauseError in the processing sequence of the R/3 load

SolutionRead SAP Note 455195.


© SAP AG 2003

Example 2: Oracle Redologs

ERROR Messages:

MDB-06055 : Range error: Field numberOriglogDirs must be in range [2,25]. Actual value is 0.

CauseYou have set the number of mirrored redo log files to 0 during an SAP system installation on UNIX/Oracle but the value must be greater than 0.

Solution1. Copy the file keydb.xml from your installation directory

<SAPinst_INSTDIR> to sapserv (SAP Note 40024)

2. Create Online Service System error message


© SAP AG 2003

Example 3: Installation CDs

ERROR Messages:MOS-01011: DBR3LOADEXEC_IND_IND InternalInstallationDo:0 SyFilesWithPatternRead (NULL) returned with 0STR FILES FOUND: 0

CauseYou perform an SAP system installation on UNIX and the installation CDs was probably copied manually to disk. 1. The installation CD was copied incompletely to disk.2. Solaris / AIX: During the copy procedure an unwanted automatic

conversion of all file and directory names occurs, changing all uppercase letters to lowercase ones.

Solution1. Check the correctness of your copied files anyway 2. If you find lowercase letters repeat the copy procedure as described

in SAP Note 459899 in topic, "SOLARIS/AIX: Copying CDs"3. Continue the installation by running ./sapinst in the

<SAPinst_INSTDIR>.


© SAP AG 2003

Example 5: Communication User SAPJSF

ERROR Messages:

FRF-00048 Value <Entered_Password> is invalid for parameter IF_PASSWORD.

CauseDuring installation you entered a password longer than 8 characters for the communication user SAPJSF.

SolutionEither restart the installation by starting SAPinst from the CD.

Or open the file keydb.xml in any text editor and search and replace all occurrences of <Entered_Password> with a new password that is no more than 8 characters. Then, continue the installation by choosing SAPinst → <Menu_Entry> → SAPinst Server with GUI from the Windows Start menu.


© SAP AG 2003

Restriction

You must not modify the SAPinst XML files, especially the keydb.xml file, unless SAP delivers a description for the modification.


© SAP AG 2003

Further Information

SAP Service Marketplace, http://service.sap.com/instguidesSAP Service Marketplace, http://service.sap.com/notes

ADM110+ +SAP+R 3+Enterprise+Installation

Documents

Transcript of ADM110+ +SAP+R 3+Enterprise+Installation