tadm12_1 en col99 fv part ltr

TADM12_1SAP NetWeaver AS

Implementation & OperationII

SAP NetWeaver

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 99Course Duration: 10 DaysMaterial Number: 50118034

An SAP course - use it to learn, reference it for work

Copyright

Copyright 2013 SAP AG or an SAP affiliate company. All rights reserved.

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

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

Trademarks

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks ofAdobe Systems Incorporated in the United States and other countries.

Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Citrix, ICA, Program Neighborhood, MetaFrame now XenApp, WinFrame, VideoFrame, andMultiWin are trademarks or registered trademarks of Citrix Systems Inc.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

Edgar Online is a registered trademark of EDGAR Online Inc., an R.R. Donnelley & Sons Company.

Facebook, the Facebook and F logo, FB, Face, Poke, Wall, and 32665 are trademarks of Facebook.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, GoogleMobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater,Google Voice, Google Mail, Gmail, YouTube, Dalvik, and Android are trademarks or registeredtrademarks of Google Inc.

HP is a registered trademark of the Hewlett-Packard Development Company L.P.

HTML, XML, XHTML, and W3C are trademarks, registered trademarks, or claimed as genericterms by the Massachusetts Institute of Technology (MIT), European Research Consortium forInformatics and Mathematics (ERCIM), or Keio University.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, Systemz, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, PowerSystems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter,System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarksor registered trademarks of IBM Corporation.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks of Microsoft Corporation.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

IOS is a registered trademark of Cisco Systems Inc.

The Klout name and logos are trademarks of Klout Inc.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Mozilla and Firefox and their logos are registered trademarks of the Mozilla Foundation.

Novell and SUSE Linux Enterprise Server are registered trademarks of Novell Inc.

g201331611644

OpenText is a registered trademark of OpenText Corporation.

Oracle and Java are registered trademarks of Oracle and its affiliates.

QR Code is a registered trademark of Denso Wave Incorporated.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch,BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld aretrademarks or registered trademarks of Research in Motion Limited.

SAVO is a registered trademark of The Savo Group Ltd.

The Skype name is a trademark of Skype or related entities.

Twitter and Tweet are trademarks or registered trademarks of Twitter.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

SAP, R/3, ABAP, BAPI, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjectsExplorer, StreamWork, SAP HANA, the Business Objects logo, BusinessObjects, Crystal Reports,Crystal Decisions, Web Intelligence, Xcelsius, Sybase, Adaptive Server, Adaptive Server Enterprise,iAnywhere, Sybase 365, SQL Anywhere, Crossgate, B2B 360 and B2B 360 Services, m@gicEDDY, Ariba, the Ariba logo, Quadrem, b-process, Ariba Discovery, SuccessFactors, Executionis the Difference, BizX Mobile Touchbase, It's time to love work again, SuccessFactors Jam andBadAss SaaS, and other SAP products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germany or an SAP affiliate company.

All other product and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National product specificationsmay vary.

Disclaimer

These materials are subject to change without notice. These materials are provided by SAP AG andits affiliated companies (SAP Group) for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to thematerials. The only warranties for SAP Group products and services are those that are set forth inthe express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

g201331611644

g201331611644

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal and external.

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. v

About This Handbook TADM12_1

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor'spresentation.

vi 2013 SAP AG or an SAP affiliate company.

All rights reserved. 2013/Q1

Contents

Course Overview ......................................................... xvCourse Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

Unit 1: Overview and Architecture of SAP Systems............... 1

Overview of SAP Systems... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Technical Architecture of SAP Systems... . . . . . . . . . . . . . . . . . . . . . . . . . 13

Unit 2: Preparing an Installation...................................... 27

Introducing SAPinst.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28General Preparation for Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Additional Preparation for Installation on Windows... . . . . . . . . . . . . 54Additional Preparation for Installation on UNIX ... . . . . . . . . . . . . . . . . 64

Unit 3: Installing SAP Solution Manager ........................... 73

Installation of SAP Solution Manager .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Installation of a Secondary Application Server.. . . . . . . . . . . . . . . . . . . 90

Unit 4: Planning an Installation...................................... 101

Planning the Installation... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Unit 5: Installation of SAP ECC (AS ABAP)....................... 123

Installation of SAP ECC.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Unit 6: Installation of SAP XSS (AS Java)......................... 139

Installation of SAP XSS ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141

Unit 7: Performing Post-Installation Activities................... 155

Overview of Post-Installation Steps ... . . . . . . . . . . . . . . . . . . . . . . . . . . . .158Completing the Installation of SAP Enhancement Packages 6 for

SAP ERP 6.0 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167SAP License, Online Documentation, Remote Connection to SAP

Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173Initial Configuration for an AS ABAP based SAP System ... . . .192Initial Configuration of an AS Java based SAP System ... . . . . .221Appendix: Installation of Standalone SAP Gateway ... . . . . . . . . .229

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. vii

Contents TADM12_1

Unit 8: Installation of SAP GUI....................................... 243

Optional: Installation of SAP GUI for Windows and SAP GUI forJava ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244

Optional: Installation and Usage of SAP GUI InstallationServer.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255

Unit 9: Patching SAP Systems....................................... 271

Software components of SAP systems that can be patched...275Patching SAP Solution Manager 7.1, Initial Shipment Stack...278Patching SAP Systems... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306SAP Notes and SAP Support Packages... . . . . . . . . . . . . . . . . . . . . . . .322Preparation for Software Maintenance... . . . . . . . . . . . . . . . . . . . . . . . . .331Support Package Manager (SPAM) and Software Update

Manager (SUM) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357Applying SAP Support Packages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367Java Support Packages, Stacks and Patches ... . . . . . . . . . . . . . . . .383Importing Corrections with SUM for AS Java ... . . . . . . . . . . . . . . . . .389Appendix: Importing Corrections with JSPM.... . . . . . . . . . . . . . . . . .404SAP Enhancement Packages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .416

Unit 10: Output Management......................................... 427

Configuring Printers in AS ABAP ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .429Concept of Logical Spool Servers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .455Managing Spool Requests.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .467Printing Assistant for Landscapes (PAL).. . . . . . . . . . . . . . . . . . . . . . . . .476

Unit 11: Scheduling Background Tasks ........................... 501

Fundamentals of Background Processing ... . . . . . . . . . . . . . . . . . . . . .503Time-Based Scheduling of Jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .517Event-Based Scheduling of Jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .531Background Processing: Further Topics .. . . . . . . . . . . . . . . . . . . . . . . . .543Job Scheduling with SAP Central Process Scheduling by

Redwood ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .561Appendix: Job Management .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .583

Unit 12: SAPconnect and SMTP..................................... 591

Communication with SAPconnect .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .592Communication Using SMTP... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .600

Glossary................................................................... 635

Index ....................................................................... 639

viii 2013 SAP AG or an SAP affiliate company.


Course OverviewTADM12 complements the knowledge and skills gained in TADM10.

Courses TADM10 and TADM12 are largely independent of the type of operatingsystem and database technology.

Like the other TADM courses, TADM12 comprises several individual courses (orparts thereof), which are arranged here in a way that will enable you to gain theknowledge you require as an SAP Technology Consultant as efficiently as possible.

Week 1 of course TADM12 is based on content taken from the followingcourses:

1. ADM110

2. ADM800

3. ADM100

4. ADM102 - updated exclusively for TADM12

5. TADM12 also contains elements that are not part of any other trainingcourse (2 lessons in Unit 9)

Week 2 of course TADM12 is based on content taken from the followingcourses:

1. ADM325

2. ADM103

3. ADM900/GRC100

Caution: Special note on the schedule/flow of activities in this part ofyour education track.

The first week of TADM12 is a challenge to your wits, you will learnmore than you thought.

In its first half, the training material describes, in logical sequence, allnecessary steps for the planning and execution of SAP system installationsand post-installation activities.

During the installation and patch activities you will encounter lengthyperiods of system activity without required input from your part.

Those non-interactive installation times will be used for covering othertopics contained in this training handbook.

Therefore, the actual sequence in which the training material will becovered will be different from the logical sequence of the units in thistraining handbook.

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. ix

Contents TADM12_1

We do this to use otherwise long periods of non-activity for passing onknowledge to you. After this weeks training, for your personal rehearsal,it will help you to work through the training material in its original,logical order.

Please take some minutes to take note of the following.

During TADM12, first week, your tasks will include the installation of severalSAP systems:

1. S00, an SAP MaxDB-based SAP Solution Manager 7.1 system

2. E00, an Sybase ASE-based SAP ECC 6.06 (-ready) system

3. X00, an SAP MaxDB-based SAP XSS system

In addition to that you will learn (among several other tasks):

1. How to use the Printing Assistant for Landscapes (PAL) to manage printerdefinitions for several SAP systems from one central SAP system

2. How to use SAP Central Process Scheduling (SAP CPS) to define and triggerjobs in remote SAP systems, using an AS Java-based application

3. How to send SMTP-based e-mails from an SAP system to an external mailinfrastructure

Those latter three tasks require some special setup in the SAP systems in whichyou would like to execute them. To let you configure that setup within theown-installed SAP systems would be very time-consuming and is not possiblewithin this week.

Therefore, the setup you will be using for this weeks training looks somewhatadvanced. The server that you will be using hosts initially (start of the trainingweek) several SAP systems, as follows:

1. DCC, an SAP MaxDB-based SAP ECC 6.06 (-ready) system,preconfigured for the tasks in units 10, 11 and 12.

2. QCC, an SAP MaxDB-based SAP ECC 6.06 (-ready) system,preconfigured for the tasks in units 10, 11 and 12.

3. PCC, an SAP MaxDB-based SAP ECC 6.06 (-ready) system,preconfigured for the tasks in units 10.

4. PSM, an SAP MaxDB-based SAP Solution Manager 7.1 system,preconfigured for the tasks in units 10 and 11.

5. DEP, an SAP MaxDB-based SAP NetWeaver Portal 7.31 system,not required during TADM12, first week.

6. QEP, an SAP MaxDB-based SAP NetWeaver Portal 7.31 system,not required during TADM12, first week.

7. PEP, an SAP MaxDB-based SAP NetWeaver Portal 7.31 system,not required during TADM12, first week.

8. NDI, an SAP MaxDB-based SAP NWDI system,

x 2013 SAP AG or an SAP affiliate company.


TADM12_1 Contents

not required during TADM12, first week.

9. TRX, an SAP TRex system, not required during TADM12, first week.

Note: Before your training starts, your instructor will execute somescripts that prepare all systems listed above, as required for this weekof TADM12.

Caution: Available disk space will become an issue during the first weekof TADM12, unless the following steps are executed.

Note: Before you start the installation of the first new SAP system (SID:S00), please follow the procedure that your instructor demonstrates toremove (COMPLETELY) the SAP systems named DEP, QEP, PEPand NDI (including their corresponding databases and file systemstructures). Those instructions will include the script-based full shutdownof all existing SAP systems (including the databases) on your trainingserver.

Note: After the successfully finished installation of the first SAP system(S00), you will follow the advice of your instructor to remove the thenno longer required Installation media to free up disk space, take carenot to delete files that you will need later on. This is described at thestart of Unit 5.

Caution: During the long-running non-interactive phases of theinstallation/patch procedures, your instructor will cover material fromseveral units and you start using the already available SAP ECC systems(DCC) to cover some content - e.g. - lessons 1 to 3 from unit 10 andlessons 1 to 4 from unit 11.

This will require the startup of SAP system DCC, while in parallelsome non-interactive installation steps are executed on your hardwareas described at the start of Unit 5.

The systems DCC, QCC, PCC and PSM are updated and technicallyconfigured for Units 10, 11 and 12. Theoretically, you could reach thisstate of configuration with your own-installed SAP systems as well, butthis would require significant time and more knowledge than is the scopeof this weeks training.

Lessons 4 of unit 10, 5 of unit 11 and unit 12 require the startup ofadditional SAP systems (QCC, PCC, PSM) and should be executedwithout parallel installation or patch processes running.

This schedule requires quick-thinking from you - as do real-life projectsthat you will encounter as an SAP Technology Consultant. So, take thechallenge!

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. xi

Contents TADM12_1

Sequence of installation-related activities - Schedule

Unit number Remarks

Unit 2:Preparing anInstallation

Lesson: General Preparation for Installation, ExecuteExercise 1, using the OS-user TADM12. Considerthe changes to Exercise 1 given at the start of Unit 2.

Unit 3:InstallingSAP SolutionManager

Lesson: Installation of SAP Solution Manager,Execute Exercise 3, using the OS-user TADM12.Consider the changes to Exercise 3 given at the startof Unit 3.

> Take care NOT to run two installation proceduresat the same time on the same server

TADM12_1 Contents

During those wait times you will cover content from other parts of thetraining material, in the sequence described in the table below.

Please make sure to check now and then the progress of the installationand patch activities.

Sequence of Units and Lessons to be covered duringnon-interactive parts of the installation and patch exercises -Schedule

Unit number Remarks

Unit 1:Overview andArchitecture ofSAP Systems

Both lessons - this content will be covered during thedialog-free part of the installation of the SAP SolutionManager


Lessons 1, 3 and 4 will be covered during thedialog-free part of the installation of the SAP SolutionManager

Unit 4:Planning anInstallation

Lesson: Planning the Installation will be coveredduring the dialog-free part of the installation of theSAP Solution Manager

In case, the installation of the SAP Solution ManagerSystem is not finished after covering Unit 4, observethe following advice:You can start with Unit 7 when the installation of theSAP Solution Manager has reached phase ConfigureSystem Landscape Directory.After SAPinst has finished successfully, you shouldtake a break from Unit 7 and start the installationof the SAP ECC system (Unit 5, below) and returnto Unit 7 after the installation of the SAP ECC systemhas reached the dialog-free phase.

Unit 7:PerformingPost-InstallationActivities

Cover all lessons and Exercises 7, 8 and 9. Considerthe changes to the Exercises given at the start of Unit7. The post-installation activities will take some time.

Unit 8:Installation ofSAP GUI

This Unit is optional - usually, the tasks describedherein are not executed by SAP system administrators.You can cover it theory-only.

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. xiii

Contents TADM12_1

The following lessons can be taught during thenon-dialog phase of the Support Package StackApplication (several hours!), they provide backgroundknowledge to the activities for lesson Patching SAPSolution Manager 7.1, Initial Shipment Stack:Patching SAP Systems,SAP Notes and SAP Support Packages,Preparation for Software Maintenance,Support Package Manager (SPAM) and SoftwareUpdate Manager (SUM),Applying SAP Support Packages,Java Support Packages, Stacks and Patches,Importing Corrections with SUM for AS Java,Appendix: Importing Corrections with JSPM,SAP Enhancement Packages.In case the Support Package Stack Application runsfor a longer time then needed for the coverage of thelessons listed above, you will start covering contentfrom Unit 10: Output Management as described below.

Unit 10:OutputManagement

Lesson: Configuring Printers in AS ABAP andExercise 16, requires the start of SAP system DCC oneach training server.Use the credentials that your instructor provides.In case the Support Package Stack Application won'tbe finished after covering the lesson ConfiguringPrinters in AS ABAP, you can continue with lessons2 and 3 of Unit 10. Cover lesson 4 only after thesuccessful application of the Support Package Stack.In case the Application of the Support Package Stackis still not finished after lesson 1 to 3 of Unit 10, youcan start with lessons 1 to 4 of Unit 11. Lesson 5 ofUnit 11 should be covered after all installation andpatch activities have been finished successfully.

In case the Support Package Stack Application hasbeen finished successfully, you can continue with someactivities from lesson Patching SAP Solution Manager7.1, Initial Shipment Stack, namely the following:11. Applying an additional Kernel patch and12. Switch to SAP JVM.

xiv 2013 SAP AG or an SAP affiliate company.


TADM12_1 Course Overview

Steps 13 - 15 (of the lesson Patching SAP SolutionManager 7.1, Initial Shipment Stack) are optionaland you succeeded in patching a newly installed ASABAP+Java-based SAP system. Congratulations!

Now, the training will continue with all lessons andunits still open, as described in the training handbook(Units 10, 11 and 12).

Target Audience

This course is intended for the following audiences:

SAP Technology Consultants (Associate Level)

Course Prerequisites

Required Knowledge

Knowledge of the content of TADM10

Course GoalsThis course will prepare you to:

Work as a Technology Consultant (Associate) within the SAP environment

Install, configure and maintain SAP systems based on SAP NetWeaver ASABAP

Install, configure and maintain SAP systems based on SAP NetWeaver ASJava

Course Objectives

After completing this course, you will be able to:

process basic tasks within the technology environment of SAP systems

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. xv

Course Overview TADM12_1

xvi 2013 SAP AG or an SAP affiliate company.


Unit 1Overview and Architecture of SAP

Systems

Unit OverviewThis unit explains the SAP Business Suite, the solutions inside (SAP ERP, SAPCRM, SAP SCM, SAP SRM) and the SAP systems within these solutions from atechnical point of view.

Caution: During the long-running non-interactive phases of theinstallation/patch procedures, your instructor will cover material fromseveral units and you start using the already available SAP ECC systems(DCC) to cover some content - e.g. - lessons 1 to 3 from unit 10 andlessons 1 to 4 from unit 11.

This will require the startup of SAP system DCC, while in parallelsome non-interactive installation steps are executed on your hardwareas described at the start of Unit 5.

The systems DCC, QCC, PCC and PSM are updated and technicallyconfigured for Units 10, 11 and 12. Theoretically, you could reach thisstate of configuration with your own-installed SAP systems as well, butthis would require significant time and more knowledge than is the scopeof this weeks training.

Lessons 4 of unit 10, 5 of unit 11 and unit 12 require the startup ofadditional SAP systems (QCC, PCC, PSM) and should be executedwithout parallel installation or patch processes running.

This schedule requires quick-thinking from you - as do real-life projectsthat you will encounter as an SAP Technology Consultant. So, take thechallenge!

Sequence of installation-related activities - Schedule

2013/Q1 2013 SAP AG or an SAP affiliate company. All rights reserved. 1

Unit 1: Overview and Architecture of SAP Systems TADM12_1

Unit number Remarks


Lesson: General Preparation for Installation, ExecuteExercise 1, using the OS-user TADM12. Considerthe changes to Exercise 1 given at the start of Unit 2.

Unit 3:InstallingSAP SolutionManager

Lesson: Installation of SAP Solution Manager,Execute Exercise 3, using the OS-user TADM12.Consider the changes to Exercise 3 given at the startof Unit 3.

> Take care NOT to run two installation proceduresat the same time on the same server

TADM12_1 Unit 1: Overview and Architecture of SAP Systems

During those wait times you will cover content from other parts of thetraining material, in the sequence described in the table below.

Please make sure to check now and then the progress of the installationand patch activities.

Sequence of Units and Lessons to be covered duringnon-interactive parts of the installation and patch exercises -Schedule

Unit number Remarks

Unit 1:Overview andArchitecture ofSAP Systems

Both lessons - this content will be covered during thedialog-free part of the installation of the SAP SolutionManager


Lessons 1, 3 and 4 will be covered during thedialog-free part of the installation of the SAP SolutionManager

Unit 4:Planning anInstallation

Lesson: Planning the Installation will be coveredduring the dialog-free part of the installation of theSAP Solution Manager

In case, the installation of the SAP Solution ManagerSystem is not finished after covering Unit 4, observethe following advice:You can start with Unit 7 when the installation of theSAP Solution Manager has reached phase ConfigureSystem Landscape Directory.After SAPinst has finished successfully, you shouldtake a break from Unit 7 and start the installationof the SAP ECC system (Unit 5, below) and returnto Unit 7 after the installation of the SAP ECC systemhas reached the dialog-free phase.

Unit 7:PerformingPost-InstallationActivities

Cover all lessons and Exercises 7, 8 and 9. Considerthe changes to the Exercises given at the start of Unit7. The post-installation activities will take some time.

Unit 8:Installation ofSAP GUI

This Unit is optional - usually, the tasks describedherein are not executed by SAP system administrators.You can cover it theory-only.



The following lessons can be taught during thenon-dialog phase of the Support Package StackApplication (several hours!), they provide backgroundknowledge to the activities for lesson Patching SAPSolution Manager 7.1, Initial Shipment Stack:Patching SAP Systems,SAP Notes and SAP Support Packages,Preparation for Software Maintenance,Support Package Manager (SPAM) and SoftwareUpdate Manager (SUM),Applying SAP Support Packages,Java Support Packages, Stacks and Patches,Importing Corrections with SUM for AS Java,Appendix: Importing Corrections with JSPM,SAP Enhancement Packages.In case the Support Package Stack Application runsfor a longer time then needed for the coverage of thelessons listed above, you will start covering contentfrom Unit 10: Output Management as describedbelow.

Unit 10:OutputManagement

Lesson: Configuring Printers in AS ABAP andExercise 16, requires the start of SAP system DCC oneach training server.Use the credentials that your instructor provides.In case the Support Package Stack Application won'tbe finished after covering the lesson ConfiguringPrinters in AS ABAP, you can continue with lessons2 and 3 of Unit 10. Cover lesson 4 only after thesuccessful application of the Support Package Stack.In case the Application of the Support Package Stackis still not finished after lesson 1 to 3 of Unit 10, youcan start with lessons 1 to 4 of Unit 11. Lesson 5 ofUnit 11 should be covered after all installation andpatch activities have been finished successfully.

In case the Support Package Stack Application hasbeen finished successfully, you can continue with someactivities from lesson Patching SAP Solution Manager7.1, Initial Shipment Stack, namely the following:11. Applying an additional Kernel patch and12. Switch to SAP JVM.

4 2013 SAP AG or an SAP affiliate company.


TADM12_1 Unit 1: Overview and Architecture of SAP Systems

Steps 13 - 15 (of the lesson Patching SAP SolutionManager 7.1, Initial Shipment Stack) are optionaland you succeeded in patching a newly installed ASABAP+Java-based SAP system. Congratulations!

Now, the training will continue with all lessons andunits still open, as described in the training handbook(Units 10, 11 and 12).

Unit ObjectivesAfter completing this unit, you will be able to:

Describes the architecture of the SAP Business Suite, the SAP solutions andthe SAP systems from a technical point of view

List the technical processes of an AS ABAP based SAP system

List the technical processes of an AS Java based SAP system

Reflect the combination of SAP systems and Unicode

Unit ContentsLesson: Overview of SAP Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Lesson: Technical Architecture of SAP Systems ... . . . . . . . . . . . . . . . . . . . . . . . . . 13



Lesson: Overview of SAP Systems

Lesson OverviewThis lesson describes the architecture of the SAP Business Suite, the SAPsolutions and the SAP systems from a technical point of view.

Lesson ObjectivesAfter completing this lesson, you will be able to:


Business ExampleDescribes the architecture of the SAP Business Suite, the SAP solutions and theSAP systems from a technical point of view.

SAP Business Suite, SAP Solutions, SAP SystemsThe SAP Business Suite consists of several SAP Solutions:

SAP ERP: SAP Enterprise Resource Planning

SAP CRM: SAP Customer Relationship Management

SAP SCM: SAP Supply Chain Management

SAP SRM: SAP Supplier Relationship Management

SAP PLM: SAP Product Lifecycle Management

The blargest and most wide-spread used solution is SAP ERP.

Note: Another term for SAP Solution is SAP Application. This term isespecially used for SAP ERP.

The SAP Solutions consist of several installable units, the SAP systems. The byfar biggest SAP system, containing the most business functions, is SAP ECC -formerly known as SAP R/3 Enterprise - formerly known as SAP R/3.

Note: SAP ECC stands for SAP Enterprise Resource Planning CentralComponent - because it is the central component of SAP ERP.

The more technical SAP systems from the different solutions are also called SAPNetWeaver systems.

Caution: There are many more components inside SAP Business Suitethan listed here.



TADM12_1 Lesson: Overview of SAP Systems

Figure 1: SAP Business Suite

Because SAP ERP is the largest SAP Solution and SAP ECC is the largestComponent we will look at these - as an example - in more detail.

Besides many others, SAP ERP contains the following SAP systems:

SAP ECC: SAP ERP Central Component

SAP XSS: SAP Employee and Manager Self Services

SAP BW: SAP NetWeaver Business Warehouse

SAP Portal: SAP NetWeaver Portal

SAP PI: SAP NetWeaver Process Integration

SAP MDM: SAP NetWeaver Master Data Management

Some of these SAP systems also belong to SAP NetWeaver: SAP BW, SAPPortal, SAP PI, SAP MDM.



Figure 2: Example: SAP ERP

Several renamings took place in the past; here are a few of them:

1. SAP R/3 was renamed to SAP R/3 Enterprise beginning with 4.7, and againwas renamed to SAP ECC beginning with 6.0.

2. SAP Basis was renamed to SAP Web Application Server (SAP Web AS)beginning with 6.10, and again was renamed to SAP NetWeaver ApplicationServer (SAP NetWeaver AS) beginning with 7.00.

3. SAP Business Warehouse (SAP BW) was renamed to SAP BusinessIntelligence (SAP BI), and was renamed back to SAP BW.

4. SAP Exchange Infrastructure (SAP XI) was renamed to SAP ProcessIntegration (SAP PI).

5. SAP Enterprise Portal (SAP EP) was renamed to SAP NetWeaver Portal.

6. ...

In addition, every SAP customer needs to run an additional SAP system: the SAPSolution Manager system. It is needed to implement, control and support the SAPsystem landscape. SAP Solution Manager is mandatory for several administrativetasks: for example patching the SAP systems and upgrading them.

For more information concerning SAP ERP consult the Installation Master Guideat SAP Service Marketplace, Quick Link instguides or SAP Service Marketplace,Quick Link erp.




Releases

The new release of the SAP Business Suite in mid 2012 is SAP Business Suite7i2011. The previous SAP Business Suite release was SAP Business Suite 7i2010.

Within SAP Business Suite 7i2011 the fours major Solutions have the followingreleases:

SAP ERP 6.06 - actually: SAP Enhancement Package 6 for SAP ERP 6.0

SAP CRM 7.01 - actually: SAP Enhancement Package 1 for SAP CRM 7.0

SAP SCM 7.01 - actually: SAP Enhancement Package 1 for SAP SCM 7.0

SAP SRM 7.01 - actually: SAP Enhancement Package 1 for SAP SRM 7.0

The major component within SAP ERP is SAP ECC. These are the releases ofSAP ECC, that are still in maintenance by SAP in 2012:

Figure 3: SAP ECC: Releases

No SAP R/3 release exists for SAP Basis/SAP Web AS/SAP NetWeaver AS 4.6D,6.10 and 7.10. Concerning the ABAP part, SAP Web AS 6.30 is the same as SAPWeb AS 6.20 (with more SAP Support Packages).

SAP ECC 6.06 is somewhat special, even while System Status reveals thatSAP_BASIS is of release 7.31, technically it is using SAP Enhancement Package3 for SAP NetWeaver 7.0. This should not confuse you, both releases (7.31,7.03) are functionally identical as far as AS ABAP is concerned.



Software ComponentsUsing the example of an up to date (June 2012) SAP ECC 6.06 system, we want tohave a look at the software components.

Figure 4: Software Components

Note: These are only the major software components of an SAP ECC6.06. There are many more.

The kernel is no software component. It is the runtime environment to run thesoftware components. The kernel is database and operating system depending.It is available for several operating systems and databases. For details see theProduct Availability Matrix at SAP Service Marketplace, Quick Link pam. thekernel is also called SAP Application Server or SAP Instance or Dispatcher andWorkprocesses.

The software components SAP_BASIS and SAP_ABA and others form the basis.They contain the basis functionality, like user administration, performance tools,the Transport Management System (TMS), development tools and so on.

The basis software components together with the kernel are also called SAPNetWeaver Application Server. In case of an ABAP based system (like SAPECC) abbreviated with AS ABAP, in case of a Java based system (like SAP XSS)abbreviated with AS Java.




The software components on top of the AS ABAP (or AS Java) are applicationspecific software components. They are not to much of interest here.

Examples for SAP system based on AS ABAP are:

SAP ECC

SAP BW

SAP CRM Server

SAP SCM Server

SAP SRM Server

Examples for SAP system based on AS Java are:

SAP XSS

SAP Portal

In addition there are two SAP system based on AS ABAP and AS Javasimultaneously, so called dual stack systems:

SAP Solution Manager

SAP PI



Lesson Summary

You should now be able to:




TADM12_1 Lesson: Technical Architecture of SAP Systems

Lesson: Technical Architecture of SAP Systems

Lesson OverviewIn this lesson, you will learn about the structure and the processes of an SAPsystem, and how to use the terms system and instance correctly. Also you willlearn about SAP systems and Unicode.





Business ExampleYou want to learn about the architecture of an SAP system.

AS ABAP and AS Java based SAP SystemsFor the installation procedure you have to understand the architecture of an SAPsystem.

An SAP system consists of the components shown in the graphic: One databaseand one or more instances. The instance that, together with the database, forms afunctional SAP system is also known as the central instance. There is not morethan one central instance installed for every SAP system. A central system is anSAP system consisting out of only the central instance and the database, runningon the same host.

It is possible to install two instances of an SAP system or even of different SAPsystems on one host. Before you install two SAP systems (and possibly theirdatabases) on one host, you should examine the extent to which the chosenhardware is capable of handling the anticipated load. Other aspects to beconsidered are situations such as upgrades or restore scenarios - for example, oneSAP system is to be recreated from a backup whilst the other SAP system shouldcontinue to be used without interference.

Within a company, no SAP system IDs (SIDs) should be used more than once.

An instance of an SAP system is an administrative unit in which components of anSAP system that provide one or more services are combined. The services withinone instance are started or stopped together.

There are three different types of SAP systems:



AS ABAP based - for example SAP ECC or SAP BW

AS Java based - for example SAP XSS or SAP Portal

AS ABAP + Java based - only SAP Solution Manager and SAP PI

The (ABAP) dispatcher is the central process of an ABAP instance. This processstarts other processes that belong to the instance, such as the gateway (abbreviatedas GW in the graphic), the Internet Communication Manager (ICM), and aconfigured number of work processes.

You configure an ABAP instance using an instance profile. The ABAP instancehas shared (main) memory areas and its own directory structure in the file system.

Figure 5: AS ABAP based SAP System

An (ABAP) instance consists of a dispatcher and several work processes. Aninstance requires a minimum of two dialog work processes. Otherwise it is notpossible to start it. Several instances can be installed on the same host. Theinstances must then have different instance numbers. The instance number is atwo-digit number, and is chosen at installation. It defines a range of standardcommunication ports for processes of the instance. The standard port of thedispatcher is 32$$ where $$ denotes the instance number. For example 3200 if theinstance number 00 was chosen at installation. If several instances are installed ona shared host, these instances use their own, separate, (main) memory areas, andeach instance has its own directory structure in the file system.

Hint: You should not use the instance numbers 98 and 99, because theyare reserved for the SAProuter.




An SAP system can have several instances. One of them is the central instance. Itincludes an additional process the ABAP Message Server which only existsonce across the system. Furthermore, the central instance is the only instance thatoffers one or more enqueue work processes.

Hint: Note that this definition of the term central instance cannot beused in the sense described when the ABAP Central Services Instance(ASCS) is installed. You will find a description of the ASCS concept inthe appendix to this lesson.

An instance is also called an application server. The application server providesthe runtime environment for the business applications of an SAP system.

The (Java) dispatcher is the central process of a Java instance. This processdistributes the incoming requests to the available server processes.

Figure 6: AS Java based SAP System

A Java instance consists of a Java dispatcher and one or more server process.Several instances can be installed on the same host.

A (Java-based) SAP system can have several instances. One of them is the (Java)central instance. It includes an additional process - the Software DeploymentManager (SDM) - which can only be configured once across the SAP system.There is also a Java Central Services (SCS or CS) instance. This CS instance offersthe Java Message Server and the Java Enqueue Server. In the standard installation,the Java central instance and the CS instance are located on the same host.



You can install additional Java instances on the same host together with the centralinstance or on other separate hosts.

AS ABAP+Java-based instances (dual stack instances) offer ABAP and Java-basedprocesses. This results in the following definition of a central instance: The centralinstance of an AS ABAP+Java-based SAP system offers all the processes of anABAP central instance and a Java central instance.

The Java Central Services instance does not belong to the AS ABAP+Java centralinstance. It is started and stopped separately.

Note: The Java server processes are not the equivalent to the ABAPwork processes: the Java server processes distribute the incoming workto underlying so called threads. So the Java server processes are kind ofsub-dispatchers.

Note: In AS Java releases starting from 7.10, there will be no Javadispatcher any longer. Instead the load balancing is been done by aJava ICM process.

Figure 7: AS ABAP+Java based SAP System

An AS ABAP+Java-based SAP system always provides one ABAP+Java-basedcentral instance. Other instances are also AS ABAP+Java-based.

Caution: Again: avoid installing AS ABAP+Java based (dual stack)systems! Exceptions: SAP PI and SAP Solution Manager.




Since several releases it is almost not possible to install other dual stack systemsany longer . This is because of several problems and high costs related to thisarchitecture.

Hint: In case you are still running a dual stack systems that was installedin former days, there is a possibility to split it up into an AS ABAP and asecond AS Java based SAP system.

This can be done using the installation tool SAPinst.

Appendix: ABAP Central Services (ASCS)As of SAP NetWeaver 7.0, for high availability AS ABAP+Java-based SAPsystems (such as SAP systems on Windows clusters), you have to set up a separateinstance for central services instance for AS ABAP systems, the ABAP CentralServices (ASCS). The ASCS instance enables you to separate the ABAP MessageServer and the ABAP Enqueue Service (not implemented as a work process in thiscase) from the ABAP central instance. This cluster will then contain the ASCSinstance and the database. Outside the cluster, you may have any number of ABAPinstances of equal priority. This means that there is no longer any central instancein your SAP system. The same concept occurs in AS Java-based SAP systems ofthe installation standard: the (Java) Central Services instance with a Java messageserver and Java enqueue server. On the Java side, the concept is still referred to asa central instance because the Software Deployment Manager is installed here.

Hint: You will find more information about the ASCS instance here:

SAP Note 1010990 - Configuring a Standalone Gateway in an HA ASCinstance

SAP Note 1011190 - MSCS: Splitting the Central Instance After Upgradeto 7.0/7.1

You will also find further information on installing and configuring ASCSinstances in the corresponding installation and upgrade guide for yourSAP system at SAP Service Marketplace, Quick Link instguides.

Usage TypesThe solutions of SAP Business Suite 7i2011 are based on SAP NetWeaver 7.31(SAP Enhancement Package 3 for SAP NetWeaver 7.3), which in turn consistsof Usage Types.



SAP NetWeaver systems are configured for a certain purpose, as indicated byUsage Types.

are structuring element for SAP software on a technical level.

determine the intended purpose of an SAP system.

are realized by installing and configuring a collection of softwarecomponents.

may require other Usage Types in the same SAP system to operate.

The following lists the usage types for SAP NetWeaver:

Application Server ABAP (AS ABAP)

Application Server Java (AS Java)

Enterprise Portal Core (EPC)

Enterprise Portal (EP)

Business Intelligence (BI)

Business Intelligence Java Components (BI Java)

Development Infrastructure (DI)

Mobile Infrastructure (MI)

Process Integration (PI)

AS ABAP is the basis of SAP ABAP systems.

AS Java is the basis of SAP Java systems.

EPC provides full portal capabilities.

EP adds additional capabilities such as knowledge management and collaborationto EPC. Usage Type EPC is therefore a prerequisite for Usage Type EP.

BI provides Business Warehouse (BW) capabilities, such as Enterprise DataWarehousing, Enterprise Reporting, Query, and Analysis, and Business Planningand Analytical Services.

BI Java is used to provide the Java runtime for IT scenarios such as EnterpriseReporting, Query, and Analysis as well as Business Planning and AnalyticalServices. It enables variants such as Information Broadcasting and Ad-hoc Query& Analysis. It also enables Web Dynpro-based BI applications and third party dataaccess via Universal Data Integration. BI Java requires Usage Types EP and EPCore in the same SAP system. BI Java is BEx Web (Business Explorer Web).

DI provides the environment for all processes of Java-based development andJava-based software life-cycle management.

MI is used to enable field personnel to participate in a business process in anoccasionally connected mode.




PI consists of core components that model, design, automate, and integrateprocesses in one or more application systems. For the integration of internal andcross-company processes, PI is used to incorporate several the functions. PI wasformerly known as XI (Exchange Infrastructure).

UnicodeUnlike other standard code pages, Unicode defines a character set that includesvirtually all characters used worldwide and as a result provides consistent,global character encoding. Unicode is defined by the Unicode consortium(see http://www.unicode.org for more information), which consists of leadingcompanies in the world-wide IT industry.

Figure 8: SAP Unicode and Non-Unicode Solution

Up to and including SAP ERP 2004, SAP has provided multiple language supportusing single code pages as well as multiple code pages in a single installation withMDMP (Multi-Display-Multi-processing), which permits the application serverto dynamically switch code pages according to the logon language and languagekeys (see SAP Note 73606). However, even in an MDMP system, an individualuser can use only the characters belonging to one code page at a time. To enhancelanguage support for SAP Business Suite systems, SAP considers Unicode theappropriate development direction and strategy because Unicode offers a single,



consistent, and standard character set encoding for virtually all languages in theworld. A code page describes the assignment of one character to one hexadecimal(HEX) value. One (normal: 1 byte) code page represents 256 characters.

SAP systems support around 40 different languages.

Only languages belonging to the same code page are usable withoutrestrictions, unless you install Unicode-based SAP systems

Up to and including SAP ECC 5.0, SAP supported multiple languages withMulti-Display-Multi-Processing (MDMP) systems.

Since SAP ECC 6.0 MDMP is not supported any longer. SAP recommendsto use Unicode as the standard technology to cover multilingual languagerequirements.

Single code page systems (Non-MDMP) are still supported for existing SAPsystems, but not any longer for new installations.

Hint: SAP recommends to convert existing SAP systems to Unicode assoon as possible. New installations can only be performed as Unicodeinstallations.

Since SAP ECC 6.0 MDMP is not supported any longer. SAP recommends to useUnicode. An upgrade from an existing SAP system older than SAP ECC 6.0 toSAP ECC 6.0 and above requires a system conversion to Unicode. You can findmore information atSAP Service Marketplace, Quick Link unicode andSAP Note 79991,SAP Note 540911,SAP Note 745030 andSAP Note 73606.

Generally single code page systems (Non-MDMP / Non-blended code pages) arestill supported (with restrictions mentioned e.g. inSAP Note 858869 andSAP Note 838402).

However SAP strongly recommends Unicode (for new installation see SAP Note838402).New releases of SAP NetWeaver and SAP applications based on SAP NetWeaver,which are released in 2007 or later, will no longer support new installations ofNon-Unicode systems.Also see SAP Note 379940.

Unicode is the recommended system type for all SAP systems that deployUnicode-enabled solutions and components.




Unicode is the mandatory system type for:

SAP systems requiring a combination of languages that are based on morethan one non-Unicode code page

SAP systems that deploy Java applications (for example Java applications,WebDynpro applications)

SAP AS ABAP systems that communicate with Java components



Lesson Summary





Related Information

SAP NetWeaver

- SAP Library at https://help.sap.com: Documentation SAP NetWeaver SAP NetWeaver 7.0 English SAP NetWeaver Library

- SAP Developer Network at irj/sdn/netweaver

SAP ECC and SAP ERP: SAP Service Marketplace, Quick Link erp

Unicode: SAP Service Marketplace, Quick Link unicode

MCOD: SAP Service Marketplace, Quick Link mcod



TADM12_1 Unit Summary

Unit SummaryYou should now be able to:






Unit Summary TADM12_1



TADM12_1 Test Your Knowledge

Test Your Knowledge

1. SAP ECC 6.06 and SAP R/3 4.6C are two completely different SAP systems(offering different business functions), which are shipped by SAP.Determine whether this statement is true or false.

True

False

2. SAP supports Unicode, Non-unicode and MDMP with SAP ECC 6.06installations.

Determine whether this statement is true or false.

True

False


Test Your Knowledge TADM12_1

Answers

1. SAP ECC 6.06 and SAP R/3 4.6C are two completely different SAP systems(offering different business functions), which are shipped by SAP.

Answer: False

Over years, SAP developed SAP R/3 4.6C with additional functionality toSAP ECC 6.06.

2. SAP supports Unicode, Non-unicode and MDMP with SAP ECC 6.06installations.

Answer: False

With SAP ECC 6.0 and above MDMP is not supported any longer.



Unit 2Preparing an Installation

Unit OverviewThis unit explains how to prepare the installation of an SAP system.

Note: Regarding Exercise 1, the following changes are required toconsider:

1. Log on to the operating system of the training server using the userTADM12, the password will be provided by your instructor.

2. The installation of the JDK works on the second attempt.

3. Set the JAVA_HOME environment variable for the user TADM12.

Unit ObjectivesAfter completing this unit, you will be able to:

Start and use SAPinst

Name the log files used by SAPinst

Perform the general preparation steps needed to install an SAP system

Perform the necessary preparation steps to install an SAP system onWindows

Perform the necessary preparation steps to install an SAP system on UNIX

Unit ContentsLesson: Introducing SAPinst .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Lesson: General Preparation for Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Exercise 1: Prepare the Installation Part 1/2.. . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Lesson: Additional Preparation for Installation on Windows ... . . . . . . . . . . . . 54

Exercise 2: Prepare the Installation Part 2/2.. . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Lesson: Additional Preparation for Installation on UNIX... . . . . . . . . . . . . . . . . . 64


Unit 2: Preparing an Installation TADM12_1

Lesson: Introducing SAPinst

Lesson OverviewThis lesson describes how to use SAPinst.




Business ExampleAs the system administrator, you would like to know some details on startingand using SAPinst.

Overview of SAPinstSAPinst includes a SAPinst GUI and a GUI server, which both use a Java RuntimeEnvironment.

In a standard installation SAPinst, SAPinst GUI, and the GUI server run onthe same host. If required, you can instead perform a remote installation withSAPinst, whereby SAPinst GUI is running on a separate host from SAPinst andthe GUI server.

When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUIconnects to the GUI server with a secure SSL connection, and the GUI serverconnects to SAPinst.

Starting SAPinstThe following procedure starts SAPinst forWindows on a single host:

1. Log on to your host as a user who is a member of the local administrationgroup.

2. Start SAPinst from the installation master DVD. Double-click sapinst.exefrom in the directory :\IM_WINDOWS_

Caution: Do not use user adm to do installations.



TADM12_1 Lesson: Introducing SAPinst

Figure 9: Start SAPinst on Windows

SAPinst normally creates the installation directory sapinst_instdir, where it keepsits log files, and which is located directly in the Program Files directory. IfSAPinst is not able to create sapinst_instdir there, it tries to create sapinst_instdirin the directory defined by the environment variable TEMP. SAPinst creates asubdirectory for each installation service.

Note: We recommend that you keep all installation directories until thesystem is completely and correctly installed.

The SAPinst Self-Extractor extracts the executables to a temporary directory(TEMP, TMP, TMPDIR, or SystemRoot). These executables are deleted afterSAPinst has stopped running. Directories called sapinst_exe.xxxxxx.xxxxsometimes remain in the temporary directory. You can safely delete them.The temporary directory also contains the SAPinst Self-Extractor log filedev_selfex.out, which might be useful if an error occurs.

Hint: If SAPinst cannot find a temporary directory, the installationterminates with the error FCO-00058.



If you want to terminate SAPinst and the SAPinst Self-Extractor, choose one ofthe following options:

Right-click the icon for the SAPinst output window located in the Windowstray and choose Exit.

Click the icon for the SAPinst output window located in the Windows trayand choose File Exit.

On UNIX you start SAPinst in the following way:

1. Log on to your host as user root.

2. Start SAPinst from the installation master DVD with the command ./sapinst.

Caution: Make sure that the root user has not set any environmentvariables for a different SAP system or database.

SAPinst normally creates the installation directory sapinst_instdir directly belowthe temporary directory. SAPinst finds the temporary directory by checking thevalue of the environment variables TEMP, TMP, or TMPDIR. If no value is setfor these variables, SAPinst uses /tmp as default installation directory. Make surethat the temporary directory has the permissions 777.

The SAPinst self-extractor extracts the SAPinst executables to the temporarydirectory. These executables are deleted again after SAPinst has stopped running.If required, you can terminate SAPinst and the SAPinst Self-Extractor by pressingCTRL+C. The temporary directory also contains the SAPinst Self-Extractor logfile dev_selfex.out, which might be useful if an error occurs.

Caution: Make sure that your operating system does not delete thecontents of the temporary directory /tmp or the contents of the directoriesto which the variables TEMP, TMP, or TMPDIR point, for example byusing a crontab entry.

Hint: If SAPinst cannot find a temporary directory, the installationterminates with the error FCO-00058.

During the installation, the default ports 21200 and 21212 and 4239 areused for communication between SAPinst, GUI server, SAPinst GUI, andHTTP server. SAPinst uses port 21200 to communicate with the GUI server.The GUI server uses port 21212 to communicate with SAPinst GUI. 4239is the port of the HTTP server, which is part of the GUI server. You getan error message if one of these ports is already in use by another service.In this case start sapinst with the following command line parameters:SAPINST_DIALOG_PORT=GUISERVER_DIALOG_PORT=GUISERVER_HTTP_PORT=




To get a list of all available SAPinst properties, start SAPinst with the parameter -p:

Windows: sapinst.exe -p

UNIX: ./sapinst -p

Remote Installation with SAPinstSAPinst can also be used to perform a remote installation. This enables you toinstall an SAP system on another host (the remote host) while monitoring theinstallation with the SAPinst GUI on your local Windows or UNIX host (thelocal host).

Figure 10: Remote Installation with SAPinst

Prerequisites to perform a remote installation with SAPinst are:

Both hosts are on the same network and can ping each other.

SAPinst Server uses the ports 21200 and 21212 to communicate withSAPinst GUI. If one of these ports is used by another service, SAPinst givesan error message.



Start SAPinst using the following procedure:

1. Log on to your remote host

Windows: as a user who is a member of the local administration group.

UNIX: as root.

2. Start SAPinst form the installation master DVD using the followingcommand:

Windows: sapinst.exe -nogui

UNIX: ./sapinst -nogui

3. On your local host start SAPinst GUI by executing the following command:

Windows: startinstgui.bat -host

UNIX: ./startInstGui.sh -host

. For this you need to have access to the installation master DVD fromyour local host.

Hint: For a list of options to start SAPinst GUI, change to thesame directory as your SAPinst executable and enter the commandstartinstgui.bat -h on Windows and ./startInstGui.sh -h on UNIX.

Troubleshooting with SAPinstIf an error occurs, SAPinst stops the installation and displays a dialog informingyou about the error. In this case, you can view the log file by choosing View Log.If you can solve the error manually, you can do during leaving SAPinst opened.After you fixed the problem choose Retry to continue the installation.

Hint: There are some known error situations where you can choose Retryand SAPinst will continue without any error.




Figure 11: SAPinst Error Log: sapinst_dev.log

All the installation information is logged in several log files. The main SAPinstoutput files contain the following information:

sapinst.log - information on installation progress

sapinst_dev.log - records all messages of every installation step in detail

The log files sapinst.log and sapinst_dev.log can be found in the currentinstallation directory.

Additional log files might be written during the installation process. The additionallogs are referenced in sapinst.log and sapinst_dev.log.

The logs of SAPinst GUI and the GUI Server are written to the folder

%userprofile%\.stdgui (Windows)

/.stdgui (UNIX)

If SAPinst GUI does not start, check the file sdtstart.err in the current%userprofile% (Windows) or (UNIX) directory.



SAPinst - XML files

SAPinst is controlled by XML files. The main XML files are:

dialog.xml - contains all dialogs used in the installation

keydb.xml - SAPinst records the installation progress and user input in thekeydb.xml file

messages.xml - contains all messages used in the installation

control.xml - contains the component definition used by SAPinst

packages.xml - for software package administration

SAPinst GUI HandlingWhen using the SAPinst GUI, the following functions are available on the differentSAPinst GUI dialogs (input screens, installation progress screen, message boxes):

Function Description

F1 Displays detailed information about each input parameter.

Back Displays the previous dialog for editing.

Next Displays the next dialog for editing.

Cancel Cancels the installation with the following options:

Stop

Stops the installation without further changing theinstallation files. You can restart SAPinst to continue theinstallation later from this point..

Continue

Continues the installation.

Log Off Stops the SAPinst GUI, but SAPinst and the GUI servercontinue running. You can later reconnect to the same SAPinstinstallation from the same or another host by starting SAPinstGUI separately.

View Log Displays the content of the sapinst.log file during theinstallation.

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

Stop Stops the installation without further changing the installationfiles. You can continue the installation later from this point.

Continue Continues with the option you have chosen before.




Lesson Summary






Lesson: General Preparation for Installation

Lesson OverviewThis lesson explains the general preparation steps needed to install an SAP system.



Business ExampleYou want to perform the general preparation steps needed to install an SAP system.

Steps for Preparing a SAP System InstallationThe following steps need to be performed as preparation for the installation of anSAP system.

General Installation Preparation Steps

Download the installation DVDs.

Read the required installation guides

Read all required SAP Notes as listed in the installation guides.

Install/update SAP front-end components like SAP GUI for Windows.

Install Java Runtime Environment for SAPinst - depending on the need.

Set environment variable for SAPinst.

Install Java Development Kit for SAP NetWeaver AS Java (depending onusage types and operation system) - depending on the need.

Set environment variable for SAP NetWeaver AS Java.

Download Java Cryptography Extension (JCE) Unlimited StrengthJurisdiction Policy Files for AS Java based SAP systems).

Check if the necessary hardware and software requirements are fulfilled(Prerequisites Check).

Caution: Please be aware of the following facts:

Newer versions of SAPinst (as used in this course) do not require aseparately installed Java Runtime Environment, they bring their own.

Newer installations of SAP systems (e.g. SAP Solution Manager 7.1SR1) automatically use SAP JVM.



TADM12_1 Lesson: General Preparation for Installation

Figure 12: Download Installation DVDs

Read Installation Guides and SAP Notes

Figure 13: Read the Installation Guides



For each installation, you should read the corresponding installation guide for yourspecific combination of operating system and database system. It can be foundat SAP Service Marketplace, Quick Link instguides.

You should read it carefully before starting the installation process. Have theinstallation guide ready during the installation to follow each successive stepof the installation procedure.

Read relevant SAP Notes

Read the current version of all the relevant SAP Notes. These SAP Notes containadditional information that is required when performing an installation. The SAPNotes can be found on the SAP Service Marketplace, Quick Link notes.

Read only the SAP Notes relevant for your specific installation.

To avoid known problems read them carefully before beginning an installation.

Have all the relevant SAP Notes at hand during the installation so that you canquickly solve potential problems that might occur.

Install SAP Front-End Software

Figure 14: Install SAP Front-End Software

Ensure that the front-end software is installed on at least one host in yoursystem environment. To simplify the administration of your SAP system, it isrecommended that you do this on the central instance host.




For more information on installing the front-end software, refer to thecorresponding unit of this class and the separate documentation:

SAP Front-End Installation Guide (English version)

SAP Frontend-Installationsleitfaden (German version)

Make DVDs available

The master guide lists the DVDs you need for the installation in the MediaInformation section. The installation guide lists the DVDs you need for theinstallation in the Preparation chapter.

Download all required DVDs and make them assessable to the host, the SAPsystem should be installed on.

JRE/JDK Installation

SAPinst is a Java based tool and thus needs a Java Runtime Environment (JRE)to be installed. If you will later on install Java based SAP software on thesame host, make sure to install the right version, if possible. For example SAPNetWeaver AS Java 7.02 needs the full J2SE SDK (Java 2 Standard EditionSoftware Development Kit), also called JDK (Java Development Kit). In thisJDK also the JRE is contained, which also works for SAPinst. Always check theProduct Availability Matrix on SAP Service Marketplace, Quick Link pam for thesupported version of the JDK. In addition following SAP Note 723909 - Java VMsettings for J2EE 6.40/7.0 provides helpful information.

Caution: Please be aware of the following facts:

Newer versions of SAPinst (as used in this course) do not requirea separately installed Java Runtime Environment, they bring theirown. For AS ABAP-based SAP-system this is the case starting fromEHP6 for SAP ECC 6.0. For AS Java-based SAP systems, this isthe case starting from SAP NetWeaver 7.1.

Newer installations of SAP systems (e.g. SAP Solution Manager7.1 SR1) automatically use SAP JVM. In this course, we will stillsee the old world as we are installing SAP Solution Manager 7.1(initial shipment).



The steps are described in detail in the following figures on the example ofWindows 2008 R2 Server x64 Edition.

Note: For UNIX operating systems it is also mandatory to install theJRE and or JDK (depending on the release of the installed product). Thedetails on those installations are not included here.

Note: If you are installing your SAP system on an Oracle database,be aware that the Oracle installer also installs an JRE on the databasehost. The location of this JRE is added automatically to the environmentvariable PATH.

Figure 15: Windows: JDK Installation

Hint: When you specify the Java installation directory, make sure that:

There are no spaces in the directory path

The directory only contains the version number and NOT the buildnumber or patch level.

This is recommended because many SAP and non-SAP tools usethe path to the Java installation directory in start scripts. If youupgrade from e.g. j2sdk1.4.2_34 to j2sdk1.4.2_36 and leave thedefault settings, the directory name changes, but the scripts don'tget changed.




If you are not certain that the JDK/JRE is installed already, you can check underStart Settings Control Panel Add/Remove Programs. The software ispresent if there is an entry for Java ....

Hint: Deactivate the automatic update feature of the Java installation.Otherwise you may upgrade your JDK unwillingly to a non-supportedversion.

After installation of the JRE/JDK you have to set an environment variable so thatSAPinst and SAP NetWeaver AS Java can locate the installed JRE/JDK.

In case you need to install more than one JDK version, you can set differentenvironment variables for SAPinst and SAP NetWeaver AS Java. SAPinstchecks environment variable SAPINST_JRE_HOME for a valid Java runtimeenvironment. If SAPINST_JRE_HOME is not found, SAPinst also checksJAVA_HOME. As SAP NetWeaver AS Java also needs the JAVA_HOMEenvironment variable to be set, you can simply add the JAVA_HOME variable ifSAPinst and SAP NetWeaver AS Java need the same JDK version.

Setting the environment variable in Windows

To set the JAVA_HOME environment variable in Windows, choose Start Settings Control Panel System and switch to the Advanced tab. SelectEnvironment Variables.

Make sure the JAVA_HOME system variable is set to the Java home directory,which is the directory in which the JDK is installed. If it is not set, create a newvariable.

The procedure to create a new variable is:

Below section System variables choose New.

Set Variable name to JAVA_HOME.

Set Variable value to the Java home directory, for example D:\j2sdk

Choose OK.

The JAVA_HOME variable is now present in the system variables list.



Figure 16: Windows: Environment Variable JAVA_HOME

If necessary repeat the steps above for the SAPINST_JRE_HOME variable to pointto an alternative JRE.

Note: The same environment variables need to be set for UNIX operatingsystems.

Hint: If you need additional JRE or JDK installations, because additionalsoftware running on the same host require this, you can also set theenvironment variables to be user specific.

Download JCE Policy Files

As of SAP NetWeaver 7.0 strong encryption is mandatory for SAP NetWeaver ASJava and for all usage types that are deployed on it. You need to obtain the JavaCryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 1.4.2.beforehand so that they can be installed by SAPinst. Download the JCE policyfiles for the SUN JDK at http://java.sun.com/j2se/1.4.2/download.html. SAPinstinstalls the JCE policy files during the installation process.




Figure 17: JCE Policy Files (SUN)

This file from Oracle can also be used for HP-UX Java SDK/JDK.

For the IBM JDK you get the JCE policy files from IBM.

Prerequisites Check

You should check the hardware and software requirements for your operatingsystem (OS) and the SAP instances using the Prerequisite Checker tool.

The Prerequisite Checker provides information about the requirements thatyou need to meet before you start the installation. For example, it checks therequirements for the different installation services.

Before using this tool consult SAP Note 855498 - Installation Prerequisite Checkerto get the latest update for the prerequisite checker. Download the attachmentfitting to your installation, here PREREQUISITE_CHECK_DATA_700.SAR, andsave it on the host. Extract the SAR file using sapcar. When executing the check,reference the extracted XML file.



Figure 18: Prerequisites Check 1/5

On the welcome screen, choose: SAP Solution Manager 7.1 SoftwareLife-Cycle Options Additional Preparation Options Prerequisites Check.




In addition to using the Prerequisite Checker you also have to check therequirements checklists for the installed services mentioned in the installationguide.

Generate SAP Solution Manager Key

Figure 23: Generate SAP Solution Manager Key

When installing an SAP system - other than SAP Solution Manager itself - youwill need a key generated by the SAP Solution Manager. Without this key asuccessful installation is not possible (depending on the release of the software tobe installed).SAP Note 811923 - Generating the SAP Solution Manager key describes how togenerate the key.

The funny thing is: instead of entering the System Number you have to enter thecentral instance number you plan to install. And instead of entering the MessageServer you have to enter the name of the host, the message server should run on. ;-)



Exercise 1: Prepare the Installation Part1/2

Exercise ObjectivesAfter completing this exercise, you will be able to:

Install the JDK

Execute the Prerequisite Checker

Business ExampleYou want to prepare the installation of an SAP system.

Task 1: Check DVDsCheck if the installation DVDs are available.

1. To log on to your host, use the host name, the user name, and the passwordgiven to you by your instructor.

Note: Use a Terminal Service Client to connect to your host.

You find the installation DVDs at D:\ADM110_NEW.

Task 2: JDK InstallationPrepare the installation by installing the JDK and setting the JAVA_HOMEvariable.

1. Install the JDK (j2sdkfb-1_4_2_-windows-amd64.exe)

to the destination directory D:\j2sdk.

You should find the installation file in folder

D:\ADM110_NEW\Inst_Additional\01_Java_SDK of your host.

2. Set the JAVA_HOME environment variable to the just installed Java homedirectory D:\j2sdk.

Task 3: JCE Policy FilesCheck that the JCE Policy Files are on your host.

1. Check that the JCE Policy Files are on your host. They should be availablein folder D:\ADM110_NEW\Inst_Additional\02_JCE_Policy_File.

Continued on next page



Task 4: Prerequisites CheckUse the Prerequisite Checker to check the hardware and software requirements.

1. Start SAPinst.

Reference the PREREQUISITE_CHECK_DATA.XMLfile at D:\ADM110_NEW\Inst_Additional\03_Prerequi-site_Check_SAP_Note_0855498




Solution 1: Prepare the Installation Part1/2

Task 1: Check DVDsCheck if the installation DVDs are available.

1. To log on to your host, use the host name, the user name, and the passwordgiven to you by your instructor.

Note: Use a Terminal Service Client to connect to your host.

You find the installation DVDs at D:\ADM110_NEW.

a) Follow the exercise description.

Task 2: JDK InstallationPrepare the installation by installing the JDK and setting the JAVA_HOMEvariable.

1. Install the JDK (j2sdkfb-1_4_2_-windows-amd64.exe)

to the destination directory D:\j2sdk.

You should find the installation file in folder

D:\ADM110_NEW\Inst_Additional\01_Java_SDK of your host.

a) Double click the file j2sdkfb-1_4_2_-windows-amd64.exe.

Follow the figures Windows: JDK Installation from the coursedocument and change the proposed installation directory to D:\j2sdk.

2. Set the JAVA_HOME environment variable to the just installed Java homedirectory D:\j2sdk.

a) Choose Control Panel All Control Panel Items System andchoose the Advanced system settings option.

Select on the tab Advanced the button Environment Variables....

Follow the figure Windows: Environment Variable JAVA_HOME.

Continued on next page



Task 3: JCE Policy FilesCheck that the JCE Policy Files are on your host.

1. Check that the JCE Policy Files are on your host. They should be availablein folder D:\ADM110_NEW\Inst_Additional\02_JCE_Policy_File.

a) Follow the step description.

Task 4: Prerequisites CheckUse the Prerequisite Checker to check the hardware and software requirements.

1. Start SAPinst.

Reference the PREREQUISITE_CHECK_DATA.XMLfile at D:\ADM110_NEW\Inst_Additional\03_Prerequi-site_Check_SAP_Note_0855498

a) Follow the instruction from the course document, section PrerequisitesCheck.




Lesson Summary





Lesson: Additional Preparation for Installation onWindows

Lesson OverviewThis lesson discusses the preparation steps that you need to perform in addition tothe general preparation steps to install an SAP system on a Windows operatingsystem.


Perform the necessary preparation steps to install an SAP system onWindows

Business ExampleYou want to perform the necessary preparation steps to install an SAP systemon Windows.

Preparing for Installation in WindowsWhen installing an SAP system on a Windows operating system you have to dothe following Windows specific preparations:

Check Windows file system

If necessary, reduce size of file cache

Prepare installation user



TADM12_1 Lesson: Additional Preparation for Installation on Windows

Check Windows File System

Figure 24: Windows File System: NTFS

You must install an SAP system on an NTFS file system. Check the partition onwhich you plan to install the SAP system for the correct file system type: open theWindows Explorer, select D:, choose Properties and switch to the General tabto see the type of file system.

Please set the paging area to the size shown in the picture above. Also, SAPinstwill tell you if you need to adapt page settings.

Domain or local installation

You can decide, if you want to install your system on the hosts locally or using aWindows domain. SAP recommends to perform a domain installation.

For a domain installation SAP recommends that all SAP system and database hostsare members of a single Windows domain. This is valid for all SAP system setups,whether standalone central systems or distributed systems. In the single domainmodel, the SAP system and the user accounts are included in a single domain.

Caution: You cannot create local users and groups on the host that is usedas domain controller. Therefore, SAP does not support running an SAPinstance (including the database instance) on the host where the DNSservice is installed.

2013/Q1 2013

tadm12_1 en col99 fv part ltr

Documents