sap tadm12 nw 7.31 col99 v099 sample

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

For Any SAP / IBM / Oracle - Materials Purchase Visit : www.erpexams.com OR Contact Via Email Directly At : [email protected]




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.

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

Unit 1: Overview and Architecture of SAP Systems 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 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.


sap tadm12 nw 7.31 col99 v099 sample

Documents