Managing SAP R 3 With Tivoli

7/29/2019 Managing SAP R 3 With Tivoli

1/327

SG24-5298-00

International Technical Support Organization

http://www.redbooks.ibm.com

Managing SAP R/3 with Tivoli

Stefan Uelpenich, Stephane Gillardo, Masahiro Kubo, Jose Hernani Oliveira Jr.,Thomas Serckx, Carsten Siegler, Theo Winkelmann


2/327


3/327

Managing SAP R/3 with Tivoli

January 1999

SG24-5298-00

International Technical Support Organization


4/327

Copyright International Business Machines Corporation 1999. All r ights reserved

Note to U.S Government Users Documentation related to restricted rights Use, duplication or disclosure issubject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

First Edition (January 1999)

This edition applies to Tivoli Manager for R/3 Version 1.5 on the Windows NT and IBM AIX operatingsystems.

Comments may be addressed to:IBM Corporation, International Technical Support OrganizationDept. HZ8 Building 678P.O. Box 12195Research Triangle Park, NC 27709-2195

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute theinformation in any way it believes appropriate without incurring any obligation to you.

Before using this information and the product it supports, be sure to read the general information inAppendix F, Special Notices on page 289.

Take Note!


5/327

Copyright IBM Corp. 1999 iii

Contents

Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

The Team That Wrote This Redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Comments Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 What is SAP R/3?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1.1 CCMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2 Challenges in Managing an SAP R/3 Environment . . . . . . . . . . . . . . . . 5

1.3 Tivoli Enterprise Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.4 The Tivoli Management Strategy for SAP R/3 . . . . . . . . . . . . . . . . . . . 9

1.4.1 Tivoli Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.4.2 Tivoli Distributed Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.4.3 Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4.4 Tivoli Software Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4.5 Tivoli Workload Scheduler (Maestro) . . . . . . . . . . . . . . . . . . . . . 111.4.6 Tivoli Output Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.4.7 Tivoli Database Management Products. . . . . . . . . . . . . . . . . . . . 15

1.4.8 Tivoli NetView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.4.9 Tivoli Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.4.10 Tivoli Global Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . 16

1.4.11 Tivoli Adstar Distributed Storage Manager (Tivoli ADSM) . . . . . 17

1.5 Tivoli Manager for R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1.6 The Benefits of Using Tivoli to Manage R/3 . . . . . . . . . . . . . . . . . . . . 19

1.7 Where to Find What . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2. Installation Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.1 Overview and Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.2 Defining Management Requirements for SAP R/3 . . . . . . . . . . . . . . . 212.3 Selecting the Necessary Tivoli Components. . . . . . . . . . . . . . . . . . . . 25

2.4 Designing a Management Solution for R/3 . . . . . . . . . . . . . . . . . . . . . 28

Chapter 3. Setting Up the SAP R/3 Management Environment . . . . . . 31

3.1 Overview and Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.2 Overview of Our SAP R/3 Environment . . . . . . . . . . . . . . . . . . . . . . . 32

3.3 Overview of Our Tivoli Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.4 The SAP R/3 Systems in Our Environment. . . . . . . . . . . . . . . . . . . . . 39

3.5 Tivoli Output Management (Destiny) in Our Environment . . . . . . . . . . 40


6/327

iv Managing SAP R/3 with Tivoli

3.5.1 Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.5.2 Domain Manager Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.5.3 Output Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.5.4 Direct Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.5.5 Composer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.5.6 Conductor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.6 Installing and Configuring Tivoli Manager for R/3 . . . . . . . . . . . . . . . . 43

3.6.1 Installing Tivoli Manager for R/3 . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.6.2 Configuring the Tivoli Manager for R/3 . . . . . . . . . . . . . . . . . . . . 463.6.3 Configuring Each R/3 System. . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.6.4 Configuring the Tivoli Manager for R/3 for Each R/3 System . . . 53

3.6.5 Configuring the TEC Server and TEC Consoles . . . . . . . . . . . . . 63

3.6.6 Configuration of the R/3 Clients . . . . . . . . . . . . . . . . . . . . . . . . . 67

3.7 Installing and Configuring Tivoli Manager for Oracle . . . . . . . . . . . . . 80

3.8 Installing and Configuring Tivoli Maestro . . . . . . . . . . . . . . . . . . . . . . 81

3.8.1 Installing Tivoli Maestro Master and FTA (Fault-Tolerant Agent). 813.8.2 Installing and Configuring Tivoli Maestro Extended Agent 3.0. . . 90

3.8.3 Creating Jobs for Tivoli Maestro in SAP R/3 . . . . . . . . . . . . . . . . 97

3.8.4 Installing and Configuring Tivoli Plus for Maestro . . . . . . . . . . . 107

3.9 Installing and Configuring Tivoli Output Management (Destiny) . . . . 115

3.9.1 Considerations Before Installation . . . . . . . . . . . . . . . . . . . . . . 1153.9.2 Destiny Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

3.9.3 Testing the Destiny Installation. . . . . . . . . . . . . . . . . . . . . . . . . 124

Chapter 4. Using the SAP R/3 Management Environment . . . . . . . . . 131

4.1 Tivoli Manager for R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

4.1.1 SAP R/3 System Management Tasks and Jobs . . . . . . . . . . . . 131

4.1.2 SAPGUI Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

4.1.3 Monitoring: Behind the Scenes . . . . . . . . . . . . . . . . . . . . . . . . . 140

4.1.4 Default Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

4.1.5 SYSLOG Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

4.2 Tivoli Workload Scheduler (Maestro) . . . . . . . . . . . . . . . . . . . . . . . . 180

4.2.1 Tivoli Maestro Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

4.2.2 Tivoli Maestro System Configuration . . . . . . . . . . . . . . . . . . . . 180

4.2.3 Tivoli Maestro Internals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

4.2.4 Tivoli Maestro Job Scheduling Object Definition . . . . . . . . . . . . 183

4.2.5 Job Scheduling Production Cycle . . . . . . . . . . . . . . . . . . . . . . . 188

4.2.6 Tivoli Maestro SAP R/3 Extended Agent. . . . . . . . . . . . . . . . . . 190

4.2.7 Batch Job Network Design Under Tivoli Maestro . . . . . . . . . . . 195

4.2.8 Tivoli Maestro SAP R/3 Extended Agent Summary. . . . . . . . . . 202

4.3 Tivoli Output Manager (Destiny) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

4.3.1 Destiny Enterprise Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

4.3.2 Domain Manager Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206


7/327

v

4.3.3 Output Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

4.3.4 Typical Domain Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

4.3.5 SAP R/3 Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Chapter 5. Management Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

5.1 Creating a Custom SAP Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

5.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

5.1.2 Technical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

5.1.3 Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2275.2 Critical Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

5.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230


5.2.3 Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

5.3 Monitoring SAP R/3 Using a Standard Numeric Script Monitor . . . . . 245

5.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

5.3.2 Steps Needed to Add the Numeric Script Monitor . . . . . . . . . . . 246

5.3.3 Details of Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

5.4 Interconnected TMRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

5.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253


5.4.3 Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Appendix A. Monitor Sources and their Attributes . . . . . . . . . . . . . . . 263

Appendix B. Event Classes for Tivoli Manager for R/3 . . . . . . . . . . . . 269

Appendix C. Custom Monitor MCSL Source File . . . . . . . . . . . . . . . . . 275

Appendix D. Destiny Database Structure . . . . . . . . . . . . . . . . . . . . . . . . 279

Appendix E. Useful SAP Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Appendix F. Special Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Appendix G. Related Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293G.1 International Technical Support Organization Publications . . . . . . . . . . 293

G.2 Redbooks on CD-ROMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

G.3 Other Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

How to Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

How IBM Employees Can Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . . . . . 295

How Customers Can Get ITSO Redbooks. . . . . . . . . . . . . . . . . . . . . . . . . . . 296

IBM Redbook Order Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297


8/327

vi Managing SAP R/3 with Tivoli

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

ITSO Redbook Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307


9/327

Copyright IBM Corp. 1999 vii

Figures

1. SAP R/3 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2. SAPGUI Initial Login Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3. CCMS Alert Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

4. Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

5. Tivoli Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

6. A Typical Output Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

7. Centralized Control of Output Resources . . . . . . . . . . . . . . . . . . . . . . . . . 13

8. SAP R/3 Managed as a Business System. . . . . . . . . . . . . . . . . . . . . . . . . 17

9. Management Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

10. Management of SAP R/3 within the Overall Systems Management . . . . . 29

11. SAP R/3 Systems in Our Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

12. Tivoli/SAP Management Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

13. Tivoli Output Manager Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

14. Installing Tivoli Manager for R/3: Install Product Window . . . . . . . . . . . . . 45

15. Installing Tivoli Manager for R/3: Result of Installation . . . . . . . . . . . . . . . 46

16. Creating the ZTV1 Development Class . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

17. Importing the Function Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

18. Checking the ZTTC180 and ZTIVOLI Tables . . . . . . . . . . . . . . . . . . . . . . 51

19. Imported Objects Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5220. Entering Parameters for the Configure TME for an R/3 System Job. . . . . 54

21. Configure TME for an R/3 System Job Status. . . . . . . . . . . . . . . . . . . . . . 55

22. Assigning the New TMR Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

23. Configuring an Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

24. Configuring the Database Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

25. Configuring a SAPGUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

26. Configuring the Remote Function Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

27. Checking the RFC Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6128. Tivoli Manager Configuration (Part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

29. Tivoli Manager Configuration (Part 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

30. Configuring the Event Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

31. Configuring the Event Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6532. Event Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

33. Directories and Files Included in the File Package . . . . . . . . . . . . . . . . . . 68

34. Edit Job for a Reference Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

35. Settings for the Jobs Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

36. Result of the Jobs Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

37. Configuring the R/3 SAPGUI Client File Package: Edit the Profile . . . . . . 74

38. Edit Job for a Native Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

39. Native Installation Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

40. Native Installation Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79


10/327

viii Managing SAP R/3 with Tivoli

41. Configuring the R/3 SAPGUI Client Native Installation Profile. . . . . . . . . . 80

42. Installing Tivoli Maestro: Creating Maestro NT Account . . . . . . . . . . . . . . 82

43. Maestro Configuration Information Window. . . . . . . . . . . . . . . . . . . . . . . . 83

44. Maestro NT Services Batchman, JOBMAN, Netman, Token Services . . . 84

45. Tivoli Maestro SHOWCPUs Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

46. Scheduling Final (Staging Maestro Database to be in Effect) . . . . . . . . . . 86

47. Confirm the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

48. Maestro Console Manager SHOWCPUs Display . . . . . . . . . . . . . . . . . . . 88

49. Maestro Silver CPU Definition Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 8950. Maestro SHOWCPUs for silver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

51. Create R/3 User Profile ZMAESTRO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

52. R/3 User MAESTRO Creation (R/3 Transaction SU01). . . . . . . . . . . . . . . 92

53. Executing the r3setup Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

54. Output from r3setup Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

55. Showing Transport Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

56. Import Function Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9657. Tivoli Maestro R/3 Function Modules List . . . . . . . . . . . . . . . . . . . . . . . . . 97

58. Background Job Definition in R/3 (SM36) . . . . . . . . . . . . . . . . . . . . . . . . . 98

59. Create Step Specifying ABAP/4 Program . . . . . . . . . . . . . . . . . . . . . . . . . 99

60. Maestro R/3 Job Definition Start Date . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

61. Maestro R/3 Job Definition: Status is Shown as Scheduled . . . . . . . . . . 10162. Tivoli Maestro SAP R/3 Extended Agent CPU Definition. . . . . . . . . . . . . 102

63. Maestro Composer New Job Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

64. SAPIBM#SAP_1 Job Definition Window . . . . . . . . . . . . . . . . . . . . . . . . . 103

65. Retrieve R3 Job List Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

66. Final Display of R3 Job Definition by Maestro . . . . . . . . . . . . . . . . . . . . . 104

67. ITSOMSTR#SAPJOB1 Schedule Definition . . . . . . . . . . . . . . . . . . . . . . 105

68. Maestro Console Manager: CPUs Display . . . . . . . . . . . . . . . . . . . . . . . 106

69. Maestro Console Manager: SHOWJOBs Display . . . . . . . . . . . . . . . . . . 106

70. R/3 Job Overview Alphabetic Window. . . . . . . . . . . . . . . . . . . . . . . . . . . 107

71. Install Product Window for Tivoli Plus for Maestro. . . . . . . . . . . . . . . . . . 108

72. Set Install Options for Tivoli Plus for Maestro . . . . . . . . . . . . . . . . . . . . . 109

73. Running Job Setup EventServer for Maestro . . . . . . . . . . . . . . . . . . . . . 11074. Adding To Existing Rule Base Options Window . . . . . . . . . . . . . . . . . . . 111

75. Setup EventServer for Maestro Job Completion . . . . . . . . . . . . . . . . . . . 111

76. Maestro Event Classes and Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

77. Running Job Configure Logfile Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . 11378. Configure Logfile Adapter Job Completion . . . . . . . . . . . . . . . . . . . . . . . 114

79. Compacting a JET Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

80. Destiny Installable Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

81. Database Selection and Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

82. Server Components for Destiny Network. . . . . . . . . . . . . . . . . . . . . . . . . 119

83. Node Name Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120


11/327

ix

84. Domain Information for Destiny Domain Structure . . . . . . . . . . . . . . . . . 121

85. Destiny Port Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

86. Read Only Message During Installation. . . . . . . . . . . . . . . . . . . . . . . . . . 122

87. Destiny Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

88. Destiny Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

89. Destiny Services on Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

90. Destiny Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

91. Destiny Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

92. Push Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12693. Destiny Conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

94. DemoWeb Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

95. Queues Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

96. Task Library: RDU System Tasks Window . . . . . . . . . . . . . . . . . . . . . . . 132

97. Task Library: RDU Server Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

98. Display OS Collect Information Options. . . . . . . . . . . . . . . . . . . . . . . . . . 134

99. OS Collection Information Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

100.Task Library: RDU Database Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

101.Cloning Profile into Dataless Profile Manager. . . . . . . . . . . . . . . . . . . . . 138

102.Configuring the R/3 SAPGUI Client File Package: Distribution to a TMA 139

103.Example of SAPGUI Access on a Windows NT Client . . . . . . . . . . . . . . 140

104.CCMS Alert Overview - Transaction RZ03 . . . . . . . . . . . . . . . . . . . . . . . 141105.Information Exchange between TEC and R/3 Application Server. . . . . . 142

106.Event Adapter: Drill-Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

107.Alert Control Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

108.Tivoli Distributed Monitoring in an SAP R/3 System . . . . . . . . . . . . . . . . 147

109.Schema of WR3RFC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

110.Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

111.Default Profile Managers, Subscription Lists and Profiles. . . . . . . . . . . . 160

112.Monitoring Collections Provided by the Tivoli Manager for R/3. . . . . . . . 162

113.RDU Predefined Server Central Monitors . . . . . . . . . . . . . . . . . . . . . . . . 164

114.RDU Predefined Server Remote Monitors . . . . . . . . . . . . . . . . . . . . . . . 165

115.RDU Predefined Database Central Monitors . . . . . . . . . . . . . . . . . . . . . 166

116.RDU Predefined Client Remote Monitors . . . . . . . . . . . . . . . . . . . . . . . . 167117.Distributing Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168118.Starting Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

119.TEC Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

120.Modifying Default Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

121.Edit Properties for Default Profile to Add a New Monitor . . . . . . . . . . . . 172

122.Add a Monitor Window Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

123.Creating a New Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

124.New Monitor Created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

125.Configuring SYSLOG via RZ06 Transaction . . . . . . . . . . . . . . . . . . . . . . 178

126.SYSLOG Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179


12/327

x Managing SAP R/3 with Tivoli

127.Tivoli Maestro Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

128.Maestro Job Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

129.Tivoli Maestro Network Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

130.Schedule Dependency Definition/Follow SchedJob Panel . . . . . . . . . . . 187

131.Maestro Console Manager View of Jobs. . . . . . . . . . . . . . . . . . . . . . . . . 187

132.Production Cycle - A Day in Tivoli Maestro . . . . . . . . . . . . . . . . . . . . . . . 189

133.Stageman Processing during Jnexday Job . . . . . . . . . . . . . . . . . . . . . . . 190

134.SAP R/3 Extended Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

135.R3batch Access Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191136.R3options File for Tivoli Maestro r3batch Methods Definition . . . . . . . . . 192

137.SAP R/3 Job Definition in Tivoli Maestro. . . . . . . . . . . . . . . . . . . . . . . . . 194

138.Job Network Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

139.SAP Jobs Defined in SAP GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

140.Maestro Jobs List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

141.Example Job Network Design by Tivoli Maestro . . . . . . . . . . . . . . . . . . . 197

142.Maestro Schedule List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198143.Maestro Console Manager SHOWSCHEDULES Window . . . . . . . . . . . 199

144.Maestro Console Manager SHOWJOBS Window. . . . . . . . . . . . . . . . . . 200

145.Showjobs Windows Displays the Job Completion Status . . . . . . . . . . . . 201

146.Final Result of Example Job Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . 201

147.R/3 SM37 Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202148.Composer Logon Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

149.Composer Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

150.Composer Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

151.Changing Print Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

152.Choosing Print Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

153.Queue Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

154.Mapper Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

155.SAP R/3 Printing into the Destiny Network . . . . . . . . . . . . . . . . . . . . . . . 212

156.Direct Client Logon Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

157.Saving Selections as Destiny Printers. . . . . . . . . . . . . . . . . . . . . . . . . . . 214

158.SAPTUNE_NUM_OF_WP Characteristics . . . . . . . . . . . . . . . . . . . . . . . 217

159.SAPTUNE_NUM_OF_WP Test Result . . . . . . . . . . . . . . . . . . . . . . . . . . 218160.SAP_WP rfc_interface File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

161.Custom Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

162.Distributed Monitoring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

163.Dm_msg_format.rls Rule Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226164.Reformatted Distributed Monitoring Events. . . . . . . . . . . . . . . . . . . . . . . 227

165.Adding a SAP Custom Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

166.Customizing our New Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

167.Event from our Custom Monitor in the TEC Console . . . . . . . . . . . . . . . 230

168.Typical R/3 Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

169.Profile Managers and Tivoli Distributed Monitoring Profiles Created . . . 237


13/327

xi

170.ABAP/4 Program for Checking Table Availability . . . . . . . . . . . . . . . . . . 247

171.Remote Function Call Supported Option in Administration Panel. . . . . . 248

172.Export Parameter Definition of Z_KUB_RS1. . . . . . . . . . . . . . . . . . . . . . 249

173.Test of Remote Function Module We Used . . . . . . . . . . . . . . . . . . . . . . 250

174.Numeric Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

175.wr3rfc Command Interface File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

176.Edit Monitor Window of Tivoli Distributed Monitoring . . . . . . . . . . . . . . . 252

177.Configure the Upper Event Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

178.Configure Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257179.sap_alert_reader_cb.sh Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

180.sap_alert_reader.sh Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

181.Custom Monitor MCSL Source File (Part 1 of 4). . . . . . . . . . . . . . . . . . . 275




185.UED Database Structure (Part 1 of 8). . . . . . . . . . . . . . . . . . . . . . . . . . . 279

186.SCD Database Structure (Part 2 of 8). . . . . . . . . . . . . . . . . . . . . . . . . . . 280

187.News Database Structure (Part 3 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . 281



190.News Database Structure (Part 6 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . 284191.News Database Structure (Part 7 of 8) . . . . . . . . . . . . . . . . . . . . . . . . . . 285



14/327

xii Managing SAP R/3 with Tivoli


15/327

Copyright IBM Corp. 1999 xiii

Tables

1. Tivoli Products for the Management of SAP R/3 . . . . . . . . . . . . . . . . . . . . 26

2. Raleigh System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3. Configuration of Raleigh System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4. Heidelberg System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5. Configuration of Heidelberg System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

6. Maestro and R/3 Job States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

7. Work Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

8. Swap Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

9. Saposcol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

10. Load Average. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

11. /sapmnt/ Filesystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

12. /usr/sap/trans Filesystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

13. /usr/sap/ Filesystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

14. Print Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

15. Orasrv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

16. /oracle//saparch Filesystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

17. Free Space Deficit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

18. Free Space Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

19. Free Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24220. Maximum Extents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

21. RDBMS State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

22. SAP System Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244


16/327

xiv Managing SAP R/3 with Tivoli


17/327

Copyright IBM Corp. 1999 xv

Preface

In this redbook we show how to manage an SAP R/3 environment using the

Tivoli Enterprise Software products. We focus on Tivoli Manager for R/3 1.5

but also include other Tivoli components, such as the Tivoli Workload

Scheduler (Maestro).

We position the Tivoli application management and systems management

strategy and show detailed examples of how to utilize this strategy to managean enterprise SAP R/3 installation. We show in detail how to set up and use

Tivoli Manager for R/3, Tivoli Workload Scheduler (Maestro), Tivoli Output

Management (Destiny) and other Tivoli products to create an integrated R/3

management environment.

All scenarios in this redbook are documented so that they can be used by

service providers in client engagements.

The Team That Wrote This Redbook

This redbook was produced by a team of specialists from around the world

working at the International Technical Support Organization, Raleigh Center.

This project was designed and managed by:

Stefan Uelpenich is a Senior ITSO Representative working as a project

leader in the ITSO Tivoli Group, Austin. He applies his extensive field

experience as an I/T architect and project leader to his work at the ITSO,

where he writes extensively and consults worldwide on all areas of systems

management. Before joining the ITSO, Stefan worked in IBM Germanys

Professional Services organization as an Advisory I/T Architect for Systems

Management, consulting major IBM customers. In this role, he architected the

systems management solution for one of Germanys largest client/server

networks. Having published 15 books on a wide area of topics in the field ofsystems management and Tivoli and being involved in numerous projects,

Stefan is one of the leading experts in the field of systems management.

The other authors of this redbook are:

Dr. Masahiro Kubo is an Advisory I/T Specialist at the Technical Support

Center in IBM Japan. He started working with Tivoli products when Tivoli

merged with IBM and is now the technical lead for design and implementation

of Tivoli systems management solutions. Recently, his customer engagement

was to build a sophisticated management solution, where Tivoli acts as a


18/327

xvi Managing SAP R/3 with Tivoli

manager of managers, managing multiple HP system management servers.

His areas of expertise include knowledge of manufacturing industry solutions

and SAP R/3 Basis. It was his pleasure to gain ABAP/4 programming skill in

this project. His writings relating to Tivoli are The Vital Point of Introducing

Tivoli, the Integrated System Control Packagepublished in ProVISION No.19

in October 1998 and Thinking Way of Business System Management, both of

which received professional paper awards from IBM Japan.

Stephane Gillardo is an I/T Specialist working for IBM Global Services in theService Delivery EMEA West group, located in La Gaude, France. He has been

working with IBM for two years, and has expertise with all Tivoli core applications

for the management of distributed systems. Stephane has been involved in Tivoli

product evaluations and in projects for Tivoli solution deployments. His areas of

expertise include Tivoli 3.6 and he was also one of the authors of another ITSO

Tivoli redbook.

Thomas Serckx is an I/T Specialist working as a systems engineer at IBM

Global Services in Belgium. He has been working for two years in the Service

Delivery group and his areas of expertise include Tivoli, networking, UNIX

and Windows NT. Now, as member of the SAP/UNIX Systems Management

team, Thomas is designing and deploying a Tivoli solution for the centralized

management of the midrange servers of major IBM outsourced customers.

Carsten Siegler is a technical consultant working in IBM Global Services in

Heidelberg, Germany. As a member of the SAP Systems Management team

he focuses on SAP R/3 systems management and SAP R/3 Basis. In his four

years of experience he supported and designed SAP R/3 systems

management solutions for the Tivoli Module for SAP R/3, SAP R/3 Backup,

SAP R/3 Archiving and SAP R/3 Basis.

Jose Hernani Oliveira Jr. is an Advisory I/T Specialist working for IBM

Global Services in the Strategic Outsourcing, Enterprise Automation group in

Sumare, Brazil. He has been with IBM for 7 years and has held various

positions as a systems analyst, technical support analyst and I/T specialist.His areas of expertise include networking, operating systems, relational

databases and object technology. He is currently working in deploying Tivoli

monitoring and automation products to outsourced SAP customers in Brazil.

Theo Winkelmann is an Advisory I/T Specialist, working as technical

consultant at IBM Global Services in South Africa. His areas of expertise

include Tivoli, TCP/IP, UNIX and Windows NT. In his current position Theo

consults major IBM accounts in South Africa and has been the lead architect

for one of the largest Tivoli projects in Africa, managing close to 100000


19/327

xvii

desktop systems and involving all Tivoli core products. Theo has previously

authored another ITSO Tivoli redbook.

Thanks to the following people for their invaluable contributions to this

project:

Bill Sadek

International Technical Support Organization, Raleigh Center

Patrick Ancipink, Poonam Dhawan, Jon Goodman, Jay Kruemcke, David

Moring

Tivoli Systems, Austin

Ellen Dickson, Terry Casstevens, Ron Cherveny, Todd Miller, Tom

Songvichitr, Sandy Jenkins

Tivoli/SAP Solutions, Raleigh

Andy Kicklighter

Tivoli Systems, Santa Clara

Ingo Averdunk

Tivoli Professional Services

Frank Fischer

Tivoli/IBM Germany

Kathryn Casamento, Linda Robinson, Shawn Walsh, Gail Christensen

Editing Team, International Technical Support Organization, Raleigh Center

Comments Welcome

Your comments are important to us!

We want our redbooks to be as helpful as possible. Please send us your

comments about this or other redbooks in one of the following ways:

Fax the evaluation form found in ITSO Redbook Evaluation on page 307

to the fax number shown on the form.

Use the electronic evaluation form found on the Redbooks Web sites:

For Internet users http://www.redbooks.ibm.com

For IBM Intranet users http://w3.itso.ibm.com

Send us a note at the following address:

[email protected]


20/327

xviii Managing SAP R/3 with Tivoli


21/327

Copyright IBM Corp. 1999 1

Chapter 1. Introduction

In this chapter we briefly introduce the SAP R/3 application system and the

Tivoli management strategy for applications in general and for SAP R/3

specifically. We give an overview of all the Tivoli management products

involved that we explore in more detail in the subsequent chapters.

1.1 What is SAP R/3?

We only give a brief overview of SAP R/3 in this section. For a more detailed

coverage of SAP R/3 refer to the appropriate R/3 materials.

SAP R/3 is a client/server application system used for Enterprise Resource

Planning (ERP). R/3 has many different modules to model all parts of the

enterprise business and can manage data from finance, sales, accounting,

manufacturing, human resources and other business departments.

A major value of R/3 is that it provides a framework for the customer to

integrate business data and business processes. R/3 can act as a catalyst for

change as it not only allows the customer to automate business processes

using information technology, but also can be used to drive changes to thebusiness processes themselves.

R/3 runs on many different platforms, including Windows NT and all major

UNIX operating systems. R/3 has a multi-tier architecture with the following

main components:

Database Server

Application Server(s)

Presentation Clients


22/327

2 Managing SAP R/3 with Tivoli

Figure 1. SAP R/3 Components

Typically, there is one database server in an R/3 system. The database

server stores data in a Relational Database Management System (RDBMS),

such as DB2, Oracle, Informix, ADABAS or Microsoft SQL Server. These

database servers can also run on different platforms, such as Oracle on

Windows NT and UNIX, DB2 on Windows NT, UNIX or OS/390 and many

others. The communications protocol used between the three main

components of the R/3 system is TCP/IP.

The users log in from their presentation clients to the applications server,

where the actual R/3 application is running. The application servers in turn

communicate with the database server. Application servers can also run on

Windows NT and all major UNIX platforms. The database server andapplication server can physically run on the same machine.

The presentation client, often referred to as SAPGUI, runs on Windowsplatforms, UNIX platforms and OS/2. The following figure shows an example

of the initial login window of the SAPGUI on Windows 95:

Database

Server

Application

Servers

Presentation Clients


23/327

Introduction 3

Figure 2. SAPGUI Initial Login Window

An R/3 system is comprised of the database server and one or more

application servers, as well as the presentation clients. The R/3 system is

identified by a three-character system identifier (SID), such as DEV, TST, etc.

The SID logically groups the database server and the application servers,

that is, it identifies the R/3 as a whole.

Instances are assigned to the application servers in the R/3 system

(remember, there can be one or more application servers per R/3 system).

One of the instances is designated as the central instance.

The previous section gives just an overview of the main components of an

R/3 system. R/3 consists of many components that we dont explain in detail

here, such as SAPGUI servers and ITS.


24/327


1.1.1 CCMS

The R/3 system contains a built-in component for systems management that

is called Computing Center Management System (CCMS). CCMS provides

functions for monitoring, system optimization, logging, etc.

CCMS can be accessed from the SAPGUI. For example, the following figure

shows an example of the CCMS Alert Monitor.

Figure 3. CCMS Alert Monitor

CCMS is, however, intended mainly for controlling and managing R/3systems and does not provide for scaling to a large-scale systems

management solution for R/3 systems. This is where the Tivoli solution

comes into place. The Tivoli Manager for R/3 uses the features provided by

CCMS and adds many additional features and also allows scaling systems

management of the R/3 system to an enterprise level while at the same time

integrating with the systems management of other components. The features

provided by the Tivoli solution will be discussed in full detail in this redbook.


25/327

Introduction 5

1.2 Challenges in Managing an SAP R/3 Environment

Management of an R/3 system constitutes a challenge for the following main

reasons:

The R/3 installation is usually highly critical.

R/3 installations are complex by nature and therefore also complex to

manage.

The R/3 installation of an enterprise is highly critical as it runs the core of the

companys business logic, such as the ordering system, sales, accounting,

payroll, human resources, etc. Therefore, usually requirements are tough in

fields such as:

Reliability

Availability

Security

Accountability

Performance

Figure 4. Requirements

The R/3 system must provide a reliable service to the end user that isavailable at the desired times, usually 24 hours, 7 days a week. The security

of the system must be guaranteed to protect the business data stored in the

R/3 system and the performance of the system must meet user requirements.

The R/3 application utilizes a complex network of components that comprise

the R/3 application system. These components include the R/3 application

itself, the operating systems and hardware on which the application

components run, the RDBMS in which R/3 stores its data and many others.

Reliability

Availability

Security

Performance

Accountability

...


26/327


Hence, in order to achieve the goals for the above requirements, a number of

components have to be managed in order to guarantee the desired service

level. The major components are:

The network

Operating systems, including attributes such as memory utilization, paging

space, etc.

Hardware devices, such as CPUs, printers, hard disks, etc.

The RDBMS in which R/3 stores its data

The R/3 application and its components themselves

When looking at the components and the requirements you will find that there

are many dependencies; for example, security of the R/3 system involves

security of the network, the RDBMS setup and the operating system.

While managing each of these separate components themselves is not

necessarily difficult or challenging, it is usually very challenging to create an

integrated management solution.

For example, there are management tools to manage the network, tools to

manage operating systems and even a number of tools to manage SAP R/3.However, a lot of the available tools constitute point products in their specific

areas and do not integrate into an overall solution.

What we want is an integrated management of the system. To illustrate this,

lets consider an example. An end user of the SAPGUI calls the help desk

and reports a problem with the application, such as slow performance,

application not available, etc.

The help desk person now needs to determine the cause of the problem and

help fix the problem. Since there are many possible reasons for a problem

that is reported that can originate in all kinds of components of the system,

the help desk person would ideally need a highly integrated and consolidatedview of the system.

For instance, the network management system (for example, NetView) could

have detected a node down event that is relevant for the problem just

reported. While the network administrator is certainly aware of the problem,

the help desk person also needs this information, perhaps consolidated so

he/she can easily comprehend its impact. This simple example would require

the network management system to be integrated with the help desk solution.


27/327

Introduction 7

Similar causes for problems with the R/3 application could originate in the

operating system on which the application runs, hardware components, etc.

All relevant components need to be monitored, so that this information is

available to determine the cause of problems.

Another important factor is to manage the R/3 application itself, which usually

includes monitoring the application components, event management,

operations management and software distribution that enable a system

administrator to include the R/3 application in the systems managementprocess. The management module that manages the R/3 system must be

highly integrated in the systems management solution, so that the

management of R/3 can be effective and also uniform with the management

of any other component in the system.

In this book we explain Tivolis consistent strategy for managing components,

such as applications in the enterprise. For SAP R/3 we explain the Tivoli

management strategy and show in detail how the integrated Tivoli solution

can provide comprehensive management of R/3 that is integrated with the

overall systems management process.

We show how the different Tivoli components, featuring the Tivoli Manager

for R/3 but also including Tivoli Framework, Tivoli Software Distribution, TivoliDistributed Monitoring, Tivoli Enterprise Console, Tivoli NetView, Tivoli

Service Desk, Tivoli Manager for RDBMS and others through their inherent

integration provide the most comprehensive management solution for SAP

R/3 in the marketplace.

1.3 Tivoli Enterprise Software

We give only a brief overview of Tivoli here. A comprehensive introduction to

Tivoli can be found in the redbook An Introduction to Tivolis TME 10,

SG24-4948.

Tivoli provides a suite of enterprise management software (Tivoli EnterpriseSoftware) that is based on the Tivoli Framework. This framework provides a

wide array of services that can be used by systems management applications

that reside on top of this framework.


28/327


Figure 5. Tivoli Architecture

Tivoli provides a set of key applications that reside on top of the Tivoli

Framework and that address core functions of systems management. These

core applications are:

Tivoli Distributed Monitoring

Tivoli Enterprise Console

Tivoli Software Distribution

Tivoli User Administration

Tivoli Security Management

Tivoli Inventory

Tivoli Remote Control

Besides these core applications, management functionality for specific

components can easily be integrated with the Tivoli Framework and the Tivoli

core applications. This management functionality is provided by software that

Tivo l iF r a m e w o r k

TivoliEnterpriseConsole

Tivoli

Softw

are

Distrib

ution

Policie

sSecu

rity

Tiv

oliInv

ento

ryTivo

liRem

ote

Contro

l

TivoliDistributed

Monitoring

Data

...

Tivoli

User

Admin

istratio

n

Mes

saging

Tiv

oliS

ecurity

Mana

gem

ent


29/327

Introduction 9

is based on the Tivoli Framework and/or that Tivoli core applications. Tivoli

Manager for R/3 is such a software module.

1.4 The Tivoli Management Strategy for SAP R/3

In this section we give an overview of the Tivoli management strategy for R/3

and the Tivoli components involved. For each component we give a brief

introduction of what part this component plays in the management of R/3.

Later on in this redbook we describe the components in more detail.

1.4.1 Tivoli Framework

The Tivoli Framework is the backbone of the Tivoli solution and the basis for

all Tivoli systems management applications. Consequently, the Tivoli

Manager for R/3 and the other Tivoli components used to manage R/3 use

and require the Tivoli Framework.

The Tivoli Framework provides the basic systems management services,

such as communications, presentation, security, etc. that all Tivoli systems

management applications use, ensuring consistency and integration.

All Tivoli systems management tasks, regardless of the application orcomponent that is to be managed, are performed using the Tivoli Desktop,

which provides a user interface consistent throughout Tivoli management

applications.

1.4.2 Tivoli Distributed Monitoring

Tivoli Distributed Monitoring is the Tivoli application for monitoring systems

and applications. Tivoli Distributed Monitoring is tightly integrated with the

Tivoli Framework and provides monitoring capabilities for a wide range of

systems and components. The strength of Tivoli Distributed Monitoring is that

monitoring collections for components can easily be added, thus allowing you

to monitor any kind of component.

The Tivoli Manager for R/3, for example, provides its own monitoring

collections for Tivoli Distributed Monitoring that allow the administrator to

monitor specific attributes of an R/3 system using Tivoli Distributed

Monitoring.

Detailed information about Tivoli Distributed Monitoring can be found in the

following redbooks:

Creating Custom Monitors for Tivoli Distributed Monitoring, SG24-5211


30/327


Migrating from Systems Monitor for AIX to TME 10 Distributed Monitoring,

SG24-4936

A First Look at TME 10 Distributed Monitoring 3.5, SG24-2112

1.4.3 Tivoli Enterprise Console

Tivoli Enterprise Console (TEC) provides a central event display and

correlation for the enterprise, regardless from which source the events are

originating. Unlike traditional SNMP managers, TEC uses event adapters thatcan convert any kind of event stream into TEC events that can then be

processed by TEC.

Event adapters are available for a wide range of systems and applications.

For example, there are adapters for NetView, Windows NT, etc.

The Tivoli Manager for R/3 provides its own adapter that can convert events

from R/3 to TEC events.

The major strength of TEC is that events from any kind of system can be

displayed, and more importantly be correlated in one place. This allows, for

example, correlating a network event that comes from NetView with an

application event coming from R/3, and triggering an action as a result of thecorrelation.

1.4.4 Tivoli Software Distribution

Tivoli Software Distribution provides a simple and reliable service to distribute

software in the enterprise across platforms and networks. Tivoli Software

Distribution has such features as fan-out and bandwidth optimization.

Software is grouped in so-called file packages that Tivoli Software

Distribution can then automatically distribute to the desired targets.

Many applications require distribution of application components or data

across the network. This function can be provided by Tivoli Software

Distribution. For example, the Tivoli Manager for R/3 provides utilities thatassist in the creation of file packages for R/3, so that the SAPGUI component

can be automatically deployed to a large number of presentation clients.

A detailed discussion of Tivoli Software Distribution can be found in the

following redbooks:

New Features in Tivoli Software Distribution 3.6, SG24-2045

The TME 10 Deployment Cookbook: Courier and Friends, SG24-4976


31/327

Introduction 11

1.4.5 Tivoli Workload Scheduler (Maestro)

Tivoli Workload Scheduler, also known as Maestro, is the Tivoli product for

enterprise-wide job scheduling. Tivoli Workload Scheduler is an application

with full functionality in scheduling purposes and is available on several

platforms. It can be integrated with Tivoli using the Tivoli Plus for Maestro

product. This product allows managing the Tivoli Workload Scheduler

(Maestro) application from the Tivoli Desktop.

For integration of SAP R/3 in enterprise-wide scheduling, there is an interfaceavailable called SAP R/3 Extended Agent. With this interface it is possible to

manage SAP R/3 jobs with the external job scheduler Maestro. Later on in

this redbook we describe in more detail the functionality and the components

of Tivoli Workload Scheduler in combination with SAP R/3.

We explain Tivoli Workload Scheduler and all its components in detail in later

chapters.


32/327


1.4.6 Tivoli Output Management

Figure 6. A Typical Output Environment

Tivoli Output Manager, formerly known as Destiny, is the Tivoli product for

enterprise-wide output control. The output environment is an ever-changing

and diverse environment containing, for example, different printing devices

(PostScript, PCL, encapsulated PostScript, plotters, line printers), different

printer cartridge fonts in printing devices, facsimile machines, Web servers,

different mail gateways (X400, PROFS, cc:Mail, Lotus Notes, Microsoft

Exchange, Microsoft MS Mail, Microsoft OutLook, SMTP) and the global

differences in paper sizes in the distribution centers. Companies are starting

to look at enterprise output managers for coordination, routing paths, delivery

and, above all, security of documents. Tivoli Output Manager is positioned to

do just that with an easy-to-use user interface and rule engine to deliverdocuments reliably across the enterprise.

Manufacturing

Marketing

EngineeringExecutive

Sales

ProductRequirements

RevenueForecast

MarketingMix

Web

Print

Fax

EmailWeb


33/327

Introduction 13

Enterprise applications such as SAP R/3 rely on the output environment to

deliver the critical daily, weekly and month-end reports to a single end user or

groups of management teams. It is the responsibility of the enterprise output

manager to orchestrate and deliver these reports according to the business

rules that have been defined by the process engineers. Figure 6 on page 12

shows a typical output environment.

Tivoli Output Manager can do the following:

Centralize output management

Controlled access of output resources

Routed output resources

Reliable and secure output channels

Automated delivery channels

1.4.6.1 Centralized Output Management

Figure 7. Centralized Control of Output Resources

Tivoli Output Manager provides administrators the option of fully centralized

administration, fully distributed administration or a mix of both environments.

The consoles that the administrators use are based on Java. Two types of

consoles are available. One console manipulates the structure of the

environment, and the other console performs operation of the environment.

The console that manipulates the environment logs on to the enterprise

component of Tivoli Output Manager and can cause WAN network traffic. The

New York

Sydney Paris NT

Central Control: Applications Security/Access Standard Policies Alert Escalation

Central Control:Central Control:

ApplicationsApplications

Security/AccessSecurity/Access Standard PoliciesStandard Policies

Alert EscalationAlert Escalation

Lights Out

Management

Lights OutLights Out

ManagementManagement

Remote Sites

Lights Out

Management

Lights OutLights Out

ManagementManagement

UNIX

Distributed Control:

Local applications Local monitoring

Distributed Control:Distributed Control:

Local applicationsLocal applications Local monitoringLocal monitoring


34/327


console that manipulates the operational structure logs on to the Domain

component of Tivoli Output Manager and can cause LAN network traffic.

The consoles will show all the alerts of the defined resources in the output

network. The consoles are also used to monitor output activity and t rack it

closely and proactively.

1.4.6.2 Controlled Access of Output Resources

Administrators and users are defined across all the output resources forglobal policy adherence and consistency. These definitions are distributed

and activated throughout the output network and are done by administrators

with the needed security profile.

Just like administrators, users also have to go through the authorization

layers to use the output network. This provides user-to-user notifications and

reliable access control of the output resources in the output network.

1.4.6.3 Routed Output Resources

Tivoli Output Manager is based on a rule base foundation. When certain

resources are down, fault tolerant routing rules could still deliver and notify

the appropriate people of the different path that was used. This is very useful

for mission-critical reports.

The rule engine can also re-spool and extract archive documents to output

resources if duplicates are detected. This is very useful for streamlining the

output environment and prevent huge reports from duplicating over slow

network links between distribution centers.

1.4.6.4 Reliable and Secure Output Channels

The delivery path from the users workstation to the output resource is always

in an encrypted form. The packets flowing between the users workstation

and the output destination are not visible for LAN sniffers and packet

analyzers, thus a good way to deliver documents over the Internet safely and

securely.

Tivoli Output Manager provides definitions for secure output resources. This

allows the users to rely on the output network for delivery to all the securedevices if their favorite device is offline.

The secure output channels are defined by the administrator and allow

specific users or groups like the executive team to use these printers.


35/327

Introduction 15

1.4.6.5 Automated Delivery Channels

This option of Tivoli Output Manager lets you define rules on certain output

resources, for example, aggregate all printing from a certain print server and

archive the data onto disk.

This attribute at first glance seems inappropriate but when it comes to

enterprise security and re-routing of output devices it makes sense. With

automated delivery channels you can track headers and apply audit rules to

all or some of your channels.

1.4.7 Tivoli Database Management Products

The Tivoli database management products allow for the seamless

management of RDBMS components with Tivoli. Similar to the Tivoli Manager

for R/3 they use the Tivoli Framework and core applications to manage a

certain application, in this case RDBMS servers.

This is important for the management of R/3 systems, as R/3 uses an

RDBMS to store its data. Hence, to provide management of the system, not

only the application, networks and operating systems need to be managed,

but also the RDBMS servers. As the Tivoli database management products

are based on Tivoli, management follows the same procedure asmanagement for any other component.

Tivoli database management products are available for a wide range of

RDBMS servers, including Oracle, Sybase, DB2, MS SQL Server and

Informix.

A detailed discussion of all available Tivoli database management products

can be found in the redbook Managing RDBMS Servers with Tivoli,

SG24-5240.

1.4.8 Tivoli NetView

Tivoli NetView is Tivolis network management solution that is focused onmanaging IP-based networks. NetView displays the nodes in the network on

a map representing the network topology and the status of network nodes.

In the case of something happening in the network, NetView generates

SNMP traps that are displayed in a central event window and which can

trigger actions or correlations. In that regard NetView is similar to TEC.

However, NetView is exclusively focused on processing SNMP events,

usually events related to the network.


36/327


NetView events, however, can be forwarded to TEC, which allows correlation

with events from other sources, for example, from the R/3 system. A simple

example could be that TEC receives an event indicating that the R/3

application server is down and also receives an event from NetView before

indicating that the network node on which the application server is running is

down.

A correlation rule can then find the dependency between the two events and

take appropriate action.

1.4.9 Tivoli Service Desk

Tivoli Service Desk is Tivolis solution for enterprise help desk

implementations. Tivoli Service Desk is integrated with other Tivoli

applications, for example, events in Tivoli Enterprise Console can be used to

generate problem records in Tivoli Service Desk.

As SAP R/3 can be managed by these Tivoli components, including Tivoli

Enterprise Console and Tivoli Distributed Monitoring (through Tivoli Manager

for R/3) problem management for the R/3 system can be seamlessly

integrated with the enterprise problem management process.

We will not discuss Tivoli Service Desk in detail in this redbook. A detailed

discussion of Tivoli Service Desk can be found in the redbook Problem

Management Using Tivoli Service Desk and TEC, SG24-5301.

1.4.10 Tivoli Global Enterprise Manager

Tivoli Global Enterprise Manager (GEM) is Tivolis solution for managing

applications and systems from a business perspective. Once an application isinstrumented for GEM, Tivoli allows management of this component in the

wider context of a business system.

While at the moment, Tivoli Manager for R/3 1.5 does not provide GEM

instrumentation, the next version of the product will provide thisinstrumentation.

The following figure gives you an idea of what that GEM integration will look

like:


37/327

Introduction 17

Figure 8. SAP R/3 Managed as a Business System

1.4.11 Tivoli Adstar Distributed Storage Manager (Tivoli ADSM)

ADSM is Tivolis enterprise backup/restore and archive/retrieve solution that

is available on a wide range of platforms. ADSM provides integration of

several databases and applications, such as DB/2, Oracle, Lotus Notes, SAP

R/3 etc.

The ADSM connection to SAP R/3 allows the customer to back up his SAP

R/3 database and archive his SAP R/3 application data with one utility.

1.5 Tivoli Manager for R/3

We give a brief overview of the Tivoli Manager for R/3 functions in this

section, as we explore all the functions available in detail later in this

redbook.


38/327


Tivoli Manager for R/3 is a key component in the mananagment of R/3

systems with Tivoli. It should, however, be noticed that this product is one of

the many Tivoli components that can be used to implement an

enterprise-wide management solution for R/3 systems, as we described in

the previous section.

While the other Tivoli management components refer to more general areas

of systems management, the Tivoli Manager for R/3 deals with specifics of

the management of the R/3 system, while at the same time leveraging theTivoli core applications.

Tivoli Manager for R/3 provides management for the R/3 component in the

areas of:

Availability management

Task automation

Deployment

Secure delegation

For availability management, the Tivoli Manager for R/3 utilizes Tivoli

Distributed Monitoring and Tivoli Enterprise Console. An event adapter isprovided that sits on top of the R/3 MIB that is provided with data from CCMS.

The event adapter then transforms the events into TEC events.

Using a similar concept, Tivoli Distributed Monitoring is used to provide

synchronous monitoring of the R/3 system. For that purpose, Tivoli Manager

for R/3 provides dedicated R/3 monitoring collections.

Tivoli Manager for R/3 provides a number of tasks to operate the R/3 system

from the Tivoli Desktop. This allows for secure and easy execution for certainR/3 tasks from anywhere in the network. Since Tivoli authorization is used for

running tasks, this also provides robust security, for example, by using

dedicated TMR roles.

A typical challenge in the management of R/3 installations is the deployment

of the SAP graphical user interface (SAPGUI) to a large number of desktops.

This task can be automated by using Tivoli Software Distribution and the tools

for creating file packages for SAP R/3 that come with Tivoli Manager for R/3.

Since Tivoli Manager for R/3 runs on the Tivoli Framework, all security

capabilities can be leveraged for the management for R/3, such as policy

regions, TMR roles and resource roles. Specifically, the Tivoli Framework

allows for secure delegation of management tasks. For example, routine


39/327

Introduction 19

tasks can be handed to junior administrators giving them exactly the

authorization level required.

1.6 The Benefits of Using Tivoli to Manage R/3

Managing an enterprise R/3 system is a complex and expensive task. The

SAP R/3 systems will be around for quite some time, maybe 15-20 years.

They will need to be fed and maintained.

This is where the Tivoli solution comes into place. Tivoli can significantly drive

down the lifecycle cost of SAP R/3. Tivoli does that by providing a framework

that allows R/3 to be managed within existing service levels and processes

that hold down cost.

We show in this redbook how R/3 can be managed within the context of the

enterprise I/T system. You will see that R/3 can be managed by Tivoli using

the same paradigm that is used for any other component in the I/T system. Atthe same time, dedicated Tivoli solutions for the management for R/3, such

as Tivoli Manager for R/3 and Tivoli Maestro Extended Agent for R/3, provide

management functions specific to R/3.

By integrating management of R/3 with the enterprise management platform

provided by Tivoli, the management of the R/3 system becomes more

effective, accountable and secure. Costs for maintaining the R/3 systems will

go down significantly as a number of management tasks can be standardized

and streamlined using Tivoli, thus allowing you to shift these tasks from

expensive R/3 specialists to a general I/T help desk.

We will show a number of examples of how R/3 can be managed using Tivoli

in this redbook, including software distribution of SAPGUI, monitoring of R/3

as part of the I/T system, managing R/3 jobs and output and more.

The Tivoli SAP solution can complement the SAP system in many ways that

help to minimize the impact of SAP operations on the overall business.

1.7 Where to Find What

We start in Chapter 2, Installation Planning on page 21 by briefly outlining

the planning that has to take place before starting to implement a

management solution for R/3. We give an overview of all the Tivoli

components involved so that a system designer can easily create a

management solution including the needed components.


40/327


In Chapter 3, Setting Up the SAP R/3 Management Environment on page 31

we show in detail how to install and configure all Tivoli management products

selected for our examples in our own environment. This includes the Tivoli

Manager for R/3, Tivoli Workload Scheduler and Tivoli Output Management.

In Chapter 4, Using the SAP R/3 Management Environment on page 131 we

use the management products set up in Chapter 3, Setting Up the SAP R/3

Management Environment on page 31. We perform basic management

examples in the environment we have set up and explain in detail how eachcomponent in the management system works. For example, we explain in

detail how Tivoli Manager for R/3 works in combination with CCMS.

In Chapter 5, Management Scenarios on page 215 we investigate some

real-life scenarios that represent typical requirements when building a

management solution for R/3. For example, we investigate how the Tivoli

Manager for R/3 works in interconnected TMRs and explain which monitors to

select in a production environment.


41/327

Copyright IBM Corp. 1999 21

Chapter 2. Installation Planning

In this chapter we discuss some of the planning considerations that have to

take place before installing the necessary Tivoli components in our

environment to manage the SAP R/3 installation.

2.1 Overview and Objective

It is important to understand the many components involved in building an

SAP R/3 management solution before actually implementing the systems

management products.

In this chapter we explain how to define the requirements for the management

of the R/3 installation, how to select the management products and how to

design an effective systems management solution for SAP R/3.

This chapter, however, can give you only some ideas to get started and

cannot replace a thorough planning process for designing your R/3

management solution.

We strongly advise that all large-scale systems management deployments forR/3 be guided by an experienced I/T architect who understands the R/3

architecture and, more importantly, the overall systems management

architecture of the environment.

2.2 Defining Management Requirements for SAP R/3

Before thinking of implementing a management solution for SAP R/3, the

management requirements for the SAP R/3 system must be clear. While

some of these requirements may be obvious and quite precise, others may be

more complex and more difficult to describe precisely.

This is why it is very important to structure the requirements in a form thatallows for proper selection of adequate tools and for designing an effective

overall solution.

Lets start with looking at a few typical management requirements for an R/3

management solution:

An administrator must be notified when an exception at the R/3 system

occurs and if possible, the problem must be corrected automatically.


42/327


Software updates in the R/3 system, especially for the many SAPGUI

clients, must be automated and must be able to be triggered from one

central location.

It must be able to perform synchronous monitoring and asynchronous

monitoring of the R/3 system and all relevant components. That is,

constant checking of critical system parameters must be possible as well

as triggering a notification when an unexpected event occurs.

The SAP R/3 system must be available to the end users 24 hours a day, 7days a week.

The availability of all components that are critical for the R/3 system must

be ensured by the management solution.

A help desk operator must be assisted by the management solution so

that calls related to R/3 can be resolved efficiently, even when other

components than the R/3 system are involved.

The management solution must be consistent with the management

solution that is employed for other applications, databases, systems or

networks.

These are just a few example requirements, but you can see that they differ inquality. While some requirements, such as automatic software distribution or

monitoring of the R/3 system are relatively precise and easy to match with a

product, others require a view of the entire IT system.

In the following sections we will give some help on structuring the

requirements.


43/327

Installation Planning 23

Figure 9. Management Layers

First of all, it is important to understand that an application such as SAP R/3

relies on many components of the IT system. Therefore, for an effectivemanagement of the R/3 system, most of these components must be covered

by the proposed management solution. For example, since R/3 relies on a

relational database system, management of this RDBMS must be covered as

well as management of the R/3 application itself.

Other components that usually must be covered are management of the

operating system, for example, paging space, memory, etc. and of the

network.

While for almost any component in the IT system you can find a management

product in the marketplace, most of these tools provide only a very specific

management solution for a specific area (point products). A comprehensive

management solution, however, especially for a complex application systemsuch as R/3, must allow for integration of all the specific component

management functions.

This function is provided by the Tivoli Framework. This framework allows you

to unify the management processes for all applications, systems, databases

and networks by providing a common set of services and a unified graphical

user interface for management. The framework also allows you to scale the

management solution to the enterprise level.

OracleOracle

DB2DB2

Sybase

OperatingOperatingSystemSystem

DatabaseDatabase

MiddlewareMiddleware

ApplicationApplication

TCP/IP

SNMP

SNANetBIOS

UNIXNetWare

Windows 95

Windows NT

OS/2 OS/390

In housedeveloped

Vendorsupplied

(SAP, PeopleSoft)

Applicationdevelopment tools

(e.g. PowerBuilder)

MQSeries CICS

DCEEncinaOrbixTuxedo

MS SQL Server

Informix

IPX

Sybase

NetworkNetwork

Tivoli

DB2 Oracle


44/327


Thus, no matter what specific components will be included in the

management solution for R/3, the base will be the Tivoli Framework

implementation. One issue that needs to be resolved here is the design of the

framework infrastructure, such as the TMR design. As the Tivoli Framework is

the basis for the systems management for all components in the IT system,

the design of the framework infrastructure will most likely be based on

general requirements, for example, on branch office structures or department

structures and not on the specific requirements for managing R/3.

However, before selecting and implementing the Tivoli management products,

the Tivoli Framework structure has to be adjusted with the specific

requirements for the management of R/3. For example, it needs to be

determined which systems in the R/3 installation need to be Tivoli Managed

Nodes, etc.

Once the basic Tivoli Framework infrastructure is defined, the Tivoli

components need to be selected that are to become part of the management

solution. The components that are relevant for management for R/3 are listed

in more detail in 2.3, Selecting the Necessary Tivoli Components on page

25.

While some components are mandatory (for example, usually the Tivoli coreapplications such as Tivoli Software Distribution, Tivoli Distributed Monitoring

and Tivoli Enterprise Console), other components can be either optional or

required only at a later stage.

To illustrate this, lets look at an example. For the immediate management of

the R/3 system it is decided to first implement the Tivoli Manager for R/3,

which is the obvious choice, as this Tivoli component deals directly with the

management of the R/3 component.

The Tivoli Manager for R/3 requires the Tivoli Framework, so the design for

the framework layout needs to be in place. Further, the Tivoli Manager for R/3

requires some of the Tivoli core applications, namely Tivoli SoftwareDistribution, Tivoli Distributed Monitoring and Tivoli Enterprise Console.

In the next step, the management for R/3 could be unified with the

management of other components, for example, the Tivoli database

management products could be included to manage the RDBMS that is used

by R/3. Other components, though not directly related to R/3, are also

relevant for the management of the R/3 system, for example, management of

the network, which can be performed using Tivoli NetView.


45/327

Installation Planning 25

It is also important to understand that Tivoli components can add to the value

of the R/3 management solution but are currently not based on the Tivoli

Framework, two of which we explain in detail in this book: Tivoli Output

Management (formerly known as Destiny) and Tivoli Workload Scheduler

(formerly known as Maestro). Since these products do not require the Tivoli

Framework, but define their own topology requirements, a design for these

topologies needs to take place.

When defining requirements, it can also be found that the requirements arebased on the different levels of the management solution. For example, a

requirement on the lowest level could be: to monitor the availability of the R/3

application processes on all of the R/3 production systems.

On the next level, this requirement could be extended to require that, once an

R/3 application process goes down, a TEC event is sent to Tivoli Enterprise

Console, where it can be correlated with other events to determine the root

cause of the problem. While the first requirement can easily be implemented

by just using Tivoli Distributed Monitoring and Tivoli Enterprise Console, the

second case requires more integration with other components, for example,

Tivoli NetView.

We can reach even more abstraction and automation by generating troubletickets in Tivoli Service Desk for certain problems that were reported to TEC.

The service desk personnel can then use an existing knowledge base to fix

problems.

Due to the nature of these levels, in most cases it is appropriate to create an

initial design where all levels are considered and then employ an incremental

approach for the implementation. That is, start with the component specific

management tasks and then increase integration with other components

step-by-step.

2.3 Selecting the Necessary Tivoli ComponentsThe main purpose of this section is to give an overview of all Tivoli

components that can be useful for the management of a complex R/3 system.

This overview is presented in the form of a table. This table will help you in a


46/327


first evaluation of which products you might want to consider for your overall

solution.

Table 1. Tivoli Products for the Management of SAP R/3

Product Name Description Requires Use for ManagingR/3

Tivoli Framework Provides basicmanagement

infrastructure for allTivoli applications

n/a Provide scalability,security and other

generic services

Tivoli DistributedMonitoring

Tivoli applicationfor sy

Documents

Managing SAP R 3 With Tivoli