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 SAP R/3 Enterprise Architecture, New Features ................................................................................................1-15 MCOD (1/2)........................................................................................................................................................1-16 MCOD (2/2)........................................................................................................................................................1-17 SAP R/3 Enterprise Architecture, New Features ................................................................................................1-19 Directory Server (1/2) .........................................................................................................................................1-20 Directory Server (2/2) .........................................................................................................................................1-21 SAP R/3 Enterprise Architecture, New Features ................................................................................................1-22 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 Content and Objectives .........................................................................................................................................2-2 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 Further Information.............................................................................................................................................2-17 Installation Planning: Unit Summary ..................................................................................................................2-18 Installation Preparation .............................................................................................................................................3-1 Content and Objectives .........................................................................................................................................3-2 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 Further Information.............................................................................................................................................3-27 Installation Preparation: Unit Summary..............................................................................................................3-28 Installation Preparation Exercises .......................................................................................................................3-29 Installation Preparation Installation Preparation Solutions ...............................................................................3-30 Installing SAP GUI ...................................................................................................................................................4-1 Content and Objectives .........................................................................................................................................4-2 Variants of SAP GUI ............................................................................................................................................4-3 Local Installation SAP GUI for Windows (1/3)....................................................................................................4-4 Local Installation SAP GUI for Windows (2/3)....................................................................................................4-5 Local Installation SAP GUI for Windows (3/3)....................................................................................................4-6

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 Installing an SAP GUI Installation Server (5/9)..................................................................................................4-11 Installing an SAP GUI Installation Server (6/9)..................................................................................................4-12 Installing an SAP GUI Installation Server (7/9)..................................................................................................4-13 Installing an SAP GUI Installation Server (8/9)..................................................................................................4-14 Installing an SAP GUI Installation Server (9/9)..................................................................................................4-15 Patching the SAP GUI (1/4)................................................................................................................................4-16 Patching the SAP GUI (2/4)................................................................................................................................4-17 Patching the SAP GUI (3/4)................................................................................................................................4-18 Patching the SAP GUI (4/4)................................................................................................................................4-19 Installing SAP GUI for Java (1/3).......................................................................................................................4-20 Installing SAP GUI for Java (2/3).......................................................................................................................4-21 Installing SAP GUI for Java (3/3).......................................................................................................................4-22 Further Information.............................................................................................................................................4-23 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 Content and Objectives .........................................................................................................................................5-2 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 Installation Process .............................................................................................................................................5-32 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 Windows Domain Information and RAM...........................................................................................................5-38 Instance Directory and Transport Host ...............................................................................................................5-39 Set Passwords for Operating System User ..........................................................................................................5-40 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 Installation Steps .................................................................................................................................................5-52 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 Installation Process .............................................................................................................................................5-57 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 Installation Steps .................................................................................................................................................5-64

Finish Installation of SAP J2EE Engine..............................................................................................................5-65 Installation Process .............................................................................................................................................5-66 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 Windows Domain Information and RAM...........................................................................................................5-71 Instance Directory and Transport Host ...............................................................................................................5-72 Set Passwords for Operating System User ..........................................................................................................5-73 CD Browser and Message Server Port ................................................................................................................5-74 Database Schema and CD Browser.....................................................................................................................5-75 Parameter for SAP J2EE Engine.........................................................................................................................5-76 Installation Steps .................................................................................................................................................5-77 Finish Dialog Instance Installation......................................................................................................................5-78 Appendix: Installing Client Software..................................................................................................................5-79 Installation Process .............................................................................................................................................5-80 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 Further Information.............................................................................................................................................5-91 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 Content and Objectives .........................................................................................................................................6-2 Post-Installation Activities ....................................................................................................................................6-3 Start and Stop the SAP System .............................................................................................................................6-4 Checking SAP System Services............................................................................................................................6-5 Post-Installation Activities ....................................................................................................................................6-6 SAP License..........................................................................................................................................................6-7 Installing SAP Licenses ........................................................................................................................................6-8 Post-Installation Activities ....................................................................................................................................6-9 Installing the SAP Online Documentation ..........................................................................................................6-10 General Information to Install the Helpfiles........................................................................................................6-11 Installation of Help Type HtmHelpFile...............................................................................................................6-12

...................................................................................................................................................................................................................................................................................................................6-23 TMS Configuration: Transport Routes ........................................................................................6-15 Post-Installation Activities ............................................................................................................. PlainHtmlFile (1/2).................................................6-47 SAP Load Generator (SGEN) .............6-50 Windows: SAP Accounts.................................................................................6-54 UNIX: Performing File and Directory Adjustments ....................................6-33 Installation of Additional Languages (1/3) .............6-24 Basic Configuration: Import of Profiles............................................................................................................................................................................................6-44 SAP J2EE Engine......................................................................................................................................................................................6-38 Implementation of Packages .......6-52 Completing and Checking Oracle Installation ..................................................................Installation of PlainHtmlHttp.......................................................................................................................................6-27 Basic Configuration: Background Jobs.......................................................................................................................................................................................................................6-14 Setup Variants and Browser for Online Help...................................6-19 SAProuter and SAPNet–R/3 Frontend........................................................................................6-25 Basic Configuration: Number of Work Processes..........................6-26 Basic Configuration: Set Up Operation Modes.......................................................6-13 Installation of PlainHtmlHttp..................................6-36 Installation of Additional Languages (3/3) .................................................................................................................................6-42 Perform a Full Backup: UNIX ....................6-37 Language Import: New Features ................................6-18 Configuring SAProuter and SAPNet–R/3 Frontend.......6-48 UNICODE Post-Installation Procedure ...................................................................................................................6-41 Perform a Full Backup: Windows.........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................6-43 Checking the RFC Destination......6-31 Installation Check ....................................6-16 SAProuter and SAPNet–R/3 Frontend....................................................................................................................................................................................................................................................................6-40 Client Copy with SAP R/3 Enterprise.....................................................................6-20 Post-Installation Activities ........................................................6-51 Installing Administration Tools for a Database .............6-35 Installation of Additional Languages (2/3) .............................6-39 Client Copy ............................................................................6-32 Activation of SAP R/3 Enterprise Extension Set ............................................................................................6-55 .......................................................................................................................................................................................................................................................6-29 Basic Configuration ...........................................................6-30 Post-Installation Activities .............................................................................6-21 Post-Installation Activities for Transport Organizer ...........................6-45 SAP J2EE Engine: User SAPJSF...........................................................6-22 TMS Configuration: Transport Domain............................................................................................................................................................................................................................................................................................................................6-17 Configuring SAProuter and SAPNet–R/3 Frontend.................................................................................................................................................................................6-53 Informix Administrative Tools .......................................................................................................6-28 Basic Configuration: User and Roles ..................................................................................... PlainHtmlFile (2/2).......................................................................................................................................6-49 Post-Installation Activities ..........................................................................................................................................................................6-46 Additional Information for SAP J2EE Engine and SDM.......................................

.......................................................................................................................7-12 Appendix: Stopping the Database using dbmgui ........................................................................................................................................................................ Screenshots (2/2) ...............................................................................................................................................................................................................................................................................................................................................................................6-56 Further Information..................................................................................................................................8-10 Final Activities on the Target System (2/3) ................................................8-12 Further Information..........................................................................................8-3 Important Notes for an Unicode Conversion .........................8-1 Content and Objectives .....................................6-62 Implementing Patches ....................................................................8-13 Converting Non-Unicode to Unicode: Unit Summary .................................................................................................7-11 Appendix: Configuring dbmgui ....................UNIX: Performing Operating System Adjustments..................................................................................................7-5 Patching the SAP J2EE Engine (1/2) ..............................................................................................................................................................8-2 Default Conversion Method...................................................................................................................................................................................................................................................8-14 Troubleshooting ........................................................................9-2 Troubleshooting ...............................................................................................................................8-7 Actions on the Target System (1/2)........................................................................................................................7-18 Converting Non-Unicode to Unicode ...............................................9-5 ..........................................................................................................7-6 Patching the SAP J2EE Engine (2/2) .........................................................8-8 Actions on the Target System (2/2)...............................................7-15 Implementing Patches: Unit Summary .................................................................................................................................................................................................................................................................8-6 Transferring the Export Files to the Target Host....................................... DB-Dependent Part) .........................................8-11 Final Activities on the Target System (3/3) ..................................................................................6-57 Post-Installation Activities: Unit Summary ........................................9-3 Guideline to Solve Problems............................................................................................................................................................................................7-14 Further Information....................................................................................................................................................................................................................................................................9-1 Content and Objectives ..................................7-3 Applying a Kernel Patch.................................................................................................................................7-4 Applying a Kernel Patch...............6-59 Post-Installation Activities Solutions .7-8 Applying a Database Patch ...............7-10 Appendix: Installation of dbmgui for SAP DB (2/2) .....................7-17 Implementing Patches Implementing Patches Solutions.................................................................9-4 Restart Installation (1/5)....7-7 Apply Support Packages using Transaction SPAM ....7-1 Content and Objectives ...............................................................................8-4 Prerequisites on the Source System ..................................................................................................................................................................7-16 Implementingof Patches Implementing Patches Exercises .....................................................7-2 Applying a Kernel Patch (incl..................................7-9 Appendix: Installation of dbmgui for SAP DB (1/2) .......................................................................................................................................................7-13 Appendix: Applying a Database Patch for SAP DB ..................................................................................................................................................................................................8-9 Final Activities on the Target System (1/3) .......................................................................................................................................................................................................................................................................................................................................................................8-5 Actions on the Source System...................................................................................................................6-58 Post-Installation Activities Post-Installation Activities Exercises ........................................ Screenshots (1/2) .............................................................................................................................................................

......................................................9-15 Troubleshooting ..........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................9-9 SAP Notes with Known Installation Problems .........................................................................................................................................................................................................................................................................................................................................................................................Restart Installation (2/5)..................................................................................................................................9-14 Example 3: Library Path ...............................................................................................................................................................................9-11 Troubleshooting .......................9-22 Further Information.........................................................................................................................................9-10 Flow Trace ........................................................................................................9-18 Example 3: Installation CDs .....9-6 Restart Installation (3/5).............................................................................................................9-16 Example 1: R/3 Load ............................................................9-8 Restart Installation (5/5)......................................................9-12 Example 1: SAPinst and Ports .............................................................................................................................................................................................................9-19 Example 4: SAP J2EE Engine ............................................................................................................................9-24 ..............9-7 Restart Installation (4/5).........................................................9-21 Restriction ....................................................................................9-23 Installation Processes: Unit Summary.....................................................9-13 Example 2: Local Settings ..................................................................................9-17 Example 2: Oracle Redologs.........................................9-20 Example 5: Communication User SAPJSF .................

FS310 Inkasso/Exkasso ADM110 SAP R/3 Enterprise Installation Diese Seite wird von Andrea für euch noch erstell! ADM110 <leave this slide blank> SAP R/3 Enterprise Installation THE BEST-RUN BUSINESSES RUN SAP © SAP AG© SAP AG 2003 2003 SAP Web Application Server 6.20 2003/Q3 Material number: 50063703 .

OSF/1®. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. R/2. All rights reserved. OS/390®. Parallel Sysplex®. PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. OS/400®. mySAP. Inc. X/Open®. AIX®. World Wide Web Consortium. Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. XML. WinFrame®. mySAP. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. VideoFrame®. Citrix®. Tivoli®. SAP. pSeries. DB2®. and Motif® are registered trademarks of the Open Group. R/3. SAP Logo. WINDOWS®. Program Neighborhood®. z/OS. 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 . MVS/ESA.Copyright Copyright 2003 SAP AG. the Citrix logo. zSeries. HTML. WebSphere®. Word®. ORACLE® is a registered trademark of ORACLE Corporation. AFP. Inc. OS/2®. © SAP AG 2003 Trademarks: Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. MetaFrame®. XHTML are trademarks or registered trademarks of W3C®. Inc. Netfinity®. NT®. Massachusetts Institute of Technology. Microsoft®. UNIX®. EXCEL®. JAVA® is a registered trademark of Sun Microsystems. Intelligent Miner. JAVASCRIPT® is a registered trademark of Sun Microsystems. DB2 Universal Database. The information contained herein may be changed without prior notice. used under license for technology invented and implemented by Netscape. AS/400®. xSeries. S/390®. IBM®. MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems. ICA®. iSeries.. DHTML. All rights reserved.com.

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

The exercises offer additional examples of material covered in the course. . The material includes space for recording classroom notes. These materials complement the course instructor's explanations.Target Audience This course is intended for the following audiences: SAP system administrators Technology consultants Duration: Two days © SAP AG 2003 This course is not a self-study program. Participants are encouraged to complete any exercises not covered during the classroom training to deepen their knowledge of the subject matter. There may not be enough time to do all the exercises included in this course during the classroom training.

Course Prerequisites Required Knowledge: SAPTEC – SAP NetWeaver: Fundamentals of the Application Platform ADM100 – SAP Web AS Administration I Recommended Knowledge: Working experience with SAP system administration © SAP AG 2003 .

New Features Installation Planning Installation Preparation Installing SAP GUI Unit 5 Unit 6 Unit 7 Unit 8 Installation Process Post-Installation Activities Implementing Patches Converting Non-Unicode to Unicode Troubleshooting Installation Problems Unit 2 Unit 3 Unit 4 Unit 9 © SAP AG 2003 .Course Content Preface Unit 1 SAP R/3 Enterprise Architecture.

SAP R/3 Enterprise Architecture. New Features Installation Planning Installation Preparation Installing SAP GUI Installation Process Post-Installation Activities Implementing Patches Converting Non-Unicode to Unicode Troubleshooting Installation Problems (C) SAP AG ADM110 1-1 . New Features 1 2 3 4 5 6 7 8 9 © SAP AG 2003 SAP R/3 Enterprise Architecture.

Directory Server List differences between SAPinst and R3setup © SAP AG 2003 (C) SAP AG ADM110 1-2 . you will be able to: Describe the architecture of SAP R/3 Enterprise and SAP J2EE Engine Explain and use the terms Unicode. LDAP New features of SAPinst Objectives: At the conclusion of this unit. MCOD. MCOD.Content and Objectives Content: Overview of SAP R/3 Enterprise architecture and SAP J2EE Engine New features with SAP R/3 Enterprise: Unicode.

SAP R/3 Enterprise Architecture. New Features SAP R/3 Enterprise Architecture SAP J2EE Engine Unicode MCOD Directory Server SAPINST © SAP AG 2003 (C) SAP AG ADM110 1-3 .

0 SAP R/3 4.5 SAP R/3 4. From a technical perspective. From a functional perspective. Specifically. at no extra cost. this is SAP Web Application Server 6. Infrastructure developments (such as performance or continuous improvement) and legally required changes are made in SAP R/3 Enterprise Core.SAP R/3 Development Strategy 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 Enterprise SAP R/3 3. 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. The extensions will be continuously developed.1 SAP R/3 4. Functional developments now take place separately in SAP R/3 Enterprise Extensions. The SAP Web Application Server is downward compatible. customers can now upgrade the technology infrastructure only without doing any functional upgrade. SAP R/3 4.6 © SAP AG 2003 The SAP R/3 Enterprise strategy follows a structured approach from both a technical and functional perspective. the latest version of SAP NetWeaver was used as the foundation for SAP R/3 Enterprise. the previous application release. These extensions do not modify the core (whereas some previous industry add-ons did). that is.20. The release cycle for SAP R/3 Enterprise Extensions is separate from that of the SAP R/3 Enterprise Core. was used as the application basis for SAP R/3 Enterprise.6C. (C) SAP AG ADM110 1-4 .

70 consists of the SAP_APPL 470 and SAP_HR 470 software components. SAP BW 3.0) also include the SAP Web Application Server but they have different application functions.10 consists of the EA-HR 110. among other things. 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. (C) SAP AG ADM110 1-5 . EA. SAP R/3 Enterprise Core 4.RETAIL 110.10 Plug-In Industry Solution Plug-In SAP_APPL SAP_HR SAP_BW SAP R/3 Enterprise Core 4.20 © SAP AG 2003 SAP Web AS 6. These components guarantee the integration of the SAP R/3 Enterprise Extension Set and the SAP R/3 Enterprise Core. the SAP kernel and the SAP_BASIS 620 and SAP_ABA 620 software components. each containing different software components.20 consists of. EA-APPL 110. EA-GLTRADE 110. Other SAP systems (such as SAP BW 3.) SAP Web Application Server (Web AS) 6..10 SAP_BASIS SAP_ABA SAP Web AS 6.. refer to SAP Note 538887. For more information about SAP R/3 Enterprise software architecture. (Note: All building blocks can have different release numbers. In addition.20 From a technical point of view. SAP R/3 Enterprise Extension Set 1.Building Blocks of SAP Systems GLTRADE Extension SAP R/3 Enterprise FINSERV Extension SAP R/3 Enterprise SAP R/3 Enterprise Extension Set 1.1 or SAP CRM 4. EA-PS 110 and EA-FINSERV 110 software components. EA-IPPE 110.70 SAP_BASIS SAP_ABA . the first SAP R/3 Enterprise release consists of three parts.

they must upgrade the extension set.20 SAP Web AS 6.00 SAP R/3 Enterprise Extension Set 3. SAP R/3 Enterprise Core is maintained through support packages (HR support packages and non HR support packages).7) SP Maintenance Maintenance Maintenance SP SP SP SP SP SP SP SAP Web AS 6.Release Strategy of SAP R/3 Enterprise 2002 Maintenance Maintenance Maintenance 2003 2004 2005 2006 2007 SAP R/3 Enterprise Extension Set 1.10 Maintenance SAP R/3 Enterprise Extension Set 2. When customers upgrade to a higher level of an extension.30 SAP Web AS 6.40 © SAP AG 2003 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. (C) SAP AG ADM110 1-6 .00 SAP R/3 Enterprise Core (4.

SAP GUI SAP GUI Linux Unix Windows Operating System OS/400 OS/390 Database Server SAP DB Informix Microsoft SQL Server © SAP AG 2003 Oracle DB2 (DB4.SAP Web AS 6. 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. The ICM enables SAP systems to communicate directly with the Internet. The Internet Communication Manager (ICM) is a new process in SAP Web AS 6. (C) SAP AG ADM110 1-7 .20: Architecture and Connectivity HTTP(S) Browser SMTP SOAP/XML Internet Communication Manager SAP Web AS RFC SAP J2EE Engine fast RFC ABAP DIAG external systems.10. DB6) Database System The SAP Web Application Server supports many open technical standards.20.

New Features SAP R/3 Enterprise Architecture SAP J2EE Engine Unicode MCOD Directory Server SAPINST © SAP AG 2003 (C) SAP AG ADM110 1-8 .SAP R/3 Enterprise Architecture.

The SAP Java Connector is a toolkit that allows a Java application to communicate with any SAP system. SDM provides tools. which provide functions similar to the transporttools tp and R3trans. Data exchange between ICM and the ABAP Dispatcher is done by memory pipes (MPI)... ICM redirects the HTTP request from the client to the SAP J2EE Engine unchanged.20. Server SAP J2EE Engine © SAP AG 2003 SAP J2EE Engine fulfills the J2EE 1.2 standard and has integrated standard APIs (JDBC. For more information. Calls from Java to ABAP system and from SAP system to Java are supported. refer to SAP Note 544979. Fast RFC provides an additional fast. to deploy SDA (Software Delivery Archives). RMI. SDM (Software Delivery Manager) is a standalone tool. JCo Dispatcher WP . (C) SAP AG ADM110 1-9 . local communication channel for JAVA-ABAP components via shared memory and an efficient representation response mapping of the data types of both systems..SAP J2EE Engine: Web Access Web Browser/ Web Server SAP Web Application Server ICM MS MPI http Dispatcher fast RFC. ICM ensures the client connection with SAP Web servers (ABAP and Java). JNDI. and so on). Connectivity between SAP J2EE Engine and SAP Web AS is available via SAP Java Connector (JCo) and fast RFC. WP Server . If the request turns out to be a Java request. SDM is used to deploy your self-developed and SAP shipped software. shipped with SAP Web AS 6..

The user SAPJSF (type: communication) is required for the RFC communication authentication between the J2EE service. • 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). Variant 2: SAP J2EE standalone • This variant is used to set up a pure Java development environment including tools. Variant 1: • The SAP J2EE Engine can be started only by starting the SAP system. monitoring.. • Administration and monitoring is done via transaction SMICM.. security.exe) Dispatcher and Server consist of: © SAP AG 2003 Managers (Thread. SAPJSF is automatically installed during a central instance installation. and the SAP system. (C) SAP AG ADM110 1-10 .SAP J2EE Engine: Installation Variants SAP J2EE Engine Standalone Installation Visual Client SAP J2EE Engine Cluster Installation Visual Client Client Client Administrator Administrator Dispatcher1 Server1 Dispatcher1 Dispatcher2 Server 1 Server 2 Server 3 Server 4 Host 1 Host 2 Java Virtual Machine (java. • Administration. .) Variant 1: Web Application Server with SAP J2EE cluster version • This variant is integrated with SAP Web Application Server. . deploy. • The SAP J2EE Engine on a dialog instance (DI) starts only if the CI and the J2EE Engine on the CI is running.. Memory.) Services (log. http. • The host on which the central instance (CI) runs serves as cluster host.. without ICM and SAP Web Application Server. This guarantees the communication between ICM and J2EE Engine. and deployment are done with J2EE admin and deploy tool. • The J2EE engines belonging to one SAP system form a cluster.

New Features SAP R/3 Enterprise Architecture SAP J2EE Engine Unicode MCOD Directory Server SAPINST © SAP AG 2003 (C) SAP AG ADM110 1-11 .SAP R/3 Enterprise Architecture.

an individual user can use only characters belonging to one code page at a time. One (normal: 1 byte) code page represents 256 characters. To further enhance language support for the mySAP Business Suite. as well as multiple code pages in a single installation with MDMP (Multi-Display-Multi-Processing). A code page describes the assignment of one character to one hexadecimal (HEX) value. consistent. Only languages belonging to the same code page are usable without restriction. Unicode is defined by the Unicode consortium (see http://www. Yet even in a MDMP system. SAP considers Unicode the appropriate development direction and strategy because Unicode offers a single. SAP supports multiple languages with MDMP (Multi-Display/MultiProcessing) systems Languages within an ellipse can be combined in one SAP system using a standard code page © SAP AG 2003 Unlike other standard code pages. global character encoding.Unicode (1/2) SAP systems support more than 30 different languages. Until now SAP has provided multiple language support using single code pages. (C) SAP AG ADM110 1-12 .org for more information) consisting of world-leading companies in the IT industry. and standard character set encoding for virtually all languages in the world.unicode. which permits the application server to dynamically switch code pages according to the logon language and language keys (see SAP Note 73606). Unicode defines a character set that includes virtually all characters used in the world and therefore provides consistent.

(C) SAP AG ADM110 1-13 . and 379940. memory.sap. Go to the SAP Service Marketplace on the Web at http://service.com/unicode.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 number Increase in resource consumption CPU. network: +30% Database size: +30% (depending on database type) © SAP AG 2003 For more information about Unicode SAP systems and their availability. refer to SAP Notes 79991. 540911.

Unicode and SAP Web AS Unicode supported since SAP Web Application Server 6. It is possible to maintain all characters from all languages. (C) SAP AG ADM110 1-14 . A single GUI can be used to access both Unicode and Non-Unicode systems. Code Page maintenance: Enhanced.10 SAP Web AS 6. Unicode-based code page architecture improves (printer) code page maintenance. 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.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 © SAP AG 2003 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).

SAP R/3 Enterprise Architecture. New Features SAP R/3 Enterprise Architecture SAP J2EE Engine Unicode MCOD Directory Server SAPINST © SAP AG 2003 (C) SAP AG ADM110 1-15 .

MCOD will be available with all mySAP Business Suite components. SAP is releasing this technology on all databases for the SAP system. MCOD is not an additional installation service. Now combined installations of both component types are also supported under special conditions. No extra effort is required because the MCOD installation is fully integrated into the standard installation procedure. Using MCOD technology is as easy as installing a separate component. development. for performance reasons SAP recommended separating OLTP applications (such as SAP R/3) and OLAP applications (such as SAP BW). go to /mcod from the SAP Service Marketplace. in line with our commitment to deliver platform-independent solutions. n Databases Simplification using MCOD option: n SAP systems. offers these main advantages: Full flexibility and independence of the installed components Simplified administration. which is a powerful way to install several mySAP Business Suite components in one physical database. When MCOD became generally available in 2002. SAP recommends running MCOD systems in the same context. and productive systems in the same MCOD database. (C) SAP AG ADM110 1-16 . 1 Database SAP R/3 RDBMS SAP BW RDBMS SAP R/3 SAP BW RDBMS SAP CRM RDBMS SAP SEM RDBMS SAP CRM SAP SEM SAP EBP RDBMS SAP EBP © SAP AG 2003 You can install multiple SAP systems in a single database using Multiple Components in One Database (MCOD).MCOD (1/2) Traditional system setup: n SAP systems. backup and recovery Additive sizing approach Data consistency across systems Reduced maintenance and operating costs For more information. it is an option of the SAP system installation. Instead. The mixing of productive and nonproductive systems is not supported. Multiple Components in One Database (MCOD). SAP does not recommend mixing test.

to ensure the following: Integrity of business data No locking conflicts on database tables No special coding for MCOD installations (C) SAP AG ADM110 1-17 . not database level. are also possible). such as multiple SAP R/3 systems.MCOD (2/2) business data SAP R/3 SAP CRM SID = ER4 SID = CM1 DB User: SAPER4 T100 (SAPER4) DB User: SAPCM1 T100 (SAPCM1) business data © SAP AG 2003 X Administrative opportunities: Multiple independent and different software solutions are located in one database (multiple identical software components. Migration of existing systems is possible. go to /mcod and /platforms on the SAP Service Marketplace. Databases support schema. Each mySAP Business Suite component connects the database with one single database user. The technical realization in detail depends on the database product. each mySAP Business Suite component uses its own schema by accessing the database with a unique dedicated database user. Point-in-time recovery of semantically related systems such as SAP R/3 and SAP CRM is possible. There is one logical and physical database instance. Data exchange between different SAP systems is done on application level. 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. For more information on released platforms and availability. This user is independent of the user logged on to the SAP system itself. All systems use the same OS/DB release.

No additional educational effort (for companies already familiar with the exchange of data between SAP systems) (C) SAP AG ADM110 1-18 .

New Features SAP R/3 Enterprise Architecture SAP J2EE Engine Unicode MCOD Directory Server SAPINST © SAP AG 2003 (C) SAP AG ADM110 1-19 .SAP R/3 Enterprise Architecture.

10. the LDAP connector is an integrated part of the SAP application server.Directory Server (1/2) HR system SAP or Non-SAP Operating System SAP Enterprise Portal Exchange of Roles Corporate Directory Server EMail SAP Web AS Phone / Fax Central User Administration © SAP AG 2003 SAP systems Other applications A directory server acts as a central repository for data that is used by different applications. but other objects can be stored as well. Go to /partnerdirectory on the SAP Service Marketplace for SAP-certified vendors of directory servers.6A. easy-to-use customizing was added (transaction LDAP). In August 2001. documents or hardware is stored. SAP has been working on integrating the directory server using LDAP for years: With SAP Basis 4. the SAP Web AS 6. (C) SAP AG ADM110 1-20 . The concepts of directory server integration and Central User Administration (CUA) can be implemented independently of one another or combined. Usually information concerning users. In contrast to relational database management systems (RDBMS). directory servers use a hierarchical structure to organize the data.10 got the "Works with LDAP" certificate of the OpenGroup. The data is important in a heterogeneous system environment. Access is possible via standard protocol such as LDAP (Lightweight Directory Access Protocol). The SAP Enterprise Portal 5. With SAP Web AS 6.0 requires a corporate directory server (as user persistence store).

setting up integration of a directory server is done in Customizing (performed via the Implementation Guide (IMG) or using transaction LDAP). refer to Quick Link /security on the SAP Service Marketplace (choose Security in Detail → Identity Management → Directory Service Integration) and SAP course ADM102. 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. three user groups are distinguished. During synchronization. (C) SAP AG ADM110 1-21 .Directory Server (2/2) SAP Web AS LDAP Directory Server (DS) SAP SAP/DS SAP/DS DS SAP Create in DS Delete in SAP Lock in SAP Ignore © SAP AG 2003 DS Create in SAP SAP/DS Compare Time Stamp Delete in DS Ignore Time Stamp Ignore Ignore Objects Technically. it is possible to select either delta synchronization (compare time stamps) or full synchronization (ignore time stamp). For further information. For this user.

New Features SAP R/3 Enterprise Architecture SAP J2EE Engine Unicode MCOD Directory Server SAPINST © SAP AG 2003 (C) SAP AG ADM110 1-22 .SAP R/3 Enterprise Architecture.

You can start SAPinst GUI on a remote computer if you want. Because SAPinst GUI is Java based. Other Features: Aborted installations can be resumed. SAPinst GUI requires a Java Runtime Environment (JRE) and a Java Development Environment (JDK). SAPinst GUI can be started on a remote computer. it stops the installation and you can retry the installation after solving the problem.log. sapinst.New Features with SAPinst SAP provides a new installation tool: System Landscape Implementation Manager: SAPinst The main advantages compared to R3SETUP are: Step back possible without restarting the installation No abort due to errors Fewer log files (such as sapinst. SAPinst does not abort because of errors. Instead.sap.com/sapinstfeedback. SAPinst Troubleshooting Guide at http://service. For more information about SAPinst. you can abort the installation manually if you want. refer to the documentation. © SAP AG 2003 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 has a graphical user interface (GUI). SAPinst GUI. SAPinst continues an aborted installation directly from the point of failure. SAPinst records installation progress in a single log file. you need a Java Runtime Environment (JRE). (C) SAP AG ADM110 1-23 . Alternatively.log) SAPinst GUI allows you to monitor the installation progress and see all messages issued by SAPinst. which allows you to monitor the progress of the installation and see all messages issued by SAPinst.

com/j2ee SAP R/3 Enterprise: service.com/security service.sap.sap.sap.com/enterprise Unicode: service.sap.sap.com/partnerdirectory © SAP AG 2003 (C) SAP AG ADM110 1-24 .20 → mySAP Technology Components → SAP Web Application Server -> SAP J2EE Engine service.sap.sap.com: SAP NetWeaver →SAP Web Application Server 6.com/unicode MCOD: service.Further Information SAP J2EE Engine: SAP Library at http://help.com/mcod Directory Server: service.

MCOD. LDAP List differences between SAPinst and R3setup © SAP AG 2003 (C) SAP AG ADM110 1-25 .SAP R/3 Enterprise Architecture. New Features: Unit Summary Now you are able to: Describe the architecture of SAP R/3 Enterprise and SAP J2EE Engine Explain and use the terms Unicode.

New Features Installation Planning Installation Preparation Installing SAP GUI Installation Process Post-Installation Activities Implementing Patches Converting Non-Unicode to Unicode Troubleshooting Installation Problems (C) SAP AG ADM110 2-1 .Installation Planning 1 2 3 4 5 6 7 8 9 © SAP AG 2003 SAP R/3 Enterprise Architecture.

you will be able to: List the requirements for an installation of SAP R/3 Enterprise Explain some technical choices to be made © SAP AG 2003 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. (C) SAP AG ADM110 2-2 . Typically this phase begins several weeks before the actual installation takes place.Content and Objectives Content: Sizing Installation Options Technical Requirements Objectives: At the conclusion of this unit.

Hardware sized too large means you invested too much money to reach your goal of good performance. Adequate hardware prevents performance losses and avoids unnecessary hardware costs.Sizing Your System Sizing determines the hardware you need to host your system: SAP System SAP System SAP System Hardware too small to host the planned system SAP System SAP System Hardware OK! Hardware too large For sizing information see http://service.sap. (C) SAP AG ADM110 2-3 .com/sizing © SAP AG 2003 Consider the following potential issues: Hardware that is sized too small costs performance because it leads to high response times and inefficient production.

a new sizing (or hardware improvement) might become necessary.6C. DB2 UDB. and so on) Functions used in the system (for example SAP R/3): lean (HR. It determines what hardware resources you will need for your SAP system. FI) or complex (PP) Release of system (SAP R/3 4. and so on) Preferred backup concept (for example. Microsoft SQL Server. SAP CRM.Sizing is an Ongoing Process Sizing is an ongoing process! new users added SAP System SAP System SAP System Hardware OK! Hardware no longer OK some time later Hardware OK again! initially after hardware resizing time © SAP AG 2003 Sizing plays a role very early in the planning of your SAP system landscape. online backup parallel to productive use requires more hardware) If one or more of the above factors are subject to change. SAP R/3 Enterprise. and so on) Type of access to the system (LAN. WAN. Solaris.6 second required?) The amount of high availability needed (full blown solutions may cost a fortune) Type of system (SAP R/3 Enterprise. SAP R/3 4. GUI type. 64-bit OS / Linux. W2K. Win NT. (C) SAP AG ADM110 2-4 .5 seconds OK or 0. HP-UX. SAP BW. 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. and so on) Type of database used (SAP DB. AIX.0B. Oracle. and so on) Type of OS (32-bit.

UTF-16 requires more space than UTF-8. depends largely on the type of Unicode representation chosen. For performance data on the database systems under Unicode. The load on RAM (again caused by the application software.sap. the resources of the system could be doubled to be prepared for some worst-case scenario.sapdb. contact your database manufacturer.sap.org. Therefore. For information about SAP DB.Sizing and Unicode Unicode influences the following factors: Load of applications on hardware (CPU & RAM) See http://service. The performance of the database system is affected as well.com/unicode Result depends on usage of UTF-8 or UTF-16 Performance of database Ask database vendor for performance results of database using Unicode © SAP AG 2003 Unicode systems use between 1 and 5 bytes of space for storing single characters (depending on the character and its Unicode representation). + 50% RAM Size of database See http://service.sap. the SAP software. refer to http://www. compared to non-Unicode systems. not the database software) increased by about 50%. increased by about 35%. in this case. Actually the load on the CPU caused by the applications.com/performance Result: about + 35% CPU. in a very simple estimate.com/unicode See http://service. (C) SAP AG ADM110 2-5 . The size of the the database of Unicode systems.

There are a few differences between the availability of SAP Web AS 6.20 Informix (SAP Note 0407317) Released Operating Systems SAP Web AS 6. For these differences.5.Supported Platforms The supported platforms for SAP R/3 Enterprise are identical to those for SAP Web AS 6. 3 times RAM on UNIX (32-bit: 20 GB Swap max. 20 GB). For details see: Released Operating Systems SAP Web AS 6. see also SAP Note 407317. 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.20 MS SQL Server (SAP Note 0407328) Released Operating Systems SAP Web AS 6.com/platforms © SAP AG 2003 The SAP Notes listed in the figure provide details about the availability of operating systems for different databases with SAP Web AS 6. (C) SAP AG ADM110 2-6 .sap. check out the difference matrix found at http://service.20 DB2/400 (SAP Note 0410783) Released Operating Systems SAP Web AS 6.20 and SAP R/3 Enterprise.20.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..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.20 Oracle (SAP Note 0407314) See also http://service.5 GB on UNIX Page/Swap: 4 times RAM on Windows OS (max.com/platforms.20. 64-bit: 20 GB Swap recommended) 64 to 512 MB RAM for SAP J2EE Engine (for both Windows OS and UNIX) For UNIX. 1.20 DB2/390 (SAP Note 0407325) Released Operating Systems SAP Web AS 6.sap.

some core business processes even run somewhat faster than before. an SAP R/3 Enterprise system does not require more hardware resources than SAP R/3 4.6C. SAP R/3 4.6C against SAP R/3 Enterprise For its non-Unicode version. Actually.6C SAP R/3 Enterprise Upgrade Hardware OK! Same Hardware: OK! Live installations and upgrades show usually less than 5% increase in hardware consumption.20). SAP R/3 Enterprise requires no more hardware than SAP R/3 4. (C) SAP AG ADM110 2-7 .Sizing SAP R/3 4. © SAP AG 2003 Aside from the additional resources needed for Unicode. because of some further improvements made (using state-of-the-art techniques available with SAP Web AS 6.6C if the same core business processes are used.

Stand-alone database instance: In this scenario the database gets "its own" hardware. an additional dialog instance is a possible solution. This setup is useful in small companies in which one server is able to offer all hardware resources needed for the system. Also it is possible (and shown in this workshop) to install more than one instance on one server. This way interferences from the SAP instance on the database performance are excluded. Productive systems with more than 20 dialog instances can be found. Some examples and considerations follow.Installation Options Central system: Dialog instance: Dispatcher Dispatcher the complete DEV system part of QAS system Stand-alone database instance: part of PRD system © SAP AG 2003 SAP software can be distributed in several ways on the available hardware. 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. you need at least one dialog instance. Because this central hardware can be sized very large. (C) SAP AG ADM110 2-8 . A dialog instance may host as many users as their corresponding hardware allows. If you are using a stand-alone database instance. 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. Central system: All software needed for an SAP system is installed on one machine (except the SAP GUI software for the end users). This decision may also be influenced by the result of the sizing because the distribution of the software can affect system performance. SAP systems may have lots of dialog instances.

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. The technical infrastructure influences the technical areas listed in the figure. (C) SAP AG ADM110 2-9 . The technical setup includes network layout.com/ti (ti = Technical Infrastructure) The following slides present some factors that affect the parameters listed above. © SAP AG 2003 The technical infrastructure describes the technical setup of the SAP system. server layout. disk layout of the database. type of computer interface used and many more details.

(C) SAP AG ADM110 2-10 .) Dispatcher Port * = can be made more secure by using SAProuter Gateway Service (Gateway) Print Service (Spool) Info Service (Message Server) Message Server Port Gateway Port 32<nn> * 36<xx> * Gateway Port 33<nn> * 515 Printer Port * SAP GUI for SAP GUI for Windows Windows © SAP AG 2003 different SAP System External programs using SAP Communication API Print Service (SAPlpd) As shown in the figure. the SAP system uses several different ports for external communication.sap. SAProuter) to ensure the SAP system's security. For more information.com/network and choose Network Integration of SAP Servers. 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. firewall. Furthermore.Network: External Ports Used by SAP Systems SAP Web Application Server Dialog Service (Dispatcher and Workproc. go to http://intranet. router. All these ports should be secured by some means (for example.

Therefore.Network: Load Caused by SAP Communication SAP GUI for SAP GUI for Windows Windows bandwidth needed per dialog step: below 7KB* Dispatcher Dispatcher recommended: 100 megabits per second or more © SAP AG 2003 * for SAP R/3 Enterprise.sap. SAP GUI for HTML. from this page. Frontend Network Requirements for SAP Solutions. and so on) Type of product used (mySAP CRM. From here you can download the document. SAP recommends offering a bandwidth of at least 100 megabits per second for this communication. The load between the application layer and the database layer is considerable. go to http://service. From the menu choose Media Library → Literature. SAP GUI for Windows and 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. Network Integration of SAP Servers.com/sizing. SD. (C) SAP AG ADM110 2-11 . mySAP BI. SAP GUI for Windows. and so on) Type of application (within SAP R/3 Enterprise: FI. 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. For more information on network layout for SAP servers. It is usually not possible to separate the database by more than LAN width from the application layer. go to http://intranet.com/network and display or download the document. HR.

sap. you have to ensure that data loss is avoided under almost all circumstances. The next slide provides some recommendations concerning the disk layout. transaction data and so on) and corresponding index data Logging data for the database (needed for recovery) Configuration data for the database Databases of SAP systems are usually stored on disks combined to some RAID level (usually 1 or 5) resides on RAID array of several physical disks For recommendations of disk layout. flood. To ensure maximum availability of your system.Database: Disk Layout and High Availability Databases of SAP systems hold different types of data: Business data (master data. earthquake. but also reliability and availability. and so on) For more information on these issues.com/ha. The disk layout for databases used for SAP systems affects not only system performance. 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. see next page © SAP AG 2003 Databases used for SAP systems can hold up to several terabytes of business data. (C) SAP AG ADM110 2-12 . go to http://service. Because you are practically not able to restore such a large database.

as shown: Business data and index data RAID 5 Current logging data RAID 1 Database configuration data RAID 1 © SAP AG 2003 Using the configuration shown above. If costs are not a factor. You should not store the historical log files of your database on any of the arrays listed in the figure. operating system and /or database vendor.sap. For these options. (C) SAP AG ADM110 2-13 .com/ha and by contacting your hardware. instead. higher-performing configurations are possible. 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). you can inform yourself at http://service. availability and performance. you get an optimum of hardware costs.Recommendations on Database Disk Layout Separate the following database data physically.

Some system IDs are reserved for SAP use only: ADD FOR OFF SQL ALL GID OMS SYS AND IBM RAW TMP ANY INT ROW UID ASC KEY SAP USR COM LOG SET VAR DBA MON SGA END NIX SHG EPS NOT SID Note: The set of reserved names may differ between different database and operating system combinations © SAP AG 2003 The ID for your SAP system (<SAPSID> or SID) and for your database system (<DBSID>) must be unique throughout your organization.SAP System Installation: SID Your SAP system ID (SID) and your database system ID must be unique. Database management systems can host more than one database (exception: when MCOD is used). The ID must consist of three alphanumeric characters. (C) SAP AG ADM110 2-14 . The first character must be a letter. The system ID must consist of three alphanumeric characters. Only uppercase letters are allowed. subsequent characters may be digits. The following system IDs are reserved for SAP use and cannot be used: ADD IBM SAP ALL INT SET AND KEY SGA ANY LOG SHG ASC MON SID COM NIX SQL DBA NOT SYS END OFF TMP EPS OMS UID FOR RAW USR GID ROW VAR The database of the SAP system should have the same name as the SAP system it belongs to.

There are critical differences in the naming conventions. For example. Therefore. using the higher security settings. SUPERDBA SYSTEM. you need the following database users: SAP DB: Oracle (9. SAP Note 495433 explains that the default password. tstadm. for example. SYS <sid>adm SAP<SID> SAPService<SID> db2<dbSID> <sid>adm and see Installation Guide <sid>OFR informix sapr3 © SAP AG 2003 Important: Read the installation guide and the related notes carefully. SAPServiceTST. must be entered as SAPOFR. password entries become case sensitive. for example. whereas the user SAPService<SID> must be named with uppercase <SID>. (C) SAP AG ADM110 2-15 . for Microsoft SQL Server the user <sid>adm must be named with lowercase <sid>.20): Microsoft SQL Server: DB2 UDB: DB2 (zOS): DB2 (iSeries): Informix: SAP<SID> SAP<SID> Control. When higher security settings are used on iSeries machines.Database Users for SAP Systems Depending on the database you use.

Choose SAP Web Application Server → Release 6.20 (on new hardware) Linux SAP DB 7.3 (on new hardware) EXAMPLE! Dispatcher heterogeneous HP-UX Oracle 9. print or download SAP Web AS Homogeneous and Heterogeneous System Copy.sap.com/osdbmigration and http://service.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 Dispatcher homogeneous HP-UX Oracle 9.com/instguides. For more information. (C) SAP AG ADM110 2-16 .20 and display. go to http://service.20 Dispatcher © SAP AG 2003 You can choose between two installation variants for your system: a new installation or a homogeneous or heterogeneous system copy.20 Dispatcher HP-UX Oracle 9.sap.

/ti. /ha.Further Information SAP Service Marketplace http://service. /network. /performance. /instguides.sap.com: Quick Links: /sizing. /platforms. /osdbmigration SAP Notes as listed in this unit © SAP AG 2003 (C) SAP AG ADM110 2-17 . /unicode.

Installation Planning: Unit Summary Now you are able to: List the requirements for an installation of SAP R/3 Enterprise Explain some technical choices to be made © SAP AG 2003 (C) SAP AG ADM110 2-18 .

New Features Installation Planning Installation Preparation Installing SAP GUI Installation Process Post-Installation Activities Implementing Patches Converting Non-Unicode to Unicode Troubleshooting Installation Problems (C) SAP AG ADM110 3-1 .Installation Preparation 1 2 3 4 5 6 7 8 9 © SAP AG 2003 SAP R/3 Enterprise Architecture.

Content and Objectives Content: General Preparation Steps Further Preparation Steps under Windows Further Preparation Steps under UNIX Objectives: At the conclusion of this unit. you will be able to: Perform the necessary preparations for the installation of SAP R/3 Enterprise © SAP AG 2003 (C) SAP AG ADM110 3-2 .

Installation Preparation General Preparation Steps Further Preparation Steps under Windows Further Preparation Steps under UNIX © SAP AG 2003 (C) SAP AG ADM110 3-3 .

Order Installation CDs http://service.com/installations © SAP AG 2003 (C) SAP AG ADM110 3-4 .com/swcat Or download CDs at http://service.sap.sap.

Download of Installation Guides http://service. Have the installation guide ready during the installation to follow each successive step of the procedure.sap. 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.com/instguides © SAP AG 2003 For each installation.sap. (C) SAP AG ADM110 3-5 .com/instguides). You should print out the installation guide and read it carefully before starting the installation process.

SAP DB 523503 .7 Inst.7 under Windows .INST: SAP Web AS 6. under UNIX . under UNIX .SAP R/3 Enterprise 4.OS Dependencies 523505 .SAP DB 533728 . if you install an SAP R/3 Enterprise system under Windows and SAP DB you should download SAP Notes 534334.7 Inst. For example.7 Inst.INST:SAP R/3 Enterprise 4.7 under Windows.INST:SAP R/3 Enterprise 4.SAP R/3 Enterprise 4.7 under Windows.7 under Windows: Oracle 529118 .INST: SAP R/3 Enterprise 4.SAP Software on UNIX .20 on Windows . Print out the relevant SAP Notes and read them carefully before beginning to install so you can avoid known problems.SAP R/3 Enterprise Installation under Windows General 529076 .MS Cluster 529150 . under UNIX . Have the relevant SAP Notes at hand during the installation so you can quickly solve potentially occurring problems.IBM DB2 UDB for UNIX and Windows © SAP AG 2003 Download the SAP Notes relevant for your specific installation. 496251 and 531372.INST: SAP R/3 Enterprise 4.Informix 531372 .7 Inst.MS SQL Server 531349 .INST: SAP R/3 Enterprise 4.INST: SAP R/3 Enterprise 4. under UNIX . under Windows 2000 .INST: SAP R/3 Enterprise 4.7 Inst.SAP R/3 Enterprise Installation under UNIX 523502 . 529151.INST: SAP R/3 Enterprise 4.Composite SAP note Installation/Upgrade SAP R/3 492222 . (C) SAP AG ADM110 3-6 . You should also download the SAP Notes mentioned in your installation guide.7 under Windows .IBM DB2 UDB for UNIX and Windows 533715 .General 529151 .Informix 523504 .Download Relevant SAP Notes! • • • • • • • • • • • • • • • 534334 .Oracle 496251 .

For more information on installing the front-end software. refer to Unit 4." of this course and the separate documentation: SAP FrontEnd Installation Guide (English version) SAP Frontend-Installationsleitfaden (German version) (C) SAP AG ADM110 3-7 .Install SAP Front-End Software SAP GUI SAP GUI SAP GUI SAP GUI SAP GUI on at least one host machine (host of central instance) © SAP AG 2003 Make sure that the front-end software is installed on at least one host machine in your system environment. we recommend that you do this on the central instance host. To simplify administration of your SAP system. “Installing SAP GUI.

You can copy an entire CD during the installation by using the SAPinst dialog CD Browser. 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. Make sure you have sufficient CD drives or copy the CDs to hard disks. (C) SAP AG ADM110 3-8 .Prepare Installation CDs share / mount CDs or copy to disk © SAP AG 2003 The CDs you need for the installation are listed in the installation guide in the section "Preparing required CDs. The EXPORT CDs (1-7) must be available in parallel anyway." 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. SAPinst wants to have all directory names and files in upper cases. SAPinst will copy the CD to the path you entered in the Copy Package to column.

Installation Preparation General Preparation Steps Further Preparation Steps under Windows Further Preparation Steps under UNIX © SAP AG 2003 (C) SAP AG ADM110 3-9 .

For performance and security reasons.Select the root directory. If you want to use the Change and Transport System to move objects between different SAP systems (that is. (C) SAP AG ADM110 3-10 . .Open Windows Explorer. This is valid for all SAP system setups. Only SAP application and database servers (no other software) should be members of these domains.Windows File System: NTFS You must use NTFS for an SAP system installation.Choose Properties. for example. no SAP instance (and no database instance) should run on the domain controller. © SAP AG 2003 An SAP system must be installed on an NTFS file system. G:. SAP systems with different SAPSIDs). . SAP recommends that all SAP system and database hosts are members of a single Windows domain.Switch to the General tab to see the type of file system that is in use. 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. Do not install the SAP directories on a FAT partition. Check the partition on which you plan to install the SAP system for the correct file system. the SAP system and the user accounts are included in a single domain. . whether standalone central systems or distributed systems. Follow this procedure to check the file system of the installation partition: . In this single domain model.

exe program.Windows NT: Update Dynamic Link Libraries SAP Kernel CD r3dllins. you are prompted to reboot the system to activate the changes. (C) SAP AG ADM110 3-11 . It does not have to be done for Windows 2000. Switch to the directory <CD_DRIVE>:\NT\I386\NTPATCH. Start the program r3dllins. If your DLLs were already up-to-date before you started the r3dllins. 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.exe.exe Windows NT For Windows NT only! © SAP AG 2003 This step is necessary for Windows NT only. no new DLLs are installed and you are not prompted to reboot. When the installation has finished.

especially for the database import.Windows: Reducing Size of File Cache Start Settings (Control Panel Network and Dial-Up Connections Local Area Connections ) © SAP AG 2003 When the option Maximize data throughput for network applications is selected among other settings. (C) SAP AG ADM110 3-12 . This also decreases the time needed for the installation. the Windows file cache is reduced in size so application server software such as an SAP system has more resources available.

To check this setting. you need a user with administration rights. choose Account Policies → Password Policy.Windows: User for Installation Installation user needs administration rights! Set minimum password lenght="0" © SAP AG 2003 For the installation. For a local installation. To check if your user is a member of the Adminstrators group. Set the minimum user password length to 0. choose Start → Settings → ControlPanel → Administrative Tools → Computer Management and select the folder Local Users and Groups → Users. In the following window. If this is a domain installation. your user needs domain administration rights. To set the Minimum password length. (C) SAP AG ADM110 3-13 . double-click on the entry. for a domain installation. your user needs local administration rights. Double-click on your user and switch to the Member Of tab. you should perform this check on the domain controller. Reset the password length to the original value after you have finished the installation. choose Start → Settings → ControlPanel → Administrative Tools → Local Security Policy.

map the IP address of the transport host to the alias SAPTRANSHOST. you can map the IP address to the alias SAPTRANSHOST in the hosts file. If no DNS server is available.Windows: SAP System Transport Host Get IP address of host Edit hosts file on each host © SAP AG 2003 You need to prepare one host in the SAP system for the role of transport host. a test or development system). This host has the function of controlling the import or export of files between the current SAP system and other SAP systems (for example. Find out the IP address of the host by using the command ping <host_name> (pay attention if DHCP is enabled). .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. If you experience problems with the alias SAPTRANSHOST in UNC paths (\\<hostname>). (C) SAP AG ADM110 3-14 . . Follow this procedure to map the IP address to the alias (no DNS server).Copy the newly edited hosts file to all hosts where an SAP instance is to run. refer to SAP Note 360515. If a DNS server is available for your system. .Go to <Drive>:\WINNT\system32\drivers\etc.

the Java Software Development Kit (abbreviated as SDK or JDK) must be installed on all hosts where SAPinst will run. some preparations are necessary.sap.Windows: Preparing SAPinst Installation 1. Add %JAVA_HOME%\bin to your system path. the System Landscape Implementation Manager. The steps in the figure are described in detail on the following pages. Java-based installation tool SAPinst © SAP AG 2003 Before installing SAPinst.20. some rework is mandatory. After installing the Java SDK.com/platforms. Because SAPinst is a Java-based tool. You can find the released JDK versions in the SAP Service Marketplace at http://service. Install Java Development Kit on every host on which you want to run SAPinst 2. (C) SAP AG ADM110 3-15 . Clean up the JDK \ext directory 3. Choose Availablility of SAP components in Detail → SAP Web AS / Basis / Kernel → OS/DB/JDK releases for SAP Web AS 6. Set the JAVA_HOME environment variable 4.

you can check under Start → Settings → ControlPanel → Add/Remove Programs." 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! (C) SAP AG ADM110 3-16 ..Windows: Java SDK Installation (1/2) 1 2 3 4 © SAP AG 2003 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. The software is present if there is an entry for "Java 2 SDK Standard Edition.

If you find any . for example.jar files. xerces. This is only possible if the application to which the JAR files belong is not running during the installation.Windows: Java SDK Installation (2/2) 5 6 7 8 © SAP AG 2003 After the successful installation. for example xerces. do the following: Rename them to. Remember to rename the files back to their original names after the installation procedure is complete.jar. check the Java \ext directory to see if there are already <parser_name>. The default path is <JAVA_HOME>\JRE\lib\ext.jar files. (C) SAP AG ADM110 3-17 .xxx.

Windows: Environment Variable JAVA_HOME (1/2) © SAP AG 2003 SAPinst needs the JAVA_HOME environment variable to be set on the host(s) where SAPinst will run. Set Variable Name to JAVA_HOME. Check if the system variable JAVA_HOME is set to the Java home directory (the directory in which the JDK is installed).1_07. for example.3. choose Start → Settings → ControlPanel → System and switch to the Advanced tab. Then click on Environment Variables. Click OK The JAVA_HOME variable is now present in the system variables list (see next slide). To check the JAVA_HOME environment variable. (C) SAP AG ADM110 3-18 . Follow this procedure to create a new variable: Choose New. create a new variable. C:\jdk1. If it is not set. Set Variable Value to the Java home directory.

Choose Edit.Enter %JAVA_HOME%\bin at the end of the Variable Value field. you have to add the Java home directory to the Path variable.Click OK. . Use a semicolon (. Follow this procedure to add the Java home directory to the Path variable: .) to separate the entry from the previous entry! . .Windows: Environment Variable JAVA_HOME (2/2) © SAP AG 2003 After setting the JAVA_HOME variable.Click Path entry in the list of system variables. (C) SAP AG ADM110 3-19 .

Installation Preparation

General Preparation Steps Further Preparation Steps under Windows

Further Preparation Steps under UNIX

© SAP AG 2003

(C) SAP AG

ADM110

3-20

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"

© SAP AG 2003

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.

(C) SAP AG

ADM110

3-21

UNIX: Setting Up File Systems

usr sap <sapsid> SYS exe profile global dgb opt run sapmnt
xxx
File system you have to set up manually symbolic link
© SAP AG 2003

...

<sapsid>

trans <Instance name> log data work

<SID> exe profile global

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.

(C) SAP AG

ADM110

3-22

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 set to <host_name>:0.0

Java based installation tool SAPinst

© SAP AG 2003

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.

(C) SAP AG

ADM110

3-23

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

© SAP AG 2003

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)

(C) SAP AG

ADM110

3-24

Preparation Checklist for Windows

Installation guide downloaded and printed out SAP Notes downloaded and printed out Installation guide and SAP Notes read SAP Front End available CDs available (copied to disk / in CD drive) File system is NTFS WIN NT only: Dynamic link libraries updated Size of file cache reduced User has admin rights / min. passw. length=0 SAPTRANSHOST set JDK installed Java \ext directory cleaned up JAVA_HOME set
© SAP AG 2003

(C) SAP AG

ADM110

3-25

Preparation Checklist for UNIX Installation guide downloaded and printed out SAP Notes downloaded and printed out Installation guide and SAP Notes read SAP Front End available CDs available (copied to disk / in CD drive) OPT.: Users created kernel parameters checked / set File system setup JDK installed JAVA_HOME set DISPLAY set Java /ext directory cleaned up © SAP AG 2003 (C) SAP AG ADM110 3-26 .

Further Information SAP Service Marketplace http://service.com: Quick Links /platforms.sap. /instguides © SAP AG 2003 (C) SAP AG ADM110 3-27 .

Installation Preparation: Unit Summary Now you are able to: Perform the necessary preparations for the installation of SAP R/3 Enterprise © SAP AG 2003 (C) SAP AG ADM110 3-28 .

3-2-1 Check if the file system of the installation partition (G:) is NTFS. You find the installation CDs under G:\SETUP. Language_1. change it to 0. and password given to you by your instructor. Presentation. SAP_J2EE_Engine. 3-2 Check and/or adjust necessary operating system settings and prepare the SAP system transport host.Exercises Unit 3: Installation Preparation At the conclusion of this exercise. 3-3 Prepare the SAPinst installation by installing the Java 2 SDK and setting the JAVA_HOME environment variable. The following CDs should be there: Export_1 to _7. 3-2-3 Check if your user has administration rights. Note: Use pcAnywhere to connect to your host. Kernel. If not. (C) SAP AG ADM110 3-29 . 3-1 Check if the installation CDs are available. 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-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. 3-2-2 Reduce the size of the Windows file cache by editing the properties of the local area connection. user name. use the host name. 3-2-4 Check if the minimum password length is set to 0. SAPINST. Server_Comp_1 and _2. RDBMS_SAP_DB. 3-1-1 To log on to your host. 3-2-5 Prepare your host to be the SAP system transport host.

3-1-1 To log on to your host use the host name. SAP_J2EE_Engine. 3-1 Check if the installation CDs are available. The following CDs should be there: Export_1 to _7. Presentation. 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-2-3 Check if your user has administration rights. user name and password given to you by your instructor. Follow the directions given on slide and notes to slide "Windows: User for Installation." 3-2-2 Reduce the size of the Windows file cache by editing the properties of the local area connection.Installation Preparation Solutions Unit 3: Installation Preparation At the conclusion of this exercise. Follow the exercise description. Note: Use pcAnywhere to connect to your host. Follow the directions given on slide and notes to slide "Windows File System: NTFS. Language_1. change it to 0. Follow the directions given on slide "Windows: Reducing Size of File Cache. 3-2 Check and/or adjust necessary operating system settings and prepare the SAP system transport host. Follow the directions given on slide and notes to slide "Windows: User for Installation. RDBMS_SAP_DB. If not." (C) SAP AG ADM110 3-30 . Server_Comp_1 and _2. 3-2-1 Check if the file system of the installation partition (G:) is NTFS. You find the installation CDs under G:\SETUP. Kernel." 3-2-4 Check if the minimum password length is set to 0. SAPINST.

3-3-1 Install the Java 2 SDK. Go to G:\SETUP\ADM110\J2SDK and double-click on the j2sdk-1_3_1_07windows-i586. you can refer to the slides "Windows: Java SDK Installation" (two slides). Follow the directions given on slide "Windows: Environment Variable JAVA_HOME (1/2)." (C) SAP AG ADM110 3-31 . 3-3-2 Set the JAVA_HOME environment variable to the just installed Java Home directory. 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. As a help. Follow the directions given on slide "Windows: Environment Variable JAVA_HOME (2/2).3-2-5 Prepare your host to be the SAP system transport host." 3-3-3 Add the Java home directory to the Path environment variable.exe file.

New Features Installation Planning Installation Preparation Installing SAP GUI Installation Process Post-Installation Activities Implementing Patches Converting Non-Unicode to Unicode Troubleshooting Installation Problems (C) SAP AG ADM110 4-1 .Installing SAP GUI 1 2 3 4 5 6 7 8 9 © SAP AG 2003 SAP R/3 Enterprise Architecture.

you will be able to: Prepare and execute an installation of SAP GUI for Windows © SAP AG 2003 (C) SAP AG ADM110 4-2 .Content and Objectives Content: Installation of SAP GUI for Windows (local/Server) Patching SAP GUI for Windows Installation of SAP GUI for Java Objectives: At the conclusion of this unit.

for example. and more. This protocol requires a very small bandwidth.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.com/ui. You will find more SAP GUI related information on http://service. with one instance of an SAP system). ITS170 and ADM102. (C) SAP AG ADM110 4-3 .Variants of SAP GUI HTML SAP ITS SAP GUI for SAP GUI for HTML HTML WebServer Common Server CGI* WGate TCP/IP AGate DIAG / RFC Dispatcher DIAG / RFC SAP GUI for SAP GUI for Java Java DIAG / RFC SAP GUI for SAP GUI for Windows Windows © SAP AG 2003 More information on http://service.sap.sap. not covered here: portal interfaces (such as iViews). Business Explorer (BEx) for accessing SAP BW systems. The use and implementation of the SAP ITS is covered in other courses. 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. thus reducing network load. SAP GUI for HTML requires the SAP Internet Transaction Server (SAP ITS) for providing access to an SAP system.

exe in \GUI\Windows\Win32 on the Presentation CD Follow the screenshots given here © SAP AG 2003 The next slides describe the local installation of SAP GUI for Windows. (C) SAP AG ADM110 4-4 . 2.Local Installation SAP GUI for Windows (1/3) Follow these steps for a local installation SAP GUI for Windows: 1. Start setup.

Local Installation SAP GUI for Windows (2/3) Select the installation directory © SAP AG 2003 Select the installation directory for the local installation of the SAP GUI. (C) SAP AG ADM110 4-5 .

the installation runs and closes with the second screen shown above. (C) SAP AG ADM110 4-6 .Local Installation SAP GUI for Windows (3/3) Select front-end components to be installed © SAP AG 2003 After you select the components to be installed.

Installing an SAP GUI Installation Server (1/9)) Follow these steps: 1.pdf Follow the screenshots given here Name a shared directory © SAP AG 2003 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. as shown above. which you will find on the Presentation CD in the folder \DOCU: pc620_EN. 2. (C) SAP AG ADM110 4-7 . 3.exe in \GUI\Windows\Win32\setup on the Presentation CD Follow the instructions in the SAP Front End Installation Guide. Start admsetup. you need a shared directory. For this installation server.

Installing an SAP GUI Installation Server (2/9) Configure the Distribution Service © SAP AG 2003 Next you need to configure the distribution service. (C) SAP AG ADM110 4-8 .

Installing an SAP GUI Installation Server (3/9) Configure the Distribution Service © SAP AG 2003 This distribution service requires users (and their passwords) to be used during the remote installation. (C) SAP AG ADM110 4-9 .

Installing an SAP GUI Installation Server (4/9) Configure the Distribution Service © SAP AG 2003 After installing the distribution services. (C) SAP AG ADM110 4-10 . you must define packages of software to be distributed (as explained in the next few slides).

(C) SAP AG ADM110 4-11 .] This list of files can be ignored. […]" © SAP AG 2003 You can ignore the error message shown in the figure.. Refer to SAP Note 587533 for details..Installing an SAP GUI Installation Server (5/9) Observe SAP Note 587533 "[.

exe program.exe Create a new SAP GUI Installation package © SAP AG 2003 To set up installation packages. You can use this program to create new installation packages for SAP GUI for Windows.Installing an SAP GUI Installation Server (6/9) Double-click SapAdmin. (C) SAP AG ADM110 4-12 . you start the SapAdmin.

Installing an SAP GUI Installation Server (7/9) Select front-end components to be installed © SAP AG 2003 You need to define the components to be included in the new package. (C) SAP AG ADM110 4-13 .

During startup of the SAP GUI. you have two options for defining where the installation should reside: The local installation puts all necessary software on the front end. Because the amount of data transferred is quite high. the remaining files are transferred from the server to the front-end via the network. this option should be used in LAN environments only. leaving a footprint of up to 200 MB. In this case. whereas the first option is the first choice in WAN environments. the amount of work for updating the local installations is higher than for the second option.Installing an SAP GUI Installation Server (8/9) Use server-based installation in LAN Local Installation in WAN and on mobile front ends © SAP AG 2003 For the installation packages. (C) SAP AG ADM110 4-14 . The server-based installation leaves many files on the server and puts only essential files on the frontend computers (some a few MB in size).

The same file is used.Installing an SAP GUI Installation Server (9/9) Give the location of the SAP GUI patch file. See the next slides. see next slides © SAP AG 2003 The installation server can be updated in the similar way to a stand-alone SAP GUI. (C) SAP AG ADM110 4-15 .

sap.com/patches to your server Follow the screenshots given on the next pages SAP Logon About SAP Logon In SAP GUI: Customizing of local layout About Start sapgui –v © SAP AG 2003 On the screenshots.exe.Patching the SAP GUI (1/4) Steps to be executed: 1. This build can be patched with a later version available on the SAP Service Marketplace.exe and Front.exe. you see the versions for the primary SAP GUI components: SAPLogon. (C) SAP AG ADM110 4-16 . Download the newest SAP GUI patch from http://service. 2. SAPGUI. The patch level of the build in the example in the figure is 22.

Patching the SAP GUI (2/4) Double-click GUI-patch © SAP AG 2003 Simply start the patch application by starting the patch executable. (C) SAP AG ADM110 4-17 .

you have to restart your front-end computer because some essential . (C) SAP AG ADM110 4-18 .dlls were exchanged.Patching the SAP GUI (3/4) Restart the computer © SAP AG 2003 After applying the patch.

the new patch level of the components shown in the figure is 32.Patching the SAP GUI (4/4) Check new patch level © SAP AG 2003 After the patch is applied. (C) SAP AG ADM110 4-19 .

sap.Installing SAP GUI for Java (1/3) Double-click PlatinGUI-###. (C) SAP AG ADM110 4-20 .jar Name the installation directory © SAP AG 2003 Download the SAP GUI for Java installation (Rev 8) files from ftp://ftp.com/pub/sapgui/java/620r8 and select your platform. Start the installation by executing the downloaded file and proceed as shown in the figure.

(C) SAP AG ADM110 4-21 .htm (correct for SAP GUI for Java Rev 8).Installing SAP GUI for Java (2/3) Configure SAP GUI for Java © SAP AG 2003 You can find the configuration details for SAP GUI for Java in the documentation.20rev8\doc\manual. The documentation is installed together with the SAP GUI and can be found in the folder [Installation directory]\6.

Installing SAP GUI for Java (3/3) Check version of SAP GUI for Java © SAP AG 2003 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. (C) SAP AG ADM110 4-22 .

folder DOCU SAP Notes as listed in this unit © SAP AG 2003 (C) SAP AG ADM110 4-23 .Further Information SAP Service Marketplace.sap.com/patches and http://service. http://service.sap.com/ui Presentation CD 1.

Installing SAP GUI: Unit Summary Now you are able to: Prepare and execute an installation of SAP GUI for Windows © SAP AG 2003 (C) SAP AG ADM110 4-24 .

you will be able to: • 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. on twdf0###.. 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). 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 Optional: Install and configure SAP GUI for Java on the server you are using for the training. 4-3-1 Install the SAP GUI for the Java Environment. on twdf0###.Installing SAP GUI Exercises Unit 4: Installing SAP GUI At the conclusion of this exercise. 4-2-1 Check the current patch level of your SAP GUI components." 4-2-3 Check the new patch level of your SAP GUI components. for example. 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-1-1 Start the program setup. (C) SAP AG ADM110 4-25 . 4-2 Raise the patch level of your locally installed SAP GUI for Windows.exe from the Presentation CD folder \GUI\Windows\Win32 and use the default installation directory. for example. 4-1 Install a local SAP GUI for Windows on the server you are using for the training.

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). (C) SAP AG ADM110 4-26 . <server>)." You have to adapt the content of the configuration files to fit your system environment (<SID>.

" Follow the exercise description. Proceed as described in this training material on the pages "Patching the SAP GUI (2/4)" and "Patching the SAP GUI (3/4). Start the program setup. you will be able to: • 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-2 Raise the patch level of your locally installed SAP GUI for Windows. Follow the exercise description." 4-2-2 You find the patch to be applied in the following location: G:\SETUP\ADM110\SAP_GUI_Patch_32. 4-2-1 Check the current patch level of your SAP GUI components. 4-1-1 Start the program setup. Follow the directions given on slide "Patching the SAP GUI (1/4). for example. on twdf0###. 4-2-3 Check the new patch level of your SAP GUI components. See 4-2-1. 4-1 Install a local SAP GUI for Windows on the server you are using for the training.exe from G:\SETUP\presentation\GUI\Windows\Win32.Installing SAP GUI Solutions Unit 4: Installing SAP GUI At the conclusion of this exercise. (C) SAP AG ADM110 4-27 .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.

Proceed as described in the training material. <server>). You find the installation files in the following location: G:\SETUP\ADM110\ SAP_GUI_For_Java.4-3 Optional: Install and configure SAP GUI for Java on the server you are using for the training. Follow the exercise description. for example. 4-3-1 Install the SAP GUI for the Java Environment." You have to adapt the content of the configuration files to fit your system environment (<SID>. (C) SAP AG ADM110 4-28 . 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). Follow the exercise description. on twdf0###.

Installation Process 1 2 3 4 5 6 7 8 9 © SAP AG 2003 SAP R/3 Enterprise Architecture. New Features Installation Planning Installation Preparation Installing SAP GUI Installation Process Post-Installation Activities Implementing Patches Converting Non-Unicode to Unicode Troubleshooting Installation Problems (C) SAP AG ADM110 5-1 .

Content and Objectives Content: Central and dialog instance installation Database installation SAP J2EE Engine installation Objectives: At the conclusion of this unit. you will be able to: Install a central instance Install a database instance Install an SAPJ2EE Engine instance Install a dialog instance © SAP AG 2003 (C) SAP AG ADM110 5-2 .

Installation Process SAPinst Installation Central Instance Installation Database Instance Installation SAP J2EE Engine Installation Dialog Instance Installation Appendix: Gateway Instance Installation © SAP AG 2003 (C) SAP AG ADM110 5-3 .

The setting of the library path environment variable is required for all SAP instance installations. (See Unit 3 Installation Preparation and installation guide for more information) (C) SAP AG ADM110 5-4 . Install Java Development Kit (SDK) Set the environment variable JAVA_HOME Check SAPinst host for .The setting of the library path environment variable is required only for the central system and the database instance installation. To connect remotely to server hosts.Prerequisites for SAPinst Prerequisites to run SAPinst: Windows: Do not use Microsoft Terminal Server for any installation procedure with SAPInst.jar-files to avoid SAPinst errors © SAP AG 2003 UNIX: Non-Unicode SAP system installation: . set the library path environment variable on your installation host depending on the used shell. As user root. Unicode SAP system installation: . use applications such as Symantec pcAnywhere or VNC.

If you install an SAP system with SAPinst for the very first time on a host. (C) SAP AG ADM110 5-5 . start SAPinst from the SAPinst CD. you can use the Windows Start menu to install additional SAP or database instances on the same host.Start SAPinst Operating System: Each SAP component is installed separately: Central Instance DB Instance Dialog Instance SAP J2EE Engine Start the SAPinst for the first time from the SAPinst CD. Afterwards. Otherwise. This directory is also used as the installation directory for the instance you are installing. When you install an SAP instance with SAPinst for the very first time on your host. SAPinst is copied to the directory you have specified. UNIX: <SAPinst CD>/SAPINST/UNIX/<platform>/INSTALL Windows: <CD drive>:\SAPinst\NT\setup. make sure that you use a separate installation directory for every instance you are going to install. you have to start SAPinst from the Kernel CD with setup. you might lose previous log and command files stored in the SAPinst installation directory.cmd © SAP AG 2003 Because the SAPinst installation directory contains important log and command files for the installation.cmd.

SAPinst is copied to <SAPinst_INSTDIR> and the start menu entries are created.Start Menu Entries Use the Windows Start menu to install additional SAP or database instances on the same host Prepare new installation Remove SAPinst files SAPinst GUI SAPinst server only SAPinst server with GUI © SAP AG 2003 After the first installation of SAPinst. 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. SAPinst GUI: Use this GUI for a remote installation. Remove SAPinst files: Delete all the files in the installation directory. SAPinst Server only: Start scroll mode but wait for remote installation call. SAPinst server with GUI: Use GUI for local installation. (C) SAP AG ADM110 5-6 .

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

© SAP AG 2003

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

(C) SAP AG

ADM110

5-7

SAPinst Installation Default Parameters

Select Custom not Standard for Installation Directory
On Windows 2000, create a separate menu item Don’t overwrite other installation directories
© SAP AG 2003

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

.

(C) SAP AG

ADM110

5-8

SAPInst Installation Finished

SAPinst is successfully installed Start menu entries are made

© SAP AG 2003

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.

(C) SAP AG

ADM110

5-9

Remote Installation with SAPinst

local
Communication Port: 21212, 21213

remote
SAPServer

PC SAPinst GUI

SAPinst

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.
© SAP AG 2003

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>

(C) SAP AG

ADM110

5-10

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

© SAP AG 2003

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.

(C) SAP AG

ADM110

5-11

SAPinst Building Blocks

User input

Installation parameters

SAPinst GUI

XML Files

Control KeyDB Dialogs Messages

Server

Start CD

Package CD‘s

Modules SysLib

OS

© SAP AG 2003

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.

(C) SAP AG

ADM110

Installation archives

Packages

5-12

(C) SAP AG ADM110 5-13 . you need a Java Runtime Environment (JRE). that allows you to monitor the progress of the installation and see all messages issued by SAPinst.xml For software package administration: packages.Appendix: Preparing SAPinst Software For dialog design: dialog. it stops the installation and you can retry the installation after solving the problem. You can start SAPinst GUI on a remote computer if you want. SAPinst continues an aborted installation directly from the point of failure. Instead. you can abort the installation manually if you want.log. Alternatively. As SAPinst GUI is Java based.xml For control flow: control. SAPinst does not abort due to errors. For more information on SAPinst.xml Definitions of screens. SAPinst records installation progress in a single log file. see the documentation. sapinst. input fields.com/sapinstfeedback. and so on Fields can be activated/deactivated for input by setting the variable enabled = true/false in the respective section For persistency layer (KeyDB): keydb. SAPinst has a graphical user interface (GUI). the previous tool: SAPinst lets you step back to correct your entries during the input phase without restarting the installation.xml Contains the input values provided by the user © SAP AG 2003 SAPinst offers these main advantages compared to R3SETUP. SAPinst Troubleshooting Guide at http://service.xml Keeps track of the installation progress Contains status of each step For logging/tracing service: messages.sap. SAPinst GUI.

Appendix: SAPinst Input Files: dialog... </frame> </dialog> © SAP AG 2003 (C) SAP AG ADM110 5-14 .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> .

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.<no>. the STATUS is set to OK. and then resumes with the phase which has STATUS ERROR or “ “ (blank) © SAP AG 2003 (C) SAP AG ADM110 5-15 .xml to keydb. it first saves keydb.Appendix: SAPinst Input Files: keydb.xml. otherwise to ERROR When SAPinst is restarted after an error.xml If phase ended successful.

SAPinst components have attributes such as OS type and DB type.. When a component is referenced as a subcomponent..Appendix: SAPinst Input Files: control.xml <component name="DIALOG_INSTANCE" os-type="windows" os="ind" db="ind" product="bw" release=“30A"> . SAPinst components have parameters. (C) SAP AG ADM110 5-16 . the parent component has to provide a context table.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 © SAP AG 2003 SAPinst components are the major building blocks of an installation.. Contexts are represented as rows in a component's context table.. the set of parameters of a component makes up its context. <parameters> <parameter name="HOSTNAME" defval="p77777"> <description>This is only a test parameter</description> </parameter> <parameter name="INSTANCE_NUMBER" defval="01"> <description>.

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 environment variables or on the SAPinst command line © SAP AG 2003 (C) SAP AG ADM110 5-17 .

(C) SAP AG ADM110 5-18 . SAP recommends <DBSID><ORACLE_VERSION> Destination: Enter the path of a new Oracle Home directory. Install this patchset using the Oracle Universal Installer. sapclient.cmd Start on database server. Download it from sapserv<x> as described in SAP Note 362060. You need 2.2 GB disk space for the Oracle 9./RUNINSTALLER © SAP AG 2003 Enter the information: File locations: Do not change the path of the Oracle source software.2.0 server software and about 250 MB for the Oracle 9.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. You need only install the latest Oracle patchset. sapserver.Appendix: Oracle Software For Oracle software: Install the Oracle database software Install patch set Windows procedure: Start on database client. 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.cmd UNIX procedure: . SAP recommends <DRIVE>:\ORACLE\<DBSID>\<ORA_VERS>.2. Destination: Enter the name of the new Oracle Home directory.

modify the settings for the OS user root and users <sapsid>adm and sqd<sapsid> that were created by SAPinst. if necessary. root <sapsid>adm sqd<sapsid> © SAP AG 2003 (C) SAP AG ADM110 5-19 .Appendix: Settings for OS Users (AIX Only) Checking Settings for OS Users (AIX only) Check and.

Installation Process SAPinst Installation Central Instance Installation Database Instance Installation SAP J2EE Engine Installation Dialog Instance Installation Appendix: Gateway Instance Installation © SAP AG 2003 (C) SAP AG ADM110 5-20 .

SAPinst automatically starts the installation of your component (for example R/3 Enterprise Unicode).. If the installation does not start automatically. to perform a system copy Accept the license agreement for STLport © SAP AG 2003 After SAPinst is successfully installed. (C) SAP AG ADM110 5-21 .. choose Start → Programs → SAPinst_menu_entry → SAPinst server with GUI. To start the installation with SAPinst.. -Default to install a central. installation or export of a R/3 Enterprise Unicode system).. start it manually. First the Welcome screen displays the possible actions (for example. Accept the license agreement for STLport.Start Installation of the Central Instance Select: Unicode . dialog or DB instance Unicode Export .

there is obviously no port conflict. Instance Number Enter the system ID Select Central instance Enter an instance number Assign a value from 0 to 97 as instance number Avoid the numbers 02. for example. For Windows installations. Because the following IDs are reserved. which also use these ports. Already installed instances are not affected.Instance Installation Type. 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. do not use port 02. 72 and 89. (C) SAP AG ADM110 5-22 . The first character must be a letter (not a digit). Only uppercase letters are allowed. 25. Assign a value from 0 to 97. The number must be two digits and must be unique for this host. Port 98 and 99 are reserved for SAProuter. 25. If an instance works properly. or 89 because they might be used by other programs © SAP AG 2003 SAP system ID: Enter the SAP system <SAPSID>. C11. you cannot assign them to your SAP system: . SAPinst does not check for occupied ports during the installation. Instance number: Enter the instance number of the central instance. Windows Terminal Server Manager). 72. The reason is that there are known problems with other applications (for example.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. SID.

To find out the host name. enter hostname at the command prompt of the database host. (C) SAP AG ADM110 5-23 . However it is possible to use a database instance ID that is different from the SAP system ID. SAP recommends that you use the same IDs for the database system and the SAP system.Database Parameters Enter the database system ID Recommendation: Use the same IDs for database system and SAP system Enter the database host © SAP AG 2003 Enter the ID of the database instance <DBSID>.

Reserve some RAM for the database instance and SAP J2EE Engine. use the following information. Domain information for the SAP system accounts: . If the system is to be distributed across more than one machine. (C) SAP AG ADM110 5-24 . Be sure to reserve at least the minimum values required for the instance (at least 256 MB for a non-unicode SAP system. the user information is stored centrally on the domain controller and is accessible from all hosts in the system.Installation in the domain of the current user In a domain installation. Perform a local installation for an SAP system to run on a single host (for a distributed system authorization problems can occure). SAP strongly recommends a domain installation. For installations on the Windows operating system. .Local installation: All Windows account and user information is stored locally. 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).Windows Domain Information and RAM Windows only: Domain information for SAP system user account on operating system Select RAM quantity © SAP AG 2003 Random Access Memory (RAM) and swap space for the central instance: The default value is the entire RAM or swap space.Installation in a different domain . at least 384 MB for a unicode SAP system).

To enable an SAP system to make use of the features offered by the Active Directory. The Active Directory is a feature of Windows 2000 and is automatically available on all domain controllers. you can configure the SAP system to use this feature. a configured SAP system can read information from the directory and also can store information there. you must configure both the Active Directory and the SAP system. For example. You must decide whether you want to use Active Directory before the installation because it influences the installation process.LDAP (Unicode Installation Only) Select No LDAP if you do not want to use an LDAP service © SAP AG 2003 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. Both the LDAP directory and the SAP system must be configured. Generic LDAP Directories Select this option to configure the system to support LDAP directories that are running on Windows or UNIX machines. If an LDAP directory is available in the corporate network. The process of preparing the SAP system for using generic LDAP services involves a number of manual steps. Active Directory: Select this option to integrate Windows 2000 Active Directory services. (C) SAP AG ADM110 5-25 . No LDAP: Select this option if you do not want to use LDAP at all.

you cannot select the local instance directories.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 © SAP AG 2003 Windows: Drive for SAP system Select the drive for the SAP base directory tree. (C) SAP AG ADM110 5-26 . the directory \usr\sap\ is created under drive D. That is. the system creates the directory /sapmnt/<SAPSID> . 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. If saploc already exists. if you enter '/sapmnt'. if you select 'D'. For example. Host with transport directory: Here you must enter the name of the host where the central transport directory is located.

SAP system service administrator: Enter and confirm the password for the SAP system administrator SAPService<sapsid>. (C) SAP AG ADM110 5-27 .Set Passwords for Operating System User Enter and confirm: Password for <SID>adm Password for SAPService<SID> © SAP AG 2003 System administrator <sapsid>adm: Enter and confirm the password for the SAP system administrator <sapsid>adm.

SAPinst first checks and finally verifies the availability and location of the required installation CDs. (C) SAP AG ADM110 5-28 .CD Browser and Message Server Port Select location of Kernel CD Enter the Message server port Enter the port number. asking for the LABEL. SAPinst does this by displaying the CD Browser window. 36<##> ##: instance number of central instance © SAP AG 2003 During the installation procedure. Message port: Enter the port number for the message server. The port number must be identical for all instances belonging to the same SAP system.ASC file that contains information about the software package to be installed. The default value is 36## where ## stands for the instance number of the central instance. You can recognize this situation by the Check Location flag displayed in the CD Browser window. SAPinst checks the availability of the software package.

CD Browser: RDBMS CD Select: Location of RDBMS CD © SAP AG 2003 (C) SAP AG ADM110 5-29 .

Installation Steps SAPinst displays the progress of the installation by highlighting the currently active installation phase © SAP AG 2003 (C) SAP AG ADM110 5-30 .

Finish Central Instance Installation © SAP AG 2003 (C) SAP AG ADM110 5-31 .

Installation Process SAPinst Installation Central Instance Installation Database Instance Installation SAP J2EE Engine Installation Dialog Instance Installation Appendix: Gateway Instance Installation © SAP AG 2003 (C) SAP AG ADM110 5-32 .

Prepare new installation 2.Preparation for Database Instance Installation SAPinst: 1. SAPinst Server with GUI (to start SAPinst) © SAP AG 2003 It is also possible to start SAPinst from the SAPINST CD with the command SETUP. (C) SAP AG ADM110 5-33 . SAPinst will be reinstalled and you can select a new installation directory.CMD on Windows and INSTALL on UNIX.

71 for SAP DB – Default to perform the installation of the DB instance Accept the license agreement for STLport © SAP AG 2003 (C) SAP AG ADM110 5-34 .Start of Database Instance Installation Select: Unicode SAP R/3 Enterprise 4.

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 (C) SAP AG ADM110 5-35 .

select Install (first) SAP system into a new database. .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 © SAP AG 2003 Follow this procedure to install the database instance: If you want to copy or migrate an existing SAP system. If you select System Copy/Migration. Otherwise. you must do the following: . 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.Refer to SAP Note 516246 for the latest information for homogeneous and heterogeneous system copy. select System Copy/Migration (for more information.Enter the migration key if you want to import the database dump of another SAP system as part of a heterogeneous SAP system copy. SAP Web Application Server Homogeneous and Heterogeneous System Copy).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. choose Standard Installation. see the documentation. . In all other cases. (C) SAP AG ADM110 5-36 .

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 © SAP AG 2003 Enter exactly the same ID of the database instance <DBSID> that you entered during the central instance installation. (C) SAP AG ADM110 5-37 . Enter exactly the same central instance number that you entered during the central instance installation. The value <##> is the number assigned to the central instance. To find out the number. Enter exactly the same name of the central instance host that you entered during the central instance installation. look under the SAP directory \usr\sap\<SAPSID>\DVEBMGS<##>.

Windows Domain Information and RAM Windows only: Domain information for SAP system user account on operating system Select RAM quantity © SAP AG 2003 (C) SAP AG ADM110 5-38 .

(C) SAP AG ADM110 5-39 .Instance Directory and Transport Host Enter: Name of the host where the central transport directory \usr\sap\trans is located © SAP AG 2003 In the Host with transport directory field. enter the name of the host where the central transport directory is located.

The password can be different from SAPService<SID> on the central instance. (C) SAP AG ADM110 5-40 . 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>.Set Passwords for Operating System User Enter and confirm: Password for <sapsid>adm Password for SAPService<SID> © SAP AG 2003 System Administrator <sid>adm: Enter and confirm the password for the SAP system administrator.

RDBMS and Export CD Select: Location of Kernel CD Location of RDBMS CD Location of Export 1 CD © SAP AG 2003 (C) SAP AG ADM110 5-41 .CD Browser: Kernel.

(C) SAP AG ADM110 5-42 .Installation Directory: Database Client Software Select drive for database client software © SAP AG 2003 Select the disk drive on which you want to install the database client software.

enter the number of workprocesses accordingly. this causes performance overhead. Single – Logs are written but not mirrored. In the Max CPU field. enter the number of physical CPUs on your system that can be used by the database.Database Parameters and Operation Mode Select: Database log mode Number of work processes CPU RAM © SAP AG 2003 These instructions are valid for an SAPDB installation only: Select a database logging mode: Demo – Logs are overwritten and insecure. (C) SAP AG ADM110 5-43 . Dual – Logs are written and mirrored. Number of work processes: If you have additional dialog instances. This is recommended in combination with hardware mirroring.

You must enter at least one LOG devspace. The sum of the LOG devspaces that you specify must exceed minimum LOG size in MB. Unicode Select: Location and size of LOG devspace Select: Location and size of DATA devspace © SAP AG 2003 Enter a size for the LOG devspace. The sum of the DATA devspaces that you specify must exceed minimum DATA size in MB. enter the drive. You must enter at least one DATA devspace.LOG and DATA Devspace Settings. (C) SAP AG ADM110 5-44 . The maximum size depends on the operating system. If you are mirroring the devspace (dual mode).

LOG and DATA Devspace Settings. Non-Unicode Select: Location and size of LOG devspace Select: Location and size of DATA devspace © SAP AG 2003 (C) SAP AG ADM110 5-45 .

Unicode Select: Location and size of SYSTEM devspace © SAP AG 2003 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.SYSTEM Devspace Settings. (C) SAP AG ADM110 5-46 .

Non-Unicode Select: Location and size of SYSTEM devspace © SAP AG 2003 (C) SAP AG ADM110 5-47 .SYSTEM Devspace Settings.

Export 4 CD.CD Browser: Export CDs Select: Location of Export 2 CD. and so on © SAP AG 2003 (C) SAP AG ADM110 5-48 . Export 3 CD.

SAP recommends that you enter the number of processors of the server. For the Number of parallel jobs. Select your DB code page. SAP recommends that you use the default settings if possible. Advanced database configuration should be performed by certified database administrators only. (C) SAP AG ADM110 5-49 . Select how many parallel jobs you want to run.Database Load Parameters. Unicode Select: Default settings © SAP AG 2003 Select how you want to load packages.

Database Load Parameters. Non-Unicode Select: Default settings © SAP AG 2003 (C) SAP AG ADM110 5-50 .

Then. (C) SAP AG ADM110 5-51 . If you do not want to install Multi National Language Support (MNLS). select MNLS Support required. 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.Multi National Language Support (Non-Unicode) © SAP AG 2003 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. select No MNLS Support required. If you want to install Multi National Language Support (MNLS).

Installation Steps SAPinst displays the progress of the installation by highlighting the currently active installation phase © SAP AG 2003 (C) SAP AG ADM110 5-52 .

Logfile sapinst.log © SAP AG 2003 (C) SAP AG ADM110 5-53 .

Prepare Multi National Language Support (NonUnicode) © SAP AG 2003 To prepare for multi national language support. (C) SAP AG ADM110 5-54 . which is attached to SAP Note 73606.pdf file. use the R3_languages.

The default password for user SAP* in client 000 will be changed.Change Passwords of ABAP Super Users Enter: Password of ABAP super user DDIC Password of ABAP super user SAP* © SAP AG 2003 Enter and confirm a new password for user DDIC. Enter and confirm a new password for user SAP*. The default password for user DDIC in client 000 will be changed. (C) SAP AG ADM110 5-55 .

Finish Installation of Database Instance © SAP AG 2003 (C) SAP AG ADM110 5-56 .

Installation Process SAPinst Installation Central Instance Installation Database Instance Installation SAP J2EE Engine Installation Dialog Instance Installation Appendix: Gateway Instance Installation © SAP AG 2003 (C) SAP AG ADM110 5-57 .

70.SAP J2EE Engine SAP Web AS 6.20. To use the system resources of your production environment in an optimal way. SAP R/3 Enterprise and SAP J2EE Engine: The SAP J2EE Engine is not required for SAP R/3 Enterprise 4. you can install it as described in SAP Note 545422. © SAP AG 2003 The SAP J2EE Engine is not required for SAP R/3 Enterprise 4. Nevertheless.70.70. if you require the SAP J2EE Engine.20 and SAP J2EE Engine: SAP J2EE Engine is implemented automatically during installation of SAP Web Application Server 6. SAP J2EE Engine is not installed automatically with SAP R/3 Enterprise 4. the SAP J2EE Engine is therefore not installed automatically with SAP R/3 Enterprise 4.70. (C) SAP AG ADM110 5-58 .

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

(C) SAP AG

ADM110

5-59

Preparation SAP J2EE Engine Installation (2/2)

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

© SAP AG 2003

(C) SAP AG

ADM110

5-60

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.

Accept the license agreement for STLport

© SAP AG 2003

(C) SAP AG

ADM110

5-61

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.
© SAP AG 2003

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

(C) SAP AG

ADM110

5-62

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
© SAP AG 2003

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.

(C) SAP AG

ADM110

5-63

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.
© SAP AG 2003

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.

(C) SAP AG

ADM110

5-64

Finish Installation of SAP J2EE Engine © SAP AG 2003 (C) SAP AG ADM110 5-65 .

Installation Process SAPinst Installation Central Instance Installation Database Instance Installation SAP J2EE Engine Installation Dialog Instance Installation Appendix: Gateway Instance Installation © SAP AG 2003 (C) SAP AG ADM110 5-66 .

<sapmnt>/<SAPSID>/global Log on to the dialog instance host as user root. SAPinst will be reinstalled and you can select a new installation directory. Check whether the dialog instance host has write access to the directories exe. 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. 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. <sapmnt>/<SAPSID>/global and mount these directories. sapmnt>/<SAPSID>/profile. profile and global: touch <sapmnt>/<SAPSID>/exe/nfs_test and rm <sapmnt>/<SAPSID>/exe/nfs_test (C) SAP AG ADM110 5-67 .CMD on Windows and INSTALL on UNIX.Preparation for Dialog Instance Installation SAPinst: 1. <sapmnt>/<SAPSID>/profile. SAPinst server with GUI (to start SAPinst) © SAP AG 2003 It is also possible to start SAPinst from SAPINST CD with the command SETUP. For a Dialog Instance only (UNIX): Mount directories from the central instance. Prepare new installation 2. Create the mount points with permissions 777: <sapmnt>/<SAPSID>/exe.

71 Dialog Instance – Java if you want to install a dialog instance with SAP J2EE Engine.Start Dialog Instance Installation Select: Unicode SAP R/3 Enterprise 4. Accept the license agreement for STLport © SAP AG 2003 (C) SAP AG ADM110 5-68 .

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. Instance Number Enter system ID Select Dialog instance Enter an instance number If the dialog instance is installed on the same host as the central instance. both instances must be assigned different numbers. enter an instance number that is different from the central instance number © SAP AG 2003 Enter exactly the same name of the SAP system <SAPSID> that you entered during the central instance installation. (C) SAP AG ADM110 5-69 .Instance Installation Type. SID.

To find out the number. Enter exactly the same name of the database instance host that you entered during the central instance installation. To find out the host name. (C) SAP AG ADM110 5-70 . Enter exactly the same name of the central instance host that you entered during the central instance installation. Enter exactly the same name of the database instance <DBSID> that you entered during the central instance installation. enter hostname at the command prompt of the central instance host. The value <##> is the number assigned to the central instance.Central Instance and Database Parameters Enter: Central instance number Central instance host Database system ID Database host © SAP AG 2003 Enter exactly the same instance number of the central instance. look under the SAP directory <DRIVE>:\usr\sap\<SAPSID>\DVEBMGS<##>.

Windows Domain Information and RAM

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

Select RAM quantity
© SAP AG 2003

(C) SAP AG

ADM110

5-71

Instance Directory and Transport Host

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

© SAP AG 2003

(C) SAP AG

ADM110

5-72

Set Passwords for Operating System User

Enter and confirm:
Password for <sapsid>adm Password for SAPService<SID>

© SAP AG 2003

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.

(C) SAP AG

ADM110

5-73

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

© SAP AG 2003

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

(C) SAP AG

ADM110

5-74

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.6D
User sap<sid> for SAP systems with releases later than 4.6C

Select
The J2EE-ENG contains the SAP J2EE Engine The JLIBS contains the J2EE development tools

© SAP AG 2003

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.

(C) SAP AG

ADM110

5-75

Parameter for SAP J2EE Engine

Select
Memory for SAP J2EE Engine of the dialog instance

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

© SAP AG 2003

(C) SAP AG

ADM110

5-76

Installation Steps SAPinst displays the progress of the installation by highlighting the currently active installation phase © SAP AG 2003 (C) SAP AG ADM110 5-77 .

Finish Dialog Instance Installation © SAP AG 2003 (C) SAP AG ADM110 5-78 .

For all other databases. SAP J2EE Engine Installation/Dialog Instance Installation/Standalone Gateway Instance Installation on <platform>. © SAP AG 2003 For more information. The client software enables the communication between a host and the database. (C) SAP AG ADM110 5-79 . see the installation guide. the client software installation is integrated in the SAPinst installation.Appendix: Installing Client Software Installation of the client software for Microsoft SQL Server and Oracle only 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.

Installation Process SAPinst Installation Central Instance Installation Database Instance Installation SAP J2EE Engine Installation Dialog Instance Installation Appendix: Gateway Instance Installation © SAP AG 2003 (C) SAP AG ADM110 5-80 .

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. refer to SAP Note 492305. with SAP Pres.Appendix: Preparation for Gateway Instance Installation (1/2) See SAP Note 492305: Windows GW Instance Inst.cmd) from the Presentation CD. (C) SAP AG ADM110 5-81 . CD 6. © SAP AG 2003 For more information. run SAPinst (Setup.

Install SAPinst 2. Finish SAPinst installation © SAP AG 2003 (C) SAP AG ADM110 5-82 . Choose installation directory 3.Appendix: Preparation for Gateway Instance Installation (2/2) 1.

Appendix: Start Gateway Instance Installation Select: Install SAP Gateway if you want to install a gateway instance Accept the license agreement for STLport © SAP AG 2003 (C) SAP AG ADM110 5-83 .

(C) SAP AG ADM110 5-84 . 72.Appendix: Installation Parameter Enter: New SAP system ID New instance number © SAP AG 2003 Enter a new SAP system ID in the SAP System ID field. You can assign a number from 0 to 97. enter the name of the gateway instance host. or 89. 25. Do not use an SAP system ID that you entered during a central instance installation. but not the numbers 2. In the Instance Hostname field. enter the number of the gateway instance. In the Instance Number field.

Appendix: LDAP Select No LDAP if you do not want to use an LDAP service © SAP AG 2003 (C) SAP AG ADM110 5-85 .

Appendix: Windows Domain Information and RAM Windows only: Domain information for SAP system user account on operating system Select RAM quantity © SAP AG 2003 (C) SAP AG ADM110 5-86 .

Appendix: SAP System Directory Select: Drive for SAP system directory © SAP AG 2003 (C) SAP AG ADM110 5-87 .

Appendix: Set Passwords for Operating System User Enter and confirm: Password for <sid>adm Password for SAPService<SID> © SAP AG 2003 (C) SAP AG ADM110 5-88 .

Appendix: CD Browser and Ports Select: Location of Presentation CD folder Gateway © SAP AG 2003 (C) SAP AG ADM110 5-89 .

Appendix: Installation Steps and End of Gateway Installation © SAP AG 2003 (C) SAP AG ADM110 5-90 .

sap. http://service.com/instguides © SAP AG 2003 (C) SAP AG ADM110 5-91 .Further Information SAP Service Marketplace.

Installation Process: Unit Summary Now you are able to: Install a central instance Install a database instance Install an SAPJ2EE Engine instance Install a dialog instance © SAP AG 2003 (C) SAP AG ADM110 5-92 .

select SAP R/3 Enterprise 4. dialog instance • Install a gateway instance You perform an installation of an SAP system including SAP J2EE Engine and gateway instance.Installation Process Exercises Unit 5: Installation Process At the conclusion of this exercise. 5-1-1 Create an installation directory named INSTALL. Use the following information to perform the installation. Use drive G:. on twdf0###.71 for SAP DB – Default to start the installation.CMD from the SAPinst CD in folder \SAPINST\NT\. 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. (C) SAP AG ADM110 5-93 . 5-2 Install the central instance on the server you are using for the training. 5-1 Install SAPinst on the server you are using for the training. database instance. for example. you will be able to: • Install SAPinst • Install a central instance. e. 5-2-1 On the welcome screen. 5-1-3 Perform the SAPinst installation. Note: Always use drive G: to install the software.g. SAP J2EE Engine instance. 5-2-2 Install the central instance. on twdf0###. 5-1-2 Start the program SETUP.

select SAP R/3 Enterprise 4. 5-3-3 Install the database instance. for example. on twdf0###. 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) Make a note of the parameters because they are needed later on.71 for SAP DB – Default to start the installation. Use the following information to perform the installation. Select the values for the following parameters as indicated here: SAP System ID Instance to install Database Installation Method Database Installation Type Database System ID Instance number Same <SID> as for central instance installation Database Instance Select Standard Installation Install (first) SAP system into a new database = SAP System ID Enter instance number of previously installed central instance 5-94 (C) SAP AG ADM110 . 5-3-2 On the welcome screen.Select the values for the following parameters as indicated here: Instance to install Database System ID Database Host Domain Information for the SAP System accounts Instance RAM Drive for SAP System directory Host with Transport Directory Kernel CD Message port RDBMS CD 5-3 Central Instance = SAP System ID Host name of your server twdf#### Local Installation 800MB G: Host name of your server twdf#### G:\SETUP\Kernel 3600 + central instance number G:\SETUP\RDBMS_SAP_DB Install the database instance on the server you are using for the training. Note: Always use drive G: to install the software. 5-3-1 Restart SAPinst.

_6. 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. _7 Choose Continue installation Install the SAP J2EE Engine instance on the server you are using for the training. _3. 5-4-3 Install the SAP J2EE Engine instance. on twdf0###. Select the values for the following parameters as described: SAP J2EE Engine CD G:\SETUP\SAP_J2EE_E (C) SAP AG ADM110 5-95 . for example. _5. select Upgrade SAP Central Instance JAVA Core 6. 5-4-1 Restart SAPinst.Instance Host Domain Information for the SAP System accounts Instance RAM Host with Transport Directory Password for user <sid>adm Password for user SAPService<SID> Kernel CD RDBMS CD Export CD 1 Drive for the client software installation Log Mode for the Database Instance Number of Work Processes Max CPU RAM for database caches Log Devspace Data Devspace System Devspace Export CDs (2 .7) Prepare multi national language support 5-4 Host name of your server twdf#### Select Local Installation 800MB (= RAM for central Instance) Host name of your server twdf#### Same password you used for central instance installation Same password you used for central instance installation G:\SETUP\Kernel G:\SETUP\RDBMS_SAP_DB G:\SETUP\Export_1 G: Demo 30 2 500MB Drive: G: Size: 1000 Drive: G: Size: 25000 Drive: G: G:\SETUP\Export_2. 5-4-2 On the welcome screen.20 to start the installation. _4.

Use the following information to perform the installation. select SAP R/3 Enterprise 4.71 Dialog Instance . 5-5-2 On the welcome screen. 5-5-1 Restart SAPinst. 5-5-3 Install the dialog instance.Java to start 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 Other than central parameters) instance number Instance number (central instance Enter instance number of parameters) previously installed central instance Instance Host Host name of your server twdf#### Database System ID = SAP System ID Database Host Host name of your server twdf#### Domain Information for the SAP Select Local Installation System accounts 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 (C) SAP AG ADM110 5-96 .Central Instance Profile SAP Web AS Administrator Account SAP J2EE Engine Parameters ngine\J2EE-ENG G:\SETUP\SAP_J2EE_E ngine\JLIBS G:\SETUP\SAP_J2EE_E ngine\SDM G:\SETUP\SAP_J2EE_E ngine\WASCOMP G:\usr\sap\<SID>\SYS\pr ofile\ <SID>_D*_<hostname> User: DDIC Client: 000 Password: use same password as in database instance installation JAVA VM maximum heap size: 64 MB 5-5 Optional: Install the dialog instance on the server you are using for the training. on twdf0###. Note: Always use drive G: to install the software. for example.

Password for user SAPService<SID> Kernel CD Message port RDBMS CD Database schema SAP J2EE Engine CD Maximum memory (MB) SAP J2EE Engine communication user SAPJSF Same password you used for central instance installation G:\SETUP\Kernel Same port you used for central instance installation G:\SETUP\RDBMS_SAP_ DB SAP DB user new style G:\SETUP\SAP_J2EE_En gine\J2EE-ENG G:\SETUP\SAP_J2EE_En gine\JLIBS 64 Client: 000 Password: Same password you used for SAP J2EE Engine installation (on central instance) (C) SAP AG ADM110 5-97 .

CMD from the SAPinst CD in folder \SAPINST\NT\. on twdf0###. Start the program SETUP. 5-1-2 Start the program SETUP. for example. Use drive G:. 5-1-3 Perform the SAPinst installation. you will be able to: • Install SAPinst • Install a central instance. on twdf0###. for example.71 for SAP DB – Default to start the installation. database instance.CMD from G:\SETUP\SAPINST\SAPINST\NT.” 5-2 Install the central instance on the server you are using for the training.” “SAPinst Installation Default Parameters” and “SAPinst Installation Finished.Installation Process Solutions Unit 5: Installation Process At the conclusion of this exercise. (C) SAP AG ADM110 5-98 . 5-1-1 Create an installation directory named INSTALL. 5-2-1 On the welcome screen. 5-1 Install SAPinst on the server you are using for the training. 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. Proceed as described on the slides “SAPinst Welcome Screen. Follow the exercise description. select SAP R/3 Enterprise 4. Follow the exercise description.

” “Instance Directory and Transport Host.” “CD Browser: RDBMS CD. Instance Number. Note: Always use drive G: to install the software.5-2-2 Install the central instance.” “Set Passwords for Operating System Users. Proceed as described on the slide “Preparation for Database Instance Installation.” “Database Parameters.” “Finish Central Instance Installation. SID. 5-3-1 Restart SAPinst. on twdf0###.” 5-3 Install the database instance on the server you are using for the training.” “Installation Steps. Select the values for the following parameters as described: Instance to install Database System ID Database Host Domain Information for the SAP System accounts Instance RAM Drive for SAP System directory Host with Transport Directory Kernel CD Message port RDBMS CD Central Instance = SAP System ID Host name of your server twdf#### Select Local Installation 800MB G: Host name of your server twdf#### G:\SETUP\Kernel 3600 + central instance number G:\SETUP\RDBMS_SAP_DB Proceed as described on the slides “Start Installation of the Central Instance.” “Windows Domain Information and RAM.” (C) SAP AG ADM110 5-99 .” “CD Browser and Message Server Port. 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 Password for user SAPService<SID> Make a note of the parameters because they are needed later on.” “Instance Installation Type. Use the following information to perform the installation. for example.

Note: Always use drive G: to install the software. Follow the exercise description. select SAP R/3 Enterprise 4.71 for SAP DB – Default to start the installation. You can choose 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) Make a note of the parameters because this information is needed later on. 5-3-3 Install the database instance. Select the values for the following parameters as described: SAP System ID Instance to install Database Installation Method Database Installation Type Database System ID Instance number Same <SID> as for central instance installation Database Instance Select Standard Installation Install (first) SAP system into a new database = SAP System ID Enter instance number of previously installed central instance Host name of your server twdf#### Select Local Installation 800MB (= RAM for central Instance) Host name of your server twdf#### Same password you used for central instance installation Same password you used for central instance installation G:\SETUP\Kernel G:\SETUP\RDBMS_SAP_DB G:\SETUP\Export_1 G: 5-100 Instance Host Domain Information for the SAP System accounts Instance RAM Host with Transport Directory Password for user <sid>adm Password for user SAPService<SID> Kernel CD RDBMS CD Export CD 1 Drive for the client software (C) SAP AG ADM110 .5-3-2 On the welcome screen. Use the following information to perform the installation.

for example.” “Instance Installation Type and SID. _3.” “LOG and DATA Devspace Settings.” “Installation Directory: Database Client Software. Use the following information to perform the installation.” “Change Password of ABAP Super Users. 5-4-3 Install the SAP J2EE Engine instance. _4.7) Prepare multi national language support Demo 30 2 500MB Drive: G: Size: 1000 Drive: G: Size: 25000 Drive: G: G:\SETUP\Export_2.” “Installation Steps. NonUnicode.” 5-4-2 On the welcome screen. _7 Choose Continue installation Proceed as described on the slides “Start of Database Instance Installation. Follow the exercise description.” “Database and Central Instance Parameters. on twdf0###. NonUnicode.” “Set Passwords for Operating System User. _6.” “Windows Domain Information and RAM.” “Database Installation Method and Type. You can choose the following parameters freely with respect to the restrictions mentioned in the training material: Password for user SAPJSF (C) SAP AG ADM110 5-101 .” “Instance Directory and Transport Host.” “Database Parameters and Operation Mode. Proceed as described on the two slides on “Preparation for SAP J2EE Engine Installation.20 to start the installation.” “SYSTEM Devspace Settings.” “Database Load Parameters. 5-4-1 Restart SAPinst.” 5-4 Install the SAP J2EE Engine instance on the server you are using for the training.” “Prepare Multi National Language Support (Non-Unicode).” “Finish Database Instance Installation. Note: Always use drive G: to install the software. Non-Unicode. select Upgrade SAP Central Instance JAVA Core 6.” “Multi National Language Support (Non-Unicode).” “CD Browser: Export CDs.installation Log Mode for the Database Instance Number of Work Processes Max CPU RAM for database caches Log Devspace Data Devspace System Devspace Export CDs (2 . _5.

Note: Always use drive G: to install the software. on twdf0###.” Use the shortcut on the desktop.” to restart the SAP system. Select the values for the following parameters as described: SAP System ID Same <SID> you used for central instance installation Instance number (dialog Other than central instance instance parameters) number Instance number (central Enter instance number of instance parameters) previously installed central instance Instance Host Host name of your server twdf#### Database System ID = SAP System ID Database Host Host name of your server (C) SAP AG ADM110 5-102 . for example. “SAP R/3 Management Console. 5-5-3 Install the dialog instance. Proceed as described on the slide “Preparation for Dialog Instance Installation.” “Parameters for Java Core. 5-5 Optional: Install the dialog instance on the server you are using for the training.71 Dialog Instance .Java to start the installation.Make a note of the parameters.” “Installation Steps. because it is needed later on. Follow the exercise description.” 5-5-2 On the welcome screen.” “Finish Installation of SAP J2EE Engine. Select the values for the following parameters as described: SAP J2EE Engine CD G:\SETUP\SAP_J2EE_Engine\J2EEENG G:\SETUP\SAP_J2EE_Engine\JLIBS G:\SETUP\SAP_J2EE_Engine\SDM G:\SETUP\SAP_J2EE_Engine\WAS COMP Central Instance Profile G:\usr\sap\<SID>\SYS\profile\ <SID>_D*_<hostname> SAP Web AS Administrator User: DDIC Account 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. 5-5-1 Restart SAPinst. Use the following information to perform the installation. select SAP R/3 Enterprise 4.

” “Instance Installation Type.” “Set Passwords for Operating System User. SID.” “CD Browser and Message Server Port.” (C) SAP AG ADM110 5-103 .” “Installation Steps.” “Instance Directory and Transport Host.” “Parameter for SAP J2EE Engine.” “Finish Dialog Instance Installation.” “Central Instance and Database Parameters. Instance Number.” “Database Schema and CD Browser.Domain Information for the SAP System accounts Instance RAM Host with Transport Directory Password for user <sid>adm Password for user SAPService<SID> Kernel CD Message port RDBMS CD Database schema SAP J2EE Engine CD twdf#### Select Local Installation 350MB Host name of your server twdf#### Same password you used for central instance installation Same password you used for central instance installation G:\SETUP\Kernel Same port you used for central instance installation G:\SETUP\RDBMS_SAP_DB SAP DB user new style G:\SETUP\SAP_J2EE_Engine \J2EE-ENG G:\SETUP\SAP_J2EE_Engine \JLIBS 64 Client: 000 Password: Same password you used for SAP J2EE Engine installation (on central instance) Maximum memory (MB) SAP J2EE Engine communication user SAPJSF Proceed as described on the slides “Start Dialog Instance Installation.” “Windows Domain Information and RAM.

New Features Installation Planning Installation Preparation Installing SAP GUI Installation Process Post-Installation Activities Implementing Patches Converting Non-Unicode to Unicode Troubleshooting Installation Problems (C) SAP AG ADM110 6-1 .Post-Installation Activities 1 2 3 4 5 6 7 8 9 © SAP AG 2003 SAP R/3 Enterprise Architecture.

SAP Online Documentation and SAProuter Configuring TMS and Basic Configuration Additional tasks Objectives: At the conclusion of this unit.Content and Objectives Content: Installation SAP License. you will be able to: Perform all necessary post-installation activities © SAP AG 2003 (C) SAP AG ADM110 6-2 .

Post-Installation Activities Restart SAP System and Final Checks SAP License SAP Online Documentation SAProuter TMS and Basic Configuration Additional Tasks Appendix © SAP AG 2003 (C) SAP AG ADM110 6-3 .

Stop SAP system using the command or alias stopsap from operating system level.Start and Stop the SAP System Log on to operating system with user <sapsid>adm and start the command or alias startsap. SAP*and DDIC. 066 DDIC in client 000 (C) SAP AG ADM110 6-4 . To log on. There are two standard users. Log on to SAP system with standard user SAP* or DDIC. Check whether database and SAP system are running. in the SAP system after the installation: SAP* in client 000. © SAP AG 2003 You can use this procedure to see if you can start and stop the SAP system after the installation. install an interface such as SAP GUI.

(C) SAP AG ADM110 6-5 .Checking SAP System Services 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) © SAP AG 2003 Check SAP system services to solve initial problems that might occur when trying to log on or run the system for the first time.

Post-Installation Activities Restart SAP System and Final Checks SAP License SAP Online Documentation SAProuter TMS and Basic Configuration Additional Tasks Appendix © SAP AG 2003 (C) SAP AG ADM110 6-6 .

you must install a permanent license. When you change the installation number.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. an SAP license is required. After the installation of the central instance. (C) SAP AG ADM110 6-7 . Choose mySAP Business Suite to reach the request page for license keys. For more information.sap. During this period. With this temporary license you cannot create new repository objects or modify SAP repository objects. all dependent information (for example. You can install several licenses. see also SAP Note 94998. go to service.com/licensekey. SSCR) is lost. database type) SAP license number must be 18 characters (enlarge with leading zeros) © SAP AG 2003 To work with the SAP system. only the user SAP* can log on to the SAP system. If the temporary license is expired. a temporary license is active for four weeks only. To request license keys.

Installing SAP Licenses Use transaction SLICENSE to install a new SAP license 1 hardware key 2 © SAP AG 2003 You can use transaction SLICENSE to determine the hardware key on all computers to which an RFC connection is maintained. This executes saplicense –get on the computer in question and the result is returned. the license key is activated immediately. After the license is installed. (C) SAP AG ADM110 6-8 . In the initial screen of transaction SLICENSE. choose Goto → Determine hardware key. You can install a new SAP license in your SAP system using the SLICENSE transaction. Then saplicense –install is executed on the computer.

Post-Installation Activities Restart SAP System and Final Checks SAP License SAP Online Documentation SAProuter TMS and Basic Configuration Additional Tasks Appendix © SAP AG 2003 (C) SAP AG ADM110 6-9 .

2. DynamicHelp) Compiled HTML (HtmlHelp) For online access from the SAP system.Online Documentation CD. With help type PlainHtmlHttp (installation of help files on a Web server). Installing the help files Customizing setup variants for Online Help Installing a Web browser or viewer © SAP AG 2003 There is one CD for each language containing both formats (standard HTML and compiled HTML). you also need to maintain Web server settings. 3. For more information about installing the SAP Online Documentation. both formats require the following steps: 1.Installing the SAP Online Documentation Online help on the CD-ROM SAP Library is delivered in two file formats: Standard HTML (PlainHtml. refer to "Installing the Online Documentation" in the root directory of the SAP Library . (C) SAP AG ADM110 6-10 .

FR for French. and so on). and so on) for directory name files © SAP AG 2003 When accessing the documentation online. FR for French. (C) SAP AG ADM110 6-11 .General Information to Install the Helpfiles General information for help types HtmlHelpFile. PlainHtmlFile: Use separate directories for different language versions of the documentation Use two-character language key (EN for English. the help processor expects directories that are named with respective two-character language keys (EN for English. PlainHtmlHttp.

2. copy help files to local hard disks or a file server. © SAP AG 2003 Compiled HTML (HTML Help): HtmlHelpFile Compiled HTML provides direct access to files with Microsoft HTML-Help Viewer. About 500 MB of disk space is needed for the German and English language versions. 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 Install help files from directory Htmlhelp\Helpdata on the SAP Library CD-ROM: 1. Disk space for one language version should be 250 MB for SAP Web Application Server For performance reasons. Create a directory on your file server. (C) SAP AG ADM110 6-12 .

instead choose another partition. © SAP AG 2003 Standard HTML: PlainHtmlHttp. Unpack the files on the local hard disk or on a file server. Digital Unix. Files are stored in a packed format on the CD-ROM. (C) SAP AG ADM110 6-13 . PlainHtmlFile (1/2) Install the help files and the search engine and search index from the directory Plainhtm on the SAP Library CD .Installation of PlainHtmlHttp. Documentation directory: Approximately 600 MB of disk space are required for one language version (Windows NTFS). HP-UX. The online help cannot be installed on a Microsoft FAT32 file system because it cannot handle the large number of files and directories. your Web server must run on one of these platforms: IBM AIX. PlainHtmlFile Files cannot be viewed directly from the CD. A Web search engine and index data for full-text search are delivered on the CD-ROM. do not install the SAP Library on the system partition. If your Web server runs under Microsoft Windows NT or Windows 2000. Under OS/2 and OS/400 you have to use insthelp directly. 1. Use the install program on the CD-ROM that matches the operating system of your Web server (directory Plainhtm/Install/<operating system>). Create a directory on the Web server 2. To be able to use the search function. SUN Solaris. The install program uses the insthelp program and is available only for Windows and UNIX (with graphical user interface). Complete installation for SAP Web AS includes about 200 thousand files in about 100 thousand directories for one language version. Storage requirements depend on the particular file system and can amount up to 2 GB (UNIX). Windows.

Installation of PlainHtmlHttp. PlainHtmlFile (2/2) © SAP AG 2003 (C) SAP AG ADM110 6-14 .

The HTML-based online documentation can be displayed with a Web browser on all front-end platforms supported by SAP.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 © SAP AG 2003 For a given front-end platform. As of Release 4. see course ADM100. Certain requirements and restrictions must be observed. For more information about setup variants for Online Help. however.6C. a setup variant specifies a help type. regardless of the user’s logon language. Installing the SAP Library. the location of the help files (server and/or path). The language version specified in the currently active setup variant determines which language version of the online help is displayed. maintenance of SAP profile parameters for the online help has no effect. For more information. refer to the installation guide. and the language version of the help files. depending on the particular platform. (C) SAP AG ADM110 6-15 .

Post-Installation Activities Restart SAP System and Final Checks SAP License SAP Online Documentation SAProuter TMS and Basic Configuration Additional Tasks Appendix © SAP AG 2003 (C) SAP AG ADM110 6-16 .

The SAProuter software is included in the standard SAP kernel. SAProuter is started as a demon under UNIX. No additional installation is required. Connection from SAP to your SAP system are controlled by SAProuter. SAPNet–R/3 Frontend is the SAP-based service system and provides the technical link between SAP customers and SAP. as a service under Windows. SAPNet–R/3 Frontend was known as the Online Service System. (C) SAP AG ADM110 6-17 . SAProuter allows you to make indirect network connections.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 SAP System Customer SAP System SAProuter SAProuter © SAP AG 2003 SAProuter increases network security and simplifies network configuration.

see course ADM960. Configure connection using transaction OSS1 (see SAP Note 17285) © SAP AG 2003 For information about installing SAProuter on the AS400 platform. read SAP Note 86329.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). For more information about using SAProuter. (C) SAP AG ADM110 6-18 .

Configuring SAProuter and SAPNet–R/3 Frontend Select the suitable SAProuter at SAP © SAP AG 2003 (C) SAP AG ADM110 6-19 .

refer to: SAP Service Marketplace at http://service.sap.com/sapnetguide SAP Library (choose Help → SAP Library in your SAP system or access the SAPLibrary at http://help.com) For information on installing SAProuter as a Microsoft Windows service.sap.sap.sap.com) © SAP AG 2003 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.SAProuter and SAPNet–R/3 Frontend For more information on setting up and using SAPNet–R/3 Frontend. 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 (C) SAP AG ADM110 6-20 .com/sapnet-guide SAP Library (choose Help → SAP Library in your SAP system or access the SAP Library at http://help.

Post-Installation Activities Restart SAP System and Final Checks SAP License SAP Online Documentation SAProuter TMS and Basic Configuration Additional Tasks Appendix © SAP AG 2003 (C) SAP AG ADM110 6-21 .

Select Standard installation.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. (C) SAP AG ADM110 6-22 . 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. if the SAP system was created based on a copy. © SAP AG 2003 If you have installed your SAP system from the SAP CD. problems could arise when you upgrade the system or modify objects with the Transport Organizer. delivered version. If you set up an SAP system that originated from a database copy using Standard installation. No adjustments based on corrections or repairs have been made. It is assumed that the SAP system is running as a correct. if the SAP system was installed from the SAP CD using SAPinst. you should not configure the CTS after installation. it is necessary to configure the CTS after installation. SAPinst provides utilities for copying and migrating databases. you must configure the CTS after installation. Select Database Copy or Database Migration.

CFG in directory © SAP AG 2003 For more information. (C) SAP AG ADM110 6-23 .TMS Configuration: Transport Domain Check and maintain (if necessary) permissions to directory /usr/sap/trans On transport domain controller: Log on in client 000. see course ADM325. DDIC (not SAP*) Start transaction STMS Transaction STMS in client 000 will: Assign the SAP system as the transport domain controller Create transport domain name DOMAIN_<SID> Create transport group GROUP_<SID> Create communication user TMSADM in client 000 Create RFC destinations Set up file DOMAIN.

TMS Configuration: Transport Routes After establishing a transport domain: Create transport routes from the domain controller. Draw a line connecting the two SAP systems between which you want to set up a transport route. For more information. from the Display Transport Routes screen. In the Create Transport Route dialog box. 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. Configuration Standard Configuration Set the system change options (transaction SE06) © SAP AG 2003 To create transport routes. change mode. choose Configuration → Transport Route → Create Transport Route. enter the required information for either the consolidation or delivery route. using the default standard configurations One-system landscape Two-system landscape Three-system landscape Start transaction STMS and choose Overview Transport Routes. see course ADM325. (C) SAP AG ADM110 6-24 . Choose Save.

the system performs a consistency check and a check of the way in which the parameters interact. These profile parameters are then stored in the database and written back to file system level. Perform the administration and maintenance of profiles in transaction RZ10. For more information.Basic Configuration: Import of Profiles Transaction RZ10 INSTANCE-PROFIL Import START-PROFIL DEFAULT-PROFIL during installation generated profiles Operating system SAP system Start import using transaction RZ10: © SAP AG 2003 After installation. During this import. To be able to use the profile administration of the SAP system. the profile parameters are present at file level only. see course ADM100. After selecting the profile to edit. you can change individual profile parameters. you import the profiles into the database by choosing Utilities → Import Profiles → Of active servers. These changes take effect only when they are read by the system (when the system is restarted). Changes to profile parameters can then be performed in the SAP system. (C) SAP AG ADM110 6-25 . the profiles must be imported into the database. In the first step.

Basic Configuration: Number of Work Processes After the installation. max 3) Number of enqueue work process = 1 Number of spool work process = 1 SAP recommends that you adapt SAP profiles using transaction RZ10. max 6) Number of update2 work process = RAM / 1024 (min 1. Nevertheless. it is possible to change SAP parameters in the corresponding files on the operating system. max 18) Number of update work process = RAM / 768 (min 1. (C) SAP AG ADM110 6-26 . max 3) Number of batch work process = RAM / 1024 (min 2. an initial configuration is available transaction RZ10 Optimize the number of work processes depending on: System resources The number of users working in each SAP system application Instance Profile Change © SAP AG 2003 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.

(C) SAP AG ADM110 6-27 . The distribution should be made primarily between the dialog and background work processes. see course ADM100. 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. the operation modes are created as empty containers in transaction RZ04.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 values Change the distribution of work processes in the individual operation modes background processing NIGHT 11121 10 2 9 3 8 4 765 BGD 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 dialog processing DAY © SAP AG 2003 The operation modes are set up in a number of steps: First. Next. For more information. In the timetable (transaction SM63). Next distribute the individual operation modes in the total number of work processes taken from the instance profile. you specify the periods for which the operation modes are valid and when the switch between the operation modes should occur.

Basic Configuration: Background Jobs Schedule background jobs with transaction SM36 Standard jobs for all used applications. rdisp/btc* © SAP AG 2003 For more information. (C) SAP AG ADM110 6-28 . for example. see course ADM100. such as basis Configure SAP profile parameters for background processing. rdisp/max_wprun_time.

Basic Configuration: User and Roles Set up user and role administration for the SAP system Preparatory steps for role maintenance (transaction PFCG) 1. (C) SAP AG ADM110 6-29 . Check parameter auth/no_check_in_some_cases = Y Start transaction SU25 and choose menu entry 1: Initially fill the customer tables transaction SU25 Create roles: transaction PFCG © SAP AG 2003 Users must be set up and roles assigned to user master records before you can use the SAP system. • Copy SAP default settings for check indicators and authorization field values using transaction SU25 (step 1: Initially fill the customer tables). 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. 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. Use profile generator (transaction PFCG) to create and maintain roles. For more information about transaction PFCG. The profile generator (transaction PFCG) is active in the standard system (the system profile parameter auth/no_check_in_some_cases is set). see courses ADM100 and CA940. Roles are collections of activities that allow a user to use one or more business scenarios of an organization. Schedule background job for time limits: You can set a time limit on the assignment of users to roles. 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. 2.

Basic Configuration Additional Tasks: Set up logon groups with transaction SMLG Install printers with transaction SPAD Configure system log with transaction SM21 © SAP AG 2003 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. see course ADM100. 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. (C) SAP AG ADM110 6-30 .

Post-Installation Activities Restart SAP System and Final Checks SAP License SAP Online Documentation SAProuter TMS and Basic Configuration Additional Tasks Appendix © SAP AG 2003 (C) SAP AG ADM110 6-31 .

TDCT. The character set specified in the SAP kernel matches the character set specified in the database system. T100. This function is also called automatically whenever you start your system or start an application server. TSTC. The structures that are checked include structures SYST. 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. and others.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 © SAP AG 2003 The consistency check is used to determine inconsistencies in your system. TFDIR. (C) SAP AG ADM110 6-32 . The critical structure definitions that are defined in both the data dictionary and the SAP kernel are identical.

reset the setting in table T000. you can deactivate the switch without problems. 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. the SAP R/3 Enterprise Extension Set." After the activation. 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'.Activation of SAP R/3 Enterprise Extension Set Activation of extension set: 1. An error message is issued when you activate one or more switches for parts of the SAP R/3 Enterprise Extension Set. in a test system without production data. The functions are activated by selecting the relevant activation switch in the IMG activity. Afterward. and of the SAP Enterprise menu. Choose SAP Reference IMG © SAP AG 2003 From a technical point of view. Clientindependent activation switches allow you to use the functions contained in the SAP R/3 Enterprise Extension Set components. Generally. Before you activate parts of SAP R/3 Enterprise. Refer to SAP Note 532499 for information on activating various components simultaneously. additional entries are displayed in the tree structures of the IMG. 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. "Activation switch for the SAP R/3 Enterprise Extension Set. Call transaction SPRO (IMG) 2. of the Application Component Hierarchy (AKH). (C) SAP AG ADM110 6-33 . depending on the component activated. that is. After the activation. Change the setting to 'T' and then activate the switches. the SAP R/3 Enterprise Extensions are delivered and installed as part of an Add-on for the SAP R/3 Enterprise Core.

(C) SAP AG ADM110 6-34 .

Classification of the language 2.20) integrates the program RSREFILL and the client maintenance function. Scheduling of the language transport 3. The imported languages must be defined in the default profiles so you can log on in these languages. Classification of the language transaction SMLT: © SAP AG 2003 Follow this procedure to classify a language: Click Classify Language or choose Language → Classify. choose the language you want to import and the corresponding supplementation language. SAP recommends that you use the language supplementation program. which (as of SAP Web Application Server 6.Installation of Additional Languages (1/3) Perform the following steps: 1. The relevant parameter is zcsa/installed_languages. See course ADM102 for more information about updating a translation language for the customizing settings of an existing customer client (other than client 000). (C) SAP AG ADM110 6-35 . On the next dialog box. Scheduling of the language supplementation 1.

This action schedules a background job that performs the import. Specify a start time and (optional) target server and choose Execute to import the language packages. The green. You do not need to import them into newly installed systems. Enter the path for the language packages. If an action terminates for technical reasons. 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.Installation of Additional Languages (2/3) 2. you can restart it. Follow this procedure to import language packages: Select the language for which you want to install extra packages and choose Language → Import package. (C) SAP AG ADM110 6-36 . Scheduling of the language transport transaction SMLT 1 2 3 4 © SAP AG 2003 The languages English and German are completely available in all newly installed systems. Choose Find package(s) to search for any available packages in the path you have entered. Check the log files.

(C) SAP AG ADM110 6-37 . This action schedules a background job that performs the supplementation. choose Information on Table Selection in the system. 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. For more information on these strategies. 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. Follow this procedure to schedule language supplementation: Choose Language → Supplement Language. Scheduling of the language supplementation transaction SMLT 1 2 3 4 © SAP AG 2003 Use the language supplementation function to fill in the gaps in a language that have not been translated completely. Enter conditions that control which tables are selected for supplementation. Supplementation actions are client-specific. The languages are supplemented in the client in which you are logged on. Monitor the supplementation and check log files.Installation of Additional Languages (3/3) 3.

6D: Transport processes (import and export) can be started in parallel. (C) SAP AG ADM110 6-38 . see course ADM102 or go to service. © SAP AG 2003 For more information. Basis Release 4.20 → SAP Web AS 6.20: Client maintenance function (RSREFILL program) is integrated into the language supplementation program. Basis Release 4.sap.com/instguides and choose SAP Web AS 6.6C Languages are now transported with the SAP transport programs R3trans and tp.Language Import: New Features New features: SAP Web Application Server 6.20: Language Transport.

"Implementing Patches. refer to unit 6.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 © SAP AG 2003 For more information about package implementation." (C) SAP AG ADM110 6-39 .

(C) SAP AG ADM110 6-40 . Consistency of the application data in the SAP delivery client is not guaranteed. see course ADM325. Client 066 is used only for remote support from SAP. 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. if you want to change the SAP system client of the communication user SAPJSF. which supersedes the previously used R/3 Properties Manager. adapt the connection parameters for every SAPJ2EE Engine instance of your SAP system (that is.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. for the SAP J2EE Engine of every SAP central instance and every SAP dialog instance) For more information concerning client copies. As a result. Starting with SAP J2EE Engine 6. use the profile SAP_CUST to copy client 000.Client Copy SAP strongly recommends: To create your first client. If you perform a client copy. Instead. you should also change the SAP system client of user SAPJSF after the client copy. 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) © SAP AG 2003 After the installation client 000 and 066 are available.

5 – 2 GB Production client in SAP R/3 Enterprise Customizing and application data > 25000 Tables >> 5 GB Target client © SAP AG 2003 (C) SAP AG ADM110 6-41 .Client Copy with SAP R/3 Enterprise Customizing client in SAP R/3 Enterprise Customizing data > 17000 Tables > 1.

Perform a Full Backup: Windows Windows Prerequisites Stop SAP system. Select Only backup the System State Data and specify the Backup media type and the destination of the backup. Save the System State Data: Choose Start → Programs → Accessories → System → Tools → Backup → Backup Wizard. Back up all SAP-specific and all database-related directories: Choose Start → Programs → Accessories → System → Tools → Backup → Backup Wizard. <HOMEDIR> of <sapsid>adm. specify the media type and destination for the backup. (C) SAP AG ADM110 6-42 . Select the Windows directory and all SAP and database-related directories. 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 © SAP AG 2003 Save the Registry: Choose Start → Programs → Accessories → System → Tools → Backup → Emergency Repair Disk. \USR\SAP\TRANS. \WINNT . Select Also Backup the Registry to the Repair directory… When you confirm your entry. the Registry is written to disk. Select Backup selected files. drives or network data. including: \USR\SAP.On the Where to Store the Backup screen.

Create the archive: tar -cf <ARCHIVNAME> <filesystem / filename> -uf <ARCHIVNAME> <filesystem / filename> . Store the archive on tape: tar -cf <tape_device> <ARCHIVNAME>. database configuration data). 2.<sapmnt>/<SAPSID> . Compress the archive: compress <ARCHIVNAME> 3.Perform a Full Backup: UNIX UNIX Prerequisites Stop SAP system and database Procedure Log on as user root. file system size. See your system administration guide for details and for operating system-specific backup procedures.root file system This saves the structure of the system and all configuration files (for example./usr/sap/<SAPSID> . logical volume manager configuration.Z © SAP AG 2003 You need to back up the following directories and files: All database-specific directories All SAP-specific directories: . Manually create a compressed tar archive containing all installed files 1.home directory of the user <sapsid>adm .. This procedure works on all hardware platforms./usr/sap/trans ... (C) SAP AG ADM110 6-43 .

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 (C) SAP AG ADM110 6-44 .Checking the RFC Destination In distributed installation (central and database instance run on different hosts).

see SAP Note 569560. is not locked. Instead. Starting with SAP J2EE Engine 6. and its password is set correctly to the one you entered during the installation by calling transaction SU01. This documentation is available in SAP Service Marketplace at http://service. use SAPJSF (a new tool). To change the SAP Communication.com/security. As a result. Choose Security in Detail → Hot Topic: J2EE. 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. © SAP AG 2003 After the installation. 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. (C) SAP AG ADM110 6-45 . For more information. 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.SAP J2EE Engine After the installation. Security Integration SAP Web AS and SAP J2EE Engine.sap. 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. make sure that user SAPJSF exists. if you want to change the SAP system client of the communication user SAPJSF. the SAP J2EE Engine is activated. which supersedes the previously used R/3 Properties Manager.20 patch level 8.

2. © SAP AG 2003 (C) SAP AG ADM110 6-46 .SAP J2EE Engine: User SAPJSF Make sure that user SAPJSF was created correctly and is not locked. Start transaction SE37 and enter the function module PRGN_J2EE_CREATE_SERVICE_USER. Choose Single Test Specify the import parameter IF_PASSWORD and choose Execute. If the user does not exist: 1. 3. Use transaction SU01 (User Maintenance).

Administration of the SAP J2EE Engine: Administration of SAP J2EE Engine is done from within the SAP system using transaction SMICM. Ports used by the SAP J2EE Engine: The ports used by the SAP J2EE Engine are listed in the file prepconf. This is located in the installation directory of the SAP J2EE Engine. © SAP AG 2003 (C) SAP AG ADM110 6-47 .Additional Information for SAP J2EE Engine and SDM File System Structure: /usr/sap/<SAPSID>/<Instance Name>/j2ee /usr/sap/<SAPSID>/<Instance Name>/sdm SDM is installed only on the central instance.log.

for example). In addition. Before the generation is started. make sure that there is enough space available in the database. this screen gives you information about current generation jobs or jobs that may have already run (predictions regarding the duration of the generation. function groups. Choose components to generate © SAP AG 2003 You can use transaction SGEN to generate the ABAP loads of a number of programs. Generation over all components requires more than 2 GB of free space. If you want to generate loads. 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. and so on. classes. 1. (C) SAP AG ADM110 6-48 . function groups. and so on.SAP Load Generator (SGEN) Use transaction SGEN to generate ABAP loads of programs. and Business Server Page applications (BSP applications). Select Generate All Objects of Selected Software Components 2. The space required can be several hundred MB. classes.

© SAP AG 2003 For more information.UNICODE Post-Installation Procedure After installing Unicode. Execute the UMG_POOL_TABLE program. (C) SAP AG ADM110 6-49 . 2. refer to SAP Note 544623. 3. follow these steps: 1. Start transaction SE38. Log on to your SAP system.

Post-Installation Activities Restart SAP System and Final Checks SAP License SAP Online Documentation SAProuter TMS and Basic Configuration Additional Tasks Appendix © SAP AG 2003 (C) SAP AG ADM110 6-50 .

In this case.Windows: SAP Accounts Check that created SAP accounts never expire In user management. Log on to operating system. the installed system will not start anymore after 42 days have passed since the installation. Choose Start → Programs → Administrative Tools → Computer Management. If this option is not selected. the installed system will not start anymore after 42 days have passed since the installation." To fix the problem. the SAP management console reports the error. (C) SAP AG ADM110 6-51 . you must set the Password never expires option for the SAP accounts. "The service did not start due to a logon failure. the Password never expires option should be set for the created SAP accounts <sapsid>adm and SAPService<SID>. © SAP AG 2003 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. after trying to access the system.

<password> db_offline If SAP DB or liveCache is installed on the computer.Installing Administration Tools for a Database SAPDB Administration tools on Windows systems: You can use Database Manager GUI (DBMGUI) to administer databases. Install DBMGUI: <CD drive>:\NT\SETUPS\DBM74. including remote ones. Your computer must meet the following minimum operating system requirements: Windows NT 4. on any Windows computer in your network. DBMGUI and SQL Studio. you must not install the administration tools in the same directory. 100 MB of free disk space If you are prompted to restart the computer after the installation.<password> dbm_getpath IndepProgPath (C) SAP AG ADM110 6-52 . be sure to bring down all databases that are running as follows: dbmcli –d <SID> -u <controluser>.0 SP4 or Windows 2000 Pentium II. you can then administer the database or send queries to it. You can check the directories used by SAP DB or liveCache as follows: dbmcli –d <SID> -u <controluser>.EXE You can use SQL Studio to send SQL statements to the database and evaluate the results. From the computer with the installed administration tool.EXE © SAP AG 2003 You can install the SAPDB administration tools.<password> dbm_getpath IndepDataPath dbmcli –d <SID> -u <controluser>. Install SQL Studio: <CD drive>:\NT\SETUPS\SQLSTD74. even if your database runs on UNIX. 64 MB RAM.

Use SAPDBA to start an archive backup. see SAP Note 142635.sap file with this statement: brbackup -i force brarchive -i force Use SAPDBA to start a online backup for one tablespace.2. (C) SAP AG ADM110 6-53 .2. Install the SAP Backup Library or the Legato Storage Manager if you are using Oracle 9. Verify that the database is running.Completing and Checking Oracle Installation Make sure the database utilities brbackup and brarchive were installed correctly BRBACKUP Database backup Database backup BRARCHIVE Offline redo log file backup Install Legato Storage Manager for Oracle 9. For more information on how to install and use the SAP backup library and the Legato Storage Manager. Load a new tape in the tape station.x © SAP AG 2003 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> .x. Initialize all tapes defined by the profile parameters volume_backup and volume_archive in the init<SAPSID>.

check the selected system and choose OK 3. 2. 1. © SAP AG 2003 (C) SAP AG ADM110 6-54 . Log on as <new_user> Go to <DRIVE>:\USR\SAP\<SAPSID>\SYS\EXE\RUN and start NTREG2ENV. 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.EXE In window ntreg2env. you must perform this procedure.Informix Administrative Tools Only members of the Informix-Admin group can access administrative tools for Informix database Therefore.

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. follow these steps: Log on as user root on the host that exports the transport directory. you have to set the permissions of the transport directory /usr/sap/trans to 771. Enter chmod 771 /usr/sap/trans. (C) SAP AG ADM110 6-55 . To do this. Enter chmod 771 /usr/sap/trans © SAP AG 2003 For security reasons.UNIX: Performing File and Directory Adjustments UNIX For security reasons.

UNIX: Performing Operating System Adjustments UNIX: These adjustments are required if your operating system is AIX or HP-UX on HP/HPPA. AIX Check that perfagent is installed as follows: lslpp -l perfagent. To do this.server The AIX software perfagent must be installed for saposcol on AIX. group shared memories together as shared memory pools. (SAP Note 37537) © SAP AG 2003 (C) SAP AG ADM110 6-56 . HP-UX on HP/HPPA or AIX on IBM/RS6000 (32 bit) Improve performance by reducing the number of shared memories.

ADM100. CA940.Further Information SAP Service Marketplace.sap. http://service. ADM960 © SAP AG 2003 (C) SAP AG ADM110 6-57 .com/instguides Courses: ADM325. ADM102.

Post-Installation Activities: Unit Summary Now you are able to: Perform all necessary post-installation activities © SAP AG 2003 (C) SAP AG ADM110 6-58 .

for example. SM51 and SM21 to check work processes and the systemlog for errors. To do this. 6-3-2 Proceed as described in SAP note 30289 unit 3. and perform CTO and TMS activities. Create file saprouttab in directory G:\usr\sap\saprouter and add the entry: “P * * *“ (C) SAP AG ADM110 6-59 . 6-2-2 Request the hardware key. 6-3-1 Install SAProuter and create permission file saprouttab. start and configure SAProuter for SAPNet–R/3 Frontend access. 6-1-1 Stop and restart SAP system using the Microsoft Management Console. 6-2-1 Check whether a temporary license is installed.exe and niping.exe from directory G:\usr\sap\<SID>\SYS\exe\run.Post-Installation Activities Exercises Unit 6: Post-Installation Activities At the conclusion of this exercise. 6-1-2 Check the developer traces on operating system. log on to the server for your training system using the Terminal Server Client or pcAnywhere. such as adapt SAP profiles. in directory G:\SETUP\Adm110\SAP_Notes. twdf####. Then log on to SAP system and perform in SAP system transaction SM50. Use the executables saprouter. you will be able to: • Perform the necessary post installation activities After installing the system you will perform some important postinstallation steps. install SAP license. 6-3-3 Create route permission table saprouttab. 6-2 Check the installed license. 6-1 Restart SAP system and final checks. 6-3 Optional: Install.2 (Installation under Windows) step 1 and 2. SAP note 30289 is stored on your server used for the course.

Proceed as described in SAP note 30289 unit 3. 6-3-6 Check the technical settings in transaction OSS1. 6-5 Optional: Import and change the SAP profiles. 6-4 Optional: Perform the post-installation activities. Stop saprouter with the command saprouter –s. 6-6 Optional: Configure operation modes. 6-6-2 Maintain timetable for operation mode.2 (Installation under windows) step 4 and 5.). 6-8-1 Check profile parameter auth/no_check_in_some_cases. “Change and Transport Organizer” (CTO) and “Transport Management System” (TMS).m. 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-5-2 Change the values of the parameters concerning number of work processes (rdisp/wp_no_*). 6-8 Preparation steps before using profile generator (transaction PFCG). 6-3-5 Implement SAProuter as service.6-3-4 Start SAProuter Proceed as described in SAP note 30289 step 4. enter twice the number for dialog and batch work processes. for example.1 (Starting SAProuter). 6-4-2 Configure TMS. 6-6-1 Set up operation modes. 6-4-1 Perform post installation action in transaction SE06. 6-8-2 Initialize profile generator. 6-10 Optional: Perform a client copy 6-10-1 Create a new client in your SAP system. 6-7 Optional: Check standard background jobs 6-7-1 Schedule the standard background jobs. (C) SAP AG ADM110 6-60 . 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. 6-5-1 Import all profiles into your SAP system.

6-11-1 Check the profile parameter rdisp/j2ee_start.m.6-11 Check status of SAP J2EE Engine and of user SAPJSF. 6-13-1 Check whether the user option Password never expires is set for the SAP accounts <sid>adm and SAPService<SID>. 6-13 Optional: Check the SAP account on windows. 6-11-2 Check current state of SAP J2EE Engine using transaction SMICM. 6-11-3 Check whether user SAPJSF is locked. (C) SAP AG ADM110 6-61 . 6-12 SAP Load Generator 6-12-1 Start the SAP Load Generator and schedule the load generator for tomorrow 8 p.

either an individual instance or the entire SAP system is stopped. Select the desired instance(s). Start the Terminal Server Client or pcAnywhere and enter the physical host name. Select the desired instance(s). Start the Microsoft Management Console by double-clicking the appropriate icon. Start the dialog instance in the same way. such as adapt SAP profiles. and perform CTO and TMS activities.Solutions Unit 6: Post-Installation Activities At the conclusion of this exercise. Depending on whether you have chosen an individual instance or the SAP system. 6-1-1 Stop and restart SAP system using the Microsoft Management Console. right-click and choose Start. Choose the node for the central instance in the Microsoft Management Console tree. 6-1 Restart SAP system and final checks. right-click and choose the Stop function from the context menu. log on to the server for your training system using the Terminal Server Client or pcAnywhere. Log on to the operating system as user <sid>adm. you will be able to: • Perform the necessary post installation activities After installing the system you will perform some important postinstallation steps. (C) SAP AG ADM110 6-62 . To do this. install SAP license.

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. Start transaction SLICENSE (Tools → Administration → Administration → SAP Licenses) and choose Goto → Determine Hardware Key. using the windows explorer.1. 6-2 Check the installed license. (Starting SAProuter) Read the SAP note and follow its instructions in unit 4. Select your server.6-1-2 Check the developer traces on operating system. start and configure SAProuter for SAPNet–R/3 Frontend access. Use the executables saprouter. open the files dev_ms. dev_w# (#= 0. Read the SAP note and follow its instructions in unit 3. Proceed as described in SAP note 30289 unit 3. SM51 and SM21 to check work processes and the systemlog for errors. 6-2-2 Request the hardware key. for example. Log on to your SAP system. which are located in the instance directory (G:\usr\sap\<SID>\D*\work). dev_disp. (C) SAP AG ADM110 6-63 .2 (Installation under Windows) step 1 and 2. Then log on to SAP system and perform in SAP system transaction SM50. 1). Check the files due to errors. in directory G:\SETUP\Adm110\SAP_Notes. 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 * * *. The SAP server (Tools → Administration → Monitor → System Monitoring → Servers or transaction SM51) displays the active SAP instances.exe from directory G:\usr\sap\<SID>\SYS\exe\run. dev_rd.exe and niping.2 (Installation under Windows) step 1 and 2. 6-3-1 Install SAProuter. 6-2-1 Check whether a temporary license is installed.1 (Starting SAProuter). 6-3-3 Start SAProuter Proceed as described in SAP note 30289 step 4. On operating system. 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>. twdf####. SAP note 30289 is stored on your server for the training. 6-3 Optional: Install. Check system log to find errors (Tools → Administration → Monitor → System log or transaction SM21). choose Determn and choose Continue (green arrow).

6-5-2 Change the values of the parameters concerning number of work processes (rdisp/wp_no_*). Proceed as described in this training material on the page “Post-Installation Activities for Transport Organizer” with the setting Standard Installation. All profile files can be imported together by choosing Utilities → Import Profiles → Of active servers.2 (Installation under Windows) step 4 and 5. Proceed as described in this training material on the pages “TMS Configuration: Transport Domain” and “TMS Configuration: Transport Routes. “Change and Transport Organizer” (CTO) and “Transport Management System” (TMS). 6-4-2 Configure TMS. Do not select Database Copy ….” 6-4 Optional: Perform the post-installation activities. Choose Create and enter the name. Stop saprouter with the command saprouter –s.” 6-5 Optional: Import and change the SAP profiles. 6-5-1 Import all profiles into your SAP system. Switch to the Instances/Operation Modes view by choosing Instances/Operation Modes. To change the values of individual parameters. Create operation modes in transaction RZ04 (Tools → CCMS → Configuration → Operation Modes/Instances). 6-6 Optional: Configure operation modes. 6-3-5 Check the technical settings in transaction OSS1.2 (Installation under windows) step 4 and 5. You define work process distribution for all instances of your system by choosing Settings → Based on current status → New instances→ Create. Choose Save. enter twice the number for dialog and batch work processes.6-3-4 Implement SAProuter as service. 6-6-1 Set up operation modes. Call profile maintenance (Tools → CCMS → Configuration → Profile Maintenance or transaction RZ10). for example. Proceed as described in SAP note 30289 unit 3. Proceed as described in this training material on the page “Configuring SAProuter and SAPNet–R/3 Frontend. To change the distribution of the work processes for (C) SAP AG ADM110 6-64 . select the instance profile and change this in extended maintenance. Read the SAP note and follow its instructions in unit 3. 6-4-1 Perform post installation action in transaction SE06. A check log displays the result of the import.

6-7 Optional: Check standard background jobs 6-7-1 Schedule the standard background jobs.the operation modes of the instances. double-click the operation modes entries. Select the start and end of the period for operation mode by double-clicking the appropriate lines. Choose Assign and then select operation mode. Use transaction RSPFPAR to check the value of the parameter.” 6-9-2 Activate the SAP R/3 Enterprise extension set. Proceed as described in this training material on the pages “Installation Check. 6-6-2 Maintain timetable for operation mode. 6-8 Preparation steps before using profile generator (transaction PFCG). Choose Normal Operation and then Change. To schedule the standard jobs. Schedule operation modes using the operation mode calendar (Tools → CCMS → Configuration → Operation Mode Calendar. Choose Tools → Administration → Administration → Client Administration → Client Maintenance or start transaction SCC4. Transaction SM63). choose Save. (C) SAP AG ADM110 6-65 . Enter 100 in the Client field. Create a new client named 100. Adapt the change options for customizing.” 6-10 Optional: Perform a client copy 6-10-1 Create a new client in your SAP system. 6-8-1 Check profile parameter auth/no_check_in_some_cases. Jobs → Default scheduling. After you have changed the distribution for all operation modes and instances. It must be set to Y. choose Save. Choose New Entries. Switch to change mode. Proceed as described in this training material on page “Activation of SAP R/3 Enterprise Extension Set. choose Reorg. Proceed as described in this training material on the pages “Basic Configuration: User and Roles. Enter a client description and enter a city. Choose transaction SM36 (Tools → CCMS → Jobs → Definition) and choose Goto → Standard jobs. You change and then save the distribution of the work processes in the Maintain Work Process Distribution window by choosing + and -.” 6-9 Installation check and activation of SAP R/3 Enterprise extension set 6-9-1 Perform the installation check. After you have assigned the entire 24-hour period to your operation modes. Change the value if necessary using transaction RZ10 (see exercise 5) 6-8-2 Initialize profile generator.

6-11-1 Check the profile parameter rdisp/j2ee_start.). Choose User names → Lock to check whether the user SAPJSF is locked. The default setting is 1.” 6-11-3 Check whether user SAPJSF is locked. Select as source client 000.” (C) SAP AG ADM110 6-66 . 6-11 Check status of SAP J2EE Engine and of user SAPJSF.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. Proceed as described in this training material on page “SAP J2EE Engine.m. 6-11-2 Check current state of SAP J2EE Engine using transaction SMICM.). Use transaction RSPFPAR to check the value of the parameter. Log on to your new client with user SAP* and password pass. Proceed as described in this training material on page “SAP Load Generator (SGEN). Choose transaction SU01 (Tools → Administration → User maintenance → Users) and enter user SAP JSF. 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).m.m. Choose Schedule as Background Job (start time: tomorrow 8 a. 6-12 SAP Load Generator 6-12-1 Start the SAP Load Generator and schedule the load generator for tomorrow 8 p. Choose Tools → Administration → Administration → Client Administration → Client Copy → Local Copy.

Proceed as described in this training material on page “Windows: SAP Accounts. Log on to operating system and choose Start → Programs → Administrative Tools → Computer Management. 6-13-1 Check whether the user option Password never expires is set for the SAP accounts <sid>adm and SAPService<SID>.6-13 Optional: Check the SAP account on windows.” (C) SAP AG ADM110 6-67 .

New Features Installation Planning Installation Preparation Installing SAP GUI Installation Process Post-Installation Activities Implementing Patches Converting Non-Unicode to Unicode Troubleshooting Installation Problems (C) SAP AG ADM110 7-1 .Implementing Patches 1 2 3 4 5 6 7 8 9 © SAP AG 2003 SAP R/3 Enterprise Architecture.

Content and Objectives 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 (C) SAP AG ADM110 7-2 .

For updating the kernel.com/patches to your server Follow SAP Note 19466 Follow the screenshots given here Supportpackages status DB patch 35 Kernel: Before status © SAP AG 2003 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). follow the instructions given in SAP Note 19466 carefully.sap. 3. Download the latest kernel patch from http://service. DB-Dependent Part) Steps to be executed: 1.Applying a Kernel Patch (incl. 2. (C) SAP AG ADM110 7-3 .

) Save the old kernel. services. (C) SAP AG ADM110 7-4 . replace parts of the old kernel with the new files © SAP AG 2003 In the screenshots. 2. SAPOsCol. 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. read the SAP Note 502999 carefully. Decompress the kernel patch files to some temporary folder Follow SAP Note 19466 (stopping the system.10-based systems.. 3.. You should apply the kernel patches to all instance-specific exe directories.Applying a Kernel Patch. Screenshots (1/2) Steps to be executed: 1.

(C) SAP AG ADM110 7-5 . the communication program between SAP J2EE Engine and ABAP kernel. Screenshots (2/2) After status © SAP AG 2003 In the \usr\sap\<SID>\<Instance>\j2ee\cluster\server\additional-lib directory.Applying a Kernel Patch. The kernel patch (in the example above) brought the kernel up to patch level 783. you can find such files as sapjco. This directory contains some files that need to be updated during a kernel patch. as can be seen in System → Status.jar.

2.Patching the SAP J2EE Engine (1/2) Steps to be executed: 1.com/patches to your server Follow SAP Note 529088 Follow the screenshots given here Before status © SAP AG 2003 The SAP J2EE Engine also needs to be updated to ensure a stable environment. follow the instructions in SAP Note 529088. It is best to apply these patches when updating the kernel. Download the latest SAP J2EE Engine patch from http://service. (C) SAP AG ADM110 7-6 . 3. After downloading and decompressing the patch file.sap.

bat Choose correct folder Always choose Upgrade! After status © SAP AG 2003 Follow the instructions in SAP Note 529088.Patching the SAP J2EE Engine (2/2) Start visual. When applying a patch to an existing SAP J2EE Engine always select Upgrade. you would lose applications already deployed! You should upgrade all instance-specific SAP J2EE Engine directories in this manner. Select the correct folder for the update of the SAP J2EE Engine. otherwise. (C) SAP AG ADM110 7-7 .

This screenshots reminds you how Support Packages are applied. only the BASIS and ABA Support Packages are applied to the SAP R/3 Enterprise system.Apply Support Packages using Transaction SPAM Read SAP Note 447925 Note that TMS needs to be configured © SAP AG 2003 The use of transaction SPAM is explained in great detail in the course ADM100 – SAP Web AS Administration I. In the example in the screenshots. (C) SAP AG ADM110 7-8 . There are several other Support Package types.

SAP Note 81737 lists the operating system fixes that should be applied in an SAP environment. For DB2 on iSeries. refer to http://www. Because different database releases might have different patch strategies. The content of these notes might have been revised. When applying patches. Follow SAP Note 544304 for installing FixPaks for DB2 UDB.htm. Therefore.4soi. (C) SAP AG ADM110 7-9 . Follow SAP Note 159268 for installing Service Packs for Microsoft SQL Server. make sure that you are using the patch description that fits your database release. please check http://service. follow the instructions on how to fix the operating system. Follow SAP Note 45876 for installing Patches for Informix.sap.Applying a Database Patch Steps to be executed: Download the latest database patch http://service.sap. Follow SAP Note 530567 for installing Patches for SAP DB. Follow SAP Note 306408 for installing Interims Patches for Oracle using OPatch.com/instguides and go to Database Upgrades © SAP AG 2003 There are different procedures for applying patches for the different databases supported by SAP systems. Also check the SAP Notes noted in the figure before applying a database patch. For DB2 on zSeries. you will notice that even databases from the same vendor can differ significantly between releases.com/patches to your server.de/Infoapar. for DB2 on iSeries/zSeries see notes.

(C) SAP AG ADM110 7-10 . 3. you will find patches for dbmgui.Appendix: Installation of dbmgui for SAP DB (1/2) Steps to be executed: 1.sap.EXE (example given) Follow the screenshots given here © SAP AG 2003 On the SAP Service Marketplace.com/patches to your server Execute DBM7403_10-10001730. These patches contain actually updated. 2. Download latest dbmgui version from http://service. full installs.

Appendix: Installation of dbmgui for SAP DB (2/2) © SAP AG 2003 The installation procedure is straight-forward. (C) SAP AG ADM110 7-11 . Simply choose an installation directory and proceed as the installation procedure proposes.

Double-click: Register the database as shown in the screenshot: © SAP AG 2003 After successful installation.Appendix: Configuring dbmgui Perform these steps to configure dbmgui: 1. By default this password is control. you can start dbmgui by double-clicking the icon just created by the setup procedure. (C) SAP AG ADM110 7-12 . You are asked to provide the control user for the SAP DB named control and the correct password for this user. To administer databases using dbmgui. you will work with the <Local> setting (refer to the screenshot). SAP Note 25591 describes how you can change the password for user control and sapr3 and SUPERDBA. 2. Click in the box next to the database name and choose Register. For most purposes. For registration you may also choose remote servers where SAP DB engines reside. you must first register the databases to be controlled.

For more information on SAP DB. recovery and so on) are running on the database. (C) SAP AG ADM110 7-13 . © SAP AG 2003 After registering the database. Select the shutdown option Quick only under special circumstances. After stopping the SAP system.Appendix: Stopping the Database using dbmgui Steps to be executed: 3. you can shut down the database: 4. Start the SAP system. you can stop it by right-clicking the database icon in dbmgui and then choosing Set Offline. take the course ADM515 – Database Administration SAP DB. The database should switch into offline mode fairly soon unless some special activities (backup. restore. The database will be started automatically.

It may be necessary to adapt the environment variable PATH and reboot the server. dialog free update using the syntax: "SDBUPD –d <SID> -u control. you should get the result message shown in the screenshot really fast. Using the dialog free patch syntax for the SDBUPD program.com/patches to your server. Follow SAP Note 530567 for SAP DB (before executing step 3). 3. Follow the steps in the screenshots. 2.sap.Appendix: Applying a Database Patch for SAP DB Steps to be executed: 1.control" Result: © SAP AG 2003 After downloading and decompressing the database patch (using sapcar –xvf <filename>). Download the latest database patch http://service. It might be necessary to add a new entry to the system environment variable Path and reboot the server. (C) SAP AG ADM110 7-14 . follow the instructions in SAP Note 530567.

com/patches SAP Notes as listed in this unit © SAP AG 2003 (C) SAP AG ADM110 7-15 . http://service.Further Information SAP Service Marketplace.sap.

Implementing Patches: Unit Summary Now you are able to: List the elements of the SAP system that need patches Apply patches to the SAP system © SAP AG 2003 (C) SAP AG ADM110 7-16 .

You can start immediately with the step "Installing the patch. You find this SAP Note as a document in folder G:\SETUP\ADM110\SAP_Notes. 7-2-2 You find the patch to be applied in the following location: G:\SETUP\ADM110\ SAP_J2EE_Engine_Patch. (C) SAP AG ADM110 7-17 .Implementing Patches Exercises Unit 7: Implementing Patches At the conclusion of this exercise. 7-1-2 You find the patch to be applied in the following location: G:\SETUP\ADM110\Kernel_Patch Proceed as described in SAP Note 19466. Proceed as described in SAP Note 529088. 7-1-1 Check the current kernel patch level of your SAP system. 7-2-1 Check the current patch level of the SAP J2EE Engine." 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. 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-2-3 Check the new patch level of the SAP J2EE Engine. Note: You can skip steps 1 and 2 of the procedure described under "Copying and installing a patch. You find this SAP Note as a document in folder G:\SETUP\ADM110\SAP_Notes. you will be able to: • Apply a kernel patch • Apply an SAP J2EE Engine patch After installing the system.

Read the PatchLevel number. 7-1-2 You find the patch to be applied in the following location: G:\SETUP\ADM110\Kernel_Patch Proceed as described in SAP Note 19466. Note: You can skip steps 1 and 2 of the procedure described under "Copying and installing a patch. See 7-1-1.Implementing Patches Solutions Unit 7: Implementing Patches At the conclusion of this exercise. you will be able to: • Apply a kernel patch • Apply an SAP J2EE Engine patch After installing the system. 7-1 Apply a kernel patch to your newly installed SAP system. follow the instructions given in the SAP Note.Pkg lvl to find the information.txt in the directory <Drive>:\usr\sap\<SID>\<Instance>\j2ee\cluster\dispatcher\managers. Alternatively. 7-2-2 You find the patch to be applied in the following location: (C) SAP AG ADM110 7-18 . You find the kernel patch level under Kernel patch number. you will patch some of its components to the latest version available. 7-2-1 Check the current patch level of the SAP J2EE Engine. 7-2 Optional: Apply a patch to the SAP J2EE Engine of your SAP system." Again. 7-1-1 Check the current kernel patch level of your SAP system. select one instance and choose Release notes. Find the file version. You find this SAP Note as a document in folder G:\SETUP\ADM110\SAP_Notes. 7-1-3 Check the new kernel patch level of your SAP system. you can start transaction SM51. Use System → Status and choose Other kernel info → Sup.

follow the instructions given in the SAP Note. Note: You can start with the step "Installing the patch. (C) SAP AG ADM110 7-19 .G:\SETUP\ADM110\SAP_J2EE_Engine_Patch. You find this SAP Note as a document in folder G:\SETUP\ADM110\SAP_Notes." Again. Proceed as described in SAP Note 529088. 7-2-3 Check the new patch level of the SAP J2EE Engine. See 7-2-1.

New Features Installation Planning Installation Preparation Installing SAP GUI Installation Process Post-Installation Activities Implementing Patches Converting Non-Unicode to Unicode Troubleshooting Installation Problems (C) SAP AG ADM110 8-1 .Converting Non-Unicode to Unicode 1 2 3 4 5 6 7 8 9 © SAP AG 2003 SAP R/3 Enterprise Architecture.

you will be able to: List the necessary steps to convert non-Unicode to Unicode © SAP AG 2003 (C) SAP AG ADM110 8-2 .Content and Objectives Content: Preparation for the conversion to Unicode Procedure to perform a conversion non-Unicode to Unicode Post-conversion tasks Objectives: At the conclusion of this unit.

Default Conversion Method This is the default conversion method: Start an export of the entire database using R3Load Install a new Unicode database Import the database using R3Load again © SAP AG 2003 (C) SAP AG ADM110 8-3 .

20 or later.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 © SAP AG 2003 If the source system is an MDMP system.20 to 6.20 or later. (C) SAP AG ADM110 8-4 . These steps are described in SAP Note 573044. Therefore you must first upgrade a non-Unicode system with a Basis release earlier than 6. If you are using HR functionality within SAP R/3 Enterprise. You can convert to Unicode as soon as the non-Unicode system uses Basis release 6. additional steps are mandatory. Currently SAP does not support an upgrade with simultaneous Unicode conversion. perform the additional steps that are described in SAP Note 551344.

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) © SAP AG 2003 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. (C) SAP AG ADM110 8-5 .

the "R3load Procedure on Windows or Unix" section Prepare the SAPinst installation Run SAPinst to export the database © SAP AG 2003 (C) SAP AG ADM110 8-6 .20: Homogeneous and Heterogeneous System Copy.Actions on the Source System Perform an export of the source database See SAP note 548016 for some database dependent steps See documentation SAP Web Application Server 6.

Transferring the Export Files to the Target Host On the target host. 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. copy file file source system © SAP AG 2003 target system (C) SAP AG ADM110 8-7 . 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. create a directory <EXPDIR> with sufficient space for the database export files available.

(C) SAP AG ADM110 8-8 .Actions on the Target System (1/2) 1. the "Input for the Installation" section. Install the target database system Select System Copy / Migration in the Selecting the database instance installation method screen © SAP AG 2003 For instructions on how to install the target database system. look at the file DBSIZE. SAP Web Application Server on <Platform>: <Database>.XML located in the directory <DRIVE>:\<EXPDIR>\DB\<DATABASE> (Windows) or <EXPDIR>/DB/<DATABASE> (UNIX) 2. 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. refer to the installation guide.

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>. © SAP AG 2003 (C) SAP AG ADM110 8-9 . Continue the target database system installation as described in the installation guide.Actions on the Target System (2/2) In the General Load Parameters window.

For more information. MONI.Final Activities on the Target System (1/3) Activate logging mechanism of the database Run installation check: Installation Check (transaction SM28) Perform post installation activities (transaction SE06) with the Database Copy option This releases all transport. SAP Web Application Server 6. repair. DBSNP. SDBAR. SDBAD.20: Homogeneous and Heterogeneous System Copy. Execute the RSBTCDEL program and select the Delete with forced mode field to delete cancelled and finished jobs Check the consistency of the Temporary Sequential Objects (TemSe) using transaction SP12. SDBAP. (C) SAP AG ADM110 8-10 . see SAP Note 16875 © SAP AG 2003 Refer to the installation guide. and customizing requests that have not been released in the source system. PAHI. the "Final Activities" section. SDBAH. Delete all entries from the following tables: ALCONSEG. OSMON. ALSYSTEMS.

the "Final Activities" section. SAP Web Application Server 6. (C) SAP AG ADM110 8-11 . which holds the repair requests from your source system. remove old ones.20: Homogeneous and Heterogeneous System Copy. These contain information about changes made to the profile of your source system Delete all entries from table TLOCK. 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.Final Activities on the Target System (2/3) Adapt the definition of the printers to meet the new system requirements Delete entries in table DDLOG for buffer synchronization. Synchronize the buffers as described in SAP Note 25380 Adapt the client information for the logical systems Adapt the RFC destinations (transaction SM59) and clean the transactional RFCs (transaction SM58) Create new operation modes. © SAP AG 2003 Refer to the installation guide.

If you encounter problems modifying a customer package using transaction SMTS or SM31. modify the corresponding entries in table TADIR.20: Homogeneous and Heterogeneous System Copy.) (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. etc. update statistics. © SAP AG 2003 Refer to the installation guide. the "Final Activities" section. (C) SAP AG ADM110 8-12 . use Validate (ENTER) instead of Save to save your changes. SAP Web Application Server 6.Final Activities on the Target System (3/3) Reschedule cancelled jobs Redefine database actions (backup.

Further Information SAP Service Marketplace. http: //service.sap.sap.com/instguides 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 (C) SAP AG ADM110 8-13 .com/unicode SAP Service Marketplace. http://service.

Converting Non-Unicode to Unicode: Unit Summary Now you are able to List the necessary steps to convert non-Unicode to Unicode © SAP AG 2003 (C) SAP AG ADM110 8-14 .

Troubleshooting 1 2 3 4 5 6 7 8 9 © SAP AG 2003 SAP R/3 Enterprise Architecture. New Features Installation Planning Installation Preparation Installing SAP GUI Installation Process Post-Installation Activities Implementing Patches Converting Non-Unicode to Unicode Troubleshooting Installation Problems (C) SAP AG ADM110 9-1 .

Content and Objectives 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 (C) SAP AG ADM110 9-2 .

Troubleshooting Guideline and Restart of the Installation Examples: Problems with SAPinst Examples: Problems during Installation © SAP AG 2003 (C) SAP AG ADM110 9-3 .

… to SAP ftp server sapservX 4. Copy the following files from your installation directory <SAPinst_INSTDIR> to sapserv<X> (see SAP Note 40024): . sapinst_dev. 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. sapinst_dev. Create a customer message via SAP Service Marketplace (http://service.com/message) or SAP Net .com/sapinstfeedback and find the SAPinst troubleshooting guide).log . Check if it is a known problem: SAP notes mentioned in installation guide SAPinst troubleshooting guide SAP notes located on service.keydb.log.xml. © SAP AG 2003 Go to the end of sapinst. You can find details about the error situation and the step that failed. Implement the solution and continue the installation.sap.Guideline to Solve Problems Try these steps to solve problems: 1. Known problem: Search for SAP notes using SAP Service Marketplace containing possible solutions. if sapinst.log and search for the message type ERROR. Search in SAP notes provided by the installation guide or other troubleshooting guides (go to service.com/notes 3.log refers to other log files in the relevant sections.log for the message type ERROR 2.Additional log file(s).sap. check these log files too.sap.xml.R/3 Frontend using the component BC-INS. Check the file sapinst. Check if it is a unknown problem: Repeat the command on the operating system.log reference the file(s) in the error message. (C) SAP AG ADM110 9-4 . If sapinst. check if the return code gives more information Create a customer message Copy files keydb.

xml. SAPinst records the installation progress in file keydb. The installation can be contuinued from the failed step without repeating previous steps. © SAP AG 2003 (C) SAP AG ADM110 9-5 .Restart Installation (1/5) SAPinst does not abort the installation in error situations.

© SAP AG 2003 (C) SAP AG ADM110 9-6 .Restart Installation (2/5) 1. Continue an installation that was not cancelled: Error dialog box is still displayed and SAPinst is waiting for your input. Choose Retry.

/sapinst © SAP AG 2003 (C) SAP AG ADM110 9-7 . problem is solved. There are two alternatives: a. Continue an installation that was cancelled Installation was aborted. Continuing the installation Windows: Unix: Start SAPinst from <SAPinst_INSTDIR> with: .Restart Installation (3/5) 2. and you want to restart.

start the installation with the default keydb.1./sapinst © SAP AG 2003 (C) SAP AG ADM110 9-8 .<no>.xml files Start SAPinst from your <SAPinst_INSTDIR> with: .Restart Installation (4/5) b. Windows: 1 2 UNIX: Rename keydb.xml file (delivered by SAP) to keydb. that is.xml file as delivered.xml Delete all keydb. Restart from scratch.

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.CMD (Windows). (C) SAP AG ADM110 9-9 . © SAP AG 2003 Reset the installation after using the Cancel button. the phase in which you enter the parameters). you have to restart the installation from CD with SETUP. If you cancel the installation in the dialog phase of SAPinst with Cancel.Restart Installation (5/5) Dialog phase: Reset the installation after using the Cancel button in the dialog phase of SAPinst (that is. Restart Installation Processing phase: The installation can be cancelled and continued in the processing phase.

70 534334: Composite SAP note Installation/Upgrade SAP R/3 Enterprise 523505: INST: SAP R/3 Enterprise 4.70 on Windows General 531372: INST: SAP R/3 Enterprise 4.70 / 4. 6. / Gateway Inst.70 on Windows .SAP DB Other SAP Notes for other databases © SAP AG 2003 (C) SAP AG ADM110 9-10 . for SAP R/3 Enterprise 4.20 545422: INST: SAP J2EE Engine Inst.70 SR1 on UNIX 529151: INST: SAP R/3 Enterprise 4.SAP Notes with Known Installation Problems SAP Notes: 492305: INST: SAP J2EE Engine / Dialog Inst.

Set environment variable FLOW_TRACE to enabled.Flow Trace Flow Trace provides more detailed information about the installation progress and success. Start SAPinst as follows: sapinst SAPINST_MESSAGE_THRESHOLD=flow_trace © SAP AG 2003 (C) SAP AG ADM110 9-11 . For detailed information during error situations. 2. restart SAPinst as follows: 1.

Troubleshooting Guideline and Restart of the Installation Examples: Problems with SAPinst Examples: Problems during Installation © SAP AG 2003 (C) SAP AG ADM110 9-12 .

one on Windows and one on UNIX: Press any key to continue and choose an unused port on this host. start SAPinst with special parameters: <SAPinst CD>/SAPINST/UNIX/ \ <platform>/INSTALL -port \ <free_port_number> (C) SAP AG ADM110 9-13 .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: © SAP AG 2003 There are two ways to solve the problem and start SAPinst.\sapinst.xml SAPINST_DIALOG_PORT=<port> (where <port> is an unused port on your host) On UNIX.exe SAPINST_CONTROL_URL=control_bootstrap. start SAPinst with special parameters: . On Windows.

jar files from Non-SAP-XML parsers (for example.. enter xhost +<name> where <name> is the host name of the Xhost.jar) in your JRE ext directory UNIX: You use an Xserver with incorrect permissions to perform the installation on another UNIX host (Xhost) Solution Check if there are already <xml_parser>.Example 2: Local Settings ERROR Messages: Trace [iaoxcguist.xxx. © SAP AG 2003 (C) SAP AG ADM110 9-14 . <JAVA_HOME>\JRE\lib\ext (on Windows) / <JAVA_HOME>/JRE/lib/ext (on UNIX).jar files in the ext directory.cpp:110] dostart GUI( ): dostart GUI( ) returns. On the Xserver.. Cause: SAPinst GUI start-up error due to local settings. Rename those files to xerces. Known reasons are: Pre-existing *. xerces.

but the library path environment variable is not set correctly. Extend your LD_LIBRARY_PATH environment variable with " ./sapinst © SAP AG 2003 (C) SAP AG ADM110 9-15 . Run SAPinst again: . 2.Example 3: Library Path ERROR Messages: ERROR: fatal: sapcppstd. Solution 1.so open failed: no such file or directory Cause You have started SAPinst on operating system Solaris or Compaq True 64.": setenv LD_LIBRARY_PATH .

Troubleshooting Guideline and Restart of the Installation Examples: Problems with SAPinst Examples: Problems during Installation © SAP AG 2003 (C) SAP AG ADM110 9-16 .

© SAP AG 2003 (C) SAP AG ADM110 9-17 ..bck already seems to exist a previous run may not have been finished cleanly file /.Example 1: R/3 Load ERROR Messages: ERROR in SAP<TABART>./<SID>/DB/SAPAPPL0.TSK./<SID>/DB/SAPAPPL0.TSK possibly corrupted /sapmnt/<SID>/exe/R3load: job finished with 1 error(s) /sapmnt/<SID>/exe/R3load: END OF LOG: 20011213092725 Cause Error in the processing sequence of the R/3 load Solution Read SAP Note 455195.log : file /..

Actual value is 0.25].Example 2: Oracle Redologs ERROR Messages: MDB-06055 : Range error: Field numberOriglogDirs must be in range [2. Cause You 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. Solution 1. Copy the file keydb. Create Online Service System error message © SAP AG 2003 (C) SAP AG ADM110 9-18 .xml from your installation directory <SAPinst_INSTDIR> to sapserv (SAP Note 40024) 2.

/sapinst in the <SAPinst_INSTDIR>. Check the correctness of your copied files anyway 2.Example 3: Installation CDs ERROR Messages: MOS-01011: DBR3LOADEXEC_IND_IND InternalInstallationDo:0 SyFilesWithPatternRead (NULL) returned with 0STR FILES FOUND: 0 Cause You perform an SAP system installation on UNIX and the installation CDs was probably copied manually to disk. Solution 1. © SAP AG 2003 (C) SAP AG ADM110 9-19 . 1. "SOLARIS/AIX: Copying CDs" 3. Solaris / AIX: During the copy procedure an unwanted automatic conversion of all file and directory names occurs. The installation CD was copied incompletely to disk. If you find lowercase letters repeat the copy procedure as described in SAP Note 459899 in topic. changing all uppercase letters to lowercase ones. 2. Continue the installation by running .

Example 4: SAP J2EE Engine © SAP AG 2003 Solution: Restart the SAP system to stop and start the SAP J2EE Engine. (C) SAP AG ADM110 9-20 .

Or open the file keydb. © SAP AG 2003 (C) SAP AG ADM110 9-21 . Cause During installation you entered a password longer than 8 characters for the communication user SAPJSF. continue the installation by choosing SAPinst → <Menu_Entry> → SAPinst Server with GUI from the Windows Start menu.Example 5: Communication User SAPJSF ERROR Messages: FRF-00048 Value <Entered_Password> is invalid for parameter IF_PASSWORD. Then. Solution Either restart the installation by starting SAPinst from the CD.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.

xml file.Restriction You must not modify the SAPinst XML files. especially the keydb. unless SAP delivers a description for the modification. © SAP AG 2003 (C) SAP AG ADM110 9-22 .

com/instguides SAP Service Marketplace.sap.Further Information SAP Service Marketplace.com/notes © SAP AG 2003 (C) SAP AG ADM110 9-23 .sap. http://service. http://service.

Installation Processes: Unit Summary Now you are able to: Handle SAPinst and installation problems Restart an installation © SAP AG 2003 (C) SAP AG ADM110 9-24 .

Sign up to vote on this title
UsefulNot useful