Tivoli Manager for R/3**publib.boulder.ibm.com/tividd/td/r3/GC31-8411-04/en_US/PDF/GC31-… · R3 UNIX and R3 Windows NT File System Monitors ..... 109 Default Profile Managers

Tivoli® Manager for R/3**User’s Guide Version 2.1

Tivoli® Manager for R/3**User’s Guide Version 2.1

Tivoli Manager for R/3 User’s Guide (September 2000)

Copyright Notice

Copyright © 1997, 2000 by Tivoli Systems Inc., an IBM Company, including this documentation and all software. All rightsreserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBMCustomer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system,or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual,or otherwise, without prior written permission of Tivoli Systems. Tivoli Systems grants you limited permission to make hardcopy orother reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry theTivoli Systems copyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. Thedocument is not intended for production and is furnished “as is” without warranty of any kind.All warranties on this document arehereby disclaimed including the warranties of merchantability and fitness for a particular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to restrictionsset forth in GSA ADP Schedule Contract with IBM Corporation.

Trademarks

The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RS/6000, Tivoli, Manage.Anything. Anywhere., The Power To Manage. Anything. Anywhere., TME, NetView, Cross-Site, Tivoli Ready, Tivoli Certified,Planet Tivoli, Tivoli Enterprise. In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group.

R/3 is a trademark of SAP AG.

Oracle is a registered trademark of Oracle Corporation.

Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.

Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available inall countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended toimply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli System’s or IBM’s validintellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead ofthe referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, exceptthose expressly designated by Tivoli Systems or IBM, are the responsibility of the user.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing ofthis document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director ofLicensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiWho Should Read This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

Prerequisite and Related Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

What This Guide Contains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Typeface Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Accessing Online Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Accessing the Files on the Product CD. . . . . . . . . . . . . . . . . . . . . . .xvii

Accessing the Files on the Tivoli Web Site. . . . . . . . . . . . . . . . . . . .xvii

Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

Contacting Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Chapter 1. Introducing Manager for R/3 . . . . . . . . . . . . . . . . . . 1Overview of the R/3 Environment with Tivoli. . . . . . . . . . . . . . . . . . . . . . . . 1

Manager for R/3 Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Availability Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Automatic Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Task Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Automated R/3 SAPGUI Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Security Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Extensibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

R/3 Release and System Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . 7

User Interface Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Integration with Tivoli Database Manager Products. . . . . . . . . . . . . . . . 8

Chapter 2. Planning for and Installing Manager for R/3 9Where to Install Manager for R/3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

iiiTivoli Manager for R/3 User’s Guide

Configuring Tivoli Management Regions. . . . . . . . . . . . . . . . . . . . . . . 10

Installing the Application Proxy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Planning for TEC Event Server Configuration. . . . . . . . . . . . . . . . . . . 13

Installing Manager for R/3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Upgrading to Version 2.1 from Version 1.5 or 1.5.1. . . . . . . . . . . . . . . 15

Upgrading to Version 2.1 from Version 2.0. . . . . . . . . . . . . . . . . . . . . 17

Installing Manager for R/3 Version 2.1. . . . . . . . . . . . . . . . . . . . . . . . 18

Uninstalling Manager for R/3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 3. Getting Started with Manager for R/3 . . . . . . . 27What Was Installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Manager for R/3 Object Endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring Manager for R/3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Assigning Authorization Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Using Manager for R/3 Configuration Tasks. . . . . . . . . . . . . . . . . . . . . . . . 35

R3 Configuration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

R3 List Maintenance Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Determining R/3 Application Server Status. . . . . . . . . . . . . . . . . . . . . . . . . 38

Determining R/3 Database Server Status. . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Determining R/3 ITS Server Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 4. Configuring Each SAP R/3 System . . . . . . . . . . 43Moving R/3 Transports into an R/3 Landscape. . . . . . . . . . . . . . . . . . . . . . . 44

Distributing the R/3 ABAP File Package. . . . . . . . . . . . . . . . . . . . . . . 45

Copying the Transports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Importing the Function Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

From the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Using the Transport Management System. . . . . . . . . . . . . . . . . . . . . . . 48

Configuring User IDs for RFC Interface Access. . . . . . . . . . . . . . . . . . . . . . 49

iv User’s Guide Version 2.1

Configuring R/3 Application Server Profiles. . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 5. Configuring Manager for R/3 . . . . . . . . . . . . . . . . 53Creating R/3 Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Deciding Where to Create R/3 Objects. . . . . . . . . . . . . . . . . . . . . . . . . 54

Creating R/3 Objects Using Automatic Discovery. . . . . . . . . . . . . . . . 55

Stopping Automatic Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Creating an R/3 Object from the Desktop. . . . . . . . . . . . . . . . . . . . . . 60

Results of Creating R/3 Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Deleting an R/3 Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Result of Deleting an R/3 System Object. . . . . . . . . . . . . . . . . . . . . . . 69

Result of Deleting an R/3 Application Server Object. . . . . . . . . . . . . . 69

Result of Deleting an R/3 Database Server Object. . . . . . . . . . . . . . . . 69

Result of Deleting an R/3 ITS Server Object. . . . . . . . . . . . . . . . . . . . 70

Creating Subscriber Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Configuring a Remote Function Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configuring Manager for R/3 for Windows NT. . . . . . . . . . . . . . . . . . . . . . 72

Creating Exit Routines for Windows NT. . . . . . . . . . . . . . . . . . . . . . . 72

Enabling the Local Administrator for SAP File Access. . . . . . . . . . . . . 73

Enabling Automatic Discovery for Windows NT. . . . . . . . . . . . . . . . . 73

Enabling the Tivoli Authentication Package for Windows NT. . . . . . . . 74

Setting the Environment Variable for Windows NT. . . . . . . . . . . . . . . 75

Configuring Manager for R/3 for HP-UX 11. . . . . . . . . . . . . . . . . . . . . . . . 75

HP-UX 11 64-bit Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

HP-UX 11 Shared Memory Windows. . . . . . . . . . . . . . . . . . . . . . . . . 75

Configuring Manager for R/3 for OS/390. . . . . . . . . . . . . . . . . . . . . . . . . . . 76

R/3 Release Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

R/3 Transports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

R/3 Database Objects with OS/390. . . . . . . . . . . . . . . . . . . . . . . . . . . 77

vTivoli Manager for R/3 User’s Guide

Data Sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Monitoring the OS/390 System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Extending Database Server Status Reporting. . . . . . . . . . . . . . . . . . . . . . . . 78

Chapter 6. Managing R/3 Events . . . . . . . . . . . . . . . . . . . . . . . . 81Configuring the TEC Event Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Configuring an Event Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Configuring Event Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Displaying Event Adapter Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Starting and Stopping an Event Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Using the Alert Event Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Understanding How the Alert Event Adapter Works. . . . . . . . . . . . . . . 88

Controlling Alert Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Using the Syslog Event Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Controlling Syslog Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Example of Controlling Syslog Events. . . . . . . . . . . . . . . . . . . . . . . . . 95

Using the IDOC Event Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Understanding How the IDOC Event Adapter Works. . . . . . . . . . . . . . 97

Viewing and Interpreting IDOC Events. . . . . . . . . . . . . . . . . . . . . . . . 98

Controlling IDOC Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Performance Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Filtering Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Chapter 7. Monitoring R/3 Resources . . . . . . . . . . . . . . . . . . 105Monitoring Collections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Monitoring Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

R3 ITS Server Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

R3 Server Remote and R3 Server Central Monitors. . . . . . . . . . . . . . 107

vi User’s Guide Version 2.1

R3 UNIX and R3 Windows NT File System Monitors. . . . . . . . . . . . 109

Default Profile Managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

R3 App Server Monitors Profile Manager. . . . . . . . . . . . . . . . . . . . . . 110

R3 DB Server Monitors Profile Manager. . . . . . . . . . . . . . . . . . . . . . 110

R3 Distributed Daemon Monitors Profile Manager. . . . . . . . . . . . . . . 111

R3 Managed Nodes Monitors Profile Manager. . . . . . . . . . . . . . . . . . 111

R3 ITS Monitors Profile Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 111

R3 Central Instance Monitors Profile Manager. . . . . . . . . . . . . . . . . . 111

Using Monitoring Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Using the Application Server Status Monitor. . . . . . . . . . . . . . . . . . . 113

Using the Storage Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Using the Performance Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Using the File System Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Using the User Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Using the Work Process Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Using the Cancelled Job Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Using OS Collect and OS/390 Monitors. . . . . . . . . . . . . . . . . . . . . . . 123

Chapter 8. Tasks for Managing R/3 Resources . . . . . . . . 127Running a Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

R3 System Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Controlling the R/3 System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

R3 App Server Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Controlling Event Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Controlling Application Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Displaying Application Server Performance Information. . . . . . . . . . . 134

Managing Batch Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Controlling R/3 Work Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

R3 DB Server Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

viiTivoli Manager for R/3 User’s Guide

Controlling a Database Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Controlling dbaccess. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

R3 ITS Server Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Controlling ITS Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Chapter 9. Distributing SAPGUI Software . . . . . . . . . . . . . 139Creating SAPGUI Software File Packages. . . . . . . . . . . . . . . . . . . . . . . . . 139

Creating SAPGUI File Packages for SAPGUI Versions Prior to 4.5B 140

Creating SAPGUI File Packages for Windows SAPGUI Versions4.5B and Later. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Distributing SAPGUI Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Chapter 10. Tivoli GEM Instrumentation . . . . . . . . . . . . . . . 147Understanding the Tivoli GEM Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Understanding the Tivoli GEM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Tivoli GEM Instrumentation Event Handling. . . . . . . . . . . . . . . . . . . . . . . 149

Instrumented Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Instrumentation Task Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Preparing to Install Manager for R/3 Instrumentation. . . . . . . . . . . . . . . . . 150

Tivoli Management Regions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Administrators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Installation Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Installing and Configuring Tivoli GEM Instrumentation for Manager forR/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Installing or Upgrading the Tivoli GEM Instrumentation DefinitionFiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Installing the Tivoli GEM Instrumentation Task Libraries. . . . . . . . . . 152

Adding the Tivoli GEM Instrumentation Rule Set. . . . . . . . . . . . . . . 154

Synchronizing the Tivoli GEM Console with the Desktop. . . . . . . . . . . . . 154

Understanding R/3 Aggregate Resources. . . . . . . . . . . . . . . . . . . . . . 155

viii User’s Guide Version 2.1

Navigating to R/3 Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Tivoli GEM Instrumentation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

R3System Component Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

R3Application Component Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

R3Database Component Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

R3ITSServer Component Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Using the Tear-Away Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Running a Task from the Tivoli GEM Console. . . . . . . . . . . . . . . . . . 159

Supported Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Monitor Operability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Viewing Monitor Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Instrumenting Tivoli GEM Connection Support to R/3 Components. . . . . . 162

Instrumenting a Connection to an R3System Component. . . . . . . . . . 163

Instrumenting a Connection to an R3Application Component. . . . . . . 163

Instrumenting a Connection to an R3ITSServer Component. . . . . . . . 164

Instrumenting a Connection to an R3Database Component. . . . . . . . . 164

Uninstalling Tivoli GEM Instrumentation Task Libraries. . . . . . . . . . . . . . . 165

Appendix A. Command Line Interface Commands 167Command Line Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

SysMan and RFC Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

wr3mib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

wr3rfc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Appendix B. Event Classes and Rules . . . . . . . . . . . . . . . . . 179Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

R/3 Alert Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

R/3 Operational Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

R/3 Syslog Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

R/3 IDOC Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

ixTivoli Manager for R/3 User’s Guide

Distributed Monitoring Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . 191

Status Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Tivoli GEM Instrumentation Event Classes. . . . . . . . . . . . . . . . . . . . 192

Tivoli GEM Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Error Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Alert Event Slots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Syslog Event Slots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

IDOC Event Slots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Cancelled Job Event Slots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

CCMS-Generated Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Rules for Manager for R/3 Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Duplicate Event Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Automatic Closing of Harmless Events. . . . . . . . . . . . . . . . . . . . . . . 200

Automatic Drill-Down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Bidirectional Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Event Correlation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Multi-Region Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Integration with Tivoli GEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Integration with Tivoli Database Manager Products. . . . . . . . . . . . . . 201

TEC Event Server Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Distributed Monitoring Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Database Status Integration Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Correlation Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Tivoli GEM Instrumentation Distributed Monitoring Rules. . . . . . . . . 205

Appendix C. Remote and Central MonitoringSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

OS Collect Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Roll Area Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

x User’s Guide Version 2.1

Page Area Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Work Process Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Work Process Dispatch Queue Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Long Running Work Process Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Buffer Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Performance Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Heap Memory Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Extended Memory Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

User Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

OS/390 DB2 Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

OS/390 Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Appendix D. IDOC Status Codes . . . . . . . . . . . . . . . . . . . . . . . 219

Appendix E. Function Module Authorization . . . . . . . . . . 223

Appendix F. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Appendix G. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . 255Setting Up the Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Task Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Monitor Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Event Adapter Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Miscellaneous Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

TEC Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Error Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Event Diagnostic Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Configuring Monitor Logging Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

xiTivoli Manager for R/3 User’s Guide

SAPGUI File Package Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Icon State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

File System Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Hints on Using Tivoli GEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Using the Tivoli GEM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Tivoli GEM Icon State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Tivoli GEM Server Database Corruption. . . . . . . . . . . . . . . . . . . . . . 276

Business and Component Description Files. . . . . . . . . . . . . . . . . . . . 276

Icon Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

xii User’s Guide Version 2.1

Preface

The Tivoli Manager for R/3 User’s Guideprovides informationabout planning for, installing, and managing R/3 systems with TivoliManager for R/3 (Manager for R/3). This guide describes the tasksand monitors that Manager for R/3 provides. It also describes how todistribute SAPGUI software.

Who Should Read This GuideThis guide is for system administrators who monitor and manage R/3systems. This guide requires knowledge of Tivoli managementsoftware, UNIX and Windows operating systems, databases, SAPR/3, and optionally, the Tivoli Global Enterprise Manager (TivoliGEM), Tivoli Manager for DB2, and Tivoli Manager for Oracleproducts.

Prerequisite and Related DocumentsFor hardware and software requirements, and other releaseinformation, refer to theTivoli Manager for R/3 Release Notes.

Related documents include:

¶ TME 10 Framework User’s Guide

¶ TME 10 Framework Planning and Installation Guide

¶ TME 10 Framework Reference Manual

¶ TME 10 Enterprise Console Rule Builder’s Guide

¶ TME 10 Enterprise Console User’s Guide

¶ TME 10 Enterprise Console Reference Manual

¶ TME 10 Enterprise Console Event Integration Facility Guide

¶ TME 10 Enterprise Console Adapters Guide

¶ TME 10 Distributed Monitoring User’s Guide

¶ TME 10 Software Distribution User’s Guide

xiiiTivoli Manager for R/3 User’s Guide

Related documents for Tivoli Global Enterprise Manager Version2.2.1 include:

¶ Tivoli Global Enterprise Manager Installation and User’s Guide

¶ Tivoli Global Enterprise Manager Instrumentation Guide

¶ Tivoli Global Enterprise Manager Release Notes

Related documents for Tivoli database manager products include:

¶ Tivoli Module for DB2 User’s Guide

¶ Tivoli Module for DB2 Release Notes

¶ Tivoli Manager for Oracle User’s Guide

¶ Tivoli Manager for Oracle Release Notes

What This Guide ContainsThis User’s Guide contains the following sections:

¶ “Introducing Manager for R/3” on page 1

Describes the basic features and functions of Manager for R/3.

¶ “Planning for and Installing Manager for R/3” on page 9

Describes installation requirements, how to install Manager forR/3, and how to uninstall Manager for R/3.

¶ “Getting Started with Manager for R/3” on page 27

Describes the information you need to get started and providesan overview of the tasks you must complete before you can useManager for R/3.

¶ “Configuring Each SAP R/3 System” on page 43

Describes how to prepare an R/3 system for use with Managerfor R/3.

¶ “Configuring Manager for R/3” on page 53

Describes how to create R/3 system objects and server objects soyou can manage your R/3 systems, R/3 application servers, R/3database servers, and R/3 ITS servers with Manager for R/3.

xiv User’s Guide Version 2.1

This chapter also describes how to configure a remote functioncall and contains information about platform-specificconfiguration tasks.

¶ “Managing R/3 Events” on page 81

Describes how to configure the TEC event server, eventconsoles, and Manager for R/3 Alert Event Adapter, SyslogEvent Adapter, and IDOC Event Adapter.

¶ “Monitoring R/3 Resources” on page 105

Describes Manager for R/3 monitoring collections, profilemanagers, and profiles.

¶ “Tasks for Managing R/3 Resources” on page 127

Describes Manager for R/3 management tasks.

¶ “Distributing SAPGUI Software” on page 139

Describes how to create R/3 SAPGUI software file packages fordistribution of the SAPGUI for the Windows NT, Windows95/98, and UNIX operating systems.

¶ “Tivoli GEM Instrumentation” on page 147

Describes planning, installation, and configuration of TivoliGEM instrumentation. It also describes the tasks and monitorsthat become accessible for managing R/3 after the Tivoli GEMcomponents have been successfully installed.

¶ “Command Line Interface Commands” on page 167

Describes the supported command line interface (CLI)commands that you can use with Manager for R/3.

¶ “Event Classes and Rules” on page 179

Describes the TEC event classes and rules delivered withManager for R/3, slot values for the events, and backgroundinformation on R/3 alerts.

¶ “Remote and Central Monitoring Sources” on page 207

Describes the monitoring sources and their attributes for the R3Server Remote Monitors and R3 Server Central Monitorscollections.

¶ “IDOC Status Codes” on page 219

xvTivoli Manager for R/3 User’s Guide

Describes the IDOC status codes.

¶ “Function Module Authorization” on page 223

Contains a list of the function modules delivered with Managerfor R/3 and the R/3 authorization required to run each module.

¶ “Messages” on page 227

Contains a list of the messages produced by Manager for R/3.

¶ “Troubleshooting” on page 255

Describes the diagnostic techniques for tasks, monitors, TivoliGEM instrumentation, and SAPGUI distribution. This sectiondescribes diagnostic commands and product directories.

Typeface ConventionsThis guide uses several typeface conventions for special terms andactions. These conventions have the following meaning:

Bold Commands, keywords, flags, and other information that youmust use literally appear inbold.

Italics Variables and new terms appear initalics. Words and phrasesthat are emphasized also appear initalics.

MonospaceCode examples, output, and system messages appear in amonospace font.

Accessing Online DocumentationManager for R/3 documentation is available in the following onlineformats on both the Manager for R/3 CD and the Tivoli Web site:

¶ Portable Document Format (.pdf, which you can view or printusing the Adobe Acrobat Reader). If you do not already haveAdobe Acrobat Reader, you can obtain it for free by clicking theGet Acrobat Reader icon at the Adobe Web site,http://www.adobe.com, and following the steps that are provided.

¶ Hyptertext Markup Language (.htm), which you can view usingyour default Web browser.

xvi User’s Guide Version 2.1

Accessing the Files on the Product CDThe .pdf and the .htm files, (sa21ug.pdf and sa21ug.htm) for theTivoli Manager for R/3 User’s Guideare available on the Managerfor R/3 CD in the /DOC directory.

Note: The Tivoli Manager for R/3 Release Notesdocument is notprovided on the Manager for R/3 CD.

Accessing the Files on the Tivoli Web SiteThe Tivoli Manager for R/3 User’s Guideand theTivoli Managerfor R/3 Release Notesare available at the following location on theTivoli Web site: http://www.tivoli.com/support/documents.

You must be a registered user to access this Web site. If you havenot registered, when the Username and Password Required prompt isdisplayed, clickCancel and follow the registration directions.

TerminologyThe following R/3 terms are used throughout this document:

ALE Application Link Enabling, the SAP communication levelfacililty for transferring IDOCs between R/3 systems.

application serverThe component of an R/3 system that processes customerwork requests.

authorization profileWithin an R/3 system, an authorization profile is a collectionof authorization objects. An authorization profile, whenassigned to an R/3 user, defines the functions that the user isallowed to perform.

central instanceThe R/3 application server that is running the messageserver.

database serverThe component of an R/3 system that handles databaserequests.

xviiTivoli Manager for R/3 User’s Guide

function moduleAn R/3 ABAP program that has a clearly defined interfaceand can be used in several programs. The function modulelibrary manages all function modules and provides searchfacilities in the development environment.

IDOC Intermediate Document, an internal SAP self-defining datastructure for the transfer of business objects in a well-definedmanner.

Internet Transaction Server (ITS server)The component of an R/3 system that provides an interfacebetween the World Wide Web and the R/3 system. An ITSserver consists of the following components:

AGateThe component that bridges an R/3 applicationserver to a WGate.

WGateThe component that bridges an AGate to a standardWeb server.

A single-host ITS server configuration is one in which boththe AGate and WGate components run on the same machine.A dual-host ITS server configuration is one in which theAGate and WGate components run on different machines.

instance numberA two-digit number identifying an R/3 application server,assigned when an R/3 administrator installed the R/3application server.

landscapeA set of R/3 systems that share the same transport directory.

RFC (remote function call)A protocol for invoking R/3 modules.

SAPGUISAP graphical user interface, the R/3 presentation software.

SID (system identifier)The three-character name of an R/3 system.

xviii User’s Guide Version 2.1

transport fileA set of ABAP objects to be imported into an R/3 system.

For a complete glossary of Tivoli and related terms, refer to theglossary at the following Web site:

http://www.tivoli.com/products/documents/glossary.

Tivoli is in the process of changing product names. Productsreferenced in this manual might still be available under their oldnames, for example, TME 10 Module for DB2 instead of TivoliManager for DB2.

Contacting Customer SupportFor support for this or any other Tivoli product, you can contactTivoli Customer Support in one of the following ways:

¶ Visit our Web site at http://www.support.tivoli.com.

¶ Send e-mail to [email protected]

Customers in the United States can also call1–800–TIVOLI8.International customers should consult the Web site for customersupport telephone numbers. You can also review the CustomerSupport Handbook, which is available on our Web site athttp://www.tivoli.com/support/handbook.

When you contact Tivoli Customer Support, be prepared to provideidentification information for your company so that supportpersonnel can assist you more readily. Company identificationinformation might also be needed to access various online servicesavailable on the Web site.

The Web site offers extensive information, including a guide tosupport services (the Customer Support Handbook); frequently askedquestions (FAQs); and documentation for all Tivoli products,including Release Notes, redbooks, and Whitepapers. The

xixTivoli Manager for R/3 User’s Guide

documentation sets for some product releases are available in bothPDF and HTML formats. Translated documents are also available forsome product releases.

You can order documentation by e-mail at [email protected]. Pleaseprovide the part number or order number of the desired document;alternatively, you can provide the document’s title, version number,and date of publication.

We are very interested in hearing about your experience with Tivoliproducts and documentation. We also welcome your suggestions forimprovements. If you have comments or suggestions about ourdocumentation, please contact us in one of the following ways:

¶ Send e-mail to [email protected].

¶ Fill out our customer feedback survey athttp://www.tivoli.com/support/feedback.

xx User’s Guide Version 2.1

Introducing Manager for R/3

This chapter provides a brief overview of Tivoli Manager for R/3 asit relates to R/3 systems. It provides a summary of the productfunctions.

Overview of the R/3 Environment with TivoliA typical R/3 environment includes one or more R/3 systems, whereeach R/3 system consists of one database server and one or moreapplication servers. The R/3 application servers can run on theUNIX and Windows NT operating systems. The database servers canrun on the UNIX, Windows NT, and OS/390 operating systems.

The typical Tivoli management environment consists of a TivoliManagement Region (TMR) server, a Tivoli Event Console (TEC)server, managed nodes, TMA endpoints, and gateways.

Manager for R/3 operates at both the machine level and the R/3system level:

¶ To manage at the machine level, Manager for R/3 uses monitorsprovided with the Tivoli Distributed Monitoring product. Thesemonitors provide status on the machines and daemons.

¶ To manage at the R/3 system level, Manager for R/3 usesmonitors, event adapters, and tasks provided with the Managerfor R/3 product. Manager for R/3 represents each R/3 systemand server as a Tivoli object. Each object is a special type ofTivoli endpoint that enables Manager for R/3 to distribute

1

1Tivoli Manager for R/3 User’s Guide

1.Introducing

Manager

forR

/3

monitors and tasks directly to the endpoint. As with any Tivoliendpoint, you can run a task against one or more applicationservers across the R/3 systems that the TMR server manages.For more information, see “Manager for R/3 Object Endpoints”on page 29.

Manager for R/3 provides three event adapters that run on R/3application servers. Two of these event adapters, the Alert EventAdapter and the Syslog Event Adapter, should be configured foreach R/3 application server. The third event adapter, the IDOC EventAdapter, needs only to be configured for one R/3 application serverin each R/3 system.

R/3 application servers are the primary resources used by Managerfor R/3 in managing the R/3 system. The application servers providemanagement information about themselves. In addition, theapplication servers are gateways for collecting R/3 database serverinformation. Manager for R/3 obtains performance information aboutthe R/3 database server through calls made to one of the R/3application servers, which allows Manager for R/3 to gather databaseinformation for all platforms, including DB2 on OS/390.

Manager for R/3 FunctionsManager for R/3 makes it easier for you to manage SAP R/3installations by providing the following features:

¶ Availability management

¶ Automatic discovery

¶ Task libraries

¶ Automated R/3 SAPGUI installation

¶ Security enhancements

¶ Extensibility

¶ R/3 release compatibility

¶ User interface options

¶ Integration with Tivoli database manager products

2 User’s Guide Version 2.1

Availability ManagementWith Manager for R/3, you can monitor and retrieve R/3 alert trapsand R/3 syslog messages using the Alert Event Adapter and theSyslog Event Adapter, respectively. You can also monitor the transferof business data from one R/3 system to another using the IDOCEvent Adapter. With the monitoring collections, you can monitor R/3application servers, Internet transaction servers (R/3 ITS servers),and R/3 file systems and daemons. When so configured, events areforwarded to a TEC event server for display and processing. You canuse the filtering capabilities to send specific events to the TEC.Manager for R/3 determines the availability of R/3 servers fromstatus events and represents server availability through the icon foreach R/3 server.

R/3 Alert Event AdapterThe R/3 Computing Center Management System (CCMS) containsan alert facility that monitors critical elements of the R/3 system andnotifies administrators of potential problems. CCMS publishes someof this information through its R/3 System Management (SysMan)interface. Manager for R/3 provides a Tivoli Enterprise Console(TEC) event adapter for querying the R/3 SysMan interface andconverting the R/3 alert traps into TEC events.

R/3 Syslog Event AdapterManager for R/3 provides a TEC event adapter that processes theR/3 syslog and converts new entries to TEC events.

R/3 IDOC Event AdapterManager for R/3 provides a TEC event adapter that monitors SAPIntermediate Documents (IDOCs) for error status codes and reportsthem as TEC events. R/3 systems use IDOCs to transfer businessdata between business systems. A business system can be an R/3system or a customer application. Successful transfer of IDOCs iscrucial to ensure that all R/3 systems are synchronized on thebusiness data they are processing.

Monitoring CollectionsManager for R/3 supplies a set of monitoring collections that providemonitors for R/3 resources. These Tivoli Distributed Monitoring


1.Introducing

Manager

forR

/3

collections provide a wide range of internal and external R/3monitors, such as monitoring performance statistics from the R/3SysMan, or monitoring internal R/3 buffer statistics by using the R/3Remote Function Call (RFC) interface. Manager for R/3 alsoprovides monitoring collections that provide monitors for R/3 ITSservers and R/3 file systems and daemons. You can configure thethresholds and responses to proactively monitor and create differentseverity levels of TEC events. See “Monitoring R/3 Resources” onpage 105 for more information.

Tivoli Enterprise Console (TEC)The TEC provides a consolidated event view for one or more R/3systems, so that you can create and configure different views for anynumber of R/3 administrators and R/3 systems.

TEC Event Server Rule BaseThe TEC event server rule base provides intelligent event processingand correlation. The Manager for R/3 TEC rule sets can be extendedto meet local processing requirements. TheTivoli Enterprise ConsoleRule Builder’s Guidedescribes a non-programming environment forextending the functionality of the rule sets. For example, you caneasily automate the gathering of additional diagnostics for a specificevent by specifying the trigger event and the desired task.

The Manager for R/3 provides rules that enable these functions:

¶ Duplicate event checking

¶ Automatic closing of harmless events

¶ Automatic drill-down

¶ Bidirectional communication

¶ Event correlation

¶ Multi-region support

¶ Integration with Tivoli GEM


For more information, see “Rules for Manager for R/3 Events”on page 199.


Automatic DiscoveryManager for R/3 provides an automatic discovery function thatdiscovers existing R/3 systems and servers and creates theappropriate Tivoli objects. Manager for R/3 provides a task thatenables you to configure when to run the automatic discoveryfunction. For more information, see “Creating R/3 Objects UsingAutomatic Discovery” on page 55.

Task LibrariesManager for R/3 provides a set of task libraries to assist inperforming operational and administrative tasks. By using thesetasks, you can start, stop, and display R/3 resources and configureManager for R/3 to meet the unique needs of each R/3 system beingmanaged. See “R3 Configuration Tasks” on page 36 and “Tasks forManaging R/3 Resources” on page 127 for more information aboutthese tasks.

Automated R/3 SAPGUI InstallationThe R/3 presentation software, usually known as the SAP graphicaluser interface (SAPGUI), runs on UNIX systems (with the Motifwindow manager), Windows NT systems, and Windows 95/98systems. Manager for R/3 enables you to create a customizedSAPGUI installation file package. The installation of the SAPGUIfile package creates the necessary program groups and icons on theuser's desktop. The following functions are provided:

¶ SAPGUI support for R/3 releases. For information aboutsupported R/3 releases, refer to theTivoli Manager for R/3Release Notes.

¶ SAPGUI installation tasks specifically configured for eachdesignated R/3 release.

¶ Installation of optional SAPGUI components. For example, youcan configure a file package to include graphics, spreadsheetmacros, and the remote function call components.

¶ Language selection

¶ Before and after installation processing, including:


1.Introducing

Manager

forR

/3

v Free space checking. The amount of free space required isautomatically calculated by the components selected. Thetarget system is checked for adequate free space before theinstallation begins.

v Platform type checking. The Tivoli Software Distributionprocess automatically checks that the proper architecture orplatform type is distributed to the endpoint.

v Optional SAPGUI command execution. The SAPGUIinstallation dialogs provide for easy input of two SAPGUIinstallation commands. This makes it possible to easilyenhance the SAPGUI installation scripts that allow remotefile system mounting with a simple network command.

¶ Administrator-defined file package organization, which enablesyou to organize file packages by business requirements ratherthan by operating system or processor architecture types. Forexample, you can organize and distribute SAPGUI installationfile packages by marketing, sales, or Computer Aided Design(CAD).

Security EnhancementsSecurity enhancements include policy region resource roles andsecure external communication.

Policy Region Resource RolesManager for R/3 configures each R/3 system as its own policyregion. In addition, Manager for R/3 uses three resource roles.Giving a Tivoli administrator these resource roles in a particularpolicy region authorizes the administrator to perform certain R/3tasks. For additional information, see “Assigning AuthorizationRoles” on page 33.

Providing Secure External CommunicationUsing a configuration task, you can specify an R/3 user ID andpassword for each R/3 system. The Manager for R/3 uses this R/3user ID and password for remote function call (RFC) processes. Thepassword is stored in encrypted form. The Manager for R/3 accessprogram obtains the user ID and password as needed to access the


RFC functions and the corresponding Advanced BusinessApplication Programming (ABAP) function modules.

ExtensibilityExtensibility is provided by the Tivoli Framework and Manager forR/3 tools, monitoring collections (see “Monitoring Collections” onpage 3), and TEC event server rule sets (see “TEC Event ServerRule Base” on page 4).

Tivoli FrameworkThe Tivoli Framework and applications provide a comprehensivemanagement system. Manager for R/3 implements the mostimportant features of the Tivoli Framework and its applicationswhile maintaining all of the extensibility of the object framework.

Manager for R/3 ToolManager for R/3 provides a powerful tool in thewr3rfc programwhen run as a command. Thewr3rfc runs the R/3 function modulesthat support the RFC interface. You can use this command tomanage the R/3 environment. (See “Command Line InterfaceCommands” on page 167.)

R/3 Release and System CompatibilityManager for R/3 supports multiple R/3 systems and releases. Thesesystems can be at different R/3 release levels. Manager for R/3 alsosupports multiple R/3 releases for distribution of the SAPGUIsoftware and multiple R/3 ITS server release levels. See theTivoliManager for R/3 Release Notesfor the release levels that aresupported.

User Interface OptionsTivoli software offers a choice of user interface options: Tivolidesktop or Tivoli GEM console. This document, in general, providesprocedures and screen illustrations using the desktop.

Using the DesktopThe Tivoli desktop is a graphical user interface, or GUI. It providesa simple way to work with your resources and monitor theircondition.


1.Introducing

Manager

forR

/3

Using Tivoli GEMTivoli Global Enterprise Manager (Tivoli GEM) provides a GUI thatrepresents managed resources in a business-systems view. Thisalternative view gives administrators a way to view not onlymanaged resources but their relationships with each other. (See“Tivoli GEM Instrumentation” on page 147.)

Integration with Tivoli Database Manager ProductsIf you have the Tivoli Manager for DB2 or the Tivoli Manager forOracle installed, Manager for R/3 can update the status of thedatabase server with the status of the database as reported by theTivoli Manager for DB2 or Tivoli Manager for Oracle.


Planning for and InstallingManager for R/3

This chapter describes the requirements you must meet before youinstall Tivoli Manager for R/3. It describes how to install Managerfor R/3, and it also describes how to uninstall Manager for R/3. IfTivoli GEM is installed, you can optionally install Tivoli GEMinstrumentation. See “Tivoli GEM Instrumentation” on page 147.

Where to Install Manager for R/3Install Manager for R/3 on the following machines:

¶ The Tivoli Management Region (TMR) server

¶ The Tivoli Enterprise Console (TEC) event server that processesManager for R/3 events

¶ Each managed node that runs an R/3 application server, R/3 ITSserver components, R/3 database server, or R/3 SAPGUIinstallation server

¶ All gateways

Installation RequirementsBefore you install the Manager for R/3, you must meet the followingrequirements:

1. Ensure that you are running on a supported operating system andthat you install all prerequisite software. Refer to theTivoli

2


2.P

lanningfor

andInstalling

Manager

forR

/3

Manager for R/3 Release Notesfor details about supportedhardware and operating systems, prerequisite software, and diskspace requirements.

2. Configure the Tivoli Management Regions (TMRs). See“Configuring Tivoli Management Regions”.

3. If you are running R/3 application servers on TMA endpoints,ensure that the TMA endpoints and gateways are properlyconfigured and functional. Refer to theTME 10 FrameworkPlanning and Installation Guide.

4. Ensure that the Application Proxy is installed. For informationabout the required level, refer to theTivoli Manager for R/3Release Notes. For installation instructions, see “Installing theApplication Proxy” on page 11.

5. Configure the TEC event server. See “Planning for TEC EventServer Configuration” on page 13.

6. Optionally, if you manage R/3 resources with Tivoli GEM, see“Tivoli GEM Instrumentation” on page 147 for installationrequirements. Also, ensure that the Tivoli GEM server isconfigured and the Tivoli GEM consoles are installed.

7. Optionally, if you want to extend Manager for R/3 databasestatus reporting, install Tivoli Manager for DB2 or TivoliManager for Oracle. You can install Manager for DB2 orManager for Oracle either before or after you install Manager forR/3. For more information, see “Extending Database ServerStatus Reporting” on page 78.

Configuring Tivoli Management RegionsBefore installing the Manager for R/3, configure the TMR to containthe Tivoli server, the TEC event server, and the R/3 applicationservers and the R/3 database servers for the R/3 system. Because R/3is normally configured with the database server and the applicationservers on the same LAN segment, this partitioning provides a goodmodel for defining a TMR boundary. TMR boundaries are importantbecause of the relationship with TEC event server boundaries; aTMR can have only one TEC event server.


You can manage multiple R/3 systems in a single TMR. These R/3systems can be used for development, test, and production. However,because production systems are so critical to an enterprise’sbusiness, you should consider placing production systems in theirown TMRs.

When multiple R/3 systems are in the same TMR, events from allsystems go to the same TEC event server. Separating productionevents from test and development events is another reason to putproduction systems in their own TMR.

Refer to theTME 10 Framework User’s Guidefor more informationabout configuring TMRs.

If you are planning to use Tivoli gateways to manage TMAendpoints and you are concerned about gateway failure, see“Deciding Where to Create R/3 Objects” on page 54 for additionalplanning information.

Installing the Application ProxyThe Application Proxy is an extension of the Tivoli Framework thatprovides a common set of services that are used by the Manager forR/3. This section describes how to install Application Proxy 1.1 ifyou do not already have it installed. This section also describes howto upgrade to Application Proxy 1.1 if you have Application Proxy1.0 installed, and it describes how to install the required ApplicationProxy patch. The following table lists the context and authorizationroles required to install or upgrade the Application Proxy:

Activity Context Required Roll

Install or upgrade theApplication Proxy

Tivoli desktop install_product

Install the ApplicationProxy patch


Installing Application Proxy Version 1.1To install the Application Proxy for the first time, follow these steps:


2.P

lanningfor

andInstalling

Manager

forR

/3

1. From theDesktop menu, selectInstall –> Install Product todisplay the Install Product dialog.

2. Click Select Mediato display the File Browser dialog. Thisdialog enables you to specify the path to the installation media.

3. Enter the full path to the Application Proxy in the Path Nametext field. The Application Proxy is located in the /APPLPRXYdirectory on the Manager for R/3 CD.

4. Click Set Path. The File Browser dialog displays the contentsof the specified media in the File scrolling list.

5. Click Set Media & Close. The File Browser dialog is closed,and the Install Product dialog is displayed withApplicationProxy, Version 1.1 listed in the Select Product toInstall scrolling list.

6. SelectApplicationProxy, Version 1.1 in the Select Product toInstall scrolling list.

7. Select the target clients on which you do not want to install theApplication Proxy from the Clients to Install On list and clickthe right arrow button to move them to the Available Clientslist.

Note: Install the Application Proxy on the following machines:

¶ TMR server

¶ TEC event server

¶ Each managed node that runs an R/3 applicationserver, R/3 database server, R/3 ITS servercomponents, or R/3 SAPGUI installation server

¶ All gateways

8. Click Install & Close. The Product Install window is displayed,listing the actions that will be taken when you complete theinstallation process.

9. Click Continue Install to perform the Application Proxyinstallation. The dialog displays messages showing the progressof the installation and when the installation is completed.


10. Click Close.

11. Install Application Proxy patch. See “Installing the ApplicationProxy Patch”.

Upgrading to Application Proxy 1.1To upgrade the Application Proxy from Version 1.0 to Version 1.1,install ApplicationProxy, Version 1.1 Upgradeas a patch. Followthese steps:

1. From theDesktop menu on the Tivoli desktop, selectInstall –>Install Patch. The ApplicationProxy, Version 1.1 Upgrade islocated in the /APXYUPGD directory on the Manager for R/3CD.

Note: Install the ApplicationProxy, Version 1.1 Upgrade on eachmachine on which you installed Application Proxy 1.0.

2. Install the required Application Proxy patch. See “Installing theApplication Proxy Patch”.

Installing the Application Proxy PatchTo install the required Application Proxy patch, from theDesktopmenu on the Tivoli desktop, selectInstall –> Install Patch. Thepatch is located in the /APXYPTCH directory on the Manager forR/3 CD. For information about the Application proxy patch that isrequired, refer to theTivoli Manager for R/3 Release Notes.

Notes:

1. Install the Application Proxy patch on each machine on whichyou have installed or upgraded to Application Proxy Version 1.1.

2. If you installed Manager for R/3 before you installed theApplication Proxy patch, you must restart the oserv on eachmachine on which the patch was installed to ensure that thepatch takes effect.

Planning for TEC Event Server ConfigurationFor each configuration, the Manager for R/3 Alert Event Adapter,Syslog Event Adapter, and IDOC Event Adapter send their events tothe configured TEC event server regardless of the TMR in which the


2.P

lanningfor

andInstalling

Manager

forR

/3

TEC event server is located. For the alert event adapter, additionaldrill-down processing is performed. Drill-down processing sendsevents using either Tivoli object calls or the Tivoliwpostemsgcommand, depending on the type of endpoint originating the event.

You can configure TEC event servers in several ways:

¶ One TMR and one TEC event server

In this configuration, the TEC event server is defined in theTMR, and the TEC event server receives all events.

¶ Multiple TMRs and multiple TEC event servers

In this configuration, each TMR is assumed to have its own TECevent server. Each TEC event server receives all events from itslocal TMR. Optionally, you can configure a TEC event server toautomatically forward events to another TEC event server inanother TMR. See “Configuring the TEC Event Server” onpage 82.

¶ Multiple TMRs and one TEC event server

In this configuration, one TEC event server receives events fromall TMRs. Support for this configuration depends on the type ofendpoints sending events to the TEC event server as follows:

v If you want to collect Manager for R/3 events only frommanaged nodes, you need to install the TEC product in everyTMR even though the TEC event server will be active inonly one TMR. Installing the TEC product in every TMRprovides the infrastructure needed by Manager for R/3 tosend events using Tivoli object calls. Resources must beshared between the TMRs.

v If you want to collect Manager for R/3 events only fromTMA endpoints, you need to install the TEC product only inthe TMR hosting the TEC event server. Resources must beshared between the TMRs, and the EventServer class must beregistered in all TMRs not hosting the TEC event server. Thisconfiguration enables Manager for R/3 to send events usingthe wpostemsgcommand from the TMA endpoints.


Note: Collecting Manager for R/3 events to a single TMR from bothmanaged nodes and TMA endpoints is not supported.

Installing Manager for R/3After meeting the requirements described in “InstallationRequirements” on page 9, you can install Manager for R/3. To installManager for R/3, do one of the following:

¶ If you have Manager for R/3 Version 1.5 or Version 1.5.1installed, see “Upgrading to Version 2.1 from Version 1.5 or1.5.1”.

Note: Versions of Manager for R/3 prior to Version 1.5 are notsupported.

¶ If you have Manager for R/3 Version 2.0 installed, see“Upgrading to Version 2.1 from Version 2.0” on page 17.

¶ If you are installing Manager for R/3 for the first time, see“Installing Manager for R/3 Version 2.1” on page 18.

The following table lists the context and authorization role requiredto install or upgrade Manager for R/3:

Activity Context Required Roll

Install or upgradeManager for R/3


Attention: Upgrading Manager for R/3 to Version 2.1 from aprevious release replaces files and, therefore, all local codemodifications that you have made will be lost. Before upgrading toVersion 2.1, make a backup copy of your local changes.

Upgrading to Version 2.1 from Version 1.5 or 1.5.1Because the Manager for R/3 product was restructured after Version1.5.1, you cannot upgrade Manager for R/3 directly from Version 1.5or Version 1.5.1 to Version 2.1. To upgrade to Version 2.1, considerone of the following options:


2.P

lanningfor

andInstalling

Manager

forR

/3

¶ If you want to preserve Version 1.5 or Version 1.5.1configuration data for managed nodes (RFC logon parameters,Alert Event Adapter parameters, and monitor profiles), do thefollowing:

1. Back up the Tivoli database.

2. Install Manager for R/3 Version 2.0 and migrateconfiguration data as described in theTivoli Manager for R/3Release Notesfor Version 2.0. You can obtain a copy of theVersion 2.0 release notes from the Tivoli Customer SupportWeb site (http://www.tivoli.com/support/).

3. Create Tivoli objects for your R/3 systems, R/3 applicationservers, and R/3 database servers as described in Chapter 5of the Tivoli Manager for R/3 User’s Guide, Version 2.0. Youcan obtain a copy of the Version 2.0 user’s guide from theTivoli Customer Support Web site(http://www.tivoli.com/support/).

4. Back up the Tivoli database, saving the backup file with adifferent name than the previous backup file.

5. Upgrade to Version 2.1 as described in “Upgrading toVersion 2.1 from Version 2.0” on page 17.


¶ Do a fresh installation of Version 2.1 as follows:


2. Uninstall Manager for R/3 Version 1.5 or Version 1.5.1 asdescribed in theTivoli Manager for R/3 Release NotesforVersion 1.5.1. You can obtain a copy of the Version 1.5.1release notes from the Tivoli Customer Support Web site(http://www.tivoli.com/support/).

3. Install Version 2.1 as described in “Installing Manager forR/3 Version 2.1” on page 18.



Upgrading to Version 2.1 from Version 2.0To upgrade Manager for R/3 from Version 2.0 to Version 2.1, backup the Tivoli database and then installTivoli Manager for R/3Version 2.1 (Upgrade from Version 2.0)as a patch. Tivoli Managerfor R/3 Version 2.1 (Upgrade from Version 2.0) is located in the/UPGRADE directory on the Manager for R/3 CD.

Notes:

1. Install the upgrade on each machine on which you installedManager for R/3 Version 2.0.

2. If you did not install Manager for R/3 Version 2.0 on allgateways, ensure that you install Manager for R/3 Version 2.1 onall gateways.

3. The Syslog Event Adapter that is installed with the upgradepatch requires the Version 2.1 transports. You can prepare yourR/3 systems prior to installing the upgrade patch by installing thetransports from the /ABAP directory on the Manager for R/3 CD.Install the transports similar to the procedure that is described in“Moving R/3 Transports into an R/3 Landscape” on page 44. Ifyou upgrade to Version 2.1 without first installing the Version 2.1transports, the Syslog event adapters will fail.

4. To receive IDOC events, configure the TEC to add theWR3IDOC event source as described in “Configuring an EventConsole” on page 83.

5. For information about upgrading Tivoli GEM instrumentationfrom Version 2.0 to Version 2.1, see “Upgrading the Tivoli GEMInstrumentation Task Libraries” on page 152.

The upgrade patch completely upgrades Manager for R/3 Version 2.0to Version 2.1, replacing all product files and updating R/3 system,R/3 application server, and R/3 database server objects. The upgradealso preserves the following configuration data:

¶ RFC logon parameters:

v Client

v User


2.P

lanningfor

andInstalling

Manager

forR

/3

v Password

v Language

¶ Alert and Syslog event adapter parameters:

v Host name of the TEC event server

v TEC event server port number

v Polling delay

v Trace logging level

v Error logging level

¶ Subscription lists

¶ Monitor profiles

Notes:

1. The upgrade does not automatically distribute the monitors. Youmust distribute the monitors manually.

2. Because the Alert and Syslog event adapters are replaced, youmust start the Alert and Syslog event adapters that are installedon UNIX. Alert and Syslog event adapters that are installed onWindows NT are automatically started.

Installing Manager for R/3 Version 2.1To install Manager for R/3, follow these steps:


2. From theDesktop menu on the Tivoli desktop, selectInstall –>Install Product to display the Install Product dialog.

3. Click Select Mediato display the File Browser dialog. Thisdialog enables you to specify the path to the installation media.

4. Enter the full path to the Manager for R/3 installation files inthe Path Name text field. The Manager for R/3 files are locatedin the /PRODUCT directory on the Manager for R/3 CD.


5. Click Set Path. The File Browser dialog displays the contentsof the specified media in the Files scrolling list.

6. Click Set Media & Close. The File Browser dialog is closed,and the Install Product dialog is displayed. The Tivoli Managerfor R/3, Version 2.1 product is listed in the Select Product to


2.P

lanningfor

andInstalling

Manager

forR

/3

Install scrolling list.

7. SelectTivoli Manager for R/3, Version 2.1 in the SelectProduct to Install scrolling list.

8. Select the target clients on which you do not want to installManager for R/3 from the Clients to Install On list and click theright arrow button to move them to the Available Clients list.

Note: Manager for R/3 must be installed on the followingmachines:

¶ TMR server

¶ TEC event server

¶ Each managed node that runs an R/3 applicationserver, R/3 database server, R/3 ITS servercomponents, or R/3 SAPGUI installation server

¶ All gateways


9. Click Install & Close. The Product Install dialog is displayed,listing the actions that will be taken when you complete theinstallation process.

10. Click Continue Install to perform the Manager for R/3installation. The Product Install dialog displays messagesshowing the progress of the installation and when theinstallation is completed.

11. Click Close. The desktop now displays the Manager for R3policy region.


Uninstalling Manager for R/3To uninstall Manager for R/3, follow these steps:


2.P

lanningfor

andInstalling

Manager

forR

/3

Note: The create_uninstall_task.shandR3Mgr_uninstall21.plcommands that are used in this procedure are installed withthe Manager for R/3. If you do not find these scripts in the$BINDIR/../generic_unix/TME/SAPUNINST directory, get acopy of these scripts from the /UNINST directory on theManager for R/3 CD.

1. If you are running automatic discovery, remove scheduled jobsfor automatic discovery. Run the following tasks in the R3Configuration Tasks library:

¶ Remove Autodiscovery for NT

¶ Remove Autodiscovery for UNIX

2. Create the Uninstall Manager for R/3 Version 2.1 task. Go to the$BINDIR/../generic_unix/TME/SAPUNINST directory on theTMR server and enter the following command:create_uninstall_task.sh Policy_Region_Name

WherePolicy_Region_Nameis the name of an existing policyregion in which you want to create the R3 Product ManagementTasks library and the Uninstall Manager for R/3 Version 2.1 task.Because the Uninstall Manager for R/3 Version 2.1 taskuninstalls Manager for R/3 policy regions and task libraries, enterthe name of an existing policy region that is not part of theManager for R/3 product.

The create_uninstall_task.shcommand creates the UninstallManager for R/3 Version 2.1 task that you can run on managednodes and TMA endpoints to uninstall Manager for R/3. Thecommand also creates the R3 Product Management Tasks libraryin the policy region you specify and adds the Uninstall Managerfor R/3 Version 2.1 task to this task library.

3. Uninstall Manager for R/3 from the TMR server. Follow thesesteps:

Note: To uninstall Manager for R/3, you must have Tivoliadministrator authority.


a. Run the following command to check for and repair databaseinconsistencies:wchkdb -u

Note any remaining inconsistencies.

b. Go to the$BINDIR/../generic_unix/TME/SAPUNINSTdirectory and enter one of the following commands:

¶ UNIX:R3Mgr_uninstall21.pl

¶ Windows NT:perl R3Mgr_uninstall21.pl

The syntax for theR3Mgr_uninstall21.pl command is:

R3Mgr_uninstall21.pl [–g] [–yes]

–g Uninstalls only Tivoli GEM Instrumentation forTivoli Manager for R/3 Version 2.1.

–yes Uninstalls the product without prompting forconfirmation.

The R3Mgr_uninstall21.pl command stops Manager for R/3event adapters and removes the following items from theTMR server:

¶ Policy regions

¶ Task libraries

¶ Monitoring collections

¶ Objects and object classes (R3System, R3AppServer,R3DBServer, and R3ITSServer)

¶ Profile managers

¶ Profiles

¶ Installed files

¶ Indicator collections


2.P

lanningfor

andInstalling

Manager

forR

/3

¶ TEC sources (WR3MIB, WR3SLOG, and WR3IDOC)

¶ Tivoli GEM instrumentation installed files and tasklibraries

Note: The R3Mgr_uninstall21.pl command does not removethe following items:

¶ Baroc classes

¶ TEC rules

¶ TEC event console filters

¶ ABAP transports

¶ Tivoli GEM instrumentation definition files fromthe Tivoli GEM server

¶ The R3 Product Management Tasks library, whichcontains the Uninstall Manager for R/3 Version 2.1task

¶ The SAPUNINST directory

¶ Scheduled jobs for automatic discovery

If you plan to reinstall Manager for R/3, you do notneed to remove the listed items. If you do not plan toreinstall Manager for R/3 and you want to remove thelisted items, you can manually remove the barocclasses, the TEC rules, the TEC event console filters,the R3 Product Management Tasks library, and theSAPUNINST directory.

To view messages pertaining to the uninstall process, look inthe R3Mgr_uninstall21.log file in one of the followingdirectories:

¶ UNIX: /tmp

¶ Windows NT managed node: %DBDIR%\tmp

¶ Windows NT TMA endpoint: %LCF_DATDIR%


c. Run the following command to check for and repair databaseinconsistencies:wchkdb -u

4. Uninstall Manager for R/3 on the managed nodes and TMAendpoints. Run the Uninstall Manager for R/3 Version 2.1 task inthe R3 Product Management Tasks library against the appropriatemanaged nodes and TMA endpoints. The following tabledescribes the authorization role and target for the uninstall task:

Task Role Target

Uninstall Manager for R/3Version 2.1

install_product Managed node andTMA endpoint

The Uninstall Manager for R/3 Version 2.1 task stops Manager forR/3 event adapters and removes the following items from themanaged nodes and TMA endpoints:

¶ Installed files

¶ Windows NT services for Manager for R/3 event adapters


2.P

lanningfor

andInstalling

Manager

forR

/3


Getting Started with Manager forR/3

This chapter provides an overview of the steps you must complete toconfigure Manager for R/3, and it provides some importantinformation about using Manager for R/3. This chapter alsodescribes the required authorization roles and targets for Manager forR/3 configuration tasks.

What Was InstalledAfter installing Manager for R/3, the Manager for R3 policy regionon the desktop contains the following:

¶ R3 Configuration policy region

¶ R3_Indicators collection

¶ The following profile managers:

v R3 App Server Monitors

v R3 Central Instance Monitors

v R3 DB Server Monitors

v R3 Distributed Daemon Monitors

v R3 ITS Monitors

v R3 Managed Node Monitors

v R3 Transports, if Software Distribution is installed

3


3.G

ettingS

tartedw

ithM

anagerfor

R/3

See “Monitoring R/3 Resources” on page 105 for informationabout the monitor profile managers. See “Moving R/3 Transportsinto an R/3 Landscape” on page 44 for information about the R3Transports profile manager.

¶ The following task libraries:

v R3 App Server Tasks

v R3 DB Server Tasks

v R3 ITS Server Tasks

v R3 System Tasks

For more information about R3 App Server Tasks, R3 DB ServerTasks, R3 ITS Server Tasks, and R3 System Tasks, see “Tasksfor Managing R/3 Resources” on page 127.

Open theManager for R3 policy region icon to display the PolicyRegion: Manager for R3 window:

The R3 Configuration policy region contains the following:


¶ R3 System List profile manager

¶ The following task libraries:v R3 Configuration Tasksv R3 List Maintenance Tasksv R3 Internal Tasks

See “Using Manager for R/3 Configuration Tasks” on page 35.

Open the R3 Configuration policy region to display the PolicyRegion: R3 Configuration window:

Manager for R/3 Object EndpointsR/3 system and server resource types are listed as availableendpoints for tasks and monitors and can be used as subscribers to aprofile manager. As endpoints and subscribers, these resource typesappear in lists where endpoints are displayed and are to be selected.For example, the new endpoint name is displayed in the Available toBecome Subscribers list when looking at the subscribers for a profilemanager. The following table describes the icon, resource type, andendpoint name for each R/3 object:

Endpoint Icon Resource Type Endpoint Name

R/3 system R3System SID_DBhostname

Example:TV4_hound


3.G

ettingS

tartedw

ithM

anagerfor

R/3

Endpoint Icon Resource Type Endpoint Name

R/3 applicationserver

R3AppServer hostname_SID_IID

Example:hound_TV4_55

R/3 databaseserver

R3DBServer hostname_SID_DB

Example:hound_TV4_DB

R/3 Internettransactionserver

R3ITSServer ¶ For a single-host R/3 ITSserver:hostname_VIIN_ITS

Example:

cedar_D02_ITS

¶ For the AGate component ofa dual-host R/3 ITS server:hostname_VIIN_ITS-AGate

Example:elm_TV1_ITS-AGate

¶ For the WGate component ofa dual-host R/3 ITS server:hostname_VIIN_ITS-WGate

Example:pine_D01_ITS-WGate

Where:

DBhostnameIs the host name of the database server.

hostnameIs the host name of the application server, database server, orInternet transaction server (ITS server).

Note: The host name of the ITS server can be the host nameof the machine that is running both the AGate andWGate ITS server components (single-host ITS


server) or the host name of the machine that isrunning the AGate or the WGate component(dual-host ITS server).

SID Is the three-character R/3 system identifier.

IID Is the two-digit R/3 instance number.

VIIN Is the virtual ITS instance name. If the SAP namingrecommendation was followed when the R/3 ITS server wasinstalled, the virtual ITS instance name is theSID of yourR/3 system.

Manager for R/3 tasks and monitors are designed to be distributed toa particular type of endpoint: managed node or TMA endpoint,R3System, R3AppServer, R3DBServer, or R3ITSServer. When youdistribute a monitor or run a task, you must specify the correct typeof endpoint. When you run a task from within the Manager for R3policy region or from the R3 Configuration policy region, theManager for R/3 lists only the appropriate type of endpoint in theAvailable Task Endpoints scrolling list on the Execute Task dialog.

Configuring Manager for R/3To configure the Manager for R/3, complete these steps:

1. Assign the Manager for R/3 authorization roles to one or moreTivoli administrators. See “Assigning Authorization Roles” onpage 33.

2. If you are using the Tivoli Enterprise Console (TEC):

a. Configure the TEC event server as described in“Configuring the TEC Event Server” on page 82.

b. Create one or more event consoles if you have not alreadydone so. Refer to theTME 10 Enterprise Console ReferenceGuide.

3. Configure each SAP R/3 system to be managed as described in“Configuring Each SAP R/3 System” on page 43.


3.G

ettingS

tartedw

ithM

anagerfor

R/3

4. Create the R/3 system and server objects for each R/3 system,R/3 application server, R/3 database server, and R/3 ITS serveryou want to manage as described in “Creating R/3 Objects” onpage 53.

5. Configure the event consoles as described in “Configuring anEvent Console” on page 83.

6. Configure the RFC as described in “Configuring a RemoteFunction Call” on page 71.

7. Perform platform-specific configuration as appropriate. See thefollowing:

¶ “Configuring Manager for R/3 for Windows NT” onpage 72

¶ “Configuring Manager for R/3 for HP-UX 11” on page 75

¶ “Configuring Manager for R/3 for OS/390” on page 76

8. Configure event adapters as described in “Configuring EventAdapters” on page 86.

9. Optionally, configure for extended database status reporting asdescribed in “Extending Database Server Status Reporting” onpage 78. You must have the Tivoli Manager for DB2 or theTivoli Manager for Oracle installed to use this feature.


After creating R/3 system objects, the Manager for R3 policy regioncontains a policy region icon for each R/3 system as shown in the


following figure:

When R/3 application server, R/3 database server, and R/3 ITSserver objects are created for an R/3 system, these objects reside inthe appropriate R/3 system policy region. In addition, the R3Configuration policy region will contain an App Server List profilemanager for each R/3 system.

Assigning Authorization RolesThe Manager for R/3 uses three authorization roles: r3_user,r3_admin, and r3_senior. Each of the Manager for R/3 tasks requireone of the Manager for R/3 authorization roles in addition to thebasic Tivoli authorization roles of user, admin, or senior.

The Manager for R/3 tasks that require senior and r3_adminauthorities include:


3.G

ettingS

tartedw

ithM

anagerfor

R/3

¶ Tasks in the R3 Configuration Tasks library, except for theConfigure Remote Function Call task and the Display EventAdapter Configuration Task

¶ The Create New Subscriber List task in the R3 List MaintenanceTask library

The Configure Remote Function Call task in the R3 ConfigurationTasks library requires senior and r3_senior authorities. The DisplayEvent Adapter task in the R3 Configuration Tasks library requiresuser and r3_user authorities.

The r3_admin and r3_senior authorization roles affect only resourcesin the Manager for R3 and the R3 Configuration policy regions. Youcan assign the r3_admin and r3_senior authorization roles as globalTivoli roles or as resource roles for the Manager for R3 and the R3Configuration policy regions.

The Manager for R/3 tasks that require at least user and r3_userauthorities include:

¶ Tasks in the R3 System Tasks library

¶ Tasks in the R3 App Server Tasks library

¶ Tasks in the R3 DB Server Tasks library

¶ Tasks in the R3 ITS Server Tasks library

The r3_user authorization role affects only resources in the R/3system policy regions. You can assign the r3_user authorization roleas a global Tivoli role or as a resource role for a specific R/3 systempolicy region.

Let’s look at an example for assigning authorization roles. Assumethat you have three administrators:Senior, Prod, andSupport andthree R/3 systems:PRD (a production system),QA1 (a test system),andQA2 (a test system). You might assign Tivoli authorization rolesto each administrator based on responsibilities as described in thefollowing table:


Administrator Responsibilities Manager for R/3Authorization Roles

Senior Manage all R/3 systems Global r3_user, r3_admin, andr3_senior

Prod Manage the production system andbackup to theSupport administrator

¶ Global r3_user

¶ r3_admin resource role forthe PRD policy region

Support Manage all test systems ¶ r3_user resource role forthe QA1 policy region

¶ r3_user resource role forthe QA2 policy region

Using Manager for R/3 Configuration TasksManager for R/3 provides the following task libraries in the R3Configuration policy region that contain tasks to help you configureManager for R/3:

¶ “R3 Configuration Tasks” on page 36

¶ “R3 List Maintenance Tasks” on page 38

Note: Manager for R/3 also contains an R3 Internal Taskslibrary in the R3 Configuration policy subregion. Thetasks in this library support internal processing ofManager for R/3 functions and are not intended to be runby Tivoli administrators.

Jobs are also provided for some tasks in the R3 Configuration Tasksand R3 List Maintenance Tasks libraries. Ajob is a task with theendpoint and other parameters already defined. Jobs provided for thetasks in the R3 Configuration Tasks and R3 List Maintenance Taskslibraries are set up to execute against the TMR server or TEC eventserver, as appropriate.

To locate the configuration tasks, follow these steps:


3.G

ettingS

tartedw

ithM

anagerfor

R/3

1. From the Manager for R3 policy region, open theR3Configuration policy region icon to display the Policy Region:R3 Configuration window.

2. From the R3 Configuration policy region, do one of thefollowing:

¶ Open theR3 Configuration Tasks library to display theconfiguration tasks and jobs.

¶ Open theR3 List Maintenance Taskslibrary to display theCreate New Subscriber List task and job.

R3 Configuration TasksThe R3 Configuration Tasks library contains the following tasks tohelp you configure the Manager for R/3:

Tasks Role Target

Configure Autodiscovery for NT.See “Creating R/3 Objects UsingAutomatic Discovery” on page 55.

r3_admin Windows NTmanaged node orTMA endpoint

Configure Autodiscovery for UNIX.See “Creating R/3 Objects UsingAutomatic Discovery” on page 55.

r3_admin UNIX managednode or TMAendpoint

Configure Client Install. See“Creating SAPGUI Software FilePackages” on page 139.

r3_admin TMR server

Configure Event Adapter. See“Configuring Event Adapters” onpage 86.

r3_admin R3AppServer

Configure Event Console. See“Configuring an Event Console” onpage 83.

r3_admin TEC event server

Configure Event Server. See“Configuring the TEC EventServer” on page 82.

r3_admin TEC event server

Configure Monitor Logging Mode.See “Configuring Monitor LoggingMode” on page 272.

r3_admin TMR server


Tasks Role Target

Configure Remote Function Call.See “Configuring a RemoteFunction Call” on page 71.

r3_senior R3System

Configure SAPGUI Package. See“Creating SAPGUI File Packagesfor Windows SAPGUI Versions4.5B and Later” on page 143.

r3_admin Managed nodethat is the R/3SAPGUIinstallation server

Configure UNIX Client Install. See“Creating SAPGUI Software FilePackages” on page 139.

r3_admin TMR server

Configure Windows 95/98 ClientInstall. See “Creating SAPGUISoftware File Packages” onpage 139.

r3_admin TMR server

Configure Windows NT ClientInstall. See “Creating SAPGUISoftware File Packages” onpage 139.

r3_admin TMR server

Create RDBMS Manager StatusMonitor. See “Extending DatabaseServer Status Reporting” onpage 78.

r3_admin TMR server

Display Event AdapterConfiguration. See “DisplayingEvent Adapter Information” onpage 87.

r3_user R3AppServer

List Available SAPGUI Packages.See “Creating SAPGUI FilePackages for Windows SAPGUIVersions 4.5B and Later” onpage 143.


List SAPGUI Package Features.See “Creating SAPGUI FilePackages for Windows SAPGUIVersions 4.5B and Later” onpage 143.



3.G

ettingS

tartedw

ithM

anagerfor

R/3

Tasks Role Target

Remove Autodiscovery for NT. See“Creating R/3 Objects UsingAutomatic Discovery” on page 55.

r3_admin Windows NTmanaged node orTMA endpoint

Remove Autodiscovery for UNIX.See “Creating R/3 Objects UsingAutomatic Discovery” on page 55.

r3_admin UNIX managednode or TMAendpoint

Send GEM Heartbeat. See“Synchronizing the Tivoli GEMConsole with the Desktop” onpage 154.

r3_admin R3System,R3AppServer,R3DBServer, orR3ITSServer

R3 List Maintenance TasksThe R3 List Maintenance Tasks library contains the following task:

Tasks Role Target

Create New Subscriber List. See“Creating Subscriber Lists” onpage 70.

r3_admin TMR server

Determining R/3 Application Server StatusThe R/3 application server icon reflects the status of the applicationserver as follows:

Icon State Description

An application server icon displayed without a statusindicator in the lower right corner indicates that the R/3application server is up and is accepting R/3 logons.

An application server icon with a yellow trianglecontaining an exclamation mark (!) in the lower rightcorner indicates that the R/3 application server is up but isnot accepting R/3 logons.

An application server icon with a yellow diamondcontaining a question mark (?) in the lower right cornerindicates that the status of the R/3 application server isunknown.



An application icon with a red circle containing a minussign (–) in the lower right corner indicates that the R/3application server is down.

To ensure that an R/3 application server reflects its current status,you must manually distribute the R3 Server Autodiscovery Monitorsprofile, which is contained in the R3 App Server Monitors profilemanager. The R3 Server Autodiscovery Monitors profile contains theApplication Server Status monitor, which reports the status of theapplication server to which the profile is distributed. See “R3 AppServer Monitors Profile Manager” on page 110.

Determining R/3 Database Server StatusThe R/3 database server icon reflects the status of the databaseserver as follows:


A database server icon displayed without a status indicatorin the lower right corner indicates that the R/3 databaseserver is up.

A database server icon with a yellow diamond containinga question mark (?) in the lower right corner indicates thatthe status of the R/3 database server is unknown.

A database server icon with a red circle containing aminus sign (–) in the lower right corner indicates that theR/3 database server is down. Down status is reported onlyif you are using Tivoli Manager for DB2 or TivoliManager for Oracle to extend database status reporting.

Manager for R/3 sets the status of the database server using thefollowing methods:

¶ From the status of the R/3 application servers

When the status of one R/3 application server is up, the status ofthe database server is reported as up. When the status of all R/3


3.G

ettingS

tartedw

ithM

anagerfor

R/3

application servers in the R/3 system is unknown or down, thestatus of the database server is reported as unknown.

¶ Optionally, from the status of the database server as reported bythe Tivoli Manager for DB2 or Tivoli Manager for Oracle

If you have Tivoli Manager for DB2 or Tivoli Manager forOracle installed, you can extend database server status reporting.See “Extending Database Server Status Reporting” on page 78.Manager for R/3 sets the status of the database server based on aTivoli Manager for DB2 or Tivoli Manager for Oracle databaseserver status event. The database server status event can reportup or down status.

Because there are potentially two methods by which Manager forR/3 sets database server status, Manager for R/3 reflects the laststatus that is reported. If you shut down an R/3 system, the R/3application servers shut down first. This results in changing thedatabase server status to unknown even if the R/3 system has notcompletely shut down. When the database server shuts down andthen comes back up, the Tivoli Manager for DB2 or Tivoli Managerfor Oracle database reports down and up status, respectively.

To ensure that an R/3 application server reflects its current status,you must manually distribute the R3 Server Autodiscovery Monitorsprofile to each application server. See “R3 App Server MonitorsProfile Manager” on page 110.

Determining R/3 ITS Server StatusThe R/3 ITS server icon reflects the status of the R/3 ITS server asfollows:


An R/3 ITS server icon displayed without a statusindicator in the lower right corner indicates that the statusof the function represented by the icon is up.



An R/3 ITS server with a yellow diamond containing aquestion mark (?) in the lower right corner indicates thatthe status of the function represented by the icon isunknown.

An R/3 ITS server icon with a red circle containing aminus sign (–) in the lower right corner indicates that thestatus of the function represented by the icon is down.

To ensure that an R/3 ITS server or R/3 ITS server componentreflects its current status, you must configure and distribute the ITSServer Status monitor to each R/3 ITS server object. Use the R3 ITSServer Monitors profile, which is contained in the R3 ITS Monitorsprofile manager to distribute this monitor to each R/3 ITS serverobject. See “R3 ITS Server Monitors” on page 106.


3.G

ettingS

tartedw

ithM

anagerfor

R/3


Configuring Each SAP R/3System

After installing Manager for R/3, configure each SAP R/3 systemthat is to be managed so that Manager for R/3 can communicatewith that system. The following procedures must be performed toenable this communication. These modifications will not adverselyaffect your R/3 installation.

The configuration process requires the following:

¶ “Moving R/3 Transports into an R/3 Landscape” on page 44

¶ “Importing the Function Modules” on page 47

¶ “Configuring User IDs for RFC Interface Access” on page 49

¶ “Configuring R/3 Application Server Profiles” on page 50

Note: Some of the R/3 tasks require that the operating system levelsidadm R/3 logon be used.

4


4.C

onfiguringE

achS

AP

R/3

System

Moving R/3 Transports into an R/3 LandscapeManager for R/3 provides several sets of transports. These transportscontain the following objects:

Transport Objects

Base ¶ Development Class J8C1

¶ Function Group J8C1






¶ Structure J_8C1_ALE1






¶ Structure J_8C1_TIV1



¶ Data Element J_8C1_C180

OS/390 Extension (Thistransport must be installedafter the Base transport.)


Note: Refer to theTivoli Manager for R/3 Release Notesfor specifictransport file names.

You must move the transports to the transport directory in each R/3landscape. To move the transports into an R/3 landscape, use one ofthe following methods:


¶ Distribute the R3 ABAP file package. Software Distribution mustbe installed on the TMR server to use this method.

¶ Copy the transport files from the TMR server to the transportdirectory.

Distributing the R/3 ABAP File PackageTo distribute the R3 ABAP file package to the appropriate R/3application server directories, follow these steps:

1. From the Manager for R3 policy region, open theR3 Transportsprofile manager icon to display the Profile Manager window.

2. If you are distributing the R3 ABAP file package to TMAendpoints, follow these steps to change the R3 Transports profilemanager from database mode to dataless mode:

a. In the Profile Manager window, from theEdit menu, selectProfile Manager to display the Edit Profile Manager dialog.

b. SelectDataless Endpoint Mode.

Note: Refer to theTME 10 Framework User’s Guideformore information about database mode and datalessmode profile managers.

c. Click Change & Close.

3. Subscribe the appropriate managed nodes or TMA endpoints tothe R3 Transports profile manager. In the Profile Managerwindow, from theProfile Manager menu, selectSubscribers todisplay the Subscribers dialog.

4. Complete the Subscribers dialog, referring to the online help ifyou need additional information.

5. For UNIX, go to the next step. For Windows NT, edit the filepackage properties to modify the destination directory path.Follow these steps:

a. Right-click theR3 ABAP FilePackageicon and selectProperties to display the File Package Properties dialog.


4.C

onfiguringE

achS

AP

R/3

System

b. From theEdit menu, selectPlatform-Specific Options –>Windows NT Options to display the File Package WindowsNT Options dialog.

c. Change the destination directory path so that the ABAP filepackage is distributed todriveLetter:/trans/, wheredriveLettermaps to \\SAPGLOBALHOST\sapmnt.SAPGLOBALHOSTrepresents the host name of the central instance.

6. Distribute the transports. From the Profile Manager window,right-click theR3 ABAP FilePackageicon and selectDistributefrom the pop-up menu to display the Distribute File Packagedialog.

7. Complete the Distribute File Package dialog as appropriate,referring to the online help if you need additional information.

Note: The default directory to which the R3 ABAP file packagewill be distributed is as follows:

¶ UNIX: /usr/sap/trans

¶ Windows NT:driveLetter:/trans/.

The distribution process automatically sets the ownership of the filesto the sapsys group.

Copying the TransportsTo copy the transport files from the TMR server to the appropriateR/3 application server directories, follow these steps:

1. Locate the transport files in the cofiles and data subdirectories inthe $BINDIR/../generic_unix/TME/SAP/2.2C/abap directory onthe TMR server.

2. Copy the transport files to the application server that will be usedto execute the import as follows:

¶ Copy all files in the cofiles subdirectory to the/usr/sap/trans/cofiles directory.

¶ Copy all files in the data subdirectory to the/usr/sap/trans/data directory.


Ensure that the files are owned by the sapsys group.

Importing the Function ModulesUse one of the following methods to import the function modules:

¶ “From the Command Line”.

¶ “Using the Transport Management System” on page 48. Thismethod applies to R/3 versions 4.0B and later only.

From the Command LineTo import the function modules from the command line, follow thesesteps:

1. Log on to the R/3 System’s Central Instance as the R/3administrator (sidadm) and change to the /usr/sap/trans/bindirectory.

Note: The transport and correction system must be alreadyconfigured and functioning.

2. Show the current contents of the transport buffer. Enter thefollowing command:tp showbuffer sid

Wheresid is the three-character identifier of your R/3 system.Verify that there are no other transports that need to be imported.

3. Add the transport to the buffer. Enter the following command:tp addtobuffer TV1Kxxxxxx sid

Note: Refer to theTivoli Manager for R/3 Release Notesforspecific transport file names.

4. Verify the transport has been placed in the buffer. Enter thefollowing command:tp showbuffer sid

5. Import the transport. Enter the following command:tp import TV1Kxxxxxx sid [u4]


4.C

onfiguringE

achS

AP

R/3

System

Note: For R/3 releases prior to 4.0A, the u4 option should bespecified. Starting with R/3 release 4.0A, the u4 option isno longer supported by SAP.

6. Verify the import. To do this, log into the R/3 DeveloperWorkBench and check the objects listed in the table in “MovingR/3 Transports into an R/3 Landscape” on page 44. If objects arenot active, activate the objects.

Note: An R/3 developer key is required to activate the objects.

Using the Transport Management SystemFor R/3 versions 4.0B and later, you can use the TransportManagement System (TMS) to transport the function modules. To dothis, follow these steps:

1. From the R/3 SAPGUI, do one of the following to start TMS:

¶ Run transactionSTMS.

¶ From theTools menu, selectAdministration , and then fromthe Transport menu, selectTransport ManagementSystem.

Note: The target system must be properly defined within atransport domain.

2. Show the available R/3 systems. Do one of the following:

¶ Click the Import Overview icon.

¶ From theOverview menu, selectImports .

3. Show the current contents of the transport buffer. Do one of thefollowing:

¶ Double-click the target system.

¶ Select the target system and then from theImport Queuemenu, selectDisplay.

The Import Queue screen is displayed.

4. Add the transport to the buffer. If the buffer already exists, go tothe next step. If the buffer does not exist, do the following:


a. From theExtras menu, selectOther requests –> Add todisplay the Add Transport Request to Import Queue dialog.

b. In the Transp. request field, enter the transport name that youwant to add, such as TV1Kxxxxxx. Then, click the greencheck and clickYes on the confirmation dialog.

Note: Refer to theTivoli Manager for R/3 Release Notesforspecific transport file names.

5. Import the transport as follows:

a. From the Import Queue window, select the transport. Then,from theRequestmenu, selectImport to display the ImportTransport Request dialog.

b. In the Target client field, select the target client from thedrop-down list.

c. Click the green check and clickYes on the confirmationdialog.

6. Verify the import. From theRequestmenu, selectDisplay –>Logs to display the Overview of transport logs window. Ifobjects are not active, activate the objects.

Note: An R/3 developer key is required to activate the objects.

Configuring User IDs for RFC Interface AccessAn R/3 user ID must be used to access the RFC interface. Anexisting user ID can be used, or a new one can be created. It isrecommended that the user ID be a CPIC-only user. The user IDneeds a set of authorizations to run the required function modules inthe R/3 system.

Required authorizations are available in the R/3 authorizationprofiles S_A.ADMIN and S_A.SYSTEM. Either one of theseauthorization profiles can be used for the user ID.


4.C

onfiguringE

achS

AP

R/3

System

If you want to assign a more restrictive set of authorizations to theuser ID, copy either the S_A.ADMIN or the S_A.SYSTEMauthorization profile and remove all authorizations except thefollowing:

¶ S_RZL_ALL

¶ S_BTCH_ALL

¶ S_ADMI_ALL

¶ S_RFC_ALL

If you want to create the most restrictive authorization profiles, referto “Function Module Authorization” on page 223 for information onthe authorizations required by each Manager for R/3 functionmodule.

Note: Starting with R/3 3.1G, R/3 provides enhanced securitycontrol for the RFC interface. RFC security checking isenabled on a per R/3 application server basis. It is set in theinstance profile by specifying auth/rfc_authority_check=1. ForR/3 3.1G through 3.1I, the default is to not enable RFCsecurity. For R/3 4.0A and later, the default is to enable RFCsecurity.

Configuring R/3 Application Server ProfilesThe R/3 application server instance profiles contain manycustomization settings for the R/3 application server. One of theconfiguration options you can set is the allocation of shared memorysegments to shared memory pools. Manager for R/3 requires thatsegment key 13 be assigned to shared memory pool 10. This is thedefault allocation for R/3. This assignment is necessary to supportproper functioning of the Alert Event Adapter and the automaticdiscovery function.

You can check the allocation of segment key 13 by examining theR/3 application server instance profile. The instance profile can bedisplayed and maintained using transaction RZ10. The parameter


ipc/shm_psize_13 controls the pool allocation for segment key 13.This parameter must have a value of -10 to ensure that it is allocatedto shared memory pool 10.


4.C

onfiguringE

achS

AP

R/3

System


Configuring Manager for R/3

This chapter describes how to create Tivoli objects for the R/3systems, application servers, database servers, and Internettransaction servers (ITS servers) that you want to manage withManager for R/3. This chapter also describes how to configure aremote function call (RFC), platform-specific configuration tasks,and how to extend R/3 database server status.

Creating R/3 ObjectsTo manage your R/3 environment with Manager for R/3, you mustconfigure Tivoli for each R/3 system, R/3 application server, R/3database server, and R/3 ITS server component that you want tomanage. To do this, you must create an object for each R/3 systemand server to be managed. You can create R/3 objects in thefollowing ways:

¶ Use the automatic discovery function. See “Creating R/3 ObjectsUsing Automatic Discovery” on page 55.

¶ From the desktop. You must create R/3 ITS server objects andR/3 database server objects, if the R/3 database server is notrunning on the same machine as an R/3 application server, usingthis method. See “Creating an R/3 Object from the Desktop” onpage 60.

Notes:

1. To ensure that an R/3 application server reflects its current status,you must manually distribute the R3 Server Autodiscovery

5


5.C

onfiguringM

anagerfor

R/3

Monitors profile, which is contained in the R3 App ServerMonitors profile manager. The R3 Server AutodiscoveryMonitors profile contains the Application Server Status monitor,which reports the status of the application server to which theprofile is distributed. See “R3 App Server Monitors ProfileManager” on page 110.

2. Because the status of an R/3 database server is based on thestatus of the R/3 application servers, to ensure that an R/3database server reflects its current status, you must manuallydistribute the Application Server Status monitor to the R/3application servers. See “R3 App Server Monitors ProfileManager” on page 110. If you have the Tivoli Manager for DB2or the Tivoli Manager for Oracle installed, you can extend thedatabase status reporting. See “Extending Database Server StatusReporting” on page 78.

3. To ensure that an R/3 ITS server reflects its current status, youmust configure and distribute the ITS Server Status monitor toeach R/3 ITS server that you want to manage. For moreinformation, see “R3 ITS Server Monitors” on page 106.

Deciding Where to Create R/3 ObjectsThis section provides information to help you decide where to createR/3 server objects in a TMA environment.

R/3 system objects are created on the TMR server; they cannot becreated elsewhere. R/3 server objects for R/3 servers that reside onmanaged nodes are created on the corresponding managed nodes;they cannot be created elsewhere. R/3 server objects for R/3 serversthat reside on TMA endpoints, by default, are created on themanaged node that hosts the TMA endpoint’s current gateway.However, you can create the R/3 server objects for TMA endpointson any managed node that you specify.

If you create R/3 server objects for TMA endpoints on the defaultmanaged node, the R/3 server objects might be distributed acrossmultiple managed nodes. If you are concerned about distributed R/3server objects, you can adopt a consolidated approach by creatingthese R/3 server objects on the TMR server or on a high availability


managed node. With this approach, you can take steps to ensure thatthis managed node has the proper backup and recovery plans in caseof failure.

Manager for R/3 objects cannot be moved after the objects arecreated. If the managed node hosting a TMA endpoint’s gatewayfails, you will need to take recovery action. If possible, restore themanaged node from a backup. If you cannot restore the managednode, you must delete the R/3 server objects for the affected TMAendpoints and then recreate the R/3 server objects on anothermanaged node.

Creating R/3 Objects Using Automatic DiscoveryThe automatic discovery function checks for running R/3 applicationservers. For each application server found, the automatic discoveryfunction creates an R3AppServer object and an R3System object, ifthey do not already exist. In addition, the automatic discoveryfunction creates an R3DBServer object if an application server isrunning on the same machine as the database server.

Notes:

1. If the application server is not running on the same machine asthe database server, you can create the R3DBServer objectmanually. See “Creating an R/3 Object from the Desktop” onpage 60 .

2. The automatic discovery function does not find and createobjects for each R/3 ITS server. You must create theR3ITSServer objects manually. See “Creating an R/3 Object fromthe Desktop” on page 60.

This section includes the following topics:

¶ “Configuring Automatic Discovery for Data Sharing” on page 56.Optionally, if you are running R/3 in a data sharing environment,follow these instructions before you schedule automaticdiscovery as described in “Scheduling Automatic Discovery” onpage 57.

¶ “Scheduling Automatic Discovery” on page 57 describes how toschedule automatic discovery for both Windows NT and UNIX.


5.C

onfiguringM

anagerfor

R/3

Configuring Automatic Discovery for Data SharingWhen Manager for R/3 creates the R/3 application server objectswithin an R/3 system policy region, Manager for R/3 assigns thename of the policy region asSID_DBHostname. The values forSIDandDBHostnameare obtained from the R/3 application servers whenthey are discovered. In a data sharing environment, the R/3application servers can report different database host names eventhough the R/3 application servers are in the same R/3 system. Thisis particularly true for OS/390. (For more information, see “DataSharing” on page 77). For a data sharing environment, you canoverride the default processing of the automatic discovery functionto force the R/3 application servers into an R/3 policy region namedwith the database host name of your choice. You do this byspecifying the database host name for each R/3 system in thesap_discovery.cfg configuration file. The automatic discoveryfunction uses the database host names specified in thesap_discovery.cfg configuration file when it creates the R/3 policyregions.

A sample sap_discovery.cfg file is provided in the$BINDIR/../generic_unix/TME/SAP/sh directory on the TMR server.The format of the sap_discovery.cfg file is as follows:SID database_hostname

WhereSID is the three-character R/3 system identifier, anddatabase_hostnameis the host name of the database server thatautomatic discovery uses when it creates the R/3 system.

To configure automatic discovery for data sharing, follow thesesteps:

1. Edit the $BINDIR/../generic_unix/TME/SAP/sh/sap_discovery.cfgfile on the TMR server to specify the appropriate SIDs and thecorresponding database host names. You can specify any or all ofyour SIDs, entering each SID and database host name on aseparate line. The database host name should be no longer thaneight alphanumeric characters. Use one or more spaces toseparate the SID from the database host name. You can also addcomments by placing a pound sign (#) in the first column of a


line. To specify the database host names for R/3 systems TV1and TV4, you would edit the sap_discovery.cfg file as follows:TV1 puli

TV4 hound

2. Distribute the sap_discovery.cfg file to each managed node andTMA endpoint on which you plan to run automatic discovery.You can use the file transfer protocol (FTP) or Tivoli SoftwareDistribution to distribute the file. The sap_discovery.cfg file mustreside in one of the following directories:

¶ Managed node: $BINDIR/../generic_unix/TME/SAP/sh

¶ TMA endpoint:$LCF_BINDIR/../../generic_unix/TME/SAP/sh

Note: The $LCF_BINDIR/../../generic_unix/TME/SAP/shdirectory does not exist prior to running a Managerfor R/3 task on the TMA endpoint. If you plan to useFTP to distribute the sap_discovery.cfg file prior torunning automatic discovery, you must manuallycreate the$LCF_BINDIR/../../generic_unix/TME/SAP/shdirectory. If you plan to use Software Distribution todistribute the sap_discovery.cfg file, you do not needto create this directory. Software Distributionautomatically creates this directory.

Scheduling Automatic DiscoveryTo schedule the automatic discovery function to automaticallydiscover your R/3 systems and servers and create R/3 objects, runone of the following tasks in the R3 Configuration Tasks library:

¶ Configure Autodiscovery for NT

¶ Configure Autodiscovery for UNIX

Each platform-specific Configure Autodiscovery task displays adialog in which you specify the interval at which to run theautomatic discovery function. You can schedule automatic discoveryto run one time immediately, or you can schedule automaticdiscovery to run later. The automatic discovery function runs at the


5.C

onfiguringM

anagerfor

R/3

specified time and populates the desktop with the R/3 objects thatare discovered. The time you specify refers to the time on themachine where the Configure Autodiscovery task is to be run. Also,for servers that are running on TMA endpoints, you can forceautomatic discovery to create the R/3 objects on any managed noderather than on the one hosting the current gateway.

Notes:

1. In the Execute Task dialog, specify only Windows NT managednodes or Windows NT TMA endpoints for the ConfigureAutodiscovery for NT task. Specify only UNIX managed nodesor UNIX TMA endpoints for the Configure Autodiscovery forUNIX task.

2. In the Execute Task dialog, specifySerial in the Execution Modefield and, if you intend to run automatic discovery immediately,specify at least180 in the Timeout field.

3. If you run the Configure Autodiscovery task more than once tochange the scheduling interval, automatic discovery runs at thecurrently scheduled time and previously scheduled times aredeleted.

If your R/3 topology does not change, you might want to stopautomatic discovery after your R/3 resources have been discovered.See “Stopping Automatic Discovery” on page 60.

Scheduling Automatic Discovery for NTTo schedule automatic discovery for Windows NT, run the ConfigureAutodiscovery for NT task. The Configure Autodiscovery for NT


dialog is displayed:

To run automatic discovery one time immediately (automaticdiscovery will run within two minutes), leave all dialog fields empty.To schedule automatic discovery to run once at a specific time, entera value in the Minute and Hour fields only. For more informationabout completing the dialog, refer to the online help.

Scheduling Automatic Discovery for UNIXTo schedule automatic discovery for UNIX, run the ConfigureAutodiscovery for UNIX task. The Configure Autodiscovery forUNIX dialog is displayed:


5.C

onfiguringM

anagerfor

R/3

To run automatic discovery one time immediately, leave all dialogfields empty. To schedule automatic discovery to run every day at aspecific time, enter a value in the Minute and Hour fields only. Formore information about completing the dialog, refer to the onlinehelp.

Stopping Automatic DiscoveryTo stop automatic discovery, run one of the following tasks in theR3 Configuration Tasks library:

¶ Remove Autodiscovery for NT

¶ Remove Autodiscovery for UNIX

Run the task against the same endpoints on which you ran theConfigure Autodiscovery task.

Creating an R/3 Object from the DesktopThis section describes how to create an R/3 system object, an R/3application server object, an R/3 database server object, and an R/3ITS server object from the desktop. For servers that are running onTMA endpoints, Manager for R/3 creates the R/3 object on themanaged node hosting the current gateway. However, you can forcethe creation of the R/3 server object to be on any managed node byspecifying the name of the managed node when you create the R/3server object. You must create the R/3 system object before you cancreate a server object.

Creating an R/3 System Object from the DesktopTo create an R/3 system object from the desktop, from theCreatemenu from the Manager for R/3 Policy Region window, select


R3Systemto display the Create R/3 System dialog.

For information about completing the dialog, refer to the online help.

This task creates a subregion for the R/3 system in the Manager forR3 policy region. The subregion icon is namedSID_DBHostname,whereSID is the value specified in the R/3 System Name (SID)field, andDBHostnameis the host name specified in the R/3Database Hostname field.

Note: If your R/3 system resides on an OS/390 database host usingdata sharing, see “Data Sharing” on page 77 for moreinformation about R/3 system policy region namingconsiderations.

Creating an Application Server Object from the DesktopTo create an R/3 application server object from the desktop, followthese steps:

1. From the Manager for R3 Policy Region window, open theappropriate R/3 system policy region to display the PolicyRegion window for the selected R/3 system.


5.C

onfiguringM

anagerfor

R/3

2. From theCreate menu, selectR3AppServer to display theCreate R/3 Application Server dialog.


This task creates an icon for the application server in the appropriateR/3 system policy region.

Creating a Database Server Object from the DesktopTo create an R/3 database server object from the desktop, followthese steps:


2. From theCreate menu, selectR3DBServer to display the CreateR/3 Database Server dialog.



This task creates an icon for the database server in the appropriateR/3 system policy region.

Creating an ITS Server Object from the DesktopTo create an R/3 ITS server object from the desktop, follow thesesteps.


2. From theCreate menu, selectR3ITSServer to display theCreate R/3 ITS Server dialog.

You can create an R/3 ITS server that represents any of thefollowing:

¶ A single-host R/3 ITS server (both the AGate and the WGatecomponents run on the same machine)

¶ An individual component (AGate or WGate) of a dual-host R/3ITS server (the AGate and the WGate components run ondifferent machines)


This task creates an icon for the R/3 ITS server in the appropriateR/3 system policy region.


5.C

onfiguringM

anagerfor

R/3

Results of Creating R/3 ObjectsThis section describes the results of creating an R/3 system, an R/3application server, an R/3 database server, and an R/3 ITS serverobject.

Result of Creating an R/3 System ObjectWhen you create an R/3 system object, the following occurs:

¶ An icon for the R/3 system policy region is created in theManager for R3 policy region.

v The icon represents an R3System resource type that can beused as the target when running tasks. See “Manager for R/3Object Endpoints” on page 29.

v The icon has a pop-up menu that enables you to performcommon tasks. If you execute a task from the pop-up menuon the R/3 system icon, the task executes on that R/3 system.The following table describes the tasks that are availablefrom the pop-up menu:

Task Description

Open Opens the R/3 policy region. This is thedefault action.

Properties Displays the properties of this R/3 system,including the SID, R/3 release, databasehost name, database type and databaserelease.

Start R/3 System

Stop R/3 System

See “R3 System Tasks” on page 131.

¶ The R/3 system is subscribed to the R3 System List profilemanager.

¶ An App Server List profile manager is created in the R3Configuration policy region.

¶ The App Server List profile manager is subscribed to the R3App Server Monitors profile manager.


¶ If Tivoli GEM instrumentation is installed, the object is added tothe Tivoli GEM server database and an icon is created on theTivoli GEM console. See “Tivoli GEM Instrumentation” onpage 147.

Result of Creating an R/3 Application Server ObjectWhen you create an R/3 application server object, the followingoccurs:

¶ An icon for the R/3 application server is created in theappropriate R/3 system policy subregion.

v The icon represents an R3AppServer resource type that canbe used as the target when running tasks and monitors. See“Manager for R/3 Object Endpoints” on page 29.

v The icon has a pop-up menu that enables you to performcommon tasks. If you execute a task from the pop-up menuon the R/3 application server icon, the task executes on thatR/3 application server. The following table describes the tasksthat are available from the pop-up menu:

Task Description

Open Displays the profiles that have beendistributed to this R/3 application server.

Properties Displays the properties of the R/3application server including host name, theinstance ID, the R/3 system name, and thestate of the R/3 application server. This isthe default action.

Start SAPGUI Runs the SAPGUI from the R/3 applicationserver to your desktop. On Windows NT,you must run this task from the samemachine on which the R/3 applicationserver is running.


5.C

onfiguringM

anagerfor

R/3

Task Description

Start Application Server

Stop Application Server

Start Alert Event Adapter

Stop Alert Event Adapter

Start Syslog Event Adapter

Stop Syslog Event Adapter

Start IDOC Event Adapter

Stop IDOC Event Adapter

See “R3 App Server Tasks” on page 132.

¶ The R3AppServer object is subscribed to the App Server Listprofile manager for the appropriate R/3 system.


Result of Creating an R/3 Database Server ObjectWhen you create an R/3 database server object, the followingoccurs:

¶ An icon for the database server is created in the appropriate R/3system policy subregion.

v The icon represents an R3DBServer resource type that can beused as the target when running tasks. See “Manager for R/3Object Endpoints” on page 29.

v The icon has a pop-up menu that enables you to performcommon tasks. If you execute a task from the pop-up menuon the R/3 database server icon, the task executes on that R/3database server. The following table describes the tasks thatare available from the pop-up menu:


Task Description

Open Displays the profiles that have beendistributed to this R/3 database server.

Properties Displays the properties of the databaseserver including host name, database type,release, R/3 system, Manager for DB2 orManager for Oracle object name, and state.This is the default action.

Start R/3 Database Server

Stop R/3 Database Server

See “R3 DB Server Tasks” on page 136.


Result of Creating an R/3 ITS Server ObjectWhen you create an R/3 ITS server object, the following occurs:

¶ An icon for the R/3 ITS server is created in the appropriate R/3system policy subregion.

v The icon represents an R3ITSServer resource type that can beused as a subscriber for profile managers. See “Manager forR/3 Object Endpoints” on page 29.

v The icon has a pop-up menu that enables you to performcommon tasks. If you execute a task from the pop-up menuon the R/3 ITS server icon, the task executes on that R/3 ITSserver. The following table describes the tasks that areavailable from the pop-up menu:

Task Description

Open Displays the profiles that have beendistributed to this R/3 ITS server.

Properties Displays the properties of the R/3 ITSserver including the ITS server name, hostname, R/3 system name, and status. This isthe default action.


5.C

onfiguringM

anagerfor

R/3

Task Description

Start ITS Server

Stop ITS Server

See “R3 ITS Server Tasks” on page 137.

¶ The R3ITSServer object is subscribed to the R3 ITS Monitorsprofile manager.


Deleting an R/3 ObjectDeleting an R/3 system, an R/3 application server, an R/3 databaseserver, and an R/3 ITS server object does not affect the R/3 systemor the server but removes the information about it that is stored inthe Tivoli database. Before you can delete an R/3 system object, youmust delete all server objects in that R/3 system policy region. Todelete an R/3 object, follow these steps:

1. Stop all Application Server Status and ITS Server Statusmonitors in the appropriate R/3 system policy region.

Attention: Deleting R/3 objects while status monitors arerunning against objects in an R/3 system can potentially corruptthe Tivoli database. For more information about this problem,refer to information about deleting R/3 objects in the″KnownProduct Defects, Limitations, and Workarounds″ section of theTivoli Manager for R/3 Release Notes.

2. Go to the policy region that contains the object you want todelete and select the appropriate R/3 system, R/3 applicationserver, R/3 database server, or R/3 ITS server icon.

3. From theEdit menu, selectDelete to remove the selected objectfrom the policy region.

4. Restart Application Server Status and ITS Server Status monitorsas appropriate.


Result of Deleting an R/3 System ObjectWhen you delete an R/3 system object, the following occurs:

¶ The icon for the R/3 system is removed from the desktop.

¶ The R3System object is unsubscribed from all profile managers.

¶ The App Server List profile manager is removed.

¶ If Tivoli GEM instrumentation is installed, the object is deletedfrom the Tivoli GEM server database, and the icon is removedfrom the Tivoli GEM console.

Result of Deleting an R/3 Application Server ObjectWhen you delete an R/3 application server object, the followingoccurs:

¶ The icon for the R/3 application server is removed from thedesktop.

¶ The R3AppServer object is unsubscribed from all profilemanagers.

¶ Manager for R/3 event adapters are stopped, Windows NTservices are removed, and the files associated with the eventadapters are removed.

¶ If Tivoli GEM instrumentation for Manager for R/3 is installed,the object is deleted from the Tivoli GEM server database, andthe icon is removed from the Tivoli GEM console.

Result of Deleting an R/3 Database Server ObjectWhen you delete an R/3 database server object, the followingoccurs:

¶ The icon for the R/3 database server is removed from thedesktop.

¶ The R3DBServer object is unsubscribed from all profilemanagers.



5.C

onfiguringM

anagerfor

R/3

Result of Deleting an R/3 ITS Server ObjectWhen you delete an R/3 ITS server object, the following occurs:

¶ The icon for the R/3 ITS server is removed from the desktop.

¶ The R3ITSServer object is unsubscribed from all profilemanagers.


Creating Subscriber ListsManager for R/3 automatically creates the following lists in the R3Configuration policy subregion:

¶ R3 System List, to which all R/3 system objects that have beendefined to Manager for R/3 are subscribed.

¶ An application server list for each R/3 system labeledSID_DBhostnameApp Server List, to which all applicationserver objects for the specified R/3 system that have beendefined to Manager for R/3 are subscribed.

These lists are subscriber-only profile managers and are updatedautomatically as resources are defined to Manager for R/3, whetherby discovery or when you manually create R/3 system and R/3application server objects. You can use these lists as target endpointswhen you run tasks and monitors. All application server lists areautomatically subscribed to the R3 App Server Monitors profilemanager. See “R3 App Server Monitors Profile Manager” onpage 110.

You can also create your own subscriber lists. For example, youmight want to create a list of all application servers across all R/3systems in your environment. To create a new subscriber list, run theCreate New Subscriber List job in the R3 List Maintenance Taskslibrary. (See “Using Manager for R/3 Configuration Tasks” onpage 35.) The Create New Subscriber List dialog is displayed inwhich you enter the name of the new subscriber list.


Configuring a Remote Function CallManager for R/3 must connect to each managed R/3 system usingthe R/3 remote function call (RFC) to run certain tasks and monitors.The user ID that is used for this access was defined when the R/3administrator configured the R/3 system. (See “Configuring User IDsfor RFC Interface Access” on page 49). To use the RFC interface fora particular R/3 system, you must configure the RFC for that systemin Tivoli. The Syslog Event Adapter and the IDOC Event Adapteruse this configuration information.

If you reconfigure an RFC, you must do the following:

¶ Rerun theConfigure Event Adapter task for the appropriateSyslog Event Adapter or IDOC Event Adapter and then stop andstart the event adapter to update the RFC configurationinformation. See “Configuring Event Adapters” on page 86.

¶ Redistribute the monitoring profiles to all R/3 application serversin the affected R/3 systems.

To configure an R/3 RFC for each R/3 system, run theConfigureRemote Function Call task in the R3 Configuration Tasks library.(See “Using Manager for R/3 Configuration Tasks” on page 35.) Thistask displays the Configure Remote Function Call dialog.

For information about completing this dialog, refer to the onlinehelp.


5.C

onfiguringM

anagerfor

R/3

Configuring Manager for R/3 for Windows NTThis section describes how to configure Manager for R/3 if you arerunning R/3 in a Windows NT environment.

Creating Exit Routines for Windows NTThe start and stop database tasks for Windows NT rely ondatabase-specific commands to fully implement their processing.Manager for R/3 does not provide these commands. Instead,Manager for R/3 provides database start and stop tasks that calluser-supplied exit routines to start and stop the database.

For start processing, you must create an exit routine calledsap_start_db_exit.sh. The start exit routine must issue anappropriate command to start the database. For stop processing, youmust create an exit routine calledsap_stop_db_exit.sh. The stop exitroutine must issue an appropriate command to stop the database.One copy of the exit routines is used for all R/3 database servers onthe node. Both exit routines are expected to be in one of thefollowing directories:

¶ Managed node: $BINDIR/../generic_unix/TME/SAP

¶ TMA endpoint: $LCF_BINDIR/../../generic_unix/TME/SAP

The Manager for R/3 database start and stop tasks pass twopositional parameters to the exit routines: database type and the R/3SID. Both parameters are character format. The routines should exitby writing a numeric return code to standard output. A return codeof zero indicates successful completion. A non-zero return codeindicates unsuccessful completion.

Example of a Start Exit Routine for an Oracle DatabaseThe following is an example of a start exit routine for an Oracledatabase:#!/bin/shecho 'Starting Service'E:/orant/Bin/oradim80.exe -STARTUP -SID $2 -STARTTYPE srvcecho 'Sleeping'sleep 10


echo 'Starting Instance'E:/orant/Bin/oradim80 -STARTUP -SID $2 -STARTTYPE inst -USRPWD \-PFILE E:\\orant\\Database\\init"$2".oraexit 0

Example of a Stop Exit Routine for an Oracle DatabaseThe following is an example of a stop exit routine for an Oracledatabase:#!/bin/shecho 'Stopping Instance'E:/orant/Bin/oradim80.exe -SHUTDOWN -SID $2 -USRPWD -SHUTTYPE \inst -SHUTMODE n &echo 'Sleeping'sleep 10echo 'Stopping Service'E:/orant/Bin/oradim80.exe -SHUTDOWN -SID $2 -SHUTTYPE srvcexit 0

Enabling the Local Administrator for SAP File AccessManager for R/3 tasks that start and stop R/3 servers rely onSAP-provided programs in the SAP-provided directories. Access tothese directories is controlled by membership in theSAP_<sid>_LocalAdmin group.

Manager for R/3 tasks are run as Administrator in a Windows NTenvironment. In a Windows NT domain, Administrator maps to eachWindows NT local Administrator. To enable the Manager for R/3tasks to run with the correct permissions, you must configure thelocal Administrator on each Windows NT application server to be amember of the SAP_<sid>_LocalAdmin group.

Enabling Automatic Discovery for Windows NTFor automatic discovery to work on Windows NT managed nodes,you must ensure that the SYSTEM user ID is added to the list oflogins for the root Tivoli Administrator. This is because theautomatic discovery function relies on the Windows NTat commandto provide scheduling, and scheduled commands are run under theSYSTEM user ID. Refer to the appropriate Windows NTdocumentation for more information about theat command.


5.C

onfiguringM

anagerfor

R/3

Enabling the Tivoli Authentication Package forWindows NT

If you are running R/3 on Windows NT, you might have configuredyour R/3 installation to share file systems of the Central Instancewith servers for Dialog instances. If your installation is configured inthis way, then Tivoli must be configured for remote file accessprivileges for some of the Manager for R/3 tasks to gain access tothe R/3 executables, in particular, for starting and stopping R/3servers.

Remote file access is configured into Tivoli through the TivoliAuthentication Package. The configuration is set during installationof the managed node or the TMA endpoint. To set remote file accessafter installation of the managed node or TMA endpoint, use thewsettap andwlcftap commands, respectively. Use one of thefollowing commands to configure the Tivoli Authentication Packagefor use by the Administrator user after installation:

¶ Managed node:

v wsettap -a -r Administrator

v wsettap -a -r domain_name\Administrator

v wsettap -a -r domain_name\sidadm, wheresid is thethree-character R/3 system identifier.

¶ TMA endpoint:

v wlcftap -a -r Administrator

v wlcftap -a -r domain_name\Administrator

v wlcftap -a -r domain_name\sidadm, wheresid is thethree-character R/3 system identifier.

For more information about the Tivoli Authentication Package, referto theTME 10 Framework Planning and Installation Guide. Formore information about thewsettap andwlcftap commands, refer tothe TME 10 Framework Reference Manual.


Setting the Environment Variable for Windows NTTo use the Manager for R/3 start and stop SAPGUI tasks, you mustset an environment variable in the Windows NT system environment.The following environment variable enables Manager for R/3 tolocate the needed R/3 files:

TIV_SAPGUI_DIRSpecifies the full path to the directory in which the SAP R/3sapgui.exe file exists, as shown in this example:TIV_SAPGUI_DIR=F:\PC\NT\SAPGUI

Configuring Manager for R/3 for HP-UX 11Manager for R/3 supports R/3 running with HP-UX 11enhancements. These enhancements include 64-bit support andshared memory windows.

HP-UX 11 64-bit SupportManager for R/3 supports R/3 systems running on HP-UX 11 in64-bit mode. Manager for R/3 automatically detects if an R/3 systemis running on a 64-bit mode system and automatically invokes thecorrect 32-bit or 64-bit programs as needed.

HP-UX 11 Shared Memory WindowsShared memory windows on HP-UX 11 is superseded by 64-bitmode. However, if you are using shared memory windows, Managerfor R/3 requires the following:

¶ The /etc/services.window file must contain entries that specifythe application server name and the memory window in whichthe application server is to start. For example, the/etc/services.window file should contain entries similar to thefollowing:peach_DO1_10 101peach_DO1_20 102

¶ The /usr/bin/setmemwindowand the/usr/bin/getmemwindowexecutables must exist on the HP-UX 11 machine.

Note: When an R/3 application server is moved from one sharedmemory environment to another, it is possible that R/3 shared


5.C

onfiguringM

anagerfor

R/3

memory resources are not properly removed. One problemthat results when this occurs is that the R/3 application serverdoes not report syslog messages. To correct this problem,manually clean up the R/3 shared memory resources. To dothis, follow these steps as described by SAP:

1. Stop the R/3 application server and enter the followingcommand at the operating system command line:ipcs -am

2. Check the output for any remaining shared memorysegments. You should find a memory segment thatbelongs to the usersidadm and is approximately 4 KB insize. Note the ID of this memory segment.

3. Remove the memory segment owned bysidadm. Enter thefollowing command:ipcrm -m ID

ReplaceID with the ID of the shared memory segment.

4. Restart the R/3 application server.

When these requirements are met, the Manager for R/3 eventadapters and monitors will work. For the Manager for R/3 start andstop R/3 system tasks to work, it is assumed that the SAP-providedstart and stop scripts in thesidadm home directory have beenmodified to use the memory windowingsetmemwindowandgetmemwindowcommands.

Configuring Manager for R/3 for OS/390This section describes considerations for using Manager for R/3 ifyou are running R/3 in an OS/390 environment.

R/3 Release SupportSAP provides OS/390 support only with R/3 releases 3.1G and later.You can run OS/390 as your database server, using OS/390 DB2 asthe database. Manager for R/3-supported application server operatingsystems with an OS/390 database server are AIX and Windows NT.


R/3 TransportsManager for R/3 delivers transports for R/3. The base set providesall function modules needed to run the standard Manager for R/3functions. An additional transport is provided for OS/390 that mustbe installed in your R/3 systems. The OS/390 transport provides thefunction modules to obtain OS/390 operating system information andOS/390 DB2 information. This transport is installed in the samemanner as the base transport. For more information about thetransports, see “Moving R/3 Transports into an R/3 Landscape” onpage 44.

During installation of the OS/390 transport, R/3 sets up default RFCdestinations. R/3 automatically assigns the RFC destinations, andthese destinations must be preserved for the Manager for R/3function modules to obtain OS/390 information.

The function modules delivered in the OS/390 transport rely on theR/3 saposcoland rfcoscol programs being installed on the OS/390operating system. SAP delivers thesaposcoland rfcoscol programsas part of the R/3 product, and SAP provides information aboutinstalling these programs. For installation information, refer to theSAP Online Service System.

R/3 Database Objects with OS/390Manager for R/3 does not provide direct support for managingresources on an OS/390 system and does not support theconfiguration of OS/390 database server objects. Therefore, Managerfor R/3 will not automatically discover your R/3 database server, andyou cannot create the R/3 database server object manually from thedesktop. Also, Manager for R/3 does not support starting andstopping OS/390 database servers.

Data SharingOS/390 systems that use data sharing have a single database systemthat is accessed by multiple database machines. Because the R/3application servers for the R/3 system are connected to differentdatabase machines, the R/3 application servers report differentdatabase host names even though the R/3 application servers are inthe same R/3 system.


5.C

onfiguringM

anagerfor

R/3

In a data sharing environment, Manager for R/3 attempts to createmultiple R/3 policy regions for the same R/3 system becauseManager for R/3 creates R/3 system policy regions using thedatabase host name as a qualifier. If you are using automaticdiscovery to create your R/3 objects, you must configure automaticdiscovery as described in “Configuring Automatic Discovery forData Sharing” on page 56 so that Manager for R/3 uses a commondatabase host name value. Configuring automatic discovery to use acommon database host name prevents the creation of multiple R/3policy regions. If you are creating your R/3 objects entirely from thedesktop, you can select any database host name when you create theR/3 system object.

Monitoring the OS/390 SystemManager for R/3 provides Distributed Monitoring sources forobtaining OS/390 and OS/390 DB2 information. See “Using OSCollect and OS/390 Monitors” on page 123 for more information.

Extending Database Server Status ReportingIf you have Tivoli Manager for DB2 or Tivoli Manager for Oracleinstalled, you can extend Manager for R/3 database status reporting.This means that you can update the status of the database serverwith the status of the database as reported by the Manager for DB2or Manager for Oracle.

To enable extended database server status reporting, follow thesesteps:

1. Distribute a DB2 Instance Status or RDBMS State monitor. Todo this, follow these steps:

a. Add a properly configured database server status monitor to aDistributed Monitoring profile. Run theCreate RDBMSManager Status Monitor job in the R3 Configuration Taskslibrary. This job displays the Create RDBMS Manager Status


Monitor dialog.

For information about completing this dialog, in particular,the user ID and group ID fields, refer to the online help.

b. Ensure that the subscriber list for the profile manager hasbeen updated with the appropriate Manager for DB2 instanceobjects or Manager for Oracle instance objects.

c. Distribute the profile to the subscribers.

Both database status monitors are configured to run every 15minutes and to generate a TEC event that Manager for R/3processes to update database server status. A TEC event isgenerated for each of the following response levels:

¶ Critical is set when the monitor returnsBecomesunavailable.


5.C

onfiguringM

anagerfor

R/3

¶ Warning is set when the monitor returnsBecomesavailable.

2. Configure the TEC event server to add the database statusintegration rules. To do this, clone the rule base that contains theManager for DB2 or Manager for Oracle database status eventclass (DB2_status or OracleInstance_rdbmsstate, respectively).For information about how to configure the TEC event server,see “Configuring the TEC Event Server” on page 82. Forinformation about the database status integration rules, see“Database Status Integration Rules” on page 204.

Note: If you installed Manager for DB2 or Manager for Oracleafter you configured the TEC event server, you mustreconfigure the TEC event server to install the databasestatus integration rules.

To determine if extended database server status reporting isconfigured for an R/3 system, selectProperties from the appropriateR3DBServer icon’s pop-up menu. If the Properties dialog shows theManager for DB2 or Manager for Oracle object name, then aconnection has been established and extended database server statusreporting is active.

Note: The association between the Manager for DB2 or Manager forOracle database server object and the Manager for R/3database server object depends on both Manager for DB2 orManager for Oracle and Manager for R/3 reporting the samevalue for the R/3 SID. Manager for R/3 sets the R/3 SIDwhen you create the R/3 system object (see “Creating R/3Objects” on page 53).


Managing R/3 Events

Manager for R/3 supplies new event classes and rule sets to enableyou to view and work with R/3 events at your Tivoli EnterpriseConsole (TEC). You can extend these classes and rule sets to providefurther enhancement, automation, and intelligent processing.

To work with R/3 events at your TEC console, you must configurethe event console, the TEC event server, and the event adapters asdescribed in the following steps:

1. Configure the TEC event server to recognize R/3 events andprocess rules concerning those events. Run the Configure EventServer task against the TEC event server to be configured.

2. Create one or more event consoles if you have not already doneso. Refer to theTME 10 Enterprise Console Reference Guide.

3. Configure the event consoles. Run the Configure Event Consoletask to assign newly created event groups to the appropriateevent consoles.

4. Configure event adapters as follows:

¶ Configure the Alert Event Adapter and the Syslog EventAdapter for each application server to process R/3information and generate the appropriate TEC events.

¶ Configure the IDOC Event Adapter for one R/3 applicationserver in each R/3 system to process intermediate document(IDOC) errors and generate the appropriate TEC events.

6


6.M

anagingR

/3E

vents

This chapter describes how to perform the event handling tasks, andit describes the following information that you should understand touse the event adapters:

¶ “Using the Alert Event Adapter” on page 88

¶ “Using the Syslog Event Adapter” on page 91

¶ “Using the IDOC Event Adapter” on page 96

¶ “Filtering Events” on page 104

The following table describes the authorization role and targetendpoint for the event handling tasks:

Tasks Role Target

Configure Event Adapter r3_admin R3AppServer

Configure Event Console r3_admin TEC event server

Configure Event Server r3_admin TEC event server

Display Event AdapterConfiguration

r3_user R3AppServer

Start Event Adapter r3_user R3AppServer

Stop Event Adapter r3_user R3AppServer

Configuring the TEC Event ServerThe Configure Event Server task configures a TEC event server forManager for R/3 by importing new classes and rules, installing newevent sources, compiling the new rule base, and then stopping andrestarting the TEC event server.

When integrating with Tivoli Manager for DB2 or Tivoli Managerfor Oracle to update R/3 database server status (see “ExtendingDatabase Server Status Reporting” on page 78), it is necessary toinclude additional database integration rules. Similarly, when usingTivoli GEM instrumentation (see “Tivoli GEM Instrumentation” onpage 147), it is necessary to include additional Tivoli GEMinstrumentation event classes and rules in the TEC rule base.Running the Configure Event Server task after installing the Tivoli


Manager for DB2, the Tivoli Manager for Oracle, or Tivoli GEMinstrumentation task libraries automatically performs these additionalrule base updates.

To configure a TEC event server, run theConfigure Event Serverjob in the R3 Configuration Tasks library. (See “Using Manager forR/3 Configuration Tasks” on page 35.) This job displays theConfigure Event Server dialog.


Configuring an Event ConsoleThe Configure Event Console job adds filters to the event consoleand assigns the group and event sources. To configure an eventconsole, run theConfigure Event Consolejob in the R3Configuration Tasks library. (See “Using Manager for R/3Configuration Tasks” on page 35.) This job displays the Configure


6.M

anagingR

/3E

vents

Event Console dialog.


When you open the TEC from the desktop, the Enterprise ConsoleEvent Groups dialog and the Enterprise Console Source Groupsdialog are displayed.


To view all events that have passed the group filter criteria, open theevent group. To view all events from all Manager for R/3 SyslogEvent Adapters, all Alert Event Adapters, or all IDOC EventAdapters, open the WR3SLOG event source, WR3MIB event source,and WR3IDOC event source, respectively. Here is an example of theevent log:


6.M

anagingR

/3E

vents

Configuring Event AdaptersTo configure either the Syslog Event Adapter, the Alert EventAdapter, or the IDOC Event Adapter, run theConfigure EventAdapter task in the R3 Configuration Tasks library. (See “UsingManager for R/3 Configuration Tasks” on page 35.) This task createsan event adapter.

Notes:

1. If you reconfigure an event adapter, stop and start the appropriateevent adapter to incorporate the changes.

2. Because IDOCs are system-wide resources, configure an IDOCEvent Adapter on only one R/3 application server in each R/3system. Configuring an IDOC Event Adapter on more than oneR/3 application server in an R/3 system generates duplicateevents for each IDOC.


The Configure Event Adapter task displays the Configure EventAdapter dialog.


Displaying Event Adapter InformationTo display the event adapter information, run theDisplay EventAdapter Configuration task in the R3 Configuration Tasks library.(See “Using Manager for R/3 Configuration Tasks” on page 35.) Thistask displays the Display Event Adapter Configuration dialog.

To display the current configuration of an event adapter, select eitherAlert Adapter, Syslog Adapter, or IDOC Adapter.

Starting and Stopping an Event AdapterManager for R/3 provides the following tasks in the R3 App ServerTasks library to start and stop an event adapter:


6.M

anagingR

/3E

vents

Start Event AdapterStarts the specified event adapter.

Stop Event AdapterStops the specified event adapter.

Using the Alert Event AdapterThe Alert Event Adapter reports R/3 alerts by querying the R/3SysMan interface for new entries and forwarding formatted events tothe TEC. R/3 systems use alerts to report an occurrence of asituation that might require operator attention. Alerts can begenerated in the following ways:

¶ Automatically based on predetermined criteria

¶ In response to the Basis Administrator setting threshold valuesagainst monitored measurements

You can view the alerts that have occurred in an R/3 system throughR/3 CCMS using transaction RZ03 or RZ20, depending on your R/3release level.

Understanding How the Alert Event Adapter WorksTo understand how the Alert Event Adapter works, you need tounderstand how R/3 alerts are processed and how this processingdiffers among R/3 releases.

Alert Processing in R/3 Releases 3.0F, 3.1x, and 4.0xIn R/3 releases 3.0F, 3.1x, and 4.0x, alerts are set and viewed in oneway: using transaction RZ06 and transaction RZ03, respectively.About 40 different alerts can be set and viewed, and each alertrepresents a single occurrence of a problem. There is no historicalrecord. The alert might have some information updated in CCMS,but once the alert is posted, it is not reposted. This level of alertreporting is referred to as″3.x alerts″.

To facilitate reporting of alerts to external systems, SAP provides anSNMP type of interface, called the SysMan interface. Because theSysMan interface is based on SNMP, the SysMan interface reports


traps. R/3 reports a trap at a level higher than the individual alerts.Traps are reported for the following summary levels of alerts:

¶ Operating System

¶ Enqueue

¶ Syslog

¶ Performance

¶ Buffers

¶ ABAP errors

¶ Roll/Page

¶ Trace Switch

¶ Other Alerts

¶ Dispatch Queue

¶ Database

Note: The SysMan interface does not allow posting of an operatingsystem trap by itself.

Because the Alert Event Adapter uses the SysMan interface, thealerts that are visible to Manager for R/3 are the 40 alerts reportedas 3.x alerts. Also, because SNMP traps are high level, more detailedinformation needs to be obtained to generate meaningful TECevents. Manager for R/3 provides TEC rules that initiate drill-downprocessing to obtain more detailed information. The detailedinformation is conveyed in a new TEC event. Both the originalevents and the drill-down events can be seen in the TEC receptionlog. When Manager for R/3 performs drill-down processing,Manager for R/3 TEC rules immediately close the original events.The resulting set of TEC events is listed in “R/3 Operational EventClasses” on page 182.

The Alert Event Adapter is dependent on the R/3 design regardingwhen traps are posted. Like alerts, traps are posted only once, andthey remain at that state until an alert severity changes or until thealert is closed. This means that alerts can occur in an R/3 system


6.M

anagingR

/3E

vents

without causing a new SysMan trap to be generated. For example,the Buffers category includes alerts for nine different buffers. If onebuffer, such as CUA, gets a yellow alert, a trap is posted to theSysMan interface. If another buffer gets a yellow alert, both alertscan be seen in CCMS, but another SysMan trap is not generated forthe second yellow buffer alert because a yellow buffer trap is alreadyoutstanding.

Alert Processing in R/3 Release 4.5In R/3 release 4.5, SAP introduced a new design for handling alerts:Monitoring Architecture. Monitoring Architecture is supportedthrough transaction RZ20. Alerts are presented hierarchically. Thereare many more alert categories than in R/3 releases 3.0F, 3.1x, and4.0x (3.x alerts), and there can be an alert history. This level of alertsis referred to as″Alert monitor 4.0″ (4.x alerts). Both 3.x and 4.xalert interfaces are available in CCMS. However, there is no implicitrelationship between these two interfaces. These two interfaces areparallel alert interfaces, and thresholds and alerts in 3.x are unrelatedto thresholds and alerts in 4.x. The CUA buffer, for example, can bealerted in one interface but not in the other interface. The 3.xinterface continues to drive the SysMan interface as in R/3 releases3.0F, 3.1x, and 4.0x, and the Alert Event Adapter reports the 3.xalerts but not the 4.x alerts. Bidirectional closing between TECevents and R/3 alerts is well synchronized just as in R/3 releases3.0F, 3.1x, and 4.0x.

Alert Processing in R/3 Release 4.6In R/3 release 4.6, SAP removed the 3.x alert interface whileretaining the SysMan interface. The 4.x alert interface of theMonitoring Architecture drives the SysMan interface. Using the 4.xalert interface has the following implications for the Alert EventAdapter:

¶ Not all 4.x alerts are posted as traps to the SysMan interface.Only 4.x alerts that correspond to 3.x alerts are posted.

¶ Posting of SysMan traps is dependent on MonitoringArchitecture internal timing. This means that classes of traps areposted at different intervals than might be observed in earlierR/3 releases.


¶ Closing of alerts must occur in the 4.x interface. Manager forR/3 bidirectional communication does not close 4.x alerts whenclosing an event from the TEC. This means that if you close anevent in TEC, the trap is closed in R/3, but the same 4.x alert (ifstill open) causes the SysMan interface to regenerate the sameTEC event.

¶ Because Monitoring Architecture has a history of alerts, closingthe newest 4.x alert simply makes the next most recent alert inthat class the new active open alert. If the corresponding trap isnot already posted, it is posted with this next most recent alert.This reposting of old alerts occurs until all open alerts in thatclass are closed.

¶ A SysMan trap that indicates″no problems″ only occurs whenall alerts, including the history, are closed in the 4.x interface.

Controlling Alert EventsThe Alert Event Adapter can generate many events. See “EventClasses and Rules” on page 179 for a listing of these events. Tominimize the number of events that are sent to the TEC, you canfilter these events at the Alert Event Adapter. To filter events, addfilter statements to the r3mibIID .conf file, whereIID represents thetwo-digit R/3 instance number. See “Filtering Events” on page 104.

The r3mibIID .conf file is created after you run the Configure EventAdapter task and, therefore, exists only after you have run this taskat least once for the specific R/3 application server. Ther3mibIID .conf file is located in one of the following directories:

¶ Managed node: $BINDIR/TME/SAP/2.2C

¶ TMA endpoint: $LCF_BINDIR/../TME/SAP/2.2C

Using the Syslog Event AdapterThe Syslog Event Adapter processes the R/3 syslog and convertsnew entries into TEC events. Because the Syslog Event Adapterobtains syslog messages through the R/3 RFC interface, the SyslogEvent Adapter must log on to the R/3 system. The Syslog Event


6.M

anagingR

/3E

vents

Adapter uses the same R/3 user ID information that was specifiedwhen you configured an RFC. See “Configuring a Remote FunctionCall” on page 71.

The Manager for R/3 provides two configuration files for the SyslogEvent Adapter: r3slogIID .cl and r3slogIID .conf, whereIID representsthe two-digit R/3 instance number. These configuration files arecreated after you run the Configure Event Adapter task and,therefore, exist only after you have run this task at least once for thespecific R/3 application server. The r3slogIID .cl and ther3slogIID .conf configuration files are located in one of the followingdirectories:



The configuration files are used as follows:

r3slogIID .clDefines the syslog events that are sent to the TEC. Eventsthat are not defined in this file cause the Syslog EventAdapter to send events with event classSAP_SYSLOG_MSG.

Modify the entries in the r3slogIID .cl file to customize thesyslog events to be sent to the TEC or add new entries tothis file to send additional syslog events to the TEC. See“Modifying Entries in the r3slogIID.cl File” on page 93 and“Adding New Entries to the r3slogIID.cl File” on page 94.

r3slogIID .confContains TEC event filter statements. By default, all syslogevents that are not specified in the r3slogIID .cl file are classSAP_SYSLOG_MSG and are filtered out. Only those eventsthat are specified in the r3slogIID .cl configuration file aresent to the TEC. If you want to see all syslog events,comment out the Filter statement in the r3slogIID .conf file.See “Filtering Events” on page 104.

The following table describes the syslog events that are defined inthe r3slogIID .cl file and are sent to the TEC by default. You can use


the Syslog Event Adapter as shipped, or you can customize whichsyslog events are sent to TEC. See “Controlling Syslog Events”.

Event Class Severity Syslog Message

SAP_SYSLOG_A08 50 (critical) Main memory destroyed.

SAP_SYSLOG_BY1 30 (warning) DB error &5.

SAP_SYSLOG_BY2 30 (warning) Database &6 for &3.

SAP_SYSLOG_BZ7 30 (warning) Storage request (&5&5 bytes) is toosmall for the record (&5&5 bytes).

SAP_SYSLOG_EAS 30 (warning) Failed to reschedule a periodic job.

SAP_SYSLOG_F7Y 40 (minor) Spool: Database is inconsistent.

SAP_SYSLOG_GEG 50 (critical) Lock table overflow.

SAP_SYSLOG_GI0 40 (minor) Error calling the central lockhandler.

SAP_SYSLOG_R0R 30 (warning) The connection was deactivated after aDB error.

SAP_SYSLOG_R20 40 (minor) Insufficient shared memory.

SAP_SYSLOG_R45 50 (critical) Shared memory destroyed.

SAP_SYSLOG_US4 30 (warning) Maximum number of users reached.

Controlling Syslog EventsYou can control the syslog events you want sent to the TEC in thefollowing ways:

¶ “Modifying Entries in the r3slogIID.cl File”.

¶ “Adding New Entries to the r3slogIID.cl File” on page 94.

¶ “Filtering Events” on page 104.

Modifying Entries in the r3slogIID.cl FileTo control the syslog events that are sent to the TEC, modify theentries in the r3slogIID .cl file. Entries for many syslog events aredefined in the r3slogIID .cl file for your convenience. Most of theentries are commented. Commented lines are preceded by asemicolon (;). To send additional syslog events to the TEC,


6.M

anagingR

/3E

vents

uncomment the appropriate event entries. Similarly, if you do notwant to send one of the default events to the TEC, do one of thefollowing:

¶ Precede the appropriate event entry with a semicolon (;).

¶ Add filter criteria to the r3slogIID.conf file. See “FilteringEvents” on page 104.

Adding New Entries to the r3slogIID.cl FileIf you want to define additional syslog events to send to the TEC,add new syslog event entries to the r3slogIID.cl file in the followingformat:MessageID [Severity [Classname]]

Where:

MessageIDIs the three-character ID that identifies the syslog message.The syslog message ID must be specified in uppercaseletters.

SeveritySpecifies the event severity. While this parameter is optional,it must be specified if an event class is specified. This value,if specified, must be one of the following:

Value Corresponding Severity Level

10 unknown

20 harmless

30 warning

40 minor

50 critical

60 fatal

If no value is specified, the default is30 (warning).

ClassnameSpecifies the event class. This parameter is optional. If youdo not specify an event class, the default class is


SAP_SYSLOG_msgID, wheremsgID is the three-charactermessage ID. The SAP_SYSLOG_msgIDevent class conveysinformation about specific syslog messages. This event classis designed as a leaf class of the SAP_SYSLOG event class,which contains all the event slot definitions.

If you specify an event class, you must create a .baroc fileand define the event class similar to the event classdefinitions in the tecad_wr3slog.baroc file in the$BINDIR/../generic_unix/TME/SAP/baroc directory. If youneed to create specific Syslog event classes by message ID,you should create event classes of the formSAP_SYSLOG_msgID. These event classes should be leafclasses of SAP_SYSLOG.

Example of Controlling Syslog EventsThe following table provides examples of how you might controlsyslog events:

To get this event... Set these controls...

SAP_SYSLOG_msgID In the r3slogIID .cl file, SAP_SYSLOG_msgID is definedand uncommented.

In the r3slogIID .conf file, add one of the following:

¶ FilterMode=IN with the following Filter statement:

Filter:Class=SAP_SYSLOG_msgID

¶ FilterMode=OUT with any Filter statements except thefollowing:

Filter:Class=SAP_SYSLOG_msgID


6.M

anagingR

/3E

vents

To get this event... Set these controls...

SAP_SYSLOG_MSG forsyslog message,msgID,wheremsgID is thethree-character syslogmessage ID.

In the r3slogIID .cl file, SAP_SYSLOG_msgID iscommented or not defined.

In the r3slogIID .conf file, add one of the following:

¶ FilterMode=IN with one of the following Filterstatements:

Filter:Class=SAP_SYSLOG_MSG;r3SyslogMsgNumber=msgID

The above Filter statement sends aSAP_SYSLOG_MSG class event only for syslogmessage,msgID.

Or —

Filter:Class=SAP_SYSLOG_MSG

The above Filter statement sends aSAP_SYSLOG_MSG class event for syslog message,msgID, and all other default syslog messages.

¶ FilterMode=OUT with any Filter statements except:Filter:Class=SAP_SYSLOG_MSG

Note: Any settings other than the settings listed in this table will result in no events forsyslog message,msgID.

Using the IDOC Event AdapterThe IDOC Event Adapter enables you to monitor the transfer ofbusiness data using SAP Intermediate Documents (IDOCs). IDOCsare created in one R/3 system and are sent to one or more R/3systems using Application Link Enabling (ALE) as the underlyingcommunication facility, which often uses the R/3 RFC. Byproactively managing the transfer of IDOCs, you can avoid theimpact that can occur to business applications when business data,such as accounting codes and plant locations, is not synchronizedacross R/3 systems.


The IDOC Event Adapter monitors the R/3 system for changes inIDOC status and converts IDOC status changes to TEC events. TheIDOC Event Adapter sends the following events to the TEC:

¶ A SAP_IDOC_STATUS event for each IDOC that is in a newerror state since last reported.

¶ A harmless SAP_IDOC_STATUS event for each IDOC that wasin a warning or error state when last reported and is now in anon-error state. This harmless event facilitates automatic closingof events in the TEC. A harmless SAP_IDOC_STATUS event isalso sent for each IDOC when the IDOC expires.

¶ A SAP_IDOC_XMIT event for each RFC destination to whichIDOCs failed transmission because of a transactional RFCcommunication problem. A SAP_IDOC_XMIT event isgenerated when an IDOC with a status code of 03 hastransmission problems.

Note: Status code 03 is a normal status that indicates that theIDOC was queued for transmission. ASAP_IDOC_STATUS event is not generated for thisIDOC.

Understanding How the IDOC Event Adapter WorksThe IDOC Event Adapter reports changes in IDOC status from onepolling cycle to the next. IDOC status is identified by status codes,which are divided between outbound and inbound IDOCs. OutboundIDOCs (status codes 00 through 50) are those IDOCs sent by thespecific R/3 system. Inbound IDOCs (status codes 51 through 74)are those IDOCs received by the specific R/3 system. For moreinformation about IDOC status codes, see “IDOC Status Codes” onpage 219.

Upon startup, the IDOC Event Adapter analyzes all IDOCs andestablishes a baseline from which to report subsequent errors. TheIDOC Event Adapter does not generate any TEC events during thefirst polling cycle, and it does not generate events for IDOCs thathave a non-error status from one polling cycle to the next.


6.M

anagingR

/3E

vents

Because the IDOC Event Adapter obtains IDOCs through the R/3RFC interface, the IDOC Event Adapter must log on to the R/3system. The IDOC Event Adapter uses the same R/3 user IDinformation that you specified when you configured an RFC. See“Configuring a Remote Function Call” on page 71.

Viewing and Interpreting IDOC EventsWhen you receive IDOC events, you will see TEC events(SAP_IDOC_STATUS and SAP_IDOC_XMIT events) as illustratedin the following TEC event log:

Manager for R/3 reports the most current information about eachIDOC by using TEC rules that close duplicate SAP_IDOC_STATUSevents. A duplicate SAP_IDOC_STATUS event is identified by threeevents slots:

¶ sub_source (the R/3 system label)

¶ r3client (the three-digit R/3 client number)

¶ r3idocNum (the 16-digit R/3 IDOC number)

For more information, see “IDOC Event Slots” on page 195.


This means that when a duplicate SAP_IDOC_STATUS event isreceived from the same R/3 system for the same R/3 client andIDOC number, the first event is closed regardless of whether theIDOC status code changed or remained the same.

Interpreting SAP_IDOC_STATUS EventsThe message area on the TEC can help you determine whichSAP_IDOC_STATUS events are important. The message areacontains the IDOC status code, the message type, partner system,and the IDOC message. After determining which events areimportant based on the IDOC status code, the message type can giveyou guidance about which application area is having the IDOCproblem. Message types are defined in R/3. Depending on yourorganization’s policies, you might need to act on an IDOC errorbased on the code and type, or you might need to provide thisinformation to someone else.

Many times, responding to an IDOC error requires that you orsomeone else log on to the R/3 system to take corrective action. Youcan use additional event slot values to determine which R/3 systemto log on to and which IDOC to investigate. To determine the R/3system, open the SAP_IDOC_STATUS event and look at thesub_source event slot, which contains the R/3 SID. To determine theIDOC that you need to investigate within this R/3 system, look atthe r3client and r3idocNum event slots. These event slots uniquelyidentify the IDOC. Depending upon the type of IDOC error, the msgevent slot might contain additional information that can help youcorrect the problem.

Interpreting SAP_IDOC_XMIT EventsThe message area on the TEC provides information to help youdetermine the cause of the transmission problem associated with aSAP_IDOC_XMIT event. The message area shows the partnersystem to which the IDOC is sent, and it shows the number ofIDOCs that have failed transmission in the last polling interval tothis partner system. When you open a SAP_IDOC_XMIT event, youcan find out additional information about the number of IDOCs thathave been sent and the number of IDOCs that have failedtransmission in the last polling interval and in the last 24 hours.


6.M

anagingR

/3E

vents

Controlling IDOC EventsYou can control the IDOC events to be sent to the TEC bymodifying the r3idocIID .conf file, whereIID represents the two-digitR/3 instance number. The r3idocIID .conf file is created after you runthe Configure Event Adapter task and, therefore, exists only afteryou have run this task at least once for the specific R/3 applicationserver. The r3idocIID .conf file is located in one of the followingdirectories:



You can customize the r3idocIID .conf file in the following ways:

¶ Add filter statements to minimize the number of events that aresent to the TEC by filtering the events at the IDOC EventAdapter. For more information, see “Filtering Events” onpage 104.

¶ Modify the entries that control the following:

v Number of days after which IDOCs with unchanged statusexpire (ABH_ExpirationDays). The default is 7 days.

v Inbound status codes that are interpreted as error codes(ABH_InboundErrorCodes). Valid values are 51 through 74.The default inbound status codes are: 51, 52, 54, 56, 60, 61,63, and 65.

v Outbound status codes that are interpreted as error codes(ABH_OutboundErrorCodes). Valid values are 00 through 50.The default outbound status codes are: 02, 04, 05, 07, 09, 11,15, 17, 20, 23, 25, 26, 27, 29, 34, 36, 37, and 40.

The following entries in the r3idocIID .conf file show the defaultvalues that the IDOC Event Adapter uses:

ABH_ExpirationDays=7ABH_InboundErrorCodes=51,52,54,56,60,61,63,65ABH_OutboundErrorCodes=02,04,05,07,09,11,15,17,20,23,25,26,27,29,34,36,37,40


Notes:

1. Error codes must be specified in a comma-separated listwithout intervening spaces.

2. Both inbound and outbound error codes must be specified. Ifboth inbound and outbound error codes are not specified orif the values specified are not valid or are not specified usingthe correct syntax, the IDOC Event Adapter uses the defaultvalues.

3. If you customize the r3idocIID .conf file, stop and start theappropriate IDOC Event Adapter to incorporate the changes.

Performance ConsiderationsBecause the performance of the IDOC Event Adapter is affected bymany variables, it is not possible to provide precise guidelines forconfiguring your R/3 system, the IDOC Event Adapter, and yourTEC event server. This section provides information to help youevaluate your environment so that you can determine a configurationthat meets your needs. The factors that affect the performance of theIDOC Event Adapter include the following:

¶ Number of IDOCs in your R/3 system

¶ Number of IDOCs in error state

¶ Number of IDOC events generated

¶ IDOC Event Adapter polling interval

¶ IDOC status codes designated as error codes

IDOCs pass through a series of steps as they are being processed inthe R/3 system. The R/3 system is able to resolve some IDOC errorsautomatically. For other IDOC errors, intervention is required. TheIDOC Event Adapter does not find IDOC errors that areautomatically resolved between IDOC Event Adapter pollingintervals and, hence, does not generate TEC events. Thus, bothability of the R/3 system to automatically resolve IDOC errors andthe IDOC Event Adapter polling interval affect the number and typeof IDOC events that you see on your TEC console.


6.M

anagingR

/3E

vents

To set the optimum polling interval for the IDOC Event Adapter,you need to evaluate your R/3 system IDOC load, the expectednumber of IDOCs in error state at any time, the frequency at whichyou want notifications, and the load on your TEC event server.Consider the following situations:

¶ If your R/3 system automatically resolves many IDOC errorsituations, a low (one to two minutes) polling interval mightcause you to get many TEC events for which you do not need totake action. In this case, setting the polling interval to a higherrate (5 to 15 minutes) can cause a higher percentage of IDOCevents sent to TEC to be of the type that require yourintervention.

¶ If you are concerned about seeing IDOC errors as soon as theyoccur, you might want to set a low polling interval (three to fiveminutes).

¶ If you need to be aware of IDOC errors on a less urgent basis,you can set a higher polling interval (30 minutes). Because theIDOC Event Adapter sends TEC events for pertinent IDOCs ateach polling interval, if you have many IDOCs in your R/3system, a higher polling interval can result in many IDOC events(several hundred or more) to be sent to your TEC event server atthe same time.

If you find that you have an excessive number of IDOC events andyou are not interested in receiving IDOC events for specific statuscodes, you can customize the IDOC status codes that the IDOCEvent Adapter considers as IDOC errors. For information about howto do this, see “Controlling IDOC Events” on page 100. By reducingthe number of status codes that the IDOC Event Adapter considersas IDOC errors, you can directly affect the number of IDOC eventsthat are sent to the TEC event server.

The IDOC Event Adapter relies on an R/3 ABAP program to locateIDOC errors in your R/3 system. To work correctly, this programmust read all the IDOCs in your R/3 system. If your R/3 systemcontains a very large number of IDOCs (hundreds of thousands ormillions), then the processing time for this ABAP program will be


extended. You can decrease this processing time by implementing anIDOC archiving strategy for your R/3 systems. Using an archivingstrategy enables you to keep the number of IDOCs in your R/3system at a manageable level.

The Tivoli test lab configured the IDOC Event Adapter to poll atfive-minute intervals and to report the default set of IDOC errorevents. The R/3 system contained 104,000 IDOCs, 2000 of whichwere in an error state. The Tivoli test lab calculated the performanceof the IDOC Event Adapter as follows:

¶ The ABAP program processed the R/3 IDOCs and located IDOCerrors in seven seconds.

¶ The IDOC Event Adapter processed 2,000 IDOC errors and sentevents to the TEC in ten seconds.

¶ The TEC event server processed the 2,000 IDOC events in 94seconds.

The Tivoli test lab calculated the performance of the IDOC EventAdapter with the following hardware and software:

¶ R/3 application server

v Netfinity

– Two 400 MHz processors

– 512 MB RAM

– One 4.5 GB IDE disk

– Five 9.1 GB SCSI disks

– Windows NT 4.0

The R/3 application server was dedicated to R/3 processing. Thismachine had no other significant load.

¶ TEC event server

v IntelliStation

– One 333 MHz processor


6.M

anagingR

/3E

vents

– 256 MB RAM

– One 6.2 GB IDE disk

– Windows NT 4.0

– TEC 3.6.1 using the default rule base

– Oracle 7.xx as the RIM RDBMS

The event load for the TEC event server was limited to theevents from the IDOC Event Adapter.

Filtering EventsYou might not want certain types of R/3 events to appear on yourTEC consoles because you regard them as harmless or unlikely torequire action. The TEC provides the following ways for you tofilter out events that you do not want to view:

¶ You can specify that the event is not to be forwarded to the TECevent server. In this case, you specify filter criteria in one ormore of the following configuration files:

Event Adapter Configuration File

Alert r3mibIID .conf

Syslog r3slogIID .conf

IDOC r3idocIID .conf

Here is an example of a Filter statement:FilterMode=OUTFilter:Class=SAP_ALERT_Trace;r3configDBName=TV5

Refer to theTME 10 Enterprise Console Adapter’s Guideformore information.

¶ You can create new rules to exclude the event. In this case, theevent is forwarded to the TEC event server, but it is eliminatedby the rules engine. Refer to theTME 10 Enterprise ConsoleRule Builder’s Guidefor more information.


Monitoring R/3 Resources

This chapter describes the monitoring collections that Manager forR/3 provides to help you manage R/3 resources. This chapter alsoexplains how to use and customize Manager for R/3 monitors.

Like any Distributed Monitoring monitor, these R/3-specific monitorsshould be customized to meet the needs of your R/3 installation. Forexample, you might want to add monitors to the default set andspecify the severity or threshold of the monitors. For additionalinformation, refer to theTME 10 Distributed Monitoring User’sGuide.

Manager for R/3 monitors are specifically designed to work withobject types provided with the Manager for R/3 product just asDistributed Monitoring monitors are designed to work with thestandard Framework endpoints: managed nodes and TMA endpoints.Distribution of one product’s monitors to another product’s endpointsis not supported. This means that you cannot distribute Manager forR/3 monitors to managed nodes and TMA endpoints, and you cannotdistribute Distributed Monitoring monitors to Manager for R/3 objectendpoints. For example, you should distribute the application serverstatus monitor to an R3AppServer object and not to a managed nodeor TMA endpoint.

7


7.M

onitoringR

/3R

esources

Monitoring CollectionsManager for R/3 provides the following monitoring collections forthe R/3 environment:

¶ R3 ITS Server Monitors

¶ R3 Server Remote Monitors

¶ R3 Server Central Monitors

¶ R3 UNIX File System Monitors

¶ R3 Windows NT File System Monitors

Monitoring SourcesEach monitoring collection contains a set of monitoring sources.Monitoring sources provide a logical grouping of the monitors tofacilitate your monitor selection. Many of the monitoring sourcesprovided for the server remote monitors and the server centralmonitors collections are common to both collections.

AttributesA monitor must be defined to report one specific value. Many of themonitoring sources enable you to select the monitoring value to bereported by selecting an attribute. For example, the roll area sourcehas attributes for roll area free space, roll area size, and roll areacurrently used.

For each monitor defined, Distributed Monitoring provides graphicaluser interface tools to individually configure specific values for themonitor, such as the frequency at which the monitor should be run,one or more threshold levels, and actions to be taken at eachthreshold.

R3 ITS Server MonitorsThe R3 ITS Server Monitors provide the ability to monitor the statusof your R/3 ITS servers. The R3 ITS Server Monitors monitoringcollection contains one monitoring source: ITS Server Status. Youcan use the R3 ITS Server Monitors profile contained in the R3 ITSMonitors profile manager to distribute this monitor. See “R3 ITSMonitors Profile Manager” on page 111.


R3 Server Remote and R3 Server Central MonitorsThe R3 Server monitors provide the ability to monitor aspects ofyour R/3 application servers and R/3 database servers. Manager forR/3 provides the R3 Server Remote and R3 Server Centralmonitoring collections, that reflect different monitoringimplementations, for this purpose. Both monitoring collectionscontain a set of monitoring sources to support a wide range ofmonitor options.

Remote monitors and central monitors differ primarily in where themonitors run, not in what they monitor. Remote monitors are run ona target endpoint and monitor an application server on that endpoint.Central monitors run on the TMR server but monitor an R/3application server on another endpoint. For central monitors to work,the monitoring implementation must provide remote communicationcapabilities rather than relying on Distributed Monitoringcommunication channels. Manager for R/3 is able to provide centralmonitors using R/3 remote function calls (RFCs).

All of the server remote monitors run against an R3AppServerendpoint. This means that when you build a monitoring profile thatincludes server remote monitors, you must distribute that profile toan R3AppServer endpoint. The monitors will not run if they aredistributed to any other endpoints.

The server central monitors are distributed to the TMR server andcommunicate with an R/3 application server using an R/3 remotefunction call (RFC). You specify the R3AppServer endpoint as anattribute when you add the monitor. Manager for R/3 provides a listof valid R3AppServer objects from which to select when setting theattribute.

The following table lists the monitoring sources, their correspondingmonitoring collection, and a reference to the attributes that pertain tothat source.


7.M

onitoringR

/3R

esources

Source

R3 ServerRemote

Collection

R3 ServerCentral

CollectionAttributeReference

Roll AreaX X

See “Roll Area” onpage 209

Page AreaX X

See “Page Area” onpage 210

Work ProcessX

See “Work ProcessSource” on page 211

Work ProcessDispatch Queue

X

See “Work ProcessDispatch QueueSource” onpage 212

Long Running WorkProcess

X

See “Long RunningWork ProcessSource” onpage 212

CUA Menu and TextBuffer

X XSee “Buffer” onpage 213

PRES Screen andDynpro Buffer


TTAB TableDescription Buffer


FTAB Field CatalogBuffer


SNTAB ShortNameTab Buffer


IRBD Initial RecordsBuffer


TABL Generic KeyBuffer


TABLP Single KeyBuffer


PXA Program BufferX X

See “Buffer” onpage 213

OS Collect -Application Server

X XSee “OS Collect” onpage 208


Source

R3 ServerRemote

Collection

R3 ServerCentral

CollectionAttributeReference

Application ServerStatus

XNo attributes

Dialog PerformanceX

See “Performance”on page 214

Update PerformanceX


Batch PerformanceX


Spool PerformanceX


OS Collect -Database Server

XSee “OS Collect” onpage 208

OS/390X

See “OS/390” onpage 217

OS/390 DB2X

See “OS/390 DB2”on page 215

Cancelled Job X No attributes

Heap Memory X X See “Heap MemorySource” onpage 214

Extended Memory X X See “ExtendedMemory Source” onpage 214

User X X See “User Source”on page 215

R3 UNIX and R3 Windows NT File System MonitorsThe R3 UNIX and Windows NT file system monitors provide theability to monitor R/3 file systems on your R/3 application servers.These monitors are organized according to the underlying operatingsystem. For more information, see “Using the File System Monitors”on page 116.


7.M

onitoringR

/3R

esources

Default Profile ManagersTo facilitate immediate monitoring capabilities, Manager for R/3provides a set of profile managers. These profile managers areavailable for application servers, database servers, ITS servers, andmanaged nodes.

R3 App Server Monitors Profile ManagerThe R3 App Server Monitors profile manager contains the followingapplication server profiles:

R3 Server Remote MonitorsContains monitors for buffer quality for each of the differentbuffers, maximum percent used for roll and page areas, R/3response time for different user processes, percent used andmaximum percent used for extended memory, and status forthe saposcol daemon.

R3 Server Autodiscovery MonitorsContains the application server status monitor. This monitorreturns the status of an R/3 application server. Distribute thisprofile to each R/3 application server to ensure that each R/3application server reflects its current status.

R3 Server Central MonitorsEnables you to use monitors from the R3 Server CentralMonitors collection. This profile is empty, and the only validsubscriber is the TMR server. Monitoring of remotemachines is performed from the TMR by distributing theprofile to this subscriber.

R3 DB Server Monitors Profile ManagerThe R3 DB Server Monitors profile manager contains the R3 DBServer Central Monitors profile. This profile enables you to usemonitors from the R3 Server Central monitoring collection, inparticular, the monitors for OS/390 and for the database server. Thisprofile is empty, and the only valid subscriber is the TMR server.Monitoring of the remote machines is performed from the TMR bydistributing the profile to this subscriber.


R3 Distributed Daemon Monitors Profile ManagerThe R3 Distributed Daemon Monitors profile manager containsprofiles that define monitors that report the status of critical R/3processes. Subscribe the appropriate managed nodes and TMAendpoints to this profile manager. This profile manager contains thefollowing profiles:

R3 Windows NT Print MonitorsContains a monitor for reporting the status (up or down) ofthe saplpd daemon on Windows NT.

R3 SAP Router MonitorsContains a monitor for reporting the status (up or down) ofthe saprouter daemon.

R3 Managed Nodes Monitors Profile ManagerThe R3 Managed Nodes profile manager does not contain anydefault profiles and is provided so you can create monitor profilesfrom Distributed Monitoring collections. The default subscriber isthe TMR server. Subscribe the appropriate managed nodes to thisprofile manager. Refer to theTME 10 Framework User’s Guideformore information about creating a profile within a profile manager.

R3 ITS Monitors Profile ManagerThe R3 ITS Monitors profile manager contains the R3 ITS ServerMonitors profile. This profile enables you to use the ITS ServerStatus monitor, which is contained in the R3 ITS Server Monitorsmonitoring collection. The ITS Server Status monitor reports thestatus (up or down) of the R/3 ITS server and has no attributes. Youmust configure and distribute this monitor to each R3ITSServerobject so that each R3ITSServer object reflects its current status. TheR3ITSServer object can represent a single-host ITS server or theAGate or the WGate component of a dual-host ITS server.

R3 Central Instance Monitors Profile ManagerThe R3 Central Instance profile manager contains the followingprofiles:

R3 Message Server MonitorsContains a message server status monitor for UNIX. This


7.M

onitoringR

/3R

esources

monitor returns the status (up or down) of the R/3 messageserver daemon. The message server status monitor has noattributes. Because there is only one message server daemonin an R/3 system, distribute this profile to only the R/3application server that is running the message server.

Manager for R/3 ships a message server status monitor forUNIX and for Windows NT in different monitoringcollections: R3 UNIX File System Monitors and R3Windows NT File System Monitors. Manager for R/3provides the R3 Message Server Monitors profile customizedto run a message server status monitor for UNIX. If youwant to run a message server status monitor for WindowsNT only, replace the message server status monitor in the R3Message Server Monitors profile with a message serverstatus monitor for Windows NT. If you want to run amessage server status monitor for both UNIX and WindowsNT, either create a new profile that contains a messageserver status monitor for Windows NT or add a messageserver status monitor for Windows NT to the R3 WindowsNT File System Monitors profile.

R3 UNIX File System MonitorsContains monitors that report the percentage of space used,the percentage of inodes used, and the amount of free spacein various R/3 UNIX directories. For more information, see“Using the File System Monitors” on page 116. Distributethis profile to each UNIX R/3 application server that has aunique file system.

R3 Windows NT File System MonitorsContains monitors that report free space and space used onthe logical disk on which various R/3 directories reside. Formore information, see “Using the File System Monitors” onpage 116. Distribute this profile to each Windows NT R/3application server that has a unique file system.


Using Monitoring SourcesThe following topics provide additional information about using theManager for R/3 monitoring sources:

¶ “Using the Application Server Status Monitor”

¶ “Using the Storage Monitors” on page 114

¶ “Using the Performance Monitors” on page 115

¶ “Using the File System Monitors” on page 116

¶ “Using the User Monitor” on page 119

¶ “Using the Work Process Monitors” on page 119

¶ “Using the Cancelled Job Monitor” on page 121

¶ “Using OS Collect and OS/390 Monitors” on page 123

Using the Application Server Status MonitorThe Application Server Status monitor provides values that controlthe setting of the R3AppServer icon state on the desktop and theautomatic closing of Manager for R/3 TEC events. Therefore, thismonitor must be properly configured and must be distributed to allR/3 application servers for complete and accurate Manager for R/3processing. You must manually distribute this monitor after creatingthe R3AppServer objects.

Manager for R/3 provides a correctly configured application serverstatus monitor in the R3 Server Autodiscovery Monitors profile. Thismonitor supports the following response levels that correspond toeach of the returned statuses:

¶ Critical level is set when the monitor returnsBecomesunavailable.

¶ Reset level is set when the monitor returnsBecomes available.

¶ Warning level is set when the monitor returnsBecomesstandby.


7.M

onitoringR

/3R

esources

If you do not choose to use the provided Application Server Statusmonitor, create an Application Server Status monitor that complieswith the following rules:

¶ Provides a unique response level for each of the monitor’sreturned statuses.

¶ Does not configure more than one response level for each of themonitor’s returned statuses.

¶ Does not configure thealways response level.

The default Application Server Status monitor is configured togenerate a TEC event for each of the response levels. These TECevents must be generated so that Manager for R/3 TEC rules canproperly close Manager for R/3 events. The default monitor is alsoconfigured to run every minute. This interval can be changed;however, it is recommended that the monitoring interval does notexceed five minutes so that the application server status changes arereflected in a timely fashion.

Because the Application Server Status monitor is key to Manager forR/3 processing, you should distribute this monitor to each R/3application server being managed. The easiest way to distribute acorrectly configured Application Server Status monitor is todistribute the R3 Server Autodiscovery Monitors profile to the R3App Server List profile manager for each R/3 system.

Manager for R/3 processing depends on the generation of a singleevent for each application server state change. In addition toconfiguring a unique response level for each of the monitor values,you must also ensure that only one copy of the monitor is distributedto each R/3 application server. Therefore, if you are distributingmultiple monitoring profiles to an R/3 application server, ensure thatthere is only one Application Server Status monitor in all themonitoring profiles that you are distributing.

Using the Storage MonitorsManager for R/3 provides monitors in the R3 Server Remote and R3Server Central monitoring collections for many of the key storageareas in R/3 application servers. You can monitor critical values,


such as free space, used spaced, and percentages for many storageareas. The specific values that can be monitored depend on theparticular storage area. You can monitor the following storage areas:

¶ Roll area

¶ Page area

¶ Extended memory

¶ Heap memory

¶ Buffers

v CUA menu and text

v FTAB field catalog

v IRBD initial records

v PRES screen and dynpro

v PXA program

v SNTAB short NameTab

v TABL generic key

v TABLP single key

v TTAB table description

For a complete listing of the monitoring sources and how they relateto the R/3 system, see “Remote and Central Monitoring Sources” onpage 207.

Using the Performance MonitorsManager for R/3 provides monitors in the R3 Server Remotemonitoring collection for monitoring the performance of key R/3work processes. You can monitor performance values, such as waittime, response time, and frequency for the following work processes:

¶ Dialog

¶ Update

¶ Batch

¶ Spool


7.M

onitoringR

/3R

esources

For a complete listing of the monitoring sources and how they relateto the R/3 system, see “Remote and Central Monitoring Sources” onpage 207.

Using the File System MonitorsManager for R/3 provides file system monitors that make it easierfor you to monitor R/3 file systems than if you used DistributedMonitoring file system monitors. Many R/3 file systems have namesthat include the R/3 SID. For example, the transport directory isnamed /usr/sap/SID/trans. To monitor the transport directory usingDistributed Monitoring monitors, you would need to create amonitoring profile for each SID, and you would need to ensure thatyou distributed the correct monitoring profile to the appropriate R/3application server. Because Manager for R/3 file system monitorsautomatically substitute the SID based on the R/3 application serverto which the monitoring profile is distributed, you can create oneprofile that you distribute to multiple R/3 application servers.

Manager for R/3 provides two monitoring collections: R3 UNIX FileSystem Monitors and R3 Windows NT File System Monitors thatcontain monitoring sources for various R/3 UNIX and Windows NTfile systems, respectively.

UNIX File System MonitorsUNIX File System monitors enable you to monitor the followingvalues for various R/3 UNIX file systems:

Used %Returns the percentage of space used in the specified filesystem

Inode Used %Returns the percentage of inodes used in the specified filesystem.

Space FreeReturns the amount of free space in KB in the specified filesystem.

The name of each monitoring source includes the name of the filesystem followed by the monitor attribute, such as SAP Transport -


Used %, SAP Transport - Inode Used %, and SAP Transport - SpaceFree. The following table describes the file system name as itappears in the name of the monitoring source and the correspondingR/3 directory, whereSID is the three-character R/3 system identifier:

File System UNIX Directory

SAP Transport /usr/sap/trans

SAP Home /usr/sap/SID

SAP Mount /sapmnt/SID

SAP Executable /sapmnt/SID/exe

SAP Profile /sapmnt/SID/profile

SAP Global /sapmnt/SID/global

Oracle datan /oracle/SID/sapdatan, wheren represents anumber from 1 through 20. Specifysapdata1 through sapdata20 in the MonitorArguments section of the Add Monitordialog.

Oracle /oracle/SID

Oracle Reorg /oracle/SID/sapreorg

Oracle Archive /oracle/SID/saparch

DB2 /db2/SID

DB2 Archive /db2/SID/log_archive

DB2 Log /db2/SID/log_dir

All of the UNIX file system monitors run against an R3AppServerendpoint. The monitors will not run if they are distributed tomanaged node endpoints. Use the R3 UNIX File System Monitorsprofile to distribute the UNIX file system monitors. For moreinformation about the R3 UNIX File System Monitors profile, see“R3 Central Instance Monitors Profile Manager” on page 111.

Windows NT File System MonitorsWindows NT File System monitors enable you to monitor R/3 filesystem values. To locate and report on the file systems, the Windows


7.M

onitoringR

/3R

esources

NT file system monitors rely on Windows NT registry keys andvalue names that are set when R/3 is installed using SAP installationtools.

Note: If you have reconfigured your system or moved files afterinstalling R/3, you must ensure that the Windows NT registryreflects your changes.

You can monitor various R/3 Windows NT file systems for thefollowing values:

Used %Returns the percentage of space used on the logical disk onwhich the specified file system resides

Space FreeReturns the amount of free space in KB on the logical diskon which the specified file system resides

The name of each monitoring source includes the name of the filesystem followed by the monitor attribute, such as SAP Home - Used% and SAP Home - Space Free.

The following table describes the file system name as it appears inthe name of the monitoring source, the corresponding R/3 directory,whereSID is the three-character R/3 system identifier, and the valuename that must exist in the Windows NT registry:

File System Windows NT Directory Windows NT ValueName

SAP Home ...\usr\sap\SID ImagePath

Oracle ...\oracle\SID SAPDATA_HOME

Oracle datan ...\oracle\SID\sapdatan, wheren represents anumber from 1 through 20. Specify sapdata1through sapdata20 in the Monitor Argumentssection of the Add Monitor dialog.

SAPDATAn

Oracle Reorg ...\oracle\SID\sapreorg SAPREORG

Oracle Archive ...\oracle\SID\saparch SAPARCH

Oracle Backup ...\oracle\SID\sapbackup SAPBACKUP


File System Windows NT Directory Windows NT ValueName

Oracle Check ...\oracle\SID\sapcheck SAPCHECK

Oracle Statistics ...\oracle\SID\sapstat SAPSTAT

Oracle Trace ...\oracle\SID\saptrace SAPTRACE

Note: The ImagePath value name resides inHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAPSID_IID . Theremaining value names reside inHKEY_LOCAL_MACHINE\SOFTWARE\SAP\SID\Environment.

All of the Windows NT file system monitors run against anR3AppServer endpoint. Use the R3 Windows NT File SystemMonitors profile to distribute the Windows NT file system monitors.For more information about the R3 Windows NT File SystemMonitors profile, see “R3 Central Instance Monitors ProfileManager” on page 111.

Using the User MonitorThe User monitor reports the number of active user sessions on anR/3 application server. Because the User monitor counts its ownsession on an R/3 application server, the number reported is onemore than the number of active user sessions displayed on theSAPGUI. You can configure the monitor to report all user sessions(the sum of all real terminal sessions and all APPC-TM terminalsessions) or user terminal sessions (all real terminal sessions). Formore information about the User monitor and how it relates to theR/3 system, see “User Source” on page 215.

Using the Work Process MonitorsManager for R/3 provides the following monitors in the R3 ServerRemote monitoring collection that enable you to monitor R/3 workprocesses:

¶ Work Process

¶ Work Process Dispatch Queue

¶ Long Running Work Process


7.M

onitoringR

/3R

esources

Using the Work Process MonitorThe Work Process monitor enables you to monitor the states ofvarious work processes, such as free, waiting, running, stopped,completed, or all states. The work processes you can monitor are:

¶ Dialog

¶ Update

¶ Enqueue

¶ Batch

¶ Spool

¶ Update2

¶ All

For more information about the Work Process monitor and how itrelates to the R/3 system, see “Work Process Source” on page 211.

Using the Work Process Dispatch Queue MonitorThis monitor enables you to report the number of queued requestsfor the following R/3 work processes:

¶ Nowp (non-work process)

¶ Dialog

¶ Update

¶ Enqueue

¶ Batch

¶ Spool

¶ Update2

¶ All

For more information about the Work Process Dispatch Queuemonitor and how it relates to the R/3 system, see “Work ProcessDispatch Queue Source” on page 212.


Using the Long Running Work Process MonitorThe Long Running Work Process monitor enables you to monitor thevarious work processes within an R/3 application server forexcessively long processing times. When you configure this monitor,you can specify the type of work process that you want to monitorand the time interval threshold that constitutes a long running state.

This monitor reports the number of long running processes, and italso returns additional information that provides detailed informationfor up to three long running processes. The detailed informationincludes:

¶ Work process type

¶ Work process number

¶ Client

¶ Elapsed time

¶ User name

¶ Report name

When Distributed Monitoring pop-ups are used, the detailedinformation is available as additional information in the pop-up.When Distributed Monitoring TEC events are generated, the detailedinformation is available in theLONG_RUNNING_PROCESS_MONITOR event class in the infoevent slot.

For more information about the Long Running Work Processmonitor and how it relates to the R/3 system, see “Long RunningWork Process Source” on page 212.

Using the Cancelled Job MonitorThe Cancelled Job monitor enables you to identify newly cancelledjobs, facilitates the reporting of detailed information about thesecancelled jobs, and enables you to identify periods in which manybatch jobs are being cancelled.


7.M

onitoringR

/3R

esources

The Cancelled Job monitor does not require any configurationparameters. This monitor operates by looking at all cancelled jobs inthe R/3 system. These jobs can include old jobs as well as newerjobs. Whenever cancelled jobs are found, this monitor determines ifthere are any jobs for which detailed information has not alreadybeen reported. If so, this monitor provides detailed information forone of the newly cancelled jobs.

The Cancelled Job monitor reports the number of cancelled jobs forwhich the monitorhas not previously reported detailed information.

When this monitor reports a non-zero value, the monitor returnsadditional detailed information related to one cancelled job. Thedetailed information includes:

¶ Job name

¶ Job ID

¶ Job date

When Distributed Monitoring pop-ups are used, this detailedinformation is available as additional information in the pop-up.When Distributed Monitoring TEC events are generated, this detailedinformation is available in the SAP_CANCELLED_JOB_MONITORevent class in the r3JobName, r3JobID, and r3JobDate event slots.

If you want to track cancelled jobs, you can write TEC rules toprocess the TEC event, keying on the job name, for example. If youwant to monitor for periods of high batch job failure, you can setthresholds against the reported value of the monitor. In both cases,you will need a general idea of the expected cancelled job rate toproperly set the monitoring interval. As a recommendation, youshould set your monitoring interval to be two to three times the rateat which you expect batch job failures.

Because this monitor operates against all jobs in an R/3 system, youneed to distribute the monitor to only one R/3 application server inthe R/3 system. Use the R3 Central Instance profile manager todistribute this monitor (see “R3 Central Instance Monitors ProfileManager” on page 111). Distributing the Cancelled Job monitor to


multiple application servers in the same R/3 system can result induplicate reporting of the same cancelled job.

Because this monitor must look at all R/3 cancelled jobs, theperformance of the monitor can be affected by the number ofcancelled jobs in the R/3 system. This monitor can adequatelyprocess up to 300 cancelled jobs. Although it is not possible toprovide a specific limit on the number of cancelled job that thismonitor can process, this monitor might be able to process morethan 300 cancelled jobs.

Note: The job limit applies to the number of cancelled jobs in theR/3 system, not the total number of jobs in the R/3 system.You can have hundreds of jobs in the R/3 system, but try tokeep the number of cancelled jobs to 300 or less.

Using OS Collect and OS/390 MonitorsMost of the monitors delivered with Manager for R/3 are intended tobe run directly on the remote endpoints. Typically, these endpointsare the R/3 application server machines. The OS/390 and some ofthe OS Collect monitors do not fit this model. Because Manager forR/3 does not always have direct access to the R/3 database server,database monitoring information is collected indirectly using R/3itself to provide the information. This section explains thedifferences between the OS/390 and OS Collect monitoring sourcesand how to use them.

OS Collect - Application ServerThis source provides operating system monitors for an applicationserver, as that information is reported in the R/3 system. Thesemonitors collect their information by communicating directly withthe application server. The communication with the applicationserver can be either directly on the application server machine or itcan be remotely from the TMR server.

To use these monitors directly on the application server machine,follow these steps:

1. Add a monitor from the Server Remote Monitors collectionwithin the R3 App Server Monitors profile manager.


7.M

onitoringR

/3R

esources

2. Add a monitor using theOS Collect – Application Servermonitoring source.

3. Select the attribute you want to monitor.

After you have added all monitors, distribute the profile to theappropriate application servers to begin monitoring.

To use these monitors on the TMR server, follow these steps:

1. Add a monitor from the Server Central Monitors collectionwithin the R3 App Server Monitors profile manager.

2. Add a monitor using theOS Collect - Application Servermonitoring source.

3. Select the attribute you want to monitor and select theapplication server you want to monitor.

After you have added all monitors, distribute the profile to the TMRserver to begin monitoring.

OS Collect - Database ServerThis source provides operating system monitors for a non-OS/390database server, as that information is reported in the R/3 system.These monitors collect their information through any applicationserver connected to the R/3 database server.

To use these monitors, follow these steps:

1. Add a monitor from the Server Central Monitors collectionwithin the R3 DB Server Monitors profile manager.

2. Add a monitor using theOS Collect - Database Serversource.

3. Select the attribute you want to monitor and select an applicationserver connected to the database server you want to monitor.



OS/390This source provides operating system monitors for an OS/390database server, as that information is reported in the R/3 system.These monitors collect their information through any applicationserver connected to the R/3 database server on the OS/390.



2. Add a monitor using theOS/390source.



OS/390 DB2The OS/390 DB2 monitoring source provides DB2 monitors for anOS/390 database server, as that information is reported in the R/3system. These monitors collect their information through anyapplication server connected to the R/3 database server on theOS/390.



2. Add a monitor using theOS/390 DB2source.




7.M

onitoringR

/3R

esources


Tasks for Managing R/3Resources

Manager for R/3 provides the following task libraries that includetasks to help you manage R/3 resources:

¶ R3 System Tasks

¶ R3 App Server Tasks

¶ R3 DB Server Tasks

¶ R3 ITS Server Tasks

This chapter describes the tasks contained within these task libraries.

Note: Manager for R/3 also provides task libraries that containconfiguration tasks to help you configure the Manager forR/3. See “Using Manager for R/3 Configuration Tasks” onpage 35.

Some tasks are provided on the pop-up menu for each R/3 system,R/3 application server, R/3 database server, and R/3 ITS server icon.Right-click an icon to display the icon’s pop-up menu.

Running a TaskTo run a task, follow these steps:

8


8.Tasks

forM

anagingR

/3R

esources

1. From the desktop, open theManager for R3 policy region tolocate the R3 System Tasks, R3 App Server Tasks, R3 DB ServerTasks, and R3 ITS Server Tasks icons.

2. Open the appropriate task library:

¶ R3 System Tasksto display R/3 system tasks

¶ R3 App Server Tasksto display application server tasks

¶ R3 DB Server Tasksto display database server tasks

¶ R3 ITS Server Tasksto display ITS server tasks

A task library window is displayed. For example, the TaskLibrary: R3 App Server Tasks window is displayed as a result of


double-clicking theR3 App Server Tasksicon.


8.Tasks

forM

anagingR

/3R

esources

3. Run the appropriate task to display the Execute Task dialog.

4. Complete theExecute Taskdialog, referring to the online help ifyou need additional information. Specify the task endpoints asfollows:

¶ For an R/3 system task, select an endpoint of typeR3System, such asSID_DBhostname(R3System).

¶ For an R/3 application server task, select an endpoint of typeR3AppServer, such ashostname_SID_IID(R3AppServer)

¶ For an R/3 database server task, select an endpoint of typeR3DBServer, such ashostname_SID_DB (R3DBServer).


¶ For an R/3 ITS server task, select an endpoint of typeR3ITSServer, such ashostname_VIIN_ITS (R3ITSServer).

For more information, see “Manager for R/3 Object Endpoints”on page 29.

5. Click Execute and Dismissto start the task. If the task requiresarguments, a dialog is displayed.

If a dialog is displayed, complete the dialog and then clickSetand Executeto start the task.

Note: Each dialog has a Help button that you can select to viewinformation about the dialog’s input fields.

R3 System TasksThe R3 System Tasks library contains the following tasks to helpyou manage R/3 systems:

Type of Task Tasks Role Target

“Controlling theR/3 System”

¶ Start R/3 System

¶ Stop R/3 System

r3_user R3Systemendpoint

Controlling the R/3 SystemManager for R/3 provides the following tasks in the R3 SystemTasks library to control the R/3 system:

Start R/3 SystemStarts the database server and all application servers in thespecified R/3 system.


8.Tasks

forM

anagingR

/3R

esources

Stop R/3 SystemStops the database server and all application servers in thespecified R/3 system.

The results of the task are displayed in an output dialog, and thestatuses of the database and application servers are displayed on theiricons.

R3 App Server TasksThe R3 App Server Tasks library contains the following tasks to helpyou manage R/3 application servers:


“ControllingEvent Adapters”on page 133

¶ Start EventAdapter

¶ Stop EventAdapter

r3_user R3AppServerendpoint

“ControllingApplicationServers” onpage 133

¶ Start Server

¶ Stop Server


“DisplayingApplicationServerPerformanceInformation” onpage 134

¶ Display BufferInformation

¶ Display Roll PageInformation

¶ Display OSCollectInformation

¶ Display OS/390Information

¶ Display OS/390DB2 Information




“Managing BatchJobs” onpage 134

¶ Display BatchJobs

¶ Cancel Batch Job

¶ Release Batch Job


“Controlling R/3Work Processes”on page 135

¶ Display WorkProcesses

¶ Cancel WorkProcess


Controlling Event AdaptersManager for R/3 provides the following tasks in the R3 App ServerTasks library to control event adapters:

Start Event AdapterStarts the Alert Event Adapter, the Syslog Event Adapter, orthe IDOC Event Adapter on the specified R/3 applicationserver.

Stop Event AdapterStops the Alert Event Adapter, the Syslog Event Adapter, orthe IDOC Event Adapter on the specified R/3 applicationserver.

A dialog is presented in which you specify which adapter to start orstop.

Controlling Application ServersManager for R/3 provides the following tasks in the R3 App ServerTasks library to control R/3 application servers:

Start ServerStarts the specified R/3 application server.

Stop ServerStops the specified R/3 application server.


8.Tasks

forM

anagingR

/3R

esources

Note: The stop command output may sometimes report an errorwith awk. This is caused when the SAP-providedstopsapscript is called while a Tivoli monitor is running. This errordoes not affect the complete shutdown processing of the R/3application server.

Displaying Application Server PerformanceInformation

The following tasks enable you to display application serverinformation for various application server buffers, roll and pageareas, and operating system metrics. These tasks display the sameinformation that the Manager for R/3 monitors report, except forpercentages which are calculated. For more information about theinformation that is returned, each task in the following list includes areference to the appropriate Manager for R/3 monitor.

¶ Display Buffer Information. See “Buffer Source” on page 213.

This task presents a dialog in which you can specify the R/3buffer type. The default isPXA – Program Buffer .

¶ Display Roll Page Information. See “Roll Area Source” onpage 209 and “Page Area Source” on page 210.

¶ Display OS Collect Information. See “OS Collect Source” onpage 208.

¶ Display OS/390 Information. See “OS/390 Source” on page 217.

¶ Display OS/390 DB2 Information. See “OS/390 DB2 Source” onpage 215.

Managing Batch JobsManager for R/3 provides the following tasks to enable you tomanage R/3 batch jobs:

Display Batch JobsDisplays the following information for R/3 batch jobs:

¶ Date

¶ Job name

¶ Job ID


¶ Scheduled by

¶ Released by

¶ Status

¶ Class

Cancel Batch JobCancels a batch job that is active. A dialog is displayed inwhich you enter the name and the job ID of the job youwant to cancel. Use the Display Batch Jobs task to determinethe appropriate job name and job ID.

Release Batch JobReleases and starts a scheduled batch job. A dialog isdisplayed in which you enter the name and job ID of the jobyou want to release. Use the Display batch jobs task todetermine the appropriate job name and job ID.

Controlling R/3 Work ProcessesManager for R/3 provides the following tasks to help you manageR/3 work processes:

Display Work ProcessesDisplays information for R/3 processes that are running onthe specified application server. R/3 process informationincludes the process ID, status, reason, and CPU time. Adialog is displayed in which you can specify if you want theCPU time for each process to be returned as part of the data.

Cancel Work ProcessCancels an R/3 process. A dialog is displayed in which youspecify the process ID and if you want a core dump. Use theDisplay Work Processes task to determine the appropriateprocess ID.


8.Tasks

forM

anagingR

/3R

esources

R3 DB Server TasksThe R/3 DB Server Tasks library contains the following tasks to helpyou manage an R/3 database:


“Controlling aDatabase Server”

¶ Start Database

¶ Stop Database

r3_user R3DBServerendpoint

“Controllingdbaccess”

Start dbaccess r3_user R3DBServerendpoint

Controlling a Database ServerManager for R/3 provides the following tasks to control the R/3database server:

Start DatabaseStarts the R/3 database server.

Stop DatabaseStops the R/3 database server.

Notes:

1. When starting or stopping a UNIX database server, the start andstop tasks log on assidadm and use the utilities of an applicationserver on the same machine. The database server must berunning on the same machine as an R/3 application server. Thestop processing also stops all SID-related application servers onthe node.

2. Starting or stopping a Windows NT database server requirescustomer exit routines. For more information, see “Creating ExitRoutines for Windows NT” on page 72.

Controlling dbaccessThe Start dbaccess task starts dbaccess on the specified databaseserver. The status of the start dbaccess job is displayed in the Startdbaccess Output dialog, and thedbaccessxterm window is


displayed. You can use structured query language (SQL) commandsto access the R/3 database. Press theCtrl-W key combination forhelp.

Note: This task is only supported with a Motif windows managerand an Informix database.

R3 ITS Server TasksThe R3 ITS Server Tasks library contains the following tasks to helpyou manage R/3 ITS servers:


“Controlling ITSServers”

¶ Start ITS Server

¶ Stop ITS Server

r3_user R3ITSServerendpoint

Controlling ITS ServersManager for R/3 provides the following tasks in the R3 ITS ServerTasks library to control R/3 ITS servers:

Start ITS ServerStarts the R/3 ITS server.

Stop ITS ServerStops the R/3 ITS server.

If the R3ITSServer object to which the Start ITS Server or Stop ITSServer task is distributed represents a single-host ITS serverconfiguration, both the AGate and WGate components are started orstopped. If the R3ITSServer object represents one gate of a dual-hostITS server configuration, the gate (AGate or WGate) represented bythe R3ITSServer object is started or stopped.


8.Tasks

forM

anagingR

/3R

esources


Distributing SAPGUI Software

This chapter describes how to create SAPGUI software file packagesfor distribution of the SAPGUI for Windows NT, Windows 95/98,and UNIX, and it describes how to distribute SAPGUI software filepackages.

Note: The tasks to create SAPGUI software file packages createprofile managers and profiles as a result of their processing.For these actions to succeed, the administrator running thesetasks must also have the Tivoli super role.

Creating SAPGUI Software File PackagesThe method you choose to create SAPGUI software file packagesdepends upon the version of the SAPGUI software you want todistribute. Follow one of these procedures:

¶ For Windows NT and Windows 95/98 SAPGUI versions prior to4.5B and for all UNIX SAPGUI versions, see “CreatingSAPGUI File Packages for SAPGUI Versions Prior to 4.5B” onpage 140.

Note: Software Distribution must be installed on the TMRserver.

¶ For Windows NT and Windows 95/98 SAPGUI versions 4.5Band later, see “Creating SAPGUI File Packages for WindowsSAPGUI Versions 4.5B and Later” on page 143.

9


9.D

istributingS

AP

GU

IS

oftware

Note: Software Distribution must be installed on the R/3SAPGUI installation server, and SAP requires that the R/3SAPGUI installation server resides on a Windows NTmachine.

Creating SAPGUI File Packages for SAPGUI VersionsPrior to 4.5B

You can create various file packages with different options andconfigurations. Each file package is identified by the name youspecify when you create the file package. You can configureSAPGUI file packages by using either a reference installation or byusing an R/3 native installation. To perform a reference installation,you first install and configure a copy of the SAPGUI. Files in thisreference copy are distributed directly to the endpoints. An R/3native installation assumes that the SAPGUI CD-ROM image isavailable on the target systems and installs directly on the targetfrom the CD-ROM, using R/3 installation tools and procedures.

To create SAPGUI software file packages for distribution of theSAPGUI for Windows NT and Windows 95/98 prior to Version 4.5Band for all UNIX versions, follow these steps:

1. From the Tivoli desktop, open the Manager for R3 policy regionto display the Policy Region: Manager for R3 window.

2. Open the R3 Configuration policy region to display the PolicyRegion: R3 Configuration window.

3. Open the R3 Configuration Tasks library to display theconfiguration tasks.

4. Run one of the following tasks or jobs:

¶ Configure Client Install

This is a reference copy installation. You must manuallyinstall one SAP client with the R/3 SAPGUI and copy thefiles to the TMR server before executing this job.

For Windows NT and Windows 95/98 installations, you mustcopy the DLLs to a subdirectory named dll under thedirectory in which the source code resides.


The AFTER script creates entries on the Windows NT andthe Windows 95/98 Start menus forsapgui.exe,saplogon.exe, andsapicon.exe. On Windows NT targets, theAFTER script will be able to find the location of thesapgui.exe, saplogon.exe, andsapicon.exeexecutablesregardless of where they exist within the source code. OnWindows 95/98 targets, you must place these executables atthe root of the directory in which the source code resides.

¶ Configure UNIX Client Install

This is an R/3 native installation.

¶ Configure Windows 95/98 Client Install


¶ Configure Windows NT Client Install


The platform-specific Configure Client Install dialog is displayed.For example, the following dialog is displayed as a result of


9.D

istributingS

AP

GU

IS

oftware

running the Configure Windows NT Client Install task.


When you create a SAPGUI software file package, a new profilemanager is created in the R3 Configuration policy region that islabeled Install Clients (ConfigurationName), whereConfigurationNameis the name you associated with the file packagewhen you created the file package. The profile manager contains thefile package for the specified configuration.

For reference installations, the file package includes BEFORE andAFTER programs and the directory from which the SAPGUIinstallation will be copied. For native installations, the file packageincludes BEFORE and AFTER programs. The SAPGUI installationCD from SAP must be accessible on the target machine. If you aredistributing the SAPGUI to several machines in one distribution, you


can choose to mount the SAPGUI CD on a network shared drive. Ifyou need to mount the SAPGUI CD during installation, you shouldconsider using the optional command fields on the platform-specificConfigure Client Install dialog.

Creating SAPGUI File Packages for Windows SAPGUIVersions 4.5B and Later

For Windows NT and Windows 95/98 SAPGUI version 4.5B andand later, SAPGUI file packages are created on an R/3 SAPGUIinstallation server using R/3 tools and procedures. Manager for R/3provides tasks that enable you to determine the appropriate filepackage to distribute and a task that enables you to create a filepackage which, when distributed, installs the SAPGUI software.Because these tasks run against the SAPGUI installation server, theSAPGUI installation server must be defined as a managed node andManager for R/3 must be installed on the SAPGUI installationserver.

To create SAPGUI file packages for distribution of the SAPGUI forWindows NT and Windows 95/98, follow these steps:

1. Optionally, determine the names of the file packages that areavailable on the R/3 SAPGUI installation server. If you know theexact name of the file package you want to distribute, proceed tostep 2 on page 144. Otherwise, run theList Available SAPGUIFile Packagestask in the R3 Configurations Task library todisplay the Listing of Available Packages dialog.

The task output lists the names the SAPGUI file packages for theselected version.


9.D

istributingS

AP

GU

IS

oftware

2. Optionally, determine the details about a SAPGUI file package.If you know which file package you want to distribute, proceedto step 3. Otherwise, run theList SAPGUI Package Featurestask in the R3 Configuration Tasks library to display the PackageFeatures dialog.

For information about completing the dialog, refer to the onlinehelp. The task output lists the details about the specified filepackage.

3. Create the SAPGUI file package for distribution. Run theConfigure SAPGUI Packagetask in the R3 Configuration Taskslibrary to display the Install Package dialog.


For information about completing the dialog, refer to the onlinehelp.

A profile manager named SAPGUI Installation Server Packages iscreated, if it does not already exist, in the R3 Configuration policyregion. This profile manager contains the SAPGUI file package youcreated. The file package contains only an AFTER program thatinitiates installation of the SAPGUI file package from the installationserver. Each file package you create is identified by the name of theSAPGUI file package you specified when you created the filepackage.

Distributing SAPGUI SoftwareYou perform the SAPGUI installations by distributing the filepackage to the subscribers you specified.

¶ For native installations on UNIX, the installation is performedby calling thecar program. Each selectable SAPGUI optioncorresponds to acar file that will be unpacked duringinstallation.

¶ For native installations of SAPGUI versions prior to 4.5B onWindows NT and Windows 95/98, the installation is performedby calling the SAP-providedsapsetupprogram.

Note: For Windows 95/98 installations, thesapsetupprogramreturns control to the installation AFTER program beforesapsetupactually completes its processing. If errors occurin the sapsetupprogram on Windows 95/98, these errorswill not be reported back to Tivoli during the file packagedistribution.

¶ For installations of SAPGUI versions 4.5B and later onWindows NT and Windows 95/98, the installation is performedby using SAP-provided tools to install the SAPGUI file packagefrom an installation server.

Note: Depending on the configuration of the SAPGUIinstallation server, you might be restricted to installing the


9.D

istributingS

AP

GU

IS

oftware

SAPGUI file package on a machine that is in the sameNT domain as the SAPGUI installation server.

Before distributing the file packages, ensure that the subscriber listfor the profile manager has been updated with the appropriateendpoints or subscriber lists. Double-click the appropriate filepackage profile manager to display the Profile Manager window.From theProfile Manager menu, selectSubscribersand completethe Subscribers dialog. After you have set the subscribers for theprofile manager, follow these steps to distribute the file package:

1. Open the appropriate profile manager to display the ProfileManager window.

2. If you are distributing the file package to TMA endpoints, followthese steps to change the file package profile manager fromdatabase mode to dataless mode:

a. From the Profile Manager window, from theEdit menu,selectProfile Manager to display the Edit Profile Managerdialog.

b. SelectDataless Endpoint Mode. Then clickChange &Close.

Note: Refer to theTME 10 Framework User’s Guideformore information about database mode and datalessmode profile managers.

3. Right-click the file package icon and selectDistribute from thepop-up menu.

4. Complete the Distribute File Package dialog, referring to theonline help for additional information.

For more information, refer to theTME 10 Software DistributionUser’s Guide.


Tivoli GEM Instrumentation

You can optionally manage R/3 resources from the Tivoli GEMconsole. To do this, you must install the following:

1. Tivoli Manager for R/3, Version 2.1 (Manager for R/3)

2. Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version2.1 (Tivoli GEM instrumentation)

This chapter provides an overview of Tivoli GEM instrumentationand describes the installation prerequisites and the steps to installTivoli GEM instrumentation. It also describes how to uninstall TivoliGEM instrumentation. For more information about Tivoli GEM,refer to the Tivoli GEM product documentation.

Tivoli GEM defines the concept of a business system to organizerelated applications. A business system includes all the applicationsthat together perform a business function, such as R/3 processing. Italso includes performance measures that determine whether thebusiness system is functioning properly.

For example, an R/3 business system would include all the instancesof the R/3 system, R/3 ITS server resources, R/3 application serverresources, and their associated database server resources. Thebusiness system includes the following:

¶ Tasks that can initiate actions against an R3System, anR3Application, an R3Database, and an R3ITSServer componentinstance

10


10.TivoliG

EM

Instrumentation

¶ Monitors that report status information about R3Application,R3Database, and R3ITSServer resource components

Tivoli GEM consists of a Tivoli GEM server that runs as anapplication on a managed node and a Tivoli GEM console. TivoliGEM uses application instrumentation to get the necessary data todisplay and manipulate business systems, such as R/3. Tivoli GEMinstrumentation enables you to graphically monitor and control R/3resources that reside on a Tivoli managed node or TMA endpoint.

Understanding the Tivoli GEM ServerThe Tivoli GEM server interacts with instrumented applications,such as the Manager for R/3, to provide information for display onthe Tivoli GEM console. The Tivoli GEM server is the recipient ofheartbeat events from instrumented application components anddetermines the business system to which a component belongs. TheTivoli GEM server also queries instrumented applications for relatedcomponents and the status of their monitors. Using this information,Tivoli GEM creates and maintains a view of the configuration ofeach business system and the availability of the business system.

The Tivoli GEM server furnishes the Tivoli GEM console with a setof tasks that are applicable for a component. These tasks appear incontext-sensitive menus on the Tivoli GEM console. The TivoliGEM server also stores files on behalf of the Tivoli GEM console,including icons, backgrounds, help files, log files, customizationviews, and settings.

Understanding the Tivoli GEM ConsoleThe Tivoli GEM console graphically displays the business systeminformation from the Tivoli GEM server. The Tivoli GEM consoledoes the following:

¶ Displays each component as a separate icon.

¶ Draws lines between icons to denote links.

¶ Uses color to indicate the status of each component and thestatus of the entire business system.


As the Tivoli GEM server receives status updates pertaining to thebusiness systems, it updates the Tivoli GEM console, enabling youto view the real-time status of the business system.

Tivoli GEM supports aggregation, which is a logical grouping ofinstances of the same or different component types. Tivoli GEMinstrumentation provides for the automatic aggregation of all R/3component instances based on the system to which they belong.Thus the initial top-level view on the Tivoli GEM console showssystem aggregate icons. Aggregates are depicted on the Tivoli GEMconsole view with a plus sign by their icon. Opening a systemaggregate produces a view with the contained R3System,R3Application, R3Database, and R3ITSServer component instanceswithin that system aggregate. The instrumented aggregation ispredefined in business system component, business system mapping,and software component description files.

Tivoli GEM Instrumentation Event HandlingThe Tivoli GEM server discovers the R/3 components upon receiptof heartbeat events. As the Tivoli GEM server receives monitor andstatus updates for the R/3 business system, it updates the TivoliGEM console. Tivoli GEM Event Enablement must be installed andconfigured on the TEC event server for Tivoli GEM events to besupported by the Tivoli Enterprise Console (TEC). ConfiguringTivoli GEM Event Enablement includes defining theAPM_HEARTBEAT and APM_THRESHOLD event classes to TECand defining the Tivoli GEM servers to which the Tivoli GEMevents will be forwarded. You must also add the Tivoli GEMinstrumentation rule set to the current rule set. See “Adding theTivoli GEM Instrumentation Rule Set” on page 154.


10.TivoliG

EM

Instrumentation

Instrumented ComponentsTivoli GEM instrumentation includes instrumentation for thecomponents which correspond to each Manager for R/3 object asdescribed in the following table:

Manager for R/3 InstrumentationComponent

Manager for R/3 Object

R3System R3System

R3Application R3AppServer

R3Database R3DBServer

R3ITSServer R3ITSServer

Instrumentation Task LibrariesSuccessful installation of Tivoli GEM instrumentation creates tasklibraries that are visible on the Tivoli desktop. The following is anoverview of the resulting desktop structure:

Note: Hostnameis the host name of the TMR server.

Preparing to Install Manager for R/3 InstrumentationReview the topics in the following sections before installing TivoliGEM instrumentation.

Tivoli Management RegionsTivoli Management Regions (TMRs) should be properly configuredbefore installing Tivoli GEM instrumentation.

Top-Level Policy RegionApplications_Hostname-region

Policy RegionPR_SAPR3_Default_Hostname-regionTask LibrariesTL_SAPR3_2.1._Default_R3System_2.1._Hostname-regionTL_SAPR3_2.1._Default_R3Application_2.1._Hostname-regionTL_SAPR3_2.1._Default_R3Database_2.1._Hostname-regionTL_SAPR3_2.1._Default_R3ITSServer_2.1._Hostname-region


AdministratorsTivoli administrators need the following authorization roles:

¶ To install Tivoli GEM instrumentation, install_product authorityis required.

¶ To start tasks from the Tivoli GEM console, r3_user authority isrequired for the user ID that you use to log on to the TivoliGEM console.

Installation Prerequisites

Before installing Tivoli GEM instrumentation, you must install andconfigure Framework, TEC, Manager for R/3, and Tivoli GEM. TheTEC event server must be running in each TMR in which TivoliGEM instrumentation is installed.

Installing and Configuring Tivoli GEMInstrumentation for Manager for R/3

The following table shows the location of the installed components:

Installed ComponentTarget Nodes

Tivoli GEMServer

TMR server

Instrumentation definition files X

Instrumentation task libraries X

To install Tivoli GEM instrumentation, follow the steps in theremaining sections of this chapter.

Installing or Upgrading the Tivoli GEMInstrumentation Definition Files

If you are installing the Tivoli GEM instrumentation definition filesfor the first time or if you have Tivoli GEM instrumentation Version2.0 installed and are upgrading to Version 2.1, you must load thenew applications management package (AMP) file. To do this, from


10.TivoliG

EM

Instrumentation

the Tivoli GEM consoleFile menu, selectLoad New AMP. Thenselect/GEMFILES/sapr3_21.pkg from the Manager for R/3 CD.

Installing the Tivoli GEM Instrumentation TaskLibraries

Install the Tivoli GEM instrumentation task libraries from the Tivolidesktop. Do one of the following:

¶ If you have Tivoli GEM instrumentation Version 2.0 installed,see “Upgrading the Tivoli GEM Instrumentation Task Libraries”.

¶ If you are installing Tivoli GEM instrumentation for the firsttime, see “Installing the Tivoli GEM Instrumentation TaskLibraries”.

Upgrading the Tivoli GEM Instrumentation Task LibrariesTo upgrade the Tivoli GEM instrumentation task libraries fromVersion 2.0 to Version 2.1, back up the Tivoli database. Then, installTivoli GEM Instrumentation for Tivoli Manager for R/3 Version2.1 (Upgrade from Version 2.0)from the Tivoli desktop as a patch.Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1(Upgrade from Version 2.0) is located in the /UPGD_GEM directoryon the Manager for R/3 CD. The upgrade patch replaces Version 2.0task libraries with Version 2.1 task libraries.

After installing the upgrade patch, delete Version 2.0 objects fromthe Tivoli GEM console and run the Send GEM Heartbeat task inthe R3 Configuration Tasks library to synchronize the Tivoli GEMconsole with the Manager for R/3 objects on the desktop.

Installing the Tivoli GEM Instrumentation Task LibrariesTo install the Tivoli GEM instrumentation task libraries, follow thesesteps from the Tivoli desktop:


2. From theInstall menu, clickInstall Product to display theInstall Product dialog.

3. Click Select Mediato display the File Browser dialog, fromwhich you specify the path to the installation media.


4. Enter the full path to the Tivoli GEM instrumentationinstallation files in the Path Name text field. The Tivoli GEMinstrumentation files are located in the /GEMIMAGE directoryon the Manager for R/3 CD.

5. Click Set Path. The File Browser dialog displays the contentsof the specified media in the Files scrolling list.

6. Click Set Media & Close. The Install Product dialog isdisplayed with Tivoli GEM Instrumentation for Tivoli Managerfor R/3 Version 2.1 listed in the Select Product to Installscrolling list.

7. SelectTivoli GEM Instrumentation for Tivoli Manager forR/3 Version 2.1.

8. Click the targets on which you do not want to install TivoliGEM instrumentation from the Clients to Install On list and


10.TivoliG

EM

Instrumentation

click the right arrow button to move them to the AvailableClients list. Install the Tivoli GEM instrumentation task librarieson the TMR server.

9. Click Install & Close. The Product Install window is displayed,listing the actions that will be taken when you complete theinstallation process.

10. Click Continue Install to begin the installation process. TheProduct Install window continues to display messages that showthe progress of the installation. Successful installation isindicated by aFinished product installation message.

11. Click Close.

12. After installing the Tivoli GEM instrumentation task libraries,backup the Tivoli database.

The Tivoli GEM instrumentation task libraries are installed in thePR_SAPR3_Default_Hostname-region policy region which is withinthe Applications_Hostname-region on the desktop.

Adding the Tivoli GEM Instrumentation Rule SetThe Tivoli GEM instrumentation rule file, sap_gemevents.rls,includes TEC rules that forward all Manager for R/3 monitor eventsto the Tivoli GEM server. To add the sap_gemevents.rls to thecurrent rule set, use the Manager for R/3 Configure Event Servertask. See “Configuring the TEC Event Server” on page 82.

Note: If you ran the Configure Event Server task before youinstalled Tivoli GEM instrumentation, you must run theConfigure Event Server task again to install thesap_gemevents.rls rule file.

Synchronizing the Tivoli GEM Console with theDesktop

The Tivoli GEM console is synchronized with the Manager for R/3objects on the desktop. When an R/3 object is created, a heartbeatevent is automatically sent to the TEC event server. The TEC eventserver forwards the event to the Tivoli GEM server, and an icon is


displayed on the Tivoli GEM console. If the Tivoli GEM consolebecomes unsynchronized with the desktop, run theSend GEMHeartbeat task in the R3 Configuration Tasks library (see “UsingManager for R/3 Configuration Tasks” on page 35) against theappropriate R3System, R3AppServer, R3DBServer, and R3ITSServerobjects. The Send GEM Heartbeat task sends a heartbeat event to theTivoli GEM server for each R/3 resource, and an icon is created onthe Tivoli GEM console, if needed. The Tivoli GEM console mightnot be synchronized with the desktop if the Tivoli GEM server wasdown when the R/3 object was created, if you installed Tivoli GEMinstrumentation after you created the R/3 objects, or if the TivoliGEM databases are erased.

Understanding R/3 Aggregate ResourcesIcons representing aggregates of R/3 resources are automaticallyprovided on the Tivoli GEM console. A Manager for R/3 icon is thehighest-level aggregate resource.

Double-click the Manager for R/3 icon to display the R/3 systemaggregate icons.

Double-click an R/3 system aggregate icon to display the R/3system, R/3 application server, R/3 database server, and R/3 ITSserver icons.

Resources might not be aggregated if the internal aggregation taskstimed out. To manually aggregate resources, right-click a resourceicon and selectAdd to Aggregate. Select the aggregate to whichyou want to add the resource. Alternatively, you can synchronize theresources from the Tivoli desktop. See “Synchronizing the TivoliGEM Console with the Desktop” on page 154.

Navigating to R/3 ResourcesOn the Tivoli GEM console, you navigate from an R/3 systemaggregate icon to a specific R/3 system, R/3 application server, R/3database server, and R/3 ITS server icon. Right-click individual R/3resources to access the pop-up menu from which you can selecttasks.


10.TivoliG

EM

Instrumentation

To locate a specific R/3 resource:

1. Open the Tivoli GEM Console.

2. Expand theApplications icon displayed in the tree view.

The Applications window is displayed containing the Managerfor R/3 icon as shown in the following figure. If the view isempty, ensure that you have created R/3 objects.

3. Display the R/3 system aggregate icons by double-clicking thebox containing the + on the Manager for R/3 icon.


4. Open the R/3 system aggregate icon to view the R/3 system, R/3application servers, R/3 database server, and R/3 ITS servericons.

Tivoli GEM Instrumentation TasksThe Tivoli GEM server furnishes the Tivoli GEM console with a setof tasks that are applicable against a component. To display the taskmenu, highlight and right-click a component icon. The tasks enableTivoli GEM users to perform actions on the component instance andto return task results to the Tivoli GEM console.

The tasks that are supported for each component are defined inbusiness system mapping and software component definition filesthat reside on the Tivoli GEM server. Installation of Tivoli GEMinstrumentation creates a task library for the R3System, theR3Application, the R3Database, and the R3ITSServer instrumentedcomponents. Each task library contains the tasks that are supportedfrom Tivoli GEM for that component.

R3System Component TasksTivoli GEM supports the following subset of Manager for R/3 tasksfor the R3System component:


10.TivoliG

EM

Instrumentation

¶ Start_System

¶ Stop_System

See “R3 System Tasks” on page 131 for more information aboutthese tasks.

R3Application Component TasksThe following Tivoli GEM instrumentation task is available for theR3Application component:

¶ Query_State reports whether the R/3 application server is up(running and accepting R/3 logons), standby, or down (notrunning, or running and not accepting R/3 logons).

Tivoli GEM also supports the following subset of Manager for R/3tasks for the R3Application component:

¶ Start_Server

¶ Stop_Server

¶ Start_Adapter

¶ Stop_Adapter

¶ Display_Buffer_Info

¶ Display_Roll_Page_Info

¶ Display_OS_Collect_Info

¶ Display_Work_Processes

¶ Cancel_Work_Process

See “R3 App Server Tasks” on page 132 for more informationabout these tasks.

R3Database Component TasksTivoli GEM supports the following subset of Manager for R/3 tasksfor the R3Database component:

¶ Query_State reports whether the R/3 database server is up,unknown, or down.

Tivoli GEM also supports the following subset of Manager for R/3tasks for the R3Database component:

¶ Start_Database


¶ Stop_Database

See “R3 DB Server Tasks” on page 136 for more informationabout these tasks.

R3ITSServer Component TasksTivoli GEM supports the following Manager for R/3 tasks for theR3ITSServer component:

¶ Query_State reports whether the R/3 ITS server is up,unknown, or down.

Tivoli GEM also supports the following subset of Manager for R/3tasks for the R3ITSServer component:

¶ Start_ITS_Server

¶ Stop_ITS_Server

See “R3 ITS Server Tasks” on page 137 for more information aboutthese tasks.

Using the Tear-Away LogBefore starting a task, open the tear-away log provided by the TivoliGEM console. The log provides current messages that show theprogress of tasks you run. To open the tear-away log, from theOptions menu, selectTear Away Log.

Running a Task from the Tivoli GEM ConsoleTivoli GEM instrumentation tasks, in addition to Manager for R/3tasks, are contained in the task libraries in thePR_SAPR3_Default_hostname-region policy region as described in“Instrumentation Task Libraries” on page 150. On the Tivoli GEMconsole, you can run instrumented tasks from the pop-up menu forthe R/3 system, the R/3 application server, the R/3 database server,and the R/3 ITS server icons.

Note: Tivoli GEM instrumentation tasks that are contained in thetask libraries but are not listed on the pop-up menu for anicon support the internal processing of Tivoli GEM functionsand are not intended to be run by Tivoli GEM users.

To run a task from the Tivoli GEM console, follow these steps:


10.TivoliG

EM

Instrumentation

1. Right-click an icon, such as an R/3 application server icon. Fromthe pop-up menu, select the appropriate task, such asDisplay_Work_Processes.

2. In this example, theGEM Log window provides informationabout the R/3 work processes.

Supported MonitorsThe Tivoli GEM console displays an icon for each monitor instancethat is supported. The monitor instance icon changes color based onthe severity of the monitor events received for that monitor. The R/3application server, R/3 database server, or R/3 ITS server iconchanges color based on the aggregate of the monitor status.

Tivoli GEM instrumentation supports the following Manager for R/3monitors for the R3Application component:¶ Application Server Status¶ Roll Area¶ Page Area¶ CUA Menu and Text Buffer¶ PRES Screen and Dynpro Buffer¶ TTAB Table Description Buffer¶ FTAB Field Catalog Buffer¶ SNTAB Short Name Tab Buffer¶ IRBD Initial Records Buffer¶ TABL Generic Key Buffer¶ TABLP Single Key Buffer¶ PXA Program Buffer¶ Dialog Performance


¶ Update Performance¶ Batch Performance¶ Spool Performance¶ OS Collect - Application Server

See “Remote and Central Monitoring Sources” on page 207 for moreinformation.

Tivoli GEM instrumentation also supports the Database Server Statusand ITS Server Status monitors for the R3Database and R3ITSServercomponents, respectively.

Monitor OperabilityTivoli GEM instrumentation includes a TEC rule that forwards allManager for R/3 monitor events to the Tivoli GEM server. When asupported monitor specifies that a TEC event be sent when athreshold is exceeded, that monitor event will be forwarded to theTivoli GEM server from the TEC. The Tivoli GEM console displaysan icon for each monitor instance that is supported. If a monitorsupports multiple arguments, then each argument (or combination ofarguments) defines an instance.

A pop-up menu is available from each monitor instance icon, whichcontains the Query_Thresholds task. This task sends a monitor eventto TEC that contains the last monitor event status if the monitor hadbeen triggered.

Viewing Monitor StatusTo view the status of supported monitors on the Tivoli GEMconsole, expand an icon for a specific R/3 server resource to display


10.TivoliG

EM

Instrumentation

the monitor status window.

Instrumenting Tivoli GEM Connection Support to R/3Components

To instrument components that provide connections to R3System,R3Application, R3Database, or R3ITSServer components, you mustinstrument the connection in your component instrumentation. Thefollowing description provides the values required to define aconnection from applications, such as MQSeries, to R3System,R3Application, R3ITSServer, or R3Database components. For moreinformation, refer to theTivoli Global Enterprise ManagerInstrumentation Guide.

To create a connection to an R/3 component, define the followingparameters in the Application Management Specification(AMS)-specified format:

¶ Connection type

¶ Connection direction

¶ Communication object information (origin/suborigin name valuepair that matches the information in the origin/suborigin slots ofthe component heartbeat to which the initiator wants to connect)

Note: For a copy of the AMS, point your Web browser to:


http://www.tivoli.com/o_products/html/body_ams_spec.html

Instrumenting a Connection to an R3SystemComponent

The R/3System component supports the following parameters:

¶ Connection type: R3System

¶ Connection direction: 3 <–> conversational

¶ (origin, suborigin):

v (0=R3System=SAPR3, 0=R3System=instance_label)

v (1=TCPIPAddress, 0=R3System=instance_label)

v (2=Hostname, 0=R3System=instance_label)

Whereinstance_labelis in the formatSID_DBhostname(SIDis the three-character R/3 system identifier, andDBhostnameis the host name of the database server).

Example:

To connect a component to R/3 systemTV4_dbserv, define adiscover connections task that returns the following string:(AMS_DC"R3System",3,"0=R3System=SAPR3","0=R3System=TV4_dbserv",,)

Instrumenting a Connection to an R3ApplicationComponent

The R3Application component supports the following parameters:

¶ Connection type: R3Application



v (0=R3Application=SAPR3, 0=R3Application=instance_label)

v (1=TCPIPAddress, 0=R3Application=instance_label)

v (2=Hostname, 0=R3Application=instance_label)


10.TivoliG

EM

Instrumentation

Whereinstance_labelis in the formatHostname_SID_IID(Hostnameis the host name of the application server,SID isthe three-character R/3 system identifier, andIID is thetwo-digit R/3 instance number.

Example:

To connect a component to R/3 application serverharrier_TV4_60,define a discover connections task that returns the following string:(AMS_DC"R3Application",3,"0=R3Application=SAPR3","0=R3Application=harrier_TV4_60",,)

Instrumenting a Connection to an R3ITSServerComponent

The R3ITSServer component supports the following parameters:

¶ Connection type: R3ITSServer



v (0=R3ITSServer=SAPR3, 0=R3ITSServer=instance_label)

v (1=TCPIPAddress, 0=R3ITSServer=instance_label)

v (2=Hostname, 0=R3ITSServer=instance_label)

Whereinstance_labelis in the formatHostname_VIIN_ITS(Hostnameis the host name of the R/3 ITS server, andVIINis the virtual ITS instance name.

Example:

To connect a component to R/3 ITS servertcasstev_TMC_ITS,define a discover connections task that returns the following string:(AMS_DC"R3ITSServer",3,"0=R3ITSServer=SAPR3","0=R3ITSServer=tcasstev_TMC_ITS",,)

Instrumenting a Connection to an R3DatabaseComponent

The R3Database component supports the following parameters:

¶ Connection type: R3Database




v (0=R3Database=SAPR3, 0=R3Database=instance_label)

v (1=TCPIPAddress, 0=R3Database=instance_label)

v (2=Hostname, 0=R3Database=instance_label)

Whereinstance_labelis in the formatHostname_SID_DB(Hostnameis the host name of the R/3 database server, andSID is the three-character R/3 system identifier.

Example:

To connect a component to R/3 database serverhound_TV4_DB,define a discover connections task that returns the following string:(AMS_DC"R3Database",3,"0=R3Database=SAPR3","0=R3Database=hound_TV4_DB",,)

Uninstalling Tivoli GEM Instrumentation TaskLibraries

To uninstall Tivoli GEM instrumentation Version 2.1 task libraries,go to the $BINDIR/../generic_unix/TME/SAPUNINST directory onthe TMR server and enter the following command:R3Mgr_uninstall21.pl –g

Note: Optionally, use the–yesparameter to uninstall Tivoli GEMinstrumentation task libraries without being prompted forconfirmation.

The R3Mgr_uninstall21.pl –g command uninstalls the Tivoli GEMinstrumentation task libraries but does not remove the definition filesfrom the Tivoli GEM server or clean up the Tivoli GEM server.


10.TivoliG

EM

Instrumentation


Command Line InterfaceCommands

Manager for R/3 uses thewr3mib andwr3rfc commands to supportits internal processing. These commands can be run directly from acommand line to support diagnostic processing as described in“Troubleshooting” on page 255. This appendix describes the Managerfor R/3 commands and their syntax.

Command Line SyntaxThe commands in this appendix use the following special charactersto define the command syntax:

[ ] Identifies an optional argument. Arguments not enclosed inbrackets are required.

... Indicates that you can specify multiple values for theprevious argument.

| Indicates mutually exclusive information. You can use theargument to the left of the separator or the argument to theright of the separator. You cannot use both arguments in asingle use of the command.

{} Delimits a set of mutually exclusive arguments when one ofthe arguments is required. If the arguments are optional, theyare enclosed in brackets ([ ]).

For example:

A


A.

Com

mand

LineInterface

Com

mands

wr3mib –a [–C Class] [–S Severity] [–n systemNumber]

The –a flag is the only required argument for this version of thewr3mib command. The brackets around the other arguments indicatethat these arguments are optional.

Another example is:

wr3mib {–a|–c|–f|–p|–s|–t}[–d] [–n systemNumber]

In this example, the–a through–t arguments are mutually exclusive,but one must be provided. The–d and–n systemNumberargumentsare optional.

SysMan and RFC CommandsThe following table lists the Manager for R/3 commands and theirpurposes:

Command Purpose

wr3mib Reads the SysMan for monitoring information.

wr3rfc Provides remote execution of R/3 functionmodules.


wr3mibReads the SysMan in support of Distributed Monitoring processing.

Note: For HP-UX 11 in 64-bit mode, use thewr3mib_64 command.The wr3mib_64 command uses the same command syntax asthe wr3mib command.

Synopsiswr3mib {–a|–c|–f|–p|–s}[–d] [–n systemNumber]

wr3mib –a [–C Class] [–S Severity] [–n systemNumber]

wr3mib –P PerfAttr –T ServType–n systemNumber

wr3mib –t [iterations polling_interval] –n systemNumber

DescriptionThe wr3mib command reads the SysMan and reports theinformation to stdout.

Arguments–f Prints all SysMan information.

–a Prints the SysMan alert table. Optional parameters for the–aargument include:

–C ClassSpecifies the alert class number to filter. For moreinformation, see “R/3 Alert Event Classes” onpage 180.

–S SeveritySpecifies the alert severity number (0 to 3) to filter.

–n systemNumberSpecifies the instance number to filter. The default isall systems.

–c Prints the SysMan configuration table.

–p Prints the SysMan performance table.


A.

Com

mand

LineInterface

Com

mands

–s Prints the SysMan system table.

–d Writes debug information to stderr.

–n systemNumberSpecifies the R/3 instance number. Only onesystemNumberis permitted.

–P PerfAttrSpecifies the performance attribute character (F = Frequency,R = Resp,W = Wait). The–T argument must be used withthis argument.

–T ServTypeSpecifies the performance attribute type number (1 fordialog,2 for update,3 for batch, or4 for spool).

–t iterations polling_delayPrints SysMan trap information, whereiterationsspecifiesthe number of times to query the SysMan andpolling_delayspecifies the amount of time between iterations. If you donot enter a value foriterations, the default is infinite. Youmust specify a value foriterations if you want to specify avalue forpolling_delay. The default forpolling_delayis 60seconds.


wr3rfcProvides remote execution of SAP R/3 function modules.

Synopsiswr3rfc [-d|-c|-u|-p|-l|-3|-2|-t|-h|-s|-g|-x|-D|-C|-?] rfc_interface[arg]...

DescriptionManager for R/3 includes a program that enables you to write simpleASCII control files to interface with R/3 RFC, rather than having towrite C programs to accomplish this task. This capability greatlysimplifies this task and reduces the time that is required to executeSAP modules from outside the SAP system.

The wr3rfc command reads two ASCII files: a configuration file andan rfc_interfacefile.

It is recommended that the configuration file contain only commandline arguments and therfc_interfacefile contain only stanza labelsand keywords.

The configuration file andrfc_interfacefile can specify any of thecommand line arguments for thewr3rfc command except thefollowing arguments:

¶ -D

¶ -C

¶ rfc_interfacefile

¶ [arg]

The wr3rfc command processes input in the following order:

1. configuration file

2. rfc_interfacefile

3. Command line

Duplicate values are overridden by the last instance that isencountered.


A.

Com

mand

LineInterface

Com

mands

The wr3rfc command uses information from therfc_interfacefile topopulate the appropriate data structures for the RFC API calls.

Notes:

1. A sample configuration file, wr3rfc_cfg.txt, is provided in one ofthe following directories:

¶ Managed node: $BINDIR/../generic_unix/TME/SAP/2.2C/rfc

¶ TMA endpoint:$LCF_BINDIR/../../generic_unix/TME/SAP/2.2C/rfc

Copy the wr3rfc_cfg.txt file to .wr3rfc_cfg and modify the.wr3rfc_cfg file for your unique processing requirements.

2. Spaces are allowed, but are not required in both command lineand configuration file entries. For example,-dparm is equivalentto -d parm andDESTINATION=PARM is equivalent toDESTINATION = PARM.

3. Blank lines are allowed.

4. Comments are indicated by a pound sign (#) in the first column.

5. For more information on configuring RFC values for remotefunction call parameters listed in the following table, see“Configuring User IDs for RFC Interface Access” on page 49.

The configuration file and command line interface allow any of thefollowing parameters:

CLIParameter

NameConfiguration File Parameter

Name Description

COMMAND OPTIONS: Indicates the start of stanzas.

–d DESTINATION= The 3-character R/3 system ID.

–c CLIENT= Specifies the 3-digit client sign-on data.

–u USER= Specifies the user ID.

–p PASSWORD= Specifies the unencrypted password.

–l LANGUAGE= Specifies the single-character languageidentifier. E is English.


CLIParameter

NameConfiguration File Parameter

Name Description

–2 or –3 MODE= CLI values are 2 or 3. The default is 3,which is R/3 mode. 2 specifies CPICmode. The MODE parameter value isalso 2 or 3.

–t TRACE= Controls tracing of an R/3 remotefunction call (RFC). YES turns tracingon. NO turns tracing off. The output ofthis trace is a file nameddev_rfc. Thefile is in the working directory of thewr3rfc program.

–h HOSTNAME= The target host. Enter a target host namesuch asmyhost.

–s SYSTEMNUMBER= Specifies the R/3 server instance number(00..96).

–g GATEWAYHOST= Specifies the gateway host. If the–gargument is not used, the–h argument isused.

–x GATEWAYSERVICE= Specifies the TCP/IP service of thegateway. The default issapgwNN, whereNN is the system number that is specifiedwith the –s argument.

–C Command line entry only. Specifies theconfiguration file. The default is./.wr3rfc_cfg.

–D Command line entry only. Specifies thedebug level:

1. High level processing

2. Lower level processing

3. Configuration file parsing

–? Command line entry only. Displays helpfor the wr3rfc command.

Stanzas in therfc_interfacefile include:


A.

Com

mand

LineInterface

Com

mands

Stanza Keywords Description

MODULE Required. This is the name of the R/3 functionmodule such as J_8C1_BUFFER_NAMES.

EXPORTPARAMETER:

Represents a stanza identifier. All export parameterstanzas should precede the first import parameter orimport table stanza.Note: The maximum number of export parametersyou can specify is 64.

NAME Defines a single field such as EXPORT1, sent tothe RFC program.

LENGTH The value of length is greater than or equal to thelength of the parameter to be exported to R/3. ForLENGTH of TYPX, LENGTH is equal to thenumber of characters entered. Every two charactersare converted to one byte for R/3.

VALUE Defines the value of the field being exported.

TYPE Specifies the data type of the NAME value.Allowable types include: [TYPC | TYPNUM |TYPX | TYPP | TYPINT | TYPINT1 | TYPINT2 |TYPFLOAT | TYPDATE | TYPTIME ].

IMPORTPARAMETER:

Represents a stanza identifier.Note: The maximum number of import parametersyou can specify is 64.

NAME Defines a single field such as IMPORT1, returnedfrom the RFC program.

TYPE Specifies the data type of the NAME value.Allowable types include: [TYPC | TYPNUM |TYPX | TYPP | TYPINT | TYPINT1 | TYPINT2 |TYPFLOAT | TYPDATE | TYPTIME ].

LENGTH Defines the length of the field being imported, suchas 250.

FORMAT Possible values are VERBOSE (print output in theform: keyword=value) or RESULT (print output inthe form: value).


Stanza Keywords Description

IMPORT TABLE: Stanza identifier:

1. IMPORT TABLE has to be the last stanza inthe command file.

2. Only one import table stanza is supported.Function modules that export multiple tables arenot supported by thewr3rfc program.

TABLENAME Defines the table such as IMPTA1, returned fromthe RFC program. This name must correspond tothe table name in the R/3 function module.

NAME Defines the name to represent a column field in thetable. Columns with different data types aresupported.

TYPE Defines the data type of the NAME value.Allowable types include: [TYPC | TYPNUM |TYPX | TYPP | TYPINT | TYPINT1 | TYPINT2 |TYPFLOAT | TYPDATE | TYPTIME ].

The CLNT data type in R/3 tables should beentered as TYPC in the cmd file.

LENGTH Specifies the length of the table column returnedfrom the RFC program, such as 250, with thefollowing rules:

1. LENGTH keyword is not needed for data typesTYPINT, TYPINT1, TYPINT2, TYPFLOAT,TYPDATE, and TYPTIME.

2. For LENGTH of TYPX, LENGTH equals thenumber of bytes of data. When displayed, eachbyte is represented as two characters.

ExamplesThe following example runs the command specified in theRfcFilecommand file on systemTV1 on SAP system number00 on hosttron:wr3rfc -h tron -d TV1 -s 00 RfcFile

This example uses the configuration file (./.wr3rfc_cfg):


A.

Com

mand

LineInterface

Com

mands

COMMAND OPTIONS:CLIENT = 000USER = SAP*PASSWORD = 06071992LANGUAGE = EMODE = 3TRACE = NO# These are for CPIC only#GATEWAYHOST = gatehost#GATEWAYSERVICE = sapgw00

This example uses therfc_interfacefile:COMMAND OPTIONS:MODULE = TH_WPINFOEXPORT PARAMETER:NAME = SRV_NAMETYPE = TYPCLENGTH = 20EXPORT PARAMETER:NAME = WITH_CPUTYPE = TYPXLENGTH = 1IMPORT TABLE:TABLENAME = WPLISTNAME = WP_NOTYPE = TYPCLENGTH = 2NAME = WP_ITYPETYPE = TYPCLENGTH = 3NAME = WP_PIDTYPE = TYPCLENGTH = 8NAME = WP_ISTATUSTYPE = TYPINT1NAME = WP_STATUSTYPE = TYPCLENGTH = 7NAME = WP_IWAITTYPE = TYPINT1NAME = WP_WAITINGTYPE = TYPCLENGTH = 5NAME = WP_SEMTYPE = TYPCLENGTH = 2NAME = WP_IRESTRTTYPE = TYPINT1NAME = WP_RESTART


TYPE = TYPCLENGTH = 4NAME = WP_DUMPSTYPE = TYPCLENGTH = 2NAME = WP_CPUTYPE = TYPCLENGTH = 8NAME = WP_ELTIMETYPE = TYPCLENGTH = 6NAME = WP_MANDTTYPE = TYPCLENGTH = 3NAME = WP_BNAMETYPE = TYPCLENGTH = 12NAME = WP_REPORTTYPE = TYPCLENGTH = 40NAME = WP_IACTIONTYPE = TYPINT1NAME = WP_ACTIONTYPE = TYPCLENGTH = 25NAME = WP_TABLETYPE = TYPCLENGTH = 30NAME = WP_SERVERTYPE = TYPCLENGTH = 20NAME = WP_WAITINFTYPE = TYPCLENGTH = 40NAME = WP_WAITTIMTYPE = TYPCLENGTH = 8


A.

Com

mand

LineInterface

Com

mands


Event Classes and Rules

This appendix contains information about the TEC event classesdelivered with Manager for R/3, new slot values for these events,and background information on R/3 alerts. It also containsinformation about the rules that Manager for R/3 provides.

Event ClassesManager for R/3 provides a set of TEC event classes. These eventclasses are categorized according to their origin and usage. Theevent classes that are provided are:

¶ R/3 Alert Event Classes

These event classes arise from alerts placed by R/3 onto itsSysMan interface. Events for these classes are generated by theAlert Event Adapter.

¶ R/3 Operational Event Classes

These event classes represent all the events that result from R/3SysMan events after drill-down processing is performed.

¶ R/3 Syslog Event Classes

These event classes represent events that result from processingthe R/3 syslog.

¶ R/3 IDOC Event Classes

These event classes represent events that result from processingR/3 IDOCs.

¶ Distributed Monitoring Event Classes

B


B.

Event

Classes

andR

ules

These event classes are associated with the Manager for R/3monitors.

¶ Special Event Classes

These event classes support internal Manager for R/3 processing.

R/3 Alert Event ClassesThese event classes correspond to alerts placed by R/3 on itsSysMan interface. R/3 identifies its alerts by an R/3 alert class. TheAlert Event Adapter reads R/3 alerts and converts them to TECevents of the appropriate event classes. Additional information onR/3 alerts is provided in “CCMS-Generated Alerts” on page 197.

The R/3 Alert Event Classes, the R/3 Alert Class, and a descriptionof the R/3 alert are described in the following table:

Event ClassR/3 Alert

Class Description

SAP_ALERT_StateChange 1 A change occurred in the operation mode ofthe R/3 system.

SAP_ALERT_SAPsysUp 2 The R/3 application server has been started.

SAP_ALERT_SAPsysDown 3 The R/3 application server has been stopped.

SAP_ALERT_SlogId 10 An alertable syslog message has beengenerated.

SAP_ALERT_SlogFreq 11 An excessive number of events have beenwritten to the R/3 syslog.

SAP_ALERT_Buf 12 An R/3 buffer problem has been detected.

SAP_ALERT_Enqueue 13 The enqueue table or its name directory isfilling up.

SAP_ALERT_Rollpag 14 Either the paging or roll area is overflowingto disk.

SAP_ALERT_Trace 15 Either an SQL or ABAP trace has beenturned on.

SAP_ALERT_DpQueue 16 The length of a dispatch queue has beenexceeded.

SAP_ALERT_PerfDia 20 A dialog work process has experiencedexcessive response time or excessive waittime.



Class Description

SAP_ALERT_PerfUpd 21 An update work process has experiencedexcessive response time or excessive waittime.

SAP_ALERT_PerfBtc 22 A batch work process has experiencedexcessive response time or excessive waittime.

SAP_ALERT_PerfSpo 23 A spool work process has experiencedexcessive response time or excessive waittime.

SAP_ALERT_AbapUpd 30 An error has occurred in an ABAP updateprocess.

SAP_ALERT_AbapErr 31 An error has occurred in an ABAP dialog orbackground process.

SAP_ALERT_AbapSql 32 An SQL error has occurred in an ABAPprogram, possibly indicating a databaseproblem.

SAP_ALERT_DbIndcs 41 A required index is missing in the database.This is triggered when a discrepancy isdetected during periodic comparison of thephysical database with the logical modelstored in R/3.

SAP_ALERT_DbFreSp 42 The database is filling up. This is triggeredbased on a periodic check and forecast of thegrowth rate.

SAP_ALERT_DbArcSt 43 There is not enough space in the databasearchive directory.

SAP_ALERT_DbBckup 44 Database backup alert.

SAP_ALERT_Spo 51 Spool alert.

SAP_ALERT_Arch 52 Archive alert.

SAP_ALERT_GenP3 53 Background task is off.

SAP_ALERT_GenP4 54 The application server profile in the profilesdirectory does not match the profile in thedatabase.

SAP_ALERT_GenP5 55 General alert class. No specific meaningidentified.


B.

Event

Classes

andR

ules


Class Description










SAP_ALERT_GenP15 65 For Oracle databases, optimizing statistics arenot being collected.

R/3 Operational Event ClassesR/3 Operational Event Classes represent the set of events that youmight see on the TEC console as a result of the Manager for R/3processing alerts from the R/3 SysMan interface. These eventscontain both the events from drill-down processing and the eventsfrom R/3 that do not require drill-down processing.

The following table describes these event classes (when the eventresults from drill-down processing, the description refers to theoriginal R/3 event):


Event Class Description

SAP_ALERT_ABAP_ERR This event results from drill-down ofSAP_ALERT_AbapErr.

SAP_ALERT_ABAP_SQL This event results from drill-down ofSAP_ALERT_AbapSql.

SAP_ALERT_ABAP_VB This event results from drill-down ofSAP_ALERT_AbapUpd.

SAP_ALERT_BUFF_CUA This event results from drill-down ofSAP_ALERT_Buf.

SAP_ALERT_BUFF_DBST This event results from drill-down ofSAP_ALERT_Buf.

SAP_ALERT_BUFF_FTAB This event results from drill-down ofSAP_ALERT_Buf.

SAP_ALERT_BUFF_IRBD This event results from drill-down ofSAP_ALERT_Buf.

SAP_ALERT_BUFF_PRES This event results from drill-down ofSAP_ALERT_Buf.

SAP_ALERT_BUFF_PXA This event results from drill-down ofSAP_ALERT_Buf.

SAP_ALERT_BUFF_SNTAB This event results from drill-down ofSAP_ALERT_Buf.

SAP_ALERT_BUFF_TABL This event results from drill-down ofSAP_ALERT_Buf.

SAP_ALERT_BUFF_TABLP This event results from drill-down ofSAP_ALERT_Buf.

SAP_ALERT_BUFF_TTAB This event results from drill-down ofSAP_ALERT_Buf.

SAP_ALERT_DB_ARCSTUCK This event results from drill-down ofSAP_ALERT_DbArcSt.

SAP_ALERT_DB_BACKUP This event results from drill-down ofSAP_ALERT_DbBckup.

SAP_ALERT_DB_FREESPC This event results from drill-down ofSAP_ALERT_DbFreSp.

SAP_ALERT_DB_INDICES This event results from drill-down ofSAP_ALERT_DbIndcs.


B.

Event

Classes

andR

ules


SAP_ALERT_DB_OPTMSTAT This event results from drill-down ofSAP_ALERT_GenP15.

SAP_ALERT_DPQU_BTC This event results from drill-down ofSAP_ALERT_DpQueue.

SAP_ALERT_DPQU_DIA This event results from drill-down ofSAP_ALERT_DpQueue.

SAP_ALERT_DPQU_ENQ This event results from drill-down ofSAP_ALERT_DpQueue.

SAP_ALERT_DPQU_SPO This event results from drill-down ofSAP_ALERT_DpQueue.

SAP_ALERT_DPQU_V2 This event results from drill-down ofSAP_ALERT_DpQueue.

SAP_ALERT_DPQU_VB This event results from drill-down ofSAP_ALERT_DpQueue.

SAP_ALERT_ENQU_ENQ This event results from drill-down ofSAP_ALERT_Enqueue.

SAP_ALERT_GENP_03 This event results from drill-down ofSAP_ALERT_GenP3. This event usually indicates thatSAPMSSYS_RSALSUP5 was disabled.

SAP_ALERT_GENP_04 This event results from drill-down ofSAP_ALERT_GenP4. This event usually indicates thata profile was not maintained.

SAP_ALERT_GENP_05 This event results from drill-down ofSAP_ALERT_GenP5.













SAP_ALERT_GENP_ARCH This event results from drill-down ofSAP_ALERT_Arch.

SAP_ALERT_GENP_SPO This event results from drill-down ofSAP_ALERT_Spo.

SAP_ALERT_OSCO_FILE Operating system file space threshold has beenexceeded.

SAP_ALERT_OSCO_LOAD Operating system load average thresholds have beenexceeded.

SAP_ALERT_OSCO_PAGE Operating system paging thresholds have beenexceeded.

SAP_ALERT_OSCO_SWAP Operating system swap thresholds have been exceeded.

SAP_ALERT_PERF_BTC This event results from drill-down ofSAP_ALERT_PerfBtc.

SAP_ALERT_PERF_DIA This event results from drill-down ofSAP_ALERT_PerfDia.

SAP_ALERT_PERF_ENQ Performance thresholds for the enqueue process havebeen exceeded.

SAP_ALERT_PERF_SPO This event results from drill-down ofSAP_ALERT_PerfSpo.

SAP_ALERT_PERF_V2 This event results from drill-down ofSAP_ALERT_PerfUpd.

SAP_ALERT_PERF_VB This event results from drill-down ofSAP_ALERT_PerfUpd.

SAP_ALERT_RLPG_PAG This event results from drill-down ofSAP_ALERT_Rollpag.


B.

Event

Classes

andR

ules


SAP_ALERT_RLPG_ROL This event results from drill-down ofSAP_ALERT_Rollpag.

SAP_ALERT_SAPsysDown This event comes directly from the Alert EventAdapter.

SAP_ALERT_SAPsysUp This event comes directly from the Alert EventAdapter.

SAP_ALERT_SLOG_FREQ This event results from drill-down ofSAP_ALERT_SlogFreq.

SAP_ALERT_SLOG_ID This event results from drill-down ofSAP_ALERT_SlogId.

SAP_ALERT_StateChange This event comes directly from Alert Event Adapter.

SAP_ALERT_TRSW_TRSW This event results from drill-down ofSAP_ALERT_Trace.

R/3 Syslog Event ClassesR/3 syslog event classes represent events from processing the R/3syslog. SAP_SYSLOG is a superclass definition for all syslog eventclasses. Syslog event classes have the following format:SAP_SYSLOG_MsgID, whereMsgID is the three-character messageID of the syslog message that generated the event. Syslog eventclasses are provided for all syslog events provided in thetecad_wr3slog.cl file, whether or not the events are sent to TEC. See“Using the Syslog Event Adapter” on page 91.

The following table describes the syslog event classes:

Event Class Syslog Message

SAP_SYSLOG_A05 No memory available.

SAP_SYSLOG_A07 Timeout.

SAP_SYSLOG_A08 Main memory destroyed.

SAP_SYSLOG_AB0 Run time error $$$$.

SAP_SYSLOG_AB1 Short dump $$$$ generated for error $$$$.

SAP_SYSLOG_B15 Memory area too small.



SAP_SYSLOG_B24 No memory available for table $$$$ in the tablebuffer.

SAP_SYSLOG_B33 Inconsistency in table $$$$ in DB interface.

SAP_SYSLOG_BB2 Inconsistent buffer &5&5.

SAP_SYSLOG_BS2 The synchronization module cannot allocate temporaryauxiliary memory.

SAP_SYSLOG_BV3 SQL error &5 occurred (poss. network pros.?) Workprocess is stopped.

SAP_SYSLOG_BV4 Work process is in reconnect status.

SAP_SYSLOG_BY1 DB error &5.

SAP_SYSLOG_BY2 Database &6 for &3.

SAP_SYSLOG_BY3 DB error &6 accessing table &5&5.

SAP_SYSLOG_BY4 DB error &6 at &3 access to table &5&5.

SAP_SYSLOG_BYL Database error &5 requires intervention by thedatabase administrator.

SAP_SYSLOG_BYM SQL error &5 (possibly a network error); WP inreconnect status.

SAP_SYSLOG_BYO Deadlock occurred.

SAP_SYSLOG_BZ7 Storage request (&5&5 bytes) is too small for therecord (&5&5 bytes).

SAP_SYSLOG_BZ8 Output buffer (&5&5 bytes) is too small for the record(&5&5 bytes).

SAP_SYSLOG_BZW Error &5 during compression/decompression (&5&5).

SAP_SYSLOG_D01 Transaction termination &5 (&a &b &c &d &e &f &g &h&i).

SAP_SYSLOG_E11 Buffer &8 could not be generated.

SAP_SYSLOG_EAA Failed to open log partition.

SAP_SYSLOG_EAS Failed to reschedule a periodic job.

SAP_SYSLOG_EAW Failed to initiate start of job $$$$.

SAP_SYSLOG_EAY Failed to read status entry for job $$$$.

SAP_SYSLOG_EAZ Failed to maintain status entry for job $$$$.

SAP_SYSLOG_EB3 Failed to start a subsequent job for job $$$$.


B.

Event

Classes

andR

ules


SAP_SYSLOG_EBF Failed to activate authorization check for user $$$$.

SAP_SYSLOG_EBG Job $$$$ was not started.

SAP_SYSLOG_EBH Cause: Preceding job $$$$ was cancelled.

SAP_SYSLOG_EBI Error scheduling a batch job.

SAP_SYSLOG_ED6 No SAP system is currently active on computer $$$$.

SAP_SYSLOG_F3U Database I/O error.

SAP_SYSLOG_F4B Not enough $$$$ memory for $$$$ block.

SAP_SYSLOG_F5O Unable to connect to database.

SAP_SYSLOG_F6H Database error: TemSe –>&B(&C)–> for table &D key &a.

SAP_SYSLOG_F7U Spool: Database access error: db_rsql $$$$ for table$$$$.

SAP_SYSLOG_F7Y Spool: Database is inconsistent.

SAP_SYSLOG_F8M Cannot send data to printer.

SAP_SYSLOG_F8X Commit to data base failed.

SAP_SYSLOG_FAI Insufficient main memory.

SAP_SYSLOG_FAJ Internal error in spool work process.

SAP_SYSLOG_FAP Spool inconsistency: Field &A does not match field &B.

SAP_SYSLOG_FBA Version of shared memory is incorrect (Spooladministration).

SAP_SYSLOG_FBB Spool component is not ready.

SAP_SYSLOG_FBI Internal error in Spool, Code &A, arg1=&B, arg2=&C,arg3=&D.

SAP_SYSLOG_FBJ db_rtab_error at table &A, error &B.

SAP_SYSLOG_FBN Spool is full!

SAP_SYSLOG_FCC Inconsistency found in calendar buffer, buffer &5&5reset.

SAP_SYSLOG_GE0 GC0 ... GDZ reserved for CCMS.

SAP_SYSLOG_GEA Internal lock administration error.

SAP_SYSLOG_GEG Lock table overflow.

SAP_SYSLOG_GEI Enqueue: Initialization error.

SAP_SYSLOG_GH0 Error in central lock handler.



SAP_SYSLOG_GI0 Error calling the central lock handler.

SAP_SYSLOG_GI6 Central lock handler can be accessed again.

SAP_SYSLOG_P00 Failed to open roll file $$$$.

SAP_SYSLOG_P05 Memory request (malloc) failed.

SAP_SYSLOG_P0B Paging file overflow ($$$$ blocks).

SAP_SYSLOG_Q0E Signal $$$$ received by operating system.

SAP_SYSLOG_Q0M Message server disconnected.

SAP_SYSLOG_Q0N Failed to send a request to the message server.

SAP_SYSLOG_Q18 Work process $$ exclusively locked by user $$$$.

SAP_SYSLOG_R00 Failed to lock semaphore $$$, RC=$$$.

SAP_SYSLOG_R05 No active session available.

SAP_SYSLOG_R0N Insufficient dialog work processes for number rangebuffer.

SAP_SYSLOG_R0O No active update server available.

SAP_SYSLOG_R0R The connection was deactivated after a DB error.

SAP_SYSLOG_R0S The update was manually deactivated.

SAP_SYSLOG_R18 SAP commit failed.

SAP_SYSLOG_R1A $$$ logon failed.

SAP_SYSLOG_R20 Insufficient shared memory.

SAP_SYSLOG_R22 SAPASRV failed, OP=$$, return code $$$.

SAP_SYSLOG_R29 No shared memory available.

SAP_SYSLOG_R2B No storage for $$$$.

SAP_SYSLOG_R33 RSTG chain defective, return code $$$.

SAP_SYSLOG_R38 Error at DB commit, return code $$$$.

SAP_SYSLOG_R3C Maximum no. users $$$$ reached.

SAP_SYSLOG_R44 RSTS: Rollout failed, return code $$$.

SAP_SYSLOG_R45 Shared memory destroyed.

SAP_SYSLOG_R65 Update terminated.

SAP_SYSLOG_S05 Profile error, return code $$$.

SAP_SYSLOG_S07 Failed to create shared tables.


B.

Event

Classes

andR

ules


SAP_SYSLOG_S0B Maximum no. $$$$ of requests per CPI-C connectionreached.

SAP_SYSLOG_S10 Service initialization failed.

SAP_SYSLOG_S1F Initialization $$$$ failed.

SAP_SYSLOG_S8D Maximum no. $$$$ of connections reached.

SAP_SYSLOG_SK0 SAPcomm: Error.

SAP_SYSLOG_SK3 Error (&A) at status update (spool open &B &C &D &E).

SAP_SYSLOG_ST0 No free memory available in class $$$$.

SAP_SYSLOG_US1 User $$$$ locked due to incorrect logon.

SAP_SYSLOG_US2 User SAP* was deleted by user $$$$.

SAP_SYSLOG_US3 Logon attempt for locked user $$$$.

SAP_SYSLOG_US4 Maximum number of users reached.

SAP_SYSLOG_US6 User buffer is too small for user $$$$.

R/3 IDOC Event ClassesR/3 IDOC event classes, which are described in the following table,represent events from processing IDOCs.

The SAP_IDOC_STATUS event class conveys information aboutspecific IDOCs and IDOC status codes. This event class is designedas a leaf class of the SAP_IDOC event class, which contains all theevent slot definitions. If you need to create specific IDOC eventclasses by status code, you should create event classes of the formSAP_IDOC_xx, wherexx is the two-digit status code. These eventclasses should be leaf classes of the SAP_IDOC event class.


SAP_IDOC_STATISTICS This event is generated when the number ofIDOC events to be sent to TEC reaches the 500limit, when enabled.

SAP_IDOC_STATUS This event is generated for IDOCs that havechanged status since the last polling cycle.



SAP_IDOC_XMIT This event is generated when IDOC transmissionfails due to an ALE/RFC communicationproblem.

Distributed Monitoring Event ClassesEach monitoring source contained in the Manager for R/3 monitoringcollections has an associated event class. These event classes areused when TEC events are generated automatically from receivedDistributed Monitoring monitors. These event classes and theirassociated monitoring sources are listed in the following table:

Event Class Monitoring Source

BATCH_SERVICE_MONITOR Batch Performance

DIALOG_SERVICE_MONITOR Dialog Performance

FIELD_DESC_BUFFER_MONITOR FTAB Field Catalog Buffer

GENERIC_KEY_BUFFER_MONITOR TABL Generic Key Buffer

INITIAL_RECORDS_BUFFER_MONITOR IRBD Initial Records Buffer

LONG_RUNNING_PROCESS_MONITOR Long running process

MENU_BUFFER_MONITOR CUA Menu and Text Buffer

OS_COLLECT_APSRVR_MONITOR OS Collect - Application Server

OS_COLLECT_DBSRVR_MONITOR OS Collect - Database Server

OS390_COLLECT_MONITOR OS/390

OS390_DB2_MONITOR OS/390 DB2

PAGE_AREA_MONITOR Page Area

PROGRAM_BUFFER_MONITOR PXA Program Buffer

ROLL_AREA_MONITOR Roll Area

SAP_CANCELLED_JOB_MONITOR Cancelled Job

SAP_EXTENDED_MEMORY_MONITOR Extended Memory

SAP_FILESYSTEM_MONITOR R3 UNIX File Systems and R3Windows NT File Systemsmonitoring sources

SAP_HEAP_MEMORY_MONITOR Heap Memory

SAP_USER_MONITOR User


B.

Event

Classes

andR

ules

Event Class Monitoring Source

SCREEN_BUFFER_MONITOR PRES Screen and DynproBuffer

SHORT_NTAB_BUFFER_MONITOR SNTAB Short NameTab Buffer

SINGLE_RECORD_BUFFER_MONITOR TABLP Single Key Buffer

SPOOL_SERVICE_MONITOR Spool Performance

TABLE_DEF_BUFFER_MONITOR TTAB Table Description Buffer

UPDATE_SERVICE_MONITOR Update Performance

WORK_PROCESS_DISPATCH_QUEUE_MONITOR Work process dispatch queue

WORK_PROCESS_MONITOR Work process

Status Event ClassesThe status event classes are described in the following table:


APSRVR_STATUS_MONITOR This event is generated when applicationserver status changes.

SAP_DAEMON_MONITOR This event is generated when message serverstatus changes.

SAP_ITS_STATUS_MONITOR This event is generated when ITS serverstatus changes.

Tivoli GEM Instrumentation Event ClassesThe Tivoli GEM instrumentation event classes are described in thefollowing table:


SAP_APM_HEARTBEAT This event is generated when an R/3 objectis created.

SAP_APM_THRESHOLD This event is generated when the status of anR/3 database server or R/3 ITS serverchanges.

Tivoli GEM Event ClassesThe Tivoli GEM event classes are described in the following table:



APM_HEARTBEAT This event is generated when an R/3 objectis created.

APM_THRESHOLD This event is generated when a Manager forR/3 monitor exceeds the threshold.

Error Event ClassesThe error event classes support internal Manager for R/3 processing.These event classes and their descriptions are listed in the followingtable:


AMS_WR3MIB_PROCESS_ALERT This event is generated whenever the alertcontrol or alert reader routines encounter anerror.

R3MGR_RFC_ERROR_IDOC This event results from a communicationerror between the IDOC Event Adapter andthe R/3 system.

SAP_SYSLOG_RFC_ERROR This event results from a communicationerror between the Syslog Event Adapter andthe R/3 system.

Alert Event SlotsThe Manager for R/3 event classes listed under R/3 Alert EventClasses, R/3 Operational Event Classes, and the event classAMS_WR3MIB_PROCESS_ALERT contain a set of slots thatcontain information pertinent to the R/3 server being monitored.These slot values are available for use in TEC rules. The followingtable describes the event slots:

Slot Description

r3alertActionString A text string that contains an R/3 recommended actionfor the alert. Typically, this slot contains a logonstring by which an administrator can launch aSAPGUI session to the affected application server.


B.

Event

Classes

andR

ules

Slot Description

r3alertAgentHostName The name of the host on which the alert occurred.Typically, database alerts are generated by R/3instances that are not necessarily run on the databasehost.

r3alertClass The numeric value used by SAP to identify the alerton the SysMan interface.

r3alertMsgString A text string from R/3 that provides more descriptiveinformation for the alert.

r3alertNumber The alert number as presented by R/3.

r3alertSapName The SID of the R/3 system in which the alert wasgenerated.

r3alertSeverity The severity of the alert, as reported by R/3.

r3alertSystemNumber The application server instance number.

r3alertTimeStamp The timestamp of the alert, as reported by R/3. Thetimestamp is in UTC format (number of secondselapsed since 1970).

r3configDBHostName The host name of the database server for this R/3system.

r3configDBName The SID of the R/3 system in which the alert wasgenerated.

r3configInstanceNameString The application server profile name; for example,DVEBMGS30.

Syslog Event SlotsThe Manager for R/3 event classes described in “R/3 Syslog EventClasses” on page 186 contain a set of event slots that provideinformation about the syslog event. The following table describesthese event slots:

Event Slot Description

r3syslogMsgNumber The three-character message ID from the syslog.

r3syslogDate The date that the message was written in the syslog.

r3syslogTime The time that the message was written in the syslog.



r3syslogInstanceName The hostname_SID_IID of the R/3 application server.

r3syslogTask The R/3 task running that is associated with the messagethat was written in the syslog.

r3syslogClient The three-digit client number associated with the syslogmessage.

r3syslogUser The R/3 user ID associated with the syslog message.

r3syslogTxCode The R/3 transaction code associated with the syslogmessage.

r3syslogMsgText A text string that provides more descriptive informationabout the syslog entry.

IDOC Event SlotsThe Manager for R/3 event classes described in “R/3 IDOC EventClasses” on page 190 contain a set of event slots that provideinformation about the IDOC event. The following table describes theevent slots for the SAP_IDOC event class:


msg The concatenated values of the r3idocStatus,r3messageType, r3partnerNumber, and r3idocMsg eventslots.

r3client The three-digit R/3 client number.

r3idocMsg A text string that contains the IDOC message. This slotcontains information from the R/3 fields STAPA1 throughSTAPA4.Note: The combination of the R/3 fields STAPA1through STAPA4 can generate a maximum string lengthof 270 characters. Because TEC limits this event slot to amaximum of 255 characters, the R/3 information can betruncated in some circumstances.

r3idocNum The 16-digit R/3 IDOC number.

r3idocStatus The two-digit R/3 IDOC status code.

r3idocStacod The eight-character R/3 IDOC status code.


B.

Event

Classes

andR

ules


r3idocDirection A one-character field that indicates whether the IDOCwas inbound or outbound in this R/3 system; 1 =outbound, 2 = inbound.

r3partnerNumber The logical system identifier of the R/3 system to whichthis R/3 system is communicating.

r3messageType The six-character IDOC message type.

r3senderIdocNum The 16-digit IDOC number of the sending R/3 system.

The following table describes the event slots for theSAP_IDOC_XMIT event class:


r3logicalDestination The logical system identifier of the R/3 system to whichthis R/3 system is communicating.

r3intTotal The total number of IDOCs processed to this destination inthe last polling cycle.

r3intFailed The number of failed IDOCs processed to this destinationin the last polling interval.

r3intFailedRatio The two-digit integer representing the percentage of failedIDOC transmissions in the last polling interval.

r324hTotal The total number of IDOCs processed to this destination inthe last 24-hour period.

r324hFailed The total number of failed IDOCs processed to thisdestination in the last 24-hour period.

r324hFailedRatio The two-digit integer representing the percentage of failedIDOC transmissions to this destination in the last 24-hourperiod.

Cancelled Job Event SlotsThe SAP_CANCELLED_JOB_MONITOR event class contains a setof slots that contain information pertinent to the cancelled R/3 job.The following table describes these event slots:



r3JobName The name of the cancelled R/3 job.

r3JobID The ID associated with the cancelled R/3 job.

r3JobDate The date that the R/3 job was scheduled.

CCMS-Generated AlertsThe Computing Center Management System (CCMS) monitors theR/3 application, the operating system, and the database. The R/3alert monitors operate from a set of predefined thresholds, some ofwhich are user-configurable. The thresholds refer to a 15-minuterunning average of the values. CCMS also generates alerts forabends in ABAP/4 programs and for messages written to the syslog.Additionally, application programs can report an alert in ageneral-purpose class using an API.

The following alerts can be generated from CCMS:

¶ Operating System Alerts

v CPU load

– User/System/Idle time: SAP recommends configuringalerts for system CPU time greater than 10% to 20%(probable swapping) and idle CPU time at 0% (probablelooping program).

– Load Average (1-, 5- and 15-minute averages): SAPrecommends configuring alerts for a load average of morethan 3 processes in the run queue (probable CPUbottleneck).

v Memory utilization

– Physical memory free/available: SAP recommendsconfiguring alerts for less than 10 MB of physicalmemory free.

– Pages out: SAP recommends configuring alerts for morethan zero pages swapped out per second.


B.

Event

Classes

andR

ules

v Swap utilization

– Available swap space: A critical alert is generated whenthere is no swap space available.

Note: Operating system alerts do not actually cause traps tobe generated by the R/3 SysMan interface. However,the Manager for R/3 does forward key operatingsystem events to the TEC event server.

¶ Database Alerts

v Missing indices: An alert is generated when a missing indexis detected. This is done through a periodic comparison of thephysical database schema with the logical data model that isstored in R/3.

v Database free space: Free space is checked on tablespacesand dbspaces and an alert is generated when these spaces arefilling. The R/3 system maintains a growth history and canpredict the growth rate based on this history.

v Database log directory: An alert is generated when there isinsufficient space to archive the database.

¶ R/3 Alerts

v Response time: This applies to dialog processes and refers tothe time between when a dialog step is received by R/3 andwhen a response is returned. Because dialog processes use anasynchronous update model, the response time should befairly consistent across a broad mix of transaction types.

v Wait time: This refers to the time that a request waits in thedispatcher queue for an available work process to service it.On average, wait time should be less than 1% of responsetime for a transaction. A high wait time indicates that notenough work processes are available or that the system isoverloaded. Response- and wait-time thresholds can beseparately configured for each instance of an applicationserver.


v Enqueue management table: The enqueue table (used formanaging locks) is kept in memory. If the enqueue table fillsup, the system can no longer set any locks and a critical alertis generated.

v System log messages: Messages that are written to syslog byR/3 can generate alerts. It is possible to specify filters thatindicate which messages, based on the message ID, shouldgenerate alerts and which messages should not generatealerts.

v Buffers: Alerts are generated if the directory of objects storedin the buffer becomes too full, if there is insufficient freespace in a buffer, or if the quality of a buffer is too low.

v Roll/Paging: The roll buffer stores the user runtimeenvironment between processing periods in a work process. Ifthe roll buffer becomes full, an alert is generated and the userruntime environment will have to be rolled to a file. If thepaging area becomes full, a file is allocated for paging. Theseevent trigger critical alerts when the roll buffer or page areais 95% full.

v Trace: If tracing is turned on, it generates an alert to indicatea performance degradation.

Rules for Manager for R/3 EventsThe TEC includes a rules engine that processes events according to aset of rules that are provided by Tivoli products or added by users.Manager for R/3 supplies a default rule base, which is a set of rulesthat provides correlation of related events and gives automatedresponses where possible. You can extend these rules by writingrules that are tailored for your installation. Refer to theTME 10Enterprise Console Rule Builder’s Guide.

Manager for R/3 rules provide these functions:

¶ Duplicate event checking

¶ Automatic closing of harmless events

¶ Automatic drill-down


B.

Event

Classes

andR

ules

¶ Bidirectional communication

¶ Event correlation

¶ Multi-region support

¶ Integration with Tivoli GEM


Duplicate Event CheckingBy design, the R/3 SysMan, and therefore the R/3 alert eventadapter, generates an event only when one of the alert classeschanges from one state to another (for example, from green toyellow or from yellow to red). An event is also generated when analert class decreases in severity (for example, from yellow to green),either when the administrator resets the alert from the CCMS AlertMonitor or when the condition corrects itself.

Manager for R/3 provides a rule that automatically closes duplicateevents when a new event is received, which is effective for all of theR/3 alert classes. A duplicate event is defined as an event of thesame event class in which designated slot values are identical.

Automatic Closing of Harmless EventsTypically, TEC users do not want the TEC console populated withharmless events. However, it is valuable to display a harmless eventfor a period of time when the event is generated as a result of aself-correcting condition. To permit this, a rule is provided thatautomatically closes harmless R/3 alerts after 60 seconds.

Automatic Drill-DownWhen the TEC event server rule base receives certain R/3 SysManevents, it automatically runs an R/3 function module through theRFC interface. The R/3 function module obtains additional and morespecific internal CCMS information about the alert. For example,when the TEC event server receives the R/3 SysMan buffer alert, itautomatically runs a special function module supplied with Managerfor R/3 to identify the specific buffer that is having a problem.


Bidirectional CommunicationBy converting R/3 alerts into R/3 internal alerts, the TEC eventserver rule base can use the RFC interface to control R/3 alerts fromthe TEC. For example, closing or acknowledging an R/3 internalalert from the TEC automatically causes the R/3 alert to be reset oracknowledged in the appropriate R/3 application server.

Event CorrelationThe TEC event server rule base correlates certain types of eventsand takes the appropriate action. For example, the TEC event serverrule base automatically resets R/3 buffer alerts for 35 minutes afterreceiving an R/3 state change event. Event correlation relieves theadministrator from handling expected buffer quality alerts during thestate transition.

Another example is the ability to identify when an R/3 serverbecomes unavailable and to automatically drop events that are nolonger relevant. When a monitored server initially fails, many eventsthat are indicative of the server failure can arrive and can causeevent flooding at a console. When a server is offline, eventcorrelation can associate subsequent events related to that server andcan discard them as not relevant. Event correlation helps to removethese events and alleviate such flooding situations.

Multi-Region SupportOptionally, you can use the TEC event server rule base to forwardevents from multiple TMRs. Then, a single administrator canmonitor a large number of R/3 systems in different TMRs.

Integration with Tivoli GEMOptionally, you can manage R/3 resources from the Tivoli GEMconsole (see “Tivoli GEM Instrumentation” on page 147). Managerfor R/3 provides rules that forward Manager for R/3 monitor eventsto the Tivoli GEM server and synchronize the Tivoli GEM consolewith the Manager for R/3 objects on the desktop.

Integration with Tivoli Database Manager ProductsIf you have the Tivoli Manager for DB2 or Tivoli Manager forOracle installed, you can optionally extend database status reporting


B.

Event

Classes

andR

ules

(see “Extending Database Server Status Reporting” on page 78).Manager for R/3 provides rules that set the status of the databaseserver from the Tivoli Manager for DB2 or Tivoli Manager forOracle database status event.

TEC Event Server RulesThe sap_tecad.rls file contains the following TEC event server rules:

Rule Name Description

ack_sap_alert Acknowledges R/3 alerts when the correspondingevents are acknowledged.

close_sap_alert Closes R/3 alerts when the corresponding events areclosed.

convert_mib_to_internal_alert Performs drill-down event processing. When the TECevent server receives certain R/3 SysMan events, theR/3 function module obtains more detailed eventinformation. The original event is closed, and only thedrill-down event is displayed.

drop_new_harmless Immediately closes internal harmless events andharmless R/3 application server monitor events.

drop_r3mgr_rfc_error_idoc_event Removes the IDOC RFC error event when an IDOCevent is received.

dup_all_sap_idoc_event Removes duplicate IDOC events.

dup_r3mgr_rfc_error_event Removes duplicate IDOC RFC error events and keepsthe original RFC error event.

dup_sap_event Removes duplicate events.

forward_sap_events Forwards events to an alternate TEC event server.

harmless_set_timer Sets a timer on each harmless event. The timer is setto 60 seconds. A timer rule will close the event whenthe timer expires.

harmless_still_open Closes harmless events after 60 seconds.

reset_certain_events_on_statechange Discards buffer alerts when they occur within 35minutes of an R/3 operational mode switch.

reset_syslog_alert Immediately resets syslog events.

sapsysdown_clone_appstatus_event Creates an event of classAPSRVR_STATUS_MONITOR when an applicationserver’s status is down.



sapsysup_clone_appstatus_event Creates an event of classAPSRVR_STATUS_MONITOR when an applicationserver’s status is up.

sapsysup_read_all_internal_alerts Gets all existing R/3 alerts when an applicationserver’s status changes from down to up.

Distributed Monitoring RulesThe sap_monitor.rls file contains the following monitor rules:


ack_sap_sentry_alert Closes duplicate events corresponding to anacknowledged event.

close_sap_sentry_alert Closes duplicate events corresponding to a closedevent.

drop_sentry_events_on_sentry_sysup Removes events that occur within 35 minutes of anR/3 application server coming up.

dup_its_down Closes duplicate ITS server status down events.

dup_its_up Closes duplicate ITS server status up events.

dup_sap_cancelled_job_event Removes duplicate cancelled job events.

dup_sap_its_down Locates duplicate ITS server status down events,increments the count on the existing event, andremoves the received event.

dup_sap_its_up Locates duplicate ITS server status up events,increments the count on the existing event, andremoves the received event.

dup_sap_monitor_event Removes duplicate events.

dup_sap_system_down Removes duplicate R/3 application server statusdown events.

dup_sap_system_up Removes duplicate R/3 application server status upevents.

sap_extract_job1 Assigns the name of the cancelled job to theR3JobName event slot and the ID of the cancelledjob to the R3JobID event slot.

sap_extract_job2 Assigns the date that the job was scheduled to theR3JobDate event slot.


B.

Event

Classes

andR

ules


sap_system_down Closes all outstanding open events for an applicationserver when the R/3 application server status changesfrom up to down.

sap_system_up Closes all outstanding open events for an applicationserver when the application server status changesfrom down to up.

sap_system_down_no_more_sentries Removes events when the corresponding R/3application server is down.

sentry_daemon_or_application_down Closes all outstanding open events when the status ofthe Distributed Monitoring application changes fromup to down.

sentry_daemon_or_application_up Closes all outstanding open events when the status ofthe Distributed Monitoring application changes fromdown to up.

sentry_host_down Closes all outstanding open events when the status ofthe Distributed Monitoring host machine changesfrom up to down.

sentry_host_up Closes all outstanding open events when the status ofthe Distributed Monitoring host machine changesfrom down to up.

set_r3sapname_slot Assigns the value of the R/3 system label to thesub_source event slot and assigns the value of theR/3 application server name to the sub_origin eventslot.

Database Status Integration RulesThe sap_mgr_db2.rls file contains the following rule:


db2_status_event Sets the status of the database server from the Managerfor DB2 database status event.

The sap_mgr_oracle.rls file contains the following rule:



oracle_status_event Sets the status of the database server from theManager for Oracle database status event.

Correlation RuleThe sap_default.rls file contains the following correlation rule:


drop_sentry_events_on_statechange Removes Distributed Monitoring events when theyoccur within 35 minutes of the R/3 application serverstatus changing from down to up.

Tivoli GEM Instrumentation Distributed MonitoringRules

The sap_gemevents.rls file contains the following rules forprocessing events that are sent from the Manager for R/3 monitors:


r3_gemevents_rule1 Forwards Manager for R/3 monitor events to the TivoliGEM server.

r3_gemevents_rule2 Forwards R/3 application server status events to the TivoliGEM server.

r3_gemevents_rule3 Changes the SAP_APM_HEARTBEAT event to theAPM_HEARTBEAT event and forwards the event to theTivoli GEM server.

r3_gemevents_rule4 Changes the SAP_APM_THRESHOLD event to theAPM_THRESHOLD event and forwards the event to theTivoli GEM server.


B.

Event

Classes

andR

ules


Remote and Central MonitoringSources

This appendix describes the monitoring sources and attributescontained in the R3 Server Remote Monitors and the R3 ServerCentral Monitors collections.

The table headings have the following meanings:

AttributeDescription of the monitor as initially seen when creating amonitor.

KeywordDescription of the monitor after it has been configured.

R/3 ReferenceA mapping of the monitored value to its R/3 equivalent. Thereference is expressed as a transaction name / grouping name(optional) / field name. If there is no direct R/3 equivalent,this column explains how the field is derived or what itmeans.

Note: The Application Server Status, ITS Server Status, and theCancelled Job monitoring sources do not have attributes.

C


C.

Rem

oteand

Central

Monitoring

Sources

OS Collect SourceThe OS Collect Application Server and OS Collect Database Serversources include the following attributes and their keywordequivalents:

Attribute Keyword R/3 Reference

CPU Utilization user(%)

USER_CPU_UTIL st06 / CPU utilization user %

CPU Utilizationsystem (%)

SYSTEM_CPU_UTIL st06 / CPU utilization system %

CPU Utilization idle(%)

IDLE_CPU_UTIL st06 / CPU utilization idle %

System Calls persecond

SYSTEM_CALLS_SEC st06 / System calls/sec

Interrupts per second INTERRUPTS_SEC st06 / Interrupts/sec

Number of CPUs NUMBER_CPUS st06 / Count

Load Average (1 min) LOAD1_AVG st06 / Load average 1 min(rounded)

Load Average (5 min) LOAD5_AVG st06 / Load average 5 min(rounded)

Load Average (15min)

LOAD15_AVG st06 / Load average 15 min(rounded)

Context switches persecond

CONTEXT_SWITCH_SEC st06 / Context switches/sec

Physical Memory PHYSICAL_MEMORY st06 / Physical mem avail kb

Physical Memory FreeFREE_MEMORY st06 / Physical mem free kb

Pages in per second PAGE_INS_SEC st06 / Pages in/sec

Pages out per secondPAGE_OUTS_SEC st06 / Pages out/sec

Kilobytes paged inper second

KB_PAGED_IN_SEC st06 / Kb paged in/sec

Kilobytes paged outper second

KB_PAGED_OUT_SEC st06 / Kb paged out/sec

Configured swapspace size

CONFIG_SWAP st06 / Configured swap kb

Free swap space FREE_SWAP st06 / Free in swap-space kb



Maximum swap spaceMAX_SWAP st06 / Maximum swap-space kb

Actual swap spacesize

SIZE_SWAP st06 / Actual swap-space kb

Disk utilization (%) DISK_UTILIZATION st06 / Disk Utilization

Disk average waittime

DISK_WAIT_TIME st06 / Disk Avg wait time ms

Disk kilobytestransferred per second

DISK_DATA_TRANSFER_SEC st06 / Disk Kb transferred/sec

Disk response time DISK_RESPONSE_TIME st06 / Disk Response time ms

Disk average queuelength

DISK_QUEUE_LENGTH st06 / Disk Queue

Disk average servicetime

DISK_SERVICE_TIME st06 / Disk Avg service time ms

Disk operations persecond

DISK_OPERATIONS_SEC st06 / Disk Operations/sec

LAN packets in persecond

LAN_PACKETS_IN_SEC LAN Packets in/sec

LAN packets out persecond

LAN_PACKETS_OUT_SEC LAN Packets out/sec

LAN collisions persecond

LAN_COLLISIONS_SEC LAN Collisions

LAN packet in errorsper second

LAN_PACKET_IN_ERRORS_SEC LAN Errors in/sec

LAN packet out errorsper second

LAN_PACKET_OUT_ERRORS_SEC LAN Errors out/sec

Note: Disk values apply to the disk with the highest response time at the last samplingperiod.

Roll Area SourceThe Roll Area source includes the following attributes and theirkeyword equivalents:


C.

Rem

oteand

Central

Monitoring

Sources


Roll Area FreeSpace

ROLL_AREA_FREE Not directly available.ROLL_AREA_SIZE minusROLL_CURRENTLY_USED

Roll Area PercentFree

ROLL_AREA_PERCENT_FREE Not directly available.ROLL_AREA_FREE divided byROLL_AREA_SIZE

Roll Area SharedMemory

ROLL_AREA_SHARED_MEMORY st02 / Roll area / In memory (Kb)

Roll Area Size ROLL_AREA_SIZE Not directly available. Total sizeof roll area

Roll CurrentlyUsed

ROLL_CURRENTLY_USED st02 / Roll area / Current use (Kb)

Roll Area PercentUsed

ROLL_AREA_PERCENT_USED Not directly available.ROLL_AREA_USED divided byROLL_AREA_SIZE.

Roll File Size ROLL_FILE_SIZE st02 / Roll area / On disk (Kb)

Roll Max Used ROLL_MAX_USED st02 / Roll area / Max. use (Kb)

Roll Max %Used

ROLL_MAX_PERCENT_USED Not directly available.ROLL_MAX_USED divided byROLL_AREA_SIZE

Page Area SourceThe Page Area source includes the following attributes and theirkeyword equivalents:


Page Area Free SpacePAGE_AREA_FREE Not directly available.PAGE_AREA_SIZE minusPAGE_CURRENTLY_USED

Page Area PercentFree

PAGE_AREA_PERCENT_FREE Not directly available.PAGE_AREA_FREE divided byPAGE_AREA_SIZE

Page Area SharedMemory

PAGE_AREA_SHARED_MEMORY st02 / Paging area / In memory(Kb)



Page Area Size PAGE_AREA_SIZE Not directly available. Total sizeof page area.

Page Currently Used PAGE_CURRENTLY_USED st02 / Page area / Current use(Kb)

Page Area PercentUsed

PAGE_AREA_PERCENT_USED Not directly available.PAGE_AREA_USED divided byPAGE_AREA_SIZE

Page File Size PAGING_FILE_SIZE st02 / Page area / On disk (Kb)

Page Max Used PAGE_MAX_USED st02 / Page area / Max. use (Kb)

Page Max % Used PAGE_MAX_PERCENT_USED Not directly available.PAGE_MAX_USED divided byPAGE_AREA_SIZE

Work Process SourceThe Work Process source includes the following attributes and theirkeyword equivalents:

Attribute 1 Keyword R/3 Reference

All All sm50 / Type

Dialog Dialog sm50 / Type

Update Update sm50 / Type

Update2 Update2 sm50 / Type

Batch Batch sm50 / Type

Spool Spool sm50 / Type

Enqueue Enqueue sm50 / Type


Free Free sm50 / Status

Waiting Waiting sm50 / Status

Running Running sm50 / Status

Stopped Stopped sm50 / Status

Completed Completed sm50 / Status


C.

Rem

oteand

Central

Monitoring

Sources


******* ******* sm50 / Status

All All sm50 / Status

Work Process Dispatch Queue SourceThe Work Process Dispatch Queue source includes the followingattributes and their keyword equivalents:


All All sm51 / queue information

Dialog Dialog sm51 / queue information

Update Update sm51 / queue information

Update2 Update2 sm51 / queue information

Batch Batch sm51 / queue information

Spool Spool sm51 / queue information

Enqueue Enqueue sm51 / queue information

Nowp Nowp sm51 / queue information

Long Running Work Process SourceThe Long Running Work Process source includes the followingattributes and their keyword equivalents:


All All sm51 / elapsed time

Dialog Dialog sm51 / elapsed time

Update Update sm51 / elapsed time

Update2 Update2 sm51 / elapsed time

Batch Batch sm51 / elapsed time

Spool Spool sm51 / elapsed time

Enqueue Enqueue sm51 / elapsed time



Threshold in seconds Specified threshold value sm51 / elapsed time

Buffer SourceBuffer sources include the following attributes and their keywordequivalents:


Allocated Memory ALLOCATED_MEMORY st02 / Allocated (Kb)

Available Memory AVAILABLE_MEMORY st02 / Available (Kb)

DB Accesses DB_ACCESSES st02 / Database accesses

DB Accesses Saved DB_ACCESSES_SAVED st02 / DB accesses saved

Frames Swapped FRAMES_SWAPPED st02 / Frames swapped

Free Directory EntriesFREE_DIR_ENTRIES st02 / Free directory (Entries)

Free Directory EntriesPercent

PERCENT_FREE_DIR_ENTRIES Not directly available.FREE_DIR_ENTRIES divided byMAX_DIR_ENTRIES.

Free Memory FREE_MEMORY st02 / Free space (Kb)

Free Memory PercentPERCENT_FREE_MEMORY Not directly available.FREE_MEMORY divided byAVAILABLE_MEMORY.

Hits HITS st02 / Hits

Hit Ratio HIT_RATIO st02 / Hit ratio (%)

Last Reset Date LAST_RESET_DATE st02 / Startup (Date)

Last Reset Time LAST_RESET_TIME st02 / Startup (Time)

Max Directory Entries MAX_DIR_ENTRIES st02 / Dir. size Entries

Objects Swapped OBJECTS_SWAPPED st02 / Object swaps

Quality QUALITY st02 / DB access quality %

Requests REQUESTS st02 / Requests

Total Resets TOTAL_RESETS st02 / Resets - Total

Used DirectoryEntries

USED_DIR_ENTRIES st02 / Directory entries - Used


C.

Rem

oteand

Central

Monitoring

Sources


Used DirectoryEntries Percent

PERCENT_USED_DIR_ENTRIES Not directly available.USED_DIR_ENTRIES divided byMAX_DIR_ENTRIES

Used Memory USED_MEMORY st02 / Size - Used

Used Memory PercentPERCENT_USED_MEMORY Not directly available.USED_MEMORY divided byAVAILABLE_MEMORY

Performance SourcePerformance sources include the following attributes and theirkeyword equivalents:


Frequency per minuteFREQUENCY al01 / Performance - Count

Response Time inmilliseconds

RESPONSE al01 / Performance - Avg. Resp.

Wait Time inmilliseconds

WAIT al01 / Performance - Avg. Wait

Heap Memory SourceThe Heap Memory source includes the following attributes and theirkeyword equivalents:


Heap Currently Used HEAP_CURRENTLY_USED st02 / Heap Memory / Currentuse (Kb)

Heap Max Used HEAP_MAX_USED st02 / Max use (Kb)

Extended Memory SourceThe Extended Memory source includes the following attributes andtheir keyword equivalents:



ExtendedCurrently Used

EXTENDED_CURRENTLY_USED st02 / Current use (Kb)

Extended MaxUsed

EXTENDED_MAX_USED st02 / Maximum use (Kb)

Extended % Used EXTENDED_PERCENT_USED st02 / Extended Memory /Current use (%)

Extended FreeSpace

EXTENDED_FREE_SPACE Not directly available. Totalsize of extended memoryminusExtended CurrentlyUsed.

Extended PercentFree

EXTENDED_PERCENT_FREE Not directly available.Extended Free Spacedivided bytotal size ofextended memory.

Extended MaxPercent Used

EXTENDED_MAX_PERCENT_USED Not directly available.Extended Max Useddividedby total size of extendedmemory.

User SourceThe User source includes the following attributes and their keywordequivalents:


All Sessions USER_TERMINAL_SESSIONS sm04 / Total sessions

User TerminalSessions

USER_TERMINAL_SESSIONS sm04 / Total non-APPC-TMsessions

OS/390 DB2 SourceOS/390 DB2 source includes the following attributes and theirkeyword equivalents:

Note: The R/3 reference in the following table applies to R/3releases 3.1x to 4.0.


C.

Rem

oteand

Central

Monitoring

Sources


Active pages of bufferpool with maximumactive

MAX_ACTIVE_BP_PAGES st04 / Max active pages (%)

Hit ratio of bufferpool with minimumhit ratio

MIN_BP_HIT_RATIO st04 / Min hit ratio (%)

Buffer Pool 0 hit ratio BP0_HIT_RATIO st04 / Buffer Pool Activity / BP0Hit Ratio (%)



32K Buffer Pool hitratio

BP32K_HIT_RATIO st04 / Buffer Pool Activity /BP32K Hit Ratio (%)

Buffer Pool shortage -any active pool

BP_SHORTAGE st04 / Buffer pool shortage

Hiper pool concern -any active pool

BP_HIPER st04 / Hiper pool concerns

Buffer Pool 0maximum activepages

BP0_MAX_ACTIVE_PAGES Not directly available. Can beseen asMax active pages (%)when this buffer is the one withthe highest active pages.





32K Buffer Poolmaximum activepages

BP32K_MAX_ACTIVE_PAGES Not directly available. Can beseen asMax active pages (%)when this buffer is the one withthe highest active pages.

Deadlocks DEADLOCKS st04 / Deadlocks

Lock Suspensions LOCK_SUSPENSIONS st04 / Suspensions



Lock Timeouts LOCK_TIMEOUTS st04 / Timeouts

Failures due to EDMpool full

EDM_POOL_FULL_FAILURES st04 / EDM pool full

EDM pool utilization(%)

EDM_POOL_IN_USE st04 / EDM pool / Pages in use(%)

Dynamic cache hitratio

DYN_CACHE_HIT_RATIO st04 / Dynamic Statement Cache/ Hit ratio (%)

Number of timesMAXKEEPD wasexceeded

MAXKEEPD_EXCEEDED st04 / MAXKEEPD exceeded

Indication of deferredclose thresholdreached

CLOSE_THRESHOLD_REACHED st04 / Deferred close thresholdreached

Commits COMMITS st04 / Commits

Rollbacks ROLLBACKS st04 / Rollbacks

Checkpoints CHECKPOINTS st04 / Checkpoints

OS/390 SourceOS/390 source includes the following attributes and their keywordequivalents:


CPU Utilization (%) CPU_UTIL os07 / Avg. Processor Utili.

CPU Utilization -system (%)

SYSTEM_CPU_UTIL os07 / MVS CPU Utilization

Paging Rate PAGING_RATE_SEC os07 / Avg. System Paging Rate

Pages In per second PAGE_INS_SEC os07 / Pages paged in/sec

Pages Out per secondPAGE_OUTS_SEC os07 / Pages paged out/sec

Pages Into Private persecond

PAGE_INS_PRIVATE_SEC os07 / Priv. pages paged in/s

Pages Out of Privateper second

PAGE_OUTS_PRIVATE_SEC os07 / Priv. pages paged out/s


C.

Rem

oteand

Central

Monitoring

Sources


Pages to ExpandedStorage per second

PAGES_TO_EXPSTOR_SEC os07 / Pages to exp. storage

Pages from ExpandedStorage per second

PAGES_FROM_EXPSTOR_SEC os07 / Pages from exp. storage

Blocked pages pagedin

BLOCKED_PAGES_PAGED_IN os07 / Blocked pages paged in

Blocks paged in BLOCKS_PAGED_IN os07 / Blocks paged in

Unused interval countUNUSED_INTERVAL_COUNT os07 / High UIC count

Available frames inexpanded storage

EXPSTOR_AVAILABLE_FRAMES os07 / Avail. exp. stor. slots

Migration age MIGRATION_AGE os07 / Migration age

Total available framesTOTAL_AVAILABLE_FRAMES os07 / No. of available frames


IDOC Status Codes

This appendix describes the IDOC status codes and thecorresponding TEC event severities. For more detailed informationabout IDOC status codes, refer to the appropriate SAPdocumentation.

Note: Harmless events are generated only if the specific IDOC wasin an error state in the previous polling cycle. Otherwise, noevents are generated.

The following table describes outbound IDOC status codes thatgenerate TEC events:

Outbound IDOCs

Code Error Event Severity SAP Meaning

02 Yes Error Error passing data to port

03 No Error if transactionSM58 indicates anRFC transmissionerror

Data pass to port OK

04 Yes Error Control information of EDIsubsystem

05 Yes Error Translation

06 No Harmless Translation

07 Yes Error Syntax check

08 No Harmless Syntax check

D


D.

IDO

CS

tatusC

odes

Outbound IDOCs


09 Yes Error Interchange handling

10 No Harmless Interchange handling

11 Yes Error Dispatch

12, 13,14

No Harmless OK

15 Yes Warning Interchange acknowledgementnegative

16 No Harmless Functional acknowledgement

17 Yes Warning Functional acknowledgementnegative

18 No Harmless Triggering EDI subsystem

20 Yes Error Triggering EDI subsystem

22 No Harmless Dispatch OK,acknowledgement still due

23 Yes Error Retransmission

24 No Harmless Control information of EDIsubsystem

25 Yes Warning Processing despite syntaxerror

26 Yes Error Syntax check

27 Yes Error ALE error

29 Yes Error Error in ALE services

30 No Harmless Ready for dispatch (ALE)

31 No Harmless IDOC is marked for deletion

33 No Harmless Original of an IDOC whichwas edited

34 Yes Error Error in control record ofIDOC

36 Yes Error Timeout error; electronicsignature not performed

37 Yes Error IDOC added incorrectly

38 No Harmless IDOC archived


Outbound IDOCs


39 No Harmless Receive confirmed

40 Yes Error Application document notcreated in target system

41 No Harmless Application document createdin target document

The following table describes the inbound IDOC status codes thatgenerate TEC events:

Inbound IDOCs


51, 52 Yes Error Posting error

53 No Harmless Posting successful

54 Yes Error Error during formalapplication check

55 No Harmless Formal application check

56 Yes Error IDOC with error added

60 Yes Error Syntax error

61 Yes Warning Processing despite syntaxerror

62 No Harmless IDOC passed to application

63 Yes Error Error passing IDOC toapplication

64 No Harmless IDOC ready to be passed toapplication

65 Yes Error ALE error

68 No Harmless IDOC is marked for deletion

70 No Harmless Original of an IDOC whichwas edited

73 No Harmless IDOC archived


D.

IDO

CS

tatusC

odes


Function Module Authorization

This appendix contains a list of the function modules delivered withManager for R/3. For each function module, the R/3 authorizationsrequired for that module are given. The authorizations list theauthorization object referenced followed by the field values requiredfor the function module. The references to the S_RFC authorizationobject are only necessary for R/3 Releases 3.1G and later that havethe RFC security check enabled.

J_8C1_ALERT_CONTROL

S_RZL_ADM, ACTVT=03

S_RFC, TYPE=FUGR, RFC_NAME=J8C1, ACTVT=16

J_8C1_ALERT_READER

S_RZL_ADM, ACTVT=01


J_8C1_BUFFER_INFO

S_RZL_ADM, ACTVT=03

S_ADMI_FCD, S_ADMI_FCD=ST0R

S_RFC, TYPE=FUGR, RFC_NAME=SO02, ACTVT=16


J_8C1_BUFFER_NAMES

S_RZL_ADM, ACTVT=03

E


E.

Function

Module

Authorization


J_8C1_DISPLAY_BATCH

S_BTCH_ADM, BTCADMIN=Y


J_8C1_EMHM_INFO

S_RZL_ADM, ACTVT=03


J_8C1_MODIFY_JOB

S_BTCH_ADM, BTCADMIN=Y

S_BTCH_JOB, JOBACTION=RELE


J_8C1_MODIFY_PROCESS

S_ADMI_FCD, S_ADMI_FCD=PADM


J_8C1_DISPLAY_PROCESS


J_8C1_IDOCS_MONITOR


J_8C1_PROC_MONITORS


J_8C1_SYSLOG_READER


J_8C1_OS_COLLECT


J_8C1_OS390_COLLECT


J_8C1_OS390_DB2



J_8C1_ROLL_PAGE_SIZES

S_RZL_ADM, ACTVT=03


J_8C1_SYSLOG_TXTS


J_8C1_USER_INFO

S_RZL_ADM, ACTVT=03



E.

Function

Module

Authorization


Messages

This appendix describes Manager for R/3 messages.

ABH0001I &1 The last few lines of the log file &2 are ...

Explanation: This message precedes the display of a set of lines from the end ofthe appropriate log. This message is always preceded by a separate error messageindicating the nature of the problem.

User Response: None.

ABH0002E &1 Command failed. &2 &3 &4

Explanation: A Tivoli or an operating system command has failed. The failingcommand is given by &2, with supporting data optionally provided by &3 and &4.

User Response: Contact Tivoli Customer Support.

ABH0500E &1 Program was invoked with incorrect syntax. Input parameters missing.

Explanation: A required input parameter was not specified on the input dialog.The program did not start.

User Response: Start the program again and be sure to specify the requiredparameters.

ABH0501E &1 The Distributed Monitoring application must be installed on this TMRserver.

Explanation: The Configure Event Server task was run on a TMR server that doesnot have Distributed Monitoring installed. The Configure Event Server task requiresDistributed Monitoring.

User Response: Install Distributed Monitoring on the TMR server.

F


F.M

essages

ABH0502E &1 Rulebase &2 must already exist.

Explanation: The Configure Event Server task attempted to clone the specifiedrule base, but the rule base does not exist.

User Response: Run the task again providing the correct rule base name.

ABH0503W &1 Universal classes have not been installed.

Explanation: The Configure Event Server task determined that the Universalclasses have not yet been installed.

User Response: None. The Universal classes will be automatically installed.

ABH0504I &1 Installing universal classes, &2.

Explanation: The Configure Event Server task is installing the Universal classes.This message is always preceded by message ABH0503W.


ABH0505W &1 Distributed Monitoring Universal Monitor Collection is not available.

Explanation: The Configure Event Server task determined that the DistributedMonitoring Universal monitor collection cannot be accessed.


ABH0506E &1 Distributed Monitoring Universal Monitor Collection has not been installed.

Explanation: The Configure Event Server task determined that the DistributedMonitoring Universal monitor collection has not been installed. The ConfigureEvent Server task requires this monitoring collection.

User Response: Install the Distributed Monitoring Universal monitor collection.

ABH0507W &1 Tivoli classes have not been installed.

Explanation: The Configure Event Server task determined that the Tivoli classeshave not been installed.

User Response: None. The Tivoli classes will be automatically installed.

ABH0509I &1 Installing Tivoli classes, &2.

Explanation: The Configure Event Server task is installing the Tivoli classes. Thismessage is always preceded by ABH0507W.



ABH0509W &1 Distributed Monitoring classes have not been installed.

Explanation: The Configure Event Server task determined that the DistributedMonitoring classes have not been installed.

User Response: None. The Distributed Monitoring classes will be automaticallyinstalled.

ABH0510I &1 Installing Distributed Monitoring classes, &2.

Explanation: The Configure Event Server task is installing the DistributedMonitoring classes. This message is always preceded by message ABH0509W.


ABH0511E &1 Distributed Monitoring rules have not been installed.

Explanation: The Configure Event Server task determined that the DistributedMonitoring rules have not been installed. The Configure Event Server task requiresthese rules.

User Response: Install the Distributed Monitoring rules.

ABH0512E &1 Rulebase, &2, does not compile correctly.

Explanation: The rule base compiler detected an error while compiling rule base&2.


ABH0513I &1 Rulebase, &2, created successfully.

Explanation: The rule base compiler successfully compiled rule base &2.


ABH0514E &1 Rulebase, &2, creation failed.

Explanation: The Configure Event Server task could not create rule base &2.


ABH0515E &1 Failed to copy rulebase &2 to rulebase &3.

Explanation: The Configure Event Server task could not copy rule base &2 torule base &3.


F.M

essages


ABH0516E &1 Failed to import &2 to rulebase &3.

Explanation: The Configure Event Server task could not import rule base &2 torule base &3.


ABH0517E &1 Failed to create event source &2.

Explanation: The Configure Event Server task could not create new event source&2.


ABH0518E &1 Failed to delete event source &2.

Explanation: The Configure Event Server task could not delete the old eventsource &2.


ABH0519E &1 Failed to load rulebase &2.

Explanation: The Configure Event Server task could not load rule base &2.


ABH0520E &1 Failed to start event server.

Explanation: The Configure Event Server task could not restart the event server.


ABH0521E &1 Failed to stop event server. Event server must be restarted.

Explanation: The Configure Event Server task could not stop the event server.


ABH0522E &1 This host is not the TEC Event Server.

Explanation: The Configure Event Server task was distributed to a host that is notthe TEC event server.

User Response: Distribute the task to the TEC event server.


ABH0523E &1 Can not find directory for rulebase &2.

Explanation: The Configure Event Server task was not able to find the directoryfor rule base &2.


ABH0524I &1 Removed old event group &2.

Explanation: The Configure Event Console task successfully removed old eventgroup &2.


ABH0525E &1 Failed to remove old event group &2.

Explanation: The Configure Event Console task could not remove the old eventgroup &2.


ABH0526I &1 Created new event group &2.

Explanation: The Configure Event Console task successfully created new eventgroup &2.


ABH0527E &1 Failed to create new event group &2.

Explanation: The Configure Event Console task could not create the new eventgroup &2.


ABH0528I &1 Assigned event group &2 to event console &3.

Explanation: The Configure Event Console task successfully assigned event group&2 to event console &3.


ABH0529E &1 Failed to assign event group &2 to event console &3.

Explanation: The Configure Event Console task could not assign event group &2to event console &3.



F.M

essages

ABH0530E &1 Event console &2 does not exist.

Explanation: The event console named &2 that was supplied to the ConfigureEvent Console task does not exist.

User Response: Run the task again with the correct event console name.

ABH0531E &1 Failed to add event filter &2.

Explanation: The Configure Event Console task could not add event filter &2.


ABH0532E &1 Subscriber list &2 already exists.

Explanation: The subscriber list name supplied to the Create Subscriber List taskalready exists.

User Response: Run the task again with a subscriber list name that does not exist.

ABH0533E &1 Module wr3rfc failed with return code &2 and output &3.

Explanation: The task script identified by &1 invoked the wr3rfc program tocommunicate with R/3 using the remote function call. The wr3rfc program failedwith return code &2 and standard output of &3.

User Response: Do the following:

1. Ensure the application server is available.

2. Run the Configure Remote Function Call task for the system that contains thisapplication server.

ABH0534I &1 Current &2 event adapter configuration for application server &3.

Explanation: This message displays the event adapter configuration parameters asa result of running the Display Event Adapter Configuration task.


ABH0535I &1 Polling Delay = &2.

Explanation: This message displays the value for the polling delay parameter as aresult of running the Display Event Adapter Configuration task.



ABH0536I &1 Event Server Port Number = &2.

Explanation: This message displays the value for the event server port numberparameter as a result of running the Display Event Adapter Configuration.


ABH0537I &1 Hostname of the Event Server = &2.

Explanation: This message displays the value for the event server hostnameparameter as a result of running the Display Event Adapter Configuration task.


ABH0539E &1 The event adapter parameters file does not exist for application server &2.

Explanation: The Display Event Adapter Configuration task was run for an eventadapter that has not been configured.

User Response: Run the Configure Event Adapter task to configure the eventadapter on this application server.

ABH0540E &1 The R/3 administrator &2 was not found.

Explanation: A task was run that requires the R/3 administrator ID, &2, but theID was not found on the machine where the task was run.

User Response: Ensure thesidadm user ID exists and is available.

ABH0541E &1 The administrator home directory &2 was not found.

Explanation: A task was run that requires the R/3 administrator ID, &2, but thehome directory for the ID was not found.

User Response: Ensure thesidadm user ID exists and that its home directory isavailable on the machine on which you want to run the task.

ABH0542E &1 The administrator profile &2 was not found in the home directory &3.

Explanation: A task was run that requires the R/3 administrator profile, &2, butthe profile was not found in the home directory for the administrator.

User Response: Ensure thesidadm user profile is in the user home directory.

ABH0543E &1 The database profiles &2 and &3 were not found.

Explanation: A task was run that requires an R/3 administrator database profile,but neither the &2 profile nor the &3 profile was found.


F.M

essages

User Response: Ensure thesidadm profiles are in the user home directory.

ABH0545E &1 The file sap_start_db_exit.sh was not found.

Explanation: The start database task was run for a database on a Windows NTmachine. However, the required start exit routine,sap_start_db_exit.sh, was notfound.

User Response: Ensure the start exit routine exists and is in the correct directory.For more information, see “Creating Exit Routines for Windows NT” on page 72.

ABH0546E &1 Program dbaccess failed with return code &2.

Explanation: The start dbaccess task could not complete properly. The return codeis &2. If another error message precedes this message, the return code might havebeen generated by that error. If no other error message precedes this message, thereturn code was set by the dbaccess program.

User Response: Do one of the following:

¶ For accompanying errors, address those errors first.

¶ For no accompanying errors, ensure that the dbaccess program is available andfunctioning correctly.

ABH0547E &1 Program wruntask failed with return code &2 while trying to execute &3task.

Explanation: The Tivoli wruntask command was attempted but failed. The task itwas trying to run was &3. The return code from thewruntask command was &2.


ABH0548I &1 Task &2 has finished with the following output: &3.

Explanation: A task has completed successfully. The task name is &2. Thestandard output is &3.


ABH0550E &1 The database stop command &2 was not found.

Explanation: The Stop Database task on Windows NT requires a user-suppliedstop exit routine, sap_stop_db_exit.sh.

User Response: Create the sap_stop_db_exit.sh stop exit routine as described in“Creating Exit Routines for Windows NT” on page 72.


ABH0551E &1 The file sap_stop_db_exit.sh was not found.

Explanation: The stop database task was run for a database on a Windows NTmachine. However, the required stop exit routine,sap_stop_db_exit.sh, was notfound.

User Response: Ensure the stop exit routine exists and is in the correct directory.For more information, see “Creating Exit Routines for Windows NT” on page 72.

ABH0553I &1 Processing completed without error.

Explanation: The cancel action completed without any errors being reported.


ABH0554E &1 Processing completed with an error, return code = &2.

Explanation: The Cancel Batch Job, Release Batch Job, or Cancel Work Processtask failed.

Possible return codes and their meanings for the Cancel Batch Job task are asfollows:

3 The job does not exist. Check if the job still exists.

4 The job is not active.

5 Insufficient authorization. Ensure that the R/3 ID configured for RFCinterface access has the proper authorization. The required authorization isfor objectS_BTCH_ADM with BTCADMIN=Y .

Possible return codes and their meanings for the Release Batch Job task are asfollows:

17 The job is not currently scheduled. No action is necessary.

18 No batch job process is available.

20 No batch job process exists for the job class of the job that is beingreleased.

21 Insufficient authorization. Ensure that the R/3 user ID configured for RFCaccess has the proper authorization. The required authorization is for theobjectS_BTCH_ADM and the Batch Administrator ID field needs to beset toY.

22 Same as return code 21 listed above.

Possible return code and its meaning for the Cancel Work Process task is as follows:

1 Insufficient authorization. Ensure that the R/3 user ID configured for RFC


F.M

essages

access has the proper authorization. The required authorization is for theobject S_ADMI_FCD and the System Administration Function fieldcontains PADM.

User Response: For other return codes, contact Tivoli Customer Support.

ABH0558E &1 Start SAPGUI command not found.

Explanation: An attempt was made to start the SAPGUI, but the SAPGUIexecutable was not found on the machine on which the task was run.

User Response: Ensure that the SAPGUI executable is available on the targetmachine, and set up the environment so that the executable can be found.

ABH0559E The Configure Remote Function Call task has not been run for this R/3 system.

Explanation: To configure the Syslog Event Adapter or the IDOC Event Adapter,you must first configure the remote function call (RFC) for the corresponding R/3system.

User Response: Run the Configure Remote Function Call task in the R3Configuration Tasks library against the appropriate R/3 system object. For moreinformation, see “Configuring a Remote Function Call” on page 71.

ABH0560E &1 Failed to delete &2 in rulebase &3.

Explanation: The specified rule could not be deleted in the rule base specified by&3.


ABH0561E Alert Control script failed with al_typ or al_styp not set. The R/3 alert class is&1.

Explanation: An environmenet variable was not set.


ABH0562E &1 Unexpected object class name.

Explanation: The Send GEM Heartbeat task was not run against a valid object.This task should be run against R3AppServer, R3DBServer, R3ITSServer, andR3System objects only.

User Response: Run the task against a valid object.


ABH0563E &1 Could not start the schedule service.

Explanation: The Windows NT schedule service was not running. The ConfigureAutodiscovery for NT task tried to start the schedule service but failed.


¶ Ensure that the user ID that the Configure Autodiscovery for NT task uses hasthe authority to start the schedule service.

¶ Configure the Windows NT service so that the schedule service is running.

ABH0564E &1 Error in time value.

Explanation: The value entered in the minute or hour field is not valid. Validvalues for the minute field are 0 through 59. Valid values for the hour field are 0through 23.

User Response: Run the task again and enter a valid value in the minute and hourfields.

ABH0565E &1 Error in date format. This should be integer between 1 and 31.

Explanation: The value entered in the date field is not valid. Valid values for thedate field are 1 through 31.

User Response: Run the task again and enter a valid value in the date field.

ABH0566E &1 Please enter the TMR region name.

Explanation: The TMR name was not provided.

User Response: Start the program again specifying the TMR name.

ABH0567E &1 Error setting the at command.

Explanation: The Configure Autodiscovery task for NT failed because it could notschedule the job using theat command.

User Response: Ensure that the values for the time parameters are valid.

ABH0568E &1 Can not run Stop Database under &2 on database server.

Explanation: The sidadm running the stop database command did not have theproper authority.

User Response: Ensure that thesidadm has the authority to stop the database.


F.M

essages

ABH0569E &1 Management object for database server, &2, does not exist. Request can notbe completed.

Explanation: The start or stop database task cannot find the specified databaseserver object.

User Response: Ensure that the R3DBServer object has been created. If you arestarting or stopping a UNIX database server, the database server must reside on thesame machine as an R/3 application server. If you are using an OS/390 databaseserver, you can ignore this message. Manager for R/3 does not start or stop anOS/390 database server.

ABH0569I &1 Management object for database server, &2, does not exist. Database servermay still be running.

Explanation: The database server object does not exist and, therefore, cannot bestopped.

User Response: Either create the R3DBServer object, or stop the database servermanually after running the Stop R/3 System task.

ABH0570E &1 Can not run Start Database under &2 on database server.

Explanation: The SAP command to start the database failed.

User Response: Obtain the sap_sysupdown_clone_event.log file from the /tmpdirectory on the TEC event server, a rules trace of the current rule set, if available,and contact Tivoli Customer Support.

ABH0571I &1 Event adapter action complete.

Explanation: The start or stop event adapter task has completed.


ABH0572E &1 Event adapter action error. Return code = &2.

Explanation: This message produces return codes related to the Alert EventAdapter, Syslog Event Adapter, or IDOC Event Adapter. Possible return codes andtheir meanings are:

27 No unique name. The Alert Event Adapter, Syslog Event Adapter, orIDOC Event Adapter is not named r3mibIID , r3slogIID , or r3idocIID ,respectively. If you are using Manager for R/3 event adapter tasks, contactTivoli Customer Support.

30 Windows NT only. The Alert Event Adapter, the Syslog Event Adapter, orthe IDOC Event Adapter has been invoked with a value other than


–install, –start, –stop, or –remove. If you are using Manager for R/3 eventadapter tasks, contact Tivoli Customer Support.

31 Windows NT only. The Alert Event Adapter, the Syslog Event Adapter, orthe IDOC Event Adapter has been invoked without a value. The eventadapter should be invoked with one of the following values: –install,–start, –stop, or –remove. If you are using Manager for R/3 event adaptertasks, contact Tivoli Customer Support.

41 Unable to open the event adapter log file. On UNIX, check the /tmpdirectory for space. On Windows NT, check the %SYSTEMROOT%\tempdirectory for space. If the temp directory does not exist, check thedirectory where the event adapter executable resides:



User Response: For other return codes, contact Tivoli Customer Support.

ABH0573I &1 No application server was found on this machine.

Explanation: The automatic discovery function was not able to find anyapplication servers in the R/3 shared memory.

User Response: Ensure that the application servers are running. If you are runningthe Configure Autodiscovery Task for NT, make sure that the user ID that ran thetask has the authority to read the R/3 shared memory. Also, make sure that the R/3application server profiles are properly configured. See “Configuring R/3Application Server Profiles” on page 50.

ABH0574E &1 Clone AppServer Status Monitor failed because the input event is incorrect.

Explanation: The data in the event is corrupted, and the shell script specified by&1 cannot determine the event type.

User Response: Obtain the log file for the &1 shell script, which is located on themachine that is running the TEC, and call Tivoli Customer Support.

ABH0575E &1 Please select the version of the SAPGUI that you want to distribute.

Explanation: The SAPGUI version was not selected on the dialog.

User Response: Run the task again and select the version of the SAPGUI that youwant to distribute.

ABH0576E &1 File &2 does not exist.

Explanation: A required file was not found on the SAPGUI installation server.


F.M

essages

User Response: Verify that the SAPGUI installation server is properly installed. Ifthe problem persists, contact Tivoli Customer Support.

ABH0577E &1 File package &2 does not exist. Enter package name exactly as shown inthe output from the List Available SAPGUI File Packages task.

Explanation: The SAPGUI file package name entered in the dialog is not valid.

User Response: Check the name of the SAPGUI file package in the output fromthe List Available SAPGUI File Packages task. Run the task again and enter theexact SAPGUI file package name in the dialog.

ABH0578E &1 The command failed.

Explanation: An error occurred while running the Configure SAPGUI Packagetask. This message precedes a set of lines from the appropriate log file.

User Response: Correct the problem that is described in the log file. If theproblem persists, contact Tivoli Customer Support.

ABH0579E &1 You must provide the name of the file package to be installed.

Explanation: The SAPGUI file package name was not entered in the InstallPackage dialog.

User Response: Run the task again and enter the exact SAPGUI file packagename. Use the List Available SAPGUI File Packages task to determine the names ofthe SAPGUI file packages that exist on the SAPGUI installation server.

ABH0580E &1 You must provide the machine name of the installation server.

Explanation: The machine name of the R/3 SAPGUI installation server was notentered in the dialog.

User Response: Run the task again and enter the machine name of the R/3SAPGUI installation server.

ABH0581E &1 You must provide the shared directory name of where NetSetup.exe islocated.

Explanation: The shared path name where theNetSetup.exeexecutable is locatedon the SAPGUI installation server was not entered in the dialog.

User Response: Run the task again and enter the shared path name where theNetSetup.exeexecutable is located.


ABH0582I &1 The file packages available for installation are:

Explanation: This message is produced by the List Available SAPGUI FilePackages task, and it lists the names of the SAPGUI file packages that exist on theR/3 SAPGUI installation server.


ABH0583I &1 The file package was created successfully.

Explanation: This message indicates that the SAPGUI file package was createdsuccessfully.


ABH0584E &1 Software Distribution must be installed on the SAPGUI installation server.

Explanation: To create a SAPGUI software package for distribution, SoftwareDistribution must be installed on the R/3 SAPGUI installation server.

User Response: Install Software Distribution on the R/3 SAPGUI installationserver and run the task again.

ABH0585I &1 Imported &2 to rulebase &3.

Explanation: This message is produced by the Configure Event Server task. Thismessages lists the rule file &2 that is imported into rule base &3.


ABH0586E &1 Profile creation failed: &2.

Explanation: Manager for R/3 could not create monitoring profile &2.


ABH0587E &1 Adding of monitor to profile failed.

Explanation: This message is issued by the Create RDBMS Manager StatusMonitor task. Manager for R/3 could not add the database status monitor to themonitoring profile.


ABH0588E &1 Setting of remote user and group IDs failed.

Explanation: The user ID and group ID could not be set for the monitoring profilethat was created.


F.M

essages


ABH0589E &1 Error setting the crontab command.

Explanation: This message is issued when scheduling autodiscovery on UNIX.This cron job was not set because of a permission problem.

User Response: Ensure that the root user has permission to create a cron job.

ABH0590E &1 Error in month format. This should be an integer between 1 and 12.

Explanation: This message is issued when scheduling autodiscovery and indicatesthat the value entered for the month is not valid.

User Response: Run the Configure Autodiscovery task again and specify a valuefrom 1 through 12 for the month. If you want to specify more than one month,separate the entries (without intervening spaces) with a comma.

ABH0591E &1 Error getting DB2 Instance Name, &2.

Explanation: The Create RDBMS Manager Status Monitor task could not find theDB2 instance name.


ABH0592E &1 Adapter &2 has not been configured.

Explanation: This message is issued when the Start Adapter task has beenexecuted against an R/3 application server that does not have a configured eventadapter.

User Response: Configure the appropriate event adapter (Alert Event Adapter,Syslog Event Adapter, or IDOC Event Adapter), and run the Start Adapter taskagain.

ABH0593W &1 Management object for database server, &2, does not exist. Database servermay not be started. Attempting to start application servers...

Explanation: The database server object does not exist and, therefore, cannot bestarted. Manager for R/3 will attempt to start the application servers. However, ifthe database server is not running, the attempt to start the application servers willfail.

User Response: Either create the R3DBServer object, or start the database servermanually before running the start R/3 system task.


ABH3001E No memory to create tables.

Explanation: Insufficient memory is available to put output information into atable.

User Response: Contact your system administrator.

ABH3002E Open failed for command file &1.

Explanation: The wr3rfc program could not open the command file (rfc_interfacefile).

User Response: Create a command file as described in “Command Line InterfaceCommands” on page 167. If the file already exists, change permissions so that thefile can be read.

ABH3003E Exceeded number of export parameters accepted by &1.

Explanation: There are too many command line (or configuration file) argumentsfor this command file. You have entered more export parameters than are specifiedin the command file.

User Response: Delete the extra export parameters, then run the command again.

ABH3004E Parameter &1 exceeds defined length.

Explanation: The length of the export parameter is greater than the specifiedlength of the parameter.

User Response: Change the length parameter so that it is greater than or equal tothe length of the value to be exported.

ABH3005E RFC_OPEN failed.

Explanation: An RFC connection could not open.

User Response: Verify that command line (or configuration file) options arecorrect. See “Command Line Interface Commands” on page 167.

ABH3006E ItCreate failed for importing table.

Explanation: There is not enough memory available to create an internal structurefor the size and shape of the table requested.

User Response: Perform the remote function call from a system with moreavailable memory. If the problem persists, contact your system administrator.


F.M

essages

ABH3007E Itfree failed for importing table.

Explanation: An attempt to free up memory by deleting all rows from a tablefailed.

User Response: Perform the remote function call from a system with moreavailable memory. If the problem persists, contact your system administrator.

ABH3008E Install Structure error.

Explanation: R/3 could not create an internal structure for the specifiedheterogeneous table.


ABH3009E Elapsed time for RfcCall has expired.

Explanation: There has been a failure in the remote function call.

User Response: Verify the command line options, especially the password.

ABH3010E In RfcListen.

Explanation: There has been a failure in the remote function call.

User Response: Verify the command line options, especially the password.

ABH3011E ItGetLine for the imported table failed.

Explanation: The ItGetLine function could not return the requested table row.


ABH3013E In RfcReceive.

Explanation: An internal error in retrieving information from R/3 has occurred.


ABH3014E In RfcCall.

Explanation: This function calls an ABAP/4 function module via RFC. It can failif RfcOpen is called with the wrong password.

User Response: Verify the command line options, such aspasswordandusername.If the problem persists, contact Tivoli Customer Support.


ABH3015E Incorrect line: &1.

Explanation: The line is not valid for the command file or configuration file.

User Response: For valid line formats, see “Command Line Interface Commands”on page 167.

ABH3016E Exceeded maximum number of input parameters.

Explanation: Exceeded the limit of 64 input or import parameters.

User Response: Specify 64 or fewer input parameters.

ABH3017E Exceeded maximum number of output parameters.

Explanation: Exceeded the maximum of 64 output parameters that are allowed tobe specified.

User Response: Specify 64 or fewer output parameters.

ABH3018E Only one IMPORT TABLE allowed.

Explanation: You can import only one table at a time.

User Response: Change the command file so that it requests only one table.

ABH3019E Malloc failed.

Explanation: Memory allocation failed for the remote function call on the user’ssystem.

User Response: Contact your system administrator.

ABH3020E Incorrect mode: &1.

Explanation: The mode indicated in the command line or the configuration file isnot correct. Valid values for mode are 2 and 3, which correspond toRFC_MODE_CPIC and RFC_MODE_R3ONLY, respectively.

User Response: Specify a valid mode value.

ABH3021E Incorrect trace: &1.

Explanation: The trace value indicated in the command line or the configurationfile is not correct. Valid values for trace are: YES and NO.

User Response: Specify a valid trace value.


F.M

essages

ABH3022E Incorrect type: &1.

Explanation: The value of the TYPE field in the command file is not correct.Valid values are: TYPC, TYPNUM, TYPX, TYPP, TYPINT, TYPINT1, TYPINT2,TYPFLOAT, TYPDATE, TYPTIME.

User Response: Specify a valid value in the TYPE field in the command file.

ABH3023E Incorrect format: &1.

Explanation: The value of the FORMAT field in the command file is not correct.Valid entries for FORMAT are RESULT and VERBOSE.

User Response: Specify a valid value in the FORMAT field in the command file.

ABH3024E Export parameter &1 must have a length specified.

Explanation: The fields, TYPC, TYPNUM, TYPX, and TYPP, within theEXPORT PARAMETER stanza must have a value specified in the LENGTH field.

User Response: Enter a value in the LENGTH field in the command file for theparameter to be exported.

ABH3025E Export parameter &1 contains an incorrect type &2.

Explanation: The specified export parameter does not have a valid value in theTYPE field. Valid types are: TYPC, TYPNUM, TYPX, TYPP, TYPINT, TYPINT1,TYPINT2, TYPFLOAT, TYPDATE, TYPTIME.

User Response: Specify a valid type in the TYPE field in the command file(rfc_interface file).

ABH3026E Import parameter &1 must have a length specified.

Explanation: The fields, TYPC, TYPNUM, TYPX, and TYPP, within theIMPORT PARAMETER stanza must have a LENGTH field specified.

User Response: Enter a value in the LENGTH field in the command file for theparameter to be imported.

ABH3027E Import parameter &1 contains an incorrect type &2.

Explanation: The value for the import parameter in the command file(rfc_interface file) is not correct. Valid types are: TYPC, TYPNUM, TYPX, TYPP,TYPINT, TYPINT1, TYPINT2, TYPFLOAT, TYPDATE, TYPTIME.

User Response: Specify a valid value in the command file.


ABH3036E Incorrect parameter type specified &1.

Explanation: The value specified in the TYPE field in the command file(rfc_interface file) is not correct. Valid types are TYPC, TYPNUM, TYPX, TYPP,TYPINT, TYPINT1, TYPINT2, TYPFLOAT, TYPDATE, and TYPTIME.

User Response: Specify a valid value in the TYPE field in the command file.

ABH3037E Incorrect format specified &1.

Explanation: The value specified in the FORMAT field in the command file is notcorrect. Valid format values are VERBOSE and RESULT.

User Response: Specify a valid value in the FORMAT field in the command file.

ABH3038E Error info: key: &1 status : &2 message : &3 internal: &4.

Explanation: This describes the last error reported by some function of the RFCAPI.


ABH3039E wr3rfc &1 rfc_interface[arg]

where:-d <Destination> 3-character SAP system id.-c 3-digit client sign on data.-u User id.-p Password.-l Language identifier; E is English.-2 or -3 CPIC mode(-2) or R/3 mode(-3).-t SAP rfc trace.-h The name of the target host.-s <nn> Target SAP server instance id.-g The gateway host. If -g is not used,

the -h argument is used.-x The TCP/IP service of the gateway. The

default is sapgwnn, where nn is the -sargument.

-C <cfgfile> The configuration file. The default is.wr3rfc.cfg in the directoryin which the wr3rfc program resides.

-D <n> The debug level [1|2|3]. 3 is the most detailed.-? This help msg.

Explanation: The syntax for thewr3rfc command is incorrect.


F.M

essages

User Response: For the command line syntax, see “Command Line InterfaceCommands” on page 167.

ABH3500-ABH3699

Explanation: Messages numbered ABH3500 through ABH3699 are written to alog file only and are intended to be conveyed to Tivoli Customer Support.Therefore, these messages are not documented in this appendix.

ABH4501E Create r3AppServer: R3 application server hostname not set.

Explanation: An R/3 application server host name was not entered in the dialog.

User Response: Run the task again and enter an R/3 application server host namein the dialog.

ABH4502E Create r3AppServer: R3 instance ID not set.

Explanation: An R/3 instance ID was not entered in the dialog.

User Response: Run the task again and enter the R/3 instance ID in the dialog.

ABH4503E Create r3AppServer: r3system OID is nil.

Explanation: An attempt was made to create the R3AppServer object insomething other than an R/3 System policy region.

User Response: Create the R3AppServer object in an R/3 System policy region.

ABH4504E Create r3AppServer: r3system &1 not found.

Explanation: An attempt was made to create the R3AppServer object insomething other than an R/3 System policy region.

User Response: Create the R3AppServer object in an R/3 System policy region.

ABH4505E Create r3AppServer: R/3 System not set.

Explanation: Autodiscovery did not create the R/3 policy region.


ABH4506E Create r3appserver: endpoint &1 not found.

Explanation: The TMA endpoint name specified in the dialog is not valid.

User Response: Specify a valid TMA endpoint name in the dialog.


ABH4507E Create r3appserver: SAP R/3 hostname not set.

Explanation: The R/3 host name was not entered in dialog.

User Response: Enter the R/3 host name in the dialog.

ABH4508E Create r3appserver: managed node &1 not found.

Explanation: The managed node name specified in the dialog is not valid.

User Response: Specify a valid managed node name in the dialog.

ABH4509E Create r3appserver: must specify managed node or endpoint.

Explanation: A managed node or endpoint name was not specified in the dialog.

User Response: Specify either a managed node name or a TMA endpoint name inthe dialog.

ABH4514E Create r3appserver: tmr_trans_begin failed.

Explanation: The transaction to create the R3AppServer object failed to begin.


ABH4515E Create r3appserver: tmf_trans_end failed.

Explanation: The transaction to create the R3AppServer object failed to end.


ABH4516E Create r3dbserver: R3 database server hostname not set.

Explanation: The R/3 database server host name was not set.


ABH4517E Create r3dbserver: r3system OID is nil.

Explanation: An attempt was made to create an R3DBServer object in somethingother than an R/3 system policy region.

User Response: Create the R3DBServer object in an R/3 system policy region.

ABH4518E Create r3dbserver: r3system &1 not found.

Explanation: An attempt was made to create the R3DBServer object in somethingother than an R/3 system policy region.


F.M

essages

User Response: Create the R3DBServer object in an R/3 system policy region.

ABH4519E Create R3DBServer: R/3 System not set.

Explanation: Autodiscovery did not create the R/3 System policy region.


ABH4520E Create r3dbserver: endpoint &1 not found.

Explanation: The TMA endpoint name specified in dialog is not valid.

User Response: Run the task again and specify a valid TMA endpoint name in thedialog.

ABH4521E Create r3dbserver: managed node &1 not found.

Explanation: The managed node name specified in dialog is not valid.

User Response: Run the task again and specify a valid managed node name in thedialog.

ABH4522E Create r3dbserver: must specify managed node or endpoint.

Explanation: The managed node name or TMA endpoint name was not specifiedin the dialog.

User Response: Run the task again and specify either the managed node name orthe TMA endpoint name in the dialog.

ABH4526E Create r3dbserver: tmf_trans_begin failed.

Explanation: The transaction to create the R3DBServer object failed to begin.


ABH4527E Create r3dbserver: tmf_trans_end failed.

Explanation: The transaction to create the R3DBServer object failed to end.


ABH4528E Create r3system: R/3 system database hostname not set.

Explanation: The R/3 database host name was not specified in the dialog.

User Response: Specify the database host name in the the dialog.


ABH4529E Create r3system: R/3 system database type not set.

Explanation: The database type was not specified in dialog.

User Response: Specify the database type in the dialog.

ABH4530E Create r3system: R/3 release not set.

Explanation: The R/3 release was not set when creating the R/3 system.


ABH4531E Create r3system: R/3 system ID not set.

Explanation: The R/3 system ID was not specified in the dialog.

User Response: Specify the R/3 system ID in the dialog.

ABH4532E There is already a r3system with the name &1.

Explanation: Manager for R/3 is trying to create an R/3 system that alreadyexists.


ABH4533E Only one instance of the R/3 system properties dialog is allowed to be active ata time. The dialog is currently being used by &1 on &2.

Explanation: The R/3 system properties dialog is already open.

User Response: Close the R/3 system properties dialog.

ABH4534E Create r3system: tmf_trans_begin failed.

Explanation: The transaction to create the R/3 system failed to begin.


ABH4535E Create r3system: tmf_trans_end failed.

Explanation: The transaction to create the R/3 system failed to end.


ABH4801E Create R3ITSServer: R3 ITS Server Host Name not set.

Explanation: When creating an R/3 ITS server, the host name was not set.



F.M

essages

ABH4803E Create R3ITSServer: R3System OID is nil.

Explanation: An attempt was made to create the R3ITSServer object in a policyregion other than an R/3 system policy region.

User Response: Create the R3ITSServer object in an R/3 system policy region.

ABH4804E Create R3ITSServer: R3System &1 not found.

Explanation: An attempt was made to create the R3ITSServer object in a policyregion other than an R/3 system policy region.

User Response: Create the R3ITSServer object in an R/3 system policy region.

ABH4805E Create R3ITSServer: End Point &1 not found.

Explanation: The TMA endpoint name specified in the dialog is not valid.

User Response: Run the task again and specify a valid TMA endpoint name.

ABH4806E Create R3ITSServer: managed node &1 not found.

Explanation: The managed node name specified in the dialog is not valid.

User Response: Run the task again and specify a valid managed node name.

ABH4807E Create R3ITSServer: Must specify Managed Node or Endpoint.

Explanation: A managed node or TMA endpoint name was not specified in thedialog.

User Response: Run the task again and specify a managed node name or a TMAendpoint name.

ABH4808E Create R3ITSServer: tmf_trans_begin failed.

Explanation: The transaction to create the R3ITSServer object failed to begin.


ABH4809E Create R3ITSServer: tmf_trans_end failed.

Explanation: The transaction to create the R3ITSServer object failed to end.



ABH4810E Only one instance of the R/3 ITS Server Properties dialog is allowed to beactive at a time. The dialog is currently being used by &1 on &2.

Explanation: The R/3 ITS server properties dialog is already open.

User Response: Close the R/3 ITS server properties dialog.

ABH4811E Create R3ITSServer: R3 ITS Server Name not set.

Explanation: The R/3 ITS server name was not specified in the dialog.

User Response: Run the task again and specify the R/3 ITS server name.

ABH6600E R3Mgr_uninstall21.pl [–g] [–yes]

Explanation: The syntax used for theR3Mgr_uninstall21.pl command was notvalid. Use the–g option to uninstall Tivoli GEM instrumentation only. Use the–yesoption to continue the uninstall process without prompts.

User Response: Run theR3Mgr_uninstall21.pl command again using the correctsyntax.

ABH6602E Cannot open log file &1.

Explanation: The specified log file could not be opened.

User Response: Do the following:

1. Ensure that there is available space in the/tmp on UNIX or the%TMP%directory on Windows NT.

2. Verify the file permissions.

3. Run the uninstall command again.

ABH6603I Continuing to uninstall Tivoli Manager for R/3...

Explanation: This message is issued when you confirm that you want to uninstallTivoli Manager for R/3.


ABH6604I Exiting uninstall at user request...

Explanation: This message is issued when you cancel uninstalling Tivoli Managerfor R/3.



F.M

essages

ABH6606I &1 This will uninstall the Tivoli Manager for R/3 Version 2.1. You should backup your Tivoli database before uninstalling Manager for R/3. Do you want tocontinue? Enter y to continue or n to quit.

Explanation: This is a reminder to back up the Tivoli database before running theR3Mgr_uninstall21.pl command.


¶ If you already backed up the Tivoli database, entery to continue.

¶ If you did not back up the Tivoli database, do the following:

1. Entern to exit.


3. Run the uninstall command again.

ABH6620I Your uninstall is now complete. Please see log: &1 for more details.

Explanation: The uninstall has completed.

User Response: View the specified log file if desired.

ABH6646I Option given to continue without prompting...

Explanation: This message is issued when the–yesparameter is specified with theR3Mgr_uninstall21.pl command. The uninstall process continues withoutprompting for a confirmation.


ABH6647I Uninstalling GEM Instrumentation only...

Explanation: This message is issued when the–g parameter is specified with theR3Mgr_uninstall21.pl command. TheR3Mgr_uninstall21.pl –g commanduninstalls Tivoli GEM instrumentation only.



Troubleshooting

This chapter describes diagnostic information and tools availablewith Manager for R/3. This chapter includes the following topics:

¶ “Setting Up the Environment”

¶ “Log Files” on page 256

¶ “TEC Events” on page 268

¶ “Configuring Monitor Logging Mode” on page 272

¶ “SAPGUI File Package Distribution” on page 273

¶ “Icon State” on page 273

¶ “File System Layout” on page 273

¶ “Hints on Using Tivoli GEM” on page 274

Setting Up the EnvironmentTo use the diagnostic tools (wr3mib andwr3rfc ), you should set upthe environment to ensure that shared libraries are available. Settingup the environment also makes it easier to locate Manager for R/3log files. To set up the environment, enter one of the followingcommands at the command prompt:

¶ On a UNIX managed node, enter one of the followingcommands:

v For non-C shells:. /etc/Tivoli/setup_env.sh

G


G.

Troubleshooting

v For C shell:source /etc/Tivoli/setup_env.csh

¶ On a UNIX TMA endpoint, enter one of the followingcommands:

v For non-C shells:. /etc/Tivoli/lcf/x/lcf_env.sh

v For C shell:source /etc/Tivoli/lcf/x/lcf_env.csh

¶ On a Windows NT managed node, enter:%SYSTEMROOT%\system32\drivers\etc\Tivoli\setup_env.cmd

¶ On a Windows NT TMA endpoint, enter:%SYSTEMROOT%\tivoli\lcf\x\lcf_env.cmd

Note: For TMA endpoints, replacex with 1 for the first TMAendpoint installed on the machine, replacex with 2 forthe second TMA endpoint installed on the machine, andso forth.

Log FilesKnowing where to look for information, such as task output and logfiles, can be key to solving a problem. This section describes whereto find various Manager for R/3 log files.

Task Log FilesThe following table describes the log file that is associated with eachManager for R/3 task. The task log files are located in one of thefollowing directories:

¶ UNIX: /tmp



Task Log File

Alert Control (internaltask)

SID_DBhostname_sap_alert_control_IID .log


Task Log File

Alert Reader (internaltask)

SID_DBhostname_sap_alert_reader_IID .log

Cancel Batch Job SID_DBhostname_sap_cancel_job.sh_IID .log

Cancel Work Process SID_DBhostname_sap_cancel_process.sh_IID .log

ConfigureAutodiscovery for NT

sap_at.log

ConfigureAutodiscovery forUNIX

sap_crontab.log

Configure Client Install sap_ci_config.log

Configure EventAdapter

¶ For the Alert Event Adapter:

SID_DBhostname_sap_config_adapter_MIBIID .log

¶ For the IDOC Event Adapter:

SID_DBhostname_sap_config_adapter_IDOCIID .log

¶ For the Syslog Event Adapter:

SID_DBhostname_sap_config_adapter_SLOGIID .log

Configure EventConsole

sap_tec_config.log

Configure Event Server sap_eventserver_config.log

Configure MonitorLogging Mode

¶ sap_monitor_debug_hostname_SID_IID.log

¶ For an R/3 ITS server component, one of the following:

sap_monitor_debug_hostname_VIIN_ITS.log

sap_monitor_debug_hostname_VIIN_ITS-AGate.log

sap_monitor_debug_hostname_VIIN_ITS-WGate.log

Configure RemoteFunction Call

SID_DBhostname_sap_config_rfc.log

Configure SAPGUIPackage

sap_sapgui_inst.log

Configure UNIX ClientInstall

sap_unix_ci_config.log

Configure Windows95/98 Client Install

sap_w95_ci_config.log


G.

Troubleshooting

Task Log File

Configure WindowsNT Client Install

sap_nt_ci_config.log

Create New SubscriberList

sap_create_subscriberlist.log

Create RDBMSManager StatusMonitor

sap_create_rdbms_mgr_profile.sh_PID.log, wherePID is theprocess ID.

Display Batch Jobs SID_DBhostname_sap_display_batch.sh_IID .log

Display BufferInformation

SID_DBhostname_sap_display_buffer_info_IID .log

Display Event AdapterConfiguration

¶ For the Alert Event Adapter:

SID_DBhostname_sap_adapter_infoMIB_IID .log


SID_DBhostname_sap_adapter_infoIDOC_IID.log


SID_DBhostname_sap_adapter_infoSLOG_IID .log

Display OS CollectInformation

SID_DBhostname_sap_display_OSCollect_info_IID .log

Display OS390 DB2Information

SID_DBhostname_sap_display_OS390_DB2_info_IID .log

Display OS390Information

SID_DBhostname_sap_display_OS390_info_IID .log

Display Roll PageInformation

SID_DBhostname_sap_display_roll_page_info_IID .log

Display WorkProcesses

SID_DBhostname_sap_display_process.sh_IID .log

List Available SAPGUIPackages

sap_sapgui_display_packs.log

List SAPGUI PackageFeatures

sap_sapgui_pack_features.log

Release Batch Job SID_DBhostname_sap_release_job.sh_IID .log

Remove Autodiscoveryfor NT

sap_unat.log


Task Log File

Remove Autodiscoveryfor UNIX

sap_uncrontab.log

Replace Event Adapter(internal task)

SID_DBhostname_sap_replace_adapter_IID .log

Send GEM Heartbeat SID_DBhostname_sap_gem_heartbeat.log

Set Remote MonitorDebug Mode (internaltask)

¶ SID_DBhostname_sap_monitor_debug_hostname_SID_IID.log

¶ For an R/3 ITS server component, one of the following:

SID_DBhostname_sap_monitor_debug_hostname_VIIN_ITS.log

SID_DBhostname_sap_monitor_debug_hostname_VIIN_ITS-AGate.log

SID_DBhostname_sap_monitor_debug_hostname_VIIN_ITS-WGate.log

Start Database SID_DBhostname_sap_start_db.log

Start Event Adapter ¶ For the Alert Event Adapter:

SID_DBhostname_sap_start_r3mib_IID .log


SID_DBhostname_sap_start_r3idoc_IID .log


SID_DBhostname_sap_start_r3slog_IID .log

Start ITS Server ¶ For a single-host R/3 ITS server:

SID_DBhostname_sap_start_itsVIINSINGLE.log

¶ For the AGate component:

SID_DBhostname_sap_start_itsVIINDUALAG.log

¶ For the WGate component:

SID_DBhostname_sap_start_itsVIINDUALWG.log

Start R/3 System SID_DBhostname_sap_start.log

Start Server SID_DBhostname_sap_start_server_IID .log

Start dbaccess SID_DBhostname_sap_start_dbaccess.log

Stop Database SID_DBhostname_sap_stop_db.log


G.

Troubleshooting

Task Log File

Stop Event Adapter ¶ For the Alert Event Adapter:

SID_DBhostname_sap_stop_r3mib_IID .log


SID_DBhostname_sap_stop_r3idoc_IID .log


SID_DBhostname_sap_stop_r3slog_IID .log

Stop ITS Server ¶ For a single-host R/3 ITS server:

SID_DBhostname_sap_stop_itsVIINSINGLE.log


SID_DBhostname_sap_stop_itsVIINDUALAG.log


SID_DBhostname_sap_stop_itsVIINDUALWG.log

Stop R/3 System SID_DBhostname_sap_stop.log

Stop Server SID_DBhostname_sap_stop_serverIID .log

Monitor Log FilesThe following table describes the log file that is associated with eachManager for R/3 monitor. The monitor log files are located in one ofthe following directories:

¶ UNIX: /tmp



Monitoring Source Log File

Application ServerStatus

SID_DBhostname_IID_app_server_monitor.log

Batch Performance SID_DBhostname_IID_batch_monitor.log



CUA Menu and TextBuffer

¶ For the central monitor:

hostname_SID_IID_menu_buffer_monitor.log

¶ For the remote monitor:

SID_DBhostname_IID_cua_monitor.log

Cancelled Job SID_DBhostname_IID_cancelled_job.log

DB2 - Inode Used%

SID_DBhostname_IID_db2dirinode_monitor.log

DB2 - Space Free SID_DBhostname_IID_db2dirfree_monitor.log

DB2 - Used % SID_DBhostname_IID_db2dirpct_monitor.log

DB2 Archive -Inode Used %

SID_DBhostname_IID_db2archivedirinode_monitor.log

DB2 Archive -Space Free

SID_DBhostname_IID_db2archivedirfree_monitor.log

DB2 Archive - Used%

SID_DBhostname_IID_db2archivedirpct_monitor.log

DB2 Log - InodeUsed %

SID_DBhostname_IID_db2logdirinode_monitor.log

DB2 Log - SpaceFree

SID_DBhostname_IID_db2logdirfree_monitor.log

DB2 Log - Used % SID_DBhostname_IID_db2logdirpct_monitor.log

Dialog Performance SID_DBhostname_IID_dialog_monitor.log

Extended Memory ¶ For the central monitor:

hostname_SID_IID_extended_monitor.log


SID_DBhostname_IID_extendedmem_monitor.log

FTAB Field CatalogBuffer


hostname_SID_IID_fielddesc_buffer_monitor.log


SID_DBhostname_IID_ftab_monitor.log


G.

Troubleshooting


Heap Memory ¶ For the central monitor:

hostname_SID_IID_heap_monitor.log


SID_DBhostname_IID_heapmem_monitor.log

IRBD InitialRecords Buffer


hostname_SID_IID_initrecs_buffer_monitor.log


SID_DBhostname_IID_irbd_monitor.log

ITS Server Status ¶ For a single-host R/3 ITS server:

SID_DBhostname_VIIN_SINGLE_itsstatus_monitor.log


SID_DBhostname_VIIN_DUALAG_itsstatus_monitor.log


SID_DBhostname_VIIN_DUALWG_itsstatus_monitor.log

Long Running WorkProcess

SID_DBhostname_IID_longrunning_monitor.log

Message ServerStatus

SID_DBhostname_IID_messageserver_monitor.log

OS Collect -Application Server


hostname_SID_IID_oscollectaps_buffer_monitor.log


SID_DBhostname_IID_oscollectaps.log

OS Collect -Database Server

hostname_SID_IID_oscollectdbs_buffer_monitor.log

OS/390 hostname_SID_IID_oshostcollect_buffer_monitor.log

OS/390 DB2 hostname_SID_IID_oshostdb2_buffer_monitor.log

Oracle - Inode Used%

SID_DBhostname_IID_oracledirinode_monitor.log

Oracle - Space FreeSID_DBhostname_IID_oracledirfree_monitor.log

Oracle - Used % SID_DBhostname_IID_oracledirpct_monitor.log



Oracle Archive -Inode Used %

SID_DBhostname_IID_oraclearchivedirinode_monitor.log

Oracle Archive -Space Free

SID_DBhostname_IID_oraclearchivedirfree_monitor.log

Oracle Archive -Used %

SID_DBhostname_IID_oraclearchivedirpct_monitor.log

Oracle Backup -Space Free

SID_DBhostname_IID_oraclebkpdirfree_monitor.log

Oracle Backup -Used %

SID_DBhostname_IID_oraclebkpdirpct_monitor.log

Oracle Check -Space Free

SID_DBhostname_IID_oraclechkdirfree_monitor.log

Oracle Check - Used%

SID_DBhostname_IID_oraclechkdirpct_monitor.log

Oracle Reorg -Inode Used %

SID_DBhostname_IID_oraclereorgdirinode_monitor.log

Oracle Reorg -Space Free

SID_DBhostname_IID_oraclereorgdirfree_monitor.log

Oracle Reorg - Used%

SID_DBhostname_IID_oraclereorgdirpct_monitor.log

Oracle Statistics -Space Free

SID_DBhostname_IID_oraclestatfree_monitor.log

Oracle Statistics -Used %

SID_DBhostname_IID_oraclestatdirpct_monitor.log

Oracle Trace - SpaceFree

SID_DBhostname_IID_oracletrcdirfree_monitor.log

Oracle Trace - Used%

SID_DBhostname_IID_oracletrcdirpct_monitor.log

Oracle datan -Inodes Used %

SID_DBhostname_IID_oraclesubdirinode_monitor.log

Oracle datan - SpaceFree

SID_DBhostname_IID_oraclesubdirfree_monitor.log

Oracle datan - Used%

SID_DBhostname_IID_oraclesubdirpct_monitor.log


G.

Troubleshooting


PRES Screen andDynpro Buffer


hostname_SID_IID_screen_buffer_monitor.log


SID_DBhostname_IID_pres_monitor.log

PXA ProgramBuffer


hostname_SID_IID_program_buffer_monitor.log


SID_DBhostname_IID_pxa_monitor.log

Page Area ¶ For the central monitor:

hostname_SID_IID_page_area_monitor.log


SID_DBhostname_IID_pagearea_monitor.log

Roll Area ¶ For the central monitor:

hostname_SID_IID_roll_area_monitor.log

¶ For the server monitor:

SID_DBhostname_IID_rollarea_monitor.log

SAP Executable -Inode Used %

SID_DBhostname_IID_sapexedirinode_monitor.log

SAP Executable -Space Free

SID_DBhostname_IID_sapexedirfree_monitor.log

SAP Executable -Used %

SID_DBhostname_IID_sapexedirpct_monitor.log

SAP Global - InodeUsed %

SID_DBhostname_IID_sapglobaldirinode_monitor.log

SAP Global - SpaceFree

SID_DBhostname_IID_sapglobaldirpct_monitor.log

SAP Global - Used%

SID_DBhostname_IID_sapglobaldirpct_monitor.log

SAP Home - InodeUsed %

SID_DBhostname_IID_saphomedirinode_monitor.log



SAP Home - SpaceFree

SID_DBhostname_IID_saphomedirfree_monitor.log

SAP Home - Used%

SID_DBhostname_IID_saphomedirpct_monitor.log

SAP Mount - InodeUsed %

SID_DBhostname_IID_sapmountdirinode_monitor.log

SAP Mount - SpaceFree

SID_DBhostname_IID_sapmountdirfree_monitor.log

SAP Mount - Used%

SID_DBhostname_IID_sapmountdirpct_monitor.log

SAP Profile - InodeUsed %

SID_DBhostname_IID_sapprofiledirinode_monitor.log

SAP Profile - SpaceFree

SID_DBhostname_IID_sapprofiledirfree_monitor.log

SAP Profile - Used%

SID_DBhostname_IID_sapprofiledirpct_monitor.log

SAP Transport -Inode Used %

SID_DBhostname_IID_saptraninode_monitor.log

SAP Transport -Space Free

SID_DBhostname_IID_saptranfree_monitor.log

SAP Transport -Used %

SID_DBhostname_IID_saptranpct_monitor.log

SNTAB ShortNameTab Buffer


hostname_SID_IID_shortntab_buffer_monitor.log


SID_DBhostname_IID_sntab_monitor.log

Spool Performance SID_DBhostname_IID_spool_monitor.log

TABL Generic KeyBuffer


hostname_SID_IID_generickey_buffer_monitor.log


SID_DBhostname_IID_tabl_monitor.log


G.

Troubleshooting


TABLP Single KeyBuffer


hostname_SID_IID_singlerec_buffer_monitor.log


SID_DBhostname_IID_tablp_monitor.log

TTAB TableDescription Buffer


hostname_SID_IID_tabledef_buffer_monitor.log


SID_DBhostname_IID_ttab_monitor.log

Update PerformanceSID_DBhostname_IID_update_monitor.log

User ¶ For the central monitor:

hostname_SID_IID_user_monitor.log


SID_DBhostname_IID_user_monitor.log

Work Process SID_DBhostname_IID_workprocess_monitor.log

Work ProcessDispatch Queue

SID_DBhostname_IID_process_dsp_q_monitor.log

Event Adapter Log FilesThe following table describes the log file that is associated with eachManager for R/3 event adapter. The event adapter log files arelocated in one of the following directories:

¶ UNIX: /tmp

¶ Windows NT: %SYSTEMROOT%\temp, where%SYSTEMROOT% is the drive where Windows NT is installed,usually C:

If the \temp directory is not found, the event adapter log files arewritten in one of the following directories:

v Managed node: %BINDIR%\TME\SAP\2.2C

v TMA endpoint: %LCF_BINDIR%\..\TME\SAP\2.2C


Event Adapter Log File

Alert Event Adapter r3mibIID .log

IDOC Event Adapter r3idocIID .log

Syslog Event Adapter r3slogIID .log

Miscellaneous Log FilesThe following table describes miscellaneous log files, such as the logfiles associated with uninstalling Manager for R/3 and TEC scripts.

Log Type Function Log Name

R3Mgr_uninstall21.pl Manager for R/3uninstall

R3Mgr_uninstall21.log

sap_alert_control_cb.sh TEC script sap_alert_control_cb.log

sap_alert_reader_cb.sh TEC script sap_alert_reader_cb.log

sap_gemhbfwd.sh TEC script sap_gemhbfwd.log

sap_gemtecfwd.sh TEC script sap_gemtecfwd.log

sap_gemthfwd.sh TEC script sap_gemthfwd.log

sap_set_r3db_state.sh TEC script sap_set_r3db_state.log

sap_sysupdown_clone_event.sh TEC script sap_sysupdown_clone_event.log

Notes:

1. The R3Mgr_uninstall21.log is located in one of the following directories:

¶ UNIX: /tmp



2. Logs related to TEC scripts are located in one of the following directories on the TECevent server:

¶ UNIX: /tmp



G.

Troubleshooting

TEC EventsAll Manager for R/3 alert events originate from the alert eventadapter. Ther3mib IID program reads the R/3 SysMan interface fora managed R/3 application server. R/3 provides information aboutR/3 alerts through the SysMan interface. Ther3mib IID programcaptures each R/3 alert, converts it to a TEC event, and forwards theevent to the TEC event server. TEC event processing is illustrated inthe following diagram:

The Manager for R/3 provides a set of rules that are run on the TECevent server. These rules will determine if the event isgenericorspecific. Generic eventsare high-level indications of a problem.More information about the alert is available inside of the R/3system. For these events, the Manager for R/3 will performdrill-down processing to gather the more detailed information. Indoing this, the original event will be discarded.Specific eventscontain all information in the event and are forwarded directly to theTEC event consoles.

The drill-down process begins with the TEC rules calling thesap_alert_reader_cb.shscript. This script runs on the TEC eventserver machine. Like tasks, this script automatically generates a logfile in the /tmp directory. This log file is calledsap_alert_reader_cb.log.

The sap_alert_reader_cb.shscript triggers the running of a task onthe remote R3AppServer. The remote task issap_alert_reader.sh.


This task also automatically creates a log file. This log file iscontained in the /tmp directory of the machine on which the R/3application server resides. This log file is called sap_alert_reader.log.

The sap_alert_reader.shscript calls thewr3rfc program to actuallyconnect to the R/3 application server. Thewr3rfc program logs onto the R/3 application server and runs a function moduleJ_8C1_ALERT_READER.

If the drill-down is successful, a more detailed event is returned tothe TEC event server by thesap_alert_reader.shscript. This moredetailed TEC event is forwarded to the TEC event consoles.

Error AlertsErrors in thesap_alert_reader_cb.shand thesap_alert_reader.shscripts will often generate a special error TEC event to the TECevent server. These events are of classAMS_WR3MIB_PROCESS_ALERT. If one of these events occurs,check the sap_alert_reader_cb.log and sap_alert_reader.log files foradditional diagnostic information.

Event Diagnostic ToolsThe processing flow for event generation involves many steps. Youcan debug these steps individually to facilitate problemdetermination. In particular, you can run thewr3mib andwr3rfcprograms from the command line to determine if thewr3mib andwr3rfc programs are working correctly.

wr3mib (r3mibIID) DiagnosticsThe first step in diagnosing event problems is to ensure thatprograms can communicate with the R/3 application server. To dothis, follow these steps:

1. Log on to the machine that is running the R/3 application server.

2. Set up the environment if you have not already done so. See“Setting Up the Environment” on page 255.

3. Go to one of the following directories:



G.

Troubleshooting


4. Run the following commands to determine if basic interfacing tothe R/3 SysMan is working and getting information back fromthe R/3 application server:wr3mib -f -n systemNumber

WheresystemNumberis the R/3 instance number.wr3mib -s -n systemNumber

wr3mib -a -n systemNumber

wr3mib -c -n systemNumber

wr3mib -t iterations polling_delay -n systemNumber

Note: If you are running HP-UX 11 in 64-bit mode, use thewr3mib_64 command. Thewr3mib_64 command usesthe same syntax as thewr3mib command.

If information is returned for all these commands, the interface isworking correctly. If information is not being returned for one ormore of these commands, the R/3 application might have had itsshared memory segments reassigned. For information about R/3memory segment assignments, see “Configuring R/3 ApplicationServer Profiles” on page 50 and “Configuring Manager for R/3 forHP-UX 11” on page 75. Then, contact Tivoli customer support.

The r3mib IID program can have tracing enabled when running as aTEC event adapter daemon. To turn on this debug tracing, use theConfigure Event Adapter task. See “Configuring Event Adapters” onpage 86. When tracing is enabled, ther3mib IID program generates alog file. See “Log Files” on page 256.

wr3rfc DiagnosticsYou can also run thewr3rfc program directly from the commandline. Several levels of diagnostics can be performed.

The most basic test is to ensure that thewr3rfc program iscommunicating with the R/3 application server. The followingcommand tests this connection:wr3rfc -u userid -c client -p password -l language -d SID-h ManagedNode -s InstanceNumber J_8C1_BUFFER_NAMES.TXT


The meanings of each of these parameters is explained in “wr3rfc”on page 171. You will need to substitute values for theuserid,client, password, language, SID, ManagedNode, andInstanceNumberparameters. This command lists the R/3 buffer names.

The wr3rfc program and the J_8C1* files that thewr3rfc programreferences are installed in different directories. To facilitatediagnostic testing, it is recommended to copy these files into acommon directory such as /tmp. Thewr3rfc program is located inone of the following directories:



The J_8C1* files are located in one of the following directories:

¶ Managed node: $BINDIR/../generic_unix/TME/SAP/2.2C/rfc

¶ TMA endpoint:$LCF_BINDIR/../../generic_unix/TME/SAP/2.2C/rfc

To see additional detail, use thewr3rfc command with the debugoption as follows:wr3rfc -D 2 -u userid -c client -p password -l language -d SID-h ManagedNode -s InstanceNumber J_8C1_BUFFER_NAMES.TXT

The wr3rfc command provides several levels of diagnosticinformation.

¶ Level one (-D 1) prints status information on the R/3communication steps to standard error output.

¶ Level two (-D 2) provides a step-by-step detailed statusbeginning after the parsing of the RFC file.

¶ Level three (-D 3) is a full step-by-step status of programexecution including the parsing of the RFC file.

The J_8C1_BUFFER_NAMES function module is provided as abasic test of the Manager for R/3 RFC functionality.


G.

Troubleshooting

Configuring Monitor Logging ModeManager for R/3 provides a method for turning on monitor trace forManager for R/3 monitors in the R3 Server Central, R3 ServerRemote, R3 ITS Server, R3 Windows NT File System, and R3UNIX File System monitoring collections. When monitor trace isenabled, each monitor running on the target R3AppServer orR3ITSServer object creates a log file. See “Log Files” on page 256.The log files are reused for each running of the monitor, soinformation is overwritten as the monitors are redispatched. Todetermine the cause of a problem with a monitor, enable monitortrace and examine the appropriate log file.

To enable monitor trace, run the Configure Monitor Logging Modejob in the R3 Configuration Tasks library in the R3 Configurationpolicy subregion. The Configure Monitor Logging Mode dialog isdisplayed:


The monitors for buffers, roll area, page area, work process, workprocess dispatch queues, long running process, cancelled job, user,heap memory, extended memory, OS Collect, OS/390, and OS/390DB2 rely on thewr3rfc program. If these monitors are failing, referto diagnostic techniques forwr3rfc as explained in “wr3rfcDiagnostics” on page 270.


SAPGUI File Package DistributionTo determine the source of problems resulting from distributingclient software (SAPGUI) file packages, look in theprofile.log file,whereprofile is the name of the file package profile. Theprofile.logfile is located in one of the following directories:

¶ Managed node:

$BINDIR/../generic_unix/TME/SAP/fp/profilemgr, whereprofilemgr is the name of the profile manager

¶ TMA endpoint:

$LCF_BINDIR/../generic_unix/TME/SAP/fp/profilemgr, whereprofilemgr is the name of the profile manager

Icon StateIf an R3AppServer or R3DBServer icon state is incorrect, ensurethat the Application Server Status monitor has been enabled and hasbeen distributed. If you want to update the state of an R3DBServericon with the status of the database server as reported by the TivoliManager for DB2 or Tivoli Manager for Oracle, ensure that theprofile that contains the database status monitor has been distributed.If an R3ITSServer icon state is incorrect, ensure that the ITS ServerStatus monitor has been enabled and has been distributed. Also,check the monitoring interval for excessively long schedule periods.

File System LayoutThe Manager for R/3 installation process creates the followingdirectories:

¶ Managed node:

$BINDIR/../generic_unix/TME/SAP

$BINDIR/TME/SAP

¶ TMA Endpoint:

$LCF_BINDIR/../../generic_unix/TME/SAP

$LCF_BINDIR/../TME/SAP


G.

Troubleshooting

The Configure Event Server task creates a rule base on the TECevent server in the following default location: /usr/tec_rules/SAP.

Hints on Using Tivoli GEMThis section contains the following information about using TivoliGEM:

¶ “Using the Tivoli GEM Console”

¶ “Tivoli GEM Icon State” on page 276

¶ “Tivoli GEM Server Database Corruption” on page 276

¶ “Business and Component Description Files” on page 276

¶ “Icon Files” on page 277

Using the Tivoli GEM ConsoleIf an R/3 system, an R/3 application server, an R/3 database servericon, or an R/3 ITS server is not displayed on the Tivoli GEMconsole, follow these steps:

¶ Verify that the Tivoli GEM business description files (BDFs) andthe component description files (CDFs) have been installed inthe $BINDIR/TDS/server/db/current/appdefs directory on theTivoli GEM server. Stop and restart the Tivoli GEM server sothat the server parses the BDFs and CDFs.

Note: After you stop the Tivoli GEM server, you might want todelete the ihserror.log and ihsmessage.log files in the$BINDIR/TDS/server/log directory. This enables you tosee only new messages regarding the Tivoli GEM serverwhen you restart it.

¶ Verify that the Tivoli GEM TEC classes and rules are installed:

1. Enter thewlscurrb command to display the name of theactive rule base.

2. Enter thewlsrbclassactive_rulebase_namecommand to listthe defined event classes. Ensure that theAPM_HEARTBEAT and the APM_THRESHOLD classes aredefined.


3. Enter thewlsrbrules active_rulebase_namecommand to listthe defined rule bases. Ensure that the interapp.rls rule baseis defined because this rule base forwardsAPM_HEARTBEAT events to the Tivoli GEM server. Also,ensure that the sap_gemevents.rls rule base is defined. Thesap_gemevents.rls rule base converts R/3 special eventclasses to Tivoli GEM event classes and forwards the eventsto the Tivoli GEM server.

4. If the needed classes or rules are not defined, configureTivoli GEM event enablement.

¶ Verify that the SAP_APM_HEARTBEAT or theAPM_HEARTBEAT event is getting to the TEC. If theSAP_APM_HEARTBEAT or the APM_HEARTBEAT event doesnot display on the TEC:

1. Enter thewtdumprl command on the TEC event server. Thewtdumprl command displays the events in the reception logon the TEC event server.

2. Look for errors associated with theSAP_APM_HEARTBEAT or the APM_HEARTBEAT event.

¶ Check the ihsttec.cfg file in the $BINDIR/TDS/EventServicedirectory to verify that the TEC event server has been configuredto send events to the Tivoli GEM server.

¶ Verify that the APM_HEARTBEAT event is getting to the TivoliGEM server.

1. Start the Tivoli GEM server with thetserver start -bcommand and option to log events to the Tivoli GEM serverlog.

2. Look in the $BINDIR/TDS/server/log/ihsmessage.log file tosee if the Tivoli GEM server is receiving the heartbeatevents.

3. If the TEC is receiving the APM_HEARTBEAT,SAP_APM_HEARTBEAT, and APM_THRESHOLD eventsbut the Tivoli GEM server is not receiving the


G.

Troubleshooting

APM_HEARTBEAT and APM_THRESHOLD events, ensurethat the TEC is configured to send events to the Tivoli GEMserver.

Tivoli GEM Icon StateIf an R/3 system, an R/3 application server, R/3 database server, orR/3 ITS server icon does not aggregate, run theSend GEMHeartbeat task in the R3 Configuration Tasks library or manuallyaggregate the icons.

Tivoli GEM Server Database CorruptionIf the Tivoli GEM databases are damaged or you want to refresh theTivoli GEM console, follow these steps:

1. Stop the Tivoli GEM server.

2. Erase all files in the current$BINDIR/TDS/server/db/backup/datab and$BINDIR/TDS/server/db/current/datab directories. Do not deletethe directories.

3. Restart the Tivoli GEM server. This automatically copies thedatabases from the default databases to the current databases.

4. Run the Send GEM Heartbeat task in the R3 Configuration Taskslibrary. The Send GEM Heartbeat task sends a heartbeat event tothe Tivoli GEM server for each R/3 resource selected as a taskendpoint, and it creates an icon on the Tivoli GEM console.

Note: The Tivoli GEM databases are damaged if you cannot log onfrom the Tivoli GEM console or if the Topology Server orTopology Communication Server windows display errormessages.

Business and Component Description FilesTivoli GEM instrumentation provides the following businessdescription files and the following component description files:

¶ R/3 Business System: R32_1Tivoli.bsdf

¶ R/3 Business System Component: R3System2_1Tivoli.bcdf


¶ R/3 Business System Mapping files for R/3 systems, R/3application servers, R/3 database servers, and R/3 ITS servers:v R3System2_1Tivol.bmdfv R3Applicatio2_1Tivol.bmdfv R3Database2_1Tivol.bmdfv R3ITSServer2_1Tivol.bmdf

¶ R/3 Software Component files for R/3 systems, R/3 applicationservers, R/3 database servers, and R/3 ITS servers:v R3System2_1Tivoli.cdfv R3Applicatio2_1Tivoli.cdfv R3Database2_1Tivoli.cdfv R3ITSServer2_1Tivoli.cdf

¶ R/3 Global Description File: SAPR32_1Tivoli.gdf

The business description files are copied into the$BINDIR/TDS/server/db/current/appdefs directory on the TivoliGEM server when you selectLoad New AMP from theFile menuon the Tivoli GEM console.

Icon FilesThe icon files include the following:

¶ Manager for R/3 icon: 16_r3_20.gif, 24_r3_20.gif, 32_r3_20.gif

¶ R/3 system aggregate icon: 16_r3system.gif, 24_r3system.gif,and 32_r3system.gif

¶ R/3 application server icon: 16_r3application.gif,24_r3application.gif, and 32_r3application.gif

¶ R/3 database server icon: 16_r3database.gif, 24_r3database.gif,and 32_r3database.gif

¶ R/3 ITS server icon: 16_r3itsserver.gif, 24_r3itsserver.gif, and32_r3itsserver.gif

The icon files are copied into the$BINDIR/TDS/server/db/current/icons directory on the Tivoli GEMserver when you selectLoad New AMP from theFile menu on theTivoli GEM console.


G.

Troubleshooting


Index

Numerics64-bit support, HP-UX 11 75

Aaccessing online documentation xviadapter, event, parameters

configuring 86displaying 87

administrator authorizationManager for R/3 33Tivoli GEM instrumentation 151

aggregation, Tivoli GEM instrumentationcorrecting 155description 148resources 155

alert, R/3CCMS-generated 197event classes 180event slots 193wr3mib diagnostics 269wr3rfc diagnostics 270

alert event adapterdescription 88filtering events 104parameters


r3mibIID.conf file 88starting 133stopping 133

application proxyinstalling 11upgrading 13

application proxy patch, installing 13application server

central monitors profile 110

application server(continued)display performance information 134monitors profile manager 110OS collect monitoring source 123remote monitors profile 110starting 133status, determining 38status monitor 110, 113stopping 133

application server status monitoring source 113assigning authorization roles

Manager for R/3 33Tivoli GEM instrumentation 151

attributes, monitoring 106authentication package for Windows NT,

enabling 74authorization

configuration tasks 36list maintenance task 38Manager for R/3 function module 223R3 App Server tasks 132R3 DB Server tasks 136R3 ITS Server tasks 137R3 System tasks 131RFC access 49roles, assigning

example 34Manager for R/3 33Tivoli GEM instrumentation 151

automatic discoveryconfiguring data sharing 56description 55enabling for Windows NT 73scheduling

UNIX 59Windows NT 58

stopping 60availability management

description 3


Index

availability management(continued)event adapters

alert 88IDOC 96syslog 91

Bbatch jobs, managing 134bidirectional communication 201buffer monitoring source 213business description files

contents 276installing 151upgrading 151

Ccancel batch job task 134cancel process task 135cancelled job, monitoring 121cancelled job event slots 196CCMS-generated alerts 197central monitors 106client software

file packageconfiguring for versions 4.5B and

later 143configuring for versions prior to

4.5B 140distributing 145

installationconfiguring for versions 4.5B and



closing harmless events 200collections, monitoring 3commands

create_uninstall_task.sh 21

commands(continued)R3Mgr_uninstall21.pl 21syntax conventions 167wlcftap 74wr3mib 169wr3mib_64 169wr3rfc 171wsettap 74

component description filescontents 276installing 151upgrading 151

Computing Center Management System(CCMS) 3, 197

configuration filesr3idocIID.conf 100r3mibIID.conf 88r3slogIID.cl 92r3slogIID.conf 92sap_discovery.cfg 56

configuration tasksconfigure autodiscovery for NT 58configure autodiscovery for UNIX 59configure event adapter 86configure event console 83configure event server 82configure remote function call 71create new subscriber list 70create RDBMS manager status monitor 78display event adapter information 87locating 35remove autodiscovery 60required role and target 36start event adapter 87stop event adapter 87

configure autodiscovery for NT task 58configure autodiscovery for UNIX task 59configure event adapter task 86configure event console task 83configure event server task 82configure remote function call task 71configuring

automatic discoverydata sharing 56UNIX 59Windows NT 58


configuring (continued)client software file package

versions 4.5B and later 143versions prior to 4.5B 140

event adapter 86event console 83event handling

event adapter 86event console 83overview 81tasks 82TEC event server 82

Manager for R/3authorization roles, assigning 33authorization roles, example 34automatic discovery, enabling for Windows

NT 73configuration tasks, locating 35desktop after configuration 32environment variable for Windows

NT 75exit routines for Windows NT 72extending database server status

reporting 78for Windows NT 72HP-UX 11 enhancements 75overview of tasks 31R/3 objects, automatic discovery,

stopping 60R/3 objects, creating 53R/3 objects, creating by automatic

discovery, description 55R/3 objects, creating by automatic

discovery for NT 58R/3 objects, creating by automatic

discovery for UNIX 59R/3 objects, creating manually 60SAP file access, enabling for Windows

NT 73tasks, overview 35Tivoli authentication package for Windows

NT 74monitor logging mode 272R/3 for alerts 50remote function call (RFC) 71

configuring (continued)SAPGUI file package

versions 4.5B and later 143versions prior to 4.5B 140

TEC event server 13, 82TMRs 10user ID for RFC access 49

console, Tivoli GEMhints on using 274overview 148refreshing 276syncronizing with the desktop 154

contacting customer support xixcopying R/3 transports 46correlation rule 205create new subscriber list task 70create RDBMS manager status monitor task 78create_uninstall_task.sh command 21creating

exit routines for Windows NT 72R/3 objects

automatic discovery for NT 58automatic discovery for UNIX 59description 53manually 60result 64where to create 54

subscriber lists 70customer support, contacting xixcustomizing events sent to TEC

alert, filtering 104IDOC

filtering 104r3idocIID.conf file, modifying 100

syslogfiltering 104r3slogIID.cl file, adding entries 94r3slogIID.cl file, modifying 93

Ddaemons, monitoring

sappld 111saprouter 111


Index

data sharing 56, 77database server

central monitors profile 110monitors profile manager 110OS collect monitoring source 124status

determining 39extending 78

database status integration rules 204dbaccess, starting 136deleting R/3 objects 68discovery, automatic

configuringfor data sharing 56UNIX 59Windows NT 58

description 55enabling for Windows NT 73stopping 60

display batch jobs task 134display buffer information task 134display event adapter information task 87display OS/390 DB2 information task 134display OS/390 information task 134display OS collect information task 134display process information task 135display processes task 135display roll page information task 134displaying event adapter configuration 87distributed monitoring

event classes 191rules 203

distributingclient software 145SAPGUI software 145transports 45

documentation, online, accessing xvidrill-down processing 182duplicate event checking 200

Eendpoint

R3AppServer 29

endpoint (continued)R3DBServer 29R3ITSServer 29R3System 29target

configuration tasks 36event handling tasks 82list maintenance task 38R3 App Server tasks 132R3 DB Server tasks 136R3 ITS Server tasks 137R3 System tasks 131

environment, setting up 255error alerts, troubleshooting 269error event classes 193event

classescategories 179distributed monitoring 191error 193operational 182R/3 alert 180R/3 syslog 186status 192Tivoli GEM 192Tivoli GEM instrumentation 192

rulescorrelation 205database status integration 204distributed monitoring 203TEC event server 202Tivoli GEM instrumentation 205

slotscancelled job 196IDOC 195R/3 alert 193R/3 syslog 194

TEC processing 268troubleshooting

wr3mib diagnostics 269wr3rfc diagnostics 270

event adapteralert

configuring 86description 3, 88displaying configuration parameters 87


event adapter(continued)filtering events 104r3mibIID.conf file 88starting 87, 133stopping 87

IDOCdescription 3, 96displaying configuration parameters 87events sent to TEC 98events sent to TEC, controlling 100filtering events 104how it works 97performance considerations 101r3idocIID.conf file 100starting 87stopping 87

syslogconfiguring 86description 3, 91displaying configuration parameters 87events sent to TEC, controlling 93events sent to TEC by default 92files 92filtering events 104r3slogIID.cl file 92r3slogIID.cl file, adding entries 94r3slogIID.cl file, modifying 93r3slogIID.conf file 92starting 87, 133stopping 87

event console, configuring 83event correlation 201event drill-down processing 200event handling

configuringevent adapter 86event console 83overview 81tasks 82TEC event server 82

Tivoli GEM instrumentation 149event server, TEC, configuring 82, 83events

IDOC, sent to TECcontrolling 100interpreting 98

events (continued)syslog, sent to TEC

by default 92controlling 93

examplesauthorization roles, assigning 34discover connections task, Tivoli GEM

R/3 application server 164R/3 database server 165R/3 ITS server 164R/3 system 163

filtering events 104instrumenting a connection

R3Application component 163R3Database component 164R3ITSServer component 164R3System component 163

syslog events, customizing events sent toTEC 95

Windows NTstart exit routine 72stop exit routine 73

wr3rfc command 175executing a task

from the desktop 127from the Tivoli GEM console 159

exit routines for Windows NT, creating 72extended database status reporting 8, 78extended memory monitoring source 214extensibility 7

Ffeatures 1file package

client softwaredistributing 145log file 273

SAPGUIdistributing 145log file 273

transportsdistributing 45objects included 44


Index

file system layout 273file systems, R/3, monitoring 116files

event adapter, alert, r3mibIID.conf 88event adapter, IDOC, r3idocIID.conf 100event adapter, syslog

r3slogIID.cl 92r3slogIID.conf 92

log, location of 256sap_discovery.cfg file 56

free space checking 5function modules

authorization, Manager for R/3 223importing

from command line 47using TMS 48

wr3rfc command 171

Ggetting started 27

Hheap memory monitoring source 214HP-UX 11

64-bit support 75shared memory windows 75

Iicon files, Tivoli GEM instrumentation 276IDOC event adapter

description 96events sent to TEC, controlling 100filtering events 104how it works 97parameters

configuring 86

IDOC event adapter(continued)parameters(continued)

displaying 87performance considerations 101r3idocIID.conf file 100

IDOC event slots 195IDOC status codes 219importing function modules

from command line 47using TMS 48

installationclient software

configuring for versions 4.5B andlater 143

configuring for versions prior to4.5B 140

distributing 145processing 5requirements


SAPGUIconfiguring for versions 4.5B and



installingapplication proxy 11application proxy patch 13Manager for R/3

authorization role required 18desktop after installation 27overview 9, 15prerequisites 9procedure 18requirements 9results 27where to install 9

Tivoli GEM instrumentationadministrator authorization 151components, location of 151overview 147requirements 151rules 154task libraries 152


instrumented components 150instrumenting connections to Manager for R/3

componentsdescription 162examples

R3Application component 163R3Database component 164R3ITSServer component 164R3System component 163

interconnected TMRs 13ITS server

monitoring collection 106status, determining 40

ITS server status monitor 111

Jjobs 35

Llibraries, task

description 5R3 App Server tasks 132R3 Configuration tasks 36R3 DB Server tasks 136R3 Internal tasks 35R3 ITS Server tasks 137R3 List Maintenance tasks 38R3 System tasks 131Tivoli GEM instrumentation 150

locating configuration tasks 35log files, location of 256logging mode, monitor, configuring 272long running work process monitoring 121, 212

Mmanaged nodes, monitors profile manager 111

management taskscancel batch job 134cancel process 135display batch jobs 134display buffer information 134display OS/390 DB2 information 134display OS/390 information 134display OS collect information 134display process information 135display processes 135display roll page information 134release batch job 134running


start database 136start dbaccess 136start event adapter 133start ITS server 137start R3 system 131start server 133stop database 136stop event adapter 133stop ITS server 137stop R3 system 131stop server 133Tivoli GEM instrumentation

description 157R3Application component 158R3Database component 158R3ITSServer component 159R3System component 157

message server status monitor 111messages 227monitoring

attributes 106buffer 213extended memory 214heap memory 214long running work process 212OS/390 217OS/390 DB2 215OS collect 208page area 210performance 214roll area 209


Index

monitoring (continued)user 215work process 211work process dispatch queue 212

collectionsITS server 106server central 107server remote 107UNIX file systems 109, 116Windows NT file systems 109, 117

logging mode, configuring 272profile manager

application server 110database server 110distributed daemon monitors 111ITS monitors 111managed nodes 111R3 central instance monitors 111

R3 DB server central monitors profile 110R3 ITS monitors profile manager 111R3 managed nodes profile manager 111R3 message server monitors profile 111R3 print monitors profile 111R3 SAP Router monitors profile 111R3 server autodiscovery monitors

profile 110R3 server central monitors profile 110R3 server remote monitors profile 110R3 UNIX file system monitors profile 112R3 Windows NT file system monitors

profile 112saplpd daemon 111saprouter daemon 111sources

application server status 113cancelled job 121file system 116long running work process 121OS/390 123, 125OS/390 DB2 125OS collect 123OS collect, application server 123OS collect, database server 124performance 115server central 107server remote 107

monitoring (continued)sources(continued)

storage areas 114summary 106user sessions 119work process 120work process dispatch queue 120

Tivoli GEM instrumentationhow monitors work 161Manager for R/3-supported monitors 160operability 161

Oobjects, R/3

creatingautomatic discovery for NT 58automatic discovery for UNIX 59manually 60result 64

deletingprocedure 68result 68

online documentation, accessing xvioperational event classes 182OS/390

data sharingconfiguring automatic discovery 56considerations 77

monitoring 78, 123R/3 database objects 77R/3 release support 76R/3 transports 77

OS/390 DB2 monitoring source 125, 215OS/390 monitoring source 125, 217OS collect monitoring source

application server 123attributes 208database server 124


Ppage area monitoring source 210performance, R/3, monitoring 115performance considerations, IDOC event

adapter 101performance monitoring source 214platform type checking 5process information, displaying 135profile manager

R3 App Server 110R3 Central Instance Monitors 111R3 DB Server 110R3 Distributed Daemon Monitors 111R3 ITS monitors 111R3 managed nodes monitors 111

RR/3 alert

CCMS-generated 197configuring 50event classes 180event slots 193wr3mib diagnostics 269wr3rfc diagnostics 270

R/3 environment with Tivoli 1R/3 objects

creating 53automatic discovery for NT 58automatic discovery for UNIX 59manually 60result 64


where to create 54R/3 syslog

event classes 186event slots 194

R/3 systemconfiguring for alerts 50

R/3 transportscopying 46

R/3 transports(continued)distributing the file package 45objects included 44

R3 App Server Monitors profile manager 110R3 App Server tasks

authorization 132cancel batch job 134cancel process 135display batch jobs 134display buffer information 134display OS/390 DB2 information 134display OS/390 information 134display OS collect information 134display process information 135display processes 135display roll page information 134release batch job 134start event adapter 133start server 133stop event adapter 133stop server 133

R3 central instance monitors profilemanager 111

R3 Configuration tasks library 36R3 DB Distributed Daemon Monitors profile

manager 111R3 DB server central monitors profile 110R3 DB Server Monitors profile manager 110R3 DB Server tasks

authorization 136start database 136start dbaccess 136stop database 136

R3 Internal tasks library 35R3 ITS Monitors profile manager 111R3 ITS Server tasks

authorization 137start ITS server 137stop ITS server 137

R3 List Maintenance tasks library 38R3 managed nodes monitors profile

manager 111R3 message server monitors profile 111R3 print monitors profile 111R3 SAP Router monitors profile 111R3 server autodiscovery monitors profile 110


Index

R3 server central monitors profile 110R3 server remote monitors profile 110R3 system tasks

start R3 system 131stop R3 system 131

R3 System tasksauthorization 131

R3 UNIX file system monitors profile 112R3 Windows NT file system monitors

profile 112R3AppServer object

creatingmanually 61result 65using automatic discovery 55


description 29endpoint name 29tasks, pop-up menu 65

R3DBServer objectcreating

manually 62result 66using automatic discovery 55



r3idocIID.conf file 100R3ITSServer object

creatingprocedure 63result 67



R3Mgr_uninstall21.pl command 21r3mibIID.conf file 88

R3System objectcreating

manually 60result 64using automatic discovery 55



release batch job task 134remote function call (RFC)

configuring 71user ID authorization 49

remote monitors 106remove autodiscovery task 60requirements, installation


RFCuser ID authorization 49

roll area monitoring source 209rules

bidirectional communication 201closing harmless events 200correlation 205database status integration 204distributed monitoring 203duplicate event checking 200event correlation 201multi-region support 201TEC event server 202Tivoli GEM instrumentation 154, 205

running a taskfrom the desktop 127from the Tivoli GEM console 159

Ssap_discovery.cfg file 56SAP file access, enabling for Windows NT 73


SAPGUIfile package

configuring for versions 4.5B andlater 143

configuring for versions prior to4.5B 140

distributing 145log file 273

installationadministrator-named file package 6command execution 6components, optional 5configuring for versions 4.5B and


4.5B 140distributing 145R/3 releases supported 5

sappld daemon, monitoring 111saprouter daemon, monitoring 111security enhancements 6send GEM heartbeat task 154server

applicationcentral monitors profile 110display performance information 134monitoring status 113OS collect monitoring source 123remote monitors profile 110starting 133status monitor 110

databasecentral monitors profile 110monitors profile manager 110OS collect monitoring source 124starting 136

ITSstarting 137status monitor 111

message, status monitor 111status

correcting on the desktop 273correcting on the Tivoli GEM

console 276Tivoli GEM

database corruption 276

server (continued)Tivoli GEM (continued)

overview 148shared memory windows, HP-UX 11,

requirements 75sources and attributes, monitoring

buffer 213extended memory 214heap memory 214long running work process 212OS/390 217OS/390 DB2 215OS collect 208page area 210performance 214roll area 209user 215work process 211work process dispatch queue 212

sourcing the environment 255start database task 136start dbaccess task 136start event adapter task 87, 133start exit routine for Windows NT 72start ITS server task 137start R3 system task 131start server task 133status

application server, determining 38correcting

on the desktop 273on the Tivoli GEM console 276

database serverdetermining 39extending 78

ITS server, determining 40status codes, IDOC 219status event classes 192status monitoring

application server 110ITS server 111message server 111

stop database task 136stop event adapter task 87, 133stop exit routine for Windows NT 73stop ITS server task 137


Index

stop R3 system task 131stop server task 133stopping automatic discovery 60storage areas, monitoring 114subscriber lists, creating 70syntax conventions, command 167syslog, R/3

event classes 186event slots 194

syslog event adapterdescription 91events sent to TEC

controlling 93default 92

filtering events 104parameters


r3slogIID.cl fileadding entries 94description 92modifying 93

r3slogIID.conf file 92starting 133stopping 133

SysMandescription 3wr3mib_64 command 169wr3mib command 169

Ttask libraries

description 5R3 App Server tasks 132R3 Configuration tasks 36R3 DB Server tasks 136R3 Internal tasks 35R3 ITS Server tasks 137R3 list maintenance tasks 38R3 System tasks 131Tivoli GEM instrumentation

description 150installing 152

task libraries(continued)Tivoli GEM instrumentation(continued)

uninstalling 165upgrading 152

tasks, configurationconfigure autodiscovery for NT 58configure autodiscovery for UNIX 59configure event adapter 86configure event console 83configure event server 82configure remote function call 71create new subscriber list 70create RDBMS manager status monitor 78display event adapter information 87remove autodiscovery 60required role and target 36start event adapter 87stop event adapter 87

tasks, managementcancel batch job 134cancel process 135database server

start database 136start dbaccess 136stop database 136

display batch jobs 134display buffer information 134display OS/390 DB2 information 134display OS/390 information 134display OS collect information 134display process information 135display processes 135display roll page information 134executing

from the Tivoli GEM console 159ITS server

start ITS server 137stop ITS server 137

R/3 systemstart R3 system 131stop R3 system 131

release batch job 134running


start event adapter 133


tasks, management(continued)start server 133stop event adapter 133stop server 133Tivoli GEM instrumentation

description 157R3Application component 158R3Database component 158R3ITSServer component 159R3System component 157

tear-away log, Tivoli GEM console 159TEC event server

configuring 13, 82rule base

bidirectional communication 201closing harmless events 200duplicate event checking 200event correlation 201event drill-down processing 200multi-region support 201

rules 202Tivoli authentication package for Windows NT,

enabling 74Tivoli customer support, contacting xixTivoli GEM

consolehints on using 274overview 148refreshing 276synchronizing with the desktop 154

event classes 192server

database corruption 276overview 148

Tivoli GEM instrumentationaggregation

description 148navigating to resources 155

event classes 192event handling 149installation requirements 150installing

business description files 151components, location of 151overview 147rules 154

Tivoli GEM instrumentation(continued)installing (continued)

task libraries 152instrumented components 150task libraries 150uninstalling task libraries 165upgrading

business description files 151task libraries 152

TMRs, configuring 10transports, R/3

copying 46distributing the file package 45objects included 44

troubleshootingenvironment, setting up 255error alerts 269event processing

wr3mib diagnostics 269wr3rfc diagnostics 270

file system layout 273log files, location of 256monitor logging mode, configuring 272server status, correcting

on the desktop 273on the Tivoli GEM console 276

TEC event processing 268Tivoli GEM console

hints on using 274refreshing 276

Tivoli GEM server database corruption 276

Uuninstalling

Manager for R/3 21Tivoli GEM instrumentation task

libraries 165UNIX file systems, monitoring

collection 109how to use 116

upgradingapplication proxy 13


Index

upgrading (continued)Manager for R/3

from version 1.5 or 1.5.1 15from version 2.0 17

Tivoli GEM instrumentation tasklibraries 152

user ID, configuring for RFC access 49user interface options

desktop 7Tivoli GEM 8

user monitoring source 215user sessions, R/3, monitoring 119

WWindows NT

creating exit routines for 72enabling

automatic discovery 73SAP file access 73Tivoli authentication package 74

environment variable, setting 75file systems, monitoring 109, 116, 117start exit routine example 72stop exit routine example 73

wlcftap command 74work process

cancelling 135displaying 135monitoring 120

work process dispatch queue, monitoring 120,212

work process monitoring source 211wr3mib_64 command 169wr3mib command 169wr3mib diagnostics 269wr3rfc command 171wr3rfc diagnostics 270wsettap command 74


Part Number: 5697ASA

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC31-8411-04

(1P)

P/N:

5697ASA